You are here:
One-to-Many Decomposition Relationship
There are different types of decompositions relationships, including the one-to-many type. A common use case for a one-to-many order decomposition is an offer containing a product that affects multiple fulfillment systems.
When a product must be sent to more than one system, you need to decompose the service into multiple technical products that are specific to those systems. For example, a TV Service Offer contains a TV Service product that must be activated through a provisioning system. Additionally, the charges defined in the service must be sent to a billing system. Depending on customer processes, other systems may also be affected.
The TV Service information must be sent to more than one system, so you need to decompose the service into multiple technical products that are specific to those systems:
- Create a TV Service Activation technical specification according to the needs of the provisioning system.
- Define a decomposition relationship between TV Service and TV Service Activation and map the information accordingly.
- Create a TV Service Billing technical specification according to the needs of the billing system.
- Define a decomposition relationship between TV Service and TV Service Billing and map the information accordingly.
