Variant Configuration $Root $Parent $Self

Hi Gurus
Please help in providing information on Variant Configuration $Root $Parent $Self, and if possible with some test cases..to make it as a base for exploring.
Thanks in advance.
Points will be rewarded.
Regards
Suddu

Dear Suddu,
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
<a href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
The procedure is as follows:
Create a Material - KMAT type with Item category (002)
Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
Regards,
Naveen.

Similar Messages

Class & Characteristics in variant configuration

Hi PP guru's
Pl explain me in detail all the configuration path , spro , tcode for the above said .
thanx in advance
Regards,
Vimalbalaji

Dear Vimalbalaji,
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
The procedure is as follows:
Create a Material - KMAT type with Item category (002)
Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
<a href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
Regards,
Naveen.

Re:Variant Configuration

Dear All,
                I am able to do variant configuration to some materials, by wrirting source code, but if the characteristics are more how can I combat the problem ?

The variant function can be defined to solve the complex dependencies with a lot o calculation, cases, and requirements. For variant table, it is a simple lookup table that you can define in order to map one or more characteristics to one characteristics.
E.g., the width of the product is defined by characteristics A, and B. You can create variant table using A and B as the key characteristics and width is the outcome (CU61 to define the structure, CU60 to create the lookup table). You can use the code in obj.dependencies like this:
table Zvariant_table ( A = $root.A,
                                          B = $root.B,
                                       width = $self.width)
(note that the obj. dependencies type is procedure)
For me, it is not eliminating the variant function. It is really depends on your requirement.

HI Gurus Reg - Variant Configuration

HI gurus
Can any body explain the
$parent, $root, $ self
and how to use that
documents i have checked and of not that much help ful
thanks in advance
Rajesh

Hi Rajesh,
These all are Object Variables:
Object Variables
You use object variables in a multi-level configuration, to describe configurable materials in a configuration structure.
You can use the following object variables:
u2022 $ROOT is the highest-level configurable material in a configuration
u2022 $SELF is the material to which the dependency is allocated
The material to which an action or procedure is allocated is the same material for which values are inferred by the action or procedure. To make it clear that actions and procedures only infer values for materials to which they are allocated, the characteristics are preceded by the variable $SELF.
In dependencies that are allocated directly to the header material, $SELF and $ROOT both mean the header material.
u2022 $PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
However, in a multi-level, interactive configuration $ROOT may refer to two different objects:
u2022 If the BOM is exploded in production, $ROOT always refers to the material that transfers requirements.
u2022 If the BOM is relevant to sales and distribution, $ROOT always refers to the header material.
Hope it helps!
Preethi

Variant configuration-- syntax error in creation of object dependencies

In variant configuration when i try to create object dependency (tcode=cu01), after entering the dependency and also description when i enter the syntax in the source code it is giving error: error in syntax check for simple condition
I have entered syntax as : engine_cap in ('1000','1400','2000'), pls guide me with the solution to create object dependency

Dear, Shakeer
Please follow along with my very own config guide of variant config.
1)     Create a configurable Material Using KMAT u2013Material Type. Item Category 0002 and Item Category Group 0002. Go to classification tab-here you maintain the class type 300 and assign the class, we will create this shortly. (So after creating class come back into MM02 and input the class that you create in step 2.)
2)     Create a class in T-Code CL01. Use class type 300 for Variants. In this we assign the characteristics we will create shortly.
3)     Create characteristics in T-Code CT04. Create your characteristic like for example, Z_Type, Z_Model, and Z_Color.
4)     We must create a characteristic for the pricing. Example, Z_CarPrice inside this characteristic we must maintain. Table Name SDCOM, Field Name VKOND in the additional data tab. Also, go to restrictions tab and enter the class type 300 Variants. Now in order to make this pricing work for you, you must maintain (enter) all the values from the characteristics. For example, Red, Blue, Black, Honda, Toyota, GLI, XLI, and 2.0D.
5)     Now going back to the characteristics in CT04 change mode. Make sure Basic Data has *Multiple Selections circled. * Character Format has 26 and a check in case sensitive. Make sure in restrictions tab class type 300 Variants is present. Go back to Values and highlight the first one. Example, Red then go to Extras->Object Dependencies->Assignments You must maintain this code $self.Z_CarPrice=u2019Redu2019 in basic data make sure itu2019s released & procedure is filled in. Go back to dependency editor and paste the same code there after 000010 $self.Z_CarPrice=u2019Redu2019 and do this for each and every value. Very Important * Maintain configuration profile in T-Code CU41 for the material -> Priority 01, Variant Configuration, Class 300, status, Released 1, then click save. Note: If 2 conditions are inactive use class group A instead of B in SPRO for Condition type VA00.
6)     Go to T-Code VK11 and enter VA00 condition type. Enter all the values maintained in the characteristics for example, Red, Blue, Black, Toyota, Etc and enter the price then click on save. Now it should work fine in VA01. Make sure you have assigned the VA00 condition type in the pricing procedure.
Good Luck,
Muhammad Ali Lozada

Sales Order text for Variant Configuration

Hello
I have researched my issue and also have asked other peers for guidance. I feel that I am really close to getting my issue to work but I am not sure what I am missing, so I am hoping that someone can give me some advice as to what to check please. See below for the description.
My issue is in reference to SD Variant Configuration and is outlined below.
Overview
Main Unit is a radio test set
Test set can have an upgraded software
Example
Model 6015 u2013 standard test set
Model 6015T u2013 Upgraded software test set
Model 6015V u2013 Upgraded Software + test Set
Requirement
Use same Material Number using Variant Configuration for the upgrades
Price is to default to the Upgraded price
NOTE:
Our materials are already established and are set up as material type Finished Goods; ERLA item category; sales order item category is a copy of TAC. I am using a Configurable Material type KMAT, item category 0002 and linking to the FG material item category ERLA in the material master.
I have created the Material Variant (KMAT) in MM01
Created the characteristic in CT04
Created Classification in MM02 for material FG
Created Super BOM for Configurable Material in CS01 and added the upgrades as Alt Bom 2 for upgrade and 3 for Upgrade+. Also added the Alt BOM text
Created Profile of configurable material in CU41
For the Material I added the configurable material to MRP 3 screen in MM02
Created the BOM link in CS40
I simulate the material in CU50. I enter my material; select the icon for configuration, I can see the characteristic Value Assignment nad see my characteristics Description. I go to the value and use the drop down I then see the pop up of all the different values.
I have created Characteristic Reference VCSD_UPDATE_ARKTX with table VCSD_UPDATE and field ARKTX - no values
I have created a characteristic Test_Choice with the 2 values one is Test Upgrade 1 and the other is Test Upgrade 2. Both of these have the description as well.
For Material Text:
I have set up a reference characteristic using 30 character format (named VCSD_UPDATE_ARKTX),
with table name VCSD_UPDATE and field name ARKTX.
Then in the Configuration Profile(CU42) for configurable material, added a procedure(named PR_PRODUCT_DESCRIPTION) to the dependencies which contains code that sets the description
$self.VCSD_UPDATE_ARKTX = ''Test Upgrade 1u201D
If $self.TEST_CHOICE = Test_Upgrade_1,
$self.VCSD_UPDATE_ARKTX = ''Test Upgrade 2u201D
If $self.TEST_CHOICE = Test_Upgrade_2,
When Entering the sales order for Material Number XXXXXX, I receive a pop up that I can select which Alternate BOM (from CS02) I would like. I select my line item and then select the configuration icon at the bottom of the sales order. I see again my characterestics values (the same as CU50) but am unable to select the radio button. Not sure if this part is standard. Still no change in the sales order line item. I have validated that I am using a copy of the standard TAC item category. How does the text change to the correct value? Am I missing a seeting somewhere. Please provide any guidance with this as I have been trying to get this to work for over a month.
Thank you for your time. It is greatly appreciated.

I have figured out that this will work if I go to the standard material (it is not KMAT but it is a FERT material type) and set the flag in the Material Master Basic Data 2 tab that this is a configurable material and not use KMAT material type for a super BOM. The text changes for this scenario so it give me hope.
This is not ideal, as I want to use the Super BOM because there are different variations (non stock items) that I need to pull through on the picking list in order to tell the end user which option needs to be loaded in the standard material. At least I know the text can change on the sales order; but I am still struggling with the use of the super BOM and changing the sales text when there is use of a super bom as you tie that to the MRP 3 screen of the FERT material type. I can set everything up, but the text will not change if I set up the material master this way. Guidance is appreciated.
Example
Material 72433 (FERT)
on sales order I enter 72433, my alternate BOM comes up with different Options. Alternate BOM 1 is standard configuration; My Alternate BOM 2 has Option 3 and 4 while alternate BOM 3 has option 5 and 6. Alternate BOM 2 is a 6015T and Alternate BOM 3 is a 6015V.
I want my sales order to pull through the text of 6015T or 6015V, whichever is chosen. I want my picklist to print out the option that was selected.

How to create Variant Configuration Material Master in SAP PP

Dear Friend's,
Pl 's guide me for How to Create Variant Configuration Material Master.
Give me step by step procedure for Creation of Variant Configuration.If some of you having screen shots for the same with one Example, that will be a very helpful to me for creating VC.
Thanks & Regards,
Sandeep N.Theurkar

Hi,
Eg: Ford car.If a sale order is raised for fiesta lxi model the system should choose red colour & for vxi blue colour respectively.
ie you need to define the characteristic and assign the values .
This characteristic need to assigned to class.
class need to be assigned to material master
1. T.code : CT04(characteristic) FORD_MODEL, Choose single value & entry required tab & give the input as 01 - fiesta_lxi & 02 - fiesta_vxi.( characteristic values)
2.Tcode: CT04, FORD_BODY( another characteristic)
Choose single value , don't click entry required.
01 - Red( characteristic values)
02- Blue
3. Create class T.code : CL02
fiesta_class
type : 300
4. OBJECT DEPENDENCY:
T.CODE : CT04
FORD_MODEL
CLICK VALUES TAB,
IN FIESTA_LXI CLICK THE 'O' meant for Obj dependency, action & extra.
Edit the dependecy,
010 $Self.ford_body = '01'. & save
Repeat the same for FIEST_VXI & instead of '01' give '02' for blue colour.
, then create a ROH as ford_body. & a KMAT material for the car. .
Then create a Super BOM with usage 3 & give component as ford_body
Then use T.code cu41 (Create config profile)
enter a profile name & class 300 & choose class assignment, choose fiest_class ,
Use T.code cu50 to check the values.
Then create a sale order.
Pl. reward if helpful.
Regards,
nandha

To access a package, the calling class must reside in the root/parent direc

My goal was to be able to access my package from anywhere within the
high level root folder (d:\zJava). But it seems the invoking class MUST
RESIDE IN THE TOP LEVEL PARENT DIRECTORY of the package. Was Java
designed to behave this way?
D:\zJava\zsamples\com\zswingpackage1> <-- packages successfully compiled here
 swing_optgrp_eg1.{class/java}
 package com.zswingpackage1;
 public class swing_optgrp_eg1 extends JFrame implements ItemListener {
D:\zJava\zsamples\com> <-- classes residing here could NOT successfully access the package 'com.zswingpackage1'. The third level subfolder is 'com'.
 package_test4.java
 /* Following import stmt. causing RUN-TIME error "Exception in thread "main" java.lang.NoClassDefFoundError: com/zswingpackage1/swing_optgrp_eg1". */
 import com.zswingpackage1;
 Package_Test4.class
 /* Unsuccessful remedies:
 i) D:\zJava\zsamples\com>java Package_Test4
 -classpath .;d:\zJava\zsamples\com\zswingpackage1
 -classpath .;d:\zJava\zsamples\com
 -classpath .;d:\zJava\zsamples (also used in compile)
 -classpath .;d:\zJava
 ii) ran from the root/parent directory of the package d:\zJava\zsamples),with and without classpath i.e.
 D:\zJava\zsamples>java com\Package_Test4 [-classpath .;d:\zJava\zsamples]
 iii) ran from the top level directory (d:\zJava), with and without classpath i.e.
 D:\zJava>java zsamples\com\Package_Test4 [-classpath .;d:\zJava\zsamples]
 Possible causes:
 - maybe the above behaviours are by design i.e. the calling class/program CANNOT be stored within the package hierarchy?
D:\zJava\zsamples\net> <-- classes residing here could NOT successfully access the package 'com.zswingpackage1'. The third level subfolder is 'net'.
 package-test6.java
 /* Following import stmt. causing RUN-TIME error "Exception in thread "main" java.lang.NoClassDefFoundError: com/zswingpackage1/swing_optgrp_eg1". */
 import com.zswingpackage1;
 Package_Test6.class
 /* Unsuccessful remedies:
 i) D:\zJava\zsamples\net>java Package_Test6
 -classpath .;d:\zJava\zsamples\com\zswingpackage1
 -classpath .;d:\zJava\zsamples\com
 -classpath .;d:\zJava\zsamples (also used in compile)
 -classpath .;d:\zJava
 ii) ran from the root/parent directory of the package (d:\zJava\zsamples), with and without classpath i.e.
 D:\zJava\zsamples>java net\Package_Test6 [-classpath .;d:\zJava\zsamples]
 iii) ran from the top level directory (d:\zJava), with and without classpath i.e.
 D:\zJava>java zsamples\net\Package_Test6 [-classpath .;d:\zJava\zsamples]
 Possible causes:
 - maybe the above behaviours are by design i.e. the calling class/program MUST be stored in the parent folder of the package hierarchy?
**D:\zJava\zsamples> <-- classes residing here SUCCESSFULLY accessed package 'com.zswingpackage1'. NO -classpath parms. were necessary!
D:\zJava\ <-- classes residing here could NOT successfully access the package 'com.zswingpackage1'. Similar scenarios as above.
D:\zJavaB\ <-- classes residing here could NOT successfully access the package 'com.zswingpackage1'. I purposely created another folder with the 'B' suffix. Similar scenarios as above.
My PC configuration:
 java version "1.4.0_01"
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
 Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
 JRun 4 (Build 47304)
 WinNT 4.0 SP5
 IE 5.50
 CLASSPATH=.;D:\jakarta-tomcat-3.3.1\lib\common\servlet.jar;
 C:\JRun4\servers\default\default-ear\default-war\WEB-INF\classes
 JAVA_HOME=C:\j2sdk1.4.0_01
 Path=C:\j2sdk1.4.0_01\bin;C:\WINNT\system32;C:\WINNT;
 C:\Program Files\Network Associates\PGPNT;C:\Program Files\MTS;d:\MSSQL7\BINN
Thank you so much for your expertise.

Hello,
I think that you use the import-declarations incorrectly.
Your code says:
import com.zswingpackage1;
... The meaning of the above declaration is the following: Import the class "zswingpackage1" from the package "com". The compiler cannot find that class, but it is probably never asked to find it in your code, so it won't report an error.
If you want to import the whole package use the following declaration instead:
import com.zswingpackage1.*;
... That means: import all classes from from the package "com.zswingpackage1".
You can also import just the classes needed, e.g.:
import com.zswingpackage1.swing_optgrp_eg1;
... I hope that does the job.
Søren

Variant Configuration Problem

Dear SAP Friends,
I have created VC including everything necessary. I have created the Sales Order also with the necessary Variant created. But I am not able to deliver as in the availability Check it has taken as per the below:
Avail Check = 01 and Checking Rule = AE
The MRP element is showing SimReq i.e. Simulated requirements.
I have not created any BOM. I have created Material with KMAT and Configurable Profile, Characteristics, Class etc.
How can I create the Super BOM with my Configurable Material (Number is 1479) as this Material Item category group is 0002 pricing at header level. But in the BOM (Tr. Code CS01), I have to give the item category group as ERLA.
My Class is ZHONDA, Characterics are ZCOL and ZCC.
I have created Variant as "RED100" for the Car and this Variant is not a Material. I am a bit confused. I did not find any suitable answer from the past thread.
Please help to solve this problem.
Regards,
Jans

Dear Jans,
Some light on Variant Configuration in Detail.
Follow these steps do the configuration:
-->Create a Material - KMAT type with Item category (002) ·
-->Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
-->Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for) ·
-->Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
-->Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
-->Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save ·
-->Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save) · Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save ·
-->Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save) ·
-->Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
I hope this will help you,
Regards,
Murali.

Steps for Variant Configuration

Hi Gurus,
Can any body tell me step by step procedure for variant configuration.
My e-mail id. <REMOVED>
Regds.......
Sumit

Hi Sumit,
Variant configuration is for manufacturing complex products. The manufacturer always has 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.
Procedure -
Create a Material - KMAT type with Item category (002)
Create Characteristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
Assign these two characteristics to a Class in CL01 - ZBikeclass (Type 300) in characteristics tab page.
Then go to CU41 Configuration profile select the material and enter the description click on the class assignment i.e. assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now go to VK11 - Enter VA00 (Condition) (For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
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.
Integration
Variant configuration is integrated in the following applications:
a.. CA Classification
b.. LO Material Master
c.. PP Bill of Material
d.. PP Routings
e.. PP-PI Master Recipes
f.. SD Sales
g.. SD Conditions
h.. MM Purchasing
i.. CO Costing
j.. PP Material Requirements Planning (MRP)
k.. PP Production Orders
You can configure the following objects:
a.. Materials
b.. Standard networks in the Project System.
c.. PM General maintenance task lists
d.. Model service specifications
Features
You do not need to create a separate material for each variant of a product in your
company. You can use one configurable material to cover all variants. You create a
super BOM and a super routing for this material, containing all the components and
operations for producing all variants of the product.
To define the features of a configurable material, you use characteristics. To
enable you to use characteristics to configure a material, you assign the material
to a class of class type 300. Possible characteristics of a car, for example, are
model, country, color, and engine. The customer can choose from among different
options for each characteristic (values).
The only limitations are combinations of features that are not possible for either
technical or marketing reasons. You cannot combine all types of car engine with all
types of transmission, for example, or certain types of upholstery are only
available for more expensive models. In Variant Configuration, you use dependencies
to control this. This prevents combinations of options that are not allowed.
Dependencies also select exactly the right BOM components and operations to produce
a variant.
Each configurable object must have a configuration profile. The configuration
profile for a material controls the configuration process in the sales order.
You can make the price of a variant dependent on the characteristic values assigned
(Pricing). You can use variant conditions to define surcharges and discounts for a
variant.
For variants that are required frequently, you can create material variants, which
can be produced without a sales order and kept in stock. When you receive a sales
order, you can check whether the variant required is in stock, so that you can
deliver immediately.
Pl go thr below links:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
http://sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Copying Variant Configuration across sales order items

Hi,
We are working with SAP 4.7.
I have a requirement to default the variant configuration values entered within line 1 of the sales order entry process on to subsequent lines. i.e. defaulting initial values for the configuration.
Our users have to enter many variant line items on a sales order and within an individual order the variant characteristics will be very similar, therefore by defaulting these values to be the same as the previously entered line would be a considerable overhead saving.
However I am having difficulty accessing the variant values which have been entered in the first line item. I have looked at userexit_move_workarea_to_sdwa and userexit_get_field_from_sdcom, however I don't know if I am heading in the right direction. Any advice appreciated.
Thanks for your time.

We are doing this with main-positions and subpositions. The sales clerk enters the main Position with all the characteristics, switches to the tab "Fast data entry" types in the main position, he wants to copy from and the material. There is a dependency which calls a function module which does the real work.
This works with 4.6B in 4.7 there is a psotion type global position which acts similiar.
Ok, now the code:
Dependency
pfunction Z_SD_WERTE_CHARACTERICS
(SD_VBAP_UEPOS         = SD_VBAP_UEPOS,
   STAERKE           = $self.STAERKE,
   BREITE              = $self.BREITE)
/code
CALL FUNCTION 'Z_SD_INHERITANCE'
     EXPORTING
          GLOBALS        = globals
     TABLES
          QUERY          = query
          MATCH          = match
     EXCEPTIONS
          FAIL           = 1
          INTERNAL_ERROR = 2
          OTHERS         = 3
/code
Z_SD_INHERITANCE
DATA: h_uepos LIKE vbap-uepos.
DATA: x_values TYPE ibco2_value_rec OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS:
-values.
    ENDLOOP.
ENDIF.
*-- Ausgabeverarbeitung
LOOP AT match WHERE atcio = 'O'.
*-- Konvertierung ATINN auf ATNAM
    SELECT SINGLE * FROM cabn WHERE atnam = match-varnam.
    CHECK sy-subrc EQ '0'.
    READ TABLE x_values WITH KEY atinn = cabn-atinn.
    IF     sy-subrc IS INITIAL AND
       NOT x_values-atwrt IS INITIAL.
      match-atwrt = x_values-atwrt.
    ELSEIF sy-subrc IS INITIAL AND
       NOT x_values-atflv IS INITIAL.
      match-atflv = x_values-atflv.
    ENDIF.
    match-atfor = cabn-atfor.
    MODIFY match.
ENDLOOP.
ENDFUNCTION.
/code
Kind regards
Matthias Kabel

Need help on variant configuration

Hi Guru,
Here we need to use variant configuration.But i am new in variant configuration.Can somebody tell me the different steps of variant configuration from PP side.I have gone through standard document. But still i need this information. The Industry in which I am going to implement this,is producing Colored, profiled sheet to provide roofing solution.The metal roofing sheet can have different profile, different colour, different thickness, different width and so on.They have nearly three thousand of different combination.
Please respond.
Regards
Rajib

Hi,
Pls. find herewith Variant Configuration Procedure steps as below
VARIANT CONFIGURATION:
1.Create a Material - KMAT type with Item category (002)
2.Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for).
3.Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
4Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
5Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save.
6.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
7.Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save.
8.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
9.Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
Variant Configuration: Complete Maintenance:
Technical name: SAP_LO_VC_MAINTAIN
Tasks
The variant configuration processor sets up the rules for multi-variant products and maintains them in the database. He or she simulates and executes the configuration. This role is required wherever variant configuration is used.
The complete model also contains sales order processing (VA01/VA02), and the connection to SCE/Internet Sales and Mobile Sales.
Activities in Variant Configuration;
Transaction
Activity
CC04
Display product structure
CWBPP
Engineering Workbench
Variant Configuration
VA01
Create sales order
VA02
Change sales order
VA03
Display sales order
CU51
Maintain configurable order BOM (multilevel)
CU52
Maintain configurable order BOM (single level)
CU50
Configuration simulation
CU80
Reporting functions for characteristics and values
Configured Objects
CU44
Material
CU45
Standard network
Assignment of Configured Materials
CS40
Create assignment for configured material
CS41
Change assignment for configured material
CS42
Display assignment for configured material
Configuration Profile
CU41
Create configuration profile
CU42
Change configuration profile
CU43
Display configuration profile
Dependencies: Single Dependency
CU01
Create single dependency
CU02
Change single dependency
CU03
Display single dependency
Dependencies: Dependency Net
CU21
Create dependency net
CU22
Change dependency net
CU23
Display dependency net
Dependencies: General
CU05
Dependency where-used list
CU04
Dependency list
Tools: Variant Function
CU65
Create function
CU66
Change function
CU67
Display function
CU68
List functions
Variant Table Structure
CU61
Create variant table
CU62
Change variant table
CU63
Display variant table
CU64
List variant tables
Variant Table Contents
CU60
Maintain variant table contents
CU59
Transfer variant table contents to database table
Knowledge Base for SCE: Knowledge-Base Object
CU31
Create knowledge-base object
CU32
Change knowledge-base object
CU33
Display knowledge-base object
Runtime Version
CU34
Create runtime version
CU35
Change runtime version
CU36
Display/export runtime version
CU37
Create SCE database schema on PC
For complete details of Variant Configuration go to the following link :
http://help.sap.com/erp2005_ehp_03/helpdata/EN/96/468f38721f9977e10000009b38f842/frameset.htm
Hope this helps.
Regards,
Prakash

SD Variant Configuration - characteristic value computation

Hi Everyone
Greetings from Vinod
i am creating a variant material which has 3 characteristics. out of the 3 characteristics, 2 are inputed by the user and the third characteristic needs to be populated with the difference of the 2 chatacteristic values that we have entered before. is there a standard setting that we have to maintain, or should we do a custom development on the same. the third characteristic value which is computed based on the difference of the precious two characteristic will then derive pricing of the variant material. please throw some suggestions and inputs in this discussion.

Hi,
calculating values of characteristics is done with so-called dependencies.
In a dependency you can define the rule how a value should be calculated.
You have to create a class of class type 300 and assign your characteristics to this class.
Assign the class to a material of material type "Configurable Materials".
Open the material with transaction PMEVC (Modeling Environment for Variant Configuration).
There you maintain a dependency of type procedure.
The source code may look like this for your example:
$SELF.CHARACTERISTIC_3 = CHARACTERISTICS_1 - CHARACTERISTIC_2
You can find details for variant configuration on help.sap.com:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
Details on transaction PMEVC (Modeling Environment for Variant Configuration):
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Modeling Environment for Variant Configuration
Information on dependencies:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Dependencies
and
-> Dependency Syntax: General Rules
Best regards,
Sebastian

Variant configuration question????

Hi gurus,
I have done variant configuration. Created a configurable material, created class and characteristics.
E.g. My configurable material is a door. The characteristics are Colour/Size/Type etc.
The values are: Colour:Green/Red - Size:2m/2.5m(wood) - Type: Small/big
I want to order from suppliers Red colour, Green colour, wood etc and keep them in stock.
How can I connect values with materials Red colour, Green colour etc in order to reduce their stock every time a Sales Order takes place????
How can I say for example that Green reduces 2kg and Red 3kg of the stocked colours? or for example the small wood 2 square m /the big 3 sqm?????etc
I do not want to use PP and MRP...I do not want a Production order to be created for every Sales order, I want for Every Sales Order the Stock of raw materials to be reduced..
Thank you in advance.

Hi Theodoros
Steps for Variant Configuration in SD
Some light on Variant Configuration in Detail.
Generally, in SD variant is effectively used for pricing for variant. The following configuration with example will be able to assist you in same regard.
The procedure is as follows:
u2022 Create a Material - KMAT as Material Type with Item Category - 002 by using TCode MM02
u2022 Create Charateristics using TCode CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
u2022 Create another Characteristics using TCode CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
u2022 Assign these two characteristics to a Class using TCode CL01 - ZBikeclass (Type 300) in characteristics tab page.
u2022 Then go to Configuration Profile using TCode CU41 select the material and enter the description click on the Class assignment, i.e., assign Zbikclass.
u2022 Now go back to Characteristic using TCode CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
u2022 Now go back go to Extras - Other Dependencies - Assignments and Assign relationship ( by default it will come just save)
u2022 Now select Blue- go to Extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
u2022 Now go back go to Extras - Other Dependencies - Assignments and Assign relationship ( by default it will come just save)
u2022 Now go to Condition Record using TCode VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
u2022 Activate the variant configuration in Sales Document make the above effective or in use.
Hope this helps you

Variant Configuration & Incompletion procedures

Hi all,
2 questions :
1. can u tell me about Variant Configuration ?
2. Importance & Steps in Incompletion procedures . My id : [email protected]
regards
Rajarshi

Hi,
These are the steps for variant configuratio
Eg: Ford car.If a sale order is raised for fiesta lxi model the system should choose red colour & for vxi blue colour respectively.
ie you need to define the characteristic and assign the values .
This characteristic need to assigned to class.
class need to be assigned to material master
1. T.code : CT04(characteristic) FORD_MODEL, Choose single value & entry required tab & give the input as 01 - fiesta_lxi & 02 - fiesta_vxi.( characteristic values)
2.Tcode: CT04, FORD_BODY( another characteristic)
Choose single value , don't click entry required.
01 - Red( characteristic values)
02- Blue
3. Create class T.code : CL02
fiesta_class
type : 300
4. OBJECT DEPENDENCY:
T.CODE : CT04
FORD_MODEL
CLICK VALUES TAB,
IN FIESTA_LXI CLICK THE 'O' meant for Obj dependency, action & extra.
Edit the dependecy,
010 $Self.ford_body = '01'. & save
Repeat the same for FIEST_VXI & instead of '01' give '02' for blue colour.
, then create a ROH as ford_body. & a KMAT material for the car. .
Then create a Super BOM with usage 3 & give component as ford_body
Then use T.code cu41 (Create config profile)
enter a profile name & class 300 & choose class assignment, choose fiest_class ,
Use T.code cu50 to check the values.
Then create a sale order.
Pl. reward if helpful.
Regards,
nandha

Variant Configuration $Root $Parent $Self

Similar Messages

Maybe you are looking for