|Bookshelf Home | Contents | Index | PDF|
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.
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:
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.
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.
|Pricing Administration Guide|