Introduction To Variant Configuration in R/3

Introduction to
Variant
Configuration in R/3
Contents
The following topics are covered by this

presentation:
 Overview
 Prerequisite
 Configuration Profile
 Dependency knowledge  Processing sequence of dependency knowledge
 More help?  Data base storage
 Low level and high level configuration

 Additional topics
 Material variants
 Class Nodes
 Communication with other application
 Important function modules / programs
 Internal tables
 Performance issues
 SAP AG 2003, Title of Presentation, Speaker Name / 2
Overview
Variant Configuration is the modeling of complex products in R/3. The

Features of the products are realized by the customer.
It is integrated or has interfaces to the following modules:
CA-CL Classification
LO-MD-BOM / LO-MD-MM Material Master, Bill of Material
PP Routings, MRP, Production order
PP-PI Master Recipes
SD Sales, Conditions
MM Purchasing
CO Costing
Moreover, you have interfaces to CRM (IPC) and APO

Overview
You can configure

•Materials
•Standard networks in the Project System.
•PM General maintenance task lists
•Model service specific
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 customer.

Overview
BOM / Routing adjusts to customer needs:
1. The car should be green

2. 192hp motor
3. Convertible
kmat
1 2 kmat 3
11 12 21 1 22
2 3 31 32
111 12 11
211
21
221
32
311 321
111 211 323
1111 121 2111 312 322
1111 2111
11111 11113
21111
21111
313 323
11112
11113

Overview
What do you need to run Variant Configuration?

Attach Dependency
Define Characteristics Knowledge Pricing
With values Discounts/ Surcharges
Attach Dependency
Collect them in a Knowledge
Class of class type 300 Attach Dependency
Knowledge
Control the scenario
Configuration Profile
Super BOM Configurable Material

1
Attach Dependency
11 12 13
Knowledge
Super Routing 1
Attach Dependency
11 12 13 Knowledge

Prerequisite
The material must be marked as configurable in the material

master. (transaction mm02, basic data 2)
Sales: Item category group 0002/0004
Delivery Plant
MRP: Strategy group e.g. 25
MRP type e.g. PD
MRP lot size EX
Availability check 02
Individual/collective 1

It controls the scenario how variant configuration is being

integrated in the sales document process.
The main dependency logic is attached to it.
You may define your own user-defined interface.
The class assignment is done here.

•Planned/Production Order
• Select the level of BOM explosion (none, single level, multi-level) in the sales
order. Up to that level you have
• 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
1
BOM explosion
In the sales order 11 12 13
111 112 121 122 131 132
1121 1321
1122 1322
BOM explosion
In pland/prod order

•Sales Order Set

• Products are supplied together, but not assembled together (Its just a grouping)
• Only sales relevant BOM items are exploded
• 11, 12, and 13 have their own BOM, can be sold separately, not only in group 1!
Sales relevant
1
11 12 13
111 112 121 122 131 132
1121 1321
1122 1322
Planned/Production relevant

•Order BOM
•Used for customer specific adjustment of the BOM
•Value assignment is done in SD, but no BOM explosion
1
Value assignment done

1
in SD
11 12 13
111 112 121 122 131 132
1121 1321
BOM explosion and changes done in CU51
1122 1322

Two types of order BOM can be choosen
•Result oriented (saves the final result with manual changes)
•Knowledge based (saves the Super BOM , manual changes, dependency

knowledge)
In general BOM explosion is controlled by BOM usage
BOM application
BOM Filters

Dependency knowledge
The following types of dependencies exists:
Dependency Where attached Used for

Characteristic value Hide a value
Preconditions
Characteristic Hide a characteristic
Characteristic Make a char required
Selection condition
BOM/Routing Select components
Characteristic Value
Infer values, send
Characteristic values from root
Procedure
Configuration Profile material to
subcomponents
BOM/Routing
Infer values top down
Constraint Configuration Profile
and vice versa

Main difference between procedure and constraints
Procedures
Constraints

Procedures ► sequential order, exactly once after every ‘Enter’
Constraints ► no fixed order, only if there are relevant changes

Color=‘red’ $root
$parent
HD=2
x $self
How to refer to the objects in the BOM?
e.g. $self.HD = 2 if $root.color =‘red’

Examples
Preconditions Color = green
Width = 25.1 inches if $self.Color specified
Selection Conditions horsepower 192
kmat
kmat
If $root.horsepower = If $root.horsepower = If $root.horsepower =
160 192 232

Comp 1
Comp
Comp 2
2 Comp 3

Procedure HD 100 $self.HD = 100 if $self.CPU=2
CPU 2
Moreover you can call functions from procedure
Function(CPU = $root.CPU, HD=$self.HD)

Constraints
Objects: PC IS_A (300) PC , PT IS_A (300) PRINTER
(usually refer to the objects by the class and class type)
Conditions: PC.CPU = 2
(defines when the constraint run)
Restrictions: PC.HD = PT.COLST
(you can restrict or set values, call functions or access variant tables)
Inferences: PT.COLST
(What characteristic should be inferred)

Finally, a few words about variant tables. They can be used in procedures,
constraints and preconditions and selection conditions for value restriction
or value set.
Characteristic Key field
CPU
HD
Color X
Table MY_CPU ( CPU = $self.CPU,

HD = $self.HD,
Color = Color )
Depending on the color , CPU and HD are infered.

Additional topics
 Processing sequence of dependency knowledge
 Data base storage
 Low level and high level configuration
 Material variants
 Class Nodes
 Communication with other application
 Important function modules / programs
 Internal tables
 Performance Issues

Processing sequence of dependency knowledge
in the interactive configuration
Procedures are exactly processed once for each configuration

run (e.g. pressing enter)
1. Procedures
1. Procedure of configuration profile
2. Procedure of characteristics
3. Procedure of characteristics values
2. Preconditions
3. Selection conditions
Constraints run whenever there is a change of a relevant

characteristic.
Use the trace functionality to figure out what runs!

Data base storage
The main anchor where the configuration of an object in an application is stored

is TABLE_APPLICATION-CUOBJ
AFPO Production order
PLAF Planned order
RESB Reservations
VBAP Sales orders
MARA(CUOBF) Plant independent material variants
MARC(CUOBJ/V) Plant specific material variants
EQUI Equipments
SER00 Serial numbers
EBAN Purchase requisitions
LIPS Deliveries
EKPO Purchase orders
VBRP Invoices
BGMP Master Warranty Item
ESLH Service packages
PBED Independent requirement data

Data base storage
Use CUOBJ and go to transaction cutableinfo
There you get all relevant configuration data stored in different tables on the data
base on one screen.
TABLE DESCRIPTION IMPORTANT FIELDS
IBIB Basic data Ibase, objnr
Instance (=ibase+1)
IBIN Instance In_recno (internal uni identif)
Valfrom, valto, cuco (profile)
IBINOWN Owner of instance Inttyp, (obtab), objkey
Characteristic values of an
IBINVALUES Sybmol_id, ataut
instance
IBSYMBOL Char-value combinations Atinn, atwrt, atflv
e.g. u9c 225714

Low level and high level configuration
High level configuration

interactive configuration , all dependencies like constraints are
processed.
Low level
refers to background explosion of BOM, production order creation, MRP
restrictions:
o selection condition,
o procedures changing master data
o class nodes replacements
! Not read are: dependencies of char, char values , configuration profile-> no

constraints, some syntax are not supported like $set_pricing_factor...

Material variants
Arise from a configurable product and has a certain configuration

stored. Can be put on stock with its configuration.
Plant independent material variants  mm03, basic data 2,

mara-cuobf
Plant specific material variants  mm03, mrp3, marc-cuobj

Class Nodes
Using classes instead of hundreds

of similar BOM items:
Kmat
Kmat
1
1
Item 11
Class item
Item 11
Item 12
Item 12
Item 13
Classify objects
Item 13
Item 14
Item 14

Communication with other applications
Very important is the pricing
Reference characteristic to SDCOM-VKOND – see note 187162
Very common is changing master data via dependencies
e.g. number of components in the BOM
Reference characteristic STPO-MENGE

The following fields can be changes by variant configuration.
Reading access to sales order data

VBAK Header data
VBAP Item data
MAEPV Material master fields
MAAPV Material master fields
VBKD Sales document: commercial data
VBPA_AG Partner: sold-to party
VBPA_WE Partner: ship-to party
VBPA_RE Partner: bill-to party
VBPA_RG Partner: payer

Changing access by using VCSD_UPDATE Structure

Gross weight of item (BRGEW)
Net weight of item (NTGEW)
Unit of weight (GEWEI)
Volume (VOLUM)
Volume unit (VOLEH)
Item quantity (KWMENG)
Sales unit of measure (VRKME)
Conversion factors
Target quantity (ZMENG)
Target quantity unit (ZIEME)
Article description (ARKTX)

You moreover have the possibility to change master of BOM, routing and
master recipes
STPO (BOM)
Item text (POTX1 and POTX2)
Variable-size item sizes 1–3 (ROMS1–3)
Number of variable-size items (ROANZ)
Variable-size item quantity (ROMEN)
Component quantity (MENGE)
PLPOD (task list and master recipe)
Activity types (LAR01–06)
Standard values (VGW01–06)
Unit of measure (VGE01–06)
Work center (ARBPL)
Operation description (LTXA1, LTXA2)

PLFLD (sequence of operations)
Lot size from (LOSVN)
Lot size to (LOSBS)
PLFHD (production resources/tools)
Quantity (MGVGW)
Quantity formula (MGFORM)
Required quantity (EWVGW)
Required quantity formula (EWFORM)

Performance issues
-> Check note 917987
for performance aspects in Variant Configuration

Introduction To Variant Configuration in R/3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction To Variant Configuration in R/3

Uploaded by

Copyright:

Available Formats

Introduction to

The following topics are covered by this

 Dependency knowledge  Processing sequence of dependency knowledge

 More help?  Data base storage

 Low level and high level configuration

 Communication with other application

 Important function modules / programs

Variant Configuration is the modeling of complex products in R/3. The

It is integrated or has interfaces to the following modules:

Moreover, you have interfaces to CRM (IPC) and APO

 SAP AG 2003, Title of Presentation, Speaker Name / 3

You can configure

•Standard networks in the Project System.

•PM General maintenance task lists

•Model service specific

The realization of a product’s Bill of Materials / routings is controlled by

 SAP AG 2003, Title of Presentation, Speaker Name / 4

BOM / Routing adjusts to customer needs:

1. The car should be green

 SAP AG 2003, Title of Presentation, Speaker Name / 5

What do you need to run Variant Configuration?

Super BOM Configurable Material

 SAP AG 2003, Title of Presentation, Speaker Name / 6

The material must be marked as configurable in the material

Sales: Item category group 0002/0004

MRP: Strategy group e.g. 25

MRP type e.g. PD

MRP lot size EX

 SAP AG 2003, Title of Presentation, Speaker Name / 7

It controls the scenario how variant configuration is being

The main dependency logic is attached to it.

You may define your own user-defined interface.

The class assignment is done here.

 SAP AG 2003, Title of Presentation, Speaker Name / 8

111 112 121 122 131 132

 SAP AG 2003, Title of Presentation, Speaker Name / 9

•Sales Order Set

111 112 121 122 131 132

 SAP AG 2003, Title of Presentation, Speaker Name / 10

Value assignment done

111 112 121 122 131 132

 SAP AG 2003, Title of Presentation, Speaker Name / 11

Two types of order BOM can be choosen

•Result oriented (saves the final result with manual changes)

•Knowledge based (saves the Super BOM , manual changes, dependency

In general BOM explosion is controlled by BOM usage

 SAP AG 2003, Title of Presentation, Speaker Name / 12

The following types of dependencies exists:

Dependency Where attached Used for

 SAP AG 2003, Title of Presentation, Speaker Name / 13

Main difference between procedure and constraints

 SAP AG 2003, Title of Presentation, Speaker Name / 14

How to refer to the objects in the BOM?

e.g. $self.HD = 2 if $root.color =‘red’

 SAP AG 2003, Title of Presentation, Speaker Name / 15

Preconditions Color = green

Width = 25.1 inches if $self.Color specified

Selection Conditions horsepower 192

If $root.horsepower = If $root.horsepower = If $root.horsepower =

160 192 232

 SAP AG 2003, Title of Presentation, Speaker Name / 16

Procedure HD 100 $self.HD = 100 if $self.CPU=2

Moreover you can call functions from procedure