Variant Configuration Online Documentation Part 20 (P.T.a.B. Sep. 16, 2012)

PP Variant Configuration Guide
The following Help Topics are available:
hltr~;lucJ~
For Help on Help, Press F1

Version
SAP-00001824
Version
Prepared for R/3 Release 2.2.
July 94
SAP-00001825
Copyrights
@1994 SAP AG. All rights reserved.
Neither this documentation nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of SAP AG.
SAP AG makes no warranties or representations with respect to the content hereof and specifically
disclaims any implied warranties of merchantability or fitness for any particular purpose. SAP AG
assumes no responsibility for any errors that may appear in this document. The information
contained in this document is subject to change without notice. SAP AG reserves the right to
make any such changes without obligation to notify any person of such revision or changes. SAP
AG makes no commitment to keep the information contained herein up to date.
SAP-00001826
Introduction
This section contains the following topics:
SAP-00001827
Tasks of Configuration
Products with a large number of variants have always been considered a problem. However,
despite the problems of producing individualized variants of a product, variant production offers a
happy medium between repetitive manufacturing and make-to-order production.
Variant Production
Engine
1600
1800
2000
2500
Extras
Anti-lock brakes
"Trip computer
Heated seats
...
...
~1
Transmission
4-gear
4-gear automatic
5-gear
5-gear automatic
...
Paintwork
Black
Red
Blue
Wheels
Steel wheels
Light alloy wheels
- standard
Light alloy wheels
- wide tires
"""
The above figure shows an example of a product with a large number of variants. It shows some
of the factors which influence which component parts are put into such a product. The more
factors there are to influence how a product is put together, the harder it is to plan possible variants
of the product.
Reasons for Complexity
There are various reasons for problems with variants:
When you produce products using variants, the combination of individual features of the product
can lead to vast numbers of variants. In the case of mid-range to top of the range cars, for
example, you scarcely ever produce two cars which are alike in all respects.
When you produce products using variants, there are often dependencies between the
individual features of the product. Not all combinations of features which are theoretically
possible are always allowed. There are two reasons for this. Some combinations may not be
possible for technical reasons. In a car, for example, you cannot combine any type of engine
with any set of gears. On the other hand, certain combinations will not be allowed for
marketing reasons. For example, certain colors of paintwork and upholstery can only be
ordered in the more expensive models of cars.
As you would expect, complex products require complex configuration tasks in sales and
SAP-00001828
distribution and production. However, a company selling or producing products with variants
needs to be able to perform these configuration tasks quickly and accurately. Since product
development and life cycles are becoming shorter all the time, this is no easy task.
SAP-00001829
Processing of Quotations and Orders

Sales Promotions
The procedure for processing quotations for complex products tends to conform to this general
pattern:
Entering the customers requirements and preferences
Producing a quotation configuration
Checking the quotation configuration for consistency and completeness
Editing the configuration in consultation with the customer
The aim is to achieve a balance between customer requirements, technical possibilities and the
price. This cyclical process is controlled by communication between sales and distribution and the
customer.
Configurable Objects
When you process a quotation for a complex product, usually you do not only have to configure the
product itself. The following objects may be configurable:
Product environment
Product
Price
Quotation texts
Factors in Quotation Processing
As is the case for all business processes, quotation processing involves a conflict of interests
between the factors of time, costs and quality.
Time
The timespan between the first contact with the customer and the handing over of the quotation is
now considered an increasingly important factor in competition. Fast reaction times are often a
competitive advantage for a company. Nowadays, the time taken over technical clearing often
leads to the situation whereby the lead time of a sales order is influenced to a considerable extent
by the technical clearing process as well as by production.
Costs
Sales and distribution costs depend to a great extent on the number of customer inquiries. This is
particularly true for products with variants, as it tends to be more expensive to produce a quotation
for variant products than for products of repetitive manufacturing. This is because of the extra
expense involved in clearing the product.
Quality
Incorrect sales orders can mean substantial losses for a company. As a rule, the longer it takes to
recognize an error, the more expensive it is to put it right. In manufacturing companies, the
growing tendency towards "just in time" production means that you can scarcely ever correct
configuration errors without delaying the delivery.
SAP-00001830
A contemporary solution to this problem is to use a computerized information system. You can
use it to fulfil a number of different functions.
Product Catalog
Catalogs can be used to give the customer an idea of the products and prices offered by a
company. However, if your products contain a lot of variants, conventional printed product
catalogs are not easy to use. Furthermore, the catalog may only contain a subsection of the
product spectrum on offer.
Electronic Catalog
One way of easing the workload on office-based sales personnel caused by secondary inquiries, is
to distribute an electronic product catalog to important customers for pricing and configuration,
instead of a paper version. If you do this, you need to consider the following points:
Hardware
To ensure that this medium has the widest possible distribution, the catalog software has to be
designed to run on standard PCs or workstations.
Presentation
As each catalog may form the first impression that a customer has of your company, particular
attention must be paid to the presentation of the catalog.
User-friendliness
As the user of the catalog will not be trained in using the catalog software, an electronic catalog
has to be largely self-explanatory and easy to use.
Explanation facility
As the user of the catalog software will not usually be an expert on the product being presented,
you need to explain suggested solutions and causes of errors for the configured product.
Sales Manual
A typical distribution channel for complex products is to use field sales personnel. The product
knowledge required is usually available to the salesperson in the form of a sales manual.
However, the same restrictions apply to sales manuals as to catalogs. For this reason, the vendor
usually sets up a central clearing office to ensure that quotations are consistent and complete.
Electronic Sales Manual
You can considerably reduce processing times by getting field sales personnel to deal with all your
quotations. This is made possible by using an electronic sales manual, which allows the
salesperson to access the correct products, prices and quotation texts. The requirements for this
kind of system are the same as for an electronic catalog. In addition, a configuration system for
field sales personnel needs to run on a portable PC (laptop or notebook).
Product Clearing
When you are dealing with complex products, customer inquiries have to be checked before they
are processed. This check is to establish whether the order can be accepted in the form
submitted. In the case of mechanical engineering products, the clearing office refers to the
knowledge of the engineers. This knowledge is often available as a technical description, but may
be stored in an unsystematic way. If the clearing office finds inconsistencies, they refer back to the
customer until they either come to an agreement between customer requirements and technical
SAP-00001831
possibilities or decide not to accept the order.

Electronic Product Clearing
A configurator can be used in a sales office to take over the functions of both technical clearing and
pricing. In this way, the technical possibility of a product can be checked when the order is first
entered. The result of the configuration process is either sent to the customer as a quotation or
sent to the PP system as a sales order. The following requirements are necessary for electronic
product clearing:
Explanation facility
The sales department must be able to give the customer a qualified explanation for any
inconsistencies in the configured product or for any missing items.
Integration in the central sales and distribution system
Full integration means that you only have to enter orders once, thereby reducing the possibility
of errors.
SAP-00001832
Work Scheduling
Work scheduling involves producing working documents for production (bills of material and
routings) from incoming sales orders. If you process identical sales orders manually, you do not
necessarily get identical bills of material and routings from identical orders. For production
planning and quality assurance purposes, it is desirable that such documents should be
standardized as far as possible. For these reasons, a computerized information system is clearly
the best solution for meeting the requirements of time, costs and quality.
Unlike the configuration processes carried out in the sales department, configuration in work
scheduling should ideally aim to produce bills of material and routings automatically from sales
orders.
SAP-00001833
Overview of Variant Configuration

When you are dealing with a product which has lots of variants, it is difficult to describe and
maintain data on the product. You need to describe clearly the complex relationships between the
components, whilst avoiding data redundancy. All variants of the product have to be represented
by an integrated bill of material and routing structure.
Complex products typically involve a large number of possible combinations of product features.
Taking a car as an example, the product has a number of features, such as color, type of
upholstery, or engine power, which describe the actual product which is to be manufactured and
delivered.
In the following figure, you see how a variant configuration is implemented in the SAP R/3 System.
A configurable object (in this case a car) is ordered using a sales order. This kind of product is
known as a standard product in the SAP System. In the sales order, the features of the product
are described and defined. The description of the variant in the sales order is then used as a basis
for collating the appropriate PP master data - bill of material and routing - to make the specific
variant required.
Configuration task
SAPterm8
Parts in stock
Materials
\
Instructionsfor
required
assembling
the product
!l
which
Log ofoperationsand
or determining/
P RTs are required
Car
List of parts
I
h
Ji/L g i~ ~ idh;e~ in i nq
q ~rerequired |
Color:
Engine:
Transmission
E xt ras : ....
red
1.81
automatic
Standard product
Characferistic:
Values:
green
red
1.8
2.0
A
B
Object
dependencies I
This section contains the following topic:

D.esc.r.ibJrlg..&.8.tandard.P.[.odu.c.t
SAP-00001834
Describing a Standard Product

When you enter a sales order, you describe a standard product using its features.
Describing the Features of an Object
When you describe a standard product, such as a car, features such as color, engine power and
transmission can influence how the finished product is made up. These features and their possible
values have to be defined in the SAP System, so that they can be used in variant configuration.
These features are defined as characteristics, and the possible values are defined as
characteristic values. To enable features to be selected for configuration, these characteristics
are stored in a class. This class is then linked to the standard product.
Object Master Data
The manufacture of a standard product, such as a car, requires a large number of component
parts. Not all of these parts will be required for every variant of the standard product. When you
enter a sales order, the characteristic values you enter determine which individual parts from the
complete list of parts for the standard product are required for the variant you want to produce.
This list of parts required for production is stored as a bill of material in the SAP R/3 System.
To produce a variant of a standard product, you also need instructions for assembling or
manufacturing the selected parts. First you need a list of all the operations which could be used to
produce an end product from the standard product. These operations are stored in the SAP R/3
System as a routing. Once the sales order has been entered and the characteristics of the
standard product have been defined, you know which parts and therefore which operations in the
routing are required to produce the finished product.
Object Dependencies
Usually, when you configure a standard product, not all the features or characteristic values of the
product can be combined with each other. For example, you cannot combine all colors of car with
all colors of upholstery. This also applies to parts in a bill of material and operations in a routing.
These dependencies within an object or between objects must also be defined in the SAP R/3
System, to allow you to configure objects consistently. For example, you can select the correct
items in a BOM and the correct operations in a routing. These dependencies are stored in the
SAP R/3 System as object dependencies.
SAP-00001835
Maintaining Standard Products

The first step in maintaining a product with variable attributes is to create your configurable object
as a standard product in the SAP S/3 System. This section describes how to maintain a standard
product and what points you need to note when you create a standard product.
SAP-00001836
Maintaining Data
Before you can configure variants, you have to maintain specific data in the material master. The
data to be maintained is as follows:
Basic data
Sales and distribution data
Materials planning data
Basic Information
A standard product is a product which is to be configured. A standard product is not in itself a
stockable material, because it includes all possible attributes of a product.
This is reflected in the material type. In release 2.2, if you want to create a configurable material,
you use a material type which is modelled on material type KMAT (configurable material). Only
materials of this material type can be configured.
Creating a Standard Product
To
create a standard product, proceed as follows:
1. Starting from the material master menu, choose Create special -~ Configurable mat..
You see a screen on which you enter the material number and the industry. In this case, you
do not enter a material type - the system automatically sets material type KMAT, because you
are using the Create special function.
.
In the following dialog boxes, you maintain the views and organizational levels for which you
want to create the material.
When you create your configurable material, you must maintain the following data:
Sales Data
.
On the Sales 2 screen, you have to enter the Item category group. The item category group
controls which item categories can be assigned in the sales order.
Group 0002 is defined as the default for configuration and appears automatically in this field if
you create your standard product using the Create special -~ Configurable mat. function.
Materials Planning Data

.
On the MRP 1 (materials planning) screen, you have to maintain the following three fields:
MRP group
The MRP group groups materials together from the MRP point of view to allocate specific
control parameters to them. The system default for this material type is 025.
MRP type
The MRP type is a key that determines whether and how the material is planned. To allow
materials planning to function properly, any type except ND (no planning) is allowed.
Lot size key
The lot size key is a key which determines which lot-sizing procedure the system uses within the
materials planning function to calculate the quantity of the material to be produced.
SAP-00001837
The only entry which makes sense in variant configuration is EX (exact lot size).
5. On the MRP 2 (materials planning) screen, you can maintain the following additional data:
Availability check
Check group for availability check. The value 01 (individual requirements) is set automatically
because of the material type.
Individ./collective
This indicator determines whether individual customer requirements planning is allowed for
dependent requirements. The indicator for individual requirements (set due to the material
type) means that the system displays dependent requirement quantities individually.
6. Maintain other data for your material. Other fields are not specifically relevant to standard
products, but you still have to make an entry in certain fields. For example, the sales price
required in the sales order must be maintained.
For more information on maintaining material master data, see the guide:
MM - BD: Managing Material Master Data.
Maintaining a Sales Price for the Standard Product
Once you have maintained the master record for the standard product, you have to maintain a
sales price for the standard product. To do this, proceed as follows:
1. In the sales and distribution menu, choose Conditions --> Prices
-~ Material price -~ Create.
2. Enter the number of your standard product in the Material field and the sales price in the
Amount field.
3. Save your data.
The sales price for your standard product is now maintained.
SAP-00001838
Object Master Data

In variant configuration, as described in .Oy..ery..j.ew of V..arj.ant Confjlquration. ,object master data is
used to describe the structure and manufacture of a configurable object which can be ordered in a
sales order. This object master data can be divided into two main parts:
the description of the structure of the configurable material
the description of the production process for the configurable material
The structure of a configurable material is described in the SAP R/3 System using a bill of material.
The production process for a configurable material is described using a routing.
SAP-00001839
BOMs as Object Master Data

A standard product cannot be produced as a finished product. A standard product is a product
which can be produced as a number of variants. For example, a standard product for a car does
not represent a product in itself. Once you have determined what kind of car is to be ordered or
produced, and decided which parts are required to produce this particular car, you can derive a
finished product (variant) from the standard product.
The same is true for the bill of material (BOM) for a standard product. The BOM is a list of the
components which are required to make all the variants of a standard product. This list contains a
description of each component, together with the quantity required and the unit of measure for each
component. This BOM can be used to describe all possible variants of a standard product.
Rather than creating a separate BOM for each variant of a product, you store the components for
all variants in one bill of material.
This BOM contains some parts which are required in all variants of the standard product. The
BOM also contains other parts which have to be selected according to which variant you require parts which can be used in an individual variant. For example, in a car you always need a
rear-view mirror, two side mirrors and a hooter. However, parts such as a particular model of
radio, a leather steering wheel, or a particular set of wheels are parts which are interchangeable
and can be selected according to the customers requirements.
Creating a BOM
A BOM for a standard product is the same as any other material BOM, and is created in the same
way.
To create a BOM for your standard product, proceed as follows:
1. Starting from the menu for bills of material, choose Bills of material -~ Material BOM -~ Create.
2. Enter the number of your standard product in the Material field, then enter the plant and BOM
usage.
You see the "New Material Items" collective entry screen.
3. Enter your components.
Classes as BOM Items
As of release 2.2, you can enter a class as a BOM item instead of a material. When you assign
characteristic values, no single material is selected automatically for this BOM item. Instead, the
classification function Find objects in class is called. Using this function, you can select objects
which are linked to the class you entered and copy them to your BOM. You use your own
selection criteria to find an object in a class. This means that you do not have to enter every single
material you might want to use as BOM items when you maintain the BOM. You only have to
enter the class to which suitable objects are linked as a class item.
If you enter a class as a class item in a bill of material, it can save you a lot of BOM maintenance
work when you want to include new BOM items. For example, you wanted windscreen wiper
blades from a specific company until now, but decide for some reason (perhaps because of
problems with deliveries) that you now want to purchase windscreen wiper blades from a different
vendor. Normally, you would have to enter new BOM items, but you can save time by replacing
your wiper blades item with a class item. You then link all the different wiper blades you could use
to the class you enter as an item.
Creating a Class for a Class Item
SAP-00001840
To create a class which can be used as a class item, proceed as follows:

1. Choose a class type which allows you to use materials classified with this class to be used in
configurable objects (bills of material and routings). In release 2.2, the standard class type
defined for this purpose is 200.
2. Classes of this class type contain an Additional data block, in which you can maintain additional
data for the class. The data on this screen is mainly concerned with the use of the class in
configurable objects. For example, you can determine:
whether the class can be used as a class item in BOMs at all
which item category the component determined via class selection is to have
which base unit of measure the selected component is to have in the resulting item category
whether you have to select a component linked to this class
whether you can select more than one object linked to this class.
Note
Class items are not used in materials planning in release 2.2. However, you can use class items
in 2.2 for modelling purposes for use in release 3.0. Materials linked to the class have to be
planned manually.
Automatic Selection of BOM Items using Classification
You can use two different classes in a configuration. First there is the class which contains the
configuration characteristics - the characteristics which are used to describe the variant. Second,
there may be other classes for classifying objects in the usual way. These classes can be used to
represent alternative BOM items. Under certain circumstances, class selection within a BOM
explosion will produce an unambiguous result, without your having to maintain object dependencies
for the BOM items.
To allow you to do this, the class used for configuration must have at least one of the
characteristics with assigned values which are maintained in the class used to classify BOM items.
If it does, it is possible to have the correct BOM item selected automatically when you assign
values to the characteristic during the configuration process. However, this is only possible if each
of the materials has only been assigned one characteristic value.
SAP-00001841
Routings as Object Master Data

When you describe a configurable material, as well as describing the structure of the material which parts are used in production - you need instructions on how to produce the standard product.
These instructions describe which operations are required to produce the variants of a product.
A configurable routing is a list of the operations which are required to produce all the variants of a
standard product. This routing can be used to describe any variant of a product. Instead of
having to create an individual routing for each variant of a product, you store the operations for all
the variants in one routing.
This routing consists of some operations, sequences of operations and production resources/tools
which are used in all variants of the standard product and others which are selected according to
the variant, and therefore can be used in a variant. An operation for polishing the finished car
when it leaves the production line is always required when you produce a car. However,
operations for installing and testing an air conditioning system are only required if an
air-conditioning system is selected as an extra.
Creating a Routing
A routing for a standard product is the same as any other routing and is created in the same way.
To create a routing for your standard product, proceed as follows:
1. Starting from the routings menu, choose Routings --> Routing --> Create.
2. Enter the number of your standard product in the Material field, and enter the plant.
You see the routing header general view.
3. Maintain the necessary header data.
4. Choose menu option Goto --~ Operation overview.
5. Enter your operations.
Note
The example above describes the maintenance of individual operations. You can also define
selectable sequences of operations, sub-operations and production resources/tools. For more
information on this subject, see the guide to "PP - Routings".
Once you have created a BOM and a routing for your configurable material, you can describe your
product from the point of view of configuration by storing the features of the configurable material in
the SAP R/3 System. For information on how to do this, see Eeatures of a ProduQt
SAP-00001842
Features of a Product
This section describes the features of a standard product and how these features are represented
in the SAP R/3 System. It describes how to maintain the following data in the SAP R/3 System:
Features of a (standard) product
Values for these features
It also tells you how to maintain a link between these features with their values and a standard
product, to allow you to configure the standard product.
It contains the following topics:
Ge.rm.r.aI.JIr~ f o.rmatiQ r~
SAP-00001843
General Information
When you receive a sales order for a standard product, the sales order has to describe the product
exactly as it has been ordered. As described in !r!t.rodu.(;tjo!]. this description is based on the
features of the product.
In the case of a car, for example, the product has a large number of features which need to be
described.
Variant Production
Engine
Extras
1600
1800
2000
2500
Anti-lock brakes
"Trip computer
Heated seats
...
...
~1
Transmission
4-gear
4-gear automatic
5-gear
5-gear automatic
...
Wheels
Paintwork
Black
Red
Blue
Steel wheels
Light alloy wheels
- standard
Light alloy wheels
- wide tires
"""
The above figure shows a car as an example of a standard product. You see some of the more
important features of the car, which are entered in the sales order, and which contain essential
information on how the product is put together. This information is then used in production and
work scheduling.
SAP-00001844
KFeatures of a Standard Product

The features of a standard product and the values assigned to them form a basis for the description
of a variant of a standard product. Once the production department has information on the exact
features of the product to be manufactured and the values assigned to these features, it is possible
to arrange provision of the necessary parts and plan for the necessary operations for producing the
product.
Characteristics
The features of a product are stored in the SAP R/3 System as characteristics. You have to
create a separate characteristic for each feature of a standard product which is relevant to
configuration of the product.
When you create characteristics, you can enter data which describes the features in more detail.
When you create a characteristic, you have to enter formatting and descriptive information. You
can also enter information which is relevant to configuration. For example, you can specifiy values
which can be assigned to a characteristic and other information which controls how the
characteristic appears in configuration.
Characteristic Values
Usually, each characteristic used in variant configuration will only have a certain number of possible
values. These possible values are stored in the SAP R/3 System as allowed values for a
characteristic. You can define one or more of these values as a standard value, according to
whether multiple value assignment is allowed for the characteristic concerned. The standard value
appears as a default when you configure your object, and becomes part of the variant unless you
enter a different value.
Characteristic Attributes
Once you have defined a feature as a characteristic and its values as characteristic values, you can
maintain additional data which describes the use of the characteristic in configuration in more
detail. For example, you can maintain attributes which influence how the characteristic appears in
configuration.
You can determine, for example:
whether you have to assign a value to a characteristic.
If you do not enter a value for a characteristic, the BOM components which are linked to the
characteristic may not be selected. This means that, if you explode the BOM in materials
planning, these parts may not be included.
In our example of a car, the characteristic Extras could be a characteristic for which you do not
have to make an entry. You can produce a car without any of the parts described in the
characteristic Extras.
However, you have to make an entry for the characteristic Paintwork, as you cannot supply a
car without paintwork.
whether you can assign only one value to a characteristic or several values.
In our example of a car, the characteristic Extras is a characteristic for which you could enter
several values, as shown in the following figure. This figure shows characteristics of a car with
some of their allowed values. You might want to produce a car with anti-lock brakes, a trip
computer, and heated seats, which means that you need to be allowed to assign more than one
value (multiple values) to the characteristic Extras.
SAP-00001845
However, you only want to assign one value to the characteristic Model, so only one value is
allowed.
whether you can enter an interval as a characteristic value.
For a numeric characteristic, you can define intervals as allowed values, if required.
whether negative values are allowed.
For some characteristics, such as a temperature, you can define negative values as allowed.
whether you see the allowed values for a characteristic directly on the screen during
configuration, or whether you have to request the possible entries first.
Characteristic Value Assignment I

Chn mo~ fi~Hiod emod p~o n
Valua~
Modal
1 600
1 800
2000
2500
3000
yes
no
Pai ntwo rk
Intarior
Anti-lock brakes
Air-conditioning system
Caralarrn
Cassette holder
Electricwindows
Headlarnpwasher
Heated seats
Heated side mirrors
O utsid e tern pera~ ure dis play
Sunroof
Towbar
Tripcomputer
4-gear auto ma~ic tran s rni s s ion
5-gear auto ma~ic tran s rni s s ion
black
blue
red
g ray
darkgreen
yellow
white
black rn etallic
black
red
SAP-00001846
Creating a Characteristic
To create a characteristic to describe a feature of a product, proceed as follows:
1. Starting from the classification menu, choose Characteristic -~ Create.
2. Enter a name for your characteristic in the Characteristic field and press Enter. You see the
basis data screen.
3. Enter format data for your characteristic. The data you have to enter depends on whether the
characteristic has numeric or alphanumeric format.
Maintain the other relevant data on this screen, in particular the status. Only characteristics
which have the status "released" can be used in variant configuration.
4. If required, maintain allowed values for your characteristic. To do this, choose menu option
Goto --> Allowed values.
5. Maintain your user interface data. This data determines how the characteristic is displayed in
variant configuration. To do this, choose menu option Goto --~ Interface control.
6. Enter other characteristic data as required.
7. Save your characteristic data.
8. Create characteristics as described above for all the product features you want to use in variant
configuration.
For more information on maintaining characteristics, see the MM - Characteristics Guide.
Classes
Before a characteristic can be used in variant configuration, you have to allocate it to a class. A
class in this context is a record which contains information on the characteristics to which you want
to assign values during configuration. The class forms the link between the characteristics and the
standard product.
Creating a Class for Configuration
One class contains all the characteristics which are required to describe a configurable object.
The characteristics are defined in the characteristics functions and copied to the class as they are.
However, you have the option of overwriting characteristic values and characteristic attributes in
class maintenance functions. This means that you can use the same characteristic in different
classes, but you can change individual characteristic attributes or the allowed values for each class.
For more information on this subject, see the guide to the MM - Classification System.
For variant configuration, you create a class for your confiurable object. This class is then used in
the configuration interface, so that you can enter values for the characteristics (features of the
product). The class for your configurable object (material) must have a class type which allows the
class to be used in variant configuration. In release 2.2, the standard class type 300 is defined for
configurable materials.
When you create your class, on the characteristic value assignment screen you have to enter all
the characteristics you need to describe the standard product. You have to release the class
before you can use it in configuration.
For information on how to create classes, see the guide to the MM - Classification System.
Linking a Standard Product to a Class
SAP-00001847
Before you can configure a standard product, you have to let the system know that the
characteristics in the class are to be used to describe the standard product. To do this, you need
to create a link between the configurable standard product and the class you want to use in
configuration.
To create a link between the configurable material and the class whose characteristics you want to
use in configuration, choose function Logistics -~ Central functions --> Var. configuration
--> Configurable objects --> Create.
This link between the standard product and the class also forms the link between the relevant BOM
and/or routing and the characteristics entered in the class. It is the basis for defining object
dependencies between the BOM components, operations, sub-operations, sequences of
operations and production resources/tools on the one hand and the characteristics and
characteristic values for the class on the other hand (see the following figure).
Material
Standard product
Car
Additional data for configurable objects

Standard product Class type/class
Car
300 / Car
Material
Class type/class
900 / Car
Assigned characteristic values

.
.
.
.
.~lbEngine (1600, 1800, 2000 ...)

.~Transrnission (4-gear, 4-gear automalic...)
.~aintwork (black, red...)
.~heels (steel wheels, light alloy wheels - standard...)
Extras (Anti-lock brakes, heated seats ...)
Enter the standard product in the Material field and press Enter. You see a screen on which you
can enter one or more classes which can then be used in configuration. You can link each class to
an organizational area. This means that, when you configure a standard product, a class is
selected automatically according to which application the configuration function was called from.
If you choose the Class detail function, you see another screen, on which you can enter
configuration parameters. On this screen, you can:
SAP-00001848
determine whether a start logo is displayed when you first call a configuration function. This
start logo is stored as a document in the class. The indicator for defining whether this
document is displayed is on this configuration parameters screen.
enter a status for the configuration parameters. You can only configure the standard product if
the configuration parameters have the status "released". No other parameters can be changed
from the standard in release 2.2.
SAP-00001849
Object Dependencies
This section describes the role of object dependencies in variant configuration. It explains what
object dependencies are and where you can maintain them.
It contains the following topics:
SAP-00001850
What are Object Dependencies?

This topic tells you what object dependencies are and what they are used for.
Object dependencies describe the dependencies between different objects in a configuration. In
variant configuration, object dependencies determine, for example:
which BOM items are to be used
how details in BOM items, such as the component quantity, are to be calculated
Currently, these object dependencies are described using characteristics and characteristic values.
SAP-00001851
Dependency Types
In the SAP R/3 System, there are three different types of object dependencies:
Preconditions
Selection conditions
Actions
The different tasks of these dependency types within a configuration are described below.
Preconditions
A precondition determines whether an object can be used in a configuration at all. If the
precondition is fulfilled, the object can be included in a configuration. You can decide for yourself
whether to include the object in the configuration or not.
Selection Conditions
A selection condition determines whether an object must be included in a configuration. If a
selection condition is fulfilled, the object has to be included in the configuration. You cannot
choose whether to include the object, as you can for a precondition.
Actions
An action can be used to change values assigned to characteristics within a configuration. An
action is carried out whenever the object to which it refers is included in a configuration.
Note
Since it is possible to link a characteristic to a field in an object, such as the component quantity for
a BOM item, you can also use an action to indirectly change data in fields in an object.
SAP-00001852
Use of Object Dependencies

Not all types of object dependency can be used with all configurable objects. The following table
shows which dependency types can be used for which configurable objects.
Use of dependency types
Object
Precondition
Characteristic
Characteristic
Value
X
X
Bill of materials
BOM item
Selection condition
Routing
Operation
Sub-operation
Sequence of operations
Production resource/tool
X
X
X
X
Configurable object
Action
Note
In release 2.2A, you can also define actions for objects in a routing. However, when you explode a
routing, these actions do not affect the field entries in the routing.
The three dependency types can have different effects on characteristics, BOMs and routings.
The following paragraphs describe how each dependency type affects each of these objects.
Characteristics
You can use both preconditions and selection conditions for characteristics.
Preconditions for Characteristics
You can define a precondition for a characteristic to determine when a characteristic is to appear
on the value assignment screen. A precondition means that a characteristic is only displayed on
the value assignment screen if a certain condition is fulfilled. For example, the characteristic is
only displayed if a certain value is assigned to another characteristic.
Using the car as an example, a characteristic for power steering could be displayed only if another
characteristic (such as the model) has a certain value.
By defining preconditions for characteristics and characteristic values, you can ensure that only
valid combinations of values are available in configuration and therefore only valid combinations
can be selected. This means that your configurations are consistent.
Selection Conditions for Characteristics
If you define a selection condition for a characteristic, you have to assign a value to the
SAP-00001853
characteristic during configuration if the selection condition is fulfilled.

You can use a selection condition in conjunction with a precondition. For example, if the
characteristic Power steering (1600 engine) appears when you are configuring a car (due to a
selection condition, in this example) you want to ensure that a value is assigned to this
characteristic. You can do this by defining a selection condition for the characteristic.
By defining selection conditions for characteristics, you can ensure that the configuration is
complete.
Actions for Characteristics
Actions are used to automatically assign a value to one characteristic when you assign a value to
another characteristic. You can define an action for a characteristic if:
you want a specific value to be assigned automatically to another characteristic if a value (any
value) is assigned to the characteristic for which you define an action
you want a specific value to be assigned automatically to another characteristic if a specific
value (or one of several specific values) is assigned to the characteristic for which you define an
action
As soon as you assign a value (or one of one or more specific values) to a characteristic for which
an action is defined, the action is automatically carried out.
Using the car as an example, power steering is supplied with almost all models of car. This means
that it is useful to define an action for the characteristic Power steering which assigns the
appropriate value to the characteristic.
Characteristic Values
You can define preconditions and actions for characteristic values, but not selection conditions.
Preconditions for Characteristic Values
In our example of the car, some extras (such as a certain model of radio, speed regulator, and so
on) are only available from a specific model upwards. In addition, some types of upholstery can
only be supplied with certain colors of paintwork.
By defining preconditions for characteristic values, you can define these dependencies between
characteristic values.
Actions for Characteristic Values
You can define actions for individual characteristic values. If you enter a value for which an action
is defined, the action is automatically carried out.
In a car, for example, you need a more powerful car battery if you have an air-conditioning system.
To ensure that the correct battery is selected, you can define an action, to be carried out if the
characteristic value Air-conditioning system is assigned to the characteristic Extras, which selects a
more powerful battery by assigning the appropriate characteristic value.
Other Objects
You can define either actions or selection conditions for other objects.
Selection Conditions for Other Objects
Selection conditions for objects other than characteristics and characteristic values are used to
select the items in a bill of material and the operations in a routing which are required to produce a
SAP-00001854
specific variant of a standard product.

By using selection conditions for other objects (BOM items, operations, sub-operations, sequences
of operations and PRTs in a routing) you determine that the object for which you define a selection
condition is included in the explosion of the superior object (BOM or routing). In this way, you can
determine which tires, which steering wheel, or which engine is selected in the BOM for the car, as
well as which operations are selected to produce the product.
Actions for Other Objects
You can define actions by linking a class to a standard product. This option allows you, for
example, to set default values for characteristics.
This option is particularly useful if you want to create actions for a specific standard product. The
system checks these actions alter each entry, and executes each action for which no condition is
defined or for which the condition defined is fulfilled.
Important
You can define actions on different levels. You can define an action for one characteristic value on
the characteristic value level, for several characteristic values on the characteristic level, or on the
standard product level. You therefore need to decide which level you want to create your actions
on. If you put an action on the characteristic or characteristic value level, but do not want this
action to be valid for all standard products, you need to incorporate a query in the action which
checks the standard product. However, as this is a work-intensive solution, which makes it difficult
to get an overview of the situation, we recommend that you maintain such actions on the standard
product level. This means that you maintain the action when you link the standard product to the
class.
SAP-00001855
Syntax of Object Dependencies

This topic tells you which key words can be used in object dependencies syntax.
Syntax is different for the two following types of dependencies:
Conditions (preconditions and selection conditions)
Actions
Examples are used to introduce the salient points. For a detailed, formal syntax description, see
Conditions
Preconditions and selection conditions have the same syntax. This syntax is described in this
topic.
The system recognizes three distinct objects when processing a configuration task:
the current configurable object ($ROOT), which you use as the starting point for the
configuration
the object which is currently being exploded in a configuration/BOM explosion ($PARENT)
the object which is currently being selected for the configuration ($SELF)
The syntax of conditions allows you to refer to characteristics of these objects and use these
characteristics in expressions of comparison. Expressions of comparison can contain simple
values and formulae, and can be combined with logical operators such as AND, OR, and NOT to
form complex logical expressions.
The examples of conditions below show how this works:
1. COLOR = red
2. COLOR = red and LENGTH > 100
.
The syntax $ROOT.VOLUME < 0.5 * TOTAL_VOLUME

$ROOT.VOLUME means that the value assigned to the characteristic VOLUME for object
$ROOT is to be checked, to see whether it is less than half of the value assigned to the
characteristic TOTAL_VOLUME. If you do not enter a reference to a specific object in this
form, the system takes $ROOT as the default reference object.
A condition generally consists of one or more expressions of comparison, linked together with AND
or OR operators.
Characteristics and characteristic values are a major part of conditions.
Note
In object dependencies, please note that you must refer to characteristics and characteristic values
using the language-independent form (key form).
The program does not distinguish between upper and lower case letters for key words, such as
AND, OR, and $ROOT).
Character strings used in conditions must be enclosed in inverted commas (), for example: COLOR
= red.
Comparison Operators
You can express comparisons for characteristics with numeric format using the following
comparison operators:
SAP-00001856
Convention 1
<
<=
Convention 2
=<
==
>
>=
Convention3 Meaning
LT
LE
less than
less than or equal
to
equal
to
greater than
greater than or
equal to
EQ
=>
GT
GE
For all other characteristic formats, there are only comparisons as to whether values are equal (=,
EQ) or not equal (<>, ><, NE).
Numeric expressions and comparisons are checked in the base units of the characteristics
concerned.
When you enter numbers containing decimals, please note that the only decimal point allowed is a
period (.). Any settings made in the user master do not apply.
For characteristics with numeric format only, you have the option of using intervals in conditions.
You can use the following expressions:
Expression
Meaning
< figure 1
<= figure 1
figure 1 - < figure 2
figure 1 - figure 2
> figure 1 - < figure 2

> figure 1 - figure 2
>= figure 1
> figure 1
less than figure 1

less than or equal to figure 1
from figure 1 to figure 2, whereby figure 1 is included in the interval,
but figure 2 is not
from figure 1 to figure 2, whereby figure 1 and figure 2 are included
in
the interval
from figure 1 to figure 2, whereby neither figure 1 nor figure 2 is
included in the interval
from figure 1 to figure 2, whereby figure 2 is included in the interval,
but figure 1 is not
greater than or equal to figure 1
greater than figure 1
You can include such intervals in comparison expressions using the IN operator.
Example:
LENGTH IN (300- 500)
This condition is true if the characteristic LENGTH has a value which is any number between 300
and 500. The figures 300 and 500 are part of the interval.
Example:
LENGTH IN (300 - 500, >600 - <700)
This condition is true if the characteristic LENGTH has a value which is any number between 300
and 500 or between 600 and 700. The figures 300 and 500 are part of the interval, but 600 and
700 are not.
You can also combine several intervals, or you can combine single values and intervals, as
required.
Example:
SAP-00001857
LENGTH IN (300 - 500,566,600 - <700, 1000)

Note
Please note that the entries after the IN operator must always be enclosed in brackets.
Logical Operators
You can use the following logical operators to combine expressions in conditions as required:
ANDand
OR
If you use the AND operator, both the parts of the condition which are linked by the AND operator
must be fulfilled in order for the condition to be fulfilled.
Beispiel:
LENGTH EQ 300
AND
WIDTH LT 200
This condition is true only if the characteristic LENGTH has a value of exactly 300 and the
characteristic WIDTH has any value which is less than 200.
If you use the OR operator, on the other hand, at least one of the parts of the condition which are
linked by the OR operator must be fulfilled in order for the condition to be fulfilled.
Example:
LENGTH EQ 300
OR
WIDTH LT 200
This condition is true if the characteristic LENGTH has a value of exactly 300 or the characteristic
WIDTH has any value which is less than 200.
Calculations
Within conditions, you can also carry out calculations. You can use the four basic types of
calculation:
-I-
(Addition)
(Subtraction)
(Division)
(Multiplication)
You can also use the following mathematical functions:

sin
cos
tan
exp
In
abs
sqrt
Example:
LENGTH
LENGTH
LENGTH
Sine function
Cosine function
Tangent function
Exponential function for base e
Natural logarithms
Absolute amount
Square root.
WIDTH + 4
SIN (0.5)
SIN (0.5/2)
SAP-00001858
LENGTH
SIN (SQRT(RADIUS))
Note
1. Please note that trigonometric functions
(cos, sin, tan) are to be entered in radian measurements.
2. When you enter decimal figures, please note that only
a period (.) is allowed as a decimal point.
Settings in the user master are ignored.
Special Expressions
In addition to comparison expressions, there is a range of special expressions, which can also be
combined to form complex expressions by using logical operators:
The characteristic has a value assigned to it (SPECIFIED).
The characteristic value is included in the range or values entered (IN).
The object has the entered material number (TYPE_OF)
The following examples illustrate these conditions:
1. SPECIFIED SPECIAL_COLOR (or SPECIAL_COLOR SPECIFIED)
If you defined such a condition as a selection condition for an operation in a routing, for
example, the operation would be included in the exploded routing if the characteristic
SPECIAL_COLOR had a value assigned to it (for object $ROOT) at the time of the explosion.
In this case, it does not matter what the value is.
2. POWER IN (250-350)
If you defined such a condition as a selection condition for a BOM component, for example, the
component would be included in the exploded BOM if the characteristic POWER had an
assigned value within the interval 250 to 350.
3. COLOR IN (red, yellow, green)
If you defined such a condition as a precondition for a characteristics, for example, this
characteristic would be included in the configuration if the characteristic COLOR had one of the
values red, yellow, or green, or did not have a value assigned to it.
Note
IN can also be used in negative conditions, for example NOT COLOR IN (red, yellow, green). In
this case, the condition is fulfilled if the value assigned to the characteristic is neither red, yellow,
nor green. However, you can only use conditions with NOT for characteristics where multiple
values are not allowed.
4. TYPE_OF ($ROOT, U91)
If you defined such a condition as a selection condition for a BOM component, for example, the
component would be included in the BOM explosion if the object $ROOT (the standard product
which is produced on the highest level) had material number U91.
You can use this condition wherever the object dependency is dependent on its environment: for
example, dependent on the use of a component in a specific BOM.
A selection condition such as
TYPE_OF ($ROOT, MATERIAL1)
AND
COLOR = red
SAP-00001859
means that the selection condition is only used if the standard product is called MATERIAL1.
The selection condition is ignored for all other standard products.
Actions
Actions describe activities which are to be carried out immediately after an object is selected or
immediately after a value has been assigned to a characteristic. The purpose of these actions is
to assign values to characteristics of the object currently being processed ($SELF) during
configuration. You can define additional conditions for these actions.
The following examples illustrate these actions:
1. $SELF.COLOR = red
This action assigns the value red to the characteristic COLOR for the object currently being
processed.
2. $SELF.TOLERANCE = FILL_TOLERANCE / 2, $SELF.LAND = $ROOT.LAND
This action assigns a value two different characteristics. Please note that you need to enter the
object reference $SELF to the left of the reference. If you define more than one value
assignment in one action, you separate the assignments with a comma.
3. $SELF.TESTDURATION = MACHINE LENGTH / 3 IF FILL TOLERANCE <= 5
4. $SELF.MENGE = 6 IF $ROOT.LAENGE > 200
Examples 3. and 4. show how you can formulate a conditioned reference using the key word IF.
You can use an action to set certain field values in the object concerned. The standard product for
example 4. could represent a table. Usually, four legs are produced for each table. However, if a
longer length of table is ordered, (over 200 cm), two extra legs are required to support the table
If the characteristic for which you want to set a value allows multiple values, you can set more than
one value for the characteristic. (see Example 5).
5. ($SELF.EXTRAS = anti-lock brakes,
($SELF.EXTRAS = electric windows,
($SELF.EXTRAS = air conditioning system,
($SELF.EXTRAS = driver airbag,
($SELF.EXTRAS = passenger airbag,) IF $ROOT.MODEL = action model summer 1994
In this example, several values are set for the characteristic EXTRAS if the condition is fulfilled.
~-.Q..b.#ct E).e...e#.d.e_n!e.s contains a complete description of syntax for conditions.
Note
In actions, you can only set values for the object which is currently being processed ($SELF). For
this reason, an action must always start with "$SELF.<characteristic name>".
If you make the action dependent on a condition, you can refer to other characteristics in the
structure.
With $PARENT.<characteristic name>, you refer to characteristics of the assembly which directly
contains the object you are processing.
With $ROOT, you refer to characteristics which belong to the standard product.
SAP-00001860
Maintaining Object Dependencies

You can maintain object dependencies for configurable objects either when you maintain the
individual object, or independently of any object, using the dependency maintenance functions.
Global Object Dependencies
If you want to use object dependencies for several objects, it is useful to maintain the object
dependencies separately, without linking them to an object. You can then link these global object
dependencies to the appropriate objects at a later date.
Maintaining Global Object Dependencies
You can maintain object dependencies independently of any object using the function
Logistics -~ Central functions --~ Var. configuration -~
Dependency--> Create. This function provides the following options for creating a dependency:
create dependency without a reference
create dependency using a reference
Creating a Dependency without a Reference
To create an object dependency without a reference, proceed as follows:
1. Call the Dependency -~ Create function.
2. On the initial screen, enter a name for your dependency. Confirm your entry.
3. You see the basis data screen, on which you:
enter a description of the dependency
assign a status to the dependency
This allows you to define the status for use of the dependency.
4. You can also make entries in the following fields:
Dependency group
The entry in this field is used to construct a matchcode. This field allows you to group
similar dependencies together, to help you find them again later.
Maintenance auth.
The maintenance authorization allows you to define which objects (such as BOMs,
operations) the dependency can be used in.
5. You also need to select the type of dependency (see .D....e...endenc ...T ..es )
6. You can define your dependency in the Dependencies editor function.
If you require, you can get the system to check your dependency for syntactical correctness,
using the Dependency -~ Check function.
7. You can maintain language-dependent descriptions for your dependency using the Lang-dep.
descript. function.
8. Save your entries.
Creating a Dependency with a Reference
SAP-00001861
To create a dependency using a reference to copy from, call the same function as for creating a
dependency without a reference.
On the initial screen, you see the Copy from: dataset. Here, you enter the name of an existing
dependency from which you want to copy data. If required, you can select a suitable dependency
using a matchcode.
The data in the reference dependency is copied to the dependency you are creating. You can
then edit or overwrite the data.
Linking Global Dependencies to Objects
As mentioned above, you can use global dependencies for all objects. Once you have create a
dependency, you have to link it to the object you want to use it for.
Linking Global Dependencies to Characteristics
To link a dependency to a characteristic, proceed as follows:
1. In the functions for creating or changing characteristics (for example, Characteristic --> Change
in the classification menu), enter the name of the characteristic you want to link to a
dependency. Press Enter.
2. Choose the Details --> Object dependency -->Link
function.
3. If no dependencies have yet been linked to the characteristic, enter the name of the
dependency.
If dependencies have already been linked to the characteristic, choose Edit -> New entries and
enter the name of the dependency in the Dependency field.
4. Save your data.
Linking Global Dependencies to Characteristic Values
To link a precondition to a characteristic value, proceed as follows:
1. In the functions for creating or changing characteristics (for example, Characteristic --> Change
in the classification menu), enter the name of the characteristic whose value you want to link to
the dependency. Press Enter.
2. Choose the Goto -> Allowed values function.
3. Select the value you want to link to the dependency.
4. Choose the Details -> Object dependency -->Link
function.
5. If no dependencies have yet been linked to the characteristic value, enter the name of the
dependency.
If dependencies have already been linked to the characteristic, choose Edit -> New entries and
6. Save your data.
Linking Global Dependencies to BOM Items
To link object dependencies to a BOM item, proceed as follows:
SAP-00001862
1. In the function for creating or changing a BOM, enter the number of the standard product whose
BOM items you want to link to a dependency. Enter the plant and usage.
Choose the Goto ~ Item overview ~ Material function. You see the BOM items.
2. Select one item which you want to link to a dependency.
4. Choose the Details ~ Object dependency ~Link
function.
5. If no dependencies have yet been linked to the BOM item, enter the name of the dependency.
If dependencies have already been linked to the BOM item, choose Edit -~ New entries and
6. Save your data.
Linking Global Dependencies to Operations in Routings
To link object dependencies to an operation in a routing, proceed as follows:
1. In the function for creating or changing a routing, enter the number of the routing whose
operations, sub-operations, sequences of operations or production resources/tools you want to
link to a dependency.
Choose the Goto -~ Operation overview function. You see the operations in the routing.
Note
From here, you can access other overview screens on which you can see object dependencies for
sequences of operations or production resources/tools. You can then select an object from these
overview screens, and link the object to the dependency on the detail screen, as for operations.
2. Select one operation which you want to link to the dependency.
3. Choose one of the detail screens using the Operation menu option.
4. Choose the Details ~ Object dependencies -~Link
function.
5. If no dependencies have yet been linked to the operation, enter the name of the dependency.
If dependencies have already been linked to the operation, choose Edit ~ New entries and
6. Save your data.
Maintaining Local Object Dependencies
As an alternative to maintaining object dependencies globally, you have the option of maintaining
object dependencies locally for individual objects. These dependencies can then only be used for
the object concerned.
If you are sure that the dependency will not be used elsewhere, you should use local object
dependencies.
You can maintain local object dependencies for the following objects:
characteristics
characteristic values
BOM items
operations in a routing
SAP-00001863
sub-operations in a routing
sequences of operations in a routing
production resources/tools in a routing
Local object dependencies are always maintained in the maintenance function for the object
concerned. You maintain local dependencies using the same function and screens as when you
link global dependencies to objects.
You can maintain local dependencies by calling the Details --> Object dependencies --> Editorfrom
any of the screens listed below.
You can also create local object dependencies using the function Details --~ Dependency --~ Link.
To do this, you then have to call the function Edit --~ New dependency --> Local on the link screen.
Object
Object maintenance screen
Characteristic
Characteristic value
BOM item
Operation/suboperation
Sequence of operations
Production resource/tool
Any screen
Allowed values screen
Item overview screen
Operation detail screen
Sequence detail screen
PRT detail screen
If no object dependencies have yet been defined for the object, you first see a dialog box in which
you specify whether you want to enter a precondition, a selection condition, or an action.
Note
You cannot use all these dependency types for all types of object. For example, you cannot use
preconditions for BOM items.
If a local dependency already exists for the object, you see the dependencies editor. If several
dependencies exist, you see the link screen, on which you see the dependencies which have
already been linked to the object. To link a new dependency to the object, choose the Edit
--~ New dependency--> Local function. You then see the dialog box in which you specify which
dependency type you want to create. Then you see the dependencies editor, in which you can
define your dependency.
SAP-00001864
Examples of Object Dependencies

This topic contains some examples of object dependencies. There is a brief explanation of the
problem, followed by a description of the dependency required for solving it, and the syntax you
need to define the dependency.
Object Dependencies for Characteristics
Let us assume that you are configuring a car, and only want the characteristic Power steering to
be displayed if the characteristic Model has either the value 1600 or no value. In all other models,
power steering is included automatically and therefore does not need to be selected.
To do this, you maintain object dependencies for the characteristic Power steering.
In a characteristic maintenance function, call the function Details ->
Object dependencies --~ Editor. Select the dependency type precondition.
Enter the following in the dependencies editor as your condition.
MODEL
eq
1600
Note
Please note that a dependency like this can only affect configuration if the class used in
configuration contains all the characteristics referred to. In this case, the class has to contain both
characteristics: Model and Power steering. In addition, 1600 must be an allowed value for the
characteristic Model.
You also maintain a second dependency for the characteristic Power steering, which determines
that you must assign a value to the the characteristic if the condition is fulfilled.
To do this, maintain the characteristic Power steering.
In the characteristic maintenance function, call the function Details -->Object
dependencies -> Editor.
Select the dependency type selection condition.
Enter the following in the dependencies editor
MODELL eq
1600
The combination of these two conditions means that the characteristic Power steering only
appears in a configuration if the value 1600 or no value is assigned to the characteristic Model, as
defined in the precondition. The selection condition you maintained means that you must assign a
value to the characteristic Power steering if the value 1600 is assigned to the characteristic
Model.
Object Dependencies for Characteristic Values
In a car, you only want to allow certain combinations of upholstery and paintwork. The value light
brown is only allowed for upholstery if the car is ordered with Paintwork in either light brown,
green or gray. You can define this using characteristics.
To do this, maintain the value light brown for the characteristic Upholstery. This is where you
define colors for the car interior.
In the characteristics maintenance function, call the function Details ->Object
dependencies -> Editor.
Select the dependency type precondition.
SAP-00001865

Paintwork
or
or
eq
light brown
green
gray
Alternatively, you could express the dependency as follows:

Paintwork in
(light brown, green, gray)
This means that the value light brown only appears as an allowed value for the characteristic
Upholstery in configuration if the characteristic Paintwork has the value light brown or green or
gray.
If another value (such as blue) is assigned to the characteristic Paintwork in configuration, the
value light brown does not appear in the list of allowed values for the characteristic Upholstery.
Object Dependencies for BOM Items
A sports steering wheel is only supplied with certain models. In the characteristics maintenance
function, you have determined that the value 001 (sports steering wheel) only appears as an
allowed value for the characteristic Extras for certain models of car.
Now you want the BOM item Sports steering wheel to be included in the BOM explosion if the
value 001 is assigned to the characteristic Extras for one of these models.
To do this, proceed as follows:
In a BOM maintenance function, select the component Sports steering wheel. Choose the
function Details --~ Object dependency --~ Editor and select the dependency type selection
condition.
Extras
eq
001
Note
In the dependencies editor, always use the language-independent characteristic value. In this
example, this is 001 and not sports steering wheel.
This dependency means that the BOM item Sports steering wheel is only selected and included
for the BOM explosion if the value 001 is assigned to the characteristic Extras. If a different value
or no value is assigned to the characteristic, the sports steering wheel is not selected and is not
included in the BOM.
SAP-00001866
Configured Materials/Stockable Types

This section describes what configured materials are and the advantages they can provide for your
company. It tells you which data you have to maintain for a configured material and what you
need to consider when you create a configured material.
.8.~.e [aI.Eun.c.tLo.ns
SAP-00001867
What is a Stockable Type?

A stockable type is a material which is derived from a specific configuration of a standard product,
and which is kept in stock. A stockable type is therefore a configured material.
The material master of the configured material is linked to a standard product, and values are
assigned to the characteristics in a class which is linked to the standard product (see the following
figure). This specific variant of the standard product can then be produced and kept in stock if
required.
Material
Stockable type
Car-SM1
Configuration
Class type/class
300/Car
Assigned characteristic values

~. Engine: 2.0
m~ Transmission: 5-gear
~- Paintwork: black
~. Wheels: steel
~. Extras: Anti-lock brakes, airbag
SAP-00001868
What are Stockable Types Used for?

If certain configurations of a standard product are used frequently, it is useful to create a stockable
material for these configurations and to produce them in advance if required. This means that, if
you receive a sales order for one of these configurations, you can supply them from stock.
SAP-00001869
Maintaining Master Data

Before you can work with configured materials/stockable types, you need to create a material
master which refers to the standard product. To do this, enter the number of your standard
product in the Standard product field on the MRP 2 screen of your material master. You then see
another screen, on which you enter the actual specification of the configured material.
Materials Planning
The MRP group field on the MRP I screen is important in materials planning for a configured
material. If you want to plan a configured material or make to stock, and want to use this data in
the sales order for availability checks and calculation of delivery times, enter 0065 (planning for
stockable types) in this field. If you do not want to plan the material, you can use other MRP
groups, such as 0026 (make to order for configured materials).
SAP-00001870
Bills of Material
Before you can break down material requirements for a configured material, once you have
maintained the necessary data in the material master, you need to link a bill of material to the
configured material.
You can either create a separate bill of material for the configured material (using the copy function
if required) or, as will more often be the case, link the material to the BOM for the standard product.
If you link the material to the BOM for the standard product, the BOM is exploded in materials
planning according to the assigned characteristic values. The system interprets the BOM by using
the selection conditions defined and assigning values to fields in the BOM item according to the
relevant actions.
Linking a Configured Material to a Material BOM
To link your configured material to the BOM for the standard product, proceed as follows:
1. Starting from the bills of material menu, choose Bills of material -~ Material BOM --~ Alloc.
config, mat. -~ Create.
2. Enter the number of your configurable material in the Material field.
On the next screen, you see that the configured material is entered as the first link. Select the
link and call the All allocs for BOM function. You see all the materials which are linked to this
BOM.
3. Save your link.
SAP-00001871
Routings
To produce a configured material, once you have maintained the necessary data in the material
master, you need to link a routing to the configured material.
You can either create a separate routing for the configured material (using the copy function if
required) or, as will more often be the case, link the material to the routing for the standard product
in the routing maintenance function.
If you link the material to the routing for the standard product, the routing is exploded in the
production order according to the assigned characteristic values. The system interprets the
routing using the selection conditions defined in the operations, sub-operations, sequences of
operations and production resources/tools in the routing.
Linking a Configured Material to a Routing
To link your configured material to the routing for the standard product, proceed as follows:
1. Starting from the routings menu, choose function Routings -~ Routing -~ Change.
2. Enter the number of your standard product.
3. Choose menu option Goto -~ Header overview.
4 Choose the functions Routing --~ Material allocation --~ New lines and enter the number of the
configured material you want to link to the routing.
5. Save your link.
Sales Orders
Once you have created a material master and a BOM for your configured material, you can create
sales orders for the material. The sales order is used to automatically generate a customer
requirement for materials planning.
Materials Planning
In the next planning run, the BOM linked to the configured material is exploded for the sales order.
If this BOM is the BOM for the standard product, the BOM is exploded according to the object
dependencies defined in the BOM. The system generates a planned order to cover the customer
requirements.
This planned order is used later to produce a production order, which consists of the configured bill
of material and the configured routing.
Once the configured material has been produced, the goods receipt can be posted, and the sales
order can be supplied.
SAP-00001872
Special Functions
If you create a sales order item for a configured material, and the MRP group 0065 (planning for
stockable types) is entered in the material master, you can use an additional function.
This enables you to change the configuration stored in the material master for an individual order.
To do this, enter the number of the configured material as the article in the sales order. Then you
can use function Item -~ Structure -~ Configuration to change the configuration, then save your
changes. This change is then passed on as a changed requirement for materials planning.
Note
The availability check and clearing of requirements always refer to the characteristic values
assigned for the stockable type. They do not take into account any changes made for an
individual order.
This allows you to plan certain variants which occur frequently and to determine the delivery date in
the sales order. However, you can still use all variant configuration functions by changing the
configuration.
SAP-00001873
Simulation
Once you have configured your standard product, you can go on to process a sales order.
However, first you will want to check the configuration, to see whether the objects have been
maintained correctly and whether you have created the correct object dependencies. This is what
the simulation function is for. Two simulation functions are supported:
....
; ...............
: ...........................................: .......
.... : ...............
: ..........................
: .....................; .......
SAP-00001874
Simulation of BOM Explosion

You have three options for checking the BOM explosion for a standard product;
Simulation for the standard product to be configured
Simulation for a configured material
Simulation for a sales order item
The difference between these options is that the assigned characteristic values are already known
for a configured material and a sales order item. In the simulation, you only see how the BOM will
be exploded in materials planning.
If you run a simulation for a standard product, you can try out a number of different combinations of
characteristic values one after the other, and see what effect they have on the BOM explosion.
Simulation for a Standard Product
To run a simulation for a standard product, proceed as follows:
1. Starting from the configuration menu, call function Environment --> Conf simulation.
The first time you call the simulation function in the current session, you see a screen on which
you select which configuration result you want to analyze.
2. Choose Dynamic BOM. Select Continue. You see the next screen.
3. If you have not entered a plant in the current session, you see an additional dialog box. Enter a
plant for your standard product. Select Continue.
4. On the next screen you see, enter the standard product for which you want to run a simulation.
5. Select Characteristics.
You see the characteristics screen, on which you enter characteristic values for the standard
product. Once you have assigned all the values required, choose the Next screen function.
The bill of material for the standard product is then exploded according to the values you
entered, and the selected objects are displayed.
You can display the BOM on which the simulation is based by selecting the Master data button.
By comparing the master data and the result of your simulation, you can check which objects
were selected and which were not.
If you select the Explode function, you can explode BOM items which are assemblies, or see which
materials are covered by a class item. You can see a summarized list using the function
Compress.
On the initial screen, you can use the View --> Scope function to determine that object
dependencies for selected objects are included for display, if object dependencies were defined.
Note
If you want to run a simulation for a routing, or if you have run a simulation for a routing and now
want to run a simulation for the BOM explosion, use the function Configuration --> Change config,
before you can start the simulation.
Simulation for a Configured Material/Sales Order Item
The difference between a stockable type and a normal standard product is that a stockable type
has already been configured using the material master. The configuration is already known for a
SAP-00001875
sales order item, as well. Characteristic values are already assigned in both cases.
Once you have linked the stockable type to the BOM for the standard product (see ~_g.u.re..d...
~...T..y.p.es ), you can simulate a BOM explosion for a stockable type using the
same function as for standard products.
To run a BOM explosion for a stockable type or a sales order item, proceed as follows:
1. Starting from the configuration menu, call function Environment --> Conf simulation.
If you have not yet called a simulation in the current session, you see a screen on which you
select which configuration result you want to see.
2. Choose Dynamic BOM. To see the next screen, select Continue.
3. If you have not entered a plant in the current session, you see an additional dialog box. Enter a
plant for your standard product. Select Continue.
4. On the next screen, define which standard product you want to run a simulation for. Enter the
standard product and select Configured objects.
5. Select Material or Order, according to whether you want a simulation for a material or a sales
order item.
6. Enter the number of the configured material or the order item number in the relevant field, and
choose Back. The entered data is copied.
7. Choose ResuR.
The BOM for the configured material or material in the sales order item is exploded according to
your entries, and the selected objects are displayed.
To see the BOM on which the simulation is based, select the Master data button. By
comparing the master data and the displayed result, you can check which objects were selected
and which were not.
SAP-00001876
Simulation of Routing Explosion

You have three options for exploding the routing for a standard product;
Simulation for the standard product to be configured
Simulation for a configured material
Simulation for a sales order item
In a simulation for a standard product, you can try out a number of different combinations of
characteristic values one after the other, and see what effect they have on the routing explosion.
Simulation for a Standard Product
To
see the routing explosion for a standard product, proceed as follows:
1. Starting from the configuration menu, call function Environment --> Confsimulafion.
If you have not yet called the simulation function in the current session, you see a screen on
which you select the configuration result you want to see.
2. Choose Dynamic routing. Select Continue to see the next screen.
3. If you have not yet entered a plant in the current session, you see an additional dialog box.
Enter a plant for your standard product. Select Continue.
4. Select Characteristics.
You see the characteristics screen, on which you assign characteristic values for the standard
product. Once you have assigned values to all the characteristics required, choose the Next
screen function.
The routing for the standard product is exploded according to your entries, and the selected
objects are displayed.
Select the Master data button to see the routing on which the simulation is based. By
and which were not.
Simulation for a Configured Material/Sales Order Item
To see the routing explosiong for a configured material or a sales order item, proceed as follows:
1. Starting from the configuration menu, call the function Environment--> Conf simulation.
If you have not yet called the simulation function in the current session, you see a screen on
which you select the configuration result you want to see.
2. Choose Dynamic routing. Select Continue to see the next screen.
3. If you have not yet entered a plant in the current session, you see an additional dialog box.
Enter a plant for your standard product. Select Continue.
4. On the next screen, enter the standard product for which you want to run a simulation. Choose
Configured objects.
5. Select Material or Order, according to whether you want to simulate a routing explosion for a
configured material or a sales order item.
6. Enter the number of the configured material or the order item number in the relevant field, and
choose Back. The entered data is copied.
7. Choose Result.
SAP-00001877
The routing for the configurable material or the sales order item material is exploded according
to your entries and the selected objects are displayed.
Select the Master data button to see the routing on which the simulation is based. By
and which were not.
SAP-00001878
Example of a Configuration
This section is an overview of the activities you need to carry out in order to work with products
which have a large number of variants. This section is divided into two topics:
SAP-00001879
Preparatory Work
A standard product is a product with many variants which is represented by a bill of material (BOM).
As well as the components which must be contained in all product variants, this bill of material
contains components which can be optional. You describe the individual product variants by
assigning values to characteristics. You define the mutual dependency of the optional components
using object dependencies stored in the system.
In sales processing you can configure standard products using a special editor. When you
configure a standard product, you define a concrete product variant from the numerous possible
variants by assigning values to the identifying characteristics of the product. You can determine the
standard products which need to be configured using the search function in the classification
system.
In sales documents, you can configure variants of a standard product in a configuration editor.
When you enter a configurable standard product, the configuration editor is called automatically.
Before You Start
Before you can configure a standard product, the following prerequirements must be met:
Create the standard product
Create a class for configuration with characteristics
Link the class to the standard product
Create the BOM for the standard product
Create the routing for the standard product
SAP-00001880
Ch~r~4~ri=lic, D
n~in~n~noo
Detining dependenaiem
betvreen ohm~o1~ri~,D
:nd vduam
Grouping together
ohamotofi:lo:
Meidadnlng clepencloncims
In ctmm~edetJoe malnlunance
or claaatllcel~n eqNiern
CIa:: nmintenanoe
I.i nldng ohar-~oM d~lio.1
(o1~) ~n
=*~ndmd produot
C~i ng oonflg umble
m~dBfi=l
Crmding la BOM
~th AI potable
ifmm~
DOM nmi ntens; noe
MAnt~ning
aele~4io n oondiion:
for DOM item
BOM rr~inten:nc4
Cmnttng la routng
~ith :all poe,eible
opemfion:
Rouing;~ ms;i ntens; noe
hbi nt~i ni ng
~deoGo n oonditJon=
for doment~ in
Jhe rou6ng
Roulnge m~intennnoe
Creating the Standard Product

You must create the standard product with a material type which allows configuration. In the
standard version of the SAP R/3 System, the material type KlVlAT has been defined for this
purpose. When you create the product, the item category group 0002 (configurable material) is
automatically proposed on the Sales 2 screen. This item category group is used to determine the
appropriate item category (for example, TAC in sales orders) for carrying out configuration in sales
documents. For more information on creating a standard product, see .M__a__intaj_nj_nq__S__[a__nd_a_r_d___
__Prod__ucts
SAP-00001881
Creating a Class with Characteristics

Characteristics are features used to describe and distinguish objects, including standard products.
Characteristics and their values describe the features of concrete attributes of a standard product.
In the case of a car, the following characteristics and their values are required to describe the
product, among others.
Characteristics and Characteristic Values
Characteristic
Color
Extras
Values
diamond black
alpine white
calypso red
anti-lock brakes
towbar
trip computer
Classes
To be able to configure a standard product, you need to create a class which contains all the
characteristics required to describe the standard product. The class must have a class type which
allows variant configuration. In the standard version of the SAP R/3 System, this is the class type
300. For more information on creating classes, see the guide to the MM - Classification System.
Linking the Standard Product to the Class
You must link the standard product to the class whose characteristics describe the standard
product. You can link several classes to a standard product and then select one of them when you
configure the standard product.
In the configuration of standard products, it is usually the case that not all characteristics and not all
characteristic values within a class can be combined with each other. The reasons for this can be
both technical (for example, certain engines can only be combined with a certain transmission) or
commercial (for example, leather upholstery can only be ordered for more expensive models).
These reciprocal relationships are stored in the system as object dependencies.
You can define any dependencies between chracteristics and characteristic values in characteristic
linking
a class to
a standard
product,and
seeallocation
.Features to
of class
a I~rod.uct
maintenance,
class
maintenance,
functions.
"
For more information on
Creating a Bill of Material for the Standard Product
To produce variants of a standard product, you require a large selection of parts. A list of these
part is stored in the form of a bill of material. This BOM contains components which must be used
in all variants of the product, together with selectable components. You describe the actual
individual variants by assigning values to the relevant characteristics.
You must create a bill of material for the standard product. You enter the relevant standard product
as the header material for the bill of material.
For individual BOM components, you can either maintain object dependencies locally in the BOM
or globally. If you define object dependencies globally, you then have to link them to the
appropriate BOM component. For more information on bills of material, see the PP- Bills of
Material Guide.
Creating a Routing for the Standard Product
SAP-00001882
You must also create a routing for the standard product. A routing is a list of instructions for
assembling the parts listed in the bill of material. Rather than creating a separate routing for each
variant, you can define all possible manufacturing processes in one routing.
Only when you assign values to the characteristics of a standard product in the sales order do you
determine which parts and which operations are required to produce the variant you require.
For individual elements of routings (such as operations, sequences of operations or production
resources/tools), you can either maintain object dependencies locally in the routing or globally. If
you define object dependencies globally, you then have to link them to the appropriate element in
the routing. For more information on creating a routing, see the guide to PP- Routings.
SAP-00001883
From Sales Order to Production Order

Once you have carried out all the necessary preparatory work, you can enter sales orders for your
products. In the sales order, the product is configured. The objects selected determine which
requirements are passed on to materials planning. Then the planned orders generated in
materials planning are used to produce production orders (see the following Figure).
Salesorder
with
standard producl
IV
ere
custOmer q
quirement J
1
plannedorder i
Conversionof
-Production~~
order )
Carrying out Configuration

When you enter a sales document for a configurable standard product, the system automatically
branches into the configuration editor. Configuration involves assigning values to the appropriate
characteristics of the standard product so that the variants requested by the customer are
determined and copied into the sales document.
Characteristic Value Assignment
You carry out characteristic value assignment in the sales document in the configuration editor. In
SAP-00001884
the Characteristic value assignment section of the screen, depending on the display you selected,
you see all relevant characteristics and the corresponding characteristic values.
This is What You Do
To assign values to a characteristic in the configuration editor, proceed as follows:
1. Select the characteristic to which you want to assign a value by using the cursor pickup function
on the characteristic.
2. Place the cursor on the required characteristic value.
3. Select Edit -->Choose in the menu or select the characteristic value using the mouse with a
double click.
The selected characteristic value and the corresponding characteristic are displayed in a
different color. This indicates that a value has been assigned to the characteristic.
Note
You can use characteristics maintenance to define default values for characteristics. The system
selects the default characteristic values automatically when it calls up the configuration editor.
However, you can cancel the selection by following the procedure above.
4. Repeat the procedure if the characteristic involved allows more than one value assignment.
5. Select Assign value -->Save to save the assigned values and the sales order.
Alternatively, select Back. This takes you out of the configuration editor onto the item entry
screen, where you can continue processing the sales order. Your value assignments are also
saved in this case.
Note
If you want to go directly to a particular characteristic in the configuration editor, press Position. Enter
the characteristic you require in the Position dialog box and press ENTER. This takes you to the
characteristic you require.
Variable Views
You can influence the display and scope of the characteristics list in the configuration editor.
To influence the display of the characteristics list, select View -->Display. For more information on
this subject, see the guide to the MM - Classification System.
To influence which chracteristics of the class appear in configuration, select View-->Scope. For
more information onfthis subject, see the guide to the MM- Classification System.
Object Dependencies for Characteristics and Values
If object dependencies have been maintained for characteristics and characteristic values, you can
display this information in the configuration editor by placing the cursor on the appropriate
characteristic or value and selecting:
Charact.dependencyto display characteristic dependencies
Value dependencyto display value dependencies
You see a dialog box in which the object dependency is displayed for the respective characteristic
or characteristic value. Press ENTER to return to the configuration editor.
Customer Requirements
SAP-00001885
When you save your sales order, a customer requirement for the standard product is automatically
sent to materials requirements planning. To see this requirement, starting from the material
requirements planning menu, call the function Evaluations
Stock/reqmts list.
Material Requirements Planning
To access material requirements planning, call MRP from the Production menu. From the MRP
menu, choose MRP -~ Sng-item, multi-lvl or sng-level.
The customer requirement is read in MRP and the requirement for the selected BOM items is
determined on the basis of the characteristic values assigned for the standard product. A planned
order is generated to cover the customer requirement. This planned order contains the
requirements for the BOM components which are required for all variants of the standard product,
together with the requirements for the BOM components which were selected according to the
object dependencies maintained in the BOM.
Planned Order
You can also see the planned order which was generated in MRP to cover the sales order in the
requirements/stock list. To look at the planned order in more detail, select the planned order and
choose function Environment --~ Display element. Using the function Edit mat. comp., you can
see which components a requirement was generated for.
Convert Planned Order
To enable you to produce the product, you have to convert the planned order generated for the
standard product to a production order. To do this, select the planned order from the
requirements/stock list and choose the function Environment ~ Convert --~ PL ord./prod, ord..
The planned order is then converted to a production order.
Production Order
When you convert the planned order to a production order, the system reads the planned order and
selects the operations which are required in production, according to the characteristic values
assigned for the standard product. The system selects the operations and production
resources/tools which are required in all variants of the standard product, together with those which
are selected for the specific variant, according to the object dependencies maintained in the
routing.
The production order which is generated by the conversion can then go through the usual
production order processing.
SAP-00001886
Syntax: Object Dependencies

SAP-00001887
Syntax of Conditions: Overview

This topic contains a formal description of the syntax for conditions. To the right of each element
of grammar, there is a key which shows the sub-elements which can be used to make up the
element. The symbol 11 separates alternative ways of forming the element. The character &
shows that the following sub-element must be used in the element as well. Numeric and logical
expressions can be bracketed. However, the following overview does not describe bracketing.
Condition ->
log. expression I I
log. expression 8, .
log. expression
atomic condition I I
log. expression & binary log. operator 8, log. expression I I
NOT 8, log. expression
atomic condition
Built-in condition I I
comparison expression
Built-in condition
SPECIFIED 8, characteristic variable I I
characteristic variable 8,SPECIFIED I I
TYPE_OF 8, ( 8, object variable 8, , 8, material number 8, )
characteristic variable 8, IN 8, value set
II
Characteristic variable
characteristic name I I
object variable 8, . 8, characteristic name
Object variable
$ROOT II
$PARENT II $SELF
Value set
num. value set
I I symb. value set
num. value set

( & num. value entry & num. value set (remainder)
num. value entry
figure II
interval
figure
integer II
decimal number
decimal number 8, exponent
II
interval
lower limit 8, - 8, upper limit I I
figure (with > or>=) I I
figure (with < or <=)
SAP-00001888
lower limit
figure I I Iowerlimit type & figure I I
figure & lower limit type
lower limit type
>= II => II GE II
EQ II > II GT
= II
upper limit
figure I I upperlimit type & figure I I
figure & upper limit type
upper limit type
<= II =< II LE II
EQ
= II
II < II LT
num. value set (remainder)

) I I , & num. value entry &num value set (remainder)
symb. value set
( & character string in inverted commas & symb. value set (remainder)
symb. value set (remainder)
) I I , & character string in inverted commas & symb.value set (remainder)
Comparison expression
symb. string & symb. comparison operator & symb. string I I
num. string & num. comparison operator & num. string
symb. string
character string in inverted commas I I
characteristic variable
symb. comparison operator
<> II >< II
EQ
II
NE II
num. string
figure I I characteristic name I I - &num. string I I
num. string & binary num. operator & num. string I I
num. function string
binary num. operator
+ II - II ~ II /
num. function string
num. function & ( & num. string & )
num. function
sin II cos
abs II sqrt
II
tan
II
exp II
In II
num. comparison operator
<= II =< II >= II
=> II <> II >< II
SAP-00001889
= II < II > II LT II
GE II GT II NE
LE II
EQ
binary log. operator
AND II OR
When you enter a key word, such as AND, NOT, $ROOT and so on, the system does not
distinguish between upper case and lower case letters. The same applies to characteristic names
and material numbers.
When you enter a characteristic variable, a distinction is made between single-value and
multiple-value characteristics. Multiple-value characteristics can only be used in simple
comparison expressions (=, <>) as either the left or right-hand side of the expression.
SAP-00001890
Syntax of Actions" Overview

This topic contains a formal description of the syntax for actions:
Actions
action
I I action 8., 8. actions
action
reference
I I IF structure
reference
symbolic reference
I I numeric reference
symbolic reference
$SELF &" & characteristic name & = & symbolic string
numeric reference
$SELF &" & characteristic name & = & numeric string
IF structure
action & IF & condition I I
( & reference & ) & IF & condition
reference
reference I I reference &, & reference
SAP-00001891
class:status;configuration parameters:status; Feature <-> characteristic; Features of a

Standard Product;Merkmal:negativer Wert;Merkmalwerte;required
characteristic; standard product:link to class; Start logo: call in configuration
SAP-00001892

Variant Configuration Online Documentation Part 20 (P.T.a.B. Sep. 16, 2012)

Uploaded by

Document Information

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 Online Documentation Part 20 (P.T.a.B. Sep. 16, 2012)

Uploaded by

Copyright:

Available Formats

PP Variant Configuration Guide

The following Help Topics are available:

For Help on Help, Press F1

Processing of Quotations and Orders

possibilities or decide not to accept the order.

Overview of Variant Configuration

This section contains the following topic:

Describing a Standard Product

Maintaining Standard Products

create a standard product, proceed as follows:

Materials Planning Data

Object Master Data

BOMs as Object Master Data

To create a class which can be used as a class item, proceed as follows:

Routings as Object Master Data

KFeatures of a Standard Product

Characteristic Value Assignment I

Additional data for configurable objects

Assigned characteristic values

.~lbEngine (1600, 1800, 2000 ...)

What are Object Dependencies?

Use of Object Dependencies

characteristic during configuration if the selection condition is fulfilled.

specific variant of a standard product.

Syntax of Object Dependencies

The syntax $ROOT.VOLUME < 0.5 * TOTAL_VOLUME

> figure 1 - < figure 2

less than figure 1

LENGTH IN (300 - 500,566,600 - <700, 1000)

You can also use the following mathematical functions:

Maintaining Object Dependencies

Examples of Object Dependencies

Enter the following in the dependencies editor as your condition.

Alternatively, you could express the dependency as follows:

(light brown, green, gray)

Configured Materials/Stockable Types

What is a Stockable Type?

Assigned characteristic values

What are Stockable Types Used for?

Maintaining Master Data

Simulation of BOM Explosion

Simulation of Routing Explosion

see the routing explosion for a standard product, proceed as follows:

I.i nldng ohar-~oM d~lio.1

Creating the Standard Product

Creating a Class with Characteristics

From Sales Order to Production Order

Carrying out Configuration

Value dependencyto display value dependencies

Syntax: Object Dependencies

Syntax of Conditions: Overview

I I symb. value set

num. value set

num. value set (remainder)

num. comparison operator

<= II =< II >= II

=> II <> II >< II

binary log. operator

Syntax of Actions" Overview

I I action 8., 8. actions

class:status;configuration parameters:status; Feature <-> characteristic; Features of a

You might also like