A Business Entity (BE) represents the main entity of the selected data to be provisioned by TDM. Business Entities can have multiple LUs with a flat or a hierarchical structure. For example, a Customer Business Entity can have Customer, Billing, Ordering and Usage LUs.
Breaking down the BE into several LUs enables maximum flexibility and it avoids duplicate development. The hierarchical structure of parent-child LUs enables creating LUs based on the natural root entity of the related data sources instead of forcefully setting unified root entities on all LUs related to a given BE.
Example
Customer LU root entity = Customer ID.
Ordering LU root entity = Order ID.
Network element LU root entity = Element ID.
Device LU root entity = Device ID.
Ordering, Network and Device LUs are attached to two BEs:
The following BEs are defined in the TDM:
You can request to load a list of selected Customer IDs, whereby the TDM task also copies the related ordering, network elements and device data of the selected customers. Alternatively, you can request to load a list of selected Order IDs whereby the TDM task also loads the related network elements and device data of the selected orders.
A parent-child hierarchy of LUs can also be defined under a BE. The relationship between the parent and child LUs is one to many. Each parent LUI can have many child LUIs.
If an LU in a BE has no parent LU, it is named Root LU whereby its root entity is equal to the root entity of the BE. A BE must have at least one Root LU.
Example of Customer #1 Hierarchy
When creating a TDM task to load Customer 1 from the PROD environment, the TDM task must also load the customer's related billing accounts and orders together with the related network elements and devices of the related orders.
The following LUIs are extracted from the source and created in Fabric for Customer 1:
A TDM BE may include several root LUs with the same list of entities. For example, if the entity ID of both the Customer and Billing LUs is Customer ID, then the BE hierarchy may be:
A TDM task can include a BE with a hierarchical structure of several LUs. When processing the TDM task, all related LUs from parent and child LUs must also be processed:
Execute the Root LUs on all task entities.
After the parent LUs have been processed, execute the child LUs of the Root LUs on all entities, as follows:
Note that if execution of the parent LU fails, the child LU is not processed and is marked as failed.
Example:
Create a TDM task to load Customers 1, 2 and 3, their orders and related network elements.
Customers' related entities:
Customer 1:
Customer 2 :
Customer 3 :
Step 1:
Step 2:
Step 3:
A Business Entity (BE) represents the main entity of the selected data to be provisioned by TDM. Business Entities can have multiple LUs with a flat or a hierarchical structure. For example, a Customer Business Entity can have Customer, Billing, Ordering and Usage LUs.
Breaking down the BE into several LUs enables maximum flexibility and it avoids duplicate development. The hierarchical structure of parent-child LUs enables creating LUs based on the natural root entity of the related data sources instead of forcefully setting unified root entities on all LUs related to a given BE.
Example
Customer LU root entity = Customer ID.
Ordering LU root entity = Order ID.
Network element LU root entity = Element ID.
Device LU root entity = Device ID.
Ordering, Network and Device LUs are attached to two BEs:
The following BEs are defined in the TDM:
You can request to load a list of selected Customer IDs, whereby the TDM task also copies the related ordering, network elements and device data of the selected customers. Alternatively, you can request to load a list of selected Order IDs whereby the TDM task also loads the related network elements and device data of the selected orders.
A parent-child hierarchy of LUs can also be defined under a BE. The relationship between the parent and child LUs is one to many. Each parent LUI can have many child LUIs.
If an LU in a BE has no parent LU, it is named Root LU whereby its root entity is equal to the root entity of the BE. A BE must have at least one Root LU.
Example of Customer #1 Hierarchy
When creating a TDM task to load Customer 1 from the PROD environment, the TDM task must also load the customer's related billing accounts and orders together with the related network elements and devices of the related orders.
The following LUIs are extracted from the source and created in Fabric for Customer 1:
A TDM BE may include several root LUs with the same list of entities. For example, if the entity ID of both the Customer and Billing LUs is Customer ID, then the BE hierarchy may be:
A TDM task can include a BE with a hierarchical structure of several LUs. When processing the TDM task, all related LUs from parent and child LUs must also be processed:
Execute the Root LUs on all task entities.
After the parent LUs have been processed, execute the child LUs of the Root LUs on all entities, as follows:
Note that if execution of the parent LU fails, the child LU is not processed and is marked as failed.
Example:
Create a TDM task to load Customers 1, 2 and 3, their orders and related network elements.
Customers' related entities:
Customer 1:
Customer 2 :
Customer 3 :
Step 1:
Step 2:
Step 3: