Pricing in VMS is based on condition technique. The basis is always the pricing procedure that has been defined as default in the SAP Internet Pricing and Configurator (SAP IPC).
It is recommended to use the standard pricing procedure RVAA01 as default value. However, you can enter your own pricing procedure as the default. In the organization roles (transaction VELORO) you can also enter other procedures for specific organizations. These values then override the default value.
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 individual configures characteristics and, where appropriate, the discounts.
You can find further information in the documentation for Sales and Distribution ond/or Materials Management under:
· Pricing and Conditions (SD)
You have defined pricing procedure RVAA01 (see above) as the default value in SAP IPC.
This procedure only describes a very simple example as a guide for creating variant conditions. Variant conditions can be very complex.
Create gross prices for the vehicle that has not been configured – once in sales and once in purchasing.
¡ 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.
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
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.
$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.
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.
You can find further information in the Basis documentation under Dependency Syntax: General Rules.
You can also use variant tables to link the configuration characteristics to the price characteristics.
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, 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.
Assign the dependency to the configuration profile (transaction CU42).
The price determination data is now complete. However, this data is not available to you until you have downloaded it to the IPC system.