SAP MII

Among others, SAP Manufacturing Integration and Intelligence (MII) is used to integrate plants and enterprise systems. SAP MII is able to integrate with various system types, communicating via RFC, HTTP or SOAP calls (depending on the communication partner).

The following entities are important:

  • Transactions are used to execute synchronous or asynchronous processes within MII. Often the counterpart on SAP ERP side is communication via IDoc.
  • JCo Messages are used to transfer data in XML format. If SAP ERP is the communication partner usually BAPI calls are made via RFC.
  • Schedulers are responsible to schedule and run transactions, queries, and other objects in SAP MII.
  • Data servers / Message Listeners are used to communicate with plants and SAP ERP systems. They can be regarded as end points / ports for the message processing.

Technical Prerequisites

The following minimum system requirements apply:

  • SAP MII:
    • SAP MII 12.2
    • SAP MII 14.0
    • SAP MII 15.0
    • SAP MII 15.1

Note that metrics "Number of failed JCo messages", "Number of intermediate JCo messages", "Number of successful JCo messages", and "Average time to process JCo messages" require to have at least:

  • SAP MII 14.0, SP09
  • SAP MII 15.0, SP07
  • SAP MII 15.1, SP02

 See also SAP note 2377889 - System requirements for SAP MII monitoring via Interface & Connection Monitoring.

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

The available monitoring categories are:

  • MII: MII messages send and received from the SAP MII system

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options

MII 

For SAP MII Monitoring, you can collect all MII messages sent or received in the managed system. You can also use the following filter parameters, to restrict the data collection:

  • Message Type: RFC, IDOC or WebService.
  • Status Group: ERROR, PROCESSING, SUCCESSFUL
  • Status: select the desired status from the input help
  • Server name: Name of the server the transaction is running on
  • Category: Queue in which the message is saved in the buffer for sequential processing. Only available if the message has processing type Category.
  • Message Name: Name of the RFC (synchronous or asynchronous), IDoc type, or Web Service message.
 

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For interfaces of type MII the following metrics are collected:

MII 

  • MII messages in status "Error" for longer than N minutes: Indicates new MII messages in the status group ERROR were collected during the collection interval
    Metric parameters: 
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider MII messages older than [minutes] 
  • Number of MII messages in status "Backlog" for longer than N minutes: The number of MII messages in the status group PROCESSING found during the collection interval
    Metric parameters:  
    • STATUS_GROUP (not changeable) = PROCESSING
    • OLDER_THAN_MINUTES = Only consider MII messages older than [minutes]