Pricing Administration Guide > Setting Up Pricing for Products with Components >

Impact of Product Versioning and Price List Line Item Effectivity on Component-Based Pricing

A product can have multiple released versions with future dates. In addition, price list line items can have effective dates. As a result, the structure of a product can be dynamic over time, because multiple versions of it can exist.

Component-based pricing takes the following into account:

• Both root CP and its components can have multiple versions across a time interval.
• Both root CP and its components can have multiple entries on a price list for different effective dates.
• The Customizable Product Adjustments (The CP Pricing Designer) can have multiple versions for different effective dates.

This section discusses some of the ways that multiple product versions and multiple effective dates affect component-based pricing.

Component Product Must Exist on the Price List of a Component-Based Product

If a component-based product does not exist on a price list as of a particular date, then the adjustments to its components should not be applied as of that date. For the adjustment to apply to the component product, it must exist on the price list of the component-based product in the same time interval as the adjustment. Consider this example:

• A component-based product, product P, has only one component product, product P1.
• P and P1 have entries in the Price List Line Item list that are shown in Table 13.

• Adjustments have been defined for P1 when it is a component of P that are shown in Table 14.

• In this case, if the product P1 is ordered in the context of the root product P on 02/15/2004, it will have a zero price. You might expect its price to be 104, based on the price override that is effective on that date, but because product P1 does not have an entry in the price list for the interval 02/05/2004 through 02/29/2004, no price appears on the transaction for it.

This behavior is consistent with the prior releases of C/OM.

NOTE:  If a root product with components does not exist on a price list on a given date, then the adjustments to its components are not applied for that date. For example, the adjustments in the CP Pricing Designer might be effective for a specific time interval during which the root product with components might not have an entry in the price list itself. The CP adjustments to the components of the root product with components do not apply during that time interval.

Time Intervals When a Product Is Not Customizable

The price list for a product with components can include a time interval when the product is not customizable. This is possible because a product might not have any structure on a given date, but might have a structure on some other date (specified in a released version with a future date).

In this case, if the user drills down from the price list line item to display the product, the application displays an error message saying that the customizable product does not have versions in the date range, and that the user should choose an appropriate time interval to set up price adjustments for the product. This means that the customizable product does not have structure at that time; that is, that it does not have component products.