GLCCON: Consolidation Data Stuck in GL_CONS_INTERFACE Interim Table EU02 with Error Due to Unmapped Accounts
Last updated on APRIL 07, 2016
Applies to:Oracle General Ledger - Version 18.104.22.168 to 22.214.171.124 [Release 11.5.10]
Information in this document applies to any platform.
Consolidation method used is Transactions. At times not all the subsidiary accounts are mapped to the parent set of books in which case journal import may end in EU02 " Unbalanced journal entry is not accepted because suspense posting is not allowed in this set of books. "
In this scenario after the mapping is corrected, is not possible to add missing lines via the journal import /correct form. Instead consolidation needs to be run again. However, even after deleting the data in the GL_INTERFACE table the erroneous data is still stuck in the interim table 'GL_CONS_INTERFACE_XXXXX' from the first consolidation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms