Creating a Variant Condition for Pricing

Use

Pricing in VMS is based on the condition technique .

In the organizational role GROS , you can define which pricing procedure should be used in vehicle configuration to determine the price.

We recommend using the standard pricing procedure RVAA01 (delivered by SAP) as the default value for the pricing procedure. However, you can enter your own pricing procedure as the default.

There are three types of price:

  • Gross listed price (action CREA Create vehicle ) as list price for the configured vehicle without dealer discounts and other discounts

  • MM price (action ORD1 Create purchase order ) and SD price (action CUOR Create sales order )

    SD and MM prices are formed from the gross price , the variant prices for the individually configured characteristics and, where applicable, the discounts.

For more information, see the documentation for Sales and Distribution and Materials Management under:

Prerequisites

You have defined pricing procedure RVAA01 (see above) as the default value.

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 and once in purchasing.

    • Sales: transaction VK11, condition type PR00, enter key combination material with release status : sales organization , distribution channel and material .

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

  2. Create object characteristics for pricing in your characteristics group – once in sales and once in purchasing (transaction CT04) and assign them to your class (transaction CL04).

    These characteristics must have multiple values and are not allowed to be displayed. The characteristics do not have any values.

    Enter the following data on the tab page Additional Data :

    • for characteristics in sales: table name SDCOM (structure which the sales order accesses), field name VKOND

    • for characteristics in purchasing: table name MMCOM (structure which the purchase order accesses), field name VKOND

  3. Create a relationship (transaction CU01 and enter a description, the status as released and, if required, a dependency group and the dependency type/relationship type as procedure). Link the configuration characteristics to the price characteristics using object dependencies.

    Example Example

    Example:

    $SELF.SD pricing characteristic = 'Variant condition for configuration characteristic_1 and characteristic value_1' IF configuration characteristic_1 EQ 'characteristic value_1'     

    You must include the characteristic values in inverted commas. Each expression must be completed with a comma, except the last one.

    End of the example.

    Caution Caution

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

    End of the caution.

    For more information, see the Basis documentation under Dependency Syntax: General Rules .

    You can also use variant tables to link the configuration characteristics to the price characteristics.

  4. Create a variant condition with a price for this characteristic value for each configuration characteristic and each possible value – once in sales and once in purchasing.

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

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

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

Result

The pricing data is now complete and is available in the Characteristic Value Assignment Screen . The data is not available in the IPC until it has been downloaded, however.