You’re offline. This is a read only version of the page.
Announcements
I get an error message during the general ledger year-end closing that says "Account Assigned to a transaction is missing". I have followed KB 855209 to find the journal entry that does not have an ACTINDX value in the GL00100 table. Does anybody know which table I remove the offending journal entry from? It says to fix these remove these entries, but from what table GL00100 or GL20000?
It is a beginning balance entry made on 6/30/2012 but shows in my 2013 open year.
Thanks.
Susan
*This post is locked for comments
Hi all,
I see you've got this problem solved, but just as an FYI, the GL close checks the tables against the GL00105 table for valid indexes. As has been said before, every transaction needs to have an index that exists in the GL00105 table. Of course 'blank' doesn't exist in the table.
The other thing that happens, is if you are closing to divisional accounts, it makes sure you have a Retained Earnings account for every division. This is true whether you have anything to 'close' to it or not.
Kind regards,
Leslie
Are you importing directly into the GL20000 table as opposed to importing GL batches and posting them? If so, I would stop doing that and import into batches. This way the GL transactions will contain records with a zero value for the ACTINDX field.
We get this error message on a fairly regular basis during year end closing. In our case the ACTINDX has always been zero and the debit amounts and credit amounts have also been zero. I think it comes from some of our Integration Manager imports. Our solution is to delete the transaction from GL20000 after verifying that both the debit and credit amounts are zero.
Keith McConnell
Joshua is totally right, that is the cause of the problem according to the knowledge base article
"The error occurs if there are transactions in the General Ledger Open table (GL20000) that have an account index value that is not present in the Account Master Table (GL00100)."
Hi All,
The message is saying you are missing an account, not the transaction right? That means there should be an ACTINDX value in the GL20000 table that does not exist in one of the following: GL00101, GL00102, GL00105.
My suggestion would be to first check all of the above GL tables for account setup to make sure the account with the specified index is missing, and if so, add the account back to the system normally if you know what the journal entry is for, and assign the account index from the GL20000 table on the transaction to the new account in all the setup tables where the new account exists.
This way you do not have to delete a GL entry, or make a correcting entry to something that may or may not be impacting your balance sheet / P&L.
I would suggest correcting the entry in GL20000 rather than removing the corrupted entry. Although I am not a big fan of Database correction, I wouldn't think updating the "Account Index" field would not be of any associated risk.
Look in the GL20000 table.
#1
André Arnaud de Cal...
293,440
Super User 2025 Season 1
#2
Martin Dráb
232,569
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
