TDM LU Implementation — Hierarchy Support
The TDM task can process Business Entities (BEs) and/or tables. A Business Entity (BE) represents the main entity of the data selected for provisioning in TDM. Each BE can include multiple LUs, organized in either a flat or a hierarchical structure. For example, a Customer BE may include CRM, Billing, Ordering and Usage LUs.
Parent LU — Implementation Guidelines
BEs are defined in the TDM self-service application. In addition, the following guidelines must be implemented to support parent-child LU hierarchy:
- Populate the ChildLink MTable object. Note that a parent LU can have multiple child LUs. For each child LU, add a separate record that includes the SQL queries to select the source and target child IDs.
TDM Relationship Tables
Starting from TDM V9.3, hierarchy is supported through the TASK_EXECUTION_ENTITIES table in the TDM database. During task execution, this table is populated with the parent LU name, parent entity, root LU name, and root entity for each executed entity.
TDM LU Implementation — Hierarchy Support
The TDM task can process Business Entities (BEs) and/or tables. A Business Entity (BE) represents the main entity of the data selected for provisioning in TDM. Each BE can include multiple LUs, organized in either a flat or a hierarchical structure. For example, a Customer BE may include CRM, Billing, Ordering and Usage LUs.
Parent LU — Implementation Guidelines
BEs are defined in the TDM self-service application. In addition, the following guidelines must be implemented to support parent-child LU hierarchy:
- Populate the ChildLink MTable object. Note that a parent LU can have multiple child LUs. For each child LU, add a separate record that includes the SQL queries to select the source and target child IDs.
TDM Relationship Tables
Starting from TDM V9.3, hierarchy is supported through the TASK_EXECUTION_ENTITIES table in the TDM database. During task execution, this table is populated with the parent LU name, parent entity, root LU name, and root entity for each executed entity.
