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 are not 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 the following table.

    Product Start Date End Date List Price

    P

    12/31/2004

    04/01/2004

    1000

    P1

    12/31/2003

    01/15/2004

    100

  • Adjustments have been defined for P1 when it is a component of P that are shown in the following table.

    Adjustment Type Adjustment Value Start Date End Date

    Price Override

    104

    02/05/2004

    02/29/2004

    Percent Discount

    10

    03/01/2004

    03/31/2004

  • In this case, if the product P1 is ordered in the context of the root product P on 02/15/2004, then 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 Customer Order Management.

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.