Variant Configuration

Author: Chandrashekhar Putcha Page 1 of 1

VARIANT CONFIGURATION

Purpose:
The purpose of this document is to give an overview and facilitate in creating the basic settings
for variant configuration from sales and distribution point of view.
Overview:
Variant Configuration is a description of complex products that are manufactured in many variants
(for example, cars). All variants are defined as one variant product. The variant product has a
super BOM, containing all the components that can be used for the product, and a super task list,
containing all the operations that can be used to manufacture the product.
By assigning the variant product to a class, you assign characteristics to the variant product. You
use these characteristics to describe an individual variant. Object dependencies ensure that the
correct components are selected from the super BOM and the correct operations are selected
from the super task list.
The basic requirements for using variant configuration is
1. Material of type KMAT ( configurable material).
2. When this material is created the system automatically selects Item Category Group :
0002.
3. When this material is used in a sales order document, the item category selected is
TAC.
Variant configuration is controlled by,
1. Class. A group of similar objects described by means of characteristics that they have in
common
2. Characteristics. Properties for describing and distinguishing between objects, such as
length, color, or weight.
3. Values for each characteristic. A value or values for the characteristic(s) of an object.
4. Object dependencies. Knowledge that describes the mutual interdependencies between
objects. For example, you can define dependencies between characteristics and
characteristic values such that 21-speed gears are only allowed for racing bicycles. You
can also use object dependencies to ensure that the correct BOM items and operations
are selected when an object is configured.
You describe object dependencies in a dependency editor using a special syntax. There
are different types of object dependencies for different purposes.
In product variant structures, local dependencies are used in the form of selection
conditions for component variants.




Variant Configuration
Author: Chandrashekhar Putcha Page 2 of 2

Procedure:
As an overview and basic understanding of variant configuration, the following steps need to be
followed to configure variants for a material and subsequent usage in sales orders.
STEP 1: Create characteristics. PATH: Logistics / central functions / classification / Master data
/ characteristics.
Depending on the material you create characteristics like for example , colour, engine capacity,
automatic or manual transmission, etc for a car.
For these characteristics defined, you now attach values,
Example : colour : red, blue, green, metallic silver, etc, Engine capacity : 1000 cc, 1500 cc, etc.


Variant Configuration
Author: Chandrashekhar Putcha Page 3 of 3
+

STEP 2: If variant pricing is to be used then you create one more characteristic VARCOND.
Note : use Table : SDCOM, & Field : VKORD, while defining this characteristic.


Variant Configuration
Author: Chandrashekhar Putcha Page 4 of 4

STEP 3: Create Class. PATH: logistics / central functions / classification / master data / classes.
Create class E.g.: car, and in the screen, go to Char tab, and enter all the characteristics that
you defined in the desired sequence. Now if you need variant pricing then you add VARCOND as
the last characteristic, otherwise dont.



Variant Configuration
Author: Chandrashekhar Putcha Page 5 of 5

STEP 4: create the material of configurable type.
In the classification view of the material master enter the class that you created. . This can also
be done from transaction code CL20N, Assign objects to classes.



Variant Configuration
Author: Chandrashekhar Putcha Page 6 of 6


STEP 5: Create a Configuration Profile. PATH : logistics / central functions / variant
configuration / configuration profile / create.
For the material created, maintain a profile and attach a class to it. Each configuration profile
must be allocated to at least one class with a class type that supports variant configuration.




Variant Configuration
Author: Chandrashekhar Putcha Page 7 of 7
STEP 6: Create condition record for VA00 (variant pricing). PATH: logistics / sales
&distribution / master data / conditions / create.
First of all ensure that you have the condition record, VA00 in the pricing procedure. The
condition type VA00 is for a absolute value , and VA01 is for a percentage. The condition record
data entered here is added to the basic price ( PR00) while carrying out pricing for the material in
the sales order.

In the figure above, the exactly same keys as used to define the characteristic values shown
below should fill the column variant. This is very important.



Variant Configuration
Author: Chandrashekhar Putcha Page 8 of 8
STEP 7: Configuration simulation. PATH: logistics / central functions / variant configuration /
environment / configuration simulation.


Here you actually provide the link between,
Material plant class characteristic value price (through the variant key that you had
entered in the previous step).
1. First check the plant for which you need to maintain the data. If required to change the
plant, press the icon change plant.
2. Then press the configuration icon to get the screen below.
Explosion
level
Change
Plant
Configuration


Variant Configuration
Author: Chandrashekhar Putcha Page 9 of 9

3. for each characteristic select a value by using F4 help, by which you get the screen below.

3. Here select one value at a time and press the assign variant condition icon, to get the
screen below, wherein you enter exactly the same variant key as defined in STEP 6.
Then save the data. In this way enter all values for every characteristic and save it.


Variant Configuration
Author: Chandrashekhar Putcha Page 10 of 10

This completes the total setup required for variant configuration.