K.5 <INFODOM>_T2T_MANAGEMENT_LEDGER_MULTI_SOURCE

This seeded batch along with the underlying DTs and T2T enables tracking of data from the Staging table to the Management ledger table using identity codes. For each distinct value of "Data Origin" in the Staging table, a new Identity code is used to populate the Management ledger and FSI_DATA_IDENTITY tables. The value of V_DATA_ORIGIN in the Staging table is mapped to the FSI_DATA_IDENTITY.description column.

The seeded batch named <INFODOM>_T2T_MANAGEMENT_LEDGER_MULTI_SOURCE will have the following three tasks in the sequence:

  1. A DT named FN_MGMT_LED_LOAD_TEMP_TABLE, which will populate the T2T_FSI_D_MANAGEMENT_LEDGER table with unique identity_code values for each of the distinct v_data_origin values in the STG_GL_DATA table. It accepts two parameters - Target Table Name and Staging Table Name.
  2. T2T named T2T_MANAGEMENT_LEDGER_MULTI_SOURCE, which will use the identity codes from the table T2T_FSI_D_MANAGEMENT_LEDGER for loading data from STG_GL_DATA to FSI_D_MANAGEMENT_LEDGER.
  3. Another DT named FN_MGMT_LED_LOAD_DATA_IDENTITY, which will populate the FSI_DATA_IDENTITY table with the information about the management ledger load. It maps the V_DATA_ORIGIN column in the STG_GL_DATA table to the DESCRIPTION column in the FSI_DATA_IDENTITY table. It will also delete the records from the T2T_FSI_D_MANAGEMENT_LEDGER table.

Note:

  1. The results of the DT execution is written to the FSI_MESSAGE_LOG table.
  2. The OOB T2T uses STG_GL_DATA as the staging table. The T2T has is customized to use any other staging table as the source.
  3. If a custom Staging table is used instead of STG_GL_DATA, the table needs to have the columns FIC_MIS_DATE and V_DATA_ORIGIN.