Existing T2Ts

Existing T2Ts are modified to make a join between stage table and SETUP_MASTER table on <stage table>.load_run_id = <EPM_LOAD_RUN_ID value> and do the data load to instrument or processing table. Even though changes are made to existing T2Ts, seeded entries in the SETUP_MASTER table will make it work without any issues if the Load Run ID column value in the staging table is the default value of zero and not null. If the Load Run ID value in the staging table is any other value other than zero, then customers have to update the 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, it has to be used to insert a complete snapshot of the data for a given MIS date. Re-execution for the given MIS date needs deletion of data from processing tables and execution of existing T2Ts. The merging of data is not supported with existing T2T.

Concerning the OFS HM application, the seeded masterbatch is provided to execute the following T2Ts in a single execution.

If any T2T is missing in the seeded masterbatch, then the user has to execute manually that T2T batch.

This seeded masterbatch contains the list of T2Ts that are common between OFS HM.

Note:

This applies to OFS HM. Even though T2Ts are part of the seeded masterbatch, they will be available as individual T2T batches. You can execute the individual T2T batches alone.