My Oracle Support Banner

Cannot Complete PPR Due To Rejected Documents - ORA-01403 and 'Document payable was failed because its parent payment was failed' (Doc ID 1582983.1)

Last updated on SEPTEMBER 14, 2018

Applies to:

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

Symptoms

Cannot Complete PPR due to Rejected Documents.
When creating a Payment Batch "PPR", several documents have been rejected.

Online FND log show the following:

IBY_VALIDATIONSETS_PUB.checkProfileFormatCompat: Getting the data from Cache For Payee Id: 18075
IBY_VALIDATIONSETS_PUB.checkProfileFormatCompat: Format:  linked to payee 18075
IBY_VALIDATIONSETS_PUB.checkProfileFormatCompat: No format was found linked to payee 18075
IBY_VALIDATIONSETS_PUB.checkProfileFormatCompat: Format cd not available. Cannot validate. Returning success.
IBY_VALIDATIONSETS_PUB.checkProfileFormatCompat: EXIT
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Payment profile is compatible with payment format for document id: 646383
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Ext Bank Acct Id field is: 6601 for the assignments
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Ext Payee Id field is: 18075 for the assignments
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Bank Acct is not present at supplier site level
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: No Address OU level Payee Exists
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: No Address level Payee Exists
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: End Date field is:  for the assignments
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Supplier / External Bankaccount is attached is valid for document id: 646383
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Fetching the value from Cache Structure l_int_bank_accts_tbl PEN$OPERATING_UNIT$102$31-JUL-13$37002
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Internal bank acct is valid for document id: 646383
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: External payee id is valid for document id: 646383
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Getting Data from Cache For Profile Id: 229
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert to the cursor
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert doc_id is 646383
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert pmt_grp_num is 2
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert payee_id is 18075
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert pmt_method_cd is EFT
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert int_bank_acct_id is 37002
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert l_payment_format_cd is SYTPCP001
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert l_bepid is
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert l_transmit_protocol_cd is
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: Before doing a bulk insert l_country is
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: The data for the index already exists
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: After doing a bulk insert to the cursor
IBY_VALIDATIONSETS_PUB.applyDocumentValidationSets: The cursor return count is0
------------------------
No Reporting Code defined for Process result id for219261 : ORA-01403: No se ha encontrado ningْn dato
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfPmtsInModifiedStatus: SQLERRM: ORA-01403: no data found
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfPmtsInModifiedStatus: SQLERRM: ORA-01403: no data found
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfPmtsInModBankAccStatus: SQLERRM: ORA-01403: no data found  
------------------------
IBY_PAYINSTR_PUB.flagSeparateRemitAdvcPayments: SQLERRM: ORA-01403: no data found
IBY_PAYINSTR_PUB.flagSeparateRemitAdvcPayments: SQLERRM: ORA-01403: no data found
"Enter Build :: Concurrent Request ID::25220851
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request: ENTER
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request: Calling app id: 200
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request: Calling app pay req cd: MERCAD1 31.07 PEN
+-----------------------------------------------------------------------------------------------------+
|STEP 1: Insert Payment Service Request:: Timestamp:31-JUL-13 05.49.12.417074000 PM -05:00|
+-----------------------------------------------------------------------------------------------------+
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfDuplicate: ENTER
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfDuplicate: Calling app payment request MERCAD1 31.07 PEN is a duplicate for calling app 200. Previously generated payment request id: 188695
IBY_DISBURSE_SUBMIT_PUB_PKG.checkIfDuplicate: EXIT
Payment service request MERCAD1 31.07 PEN is a duplicate. Skipping insert of request


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submit PPR.
2. Rejected Scheduled Payments = xx (number of rejected payable documents)


The following select statement will show the validation failures, or use the Funds Disbursement Analyzer (Doc ID 1587455.1) which will show the same in the 'PPR Data Collection' section.

Select * from
(
SELECT *
FROM iby_transaction_errors
WHERE transaction_type in ('PAYMENT')
AND transaction_id IN (
    select distinct PAYMENT_ID from IBY_PAYMENTS_ALL where PAYMENT_PROCESS_REQUEST_NAME = :PPR_NAME )
UNION
SELECT *
FROM iby_transaction_errors
WHERE transaction_type in ('DOCUMENT_PAYABLE')
AND transaction_id IN (
     select distinct DOCUMENT_PAYABLE_ID from IBY_DOCS_PAYABLE_ALL
     where PAYMENT_SERVICE_REQUEST_ID in
          (SELECT payment_service_request_id
           FROM APPS.iby_pay_service_requests
           WHERE calling_app_id = 200
           AND call_app_pay_service_req_code = :PPR_NAME))
UNION
SELECT *
FROM iby_transaction_errors
WHERE transaction_type in ('PAYMENT_INSTRUCTION')
AND transaction_id IN (
       SELECT distinct payment_instruction_id
       FROM APPS.iby_payments_all
       WHERE payment_service_request_id in
           (SELECT payment_service_request_id
           FROM iby_pay_service_requests
           WHERE calling_app_id = 200
           AND call_app_pay_service_req_code = :PPR_NAME))
) xx_iby_transaction_errors
order by 2;

=============
The output is:
=============

TRANSACTION_TYPE = DOCUMENT_PAYABLE
ERROR_CODE = IBY_DOC_FAILED_BY_PARENT_PMT
ERROR_STATUS = ACTIVE
CALLING_APP_DOC_UNIQUE_REF1 = 88757
OVERRIDE_ALLOWED_ON_ERROR_FLAG = N
DO_NOT_APPLY_ERROR_FLAG = N
CALLING_APP_ID = 200
PAY_PROC_TRXN_TYPE_CODE = PAYABLES_DOC
ERROR_TYPE = VALIDATION
ERROR_MESSAGE =   

Document payable was failed because its parent payment was failed

VALIDATION_SET_CODE = CORE_PAYMENT_VALIDATION

Changes

 Applied the Patches 11699958 and 15867522.

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!


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