SAP OEE 15.1 Help

CUSTOMER
Document Version: 15.1.5 – 2017-07-10
SAP Overall Equipment Effectiveness Management

Content
1 SAP Overall Equipment Effectiveness Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 OEE Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 User Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SAP ERP Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OEE Integration and Services (JAVA Layer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SAP HANA Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.4 OEE Customizing Settings in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
1.5 Master Data in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creating Global Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creating Plant Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creating Plant Reason Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.6 ERP-Shop Floor Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
ERP-Shop Floor Integration Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Integration of Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Integration of Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Integration of Transaction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1.7 SAP OEE CTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
SAP OEE NetWeaver Configuration CTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
SAP OEE Integration Configuration CTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
SAP OEE Configuration CTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Re-executing CTC Wizards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
CTC to Setup OEE Demo Plant Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
CTC for Archiving OEE Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
1.8 Configurations in SAP MII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
SAP MII Configurations for ERP-Shop Floor Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Transport OEE Configurations (SAP MII). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
1.9 Configurations for Worker UIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Configuring Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuring Order Status Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configuring User Administration Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring User Group and Dashboard Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configuring Customized Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuring Reason Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuring Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2 CUSTOMER Content
Configuring Scheduled Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Uploading OEE Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configuring Custom Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring Order Dispatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Display SAP ERP Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring Plant Maintenance Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
1.10 OEE Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Operator Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
1.11 Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
1.12 Plant-level Reporting and Analytics in OEE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configurations for OEE Lumira Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
1.13 Apps on Application Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Configuration of GI-GR apps with EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Configurations for Good Issue and Goods Receipt Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
1.14 Automatic Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Custom Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Back-End Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Content CUSTOMER 3
1 SAP Overall Equipment Effectiveness
Management
Use
SAP Overall Equipment Effectiveness Management (SAP OEE Management) allows you to measure and analyze
plant performance both in real-time and historically. It utilizes common sources of manufacturing data to obtain
metrics that enable you to measure availability and performance of equipment and the quality of goods produced
by that equipment.
Implementation Considerations
The OEE solution utilizes the following software components:
Table 1:
Software Component Dependent Software Component
OEE_ERP 15.0 SP03 SAP ERP 6.0/6.0X
For more information, see 1804140
OEE_MII 15.1 For more information, see the Installation Guide for SAP MII at
http://help.sap.com SAP Manufacturing Integration and
Intelligence 15.1 Installation and Upgrade Information .
HCO_HBA_OEE 1.0 SP06 SAP HANA Analytics Foundation 1.0 SP02
SAP HANA 1.0 SP05 revision 51 or higher
HCO_HBA_APPS_OEE 1.0 SP06 SAP HANA 1.0 SP05 revision 51 or higher
SAP HANA Analytics Foundation 1.0 SP02
HCO_HBA_OEE 1.0 SP06
SAP OEE application consists of the following functional building blocks:
● Customizing settings and master data in SAP ERP

● ERP-shop floor integration framework
● OEE dashboards, which includes dashboard configuration and access
● Custom actions in SAP MII for automated data collections
● Analytics and reports

4 CUSTOMER SAP Overall Equipment Effectiveness Management
Features
The SAP OEE application has the following features:
● Allows collection of all kinds of production losses and data collections that can be beyond the OEE classical
key performance indicator (KPI) definitions.
● OEE dashboards enable collection of OEE-relevant production data such as downtimes, quantities, reason
codes, and so on.
● Provides an out-of-the-box integration between SAP ERP, shop floor (SAP MII) and analytics (SAP HANA)
systems.
● Analytics and charts that focus on OEE and production loss related KPIs. Drill down capability to enable root
cause analysis of losses gives you an insight into the reasons for the losses.
You also have the flexibility to customize the analytical reports.
For more information, see SAP Note 1834144 .
● Enables extensions of the dashboards and analytics as per your requirements.
1.1 System Landscape
Use
This section contains information about the system landscape requirements for OEE.

SAP Overall Equipment Effectiveness Management CUSTOMER 5
Process
Typical OEE system landscape is depicted as follows:
Figure 1: SAP OEE System Landscape
1. You create the configurations and master data for SAP OEE in the SAP ERP system. SAP OEE is a non-
modifying add-on for maintaining the master data and is enabled for SAP S/4HANA.
For more information, see OEE Customizing Settings in SAP ERP [page 25] and Master Data in SAP ERP
[page 26].
2. The master data required for the analytics is copied to the SAP HANA system using SAP Landscape
Transformation (SLT). The integration is provided by SAP OEE.
3. The master and configuration data required for the shop floor execution is transferred to the shop floor SAP
MII systems. The replication is done through IDocs.
For more information, see the topics under the section ERP-Shop Floor Integration [page 31].
4. SAP OEE provides Central Technical Configuration (CTC) templates to perform the required configuration
settings for SAP NetWeaver, SAP OEE Integration framework, and OEE dashboards. For more information on
the OEE CTCs, see topics under the section SAP OEE CTC [page 62].
5. Production data is collected through the OEE dashboards provided by SAP OEE.
For more information, see OEE Dashboard [page 107].
Data can also be collected automatically through plant systems. For this, you must configure your Plant
Connectivity (PCo) and SAP MII systems.
For more information, see Automatic Data Collection [page 127].

6. Analytics can be performed on the collected data. For this, the data is initially stored in the local SAP MII
system and then transferred to the central SAP HANA database. SAP OEE provides a list of standard charts
and reports to analyze the data available in SAP HANA system. The collected data, however, remains stored
in the SAP MII system.
For more information, see http://help.sap.com Technology Platform SAP HANA Live Application
Help SAP HANA Live for Manufacturing .
1.2 OEE Calculations
Definition
OEE is a key performance indicator (KPI) that provides an insight into the efficiency of your manufacturing
processes. It is a product of other manufacturing KPIs.
OEE = Availability X Performance X Quality
where,
● Availability: The ratio of amount of time a resource was actually productive to the amount of time the resource
was available to be productive. The Availability KPI is derived from the granular elements such as Loading
Time, Unscheduled Downtime, and Net Production Time.
● Performance: The ratio of the actual speed with the designed speed. The Performance KPI is derived from
granular elements such as Net Production Time, Speed Loss, and Net Operating Time.
● Quality: The ratio of good product produced to the amount of total product produced. The Quality KPI is
derived from the granular elements such as Net Operating Time, Quality Loss, and Value Operating Time.
OEE and its constituent KPIs are calculated using production or process order-operation data converted into
terms of time.
SAP OEE application uses the basic elements, as shown in the following diagram, required for calculating OEE and
its KPIs.

Use
Figure 2: OEE Data Elements
OEE data elements are categorized into elements that are reported and elements that are derived from the
reported elements. The elements can be defined as follows:
1. Total Production Time: This is a calculated element. It is the total time available considering 24 hours in a day
and all seven days as working.
2. Flow Time: This is a reported element. Flow time is the time taken between the start of an order and the first
finished product. Impact on KPIs is similar to that of Scheduled Down.
If you want to consider flow time in OEE KPI calculations, configure a data collection element for flow time in
the Customizing activity Define Data Collection Element in SAP ERP and transfer this to SAP MII. You can then
report flow time when reporting downtimes from the OEE dashboard.
3. Changeover: This is a reported element. Changeover is the duration used to perform activities required for a
changeover event when different products are produced on the line. Impact on KPIs is similar to that of
Scheduled Down.
4. Scheduled Down: This is a reported element. The OEE application considers the holidays maintained in the
factory calendar and shift pattern definitions. The holiday calendar needs to be loaded manually using the
downtime maintenance screen.
Shift breaks are considered in OEE KPI calculations if you enable the Use Shift Break option while configuring
the plant hierarchy.
For more information, see Configuring Scheduled Downtime [page 101].

5. Loading Time: This is a calculated element. This is the time between the start and end of an order. In the SAP
OEE application, the start and the end of the order is reported from the shop floor. The reported time excludes
the durations of the scheduled downs. It also excludes the times when the order was on hold.
6. Unscheduled Down: This is a reported element. In the SAP OEE application it consists of all the unplanned
downtimes reported from the shop floor. The unplanned downtimes effective in the downtime calculations are
based on the line behavior and bottleneck behavior defined in your system.
For more information, see Configuring Customized Values [page 88]
7. Net Production Time: This is a calculated element. It is the duration obtained after deducting the
unscheduled downtimes from the loading time.
This element divided by the Loading Time is the Availability KPI and is a factor in calculating the OEE KPI.
8. Speed Loss: This is a reported element. It is the duration obtained after deducting the time that would have
been required to produce the same quantity at nominal speed from the actual time taken to produce the
reported production quantity.
9. Net Operating Time: This is a calculated element. It is duration obtained after deducting speed loss from the
net production time. This element divided by the Net Production Time is the Performance KPI and is a factor
in calculating the OEE KPI
10. Quality Loss: This is a reported element. It is the time taken to produce the rejected quantities, considering
they were produced at nominal speed. In the SAP OEE application, this element is reported from the shop
floor using the operator dashboard or automatically using Plant Connectivity (PCo).
11. Value Operating Time: This is a calculated element. It is the duration obtained after deducting quality loss
from the net operating time. This element divided by the Net Operating Time is the Quality KPI and is a factor
in calculating the OEE KPI.
For more information, see the documentation for the following Customizing activities in SAP ERP under
Production Overall Equipment Effectiveness :
● Define Data Element Types

● Define Data Elements
● Define Data Collection Contexts
● Define Data Collection Elements
● Define KPIs
More Information
OEE Customizing Settings in SAP ERP [page 25]
Configuring Activities [page 74]
1.3 User Roles and Authorizations
Definition
The actions that a user can perform depend on the permissions assigned to the user’s role.

Therefore you create roles and assign the appropriate actions to these roles. You then assign the roles to users in
the appropriate systems.
More Information
You can find authorization related information in the following:
● SAP ERP Layer [page 10]

● OEE Integration and Services (JAVA Layer) [page 11]
● SAP HANA Layer [page 23]
1.3.1 SAP ERP Layer
Definition
This section contains information about the OEE-relevant authorization objects for the software component
OEE_ERP 15.0.
Use
You create a role containing all the necessary OEE-relevant authorization objects and maintain appropriate values
for the fields of the authorization objects. You create the required roles in Role Maintenance (transaction code
pfcg) and assign the relevant authorization objects to the roles. You associate the relevant activities to the
authorization objects.
You then assign the role to users or user groups who can create, update, or maintain OEE configuration data or
master data in ERP. You can assign the roles you created to users through User Maintenance (transaction code
su01).
The OEE authorization objects to be assigned to your roles to access OEE transactions and perform create,
delete, update, display, or execute operations on them are:
1. Cross application authorization object

S_TCODE
This is the authorization object to the following OEE transactions:
○ /OEE/BO_IDOC: OEE IDoc Selection report (see OEE IDoc Selection) [page 42]
○ /OEE/GLOBAL_HIER: Creating Global Hierarchy (see Creating Global Hierarchy [page 26])
○ /OEE/PLANT_HIER: Creating Plant Hierarchy (see Creating Plant Hierarchy [page 27])
○ /OEE/PLANT_RC: Creating Plant Reason Codes (see Creating Plant Reason Codes [page 30])
○ /OEE/RC_EXCELUPLOAD: Uploading Reason Codes Through MS-Excel (see the note mentioned in
Creating Plant Reason Codes [page 30])
○ /OEE/PLANT_HIER_UPLD: Uploading Plant Hierarchy Data Through MS-Excel (see the note mentioned in
Creating Plant Hierarchy [page 27])

2. Basis: Administration
○ S_TABU_DIS
Authorization object for display and change authorization on maintenance views.
Activity: Display, Change.
Table authorization group: *
○ S_TABU_LIN
Authorization object for organizational criterion on maintenance views.
Activity: All activities.
Organizational criterion for key: OEE_RC_PLANT
Org. Crit. Attribute 1: List of plants for which user should have all authorization for reason code
maintenance.
3. OEE Authorization Check
○ /OEE/C_MGH
Authorization object for create, change, display authorization on global hierarchy.
OEE hierarchy template: List of templates for which user has authorization on global hierarchy
operations.
Activity: Create or generate, display, change, delete.
○ /OEE/C_MPH
Authorization object for create, change, display authorization on plant hierarchy.
Plant: List of plants for which user has authorization on plant hierarchy operations.
○ /OEE/IDOC
Authorization object to execute the OEE IDoc Selection report.
Activity: Execute
○ /OEE/C_PRC
Authorization to create reason codes using MS-Excel upload.
Plant: List of plants for which the user has authorization to upload reason codes through MS-Excel.
○ OEE/C_GRC
Authorization to create reason codes using MS-Excel upload.
1.3.2 OEE Integration and Services (JAVA Layer)
Definition
This section contains information about the SAP OEE-relevant authorizations for the software component
OEE_MII 15.1.
Use
SAP OEE uses the authorization concept provided by SAP NetWeaver. Therefore, the recommendations and
guidelines for authorizations as described in the SAP NetWeaver Application Server Java Security Guide apply to
SAP OEE.

The SAP NetWeaver authorization concept is based on assigning authorizations to users depending on their roles.
For role maintenance, use the user administration console in the SAP User Management Engine in SAP ERP.
Note
For more information about how to create roles, see Creating Authorization Roles in the SAP NetWeaver 7.3
Library help at http://help.sap.com/nw73 .
In SAP OEE, transaction data is segregated according to the client and plant. Users can perform set of operations
depending on the client and plant they are responsible for. You can grant user access to client and plant by
assigning a User Management Engine (UME) user group in Admin Configuration User Group Assignment and User
Group Dashboard Assignment. You can make these assignments through the Worker UI Management section on
the SAP MII main menu screen.
For more information, see Configuring User Administration Group [page 86] and Configuring User Group and
Dashboard Assignment [page 87].
When users log on to the OEE dashboard for the first time, they are automatically logged on to one of the plants
configured in the system based on the records available in Supported Plants.
To be able to assign a specific configuration to a user in UME, first create a default client, plant, work unit, and
dashboard fields in SAP NetWeaver as follows:
1. In Identity Management, choose Configuration.

2. In the Configuration screen, choose the User Administrator UI tab page and choose Modify Configuration.
3. In the Administrator-Management Custom Attributes field, enter the following data SAPOEE:DEFAULT
CLIENT; SAPOEE:DEFAULT PLANT; SAPOEE:DEFAULT WORKUNIT; SAPOEE:DEFAULT POD; SAPOEE:ERP
PERSONNEL NUMBER.
4. Save your entries.
After you have created the default field, you can assign default site to a user as follows:
1. Log on to SAP NetWeaver as administrator user.

2. Navigate to Identity Management and select user that you want to assign default site to.
3. Choose Modify. On the Customized Information tab page, enter values for the following fields:
○ Default Client
○ Default Plant
○ Default Work Unit
○ Default Dashboard
5. Repeat these steps for each user.
Note
If you create the default fields in SAP NetWeaver UME, but do not define default field values for the user in UME
User Configuration, on the first logon user will be redirected to what comes first alphabetically in the list where
this user is defined.

SAP OEE delivers the following actions:
Table 2:
Action Type Description
OEEProductionRun_Read Transaction Action to enable read of shift related

data collection header data.
OEEReleaseDemand_Read Transaction Action to enable read of operation level

demand data.
OEEReportDowntime_Read Transaction Action to enable read of reported down

times.
OEEDataCollection_Read Transaction Action to enable read of reported data

collection.
OEEProductionOrder_Read Transaction Action to enable read of production or

der.
OEEProductionRun_Operator Transaction Action to enable read and change pro

duction activity
OEEProductionRun_Create_Update Transaction Actions to enable create and update of

shift related data collection header data.
This is required close a shift.
OEEReleaseDemand_Create_Update Transaction Actions to enable create and update of

operation level demand data. This is re
quired to do close order
OEEProductionRun_All Transaction Action to enable all operation on shift re

lated data collection header record.
OEEReleaseDemand_All Transaction Action to enable all operation on opera

tion level demand data.
OEEReportDowntime_All Transaction Action to enable all operation for report

down times.
OEEDataCollection_All Transaction Action to enable all operation for data

collection and report all quantity.
OEEProductionOrder_All Transaction Action to enable all operation for pro

duction order.
OEEQueueMonitor_All Transaction Action to enable create, read, update,

and delete of entries in the OEE integra
tion queue.
OEEQueueMonitor_Read Transaction Action to enable read of OEE integration

queue.

OEEScheduledDown_Create Transaction Action to enable create of scheduled

downtime.
OEEWorkflowConfig_All Configuration Action to enable create, read, update,

and delete of workflow configurations.
OEEWorkflowConfig_Read Configuration Action to enable read of workflow config

urations.
OEEGlobalConfig_All Configuration Action to enable create, read, update,

and delete of global configurations.
OEEGlobalConfig_Read Configuration Action to enable read of global configu

rations.
OEESupportedPlants_All Configuration Action to enable create, read, update,

and delete of the supported plants.
OEESupportedPlants_Read Configuration Action to enable read of the supported

plants.
OEEActivity_Read Configuration Action to enable read of activity configu

ration.
OEEPod_Read Configuration Action to enable read of dashboard con

figuration.
OEEUserGroupPodAssignment_Read Configuration Action to enable read of user group

dashboard assignment.
OEECustomizationName_Read Configuration Action to enable read of customization

name.
OEECustomizationValue_Read Configuration Action to enable read of customization

value.
OEEConfigUserGroupAssignment_Re Configuration Action to enable read of users who have

ad authorization to assign user groups to
dashboard.
OEEUserGroupAssignment_Read Configuration Action to enable read of user group as

signment.
OEEScheduledDown_Read Configuration Action to enable read of schedule down.
OEEStatus_Read Configuration Action to enable read of status configu

ration.

OEEActivity_All Configuration Action to enable all operation on activity.

It is required to create and update activi
ties.
OEEPod_All Configuration Action to enable all operation on dash

board. It is required to create and update
dashboards.
OEEUserGroupPodAssignment_All Configuration Action to enable all operation on user

group dashboard assignment. It is re
quired to assign dashboard to a user
group.
OEECustomizationName_All Configuration Action to enable all operation on cus

tomization name. It is required to create
and update customization names and
their allowed values.
OEECustomizationValue_All Configuration Action to enable all operation on cus

tomization value. It is required to create
and update customization values and
their details.
OEEConfigUserGroupAssignment_Al Configuration Action to enable assignment of authori

l zation to users, who in turn can assign
user groups to dashboards.
OEEUserGroupAssignment_All Configuration Action to enable all operation on user

group assignment. This is required to as
sign users the authorization to perform
user group dashboard assignment.
OEEScheduledDown_All Configuration Action to enable all operation on sched

uled down maintenance. This is required
to create and update scheduled downs.
OEEStatus_All Configuration Action to enable all operation on status.

This is required to create and update
status configurations.
OEEExtension_All Configuration Action to enable all operation on exten

sion maintenance.
OEEMasterConfiguration_Read Configuration Action to enable read of SAP ERP mas

ter and configuration objects.
OEEReasonCodeMapping_Read Configuration Action to enable read of assigned reason

codes in configuration.

OEEReasonCodeMapping_All Configuration Action to enable permissions to assign

or delete assignment of reason codes in
configuration.
OEEErpConfirmations_Read Configuration Action to enable read of confirmation re

lated data.
OEEErpConfirmations_All Configuration Action to enable permission to send con

firmations.
OEEExtension_Read Configuration Action to enable read of extensions

maintained.
OEEIntegrationIdoc_All Configuration Action to enable execution of IDocs.
OEEIntegrationReconcileIdoc_All Configuration Action to enable reconcile IDocs.
OEESAPIntQuery_All Configuration Action to enable all permissions for SAP

integration query object.
SAP OEE delivers the following roles and their associated actions:
Table 3:
Role Name Description Associated Actions
OEE_OPERATOR Assign this role to the operator who OEEProductionRun_Operator

would do all data collection using opera
tor dashboard. OEEReportDowntime_All
This role has all authorization to report OEEDataCollection_All

production, rejection, and other data col
lection. The role also has authorization OEEProductionOrder_All
to report downtimes and uptimes on a
work unit. OEEExtension_Read
The role, however, has only read authori OEEReasonCodeMapping_Read

zation on configuration data.
OEEStatus_Read
OEEScheduledDown_Read
OEEUserGroupPodAssignment_Read
OEEUserGroupAssignment_Read
OEEConfigUserGroupAssignment_Re
ad
OEEProductionOrder_Read

OEECustomizationValue_Read
OEEPod_Read
OEECustomizationName_Read
OEEActivity_Read
OEEProductionRun_Read
OEEReleaseDemand_Read
OEEQueueMonitor_Read
OEESupportedPlants_Read
OEEWorkflowConfig_Read
OEEGlobalConfig_Read
OEEMasterConfiguration_Read
OEEReasonCodeMapping_Read
OEEERPConfirmations_All
OEE_SUPERVISOR Assign this role to a supervisor who has OEEProductionRun_Create_Update

additional authorizations to start, stop,
resume, close shift, and complete order. OEEReleaseDemand_Create_Update
The role also has the required authoriza OEEReportDowntime_All

tion on some configuration activities.
OEEDataCollection_All
OEEProductionOrder_All
OEEExtension_Read
OEEStatus_Read
ad

OEEPod_Read
OEEActivity_Read
OEE_ADMIN This role is for allowing access to OEE OEEActivity_All

configuration screens.
OEEPod_All
OEEUserGroupPodAssignment_All
OEECustomizationName_All
OEECustomizationValue_All
OEEConfigUserGroupAssignment_Al
l
OEEUserGroupAssignment_All
OEEScheduledDown_All
OEEStatus_All
OEEReasonCodeMapping_All
OEEExtension_All
OEEQueueMonitor_All
OEESupportedPlants_All

OEEWorkflowConfig_All
OEEGlobalConfig_All
OEEReasonCodeMappingAll
OEEErpConfirmations_All
OEEExtension_Read
OEE_SUPERADMIN This role has all authorizations. This role OEEProductionRun_All

also has some specific actions to set up
user group admin for specific plants. OEEReleaseDemand_All
OEEReportDowntime_All
OEEActivity_All
OEEUserGroupPodAssignment_All
OEEUserGroupAssignment_All
OEEScheduledDown_All
OEECustomizationName_All
OEECustomizationValue_All
OEEExtension_All
OEEStatus_All
OEEPod_All
OEEQueueMonitor_All
OEESupportedPlants_All
OEEWorkflowConfig_All
OEEGlobalConfig_All
OEESAPIntQuery_All

OEE_INTEGRATOR This role is for enabling the integration OEEIntegrationIdoc_All

from ERP to OEE.
OEEIntegrationReconcileIdoc_All
OEEReleaseDemand_Create_Update
OEEExtension_Read
OEEStatus_Read
ad
OEEPod_Read
OEEActivity_Read
OEEProductionRun_Read
OEEReleaseDemand_Read
OEEProductionRun_Operator
OEEReportDowntime_All
OEEQueueMonitor_All

OEESAPIntQuery_All
OEEScheduledDown_Create
OEE_READ_ONLY This role is to allow a user to see all the OEEProductionRun_Read

data on the dashboard. However, no re
porting or editing is possible. OEEReleaseDemand_Read
OEEReportDowntime_Read
OEEDataCollection_Read
OEEExtension_Read
OEEStatus_Read
ad
OEEPod_Read
OEEActivity_Read

OEEERPConfirmations_Read
SAP OEE also delivers the following users by default:
1. OEE_ADMIN: This user has the OEE_SUPERADMIN role to start the initial setup.
2. OEE_INTEGRATOR: This user has the OEE_INTEGRATOR role that can be used in integration configuration.
These users are also assigned SAP MII and SAP NetWeaver roles required to perform relevant administrative
tasks.
SAP MII roles assigned are:
● SAP_XMII_Administrator
● SAP_XMII_User
● SAP_XMII_Developer
● SAP_XMII_DynamicQuery
● SAP_XMII_Read_Only
● SAP_XMII_Super_Administrator
● SAP_XMII_ProjectManagement
For more information on the SAP MII roles, see the SAP MII security guide at http://help.sap.com SAP
Business Suite SAP Manufacturing SAP Manufacturing Integration and Intelligence 15.1 Security
Information .
SAP NetWeaver role assigned is ADMINISTRATOR.
You should create plant and line specific user groups for roles such as operator, supervisor, and administrator and
assign the corresponding roles delivered by OEE. If required, you can also create custom roles by assigning
appropriate actions and use those in plant and line specific user group.
More Information
Installation Guide for SAP MII 15.0 at https://service.sap.com/instguides SAP Business Suite Applications
SAP Manufacturing SAP Manufacturing Integration and Intelligence

1.3.3 SAP HANA Layer
Definition
This section contains information about the OEE-relevant authorizations for the software component OEE_HANA.
Use
SAP HANA analytical privileges restrict authorization in a query view to specific values of an attribute. For
example, if user has analytical privilege for plant 1000 only data for the corporation and that plant is visible; no
other data is visible.
SAP HANA analytical privileges work together with Structured Query Language (SQL) privileges, which are
SELECT privileges on the query views. You create the analytical privileges on the query views in SAP HANA.
Ensure the following when creating analytical privileges:
1. Create analytical privileges only on query views.

2. Grant full analytical privileges for all underlying non query views
3. Grant full SQL privilege on the query view
4. Do not grant any SQL privilege on the underlying non query views
Procedure to grant analytical privilege on a query view
1. Full analytical privilege on non query views

1. Install the Analytics Authorization Assistant tool in the SAP HANA studio.
For more information, see Analytics Authorization Assistant at http://service.sap.com/swdc
Support Packages and Patches Browse Our Download Catalog SAP Content Content for SAP
HANA Analytics Foundation for SAP Business Suite .
2. Open the SAP HANA studio, choose Analytics Authorization Create Authorizations for Non-Query
Views .
3. Select the SAP HANA system.
4. Enter a relevant prefix, for example, Full.
5. Choose the package where analytical privileges are to be created.
6. In the Package Selection pane, choose the package containing the query view.
7. Select the query view. Ensure that all the non query views are displayed.
8. Choose Finish.
This creates the full analytical privilege on all the non query views in the selected package.
2. Selective analytical privilege on query views
There are two ways to provide selective analytical privileges on query views. You can use any one of them:
○ Selective analytical privilege on all query views
1. In the SAP HANA studio, goto the Navigator pane. Choose your content package.
2. Right click on the content package and choose New Analytical Privilege .
3. In the New Analytic Privilege wizard, enter the name with the prefix AP.
Choose Create New.

4. Choose the query view and select Add. Choose Finish.
5. In the Associated Attributes Restrictions section, add the query view and the attribute on which you
want to add the analytical privilege.
6. In the Assign Restrictions section, add the following:
○ Operator: Equal Value: the plant number
○ Operator: Equal Value: empty plant
It is mandatory to maintain the value empty plant.
7. Activate the analytical privilege.
○ Selective analytical privilege on all query views except OEEQuery
You can also assign analytical privileges to query views by using the users or roles created in ABAP. The
authorizations of the user in the ABAP system are copied as analytical privilege in SAP HANA.
Prerequisites for using this method are:
1. Tables User buffer content for fast RFC logon - new (USRBF2) and User master: Authorizations
(UST12) are replicated from SAP ERP to SAP_OEE schema.
2. A user exists in SAP ERP (transaction code su01) who has appropriate OEE Roles assigned
(transaction code pfcg).
Note
The ABAP authorization object /OEE/C_MPHis used in assigning analytical privilege to the Plant
attribute.
1. Open the SAP HANA studio, choose Analytics Authorization Create Authorizations for Query
Views .
2. Select the SAP HANA system.
3. Choose package where analytical privileges are to be created.
4. In the Package Selection pane, choose package containing the query view.
5. Select the query view.
OEEQuery is not an option here.
6. In the SAP Client field, enter the SAP ERP client where the users and roles have been created.
7. In the ABAP User field, enter the SAP ERP user name to which the roles have been assigned and
whose authorizations you want to copy as analytical privileges.
8. Generate the query view.
3. Assigning analytical privilege to user
Note
Ensure that the user has SELECT privilege on the query view. These privileges are included in the Granted
Roles: DLM_MODELLING_SAP_ECC_SMALL, DLM_TEST_AUTHORIZATIONS, and PUBLIC.
You can verify this by viewing the user on the Granted Roles tab in the Security folder within the SAP HANA
Studio.
1. In the SAP HANA studio, under the Security folder, open the user.
2. On the Analytical Privileges tab, add both, full and selective analytical privileges.
3. Activate the user assignment.
The user is now able to see the specified plant data along with the global hierarchy information in the
query view report.

SAP OEE provides the following report to query view mappings:
○ Data Collection Element and Data Element report to Data Collection query
○ KPI Analysis report to OEE query
○ Loss Analysis report to Losses by Reason Code query
○ Loss Analysis report to Machine Losses query
○ Asset Utilization report to Scheduled Downtime query
More Information
Admin Guide for SAP HANA Live at https://service.sap.com/instguides SAP In-Memory Computing SAP
HANA Live for SAP Business Suite
1.4 OEE Customizing Settings in SAP ERP
SAP OEE application requires you to configure the following Customizing settings in the SAP ERP system:
● Define Hierarchy Template

● Define Hierarchy Node Classification
● Assign Logical System
● Define Machine Groups
● Define Production Modes
● Define Production Activity
● Define Data Element Types
● Define Data Elements
● Define Data Collection Contexts
● Define Data Collection Elements
● Define KPIs
● Define Global Reason Codes
To configure the Customizing activities in SAP ERP, use transaction code spro and then choose SAP Reference
IMG. The OEE-relevant Customizing activities are available under Production Overall Equipment
Effectiveness .
The Customizing activities have associated help documents that explain how to configure the Customizing
activities.

1.5 Master Data in SAP ERP
Definition
SAP OEE application uses plant-related and production-related master data from SAP ERP to calculate OEE KPIs
and provide data for analyzing plant performance.
To configure the master data, on the SAP Easy Access screen choose Logistics Production Overall
Equipment Effectiveness Master Data .
Use
OEE uses the following existing master data:
● Material master
● Work center and their associated capacities
In addition, you define the following OEE-relevant master data:
● Global hierarchy
For more information, see Creating Global Hierarchy [page 26]
● Plant hierarchy
For more information, see Creating Plant Hierarchy [page 27]
● Plant reason codes
For more information, see Creating Plant Reason Codes [page 30]
Data is transferred from SAP ERP to the ERP-Shop Floor Integration framework through IDocs.
More Information
ERP-Shop Floor Integration [page 31]
1.5.1 Creating Global Hierarchy
Prerequisites
● You have made the Customizing settings to define a global hierarchy template in Define OEE Hierarchy
Template under Production Overall Equipment Effectiveness .
● You have selected the option Aggregate Globally for those nodes of a plant hierarchy whose data you want to
aggregate globally in KPI calculation. You can select this option from the Create Plant Hierarchy screen.
If the option is not selected for a node, the global hierarchy can still be created but values are not displayed.

For more information, see Creating Plant Hierarchy [page 27].
Procedure
Caution
You can define only one global hierarchy template for an SAP ERP system.
1. On the SAP Easy Access screen, choose Logistics Production Overall Equipment Effectiveness Master
Data Global Hierarchy .
On the Global Hierarchy screen, choose the template you want to use to create a global hierarchy.
Choose whether you want to display, create, change, or delete the global hierarchy.
2. You can add different node types such as corporation, region, country, and plant at subsequent node levels in
the hierarchy based on the selected hierarchy template. The system guides you with the possible node types
that you can add at any given node while creating the hierarchy.
3. For every node type enter the validity period on the Details tab.
4. You can select the key performance indicators (KPIs) relevant for a node and maintain the target values. KPIs
can be assigned to all node levels in the hierarchy. KPI targets are material independent. You can specify the
KPI value range as positive, negative, or bi-directional based on the KPI type. These value ranges are used
while generating analytic reports.
5. To publish a hierarchy to the SAP HANA database, select the Publish option available on the secondary click
at the different nodes of the hierarchy.
The status of the hierarchy is displayed in the Status field on the Details tab. When a hierarchy's status is
Published, it is copied to the SAP HANA database. KPIs are reported after the hierarchy is published.
6. You can delete a node only if it is not published or is valid from a future date. When you delete such a node, the
node details no longer exist in the system.
1.5.2 Creating Plant Hierarchy
Prerequisites
● You have made the following Customizing settings under Production Overall Equipment Effectiveness :
○ Define OEE Hierarchy Template
○ Define Hierarchy Node Classification
○ Define KPIs
○ Define Machine Groups

Context
In OEE, plant hierarchy is a replication of a shop floor model. It is the basis on which shop floor data is collected
and analytics is provided.
Plant hierarchy enables in defining the building blocks of a free flowing hierarchy that you want to use to calculate
OEE metrics. It provides the hierarchy dimensions required for reporting KPIs across plant, department, line, work
center, and machine.
A plant hierarchy should be published and sent to SAP MII before the OEE dashboard can be used.
Procedure
1. On the SAP Easy Access screen, choose Logistics Production Overall Equipment Effectiveness Master
Data Plant Hierarchy .
On the Plant Hierarchy screen, enter the plant whose hierarchy you want to display, change, or create.
To create a new plant hierarchy, select a template suitable to the layout of your plant.
By default, system creates a plant hierarchy with plant as the root node type.
2. You can add different node types such as work centers, groupings, and machines at subsequent node levels in
the hierarchy based on the selected hierarchy template. The system guides you with the possible node types
that you can add at any given node while creating the hierarchy.
3. For every node type, including plant, enter the validity period on the Details tab.
4. You can select the key performance indicators (KPIs) relevant for a node and maintain the target values. KPIs
can be assigned to all node levels in the hierarchy. The KPI definition can be material-specific. If material is not
specified, the KPI target is considered for all the materials. You can specify the KPI value range as positive,
negative, or bi-directional based on the KPI type. These value ranges are used while generating analytic
reports and on the real time operator dashboard.
Note
You can also upload some of the plant hierarchy data to SAP ERP using report OEE: Mass Upload of Plant
Hierarchy Data (transaction /oee/plant_hier_upld). Use the report to upload data related to KPIs,
standard rates, technical objects, bottlenecks, and conversion factor. A template containing the format in
which data should be uploaded is available in SAP note 2221155 .
5. You can add technical information about a node on the Classification tab. To maintain data on this tab, the
Customizing activity Define Hierarchy Node Classification must be configured.
6. You can maintain the source and target quantity for a machine or line on the Conversion tab. These quantities
can be material-specific or material-independent. System calculates the conversion factor based on the
quantities maintained. Conversion factor can be maintained on a plant hierarchy node of type machine or
work center. The conversion factor maintained on the machine overrides the one maintained on the line.
Conversion factor enables conversion of a reported quantity on a machine to the equivalent quantity on the
line. For example, when quantity such as scrap is reported on a machine and indicates that it impacts line,
system uses the conversion factor, if maintained, to determine the effect on the overall Quality KPI.

Example
A material with Base UoM in PC (piece) is being produced. On the line, we have a machine that reports
scrap of an intermediate product in KG. To convert this scrap on the machine to the scrap quantity on Line,
a conversion factor is maintained as:
Source Quantity: 5 KG
Target Quantity: 2 PC
This implies that a scrap of 5 KG reported from on the machine is equivalent to a loss of 2 PC on the Line.
Note
The conversion factor functionality is available as of OEE_ERP 15.0 SP03 release with business function
Master Data Enhancement in OEE (/OEE/BF_ENH_MD). The functionality is not available for SAP MII 15.0
and its SP releases.
7. You can define a Grouping node under node type work center and maintain capacity information at the
Grouping node if the work center is a multi capacity.
8. To make a hierarchy available in the SAP HANA database or shop floor, select the Publish option available on
the secondary click at the plant node. When a hierarchy is published, system copies it to the SAP HANA
database and the shop floor system (SAP MII).
Ensure that Customizing Assign Logical System is configured. To send IDocs manually, use the report OEE
IDoc Selection (transaction code /OEE/BO_IDOC.
9. You can delete a node only if the node is not published or is valid from a future date. When you delete such a
node, you cannot report any data on the deleted node.
10. You can report production at a node only if the node is of type Work Center in the plant hierarchy template or
the node is a capacity.
To map a node of type Work Center to the corresponding PP/PI work center or resource, select the Report
Production flag. You can then enter the associated work center/resource and capacity category from SAP
ERP that you want to refer to. This gives information about calendar and shifts applicable to the node and
allows you to refer to the capacity of the associated work center. This reference also enables SAP OEE to
download the orders relevant to the line.
○ If a node is marked as reporting production and is assigned a multi capacity work center, then its child
nodes can also report production.
○ The child nodes can be markd as capacities.
○ The child nodes can be assigned the individual capacities of the parent work center. You assign the
individual capacity to the child nodes in the Reference to the Work Center Capacity section.
Orders that use individual capacity are dispatched according to the corresponding hierarchy node.
For example, consider a multi capacity work center WC1 with two individual capacities M_1 and M_2. For a
production order if the total quantity has been split into individual capacities, then these split quantities
are dispatched to the corresponding SAP OEE nodes. These quantities are available at the nodes
representing M_1 and M_2 on the OEE dashboard.
For more information, see Customizations for Line Behavior [page 93].
11. For a node at which you choose Report Production, you also define the standard rate. Specify the time period
for which standard rate is valid. The standard rate is defined for a material. You can associate the relevant
Task List Type, Routing/Recipe Group, Routing Version, and Operation/Activity.

Define the nominal quantity that should be produced in a particular duration. To do this, in the Standard Rate
section enter:
○ Quantity and its UoM

○ Duration and its UoM
Note
If quantity and duration with the UoMs are not specified here, you cannot start the order-operation from
the OEE dashboard.
The UoM you specify here must be same as the UoM, or one of the alternate UoMs maintained in the Material
Master. If the UoMs are different, quantity entered through the OEE dashboard cannot be confirmed in ERP.
Alternatively, you can also specify the standard rate in the Standard Rate field on the Details tab. In that case,
SAP OEE obtains the standard rate from the production or process order.
12. Select the Use Shift Break option if you want the shift breaks maintained in shift schedule (transaction code
op4a) to be considered while calculating the OEE metric Loading Time.
13. You can mark a node of type machine as bottleneck. The bottleneck configuration can be for a specific
material or routing or other task list types.
14. You can choose to include data reported at a node for KPI aggregation at the global level. To do this, select the
Aggregate Globally option for that node.
1.5.3 Creating Plant Reason Codes
Prerequisites
You have made the Customizing settings to define global reason codes in Define Global Reason Codes under
Production Overall Equipment Effectiveness .
Procedure
Note
You can do a mass upload of reason codes using the report Mass Upload of Reason Codes (transaction
code /oee/rc_excelupload). You enter the reason codes in a MS-Excel file in a predefined format, convert
the file to an XML file and upload the XML. The format in which data should be maintained is available in the
SAP Note 2221155 .
The option is available on the SAP Easy Access screen Logistics Production Overall Equipment
Effectiveness Information System Mass Upload of Reason Codes .
For more information, see the associated report documentation in the SAP ERP system.

You can also create plant level reason codes as follows:
1. On the SAP Easy Access menu, choose Logistics Production Overall Equipment Effectiveness Master
Data Plant Reason Code .
On the Create Plant Reason Codes screen, choose the global reason code levels 1, 2, and 3 that are relevant to
you.
2. You can assign plant level reason codes to an existing global reason code hierarchy. You can create and
assign up to seven levels of plant level reason codes.
You can view and change plant reason codes only for those plants for which you have authorization. For more
information, see User Roles and Authorizations [page 9].
3. Specify the plant for which you want to create the reason codes. You can add multiple reason codes at the
same reason code level.
4. You can map reason codes to an existing reason code from Quality Management module. To do this, enter the
relevant data in the Catalog, Code Group, and Code fields.
5. Map the reason code to an appropriate data element type belonging to the loss category.
All reason codes that you assign to a reason code hierarchy, including the ones that you assign at the plant
level, must be mapped to the same data element type.
6. You can maintain the planned duration of a scheduled downtime with a particular reason code. For this, you
maintain the standard duration in minutes for reason codes that belong to data element of type scheduled
downtime (SCHD_DOWN).
If the standard duration maintained is set as Is Fixed, then this duration cannot be modified by operators
when reporting a downtime. If it is not set as fixed, the operators have the flexibility to modify the standard
duration when reporting the downtime.
1.6 ERP-Shop Floor Integration

Use
The ERP-Shop Floor Integration framework provides integration of SAP OEE related data from SAP ERP with shop
floor SAP Manufacturing Integration and Intelligence (SAP MII) systems. This framework allows replication of
configuration data, master data, and transaction data from SAP ERP into SAP MII. You configure different
workflows to process the replicated data.
Data is replicated using IDocs.
The following reports are used to select the objects for which IDocs are to be created and transferred to ERP-Shop
Floor Integration framework.
● OEE IDoc Selection (transaction code /oee/bo_idoc)

For more information, see OEE IDoc Selection [page 42].
● Select Master Data for Transfer (transaction code /poim)
● Select Transaction Data for Transfer (transaction code /poit)
Note
SAP OEE provides CTC templates to configure your systems with the settings required for the ERP-Shop Floor
Integration framework.

The system landscape for the integration consists of the following components:
● SAP ERP Central Component 6.0 SP19 or higher with OEE add–on OEE_ERP 15.0 SP03
● SAP MII 15.1 or higher
● SAP NetWeaver 7.40 or 7.50 or higher
Figure 3: SAP ERP-Shop Floor Integration
1.6.1 ERP-Shop Floor Integration Configuration
Use
This section describes how to configure the ERP-Shop Floor Integration for SAP OEE Management.
Process
1. You configure the ALE for communication with SAP OEE (see Customizing for ALE for Communication with
SAP OEE [page 33]).
2. Execute the OEE CTCs. (see CTCs for OEE [page 41])
3. You send the OEE-relevant IDocs from SAP ERP to ERP-Shop Floor Integration framework (see OEE IDoc
Selection [page 42]).
4. The IDocs are received by the IDoc message listener configured in SAP NetWeaver by the SAP OEE
Integration Configuration CTC. The IDocs are processed as per the standard work flow. For more information,
see SAP MII Configurations for ERP-Shop Floor Integration. [page 72]

1.6.1.1 Customizing for ALE for Communication with SAP
OEE
Prerequisites
● You have created a plant in SAP ERP.

● You have configured SAP MII Message Listener.
● You have authorizations included in the following single roles in SAP ERP to maintain ALE settings:
○ SAP_IDOC_IMPLEMENTATION
○ SAP_WPS_ADMIN with additional object B_ALE_LSYS
○ SAP_AUDITOR_SA_BC
Activities
Maintaining a Logical System
1. In Customizing for Logistics - General, choose Supply Chain Planning Interfaces (SCPI) Production
Optimization Interface (POI) ALE settings for POI Maintain logical system .
2. On the Change View “Logical Systems”: Overview screen, choose New Entries.
3. Enter the following data:
Table 4:
Field Description User Action and Values Comments
Log.System System in which applications Enter the name of the RFC Limit name to CHAR 10 to fa
run integrated on a shared destination previously cre cilitate naming conventions
data basis ated of related objects
Name Short meaningful descrip Enter a short meaningful de

tion of the logical system scription
Defining RFC Destination
Optimization Interface (POI) ALE settings for POI Define RFC Destination .
2. On the Configuration of RFC Connections screen, select the TCP/IP connections node and choose the Create
icon.

3. On the RFC Destination screen, enter the following data:
Table 5:
RFC Destination Standard name of an RFC Enter a meaningful name You will enter the RFC des
destination that identifies both the SAP tination name several
MII Message Listener and times. We recommend that
SAP ERP you keep it simple and
memorable.
We also recommend that

the RFC Destination,
Program ID, and SAP MII
Message Listener have the
same name. The name
must be all uppercase as
some fields are case sensi
tive. This will ensure con
sistency throughout the
process.
Connection Type Type of RFC connection Enter T Type T destinations are

connections to external
programs that use the RFC
API to receive Remote
Function Calls.
Description 1 Short description of the Enter a short meaningful

RFC destination description (Optional)
4. Press Enter .
5. On the Technical Settings tab page on the RFC Destination screen, enter the following data:
Table 6:
Activation Type Radio buttons Choose Registered Server Using the registering feature
Program of the SAP gateway, RFC
server programs can be
started before; register at
this SAP gateway and then
wait for RFC call requests.

Start on Application Server Identification of a registered Enter the same name as the We recommend that you use
RFC server program RFC Destination both the name of the RFC
Program
server program and the host
name of the RFC server pro
gram.
The Program ID you enter

here corresponds to the
Message Listener in SAP MII
and must therefore have the
same name.
Gateway Options Gateway host name Enter the SAP system appli You can find out the name of
cation server the gateway service by log
Gateway Host
ging on the application
server you defined above
and starting the transaction
SMGW. The name of the
gateway server can be
looked up in the menu
Goto Parameters
Display
Gateway Service Gateway service Enter sapgw<SAP You can find out the name of
system number> the gateway service by log
ging on the application
server you defined above
and starting the transaction
SMGW. The name of the gate
way server can be looked up
in the menu Goto
Parameters Display

7. Ensure that the communication type is unicode.
8. (Optional) If you configured SAP MII IDoc Listener, test the RFC connection.
Defining a Logical Port
Optimization Interface (POI) ALE settings for POI Define port .
2. On the Ports in IDoc processing screen, select the Transactional RFC node and choose the Create icon.
3. In the Ports in IDoc processing dialog, select the own port name and enter a descriptive port name. We
recommend that you use the same name as that of the RFC connection previously created.
4. Choose the Enter icon.

5. On the Ports in IDoc processing screen, enter the following data:
Table 7:
Field Description User Action and Values
Description Short description of the port Enter a short meaningful description
Version Enables system select appropriate con Select IDoc record types SAP Release
trol record 4.x
RFC destination Standard name of an RFC destination Enter the name of the RFC destination
previously created
Maintaining a Partner Profile
Optimization Interface (POI) ALE settings for POI Maintain partner profile .
2. On the Partner profiles screen, create a new profile for Partner Type LS.
3. Enter the following data:
Table 8:
Partner no. Uniquely identifies a vendor, Enter the logical system pre
customer, or a logical sys viously created
tem
Ty. Classifies the recipient of er Enter C (Job)

ror notifications
Agent Specifies the job (person or Use matchcode search to Job key is internally gener
group of people) to be noti select the job number re ated when creating agents
fied if processing errors oc sponsible for error handling
cur

5. Under the Outbound Parameters table, choose the Create Outbound Parameter icon.

6. On the Partner profiles: Outbound parameters screen, enter the following data for each message type:
Table 9:
Message Type Uniquely assigned to SAP Enter the following: If you are using multi ca
ERP document types pacity work centers in your
MATMAS
orders, then maintain
LOIPRO Message Type as LOIPRO
and Message Code as OEE.
LOIWCS
LOICAL
/OEE/
CONF_CLASSIFICATION
/OEE/
CONF_CLASSIFICATION
_RECO
/OEE/CONF_DCELEM
/OEE/
CONF_DCELEM_RECO
/OEE/CONF_DCE_CTX
/OEE/
CONF_DCE_CTX_RECO
/OEE/CONF_KPI
/OEE/CONF_KPI_RECO
/OEE/CONF_MCGRP
/OEE/
CONF_MCGRP_RECO
/OEE/CONF_PRDACT
/OEE/
CONF_PRDACT_RECO
/OEE/CONF_PRODMODE
/OEE/
CONF_PRODMODE_RECO
/OEE/CONF_RC
/OEE/CONF_RC_RECO
/OEE/CONF_SHIFT
/OEE/CONF_TIMEELEM

/OEE/
CONF_TIMEELEM_RECO
/OEE/CONF_TIMEEL_TP
/OEE/
CONF_TIMEEL_TP_RECO
/OEE/
PLANT_HIERARCHY
/OEE/
PLANT_HIERARCHY_REC
/OEE/
STDVALKEY_FORMULAPA
RAM
/OEE/
STDVALKEY_PARAM_REC
O
SYNCH
T006_A
Receiver port Specifies how the IDocs are Enter the logical system pre
transferred to the EDI sub viously created
system
Output Mode Output is started immedi Select Transfer IDoc Immed.

ately for each individual IDoc and Do not start subsystem
The external subsystem is

not started from SAP ERP. It
must become active itself in
order to fetch the data.

IDoc Type Can be used without addi Enter the following: Each basic type corresponds
tional coding for data com to the list of message types
Basic type MATMAS05
munication above.
LOIPRO01
Note
LOICAL01
Enter the message code
LOIWCS02
OEE for LOIPRO01 if you
LOIWCS03 want to distribute the in
dividual capacity require
/OEE/
ments defined in the or
CLASSIFICATION01 der.
/OEE/
CLASSIFICATION02 Use IDoc Type LOIWCS03 if
you want to collect data for
/OEE/DCELEM01 production activities like set
/OEE/DCELEM02 up, processing, and tear-

down.
/OEE/DCECTX01
/OEE/DCECTX02
/OEE/KPI01
/OEE/KPI02
/OEE/MCGRP01
/OEE/MCGRP02
/OEE/PRDACTIVITY01
/OEE/PRDACTIVITY02
/OEE/PRODMODE01
/OEE/PRODMODE02
/OEE/RC01
/OEE/RC02
/OEE/SHIFT01
/OEE/
STDVALKEY_FORMULAPA
RAM01
/OEE/
STDVALKEY_FORMULAPA
RAM02
/OEE/TIMEELEM01

/OEE/TIMEELEM02
/OEE/TIMEELTP01
/OEE/TIMEELTP02
/OEE/PLANT01
/OEE/PLANT02
/OEE/PLANT03
/OEE/PLANT04
SYNCHRON
T006_01
Cancel Processing After If selected, the IDoc Interface Select the checkbox
Syntax Error terminates the processing in
the event that a syntax error
is found

8. Repeat steps 5–7 for each listed basic type.
Maintaining a Customer Distribution Model
Optimization Interface (POI) ALE settings for POI Maintain customer distribution model directly
2. On the Change Distribution Model screen, choose Create model view.
3. On the Create Model View screen, enter the following data:
Table 10:
Short text Short description of view of Enter a short meaningful de

distribution model scription
Technical name View of ALE model Enter a technical name
Start date Identifies the start of a valid Enter the start date of the
ity period validity period
End Date Identifies the end of the val Enter the end date of the val
idity period idity period

5. On the Change Distribution Model screen, select the distribution model previously created and choose Add
message type.

6. On the Add Message Type screen, enter the following data:
Table 11:
Model view View of distribution model Enter the name of the previ
ously created distribution
model
Sender Name of the logical source Enter the name of the sys This is usually the logical
system for exchanging mes tem sending the IDocs system name for the SAP cli
sages ent.
Receiver Name of the logical target Enter the name of the logical
system for exchanging mes system previously created
sages
Message Type Identifies different IDoc Enter the message type: Each message type is added
types separately following the
MATMAS
same steps.
LOICAL
LOIWCS
LOIPRO

8. Repeat steps 5–7 to add each message type to the distribution model as listed above.
1.6.1.2 CTCs for OEE
Use
This section explains the CTCs required to setup OEE.
Process
1. Run the SAP OEE NetWeaver Configuration CTC (see SAP OEE NetWeaver Configuration CTC [page 62])
2. Run the SAP OEE Integration CTC (see SAP OEE Integration Configuration CTC [page 64])
For the IDoc message type, this CTC configures the message processing rule. Based on the rule, the OEE-
relevant IDocs are categorized with the category name SAPOEEINT_INBOUND_QUEUE.

The CTC also configures the OEE-relevant schedulers. You can view the following OEE schedulers from SAP
MII main menu System Management Scheduler :
○ OEEInboundMessageEnqueuer: This scheduler picks the OEE-relevant messages from the SAP MII
Message Queue, which can be seen in the message monitor and classifies the IDocs to the corresponding
IDoc type and enqueues them into the OEE Message Queue.
○ OEEConfirmationsEnqueuer: This scheduler reads data from OEE database tables for completed
release demands and enqueues them in the OEE Message Queue. If you have enabled periodic
confirmation to SAP ERP under Worker UI Management General Configuration then the scheduler
sends confirmations to SAP ERP at the period you set. Confirmations are sent even if the release demand
is not complete. By default, this scheduler is disabled.
○ OEEMessageDispatcher: This scheduler saves the IDoc data into different OEE database tables based
on the IDoc type. The scheduler saves the IDoc data based on the workflow configured for that IDoc type
in ERP-Shop Floor Integration for Worker UI Workflow Configuration .
It also sends order-operation completion confirmations to SAP ERP at a scheduled frequency. For this, it
reads the OEE Message Queue for confirmations and uses the order confirmation Business Application
Programming Interface (BAPI) to send information to SAP ERP. The scheduler sends confirmation to SAP
ERP based on the workflow configured for the confirmation type in the Workflow Configuration.
For more information, seeSAP MII Configurations for ERP-Shop Floor Integration [page 72].
○ OEEQueueMessageCleaner: This scheduler deletes messages from the ERP-Shop Floor Integration for
Worker UI Queue Monitor at a scheduled frequency. You enter the frequency when you run this CTC.
By default, this scheduled is disabled. The scheduler deletes messages that have already been processed
successfully or have failed. It does not delete messages that are new or have not reached the maximum
retry attempts at processing. You can change the maximum number of processing attempts in the
workflow defined for that IDoc type at ERP-Shop Floor Integration for Worker UI Workflow Configuration.
○ OEEAutoCsvDownloadForReports: This scheduler is used in plant level reporting. For more
information, see Plant-level Reporting and Analytics in OEE [page 122].
You can change the configuration of the schedulers as per your requirement.
3. Run the OEE Configuration CTC (see SAP OEE Configuration CTC [page 68])
1.6.1.3 OEE IDoc Selection
Use
You can select and send IDocs containing data of SAP OEE Management relevant objects using OEE IDoc
Selection (transaction code /oee/bo_idoc) report. The IDocs are sent from SAP ERP to the ERP-Shop Floor
Integration framework. The framework replicates the object data from the IDocs and stores it in the SAP OEE
database tables in SAP MII.
Integration
On the selection screen, you specify the logical system that identifies the target system where you want the report
to send the IDocs after generating them.

You specify the objects whose IDocs you want the report to generate and send. IDocs can be generated for all
entries of an object, or a range of entries of the object. The reconcile option allows you to generate IDocs with all
keys of an object. This way a deleted record that was previously sent can be marked as obsolete in the ERP-Shop
Floor Integration framework.
Note
The reconcile option is not available for shift, UoM, and plant hierarchy. The reconcile option for reason codes
is not relevant SAP MII OEE 15.1 release onwards.
Activities
To access this report, on the SAP Easy Access screen choose Logistics Production Overall Equipment
Effectiveness Information System IDoc Selection .
This report is also available under Logistics Production - Process Overall Equipment Effectiveness
Information System IDoc Selection .
More Information
Integration of Configuration Data [page 43]
Integration of Master Data [page 55]
Integration of Transaction Data [page 59]
1.6.2 Integration of Configuration Data
Use
SAP OEE Management relevant configuration data is transferred from SAP ERP to ERP-Shop Floor Integration
framework.
This data consists of existing configuration data and OEE-relevant Customizing settings that you make for SAP
OEE in SAP ERP under Production Overall Equipment Effectiveness . You can reach the Customizing using
transaction /spro.
Configuration data is transferred using IDocs.
The following configuration data is transferred:
Note
Ensure that the data is transferred in the order in which it is listed.

Table 12:
Configuration data Report used to transfer the data
● Data collection elements contexts OEE IDoc Selection

● Data collection elements
For more information, see report OEE IDoc Selection [page
● Data Element Types
42] (transaction code /oee/bo_idoc).
● Data elements
● KPI definitions
● Machine groups
● Production modes
● Production Activity
● Hierarchy Node Classifications
● UoM and dimension
● Shift definitions and break schedules
● Standard value key and formula parameters
● Factory calendar Select Master Data for Transfer (transaction code /poim)
Features
● Near-real time data integration.

● Transfer of additional attributes through reconciliation option of report OEE IDoc Selection (OEE/
R_IDOC_CONF).
1.6.2.1 Transfer of Data Element Types
Use
This function enables transfer of configuration data for data element types from SAP ERP to SAP OEE
Management to create and update data element type records in SAP OEE database tables in SAP MII.
Prerequisites
● You have made the Customizing settings for Define Data Element Types under Production Overall
Equipment Effectiveness (see OEE Customizing Settings in SAP ERP [page 25]).
● You have set up ALE communication to create and transmit /OEE/TIMEELTP01 and /OEE/TIMEELTP02
IDocs (see Customizing for ALE for Communication with SAP OEE [page 33]).

Activities
● You create or update the definitions of data element types in SAP ERP.
● You send it to ERP-Shop Floor Integration framework (see OEE IDoc Selection [page 42]).
● ERP-Shop Floor Integration framework creates or updates the record in SAP OEE database tables.
1.6.2.2 Transfer of Data Elements
Use
This function enables transfer of configuration data for data elements from SAP ERP to SAP OEE Management to
create and update data elements records in SAP OEE database tables in SAP MII.
Integration
Data elements is a configuration object that along with data collection element allows you to define the data that
you want to consider while calculating the granular OEE KPIs like scheduled downtime, quality loss, performance
loss, and so on. (See Transfer of Data Element Types [page 44])
Transaction data reported from the shop floor is collected through data collection elements. Data elements are
assigned to data collection elements. Data elements enable you to determine whether the data collection element
is for reporting data for production or loss. You can further categorize loss type of data into subtypes such as
speed loss, quality loss, scheduled down, or unscheduled down. This categorization of data collection elements
facilitates aggregation of specific types of data elements for calculation of granular KPIs.
For example, scheduled downtime KPI is calculated by aggregating all those transaction data that have data
element type as loss and data element subtype as scheduled downtime.
Prerequisites
● You have made the Customizing settings for Define Data Elements under Production Overall Equipment
Effectiveness (see OEE Customizing Settings in SAP ERP [page 25]).
● You have set up ALE communication to create and transmit /OEE/TIMEELEM01 and /OEE/TIMEELEM02
Activities
● You create or update the data elements definition in SAP ERP.

1.6.2.3 Transfer of Data Collection Element Contexts
Use
This function enables transfer of configuration data for data collection element contexts from SAP ERP to SAP
OEE Management to create and update data collection element contexts records in SAP OEE database tables in
SAP MII.
Prerequisites
● You have made the Customizing settings for Define Data Collection Contexts under Production Overall
● You have set up ALE communication to create and transmit /OEE/DCECTX01 and /OEE/DCECTX02 IDocs
(see Customizing for ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update the data collection element contexts definition in SAP ERP.
1.6.2.4 Transfer of Data Collection Elements
Use
This function enables transfer of configuration data for data collection elements from SAP ERP to SAP OEE
Management to create and update data collection elements record in SAP OEE database tables in SAP MII.
Integration
Data collection elements that you define in SAP ERP are available for assignment to a dashboard.
Shop floor operator can report transaction data through these data collection elements.

(See Transfer of Data Elements [page 45])
Data collection element defines the type of the actual data being collected from the shop floor. Along with the
configurations for data elements, you can configure the data collection elements based on the type of data being
collected through the data collection element. They can be categorized as collecting data of quantity type or time
type. You can further categorize by defining the context of the data, whether the data is for a finished product, raw
material, or utilities. By default, data collected in the finished product context is considered for OEE calculations.
You can also configure the data collection element to specify if the transaction data being collected through the
data collection element is order or operation independent. By default, data that is order-dependent is considered
for OEE calculations.
Prerequisites
● You have maintained the Customizing settings for Define Data Collection Elements under Production
Overall Equipment Effectiveness (see OEE Customizing Settings in SAP ERP [page 25]).
● You have set up ALE communication to create and transmit /OEE/DCELEM01 and /OEE/DCELEM02 IDocs
Activities
● You create or update the data collection elements definition in SAP ERP.
1.6.2.5 Transfer of KPI Definitions
Use
This function enables transfer of configuration data for reason codes from SAP ERP to SAP OEE Management to
create and update KPI definitions records in SAP OEE database tables in SAP MII.
Integration
KPIs that you define in customizing are assigned and calculated at different nodes of a plant hierarchy. You
specify the target values for the KPIs that are assigned to a node (see Creating Plant Hierarchy [page 27]).
The shop floor operator enters production data used to calculate the KPIs through the dashboard (see Operator
Dashboard [page 109]).
SAP provides OEE calculations based on the standard KPI definitions (see OEE Calculations [page 7]).

You can define your own logic to calculate non standard KPIs. The data collection elements for these KPIs are
configured in SAP ERP and the production data is collected from the shop floor into the SAP NetWeaver database.
You define the data collection logic in the Java layer. This data is replicated into SAP HANA database where the
KPIs are aggregated and visualized.
Prerequisites
● You have made the Customizing settings for Define KPI Definitions under Production Overall Equipment
● You have set up ALE communication to create and transmit /OEE/KPI01 and /OEE/KPI02 IDocs (see
Customizing for ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update the KPI definitions in SAP ERP.

● ERP-Shop Floor Integration framework creates or updates the records in SAP OEE database tables.
1.6.2.6 Transfer of Machine Groups
Use
This function enables transfer of configuration data for machine groups from SAP ERP to SAP OEE Management
to create and update machine group records in SAP OEE database tables in SAP MII.
Machine groups logically group the plant hierarchy nodes defined as machine.
Integration
Machines groups are used to provide analytical information on a set of machines that belong to a group.
For example, an analysis could be performed in the SAP HANA database for Scheduled Downtime of Filler
Machines versus Scheduled Downtime of Blender Machines. The machine groups Filler Machines and Blender
Machines would be used in this analysis.
For more information, see http://help.sap.com SAP In-Memory Computing Innovations for SAP Business
Suite SAP HANA Live for SAP Business Suite Application Help SAP HANA Live for Manufacturing .

Prerequisites
● You have made the Customizing settings for Define Machine Groups under Production Overall Equipment
● You have set up ALE communication to create and transmit /OEE/MCGRP01 and /OEE/MCGRP02 IDocs
Activities
● You create or update the machine group definition in SAP ERP.

1.6.2.7 Transfer of Production Modes
Use
This function enables transfer of configuration data for production modes from SAP ERP to SAP OEE
Management to create and update the production mode records in SAP OEE database tables in SAP MII.
Integration
Production modes defined in SAP ERP are replicated to shop floor. Before starting an order or operation you can
specify the mode of the production run. Depending on the mode, production data is available for analysis. OEE is
calculated for all production modes.
For example, the shop floor is running an order in trial mode. However, you may only be interested in analysis of
production done on a regular mode and not interested in analysis of production done on trial mode. In such a
scenario, defining the production mode enables you to perform analysis for the data when production mode was
regular.
Prerequisites
● You have made the Customizing settings for Define Production Modes under Production Overall
● You have set up ALE communication to create and transmit /OEE/PRODMODE01 and /OEE/PRODMODE02

Activities
● You create or update the production mode definition in SAP ERP.

1.6.2.8 Transfer of Production Activities
Use
This function enables transfer of configuration data for production activities from SAP ERP to SAP OEE
Management to create and update production activities records in SAP OEE database tables in SAP MII.
Integration
Production activity enables you to define the different phases of an operation execution in a production order
such as setup, processing, tear down, ramp up, and so on. The production activities are mapped to a report type
class defined in SAP ERP. Based on the mapping, reported time is sent to the correct activity during confirmation.
For example, if a production activity is mapped to a Report Type class Setup, then SAP OEE updates the setup
time in SAP ERP.
During analysis, you can view the KPIs at each phase of operation execution in a production order.
Prerequisites
● You have made the Customizing settings for Define Production Activity under Production Overall
● You have set up ALE communication to create and transmit /OEE/PRDACTIVITY01 and /OEE/
PRDACTIVITY02 IDocs (see Customizing for ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update the production activities definition in SAP ERP.


1.6.2.9 Transfer of Hierarchy Node Classifications
Use
This function enables transfer of configuration data for hierarchy node classifications from SAP ERP to SAP OEE
Management to create and update hierarchy node classifications records in SAP OEE database tables in SAP MII.
Integration
Hierarchy node classifications defined in SAP ERP are replicated to the shop floor. You can use them to maintain
custom values for a node in the plant hierarchy.
Prerequisites
● You have made the Customizing settings for Define Hierarchy Node Classification under Production
● You have set up ALE communication to create and transmit /OEE/CLASSIFICATION01 and /OEE/
CLASSIFICATION02 IDocs (see Customizing for ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update the hierarchy node classification definition in SAP ERP.
1.6.2.10 Transfer of UoM and Dimensions
Use
This function enables the transfer of data for UoMs and dimensions from SAP ERP to SAP OEE Management to
create and update corresponding records in SAP OEE database tables in SAP MII.
Integration
UoM in which data is reported from the shop floor can be material dependent or independent.

UoM for a material can be reported in the base unit, alternate units, or UoMs of the same dimension as that of the
base UoM. For a particular dimension, the UoM can be maintained in different units.
When the operator reports good quantity of a material, the reported UoM is converted to the UoM in which the
standard rate for that material is defined. The conversion factor is obtained from the material header and
alternate UoM tables.
For material independent UoMs such as time dimension UoMs, any data that is replicated for time, for example,
standard rate reported in minutes is converted into seconds. For this conversion, the UoM and dimension tables
are used.
Prerequisites
● You have created UoM and dimensions with material-relevant data (transaction code /cuni).
● You have set up ALE communication to create and transmit T006_01 IDoc (see Customizing for ALE for
Communication with SAP OEE [page 33]).
Activities
● You create or update a UoM or dimensions master record in SAP ERP.

1.6.2.11 Transfer of Shift Definitions and Break Schedules
Use
This function enables the transfer of shift definitions data from SAP ERP to SAP OEE Management to create and
update shift definition records in SAP OEE database tables in SAP MII.
Integration
Shifts and break schedules are mapped to work center capacities. This enables SAP OEE to take shift start and
end times, and fixed scheduled breaks into account while calculating OEE KPIs and analyzing them.
For example, in case of a breakdown whose duration overlaps a scheduled break, the system factors in the
scheduled break and reduces the breakdown duration accordingly. This enables an accurate plant performance
analysis that is based on shifts.
To factor in the shift breaks, enable the Use Shift Break option while configuring the plant hierarchy.

Analysis based on shifts also uses shift data. For example, an analysis of scheduled downtime during morning
shifts.
Prerequisites
● You have created shift definitions

● You have set up ALE communication to create and transmit /OEE/SHIFT01 IDoc (see Customizing for ALE for
Activities
● You create or update a shift definition master record in ERP.

1.6.2.12 Transfer of Standard Value Key and Formula

Parameters
Use
This function enables transfer of standard value key and formula parameters from SAP ERP to SAP OEE
Management to create and update standard value key and formula parameters records in SAP OEE database
tables in SAP MII.
Integration
Standard value keys and the assigned formula parameters that you define in SAP ERP are assigned to work
centers. Formula parameters assigned to a work center allow you to report activities like set up, tear down, and so
on that are applicable to that work center.
Prerequisites
● You have created the formula parameters and standard value keys with plant-relevant and production-
relevant data in the Logistics module (transaction codes for standard value key: /op19 and formula
parameter: /op7b).

● You have assigned formula parameters to standard value keys.
● You have set up ALE communication to create and transmit /OEE/
STDVALKEY_FORMULAPARAM01 and /OEE/STDVALKEY_FORMULAPARAM02 IDocs (see Customizing for
ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update a standard value and formula parameter master record in SAP ERP.
● You send it to ERP-Shop Floor Integration framework (See OEE IDoc Selection [page 42]).
1.6.2.13 Transfer of Factory Calendar
Use
This function enables the transfer of factory calendar data from SAP ERP to SAP OEE Management to create and
update the corresponding factory calendar records in SAP OEE database tables in SAP MII.
Integration
ERP-Shop Floor Integration framework uses the factory calendar to validate if the date on which data is being
reported at a plant hierarchy node is a working day.
Prerequisites
● You have created factory calendar (transaction code /scal).

● You have set up ALE communication to create and transmit LOICAL01 IDoc (see Customizing for ALE for
Activities
● You create or update a factory calendar master record in SAP ERP.

● You send it to ERP-Shop Floor Integration framework.

1.6.3 Integration of Master Data
Use
SAP OEE relevant master data is transferred from SAP ERP to ERP-Shop Floor Integration framework.
Master data is transferred using IDocs.
The following master data is transferred:
Note
Ensure that the data is transferred in the order in which it is listed.
Table 13:
Master Data Report used to transfer the data
● Plant hierarchy data OEE IDoc Selection

● Reason codes (loss tree)
For more information, see report OEE IDoc Selection [page
42] (transaction code /oee/bo_idoc).
● Work center and capacities Select Master Data for Transfer (transaction code /poim)
● Material
Features
● Near-real time data integration.

● Transfer of additional attributes through reconcile option of reports Select Master Data for Transfer
(RCCLMDAT) and OEE IDoc Selection (OEE/R_IDOC_CONF).
1.6.3.1 Transfer of Plant Hierarchy Data
Use
This function enables the transfer of plant hierarchy data from SAP ERP to SAP OEE Management to create and
update the plant hierarchy records in SAP OEE database tables in SAP MII. Data for KPIs, standard rates,
bottlenecks and other settings defined at the different nodes of plant hierarchy is also transferred along with the
plant hierarchy data.
Data of a plant hierarchy in status Published is transferred.
Plant hierarchy data can also be transferred from one SAP ERP system to another SAP ERP system.
On the selection screen of the OEE IDoc Selection report (transaction code /oee/bo_idoc), you specify the
logical system that identifies the target ERP system.

Integration
Shop floor data is reported against a node in the plant hierarchy. This enables analysis of data against a particular
node in the hierarchy. Data associated with the plant hierarchy is specific to the type of node it is reported against.
You can configure the hierarchy nodes in the customizing activity Define Hierarchy Template under Production
The different data that can be associated with a node are used as follows:
● Data related to work center reference, capacity reference, standard rates, shift breaks, plant maintenance
related technical objects and so on is used in the SAP MII layer to determine the node on which an order or
operation is running.
● Work center reference, capacity reference, standard rate, including preventive maintenance and shift breaks,
or reporting production is used in the SAP MII layer to determine the node on which an order or operation is
running.
● Material and routing specific standard rates of production on a node is used in the SAP MII layer to calculate
the Net Production Quantity.
● Nodes marked as bottlenecks by default, or for a specific combination of material and routing details are used
in the SAP MII layer to determine whether or not a node’s parent must be marked as down when a downtime
event occurs at that node.
● KPI targets defined for a node are used in the ERP-Shop Floor Integration framework to determine the color
codes of the ANDON buttons for OEE KPIs on the shop floor UI.
● Machine groups associated to a node are used in the SAP MII layer to report data against. Data for machine
groups is used in the SAP HANA layer to analyze the machine groups.
● Conversion factor data is used for conversion of a reported quantity on a machine to the equivalent quantity
on the line.
● Technical Objects are used for integration to the SAP Plant Maintenance (PM) module.
Plant hierarchies defined in SAP ERP are available through the operator's dashboard for entering data against
them.
Prerequisites
● You have created or updated plant hierarchy master record in the Logistics module.
● You have defined KPI targets, standard rates, bottlenecks, machine groups and other relevant data for the
nodes of the plant hierarchy.
● You have set up ALE communication to create and transmit /OEE/PLANT01 IDoc (see Customizing for ALE
for Communication with SAP OEE [page 33]).
Activities
● You create or update a plant hierarchy master record in SAP ERP (see Creating Plant Hierarchy [page 27]).

1.6.3.2 Transfer of Reason Codes
Use
This function enables transfer of master data for reason codes from SAP ERP to SAP OEE Management to create
and update reason code or loss tree records in SAP OEE database tables in SAP MII.
Integration
Reason codes can be defined up to ten levels deep, this includes three levels of global reason codes and seven
levels of plant reason codes. The plant reason codes you define in SAP ERP is available to the shop floor operator
for reporting events. These reported events are used in root cause analysis of losses. (See Creating Plant Reason
Codes [page 30])
For example, an event Breakdown on the shop floor is further categorized based on reason code assignment. The
first level of plant reason code could be Material Starving. It is possible that no other levels need to be assigned as
the first level is sufficient for root cause analysis.
An event Planned Maintenance on the shop floor could be categorized with first level of plant reason code as
Changeover. A second level of plant reason code of Product Change could be associated with this. At the next
level, the reason code could be Salt Flush. Thus, during analysis, a drill down up to the root cause of Planned
Maintenance event can be performed.
Prerequisites
● You have made the Customizing settings for Define Reason Codes under Production Overall Equipment
● You have set up ALE communication to create and transmit /OEE/RC01 and /OEE/RC02 IDocs (see
Customizing for ALE for Communication with SAP OEE [page 33]).
Activities
● You create or update the reason code or loss tree definition in SAP ERP.
● ERP-Shop Floor Integration framework creates or updates the records in SAP OEE database tables.

1.6.3.3 Transfer of Work Centers and Capacities
Use
This function enables transfer of work center or resource data from SAP ERP to SAP OEE Management to create
and update work center and capacities records in SAP OEE database tables in SAP MII.
Integration
Plant hierarchy nodes that report production refer to SAP ERP work centers or resources and their associated
capacities.
Production and process orders are released against these work centers or resources that are associated to plant
hierarchy nodes. The shift and the factory calendar used for OEE calculations and analysis are determined from
the work center or resources capacities.
Prerequisites
● You have created work centers (transaction code /cr01) and resources (transaction code /crc1) with plant-
relevant and production-relevant data in the Logistics module .
● You have assigned capacities to work centers or resources.
● You have set up ALE communication to create and transmit LOIWCS02 or LOIWCS03 IDocs (see Customizing
for ALE for Communication with SAP OEE [page 33]).
● Intervals and shifts should be maintained against the relevant capacity header. Also set the field Active
Version to 1.
Activities
● You create or update a work center or resource master record in SAP ERP.
● ERP-Shop Floor Integration framework creates or updates the work center record in SAP OEE database
tables.

1.6.3.4 Transfer of Material
Use
This function enables the transfer of material data from SAP ERP to SAP OEE Management to create or update
the corresponding material records in SAP OEE database tables in SAP MII.
Integration
Material master data is replicated to the shop floor where it is used to determine the language independent
description of the material and other material specific details.
The UoMs in which production is reported on the shop floor is obtained from:
● Base UoM of material

● Alternate UoM of the material
● UoMs of same dimension as that of the base UoM of the material
Analysis can be done based on materials, for example, analysis of unscheduled downtime when material XYZ was
being produced. Production is reported against finished as well as raw materials on the shop floor. Details of these
materials are obtained from the replicated material data.
Prerequisites
● You have set up material master records with plant-relevant and production-relevant data in the Logistics
module.
● You have set up ALE communication to create and transmit MATMAS05 IDoc (see Customizing for ALE for
Activities
● You create or update a material master record in SAP ERP.

● ERP-Shop Floor Integration framework creates or updates the corresponding material record in SAP OEE
database tables.
1.6.4 Integration of Transaction Data
Transaction data for production orders and process orders is transferred from SAP ERP to ERP-Shop Floor
Integration framework to update and change records in SAP OEE database tables in SAP MII.

Transaction data is transferred using IDocs.
You transfer the following transaction data using report Start Download of Transaction Data (transaction code /
poit):
● Production orders
● Process orders
1.6.4.1 Transfer of Production Orders
Use
This function enables the transfer of production order data from SAP ERP to SAP OEE Management to create and
update the corresponding production shop order records in SAP OEE database tables in SAP MII.
Integration
Production orders with status Created or Released in SAP ERP are transferred to the ERP-Shop Floor Integration
framework. Orders with Created status are displayed on the Dispatch Quantity screen and not processed further.
The production order can be released completely or partially. By default, the entire production order quantity is
released.
The operator can use the dashboard to start order-operations only after the production order quantity has been
released from the ERP-Shop Floor Integration framework. You can start an order for the different operations in
the production order, since release demands are created for the operations in the order (see Configuring Order
Dispatch [page 104]).
Recommendation
Use production orders without sub operations as the sub operations for production orders are not supported
on the SAP OEE dashboard.
Also use production orders with single sequence as multiple sequences are not addressed by SAP OEE.
Prerequisites
● You have created a production order either manually or automatically by converting a planned order.
● You have set up ALE communication to create and transmit LOIPRO01 IDoc (see Customizing for ALE for
● You have defined unique ISO codes for at least one unit of measure for every dimension.

Activities
● You create a production order either manually or automatically by converting a planned order or update the
production order in SAP ERP.
● ERP-Shop Floor Integration framework creates or updates the corresponding production shop order record in
the SAP OEE database tables.
1.6.4.2 Transfer of Process Orders
Use
This function enables the transfer of process order data from SAP ERP to SAP OEE Management to create or
update the corresponding process shop order records in SAP OEE database tables in SAP MII.
Integration
Process orders with status Created or Released in ERP are transferred to the ERP-Shop Floor Integration
framework. Orders with Created status are displayed on the Dispatch Quantity screen and are not processed
further.
The process order can be released completely or partially. By default, the entire process order quantity is
released.
The operator can use the dashboard to start order phases only after the process order quantity has been released
from the ERP-Shop Floor Integration framework. You can start an order for the different phases in the process
order, since release demands are created for the phases in the order.
Prerequisites
● You have created a process order either manually or automatically by converting a planned order.
● You have set up ALE communication to create and transmit LOIPRO01 IDoc (see Customizing for ALE for
Activities
● You create a process order either manually or automatically by converting a planned order or update the
process order in SAP ERP.

● ERP-Shop Floor Integration framework creates or updates the corresponding process order records in the
SAP OEE database tables.
1.7 SAP OEE CTC
Use
The configuration of SAP OEE is performed through Central Technical Configuration (CTC) wizards so that all the
configurations can be entered in one central application. After the .sca file is deployed, you run the CTC wizards
for SAP OEE to perform the necessary configurations.
You run the following CTCs to setup the system:
1. SAP OEE NetWeaver Configuration (see SAP OEE NetWeaver Configuration CTC [page 62])
After you run this CTC, you can create the logging destinations and categories for logging OEE configuration
data. For more information, see SAP Note 1889923 .
2. SAP OEE Integration Configuration (see SAP OEE Integration Configuration CTC [page 64]).
○ You run this CTC for every client and plant combination.
○ After you run this CTC, restart the SAP NetWeaver server.
3. SAP OEE Configuration (see SAP OEE Configuration CTC [page 68]). You run this CTC for every client and
plant combination.
You can access these CTCs through NetWeaver Administrator Configuration Scenarios Configuration
Wizard: SAP OEE NetWeaver Configurations .
More Information
Re-executing CTC Wizards [page 69]
Configuring New Plant [page 69]
1.7.1 SAP OEE NetWeaver Configuration CTC
This CTC configures SAP NetWeaver with an OEE user who has the required roles to perform all OEE related
actions. You provide information for this through the SAP OEE NetWeaver Configuration wizard.
This CTC performs the following actions:
1. Creates or updates OEE_ADMIN and OEE_INTEGRATOR users.

2. Assigns the following roles to the OEE_ADMIN user:
○ OEE_SUPERADMIN
○ OEE_INTEGRATOR

○ SAP_XMII_User
○ SAP_XMII_Administrator
○ SAP_XMII_Developer
○ SAP_XMII_DynamicQuery
○ SAP_XMII_Read_Only
○ SAP_XMII_Super_Administrator
○ SAP_XMII_ProjectManagement
○ ADMINISTRATOR This is the SAP NetWeaver Administrator role.
The OEE_ADMIN user has the superset of all possible roles to perform all the actions in SAP OEE Management.
3. Assigns the following roles to the OEE_INTEGRATOR user:
○ OEE_INTEGRATOR
○ SAP_XMII_User
○ SAP_XMII_Administrator
○ SAP_XMII_Developer
○ SAP_XMII_DynamicQuery
○ SAP_XMII_Read_Only
○ SAP_XMII_Super_Administrator
○ SAP_XMII_ProjectManagement
Fields
The following table describes the fields on the wizard that require explanation:
Table 14:
Password of OEE_ADMIN User screen
Field Description
OEE_ADMIN Password Enter the password for the OEE_ADMIN user.
SAP NetWeaver Instance for SAP MII screen

Protocol http or https
Caution
To use SSL (HTTPS) communication channel, the
SAP_XMII_Developer role with the
Destination_Service_Write_Permission action must be as
signed.
Proceed as follows:
1. Log on to SAP NetWeaver Administration and choose
Configuration Security Identity Management
Search Criteria: Role and search for

SAP_XMII_Developer.
2. Modify the SAP_XMII_Developer role.
3. Move Destination_Service_Write_Permission to
Assigned Actions.
Host Enter the name of the SAP MII host server.
Port Enter the SAP MII port number.
SSL Port Enter the name of the SSL port if you have selected the proto
col as https.
1.7.2 SAP OEE Integration Configuration CTC
This CTC wizard configures SAP MII and integration-related SAP OEE elements for SAP OEE and SAP ERP
integration.
You provide information for this through the SAP OEE Integration CTC wizard.
Prerequisites
● You have configured ALE configurations.

For more information, see Customizing for ALE for Communication with SAP OEE [page 33].
● You have run the SAP OEE NetWeaver CTC.

Fields
Note
For more information about the typical values for the fields in CTC of SAP OEE Integration Configuration wizard
see the SAP MII Installation guide at http://service.sap.com/instguides SAP Business Suite Applications
SAP Manufacturing SAP Manufacturing Integration and Intelligence .
Table 15:
JRA Adapter Information screen
Fields Description
Connection Factory Name Enter the connection factory name
To add the autoCommit property to the JRA Connection, see

SAP Note 2217030 which explains how to configure JRA
Connection Factory with autoCommit set to false.
Server Enter the SAP ERP server name associated with your OEE
plant(s)
Client Enter the ERP client
System Number Enter the ERP system number
Language Enter the ERP logon language
Select to configure EWM Select the checkbox if you want to connect to SAP EWM. En
ter the SAP EWM JRA information.
This is required if you want to use Goods Issue and Goods Re
ceipt apps in integration with SAP EWM.
Supported SAP OEE Plant screen
Field Description
ERP Plant Enter the name of an existing SAP ERP plant to be integrated
with SAP OEE Management.
SAP OEE_ADMIN Password Enter the OEE_ADMIN password for verification
SAP ERP JRA Connector Name Enter the JRA connector name that you want to use.
SAP ERP Time Zone Enter the time zone in which the SAP ERP system is located.
SAP OEE Time Zone Enter the time zone in which the OEE plant is located.

SAP NetWeaver Instance for SAP MII screen
SAP NetWeaver Information section
Protocol http or https
Caution
To use SSL (HTTPS) communication channel, the
SAP_XMII_Developer role with the
Destination_Service_Write_Permission action
must be assigned.
Proceed as follows:
1. Log on to SAP NetWeaver Administration and choose
Configuration Security Identity Management
Search Criteria: Role and search for

SAP_XMII_Developer.
2. Modify theSAP_XMII_Developer role.
3. Move Destination_Service_Write_Permission to
Assigned Actions.
Host Enter the name of the SAP MII host server.
Port Enter the SAP MII port number.
SSL Port Enter the name of the SSL port if you have selected the proto
col as https.
XMIIIDOC Listener: Enter the name of SAP MII message listener that you want to
associate with the SAP ERP system.
SAP ERP Connection Information section
For the selected SAP MII message listener, provide the following
Program ID Enter the program ID configured in SAP ERP to send IDocs.

For more information, see Customizing for ALE for Communi
cation with SAP OEE [page 33]
SAP MII Schedulers screen
Message Dispatcher
Number of Messages Enter the number of messages to be processed at the speci

fied interval.
Pattern Enter the frequency at which the scheduler dispatches mes

sages to SAP OEE database tables. For example, for the pat
tern 0 * * * * *, scheduler runs every minute.

Queue Message Cleaner - By default, this scheduler is disabled.
Message Retention Period (hours) Enter the duration for which messages should be retained in
the SAP OEE Integration message queue.
Pattern Enter the frequency at which the scheduler deletes the mes
sages from the SAP OEE Integration after the specified reten
tion period.
IDoc Inbound Enqueuer
Number of Messages (qty) Enter the number of messages to be enqueued at the speci
fied interval.
Pattern Enter the frequency at which the scheduler enqueues the

messages for processing.
Confirmation Enqueuer - By default this scheduler is disabled.
Number of Messages Enter the number of messages to be enqueued at the speci

fied interval.
Pattern Enter the frequency at which the scheduler enqueues the

messages for processing.
Update Configuration screen
OEE Control Keys
Pre XSLT Transaction Parameter Specify the OEE relevant operations within a production or
process order. You can do this by entering the control key of
the operations that are OEE relevant.
If control keys are entered, only those operations will be avail

able in SAP OEE. However, if no control keys are entered then
all the operations are transferred. Ensure that you enter the
control keys separated by semi colons.
An example string is defaulted. You can refer to it to write your

own string.
Location of Auto CSV Download for OEE Reports screen
Export CSV Parameters
FTP Location Enter the FTP location where the CSV file is downloaded.
MII Scheduler Pattern Define the frequency at which the CSV should be downloaded.

Post-CTC Execution Procedures
Update the SAP MII Message Listener as follows:
1. Log on to SAP MII with the OEE_ADMIN user using the following URL: http://
<SAP_MII_host>:<SAP_MII_port>/XMII.
2. On the SAP MII main menu screen, choose Message Services Message Listeners .
3. Select the XMIIIDOCnn that has been recently configured with the CTC wizard.
4. On the Details Configuration tab page, if the SAP Server name and SAP Client number are blank, choose
Update.
5. On the Details Status tab page, verify the connection status.
If SAP MII Listener XMIIIDOCnn status is Not Connected, check if SAP ERP system is accessible and correct
credentials are defined in SAP NetWeaver XMIIIDOCnn resource adapter properties. If you cannot access the
ERP system, resolve connection issues and then update the Message Listener in SAP MII.
Note
If you notice any incorrect configurations in SAP NetWeaver XMIIIDOCnn resource adapter properties, we
recommend that you re-execute the SAP OEE Integration CTC wizard with correct values.
1.7.3 SAP OEE Configuration CTC
This CTC configures the system defaults for SAP OEE such as activities, OEE dashboard and so on. You provide
information for this through the SAP OEE Configuration wizard.
This CTC performs the following actions:
1. Creates default loading statuses along with descriptions in the languages supported by SAP.
2. Creates default activities along with descriptions in the languages supported by SAP.
3. Creates default dashboards along with default buttons, their associated activities and their descriptions in the
languages supported by SAP.
4. Creates default Customization names along with their allowed values (if applicable) and their descriptions in
the languages supported by SAP.
Fields
Table 16:
ERP Client and Plant Information screen
Field Description

ERP Client Enter the ERP client where the above plant is configured.
ERP Plant Enter the name of an existing SAP ERP plant to be integrated
with SAP OEE Management.
Note
In a clustered environment, access the SAP OEE Configuration CTC through the Web dispatcher URL for the
SAP NetWeaver system.
1.7.3.1 Configuring New Plant
The first plant gets configured automatically in SAP MII when you run SAP OEE NetWeaver Configuration CTC
(see SAP OEE NetWeaver Configuration CTC [page 62]) and SAP OEE Integration Configuration CTC (see SAP
OEE Integration Configuration CTC [page 64]).
To configure the second plant onwards:
1. On the SAP MII main menu, choose ERP-Shop Floor Integration for Worker UI Supported Plants. .
In the SAP OEE Plants List section choose Create. Enter the details of the new plant in the SAP OEE Plant
Details section. The SAP ERP JRA Factory Name can be the same as that maintained for the first plant.
2. Run the SAP OEE Configuration CTC again providing the new client and plant information (see SAP OEE
Configuration CTC [page 68]).
1.7.4 Re-executing CTC Wizards
If execution of the SAP OEE CTC wizards was interrupted for any reason, resolve the root cause issue and re-
execute the SAP OEE CTC wizard.
In Configuration Tasks view, choose Show Category All Configuration Tasks
Select appropriate SAP OEE Integration task, and choose Re-execute.
Do not use the Resume or Takeover Session buttons to continue with any of the SAP OEE CTC wizards.
If any wizard is in the Currently Executing status, choose Show Category Running Configuration Tasks
Select appropriate task and choose Cancel Process.
After SAP OEE CTC templates are executed, one SAP OEE plant is configured. To configure multiple SAP OEE
plants, execute CTC templates SAP OEE Integration and SAP OEE Configuration wizards for each plant.
To manually make minor corrections or modifications in the current configurations, see ERP-Shop Floor
Integration Configuration [page 32].

1.7.5 CTC to Setup OEE Demo Plant Data
Use
You can run a proof of concept with OEE which helps you understand and demonstrate how the application works.
For this, OEE provides a CTC: SAP OEE Demo Plant Data Setup. The CTC sets up a model plant master data and
associated order data in SAP MII. After executing the CTC, you can start the OEE application, work with the OEE
worker UI and understand the features and functions of the OEE application.
The CTC creates ERP-related master data in SAP MII and provides a sample OEE framework which you can use
for custom development.
Prerequisites
You have run the SAP OEE NetWeaver Configuration CTC.
For more information, see SAP OEE NetWeaver Configuration CTC [page 62].
Procedure
1. Access the CTC through NetWeaver Administrator (NWA) Configuration Scenarios Configuration
Wizard .
Search for OEE CTCs by entering *OEE* in the Find field.
2. Run the SAP OEE Demo Plant Data Setup. Enter the OEE_Integrator password.
3. On the User Group Dashboard Assignment tab, add the SAP UME User Group Everyone and select dashboard
Operator Dashboard.
Save the changes.
4. The sample OEE dashboard is now configured and is available for you to use. You can see orders in the New
state on the Manage Order screen. You can start reporting sample data from the OEE dashboard.
More Information
SAP OEE CTC [page 62]
1.7.6 CTC for Archiving OEE Data
You can archive OEE data using the SAP OEE Archiving Configuration CTC.

Prerequisite
For information on how to setup OEE data archiving, see 2484228 .
Procedure
1. Run the SAP OEE Archiving Configuration CTC from NWA Configuration Scenarios Configuration
Wizard .
2. Enter the following details:
○ SAP OEE_Admin password: Enter the password for the OEE_ADMIN user.
○ Protocol: http or https
○ Host: Enter the name of the SAP MII host server.
Caution
To use SSL (HTTPS) communication channel, the SAP_XMII_Developer role with the
Destination_Service_Write_Permission action must be assigned.
Proceed as follows:
1. Log on to SAP NetWeaver Administration and choose Configuration Security Identity

Management Search Criteria: Role and search for SAP_XMII_Developer.
2. Modify the SAP_XMII_Developer role.
3. Move Destination_Service_Write_Permission to Assigned Actions.
○ Port: Enter the SAP MII port number.

○ SAP ERP Client: Data is archived for a SAP ERP client and plant combination. Specify the client and plant
whose data you want to archive.
○ SAP ERP Plant: Data is archived for a SAP ERP client and plant combination. Specify the client and plant
whose data you want to archive.
○ Retention Time in Days: System checks for duration since which the data is availabke in the database and
archives data that is older than the number of days you specify here.
○ MII Scheduler Pattern: Specify the pattern for the OEE Archiving Job scheduler run. The scheduler
performs the data archiving at the specified pattern.
Note
This CTC creates the OEE Archiving Job scheduler; however, you must manually enable the scheduler
in MII.
○ Batch Size: The number of records that should be archived in a scheduler run.

1.8 Configurations in SAP MII
This section describes how to configure ERP-Shop Floor Integration in SAP MII.
1.8.1 SAP MII Configurations for ERP-Shop Floor Integration
Use
Configurations for ERP-Shop Floor Integration framework are made in SAP MII.
The configurations are done by the SAP OEE CTCs. You can also change these configurations.
Prerequisites
You have executed the SAP OEE CTCs.
Process
The configuration settings for ERP-Shop Floor Integration are available from the SAP MII main menu screen
ERP-Shop Floor Integration for Worker UI :
1. Global Configurations
You can view the following OEE-relevant properties here:
○ SAPMPM_ASYNCH_ENQUEUE_TXN
This property enqueues all production order relevant data reported from the OEE dashboard into the OEE
Message Queue.
○ SAPMPM_UOM_CONVERSION_TXN
This property enables the conversion from one UoM to another as per standard SAP logic for UoM
conversion.
○ SAPOEEINT_RETRY_RETENTION_PERIOD
This property contains the duration in minutes that should elapse before an attempt is made to process a
message again.
2. Supported Plants
You can view the plants that are supported by a particular SAP MII instance.
ERP-Shop Floor Integration framework processes only those production order IDocs that belong to the clients
and plants listed here.
For outbound communications to SAP ERP, SAP S/4HANA, or SAP EWM, the JRA Factories maintained here
are used by the standard solution.
3. Workflow Configurations

The workflow configured to process the IDocs is:
○ Standard Workflow
This workflow is used to convert the message from the source XML format to the target XML format using
a set of Extensible Stylesheet Language Transformations (XSLT). You can view the XSLT definitions used
for the conversion.
Select the message type from the Type List section on the Workflow Configuration screen. The
corresponding XSLTs details are displayed in the Type Details section.
For all standard message types of OEE in workflow configuration, Standard Workflow is used to process
the IDocs and send confirmations to SAP ERP.
4. Queue Monitor
The Queue Monitor enables you to trace the status of an IDoc after it was received in the ERP-Shop Floor
Integration framework. Use the Trace option to view the status of the IDoc. You can also view the intermediate
XMLs generated after XSL transformations. You can delete an IDoc from here.
You can also retry processing an IDoc that is in the failed state. To do this, select the IDoc and choose Retry.
The status of the IDoc changes from Failed to Retry.
1.8.2 Transport OEE Configurations (SAP MII)
Use
You can transport OEE-relevant configurations made in SAP MII. You can export and import the OEE
configurations between the source and target SAP MII systems.
System creates the XML files for the configurations that you choose to export. You can export these files using the
File System export method or through Enhanced Change and Transport System (CTS+).
To understand how transports are made using CTS+, see .
Activities
To select the configurations that you want to export:
1. From the SAP MII main menu screen, choose System Management Configurations .
A list of configurations that can be exported are displayed.
2. Select the configurations that you want to export.
In addition to the SAP MII configurations (see ) the following OEE-specific configurations can be exported:
Table 17:
Configuration Associated XML file
Dashboard Configuration OEEPod.xml
Activity Configuration OEEActivity.xml

Configuration Associated XML file
Order Status Description OEEStatus.xml
Workflow Configuration OEEWorkflow.xml
User Group Dashboard Assignment OEEUserGrpPodAssign.xml
Customization Configuration OEECustomization.xml
Reason Code Configuration OEEReasonCodeConfig.xml
Extension Configuration OEEExtension.xml
3. Enter the Pass Phrase. Choose Export.

4. Enter the target client and plant.
The system creates XML files containing the configuration data. The XML files are zipped.
5. Depending on the export method you choose, the zipped file is exported as follows:
○ File System: You save the zipped file at a secure location. You then import the configurations into the
target SAP MII systems relevant to you.
○ CTS+: The system exports the zipped file to the CTS+ system. The CTS+ system then imports the zipped
file into the target system you specified.
6. When you export using CTS+, the configurations are automatically implemented in the target system.
1.9 Configurations for Worker UIs
SAP OEE Management application provides a set of dashboards that enable the shop floor personnel to report
and view production data for production orders and process orders. Shop floor personnel can access an OEE
dashboard depending on the role assigned to them. (See OEE Dashboard [page 107] and Operator Dashboard
[page 109])
These dashboards are built based on metadata defined in the OEE master data and hierarchy definitions. (See
Master Data in SAP ERP [page 26])
You can, however, configure certain aspects of the OEE dashboards to customize them according to your
requirements. The configuration options are available in the Worker UI Management section on the SAP MII main
menu screen.
1.9.1 Configuring Activities
Use
You can configure the OEE activities that you want to use on the OEE dashboard. The activities are available for
selection when you configure the OEE dashboard.

For information on how to create activities, see SAP Note 1840786 .
You can copy the activity configurations made for one client and plant to another client and plant. To copy the
activity configurations, click on the username in the top right corner of the Activity Configuration screen and select
Copy Activity Configuration.
By default, SAP OEE provides the following standard activities:
Table 18:
Activity ID Activity URL of the Activity Description
ACT_ORD SAP-Manage Orders sap.oee.ui.oeeSelectO Show the list of orders on a line on Manage Order
rder screen. Allows start, complete, or hold of orders.
ACT_ORD_DET SAP-Order Details sap.oee.ui.orderDetai Show the details of an order on the Manage Order
ls screen. Allows the edit or order execution time
stamps.
ACT_REP_QTY SAP-Report Pro sap.oee.ui.oeeReportQ Show the reported quantities on Report Production
duced or Rejected uantity screen against finished product. Quantities can be
Quantity reported on the line.
ACT_REP_QTY_HR SAP-Report Hourly sap.oee.ui.oeeReportQ Show the reported quantities on Report Production
Production uantityHourly screen against finished product. Quantities can be
reported on hourly basis.
ACT_REV_ORD SAP-Review Order sap.oee.ui.oeeReviewO Show the consolidated data for an order. Show the
rder details for the order across all shifts.
ACT_REV_SFT SAP-Review Shift sap.oee.ui.oeeReviewS Show list of orders executed for the given shift and
hift their associated data.
ACT_REV_ORD_GRAP SAP-Review Order sap.oee.ui.oeeReviewO Show the consolidated data for an order in graphi
H with Graphical Dis rderGraphical cal display. Show the details for the order across
play all shifts.
ACT_REV_SFT_GRAP SAP-Review Shift sap.oee.ui.oeeReviewS Show list of orders executed for the given shift and
H with Graphical Dis hiftGraphical their associated data. Show the OEE KPIs in graph
play ical display.
ACT_SL SAP-Report Speed sap.oee.ui.oeeSpeedLoss Show the reported speed loss quantity and provide
Loss option to report and edit speed loss data.
ACT_SL_HR SAP-Report Speed sap.oee.ui.oeeSpeedLo Show the reported speed loss quantity and provide
Loss Hourly ssHourly option to report and edit speed loss data. Data can
be reported on hourly basis.
ACT_DOWN_LIST SAP-Manage Down sap.oee.ui.oeeDowntim Show the list of reported downtimes. Provide the
times eList option to report and edit downtimes.

ACT_RAW_MAT SAP-Report Raw sap.oee.ui.oeeReportC Show the list of raw materials used in an order-op
Material Data Collec omponents eration. Option to report the consumption.
tion
ACT_GENERIC SAP-Generic Data sap.oee.ui.oeeGeneric Show the list of configured custom data collection
Collection DataCollection elements. Data can be reported against these data
collection elements.
ACT_ORD_IND SAP-Order Inde sap.oee.ui.oeeReportO Show the list of custom data collection elements,
pendent Data Col rderIndependentDataCo which are configured to be of type order-independ
lection llection ent. Data can be reported against these data col
lection elements.
ACT_STD_VAL SAP-Standard Value sap.oee.ui.oeeReportS Show the list of standard value parameter config
Data Collection tandardValueDataColle ured for a particular work center. Data can be re
ction ported against these standard value key parame
ters.
ACT_PLANT_MONITO SAP-Plant Monitor sap.oee.ui.plantMonit Show the high-level status of the various lines in
R or the plant.
ACT_LINE_MONITOR SAP-Line Monitor sap.oee.ui.lineMonito Show the details of a line.

r
ACT_STD_PANEL_1 SAP-First Standard sap.oee.ui.oeeOperato Show the order card and list of open downtimes
Panel rDashboardStandardDel
iveredActivityForPane
l1
ACT_STD_PANEL_2 SAP-Second Stand sap.oee.ui.oeeOperato Show the current shift KPIs and list of untagged
ard Panel rDashboardStandardDel events.
l2
ACT_STD_PANEL_3 SAP-Third Standard sap.oee.ui.oeeOperato Show the line availability summary and top down
Panel rDashboardStandardDel times.
l3
ACT_KPI SAP-KPI Tile Con sap.oee.ui.oeeKpiTile Show the OEE KPIs.

tainer Container
ACT_ORDER_CARD SAP-Order Card sap.oee.ui.orderCardT Show the order card.

ile
ACT_UNTAGGED SAP-Untagged De sap.oee.ui.untaggedDe Show untagged events.

tails tailsTile

ACT_WC_STRIP SAP-WC Strip sap.oee.ui.oeeWorkcen Show the availability summary.

terAvailibilityStrip
ACT_TOP_DT SAP-Top Downtimes sap.oee.ui.TopDowntim Show the top downtimes.

es
ACT_OPEN_DOWNS SAP-Open Down sap.oee.ui.openDownsT Show the open downtimes.

times ile
DC_CONF_EXT_ACT SAP-ERP order con com.sap.xapps.oee.ext Extension to send confirmations to SAP ERP when
firmation for DC ension.extensions.Erp data is collected for an order-operation.
ConfirmationOnDCExten
sion
ORDER_CONF_EXT_A SAP-ERP order con com.sap.xapps.oee.ext Extension to send confirmations to SAP ERP when
CT firmation ension.extensions.Erp an order-operation is completed.
OrderConfirmationExte
nsion
RUN_CONF_EXT SAP-ERP order con com.sap.xapps.oee.ext Extension to send confirmations to SAP ERP when
firmation for run ension.extensions.Erp an order-operation is paused or shift is completed.
OrderConfirmationForR
unExtension
SCRAP_COMP_DC_GM SAP-ERP scrap con com.sap.xapps.oee.ext Extension to send goods movement to SAP ERP
_EXT firmation for goods ension.extensions.Erp for scrapped components when data is collected.
movement for DC ScrappedComponentGood
sMovementOnDCExtensio
n
SCRAP_COMP_GM_EX SAP-ERP scrap con com.sap.xapps.oee.ext Extension to send confirmations to SAP ERP for
T firmation for goods ension.extensions.Erp scraped components when order-operation is
movement ScrappedComponentGood completed.
sMovementForRunExtens
ion
ACT_OEE_ALERT SAP-Create Alert sap.oee.ui.oeeAlert Create alerts from dashboard for a work unit.
ACT_PM_NOTIF_LIS SAP-Manage Notifi sap.oee.ui.oeeNotific Raise notifications in the Plant Maintenance mod
T cations ationList ule of SAP ERP
ACT_RPT_PRD_MAC SAP-Report Produc sap.oee.ui.oeeReportP Show the reported quantities on Report Produc
tion on Line and Ma roductionOnLineAndMac tion screen against finished product. Quantities
chine hine can be reported at line or machine.
ACT_GENERIC_MAC SAP-Generic Ma sap.oee.ui.oeeGeneric Show the list of configured custom data collection
chine Data Collec MachineDataCollection elements. Data can be reported against these data
tion collection elements at line or machine.

ACT_ORD_IND_MAC SAP-Order Inde sap.oee.ui.oeeReportO Show the list of custom data collection elements,
pendent Machine rderIndependentMachin which are configured to be of type order-independ
Data Collection eDataCollection ent. Data can be reported against these data col
lection elements at line and machine.
ACT_SA_REV_ORD Standalone Review sap.oee.ui.oeeStandal Show data reported against an order and the
Order oneReviewOrder standard KPIs of the order.
ACT_SA_REV_SFT Standalone Review sap.oee.ui.oeeStandal Show data reported during a shift and standard
Shift oneReviewShift KPIs for the shift.
ACT_STD_COMP_GI Goods Issue sap.oee.m.goodsissue Goods Issue App
ACT_STD_COMP_GR Goods Receipt sap.oee.m.goodsreceip Goods Receipt App

t
Some activities have options, the default values of which are configured by the SAP OEE Configurations CTC:
Table 19:
Activity Option Option Description Values
ACT_ORD DEFAULT_FILTERS Default filters to be enabled ACT (Default Value)

on load of the screen. Multiple
values can be assigned. NEW (new orders)
CMPL (completed orders)
OBS (Aborted)
HOLD (orders on hold)
SHIFT (orders relevant for the

selected shift)
ACT_KPI ALLOWED_KPI KPIs to be shown on the You can maintain any of the
screen. KPIs configured in SAP ERP
for this option. By default, no
Multiple values can be as
values are maintained. The
signed.
four KPIs Availability, Per
formance, Quality, and OEE
are visible on the UI. If you
add options, then only those
KPIs are seen on the UI.

ACT_DOWN_LIST DEFAULT_TAB Tab to be defaulted on load of Default value of this option is

the screen. set to BREAKDOWN (All Down
times).
Only one value can be as
signed. You can also set the default
option to any of the following:
MINOR, LINEDOWN, or
OVERLAPPING.
ALLOW_TABS This helps you configure the OVERLAPPING

user interface for Manage
FLOWTIME
Downtime screen.
MINOR
You can use this option to re
strict the different downtime SHIFT BREAKS
tabs that you want to display
OTHERS
on the screen. All tabs except
Others are displayed by de
fault.
Multiple values can be as

signed.
SHOW_MINOR_DOWNS This enables display of minor TRUE

downtimes on the All
FALSE
Downtime tab in the Manage
Downtime screen.
Only one value can be as

signed.
ACT_GENERIC CONTEXT Data Collection (DC) Ele Provide DC element context

ments to be displayed on the in the option detail. This lists
screen, either based on the all the DC element of the con
Data Element Context or the text where ACT_GENERIC ac
Data Collection Elements. tivity is used.
DCELEMENT Provide the list of DC element

in the option detail. This lists
all the DC element where
ACT_GENERIC activity is
used.
ACT_GENERIC_MAC CONTEXT Data Collection Elements to Provide DC element context

be displayed on the screen, ei in the option detail. This lists
ther based on the Data Ele all the DC element of the con
ment Context or the Data Col text where ACT_GENERIC ac
lection Elements. tivity is used.

DCELEMENT Provide the list of DC element

in the option detail. This lists
all the DC element where
ACT_GENERIC activity is
used.
ACT_LINE_MONITOR AUTO_REF_TIME_IN_MIN Refresh interval for the Default value of this option is
screen, specified in minutes. set to 1 min.
ACT_PLANT_MONITOR LINES_TO_BE_SHOWN Lines to be shown on the You have to add this option
Plant Monitor. Can be used to manually. Assign the node IDs
control visibility of lines. of the lines that you want to
see as option values. You can
Multiple NODE_IDs can be as
find the node IDs from the
signed as values.
SAP main menu screen
Worker UI Management
Display SAP ERP Master
Data
ACT_REV_SFT_GRAPH KPI_DISP_TYPE You have to add this option TILE (Default)

manually. You can assign the
GAUGE
option value GAUGE or TILE
to change OEE KPIs display.
A single value can be as

signed.
ACT_REV_ORD_GRAPH KPI_DISP_TYPE You have to add this option TILE (Default)

manually. You can assign the
GAUGE
option value GAUGE or TILE
to change OEE KPIs display.
A single value can be as

signed.
ACT_SL EN_SPEED_LOSS_CALC Enable or disable Speed Loss FALSE (Default)

Calculator
TRUE
ACT_ORD_IND_MAC ALLOW_YIELD_ON_MACH Control whether Yield report TRUE (Default)

ing will be allowed on machine
FALSE
level.
ACT_STD_PANEL_1 NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_STD_PANEL_2 NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.

CONTEXT SHIFT or ORDER If no value or if SHIFT is speci

fied, then the panel shows the
information for the shift.
If value specified is ORDER,

then details are displayed
based on the selected order.
ACT_STD_PANEL_3 CONTEXT SHIFT or ORDER If no value or if SHIFT is speci

fied, then the panel shows the
information for the shift.
If value specified is ORDER,

then details are displayed
based on the selected order.
ACT_REV_ORD, NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_REV_SFT, NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_REV_ORD_GRAPH NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_OPEN_DOWNS NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_UNTAGGED NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_REV_SFT_GRAPH NAV_TO_DOWNTIME ACTIVITY_ID Activity to navigate to on click

of the control.
ACT_RPT_PRD_MAC ALLOW_YIELD_ON_MACH Control whether Yield report TRUE (Default)

ing will be allowed on machine
FALSE
level.
ACT_PM_NOTIF_LIST DURATION Duration (in hours) for which Default value is set to 4
the existing notifications (hours).
should be retrieved on load of
the screen
ACT_REP_QTY_HR DEFAULT_TAB Default tab to be selected on Value of this option can be a

load of the screen Data Collection Element
name.
OEE also provides the option to download the code of an activity, make changes according to your requirement
and add it as a custom activity.

You can view the change log of activity configuration in SAP NetWeaver Application logs. Search with the
category/Applications/OEE/ConfigurationLog/ActivityLog
Procedure
Create custom activity
1. On the SAP MII main menu, choose Worker UI Management Activity Configuration . The Activity
Configuration screen appears.
A list of default activities assigned to the client and plant of the user appears. The activity data is created when
you run the SAP OEE Configuration CTC wizard.
To see the list of available activities, choose the master list icon on the top left corner of the Activity
Configuration screen.
2. You can create a new activity or change an existing activity.
3. To create a new activity, enter the Activity ID.
On the Main tab:
○ Enter the class or url to the activity in your SAP Workspace
○ Choose the activity type as:
○ UI: If the activity is visible to the user
○ Transactions: If the activity is to be linked to an SAP MII transaction
○ External App: If the activity is to be linked to an external URL
4. Enter the description of the activity in the languages that you want.
5. If required, enter the Activity option names and their values.
6. You can also change or delete custom activity.
More Information
SAP OEE Configurations CTC [page 68]
1.9.1.1 Creating Generic Activity to Collect Custom DC

Elements
Procedure
1. On the SAP MII main menu, choose Worker UI Management Activity Configuration .
2. Enter a meaningful name for the activity. For example, if you are creating an activity to collect labor-related
data then you can enter the activity name as AC_LABOR_DC.

3. On the Main tab:
1. In the Class or URL field enter the sap.oee.ui.oeeGenericDataCollection. This is an SAP-delivered activity
for collecting custom data collection elements.
2. In the Activity Type field, select UI.
4. On the Activity Description tab, choose Add to enter a description for the activity in the required languages.
The description given here appears on the dashboard.
5. On the Options tab, choose Add to enter the option name, option description in the required languages, and
the option values.
Ensure that you enter the option name in Option Name field as DCELEMENT.
6. In the Options Value section, enter the data collection elements that you want to use to collect data from the
dashboard.
1.9.2 Configuring Dashboard
Use
You can configure the OEE dashboard to contain the options and activities that you require. You can define the
dashboard to have the activities you want, associate buttons to these activities, define the location and sequence
of these buttons on the dashboard.
You can copy the dashboard configurations from one client and plant to another client and plant. To copy the
dashboard configurations, click on the username in the top right corner of the Dashboard Configuration screen
and select Copy Dashboard Configuration.
You can define the languages in which the dashboards are available.
Prerequisites
Ensure that your user admin group has the permission to configure the OEE dashboard.
For more information, see the Authorization section in the SAP MII Installation Guide at http://service.sap.com/
instguides SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Integration and
Intelligence
Procedure
1. On the SAP MII main menu screen, choose Worker UI Management Dashboard Configuration .
The OEE Dashboard Configuration screen appears.
To see the list of dashboards available for the client and plant, choose the master list icon on the top left
corner of the OEE Dashboard Configuration screen.
You can define different OEE dashboards for a client and plant.

2. To change the client and plant, select the relevant client and plant from the dropdown with the user name on
the right top corner.
3. You can review an existing OEE dashboard and change its attributes to meet your requirements. You can also
change an existing custom dashboard. However, you cannot modify SAP-delivered dashboards.
4. You can view the change log of dashboard configuration in SAP NetWeaver Application logs. Search with the
category/Applications/OEE/ConfigurationLog/PodLog
Creating a New Dashboard
You can copy and make changes to an existing dashboard or create a new dashboard. Define attributes as follows:
Dashboard Details
Table 20:
Attribute How to Configure
Dashboard ID Assign a unique ID
OEE Dashboard Type Choose the dashboard type.
Dashboard Logo You can add your company logo to the dashboard. Ensure
that the logo is available in the Web folder of your SAP MII in
stance.
Enter the url to your logo in the Logo field. The system scales
the image to 96x36 pixels. You specifically add the logo to ev
ery dashboard on which you want the logo to appear.
By default, the SAP logo is displayed.
Dashboard Layout The layout determines the number of sections on the dash
board.
The Dashboard Section Content tab enables you to assign ac

tivities to the different sections of the dashboard as per your
requirement.
Dashboard Descriptions
You enter the name of the dashboard in the different languages. This allows you to maintain locale-specific
description for the dashboards.
Dashboard Buttons
You can assign existing buttons or create new ones. Choose the Dashboard Buttons tab to add buttons.
Define the attributes of a button as follows:
Table 21:
Button ID Assign a unique button ID.

Activity Assign an activity to the button.
Note
When assigning activities, for a dashboard of type Real
Time, you can assign activities of type UI. For dashboards
of type Application Launchpad you can assign activities of
type UI Component.
For example, to report raw material consumption data from

the dashboard, you create a button Raw Material. Assign the
activity SAP-Report Raw Material Data Collection to it.
Button Sequence Ensure that sequence number assigned to each button is

unique.
Button Type Specify if the button is a normal or group button. A group but
ton consists of child buttons that are of type normal. You can
assign attributes to a child button that are similar to the attrib
utes of the parent button.
Button Icon You can add icons to buttons.
Icons from the SAP UI5 library are available for selection.
Button Description Enter a description of the button in the languages required.
More Information
Configuring Extensions [page 99]
1.9.3 Configuring Order Status Description
Context
You can configure the status descriptions that you want to use when maintaining the status of an order-operation
from the OEE real time dashboard.

You can copy the order status descriptions maintained in one client and plant to another client and plant. To copy
the descriptions, click on the username in the top right corner of the Order Description screen and select Copy
Order Descriptions.
By default, SAP provides the following status options:
● New (NEW): For new orders downloaded from SAP ERP

● Active (ACTIVE): For orders that are in progress
● Hold (HOLD): For orders that are paused
● Completed (CMPL): For orders that are completed
● Aborted (OBS): For orders that are aborted
● Review (REV): For orders that were not set to complete within a shift and should be reopened in the next shift
Procedure
1. On the SAP MII main menu screen, choose Worker UI Management Modify Order Status Configuration .
The Modify Order Status Configuration screen appears.
2. When you select a status you can see the existing descriptions for a status in the different languages. You can
change the description of the status in a particular language and for a specific client and plant.
You can change the client and plant and see the existing status descriptions.
3. Choose Update to save your changes.
4. You can view the change log of order descriptions in SAP NetWeaver Application logs. Search with the
category/Applications/OEE/ConfigurationLog/StatusLog.
1.9.4 Configuring User Administration Group
Context
The OEE_SUPERADMIN role provided with the SAP OEE application has the permission to assign user
administration groups to different clients and plants within an organization. You must first assign this role to a
user in your organization who can then assign the user administration groups at plant and client node level.
Only the assigned user administration groups have permission to view configuration data for the different nodes
of a plant and client. The user with OEE_SUPERADMIN role can view all the configuration data for all the clients and
plants.
User with the OEE_SUPERADMIN role can create the following:
● User group with OEE_ADMIN role: This group can be assigned to a specific plant and are the administrators of
the plant.
● User groups with OEE_OPERATOR and OEE_SUPERVISOR role: These groups can be assigned to specific lines
under the plant where they can report order-operation data.

For more information on role-specific authorizations, see OEE Integration and Services (JAVA Layer) [page 11].
Note
The user administration groups are defined through User Management Engine (UME) actions in SAP
NetWeaver Administration Identity Management .
Procedure
1. On the SAP MII main menu screen, choose Worker UI Management General Configuration .
The General Configuration screen appears.

2. To display the plant hierarchy, choose the master list icon on the top left corner of the screen.
To change the client and plant, select the relevant client and plant from the dropdown with the user name on
the right top corner.
3. At the plant level node, on the Admin Configuration User Group Assignment tab, assign the user groups.
Assign only those user groups that are eligible to view configuration data for the different nodes of the plant.
1.9.5 Configuring User Group and Dashboard Assignment
Context
You can assign user groups and OEE dashboards to a node in the plant hierarchy, if that node:
● Reports production
● Is a work unit
Procedure
Choose the Dashboard Assignment tab.
Dashboards can be assigned to user groups on plant and line level nodes. To display the plant hierarchy
nodes, choose the master list icon on the top left corner of the screen.
For more information, see Configuring User Administration Group [page 86].

2. To change the client and plant, select Change Client and Plant from the dropdown with the user name on the
right top corner.
3. Select the relevant node from the hierarchy and make the required assignments.
4. You can assign multiple user groups and the relevant dashboards to a node.
This provides you the flexibility to have different dashboards for different user groups on the same node.
You can assign multiple dashboards to the same user group.
For example, for a work unit A, an operator can be assigned dashboard through which they can report data
and events. For the same node, a supervisor can be assigned a different dashboard using which they can read
the reported data. The supervisor can also be assigned another dashboard from where they can monitor the
plant or line data.
1.9.6 Configuring Customized Values
Use
SAP OEE provides you the option to configure the OEE application according to your requirements. The
customizations that you can configure are available based on the selected node type.
SAP OEE Configurations CTC configures the names of customizations. The customization values are specific to a
node, therefore the default values of the customizations are configured when you send a plant hierarchy IDoc
from SAP ERP to ERP-Shop Floor Integration framework. You can change these default values according to your
requirement.
For more information, see SAP OEE Configuration CTC [page 68].
Procedure
Here’s how you can customize:
1. On the SAP MII main menu screen, choose Worker UI Management General Configuration . The General
Configuration screen appears.
To display the plant hierarchy nodes, choose the master list icon on the top left corner of the screen.
2. On the Customization Configuration tab, you can maintain the values to determine:
Table 22: Worker UI Behavior
Customization Name Use
Minor Stoppages Should be Included in Availability If set to yes, the system considers minor stoppages in OEE
KPI calculations.
Irrelevant for OEE Calculation System does not consider data reported at the line for KPI
calculations.

Decimal value precision Applicable for all reported quantity and fields that require
quantity on the OEE dashboard.
Date range for order selection This is the duration in the past and future from the current
date, within which if the scheduled start date of an order
lies, the order is shown in the new, hold, or completed or
ders list.
Example
If the date range for order selection is set to 2880 mins,
and the current date is November 20, 2013, then the
system displays all the orders that have a scheduled
start date between November 18, 2013 and November
22, 2013 in the new, hold, or completed orders list.
Serial no. is mandatory for reporting production If set to yes, system does not allow reporting of production
without serial number
Shift handover available before shift end If set to yes, system does not allow reporting of production
without serial number
Unaccounted Speed Loss Limit If set to yes, order can be completed even when unac
counted time exists.
Enable Entry of Crew Size If set to yes, the system would prompt the operator to enter
the crew size when starting an order or entering a down
time.
Allow Modification of Automation Records If set to no, system does not allow any modifications to be
made to data reported through automation. If set to yes,
you can modify the records from the dashboard.
Allow multiple orders to be started at same time If set to yes, multiple orders can run at the same time.
Shrinking Order Duration Allowed If set to yes, order execution duration can be reduced.
Example
The operator reports the start of an order-operation as
10:00 am, and later realizes that the correct time is 11:00
am. If this customization is set to yes, the option to
change the time is available on the dashboard. However,
all the production data and downtime events reported in
the duration between 10:00 and 11:00 am is lost.
Allowed time limit for starting order in the past Duration within which an order in the past can be started for
reporting purposes.

Allowed Modification Limit Duration from the current time within which order related
data already reported can be modified.
Minor Stoppage Limit Duration of a downtime that is considered by the system to

be a minor stoppage. Downtimes classified as minor stop
pages are grouped together when displaying to the user.
User can assign a reason code to the group.
Order completion when unaccounted time exists If set to yes, allows to mark an order to complete even if un
accounted time exists.
Batch no. is mandatory for batch managed material If set to yes, system does not allow reporting of production
without batch number.
Relevant Production Activity User should maintain the production activities correspond
ing to the Standard Value Keys that are relevant for the line
while maintaining customizations for the plant hierarchy in
SAP MII. This enables the selection of production activity
when executing an order-operation.
Downtime Entry Type Downtime can be reported based on the duration or time
period/interval of the downtime.
By default, downtime entry type is time period based.
For more information, see Downtime Entry Types [page

116].
Allow Micro Stoppage Reporting The option to report micro stoppages is available. Smaller
stoppages can be grouped together and reported as a mi
cro stoppage by providing the total duration and the num
ber of such stoppages. By default, the value is set to 'No'.
Default UoM for Production Reporting Select the UoM that should be defaukted on the OEE dash
board for reporting and display of production quantities.
By default, Base UoM is used. If Production UoM is selected,

the production UoM of the order is used.
This customization is set at the plant level.
Table 23: Application Configuration
Default Data Collection Element – Unscheduled Down If you use your own custom data collection elements for un
scheduled downtime, then map those custom data collec
tion elements here instead
SAP OEE Application Transaction Mode Determines whether the GI-GR apps run in online or offline
mode.

Default Data Collection Element – Scrap If you use your own custom data collection elements for
scrap, then map those custom data collection elements
here instead.
Default Data Collection Element – Speed Loss If you use your own custom data collection elements for
speed loss, then map those custom data collection ele
ments here instead.
Default Data Collection Element – Scheduled Down If you use your own custom data collection elements for
scheduled downtime, then map those custom data collec
tion elements here instead.
Retention time for SAP HANA replicated tables Duration for which data in SAP HANA replicated tables to
be retained.
If you want to retain data for a particular period, then run

transaction SAPMPM/apps/DataArchive/
ArchiveHANAReplicatedTables.
Caution
Data will be deleted after the specified retention time.
Offline-Online Mode Change Transaction Enables configuration of transaction when the mode is
changed.
Online-Offline Mode Change Transaction Enables configuration of transaction when the mode is
changed.
Unit of Measure Conversion Transaction Allows conversion of quantity in particular for a given mate
rial, quantity, and UoM.
Enable Audit Log Enables audit logs of the selected objects to be displayed.
Table 24: Integration with other SAP systems
PM Notification Type Enables triggering of notification creation. Choose the noti

fication types that should available in OEE from the notifica
tion types maintained in ERP.
Enable Periodic Confirmations If set to 'Yes', OEE periodically confirms production data to
SAP ERP.
Allow Automatic PM Notification Trigger If this customization value is set to 'Yes' an approval will not
be required and the notifications are scheduled for creation
in ERP. By default, the value is set to 'No'.

SAP ERP Type OEE ERP add-on is enabled for SAP S/4HANA. You can as
sign the ERP system type available in your landscape to the
plant node.
SAP ERP Sends UOM in ISO Code IDocs sent from SAP ERP to SAP MII can carry UoMs as ISO
codes or as customer specified UoM keys. By default, the
value is set to 'Yes' indicating that the system expects ISO
Codes.
This customization is set at the plant level.
Table 25: Line Behavior
Line Behavior For information on Line behavior, see Customizations for

Line Behavior [page 93].
Caution
Line Behavior customization can be set only once as this
customization is dependent on your line structure and
KPIs to be calculated.
This is a mandatory configuration do be done manually.

System does not set any default values as it is specific to
your line structure.
Multiplier Value in Percentage For more information, see Customizations for Line Behavior
[page 93].
Order Release Mode Enables dispatch of an order quantity manually. By default,

the order release is set to Automatic (see Configuring Order
Dispatch [page 104]).
This customization is set at the line level.
3. Default values can be set at the plant node level of the hierarchy and are cascaded to the lower nodes. If a
customization value already exists at the lower nodes, then that value takes precedence over the
customization value maintained at the plant node level.
4. Customized values can be maintained for all materials or can be material-specific.
5. You can view the change log of customization configurations in SAP NetWeaver Application log. Search with
the category/Applications/OEE/ConfigurationLog/GeneralConfigurationLog.

1.9.6.1 Customizations for Line Behavior
Use
The customization of line behavior and the corresponding system behavior is as follows:
Table 26:
Line Behavior Customization Mark line down when all bot Mark line down when any Machine downtime affects
tlenecks are down bottleneck is down line (Based on Multiplier)
Order release and download On line level On line level On line level
Order-operation execution Operator dashboard operates Operator dashboard operates Operator dashboard operates
at line level. at line level. at line level.
Downtime behavior System considers the line to System considers the line to System considers the line to
be down only if all the bottle be down even if one bottle be down even if one bottle
neck machines are down. neck machine is down. neck machine is down. The
exact impact of this downtime
on the availability KPI de
pends on the Multiplier Value.
You can override the default line behavior. Choose Mark Line You can override the default
Down option when reporting downtime; this will mark the line line behavior. Choose Mark
down irrespective of the default line behavior setting. Down Line Down option when re
time can be reported on the work units: line, bottleneck ma porting downtime; this will
chine, and non bottleneck machine mark the line down irrespec
tive of the default line behav
ior setting. However, the ex
act impact of this downtime
on the availability KPI de
pends on the Multiplier Value.
Downtime can be reported on

the work units: line, bottle
neck machine, and non bottle
neck machine

Line Behavior Customization Mark line down when all bot Mark line down when any Machine downtime affects
tlenecks are down bottleneck is down line (Based on Multiplier)
KPI calculation Availability KPI is impacted Availability KPI is impacted when:

when:
1. Downtime is reported on the work unit representing the
1. Downtime is reported on line.
the work unit represent 2. Any downtime is reported on a bottleneck machine.
ing the line. 3. Downtime is reported on a non‑bottleneck machine with
2. A downtime on a bottle the Mark Line Down option selected.
neck machine impacts
the availability of the line
if all the bottlenecks are
down. If any of the bottle
neck machines is up dur
ing the time period, there
is no impact on the avail
ability of the line
3. Downtime is reported on
a non‑bottleneck ma
chine with the Mark Line
Down option selected.

Table 27:
Line Behavior Customization Multi-Capacity Multi-Line Multi-Capacity Single-Line Multi-Capacity Represents

Representation Representation Single-Line (Based on Multi
plier)
Note
For Process orders, the
customization Order Re
lease Mode should be
configured as Manual
Order release and download On capacities. On line level On line level
Order is released on work unit Prerequisite: Prerequisite:

capacities depending upon
Ensure that the workflow for Ensure that the workflow for
the quantities assigned to the
IDoc LOIPRO01 is modified IDoc LOIPRO01 is modified
individual capacities on order
and a partner or customer and a partner or customer
release in SAP ERP or from
XSLT overrides the standard XSLT overrides the standard
the SAP MII main menu
delivered XSLT. delivered XSLT.
screen Worker UI
The partner or customer The partner or customer
Management Order
XSLT should map the XSLT should map the
Dispatch . numberOfCapacities tag numberOfCapacities tag
under the segment under the segment
productionOrderProcesse productionOrderProcesse
s to the number of capacities s to the number of capacities
to be used for executing an to be used for executing an
order. This would depend on order. This would depend on
the IDoc in use. the IDoc in use.
The exact impact of a ma

chine downtime on the availa
bility KPI depends on the Mul
tiplier Value.

plier)
Note
Order-operation execution Order start is allowed at the Operator dashboard operates Operator dashboard operates
work unit capacity. at line level. at line level.
Operator dashboard operates When starting an order, the When starting an order, the
the work unit capacity with operator has to select n num operator has to select n num
each capacity acting as a se ber of capacities where n is ber of capacities where n is
lectable work unit on the op the number of capacities re the number of capacities re
erator dashboard. quired for executing the order quired for executing the order
as maintained during order as maintained during order
release. If capacities are not release. If capacities are not
selected order-operation is selected order-operation is
run on the work unit. run on the work unit.

tiplier Value.
Downtime behavior Production and downtime Production and downtime can Production and downtime can
data can be reported on the be reported on machines or be reported on any of the ca
work unit, machines, or on the any of the capacities associ pacities associated with the
individual capacities associ ated with the work unit. Sys work unit. System considers
ated with the order-operation. tem considers the reported the reported data collectively
System considers the re data collectively on the work on the work unit.
ported data separately for unit.
each capacity.
tiplier Value.
Downtime can be reported on the work units: line, bottleneck machine, non bottleneck ma
chine, and work unit capacity.
Downtime reported on a bottleneck machine affects the parent capacity.

plier)
Note
KPI calculation Availability KPI is impacted KPIs are calculated by consid KPIs are calculated by consid
when: ering the number of capaci ering the number of capaci
ties to be used. ties to be used.
the work unit represent Availability KPI is impacted
ing the line.
Example
when:
2. Any downtime is re If an order executes for 60
ported on a bottleneck mins and uses 5 capaci
the work unit represent
machine. ties, then the loading time
ing the line.
3. Downtime is reported on would be 60 * 5 = 300
2. Any downtime is re
a non‑bottleneck ma mins.
ported on a bottleneck
machine.
Down option selected. Availability KPI is impacted
4. Downtime is reported on when:
a work unit capacity. 1. Downtime is reported on chine with the Mark Line
the work unit represent Down option selected.
ing the line.
4. Downtime reported on a
2. Any downtime is re work unit capacity.
ported on a bottleneck
machine.
tiplier Value.
Down option selected.
4. Downtime reported on a
work unit capacity.
Customizations for assigning downtime weightage to machines
A bottleneck machine or a machine when down may not be impacting the line completely. It is possible that the
line’s KPIs are affected only partially.
The customization Effect of Machine Down on Line (in Percentage) allows you to maintain the value (in
percentage) which denotes the affect a machine downtime will have on the KPI of a line. This customization is
maintained at machine level.
System considers the value of this customization if you have set the customization value of Line Behavior as
Machine Downtime Affects Line (Based on Multiplier).

Example
Consider a line has a machine M1, and two parallel bottlenecks M2 and M3. The customization value for Line
behavior is selected as Machine Downtime Affects Line (Based on Multiplier).
Table 28:
Machine/Bottleneck Effect of Machine Down on Line (in Effect of Machine Down on Line KPIs
Percentage)
M1 0% If this machine is reported as down with

Impacts Line checked, the system will
still consider that the Line KPI is not im
pacted at all.
M2 50% If this bottleneck machine is reported

as down, the system will consider 50%
of this downtime duration as the impact
on Line KPIs
M3 50% If this bottleneck machine is reported

as down, the system will consider 50%
of this downtime duration as the impact
on Line KPIs
More Information
Configuring Customized Values [page 88]
1.9.6.2 User-defined Customizations
Context
You can define your own customizations and maintain their values:
1. Use the transaction CustomizationCreateUpload to configure user-defined customization. The

transaction is available in the SAP MII workbench Catalog SAPMPM .
2. Transaction CustomizationValueRead allows you to read (including SAP standard customizations) and
CustomizationDelete allows you to delete user-defined customization.
For more details, see 2483181 .
3. After you have configured the customization, you can view them and maintain their values in the User-Defined
section on the Customization Configuration tab in General Configuration screen.
With user-defined customizations, you can centrally manage your customization even for custom developed
code.

1.9.7 Configuring Reason Code Mapping
Context
You can assign the most relevant reason codes that are applicable to the machine and work center nodes. You
select the relevant subset of reason codes from the pool of reason codes that are configured in SAP ERP. Events
on the nodes can then be reported on these reason codes.
For more information, see:
● Customizing for Define Global Reason Codes under Production Overall Equipment Effectiveness .
● Creating Plant Reason Codes [page 30]
Procedure

2. Reason Code Configuration tab is available on nodes of type work center and machine. You can assign the
reason codes relevant to a node.
3. Choose a relevant data collection element and select the reason code that you want to assign.
The reason codes that you assign here are available for selection when events are reported against the
associated data collection element on the OEE dashboard.
If you do not assign any reason codes here, then the system displays all the reason codes associated with the
data collection element from the master data. For more information, see Creating Plant Reason Codes [page
30].
1.9.8 Configuring Extensions
Use
You can use extensions to change or enhance the logic of a method. You can add, edit, or delete extensions
assigned to different methods.
Methods are assigned to nodes that report production.

Procedure
1. On the SAP MII main menu, choose Worker UI Management General Configuration. .
The Extension Configuration tab is available on nodes that report production.
2. Select a method from the list of methods. List of existing extensions is displayed.
By default, the following extensions are provided:
○ SAP-ERP confirmation on order complete (ORDER_CONF_EXT) on the service method Complete Order
○ SAP-ERP confirmation on order stop/shift complete (RUN_CONF_EXT) on the service methods Stop Order
and Close Shift
○ ERP confirmation on reporting quantity (DC_CONF_EXT) on the service method Report Data
If you want to report data on completed orders then enable this extension so that data on completed
orders can be confirmed to SAP ERP.
You can edit or delete an existing extension. You can also add an extension.
3. Define when the extension should run. For this, select the corresponding type as follows:
○ Pre: Extension runs before the method.
○ Post: Extension runs after the method.
○ Exception: Extension runs to handle an error that occurs during the method run.
4. Specify the sequence. This determines the order in which the extensions are executed. The same sequence
can be assigned to multiple extensions.
5. Enable the extensions that you want.
Creating New Extensions
1. Create an SAP MII transaction with the transaction parameters XMLInputString, XMLOutputString, and
XMLModifedOutputString with data type as XML.
These XMLs provide the transaction with the input and output arguments of the method you want to extend.
Save the transaction.
2. From the SAP MII main menu screen, choose Worker UI Management Activity Configuration .
Enter the activity ID for the new activity. Enter the URL of the SAP MII transaction in the Class or URL field.
Select the activity type as Transaction.
Save your entries.
3. On the OEE User Assignment screen, select the Extension Configuration tab.
In the Method section, select the method that you want to extend.
4. Select the activity that you created and save your entries.
For more information on the request and response xmls of the extensible APIs, see SAP Note 1844194 .

1.9.9 Configuring Scheduled Downtime
Context
You can view downtimes existing in the system. You can also maintain downtimes for maintenance activities,
public holidays, and company specific downtimes as scheduled downtimes using Load From Calendar. You can
maintain these downtimes for the client and plants for which you have authorizations.
The highest node at which a scheduled downtime can be maintained is the work center node (see Creating Plant
Hierarchy [page 27]).
Procedure
1. On the SAP MII main menu screen, choose Worker UI Management Scheduled Downtime Maintenance .
2. Select the client and plant for which you want to maintain scheduled downtimes. You can view existing
scheduled downtimes and maintain new ones.
○ Select the time period for which you want to retrieve the scheduled downtimes. System displays the
scheduled downtimes occurring within that time period.
○ To create a new scheduled downtime from the factory calendar, choose Load From Calendar. Filter on the
date range within which you want to see the scheduled downtimes.
○ Select the records that you want to save as scheduled downtimes.
○ Assign a reason code. Depending on the client and plant, system displays the reason codes configured as
type scheduled down.
Note
You cannot maintain a new scheduled downtime if there is an existing scheduled downtime that has
the same start time. System does not allow you to maintain overlapping scheduled downtimes.
3. You can also add or delete a scheduled downtime from the real-time OEE dashboard.
To do this:
1. On the SAP MII main menu screen, choose Worker UI Management OEE Dashboard Manage
Downtime . Choose the Report New option.
2. Select a work unit. To report a scheduled downtime, choose Skip Assignment. The Manage Downtime
screen appears.
3. Select the downtime type as Scheduled Downtime.
Enter the downtime data such as start time, end time, and duration.
4. System creates a scheduled downtime.

1.9.10 Uploading OEE Data
Context
You can upload OEE-relevant configuration and transaction data to OEE. You format the data in CSV files
according to the templates provided. System makes the configurations or uploads the transactional data as
specified in the CSV files you upload.
You can upload reason code assignments to machines data, downtimes, and the OEE Plant Hierarchy as Plant
Information Catalog (PIC) in SAP MII.
Procedure
1. From the SAP MII main menu screen, choose Worker UI Management Data Upload . The Data Upload
screen appears.
2. Choose Download Templates to download all available templates.
3. Format your data according to the format specified in the corresponding template. Save the file as a CSV file
in your SAP MII workspace.
Note
The template for downtime data displays the MS Windows time stamp format configured in your machine.
However, the time stamp format in which data should be maintained in the CSV file is mm:dd:yyyy
hh:mm:ss. Ensure that you enter the data in the specified format.
4. Browse to the CSV file and choose Upload File.
The system reads the CSV file and makes the relevant OEE configurations as follows:
Table 29:
Data Uploaded System Response
Downtimes System updates the relevant OEE tables with the down
times or custom events (custom data collection elements
You can use the Data Upload option to upload mass data
of type Time Duration) data from the CSV file.
and use it as an alternate way to maintain downtimes avail
able on the General Configuration screen.
For more information, see Manage Downtimes [page 113].

Data Uploaded System Response
Reason Code Assignments to Machine System assigns the reason codes to the plant hierarchy no
des.
You can use the Data Upload option to upload mass data
and use it as an alternate way to maintain reason code as You can see the assignment on the SAP MII main menu,
signment available on the General Configuration screen. choose Worker UI Configuration General Configuration
For more information, see Configuring Reason Code Map Reason Code Configuration .
ping [page 99].
1.9.11 Configuring Custom Translations
Use
OEE provides the flexibility of using custom translation texts. You can replace the standard OEE texts with custom
translations in any relevant language.
Procedure
To enable use of custom translations:
1. From the SAP MII main menu screen, choose Worker UI Management Data Upload .
2. On the Data Upload screen choose Download Templates to download the .xlf files for the standard languages
supported by OEE.
3. Update the .xlf files with your custom translations.
4. Save the file with the filename OEEUITexts_<XX>, where XX is the ISO code of the language of the custom
translation.
5. Upload the .properties file in SAP MII workbench under the Web project SAPOEE_CUSTOM in the
ResourceBundles folder.
6. Clear your browser's cache.

1.9.12 Configuring Order Dispatch
Prerequisites
Enable manual dispatch of order in one of the following ways:
● Configure the value of the customization Order Release Mode to Manual.

This configuration is at the line level. By default, the customization value is set to Automatic.
● Configure an Extensible Stylesheet Language Transformations (XSLT) transaction in the workflow
configuration for LOIPRO01 that disables the auto release of the order.
Note
If the workflow configuration has disabled auto release or if any of the work center on which an order is
released has the customizing value set to Manual, then the order can only be released manually.
Context
You can dispatch partial quantity for an order both manually and automatically.
Procedure
1. On the SAP MII main menu screen, choose Worker UI Management Order Dispatch . The Order Details
screen appears.
A list of orders corresponding to the default client and plant are displayed along with the details of the
selected order.
2. To change the client and plant, click the dropdown with the user name on the top right corner and choose
Change Client and Plant.
3. To see the list of orders for the client and plant, choose the master list icon on the top left corner of the Order
Details screen.
4. Select an order from the list. This displays the list of operations/phases for that order.
5. You can also filter for orders based on:
○ Status:
○ Created in ERP
○ Released in ERP
○ Partially Dispatched to Shop Floor
○ Fully Dispatched to Shop Floor
○ Scheduled Start and End Date Range

○ Material
○ Work Unit
6. Enter the quantity to be dispatched for each operation. By default, this value is defaulted to the operation/
phase quantity based on the master data.
7. Choose Dispatch Quantity.
If the entered quantity is less than the operation quantity, the operation/phase with the partial quantity is
dispatched and is available on the OEE dashboard. Production run data can be reported for this dispatched
operation/phase.
Note
The Dispatch Quantity option is available only if the order is released in SAP ERP.
8. When the total quantity released equals target quantity, the order is marked as completely dispatched and is
not available for dispatch anymore.
1.9.13 Display SAP ERP Master Data
You can view the master data for a plant hierarchy as maintained in SAP ERP. When you select a plant hierarchy
node, the system displays the node-relevant master data.
By default, system displays plant hierarchy data of the client and plant assigned to the user. You can also view
data of a different client and plant.
To view the plant hierarchy data, from the SAP MII main menu screen, choose Worker UI Management
Display SAP ERP Master Data .
To display the plant hierarchy, choose the master list icon on the top left corner of the screen.
1.9.14 Configuring Plant Maintenance Notification
Use
OEE provides an option to trigger creation of plant maintenance (PM) notification in ERP from the OEE dashboard.
You can trigger notifications for downtime events already reported or trigger one when reporting a new downtime.
In case a machine needs maintenance, you can also trigger a notification without reporting an associated
downtime event.
You can monitor the status of the notification, for example, whether your request to create notification was
approved or rejected. You can decide if you want a notification triggered by an operator to be directly sent to ERP
or if you want a supervisor to approve it before sending.
OEE provides a customization Allow Automatic PM Notification Trigger for this. If approved, the notification is
queued for creation in ERP and after creation the notification number is updated against the notification.

Prerequisites
You have implemented SAP Note 2217030 .
Process
To enable triggering of PM notification, do the following:
1. Configure customizations
1. Assign the customization PM Notification Type to plant hierarchy nodes where you want to enable
triggering of notification creation. Choose the notification types that should available in OEE from the
notification types maintained in ERP.
Caution
Ensure the notification types that you add are available in ERP otherwise the notification will not be
created in ERP.
2. Configure the customization Allow Automatic PM Notification Trigger

If this customization value is set to "Yes" an approval will not be required and the notifications are
scheduled for creation in ERP. By default, the value is set to "No".
2. Configure Activity
OEE provides the activity ACT_PM_NOTIF_LIST for PM notification. The activity is not included as part of
standard dashboard. You can add the activity in the custom dashboard:
3. If you want to be able to trigger PM notification creation from the Manage Downtime screen, add the activity
option ALLOW_PM_NOTIF in the activity ACT_DOWN_LIST.
For more information, see Creating Plant Maintenance Notification [page 106].
1.9.14.1 Creating Plant Maintenance Notification
Use
You can create a PM notification for a work center or machine available. If the system does not find a shift for the
current time, it picks a period six hours prior to the current time. You can also choose a shift of your choice. You
can add the activity option DURATIONof activity ACT_PM_NOTIF_LIST to overwrite the period which the system
considers if shift is not found.
Procedure
To create a PM notification:
1. From the dashboard, choose the button to which you assigned the activity.

2. You can view all the notification creations triggered for the selected work center in the selected shift.
3. To create a new PM notification, choose a technical object assigned to the machine.
Note
Technical objects are assigned to machines while creating the plant hierarchy in ERP. If technical objects
were not assigned, you will be unable to create PM notifications for that machine.
4. Enter the required information such as notification type, start time and so on. Select the Breakdown
checkbox, if the machine has broken down.
5. System lists the notification with the status as Pending Approval. This is if you have chosen to include an
approval step before sending the notification to ERP by setting the customization value of Allow Automatic PM
Notification Trigger to "No".
6. If approved, the PM notification is scheduled for creation in ERP. After the notification is created in ERP, the
notification number is displayed in OEE. If rejected, a notification cannot be scheduled for creation. You have
the option to delete the rejected notifications.
7. You can make changes to a notification after it is already created in ERP. Depending on the customizing,
changes are either automatically sent to ERP or sent after approval. Changes or updates made to the
notification in ERP can also be synced back into OEE.
Creating a Downtime and PM Notification Simultaneously
Prerequisite
Ensure that you have added the option ALLOW_PM_NOTIF in the activity ACT_DOWN_LIST and configured it in a
custom dashboard.
For more information, see Configuring Plant Maintenance Notification [page 105].
1. From the Manage Downtime screen, create a downtime. You have the option to create a PM notification for
the downtime from theReport Downtime dialog box.
2. Select the relevant functional location.
System creates the request for PM notification and lists it along with the other PM notifications triggered for
that machine in the selected shift.
3. You can also create a notification for an existing downtime. The information for notification is defaulted from
the downtime record.
The status for notifications created from the Manage Downtime screen is displayed alongwith the other
notifications created for that machine.
1.10 OEE Dashboard
Use
SAP OEE application delivers a set of user interfaces (dashboards) for the shop floor personnel. These
dashboards are installed on the local SAP Manufacturing Integration and Intelligence (SAP MII) plant systems.
They enable collection of production data with respect to SAP ERP production orders or process orders.
The dashboards are built based on the metadata defined in the master data and hierarchy definitions.

SAP OEE provides you the flexibility to configure these dashboards as per your requirements.
For more information, see Configuring OEE Dashboard [page 83].
When a user logs in for the first time, the default dashboard configured for the user appears. The dashboard is
displayed based on the user group and OEE dashboard assignment. For more information, see Configuring User
Group and OEE Dashboard Assignment. [page 87]
SAP OEE dashboards support the Gregorian calendar.
By default, SAP provides the following OEE dashboards:
Table 30:
Dashboard Use
Plant Monitor View the high level status of the various lines in the plant. You
can go to the line monitor from plant monitor to view the line
data.
Line Monitor View the details of a single line.
Operator Dashboard Enter data from the shop floor for an order-operation run.
Enter production relevant data offline (not in real time mode)

during a shift or after a shift has closed.
You can use the dashboard to start orders in the past, report
production in the past, report downtimes that occurred in the
past, or complete orders in the past. You can enter data on an
hourly basis.
Application Launchpad By default, you can launch the Goods Issue and Goods Re
ceipt apps from the Application Launchpad. You can add
more tiles to the Launchpad, for example the OEE dashboard.
You can determine the behavior of the SAP OEE dashboard by configuring the relevant customization values and
activities. For more information, see Configuring Customized Values [page 88] and Configuring Activities [page
74].
More Information
Configurations for Worker UIs [page 74]

1.10.1 Operator Dashboard
Use
The standard OEE operator dashboard for the operator allows you to:
● Provide visibility into shift operations

● View a list of available orders and start, hold, and complete an order
● Report produced quantities

● Report downtimes
● Report speed loss
● Review the executed orders
The layout and activities possible from the dashboard are based on the configurations made for the dashboard.
For more information, see the topics under Configurations for Worker UIs [page 74].
Prerequisites
Relevant user group to dashboard assignment is made for your user group.
For more information, see Configuring User Group and OEE Dashboard Assignment [page 87].
Features
The default OEE dashboard provides the following shop floor information in context of the selected work unit and
shift:
● Active orders and associated production data

The dashboard supports multiple orders running simultaneously on a work unit. You can filter for new orders.
You can also filter and review orders that are in different states such as active, on hold, or completed.
The order card always shows the updated status of the selected order-operation and provides an overview of
all the order-operations that are active or started in the selected shift.
From the order card on the dashboard, you can choose a different order active on the work unit and view the
details.
For more information, see Manage Orders [page 110].
● Work unit and shift in progress
The context of the dashboard depends on the work unit. The dashboard displays shop floor data based on the
selected work unit and shift.
You can report production data for order-operations that belong to the work unit and the selected shift. For
more information, see Report Production [page 117].
If you do not see any shift-related information on the dashboard, check the master data setup. For more
information, see Transfer of Work Centers and Capacities [page 58].
● Performance strip: This strip displays the downtimes on the work unit that occurred in the past eight hours.
● Open downtimes: These are downtimes that are still ongoing and have not been reported up.

For more information, see Manage Downtimes [page 113].
● Untagged events: These are downtimes for the current order-operation for which a reason is not assigned.
● OEE KPIs: These KPIs indicate the trend in which the shift is progressing.
● Alerts: The alert icon on top right-hand corner of the dashboard indicates that there are alerts. Choose the
icon to see the details of the alert. The system notifies if alerts are raised for the role assigned to the user.
Alerts are assigned to roles in SAP MII.
Click the alert icon to see the event that caused the alert, change the status of the alert to in-progress or
acknowledge. For a high alert, OEE automatically displays the high alert information in a dialog box.
● Speed loss: You can report data for unaccounted speed loss that occurred on an order-operation.
For more information, see Report Speed Loss [page 116].
● Review the shift: You can review and edit data reported for the order-operations that ran during a shift. For
more information, see Review Shift [page 119].
More Information
● Configuring OEE Dashboard [page 83]

● Configuring Reason Code Mapping [page 99]
● Configuring Activities [page 74]
1.10.1.1 Manage Orders
Use
The OEE dashboard enables you to view all the order-operations that belong to the selected shift. Details such as
planned quantity, total produced quantity, order-operation status, and so on, are displayed.
From the OEE dashboard, you can:
● Start an order-operation
● Enter crew size of the team working on the order-operation
● Put on hold or resume an order-operation
● Set an active order-operation back to status new. This is possible only if no data has been collected for the
order-operation.
● Assign or change the production activity assigned to an order-operation
● Complete an order-operation
● Abort the execution of an order-operation. Order-operations on hold can be aborted. Data reported on the
order-operation while it was active is considered in KPI calculations.
● Search and filter order-operations based on order number, phase, material, status, shift, and so on
● Sort order-operations based on status, planned start or actual start
● View and edit order execution details such as start date and time. You can also see who made the last
changes.

Procedure
To start or resume an order:
1. Choose the Manage Orders button from the footer of the dashboard.
The Select Order screen appears.
2. By default, the active order-operations are displayed. To see orders that are new, on hold, or completed select
the relevant option.
3. Depending on the status of the order-operation, you can do the following:
Table 31:
Order-Operation Status What You Can Do System Response
New Start an order-operation When entering data in real time:
When you start a new order, by default

the system time is the start time of the
order-operation. You can change the
start time, however, ensure that start
time falls within the duration of the se
lected shift.
When entering data for past shifts:
When you start a new order belonging

to a past shift, the system prompts for
the Target Status of the order-opera
tion. The target statuses imply the fol
lowing:
○ Active: The order-operation

started at the specified time con
tinues to be Active at the Current
time
○ Hold: The order-operation was put
on hold at the specified time. Sys
tem prompts to enter a time when
the order was put on hold.
○ Completed: The order-operation
was completed at the specified
time.

Active Put on hold or set to complete When entering data in real time:
When you set an order to complete, by

default the current system time is the
end time of the order-operation.
You can change the end time, however,

ensure that the time falls within the du
ration of the selected shift.

lowing:

time
time.
Set to new If no data is collected for the order-op

eration system reverts the order back
If you have inadvertently started an or
to status new.
der-operation, you can set it back to
new.
To set an active order-operation back

to new, on the Manage Order screen,
choose Details Set to New .

Hold Resume an order or set the order to When entering data in real time
complete
When you set an order to complete, by
default the current system time is the
end time.
You can change the end time, however,

ensure that the time falls within the du
ration of the selected shift.

lowing:

time
time.
Completed No change is possible
Aborted Set the order-operation back to hold or When you set the order-operation to
set it to completed. complete, OEE sends a confirmation to
SAP ERP.
4. To see the execution summary of an order-operation, click the Details button.

You can change the start and end time of an order-operation interval within the shift boundaries of that
interval. For order-operations in Hold or Resume status, the change in start or end time should not overlap
with the start or end times of the consecutive intervals that fall within the same shift.
The crew size in the last interval is displayed on the order card.
1.10.1.2 Manage Downtimes
Use
Downtimes are considered in the OEE KPI calculations and indicate how they affect the progress of the shift.
SAP OEE supports both automatically and manually reported downtimes. Downtimes can be reported based on
their time stamp or duration.

From the OEE dashboard you can:
● Report downtimes of type:

○ Scheduled
○ Unscheduled
○ Flow time (on a line)
○ Changeover (on a line or bottleneck machine)
● Report custom downtimes
1. To be able to report custom downtimes, you define a custom data element of type Time and category
Loss in the Customizing for OEE in SAP ERP.
2. Define a corresponding data collection element that is transferred to SAP MII. Note that this custom data
collection element is not considered in standard OEE calculations.
3. The custom defined data element is available from the Manage Downtime screen for reporting.
● View and edit open downtimes: change the start and end time, duration, type of downtime. You can also
assign reason code and the machine affecting the downtime.
● Report end of downtime.
● View untagged downtimes and assign reason codes to them
● Delete a downtime
● Split a downtime and assign different reason codes
● View shift breaks as defined in the shift definition master data in SAP ERP
● Enter the crew size that worked on resolving an unscheduled downtime or a changeover
Activities
1. Choose Manage Downtime button from the footer of the OEE dashboard. The Manage Downtime screen
appears.
You can see all the downtimes that were reported for the order-operation during the selected shift.
2. To report a new downtime, choose Report New from the footer of the Manage Downtime screen.
By default, system creates an unscheduled downtime.
3. Select the work unit on which you want to report downtime. The Select Work Unit dialog box appears.
Bottleneck machines are highlighted.
Assign the reason for the downtime.
4. To report a scheduled downtime, choose Skip Assignment on the Select Reason Code dialog box.
Change the downtime type to scheduled down. Assign the reason for the downtime.
5. Enter the start time.
System considers a downtime as an open downtime until the end of the downtime is not entered. Open
downtimes can also be edited from the dashboard.
Note
Open downtime durations are considered in OEE KPI calculations. The downtime duration considered is
calculated as Current Time – Downtime Start Time.

6. OEE handles downtimes as follows:
Table 32:
Type of Downtime Definition System Response
Minor Stoppage Downtime duration less than or equal All minor stoppages are grouped to
to the duration customized as minor gether. This makes it easier to assign
stoppage. reason codes to the losses.
For more information, see Configuring

Customized Values [page 88].
All Downtimes All downtimes except minor stoppages

are displayed. You can configure the
system to show minor downtimes. For
more information, see Configuring Ac
tivities [page 74].
Line down All downtimes that the system recog Downtime is considered in OEE and
nizes as downtimes impacting the line availability KPI calculations.
KPIs are displayed.
Depends on the line behavior defined in

Customizing.
For more information, see Configuring

Customized Values [page 88]
Shared downtime Downtime whose time interval overlaps You can assign a downtime to one or
two or more order-operations. more order-operation overalapping
with the downtime interval to indicate
the order-operation(s) impacted by the
downtime.
To assign a shared downtime to an or

der-operation, choose the Details but
ton. Select the downtime and choose
Assign to Order. Choose the order-op
eration(s) to which you want to assign
the downtime.
Flow time Flow time is the time taken, after pro Downtime is considered in OEE and
duction starts, for the material to reach Availability KPI calculations.
the entire line. It is a non productive
To be able to report flow time, you con
time and the system subtracts it from
figure a data collection element for
the Loading Time.
flow time in the Customizing activity
Define Data Collection Element in SAP
ERP and transfer this to SAP MII.

1.10.1.2.1 Downtime Entry Types
Use
SAP OEE provides the option to make downtime entries in two ways:
● Time interval based: You mention the start and end time of the downtime.
● Duration based: You enter the duration of downtime.
In duration based, the different types of downtimes are handled as follows:
○ Scheduled downtime: System links the downtime to the shift in which it is reported.
○ Unscheduled downtime: Operator selects the order-operation that is impacted by the downtime.
Plant maintenance notification is not possible with duration based downtime.
Prerequisites
You have configured the customization Downtime Entry Type.
For more information, see Configuring Customized Values [page 88].
1.10.1.3 Report Speed Loss
Use
When good quantity produced in a particular duration is lower than the quantity that should be produced at the
standard rate of production, then this loss in quantity is expressed as speed loss. Speed loss needs to be
accounted for as it is a factor used in calculation of the performance KPI. It is expressed in units of time.
If there is a speed loss during the current order-operation, you can see it in the Untagged section on the OEE
dashboard.
Activities
To account for speed loss:
1. On the OEE dashboard, choose Speed Loss button from the footer or choose Speed Loss from the Untagged
section. The Speed Loss screen with a summary of the order-operation appears.
2. Choose Split.
The Open Speed Loss dialog box appears.
A speed loss calculator is available that you can use to calculate the unaccounted time. You can calculate the
unaccounted time based on either the quantity produced or actual speed of production. To enable the
calculator, copy the activity ACT_SL and add the option EN_SPEED_LOSS_CALC to the activity. The default
value of this option is set to False.

3. You can split the speed loss time into smaller durations. Assign the reasons that caused the speed loss. You
can also assign the machine that caused the speed loss.
4. You can also edit or delete an already accounted-for speed loss.
1.10.1.4 Report Production
Use
You can report the following production data on a line from the OEE dashboard:
● Good quantity
● Scrap quantity and the reason for the scrap
● Rework and the reason for the rework
OEE also provides an option to report data at the machine level. For more information, see Machine-Level Data
Collection [page 118].
Activities
To report production:
1. Choose Report Production button from the footer of the dashboard.

The Report Production screen appears.
2. To report new data, enter the quantity for the relevant production data parameter. Assign reason codes and
add comments where required.
You can report quantities in a UoM that is not the standard UoM for the material as configured in the backend
SAP ERP. The system converts the reported quantity into the standard UoM and displays the quantity in the
standard UoM.
The good quantity you report is taken into account and the system updates the quantities total produced
quantity and total remaining quantity displayed in the order card.
3. You can view data which has already been reported for the order-operation. To do this, choose the Details
button for the relevant production data parameter.
For a reported quantity, you can:
○ View detail such as the date and time when a quantity was reported
○ View who reported the quantity
○ Delete reported quantity if the order-operation is still active
If the order-operation is set to compete, only authorized users can edit the reported quantities.
4. OEE confirms production to SAP ERP based on the status at which you choose to confirm production data:
production is reported, order is completed, or shift is completed. If customization is not maintained, OEE
confirms production data to SAP ERP on completion of order-operation.
For more information, see Configuring Extensions [page 99].
5. Choose Save.

1.10.1.4.1 Machine-level Data Collection
Use
OEE provides the option to report data at machine level. Activities are provided that enable this reporting. The
activities allow you to report data that impacts line, generic data, and order-independent data at machine level.
If you report data at machine level that has an impact on the data reported on the corresponding line, you have
the option to mark such data accordingly. System considers this data in OEE KPI calculations.
Activities
Depending on the type of data you want to collect at machine level, configure the following activities on a custom
dashboard:
Table 33:
Data Collection Type Activity URL
Data impacting line ACT_RPT_PRD_MAC sap.oee.ui.oeeReportProductionO

nLineAndMachine
Generic data collection ACT_GENERIC_MAC sap.oee.ui.oeeGenericMachineDat

aCollection
Order-independent data at machine ACT_ORD_IND_MAC sap.oee.ui.oeeReportOrderIndepe

level ndentMachineDataCollection
The line and all the assigned machine are displayed. You have the option to report data directly on the line or any
of the machines.
Note
The activities are available from the SAP MII main menu Worker UI Management Activity Configuration .
More Information
Report Production [page 117]

1.10.1.5 Review Shift
Use
You can review and edit data reported for a shift.
Shift review enables you to review historical data for shifts. You can change the reported data if you are still within
the duration allowed for modification.
Note
The system administrator configures the duration within which modification is be allowed. For more
information, see Configuring Customized Values [page 88].
Prerequisites
Data for a shift can be reviewed by users who have any one of the following roles, OEE_SUPERVISOR,
OEE_OPERATOR, or OEE_SUPERADMIN assigned to them (see OEE Integration and Services (JAVA Layer) [page
11]).
Activities
1. You can launch the review shift screen from:

○ SAP MII main menu screen
Choose Worker UI Management Review Shift . The Review Shift screen appears.
○ OEE dashboard
Choose the Review Shift button from the footer on the OEE dashboard. The Review Shift screen appears.
2. System displays data that belongs to the default work unit assigned to your user and role and the current
shift. To see data for a different shift or work unit, change the work unit or shift as per your requirement.
Select the date for which you want to see the data.
3. You can review shift data for the order-operations that are active or completed in a shift.

For a selected order-operation, you can:
Table 34:
Review Edit
○ Order card ○ Edit or assign reasons to untagged events

○ Top downtimes for the order-operation in the selected ○ For shared downtimes, assign the downtime to an or
shift der-operation
○ Top five reasons for the downtimes
○ Order-operation KPIs and shift KPIs
○ Data reported for the customized data collection ele
ments, such as water, oil
○ Order-independent data that was reported in the shift
○ OEE time elements and the corresponding OEE KPIs
4. Choose the Shift-related data option to view the shift KPIs and the availability summary. You can also see the
order-independent data reported in the shift.
5. Shift Handover button in the footer enables you to complete shift handover tasks like entering the name of the
person to whom the shift is being handed over, any shift related comments, and logging out. You also get an
overview of the orders that are being moved to the next shift.
1.10.1.6 Report Other Data
Use
You can configure the OEE dashboard to collect production related data as per your requirement. For example,
you may want to collect data such as power or water consumed for an order-operation, which is data that is not
collected using standard OEE data collection options.
Procedure
To collect custom production data, do the following:
1. Configure the activities that correspond to the data you want to collect.
You can configure an activity as follows:
1. On the SAP MII main menu screen, choose Worker UI Management Activity Configuration . The
Activity Configuration screen appears.
2. On this screen, you configure the activity that you want to access from the dashboard.
To configure an activity to collect custom data collection element, enter the URL
sap.oee.ui.oeeGenericDataCollection. This is an SAP-delivered activity for collecting custom
data collection elements.
For more information on how to configure an activity to collect custom data, see the Create generic
activity to collect custom data collection elements section in the topic Configuring Activities [page 74].

Note
Ensure that before you configure the activity, you have defined the data collection element in SAP ERP
and sent the IDocs containing this data collection element information to SAP MII.
2. Assign these activities to buttons. Assign the buttons to the relevant dashboard.
For more information, see Configuring OEE Dashboard [page 83].
3. Operators can now report the configured custom data from the dashboard.
1.11 Audit Log
Use
OEE provides an option to view logs where you can see the history of changes made to different OEE objects.
You can view logs based on:
● The object, for example, orders

● Description type of the object
● Change made to the object – creation, update or deletion
● Changes made to object in a particular date range
Prerequisites
● The audit log can be viewed by users who have the role OEE_ADMIN and OEE_SUPERVISOR.
● You have configured the customization Display Audit Log with value Order (ORD). This customization is
configured at the client and plant level.
Activities
1. You can see the log from SAP MII main menu Worker UI Management Audit Log
System displays the audit logs for the selected client and plant.
2. To change the client and plant, select Change Client and Plant from the dropdown with the user name on the
right top corner and choose the relevant client and plant.

1.12 Plant-level Reporting and Analytics in OEE
Use
Plant-level reporting and analytics can be done with SAP OEE using the SAP Lumira tool. Lumira consumes local
OEE MII data to generate the analytical reports. SAP OEE delivers an out-of-the-box plug-in for Lumira to enable
local MII-based reporting. It also delivers out-of-the-box data extraction from MII that can be consumed directly in
Lumira. This functionality reduces the dependency on HANA-based reporting which provides a consolidated and
central reporting for all plants.
The configurations required to generate the reports are made by the SAP OEE Integration CTC (see SAP OEE
Integration Configuration CTC) [page 64].
Additionally, there are configurations that you make to enable OEE data analysis in Lumira. For more information,
see Configurations for OEE Lumira Reports [page 122].
The SAP OEE Integration CTC configures:
1. OEEAutoCsvDownloadForReports scheduler. This scheduler runs the services that fetch data for the
reports and creates three CSV files.
CSV files contain the following data:
1. DataReport.CSV
Contains quality loss and speed loss data.
2. KPIAnalysisReport.CSV
Contains KPI and OEE losses data.
3. ProductionRunEventReport.CSV
Contains unscheduled and scheduled downtime data.
2. Frequency of the scheduler. By default, the frequency is 1 day, you can change it to meet your requirements.
The data displayed in the reports refreshes at the same frequency as of this scheduler.
3. Location where the CSV files containing the relevant data are created. You give this location when you run this
CTC.
1.12.1 Configurations for OEE Lumira Reports
Use
OEE data reported from the shopfloor is stored in OEE tables in SAP MII. The data relevant for plant performance
analysis are stored in CSV files. The metadata required for visualization in Lumira is available as an OEE Lumira
plug-in which you can export and install.

Prerequisites
Lumira desktop version 1.25 is installed in your system landscape.
For more information, see the Installation and Upgrade guide for Lumira on the SAP help portal at http://
help.sap.com Analytics SAP Lumira
Process
To enable OEE data analysis in Lumira, do the following:
1. Export the OEE Lumira extension from SAP MII

The extension sap.oee.lumira.dae.extension is required to generate analytical reports on OEE data in
Lumira. The extension is available in SAP MII. Choose Content Development Workbench Web tab
SAP MPM WEB Lumira Plugin .
The extension contains metadata information required to consume the CSV files containing OEE data in SAP
Lumira.
2. Install the OEE Lumira extension on Lumira desktop.
Choose File Extensions . In the Extension Manager choose Manual Installation. Download the extension.
You may have to restart the Lumira desktop to enable the extension.
3. Add the datasets you want to analyze. You have to do this once for every dataset:
1. Choose File Create . Choose OEE Data Acquisition Extension.
2. Enter the name for the dataset.
3. Enter the path to the CSV file.
This is the path to the FTP location where CSV files are downloaded. You enter the FTP location when
running the SAP OEE Integration Configuration CTC.
If the FTP location is not maintained, the files are located at C:\<usr>\sap\<serverInstance>
\J00\j2ee\cluster\server0\LumiraReports.
4. Enter the path to the metadata file.
4. You prepare the report to visualize the data.
After adding the dataset:
○ Choose Prepare Languages Options Filter to choose the language in which you want to see the
reports in. By default, the reports are displayed in English and the plants language, if the plant’s language
is supported by OEE.
○ Choose Visualize. Add the dimensions and measures for the report.
1.13 Apps on Application Launchpad
OEE provides Application Launchpad from where production workers can launch applications (apps) relevant to
their work. The apps are available to the assigned users from the SAP MII main menu Worker UI Management
Application Launchpad . The apps are available after you have made the configurations required to enable the
apps.

For information on the configurations, see Configurations for Good Issue and Goods Receipt Apps [page 125].
With SAP MII 15.1, OEE delivers the following apps in the Application Launchpad:
● Goods Issue
● Goods Receipt
Production workers can use the apps to:
● Post goods issue for recording consumption and reversal of raw materials used in the production process,
against a production or process order available in MII OEE.
● Post goods receipt for recording production declaration or reversal, against a production or process order
available in MII OEE.
1.13.1 Configuration of GI-GR apps with EWM
Use
From 15.1 SP01 release, the Goods Issue (GI) and Goods Receipt (GR) apps can perform goods issue and goods
receipt with the SAP Extended Warehouse Management (EWM) system. For more information regarding the
configurations required, see 2225320 .
Procedure
You configure the apps as follows:
1. From SAP NetWeaver Administrator (NWA) run the SAP OEE Configuration CTC.
The CTC configures:
1. Customization SAP OEE Application Transaction Mode.
You add the customization at plant level. The customization value determines whether the apps run in
online or offline mode. By default, the value is online. The mode helps to pick up the relevant transactions
from the activities. This customization also provides the option to configure the transaction when the
mode is changed.
2. Customizations Offline-Online Mode Change Transaction and Online-Offline Mode Change Transaction.
These customizations provide the option to configure the transaction when the mode is changed.
3. Default dashboard SAP_APP_LP_POD of type Application Launchpad.
The default dashboard contains the default group and default activities required to configure the
Application Launchpad and the GI and GR apps.
The two default activities are ACT_STD_COMP_GI and ACT_STD_COMP_GR.
2. Configure the Application Launchpad.
1. From the General Configuration screen, assign the dashboard you created to the relevant users.
2. The launchpad containing the dashboard with the assigned apps is available to the users from SAP MII
main menu Worker UI Management Application Launchpad .
3. Enhance the IDoc LOIPRO01 to identify HU (handling unit) managed and bulk managed material.
For information on how to configure the IDoc, see 2441220 .

1.13.2 Configurations for Good Issue and Goods Receipt Apps
Use
To enable the Goods Issue (GI) and Goods Receipt (GR) apps you have to make some configurations in your
landscape.
Process
You configure the apps as follows:
1. From SAP NetWeaver Administrator (NWA) run the SAP OEE Configuration CTC.
The CTC configures:
1. The customization SAP OEE Application Transaction Mode. You add the customization at plant level. The
customization value determines whether the apps run in online or offline mode. By default, the value is
online.
The mode helps to pick up the relevant transactions from the activities. This customization also provides
the option to configure the transaction when the mode is changed.
2. The default dashboard SAP_APP_LP_POD of type Application Launchpad. You copy and configure your
own dashboard using this dashboard from the OEE Dashboard Configuration screen. The default
dashboard contains the default group and default activities required to configure the Application
Launchpad and the Good Issue and Goods Receipt apps.
2. Configure the apps
1. Configure the activities relevant for the apps (see the activities specific to the apps below). From the SAP
MII main menu, choose Worker UI Management Activity Configuration . On the Activity
Configuration screen:
1. ChooseCreate Activity
2. Enter the relevant Activity ID
3. Select Activity Type as UI Component
4. Enter the URL. For GI, use sap.oee.m.goodsissue. For GR, use sap.oee.m.goodsreceipt.
2. Configure the Goods Issue app by configuring the following activities and options. The input and output
parameters of these activities are available in SAP Note 2225320 .
Table 35:
Activity Options Description
ACT_STD_COMP_GI TRX_ACT_ORD_ONL Transaction for active order details

when in online mode (Optional)
TRX_SSCC_SCN_ONL Transaction to retrieve details on

SSCC or barcode scan when in online
mode

TRX_GET_BAT_ONL Transaction to retrieve batch details

when in online mode
TRX_GDS_MVT_ONL Transaction to post goods movement

when in online mode
TRX_GDS_MVT_RPT_ONL Transaction to view goods movement

report in online mode
TRX_ACT_ORD_OFFL Transaction for active order details

when in offline mode (Optional)
TRX_SSCC_SCN_OFFL Transaction to retrieve details on

SSCC or barcode scan when in offline
mode
TRX_GET_BAT_OFFL Transaction to retrieve batch details

when in offline mode
TRX_GDS_MVT_OFFL Transaction to post goods movement

TRX_GDS_MVT_RPT_OFFL Transaction to view goods movement

report in offline mode
ACT_W_D_BULK Activity to plug-in user defined weigh

and dispense screen for bulk material
ACT_W_D_HU Activity to plug-in user defined weigh

and dispense screen for HU managed
material
3. Configure the Goods Receipt app by configuring the following activities and options. The input and output
parameters of these activities are available in SAP Note 2225320 .
Table 36:
ACT_STD_COMP_GR TRX_ACT_ORD_ONL Transaction for active order details

when in online mode (Optional)
TRX_GEN_BAT_ONL Transaction to generate batch details

when in online mode
TRX_GDS_MVT_ONL Transaction to post goods movement

when in online mode

TRX_ACT_ORD_OFFL Transaction for active order details

when in offline mode (Optional)
TRX_GEN_BAT_OFFL Transaction to generate batch details

TRX_GDS_MVT_OFFL Transaction to post goods movement

You can see all the components of an order-operation independent of the workcenter. To do this, add the
option WORKUNIT_FILTER for the activity ACT_STD_COMP_GI and ACT_STD_COMP_GR and set the
value as False.
3. Configure the Application Launchpad

1. From the SAP MII main menu, choose Worker UI Management Dashboard Configuration .
On the OEE Dashboard Configuration screen:
1. Copy the default dashboard SAP_APP_LP_POD. Maintain the type as Application Launchpad.
Only dashboards of this type are displayed on Application Launchpad.
2. Assign the activities you created for the apps as Dashboard Buttons.
1. Select the Dashboard tab and choose Add Entry.
2. Enter the relevant activity in the Button ID field.
3. Add the activities created for the apps.
You can add activities of type UI Component or External App.
2. From the General Configuration screen:
1. Assign the dashboard you created to the relevant users.
2. The launchpad containing the dashboard with the assigned apps is available to the users from SAP
MII main menu Worker UI Management Application Launchpad .
More Information
Applications in OEE [page 123]
1.14 Automatic Data Collection
Use
SAP OEE provides the option to collect data automatically. For this, OEE provides a set of services and custom
action SAP OEE Service Interface in SAP MII that can be used to create SAP MII transactions. These transactions
can then be triggered from the plant connectivity (PCo) system when the relevant event occurs.

This custom action allows you to upload, expand and customize functions of the SAP OEE application. You can
build transactions using this action.
You configure the data collected by the PCo tags such that it provides the required input parameters to the
transaction you created. SAP OEE provides the service ShopFloorDataCollectionsService to create custom
actions.
Procedure
You can access the OEE custom action as follows:
1. From the SAP MII main menu screen choose Content Development Workbench .
2. On the Catalog tab choose SAPMPM.
Choose File New Transaction .
3. On the Actions tab, choose SAP_OEE_Integration. Choose the custom action SAP OEE Service Interface
available under this action.
You can build transactions using the service that is available for this custom action. For more information, see
Back-End Services [page 129].
Example
You can create a transaction to automatically report downtime event from the shop floor
More Information
1.14.1 Custom Actions
Use
SAP OEE-relevant custom action SAP OEE Service Interface allows you to upload, expand and customize
functions of the SAP OEE Management application.
For information on how to work with custom actions, see .

Features
The following custom actions are available:
● SAP OEE Service Interface: This custom action receives automatic data from the shop floor. Here, instead of
receiving data from the user interface, the machine itself reports data. This custom action encapsulates all
the OEE back-end services into a custom action. You create a transaction using this custom action.
● Convert Material UoM: This custom action does material specific UoM conversion. It uses the conversion
factors of UoMs mentioned in the material header, material alternate UoM, or UoM and dimension tables to
perform conversion from source UoM to target UoM. This custom action is used by the OEE back-end
services to perform UoM conversion.
● Archive Non HANA Replicated Tables: This custom action deletes all the transaction data that was not
replicated to SAP HANA. System deletes the data after the retention time that you have maintained in the
Retention Time for Non HANA Replicated Tables field.
Enter the retention time from the SAP MII main menu screen Worker UI Management General
Configuration Customization Configuration . Choose Add and select Retention Time for Non HANA
Replicated Tables in the Customization Name field.
● Archive HANA Replicated Tables: This custom action deletes all the transaction data that was replicated to
SAP HANA. System deletes the data after the retention time that you have maintained in the Retention Time
for HANA Replicated Tables field.
Enter the retention time from the SAP MII main menu screen Worker UI Management General
Configuration Customization Configuration . Choose Add and select Retention Time for HANA Replicated
Tables in the Customization Name field.
1.14.2 Back-End Services
You can use the service ShopFloorDataCollectionsService to create custom actions.
For information on the request and response XML for the service methods, see 2457333 .
This service has the following methods:
Table 37:
Method Description
startProductionRun Starts a production order
completeProductionOrder Completes a production order
pauseProductionRun Pauses a production run
resumeProductionRun Resumes a production run
reportProduction Reports production data
reportRejection Reports rejected quantity

Method Description
reportUnscheduledDowntime Reports downtime
reportUnscheduledUptime Reports uptime
reportSpeedLoss Reports a loss in speed
changeProductionActivity Reports a change in production activity
reportRawMaterialConsumption
Note
This method is deprecated as of SAP MII 15.1 SP02.
To report the raw materials consumed during the order-

operation run, you can use the Goods Issue and Goods Re
ceipt apps instead.
For more information, see Apps on Application Launchpad

[page 123]
reportRawMaterialScrap Reports the raw material quantity that was scraped during an
order-operation
reportScheduledDowntime Reports start of planned downtime
reportScheduledUptime Reports end of planned downtime
reportOtherDataCollection Reports data collected for an order-operation, for example

utilities like electricity consumption
reportStandardValueParameter Reports standard value data collection for all the parameters
getActiveRunsforNodeID Retrieves all the active runs for the node ID
reportFlowtimeStart Reports start of flow time
Flow time is the time taken, after production starts, for the
material to reach the entire line. It is a non productive time
and is subtracted from the Loading Time.
reportFlowtimeEnd Reports end of flow time
getOeeKPIs Gives the values of the relevant SAP OEE KPIs for the current
shift
abortProductionRun Sets the status of the production run to Aborted
reportEvent Can be used to report data collection against any duration

type DC Elements
restartActiveRunsInCurrentShift Moves runs active in older shifts to current shift

Method Description
releaseDemand Used to release quantity against an order for execution on the

Worker UI (relevant for manual release scenarios)
reportQuantity Can be used to report data collection against any quantity

type DC Elements
createPMNotification Used to create a PM Notification object and optionally trigger

the notification creation in SAP ERP
deleteEvent Can be used to delete an already reported downtime using

down-ID/event-ID.
deleteReportedQuantity Can be used to delete a reported data collection record. Takes

the entry-ID of the record to be deleted as input.
editEvent Can be used to update a downtime record, the values to be

updated should be sent as input along with a valid down-ID/
event-ID.
getOeeKpiDetails Can be used to query detailed downtime and data collection

information that impacts a work unit’s KPI.
getOEEKpisForRunsInShift Returns OEE standard KPIs for each run that was started in a
shift.
For methods that use a date, time or time stamp, use the format MM-dd-yyyy HH:mm:ss.

Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).

132 CUSTOMER Important Disclaimers and Legal Information
Important Disclaimers and Legal Information CUSTOMER 133
go.sap.com/registration/
contact.html
© 2017 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. The information contained herein may
be changed without prior notice.
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 are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP 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.
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. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

SAP OEE 15.1 Help

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP OEE 15.1 Help

Uploaded by

Copyright:

Available Formats

CUSTOMER

Document Version: 15.1.5 – 2017-07-10

SAP Overall Equipment Effectiveness Management

1 SAP Overall Equipment Effectiveness Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

SAP Overall Equipment Effectiveness Management

SAP Overall Equipment Effectiveness Management

The OEE solution utilizes the following software components:

Software Component Dependent Software Component

OEE_ERP 15.0 SP03 SAP ERP 6.0/6.0X

For more information, see 1804140

http://help.sap.com SAP Manufacturing Integration and

Intelligence 15.1 Installation and Upgrade Information .

HCO_HBA_OEE 1.0 SP06 SAP HANA Analytics Foundation 1.0 SP02

SAP HANA 1.0 SP05 revision 51 or higher

HCO_HBA_APPS_OEE 1.0 SP06 SAP HANA 1.0 SP05 revision 51 or higher

SAP HANA Analytics Foundation 1.0 SP02

HCO_HBA_OEE 1.0 SP06

SAP OEE application consists of the following functional building blocks:

● Customizing settings and master data in SAP ERP

SAP Overall Equipment Effectiveness Management

The SAP OEE application has the following features:

1.1 System Landscape

SAP Overall Equipment Effectiveness Management

Typical OEE system landscape is depicted as follows:

Figure 1: SAP OEE System Landscape

SAP Overall Equipment Effectiveness Management

1.2 OEE Calculations

OEE = Availability X Performance X Quality

SAP Overall Equipment Effectiveness Management

Figure 2: OEE Data Elements

SAP Overall Equipment Effectiveness Management

● Define Data Element Types

OEE Customizing Settings in SAP ERP [page 25]

Configuring Activities [page 74]

1.3 User Roles and Authorizations

SAP Overall Equipment Effectiveness Management

You can find authorization related information in the following:

● SAP ERP Layer [page 10]

1.3.1 SAP ERP Layer

1. Cross application authorization object

SAP Overall Equipment Effectiveness Management

1.3.2 OEE Integration and Services (JAVA Layer)

SAP Overall Equipment Effectiveness Management

1. In Identity Management, choose Configuration.

1. Log on to SAP NetWeaver as administrator user.

SAP Overall Equipment Effectiveness Management

Action Type Description

OEEProductionRun_Read Transaction Action to enable read of shift related

OEEReleaseDemand_Read Transaction Action to enable read of operation level

OEEReportDowntime_Read Transaction Action to enable read of reported down

OEEDataCollection_Read Transaction Action to enable read of reported data

OEEProductionOrder_Read Transaction Action to enable read of production or­

OEEProductionRun_Operator Transaction Action to enable read and change pro­

OEEProductionRun_Create_Update Transaction Actions to enable create and update of

OEEReleaseDemand_Create_Update Transaction Actions to enable create and update of

OEEProductionRun_All Transaction Action to enable all operation on shift re­

OEEReleaseDemand_All Transaction Action to enable all operation on opera­

OEEReportDowntime_All Transaction Action to enable all operation for report

OEEDataCollection_All Transaction Action to enable all operation for data

OEEProductionOrder_All Transaction Action to enable all operation for pro­

OEEQueueMonitor_All Transaction Action to enable create, read, update,

OEEQueueMonitor_Read Transaction Action to enable read of OEE integration

SAP Overall Equipment Effectiveness Management

OEEScheduledDown_Create Transaction Action to enable create of scheduled

OEEProductionOrder_Read Transaction Action to enable read of production or

OEEProductionRun_Operator Transaction Action to enable read and change pro

OEEProductionRun_All Transaction Action to enable all operation on shift re

OEEReleaseDemand_All Transaction Action to enable all operation on opera

OEEProductionOrder_All Transaction Action to enable all operation for pro

OEEWorkflowConfig_Read Configuration Action to enable read of workflow config

OEEGlobalConfig_Read Configuration Action to enable read of global configu

OEEActivity_Read Configuration Action to enable read of activity configu

OEEPod_Read Configuration Action to enable read of dashboard con

OEEUserGroupAssignment_Read Configuration Action to enable read of user group as

OEEStatus_Read Configuration Action to enable read of status configu

OEEPod_All Configuration Action to enable all operation on dash

OEECustomizationName_All Configuration Action to enable all operation on cus

OEECustomizationValue_All Configuration Action to enable all operation on cus

OEEConfigUserGroupAssignment_Al Configuration Action to enable assignment of authori

OEEScheduledDown_All Configuration Action to enable all operation on sched

OEEExtension_All Configuration Action to enable all operation on exten

OEEMasterConfiguration_Read Configuration Action to enable read of SAP ERP mas

OEEErpConfirmations_Read Configuration Action to enable read of confirmation re

OEEErpConfirmations_All Configuration Action to enable permission to send con

The role, however, has only read authori OEEReasonCodeMapping_Read

The role also has the required authoriza OEEReportDowntime_All