Journal Entries From Financial Accounting Hub Are Going Into Suspense
(Doc ID 2353768.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Financials Accounting Hub - Version 12.2 and later
Information in this document applies to any platform.
All journal entries from Financial Accounting Hub (FAH) are generating using the suspense code combination (CCID) even though the CCID used in interface is valid, and the journal fails Create Accounting with Error Message:
"There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects. Please enable the profile option SLA: Enable Diagnostics,create accounting again, and run the report Transaction Objects Diagnostics to identify the problem."
FND: Connection Tagging is enabled
This occurs in the specific scenario where when one row fails with an invalid account, then all subsequent journal rows generate to suspense account.
If no rows fail, all journal lines generate using the correct CCIDs.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Apply patch 25210929:R12.XLA.C|