Administrator's Guide

SAP Overall Equipment Effectiveness Management 1.0

OEE_MII Component

Target Audience
Çz¦Oõó Technical Consultants
Çz¦Oõó System Administrators
Çz¦Oõó Solution Consultants
Çz¦Oõó Business Process Owners
Çz¦Oõó Support Specialists

PUBLIC
Çz¦«Ð<²Dƒg¦ŽZ›#Éèþøfl!¯E˘È|˝IN±˚³¢Vá–ÃÖ½—Æ!¬bzðmÔ‹−⁄Q]PSU5%Ÿ⁄–Òd
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location:http://service.sap.com/instguides.

The following table provides an overview of the most important document changes.
Version Date Description
1.0 2013-06-17 Initial Version
1.1 2014-01-10 CTC details updated

2/42 PUBLIC 2014-01-10

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 SAP OEE Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Software Units of SAP OEE Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 SAP OEE System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Overall Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Audit License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.1 Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4.1 SAP NetWeaver 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4.2 Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 12
3.4.3 SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4.4 Plant Connectivity (PCo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5.1 Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5.2 Installing SAP OEE Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.3 CTC Templates for SAP OEE Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.3.1 Configuring SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.3.2 Configuring SAP OEE Integration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.3.3 SAP OEE Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5.3.4 Re-Executing CTC templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4 Operations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2 Monitoring SAP OEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2.2 GRMG Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2014-01-10 PUBLIC 3/42

4.3 Detail Monitoring and Tools for Problem and Performance
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4 Data Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.5 Managing SAP OEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5.2 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5.3 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.7 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.7.1 Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.7.2 Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.8 TroubleShooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.9 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.9.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.9.2 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5 Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.1 User Administration and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.1 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.2 User Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.3 Standard Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.4 Integration Into Single Sign-On Environments . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2 Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.3 Session Security Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4 Network and Communication Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4.1 Communication Channel Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.5 Data Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.6 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.7 Enterprise Services Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.8 Security Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4/42 PUBLIC 2014-01-10

1 Getting Started
1.1 About This Document

1 Getting Started

1.1 About This Document

This Administrator’s Guide is the central starting point for the technical implementation of OEE_MII
software component of SAP Overall Equipment Effectiveness Management (SAP OEE Management).
You can find cross-scenario implementation information as well as scenario-specific information in
this guide.
Use the Administrator’s Guide to get an overview of SAP OEE Management, its software units, and its
scenarios from a technical perspective. The Administrator's Guide is a planning tool that helps you to
design your system landscape. It refers you to the required detailed documentation. The
Administrator’s Guide is a single source of information to support the implementation and operation
of SAP OEE Management.

NOTE

You can find the most current version of this document on SAP Service Marketplace at http://
service.sap.com/instguides.
We strongly recommend that you use the document available there. The guide will be updated
according to updates of the software.

The Administrator's guide consists of the following main sections:

YÙı4E@ Planning Information
The first two chapters of the Administrator’s Guide provide you with the most important
information regarding the implementation of SAP OEE Management, including an overview of
the related planning information, its software units, the system landscape, and the overall
implementation sequence.
YÙı4E@ Installation Overview
This chapter gives you an overview of the installation components and the sequence in which they
are installed.
YÙı4E@ Operation Information
This chapter provides you with the information that you require to operate SAP OEE Management.
YÙı4E@ Security Information
This chapter provides you with the information that you require to operate SAP OEE Management
securely.

2014-01-10 PUBLIC 5/42

1 Getting Started
1.1 About This Document

Constraints

#‡¥:‰c The business scenarios that are presented here serve as examples of how you can use SAP software
in your company. The business scenarios are only intended as models and do not necessarily run
the way they are described here in your customer-specific system landscape. Ensure to check your
requirements and systems to determine whether these scenarios can be used productively at your
site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems
to ensure they are complete and free of errors before going live.
#‡¥:‰c This guide primarily discusses the overall technical implementation of SAP OEE Management,
rather than its subordinate components. This means that additional software dependencies might
exist without being mentioned explicitly in this document. You can find more information on
component-specific software dependencies in the corresponding installation guides.

NOTE

You can find the most current information about the technical implementation of SAP OEE
Management and the latest installation and configuration guides on SAP Service Marketplace at
http://service.sap.com/instguides.
We strongly recommend that you use the document available there. The guides are regularly
updated.

Related Information

For more information about implementation topics not covered in this guide, see the following content
on SAP Service Marketplace:
Content Location on SAP Service Marketplace
Latest versions of installation and http://service.sap.com/instguides
upgrade guides
General information about <name of http://service.sap.com/<quick link>
your product>
Sizing, calculation of hardware http://service.sap.com/quicksizer
requirements — such as CPU, disk and
memory resource — with the Quick
Sizer tool
Released platforms and technology- http://service.sap.com/platforms
related topics such as maintenance To access the Platform Availability Matrix directly, enter http://
strategies and language support service.sap.com/pam

Network Security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about Support Package http://service.sap.com/sp-stacks

Stacks, latest software versions and
patch level requirements
Information about Unicode http://www.sdn.sap.com/irj/sdn/i18n
technology

6/42 PUBLIC 2014-01-10

1 Getting Started
1.1 About This Document

Further Useful Links

The following table lists further useful links on SAP Service Marketplace:
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/messages

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and ordering of http://service.sap.com/swdc

software)
SAP Online Knowledge Products (OKPs) — role-specific learning maps http://service.sap.com/rkt

Related Guides

You can find more information about the relevant applications in the following documents:
Title Location
SAP NetWeaver 7.3 http://service.sap.com/installNW73 Installation Planning Master Guide

2014-01-10 PUBLIC 7/42

This page is left blank for documents
that are printed on both sides.
2 SAP OEE Management Overview
2.1 Software Units of SAP OEE Management

2 SAP OEE Management Overview

2.1 Software Units of SAP OEE Management

The software units required for SAP OEE Management are as follows:
£¨ôÀgŒ SAP NetWeaver 7.3
£¨ôÀgŒ SAP MII 14.0
All components are mandatory.

2.2 SAP OEE System Landscape

The following section describes the various ways in which the system landscape for SAP OEE
Management can be set up.

2.2.1 System Landscape

£¨ô&B_-'Û„[¢¬ÈlŸê!îˇœeSystem Landscape

NOTE

For high availability, performance, and scalability, refer to SAP NetWeaver Installation Guides at
https://service.sap.com/instguidesnw73.

2014-01-10 PUBLIC 9/42

This page is left blank for documents
that are printed on both sides.
3 Installation Information
3.1 Overall Implementation Sequence

3 Installation Information

3.1 Overall Implementation Sequence

The following table describes the overall installation sequence for SAP OEE Management. This table
contains all available software units.
Implementation Sequence
Step Action (Required Documentation) Remarks/Subsequent steps
1 SAP NetWeaver (7.3) Server component
2 SAP MII 14.0 Server component
3 SAP Overall Equipment Server component
Effectiveness Management

NOTE

The SAP_XMII_Administrator role must be assigned to the administrative AS Java user to log on
to SUM and deploy SAPOEEMII<XX>.SCA

3.2 Audit License

For SAP ERP installations, where SAP HANA is a component of SAP OEE system landscape you must
make the following configurations:
1. Create a connection from the productive SAP ERP system to the productive SAP HANA system
with name HDB.
If HDB is already in use, give another name.
2. Implement implicit enhancement spot at the start of function module: /OEE/LICENSE_AUDIT
1. Select Enhancement Source Code.
2. Select Edit Enhancement Operation Show Implicit Enhancement Options
3. Select the option at the start of the function module, right click and select Enhancement
Implementation Create
4. Select Enhancement Type as Code.
5. Give a name and short text for the Enhancement Implementation.
3. Assign the name of the connection to variable C_CONNECTION_NAME.

2014-01-10 PUBLIC 11/42

3 Installation Information
3.3 Planning

3.3 Planning
3.3.1 Process Flow
To plan your SAP OEE Management installation, do the following:
1. Read all documentation related to SAP OEE Management.
See the SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite
Applications SAP Manufacturing SAP Overall Equipment Effectiveness Management 1.0 .
2. Verify your system landscape.
For information on the minimal system landscape required for SAP OEE Management, see the SAP
OEE Management Master Guide on the SAP Service Marketplace at http://service.sap.com/
instguides SAP Business Suite Applications SAP Manufacturing SAP Overall Equipment Effectiveness
Management 1.0 .

3.4 Preparation
3.4.1 SAP NetWeaver 7.3
Install and configure SAP NetWeaver Java Application Server SP09 or higher with a Usage Selection of
Application Server Java.
For more information:
æ˸Þr NW 730: See the SAP Service Marketplace at http://service.sap.com/instguidesnw SAP
NetWeaver 7.3 Installation .
æ˸Þr NW 730 Enhancement Package 1 SP07: See SAP Help Portal at http://help.sap.com/nw73 SAP
NetWeaver 7.3 Including Enhancement Package 1 .

NOTE

If you plan to use the OEE_HANA component then:

æ˸Þr Install SAP NetWeaver on IBM DB2 LUW/ UDB (DB6) or Sybase ASE only if ERP is also using
the same DB
æ˸Þr Do not install SAP NetWeaver on IBM Informix as it is not yet supported by SLT

3.4.2 Checking Hardware and Software Requirements

The SAP OEE 1.0 host machine must meet the following requirements for SAP NetWeaver Java
Application Server.
For more information, see:
æ˸Þr NW 730: See the SAP Service Marketplace at http://service.sap.com/instguidesnw SAP
NetWeaver 7.3 Installation .

12/42 PUBLIC 2014-01-10

3 Installation Information
3.4 Preparation

2Ïx÷xfl NW 731: SAP Help Portal at http://service.sap.com/nw SAP NetWeaver 7.3 Including Enhancement
Package 1 .
2Ïx÷xfl Quick Sizer: See http://service.sap.com/sizing.

3.4.3 SAP MII

Install and configure SAP MII.
For more information see the SAP Service Marketplace at http://service.sap.com/instguides
SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Integration and Intelligence .

3.4.4 Plant Connectivity (PCo)

PCo connects the shop floor to SAP MII. It enables automatic data collection.
The following set up is required for data collection using PCo:
1. Create a transaction for reporting events in SAP MII as follows:
1. On the SAP MII main menu screen, choose Content Development Workbench . Create a new
project File New Project .
2. Create a new transaction in the project you created. To do this, choose File New
Transaction .
3. Create a transaction property of type xml. To do this, choose Transaction Properties .
This is the xml that will be used from PCo.
4. Select the Actions tab and choose SAP_OEE_Integration.
5. Select the SAPOEE Service Interface action from the list. Drag and drop the action into the
empty sequence of the newly created transaction.
6. Right click on the added action and select Configure.
7. Enter the following in the configuration dialog box:
1. Select a Credential Alias. This alias should have required roles to perform reporting.
2. Choose Search
3. Select the Service and Method name based on the type of reporting to be done. For example,
select ShopFloorDataCollectionService - reportProduction for reporting good quantity.
4. Choose OK. In the dialog box that appears asking if you want to generate request/response
xml, choose Yes.
8. Right click on the added action and select Links.
9. Expand the SAPOEE_Service_Interface_0 and the Request object. For example, expand the
ReportProduction object.
10. For example, the following input values will be filled from the PCo xml for ReportProduction:
2Ïx÷xfl nodeID
2Ïx÷xfl orderNumber

2014-01-10 PUBLIC 13/42

3 Installation Information
3.5 Installation

±+´ÍòŽ operationNumber
±+´ÍòŽ dataCollectionElement
±+´ÍòŽ material
±+´ÍòŽ reportingQuantity
±+´ÍòŽ reportingUOM
±+´ÍòŽ rc1 to rc8
±+´ÍòŽ comments
±+´ÍòŽ eventTime
You link the xml input values to the ReportProduction object values.
Save the transaction
2. In the PCo server, configure the following:
1. Configure the source server.
For more information, see the topics in the Source System section of the application help for PCo
at http://help.sap.com SAP Business Suite SAP Manufacturing SAP Plant Connectivity .
2. Configure the destination server.
For more information, see the topics in the Destination System section of the application help for
PCo.
3. Configure the agent instance.
For more information, see the topics in the Agent Instance section of the application help for
PCo.
4. Configure notification. When creating notification, ensure that you select the SAP MII
transaction that corresponds to the event you are notifying.
For more information, see the topics in the Notification section of the application help for PCo.

3.5 Installation
3.5.1 Prerequisite
±+´ÍòŽ You have installed SAP NetWeaver Java Application Server with a Usage Selection of Application Server
Java.
±+´ÍòŽ You have installed SAP MII 14.0.
±+´ÍòŽ You have downloaded the SAP OEE components as follows:
1. Logon to SAP Service Marketplace at http://service.sap.com.
2. Choose Software Download Support Packages and Patches A-Z Index O SAP OEEMII
3. Select the option SAP OEEMII.
4. Choose SAP OEEMII 1.0 Entry by Component .
5. Select Server on SAP NetWeaver.
OEEMII 1.0 component is available.

14/42 PUBLIC 2014-01-10

3 Installation Information
3.5 Installation

6. Download the latest SP and patch for both these components.

7. Follow the steps as mentioned in the topic Installing SAP OEE Using Software Update Manager.

3.5.2 Installing SAP OEE Management

1. Logon to the SAP Service Marketplace at http://service.sap.com/sltoolset.
2. Choose Software Logistics Toolset 1.0.
3. Navigate to SUM under documentation tools and choose Updating SAP Systems Using Software Update
Manager 1.0 (SP04 or higher).
4. Choose Update of SAP Systems Using Software Update Manager (Java Systems).
5. Follow the instructions as in section Applying Single Component Updates and Patches Using a Manually Prepared
Directory.

3.5.3 CTC Templates for SAP OEE Management

SAP OEE Management application runs only after the default configuration settings are done.
After the .sca file is deployed, user has to run the CTC Templates for SAP OEE Management to perform
necessary configurations.

Prerequisites

ØÉ›««¶ You have configured SAP ERP to communicate with SAP MII. This involves the following:
ØÉ›««Ù Setting up ALE user
ØÉ›««Ù ALE configuration
ØÉ›««Ù Other customizing activities
For more information, see ERP-Shop Floor Configuration topic at http://help.sap.com SAP Business
Suite SAP Manufacturing SAP Overall Equipment Effectiveness Management .
The three CTC templates that you must run to setup the system are as follows:

3.5.3.1 Configuring SAP NetWeaver

This CTC configures SAP NetWeaver with an OEE user who has the required roles to perform all OEE
related actions.
You can access this CTC through NetWeaver Administrator Configuration Scenarios Configuration Wizard:
SAP OEE NetWeaver Configurations
This CTC performs the following actions:
1. Creates or updates OEE_ADMIN user.
2. Assigns the following roles to the OEE_ADMIN user:
ØÉ›««¶ OEE_SUPERADMIN

2014-01-10 PUBLIC 15/42

3 Installation Information
3.5 Installation

ë™[~¢]
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
ë™[~¢]
NWA_SUPERADMIN
The OEE_ADMIN user has the superset of all possible roles to perform all the actions in SAP
OEE Management.
3. Collects the following information required to configure the integration between SAP OEE and
SAP ERP:
Page / Field Example Value / Comment
Page 1 of 3: Password for OEE_ADMIN user
Page 2 of 3: SAP NetWeaver Instance for SAP MII
SAP NetWeaver
Information
Protocol: http
ë™[~¢] http CAUTION
ë™[~¢] https 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.
Host miiserver
Port 50000
SSL Port 50001
Page 3 of 3:
Confirmation Page
The Last
Configuration Step

3.5.3.2 Configuring SAP OEE Integration Interfaces

The SAP OEE Integration CTC wizard configures SAP MII, and integration-related SAP OEE elements
for SAP OEE and ERP integration.
This CTC configures the ERP-Shop floor integration with the following:

16/42 PUBLIC 2014-01-10

3 Installation Information
3.5 Installation

A§ø¦ SAP MII schedulers

A§ø¦ Workflow configuration
A§ø¦ Global configuration
A§ø¦ Supported plants
You can access this CTC through NetWeaver Administrator Configuration Scenarios Configuration Wizard:
SAP OEE Integration
SAP ERP must be configured manually according to the SAP OEE documentation. For more
information, see ERP-Shop Floor Integration Configuration at http://help.sap.com SAP Business Suite
SAP Manufacturing SAP Overall Equipment Effectiveness Management .
This CTC collects the following information required to configure the ERP-Shop Floor integration:
Page / Field Example Value / Comment
Page 1 of 6: JRA Adapter Information
Connection Factory name Enter the connection factory name
Server Enter the ERP server name associated with your OEE plant(s)
Page 2 of 6: Supported SAP OEE Plant
ERP Plant 2010 – the name of an existing SAP ERP plant to be integrated with SAP OEE
Management
SAP OEE_ADMIN Password <SITE_ADMIN's password>
SAP ERP JRA Connector Name JRA Connector Name
SAP ERP Time Zone America/Los_Angeles
SAP OEE Time Zone America/New_York
Page 3 of 6: SAP NetWeaver Instance for SAP MII
SAP NetWeaver Information
Protocol: http
A§ø¦ http
A§ø¦ 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 the SAP_XMII_Developer role.
3. Move Destination_Service_Write_Permission to Assigned Actions.
Host miiserver
Port 50000
SSL Port 50001
XMIIIDOC Listener: XMIIIDOC01
A§ø¦ XMIIIDOC01
A§ø¦ XMIIIDOC02
A§ø¦ ......
A§ø¦ XMIIIDOC10
SAP ERP Connection Information

2014-01-10 PUBLIC 17/42

3 Installation Information
3.5 Installation

Page / Field Example Value / Comment

XMIIIDOC01 Listener
Program ID XMII_ERP3
Server erp3.sap.corp
User VERPSFI_ALE
Password <The user's password>
Client 200
System Number 62
Language EN
Page 4 of 6: SAP MII Schedulers
Message Dispatcher
Number of Messages (qty) 50
Pattern 0 * * * * * (every minute)
Message Enquequer
Number of Messages (qty) 200
Pattern 0 * * * * * (every minute)
Queue Message Cleaner
Message Retention Period 24
(hours)
Pattern 0 * * * * * (every minute)
IDOC Inbound Enqueuer
Number of Messages (qty) 200
Pattern 0 * * * * * (every minute)
Page 5 of 6: Update
Configuration
SAP OEE Integration
Workflow Configuration
Pre XSLT Transaction Specify the SAP OEE relevant operations within a production or process order.
Parameter You can do this by entering the control key of the operations that are OEE
relevant.
An example string is defaulted. You can refer to it to write your own string
containing the control keys for the OEE relevant operations.
Page 8 of 8: Confirmation Page
The Last Configuration Step

Post CTC Execution Procedures

Updating the SAP MII Message Listener

1. Log on to SAP MII with the OEESYS user using the following URL:http://
<SAP_MII_host>:<SAP_MII_port>/XMII.
2. In the SAP ERP OEE Integrationmenu, choose SAP MII Configuration Message Listeners .
3. Select the XMIIIDOCnn that has been recently configured with the CTC wizard.

18/42 PUBLIC 2014-01-10

3 Installation Information
3.5 Installation

4. On the Details Configuration tab page, if the SAP Server name and SAP Client numberare 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 SAPOEE INTCTC wizard with correct
values.

3.5.3.3 SAP OEE Configurations

This CTC can be run with the user OEE_ADMIN that was created when you run SAP OEE NetWeaver
Configuration CTC or a user who has the role OEE_SUPERADMIN assigned.
This CTC configures the system defaults for OEE such as activities, production operator dashboard
(POD) and so on.
You can access this CTC through NetWeaver Administrator Configuration Scenarios Configuration Wizard:
SAP OEE Configurations .
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.
5. Collects the following information required to configure the system defaults for OEE:
Page / Field Example Value / Comment
Page 1 of 2: ERP Client and Plant Information
ERP Plant 2010 – the name of an existing SAP ERP plant to be integrated with SAP OEE
Management
ERP Client The ERP Client where the above Plant is configured
Page 2 of 2: Confirmation Page
The Last Configuration Step

NOTE

In a clustered environment, access SAP OEE CTC via the Webdispatcher URL for this SAP
NetWeaver system.

2014-01-10 PUBLIC 19/42

3 Installation Information
3.5 Installation

3.5.3.4 Re-Executing CTC templates

If any of the SAP OEE CTC wizard 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 SAPOEE
Integration task, and choose Re-execute.
Do not use the Resume or Takeover Session buttons to continue with any of the SAP OEE CTC templates.
If any template 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 Configurations for each
plant.
To make minor corrections or modifications in the current configurations manually, see Configuration
of SAP OEE Integration Interfaces at http://help.sap.com SAP Business Suite SAP Manufacturing
SAP OEE Management ERP-Shop Floor Integration .

20/42 PUBLIC 2014-01-10

4 Operations Information
4.1 Important Notes

4 Operations Information

Designing, implementing, and running your SAP applications at peak performance, 24 hours a day,
has never been more vital for your business success than now.
This guide provides a starting point for managing, maintaining, and running your SAP applications
optimally. It contains specific information for various tasks and lists the tools to implement them.
This guide provides references to the documentation required for these tasks, such as Master Guide
and SAP Library.

4.1 Important Notes

SAP Note Number Title
1107033 How to display Java monitoring data of NW7.1 in CCMS
617547 Sending alerts as mail and SMS
508140 Customer messages–Customer logon data

4.2 Monitoring SAP OEE

Within the management of SAP Technology, monitoring is an essential task. You can find more
information about the underlying technology in the SAP Netweaver Administrator’s Guide - Technical
Operations Manual in the SAP Library under SAP Netweaver Library.
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 Including
Enhancement Package 1 System Administration and Maintenance Information Technical Operations for SAP NetWeaver
Administration of Application Server JAVA (AS JAVA) Monitoring .
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 System
Administration and Maintenance Information Technical Operations for SAP NetWeaver Administration of SAP
NetWeaver Systems and Components Administration of Application Server JAVA (AS JAVA) Monitoring .
OEE depends on SAP MII for monitoring in CCMS. For more information on CCMS and MTEs refer
to the Monitoring in SAP MII section at http://help.sap.com SAP Business Suite SAP Manufacturing
SAP Manufacturing Integration and Intelligence System Administration and Maintenance Information Application
Operations Guide .

4.2.1 Prerequisites
Refer to the SAP MII Operations guide for setting up the SAP MII monitoring.

2014-01-10 PUBLIC 21/42

4 Operations Information
4.3 Detail Monitoring and Tools for Problem and Performance Analysis

4.2.2 GRMG Monitoring

You use the Generic Request and Message Generator (GRMG) to monitor the availability of SAP OEE
Management. You need to specify the required configuration settings in a GRMG customizing file,
which is transferred to CEN by a CCMS agent. For more information about the GRMG, see SAP Note
1826307.

4.3 Detail Monitoring and Tools for Problem and Performance

Analysis
4.3.1 Trace and Log Files
Trace files and log files are essential for analyzing problems.
The technology of SAP OEE is based on SAP NetWeaver Java Application Server. This guide covers only
the differences and additional information specific to this solution.
SAP OEE uses the standard SAP NetWeaver 7.30 logging infrastructure.
SAP OEE log and trace information is written to the following files:
ÑíW]˛ë Application
ÑíW]˛ë DefaultTrace
Logging locations in SAP NetWeaver:
ÑíW]˛ë General logging category: /Applications/OEE/Common
ÑíW]˛ë Log security related category: /System/Security/Audit/OEE/SecurityLog
ÑíW]˛ë Tracing location: com.sap.xapps.mpm
The logging level is controlled by SAP NetWeaver 7.30. To view these files, use the standard SAP
NetWeaver logging utilities.
If you show logging categories, the SAP OEE files are written to the base category /Applications/OEE
and include subcategories.
If you show tracing locations, the SAP OEE files are written to com.sap.xapps.mpm.*.

4.4 Data Retention

SAP OEE retains data for the duration you specify. You can specify the retention time on the Customization
Configuration tab in the OEE User Assignment screen. To do this, on the SAP MII main menu screen, choose
Worker UI Management General Configuration .
You maintain the retention time for data of an entire plant.
The file path to the two transactions used to delete data are:
ÑíW]˛ë SAPMPM/apps/DataArchive/ArchiveHANAReplicatedTables: This deletes data already replicated
to SAP HANA.

22/42 PUBLIC 2014-01-10

 4 Operations Information
4.5 Managing SAP OEE

£‡2HÂ4 SAPMPM/apps/DataArchive/ArchiveNonHANAReplicatedTables: This deletes data not replicated

to SAP HANA.
All transactional data is deleted after the retention period. Master data is not deleted.
You can either create schedulers for these transactions or run the transactions manually.

4.5 Managing SAP OEE

4.5.1 Starting and Stopping
1. Choose SAP NetWeaver Administrator Operations Systems Start & Stop .
2. Choose the Java Applications tab page and search for xapps~mpm~ear.
3. Start or stop the applications.

4.5.2 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in
case of failure.
The backup and restore strategy for SAP OEE consists of the following:
£‡2HÂ4 Backup and restore coverage for each component
£‡2HÂ4 Cross-system data dependencies and handling
The backup and restore strategy for your system landscape should not only consider SAP systems but
should also be embedded in overall business requirements and incorporate your company's entire
process flow.
In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of
a data center through fire. It is most important in this context that you ensure that backup devices are
not lost together with normal data storage (separation of storage locations).
Based on the type of application data contained in a component, we have introduced a categorization
scheme for system components that can be used to analyze the backup requirements of any system
component and to easily determine an appropriate backup method for this component.
SAP OEE data is stored in the SAP NetWeaver database; therefore, you can use the SAP NetWeaver Java
Application Server backup process to back up SAP OEE.
For more information about backing up and restoring your SAP NetWeaver Java Application Server
system, see https://service.sap.com/nw73 Operations .

4.5.3 Load Balancing

Logging on and load balancing for SAP OEE is handled by SAP NetWeaver Java Application Server. SAP
OEE data is stored in the SAP NetWeaver Java Application Server database.

2014-01-10 PUBLIC 23/42

4 Operations Information
4.6 High Availability

For more information in NW730, see Server Selection and Load Balancing Using the SAP Web Dispatcher in the
SAP NetWeaver Library on the SAP Help Portal at http://help.sap.com/nw730 SAP NetWeaver .

4.6 High Availability

When the SAP NetWeaver server is restarted, the SAP OEE application is restarted.
For more information on disaster recovery steps in SAP NetWeaver, see SAP High Availability. In a
clustered environment, SAP NetWeaver may handle machine failover. However, running status of the
machine that crashed is lost.
For more information, see https://service.sap.com/nw73 Operations .
For more information on data consistency, see http://help.sap.com SAP NetWeaver 7.3 Including
Enhancement Package 1 Application Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle
Management Security and User Administration User Administration and Identity Management User Management of
the Application Server Java Checking the Consistency of Entries in the UME Database
For more information on data consistency, see http://help.sap.com SAP NetWeaver 7.3 Application
Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Security and User
Administration User Administration and Identity Management User Management of the Application Server Java
Checking the Consistency of Entries in the UME Database .

4.7 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and
testing procedures for complex software landscapes and multiple software development platforms.
These functions support your project teams, development teams, and application support teams. The
goal of Software Change Management is to establish consistent, solution-wide change management
that allows for specific maintenance procedures, global rollouts (including localizations), and open
integration with third-party products.
The following topics are covered:
Ñ·ñ›õ¸ Transport and Change Management: Enables and secures the distribution of software changes from the
development environment to the quality assurance and production environment.
Ñ·ñ›õ¸ Development Request and Development Release Management: Enables customer-specific maintenance
procedures and open integration with third-party products.
Ñ·ñ›õ¸ Template Management: Enables and secures the rollout of global templates, including localizations.
Ñ·ñ›õ¸ Quality Management and Test Management: Reduce the time, cost, and risk associated with software
changes.
Ñ·ñ›õ¸ Support Packages and SAP Notes Implementation: Provide standardized software distribution and
maintenance procedures.
Ñ·ñ›õ¸ Release and Upgrade Management: Reduces the time, cost, and risk associated with upgrades.

24/42 PUBLIC 2014-01-10

4 Operations Information
4.8 TroubleShooting

4.7.1 Transport and Change Management

SAP OEE Management has three configuration objects, for example, status, activity and production
operator dashboard (POD). As of now there is no way to transport those configuration. OEE CTC
template takes care of creation of default data for these entries.
SAP OEE also supports extension possibilities where in customer can write an SAP MII transaction and
plugin to a list of extension points. Change management for the same is handled by SAP MII workbench
with NWDI integration.
Other then the above mentioned scenarios there is no need of transport and change management.

4.7.2 Support Packages and Patch Implementation

We recommend implementing Support Package Stacks (SP-Stacks), which are sets of Support Packages
and patches for the respective product version that must be used in the given combination. You can
find detailed information about the availability of SP-Stacks for SAP OEE on the SAP Service Marketplace
at http://service.sap.com/sp-stacks.
For more information about the implementation of support packages and possible issues, see http://
service.sap.com/patches SAP Support Packages in Detail .
For information about the tools necessary for implementing patches, see the SAP Help Portal:
KK¡`ð· NW 730: http://help.sap.com/nwce SAP NetWeaver Composition Environment Software Life Cycle
Management .
KK¡`ð· NW730 EHP1: http://help.sap.com/nwce of SAP NetWeaver CE General System Administration
Software Life Cycle Management .

4.8 TroubleShooting
To troubleshoot SAP OEE 1.0, check the logs by setting the logging level to ALL and viewing the tracing
locations for errors.
For general troubleshooting information, see the SAP NetWeaver Java Application Server on the SAP
Help Portal:
KK¡`ð· NW 730:See the SAP Technology Troubleshooting guide on http://wiki.sdn.sap.com/wiki/
display/TechTSG.

KK¡`ð· SAP NetWeaver Composition Environment (SAP NetWeaver CE) 7.1 EHP1 SP05: http://
help.sap.com/nw73 System Administration and Maintenance Information .

2014-01-10 PUBLIC 25/42

4 Operations Information
4.9 Support Desk Management

4.9 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support
organization that integrates your users, internal support employees, partners, and SAP Active Global
Support specialists with an efficient problem resolution procedure.
For support desk management, you need the methodology, management procedures, and tools
infrastructure to run your internal support organization efficiently.

4.9.1 Remote Support Setup

For information about SAP support requests for access to your SAP OEE data, see SAP Note 508140.
A support user with an SAP OEE read-only role, SAP_OEE_Read_Only, is used to log into SAP OEE.

4.9.2 Problem Message Handover

To send SAP OEE problem messages or tickets to SAP support, use the appropriate component from
the following SAP OEE component hierarchy in the SAP Customer Support System:
Ÿ'Næ MFG
Ÿ'N› MFG-MPM (Manufacturing Performance Management)

26/42 PUBLIC 2014-01-10

5 Security Information
5.1 User Administration and Authentication

5 Security Information

5.1 User Administration and Authentication

SAP OEE uses the user management and authentication mechanisms provided with the SAP NetWeaver
platform, in particular the SAP NetWeaver Application Server Java. Therefore, the security
recommendations and guidelines for user administration and authentication as described in the SAP
NetWeaver Application Server Java Security Guide also apply to SAP OEE.
For more information, see the SAP Help Portal at http://help.sap.com/nw73 Security Guide .
In addition to these guidelines, we include information about user administration and authentication
that specifically applies to SAP MII.

5.1.1 User Management

User management for SAP OEE uses the mechanisms provided with SAP NetWeaver Application Server
Java, such as tools and password policies. SAP OEE does not support the SAP NetWeaver Technical User
concept.
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 Including
Enhancement Package 1 Application Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle
Management Security and User Administration User Administration and Identity Management User Management of
the Application Server Java
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 Application
Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Security and User
Administration User Administration and Identity Management User Management of the Application Server Java

5.1.2 User Administration Tools

User management and user administration in SAP OEE is handled by the SAP User Management Engine
in SAP ERP.

5.1.3 Standard Users

SAP OEE delivers one standard user called OEE_ADMIN who can perform some of the administrative
configuration. You must create users in the SAP User Management Engine in SAP ERP.

2014-01-10 PUBLIC 27/42

5 Security Information
5.2 Authorizations

5.1.4 Integration Into Single Sign-On Environments

SAP OEE supports the SSO mechanisms provided by SAP NetWeaver 7.3. Therefore, the security
recommendations and guidelines for user administration and authentication as described in the SAP
NetWeaver 7.3 Security Guide also apply to SAP OEE. The supported mechanisms are as follows:
nS}mg¢ Secure Network Communications (SNC)
SNC is available for user authentication and provides for an SSO environment when using remote
function calls. For more information, see Secure Network Communications (SNC) in the SAP NetWeaver
Application Server Security Guide.
nS}mg¢ SAP Logon Tickets
SAP OEE supports the use of logon tickets for SSO when using a Web browser as the front-end
client. In this case, users can be issued a logon ticket after they have authenticated themselves with
the initial SAP system. The ticket can then be submitted to other systems (SAP or external systems)
as an authentication token. The user does not need to enter a user ID or password for authentication
but can access the system directly after the system has checked the logon ticket.
You can find more information under Logon Tickets in the SAP NetWeaver Application Server Security
Guide.
nS}mg¢ Client Certificates
As an alternative to user authentication using a user ID and passwords, users using a Web browser
as a front-end client can also provide X.509 client certificates to use for authentication. In this case,
user authentication is performed on the Web server using the Secure Sockets Layer Protocol (SSL
Protocol) and no passwords have to be transferred. User authorizations are valid in accordance
with the authorization concept in the SAP system.
You can find more information under Client Certificates in the SAP NetWeaver Application Server Security
Guide.

5.2 Authorizations
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 based on roles.
For role maintenance, use the user administration console in the SAP User Management Engine in SAP
ERP.
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 Including
Enhancement Package 1 Application Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle
Management Security and User Administration User Administration and Identity Management User Management of
the Application Server Java .

28/42 PUBLIC 2014-01-10

5 Security Information
5.2 Authorizations

For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 Application
Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Security and User
Administration User Administration and Identity Management User Management of the Application Server Java .
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 UME user group in OEE User Admin Group Assignment and User Group
Dashboard Assignment.
When users log on to the dashboard of SAP OEE for the first time, they are automatically logged on to
the first client, plant and the work unit. It is possible to assign default client, plant, and work unit to a
user.
To be able to assign this to a user in UME, first create a default client, plant, work unit, and POD 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:
á¢!G‡ Default Client
á¢!G‡ Default Plant
á¢!G‡ Default Work Unit
á¢!G‡ Default POD
4. Save your entries.
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:

Action Type Description
OEEProductionRun_Read Transaction Action to enable read of shift related
data collection header data.

2014-01-10 PUBLIC 29/42

5 Security Information
5.2 Authorizations
Action
OEEReleaseDemand_Read
OEEReportDowntime_Read
OEEDataCollection_Read
OEEProductionOrder_Read
OEEProductionRun_Operator
OEEProductionRun_Create_Upda Transaction
te
OEEReleaseDemand_Create_Upda Transaction
te
OEEProductionRun_All
OEEReleaseDemand_All
OEEReportDowntime_All
OEEDataCollection_All
OEEProductionOrder_All
OEEQueueMonitor_All
OEEQueueMonitor_Read
OEEWorkflowConfig_All
OEEWorkflowConfig_Read
OEEGlobalConfig_All
OEEGlobalConfig_Read
30/42
Type Description
Transaction Action to enable read of operation
level demand data.
Transaction Action to enable read of reported
down times.
Transaction Action to enable read of reported
data collection.
Transaction Action to enable read of production
order.
Transaction Action to enable read and change
production activity
Actions to enable create and update
of shift related data collection
header data. This is required close a
shift.
Actions to enable create and update
of operation level demand data. This
is required to do close order
Transaction Action to enable all operation on
shift related data collection header
record.
Transaction Action to enable all operation on
operation level demand data.
Transaction Action to enable all operation for
report down times.
Transaction Action to enable all operation for
data collection and report all
quantity.
Transaction Action to enable all operation for
production order.
Transaction Action to enable create, read,
update, and delete of entries in the
OEE integration queue.
Transaction Action to enable read of OEE
integration queue.
Configuration Action to enable create, read,
update, and delete of workflow
configurations.
Configuration Action to enable read of workflow
configurations.
Configuration Action to enable create, read,
update, and delete of global
configurations.
Configuration Action to enable read of global
configurations.
PUBLIC 2014-01-10
5 Security Information
5.2 Authorizations

Action Type Description

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
configuration.
OEEPod_Read Configuration Action to enable read of dashboard
configuration.
OEEUserGroupPodAssignment_R Configuration Action to enable read of user group
ead dashboard assignment.
OEECustomizationName_Read Configuration Action to enable read of
customization name.
OEECustomizationValue_Read Configuration Action to enable read of
customization value.
OEEConfigUserGroupAssignment Configuration Action to enable read of users who
_Read have authorization to assign user
groups to dashboard.
OEEUserGroupAssignment_Read Configuration Action to enable read of user group
assignment.
OEEScheduledDown_Read Configuration Action to enable read of schedule
down.
OEEStatus_Read Configuration Action to enable read of status
configuration.
OEEActivity_All Configuration Action to enable all operation on
activity. It is required to create and
update activities.
OEEPod_All Configuration Action to enable all operation on
dashboard. It is required to create
and update dashboards.
OEEUserGroupPodAssignment_Al Configuration Action to enable all operation on
l user group dashboard assignment. It
is required to assign dashboard to a
user group.
OEECustomizationName_All Configuration Action to enable all operation on
customization name. It is required
to create and update customization
names and their allowed values.
OEECustomizationValue_All Configuration Action to enable all operation on
customization value. It is required
to create and update customization
values and their details.
OEEConfigUserGroupAssignment Configuration Action to enable assignment of
_All authorization to users, who in turn

2014-01-10 PUBLIC 31/42

5 Security Information
5.2 Authorizations

Action Type Description

OEEUserGroupAssignment_All
OEEScheduledDown_All
OEEStatus_All
OEEExtension_All
OEEMasterConfiguration_Read
OEEReasonCodeMapping_Read
OEEReasonCodeMapping_All
OEEErpConfirmations_Read
OEEErpConfirmations_All
OEEExtension_Read
OEEIntegrationIdoc_All
OEEIntegrationReconcileIdoc_All Configuration
OEESAPIntQuery_All
can assign user groups to
dashboards.
Configuration Action to enable all operation on
user group assignment. This is
required to assign users the
authorization to perform user
group dashboard assignment.
Configuration Action to enable all operation on
scheduled down maintenance. This
is required to create and update
scheduled downs.
Configuration Action to enable all operation on
status. This is required to create and
update status configurations.
Configuration Action to enable all operation on
extension maintenance.
Configuration Action to enable read of SAP ERP
master and configuration objects.
Configuration Action to enable read of assigned
reason codes in configuration.
Configuration Action to enable permissions to
assign or delete assignment of
reason codes in configuration.
Configuration Action to enable read of
confirmation related data.
Configuration Action to enable permission to send
confirmations.
Configuration Action to enable read of extensions
maintained.
Configuration Action to enable execution of IDocs.
Action to enable reconcile IDocs.
Configuration Action to enable all permissions for
SAP integration query object.

SAP OEE delivers the following roles and their associated actions:
Role Name Description
OEE_OPERATOR Assign this role to the operator who
would do all data collection using
operator dashboard.
This role has all authorization to
report production, rejection, and
other data collection. The role also
has authorization to report
downtimes and uptimes on a work
unit.
Associated Actions
OEEProductionRun_Operator
OEEReportDowntime_All
OEEDataCollection_All
OEEProductionOrder_All
OEEExtension_Read
OEEReasonCodeMapping_Read
OEEStatus_Read

32/42 PUBLIC 2014-01-10

5 Security Information
5.2 Authorizations

Role Name Description Associated Actions

The role, however, has only read
authorization on configuration
data.
OEE_SUPERVISOR Assign this role to a supervisor who OEEProductionRun_Create_Upda
has additional authorizations to
start, stop, resume, close shift, and OEEReleaseDemand_Create_Upda
complete order.
The role also has the required
authorization on some
configuration activities.
OEEScheduledDown_Read
OEEUserGroupPodAssignment_R
ead
OEEUserGroupAssignment_Read
OEEConfigUserGroupAssignment
_Read
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_Read
te
te
OEEReportDowntime_All
OEEDataCollection_All
OEEProductionOrder_All
OEEExtension_Read
OEEReasonCodeMapping_Read
OEEStatus_Read
OEEScheduledDown_Read
OEEUserGroupPodAssignment_R
ead
OEEUserGroupAssignment_Read
OEEConfigUserGroupAssignment
_Read
OEEProductionOrder_Read
OEECustomizationValue_Read
OEEPod_Read
OEECustomizationName_Read
OEEActivity_Read

2014-01-10 PUBLIC 33/42

5 Security Information
5.2 Authorizations

Role Name Description Associated Actions

OEE_ADMIN This role is for allowing access to
OEE configuration screens.
OEE_SUPERADMIN This role has all authorizations. This OEEProductionRun_All
role also has some specific actions to OEEReleaseDemand_All
set up user group admin for specific
plants.
OEEQueueMonitor_Read
OEESupportedPlants_Read
OEEWorkflowConfig_Read
OEEGlobalConfig_Read
OEEMasterConfiguration_Read
OEEReasonCodeMapping_Read
OEEERPConfirmations_All
OEEActivity_All
OEEPod_All
OEEUserGroupPodAssignment_Al
l
OEECustomizationName_All
OEECustomizationValue_All
OEEConfigUserGroupAssignment
_All
OEEUserGroupAssignment_All
OEEScheduledDown_All
OEEStatus_All
OEEReasonCodeMapping_All
OEEExtension_All
OEEQueueMonitor_All
OEESupportedPlants_All
OEEWorkflowConfig_All
OEEGlobalConfig_All
OEEMasterConfiguration_Read
OEEReasonCodeMappingAll
OEEErpConfirmations_All
OEEExtension_Read
OEEReportDowntime_All
OEEDataCollection_All
OEEActivity_All
OEEUserGroupPodAssignment_Al
l
OEEUserGroupAssignment_All
OEEScheduledDown_All
OEECustomizationName_All
OEECustomizationValue_All
OEEProductionOrder_All
OEEExtension_All

34/42 PUBLIC 2014-01-10

5 Security Information
5.2 Authorizations

Role Name Description Associated Actions

OEE_INTEGRATOR This role is for enabling the
integration from ERP to OEE.
OEEStatus_All
OEEReasonCodeMapping_All
OEEPod_All
OEEQueueMonitor_All
OEESupportedPlants_All
OEEWorkflowConfig_All
OEEGlobalConfig_All
OEESAPIntQuery_All
OEEMasterConfiguration_Read
OEEReasonCodeMapping_All
OEEERPConfirmations_All
OEEIntegrationIdoc_All
OEEIntegrationReconcileIdoc_All
OEEReleaseDemand_Create_Upda
te
OEEExtension_Read
OEEReasonCodeMapping_Read
OEEStatus_Read
OEEScheduledDown_Read
OEEUserGroupPodAssignment_R
ead
OEEUserGroupAssignment_Read
OEEConfigUserGroupAssignment
_Read
OEECustomizationValue_Read
OEEPod_Read
OEECustomizationName_Read
OEEActivity_Read
OEEProductionRun_Read
OEEReleaseDemand_Read
OEEProductionRun_Operator
OEEReportDowntime_All
OEEDataCollection_All
OEEProductionOrder_All
OEEQueueMonitor_All
OEESupportedPlants_Read
OEEWorkflowConfig_Read
OEEGlobalConfig_Read
OEESAPIntQuery_All
OEEMasterConfiguration_Read
OEEReasonCodeMapping_Read

2014-01-10 PUBLIC 35/42

5 Security Information
5.2 Authorizations

Role Name Description Associated Actions

OEEERPConfirmations_All
OEE_READ_ONLY This role is to allow a user to see all OEEProductionRun_Read
the data on the dashboard. OEEReleaseDemand_Read
However, no reporting or editing is
OEEReportDowntime_Read
possible.
OEEDataCollection_Read
OEEProductionOrder_Read
OEEExtension_Read
OEEReasonCodeMapping_Read
OEEStatus_Read
OEEScheduledDown_Read
OEEUserGroupPodAssignment_R
ead
OEEUserGroupAssignment_Read
OEEConfigUserGroupAssignment
_Read
OEECustomizationValue_Read
OEEPod_Read
OEECustomizationName_Read
OEEActivity_Read
OEEQueueMonitor_Read
OEESupportedPlants_Read
OEEWorkflowConfig_Read
OEEGlobalConfig_Read
OEEMasterConfiguration_Read
OEEReasonCodeMapping_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 set up.
2. OEE_INTEGRATOR: This user has the OEE_INTEGRATOR role which 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:
å¶zaí SAP_XMII_Administrator
å¶zaí SAP_XMII_User
å¶zaí SAP_XMII_Developer
å¶zaí SAP_XMII_DynamicQuery
å¶zaí SAP_XMII_Read_Only

36/42 PUBLIC 2014-01-10

5 Security Information
5.3 Session Security Protection

Ã5ôÓÓÄ SAP_XMII_Super_Administrator
Ã5ôÓÓÄ 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 14.0
Security Information .
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.

5.3 Session Security Protection

To prevent access in javascript or plug-ins to the SAP logon ticket and security session cookie(s), we
recommend activating secure session management.
We also highly recommend using SSL to protect the network communications where these security-
relevant cookies are transferred.

5.4 Network and Communication Security

Your network infrastructure is important in protecting your system. Your network needs to support
the communication necessary for your business needs without allowing unauthorized access. A well-
defined network topology can eliminate many security threats based on software flaws (at both the
operating system and application level) or network attacks such as eavesdropping. If users cannot log
on to your application or database servers at the operating system or database layer, there is no way for
intruders to compromise the machines and gain access to the backend system’s database or files.
Additionally, if users cannot connect to the server local area network (LAN), they cannot exploit well-
known bugs and security holes in network services on the server machines.
The network topology for SAP OEE is based on the topology used by the SAP NetWeaver platform.
Therefore, the security guidelines and recommendations described in the SAP NetWeaver 73 Security
Guide also apply to SAP OEE.
Details that specifically apply to the SAP OEE are described in the Communication Channel Security
topic. This topic describes the communication paths and protocols used by SAP OEE.
For more information, see the following sections in the SAP NetWeaver Security Guide:
Ã5ôÓÓÄ Network and Communication Security
Ã5ôÓÓÄ Security Aspects for Connectivity and Interoperability

5.4.1 Communication Channel Security

The table below shows the communication channels used by SAP OEE, the protocol used for the
connection and the type of data transferred.

2014-01-10 PUBLIC 37/42

5 Security Information
5.5 Data Storage Security

Data Requiring Special

Communication Path Protocol Used Type of Data Transferred Protection
Frontend client using a Web HTTPS All application data Credential Store Data,
browser to application server Configurations
Import/ export
Application server to SAP ERP SAP JRA, SAP Java All Business Data
Connector (SAP JCo)
Provided by SAP MII
Application server to shop floor TCP/IP All Business Data
systems

DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTP
connections are protected using the Secure Sockets Layer (SSL) protocol.

RECOMMENDATION

We strongly recommend using secure protocols (SSL, SNC) whenever possible.

For more information, see Transport Layer Security in the SAP NetWeaver Security Guide.

5.5 Data Storage Security

For more information, see the security guides of SAP NetWeaver 7.3 http://service.sap.com/
securityguide. Credentials, or the combination of a user name and password, are maintained in the
SAP MII credential store and stored in an encrypted form in the SAP MII database.

5.6 Ports
SAP OEE runs on SAP NetWeaver and uses the ports from the AS Java.
For more information, see the topics for AS Java Ports in the corresponding SAP NetWeaver Security
Guides.

5.7 Enterprise Services Security

The following chapters in the NetWeaver Security Guide and documentation are relevant for all
enterprise services delivered with SAP OEE:
•ˆá›±� Security Guide Web Services
•ˆá›±� Recommended WS Security Scenarios
•ˆá›±� SAP NetWeaver Process Integration Security Guide
Currently, SAP OEE does not support SystemCookiesDataProtection indicator of AS Java. Turn off the
indicator in Display Templates screen.

38/42 PUBLIC 2014-01-10

5 Security Information
5.8 Security Logging and Tracing

5.8 Security Logging and Tracing

Security-relevant changes are logged using a separate category (/system/security/audit/OEE) in the
standard SAP User Management Engine in SAP ERP logging file.
Security permissions for data servers and services are written to the security log with the SAP OEE
Security category. The data includes the previous value and the value to which the security permission
was changed.
Security permissions for transactions and templates are also written to the same log, but only a status
change is noted.

2014-01-10 PUBLIC 39/42

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example À«nì(Á Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
À«nì(Á Cross-references to other documentation or published works
Example À«nì(Á Output on the screen following a user action, for example, messages
À«nì(Á Source code or syntax quoted directly from a program
À«nì(Á File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

40/42 PUBLIC 2014-01-10

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP Group 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 AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.comhttp://service.sap.com/
instguidesinstguides

2014-01-10 PUBLIC 41/42

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.