Trigger Date Extraction In Delinquency Process (C1-DLN-PROC) (Doc ID 3049611.1)

Last updated on SEPTEMBER 24, 2024

Applies to:

Symptoms

On RMB v6.1.0.0.0, Issue with Trigger Date Extraction in Delinquency Process (C1-DLN-PROC).

We configured Delinquency Process(C1-DLN-PROC) for GDE and took the incremental extract using F1-GEEXO batch.
Now discovered an incident where the trigger date is not being extracted correctly.
Although the trigger dates are visible in the ORMB UI, they appear as null in the extracted JSON.

Note that we ran the C1-ACDLQ / C1-DPEVL & CM-DTRDT on the 7/8. So for all new DP's that got created on 7/8, CM-DTRDT, stamped the first events with trigger dates of 8/6/2024 instead of 7/8/2024.
Per review with Business, the ask was to correct these trigger dates for all the newly created DP's to be 7/8/2024 and reset the subsequent event dates as well to match the 30/60/90 days.
To do this, we had to blank out the trigger dates and set the status of DPs back to 'PEVL'.
A backend update was performed to reflect this info.

Then we reran DPEVL and DTRDT with a batch business date of 7/2/2024 (i.e. less than the trigger date of 7/8/2024).
This reset the Trigger dates to the desired 07-08-2024 for the first events and the subsequent events as well based on the 30/60/90 logic.
The GDE Incremental data extract jobs were run after the completion of CM-DTRDT job on 7/9/2024 where the updated Trigger dates did not get extracted in the JSON files.

STEPS
----------
1. Create new Data Extract Request Type - DEXT_DEL with all required information.
2. Run the C1-DTEX batch by providing the Data Extract Code.
3. Validate Delinquency Process information in Extracted file in Full and Incremental mode

Cause

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