TDM Parameters Handling
The TDM enables the user to select entities based on predefined parameters when creating a load task or a reserve task. The list of available parameters is displayed on the task's BE (Business Entity). A BE can have flat or hierarchical structure and each LU can have its own parameters list and its own LU PARAMS table.
The entities selection on a TDM task selects a subset of root entities, but the parameters for selection can be based on the child LU's parameters as well. Therefore, it is highly important to have the linkage between the root entity and the children entities when selecting entities based on parameters.
Clicking the 
in the [task window] invokes wsGetNumberOfMatchingEntities Fabric Web-Service (imported from the TDM Library) to for the number of root entities that match the selected parameters. The Web-Service generates a MATERIALIZED VIEW in the [TDM DB] on each combination of BE and source environment:
lu_relations_<BE name>_<Source Environment Name>
Each root entity ID is populated in one single record that contains all the related parameters and values of all the LUs. The select of matching entities runs on the MATERIALIZED VIEW.
This VIEW is refreshed by the checkMigrateAndUpdateTDMDB job refreshes the view to get the newly synched entities when updating extract tasks status to completed.
Example:
Customer BE has four LUs:
- Two root LUs: Customer and Collection.
- Customer LU has two children LUs:
- Billing
- Order
Even LU of the BE has its own LU_PARAMS table in the TDM DB.
Customer #65 has the following children IDs:
- Billing LU: #169, #170, #171, #172, and #173.
- Order LU: #279, #280, #281, #282, #283, #284, and #285.
Synching Customer ID #1 inserts the following record into CUSTOMER_PARAMS TDM DB table:
Synching Collection ID #1 inserts the following records into COLLECTION_PARAMS TDM DB table:
| entity_id | source_environment | COLLECTION.COLLECTION_STATUS |
| 65 | SRC | {"5","4","3","1","2"} |
Synching Billing IDs #169, #170, #171, #172, and #173 inserts the following records into BILLING_PARAMS TDM DB table:
Synching Order IDs #279, #280, #281, #282, and #283. #284, and #285 inserts the following records into ORDER_PARAMS TDM DB table:
The tester selects entities based on the following parameters:
- NO_OF_OPEN_CASES > 0 AND VIP_STATUS = "Gold" AND ORDER_TYPE = "New"
wsGetNumberOfMatchingEntities Fabric Web-Service generates a new MATERIALIZED VIEW in the TDM DB named lu_relations_Customer_SRC:
TDM Parameters Handling
The TDM enables the user to select entities based on predefined parameters when creating a load task or a reserve task. The list of available parameters is displayed on the task's BE (Business Entity). A BE can have flat or hierarchical structure and each LU can have its own parameters list and its own LU PARAMS table.
The entities selection on a TDM task selects a subset of root entities, but the parameters for selection can be based on the child LU's parameters as well. Therefore, it is highly important to have the linkage between the root entity and the children entities when selecting entities based on parameters.
Clicking the in the [task window] invokes wsGetNumberOfMatchingEntities Fabric Web-Service (imported from the TDM Library) to for the number of root entities that match the selected parameters. The Web-Service generates a MATERIALIZED VIEW in the [TDM DB] on each combination of BE and source environment:
lu_relations_<BE name>_<Source Environment Name>
Each root entity ID is populated in one single record that contains all the related parameters and values of all the LUs. The select of matching entities runs on the MATERIALIZED VIEW.
This VIEW is refreshed by the checkMigrateAndUpdateTDMDB job refreshes the view to get the newly synched entities when updating extract tasks status to completed.
Example:
Customer BE has four LUs:
- Two root LUs: Customer and Collection.
- Customer LU has two children LUs:
- Billing
- Order
Even LU of the BE has its own LU_PARAMS table in the TDM DB.
Customer #65 has the following children IDs:
- Billing LU: #169, #170, #171, #172, and #173.
- Order LU: #279, #280, #281, #282, #283, #284, and #285.
Synching Customer ID #1 inserts the following record into CUSTOMER_PARAMS TDM DB table:
Synching Collection ID #1 inserts the following records into COLLECTION_PARAMS TDM DB table:
| entity_id | source_environment | COLLECTION.COLLECTION_STATUS |
| 65 | SRC | {"5","4","3","1","2"} |
Synching Billing IDs #169, #170, #171, #172, and #173 inserts the following records into BILLING_PARAMS TDM DB table:
Synching Order IDs #279, #280, #281, #282, and #283. #284, and #285 inserts the following records into ORDER_PARAMS TDM DB table:
The tester selects entities based on the following parameters:
- NO_OF_OPEN_CASES > 0 AND VIP_STATUS = "Gold" AND ORDER_TYPE = "New"
wsGetNumberOfMatchingEntities Fabric Web-Service generates a new MATERIALIZED VIEW in the TDM DB named lu_relations_Customer_SRC:
