Variant Configuration Dependencies Types

Hi,
Gurus,
I know They are 5 dependencies types in Configurable Profile .But i want in which contest each one can be used with examples.? explaning each one with one examples?
PreCondition
Selection Condition,
Action,
Procedure,
Constraints
Looking forward
Thx,
Ragas
Edited by: Raga on Mar 20, 2009 11:49 PM
Edited by: Raga on Mar 20, 2009 11:51 PM

Hi Refer to following links for examples; examples are self explanatory if you know a little bit about class, characteristic, and how to write dependencies
1] for precondition example
a] for characteristic values:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
b] for characteristic
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
2] for selection condition example
a] For Bom items
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
b]For characteristic
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
3] for Procedure
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
4] For Action
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
Hope this will help you
Regards,
Mahesh

Similar Messages

Variant configuration class types

Hi Friends,
I have some questions on variant configuration class types
What is the difference among following class types?
1. 001 --- Material class
2. 023 -
Batch
3. 200-----Material (Configurable objects)
4. 300-----Variants
In which business scenario we can define above class type? Could you please explain with some example scenarios?
And also what is the difference between "Fully configured material" and "Configurable Material"
Valuable information in this regard is greatly appreciated.
Best Regards,
Krish

Hi Krish,
1. 001 --- Material class for general information of one material. It is fix information.
    Example : Tiles
    Class 001, characteristic : Size : 30 x 30, Color : White, etc
2. 023 -
Batch for goods receipt / production specific data
    Example : Tile
     Class 023, characteristic : Prod Date : 23.08.2011, Grade : First Grade, etc
3. 200-----Material (Configurable objects), For Configurable material (strategy in MRP 3 : 20, make to order type). In sales order we must define the characteristic of product customer as customer request.
   Example : Car
   Class 200, characteristic : AC : Yes / No, Tire : Upgrade / Standard, etc
   From Characteristic chosen in sales order will determine the BOM and Routing of production order. See Variant   Configuration topic for more detail.
4. 300-----Variants for material variant. We create material variant for configurable material. Value of characteristic is determine in material master.
    Example : Car Type 1
     Class 300, Characteristic ; AC : Yes, Tire : Upgrade
Hope it give you brief explanation.
Best Regards,
Arman Lie

Variant Configuration Dependencies

Hi VC Guru's
Can someone please detaile me about the usage of Different Dependencies in the Business.
Which Dependency to be used for what Business need.
Thanks
Kalyan

Hi,
You can refer to the help document from http://help.sap.com/saphelp_470/helpdata/en/92/58c228417011d189ec0000e81ddfac/frameset.htm
BR
Z.T

Process order with variant configuration material

Hi,
I create a process order for a material XX.
This material has a BOM with a material that has variant configuration "class type 300" for price configuration.
When I save the process order I get a message saying "There are still characteristics for components to evaluate". I dont want to evaluate this material in my process order.
What can I do to not have this message?
Regards.

Hi all,
Yes, I work with variant configuration. But sales orders are not involved.
What I do is:
1) I create a purchase order for material X (this material belongs to a BOM), this material has variant configuration. I give a value to the characteristics in the PO.
2) I create a process for a material XXX that has a BOM (material X is in the BOM and cannot be removed).
3) When I save the process order the system asks me to evaluate again the characteristics. This is what I dont want it to do.
Any ideas?
Regards.
Eduardo

Details about Master production Scheduling & Variant configuration

1) What are the steps for Master Production Scheduling (MPS)?
2) What are the steps for Variant Configuration?

Hi,
MPS:
With in your planning time fence (maintained in mat master ) , you will get firmed planned orders because your MRP Type P1 - P4 has firming type.
And the firmed planned orders will not change after next MRP run.
You have to set MRP Type p1 - p4. acc to firming type. in ur mat master.
Then run MPS .It is generally for important products and it is run single level.Because it will not change your procurement proposals as it has firming type.So you get effective planning for your imp products.
Variant configuration:
Go to mm01 create a material and in bd2 view mark the check box material is configurable and then save the material and go to ct04 create chara.
Go to cl01 and create class with class type 300 and assign the charac. to it
Go to tcode cu41 create the profile using material code and assign the class to it
then got tcode mm02 and assign the profile there
Variant configuration material type is KMAT (SAP std), u can use this material type alternately u can mark the indicator in basic data 2 view ->client specific configuration->Material is configurable tick.
For further reference, check the link below
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf

Variant Configuration Dependency Language

Does anyone know a good reference to use when writing Variant Configuration Dependencies? I am interested in command syntax as well as structure of the dependency program.

For syntax reference you'll just have to use the SAP material. A google search will also provide some links with OD (Object dependency) examples.
As far as structure, if you mean line, character - spacing, there's nothing. Just structure so it is as readable as possible. If I have multiple AND / OR's I will break them into separate lines and use the ( ) a lot to ensure the statement's are interpreted correctly.

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

Positional Dependencies in Variant Configuration

Hi all,
Is it possible to implement positional dependencies in Variant Configuration?
We want to design the configurable material (e.g: Rack) by deciding where and how many of the components go into creating the rack.
We have to implement dependencies which restrict the position where the component can be placed in the rack and depending on where the component is placed, modify the length of a different component.
Thank you for your help

Hi Nirmal,
In your case , Position of component is Variant, so create "Component _Position" as one Characteristics and assign the value (For Ex top, middle bottom).
create Dependencies formula for selection condition at Component assigned in super BOM. Based on the char - position value, component will be selected.
Regards
Pradeep

Pulling Variant Configurator's object dependencies

hello friends
could someone please let me know if there are any BAPIs that can pull VC's object dependencies.
Any comments or feedback on this will be highly appreciated.
Thanks
Ram

All the function modules below are related to object dependency and variant configurations. Please reward points is useful
CARD_CLASS_CHAR_READ_ALLOC
CARD_CLASS_CHAR_READ_DEP
CARD_CLASS_CHAR_VAL_READ_ALLOC
CARD_CLASS_CHAR_VAL_READ_DEP
CARD_CLASS_READ
CARD_CLASS_READ_ALLOC
CARD_CLASS_READ_ATTR
CARD_CLASS_READ_CHARACTS
CARD_CLASS_READ_DEP
CARD_CHARACTERISTIC_READ
CARD_CHAR_READ_ALLOC
CARD_CHAR_READ_ALLOC_CLASS
CARD_CHAR_READ_DEP
CARD_CHAR_VAL_READ_ALLOC
CARD_CHAR_VAL_READ_DEP
CARD_CNET_CONSTRAINT_READ
CARD_CONSTRAINT_NET_READ
CARD_CON_PROFILE_READ
CARD_TABLE_SELECT_LINES
CARD_DEPENDENCY_READ
CARD_GET_ALL_DEPENDENCIES
CARD_FUNCTION_READ
CARD_TABLE_READ_ENTRIES
CARD_TABLE_READ_STRUCTURE

Variant Configuration and Dependencies?

Hi,
How is variant configuration is used and dependencies? Can someone give the step by step details with an example? What are the sample questions that can be asked about variant configuration in the interview?
Thank you

Hi Altin,
The process of Variant Configuration and its dependency uses defers from scenario to scenario,
Please click on the Link
http://help.sap.com/saphelp_erp60_sp/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
or refer to SAP PLM 145 or LO990.
To check an end user documentation of how to create Knowledge base objects of Variant Configuration
please refer to link
service.sap.com/var_conf or https://websmp202.sap-ag.de/var_conf
This link should explain different strategies and scenarios where Variant Configuration is used.
If you have access to SAP IDES systems:
USE models T-VPP00 for Sales BOM and T-VPC00 for regular.
Need more help please let me know
Thanks
Ajay

Why don't we do the confirmation in variant configuration?

Hello guys,
As far as i know that in variant configuration we don't do the confirmation, we directly do the goods receipt.Is it right?If yes than why?
Following are the steps we do while doing the variant configuration scenario:
1)First we create the characteristics and give the values inside it.
2)Then we create the class of class type 200 and give characteristics defined in it.
3)Then we create the variant of class type 300 and give all the characteristics inside it.
4)Now we create the configurable material with Basic data 1,2, MRP 1,2,3,4 , Classification view ,workscheduling view.
In classification view, we give the variant of class type 300.So it shows all the characteristics and its value over there.There we select all the values.
5)Now we create the super bom of configurable material and in class tab we give all the classes of class type 200.Here even we can maintain the dependencies if we define all the characteristics value in item tab.
6)Then we create the super routing and inside it we give all the possible operations inside it.Right now my routing contains operations which are necessary all the times.
7)Then we create the configurable profile for configurable material of class type 300.
8)Now we give the requirement in md81 for configurable material and there we select the characteristics values which we want.
9)After that we run the mrp for configurable material and it generates procurement proposals(planned order) for it.
10) Afer this we convert this planned order into production order and release it and save it.
11) After this we do the goods receipt for the production order in mb31.Because of this it shows the stock of sales order as production order qty.
This procedure my tutor has taught me.Have i missed any steps or am i wrong somewhere?If that the case than plz guide me.

if you can generate a production order then you can always confirm it according to SAP PP logic.
we use variant configuration for the manufacturing of complex products. once the component quantities and
operation are selected for a particular variant and copied to Production order, the rest of the process is same
as normal Production Control. Revert back with any queries you have.
Regards,

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.

Purchase of variant configuration material from external source

Hi,
I am working with variant configuration scenario , Here some material procured from external source and per characteristics requirements , these characteristics have varied price , these price should be maintain at condition level .
The Material purchases from external source its price according to characteristic select.
Pl helps me how these scenario resolve.

H Rajesh,
1.Create another New characteristic called ZPrice .Give the description and go directly to Addnl Data Tab.Here in the table name Enter "MMCOM" and in the Field Name Enter "VKOND" at CT04 & save .
2.Now Goto CT04 in change mode, for Zprice Go to values tab and select RED &.Goto Extras-> Object Dependencies->Editor and then select Procedure & define condition.
3. Goto Inforecord Choose Extras ->Variant conditions.
Enter a variant key. Choose the desired condition type and specify the period during which the discounts and surcharges are to apply.
Enter the amount and save.
For More help please Refer Below SAP link
[Variant Configuration |http://help.sap.com/saphelp_47x200/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm]
Regards
Pradeep
Edited by: Pradeep Kumar on Mar 4, 2008 10:36 AM
Edited by: Pradeep Kumar on Mar 4, 2008 10:37 AM

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.

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.

Variant Configuration Dependencies Types

Similar Messages

Maybe you are looking for