Selecting Processed XML Messages  

Use

You can select particular processed XML messages from all existing processed XML messages. The XML messages you select are then compiled in a list for evaluation purposes. 

To condense the list of messages to be selected, use particular selection criteria, only select messages with errors, or only select messages for which the delay was relatively large between when the message was sent, and when it was executed.

Prerequisites

In the Monitoring menu you chose the entry Monitor for Processed XML Messages and the system now displays the screen with the same name.

Procedure

Depending on which archived XML messages you want to select, proceed as follows:

·        To select messages according to criteria that apply to all messages, choose All Messages (default).

Define your selection criteria and choose Execute. All messages that match the selection criteria are listed. If the system does not find any messages, it displays a corresponding message.

·        To select messages according to criteria that only apply to messages with errors, choose Only Messages with Errors.

Define your selection criteria and choose Execute. All messages with errors that match the selection criteria are listed. If the system does not find any messages with errors, it displays a corresponding message.

·        To select messages according to criteria that only apply to messages with critical time delays during processing, choose Delayed Messages.

Define your selection criteria and choose Execute. All messages with critical time delays that match the selection criteria are listed. If the system does not find any messages, it displays a corresponding message.

For more information about time delays, choose F1.

In each of the three cases you also have the option of selecting acknowledgment messages as well. In addition, for all three options you can choose from different standard selection criteria and enhanced selection criteria. These can also be combined in any way you require.

Result

The system displays a list with the selected persisted XML messages. The list contains the following standard information about the messages displayed:

To switch between different views, choose Layout Settings (). You can define your preferred view as the default setting and you also have the option of defining your own view.

·        XML message status

Each XML message has a status.

¡        If the system does not find any versions for the XML message you selected, it displays the overall processing status. This is the status after the last executed processing step.

¡        If the system has already found the versions, it displays the status of the respective processing step.

Choose Legend () to display a list of the different message statuses. For more information see the Processing Status section.

·        Status of the acknowledgment message

The status of the acknowledgment message is displayed for asynchronous messages here.

Choose Legend () to display a list of the different acknowledgment statuses. For more information see the Processing Status section.

·        Date executed

Message processing is usually started and completed on the same day. For this reason, only the start date is shown in the list (Executed On). If the end date is different to the start date, End Time (see below) is set to ??:??:??. This situation could arise if an XML message with errors is rescheduled for the following day, after its errors have been corrected, for example.

·        Execution Time

If the system has already found the versions for the selected XML message, the display changes. Start Time is only displayed for inbound processing. For all other versions the end date is displayed as the date (Executed On). The Start Time is initialized and End Time is outputted.

To display the complete history of the message, click the time on the end date (Until) or ??:??:??.

·        Sender

The sender business system.

·        Namespace of the sender interface

The namespace of the outbound interface with which the message from the sender was received.

·        Name of the sender interface

The name of the outbound interface with which the message from the sender was received.

·        Receiver

The receiver business system (if one exists).

·        Namespace of the receiver interface

The namespace of the inbound interface with which the message was sent to the receiver (if one exists).

·        Name of the receiver interface

The name of the inbound interface with which the message was sent to the receiver (if one exists).

·        Message ID

·        The executed Pipeline

·        Displayed version

If the system does not find any versions for the selected XML message, it displays the most recent version of the XML message with the text Current Status. If the system has already found the versions, it displays the corresponding processing step.

·        Message Type (Synchronous or Asynchronous)

·        Delivery type of a message (Quality of Service)

·        Technical inbound channel of the message

The technical inbound channel refers to the origin of a message. The following are possible entries:

¡        IENGINE

The message originates from the Integration Engine.

¡        IDOC

The message originates from the IDoc adapter.

¡        RFC

The message originates from the RFC adapter.

¡        PLAINHTTP

The message was sent without control information and originates from a plain HTTP adapter.

¡        PROXY

The message originates from the proxy runtime.

¡        AENGINE

The message was sent in internal SAP-message format and originates from an Adapter Engine.

¡        PE

The message originates from the Process Engine.

In the PE inbound channel you can go directly to the corresponding workflow display.

In the IDOC and RFC inbound channels you can switch directly to the screen for displaying XML messages in the IDoc/RFC adapter.

·        Technical outbound channel of the message

The technical outbound channel refers to the where the message is sent. The following types are possible:

¡        IENGINE

The message is going to the Integration Engine.

¡        IDOC

The message is going to the IDoc adapter.

¡        RFC

The message is going to the RFC adapter.

¡        PLAINHTTP

The message is sent without control information and is going to a plain HTTP adapter.

¡        PROXY

The message is going to the proxy runtime.

¡        AENGINE

The message is sent in internal SAP-message format and is going to an Adapter Engine.

¡        PE

The message is going to the Process Engine.

In the PE outbound channel you can go directly to the corresponding workflow display.

In the IDOC and RFC inbound channels you can switch directly to the screen for displaying XML messages in the IDoc/RFC adapter.

·        Status of the message in the technical outbound channel

If the message is going to an IDoc or RFC adapter (outbound channel IDOC or RFC), this column displays the status of message processing in the corresponding adapter. The display remains empty for messages with errors.

Choose Legend () to display a list of the different message statuses.

·        Queue name (ID), in which the message is currently located (only in asynchronous processing).

To navigate to the qRFC monitor for the corresponding queue, click a queue ID.

·        Message status in displayed queue

Choose Legend () to display a list of the different message statuses.

·        The reorganization status of the message

The reorganization status of a message specifies whether the message was marked for deletion or whether it has already been archived. If the display is empty, the message status is initial.

Choose Legend () to display a list of the different message statuses.

·        The message ID of the original message if it is an acknowledgment message - the request message of which was subject to message branching following receiver identification (only for acknowledgment messages).

·        The message ID of the request message that lead to the acknowledgment message (only for acknowledgment messages).

·        The message ID of the original message when the message is the result of message branching following receiver identification.

The system lists XML messages in chronological order. You can display each of the listed XML messages in the following ways:

·        Click on the corresponding message ID

·        Double-click on the contents of another column provided that the contents has no link

You also have the following options:

·        To compare and display the different versions of an XML message, select the line with the corresponding message ID and choose Display ().

·        To display the error long text for an XML message with errors, select the line with the message in question and choose Error Information (), or choose the symbol  in the status column. The error long text contains possible error causes as well as information for troubleshooting.

This option is only relevant for XML messages with errors ().

·        To update the display, choose Refresh ().

The system determines the current status of the persistency layer and any new XML messages written to the persistency layer are sorted according to the time they were sent.

The versions are updated for XML messages with version display.

·        To check and update the status of messages in an outbound adapter or in a queue, choose Refresh Status ().

You can check and update the status of messages of this type until they have been processed.

·        To reschedule a message with errors having corrected the error, select the corresponding line and choose Restart (). The system displays a confirmation prompt.

This option is only relevant for asynchronous XML messages with errors ().

·        To confirm a message with errors and to mark it for deletion, select the corresponding line and choose Confirm Error (). The system displays a confirmation prompt.

This option is only relevant for XML messages with errors ().

·        To display the versions of a particular XML message, select the corresponding line and choose Expand ().

The versions available including version number and action executed are expanded beneath the selected line.  If no versions exist, the system displays a corresponding message.

To display any of the XML messages listed, click the corresponding message ID.

Versions of an XML message only exist if message processing, including logging was executed.

·        To find versions for all XML messages in the list, choose Expand All Messages ().

The system displays existing persisted messages and sorts them according to their message ID and version.

·        To hide the versions again, choose Hide Versions ().

·        To display the history of a particular message, select the corresponding line and choose Message History ().

The system displays information on the life cycle of the XML message in a separate dialog box.