GL Posting Error (Fixed Assets)

(0) Share

Report

Posted on by Community Member

I keep getting the following error when I try to post this Fixed Assets Batch. See how the account number isn't populating and it has a zero dollar amount. I've tried deleting that line and it won't let me and I've tried putting an Account number in there and it won't save. How do I get this entry to post?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Community Member on at

Like (0)

Report

Was this reply helpful? Yes No
Romryan on at

Like (0)

Report

you have not posted the error

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I know. I can't get it to post for some reason.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

It has the account number blank and then zero dollars but won't let me delete the line, nor will it let me put an account in there just so it will post. And when I try to post it says "One or more accounts is invalid." Any suggestions/help you can give me would be greatly appreciated.

Was this reply helpful? Yes No
Suggested answer

Victoria Yudin 22,769 on at

Like (1)

Report

I have seen this happen when the GL accounts (in this case for Fixed Assets) were imported or changed manually in SQL and there is an account index in the tables, but that account index is not in your GL tables.

If you can find the offending Fixed Asset and look at its account numbers you will likely see one where the account is blank and the Account Description says something like "Account not found" instead of also being blank.

I am surprised it's not letting you delete the line in the GL. If you expand the view in the GL transaction to show the Account Description, does it say "Account not found"?

Instead of deleting it - will it let you type in an account number?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I am having the same issue.

> Retired and asset not knowing that it did not have all account fields populated.

> Ran the GL Posting routine

> The posting has a line for the transaction with no account and $0.00 in both the Debit and Credit fields.

> Tried to add an account, but it still would not post the transaction.

> Corrected the accounts on the asset.

> Undid the retirement.

> Processed the posting, and now both the retirement and retirement undo transactions have a line with a missing account.

> Booked the retirement again.

> Processed the posting. The original retirement and retirement undo are still missing an account, but the new retirement has the field populated. No matter what account I try to enter for those lines, I still get the same "invalid account" error, and I cannot delete the lines in the GL Posting routine.

This error is occurring in the FA module, running the routine to create the GL Posting. If it were in the GL side, I would be able to delete the line without any trouble.

Any ideas from anyone?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I had this exact same issue. I tried the solution Victoria suggested, though the assumed symptoms didn't match.

I went to the offending asset and looked at the assigned GL accounts. None of them showed as "Account Not Found".... instead they showed legitimate GL accounts.

So anyway, I replaced the GL accoutnts... no big deal for me since this asset didn't even have a distribution... it had no acquisition cost.

It didn't occur to me to check if the old GL accounts were inactive.

Was this reply helpful? Yes No
Suggested answer

HeatherD 425 on at

Like (0)

Report

All,

There is a script posted here to resolve the issue: www.erpsoftwareblog.com/.../fixed-assets-additions-no-accounts-gl-posting-faadd

However, as you know, writing to SQL directly is often a last resort especially if you do not have someone with the skill set to understand what is happening in your org.

My "silly" workaround is to simply hand-key the missing entries in GL and going forward always use a range for your GL Posting. If this issue happened in 2018-02, then next period 2018-03 this transaction will not be selected in the range and the error will not occur.

Let me know if you need more clarity in my resolution suggestions.

Was this reply helpful? Yes No