Show TOC

Background documentationQueue Monitor Locate this document in the navigation structure


You use this activity to monitor and diagnose messages exchanged between SAP ERP and SAP ME.

On the Outbound ME Messages tab page, you can obtain information about collaboration messages sent from SAP ME that have not yet been moved from the Outbound ME Messages queue into the Integration Message Queue for processing by SAPMEINT (see Configuring SAP ME Outbound Collaboration).

To view child records for messages, choose the Advanced Queue Monitor button on the right.

To view all records or resize the table, use the Option menu on the right.

Example Example

  • You have sent a material message from SAP ERP to SAP ME.

  • In SAP ME, you determine the record was not received.

  • In Queue Monitor, you filter by the Document Type MATMAS03 and see that the status of your message is SPLIT_DONE, which indicates partial success.

    You filter by the Document Type Z_MATMAS03 and see that the status of your message is FAILED. The text in the Message column indicates you have created the material incorrectly in the ERP system.

  • You return to the SAP ERP system, correct the material, and resend the message.

    The Queue Monitor now displays a new set of MATMAS03 and Z_MATMAS03 messages with the statuses SPLIT_DONE and PASSED. The material record now appears in SAP ME.

End of the example.

Example Example

  • You have sent an inventory message from SAP ERP to SAP ME using the MIGO transaction and the 311 movement type.

  • In SAP ME, you determine the floor stock record was not received.

  • In Queue Monitor, you filter by the Document Type INVCON02_INV_PEG and the date and hour in which you sent the message. The text in the Message column in the search results indicates you have not previously sent the material for this inventory to SAP ME.

  • You return to the SAP ERP system, send the material message, and determine in Queue Monitor that the material message processed successfully.

  • In Queue Monitor, you filter again for your original inventory message, select it in the search results by clicking the row, and choose the Retry button once.

    The message processes with the PASSED status and the floor stock is received in SAP ME.

End of the example.

The following table describes fields requiring explanation:



Document Type

The type of workflow that is used to dispatch messages for processing.

Use to filter messages in the search results.

For more information, see Configuration of Standard SAPMEINT Interfaces.

Parent ID

The ID assigned to related messages during the split or correlation workflow.

The split workflow splits a single message into multiple messages. For example, the MATMAS03 IDoc that comes from SAP ERP may contain multiple plant data. SAPMEINT needs to create this material in many sites in SAP ME using many Web service calls.

The split workflow splits the MATMAS03 IDoc into multiple IDocs (with the type Z_MATMAS03) so that all the split documents are processed by the standard workflow.

The correlation workflow finds correlated messages and merges them into a single one based on a correlation key.


Identifies the objects for which the message was sent based on settings in SAPMEINT Workflow Configuration (see Modifying the Identifier Parameter).

By default, displays the following values:

  • Material — Plant (WERKS)-Material Number (MATNR)

    Note Note

    The split workflow does not display WERKS.

    End of the note.
  • BOM — Plant (WERKS)-Material Number (MATNR)-BOM Usage (STLAN)-Alternative BOM (STLAL)

  • Routing — Plant (WERKS) -Key for Task List Group (PLNNR) Group Counter (PLNAL)

  • Production order — Plant (WERKS)-Order Number (AUFNR)

  • Planned order — Plant (WERKS)-Planned order number (PLNUM)

  • Classification — Plant (WERKS)-Key of object to be classified (OBJEK)

    Note Note

    The split workflow does not display WERKS.

    End of the note.
  • Floor stock — Plant (WERKS)-Material Number (MATNR) - Material Document Number (MBLNR)-Line Number (ZEILE)

  • Service order — Plant (WERKS)-Order Number (AUFNR)

  • Work center — Plant (WERKS)-Work Center(ARBPL)

  • User — Document Number (DOCNUM)

  • Equipment status change — Plant (WERKS)-Equipment Number (EQUNR)-Order Number (AUFNR)

  • Document — Plant (WERKS) -Document Number (DOKNR)-Document Type (DOKTL)-Document Type (DOKAR)

  • Production order yield confirmation — Site-Shop Order-Step ID-SFC

  • Production order scrap confirmation — Site-Shop Order-Step ID-SFC

  • Planned order yield confirmation —Site-Production Version-Shop Order-Step ID-SFC

  • Planned order scrap confirmation — Site-Production Version-Shop Order-Step ID-SFC

  • Service order complete — Site-Shop Order

  • Quality notification — Site-Shop Order-Batch Number-Operation-NC Code

  • Equipment status change (Production and Unscheduled Down) Site-Equipment Number

  • Equipment usage — Site-Message ID

  • Maintain floor stock — Site-Floor Storage Location or Shop Order

Correlation Key

The key assigned to correlated messages during the correlation workflow.


Displays rows matching the Document Type that you have selected in the filtering field.

If you select All, the table displays all processed document types.


Allows you to select and re-process a message with the FAILED status in the search results, after correcting the cause of the failure.

Choose Retry only once, unless the message appears with the FAILED status again.


Deletes the selected message from the search results and removes the record from the database


Use to diagnose a selected message with the FAILED status in the search results.

On the Document Trace screen that appears after choosing Trace, you can select and view the Original Document, the Request, or the Response, depending on the workflow specifications.

Clear Form

Returns Queue Monitor to its default state without removing records from the database

Clear Dates

Removes the dates you have entered in the From and To fields