R12:AP: Generic Data Fix (GDF) Patch to Correct the Data Corruption for Posted Flag having Value as 'S'
(Doc ID 1088872.1)
Last updated on JUNE 21, 2023
Applies to:Oracle Payables - Version 12.0.0 to 12.2 [Release 12.0 to 12.2]
Information in this document applies to any platform.
There are Payables transactions (invoices and payments) with incorrect status of Posted_flag as 'S'.
The transactions are stuck in processing status and they are shown as Unprocessed.
This value, 'S', should be there only when there is an accounting operation going on the record and a concurrent program is in progress.
Once the accounting of the record goes through successfully in which case the event status code in XLA_EVENTS table is 'P', the value of this flag should be 'Y'. Else for all other conditions, it should be 'N'.
Steps to reproduce:
- Log into Oracle applications using a Payables responsibility.
- (N) Payables Responsibility -> Submit Create Accounting program. If the Create Accounting program completes in error and the issue is encountered then Posted Flag of transactions are stuck in status: 'S'.
- This will cause the transactions to be shown in incorrect accounting status: Unprocessed.
"ORA-1403: no data found occurred in AP_Accounting_Pay_Pkg.Do_Pay_Accounting<- AP_SLA_PROCESSING_PKG.EXTRACT"
Note: Currently, the issues is not reproducible on will. Patches 7351478 and 9756762 are available in code lines of R12.1.x and R12.2.x
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