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

Similar Messages

Variant configuration on planned orders, missing dependencies rules

Dear Gurus,
I`m facing a strange situation here. After MRP run, de material is corrected explode, but is not considering a procedure in a specific dependency rule. Instead of making the correct UoM calculation for convertion, the system is just considering the dimension of the item, and not the formula on the dependency rule.
If I simulate the process under CU50, the explotion works fine, but, on planned order creation, the information is completely wrong.
If does anyone have a clue on this, I`ll be glad to to give some points.
Kind regards to all
Oliver Formicola

Hi Oliver.
where is this OD assigned. Is it on the header level or lower level ? There is a restriction when it comes to MRP.
When you create a planned order (MD11) the items are configured ie object dependencies are run only the ones attached to the items, the od's assigned the profile arenot run. Additionally , please review note 546516 that has explaination on the fields if you are using.
Please provide more explaination if that doesnot help
Thanks
Amber

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

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-- 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

ECM - Variant Configuration - Disable for specific Object?

Once we use change number for a material and Configuration profile, the change number will be mandatory field. This also occurs for CU02 - Object Dependencies, CL02 - Classification, CU60 Variant Tables and CT04 Characteristics.
We know this is a crazy question to some that have strict controls, but we would like to remove the requirement for some materials & configuration that no longer require engineering change management. Has someone experience something similar or implemented a configuration change that would fulfill our requirements?
Reading through the process documents, I believe it is not possible. But I thought I would check with the global experts on this matter.
Best Regards and Thank you for your feedback,
Ed

Hi,
I would suggest you better go with the authorization control for the same. Beacuse by that way you will be alble to meet your requirement up to some extend but by this way as you are asking, there is crezy in true mean as you wrightly said.
Regards,
Shyamal

Events on objects of variant configuration, like class, characteristic,...

Hello,
objects of classification of variants like BUS1088, BUS1003, object dependencies,
... have no events. I tried to add events to those events but there are no change document objects or status objects I could find to define my own events. Has anybody an idea how to react on changes in the definition of a variant e.g. if the object dependencies, characteristics, variant tables, are changed by development? There is also no control object record written for those objects in SAP change management.
An hints welcome
Ralf Staenglen

Hi Shah Ji,
Try to maintain your Super BOM at configurable material not at your variant. Just link your variant to configurable material super bom with tcode CS40.
Other way to create super bom besides using class :
try to use Classification as selection indicator for BOM.
1. at bom, maintain class type 001 and tick you selection indicator at item detail BOM
2. at material master, Maintain your component classification for class type 001 and set the characteristic desired.
or try to use object dependencies for super BOM :
1. at bom item, go to extra > Object dependency > editor > selection indicator. Put you "Characteristic = Value"
Hope it helps, mind sharing some points if it helps
regards,
arman

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

Object dependecies---variant configuration

HI PP team
Any one can explain the difference between the 5 object dependencies in variant configuration as well little overview where it will differentiate in different business scenarios like as auto,sanitary industries
thanks
shaik

Hi,
Five Object Dependencies are
Pre Condition: This is used for Hide/display the Char and Char values.
For Example CHAR_COLOR having a value RED only displayed IF CHAR_MODEL value 'SANTRO'
Selected.
Then you should assign the precondition at value RED level as
Syntax
CHAR_MODEL = 'SANTRO'
Selection Condition: It is used for selection of BOM Components and Routing Operations and Make
the Char as to be required entry in perticular condition.
Actions: This is Obsoleted (now.not in Use).
Procedure: It is used to Inference the Char Values to A char.
IF SANTRO is available in only RED then IF you selected SANTRO for CHAR_MODEL system auto infer the value RED for CHAR_Color.
Syntax
$SELF.CHAR_COLOR = 'RED' IF $SELF.CHAR_MODEL = 'SANTRO'
Constraint: Used to Restrict and infer the value for a Char.
Procedure and are Constraints are assigned to Config Profile which is Central configuration object in VC
Regards
Praveen

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

How to assign object dependancies in variant configuration

Hi,
I had maintain object depedacies, but in BOM for a specific assembly, that object depedancies should come, for that where I have to assign that dependancies, if possible give me the whole proceedure for the object dependancy creation and assignment.
thanks.

Hi Samir ,
Is your material configurable ? If not , at first you need to create a confgurable material.
In material master Basic Data -2 , there is an indicator " Material is configurable ". Mark the same.
Only for configurable materials you find the object dependencies column in BOM .( CS01 )
Regards
Ramesh Ch

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.

BDC selecting component - Assigning object dependencies

Hi,
I am facing a problem in developing a BDC program. In transaction CS02, for a configurable material there may be n number of components. The number of components may vary from material to material. My requirement is to assign object dependency Q & S to all the components for a given material.
Through BDC program how can i pick the components one by one and assign object dependencies Q and S at runtime??? Dynamically on what basis do i have to pick the component? Any supporting code will be more helpfull. Very thankfull to you for solving the issue.
Thanks,
RAM

I have a program which does exactly this. What it does it excepts a flat comma-delimited file and uses this to chose the component and assign the obj dep. Now that I'm looking at it, it looks that it will allow up to three obj dep to be added for a single component. The file layout will need to have......
material number
plant
item number
component material lnumber
object dep 1
object dep 2
object dep 3
I can send you the code if you email me at the address on my business card.
Regards
Rich Heilman

Variant configuration document

Dear Experts,
I am new to Variant configuration ,so I want an end end to document with example related to PP .Which includes create of characteristic ,class,super BOM,super routing,maintain of object dependencies ,configuration profile ,configuration material also checking of configuration.
Regards
Arabind

Hi Arbind,
It is very difficult discuss all variant configuration concept in a document.
In addition to our Expert Ramgiri link
Please refer below link
Variant Configuration Material Variants : Creation,Usage in Sales order for replacing Configurable Material Part 1
Variant Configuration - Basic idea
If you have any doubts other than this kindly revert back.
Thanks & Regards
Sandeep Kumar Praharaj

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

Pulling Variant Configurator's object dependencies

Similar Messages

Maybe you are looking for