BAT Stuck In Staus "Settlement In Process", Build Payments Failed and PPR Not Created In AP due to Error in Build Payment Program "BUILD_ERROR" (Doc ID 1965636.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

We have created BAT and and the status of the same is in Settlement in Process and when we went to Funds disbursement Process manager responsibility we are not able to see the Payment process request created against BAT though the    payment_service_request_status in the iby_pay_service_requests table is BUILD_ERROR". 

File descroption : Build payment log file

Findings
-----------
BUILD PROGRAM ERROR - CANNOT INSERT DOCUMENTS FOR PAYMENT SERVICE REQUEST
Build program error: Unable to insert documents payable of the provided payment service request into database.

File descroption : FND debug log
Findings
-----------
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext: Given payee context: payee party id 327605, party site id 349332, supplier site id , org id 24278, org type LEGAL_ENTITY, pmt_function CASH_PAYMENT
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:Fatal: Exception when attempting to perform exact match for given payee context.6
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:Fatal: Exception when attempting to perform exact match for given payee context.6
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:SQL code: -14226
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:SQL code: -14226
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:SQL err msg: ORA-01422: exact fetch returns more than requested number of rows6
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:SQL err msg: ORA-01422: exact fetch returns more than requested number of rows6
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.derivePayeeIdFromContext:EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:Exception occured when attempting to insert documents for calling app id 260, calling app payment service request id 7168
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:Exception occured when attempting to insert documents for calling app id 260, calling app payment service request id 7168
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:SQLCODE: -1422
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:SQLCODE: -1422
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:SQLERRM: ORA-01422: exact fetch returns more than requested number of rows
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:SQLERRM: ORA-01422: exact fetch returns more than requested number of rows
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.insert_payreq_documents:EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Could not insert documents payable for payment service request. Calling app id 260, calling app payment service request cd 7168
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Could not insert documents payable for payment service request. Calling app id 260, calling app payment service request cd 7168
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Payment service request cannot be processed further. Exiting build program.
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request:Payment service request cannot be processed further. Exiting build program.
[DEBUG]  [FND_MAX_JDBC_CONNECTIONS]:[500]
FND
Build program error: Unable to insert documents payable of the provided payment service request into database.
+---------------------------------------------------------------------------+
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:ENTER
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:ENTER
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:Input params - object id: 16798, object type: PAYMENT_REQUEST
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:Input params - object id: 16798, object type: PAYMENT_REQUEST
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:Returning success response ..
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:Returning success response ..
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:EXIT
IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity:EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request: Unlocked Payment service Request
IBY_DISBURSE_SUBMIT_PUB_PKG.update_payreq_status: Enter
IBY_DISBURSE_SUBMIT_PUB_PKG.update_payreq_status: EXIT

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