HI,
Pls. find the details about Variant Configuration :
Variant Configuration (LO-VC)
Purpose
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:
CA Classification
LO Material Master
PP Bill of Material
PP Routings
PPu2013PI Master Recipes
SD Sales
SD Conditions
MM Purchasing
CO Costing
PP Material Requirements Planning (MRP)
PP Production Orders
You can configure the following objects:
Materials
Standard networks in the Project System.
PM General maintenance task lists
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.
VARIANT CONFIGURATION PROCEDURE
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
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.
Revert if you need more details.
Award points if useful.
Regards,
Tejas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.