My Oracle Support Banner

R12: AP: Unable to Close Payables Accounting Period Due to Unaccounted Payment Linked to Two Skipped Consecutive Check_ID (Doc ID 3038886.1)

Last updated on FEBRUARY 26, 2025

Applies to:

Oracle Payables - Version 12.2.10 and later
Information in this document applies to any platform.

Symptoms

Unable to close Payables (AP) accounting period.

Period Close Exception report list one PAYMENT CREATED accounting event under "Other Exceptions".

Unable to account payment; "Create Accounting" process finds no records to account.

Payment workbench shows the unaccounted payment with no invoices being paid

Attempting to view the payments of the invoice expected to be paid by the unaccounted payment, via the Invoice Workbench, raises the following error:

APP-SQLAP-10000: ORA-01403: no data found occurred in
APXINWKB->INV_SUM_FOLDER_ITEM_OVERFLOW ->
AP_ACCOUNTING_EVENTS_PKG.UPDATE_INVOICE_EVENTS_STATUS
with parameters (p_invoice_id = &invoice_id)
while performing the following operation:
&DEBUG_INFO 

 

Steps to reproduce:

  1. Log into Oracle Applications using a Payables responsibility
  2. Open the Invoice Workbench
  3. (N) Invoices > Entry > Invoices
  4. Query the Invoice expected to be paid by the unaccounted Payment
  5. Click on the [View Payments] tab
  6. Popup Error message described above.
      

 

And output of the "EBS Payables Period Close Analyzer Report" (CAANLZR), shows one unaccounted "PAYMENT CREATED" accounting event, linked to missing check record.  To better illustrate this, consider the following fictitious output of the CAANLZR:

Error Signatures

â–¼Unaccounted Transactions

LEDGER_ID SOURCE_ID_INT_1
(Check_ID)		 ENTITY_CODE EVENT_
STATUS_CODE		 PROCESS_
STATUS_CODE		 APPLICATION_ID EVENT_ID EVENT_TYPE_CODE EVENT_DATE TRANSACTION_NUMBER
2021 1999997 AP_PAYMENTS U U 200 799995 PAYMENT CREATED 2024-06-30 130

Error: Unaccounted Transactions
Findings and Recommendations:
Run the create accounting process to account these transactions and post to General Ledger
See Doc ID 1313324.1
Alternative - The period can still be closed by sweeping the unposted rows to the next period
SeeDoc ID 560378.1 for more information on the sweep process
If the transactions do not get accounted and no relevant fixes are listed in the Error section, please log a new service request for assistance.

A query from table AP_CHECKS_ALL show No records for check_ID 1999997.

 

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.