R12: AP/IBY: Payment Instruction (PI) Is Stuck In "Submitted For Printing" Status when Record Print Status hits Payment Mismatch Error
Last updated on AUGUST 25, 2017
Applies to:Oracle Payables - Version 12.0.0 and later
Oracle Payments - Version 12.0.0 and later
Information in this document applies to any platform.
When processing a check batch, the PPR completes successfully, and then the Payment Instruction successfully formats the checks. However, the batch becomes stuck in Payment Instruction status "Submitted for Printing" when the Record Print Status step fails to record the checks due to a Payment Mismatch Error.
The following is an example of related information that appears in the Record Print Status concurrent request log file for such a case.
Please contact the System Administrator and report the payment(s) listed below.You can process the remaining payments by initiating stop and confirming stop on the payment reference number(s) listed below.
The following document(s) payable exists in iby_docs_payable_all but not in ap_invoice_payments_all or ap_selected_invoices_all:
Payment Reference Number: xxxxx
In such cases, there does not appear to be anything the user can do to resolve the problem, since the payments in the Payment Instruction cannot be recorded, and the product is specifically designed to not allow the user to directly Terminate a check batch for which the Payment Instruction has reached Status: Submitted for Printing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms