You are here:
Decomposition use cases
These use cases highlight how decomposition operates in different situations. For these use cases, let's assume that the orders are in progress, with the downstream order item having the scope of Account.
For more information about scope, see Setting the Product Scope
Figure 1 shows the catalog. The Broadband product has several attributes (Modem Delivery, Modem vendor, and so on), two of which have conditions. The Video Streaming product also has an attribute with a condition.
Figure 2 shows the original sales order. All the scenarios below begin with this order, except for "Change to a child order item," which uses Figure 8 as its original order.
The customer has ordered Broadband and Video Streaming, but has not ordered the mobile router. Because the scope is set to Account, these two order items result in a single, combined fulfillment request. The serial number is set by an integration adapter somewhere during the fulfillment process.
Simple amend
In this scenario, a supplemental order is raised to add a mobile router. This supplemental order has the following effects:
A new downstream fulfillment request is added to account for the delivery of the mobile router. This fulfillment request has a supplemental action of Create.
The fulfillment request Delivery specification gets a supplemental action of Amend because it's the parent of the new fulfillment request.
The Broadband order item has changed, so gets a supplemental action of Amend.
Other attributes are unaffected.
Simple amend with a failed condition
In the catalog, there's a condition that Mobile Delivery must equal Y. The original order met that requirement, but the supplemental order in this scenario changes it to N. This means that the condition is no longer met, so the change cannot be accepted.
As noted before, the scope is set so that the downstream technical order item combines the two orders.
As in the simple amend, a new downstream fulfillment request is added to account for the delivery of the mobile router. This fulfillment request has a supplemental action of Create.
The Broadband order item has a change, so it's marked as Amend.
Modem Delivery no longer meets the condition Y, so the Broadband order item can no longer be accepted. The link to Delivery specification becomes inactive, and all its attributes remain as they were in the original order.
NoteInactive decomposition relationships are viewable in the decomposition plan view when you click the chain icon. As usual, active relationships are highlighted in blue. Inactive ones are highlighted in red.
The Video Streaming order item is unchanged. So Delivery specification now has a canceled state (from the failed Broadband order item), but also an unchanged state (from the Video Streaming order item). These conditions resolve to an Amend state for Delivery specification.
Simple amend with a full cancel due to conditions
In this scenario, both conditions leading to Delivery specification fail.
The same rules apply for the first order item as in the Simple Amend with a failed condition.
The second order item (Video Streaming), now has a new value for STB Delivery that doesn't meet the condition set for it. So Video Streaming, like Broadband, breaks its relationship with Delivery specification.
Because both order items are canceled, the technical order item is marked as Cancel. None of the values from Broadband or Video Streaming are propagated, and they all remain as they were in the original order.
Cancellation
In this scenario the Broadband order item is canceled. In other words, it's a partial cancellation.
Broadband has a supplemental action of Cancel.
Because Broadband is canceled, none of its attributes are propagated to Delivery specification, and they remain as they were in the original order.
Video Streaming is not changed, so its fulfillment request would normally be set to no change. But the scope in this case combines both order items into one technical order item: Credit Check. So the Credit Check order item now has a canceled state (from the canceled Broadband order item), but also an unchanged state (from the Video Streaming order item). These conditions resolve to an Amend state for the Credit Check item.
Delivery specification has Cancel from Broadband and No Change from Video Streaming. These two states together mean that Delivery specification is being changed. So it gets the supplemental action of Amend.
In this scenario, both Broadband and Visual Streaming are canceled. It's a full cancellation.
As a result of Broadband having a SupplementalAction of Cancel, Delivery specification is also set to Cancel. The values from Broadband are not propagated, and they remain as they were in the original order.
Video Streaming also has a SupplementalAction of Cancel, so it also passes the Cancel supplemental action to Delivery specification. And as with Broadband, the values from Video Streaming are not propagated, and remain as they were in the original order.
Since Delivery Specification is set to Cancel from both its upstream order items, then of course it is set to Cancel.
There's another type of cancellation: Assume a scenario in which a supplemental order has been submitted that cancels one order item (let's say, iPhone), while other order items continue. Then, a second supplemental order is submitted, changing a second order item in the same order (let's say Galaxy).
In the second supplemental order, the fulfillment operator will see both the Amend SupplementalAction for the Galaxy, and the Cancel SupplentalAction for the iPhone. This does not mean that the Cancel action is happening twice. Rather, it's been carried forward from the previous supplemental order, and can be safely ignored.
Change to a child order item
In this example, we'll start with a new original order (Fig. 8) and then amend it by canceling a child order item.
A supplemental order is submitted that requires canceling the child order item Visual Voicemail.
Both Visual Voicemail Activation and Visual Voicemail Product Billing are canceled so that OM can roll back these fulfillment requests.
Because Visual Voicemail Product Billing is changed, its parent (Phone Service Product Billing) is marked as Amend. This logic works when any child is marked as Cancel, Create, or Amend.
