Recourse Related Fields In Accounts Table Not Available not available in conversion process to provide values from legacy (Doc ID 3055695.1)

Last updated on OCTOBER 26, 2024

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
Recourse Related Fields In Accounts Table Not Available not available in conversion process to provide values from legacy

Accounts table in servicing has several recourse related fields as well as their current (_CUR) counterparts such as:
ACC_RECOURSE_IND ,ACC_RECOURSE_MAX_PER ,ACC_RECOURSE_TYPE_CD ,ACC_RECOURSE_REASON_CD ,ACC_RECOURSE_AMT
,ACC_RECOURSE_IND_CUR ,ACC_RECOURSE_TYPE_CD_CUR ,ACC_RECOURSE_REASON_CD_CUR ,ACC_RECOURSE_MAX_PER_CUR ,ACC_RECOURSE_AMT_CUR

The normal fields such as ACC_RECOURSE_MAX_PER come from contract setup, while the current fields such as ACC_RECOURSE_MAX_PER_CUR come from recourse maintainence transactions and represent the current values of those fields.

However, from migration route, we do not find any of these CURRENT fields available in the accounts migration file, to allow these values to proceed to servicing via migration process. Even in the contract file, only APP_RECOURSE_TYPE_CD is available. Hence all of these fields in accounts table after being migrated come from existing contract setup and the normal and CURRENT fields are identical.

Ideally, customer expects following fields should be available in contracts file, api_con_111.dat:
APP_RECOURSE_IND,APP_RECOURSE_MAX_PER,APP_RECOURSE_TYPE_CD ,APP_RECOURSE_REASON_CD ,APP_RECOURSE_AMT

and the corresponding CURRENT fields in accounts file, api_acc_111.dat:
ACC_RECOURSE_IND_CUR,ACC_RECOURSE_TYPE_CD_CUR ,ACC_RECOURSE_REASON_CD_CUR ,ACC_RECOURSE_MAX_PER_CUR ,ACC_RECOURSE_AMT_CUR

If these fields are populated, then they should be allowed to proceed to servicing accounts table, and if not available, the existing process of deriving these fields from contract setup can be followed as usual.

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.