Professional Documents
Culture Documents
Variant Configuration
Variant Configuration
Variant Configuration
SD Sales, Conditions
MM Purchasing
CO Costing
It is possible to configure:
Materials
Standard networks in the Project
System
PM General maintenance task lists
Model service specifications
The master data of a configuration model comprises materials, bills of material (BOMs), classes,
characteristics,
dependencies, and configuration profiles.
The realization of a product's Bill of Materials / routings is controlled by the configuration model
and its dependency knowledge
which is modeled and designed by the user.
The following steps are required to be able to configure objects and simplify and automate the
production process:
Configuration Profile
The configuration profile contains the main dependency logic for the configurable material,
controls how
BOM explosion is processed and allows further specifications for the BOM. Additionally, the class
assignment
can also be maintained here.
1. Planned/Production Order
2. Sales Order (SET)
3. Order BOM
1.Planned/Production Order
When the level of BOM explosion (none, single level, multi-level) in the sales order is selected,
the following
processes apply:
All configurable items are configured
in the sales order
Sales relevant items are copied to the
sales order as sales items
Value assignments are stored on the
data base for each configurable
material
Order BOM is used for customer specific adjustment of the BOM and the value assignment is
done in SD,
but not in BOM explosion.
Generally, the BOM explosion is controlled by the BOM usage, the BOM application and the BOM
filters.
Dependency Knowledge
The following type of dependencies are used in variant configuration:
Dependency Where it is What it is used For Processing order
Type attached
The objects in the BOM can be called by either: $SELF , $PARENT or $ROOT depending on the
level on which the object can be found.
Low level and high level configuration
High Level
On high level, every interactive configuration and all dependencies are processed.
Low level
Low level configuration refers to background explosion of BOM, production order creation and
MRP restrictions of the selection condition,
the procedures changing master data and the class nodes replacements.
In low level configuration, processing of dependcies is limited and some syntax such as
$set_pricing_factor is not read.
Class Nodes
Class nodes can be created by using classes as nodes instead of setting multiple BOM items in a
following manner:
Database storage
The main anchor where the configuration of an object in an application is stored is
TABLE_APPLICATION-CUOBJ
Table Description
RESB Reservations
EQUI Equipments
LIPS Deliveries
VBRP Invoices
Very common is changing master data via dependencies e.g. number of components in the BOM
Reference characteristic STPO-MENGE
VOLUM Volume
You moreover have the possibility to change master of BOM, routing and master recipes
Table Description
Table Description
Table Description
Table Description
MGVGW Quantity
Performance issues
No labels