Creating Variant Conditions for Pricing 

Use

Pricing in VMS is based on condition technique. Th basis is always the pricing procedure that has been defined as default in the Internet Pricing and Configurator (IPC).

SAP recommends that you define the standard SAP pricing procedure RVAA01 as default pricing procedure. However, you can enter your own pricing procedure as the default. You can also define other procedures for specific organizations in the organizational roles (transaction VELORO). These procedures then override the default procedure (see also: The Concept of Roles).

There are three types of price:

For more information, see the Standard documentation:

Prerequisites

The following procedure presumes that pricing procedure RVAA01 (see above) has been defined as the default in the IPC.

Procedure

This procedure only describes a very simple example as a guide for creating variant conditions. Variant conditions can be very complex.

  1. Create gross prices for the vehicle that has not been configured – once in sales (SD) and once in purchasing (MM).
  2. Sales: transaction VK11, condition type PR00, key combination material with release status; enter sales organization, distribution channel and material.

    Purchasing: transaction MEK1, condition type PB00, key combination material info. record; enter vendor, material and purchasing organization.

  3. Create object characteristics for pricing in your characteristics group – one in sales (SD) and once in purchasing (MM) (transaction CT04) and assign them to your class (transaction CL04).
  4. These characteristics must have multiple values and are not allowed to be displayed. The characteristics do not have any values.

    Enter the following on the tab page Additional data: table name SDCOM (structure that links to the SD order) and field name VKOND for SD characteristics; table name MMCOM (structure that links to the purchase order) and field name VKOND for MM characteristics.

  5. Create a description (transaction CU01 and enter description, status released and, if required, a dependency group and the dependency type procedure). Link the configuration characteristics to the price characteristics using object dependencies. Example:
  6. $SELF.SD pricing characteristic = 'Variant condition for configuration characteristic_1 and characteristic value_1'
    IF configuration characteristic_1 EQ 'characteristic value_1'

    Please ensure that the characteristic values are included in inverted commas. Each expression must be completed with a comma, except the last one.

    If you have created the keys for variant configuration with small letters, you must also use small letters for the object dependencies. Likewise capital letters.

    You can find further information under Dependency Syntax: General Rules.

    You can also use variant tables to link the configuration characteristics to the price characteristics (see also: Variant Tables).

  7. Create a variant condition with a price for this characteristic value for each configuration characteristic and each possible value – once in sales (SD) and once in purchasing (MM).

Sales: transaction VK11, condition type VA00, key combination variants; enter sales organization, distribution channel and material.

Purchasing: transaction MEK1, condition type VA00, key combination variants for info. record; enter vendor, material, purchasing organization and info. record category.

  1. Assign the dependency to the configuration profile (transaction CU42).

Result

The price determination data is now complete. However, this data is not available in the IPC until it has been transferred there (see: Downloading Data to the IPC).