R12: AP/IBY: BUILD PROGRAM ERROR - CANNOT VALIDATE DOCUMENTS, ORA-00001: unique constraint (APPS.IBY_DOCS_PAYABLE_VAL_GT_U1) violated (Doc ID 2128143.1)

Last updated on APRIL 25, 2016

Applies to:

Oracle Payments - Version 12.0.0 and later
Oracle Payables - Version 12.0.0 and later
Oracle Human Resources - Version 12.0 and later
Information in this document applies to any platform.

Symptoms

The Build Payments concurrent program suddenly fails consistently in the Document Validation step while processing check batches.
The following messaging is seen in the failed Build Payments concurrent request log files.

ERROR
-----------------------
BUILD PROGRAM ERROR - CANNOT VALIDATE DOCUMENTS
Error Message:BUILD PROGRAM ERROR - CANNOT VALIDATE DOCUMENTS
.
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:|STEP 4: Document Validation
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:+----------------------------------------------------------------------------------------------------+
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Exception occured when validating documents. Document validation will be aborted and no document statuses will be committed for payment request 19046
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:SQLCODE: 1
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:SQLERRM: User-Defined Exception
Build program error: Exception occured when attempting to validate the documents payable of the provided payment service request.

The customer who reported the error condition was able to run several small check batches which each processing a small subset of the total collection of invoices that were waiting to be paid via check. Upon identifying the small grouping of selected invoices that would consistently trigger the Build Payments failure, the customer utilized the instructions from Note "How To Get The FND Debug Log For On-Line Processes And For Concurrent Requests" (Doc ID 1320736.1) to capture the debug log.  The additional messaging in the debug log file included

IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:|STEP 4: Document Validation

IBY_VALIDATIONSETS_PUB.initDocDataForPPR: IBY_VALIDATIONSETS_PUB.initDocDataForPPR:Enter initDocDataForPPR
IBY_VALIDATIONSETS_PUB.initDocDataForPPR: IBY_VALIDATIONSETS_PUB.initDocDataForPPR:Process Type is:STANDARD
Enter:TIMESTAMP:: iby.plsql.IBY_FD_EXTRACT_GEN_PVT.Get_FP_TaxRegistration:: 13-APR-16
Payer tax reg number not found in the cache for p_legal_entity_id : 101
Inserting tax reg number l_tax_registration : in cache for p_legal_entity_id : 101
Exit:TIMESTAMP:: iby.plsql.IBY_FD_EXTRACT_GEN_PVT.Get_FP_TaxRegistration:: 13-APR-16
Enter:TIMESTAMP:: iby.plsql.IBY_FD_EXTRACT_GEN_PVT.Get_FP_TaxRegistration:: 13-APR-16
Reg.No found in the cache for p_legal_entity_id : 101
Fetched tax reg number l_registration_number : in cache for p_legal_entity_id : 101
Exit:TIMESTAMP:: iby.plsql.IBY_FD_EXTRACT_GEN_PVT.Get_FP_TaxRegistration:: 13-APR-16
IBY_VALIDATIONSETS_PUB.initDocDataForPPR: IBY_VALIDATIONSETS_PUB.initDocDataForPPR:Exit initDocDataForPPR
IBY_VALIDATIONSETS_PUB.initDocDataForPPR: IBY_VALIDATIONSETS_PUB.initDocDataForPPR:SQL code: -1
IBY_VALIDATIONSETS_PUB.initDocDataForPPR: IBY_VALIDATIONSETS_PUB.initDocDataForPPR:SQL err msg: ORA-00001: unique constraint (APPS.IBY_DOCS_PAYABLE_VAL_GT_U1) violated
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets:ORA-00001: unique constraint (APPS.IBY_DOCS_PAYABLE_VAL_GT_U1) violated
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Exception occured when validating documents. Document validation will be aborted and no document statuses will be committed for payment request 19109
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:SQLCODE: 1
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:SQLERRM: User-Defined Exception
Build program error: Exception occured when attempting to validate the documents payable of the provided payment service request.

The customer also utilized the instructions from Note :R12.0+: Payables Payment Batch Data Gathering (IBY Schema)" (Doc ID 759037.1) to capture a dump of setup table data and transaction table data for the small check batch in question.

Upon isolating a specific employee supplier whose Expense Report appeared to be triggering the error condition, the customer generated the Employee Diagnostic, using Note "R12 Supplier Details Diagnostics Test" (Doc ID 1362792.1).  The Supplier Diagnostic output revealed 3 rows from PER_ADDRESSES, of which two rows appear to be duplicates outside of having distinct values in column ADDRESS_ID.



Cause

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