R12 Generic Data Fix (GDF) Patch 17956201 - Delete Unprocessed Budgetary Accounting Events Hindering Payables Period Closure
(Doc ID 985228.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Payables - Version 12.0.0 to 12.2.4 [Release 12.0 to 12.2]Information in this document applies to any platform.
Symptoms
Some unprocessed Budgetary Accounting Events exists in the system which would prevent period closure. The affected invoices would be listed as Unaccounted.
Reversal Pairs in the Invoice Distributions, both of which have not been encumbered, but at least one of them has a BC event stamped.
Steps to reproduce:
- Log into Oracle applications using a Payables responsibility.
- Open the Invoice Workbench
(N) Invoices > Entry > Invoice - Create a Payables Invoice in Encumbrance Subledger Accounting Method.
- Validate and account the invoice
- The following <Note> occurs:
"Online accounting could not be created for this transaction. Please inform your system administrator that the Create Accounting program has encountered an internal error." - The invoice distributions which have been approved, is marked as Encumbered but the corresponding BC event has not been Accounted
- Next, discard an invoice line
- From a Payables responsibility navigate to "Accounting" -> "Control Payables Periods"
- Enter in a ledger name at the prompt
- Click "Find"
- Scroll to the period in question
- Change the Period Status to "Closed"
- Click "Save"
- If there are any transactions blocking the close you will receive a "APP-SQLAP-10304: You cannot close this period because exceptions exist."
- Click "OK"
- Click "Exceptions"
- Click "Review"
- A message giving the concurrent request_id submitted will appear
- Click "OK"
- Click on "View" -> "Requests"
- Click "Find"
- Select the row with the request_id given
- Click "View Output"
- The invoice is reported under "Unaccounted Invoices" section.
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 |
DATA-FIX |
CODE-FIX |
References |