Getting Started with Endeca LatitudeFull description
MATLAB
We are currently in a world of technology where everyone has a camera and wants to take photos of people or places. All of them want to enhance their photos and will eventually end up with Adobe Photoshop.
Ubuntu Manual
SAP
Getting Started With Configuration Control An introduction into Configuration Control not only for beginners
Prerequisites, boundary of the topics .................................................................. ............................................................................................. ........................... 7
3
What is Configuration Control about? ................................................................. ............................................................................................ ........................... 8 3.1
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..................................... 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
The example ............................................................... .......................................................................................................................... ........................................................... 35
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
General remarks ............................................................................................................ ............................................................................................................ 45 Page 1 of 177
Prerequisites, boundary of the topics .................................................................. ............................................................................................. ........................... 7
3
What is Configuration Control about? ................................................................. ............................................................................................ ........................... 8 3.1
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..................................... 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
The example ............................................................... .......................................................................................................................... ........................................................... 35
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
General remarks ............................................................................................................ ............................................................................................................ 45 Page 1 of 177
SAP
Getting Started With Configuration Control
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
General ................................................................................................. .......................................................................................................................... ......................... 51
General ................................................................................................. .......................................................................................................................... ......................... 53
8.4.2
Example .............................................................. ......................................................................................................................... ........................................................... 53
8.5
9
Dismantling equipment with IE4N ............................................................... ........................................................................................ ......................... 53
Installing equipment with IE4N ......................................................... ............................................................................................. .................................... 55
8.5.1
General ................................................................................................. .......................................................................................................................... ......................... 55
8.5.2
Local check and forced installation .................................................................... ............................................................................... ........... 55
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 quantity check....... 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 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 but a wrong FID .................... 64
8.5.3.7
Other important messages in the process ............................................................. ................................................................ ... 66
Usage of bill of material (BOM) ................................................................. ..................................................................................................... .................................... 67 9.1
General ............................................................ ............................................................................................................................... ...................................................................... ... 67
9.2
Customizing relevant for cBOM usage ......................................................... .................................................................................. ......................... 68
cBOM and the MPL................................................................. ................................................................................................................ ............................................... 70
9.5
Usage of the cBOM in actual structure ...................................................................... ................................................................................. ........... 70
9.5.1
How to create c reate 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
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
Only Configuration Control needs configuration Information of the serialized
equipment 84 10.6 11
FID-Grouping and configuration of top equipment .............................................................. 84 Parameter Effectivity of Engineering Change Management (ECM) .......................................... 85
Title image: SAP Brand Tools: Airplane hangar, George Hammerstein, Corbis, http://imagedirectory.wdf.sap.corp:6085/ImageLibrary/ImageDetailsView?imageId=1816e7bb-18814fab-be27-1ee0318d70e7
Page 6 of 177
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
3
It is recommended to use Configuration Control since EhP4.
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 technica l 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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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). th
The development of Configuration Control was once triggered in the 1990 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 t he 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
SAP
Getting Started With Configuration Control
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 o r 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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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. Dif ferent 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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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 f uel 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
SAP
5
Getting Started With Configuration Control
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 tec hnical 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 Configuratio n 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
SAP
Getting Started With Configuration Control
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 classification functionality Transaction CT04
The characteristics might be used later on for the purpose of object dependency. In our example you might use them to characterize the 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 n eed to distinguish between different types, you do not need to create characteristics.
2
Create a class with the class type 300 (Variants) and assign the characteristics of step 1 (when available) . Transaction CL01
See Figure 8. This class have to be used later on In the assignment of the configuration profile of the configurable material (Step 3) As product class inside the access node definition (Step 4) This step is mandatory!
3
Create a configurable material Transaction MM01
See Figure 9. This configurable material is used later on as formal access variant inside the access node as carrier inside an equipment to link an actual technical object structure to a MPL o o to provide the MPL explosion with information about the current shape (e.g. about the current aircraft type) via variant configuration This step is mandatory!
4
Add configuration profile for the material just created Transaction CU41
See Figure 10. Assign the variant class created with step 2 to the material created with step 3. This step is mandatory!
Page 17 of 177
SAP
5
Getting Started With Configuration Control
Create the access node Transaction PPE (usage of A&D industry solution) or PDN (usage of enterprise extension)
See Figure 11. Within this step you have to provide the access node with a valid access node name. The node name has to be unique within the same client and used product class! the product class from step 2 the access node variant using t he configurable material created with step 3: Keep in mind that the used product class of the access o 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 This step is mandatory! 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
SAP
Getting Started With Configuration Control
Figure 9 Create variant class via transaction CL01 and assign characteristic
Figure 10 Create configurable material via transaction MM01
Page 19 of 177
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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 be part of the validation via Configuration Control Transaction MM01 to create a material Customizing transaction OIS2 for the serial number profile Create the structure node PPE Transaction (usage of A&D industry solution) or (usage of PDN enterprise extension)
The materials to be created must contain a serial number profile to enable the serialization procedure at least for material management actions like goods receipt and issue. The material must not be a configurable material!
2
Do not forget to maintain general plant data, sales- and distribution-data and accounting data (E.g. for the processing with transaction IE4N) This step is mandatory! Within this step you have provide the structure node with a valid node name. The node name has to be unique within the same client and used product class! the same product class and class type as the access node created before. 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: The same material can be used in structure node o 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 o Choose o Enter the structure node data When you create the structure node choose ‘Product structure’ (CMP) as application choose ‘Product Variant Structure‘ as iPPE object type choose ‘Structure Node’ (S_ST) as node type This step is mandatory!
Table 2 How to create a structure node
Page 22 of 177
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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 – 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
SAP
Getting Started With Configuration Control
Step
Action
Comment
1
Create an equipment which should be the link to the corresponding MPL. Transaction IE01 create the equipment Transaction IE02 to change the equipment
A view should be used where the following tab strips for the equipment transactions are visible: Configuration Data Configuration Control SerData (for material and serial number) Within the tab strip ‘Configura ‘Configuration Data’, 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. and 5.5. This This formal step is absolutely essential to link the actual structure to the MPL! ‘Configuration Control’, 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 – link – the 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 ‘Configura ‘Configuration Data’, Data’, you must manually delete the assignment to the access node and to reassign it to an access node that fits! See Figure See Figure 18 to Figure to Figure 19. This step is mandatory!
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
1
Create an equipment which should be relevant for the checks of Configuration Control. Transaction IE01 create the equipment Transaction IE02 to change the equipment
A view should be used where the following tab strips for the equipment transactions are visible: Configuration Data Configuration Control SerData (for material and serial number) Within the tab strip ‘Configuration Control’, you perform the linkage to the 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.
This step is mandatory! Table 4 How to create an equipment that is relevant for the check.
Page 27 of 177
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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 S EAT01
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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. 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 and Figure 28! The result for the check of this actual structure (see Figure (see Figure 30) with 30) with Configuration Control does not differ to Figure to Figure 23 (see Figure (see Figure 32). 32).
Page 39 of 177
SAP
Getting Started With Configuration Control
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 Within Figure 35 the result of the parent FID determination by the method introduced in Figure in Figure 31 is shown. For the equipment ESEAT01, ESEAT02, ESEAT03 and ESEAT04 the parent FID is now EAC0101. 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 c heck. 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.
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
SAP
Getting Started With Configuration Control
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
SAP
Example
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
6.4 View nodes 6.4.1 General remarks 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
SAP
Getting Started With Configuration Control
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
SAP
Example
Getting Started With Configuration Control
Modeled MPL
Extracted MPL relevant for check
1
2
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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
SAP
Getting Started With Configuration Control
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 o r 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
SAP
Getting Started With Configuration Control
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
