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

Similar Messages

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

Generating Runtime version of a KB Object of Variant Configurable product

Hi All
There is a VC Product which needs to be transported to the CRM server via Middleware.
Hence I need to create a Knowledge Base (KB Object) and generate a Run-Time version of the same.
I am getting an error while generating the Run Time version. The description of the error is as follows:
Object characteristic COSTING_LOT_SIZE is supported in IPC scnearios 3,5
and
Object characteristic PRICE_LIST is not supported in IPC scnearios.
The exceptions raised are STPO-MENGE (Component Quantity) and SDCOM-VKOND (Variant Condition)
Please provide your inputs and suggestions in this regard.
P.S: Once I generate the run time version successfully, the CRM Middleware Consultant needs to download the VC Product to CRM.
Thanks in Advance
Regards
Chaitanya

Sreekanth,
these errors need to be analyzed by VC modeler. They indicate incompatibilies between VC and SCE. Certain expressions which are possible in the VC are not supported by the IPC (see deltalist in the Online Doc).
For example, error 1) and 2) indicate that a procedure has been assigned to a characteristic (not best practice, but often done out of convenience). It needs to be assigned to a configuration profile to run in the IPC. The variant tables seem to have empty cells which is an undefined state (tables are represented as relational tables in the IPC). BOM items need to have an integer quantity. And so on.
You can't solve these issues from a mere techncial perspective as modeling changes can have a busienss impact. The person responsible for the VC models needs to look at it.
Regards, Michael

ATP Check for Components for Variant Configuration

Hi Gurus,
Does it exist a way to perform the ATP Check for components (in variant configuration) like in a test?
I mean, I know that when I create a SO (with the correct settings) the system will perform the ATP Check for components (Missing parts list). But is it possible to do this without trying to create the SO? Maybe a tcode as CU50 or PMEVC where I could enter the variant configuration values, then it explodes the BOM and do the ATP Check (as a simulation).
Thanks in advance.
Best regards.

Hi Christopher,
If you enable the "Component Availability" within your configuration profile (under Confign initial screen, Confign Parameters), then you will see an additional option within CU50 while configuring. By pressing this button, you can see an availability check as of the date specified on the CU50 initial screen. You can also modify the quantity on the CU50 initial screen for a more realistic simulation of a sales order (where a customer may order more than one of a product). See screenshots below:
In CU42:
In Value Assignment of CU50:
Hope this helps!

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

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

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

Tolerance Limits for Class Character in Variant Configuration

HI all,
We are Using Variant Configuration, for this we have linked MIC's to Class character, When The Inspection Lot is created the Lower & Upper Limit in the specification comes as the character Value.it does not takes in to consedration the tolerance key assigned to it. For E.g. Charater Dia has value 20, & in the Tolerance key for 20 +/- 0.10 is maintained, when the Inspection lot is created the Upper & lower Limit comes as 20-20 instead 19.9 - 20.1
I have gone through SAP Note 210658, the sample code provided in note is for "Material Specification" I have tried the same with minor code correction the specifications in the lot comes as desired i.e. specifications in the lot consider the tolerance key.
Our Requirment is of task list, in the same not EXIT for task list is also mentioned but no souce code is provided, when we are using the above program (Used for Material Specification) after doing the desired changes, & when we run in de-bugging mode it shows all the calculations are being done, but finally in the lot specification appear as the charater value ( 20-20) & in the inspection lot One first MIC comes it delete's all other MIC's assigned in the Plan.
Has any body worked on this requirment, please let me know how to do the same, & if any body has used EXIT_SAPLQPAP_001 (Enhancement QPAP0001.)Plese provide me with the soution if any one has worked on it.
Thanks & Regards
Gaurav Behl

Hi ravi,
I did't work on class hierarachies but i do have a document regarding classification.
Regards,
Kanth

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

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

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

Variant Configuration data upload

Hi Gurus
In Variant configuration is there any standard method followed to upload the data like characteristics,class,object dependencies
Please give me some detailed Data Uploading tips specific to Variant Configuration
thanks
K.Prabakaran

Hi Prabakaran..,
As per my knowledge it is not there. these are purly product specific.
but you can transfer Chracteristics, class, dependencies, configuration profile, dependences, tables, table contents, material master, super bom from one client to another through ALE.
regards.

Variant Configuration teg

Hi Sapgurus,
Could you please explain Variant Configuration steps in detail.It's little urgent.And also if you have any detailed document please send to the following mail.Points will be awarded.
with Regards,
mhreddy

Hi,
Pls. find the Varian Configuration step by step procedure 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.
3.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).
4.Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
5.Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikeclass.
6.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.
7.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
8.Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save.
9.Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save).
10.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
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
Integration
There are further single roles for other aspects of the configuration environment.
Also required are the individual roles for all BOM processing (SAP_LO_MD_BOM_MAINTAIN), and classification (SAP_CA_CL_MAINTAIN).
Useful Tables for VC:
Characteristics :
CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values
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
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)
Hope this helps.
Pls. provide mail id full so I can send other doc.
Regards,
Tejas

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

Similar Messages

Maybe you are looking for