Material Configurable SAP | Areas Of Computer Science | Computing

_________________________________

_________________________________
_________________________________
_________________________________

Exploiting Variant Configuration
for Use in Advanced Planning
and Modeling

_________________________________
_________________________________
_________________________________
_________________________________

Jean-Yves Popovic
ADELANTE

_________________________________
_________________________________

© 2008 Wellesley Information Services. All rights reserved.

What We’ll Cover…








_________________________________

Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM
and OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
1

Who Should Use Variant Configuration?

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Example of industries relevant to SAP VC:

_________________________________
_________________________________

Product
Complexity

_________________________________

Aircraft
Automobiles

_________________________________
PCs

_________________________________
_________________________________
Pumps

Motorcycles

_________________________________

Elevator
Systems

_________________________________

Bicycle
Furniture

_________________________________
Mass
Production
2

VC Concepts and Functionalities

_________________________________

Process flow:

_________________________________
Super Routing

Super BOM
interior
seats
seats

_________________________________

car

car
body
body
body

+

Op.10
Op.20

+

_________________________________

dashboard
Op.30

_________________________________
_________________________________
Sales/Customer Services

Production/Procurement

Engineering

_________________________________
Sales Quote

Sales Order

_________________________________

Prod Order

_________________________________

Order BOM

Purch Order

_________________________________
3

Variant Configuration Knowledge Base
Material Master

Variant Class

Material Type: KMAT
Desc.: Italian BMT
Variant Class: <Italian BMT>

_________________________________
Pricing
Conditions

_________________________________

ƒ ...

_________________________________
_________________________________

Desc.: Italian BMT
Type: 300
Characteristic: Bread Type
Possible Values:

Super
BOM

Super
Routing

Regular
Italian
Herbs

ƒ Item 10: ...
ƒ Item 20: ...

ƒ Op. 10 ...
ƒ Op. 20 ...

_________________________________

Configuration
Profile

_________________________________

ƒ Order BOM
ƒ BOM explosion
ƒ User Interface

_________________________________

Characteristic: Length

_________________________________

Possible Values:
6”
12”

Dependencies

_________________________________

ƒ Precondition (PC)
ƒ Selection Condition (SC)
ƒ Procedures (P)
ƒ Constraints (C)

_________________________________
4

What We’ll Cover…








Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM
and OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
5

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Material Variants: Concept

Definition:
Œ

_________________________________

A material variant is a material that is kept in stock and that is
a specific configuration of a configurable material

_________________________________
_________________________________

Purpose:
Œ
Œ
Œ

_________________________________

Planning (forecast, Make-To-Stock)
Pre-Assembly
Sales Order (delivery date: ATP)

_________________________________
_________________________________
_________________________________

Type Matching:
Œ

_________________________________

When assigning value to a configurable material, the system
will look for a material variant

_________________________________
_________________________________
6

Material Variants: Material Master

_________________________________

Create Material Master (material type must allow for
stock):
Œ

_________________________________
_________________________________

Basic Data 2 view:

_________________________________

OR:
Œ

MRP 3 view:

Reference the
Configurable
Material

_________________________________

Bring the
Configuration screen
(Value Assignment)

_________________________________
_________________________________
_________________________________

_________________________________

Note:
Œ
Œ

Cross-plant configurable material can only be used in
purchasing
Values assigned are stored in the Material Master record

_________________________________
7

Material Variants: BOM

_________________________________

Create a new BOM or link the material variant to the
BOM of the configurable material:

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
8

Material Variants: Routing

_________________________________

Create a new Routing or link the material variant to the
Routing of the configurable material:
Œ

_________________________________
_________________________________

Using transaction CA02, assign the material variant to the
routing of the configurable material

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
9

Material Variants: Type Matching Settings

_________________________________

In the configuration profile (use transaction CU42) of the
configurable material:
On request or permanent
(performance!)

_________________________________
_________________________________
_________________________________

Warning

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
Type Matching performed as
configuration is done (partial)
or when it is finished (complete)
(performance!)

_________________________________
Warning

10

Material Variants: Results

_________________________________

Using Configuration
simulation (transaction
CU50):

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Appears as soon as the
configuration matches

_________________________________
11

Variant Pricing: Concept

_________________________________

The configurable material has a basic price
You can define surcharges/discounts (variant
conditions) that depend on characteristic values
Condition types VA00 (absolute amounts) and VA01
(percentage amounts) are defined for variant conditions
Variant conditions can be created with reference to a
material, a distribution channel, and a sales organization
You assign variant conditions to characteristic values

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

12

Variant Pricing: Surcharge/Discount Characteristic
1.

_________________________________

Create a multiple-value characteristic with reference to
field SDCOM-VKOND:

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
13

Variant Pricing: Surcharge/Discount Characteristic (cont.)
2.

_________________________________

Create a condition record of condition type VA00
(absolute) or VA01 (percentage):
Œ

Œ

_________________________________
_________________________________

Key field “Variant” is your choice; this is the variant condition
key that you will use in dependencies (caution: casesensitive)
Make sure your pricing procedure reads condition types VA00
and/or VA01

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
14

Variant Pricing: Assignment or Dependency
3.

_________________________________

Using the configuration simulation (transaction CU50),
assign the condition record to the characteristic value:

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

1. F4 on the
value field

2. Select the value

_________________________________
_________________________________

3. Click on the Variant
Condition icon

4. Save
15

Variant Pricing: Results
4.

_________________________________

In the Sales Order entry screen (base price = 5 EUR):

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
16

Variant Pricing: Others

_________________________________

Dependencies:
Œ

_________________________________

Instead of assigning condition records to characteristics
value, you can use dependencies (procedures) to the
configuration profile:
f Example:
$self.Z_SURCHARGE = ‘surcharge_bread’ if Z_BREAD eq ‘D’

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
17

Variant Pricing: Others (cont.)

_________________________________

Pricing Factor:
Œ
Œ

Œ

_________________________________

You can assign a pricing factor to the variant condition
The factor can be a constant, a numeric characteristic, or a
numeric expression
f $self.Z_SURCHARGE = ‘surcharge_bread’
f $SET_PRICING_FACTOR ($self, Z_SURCHARGE,
‘surcharge_bread’, BREAD_SIZE/12)
This will alter the surcharge (based on bread type) by a factor
that is based on the bread size

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
18

Variant Pricing in Purchasing (MM)

_________________________________

Same technique as for sales, using condition records of
condition type VA00 or VA01, except:
Œ
Œ

_________________________________
_________________________________

The reference characteristic refers to MMCOM-VKOND
Only assign condition records using dependencies

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
19

What We’ll Cover…








Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
20

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Object Dependencies: Dependency Types

Declarative: Point in time and sequence not relevant to
the result
Œ

_________________________________
_________________________________

Constraints and Actions (obsolete)

_________________________________

Semi-declarative: Like declarative, but processed
procedurally
Œ
Œ

_________________________________

_________________________________

Preconditions
Selection conditions

_________________________________
_________________________________

Procedural: Result depends on processing sequence
and point in time
Œ

_________________________________

Procedures

_________________________________
_________________________________
21

Object Dependencies: Dependency Types (cont.)
Usage

Dependency

Semi-declarative

Selection
Condition
(SC)

Must a char. (or char. value)
be selected?

Procedural

Procedure
(P)

Infer values, including
reference data (overwrite,
recursive)

Declarative

Precondition
(PC)

Constraint
(C)

Infer values and
consistency check (multilevel)

BOM Item
Routing Op.

Characteristic

Characteristic
Value

_________________________________
Configuration
Profile

Can a characteristic (or
char. value) be selected?

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

22

Object Dependencies

_________________________________

Processing sequence in value assignment:
Œ

Constraints

Œ

_________________________________

ENTER Œ
1. Default values for characteristics
2. All procedures, exactly once, in the following
sequence:
ƒ Configuration profile
ƒ Characteristics
ƒ Characteristic values
3. All preconditions and then all selection
conditions
ΠCharacteristic Value

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
23

Object Dependencies: Constraints

Designed for multi-level complex interactive
configuration (but useful for single-level configuration)
Infer values and check configuration consistency
Œ

_________________________________
_________________________________
_________________________________

Between any objects in a configuration task

_________________________________

Active in configuration only
Œ

Œ

_________________________________

No effect on BOM and task-list explosion in low-level
configuration (in MRP, for example)
Cannot replace selection conditions and procedures

_________________________________
_________________________________
_________________________________

Constraints are not assigned directly to individual
objects. They are grouped together to form a
dependency net and assigned to a configuration profile.

_________________________________
_________________________________
24

Object Dependencies: Constraints Structure

_________________________________

Constraints Structure:
Œ

Œ

Œ

Œ

OBJECTS:
f Specify the objects that are relevant to the constraint
(class, characteristic, material)
f Variables can be defined
CONDITION (optional):
f Condition that must be fulfilled to process the constraint
RESTRICTIONS:
f Relation between elements in the Objects section that
must be true (consistency check and inference)
f Direct or using variant functions and variant tables
INFERENCES (optional):
f Applies to formulas in the restriction
f Table calls or function calls

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
25

Object Dependencies: Example of Constraint

_________________________________

BOX is a class, with four characteristics (Length, Width,
Height, and Volume)
If any three of the variables are known, the fourth is
automatically inferred.

_________________________________
_________________________________
_________________________________
_________________________________

OBJECTS:
(300) BOX,
where L = Length;
W = Width;
H = Height;
V = Volume.
RESTRICTIONS: V = L * W * H.
INFERENCES: V = L * W * H.

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
26

Object Dependencies: Variant Tables


Variant tables describe allowed combinations of values
in Selection Conditions, Preconditions, Procedures, and
Constraints
Can infer values in procedures and constraints
Restrictions:
Œ

Œ

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Recommended to use single-value
characteristics
You cannot define dependencies for
table entries

_________________________________
_________________________________
_________________________________

It is possible (recommended) to link
existing variant tables to new
database tables (performance)

_________________________________
_________________________________
27

Object Dependencies: Create Variant Tables

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
28

Object Dependencies: Table Contents

_________________________________
_________________________________
_________________________________

Table display
options:

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
29

Object Dependencies: Variant Tables (Example)

_________________________________

Constraint:
OBJECTS:
PC IS_A (300)PC.
RESTRICTIONS:
table CS (PRINTER = PC.PRINTER,
MONITOR = PC.MONITOR,
Variant Table CS
CPU = PC.CPU).
INFERENCES:
Characteristic: PRINTER MONITOR
PC.PRINTER,
Key?
X
X
PC.MONITOR,
PC>CPU.
Inkjet
20”

Allowed
Values:

_________________________________
_________________________________
_________________________________
_________________________________

CPU
X

_________________________________

Standard

_________________________________

Laser_1

21”

Medium

Laser_2

24”

Fast

Result: If each characteristic is a key (no ambiguity),
only one characteristic value needs to be assigned in
order to infer the other two

_________________________________
_________________________________
_________________________________
30

Object Dependencies: Variant Functions

_________________________________

You can call a function module (ABAP program) in a
dependency
Procedure:
Œ
Œ
Œ
Œ

_________________________________
_________________________________
_________________________________

Define input and output characteristics
Define an ABAP program (function module)
Create a function that calls the ABAP program
Enter the function in a dependency (a procedure, for example)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
31

What We’ll Cover…








Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM
and OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
32

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Configuration Scenarios


_________________________________

Variant Configuration is not limited to configuring the
header material
Typically, subassemblies can be configured as well
The corresponding materials will be set accordingly
(configurable material, super BOM, configuration
profile, etc.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

KMAT

_________________________________

car
KMAT

interior

engine

_________________________________

body

_________________________________

KMAT

seats

dashboard

_________________________________
fabric

frame
33

Configuration Scenarios (cont.)

_________________________________

The configuration parameters section of the
configuration profile includes “Process” parameters and
“BOM explosion” parameters
The combination of the two determines the behavior of
the entire configuration process

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

34

Configuration Scenarios: Plnd/Prod Order Process

The final configuration is determined at Sales Order
entry during configuration (value assignment process)
Single or Multi-level configuration in the Sales Order
Œ
Œ


_________________________________
_________________________________

Header material is configured interactively
Lower-level configurable items (not only sales-relevant items)
can be configured interactively (if explosion)

_________________________________
_________________________________

Pricing at header material level
No Order BOM:
Œ

_________________________________

_________________________________
_________________________________

Only value assignment in the configuration process
determines the BOM components

_________________________________

One (or more) lines in the Sales Order, and one (or
more) new BOMs with reference to the line item
Examples:
Œ

_________________________________
_________________________________

Automobiles, bicycles, catalogue furniture, …
35

Configuration Scenarios: Sales Order (SET)

Usage: kits (or sets)
As in Plnd/Prod Order, the final configuration is
determined at Sales Order entry during configuration
(value assignment process)
(No single) multi-level configuration in the Sales Order
Œ


_________________________________
_________________________________
_________________________________
_________________________________

Header material is configured interactively, as well as lower
level configurable items (but only sales-relevant items)

_________________________________

Pricing at header material level or at sub-item level
No Order BOM:
Œ

_________________________________

_________________________________
_________________________________

Only value assignment in the configuration process
determines the BOM components

_________________________________

Several lines in the Sales Order
Examples:
Œ

_________________________________

PC packages (PC + printer + bag + software), …
36

Configuration Scenarios: Order BOMs

_________________________________

Two-step process:

_________________________________

1. Sales (VA01)

Header material is configured interactively
f No Order BOM yet
2. Technical Order processing (Order BOM maintenance CU51)
f Configuration of sub-levels
f Any component can be changed, deleted, copied, or added
f Order BOM created
f



One line in the Sales Order, and one (or more) new
BOMs with reference to the line item (Order BOMs)
Pricing at header material level only
Examples:
Œ

More complex Made-To-Order items, such as heavy
machinery, aircraft, configurable kitchens, etc.

Œ

_________________________________
_________________________________
_________________________________

_________________________________
_________________________________
37

_________________________________

Two ways of saving the configuration results:
Œ

_________________________________

_________________________________

Configuration Scenarios: More on Order BOMs

_________________________________

_________________________________

Knowledge-based:
f Super BOM + value assignment + Object dependencies +
manual changes
f Performance-intensive
Result-oriented:
f Order BOM + manual changes

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
38

Configuration Scenarios: More on Order BOMs (cont.)

Other settings:
Œ

_________________________________
_________________________________

Automatic Fixing: Create Order BOM after configuration in
Sales Order processing (vs. after technical processing,
using CU51)

_________________________________
_________________________________

Maintenance in Order Allowed:
Œ

_________________________________

Allows for technical processing during Sales Order
processing

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
39

Configuration Scenarios: More on Order BOMs (cont.)

Fixing:
Œ

Œ

Œ

_________________________________
_________________________________

Order BOMs are saved after technical processing (CU51) even
if no changes occurred
Fixing parameters determines which assemblies in the BOM
structure you want to create order BOMs for
Scope of fixing: selected assembly, top-down or bottom-up

_________________________________
_________________________________
_________________________________
_________________________________

Instantiation (result-oriented only):
Œ

Œ
Œ

If the same configurable material occurs more than once in
the BOM structure (example: 2 DVD players in the PC), how do
you differentiate (risk of confusion)?
Instantiation creates separate material master records
Scope of instantiation: selected assembly, top-down, or
bottom-up

_________________________________
_________________________________
_________________________________
_________________________________

40

Configuration Scenarios: Summary

_________________________________

BOM EXPLOSION
Process

None

Plnd/
Prod.
Order

Single-level (header) configuration
BOM explosion (and dependencies
for subs) in MRP only
One main item in Sales Order

Sales
Order
(SET)

Order
BOM

Single-level

_________________________________
Multiple-level

Multi-level, interactive configuration (all items)
Pricing at Header level
One or more lines in Sales Order (linked to main item)
No Order BOM

N/A

“SET” or “KIT” (example: PC package)
Multi-level, interactive configuration (sales-relevant
items only)
Pricing at main item (header) or sub-item level
Several lines in Sales Order (linked to main item)
No Order BOM

N/A

Two-step process: Sales Order and BOM processing
In sales order, single-level configuration (standard) and
no BOM explosion
In BOM maintenance, multi-level configuration, with
manual changes possible (add, delete, or change items)
Pricing at header level only
41

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

What We’ll Cover…








_________________________________

Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
42

Planning for VC

Œ
Œ
Œ

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Four main planning methods:
Œ

_________________________________

_________________________________

Planning at Assembly level
Standard product planning (characteristic-based planning)
Assembly planning with characteristics planning
Planning with planning variants

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
43

Planning for VC: Planning at Assembly Level

_________________________________

Concepts:
Œ
Œ
Œ

Œ

_________________________________

Typical Make-To-Order strategy
Assembly is kept in stock
Planned Independent Requirements entered at assembly
level
When planned orders/production orders are created for the
finished product, dependent requirements/reservations are
cleared against the Planned Independent Requirements

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
44

Planning for VC: Planning at Assembly Level (cont.)

_________________________________

Settings:

_________________________________
Configurable
Finished product
Strategy: 25

_________________________________

Material Master
ƒ Strategy: 70
ƒ Individual/collective requirements = 2
ƒ Mixed MRP indicator

Assembly
Strategy: 70

_________________________________

Assembly
70

_________________________________
_________________________________
_________________________________

+•
-•
-•

No forecast required for header material
Where to get figures for assembly requirements
Large data entry effort

_________________________________
_________________________________
_________________________________
45

Planning for VC: Standard Product Planning

_________________________________

Concepts:
Œ

Œ

Œ

_________________________________

Planning is done at configurable product level (Planned
Independent Requirements)
Non-convertible Planned Orders are created, with dependent
requirements for components according to usage
probabilities of the characteristic values
Incoming Sales Orders consume the configurable material’s
independent requirements

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
46

Planning for VC: Standard Product Planning (cont.)

_________________________________

Settings:
Œ
Œ

Œ

Œ

Strategy 56 for configurable product
Create and maintain planning
(combination) tables (MDP1)
f Same as variant tables
Create and maintain planning
profiles (MDPH)
f Which characteristics are
relevant to planning?
Create planned independent
requirements
f Define planned frequency/usage
probability of characteristic
values

_________________________________
Configurable
Finished product
Strategy: 56

_________________________________
_________________________________

Assembly

Assembly

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
47

Planning for VC: Standard Product Planning (cont.)
+•

Reduction of data entry effort
Œ

-•

_________________________________
_________________________________

Caution: depends on number of characteristics values
affecting planning

_________________________________
_________________________________

Secondary requirements are consumed according to
values assigned in planning (not values in the Sales
Order)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
48

Planning for VC: Assembly Processing with Characteristics
Planning

Concepts:
Œ

Œ

Œ

Œ

_________________________________
_________________________________

Same as previous strategy: Planning is done at configurable
product level (Planned Independent Requirements, or PIRs),
based on characteristic (usage probability), except that the
PIRs are inactive
Long-term planning is used to create dependent requirements
for the assemblies
These dependent requirements are then activated (transferred
from the planning scenario)
Therefore, the secondary requirements are consumed based
on actual sales (vs. planned usage)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
49

Planning for VC: Assembly Processing with Characteristics
Planning (cont.)

Settings:
Œ
Œ



Strategy 89 for configurable product
Strategy 70 for assembly

Create and maintain combination
tables and planning profiles
Create and run long-term-planning
scenario
Copy simulated dependent
requirements (MS66) Πactive
dependent requirements
Incoming Sales Order ΠProduction
Order ΠDependent Requirements
consume Dependent Requirements
in planning

_________________________________
_________________________________

Configurable
Finished product
Strategy: 89
Assembly
Strategy: 70

_________________________________
_________________________________

Assembly

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
50

Planning for VC: Assembly Processing with Characteristics
Planning (cont.)
+•
+•
-•
+•

Advantages of all strategies
Less planning effort, but …
… more steps involved (Long-Term Planning)
More precise consumption of planned requirements

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

51

Planning for VC: Planning with Planning Variants

_________________________________

Concepts:
Œ

Œ

Œ
Œ

_________________________________

Use material variants (e.g., a Make-to-Stock product based on a
specific configuration of a configurable material)
Create Planned Independent Requirements for the planning
variants
Dependent requirements are created for the assembly
Incoming Sales Orders trigger Planned Independent
Requirement consumption based on Type Matching (weighting
of characteristics)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
52

Planning for VC: Planning with Planning Variants (cont.)

_________________________________

Settings:
Œ
Œ
Œ
Œ

_________________________________

Strategy 54 for the configurable material and the variants
Assign characteristic values in MRP3 view of planning variant
Define settings for Type Matching (see next slide)
Maintain Planned Independent Requirements for planning
variants
Configurable
Finished product
54
Assembly

Planning
Variant I
54

_________________________________
_________________________________
_________________________________
_________________________________

Planning
Variant II
54

_________________________________
_________________________________

Assembly

_________________________________
_________________________________
53

Planning for VC: Planning with Planning Variants (cont.)

Problem:
Œ

_________________________________
_________________________________

If a Sales Order configuration
does not match a Planning
Variant at 100%, which
Planning Variant should the
Planned Independent
Requirements be consumed
from?

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Solution:
Œ

Œ

_________________________________

Characteristics are given Weighting Factors in Type Matching
settings (transaction MDPV)
The order consumes the planned requirements for the
planning variant with the highest sum of weightings

_________________________________
_________________________________
54

What We’ll Cover…








_________________________________

Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
55

Engineering Change Management (ECM)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Variant Configuration object changes (Classes,
Characteristics, BOMs, Routings, Dependencies,
Configuration Profiles, etc.) can be managed with ECM
ECM will control and activate planned changes to the VC
model through a Change Master Record (Change
Number) or through Engineering Change Requests and
Orders (ECR and ECO)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

56

ECM and Order Change Management (OCM)

The Change Master Record (or ECR/ECO) controls:
Œ
Œ
Œ
Œ

_________________________________
_________________________________

Which objects can be changed (specific objects)
Valid-from date of the change
Reason for changes
Status

_________________________________
_________________________________
_________________________________

Planned changes can affect existing Sales Orders and
production orders: You then need OCM

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
57

OCM

Restriction:
Œ

Œ

_________________________________
_________________________________

Effective change objects:
f Material BOM
f Order BOM
f Routing
Not supported in OCM (up to ECC 5.0):
f Material Master, Work Centers, changes to quantities or
dates in Sales Orders, …

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Prerequisite (settings):
Œ

Œ

_________________________________

Overall change profile (in IMG) assigned to Material (Work
Scheduling view)
Requirements Class must be “EC mgt” flagged (in IMG)

_________________________________
_________________________________
58

OCM (cont.)

_________________________________

Process
Œ

Œ

Œ

_________________________________

Sales Order or Master Data are changed using an ECM
Change Number
Transaction COCM:
f Determination of Production Orders affected by that
change
Transaction COCM1:
f Simulation of a Production Order (based on that change)
f Comparison with active production orders
f Identification of changes, check whether they are allowed
f Change Production Orders

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
59

What We’ll Cover…








_________________________________

Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
60

SCE/IPC: Overview

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

You need VC configuration methods to be available on
the Internet or for field sales without being permanently
online with SAP ERP (R/3 or SAP ECC)
SCE/IPC can be used as product configurator for
Internet sales applications (online store, CRM scenarios)
by synchronizing your modeling in ERP
It has a separate database and has open architecture
(Java application, APIs)
It can therefore be integrated with third-party systems

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

61

SCE/IPC: Architecture

_________________________________

Separation between user interface and configuration
server:

_________________________________
_________________________________

Standard User
Interface

_________________________________

SCE APIs

IPC
SCE

_________________________________
_________________________________

Knowledge Base
Pricing Data

_________________________________
_________________________________

Knowledge Base
and Pricing
(IDoc)

_________________________________
_________________________________

SAP ERP
or SAP CRM
62

SCE/IPC: Process

Modeling in SAP R/3 or ECC
Creating a knowledge-base object (CU31)
Œ

Œ

_________________________________
_________________________________

Collects all the information about a model:
f Material master, BOM, classes,
characteristics, dependencies, …
A KB object is like a list of pointers to the
data required

_________________________________
_________________________________
_________________________________
_________________________________

Creating one (or more) runtime versions
Œ

_________________________________

Based on a knowledge-base object

_________________________________

Downloading the runtime version to the
SCE database
Configuring in the SCE

_________________________________
_________________________________
63

What We’ll Cover…








_________________________________

Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
64

Performance

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

_________________________________

Performance can be an issue in VC models
This section presents some hints and tips on how to
improve performance

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
65

Performance (cont.)

As few configuration levels as possible
Keep configuration model small:
Œ

_________________________________
_________________________________

Several small models are better than a single large model

_________________________________

Separate BOMs (to restrict the number of levels in the
BOM explosion in SD)
Œ
Œ

_________________________________

_________________________________

For configuration in SD (application SD01), and
For MRP and Production Order (application PP01)

_________________________________
_________________________________

In Task Lists (Routings): alternative sequences instead
of several consecutive operations with the same
selection conditions
Œ
Œ

_________________________________
_________________________________

Assign the selection condition to the sequence
May need a dummy operation in the standard sequence

_________________________________
66

Performance (cont.)

_________________________________

In the configuration profile:
Œ
Œ

_________________________________

Restricts allowed screens on the interface design
“On request” better than “Permanent”

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
67

Performance (cont.)

Default values: quicker if defined in the characteristic
than if set by dependencies
Class nodes (class item in BOM)
Œ
Œ

_________________________________
_________________________________
_________________________________
_________________________________

Minimize number of characteristics
If few materials, use separate material items (with
dependencies) instead of class nodes

_________________________________
_________________________________

Using constraints:
Œ
Œ
Œ

Œ
Œ

_________________________________

Minimize the number of nets
Use the CONDITION section
Set up the CONDITION as “disjunctive standard form”
f Example: not a or not b (instead of not [a and b])
Use characteristic variables
Enter what’s really needed in the INFERENCES section

_________________________________
_________________________________
_________________________________
68

Performance (cont.)

Transparent tables instead of variant tables
Œ
Œ
Œ

_________________________________

Create a custom transparent table
Link variant table to database table
Data transfer to database table

_________________________________
_________________________________

Define global dependencies if used more than once
(local dependencies must be loaded several times)
Value check using function module, instead of:
Œ
Œ
Œ

_________________________________

_________________________________
_________________________________
_________________________________

Preconditions
Restrictable characteristics with constraints
Variant tables

_________________________________
_________________________________

Do not mix procedures (actions) and constraints (value
inferences should not influence each other)

_________________________________
69

Client Management

_________________________________

VC models are Master Data
Master Data cannot be transported (DEV ΠTEST ΠQA
ΠPROD)
How do you (safely) change your models?
Œ

Œ

_________________________________
_________________________________
_________________________________
_________________________________

Set up a VC “Golden Client,” containing all the objects
relevant to VC
Transport data using data distribution with Application Link
Enabling (ALE)
f Using SAP standard Message Types (IDocs)
f Transport sequence predetermined

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
70

VC Projects: Modeling Guidelines

What are the products?
Œ
Œ
Œ

_________________________________
_________________________________

One product with millions of variants?
Millions of products without variants?
A middle way?

_________________________________
_________________________________

Single-level or multi-level?
Œ

Œ

_________________________________

Can lower-level configurable materials be determined from the
configuration of the header material?
Modeling tips

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

71

VC Projects: Modeling Guidelines (cont.)

Customer viewpoint vs. production viewpoint
Œ

_________________________________
_________________________________

Kitchen example:
f Production looks at the individual closets
f Closets are assembled at customer premises
f The “Kitchen” level is not relevant to production

_________________________________
_________________________________
_________________________________

Characteristics – what not to do:
Œ

Œ

Two (or more) characteristics representing the same attribute
f Example: One characteristic for horsepower, one for
kilowatt
Although, different allowed values or meanings in one
characteristic
f Example: The length of a ship and the length of a
microprocessor must not be represented by the same
characteristic
72

What We’ll Cover…








Introduction: Variant Configuration (VC) concepts review
Material Variants (Type Matching) and Variant Pricing
(SD, MM)
More on Object Dependencies
Configuration scenarios
Planning for VC
Engineering and Order Change Management (ECM and
OCM)
Sales Configuration Engine (SCE) and Internet Pricing
and Configuration (IPC)
Miscellaneous: Performance, client management, and
modeling tips
Wrap-up
73

Œ

_________________________________

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

SAP Help Œ Enterprise Central Component Œ Logistics Œ
Logistics General (LO) ΠVariant Configuration (LO-VC)
http://help.sap.com/saphelp_erp2005/helpdata/en/92/58d45541
7011d189ec0000e81ddfac/frameset.htm

_________________________________
_________________________________
_________________________________
_________________________________

SAP VC User Group
www.configuration-workgroup.com

_________________________________

Œ

_________________________________

SAP Notes:
Œ
Œ

_________________________________

Configuration Workgroup (CWG)
Œ

_________________________________

_________________________________

help.sap.com
Œ

_________________________________

_________________________________

Resources

_________________________________

_________________________________

148778 and 502425: Header/component combination of
scenarios
660269: Error in Help

_________________________________
_________________________________

SAP PLM146 course “Variant Configuration: Scenarios
and Enhancements”
74

7 Key Points to Take Home

_________________________________

You now have an overview of endless VC possibilities
(and resulting complexity)
It is particularly important that you understand Planning
and Configuration Scenarios
There are always many ways to solve your problem, but
only one will be optimal
Modeling (in blueprint) is done on paper (Excel, etc.) and
is more than ever crucial to the success of the project
SAP VC is more an art than a science

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

75

7 Key Points to Take Home (cont.)

_________________________________

Remember that SAP VC spans the entire organization
(Sales, Engineering, Production, etc.)
“If I’m told, I forget. If I’m shown, I remember. If I do it, I
understand.”
Now you need to understand more … on your own!

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
76

Your Turn!

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

How to contact me:
Jean-Yves Popovic
jypopovic@adelante-tm.com

_________________________________
_________________________________
77

Notes:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026

Copyright © 2008 Wellesley Information Services. All rights reserved.

Sign up to vote on this title
UsefulNot useful