32  Load Run IDs for T2Ts

You can load the data into OFSAA using the OFSAA T2Ts.

OFSAA Data Model includes Load Run Identifier as part of the primary key for a set of staging tables. This enables data to be stored for multiple Load Runs for any date. OFSAA Data Model also has a table to maintain master information about Load Run and can be used for identifying or filtering Load Run during Run execution within OFSAA.

Before loading data into the staging table, generate a Load Run Identifier to stamp the records from the source. These records can be a complete snapshot or can be partial or Incremental Data, too. This Load Run Identifier can be generated by calling the function in the OFSAA Atomic Schema named fn_register_load_run. The function expects some input parameters and returns a unique Load Run Identifier to the calling program.

The SETUP_MASTER in OFS LLFP is seeded with key/value pair of (EPM_LOAD_RUN_ID,0) value.

The following process flow diagram illustrates the Load Run ID for the T2T process.

Figure 124: Load Run ID for T2T Process Flow

Title: Description of Load Run ID for T2T Process Flow follows - Description: This diagram illustrates the process flow of Load Run ID process for T2Ts.

Existing T2Ts

Existing T2Ts are modified to join the stage table and SETUP_ MASTER table on <stage table>.load_run_id = < BASE_LOAD_RUN_ID value>/ <EPM_LOAD_RUN_ID value> and perform the data load on the instrument and OFS LLFP processing tables. Even though changes are made to the existing T2Ts, seeded entries in the SETUP_ MASTER table it works if the Load Run ID column value in the stage table contains the default value of 0. If the Load Run ID value in the stage table is a value other than 0, then update the BASE_LOAD_RUN_ID/ EPM_LOAD_RUN_ID parameter value in the SETUP_MASTER table with the used Load Run ID value for the load.

While using modified existing T2Ts, insert a complete snapshot of the data for a given MIS date. Merging of data is not supported with existing T2Ts. Re-execution for a given MIS date needs deletion of data from instrument tables and execution of existing T2Ts. Deletion of data is not required for OFS LLFP processing tables. Seeded master batches are provided to execute the T2Ts in a single execution.