AP_IBY_PMT_MISMATCH Caused by IBY Removal of Selected Invoices

(Doc ID 1308095.1)

Last updated on SEPTEMBER 23, 2016

Applies to:

Oracle Payables - Version: 12.0.1 to 12.1.3 - Release: 12.0 to 12.1
Information in this document applies to any platform.


The following data pattern issues are being occured when the error with ap_iby_pmt_mismatch error is caused.

Rows in iby_docs_payable all: 34 (all have a document status of PAYMENT_CREATED and a related payment with status of SUBMITTED FOR PRINTING)
Rows in ap_selected_invoices_all: 29
The payment schedules related to the 5 missing selected invoices have a null
checkrun_id (so they can be selected in a new PPR).

Originally 34 invoices were selected for payment in AP. The iby build process started and populated the 34 rows in iby_docs_payable. At some point after this iby code called
AP_PMT_CALLOUT_PKG.documents_payable_rejected which removed the 5 rows from
ap_selected_invoices_all and nulled out the checkrun ids on the payment schedules. However the iby code did not remove or change the status on the iby docs and payments. When the  ap_pmt_callout_pkg attemts to complete the payments it finds that there are more iby docs than selected invoices and raises a mismatch error.


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