Variant Configuration

VARIANT CONFIGURATION
Variant Configuration is for Manufacturing Complex Product in which customer determines the features of the product e.g: Automobile Industry Furniture Manufacturing No need to create separate Material for each Variant of the product.

Advantages of VC
No need to Create separate material master for each variant combination. Super BOM and Super Routing is enough for representing all possible Variants and Operations. Able to react more flexible to customer demands. Increase Information exchange between sales, engineering and production.

Master Data
What is Configurable Material? A material with different features or characteristics and options is known as configurable material. Example: PC, Car. Configurable materials are either created in a material type that allows the configuration (n the standard system, the material type KMAT) or they are given the indicator Configurable in the material master record.

Master Data

Material is Configurable tick in Basic Data 2 Tab Page of the Material Master

Master Data
Master Data Used for VC are as follows 1. Super BOM 2. Super Routing 3. Characteristic 4. Class 5. Object Dependencies 6. Configuration Profile 7. SD Condition records

Master Data
Super BOM Super BOM Contains all the components for producing configurable product. It contains both variant as well as non-variant parts required for producing configurable product. Advantages: No need to create a separate BOM One configurable material to cover variants.

Master Data
Super Routing A configurable routing describes the production process for all variants of a product. Instead of creating a routing for each variant of a product, you can create operations for one routing, or a "super" routing. Advantages: No need to create a separate Routing One configurable material to cover variants.

Master Data (Characteristic)

Characteristic is used to define the features of a configurable material Characteristics describe the properties of objects. The values of a characteristic specify these properties. It is also possible to use table name and its field name in order to change the Object quantity or values. I.e. BOM item quantity or Operation time, which is known as reference characteristic.

Master Data (Characteristic)

Engine 1600 1800 2000 2500 ... Extras ABS Cruise control Heated seats ...

Transmission 4-gear 4-gear automatic 5-gear 5-gear automatic ...

Paintwork Black Red Blue ...

Wheels Steel wheels Light alloy wheels standard Light alloy wheels wide tires ...

Master Data (Characteristic)

The graphic shows the individual product options such as engine, gears, paintwork, mapped as characteristics. You define values for characteristics, to allow you to select specific options, such as 'black' for paintwork.

Master Data (Characteristic)

Transaction Code: CT04

Settings for the Characteristic (Basic Data Tab)

Master Data (Characteristic)

Single Value : Only one value can be assigned to the characteristics at the time of configuration. Multiple Value: Multiple Values can be selected at the time of configuration Restrictable Tick: The values of a restrictable characteristic can be restricted during configuration to certain allowed values Entry Required: This tick makes the characteristic entry required at the time of configuration

Master Data (Characteristic)

Data Type and Length of character for the characteristic

Settings will change as per the data type input.

Master Data (Characteristic)

Additional settings appeared for the Numeric Data type; No of Chars, Decimal Places, Unit of Measure, Neg. Values and interval values allowed.

Master Data (Characteristic)

This are the allowed values for the characteristic. Check Additional Values tick if User wants other than allowed values

Master Data (Characteristic)

Settings in Additional Data Tab of the characteristic

Master Data (Characteristic)

Not Ready for Input: This settings makes the characteristic not ready for input. It means the value can be derived through object dependency only.
VC_CHAR_REF_BOM is not ready for input

Master Data (Characteristic)

No Display: This setting makes the characteristic hidden.

The following Characteristic are No Display Characteristic.

Master Data (Characteristic)

Display Allowed Values: This setting display all allowed values. There is no need to select option button.

This will show all values and if double clicked on value it will be selected and turns out to blue colour

Master Data (Reference Characteristic)

This are the write reference characteristic

Master Data (Reference Characteristic)

There are two type of functionality Write Reference Characteristics You can transfer values from the configuration to the application using reference characteristics with write access to table fields. These types of reference characteristics refer to: Table STPO and field MENGE for transferring the item quantity Table SDCOM and field VKOND for transferring variantdependent surcharges or discounts on prices. Control Reference Characteristics Certain reference characteristics allow you to control the user interface during configuration; this includes the visibility and readyfor-input status of characteristics. These reference characteristics refer to the table SCREEN_DEP and the fields: INVISIBLE for controlling the visibility of characteristics NO_INPUT for controlling the ready-for-input status of characteristics

Master Data (Reference Characteristic)

This is the reference characteristic. It refers to the Table Field as shown.

Master Data (Reference Characteristic)

Table/Structures whose field values can be read by dependency VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG, MAEPV, MAAPV. Table/Structures whose field values can be Changed by dependency SDCOM Communication between SD and Variant configuration

Master Data (Class)

Class is used to hold the characteristics that describe a configurable material. You can only use a class in variant configuration if the class has a class type that supports variant configuration. Eg: Class Type 300

Master Data (Class)

Class of Class Type 300 holding the characteristic as shown.

Master Data (Class)

Assign Class to Configurable Material

Master Data (Configuration Profile)

It is central setting for configuring the configurable object There can be several profiles with different settings for an object. User need to select specific profile during configuration.

Master Data (Configuration Profile)

Different Profile for Configuration profile having different setting.

Master Data (Configuration Profile)

Dependencies assigned to the configuration profile

Master Data (Configuration Profile)

This are various settings in the configuration profile

Master Data (Configuration Profile)

Planned/Production Order: If selected with BOM explosion None. No BOM explosion takes place in the sales order. Components required are not determined until MRP or Production Stage. If selected Single Level: Only one level of BOM results can be seen in Sales Order. If Selected Multi Level: All level of BOM results can be seen in the sales order.

Master Data (Configuration Profile)

Sales Order (SET) : The forms means that in the sales order user can process Salesrelevant BOM Items. Requirement transfer and Pricing are at component level. Eg: BOM of PC
PC

Printer

Monitor

Keyboard

CPU

Master Data (Configuration Profile)

A PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that can be manufactured separately. In the sales order, user want to see the individual components that make up the computer as order items, as well as the whole computer In sales order processing, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing.

Master Data (Configuration Profile)

Example of SET processing. Component 1927 appearing as an order item.

Master Data (Configuration Profile)

Order BOM: This Processing option is selected if user wants to make customer specific changes to the material BOM that user has configured in the sales order. BOM is not exploded in the sales order.

Master Data (Configuration Profile)

Two Types of Order BOM 1. Result Oriented Order BOM Saves the Configured BOM with manual changes 2. Knowledge Base Order BOM Saves the Super BOM with manual changes and dependencies, not the configured BOM. When user exploded the BOM, the dependencies are processed dynamically and only the selected items are displayed.

Master Data (Configuration Profile)

Knowledge Base Order BOM setting in Configuration Profile

Maintenance of Order BOM setting in Configuration Profile

Master Data (Configuration Profile)

At the time of configuration of sales order Engineering Button appears to change or delete BOM Item.

Object Dependencies
Purpose 1. Describe the interdependencies between characteristics and characteristic values. 2. Control which components are selected from a bill of material (BOM) and which operations are selected from a task list 3. Change the values of fields in BOM items and operations during configuration

Object Dependencies Types

The SAP System supports the following types of dependencies: Preconditions Selection conditions Actions (obsolete) Procedures Constraints

Object Dependencies
Global and Local Dependencies The differences between global and local dependencies are as follows: Global dependencies are created centrally and can be assigned to several objects. Local dependencies are created for one object and can only be used with this object.

Object Dependencies
Precondition: You can allocate preconditions to the following objects: A characteristic that you want to hide A characteristic value that you want to hide

Object Dependencies

Create Dependency through CU01 and select precondition for hiding value 2 for char VC_RAM

Object Dependencies

Syntax for Precondition.

Object Dependencies

Assign a Dependency PRE_01 to the value 2 of the characteristic VC_RAM

Object Dependencies
Check the configuration in simulation CU50. Value 2 for Char VC_RAM is invisible when VC_HARD_DISK value is 40.

Object Dependencies
In order to Hide Characteristic, assign dependency to characteristic not characteristic value.
Click here to assign dependency in order to hide the characteristic

Object Dependencies
Selection Condition Selection conditions determine which variants require a specific component or operation Selection conditions determine when it is mandatory to assign a value to a characteristic

Object Dependencies
You can allocate selection conditions to the following objects: Characteristics BOM items Operations in task lists Sub-operations Sequences of operations Production resources/tools (PRTs)

Object Dependencies
Syntax for selection condition is same as precondition but the functionality is different.
Selection condition assigned to the BOM items

Object Dependencies

This is the selection condition syntax written for BOM Item 10

Object Dependencies
Procedure 1. Procedure is used to infer values for the characteristic. 2. Procedure can overwrite default values that are set by other procedure. 3. Procedures can set default values for a characteristic, which can be overwritten by the user. 4. If several procedures are assigned to an object, you can define a processing sequence

Object Dependencies
You can assign procedures to the following objects: The characteristic value that triggers the procedure The characteristic that triggers the procedure The configuration profile of the configurable object BOM items to change the component quantity, for example Operations in task lists to change the standard values, for example

Object Dependencies
Use of Procedure If you use a procedure to infer a value for a characteristic, you enter the variable $SELF before the characteristic. Procedures can overwrite values that are set by other procedures. Procedures are always used for pricing

Object Dependencies
Additional keywords for procedures: Set default values:
$SET_DEFAULT ($SELF, <characteristic>, <term>)

Delete default values:

$DEL_DEFAULT ($SELF, <characteristic>, <term>)

Object Dependencies
Syntax for Procedure
Example of setting and deleting the default value

Object Dependencies
Produce a sum of the values for a characteristic in a multi-level configuration:
$SUM_PARTS ($SELF, <characteristic>)

Add the components of a BOM together:

$COUNT_PARTS (<$SELF>)

Surcharge for variant conditions:

$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>,<factor>)

Object Dependencies
In procedures, you can use the following keywords, which are not allowed in actions: NOT SPECIFIED NOT TYPE_OF <multiple-value characteristic>NE<value>

Object Dependencies

This is the simple procedure to infer the value for the Characteristic VC_MONITOR

Object Dependencies

Value 21 inferred for the characteristic

Object Dependencies (Variant Tables)

Purpose Tables are used to store combinations of values for different characteristics Tables are an aid to entry for dependencies. You enter the table in a dependency. The system uses the table to infer and check values.

Object Dependencies (Variant Tables)

There are two steps to creating a table: 1. You define the table structure. TCODE: CU61 You enter the characteristics that you want in the table and define value assignment alternatives. The characteristics in the class can be identical to those in the table. However, only use singlevalue characteristics in tables. If the characteristics of the class are multiple-value, create single-value characteristics especially for the table. However, the characteristics must have the same format and values. 2. You maintain the table entries. TCODE: CU60

Object Dependencies (Variant Tables)

Structure of Variant Table. Mark key field for input characteristic and unmark the characteristic which need to infer

Object Dependencies (Variant Tables)

Maintain values for the table TAB_COMPUTER in CU60

Object Dependencies

Call Table TAB_COMPUTER in a procedure to infer value of the Char VC_COMPUTER_COLOR

Object Dependencies
Assign Procedure PRO_COMPUTER to the configuration profile of the material TCODE CU42

Object Dependencies
Value RED inferred for the Characteristic VC_COMPUTER_COLOR through procedure PRO_COMPUTER

Object Dependencies
Constraint This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of a constraint is to monitor the consistency of a configuration.

Object Dependencies
Features of Constraint 1. Constraint is used to infer or restrict the characteristic values 2. Constraint are used to check the consistency of the configuration. 3. It is used to describe the dependencies between completely different objects and their characteristics. 4. Processing sequence is not relevant in the constraint. 5. Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.

Object Dependencies
Structure of Constraints There are four sections in a constraint. Each part is identified by a keyword. The keyword is followed by a colon. Each section ends with a period. OBJECTS: In this section, you enter the objects that are relevant to the constraint. You must enter the relevant objects in all constraints. You can also define variables for objects or characteristics. CONDITION: The condition entered here must be fulfilled in order for the constraint to be used. You do not need to enter a condition in a constraint. You can leave out the keyword CONDITION: if required. However, if you enter the keyword you must enter a condition.

Object Dependencies
RESTRICTIONS: In this section, you enter the relation that must exist between the objects and characteristics if the configuration is to be consistent. You must enter a restriction in a constraint. INFERENCES: In this section, you enter the characteristics for which characteristic values are to be inferred. The main purpose of constraints is to check the consistency of

Object Dependencies

Syntax for constraint. Table is call to restrict the values for the characteristic VC_COMPUTER_COLOR

Object Dependencies
Value combination for row no 1 and 6 are same but the last characteristic has different value (Red and Green). Constraint will restrict the value of Char VC_COMPUTER_COLOR into Red and Green.

Object Dependencies

Values are restricted as per the table

Object Dependencies

Red Color inferred for the 2nd combination of the table

Variant Pricing
1. 2. 3. 4. 5. 6. 7. Steps for Variant Pricing Create Condition Table (Use Varcond as one of the field in the table) Create Access Sequence Create Condition Type Assign condition type to Pricing Procedure Create Reference characteristic (refer SDCOM table and VKOND field) Assign Variant key to reference characteristic through dependency Maintain Condition record (VK11) for the Variant key.

Variant Pricing

Select the required field in the table and Variant as one of the field.

Variant Pricing
Technical View of the Table

Variant Pricing
Create an access sequence VA00 and assign the condition table 57

Variant Pricing

Create Condition Type VA00 and assign access sequence VA00 to the condition type

Variant Pricing
Assign Condition Type VA00 to Pricing Procedure RVAA01 as shown

Variant Pricing

Create a reference characteristic VC_CHAR_PRICE_REF referring the table SDCOM and VKOND

Variant Pricing

Create a procedure PRO_PRC_01 to infer variant key ABC under certain condition as shown

Variant Pricing
Assign procedure to configuration profile of the material

Variant Pricing

Maintain a Condition record for Condition Type VA00

Variant Pricing
Create a sales order and assign value 2 to the char VC_RAM which will trigger the pricing procedure.

Variant Pricing

Variant key ABC picked up in the pricing of the computer.

Material Variant
A material variant is a material that can be kept in stock and that arises from an individual configuration of a configurable product. The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material. This variant of the configurable material can then be manufactured and kept in stock.

Material Variant

Create a material master of Material Variant and assign configurable material COMPUTER in MRP 3 view of MM and then configure the variant as shown in the next slide.

Material Variant

This is the configured variant

Material Variant

Sales Order created on configurable material COMPUTER. After configuring the material, type matching took place and material variant found as shown

Material Variant

After Type matching, configurable material will be replaced by material variant.