R12: AP: Undo Accounting Errors out with "XLA-95103: An internal error occurred." or "Journal entry cannot be reversed as its not transferred to General Ledger."
(Doc ID 1664403.1)
Last updated on DECEMBER 07, 2023
Applies to:
Oracle Subledger Accounting - Version 12.0.0 and laterOracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.
Symptoms
Undo Accounting Errors out with "XLA-95103: An internal error occurred." or "Journal entry cannot be reversed as its not transferred to General Ledger."
Undo Accounting ERROR can be as below :
Journal entry cannot be reversed as its not transferred to General Ledger.
"-: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla.plsql.xla_datafixes_pub.reverse_journal_entries. Journal entry cannot be reversed as its".
"-: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla.plsql.xla_datafixes_pub.reverse_journal_entries. Journal entry cannot be reversed as its".
FND Debug Log shows:
l_Return_Status=U
"Undo_Accounting : Error in xla_DataFixes_Pub.Reverse_Journal_entries:FND"
Undo Accounting Unsuccessful for Invoice id event id
"Undo_Accounting : Error in xla_DataFixes_Pub.Reverse_Journal_entries:FND"
Undo Accounting Unsuccessful for Invoice id event id
RDBMS version 11g (11.1.07 Typically shows this error)
To confirm the issue execute both SQL statements given below. If SQL02 return rows and SQL01 does not, then issue is confirmed.
- -- SQL01
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |