Variant Configuration (With AVC) in Sap S/4Hana: Participant Handbook

S4105
Variant Configuration (with AVC) in

SAP S/4HANA
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 20
Course Duration: 5 Day(s)
Material Number: 50158854
SAP Copyrights, Trademarks and
Disclaimers
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
American English is the standard used in this handbook.

The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iii

iv © Copyright. All rights reserved.
Contents
ix Course Overview
1 Unit 1: Introduction to Variant Configuration
2 Lesson: Introduction to Variant Configuration

11 Exercise 1: Working with a Fully Modeled Configuration Task
23 Unit 2: Classification Tools
24 Lesson: Characteristics Maintenance

33 Exercise 2: Manage Characteristics
40 Lesson: Class Maintenance
49 Exercise 3: Manage Classes
59 Unit 3: Materials, BOMs and Task Lists
60 Lesson: Material
65 Exercise 4: Manage Materials
79 Lesson: Material BOM
83 Exercise 5: BOM Maintenance (Without Dependencies)
90 Lesson: Task List
93 Exercise 6: Routing Maintenance (Without Dependencies)
107 Unit 4: Configuration Profile
109 Lesson: Classic and Advanced Variant Configuration

114 Lesson: Configuration Profile
125 Exercise 7: Create And Test A Configuration Profile
133 Unit 5: Overview of Object Dependencies
135 Lesson: Use and Types of Dependencies

141 Lesson: Paradigms of the SAP Configurator and Introduction to the
Syntax
151 Lesson: Variant Tables, Functions and PMEVC
163 Unit 6: Object Dependencies in BOMs and Task Lists
164 Lesson: Selection Condition in BOMs and Task Lists

169 Exercise 8: Material BOM: Object Dependencies
197 Exercise 9: Routing: Object Dependencies
214 Lesson: Class Nodes
217 Exercise 10: Maintain Class Nodes
229 Lesson: Procedures with Reference Characteristics (Quantity and
Time Change)
233 Exercise 11: Change the Component Quantity (Reference
Characteristics)
© Copyright. All rights reserved. v

251 Unit 7: Dependencies for the Value Assignment Interface - 1
252 Lesson: Interface Design, Characteristic Grouping and PMEVC

257 Exercise 12: Table Constraint Using a Wizard
263 Lesson: Constraints: An Introduction
268 Lesson: Constraints: First Details
277 Exercise 13: Constraint: A Simple Example
283 Exercise 14: Optional: Constraint in a Multilevel Configuration
with Additional Modeling Steps
303 Unit 8: Dependencies for the Value Assignment Interface - 2
304 Lesson: Procedures for Value Assignment Interface

311 Exercise 15: Default Values with Procedures (With / Without
Variant Tables)
323 Lesson: Facet Changes with Pre- and Selection Conditions
329 Exercise 16: Pre- and Selection Conditions for Characteristics
and Values
339 Unit 9: Variant Configuration in Pricing
340 Lesson: Pricing and Variant Configuration in Sales

345 Exercise 17: Modeling of Value-Dependent Pricing in Sales
Orders
355 Exercise 18: Pricing with $set_pricing_factor
363 Lesson: Pricing and Variant Configuration in Purchasing
367 Unit 10: Material Variants
368 Lesson: Material Variants

373 Exercise 19: Material Variants with Pricing, Material BOM and
Routing
391 Unit 11: VC – Integration Logistic Chain
393 Lesson: Processes in SD

405 Lesson: Processes in Planning and Production
409 Exercise 20: Process for Quotation → Order → Planning →
Production
423 Unit 12: Product Structure
424 Lesson: Product Structure

433 Exercise 21: Overview: Product Structure Management
443 Unit 13: Configuration Profil: Transfer Classic (LO-VC) into Advanced
Scenario (AVC)
445 Lesson: Transfer Classic into Advanced Scenario
vi © Copyright. All rights reserved.

455 Unit 14: Appendix
457 Lesson: Knowledge Base and Runtime Version

465 Exercise 22: Knowledge Base and Runtime version
471 Lesson: Master Data Changes with Engineering Change
Management
479 Exercise 23: Master Data Changes with ECM
497 Lesson: Order Change Management
503 Exercise 24: Order Change Management
515 Lesson: Data for Exercises, Additional Slides
531 Lesson: Data for Exercises
© Copyright. All rights reserved. vii

viii © Copyright. All rights reserved.
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Super / Key / Power User
● Business User
● Business Analyst
● Business Process Architect
● Business Process Owner/Team Lead/Power User
● Solution Architect
© Copyright. All rights reserved. ix

x © Copyright. All rights reserved.
UNIT 1 Introduction to Variant
Configuration
Lesson 1
Introduction to Variant Configuration 2
Exercise 1: Working with a Fully Modeled Configuration Task 11
UNIT OBJECTIVES
● Give an introduction to Variant Configuration

● Identify four configurable object types
● Create sales order for a configurable material
© Copyright. All rights reserved. 1

Unit 1
Lesson 1
Introduction to Variant Configuration
LESSON OVERVIEW
Business Scenario
Your company produces or sells products with different designs. You decide to use the
variant configuration of the SAP system to reduce the effort and warehouse management
costs. Also, you would like to maintain all possible product variants.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Introduction to Variant Configuration
Figure 1: Customer — Inquiry — Quotation — Sales Order
2 © Copyright. All rights reserved.

Lesson: Introduction to Variant Configuration
Variant Configuration in SAP ERP lets you check the following as soon as you relate a sales
order:
● Whether the required variant can be produced (only variants that are technically possible
can be ordered)
● What price you can quote for the product
● Whether the customer's specifications can be covered from stock
● And so on
Figure 2: Variant Configuration: Knowledge Base for Materials
Animation: Variant Configuration: Knowledge Base for Materials

For more information on Variant Configuration: Knowledge Base for Materials ,
please view the animation in the lesson Introduction to Variant Configuration in
your online course.
The following objects make up the knowledge base of a configured material:

The material master is where the configurable attribute is defined along with some additional
planning and control data.
Characteristics and values must be created in the classification system and collected in
variant classes (class type 300).
The configuration profile contains control data for the configuration process and result.
A super BOM must be created that contains all standard components and all possible variable
components, as well as assemblies that are required to configure a variant product.

Unit 1: Introduction to Variant Configuration
A super task list must be created that includes all operations, suboperations, sequences, and
production resources and tools (PRTs) required to manufacture all possible variants.
Pricing condition records must be created for pricing the configurable material.
There are five different types of object dependencies which can be used during the
configuration process. Dependencies provide the rules or logic for the configuration process.
Configurable materials are often used in specific industry sectors, such as aerospace and
defense, the automotive industry, make-to-order production, assemble-to-order production,
and the hi-tech industry.
Figure 4: Configurable Fork Lift
Example: Configurable Forklift

Products with a large number of features and options have a large range of possible variants.
Without additional restrictions, the example shown could produce 19,440 variants.
In practice, there are restrictions in the form of rules that reduce the number of possible
options. These rules must be defined and applied during the configuration process.
Complex products are reflected in complex configuration tasks for sales and production.
However, a company that sells or produces products with variants needs to perform these
tasks quickly and accurately. As the development cycles and life cycles of products become
shorter and shorter, this is becoming increasingly difficult.
How many data records had to be created and maintained without variant configuration in the
SAP system? In the example above, up to 19,440 material masters, BOMs, task lists, costing
records, pricing records, and so on.
Configurable Product is the general term for a product that has a large number of variants.
The features that are used to create complex products are stored in the SAP system as
characteristics and values.

Figure 5: Configurable Product, Class, Class Type
A configurable material needs a material master record to do the following:

● Store important planning and control data.
● Link the product to other objects in the variant configuration data model by assigning it to
a variant class.
In variant configuration, a variant class groups together the set of characteristics that
describe a configurable material.
You can only use variant classes or class nodes to group together characteristics for this
purpose. The class type of a class determines whether the class is a variant class or class
node. In the standard system, only classes of class type 300 are variant classes. Classes of
class type 200 are class items (class nodes). In Customizing for classification, you can define
further class types – including class types for variant classes.

Figure 6: Configurable Product, Class and Characteristics
Animation: Configurable Product, Class and Characteristics

For more information on Configurable Product, Class and Characteristics, please
view the animation in the lesson Introduction to Variant Configuration in your
online course.
You define the features of a product in the SAP system by defining characteristics. You define
values for each characteristic, and use these values to describe the customer's requirements.
You assign the characteristics that describe your configurable product to the variant class.
The configurable material is assigned to the variant class. By assigning the configurable
material to the class, you are able to configure the product using the characteristics of the
class.

BOM Forklift
Figure 8: Super BOM Fork Lift
You use the BOM to define which parts can be used in a configurable material. You create a
super BOM for the configurable material, containing parts that may be used in specific
variants only (variable parts) and parts that are required in all variants (non-variable parts).
This BOM can contain items that are in themselves configurable materials (multi-level
configuration).
Figure 9: Bill of Material: Fork Lift

Animation: Bill of Material: Fork Lift

For more information on Bill of Material: Fork Lift, please view the animation in
the lesson Introduction to Variant Configuration in your online course.
You can use preconditions to check the consistency of the values you assign. This allows you
to ensure that only valid combinations of values appear and can be selected in configuration.
You can also use selection conditions to determine that a specific BOM item and operation
must be selected if a certain value is assigned. This allows you to determine which seat, seat
back and extras must be selected.
Figure 11: Routing: Fork Lift
Animation: Routing: Fork Lift

For more information on Routing: Fork Lift, please view the animation in the
lesson Introduction to Variant Configuration in your online course.
The routing of a configurable material:

● Has one standard sequence
● May have one or more parallel and alternative sequences
● Comprises operations, which can have suboperations
● May have production resources/tools (PRTs) assigned to operations
You can use object dependencies to determine the extent to which sequences (except the
standard sequence), operations, suboperations, and PRTs are required for each variant to be
produced, and whether they can be used in exactly this form.

Figure 13: Interdependencies Between Objects in the Model
Figure 14: Other Configurable Object Types


Unit 1
Exercise 1
Working with a Fully Modeled Configuration
Task
Simulation: Working with a Fully Modeled Configuration Task

For more information on Working with a Fully Modeled Configuration Task,
please view the simulation in the lesson Introduction to Variant Configuration in
your online course.
Business Scenario
Modeling for configuration tasks is complete for the forklift described below. You now want to
test the result.
Task 1: Presettings
Before you perform the exercise, configure some presettings.
1. Make the OK code visible in your SAP Fiori Launchpad. Also, display the key information
inside drop down lists.
Start the SAP Fiori Launchpad using the following data:
User: S4105–##
Password: Welcome1
Language: EN
Note:
Please replace ## by your group number, assigned by your instructor.
Open the group Classification and start the app Manage Characteristics.
Now navigate as follows: More → GUI- Actions and Settings → Settings. Select tab page
Interaction Design → Visualization and set the box Show OK -Code-Field, the box Show
Buttons with Icons * , and both boxes for Drop Down Lists.
Save. Open the Home screen.
2. Change some SAP GUI settings.

Start the SAP logon pad. Do not login at this time.
Select the icon on the left header side. In the drop down area, select the entry Options.
Now open the following area:

Visual Design → Theme Settings → Select Theme → “Belize theme “ or " SAP Signature
Theme" .. For " SAP Signature Theme" maybe deselect “Use Corbu style icons”.
In the area Interactions Design select Visualization 1 → “Controls”. Define the indicator for
both boxes.
Depending on your choice, deselect the extended search inside Visualization 2.
Close your SAP Logon Pad and restart it.
3. Login to SAP GUI.

Select the system T41, the Backend system.
Enter the following data:
Client: 400
User: S4105–##
Password: Welcome1
Language: EN
Task 2: Create a Sales Order

Create a sales order for a configurable material T-FCL00. Familiarize yourself with the views
and functions of the configuration user interface.
1. Start the app Create a Sales Order. Enter the following values:
Order Type: OR
Sales Organization: 1010
Distribution channel: 10
Division 00
Press the Continue button. Enter the following values:

Sold to party: T-C400
Cust. Reference: your choice
Material: T-FCL00
Order quantity: 1 PC
The system opens the characteristics value screen for Variant configuration.
2. Select the characteristic values of your choice. Use click for selecting the values.
3. What are the values for Engine Performance, when no Type of Drive is selected?
4. What are the values offered for the Engine Performance, if type of drive Diesel is selected?
5. Could you see the values for the variant conditions?

Could you change the values for the variant conditions?
6. Display the object dependency using the characteristic Tonnage Capacity.

7. Check the characteristic values assignment screen and check the pricing conditions.
Open the pricing view.
8. Select Done and then the Apply button of the Review Availability Check Result and open
the overview screen of your sales order.
How many items are there?
What is the net value?
What are the value-dependent surcharges?
What is the total value?
Exit the sales order without saving.

Unit 1
Solution 1
Working with a Fully Modeled Configuration
Task
Simulation: Working with a Fully Modeled Configuration Task

For more information on Working with a Fully Modeled Configuration Task,
please view the simulation in the lesson Introduction to Variant Configuration in
your online course.
Business Scenario
Modeling for configuration tasks is complete for the forklift described below. You now want to
test the result.
Task 1: Presettings
Before you perform the exercise, configure some presettings.
1. Make the OK code visible in your SAP Fiori Launchpad. Also, display the key information
inside drop down lists.
Start the SAP Fiori Launchpad using the following data:
User: S4105–##
Password: Welcome1
Language: EN
Note:
Please replace ## by your group number, assigned by your instructor.
Open the group Classification and start the app Manage Characteristics.
Now navigate as follows: More → GUI- Actions and Settings → Settings. Select tab page
Interaction Design → Visualization and set the box Show OK -Code-Field, the box Show
Buttons with Icons * , and both boxes for Drop Down Lists.
Save. Open the Home screen.
a) Choose the Windows Start button. The SAP Fiori Launchpad app becomes visible.
Select the app. When you do this for the first time, a Chrome Welcome window
becomes visible. Always select Chrome.
b) Login using the data in the table.
c) Open the Classification group and start the app Manage Characteristics.

d) Now navigate as follows: More → GUI-Actions and Settings → Settings . Select tab
page Interaction Design → Visualization and set the box Show OK -Code-Field , the box
Show Buttons with Icons * and both boxes for Drop Down Lists.
e) Save.
f) Go back to the Home screen.
2. Change some SAP GUI settings.

Start the SAP logon pad. Do not login at this time.
Select the icon on the left header side. In the drop down area, select the entry Options.
Now open the following area:
Visual Design → Theme Settings → Select Theme → “Belize theme “ or " SAP Signature
Theme" .. For " SAP Signature Theme" maybe deselect “Use Corbu style icons”.
In the area Interactions Design select Visualization 1 → “Controls”. Define the indicator for
both boxes.
Depending on your choice, deselect the extended search inside Visualization 2.
Close your SAP Logon Pad and restart it.
a) Open the SAP logon pad. Do not perform a login at this time.
b) Select the icon on the left header side. In the drop down area, select the entry Options.
c) Now open the following area: Visual Design → Theme Settings → “Belize Theme “ . For
" SAP Signature Theme" maybe deselect Use Corbu style icons.
d) In the area Interactions Design, select Visualization 1 → “Controls”. Define the indicator
for both boxes.
e) Depending on your choice, deselect the Enhanced Search inside Visualization 2
f) Choose Apply and OK. Close your SAP Logon Pad and restart it. Your changes should
be visible.
3. Login to SAP GUI.

Select the system T41, the Backend system.
Client: 400
User: S4105–##
Password: Welcome1
Language: EN
a) Select the system T41 inside your SAP logon pad.
b) Double click on it and enter your login credentials.

Create a sales order for a configurable material T-FCL00. Familiarize yourself with the views
and functions of the configuration user interface.
1. Start the app Create a Sales Order. Enter the following values:

Order Type: OR
Distribution channel: 10
Division 00
Press the Continue button. Enter the following values:

Material: T-FCL00
Order quantity: 1 PC
The system opens the characteristics value screen for Variant configuration.
a) Create a sales order for material T-FCL00.
Use the following menu path:
SAP Fiori Launchpad → group “Sales Add On” → Tile “Create Sales Order”
Add the following data in the initial screen and the header area of your sales order:
Order Type: OR
Distribution channel 10
Division 00
Then press enter on your keyboard.
Sold to party T-C400
Material: T-FCL00
Order quantity 1 PC
b) Press Enter
2. Select the characteristic values of your choice. Use click for selecting the values.
a) Select the characteristic values with click.
3. What are the values for Engine Performance, when no Type of Drive is selected?
a) 18, 25, 30, 45 and 55 kW
4. What are the values offered for the Engine Performance, if type of drive Diesel is selected?
a) Only 30, 45 and 55
5. Could you see the values for the variant conditions?

Could you change the values for the variant conditions?

a) If you don't see the values for the variant condition, than Setting- Button → Show
hidden characteristics → Yes
b) No, you can't change the values for the variant conditions. This value was set through a
procedure and can not be changed. In order to avoid errors here, the characteristic
was not set ready for input.
Display the explanations for the variant condition. To do this, show the Inspector (=
Icon header area, right hand side.)
6. Display the object dependency using the characteristic Tonnage Capacity.

a) For additional information, use the inspector for the characteristic Tonnage Capacity.
For the sake of simplicity, click on the characteristic.
Using the inspector, open the 3rd tab page to display the object dependencies. On the
second, you find the characteristic values. Select the value 5000. The object
dependency is added.
Characteris- Tonnage Capacity Pre and selection condition AVC
tic:
Value: 5.000 precondition AVC
7. Check the characteristic values assignment screen and check the pricing conditions.
Open the pricing view.
a) Select the net value on top left of the screen to have a look at the conditions. Then
close the dialog.
Here you are able to display everything.
8. Select Done and then the Apply button of the Review Availability Check Result and open
the overview screen of your sales order.
How many items are there?
What is the net value?
What are the value-dependent surcharges?
What is the total value?
Exit the sales order without saving.
a) One the value assignment screen of your sales order, choose the button Done.
b) If the view Review Availability Check Result appears, than continue with the Apply
button.
You are back in the view "Create Standard Order Overview".
c) How many items are there?

One
d) What is the net value? Use the Item conditions button. It’s the 11th button.
The net value will differ depending on the characteristic values that were selected or
set using dependencies.
Basic price for the fork lift: 30.000 €
Surcharge: 70 € for each 100 kg counterbalance

Surcharge: 100 € for the road set
Surcharge: 90 € for the additional lights
e) What are the value-dependent surcharges?

The value-dependent surcharges will differ depending on the characteristic values that
were selected or set using dependencies.
f) What is the total value?

The total value will differ depending on the characteristic values that were selected or
set using dependencies. It is the Price plus any variant surcharges minus any
discounts.
g) Exit the sales order without saving.

LESSON SUMMARY
You should now be able to:


Unit 1
Learning Assessment
1. Which configurable object types exist?

Choose the correct answers.
X A Material
X B Material BOM
X C Routing
X D General maintenance task list
X E Standard network
X F Model service specification
2. What is important when creating sales orders with configurable materials?

Choose the correct answer.
X A Nothing. The system automatically recognizes that these are configurable

materials.
X B You must use special apps or transactions for sales orders with configurable
materials.
X C You must flag this as configurable when assigning the configurable material to the
sales order.

Unit 1: Learning Assessment

UNIT 2 Classification Tools
Lesson 1
Characteristics Maintenance 24
Exercise 2: Manage Characteristics 33
Lesson 2
Class Maintenance 40
Exercise 3: Manage Classes 49
UNIT OBJECTIVES
● Describe characteristics maintenance

● Explain the special features of characteristics maintenance for VC
● Work with reference characteristics and create a linkage to database tables and fields
● Maintain classes
● Assign objects to classes and search objects in classes

Unit 2
Lesson 1
Characteristics Maintenance
LESSON OVERVIEW
Business Scenario
Your company has decided to implement Variant Configuration. This solution is based on the
classification system. You must therefore define characteristics and characteristic values and
assign the characteristics to the classes.
LESSON OBJECTIVES
Characteristics Maintenance
Figure 16: Variant Configuration Knowledge Base for Materials

Lesson: Characteristics Maintenance
Animation: Variant Configuration Knowledge Base for Materials

For more information on Variant Configuration Knowledge Base for Materials,
please view the animation in the lesson Characteristics Maintenance in your
online course.
Characteristics and values and at least one variant class (class type 300) must be created in
SAP classification.
Figure 18: Screens: Characteristics
Naming conventions:
● Letters, figures, underscore, and hyphen
● Characteristic names must start with a letter
Characteristic names with a hyphen require a keyword when used in dependencies. If you use
a characteristic whose name contains a hyphen, you must use the expression SKEY to
address the characteristic in dependencies. Enter the characteristic name in single quotation
marks:
SKEY 'EXT-COLOR'.
Figure 19: Characteristic Status

Unit 2: Classification Tools
You can define additional statuses in Customizing for classification, if required.

You can also change existing statuses. The slide shows the standard settings.
Format / Data type for Values
Figure 20: Format / Data Type For Values
Animation: Format / Data Type For Values

For more information on Format / Data Type For Values, please view the
animation in the lesson Characteristics Maintenance in your online course.
Exponent
0: no exp. expression
1: standard 1, ... E-xx
2: predefined exponent 0, ... E- (Exponent entered)
3: scientifically ---,-- E-xx
Formats DATE, TIME can be queried in object dependencies. If you use the CURR format, the
currency itself is not taken into account in variant configuration.
You use the Entry Required indicator to define whether it is mandatory to assign a value to a
characteristic.

Characteristics: Additional Settings
Figure 22: Allowed Values: Value Assignment Type For Characteristics
Animation: Allowed Values: Value Assignment Type For Characteristics

For more information on Allowed Values: Value Assignment Type For
Characteristics, please view the animation in the lesson Characteristics
Maintenance in your online course.
Intervals can be restricted, unrestricted, closed, half open, or open.

For example: 100 - 200 , >100 , <= 100 , >100 - <200.
The allowed values and allowed intervals that you define are binding for value assignment,
unless you define that additional values are also allowed. However, you can restrict intervals.
You can overwrite characteristic values for a specific class.
Indicators: Single-value, Multiple values, and Restrictable.
The Single-value indicator means that only one value can be assigned to an object. If you
assign a class or other hierarchy node to a class, you can assign more than one value. This
serves to restrict the allowed values.
The Multiple values indicator means that you can assign more than one value during value
assignment.
The Restrictable indicator is for a special kind of single-value characteristic, which can only be
used in constraints.

Other Options for Characteristics Maintenance
Figure 24: Other Options for Characteristics Maintenance
In addition to constants and intervals, you can also enter characteristic values in the form of a
hierarchy, in order to structure the entry of characteristic values.
You can create a long text for a characteristic by choosing Documentation. On the Values tab,
you can create a long text for values of CHAR characteristics.
If you have defined a default value for a characteristic, you see this characteristic value
immediately in value assignment functions. You can decide whether to accept the default
value or select a different value.
Characteristics list:
You can use this function creates a list of all characteristics and characteristic values.
Where-used list for characteristics and characteristic values
For example, you can create a list of all objects here, to which a particular characteristic value
has been assigned. For example, you want to delete a value, but this is not allowed because
objects have already been assigned a value. The objects were valuated with this value.
In the class menu, choose Environment → Reporting → Where—Used List for
Characteristics / Characteristic values.
Enter the characteristic and the characteristic value.
Reference Characteristics

Figure 25: Reference Characteristics
Reference characteristics are characteristics that refer to table fields. You need reference
characteristics in configuration if you want to refer to the values of table fields in object
dependencies.
Basic data (such as format and length) is copied from the table field in the repository to the
characteristic.
Reference characteristics can fulfill two functions:
● Read-only access to table fields in conditions
● Changes to field contents with object dependencies
You create reference characteristics using the Additional data screen in characteristics
maintenance. Enter the table field to which you want the characteristic to refer. If you want to
refer to a table field in several tables, you can enter several tables. However, the format of the
field must be the same in all tables.

Reference Characteristics: Usable Tables
Figure 26: Reference Characteristics- Write Access
Animation: Reference Characteristics- Write Access

For more information on Reference Characteristics- Write Access, please view
the animation in the lesson Characteristics Maintenance in your online course.
To influence prices in sales we need a reference characteristic, that can be used to transfer
variant conditions. For this purpose you create an object characteristic - the field is called
VKOND, the table SDCOM.
In purchasing, field VKOND in table MMCOM is used for maintaining variant conditions.
In table PLPO, not all fields can be changed. Structure PLPO_CFMOD defines which fields can
be changed.
You can also use the table ESSL for reference characteristics for model service specifications
(analog to table PLPO).

Figure 28: Reference Characteristics- Read Only Access
You can use reference characteristics to refer to these sales order tables. However,
dependencies have read-only access to fields in these tables. You cannot use dependencies
to change field values.
More sales order tables are the addresses of partners VBADR_AG, VBADR_WE, VBADR_RE
and VBADR_RG.
For configuration of material variants you can also read the tables MARA, MARC and MAKT.


Unit 2
Exercise 2
Manage Characteristics
Simulation: Manage Characteristics

For more information on Manage Characteristics, please view the simulation in
the lesson Characteristics Maintenance in your online course.
Business Scenario
A basic requirement for setting up a variant model is to create the necessary characteristics
and values. In our modeling scenario, the following characteristics will be used:
Extras, driving seat and seat back for your forklift.
Create Characteristics
1. Create characteristics for your configurable product. Open the app Manage
Characteristics.
Characteristic: T_FCLX##
Description: Extras ##
Chars group: T-##
Status: Released
Data type: Character format
Number of Characters 1
Value Assignment Multiple Values!!!
Values: A Road Equipment
B Additional Lighting
C Rear View Camera
D Driving Mirror small
E Driving Mirror large
Hint:
Double check the box Value Assignment and the indicator for Multiple Values
on Basic Data screen. It’s necessary for later exercises.

Save your characteristic.
2. Create a second characteristic. Use the known navigation path. Enter the following values:
Characteristic: T_FCLG##
Description: Driving seat ##
Chars group: T-##
Status: Released
Format: Character format
Values: 1 fix
2 rotable
3. Create a third characteristic. Use the known navigation path. Enter the following values:
Characteristic: T_FCLH##
Description: Seat back ##
Chars group: T-##
Status: Released
Format: Character format (number = 1)
Values: 1 Standard
2 Standard with headrest
3 Extended

Unit 2
Solution 2
Manage Characteristics
Simulation: Manage Characteristics

For more information on Manage Characteristics, please view the simulation in
the lesson Characteristics Maintenance in your online course.
Business Scenario
A basic requirement for setting up a variant model is to create the necessary characteristics
and values. In our modeling scenario, the following characteristics will be used:
Extras, driving seat and seat back for your forklift.
Create Characteristics
1. Create characteristics for your configurable product. Open the app Manage
Characteristics.
Chars group: T-##
Status: Released
Value Assignment Multiple Values!!!
Values: A Road Equipment
C Rear View Camera
Hint:
Double check the box Value Assignment and the indicator for Multiple Values
on Basic Data screen. It’s necessary for later exercises.


a) Create a characteristic.
Use the following paths:
SAP Fiori Launchpad → group, Classification → Tile, Manage Characteristics.
Or, inside the backend system T41:
Start transaction code CT04 or use the menu path: SAP Easy Access menu → Cross
Application Components → Classification System → Master Data → Characteristics.
Chars group: T-##
Status: Released
Caution!!! box Value As- Multiple Values

signment
Characteristic values: A Road Equipment
C Rear View Camera
2. Create a second characteristic. Use the known navigation path. Enter the following values:
Chars group: T-##
Status: Released
Format: Character format
Values: 1 fix
2 rotable

a) Create a second characteristic.

Enter the following on the initial screen, in the area Basic Data and Values.
Chars group: T-##
Status: Released
Format: Character format (number= 1)
Values: 1 fix
2 rotable
b) Save your characteristic.
3. Create a third characteristic. Use the known navigation path. Enter the following values:
Chars group: T-##
Status: Released
Values: 1 Standard
3 Extended

a) Create a third characteristic. Use the known navigation path. Enter the following
values:
Chars group: T-##
Status: Released
Values: 1 Standard

3 Extended
b) Go back to the Home screen.

LESSON SUMMARY

Unit 2
Lesson 2
Class Maintenance
LESSON OVERVIEW
Business Scenario
Your company has decided to implement the variant configuration of the SAP system. This
functionality is rooted in the classification system. You must therefore define characteristics
and characteristic values and assign the characteristics to the classes.
LESSON OBJECTIVES
Class Maintenance
Figure 30: Classes in Variant Configuration
A class type is defined as a class type for variants or for class nodes in the control parameters
of Customizing.
In the standard system, you can define an existing class type for class nodes by setting an
indicator.
You can only create a new variant class type by creating a new class type.

Lesson: Class Maintenance
Figure 31: Screen: Classes
Basic data: You must set the status of a class. For example, in the standard system, the class
statuses for all class types are:
0 = In preparation (only class maintenance)

1 = Released (no restrictions)
2 = Locked (no classification allowed)
Characteristics:
● You can assign characteristics to your class. The sequence of the characteristics in the
class is also the sequence of characteristics that is displayed during configuration,
provided that no interface design is used. The characteristics describe the objects that you
classify in your class.
Additional data:
● You can maintain data for using the class as a BOM item for a configurable material (class
node).
Figure 32: Class Type

Animation: Class Type

For more information on Class Type, please view the animation in the lesson
Class Maintenance in your online course.
The class type has central control functions for class maintenance.
You cannot change the class type once you have saved a class.
You can define additional class types with different features in Customizing, if required.
Class statuses, classification statuses, organizational areas, text types, functions, and filters
are all defined based on class type.
Classification Functions
Figure 34: Classification Functions
Animation: Classification Functions

For more information on Classification Functions, please view the animation in
the lesson Class Maintenance in your online course.
Tasks of the classification system and sequence of your maintenance:
1. Define characteristics and allowed values
2. Maintain class, assigning characteristics to class
3. Classify objects (create objects, then from either master data or classification system,
assign objects to class and assign values)

4. Find objects
Figure 36: How to Classify Objects
Animation: How to Classify Objects

For more information on How to Classify Objects, please view the animation in
the lesson Class Maintenance in your online course.
The following functions for classifying an object in a class are supported:

● You can assign an object to one or more classes. You can either use the assignment
function Object to classes, objects of a class or inside Master records.
● The configurable material can also be maintained in the transactions of maintenance of the
configuration profile or inside the PMEVC.
● You can assign several objects to a class at once by using the Objects to Class assignment
function.

Class Node: Class Maintenance
Figure 38: Class Node: Class Maintenance
Required component: If this flag is set:

● It does not affect low-level configuration.
● Only affects high-level configuration if a BOM or configuration structure is exploded. (In
other words, not in sales, or in the sales view of the planned/production order scenario
without BOM explosion, or in the order BOM scenario.) You see an inconsistency message
if the system has not found any component in its attempt to replace the class node. The
configuration can only be saved with a status other than the status Released.
Multiple selection: If this flag is not set:

● It does not affect low-level configuration.
● Only affects high-level configuration if a BOM or configuration structure is exploded, and
the scenario used is either sales order with manual changes allowed, or order BOM. You
see an inconsistency message if the system has found more than one component in its
attempt to replace the class node. The configuration can only be saved with a status other
than the status Released. The inconsistency on the result screen can be resolved either in
sales order maintenance (sales order scenario with manual changes) or in technical post-
processing (order BOM scenario), by starting the search for an object by classification.
The Multiple selection flag should not be used. No inconsistency message would be
generated, and the configuration could be saved with status Released. You can really only
replace a class node with one material component.

Class Specific Changes to Characteristics
Figure 39: Class Specific Changes to Characteristics
You define the characteristics to be assigned to a class in characteristics maintenance

functions. However, there are cases where this central definition of characteristics is not
enough. In these cases, you can overwrite the characteristics of a class for the specific class.
These changes only apply to the characteristic in this class.
You can overwrite the indicators shown in the graphic. You can also change the allowed
values of a characteristic for a specific class. You can assign class-specific object
dependencies or link class-specific documents to a characteristic.

Figure 40: Class Hierarchy: Two Ways to Set Up a Class Hierarchy
Animation: Class Hierarchy: Two Ways to Set Up a Class Hierarchy

For more information on Class Hierarchy: Two Ways to Set Up a Class Hierarchy,
please view the animation in the lesson Class Maintenance in your online course.
The classification system lets you set up a hierarchy of classes made up of several superior
and subordinate classes.
Using the Objects to Class allocation function, you can allocate one or more subordinate
classes to a superior class.
Using the Class to Classes assignment function, you can assign one class to one or more
superior classes.
Class hierarchies can also be processed using the Graphical Hierarchy Maintenance master
data function and the Hierarchy Class List evaluation function.
Document Links

Figure 42: Document Links
You can link a document from the Document Management system to a class, characteristic,
or characteristic value.
Procedure to link a document to a class:
● On the initial screen for class maintenance, choose Document or Goto → Document.
● Enter the key of the document you want to link to the class. You can use this document to
store information on the class and the objects assigned to it. By linking a drawing or
graphic to the document, you can make this information available to the class.
Only LO-VC, not AVC: In the configuration, the document can be used as a start logo for the
class (see the configuration profile settings).
Only LO-VC, not AVC: You can access documentation about characteristics and values by
choosing the F4 help on the value assignment screen.


Unit 2
Exercise 3
Manage Classes
Simulation: Manage Classes

For more information on Manage Classes, please view the simulation in the
lesson Class Maintenance in your online course.
Business Example
Your modeling tasks now requires you to maintain the relevant variant classes and class
nodes.
Task 1: Create a Variant Class
1. Create variant class T_FCL## . Use the app Manage Classes.

Class T_FCL##
Class type 300 (= Variants)
Description: Class for forklift T-FCL##
Status: Released
Group: T-##
Valid from / to: Accept the default
Assign the 3 characteristics you created in a previous exercise to your new class
T_FCLX##, T_FCLG## and T_FCLH##.
Task 2: Check Existing Classes

For a subsequent exercise, you will need a class node to add color components and engine
components.
Check the existing class nodes T_FC_COLOR and T_FC_ENGINE. Both were defined with class
type 200.
Hint:
Note that these class nodes are used by all course participants.
Do not make any changes to these class nodes!
1. Display class node T_FC_COLOR with class type 200 for color components.
Display the view Addnl Data.

Can this class be used in BOMs?

What is the unit of measure for the resulting components?
Which item category is used for the resulting component in the bill of material?
2. Check the tab page for the characteristics.

Which characteristics are assigned to the class node?
Which values can these characteristics have?
Close your classes screen.
3. Search all materials that are connected to this class node. Use the app Find Objects in
Classes.
Display all materials that are assigned to class with the right values.
Are values assigned to all characteristics of the class node for all materials?
Are there assigned materials for all value combinations?
4. Display class (200)T_FC_ENGINE. This class is relevant for the components of the forklift
engine.

6. Search all materials that are connected to this class node.

Close the app.

Unit 2
Solution 3
Manage Classes
Simulation: Manage Classes

For more information on Manage Classes, please view the simulation in the
lesson Class Maintenance in your online course.
Business Example
Your modeling tasks now requires you to maintain the relevant variant classes and class
nodes.
Task 1: Create a Variant Class
1. Create variant class T_FCL## . Use the app Manage Classes.

Class T_FCL##
Class type 300 (= Variants)
Description: Class for forklift T-FCL##
Status: Released
Group: T-##
Valid from / to: Accept the default
Assign the 3 characteristics you created in a previous exercise to your new class
T_FCLX##, T_FCLG## and T_FCLH##.
a) Create a class. Use the following menu paths:
SAP Fiori Launchpad → Group Classification → Tile/ App Manage Classes.
Or inside the SAP GUI, start transaction code CL02.
SAP- Easy Access Menu → Cross Application Components → Classification
System → Master Data → Classes.
Class: T_FCL##
Class Type: 300
Choose the Create button.

Enter the description Class for forklift T-FCL##.

Set the status to Released.

Define the group T-##. The validity is automatically set.
b) Add the characteristics: T_FCLX##, T_FCLG## and T_FCLH##.
c) Save your class.
d) Open the Home screen.
Task 2: Check Existing Classes

For a subsequent exercise, you will need a class node to add color components and engine
components.
Check the existing class nodes T_FC_COLOR and T_FC_ENGINE. Both were defined with class
type 200.
Hint:
Note that these class nodes are used by all course participants.
Do not make any changes to these class nodes!
1. Display class node T_FC_COLOR with class type 200 for color components.
a) Display the class node.
SAP Fiori Launchpad → Group Classification → Tile/App Manage Classes
Or inside the SAP GUI, start transaction code CL02.
Class: T_FC_COLOR
Class Type 200
Display the class (Button). Display the view Addnl Data.
b) Can this class be used in BOMs?

Yes
c) What is the unit of measure for the resulting components?

L (Liter)
d) Which item category is used for the resulting component in the bill of material?
L (stock item)



a) Display the tab page for the characteristics.
T_FC021
Choose the Display values button.
(0=without, R=-red, B=blue, G=green, Y=yellow, W=white, S=black)
b) Close your classes screen.
3. Search all materials that are connected to this class node. Use the app Find Objects in
Classes.
a) Find Object in classes.
Use the following menu paths:
SAP Fiori Launchpad → Group Classification → Tile Find Objects in classes.
Or, in the SAP GUI, start transaction Code: CL30N .
Class: T_FC_COLOR
Class Type: 200
→ Continue
b) Display all materials that are assigned to class with the right values.
Choose the button: → Find in initial class
==>All materials are displayed inclusive assigned values.
c) Are values assigned to all characteristics of the class node for all materials?
Yes
d) Are there assigned materials for all value combinations?

Yes( Except “without color”)
4. Display class (200)T_FC_ENGINE. This class is relevant for the components of the forklift
engine.
a) Display the class node:
SAP Fiori Launchpad → Group Classification → Tile/App Manage Classes
Or inside SAP GUI, start transaction code CL02.


Class: T_FC_Engine
Class Type 200
Display this class (button). Display the view Addnl. Data.
b) Can this class be used in BOMs?

Yes
c) What is the unit of measure for the resulting components?

PC Piece
d) Which item category is used for the resulting component in the bill of material?
L (stock item)

a) Display the tab page for the characteristics.
Which characteristics are assigned to the class node??
T_FC000 and T_FC001
Choose the button Display values.
(D=Diesel, G=Gas, E=Electric), (18, 25, 30, 45, 55 kW)
b) Close your classes screen.
6. Search all materials that are connected to this class node.

Close the app.
a) Find Object in classes.
Use the following menu paths:
SAP Fiori Launchpad → Group Classification → Tile Find Objects in classes.
Or in the SAP GUI, start transaction code: CL30N .
Class: T_FC_Engine
Class Type: 200
→ Continue.

Choose the button: → Find in initial class
==>All materials are displayed inclusive assigned values.
Yes
No: only 3 performance values for every engine type.
b) Close the app.

LESSON SUMMARY

Unit 2
Learning Assessment
1. What do you have to consider with regards to the data type of the characteristic if you
want to use the characteristic in variant configuration?
X A You can only use characteristics with data type CHAR.
X B You can only use characteristics with data type NUM.
X C You can only use characteristics with data type NUM and CHAR.
X D You can use characteristics of all 5 data types. For DATE, TIME, and CURR, there
are restrictions regarding the use in object dependencies.
2. You can work with reference characteristics in variant configuration. Which database
tables can be used here?
X A Only database tables of the material master (MARA, MARC, ...).
X B Only database tables of the sales order (VBAK, VBAP, ... ).
X C A large number of database tables exist that you can use. However, these database
tables must be marked accordingly in the header.
X D A large number of database tables exist that you can use. These database tables
are not marked as such. You must know or know where they are, which database
tables they are.
3. Which apps or transactions can you use to assign the material master to the variant class,
that is, to create the link material master - variant class?
X A Material master or product master maintenance (MM01, ...)
X B Classification (CL24N, CL20N)
X C Class maintenance (CL02, ...)
X D Modeling Environment for Variant Configuration (PMEVC)
X E Maintenance of the configuration profile (CU41, ...)


UNIT 3 Materials, BOMs and Task Lists
Lesson 1
Material 60
Exercise 4: Manage Materials 65
Lesson 2
Material BOM 79
Exercise 5: BOM Maintenance (Without Dependencies) 83
Lesson 3
Task List 90
Exercise 6: Routing Maintenance (Without Dependencies) 93
UNIT OBJECTIVES
● Work with Materials and perform the necessary settings for VC

● Work with Bill of Materials and perform the necessary settings for VC
● Do the necessary settings for VC
● Maintain a Task List and perform the necessary settings for VC

Unit 3
Lesson 1
Material
LESSON OVERVIEW
Business Scenario
Since your company uses variant configuration, you have to create a material master record,
a BOM, and a routing. This allows you to represent all variants of the product.
LESSON OBJECTIVES
Material Master
Figure 44: Variant Configuration Knowledge Base for Materials (1)
Animation: Variant Configuration Knowledge Base for Materials (1)

For more information on Variant Configuration Knowledge Base for Materials (1),
please view the animation in the lesson Material in your online course.
The material master record, the (super) BOM, and the (super) task list are three central
objects in the variant configuration model.

Lesson: Material
The material master record collects information and control quantities for the configurable
product.
The bill of material and routing (task list) carry the object dependencies.
Figure 46: Variant Configuration Knowledge Base for Materials (2)
Configurable Material
Figure 47: Configurable Material
The configurable material is the material number under which all variants of a product are
stored in SAP ERP.
The material master record is the reference point for further objects that are relevant to the
variant product. Bills of material, routings, and so on are all created for this material.
The material master record contains important control parameters, which especially affect
material requirements planning (MRP) and sales.

Unit 3: Materials, BOMs and Task Lists
Animation: Configurable Material

For more information on Configurable Material, please view the animation in the
lesson Material in your online course.
Views for Material Master Maintenance
Figure 49: Views for Material Master Maintenance
Material master records are also referred to as materials and product masters.
Each department has its own view on a material master record. For BOM maintenance, it does
not matter which views exist, provided that at least one view exists at the plant level.
In Customizing for bills of material, you can define which material types can be used to create
BOMs and which material types are not allowed in BOMs.
The material status must allow BOM maintenance.
The user-specific material master allows you to tailor the data displayed to meet your specific
requirements.
You can define default settings for the views, the industry sector, and the organizational
levels.
The views selected have particular relevance to how the material is processed. For example,
Basic Data defines if the material is configurable; MRP sets planning parameters; Sales
identifies the item category group and general item category group; Work Scheduling sets the
order change profile; and Classification can be used for class and characteristic value
assignments.
Settings for Configurable Materials

Lesson: Material
Figure 50: Settings for Configurable Materials
Configurable Material: Detailed Information

In the standard system, material type KMAT is defined for configurable materials.
You can define a material as configurable even if the material has a non-configurable material
type, by setting the indicator on the basic data screen of the material master.
You must define the following configuration-specific settings in the material master of a
configurable material:
● In the sales data, you enter the item category group. The item category group controls the
assignment of item categories in sales orders. The item category of an item influences the
transfer of requirements and pricing for the item.
● In the MRP data, you enter an MRP group or a strategy group. The strategy group
determines the planning strategy for the configurable material (for example, make-to-
order production). The MRP type determines whether and how the material is planned (for
example, using planned orders). The lot size determines the lot-size procedure that the
system uses to calculate the quantity of the material to be produced. A configurable
material needs exact lot sizes.
● The Individual/Collective indicator controls whether separate segments for requirements
for the configurable material are created in the MRP requirements explosion.
● To enable availability checks for the material and its components, enter a checking rule.
The default checking rule for a configurable material is 02.
● To enable order change management (OCM), define the profile in the work scheduling
view.

Phantom Assemblies
Figure 51: Phantom Assemblies
Animation: Phantom Assemblies

For more information on Phantom Assemblies, please view the animation in the
Phantom Assembly
A phantom assembly is a logical grouping of materials. Normally, a phantom assembly is
created in the design to simply describe and manage a number of components as a whole.
The components of a phantom assembly are immediately inserted in the higher-level
assembly. In contrast, components in a "real" assembly are first assembled to form the
header material. Then the header material is inserted into the superordinate assembly.
Example: The phantom assembly "Extras" contains the components "Road set", "Camera"
and "Mirror”. "Road set", "Camera" and "Mirror” are immediately inserted into the fork lift.
The "drivers seat" assembly includes materials as components. First, these components are
assembled into a “drivers seat” and then added to the fork lift.

Unit 3
Exercise 4
Manage Materials
Simulation: Manage Materials

For more information on Manage Materials, please view the simulation in the
Business Scenario
In this stage of configuration model, you must create the material master records for the
configurable items. Along with the forklift, the header material of each assembly where you
want to use object dependencies must be configurable. You will need to create two master
records: one for the forklift and one for the extras.
Create 2 Material Master Records

Create the following material master records for your configurable forklift and the extras:
Forklift T-FCL## Material Type: Finished Product
Extras T-FCX## Material Type: Semi Finished Product
1. Create T-FCL## with the app Create Materials.

Use the following data on the initial screen:
Material: T-FCL##
Industry Sector: M (Mechanical Engineering)
Material Type: Finished Product
Copy from Material: T-FCL00
Hint:
Use material T-FCL00 as a template.
Select the following views:
Basic Data 1+ 2
Classification
Sales: Sales Org. Data 1 + 2
Sales: General / Plant Data

MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+2
Costing 1+ 2
Note:
Set the checkbox Create views selected.
Save your settings with the box Default setting.

Open Organizational levels.
Note:
Also enter the values for Copy from.
Copy from
Plant 1010 1010
Sales Org 1010 1010
Distribution Channel 10 10

In Basic Data 1+2, change or enter the following data:
Description: Forklift T-FCL## configurable

Base unit of Measure: PC
Gross weight: 3.374 KG
Net weight: 3.100
Volume: 12 m3
Size / dimensions: 2x2x3M
Check Box Material is configurable (Basic Data 2)
In the Classification view, enter the following data:
Class Type: 300
Class: T_FCL##

Lesson: Material
Hint:
Delete the existing class.
Add your class. Do not do a value assignment.
Note:
If necessary:
You are able to change the class type allocation with Extras → Change Class
type .
To reach the next screen, choose the Next Screen (F8) button.
Note:
Check the following data. The field content was copied from the template
material.
Sales Org 1+2
Delivering Plant 1010
Tax Classification 1
Item category group 0002
Sales: General / Plant
Trans Grp. 0001
Loading Grp 0001
MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Lot Sizing Procedure EX
Procurement type X or E
SchedMargin key 001
DELETE Prod. stor. location: DELETE 101A

Otherwise, the system issues a warning mes-
sage.
In-house production 25
Strategy group 25

Availability check Y2
The following message may appear:: „The

production versions of the reference material
have not been adopted”
Work Scheduling
Prodn. Supervisor F##
Overall profile P00001
Accounting 1
Valuation Class 7920
Warning Message:
“Validity date in the past.”
Please confirm with Enter
Save your material.
2. Create T-FCX## with Industry Sector M (Mechanical Engineering), Material Type: Semi-
finished Product, and Plant 1010.
Hint:
Use material T-FCX00 as a template.
Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+2
Costing 1+ 2
Note:
Open Organizational levels:
Note:
Also enter values for Copy from.

Lesson: Material
Copy from
Plant 1010 1010
Change or enter inside Basic Data 1+2:
● Description: Accessories Forklift T-FCX## configurable
Save your Material.

Unit 3
Solution 4
Manage Materials
Simulation: Manage Materials

For more information on Manage Materials, please view the simulation in the
Business Scenario
In this stage of configuration model, you must create the material master records for the
configurable items. Along with the forklift, the header material of each assembly where you
want to use object dependencies must be configurable. You will need to create two master
records: one for the forklift and one for the extras.
Create 2 Material Master Records

Create the following material master records for your configurable forklift and the extras:
Forklift T-FCL## Material Type: Finished Product
Extras T-FCX## Material Type: Semi Finished Product
1. Create T-FCL## with the app Create Materials.

Use the following data on the initial screen:
Material: T-FCL##
Copy from Material: T-FCL00
Hint:
Use material T-FCL00 as a template.
Basic Data 1+ 2
Classification
Sales: Sales Org. Data 1 + 2

Lesson: Material
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+2
Costing 1+ 2
Note:

Note:
Copy from
Plant 1010 1010
Sales Org 1010 1010

In Basic Data 1+2, change or enter the following data:
Description: Forklift T-FCL## configurable

Base unit of Measure: PC
Net weight: 3.100
Volume: 12 m3
Size / dimensions: 2x2x3M
Check Box Material is configurable (Basic Data 2)
In the Classification view, enter the following data:
Class Type: 300
Class: T_FCL##

Hint:
Delete the existing class.
Add your class. Do not do a value assignment.
Note:
If necessary:
You are able to change the class type allocation with Extras → Change Class
type .
Note:
Check the following data. The field content was copied from the template
material.
Sales Org 1+2
Trans Grp. 0001
Loading Grp 0001
MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Lot Sizing Procedure EX
SchedMargin key 001
DELETE Prod. stor. location: DELETE 101A

Otherwise, the system issues a warning mes-
sage.
Strategy group 25

Lesson: Material
The following message may appear:: „The

production versions of the reference material
have not been adopted”
Work Scheduling
Accounting 1
Warning Message:
Save your material.

a) Create a material with a template.
SAP Fiori Launchpad → Group Product Master → App Create Material.
Alternatively, use MM01.
Or SAP GUI → SAP-Menu → Logistics → Production → Master Data → Material
Master → Material → Create (General) → Create.
Material: T-FCL##
Industry Sector: Mechanical Engineering
Template Material: T-FCL00
Enter your data:

Basic Data 1+ 2
Classification
Sales: Sales Org Data 1 + 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+2

Costing 1+ 2
Note:
Save your settings

Note:
Copy from
Plant 1010 1010
Sales Org 1010 1010
Save your settings

Enter
Enter the values for each view.

● Description Forklift T-FCL## configurable
● Base unit of Measure: PC (piece)
● Gross weight: 3.374 KG
● Net weight: 3.100
● Check Box : Material is configurable
Enter inside the view Classification:
Class Type: 300
Class: T_FCL##

Lesson: Material
Hint:
Assign the material to this particular class. Do not do a value assignment.
You are able to change the class type allocation with Extras → Change
Class type .
Sales Org 1+2
Trans Grp. 0001
Loading Grp 0001
MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Lot size EX
DELETE Prod. stor. location: 101A

SchedMargin key 001
Strategy group 25
„The production versions of the reference

material have not been adopted”
Work Scheduling
Accounting 1

Warning Message:
Save your Material.
2. Create T-FCX## with Industry Sector M (Mechanical Engineering), Material Type: Semi-
finished Product, and Plant 1010.
Hint:
Use material T-FCX00 as a template.
Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+2
Costing 1+ 2
Note:
Note:
Copy from
Plant 1010 1010
Save your Material.

SAP Fiori Launchpad → group Product Master → Tile Create Material.
Alternatively, use MM01.

Lesson: Material
Or SAP GUI → SAP-Menu → Logistics → Production → Master Data → Material

Material: T-FCX##
Material Type: Semifinished Product
Template Material: T-FCX00
Enter your data.

Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+ 2
Costing 1+ 2
Note:
Set the checkbox: Create views selected.
Note:
Copy from
Plant 1010 1010
Save your Material.

LESSON SUMMARY

Unit 3
Lesson 2
Material BOM
LESSON OVERVIEW
Business Scenario
You have to create material BOMs for your Variant Configuration scenarios.
LESSON OBJECTIVES
Bill of Material
Figure 54: Super BOM
Definition: Bill of Material

A bill of material is a formally structured list for an object, and contains all related objects,
their description, their quantity, and their unit.
The BOM of a configurable material contains all the parts that are required for all possible
variants of the material. Object dependencies are used to configure the BOM: only the parts
that are required for a specific variant are selected. The BOM is exploded according to the
characteristic values assigned.

Animation: Super BOM

For more information on Super BOM, please view the animation in the lesson
Material BOM in your online course.
You can also make manual changes to the BOM for a sales order, provided that the settings in
the configuration profile allow this. You can, for example, delete or insert components. The
BOM is then saved as an order BOM for the sales order.
You can change the BOM in the production order (as in production without variants).
Special Item Types in a Configurable BOM
Figure 56: Class Item: Item Category K
Animation: Class Item: Item Category K

For more information on Class Item: Item Category K, please view the animation
in the lesson Material BOM in your online course.
You can enter a class in which materials or documents are classified as an item in a BOM. The
class must have a class type that allows it to be used as a BOM item.
In the standard system, you can use classes of class type 200, for materials, and class type
201, for documents, as class items.
Only these two object types can be selected via a class item.
When you assign characteristic values in configuration functions, the class is replaced by a
material or a document.

Lesson: Material BOM
Figure 58: Non-Stock Item / Item Category N
You can create non-stock items both with and without a material master record. If you enter a
non-stock item without entering a material number, you must enter a descriptive text and
procurement data.
You enter purchasing data for non-stock items with or without a material number (except
materials with material type KMAT). The system uses the pricing data to determine the
release strategy. The material group is required for generating a purchase requisition. The
component is procured directly for the production order. Purchase requisitions are created
automatically.
A non-stock item can also be a configurable material. In this example, EXTRAS is a place
holder that contains the three components as pictured. The selection of the desired EXTRAS
is chosen when the sales order is configured and must contain the appropriate object
dependencies. Direct procurement logic is not used for non-stock items with material type
KMAT.

Figure 59: Variable-Size Item: Item Category R
If you want to use one material number to represent different-sized pieces of a material, you
assign item category R.
On the Variable-Size Item Data detail screen, the system uses the sizes and formula you enter
(if any) to immediately calculate the variable-size item quantity required.
Material requirements can be determined directly from the BOM explosion, without having to
perform additional steps first.
You do not need to maintain a separate material master record for each different section of
the material that is cut to size.
Variable-size items are useful in variant configuration because you can use dependencies with
reference characteristics to maintain variable-size item data.

Unit 3
Exercise 5
BOM Maintenance (Without Dependencies)
Simulation: BOM Maintenance (Without Dependencies)

For more information on BOM Maintenance (Without Dependencies), please view
the simulation in the lesson Material BOM in your online course.
Business Scenario
To model your forklift and other configurable in-house materials, you must create a maximum
BOM. Since the BOM structure is multi-level, you must create several BOMs in the system. In
our exercise, you have to create a BOM for your forklift T-FCL## and your extras T-FCX##.
Task 1: Create First Material BOM
1. Create first material BOM.

For detailed information check the appendix of this handbook.
Start the app Create Material BOM.
On the initial screen, enter the following:
Material: T-FCL##
Plant: 1010
Usage: 1– Production
In Create material BOM: General Item Overview: enter the following components. For item
0080, replace it with your material.
Item: Item Cate- Component Quantity Unit

gory
0010 L T-FV3C00 1 KG
0020 K (200) 2 L
T_FC_COLOR.
0030 L T-FV5D01 1 PC
0030 L T-FV5D02 1 PC
0030 L T-FV5D03 1 PC
0030 L T-FV5D04 1 PC
0030 L T-FV5D05 1 PC

0030 L T-FV5D06 1 PC
0040 K (200) 1 PC
T_FC_Engine.
0050 L T-FC7XX 1 PC
0060 L T-FL200 1 PC
0070 L T-FL300 1 PC
0080 L T-FCX## 1 PC
Note:
Be careful with the item numbers. To add a class key, select the view Class.
Save your first material BOM.
Task 2: Create Second Material BOM
1. Create a second BOM.

For detailed information, check the appendix of this handbook.
Enter the following:
Material: T-FCX##
Plant: 1010
Enter the following components:

gory
0010 L T-FL8A00 1 PC
0020 L T-FL8B00 1 PC
0030 L T-FL8C00 1 PC
0040 L T-FV5C01 1 PC
0050 L T-FV5C02 1 PC
Save your second material BOM.

Unit 3
Solution 5
BOM Maintenance (Without Dependencies)
Simulation: BOM Maintenance (Without Dependencies)

For more information on BOM Maintenance (Without Dependencies), please view
the simulation in the lesson Material BOM in your online course.
Business Scenario
To model your forklift and other configurable in-house materials, you must create a maximum
BOM. Since the BOM structure is multi-level, you must create several BOMs in the system. In
our exercise, you have to create a BOM for your forklift T-FCL## and your extras T-FCX##.
Task 1: Create First Material BOM
1. Create first material BOM.

For detailed information check the appendix of this handbook.
Material: T-FCL##
Plant: 1010
In Create material BOM: General Item Overview: enter the following components. For item
0080, replace it with your material.

gory
0010 L T-FV3C00 1 KG
0020 K (200) 2 L
T_FC_COLOR.
0030 L T-FV5D01 1 PC
0030 L T-FV5D02 1 PC
0030 L T-FV5D03 1 PC
0030 L T-FV5D04 1 PC
0030 L T-FV5D05 1 PC

0030 L T-FV5D06 1 PC
0040 K (200) 1 PC
T_FC_Engine.
0050 L T-FC7XX 1 PC
0060 L T-FL200 1 PC
0070 L T-FL300 1 PC
0080 L T-FCX## 1 PC
Note:
Be careful with the item numbers. To add a class key, select the view Class.

a) Create a material BOM for T-FCL## in plant 1010 and usage 1.
SAP Fiori Launchpad → Group Product Engineering → Tile Create Material BOM.
Or, in the backend system: CS01
Or, choose the following path: SAP GUI → SAP-Menu → Logistics → Production →
Master Data → Bills of Material → Bill of Material → Material BOM → Create.
Material: T-FCL##
Plant: 1010
Usage: 1 = Production
If you want use 'Copy from' , than click on this button, insert the copy from material,
click 'enter', click 'select all', click 'copy'. For item 0080, replace it with your material.
And delete all object dependencies.
If you use "Copy From" you get a warning message about Storage Location. Delete the
storage location.
If you don't use 'Copy from' , than in Create material BOM: General Item Overview,
enter the following components.

gory
0010 L T-FV3C00 1 KG
0020 K (200) 2 L
T_FC_COLOR.
0030 L T-FV5D01 1 PC
0030 L T-FV5D02 1 PC

0030 L T-FV5D03 1 PC
0030 L T-FV5D04 1 PC
0030 L T-FV5D05 1 PC
0030 L T-FV5D06 1 PC
0040 K (200) 1 PC
T_FC_Engine.
0050 L T-FC7XX 1 PC
0060 L T-FL200 1 PC
0070 L T-FL300 1 PC
0080 L T-FCX## 1 PC
Task 2: Create Second Material BOM
1. Create a second BOM.

For detailed information, check the appendix of this handbook.
Material: T-FCX##
Plant: 1010
Enter the following components:

gory
0010 L T-FL8A00 1 PC
0020 L T-FL8B00 1 PC
0030 L T-FL8C00 1 PC
0040 L T-FV5C01 1 PC
0050 L T-FV5C02 1 PC

a) Create a material BOM for T-FCX## in plant 1010 and usage 1.
SAP Fiori Launchpad → Group Product Engineering → Tile Create Material BOM

Or, in the backend system: CS01

Or, choose the following path: SAP GUI → SAP-Menu → Logistics → Production →
Master Data → Bills of Material → Bill of Material → Material BOM → Create.
Material: T-FCX##
Plant: 1010
Usage: 1 = Production
If you want use 'Copy from' , than click on this button, insert the copy from material,
click 'enter', click 'select all', click 'copy'. And delete all object dependencies.
If you don't use 'Copy from' , than in Create material BOM: General Item Overview,
enter the following components.

gory
0010 L T-FL8A00 1 PC
0020 L T-FL8B00 1 PC
0030 L T-FL8C00 1 PC
0040 L T-FV5C01 1 PC
0050 L T-FV5C02 1 PC

LESSON SUMMARY

Unit 3
Lesson 3
Task List
LESSON OVERVIEW
Business Scenario
Since your company uses variant configuration, you have to create a routing.
LESSON OBJECTIVES
Task List
Figure 61: Super Task List
A task list is a list that describes the process for producing a material or for performing a
service. The task list contains all the operations, suboperations, and production resources/
tools (PRTs) that are required to produce the material.
The task list (routing) for a configurable material contains all the sequences, operations,
suboperations, and PRT assignments that are required to produce all possible variants of the
material. You then assign dependencies to the operations, sequences, and PRTs in routings
for configurable materials.
Animation: Super Task List

For more information on Super Task List, please view the animation in the lesson
Task List in your online course.

Lesson: Task List
The operations for a specific variant are selected by object dependencies.

The routing is exploded according to the characteristic values you assign.
You can create a routing by copying the configuration simulation. You can do this for a
specific sales order.
Figure 63: Task List
Task List: Sequence

An alternative sequence allows you to select alternative operations for a sequence of
operations. This can be useful to deal with either different production processes for different
lot sizes, or capacity problems.
A parallel sequence allows you to process operations simultaneously with operations in the
standard sequence of the routing.
Suboperations are a more detailed definition of the operational activity. The suboperations
comprise a hierarchy below the main operation for which they define additional details in
costing and capacity planning.
The control key setting also plays an important role here.
Scheduling is always done at operation level.
The standard values for suboperations can be summarized per operation, with the same
dimension and unit.
You can assign PRTs to any operation. The PRT must have a master record.


Unit 3
Exercise 6
Routing Maintenance (Without Dependencies)
Simulation: Routing Maintenance (Without Dependencies)

For more information on Routing Maintenance (Without Dependencies), please
view the simulation in the lesson Task List in your online course.
Business Scenario
In the modeling of the forklift configuration task, you must create the routing for your forklift
truck in this step. We will only create a routing for the forklift here. The accessory assembly
has been defined as a dummy assembly so that its components are provided directly to the
production order of the forklift.
Task 1: Create a Routing
1. Create a new routing based on an existing one.

Select the app Create Routing. It can be found inside group Production Engineering.
Field Value
Material: T-FCL##
Plant: 1010
Choose Continue.
In Create Routing: Header Data Check, add the following information:
Field Value
Description: Forklift T-FCL##

Overall Status: 4 – released
Open the view Operation.
2. Add the following operations:
Note:
Duration is in minutes.

Operation: Work Center Description Setup time Machine Labor Time

Time
0100 T-E00 Allocation 00 00 40
Components
0200 T-F00 Assy Drive 20 60 30
Chassis
0300 T-G00 Under Car- 30 60 90
riage
0400 T-H00 Driver’s Carb 40 60 20
assy
0500 T-K00 Hydraulics 10 25 40
with Lift
0600 T-M00 Lift with 10 30 10
Chassis assy
0700 T-L00 Varnishing 35 60 30
0800 T-P00 Road Eqipm. 00 00 20
assy
0810 T-P00 Rear view 00 00 20
camera assy
0820 T-P00 Add. Light 00 00 20
assy
0900 T-Z00 Final Inspec- 00 00 80
tion
Note:
You need to press Enter after inputting the operation values so that the column
names (Setup, Machine and Labor) will appear.
Save your routing.
Task 2: Add Production Resource Tools
1. Add the following PRTs to operation 0600. Highlight the row and select the box PRT,
which can be found in the header area.
A new screen opens. Select the box Other. Add the following:
T_FV_002
Choose Back.
The PRT overview screen opens again. Choose Other again, and add the following:
T_FV_004
Choose Back.
T_FV_008

Lesson: Task List
The PRT overview screen opens again. Click back to open the Operation Overview screen.
Add a Document as a PRT to operation 900. Use the known path. Add the following:
Document: T-D03
Document Type: DRW
Document part: 000
Document version: 00
Quantity: 1
unit: PC
Now save your Routing.
Task 3: Create Product Versions
1. Change your material T-FCL## and add a product version.

Use the app Change Material in the SAP Fiori launchpad.
On the initial screen enter: Material T-FCL##
Select the view Work Scheduling with plant 1010.
Choose the button → ProdVersions
In the Production Version Overview, enter the following:
Version: 1
Production Version Text: Version 1
Valid from: Today’s date
Valid to: 31.12.9999
Select the Details box. Enter the following data:

→ Details
Detailed planning Tasklist Type: Routing

Group and group counter –> select F4– Help “Search using ma-
terial”
Bill of Material Alternative 1

Usage 1
Choose Check.
Choose Cancel.
Choose Continue.
Choose Continue.
Save your material changes.
2. Now change your material T-FCX## and add a product version.


On the initial screen enter: Material T-FCX##
Version: 1
Valid to: 31.12.9999

→ Details

Usage 1
Choose Check.
Choose Back.
Choose Continue.
Choose Continue.

Unit 3
Solution 6
Routing Maintenance (Without Dependencies)
Simulation: Routing Maintenance (Without Dependencies)

For more information on Routing Maintenance (Without Dependencies), please
view the simulation in the lesson Task List in your online course.
Business Scenario
In the modeling of the forklift configuration task, you must create the routing for your forklift
truck in this step. We will only create a routing for the forklift here. The accessory assembly
has been defined as a dummy assembly so that its components are provided directly to the
production order of the forklift.
Task 1: Create a Routing
1. Create a new routing based on an existing one.

Select the app Create Routing. It can be found inside group Production Engineering.
Field Value
Material: T-FCL##
Plant: 1010
Choose Continue.
In Create Routing: Header Data Check, add the following information:
Field Value

Open the view Operation.

a) Select the Create Routing tile.
Field Value
Material: T-FCL##

Field Value
Plant: 1010
b) Define the following:

Field Value

c) Choose the Operation button.
2. Add the following operations:
Note:
Duration is in minutes.
Operation: Work Center Description Setup time Machine Labor Time

Time
0100 T-E00 Allocation 00 00 40
Components
0200 T-F00 Assy Drive 20 60 30
Chassis
0300 T-G00 Under Car- 30 60 90
riage
0400 T-H00 Driver’s Carb 40 60 20
assy
0500 T-K00 Hydraulics 10 25 40
with Lift
0600 T-M00 Lift with 10 30 10
Chassis assy
0700 T-L00 Varnishing 35 60 30
0800 T-P00 Road Eqipm. 00 00 20
assy
0810 T-P00 Rear view 00 00 20
camera assy
0820 T-P00 Add. Light 00 00 20
assy
0900 T-Z00 Final Inspec- 00 00 80
tion

Lesson: Task List
Note:
You need to press Enter after inputting the operation values so that the column
names (Setup, Machine and Labor) will appear.
Save your routing.

a) Enter the values of your exercise.
b) Save your routing.
Task 2: Add Production Resource Tools
1. Add the following PRTs to operation 0600. Highlight the row and select the box PRT,
which can be found in the header area.
A new screen opens. Select the box Other. Add the following:
T_FV_002
Choose Back.
T_FV_004
Choose Back.
T_FV_008
The PRT overview screen opens again. Click back to open the Operation Overview screen.
Add a Document as a PRT to operation 900. Use the known path. Add the following:
Document: T-D03
Document Type: DRW
Document part: 000
Quantity: 1
unit: PC
Now save your Routing.

a) Highlight the row and select the box PRT, which can be found in the header area.
b) Select the box Other. Add the following:

T_FV_002
Choose Back.
c) Select the box Other. Add the following:

T_FV_004
Choose Back.

d) Select the box Other. Add the following:

T_FV_008
Choose Back.
The PRT overview screen opens again. Click Back. The Operation Overview screen
opens.
e) Add a document as a PRT to operation 900. Use the known path. Add the following:
Document: T-D03
Document Type: DRW
Document part: 000
Quantity: 1
unit: PC
f) Now save your Routing.
Task 3: Create Product Versions
1. Change your material T-FCL## and add a product version.

On the initial screen enter: Material T-FCL##
Version: 1
Valid to: 31.12.9999

→ Details

Group and group counter –> select F4– Help “Search using ma-
terial”

Usage 1
Choose Check.

Lesson: Task List
Choose Cancel.
Choose Continue.
Choose Continue.
a) Change your material.
Use the app Change material in the SAP Fiori launchpad, or the transaction MM02.
On the initial screen enter the following:
Material: T-FCL##
b) Select the view Work Scheduling with plant 1010.
c) Choose the button → ProdVersions.
d) In the Production Version Overview, enter the following:

Version: 1
Valid to: 31.12.9999
e) Select the Details box.

→ Details

Group and group counter –> select F4– Help Search using
material”

Usage 1
Choose Check.
Choose Cancel .
Choose Continue .
Choose Continue .
f) Save your material changes.
2. Now change your material T-FCX## and add a product version.

On the initial screen enter: Material T-FCX##

Version: 1
Valid to: 31.12.9999

→ Details

Usage 1
Choose Check.
Choose Back.
Choose Continue.
Choose Continue.
a) Change your material.
Use the app Change material in the SAP Fiori launchpad, or the transaction MM02.
Material: T-FCX##
b) Select the view Work Scheduling with plant 1010.
c) Choose the button → ProdVersions.
d) In the Production Version Overview, enter the following:

Version: 1
Valid to: 31.12.9999
e) Select the Details box.

→ Details

Usage 1

Lesson: Task List
Choose Check.
Choose Back.
Choose Continue.
Choose Continue.
f) Save your material changes.

LESSON SUMMARY

Unit 3
Learning Assessment
1. You want to set up a multi-level BOM structure for your configurable product. Which
material masters must be configurable?
X A It is sufficient for the header material to be configurable.
X B It is sufficient if the header material and all assemblies to which you want to assign
with a configuration profile are configurable.
X C The header material and all assemblies in whose BOMs object dependencies are to
be used must be configurable. And all materials between the header material and
these assemblies.
X D All materials in a multi-level configurable BOM structure must be configurable.
2. How does a BOM become a configurable BOM? In other words, what do you have to do to
assign object dependencies to a BOM?
X A The BOM header material must be configurable.
X B The header material of the BOM must be configurable and at least one variant
class and configuration profile must have been assigned to the header material.
X C The header material of the BOM must be configurable and you must use special
transactions to maintain the BOM.
X D It is sufficient to use special transactions to maintain the BOM.

3. How does a routing become a configurable routing? In other words, what do you have to
do to assign object dependencies to a routing?
X A Each routing is configurable. However, dependencies are only evaluated in

conjunction with a configurable material master as the header material.
X B The header material of the routing must be configurable.
X C The header material of the routing must be configurable and at least one variant
class and configuration profile must have been assigned to the header material.
X D The header material of the routing must be configurable and you must use special
transactions for maintaining the routing.
X E It is sufficient to use special transactions to maintain the routing.

UNIT 4 Configuration Profile
Lesson 1
Classic and Advanced Variant Configuration 109
Lesson 2
Configuration Profile 114
Exercise 7: Create And Test A Configuration Profile 125
UNIT OBJECTIVES
● Explain the differences and similarities between classic and advanced variant
configuration
● Define a configuration profile and use different configuration scenarios

Unit 4: Configuration Profile

Unit 4
Lesson 1
Classic and Advanced Variant Configuration
LESSON OBJECTIVES
configuration
Classic and Advanced Variant Configuration

Business Scenario
The advanced variant configuration improves your company's sales, product management,
and product engineering performance with SAP S/4HANA for advanced variant configuration.
Advanced Variant Configuration: First Settings

Value Proposition
Streamline your product modeling with advanced configuration simulation capabilities in a
comprehensive simulation environment for variant configuration models
● Make faster and more informed decisions about your product portfolio by leveraging real-
time analytics for configuration and classification in all related business objects (for
example, sales order, batch, product master).
● Improve your configuration efficiency through a state-of-the-art SAP Fiori user experience
and a high-performing configurator based on SAP HANA capabilities.
● Streamline your product modeling with advanced configuration simulation capabilities in a
comprehensive simulation environment for variant configuration models.
Capabilities
● New integrated advanced variant configurator supporting single-level variant configuration
models.
● Support for make-to-stock scenarios using material variants and make-to-order scenarios
using configurable materials.
● Reusable SAP Fiori configuration user experience (UX) integrated into sales order and
material master providing improved user guidance through more precise value
restrictions, filtering, and undo and redo functionality.
● State-of-the-art configuration engine leveraging SAP HANA capabilities.
● New simulation environment for bills of materials (BOMs) using SAP Fiori UX.
● Syntax enhancement: negative variant tables.

● Flexible report that allows users to generate core data services (CDS) views based on
user-selected variant configurator characteristics.
Figure 65: Advanced Variant Configuration
Animation: Advanced Variant Configuration

For more information on Advanced Variant Configuration, please view the
animation in the lesson Classic and Advanced Variant Configuration in your
online course.
The classical variant configuration and the advanced variant configuration can both be used in
SAP S/4HANA, on-premise.
The classical variant configuration in SAP S/4HANA, on-premise works as before (with some
minor changes).
The advanced variant configuration uses the same database tables for configuration data and
master data as the classical variant configuration.
Group “Variant Configuration Modeling” inside SAP Fiori Launchpad
Figure 67: Group “Variant Configuration Modeling” inside SAP Fiori Launchpad

Lesson: Classic and Advanced Variant Configuration
For low-level dependencies, the processing mode is supposed to be “classic”. As the bill of
materials (BOM) explosion only considers “classic” dependency knowledge and ignores
“advanced” dependency knowledge, incorrect data here does not cause problems.
The Consistency check in the Variant Configuration Modeling Environment (PMEVC) shows
whether there are such ‘mixed’ Processing Mode situations in the model.
Simulation of “Advanced” configuration models can be done directly from the PMEVC. The
user can use the Simulate Configuration Models app also.
Variant Configuration: Modeling Environment
Figure 68: Variant Configuration: Modeling Environment
Animation: Variant Configuration: Modeling Environment

For more information on Variant Configuration: Modeling Environment, please
view the animation in the lesson Classic and Advanced Variant Configuration in
your online course.
By default, all the existing variant configuration models in the system are Classic.
With the app VC- Modeling Environment, you work, initially, with this classic scenario.
Advanced Variant Configuration in Configuration Profile

Figure 70: Advanced Variant Configuration in Configuration Profile
Animation: Advanced Variant Configuration in Configuration Profile

For more information on Advanced Variant Configuration in Configuration
Profile, please view the animation in the lesson Classic and Advanced Variant
Configuration in your online course.
To be able to use the new SAP Fiori based Advanced Variant Configuration, you have to set up
this for the model. This can be done in the Configuration Profile, where you find the
processing mode.
Note that this is possible for all the dependency objects (Dependency Net, Constraint,
Precondition, Selection Condition, Procedure).
Simulation Environment
Figure 72: Simulation Environment

Lesson: Classic and Advanced Variant Configuration
Animation: Simulation Environment

For more information on Simulation Environment, please view the animation in
the lesson Classic and Advanced Variant Configuration in your online course.
With the new advanced variant configuration, two scenarios are available. You can easily use
the existing scenarios, which you know, or work with the advanced scenario.
If you select the advanced scenario, you can work with a different simulation environment.
LESSON SUMMARY
configuration

Unit 4
Lesson 2
Configuration Profile
LESSON OVERVIEW
Business Scenario
For variant configuration you have to use the configuration profile. Therefore, you would like
to get a deeper insight into your configuration profile.
Additionally you work with the scenarios “Planned and Production Order”, “Order BOM” and
“Sales Order”.
LESSON OBJECTIVES
Figure 74: Configuration Profile for Material
You define essential settings for materials in the configuration profile. These options are
restricted for other configurable object types.
You select a class type.
You set the processing mode:

Lesson: Configuration Profile
● Classic (LO-VC)
● Advanced Variant Configuration (AVC)
You can define settings that affect configuration. You define these settings for each object,
and they apply to the object wherever it is used. However, you can overwrite these settings
with your own settings in the configuration editor (Classic = LO-VC).
You can specify an interface design (Classic = LO-VC) or grouping characteristics (Advanced
Variant Configuration = AVC) together on the value assignment screen.
You can use the configuration profile to assign dependencies to a configurable object.
Dependency nets can only be assigned to a configuration profile. If you assign actions and
procedures to the configuration profile, you can manage them more easily because they are
all in one place.
For materials, you must also maintain configuration parameters for BOM explosion.
Depending on the configuration parameters you set, other fields in the configuration profile
are hidden or shown.
The configurable material must be assigned to at least one variant class. This link is usually a
material-to-class allocation only, without assigning values. Assigning values would restrict the
allowed values.
You can assign a material to a class in the following ways:
● In the material master record (classification data)
● In the classification menu (maintain assignment)
● In the configuration profile (class assignment)
Configuration Profile: Scenario: Planned- / Production Order without BOM

Explosion
Figure 75: Scenario: Planned- / Production Order Without BOM Explosion

Animation: Scenario: Planned- / Production Order Without BOM Explosion

For more information on Scenario: Planned- / Production Order Without BOM
Explosion, please view the animation in the lesson Configuration Profile in your
online course.
Only the header material is configured interactively in the sales order.

The result is one order item in the sales order.
The BOM is only simulated in the configuration simulation - it is not exploded in the sales
order.
All components (variable and non-variable parts) are determined automatically during the
MRP run process.
Flow
● Create a sales order and enter the configurable material as an order item.
● You see the configuration editor, where you assign values to the characteristics of the
material. As you enter characteristic values, dependencies for the characteristics and
values are processed.
● You cannot go to other overviews in the configuration editor if you select None under BOM
explosion.
● In MRP, requirements are determined for the item in the sales order. In the planned order
or production order, the components of the BOM and the operations of the routing are
determined according to the characteristic assigned in the sales order. Low-level
configuration applies.

Configuration Profile: Scenario: Order BOM
Figure 77: Order BOM: Overview
Purpose
You choose this processing method if the BOM of the material that was configured in the
sales order, is to be changed on a customer-specific basis. In the Sales Order screen, assign
values to the characteristics.
Under AVC, the BOM is also exploded here. If available and set appropriately, can be
configured on multiple levels. If available and set appropriately, you can An engineer-to-order
(ETO) process.
Under LO-VC, in the standard process, the BOM is not exploded. The BOM components are
not dependent until the order BOM is processed determined by the characteristic value
assignment. Without a BOM, you can also configure only one level first. However, under LO-
VC, there are also deviations from this standard. Using a special flag (maintenance in order
allowed), a BOM explosion can be reached. A multilevel configuration is then also possible.
Prerequisites
The configuration profile of the configurable material specifies the “order BOM” process with
BOM explosion.

Figure 78: Order BOM: Step 1
Animation: Order BOM: Step 1

For more information on Order BOM: Step 1, please view the animation in the
lesson Configuration Profile in your online course.
Create a sales order and enter the configurable material as an order item.
You see the configuration editor, where you assign values to the characteristics of the
material.
As you enter characteristic values, dependencies for the characteristics and values are
processed.
Under AVC: Bill of Material is exploded in the sales order. Under LO-VC, we don't have a BOM
in sales order. (This is standard under LO-VC. We have also a BOM explosion under LO-VC, if
you use flag "maintenance in order allowed".)
If you have a BOM explosion in the sales order, characteristics can be subordinate
configurable materials are not valuated in the sales order.
The header material appears as a sales order item.
You can also create an order BOM for a quotation.

Figure 80: Order BOM: Step 2
Procedure:
● If you have created a sales order, process the Order BOM using special apps or
transaction. In these apps and transaction, explodes the entire structure of the order BOM.
You can assign subordinate configurable assemblies.
Under AVC, you can also change the configuration of header material.
In the technical clarification, you define which assemblies must be changed and which new
assemblies are required.
You can make the following changes to an order BOM:
Change BOM items (such as B. quantity); insert items; delete items;
Copy items; Cut items; Replace class items manually in LO-VC.
Under LO-VC only: Result-oriented order BOM:

● If you set this indicator, the configured order BOM is saved with all manual changes.
● If you do not set this indicator, the super BOM is saved with all manual changes and object
dependencies (selection conditions and procedures). When you call the BOM, the
selection conditions are processed automatically and only the selected items are
displayed.
Under LO-VC only: Automatic fixing:

● If this indicator is set, you can use the maintenance function to save an order BOM, even if
no changes are made to the BOM.
● If this indicator is not set, an order BOM is only created if you make manual changes to the
BOM.

Under LO-VC only: Maintenance allowed in Sales Order

The Maintenance in order allowed indicator allows you to go to the engineering view without
leaving sales order maintenance.
In the sales order, you see a button labeled Engineering.
● This means that the assigned values are temporarily fixed.
● The BOM can be exploded.
● You can do a multilevel configuration.
● You cannot maintain an order BOM in the sales order.
Figure 81: Group "Order Bill of Material“ in the Fiori Launchpad
Additional possibilities under AVC:

There are two additional apps:
If engineer-to-order production is recognized as required in the sales order, than this sales
order ends up in the "Order Engineering Worklist". From here, you can the engineering
process.
You can change the configuration. You can create order BOMs, In the order BOMS you can
create, change and delete items.
There is another app for managing existing order BOMs.

Sales Order: SET Processing
Figure 82: Sales Order: SET Processing 1
Purpose
You can use this processing type to describe variant products that comprise several salable
configurable materials. These products are supplied together, but are not assembled using a
production order.
For example, a fork lift is made up of the components drive, chassis, drivers carb and lift.
These components are all salable materials that can be manufactured and sold separately. In
the sales order, you want to see order items for the individual components that make up the
fork lift, as well as the whole fork lift. In sales order processing, these products are grouped
together in a SET. For this reason, this type of processing is also referred to as SET
processing.
Process Flow
Create a sales order and enter the configurable material as an order item. You see the
configuration editor, where you assign values to the characteristics of the material. You can
then display the result of the BOM explosion by choosing Result. You see all the sales-relevant
BOM components that are selected according to the values assigned.

Figure 83: Sales Order: SET Processing 2
Animation: Sales Order: SET Processing 2

For more information on Sales Order: SET Processing 2, please view the
animation in the lesson Configuration Profile in your online course.
This scenario means that in the sales order you can only process sales-relevant BOM items.
You can also configure the configurable assemblies that are sales relevant.
You can use constraints to infer characteristic values between assemblies.
Once you have configured all materials, you return to the order item entry screen.
All BOM items that were selected and are relevant to sales are displayed as subitems for the
main item in the sales order.
You can use the item category group to control requirements transfer and pricing at
component level.

Scenario: Planned- / Production Order with BOM Explosion
Figure 85: Scenario: Planned- / Production Order with BOM Explosion
Animation: Scenario: Planned- / Production Order with BOM Explosion

For more information on Scenario: Planned- / Production Order with BOM
Explosion, please view the animation in the lesson Configuration Profile in your
online course.
Multi-level configuration in Sales order:

● Configuration: Multilevel, interactive configuration of all configurable items (not only sales-
relevant items) in sales order.
● Characteristic values can be saved for each configurable component.
● Pricing for the header material
Sales BOM and Production BOM:

● You can use separate BOMs for sales and production.
● You can also combine the two, by defining sales-relevant items in a universal BOM.


Unit 4
Exercise 7
Create And Test A Configuration Profile
Simulation: Create And Test A Configuration Profile

For more information on Create And Test A Configuration Profile, please view the
simulation in the lesson Configuration Profile in your online course.
Business Scenario
In the model for the forklift configuration task, this step is to create the configuration profile.
This will make it possible to configure your forklift on one level with the advanced VC.
Task 1: Create Configuration Profile

Create a configuration profile for your forklift T-FCL## with the use of the modeling
environment.
1. Open the app VC Modeling Environment. It can be found in the group Variant Configuration
Modeling.
Material: T-FCL##
Date: Today’s date

Class Type: 300
Plant: 1010
BOM Application PP01
Enter Model.
On the left hand side, inside the tree, your material is visible.
Open the next level.
Your class 300 T_FCL## is displayed.
Note:
If the icon meaning is not clear for you, select the legends Icons box.
2. Select the material with the right mouse button and select Create Configuration Profile.
Material T_FCL## (grayed out)
(grayed out)

Class Type: 300 (grayed out)
Configuration Profile T-FCL##
Radio Button: Without Change No.
Radio Button: BOM Must Not Be Exploded for Material
Continue and in Basic Data, enter the following:
Processing Mode Advanced Variant Configuration
Process Plan.- / Production Order
BOM Explosion None
You get a pop up AVC behavior change … . Continue with Enter

Leave the rest as it is.
Save your configuration profile.
Task 2: Test your Settings

Check your work and test your scenario.
1. Select the Test button inside the header area. A new screen opens: Simulate Configuration
Models.
First answer the following question: which characteristics are single or multiple valued?
2. Assign values of your choice to all characteristics.
3. Check the result inside the tree control. Don’t use the entry Exploded BOM. Use the left
handed button and switch to Super BOM.
What is displayed now?
4. Change the view to your routing.
5. Close the simulation via Cancel and Yes.

Unit 4
Solution 7
Create And Test A Configuration Profile
Simulation: Create And Test A Configuration Profile

For more information on Create And Test A Configuration Profile, please view the
simulation in the lesson Configuration Profile in your online course.
Business Scenario
In the model for the forklift configuration task, this step is to create the configuration profile.
This will make it possible to configure your forklift on one level with the advanced VC.
Task 1: Create Configuration Profile

Create a configuration profile for your forklift T-FCL## with the use of the modeling
environment.
1. Open the app VC Modeling Environment. It can be found in the group Variant Configuration
Modeling.
Material: T-FCL##

Class Type: 300
Plant: 1010
Enter Model.
On the left hand side, inside the tree, your material is visible.
Note:
If the icon meaning is not clear for you, select the legends Icons box.
a) Open the App VC Modeling Environment.

It can be found in the group Variant Configuration Modeling.

Material: T-FCL##

Class Type: 300
Plant: 1010
Enter Model.
b) On the left hand side, inside the tree, your material is visible.
2. Select the material with the right mouse button and select Create Configuration Profile.
(grayed out)
Continue and in Basic Data, enter the following:
BOM Explosion None

a) Pull down menu Material → Create Configuration Profile.
b) Enter the following:

(grayed out)

c) Continue and in Basic Data, enter the following:

BOM Explosion None

Task 2: Test your Settings

Check your work and test your scenario.
1. Select the Test button inside the header area. A new screen opens: Simulate Configuration
Models.
First answer the following question: which characteristics are single or multiple valued?
a) Select the characteristics.
Characteristic Extras is multi-valued. When you open the selection screen, checkboxes
can be set.
All other characteristics just show drop down boxes, where one value can be selected.
2. Assign values of your choice to all characteristics.

a) Open the drop down boxes for every characteristic.
3. Check the result inside the tree control. Don’t use the entry Exploded BOM. Use the left
handed button and switch to Super BOM.
What is displayed now?
a) Display the Super BOM:
Select the button Toggle Super BOM .
All components are displayed. To get a reduced screen depending on your value
assignment, object dependencies have to be defined.
4. Change the view to your routing.

a) Use the button Routing in the row of Forklift … .
Every operation is displayed, no object dependencies are defined.
5. Close the simulation via Cancel and Yes.

LESSON SUMMARY

Unit 4
Learning Assessment
1. Which prerequisites must be fulfilled before you can assign a released configuration
profile to a material master?
X A Material must be configurable.
X B A variant class must be assigned to the material.
X C This variant class must contain characteristics.
X D A BOM must be assigned to the material.
X E A routing must be assigned to the material.
2. Which configuration scenarios exist for both classic and advanced processing mode.
Which configuration scenarios exist only for advanced processing mode.
X A Configuration Scenarios Planned Order / Production Order Without BOM

Explosion
X B Configuration Scenarios Planned Order / Production Order with BOM Explosion
X C Configuration Scenarios Order BOM
X D Configuration Scenarios Sales Order (SET)
X E There are no configuration scenarios only for advanced processing mode.


UNIT 5 Overview of Object
Dependencies
Lesson 1
Use and Types of Dependencies 135
Lesson 2
Paradigms of the SAP Configurator and Introduction to the Syntax 141
Lesson 3
Variant Tables, Functions and PMEVC 151
UNIT OBJECTIVES
● Explain the use, types and function of object dependencies

● Explain the paradigms of the SAP configurator
● Give an introduction the syntax
● Understand variant tables and functions
● Explain the benefits of the product modeling environment PMEVC

Unit 5: Overview of Object Dependencies

Unit 5
Lesson 1
Use and Types of Dependencies
LESSON OVERVIEW
Business Scenario
Your project team spent a lot of time building the variant configuration knowledge base. But
you noticed that the system selects all parts when you tried to configure a product. What
happens? What goes wrong? What is missing?
LESSON OBJECTIVES
Object Dependencies - Use and Types
Figure 88: Knowledge Base of Variant Configuration for Materials (1)

Figure 89: Knowledge Base of Variant Configuration for Materials (2)
Animation: Knowledge Base of Variant Configuration for Materials (2)

For more information on Knowledge Base of Variant Configuration for Materials
(2), please view the animation in the lesson Use and Types of Dependencies in
your online course.
Object Dependencies
Figure 91: Definition Local Object Dependencies

Lesson: Use and Types of Dependencies
Figure 92: Definition Global Object Dependencies
Dependency Types
Figure 93: Dependency Types
Animation: Dependency Types

For more information on Dependency Types, please view the animation in the
lesson Use and Types of Dependencies in your online course.
Assignment of Object Dependencies

Figure 95: Assignment of Object Dependencies
Figure 96: Object Dependencies in Classification and Variant Configuration
Processing Sequence of Object Dependencies

Lesson: Use and Types of Dependencies
Figure 97: Processing Sequence: Object Dependencies (Low Level)
Figure 98: Processing Sequence for Object Dependencies (High Level AVC)
Processing sequence BOM / Routing
1. Selection conditions for objects.
2. Procedures on objects have been excluded, as far as these objects are not selected due to
the selection conditions.
Processing Sequence AVC = Advanced processing mode

Starting the processing of the object, dependencies are processed as follows:
1. Starting with the $root object: Values set by procedures are reset.
2. The BAdI VCH_HL_PRE_VALIDATE_ASSIGN is processed.
$root instance

1. Constraints for only the $root object are processed and are also processed repeatedly if
the conditions change.
2. Static default values (static default values that lead to inconsistencies will be withdrawn
immediately.)
3. All procedures are evaluated exactly once, in the following order:

● Configuration profile
● Characteristics
● Characteristic values
The execution sequence of the procedures per object is defined at the level of the object
dependencies assignment.
Then area ll preconditions and then all selection conditions executed.
According to next level bill of materials explosion and "left" starting with step 2. Always taking
into account an additional instance. (Finally, the procedures that are set to this $root level are
processed again (due to pricing, etc.).
The BAdI VCH_HL_POST_VALIDATE_ASSIGN is processed.
If an unrecoverable inconsistency is found, the processing terminates at this point. (Not under
LO-VC = classical Processing Mode).
There are two additional BADIs that you can use when branching to the configuration and
from the configuration can be processed.
Processing Sequence LO-VC = Classic processing mode
The following processing sequence applies to the value assignment user interface in high-
level configuration.
The processing is started according to the settings during data release or on request.
The object dependencies of the configuration profile, valuated characteristics and
characteristic values is used.
All procedures exactly once in the following sequence:
● Characteristics
● Characteristic values
Within each object, the procedures are executed in the order which you define.
All actions as far as changes have been made by the procedures ( all constraints are
processed immediately for which relevant changes.)
All preconditions and then the selection conditions.
LESSON SUMMARY

Unit 5
Lesson 2
Paradigms of the SAP Configurator and
Introduction to the Syntax
LESSON OVERVIEW
Business Scenario
Your project team wants to get an overview of the paradigms of the SAP configurator and its
syntax.
LESSON OBJECTIVES
Paradigms of the SAP Configurator and Introduction to the Syntax
Figure 99: Paradigms of the SAP-Configurator
In declarative dependencies, the point in time when the dependency is processed and the
sequence in which the dependencies are processed are not relevant to the result. The result
of a declarative dependency can be explained logically.
The dependency describes a rule that must always apply. This contrasts with procedural
dependencies, where the result depends on the processing sequence and the point in time

when the dependency is processed. Some expressions are in themselves non-declarative. For
this reason, these expressions cannot be used in declarative object dependencies:
NOT SPECIFIED; NOT TYPE_OF; <multiple-value characteristic> NE <value>
You can use these expressions in preconditions and selection conditions. Since preconditions
and selection conditions are not processed until the end of the configuration process, you can
assume that values have been assigned to all the characteristics that are intended to have
values, and that any missing information is deliberately not given.
When the not equals (NE) expression is processed for multiple-value characteristics, there is
a difference between constraints and actions. In constraints, not equals can be expressed for
multiple-value characteristics, because individual values are processed in constraints. In
actions, however, the sum of the selected values is processed. Since it is not clear whether it
is deliberate that no value was selected for a multiple-value characteristic or whether a value
will be assigned at a later point in time, this expression cannot be processed in actions.
Dependencies, classes, and objects support a declarative and object-oriented solution for a
knowledge base. The system determines the processing sequence of the object
dependencies and ensures that they are only executed when required.
Syntax
Figure 100: Syntax – General Comments

Lesson: Paradigms of the SAP Configurator and Introduction to the Syntax
Figure 101: Syntax – General Rules
Syntax – Variables for Objects and Characteristics
Figure 102: Syntax – Variables for Objects and Characteristics (1)

Operators

Figure 105: Operators
Animation: Operators
For more information on Operators, please view the animation in the lesson
Paradigms of the SAP Configurator and Introduction to the Syntax in your online
course.
Arithmetical Expressions
Figure 107: Arithmetical Expressions
Intervals

Figure 108: Intervals
Specified
Figure 109: Specified
Animation: Specified
For more information on Specified, please view the animation in the lesson
Paradigms of the SAP Configurator and Introduction to the Syntax in your online
course.
TYPE_OF

Figure 111: TYPE_OF
Character String Operators
Figure 112: Character String Operators

Additional Syntax
Figure 113: More Syntax Elements
Example for mdata:

Item quantity “1” is entered in the bill of material, and T_POS_MENGE is a reference
characteristic with reference to database field.
STPO-MENGE.
This triggers the following procedure:
$self.t_pos_menge = $self.t_pos_menge + 1,
$self.t_pos_menge = $self.t_pos_menge * 2
This produces the value 1 for the item quantity since the procedure terminates.
The subsequent procedure is then triggered:
$self.t_pos_menge = mdata $self.t_pos_menge + 1,
$self.t_pos_menge = $self.t_pos_menge * 2
This produces the value 4 for the item quantity.
The subsequent procedure is then triggered:
$self.t_pos_menge = mdata $self.t_pos_menge + 1,
$self.t_pos_menge = mdata $self.t_pos_menge * 2
This produces the value 2 for the item quantity.

Figure 114: More New Syntax Elements
Figure 115: Dependency Status
Animation: Dependency Status

For more information on Dependency Status, please view the animation in the
lesson Paradigms of the SAP Configurator and Introduction to the Syntax in your
online course.
Local and global object dependencies have a status.

Object dependencies can have the status Released , only if the syntax has no errors. An empty
syntax is an error.

For global object dependencies, a manual-only conversion of a status is available.

For local object dependencies, an automatic release is available as well.
LESSON SUMMARY

Unit 5
Lesson 3
Variant Tables, Functions and PMEVC
LESSON OVERVIEW
Business Scenario
Your project team wants to get an overview of variant tables, functions and traces. When
should which tools be used sensibly?
LESSON OBJECTIVES
Variant Tables
Figure 117: Variant Tables (1)

Figure 118: Variant Tables (2)
Animation: Variant Tables (2)

For more information on Variant Tables (2), please view the animation in the
lesson Variant Tables, Functions and PMEVC in your online course.
Variant Functions
Figure 120: Variant Functions and BAdIs

Lesson: Variant Tables, Functions and PMEVC
Animation: Variant Functions and BAdIs

For more information on Variant Functions and BAdIs, please view the animation
in the lesson Variant Tables, Functions and PMEVC in your online course.
No variant functions are available under advanced processing mode AVC. order. Instead, you
work with BAdIs. These are/were created with releases realized in 2019.
New BAdIs in AVC
Figure 122: New BAdIs in AVC
VCH_HL_MD_DOMAIN_MODIFY
Overrule the values predefined in the characteristic master data
Execution
— Only AVC high-level configuration
— First activation of a configurable instance
Scope
— Add new domain values and intervals
— Delete predefined domain values
— Change certain attributes of predefined values
Use Case Examples

— Build-up empty domains from tables including language-specific description for string
characteristics
— Add temporary values for special promotions
— Change value description for certain customers
— Change static defaults, for example, for certain customer materials
— Restrict domains on level of configuration model

VCH_HL_PRE_VALIDATE_ASSIGN
Modify value assignments before processing the dependencies
Execution
— Every round trip before dependency processing
— Considered in high-level dependency processing
— Control assignment on all instances
Scope
— Add new assignments
— Delete value assignments
Use Case Examples:

— Call external web service, RFCs, other APIs
— Call external engine, for example, BRF+
— Pass values from one instance to another instance without specifying every characteristic
— Read other class types like 001, 019, 017 and z-tables
— Read master data table (only data stored on database) for value assignment
— Check user inputs before dependency processing
— Replaces many variant functions of LO-VC
VCH_HL_POST_VALIDATE_ASSIGN
Modify value assignments after processing the dependencies
Execution
— Every round trip after dependency processing
— NOT Considered in high-level dependency processing
Scope
— Add new assignments (all instances)
— Delete value assignments (all instances)
Use Case Examples:

— Switch author to external assignments (avoid changes by user)
— $SUM_PART; $COUNT_PART (if not needed in validation)
— Calculation of weights, surfaces, electrical and mechanical parameters
— Ability to review fully configured object looking for specific information and set a value
— Replaces many variant functions of LO-VC
VCH_HL_ON_SAVE
Modify value assignments while leaving configuration

Execution
— While leaving configuration
— NOT Considered in high-level dependency processing
Scope
— Lock configuration
— Add new assignments
— Delete value assignments
Use Case Examples:

— Special checks on valuation consistency
— Set values for other processes to use (customer tables)
— Delete values of helper characteristics (not to be stored to CBASE)
Traces
The processing of object dependencies is not documented in the standard system. However,
documentation can be activated using the trace.
A trace exists under LO-VC.
Figure 123: Trace- Function in Variant Configuration
Animation: Trace- Function in Variant Configuration

For more information on Trace- Function in Variant Configuration, please view
the animation in the lesson Variant Tables, Functions and PMEVC in your online
course.
A trace also exists under AVC. This was greatly expanded in 2019.

Figure 125: Trace Under AVC 1
Figure 126: Trace Under AVC 2
Inconsistent

Figure 127: Inconsistent
Product Modeling Environment

The product modeling environment PMEVC represents a different transaction. It contains a
large proportion of the modeling activities that were previously spread over many
transactions. These previous transactions remain valid. In addition, the product modeling
environment includes new functionality and legacy functionality in a more elegant way. You
can always switch between the PMEVC and the previous transactions.
The product modeling environment supports all steps for interactive configuration - the "in-
light" configuration - generally the configuration in sales.
This means:
● Create and change configuration profile
● Assign variant classes
● Create and change characteristics and assign them to variant classes
● Create and change object dependencies
● Assign dependencies or create from the assignment for configuration profile,
characteristic, BOM and routing
● Create and change variant tables together with content
● Create and change variant functions
● Create knowledge base and runtime version for IPC
Better realized:
● Dependency maintenance
● Create and change interface design under LO-VC, but also Characteristic groups under
AVC
● Assign variant conditions

● Simulation
● Drag and drop - functionality
Figure 128: Product Modeling Environment
Figure 129: PMEVC- View

Animation: PMEVC- View

For more information on PMEVC- View, please view the animation in the lesson
Variant Tables, Functions and PMEVC in your online course.
The Navigation area displays the material number, the source date, and some buttons.
The button Explode model makes it possible that all model-related objects are copied to the
work list.
Object tree contains of the following:
● Root material
● Variant classes
● Material BOMs and routings
● Knowledge base object and runtime version
● All other objects: description, characteristics status, values and dependencies are
displayed on the detail view (double click on object).
Worklist contains all objects, exploded inside the tree.

Details shows you the object details you selected inside object tree with a double click.
If you select Overview of the changed objects, the system displays the objects of the model
that you have changed since the last save, that is, objects that have not yet been backed up.
From here you can navigate to the object detail screen by clicking double-click on the object.
Figure 131: PMEVC Maintenance (1)

Figure 132: PMEVC Maintenance (2)
LESSON SUMMARY

Unit 5
Learning Assessment
1. What types of object dependencies can be used in material BOMs and routings?
X A Precondition
X B Selection condition
X C Procedures
X D Constraints and Constraint nets
2. In what types of object dependencies can instances with $self $parent and $root be
addressed?
X A Precondition
X B Selection condition
X C Procedures
X D Constraints
X E Constraint nets
3. With the modeling environment PMEVC, you can perform almost all steps of modeling the
model in Variant Configuration. Some master data cannot be created or changed with the
PMEVC. What are these?
X A You cannot create or change a material master with the PMEVC.
X B You cannot create or change characteristics with the PMEVC.
X C You cannot create classes with the PMEVC.
X D You cannot create or change configuration profiles with the PMEVC.
X E You cannot create or change BOMs with PMEVC.
X F You cannot create or change routings with PMEVC.


UNIT 6 Object Dependencies in BOMs
and Task Lists
Lesson 1
Selection Condition in BOMs and Task Lists 164
Exercise 8: Material BOM: Object Dependencies 169
Exercise 9: Routing: Object Dependencies 197
Lesson 2
Class Nodes 214
Exercise 10: Maintain Class Nodes 217
Lesson 3
Procedures with Reference Characteristics (Quantity and Time Change) 229
Exercise 11: Change the Component Quantity (Reference Characteristics) 233
UNIT OBJECTIVES
● Define selection conditions in BOMs and task lists

● Explain the benefits of class nodes
● Define and work with class nodes
● Define procedures with reference characteristics (quantityand time change)
● Change time and quantity with procedures

Unit 6
Lesson 1
Selection Condition in BOMs and Task Lists
LESSON OVERVIEW
Business Scenario
You have to control the interactive and dynamic selection of BOM components and routing
operations.
LESSON OBJECTIVES
Dependencies in BOMs and Task Lists
Figure 133: Dependencies in BOMs and Task Lists
The object dependency is assigned to the object that it is meant to influence according to its
task. Before you create a dependency, you must select the appropriate dependency type. The
dependency type then determines how the syntax is checked in the dependency editor.
Selection conditions are used to select the appropriate BOM component, task list operations,
PRT, and so on from the super BOM and/or routing.
Procedures are used to change the item or operation data. Procedures can incorporate the
output quantity in the calculation. This also allows overwriting.

Lesson: Selection Condition in BOMs and Task Lists
Animation: Dependencies in BOMs and Task Lists

For more information on Dependencies in BOMs and Task Lists, please view the
animation in the lesson Selection Condition in BOMs and Task Lists in your online
course.
Figure 135: Selection Condition for a BOM
Animation: Selection Condition for a BOM

For more information on Selection Condition for a BOM, please view the
course.
Depending on the characteristic values you assign during value assignment, you can define
which BOM components are selected.
For example, if you assigned the value 'fix’ to characteristic SEAT, you can use a selection
condition to determine that the BOM component for the Seat fix is selected.
If a different value is chosen for the characteristic SEAT, the BOM component for the Seat fix
is not selected. If characteristic SEAT has no value, the BOM component for the Seat fix is not
selected either. Please note that this is different to the effect of preconditions!
When you create a selection condition, you have the following options:
● Create locally (for the BOM item)
● Create globally (uses a separate menu path and is identified by a name)

Unit 6: Object Dependencies in BOMs and Task Lists
Once a global selection condition has been created, it must be assigned to the appropriate
object(s). A selection condition is fulfilled if the value in the condition is set for the
characteristic.
A selection condition is not fulfilled if:
● A different value is set for the characteristic
● No value is selected for the characteristic
Selection Condition in BOMs: Classic and Advanced
Figure 137: PMEVC: Selection Conditions in BOMs
Animation: PMEVC: Selection Conditions in BOMs

For more information on PMEVC: Selection Conditions in BOMs, please view the
course.
With the help of PMEVC (Product Modeling Environment), we can create and maintain object
dependencies in BOMs.
● Create and assign object dependencies
● Create local and global object dependencies
● With the help of drag and drop (single value of a characteristic), we can create syntax
● With help of drag and drop (single or multiple values of a characteristic), we can create
complete new local (but possibly also global), object dependencies as Selection condition
is created. Local or global can be set.

Figure 139: Selection Condition for a Task List
You use selection conditions for a task list to define which sequences, operations,
suboperations, and production resources/tools (PRTs) are to be selected for a specific
variant.
In this example the operation Assy Road Set is only selected if a value is assigned to
characteristic EXTRAS. Note the special keyword in the syntax, Specified. By using the
keyword Specified in a selection condition, you state that it does not matter which value is
assigned to the characteristic: any value triggers the selection condition.
Figure 140: Selection Condition: PRT in Task Lists

Animation: Selection Condition: PRT in Task Lists

For more information on Selection Condition: PRT in Task Lists, please view the
course.
The production resource/tool (PRT for ## mast height) is assigned to operation 500 (Assy
Lift).
You use a selection condition to define that the PRT is selected only if the value Large is
assigned to the characteristic Mast height. If a value other than Large is assigned to the
characteristic Mast height, operation 500 appears without an assigned PRT in the task list
explosion.
Before operation 500 Assy Lift can be selected at all, a value must be assigned to the
characteristic lift. However, it does not matter which value is assigned to the characteristic.

Unit 6
Exercise 8
Material BOM: Object Dependencies
Simulation: Material BOM: Object Dependencies

For more information on Material BOM: Object Dependencies, please view the
simulation in the lesson Selection Condition in BOMs and Task Lists in your
online course.
Business Scenario
When we simulated the configuration, we saw that the super BOM was displayed in the
configuration result. We now have to create and assign object dependencies so that we can
select the correct components from the super BOM and create a BOM that can be used to
manufacture the configured product.
Task 1: Check your Material BOMs

Verify in both material BOMs that no object dependencies exist.
1. Open the following BOM in display mode. Use the app Display Material BOM in group
Product Engineering .
Enter:
Material: T-FCL##
Plant: 1010
Usage: 1
Check the components and the object dependencies indicator.

No indicator is visible.
Close the BOM.
Enter:
Material: T-FCX##
Plant: 1010
Usage: 1

Close the BOM.

Task 2: First Object Dependencies

Create five selection conditions.
1. Open the app VC Modeling Environment.

Material: T-FCL##
Change Number: no entry
Class Type: 300
Plant: 1010
BOM application PP01
Continue with Enter Model.

Before you continue, check the following settings:
→ More → Extras → Settings... → Tab Page Dependencies → Radio button: Create
Global Selection Condition. Choose Continue.
2. Create a first selection condition that selects the correct BOM component for the Road
Equipment, depending on the values assigned to characteristic T_FCLX_##.
Open the object tree and the first level of your material BOM and your class. The
characteristics and components should be visible.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value A.
Open:
Material BOM 1 01 → Item 0080 L T-FCX## → Material T-FCX## → material BOM 1 01
→ Item 0010 L T-FL8A00.
Set the checkbox for value A- Road Equipment.
Now drag your characteristic value A to item 0010 L T-FL8A00.
A pop-up appears: Open Bill of Material.
→ Continue.
A pop-up appears: Create Selection Condition for BOM item.
Enter:
Dependency: T_SEL_FCLX##_EQ_A
Description: Sel, Cond. Road Equipment ##
The status is set to released.

Add the group T-##.
Save your Selection Condition.
3. Create a second selection condition that selects the correct BOM component for the
Additional Lighting, depending on the values assigned to characteristic T_FCLX_##.

Open the tree and the first level of your material BOM and your class. The characteristics
and components should be visible.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value B
Open:
→ Item 0030 L T-FL8C00
Set the checkbox for Value B- Additional Lighting.
Now drag your characteristic value B to item 0030 L T-FL8C00.
→ Continue:
Enter:
Dependency: T_SEL_FCLX##_EQ_B
Description: Sel, Cond. Add. Lighting ##

Add the group T-##.
4. Create a third selection condition that selects the correct BOM component for the Rear
view camera, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value C
Open:
→ Item 0020 L T-FL8B00
Set the checkbox for Value C- Rear View Camera.
Now drag your characteristic value C to item 0020 L T-FL8B00.
→ Continue.
Enter:
Dependency: T_SEL_FCLX##_EQ_C
Description: Sel. Cond. Rear View Camera##

Add the group T-##.

5. Create a fourth selection condition that selects the correct BOM component for the
Driving mirror small, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value D
Open:
→ Item 0040 L T-FV5C01
Set the checkbox for Value D- Driving Mirror Small.
Now drag your characteristic value D to item 0040 L T-FV5C01.
→ Continue.
A pop-up appears: Create Selection Condition for BOM item..
Enter:
Dependency: T_SEL_FCLX##_EQ_D
Description: Sel, Cond. Drv. Mirr. Small ##

Add the group T-##.
6. Create a fifth selection condition that selects the correct BOM component for the Driving
Mirror large, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value E
Open:
Set the checkbox for Value E- Driving Mirror Large.
Now drag your characteristic value E to item 0050 L T-FV5C02.
→ Continue.
Enter:

Dependency: T_SEL_FCLX##_EQ_E
Description: Sel, Cond. Drv. Mirr. Large ##

Add the group T-##.
7. Test your definition of your selection conditions.

A new tab page opens.
As long as the characteristic Extras is empty, component T-FCX## can’t be opened.
Assign a value for Extras of your choice.
Refresh the tree view and the material BOM for component T-FCX## can open.
8. Close your simulation tab page. Open the Configuration screen again. Do not leave the
app.
Task 3: Second Part for Selection Conditions

Create the right selection conditions for your BOM items depending on the values of
characteristics T_FCLG## and T_FCLH##. Add the date with the following content:
Component: Syntax Name Description: Syntax

T-FV5D01 T_SEL_FCLG_H##_EQ_1_1 Sel Cond. fix + T_FCLG##= '1' and
Stand ## T_FCLH## = '1'
T-FV5D02 T_SEL_FCLG_H##_EQ_1_2 Sel Cond. fix+ HR. T_FCLG## = '1' and
## T_FCLH## = '2'
T-FV5D03 T_SEL_FCLG_H##_EQ_1_3 Sel Cond. fix + Ex- T_FCLG## = '1' and
tend. ## T_FCLH##= '3'
T-FV5D04 T_SEL_FCLG_H##_EQ_2_1 Sel Cond rota. + T_FCLG## = '2' and
T-FV5D05 T_SEL_FCLG_H##_EQ_2_2 Sel Cond rota + HR T_FCLG## = '2' and
## T_FCLH## = '2'
T-FV5D06 T_SEL_FCLG_H##_EQ_2_3 Sel Cond rota + Ex- T_FCLG## = '2' and
tend.. ## T_FCLH## = '3'
1. Work again with the tree on the left hand side. Navigate as follows:
→ Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLG## → Value 1.
→ Material BOM 1 01 → item 0030 L T-FV5D01 .
Set the checkbox for characteristic value 1.
Drag Characteristic value 1 to item 0030 L T-FV5D01 and drop.
→ Continue.
Enter:

Dependency: T_SEL_FCLG_H##_EQ_1_1
Description: Sel, Cond. fix + Stand. ##

Add the group T-##.
Save your selection condition.
The first part is created. Open the tab page Editor. Click on the “Pencil” in the header area
to edit the syntax. A pop-up appears. Choose Continue.
At the moment, you see the following syntax: T_FCLG## = '1'
Place your cursor at the end of the syntax and select the Input Help (F4) button.
Inside the pop-up, select Operators → AND. Choose Continue.
=> Syntax added.
Inside the pop-up, select Symbolic Characters → T_FCLH## . Choose Continue.
Inside the pop-up select → Operators → = Choose Continue.
Inside the pop-up, select → Symbolic values → 1. Choose Continue.
Now your syntax is as follows:
T_FCLG##= '1' and T_FCLH## = '1'
Check your syntax. The syntax check should be error free.

Save your syntax.
2. Now repeat the step for the following:

T-FV5D02 T_SEL_FCLG_H##_EQ_1_2 Sel Cond. fix+HR. T_FCLG## = '1' and

## T_FCLH = '2'
→ Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLG## → Value 1

→ Material BOM 1 01 → item 0030 L T-FV5D02
→ Continue.
Enter:

Description: Sel, Cond. fix + HR. ##

Add the group T-##.
The first part is created. Open the tab page Editor.
Place your cursor at the end of the syntax, and enter the following manually:
AND T_FCLH## = '2'
=> Syntax added.

Save your syntax.

T-FV5D03 T_SEL_FCLG_H##_EQ_1_3 Sel Cond. fix+ex- T_FCLG## = '1' and

tend. ## T_FCLH## = '3'

→ Continue.
Enter:
Description: Sel Cond. fix+extend. ##

Add the group T-##.
At the moment you see the following syntax: T_FCLG## = '1'
Place your cursor at the end of the syntax and enter the following manually:
AND T_FCLH## = '3'
=> Syntax added.

Save your syntax.


T-FV5D04 T_SEL_FCLG_H##_EQ_2_1 Sel Cond. Rota T_FCLG## = '2' and

+stand. ## T_FCLH## = '1'

→ Continue
Enter:
Description: Sel Cond. Rota+stand. ##

Add the group T-##.
At the moment you see the following syntax. T_FCLG## = '2'
AND T_FCLH## = '1'
=> Syntax added.



+HR ## T_FCLH## = '2'

→ Continue.

Enter:
Description: Sel Cond. Rota+HR ##

Add the group T-##.
AND T_FCLH## = '2'
=> Syntax added.



+Extend ## T_FCLH## = '3'

→ Continue.
Enter:
Description: Sel Cond. Rota+Extend ##

Add the group T-##.
AND T_FCLH## = '3'
=> Syntax added.



A new screen opens.
Switch the view to Super BOM.
As long as the characteristic Driving Seat and Seat back are empty, Component T-FV5D0#
is empty.
If you assign any values, refresh the tree view and the component T-FV5D0# is visible.
8. Close the view.
9. Stay in the VC Modeling Environment app.

Unit 6
Solution 8
Material BOM: Object Dependencies
Simulation: Material BOM: Object Dependencies

For more information on Material BOM: Object Dependencies, please view the
online course.
Business Scenario
When we simulated the configuration, we saw that the super BOM was displayed in the
configuration result. We now have to create and assign object dependencies so that we can
select the correct components from the super BOM and create a BOM that can be used to
manufacture the configured product.
Task 1: Check your Material BOMs

Verify in both material BOMs that no object dependencies exist.
Enter:
Material: T-FCL##
Plant: 1010
Usage: 1

Close the BOM.
a) Use the app Display Material BOM.
Enter the key information and check the components view.
Leave the material BOM.
Enter:
Material: T-FCX##
Plant: 1010
Usage: 1


Close the BOM.
a) Use the app Display Material BOM.
Enter the key information and check the components view.
Leave the material BOM.
Task 2: First Object Dependencies

Create five selection conditions.
1. Open the app VC Modeling Environment.

Material: T-FCL##
Change Number: no entry
Class Type: 300
Plant: 1010
Continue with Enter Model.

Before you continue, check the following settings:
→ More → Extras → Settings... → Tab Page Dependencies → Radio button: Create
Global Selection Condition. Choose Continue.
a) Open the app VC Modeling Environment.
b) Check the settings:

→ More → Extras → Settings... → Tab Page “Dependencies” → radio Button:
Create Global Selection Condition . Choose Continue.
2. Create a first selection condition that selects the correct BOM component for the Road
Equipment, depending on the values assigned to characteristic T_FCLX_##.
Open the object tree and the first level of your material BOM and your class. The
characteristics and components should be visible.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value A.
Open:
→ Item 0010 L T-FL8A00.
Set the checkbox for value A- Road Equipment.
Now drag your characteristic value A to item 0010 L T-FL8A00.
→ Continue.


Enter:

Add the group T-##.
a) Open the tree:
Open the first level of your material BOM and your class. The following should be
visible:
→ Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value
A
Note:
For better drag and drop, set the checkbox on the left hand side.
and → Material BOM 1 01 → Item 0080 L T-FCX## → Material T-FCX## → material

BOM 1 01 → Item 0010 L T-FL8A00.
b) Now drag your characteristic value A to item 0010 L T-FL8A00.

→ Continue.
Enter:

Add the group T-##.
Save your selection Condition.
3. Create a second selection condition that selects the correct BOM component for the
Additional Lighting, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value B
Open:
→ Item 0030 L T-FL8C00

Set the checkbox for Value B- Additional Lighting.

Now drag your characteristic value B to item 0030 L T-FL8C00.
→ Continue:
Enter:
Description: Sel, Cond. Add. Lighting ##

Add the group T-##.
a) Open the tree.
visible:
B
Note:

BOM 1 01 → Item 0030 L T-FL8C00.
b) Now drag your characteristic value B to item 0030 L T-FL8C00.

→ Continue.
A pop-up appears Create Selection Condition for BOM item.
Enter:
Description: Sel, Cond. Add Lighting ##

Add the group T-##.
4. Create a third selection condition that selects the correct BOM component for the Rear
view camera, depending on the values assigned to characteristic T_FCLX_##.
Open:

Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value C

Open:
→ Item 0020 L T-FL8B00
Set the checkbox for Value C- Rear View Camera.
Now drag your characteristic value C to item 0020 L T-FL8B00.
→ Continue.
Enter:

Add the group T-##.
a) Open the tree.
visible:
C
Note:
For better drag and drop, set the check box on the left hand side.

BOM 1 01 → Item 0020 L T-FL8B00
b) Now drag your characteristic value C to item 0020 L T-FL8B00.

→ Continue.
Enter:

Add the group T-##.

5. Create a fourth selection condition that selects the correct BOM component for the
Driving mirror small, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value D
Open:
Set the checkbox for Value D- Driving Mirror Small.
Now drag your characteristic value D to item 0040 L T-FV5C01.
→ Continue.
A pop-up appears: Create Selection Condition for BOM item..
Enter:

Add the group T-##.
a) Open the tree.
visible:
D
Note:

BOM 1 01 → Item 0040 L T-FV5C01
b) Now drag your characteristic value D to item 0040 L T-FV5C01.

→ Continue.
A pop- up appears: Create Selection Condition for BOM item.
Enter:


Add the group T-##.
6. Create a fifth selection condition that selects the correct BOM component for the Driving
Mirror large, depending on the values assigned to characteristic T_FCLX_##.
Open:
Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLX## → Value E
Open:
Set the checkbox for Value E- Driving Mirror Large.
Now drag your characteristic value E to item 0050 L T-FV5C02.
→ Continue.
Enter:

Add the group T-##.
a) Open the tree.
visible:
E
Note:

BOM 1 01 → Item 0050 L T-FV5C02
b) Now drag your characteristic value E to item 0050 L T-FV5C02.


→ Continue.
Enter:

Add the group T-##.

A new tab page opens.
As long as the characteristic Extras is empty, component T-FCX## can’t be opened.
Assign a value for Extras of your choice.
Refresh the tree view and the material BOM for component T-FCX## can open.
a) Select the box Test.
b) As long as the characteristic Extras is empty, Component T-FCX## can’t be opened.
c) If you assign a value, refresh the tree view and the material BOM for component T-
FCX## can be opened.
8. Close your simulation tab page. Open the Configuration screen again. Do not leave the
app.
a) In case you close the screen, reopen the app VC Modeling Environment. Enter the data
from the first step.
Task 3: Second Part for Selection Conditions

Create the right selection conditions for your BOM items depending on the values of
characteristics T_FCLG## and T_FCLH##. Add the date with the following content:

T-FV5D01 T_SEL_FCLG_H##_EQ_1_1 Sel Cond. fix + T_FCLG##= '1' and
T-FV5D02 T_SEL_FCLG_H##_EQ_1_2 Sel Cond. fix+ HR. T_FCLG## = '1' and
## T_FCLH## = '2'
T-FV5D03 T_SEL_FCLG_H##_EQ_1_3 Sel Cond. fix + Ex- T_FCLG## = '1' and
tend. ## T_FCLH##= '3'
T-FV5D04 T_SEL_FCLG_H##_EQ_2_1 Sel Cond rota. + T_FCLG## = '2' and
T-FV5D05 T_SEL_FCLG_H##_EQ_2_2 Sel Cond rota + HR T_FCLG## = '2' and
## T_FCLH## = '2'
T-FV5D06 T_SEL_FCLG_H##_EQ_2_3 Sel Cond rota + Ex- T_FCLG## = '2' and
tend.. ## T_FCLH## = '3'

1. Work again with the tree on the left hand side. Navigate as follows:
→ Material T-FCL## → Class 300 T_FCL## → Characteristic T_FCLG## → Value 1.
→ Material BOM 1 01 → item 0030 L T-FV5D01 .
→ Continue.
Enter:
Description: Sel, Cond. fix + Stand. ##

Add the group T-##.
Save your selection condition.
The first part is created. Open the tab page Editor. Click on the “Pencil” in the header area
to edit the syntax. A pop-up appears. Choose Continue.
Inside the pop-up, select Operators → AND. Choose Continue.
=> Syntax added.
Inside the pop-up, select Symbolic Characters → T_FCLH## . Choose Continue.
Inside the pop-up select → Operators → = Choose Continue.
T_FCLG##= '1' and T_FCLH## = '1'

Save your syntax.
a) Work again with the tree on the left hand side. Navigate as follows:
→ Material BOMe 1 01 → item 0030 L T-FV5D01
A pop— up appears: Open Bill of Material.

→ Continue.
Enter:
Description: Sel, Cond. fix + stand. ##

Add the group T-##.
Save your syntax.
b) Now add the second part.

Go in Change-Mode (Pencil-Button).
Inside the pop-up, select → Operators → AND. Choose Continue.
=> Syntax added.
Inside the pop-up, select → Symbolic Characters → T_FCLH## . Choose Continue.
Inside the pop-up, select → Operators → = . Choose Continue.
T_FCLG## = '1' and T_FCLH## = '1'
c) Save your syntax.

T-FV5D02 T_SEL_FCLG_H##_EQ_1_2 Sel Cond. fix+HR. T_FCLG## = '1' and

## T_FCLH = '2'


→ Continue.
Enter:

Add the group T-##.
The first part is created. Open the tab page Editor.
Place your cursor at the end of the syntax, and enter the following manually:
AND T_FCLH## = '2'
=> Syntax added.

Save your syntax.
→ Continue:
Enter:

Add the group T-##.

AND T_FCLH##= '2'

T_FCLG## = '1' and T_FCLH## = '2'


T-FV5D03 T_SEL_FCLG_H##_EQ_1_3 Sel Cond. fix+ex- T_FCLG## = '1' and

tend. ## T_FCLH## = '3'

→ Continue.
Enter:

Add the group T-##.
AND T_FCLH## = '3'
=> Syntax added.

Save your syntax.
→ Continue:
Enter:


Add the group T-##.

AND T_FCLH## = '3'

T_FCLG## = '1' and T_FCLH## = '3'
c) Save your selection condition.


+stand. ## T_FCLH## = '1'

→ Continue
Enter:

Add the group T-##.
At the moment you see the following syntax. T_FCLG## = '2'
AND T_FCLH## = '1'
=> Syntax added.


→ Continue.
Enter:

Add the group T-##.

AND T_FCLH## = '1'

T_FCLG## = '2' and T_FCLH## = '1'
c) Save your selection condition.


+HR ## T_FCLH## = '2'

→ Continue.
Enter:


Add the group T-##.
AND T_FCLH## = '2'
=> Syntax added.

→ Continue.
Enter:

Add the group T-##.

AND T_FCLH## = '2'

T_FCLG## = '2' and T_FCLH## = '2'


+Extend ## T_FCLH## = '3'


→ Continue.
Enter:

Add the group T-##.
AND T_FCLH## = '3'
=> Syntax added.

→ Continue.
Enter:

Add the group T-##.

AND T_FCLH## = '3'


T_FCLG## = '2' and T_FCLH## = '3'
c) Save the syntax.

A new screen opens.
Switch the view to Super BOM.
As long as the characteristic Driving Seat and Seat back are empty, Component T-FV5D0#
is empty.
If you assign any values, refresh the tree view and the component T-FV5D0# is visible.
a) Select the box Test.
b) Switch the view to Super BOM.
c) As long as the characteristic Driving Seat and Seat back are empty, Component T-
FV5D0# is empty.
d) If you assign any values, refresh the tree view and one of the components T-FV5D0# is
visible.
8. Close the view.
9. Stay in the VC Modeling Environment app.


Unit 6
Exercise 9
Routing: Object Dependencies
Simulation: Routing: Object Dependencies

For more information on Routing: Object Dependencies, please view the
online course.
Business scenario
The configuration modeling is also relevant to the routing of the forklift. In order to select the
required operation(s) and PRTs, selection conditions, similar to those for the BOM, are
needed. You now must either write new rules or use valid existing rules to select these
objects.
Task 1: Selection Conditions for Operations

Stay inside VC Modeling environment.
1. You created the following routing for your forklift:

Operation Work Center Description
100 T-E00 Allocation components

200 T-F00 Assy Drive -> chassis
300 T-G00 Chassis under carriage
400 T-H00 Driver's carb assy
500 T-K00 Assy Hydraulics with lift
600 T-M00 Assy lift with chassis
— — with PRTS
700 T-L00 Varnishing
800 T-P00 Assy road equipment
810 T-P00 Assy rear view camera
820 T-P00 Add lights
900 T-Z00 Final inspec + road test
— — with PRTS
Check which selection conditions are relevant for the following scenario:
Operations 800, 810 and 820 are only selected depending on the assignment of extras
characteristic T_FCLX##.

Which new selection conditions are required?
2. If necessary, open your modeling environment again. Assign the selection conditions to
your routing operations.
Optional: Execute again the app VC Modeling Environment.
Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
BOM Application: PP01
Enter Model.
Open the routing and check the operations.
Operation 800:
● right mouse click → Assign Dependency:
● Confirm the pop-up.
● Enter: T_SEL_FCLX##_EQ_A
Save your data.

Operation 810:
● Enter: T_SEL_FCLX##_EQ_C
Save your data.

Operation 820:
● Enter: T_SEL_FCLX##_EQ_B
Save your data.
3. Test your dependencies.

On the left hand side, change the view from Exploded BOM to Routing.
At the moment, no characteristic value assignment took place. So operation 800, 810, and
820 are not displayed.
Select for the accessories a value of your choice.

Refresh the displayed routing.

The relevant operation is visible.
Repeat now with the other characteristic assignments.
Leave the simulation open.
4. Check the PRT assignments on operation 600.

At the moment no assignment is visible.
Open the Toggle Inspector on the right hand side.
Double click on operation 0600. The details open.
Basic information is displayed. Check the other icons. PRTs are displayed.
Close the tab page.
Stay inside the VC Modeling Environment.
Task 2: New Characteristic

Inside your VC modeling environment, you create a new characteristic.
1. Create a new characteristic.

Select the class 300/T_FCL## with the right mouse button.
Select the entry Create Characteristic.
The pop-up Open Class becomes visible. Continue.
Enter:
Characteristic: T_FCLD##
Now enter:
Description: Mast height ##
Characteristic Group: T-##
Status: Released
Data Type: Character Format
Number of Characters: 1
Value Assignment: Single Value
Assign the following values:
Characteristic Value: Description:

1 small = 2m
2 middle= 4m
3 large = 8m

Task 3: Selection Condition for PRTs
1. You are in the VC modeling environment. Or open the VC modeling environment again.
Enter:
Material: T-FCL##
Change No: no entry
Class Type: 300
Plant: 1010
On the left hand side, open routing and operation 0600. Three PRTs are displayed.
2. Create the right selection conditions, which select the right PRTs on operation 600,
depending the value assignment of characteristic T_FCLD##.
RESULT should be as follows:
PRTs Name: Description: Syntax

T_FV_002 T_SEL_FCLD##_EQ_1 Sel Cond. 2m T_FCLD## = '1'
height ##
height ##
height ##
3. First PRT:
Select PRT 010 with the right mouse and select the entry:
Create Dependency → Global
A pop-up appears. Continue
A pop-up appears. "Configuration for T-FCL## ...”
Enter:
Dependency: T_SEL_FCLD##_EQ_1
Description Sel. Cond. 2m height
Processing Mode Classic
Dependency Type: Selection Condition
Group: T-##
Switch to Editor and enter the following:

T_FCLD## = '1'
Check the syntax.
Open Basic Data and set the status to Released.
Save.
4. Second PRT:
A pop-up appears. Continue.
Enter:
Group: T-##

T_FCLD## = '2'
Check the syntax.
Save.
5. Third PRT:
A pop-up appears. Configuration for T-FCL## ...”
Enter:
Group: T-##


T_FCLD## = '3'
Check the syntax.
Save.
Task 4: Test your Result
1. Choose the Test button. The Simulate Configuration Models screen opens.
Select the routing on the left hand side.
Double click operation 0600.
2. Toggle Inspector is open.

No PRTs are visible for operation 0600.
3. Assign the value Middle 4m for the characteristic Mast Height ##.
Check the PRT information inside the inspector.
Preferred values are visible.
Small and large are excluded.
Middle is selected.
4. Close the simulation screen.

Unit 6
Solution 9
Routing: Object Dependencies
Simulation: Routing: Object Dependencies

For more information on Routing: Object Dependencies, please view the
online course.
Business scenario
The configuration modeling is also relevant to the routing of the forklift. In order to select the
required operation(s) and PRTs, selection conditions, similar to those for the BOM, are
needed. You now must either write new rules or use valid existing rules to select these
objects.
Task 1: Selection Conditions for Operations

Stay inside VC Modeling environment.
1. You created the following routing for your forklift:

Operation Work Center Description
100 T-E00 Allocation components

200 T-F00 Assy Drive -> chassis
300 T-G00 Chassis under carriage
400 T-H00 Driver's carb assy
500 T-K00 Assy Hydraulics with lift
600 T-M00 Assy lift with chassis
— — with PRTS
700 T-L00 Varnishing
800 T-P00 Assy road equipment
810 T-P00 Assy rear view camera
820 T-P00 Add lights
900 T-Z00 Final inspec + road test
— — with PRTS
Check which selection conditions are relevant for the following scenario:
Operations 800, 810 and 820 are only selected depending on the assignment of extras
characteristic T_FCLX##.

Which new selection conditions are required?

a) Which new selection conditions are required?
No new selection conditions are required. We created global dependencies which can
also be assigned to the routing. This was done in the prior exercise.
2. If necessary, open your modeling environment again. Assign the selection conditions to
your routing operations.
Optional: Execute again the app VC Modeling Environment.
Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
Operation 800:
Save your data.

Operation 810:
Save your data.

Operation 820:
Save your data.

a) Execute again the app VC Modeling Environment.

SAP Fiori Launchpad → Group Variant Configuration Modeling → VC- Modeling

Environment
Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter.
b) Operation 800:
Save your data.
c) Operation 810:
Save your data.
d) Operation 820:
Save your data.
3. Test your dependencies.

On the left hand side, change the view from Exploded BOM to Routing.
At the moment, no characteristic value assignment took place. So operation 800, 810, and
820 are not displayed.
Select for the accessories a value of your choice.
Refresh the displayed routing.
The relevant operation is visible.

Repeat now with the other characteristic assignments.

Leave the simulation open.
a) Select the Test button and go in simulation.
On the left hand side, change from exploded BOM to Routing. (Button in row with
Forklift …)
At the moment, no characteristic value assignment took place. So operation 800, 810,
and 820 are not displayed.
b) Select the following assignment:

Characteristic: Extras ##
Value: A- Road Equipment
Refresh your routing tree.

Operation 800 is visible.
c) Repeat now with other characteristic assignments.
d) Leave the simulation open.
4. Check the PRT assignments on operation 600.

At the moment no assignment is visible.
Open the Toggle Inspector on the right hand side.
Double click on operation 0600. The details open.
Basic information is displayed. Check the other icons. PRTs are displayed.
Close the tab page.
Stay inside the VC Modeling Environment.
a) Open the Toggle Inspector on the right hand side.
b) Double click on operation 0600. The details open.
c) Basic information is displayed. Check the other icons. PRTs are displayed.
d) Close the tab page.
e) Stay inside the VC Modeling Environment.
Task 2: New Characteristic

Inside your VC modeling environment, you create a new characteristic.
1. Create a new characteristic.

Select the class 300/T_FCL## with the right mouse button.
Select the entry Create Characteristic.
The pop-up Open Class becomes visible. Continue.
Enter:
Characteristic: T_FCLD##
Now enter:

Status: Released
Assign the following values:

1 small = 2m
2 middle= 4m
3 large = 8m
a) Create a new characteristic.

Select the class 300/T_FCL## with the right mouse button. Select the entry Create
Characteristic.
b) The pop-up Open Class becomes visible. Continue.
c) Characteristic: T_FCLD##
d) Now enter:
Status: Released
e) With the values:

1 small = 2m
2 middle= 4m
3 large = 8m
f) Save

Task 3: Selection Condition for PRTs
1. You are in the VC modeling environment. Or open the VC modeling environment again.
Enter:
Material: T-FCL##
Change No: no entry
Class Type: 300
Plant: 1010
On the left hand side, open routing and operation 0600. Three PRTs are displayed.
a) Open the VC modeling environment again. Enter
Material: T-FCL##
Change No: no entry
Class Type: 300
Plant: 1010
b) On the left hand side, open routing and operation 0600. Three PRTs are displayed.
2. Create the right selection conditions, which select the right PRTs on operation 600,
depending the value assignment of characteristic T_FCLD##.
RESULT should be as follows:
PRTs Name: Description: Syntax

height ##
height ##
height ##
3. First PRT:
Enter:

Group: T-##

T_FCLD## = '1'
Check the syntax.
Save.
a) Select PRT 010 with the right mouse and select the entry:
b) "Configuration for T-FCL## ”

Enter:
Group: T-##
c) Switch to Editor .
T_FCLD## = '1'
Check the syntax.
Save.
4. Second PRT:

Enter:
Group: T-##

T_FCLD## = '2'
Check the syntax.
Save.
b) "Configuration for T-FCL## ...”

Enter:
Group: T-##
T_FCLD## = '2'
Check the syntax.
Save.
5. Third PRT:

A pop-up appears. Configuration for T-FCL## ...”

Enter:
Group: T-##

T_FCLD## = '3'
Check the syntax.
Save.
b) Configuration for T-FCL## ...”

Enter:
Group: T-##
T_FCLD## = '3'
Check the syntax.
Save.
Task 4: Test your Result
1. Choose the Test button. The Simulate Configuration Models screen opens.
Select the routing on the left hand side.

Double click operation 0600.

a) Switch the view from Exploded BOM to Routing.
2. Toggle Inspector is open.

No PRTs are visible for operation 0600.
a) Toggle inspector is right-hand sided.
3. Assign the value Middle 4m for the characteristic Mast Height ##.
Check the PRT information inside the inspector.
Preferred values are visible.
Small and large are excluded.
Middle is selected.
a) Select a value for your characteristic.
Characteristic: Mast height ##
Value: Middle 4m
b) Check the Inspector for operation 0600.

Select the second button.
Selected value: Middle 4m
4. Close the simulation screen.

LESSON SUMMARY

Unit 6
Lesson 2
Class Nodes
LESSON OVERVIEW
Business Scenario
You have to control the interactive and dynamic selection of BOM components and routing
operations.
LESSON OBJECTIVES
Class Nodes
Figure 144: Class Nodes in a BOM
You can enter a class as a BOM item instead of a material. First, you must create the class in
the classification menu and assign objects to it. Since only documents or materials can be
included as BOM components, only classes with this object type are permitted.
The class must have a class type that allows it to be used in BOMs. You define this setting in
Customizing for the classification system. In the standard system, material class type 200
and document class type 201 can be used in BOMs.

Lesson: Class Nodes
Animation: Class Nodes in a BOM

For more information on Class Nodes in a BOM, please view the animation in the
lesson Class Nodes in your online course.
The class can be replaced by the values assigned to the:

● Configurable material
● Class node using procedures for the BOM item
● Class node using constraints for the configuration profile
Alternatively, you can start the Find Objects function for the class and select a material.
The procedure depends on whether manual changes to the BOM are allowed.
The class can be replaced by a classified material component by assigning values to the class
node. If no values are assigned to the class node, the values assigned to the header material
are used. The system searches the BOM structure from the bottom up, according to the
values assigned to the characteristics of the class nodes.


Unit 6
Exercise 10
Maintain Class Nodes
Simulation: Maintain Class Nodes

For more information on Maintain Class Nodes, please view the simulation in the
Business Scenario
Class nodes can be replaced according to features actually selected by the customer. This is
the case for the color and engine of our forklift.
Task 1: Engine Class-Node

Inside your material BOM, you added the class node T_FC_ENGINE.
1. In order to replace the class node in the BOM with a classified component, we must add
the characteristics of the class node T_FC_ENGINE to our variant class T_FCL##.
Open VC Modeling Environment again.
Material: T-FCL##
Date: Today’s Date
Class type: 300
Plant: 1010
Enter Model.
Open the tree on the left hand side. Double click the class.
The Characteristics tab page becomes visible.
Switch to change mode. Use the pencil.
Add the following characteristics:
Characteristics:
T_FC000 Type of Drive
T_FC001 Engine Performance
Save your class changes.

2. Test your changes. Use the relevant button inside the header information.
First, switch the view on the left hand side to Super BOM. The class node is visible.
Now test several assignments. Change your characteristics in the described way and
check the results inside Super BOM.
Note:
Don’t forget to refresh your Super BOM every time.
● There are no entries for Type of Drive and engine performance:
● Type of Drive set to Diesel and Engine Performance set to 55KW.
● Only Type of Drive set to Diesel.
Open the inspector on the right hand side.

Double click on Class Node Engine left hand side and you can see the component in
Inspector .
The details are visible inside inspector.
3. Open the material BOM tree and select the item 0040 K 200 T_FC_Engine with the right
mouse button.
For the knowledge base and the runtime version, you have to add the characteristics value
assignment to the class node inside material BOM item.
Create a procedure and make the following definition: System reads the assignment of the
header material and links the values to the class node.
Choose Create Dependency → Global (Reusable)
A pop-up Open Bill of Material appears. Click on Continue.
Create Dependency on BOM Item appears. Enter the following:
Dependency: T_PROC_ENGINE_##
Choose a Dependency Type: Radio button: Procedure
In Basic Data, enter the following:

Description: Class with direct values
Group: T-##
Radio button: Procedure
Switch to Editor and enter:
$self.T_FC000 = $root.T_FC000 ,
$self.T_FC001 = $root.T_FC001 .
Check and save your syntax.

Open the Basic Data screen.
Switch the Status to Released. If necessary, change to Edit mode.

Lesson: Class Nodes
Save your procedure.
Task 2: Class Node Color
1. Using the second class node (T_FC_Color), you would like to define a separate
characteristic - you won't use an existing characteristic and move it to your variant class.
Inside your navigation tree select the class 300 T_FCL## with the right mouse. Choose
Create Characteristic.
A pop-up appears: Open Class. Continue.
Enter the following characteristic:
Characteristic: T_FCLC##
Now enter the following:

Description: Color ##
Status: Released
Data Type Character
Value Assignment Single Value
Open Values. Enter the following:
0 without
R red
B blue
G green
Y Yellow
W white
S black
2. Now this value assignment has to be connected to the right characteristic of your class
node. This will be done with a procedure.
Open your material BOM. Select you class on item 0020 K 200 T_FC_COLOR with the
right mouse button:
A pop-up appears: Open Bill of Material. Continue.

Dependency: T_PROC_COLOR_##
Dependency Type: Procedure
Continue.
Description: Color value: Header to Item
Group: T-##
Open Editor and enter the following syntax:

$self.T_FC021 = $root.T_FCLC## .
Check your syntax.

Open again Basic Data and set the status to Released.
Save your data.
3. Test your scenario.

Switch Exploded BOM to Super BOM.
Now test several value assignments for your new characteristic Color ##.
● Without (0)
● Red (R)
Note:
Don’t forget to refresh your Super BOM.
Open the inspector again. Click on the component Class Node Color for details.
Close the simulation.

Unit 6
Solution 10
Maintain Class Nodes
Simulation: Maintain Class Nodes

For more information on Maintain Class Nodes, please view the simulation in the
Business Scenario
Class nodes can be replaced according to features actually selected by the customer. This is
the case for the color and engine of our forklift.
Task 1: Engine Class-Node

Inside your material BOM, you added the class node T_FC_ENGINE.
1. In order to replace the class node in the BOM with a classified component, we must add
the characteristics of the class node T_FC_ENGINE to our variant class T_FCL##.
Open VC Modeling Environment again.
Material: T-FCL##
Class type: 300
Plant: 1010
Enter Model.
Open the tree on the left hand side. Double click the class.
The Characteristics tab page becomes visible.
Switch to change mode. Use the pencil.
Add the following characteristics:
Characteristics:
Save your class changes.

a) Open VC Modeling Environment.

Material: T-FCL##
Class type: 300
Plant: 1010
b) Open the navigation tree.
c) Double click on class T_FCL##. The Detail screen opens.
d) Select the entry Characteristics. Switch to change mode.
e) Add the following characteristics:

Characteristics:
Save your class.
2. Test your changes. Use the relevant button inside the header information.
First, switch the view on the left hand side to Super BOM. The class node is visible.
Now test several assignments. Change your characteristics in the described way and
check the results inside Super BOM.
Note:
Don’t forget to refresh your Super BOM every time.
● There are no entries for Type of Drive and engine performance:
● Type of Drive set to Diesel and Engine Performance set to 55KW.
● Only Type of Drive set to Diesel.
Open the inspector on the right hand side.

Inspector .
The details are visible inside inspector.
a) Choose Test.
Switch the view Exploded BOM to Super BOM. Test several value assignments:
No entries for “Type of Drive” ==> nothing happens. Class node grayed out.
and “engine performance”.

Lesson: Class Nodes
Type of Drive set to Diesel ==> Engine T-FV1A93

Engine Performance set to
55KW
Note:
If necessary refresh your evalua-
tion tree.
Only ==> Engine T-FV1A91

Type of Drive set to Diesel
Open additional information to your component. Open the inspector.

Inspector .
b) Does every combination of values lead to an material BOM entry?

Try Type of Drive: Gas with Engine Performance: 55KW.
The class is still there.
c) The following combinations result in a material number, which replaces the class node:
Diesel no 18 kW, no 25 kW Motor
Gas no 18 kW, no 55 kW Motor
Electric no 45 kW, no 55 kW Motor
d) Only close the simulation screen.
3. Open the material BOM tree and select the item 0040 K 200 T_FC_Engine with the right
mouse button.
For the knowledge base and the runtime version, you have to add the characteristics value
assignment to the class node inside material BOM item.
Create a procedure and make the following definition: System reads the assignment of the
header material and links the values to the class node.
Create Dependency on BOM Item appears. Enter the following:

Description: Class with direct values
Group: T-##
Switch to Editor and enter:

Check and save your syntax.

Open the Basic Data screen.
Switch the Status to Released. If necessary, change to Edit mode.
a) Open the material BOM tree and select the item 0040 K 200 T_FC_Engine with the
right mouse button.
b) Create Dependency on BOM Item appears. Enter the following:

c) In Basic Data, enter the following:

Description: Class with direct values:
Group: T-##
d) Switch to Editor and enter the following syntax:

e) Check your syntax.
f) Open the Basic Data screen. Switch the Status to Released. If necessary, change to
Edit mode.
g) Save your procedure.
Task 2: Class Node Color
1. Using the second class node (T_FC_Color), you would like to define a separate
characteristic - you won't use an existing characteristic and move it to your variant class.
Inside your navigation tree select the class 300 T_FCL## with the right mouse. Choose
Create Characteristic.
A pop-up appears: Open Class. Continue.
Enter the following characteristic:
Now enter the following:

Lesson: Class Nodes
Status: Released
Data Type Character
Open Values. Enter the following:
0 without
R red
B blue
G green
Y Yellow
W white
S black

a) In VC Modeling Environment , open the tree and use the right mouse button on class
300 T_FCL##.
Choose Create Characteristic.
b) A pop-up appears: Open Class. Continue.
c) Enter the following characteristic:

d) Now enter the following on the Basic Data screen:

Status: Released
Data Type Character
e) Open Values. Enter the following:

0 without
R red
B blue
G green
Y Yellow
W white
S black
f) Save your characteristic.
2. Now this value assignment has to be connected to the right characteristic of your class
node. This will be done with a procedure.
Open your material BOM. Select you class on item 0020 K 200 T_FC_COLOR with the
right mouse button:
Continue.
Group: T-##
Open Editor and enter the following syntax:

Check your syntax.

Open again Basic Data and set the status to Released.
Save your data.
a) Open your material BOM.
Select your class on item 0020 K 200 T_FC_COLOR with the right mouse button:
b) Enter the following:


Lesson: Class Nodes
c) In Basic Data, enter the following:

Group: T-##
d) Open Editor and enter the following syntax:

Check your syntax.
e) Open Basic Data again and set the status to Released.
f) Save your data.

Switch Exploded BOM to Super BOM.
Now test several value assignments for your new characteristic Color ##.
● Without (0)
● Red (R)
Note:
Don’t forget to refresh your Super BOM.
Open the inspector again. Click on the component Class Node Color for details.
a) Test (button) your scenario.
b) Change from Exploded BOM to Super BOM.
c) Do a value assignment for characteristic Color ##.

Select, for example, the value Red.
Class node is replaced by T-FV5E01.
Don’t forget to refresh.
d) Close the simulation.

LESSON SUMMARY

Unit 6
Lesson 3
Procedures with Reference Characteristics
(Quantity and Time Change)
LESSON OVERVIEW
Business Scenario
You have controlled the selection of BOM components and routing operations using selection
conditions. Now you have to make changes to these elements of the exploded BOM or
routing. For example, you would like to change quantities, dimensions, and planned times.
LESSON OBJECTIVES
Procedures in Material BOMs (Change Quantities with Reference Characteristics)
Figure 147: Use of Reference Characteristics

Animation: Use of Reference Characteristics

For more information on Use of Reference Characteristics, please view the
animation in the lesson Procedures with Reference Characteristics (Quantity and
Time Change) in your online course.
You can use reference characteristics in procedures to change the values in master data
fields. In reference characteristics, you define a reference to the appropriate table and field
name.
These are examples of creating two reference characteristics: TSTPO_MENGE, which refers
to field MENGE in the BOM table STPO and another reference characteristic,
T_PLPO_VGW03, which is created with a reference to table PLPO and field VGW03.
Figure 149: Procedure for a BOM Item
Animation: Procedure for a BOM Item

For more information on Procedure for a BOM Item, please view the animation in
the lesson Procedures with Reference Characteristics (Quantity and Time
Change) in your online course.
For this procedure, you need to use the reference characteristic T_STPO_MENGE which
refers to field STPO-MENGE.
You refer to this reference characteristic in a procedure. You assign the value you want the
characteristic to have if value Length, Width and Height is assigned to the characteristic
Counterweight.
You assign this procedure to the BOM item whose quantity you want to change. As soon as
the BOM item is selected, the procedure is processed, providing that any conditions attached
to it are fulfilled.

Lesson: Procedures with Reference Characteristics (Quantity and Time Change)
Characteristics that are to be assigned a value in a dependency must be preceded with $SELF
to show that values are assigned at this level. In the example above, characteristic
T_STPO_MENGE must be prefixed with object variable $SELF to make it clear that the
characteristic refers to the current object – the BOM item.
You can check the effect of this procedure by simulating the BOM explosion (for example, in
the configuration simulation function).
Procedure for an Operation in a Task List (With Reference Characteristic Change

Times)
Figure 151: Procedure for an Operation in a Task List
Animation: Procedure for an Operation in a Task List

For more information on Procedure for an Operation in a Task List, please view
the animation in the lesson Procedures with Reference Characteristics (Quantity
and Time Change) in your online course.
You can also use object dependencies to change field values in task list tables for the routing.
For example, you can change a standard value for an operation.
To do this, you create a reference characteristic that refers to one of the fields for standard
values (VGW01–06) in table PLPO.
In a previous example, reference characteristic T_PLPO_VGW03 was defined for this purpose.
In this procedure, the value of reference characteristic T_PLPO_VGW03 is set to 30 minutes
more if the customer chooses a mast height large.
You assign this procedure to the operation. As soon as the operation is selected, the
procedure is processed, provided that any conditions attached to it are fulfilled.
You can check the effect of the procedure by simulating the task list explosion.


Unit 6
Exercise 11
Change the Component Quantity (Reference
Characteristics)
Simulation: Change the Component Quantity (Reference Characteristics)

For more information on Change the Component Quantity (Reference
Characteristics), please view the simulation in the lesson Procedures with
Reference Characteristics (Quantity and Time Change) in your online course.
Business Scenario
With selection conditions, you defined which Material BOM components or routing operations
are selected or not.
Now, it could be necessary to change these objects you selected inside material BOM and
routing. Therefore, you may access database fields and modify their values based on certain
conditions.
Inside the first task, you change the mass of your counterweight depending on length, width,
and height, based on your configuration.
Inside your second task, you increase the labor time of the relevant operation on 30min, if the
mast height is large.
Task 1: Material BOM item: Procedure

Create the necessary reference characteristic for your material BOM item and enter the
dependency, ensuring that the counterweight is calculated depending on weight, height, and
length.
1. Open the app VC Modeling Environment again, with the following data:
Material: T-FCL##
Change No.: no entry
Class Type: 300
Plant: 1010
Check the footer area. There you find the entry Environment.
2. Create a reference characteristic.

Navigate as follows:
→ Environment → Characteristics.

Select the right mouse button and the entry Create Characteristic.
The pop-up Create Characteristic appears. Enter the following:
Characteristic: T_STPO_MENGE_##
Check Box: Create Reference Characteristic
The system opens the view Additional Data. Enter the following:
Table: STPO
Field: MENGE
Press the enter button on your keyboard. Information becomes visible.

Open Basic Data. The data was changed.
Save your characteristic. Stay inside the app.
3. Copy characteristics T_FCLR00 to your characteristic T_FCLR##.
Note:
For the sake of simplicity, open a second tab page and start the relevant app.
Open the app Manage Characteristics. It can be found inside group Classification.
Characteristic: T_FCLR##
Don’t enter the data. Choose the button Create with Template.
Enter Template: T_FCLR00.
Accept all template indicators in the area Template: Choose Block.
Change the description to: Counterbalance Length ## and change the characteristic
group to T-##.
4. Copy characteristics T_FCLS00 to T_FCLS##.

Open the app Manage Characteristics. It can be found inside the group Classification.
Characteristic: T_FCLS##
Enter Template: T_FCLS00.
Change the description to: Counterbalance Width ## and change the characteristic group
to T-##

5. Copy characteristic T_FCLT00 to your characteristics. T_FCLT##.

Characteristic: T_FCLT##
Enter Template: T_FCLT00.
Change the description to: Counterbalance Height ## and change the characteristic group
to T-##.
Close the app.
6. Connect T_FCLR##, T_FCLS##, T_FCLT## to class 300 T_FCL##.

Open the app VC Modeling Environment and enter the following:
Material: T-FCL##
Class Type: 300
Plant: 1010
Double click your class 300 T_FCL## and open the Characteristics view. Switch to Change
mode.
Add the following Characteristics:
T_FCLR##
T_FCLS##
T_FCLT##
Save your assignment.
7. Create a procedure T_PROC_T_STPO_MENGE_## for item 0010– Counterweight inside

material BOM.
This procedure calculates the quantity depending on Length x Width x Height x 7.2g.
Do the following:
Create a global dependency for item 0010 T-FV3C00 . Select the right mouse button and
create a global dependency.
Enter Dependency: T_PROC_T_STPO_MENGE_## .
Don’t forget the radio button Procedure.
On the Basic Data screen, enter the following:

Description: Quantity overwritten w. weight
Group T-##
Open Editor and enter the following:
$self.t_stpo_menge_## =
t_fclr## *
t_fcls## *
t_fclt## *
7.2 / 1000000
8. Test your procedure.

Set the following values:
Counterbalance Length: 800
Counterbalance Width: 700
Counterbalance Height: 600
Refresh the Exploded BOM. As a result, the quantity of your counterweight T-FV3C00
changes to 2.419,2 kg.
9. Close the screen and open the VC Modeling Environment again.
Task 2: Routing Operation: Procedure
1. Create a Reference Characteristic T_PLPO_VGW02_## inside VC Modeling Environment.

Open the area Environment and create a new characteristic.
The relevant box opens. Enter the following:
Characteristic: T_PLPO_VGW02_##
Continue.
Inside the tab page Additional Data, enter the following:
Table: PLPO
Field: VGW02
Enter the data.

Information is displayed.
Open Basic Data and add group T-##. Add your group number to the description.
Save your data and stay inside application.

2. Now create and add the procedure T_PROC_PLPO_VGW02_PLUS30_## to operation

0600. Define the relevant dependencies that increases the machine time plus 30 min, if
the mast height is set to large.
Select your routing and click with the right mouse button on operation 0600. Select
Create Dependency → Global.
Continue on Open Operation Entity.
On Configuration for T-FCL##, enter the following:
Dependency: T_PROC_PLPO_VGW02_PLUS30_##
Radio button for Dependency Type Procedure
Description: Increase machine time + 30min

Group: T-##
$self.t_plpo_vgw02_## =
mdata
$self.t_plpo_vgw02_##
+ 30
if t_fcld## = '3'
Check your syntax.

Save your data.
3. Test your object dependency..

Change the tree from Exploded BOM to Routing.
Check the operation 0600. Click the operation and check the inspector. The machine time
is set to 30 min.
Now set the mast height to Large = 8m.
Refresh the routing. Click the operation 0600. Check the inspector. The machine time is
increased to 60 min.
Close the screen.

Unit 6
Solution 11
Change the Component Quantity (Reference
Characteristics)
Simulation: Change the Component Quantity (Reference Characteristics)

For more information on Change the Component Quantity (Reference
Characteristics), please view the simulation in the lesson Procedures with
Reference Characteristics (Quantity and Time Change) in your online course.
Business Scenario
With selection conditions, you defined which Material BOM components or routing operations
are selected or not.
Now, it could be necessary to change these objects you selected inside material BOM and
routing. Therefore, you may access database fields and modify their values based on certain
conditions.
Inside the first task, you change the mass of your counterweight depending on length, width,
and height, based on your configuration.
Inside your second task, you increase the labor time of the relevant operation on 30min, if the
mast height is large.
Task 1: Material BOM item: Procedure

Create the necessary reference characteristic for your material BOM item and enter the
dependency, ensuring that the counterweight is calculated depending on weight, height, and
length.
1. Open the app VC Modeling Environment again, with the following data:
Material: T-FCL##
Class Type: 300
Plant: 1010
Check the footer area. There you find the entry Environment.
a) Open the app VC Modeling Environment and enter the following:
Material: T-FCL##


Class Type: 300
Plant: 1010
b) Check the footer area. There you find the entry Environment.
2. Create a reference characteristic.

Navigate as follows:
The system opens the view Additional Data. Enter the following:
Table: STPO
Field: MENGE

Open Basic Data. The data was changed.
Save your characteristic. Stay inside the app.
a) Navigate as follows:
b) The system opens the view Additional Data. Enter the following:
Table: STPO
Field: MENGE

Open Basic Data. The data was changed. Add the characteristic group T-##

c) Save your characteristic. Stay inside the app.
3. Copy characteristics T_FCLR00 to your characteristic T_FCLR##.
Note:
For the sake of simplicity, open a second tab page and start the relevant app.
Characteristic: T_FCLR##
Enter Template: T_FCLR00.
Accept all template indicators in the area Template: Choose Block.
Change the description to: Counterbalance Length ## and change the characteristic
group to T-##.
a) Open the app Manage Characteristics. It can be found inside the group Classification.
b) Enter the Characteristic T_FCLR##, and choose the button Create with Template.
Enter Template : T_FCLR00.
c) Change the description to: Counterbalance Length ## and change the characteristic
group to T-##.
d) Save your characteristic.
4. Copy characteristics T_FCLS00 to T_FCLS##.

Characteristic: T_FCLS##
Enter Template: T_FCLS00.
Change the description to: Counterbalance Width ## and change the characteristic group
to T-##
a) Open the app Manage Characteristics. It can be found inside the group Classification.
b) Enter: Characteristic: T_FCLS## and choose the button: Create with Template. Enter
Template : T_FCLS00.
c) Change the description to: Counterbalance Width ## and change the characteristic
group to T-##.

5. Copy characteristic T_FCLT00 to your characteristics. T_FCLT##.

Characteristic: T_FCLT##
Enter Template: T_FCLT00.
Change the description to: Counterbalance Height ## and change the characteristic group
to T-##.
Close the app.
a) Open the app Manage Characteristics. It can be found inside group Classification.
b) Enter: Characteristic: T_FCLT## and choose the button Create with Template. Enter
Template: T_FCLT00.
c) Change the description to Counterbalance Heigth ## and change the characteristic

group to T-##.
e) Close the app.
6. Connect T_FCLR##, T_FCLS##, T_FCLT## to class 300 T_FCL##.

Material: T-FCL##
Class Type: 300
Plant: 1010
Double click your class 300 T_FCL## and open the Characteristics view. Switch to Change
mode.
Add the following Characteristics:
T_FCLR##
T_FCLS##
T_FCLT##

Material: T-FCL##


Class Type: 300
Plant: 1010
b) Double click to class 300 T_FCL## and open the Characteristics view. Switch to
Change mode.
c) Add the following Characteristics:

T_FCLR##
T_FCLS##
T_FCLT##
7. Create a procedure T_PROC_T_STPO_MENGE_## for item 0010– Counterweight inside

material BOM.
This procedure calculates the quantity depending on Length x Width x Height x 7.2g.
Do the following:
Create a global dependency for item 0010 T-FV3C00 . Select the right mouse button and
create a global dependency.
Enter Dependency: T_PROC_T_STPO_MENGE_## .
Group T-##
t_fclr## *
t_fcls## *
t_fclt## *
7.2 / 1000000
a) Create the procedure and assign it.

Select the material BOM and click with the right mouse button on the item 0010 T-
FV3C00 .
Choose → Create Dependency → Global (Reusable).

Continue on to the screen Open Bill of Material.

Inside the pop-up, enter the following:
Dependency: T_PROC_T_STPO_MENGE_##
b) On the Basic Data screen, enter the following:

Group T-##

t_fclr## *
t_fcls## *
t_fclt## *
7.2 / 1000000
Check your syntax.

Save your dependency.

Set the following values:
Refresh the Exploded BOM. As a result, the quantity of your counterweight T-FV3C00
changes to 2.419,2 kg.
a) Choose Test.
b) Define the following characteristic values:

c) Check the result inside the Exploded BOM. Counterweight is recalculated to 2.419,2
kg.
9. Close the screen and open the VC Modeling Environment again.

Task 2: Routing Operation: Procedure
1. Create a Reference Characteristic T_PLPO_VGW02_## inside VC Modeling Environment.

Open the area Environment and create a new characteristic.
The relevant box opens. Enter the following:
Continue.
Table: PLPO
Field: VGW02
Enter the data.

Save your data and stay inside application.
a) Open the area Environment and create a new characteristic.
→ Environment → Characteristics , select the right mouse button and choose Create
Characteristic.
Table: PLPO
Field: VGW02
Enter the data.

b) Save your data.
c) Stay inside the application.
2. Now create and add the procedure T_PROC_PLPO_VGW02_PLUS30_## to operation

0600. Define the relevant dependencies that increases the machine time plus 30 min, if
the mast height is set to large.
Select your routing and click with the right mouse button on operation 0600. Select

Continue on Open Operation Entity.

On Configuration for T-FCL##, enter the following:
Description: Increase machine time + 30min

Group: T-##
mdata
+ 30
if t_fcld## = '3'
Check your syntax.

Save your data.
a) Select your routing and click with the right mouse button on operation 0600. Select
b) Continue on Open Operation Entity.
c) On Configuration for T-FCL##, enter the following:

d) On the Basic Data screen, enter the following:

Description: Increase machine time + 30 min
Group: T-##
e) Open Editor and enter the following:

mdata
+ 30
if t_fcld## = '3'
Check your syntax.
f) Open Basic Data and the status to Released.
g) Save your data.
3. Test your object dependency..

Change the tree from Exploded BOM to Routing.
Check the operation 0600. Click the operation and check the inspector. The machine time
is set to 30 min.
Now set the mast height to Large = 8m.
Refresh the routing. Click the operation 0600. Check the inspector. The machine time is
Close the screen.
a) Use Test—Button.
b) Change the tree from exploded BOM to routing.
c) Check the operation 0600. Click the operation and check the inspector. Machine time
is set to 30 min.
d) Set the mast height to Large = 8m.
e) Refresh the routing. Click the operation 0600. Check the inspector. Machine time is
f) Close the screen.

LESSON SUMMARY


Unit 6
Learning Assessment
1. The syntax elements $self, $parent and $root can be used in selection conditions. The
characteristics of which of these configuration instances can be addressed and used in
selection conditions in the BOM and task list?
X A $self
X B $parent
X C $root
2. What techniques can be used to ensure that a class node is replaced by a material (or
document)?
X A By the values assigned to the configurable material.
X B By the values assigned to the class node using procedures for the BOM item.
X C By the values assigned to the class node using precondition for the BOM item.
X D By the values assigned to the class node using selection condition for the BOM
item.
X E By the values assigned to the class node using constraints for the configuration
profile.
X F You can start the Find Objects function for the class and select a material
(document).

3. You can use procedures and reference characteristics to change fields in the exploded
BOM and task list. The fields of which tables can be used in this way?
X A STKO
X B STPO
X C PLKO
X D PLPO
X E PLFL
X F PLFH

UNIT 7 Dependencies for the Value
Assignment Interface - 1
Lesson 1
Interface Design, Characteristic Grouping and PMEVC 252
Exercise 12: Table Constraint Using a Wizard 257
Lesson 2
Constraints: An Introduction 263
Lesson 3
Constraints: First Details 268
Exercise 13: Constraint: A Simple Example 277
Exercise 14: Optional: Constraint in a Multilevel Configuration with Additional Modeling 283
Steps
UNIT OBJECTIVES
● Define an interface design / a characteristic group and work with PMEVC

● Work again with the product modeling environment
● Explain the benefits of constraints
● Define your own constraints
● Edit formulas and tables

Unit 7
Lesson 1
Interface Design, Characteristic Grouping and
PMEVC
LESSON OVERVIEW
Business Scenario
Ensure that the configuration is complete and consistent.
LESSON OBJECTIVES
Interface Design
Figure 154: Interface Design (1)
You can define 15 buttons and 10 tab pages maximum.

Lesson: Interface Design, Characteristic Grouping and PMEVC
Figure 155: Interface Design (2)
Interface Design for LO-VC

Authorization object C_LOVC_DSG
Using the User Interface, you are able to add a push button as characteristic grouping. If the
name of the characteristics group starts with CUSTOMER_PUSHBUTTON_ , the system
works with an User-Exit (- a user specific function in customer exit CEI00000).
Only Materials
Sequence: in sales (customer order and configuration simulation) or for engineering (order
BOM and configuration simulation). If you do not set an indicator, the sequence is valid for
both.
Print relevance in sales (order confirmation, delivery, billing) or purchasing (order). This
function is integrated into the print function for sales and purchasing. If no characteristic
group is maintained for the item to be printed, all characteristics with a value assigned are
printed (including the hidden ones). If there is a characteristic group for the print output, then
only the characteristics with values that are assigned to the group are printed in the sequence
defined.
Interface Design / Characteristic Groups for AVC
Under AVC, the above surface design for LO-VC cannot be used. But even here
characteristics can be grouped on tab pages. To do this, assign the following to the
configuration profile Characteristic Groups. These characteristic groups must be created
beforehand.
A characteristic group consists of:
● A sorted list of characteristics and
● Labels for the tab page

Unit 7: Dependencies for the Value Assignment Interface - 1
Figure 156: Interface Design / Characteristic Groups for AVC
Animation: Interface Design / Characteristic Groups for AVC

For more information on Interface Design / Characteristic Groups for AVC,
please view the animation in the lesson Interface Design, Characteristic Grouping
and PMEVC in your online course.
Product Modeling Environment - PMEVC
Figure 158: Product Modeling Environment

The Product Modeling Environment PMEVC is a different transaction, all previous

transactions are still valid.
You can create and change the most of master data of a variant configuration model.
Some of maintenance transactions in PMEVC are better and more elegant as in previous
transactions.
PMEVC Maintenance
The following restrictions exist:
● Master data such as material master, BOM, routings or classes cannot be created.
● These master data cannot be changed in principle (that is with Exceptions for Assigning
Object Dependencies and Overwriting Characteristics).
● The PMEVC can only be used for configurable material masters and not for other
configurable object types.
PMEVC: Restricted Characteristics And Table Constraint Wizard
Figure 159: PMEVC: Restricted Characteristics And Table Constraint Wizard
Outside the PMEVC, the configurable material and the variant class (possibly empty) have to
be created.
From the context menu of the variant class (left in the navigation tree) you can create
characteristics from the assignment. Here we need single valued restrictable characteristics.
Subsequently, you can use the table constraint wizard to create tables. This includes the
following steps in detail:
1. Open the context menu of your configuration profile. An overview screen becomes visible
and you continue.

2. In the area Mode of Action you select restricted values.
3. Configuration object (= Constraint: Objects-Part) is a variant class.
4. For the new variant table you select the relevant characteristics, name the table and add a
description.
5. Then you can add a long text as an explanation for the variant table or accept the system
suggestion.
6. Add the constraint name or accept the suggestion.
7. All steps are done.
8. At last you create the variant table content.
When you assign the content for the variant table, you are able to add single or multiple
values. If you define multiple values, at least you have to use the button normalize . Then every
value is displayed separately.

Unit 7
Exercise 12
Table Constraint Using a Wizard
Create a Table Constraint Using a Wizard
Simulation: Table Constraint Using a Wizard

For more information on Table Constraint Using a Wizard, please view the
simulation in the lesson Interface Design, Characteristic Grouping and PMEVC in
your online course.
You realize that only for some combinations of Type of Drive and Engine Performance material
components exist. Therefore, you have to define a table constraint that defines possible
combinations.
In addition, you have to define a constraint that restricts the characteristics. To speed up, you
use a table constraint wizard.
1. Open the app VC Modeling Environment with the following data:

Material: T-FCL##
Class Type: 300
Plant: 1010
2. Open your navigation tree inside the VC Modeling Environment app.

The first entry below the material is the configuration profile. Here you would like to define
the table constraint.
Open the context menu of profile T-FCL## with the right mouse button and select Create
Table Constraint Using Wizard. Choose Continue.
1. Mode of Action: Value Restriction.

2. Configuration Object: Set the radio button for class 300 T_FCL##.
3. New Variant Table: Set the checkbox for both Characteristics T_FC000 and
T_FC0001. Name the variant table: TAB1_## with the description: Allowed combination
part 1.
4. Explanation: Leave it as it is. Continue.
5. Constraint Name: Change the Table Constraint to T_CS_Tab1_## and the
description to CS Allowed combination part 1.
6. Complete: Check the result screen and choose Complete.
Continue with the pop-up Open Configuration Profile .

3. The Variant Table Contents view opens.

Click 3 times on the + button. Three rows are added.
For the first Characteristic T_FC000, select the F4 help in the first row. Select the value E-
Electric.
Note:
For the value assignment of T_FC0001, working with F4 help doesn’t get the
right result, as you can only select one value. Therefore, double click in the
T_FC0001 field. A pop-up for multi-value assignment opens. Select 18, 25,30.
T_FC000 T_FC0001
E 18,25,30
Now do the same for T_FC000 Gas and Diesel. Add the following:
T_FC000 T_FC001
G 25, 30, 45
D 30, 45, 55
Normalize your table. Select the second last button inside the table area.
Now every value has an own row.
Switch to Basic Data. Add group T-##.
Save your data.
4. Check the Processing mode of your Constraint Net KJP_TWT-FCL##01. This is Advanced
Variant Configuration.
Inside the navigation tree, double click on Constraint net KJP_TWT-FCL##01
Basic Data opens. Change to the Change mode and set the following:
5. Test your changes.

Set the Type of Drive to Electric.
Engine Performance is reduced to 18, 25, or 30KW.
Close the simulation screen.

Unit 7
Solution 12
Table Constraint Using a Wizard
Create a Table Constraint Using a Wizard
Simulation: Table Constraint Using a Wizard

For more information on Table Constraint Using a Wizard, please view the
simulation in the lesson Interface Design, Characteristic Grouping and PMEVC in
your online course.
You realize that only for some combinations of Type of Drive and Engine Performance material
components exist. Therefore, you have to define a table constraint that defines possible
combinations.
In addition, you have to define a constraint that restricts the characteristics. To speed up, you
use a table constraint wizard.
1. Open the app VC Modeling Environment with the following data:

Material: T-FCL##
Class Type: 300
Plant: 1010

Material: T-FCL##
Class Type: 300
Plant: 1010
2. Open your navigation tree inside the VC Modeling Environment app.

The first entry below the material is the configuration profile. Here you would like to define
the table constraint.
Open the context menu of profile T-FCL## with the right mouse button and select Create
Table Constraint Using Wizard. Choose Continue.

1. Mode of Action: Value Restriction.

2. Configuration Object: Set the radio button for class 300 T_FCL##.
3. New Variant Table: Set the checkbox for both Characteristics T_FC000 and
T_FC0001. Name the variant table: TAB1_## with the description: Allowed combination
part 1.
4. Explanation: Leave it as it is. Continue.
5. Constraint Name: Change the Table Constraint to T_CS_Tab1_## and the
description to CS Allowed combination part 1.
6. Complete: Check the result screen and choose Complete.
Continue with the pop-up Open Configuration Profile .

a) Open your navigation tree inside the VC Modeling Environment app.
b) The second entry below the material is the configuration profile. Here you would like to
define the table constraint. Open the context menu of profile T-FCL## with the right
mouse button and select Create Table Constraint Using Wizard. Choose Continue.
c) The Table Constraint Wizard is opened. Click Continue
d) Mode of Action: Value Restriction.
e) Configuration Object: Set the radio button for class 300 T_FCL##.
f) New Variant Table: Set the checkbox for both Characteristics T_FC000 and
T_FC0001. Name the variant table: TAB1_## with the description: Allowed
combination part 1.
g) Explanation: Leave it as it is.
h) Constraint Name: Set the Table Constraint to T_CS_Tab1_## and the description to
CS Allowed combination part 1.
i) Complete: Check the result screen and click on Complete.
j) Continue with the pop-up Open Configuration Profile .
3. The Variant Table Contents view opens.

Click 3 times on the + button. Three rows are added.
For the first Characteristic T_FC000, select the F4 help in the first row. Select the value E-
Electric.
Note:
For the value assignment of T_FC0001, working with F4 help doesn’t get the
right result, as you can only select one value. Therefore, double click in the
T_FC0001 field. A pop-up for multi-value assignment opens. Select 18, 25,30.
T_FC000 T_FC0001
E 18,25,30
Now do the same for T_FC000 Gas and Diesel. Add the following:
T_FC000 T_FC001
G 25, 30, 45

D 30, 45, 55
Normalize your table. Select the second last button inside the table area.
Now every value has an own row.
Switch to Basic Data. Add group T-##.
Save your data.
a) The Variant Table Content View is open. Click 3 times on the + button. Three rows are
added.
b) For the first Characteristic T_FC000, select the F4 help.

For the value assignment of T_FC0001, working with F4 help doesn’t get the right
result, as you can only select one value. Therefore, double click in the T_FC0001 field.
A pop-up for multi-value assignment opens. Select 18,25,30.
T_FC000 T_FC0001
E 18,25,30
c) Now the same for T_FC000 Gas and Diesel. Add the following:
T_FC000 T_FC001
G 25, 30, 45
D 30, 45, 55
d) Normalize your table. Select the second last button inside the table area. Now every
value has an own row.
Pop up about "Normalization can not be reverted": has to be confirmed.
e) Switch to Basic Data. Add group T-##.
f) Save your data.
4. Check the Processing mode of your Constraint Net KJP_TWT-FCL##01. This is Advanced
Variant Configuration.
Inside the navigation tree, double click on Constraint net KJP_TWT-FCL##01
Basic Data opens. Change to the Change mode and set the following:
a) Inside the navigation tree, double click on Constraint net KJP_TWT-FCL##01 .
Basic Data opens. Check:
Processing mode: Advanced Variant Configuration
5. Test your changes.

Set the Type of Drive to Electric.
Engine Performance is reduced to 18, 25, or 30KW.
Close the simulation screen.
a) Perform this step of exercise.

LESSON SUMMARY

Unit 7
Lesson 2
Constraints: An Introduction
LESSON OVERVIEW
Business Scenario
Your company also has configurable products that consist of multiple configurable
assemblies. A more complex approach is required to perform a multi-level configuration. In
addition, the considerably more extensive functionality and syntax of constraints should be
used
LESSON OBJECTIVES
Constraint: An Introduction
Figure 161: Constraints
This dependency type is mainly for intensively interactive configuration tasks and for
configuration tasks in which you need to take into account the dependencies between the
characteristics of several objects. The main purpose of constraints is to check and to ensure
the consistency of a configuration.
Constraints have the following distinguishing features:
● You can use constraints to describe the dependencies between completely different
objects and their characteristics.
● Constraints are used to store information on conditions that must be fulfilled if the
configuration is to be consistent.
● Constraints are not directly assigned to individual objects. They are grouped together to
form dependency nets and assigned to a configurable material via configuration profile.

In constraints specify objects in their general form - alongside the use of $SELF, $ROOT oder
$PARENT. As a rule, you refer to objects in constraints by entering the class to which the
objects are assigned.
Constraints are declarative dependencies. The processing sequence of constraints and the
point in time when constraints are processed are not relevant.
Constraints are not processed in a specific order. You cannot determine when a specific
constraint is used.
In any processing situation, a constraint is only processed once. However, if a value that is
relevant to the constraint is changed, the constraint is triggered again.
Figure 162: Complex Multilevel Configuration
Figure 163: Creating a Constraint

Lesson: Constraints: An Introduction
Animation: Creating a Constraint

For more information on Creating a Constraint, please view the animation in the
lesson Constraints: An Introduction in your online course.
Constraints can only be created locally within a dependency net.

Dependency nets group constraints together and contain central control parameters.
To create a constraint:
1. Create a dependency net. You create dependency nets under a separate menu option
(transactions CU21 or PMEVC) in the variant configuration menu. You only create the
basic data in the dependency net, and release the net once it is ready. If you want to
include further constraints in a dependency net, choose Change dependency net.
2. To create individual constraints, choose Assignments in the dependency net. Like other
simple dependencies, a constraint comprises basic data and source code.
3. Assign the dependency net to the configuration profile. You cannot assign a dependency
net to other object types.
Constraints can only be processed in a configuration if the dependency net and constraints
are released.
Figure 165: Dependency Net for the Header Material

Figure 166: Structure of a Constraint
Animation: Structure of a Constraint

For more information on Structure of a Constraint, please view the animation in
the lesson Constraints: An Introduction in your online course.
There are four sections in a constraint. Each section is identified by a keyword. The keyword is
followed by a colon. Each section can be closed with a point.
OBJECTS:
The objects of the constraint are specified in this part, as long as they are not the $self, $part,
or $root instance. All other objects that are addressed in the constraint must be specified
here. You can also specify variables for objects or characteristics. If only the three instances
$self-, $parent, and $root are required and no variables are to be defined, the objects part can
be omitted.
CONDITION:
The condition entered here must be fulfilled in order for the constraint to be processed. You
do not need to enter a condition in a constraint. You can leave out the condition section.
However, if you enter the keyword CONDITION, you must enter a condition.
RESTRICTIONS:
In this section, you enter the interdependencies that must exist between the objects and
characteristics if the configuration is to be consistent. You must enter a restriction in a
constraint.
INFERENCES:
In this part, you specify for LO-VC the characteristics whose values are to be displayed using
additional functions. Should be derived or restricted. The Inferences part is optional. You need
for LO-VC if the evaluation of the constraint is performed using the functions of procedures

Lesson: Constraints: An Introduction
goes out. Under AVC, an inferences part is not required - the additional Functionality is always
active.
LESSON SUMMARY

Unit 7
Lesson 3
Constraints: First Details
LESSON OVERVIEW
Business Scenario
Your company also has configurable products that consist of multiple configurable
assemblies. A more complex approach is required to perform a multi-level configuration. You
work with constraints to make a value derivation and consistency check for an object as well
as between different objects. In addition, the considerably more extensive functionality and
syntax of constraints should be used
LESSON OBJECTIVES
Constraints: OBJECTS-Part
Figure 168: OBJECTS – Section

Lesson: Constraints: First Details
Animation: OBJECTS – Section

For more information on OBJECTS – Section, please view the animation in the
lesson Constraints: First Details in your online course.
The OBJECTS part is optional. It can be omitted if only the three instances $self, $parent, and
$root are to be addressed and no variables are required
Class and Class type
The usual way to declare an object in a constraint is by entering the class and class type. If
you want to use a constraint to refer to a fork lift classified in class Forklift of class type 300,
you enter the fork lift as follows: (300) fork lift.
Object Key
If you want to refer to a specific material, you enter the identifier for the object type, the class
type, and the object key. Mat in this example is the object identifier for materials. You define
the object identifier for referring to objects in dependencies by choosing Maintain Object
Types in Customizing for Classification.
The object key for materials is the material number. The object key is also specified in
Customizing for Classification.
In the step Maintain object keys, you define which fields are used to specify an object. You also
enter the field name of the key field. The material number key field is referred to by formal
parameter NR. An object key can consist of several partial keys, as is the case for documents:
(Document)(017)(TYPE = 'DRW', VERSION = '00', PART = '000', NR = 'D4545')
For the class type, enter the class type of the class to which the object is assigned. If the
object is not assigned to a class, do not enter a class type. However, you must enter empty
parentheses as a place holder.
(Material)()(NR = 'MAT-A')

Constraints: Variables
Figure 170: Variables for Objects, Classes, and Characteristics
Animation: Variables for Objects, Classes, and Characteristics

For more information on Variables for Objects, Classes, and Characteristics,
please view the animation in the lesson Constraints: First Details in your online
course.
Defining Variables
If you use a class to refer to an object, you use the expression IS_A to define a variable: X IS_A
(300) T_FC00.
If you refer to an object using the object key, and do not enter a class, you use the expression
IS_OBJECT to define a variable: Y IS_OBJECT (Material)(300)(NR=T-FC00).
Variables for the $self, $part, and $root instances are defined using the keyword AS: Z AS
$SELF
If you use the object key to refer to an object, you must define a variable. If you use a class or
an instance to refer to an object, defining a variable is optional.
You can enter a ? to make your variables easier to identify: ?X IS_A (300) T_FC00.
The variables referred to in a constraint must already be known when you create a constraint.
Constraint-Example without variables
OBJECTS: (300)T_FC498 ,
(300)T_FC598 .
CONDITION: (300)T_FC598.T_FC004 specified .
RESTRICTION: (300)T_FC598.t_FC003 = (300)T_FC498.t_FC022 .

Constraint-Example with variables

OOBJECTS: ?carr is_a (300)T_FC498 ,
?cab is_a (300)T_FC598 .
CONDITION: ?cab.T_FC004 specified .
RESTRICTION: ?cab.t_FC003 = ?carr.t_FC022.
Constraint-Example with characteristic variables

OBJECTS: (300)T_FC498 where wheels = T_FC022 ,
(300)T_FC598 where seat = T_FC003 ;
back = T_FC004 .
CONDITION: specified back .
RESTRICTION: seat = wheels.
Figure 172: Constraints with and Without Local Variables
Advantages of variables:
● Self-explanatory names
● Easier to maintain subsequent sections of constraint
● Less code
It is entirely up to you whether you use variables or not.

Variables are an option for supporting modeling.
Characteristic variables can be used in conjunction with object variables and class variables.
RESTRICTIONS – Section

Figure 173: RESTRICTIONS – Section
In the RESTRICTIONS section of a constraint, you enter the consistency checks that the
constraint is to make. The constraint returns an inconsistency if the RESTRICTIONS section is
not true. You cannot enter non-declarative expressions.
You can also use the statement FALSE as a restriction. This means that situations described
in the condition section are inconsistent. If this situation occurs, an inconsistency message is
returned.
In the RESTRICTIONS section of a constraint, you can also call tables that you defined
previously. This makes a constraint a powerful tool, since you can replace a large number of
preconditions by using a table call in a constraint.
You can also use tables to restrict the allowed range of values. For example, you can use a
table call to define the value combinations for the mass height and drive type. If you refer to a
table in a constraint, only the value combinations defined in the table are valid. Under LO-VC,
you must use restrictable characteristics and the INFERENCES part for this.

Constraints: Examples for RESTRICTION part
Figure 174: Examples of a Restrictions Section
The constraint returns an inconsistency if the RESTRICTIONS section is not true. The
RESTRICTIONS section can also infer a value for the printer software, in the first example, and
for the two characteristics of the class node in the second example.
Constraints can hide values of a restrictable characteristic that are not allowed. To do this,
under LO-VC, the constraint must contain restrictable characteristics and an inferences part.
Under AVC, this always happens.
CONDITION part
In the CONDITION section, you specify when the constraint is processed. A constraint is only
processed if the condition section is true. The syntax of a condition is similar to the syntax of a
precondition or selection condition. However, the following differences apply:
TYPE_OF is not allowed in constraints.
You can use variables for objects, classes, and characteristics.
You can use logical expressions of any complexity, including nested disjunctions and
conjunctions (AND, OR and parentheses).
In addition, you can use the expressions PART_OF and SUBPART_OF. PART_OF checks
whether a material or document is in the BOM of another material or document.
SUBPART_OF checks the same thing across multiple levels of the BOM.
In the condition section and in IF conditions in the restrictions section, statements such as the
following are false if the characteristic has no value assigned: =.
The functioning of such statements is the same as in preconditions and selection conditions.

Figure 175: Example of a Condition Section
Constraints with (LO-VC) and without (AVC) Inferences
Figure 176: INFERENCES Section
Animation: INFERENCES Section

For more information on INFERENCES Section, please view the animation in the
lesson Constraints: First Details in your online course.
The inferences section can only contain characteristic variables.

If you use a table call or a function call, the relevant access keys must be defined there (value
assignment alternative of a table or function).
If you use arithmetical expressions, it must be possible to interpret a variable.
Constraints with Formula and with (LO-VC) and without (AVC) Inferences
Figure 178: Constraints with Formula and Inferences
Animation: Constraints with Formula and Inferences

For more information on Constraints with Formula and Inferences, please view
the animation in the lesson Constraints: First Details in your online course.
The configurator automatically converts the equations in such a way that, if sufficient input is
made, the following values are displayed of values the remaining can be calculated. Possible
entries to calculate all further sizes would have to be calculated:
● 2 sizes from length, width, area, circumference, and aspect ratio
● 1 Size from height and volume
Variant tables or variant functions with value assignment alternative works in the same way.
For variant functions, the programmer is responsible for ensuring that the inverse equation is
there and is called.


Unit 7
Exercise 13
Constraint: A Simple Example
Simulation: Constraint: A Simple Example

For more information on Constraint: A Simple Example, please view the
simulation in the lesson Constraints: First Details in your online course.
Business Scenario
In this exercise, you create a simple constraint.
Within a single level configuration, a required value assignment has to be defined with a
constraint.
An Example
If you select an engine with a performance of 55KW, the tonnage of your forklift is
automatically set to 5000 kg.
1. Check your constraint net. In a former exercise you created a constraint net, connected to
your configuration profile. Check your data.
Open the next level of your configuration profile. Check the description. A standard
constraint net is visible.
Open the next level of your constraint net. The constraint T_CS_TAB1_## becomes
visible.
2. Copy characteristic T_FCLF99 to your characteristic T_FCLF##.

Characteristic: T_FCLF##
Enter Template: T_FCLF99.
Change the description to Tonnage Capacity ## and char. group to T-##.
3. Connect T_FCLF## to class 300 T_FCL##.

Material: T-FCL##

Class Type: 300

Plant: 1010
Double click your class 300 T_FCL## and open the view Characteristics. Switch to Change
mode.
Add the characteristic T_FCLF##.
4. Use your constraint net and create a new constraint T_CS_FCL##.

Select again, with the right mouse button, the context menu of your constraint net. Select
the entry Create Constraint.
Use the following data:
Constraint: T_CS_FCL##
Description: 55KW Engine w. tonnage 5000kg
Group: T-##
Processing Mode: A =Advanced VC (grayed out)
Switch to editor and enter the following:
OBJECTS: (300)T_FCL##
RESTRICTIONS: (300)T_FCL##.T_FCLF## = 5000

if (300)T_FCL##.T_FC001 = 55.
or even simpler and shorter:
RESTRICTIONS: $self.T_FCLF## = 5000

if $self.T_FC001 = 55.

Save your constraint.
5. Test your constraint.

Set the Engine Performance to 55 KW.
What happens with the characteristic Tonnage Capacity and Type of Drive?
Now add other values. Set the mast height to small. Tonnage capacity is set to 5000 kg.
Set the fork length to large. What happens to tonnage capacity? It is grayed out.
6. Close your simulation screen.

Unit 7
Solution 13
Constraint: A Simple Example
Simulation: Constraint: A Simple Example

For more information on Constraint: A Simple Example, please view the
simulation in the lesson Constraints: First Details in your online course.
Business Scenario
In this exercise, you create a simple constraint.
Within a single level configuration, a required value assignment has to be defined with a
constraint.
An Example
If you select an engine with a performance of 55KW, the tonnage of your forklift is
automatically set to 5000 kg.
1. Check your constraint net. In a former exercise you created a constraint net, connected to
your configuration profile. Check your data.
visible.
a) Check your constraint net.
visible.
2. Copy characteristic T_FCLF99 to your characteristic T_FCLF##.

Characteristic: T_FCLF##
Enter Template: T_FCLF99.
Change the description to Tonnage Capacity ## and char. group to T-##.

b) Enter Characteristic: T_FCLF## and choose the button Create with Template. Enter
Template: T_FCLF99.
c) Change the description to Tonnage Capacity ## and char. group to T-##.
3. Connect T_FCLF## to class 300 T_FCL##.

Material: T-FCL##
Class Type: 300
Plant: 1010
mode.
Add the characteristic T_FCLF##.
Material: T-FCL##
Class Type: 300
Plant: 1010
b) Double click the class 300 T_FCL## and open the view Characteristics. Switch to
Change mode.
c) Add the characteristic T_FCLF##.

4. Use your constraint net and create a new constraint T_CS_FCL##.

Select again, with the right mouse button, the context menu of your constraint net. Select
the entry Create Constraint.
Use the following data:
Constraint: T_CS_FCL##
Group: T-##

Processing Mode: A =Advanced VC (grayed out)
Switch to editor and enter the following:

if (300)T_FCL##.T_FC001 = 55.
or even simpler and shorter:


a) Select again, with the right mouse button, the context menu of your constraint net.
Select the entry Create Constraint.
b) Enter the constraint name: T_CS_FCL##.
c) Basic Data:
Group: T-##
Processing Mode: A =Advanced VC
d) Editor:

if (300)T_FCL##.T_FC001 = 55.
or :

Check your syntax.
e) Switch back to Basic Data and set the status to Released.
f) Save your constraint.
5. Test your constraint.

Set the Engine Performance to 55 KW.

Now add other values. Set the mast height to small. Tonnage capacity is set to 5000 kg.
Set the fork length to large. What happens to tonnage capacity? It is grayed out.
a) Set the Engine Performance to 55 KW.
Tonnage is set to 5000 kg and Type of Drive to Diesel.
b) Now add other values. Set the mast height to small. Tonnage capacity is set to 5000
kg.
6. Close your simulation screen.

Unit 7
Exercise 14
Optional: Constraint in a Multilevel
Configuration with Additional Modeling Steps
Simulation: Optional: Constraint in a Multilevel Configuration with Additional

Modeling Steps
For more information on Optional: Constraint in a Multilevel Configuration with
Additional Modeling Steps, please view the simulation in the lesson Constraints:
First Details in your online course.
Business Scenario
The configurable forklift is to be assigned another configurable component. A multi-level
configuration should be possible. A constraint is used to compare the evaluation of the header
configuration and the component configuration.
This means:
— Create a new material T-FC7XX## (with a template)

— Assign the new material to material BOM T-FCL## / 1010 / 1
— Create a new variant class (300) T_FC7XX##.
— Assign Characteristics to the new variant class
— Assign a new second configuration profile to the material T-FCL##
— Create a new configuration profile for component T-FC7XX##
— Add a new constraint net and create a new constraint, which synchronizes the
evaluation of the header configuration and the component configuration
Task 1: Create Material
1. Create a material.
Enter:
Material: T-FC7XX##
Template material: T-FC7XX
● Basic Data 1+ 2
● MRP 1+ 2+ 3 + 4

● Work Scheduling
● Accounting 1+ 2
● Costing 1+ 2
Note:
Set the check box: Create views selected.
Note:
Enter values also for Copy from.
Enter in both cases plant 1010.

Change or enter the following in Basic Data 1+2:
● Description Lift T-F7XX## configurable
Save your Material.
Task 2: Change your Material BOM
1. Add a component in your material BOM.

Open the app Change Material BOM. It can be found inside the group Product Engineering.
Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
Add a component of item 0050.

Component new: T-FC7XX## 1 PC
Save your material BOM.
Task 3: Create a New Class

Create class T_FC7XX## with class type 300.
1. Open the app Manage Classes.

Enter:
Class: T_FC7XX##
Class type: 300

Enter the following description: Class T_FC7XX##. Set the Class group to T-##.
Save your class.
Task 4: Work with Variant Class and Configuration Profile
1. Copy characteristic T_FCLE99, to your characteristic T_FCLE##.

Enter:
Characteristic: T_FCLE##
Enter Template: T_FCLE99.
Change the description to Fork length ## and char. group to T-##.
2. Open VC Modeling Environment for T-FCL##.

Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
3. Select component T-FC7XX## and assign variant class (300)T_FC7XX##.

Finally assign the following characteristics to your class.
T_FCLD## = Mast Height
T_FCLE## = Fork Length
T_FCLF## = Tonnage Capacity
Select the material BOM inside your object tree. Select the material T-FC7XX## with the
right mouse button. Don’t select the component item entry.
Select Assign Class with class T_FC7XX## and class type 300.
Double click the class and change to edit mode.
Assign the characteristics T_FCLD##, T_FCLE## and T_FCLF##.
Save your class.
4. Add to your header material T-FCL## a second configuration profile: T-FCL##-MV

Use the same settings as your defined for profile T-FCL##. Inside Basic Data change:
BOM Explosion: Multilevel with Application PP01.

Processing Mode: Advanced VC

Add the dependencies of your old profile to the new one.
Lock the first profile.
5. Add a configuration profile T-FC7XX## to your material T-FC7XX##. Work with the same
settings as inside your prior exercise.
Select the entry Create Configuration Profile.
Name it as follows:
Configuration Profile T-FC7XX##
In Basic Data, select:

Process: Plan. / Production Order
BOM Explosion: Multilevel with Application PP01
Save it.
Task 5: Create a Constraint Net and Constraint

A constraint is used to compare the evaluation of the header configuration and the
component configuration.
1. Create a constraint net T_CN_FCL7XX## for the configuration profile T-FC7XX## on

material T-FC7XX##.
Select the right navigation path and create a global dependency for your configuration
profile.
Inside the relevant pop-up, enter the following:
Dependency: T_CN_FCL7XX##
Radio Button: Constraint Net
Description: CSN for T-FCL7XX##
Processing Mode: A Advanced VC
Status: Released
Group: T-##
Save your constraint net.
2. Create a constraint T_CS_FCL##_FC7## inside your net. This constraint is used to

compare the evaluation of the header configuration T-FCL## and the component
configuration T-FC7XX##.

Select your constraint net T_CN_FCL7XX## inside your object tree. Inside the context
menu, select Create Constraint.
Name the constraint as follows:
Constraint: T_CS_FCL##_FC7##
In Basic Data, enter:
Description: Evaluate header component
Processing Mode A Advanced VC
Status: in Preparation
Group: T-##
Select the area Editor. Enter:
OBJECTS: ?HEAD is_a (300)T_FCL## ,

?COMP is_a (300)T_FC7XX##.
Restriction:
?HEAD.T_FCLD## = ?COMP.T_FCLD## ,
?HEAD.T_FCLE## = ?COMP.T_FCLE## ,
?HEAD.T_FCLF## = ?COMP.T_FCLF## .
Test your syntax.

Change the status to Released.

Be aware of the following: The tree control on the left hand side is switched to Configurable
items.
Set the following values in the named sequence:
● T_FCLE## Fork Length : Long
● T_FCLD## Mast height: Large
● T_FCLF## Tonnage: 1600kg
In the Configurable items area, double click on T-FC7XX##. Now value changes are
allowed.
Delete the value assignment on the header area.
Now do the value assignment on item level T-FC7XX##. Do it with the same values.
As a result, the header characteristics can’t be changed.
4. Inside your VC Modeling Environment screen, do the following:

● Change the configuration profile status of T-FCL##-MV to Locked, which is assigned to

header material T-FCL##.
● Change the configuration profile status of T-FCL## to Released, which is assigned to

Save your changes.
1. Change your material BOM T-FCL## 1010 1. Delete Component T-FC7XX## = item 0050.
Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
Delete component of item 0050.

Component: T-FC7XX##

Unit 7
Solution 14
Optional: Constraint in a Multilevel
Configuration with Additional Modeling Steps
Simulation: Optional: Constraint in a Multilevel Configuration with Additional

Modeling Steps
For more information on Optional: Constraint in a Multilevel Configuration with
Additional Modeling Steps, please view the simulation in the lesson Constraints:
First Details in your online course.
Business Scenario
The configurable forklift is to be assigned another configurable component. A multi-level
configuration should be possible. A constraint is used to compare the evaluation of the header
configuration and the component configuration.
This means:
— Create a new material T-FC7XX## (with a template)

— Assign the new material to material BOM T-FCL## / 1010 / 1
— Create a new variant class (300) T_FC7XX##.
— Assign Characteristics to the new variant class
— Assign a new second configuration profile to the material T-FCL##
— Create a new configuration profile for component T-FC7XX##
— Add a new constraint net and create a new constraint, which synchronizes the
evaluation of the header configuration and the component configuration
Task 1: Create Material
1. Create a material.
Enter:
Material: T-FC7XX##
Template material: T-FC7XX
● Basic Data 1+ 2
● MRP 1+ 2+ 3 + 4

● Work Scheduling
● Accounting 1+ 2
● Costing 1+ 2
Note:
Note:
Enter in both cases plant 1010.

Save your Material.

SAP Fiori Launchpad → group Product Master → Tile Create Material
Or, MM01.
Or, SAP GUI → SAP-Menu → Logistics → Production → Master Data → Material
Material: T-FC7XX##
Material Type: Semi finished Product
Template Material: T-FC7XX
Enter your data:

● Basic Data 1+ 2
● MRP 1+ 2+ 3 + 4
● Work Scheduling
● Accounting 1+ 2
● Costing 1+ 2

Note:
Note:
● Plant 1010
● Copy from Plant 1010
Save your Material.
1. Add a component in your material BOM.

Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
Add a component of item 0050.

Component new: T-FC7XX## 1 PC

a) Open the app Change Material BOM. It can be found inside the group Product
Engineering.
Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
b) Add component T-FC7XX## inside item 0050. Add quantity and unit: 1 PC
c) Save your material BOM.
Task 3: Create a New Class

Create class T_FC7XX## with class type 300.

1. Open the app Manage Classes.

Enter:
Class: T_FC7XX##
Class type: 300

Enter the following description: Class T_FC7XX##. Set the Class group to T-##.
Save your class.
a) Create a new class. Execute the app Manage Classes.
b) Enter the following key:

Class: T_FC7XX##
Class Type: 300
Inside Basic Data, enter the following:

Description: T_FC7XX##
Class group: T-##
c) Save your data.
Task 4: Work with Variant Class and Configuration Profile
1. Copy characteristic T_FCLE99, to your characteristic T_FCLE##.

Enter:
b) Enter Characteristic: T_FCLE## and choose the button Create with Template. Enter
Template: T_FCLE99.
c) Change the description to Fork Length ## and char. group to T-##.
2. Open VC Modeling Environment for T-FCL##.

Enter:
Material: T-FCL##

Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
a) Open:
Environment
Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter.
3. Select component T-FC7XX## and assign variant class (300)T_FC7XX##.

Finally assign the following characteristics to your class.
T_FCLD## = Mast Height
T_FCLE## = Fork Length
T_FCLF## = Tonnage Capacity
Select Assign Class with class T_FC7XX## and class type 300.
Double click the class and change to edit mode.
Assign the characteristics T_FCLD##, T_FCLE## and T_FCLF##.
Save your class.
a) Open material BOM tree. Open item 0050. Perform a right mouse click on material T-
FC7XX##.
Select the entry Assign Class.
Enter:
Class: T_FC7XX##

Classtype: 300
b) Assign Characteristics.
Double click on class 300 T_FC7XX##.
The detail screen opens. Select the tab page Characteristics and switch to Change
mode. Enter:
T_FCLD##
T_FCLE##
T_FCLF##
Save your data.
4. Add to your header material T-FCL## a second configuration profile: T-FCL##-MV

Use the same settings as your defined for profile T-FCL##. Inside Basic Data change:
BOM Explosion: Multilevel with Application PP01.
Add the dependencies of your old profile to the new one.
Lock the first profile.
a) Select the context menu of material T-FCL##.
Select the entry: Create Configuration Profile
Enter:
Configuration Profile: T-FCL##-MV
Basic Data:
Processing Mode: : A- Advanced VC

BOM Explosion: Multilevel with PP01
Status: Released
b) Add the dependencies of your old profile to the new one.

Do the following:
Open the source configuration profile, highlight a line inside the dependencies area,
and work with Control C and Control V in your target profile.
c) Lock the first profile.

Change the configuration profile status to Locked.
5. Add a configuration profile T-FC7XX## to your material T-FC7XX##. Work with the same
settings as inside your prior exercise.
Select the entry Create Configuration Profile.

Name it as follows:
In Basic Data, select:

Save it.
a) Select the material BOM inside your object tree. Select the material T-FC7XX## with
the right mouse button. Don’t select the component item entry. Select the entry
Create Configuration Profile.
Select the following path: Material BOM → item 0050 T-FC7XX## → Material T-
FC7XX## → Create Configuration Profile.
b) Name it as follows:
c) In Basic Data, select:

d) Save it.
Task 5: Create a Constraint Net and Constraint

A constraint is used to compare the evaluation of the header configuration and the
component configuration.
1. Create a constraint net T_CN_FCL7XX## for the configuration profile T-FC7XX## on

material T-FC7XX##.
Select the right navigation path and create a global dependency for your configuration
profile.
Inside the relevant pop-up, enter the following:
Status: Released

Group: T-##
Save your constraint net.

a) Create a constraint net T_CN_FCL7XX##:
Select the following path: Material BOM → item 0050 T-FC7XX## → Material T-
FC7XX## → Configuration Profile → Create Dependency → Global.
Inside the relevant pop-up, enter:
b) On Basic Data:
Status: Released
Group: T-##
c) Save your constraint net.
2. Create a constraint T_CS_FCL##_FC7## inside your net. This constraint is used to

compare the evaluation of the header configuration T-FCL## and the component
configuration T-FC7XX##.
Name the constraint as follows:
In Basic Data, enter:
Processing Mode A Advanced VC
Group: T-##
Select the area Editor. Enter:

Restriction:

Test your syntax.

Change the status to Released.
a) Create a constraint for your constraint net.
Name the constraint as follows
b) In Basic Data, enter:

Processing Mode Advanced VC
Group: T-##
c) Select the area Editor. Enter:

Restriction:
d) Check your syntax.
e) Change the status to Released.
f) Save your constraint.

Be aware of the following: The tree control on the left hand side is switched to Configurable
items.
Set the following values in the named sequence:
● T_FCLF## Tonnage: 1600kg

allowed.
Delete the value assignment on the header area.
Now do the value assignment on item level T-FC7XX##. Do it with the same values.
a) Go to Test
b) Check / Change the tree control to Configurable items.
c) Set the following values in the named sequence:
● T_FCLF## Tonnage: 1600 kg
allowed.
In the Configurable items area, double click on T-FCL##. Delete the value assignment
here (on header area).
d) In the Configurable items area, double click on T-FC7XX##. Now do the value
assignment here (on item level T-FC7XX##). Do it with the same values.
e) Close the simulation screen.
4. Inside your VC Modeling Environment screen, do the following:
● Change the configuration profile status of T-FCL##-MV to Locked, which is assigned to

● Change the configuration profile status of T-FCL## to Released, which is assigned to

Save your changes.
1. Change your material BOM T-FCL## 1010 1. Delete Component T-FC7XX## = item 0050.
Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
Delete component of item 0050.

Component: T-FC7XX##

a) Open the app Change Material BOM. It can be found inside the group Product
Engineering.
Enter the key:
Material: T-FCL##
Plant: 1010
BOM usage: 1
b) Delete component T-FC7XX## = item 0050.
c) Save your material BOM.

LESSON SUMMARY

Unit 7
Learning Assessment
1. Interface design and characteristic groups allow you to design the interface. Where can
something be used?
X A Interface design under LO-VC (classic processing mode)
X B Interface design under AVC (advanced processing mode)
X C Characteristic groups under LO-VC (classic processing mode)
X D Characteristic groups under AVC (advanced processing mode)
2. A constraint can consist of up to 4 parts. Which of the 4 parts are mandatory?

X A OBJECTS
X B CONDITION
X C RESTRICTIONS
X D INFERENCES
3. There are differences between LO-VC and AVC with regard to constraints. Parts are no
longer required under AVC. Which parts are it about?
X A OBJECTS
X B CONDITION
X C RESTRICTIONS
X D INFERENCES


UNIT 8 Dependencies for the Value
Assignment Interface - 2
Lesson 1
Procedures for Value Assignment Interface 304
Exercise 15: Default Values with Procedures (With / Without Variant Tables) 311
Lesson 2
Facet Changes with Pre- and Selection Conditions 323
Exercise 16: Pre- and Selection Conditions for Characteristics and Values 329
UNIT OBJECTIVES
● Define and work with Procedures

● Define variant tables in simple dependencies to interfere values
● Use additional functionalities of procedures
● Pre- and selection conditions for value assignment interface
● Work with selection conditions for characteristics, declared to required characteristics

Unit 8
Lesson 1
Procedures for Value Assignment Interface
LESSON OVERVIEW
Business Scenario
Ensure that the configuration is complete and consistent. Therefore, you work with
procedures to set values using procedures.
LESSON OBJECTIVES
Procedures
Figure 182: Procedures

Lesson: Procedures for Value Assignment Interface
Animation: Procedures
For more information on Procedures , please view the animation in the lesson
Procedures for Value Assignment Interface in your online course.
You can assign procedures to the following objects:

● The characteristic value that triggers the procedure.
● The characteristic that triggers the procedure.
● The configuration profile of the configurable object. It is easier to manage procedures
assigned to the configuration profile, because they are all in one place.
● BOM items – to change the quantity, for example.
● Operations – to change the standard values, for example.
The processing sequence of procedures is defined at dependency assignment level.

Procedures can overwrite values set by other procedures. In contrast, if different values are
set for a single-value characteristic by constraints, or user entries, an inconsistency occurs.
None may overwrite the other - exception procedures among each other (and default values).
If two procedures set the value of a single-value characteristic, the last in the sequence wins
out. This means you need to ensure that the sequence of procedures is correct - otherwise
the wrong value could be set.
Procedures: Syntax
Figure 184: Syntax Elements (Procedures Only)
Procedures are always used for pricing (here also $SET_PRICING_FACTOR).

You can use the following elements in procedures only:

NOT SPECIFIED
NOT TYPE_OF
<multiple-value characteristic> NE <Value > (identical to NOT <Value> IN <multiple-value
characteristic>)
$COUNT_PARTS: You can calculate the sum of the number of BOM items.
$SUM_PARTS: You can calculate the sum of numeric characteristic values for individual
objects.
As well as using procedures to infer values, you can use procedures to:
Access values that were changed by a procedure, to change them again (Figure = Figure +1)
You can use procedures to set soft values that can be set by the user or by choosing
dependencies can be overwritten (?= or $SET_DEFAULT). You can also delete default values
set using procedures. ($DEL_DEFAULT).
Figure 185: Procedure for a Characteristic Value
Animation: Procedure for a Characteristic Value

For more information on Procedure for a Characteristic Value, please view the
animation in the lesson Procedures for Value Assignment Interface in your online
course.
This procedure can also be assigned to the configuration profile. To get the same effect, the
syntax would have to be as follows:
$self.FORK_LENGTH = ‘SHORT’
IF
$root.MAST_HEIGHT = ‘LARGE’

Procedure for the Configuration Profile
Figure 187: Procedure for the Configuration Profile
Procedures and Variant Tables
Figure 188: Structure of a Variant Table
Table maintenance:
1. Create table structure.

Define characteristics as columns.

No evaluation alternatives required for conditions (for example, preconditions).

An evaluation alternative is required for procedures.
Possible for constraints without, with one or more evaluation alternatives.
2. Define content.
Figure 189: Example of a Variant Table
Figure 190: Variant Tables and Procedures
You can assign a variant table to a procedure to calculate missing values in a configuration.
If the interdependencies between objects are more complex, you can assign variant tables to
a Constraint.
To use procedures with variant tables to infer values, you define value assignment
alternatives. A value assignment alternative describes which table fields are key fields and
which are data fields. The key fields determine the values in the data fields.
Characteristics that refer to data fields in the table must be preceded with the variable $SELF,
to ensure that values can be inferred for these characteristics.

Animation: Variant Tables and Procedures

For more information on Variant Tables and Procedures , please view the
animation in the lesson Procedures for Value Assignment Interface in your online
course.
Example: Variant Table with Key Fields
Figure 192: Example: Variant Table with Key Fields
Procedures and Default Values
Figure 193: Procedure for Setting a Default Value

Procedures with $set_default and $del_default
Figure 194: Procedure with $set_default and $del_default
Procedures and x = x+ 1
Figure 195: Procedures: Successive Calculation & Overwrite

Unit 8
Exercise 15
Default Values with Procedures (With /
Without Variant Tables)
Simulation: Default Values with Procedures (With / Without Variant Tables)

For more information on Default Values with Procedures (With / Without Variant
Tables), please view the simulation in the lesson Procedures for Value
Assignment Interface in your online course.
Business Scenario
You can set default values in characteristics maintenance. However, if you do not always want
the same default value – for example, if you want the default value to depend on the value
assigned to other characteristics – you can use procedures to define this.
Task 1: Create Characteristic and Assign to a Class
1. If you performed the second, optional exercise on constraints, this step is omitted
(T_FCLE## has already been created).
Copy characteristic T_FCLE99, to your characteristic T_FCLE##.
Enter:
2. Connect T_FCLF## (and T_FCLE##) to class 300 T_FCL##.

Material: T-FCL##
Class Type: 300
Plant: 1010

mode.
Add the characteristic: T_FCLF##.
If the characteristic was already created and assigned in the last exercise and not in the
last step, then also add T-FCLE##.
Task 2: Alternative 1: Default Values Defined with a Procedure

Depending on the evaluation of the mast height, a fork length should be proposed via
dependencies.
For a mast height set to large, a fork length small should be suggested.
For a mast height set to middle, a fork length middle should be suggested.
For a mast height set to small, a fork length small should be suggested.
1. Create a procedure T_PROC_SET_DEFAULT_T_FCLE_##, which fits the requirements.

Connect this procedure with the configuration profile of your material.
Open the app VC Modeling Environment. Enter known material T-FCL##, class type 300,
plant 1010, and BOM application PP01.
Inside the modeling environment, select your configuration profile T-FCL## with the right
mouse button and create a global dependency as a procedure. Name it the following:
Description: T_PROC_SET_DEFAULT_T_FCLE_##
Note:
Description: Default values for T_FCLE##

Group: T-##
Open the editor, and enter the following:

$self.T_FCLE## ?= '1' if $self.T_FCLD## = '3',
$self.T_FCLE## ?= '3' if $self.T_FCLD## = '1'
Check your syntax.



Set your Mast height to Middle.
What happens to your fork length?
Are you able to change the value of fork length?
Are you able to change the value of fork length to (None)?
Delete the value of mast height. Mast height and fork length are set to none.
Set know the fork length to middle.
What happens to mast height?
Task 3: Alternative 2: Default values for a procedure defined with a variant table
Note:
If you have completed “Alternative 1”, open the procedure and set the status to
3– Locked.
Depending on the evaluation of the mast height, a fork length should be proposed via variant
table and dependencies.
1. Create Variant table TAB2_##.

Open the app VC Modeling Environment. Enter the known material T-FCL##, class type
300, plant 1010 and BOM application PP01.
Open the area Environment, with the entry Variant table.
Create a Variant Table TAB2_##.
Set the following:

Status: Released
Group: T-##
Select the area Characteristics with the following:
Characteristics Key
T_FCLD## Check box
T_FCLE## nothing
Choose Contents. Add 3 rows. Enter:

T_FCLD## T_FCLE##
1 3

2 2
3 1
Save your table.
2. Create a procedure T_PROC_TAB_DEFAULT_T_FCLE_## which defines default values

using the table.
mouse button and create a global dependency as a procedure. Name it as follows:
Description: T_PROC_TAB_DEFAULT_T_FCLE_##
Note:

Group: T-##

table tab2_## ( T_FCLD## = T_FCLD## ,
T_FCLE## ?= $self.T_FCLE## )
Check your syntax.


Set your Mast height to middle.

Unit 8
Solution 15
Default Values with Procedures (With /
Without Variant Tables)
Simulation: Default Values with Procedures (With / Without Variant Tables)

For more information on Default Values with Procedures (With / Without Variant
Tables), please view the simulation in the lesson Procedures for Value
Assignment Interface in your online course.
Business Scenario
You can set default values in characteristics maintenance. However, if you do not always want
the same default value – for example, if you want the default value to depend on the value
assigned to other characteristics – you can use procedures to define this.
Task 1: Create Characteristic and Assign to a Class
1. If you performed the second, optional exercise on constraints, this step is omitted
(T_FCLE## has already been created).
Copy characteristic T_FCLE99, to your characteristic T_FCLE##.
Enter:
b) Enter Characteristic: T_FCLE## and choose the button Create with Template. Enter
Template: T_FCLE99.
c) Change the description to Fork Length ## and char. group to T-##.
2. Connect T_FCLF## (and T_FCLE##) to class 300 T_FCL##.

Material: T-FCL##


Class Type: 300
Plant: 1010
mode.
Add the characteristic: T_FCLF##.
If the characteristic was already created and assigned in the last exercise and not in the
last step, then also add T-FCLE##.
Material: T-FCL##
Class Type: 300
Plant: 1010
b) Double click the class 300 T_FCL## and open the view Characteristics. Switch to
Change mode.
c) Add the characteristic: T_FCLF##

Task 2: Alternative 1: Default Values Defined with a Procedure

Depending on the evaluation of the mast height, a fork length should be proposed via
dependencies.
1. Create a procedure T_PROC_SET_DEFAULT_T_FCLE_##, which fits the requirements.

Connect this procedure with the configuration profile of your material.
Open the app VC Modeling Environment. Enter known material T-FCL##, class type 300,
plant 1010, and BOM application PP01.
mouse button and create a global dependency as a procedure. Name it the following:
Description: T_PROC_SET_DEFAULT_T_FCLE_##

Note:

Group: T-##

Check your syntax.

a) Open the VC Modeling Environment.
Material: T-FCL##
Class Type: 300
Plant: 1010
b) Create a procedure.
Select your configuration profile T-FCL## with the right mouse button → Context
menu → Create Dependency → Global ...
On the first pop-up, choose continue.
Dependency T_PROC_SET_DEFAULT_T_FCLE_##
Description Default values for T_FCLE##

Group: T-##

Editor (Syntax:) $self.T_FCLE## ?= '1' if $self.T_FCLD## = '3',

Check your syntax.

Release your procedure.

a) Choose Test
b) What happens to your fork length?

Fork length is set to middle. It is a default value.
c) Are you able to change the value of fork length?

Yes, you are able to change the default value.
d) Are you able to change the value of fork length to (None)?

You can't delete the default value.
e) Delete the value of mast height. Mast height and fork length are set to none.
f) Set now the fork length to middle. What happens to mast height?
Nothing. No values assigned to mast height.
Task 3: Alternative 2: Default values for a procedure defined with a variant table
Note:
If you have completed “Alternative 1”, open the procedure and set the status to
3– Locked.
Depending on the evaluation of the mast height, a fork length should be proposed via variant
table and dependencies.
1. Create Variant table TAB2_##.

Open the app VC Modeling Environment. Enter the known material T-FCL##, class type
300, plant 1010 and BOM application PP01.
Open the area Environment, with the entry Variant table.
Create a Variant Table TAB2_##.
Set the following:

Status: Released
Group: T-##
Select the area Characteristics with the following:
Characteristics Key
T_FCLD## Check box
T_FCLE## nothing
Choose Contents. Add 3 rows. Enter:

T_FCLD## T_FCLE##
1 3
2 2
3 1
Save your table.

a) Open the VC Modeling Environment.
Material: T-FCL##
Class Type: 300
Plant: 1010
b) Select Environment and Variant Tables.Select the entry: Create Variant Table.
Variant Table TAB2_##
c) Select area Basic Data:, with the following values:

Status 1 =Released
Group T-##
d) Select the area Characteristics, with the following values:

Characteristics Key
T_FCLD## Check box
T_FCLE## nothing
e) Choose Contents. Add 3 rows. Enter the following:

T_FCLD## T_FCLE##
1 3
2 2
3 1
f) Save your table.
2. Create a procedure T_PROC_TAB_DEFAULT_T_FCLE_## which defines default values

using the table.
mouse button and create a global dependency as a procedure. Name it as follows:
Description: T_PROC_TAB_DEFAULT_T_FCLE_##
Note:

Group: T-##

table tab2_## ( T_FCLD## = T_FCLD## ,
Check your syntax.


a) Create a procedure.
Select your configuration profile T-FCL## with the right mouse button → Context
menu → Create Dependency → Global ...
On the first pop-up, choose continue.
Dependency T_PROC_TAB_DEFAULT_T_FCLE_##
Description Default values for T_FCLE##

Group: T-##
Editor (Syntax:) table tab2_## ( T_FCLD## = T_FCLD## ,

Check your syntax.

Release your procedure.

Set your Mast height to middle.
a) Choose Test
What happens to your fork length? Fork length is set to middle. It is a default value.
Are you able to change the value of fork length? Yes, you are able to change the default
value.
Are you able to change the value of fork length to (None)? You can't delete the default
value.
Set now the fork length to middle.
What happens to mast height? Nothing. No values assigned to mast height.

LESSON SUMMARY

Unit 8
Lesson 2
Facet Changes with Pre- and Selection
Conditions
LESSON OVERVIEW
Business Scenario
Ensure that the configuration is complete and consistent. Therefore, you decide the use of
pre- and selection conditions for the value assignment interface.
LESSON OBJECTIVES
Pre- and Selection Conditions for Value Assignment Interface
Figure 197: Uses of Object Dependencies
Preconditions

Figure 198: Preconditions
Figure 199: Precondition for a Characteristic Value
If a certain value is set for the characteristics Mast Height and Fork Length, some of the values
for characteristic Tonnage Capacity are hidden.
In a precondition, you define the circumstances under which a characteristic or characteristic
value is hidden or not ready for input.
If a Mast height other than large or fork length other than long is selected, all of the available
values are no longer offered for the Tonnage capacity characteristic. If the mast height and
fork length characteristics have no value, all values are offered for the Tonnage Capacity
characteristic, since the precondition is not violated. This is an important difference between
preconditions and selection conditions.
Animation: Precondition for a Characteristic Value

For more information on Precondition for a Characteristic Value, please view the
animation in the lesson Facet Changes with Pre- and Selection Conditions in your
online course.
A precondition is fulfilled:
● If the condition you enter is either true or unknown.

Lesson: Facet Changes with Pre- and Selection Conditions
● The specified value is selected for the specified characteristic.

● No value is selected for the specified characteristic.
The precondition is not fulfilled:

● If a different value is selected for the specified characteristic.
You can also use restrictable characteristics to limit the allowed values of characteristics (see
the section on constraints with inferences).
Precondition for Characteristics
Figure 201: Precondition for Characteristics
Animation: Precondition for Characteristics

For more information on Precondition for Characteristics, please view the
online course.
In a precondition, you define the circumstances under which a characteristic or characteristic

value is hidden or not ready for input.
In this precondition you defined, that MASTHEIGHT AND FORKLENGTH must be specified
before TONNAGECAPACITY is ready for input. If MASTHEIGHT AND FORKLENGTH is not
specified, characteristic TONNAGECAPACITY is not ready for input.
Precondition with Variant Table

If you use tables for preconditions, enter the valid value combinations for the preconditions in
the individual table rows.
A precondition is only fulfilled if the characteristic value assignment matches a table line. This
ensures that the configuration is consistent.
There may be lines with completely identical entries. The lines must be completely filled, with
no unvalued entries.

Figure 203: Variant Tables in Preconditions
Animation: Variant Tables in Preconditions

For more information on Variant Tables in Preconditions, please view the
online course.
If only allowed values are to be displayed in the valuation, enter the characteristic value to
which the precondition should refer directly in the precondition. The value is then only offered
if it is allowed on the basis of the value combinations defined in the table. The precondition is
assigned to the value to which it refers:
table TAB2 (Mastheight = $root.Mastheight

Forklength = 'Long')
If you want to use the precondition for the consistency check, you do not have to enter any
direct characteristic values in the precondition. Then it is only checked after the value has
been set whether the entire combination of values is allowed or not allowed. If the value
assignment is not allowed, you will receive an inconsistency message. You connect this
precondition to the characteristic whose valuation is to be checked using a precondition.

Selection Condition on Characteristic
Figure 205: Selection Condition
Figure 206: Selection Condition for a Characteristic
Animation: Selection Condition for a Characteristic

For more information on Selection Condition for a Characteristic, please view the
online course.
You can use a selection condition to achieve that a characteristic must be valuated.
In this example, it should be achieved that characteristic TONNAGECAPACITY becomes a
required characteristic. You can already specify in characteristic maintenance that the entry
for a characteristic is required. This leads to a permanent feature. This is not wanted in our
example. Therefore, a selection condition for the characteristic has to be created.


Unit 8
Exercise 16
Pre- and Selection Conditions for
Characteristics and Values
Simulation: Pre- and Selection Conditions for Characteristics and Values

For more information on Pre- and Selection Conditions for Characteristics and
Values, please view the simulation in the lesson Facet Changes with Pre- and
Selection Conditions in your online course.
Business Scenario
A configuration (characteristic valuation) must be complete and consistent so that the
configuration in the sales order can be released and the sales order issues requirements. Only
in this way can we plan and manufacture for the production of individual customers.
With pre and selection conditions, you can dynamically control when your characteristic value
assignment is complete and consistent.
Task 1: Precondition 1
1. Characteristic T_FCLF## = Tonnage Capacity can only get value assignments when
characteristic T_FCLD## = Mast height and T_FCLE## = fork length get assigned values.
Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF##. Open the
context menu with the right mouse button.
Choose Create Dependency → Global.
Inside Create Dependency on Characteristic, add the following:
Dependency: T_PRE_T_FCLD_FCLE_SPEC_##
Dependency Type: Precondition
On Basic Data, add the following:

Description: First T_FCLD## and T_FCLE##
Group: T-##
Select Editor and add the following:

t_fcld## specified and t_fcle## specified
Change the status to Released. Save your data.

1. For Characteristic T_FCLF## = Tonnage Capacity, the value 5000 kg can only be selected
when characteristic T_FCLD## = Mast hight or T_FCLE## = fork length don’t use the
value 3.
Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF## and value
5000kg. Open the context menu with the right mouse button.
Dependency: T_PRE_T_FCLD_FCLE_NE3_##

Description: Only if T_FCLD## or E## <>3
Group: T-##

T_FCLD## <> '3' or T_FCLE## <> '3'
Task 3: Selection Condition
1. Characteristic T_FCLF## = Tonnage Capacity must be evaluated, if characteristics

T_FCLD## = Mast height and T_FCLE## = Fork length are evaluated. Create a Selection
Condition for Characteristic T_FCLF##.
Dependency: T_SEL_T_FCLD_FCLE_SPEC_##

Description: Eval T_FCLD## and T_FCLE##
Group: T-##
Select Editor, and add the following:


2. Test your data.

Tonnage Capacity:
● 1. Try to select the tonnage capacity.
● 2. Set the mast height to large and the fork length to long. Now you are able to select
the tonnage capacity.
Note:
Can you select the tonnage capacity 5000 kg?
Tonnage Capacity:
● 3. Set the mast height to middle and the fork length to middle. Now you are able to
select the tonnage capacity.
Note:
Select the tonnage capacity of 5000 kg. If necessary, refresh your data.

Unit 8
Solution 16
Pre- and Selection Conditions for
Characteristics and Values
Simulation: Pre- and Selection Conditions for Characteristics and Values

For more information on Pre- and Selection Conditions for Characteristics and
Values, please view the simulation in the lesson Facet Changes with Pre- and
Selection Conditions in your online course.
Business Scenario
A configuration (characteristic valuation) must be complete and consistent so that the
configuration in the sales order can be released and the sales order issues requirements. Only
in this way can we plan and manufacture for the production of individual customers.
With pre and selection conditions, you can dynamically control when your characteristic value
assignment is complete and consistent.
1. Characteristic T_FCLF## = Tonnage Capacity can only get value assignments when
characteristic T_FCLD## = Mast height and T_FCLE## = fork length get assigned values.

Description: First T_FCLD## and T_FCLE##
Group: T-##


a) Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF##.

Open the context menu with the right mouse button. Choose Create Dependency →
Global.
b) Inside Create Dependency on Characteristic, add the following:

c) On Basic Data, add the following:

Description: first T_FCLD## and T_FCLE##
Group: T-##
d) Select Editor and add the following:

e) Change the status to Released. Save your data.
1. For Characteristic T_FCLF## = Tonnage Capacity, the value 5000 kg can only be selected
when characteristic T_FCLD## = Mast hight or T_FCLE## = fork length don’t use the
value 3.
Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF## and value
5000kg. Open the context menu with the right mouse button.

Description: Only if T_FCLD## or E## <>3
Group: T-##

T_FCLD## <> '3' or T_FCLE## <> '3'
a) Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF## and value
5000kg.
Global.

b) Inside Create Dependency on Characteristic, add the following values:

c) On Basic Data, add the following values:

Description: only if T_FCLD## or E## <>3
Group: T-##
d) Select Editor, and add the following:

t_fcld## <> '3' or t_fcle## <> '3'
Task 3: Selection Condition
1. Characteristic T_FCLF## = Tonnage Capacity must be evaluated, if characteristics

T_FCLD## = Mast height and T_FCLE## = Fork length are evaluated. Create a Selection
Condition for Characteristic T_FCLF##.

Group: T-##
Select Editor, and add the following:


a) Work with your class 300 T_FCL##. Navigate to characteristic T_FCLF##.
Global.
b) Inside Create Dependency on Characteristic, add the following values:


c) On Basic Data, add the following values:

Group: T-##
d) Select Editor, and add the following:

2. Test your data.

Tonnage Capacity:
● 1. Try to select the tonnage capacity.
● 2. Set the mast height to large and the fork length to long. Now you are able to select
the tonnage capacity.
Note:
Can you select the tonnage capacity 5000 kg?
Tonnage Capacity:
● 3. Set the mast height to middle and the fork length to middle. Now you are able to
select the tonnage capacity.
Note:
Select the tonnage capacity of 5000 kg. If necessary, refresh your data.
a) Start the simualtion with button Test
b) 1. Try to select the tonnage capacity.

This is not possible.
c) 2. Set the mast height to large and the fork length to long.
Now you are able to select the tonnage capacity.
Now tonnage capacity needs to be assessed.
You can't select the tonnage capacity of 5000 kg.
d) 3. Set the mast height to middle and the fork length to middle.
Now you are able to select the tonnage capacity.
Now tonnage capacity needs to be assessed.
You can select the tonnage capacity of 5000 kg.

LESSON SUMMARY

Unit 8
Learning Assessment
1. $del_default can delete default values. Which restrictions are to be considered?

X A There are no restrictions. All default values can be deleted in this way.
X B In this way, only default values defined in the characteristic can be deleted.
X C In this way, only default values that were set via ?= or $set_default can be deleted.
X D This functionality is not available under AVC.
X E This functionality is not available under LO-VC.
X F This functionality can be used under LO-VC as well as under AVC.
2. Which syntax elements can only be used in procedures?

X A $self, $parent, $root
X B $sum_parts
X C ?=
X D table
X E function
3. Pre and selection conditions can be assigned to characteristics and characteristic values.
What is not working?
X A Precondition to the characteristic
X B Precondition to the characteristic value
X C Selection condition to the characteristic
X D Selection condition to the characteristic value


UNIT 9 Variant Configuration in Pricing
Lesson 1
Pricing and Variant Configuration in Sales 340
Exercise 17: Modeling of Value-Dependent Pricing in Sales Orders 345
Exercise 18: Pricing with $set_pricing_factor 355
Lesson 2
Pricing and Variant Configuration in Purchasing 363
UNIT OBJECTIVES
● Do the pricing for your variant configuration scenario

● Add factors to pricing
● Define the pricing for variant configuration in purchasing

Unit 9
Lesson 1
Pricing and Variant Configuration in Sales
LESSON OVERVIEW
Business Scenario
You can now configure simple and complex products. But you still need to provide the
necessary information for pricing so that prices for the configurable product can be
determined based on the characteristic value assignment.
LESSON OBJECTIVES
Pricing and Variant Configuration in Sales
Figure 209: Pricing in Sales: The Basics
You can create a basic price for a configurable material. However, the price can also depend
on the product features of a specific variant that result from the value assignment process in
the sales order.

Lesson: Pricing and Variant Configuration in Sales
Since the product features of a configurable material are represented by characteristics and
their values, you can define surcharges and discounts that depend on characteristic values.
You define variant conditions for the surcharges and discounts. Condition types VA00
(absolute amounts) and VA01 (percentage amounts) are defined for variant conditions. You
can create variant conditions with reference to a material, a distribution channel, and a sales
organization.
A surcharge or discount is identified by a variant key. By assigning variant conditions to
characteristic values, or using dependencies, you control when a surcharge or discount is
applied. You define a characteristic with a reference to table SDCOM, field VKOND, to access
the condition table in dependencies.
If you use dependencies, you use the relevant variant keys to assign values to the reference
characteristic. (Watch out for upper and lower case!)
Figure 210: General Information
Animation: General Information

For more information on General Information, please view the animation in the
lesson Pricing and Variant Configuration in Sales in your online course.
Pricing is based on the configuration. This is the result of the assignment of values to
characteristics in the sales order.
Information that identifies the condition records that are relevant to pricing is sent to Sales
and Distribution (SD). The relevant records are determined in the following ways:
● By links between characteristic values and condition record keys.

Unit 9: Variant Configuration in Pricing
● By dependencies. A reference characteristic enters the keys of condition records in the

table field for variant conditions.
The value of the percentage or absolute surcharges is determined from the table of condition
records, according to the organizational levels and the material number.
Figure 212: Pricing in SD: Maintenance
Animation: Pricing in SD: Maintenance

For more information on Pricing in SD: Maintenance, please view the animation in
the lesson Pricing and Variant Configuration in Sales in your online course.
Pricing in the SD system is based on conditions.

Objects in the configuration are described by characteristics and characteristic values.
Pricing for configurable objects must therefore read both the characteristics and values that
have been assigned to a configurable material, as well as the SD conditions.
Create a reference characteristic (such as SURCHARGE) with reference to field SDCOM-
VKOND.
Create condition records with condition type VA00 (absolute amounts) and/or VA01
(percentage amounts). You can use both VA01 and VA00 in pricing. You can define any key
for the condition records (CAUTION: the keys are case-sensitive.)
You create the one-to-one assignments between characteristic values and condition records
using the PMEVC, here the detail view of the configurable material.
In the dependencies (procedures), you assign condition record keys to the reference
characteristic and enter conditions if required. You usually assign the procedure to the
configuration profile. The following example illustrates the syntax: SURCHARGE is a reference
characteristic for field SDCOM-VKOND. Surcharge_xyz is a condition record key.
$SELF.<Reference Charcateristic > = `Key of condition record if <conditions>
Beispiel: $SELF.SURCHARGE = `surcharge_xyz`

if EXTAS eq `ROADSET`and EXTRAS eq `MIRROR`.

Pricing Factors
Figure 214: Pricing Factors


Unit 9
Exercise 17
Modeling of Value-Dependent Pricing in Sales
Orders
Simulation: Modeling of Value-Dependent Pricing in Sales Orders

For more information on Modeling of Value-Dependent Pricing in Sales Orders,
please view the simulation in the lesson Pricing and Variant Configuration in
Sales in your online course.
Business Scenario
In our modeling exercise, the options for variant configuration should be used for pricing. In
addition to the maintained base price, valuation-dependent surcharges are defined and used.
Task 1: Create a Condition Record: Basic price

The sales price of your forklift should be a combination of basic price 30000.- and surcharges
of your extras. The surcharges are as follows:
100 for Road Equipment
90 for Additional Light
220 for Back view camera
—25 Reduction for small mirror
50 for large mirror
1. Directly execute the app Create Sales Condition. It can be found inside the group Sales
Add On.
Enter Condition Type PR00.
Inside the pop-up, select Material with release status.
Inside the header area, enter:
Distribution Channel: 10
Enter:
Material: T-FCL##
Amount: 30000

Unit: EUR or USD or ...
Save your condition.
Task 2: Create a Reference Characteristic

For the execution of a accurate pricing, you have to create a reference characteristic with a
connection to table SDCOM-VKOND.
Create a pricing reference characteristic T_SDCOM_VKOND_## and assign it to your class.
1. Execute the app VC Modeling Environment again.

Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
2. Inside the object tree, select the class 300 T_FCL##, open the context menu with the right
mouse button, and select:
Create Characteristic:
Characteristic: T_SDCOM_VKOND_##
Inside the area Reference to Table Field, enter:

Tab: SDCOM
Field: VKOND
Inside Basic Data check the status is set to Released.

Inside Additional Data set the check box No Display.
Task 3: Create Some Condition Records: Extras
1. Execute app Create Sales Condition .
Note:
May be left open.

Enter Condition Type VA00.
Material: T-FCL##
2. Enter the following variants:

XA## 100 EUR or USD or...
XB## 90 EUR or USD or...

XC## 220 EUR or USD or...
XD## — 25 EUR or USD or...
XE## 50 EUR or USD or...
Save your conditions.
Task 4: Add Pricing Information to Material

Connect your characteristic values of your extras with the condition record.
1. Open the VC modeling environment again.

Select your header material T-FCL## with a double click.
Open the tab page Variant Pricing and switch to Change Mode.
Enter:
Characteristic Char Value Variant Cond. Variant Cond. Description:

T_FCLX## A XA## Surcharge Road Equip.
T_FCLX## B XB## Surcharge Light
T_FCLX## C XC## Surcharge Camera
T_FCLX## D XD## Reduction mirror small
T_FCLX## E XE## Surcharge mirror large
Save your data.

Test your data and create a sales order.
1. Open the app Create Sales Order. It can be found inside the group Sales Add On.
Inside the initial screen, enter:
Order Type: OR
Distribution Channel 10

Division: 00
Continue.
2. Inside the overview screen enter:

Ship to party: T-C400
Cust Reference: your choice
Material: T-FCL##
Quantity: 1
3. Inside the value assignment screen do the following:
● Check the net value inside header.
● Set values for the Extras and Tonnage Capacity (also for Mast Height and also for Fork
Length). Check the variant condition (last row).
● Click on Done.
● Click on Complete Delivery.
4. Check Conditions.
Inside the Overview screen, open the conditions view.
Select the right icon inside the Sales view. It’s the 11th button, named Item conditions.
Cancel the sales order creation.

Unit 9
Solution 17
Modeling of Value-Dependent Pricing in Sales
Orders
Simulation: Modeling of Value-Dependent Pricing in Sales Orders

For more information on Modeling of Value-Dependent Pricing in Sales Orders,
please view the simulation in the lesson Pricing and Variant Configuration in
Sales in your online course.
Business Scenario
In our modeling exercise, the options for variant configuration should be used for pricing. In
addition to the maintained base price, valuation-dependent surcharges are defined and used.
Task 1: Create a Condition Record: Basic price

The sales price of your forklift should be a combination of basic price 30000.- and surcharges
of your extras. The surcharges are as follows:
100 for Road Equipment
90 for Additional Light
220 for Back view camera
—25 Reduction for small mirror
50 for large mirror
1. Directly execute the app Create Sales Condition. It can be found inside the group Sales
Add On.
Enter Condition Type PR00.
Inside the pop-up, select Material with release status.
Inside the header area, enter:
Enter:
Material: T-FCL##
Amount: 30000

Save your condition.

a) Directly execute the Create Sales Condition. It can be found inside the group Sales Add
On.
b) Enter Condition Type PR00.
c) Inside the pop-up select Material with release status.
d) Inside the header area, enter:

e) Enter:
Material: T-FCL##
Amount: 30000
f) Save your data.
g) Close the app.
Task 2: Create a Reference Characteristic

For the execution of a accurate pricing, you have to create a reference characteristic with a
connection to table SDCOM-VKOND.
Create a pricing reference characteristic T_SDCOM_VKOND_## and assign it to your class.
1. Execute the app VC Modeling Environment again.

Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
a) Open the app.
Environment.

Enter:
Material: T-FCL##
Change No. no entry
Class Type: 300
Plant: 1010
Enter Model.
2. Inside the object tree, select the class 300 T_FCL##, open the context menu with the right
mouse button, and select:
Inside the area Reference to Table Field, enter:

Tab: SDCOM
Field: VKOND
Inside Basic Data check the status is set to Released.

Inside Additional Data set the check box No Display.
a) Select the class 300 T_FCL##, open the context menu with the right mouse button
and:
b) Inside the area Reference to Table Field, enter:

Tab: SDCOM
Field: VKOND
c) Inside Basic Data check the status is set to Released.
d) Inside Additional Data set the check box No Display.
e) Save your characteristic.

Task 3: Create Some Condition Records: Extras
1. Execute app Create Sales Condition .
Note:
May be left open.
Enter Condition Type VA00.
Material: T-FCL##
a) Execute the app Create Sales Condition .
b) Enter the Condition Type VA00.
c) Inside the header area, enter:

Material: T-FCL##
2. Enter the following variants:


Save your conditions.

a) Enter:

b) Save your conditions.
Task 4: Add Pricing Information to Material

Connect your characteristic values of your extras with the condition record.

1. Open the VC modeling environment again.

Select your header material T-FCL## with a double click.
Open the tab page Variant Pricing and switch to Change Mode.
Enter:
Characteristic Char Value Variant Cond. Variant Cond. Description:

Save your data.

a) You are in VC modeling environment .
b) Select your header material T-FCL## with a double click.
c) Open the tab page Variant Pricing and switch to Change Mode.
d) Enter:
Characteris- Char Value Variant Cond Variant Cond Description:
tic
e) Save your data.

1. Open the app Create Sales Order. It can be found inside the group Sales Add On.
Order Type: OR
Division: 00
Continue.
a) Open the group Sales Add On. Execute the app Create Sales Orders.

b) Inside the initial screen, enter:

Order Type: OR
Division: 00
Continue.
2. Inside the overview screen enter:

Material: T-FCL##
Quantity: 1
3. Inside the value assignment screen do the following:
● Set values for the Extras and Tonnage Capacity (also for Mast Height and also for Fork
Length). Check the variant condition (last row).
● Click on Done.
a) Check the net value: it’s 30000 (if without values for all characteristics).
b) Set (all) values for the Extras and Tonnage Capacity (also for Mast Height and also for
Fork Length).
Check the net value: it’s 30435 (if with all extras).
More details you find with click on net value.
You find Variant Condition Key as last characteristic (if show hidden characteristics -
see settings)
c) Click on Done.
d) If you see Review Availability Check Result , than click on Apply .
a) Select the button Item Conditions. Check the data.
b) Leave the sales order without saving data.

Unit 9
Exercise 18
Pricing with $set_pricing_factor
Simulation: Pricing with $set_pricing_factor

For more information on Pricing with $set_pricing_factor, please view the
simulation in the lesson Pricing and Variant Configuration in Sales in your online
course.
Business Scenario
The price of the forklift is also dependent on the tonnage capacity. The price must include a
surcharge that directly depends on the value of the tonnage capacity.
Task 1: Create a Condition

Create a surcharge of 70.– per 100 kg tonnage capacity.
1. Create again condition records.

Execute the app Create Sales Condition .
Enter:
Condition Type: VA00
Inside the header, enter:

Material: T-FCL##
Variants:
100KG## 70,- EUR or USD or ...
Save.
Hint:
The unit of measure is here piece, i. per forklift. The unit of measure refers to
the configurable material. Forklift trucks are not sold in kg.
Task 2: Define Dependencies
1. Open the VC Modeling Environment. The data is known.

Create a global dependency for configuration profile T-FCL##.

Enter:
Dependency: T_PROC_PRICE_##
Basic Data:
Description: Addition Pricing and factor

Group: T-##
Editor: Syntax:
($self.T_SDCOM_VKOND_## = '100KG##',
$set_pricing_factor($self, T_SDCOM_VKOND_##, '100KG##', T_FCLF## / 100))
if T_FCLF## SPECIFIED
Check your syntax.

Save your data.

1. Open the app Create Sales Order. It can be found inside the group Sales Add On. Enter:
Order Type: OR
Division: 00
Continue.
2. Inside the overview screen, enter:

Material: T-FCL##
Quantity: 1
3. Inside the value assignment screen, do the following:

● Set values for the Extras.

Set values for the Tonnage Capacity (Mast height, Fork length).
Check the variant condition in net value and last characteristic (last row).
● Click on Done.
● Click on Apply .
Check the surcharges.

Unit 9
Solution 18
Pricing with $set_pricing_factor
Simulation: Pricing with $set_pricing_factor

For more information on Pricing with $set_pricing_factor, please view the
simulation in the lesson Pricing and Variant Configuration in Sales in your online
course.
Business Scenario
The price of the forklift is also dependent on the tonnage capacity. The price must include a
surcharge that directly depends on the value of the tonnage capacity.
Task 1: Create a Condition

Create a surcharge of 70.– per 100 kg tonnage capacity.
1. Create again condition records.

Execute the app Create Sales Condition .
Enter:
Inside the header, enter:

Material: T-FCL##
Variants:
Save.
Hint:
The unit of measure is here piece, i. per forklift. The unit of measure refers to
the configurable material. Forklift trucks are not sold in kg.
a) Execute the app Create Sales Condition.
b) Enter:
Enter:

c) Inside header enter:

Material: T-FCL##
d) Variants:
e) Save.
Task 2: Define Dependencies
1. Open the VC Modeling Environment. The data is known.

Create a global dependency for configuration profile T-FCL##.
Enter:
Basic Data:

Group: T-##
Editor: Syntax:
Check your syntax.

Save your data.
a) Open the app VC Modeling Environment.
Enter Material T-FL##, Plant 1010, Class Type 300, and BOM Application PP01.
b) Select your configuration profile T-FCL## and create a global dependency.
c) Enter:

d) Inside Basic Data, enter:

Group: T-##
e) Editor: Syntax:
f) Check your syntax.
g) Set the status to Released.
h) Save your data.

1. Open the app Create Sales Order. It can be found inside the group Sales Add On. Enter:
Order Type: OR
Division: 00
Continue.
a) Open the group Sales Documents. Execute the app Manage Sales Orders.
On the initial screen, select the entry Create Sales Order.

Order Type: OR
Division: 00
Continue.
2. Inside the overview screen, enter:


Material: T-FCL##
Quantity: 1
3. Inside the value assignment screen, do the following:
● Set values for the Extras.

Set values for the Tonnage Capacity (Mast height, Fork length).
Check the variant condition in net value and last characteristic (last row).
● Click on Done.
● Click on Apply .
a) Check the net value: it’s set to 30000 + Extra + Tonnage Capacity
b) Click on Done.
c) In Review Availability Check result click on Apply.
Check the surcharges.
a) Select the button Item Conditions. Check the data.
b) Select the right icon inside Sales view. It’s the 11th button, named Item conditions.
c) Check the surcharges.
d) Leave the sales order without saving the data.

LESSON SUMMARY

Unit 9
Lesson 2
Pricing and Variant Configuration in
Purchasing
LESSON OVERVIEW
Business Scenario
You can now configure simple and complex products. But you still need to provide the
necessary information for pricing so that prices for the configurable product can be
determined based on the characteristic value assignment.
LESSON OBJECTIVES
Pricing and Variant Configuration in Purchasing
Figure 217: Pricing in Purchasing I
Animation: Pricing in Purchasing I

For more information on Pricing in Purchasing I, please view the animation in the
lesson Pricing and Variant Configuration in Purchasing in your online course.

You maintain condition records for pricing a configurable material in the purchasing info
record.
The procedure is similar to the pricing process in sales and distribution.
The characteristic values assigned come from the sales order or the material master record
(material variant). You can also configure a material in the purchase order.
To create condition records in the purchasing info record, choose: Extras → Variant
Conditions. The variant key corresponds to the price.
By means of object dependencies, the condition records are transferred as values to the
reference characteristic that refers to MMCOM-VKOND. Assign this reference characteristic
to the variant class of the configurable material.
In dependencies (procedures), use the variant key to assign the variant condition to the
reference characteristic. Assign the dependencies to the configuration profile of the
externally procured material.
Figure 219: Pricing in Purchasing II
LESSON SUMMARY

Unit 9
Learning Assessment
1. Which points have to be considered when using $set_pricing_factor?

X A $set_pricing_factor can only be used in procedures. This is not allowed in other

types of object dependencies. New: set_pricing_factor can (only) be used in
constraints with AVC.
X B $set_pricing_factor only sets the factor. The variant condition must already be
assigned.
X C Only integer numbers can be used as factors.
X D The syntax $set_pricing_factor can only be used under AVC (Advanced Processing
Mode).
X E The syntax $set_pricing_factor can only be used under LO-VC (Classic Processing
Mode).
2. Variant conditions can also be used for pricing in Purchasing. However, what are the
restrictions here?
X A The MMCOM-VKOND field does not exist in the standard system.
X B You can only use VA01 as a condition type (not VA00).
X C You cannot use the direct assignment of variant conditions to characteristic values
under LO-VC.
X D You cannot use procedures here.
X E You cannot use $set_pricing_factor.
X F There are not restrictions under AVC.


UNIT 10 Material Variants
Lesson 1
Material Variants 368
Exercise 19: Material Variants with Pricing, Material BOM and Routing 373
UNIT OBJECTIVES
● Explain the benefits of working with material variants

● Create material variants

Unit 10
Lesson 1
Material Variants
LESSON OVERVIEW
Business Scenario
Your company wants to manufacture and store anonymously material variants, that are
special configurations of your configurable material. Which techniques do you use?
LESSON OBJECTIVES
Material Variants
Figure 220: Material Variants: Concept
The material master record of a material variant is linked to the configurable material and
configured using the characteristics of the configurable material. This variant of the
configurable material can then be manufactured and kept in stock.

Lesson: Material Variants
Figure 221: Material Variants: System Activities
You create material variants with a material type that is kept in stock.
To let you assign characteristic values to a material variant, you link the material to the
configurable material whose characteristics you want to use to describe the variant.
You can enter a cross-plant configurable material on the basic data screen. However, a cross-
plant configurable material can only be used in purchasing. There, you can print out a
document item with its assigned values. If you do not enter a plant-specific configurable
material for the material, the characteristic values of the cross-plant configurable material are
displayed.
Animation: Material Variants: System Activities

For more information on Material Variants: System Activities, please view the
animation in the lesson Material Variants in your online course.
Before you can use type matching in SD, you must enter a plant-specific configurable material
in the MRP data of the material master.
To assign values, choose Configure Variant. You also need to maintain a BOM for material
variants. You can either create a new BOM for the material, which is separate from the
configurable material, or you can link the material variant to the BOM of the configurable
material. The BOM is then interpreted and exploded according to the values you assign in the
material master record.
You can also create a separate task list (routing) for the material variant, or use the task list of
the configurable material. The task list for the configurable material is also interpreted and
exploded according to the characteristic values assigned in the material master record.

Unit 10: Material Variants
Figure 223: Material Variant
Now you have to model the material variant. As material variants are also supposed to be
planned, manufactured, and sold, you also require a BOM, routing, and pricing. For this
reason, you need a specific material master.
In simple terms, you can either create specific data or use the data of the configurable
material.
There are two scenarios for type matching of a material variant.
The first is defined inside Configuration Profile under Settings. This is used in the evaluation
screen and is only informative.
The second “ftype matching ” scenario is set in Customizing for item categories in Sales and
Distribution. Here you can activate the type matching for material variants, set an availability
check and set actions for material variants (notes or hard replacement).
Animation: Material Variant

For more information on Material Variant, please view the animation in the lesson
Material Variants in your online course.
You can exclude some characteristics from type matching, means: you find material variants,
even though the characteristics show differences. Such excluded characteristics are stored
inside table CABN_EXCL To evaluate/read this table you execute report
RCU_EXCL_CHARACTERISTICS . This report is also available as transaction
RU_EXCL_CSTIC.

Material Variants: Header Material and Assemblies
Figure 225: Material Variants - Type Matching
Type matching for BOM header materials:

● Type matching for header materials can run as you process a sales order. If all of the
characteristic values assigned to the configurable material match those assigned to the
material variant, the configurable material can be replaced with the material variant. The
substitution can take the form of either a message to the user that a variant exists, or an
automatic replacement of the configurable material - depending on the system settings.
Type matching for BOM subassemblies (order BOM profile only):

● When you process an order BOM, you can replace assemblies in the BOM with suitable
material variants. The characteristic values assigned to the assembly must be identical to
the values assigned to the material variant.
The system checks all configurable assemblies in the BOM and searches for matching
material variants. You cannot call type matching for one assembly at a time. Type matching
must be started manually by requesting the function - it cannot be started automatically.
Substitution is also done manually.

Figure 226: Configured Task List
Only for LO-VC

Creating a task list for a material or sales order from the simulation:
In the configuration simulation choose View → Objects → Task List to display the exploded
task list. You can copy the result to create a new task list without leaving the simulation.
On the result screen for a simulated task list explosion, choose Environment → Result as task
list to create a new task list. Enter the object for which you want to create the task list. When
you create the new task list, you automatically copy the material assignment from the
template, unless you enter a different material.
Animation: Configured Task List

For more information on Configured Task List, please view the animation in the
lesson Material Variants in your online course.
This functionality is also available in the order BOM transaction CU51.

There is currently no comparable functionality under AVC.

Unit 10
Exercise 19
Material Variants with Pricing, Material BOM
and Routing
Simulation: Material Variants with Pricing, Material BOM and Routing

For more information on Material Variants with Pricing, Material BOM and
Routing, please view the simulation in the lesson Material Variants in your online
course.
Business Scenario
Your company has noticed that often customers choose the same options for the product. To
satisfy customer requirements more quickly, a model of the forklift could be produced and
stocked in anticipation of an order. To do this, you create a variant for your configurable
forklift.
Task 1: Create a Material Master

The configurable material T-FCL## does not exist as a physical material, and cannot be made
to stock. Therefore, you want to make a forklift variant T-FCL##-1 to stock, independent of
any order.
1. Create material variant: T-FCL##-1

Material: T-FCL##-1
Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+ 2
Costing 1+ 2

Note:
Set the check box Create views selected.
Plant 1010
Sales Org 1010
Change / enter the following inBasic Data 1+2:
● Description Variant 1 of Forklift T-FCL##
Sales Org 1+2
T-FCL##
Pricing Reference Ma-
terial:
tem Category Group: NORM
Trans Grp. 0001
Loading Grp 0001
MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Lot size Procedure FX
Fixed lot size: 100

SchedMargin key 001
Strategy group 65

Individual / Coll. 2
Work Scheduling
Costing 2
Standard price: 25000
Save your Material.
Task 2: Product Master
1. Expand your material inside product master and do a value assignment.

Open the app Manage Product Master Data. It can be found inside the Product Master
group.
Search for the following:
Product : T-FCL##-1
Click on Go.
One result is found. Click on the line. The Detail screen opens.
Switch to Edit mode.
Open the Plants view.
Click on the line for plant 1010. The Detail screen opens.
2. Plant detail screen: Select the view Configuration.

Enter:
Configurable Product: T-FCL##
Select the entry: Configure Variant:

Extras: no entry
Driving Seat: 1 = fix
Seat Back: 1 = Standard
Mast height: 1 = small
Type of Drive: D = Diesel
Engine Performance: 45 kW
Color: R= red
Counterbalance: Length x Width x Height 400 x 500 x 600 mm
Tonnage Capacity: 3.500 kg

Fork length: 3 = long
Apply your data.

Apply plant data.
Save your Product.
Task 3: Material BOM
1. You don’t need a special BOM for your material variant. You connect your variant with
your Super BOM.
Open the app Create Link to Configurable Material in group Variant Configuration
Modeling. Enter:
Material T-FCL##-1
Plant: 1010
BOM Usage: 1
Alternative: no entry
Enter your data.

Save your data.
Task 4: Routing
1. For your material you need a appropriate routing. Connect your material with the
supersession routing.
Open the app Change Routing in group Product Engineering .
On the initial screen, enter:
Material: T-FCL##
Plant: 1010
Select the Header button.

Inside the header, select the button Assignment. Enter:
GrC: 1
Material: T-FCL##-1
Plant: 1010
Save your routing assignment.
2. Save your routing assignment.
Task 5: Sales Order

If you want to test variant matching, create a sales order for your configurable material T-
FCL##, (not for the material variant), using the same data as in your previous sales orders.
On the value assignment screen, enter the characteristic values that you have assigned to the
material variant. Here - in view Variant Configuration you can see the Fully Matching Product
Variant and you can start a Variant Matching . When you go back from the value assignment

screen to the sales order overview, you should see a message informing you that the will be
replaced by the variant.
1. Open the app Create Sales Order. On the initial screen, enter the following:
Order Type: OR
Division: 00
Continue.
2. On the overview screen, enter:

Material: T-FCL##
Quantity: 1
3. Value Assignment screen:

Extras: no entry
Color: R= Red
fork length: 3 = lang
Tonnage capacity: 3.500 kg
Inside the value assignment screen do the following:
● Check the button Variant Matching. Your material Variant is found.
● Double click the variant.
System message: ... your material will be replaced....
● Click on Replace.

Check the overview screen. The eplacement took place.

Close the sales order screen.

Unit 10
Solution 19
Material Variants with Pricing, Material BOM
and Routing
Simulation: Material Variants with Pricing, Material BOM and Routing

For more information on Material Variants with Pricing, Material BOM and
Routing, please view the simulation in the lesson Material Variants in your online
course.
Business Scenario
Your company has noticed that often customers choose the same options for the product. To
satisfy customer requirements more quickly, a model of the forklift could be produced and
stocked in anticipation of an order. To do this, you create a variant for your configurable
forklift.
Task 1: Create a Material Master

The configurable material T-FCL## does not exist as a physical material, and cannot be made
to stock. Therefore, you want to make a forklift variant T-FCL##-1 to stock, independent of
any order.
1. Create material variant: T-FCL##-1

Material: T-FCL##-1
Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+ 2
Costing 1+ 2

Note:
Set the check box Create views selected.
Plant 1010
Sales Org 1010
Change / enter the following inBasic Data 1+2:
● Description Variant 1 of Forklift T-FCL##
Sales Org 1+2
T-FCL##
Pricing Reference Ma-
terial:
tem Category Group: NORM
Trans Grp. 0001
Loading Grp 0001
MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Fixed lot size: 100

SchedMargin key 001
Strategy group 65

Work Scheduling
Costing 2
Save your Material.

a) Enter the app Create Material . Inside the initial screen, enter:
Material: T-FCL##-1
Industry Sector M (Mechanical Engineering)
b) Select the following views:

Basic Data 1+ 2
MRP 1+ 2+ 3 + 4
Work Scheduling
Accounting 1+ 2
Costing 1+ 2
Plant 1010
Sales Org 1010
Distribution Chan- 10
nel
Change / enter the following in Basic Data 1+2:
Description Variant 1 of Forklift T-FCL##

Base unit of Measure PC

Net weight: 3.100
c) Sales Org 1+2

T-FCL##
Pricing Reference Material:
Item Category Group: NORM
d) Sales: General / Plant

Trans Grp. 0001
Loading Grp 0001
e) MRP 1, 2, 3, 4
MRP Type PD
MRP Controller F##
Fixed lot size: 100
SchedMargin key 001
Strategy group 65
f) Work Scheduling
g) Costing 2
h) Save your Material.
Task 2: Product Master
1. Expand your material inside product master and do a value assignment.

Open the app Manage Product Master Data. It can be found inside the Product Master
group.
Product : T-FCL##-1
Click on Go.
Switch to Edit mode.
Open the Plants view.
Click on the line for plant 1010. The Detail screen opens.
a) Open the app Manage Product Master Data.
It can be found inside the Product Master group.
Product: T-FCL##-1
Click on Go.
b) Switch to Edit mode.
c) Open the Plants view.
d) Click on the line for plant 1010. The Detail screen opens.
2. Plant detail screen: Select the view Configuration.

Enter:
Select the entry: Configure Variant:

Extras: no entry
Color: R= red
Apply your data.

Apply plant data.

Save your Product.

a) Select the view Configuration and enter:
b) Select the right hand side entry Configure Variant:

Extras:: no entry
Color: R= red
c) Apply your data.
d) Apply plant data.
e) Save your Product.
Task 3: Material BOM
1. You don’t need a special BOM for your material variant. You connect your variant with
your Super BOM.
Open the app Create Link to Configurable Material in group Variant Configuration
Modeling. Enter:
Material T-FCL##-1
Plant: 1010
BOM Usage: 1
Enter your data.

Save your data.
a) Open the app Create Link to Configurable Material in group Variant Configuration
Modeling.
b) Enter:
Material T-FCL##-1
Plant: 1010
BOM Usage: 1

c) Enter
d) Save your data.
Task 4: Routing
1. For your material you need a appropriate routing. Connect your material with the
supersession routing.
Open the app Change Routing in group Product Engineering .
Material: T-FCL##
Plant: 1010
Select the Header button.

Inside the header, select the button Assignment. Enter:
GrC: 1
Material: T-FCL##-1
Plant: 1010
Save your routing assignment.

a) Open the app Change Routing in group Product Engineering .
b) On the initial screen, enter:

Material: T-FCL##
Plant: 1010
c) Select the Header button.
d) Inside the header, select the button Assignments.

Enter:
GrC: 1
Material: T-FCL##-1
Plant: 1010
e) Enter
2. Save your routing assignment.

a) Save your data.
Task 5: Sales Order

If you want to test variant matching, create a sales order for your configurable material T-
FCL##, (not for the material variant), using the same data as in your previous sales orders.
On the value assignment screen, enter the characteristic values that you have assigned to the
material variant. Here - in view Variant Configuration you can see the Fully Matching Product
Variant and you can start a Variant Matching . When you go back from the value assignment

screen to the sales order overview, you should see a message informing you that the will be
replaced by the variant.
1. Open the app Create Sales Order. On the initial screen, enter the following:
Order Type: OR
Division: 00
Continue.
a) Open the group Sales Add On. Execute the app Create Sales Order.
b) On the initial screen, enter:

Order Type: OR
Division: 00
Continue.
2. On the overview screen, enter:

Material: T-FCL##
Quantity: 1
3. Value Assignment screen:

Extras: no entry
Color: R= Red

Inside the value assignment screen do the following:
● Check the button Variant Matching. Your material Variant is found.
● Double click the variant.
System message: ... your material will be replaced....
● Click on Replace.
Check the overview screen. The eplacement took place.

Close the sales order screen.
a) Do the value assignment.
Accessories: no entry
Color: R= red
b) Check the button Variant Matching. Your material Variant is found.
c) Double click the variant. System message: ... your material will be replaced....
d) Click on Replace.
e) You are in the overview screen. If not, than click on Complete Delivery.
f) Check the overview screen. The replacement took place.
g) Cancel the creation.
h) Close the sales order screen.

LESSON SUMMARY

Unit 10
Learning Assessment
1. Material variants require a BOM for planning and production. What options are available
for this.
X A You can create your own independent BOM for the material variant.
X B You can create your own BOM for the material variant using a BOM exploded in
simulative mode as a template.
X C You can simply assign the material variant to the BOM of the configurable material.
2. Material variants require a routing for planning and production. What options are available
for this.
X A You can create your own independent routing for the material variant.
X B You can create your own routing for the material variant and use a simulatively
exploded routing as a copy model. However, this option currently only exists for LO-
VC (classic processing mode).
X C You can create your own routing for the material variant and use a simulatively
exploded routing as a copy model. However, this option currently only exists for AVC
(advanced processing mode).
X D You can simply assign the material variant to the routing of the configurable
material.

3. Where do the settings for Variant Matching exist?

X A There is no Variant Matching under LO-VC (classic processing mode). This means
that there are no settings in the configuration profile.
X B Variant Matching exists under LO-VC (classic processing mode). There are also
settings in the configuration profile.
X C There is no Variant Matching under AVC (advanced processing mode). This means
that there are no settings in the configuration profile.
X D Variant Matching exists under AVC (advanced processing mode). However, there
are no settings in the configuration profile.
X E There are also settings in Customizing for item categories in Sales and
Distribution.

UNIT 11 VC – Integration Logistic Chain
Lesson 1
Processes in SD 393
Lesson 2
Processes in Planning and Production 405
Exercise 20: Process for Quotation → Order → Planning → Production 409
UNIT OBJECTIVES
● Explain the processes in sales and distribution

● Define dependencies depending on sales document category or type
● Define processes for planning and production

Unit 11: VC – Integration Logistic Chain

Unit 11
Lesson 1
Processes in SD
LESSON OVERVIEW
Business Scenario
The project team needs an overview of the entire logistics process regarding our modeled
configurable product. This means:
● Quotation
● Sales order with connection to quotation
● Procurement
● Shipping
LESSON OBJECTIVES
Processes in Distribution
Figure 229: Business Process Integration

There is usually a quotation phase involved in the make-to-order business process.

Variant configuration can be used within the quotation phase.
Order BOMs can be used for the make-to-order quotations to create a technically complete
product structure, which can be used as the basis for product costing and pricing.
Material requirements can be planned only after the quotation has been converted to a sales
order.
Subordinate assemblies, components, and raw materials may be pre-planned and already
available or not planned (direct production).
If the direct production method is used, collective orders may also be used to simplify the
production and costing processes.
Finally, all related production orders are allocated directly to the originating sales order line
item.
Overview of Sales Processes and Documents
Figure 230: Overview of Sales Processes and Documents
Animation: Overview of Sales Processes and Documents

For more information on Overview of Sales Processes and Documents, please
view the animation in the lesson Processes in SD in your online course.
The above graphic shows the relationships between the subprocesses of sales order
processing in the SAP system. The sequence of blocks from top to bottom shows the usual
chronological sequence in the sales process.
The boxes inside the blocks show the relevant sales and accounting documents.
Contracts and scheduling agreements are sales support documents in presales.

Lesson: Processes in SD
Sales documents are documents that are created during presales and order processing.
Inquiries, quotations, contracts, scheduling agreements and standard orders are examples of
sales document types.
Deliveries, transport orders, and transports are shipping documents.
Goods issue documents contain the changes to stock, and are the basis for accounting
documents.
Billing documents serve as the basis for accounting documents.
Presales activity: quotation
Figure 232: Presales Activity: Quotation
The quotation must be complete. Otherwise, you cannot create orders with reference to the
quotation.
The quotation must not generate requirements. See the following slides for more information.
You can run pricing in a quotation. You can use the sales order costing function to do this.
You can also maintain order BOMs and order task lists in the quotation. You could then use
them for sales order costing.
Sales order costing can run in either unit costing or product costing. In unit costing, you can
use the result of product costing and other manually created costing elements.
Create Order

Figure 233: Create Order
Animation: Create Order

For more information on Create Order , please view the animation in the lesson
Processes in SD in your online course.
An order can refer to an existing business transaction. For example, you can use one or more
inquiries and/or quotations as templates. In this case, the SAP system copies the relevant
data to the order. A quotation can also be the basis for several orders. You can determine that
only quotations for one customer are brought together.
In variant configuration, too, you can create orders with reference to presales activities. The
values assigned during configuration are also copied. However, the dependencies on the value
assignment screen for configuration are reprocessed, if you work with ‘Copy’. If your
dependencies read the order type or SD document category, you may have different results.

Processes in SD: Handover Requirements
Figure 235: Controlling the Requirements Transfer
Processes in SD: Strategies — Requirement Types — Requirement Classes
Figure 236: Strategies in Variant Configuration
Requirements class 103 Planning without final assembly contains the following settings:
Planning indicator 3 = Single item planing

Consumption indicator 2 = Consumption planning without final assembly
Configuration allowed / -
Required
Configuration consumption -

Requirements reduction indi- -=

cator
No reduction of independent requirements (only for sales
order issue)
Requirements type 1 = Planned independent requirements
Requirements class 105 Assembly planning contains the following settings:
Planning indicator 1= Net requirements planning

Consumption indicator 1= Consumption planning with final assembly
Configuration allowed / -
Required
Configuration consumption -
Requirements reduction indi- -=
cator
No reduction of independent requirements (only for sales
order issue)
Requirements type 1 = Planned independent requirements
Figure 237: Requirements Classes
You use requirement types to identify different requirements (for example, order
requirement, delivery requirement, or individual customer requirement). One requirements
class is assigned to each requirements type.

A requirements class controls all functions in logistics that are relevant to requirements. The
requirements class defines the following sales-relevant points:
● Whether there is an availability check and requirements transfer for a transaction.
● Whether the requirement is relevant to MRP.
● The assignment indicator from the sales side that controls how customer requirements.
● Whether an item is to be posted to auxiliary account assignment.
Reqmts class 46 200 201 202 212 43 42

Availablilty X X X X X
Transfer of X X X X X X X
Reqmts
Allocation in- Planning Planning
dicator without without
assembly assembly
Configuration Required Optional Optional Optional Required Required
Cons. confble Chars Chars
matl. planning planning
Assembly 4 = plan- 2= pro- 2 = Net- 2 = Net-
type ning or- duction work work
der order
Order type PP04 PS04 PS04

Schedule Line and Item Categories
Figure 238: Schedule Line Categories
SAP can only copy items for which schedule line items were formed from a sales document to
a delivery. Schedule line items are controlled according to the schedule line item category.
Movement type = Movement type for posting quantities and changed values to inventory
accounting. The movement type is only relevant to items/schedule line items with goods
movements. (In other words, not to items in inquiries, quotations, or orders that are not
relevant to inventory management.)
Delivery relevance of schedule line item category = only if a physical goods movement is to
occur. (In other words, not in a quotation, for example.)
Requirement = Requirements transfer at schedule line item level.
Availability = Availability check at schedule line item level.
Standard settings:
Character 1 = (A Inquiry, B Quotation, C Order, D Returns).
Character 2 = (T No inventory management, N No MRP, P Deterministic MRP, V ,X ).
Schedule line catego- CP = Deterministic CN =No MRP CT = No inventory

ry MRP management, no GI
Item is relevant for X X X
delivery
Movement Type 601 601
Incompletion proce- 30 30 31
dure

Require /Assembly X
Availability check X
Product allocation ac- X
tive
Item categories
Figure 239: Item Categories
Animation: Item Categories

For more information on Item Categories, please view the animation in the lesson
Processes in SD in your online course.
Configuration strategy: Standard = 01 (lets you override the standard call of the value
assignment interface).
Material variant action: Controls the system's reaction to found material variants.
ATP material variant: Allows an ATP check for found material variants.
Structure scope: Controls BOM explosion in DS (standard = D = with configuration: the
configuration profile determines the BOM explosion).
Application: BOM application for BOM explosion in SD: overrides application in configuration
profile.
Variant matching: Activates material variant matching.

Create delivery group: Collects main item and subitems to form a delivery group.
Manual alternative: Alternative BOMs can be selected manually.
Parameter effectivities: In the sales order, you can assign values to effectivity parameters
(engineering change management).
item category TAC = variant configuration TAM TAE TAN

Sched. Line allowed X X X X
Billing Relevance A = delivery related billing docu- A A
ment
Pricing X = yes, pricing standard X
Configuration Strategy 01 01
Variant Matching X
Mat. Variant Action 1 = note — only in append
ATP material
Structure scope D D
Application SD01
Pricing Types in SD
Figure 241: Pricing Types in SD

Animation: Pricing Types in SD

For more information on Pricing Types in SD, please view the animation in the
lesson Processes in SD in your online course.
Pricing types:
● Simple pricing with surcharges and discounts (also dependent on characteristic values
assigned to configured product)
● Unit costing/product costing
● Combinations of both
Relevant condition types:

● PR00, VA00, VA01, EK01, EK02
Please note:
● Multilevel pricing is not possible.
● The characteristics of lower-level assemblies do not affect pricing.
● Changes made in order BOM maintenance do not affect pricing (exception - indirectly via
product costing).
● Product costing for an item is carried out from the sales order (on the basis of the BOM
and task list).
Costing and Pricing in SD
Figure 243: Costing and Pricing in SD

Animation: Costing and Pricing in SD

For more information on Costing and Pricing in SD, please view the animation in
the lesson Processes in SD in your online course.
The sales document type (Customizing for Sales) is used to determine which condition type
(EK01/EK02) is to be used for costing.
Condition type EK01 or EK02 must be specified for the corresponding pricing procedure
defined for the sales order.
Condition type EK01/EK02 uses Condition category “Q” = costing.
You can specify that a sales order item should be costed automatically. You activate this in
the corresponding requirements class.
You can also specify in the requirements class whether product costing or unit costing should
be used to cost the item. If this indicator is not set, you have to select the costing method
manually.
LESSON SUMMARY

Unit 11
Lesson 2
Processes in Planning and Production
LESSON OVERVIEW
Business Scenario
The project team needs an overview of the entire logistics chain regarding our modeled
configurable product. This contains:
● Shop floor control
● Customer request changes
● Shipping
LESSON OBJECTIVES
Planning and Production Process for Configurable Products
Figure 245: Process Flow for Sales Order Related Production

Animation: Process Flow for Sales Order Related Production

For more information on Process Flow for Sales Order Related Production,
please view the animation in the lesson Processes in Planning and Production in
your online course.
Sales order related production means that the product is manufactured for a specific sales
order, not made to stock.
An individual customer requirement is generated from the sales order item and passed on to
MRP.
Then you use MRP to plan material requirements and the product is manufactured in
production. When the product is finished, you post a goods receipt to sales order stock for
this particular sales order item.
As soon as the delivery is due, you can create the delivery in SD and post a goods issue. The
goods issue causes a reduction in the sales order stock. Then you create the billing document
in SD.
Figure 247: Production Order
Animation: Production Order

For more information on Production Order , please view the animation in the
lesson Processes in Planning and Production in your online course.
The production order runs through a series of individual activities.

Determining the WIP, calculating variances, and clearing are general periodic operations for
cost controlling.

Lesson: Processes in Planning and Production
You must define a series of settings for each individual stage if an order is to be processed
successfully.
CO configuration includes a special feature which sets the prerequisites for determining the
WIP, calculating variances, and clearing.
Figure 249: Change Process: Sales Order — Production Order
In the standard system, you are allowed to make changes to sales order items for which
production orders already exist.
Once the values assigned to a configurable item in the sales order have been changed, the
production order is not automatically updated. (However, this can be implemented using
assembly processing.)
In a standard scenario, it is permitted to make changes to items in the sales order for which
production orders already exist.
After a change has been made to the valuation of a configurable item in the sales order, the
corresponding production order is not updated automatically. (However, this can be realized
by assembly processing.)
As long as no “Time Ticket” or goods movements have taken place for the production order, it
is possible via Read PP master data to update the production order. The reading of the PP
master data is also approved orders possible. The release is then withdrawn.
Once confirmations or goods movements exist for the production order, an automatic update
is no longer possible. You can use OCM to support manual changes to production orders. This
partially automates the process.

Processes Behind Planning and Production
Figure 250: Finishing Up in SD

Unit 11
Exercise 20
Process for Quotation → Order → Planning →
Production
Simulation: Process for Quotation → Order → Planning → Production

For more information on Process for Quotation → Order → Planning →
Production, please view the simulation in the lesson Processes in Planning and
Production in your online course.
Business Scenario
You received a customer inquiry for a specific configuration of the forklift. Now you have to
respond with a formal quotation.
Later, this customer sends a purchase order for this product as originally configured.
Then you have to convert the quotation into a sales order.
To start the procurement process, an MRP run is executed to create procurement elements
and start production.
Task 1: Create a Quotation
1. Start the relevant app. It can be found inside the group Sales Add On.
2. Enter the following inside the initial screen:

Quotation Type QT
Division: 00
Overview screen:
Sales to party T-C400
Ship to party T-C400
Cust. Reference: <any>
Valid to: Today’s date + 1 month
Material: T-FCL##
Order Quantity 1

Execute.
Do a value assignment. For example:
Extras: Road Equipment
Driving Seat: fix
Seat Back: Standard
Type of Drive: Diesel
Engine Performance: 55KW
Mast Height: Large
Color: Black
Counterbalance: Length x Width x Height 400 x 500 x 600
Fork Length: Short
Tonnage Capacity: 5000
Click on Done.
Save your data.
Write down quotation number. _____________________________________
Task 2: Create a Sales Order with Reference
1. Now you create a sales order and connect it to your quotation.

Execute the right app. It can be found inside the Sales Add on area.
Enter the following inside the initial screen:
Order Type: OR
Sales Office 00
BEFORE YOU EXECUTE: Check the footer line. → Create with Reference. Enter your
Quotation number.
Note:
If you are not able to enter a Quotation number, perform a F4 help inside the
field Quot. Then select Search for Sales Document by customer and enter your
user inside field Created by.
Apply the Review Availability Check Result .

Add a Cust. Reference of your choice.
Save your Sales Order.________________________

Task 3: Stock Requirements List
1. Display the Stock Requirements List.

Execute the right app inside the group Sales Add On.
Enter material T-FLC## for plant 1010.
Click on Continue.
The first line displays the sales order stock and the second the sales order with item
number.
Double click the second line and check the Requirements class MMTO config. value. Don’t
close the pop-up.
Select the F9 help to display the configuration.
Select the F7 help to display the sales order.
Close the screen.
Task 4: MRP run: Make to Order (Multi Level)

You perform a MRP run.
1. Perform a multi level MRP run for the sales order for your forklift T-FCL##.
Execute the app MTO Planning MD50.
Enter:
Sales Order: (your noticed number)
Sales Order item 0010
Execute twice, until you get a result screen.
1. Display the Stock Requirements List MD04.

Click on Continue.
Your planned order is visible. Check the detail screen. Double click the number of the
planned order.
Display the details of your planned order. Select the Display Element (F7) icon.
Inside your planned order, select the entry Component Overview.
Close the screen and move back until the stock requirements list is displayed again.
Task 6: Convert your Planned Order into a Production Order
1. Convert your Planned order into a Production order

Inside your stock requirements list, double click again on your planned order number.
Select the button —> Prod. Ord..
The header of your Production Order opens.
2. Release and save your Production Order.

3. Refresh your Stock / Requirements list.

Your Production Order number is visible.
Close the screen.

Unit 11
Solution 20
Process for Quotation → Order → Planning →
Production
Simulation: Process for Quotation → Order → Planning → Production

For more information on Process for Quotation → Order → Planning →
Production, please view the simulation in the lesson Processes in Planning and
Production in your online course.
Business Scenario
You received a customer inquiry for a specific configuration of the forklift. Now you have to
respond with a formal quotation.
Later, this customer sends a purchase order for this product as originally configured.
Then you have to convert the quotation into a sales order.
To start the procurement process, an MRP run is executed to create procurement elements
and start production.
Task 1: Create a Quotation
1. Start the relevant app. It can be found inside the group Sales Add On.
a) Open the group Sales Add On. Execute the app Create Sales Quotation.
2. Enter the following inside the initial screen:

Quotation Type QT
Division: 00
Overview screen:
Ship to party T-C400
Valid to: Today’s date + 1 month
Material: T-FCL##

Order Quantity 1
Execute.
Do a value assignment. For example:
Extras: Road Equipment
Driving Seat: fix
Seat Back: Standard
Type of Drive: Diesel
Mast Height: Large
Color: Black
Counterbalance: Length x Width x Height 400 x 500 x 600
Fork Length: Short
Tonnage Capacity: 5000
Click on Done.
Save your data.
Write down quotation number. _____________________________________
a) Enter the following inside the initial screen:
Quotation Type QT
Division: 00
b) Overview screen:
Valid to: Today’s date + 30 days
Material: T-FCL##
Order Quantity: 1
c) Enter
d) Do a value assignment. Open the exercise to get some example data.
e) Done

f) Save your data.
g) Write down quotation number.___________________________
Task 2: Create a Sales Order with Reference
1. Now you create a sales order and connect it to your quotation.

Execute the right app. It can be found inside the Sales Add on area.
Enter the following inside the initial screen:
Order Type: OR
Sales Office 00
BEFORE YOU EXECUTE: Check the footer line. → Create with Reference. Enter your
Quotation number.
Note:
If you are not able to enter a Quotation number, perform a F4 help inside the
field Quot. Then select Search for Sales Document by customer and enter your
Apply the Review Availability Check Result .

Add a Cust. Reference of your choice.
Save your Sales Order.________________________
a) App Create Sales Order
b) Enter the following inside the initial screen:

Order Type: OR
Sales Office 00
BEFORE YOU EXECUTE: Check the footer line. → Create with Reference
c) Enter your Quotation number.
Note:
If you are not able to enter Quotation number, perform a F4 help inside field
Quot. Then select Search for Sales Document by customer and enter your
Copy your number.

d) Apply the Review Availability Check Result .
e) Add a Cust. Reference of your choice.
f) Save your Sales Order.
g) Write down the number. ___________________
1. Display the Stock Requirements List.

Click on Continue.
The first line displays the sales order stock and the second the sales order with item
number.
Double click the second line and check the Requirements class MMTO config. value. Don’t
close the pop-up.
Select the F9 help to display the configuration.
Close the screen.
a) Execute app Display Stock / Req. List MD04 in group Sales Add One .
b) Enter material T-FCL## for plant 1010. Click on Continue.
c) The first line displays the sales order stock and the second the sales order with item
number.
Double click the second line and check the Requirements class MMTO config. value.
Don’t close the pop-up.
Select the F9 help to display the configuration. Close (Button) the configuration.
d) Close the screen.
Task 4: MRP run: Make to Order (Multi Level)

You perform a MRP run.
1. Perform a multi level MRP run for the sales order for your forklift T-FCL##.
Execute the app MTO Planning MD50.
Enter:
Sales Order item 0010
Execute twice, until you get a result screen.

a) Make to Order: Multi Level
Execute the app MTO Planning. It can be found inside Sales Add On.

Sales Order item (10)
b) Continue or Enter button on your keyboard.
c) A warning message becomes visible.
d) Continue or Enter button on your keyboard again. MRP Run takes place.
1. Display the Stock Requirements List MD04.

Click on Continue.
Your planned order is visible. Check the detail screen. Double click the number of the
planned order.
Display the details of your planned order. Select the Display Element (F7) icon.
Inside your planned order, select the entry Component Overview.
Close the screen and move back until the stock requirements list is displayed again.
a) Execute the app Display Stock / Req. List.
b) Enter material T-FCL## for plant 1010 .Click on Continue.
c) Your planned order is visible. Check the detail screen. Double click the number of the
planned order.
d) Display the details of your planned order. Select the Display Element (F7) icon. Inside
your planned order select the entry Component Overview.
e) Close the screen and move back until the stock requirements list is displayed again.
Task 6: Convert your Planned Order into a Production Order
1. Convert your Planned order into a Production order

Inside your stock requirements list, double click again on your planned order number.
Select the button —> Prod. Ord..
The header of your Production Order opens.
a) Inside your stock requirements list, double click again on your planned order number.
b) Inside the pop-up select the button —> Prod. Ord.
2. Release and save your Production Order.

a) Select the button Release Order inside the header area.
b) A box opens and gives you information concerning not- available materials. Select the
box Release Order .
c) Save your Order.
3. Refresh your Stock / Requirements list.

Your Production Order number is visible.
Close the screen.

a) Select the Refresh button.
b) The Production Order is visible.
c) Close the screen.

LESSON SUMMARY


Unit 11
Learning Assessment
1. Can variant configuration also be used in pre-sales activities in Sales and Distribution? If
so, what should I bear in mind?
X A No, you can only work with variant configuration in sales orders.
X B Yes, you can also work with variant configuration in pre-sales activities. The
configuration always leads to the same result.
X C Yes, you can also work with variant configuration in pre-sales activities. You can
query the VBAK table in the configuration and thus define specific rules.
X D Yes, you can also work with variant configuration in pre-sales activities. However,
you cannot use the sales document tables (VBAK, VBAP, ...) in the configuration. This
is only possible in the sales order.
2. You work with make-to-order production with configuration. The planned order and
production order were created with reference to the sales order. What is important with
regard to the configured sales order item?
X A No configuration is visible in the planned order and production order.
X B In the planned order and production order, the configuration is visible but cannot
be changed.
X C The configuration is visible and can be changed in the planned order and
production order. However, dependencies are not processed here.
X D The configuration is visible and can be changed in the planned order and
production order. Object dependencies are also processed here.
X E In the planned order and production order, the component list and operation list
cannot be changed.
X F You can change the component list in the planned order. You can change the
component list and operation list in the production order.


UNIT 12 Product Structure
Lesson 1
Product Structure 424
Exercise 21: Overview: Product Structure Management 433
UNIT OBJECTIVES
● Explain Product Structure in IPPE

● Use the product structure inside Product Structure Management (PSM)

Unit 12
Lesson 1
Product Structure
LESSON OVERVIEW
Business Scenario
Within your company, you want to carry out product development with the SAP system at a
very early stage. The focus is on the functional structure and product design. Material
masters are not an issue in this early phase.
Preferably, the tool should also be used for modeling products with many variants.
LESSON OBJECTIVES
Integrated Product and Process — Engineering (IPPE)

Up to now, many companies have been dealing with the question of which master data is
required to model a configuration product, such as a car or pump. To solve this problem, your
company has been using variant configuration with a super BOM. You are now looking for an
alternative with which you can define a product configuration at an early stage without
material masters or BOMs.
You decide, therefore, to use Integrated Product Engineering (IPE). IPE provides a platform
that is suitable not only for development, but also for managing the entire product lifecycle.
IPE offers considerably more functions for modeling a product than the standard BOM.

Lesson: Product Structure
Figure 252: From Requirements to Production
Animation: From Requirements to Production

For more information on From Requirements to Production, please view the
animation in the lesson Product Structure in your online course.
A product development scenario could comprise the following sections:

Requirement structure: Contains documents, requirements, specifications, and properties for
functional, conceptual, and design structure.
Functional structure: The functional structure is the first structure of the product. It does not
normally contain material masters, but only conceptual ideas.
Concept and design structure: The concept and design structure contains alternative
concepts for individual functional structure nodes. A final decision for a concept can only be
made when the product structure is released for supply chain processes.
Product structure: The product structure contains the final concepts. It also contains
information about production planning and production.
The purpose of the product variant structure (PVS) is to create a product description that is
free of redundancy. The aim is to create not only a product structure, but also entire groups of
similar products, some of which may have a high degree of variability.
The PVS is the basis for all processes along the supply chain that use this product structure. It
is a highly integrated data model that supports efficient IT management of product
structures.
In the converter scenario, only the PVS is used as part of IPE. Once the product structure has
reached a certain development status, it is converted to a conventional bill of material. This
can then be incorporated as standard in all supply chain processes, especially in production.
Product Structure for Products with Multiple Variants

Unit 12: Product Structure
Figure 254: Product Structure for Products with Multiple Variants
Animation: Product Structure for Products with Multiple Variants

For more information on Product Structure for Products with Multiple Variants,
please view the animation in the lesson Product Structure in your online course.
The PVS comprises of three main elements:
1. The access node defines the product that you want to sell or produce.
2. The view node defines logical or function groups in your product. You do not assign
material numbers to this node.
3. The structure node defines the components that you use to produce your product.
A structure node represents a function or product group and is not a material. You can define
variants within a structure node. These variants, in turn, define non-variable parts or
(primarily) optional parts (such as different types of casing that can be used for a pump).
Selection conditions are used to specify when which variants are used.
In the early product development phases, a material master does not have to be assigned to
the variants (as is the case during prototype development). Material references should exist
before production starts, however, since material planning and goods movements cannot
take place without them.
You can design multiple, competing solutions at variant level. To do so, you create a concept
group to group together the actual concepts. You can test the individual concepts as part of
the overall conceptual design for the product and transfer (overwrite) a concept to the variant
as a result.
The product variant structure is edited in an IPE workbench.

Figure 256: iPPE Workbench
Product Structure Management
Figure 257: Product Structure Management
Animation: Product Structure Management

For more information on Product Structure Management, please view the
animation in the lesson Product Structure in your online course.
The product family is the top-level element of the product structure and defines its entry
point. A product family may have documents assigned.

● The product family has a product class associated with it, which defines the product
characteristics of all products defined by the respective product structure.
● The product family has one or more product variants associated with it.
● Product families can be classified using class type 053.
The product variant is specific representation of a product.

● It has a configurable material or a material variant assigned to it. If a configurable material
is assigned, the product variant can represent all possible configurations allowed for this
material.
● If a material variant is assigned, the product variant represents one specific product, that
is, a specific configuration of the product structure.
● A product variant may have documents assigned. Product variants can be classified using
class type 056. The product view is a structural element allowing for functional or logical
grouping of the product structure.
Product views do not have components and are ignored in the structure explosion.
● Product views can be inserted at any point in the structure – they may be subordinate to
product families, product items, and other product views and may have product items and
other product views as subordinates.
● A product view may have documents assigned. Product views can be classified using class
type 053.
Product Items
Figure 259: Product Items
The product item is an abstract representation of a component within a product structure. A

product item like the product family or view has a variant class, that is, the product class
assigned.

● A product item has the same purpose for the product structure as a BOM item has for the
BOM but does not have a material component assigned.
● Product items are used to make up a multi-level configurable product structure using part-
of relationships between the various levels. A product item has one or more product item
variants associated with. A product item may have documents assigned.
● Product items can be classified using class type 053. The product item variant is a specific
representation of a component within a product structure.
A product item variant is always assigned to a product item.

● A product item variant may have a material assigned to it. The material assignment is not
necessary in order to build up the product structure. However, the material assignment
needs to be completed prior to entering any logistics or the handover-to-manufacturing
processes.
● A product item variant may have documents assigned. A product item variant may have
CAD documents assigned.
● Product item variants can be classified using class type 056. The product class is a variant
class containing the characteristics which describe the product.
Define Object Dependencies
Figure 260: Define Object Dependencies
Animation: Define Object Dependencies

For more information on Define Object Dependencies, please view the animation
in the lesson Product Structure in your online course.
Another way of defining object dependencies is the use of a Dependency Maintenance Table.

Inside the Product Structure, you select the relevant Product Structure and the tab page
Product Item Variants. For the defined variants, you can define the object dependencies.
The Object dependency table will be visible. In this table, you will find the selected variants
and the characteristics. Now it is up to you to define the right selection conditions.
Guided Synchronization
One important link in the value chain of an enterprise which develops and manufactures
products takes the form of the interface between product development and manufacturing.
The task of product development is to develop, validate, and document a product in
accordance with certain requirements. Once the product has reached a certain level of
maturity, the product data – usually consisting of drawings, documents, material records and
parts lists – can be handed over to manufacturing. However, one recurrent observation on the
handover of the design parts list from product development (engineering BOM or eBOM) is
that the items it contains cannot be taken over one-to-one into the manufacturing parts list
(manufacturing BOM or mBOM).
Figure 262: GSS- Main Process
Animation: GSS- Main Process

For more information on GSS- Main Process, please view the animation in the
lesson Product Structure in your online course.
The process of BOM synchronization is embedded between product development and

manufacturing planning, and works as an interface between design validation on the
engineering and process design on the manufacturing side. The same process you could have
between manufacturing and after-sales. As seen on the previous slides, there are several
steps necessary to define the synchronization process.
In particular, it includes the following:
● Planning of the synchronization
● Release of the eBOM - It requires the definition of the release status, which defines and
identifies the content for the synchronization process
● Synchronization process

● Reconciliation process to solve conflicts and inconsistencies

● Save the new structure or changes
Figure 264: GSS-Main Process: PSM
Animation: GSS-Main Process: PSM

For more information on GSS-Main Process: PSM, please view the animation in
the lesson Product Structure in your online course.
Plan Synchronization for PSM to BOM is the initial process step and a prerequisite for the
synchronization PSM to BOM. To hand over a PSM to manufacturing using GSS, it is
necessary to create a synchronization unit in the Plan UI. The synchronization unit defines the
target structure in detail and describes parameters for the synchronization. You can define
more than one synchronization unit per PSM (for example, if you want to duplicate a PSM for
several plants).
The following data needs to be maintained for the synchronization process:
● Target BOM
● Owning Context
● Status of Change Number
The status of the Change Number indicates the maturity, which marks the change relevant for
the synchronization process. In the Plan UI, you can trigger then the subsequent
synchronization process.
Synchronization PSM to BOM

Figure 266: Synchronization PSM to BOM
Synchronization PSM to BOM is the main process step of GSS which can be divided into the
following:
1. An automatic synchronization of changes and determination of deviations.
2. The guided reconciliation of the structures.
Synchronization can be initial or ongoing. Engineering change numbers need to be mapped

with manufacturing change numbers. Only change numbers with a required change status are
considered during the synchronization process.
In the reconciliation workbench, you can do the following:
● Compare the source with the target BOM.
● Identify and resolve the conflicts using traffic lights indication.
● Add new components in the target structure.
● Delete obsolete components in the target structure.
● Use a clipboard to copy or store components for further processing.

Unit 12
Exercise 21
Overview: Product Structure Management
Simulation: Overview: Product Structure Management

For more information on Overview: Product Structure Management, please view
the simulation in the lesson Product Structure in your online course.
Business Scenario
Your company's management has decided to model new prototypes in the SAP system. Since
no material masters or BOMs exist for any components of the prototype, management has
decided to use the Product Structure Management (PSM). This allows you to model your new
prototypes with or without material masters.
Task 1: Product Structure Management

Display an existing structure and navigate in the PSM.
1. Execute the app Manage Product Structures, which can be found inside the area Product
Structure.
Search for T_FC.
Deselect the value for Created by.
Click on Go.
Select the node T_FC.
The Detail screen opens.
2. Which product variants, product items and views are connected to product family T_FC?
Check the next level of T_FC inside the navigation tree.
Check the tab page Product Variants on the right hand side.
3. Open the next level of the view T_FC_V1 (Drive Assy).

Open the next level of Product Item T_FC_11 and their Product Item Variants.
Scroll for the variant 91 (Diesel 30 kW) to the right and check the data. . A material is
assigned.
4. Check the details of Product item T_FC_11. Open the tab page Product Item Variants. Open
the dependencies for all variants.
Task 2: Configuration Simulation

Test the simulation.
1. Use the button Edit Simulation.

Define as follows:
Simulation name: S4105–##

Simulation description: my simulation
Enter the following as an Entry Point :
Material: T-FC60
Plant: 1010
Usage: Production
Select the button Create Configuration on the right hand side.

Do a value assignment.
Tab page Drive:

Type of Drive D — Diesel
Engine Performance 30 kW
Tab page Carrier:
Driving Seat: 1 - fix
Seat Back: 1 – Standard
Tail light: 1 - Standard
Front window: 1 — Standard
Driving mirror 2 — large
Road Equipment: 1 — mit
Schelter Width: 1000 mm
Schelter Length: 1000 mm
Color: Y — yellow
Wheels: 2 — Pneu
Tab page Lift Pole:
Mast height: 2 — middle
Fork Length: 2 — middle
Mast height in m: (Calculated) 4 m
Fork Length in m: (Calculated) 3 m
Tonnage Capacity: 2000 kg
Couterbalance Width: 777 mm
Couterbalance Length: 555 mm
Couterbalance Height: 333 mm
Couterbalance Volume: (Calculated) 0,143601 m3
Couterbalance Mass: (Calculated) 1033,929 kg

Save your Simulation.

Activate your Simulation.
Check the product structure navigation tree. For example check the Engine item. It’s
reduced to Diesel with 30 KW.
Close the screen.

Unit 12
Solution 21
Overview: Product Structure Management
Simulation: Overview: Product Structure Management

For more information on Overview: Product Structure Management, please view
the simulation in the lesson Product Structure in your online course.
Business Scenario
Your company's management has decided to model new prototypes in the SAP system. Since
no material masters or BOMs exist for any components of the prototype, management has
decided to use the Product Structure Management (PSM). This allows you to model your new
prototypes with or without material masters.
Task 1: Product Structure Management

Display an existing structure and navigate in the PSM.
1. Execute the app Manage Product Structures, which can be found inside the area Product
Structure.
Search for T_FC.
Deselect the value for Created by.
Click on Go.
Select the node T_FC.
The Detail screen opens.
a) Execute the app Manage Product Structures.
b) Search for T_FC. Deselect the value for Created by.
c) Go => Search Result
d) Select the node T_FC and click on it.
e) The Detail screen opens.
2. Which product variants, product items and views are connected to product family T_FC?
Check the next level of T_FC inside the navigation tree.
Check the tab page Product Variants on the right hand side.
a) The next level contains the following:
● Product Item T_FC_8
● View T_FC_V1

● View T_FC_V2
● View T_FC_V3
● View T_FC_V4
● View T_FC_V5
● View T_FC_V6
● View T_FC_V7
b) The product family T_FC contain the Product Variants V1 with material T-FC60
See icon "+" in column "Actions" .
3. Open the next level of the view T_FC_V1 (Drive Assy).

Open the next level of Product Item T_FC_11 and their Product Item Variants.
Scroll for the variant 91 (Diesel 30 kW) to the right and check the data. . A material is
assigned.
a) Open view T_FC_V1. 4 Product items are displayed.
● T_FC_11
● T_FC_12
● T_FC_13
● T_FC_14
b) Open Product item T_FC_11.
● Product Item Variant 91
c) Click on Product item variant 91 and scroll to the right. Material T—FV1A91 is displayed.
4. Check the details of Product item T_FC_11. Open the tab page Product Item Variants. Open
the dependencies for all variants.
a) Click on Product item T_FC_11.
b) Context menu of this product item → Display Product Item
c) Check the details.

d) Open view Product Item Variants.
e) Select the button Dependencies with the entry For all Variants.
f) Dependencies are displayed.
g) Close the Dependency Maintenance Table (DMT) with button Close.
Task 2: Configuration Simulation

Test the simulation.
1. Use the button Edit Simulation.

Define as follows:
Simulation name: S4105–##
Simulation description: my simulation
Enter the following as an Entry Point :
Material: T-FC60
Plant: 1010
Usage: Production
Select the button Create Configuration on the right hand side.

Do a value assignment.
Tab page Drive:

Type of Drive D — Diesel
Engine Performance 30 kW
Tab page Carrier:
Driving Seat: 1 - fix
Seat Back: 1 – Standard
Tail light: 1 - Standard
Front window: 1 — Standard
Driving mirror 2 — large
Road Equipment: 1 — mit
Schelter Width: 1000 mm
Schelter Length: 1000 mm
Color: Y — yellow
Wheels: 2 — Pneu
Tab page Lift Pole:
Mast height: 2 — middle
Fork Length: 2 — middle

Mast height in m: (Calculated) 4 m

Fork Length in m: (Calculated) 3 m
Tonnage Capacity: 2000 kg
Couterbalance Width: 777 mm
Couterbalance Length: 555 mm
Couterbalance Height: 333 mm
Couterbalance Volume: (Calculated) 0,143601 m3
Couterbalance Mass: (Calculated) 1033,929 kg
Save your Simulation.

Activate your Simulation.
Check the product structure navigation tree. For example check the Engine item. It’s
reduced to Diesel with 30 KW.
Close the screen.
a) Perform the exercise.

LESSON SUMMARY

Unit 12
Learning Assessment
1. You can assign Component Variants or Product Item Variant object dependencies. What
kind of object dependencies?
X A Precondition
X B Selection Condition
X C Procedures
X D Constraints


UNIT 13 Configuration Profil: Transfer
Classic (LO-VC) into Advanced
Scenario (AVC)
Lesson 1
Transfer Classic into Advanced Scenario 445
UNIT OBJECTIVES
● Configuration Profil: Transfer Classic (LO-VC) into Advanced Scenario (AVC)

Unit 13: Configuration Profil: Transfer Classic (LO-VC) into Advanced Scenario (AVC)

Unit 13
Lesson 1
Transfer Classic into Advanced Scenario
LESSON OBJECTIVES
Transfer Classic into Advanced Scenario

Business Scenario
In the past, you used your VC in a SAP ERP Central Component (SAP ECC). Now, you would
like to migrate your VC scenarios to SAP S/4HANA. Next to the classic scenario, you can
work with the advanced configuration scenario.
Transition of scenarios
Figure 268: Possible Scenarios
Animation: Possible Scenarios

For more information on Possible Scenarios, please view the animation in the
lesson Transfer Classic into Advanced Scenario in your online course.
With the new features, you can migrate existing, classic scenarios to the advanced model. You
can choose whether to use the classic models for the existing scenarios, or migrate them to
the advanced model.
For low-level configuration in the Material BOM and routing, work with the classic mode.

Figure 270: Processing Mode
Animation: Processing Mode

For more information on Processing Mode , please view the animation in the
lesson Transfer Classic into Advanced Scenario in your online course.
You can only decide which configuration mode to use for the following objects:
● Constraint net
● Object dependencies
All other objects, like BOMs and routings with the low-level configuration, characteristics and
classes, or materials, use the standard, classic scenarios.
Figure 272: Transition of Product Model

Lesson: Transfer Classic into Advanced Scenario
Before you can use a classic model with the advanced mode, several steps must be
performed.
Steps to use a Classic Model with Advanced Mode
Figure 273: Step 1: Copy LOVC into AVC
The first step is to copy a single classic configuration model.

Copy the following objects:
● Dependencies at a certain due date
● Constraints
● Dependencies joined to configuration profile
● Dependencies joined to cstic and cstic values in related classes
Copy scope:
● Dependencies can be manually selected or excluded for copy
● Reused dependencies are copied only once
Create independent dependencies (Advanced) joined to the AVC model.

Figure 274: Step 2: Advanced Syntax Checks
Animation: Step 2: Advanced Syntax Checks

For more information on Step 2: Advanced Syntax Checks, please view the
animation in the lesson Transfer Classic into Advanced Scenario in your online
course.
The second step is to check the compatibility of a single advanced configuration model (AVC):
● After transformation
● At any time while modeling
Check the following objects:

● Dependencies (AVC) at a certain due date
● Constraints
● Dependencies assigned to configuration profile
● Dependencies assigned to characteristic and characteristic values in related classes
Check scope:
● Not supported syntax / operations
● Not supported master data
● Not supported VT structure and content
Non-compatible object dependencies are listed.

Incompatible object dependencies must be checked and adapted by the modeler.

Figure 276: Step 3: Compare
The third step is compare, using report results, the variant configuration model with existing
configurations (for example, Sales Order).
The simulation environment of the advanced variant configuration can be used for further
tests of the new variant configuration model.
The differences in results between classic and advanced variant configuration model are
shown.
Use
● If the users use the classic or advanced engine to execute their configurations, they can
see differences between the two results. With this report, they can easily compare the
expected results of the configurations. The users can execute configurations of sales order
items or material variants. After the execution, the comparison table shows the differences
and the equalities between the results of the two engines.
Requirements
● This report can execute only those sales order items and material variants that were
configured with the classic profile. However, the contained configurable material should
have at least one existing valid advanced variant configuration profile too.
Selection
On the Selection screen, you should set the following parameters before executing the
comparison:
● Choose Sales Order or Material Variant.
● Set the date of the configuration.
● Enter a Sales Document with Sales Document Item (if you selected the Sales Order
option).
● Enter a Material Variant with a Plant (if you selected the Material Variant option. For Cross-
Plant Material Variants, do not fill the Plant field).

● Decide whether you want to see the differences only, or the equalities as well, in the
comparison table.
Output
After you execute the comparison, and it did not return any error message, the comparison
table appears:
● The first section shows the details of the characteristics.
● The middle section shows the results of the classic engine.
● The last section shows the results of the advanced engine.
● If a line contains any differences, a red not equal sign is shown between the results of the
classic and advanced engine. In other cases, a green not equal sign is shown.
Figure 277: Step 4: Switch LO-VC Material Variants to AVC
Animation: Step 4: Switch LO-VC Material Variants to AVC

For more information on Step 4: Switch LO-VC Material Variants to AVC, please
view the animation in the lesson Transfer Classic into Advanced Scenario in your
online course.
When you switch the LO-VC model to the advanced model, you must perform the following
steps:
1. Execute the relevant transaction VCHMOVAVR.
2. Enter the material variants of the variants, which belong to a particular material inside the
initial screen.
3. Execute, and all relevant materials are listed. Highlight the ones you would like to transfer.
4. Start the conversion.

Note:
All transfers are irreversible.
Note the following:

● Material variants are always assigned to one specific configuration profile.
● Material variants can be switched via report to the new AVC model.
● In some cases, the valuation of the material variants must be adjusted.
● The material variants are assigned to the new models of the advanced variant
configuration.
Figure 279: Step 5: Check the Transfer Result
Animation: Step 5: Check the Transfer Result

For more information on Step 5: Check the Transfer Result, please view the
animation in the lesson Transfer Classic into Advanced Scenario in your online
course.
When the transfer occurs, a log file is displayed. In this log file, every step is displayed, starting
with the model, the source and target material number, classes, change numbers, and so on.
The object dependencies are also listed.
In the end, the transfer of the model is successful.
Configuration Profile with AVC- Checks

Figure 281: Configuration Profile with AVC- Checks
With the PMEVC, you can perform advanced syntax checks for the advanced configuration. In
this case, you check the configuration profile with the attached objects.
LESSON SUMMARY

Unit 13
Learning Assessment
1. You want to carry out a transfer from a LO-VC to an AVC scenario using transaction
VCHMOVCOPY. What are the requirements? What is the result of this transaction?
X A Prerequisite is a LO-VC configuration profile with LO-VC object dependencies. The

transaction VCHMOVCOPY generates a new AVC configuration profile and new AVC
object dependencies.
X B Prerequisite is a LO-VC configuration profile with LO-VC object dependencies and

an AVC configuration profile (possibly without object dependencies). The transaction
VCHMOVCOPY generates new AVC object dependencies and assigns it to the AVC
configuration profile.
X C Prerequisite is a LO-VC configuration profile with LO-VC object dependencies and

an AVC configuration profile (possibly without object dependencies). The transaction
VCHMOVCOPY converts the LO-VC object dependencies to AVC object
dependencies, deletes it from the LO-VC configuration profile and assigns it to the
AVC configuration profile.


UNIT 14 Appendix
Lesson 1
Knowledge Base and Runtime Version 457
Exercise 22: Knowledge Base and Runtime version 465
Lesson 2
Master Data Changes with Engineering Change Management 471
Exercise 23: Master Data Changes with ECM 479
Lesson 3
Order Change Management 497
Exercise 24: Order Change Management 503
Lesson 4
Data for Exercises, Additional Slides 515
Lesson 5
Data for Exercises 531
UNIT OBJECTIVES
● Define knowledge base and runtime version

● Define configuration models in SAP S/4 HANA backend
● Understand the benefits of a knowledge base and runtime version
● Perform master data changes with Engineering Change Management (ECM)
● Define the benefits of Order Change Management
● Define a release key for OCM
● Perform OCM changes
● Read additional data which is used in our exercises
● Understand the additional slides

Unit 14: Appendix
● Get an overview of the used exercise data

Unit 14
Lesson 1
Knowledge Base and Runtime Version
LESSON OVERVIEW
Business Scenario
In variant configuration, you want to use a standard configuration methodology for all
configuration applications inside and outside the backend system.
LESSON OBJECTIVES
Knowledge Base
Figure 282: Knowledge Base: Overview
Animation: Knowledge Base: Overview

For more information on Knowledge Base: Overview, please view the animation
in the lesson Knowledge Base and Runtime Version in your online course.
Modeling is not only for the backend system.

You have set up a variant configuration model using PMEVC and the transactions for master
data maintenance (classes, material masters, BOMs, routings, variant conditions, and so on).
This model can also be used outside the backend system.
Applications are shown in the figure.

Unit 14: Appendix
In order to be able to use the model outside, a so-called knowledge base is required.
The knowledge base contains of the following:
● Knowledge Base
● Runtime Version
Model of VC: Satellites
Figure 284: Model of VC: Satellites
Animation: Model of VC: Satellites

For more information on Model of VC: Satellites, please view the animation in the
lesson Knowledge Base and Runtime Version in your online course.
Configuration Engine:
Purpose:
● This component is a core Business Solutions component in the way that it is implemented
to provide support for sales processes with interactive product configuration, for example.
The components in particular suitable for applications that focus on interaction in the
configuration process.
● The Configuration Engine is sometimes also referred to as the Internet Pricing and
Configurator (IPC) or as the Sales Configuration Engine (SCE).
Prerequisites:

Lesson: Knowledge Base and Runtime Version
● The application must be able to provide runtime versions of knowledge-base objects. The
Configuration Engine is part of the application platform that is based on SAP NetWeaver.
Integration:
● As a component of solutions such as SAP Internet Sales, the Configuration Engine can be
used for all applications that have the appropriate interfaces. The overview below shows
the Configuration Engine embedded between the knowledge base and the application or
user interface for interactive configuration.
Interfaces:
● Like other components, the Configuration Engine has a series of interfaces. To ensure that
the Configuration Engine can function as intended, knowledge and correct usage of the
following interfaces is required:
Runtime Versions of Knowledge-Base Objects:

● The Configuration Engine is essentially based on runtime versions of knowledge-base
objects. The knowledge base, collected in knowledge-base objects, results from models
that are created to describe configurable objects, their properties, and their
interdependencies. Master data maintenance is responsible for creating and updating
these models. The master data is maintained as part of the application in which the
Configuration Engine functions.
External Configuration:
● You start the Configuration Engine by calling an application. You want to create a new
configuration for a specific object type. For example, you want to configure a computer in a
sales order. The Configuration Engine receives this request with the specific object type; it
searches the knowledge base and compiles an active configuration (on the basis of all the
information and rules this contains). The application can request a copy of the active
configuration, usually at the end when all the features have been defined for the computer.
This copy, or external configuration, can also be saved by the application. In comparison,
the active configuration is volatile, that is, the Configuration Engine does not save any
results. An existing external configuration can also form the starting point of a
configuration, if, for example, the order is to be changed at the customer's request.
Pricing Engine:
● The knowledge base (the basis for the configuration) can contain keys that represent
price-relevant information with regard to the specification of a characteristic. These keys
are called variant condition keys.
SAP Solution Sales Configuration:

Use:
● SAP Solution Sales Configuration (on-premise edition) is a system that helps customers to
configure and sell solutions made of complex product combinations. In addition to selling
their own products, many businesses also sell solutions that include products, services,
and parts from other manufacturers. For example, many technology companies sell
solutions that include combinations of highly complex hardware, software, and services,
and each of these can have options or features that must be specified by a customer
during the ordering process. From a modeling perspective, each individual product can be
split into many different instances, and there are many possible relationships and
dependencies between the product instances. SAP Solution Sales Configuration (on-

Unit 14: Appendix
premise edition) provides a flexible modeling environment, which in turn simplifies the
ordering and configuration process for the customer. SAP Solution Sales Configuration
(on-premise edition) includes a configuration engine that provides the ability to perform
bottom-up configuration as well as the normal top-down approach. The system offers
innovations that make it easier to maintain configuration model data. The system is
designed to provide efficient configuration execution performance and advanced
integration capabilities.
Integration:
SAP Solution Sales Configuration (on-premise edition) is integrated with the following
systems:
● SAP Customer Relationship Management (SAP CRM) 7.0 EhP 4
● SAP ERP Central Component 6.0 EhP 8
● Hybris Commerce Suite
For information about supported versions, see SAP Note 2227752, information published on
SAP site (Supported Combinations of SAP Commerce Platform and SAP Solution Sales
Configuration).
Features:
Solution Modeling Environment:
● The system provides a modeling environment for creating complex solution models. The
solution modeling environment is based on the Eclipse Rich Client Platform (RCP) and can
be integrated with SAP CRM and SAP ERP for exchanging configuration master data.
Within the modeling environment, you define model elements such as classes and
characteristics, and then you define dependencies between your model elements. The
solution modeling environment can also be integrated with a Source Code Management
System to support collaborative modeling and allow several modelers to work on the same
model simultaneously. The solution modeling environment includes a test user interface
and a configuration engine, which allow you to test and optimize your model before
transporting it to the target sales system. For more information, see Solution Modeling
Environment.
Solution Configuration Environment:

● The application provides a configuration engine and a configuration user interface that
fully integrate with the ordering process in the SAP CRM and SAP ERP systems. You can
enter an advanced mode product (a solution) as an item in a sales document, and then
choose to configure it. The system opens the enhanced configuration user interface,
where you can enter the solution components and configure their options. When you save
the configuration, you are returned to the sales document. For more information, see
Solution Configuration Environment.
Integration with Non-SAP Sales Systems:

● SAP Solution Sales Configuration (on-premise edition) can also be integrated with non-
SAP sales systems. For more information, see Integration with Other Sales Systems.
Solution Configuration Analytics:

● SAP Solution Sales Configuration (on-premise edition) provides a set of DataSources for
extracting solution configuration data from the SAP CRM system to a data warehouse.
For more information, see Solution Configuration Analytics.

SAP Variant Configuration and Pricing:

Introduction:
● SAP Variant Configuration and Pricing can be used to build applications that enable sales
teams, customers, and channel partners to configure and price products and services
accurately and efficiently. This solution provides functionality to replicate configuration
models and pricing data of SAP ERP or SAP S/4HANA, in the SAP Cloud Platform. That
data can be used by micro services for product configuration and pricing.
Security:
● SAP Variant Configuration and Pricing relies on the platform security provided by SAP
Cloud Platform. The customers' data is strictly isolated via dedicated SAP Cloud Platform,
SAP HANA service instances. Custom-coding, for example, for variant functions or pricing
user-exits, is not allowed.
System Requirement:
● Before starting, make sure that you have all required versions of the software you are
integrating. For that please refer to SAP Note 2711932 Information published on SAP site.
To exchange data between cloud solution SAP Variant Configuration and Pricing and the
licensee’s local on-premise SAP ERP back end, SAP Variant Configuration and Pricing also
comprises the SDI Data Provisioning Agent, which is part of SAP HANA smart data
integration. The SDI Data Provisioning Agent is an on-premise application that is to be
installed and operated locally in the customer’s on-premise landscape. For data exchange
with SAP back-end systems, using a third-party runtime database obtained from SAP,
such as Microsoft SQL Server or Oracle, certain restrictions apply according to the
applicable on-premise license agreements for the third-party runtime databases. One such
restriction is that the licensee may not access these databases directly via systems or
technologies that have not been licensed specifically for use with such runtime database.
● Therefore, the corresponding SDI Data Provisioning Agent LogReader Adapters provided
with SAP Variant Configuration and Pricing may not be used to directly access, or replicate
data from, such third-party runtime databases licensed from SAP. For third-party
database licenses not obtained from SAP, please refer to the respective license
agreements on the available options for data exchange via direct database accesses.
For more information about interoperability and maintenance rules for the Data Provisioning
Agent, see SAP Note 2546811, Information published on SAP site.

Unit 14: Appendix
Figure 286: Process: Modeling and Knowledge Base
Knowledge Base with Knowledge Base Object
Figure 287: Knowledge Base

Animation: Knowledge Base

For more information on Knowledge Base , please view the animation in the
The knowledge base first requires a knowledge-base object.

The knowledge-base object collects information on which data is required for the configurable
product. In other words, the knowledge-base object is like a list of pointers to all of the
necessary data - not the data itself.
Knowledge Base with Runtime Version
Figure 289: Runtime Versions
Engineering change management for the SAP ERP system is integrated into the process of
creating a knowledge base for the IPC or SCE.
1. When you generate runtime versions, the date that you specify also applies to changes
made with engineering change management.
2. You can use transaction PMEVC or CU35 to update runtime versions. This transaction
updates the version, thereby:
● Checking for consistency
● Letting you change the date
● Overwriting the old version

Unit 14: Appendix
Animation: Runtime Versions

For more information on Runtime Versions , please view the animation in the

Unit 14
Exercise 22
Knowledge Base and Runtime version
Create a Knowledge Base and a Runtime Version
Simulation: Knowledge Base and Runtime version

For more information on Knowledge Base and Runtime version, please view the
simulation in the lesson Knowledge Base and Runtime Version in your online
course.
1. Check the data of T-FCL## inside VC Modeling Environment.

Material T-FCL##
Class Type 300
Plant 1010
Perform a test.
● Select the button Check Model.
Set the Check Options to:
● Select all, only deselect the last one. No customer specific checks.
Continue.
You get the following information: No knowledge base exists.
Continue.
If a Profile Name view appears. Double click profile T-FCL##. Click on OK.
Warning and standard messages appear.
2. Create a knowledge base for T-FCL##.

Select your material T-FCL## inside your object tree and open the context menu with the
right mouse button.
Select Create or Assign KB object.
Accept the suggested entries of the pop-up.
Save your data.
3. Create a run time version within you knowledge base object.

Select the knowledge base inside navigation tree.

Unit 14: Appendix
Note:
The knowledge base can be found between material BOM and routing.
Open the context menu and select Create Runtime Version.

Enter:
Version 01
Enter
Inside Basic Data , set the status to:
Status 1
Don’t change the other data.

Select the button Check.
A pop-up appears. Save your Runtime version.
Result screen is visible.
Move back to configuration screen.
Select the button Generate and Save of your runtime version.
Version saved.
Close your app and open Home screen again.

Unit 14
Solution 22
Knowledge Base and Runtime version
Create a Knowledge Base and a Runtime Version
Simulation: Knowledge Base and Runtime version

For more information on Knowledge Base and Runtime version, please view the
simulation in the lesson Knowledge Base and Runtime Version in your online
course.
1. Check the data of T-FCL## inside VC Modeling Environment.

Material T-FCL##
Class Type 300
Plant 1010
Perform a test.
Set the Check Options to:
● Select all, only deselect the last one. No customer specific checks.
Continue.
You get the following information: No knowledge base exists.
Continue.
If a Profile Name view appears. Double click profile T-FCL##. Click on OK.
Warning and standard messages appear.
a) Start the app VC Modeling Environment.
Enter:
Material T-FCL##
Class Type 300
Plant 1010

Unit 14: Appendix
b) Perform the tests:
c) Set the Check Options to:
● Select all, only deselect the last one.
Continue.
d) You get the following information: No knowledge base exists.

Continue.
e) If a Profile name view appears. Double click profile T-FCL##. Click on OK.
f) Warning and standard messages appear.
g) Close the list of messages (last button)
2. Create a knowledge base for T-FCL##.

Select your material T-FCL## inside your object tree and open the context menu with the
right mouse button.
Select Create or Assign KB object.
Accept the suggested entries of the pop-up.
Save your data.
a) Select your material T-FCL## inside your object tree and open the context menu with
the right mouse button.
b) Select Create or Assign KB object.
c) Accept the suggested entries of the appearing pop-up.
d) Save your data.
3. Create a run time version within you knowledge base object.

Select the knowledge base inside navigation tree.
Note:
The knowledge base can be found between material BOM and routing.
Open the context menu and select Create Runtime Version.

Enter:
Version 01
Enter
Inside Basic Data , set the status to:
Status 1

Select the button Check.

A pop-up appears. Save your Runtime version.

Result screen is visible.
Move back to configuration screen.
Select the button Generate and Save of your runtime version.
Version saved.
Close your app and open Home screen again.
a) Select the knowledge base inside the navigation tree.
b) Open the context menu and select Create Runtime Version.

Enter:
Version 01
Inside Basic Data, set the status to:
Status 1
c) Select the button Check.

This button can be found next to the text Basic Data.
A pop-up appears. Save your Runtime version. The Result screen is visible.
d) Move back to VC modeling screen.
e) Select the button Generate and Save.

It can be found next to button Check.
f) The Version is saved.
g) Close your VC Modeling app.

Unit 14: Appendix
LESSON SUMMARY

Unit 14
Lesson 2
Master Data Changes with Engineering Change
Management
LESSON OVERVIEW
Business Scenario
You want to maintain planned changes to the model of your configurable product using
engineering change management and activate them on a fixed key date.
LESSON OBJECTIVES
ECM: Engineering Change Management
Figure 292: Why Make Changes with Engineering Change Management?
Engineering change management is a central logistics function that can be used to document
changes to master data.
By using a valid-from date for the change master record, the changes become valid on a
predefined date. You can also use additional effectivity parameters.

Unit 14: Appendix
You can use engineering change management to store SAP objects (for example, BOMs,
routings) more than once. This means that the objects can be stored in all relevant change
statuses.
The changes take effect automatically at the predefined time in all areas of the logistics
process chain (for example, sales orders, material requirements planning, and shop floor and
production control).
You can use engineering change management to group changes to different SAP objects that
are affected by one change.
The time of the changes can be the same for all objects. However, you can define different
validity dates for individual objects using alternative dates.
You can create general documentation for the change and also special documentation for
each specific object change.
You can use engineering change management to fulfill your legal obligations to document
changes.
Change Documents and History
Figure 293: Change Documents and History
Animation: Change Documents and History

For more information on Change Documents and History, please view the
animation in the lesson Master Data Changes with Engineering Change
Management in your online course.
You can make object changes (for example, BOM and routing changes) in SAP either with or
without history.

Lesson: Master Data Changes with Engineering Change Management
The system generates change documents even for changes without history, but the change
statuses are not saved.
Note:
In some cases, even change documents can be suppressed. This can be set, for
example, for classification and routings.
Changes without history

These are changes that do not have to be documented because they take place during the
development stage of the product, for example. The status of the object before the change is
not saved. You can only find out about the status of the object before the change by using
change documents.
Changes with history
These are changes that must be documented because they take place during production, for
example. Both the status before and after the change is saved. The system generates change
documents. These change documents differ for some objects from those generated for
changes without history. Engineering change management in SAP enables you to document
changes completely.
Structure of a change master record
Figure 295: Structure of a Change Master Record
The change header contains a short description of the change, the valid-from date, and the
change status.
You determine which objects can be changed with the change master record by selecting the
object types.
One of the functions of the object management records is to enable you to document changes
to a specific object, for example, material BOM for fork lift T-FC99 1010 1.

Unit 14: Appendix
Alternative dates allow you to control the valid-from date of individual objects more precisely.
You can allocate accompanying documents to the change master record.
You can use classification to search for change master records.
Linked Object Types
Figure 296: Linked Object Types
Animation: Linked Object Types

For more information on Linked Object Types, please view the animation in the
lesson Master Data Changes with Engineering Change Management in your
online course.
Engineering change management is a central logistics function that can be used with the
following objects:
● Material master record
● Different BOM categories: material BOMs, document structures, equipment BOMs,
functional location BOMs, standard BOMs and sales order BOMs
● Various types of task list: routings, reference operation sets, rate routings, reference rate
routings, inspection plans, equipment task lists, functional location task lists, master
recipes and general maintenance task lists
● Documents
● Characteristics, characteristics of a class, and classification
● Variant tables, object dependencies, and configuration profile

● Substance, phrase, and dangerous goods (SAP EH&S)

● Part of the product variant structure (integrated product and process engineering [iPPE])
Figure 298: Object Type Indicators
Animation: Object Type Indicators

For more information on Object Type Indicators, please view the animation in the
lesson Master Data Changes with Engineering Change Management in your
online course.
The following indicators control processing with the change number for the individual object
types:
Active = object type for the change number is active: You must set this indicator if you want to
process objects of the object type concerned with the change number.
Object = an object management record is required for each object: If you set this indicator,
then you can only make a change to an object of the object type concerned if you create an
object management record for the object first.
MgtRec. = object management record is generated: If you set this indicator, the system
generates an object management record automatically when you process (create or change)
an object of the object type concerned with the change number. If you set this indicator, you
can make changes to all objects of the object type with the change number.
Gen new = object management record is only generated automatically when you create an
object for the first time: If you set this indicator, an object management record is only created
automatically when you create an object of the object type concerned. If you want to process
an existing object with the change number, create an object management record manually
first.
GenDial = generated in dialog: When the object management record is generated
automatically, the system branches to a dialog screen where you can enter object-specific
documentation. (Exception: sales order BOM).
Lock = object type locked for changes: You can lock and unlock the object type as required.
Object Management Records and Alternative Dates

Unit 14: Appendix
Figure 300: Object Management Records and Alternative Dates
The object management record is an independent master record in the SAP system.
However, you can create a record only in connection with a change master record. This
means that it is change number-specific.
When you enter an object in the object overview of the change master record, an object
management record is created in the background. You can create any number of object
management records for a change master record.
You can currently create object management records only for materials, BOMs, routings, and
documents.
Use the object management record to document and control changes to a specific object. You
can also define an object-related valid-from date.
The valid-from date in the change header determines when the changes made with reference
to the change number become effective. If you want to override this for an object, then you
must create alternative dates. The alternative date only exists within the change master
record. You then assign these alternative dates to one or more object management records.
As soon as an alternative date is assigned to at least one object management
Variant configuration objects

Figure 301: Variant Configuration Objects
You can maintain both a single dependency and a dependency net with reference to a change
number. When you change the basic data or the source code with reference to a change
number, the system saves both the old and the new object statuses.
You define how the configuration profile for a material or a standard network is processed in
Customizing for Variant Configuration. Under Maintain status, you determine for each
configurable object (material and standard network) whether changes to configuration
profiles with a certain status (for example, released) are stored with history.
Several views exist for the configuration object material. For other configuration objects,
there is only one view.
The table contents of a variant table can be changed with history, but the table structure
cannot.
There is a history requirement for all variant configuration objects that you have processed
with reference to a change number.

Unit 14: Appendix

Unit 14
Exercise 23
Master Data Changes with ECM
Simulation: Master Data Changes with ECM

For more information on Master Data Changes with ECM, please view the
simulation in the lesson Master Data Changes with Engineering Change
Business Scenario
You would like to install a new extra-large rear view mirror in your forklift. Therefore, you need
to adjust the data model of T-FCL## . You carry this change with history and assign a revision
level.
Task 1: Create a Change Number
1. Create a change number.

Execute the app Manage Change Master. It can be found in the area Change Handling.
Here use the button Create
Change number: T-EC##
Function: Without Release Key
Inside Change Header, enter:

Description: Changes on forklift T-FCL##
Valid from: Today’s date +2 months
Status: 01 Active
Reason for Change new extra large mirror
Select the button Object Types.

Set the object types indicator for the following:
Object: Active Object

Bill of Material: + +
Task List: + +
Material: + +
Characteristic +

Unit 14: Appendix
Object Dependencies +
Select the button Objects inside the header area.

Enter the following object keys with the following description:
Area Material:
Object keys Description:

Material: T-FV5X## New Semi finished product
T-FCL## New Revision level
You get a warning message. Your material T-FV5X## does not exist. That’s right.
Area Material BOM:
Material BOM T-FCX##, 1010, 1 Add a component
Area TL:
Task List: Task list type N , Group number Add an operation

search with F4 help and material T-
FCL## and plant 1010.
Create an element for Alternative Dates. Select the right icon inside the header.
A new screen opens. Enter:
Alternative date: Today

valid from: today’s date
Set the check box on the left hand side and click on Object assign.
Select your material T-FV5X##.
Click on the box Assign alt. date.
Save your data.
Task 2: Create a Material

Create Material T-FV5X## with a template material.
1. Execute the app Create Material (Area Product Master).

Material: T-FV5X##
Material Type: SEMI- Semi finished product

Change Number: T-EC##

Template Material: T-FV5C02
● Basic Data 1+2
● MRP 1–4
Note:
Deselect the other suggested views.
Select the following Organizational Levels:
● Plant 1010
● Copy from plant 1010
Change the description and add your group number. (Driving Mirror Extra Large ##)
Save your material.
Task 3: Change a Characteristic
1. Start the app Manage Characteristics.

Change Number : T-EC##
Inside your characteristic, add a value as follows:

Value F
Description: Extra large mirror
Save your changes.
Task 4: Change a Material BOM

Change a material BOM and add the component you created.
1. Execute app Change Material BOM (Area Product Engineering).

Material: T-FCX##
Plant: 1010
Usage: 1
Accept the warning message.

Inside the General Item Overview screen, add:

Unit 14: Appendix
Item: 0060
Component: T-FV5X##
Quantity 1
UoM PC
Now assign a new dependency.

Do the following:
Select item 0060 and press the button: Dependency Assignment.
Enter:
Dependency T_SEL_FCLX##_EQ_F
Press the Enter button on your keyboard.

A new pop-up appears. The Dependency key is suggested.
Add Change number and select the button Copy Template.
Dependency: T_SEL_FCLX##_EQ_F (copied)

Select: Copy Template
Copy template dependency: T_SEL_FCLX##_EQ_E
Change the description to:

Description: Drive mirror extra large ##
Select Dependency editor.

Change the syntax to:
T_FCLX## = 'F'
Test your syntax.

Save your syntax.
Change the status to 1– Released.
Save your BOM.
Task 5: Change a Routing

Change your routing and add a new operation for your new mirror.
1. Start the app Change Routing. in Group Product Engineering

Material: T-FCL##

Plant: 1010
Add a new operation 0830.

Enter:
Operation: 0830
Work Center: T-P00
Plant: 1010
Description: Assembly extra large mirror
Labor Time 20 Min
2. Assign a dependency.
Select the operation 0830 and navigate as follows: More → Extras → Object
Dependencies → Assignments.
Add Dependency: T_SEL_FCLX##_EQ_F
Save your routing.
Task 6: Change a Material and Add a Revision Level

Add a revision level to material T-FCL## .
1. Start the app Change Material.

Material: T-FCL##
Change number: no entry !!
Note:
At this stage you don’t enter your change number. You won’t change the whole
material - you would like to add only a revision level with a change number.
Select the viewBasic Data 1. Deselect the other.

Select the button Create Revision Level.
Add your change number T-EC##. Revision level 01 is suggested.
Save your material.
Task 7: Start a Simulation
1. Start the app Simulate Configuration Models. It can be found inside the group Variant
Configuration Modeling.
2. Search for Product T-FCL## and plant 1010.

Check the Type. You search a Product. Your product is found. Select it.
3. Do a simulation of your choice. Check the date inside header.

The date is today’s date. So no changes should be visible.

Unit 14: Appendix
Check the characteristic Extras. Is the extra large mirror value visible?
Switch from Exploded BOM to Routing. Does the new operation appear?
Switch from Routing to Super BOM. If necessary, add the Parameter— BOM Application
PP01.
Check the material BOM of T-FCX##. Is the new component T-FV5X## visible?
4. Do a simulation with a date: Today’s date + 2 months.

Click on the box Parameters.
Enter:
Configuration date: Today’s date + 3 months
Check the configuration.

If yes, please select the value.
Switch from Routing to Super BOM. If necessary add the Parameter— BOM Application
PP01.

Unit 14
Solution 23
Master Data Changes with ECM
Simulation: Master Data Changes with ECM

For more information on Master Data Changes with ECM, please view the
simulation in the lesson Master Data Changes with Engineering Change
Business Scenario
You would like to install a new extra-large rear view mirror in your forklift. Therefore, you need
to adjust the data model of T-FCL## . You carry this change with history and assign a revision
level.
Task 1: Create a Change Number
1. Create a change number.

Execute the app Manage Change Master. It can be found in the area Change Handling.
Here use the button Create
Function: Without Release Key
Inside Change Header, enter:

Description: Changes on forklift T-FCL##
Valid from: Today’s date +2 months
Status: 01 Active
Select the button Object Types.

Set the object types indicator for the following:

Task List: + +
Material: + +
Characteristic +

Unit 14: Appendix
Select the button Objects inside the header area.

Enter the following object keys with the following description:
Area Material:

Area Material BOM:
Material BOM T-FCX##, 1010, 1 Add a component
Area TL:

search with F4 help and material T-
FCL## and plant 1010.
Create an element for Alternative Dates. Select the right icon inside the header.

valid from: today’s date
Select your material T-FV5X##.
Click on the box Assign alt. date.
Save your data.
a) Execute the app Manage Change Master. It can be found in the area Change Handling.
b) Here use the button Create
c) On the initial screen, than enter:

Function: without a release key
d) Inside the change header, than enter:

Description: Changes on model T-FCL##

Valid from: Today’s date + 2 months
Change no. status: 01
e) Set the object types indicator for the following:

task List: + +
Material: + +
Characteristic +
f) Select the button Objects inside the header area.

Area Material:

Area Material BOM:
Material T-FCX##, 1010, 1 Add a component

BOM:
Area TL:

search with F4 help and material
T-FCL## and plant 1010.
g) Create an element for Alternative Dates. Select the right icon inside the header.

Valid from: today’s date

Unit 14: Appendix
Select your material T-FV5X## and click on the box Assign. alt. date.
h) Save your data.
Task 2: Create a Material

Create Material T-FV5X## with a template material.
1. Execute the app Create Material (Area Product Master).

Material: T-FV5X##
Template Material: T-FV5C02
● Basic Data 1+2
● MRP 1–4
Note:
Deselect the other suggested views.
Select the following Organizational Levels:
● Plant 1010
● Copy from plant 1010
Change the description and add your group number. (Driving Mirror Extra Large ##)
Save your material.
a) Execute the app Create Material (Area Product Master).

Material: T-FV5X##
Template Material T-FV5C02
c) Select the following views:
● Basic Data 1+2
● MRP 1–4

d) Select the following Org. Levels:
● Plant 1010
● Template plant 1010
e) Change the description to Driving Mirror Extra Large ##
f) Save your material.
Task 3: Change a Characteristic
1. Start the app Manage Characteristics.

Inside your characteristic, add a value as follows:

Value F
Save your changes.

a) Start the app Manage Characteristics inside group Classification.
b) Open the tab page Values.

Add the following value:
Value F
c) Save your changes.
Task 4: Change a Material BOM

Change a material BOM and add the component you created.
1. Execute app Change Material BOM (Area Product Engineering).

Material: T-FCX##
Plant: 1010
Usage: 1
Accept the warning message.

Unit 14: Appendix
Inside the General Item Overview screen, add:

Item: 0060
Component: T-FV5X##
Quantity 1
UoM PC
Now assign a new dependency.

Do the following:
Select item 0060 and press the button: Dependency Assignment.
Enter:
Press the Enter button on your keyboard.

A new pop-up appears. The Dependency key is suggested.
Add Change number and select the button Copy Template.

Change the description to:

Select Dependency editor.

Change the syntax to:
T_FCLX## = 'F'
Test your syntax.

Save your syntax.
Save your BOM.
a) Execute the app Change Material BOM (Area Product Engineering).

Material: T-FCX##
Plant: 1010

Usage: 1
Accept the warning message. (Date … copied from change number)
c) On the General Item Overview screen, add the following:

Item: 0060
Component: T-FV5X##
Quantity 1
UoM PC
d) Add a dependency. Do the following:

Select item 0060 and select the header entry: Dependency Assignment.
Insert:
Enter
Enter .
e) A new pop-up (Create Dependency) appears.

Here insert:

Not Enter: Use Button Copy Template
Enter
f) Inside Basic Data, change the description to:

Inside Dependency editor , change the syntax to:

T_FCLX## = 'F'
Test your syntax.

Save your syntax.

Unit 14: Appendix
g) Save your dependency.
h) Save your BOM.
Task 5: Change a Routing

Change your routing and add a new operation for your new mirror.
1. Start the app Change Routing. in Group Product Engineering

Material: T-FCL##
Plant: 1010
Add a new operation 0830.

Enter:
Operation: 0830
Work Center: T-P00
Plant: 1010
Labor Time 20 Min
a) Start the app Change Routing. in Group Product Engineering

Material: T-FCL##
Plant: 1010
Enter
Accept the warning message. (...date is overwritten from the change number)
c) Add a new operation 0830.

Enter:
Operation: 0830
Work Center: T-P00
Plant: 1010
Labor Time 20 MIN
2. Assign a dependency.
Select the operation 0830 and navigate as follows: More → Extras → Object

Add Dependency: T_SEL_FCLX##_EQ_F

Save your routing.
a) Assign a dependency.
Select the operation and navigate as follows:More → Extras → Object
Add Dependency: T_SEL_FCLX##_EQ_F.
Note:
This dependency was created inside your material BOM.
b) Save your routing.
Task 6: Change a Material and Add a Revision Level

Add a revision level to material T-FCL## .
1. Start the app Change Material.

Material: T-FCL##
Change number: no entry !!
Note:
At this stage you don’t enter your change number. You won’t change the whole
material - you would like to add only a revision level with a change number.
Select the viewBasic Data 1. Deselect the other.

Select the button Create Revision Level.
Save your material.
a) Start the app Change Material.

Material: T-FCL##
Caution:
Don’t enter your change number.
c) Select the view Basic Data 1. Deselect the other.
d) Inside the Basic Data 1 view, select the button Create Revision Level (button right
behind description).
e) Save your material.

Unit 14: Appendix
Task 7: Start a Simulation
1. Start the app Simulate Configuration Models. It can be found inside the group Variant
Configuration Modeling.
2. Search for Product T-FCL## and plant 1010.

Check the Type. You search a Product. Your product is found. Select it.
3. Do a simulation of your choice. Check the date inside header.

Switch from Routing to Super BOM. If necessary, add the Parameter— BOM Application
PP01.
a) Check the date inside header.
b) Check the characteristic Extras. Is the extra large mirror value visible?
No.
c) Switch from Exploded BOM to Routing. Does the new operation appear?
No operation 0830 is visible.
d) Switch from Routing to Super BOM.

If necessary, add the Parameter— BOM Application PP01.
No.
4. Do a simulation with a date: Today’s date + 2 months.

Click on the box Parameters.
Enter:
Configuration date: Today’s date + 3 months
Check the configuration.

If yes, please select the value.
Switch from Routing to Super BOM. If necessary add the Parameter— BOM Application
PP01.
a) Check the date inside header.
b) Check the characteristic Extras. Is the extra large mirror value visible?
Yes. The Extra large mirror is visible.
Select this value.

c) Switch from Exploded BOM to Routing. Does the new operation appear?
Yes. Operation 0830 is visible.
d) Switch from Routing to Super BOM.

Yes, the component is visible.
e) Close the simulation.

Unit 14: Appendix
LESSON SUMMARY

Unit 14
Lesson 3
Order Change Management
LESSON OVERVIEW
Business Scenario
Planned changes to master data can refer to production orders that have already been
created.
Changes to sales orders that are already in production should also be possible. Therefore, you
want to use OCM.
LESSON OBJECTIVES
OCM: Order Change Management — Overview
Figure 303: OCM –Why? When? Who?

Unit 14: Appendix
Figure 304: OCM: Prerequisites for Change Process
To use engineering change management successfully, the prerequisites above must be

fulfilled.
The overall change profile is used to control in detail whether changes are allowed.
The overall change profile comprises three subprofiles for controlling changes to PP master
data, sales orders, and assembly processing.
These profiles are maintained in Customizing (Production Orders → Operations →
Engineering Change Management).
The overall change profile must be assigned to individual material master records.
If changes made to a sales order item are involved in OCM engineering change management,
the requirements class (Customizing for Sales and Distribution) must be prepared
accordingly.
Animation: OCM: Prerequisites for Change Process

For more information on OCM: Prerequisites for Change Process, please view the
animation in the lesson Order Change Management in your online course.

Lesson: Order Change Management
OCM: Process Sales Order
Figure 306: OCM: Sales Order Change Process
Animation: OCM: Sales Order Change Process

For more information on OCM: Sales Order Change Process, please view the
Required changes to a sales order automatically generate a planned change.

Relevant changes in this process can include:
● Change to assigned characteristic values (variant configuration)
● Change to BOM explosion number
● Change master records that are:
Assigned to the sales order (direct assignment) –
Valid for this sales order (parameter effectivity)
In this process, the required changes are determined by comparing the objects in the active
production order and a simulated production order.
This means that a simulated production order is always required. This is not operationally
effective.
When you start to determine changes, the active production order is locked for changes.

Unit 14: Appendix
To check whether changes are allowed, the change profile in the material master is checked.
This controls the generation of information messages, warning messages, and error
messages.
When you start to check changes, the active production order is locked for entry of actual
data.
The change process shown in the graphic is completed by these functions:
● Confirmation of changes (optional)
● Deletion of temporarily generated data objects (such as planned changes and determined
changes)
No changes are generated for planned orders and purchase orders.
OCM: Master Data Changes
Figure 308: OCM: Master Data Change Process
Animation: OCM: Master Data Change Process

For more information on OCM: Master Data Change Process, please view the
The change process for master data covers only changes to: bills of material (material BOMs,
sales order BOMs, and WBS BOMs) and routings.
When you release a leading change master record, the system automatically creates a
planned change for the change master record.

On the basis of the planned changes for change master records, the production orders
affected by changes are determined in an intermediate step, and planned changes are
created for the orders found in this way.
The required changes (change instructions) are determined in a multilevel process in the
form of “change objects” (core orders). See also the slide on “Change Objects”.
When you start to determine changes, the active production order is locked for changes.
To check whether changes are allowed, the change profile in the material master is checked.
This controls the generation of information messages, warning messages, and error
messages.
OCM: Changes for Assembly orders
Figure 310: OCM: Change Management in Assembly Orders
Animation: OCM: Change Management in Assembly Orders

For more information on OCM: Change Management in Assembly Orders, please
view the animation in the lesson Order Change Management in your online
course.
Required changes to a sales order automatically lead to a change in the assembly order.

Unit 14: Appendix

Unit 14
Exercise 24
Simulation: Order Change Management

For more information on Order Change Management, please view the simulation
in the lesson Order Change Management in your online course.
Business Scenario
Your customer has requested a change to the original configuration of the sales order that
was created in a previous unit. Since the production order has already been released and
open purchase orders exist for this sales order item, it is not possible to read the PP master
data. You need to determine how changes to the configuration may affect these open orders.
Task 1: Check the Material

To perform this task, you have to add an overall profile. This profile connects you sales order
changes with the operations and components of your production order. Are changes possible
depending on the actual situation of your production order?
1. Check your material master record for T-FCL## to be sure that the overall profile P00001
is assigned on the work scheduling view.
Task 2: Work with the Stock Requirements List and Change your Sales Order
Inside your stock requirements list, your sales order and production order are available.
1. Change the sales order by selecting a different characteristic value for the forklift engine,
performance, and seat.
Open the app for the Display Stock / Req. List MD04.
Enter:
Material: T-FCL##
Plant: 1010
Execute.
Your sales and production order are visible.
2. Change the value assignment of your sales order.

Perform a double click on the sales order number. A pop-up appears. Now select the right
button to change your sales order.
Inside your sales order, set the check box of your item and select the button Item Details:
Configuration.
A pop-up appears. A production order is available. Continue.

Unit 14: Appendix
Change the following characteristics and enter the new values:

Driving Seat: rotable
Tonnage Capacity: your choice
Click on Done.
Save your Sales Order.
Write down again your sales order number: __________________
Write down your production order number: _______________
3. Optional: Check the components list of your production order.
Task 3: Time Ticket for Production Order

You stay inside your stock requirements list. Create a time ticket for your production order. In
this exercise, you don’t execute an app - you work with the OK code you made visible inside
header area.
1. Check your order number.
2. Execute the transaction CO11N. Combine it with /N.

Use the OK code field.
3. Enter Time Ticket for the Production Order.

Order: your order number
Sequence 0
Operation: 0100
Save your time ticket.
Task 4: First Part of OCM Process: COCM

In this exercise, you don’t execute an app - you work with the OK code you made visible inside
header area.
1. Execute the transaction COCM inside the OK code field. Don’t forget to combine the
transaction with /N.
Search for the initiating objects.
Set the check box for Sales Order.
Enter your sales order number. You wrote it down in your last task.
Click on Execute.
2. A new screen opens.

Your Sales Order is visible.
Set the check box on the left hand side and tick on the box Search for Procurement
Element. It’s the first icon. As a result, your production order is displayed.

Set the check box on the left hand side of your production order and select the box
Procurement Element.
Now the connection between your sales and production order is established.
Task 5: Second Part of OCM Process: COCM1
1. Execute the transaction COCM1 to continue the process. Don’t forget to combine the
Set the check box for production order. Enter your production order number. Execute.
2. Execute the Process Steps: Create Simulation Order and Determine Changes.
Do the following:
Set the checkbox for your production order line.
Click on “Execute the Process Steps”.
A pop-up appears.
Set the boxes for Create Simulation Order and Determine Changes.
The first step can be used to create a simulative production order, where you would be
able to check the components list and the configuration.
But we assume that everything goes well. Therefore, you directly determine the changes.
Check the determined changes and select the box Changes.
A new screen opens, which explains the upcoming changes to your production order.
Click on Exit.
3. Execute the Process Step: Check Changes.

Do the following:
Set the check box for your production order line.
Click on Execute the Process Steps.
A pop-up appears.
Set the box for Check Changes.
Select the box Changes.
A new screen opens, which explains in detail whether the changes can take place or not.
Inside the material you defined an overall profile which connect your sales order changes
with the production order, what is allowed, and what is not.
Save and Exit.
4. Execute the Process Step: Change Original Order.

Do the following:
A pop-up appears.
Set the box for Change Original Order.
A new screen opens, which explains in detail whether the changes happened or not.

Unit 14: Appendix
All changes took place.

Exit.
Task 6: Check your Production Order
1. Check your production Order.

Open the app for the stock requirements list.
Enter:
Material: T-FCL##
Plant: 1010
Execute.
Your Production Order is visible. Double click on the order number.
Open your order in change mode.
2. Open the components view and accept the changes.

Select the button components.
To confirm the changes, do the following:
● Select all components.
● Navigate: More → Component → Change Action → Confirm
● Deselect all components.
Some components are grayed out, depending on your sales order changes.
Open again header of your production order.
3. Open the operations view and accept the changes.

Select the button operations.
● Select all operations.
● Navigate: More → Operation → Change Action → Confirm
● Deselect all operations.
4. Save your Production Order.

Save and close the production order.
5. Close the stock requirements list.
6. Open the home screen.

Unit 14
Solution 24
Simulation: Order Change Management

For more information on Order Change Management, please view the simulation
in the lesson Order Change Management in your online course.
Business Scenario
Your customer has requested a change to the original configuration of the sales order that
was created in a previous unit. Since the production order has already been released and
open purchase orders exist for this sales order item, it is not possible to read the PP master
data. You need to determine how changes to the configuration may affect these open orders.
Task 1: Check the Material

To perform this task, you have to add an overall profile. This profile connects you sales order
changes with the operations and components of your production order. Are changes possible
depending on the actual situation of your production order?
1. Check your material master record for T-FCL## to be sure that the overall profile P00001
is assigned on the work scheduling view.
a) Execute the app Change Material and enter the number T-FCL##.
b) Check the work scheduling view for plant 1010.

Overall profile P00001 is assigned.
c) Close your material.
Task 2: Work with the Stock Requirements List and Change your Sales Order
Inside your stock requirements list, your sales order and production order are available.
1. Change the sales order by selecting a different characteristic value for the forklift engine,
performance, and seat.
Open the app for the Display Stock / Req. List MD04.
Enter:
Material: T-FCL##
Plant: 1010
Execute.
a) Execute the app for the stock requirements list.
2. Change the value assignment of your sales order.

Unit 14: Appendix
Perform a double click on the sales order number. A pop-up appears. Now select the right
button to change your sales order.
Inside your sales order, set the check box of your item and select the button Item Details:
Configuration.
A pop-up appears. A production order is available. Continue.
Change the following characteristics and enter the new values:
Click on Done.
Save your Sales Order.
Write down again your sales order number: __________________
Write down your production order number: _______________
a) Perform a double click on the sales order number.
b) A pop-up appears. Now select the right button to change your sales order.
c) Inside your sales order, set the check box of your item and select the button Item
Details: Configuration.
d) A pop-up appears. A production order is available. Continue.
e) Change the following characteristics and enter the new values:

f) Click on Done and save your Sales Order.
g) The system jumps back to the Stock / Requirements List.
h) Write down again your sales order number: __________________
i) Write down your production order number: _______________
3. Optional: Check the components list of your production order.

a) Double click the order number.
b) Inside the pop-up, select the button Display Element.
c) Inside the production order, select the button Components.

Your unchanged components list is visible.
d) Leave the screen.
Task 3: Time Ticket for Production Order

You stay inside your stock requirements list. Create a time ticket for your production order. In
this exercise, you don’t execute an app - you work with the OK code you made visible inside
header area.

1. Check your order number.

a) Production Order Number: __________
2. Execute the transaction CO11N. Combine it with /N.

Use the OK code field.
a) Optional: make the OK Code field visible.
Navigate as follows: More → Gui Actions and Settings → Settings. Open the area
Interaction Design and set the check box for Show OK Code Field.
b) Enter T-Code: /NCO11N
Note:
If necessary: combine it with /N to start a new transaction.
3. Enter Time Ticket for the Production Order.

Order: your order number
Sequence 0
Operation: 0100
Save your time ticket.

a) Enter production order number, sequence 0 and operation 0100.
b) Enter
c) Save your time ticket.
Task 4: First Part of OCM Process: COCM

In this exercise, you don’t execute an app - you work with the OK code you made visible inside
header area.
1. Execute the transaction COCM inside the OK code field. Don’t forget to combine the
Search for the initiating objects.
Set the check box for Sales Order.
Enter your sales order number. You wrote it down in your last task.
Click on Execute.
a) Execute transaction /NCOCM inside the OK code field of your SAP Fiori Launchpad.
Enter it inside your transaction code field of your SAP Fiori Launchpad.
b) Set the check box for Sales Order. Enter your sales order number.
You wrote it down in your last task.
Click on Execute.
2. A new screen opens.

Your Sales Order is visible.

Unit 14: Appendix
Set the check box on the left hand side and tick on the box Search for Procurement
Element. It’s the first icon. As a result, your production order is displayed.
Set the check box on the left hand side of your production order and select the box
Procurement Element.
Now the connection between your sales and production order is established.
a) Set the checkbox next to your sales order number.
b) Select the icon Search for Procurement Element.

The connection between your sales and production order is established.
Task 5: Second Part of OCM Process: COCM1
1. Execute the transaction COCM1 to continue the process. Don’t forget to combine the
Set the check box for production order. Enter your production order number. Execute.
a) Execute the following transaction inside OK code field: /NCOCM1.
b) Inside the initial screen, set the box for production order.
c) Enter your production order number and click on Execute.
2. Execute the Process Steps: Create Simulation Order and Determine Changes.
Do the following:
Set the checkbox for your production order line.
Click on “Execute the Process Steps”.
A pop-up appears.
The first step can be used to create a simulative production order, where you would be
able to check the components list and the configuration.
But we assume that everything goes well. Therefore, you directly determine the changes.
Check the determined changes and select the box Changes.
Click on Exit.
a) Set the check box for your production order line.
b) Click on Execute the Process Steps (= 1. button).
c) A pop-up appears.
d) Check the determined changes and select the box Changes.

e) Click on Exit.
3. Execute the Process Step: Check Changes.

Do the following:


A pop-up appears.
A new screen opens, which explains in detail whether the changes can take place or not.
Inside the material you defined an overall profile which connect your sales order changes
with the production order, what is allowed, and what is not.
Save and Exit.
a) Set the checkbox for your production order line.
b) Click on Execute the Process Steps.

A new screen opens, which explains in detail whether the changes can take place or
not.
e) Save and Exit.
4. Execute the Process Step: Change Original Order.

Do the following:
A pop-up appears.
Set the box for Change Original Order.
All changes took place.
Exit.
a) Set the check box for your production order line.
b) Click on Execute the Process Steps.
Set the box for Change Original Order. .

e) All changes took place.
f) Exit.
Task 6: Check your Production Order
1. Check your production Order.

Unit 14: Appendix
Open the app for the stock requirements list.

Enter:
Material: T-FCL##
Plant: 1010
Execute.
Your Production Order is visible. Double click on the order number.
Open your order in change mode.
a) Execute the app for the stock requirements list.
Your Production Order is visible.
b) Double click the order number.
c) Select the change button.
2. Open the components view and accept the changes.

Select the button components.
● Select all components.
● Navigate: More → Component → Change Action → Confirm
● Deselect all components.
a) Select all components.
b) Navigate: More → Component → Change Action → Confirm
c) Deselect all components

d) Open the header of your production order again.
3. Open the operations view and accept the changes.

Select the button operations.
● Select all operations.
● Navigate: More → Operation → Change Action → Confirm
● Deselect all operations.
a) Select all operations.
b) Navigate: More → Operation → Change Action → Confirm

c) Deselect all operations.

Some operations are grayed out, depending on your sales order changes.
d) Open again header of your production order.
4. Save your Production Order.

Save and close the production order.
a) Select the right button.
5. Close the stock requirements list.
6. Open the home screen.

Unit 14: Appendix
LESSON SUMMARY

Unit 14
Lesson 4
Data for Exercises, Additional Slides
LESSON OVERVIEW
LESSON OBJECTIVES
Data for Exercises, Demo Example
Figure 313: Exercise Data: Material BOM and Characteristics
Exercise Data: Routing

Unit 14: Appendix
Figure 314: Exercise Data: Routing
Animation: Exercise Data: Routing

For more information on Exercise Data: Routing , please view the animation in
the lesson Data for Exercises, Additional Slides in your online course.
Trainer Data: Routing
Figure 316: Trainer Data: Routing

Lesson: Data for Exercises, Additional Slides
AVC Example
Figure 317: AVC Example: Planned + Production Order without BOM Explosion
Figure 318: AVC Example: Planned + Production Order with BOM Explosion
AVC / LO-VC Scenario Sales Order, Order BOM and Planned and Production Order

Unit 14: Appendix
Figure 319: AVC / LO-VC Scenario Sales Order: Order BOM with Planned and Production Order
LO-VC Example: Planned + Production Order without BOM explosion
Figure 320: LO-VC Example: Planned + Production Order without BOM Explosion

DB Tables for VC
Figure 321: Data Base Tables for VC (1)
Animation: Data Base Tables for VC (1)

For more information on Data Base Tables for VC (1), please view the animation
in the lesson Data for Exercises, Additional Slides in your online course.
MARA General material data

MARC Plant data for material
CUCO Master data table for configuration profiles
VBAP Item data for sales document
INOB Assignment of an internal number to any object
MAST Link between material and bill of material
KDST Link between sales order item and bill of material
AUSP Values assigned to characteristics
KSSK Assignment table: object to class
CUOB Assignment of object to dependencies
STPO BOM items
CABN Master data for characteristics
KLAH Master data for class header
KSML Assignment of characteristics to classes
CAWN Master data for characteristic values
CUEX Dependency compilation

Unit 14: Appendix
CUKB Administrative information on dependency maintenance

CUKN Dependency source code base for variants / configuration
Animation: Data Base Tables for VC (2)

For more information on Data Base Tables for VC (2), please view the animation
in the lesson Data for Exercises, Additional Slides in your online course.

IBIB IBase administrative data

IBIN Data of an instance version
IBINT Instance description
IBST Root relationship and is_part_of relationship(Parent and Root)
IBINVALUES Assignment of a characteristic value to an instance
IBINOWN Owner of root instance and therefore of IBASE(for example, sales order item)
IBINOBS Instance observer (for example, follow-up documents for sales order, such as
production order)
IBSTREF BOM reference to an is_part_of relationship / instance
IBSYMBOL Characteristic value (single value or interval)

Unit 14: Appendix
Configuration Profile: Additional slides
Figure 326: Basic Data
Figure 327: Configuration Initial Screen

Figure 328: Configuration Profile
Animation: Configuration Profile

For more information on Configuration Profile, please view the animation in the
lesson Data for Exercises, Additional Slides in your online course.
The use of filters lets you restrict the explosion of BOMs in high-level configuration.
Hint:
The filters apply to all high-level configuration, so components that are not
displayed because of the filter are ignored in both the sales order and in order
BOM maintenance.
The BOM explosion in high-level configuration can be restricted by the explosion level in the
configuration profile and the definition of BOM applications assigned to the configuration
profile, as well as by filters.

Unit 14: Appendix
Figure 330: Configuration Profile – User Interface
Configuration - Browser
The configuration browser lets you navigate around the configuration structure, and at the
same time displays the value assignment screen for the selected material, so that you can
enter values.
The configuration browser thereby provides the functions of the configuration structure
screen and value assignment screen, so you can only select the configuration browser if you
have not selected these screens.
Settings
● Can be defined in the configuration profile. They are then saved for the specific
configuration profile. These settings have the lowest priority.
● Can be defined on the value assignment screen. If you save these settings, they are saved
for your user for all configuration profiles. These settings have a higher priority.
● Settings that you define on the value assignment screen and do not save are known as the
current settings.
These settings have the highest priority.
Note:
However, you can switch between the three different settings at any time
(provided that they exist).
Configuration Simulation

Figure 331: Configuration Simulation
Configuration Profile: Order BOM
Figure 332: Configuration Profile: Order BOM
Configuration Profile: Scenarios

Unit 14: Appendix
Figure 333: Configuration Profile: Scenarios
Single-level BOM explosion for the header material.

In other words, the (single-level) BOM of the material is exploded. The BOM explosion stops
after this. Any configurable assemblies in this BOM can be configured, provided that their
configuration profiles allow it.
Single-level BOM explosion for configurable assemblies according to the functionality above.
The prerequisite for this is that the material above the assembly has a multilevel configuration
scenario and its BOM has been exploded.
Overview: Combination of scenarios
Figure 334: Overview: Combination of Scenarios
Configuration Profile: Details of Interface Design

Figure 335: Configuration Profile: Details of Interface Design
Additional Slides: Item types
Figure 336: Transfer of Requirements and Pricing at Header Level (1)
If the immediately superior configurable material has item category TAC, a subordinate
configurable material with item category group 0002 is assigned item category TAE. This
means that the material is not relevant to pricing and transfer of requirements. Components
with item category group NORM also have item category TAE.

Unit 14: Appendix
Figure 337: Transfer of Requirements and Pricing at Header Level (2)
Animation: Transfer of Requirements and Pricing at Header Level

For more information on Transfer of Requirements and Pricing at Header Level,
please view the animation in the lesson Data for Exercises, Additional Slides in
your online course.
If the immediately superior configurable material has item category TAC, a subordinate
configurable material with item category group 0004 is assigned item category TAE.
Components with item category group NORM also have item category TAE. Only the superior
material is involved in pricing and transfers requirements.
Transfer of Requirements and Pricing at Component Level

Figure 339: Transfer of Requirements and Pricing at Component Level (1)
Item category group 0004 is maintained for the configurable material. The BOM for the
material is made up of finished products or trading goods. These materials have item
category group NORM.
In the sales order, the configurable material has item category TAM in the sales order and is
not relevant to pricing or transfer of requirements.
The subordinate order items have item category TAN. Order items with this item category
transfer requirements and are relevant to pricing.

Unit 14: Appendix
If the superior configurable material has item category TAM, a subordinate configurable
material with item category group 0002 is assigned item category TAC. This means that the
subordinate material transfers requirements.
Components of the header material with item category group NORM have item category TAN
and do not transfer requirements. Components of subordinate configurable materials with
item category group NORM have item category TAE and do not transfer requirements.
Animation: Transfer of Requirements and Pricing at Component Level

For more information on Transfer of Requirements and Pricing at Component
Level, please view the animation in the lesson Data for Exercises, Additional
Slides in your online course.
If the superior configurable material has item category TAM, a subordinate configurable
material with item category group 0004 is also assigned item category TAM. Components
with item category group NORM have item category TAN and are relevant to requirements
and pricing.
LESSON SUMMARY

Unit 14
Lesson 5
Data for Exercises
LESSON OVERVIEW
LESSON OBJECTIVES
Exercise data
All data for your exercise group is not available in the training master and therefore it is not in
the current training system.
All data for exercise group 00 and group-independent is available in the Training Master and
therefore in the current training system.
Materials
Type of Data Data Data
Your exercise group group 00
Fork Lift group ## configura- T-FCL## T-FCL00

ble
Extras group ## configurable T-FCX## T-FCX00
Counterweight T-FV3C00
Several colors T-FV5E01 red, T-FV5E02 blue , T-FV5E02 green,
T-FV5E04 yellow , T-FV5E05 black , T-FV5E06 white
Several seat units Standard,with headrest, extra long

fix: TFV5D01, TFV5D02, TFV5D03
rotable: TFV5D04, TFV5D05, TFV5D06
Several Engines Diesel: T-FV1A91 30 kW, T-FV1A92 45 kW, T-FV1A93 55 kW
Gas: T-FV1A94 25 kW, T-FV1A95 30 kW, T-FV1A96 45 kW
Electro: T-FV1A97 18 kW, T-FV1A98 25 kW, T-FV1A99 30 kW
Gear box with components T-FL200
Clutch T-FL2A00
Gear wheel T-FL2B00
Chassis with components T-FL300

Unit 14: Appendix
Carrier T-FL3A00
Frame T-FL3B00
Counterweight T-FL3C00
Extras with components T-FL800
Road equipment T-FL8A00
Rear view camera T-FL8B00
Additional lighting T-FL8C00
Rear mirror small T-FV5C01
Rear mirror large T-FV5C02
Material BOM
Header material Components

T-FCL## (plant 1010) (usage 1) T-FV3C00
class (200) T_FC_COLOR
T-FV5D01
T-FV5D02
T-FV5D03
T-FV5D04
T-FV5D05
T-FV5D06
Class(200) T_FC_ENGINE
T-FL200
T-FL300
T-FCX##
T-FCX## (Plant 1010) (Usage 1) T-FL8A00

T-FL8B00
T-FL8C00
T-FV5C01
T-FV5C02
T-FL200 (Plant 1010) (Usage 1) T-FL2A00

T-FL2B00
T-FL300 (Plant 1010) (Usage 1)
T-FL3A00
T-FL3B00

Lesson: Data for Exercises
T-FL3C00
Routing
for Material
T-FCL##
Plant: 1010
Usage: 1
Classes
(300)T_FCL##
(300)T_FC7##
(200)T_FC_COLOR
(200)T_FC_ENGINE
Characteristics

T_FCLC## Color
T_FCLD## Mast height
T_FCLE## Fork length (Group 00 with and group 99 without dependen-
cies)
T_FCLF## Tonnage Capacity (Group 00 with and group 99 without de-
pendencies)
T_FCLG## Drivers seat
T_FCLH## Seat Back
T_FCLR## Counterweight Length
T_FCLS## Counterweight Width
T_FCLT## Gegengewicht Height
T_FCLX## Extras
T_PLPO_VGW02_## Standard value 2
T_SDCOM_VKOND Variant conditions
T_STPO_MENGE Component Quantity
Dependencies

Unit 14: Appendix
Constraint net KJP_TWT-FCL##001

Constraints TAB1_##
T_CS_FCL##
Preconditions T_PRE_T_FCLD_FCLE_NE3_##
T_PRE_T_FCLD_FCLE_SPEC_##
Procedures T_PROC_COLOR_##
T_PROC_ENGINE_##
T_PROC_PLPO_VGW02_PLUS30_##
T_PROC_PRICE_##
T_PROC_SET_DEFAULT_T_FCLE_##
T_PROC_TAB_DEFAULT_T_FCLE_##
T_PROC_T_STPO_MENGE_##
Selection Conditions T_SEL_FCLD##_EQ_1, ...EQ_2, ...EQ3
T_SEL_FCLG_H##_EQ_1_1, ... EQ_1_2, ...EQ_1_3
T_SEL_FCLG_H##_EQ_2_1, ... EQ_2_2, ...EQ_2_3
T_SEL_FCLX##_EQ_A, ...EQ_B, ...EQ_C, ...EQ_D, ...EQ_E
T_SEL_T_FCLD_FCLE_SPEC_##
Variant tables
TAB1_## Allowed combination part 1

TAB2_## Proposed combinations part 2
Configuration profile
for Material T-FCL## T-FCL##

T-FCL##-MV (optional Constraint-Exercise)
for Material T-FC7XX## T-FC7XX## (optional Constraint-Exercise)
Knowledge base and runtime version
Knowledge base object T-FCL00

Runtime version 01
Variant conditions
XA## Surcharge Road Equipment

Lesson: Data for Exercises
XB## Surcharge Addotional Light

XC## Surcharge Camera
XD## Discount mirror small
XE## Discount mirror large
100KG## (Surcharge per 100 kg tonnage capacity)
LESSON SUMMARY

Unit 14: Appendix

Unit 14
Learning Assessment
1. With which app can the knowledge base object and the runtime version be generated?
X A App VC Modeling Environment = Transaction PMEVC
X B App Change Configuration Profile = Transaction CU42
X C App Simulate Configuration Models
X D App Variant Configuration Overview
2. You can change the model using engineering change management (ECM). Which objects
cannot be changed (or created) with engineering change management?
X A Class
X B Characteristic
X C Material BOM
X D Work center
X E Configuration profile
X F Object dependency
X G Variant table content
X H Variant table structure
X I Variant function and BAdIs

3. For which change process can OCM (order change management) be used?
X A Sales Order Change Process: Changes to the configuration in the sales order.
X B Master Data change process: Changes to parts list and routing included object
dependencies.
X C Master Data change process: Changes to the high level configuration
X D Change Management in Assembly Orders: Changes to the configuration in the

sales order.

Variant Configuration (With AVC) in Sap S/4Hana: Participant Handbook

Uploaded by

Copyright:

Available Formats

You might also like

Variant Configuration (With AVC) in Sap S/4Hana: Participant Handbook

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

Variant Configuration (With AVC) in Sap S/4Hana: Participant Handbook

Uploaded by

Copyright:

Available Formats

S4105

Variant Configuration (with AVC) in

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iii

1 Unit 1: Introduction to Variant Configuration

2 Lesson: Introduction to Variant Configuration

23 Unit 2: Classification Tools

24 Lesson: Characteristics Maintenance

59 Unit 3: Materials, BOMs and Task Lists

107 Unit 4: Configuration Profile

109 Lesson: Classic and Advanced Variant Configuration

133 Unit 5: Overview of Object Dependencies

135 Lesson: Use and Types of Dependencies

163 Unit 6: Object Dependencies in BOMs and Task Lists

164 Lesson: Selection Condition in BOMs and Task Lists

© Copyright. All rights reserved. v

252 Lesson: Interface Design, Characteristic Grouping and PMEVC

303 Unit 8: Dependencies for the Value Assignment Interface - 2

304 Lesson: Procedures for Value Assignment Interface

339 Unit 9: Variant Configuration in Pricing

340 Lesson: Pricing and Variant Configuration in Sales

367 Unit 10: Material Variants

368 Lesson: Material Variants

391 Unit 11: VC – Integration Logistic Chain

393 Lesson: Processes in SD

423 Unit 12: Product Structure

424 Lesson: Product Structure

445 Lesson: Transfer Classic into Advanced Scenario

vi © Copyright. All rights reserved.

457 Lesson: Knowledge Base and Runtime Version

© Copyright. All rights reserved. vii

© Copyright. All rights reserved. ix

● Give an introduction to Variant Configuration

© Copyright. All rights reserved. 1

Introduction to Variant Configuration

Figure 1: Customer — Inquiry — Quotation — Sales Order

2 © Copyright. All rights reserved.

Figure 2: Variant Configuration: Knowledge Base for Materials

Animation: Variant Configuration: Knowledge Base for Materials

The following objects make up the knowledge base of a configured material:

© Copyright. All rights reserved. 3

Figure 4: Configurable Fork Lift

Example: Configurable Forklift

4 © Copyright. All rights reserved.

Figure 5: Configurable Product, Class, Class Type

A configurable material needs a material master record to do the following:

© Copyright. All rights reserved. 5

Figure 6: Configurable Product, Class and Characteristics

Animation: Configurable Product, Class and Characteristics

6 © Copyright. All rights reserved.

Figure 8: Super BOM Fork Lift

Figure 9: Bill of Material: Fork Lift

© Copyright. All rights reserved. 7