Getting Started With Configuration Control

SAP
Getting Started
With Configuration
Control
An introduction into Configuration Control not only for
beginners
Version:
4/28/2014
Robert Hügel
4/28/2014
SAP Getting Started With Configuration Control
Table of Contents
1 Motivation ....................................................................................................................................... 7
2 Prerequisites, boundary of the topics ............................................................................................. 7
3 What is Configuration Control about? ............................................................................................ 8
3.1 Technical objects ..................................................................................................................... 8
3.2 Consistence check of the technical objects............................................................................. 9
4 Before modeling define your needs .............................................................................................. 10
5 Basic rules of modeling, the first example .................................................................................... 16
5.1 General .................................................................................................................................. 16
5.2 iPPE, Integrated Product- and Process-Engineering.............................................................. 16
5.3 The example .......................................................................................................................... 16
5.4 Access node and product class .............................................................................................. 17
5.5 Structure nodes, building up a structure inside the MPL ...................................................... 21
5.6 Building up the actual structure ............................................................................................ 24
5.6.1 General remarks ............................................................................................................ 24
5.6.2 Top equipment, hard link to the corresponding set of rules ........................................ 24
5.6.3 Equipment relevant for the check of Configuration Control......................................... 26
5.6.4 Configuration check with transaction CCM2 ................................................................. 29
5.6.5 Multiple usage of a MPL ................................................................................................ 31
5.6.6 The three steps of Configuration Control...................................................................... 31
5.6.7 FID grouping (1), interpretation of the actual structure for Configuration Control
purpose 32
6 View nodes and functional locations ............................................................................................ 35
6.1 Motivation ............................................................................................................................. 35
6.2 The example .......................................................................................................................... 35
6.3 Functional locations .............................................................................................................. 37
6.3.1 The very top functional location ................................................................................... 37
6.3.2 Functional locations as installation location for equipment ......................................... 37
6.3.3 Meaning of structure levels........................................................................................... 37
6.3.4 FID Grouping (2), influence of functional locations ...................................................... 38
6.3.5 Wrong usage of functional locations, error message CCMM047.................................. 40
6.3.6 Determination of top equipment with link to MPL access node, error message
CCMM021 ...................................................................................................................................... 42
6.4 View nodes ............................................................................................................................ 45
6.4.1 General remarks ............................................................................................................ 45
Page 1 of 177
6.4.2 Rules on relations between different types of MPL nodes ........................................... 45

6.4.3 Attributes of a view node .............................................................................................. 45
6.4.4 Final rules for the determination of the parent MPL node, error message CCMM047 46
7 iPPE node types, usage for modelling the MPL ............................................................................. 48
8 Productive usage of Configuration Control ................................................................................... 50
8.1 General .................................................................................................................................. 50
8.2 Transaction IE4N, installation/dismantling with or without goods movement .................... 51
8.3 Structure Gaps ....................................................................................................................... 51
8.3.1 General .......................................................................................................................... 51
8.3.2 Content .......................................................................................................................... 52
8.3.3 Creation, Deletion, Adjustment..................................................................................... 52
8.4 Dismantling equipment with IE4N ........................................................................................ 53
8.4.1 General .......................................................................................................................... 53
8.4.2 Example ......................................................................................................................... 53
8.5 Installing equipment with IE4N ............................................................................................. 55
8.5.1 General .......................................................................................................................... 55
8.5.2 Local check and forced installation ............................................................................... 55
8.5.3 Examples........................................................................................................................ 56
8.5.3.1 Installation in an installation location without structure gap ................................... 56
8.5.3.2 Dismantling of an equipment, Structure gap is also part of the quantity check....... 59
8.5.3.3 Manipulating a structure gap .................................................................................... 59
8.5.3.4 Installation of a part with a wrong material number and a corresponding FID........ 60
8.5.3.5 Dismantling of a wrong part ...................................................................................... 63
8.5.3.6 Installation of a part with a correct material number but a wrong FID .................... 64
8.5.3.7 Other important messages in the process ................................................................ 66
9 Usage of bill of material (BOM) ..................................................................................................... 67
9.1 General .................................................................................................................................. 67
9.2 Customizing relevant for cBOM usage .................................................................................. 68
9.3 Technical preconditions ........................................................................................................ 70
9.4 cBOM and the MPL ................................................................................................................ 70
9.5 Usage of the cBOM in actual structure ................................................................................. 70
9.5.1 How to create a cBOM?................................................................................................. 70
9.5.2 How to maintain a cBOM? ............................................................................................ 72
9.5.3 How to display a cBOM ................................................................................................. 74
Page 2 of 177
10 Object Dependency ................................................................................................................... 74

10.1 Motivation ............................................................................................................................. 74
10.2 Introduction ........................................................................................................................... 75
10.3 Modeling the MPL ................................................................................................................. 76
10.4 Actual structure ..................................................................................................................... 79
10.5 Usage of the configuration of the top equipment in logistic processes together with
Configuration Control ........................................................................................................................ 82
10.5.1 Top equipment is not part of a logistic process like a goods movement ...................... 82
10.5.2 Top equipment is part of a logistic process like a goods movement ............................ 82
10.5.2.1 Logistic process and Configuration Control needs configuration information of the
serialized equipment ................................................................................................................. 82
10.5.2.2 Only Configuration Control needs configuration Information of the serialized
equipment 84
10.6 FID-Grouping and configuration of top equipment .............................................................. 84
11 Parameter Effectivity of Engineering Change Management (ECM) .......................................... 85
11.1 Motivation ............................................................................................................................. 85
11.2 Customizing settings for ECM................................................................................................ 86
11.2.1 Parameter effectivity must be activated ....................................................................... 86
11.2.2 Maintain the proper effectivity parameter and the effectivity type ............................ 86
11.2.3 Maintain the effectivity type ......................................................................................... 87
11.3 General customizing setting for iPPE .................................................................................... 87
11.4 Create change numbers (ECN) using transaction CC01......................................................... 87
11.5 Modeling the MPL ................................................................................................................. 90
11.6 Actual structure, top equipment and its’ configurable material .......................................... 91
11.7 Results of check ..................................................................................................................... 93
11.8 FID-Grouping and value for parameter effectivity of top equipment................................... 95
12 Usage of coupled MPLs ............................................................................................................. 96
12.1 Motivation ............................................................................................................................. 96
12.2 Sum up the current structures of the aircraft ....................................................................... 98
12.3 Set up of coupled MPLs by using an example ....................................................................... 99
12.3.1 Definition of the subordinate MPL ................................................................................ 99
12.4 Enhancement of the actual structure ................................................................................. 104
12.4.1 General remarks .......................................................................................................... 104
12.4.2 The top equipment of the structure............................................................................ 105
12.4.3 Subordinate equipment .............................................................................................. 106
Page 3 of 177
12.4.4 Final actual structure ................................................................................................... 106

12.5 Implement the partial check ............................................................................................... 108
12.5.1 General remarks .......................................................................................................... 108
12.5.2 BAdI BADI_CCM_EXPLOSION ...................................................................................... 109
12.5.2.1 Additional attributes ........................................................................................... 109
12.5.2.2 Additional method CHECK_FUNCID .................................................................... 109
12.5.2.3 Interface methods ............................................................................................... 111
12.5.3 BAdI BADI_CCM_EXPL_ALWD ..................................................................................... 113
12.5.3.1 General remark.................................................................................................... 113
12.5.3.2 Interface methods ............................................................................................... 113
12.6 Usage and results ................................................................................................................ 114
12.7 FID Grouping (3) .................................................................................................................. 117
12.8 Multiple usage of subordinate MPL, Top-Assembly-FID ..................................................... 122
13 Details of quantity check ......................................................................................................... 123
13.1 Motivation ........................................................................................................................... 123
13.2 How does the quantity check in Configuration Control work from a technical point of view?
123
13.3 Example ............................................................................................................................... 125
13.3.1 Situation ...................................................................................................................... 125
13.3.2 Recommendation ........................................................................................................ 130
14 Interchangeability.................................................................................................................... 133
14.1 Motivation ........................................................................................................................... 133
14.2 Integration in Configuration Control ................................................................................... 134
14.3 Modelling............................................................................................................................. 134
14.4 Interchangeability, object dependency and parameter effectivity..................................... 139
14.5 Runtime ............................................................................................................................... 139
14.6 How to switch of interchangeability in Configuration Control? .......................................... 139
14.7 Summary of Restrictions ..................................................................................................... 140
15 Set-Relationship ...................................................................................................................... 141
15.1 Motivation ........................................................................................................................... 141
15.2 Usage and modelling ........................................................................................................... 141
15.3 Integration in Configuration Control ................................................................................... 152
15.4 Restrictions and recommendations .................................................................................... 158
16 Cancel-Part Relationships ........................................................................................................ 159
16.1 Motivation ........................................................................................................................... 159
Page 4 of 177
16.2 Usage and modelling ........................................................................................................... 159

17 Mission dependent modelling and optional parts. ................................................................. 167
18 Data modeling and runtime .................................................................................................... 168
19 Used literature, bibliography .................................................................................................. 169
20 Table of messages of Configuration Control ........................................................................... 171
21 Table of figures ........................................................................................................................ 173
Page 5 of 177
© 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be
reproduced or transmitted in any form or for any purpose without the express permission of SAP AG
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other
countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices. Some software products marketed by SAP AG and its
distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP
affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP AG or its affiliated companies at
any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-
looking statements, which speak only as of their dates, and they should not be relied upon in making
purchasing decisions.
Title image:
SAP Brand Tools: Airplane hangar, George Hammerstein, Corbis,

http://imagedirectory.wdf.sap.corp:6085/ImageLibrary/ImageDetailsView?imageId=1816e7bb-1881-
4fab-be27-1ee0318d70e7
Page 6 of 177
1 Motivation
This document is made to arouse the understanding how Configuration Control is working.
Basic modeling skills of the data used for Configuration Control should be provided.
This documentation does not replace a consultant experienced in Configuration Control!
If available, technical chapters should provide an insight into the coding of the application to enable
users to adjust the application to their needs.
2 Prerequisites, boundary of the topics

This chapter should show the prerequisites and boundaries f this document:
 This document is making use of the Configuration Control functionality since EhP4.
 Making use of Configuration Control it is necessary to have good knowledge in the areas
shown in Figure 1. It is showing the world of Configuration Control and the applications used
to make Configuration Control running. This document is not made to explain the details of
all the mentioned used applications. Explanations are made as far as they are necessary to
get the basic knowledge of configuration control and how to model data.
Figure 1 The world of Configuration Control
 Specific chapters provide information on industry specific enhancements of Configuration

Control e.g. Aerospace & Defense (IS-ADEC).
 This document does not make an experienced Configuration Control consultant obsolete
when you want to introduce Configuration Control at your company!
 This document does not explain the used transactions and the underlying applications like
LO-VC and the customizing in detail. Explanations are given as far they are necessary to
understand the basics of configuration control.
 This document is only available in English.
 Anyhow, please make sure that the shown settings in the customizing are not in
contradictory to other business requirements of your system!
Page 7 of 177
 It is recommended to use Configuration Control since EhP4.
3 What is Configuration Control about?
3.1 Technical objects

SAP supports the maintenance of technical devices e.g. means of transport such as aircrafts, devices
of the chemical industry or utilities, buildings … by an application called Plant Maintenance.
Supported actions are for example
 Maintenance planning
 Maintenance processing
 Event documentation
 Accounting
 Installation/dismantling of parts into/from a technical device
 …
The basis for all the maintenance actions which can be performed on a technical devices with the
SAP application is a data model inside the system that represents the technical device and its’
subassemblies. Within the SAP system this modeling happens via the data objects functional location
and equipment.
Technical devices, assets, buildings or parts of it can be structured with functional locations. These
functional locations are often used to model the technical device on a high and rough level. The goal
is to separate the technical device in those organizational units that fits for the company. The
separation inside the structure often happens in dependence on
 Technical aspects: Devices of the engine, parts of the landing gear, press …
 Functional or process driven aspects: Condensation …
 Topological aspects: Building, hall, …
Equipment usually are independent, physical, individual objects to be maintained such as the engine,
the pump ….
Equipment can be installed into functional locations and equipment. In opposite functional locations
can only be assigned to superior functional locations.
Figure 2 is showing the structure of technical objects of a technical device, here an aircraft.
Page 8 of 177
Figure 2 Structure of a technical device using technical objects functional locations and equipment
3.2 Consistence check of the technical objects.

Technical object structures modeled within the SAP system can be quite complex. Thinking at an
aircraft such a structure can contain more than 5000 technical objects (functional locations and
equipment). This structure reflects the current configuration of a technical device. All other
maintenance actions relay on the correctness and reliability of this structure.
The major question which might came up at this point of time: How can the correctness of the
configuration of such complex structures can be guaranteed and checked?
Figure 3 is showing the overview on the solution Configuration Control inside the SAP system.
Configuration Control is used to uphold the operational safety and reliability of technical devices
inside the SAP system.
Figure 3 Overview Configuration Control
Page 9 of 177
Within the system a data structure is defined which represents the set of rules to be used for
validation checks. This structure contains more or less the valid parts and the quantity of the parts
and the location inside the technical structure. This set of rules is used to check the actual structures
of technical devices inside the system to find invalid or missing parts.
This set of rules is called Master Parts List (MPL) and is modeled by making use of the structuring
tools of the SAP application iPPE (Integrated Product & Process Engineering).
The development of Configuration Control was once triggered in the 1990th by the civil airlines and
was developed as industry solution of Aerospace & Defense. Within the R/3 Enterprise release 4.7 a
retrofit to the SAP standard took place in the year 2003.
4 Before modeling, define your needs

The most effort to spend within Configuration Control is to create a data model for the MPL and for
the actual structure of equipment and functional locations which is in accordance with the modeling
rules of the Configuration Control application! Any modeling error can lead to wrong or misleading
validation results of the application.
Therefore you first must have got an understanding on the needs of your company concerning the
checks you want to perform with Configuration Control.
This chapter should provide you with some ideas what topics to respect inside your data model.
Behind each topic you will find a keyword that gave a hint to a possible modeling solution. These
possible approaches are explained later on.
Page 10 of 177
Question/Task:
 Does a task sharing of maintenance, repair and overhaul activities at the technical device
exist? Are different teams with different skills responsible for different subassemblies?
 Can the technical device separated in different units from an organizational or technical
point of view?
 Does there exist the burden of proof for configuration checks of assemblies of a technical
device? On which level of the structure? On the whole structure or also on subassemblies of
it?
 Does there exist very big and complex subassemblies, should the data model allow the
installation/dismantling of those parts and the individual check of them?
Example:
Within the aircraft maintenance it can be expected that different teams are responsible for the
maintenance, repair and overhaul of the engines, landing gears, wing devices, ect. On the one and
these teams should be enabled to check the subassemblies they are experts in by using
Configuration Control. On the other hand a complete check of the complete aircraft should be
possible (see Figure 4).
Figure 4 Subassemblies at an aircraft
Possible approach:
Coupled MPLs with different product classes and usage of the complete and partial check inside
Configuration Control.
Page 11 of 177
Question/Task:
Does exist the need that one and the same technical device has to be adjusted to different
operational conditions?
Example:
Within the defense area a fighter aircraft has to fulfill different missions. The aircraft itself remains
the same in the major parts. Different operational task might need different additional parts, which
are not necessary for the basic operation of the fighter aircraft (see Figure 5).
Figure 5 Operational tasks of a fighter aircraft
Possible approach:
Coupled MPLs with different product classes, variant configuration, object dependency, customer
specific filtering functions for MPL and actual structure.
Page 12 of 177
Question/Task:
Are there technical devices of the same model but different types?
Example:
An aircraft manufacturer AC is producing two different aircraft models AC2 and AC3. Within the
airline the aircraft model Boeing AC2 is used. Different types are in operation e.g. the short range
type AC2-S and the long range type AC2-L (see Figure 6).
Figure 6 Aircraft models and types
Possible approaches:
 Create an MPL for each type of the model.

Disadvantage: This means high effort because of the fact that several MPLs of almost the
same object have to be created and maintained.
Advantage: Easy to model
 Use one and the same MPL for one model. Differentiate within the MPL between the
different types by using object dependency.
Disadvantage: Because of object dependency has to be taken into account the modeling of
the single MPL is more complex.
Advantage: Only one MPL to create and maintain.
Page 13 of 177
Question/Task:
Is there the need to model individual characteristics for different technical devices of the same
model?
Example:
The airline is using several aircrafts of the same model AC3 (see Figure 6). The single aircrafts are
identified by their tail number. The AC3 with the tail number AAAA-01 has 10 seats less than the
AC3 with the tail number BBBB-02.
Possible approach:
Model one MPL for the aircraft of the model AC3 and make use of Engineering Change Management
(ECM).
Question/Task:
Is there existing the possibility that materials are interchangeable concerning their
 form,
 fit and
 function?
Example:
The pump with the material number B can be used the same way than pump with the material
number B; form fit and function are identical.
Possible approach:
Usage of the material interchangeability functionality (e.g. via FFF-classes) .
Only available in the industry solution Aerospace & Defense.
Question/Task:
Are there existing rules for the exchange order of parts?
Example:
If once a fuel pump with the material number FP01 was installed into a technical device it is only
allowed to replace this pump with a fuel pump with the material number FP02.
Possible approach:
Usage of the Cancel-Parts-Relationship approach.
Page 14 of 177
Question/Task:
Are there existing relations between parts of different installation locations inside a technical device
or subassembly due to their properties?
Example:
If the fuel pump with the material number FP01 is installed within the aircraft engine the fuel
withdrawal line must have the material number FWL01.
Possible approach:
Usage of the Set-Relationship approach.
Only available in the industry solution Aerospace & Defense.
Question/Task:
Which part of a technical device should participate at the checks of Configuration Control?
Example:
See ‘Possible approach’.
Possible approach:
Finally this depends at the use case and the industry sector where Configuration Control should be
used. An airline might have a different view which parts are worth to participate, e.g. because of
safety and reliability, than the manufacturer of an aircraft engine. One might have the view of the
operator and maintainer the other one of the producer.
In any case you should be aware of the amount of data to be processed by Configuration Control
and the resulting runtime. SAP note 1536543 [SAP N1536543] should give you an idea about this.
Page 15 of 177
5 Basic rules of modeling, the first example
5.1 General
In this chapter you should be made familiar with the basics how to model an MPL and how to link
this MPL to an actual structure of technical objects of a technical device.
The functionality of Configuration Control is not able to detect modeling issues! Any modeling
error inside the actual structure or the MLP can cause fussy results inside the resulting check list of
Configuration Control!
5.2 iPPE, Integrated Product- and Process-Engineering

The MPL is build up with the means of the iPPE (Integrated Product- and Process-Engineering).
You can use the Integrated Product and Process Engineering (iPPE) component to collect all the data
for an entire product life cycle in one integrated model. It is particularly suited to products with many
variants. You can use iPPE to document data, and later re-use and update it, from early phases of the
research and development process for a product. You can represent a complete production model
because Integrated Product and Process Engineering allows you to keep the master data for bill of
material (BOM) routings, and line design in one model. It is particularly suited to repetitive
manufacturing [SAP Help, iPPE].
Please keep mind that the MPL is only using a minor part of the mighty iPPE functionality. Not
everything allowed in the iPPE is allowed in the context of MPL modeling!
Building up a MPL is more or less respecting the specific rules of cook book which was once was
devised by the developers of the Configuration Control functionality!
5.3 The example

With the very easy example from Figure 7 we start to understand the basics of modeling a MPL.
Figure 7 First example to model a MPL
Page 16 of 177
An aircraft should be checked by the means of configuration control whether the correct materials
with the correct quantity are used for the fuel tanks and the tiers.
This aircraft must contain
 2 fuel tanks with the material number FT01

 2 tiers with the material number TR01
 Every tier has got 4 seats with the material number SEAT01
Please keep in mind that this example seems not to be quite realistic, but it should fulfill the needs
for a basic explanation of MPL creation.
5.4 Access node and product class

As formal starting point for the MPL we need an entry for the check into the iPPE. This is done by a so
called access node which presides over the subordinate MPL:
 The access node is used to link the current set of rules to an actual structure of technical
object which has to be checked by the MPL.
 The access node itself does not contain any information which is relevant for the check! It is
more or less the nut shell around the included set of rules.
Within Table 1 you find the necessary steps and basic rules to create an access node.
Step Action Comment

1 Create characteristics using the The characteristics might be used later on for the purpose of object
classification functionality dependency. In our example you might use them to characterize the
 Transaction CT04 aircraft type, e.g. long range, short range or freight version of the aircraft.
With this characteristic it is possible to judge inside one set of rules
between different aircraft types.
If you do not have the need to distinguish between different types, you do
not need to create characteristics.
See Figure 8.
2 Create a class with the class This class have to be used later on
type 300 (Variants) and assign  In the assignment of the configuration profile of the
the characteristics of step 1 configurable material (Step 3)
(when available) .  As product class inside the access node definition (Step 4)
 Transaction CL01
This step is mandatory!
See Figure 9.
3 Create a configurable material This configurable material is used later on
 Transaction MM01  as formal access variant inside the access node
 as carrier inside an equipment
o to link an actual technical object structure to a MPL
o to provide the MPL explosion with information about
the current shape (e.g. about the current aircraft type)
via variant configuration
See Figure 10.

4 Add configuration profile for Assign the variant class created with step 2 to the material created with
the material just created step 3.
 Transaction CU41
Page 17 of 177
See Figure 11.

5 Create the access node Within this step you have to provide the access node with
 Transaction PPE  a valid access node name. The node name has to be unique
(usage of A&D within the same client and used product class!
industry solution) or  the product class from step 2
 PDN (usage of  the access node variant using the configurable material created
enterprise extension) with step 3:
o Keep in mind that the used product class of the access
node and the variant class assigned to the
configurable material created with step 3 must be the
same!
o The configurable material can only be used one time
for one access node to define an access!
 an access definition. Use the ‘Copy Entry’-functionality to create
an access to the existing access variant. The usage of the access
must be ‘Engineering/design’ (ENG).
With this you allow the access from ‘outside’ to the included
MPL.
One MPL must contain exactly one access node at the top of the MPL!
When you create the access node

 choose ‘Product structure’ (CMP) as application
 choose ‘Product Variant Structure‘ as iPPE object type
 choose ‘Access Node’ (S_HD) as node type
See Figure 12, Figure 13, Figure 14.

Table 1 How to create an access node
Figure 8 to Figure 14 are showing the preparation and the definition of the access node for the
example.
Within Figure 8 some valid values for the characteristic AC_TYPE are defined. They will be used later
on in an example.
Figure 8 Create characteristic via transaction CT04
Page 18 of 177
Figure 9 Create variant class via transaction CL01 and assign characteristic
Figure 10 Create configurable material via transaction MM01
Page 19 of 177
Figure 11 Assign the variant class via configuration profile to configurable material via transaction CU41
Figure 12 Create an access node inside the transaction PPE or PDN
Page 20 of 177
Figure 13 Access node, create an access variant
Figure 14 Access node, access definition
5.5 Structure nodes, building up a structure inside the MPL

Within the next step we have to create the structure nodes below the access node. With the
structure nodes it is possible to create a structure in dependence on the structure of the actual
technical object structure to be checked.
Only structure nodes containing data relevant for the validation via Configuration Control!
Inside the structure node you list the materials which are valid for the corresponding part in the
actual structure. Each single material has to be mentioned in one separate variant of the structure
node.
The quantity of all structure node variants of one structure node must be identical.
If you’ve more than one variant at one structure node and the quantity is greater than one, the
corresponding parts in the actual structure can use the materials listed as variants in the structure
node; the material number must not be identical for the corresponding parts.
The materials used inside the structure node variants must contain a serial number profile to enable
the serialization procedure especially for material management actions and logistic processes like
goods movement! This is very important for
Page 21 of 177
 goods issues in combination with installing actions of a part

 dismantling actions in combination with goods receipts
e.g. via the transaction IE4N. Within Table 2 you find the necessary steps and basic rules to create a
structure node.
Step Action Comment

1 Create materials which should The materials to be created must contain a serial number profile to enable
be part of the validation via the serialization procedure at least for material management actions like
Configuration Control goods receipt and issue.
 Transaction MM01 to The material must not be a configurable material!
create a material
 Customizing Do not forget to maintain general plant data, sales- and distribution-data
transaction OIS2 for and accounting data (E.g. for the processing with transaction IE4N)
the serial number
profile This step is mandatory!
2 Create the structure node Within this step you have provide the structure node with
 Transaction PPE  a valid node name. The node name has to be unique within the
(usage of A&D same client and used product class!
industry solution) or  the same product class and class type as the access node
 PDN (usage of created before.
enterprise extension) In general structure nodes without product class are not allowed
within the MPL!
 One or more structure node variants using the materials created
with step 1. These materials are the valid materials allowed for
this current structure node:
o The same material can be used in structure node
variants more than one time at different structure
nodes inside the same MPL. But within a branch of a
MPL tree it is not allowed that a subordinate structure
node contains a structure node variant with the same
material number than the material number of a
structure node variant of a superior structure node!
o The same material can be used in structure node
variants more than one time at different structure
nodes inside different MPL
Assign the structure node to a superior node inside the current MPL. This
can be another structure node or the access node inside the MPL. It is not
allowed to assign a structure node inside a MPL more than one superior
node.
How to assign a structure node to a superior node?

 To assign the new structure node to a superior node you can
enter the name inside the tab strip ‘Relationship‘.
 Figure 15 is showing a way to create and assign a structure node
in one step:
o Mark the superior node
o Press the right mouse button to reach the context
menu.
o Choose <Create Relatshp>
o Choose <Structure Node>
o Enter the structure node data
When you create the structure node

 choose ‘Structure Node’ (S_ST) as node type

Table 2 How to create a structure node
Page 22 of 177
For our example the materials
 FT01 (FUEL TANK 01, 5000L)

 FT02 (FUEL TANK 02, 8000L)
 TR01 (TIER 01, 2*2 SEATS)
 TR02 (TIER 02, 2*3 SEATS)
 SEAT01 (SEAT 01)
were created. Please don’t mind about the additional materials FT02 and TR02. We need them later
for further explanations.
Figure 15 is showing how to create a structure node and how to assign it to a superior node in one
step. To reach this
1. you’ve to mark the node where you want to assign a subordinate note.
2. Than press the right mouse button to reach the show context menu.
Figure 15 Create and assign a structure node
Figure 16 is showing the complete MPL of the example inside transaction PPE or PDN.
Figure 16 The MPL defined by means of iPPE
Within Figure 17 you can find an overview over the created MPL with all relevant data.
Page 23 of 177
Figure 17 Complete MPL for the example
5.6 Building up the actual structure

5.6.1 General remarks
Within the next step the structure to be checked is set up.
This structure can contain technical objects like functional locations, equipment and special Bill-Of-
Material-items (BOM). The usage of special BOM-items is available since EhP2.
While functional locations are ‘only used’ to structure the actual structure, only equipment and BOM
items are relevant for the check of Configuration Control! This means, functional locations are not
part of the check!
It is very important, that this structure fulfill the needs of Configuration Control! Normally it is pretty
complex to adopt existing, old structures of technical objects to the needs of Configuration Control.
Within the first example we only use equipment to gain the basic knowledge of modeling.
5.6.2 Top equipment, hard link to the corresponding set of rules

The top equipment is the formal partner of the access node inside the MPL. This equipment is used
to guarantee the link between its subordinate objects – installed equipment and special BOM items –
and the access node inside the corresponding MPL.
Furthermore this equipment is very important to provide the filter data for the explosion of the MPL.
We will see this later in the chapters concerning
 object dependency and

 parameter effectivity.
Only by this equipment this data can be provided! It presides the subordinate technical structure.
This equipment is not part of the check of Configuration Control!
Table 3 is showing the basic rules how to create the top equipment.
Page 24 of 177
Step Action Comment

1 Create an equipment which A view should be used where the following tab strips for the equipment
should be the link to the transactions are visible:
corresponding MPL.  Configuration Data
 Transaction IE01  Configuration Control
create the equipment  SerData (for material and serial number)
 Transaction IE02 to
change the Within the tab strip
equipment  ‘Configuration Data’, enter the number of the configurable
material. Use the material you’ve created within chapter 5.4.
This material contains within its configuration profile the same
class as the MPL you’ve created within chapter 5.4 and 5.5. This
formal step is absolutely essential to link the actual structure to
the MPL!
 ‘Configuration Control’, you perform the real linkage to the MPL.
Using the configurable material and its (product) class entered
before on the tab strip ‘Configuration Data’ the iPPE nodes are
scanned to find access nodes with the same configurable
material-product class-combination inside the access
information. If found, a list is shown, where you can choose the
access node you want to link the current equipment with. This
link – the internal node number of the access node - is stored
inside the equipment data. Therefore this link is called hard link.
On the ‘Configuration Control’ tab strip press in the screen area
‘iPPE Access Information’ the button to perform the iPPE access
and choose the corresponding entry in the popup.
Anytime you change the configurable material on the tab strip
‘Configuration Data’, you must manually delete the assignment
to the access node and to reassign it to an access node that fits!
See Figure 18 to Figure 19.

Table 3 How to create a top equipment
Add configurable material
Figure 18 Inside the tab strip ‘Configuration data’ of the top equipment
Page 25 of 177
Figure 19 Create the assignment to the access node inside the tab strip ‘Configuration Control’
5.6.3 Equipment relevant for the check of Configuration Control

Within the next step the actual structure below the top equipment is build up.
These equipment are relevant for the checks of Configuration Control. By standard the following
checks will be performed inside the Configuration Control Workbench (Transaction CCM2):
 Used material number inside the installed equipment against the material number inside the
MPL
 Quantity of the installed equipment against the desired quantity of the material inside the
MPL. Every single equipment counts as one piece in the quantity check!
 Installation location in comparison to the MPL structure
Only equipment installed below the top equipment are part of the check! We will see later on how
this is working, when we are using functional location for structuring purpose. At the moment we use
a pure equipment structure.
These equipment are part of maintenance, repair and overhaul process. Whitin this process this
equipment are dismantled from and installed into the actual structure.
Page 26 of 177
The material number of the equipment to be checked by Configuration Control is part of the serial
number data of the equipment. Providing also a valid value for the serial number for the material
number the equipment can take part in the logistic processes like a goods movement.
With this data the transaction IE4N can be used to perform the installation or dismantling together
with a goods movement.
Step Action Comment

should be relevant for the transactions are visible:
checks of Configuration  Configuration Data
Control.  Configuration Control
 Transaction IE01  SerData (for material and serial number)
create the equipment
 Transaction IE02 to Within the tab strip
change the  ‘Configuration Control’, you perform the linkage to the
equipment corresponding structure node inside the MPL assigned via the
top equipment.
To reach this the Functional Identifier (FID) is introduced as
additional equipment data. This FID is a free text field without
any checks behind when entering it, but it has to correspond to
the MPL structure node which is containing the rule – the valid
material numbers – for the equipment to be checked. This
means that the FID on the equipment side is the name of the
structure node on the MPL side.
The link via the FID to the structure node is called soft link as
the readable structure node name is stored and not the internal
node number – the primary key- of the structure node. This soft
link is used to allow the installation of the equipment across all
technical object structures below any top equipment. These top
equipment might be assigned to different access nodes. Within
the different MPLs it might be possible that there are existing
structure nodes with the same node name and material
numbers within their variants.
From a business point of view the FID represents the form, fit
and function of a part inside a technical structure.
Within the Configuration Control standard application
Equipment without FID are not allowed! The only exception is
the top equipment with the link to the MPL access node.
 ‘SerData’ you’ve to enter the material number of the
equipment. This material number is checked against the
material number of the structure node variant of the
corresponding structure node.
If the equipment should be part of a logistic process like a goods
movement, a serial number must also be provided. The
combination of the material- and serial number on this tab strip
is used for logistic processes e.g. goods movement if the
material is serialized.
Installation of the equipment:

As the equipment is part of an actual structure of a technical
object, it has to be installed at the corresponding installation
location of the structure of the technical object.
See Figure 20.

Table 4 How to create an equipment that is relevant for the check.
Page 27 of 177
Figure 20 Equipment representing the fuel tank inside the technical object structure
Figure 20 is showing an equipment representing the fuel tank inside the aircraft to be checked by the
rules of the structure node SN_FT. Due to the mentioned soft link via the FID the related structure
node can be located in different MPLs.
Figure 21 is showing the complete actual technical structure of the aircraft 01 which only contains
equipment in this example.
Page 28 of 177
Figure 21 Complete actual technical object structure for the aircraft 01
5.6.4 Configuration check with transaction CCM2

Whit all this data we are able to start the configuration check the first time. We do this by using the
transaction CCM2. Figure 22 is showing how to start the transaction CCM2 with our example from
above. Entering the technical object to start the check with and pressing the [Load]-button is reading
the actual structure. If the technical object entered is no equipment with link to a MPL access node,
the functionality is searching up the tree of technical objects in a predefined manner to find a proper
equipment with access information to the MPL. Only with this access information it is possible to find
the MPL to be used for the check. Pressing the [Check]-button the check against the MPL take place.
Within Figure 23 you can see the result of the check.
Page 29 of 177
Figure 22 Start configuration check with transaction CCM2
Figure 23 Result of the first check within transaction CCM2
The warning message
Not all objects in FID group have the same superordinate equipment (Message no.
CCMM035)
indicate correctly that the equipment listed are installed into two different installation locations:
Equipment ETR01 and ETR02.
Page 30 of 177
5.6.5 Multiple usage of a MPL

So far we have assigned only one equipment EAC01-01, which is standing for aircraft 01 to the MPL.
But what about the fact, that we have more than one aircraft of the same type as aircraft 01? How to
check these technical devices? Do we need to have a separate MPL for every aircraft?
If the aircrafts are pretty identical, e.g. if they have the same type, we can use the same MPL. We will
see later, how we can distinguish between the individual aircrafts and their special characteristics
within one MPL. Figure 24 is showing the multiple usage of one MPL for the aircraft 01, 02 and 03.
With this technique you might be able to reduce the data maintenance effort.
Figure 24 Multiple usage of one MPL
5.6.6 The three steps of Configuration Control

Within Figure 25 the three steps of the way how Configuration Control is working is shown.
Within step 1 the actual structure is read starting with the top equipment that contains the link to
the access node of the MPL.
Within step 2, which is the most complex one, the MPL is read, making use of
 filter criteria given by the top equipment,

 set relationship functionality
 interchangeability.
Page 31 of 177
These three points are explained later.
In the step 3 the check takes place which is performing
 the FID grouping of the technical objects (e.g. equipment)

 the validity check of the used materials and quantity of the installed technical objects inside
the actual structure.
 The structural check concerning the installation location.
Figure 25 Three steps in the processing of Configuration Control Workbench
Please don’t mind about the mentioned topics Figure 25 we did not discuss so far. This is done the
following chapters.
5.6.7 FID grouping (1), interpretation of the actual structure for Configuration Control
purpose
The FID grouping is taking place in the check part of configuration control after the actual structure
and the MPL were read.
To be able to compare the actual structure and the MPL the FIDs of the equipment and BOM items
 are grouped by their FID.

 are used to create a parent-child relationship between the technical objects.
This is necessary to make the actual structure comparable to the MPL structure nodes names and its’
variant and structural information.
At the moment we should concentrate on pure equipment structures and how they are exploded
concentrating on FID inside the equipment.
Page 32 of 177
Figure 26 is showing the determination of the FID of the superior technical object, the so called
parent FID.
Figure 26 Interpretation of the equipment structure respecting the FID
As result of the interpretation shown in Figure 26 we get the information related to the FID shown in
Figure 27. All the relevant technical objects (here equipment) are grouped by their FID. This means
 the FID-Group for SN_FT contains the equipment EFT01 and EFT02
 the FID-Group for SN_TR contains the equipment ETR01 and ETR02
 the FID-Group for SN_SEAT contains the equipment ESEAT01, …, ESEAT08
Figure 27 Parent FID and FID-grouping
Page 33 of 177
Furthermore we know that the ‘FID’ of the related superior object of equipment EFT01 is EAC01-01.
As the top equipment does not contain a FID information, the MPL node name of the access node is
taken over in a formal way.
For equipment ESEAT05 the FID of the related superior object is SN_TR. As result we get a similar
structure as show in Figure 17.
With this information we are able to perform the check against the MPL. Figure 28 is showing the
result in another way.
Figure 28 Actual structure grouped by FID and Parent
You might ask: Why do I need to know this? The FID-grouping of the actual structure is essential for
the checks in Configuration Control. And it has an influence on the check result. Please keep in mind
that the FIDs are nothing else than the structure node (names) inside the MPL.
Knowing the FID-grouping you might be able to interpret the results of the checks in a better way.
Furthermore the FID-grouping has an influence on the quantity check.
Let’s assume we want to check the equipment for FID group SN_SEAT:
The corresponding structure node SN_SEAT provides us
1. with the expected material number SEAT01 (Rule 1)

2. with the parent FID SN_TR (Rule 2)
3. with the expected quantity of 8 objects (Rule 3)
Page 34 of 177
With this information we can check equipment by equipment that all equipment with the FID
SN_SEAT are respecting the rules 1 and 2 of the structure node SN_SEAT:
 every equipment has got the material number SEAT01

 every equipment has got a superior equipment with the FID SN_TR
What about the quantity of 8? Looking at the MPL, the structure node SN_SEAT has a quantity of 4.
The superior structure node SN_TR has a quantity of 2. This means for the check a required amount
of 2*4 = 8 objects (here equipment) with the material number SEAT01 and the FID SN_SEAT. The
superior node of structure node SN_TR in the MPL is the access node AN_AC01 which does not
contribute at the quantity check. If we count the relevant equipment, we find 8 pieces. With this the
quantity check is passed.
6 View nodes and functional locations

6.1 Motivation
Beside the technical objects in the actual structure - so far we know equipment - which needs to be
checked by Configuration Control there might be the need to provide the actual structure and the set
of rules (MPL) with structural units to make it better to be read and understand. For this purpose
 functional locations in the actual structures

 view nodes in the MPL
can be used.
As mentioned in chapter 5.6.1, only equipment and special BOM items are relevant for the check!
View nodes and functional locations are not part of the check!
6.2 The example

The example for chapter 5.3 should be structured as shown in Figure 29.
Page 35 of 177
Figure 29 Structuring of the actual structure of aircraft 01
Using functional locations the Aircraft 01 should be structured into the following structural units
inside the actual structure:
 The whole aircraft 01: FLAC01

 Passengers cabin of aircraft 01: FLAC01 -CABIN
 Tier 01 in passengers cabin: FLAC01 -CABIN -TR01
 Tier 02 in passengers cabin: FLAC01 -CABIN -TR02
 Left Wing of aircraft 01: FLAC01 -LWING
 Right Wing of aircraft 01: FLAC01 -RWING
Please see chapter 3.1 for the meaning of the functional location which is used to be the structural
unit here. Often such a structuring is mandatory in specific industries when you model technical
structures by means of digital data processing. One example are the ATA chapters (ATA = Air
Transport Association, Airlines for America [A4A]) for aircraft operating companies.
Within the corresponding MPL we want to have the following structural units:
 Passengers cabin of aircraft: VN_CABIN

 Tiers inside the passengers cabin: VN_CABIN_TIER
 Wings of aircraft: VN_WING
Page 36 of 177
A structural unit for the aircraft is not necessary as the access node AN_AC01 is used for this
purpose.
6.3 Functional locations

6.3.1 The very top functional location
The most top functional location has an important meaning inside the whole structure. Within this
functional location the top equipment must be installed! The top equipment is the equipment with
the link to the access node of the corresponding MPL.
It is not allowed to have any additional top equipment installed at that functional location or at this
structure level!
It is not allowed to have any further equipment installed at this level!
Anyhow, functional locations do not contain any Configuration Control relevant information.
6.3.2 Functional locations as installation location for equipment

There does exist the following modeling rules for functional locations which are not the very top
functional location inside Configuration Control:
 Functional locations needn’t have a installed equipment

 Within functional locations you are allowed to install one single equipment!
6.3.3 Meaning of structure levels

It is pretty important to understand that the functional locations are used as formal structuring units
inside the Configuration Control context. While Configuration Control validates the actual structure
the functional locations are formally faded out! Only the very top functional location with the
installed top equipment has got an exceptional meaning.
In Figure 30 you can find the enhanced actual structure as requested.
Page 37 of 177
Figure 30 Actual structure with functional locations
6.3.4 FID Grouping (2), influence of functional locations

Figure 31 is showing the complete process of the determination of the parent FID within the FID
grouping (please see Figure 26 in addition).
Page 38 of 177
Figure 31 Interpretation of the technical object structure respecting the FID, find parent FID
This mechanism is pretty important for the structuring of the actual structure and how it is
interpreted by Configuration Control. Later we will see an example which is modeled in a wrong way.
A wrong usage of functional locations can cause fuzzy check results in Configuration Control. A
example can be found in chapter 6.3.5.
At the moment we do not use view nodes in the MPL.
The result of the FID-grouping is the same as shown in the Figure 27 and Figure 28!
The result for the check of this actual structure (see Figure 30) with Configuration Control does not
differ to Figure 23 (see Figure 32).
Page 39 of 177
Figure 32 Check results with functional locations within transaction CCM2
6.3.5 Wrong usage of functional locations, error message CCMM047

Within our current example we’ve installed the equipment ESEAT01, ESEAT02, ESEAT03 and ESEAT04
into the equipment ETR01. Now we perform some changes at the actual structure. These four seats
should now be installed into the new functional location FLAC01 -CABIN -TR01SEAT. This functional
location is assigned to functional location FLAC01 -CABIN -TR01. Figure 33 and Figure 34 are
showing the changed structure. From a business point of view this does not make any sense, but the
example should show the wrong usage of functional locations and its influence on the FID grouping
and parent FID determination.
Within Figure 35 the result of the parent FID determination by the method introduced in Figure 31 is
shown. For the equipment ESEAT01, ESEAT02, ESEAT03 and ESEAT04 the parent FID is now EAC01-
01. This is wrong. Concerning the MPL the parent node of the node SN_SEAT is SN_TR! That means,
the parent FID of an equipment with the FID SN_SEAT must be SN_TR. Figure 36 is showing Within
the result of the check. The error message
Function identifiers of superior objects do not correspond at Equipment ESEAT01 (Message

no. CCMM047)
indicates the modeling error of the actual structure. Same is valid for the equipment ESEAT02,
ESEAT03 and ESEAT04.
Page 40 of 177
Figure 33 New functional location FLAC01 -CABIN -TR01SEAT; overview
Figure 34 New functional location FLAC01 -CABIN -TR01SEAT; complete structure
Page 41 of 177
Figure 35 Parent FID determination
Figure 36 Result of check within transaction CCM2
6.3.6 Determination of top equipment with link to MPL access node, error message
CCMM021
In some cases you get the error message
There is no top item of equipment (Message no. CCMM021).
This message indicates a modeling error in your actual structure.
Page 42 of 177
A very important step within Configuration Control is the determination of the top equipment within
an actual structure. This top equipment provides the Configuration Control how the MPL should be
exploded. This is done by
 the variant configuration data or

 the ECM data
of the top equipment. We will learn the meaning of both in one of the following chapters.
The rules of chapter 6.3.1 and 6.3.2 have to be respected. The mechanism shown in Figure 37 is more
or less also used to determine the top equipment and the link to the access node.
Figure 37 Determination of top equipment
Please use the mechanism shown in Figure 37 to validate your actual structure.
The SAP note 1515830 [SAP N1515830] provides additional information.
Table 5 is showing some valid and invalid actual structures concerning the rules shown in Figure 37
Page 43 of 177
Example Remark
This structure is valid. By the rules of Figure 37
the top equipment E1 with the link to the MPL
access node can be found.
This structure is valid. By the rules of Figure 37

the top equipment E1 with the link to the MPL
access node can be found.
This structure is invalid. The top equipment E1 is

not installed in FL1 and cannot be found by the
rules of Figure 37.
This structure is invalid. There doesn’t exist a top

equipment for equipment E4 that can be found
by the rules of Figure 37.
Legend:
Table 5 Valid and invalid examples
Anyhow it is not allowed to have more than one top equipment installed at a functional location!
This is because the top equipment presides the subordinate technical structure.
Page 44 of 177
6.4 View nodes

On MPL side we can use so called view nodes to structure a MPL. View nodes are iPPE nodes without
any material variant. In opposite to structure nodes they do not contain any rule relevant data. Inside
the MPL they take over more or less the role of the functional locations used inside the actual
structure.
6.4.2 Rules on relations between different types of MPL nodes

Due to this there are the following basic modeling rules for access nodes, structure nodes and view
nodes:
 Access nodes:
o An access node is the most top node of a MPL
o It is not allowed to assign an access node to a superior structure node
o It is not allowed to assign an access node to a superior view node
 Structure nodes:
o A structure node can be assigned to a superior access node
o A structure node can be assigned to superior structure node
o A structure node can be assigned to superior view node
 View node:
o A view node can be assigned to a superior access node
o A view node can be assigned to superior view node
o It is not allowed to assign a view node to a superior structure node! This can be
compared to functional locations in the actual structure; you are not allowed to
‘install’ a functional location into a superior equipment.
6.4.3 Attributes of a view node

Figure 38 is showing the attribute of a view note. Class and class type must be the same as of access
node and structure node.
Figure 38 Create a view node
Page 45 of 177
6.4.4 Final rules for the determination of the parent MPL node, error message CCMM047
The usage of view nodes have an influence on the determination of the parent node name of a
structure node! Figure 39 is showing how the parent node of a structure node is determined. Finally
this method is used to extract the structure relevant for the check.
Figure 39 Determination of the parent node names
Table 6 is showing some examples how this extraction is working. It is pretty important to
understand this extraction of the structure nodes and the related parent nodes as this information is
part of the configuration check.
Let’s have a look at the second example in Table 6:
If the actual structure contains an equipment XYZ with the FID SN3, this equipment must be
installed into an equipment with the FID SN2! If the equipment with the FID SN3 does not
meet this rule the error message
Function identifiers of superior objects do not correspond at Equipment XYZ (Message

no. CCMM047)
is raised for this equipment.
Page 46 of 177
Example Modeled MPL Extracted MPL relevant for check

1
Legend:
Table 6 Example for MPL extraction
Figure 40 is showing our aircraft example with view nodes inside the MPL and the extracted MPL
structure inside the configuration check.
Page 47 of 177
Figure 40 Aircraft example with view nodes
The major disadvantage of view nodes is that they increase the runtime of the MPL explosion (Step 2
in Figure 25). Because of this it is recommended to reduce the usage of the view nodes to a
minimum.
7 iPPE node types, usage for modelling the MPL

The explanations of this chapter came from the SAP course WDECCT 'Anlagenkonfiguration' which is
only available in German at the moment [SAP course WDECCT].
First of we must be clear of the fact what iPPE stands for. It is Integrated Product and Process
Engineering. Using the iPPE tool the structure of a product with all its variants can be modeled from
perspective of construction. The main goal is to have a description of the product and its variants
free of redundancy which can be used in the following processes of production and service.
From the maintenance perspective a set of rules - the MPL-should be set up.
Basically the iPPE should support the complete lifecycle of a product
 Development of the product

 Process planning for production
 Service for delivered products
by managing the attributes and the structure of a product. Using the industry solution Discrete
Industries & Mill Products process data can be modeled as well.
Page 48 of 177
Therefor iPPE is using three applications types:
 CMP Components for product data and structures

 ACT Activities
 FLO Factory Layout
Within Configuration Control we use the iPPE application CMP to build up the MPL. For production
an planning purpose a product structure is build using the application CMP, too. With this a so called
Product Variant Structure (PVS) is build.
Both, MPL and PVS, are using the same node types within the application CMP. These node types
are:
 Access node
 Structure node
 View nodes.
It might be possible that technical structure like an aircraft is modelled within the PSV for production
purpose. This structure is very detailed to satisfy the production needs.
Within the MPL we do not need all the production relevant parts. Only maintenance and security
relevant parts should be part of the MPL.
If we use MPL and PVS in the same system this might lead to problems within the Material Resource
Planning (MRP) as also the node of the MPL taking part although they are not relevant for
production. Therefore iPPE data in the area of construction/production and maintenance should
strictly be separated in order not to disturb follow-up-processes (like MRP for production and
recursion checks).
Due to the rules of the iPPE node type for the application CMP it is also not possible to us the same
materials inside an equipment BOM and a iPPE structure node variant.
Within this document we use the same standard node types for the MPL as used in the PVS. For this
document we act under the assumption, that in the system or client we create our MPL no
production relevant PVS does exist!
With ERP 6.0 Ehp4 new node types for the MPL are introduced for the application CMP. These node
types should only be used for MPL modelling within iPPE. With these new node types it is possible to
clearly separate the MPL from the PVS inside the same system! With this node types it is possible it is
possible to use the same materials inside the equipment BOM and the iPPE structure node variants.
With the standard iPPE node types this is not possible. Figure 41 is showing the new node types since
EhP4.
Page 49 of 177
Figure 41 New node type since EhP4
To make use of the new node types within EhP4, you have to turn on the LOG_EAM_CC business
function, and make sure, that you have EA_IPPE-404 installed beforehand. iPPE made some
developments in EhP4, which are prerequisites for this function. You should use the new MPL node
types in iPPE to avoid the conflicts with BOM using the same materials. You can use the report
PPE_CONVERT_PVS_MPL to convert your "old" iPPE structures to the new MPL structure. Please
consider the specific behaviour of this report! You can find further information in [SAP Help,
Conversion of Standard iPPE Structures].
8 Productive usage of Configuration Control

8.1 General
So far we’ve learned the basics to model a MPL and the corresponding actual structure. These basics
are pretty relevant for the initial setup of the two data structures. Before we are going to discuss
further possibilities of data modeling, we have a look at the productive usage of the data which
we’ve set up before. We have a look at
 the transaction IE4N (installation/dismantling with or without goods movement)

 Common error messages of the transaction CCM2 (Configuration Control Workbench) while
the maintenance process
 local check of Configuration Control inside IE4N
 structure gaps.
The chapter 7 concentrates on the Configuration Control relevant Parts of transaction IE4N.
Page 50 of 177
8.2 Transaction IE4N, installation/dismantling with or without goods

movement
While maintaining a technical device like an aircraft, parts are dismantled and/or installed and put
to/taken from stock. This is done to overhaul or inspect parts, replace defect parts and install new
parts. These parts might be modeled in the SAP system as equipment or serialized equipment when
you want to perform logistic processes (e.g. a goods issue or receipt) as well.
In opposite to the classical transactions of the plant maintenance functionality of SAP to install or
dismantle equipment/serialized equipment like IE01, IE02, IQ01, IQ02 which are only able to perform
the pure installation/dismantling, the transaction IE4N is able to
 installation/dismantling with measurement point linkage and measurement point document

transfer
 perform the local check of configuration control
 create structure gaps when a part is dismantled
 create/change an notification on the performed action
 ‘installation/dismantling’ parts into/from a special type of equipment related bill of material
(BOM), (since EhP2)
If you want to make use of the Configuration Control functionality, you have to use the transaction
IE4N for any dismantling and installing actions.
8.3 Structure Gaps

8.3.1 General
The structure gap was introduced with the Configuration Control functionality.
The structure gap is a flag or placeholder for a dismantled part.
The structure gap is also included into the checks of Configuration Control. Within the checks the
structure gap indicates the missing, dismantled parts.
The information of the structure gap can be used inside the installation process of transaction IE4N
to gain knowledge about:
 Possible installation location, when the equipment number or the material/serial-number

combination of the part to be installed is known.
 Possible and allowed material number of a part/equipment, if the installation location is
known.
The structure gap is also part of the quantity check in the Configuration Control Workbench. If the
expected quantity of installed parts in an installation location is two for example and there does exist
a structure gap and a installed equipment for this installation location, no quantity error message
occurs. The additional message
Structure gap at Functional Location/Equipment <object number> (Message no. CCMM041)
indicates the existence of the gap.
Page 51 of 177
If the expected quantity of installed parts in an installation location is one for example and there
does exist a structure gap and a installed equipment for this installation location, a quantity error
message occurs:
<n> object(s) found below superior object <object number>. Expected quantity is <m> PC
(Message no. CCMM033)
Furthermore the Information for the structure gap is used to adjust the FID information of the part to
be installed. If the FID of the part to be installed does not fit to the FID of the structure gap, the FID
of the part to be installed is adjusted to the FID of the structure gap.
8.3.2 Content
A structure gap contains the following data:
 Primary key of structure gap

 Data of the installation location/Superior object:
o Object number of the installation location/superior object
o Equipment position at installation location/superior object
 Dismantled object:
o Functional identifier of the dismantled object (equipment or BOM item)
o Material Number of the dismantled object (equipment or BOM item)
o Object number of the dismantled equipment
o BOM item relevant data:
 Quantity of missing parts per item
 Unit of measure of item
 Item node number
 Equipment Bill of Material Indicator
 Item Number
 Administrative data:
o Creation date of structure gap
o Creator of structure gap
o Change data of structure gap
o Changed by
The data of a structure gap is located in the table CCMHOLE.
8.3.3 Creation, Deletion, Adjustment

A structure gap is created or adjusted
 whenever you dismantle an equipment with transaction IE4N

 whenever you ‘dismantle’ parts from a special type of equipment related bill of material
(BOM) with transaction IE4N by reducing the quantity of a BOM item, (since EhP2)
 whenever you create a structure gap manually via transaction CCM2
A structure gap is deleted or adjusted
 whenever you install an equipment with transaction IE4N
Page 52 of 177
 whenever you ‘install’ parts into a special type of equipment related bill of material (BOM)
with transaction IE4N by increasing the quantity of a BOM item, (since EhP2)
 whenever you delete a structure gap manually via transaction CCM2
8.4 Dismantling equipment with IE4N

8.4.1 General
Dismantling an equipment with transaction IE4N, this transaction is performing the following actions:
 Dismantle the equipment from the installation location and release the measurement
document transfer.
 Performing a goods receipt if required by the chosen IE4N dismantling action for the
serialized equipment which is dismantled.
 Create a structure gap to memorize the installation location and the equipment formerly
installed with all its’ data (e.g. object number of the equipment, material number and FID).
 Create/change a notification for the dismantling action.
8.4.2 Example
With the following example we concentrate on the behavior of the Configuration Control Workbench
checking a structure where a dismantling takes place before.
Within our known and so far correct aircraft example (functional location FLAC01) we dismantle
equipment ESEAT04 from equipment ETR01 using the transaction IE4N (see Figure 42).
Figure 42 Dismantling via IE4N
Page 53 of 177
If we now start transaction CCM2 to check the actual structure against the MPL, we get the following
result (see Figure 43):
Figure 43 Configuration Control check with transaction CCM2 after dismantling of equipment ESEAT04
The message
Structure gap at Equipment ETR01 (Message No. CCMM041)
indicates that a part is missing inside the actual structure.
In the next step we dismantle the fuel tank EFT01 with transaction IE4N (see Figure 44). The message
Structure gap at Functional Location FLAC01 –LWING (Message No. CCMM041)
indicates this action.
Page 54 of 177
Figure 44 Configuration Control check with transaction CCM2 after dismantling of equipment EFT01
8.5 Installing equipment with IE4N

8.5.1 General
Installing an equipment with transaction IE4N, this transaction is performing the following actions:
 Installing the equipment into the installation location and connect measurement points and
counters for the measurement document transfer between the installation location and the
installed equipment.
 Performing a goods issue if required by the chosen IE4N installing action for the serialized
equipment which is installed.
 Delete the corresponding structure gap of the installation location for the installed
equipment.
 Create/change a notification for the installing action.
 Perform the Configuration Control local check
8.5.2 Local check and forced installation

The local check of Configuration Control is part of the installation process of the transaction IE4N.
In opposite to the checks inside the transaction CCM2 (Configuration Control Workbench) this check
only performs a check, whether the material number of the part to be installed reflects a material
number given in the corresponding MPL-structure-node.
Checks, that make it necessary to explode or analyze the complete MPL or actual structure as
Page 55 of 177
 Quantity checks,
 Checks from Set-Relationship,
are not performed! This is because of the runtime of transaction IE4N.
Figure 45 is giving an overview of the local check.
Figure 45 Local Check of Configuration Control in IE4N
The methodology to determine of the top equipment within Step 1 can be found in Figure 37.
If the material of the installed part/equipment does not fit an error message does occur. This error
message is preventing transaction IE4N to install this wrong part/equipment.
You can overrule the result of this check and install the wrong part/equipment by the forced
installation functionality of transaction IE4N. The fact that you’ve performed a forced installation is
memorized in the equipment data. When you check the actual structure with the Configuration
Control Workbench (transaction CCM2) an error message indicates the part with the wrong material
number and the forced installation.
8.5.3 Examples
With the following examples we try to get knowledge how IE4N and CCM2 reacts on different
common situations. We again change the actual structure of aircraft starting with functional location
step by step.
8.5.3.1 Installation in an installation location without structure gap

By accident we install the equipment EASEAT04 under the equipment EATR02.
Page 56 of 177
Figure 46 Message by structure gap evaluation of IE4N
In Figure 46 the message CCMM128 indicates that an installation should take place at an installation
location where no part was dismantled beforehand. If you confirm the warning message and save the
changes, the equipment EASEAT04 is installed into equipment ETR02.
Figure 47 is showing the log of IE4N after the successful installation. The messages CCMM028,
CCMM149 and CCMM162 indicates the installation without structure gap.
Performing the configuration check with transaction CCM2, we get the message CCMM033, as the
amount of installed parts in equipment ETR02 is 5 where 4 seats are expected (see Figure 48):
5 object(s) found below superior object ETR02. Expected quantity is 4 PC (Message no.
CCMM033)
Page 57 of 177
Figure 47 Log of IE4N after installation performed
Figure 48 Configuration Control check with transaction CCM2 after installing equipment ESEAT04
Page 58 of 177
8.5.3.2 Dismantling of an equipment, Structure gap is also part of the quantity check
Within the next step we dismantle the equipment ESEAT04 that we installed by mistake with
transaction IE4N. During the dismantling again at structure gap for the installation location ETR02 is
created. Figure 49 is showing the check in transaction CCM2. The structure gap created by the
preceding dismantling of equipment ESEAT04 is also taken into account into the quantity check for
the parts/equipment installed into the equipment ETR02. Because of this we get the error message
CCMM033, again (see Figure 49).
Figure 49 Configuration Control check with transaction CCM2 after dismantling equipment ESEAT04 again
8.5.3.3 Manipulating a structure gap

In the next step we want to get rid of the ‘wrong’ structure gap at equipment ETR02.
To manipulate a structure gap you’ve to use the transaction CCM2. With this transaction it is possible
 Create a new structure gap for an installation location like a functional location or an
equipment.
 Delete an existing structure gap.
 Change content of a structure gap.
Figure 50 is showing the way to delete a structure gap.
Page 59 of 177
Figure 50 Delete a structure gap
8.5.3.4 Installation of a part with a wrong material number and a corresponding FID
We start this installation with the actual structure given in Figure 44.
We try to install the equipment WRONG01 with the material number WRONGMAT and serial number
1 into the functional location FLAC01 -LWING with transaction IE4N. The FID of this part is SN_FT.
There does exist a structure gap for this installation location.
The first try failed because of the rules coming from the MPL: A part with the FID SN_FT must have
the material number FT01!
Figure 51 is showing the error messages
Material WRONGMAT of Equipment WRONG01 is not valid (Message no. CCMM031)
coming up at the first try. With this the option to perform a forced installation is offered.
Message
Structure gap can be deleted at funct.loc. FLAC01 -LWING (Message no. CCMM280)
indicating, that despite the wrong material number the structure gap will be deleted by process of
forced installation.
Page 60 of 177
Figure 51 Install a part with a wrong material number
We activate the forced installation functionality and perform the installation. Error! Reference
ource not found. is showing the log after the forced installation.
The fact that you’ve performed a forced installation is notified in the equipment time segment which
is relevant for the installation (see Figure 53).
Figure 54 is showing the corresponding messages of transaction CCM2 after the forced installation.
Because of the fact that the installed equipment WRONG01 contains a wrong material number
WRONGMAT, which is indicated by message
Equipment WRONG01 (forced installation mode). Material WRONGMAT is not valid (Message
no. CCMM031)
a quantity check is not possible by Configuration Control Functionality for the equipment with the
FID SN_FT. This is indicated by the message
Quantity has not been checked (Message no. CCMM050).
Page 61 of 177
Figure 52 Messages when forced installation took place
Figure 53 Indicator for forced installation
Page 62 of 177
Figure 54 Log of transaction CCM2
8.5.3.5 Dismantling of a wrong part

In the next step we dismantle the wrong part/equipment WRONG01 from the functional location
FLAC01 -LWING with transaction IE4N. The result is again a structure gap at the functional location
FLAC01 -LWING. Within Figure 55 the result of the Configuration Check can be seen. The message
Material WRONGMAT of Structure Gap (Functional Location FLAC01 -LWING) is not valid
(Message no. CCMM031)
is indicating the fact, that a wrong part was installed before.
Page 63 of 177
Figure 55 Log of transaction CCM2 after dismantling of a wrong part
8.5.3.6 Installation of a part with a correct material number but a wrong FID
We now try to install the equipment WRONG02 with the correct material number FT01 and serial
number 3 into the functional location FLAC01 -LWING with transaction IE4N. The FID of this part is
SN_WRONG, which does not correspond to the information inside the structure gap at the functional
location FLAC01 -LWING.
Figure 56 is showing the log of transaction IE4N if we try to perform this installation. As shown in
chapter 8.5.3.4 we have to perform a forced installation. As result the FID of the equipment
WRONG02 is adjusted from the wrong value SN_WRONG to the correct value SN_FT when you save
the data of the forced installation (see Figure 57).
You can find the same behavior, when you try to install a part with a missing FID. Precondition is an
existing structure gap for the installation location.
Figure 58 is showing the result of the Configuration Control functionality using transaction CCM2.
Page 64 of 177
Figure 56 Log of transaction IE4N after the try to install a part with a wrong FID
Figure 57 Adjusted FID
Page 65 of 177
Figure 58 Log of transaction CCM2 after dismantling of a wrong part
8.5.3.7 Other important messages in the process

During the usage of the transaction IE4N and CCM2 there are some other messages which might
came up:
 No iPPE structure found for FID <FID-Number> and class <class name/class type> (Message
no. CCMM254)
This message came up within the installation process of transaction IE4N when the FID of the
structure gap is wrong
 No corresponding iPPE structure node found for function identifier (Message no. CCMM045)
This Message came up within CCM2 when an installed part (e.g. an equipment) has got a FID
which is unknown in the MPL.
Page 66 of 177
9 Usage of bill of material (BOM)
9.1 General
So far we get knowledge about the equipment as relevant part of the validation check of the
Configuration Control functionality.
Often you have the requirement to check the validity of parts inside an actual structure against the
MPL without having the data ‘overhead’ of an equipment like
 time segments
 accounting and location data
This requirement often came up when you’ve
 non serialized parts to be

o installed and dismantled into/from a technical object
o respected by Configuration Control functionality.
 masses of identical parts inside a technical object to be validated
 not the need to track the installation history of a part
To satisfy this requirement SAP introduced with EhP2 the usage of a specific kind of equipment BOM.
This Configuration Control related equipment BOM is will be called cBOM inside this document.
This specific kind of BOM mustn’t be mixed up with the classic BOMs of materials, equipment and
functional location. It can’t be used inside the Material Resource Planning or as template list for the
components inside a maintenance order.
Within this cBOM you enter a list of parts with
 their material number and

 their quantity
item by item.
Multiple levels are not supported within a cBOM.
Only one single cBOM is allowed per equipment. A differentiation via the plant is not allowed.
Within the transaction IE4N you are able to ‘dismantle’ and ‘install’ parts from/into the cBOM of an
equipment and put/take them into/from stock. The structure gaps are maintained accordingly.
For transaction IE4N there are existing the following restrictions:
 No support of forced install/removal on BOM items, because there is no way to document it.
 Swap does not support non serialized parts
 Installation/Removal without MM posting does not support Installation/Removal of non-
serialized equipment
 Non stock materials will not be supported as equipment BOM items for Configuration
Control purposes (Only stock items are supported).
Page 67 of 177
9.2 Customizing relevant for cBOM usage

To make use of the cBOM functionality, you’ve to perform some customizing settings.
Frist of all you’ve to define a new BOM usage ‘C’. Use the customizing path
Production-> Basic Data->Bill of Material-> General Data-> BOM Usage-> Define BOM Usages
In Figure 59 you find the settings for this new BOM usage.
Figure 59 Define new BOM usage
After this you’ve to make settings for the order of priority of BOM usage via the customizing path
Production-> Basic Data->Bill of Material-> Alternative Determination -> Define Order of

Priority for BOM Usages
In Figure 60 you find the settings you’ve to make. Use the selection ID ‘CC’.
After this you’ve to define the relevant application via the customizing path
Production-> Basic Data->Bill of Material-> Alternative Determination -> Define Applications
In Figure 61you find the settings you’ve to make. Use the application ‘CC01’.
Page 68 of 177
Figure 60 Define order of priority of BOM usage
Figure 61 Define the application
Finally you’ve to activate the usage of the cBOM via the customizing path
Plant Maintenance and Customer Service-> Maintenance and Service Processing->

Configuration Control-> Make Settings for Equipment BOM in Configuration Control
You must make the following settings if you want to use the equipment BOM functions in the
configuration control workbench (see Figure 62):
 Activate the indicator ‘BOM Mode Allowed’
 Usage: C
Page 69 of 177
 Application: CC01
 Define Item Category. L
Figure 62 Activate cBOM usage for Configuration Control
9.3 Technical preconditions

You can make use of the cBOM under the following preconditions:
Enhancement package:
SAP ECC 6.0, Enterprise Extension PLM, Enhancement Package 2 (EA-PLM 602)
Business function to activate:
To use this function, you must activate the business function Enterprise Asset Mgmt Part 2
(LOG_EAM_SIMP) or A&D Maint., Repair & Overhaul (AD_MRO_CI_1).
BAdIs to implement:
To activate the cBOM-usage inside transaction IE4N you’ve to implement the BAdIs
 BADI_CCM_IE4N_MODE - BAdI: IE4N Mode Activation

 BADI_CCM_IE4N_AUTHORITY - BAdI: Authorization Check
9.4 cBOM and the MPL

Within the definition and modeling of the MPL, there are no additional rules concerning the usage of
cBOMs.
9.5 Usage of the cBOM in actual structure

9.5.1 How to create a cBOM?
Using the transaction IB01 you can initially create a cBOM.
On the initial screen of IB01 enter:
 the number of the equipment you want to pride a cBOM with

 leave the entry for the plant empty (group BOM)
 ‘C for Configuration Control for BOM usage
Page 70 of 177
On the detail screen add the parts item by item. Within one item you’ve to enter:
 L (stock item) in the column ‘Item Category’

 The corresponding material number for the part in the column ‘Component’
 The corresponding FID in the column ‘Function ID’
 The corresponding quantity in the column ‘quantity’
In our example we replace the equipment ESEAT01, …, ESEAT08 by corresponding cBOM items for
the equipment ETR01 and ETR02.
In Figure 63 you can see the creation of the cBOM for equipment ETR01
Figure 63 Creation of cBOM for equipment ETR01
In Figure 64 you can see the actual structure of aircraft below functional location FLAC01.
In Figure 65 you can find the result of the check of Configuration Control for the aircraft FLAC01.
Page 71 of 177
Figure 64 Actual structure with cBOM
Figure 65 Result of transaction CCM2 for the aircraft under functional location FLAC01
9.5.2 How to maintain a cBOM?

If a cBOM was initially created you have to maintain the content of this cBOM via transaction IE4N
using the two additional IE4N modes for
 Installation of non-serialized materials (equipment BOM item) with material movement (goods
issue)
 Dismantling of non-serialized materials (equipment BOM item) with material movement (goods
receipt)
If the equipment, where the cBOM is assigned to, has got the system status
Page 72 of 177
 On Stock
 Installed (in functional location or equipment)
it is not possible to maintain the cBOM via transaction IB02 ‘Change equipment BOM’. If you ignore
this you get the message
Only equipment BOM with status AVLB can be changed (Message no. CCMM506)
This is to avoid stock inconsistencies.
Only in very exceptional cases you should maintain the content of a cBOM via transaction IB02 when
the status of the equipment is ‘Available’. If you try to change a cBOM of an equipment with the
status ‘Available’ the message
Changes to equipment BOM will not be considered in warehouse stock (Message no.
CCMM505)
indicates possible side effects.
Figure 66 is showing the effect on
 Item quantity of cBOM

 Stock
 Structure gap
due to different actions on the cBOM of equipment ETR01 with transaction IE4N
Page 73 of 177
Figure 66 IE4N actions on cBOM
9.5.3 How to display a cBOM

Please use transaction IB03 ‘Display equipment BOM’ for this purpose.
10 Object Dependency
10.1 Motivation
Imagine the following situation. An aircraft manufacturer is proving his customers with one aircraft
model, lets’ call this model AC, separated in different types:
 Model AC for short range (Type S)

 Model AC for long range (Type L)
Your airline is operating several aircrafts of the model AC of the short and long range type. You want
to use Configuration Control to validate the consistency of your aircrafts.
The two types of the model are pretty similar!
Several approaches for the MPL model are possible:
Page 74 of 177
1. Create a MPL for each aircraft

 Advantage: Easy to model
 Disadvantage: Because of the masses of MPLs very cumbersome to maintain as you’ve
one MPL per aircraft.
2. Create a MPL for each model of the type
 Easy to model.
 Again you’ve two MPLs to maintain, which are pretty similar.
3. Create a MPL for the model and use specific conditions to separate the different types within
the MPL.
 More complex modeling of the MPL because the different models should be handled
within one MPL.
 The efforts to maintain this MPL are pretty less.
Within this chapter we concentrate on the approach 3. The conditions are defined via the so called
Object Dependency approach of the iPPE-functionality.
For explanation we use again our known aircraft example from Figure 64 and Figure 65. From chapter
5.3 we know the following parts, the aircraft must contain:
 2 fuel tanks with the material number FT01 (FUEL TANK 01, 5000L)
Now we expand this list of parts for the short and long range aircraft type of the aircraft model AC:
 2 fuel tanks with the material number:

o FT01 short range type S (FUEL TANK 01, 5000L)
o FT02 long range type L (FUEL TANK 02, 8000L)
10.2 Introduction
From the chapter 5.4 and 5.5 you know that all structure nodes inside an MPL has got the same
product class. In our example we use the product class AC for the aircraft. This product class contains
characteristic which we make use of now. We use the characteristic AC_TYPE to define the condition
when structure node variants are valid. To do this we use the so called Object Dependency of the
iPPE.
On the other hand side we have the actual structure to be checked with the MPL. This actual
structure must provide the set of rule - the MPL – with an explicit filter criteria to explode the MPL.
Transferred to our aircraft example, we have to tell the MPL, which type of aircraft of model AC has
to be checked; short or long range. The top equipment – the equipment with the link to the access
node – is used for this purpose. This equipment is using inside its’ configuration data the same
configurable material as the access node variant in the access node does. By configuration of the
equipment we set the filter criteria to explode the MPL. In our aircraft example we use the
configurable material AC_CB. Via configuration we choose the corresponding aircraft type; short or
Page 75 of 177
long range. Remark: Within the configuration profile of the configurable material AC_CB the product
class AC used for iPPE is assigned.
Figure 67 is showing the concept of object dependency.
Figure 67 Concept of object dependency
10.3 Modeling the MPL

To maintain the condition when a structure variant is valid, we use the object dependency. Within
this functionality complex validity rules based on the characteristics of the product class of the
structure node can be maintained. For this modeling approach it is pretty important that all structure
nodes of the MPL have the same product class ass the access node! In general structure nodes
without product class are not allowed within the MPL!
Concerning the quantity of structure node variants of one structure node, the following rules are
important in context with object dependency:
 Structure node variants which have the same condition inside the object dependency must
have the same quantity.
 If there does exist a structure node variant without any condition, it is valid every time! Every
other structure node variant with condition must have the quantity of the structure node
variant without condition!
Page 76 of 177
 If there exist structure node variants with different conditions, different quantities for every
condition. But then a structure node without condition is not allowed anymore.
Within our aircraft example we use only the characteristic of the aircraft type AC_TYPE.
Figure 68 till Figure 72 are showing the necessary changes for the structure node representing the
fuel tank for our aircraft example. The structure node SN_FT should be able to represent the valid
materials for the short and long range aircraft.
Figure 68 Additional variants for the structure node SN_FT, switch on object dependency to maintain validity, step 1 and
2
Figure 69 Popup: Dependencies Change: Step 3
Page 77 of 177
Figure 70 Popup: Dependencies Change: Step 4 and 5
Figure 71 Popup: Dependencies Change: Step 6
Page 78 of 177
Figure 72 Structure node SN_FT: Result with maintained object dependency
10.4 Actual structure

Within the actual structure we have to maintain the configuration of the top equipment which
represents the link to the access note of the MPL. With this we define filter criteria for the MPL. With
this filter the MPLs gets knowledge which structure node variants are relevant for the check.
Within our aircraft example we use an individual configuration. But you can also use a reference to a
material variant of the configurable material. In this case this configured material has to contain the
corresponding configuration.
Are showing the changes on the Configuration Data tab strip of the top equipment EAC01-01 for a
short range aircraft.
Figure 73 Configure top equipment, Configuration Data tab strip: Step 1
Page 79 of 177
Figure 74 Configure top equipment, Characteristic value assignment: Step 2
Figure 75 Configure top equipment: Result of individual configuration
Page 80 of 177
Figure 76 Result of the check with Configuration Control
Figure 76 is showing the result of the check of Configuration Control for the actual structure below
the functional location FLAC01. Within the top equipment EAC01-01 we configured a short range
aircraft.
Within the next step we dismantle the equipment EFT01 representing the 5000l fuel tank on the left
wing. Afterwards we install a 8000l fuel tank - equipment EFT01LONG with material number FT02 -
into the left wing and perform the check of Configuration Control again.
Figure 77 Result of the check with Configuration Control with the wrong part
Page 81 of 177
Figure 77 is showing the result of the check. Configuration Control found a wrong part be installed as
fuel tank in the left wing as for the short range aircraft only a part with the material number FT01
(fuel tank with 5000l) is valid.
You might ask: You can also fly short range with a 8000 l tank, can’t you? Yes, you can. But this
example should only show the possibilities of object dependency.
10.5 Usage of the configuration of the top equipment in logistic processes

together with Configuration Control
We have to differentiate two requirements:
 Top equipment is not part of a logistic process like a goods movement:

 Top equipment is part of a logistic process like a goods movement
The following two chapter should give some ideas how to handle those two requirements. Please
also see note SAP note 538751 [SAP N538751].
10.5.1 Top equipment is not part of a logistic process like a goods movement
Please follow the steps you know from chapter 5.4, 5.6.2, 10.3 and 10.4. Here we just use the
configurable material for the individual configuration of the top equipment.
10.5.2 Top equipment is part of a logistic process like a goods movement
10.5.2.1 Logistic process and Configuration Control needs configuration information of

the serialized equipment
Within this requirement you include the top equipment as serialized part with material and serial
number into a logistic process. The configuration of the top equipment is used for the logistic process
(e.g. goods movement) on the one hand and for Configuration Control purpose on the other hand
side. If the (individual) configuration of the equipment differs from the configuration given by the
logistic process of the goods movement an error will occur. Due to this it is pretty important to
synchronize the configuration of the movement process with the configuration of the top
equipment! The recommended way to reach this requirement is the usage a configured material
which has to be the same inside the top equipment and in the logistic process, e.g. the movement.
Table 7 in you can find the relevant steps for Configuration Control. They look pretty similar than the
steps in Table 1 and Table 3, but there are minor but essential differences.
Step Action Comment

1 Create characteristics using the The characteristics might be used later on for the purpose of object
classification functionality dependency. In our example you might use them to characterize the
 Transaction CT04 aircraft type, e.g. long range, short range or freight version of the aircraft.
With this characteristic it is possible to judge inside one set of rules
between different aircraft types.
If you do not have the need to distinguish between different types, you do
not need to create characteristics.
2 Create a class with the class This class have to be used later on
type 300 (Variants) and assign  In the assignment of the configuration profile of the
the characteristics of step 1 configurable material (Step 3)
(when available) .  As product class inside the access node definition (Step 4)
 Transaction CL01
3 Create a configurable material This configurable material is used later on
Page 82 of 177
 Transaction MM01  as formal access variant inside the access node

 as carrier inside an equipment
o to link an actual technical object structure to a MPL
o to provide the MPL explosion with information about
the current shape (e.g. about the current aircraft type)
via variant configuration

4 Add configuration profile for Assign the variant class created with step 2 to the material created with
the material just created step 3.
 Transaction CU41
5 Create configured material Configure the material concerning the needs of the filter criteria needed
based on the configurable for the MPL explosion.
material
 Transaction MM01 This configured material must be used in the complete logistic process
later on, e.g. as material which should be used inside a goods movement.
This configured material has to be used as material number for the serial
number of the top equipment which is the serialized part to be moved
inside the logistic process.

6 Create the access node Within this step you have to provide the access node with
 Transaction PPE  a valid access node name. The node name has to be unique
(usage of A&D within the same client and used product class!
industry solution) or  the product class from step 2
 PDN (usage of  the access node variant using the configured material created
enterprise extension) with step 5:
o Keep in mind that the used product class of the access
node and the variant class assigned to the
configurable material created with step 3 must be the
same!
o The configured material can only be used one time for
one access node to define an access!
 an access definition. Use the ‘Copy Entry’-functionality to create
an access to the existing access variant. The usage of the access
must be ‘Engineering/design’ (ENG).
With this you allow the access from ‘outside’ to the included
MPL.
One MPL must contain exactly one access node at the top of the MPL!
When you create the access node

 choose ‘Access Node’ (S_HD) as node type

should be the link to the transactions are visible:
corresponding MPL.  Configuration Data
 Transaction IE01  Configuration Control
create the equipment  SerData (for material and serial number)
 Transaction IE02 to
change the Within the tab strip
equipment  ‘Configuration Data’
o Enter the number of the configurable material. Use
the material you’ve created within step 3. This
material contains within its configuration profile the
same class as the MPL you’ve created within step 6.
o Now create a reference to the configured material
created with step 5 using the button 'Assign ref.' Enter
Page 83 of 177
the number of the configured material in the popup.

o Never copy the reference by pressing the button 'Copy
ref.' as this would make the configuration individual
and independent from the configuration of the logistic
process!
o This formal step is absolutely essential to link the
actual structure to the MPL!
 ‘Configuration Control’, you perform the real linkage to the MPL.
Using the configured material and the (product) class of the
configurable material entered before on the tab strip
‘Configuration Data’ the iPPE nodes are scanned to find access
nodes with the same configured material-product class-
combination inside the access information. If found, a list is
shown, where you can choose the access node you want to link
the current equipment with. This link – the internal node
number of the access node - is stored inside the equipment
data. Therefore this link is called hard link.
On the ‘Configuration Control’ tab strip press in the screen area
‘iPPE Access Information’ the button to perform the iPPE access
and choose the corresponding entry in the popup.
 ‘SerData’ enter the material number of the configured material
created with step 5 and a proper serial number for the logistic
processes.
Material-to-material movements with a serialized part which
represents also a top equipment are pretty critical as they might
change the content of the configuration.

Table 7 How to create an access node with a configured material
10.5.2.2 Only Configuration Control needs configuration Information of the serialized

equipment
Within this requirement you include the top equipment as serialized part with material and serial
number into a logistic process. The configuration of the top equipment is not used for the logistic
process (e.g. goods movement). The configuration of the top equipment is only used for
Configuration Control.
For this use case it is very important that the material mentioned inside the ‘SerData’ tab strip for the
serial number data of the top equipment does not contain a material with any configuration!
The configuration on the ‘Configuration Data’ tab strip is only relevant for Configuration Control. It
can be individual or refer to a configured material.
Keep in mind that material-to-material movements of this serialized equipment might be critical.
10.6 FID-Grouping and configuration of top equipment

The configuration of the top equipment is a relevant part of the FID grouping of the actual structure.
That means that FID groups for the actual structure are also grouped concerning the configuration
settings of the top equipment.
As we only have one single MPL in use this is not relevant at the moment but this fact is very
essential for coupled MPLs as we see later on.
Page 84 of 177
11 Parameter Effectivity of Engineering Change Management (ECM)
11.1 Motivation
With Object Dependency we are able to make major differences within one MPL between several
types of one model of the aircraft. But what about the ‘small’ differences between the individual
aircrafts of one type of a model within the fleet of the customer?
Let’s explain this at an example:
Again an aircraft manufacturer is proving his customers with one aircraft model, lets’ call this model
AC, separated in different types:
 Model AC for short range (Type S)

 Model AC for long range (Type L)
The customer is using both types and is creating one single MPL for the model AC. Within the fleet of
the short range type there is existing an aircraft with the individual tail number ACSR06 that has got
three tiers installed instead of two. The other five short range aircrafts has got two tiers (ACSR01 –
ACSR05). The four long range aircrafts have two tiers in general (ACLR01-ACLR04).
To model this, we can use the approach of the Parameter Effectivity of Engineering Change
Management (ECM). The tail number of the aircraft should be used in our example and for further
explanations as individual criteria for the MPL explosion. Within this approach the tail number is used
as ECM related serial number. Please don't mix up this specific serial number with the serial number
used in the equipment master data (Field EQUI-SERNR). This specific serial number has to be
maintained additionally.
Actually you define a structure node inside the MPL. This structure node contains a variant with a
valid material number. The variant must contain an Engineering Change Number (ECN). This ECN
describes the preconditions when this variant is valid; e.g. a range of specific serial numbers – in our
case the tail number of the aircraft.
The highest ECN per structure node variant should be taken into account when MPL is resolved for
Configuration Control. This should enable you to model progressing changes/modification processes
of a technical object during its life cycle.
The explicit Parameter Effectivity value – the explosion criteria for the MPL - of the specific serial
number is gained by the proper top equipment linked to the access node of the MPL.
Generally the ECM is used to build up progressing changes of technical objects during their life cycle
in the Configuration Control and MPL context. On the contrary the object dependency which is used
to distinguish between different types of one model. Using ECM for MPL purpose means an
additional condition for resolving an MPL-structure.
Page 85 of 177
11.2 Customizing settings for ECM

To use the ECM approach for Configuration Control we have to make some settings inside the
customizing.
11.2.1 Parameter effectivity must be activated

Customizing path:
Cross-Application Components→Engineering Change Management→Set Up Control Data
Action:
Activate 'Parameter Effectivity' in the screen area 'Validity'.
11.2.2 Maintain the proper effectivity parameter and the effectivity type
Customizing path:
Cross-Application Components→Engineering Change Management→Parameter

Effectivity→Define Parameters
Action:
You may check whether the special effectivity parameter SERNR which we want to use for our
example for the tail number of the aircraft might exists (see Figure 78). Use ‘O’(Open interval)
for type.
Figure 78 SERNR as Effectivity Parameter to be used as tail number
Page 86 of 177
11.2.3 Maintain the effectivity type

Customizing path:
Cross-Application Components→Engineering Change Management→Parameter

Effectivity→Define Effectivity Types
Action:
Create for our example a new type e.g. with name ZTAILNR. Maintain all mandatory data and
mark the line with the effectivity parameter SERNR (see Figure 79). As we want to use the
same change numbers with the same effectivity type, the priority does not have an effect.
Figure 79 Define effectivity type for tail number
11.3 General customizing setting for iPPE

Customizing path:
Production→General Settings→Define General iPPE Customizing (Transaction OPPE01)
Action:
Enter 'History by Sequence' in the field 'Explosion Type for Component Variants' in the screen
area 'Define PVS Parameters'.
In addition see note 815818 [SAP N815818].
Anyhow, please make sure that the settings in the customizing are contradictory to other business
requirements!
11.4 Create change numbers (ECN) using transaction CC01

The following steps needs to be performed (see Figure 80 to Figure 83):
 On the entry screen enter a change number and a proper effectivity type from above in the
screen area 'Control'.
Page 87 of 177
 On the detail screen for the header:
Maintain the status of the change number which should be active
 Maintain the valid object types by pressing the button 'Object Types' or use the menu path
<Goto><Object Types> or press F6:
For object type 'PVS Variant' activate the indicators for
o Object type active for change number (Actv.)

o A management record is required for each object (Object)
o Object management record generated (MgtRec)
 Maintain the validity of the change number via the button ‘Detail view’ or use the menu path
<Goto><Validity> or press SHIFT-F9.
For the structure node variants the following two ECNs are created for our example:
 ECNSR01: validity of serial number = ACSR01, ACSR02, ACSR03, ACSR04 and ACSR05
 ECNSR02: validity of serial number = ACSR06
 ECNLR01: validity of serial number = ACLR01, ACLR02, ACLR03 and ACLR04
Figure 80 Define a change number, part 1
Page 88 of 177
Page 89 of 177
11.5 Modeling the MPL

Figure 84 is showing the assignment of the change number created before.
Figure 84 Assignment of the change number
Figure 85 is showing the two variants of structure node SN_TR divided by the change number.
Page 90 of 177
Figure 85 Structure node SN_TR with two variants divided by change number.
Concerning the quantity of structure node variants of one structure node, the following rules are
important in context with an ECN:
 Structure node variants which have the same condition inside the object dependency must
have the same quantity.
 If there does exist a structure node variant without any condition, it is valid every time! Every
other structure node variant with condition must have the quantity of the structure node
variant without condition!
 If there exist structure node variants with different conditions, different quantities for every
condition. But then a structure node without condition is not allowed anymore.
If you do not respect these modeling rules, the checks of Configuration Control will raise fuzzy
results. The same is valid for object dependency.
In our example we use different quantities. But you can also use different material numbers or a
mixture of both.
11.6 Actual structure, top equipment and its’ configurable material

The top equipment linked to the access node must provide on the one hand the data for object
dependency (see chapter 10)on the other hand it has to provide the filter criteria for the parameter
effectivity.
But first of all we have to adjust the data of the configurable material we used in the top equipment.
To link a top equipment with the corresponding access node inside the MPL configurable material
has to be used (see Figure 18 and Table 3). Inside the master data of this configurable material the
indicator 'Assign effect. vals' in the 'general data' screen area of the material tabstrip 'basic data 1'
has to be activated to make the material ready to use parameter effectivity (see Figure 86). When a
material variant of the configurable material is used on the 'serial number'-tab strip of the top
equipment, the indicator 'Assign effect. vals' has to be active for this material, too.
Page 91 of 177
Figure 86 Activate usage for parameter effectivity in material master
In the next steps we have to adjust the top equipment accordingly:
 The configurable material has to be entered for the material number on the 'serial number'-
tabstrip (SerData) of the top equipment which is linked to the access node. This is an
essential step otherwise it wouldn’t be possible to assign the current parameter effectivity
value for this equipment (see Figure 87).
Figure 87 Configurable material at the serial number tab strip of the equipment
Page 92 of 177
 Now we have to provide the filter criteria - the tail number ACSR06 – to the top equipment
of our technical structure. With this criterion the check of Configuration Control knows,
which variant is valid, when the variant has a corresponding change number. This has to be
done on the 'Configuration control'-tab strip (see Figure 88).
If you want to change the existing parameter effectivity value for this equipment you have to
delete it first with the functionality on the 'Configuration control'-tab strip of the equipment.
Figure 88 Enter the tail number
11.7 Results of check

After the data adjustment for ECM the check for Configuration Control is performed. In Figure 89 you
see the result of the check. The error message indicates missing quantity. As you might remember
we check the aircraft with the short range aircraft with the tail number ACSR06 which need to have
three tiers. But currently there only are existing two tiers. After we add a third tier
 Functional location FLAC01 -CABIN -TR03

 Equipment ETR03
 cBOM with 4 seats for equipment ETR03
into the actual structure Configuration Control is accepting it (see Figure 90).
Page 93 of 177
Figure 89 Result of check of Configuration Control
Figure 90 Result of check of Configuration Control after the correction of the actual structure
Page 94 of 177
11.8 FID-Grouping and value for parameter effectivity of top equipment

The value(s) for the parameter effectivity of the top equipment is a relevant part of the FID grouping
of the actual structure. That means that FID groups for the actual structure are also grouped
concerning the value(s) for the parameter effectivity of the top equipment.
As we only have one single MPL in use this is not relevant at the moment but this fact is very
essential for coupled MPLs as we see later on.
Page 95 of 177
12 Usage of coupled MPLs
12.1 Motivation
Often big technical structures can split into subassemblies which can be checked on their own. The
split might be performed respecting
 operational,
 maintenance or
 organizational
aspects. Thinking at an aircraft the split might refer to the landing gears, engines, flight electronic
and so one. The business background of this split is the expectation that departments responsible for
the maintenance of the aircraft engine might not be experienced in landing gears. Doing this the
check load can be split and the runtime can be reduced as only dedicated assemblies of a complex
and big structure needs to be checked.
Figure 91 is showing the usage of coupled MPLs for an aircraft with two engines and landing gears:
 The department responsible for the engines is checking the two engines by using a complete
check for each of the engines (point ❷ in Figure 91)
 The department responsible for the landing gears is checking the landing gears by using a
complete check for each of the landing gears (point ❸ in Figure 91)
 The department responsible for the complete aircraft can perform
o a partial check of the aircraft up to the structure nodes of the engine and the landing
gear inside the aircraft MPL (point ❶ in Figure 91). This is more or less a global
check for the engines and the landing gears to answer the question: Are all engines
and landing gears installed and does the top equipment of these installed objects
contain the right material number
o a complete check of the whole aircraft with all parts of the engines and landing gears
which is very time consuming (point ❹ in the Figure 91).
Page 96 of 177
Figure 91 Overview: Usage of coupled MPLs
For our example, we concentrate now on the engines, which still are missing. The landing gears will
work the same way. Please keep in mind, that our example should serve to explain the basics of
coupled MPLs!
Page 97 of 177
12.2 Sum up the current structures of the aircraft

Within this chapter we shortly should memorize, what we’ve done so far for the aircrafts.
Figure 95 is showing the MPL to check our aircrafts
Figure 92 MPL of the aircraft
Figure 93 is showing the actual structure of the short range aircraft with the tail number ACSR06
Page 98 of 177
Figure 93 Actual structure of the short range aircraft with the tail number ACSR06t
12.3 Set up of coupled MPLs by using an example

12.3.1 Definition of the subordinate MPL
Our aircraft should have two engines installed. One engine at the left wing and one engine at the
right wing. The only difference between the engines should be the bold to install them at the wing.
The engine should consist of the following parts:
 Turbine with the material number TURBINE01

 Fuel pump with the material number PUMP01
 Bolt to fix engine at the wing
o With the material number BOLT01 for the left wing
o With the material number BOLT02 for the right wing
The setup of the MPL works as described in chapter 5.4 and 5.5.
Essential rules and recommendations:
 It is highly recommended to that the product class of every subordinate MPL differs! We
make use of this later on in the implementation of BAdI BADI_CCM_EXPL_ALWD. The
implementation of this BAdI is essential to make partial check running.
Page 99 of 177
 At this point of time it is important to spend some thoughts on a unique criterion to

differentiate between the equipments of different assemblies to filter them in partial check.
In our aircraft example we divide the assemblies for
o the general aircraft,
o the engines and
o landing gears.
For our example we will make use of the structure nodes inside our MPLs. We need this
structure node name as FIDs inside the equipment. This FIDs we will make use in the
implementation of BAdI BADI_CCM_EXPLOSION. The implementation of this BAdI is
essential to make partial check running (see 12.5).
Figure 94 is showing the structure node naming convention for our example.
Figure 94 Naming convention for the prefix of structure nodes
For the subordinate MPL for the engine we
 create the characteristic EN_POSITION (position at the wing at the aircraft) with the possible
values
o L Left wing
o R Right wing
 create the product class EN for the engine with the class type 300 (variant) and assign the
characteristic EN_POSITION
 create the configurable material EN_CB and assign within the configuration profile the
product class EN.
Finally we create the MPL for the engine (see Figure 95).
Page 100 of 177
Figure 95 MPL of the engine
In the next step we link the engine MPL to the aircraft MPL.
We need a material variant of the configurable material EN_CB. Therefore we create the material
EN01:
 Material EN01 itself:

o Inside the material data of EN01 we have to enter the configurable material EN_CB
for the Cross-Plant Configurable Material and press the button to configure the
variant. For our example we save an empty configuration (see Figure 96).
o Furthermore this material is used to be entered inside the serial number tab strip for
the equipment that represents an engine itself. This equipment is used for
installation, dismantling and goods movement processes. Therefore material data
like general and plant data for sales, general data for plant and storage location and
accounting data might to be maintained as well.
 Inside the engine MPL (subordinate):
o This material variant is used to link the engine MPL with the aircraft MPL.
o Inside the engine MPL this material variant EN01 has to be used as additional access
variant (see Figure 97).
o After including this material variant EN01 as access variant an additional access via
this access variant has to be defined (see Chapter 5.4 and Figure 14).
o Using object dependency (see Chapter) for the structure node EN_BOLT we make
sure that the material BOLT01 is used for the left engine and the material BOLT02 is
used for the right engine.
 Inside the aircraft MPL (superior):
o We have to define a structure node that stands for the aircraft engines in general
and which is therefore part of the check. As it is an aircraft related node we have to
use the prefix SN_. The node name is SN_ENGINE.
o The note must contain at last one structure node variant with a valid material
number (no configurable material). We use the material EN01 for this purpose. As
the aircraft has two engines the quantity inside the structure node is two.
Page 101 of 177

o As the material EN01 is also mentioned inside an access variant and is defined as
access in the access node AN_EN01 the linkage between the two MPLs was
performed. You can see the success of our action by exploding the structure node
SN_ENGINE. You will find the structure nodes EN_TURBINE, EN_PUMP and EN_BOLT
assigned (see Figure 98 and Figure 99)
o In our example we locate the structure node for the engine below the view node
VN_WING.
Figure 96 Create material variant EN01
Page 102 of 177

Figure 97 Additional access variant in the MPL of the engine
Figure 98 Coupling via new structure node SN_ENGINE
Page 103 of 177

Figure 99 Overview of coupled MPLs
12.4 Enhancement of the actual structure

Within this chapter we add equipment structures containing the parts of the two engines into our
technical structure of the aircraft.
Page 104 of 177

Usually subassemblies as the engine are a matter of installation and dismantling. Due to this it does
not make sense to model subassemblies with functional locations. This also means that view nodes
on the MLP side does not make senses for subordinate the MPL as well.
12.4.2 The top equipment of the structure

The top equipment of the engine structure must fulfill the following requirements:
1. Perform a hard link to the MPL of the engine to be able to check the engine on its own.
Please refer to Table 3 and step 7 of Table 7 for the creation of a top equipment..
In our example we have got two top
 equipment ELENGINE for the left engine and

 equipment ERENGINE for the right engine.
We provide this equipment on the Tab strip ‘Configuration Data’ with the number of the
configurable material EN_CB and perform a link to the corresponding access node of the MPL
(AN_EN01) on the tab strip ‘Configuration Control’.
2. Be check relevant part of the superior assembly to be able to check the whole technical
object with all its parts
Provide the FID on the tab strip ‘Configuration Control’ with the node name of structure node
of the superior MPL.
In our example we use the node SN_ENGINE as this node is part of the superior aircraft MPL.
3. Be able to provide filter data for object dependency and ECM.
As we want to differ between the engine on the left wing and the engine on the right wing –
the bolt to fix the engine at the wing is different for the left and right engine – we have to
configure the top equipment of the equipment structure for the engine. For our example we
use an individual configuration for these equipment. It is also possible to refer to a material
variant for this purpose, but we want to use an individual configuration now. We use ‘L’ =
Left wing for the left engine and R = Right wing for the right engine to get the correct set of
rule for the configuration check.
Finally the two new top equipment have to be installed into the actual structure of the aircraft. In or
example we use the functional locations
 FLAC01 -LWING for the left engine (equipment ELENGINE)

 FLAC01 -RWING for the right engine (equipment ERENGINE)
To sum it up, and this is very important to understand, the top equipment of subassemblies contains
both
 Access data to the corresponding MPL. This information is relevant for the complete check of
the aircraft and the complete check of the engine.
 Data relevant to be checked by Configuration Control when the superior assembly (the
aircraft) is checked by a complete check.
Page 105 of 177
12.4.3 Subordinate equipment

Please refer to chapter 5.6.3.
12.4.4 Final actual structure

Figure 100 is showing the actual structure for the engines. Figure 101 is showing the complete actual
structure.
Figure 100 Actual structure of the engines
Page 106 of 177

Figure 101 Complete actual structure of the aircraft
Page 107 of 177

12.5 Implement the partial check

With the current data we modeled, we can perform the following checks of Figure 91:
 A complete check for each of the engines (point ❷ in Figure 91)

 A complete check of the whole aircraft with all parts of the engines and landing gears which
is very time consuming (point ❹ in the Figure 91).
The partial check of the aircraft up to the structure nodes of the engine and the landing gear inside
the aircraft MPL (point ❶ in Figure 91) is still not possible.
To activate the partial check the two BAdIs
 BADI_CCM_EXPLOSION and
 BADI_CCM_EXPL_ALWD
have to be implemented according the needs of our/your data model.
Actual structure:
The BAdI BADI_CCM_EXPLOSION is able to influence the explosion of the actual structure and
offers an additional ‘Load’-button in the Configuration Control Workbench (transaction CCM2)
for the partial load of the actual structure.
To filter the data of the allowed structure for the partial check, we make use of the FID of the
equipment relevant for check (see Figure 94).The complete check is working without filtering via
the implementations of the BAdI BADI_CCM_EXPLOSION!
For our example we define the following criteria for partial check:
 If we perform a partial check on the aircraft only the equipment with the FID-prefix SN_
are relevant
 If we perform a partial check on an engine only the equipment with the FID-prefix EN_
are relevant
 If we perform a partial check on a landing gear only the equipment with the FID-prefix
LG_ are relevant. The data for the landing gears are not maintained. But they work the
same way than the engines.
MPL:
The BAdI BADI_CCM_EXPL_ALWD is able to influence the explosion of theMPL and offers an
additional ‘Check’-button in Configuration Control Workbench (transaction CCM2) for the partial
load of the MPL and the partial check. The complete check is working without filtering via the
implementations of the BAdI BADI_CCM_EXPL_ALWD!
As indicator to stop the explosion on MPL side we use the product class of the MPL:
 If we perform a partial check on the aircraft only the structure nodes with the product
class AC are relevant
Page 108 of 177

 If we perform a partial check on an engine only the structure nodes with product class
EN are relevant.
 If we perform a partial check on a landing gear only the structure nodes with product
class LG are relevant. The data for the landing gears are not maintained. But they work
the same way than the engines.
The implementations below are made to serve the requirements of the example from above. If you
want to implement the partial check for your company and your business, your implementations will
look quite different and much more complex. Please don’t take over the implementations below
without analyzing your special business case, as they might not fit for it!
12.5.2 BAdI BADI_CCM_EXPLOSION

For our example the implementation of BAdI BADI_CCM_EXPLOSION take place in class
ZCL_IM_IMP_CCM_EXPLOSION
12.5.2.1 Additional attributes
12.5.2.2 Additional method CHECK_FUNCID

Definition of the method:
Parameter of method CHECK_FUNCID:
Page 109 of 177

Coding of method CHECK_FUNCID:
METHOD check_funcid.
***********************************************************************
* Remark:
* o Every new load of an actual structure create a new instance
* of the implementation class ZCL_IM_IMP_CCM_EXPLOSION!
* o This coding relies on the correct modelling of the
* actual structure!
***********************************************************************
* Local data definition:
DATA :
lv_funcid_pre TYPE ccc_funcid.
*----------------------------------------------------------------------
* Set:
ev_pre_funcid_identical = c_no. "Assume the negative case first
*----------------------------------------------------------------------
IF me->nv_funcid_pre IS INITIAL.
* Instance memory for prefix of FID is empty, set the instance memory.
* Remark:
* o Only an equipment without link to an access node
* is able to set the current prefix for the FID
* o Structure gaps and cBOM-items are not allowed to set
* prefix for the FID, they can only consume it.
IF iv_objtype = c_objtype_equi "Equipment
AND iv_ppeguid IS INITIAL "No equipment with link to acces node
AND NOT iv_funcid IS INITIAL. "FID available
* Set prefix for FID
* Remark:
* Separator of the prefix is the first '_'-sign.
me-nv_funcid_pre =
substring_before( val = iv_funcid sub = c_pre_separator ).
ev_pre_funcid_identical = c_yes.
ELSEIF iv_objtype = c_objtype_equi "Equipment

AND NOT iv_ppeguid IS INITIAL. "Equipment with link to acces node
* Just accept equipment.
ELSE.
* Reject any other case because of modeling issue.
ev_pre_funcid_identical = c_no.
ENDIF. "IF iv_objtype = c_objtype_equi ...
ELSE.
* Check instance memory for prefix of FID.
* Remark:
* If nv_funcid_pre is set in the if-part before,
* there is no need for a check as the object in
* question set the prefix of the FID.
IF ( iv_objtype = c_objtype_equi "Equipment
Page 110 of 177

OR iv_objtype = c_objtype_cbomitem "cBOM-item

OR iv_objtype = c_objtype_gap "Structure gap
)
AND NOT iv_funcid IS INITIAL. "FID available
* Get prefix of current FID
lv_funcid_pre = substring_before( val = iv_funcid sub = c_pre_separator ).
* Compare:
IF lv_funcid_pre <> me->nv_funcid_pre.
* Prefix of current FID and instance memory differs
ELSE.
* Prefix of current FID and instance memory identical
ENDIF. "IF lv_funcid_pre <> nv_funcid_pre.
ELSE.
* Reject any other case because of modeling issue.
ENDIF. "IF ( iv_objtype = c_objtype_equi ...
ENDIF. "IF me->nv_funcid_pre IS INITIAL.
ENDMETHOD.
12.5.2.3 Interface methods
Coding of interface method IF_EX_BADI_CCM_EXPLOSION~EQUI_CHECK
METHOD if_ex_badi_ccm_explosion~equi_check.
DATA:
lv_pre_funcid_identical(1) TYPE c.
CALL METHOD me->check_funcid

EXPORTING
iv_funcid = iv_itob-funcid
iv_ppeguid = iv_itob-ppeguid
iv_objtype = c_objtype_equi
IMPORTING
ev_pre_funcid_identical = lv_pre_funcid_identical.
IF lv_pre_funcid_identical = c_no.
RAISE not_found.
ENDIF.
ENDMETHOD.
Coding of interface method IF_EX_BADI_CCM_EXPLOSION~SGAP_CHECK
METHOD if_ex_badi_ccm_explosion~sgap_check.
DATA:
lv_ppeguid TYPE pvs_guid_ccc,
CLEAR lv_ppeguid.

EXPORTING
iv_funcid = is_gap_data-funcid
iv_ppeguid = lv_ppeguid
iv_objtype = c_objtype_gap
IMPORTING
Page 111 of 177

RAISE not_found.
ENDIF.
ENDMETHOD.
Coding of interface method IF_EX_BADI_CCM_EXPLOSION~BITEM_CHECK
METHOD if_ex_badi_ccm_explosion~bitem_check.
DATA:
lv_ppeguid TYPE pvs_guid_ccc,
CLEAR lv_ppeguid.

EXPORTING
iv_funcid = is_bitem_data-funcid
iv_ppeguid = lv_ppeguid
iv_objtype = c_objtype_cbomitem
IMPORTING
RAISE not_found.
ENDIF.
ENDMETHOD.
The interface methods are not implemented IF_EX_BADI_CCM_EXPLOSION~FLOC_CHECK and

IF_EX_BADI_CCM_EXPLOSION~ CONFIG_CHECK_FILTER_ELEMENTS are not implemented.
Page 112 of 177

12.5.3 BAdI BADI_CCM_EXPL_ALWD
12.5.3.1 General remark

For our example the implementation of BAdI BADI_CCM_EXPL_ALWD take place in class
ZCL_IM_IMP_CCM_EXPL_ALWD.
12.5.3.2 Interface methods
Coding of interface method MPL_NODE_CHECK
This coding is taken over from the inactive implementation BADI_CCM_EXPL_ALWD (Impl.: Restrict
structure explosion of allowed configuration)
method IF_EX_BADI_CCM_EXPL_ALWD~MPL_NODE_CHECK.
* Method to stop an explosion depending on some parameters:
* IS_PNODID-CLINT: internal representaion of product class
* CT_STRUCT: table of relations which are exploded. This table
* can be modified: by deleting entries the new nodes indicated
* by PNGUID2 are not taken into account and are no further
* exploded
* Default implementation: whenever the product class from current node

* (IS_PNODID-CLINT) differs from the the new node (CT_STRUCT-pguid2),
* the explosion is stopped by deleting this relation
data: ls_struct type pvs_struct,

lt_pnodid_li_tab type PPET_PNODID_LI_TAB,
ls_pnodid_li type PPET_PNODID_LI,
lt_pncmp_tab type PPET1_PNCMP_LI_TAB.
check not IS_PNODID-CLINT is initial.

check not CT_STRUCT[] is initial.
loop at CT_STRUCT into ls_struct where otype2 eq 'N'.

clear ls_pnodid_li.
ls_pnodid_li-pnguid = ls_struct-pnguid2.
append ls_pnodid_li to lt_pnodid_li_tab.
endloop.
CALL FUNCTION 'PVSLICMP_PN_READ'

EXPORTING
im_msg_handling = ppet_msg_options-do_none
im_with_text = space
CHANGING
ch_pnodid_tab = lt_pnodid_li_tab
CH_PNCMP_TAB = lt_pncmp_tab.
loop at lt_pnodid_li_tab into ls_pnodid_li

where clint ne IS_PNODID-CLINT.
delete CT_STRUCT where otype2 = 'N' and
pnguid2 = ls_pnodid_li-pnguid.
endloop.
**********************************************************
* IBS-DI: method has been created for note 458558
endmethod.
Coding of interface method CONFIG_CHECK_FILTER_ELEMENTS
Page 113 of 177

This coding is taken over from the inactive implementation BADI_CCM_EXPL_ALWD (Impl.: Restrict
structure explosion of allowed configuration)
method IF_EX_BADI_CCM_EXPL_ALWD~CONFIG_CHECK_FILTER_ELEMENTS.
************************************************************************
* !! DON'T replace this piece of coding in the new BADI implementation *
* It is used to distinguish between partial and complete configuration *
* check. In case of partial configuration check the configurations are *
* filtered out in this method. *
************************************************************************
class cl_ex_badi_ccm_expl_alwd definition load.

check
cl_ex_badi_ccm_expl_alwd=>if_ex_badi_ccm_expl_alwd~gv_bypass_badi
is initial.
************************************************************************
* !!! PUT YOUR OWN CODE HERE !!! *
************************************************************************
endmethod.
12.6 Usage and results

After implementation the Configuration Control Workbench offers the following functionality to load
and check data (see Figure 102):
 For partial check

o Load: Partial load of actual structure
o Check: Partial load of MPL and partial check
If you’ve pressed the ‘Load’ button for the corresponding entry object of the actual structure,
it only makes sense to press the ‘Check’-button.
 For complete check:
o Load (Extended): Complete load of the actual structure
o Check (Extended): Complete load of the MPL and complete check
If you’ve pressed the ‘Load (Extended)’ button for the corresponding entry object of the
actual structure, it only makes sense to press the ‘Check (Extended)’-button.
Page 114 of 177

Figure 102 Buttons for load and check
Figure 103 is showing the result of the complete check on aircraft level contains the aircraft and the
engines (starting point functional location FLAC01 or top equipment EAC01-01). All parts of the
aircraft and the engines are checked!
Figure 103 Complete check on aircraft level
Page 115 of 177

Figure 104 is showing the partial check of the aircraft. This check only takes care of the original parts
of the aircraft. The engines are only checked on top level. That means only the material number of
these installed equipment ELENGINE and ERENGINE representing the complete engines and the
quantity is checked. The parts of the engines themselves are out of scope in this check.
Figure 104 Partial check for the aircraft only
Figure 105 is showing the possible entry points of the technical objects for the check. The entry
points are the technical objects – functional locations or equipment - of the actual structure you
want to perform the check. Please keep in mind that the Configuration Control Workbench can’t
check a single equipment or cBOM-item. Starting with the entry point the workbench is to find the
top equipment using the rules shown in Figure 37. With the rules the corresponding top equipment is
determined to start the check with. When you start with a functional location the determination of
the top equipment is starting with the step ‘Read this functional location’ in Figure 37.
Page 116 of 177

Figure 105 Entry points for check
Figure 106 is showing the complete check of the right engine.
Figure 106 Complete check of the right engine
12.7 FID Grouping (3)

With the usage of coupled MPLs we can have a detailed look on the FID grouping. Please refer to
chapter 5.6.7 and 6.3.4.
If you perform a complete check for the aircraft you may wonder on the fact, that inside the
exploded MPL the structure nodes for the engine are all duplicated (see Figure 107). This is not
Page 117 of 177

because of the fact that the aircraft contains two engines! It is because of the different configuration
of the left and right engine inside the actual structure! The left engine is using for the bolt the
material with the material number BOLT01, the right engine is using for the bolt the material with
the material number BOLT02. That means we have got different set of rules for the left and for the
right engine. At the end we have got two major FID groups for the engine, one for the left engine,
one for the right engine.
Figure 107 FID grouping in UI
The same is valid for ECM data (see chapter 11).
To sum it up the FID grouping differs between
 Different configuration data within the top equipment

 Different filter data for ECM within the top equipment
 Different Top-Assembly-FID inside the MPL (since EhP4, see chapter 0).
Figure 108 is showing the details for the FID group relevant checks. The check routines of
configuration control checks whether the corresponding parts of the actual structure fulfills the rules
of this FID groups In Figure 109 you can find the equipment and BOM items assigned to the FID-
groups..
Page 118 of 177

Figure 108 FID group relevant checks in detail
Page 119 of 177

Figure 109 FID grouping of the actual structure for the individual objects
As we now have all basics Figure 110 is showing the way how configuration control determines the
valid materials from the MPL
Page 120 of 177

Figure 110 Overview: How Configuration Control determines valid materials
This process chart is later on important to understand the way interchangeability and Set-
Relationship is working.
Page 121 of 177

12.8 Multiple usage of subordinate MPL, Top-Assembly-FID

So far we act under the assumption that the access node of the subordinate MPL is only allowed to
be assigned to one single structure node of the same superior MPL. This rule is valid for the
Configuration Control approach for releases lower than EhP4!
Anyhow it is allowed to assign a subordinate MPL to different superior MPLs. Precondition is that this
superior MLPs are not linked to each other anyhow!
Since EhP4 it is allowed to link the access node of a subordinate MPL to different structure nodes of
the same superior MPL. Now it is important - while creating the FID-groups - also to divide between
different Top-Assembly-FIDs (Top-FIDs) for the FID grouping. These are the node names of the
structure nodes of the superior MPL where the access nodes are linked to.
Let’s assume an aircraft is using an identical subassembly in different locations inside a MPL. E.g. an
air condition device which might be used inside the cockpit, galley, ....
In Figure 111 the structure node SN_DEV01 and SN_DEV02 represents the top nodes of complex
subordinate assemblies. These assemblies contain the same parts, so it seems quite logical use the
same subordinate MPL for checks. This subordinate MPL is starting with the access node AN_DEV in
the example shown in Figure 111.
Figure 111 Multiple usage of subordinate MPL
For the FID-grouping the structure nodes names SN_DEV01 and SN_DEV02 are used for the grouping
purpose and are called Top Assembly FIDs (Top-FIDs). That means that two FID groups are build for
this example.
Page 122 of 177

13 Details of quantity check
13.1 Motivation
Within this chapter we concentrate on the different methods of the quantity check (please see also
SAP note 1599891 [SAP N1599891]).
13.2 How does the quantity check in Configuration Control work from a
technical point of view?
The quantity check of Configuration Control is located inside the BAdI BADI_CCM_QTY_CHECK. This
BAdI is for single usage only and can be influenced by customer with own implementation.
There are existing two methods
 CONFIG_CHECK_QUANTITY
 QUANTITY_CHECK_FOR_FID
within this BAdI for different ways of quantity checks:
 Default implementation of method CONFIG_CHECK_QUANTITY

o Check quantity for all technical objects – equipment and BOM-items - using the
same
 FID/structure node name
 configuration
 parameter effectivity data
 superior structure node with the same Top-Assembly-FID (since EhP4)
The technical objects are grouped by using the four conditions from above in the FID-
groups. Within such a group the actual quantity is determined and checked against
the allowed quantity from the MPL.
o The allowed quantity is determined by the MPL by using the same conditions from
above (FID, configuration, parameter effectivity data, Top-Assembly-FID) by climbing
up the structure inside the MPL, with respect to coupled MPLs, and multiplying
related quantities of the structure nodes.
o The method is raising the message CCMM 033 when the quantity doesn’t match.
o The call stack is showing the place where the method CONFIG_CHECK_QUANTITY is
called:
Page 123 of 177

Level Program object

13 METHOD IF_EX_BADI_CCM_QTY_CHECK~CONFIG_CHECK_QUANTITY
CL_DEF_IM_BADI_CCM_QTY_CHECK==CP
12 METHOD IF_EX_BADI_CCM_QTY_CHECK~CONFIG_CHECK_QUANTITY
CL_EX_BADI_CCM_QTY_CHECK======CP
11 METHOD CONFIG_CHECK_FOR_GROUP CL_CCM_CONFIG_CHECK_GROUP=====CP
10 METHOD CONSTRUCTOR CL_CCM_CONFIG_CHECK_GROUP=====CP
9 METHOD CHECK_AS_MNTD_VS_ALLOWED_CONF
CL_CCM_CONFIG_CHECK_HEADER====CP
8 METHOD RUN_CONFIGURATION_CHECK CL_CCM_CONFIG_CHECK_HEADER====CP
7 METHOD CONFIGURATION_CHECK CL_CCM_CONFIGURATION_MANAGER==CP
6 METHOD HANDLE_BUTTONS CL_CCM_CFG_CHECK_AREA=========CP
5 METHOD ON_CLICKED CL_DD_BUTTON_ELEMENT==========CP
4 METHOD ON_SAPEVENT CL_DD_FORM_ELEMENT============CP
3 METHOD DISPATCH CL_GUI_HTML_VIEWER============CP
2 METHOD DISPATCH CL_GUI_CFW====================CP
1 MODULE (PAI) DISPATCH SAPLCCM_CFG_CONTROLLER
Page 124 of 177

 Default implementation of method QUANTITY_CHECK_FOR_FID

o Check quantity for all technical objects using the same FID! This check is collecting all
the technical objects with the same FID regardless the configuration or parameter
effectivity data and creates an overall sum.
o Always the quantity of the first found, valid structure node variant for a FID is used
inside this quality check.
o The overall allowed quantity is determined by climbing up the structure inside the
MPL, with respect to coupled MPLs, and multiplying related quantities of the
structure nodes.
o Since ECC600 EhP4 at least the superior objects with the same FID are used to create
the groups to determine the overall sum. This is to respect the location inside the
MPL.
o This check was created by using the following assumption: The quantity is identical
for all valid variants of a structure node. The material can differ. This design was a
requirement of the civil aircraft operation, were the aircrafts supposed to be very
symmetric.
o The method is raising the message CCMM 052 when the quantity doesn’t match.
o This check is only performed when the check of CONFIG_CHECK_QUANTITY is passed
successfully.
o The call stack is showing the place where the method QUANTITY_CHECK_FOR_FID is
called:

11 METHOD IF_EX_BADI_CCM_QTY_CHECK~QUANTITY_CHECK_FOR_FID
CL_DEF_IM_BADI_CCM_QTY_CHECK==CP
10 METHOD IF_EX_BADI_CCM_QTY_CHECK~QUANTITY_CHECK_FOR_FID
CL_EX_BADI_CCM_QTY_CHECK======CP
9 METHOD CHECK_AS_MNTD_VS_ALLOWED_CONF
CL_CCM_CONFIG_CHECK_HEADER====CP
8 METHOD RUN_CONFIGURATION_CHECK CL_CCM_CONFIG_CHECK_HEADER====CP
7 METHOD CONFIGURATION_CHECK CL_CCM_CONFIGURATION_MANAGER==CP
13.3 Example
13.3.1 Situation
Within our example we want to model an aircraft using the subordinate MPLs which is using a non-
symmetric approach concerning the quantity. The aircraft should have three engines:
 Right engine
 Left engine
 Middle engine
Depending on the location of the engine at the aircraft, a different quantity of parts (material
number ENPART01) must be used for the engine (see Figure 112).
Page 125 of 177

Figure 112 Aircraft with asymmetric usage of the quantity of the parts inside the engines
The MPL of the engine should be modeled as separate MPL. Apart of the quantity of the part
ENPART01 the three engines are identical. Within the data model of the engine we want to manage
the different quantity via object dependency.
The aircraft itself is modeled as a separate, superior MPL.
The precondition for the following modelling approach is the usage of Ehp4.
For the actual structure we only use equipment.
Please note that the modelling of this example is not pretty realistic, but it should serve to explain
the quantity check best.
Figure 113 is showing the MPLs of our example. Figure 114 is showing the equipment structure.
Figure 115 is showing the result of the complete check of the aircraft starting with top equipment
EAC02-01.
Page 126 of 177

Figure 113 MPLs of the example
Figure 114 Equipment structure of the example
Page 127 of 177

Figure 115 Result of the complete check of the aircraft
Please remember chapter 0 which is also relevant for FID grouping here.
Before we start to discuss the results of the check shown in Figure 115 it is important to notify the
order of the variant explosion of the structure node EN02_PART01 below the structure node
SN_WENGINE:
Page 128 of 177

 First the data to check the left engine is exploded (2 parts of material ENPART01 necessary,
variant SV02 of structure node SN_WENGINE)
 than the data to check the right engine is exploded (1 parts of material ENPART01 necessary,
variant SV01 of structure node SN_WENGINE). The order the program is exploding the
variants of a structure node is more or less accidental. This is important to understand the
results of the quantity check.
The error message CCMM052 for the complete check of the aircraft is misleading here. This behavior
can be explained by the design prerequisites of the implementation of the responsible method
QUANTITY_CHECK_FOR_FID of BAdI BADI_CCM_QTY_CHECK (see chapter 13.2).
How can the allowed quantity for the device with the FID EN02_PART01 below the superior device
SN_WENGINE can be explained for the complete check of the whole aircraft?
1. The allowed quantity for the device with the FID EN02_PART01 of the engine MPL, located
below the device with the FID SN_WENGINE, is determined the following way (see chapter
13.2):
2 (first found valid variant SV02 of structure node EN02_PART01) •1)
2 (Structure node SN_WENGINE) •
1 (Access node EAC02_01) =
4
1
) For the right and left engine the same path to the most top access node in the MPL
concerning the FID is valid (EN02_PART01 → SN_WEngine → EAC02_01). The configuration
for the right or left engine is not taken into account (one part of material ENPART01 for right
engine, two parts of material ENPART01 for left engine) for this quantity check. The quantity
of the first found, valid variant of the possible set of valid variants is used.
These valid variants are drawn by the MPL explosion beforehand. Although this explosion is
respecting the configuration of the equipment (left and right engine) the quantity check
inside method QUANTITY_CHECK_FOR_FID of BAdI BADI_CCM_QTY_CHECK relies on the FIDs
and the resulting FID-groups only. This means the right and left engine are within the same
FID group and are handled with the same quantity – here the quantity of the first valid
variant SV02 determined for the FID-group by the program. Keep in mind that the example is
build into EhP4. That means at least the FIDs of the superior objects are respected and the
quantity for the middle engine (three parts of material ENPART01) is out of scope.
Page 129 of 177

2. As the example was made in an EhP4 system the FIDs of the superior objects are respected.
The allowed quantity for the device with the FID EN02_PART01 of the engine MPL, located
below the device with the FID SN_MENGINE, is determined the following way:
3 (first valid variant SV03 of structure node EN02_PART01) •2)
1 (Structure node SN_MENGINE) •
1 (Structure node SN_PART01) •
1 (Access node node EAC02_01) =
2) The valid variants are drawn by the MPL explosion beforehand. This explosion is
respecting the configuration and determines the variant SV03 of the structure node
EN02_PART01 as valid. But the quantity check inside method QUANTITY_CHECK_FOR_FID
of BAdI BADI_CCM_QTY_CHECK relies on the FIDs and the resulting FID-groups only. As
there is only one valid variant SV03 with quantity 3 drawn by the MPL explosion
beforehand the quantity 3 is used for checking purpose. The differentiation between
right/left engine and middle engine happens in EhP4 because the quantity check respects
the FIDs of the superior objects.
3. In addition 7 valid parts are determined. Performing the same test in a system below EhP4,
the amount of valid parts would be 2 as the possible different locations of the device with
the FID EN02_PART01 are not respected.
If the configuration check is started at the level of equipment

 EAC02-01-RENG (complete check for the right engine)
 EAC02-01-LENG (complete check for the left engine)
 EAC02-01-MENG (complete check for the middle engine)
no error message occurs.
13.3.2 Recommendation
Whenever you plan to model such a non symmetric situation within Configuration Control it is
recommended to switch of the message CCMM 052 by customizing, to avoid confusing messages
coming up from method QUANTITY_CHECK_FOR_FID of BAdI BADI_CCM_QTY_CHECK. You can use
the customizing transaction OMPL1 for Configuration Control message customizing for that purpose
(see Figure 116).
The checks running in the method CONFIG_CHECK_QUANTITY of BAdI BADI_CCM_QTY_CHECK are

not touched by this change.
Another possibility would be an own implementation of the BAdI BADI_CCM_QTY_CHECK.
Page 130 of 177

Figure 116 Change customizing with transaction OMPL1
After changing the customizing the result of the complete check looks as shown in Figure 116.
Figure 117 Complete check of the aircraft after changing the customizing
Figure 118 is showing the effect on the quantity check when the equipment EEN02-PART01-02 is
dismantled via transaction IE4N. Using IE4N a structure gap is created.
Page 131 of 177

Figure 118 Dismantling EEN02-PART01-02 via IE4N
Figure 119 is showing the effect on the quantity check when the equipment EEN02-PART01-02 is
dismantled via transaction IE02. Using IE02 no structure gap is created.
Figure 119 Dismantling EEN02-PART01-02 via IE02
Page 132 of 177

14 Interchangeability
14.1 Motivation
In logistical processes it is often necessary to interchange parts. Within Discrete Industries and Mill
Products (DIMP), the following functions are provided [SAP Help, Parts Interchangeability].
Parts interchangeability comprises the following functions [SAP Help, Parts Interchangeability]:
 Fully interchangeable parts
o Parts that are fully interchangeable with each other and are grouped in a common
class of interchangeable parts - a form-fit-function class (FFF class).
o You can group fully interchangeable parts of an FFF class in MPN-MRP sets subject to
plant and MRP area. The system treats these parts as fully interchangeable parts in
planning, inventory management, and the availability check.
o Inventory-managed manufacturer parts
Some parts from different manufacturers are interchangeable in the purchasing,
MRP and availability check functions due to having the same technical
characteristics. The system recognizes these as interchangeable and manages them
with their own individual stocks.
 Restricted or one-way interchangeable parts
These parts cannot belong to the same FFF class. You use interchangeability codes to group
these parts. Restricted interchangeability is available for all processes that support MPN.
 Material exchange functions are available in the following applications:
o Material Exchange Using SCM
o Material Exchange in Purchasing
o Material Exchange in MRP
o Material Exchange in Inventory Management
Goods movement using transaction code MIGO. You can interchange parts in the
following:
 Goods issue for the stock transport order and reservation
 Goods receipt for the purchase order
o Material Exchange in the Sales Order Product Selection
o Creation of subitems in stock transport orders. For more information, see Material
Exchange in Stock Transport Orders.
o Material Exchange in PM Orders, PP Orders, and Networks
 Supersession
Changes to the design, form and function of parts require vendors and manufacturers to
replace obsolete parts with new versions of the same parts. If a new version of a part can
replace the old version, the system issues a new part number. The new number requires
changes to be made in stock, in procurement, in production, in material requirements
planning and in sales; that means in all core processes in the supply chain. You must also
determine replacement rules and validity dates for the new part.
The configuration check supports the following interchangeability functions [SAP Help, Additional
Features]:
 Interchangeability using form-fit-function classes (FFF class). The system considers a part
suitable for interchangeability if it belongs to the same FFF class.
Example:
Part MATA is assigned to the structure node (function identifier) with only one valid
variant. Part MATA has been assigned to the same FFF class as part MATB. Therefore,
the configuration check for the function identifier also evaluates part MATB as valid.
 Rules-based ATP check in SAP SCM.
Page 133 of 177

Within this documentation only the classical approach with FFF classes is described. Within the
material interchangeability only fully interchangeability is supported by Configuration Control.
Pretty important for the usage of the interchangeable parts in Configuration Control is the
knowledge about the fact who is maintaining this data. The interchangeability data usually is
managed by the material management or logistic department. Whilst the materials inside the
structure nodes of the MPL for Configuration Control purpose are managed by the maintenance
department after being approved as valid material for the set of rules. Therefore often materials
being taken as valid interchangeable parts form logistic perspective are not allowed in the context of
configuration control.
14.2 Integration in Configuration Control

Figure 120 is showing how the interchangeability is integrated into configuration control.
Figure 120 Integration into Configuration Control
For every found valid material inside a structure node variant the interchangeability functionality is
trigger to determine possible interchangeable materials. This is increasing the runtime (see chapter
14.5).
14.3 Modelling
The modelling should be demonstrated at a very small example, where the three materials
 EXAMPL14_00017
 EXAMPL14_00018
 EXAMPL14_00019
Page 134 of 177
should be fully interchangeable.
First we have to define a suitable Manufacturer Part Profile, that allows us to use the
interchangeability functionality within our business process. Figure 121 is the necessary settings in
customizing for the MPN profile EX14.
Figure 121 Manufacturer Part Profile
In the next step we define material master data for a so called Form-Fit-Function-Class (FFFC) which
we use later on to assign the material to be interchangeable (please see Figure 122). Within this
special type of material we have to enter the Manufacturer Part Profile. The material type FFFC has
to be used.
Inside the MPL we only maintain the single variant 1 for structure node EXAMPL14_00007 which
contains the material EXAMPL14_00017 as valid material (see Figure 123).
Via transaction PIC01 we define the interchangeable materials for the FFF-class FFFC_EXAMPL14_01
(see Figure 124).
Page 135 of 177

Figure 122 Form-Fit-Function-Class FFFC_EXAPL14_01
Figure 123 MPL of example
Page 136 of 177

Figure 124 Define materials for FFF class
The equipment 10033100 linked via the FID EXAMPL14_0007 of the actual structure contains the
material number EXAMPL14_00019.
Figure 125 is showing the result of the check of Configuration Control. Looking at the details for the
structure node EXAMPL14_00007 three valid materials can be found:
 One with the structure node variant number 1 which is EXAMPL14_00017. This material is
coming form the MPL.
 Two with no structure node variant number which are EXAMPL14_00018 and
EXAMPL14_00019. These materials are coming from the interchangeability information from
the FFF class FFFC_EXAMPL14_01.
Page 137 of 177

Figure 125 Result of Configuration Control Check
Page 138 of 177

14.4 Interchangeability, object dependency and parameter effectivity

Materials determined by interchangeability are not checked against the current filter criteria given by
configuration (object dependency) and parameter effectivity (ECM) used inside the MPL explosion!
Let’s assume a structure node has got the two variants
 SV1 with material A
 SV2 with material B
Via object dependency and configuration of the top equipment linked to the corresponding access
node the material B is filtered out within the MPL explosion because it is not valid.
But, via the corresponding FFF Class the material A should be interchangeable with material B. As the
interchangeability functionality runs ‘outside’ configuration control as own application, material B is
now drawn as valid material, although it is forbidden by the MPL rules. That means a material
excluded by rules of MPL can come in via interchangeability again.
14.5 Runtime
In general every approach of interchangeability (classical FFF classes or Rules-based ATP check) inside
Configuration Control is increasing the runtime of the check in a considerable way. Therefore it is
recommended to insert all valid materials inside the structure node variants and switch of the
interchangeability.
14.6 How to switch of interchangeability in Configuration Control?

Unfortunately there doesn’t exit an explicit switch to switch off the interchangeability functionality in
Configuration Control. If you are sure, that you do not want to use interchangeability inside
Configuration Control you should switch it off with the code modification shown below.
To switch of this functionality you have to modify the internal Aerospace & Defense implementation
'DIAD_CCM_INTERNAL' of the BADI BADI_CCM_INTERNAL. Inside the method
'ADD_INTERCHANGEABLE_PARTS ' a 'RETURN.'-statement should be inserted at the very beginning of
the method (see note 1536543).
Coding of method IF_EX_BADI_CCM_INTERNAL~ADD_INTERCHANGEABLE_PARTS of implementation

DIAD_CCM_INTERNAL of BAdI BADI_CCM_INTERNAL (up to EhP3)
METHOD if_ex_badi_ccm_internal~add_interchangeable_parts .
DATA: lt_fully_ic TYPE STANDARD TABLE OF v_picpsrl,

lt_fully_ic_val TYPE STANDARD TABLE OF v_picpsrl,
l_werks TYPE werka,
ls_fully_ic TYPE v_picpsrl,
ls_fully_ic_val TYPE v_picpsrl,
lt_picpsrl_01 TYPE STANDARD TABLE OF v_picpsrl, "N929933
lt_picpsrl_02 TYPE STANDARD TABLE OF v_picpsrl, "N929933
l_et_picpsrl TYPE v_picpsrl,
l_pnodid_ext TYPE ppet_pnodid_ext,
l_objid_ext TYPE balpval,
l_msgv1 TYPE msgv1,
l_s_msg TYPE bal_s_msg,
l_s_par TYPE bal_s_par,
l_context TYPE mpl_bal_context,
l_materials_for_node TYPE mpl_materials_for_node.
FIELD-SYMBOLS: <source> TYPE x,

<target> TYPE x.
*-----ADPIC ERP2007
DATA: lr_adpic_services TYPE REF TO cl_adpic_services,
lt_picps_all TYPE adpic_t_material,
ls_picps_all TYPE adpic_s_material,
lt_return TYPE adpic_t_bapiret2,
lt_all_parts_for_node_buffer TYPE tab_mpl_materials_for_node,
l_materials_for_node_buffer TYPE mpl_materials_for_node.
Page 139 of 177

DATA: lt_mat_msg TYPE adpic_t_mat_msg,

lt_smesg TYPE tsmesg,
ls_smesg TYPE smesg,
ls_ref_mara TYPE mara,
lr_check_engine TYPE REF TO cl_adpic_check_engine.
*-----
RETURN. "Modification: Leave method Insert RETURN statement to leave

method for interchangeable
REFRESH lt_fully_ic.
REFRESH lt_fully_ic_val. materials
WRITE is_filt_expl-locid TO l_werks.
BREAK-POINT ID adpic_rc_add_ic_mats_ccm2.
(…)
14.7 Summary of Restrictions

In general the following restrictions do exist:
 Interchangeability is only available in Aerospace & Defense
 Classical interchangeability: Only fully interchangeability using form-fit-function classes
applies.
 Interchangeability is only available for structure node variants
 The rules of object dependency and ECM are not taken into account
Page 140 of 177

15 Set-Relationship
15.1 Motivation
In Configuration Control for SAP for Aerospace & Defense, you can create set relationships between
material variants in different structure nodes of a MPL. Set relationships indicate that a part
(material), which is MPL structure node variant, can be used only in combination with another part
(material) in a different MPL structure node of the same MPL. Parts that are related to each other
belong to the same set [SAP Help, Set Relationship].
Figure 126 Small example for Set Relationship
Figure 126 is showing an example where Set Relationship approach is used to set up a rule between
the structure nodes SN01 and SN04 of a MPL. The set combination contains a list of set variants.
These set variants contains the information of the related structure nodes and the chosen structure
node variants.
15.2 Usage and modelling

To make use of the Set Relationship approach we have to activate the corresponding customizing
(see Figure 127, transaction OMPL2).
In the next step we define a set combination for an existing MPL starting with the access node
EXAMPL15_00001. Figure 128 is showing the initial step to create a set combination. The application
has to be SET (SET Documentation) and the type has to be S_SET (Combination). The name of the set
combination is EXAMPL15_00001 and should create a relation between the structure nodes
EXAMPL15_00002 and EXAMPL00010 of this MPL. We just use the same name for the set
combination as used for the access node in this example.
Page 141 of 177

Figure 127 Activate Set Relationship for Configuration Control
Page 142 of 177

Figure 128 Create a set combination
In the next step we have to define the set variants and the structure nodes which should take part
into the set combination (see Figure 129).
Figure 129 Add set variants and structure nodes to the set combination
Page 143 of 177

Save the definition of the set combination and start to maintain the set variants (see Figure 130).
Figure 130 Start to maintain the set variants
In the next steps (see Figure 131, Figure 132, Figure 133 and Figure 134) you can find how to assign
the structure node variants to the set variant SV01. We have to do the same for the set variants SV02
and SV03. The result of the assignment can be found in Figure 135.
Page 144 of 177

Figure 131 Maintain set variant SV01 (Set Variant 01) – Part 1
Page 145 of 177

Page 146 of 177

Page 147 of 177

Figure 135 Result of the definition
If we start the Configuration Control Check via transaction CCM2 for the related top equipment
10033101 we get the result as shown in Figure 136. So far we do not have any issue into the actual
structure.
Page 148 of 177

Figure 136 Result of Configuration Control Check
Inside the log of the MPL explosion we can see the entries of the Set Relationship functionality (see
Figure 137)
Page 149 of 177

Figure 137 Log of MPL explosion
With our example we create an additional rule which is checking the material combination in the
actual structure of
 the equipment 10033102 (FID EXAMPL15_00002, material number EXAMPL15_00004) and

 the equipment 10033110 (FID EXAMPL15_00010, material number EXAMPL15_00028)
The combination of the material numbers of these equipment fulfils the rule of set variant SV03 (see
Figure 135).
In the next step we change for testing purpose manually (without any material-to-material
movement) the material number from equipment 10033110 from EXAMPL15_00028 to
EXAMPL15_00026. Without the defined set combination EXAMPL15_00001 this would be a valid
material number. But with this set combination the result is as expected (see Figure 138). The
combination of the material numbers of equipment 10033102 and 10033110 violates the rules of the
set combination EXAMPL15_00001. Due to this both equipment are mentioned as not valid inside
the check of Configuration Control.
Page 150 of 177

Figure 138 Rule violation
Page 151 of 177

Below you can find some important rules to define a set combination:
 Create a set combination only within one and the same MPL! A Set Relationship between
different MPLs is not supported.
 It is possible to define more than one set combination for a MPL
 A set combination must contain at least two structure nodes. These structure nodes must be
part of the same MPL. It is allowed to have more than two structure nodes assigned to a set
combination.
 If one structure node variant of a structure node is member of a Set Variant, every structure
node variant of this structure node must be part of a Set Variant of this set combination
anyhow!
 A structure node (and its variants) can be part of more than one set combination. But this
depends on the customizing of the relations type of the used node type S_SET we used in our
example (Customizing path: Production → Basic Data → Integrated Product Engineering →
iPPE Object Administration → Define General iPPE Relationship Types)
 Please also consider [SAP N1410845].
15.3 Integration in Configuration Control

Below you can find the call stack where the Set Relationship functionality is located:
16 METHOD GET_VALID_VARIANTS_IN_SET
CL_DEF_IM_BADI_MPL_IWB========CP
15 METHOD CHECK_SET_DEPENDENCY CL_DEF_IM_BADI_MPL_IWB========CP
14 METHOD IF_EX_BADI_MPL_IWB~GET_VALID_PARTS_PER_LOC
13 METHOD GET_TREE_HIERARCHY CL_DEF_IM_BADI_MPL_IWB========CP
12 METHOD IF_EX_BADI_MPL_IWB~GET_PRODUCT_STRUCTURE
CL_EX_BADI_MPL_IWB============CP
CL_MPL_IWB_ADAPTER============CP
9 METHOD LOAD_TARGET_CONFIGURATION
CL_CCM_TARGET_CONFIG==========CP
8 METHOD LOAD_ALLOWED_CONFIG CL_CCM_CONFIGURATION_MANAGER==CP
7 METHOD LOAD_CONFIGURATIONS_FOR_CHECK
CL_CCM_CFG_CHECK_AREA=========CP
Method GET_TREE_HIERARCHY is exploding the MPL and is passing the found structure nodes to
method GET_VALID_PARTS_PER_LOC. The method GET_VALID_PARTS_PER_LOC determines the
valid structure node variants with their material number of this structure node respecting object
dependency and parameter effectivity. Every found variant is than passed to the method
CHECK_SET_DEPENDENCY to check the material against the rules of the Set Relationship.
Figure 139 is showing the integration of the Set Relationship functionality into Configuration Control.
Page 152 of 177

Figure 139 Integration of Set Relationship functionalityRule violation
If there does exist more than one equipment or BOM-item and one single part number does not fit,
Set Relationship marked the current structure node variant SNVar as invalid!
With this there are additional facts to know:

Page 153 of 177
 If an equipment or BOM item - which is identified as part of a Set combination via its FID - is
containing a wrong part number (material number), eventually all the found valid part
numbers of the other structure nodes which are part of the Set combination get invalid. This
leads to the fact, that there doesn’t exist any valid part numbers for the structure node for
the Configuration Control check at the end. For the Set Relationship check only the FID and
the material number of the equipment or BOM item is relevant.
 The Set Relationship check does not respect any hierarchy of technical objects. The
installation location of an equipment and its hierarchy level is out of interest. All equipment
are equal form the perspective of the Set Relationship check. The check is only using the FID,
as the assignment to the set combination happens via the structure node name/FID.
 If a combination of equipment/BOM items is wrong, only a statement can be made that
something with the equipment/BOM items grouped together via a set combination goes
wrong. This means that, the more equipment/BOM items with different FID taking part at a
set combination the more difficult is the finding of the cause of an error. Quantities greater
than one also making the finding of a possible issue complex. To find the single object which
is wrong inside the combination
The following examples (Figure 140, Figure 141, Figure 142, Table 8, Table 9 and Table 10 )should
demonstrate the behavior.
Example 1
Figure 140 Example 1
Page 154 of 177

Case Equi. EQ02 Equi. EQ03 Equi. EQ04 Equi. EQ05 Result of check in Configuration Control
FID SN01 FID SN02 FID SN01 FID SN02
1 MAT01 MAT03 MAT01 MAT03 No error.
2 MAT01 MAT04 MAT01 MAT03 Error on equipment EQ01, EQ03 and EQ04.
Only equipment EQ05 is passing the check. 1)
4 MAT02 MAT04 MAT01 MAT03 Error on all equipment.
Remarks:
1) Checking the material MAT03 of structure node variant 01 of structure node SN02 it is
determined, that all the equipment with the FID SN01 contains the material number MAT01.
Because of this the material MAT03 of structure node variant 01 of structure node SN02 is
handled as valid part number for the further validity check in Configuration Control. Because
of this the set variant SV01 is fulfilled and because of this only equipment EQ05 is passing the
check in Configuration Control successfully, as for the structure node SN02 a valid part
number was find via the Set Relationship check.
Table 8 Cases for different material numbers for the equipment of example 1
Page 155 of 177

Example 2
Page 156 of 177

Case Equi. EQ02 Equi. EQ03 Equi. EQ04 Equi. EQ05 Result of check in Configuration Control
FID SN01 FID SN02 FID SN01 FID SN02
4 MAT02 MAT04 MAT01 MAT03 Error on all equipment.
Remarks:
The result of the check for example 1 and 2 is the same as the installation location is of interest!
Page 157 of 177

Example 3
Case Equi. EQ02 Equi. EQ03 Equi. EQ04 Result of check in Configuration Control
FID SN01 FID SN02 FID SN03
1 MAT01 MAT03 MAT05 No error.
2 MAT01 MAT04 MAT05 Error on all equipment.
3 MAT02 MAT04 MAT06 No error.
15.4 Restrictions and recommendations

Restrictions:
 Set Relationship does not work inside the local check of IE4N
 Set Relationship is only part of the Aerospace & Defense functionality
Recommendations:
 From the runtime perspective the usage of the Set Relationship functionality does decrease
the runtime of the check of Configuration Control. This is because of the additional explosion
of the set combinations. If possible avoid the usage of Set Relationship and try to replace it
by using Object Dependency.
 Because of the combinatorics and traceability you should avoid
o to use Set Relationship and Object Dependency within one structure node
o to use Set Relationship for structure nodes with quantities higher than one.
Page 158 of 177

16 Cancel-Part Relationships
16.1 Motivation
The Cancel-Part Relationships functionality is used to build up an additional set of rules inside the
MPL, which is checking the order in which parts can replace each other at the same installation
location inside an actual structure depending on the material number. With this it is possible to
model a part regression: If an equipment with the material number A was dismantled form an
installation location it can only an equipment with the material number B can be installed again at
this installation location. You can find further information at [SAP Help, Cancel-Parts Relationship].
16.2 Usage and modelling

This specific set of rules has to be defined for the structure node variants of a structure node. This
rule is than only valid for this structure node. The structure node variants of this structure node has
to be labeled with a special class AD_MPL_VARIANTS of the type 056 (iPPE Variant). With this
labeling Configuration Control is able to identify the structure node variants of a structure node
taking part at a Cancel-Parts Relationship block. This class must contain the characteristic
AD_CANCEL_PARTS where multiple values can be assigned to (see Figure 143).
Figure 143 Class AD_MPL_VARIANTS
The class AD_MPL_VARIANTS has to be created via the report
 RDIADCLGEN for A&D with the release lower or equal DIMP4.71

 RIMPLCLGEN for EA-APPL since EA2.0 and A&D higher than DIMP4.71
These reports are also creating the characteristic AD_CANCEL_PARTS.
Page 159 of 177

In the next step you’ve to activate the Cancel-Parts-Relationships functionality via customizing (see
Figure 144).
Figure 144 Activate Cancel-Part Relationships by customizing
By design the Cancel-Part Relationships functionality only works by installing a serialized equipment
or cBOM-item(s) by transaction IE4N. This means that this check only works together with the local
check functionality of IE4N (see chapter 8.5.2).
The Cancel-Part Relationships check inside Configuration Control is making use of the material
number of the part dismantled before via IE4N. This information can be found inside the structure
gap as preceding material number (see chapter 8.3).
To explain the functionality we use the small MPL shown in Figure 145. The structure node
AIRCRAFT_00003 should contain the set of rules shown in Figure 146. Figure 147 is showing the
adoption using the classification for each structure node variant of structure node AIRCRAFT_00003
via the class AD_MPL_VARIANTS.
Page 160 of 177

Figure 145 Cancel-Part Relationships for structure node AIRCRAFT_00003
Figure 146 Cancel-Part Relationships for structure node AIRCRAFT_00003, set of rules
Page 161 of 177

Figure 147 Cancel-Part Relationships for structure node AIRCRAFT_00003, adoption
In Figure 148 you can find the actual structure we use. We want to use this set of rules to check the
installation of equipment into the installation location equipment 10000697 via transaction IE4N.
Figure 148 Actual structure for Cancel-Part Relationships
Page 162 of 177

Figure 149 Possible replacement for equipment 10000698
Figure 149 is showing the equipment which should replace the equipment 10000698. Both
equipment have got the FID AIRCRAFT_00003.
First we dismantle the equipment 10000698 from equipment 10000697 using transaction IE4N. Using
transaction IE4N is essential, as only this transaction is creating a structure gap which is important for
the Cancel-Part Relationships functionality (see Figure 150). Doing this a structure gap was created
with the following attributes:

o Object number of the installation location/superior object: IE000000000010000697
o Functional identifier of the dismantled object (equipment or BOM item):
AIRCRAFT_00003
o Material Number of the dismantled object (equipment or BOM item):
AIRCRAFT_00005
o Object number of the dismantled equipment IE000000000010000698
Page 163 of 177

Figure 150 Dismantle equipment 10000698 via transaction IE4N
Theoretically we can install the equipment 10000698 into 10000697 again. This step would be
successful as in Cancel-Part Relationships general it is allowed to install a part with the same material
number as the material number of the part dismantled before.
In the next step we install the equipment 10000700 (Figure 149). This installation fulfills the rules of
Cancel-Part Relationships (see Figure 151). With this installation the structure gap was deleted.
In the next step we dismantle 10000700 with the material number AIRCRAFT_00006 with transaction
IE4N. ). Doing this a structure gap was created with the following attributes:

o Object number of the installation location/superior object: IE000000000010000697
o Functional identifier of the dismantled object (equipment or BOM item):
AIRCRAFT_00003
o Material Number of the dismantled object (equipment or BOM item):
AIRCRAFT_00006
o Object number of the dismantled equipment IE000000000010000700
If we now try to install the equipment 10000698 with the material number AIRCRAFT_00005 again
with IE4N we get an error message as this installation violates the Cancel-Part Relationships rule for
the structure node AIRCRAFT_00003 (see Figure 152):
A part with the material number AIRCRAFT_00005 can’t succeed a dismantled part with the
material number AIRCRAFT_00006 (see Figure 146).
Page 164 of 177

Figure 151 Install equipment 10000700 via transaction IE4N
Figure 152 Install equipment 10000698 via transaction IE4N again
The installation of equipment
 10000700 (material number AIRCRAFT_00006) or

 10000701 (material number AIRCRAFT_00007)
with transaction IE4N is successful. The rules of Cancel-Part Relationships rule for structure node
AIRCRAFT_00003 are fulfilled (see Figure 153).
Page 165 of 177

Figure 153 Install equipment 10000701 via transaction IE4N
Page 166 of 177

17 Mission dependent modelling and optional parts.

Since EhP 4 SAP is offering within the software layer EA-APPL within the enhancement spot
ES_CCM_CUST_CHECK the BAdI BADI_CCM_CHECK_SCOPE. This BAdI can be used to model a
mission dependent MPL or optional parts. The BAdI can be found in the customizing under Plant
Maintenance and Customer Service → Maintenance and Service Processing → System Enhancements
and Data Transfer → Business Add-Ins → Configuration Control → BAdI: Define Customer-Specific
Scope of Configuration Check.
Within the documentation of the BAdI BADI_CCM_CHECK_SCOPE an example is mentioned:
… There are assemblies in any industry with optional parts that are not required for normal
operation. For example a fighter aircraft can have various weapon systems, that can undergo validity
checks although they are not required and used for a flight. Normally, if a component is missing, the
configuration check will issue an error. However, if this component is optional, the check should not
issue an error because the component is intentionally not installed. The BAdI can be used to remove
allowed elements, if optional actual elements are missing. That way no error message will be issued
… [SAP BADI_CCM_CHECK_SCOPE].
Please understand that further remarks on this would go beyond the scope of this document. For
further questions on the implementation of this BAdI and the data model you should contact your
Configuration Control consultant.
Page 167 of 177

18 Data modeling and runtime

Beside the recommendations of the chapters before, please see SAP note 1536543 ‘Configuration
Control: Modeling and runtime’ [SAP N1536543] in addition.
Please understand that further remarks on this would go beyond the scope of this document. For
further questions you should contact your Configuration Control consultant.
Page 168 of 177

19 Used literature, bibliography

 [A4A]: Homepage of Airlines for America formerly known as Air Transport Association of
America (ATA): http://www.airlines.org
 [SAP BADI_CCM_CHECK_SCOPE]: Documentation of BAdI BADI_CCM_CHECK_SCOPE
 [SAP course WDECCT]: SAP course WDECCT 'Anlagenkonfiguration'
 [SAP Help, Additional Features]: SAP Business Suite, SAP ERP, SAP EHP5 for SAP ERP 6.0, SAP
for Aerospace & Defense, Maintenance, Repair and Overhaul (MRO), Maintenance ad Service
Processing, Configuration Control for SAP for Aerospace & Defense, Additional Features for
Overall Configuration Check,
http://help.sap.com/erp2005_ehp_05/helpdata/en/cc/71fe40f652f323e10000000a155106/c
ontent.htm?frameset=/en/1f/71fe40f652f323e10000000a155106/frameset.htm
 [SAP Help, Cancel-Parts Relationship]: SAP Business Suite, SAP ERP, SAP EHP7 for SAP ERP 6.0,
SAP ERP Central Component, Plant Maintenance (PM), Technical Objects (CS-BD/PM-EQM),
Configuration Control, Cancel-Parts Relationships,
http://help.sap.com/erp2005_ehp_07/helpdata/en/e3/67003f662e781fe10000000a114084/
content.htm?frameset=/en/31/68003f662e781fe10000000a114084/frameset.htm,
Processing Cancel-Parts Relationships,
http://help.sap.com/erp2005_ehp_07/helpdata/en/31/68003f662e781fe10000000a114084/
content.htm?frameset=/en/e3/67003f662e781fe10000000a114084/frameset.htm
 [SAP Help, Conversion of Standard iPPE Structures]: SAP ERP Central Component, Plant
Maintenance (PM), Technical Objects (CS-BD/PM-EQM), Configuration Control, Conversion of
Standard iPPE (PSV) Structures to MPL Structures,
http://help.sap.com/erp2005_ehp_07/helpdata/en/45/2655ee81702b31e10000000a1553f7
/content.htm?frameset=/en/31/68003f662e781fe10000000a114084/frameset.htm
 [SAP Help, iPPE]: SAP Business Suite, SAP ERP, SAP ERP 6.0, Integrated Product and Process
Engineering (iPPE),
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c9/f10736adb6cd0fe10000009b38f839/
frameset.htm
 [SAP Help, Parts Interchangeability]: SAP Business Suite, SAP ERP, SAP EHP5 for SAP ERP 6.0,
SAP for Aerospace & Defense, Maintenance, Repair and Overhaul (MRO), Inventory
Management, Parts Interchangeability,
http://help.sap.com/erp2005_ehp_05/helpdata/en/1a/86d2363e85070de10000009b38f839/
frameset.htm
 [SAP Help, Set Relationship]: SAP Business Suite, SAP ERP, SAP EHP5 for SAP ERP 6.0, SAP for
Aerospace & Defense, Maintenance, Repair and Overhaul (MRO), Maintenance and Service
Processing, Configuration Control for SAP for Aerospace & Defense, Set Relationships in
Configuration Control,
http://help.sap.com/erp2005_ehp_05/helpdata/en/70/71fe40f652f323e10000000a155106/
content.htm
 [SAP N815818]: SAP note 815818: iPPE: ECM processor determines incorrect change
statuses, SAP.
 [SAP N538751]: SAP note 538751: Creating an access link between equipment and iPPE node,
SAP.
 [SAP N1515830]: SAP note 1515830: CCM2 Missing Check for Access Link in Equipment, SAP.
 [SAP N1536543]: SAP note 1536543: Configuration Control: Modeling and runtime, SAP.
Page 169 of 177
 [SAP N1599891]: SAP note 1599891: CCM2: Quantity Check, SAP

 [SAP N1410845]: SAP note 1410845: Set relationships and material interchangeabilities in CC
 [SAP N1536543]: SAP note 1536543: Configuration Control: Modeling and runtime
Page 170 of 177

20 Table of messages of Configuration Control

Message number Message text See chapter
CCMM021 There is no top item of equipment 6.3.6
CCMM028 No structure gap exists at Equipment 8.5.3.1

<equipment number>, No structure gap
exists at Functional Location <functional
location number>
CCMM031 Material <material number> of Equipment 8.5.3.4, 8.5.3.5, 10.4

<equipment number> is not valid
Material <material number> of Structure

Gap (<installation location>)is not valid
CCMM033 <n> object(s) found below superior object 8.3.1, 8.5.3.1, 8.5.3.2, 11.7,
<object number>. Expected quantity is <m> 13.3.2
<unit>
CCMM034 Equipment <equipment number> (forced 8.5.3.4

installation mode). Material <material
number> is not valid.
CCMM035 Not all objects in FID group have the same 5.6.4
superordinate equipment
CCMM037 Function identifier SN_FT of Structure Gap 8.5.3.6

will be used for configuration check
CCMM038 FID <FID of object to be installed> deviates 8.5.3.6

from FID <FID of structure gap> of
previously installed object
CCMM041 Structure gap at Functional 8.3.1, 8.4.2, 13.3.2

Location/Equipment <object number>
CCMM045 No corresponding iPPE structure node 8.5.3.7

found for function identifier
CCMM046 Equipment <equipment number> has been 8.5.3.4, 8.5.3.6

installed with forced installation
CCMM047 Function identifiers of superior objects do 6.3.5, 6.4.4

not correspond at Equipment <equipment
number>
CCMM050 Quantity has not been checked 8.5.3.4
CCMM052 <n> objects were found for FID <FID of 13.3.1
Page 171 of 177

object(s) to be checked>. Expected amount

is <m> <unit>
CCMM128 No structure gap exists at <installation 8.5.3.1

location>
CCMM149 No structure gap exists for superior object 8.5.3.1

<object number>
CCMM176 Equipment <equipment number> installed 8.5.3.4

despite validation errors (forced
installation)
CCMM162 No further outstanding structure gap exists 8.5.3.1, 8.5.3.4

for installed equipment <equipment
number>
CCMM214 Structure gap has be deleted successfully at 8.5.3.4

func.loc <functional location>
CCMM254 No iPPE structure found for FID <FID- 8.5.3.7

Number> and class <class name/class type>
CCMM280 Structure gap can be deleted at funct.loc. 8.5.3.4

<functional location number>
CCMM505 Changes to equipment BOM will not be 9.5.2

considered in warehouse stock
CCMM506 Only equipment BOM with status AVLB can 9.5.2

be changed
Page 172 of 177

21 Table of figures
Figure 1 The world of Configuration Control .......................................................................................... 7
Figure 2 Structure of a technical device using technical objects functional locations and equipment .. 9
Figure 3 Overview Configuration Control................................................................................................ 9
Figure 4 Subassemblies at an aircraft.................................................................................................... 11
Figure 5 Operational tasks of a fighter aircraft ..................................................................................... 12
Figure 6 Aircraft models and types ....................................................................................................... 13
Figure 7 First example to model a MPL ................................................................................................. 16
Figure 8 Create characteristic via transaction CT04 .............................................................................. 18
Figure 9 Create variant class via transaction CL01 and assign characteristic ....................................... 19
Figure 10 Create configurable material via transaction MM01 ............................................................ 19
Figure 11 Assign the variant class via configuration profile to configurable material via transaction
CU41 ...................................................................................................................................................... 20
Figure 12 Create an access node inside the transaction PPE or PDN.................................................... 20
Figure 13 Access node, create an access variant .................................................................................. 21
Figure 14 Access node, access definition .............................................................................................. 21
Figure 15 Create and assign a structure node ....................................................................................... 23
Figure 16 The MPL defined by means of iPPE ...................................................................................... 23
Figure 17 Complete MPL for the example............................................................................................. 24
Figure 18 Inside the tab strip ‘Configuration data’ of the top equipment ............................................ 25
Figure 19 Create the assignment to the access node inside the tab strip ‘Configuration Control’ ...... 26
Figure 20 Equipment representing the fuel tank inside the technical object structure ....................... 28
Figure 21 Complete actual technical object structure for the aircraft 01............................................. 29
Figure 22 Start configuration check with transaction CCM2 ................................................................ 30
Figure 23 Result of the first check within transaction CCM2 ................................................................ 30
Figure 24 Multiple usage of one MPL.................................................................................................... 31
Figure 25 Three steps in the processing of Configuration Control Workbench .................................... 32
Figure 26 Interpretation of the equipment structure respecting the FID ............................................. 33
Figure 27 Parent FID and FID-grouping ................................................................................................. 33
Figure 28 Actual structure grouped by FID and Parent ......................................................................... 34
Figure 29 Structuring of the actual structure of aircraft 01 .................................................................. 36
Figure 30 Actual structure with functional locations ............................................................................ 38
Figure 31 Interpretation of the technical object structure respecting the FID, find parent FID ........... 39
Figure 32 Check results with functional locations within transaction CCM2 ........................................ 40
Figure 33 New functional location FLAC01 -CABIN -TR01SEAT; overview ......................................... 41
Figure 34 New functional location FLAC01 -CABIN -TR01SEAT; complete structure ......................... 41
Figure 35 Parent FID determination ...................................................................................................... 42
Figure 36 Result of check within transaction CCM2.............................................................................. 42
Figure 37 Determination of top equipment .......................................................................................... 43
Figure 38 Create a view node ................................................................................................................ 45
Figure 39 Determination of the parent node names ............................................................................ 46
Figure 40 Aircraft example with view nodes ......................................................................................... 48
Figure 41 New node type since EhP4 .................................................................................................... 50
Figure 42 Dismantling via IE4N .............................................................................................................. 53
Page 173 of 177

Figure 43 Configuration Control check with transaction CCM2 after dismantling of equipment
ESEAT04 ................................................................................................................................................. 54
Figure 44 Configuration Control check with transaction CCM2 after dismantling of equipment EFT01
............................................................................................................................................................... 55
Figure 45 Local Check of Configuration Control in IE4N ....................................................................... 56
Figure 46 Message by structure gap evaluation of IE4N ....................................................................... 57
Figure 47 Log of IE4N after installation performed ............................................................................... 58
Figure 48 Configuration Control check with transaction CCM2 after installing equipment ESEAT04 .. 58
Figure 49 Configuration Control check with transaction CCM2 after dismantling equipment ESEAT04
again ...................................................................................................................................................... 59
Figure 50 Delete a structure gap ........................................................................................................... 60
Figure 51 Install a part with a wrong material number ........................................................................ 61
Figure 52 Messages when forced installation took place ..................................................................... 62
Figure 53 Indicator for forced installation............................................................................................. 62
Figure 54 Log of transaction CCM2 ....................................................................................................... 63
Figure 55 Log of transaction CCM2 after dismantling of a wrong part ................................................. 64
Figure 56 Log of transaction IE4N after the try to install a part with a wrong FID ............................... 65
Figure 57 Adjusted FID .......................................................................................................................... 65
Figure 58 Log of transaction CCM2 after dismantling of a wrong part ................................................. 66
Figure 59 Define new BOM usage ......................................................................................................... 68
Figure 60 Define order of priority of BOM usage .................................................................................. 69
Figure 61 Define the application ........................................................................................................... 69
Figure 62 Activate cBOM usage for Configuration Control ................................................................... 70
Figure 63 Creation of cBOM for equipment ETR01 ............................................................................... 71
Figure 64 Actual structure with cBOM .................................................................................................. 72
Figure 65 Result of transaction CCM2 for the aircraft under functional location FLAC01 .................... 72
Figure 66 IE4N actions on cBOM ........................................................................................................... 74
Figure 67 Concept of object dependency ............................................................................................. 76
Figure 68 Additional variants for the structure node SN_FT, switch on object dependency to maintain
validity, step 1 and 2 ............................................................................................................................. 77
Figure 69 Popup: Dependencies Change: Step 3 .................................................................................. 77
Figure 70 Popup: Dependencies Change: Step 4 and 5......................................................................... 78
Figure 71 Popup: Dependencies Change: Step 6 .................................................................................. 78
Figure 72 Structure node SN_FT: Result with maintained object dependency .................................... 79
Figure 73 Configure top equipment, Configuration Data tab strip: Step 1 ........................................... 79
Figure 74 Configure top equipment, Characteristic value assignment: Step 2 ..................................... 80
Figure 75 Configure top equipment: Result of individual configuration............................................... 80
Figure 76 Result of the check with Configuration Control .................................................................... 81
Figure 77 Result of the check with Configuration Control with the wrong part ................................... 81
Figure 78 SERNR as Effectivity Parameter to be used as tail number ................................................... 86
Figure 79 Define effectivity type for tail number .................................................................................. 87
Figure 80 Define a change number, part 1 ............................................................................................ 88
Page 174 of 177

Figure 84 Assignment of the change number ....................................................................................... 90

Figure 85 Structure node SN_TR with two variants divided by change number. ................................. 91
Figure 86 Activate usage for parameter effectivity in material master ................................................ 92
Figure 87 Configurable material at the serial number tab strip of the equipment .............................. 92
Figure 88 Enter the tail number ............................................................................................................ 93
Figure 89 Result of check of Configuration Control .............................................................................. 94
Figure 90 Result of check of Configuration Control after the correction of the actual structure......... 94
Figure 91 Overview: Usage of coupled MPLs ........................................................................................ 97
Figure 92 MPL of the aircraft ................................................................................................................. 98
Figure 93 Actual structure of the short range aircraft with the tail number ACSR06t ......................... 99
Figure 94 Naming convention for the prefix of structure nodes ........................................................ 100
Figure 95 MPL of the engine ............................................................................................................... 101
Figure 96 Create material variant EN01 .............................................................................................. 102
Figure 97 Additional access variant in the MPL of the engine ............................................................ 103
Figure 98 Coupling via new structure node SN_ENGINE..................................................................... 103
Figure 99 Overview of coupled MPLs .................................................................................................. 104
Figure 100 Actual structure of the engines ......................................................................................... 106
Figure 101 Complete actual structure of the aircraft ......................................................................... 107
Figure 102 Buttons for load and check................................................................................................ 115
Figure 103 Complete check on aircraft level ....................................................................................... 115
Figure 104 Partial check for the aircraft only ...................................................................................... 116
Figure 105 Entry points for check........................................................................................................ 117
Figure 106 Complete check of the right engine .................................................................................. 117
Figure 107 FID grouping in UI .............................................................................................................. 118
Figure 108 FID group relevant checks in detail ................................................................................... 119
Figure 109 FID grouping of the actual structure for the individual objects ........................................ 120
Figure 110 Overview: How Configuration Control determines valid materials .................................. 121
Figure 111 Multiple usage of subordinate MPL .................................................................................. 122
Figure 112 Aircraft with asymmetric usage of the quantity of the parts inside the engines .............. 126
Figure 113 MPLs of the example ......................................................................................................... 127
Figure 114 Equipment structure of the example ................................................................................ 127
Figure 115 Result of the complete check of the aircraft ..................................................................... 128
Figure 116 Change customizing with transaction OMPL1................................................................... 131
Figure 117 Complete check of the aircraft after changing the customizing ....................................... 131
Figure 118 Dismantling EEN02-PART01-02 via IE4N ........................................................................... 132
Figure 119 Dismantling EEN02-PART01-02 via IE02 ............................................................................ 132
Figure 120 Integration into Configuration Control.............................................................................. 134
Figure 121 Manufacturer Part Profile ................................................................................................. 135
Figure 122 Form-Fit-Function-Class FFFC_EXAPL14_01 ...................................................................... 136
Figure 123 MPL of example ................................................................................................................. 136
Figure 124 Define materials for FFF class ............................................................................................ 137
Figure 125 Result of Configuration Control Check .............................................................................. 138
Figure 126 Small example for Set Relationship ................................................................................... 141
Figure 127 Activate Set Relationship for Configuration Control ......................................................... 142
Figure 128 Create a set combination .................................................................................................. 143
Page 175 of 177

Figure 129 Add set variants and structure nodes to the set combination.......................................... 143
Figure 130 Start to maintain the set variants...................................................................................... 144
Figure 131 Maintain set variant SV01 (Set Variant 01) – Part 1 .......................................................... 145
Figure 135 Result of the definition ...................................................................................................... 148
Figure 136 Result of Configuration Control Check .............................................................................. 149
Figure 137 Log of MPL explosion......................................................................................................... 150
Figure 138 Rule violation ..................................................................................................................... 151
Figure 139 Integration of Set Relationship functionalityRule violation .............................................. 153
Figure 140 Example 1 .......................................................................................................................... 154
Figure 141 Example 2 .......................................................................................................................... 156
Figure 142 Example 3 .......................................................................................................................... 158
Figure 143 Class AD_MPL_VARIANTS .................................................................................................. 159
Figure 144 Activate Cancel-Part Relationships by customizing........................................................... 160
Figure 145 Cancel-Part Relationships for structure node AIRCRAFT_00003 ...................................... 161
Figure 146 Cancel-Part Relationships for structure node AIRCRAFT_00003, set of rules................... 161
Figure 147 Cancel-Part Relationships for structure node AIRCRAFT_00003, adoption ...................... 162
Figure 148 Actual structure for Cancel-Part Relationships ................................................................. 162
Figure 149 Possible replacement for equipment 10000698 ............................................................... 163
Figure 150 Dismantle equipment 10000698 via transaction IE4N ...................................................... 164
Figure 151 Install equipment 10000700 via transaction IE4N ............................................................ 165
Figure 152 Install equipment 10000698 via transaction IE4N again ................................................... 165
Figure 153 Install equipment 10000701 via transaction IE4N ............................................................ 166
Page 176 of 177

Getting Started With Configuration Control

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Getting Started With Configuration Control

Transféré par

Droits d'auteur :

Formats disponibles

SAP

6.4.2 Rules on relations between different types of MPL nodes ........................................... 45

10 Object Dependency ................................................................................................................... 74

12.4.4 Final actual structure ................................................................................................... 106

16.2 Usage and modelling ........................................................................................................... 159

National product specifications may vary.

SAP Brand Tools: Airplane hangar, George Hammerstein, Corbis,

This documentation does not replace a consultant experienced in Configuration Control!

2 Prerequisites, boundary of the topics

Figure 1 The world of Configuration Control

 Specific chapters provide information on industry specific enhancements of Configuration

 It is recommended to use Configuration Control since EhP4.

3 What is Configuration Control about?

3.1 Technical objects

Supported actions are for example

3.2 Consistence check of the technical objects.

Figure 3 Overview Configuration Control

4 Before modeling, define your needs

Figure 4 Subassemblies at an aircraft

Figure 5 Operational tasks of a fighter aircraft

Figure 6 Aircraft models and types

 Create an MPL for each type of the model.

Usage of the material interchangeability functionality (e.g. via FFF-classes) .

Only available in the industry solution Aerospace & Defense.

Are there existing rules for the exchange order of parts?

Usage of the Cancel-Parts-Relationship approach.

Usage of the Set-Relationship approach.

Only available in the industry solution Aerospace & Defense.

See ‘Possible approach’.

5 Basic rules of modeling, the first example

5.2 iPPE, Integrated Product- and Process-Engineering

5.3 The example

Figure 7 First example to model a MPL

This aircraft must contain

 2 fuel tanks with the material number FT01

5.4 Access node and product class

Step Action Comment

This step is mandatory!

See Figure 10.

See Figure 11.

When you create the access node

This step is mandatory!

See Figure 12, Figure 13, Figure 14.

Figure 8 Create characteristic via transaction CT04

Figure 10 Create configurable material via transaction MM01

Figure 12 Create an access node inside the transaction PPE or PDN

Figure 13 Access node, create an access variant

Figure 14 Access node, access definition

5.5 Structure nodes, building up a structure inside the MPL

 goods issues in combination with installing actions of a part

Step Action Comment

How to assign a structure node to a superior node?

When you create the structure node

This step is mandatory!

For our example the materials

 FT01 (FUEL TANK 01, 5000L)

Figure 15 Create and assign a structure node

Figure 16 The MPL defined by means of iPPE

Figure 17 Complete MPL for the example

5.6 Building up the actual structure

5.6.2 Top equipment, hard link to the corresponding set of rules

 object dependency and

This equipment is not part of the check of Configuration Control!

Step Action Comment