SCM740

SCM740
SAP ERP Integration with SAP

Manufacturing Execution
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 01
Course Duration: 2 Day(s)
e-book Duration: 8 Hours
Material Number: 50155245
SAP Copyrights, Trademarks and
Disclaimers
© 2020 SAP SE or an SAP affiliate company. All rights reserved.

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

Typographic Conventions
American English is the standard used in this handbook.

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

Contents
vi Course Overview
1 Unit 1: Master Data Setup for Production in SAP Manufacturing

Execution
2 Lesson: Working With Work Centers and Resources in SAP

7 Lesson: Setting up Production Lines
15 Lesson: Working With Materials in SAP Manufacturing Execution
19 Lesson: Working With Bills of Material in SAP Manufacturing
Execution
32 Unit 2: Master Data Integration
33 Lesson: Configuring Material Master Integration

41 Lesson: Configuring Bill of Material Integration
47 Lesson: Configuring Work Center Integration
55 Lesson: Configuring Routing Integration
80 Unit 3: Production Order Transactional Data Integration
81 Lesson: Configuring Production Order Integration

90 Lesson: Configuring Floor Stock Integration
98 Lesson: Configuring Production Order Confirmations
© Copyright. All rights reserved. v

Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
Systems Architect
Application Consultant
Development Consultant
Super / Key / Power User
© Copyright. All rights reserved. vi

UNIT 1 Master Data Setup for
Production in SAP
Manufacturing
Execution
Lesson 1
Working With Work Centers and Resources in SAP Manufacturing Execution 2
Lesson 2
Setting up Production Lines 7
Lesson 3
Working With Materials in SAP Manufacturing Execution 15
Lesson 4
Working With Bills of Material in SAP Manufacturing Execution 19
UNIT OBJECTIVES
Understand the difference and relationship between work centers and resources
Understand the purpose of using work centers
Understand the purpose of using resources
Understand the relationship between work centers and resources and the possibility to
nest them
Understand the purpose and settings of operations
Understand the purpose and settings of routings
Understand the usage of in-line work instructions
Explain the purpose of using materials and its settings
Explain the purpose of using a bill of material (BOM) and explain its structure
© Copyright. All rights reserved. 1

Unit 1
Lesson 1
Working With Work Centers and Resources in
SAP Manufacturing Execution
LESSON OBJECTIVES
After completing this lesson, you will be able to:
nest them
Work Center and Resource Overview
Figure 1: Work Centers and Resources in SAP Manufacturing Execution
In SAP Manufacturing Execution, a work center is defined as a specific location in the site
where goods are produced, processed, or stored. Work centers are used to divide the
portions of a routing along functional work lines, and therefore, a work center corresponds to
a sequence of resources required to produce or assemble a material. In SAP Manufacturing
Execution, work centers are mainly used for the following purposes:
Determination of the granularity of the work in progress (WIP) reports
To group together different equipments that are system-wise managed as resources, for
example, several identical drills are available at the same workbench
To control where a product is released

Lesson: Working With Work Centers and Resources in SAP Manufacturing Execution
To determine the order of resources that SFCs should follow in the work center, for
example, 1) drill holes using a drill, 2) thread using a thread cutter, 3) mount screws with a
screw driver
A resource is defined as a machine or other piece of equipment used to perform an operation.

A resource may be very simple (for example, a drill, a thread cutter, a screw driver), or a
complex machine (for example, a painting robot or an automated assembly machine for
manufacturing electronic circuits). A resource can also represent a workbench or a basic
processing area where operations are performed without using equipment, such as a staging
area where individual components for the different production orders are staged.
Work Centers
Figure 2: Work Centers in SAP Manufacturing Execution
As already stated, a work center is defined as a specific location in the site where goods are
produced, processed, or stored. Possible settings for the work center are shown in the figure.
On header level, the work center is defined per site and characterized by a main key for
example, ASSY-BENCH-00. On the Main tab, the user can maintain a language-specific
description, the work center status (such as enabled or disabled), the work center type (for
example, assembly, dispatch, production control, and so on), and ERP-related data.
When a shop order is released, the system places the SFC(s) in queue at the first operation on
the routing in the default work center, which is maintained in the routing step. This setting can
be overwritten in Shop Order Maintenance and/or Shop Order Release apps, for example, by
supervisors in order to balance the workload between different work centers. In order to be
able to release SFCs to individual work centers, such as production lines, the indicator SFC
can be released to this Work Center must be set for this work center.
On the Users tab, several users that are working at this work center can be assigned. If a work
center POD is used by the production operators, the user must be assigned to this work
center in order to be able to enter the work center in the POD. If the user is not assigned, the
work center will not be visible to this user, although it exists in the system.
In addition, it is possible to set up a hierarchical structure of work centers and resources in
order to sequence resources within a work center. In this case, the header work center, for
example a production line, can contain several nested sub-work centers and/or resources. In
the case of a production line, the nested items perform the individual steps and the system
enforces that the steps are executed exactly in the specified sequence, using the assigned
resources. If different production lines are available on your shop floor, the system will route

Unit 1: Master Data Setup for Production in SAP Manufacturing Execution
the SFCs through the production line in the specified sequence. In this case, the header work
center can also be interpreted as a routing.
In SAP Manufacturing Execution, work centers are set up using the Work Center Maintenance
activity.
Resources
Figure 3: Resources in SAP Manufacturing Execution
As already stated, a resource is a machine or piece of equipment that performs work at an

operation in order to manufacture a product. Similar to work centers, the resource
information is also distributed between tabs. On header level, the resource is defined on site
level and characterized by a main key, for example, DRILL-00. On the Main tab, the user can
maintain the description, the status, (for example, enabled, disabled, scheduled
downtime,and so on), and ERP data if the resource is imported from ERP.
Resources can be assigned to different resource types. Resource types are used to categorize
similar machines or other resources into groups, such as drills, as indicated above. The
resource type determines which resource is available for the shop floor worker when starting
an operation in the POD as the resource type must be maintained when setting up an
operation. As an example, let's assume that the first manufacturing step consists of drilling
holes. On the operation level, the resource type drills is assigned. If an operator starts the
drilling step, the system offers all drills assigned to the resource type drill for selection. Note
that there is a m:n relationship between resources and resource types, so that a resource can
be assigned to more than one resource type.
Usually, one resource is only used by one operator, and the same operator starts and stops
working on an SFC with this resource. However, there might be production setups where one
operator of one shift starts the SFC at a resource and another operator who is assigned to a
later shift finishes the SFC at this resource (for example, an oven in which components are
heated over several hours). In this case, the process resource indicator must be set and it is
then possible that the same SFC is started and stopped by different operators at the same
resource. Note that this setting is also important when performing in-process quality
inspections with ERP. If a passed quality inspection will move the SFC from one to the
adjacent step and the valuation of the quality inspection is performed by ERP, the process
resource indicator must be enabled for the quality inspection resource.

Lesson: Working With Work Centers and Resources in SAP Manufacturing Execution
If it is required to track the productive time of each resource, for example, for calculating a
productive utilization, the corresponding system rule must be enabled. Note that enabling this
setting might negatively impact your system performance.
In SAP Manufacturing Execution, resources are maintained in the Resource Maintenance app,
whereas resource types are managed in the Resource Type Maintenance app.
Use Cases for Nesting and Sequencing
Figure 4: Nesting Work Centers and Resources
The figure, Nesting Work Centers and Resources, shows a commonly used approach with
several nested work centers and their various categories. WC1 corresponds to the building
where the pumps are assembled. Pump manufacturing takes place in two separate, but
identical assembly lines, WC3 and WC6. Due to reporting reasons, the identical lines WC3 and
WC6 are grouped to a line group WC2.
The smallest boxes in the figure represent resources that execute the individual assembly
steps. Some resources are also work centers. For example, WC8 / WC10 could correspond to
a work center that contains only a single resource, such as a painting robot.
WC3 and WC6 are Line category work centers. Each of these work centers categorizes an
entire routing. These routings have identical routing steps (operations), but each of the two
corresponding steps will be executed on a different resource. For example, if the first step on
routing 1 is ASSEMBLY-00, the first step on routing 2 is also ASSEMBLY-00. However, the
operator on routing 1 enters BENCH-01 (located at work center WC7) as the resource in the
Production Operator Dashboard, while the operator on routing 2 enters BENCH-02 (located
at work center WC9). This approach allows you to track information, for example, usage time
for calculating the utilization, about each resource separately.
The SFCs Can Be Released to This Work Centercheckbox in Work Center
Maintenance controls where users can release SFC numbers. In the example, this checkbox is
selected for WC3 and WC6 only. All other work centers are used for reporting purposes.

Figure 5: Sequencing Resources Within a Work Center
It is possible to set up a hierarchical structure of work centers and resources in order to

sequence resources within a work center. As shown in the figure, Sequencing Resources
Within a Work Center, the work center ASSY-BENCH-00 has three resources (R-DRILL-00, R-
SCREWDRIVER-00, and R-CALIPER-00) assigned. If the system rule Queue SFC at a resource
is set to true, a user can start the first operation (for example, drill) of a production routing at
resource R-DRILL-00. If the first operation is completed, the system will put the SFC in queue
at the second operation (for example, apply screws) and resource R-SCREWDRIVER-00 as
this resource is the next resource in the sequence. The third operation (quality inspection)
must also be completed inside work center ASSY-BENCH-00 by resource R-CALIPER-00. It is
not possible to move the pump SFC 4711 to the second work center ASSY-BENCH-01 and
finalize the assembly with resource R-CALIPER-01.
LESSON SUMMARY
You should now be able to:
nest them

Unit 1
Lesson 2
Setting up Production Lines
LESSON OBJECTIVES
Operations
Figure 6: Properties of Production Operations
Operations are defined as individual, basic steps that are required to manufacture a product.
Before you create routings, you must define operations that will serve as building blocks for
routings. Each operation is started and completed by production operators or machines on
the shop floor. As usual, operation details are maintained on several tabs as indicated in the
figure. On header level, the operation key and the site where the operation is valid are defined.
On the Main tab, the description, the status (for example, new, releasable, obsolete), and the
operation type (normal, test, special), are defined. In addition, information about the default
resource type or even a specific default resource can be entered. If only the default resource
type is maintained, the operator can choose from the list of available resources that belong to
this resource type, if an SFC is started for a specific operation. If the default resource is given,
the SFC will be started at this resource. For example, if the resource type of
the ASSEMBLY-00 operation is RT-BENCH-00, and the RT-BENCH-00 resource type
includes BENCH1-00, BENCH2-00, and BENCH3-00, an operator who
enters ASSEMBLY-00 as the operation in the PODs can enter BENCH1-00, BENCH2-00,

or BENCH3-00 as the resource. Furthermore, ERP-related data is displayed if the operation

was replicated from an ERP routing.
Operations of the type normal are usually required for manufacturing purposes. Test
operations are used to perform quality inspections. Operations belonging to both types are
usually added to production routings and it is possible to queue and release SFCs to these
operations. In addition, operations of the type special can be defined. These operations
cannot be used in standard manufacturing routings, but require the use of the routing type
special. A special operation is an operation that allows an operator to pull SFCs from another
arbitrary routing/operation to this operation and start the SFC here, for example, in order to
execute a random quality inspection. In order to be able to pull SFCs from another routing to
the special operation, the special operation must be the first step in the respective routing.
On the Certifications tab, the required certification and user group can be assigned to this
operation, in order to ensure that only trained and qualified personnel are able to execute this
manufacturing operation.
On the Activity Hooks tab, activities can be assigned to hook points (for example, pre_start,
post_start, pre_complete, post_complete, and so on), in order to execute automated checks,
for example, before an operation is completed. In the example above, the activities CT520
(Check Configuration) and NC520 (Check SFC for open NC codes) are performed before the
operation is completed. The first operation checks whether all components specified in the
BOM have been assembled. The second operation checks whether open defect codes (NC
codes) exist. If not all of the components have been assembled, or open NC codes exist, the
operation cannot be completed and an error message is displayed.
In SAP Manufacturing Execution, operations are defined in the Operation Maintenance
activity.
Figure 7: Example: Setting up an Routing by Leveraging Operation Building Blocks
As shown in the figure, when setting up a routing, one or more operation building blocks are
put together into the routing and brought into the sequence that is required in order to
execute the manufacturing process. As operations are building blocks, it is possible to reuse
one operation in multiple routings. For the second step, special instructions that describe the
quality inspection process in detail are supplied and displayed to the operator.
As indicated for the first operation, an elapsed time check is performed before the operation
is finished by assigning the ELAPSED_TIManufacturing Execution_CHECK activity to the hook
point PRE_COMPLETE. When the operator tries to complete the SFC at the first operation,
the system checks whether the required time, which is maintained on operation level, has
passed. If this is not the case, the operator cannot complete the SFC and must wait until (at

Lesson: Setting up Production Lines
least) the required time has passed. A business example could be a painting operation where
a certain waiting time is required so that the paint is dry enough for the execution of the
subsequent manufacturing steps.
In addition, the QUAL-INSP-00 operation might be set up to enable the recording of
nonconformances. On the Main tab, it is also possible to assign a nonconformance client to
this operation which will be displayed in the POD. The operator can then log one or more
noconformance codes for the SFC at this operation.
Routings
Figure 8: Properties of Routings
In SAP Manufacturing Execution, a routing is defined as a set of work steps that are required
to execute the production of a good. The routing contains the relevant operations, their
sequence, and the work centers at which the operations will be executed. The routing data is
organized into different tabs. On the Main tab, the routing description, the status, and the
maintenance mode (tabular or graphical) are maintained. The latter setting determines the
content of the second tab. If tabular maintenance mode is chosen, the user can maintain the
routing in a tabular mode where the different operations and their respective settings are
maintained in a table. If graphical maintenance mode is chosen, the user can graphically
maintain the operations in the routing and their sequence. On the left side of the graphical
routing window, the repository of available operations displays, and the user can add
operations via drag-and-drop to the routing. By drawing arrows from one step to another, the
operation sequence is determined.
The routing type determines the flow of an SFC through the production process. Production
routings are used to manufacture a product. Nonconformance (NC) routings are used to
analyze and resolve a nonconformance. These routing types are not used when an order is
released to production. Instead, NC routings are usually connected to NC codes and triggered
if an operator detects an NC, for example, when performing a quality inspection operation.
Routings of the type special are used for special processes. It is possible to directly move an
SFC to a special routing, for example, for an unscheduled, ad-hoc quality inspection.
The example in the figure shows a very simple routing flow consisting of three steps
(assembly, quality inspection, and packaging). The first step (ASSEMBLY-00) is marked as
entry step so that the SFC can be released at order release to the first operation of the
routing. On the shop floor, the operator performing the assembly step opens the POD, selects
operation ASSEMBLY-00 and the used resource, and starts the SFC at this operation. When

finished, the operator completes the SFC and the system routes the SFC to the quality
inspection step (QUAL-INSP-00). After start and complete, the SFC is routed to the
packaging (PACKAGING-00) step. After the operator finishes the SFC here, the SFC is
produced and the respective SFC status is done.
In SAP Manufacturing Execution, routings are maintained using the Routing Maintenance app.
Note that this activity starts a Java application. Therefore, it is not possible any more to
execute this app if this is not supported by your browser (for example, Google Chrome). As of
now, the app can still be used in Internet Explorer. Alternatively, a stand-alone package can be
deployed to PC users, (see SAP note 2814817), so that the routing maintenance can be
started locally. The same applies to Dynamic Routing Maintenance .
Routings with Branches, Repair Loops, and Dependent Steps
Figure 9: Graphical Routing With Repair Loop
In the figure, Graphical Routing With Repair Loop, a more complex routing including an
additional repair step is displayed. Similar to the previous example, the manufacturing
process consists of three steps (assembly, quality inspection, and packaging). After the
quality inspection, a branching point (1) is introduced. If the operator detects failures during
the quality inspection step, an additional repair step (REPAIR-00) is required, where the
broken device may be repaired. After repair, the device is routed back to the quality
inspection step where the quality inspection is re-executed. If the operator does not detect
any failures, the device is routed to the packaging step. Note that the repair branch is not
limited to one step. It is possible to add an arbitrary number of additional steps (such as
disassembly, repair, and so on) to the rework branch.
At the branching point (1), a decision about the SFCs next step is required. The decision can
be taken by the operator, automated using a script, or by using a nonconformance code. The
decision can be made by the operator performing the current step or by the operator(s)
performing the next steps. In the first case, the system displays a popup and the completing
operator can select. In the second case, the SFC is put in queue at all possible follow-up steps
and the first operator starting the SFC at their step wins. If the decision is automated, it is
possible to define a script at the branching point or use a nonconformance code disposition.
The script could check whether there are defects or open nonconformances, for example. In
the case of a defect, the SFC is automatically routed to the repair step. If there are no defects,
the SFC is processed at the packaging step. Based on the entered nonconformance code,
special analysis and repair routings could be required. It is therefore possible to assign
routings of the NC Routing type to defect codes. If the operator logs the defect code, the
system can automatically route the SFC to the assigned routing.

Figure 10: Graphical Routing With Branches
The figure, Graphical Routing With Branches, shows a routing flow containing three alternate
steps. After assembly, the painting operation can be executed manually (PAINT-00), or with
two different painting robots (PAINT-01/02). If the system completes the first step, the
branching point (1) is reached and the system displays a popup, where the operator can
choose the subsequent step. For example, the operator could select an operation with free
capacity in order to balance work between the three available possibilities. Note that after
choosing one next step, the SFC can only be started at this step. It is not possible to start the
SFC at one of the other two steps.
Figure 11: Graphical Routing With Dependent Steps
The figure, Graphical Routing With Dependent Steps, shows two alternative routing options
leveraging the any order and the simultaneous group settings. All operations in the any order
group (on the left side of the figure) can be executed in an arbitrary order. However, it is not
possible to execute these operations simultaneously. After completing the assembly
operation (ASSEMBLY-00), the SFC is put in the queue at all operations in the any order
group. If the operator starts the SFC, for example, at the DRILL-00 operation, the SFC are
dequeued from all other operations in the any order group. After the SFC is finished at the
DRILL-00 operation, the SFC is again put in the queue of all operations in the any order group.
The system continues this until all operations of the any order group are completed. Then, the
SFC is put in the queue of the packaging operation (PACKAGING-00).

The simultaneous group (on the right side of the figure) is used for operations that can be
executed in parallel (for example, different quality inspection) for the same SFC. After
completion of the assembly operation (ASSEMBLY-00), the system puts the SFC in the
queue of both operations included in the simultaneous group (BEND-00 and DRILL-00). The
SFC can be started at the different operations at the same time. After the SFC is finished at
both operations, the system routes the SFC to the packaging operation (PACKAGING-00).
Note that it is also possible to define more complex flows, such as more than one subsequent
step, in the simultaneous group.
Nested Routing Types
Figure 12: Nesting Different Routing Types
The figure shows a very complex work flow with tree nested routings. The default production
routing (orange box) consists of three steps (assembly, quality inspection, and packaging). If
there are errors identified in the quality inspection step (1), the SFC is routed to the defect
routing (blue box). This routing is of the NC type. Here, a different operator analyzes the
product and executes a repair. In case of successful repair (2), the product is routed back (3)
to the original step in the default production routing and the production continues.
Alternatively, the product can also be routed to the next operation in the production chain. In
the example in the figure, this would correspond to the packaging operation
(PACKAGING-00).
If the operator cannot identify the defect, another operator with more specialized analysis
equipment might be involved (4). In this case, the product can be routed to a third routing of
type special (purple box). Here, additional analysis and repair steps may be executed.
Depending on the outcome, this operator can decide to scrap (5) the SFC or return (6) the
SFC to the next step in order to continue the production process. Note that since the third
routing is of type special routing, the return step does not route the SFC back to the previous
step in the chain ( defect routing), but transfers the SFC back to the routing which initiated
the deviation process flow ( default production routing).

In-Line Work Instructions
Figure 13: Types of Work Instructions and Assignment to Objects
A work instructionis an explanation of what to do in a particular production circumstance. As

shown in the figure, work instructions can be files of various file types that are uploaded to the
system, or links to external storage systems. The documents are attached to material groups,
materials, routings, operations, work centers, resource types, resources, individual shop
orders, or even SFCs. If multiple attachments are defined at a single point, the sequence by
which the system processes these work instructions must be specified.
If the operator executes a production step where a document is attached using one of the
attachment points stated above, the document can be displayed either manually or
automatically. The operator can review the detailed instructions and then execute the work as
specified.
Work Instruction Viewer (WI500)
The Work Instruction Viewer activity is attached to a POD button and launches work
instructions to the production operator based upon the POD configuration. The administrator
can configure the POD to display work instructions in the following ways:
Add a standalone button to the POD, specifically designed to run the Work Instruction
Viewer activity.
Add the Work Instruction Viewer activity to an existing POD button, such as Start or
Complete , to launch the Work Instruction Viewer when the operation is started or
completed by the operator against an SFC.
A primary POD button must be associated with the Work Instruction List plug-in or the Work
Instruction Viewer plug-in. The Work Instruction List plug-in (WI_LIST_DISPLAY) displays a
list of all of the work instructions that are associated with the SAP Manufacturing Execution
objects currently in effect in the POD. It also contains a View button that invokes the Work
Instruction Viewer plug-in for the selected work instructions.
In SAP Manufacturing Execution, work instructions and their attachment points are
maintained in the Work Instruction Maintenance activity.
LESSON SUMMARY


Unit 1
Lesson 3
Working With Materials in SAP Manufacturing
Execution
LESSON OBJECTIVES
Materials Overview
Figure 14: Materials in SAP Manufacturing Execution
A material in SAP Manufacturing Execution is defined as a unique manufactured or purchased

part that is processed or consumed on the shop floor. As all master data, it is defined on site
level. As indicated in the figure, the material data is organized on different tabs. On the Main
tab, the most important data is displayed, such as the language dependent description, the
status, and the material type.
Materials in SAP Manufacturing Execution can be of different types. Manufactured materials
are produced on the shop floor. If a component is manufactured or purchased from suppliers,
the type Manufactured/Purchased can be chosen. For purchased components that are not
manufactured, the type Purchased is available. It is possible to create production orders for
materials of the type Manufactured or Manufactured/Purchased. On the contrary, it is not
possible to create production orders for materials of the type Purchased. In addition to the
material type, the default routing and BOM can be specified on material level per order type. If
no other information is supplied (for example, by transferring order specific information from
ERP or by specifying different information in the shop order or at shop order release), the
default BOM and routing are used when the shop order is released.

The lot size setting, in combination with the quantity restriction, controls the received (in case
of purchased) or manufactured quantity. The lot size defines whether the material on the
shop floor is managed as a separate unit (lot size 1) or whether individual units are grouped
together as a lot (lot size > 1). The setting applies both to manufactured and purchased
materials. In the case of manufactured materials, the lot size determines how many SFCs will
be created at release of a shop order. Assuming a lot size of 10 pc and a manufacturing
quantity of 30 pc, three SFCs managing 10 pc, respectively, will be created. In case of
purchased materials, the lot size is taken into consideration during floor stock receipt and
determines how many pieces are managed by one floor stock unit.
The quantity restriction (only 1.0, any number, or whole number) influences the lot size. If
quantity restriction is set to only 1.0, the lot size must be 1 as well. This usually corresponds to
serialized materials that are individually built and managed through the entire production
process. If quantity restriction is set to whole number, the lot size can only be an integer. If
quantity restriction is set to any number, the lot size can be an arbitrary, also floating point
number. The latter two cases correspond to a situation where SAP Manufacturing Execution
cannot track individual pieces. Instead, multiple items are managed in the same SFC as a
homogenous quantity.
On the Build tab, it is possible to define data to be collected during assembly and floor stock
receipt, for example, for traceability purposes. A potential business scenario could be the
assembly of a serialized component into a serialized finished good, such as a medical device.
Another scenario corresponds to the situation where components bearing a supplier serial
number are purchased.
The ERP production storage location and ERP putaway storage location fields are taken into
consideration when SAP Manufacturing Execution is connected to SAP ERP and material
movements are posted. The first field determines the default storage location for
components, whereas the latter field determines where the finished goods will be stored.
On the Alternate Materials tab, it is possible to define alternate components that can be
assembled instead, for example, if this material is not available. A similar setting can also be
made on BOM level for each BOM item. If the setting is made on material level, the alternate
component applies to all BOM items that reference this material. If the alternative component
setting is made on BOM item level, the alternate component only applies to the BOM item.
On the Documents tab, it is possible to assign documents, such as drawings, labels, and so on,
to the material containing additional information. Documents must be set up in the Document
Maintenance activity.
On the Certifications tab, certifications can be assigned to the material. The certification
process ensures that only trained and certified personnel are able to perform specific jobs or
tasks for a material and the system prevents users without the certification to work with this
material.
On the Material Groups tab, the material can be assigned to one or more material group(s) in
order to logically group similar materials. For example, it is useful to define material groups if
similar manufactured materials will have the same SFC numbering scheme, as the numbering
scheme can be defined either on material or on material group level.
In the system, material master settings are performed with the Material Maintenance activity.
Material groups are defined and managed in the Material Group Maintenance activity.

Lesson: Working With Materials in SAP Manufacturing Execution
Figure 15: Additional Settings in the Material Master
The quantity multiplier and panel settings mainly apply to electronic circuits. The quantity
multiplier represents the planned number of pieces of a material that will be produced. As
shown in the figure, eight units (A-H) of a material will be produced. However, due to handling
purposes, the eight individual units are grouped together at the beginning of the
manufacturing process. At a certain step, the eight units are cut into individual pieces and the
SFCs quantity is multiplied by the quantity multiplier. Multiplication can occur either manually
by the operator in the POD, or by assigning the hook point activity PR597 to the cutting
operation.
If the indicator panel is set, the system assumes that more than one piece will be produced
from the same material. For each piece, a location identifier (A-H in the figure) can be defined
and the amount of available locations depends on the materials lot size. At a predefined
operation, the panel is cut into individual pieces and the SFC is split up into individual SFCs by
executing the Serialize activity (PR550). After serialization, the old SFC number is invalid with
zero quantity and new SFCs are created with a respective quantity. This process allows the
operator to scrap individual slots in case of defects even before the SFC is serialized.
Time-sensitive materials are materials where the chemical and physical properties change
over time, such as paint, glue, or other materials that are sensitive to moisture and/or oxygen.
As these materials deteriorate under ambient conditions, the system must make sure that
they cannot be consumed after a certain time. Using the time-sensitive materials
functionality, shop floor operators can be notified that materials have expired during the work
process. Once the respective checkbox is selected, it is possible to maintain the shelf life and
the floor life times, respectively. The shelf life time is the time a material can be stored under
controlled conditions, for example, in a fridge. The floor life time corresponds to the time a
material can stay in good order on the shop floor under ambient conditions. The system
counts both times and informs the operator if, for example, the maximum shelf life has been
reached. Note that the floor life time is not accumulated over multiple usages. Each time the
operator checks a time-sensitive material out, the system resets the floor life clock. The shelf
life clock however keeps running. In order to use the time-sensitive materials functionality, the
POD plug-in Time-Sensitive Material Check In/Out must be configured in the POD.

Selection of Routing and BOM at Order Release for Different Order Types
Figure 16: Selection of Routing and BOM at Order Release for Different Order Types
On the material level, default settings for routing and BOM can be defined for different order
types, for example, standard production order, inspection order, or rework order. Upon
release of the specific shop order, default BOM and routing are assigned, provided they have
not been received via the production order download from ERP, or manually entered in the
shop order through the Manage Shop Order or Release Shop Order apps, respectively.
Potential business scenarios include the following: Your company manufactures a finished
good in a make-to-stock scenario. As the production process is well defined, it is possible to
assign a default routing and BOM on material level so that all production orders, independent
of the lot size, are executed in the same way. In a rework scenario, defect goods can be
reworked in order to be able to sell them. In this case, no BOM might be required as all
components have already been assembled. However, a special inspection or repair routing
(for example, REWORK-T-F100, as shown in the figure) must be executed in order to analyze,
identify, and resolve the defect. Inspection orders are mainly used if incoming inspections, for
raw materials for example, will be performed on the shop floor. The BOM could contain
measuring devices for analyzing the raw materials quality and the inspection routing could
define the quality inspection process.
LESSON SUMMARY

Unit 1
Lesson 4
Working With Bills of Material in SAP
LESSON OBJECTIVES
BOM Overview - BOM Header and BOM Items
Figure 17: Bill of Materials (BOM) for Production
A bill of material (BOM) is defined as a structured list of all the components, and their
quantities that make up an assembly. The BOM consists of the header and the item level.
On the header level of a BOM, the BOM type (master, shop order SFC, or configurable) is
maintained. The key fields are the BOM ID and the version, for example, T-F100-1-1 / A. If the
BOM is imported from ERP, the ERP key field is displayed. Finally, a BOM has a text
description and a status that indicates whether a BOM is still in draft mode (status new) or
can be used in a production process (releasable).
The BOM type indicates for which scenario the BOM can be used. A master BOM is the default
type that is used when manufacturing a product. A shop order BOM is usually created when
BOMs are imported from SAP ERP. If the master BOM is different from the BOM that is sent
together with the ERP order, shop-order specific BOMs are created (if the system rule "Ignore
BOM Update" is set to false). Finally, it is possible to have SFC-specific BOMs if a certain SFC
requires the assembly of specific components that differ from the master or shop-order BOM.
When trying to identify which BOM to use, the SFC BOM takes precedence over the shop-
order BOM, and the latter takes precedence over the master BOM.
On the item level of a BOM, the individual components, their respective assembly sequence,
the assembly quantity, and the assembly operation are maintained. The item quantity

corresponds to the quantity that is required to produce one manufactured product. In the
example shown in the figure, the pump consists of one casing, one fly wheel, one hollow shaft,
one electrical turbodrive and eight screws, respectively. Note that, in contrast to ERP, the
BOM in SAP Manufacturing Execution is always normalized to one piece of the manufactured
product.
In SAP Manufacturing Execution, BOMs are maintained in the BOM Maintenance activity. In
BOM maintenance, you create, update, display, or change BOMs.
Figure 18: Additional Settings on BOM Item Level
In addition to the previous section, it is possible to make additional settings for each BOM
item.
The component type further identifies a component. The default type (normal) corresponds
to a component that is assembled. The test type corresponds to a test part and needs to be
removed at a defined disassembly operation. Operators should remove all defined test parts
for a material before completing the assembly process. The system can perform a
corresponding check if the TEST_PART rule of the Check Configuration activity is set to true.
Phantom assembly components are parts that have a bill of material (BOM), but are not
usually produced with a production order. They are produced as part of a parent assembly.
The material requirements for a production order include all components of the phantom
component, but the phantom component is not included. This allows a more structured
organization of the bill of material, without adding more work orders or stocked assemblies.
Reference designators specify where operators or machines must load components onto
assemblies. For example, reference designators can tell an operator that you want the same
component, such as a specific resistor model, loaded in four different places on a specific
board.
It is possible to enforce the system to record additional data during assembly, such as the
serial number of the used component. If this information is required for traceability purposes,
the assembly data type must be specified. Note that it is also possible to define this setting on
material level. If a respective setting is available on the material and on the BOM item level,
the BOM item setting takes precedence and overrides the settings on material level.
Usually, the BOM item corresponds to the component that will be assembled. However, it
might be possible that this component is not available, for example, if the component cannot
be delivered by the supplier. If this is the case, it is possible to specify alternate components
which can be used as a substitute. Similar to the previous setting, BOM item level settings
take precedence over the settings on the material level.
In some cases, the required component quantity cannot be preplanned (for example, lube,
paint, and so on) and might therefore differ from the BOM item quantity. For these
components, the Assembly Quantity as Required flag can be set. If set, the production
operator enters the consumed quantity of the respective component in the operation POD.

Lesson: Working With Bills of Material in SAP Manufacturing Execution
Components bearing this indicator will have no value in the Assembly Quantity field in the
POD. However, reports (such as an As-Build Summary Report) will show the right quantity.
BOM Building Blocks
Figure 19: Building BOMs by Using Building Blocks
If a set of components is used in many BOMs, it is possible to define building block BOMs in
the system. The latter contain a list of components. When creating a new BOM, instead of
supplying all components individually, the user can enter the building block BOM which is
automatically exploded by the system. After BOM explosion, the user can maintain further
details on the item level.
Hook Point Activities
Figure 20: Hook Point Activities Check Configuration (CT520) and Auto Assemble Component
(AUTOASSY_COMPONENT)
It is possible to set up the SAP Manufacturing Execution system to verify whether all BOM
components have been assembled correctly during the manufacturing of a product. To do
this, the CT520 hook point activity can be used to compare the components in the build
history of an SFC number to its BOM, to ensure that the SFCs have the correct number of
assembled components. This activity is commonly used with
the PRE_START, PRE_COMPLETE, and POST_COMPLETE hook points. If this activity is
executed at PRE_START, it checks for components of the previous operations only. If this
activity is executed at PRE_COMPLETE or POST_COMPLETE, it checks for components at the
current operation and all previous operations. For example, if CT520 is enabled as

PRE_COMPLETE step of the last assembly operation of a routing, the system will check
whether all BOM components have been assembled in the correct quantity.
If the Assembly Quantity as Required flag is set for a BOM item, the system will verify whether
or not the respective component was assembled at all, but it will not check the assembly
quantity.
Usually, the operator must specify the assembled components and their respective quantity
in the POD. If the system will automatically assemble the BOM components without the
operators input, the AUTOASSY_COMPONENT hook point activity can be used. This activity
automatically assembles components that have the assembly data type NONE and a defined
assemble operation, and saves the data to the SFC number's as-built record. This can occur
upon shop order release or at a specific operation by enabling the activity at one of the hook
points PRE_START, PRE_COMPLETE, or POST_ORDER_RELEASE.
To Create a BOM Template
1. In the SAP Manufacturing Execution activity manager, choose Product

Genealogy Genealogy Maintenance BOM Maintenance.
2. Enter BOM-TEMPLATE-##in the BOM field and A in the Version field.
3. Select the BOM Template checkbox.
4. Choose Save to save the BOM header and ignore the following message: No current
version defined for BOM TEST .
5. Maintain BOM items and respective quantities.
6. In the Status field, select Releasable and save the data.
7. Choose Clear to clear the page and create a new BOM.
8. In the new BOM, add a new BOM item. On the Component Details screen, browse for the
template BOM created above in order to add all components from the template BOM into
the current BOM.
9. Afterwards, change the quantities and assign assembly operations to each BOM item.
A template BOM is created. The template BOM can be used when other BOMs are set up.
LESSON SUMMARY

Unit 1
Learning Assessment
1. In SAP Manufacturing Execution, a work center is defined as a specific location in the site
where goods are produced, processed, or stored.
Determine whether this statement is true or false.
X True
X False
2. It is not possible to define a work center hierarchy that corresponds, for example, to a
production line.
X True
X False
3. Discuss when work centers or resources are used.
4. Explain the concept of operations.
5. Before routings can be created, it is mandatory to create the respective operations.

X True
X False

Unit 1: Learning Assessment
6. It is not possible to use the same operation in more than one routing.
X True
X False
7. Which of the following operation types are available in the system?

Choose the correct answers.
X A Normal operation
X B Test operation
X C Special operation
X D Non conformance operation
X E Repair operation
8. Define the concept of routings in SAP Manufacturing Execution.
9. How can routings be created in the system?

X A Replication from ERP
X B Manually as a tabular routing
X C Manually as a graphical routing
10. Routings cannot be nested hierarchically.

X True
X False
11. Routings can have a complex hierarchy to model analysis-repair loops of different
complexity.
X True
X False

12. Define the concept of work instruction in SAP Manufacturing Execution.
13. Work instructions can be automatically displayed to the operator using the Work
Instruction plug-in.
X True
X False
14. Work instructions must always be maintained in the material master.

X True
X False
15. Define the concept of materials in SAP Manufacturing Execution.
16. Which of the following material types are available?

X A Manufactured
X B Purchased
X C Manufactured/Purchased
X D Tool
17. Materials must always be configured as lot size 1.0 in SAP Manufacturing Execution.
X True
X False

18. Explain how the default BOM and routing are selected at order release.
19. Explain the concept of BOMs in SAP Manufacturing Execution.
20. BOM item quantities can be specified for quantities other than one header material.
X True
X False
21. Which of the following BOM types are available in the SAP Manufacturing Execution
system?
X A Master BOM
X B SFC BOM
X C Order BOM
X D Nonconformance BOM
22. Define the concept of test items in BOMs.

Unit 1
Learning Assessment - Answers
1. In SAP Manufacturing Execution, a work center is defined as a specific location in the site
where goods are produced, processed, or stored.
X True
X False
2. It is not possible to define a work center hierarchy that corresponds, for example, to a
production line.
X True
X False
3. Discuss when work centers or resources are used.
A resource is defined as a machine or other piece of equipment used to perform an

operation. Work centers are used to divide the portions of a routing along functional work
lines, and therefore, a work center corresponds to a sequence of resources required to
produce or assemble a material.
4. Explain the concept of operations.
Operations are defined as individual, basic steps that are required to manufacture a
product.
5. Before routings can be created, it is mandatory to create the respective operations.

X True
X False

Unit 1: Learning Assessment - Answers
6. It is not possible to use the same operation in more than one routing.
X True
X False
7. Which of the following operation types are available in the system?

X A Normal operation
X B Test operation
X C Special operation
X D Non conformance operation
X E Repair operation
8. Define the concept of routings in SAP Manufacturing Execution.
In SAP Manufacturing Execution, a routing is defined as a set of work steps that are
required to execute the production of a good. The routing contains the relevant
operations, their sequence, and the work centers at which the operations will be executed.
9. How can routings be created in the system?

X A Replication from ERP
X B Manually as a tabular routing
X C Manually as a graphical routing
10. Routings cannot be nested hierarchically.

X True
X False

11. Routings can have a complex hierarchy to model analysis-repair loops of different
complexity.
X True
X False
12. Define the concept of work instruction in SAP Manufacturing Execution.
A work instruction is an explanation of what to do in a particular production circumstance.
13. Work instructions can be automatically displayed to the operator using the Work
Instruction plug-in.
X True
X False
14. Work instructions must always be maintained in the material master.

X True
X False
15. Define the concept of materials in SAP Manufacturing Execution.
A material in SAP Manufacturing Execution is defined as a unique manufactured or

purchased part, that is processed or consumed on the shop floor. As with all master data,
it is defined on site level.
16. Which of the following material types are available?

X A Manufactured
X B Purchased
X C Manufactured/Purchased
X D Tool

17. Materials must always be configured as lot size 1.0 in SAP Manufacturing Execution.
X True
X False
18. Explain how the default BOM and routing are selected at order release.
On the material level, default settings for routing and BOM can be defined for different
order types, for example, standard production order, inspection order, or rework order.
Upon release of the specific shop order, default BOM and routing are assigned, provided
they have not been received via the production order download from ERP, or manually
entered in the shop order through the Manage Shop Order or Release Shop Order apps,
respectively.
19. Explain the concept of BOMs in SAP Manufacturing Execution.
A bill of material (BOM) is defined as a structured list of all the components, and their
quantities, that make up an assembly. The BOM consists of the header and the item level.
20. BOM item quantities can be specified for quantities other than one header material.
X True
X False
21. Which of the following BOM types are available in the SAP Manufacturing Execution
system?
X A Master BOM
X B SFC BOM
X C Order BOM
X D Nonconformance BOM

22. Define the concept of test items in BOMs.
The test type corresponds to a test part and needs to be removed at a defined
disassembly operation. Operators should remove all defined test parts for a material
before completing the assembly process. The system can perform a corresponding check
if the TEST_PART rule of the Check Configuration activity is set to true.

UNIT 2 Master Data Integration
Lesson 1
Configuring Material Master Integration 33
Lesson 2
Configuring Bill of Material Integration 41
Lesson 3
Configuring Work Center Integration 47
Lesson 4
Configuring Routing Integration 55
UNIT OBJECTIVES
Understand the integration of the SAP ERP material master with SAP Manufacturing
Execution
Understand the integration of the SAP ERP BOM with SAP Manufacturing Execution
Understand the integration of the SAP ERP work centers with SAP Manufacturing
Execution
Understand the integration of the SAP ERP routing with SAP Manufacturing Execution

Unit 2
Lesson 1
Configuring Material Master Integration
LESSON OBJECTIVES
Execution
Material Master Integration
Figure 21: Integration of the SAP ERP Material Master to SAP Manufacturing Execution
Before production orders, BOMs, or floor stock can be created in SAP Manufacturing
Execution, the respective material master must be created. The material integration process
ensures that a material created and/or updated in SAP ERP is transferred to SAP
Manufacturing Execution. The figure shows the process and data flow from SAP ERP through
SAPMEINT, running on SAP Manufacturing Integration and Intelligence, to SAP
Manufacturing Execution. A user creates a new material master in SAP ERP by maintaining
the required views (for example Basic Data 1, Basic Data 2, Classification, Work Scheduling,
MRP2, and so on). Some of the views (for example Basic Data 1 and 2) are cross-plant, other
views (for example, Work Scheduling and MRP2) contain plant-specific data. After the
material master has been created, the replication process is triggered and SAP ERP creates
an IDoc (MATMAS03 or MATMAS05) which is received by the SAPMEINT integration
component running on SAP Manufacturing Integration and Intelligence. In SAPMEINT, a split
workflow receives the IDoc, processes the data, and triggers one or more standard workflows,
depending on the number of sites defined in SAP Manufacturing Execution. The material data
is received by a service transaction running in SAP Manufacturing Execution, where a new
material master is created by the service. After successful transfer, the user can verify
whether all of the fields and values have been transferred correctly. If so, the created material

Unit 2: Master Data Integration
master can be enriched on the SAP Manufacturing Execution side, with data that is only
relevant for the manufacturing process.
Changes to the material master in SAP ERP can also be transferred to SAP Manufacturing
Execution following the same process. The respective update logic will be discussed later in
this unit.
Figure 22: Material IDoc MATMAS05
Intermediate Document (IDoc) is the standard SAP format for Electronic Data Interchange
(EDI) between systems. Different message types (such as materials, classification,
production orders, and so on) normally represent different specific formats, the IDoc types -
for example MATMAS05, CLFMAS02, LOIPRO03, and so on. The IDoc interface exchanges
business data with an external system, such as SAP Manufacturing Execution. The IDoc
interface consists of the definition of a data structure, along with processing logic for this data
structure. The data structure is the IDoc. The IDoc is the exchange format common to all the
communicating systems.
All IDocs are structured according to specific rules. IDocs contain administration information
for technical processing, as well as the actual application data, which is stored in segments. A
segment comprises segment fields as the smallest unit of the IDoc and it is possible to
establish a hierarchy of segments.
In the figure, Material IDoc MATMAS05, an excerpt of the IDoc type MATMAS05 (which can
be used for the transfer of the material master from SAP ERP to SAP Manufacturing
Execution) is displayed on the left side, with the three segments E1MARA1M, E1MAKTM, and
E1MARCM. In the IDoc, the (usually unique) segment E1MARA1M contains the header data of
the material master which is stored in the MARA table in the SAP ERP system. The material
short texts are stored in the E1MAKTM segment and correspond to the MAKT table of the
SAP ERP system. As the material short text can be maintained language dependent, the
respective segment occurs as many times as there are language-specific short texts
maintained for the respective material. The plant-dependent data (stored in the MARC table
of the SAP ERP system) is contained in the E1MARCM segment. This segment can also occur
multiple times if the material master is set up accordingly. In SAP ERP, data that is
manufacturing relevant is usually plant-specific.
On the right side of the figure, an example IDoc for the material T-F100 is displayed. On the
header, the material number and the base unit of measure is shown. For the language-specific
material short text, two entries (German and English, respectively) are transferred. In
addition, the IDoc contains plant-specific data for the two plants 1000 and 1100, respectively,
in the E1MARCM segment. In the example in the figure, the procurement type of the T-F100

Lesson: Configuring Material Master Integration
material is set to E (in-house production) and X (both procurement types) in the plant 1000
and 1100, respectively. In addition, the production storage location is maintained only in plant
1000.
As mentioned in the previous figure, this IDoc is sent out by SAP ERP to the SAP
Manufacturing Execution system, for example, after the material master of the T-F100
material is created. In the latter system, SAPMEINT receives the IDoc and triggers the
creation of a new material master in SAP Manufacturing Execution.
Figure 23: MEINT Processing Logic for Material Master IDocs
In the figure, the detailed processing logic of SAPMEINT is displayed. A material IDoc
MATMAS05 is received. For each material, one IDoc is transferred from SAP ERP to
SAPMEINT. The message listener running on SAP Manufacturing Integration and Intelligence
receives the IDoc and triggers the split workflow MATMAS05. Technically, the IDoc has an
XML structure which can be manipulated using XSLT (Extensible Stylesheet Language
Transformations). For each workflow in SAPMEINT, different additional data manipulations
can be defined at different time points and for different use cases. For example, it is possible
to trigger a pre XSLT manipulation that reads additional data from the database that can then
be used in the subsequent XSLT. In addition to the default pre XSLT manipulation delivered
by SAP, partners and customers can define their own processing logic.
As shown in the example in the figure, the split workflow MATMAS05 receives the
MATMAS05 IDoc. Then, the pre XSLT transformation transaction Visiprise/
ERPShopFloorIntegration/frame/workflow/EnrichMessageWithSuppPlantData is
executed. This transaction reads all sites that are available in the SAP Manufacturing
Execution system. In the next step, the split XSLT WEB://Visiprise/XSLT/Inbound/
Material/MaterialSplitMATMAS05.xslt is executed. This XSLT splits the received IDoc
and creates as many subsequent IDocs of type Z_MATMAS05 as there are sites available. If
the IDoc MATMAS05 contains plant-data that has no corresponding site in SAP
Manufacturing Execution, the respective data is ignored. The subsequent IDocs
Z_MATMAS05 are received by the standard workflow Z_MATMAS05 which executes the
request XSLT WEB://Visiprise/XSLT/Inbound/Material/
MaterialRequestMATMAS05.xslt , that maps the ERP data fields to the SAP Manufacturing
Execution data fields. In the next step, the Service Transaction
java:com.sap.me.integration.ERPItemHandler is called which creates a new
material. If the material creation in SAP Manufacturing Execution is successful, a generic
success response XSLT WEB://Visiprise/XSLT/Inbound/GenericResponse.xslt is
sent.

Note that it is also possible to send the MATMAS03 IDoc type from SAP ERP to SAP
Manufacturing Execution, if no long material numbers are required. However, the respective
processing logic is similar to as shown in the figure. When using MATMAS03, the split
workflow MATMAS03 and the standard workflow Z_MATMAS03 are executed, respectively.
Note that customers can also enhance existing IDoc types or create new ones containing
additional data. In this case, new processing transactions are required that are able to map
customer-specific fields to the SAP Manufacturing Execution database.
In the Queue Monitor , the IDoc MATMAS05 received from SAP ERP can be identified by an
identifier which corresponds to the material number, for example T-F100. The follow-up IDoc
Z_MATMAS05 is identified by a combination of site and material number, for example 1000-
T-F100.
Prerequisites and Change Management
Figure 24: Prerequisites in SAP ERP and SAP Manufacturing Exaction
In order to enable communication between SAP ERP and SAP Manufacturing Execution,
Application Link Enabling (ALE), communication must be established between both systems.
This is usually done by the colleagues responsible for the administration of the SAP system
and will not be covered in detail in this course. However, in the ALE settings, the IDoc type
MATMAS03 or MATMAS05 is chosen for the transfer of the material master. For newer
systems (SAP ERP 6.0 EHP 6 and activated business function LOG_PP_MES_INT_03), the
new Data Replication Framework (DRF) can be used for the replication of the material master.
Using the latter has the general advantage that the SAP ERP system writes change pointers if
a respective master data object is changed, and the changes can be transferred directly after
the change is saved. In the ALE approach, data is sent out periodically, (for example, over
night), so there may be a temporary inconsistency between the master data in SAP ERP and
the respective data in SAP Manufacturing Execution. For details regarding the improved
integration, we recommend to carefully read SAP Note 1793291, which provides answers to
frequently asked questions. Usually, changes to master data, such as the material master, are
sent out periodically also, if DRF is used. However, it is possible to trigger the IDoc
immediately after the change is saved. The required business functions and settings are
explained in detail in SAP Note 2515556.
When using DRF, the material master IDoc can be triggered using the transaction DRFOUT .
The transaction is based on the standard report RDRF_MESSAGE_OUT, which can also be
scheduled periodically if instantaneous data replication is not required. When using the ALE
scenario, the transaction BD10 can be used to trigger the material master IDoc.

On the SAP Manufacturing Execution side, the system rule settings must be set up such that
the rule ERP Integration Active is set to true . Otherwise, the sent data is ignored by SAP
Manufacturing Execution. Furthermore, settings regarding the field update logic for the
material master must be set up. In the ERP Field Maintenance application, settings for the
individual fields of the material object can be made. For more information, see the figure in the
next section.
Figure 25: Change Management Logic of MEINT for the Material Master
If an object is created in SAP ERP and transferred to SAP Manufacturing execution, a new
object with version A is created by SAPMEINT. If an object is changed in SAP ERP, the update
logic set up in ERP Field Maintenance determines how changes on the ERP side affect data in
SAP Manufacturing Execution and how the update is done. In general, the three possibilities
for how a change on the ERP side is processed by SAP Manufacturing Execution are as
follows:
1. Create a new version of the object.
2. Update the current version.
3. Ignore the update.
However, the material master setup process only supports the second variant, so that it is
only possible to update the current version of the material after a change is done in SAP ERP
and transferred to SAP Manufacturing Execution.
In addition to the update logic, it must be determined which of the two systems is the master
for fields that exist in both systems. For example, the Production Storage Location can be
maintained both in the SAP ERP and the SAP Manufacturing Execution system. Changes
must be transferred from the primary to the secondary system. If SAP ERP is defined as a
master for this field, the Update Indicator of the respective field is set to Update for the
category material in the ERP Field Maintenance application. If a field will be maintained in SAP
Manufacturing Execution, the respective field must not be added to the list so that data is not
overwritten when the IDoc from SAP ERP is processed.

Material Classification Integration
Figure 26: Integration of Classification Data of the SAP ERP Material Master to SAP Manufacturing Execution
The purpose of material classification is to attach additional information to the material

master. During import, the classification data is mapped to Custom Data fields in Material
Maintenance in SAP Manufacturing Execution. The figure displays the transfer process and
data flow of material classification data. It is very similar to the approach of the material
master replication. In SAP ERP, a material is classified by assigning a material class (class
type 001) to the respective material in the material master. When the material master is sent
from SAP ERP to SAP Manufacturing Execution, the IDoc CLFMAS02 is also triggered. Note
that this IDoc is always send out together with the material master IDoc and that it is not
possible to send classification data separately in SAP standard. The CLFMAS02 IDoc is
received by SAPMEINT by a split workflow. The split workflow triggers one or more standard
workflows, depending on the sites that are available in SAP Manufacturing Execution. The
standard workflow calls a service transaction in SAP Manufacturing Execution which updates
the custom fields of the respective material master. Afterwards, the user can verify the data
transfer in the Manage Materials application on the CUSTOM DATA tab.
Figure 27: Classification IDoc CLFMAS02

In the figure, the CLFMAS02 IDoc type is shown. The first segment E1OCLFM contains the
header class data and where it is assigned to. In the example in the figure, the class type 001
is assigned to the object T-F100 which is maintained in the MARA table. This is the technical
representation of a material which is classified with a material class. The second segment
E1KSSKM contains the assigned class (class 100 in this example). For each class, one or more
characteristics can be maintained. The respective characteristic values are transmitted in the
third segment, E1AUSPM. As there is a one to many relationship from a class to the assigned
class characteristic, the third segment can occur multiple times in the IDoc. In the example,
three characteristics (pump capacity = C002, turning speed = C003, usage = C005) with
respective values are assigned to the pump T-F100. In SAP ERP, class characteristics can
have various data formats such as numeric, date, time, character, and so on. Technically, the
different data formats are saved to different database fields. In the default SAPMEINT
mapping logic, only the field Characteristic Value (ATWRT) is mapped to a Custom Field of the
Material Master in SAP Manufacturing Execution.
Figure 28: MEINT Processing Logic for Material Classification IDocs
In the figure, the detailed processing logic of SAPMEINT is shown: A material classification
IDoc CLFMAS02 is received by the split workflow CLFMAS02_SAVE_ITEM_CUST_FLDS. As
for the material master IDoc, the split workflow executes a pre XSLT manipulation
Visiprise/ERPShopFloorIntegration/frame/workflow/
EnrichMessageWithSuppPlantData that reads the sites defined in SAP Manufacturing
Execution. The split XSLT Visiprise/XSLT/Inbound/MaterialCustomData/
MaterialCustomDataSplit.xslt is then triggered which creates one IDoc
Z_CLFMAS02_SAVE_ITEM_CUST_FLDS per combination of material and site.
The standard workflow Z_CLFMAS02_SAVE_ITEM_CUST_FLDS receives the IDoc and
executes the Pre XSLT manipulation Visiprise/ERPShopFloorIntegration/workflow/
MaterialCustomData/CLFMAS_LMN_Enrichment in order to obtain the long material
name, if the long material number functionality is switched on. The mapping from SAP ERP
fields to SAP Manufacturing Execution fields is performed by the request XSLT Visiprise/
XSLT/Inbound/MaterialCustomData/MaterialCustomDataRequest.xslt .
Afterwards, the service transaction
java:com.sap.me.integration.ERPItemCustomDataHandler is called and updates
custom fields of the respective material object. If successful, the generic SUCCESS response
is sent out. As a result of this processing logic, the fields defined on the CUSTOM DATA tab of

the material are updated with classification values. Note that, in order to be able to add or
update the custom fields, the respective material master must exist in SAP Manufacturing
Execution. Therefore, it must be ensured that the CLFMAS02 IDoc is always processed before
the respective material IDoc.
Similar to the prerequisites for the material master, ALE communication settings to transmit
the CLFMAS02 IDoc must be configured on the ERP side. On the SAP Manufacturing
Execution side, the system rule settings must be set up such that the rule ERP Integration
Active is set to true . Otherwise, the sent data is ignored by SAP Manufacturing Execution.
Furthermore, settings regarding the field update logic for the material master must be set up.
In the ERP Field Maintenance application, settings for the individual fields of the material
object can be made. With respect to change management, the same logic as discussed above
applies.
Technically, SAP ERP classification values are mapped to custom data fields of the material
master of SAP Manufacturing Execution. Therefore, before being able to process the IDoc, the
respective customer fields must be added to the Material category in the Custom Data
Maintenance application. The data field key must be identical to the characteristic name
which is defined in SAP ERP in order to successfully map the classification data.
LESSON SUMMARY
Execution

Unit 2
Lesson 2
Configuring Bill of Material Integration
LESSON OBJECTIVES
Bill of Material Integration
Figure 30: Integration of the SAP ERP Bill of Material to SAP Manufacturing Execution
The basic bill of material (BOM) in SAP ERP contains a list of all the components belonging to
the assembly. This structured list of components is transferred to SAP Manufacturing
Execution in the BOM integration process to ensure that all of the components are tracked
during the manufacturing process. Each BOM is transferred as a single level BOM, so any
subassembly BOMs need to be transferred over separately. The figure shows the process and
data flow from SAP ERP through SAPMEINT running on SAP Manufacturing Integration and
Intelligence to SAP Manufacturing Execution. A user creates a new master BOM in SAP ERP
by maintaining the BOM header and assigning BOM components. A BOM in SAP ERP is
always plant-specific as the plant is defined as one of the key fields. After the master BOM has
been created, the replication process is triggered and SAP ERP creates an IDoc (BOMMAT03)
which is received by the SAPMEINT integration component running on SAP Manufacturing
Integration and Intelligence. In SAPMEINT, a standard workflow receives the IDoc and
executes data mapping. The BOM data is received by a service transaction running in SAP
Manufacturing Execution where a new BOM is created by the service. After successful
transfer, the user can verify whether all of the fields and values have been transferred
correctly. If so, the created BOM can be enriched on the SAP Manufacturing Execution side,
with data that is only relevant for the manufacturing process.

Changes to the master BOM in SAP ERP can also be transferred to SAP Manufacturing
this unit.
Figure 31: Bill of Material IDoc BOMMAT03
In the figure, an excerpt of the IDoc type BOMMAT03 (which can be used for the transfer of
the master BOM from SAP ERP to SAP Manufacturing Execution) is displayed on the left side
with the segments E1STZUM, E1MASTM, E1STKOM, and E1STPOM. In the IDoc, the segment
E1STZUM contains the header data of the master BOM which is stored in the STZU table in
the SAP ERP system. The E1MASTM segment contains the material that is assigned to this
BOM and the E1STKOM segment contains additional BOM header data, for example the base
quantity. For each BOM item, a segment E1STPOM is created which contains information
about the component, such as material number and quantity, respectively. This segment can
occur multiple times as there is a one to many relationship between the BOM and the BOM
items.
On the right side of the figure, an example IDoc for the BOM 714 for the manufacturing of the
T-F100 material in plant 1000 is displayed. On the header, the base unit of measure and the
base quantity is shown. In SAP ERP, the base quantity can be an arbitrary quantity and the
unit of measurement and the component quantities of each component correspond to the
quantity in the BOM header. For example, it is possible to define the BOM for one pump. In
this case, the base quantity is 1 pc and for all BOM items, the user specifies how many of each
item are required to assemble one pump. Alternatively, it is also possible to define a BOM for
the manufacturing of 100 pumps, for example, if the usual manufacturing lot size is 100 pc. In
this case, the user must specify for each BOM item how many units of each components are
required to assemble 100 pumps.
In the example shown in the figure, the BOM is defined for the manufacturing of one pc of the
T-F100 pump. The BOM ID in SAP ERP is 714 and the master BOM is assigned to the T-F100
material in the plant 1000. The BOM contains two item materials T-B100 and T-T300 with an
assembly quantity of 1 pc and 8 pc, respectively, meaning that for the manufacturing of one
pump, one pc of T-B100 and eight pc of T-T300 are required.
Manufacturing Execution system, for example, after the master BOM of the T-F100 material
in the plant 1000 was created. In the latter system, SAPMEINT receives the IDoc and triggers
the creation of a new BOM in SAP Manufacturing Execution.

Lesson: Configuring Bill of Material Integration
Figure 32: MEINT Processing Logic for Bill of Material IDocs
In the figure, the detailed processing logic of SAPMEINT is displayed. A BOM IDoc
BOMMAT03 is received. For each BOM and plant combination, one IDoc is transferred from
SAP ERP to SAPMEINT. The message listener running on SAP Manufacturing Integration and
Intelligence receives the IDoc and triggers the standard workflow BOMMAT03. Technically,
the IDoc has an XML structure which can be manipulated using XSLT (Extensible Stylesheet
Language Transformations). For each workflow in SAPMEINT, different additional data
manipulations can be defined at different time points and for different use cases. For
example, it is possible to trigger a pre XSLT manipulation that reads additional data from the
database that can then be used in the subsequent XSLT. In addition to the default pre XSLT
manipulation delivered by SAP, partners and customers can define their own processing
logic.
The standard workflow BOMMAT03 receives the IDoc and executes the request XSLT
Visiprise/XSLT/Inbound/BOM/BOMRequest.xslt that maps the ERP data fields to the
SAP Manufacturing Execution data fields. In the next step, the Service Transaction
java:com.sap.me.integration.ERPBomHandler is called which creates a new BOM. If
the BOM creation in SAP Manufacturing Execution is successful, a generic success response
XSLT Visiprise/XSLT/Inbound/GenericResponse.xslt is sent.
As explained in the previous figure, the BOM in SAP ERP can also be defined for a different
base quantity than 1 pc. However, SAP Manufacturing Execution does not support this
functionality and expects that the BOM and the respective BOM items are always defined for
one unit of the manufactured product. Therefore, during import, the BOM item quantities are
divided by the quantity in the base unit of measure in order to normalize all BOM item
quantities.
In the Queue Monitor , the IDoc BOMMAT03 received from SAP ERP can be identified by an
identifier which corresponds to the scheme "<Plant> - <Material Number (MATNR)> - <BOM
Usage (STLAN)> - <Alternative BOM (STLAL)>", for example, T-F100-1-01.

Application Link Enabling (ALE) communication must be established between both systems.
BOMMAT03 is chosen for the transfer of the master BOM. Note that DRF is not available for
the transfer of BOMs so that the ALE scenario (transaction BD30) must be used.
Manufacturing Execution. Furthermore, settings regarding the field update logic for the BOM
must be set up. In the ERP Field Maintenance application, settings for the individual fields of
the BOM object can be made. For more information, see the figure in the next section.
Figure 34: Change Management Logic of MEINT for the Material Master
object with version A is created by SAPMEINT. If an object is changed in SAP ERP, the update
logic set up in ERP Field Maintenance determines how changes on the ERP side affect data in
SAP Manufacturing Execution and how the update is done. In general, the three possibilities

Lesson: Configuring Bill of Material Integration
for how a change on the ERP-side is processed by SAP Manufacturing Execution are as
follows:
For BOMs, all three scenarios are supported by SAP Manufacturing Execution. In the example
in the figure, the BOM Component List setting is set to Upversion , meaning that if the BOM
components or the quantities are changed in SAP ERP, a new BOM version will be created in
SAP Manufacturing Execution, which will become the new current version. The Description
field setting is set to Update so that the current version of the BOM will be updated with the
changed data. If a field is only maintained in SAP Manufacturing Execution, the respective
entry must not be maintained in ERP Field Maintenance. In addition, it is also possible to set
the Restricted indicator. If SAPMEINT receives a BOM IDoc where the field value does not
agree with the value of the respective field in SAP Manufacturing Execution, the IDoc will not
be processed and is displayed with an error status in the Queue Monitor .
Additional Information
Figure 35: Additional Integration Details
In SAP ERP, the assignment of components to routing operations is not maintained on BOM
level, but in the routing. Therefore, the BOMMAT03 IDoc does not contain component
allocation information, and the BOM created in SAP Manufacturing Execution does not
contain assigned assembly operations. Later, when transferring an order, this information is
added to the respective BOM. Furthermore, in SAP Manufacturing Execution, the BOM object
has a Custom Field ERP_MATERIAL and this field is populated with the value from the field
MATNR. SAP Manufacturing Execution associates this material with BOM by populating the
BOM field in Material Maintenance .
In SAP ERP, alternative BOM items can be maintained by assigning BOM items to the same
Alternative Item Group. During transfer of the BOMMAT03 IDoc, this information is
transferred to SAP Manufacturing Execution and the respective information is available on
the Alternates tab of the BOM component. During mapping, the component with the highest
usage probability is listed as a BOM component. All other items in the same alternative group
are displayed on the Alternates tab.
Co-product is a product that is produced in addition to the main product range. This holds
significant financial value. Co-products are desirable products because they can be used in
other production processes or even sold as standalone offerings. A by-product is a secondary
product derived from a manufacturing process or chemical reaction. It is not the primary
product or service being produced. In the context of production, a by-product can be defined
as the output from a joint production process that is minor in quantity or net realizable value
when compared to the main product. In SAP ERP, co- and by-products are maintained with

negative quantities in the BOM. When transferring the BOMMAT03 IDoc to SAP
Manufacturing Execution, the co-/by-product information is not displayed correctly. After the
production order IDoc is received and a respective BOM is created by SAPMEINT, only then
will the co-/by-product indicator be corrected.
LESSON SUMMARY

Unit 2
Lesson 3
Configuring Work Center Integration
LESSON OBJECTIVES
Execution
Work Center Integration
Figure 36: Integration of the SAP ERP Work Center to SAP Manufacturing Execution
A work center is an area at a site at which inventory is manufactured or processed. A work

center in SAP ERP can be mapped to either a work center or a resource in SAP Manufacturing
Execution, depending on how the work center is configured. To keep the resources and work
centers in SAP Manufacturing Execution consistent with the capacity that is defined as
available in SAP ERP, you can transfer the defined production work centers for each plant.
The figure shows the process and data flow from SAP ERP through SAPMEINT running on
SAP Manufacturing Integration and Intelligence to SAP Manufacturing Execution. A user
creates a new work center in SAP ERP by maintaining the work center header and assigning
different capacities to the work center. A work center in SAP ERP is always plant-specific as
the plant is defined as one of the key fields. After the work center and the related data has
been created, the replication process is triggered and SAP ERP creates an IDoc (LOIWCS03)
executes data mapping. The work center data is received by a service transaction running in
SAP Manufacturing Execution where a new work center is created by the service. After
successful transfer, the user can verify whether all fields and values have been transferred
correctly. If so, the created work center can be enriched on the SAP Manufacturing Execution
side, with data that is only relevant for the manufacturing process. For example, additional

resources that are only available in SAP Manufacturing Execution could be added to the work
center.
Changes to the work center in SAP ERP can also be transferred to SAP Manufacturing
this unit.
Figure 37: Work Center IDoc LOIWCS03
In the figure, an excerpt of the IDoc type LOIWCS03 (which can be used for the transfer of the
work centers from SAP ERP to SAP Manufacturing Execution) is displayed on the left side
with the segments E1CRHDL, E1CRTXL, E1KAKOL, and E1KAKOIL. In the IDoc, the segment
E1CRHDL contains the header data of the work center which is stored in the CRHD table in the
SAP ERP system. The E1CRTXL segment contains the language dependent work center short
texts. The segments E1KAKOL and E1KAKOIL contain information about the individual
capacities that can be assigned to the work center.
On the right side of the figure, an example IDoc for the work center T-E00 ("Final Assembly")
in plant 1000 is displayed. In the header, the work center key and the standard value key as
defined in SAP ERP is displayed, followed by the language dependent work center short texts
in the next segment. For this work center, three individual capacities (for example Drill I to III)
have been defined in order to being able to perform a detailed capacity planning in SAP ERP.
Manufacturing Execution system, for example, after the work center T-E00 in the plant 1000
is created. In the latter system, SAPMEINT receives the IDoc and triggers the creation of a
new work center in SAP Manufacturing Execution.

Lesson: Configuring Work Center Integration
Figure 38: MEINT Processing Logic for Work Center IDocs
In the figure, the detailed processing logic of SAPMEINT is displayed. A work center IDoc
LOIWCS03 is received. For each work center and plant combination, one IDoc is transferred
from SAP ERP to SAPMEINT. The message listener running on SAP Manufacturing Integration
and Intelligence receives the IDoc and triggers the standard workflow LOIWCS03. Technically,
the IDoc has an XML structure which can be manipulated using XSLT (Extensible Stylesheet
database that can then be used in the subsequent XSLT. In addition to the default pre XSLT
logic.
The standard workflow LOIWCS03 receives the IDoc and executes the pre XSLT manipulation
Visiprise/ERPShopFloorIntegration/workflow/WorkCenter/
WorkCenterSvkEnrichment.trx . This transaction executes a BAPI call to SAP ERP to
receive the standard value key details (description and list of parameter IDs) which are
required for the further logic. Then, the request XSLT Visiprise/XSLT/Inbound/
WorkCenter/WorkCenterRequestLOIWCS03.xslt maps the ERP data fields to SAP
Manufacturing Execution data fields. In the next step, the Service Transaction
java:com.sap.me.integration.ERPWorkCenterWithResourcesHandler is called,
which creates a new work center. If the work center creation in SAP Manufacturing Execution
is successful, a generic success response XSLT Visiprise/XSLT/Inbound/
GenericResponse.xslt is sent.
If the pre XSLT manipulation can retrieve a standard value key, the respective entry is also
created in the SAP Manufacturing Execution database. The entry can be maintained using the
Standard Value Key Maintenance application.
Note that customers can also enhance existing IDoc types and/or create new ones containing
In the Queue Monitor , the IDoc LOIWCS03 received from SAP ERP can be identified by an
identifier which corresponds to the scheme <Plant (WERKS)> - Work Center (ARBPL)", for
example, 1000-T-E00.

LOIWCS03 is chosen for the transfer of the work center. For newer systems (SAP ERP 6.0
EHP 6 and activated business function LOG_PP_MES_INT_03), the new Data Replication
Framework (DRF) can be used for the replication of the work center. Using the latter has the
general advantage that the SAP ERP system writes change pointers if a respective master
data object was changed and that the changes can be transferred directly after the change
was saved. In the ALE approach, data is sent out periodically (for example, over night) so
there may be a temporary inconsistency between the master data in SAP ERP and the
respective data in SAP Manufacturing Execution. For details regarding the improved
integration, we recommend to carefully read SAP Note 1793291, which provides answers to
frequently asked questions. Usually, changes to master data, such as the work center, are
sent out periodically also, if DRF is used.
When using DRF, the routing IDoc can be triggered using transaction DRFOUT . The transaction
is based on the standard report RDRF_MESSAGE_OUT which can also be scheduled
periodically if instantaneous data replication is not required. If immediate data replication of
work center changes is required, this is also possible. See SAP Note 2515556 for details.
When using the ALE scenario, the transaction POIM can be used to trigger the work center
IDoc. However, note that the use of new IDoc types in combination with the POIM transaction
is not supported and the LOIWCS02 IDoc type must be used instead. See SAP Note 1793291.
Manufacturing Execution. Furthermore, settings regarding the field update logic for the work
center must be set up. In the ERP Field Maintenance application, settings for the individual
fields of the work center object can be made. For more information, see the figure in the next
section.

Figure 40: Change Management Logic of MEINT for the Work Center
object created by SAPMEINT. If an object is changed in SAP ERP, the update logic set up in
ERP Field Maintenance determines how changes on the ERP side affect data in SAP
Manufacturing Execution and how the update is done. In general, the three possibilities for
how a change on the ERP side is processed by SAP Manufacturing Execution are as follows:
However, the work center setup process only supports the second variant so that it is only
possible to update the work center after a change was done in SAP ERP and transferred to
SAP Manufacturing Execution. Note that the work center in SAP Manufacturing Execution
does not have a version.
for fields that exist in both systems. For example, the Description can be maintained both in
the SAP ERP and the SAP Manufacturing Execution system. Changes must be transferred
from the primary to the secondary system. If SAP ERP is defined as a master for this field, the
Update Indicator of the respective field is set to Update for the category Work Center in the
ERP Field Maintenance application. If a field will be maintained in SAP Manufacturing
Execution, the respective field must not be added to the list so that data is not overwritten
when the IDoc from SAP ERP is processed.

Additional Information
Figure 41: Additional Integration Details: Work Centers With Individual Capacities
If a detailed planning in SAP ERP on individual capacities is required, it is possible to define

one or more capacities in each work center capacity. If a LOIWCS03 IDoc is sent to SAP
Manufacturing Execution, SAPMEINT creates a work center for the ERP work center and one
resource per work center capacity. The resources are then automatically assigned to the work
center as nested resources. A possible business scenario could be, for example, an assembly
line with individual segments. The assembly line corresponds to the work center and the
individual segments correspond to the capacities, respectively. When a shop order is then
released to the work center in SAP Manufacturing Execution, the system ensures that the
individual SFCs can only be processed on the resources that are attached to this work center.
Using this approach, a sequential processing of SFCs along a production line can be enforced
easily.
When SAP Manufacturing Execution receives an update, the following scenarios can be
distinguished:
1. Only the capacity is updated: In this case, SAPMEINT updates the resource.
2. If a capacity is removed from the work center in SAP ERP, the corresponding SAP
Manufacturing Execution resource is removed from work center members but still present
in the system. The resources status is automatically changed to disabled or pending,
depending on whether there is work done on the resource.
3. If the capacity is assigned again to the work center, the resource is updated and assigned
again to the work center.
In all cases, the system will respect the update rules as defined in the ERP Field Settings
application.

Figure 42: Additional Integration Details: Mapping of SAP ERP Work Centers to SAP Manufacturing Execution
Resources and Work Centers
It is possible to set up work centers in SAP ERP such that they are automatically converted to
work centers or resources in SAP Manufacturing Execution. Instead of the LOIWCS03 IDoc
type, LOIWCS02 must be used. As shown in the figure, a SAP ERP work center that is
assigned to the category 9000 is automatically mapped to a SAP Manufacturing Execution
work center. If the work center is assigned to the category 9100 instead, SAPMEINT creates a
resource for this work center. Note that in order to enable the LOIWCS02 IDoc, the respective
ALE and DRF customizing must be executed and corresponding Work Center Categories
must be set up in the customizing of the SAP ERP system.
Figure 43: Additional Integration Details: Work Centers with Standard Value Keys
Standard value keys (SVK) are defined in SAP ERP and assigned to work centers together
with formulas that are used to calculate the operation duration and capacity requirement. For
example, on the work center, a processing formula is assigned to a capacity category that
defines that the capacity requirement in minutes corresponds to the sum of a fixed value plus
a flexible value that depends on the number of manufactured items. When assigning the work
center to an operation in the routing, the values are entered as a function of the operation
quantity. When the routing is used in a production order for the production of a certain
quantity, the required time is calculated. Let's assume a fixed time of 30 minutes, plus a
variable time of 10 minutes per item. If 10 items are manufactured, the required time is 30 +
10 * 10 min/item = 130 minutes. This theoretical benchmark value is then compared to the
time that was really needed to produce the goods. Deviations can occur, for example, if the

production ran more smoothly than actually planned (less time consumed), or if the
production took more time due to a machine malfunction.
As shown in the figure, the replication of SVK and related data from SAP ERP to SAP
Manufacturing Execution is possible. When the work center is replicated, the work center and
the SVK are created by SAPMEINT. Afterwards, the routing is replicated to SAP
Manufacturing Execution and the production standards are created in the SAP Manufacturing
Execution database on material-routing level. After the production order is transferred to SAP
Manufacturing Execution, the value is updated. This update is required due to the fact that it
is possible to maintain different values in the production order than actually planned in the
routing.
After the shop order was executed and real production times were recorded, the planned
values can be compared to the as-is values (for example, using the Earned Standards Log
Report) in order to calculate KPIs or correct the planned values. Note that it is a prerequisite
to have the Earned Standards plugin in the POD. This configuration is not included in the
delivered standard PODs in SAP Manufacturing Execution and must be configured in a
customer environment.
LESSON SUMMARY
Execution

Unit 2
Lesson 4
Configuring Routing Integration
LESSON OBJECTIVES
Routing Integration
Figure 44: Integration of the SAP ERP Routing to SAP Manufacturing Execution
In SAP ERP, the routing describes how to manufacture a product by specifying a sequence of
order operations. The routing is defined on material level with a possible 1:n relationship
between routing and materials. In the easiest case, a routing consists of one or more
operations, for example assembly, quality inspection, and packaging. It is possible to assign
BOM components to the individual routing steps. If BOM components are not explicitly
assigned to an operation, the system assumes that all BOM components are assigned to the
first routing step. Furthermore, it is possible to assign production resources and tools (PRT),
for example documents, to the individual routing steps that explain the manufacturing steps
in more detail. After the routing is created and released, it can be distributed to SAP
Manufacturing Execution using an IDoc. The figure shows the process and data flow from SAP
ERP through SAPMEINT running on SAP Manufacturing Integration and Intelligence to SAP
Manufacturing Execution. A user creates a new routing in SAP ERP by maintaining the routing
header and operations. Optionally, BOM components and PRTs can be assigned to the
individual operations. As with most manufacturing-relevant data, the routing is also plant-
specific. After the data has been created, the replication process is triggered and SAP ERP
creates an IDoc (LOIROU03), which is received by the SAPMEINT integration component
running on SAP Manufacturing Integration and Intelligence. In SAPMEINT, a standard
workflow receives the IDoc and executes data mapping. Note that in contrast to SAP ERP, the
routing and the operations are two different master data objects in SAP Manufacturing

Execution. Therefore, the service transaction running in SAP Manufacturing Execution

receiving the routing data also creates manufacturing operations, which are linked to the
respective routing in SAP Manufacturing Execution. After successful transfer, the user can
verify whether all of the fields and values have been transferred correctly. If so, the routing
and operations can be enriched on the SAP Manufacturing Execution side, with data that is
only relevant for the manufacturing process.
Changes to the routing in SAP ERP can also be transferred to SAP Manufacturing Execution
following the same process. The respective update logic will be discussed later in this unit.
Figure 45: Routing IDoc LOIROU03
In the figure, an excerpt of the IDoc type LOIROU03 (which can be used for the transfer of
routings from SAP ERP to SAP Manufacturing Execution) is displayed on the left side, with the
top segments E1MAPLL and E1MAPAL which are used to transfer the material-to-plan
assignment, as well as the plans lot size. The segment E1PLKOL contains the task list header
with, for example, the task list unit of measure, the short text, and the validity date. If long
texts are maintained on the header level of the routing, this information is included in the
E1PLLTH segment. The task list sequence segment E1PLFLL contains one E1PLPOL segment
for each production operation in the routing. If PRTs are assigned to an operation, this
information is transferred using the E1PLDOC segment of the IDoc. If BOM items are assigned
on operation level (not shown in the example in the figure), the IDoc contains the additional
segment E1PLMZL as a child of the E1PLPOL segment.
On the right side of the figure, an example IDoc that contains the routing for the
manufacturing of the material T-F100 is displayed. On the top, the material (T-F100) that is
assigned to the routing (plan group 500000276) is displayed. The routing is only valid for the
manufacturing of one to 999 pc. However, note that this information is not taken into account
by SAP Manufacturing Execution, as the routing in SAP Manufacturing Execution is not lot-
size dependent. The routing contains one production operation (10 / Component Assembly)
with detailed information, such as setup, machine, and labor time, respectively. In addition, a
PRT (document) is assigned to this operation.
Manufacturing Execution system, for example, after the production routing for material T-
F100 in plant 1000 was created and released. In the latter system, SAPMEINT receives the
IDoc and triggers the creation of a new routing and the related operations in SAP
Manufacturing Execution.

Lesson: Configuring Routing Integration
Figure 46: MEINT Processing Logic for Routing IDocs
The figure displays the detailed processing logic of SAPMEINT. A routing IDoc LOIROU03 is
received. For each routing in the plant, one IDoc is transferred from SAP ERP to SAPMEINT.
The message listener running on SAP Manufacturing Integration and Intelligence receives the
IDoc and triggers the standard workflow LOIROU03. Technically, the IDoc has an XML
structure which can be manipulated using XSLT (Extensible Stylesheet Language
The standard workflow LOIROU03 receives the IDoc and executes the request XSLT
Visiprise/XSLT/Inbound/Routing/RoutingRequest.xslt that maps the ERP data
fields to the SAP Manufacturing Execution data fields. In the next step, the Service
Transaction java:com.sap.me.integration.ERPRouterHandler is called which creates
a new routing and operations. If the creation in SAP Manufacturing Execution was successful,
a generic success response XSLT Visiprise/XSLT/Inbound/GenericResponse.xslt is
sent.
In the Queue Monitor , the IDoc LOIROU03 received from SAP ERP can be identified by an
identifier which corresponds to the scheme "<Plant (WERKS)> - Group (PLNNR) - Group
Counter (PLNAL)", for example, 1000-5000576-1.

LOIROU03 is chosen for the transfer of the routing. For newer systems (SAP ERP 6.0 EHP 5
and activated business function LOG_PP_MES_INT_02), the new Data Replication Framework
(DRF) can be used for the replication of the routing. Using the latter has the general
advantage that the SAP ERP system writes change pointers if a respective master data object
is changed, and that the changes can be transferred directly after the change is saved. In the
ALE approach, data is sent out periodically (for example, over night) so there may be a
temporary inconsistency between the master data in SAP ERP and the respective data in SAP
Manufacturing Execution. For details regarding the improved integration, we recommend to
carefully read SAP Note 1793291, which provides answers to frequently asked questions.
Usually, changes to master data, such as the routing, are sent out periodically also, if DRF is
used.
When using DRF, the routing IDoc can be triggered using the transaction DRFOUT . The
transaction is based on the standard report RDRF_MESSAGE_OUT which can also be
scheduled periodically if instantaneous data replication is not required. If immediate data
replication of routing changes is required, this is also possible. See SAP Note 2515556. When
using the ALE scenario, the transaction POIM can be used to trigger the routing IDoc.
However, note that the IDoc type LOIROU02 must be used in combination with the POIM
transaction. See SAP Note 1793291.
As the SAP ERP routing references work centers, this master data object must be available in
SAP Manufacturing Execution before routings can be replicated. Furthermore, as a routing in
SAP ERP is material-specific, the respective manufactured material must also exist in SAP
Manufacturing Execution before data replication.
Manufacturing Execution. Furthermore, settings regarding the field update logic for the
routing and routing step must be set up. In the ERP Field Maintenance application, settings for
the individual fields of the routing and routing step objects can be made. For more
information, see the figure in the next section.

Note that the following routing functions that are available in SAP ERP are not supported by
SAP Manufacturing Execution:
Multiple group counters
Additional sequences
SAP ERP milestone operations
Figure 48: Change Management Logic of SAPMEINT for the Routing
object created by SAPMEINT. If an object is changed in SAP ERP, the update logic set up in
ERP Field Maintenance determines how changes on the ERP side affect data in SAP
Manufacturing Execution, and how the update is done. In general, the three possibilities for
how a change on the ERP side is processed by SAP Manufacturing Execution are as follows:
The routing setup process supports all three versions. When SAPMEINT successfully creates
a new routing version, the version number is incremented, for example, from A-1 to A-2. The
highest version of a routing is set to Releasable and flagged as Current Version . Furthermore,
the last operation contained in a routing received from SAP ERP will be flagged as a reporting
step in SAP Manufacturing Execution so that SAPMEINT automatically sends the goods
receipt of the manufactured material to SAP ERP. By default, SAPMEINT creates a new
routing version if at least one of the following conditions is fulfilled:
Operation number was changed
Operation control key was changed
Operation short text was changed
for fields that exist in both systems. For example, the Description can be maintained both in
the SAP ERP and the SAP Manufacturing Execution system. Changes must be transferred
from the primary to the secondary system. If SAP ERP is defined as a master for this field, the
Update Indicator of the respective field is set to Update for the category Routing in the ERP
Field Maintenance application. If a field will be maintained in SAP Manufacturing Execution,

the respective field must not be added to the list so that data is not overwritten when the IDoc
from SAP ERP is processed.
Additional Information and Scenarios
Figure 49: Additional Integration Details: Routing With Inspection Characteristics
In SAP ERP, in-process quality inspection can be integrated into the manufacturing process
by assigning inspection characteristics to operations in the routing. In addition, the inspection
type for in-process inspection (03 in the SAP standard) must be assigned to the material
master in the manufacturing plant. If the production order is released SAP ERP automatically
creates an inspection lot which is required to execute the in-process quality inspection
process.
In the example shown in the figure, a qualitative inspection characteristic (for example,
Functional test), with two possible results (for example, pass or fail), is assigned to the
second manufacturing operation. If the routing is transferred to SAP Manufacturing Execution
in an IDoc, the respective quality inspection information is not transferred from SAP ERP to
SAP Manufacturing Execution as the routing or operation in SAP Manufacturing Execution
cannot store such information. Instead, the inspection-related information can only be
transferred to SAP Manufacturing Execution, together with the order itself, using the
LOIPRO03 IDoc. After the order IDoc is received in SAP Manufacturing Execution, the shop
order contains inspection-related information (for example, inspection lot number, sample
size, and operation in which the quality inspection will be executed), that is displayed on the
QM Inspection tab in the Shop Order Maintenance application.
For each in-process inspection operation (operation 20 in the example shown in the figure),
an own data collection group is created during receipt of the LOIPRO03 IDoc which can be
identified by the identifier "<Production Order Number>-<a 10-based counter>", for example
5003352-10. The data collection group is attached to the shop order/routing/routing step.
For each inspection characteristic of the operation in SAP ERP, a respective parameter in the
data collection group is created. Upon data transfer, the inspection sample size is calculated
by taking the ERP sampling procedure into account (for example, if a sampling procedure
states that 10% of the produced items must be inspected, a manufacturing lot size of 100
items corresponds to a SFC group size of 100 and an inspection sample size of 10). Note that
both the integration of qualitative and quantitative inspection characteristics is possible in
SAP Manufacturing Execution. For quantitative inspection characteristics, the respective
limits (minimum and maximum), as well as the target value, are imported from SAP ERP. In
the case of quantitative inspections, the following two scenarios can be distinguished:

Qualitative inspection with pass/fail outcome: In this case, a Boolean parameter with two
possible values (ACCEPT and REJECT) is created.
Qualitative inspection with characteristic attributes: In this case, a Data Field List
parameter is created. The assigned data field contains the possible characteristic
attributes (for example, color values).
Note that as a prerequisite of the second scenario, a respective data field of the type List must
exist in SAP Manufacturing Execution before importing the order IDoc. If the data field does
not exist, an error will occur during import. SAP Manufacturing Execution offers the possibility
to import QM selected sets from SAP ERP which contain the characteristic attributes using
the Data Field Definition Maintenance application. Furthermore, note that classed result
recording is not supported by SAP Manufacturing Execution.
Figure 50: Additional Integration Details: Routing With Allocated Components
In SAP ERP, it is possible to assign BOM components to routing operations in order to

influence the component requirement date. If no explicit assignment between BOM
components and routing operations is done, the system assumes that all components are
needed at the first operation, and the requirement date of the component corresponds to the
start date of the first operation. Otherwise, the respective components are needed at a later
point in time and the respective purchasing process can start later, for example.
In SAP Manufacturing Execution, there is no component assignment possible on routing and
on operation level. Instead, the assignment of components and operations is maintained in
the BOM. As BOM and routing are transferred independently from SAP ERP to SAP
Manufacturing Execution, it is not possible to transfer the assignment of components to
operations when transferring the routing. Instead, this information is transferred together
with the order in the LOIPRO03 IDoc.
In the example shown in the figure, the component T-B100 (T-B900) is assigned to the first
(third) manufacturing operation in SAP ERP. When the respective routing is transferred to
SAP Manufacturing Execution, the component assignment is lost. When the respective BOM
is transferred in a BOMMAT03 IDoc, the components are transferred, but without the
assignment to production operations. Only when transferring the order IDoc LOIPRO03, the
BOM components in SAP Manufacturing Execution is enriched with assembly operations and
the respective information is displayed in the BOM Maintenance application.

Figure 51: Additional Integration Details: Routing With Allocated Document Info Records
Similar to assigning components to manufacturing operations, it is possible to attach

documents to routing operations in SAP ERP. The documents can, for example, contain
detailed information for the shop floor personnel explaining how to assemble a certain
component. When the order is transferred from SAP ERP to SAP Manufacturing Execution,
the SAPMEINT component creates or updates a routing, operation(s), and work instructions.
For each assigned document info set, a work instruction is created in SAP Manufacturing
Execution. However, at this point in time, the work instruction is not attached to the shop
order or operation. Only after the production order IDoc is received from SAP ERP, SAP
Manufacturing Execution updates the work instruction record. For document info records
that are assigned on order level in SAP ERP, (for example, documents maintained as a BOM
item or in the material master), SAPMEINT attaches the work instruction to the order. If
document info records are directly assigned to an operation (for example, as displayed in the
figure, where the T-D00 drawing is attached to the assembly operation), the respective work
instruction in SAP Manufacturing Execution is assigned to the respective operation of the
routing and the order.
Note that the original document is not transferred from SAP ERP to SAP Manufacturing
Execution when transferring the routing or order IDoc. Instead, a link is shipped to SAP
Manufacturing Execution and the operator can open the linked document directly in SAP ERP.
Routing Integration from SAP Manufacturing Execution to SAP ERP
Figure 52: Integration of the SAP Manufacturing Execution Routing to SAP ERP

It is also possible to create routings in SAP Manufacturing Execution and afterwards transfer
them to SAP ERP following the process shown in the figure. In the first step, the user creates
one or more operations in SAP Manufacturing Execution. Then, a routing is created and the
operations are linked in the routing. If the system rule Enable Replication of ME routing to ERP
system is set to true , all routings created in SAP Manufacturing Execution are transferred to
SAP ERP. However, if the system rule is set to false, only routings in SAP Manufacturing
Execution where the Replication to ERP indicator is set to yes are transferred to SAP ERP. The
third step of routing maintenance consists of assigning the routing as a default routing to one
or more materials in SAP Manufacturing Execution. This can either be done using the Routing
Maintenance or the Material Maintenance applications. Upon saving the material, the routing
data is exported using SAPMEINT and a routingExportRequest is created. This request calls a
BAPI CO_MES_ROUTING_CREATE_PUSH in SAP ERP which creates a routing for the
material. After successful creation, the user can allocate BOM components to the routing in
SAP ERP and use the routing to create a production order.
A user can execute various actions in SAP Manufacturing Execution, with respect to the
routing maintenance that creates a routing in SAP ERP:
A new routing R1 / version A is created in SAP Manufacturing Execution and assigned to a

material M1 / version A. After saving the material, SAPMEINT creates a new routing group
and task list inside the routing group with group counter 01.
Another material M2 / version A is assigned to the same routing R1 / version A. After

saving the material SAPMEINT creates a new routing group. Note that SAPMEINT does not
enhance the routing group created in the previous step by adding a new material. Instead,
for each material, a new routing group is created.
A second version B of routing R1 is created and attached to material M1 / version A. After

saving the material, SAPMEINT enhances the first routing group and creates a mew task
list inside the already existing routing group, for example with group counter 02. As the
material M2 / version A is explicitly attached to routing R1 / version A, the respective
routing group will not be affected by the routing update in SAP Manufacturing Execution.
In SAP ERP, on task list header level, information about the SAP Manufacturing Execution
routing is displayed if the routings were imported from SAP Manufacturing Execution to SAP
ERP using SAPMEINT. Note that it is also possible to enhance the created routing in SAP ERP
by implementing the BAdi CO_MES_INT_ROUTING_INBOUND.
In order to enable the replication of routing from SAP Manufacturing Execution to SAP ERP,
the ERP work centers must be available in SAP Manufacturing Execution. Furthermore, ERP
control keys must be set up using the Control Key Maintenance application. In the System
Rule Maintenance application, the following settings must be enabled:
ERP Integration Active = True

Enable Replication of ME Routing to ERP = True
Ignore Routing Update = True
Note that the replication of routings from SAP Manufacturing Execution to SAP ERP can be
configured globally on site level, or individually, for each routing. In the first case, the system
rule Ignore Routing Update must be set to True . In the latter case, the system rule can be set
to False, but for each routing, the respective replication indicator must be enabled. If SAP
Manufacturing Execution will be the leading system for routing maintenance, it makes sense
to set the system rule Ignore Routing Update to False. If an order IDoc is received containing a
routing, the routing coming from ERP is ignored by SAPMEINT and the routing maintained in
SAP Manufacturing Execution is used for the order.
LESSON SUMMARY

Unit 2
Learning Assessment
1. The material master IDoc MATMAS03 or MATMAS03 are structured into different
segments. Some segments occur only once while other segments occur multiple times.
X True
X False
2. In order to transfer long material numbers, the IDoc MATMAS03 must be used.
X True
X False
3. If the default IDoc processing logic is not sufficient, the following enhancement options
exist:
X A The default logic cannot be enhanced.
X B Customers can define their own processing logic.
X C Customers can use a processing logic developed by a partner.
4. If a MATMAS03/05 IDoc is received that contains information for multiple plants, the
SAPMEINT behaves as follows:
X A The same IDoc is forwarded to SAP Manufacturing Execution without any changes.
X B A split workflow reads the available sites in SAP Manufacturing Execution and
splits the original IDoc into one IDoc for each site.
X C If site-specific information from SAP ERP is received for a site that does not exist in
SAP Manufacturing Execution, the respective information is ignored.

5. Describe the data flow from SAP ERP to SAP Manufacturing Execution for the transfer of a
material master.
6. Discuss the change management functionality for the creation of a material master.
7. When material classification will be transferred, it is possible to trigger the respective IDoc
independently from the material master IDoc.
X True
X False
8. In SAP Manufacturing Execution, it is possible to define a header quantity in the BOM that
is different from 1 (in the unit of measure of the manufactured material).
X True
X False
9. The replication of a BOM from SAP ERP to SAP Manufacturing Execution is executed
using the Data Replication Framework (DRF).
X True
X False
10. Which of the following statements are correct?

X A When a BOM is transferred from SAP ERP to SAP Manufacturing Execution, the
BOM item quantities are normalized.
X B In SAPMEINT, a split workflow is executed if the BOMMAT03 IDoc is received from

SAP ERP.
X C When the BOMMAT03 IDoc is received, only a standard workflow executing an

XML transformation is executed by SAPMEINT.

11. Which of the following BOM item information can only be transferred together with the
production order?
X A Alternative components
X B By-products
X C Co-products
X D BOM with assembly operations
BOM.
13. Discuss the change management functionality for creation of a BOM.
14. When work centers in SAP Manufacturing Execution are updated with data from SAP ERP,
it is possible to automatically create a new work center version of an ERP field changed.
X True
X False
15. If work centers defined in SAP ERP will be automatically converted to SAP Manufacturing
Execution resources and work centers during data transfer, the IDoc type LOIWCS03
must be used.
X True
X False

16. If SAP ERP work centers have individual capacities assigned, SAPMEINT creates a work
center in SAP Manufacturing Execution for the ERP work center and resources for the
work center categories.
X True
X False
17. Which of the following prerequisites must be fulfilled to transfer a work center from SAP
ERP to a work center in SAP Manufacturing Execution?
X A ALE and DRF communication settings for the LOIWCS03 IDoc type must be set up.
X B The system rule setting ERP Integration Active in SAP Manufacturing Execution
must be set to false.
X C ERP Field Maintenance Settings must be done for the category Work Center.
X D ERP Field Maintenance Settings must be done for the category Resource.
18. Which of the following statements is correct?

X A SAPMEINT only allows to update the work center in SAP Manufacturing Execution.
X B When SAPMEINT receives a LOIWCS03 IDoc, a split and a standard workflow are
executed in order to split the work center data for each site.
X C When SAPMEINT receives a LOIWCS03 IDoc, only a standard workflow is

executed.
X D It is not possible to transfer Standard Value Keys from SAP ERP to SAP
19. If the standard logic for transferring work center data from SAP ERP to SAP
Manufacturing Execution is not sufficient, it is not possible for the customer to write their
own transaction to fulfill customer-specific requirements.
X True
X False
20. Discuss the logic of SAPMEINT when a LOIWCS03 IDoc is received.

21. Discuss why it is sufficient to execute a standard workflow when a LOIWCS03 IDoc is
received.
22. Explain the behavior of SAPMEINT if an individual capacity that is assigned to a work
center in SAP ERP is deleted and an IDoc with updated data is received.
23. If inspection characteristics are assigned to a routing operation maintained in SAP ERP,
the respective operation created in SAP Manufacturing Execution by SAPMEINT will
contain a data collection group with the respective parameters after import of the
LOIROU03 IDoc.
X True
X False
24. Routing information can be distributed using ALE or DRF.

X True
X False
25. Before a routing can be transferred from SAP ERP to SAP Manufacturing Execution, the
respective work centers must exist in SAP Manufacturing Execution.
X True
X False

26. Before a routing can be transferred from SAP ERP to SAP Manufacturing Execution, which
of the following master data objects must exist in SAP Manufacturing Execution?
X A Work Center
X B Resources
X C BOM
X D Materials
27. When a routing is created by SAPMEINT, a new routing version is created if which of the
following conditions apply?
X A Operation number was changed
X B Operation control key was changed
X C Operation short text was changed
X D Operation times were changed
X E BOM item to operation assignment was changed
28. In a system environment consisting of a SAP ERP system and a SAP Manufacturing
Execution system, which of the following routing maintenance options are available?
X A Maintenance of all routings in SAP ERP and replication to SAP Manufacturing

Execution
X B Maintenance of all routings in SAP Manufacturing Execution and replication to SAP

ERP
X C Maintenance of some routings in SAP ERP and some routings in SAP

X D All routings must be maintained either in the SAP ERP or the SAP Manufacturing
Execution system
29. Discuss the logic of SAPMEINT when a LOIROU03 IDoc is received.

30. Explain how the BOM component allocation to routing operations is transferred to SAP
31. Discuss the required process and settings if SAP Manufacturing Execution will be the
master system for routing maintenance and the routings will be transferred to SAP ERP.

Unit 2
1. The material master IDoc MATMAS03 or MATMAS03 are structured into different
segments. Some segments occur only once while other segments occur multiple times.
X True
X False
2. In order to transfer long material numbers, the IDoc MATMAS03 must be used.
X True
X False
3. If the default IDoc processing logic is not sufficient, the following enhancement options
exist:
X A The default logic cannot be enhanced.
X B Customers can define their own processing logic.
X C Customers can use a processing logic developed by a partner.
4. If a MATMAS03/05 IDoc is received that contains information for multiple plants, the
SAPMEINT behaves as follows:
X A The same IDoc is forwarded to SAP Manufacturing Execution without any changes.
X B A split workflow reads the available sites in SAP Manufacturing Execution and
splits the original IDoc into one IDoc for each site.
X C If site-specific information from SAP ERP is received for a site that does not exist in
SAP Manufacturing Execution, the respective information is ignored.

material master.
A user creates a new material master in SAP ERP by maintaining the required view. After
the material master has been created, the replication process is triggered and SAP ERP
creates an MATMAS05 IDoc, which is received by the SAPMEINT integration component
running on SAP Manufacturing Integration and Intelligence. In SAPMEINT, a split workflow
receives the IDoc, processes the data, and triggers one or more standard workflows. The
material data is received by a service transaction running in SAP Manufacturing Eecution
where a new material master is created by the service. After successful transfer, the user
can verify whether all of the fields and values have been transferred correctly. If so, the
created material master can be enriched on the SAP Manufacturing Execution side with
data that is only relevant for the manufacturing process.
6. Discuss the change management functionality for the creation of a material master.
The material master setup process only supports an update mechanism so that it is only
possible to update the current version of the material after a change is done in SAP ERP
and transferred to SAP Manufacturing Execution. In addition, it must be defined which
system is the master system for each field and the update rules must be set up
accordingly.
7. When material classification will be transferred, it is possible to trigger the respective IDoc
independently from the material master IDoc.
X True
X False
8. In SAP Manufacturing Execution, it is possible to define a header quantity in the BOM that
is different from 1 (in the unit of measure of the manufactured material).
X True
X False
9. The replication of a BOM from SAP ERP to SAP Manufacturing Execution is executed
using the Data Replication Framework (DRF).
X True
X False


X A When a BOM is transferred from SAP ERP to SAP Manufacturing Execution, the
BOM item quantities are normalized.
X B In SAPMEINT, a split workflow is executed if the BOMMAT03 IDoc is received from

SAP ERP.
X C When the BOMMAT03 IDoc is received, only a standard workflow executing an

XML transformation is executed by SAPMEINT.
11. Which of the following BOM item information can only be transferred together with the
production order?
X A Alternative components
X B By-products
X C Co-products
X D BOM with assembly operations
BOM.
Each BOM is transferred as a single level BOM, so any subassembly BOMs need to be
transferred over separately. A user creates a new master BOM in SAP ERP by maintaining
the BOM header and assigning BOM components. After the master BOM has been
created, the replication process is triggered and SAP ERP creates an IDoc (BOMMAT03)
executes data mapping. The BOM data is received by a service transaction running in SAP
Manufacturing Execution, where a new BOM is created by the service. After successful
transfer, the user can verify whether all of the fields and values have been transferred
correctly. If so, the created BOM can be enriched on the SAP Manufacturing Execution
side with data that is only relevant for the manufacturing process.
13. Discuss the change management functionality for creation of a BOM.
For BOMs, the scenarios update existing BOM, create a new BOM version, and ignore the
update are supported by SAP Manufacturing Execution. In addition, it must be defined
which of the two systems acts as a master for each field and the field update logic must be
configured accordingly.

14. When work centers in SAP Manufacturing Execution are updated with data from SAP ERP,
it is possible to automatically create a new work center version of an ERP field changed.
X True
X False
15. If work centers defined in SAP ERP will be automatically converted to SAP Manufacturing
Execution resources and work centers during data transfer, the IDoc type LOIWCS03
must be used.
X True
X False
16. If SAP ERP work centers have individual capacities assigned, SAPMEINT creates a work
center in SAP Manufacturing Execution for the ERP work center and resources for the
work center categories.
X True
X False
17. Which of the following prerequisites must be fulfilled to transfer a work center from SAP
ERP to a work center in SAP Manufacturing Execution?
X A ALE and DRF communication settings for the LOIWCS03 IDoc type must be set up.
X B The system rule setting ERP Integration Active in SAP Manufacturing Execution
must be set to false.
X C ERP Field Maintenance Settings must be done for the category Work Center.
X D ERP Field Maintenance Settings must be done for the category Resource.


X A SAPMEINT only allows to update the work center in SAP Manufacturing Execution.
X B When SAPMEINT receives a LOIWCS03 IDoc, a split and a standard workflow are
executed in order to split the work center data for each site.
X C When SAPMEINT receives a LOIWCS03 IDoc, only a standard workflow is

executed.
X D It is not possible to transfer Standard Value Keys from SAP ERP to SAP
19. If the standard logic for transferring work center data from SAP ERP to SAP
Manufacturing Execution is not sufficient, it is not possible for the customer to write their
own transaction to fulfill customer-specific requirements.
X True
X False
20. Discuss the logic of SAPMEINT when a LOIWCS03 IDoc is received.
The standard workflow LOIWCS03 receives the IDoc and executes a pre XSLT
manipulation to receive the standard value key details. Then, the mapping from SAP ERP
to SAP Manufacturing Execution is executed using a XSLT. In the next step, a Service
Transaction is called which creates a new work center. If the work center creation in SAP
Manufacturing Execution is successful, a generic success response is received.
21. Discuss why it is sufficient to execute a standard workflow when a LOIWCS03 IDoc is
received.
In SAP ERP, the work center is defined on plant level. Therefore, the respective IDoc does
not contain information for more than one plant, which is why the execution of a split
workflow is not required.
22. Explain the behavior of SAPMEINT if an individual capacity that is assigned to a work
center in SAP ERP is deleted and an IDoc with updated data is received.
If a capacity is removed from the work center in SAP ERP, the corresponding SAP
Manufacturing Execution resource is removed from work center members but still present
in the system. The resources status is automatically changed to disabled or pending,
depending on whether there is work done on the resource.

23. If inspection characteristics are assigned to a routing operation maintained in SAP ERP,
the respective operation created in SAP Manufacturing Execution by SAPMEINT will
contain a data collection group with the respective parameters after import of the
LOIROU03 IDoc.
X True
X False
24. Routing information can be distributed using ALE or DRF.

X True
X False
25. Before a routing can be transferred from SAP ERP to SAP Manufacturing Execution, the
respective work centers must exist in SAP Manufacturing Execution.
X True
X False
26. Before a routing can be transferred from SAP ERP to SAP Manufacturing Execution, which
of the following master data objects must exist in SAP Manufacturing Execution?
X A Work Center
X B Resources
X C BOM
X D Materials

27. When a routing is created by SAPMEINT, a new routing version is created if which of the
following conditions apply?
X A Operation number was changed
X B Operation control key was changed
X C Operation short text was changed
X D Operation times were changed
X E BOM item to operation assignment was changed
28. In a system environment consisting of a SAP ERP system and a SAP Manufacturing
Execution system, which of the following routing maintenance options are available?
X A Maintenance of all routings in SAP ERP and replication to SAP Manufacturing

Execution
X B Maintenance of all routings in SAP Manufacturing Execution and replication to SAP

ERP
X C Maintenance of some routings in SAP ERP and some routings in SAP

X D All routings must be maintained either in the SAP ERP or the SAP Manufacturing
Execution system
29. Discuss the logic of SAPMEINT when a LOIROU03 IDoc is received.
The standard workflow LOIROU03 receives the IDoc and an XSLT maps the ERP data
fields to SAP Manufacturing Execution data fields. In the next step, a Service Transaction
is called which creates a new routing and operations. If the creation in SAP Manufacturing
Execution is successful, a generic success response is sent.
30. Explain how the BOM component allocation to routing operations is transferred to SAP
In SAP Manufacturing Execution, there is no component assignment possible on routing

and on operation level. Instead, the assignment of components and operations is
maintained in the BOM. As BOM and routing are transferred independently from SAP ERP
to SAP Manufacturing Execution, it is not possible to transfer the assignment of
components to operations when transferring the routing. Instead, this information is
transferred together with the order in the LOIPRO03 IDoc.

31. Discuss the required process and settings if SAP Manufacturing Execution will be the
master system for routing maintenance and the routings will be transferred to SAP ERP.
In the first step, the user creates one or more operations in SAP Manufacturing Execution.
Then, a routing is created and the operations are linked in the routing. If the system rule
Enable Replication of ME routing to ERP system is set to true , all routings created in SAP
Manufacturing Execution are transferred to SAP ERP. The third step of routing
maintenance consists of assigning the routing as a default routing to one or more
materials in SAP Manufacturing Execution. This can either be done using the Routing
Maintenance or the Material Maintenance application. Upon saving the material, the
routing data is exported using SAPMEINT and a routingExportRequest is created. This
request calls a BAPI CO_MES_ROUTING_CREATE_PUSHin SAP ERP which creates a
routing for the material. After successful creation, the user can allocate BOM components
to the routing in SAP ERP and use the routing to create a production order.

UNIT 3 Production Order
Transactional Data
Integration
Lesson 1
Configuring Production Order Integration 81
Lesson 2
Configuring Floor Stock Integration 90
Lesson 3
Configuring Production Order Confirmations 98
UNIT OBJECTIVES
Understand the production order integration between SAP ERP and SAP Manufacturing
Execution
Understand the floor stock integration between SAP ERP and SAP Manufacturing
Execution
Understand the order integration between SAP ERP and SAP Manufacturing Execution

Unit 3
Lesson 1
Configuring Production Order Integration
LESSON OBJECTIVES
Execution
Production Order Integration Process
Figure 54: Production Order Integration Process
The figure displays the process and data flow of the order integration process. In SAP ERP, a
production order is created. After the order is released to production by executing a status
change, the order and the related data (for example routing, BOM, documents, quality
inspection data) is replicated to SAP Manufacturing Execution using an IDoc. The latter is
received by a standard workflow in SAPMEINT which transforms the IDoc data into order and
related data. Then, SAPMEINT calls a service transaction in SAP Manufacturing Execution
which creates the shop order and the related objects. Assuming that SAP ERP is the leading
system for all production-relevant master data (such as BOM and routing), SAP
Manufacturing Execution will use the data transmitted in the IDoc and map them to own
master data objects, as follows:
The SAP ERP routing is mapped to routing and operations in SAP Manufacturing
Execution.
The SAP ERP BOM is mapped to a BOM in SAP Manufacturing Execution.
In-process inspections in SAP ERP are mapped to data collections in SAP Manufacturing
Execution.

Unit 3: Production Order Transactional Data Integration
Document info records on order header and operation level in SAP ERP are mapped to
work instructions in SAP Manufacturing Execution.
If an order is updated in SAP ERP (for example quantity, date, status changes, and so on), a
new order IDoc is created and distributed to the MES system. This IDoc is received by the
same standard workflow and changes to the shop order are done in the SAP Manufacturing
Execution system. If changes to order data should not be possible, this can be done in any of
the following:
SAP ERP by preventing changes to the production order,
SAPMEINT by adapting the standard integration workflows, or
SAP Manufacturing Execution by setting (global or site-specific) system rules and ERP
field settings.
The detailed order update logic will be discussed later in this chapter.
Figure 55: Order Integration Scenario: SAP ERP vs. SAP Manufacturing Execution as Leading System
In the figure, two business scenarios are displayed. In the left scenario, SAP ERP is the leading
system for all production-relevant master data. On the right side, SAP Manufacturing
Execution is the leading system.
If SAP ERP is the leading system, production-relevant master data such as material, work
center, BOM and routing are transmitted from SAP ERP to SAP Manufacturing Execution
before releasing a production order. In SAP ERP, when creating a production order, the
routing and BOM are copied to that specific order. Any changes to routing and BOM after
creation of the order are usually not automatically transferred to the order. Therefore, the
order IDoc also contains BOM and routing data and it is optional to transfer BOM and routing
before transferring the order. When the order is released in SAP ERP by executing a status
change, an IDoc is triggered which replicates the order to SAP Manufacturing Execution.
During import, SAP Manufacturing Execution checks whether a respective routing and BOM
already exist. If they do not exist, a new routing and BOM are automatically created. If they
exist, the system compares the data and creates a new version, if significant data changes
were done on the ERP side. As a result, the shop order in SAP Manufacturing Execution will
always use the BOM and routing data as they were defined in SAP ERP. As a last step, the
production supervisor (partially or entirely) releases the order to the shop floor so that the
shop floor personnel can start working on the individual SFCs.

Lesson: Configuring Production Order Integration
If SAP Manufacturing Execution is the leading system, a minimum set of master data must be
transferred from SAP ERP to SAP Manufacturing Execution before the order can be imported.
After material master and work centers have been transferred using the respective IDocs, the
personnel responsible for master data maintenance can set up BOMs, operations, and
routings in SAP Manufacturing Execution for use in the subsequent production processes.
After all master data is set up, the order can be created and released in SAP ERP, which
triggers the data transfer to SAP Manufacturing Execution using an IDoc. In order to be able
to start working on the individual SFCs, the order must be released to the shop floor. As SAP
Manufacturing Execution is set up to be the leading system for BOM and routing, the BOM
and routing contained in the order IDoc are ignored during import. Instead, SAP
Manufacturing Execution references the current version of the BOM and routing as they are
maintained in SAP Manufacturing Execution for this new order. As a result, the shop order in
SAP Manufacturing Execution will not use the BOM and routing data as they are set up in SAP
ERP, but will use their own respective data. This business scenario is usually used if the
detailed production workflow is too complex to be set up in SAP ERP. In this case, in SAP ERP,
a more granular routing is set up that is sufficient to calculate (average) capacity
requirements to the individual work centers so that a realistic production plan can be created.
In SAP Manufacturing Execution, the detailed, complex, and realistic production workflow is
used for the execution of the order.
Technical Details
Figure 56: Routing IDoc LOIPRO03
In the figure, an excerpt of the IDoc type LOIPRO03 (which can be used for the transfer of
production orders from SAP ERP to SAP Manufacturing Execution) is displayed on the left
side. The segment E1AFKOL contains the order header which is saved in SAP ERP tables
AFKO and AUFK, respectively. The segment E1AFDFH contains document information sets
that are assigned on order header level. In SAP ERP, these documents can either originate
from the BOM, or they can be assigned on the material master level. The segment E1AFLL
contains the order sequences (table AFFL). For each sequence, a list of order operations is
provided in the E1AFVOL segment. For each operation in SAP ERP, a respective segment
entry exists. Finally, the two segments, E1AFDFO and E1RESBL, are transmitted as child
objects of the order operation segment E1AFVOL. The former segment contains document
information records that are assigned on operation level. The latter segment contains
reservations and dependent requirements, for example, component materials and their
respective quantities.

On the right side of the figure, an example IDoc that contains a production order for the
manufacturing of 30 pc of the T-F100 material is displayed. On the order header level, the
order number and type, the material, and the respective quantity, as well as BOM and routing
information, are stored. In the example, the order contains two operations (Component
Assembly and Quality Inspection). In the first operation, two components (T-B100 and T-
T300) must be assembled. The second operation does not contain any components.
As mentioned above, this IDoc is sent out by SAP ERP to the SAP Manufacturing Execution
system after the production order is created and released. In the latter system, SAPMEINT
receives the IDoc and triggers the creation of a shop order in SAP Manufacturing Execution.
Figure 57: MEINT Processing Logic for Production Order IDocs
The figure displays the detailed processing logic of SAPMEINT. A production order IDoc
LOIPRO03 is received. For each order, one IDoc is transferred from SAP ERP to SAPMEINT.
The message listener running on SAP Manufacturing Integration and Intelligence receives the
IDoc and triggers the standard workflow LOIPRO03. Technically, the IDoc has an XML
structure which can be manipulated using XSLT (Extensible Stylesheet Language
The standard workflow LOIPRO03 receives the IDoc and executes the pre XSLT
transformation
java:com.sap.me.integration.actions.workflow.inbound.productionorder.Pr
oductionOrderPreXSLT , which deletes quality-inspection information from the IDoc. Note
that this information is retrieved by SAP Manufacturing Execution at a later point in time.
Then, the request XSLT Visiprise/XSLT/Inbound/ProductionOrder/ECC60EHP5/
ProductionOrderRequestLOIPRO03.xslt that maps the ERP data fields to SAP
Manufacturing Execution data fields is executed. A post XSLT transformation
java:com.sap.me.integration.actions.workflow.inbound.OrderDateEnrichmen
t enriches the order data by converting date and time fields to the local SAP Manufacturing
Execution time zone and (optionally) releases the order to production. Finally, the Service
Transaction java:com.sap.me.integration.ERPProductionOrderHandler is
executed. This comprehensive service transaction not only creates a shop order in SAP
Manufacturing Execution, but also executes the BOM and routing comparison logic. If

required, new versions of the routing and BOM are created in SAP Manufacturing Execution. If
the creation in SAP Manufacturing Execution is successful, a generic success response XSLT
Visiprise/XSLT/Inbound/GenericResponse.xslt is sent. Note that the response
contains information about the used routing and BOM versions.
Note that customers can also enhance existing IDoc types and create new ones containing
If the order contains in-process quality inspection data, the system will create a data
collection group with the quality inspection data and link the data collection group to this shop
order. Similarly, ERP document info records that are received in the order IDoc and that are
stored in SAP Manufacturing Execution as work instructions will be linked to the shop order at
this stage.
In the Queue Monitor , the IDoc LOIPRO03 received from SAP ERP can be identified by an
identifier which corresponds to the scheme "<Plant (WERKS)> - Order Number (AUFNR)", for
example, 1000-60002889.
LOIPRO03 is chosen for the transfer of the production order. When using the DRF framework,
a production order that matches the DRF filter criteria (for example, plant and order type) is
automatically transferred from SAP ERP to SAP Manufacturing Execution.
On the SAP ERP side, the following prerequisites must be fulfilled in addition to the ALE and
DRF settings:
Material master records for the finished and component materials must be transferred to
SAP Manufacturing Execution.
Work centers referenced in the individual routing operations must be transferred to SAP

Manufacturing Execution. Furthermore, settings regarding the field update logic for the shop
order, routing, routing step (operation), and BOM must be set up. In the system, these
settings can be made using the ERP Field Maintenance application. Depending on whether
SAP ERP or SAP Manufacturing Execution is the leading system for the routing and BOM, the
respective master data objects must be available in SAP Manufacturing Execution. Note that
setting up routing, operations, and BOM in SAP Manufacturing Execution is optional, as the
data delivered via the LOIPRO03 IDoc can also be used instead. If default values will be taken
into account when importing the production order, these values must be set up using the
Default Value Maintenance application. Note that the values are only taken into account if the
respective fields are empty.
Figure 59: Import of the Production Order: When are Routings and BOMs Updated?
During the import of production order data to SAP Manufacturing Execution, SAPMEINT can
create a new BOM and/or routing version, or use the existing BOM and/or routing version.
The decision flow is shown in the schema in the figure. First, SAPMEINT determines the
current version of the material in SAP Manufacturing Execution and uses this version as the
version for the shop order. Then, the system rules Ignore BOM Update and Ignore Routing
Update are checked. If one of the two rules is set to true , the respective data sent with the
ERP order is ignored and the existing object (order or BOM) is linked. This scenario is often
used if SAP Manufacturing Execution is the leading system for BOMs and/or routings, for
example, if complex manufacturing routings are used to model the processes on the shop
floor which cannot be modeled in an ERP routing.
If the system rules are set to false, the system compares the order data with the existing
master routing and/or BOM. If the data in the order does not agree with the master data
available in SAP Manufacturing Execution, a new version of the respective object is created,
set as the current version and linked in the newly created shop order.
For BOMs, the following checks are performed for each BOM item:
Material number
Quantity
Components assignment to operations

If one of the attributes above does not agree with the Master BOM, a new BOM version is
created. In addition, the settings maintained in the ERP Field Maintenance application are
taken into account.
For routings, the following checks are performed for each operation:
Operation number
Operation text (Description)
If one of the attributes above does not agree with the Master Routing, a new routing version is
created. In addition, the settings maintained in the ERP Field Maintenance application are
taken into account.
Figure 60: Order Updates in SAP ERP
Depending on the settings in SAP ERP, (for example, activated business functions
LOG_PP_MES_INT_01 and LOG_PP_MES_INT_02), it is possible to restrict or allow making
changes to production orders that are already distributed to the manufacturing execution
system. If only the first business function is active in the customer system, a distributed order
can only be changed with restrictions, as it is only distributed once to the MES system. After
activating the second business function, LOG_PP_MES_INT_02, the restrictions are less
severe, as subsequent changes are distributed to the manufacturing execution system. Still,
basic restrictions (for example, reducing the order quantity) apply, as they are required to
guarantee consistent data exchange between SAP ERP and the manufacturing execution
system.
If customers would like to restrict the possible changes to an order in SAP ERP, two
enhancement possibilities are provided. By implementing the BAdI CO_MES_INT_FCODE, it is
possible to restrict the actions a user can execute for a distributed order. Actions usually
correspond to menu entries and button functions in the SAP ERP transactions. After
implementation of the BAdI CO_MES_INT_FIELDS, it is possible to restrict editing of individual
fields as a function of the distribution status. SAP delivers example implementations for both
BAdIs that can be used as a copy template by the application developer.
The following list contains some examples for how changes to a production order in SAP ERP
are mapped to SAP Manufacturing Execution:
When increasing the order quantity in SAP ERP, the quantity of the shop order will also be
increased in SAP Manufacturing Execution.
Setting the Technically Complete status in SAP ERP sets the Closed status of the
respective order in SAP Manufacturing Execution

Changing the operation sequence to a released order in SAP ERP puts the SFCs on hold in
SAP Manufacturing Execution. A respective hold reason code is applied to all SFCs of the
order. After reviewing all changes, the shop floor supervisor can release the hold status
using the SFC Release Holdapplication. Note that it might be required to route some SFCs
to a new operation which can be realized using the Change Production application.
As discussed in the previous figure, it is also possible to ignore updates to BOM and/or
routings by setting the respective system rules Ignore BOM Update and Ignore Routing
Update. If mapping is enabled and both system rules are set to false, then existing BOM and
routing records are updated in SAP Manufacturing Execution, according to the respective
Update Indicator field setting in the ERP Field Maintenance application. However, if the shop
order has been already released in SAP Manufacturing Execution and if the production has
already started (SFC numbers are Active ), the BOM and routing will not be updated
automatically and the shop floor supervisor might need to perform these updates manually
using the Change Production application.
Additional Order-Integration Processes
Figure 61: Additional Information (I)
In SAP ERP, the put-away storage location for the manufactured product is usually stored in
the material master. When creating a production order, this value is copied to the order and
then transferred to SAP Manufacturing Execution in the production order IDoc. In special
cases, it is possible to change the put-away storage location in the order. When the respective
order IDoc is transferred to SAP Manufacturing Execution, the changed put-away storage
location is stored on shop order level in SAP Manufacturing Execution. When executing the
last reporting step in a POD, the respective goods receipt of the final component is posted to
this storage location instead of to the default storage location that is maintained in the
material master.
As already stated above, the production order IDoc transferred from SAP ERP contains BOM
and routing information, as these values are copied from the master objects in SAP ERP to
the respective production order. During import, SAP Manufacturing Execution compares the
order BOM and routing to the already existing master records that might have been created
either by previous production orders or during master data synchronization. If the BOM
and/or routing match, (see the figure for a detailed description of the comparison algorithm),
the already existing master BOM and/or routing are referenced by the newly created shop
order. Otherwise, a new BOM and routing version are created and linked to the imported shop
order. Already existing orders are not affected as they continue referencing the old versions.

Figure 62: Additional Information (II)
In SAP ERP, it is possible to define an in-process quality inspection by enabling the inspection
type 03 in the material master in the production plant. Furthermore, qualitative and
quantitative inspection characteristics must be defined in the routing operations. During
import, SAP Manufacturing Execution creates a data collection group for each routing
operation with assigned inspection characteristics. For each characteristic, a corresponding
parameter in the data collection group is created. Depending on the characteristic type
(quantitative or qualitative), a respective parameter type (Numeric, Boolean, or Data Field
List) is created. The data collection groups are then assigned on order / routing / routing step
level so that the shop floor personnel can capture quality-relevant data during production
using the Data Collection POD plugin. Depending on the inspection scenario which is
determined by the sampling procedure (100% sampling or partial sampling), the inspection
valuation either occurs in SAP Manufacturing Execution (100% sampling) or in ERP (<100 %
sampling).
If SAPMEINT receives a production order IDoc containing Document Info Records, respective
work instructions will be created in SAP Manufacturing Execution and linked to the shop
order, (documents on header level of the order), or a combination of shop order / routing /
routing step (documents on operation level). Note that the document is not transferred to
SAP Manufacturing Execution. Instead, a link to the document is saved in the respective work
instruction. If the shop floor operator displays the work instruction in the POD, the document
can be opened using a link.
LESSON SUMMARY
Execution

Unit 3
Lesson 2
Configuring Floor Stock Integration
LESSON OBJECTIVES
Execution
Inventory Processes
Figure 63: Transfer of Floor Stock Data: The Process in Inventory Management
In SAP Manufacturing Execution, the following two strategies for the integration of goods
movements between SAP ERP and SAP Manufacturing Execution are possible:
Synchronize goods movement between a central storage location to a production storage

location
Synchronize goods issue to the production order
In both cases, the respective goods movements will be synchronized from SAP ERP to SAP
Manufacturing Execution using DRF, and create a Floor Stock record in SAP Manufacturing
Execution.
The figure illustrates both processes. Components are stored in a central warehouse at a
central storage location, for example, L099. Once required by manufacturing, the production-
relevant components are transferred from the central storage location to a production
storage location, for example, 0001. Here, the components are stored short-term and in a
smaller quantity for a timely consumption by manufacturing processes. In SAP ERP, this
process corresponds to goods movements inside a plant from one storage location to another
one. The respective goods movements (movement type 311 in the SAP standard) are
synchronized between SAP ERP and SAP Manufacturing Execution. In the latter system, the

Lesson: Configuring Floor Stock Integration
goods movement is received via an IDoc and creates a floor stock ID for the respective
component. Note that the respective goods movement is independent from any production
order. Therefore, the floor stock cannot be pegged to a production order and can therefore be
consumed by any shop floor order. This process variant is often used for bulk components
that must be available at the production site in sufficient quantity, for example, screws. When
the components are consumed during the production process, for example, during
component assembly, the respective component consumption is reported back to SAP ERP
together with the production confirmation where a component consumption against the
production order (movement type 261 in the SAP standard) is recorded. At the same time, the
SAP Manufacturing Execution inventory record is decreased by the consumed amount.
The alternative process variant is displayed in the lower section of the process diagram. Here,
components are consumed by a production order, for example, during component staging
from the central storage location (for example, L099) for a production order. In SAP ERP, this
process corresponds to a goods issue to a production order (movement type 261 in the SAP
standard). Upon consumption, the inventory in SAP ERP of the respective component is
reduced by the consumed amount and the value of the respective component is added to the
production order. The corresponding goods movement is synchronized between SAP ERP
and SAP Manufacturing Execution using an IDoc. In the latter system, the IDoc creates a floor
stock record for the respective component. Note that, as the goods issue is specific to a
production order, the respective inventory record is pegged against a specific production
order and SAP Manufacturing Execution can ensure that the respective floor stock ID can only
be consumed for that specific production order. This process variant is often used for high-
priced components, or if a full component traceability is required, for example in regulated
production processes for medical devices. When the components are physically consumed
during the production process in SAP Manufacturing Execution, for example during
component assembly, the respective component consumption is not reported back to SAP
ERP together with the production confirmation as, on the SAP ERP side, the respective
component was already consumed against the production order. However, in SAP
Manufacturing Execution, the respective floor stock record is decreased by the consumed
quantity.
Order-Independent Floor Stock Replenishment
Figure 64: Floor Stock Replenishment Process
In the figure, the process and data flow of the floor stock replenishment process is displayed.
In SAP ERP, a goods movement from the central storage location to the production storage
location is triggered. Technically, this corresponds to a goods movement of type 311 in the
SAP standard. The goods movement is replicated using an IDoc and received by a standard

workflow in SAPMEINT, which transforms the IDoc data into inventory data. Then, SAPMEINT
calls a service transaction in SAP Manufacturing Execution which creates the respective
inventory record. The inventory record contains information about the issuing and the
receiving storage location, respectively, and the material document identifier created in SAP
ERP. However, as the goods movement is not specific to any production order, the respective
inventory record in SAP Manufacturing Execution is not pegged against an order.
When an SFC is completed at an operation where the respective component is assembled and
the required inventory data is recorded in the POD, the confirmation data is sent from SAP
Manufacturing Execution through SAPMEINT to SAP ERP using a BAPI call. The BAPI call
posts the component consumption for the production order which corresponds to a goods
movement of type 261 against a production order in the SAP standard. A time ticket
confirmation for the production order operation is created in SAP ERP.
Figure 65: Return and Scrap in the Floor Stock Replenishment Process
In the figure, the process and data flow for returning not required inventory back to the
central storage location as well as the related scrapping process is displayed for the floor
stock replenishment process. In SAP Manufacturing Execution, the quantity on hand of the
respective inventory record is changed with a reason code. The reason code can either
indicate a return or a scrap of the component. For returns, SAPMEINT executes a BAPI call in
SAP ERP and reverses the goods movement from the central storage location to the
production storage location by posting a respective goods movement reversal. Technically,
this corresponds to a goods movement of type 312 in the SAP standard, which cancels the
original goods movement of type 311. For scraps, SAPMEINT also executes a BAPI call and
posts the component scrap against a cost center. In the SAP standard, this corresponds to a
goods movement of type 511. The respective cost center is maintained in SAP Manufacturing
Execution in the respective reason code in a custom data field. Note that it is possible to
create multiple reason codes in SAP Manufacturing Execution. Reason codes starting with the
prefix RTN- trigger a component return, whereas reason codes with the prefix SCR- trigger a
scrap.

Order-Specific Floor Stock Consumption
Figure 66: Production-Order Specific Consumption Process
In the figure, the process and data flow of the production-order specific consumption process
is displayed. In SAP ERP, a component consumption from any storage location against a
production order is triggered. Technically, this corresponds to a goods movement of type 261
with respect to a production order in the SAP standard. The goods movement is replicated
using an IDoc and received by a standard workflow in SAPMEINT, which transforms the IDoc
data into inventory data. Then, SAPMEINT calls a service transaction in SAP Manufacturing
Execution, which creates the respective inventory record. The inventory record contains
information about the issuing and the receiving storage location, respectively, and the
material document identifier created in SAP ERP. In addition, as the goods movement is
specific to a production order, the respective inventory record in SAP Manufacturing
Execution is pegged against this order.
When an SFC is completed at an operation where the respective component is assembled and
the required inventory data is recorded in the POD, the confirmation data is sent from SAP
Manufacturing Execution through SAPMEINT to SAP ERP using a BAPI call. The BAPI call
creates a time ticket confirmation for the production order operation in SAP ERP. However, a
posting of the consumed component is not required at this process step, as the goods issue
of the component to the production order already took place. Note that following the Order-
Specific Floor Stock Consumption process variant, a temporary inconsistency between SAP
ERP and SAP Manufacturing Execution inventory records for components might occur as the
component is already consumed in SAP ERP, but might only be consumed in SAP
Manufacturing Execution if the respective assembly operation is completed.

Figure 67: Return and Scrap in the Production-Order Specific Consumption Process
In the figure, the process and data flow for returning not required inventory back to the
central storage location as well as the related scrapping process is displayed for the
production-order specific consumption process. In SAP Manufacturing Execution, the
quantity on hand of the respective inventory record is changed with a reason code. The
reason code can either indicate a return or a scrap of the component. For returns, SAPMEINT
executes a BAPI call in SAP ERP and reverses the goods issue posting to the production order
by posting a respective goods movement reversal. Technically, this corresponds to a goods
movement of type 261 in the SAP standard which cancels the original goods movement of
type 261. For scraps, SAPMEINT also executes a BAPI call and posts the component scrap
against a cost center. In the SAP standard, this corresponds to a goods movement of type
511. However, due to the fact that the respective component was already consumed in SAP
ERP at goods issue to the production order, the additional reversal posting of the goods issue
to the production order is required before the scrap posting against the cost center can be
performed. Technically, the reversal posting corresponds to a goods movement of type 262 in
the SAP standard.
As for the previous process, the respective cost center is maintained in SAP Manufacturing
Execution in the respective reason code in a custom data field. Note that it is possible to
create multiple reason codes in SAP Manufacturing Execution. Reason codes starting with the
prefix RTN- trigger a component return, whereas reason codes with the prefix SCR- trigger a
scrap.

Technical Details
Figure 68: Routing IDoc INVCON02
In the figure, an excerpt of the IDoc type LOIROU03 (which can be used for the transfer of
routings from SAP ERP to SAP Manufacturing Execution) is displayed on the left side, with the
top segments E1MAPLL and E1MAPAL, which are used to transfer the material-to-plan
assignment as well as the plans lot size. The segment E1PLKOL contains the task list header
with, for example, the task list unit of measure, the short text, and the validity date. If long
texts are maintained on the header level of the routing, this information is included in the
E1PLLTH segment. The task list sequence segment E1PLFLL contains one E1PLPOL segment
for each production operation in the routing. If PRTs are assigned to an operation, this
information is transferred using the E1PLDOC segment of the IDoc. If BOM items are assigned
on operation level, (not shown in this example), the IDoc contains the additional segment
E1PLMZL as a child of the E1PLPOL segment.
On the right side of the figure, an example IDoc that contains the routing for the
manufacturing of the material T-F100 is displayed. On the top, the material (T-F100) that is
assigned to the routing (plan group 500000276) is displayed. The routing is only valid for the
manufacturing of one to 999 pc. However, note that this information is not taken into account
by SAP Manufacturing Execution, as the routing in SAP Manufacturing Execution is not lot-
size dependent. The routing contains one production operation (10 / Component Assembly)
with detailed information such as setup, machine, and labor time, respectively. In addition, a
PRT (document) is assigned to this operation.
Manufacturing Execution system, for example, after the production routing for material T-
F100 in plant 1000 is created and released. In the latter system, SAPMEINT receives the IDoc
and triggers the creation of a new routing and the related operations in SAP Manufacturing
Execution.

Figure 69: MEINT Processing Logic for Material Document IDocs
The figure displays the detailed processing logic of SAPMEINT. A material document IDoc
INVCON02 is received. For each material document, one IDoc is transferred from SAP ERP to
SAPMEINT. The message listener running on SAP Manufacturing Integration and Intelligence
receives the IDoc and triggers the standard workflow INVCON02_INV_PEG. Technically, the
IDoc has an XML structure which can be manipulated using XSLT (Extensible Stylesheet
database, that can then be used in the subsequent XSLT. In addition to the default pre XSLT
logic.
The standard workflow INVCON02_INV_PEG receives the IDoc and executes the pre XSLT
transformation Visiprise/ERPShopFloorIntegration/workflow/
InventoryReceiptWithPegging/BatchCharsEnrichment , which enriches the data with
batch characteristic data by executing a BAPI call to SAP ERP. Then, the request XSLT
Visiprise/XSLT/Inbound/InventoryReceipt/InventoryReceiptRequest.xslt
that maps the ERP data fields to SAP Manufacturing Execution data fields is executed. In the
next step, the Service Transaction
java:com.sap.me.integration.ERPInventoryReceiptHandler is called which
creates a floor stock record per material document item. If the creation in SAP Manufacturing
Execution was successful, a generic success response XSLT Visiprise/XSLT/Inbound/
InventoryReceipt/InventoryReceiptResponse.xslt is sent.
Note that customers can also enhance existing IDoc types and create new ones containing
In the Queue Monitor , the IDoc INVCON02 received from SAP ERP can be identified by an
identifier which corresponds to the scheme "<Plant (WERKS)> - Material Document", for
example, 1000-490001023.
In the case of returns and scrap movements triggered by SAP Manufacturing Execution, the
standard workflow maintainInventoryRequest is executed, which calls the SAP ERP BAPI
BAPI_GOODSMVT_CREATE. Based on the entered reason code, the respective movement
type (for example 311, 262, or 551) is passed to the BAPI. In the Queue Monitor , the workflow
identifier corresponds to the naming scheme "<Site>-<Storage Location of Floor Stock> -
<Shop Order>".

Prerequisites and Required Settings
In the ALE settings, the IDoc type INVCON02 is selected for transmitting material document
IDocs. Furthermore, the respective DRF filter parameters (for example, plant and movement
type) must be set up so that only the material document IDocs that are relevant to SAP
Manufacturing Execution are automatically transmitted. When using DRF, transactional data
is usually automatically transmitted upon saving the respective data record. There is no
report scheduling required. In addition, in order to be able to create inventory records for the
respective materials in SAP Manufacturing Execution, the material masters must have been
transferred from SAP ERP to SAP Manufacturing Execution.
On the SAP Manufacturing Execution side, the ERP integration must be activated and the
receiving storage locations must be set up using the Storage Location Maintenance
application. As the system creates inventory IDs for each goods movement, the numbering
patterns for the floor stock receipt must be set up. This can either be done per material group
or on material level. The data types INV or INV_SFC of the Assembly category must contain
the required data fields, for example, INVENTORY_ID or INVENTORY_ID_SFC. In the material
master of all components, the user must assign the data type ERP_INV_RCPT_DATA as Data
to Collect on Floor Stock Receipt . The respective data type provides the required fields, for
example Material Document, where data from SAP ERP is mapped to. If the shop floor
personnel will record the assembled inventory ID during component assembly, the data type
INV or INV_SFC must be assigned as Data to Collect on Assembly . By assigning this data type,
the system requires the shop floor operator to provide the used inventory ID where the
component was taken from. Following this approach, the system can also check the pegging
relationship between the inventory record and the shop order.
LESSON SUMMARY
Execution

Unit 3
Lesson 3
Configuring Production Order Confirmations
LESSON OBJECTIVES
Production Order Confirmations - Overview
Figure 71: Production Order Completions: Overview
If an SFC moves through the different production operations, collaboration messages are
sent from SAP Manufacturing Execution to SAP ERP. The figure displays an example process
flow, showing the manufacturing process of the SFC 10043 of the T-F100 material. At the
ASSEMBLY-00 operation, the component material T-B100 (for example, casing) is
assembled into the SFC. The control key PP01 is flagged as ERP reporting relevant. Therefore,
when the SFC is completed, a Yield Confirmation request is triggered that sends information
about the assembly operation (for example, operation yield) to SAP ERP (1). As a component
is consumed, the consumption of the component T-B100 is also included in the request.
In the next step (QUAL-INSP-00), a quality inspection is executed. Due to the control key
settings, a Yield Confirmation is triggered when the SFC is completed at this step (2). As there
are no components consumed, no component consumption is transmitted to SAP ERP. After
the SFC completes the PACKAGING-00 operation (3), a respective Yield Confirmation with a
component consumption for component T-B900 is sent. Now, the SAP Manufacturing
Execution system checks whether all SFC of this order are completed. If this is the case, a
Production Order Complete request is also triggered that sets the final confirmation flag for all
operations of the order in SAP ERP.

Lesson: Configuring Production Order Confirmations
In case of a nonconformance, the SFC can also be routed to the REPAIR-00 operation after
completing the QUAL-INSP-00 operation. The control key of the REPAIR-00 operation is not
flagged as ERP reporting relevant. Therefore, no Yield Confirmation request is triggered when
the SFC is completed at this operation.
SAPMEINT Processing Logic
Figure 72: MEINT Processing Logic for Production Order Yield Confirmations
In the figure, the detailed processing logic of SAPMEINT is displayed. Upon operation
confirmation, SAP Manufacturing Execution triggers the collaboration link
COLLABORATION_ERP_YIELD_CONFIRMATION which is linked to the
ERP_YIELD_CONFIRMATION directive in SAP Manufacturing Execution standard (see the
Collaboration Link Maintenance application). The collaboration message is enriched with
additional data by the pre XSLT transaction
java:com.sap.me.integration.actions.workflow.outbound.ConfirmationDateE
nrichment and contains data about the completed operation (for example, order and
operation numbers, SFC number, SFC quantity, and the consumed components). The XML
document is transformed from SAP Manufacturing Execution data structure to SAP ERP data
structure by executing the request XSLT Visiprise/XSLT/Outbound/Confirmation/
ECC60EHP5/YieldConfirmation/YieldConfirmationRequest.xslt . Then, the service
transaction Visiprise/ERPShopFloorIntegration/frame/workflow/
StdSAPBAPIHandler with the parameter CO_MES_PRODORDCONF_CREATE_TT is called.
The parameter passed to the service transaction corresponds to the name of the BAPI that is
called in SAP ERP to post the time ticket confirmation. Afterwards, the BAPI response
received from SAP ERP is converted using the response XSLT Visiprise/XSLT/Outbound/
Confirmation/ECC60EHP5/ConfirmationResponse.xslt .
In case of success, a time ticket confirmation for the operation of the respective order is
created. If the confirmation message also contains component consumption, a respective
material document with movement type 261 corresponding to a goods issue to a production
order is created.
In case of an error, the workflow calls a fail handler Visiprise/
ERPShopFloorIntegration/workflow/Confirmation/
SAPMEAlarmConfirmationYieldFailureHandler which creates an alarm in the
SAPMEINT Queue Monitor that sends an alarm message to SAP Manufacturing Execution.
Here, the failed collaboration can be analyzed in the Collaboration Log Report application.

Note that in order to be able to see error messages in the log, the respective indicator in the
collaboration directive must be set.
In the Queue Monitor , the request can be identified by an identifier which corresponds to the
scheme "<Site> - <Order> - <Operation> - <SFC>", for example,
1000-60002887-0010-10008.
When the operation is marked as Last Reporting Step, the yield confirmation request
transmits the final confirmation indicator to SAP ERP and, in addition, a goods receipt of the
final product. In this case, the BAPI call creates a time ticket confirmation as for the other
reporting steps and a goods receipt (movement type 101) for the process order.
Figure 73: MEINT Processing Logic for Production Order Completion
In the figure, the detailed processing logic of SAPMEINT is displayed. If a) the production
order status changes to done (as all SFCs of the order are completed at the last reporting
step) or b) the production order status is changed to Closed, SAP Manufacturing Execution
triggers the collaboration link COLLABORATION_SHOPORDER_COMPLETE which is linked to
the ERP_SO_COMPLETE directive in SAP Manufacturing Execution standard (see the
Collaboration Link Maintenance application). The collaboration message is enriched with
additional data by the pre XSLT transaction Visiprise/ERPShopFloorIntegration/
workflow/ProductionOrderComplete/OperationEnrichment which calls the BAPI
BAPI_PRODORD_GET_DETAIL in SAP ERP to retrieve the reporting steps of the order. The
XML document is transformed from the SAP Manufacturing Execution data structure to the
SAP ERP data structure by executing the request XSLT Visiprise/XSLT/Outbound/
ProductionOrderComplete/ProductionOrderCompleteRequest.xslt . Then, the
service transaction Visiprise/ERPShopFloorIntegration/frame/workflow/
StdSAPBAPIHandler with the parameter BAPI_PRODORDCONF_CREATE_TT is called. The
parameter passed to the service transaction corresponds to the name of the BAPI that is
called in SAP ERP to post the order completion. When the order completion is posted, the
Final Confirmation and the Clear Reservation flags are set for all reporting-relevant operations.
After the BAPI call is executed, the BAPI response received from SAP ERP is converted using
the response XSLT Visiprise/XSLT/Outbound/ProductionOrderComplete/
ProductionOrderCompleteResponse.xslt .
In the Queue Monitor , the request can be identified by an identifier which corresponds to the
scheme "<Site> - <Order>", for example, 1000-60002887.

Technical Prerequisites
In order to enable the transfer of operation and order confirmations from SAP Manufacturing
Execution to SAP ERP, several prerequisites must be fulfilled, both in SAP Manufacturing
Execution and SAP ERP.
In SAP ERP, the control keys that are used by the respective manufacturing operations must
not trigger automatic goods receipt for the produced goods, as SAP Manufacturing Execution
explicitly reports the delivery of the final product in the last reporting step. Furthermore, it
must be possible to confirm operations. The confirmation of milestone operations in SAP ERP
automatically also confirms the previous operations. In an SAP ERP SAP Manufacturing
Execution environment, operation confirmations are explicitly sent by the manufacturing
execution system, therefore, it is not possible to use milestone operations in orders that are
executed using SAP Manufacturing Execution. In SAP ERP, it is also possible to enforce an
order check when confirming operations. If enabled, the SAP ERP system raises a message if
an operation is confirmed, although the predecessor is not. This must not be enabled for the
order types that are sent to SAP Manufacturing Execution.
In SAP Manufacturing Execution, the collaboration links and directives must be set up. This is
usually done during system setup. Furthermore, production orders must be imported from
SAP ERP to SAP Manufacturing Execution and the corresponding SFCs must be released to
the shop floor in order to be able to process them in the operator POD. In order to start a
collaboration event, the SAP Manufacturing Execution routings must contain at least one
reporting step that is ERP reporting relevant. Note that it is not required that all steps are
flagged as reporting relevant. However, it is recommended to always set the last operation of
a routing as reporting relevant in order to ensure that all of the data is transferred back to SAP
ERP correctly.
Message Correlation and Separate Material Movements
Figure 75: Alternative Approaches

For each completed operation, SAP Manufacturing Execution sends a yield confirmation
request that can contain component consumptions and goods receipts. In addition, for each
completed order, a respective completion request is sent. In a high-frequency production
environment, this might lead to a lot of correlation messages that are exchanged between
SAP Manufacturing Execution and the SAP ERP system. In order to take load from the
interface, it is possible to correlate individual messages. Furthermore, a high amount of
messages might lead to locking issues in SAP ERP, if, for example, the system tries to post an
operation confirmation for two operations of the same order at the same time. If correlation is
used for operations (orders), yieldConfirmationCorrelationRequest
(productionOrderCompleteCorrelationRequest ) messages are triggered. SAPMEINT monitors
the number of messages and their respective queue time. If either the number of messages is
equal to a parameter set up when configuring the system, or a maximum waiting time is
reached, the individual messages are bundled together in a
CorrelatedYieldConfirmationRequest (CorrelatedProductionOrderCompleteRequest ) and sent
to SAP ERP. If correlation is used on operation level, it is also recommended to enable this
feature on order level, to ensure that the messages are processed in the correct sequence.
In the default setup, goods movements for components are sent together with the respective
operation confirmation from SAP Manufacturing Execution to SAP ERP. In order to prevent
lockings, it is also possible to separate the operation yield confirmation from the related
goods issue posting. If SAP Manufacturing Execution is configured in such a way, the
component consumption is reported to SAP ERP by sending a separate
componentAddRequest message after the shop floor operator has assembled the respective
component in the POD. Technically, the SAP ERP BAPI MB_MES_BAPI_GOODSMVT_CREATE
is called to post the goods movement for the component consumption.
Both settings are usually made when the SAP Manufacturing Execution system is set up. For
detailed configuration steps, refer to the SAP Manufacturing Execution Integration guide,
which is published on the SAP Manufacturing Execution application help page.
Scrap and Rework
Figure 76: Unplanned Events: Scrap and Rework
Unplanned events, for example scrap and rework, can occur during production. The figure
displays two SFC flows. On the left side, an SFC is assembled in the ASSEMBLY-00 step.
Then, a quality inspection operation is executed where it is discovered that the SFC is faulty
and needs to be scrapped (1). On the right side, a quality inspection operation is executed and
the operator decides that it is possible to repair the SFC. Therefore, the SFC is routed to a
repair operation (2). After the repair operation, the SFC is routed back again to the quality
inspection operation (3), where the quality inspection is performed a second time (4).

If the operator or the supervisor decide to scrap the SFC, a respective

scrapConfirmationRequest is triggered (1) and the following data are sent to SAP ERP:
Plant
Order and operation
Quantity that has been scrapped
Assembled components (optional)
When received in SAP ERP, a time ticket confirmation for the respective operation is created
with scrap. If components were consumed to assemble the defect product, the respective
component consumption is also transferred and goods issue positing against the order is
executed.
In SAP Manufacturing Execution, scrapping of an SFC can either be automatically triggered by
logging an NC code with the appropriate configuration, or manually using the SFC Scrap/
Delete activity.
If the operator or the supervisor decide to repair the SFC in a repair loop, a yield confirmation
is sent to SAP ERP each time when the SFC is completed at the quality inspection operation
(2 and 4). For the second and all following yield confirmations of the same SFC, SAP
Manufacturing Execution sends a respective flag to SAP ERP so that the rework counter can
be incremented accordingly. For each pass of the quality inspection, if components are
assembled, the respective component consumption is transmitted to SAP ERP in the yield
confirmation message.
Note the following special process flows:
The yield confirmation is always executed if an operation is completed. For example, if the
SFC is moved from the repair to the quality inspection step (4) without completing the
repair step, for example, using a NC code routing, and the quality inspection step is
completed (4), the yield confirmation contains data about this step. No information about
the repair step is transferred to SAP ERP.
A scrap confirmation message is always sent, irrespective of whether the corresponding

step is marked as an ERP reporting step. For example, let us assume that the SFC is
completed at the quality inspection step (2) and sent to the repair step. At the repair step,
the SFC is directly routed back to the quality inspection step without completing the repair
step (4). If the SFC is now scrapped at the second pass of the quality inspection step (4),
the respective scrap message is sent for the repair (4) step and not for the quality
inspection step (4).
LESSON SUMMARY

Unit 3
Learning Assessment
1. When a production order is updated in SAP ERP, it is not possible to synchronize the
changes to SAP Manufacturing Execution.
X True
X False
2. Setting the Technically Complete status on order level in SAP ERP sets the shop order
status to Closed in SAP Manufacturing Execution.
X True
X False
3. If SAP ERP is the leading system for BOM and routing, SAPMEINT tries to merge the
master data transmitted in the LOIPRO03 IDoc with data that already exist in SAP
X True
X False

4. Which of the following statements regarding order integration between SAP

Manufacturing Execution and SAP ERP are correct?
X A If an SAP ERP production order contains a put-away storage location that differs
from the one maintained in the material master, an error message is raised in the
SAPMEINT integration queue when posting the goods receipt of the finished product.
X B If an SAP ERP production order contains a put-away storage location that differs
from the one maintained in the material master, the goods receipt is posted to this
storage location.
X C If a production order contains information about in-process quality inspection, a

data collection group with respective parameters is created by SAPMEINT.
X D When contained in a LOIPRO03 IDoc, document info sets are transferred

completely to SAP Manufacturing Execution, including the documents, so that no
connection to SAP ERP is required in order to display the documents.
5. Discuss the merge logic that is applied by SAP Manufacturing Execution when a
production order IDoc with routing and BOM is received.
6. Explain how it is possible to restrict changes to the production order in SAP ERP.
7. In the production order specific component consumption process, the time ticket
confirmation contain yield confirmations and component consumptions.
X True
X False
8. In the floor stock replenishment process, the time ticket confirmation contain yield
confirmations and component consumptions.
X True
X False

9. It is only possible to use one of the two inventory integration processes per site in SAP
X True
X False
10. Which of the following statements are correct for scrap and return postings in the
production-order specific consumption process?
X A Inventory changes with a return reason code trigger a reversal of the good issue to
the production order.
X B Inventory changes with a scrap reason code trigger only a reversal of the goods
issue to the production order.
X C Inventory changes with a scrap reason code trigger only a scrapping goods
movement.
X D Inventory changes with a scrap reason code trigger a reversal of the goods issue to
the production order, followed by a scrapping goods movement.
11. Which of the following statements are correct for scrap and return postings in the floor
stock replenishment process?
X B Inventory changes with a return reason code trigger a storage location to storage
location goods movement.
movement against a cost center.
X D The cost center is maintained on reason code level.
12. Discuss the processing logic of the production order specific consumption process.
13. Discuss the SAPMEINT processing logic for Material Document IDocs.

14. If all SFCs of an order are completed at the last ERP reporting relevant step, a Production
Order Complete request is sent out from SAP Manufacturing Execution to SAP ERP.
X True
X False
15. The last operation of a production routing must always be marked as ERP reporting
relevant.
X True
X False
16. If an SFC moves through a production operation more than once, a yield confirmation
request is only sent out for the first pass of the SFC through the operation.
X True
X False

X A During yield confirmation request, a component consumption can be transmitted

to SAP ERP.
X B It is possible to separate the yield confirmation from the component consumption.
X C At the last reporting relevant step, a goods receipt message against the process
order is sent to SAP ERP.
X D It is possible to use Milestone Operations in routings in SAP ERP.
X E It is possible to use control keys allowing Automated Goods Receipt when a SAP
ERP production order is executed in SAP Manufacturing Execution.


X A A scrap confirmation request is sent together with a yield confirmation request.
X B A scrap confirmation request is sent separately from a yield confirmation request,

but only if the respective production operation is completed.
X C A scrap confirmation request is sent separately from a yield confirmation request.

It is not necessary to complete the respective manufacturing operation.
19. Discuss the SAPMEINT processing logic of a production operation yield confirmation.
20. Explain when messages are sent from SAP Manufacturing Execution to SAP ERP while the
SFC moves through the manufacturing process.

Unit 3
1. When a production order is updated in SAP ERP, it is not possible to synchronize the
changes to SAP Manufacturing Execution.
X True
X False
2. Setting the Technically Complete status on order level in SAP ERP sets the shop order
status to Closed in SAP Manufacturing Execution.
X True
X False
3. If SAP ERP is the leading system for BOM and routing, SAPMEINT tries to merge the
master data transmitted in the LOIPRO03 IDoc with data that already exist in SAP
X True
X False

4. Which of the following statements regarding order integration between SAP

Manufacturing Execution and SAP ERP are correct?
X A If an SAP ERP production order contains a put-away storage location that differs
from the one maintained in the material master, an error message is raised in the
SAPMEINT integration queue when posting the goods receipt of the finished product.
X B If an SAP ERP production order contains a put-away storage location that differs
from the one maintained in the material master, the goods receipt is posted to this
storage location.
X C If a production order contains information about in-process quality inspection, a

data collection group with respective parameters is created by SAPMEINT.
X D When contained in a LOIPRO03 IDoc, document info sets are transferred

completely to SAP Manufacturing Execution, including the documents, so that no
connection to SAP ERP is required in order to display the documents.
5. Discuss the merge logic that is applied by SAP Manufacturing Execution when a
production order IDoc with routing and BOM is received.
First, SAPMEINT determines the current version of material in SAP Manufacturing

Execution and uses this version as the version for the shop order. Then, the system rules
Ignore BOM Update and Ignore Routing Update are checked. If one of the two rules is set
to true , the respective data sent with the ERP order is ignored and the existing object
(order or BOM) is linked. If the system rules are set to false, the system compares the
order data with the existing master routing and/or BOM. If the data in the order does not
agree with the master data available in SAP Manufacturing Execution, a new version of the
respective object is created, set as the current version, and linked in the newly created
shop order.
6. Explain how it is possible to restrict changes to the production order in SAP ERP.
If customers would like to restrict the possible changes to an order in SAP ERP, two
enhancement possibilities are provided. By implementing the BAdI CO_MES_INT_FCODE,
it is possible to restrict the actions a user can execute for a distributed order. Actions
usually correspond to menu entries and button functions in the SAP ERP transactions.
After implementation of the BAdI CO_MES_INT_FIELDS, it is possible to restrict editing of
individual fields as a function of the distribution status. SAP delivers example
implementations for both BAdIs that can be used as a copy template by the application
developer.

7. In the production order specific component consumption process, the time ticket
confirmation contain yield confirmations and component consumptions.
X True
X False
8. In the floor stock replenishment process, the time ticket confirmation contain yield
confirmations and component consumptions.
X True
X False
9. It is only possible to use one of the two inventory integration processes per site in SAP
X True
X False
10. Which of the following statements are correct for scrap and return postings in the
production-order specific consumption process?
X B Inventory changes with a scrap reason code trigger only a reversal of the goods
issue to the production order.
movement.
X D Inventory changes with a scrap reason code trigger a reversal of the goods issue to
the production order, followed by a scrapping goods movement.

11. Which of the following statements are correct for scrap and return postings in the floor
stock replenishment process?
X B Inventory changes with a return reason code trigger a storage location to storage
location goods movement.
movement against a cost center.
X D The cost center is maintained on reason code level.
12. Discuss the processing logic of the production order specific consumption process.
In SAP ERP, a component consumption from any storage location against a production
order is triggered. The goods movement is replicated using an IDoc and received by a
standard workflow in SAPMEINT, which transforms the IDoc data into inventory data.
Then, SAPMEINT calls a service transaction in SAP Manufacturing Execution which
creates the respective inventory record. The inventory record contains information about
the issuing and the receiving storage location, respectively, and the material document
identifier created in SAP ERP. In addition, as the goods movement is specific to a
production order, the respective inventory record in SAP Manufacturing Execution is
pegged against this order. When an SFC is completed at an operation, the confirmation
data is sent from SAP Manufacturing Execution through SAPMEINT to SAP ERP using a
BAPI call. The BAPI call creates a time ticket confirmation for the production order
operation in SAP ERP. However, a posting of the consumed component is not required at
this process step, as the goods issue of the component to the production order already
took place.
13. Discuss the SAPMEINT processing logic for Material Document IDocs.
The standard workflow INVCON02_INV_PEG receives the IDoc and executes a pre XSLT
transformation which enriches the data with batch characteristic data by executing a BAPI
call to SAP ERP. Then, a request XSLT maps the ERP data fields to SAP Manufacturing
Execution data fields. In the next step, a Service Transaction creates a floor stock record
per material document item. If the creation in SAP Manufacturing Execution was
successful, a generic success response XSLT is sent.

14. If all SFCs of an order are completed at the last ERP reporting relevant step, a Production
Order Complete request is sent out from SAP Manufacturing Execution to SAP ERP.
X True
X False
15. The last operation of a production routing must always be marked as ERP reporting
relevant.
X True
X False
16. If an SFC moves through a production operation more than once, a yield confirmation
request is only sent out for the first pass of the SFC through the operation.
X True
X False

X A During yield confirmation request, a component consumption can be transmitted

to SAP ERP.
X B It is possible to separate the yield confirmation from the component consumption.
X C At the last reporting relevant step, a goods receipt message against the process
order is sent to SAP ERP.
X D It is possible to use Milestone Operations in routings in SAP ERP.
X E It is possible to use control keys allowing Automated Goods Receipt when a SAP
ERP production order is executed in SAP Manufacturing Execution.


X A A scrap confirmation request is sent together with a yield confirmation request.
X B A scrap confirmation request is sent separately from a yield confirmation request,

but only if the respective production operation is completed.
X C A scrap confirmation request is sent separately from a yield confirmation request.

It is not necessary to complete the respective manufacturing operation.
19. Discuss the SAPMEINT processing logic of a production operation yield confirmation.
First, a pre XSLT transaction is executed that enriches the message collaboration
message with additional data. Using an XSLT request, the fields are mapped from SAP
Manufacturing Execution to SAP ERP. Then, a generic service transaction is called that
calls a BAPI in SAP ERP for posting a time ticket confirmation, together with goods issue
and goods receipt against a production order. In case of an error, a fail handler raises an
error message that can be displayed in the Queue Monitor .
20. Explain when messages are sent from SAP Manufacturing Execution to SAP ERP while the
SFC moves through the manufacturing process.
If an operation is marked as ERP reporting relevant, a yield correlation message is

triggered when the SFC completes the respective operation. If all SFCs of an order are
completed, a order complete correlation message is sent. In addition, scrapping an SFC
also triggers a message to SAP ERP.

SCM740 - EN - Col01 SAP ERP Integration With SAP Manufacturing Execution

Uploaded by

Copyright:

Available Formats

You might also like

SCM740 - EN - Col01 SAP ERP Integration With SAP Manufacturing Execution

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SCM740 - EN - Col01 SAP ERP Integration With SAP Manufacturing Execution

Uploaded by

Copyright:

Available Formats

SAP ERP Integration with SAP

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

© Copyright. All rights reserved. iii

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iv

1 Unit 1: Master Data Setup for Production in SAP Manufacturing

2 Lesson: Working With Work Centers and Resources in SAP

32 Unit 2: Master Data Integration

33 Lesson: Configuring Material Master Integration

80 Unit 3: Production Order Transactional Data Integration

81 Lesson: Configuring Production Order Integration

© Copyright. All rights reserved. v

Super / Key / Power User

© Copyright. All rights reserved. vi

Understand the purpose of using work centers

Understand the purpose of using resources

Understand the purpose and settings of operations

Understand the purpose and settings of routings

Understand the usage of in-line work instructions

Explain the purpose of using materials and its settings

© Copyright. All rights reserved. 1

Understand the purpose of using work centers

Understand the purpose of using resources

Work Center and Resource Overview

Figure 1: Work Centers and Resources in SAP Manufacturing Execution

Determination of the granularity of the work in progress (WIP) reports

To control where a product is released

© Copyright. All rights reserved. 2

A resource is defined as a machine or other piece of equipment used to perform an operation.

Figure 2: Work Centers in SAP Manufacturing Execution

© Copyright. All rights reserved. 3

Figure 3: Resources in SAP Manufacturing Execution

As already stated, a resource is a machine or piece of equipment that performs work at an

© Copyright. All rights reserved. 4

Use Cases for Nesting and Sequencing

Figure 4: Nesting Work Centers and Resources

© Copyright. All rights reserved. 5

Figure 5: Sequencing Resources Within a Work Center

It is possible to set up a hierarchical structure of work centers and resources in order to

Understand the purpose of using work centers

Understand the purpose of using resources

© Copyright. All rights reserved. 6

Understand the purpose and settings of operations

Understand the purpose and settings of routings

Understand the usage of in-line work instructions

Figure 6: Properties of Production Operations

© Copyright. All rights reserved. 7

or BENCH3-00 as the resource. Furthermore, ERP-related data is displayed if the operation

Figure 7: Example: Setting up an Routing by Leveraging Operation Building Blocks

© Copyright. All rights reserved. 8

Figure 8: Properties of Routings

© Copyright. All rights reserved. 9

Routings with Branches, Repair Loops, and Dependent Steps