Purchasing: Price Determination for Configured Materials


As of Release 4.0A, you can maintain variant conditions in the purchasing info record for configurable materials . The technique corresponds to that involving variant conditions in sales documents in the Sales and Distribution component.

The individual variant conditions are identified by a variant key. When you specify the variant key, note that the system differentiates between upper- and lower-case.


If a bicycle frame is ordered in the color 'SILVER METALLIC', the vendor adds a surcharge of $20.00 to the price. To reflect this, the variant condition SILVER is created. If a frame in silver metallic color is now chosen, the variant condition is taken into account in the price calculation for this product.


The material configuration specified in the sales order or material master record is adopted in the purchase order. The net price for the material is then displayed in the PO item overview. When you display the conditions for the item, you see the value with which the variant conditions have been taken into account in determining the net price.


A reference characteristic pointing to the field VKOND in the structure MMCOM must have been created. The reference characteristic must be assigned to the variant class of the configurable material.

With the aid of the reference characteristic, you can link to the variant condition in object dependencies. The conditions are accessed via their variant keys.


A new access sequence - 0014 - and two new condition types - VA00 (quantity-dependent) and VA01 (percentage) - have been defined in Customizing for Purchasing. The condition types are located in schema RM0000. They have the indicator variant condition . The condition category '0' (variants) is thus no longer necessary.

Change system parameters in customizing

For more on this topic, refer to the IMG

Define price determination process .

Changes to the interface

You maintain variant conditions in the purchasing info record via Extras -> Variant conditions . The name of the key must not exceed 26 characters in length.

Further notes

Further information is available in the documentation LO Variant configuration.