Mapping Temporary Information to a Technical Product

You can use the Order Management Decomposition Relationship screen to map virtually any field or attribute from the source to the target.

In doing so, avoid mapping the action for use in orchestration conditions. This is not recommended because it might impact the Move, Add, Change, Delete (MACD) scenarios. Issues may appear after running a sequence of orders.

For example, a customer may require a certain outcome when the action is “Disconnect”. One solution is to map the action to an RFS attribute and then use the value during orchestration. The new fulfillment process may proceed without error at first. However, the new MACD action is “Add”, so this value is assetized in the technical inventory item. The next MACD order that does not change the order item would have the value of “NoChange”, which is different from the already assetized “Add”. As such, the Order Management decomposition process sets the action to “Modify” for the corresponding fulfillment request, which is not the expected action.