EAR9.2: Document Field Is Not Being Populated By Payment Predictor When Using #DTL_TLR (Doc ID 2306384.1)

Last updated on NOVEMBER 25, 2019

Applies to:

Symptoms

Issue:
======================
Document field is not being populated by Payment Predictor when using #DTL_TLR

Steps:
======================
(Setup)
1. Setup Receivables Option ? Predictor Detail Options
2. Setup Receivables Option ? Payment Options: Payment Predictor Method: STANDARD
3. Create new Predictor Methods - STANDARD
4. Create new Predictor Methods - STANDARDMF with having #DTL_TLR
5. Setup Customer Information ? Bill To Options tab: Set STANDARDMF into the default Predictor Method for Customer USA02.

(Step)
1. Create a pending item and post it.
2. Create a deposit.
3. Run Payment Predictor.
4. Checking related tables after running Payment Predictor. (Please see the file Tables1 which contains records for related tables.)
5. Value (Item ID) was not populated to the DOCUMENT field in the PENDING_ITEM table.
6. Run ARUPDATE.
7. Checking related tables after running ARUPDATE. (Please see the file Tables2 which contains records for related tables.)
8. Value (Item ID) was not populated to the DOCUMENT field in the ITEM table.

Please also see replication step.

Actual Behavior:
======================
Document field is not being populated by Payment Predictor when using #DTL_TLR

Expected Behavior:
======================
Document field should be populated by Payment Predictor when using #DTL_TLR

Business Impacts:
======================
Due to this issue, users cannot retain values in the Document ID field.

Changes

Cause

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