You are here:
Relies On Scope
Setting the scope to Relies On results in a single technical product for all commercial items that rely on each other.
The Relies On scope allows you to make bundles containing commercial products that aren't in the same parent-child hierarchy.
Consider that you have two commercial products that don't have a parent-child relationship, or even exist in the same parent-child tree. They're completely independent. Let's say that each of the commercial products is configured to decompose to a Billing technical product.
The Relies On scope allows you to say, "consider these products as part of a bundle, even though they're not in the same hierarchy. If they're in the same order, then decompose them to one technical product." Unlike Account scope or Order scope, you're able to relate individual commercial products together without affecting what happens with other bundles.
Example of Relies On scope with a simple setup
In the following example, the catalog is set up with two independent commercial products that each have a decomposition relationship (or DR) to Activation spec. Activation spec has the scope Relies On. Without using the Relies On scope, this scenario would result in two Activation Spec technical products.
Catalog
When creating the order, the operator sets the Roaming service to rely on the Voice service (remember that the Activation Spec already has the Relies On scope in the catalog). The result is that the two commercial products decompose to a single Activation Spec.
Order
Further Examples of Relies On Scope
Let's look at several different orders all based on a given catalog setup. This catalog setup has four commercial products that each have a decomposition relationship with the same technical product (imaginatively called TechProd01). That technical product has the Relies On scope.
Here's what the catalog looks like:
Here's how an order would look if the operator entering the order has CommProd04 relying on CommProd03, which relies on CommProd02, and so on. Because they all rely on each other, they only decompose to a single instance of TechProd01.
Now imagine that one of the commercial products relies on two of the
other ones. What happens in that case? Again, each commercial product relies on, or
is relied on, by another. Since TechProd01 has the Relies On scope, the commercial
products decompose to a single instance of TechProd01.
Now, let's look at a loop. In this case, each commercial product
relies on another one. The result probably seems familiar by now. Once again,
there's one instance of TechProd01.
Finally, let's see what happens when a commercial item relies on
another one within a hierarchy of its own. Note that although Mobile Access and SIM
are in the same hierarchy, they each decompose to their own instances of Activation
Spec. That's because SIM and 10 GB Data don't have a Relies On relationship.
