Introduction to Variant Configuration with an example model

created by Philipp Kuster

Version 2
inShare1

on Mar 18, 2012 8:37 AM, last modified by Philipp Kuster on May 13, 2012 11:10 AM

Purpose
This guide is supposed to be a short introduction to Variant Configuration with a simple example. With that guide one should be able to set up a first configuration model. If you need further information about this topic please have a look at the online help of SAP, which you can find here: http://help.sap.com.

Variant Configuration
To get an understanding of what Variant Configuration actually is let's read the description offered by the SAP Online Help: "Variant configuration is for manufacturing complex products. The manufacturer is always having to offer new variants of its products. Often, new variants are created by modifying existing product designs as you process the order. The important thing is to react quickly to customers' requirements. The customer determines the features of the product. A customer buying a car, for example, can choose the features of the car and combine these features as required. The product configurator improves information exchange between sales, engineering, and production. Variant configuration helps the customer or salesperson to put together specifications for the product and ensure that the product can be produced from these specifications. It also ensures that production costs do not overstep the mark." Now that we know what's behind these two words we can start to build an example model.

Example Model
In order to keep this guide compact this model will be quite simple. Let's assume that we want to configure a computer. A computer consists of different components which will be chosen accordingly to the characteristics. Our characteristics of the computer are: Characteristic VC_CHR_TYPE VC_CHR_CPU Possible Values Office computer Gaming computer Server Laptop VC_CHR_GRAPHIC_CARD VC_CHR_OTHER_EQUIPMENT (multiple values) A-CPU I-CPU 2 GB 4 GB 8 GB 16 GB N-Graphic Card A-Graphic Card Onboard

VC_CHR_MAIN_MEMORY

High-End Sound Card TV Tuner Card Modem

Each characteristic needs exact one entry except VC_CHR_OTHER_EQUIPMENT. Our computer is a "complex" material and consists of other materials. Therefore we need a bill of materials. Each component has got only one characteristic: VC_CHR_Price Numeric Value

The materials are finished products which are not configurable itself. Bill of materials Components VC_MAT_A_CPU VC_MAT_MEM_2 VC_MAT_MEM_4 VC_MAT_MEM_8

Components VC_MAT_MEM_16 VC_MAT_GRAPH_N VC_MAT_GRAPH_A VC_MAT_GRAPH_O VC_MAT_EQU_SOUND VC_MAT_EQU_TV VC_MAT_EQU_MODEM The characteristics of the computer are not independent among each other. Hence, we define some dependencies. Preconditions Precondition Characteristic / Char. - Value Condition VC_EX_CON1 Other Equipment VC_EX_CON2 8GB + 16GB; A-CPU VC_EX_CON3 N-Graphic Card + A-Graphic Card VC_EX_CON4 Onboard VC_CHR_TYPE <> 'Server' AND VC_CHR_TYPE <> 'Laptop' VC_CHR_TYPE = 'Server' VC_CHR_TYPE = 'Gaming computer' OR VC_CHR_TYPE = 'Laptop' VC_CHR_TYPE = 'Server' OR VC_CHR_TYPE = 'Office computer'

Selection conditions As it is described above the components of the computer will be chosen by means of the chosen characteristics. To implement this functionality we need selection conditions. Material Selection Condition VC_MAT_A_CPU VC_MAT_I_CPU VC_MAT_MEM_2 VC_MAT_MEM_4 VC_MAT_MEM_8 VC_MAT_MEM_16 VC_MAT_GRAPH_N VC_MAT_GRAPH_A VC_MAT_GRAPH_O VC_MAT_EQU_SOUND VC_MAT_EQU_TV VC_MAT_EQU_MODEM VC_CHR_CPU = 'A-CPU' VC_CHR_CPU = 'I-CPU' VC_CHR_MAIN_MEMORY = 2 VC_CHR_MAIN_MEMORY = 4 VC_CHR_MAIN_MEMORY = 8 C_CHR_MAIN_MEMORY = 16 VC_CHR_GRAPHIC_CARD = 'N-Graphic Card' VC_CHR_GRAPHIC_CARD = 'A-Graphic Card' VC_CHR_GRAPHIC_CARD = 'Onboard' 'High-End Sound Card' IN VC_CHR_OTHER_EQUIPMENT 'TV Tuner Card' IN VC_CHR_OTHER_EQUIPMENT 'Modem' IN VC_CHR_OTHER_EQUIPMENT

How to transfer the model into the SAP System?

First of all we need to define the characteristics. This can be done with the help of transaction CT04. After you're done with that you should create a new class which contains all previously created characteristics. You have to consider one important fact: The class should be created with a class type which is intended for Variant Configuration (SAP Standard: Class type 300). The corresponding transaction is: CL02

If you have done it correctly then you should have something like this:

Now you should apply the preconditions to the characteristics and its values. Bill of materials - Materials In order to create a bill of materials we need - of course - materials. These materials can be assigned to a class. As described above this class has got only one characteristic: VC_CHR_PRICE. Moreover the class doesn't have to be of type 300 because the materials are - in our case - not configurable. If you have created this class we can create each material with transaction: MM01.Here you must specify the industry sector and the material type of the material. In our simple example it's enough to classify the material and to set a plant. Hence, we have to select the Classification and e.g. Purchasing View.

Specify the plant in which the material is used.

Enter the material description and the base unit of measure.

Then classify and valuate the material.

After that you can go on to the Purchasing view which is shown below:

Enter the description, the base unit of measure and a material group.Repeat this step for all components of our computer. Bill of Materials - The computer material Now we created all components of the computer, but something is still missing - the computer itself. So we have to make a new material for our computer. This is the configurable material. You should either select "Configurable Mat" as material type in the start screen or you have to select it in the basic data in order to sign this material as configurable.

Select the Purchasing and Classification view here as well, assign a plant, write a description and classify the material with our computer class. Bill of materials Now we have all things done to create the bill of materials. The transaction CS01 supports us by this task. Here you have to enter the name of the material which is supposed to have a BOM. Moreover the plant and the BOM Usage fields are required.

After that you get the following screen:

After you entered all components the bill of material is nearly complete. You may have wondered about the selection conditions we defined in our model earlier. Now it's time to apply them to each position in our bill of material. To do so, select the component and then choose the dependency assignment or editor via menu.

If you choose to use the editor then you create only a local dependency. The assignment functionality is for global dependencies. (see SAP Online Help - Variant Configuration for more detailed information). If you want to use global dependencies you need to create the dependencies in transaction cu01 first.

After we assigned all dependencies the bill of materials is completed. Now we have to create a configuration profile with the help of transaction: CU41. First you're asked to choose the configurable object to which you want to assign the profile.

Then you have to enter the name of the - in this case - material. After that you'll get the following dialog:

In the displayed list you can add some configuration profiles, while the priority of each profile depends on the position. (The lower the number the higher the priority). Besides the name of the profile you have to choose the class type of this configuration. In this case we have to choose class type 300 - the SAP standard class type for configurable classes. With double-clicking on the profile name you'll get to the configuration screen of the profile. Besides the basic data which are selfexplanatory you can set some other properties. For example you can choose the process which is indented for this material. Each process is explained in the F4-help. The next option BOM explosion - indicates how the bill of material is exploded in the sales order. If you choose "Sing-Level" or "Multi-Level" you have to set the application of the material and you are free to apply a filter.

Now all the settings were made and we can test the configuration. Test of the configuration You can simulate your configuration with the transaction CU50.

Enter the Name of the material and the plant and press F8. After that you can configure the material by means of the characteristics.

Then you can see the result bill of materials by clicking the marked button.

As a result we receive a bill of material according to the characteristics entered.

A material CYCLE is created as a configurable material with Gen. Item category group as 0004 and Item category group as ERLA. Also material CYCLE is a BOM material, which has sub items. Go to Transaction code: MM01. Do the following:

1. Basic Data 2 Screen: Set Material is Configurable Indicator 2. To determine item category TAC in sales order, maintain a suitable item category group such as 0002

3. 4. 5. 6.

MRP 2 View: Procurement type E: In house Production MRP 3 View: Strategy Group. 25: Make-to-order for configurable used for demo MRP3 View: Availability Check 02: Individual Requirement Classification view: Attach the variant class

Go to tab classification and select the class type Variants-300 as shown below.

Assign the class CYCLECLASS in the assignments area.

The class CYCLECLASS is created with the class type 300 (Variants) for the material cycle. Transaction Code: CL01.

Now maintain the characteristics as shown below in the screen shot. 1) CYCLETYRES 2) SYSTEM

3) CYCLEMODEL

4) CYCLEPRIZE

Now the characteristic CYCLETYRES was created with character format. Transaction Code: CT04.

Go to the values tab and maintain the characteristic values and description as per the requirement.

Now the characteristic SYSTEM was created with character format. Now Go to Transaction Code: CT04.

Go to the values tab and maintain the characteristic values and description as per the requirement.

Now the characteristic CYCLEMODEL was created with character format. Transaction Code: CT04.

Go to the values tab and maintain the characteristic values and description as per the requirement.

Now the characteristic CYCLEPRICE was created with character format. This characteristic is allowed for multiple values. Transaction Code: CT04.

Go to the additional data tab and maintain the table name as SDCOM (which links Sales and Distribution with Variant configuration) and field name as VKOND.

Now we have to maintain the dependencies for the class CYCLECLASS. The dependency CYCLEPRICE is created for the class. Go to dependency editor as shown below. Transaction Code: CU01.

Maintain the combination.

dependency

editor

for

pricing

the

material CYCLE based

on

the

required

Also we need to maintain the configuration profile for the material CYCLE. A configuration profile CYCLE is created for the material CYCLE and set the status as released. Go to Transaction Code: CU41.

The necessary settings need to be maintained for the configurable material CYCLE to explore in a sales order.

We have to create the variant conditions for the characteristics maintained in the class CYCLECLASS. Then go to configuration or press F8 as shown below. Transaction code: CU50.

Select one of the characteristics and go for its value and press the icon assign variant condition. Like wise we can maintain the variants for all the char. Values of the characteristics.

This is the variant as specified as medium range which should have the condition records maintained for VA00 and VA01.

Finally maintain the condition records for the condition VA00 by using the transaction code: VK11. The below specified conditions are active for the material CYCLE.

Now let us create a sales order. As the material is a BOM material it should explore with the sub-items and also should give us the screen to select the required material.

Press enter for the various characteristics of the material. As the material CYCLE is a configurable material, we can choose various options for the material as shown below.

The material CYCLE is exploded with the sub-items and the net value is directly calculated based on the variants maintained for condition type VA00.

The BOM components for material CYCLE are: Transaction Code: CS02. RIM, PEDDLE, TYRES are the sub-items for material CYCLE.

This is the complete overview of the variant configuration for a BOM material.

Material variant not configurable using SET processing multiKMATs

This question is Assumed Answered.

Duncan Brown
Jun 17, 2010 4:14 PM
Hi, How do I set up a material variant to allow configuration when used in a "SET processing" sales order? I have searched and read through SAP notes, forum threads, SAP-VC books without success to achieve this specific requirement, any help here is greatly appreciated. ECC6.0. The business model is MTO manufacturing. Background and working scenario: Using material variants (without type matching. All products are MTO). The material variant is configurable at point of order processing [VA01]. When the material variant is entered directly as a sales item the material is configurable and creates a production order. The material variant is fully linked to a KMAT superBOM. The item category of the material variant in MM data>sales = NORM the KMAT item category in MM data>sales = 0002 The sales order item category = TAN (material variant is configurable > this is OK) Problem scenario: The business now sells one material as a "system" (or SET) made of multiply material variants, requiring multi-line sales order entries each with individual production orders. Pricing etc required at component level, as if all items were entered separately. I can get the system working with KMATs within KMATs where the items at component level are configurable but not with material variants. I have a superior KMAT. MM data>sales item category = 0004. Configuration profile is set up for sales order (SET) process, multi-level BOM explosion and Application type SD01 for sales and distribution. The superior KMAT BOM is created with BOM usage 5 and all BOM components (material variants) have the relevant for sales indicator set in the BOM item detail. Additional info: The configuration profile of the KMAT for the material variants is set up for Order BOM process, multi-level BOM explosion Application type [customised copy of] PP01 Material type used for KMAT and material variants = FERT (with material is configurable indicator set only for KMATs) Super routings not used. Each material variant has its own individual task list (if this helps explain why we have configurable material variants)

Material variant (MV) is a 'configured' avatar of the configurable material. I am unable to understand why you are trying to go against fundamentals and make a MV 'configurable'. Even if a MV has its own task list, that does not qualify a MV to be configurable. I would stick to KMAT under KMAT BOM with variant matching and replacement and use Super Routing in addition. This is what I have seen working in even complex multi-level BOM scenarios in a IS-Mill situation. Hi Chandrasekhar Thanks for your reply. I understand KMAT under KMAT and using Super Routings is best practice and normally I do not go against SAP fundementals. Had this been a new implementation I would recommend this approach. Using configurable material variants as a direct item in the sales order does work and works well to suit the business processes and available data. Is it possible for configurable material variants to be configurable when used under KMAT BOM in SET processing? I can provide further details if required but in brief it was a compromise with the business to use configurable material variants (MV) based on time scale, resource, data and working in a live environment. There is a plan to use Super Routings but this project is scheduled end next year with production. When the data structure was designed the use of SET or system product processing was not in scope. All products are make-to-order. No stock units are used. On average each KMAT has 80 MV's with potentially 1000 variants possible for each MV so this is one reason why configuring the MV was chosen. Working in a live envirnoment with limited production data available changing to Super Routings would have delayed the original project objectives.