SAP MII Workbench Config Guide
SAP MII Workbench Config Guide
3 System Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
7 ADS Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 Configuring ADS Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
13 KPI Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
14 Configuring Enhanced Change and Transport System (CTS+) with SAP MII. . . . . . . . . . . . . . . 28
This business scenario configuration guide applies to general configuration of SAP MII 15.2. 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.2.
The business scenario configuration guide contains steps required to implement various business scenarios in
SAP MII.
Creating User for MII 15.2 SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Integrating MII with NWDI SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Configuring Listeners for IDOC/RFC Communication SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
SAP ERP
Configuring JRA for the JRA Actions SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
SAP ERP
Configuring MII Dataservers SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Configuring MII Schedulers SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Configuring Connections in MII SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Enhanced Change and Transport System (CTS+) SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Plant Information Catalog SAP Manufacturing Integration and Intelligence (SAP MII)
15.2
Note
For more information about the necessary components and releases, see service.sap.com/
instguides.
Use
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
SAP Library
Prerequisites
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.
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.
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.
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.
Use
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.2, 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
● SAP_XMII_PIM_Super_Administrator
● SAP_XMII_PIM_Administrator
For more details, see Actions for Permissions in the SAP MII help at http://help.sap.com/mii Security
Services User Management .
Procedure
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.
Use
To integrate NWDI with SAP MII, you have to configure SLD in NetWeaver Administrator.
Procedure
Use
You need to configure printing of production-related documents using SAP NetWeaver Adobe Document
Services component.
Prerequisites
● You have set up one or more network printers on your system network and installed printer drivers on the
server.
Note that after installing a new printer on Windows, SAP NetWeaver server must be restarted for having
access to the printers.
● You have granted appropriate rights to SAP NetWeaver Services starting user to access the network
printer. By default, SAP NetWeaver starting user is a local user that cannot access networks resources like
network printers. Contact your system administrator for more information. If SAP NetWeaver starting user
has been changed, stop SAP NetWeaver from sapmmc console, then stop corresponding OS services and
start all of them again.
Procedure
1. Install and configure SAP NetWeaver Adobe Document Services component as follows:
1. During the SAP NetWeaver installation, select to install the Adobe Document Services component.
After the installation, check if Adobe Document Services have been installed at http://
<nwhost>:<port>/nwa under Configuration Management Infrastructure Adobe Document
Services .
2. Create a user for basic authentication as follows:
1. Navigate tohttp://<server>:<port>/useradmin to start the User Management.
2. On the Identity Management tab page, select Search Criteria as Group.
3. Choose Create Group to create the ADSCallers group. Save the group.
4. Select User in the Search Criteria dropdown list.
5. Choose Create User and enter ADSUser for the user name, enter a password.
6. Under Security Policy, choose Technical User.
7. On the Assigned Roles tab page, in Available Roles, search for the SAP_ADSCALLER role and choose
Add to assign this role to the ADSUser user.
The SAP_ADSCALLER role was created during the installation of your system. Assign this role
only to the users that need to access Adobe document services.
Note
The Key Pair and Public-Key Certificate can be created through SAP NetWeaver Administrator. For
more information, see Creating a Key Pair and Public-Key Certificate and Signing It at http://
help.sap.com SAP NetWeaver 7.3 Function-Oriented View Adobe Document Services for
Form Processing Configuring Adobe Document Services for Form Processing (Java) .
3. Configure WSDL destination for X.509 client certificate authentication on MII server as follows:
1. Navigate to the SAP NetWeaver Administrator (NWA) at http://<server>:<port>/nwa.
2. Log on to the SAP NWA with a user that has administrator privileges.
3. In the SAP NWA, navigate to SOA Management Technical Configuration Destination
Template Management .
4. Choose New to create a logical port.
5. Choose WSDL as a destination type.
6. Enter SecureConfigPort_Document in the Destination Name field.
7. Enter https://<host>:<port>/AdobeDocumentServicesSec/Config?
wsdl&mode=ws_policy&style=document in the URL field and choose Next.
8. Choose HTTP Authentication in the Authentication group box and select the X.509 Client
Certificate indicator.
9. Choose the Details button. Choose DEFAULT as a Keystore view. Choose the view entry that was
imported in step 2 as a Private Key.
10. Choose Finish to save your entries.
For more information about configuration of SAP NetWeaver Adobe Document Services (ADS), see Configuring
Adobe Document Services for Form Processing (Java) at http://help.sap.com SAP NetWeaver 7.3
Function-Oriented View Adobe Document Services for Form Processing .
Use
SAP MII provides a set of pre-shipped IDOC and RFC listeners (synchronous and asynchronous). 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
Note
Note
These values are specific for MII. XMII and XMIISRFC are for RFC listeners and XMIIIDOC is for IDoc
listeners
Additionally, the following properties are required for load balancing in a cluster:
1. On the SAP MII administration menu, choose Message Services Message Monitor.
2. Choose Advanced.
3. Enter the time period in the From Time and To Date fields.
4. Choose Go.
The IDocs or RFCs sent from the SAP ERP system will be visible in the Message Monitor screen.
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. On the SAP MII administration menu, choose Message Services Message Monitor.
2. Select XMIIMESSAGELISTENER in the Message Listeners and choose Edit.
3. Choose Configuration Add.
4. From the Schema column, browse and choose a schema.
5. Choose Link Editor from XPath for Message Name column
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=
<MessageID>
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. On the SAP MII administration menu, choose Message Services Message Processing 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.
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 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.
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. On the SAP MII administration menu, choose 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.
Prerequisites
The above mentioned pages are located within the NetWeaver Administration (http://<server>:<port>/
nwa) configuration page.
Procedure
Note
If status is Started, follow the steps as in the section Cloning the Default JRA Configuration.
Note
Additional parameters for Load Balancing across a cluster, such as MessageServer, SystemID, and
Group instead of ServerName and PortNumber can be assigned.
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 SAP JRA
Interface SAP JRA Start Session
Use
MII data servers can be configured in the SAP MII server using the Data Servers administration screen.
Procedure
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.
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.
DateSuffix Suffix to the start date and end date parameters in query
templates used to format the date to match the database
configuration.
The query does not have to return rows, but it must suc
ceed.
For details on the fields in the Connection tab, see the topic Server Parameters in SAP MII application help
at http://help.sap.com/mii Data Services Data Servers Connectors . For other types of data
servers, see the topic Data Servers.
Use
You use the SAP Manufacturing Integration and Intelligence (SAP MII) Scheduler to do the following:
Procedure
From the Persistence Transaction dropdown list choose the transaction, Always/On Error/Never. Also, you can
choose the log level.
1. Select Virtual Tag . Select the Run Historical Data check box to run the job in History mode.
2. To run the job in Current mode, keep the Run Historical Data check box unchecked.
3. Choose OK. The details screen appears.
4. Enter the description.
5. Select Enabled check box for the scheduler to be enabled and running at the specified scheduled time.
6. Select the virtual tag for which the job should be run.
7. Enter credentials in the User Name and Password.
8. If the mode is history, specify the execution time, start time, and end time.
9. If the mode is current, define the pattern that determines the execution schedule.
10. Save the scheduler.
11. Choose Run.
Use
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.2 supports the following connection types:
Procedure
Note
○ 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)
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
Use
KPI Monitor can be used to supervise the values of all those KPI(s) that are visible for the current user’s 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
To import and export the search templates between different systems, choose the relevant buttons from the
SAP MII: KPI Monitor screen.
Use
You have to register Enhanced Change and Transport System (CTS+) as RFC destination in the NetWeaver
server.
Procedure
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
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:
Procedure
To import Plant Information Catalog (PIC) using SAP MII: Configurations screen:
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.
Category
1. From the SAP MII administration screen, choose Catalog Services Category Add.
Property Sets
1. On the SAP MII administration menu, choose 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.
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.
Access control for users can be configured for each node in the Plant Hierarchy. The users must be members
of user groups created in UME and the user groups can be given access to perform specific operations. The
following roles are used to control the access.
Users assigned with the role SAP_XMII_PIM_Super_Administrator has full access to the entire plant hierarchy
and can perform all operations. Super Administrators can assign Node Admins on PIM Node Admin tab.
Users assigned with the role SAP_XMII_PIM_Super_Administrator has full access to the entire plant hierarchy
and can perform all operations. Super Administrators can assign Node Admins on PIM Node Admin tab.
Users assigned with the role SAP_XMII_PIM_Super_Administrator has full access to the entire plant hierarchy
and can perform all operations. Super Administrators can assign Node Admins on PIM Node Admin tab.
Users assigned with the role SAP_XMII_PIM_Administrator can be added as Node Admins for PIC Node. Only
Super Administrators have access to assign Node Admins. Node Admins have full access to perform all
operations for that node. Node Admins can assign other User Groups and give relevant authorizations to
perform operations on that node.
PIM/PIC Users
Users assigned with the roles which contains the action XMII_Catalog_Editor or other related actions can be
given access to the node by adding the User Group in Node Authorization tab. User Group assignment can be
done by Super Administrators and Node Admins Permissions to read/write/delete/execute/transport can be
given to the User Group. User should have the role with the action XMII_PIM_RWDTransport additionally for
transporting PIM/PIC data. For more details, see the topic Actions and Permissions
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:
Note
You can also configure multiple ERP systems by selecting other adapters such as MII Plant Information
Catalog Connection 01, MII Plant Information Catalog Connection 02, MII Plant Information Catalog
Connection 03, and MII Plant Information Catalog Connection 04 and configure the same.
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
To send mail notifications for MII applications such as Alert Framework and Plant Information Catalog, do the
following configurations:
Use
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 (http://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 page.
● Flash Payer Version 10.3X or higher
Procedure
Use
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 http://service.sap.com Software Downloads Installations and
Upgrades A-Z Index Crystal Reports 2011.
For more information, see Tools and Archive topic in the SAP MII application help at http://
help.sap.com/mii Content Development SAP MII Hana Integration .
Procedure
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 http://
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.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.