Thursday, April 23, 2009

Variant Configuration


Variant configuration - integrated applications:
CA Classification
LO Material Master
PP Bill of Material
PP Routings
PP–PI Master Recipes
SD Sales
SD Conditions
MM Purchasing
CO Costing
PP Material Requirements Planning (MRP)
PP Production Orders


We can configure the following objects:
Materials
Standard networks in the Project System.
PM General maintenance task lists
Model service specifications

Salient Features of Variant Configuration:
Configurable Material – to cover all variants
Super BOM – containing all components
Super Routing – containing all operations
Characteristics – features of configurable material
Classification – class type 300
Dependencies – to control selection of the combinations of features, the BOM components and Operations
Configuration Profile – controls the configuration process

Master Data Settings For Variant Configuration For Material:
1.Material Master :
- Std Material type KMAT or Material type must allow configuration.
- Material must have classification view.

Material Master Data for Configurable Materials:
Basic Data:
· Material is configurable Indicator
Sales:
· Item category Group : 0002 or 0004
· Delivering Plant
MRP:
Strategy Group : 25
MRP Type : PD
MRP Lot Size : EX
Availability Check : 02
Individual/Collective Requirement : 1

Creation of Material Master :
Screen showing Material is configurable indicator
Transaction code – MM01





Material is configurable
indicator







Screen showing Delivering Plant (Transaction code – MM01)
Delivering
Plant







Screen showing item Category (T. code- MM01)
Item Category 0002







Screen showing Strategy group (25) for configurable material
Transaction code: MM01
Availability
Check 02 -
Individual requirements
Strategy 25 for
Configurable
Material






2. Super BOM:
· Contains Variant and Non-variant Parts
· Object Dependencies
· Selection Conditions-to select variant parts
· Procedures and Actions- to change field values viz component quantity.
· Can use Classes as BOM items
· Can contain Configurable Material as components














Creation of Super BOM:
Transaction Code: CS01
The screen shows all components (variant and non-variant components) needed to produce all the variants of a configurable material.
OBJECT
DEPENDENCY
INDICATOR
NO OBJECT DEPENDENCY
INDICATOR, NON VARIANT PART
OBJECT DEPENDENCY
VARIANT PART



3. Super Routing:
· Contains all the Operations, Operation, sequences and Production Resources/Tools (PRTs) required to manufacture all variants.
· Dependencies assignment to the operations ,operation sequences and PRTs
· Dependencies used are selection conditions, procedures and actions













Creation of Super Routing:
Transaction Code: CA01
Contains all the operations required to produce all variants of the configurable material, having object dependencies assigned to it
NO OBJECT DEPENDENCY INDICATOR, OPERATION IS COMMON TO ALL VARIANTS

OBJECT DEPENDENCY INDICATOR, OPERATION IS SPECIFIC TO A VARIANT





4. Characteristics:
· To define the features of the configurable Material
· Assignment of object dependencies to characteristics and characteristics value to ensure complete & consistent configuration
· Characteristics values can be restricted during configuration using restrictable characteristics.












Creation of Characteristics:
Transaction Code: CT04
TYPE OF VALUE
VALUE ASSIGNMENT
ATTRIBUTES
STATUS
OBJECT
DEPENDENCY
INDICATOR
Screen showing the status, value assignment data for the characteristics, i.e. Basic Data.



Assignment of values to characteristics:
Transaction code: CT04
OBJECT DEPENDENCY
INDICATOR

ALLOWED VALUES
Three values assigned to this specific characteristic





5. Classification:
· To hold the characteristics of the configurable material
· Class used should support variant configuration
· SAP Standard class for variant configuration is 300
· Can be used for classifying materials
· Class hierarchy can be set up for these classes
· Can be used to find objects
· All objects linked to configurable material are classified
· Classes can be used as BOM components
· After configuration the class item is replaced by specific component
· Only Documents and Materials can be used as class components in the BOM
· Configurable Material is assigned to Class 300










Creation of Variant Class:
Transaction Code: CL02
STATUS OF THE CLASS
The screen showing the basic data of the variant class




Assignment of Characteristics to Variant Class:
Transaction Code: CL02
CHARACTERISTICS
The screen showing all characteristics of the configurable material assigned to the class



Assignment of Variant Class to Configurable Material:
Transaction code: CL20N
CHARACTERSTIC VALUES
CHARACTERISTICS
CONFIGURABLE CLASS NAME
CONFIGURABLE CLASS TYPE 300
CONFIGURABLE MATERIAL
The screen showing Variant class assigned to the configurable Material along with characteristics.





6. Configuration Profile:
· To define central settings for configuring the object
· Configurable object can have more than one profile
· Allows to assign the configurable object to variant class
· Define settings that affect the display of characteristics in value assignment screen
· To assign object Dependencies to the configurable material viz Dependency net, procedures and actions
· To maintain configuration parameters for BOM explosion













Creating Configuration Profile:
Logistics---Central Functions ---Variant configuration---Configuration Profile---Create (T. Code- CU41).
CONFIGURABLE MATERIAL
Initial screen of configuration profile.





Next Screen of configuration Profile
CLASS ASSIGNMENT







Basic Data of Configuration Profile
STATUS OF THE
PROFILE
OBJECT DEPENDENCY
INDICATOR
The Variant class can also be assigned to the Configurable Material from the configuration profile using Tab Page Class assignment as shown in this page





Configuration settings in the Configuration Profile
This Page depicts how the configuration is processed (value assignment), level of BOM explosion, BOM application.





Value assignment Settings in the configuration Profile







7. Object Dependencies:
Purpose:
· To describe the interdependencies between characteristics and characteristic values
· Component and Operation selection
· To change the values of fields for BOM components and Operations





Integration:
· Classification System
· Variant Configuration






Creating Global Dependencies:
Logistics---Central Functions ---Variant configuration---Dependency---Single Dependency---Create (T. Code - CU01).






DEPENDENCY TYPE

STATUS







CLICK CHECK
NO SYNTAX ERROR MESSAGE SHOULD BE DISPLAYED
SYNTAX








CHANGE THE STATUS TO RELEASED, SAVE








Dependency Types:
Administrative Types:
· Global dependencies are created centrally and can be assigned to several objects. External number/name assignment for the Global Dep
· Local dependencies are created for one object and can be used with that object only. Internal Number assignment for local Dependency

Technical Types:
· Preconditions
· Selection Conditions
· Actions
· Procedures
· Constraints


Preconditions:
· To hide characteristics and characteristic values which are not allowed while configuration.
· Allocated to characteristic or characteristic value that we want to hide
· Precondition is fulfilled if the condition entered is fulfilled or not violated.
· A Precondition is fulfilled, if the specified value is selected for the specified characteristic or no value is selected for the specified characteristics
· A Precondition is not fulfilled if a different value is selected for the specified characteristics

Selection Conditions:
· To determine which variants require a specific component or operation
· To determine when it is mandatory to assign a value to a characteristic
· We can allocate the selection condition to the following objects
Characteristics
BOM components
Operations
Suboperations
Sequences of operations
Production Resources/Tools (PRTs)
· Selection condition is fulfilled if the value in the condition is set for the characteristic
· Selection condition is not fulfilled if a different value is set or no value is set



Procedures:
· To infer values for characteristics
· Can be assigned to the following objects
Characteristic that triggers procedure
Characteristic value that triggers procedure
Configuration Profile
BOM components
Operations in the task lists
· Uses the variable $SELF before characteristic
· Procedures are always used for variant pricing
· Procedures can overwrite values set by other procedures
· Various Key words(variables) used in procedures
$SET_DEFAULT
$DEL_DEFAULT
$SUM_PARTS
$COUNT_PARTS
$SET_PRICING_FACTOR
NOT SPECIFIED
NOT TYPE_OF

· Processing sequence can be defined in case of multiple procedures assigned to an object


Assigning Object Dependencies:
· We can assign the following object dependencies to the following objects
Configuration profile
Dependency nets
Procedures
Characteristics
Procedures
Preconditions
Selection conditions
Characteristic values
Procedures
Preconditions
BOM items
Procedures
Selection conditions
Operations in task lists
Procedures
Selection conditions
Production resources/tools (PRTs)
Procedures
Selection conditions




Constraints:
· Mainly used for intensively interactive configuration
· The main purpose of a constraint is to monitor the consistency of a configuration
· Can be used to describe the dependencies between completely different objects and their characteristics
· Constraints are not directly allocated to individual objects
· Constraints are grouped together to form dependency nets and allocated to configuration profile
· Object variables $SELF, $ROOT,$PARENT are not used
· Refer to objects by entering the class to which the objects are allocated
· Constraints are declarative dependencies, the processing sequence and the point in time when constraints are processed are not relevant
· Constraints are not processed in a specific order, we cannot determine when a specific constraint is used
· In any processing situation a constraint is processed only once , if a value that is relevant to the constraints is changed, the constraint is triggered again







Structure of Constraints:
· Four sections in a constraint,each part is identified by a key word, key word is followed by a colon, each section ends with a period
· Four Sections
OBJECTS: must
CONDITION: optional, if entered must be fulfilled
RESTRICTIONS: must, relation between objects and characteristics
INFERENCES: enter characteristics for which values are to be inferred









Actions:
· To infer values for characteristics, cannot overwrite values that are set by an action
· To change field values in BOM items or operations in routings
· We can assign actions to the following objects
Characteristic value that triggers action
Characteristic that triggers action
BOM items –viz for changing the quantity
Configuration profile
Operations in task list – viz to change the
Standard values
· Enter the variable $SELF before the characteristic
· Cannot use the following expressions
NOT SPECIFIED
NOT TYPE_OF
NE





8. Configuration Simulation:
· To check the authenticity configuration Model created before actual process
· To test whether we have created objects correctly and whether dependencies work
· BOM for this simulation is selected according to the BOM application in the configuration profile
· Can use configuration simulation only for materials













Simulating BOM/Task List Explosion:
CLICK HERE
BOM /ROUTING
SELECTION
CONFIGURABLE MATERIAL








SPACE FOR ASSIGNING VALUES
CHARACTERISTICS







VALUE ASSIGNMENT
















CLICK RESULT
VALUES ASSIGNED
TO
CHARACTERISTICS







The Screen shows the components selected according to the value assignment to characteristics
CLICK CHECK








CLICK
LIST
Message Configuration is consistent and complete is displayed





The screen shows the list of variant and non-variant components selected







Procedures.
$self.color=Green if Pressure>=10
$self.color=Red if Pressure>=50
Sort sequences only apply for that object.