VARIANT CONFIGURATION OVERVIEW
Prepared by
Arun prasad C R
*Please place your comments

Variant Configuration
Introduction:
• Variant Configuration is useful if you have a large number of
combination of parts that go into a product. It means different permutations
and combinations of the parts for same material.
• If you maintain a unique material code for each possible
combination of parts, you require a large number of material numbers.
• Usually involves Make to Order Production Process
Variant Configuration
Examples:
• A customer ordering a computer can choose different
combinations of monitor, CPU, keyboard.
• A customer ordering a car can choose different combinations of
accessories and color.
• In a business involving steel manufacturing, the customer may
order steel involving different physical properties like tensile strength,
diameter.
Source: SAP

Industries for Configurable Products
Variant Configuration
Source: SAP

Cross Module Integration
Variant configuration is integrated with the following applications:
CA Classification
LO Material Master
PP Bill of Material
PP Routings
PP Material Requirements Planning (MRP)
PP Production Orders
PP–PI Master Recipes
Variant Configuration
CO Costing
SD Sales
SD Conditions
MM Purchasing
Source: SAP

Overview of Terms
Variant Configuration
Source: SAP

Overview of Terms
• A configurable material has a special bill of material called the
Super BOM in which all possible combinations are stored.
• The product is configured in the sales order by choosing the
required Characteristic Values.
• The requirements are passed on Production Planning. On
Explosion of the Bill of Material, the system selects the components
assigned to the characteristics values in the order.
Variant Configuration
• After production, the material is assigned as sales order stock
for delivery to customer.
Source: SAP

• Sales Order Processing

IDES Demo
Process Steps to be used in the demo:
• Creating a Sales Order
• Checking Requirements Using MRP
• Requirements Planning
• Converting the Planned Order into a Production Order
• Confirming the Production Order
• Checking the Production Order Settlement
Variant Configuration
• Creating a Delivery
• Creating a Billing Document
Source: SAP

Enterprise Structure used for demo
Company Code 1000
Sales Org 100
Distribution Channel 12
Variant Configuration
Division 00
Plant 1000
Storage Location 0001
Shipping Point 1000
Source: SAP

MTO Process Overview
Make-To-Order Production With a Configurable Product:
In this process, you create a sales order in SD and transfer the requirements to PP.
The requirements are checked using MRP, before a production order is generated.
This production order is created in PP.
Shipping and billing both occur in SD.
Finally, you check the costs and revenues in CO.
Variant Configuration
Source: SDN

Creating a Sales Order (T Code :VA01)
• After entering the sales data, a configuration screen pops up.
• Configure the material by selecting the characteristics.
• Note that the value of Variant Conditions changes as per selection.
Variant Configuration
Source: SAP

Creating a Sales Order (VA01)
• The system allows analysis of Object Dependencies and Variant Conditions.
• Item Category determined in Sales Order is TAC.
• Note the Material Availability Date and save the sales order (for test11048 and 11059).
Variant Configuration
Source: SAP

• Configuration for VC

Configuration Details: Material Type
OMS2: In definition of KMAT Material Type, indicator ‘Material is Configurable’ is set
Other material types like FERT (Finished Product) can also be used if the indicator is
set in material master
Variant Configuration
Source: SAP

Configuration Details: Item Category in sales order
VOV4: Item Category determination is set to determine item category TAC
Variant Configuration
VOV8: Item Category TAC
Source: SAP

Configuration Details: Condition type for Pricing
Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing
Variant Configuration
Source: SAP

Configuration Details: Requirement type KEK
The requirement class controls the MRP and the requirements consumption strategy
as well as the relevancy for planning, settlement profile for costing.
Requirements type KEK is determined for strategy group 25 and also for item category TAC.
Variant Configuration
Source: SAP

Classification System: Characteristics
Mayback 57 S
Engine
Color
Rear wheel
Seat
Exhaust
Antitheft device
Variant Configuration
Other Options
Source: SAP

Classification System: Characteristics
Variant Configuration
Source: SAP

Classification System: Characteristics
Variant Configuration
Source: SAP

Classification System: Characteristics
CT04: Create characteristics
• Data type can be CHAR, NUM, DATE, TIME, CURR
Variant Configuration
List of values and default value for characteristics can be stored in Value tab.
Source: SAP

Reference Characteristics
Reference characteristics are characteristics that refer to table fields.
Variant Configuration
Tables / Structures whose filed values can be changed by dependencies:
SDCOM - Communication between SD and Variant Configuration
VCSD_UPDATE - Table for Updating Sales Documents from the Configuration
MMCOM, STPO, PLPO, PLFH, PLFL
Tables / Structures whose filed values can be read by dependencies:
VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG
VEDA, MAEPV, MAAPV
Source: SAP

Classification System: Characteristics
CT04: Create characteristics
• Object dependencies like pre conditions, selection condition, action,
procedures can be created for characteristics
• Object dependencies like pre conditions, action, procedure can be
created for characteristic values
Variant Configuration
Source: SAP

Classification System: Class
CL01 /CL02: Create class under class type 300 for Variants
Variant Configuration
Assign the characteristics to the class.
During Material Master creation for Super BoM, this class will be used in the
Classification view.
Source: SAP

Material Master of Super BoM (MM02)
• Basic Data 2 Screen: Set ‘Material is Configurable’ Indicator
• To determine item category TAC in sales order, maintain a suitable item
category group such as 0002
• MRP 2 View: Procurement type ‘E: In house Production’
• MRP 3 View: Strategy Grp. ’25: Make-to-order for configurable’ used for demo
• MRP3 View: Availability Check ’02: Individual Requirement’
• Classification view: Attach the variant class
Variant Configuration
Source: SAP

Bill of Materials (CS01 / CS02 / CS03)
Variant Configuration
Source: SAP

Object Dependency in BoM (CS02)
Components in Production Order can be selected using Object Dependency type
Selection Condition
Variant Configuration
Source: SAP

Routings (CA02)
Operations in Production Order can be selected using Object Dependency type
Selection Condition
Variant Configuration
Source: SAP

Configuration Profile: Process
Planned/production Order; explosion indicator None (others Single level or Multiple level)
The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the
variant are required. The components are determined later during material requirements planning or
production, so there is no need to explode the BOM in the sales order.
Sales order (SET): See next slide also
In the sales order, sales-relevant components are shown as sub-items of the header material.
Requirements are transferred and pricing is calculated at component level, not at header material level.
Order BOM
You create a sales order. In order BoM, you can insert extra items or delete items manually. The
Variant Configuration
changed BOM is stored as a separate BOM for the sales order.
Source: SAP
CU42

Configuration Profile: SET
This processing form means that in the sales order you can only process sales-relevant BOM
items. You can use the item category group like 0004 at configurable material level to define
that requirements transfer and pricing are at component level.
For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These
components are all salable materials that are manufactured separately. In the sales order, you
want to see the individual components that make up the computer as order items, as well
as the whole computer. In the sales order, these products are grouped together in a SET. For
this reason, this type of processing is also referred to as set processing.
Variant Configuration
Source: SAP

Configuration Profile: Dependencies
Dependencies like Actions and Procedure can be assigned to Configuration Profile.
Variant Configuration
Source: SAP

Configuration Profile: Variant Table
• Tables are used to store combinations of values for different characteristics
• A table HD_1300_COLOR_PR is created in CU62 transaction.
It has 2 fields: HD_COLOR (key field) and SURCHARGE.
The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2.
• The table contents are given below (see transaction CU60)
Variant Configuration
VK30: Has description entries for the surcharge
column listed above
VK12: Will pick up pricing value based on
condition type VA00
Source: SAP

Pricing
Check definition of characteristic SURCHARGE2 – Additional data tab -> reference table and field
Variant Configuration
Simple method to achieve Variant Pricing is given below:
• Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND.
• Put this characteristic in the class HD-000 which was used for the configurable material
• Now go to CT04 and change the Characteristic HD_COLOR
Go to values tab and select Red.
Go to Extras-> Object Dependencies->Editor and then select Procedure.
In front of 000010 Enter $self.surcharge2='HD-003_03'.
Similarly Select Black to enter $self.surcharge2='HD-003_02‘. Same way 'HD-003_01’ for Silver
• VK30: Has description entries for the surcharge column listed above
• VK12: Will pick up pricing value based on condition type VA00
Source: SAP

Pricing
VK30: Maintain descriptions for variant price conditions
(optional step; done while creating dependencies for surcharges; maintains consistencies of configuration)
Variant Configuration
VK11 / VK12: Maintain actual condition record for variant price surcharges
Source: SAP

Pricing Factors
Pricing factors can only be maintained on characteristic level.
The syntax of pricing factors is as follows:
$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>)
This expression contains the following information:
• The characteristic that refers to structure SDCOM, in which variant conditions are defined.
• The variant key used to infer the condition for a characteristic value.
Variant Configuration
• The factor by which the surcharge increases.
Source: SAP

Material Variant
• For variants that are required frequently, create material variants, which can be produced without
a sales order and kept in stock.
• When a sales order is received, check whether the variant is in stock and deliver immediately.
• The material master record of a material variant is linked to the configurable material and
configured using the characteristics of the configurable material.
Variant Configuration
Source: SAP

Material Variant in Sales Order
On the value assignment screen, you can check whether the values assigned match the
configuration of a material variant.
Variant Configuration
Source: SAP

Material Variant
Replacement of configurable material by a material variant
Variant Configuration
Source: SAP

Material Variant
Item category gets changed to TAN; Pricing will also change as per new MTS product.
Variant Configuration
Source: SAP

Summary of day 1
By now, you should be comfortable with the following topics:
• Explain what Variant Configuration is and its use in make to order scenario
• Using Variant Configuration during sales order processing
• Configuration details like item category and condition types
• Classification System - Characteristics and Classes
• Super BoM, Configuration Profile, Object Dependencies
• Pricing Surcharges in sales order processing
Variant Configuration
• Using Material Variants for make to stock scenario
Source: SAP

• Day 2: Understanding Object Dependencies in detail

Dependency Types
Variant Configuration
Source: SAP

Pre Condition
Variant Configuration
Only if the model specified is racing, the bicycle can have 21 gears.
1. Create a precondition with the following source code:
MODEL eq 'Racing' and Specified MODEL
2. Allocate the precondition to value 21 of characteristic GEARS
Source: SAP

Selection Condition
A selection condition is allocated to each component and each operation. This selection condition
determines which components and operations are selected for a variant.
Variant Configuration
Source: SAP

Changing Master Data with Dependencies
In variant configuration, you can use reference characteristics with dependencies to change
field values of tables for bills of material (BOMs), task lists, and master recipes.
Table names and fields are given below for reference.
Table STPO field MENGE can be used to change component quantities of BoM.
Table PLPOD field VGW01 can be used to change setup time of Operation.
Variant Configuration
Source: SAP

Procedures
Procedures can set default values for a characteristic (can be overwritten by the user)
Variant Configuration
Source: SAP

Procedures
• Set default values:
$SET_DEFAULT ($SELF, <characteristic>, <term>)
For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT
($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER'
• Delete default values:
$DEL_DEFAULT ($SELF, <characteristic>, <term>)
Variant Configuration
Produce a sum of the values for a characteristic in a multi-level configuration:
$SUM_PARTS ($SELF, <characteristic>)
It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE,
gross weight field BRGEW
• Add the components of a BOM together:
$COUNT_PARTS (<$SELF>)
• Surcharge for variant conditions in Pricing:
$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>)
Source: SAP

Constraints and Dependency Net
The main purpose of a constraint is to monitor the consistency of a configuration.
There are four sections in a constraint.
1. OBJECTS: Declaration of all classes and objects used.
2. CONDITION: Pre requisite for processing the constraint.
3. RESTRICTIONS: For interdependencies and consistency check; check and set values.
4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred.
Variant Configuration
Constraints are grouped together in dependency nets.
The dependency net can be allocated to a configuration profile.
Example: The hard disk can only have the value ‘1620’ for a tower, or ‘850’ for a mini tower.
OBJECTS: PC IS_A (300) PC
RESTRICTIONS:
PC.HARD_DISK = ‘1620’ if PC.CASING = ‘Tower’,
PC.HARD_DISK = ‘850’ if PC.CASING = ‘Mini tower’.
Source: SAP

Actions
Actions can be used to infer values for characteristics.
Actions can also be used to change field values in BOM items or operations in routings.
Procedures can set default values for a characteristic, which can be overwritten by the user.
The user cannot overwrite values that are set by an action.
For new developments, use Procedures rather than Actions (to become obsolete)
Variant Configuration
Source: SAP

Object Variables used in Multi level configurations
Variant Configuration
Source: SAP

Allowed Dependency Types
• Preconditions are allowed for characteristics and characteristic values.
• Selection conditions are allowed for characteristics, BOM items, operations, and
production resources/tools.
• Procedures & Actions are allowed for characteristics, characteristic values, BOM
items, operations, and configuration profiles.
• Constraints can only be linked to a configuration profile via dependency nets.
Variant Configuration
Source: SAP

Processing Sequence for Dependencies
• Each time you enter a value for a characteristic on the value assignment screen and
confirm the value, the system processes all the dependencies.
• The dependencies are processed in the following sequence:
1. All actions several times, until no more values can be inferred.
2. All procedures exactly once in the following sequence:
a) Procedures for the configuration profile in the order you defined
b) Procedures for characteristics
Variant Configuration
c) Procedures for characteristic values
The procedures for each characteristic or value are processed in the order you defined.
3. Actions
Values set by procedures can also trigger actions. For this reason, all actions are
processed again.
4. Preconditions
5. Selection conditions for characteristics
Constraints are processed in parallel with points 1–3, if all the objects in the OBJECTS
section are present, and if all the conditions in the CONDITIONS section are fulfilled
Source: SAP

• Transfer to Production Planning (Demo)

2. Checking Requirements Using MRP (T Code :MD04)
Step1 to create sales order has already been discussed earlier.
2. Stock Requirements List:
• The sales order is displayed as a separate planning segment (sales order stock
required on material availability date and sales order).
Variant Configuration
Source: SAP

3. Requirements Planning (T Code :MD50)
The sales order will now be converted into a planned order. Planned Orders
represent the first step toward an actual production schedule for the Shop Floor.
Variant Configuration
Source: SAP

4. Convert the Planned Order into a Production Order (MD04)
• Planned Orders are a result of MRP run and serve to provide an initial
Production Schedule.
• Production Orders contain comprehensive information to support a shop
floor schedule and provide a method to confirm operations performed.
• Production orders can be created with reference to a Planned Order.
Variant Configuration
Source: SAP

4. Convert the Planned Order into a Production Order (MD04)
Object Dependency:
BoM Selection Condition ensures only necessary material components are taken.
Variant Configuration
Source: SAP

4. Convert the Planned Order into a Production Order (MD04)
Object Dependency:
Routing Selection Condition ensures only necessary operations are taken.
Variant Configuration
Source: SAP

4. Convert the Planned Order into a Production Order (MD04)
Prior to release of order, it is not possible for anyone to enter confirmations for the
operations in the order.
Release the Order and Save it.
Display the operation scheduling overview, choose Goto  Graphic  Gantt chart.
Variant Configuration
Source: SAP

4. Convert the Planned Order into a Production Order (MD04)
Display the planned costs, choose Goto  Costs  Analysis
Variant Configuration
Source: SAP

5. Confirming Production Order (CO11N)
Production Control  Confirmation  Enter  For Operation  Time Ticket
Variant Configuration
Source: SAP

5. Confirming Production Order (CO11N)
• Back flushing (posting of an issue of components or material withdrawals)
• Storage of the finished product in the warehouse to sales order stock
• Goods Movements are posted (errors if any can be corrected in COGI)
• Actual costs are calculated
• Just in case, to close the order without yielding a product, perform Restrict
Processing -> Technical Completion for Production Order in CO02.
Variant Configuration
Source: SAP

5. Confirming Production Order (CO11N)
• Sample Material Document and FI document entries are shown below
Variant Configuration
Source: SAP

6. Checking the Settlement of the Production Order
From the Production Control node, choose Period-End Closing  Settlement 
Individual Processing (KO88)
Perform order settlement to transfer the costs of the production order to sales order.
Analyze the current cost situation for the Production Order
Variant Configuration
Source: SAP

7. Creating a Delivery (VL10G for delivery due list, VL01N for single delivery)
Assign a serial number to the material. Pick and post the goods issue.
Movement type will be 601 E indicating delivery from sales order stock.
Accounting document will be generated to capture the change in inventory.
Variant Configuration
Source: SAP

8. Creating Billing Document (VF04/VF06 for due list, VF01 for single invoice)
VF01: Create the invoice – sample accounting entries (without tax) are shown below
F-28: Receive the payment from the customer
Variant Configuration
Source: SAP

Other Information
• CRM: It is possible to have configurable products among your Online Store
offerings using the IPC (Internet Pricing and Configurator). It allows customers to
interactively choose product options via an easy-to-use interface. Customers can mix-
and-match these options to build the exact product they wish to purchase.
• ECC 5.0: Single transaction PMEVC – Modeling Environment for VC
Variant Configuration
Source: SAP

Summary
By now, you should be comfortable with the object dependencies and the following topics:
• Pre conditions
• Selection conditions
• Procedures
• Actions
• Constraints and Dependency Net
Variant Configuration
• Transfer of sales order requirements to PP
• Delivery from sales order stock
• Invoicing the customer
Source: SAP

Variant Configuration
THANK YOU