Show TOC

Status Monitor for ALE MessagesLocate this document in the navigation structure

Use

You use the status monitor to monitor the processing status of IDocs in ALE inbound and outbound processing, and to process IDocs manually.

Features

Go to the status monitor selection screen with Start of the navigation path Tools Next navigation step IDoc Interface/ALE Next navigation step Administration Next navigation step Monitoring Next navigation step IDoc Display Next navigation step Status Monitor (BD87) End of the navigation path.

Use the selection options to restrict and display the IDoc selection.

The IDocs are arranged by status in the hierarchy. You can rearrange them by message type, object type, or by partner system. You can display a selection of IDocs, process IDocs directly, or first restrict their number and then process them.

From the hierarchy display you can select an IDoc in the list and from here branch to the IDoc individual display.

Restricting IDoc Selection

In the selection screen, you can use the following options to display the status of IDocs:

  • IDoc number

  • Date created *

  • Time created

  • Date changed *

  • Time changed

  • IDoc status

  • Partner system

  • Message type

  • Business object type and object key (selection takes longer than with message type)

    * The arrow keys are used to scroll week by week.

Note

Effects of selection on performance:

  • The following selection is best for performance:

    - Change date

    - Status

    - Message type

    Selection of business object types has a negative effect on performance.

  • Note that it can take a long time to display IDoc entries in tRFC queue. You should therefore only expand this node if you really need to.

  • Expanding the subtree to the level of the error can also be very time-consuming.

Based on your selection, IDocs in inbound and outbound processing are displayed in a hierarchy grouped by their status.

  • Status

    (Text with or without status numbers, number of IDocs)

  • Message type

    (Object method: with Start of the navigation path Settings Next navigation step Business Object End of the navigation path Display)

  • Message text

In the tree display, you can right click to call up context-specific menus.

To display a legend of the symbols used in the hierarchy, choose Start of the navigation path Goto Next navigation step Display legend End of the navigation path.

You can also restrict the number of IDocs to display from the hierarchy screen by choosing Select IDocs.

Changing the Hierarchy Display

Using the Settings menu, and partly by using the symbols, you can change the hierarchy as follows:

  • Message type/object type highlighted

  • IDoc status highlighted

  • Display partner systems (highlighted message type or IDoc status)

    This setting has a negative effect on the performance of the activities.

You can assign status information in groups and hide/show status numbers (using the Settings menu).

Displaying the IDoc List

You can choose Display IDocs to display a list of the associated IDocs for each main entry or sub-entry that contains the following information:

  • IDoc number

  • Status

  • Message type

  • Object type (only for business objects)

  • Object type (only for business objects)

  • Status text

  • Partner number of receiving system

  • Date created

  • Time created

  • IDoc basic type

  • Number of segments

Displaying individual IDocs

You can display the IDocs belonging to the IDoc numbers individually. Select an IDoc and choose Display IDocs or double click on the IDoc. The IDoc display contains the control record, data records and status records.

Displaying links to objects

To display links select an IDoc number and choose Display links.

A list of objects linked directly to the IDoc appears.

Displaying Status Long Text

In the IDoc selection you can display the associated status long text of an IDoc number by selecting the button of the same name.

Display object keys

For each IDoc number in the IDoc selection you can also display the columns Object type and Object key by choosing the button Object key.

Determining Status in Receiving System

You can determine the status of the IDocs in the receiving system (inbound processing) using ALE Audit and IDoc Tracing:

  • Asynchronous Status Confirmation

    Provided that you Monitor the Status of Inbound IDocs Using ALE Audit and confirmations are returned from the receiving system periodically, confirmations are displayed in the status monitor hierarchy. Such IDocs have status 39, 40 or 41. The confirmations contains status information from the receiving system. In the appropriate IDoc selection for each IDoc you can find the partner number and the status of the assigned IDoc in the receiving system (50, 51...).

    Alternatively, you can display an aggregated overview of all periodic confirmations. To do this you have to Evaluate the Audit Database in the sending system (outbound processing). Choose Start of the navigation path Goto Next navigation step ALE Audit Next navigation step Evaluate Audit Statistics End of the navigation path.

  • Synchronous status determination

    For inbound IDocs (in the receiving system) and for outbound IDocs with status 3 and 12 you can synchronously call up the status of the IDoc in the partner system. Choose Trace IDocs in the status monitor hierarchy. For more information see System-Wide IDoc Tracing.

You can print the hierarchy of the status monitor ( Start of the navigation path IDoc selection Next navigation step Print End of the navigation path).

Processing IDocs

If incomplete IDocs or IDocs with errors exist, you can determine the cause and correct the problem using the status long text (click right mouse button or choose IDoc selection).

You can then process the IDocs, or first restrict the number of IDocs and then process them.

A list of processed IDocs with their previous and current status appears.

Note
  • In inbound processing, you can subsequently post non-posted IDocs (status 51) (for more information, see Error Handling.

  • You can not process communication errors.