Dependency tables in variant configuration

Dear PP Guys,
Pl. tell me where the local and global dependencies are getting stored i.e.ABAP table name. I want to develop a report where the client wat to see the dependency written against a component in a bom.
Regards
Laxmikanth

Dear,
Dependencies - CUKN ,CUOB,CUKB,CUKBT,CUXREF.
Also refer this thread,
Re: Object Depedencies in BOM
Regards,
R.Brahmankar

Similar Messages

Table needed- Variant configuration details of a material in a sales order

Dear Friends,
I would like to display all variant configuration details/characteristics and values of a particular item in the sales order in a table. Is there any standard SAP table available to serve this purpose??
Ex: I would like to give the sales doc no and the item no and material. The system has to display all the variant configuration details (Characteristics and the values) for the particular item
could you please suggest any other methods to achieve this?
Regards,
Kali

HI Kali
There is no standard SAP table available for your requirement.
Instead use FM "VC_I_Get_Configuration", and pass your sales order and item number to fetch Variant char. value for that line item in sales order.
This is the only solution.

Variant Configurator : Value set by user or dependency ?

Hi,
How can i determine whether a value in a characteristic in the variant configurator is set by a user or by a dependency ?
with regards
Erik

Hi,
When a variant is created , inthat particular screen, theres an option
Whether it is cretd by user or system.
And table name is RSVAR
field is TRANSPORT
Thanks,
Shreya

How do I extract the data of Variant configuration into internal tables

Hi Experts,
How can I extract the data of variant configuration into an internal tables while preparing the report.
Thanks,
bsv.

Hi i´m not a "Expert.." but may I can help you:
CUCB_GET_VALUES_FROM_INSTANCE
Example:
Instance = MARA-CUOBF or
Instance = lips-cuobj
Result is the data of the Variant tables.
I need that for a simple report to evaluate customer & and his Variants......
Robert

Using dependancy in variant configuration.......

Hi
PP gurus..
Can u explain me wht is the convention of using"$" sign while creating dependancy in variant configuration.?

Hi Yogesh,
As Satish said, it is a syntax which is used to denote the start of a PROCEDURE in object dependencies. It is convention used to notify the compiler that the object dependency used is an PROCEDURE

Re: Variant tables usuage for variant configuration.

Dear All.
I have variant configuration and I need variant tables for the dependencies. Can any body guide me how to use the variant tables.

Hi.
I have used them mostly as a repository of technical data unknown to sales department (guys who create and configure sales order).
In a Packaging Industry they used variants for folding cartons and all technical data was maintained by a Techical Area in variant tables. Data was retrieved from configuration using procedures.
Variant table data is maintained in transaction CU60. This is not a very friendly interface and can't deal with multi-user updation. This is why one year after go-live this company started to use a Z-tables and LINKED them to variant tables (CU62). Using this you can work with same procedures but with much more easier data maintenance. I recommend to take this in account.
regards, SL

Variant Configuration tables

Hi,
I need all Variant Configuration related Tables.
Can you give me list of it or link for the same.

Hi Chetan,
Find below the tables related to Variant Configuration
1.1     Characteristics:
                     CABN                    Characteristics ( o.a. batch/vendor)
     CABNT                    Characteristics description
     CAWN                    Characteristics ( o.a. material)
     CAWNT                                    Characteristics description
     AUSP                    Characteristic Values
1.2     Class types and objects :
                     TCLAO                                                          Several class types for object
     TCLA                    Class types ( vb. lfa1 => v10 en 010)
     TCLAT                    Class type text
     TCLT                    Classifiable objects
     TCLC                    Classification status
1.3     Links:
                     INOB                    Link between Internal Number and Object
     KLAH                     Class header data
     KSSK                    Allocation Table: Object (vb.matnr) to Class
     KSML                    Characteristics for a class (internal number)
With best regards
Shankarling.

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

Variant Configuration including Bitmap

Hi there,
we using often small bitmaps to show the customers a hint to the selected articles. The output of SD Order are sapscript forms and we solve this with include of an Bitmap in sapscript article description.
Now i try to include such a bitmap in a variant configuration. If the user select a value 1 of a Characteristic ist should print bitmap xx, if the user select value 2 of a Characteristic ist should print bitmap yy and so on.
Is anyone who had solve such a problem or know how could i realize this in sapscript.
Is there a possibility to define a variable in the characteristics value or in the maintaining dependencies of a value?
While processing the variant configuration table in sapscript (loop at tkomcon conf_out = tkomcon) this could be done by an if then else statement. But i don't like to process this on all variant articles. So i search for a solution to sove this in the article description/variant characteristics depending on a selected value.
Thanks for help
Karl Mueller

Hi
1) A configurable material , let us say can have 1000 of variants based on the characteristics combination. Out of these 1000 variants we will be interested to stock only a few variants . This could be say 10 or 20, and for these only, we need to create material variants. Actually this process is similar to the creation of 10 or 20 new materials..but here by selecting the characteristics, we are creating the materials which are known as material variants.
Hence we will not be creating material variants for all possible combinations
2) For the material variants that we created, we plan, produce & stock the required quantities.During SO creation we enter the specification ie characteristics combination given by the customer. In Sale order itself we can make the system to check whether a material/stock exist for the given characteristics combination and assign the promise date suitably.
Regards,
Ramasamy

SD SAP Variant Configuration questions

Hello guys, I'm preparing for an exam and trying to find the answers for the following questions, please help me, I need them as soon as possible, full points will be given to any answer, Thanks all !
- What is variant configuration?
- What is characteristic?
- What is value?
- What is class?
- What is configuration profile?
- What is dependency and what are the types?
- What is a variant table?
- And the transaction codes for the above.

Dear Kevin,
Thease are possible quetions
the possible questions could be
1. What is item category group in VC
2. what is the item category for the material in VC
3. What is meant by class
4.what is meant by Charateristics values
5.how pricing in mapped in variant confi
6.what are setting in material master in variant material
7.can material type FERT can used has variant material(KMAT), if it is then how
8.waht is requiremnt type while doing variant confi
9.what is stragey group you will select in for vaiant material
10.what is meant by object dependency
11.waht arethe dependency types
12.waht is meant by precondition,selection conditions,actions, procedures
Hope this helps you
Prem.

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.

ALE Variant Configuration

Hi , I am not having much idea about ALE , I am some problems in it.
When running the ALE to move the Variant Configurator from Client 130 to other Clients, I am running into the following issues.
1)it does not copy the dependencies within the Configuration Profile. It copies the dependencies themselves and the profile, but when you go into the profile, there are no dependencies listed. An example is: For SLCase in Client 130, go into the profile and you can see several dependencies there, but when you go into Client 110.
2)it does not always update the dependency when it already exists.
3)it does not update the Table structure when the table already exists.
4)it does not update the data in the table when the table already exists (this oculd be because the structure of the table changed in Client 130, but didn't update the structure in the other clients (as in #3 above).
5)it does not update the Default checkbox on the characteristic when the characteristic already exits.
Thanks.
Ankesh Jindal

Hi
Check SAP note 10745. It has details how to transfer classification data from one client o another by ALE. Hope it will help to solve your problem
Regards
Antony

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

Dependency tables in variant configuration

Similar Messages

Maybe you are looking for