Configuration Guide

Configuration Guide
Document version: 1.1 2014-05-16
PUBLIC
SAP Manufacturing Integration and Intelligence 15.0
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:xxx/xxx.
The following table provides an overview of the most important document changes.
Table 1
Version
Date
Description
1.0
2014-05-16
Initial document
1.1
2014-08-30
Added the section Transport OEE Configurations (SAP MII)
PUBLIC
&FP_Copyright;

Document History
Content
SAP MII Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Documentation Landscape for SAP Solutions and Business Scenarios . . . . . . . . . . . . . . . . . . . . 6
System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Creating users for MII 15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Initial Logon to SAP MII System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Integrating SAP MII with NWDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring Message Listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring JRA for the JRA Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring SAP MII Dataservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10
Configuring SAP MII Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11
Configuring Connections in SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
12
KPI Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
13
Configuring Enhanced Change and Transport System (CTS+) with SAP MII . . . . . . . . . . . . . . . 26
14
Transporting OEE Configurations (SAP MII) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
15
Plant Information Catalog (PIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
16
SAP MII Mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
17
Configuring Dashboards Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
18
Configuring MII Crystal Reports Connector in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . 33
19
Configuring Solution Manager for SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
A
A.1
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Content
PUBLIC
&FP_Copyright;
PUBLIC
&FP_Copyright;
SAP MII Configuration Guide
This business scenario configuration guide applies to general configuration of SAP MII 15.0. This includes
configurations that are needed only once as well as configurations that may be needed more than once during the
usage of SAP MII 15.0.
The business scenario configuration guide contains steps required to implement various business scenarios in SAP
MII.
Business Scenario and Application Components
Table 2
Business Scenario
Application Components
Creating User for MII 15.0
SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

SAP Netweaver 7.30 or higher
Integrating MII with NWDI

SAP Netweaver Development Infrastructure
Configuring Listeners for IDOC/RFC Communication

SAP ERP
Configuring JRA for the JRA Actions

SAP ERP
Configuring MII Dataservers

Configuring MII Schedulers

Configuring Connections in MII

KPI Monitor

Enhanced Change and Transport System (CTS+)

Plant Information Catalog

Note
For more information about the necessary components and releases, see service.sap.com/instguides.

SAP MII Configuration Guide
PUBLIC
&FP_Copyright;
Documentation Landscape for SAP

Solutions and Business Scenarios
This documentation gives you an overview of the major sources of information available to you on SAP solutions and
business scenarios. Always use the current documents in your implementation.
Current Documents
Table 3
Document
Quick Links on the SAP Service Marketplace
Business Scenario Description
service.sap.com/instguides
Master Guide, Installation and Upgrade Guides
service.sap.com/ibc
Business-Scenario Configuration Guide
service.sap.com/ibc
SAP Library
Help Portal (help.sap.com) with all releases of an SAP

component
To display the SAP Library in an SAP system, choose
Help
SAP Library
Current Supplementary Information

Table 4
Information
Quick Links on the SAP Service Marketplace
SAP Notes
service.sap.com/notes to search for SAP Notes

service.sap.com/instguides listed by installation
and upgrade guide
Prerequisites
The following documents are available for an SAP solution:
Master, Installation, and Upgrade Guides
These documents describe how you install or upgrade the system landscape required by a business scenario. The
central initial access document for each SAP solution is the Master Guide. It lists the SAP application components
and third-party applications required by each business scenario and refers to their installation and upgrade guides.
These are component installation guides, business scenario upgrade guides, and component upgrade guides.
Business Scenario Configuration Guide
This document describes the settings you use to configure the SAP application components and third-party
applications required for a specific business scenario. It contains information specific to business scenarios for the
particular IMG activity. It does not reiterate the Customizing documentation but refers to particular IMG texts.
Business Scenario Description
PUBLIC
&FP_Copyright;

Documentation Landscape for SAP Solutions and Business Scenarios
This document describes how a business scenario runs once all components have been installed and configured. All
the business processes of a business scenario are represented graphically in the component view, which illustrates
the process steps of each SAP component.
SAP Library
This contains the entire documentation of SAP components and business scenarios. The business scenario
description is part of the SAP Library.

Documentation Landscape for SAP Solutions and Business Scenarios
PUBLIC
&FP_Copyright;
System Connections
Prerequisites
You have installed the components listed in the Software Component Matrix section in the SAP Manufacturing
Integration and Intelligence (SAP xMII) Master Guide. For more information, see service.sap.com/
instguides.
You have already read the Scenario & Process Component List, which is found on the SAP Service Marketplace
at service.sap.com/scl.
PUBLIC
&FP_Copyright;

System Connections
Creating users for MII 15.0
In order to access SAP MII and implement SAP MII functionalities, various users with specific roles to perform specific
actions must be created. For SAP MII 15.0, following are the existing roles:
SAP_XMII_Administrator
SAP_XMII_Approver
SAP_XMII_Developer
SAP_XMII_DynamicQuery
SAP_XMII_ProjectManagement
SAP_XMII_Read_only
SAP_XMII_Super_Administrator
SAP_XMII_User
For more details, see Actions for Permissions [external document].
Procedure
1.
Logon to the SAP MII system http://<MII servername>:<port>/nwa.
2.
Logon to the Netweaver Administration (nwa) by providing valid credentials.
3.
Choose
Configuration tab
4.
Choose
General Information
5.
On the Assigned Roles tab, enter *MII* in the Search Criteria field.
6.
Choose Go.
7.
Select the roles to be assigned to the current user and choose Add.
8.
Choose Save.
Identity Management
Details
Create User.
and enter the details.
An MII user will be created for the logged in user.

Creating users for MII 15.0
PUBLIC
&FP_Copyright;
Initial Logon to SAP MII System
Once the new MII user logs in for the first time into the SAP MII system, he will be prompted to change the initial
password that was defined while creating the user. Logon to the system using the URL <server protocol>://
<server>:<port>/XMII.
10
PUBLIC
&FP_Copyright;

Initial Logon to SAP MII System
Integrating SAP MII with NWDI
To integrate NWDI with SAP MII, you have to configure SLD in NetWeaver Administrator.
Procedure
1.
2.
3.
To configure SLD with SAP Netweaver, do the following:

1.
Choose
Configuration
Infrastructure
Java System Properties.
2.
Under Templates tab, select the instance id.
3.
Choose SDIC Services in Services tab.
4.
Enter sdic.sld.url in the Name column.
5.
Enter sdic.nwdiservers.admin.user with you user name.
6.
Choose Save.
Load the security certificates in NWA.

1.
Choose
2.
Filter for TrustedCAs in Key Storage Views.
3.
Choose Import Entry to import a certificate.
4.
Choose X.509 Certificate as Entry Type.
5.
Browse the certificate from your local system.
6.
Choose Import.
7.
Repeat Steps df to import all the certificates.
Configuration
Security
Certificates and Keys.
Setup your SAP MII system with NWDI configurations

Content Development
NWDI Configuration.
1.
On the SAP MII home page, choose
2.
Choose Edit and enter your user name and windows password.
3.
Select Enabled and Extended check boxes.
4.
In theDevelopment Configuration section, enter configuration name and support component in the relevant
fields.
5.
Choose Save.
You can perform DTR activities in the SAP MII Workbench.

Integrating SAP MII with NWDI
PUBLIC
&FP_Copyright;
11
Configuring Message Listeners
Configuring Message Listeners for IDOC/RFC Communication

SAP MII provides a set of pre-shipped IDOC and RFC listeners. These can be configured to receive IDOCs and RFCs
from an SAP ERP system. To enable the ERP system to issue RFCs or IDOCs for the SAP MII RFC Listener or IDOC
Listener, RFC Destinations must be defined on the ERP system. The configurations on SAP MII is as follows:
Procedure
Creating an IDoc Listener in SAP MII
1.
Logon to SAP Netweaver Administrator.
2.
On the Configuration tab, choose
Infrastructure
Application Resources.
The Application Resources: Overview screen appears.

3.
Choose Resource Adapters from the Show field.
4.
Select any IDoc that starts with XMII from the Resource Name column.
5.
Enter the following values in the Properties tab:
ProgramID: Server's program ID as defined in SAP ERP system
MaxReaderThreadCount: Maximum count of listening servers. The minimum count is 1.
SAPClient: Client of the SAP ERP system
UserName: User who can access the configured SAP ERP system
Password:
Language:
Server Name: SAP ERP Application Server name
Port Number: System number of SAP ERP system
Binding Key: XMIIIDOC
Note
This value is specific for XMII and should not be changed.
6.
Choose Save.
Testing the Connection for IDoc

1.
Logon to SAP MII system.
2.
Choose
3.
Select any message listener and choose Edit.
4.
Select message name/type from the Message Name field and choose Save.
5.
Choose Update.
6.
On the Configuration tab, check for SAP Server and client name. This should be the same as the SAP ERP system.
Message Services
Message Listeners.
A message regarding connection status appears on the Status tab.
12
PUBLIC
&FP_Copyright;

Check to see if IDocs or RFCs were received in SAP MII

1.
On the SAP MII administration menu, choose
Message Services
2.
Choose Advanced.
3.
Enter the time period in the From Time and To Date fields.
4.
Choose Go.
Message Monitor.
The IDocs or RFCs sent from the SAP ERP system will be visible in the Message Monitor screen.
Configuring Message Listener for HTTP Messages

SAP MII provides a pre-shipped message listener XMIIMESSAGELISTENER for HTTP messages. The message name
and Id fields can be configured either using the pre-shipped listener or by passing as parameters on this URL.
Following are the steps to configure these fields using the pre-shipped listener:
1.
2.
Select XMIIMESSAGELISTENER in the Message Listeners and choose Edit.
3.
Choose
4.
From the Schema column, browse and choose a schema.
5.
Choose Link Editor from XPath for Message Name column
Configuration
Message Services
Message Monitor.
Add.
The structure of the schema to choose the XPath for the message name appears.
6.
Repeat Step 5 to choose an XPath for Message ID.
Alternatively the parameters can also be passed as parameters using the URL, http://host:port//XMII/
Illuminator?
service=WSMessageListener&mode=WSMessageListenerServer&Name=<MessageName>MessageID=<Me
ssageID>
Specifying the MessageID parameter provides Exactly Once support for HTTP messages. For Exactly Once In Order
support, the URL needs to be configured with the additional parameters SequenceName and MessageNumber. The
URL for EOIO is as follows: http://host:port//XMII/Illuminator?
service=WSMessageListener&mode=WSMessageListenerServer&Name=<MessageName>MessageID=<Me
ssageID>&SequenceName=<SequenceName>&MessageNumber=<MessageNumber>.
Setting up a Message Processing Rule

Message processing rules determine the method to process incoming RFCs and IDOCs. Messages are processed
based on their type. A message processing rule can be created as follows:
1.
2.
Choose Create.
3.
Enter a rule name.
4.
Select the name of your IDoc Listener from the Message Listener dropdown list.
5.
The Message Type will be selected by default based on the Message Listener.
Message Services
Message Processing Rules.
You can also use wildcards in the Message Type field.

6.
Enter message name in the Message Name textbox.
7.
Choose Category/Transaction as the Processing Type.

For asynchronous mode of processing, choose Transaction. Browse for a valid transaction. Set the input
parameter to the correct xml input parameter name.
On choosing Transaction, the transactions in the SAP MII Workbench are displayed. Select the transaction
with transaction parameter of data type XML. Once selected, the transaction parameters are displayed in

PUBLIC
&FP_Copyright;
13
the Parameters table. Select the check box against the parameter to set the input parameter to the correct
XML input parameter name.
On choosing Category, choose Add, enter a category name and description and save.
Setting up a Message Cleanup Rule

The messages that are obsolete or no longer needed can be deleted from SAP MII through the message cleanup
rules. A message cleanup rule can be created as follows:
1.
Message Services
Message Cleanup Rules.
2.
Choose Create.
3.
Enter a rule name
4.
Select the name of your IDoc Listener from the Message Listener dropdown list.
5.
The Message Type will be selected by default based on the Message Listener.
6.
Enter message name or type in the Message Name textbox.
7.
Enter a value in hours in the Messages Older Than textbox
8.
Select the desired Processing Status.
9.
Select Enabled checkbox.
10. Choose Save.
14
PUBLIC
&FP_Copyright;

Prerequisites
You must have write permissions to the following pages:
Operation Management
Configuration Management
Systems
Start & Stop
Infrastructure
Application Resources
The above mentioned pages are located within the NetWeaver Administration (http://<server>:<port>/nwa)
configuration page.
Procedure
Starting the JRA Applications
1.
Login to the NetWeaver Administrator page (http://<server>:<port>/nwa).
2.
Choose
3.
Select the Java EE Applications tab.
4.
Enter jra in the application list filter box.
5.
Select tc~sapjra from the list.
Operation Management
Start & Stop.
Note
If status is Started, follow the steps as in the section Cloning the Default JRA Configuration.
6.
Choose Start in the Application Details section.
7.
Select On All Instances.
8.
Set Started as initial state option.
9.
Choose Save.
Cloning the Default JRA Configuration

1.
Login to the NetWeaver Administrator page (http://<server>:<port>/nwa).
2.
Choose
3.
Select JCA Resources.
4.
Select SAPJavaResourceAdapter15 from the Resource list.
5.
In the Resource Details section, select the Dependent JCA Connection Factories tab
6.
Choose Copy and Add New JCA Connection Factory to define JRA connection
7.
Enter relevant resource name for the JNDI (Java Naming Directory Interface) name.
Configuration Management
Infrastructure
You must following the standard naming convention. The recommended naming convention is <Company
name>/MIISyncComm1. In the actions, the resource MIISyncComm1 will appear as deployedAdapters/SAP/
MIISyncComm1/<type>/SAP/MIISyncComm1 where type can be as follows:

PUBLIC
&FP_Copyright;
15
NonGlobal: These connections are SAP ERP specific. Connections acquired from connection factory with
this setting will not be enlisted into distributed (Java Transaction API or JTA) transactions.
Shareable: This is an default JRA operation. All connections returned to the application will share one
physical connection. Only one physical connection is created even if the application wants to acquire 2 or
more connections form one resource adapter.
Unsharable: Each connection for the application will use separate physical connections from the connection
pool. 2 or more physical connections are created if the application requires 2 or more connections from
one resource adapter
8.
Choose Configuration Properties tab.
9.
Enter the following values for the JRA communication configuration:
SAPClient: SAP ERP Client number
UserName:
Password:
Language : Enter login language for the user
ServerName: The SAP ERP server URL as it resolves on your network (Fully Qualified)
PortNumber: ERP defined system number
Note
Additional parameters for Load Balancing across a cluster, such as MessageServer, SystemID, and Group
instead of ServerName and PortNumber can be assigned. For details on assigning the additional parameters,
see help.sap.com Parameters for SAP [external document] JRA Configuration.
10. Optionally, you can limit the size and connection wait time for the JRA connections in the connection pool by
selecting the Connection Pooling tab and entering values in the Maximum Connections and Maximum Time to
Wait for Connection (Sec.) fields
11. Choose Save.
12. Logon to the SAP MII Workbench and verify that your newly created adapter appears in the
Interface SAP JRA Start Session
16
PUBLIC
&FP_Copyright;
SAP JRA

Configuring SAP MII Dataservers
MII data servers can be configured in the SAP MII server using the Data Servers administration screen.
Procedure
Following are the configurations required for all data servers:
1.
From the Settings tab of the Details section, select Allow Dynamic Query checkbox.
2.
From the Users tab, search the users in the Available Users column. Add them to the Assigned Users column.
1.Configuring PCo Dataservers

1.
Logon to the SAP MII system using <Server Protocol>://<MI Servername>:<port>/XMII/

Menu.jsp.
2.
Enter valid credentials.
3.
4.
On the Data Services screen, choose Create.
Data Services
Data Servers.
The SAP MII: Data Servers screen appears.

5.
Enter the following details:
Server Name:
Connector Type:PCo Connector
Description: Description for the sevrer.
6.
Choose Next.
7.
Enter the URL of the Pco instance as <Server Protocol>://<PCo Servername>:<port>/PCo

Management or use the registered Pco instance.
For using the registered Pco instance, browse to choose the instance and choose Next.
8.
Enter credentials for the Pco server and choose OK.
9.
Choose one PCo Agent and choose Finish.
10. Select the Enabled.

11. Choose Save.
2.Configuring IDBC Dataservers

You have to upload Java Database Connectivity (JDBC) drivers. For more details, see Uploading JDBC drivers
[external document].
1.
Follow steps 16 as in section Configuring PCo Dataservers.

In Step 5, enter IDBC in the Connector Type field.
2.
Select Enabled checkbox in the Settings tab of the Details section.
3.
Enter the details in the Connection tab and choose Save. Following are some of the fields in the Connection tab:

PUBLIC
&FP_Copyright;
17
Table 5
Parameter
Description
DatePrefix
Prefix to the start date and end date parameters in query

templates used to format the date to match the database
configuration.
If you are connecting to a Microsoft SQL server database,
the typical prefix is a single quote. If you are connecting to
an Oracle database, an example of a prefix is GetDate('.
DateSuffix
Suffix to the start date and end date parameters in query

templates used to format the date to match the database
configuration.
If you are connecting to a Microsoft SQL server database,
the typical suffix is a single quote. If you are connecting to
an Oracle database, an example of a suffix is ','MM/DD/
YYYY HH24:MI:SS').
InitCommand
Command used by the database connector that is run when

a connection pool is created.
You can use it to set the database locale in Oracle.
InternalDateFormat
Date format used to construct WHERE clause conditions.

Controls the construction of the WHERE clause for date
comparisons for specific databases and servers.
JDBCDriver
Java Database Connectivity (JDBC) driver classpath used

to connect to the server.
See JDBC Drivers. [external document]
Password
Password to connect to the database.

The password field shows six asterisks even if your
password has more or less characters or is blank.
Passwords are not passed between browser clients and the
database. The Servers.xml file is not accessible through
the Web server.
PoolMax
Maximum number of connections the pool allocates.

If a request is received and all connections are in use and
allocated, the query waits for an available connection or the
specified timeout period.
PoolSize
Number of connections to be established with the database

when the connection pool is initialized.
ServerURL
Driver-specific string that defines how to access the

database.
For example, with the Microsoft SQL Server 2000 JDBC
driver, the ServerURL is: jdbc:inetdae://
hammer9:1433?
database=MyDatabase&sql7=true. The SQL
18
PUBLIC
&FP_Copyright;

Parameter
Description
server on machine hammer9 is connected to the
MyDatabase database using TCP/IP port 1433.

For additional URL parameters, see the documentation from
the vendor of the JDBC driver you are using.
TimeOut
Length of time (in minutes) that elapses before an unused

connection expires and its resources are released back to
the server. The connection pool maintains a minimum
number of connections and, if necessary, creates a new
connection.
UseCount
Number of times a connection can be used before it is

terminated and its resources are released back to the
server.
This parameter is only required for ODBC data sources that
have resource leaks when they execute many statements.
User Name
Database-specific user ID.
ValidationQuery
Query used to determine if a database connection is valid.

For example, when using Microsoft SQL Server, you can use
SELECT GETDATE() or SELECT * FROM Orders

WHERE OrderId=-1.
The query does not have to return rows, but it must succeed.
WaitTime
Amount of time SAP MII waits for a connection before it fails.
For details on the fields in the Connection tab, see Server Parameters. [external document]For other types of
data servers, see Data Servers. [external document]
For details on the fields in the Connection tab, see Server Parameters. [external document]

PUBLIC
&FP_Copyright;
19
10 Configuring SAP MII Schedulers
You use the SAP Manufacturing Integration and Intelligence (SAP MII) Scheduler to do the following:
Set up scheduled jobs
Run transactions, queries, and manufacturing data objects (MDO) on different schedules
View a summary of scheduled jobs
Procedure
To create a scheduled job, do the following:
1.
System Management
Scheduler.
2.
Choose Create.
3.
Enter a name for the scheduled job.
4.
Select the type of job (Transaction/Query/Manufacturing Data Object (MDO)/Key Performance Indicator) and
choose OK.
Configuring Scheduler for a Transaction

1.
On selecting a transaction, the Details screen appears.
2.
Enter the description.
3.
Select Enabled check box for the scheduler to be enabled and running at the specified scheduled time.
4.
Browse the folders in the SAP MII Workbench and select a transaction.
5.
Choose OK.
6.
Enter credentials in the User Name and Password fields.
7.
Choose a pattern for your scheduled job.
8.
Choose OK.
From the Persistence Transaction dropdown list choose the transaction, Always/On Error/Never. Also, you can
choose the log level.
Configuring Scheduler for a Query
1.
On selecting a query, the Details screen appears.
2.
3.
4.
Browse the folders in the SAP MII Workbench and select a query.
The parameters table displays the parameters of the selected query.
5.
Choose OK.
6.
7.
8.
Choose OK.
Configuring Scheduler for Manufacturing Data Object (MDO)

1.
20
On selecting a query, the Details screen appears.
PUBLIC
&FP_Copyright;

Configuring SAP MII Schedulers
2.
3.
4.
Browse the folders in the SAP MII Workbench and select an MDO.
5.
Choose OK.
6.
7.
8.
Choose OK.
9.
From the Mode field, select Replace/Update/Delete.
Replace: This mode will replace all the data in the result set of the MDO object with new data.
Update: Updates the current result set of the MDO object.
Delete: Allows the MDO query to perform delete operations on MDO object data.
The parameters table displays the parameters of the selected MDO.

10. Choose Add and enter parameter key and value.
11. From the Postexecution tab, browse and choose a transaction.
The table displays the parameters of the selected transaction.
12. Choose Add and enter the input parameters for the Delete MDO Query.
Configuring Scheduler for Key Performance Indicator (KPI)
1.
On selecting a KPI, the Details screen appears.
2.
3.
4.
Browse the folders in the SAP MII Workbench and select an KPI.
5.
Choose OK.
6.
7.
8.
Choose OK.
9.
From the Mode field, select Append/Delete.
Append: Appends the data to the existing result set of the KPI object
Delete: Allows the KPI query to perform delete operations on the selected KPI object data.
The parameters table displays the parameters of the selected KPI.

10. Choose Add and enter parameter key and value.
11. From the Postexecution tab, browse and choose a transaction.
The table displays the parameters of the selected transaction.
12. Choose Delete to enable the delete tab.
13. Browse and select a KPI query template from the SAP MII Workbench.
14. Choose Add and save the scheduler.
15. Choose Run.
To edit a scheduled job, do the following:
1.
2.
Select the job from the table and choose Edit.
3.
From the Details section, edit the data and choose Save.
System Management
Scheduler.
To delete a scheduled job, do the following:

PUBLIC
&FP_Copyright;
21
1.
2.
Select the job from the table and choose Delete.
3.
Choose Yes.
22
PUBLIC
&FP_Copyright;
System Management
Scheduler.

11
Configuring Connections in SAP MII
You can maintain alias connection for the different MII connection types available on the Connections screen.
Everytime you connect to a server, you can provide connection alias details instead of providing connections details.
SAP MII 15.0 supports the following connection types:
BC (SAP Business Connector)
WAS (SAP NetWeaver Application Server)
JCO (SAP Java Connector)
JRA (Java Resource Adapter)
FTP (File Transfer Protocol)
MAIL (E-mail)
JMS (Java Message Service)
EJB (Enterprise JavaBeans)
CR (Crystal Reports)
Procedure
To configure JCo connection, do the following:
1.
Logon to the SAP MII system using <Server Protocol>://<MI Servername>:<port>/XMII/

Menu.jsp.
2.
Choose
3.
From the System Connections tab, choose Create.
Data Services
Connections.
The Connections Create screen appears.

4.
Enter a name and select JCo from the Connection Type field.
5.
Choose OK.
The Details section appears.
6.
Enter the following in the Settings tab.
Description:
Server: Hostname of the SAP system
Client: Client within the system that you want to access
System: Instance number for the SAP system
Pool Size: session timeout
Note
Default value is 10.
SSO:True/False (Check the checkbox if SSO is required and also maintain the credentials using Credential
Alias screen in SAP MII for the SAP system)
Language:

PUBLIC
&FP_Copyright;
23
7.
Choose Save.
Follow the above procedure for all connection types except for Crystal Reports. The following connection types are
available for Crystal Reports:
JDBC
Java Beans
XML and Web Services
Access/Excel
ADO.NET
Database Files
ODBC
OLAP
OLE DB
SAP Info Sets
In the Settings tab, you can select any of the above mentioned connection types for crystal reports and maintain the
connection parameters or properties
24
PUBLIC
&FP_Copyright;

12
KPI Monitor
KPI Monitor can be used to supervise the values of all those KPI(s) that are visible for the current users role. This
screen provides a search template and you can define a custom search based on your defined date range, a specific
set of dimensions and their values for any selected KPI . Thus, using the KPI Monitor, you can create and save different
search templates with different sets of KPI(s) and their specifications that you wants to monitor. On this screen, you
can also view KPI values graphically along with other details like Trend, Status, and many other specifications as
defined in the KPI file definition.
Procedure
1.
On the SAP MII: KPI Monitor screen, choose Create.
2.
Enter the name and description in the relevant columns.
3.
Select the duration in the Duration field.
4.
Choose Add.
The Available KPIs screen displaying a list of KPIs appears. Since the KPIs are role based, the KPIs assigned to
the user are displayed in this screen.
5.
From the Subscribe column, select the KPIs and choose OK.
The selected KPIs are now available in the Subscribed KPIs column.
6.
From the Selected Dimensions section, choose Add.

The Available Dimension(s) screen appears.
7.
Select the dimensions and choose OK.

The dimensions are added to the selected KPI. You can also specify values to the dimensions to query the KPI
values. .
8.
Choose Save.
To view the data for the selected KPI, choose Run.

To import and export the search templates between different systems, choose the relevant buttons from the SAP
MII: KPI Monitor screen.

KPI Monitor
PUBLIC
&FP_Copyright;
25
13
Configuring Enhanced Change and

Transport System (CTS+) with SAP MII
You have to register Enhanced Change and Transport System (CTS+) as RFC destination in the NetWeaver server.
Procedure
1.
Logon to the SAP NetWeaver administration screen using administrator credentials.
2.
Go to Configuration/Security/Destinations.
3.
Choose Create in the Destinations List table.

The Destinations screen appears.
4.
5.
Enter the following:
Hosting System:Local Java System N73
Destination Name:sap.com/com.sap.tc.di.CTSServer
Destination Type:RFC
Choose Next.
The Connection screen appears.
6.
7.
Target Host: Name of the CTS system
System Number: CTS system number
System ID: CTS system ID
Choose Next.
The Authentication screen appears.
8.
9.
Authentication User:
Language:
Client:
User Name: CTS system user name
Password: CTS system password
In the Repository Connection, enter the details in Destination name, User Name and Password.
10. Choose Finish.

To test the RFC connection, select the created destination in the Destination List table, choose Ping Connection
button in the Destination Details column. A success message appears.
To create an application in the CTS system, see SAP Help Portal at http://help.sap.com Application Lifecycle
Mgmt CTS PLUG-IN 1.0 Change and Transport System (Including CTS Plug-In) Change and Transport System
- Overview (BC-CTS) Performing Configuration Steps for Non-ABAP Transports Connecting Further Applications
with the Change and Transport System Configuring Source Systems for Further Applications.
26
PUBLIC
&FP_Copyright;

Configuring Enhanced Change and Transport System (CTS+) with SAP MII
14 Transporting OEE Configurations (SAP MII)
Procedure
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. XML files are created 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+).
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, the following OEE-specific configurations can be exported:
Table 6
Configuration
Associated XML File
Dashboard Configuration
OEEPod.xml
Activity Configuration
OEEActivity.xml
Order Status Description
OEEStatus.xml
Workflow Configuration
OEEWorkflow.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.
6.
Depending on the export method you choose, the zipped XML 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.
When export is done using CTS+, the configurations are automatically implemented in the target system.

Transporting OEE Configurations (SAP MII)
PUBLIC
&FP_Copyright;
27
15
Plant Information Catalog (PIC)
Procedure
To import Plant Information Catalog (PIC) using SAP MII: Configurations screen:
You must have a change list.
The status of all the tags and groups in the working version must be Open or Marked for Delete.
A category is an identifier of a group or a tag in an enterprise. For example, Plant, Work Center, functional location
and so on. You can associate property sets to categories.
Following are the configurations for Plant Information Catalog (PIC):
Category
1.
From the SAP MII administration screen, choose
1.
Catalog Services
Catalog Services
Category
Add.
Category.
The Category screen appears.

2.
From the Category tab, choose Add.
3.
In the Name column, enter the name.
4.
Choose Add from the Property Set tab
5.
Select the property sets available in the Property Set tab.
6.
From the Localization tab, choose Add.
7.
Choose the language from the drop-down list.
Property Sets
1.
Catalog Services
Property Sets.
The Property Set screen appears.

2.
Choose Add.
3.
In the Property Set tab, enter the name and description in the Property Set and Description fields.
Roles for Approver

The role of the approver is to verify whether the changes to the groups, tags, property sets, and categories are
available in the Plant Information Catalog. To approve your change lists, you must be assigned the role
SAP_XMII_ADMINISTRATOR or SAP_XMII_SUPER_ADMINISTRATOR. You must be assigned the role
SAP_XMII_APPROVER to approve change lists created by others.
Configuration of SAP ERP system with SAP MII

You have configured the SAP ERP system. You can use the resource adapter MII Plant Information Catalog
Connection to point to the desired SAP ERP system and to get Production Planning (PP) and Plant Maintenance
(PM) hierarchies. To do so:
1.
Logon to the NetWeaver administration screen using the URL <host>:<port>/nws.
2.
Choose
28
Configuration
PUBLIC
&FP_Copyright;
Infrastructure

3.
From the drop-down list, choose Resource Adapters.
4.
Select MII Plant Information Catalog Connection and configure the properties under the Properties tab.
More Information
To enable SAP ERP Production Planning and Plant Maintenence hierarchy integration with SAP MII Plant Information
Catalog, the following notes must be implemented:
1822818
1897708

PUBLIC
&FP_Copyright;
29
16
SAP MII Mail Configuration
Procedure
To send mail notifications for MII applications such as Alert Framework and Plant Information Catalog, do the
following configurations:
1.
To create a connection, do the following:

1.
On the SAP MII Administration Menu, choose
Data Servers
Connections
Create.
The SAP MII: Connections screen appears.

2.
Enter MII_MAIL_CONFIG in the Connection Name field.

The Details screen appears.
3.
2.
Enter the details of the mail server.
Choose
Security Services
Credential Stores
Create.
The SAP MII: Credential Stores screen appears.

3.
Enter MII_MAIL_ADMIN in the Name field.

The Details screen appears.
4.
30
Enter the details of the mail server as in the Connections screen.
PUBLIC
&FP_Copyright;

SAP MII Mail Configuration
17
Configuring Dashboards Connector
You use SAP Business Objects Dashboards Integration to leverage data from SAP MII queries and SAP MII tag data
available in SAP Business Objects Dashboards to create powerful, interactive dashboards on top of real time
manufacturing data down to the machine level.
You use the Dashboard connector as a data source inside SAP Business Objects Dashboards to integrate with SAP
MII. A generated output flash file (.swf) can as well be embedded in any HTML/JSP/IRPT page in the SAP MII system.
To create customized, dynamic and interactive dashboards, you have to configure dashboards connector.
Prerequisites
You have:
Installed SAP Business Objects Dashboards 4.0 application in your local system from the service market place
( service.sap.com Software Downloads Installations and Upgrades A-Z Index SBOP Dashboards
4.0. )
Microsoft Excel
Downloaded Dashboards Connector from the Tools and Archive [external document] page
Flash Payer Version 10.3X or higher
Procedure
1.
Install the connector in the Dashboards 4.0 application. To do so:

1.
On the Dashboards 4.1 application, choose
File
Manage Add-ons
The Add-On Manager screen appears.

2.
Choose Install Add-On.
3.
Select MII Connector.
4.
Choose OK.
2.
On the Dashboard 4.0 application, choose
Data
Connections.
3.
Choose Add and select MII Connector from Add-On Connections.

The Data Manager screen appears.
4.
Configure the connector by entering connection name, protocol, machine name, port, credentials like username
and password, and WSDL paths.
5.
Choose Test Connection to verify connections.
6.
Choose, browse and select the query template by browsing through the project hierarchy.
7.
To check XML output, choose Preview XML.
8.
To bind the parameters to a spreadsheet, select a parameter from the Output Parameter field and choose the
cell selector
9.
and select an area in the spreadsheet.
On the Usage tab, select Refresh on Load.

PUBLIC
&FP_Copyright;
31
10. Close the connection dialog and choose a component that would render the value on the spreadsheet.
11. Choose Preview to preview the dashboard in the application.
12. To execute dashboards from SAP MII Workbenck, do the following:
1.
Export the dashboards by choosing

system.
File
Export
HTML.
Save the swf and html objects in the file
2.
Import the exported objects in MII Workbench by choosing the project under Web tab. choose import.
Choose the exported objects and say OK.
13. Choose Test to run the imported html file.
32
PUBLIC
&FP_Copyright;

18
Configuring MII Crystal Reports Connector

in Crystal Reports
Crystal Reports is a Business Objects tool used for reporting. Any MII user can create reports from MII query
templates.
Prerequisites
You have:
1.
Installed Crystal Reports 2011 from

A-Z Index Crystal Reports 2011.
service.sap.com
Software Downloads
Installations and Upgrades
Downloaded Crystal Report connector from the Tools and Archive [external document] page.
Procedure
To configure Crystal Reports 2011, do the following:
1.
Copy the connector to <CR_Install_Dir>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java

\lib\external.
2.
Update classpath element in CRConfig.xml to include path to the CRMIIConnector.jar file. The CRConfig.xml can
be located in CR_Install_Dir>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java where
<CR_Install_Dir> is the Crystal Reports installation directory.
To embed crystal reports to SAP MII web page (IRPT/JSP), do the following:
1.
Download custom tags sdk from SAP MII Admin page ( System Resources
Custom Report Tags. )
2.
Import crystalreportviewers folder available under WEB folder of your project to the Web tab of MII Workbench.
To do so, download Crystal Reports Runtime libraries for Java from www.businessobjects.com/campaigns/
forms/downloads/crystal/eclipse/datasave.asp. Extract the downloaded zip file to fetch the folder
crystalreportviewers. The extracted contents also contains the required Crystal Reports dependency jars
needed for creating the custom tags bundle.
Creating Connection to SAP MII Server

1.
Choose
Start
Crystal Reports 2011 .
The Crystal Report application appears.

2.
Choose
File
New
Blank Report .
The Database Expert screen appears.

3.
From Create New Connection, choose JDBC (JNDI).

The JDBC (JNDI) screen appears.
4.
Connection URL:jdbc:sapxmii://<Servername>:<port>/

Configuring MII Crystal Reports Connector in Crystal Reports
PUBLIC
&FP_Copyright;
33
In case of https connection, an additional parameter ssl is to be used in the URL that is, jdbc:sapxmii://
<Servername>:<port>>/?ssl=true and server certificate has to be imported into the jvm.
5.
Database Classname:com.sap.xmii.bobj.crystal.jdbc.CRMIIConnector
Choose Next.
The Connection Information screen appears.
6.
7.
Enter the credentials in the following fields:
UserID:
Password:
Choose Finish.
The connection is added to MyConnections and on expanding the connection the query templates for that MII
instance are listed.
34
PUBLIC
&FP_Copyright;

Configuring MII Crystal Reports Connector in Crystal Reports
19
Configuring Solution Manager for SAP MII
Procedure
Adding Java System to SLD
1.
Logon to the NetWeaver Administration screen in SAP MII system.
2.
Choose
Configuration
Security
Destinations.
The Destination Wizard screen appears.

3.
Enter the following details:
Destination Name:SLD_Client
Destination Type:HTTP
4.
Choose Next.
5.
Enter the sld url of the solution manager system URL field.
6.
Choose Finish.
7.
Create another destination with the following details:
Destination Name:SLD_DataSupplier
Destination Type:HTTP
8.
Choose Next.
9.
Enter the sld url of the solution manager system in the URL field.
10. Verify the configurations in the destination and SLD system by choosing
Data Supplier Configuration.
Configuration
Infrastructure
SLD
Adding Diagnostic Agent to SLD

1.
Goto SAP MMC and stop the diagnostic agent.
2.
Open a command prompt and navigate to the script folder of the agent path: usr/sap/<SID_AGT>/SMDAXX/
script
3.
Enter sapms://solman.full.qual.host.name port:<message server port> user:"SMD_ADMIN"

pwd:"XXXXXXXX".
4.
Enter the user name as SMD_ADMIN and relevant password.

A success message appears.
5.
Start the diagnostics agent from SAP MMC.
Loading Template XML to Solution Manager System

1.
Logon to SolMan system.
2.
Call the transaction solman_setup.

A web page appears.
3.
Choose
Administration
4.
Choose
Framework
5.
Select the system registered to the solution manager system from the views.
Solution Manager Administration
Infrastructure.
Root Cause Analysis.

PUBLIC
&FP_Copyright;
35
6.
Browse and select the XML file under Change Reporting Template Management section.
7.
Choose OK.
A success message appears if the XML is valid and well formed.
Configuring Managed System

1.
Logon to Solution Manager System.
2.
Call the transaction solman_setup.
3.
Choose Managed System Configuration.
4.
Select the java system and choose Configure System.

The java system and xMII software components are added if the check boxes in the Installed column are selected.
Additionally, verify if the checkbox in the Diagnostically Relevant column is selected.
5.
From the Select Product tab, select a system and choose Display Technical Configuration.
Verify if the Diagnostically Relevant checkbox is selected for the selected software components.
6.
From the Check Prerequisites tab, choose Prerequisites Check.

A list of major issues appears. Correct the issues and rerun the checks.
7.
From the Assign Diagnostics Agent tab, choose Agent Assignment, select the system and move to SLD Agent
Candidates tab.
8.
Select the corresponding agent, choose
Get Agents
Connect.
The Status column indicates that the agent is assigned to the managed system.
9.
Choose Enter System Parameters tab and enter all the relevant parameters of the managed system.
10. From the Enter Landscape Parameters tab, select the JAVA server and enter the parameters that were uploaded
as part of the template.
11. You can create users manually or from SolMan roles by choosing the Create Users tab.
12. On the Configure Automatically tab, check for the status of the Extractor Setup.
36
PUBLIC
&FP_Copyright;

Reference
A.1
The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various phases in the
life cycle of SAP software.
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many
glossary entries in English and German.
Target group:
Relevant for all target groups
Current version:
On SAP Help Portal at
In the SAP system in transaction STERM
help.sap.com Glossary
SAP Library is a collection of documentation for SAP software covering functions and processes.
Target group:
Consultants
System administrators
Project teams for implementations or upgrades
Current version:
On SAP Help Portal at help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising security
levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and
suggestions. SAP applications have a security guide of their own.
Target group:
Technology consultants
Solution consultants
Current version:
On SAP Service Marketplace at service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required installable units for
each business or IT scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an
implementation. It also provides references to other documents, such as installation guides, the technical infrastructure
guide and SAP Notes.
Target group:

Reference
PUBLIC
&FP_Copyright;
37
Project teams for implementations
Current version:
On SAP Service Marketplace at service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking into account the
combinations of operating systems and databases. It does not describe any business-related configuration.
Target group:
Current version:
Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle platform.
One of its main functions is the configuration of business scenarios, business processes, and implementable steps. It
contains Customizing activities, transactions, and so on, as well as documentation.
Target group:
Current version:
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing
activities and their documentation are structured from a functional perspective. (In order to configure a whole system
landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing
activities in the individual SAP systems, is used.)
Target group:
Project teams for implementations or upgrades
Current version:
In the SAP menu of the SAP system under
Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and
precedes the application operations guides of SAP Business Suite. The manual refers users to the tools and
documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance,
transports, and tests.
Target group:
Current version:
The application operations guide is used for operating an SAP application once all tasks in the technical operations
manual have been completed. It refers users to the tools and documentation that are needed to carry out the various
operations-related tasks.
Target group:
38
PUBLIC
&FP_Copyright;

Reference
Current version:
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP
solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers
to other documents, such as upgrade guides and SAP Notes.
Target group:
Project teams for upgrades
Current version:
The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of
operating systems and databases. It does not describe any business-related configuration.
Target group:
Current version:
Release notes are documents that contain short descriptions of new features in a particular release or changes to
existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for
generating delta and upgrade Customizing in the Implementation Guide (IMG).
Target group:
Consultants
Current version:
On SAP Service Marketplace at service.sap.com/releasenotes
In the SAP menu of the SAP system under

Reference
Help Release Notes
(only ABAP developments)
PUBLIC
&FP_Copyright;
39
Typographic Conventions
Table 7
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
Example
Arrows separating the parts of a navigation path, for example, menu options
Example
Emphasized words or expressions
Example
Words or characters that you enter in the system exactly as they appear in the documentation
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
Example
Hyperlink to an SAP Note, for example, SAP Note 123456
Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Example
Cross-references to other documentation or published works
Output on the screen following a user action, for example, messages
Source code or syntax quoted directly from a program
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
40
PUBLIC
&FP_Copyright;
Keys on the keyboard

Typographic Conventions
www.sap.com
&FP_Copyright;
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 www.sap.com/corporate-en/legal/copyright/
index.epx#trademark for additional trademark information and
notices.
Please see www.sap.com/corporate-en/legal/copyright/index.epx
for disclaimer information and notices.

Configuration Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Configuration Guide

Caricato da

Copyright:

Formati disponibili

Configuration Guide

Document version: 1.1 2014-05-16

SAP Manufacturing Integration and Intelligence 15.0

Added the section Transport OEE Configurations (SAP MII)

SAP Manufacturing Integration and Intelligence 15.0

SAP MII Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Documentation Landscape for SAP Solutions and Business Scenarios . . . . . . . . . . . . . . . . . . . . 6

Creating users for MII 15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Initial Logon to SAP MII System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Integrating SAP MII with NWDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring Message Listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring JRA for the JRA Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring SAP MII Dataservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring SAP MII Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring Connections in SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Transporting OEE Configurations (SAP MII) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Plant Information Catalog (PIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SAP MII Mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring Dashboards Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring MII Crystal Reports Connector in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring Solution Manager for SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SAP Manufacturing Integration and Intelligence 15.0

SAP Manufacturing Integration and Intelligence 15.0

SAP MII Configuration Guide

Creating User for MII 15.0

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Integrating MII with NWDI

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Configuring Listeners for IDOC/RFC Communication

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Configuring JRA for the JRA Actions

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Configuring MII Dataservers

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Configuring MII Schedulers

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Configuring Connections in MII

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Enhanced Change and Transport System (CTS+)

SAP Manufacturing Integration and Intelligence (SAP MII) 15.0

Plant Information Catalog

SAP Manufacturing Integration and Intelligence (SAP MII) 14.0

SAP Manufacturing Integration and Intelligence 15.0

Documentation Landscape for SAP

Quick Links on the SAP Service Marketplace

Business Scenario Description

Master Guide, Installation and Upgrade Guides

Business-Scenario Configuration Guide

Help Portal (help.sap.com) with all releases of an SAP

Current Supplementary Information

Quick Links on the SAP Service Marketplace

service.sap.com/notes to search for SAP Notes

SAP Manufacturing Integration and Intelligence 15.0

SAP Manufacturing Integration and Intelligence 15.0

SAP Manufacturing Integration and Intelligence 15.0

Creating users for MII 15.0

For more details, see Actions for Permissions [external document].

Logon to the SAP MII system http://<MII servername>:<port>/nwa.

Logon to the Netweaver Administration (nwa) by providing valid credentials.

and enter the details.

An MII user will be created for the logged in user.

SAP Manufacturing Integration and Intelligence 15.0

Initial Logon to SAP MII System