How Mapping Works When a Commercial Product Relies on another

When a commercial product relies on another, you can map attribute and field values from both products to the technical product during decomposition.

For example, let's say you have a Roaming commercial product that relies on a Voice commercial product. You can map it so that when the Roaming product decomposes, it passes on attribute values from the Voice product as well as itself.

The same relationship works for setting conditions for decomposition. Industries Order Management honors Relies On relationships when validating conditions.

Let's look at some examples of how this works. In this first example, two commercial products (Voice Product and Roaming) decompose to the Billing Item technical product.

In the catalog, Roaming is set to rely on Voice Product. When Roaming decomposes to Billing item, it can map its own attribute value (CostCode2 = 222) and also attribute values from Voice Product (CostCode1 = 111). It doesn't matter whether Voice product itself decomposes to Billing Item. Its attribute value is mapped, because Roaming relies on it.

In this slightly more complicated example, there are three commercial products. Only one product (Roaming) decomposes to TechProd01. But because Roaming relies on Voice, and Voice relies on Comms Package, you can map attribute or field values from any or all of those products. Industries OM checks all the Relies On relationships and honor the mapping for all of them.