Selecting Processed Messages 

Use

You select particular messages from the list of available processed messages for evaluation purposes. You can restrict the number of messages for selection by using particular selection criteria.

Prerequisites

You have selected a view (Default or Process) in the monitor for processed XML messages and now want to select messages.

Procedure

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

●      If you want to select your messages by applying particular criteria to all messages, leave the Status Group and Status input fields empty (default setting).

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

●      If you only want to select messages that belong to a particular status group, select a status group.

Define your selection criteria and choose Execute. The system lists all messages that belong to the selected status group and match the specified selection criteria. If the system does not find any messages, it displays a corresponding message.

●      If you only want to select messages that have a particular status, select a status as well as the status group, or leave the Status Group field empty and just select a status.

Define your selection criteria and choose Execute. The system lists all messages that belong to the selected status group or have the selected status, or both, and match the specified selection criteria. If the system does not find any messages, it displays a corresponding message.

In all three options you can choose from various standard selection criteria and advanced selection criteria and combine them in any way you require. The advanced selection criteria give you the option of selecting acknowledgment messages as well.

Result

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

To switch between different views, choose Select Layout... (). You can also create your own view and define the preferred view as the default.

●      Message status

Each message has a status.

If the system has not determined any versions for the 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.

To display the individual status, choose Legend (). For more information, see Processing Status.

●      Status of the acknowledgment message

The system displays the status of the acknowledgment message for asynchronous messages.

To display the individual acknowledgment status, choose Legend (). For more information, see Processing Status.

●      Start of execution

Date (Executed From) and time (Start Time) of the start of message processing.

●      End of execution

Date (Executed Until) and time (End Time) of the end of message processing.

To display the entire history of the message, click the end time.

●      Sender

The sender party from which the message was received.

●      Sender schema

The identification scheme with which the message from the sender was received.

●      Sender agency

The issuing agency with which the message from the sender was received.

●      Sender component

The communication components with which the message from the sender was received.

●      Sender interface namespace

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

●      Sender interface name

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

●      Receiver

The receiver party (if one exists) that the message is sent to.

●      Receiver schema

The identification scheme with which the message is sent to the receiver (if one exists).

●      Receiver agency

The issuing agency with which the message is sent to the receiver (if one exists).

●      Receiver component

The communication component with which the message is sent to the receiver (if one exists).

●      Receiver interface namespace

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

●      Receiver interface name

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

●      Message ID

●      Executed pipeline

●      Message package

Displays whether the message is a message package or not.

●      Displayed version

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

●      Message type (synchronous or asynchronous)

●      Quality of service of the message

●      Technical inbound channel of the message

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

Technical Inbound Channels

Inbound Channel	Description
IENGINE	The message originates from an Integration Engine.
IDOC	The message originates from an IDoc adapter. You can branch from here directly to the display of XML messages in the IDoc 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 a Business Process Engine. You can branch from here directly to the corresponding workflow display .
SA_COMM	There is a coupling between synchronous and asynchronous processing. The message is transferred to a Business Process Engine and you can branch from here directly to the corresponding workflow display.
WS	The message originates from the Web service.

 

●      Technical outbound channel of the message

The technical outbound channel refers to the destination of the message. The following are possible outbound channels:

Technical Outbound Channels

Outbound Channel	Description
IENGINE	The message is going to an Integration Engine.
IDOC	The message is going to an IDoc adapter. You can branch from here directly to the display of XML messages in the IDoc 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 going to the Adapter Engine.
PE	The message is going to a Business Process Engine. You can branch from here directly to the corresponding workflow display.
SA_COMM	There is a coupling between synchronous and asynchronous processing. The message is received from a Business Process Engine and you can branch from here directly to the corresponding workflow display.
WS	The message is going to an Web service.

 

●      Status of the message in the technical outbound channel

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

To display the individual status, choose Legend ().

●      Name (ID) of the queue 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

To display the individual status, choose Legend ().

●      Job ID of the processing job to which the message was assigned for event-driven processing.

●      Job status

Displays whether the job to which the message was assigned for event-driven processing has already been executed or not.

To display the individual job status, choose Legend ().

●      Reorganization status of the message

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

●      Message ID of the original message in the case of an acknowledgment message where the corresponding request message has undergone message branching following receiver determination (only applies to acknowledgment messages).

●      Message ID of the original message that resulted in the acknowledgment message (only for acknowledgment messages).

●      Message ID of the original message when the message is the result of message branching following receiver identification.

To display the individual status, choose Legend ().

●      Error category, if an error occurred in a message.

●      Error ID, if an error occurred in a message.

●      Number of existing versions of a message

●      Security flag indicating whether security measures were taken during message processing

●      Persistence flag of messages that were sent using the Web service protocol.

Clicking the persistence ID takes you to the Version Display of the message.

The following information is only displayed if you have selected the process view.

●      Process party of the message

The sender party from which the message is received in the Business Process Engine, or the receiver party to which the message is sent from the Business Process Engine.

●      Process component

The integration process component from which the message was received in the Business Process Engine, or of the message from the Business Process Engine of the receiver to whom the message was sent.

●      Process ID

An instance of the process that is defined by the process party and the process component. You can go from here straight to the workflow log.

●      Process definition

The ccBPM process definition used by the process instance. You can go from here to the workflow definition in the Process Builder.

Before the Process Builder is started, the version of the workflow and the number of the workflow step that the process addresses are displayed.

●      XML object name

You can go from here straight to the transaction (SWF_XMP1) for displaying the XML object type. Here you can test the object.

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

●      Click the corresponding message ID

●      Double-click the contents of another column provided that the content has no link

You also have the following options:

●      To display and compare the different versions of a message, select the line with the corresponding message ID and choose display ().

●      To display the error text for a 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 text contains possible error causes as well as information for troubleshooting.

This option is only relevant for messages with errors.

●      To select messages that reference a specific message, select the message and choose Referencing Messages ().

The system displays the messages that reference the selected message.

●      To update the display, choose Refresh ().

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

The versions are updated for messages with version display.

●      To check and update the status of messages, choose Refresh Status ().

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

●      To execute a message with errors again once you have corrected the error, select the corresponding line and choose Restart (). The system displays a confirmation prompt.

When you restart, the last productive version of a message is automatically rescheduled. Consequently, it is possible that not all processing steps are performed again.

If the error occurs during XML validation, the system asks whether you want to skip XML validation during the restart.

To restart numerous messages with errors together, use the program RSXMB_RESTART_MESSAGES. To skip XML validation for messages with validation errors, select the relevant checkbox.

Do not use this program in a background job, especially if you want to skip XML validation. This is important in order to avoid any validation errors being overseen.

These options are only relevant for asynchronous messages with errors.

●      To cancel further processing of a message with errors, select the corresponding line and choose . The message can then be either archived or deleted. The system displays a confirmation prompt.

To cancel multiple message of this type simultaneously, use the program RSXMB_CANCEL_MESSAGES to cancel messages with errors.

This option is only relevant for asynchronous messages with errors.

●      To display the versions of a particular 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 message versions listed, click the corresponding message ID.

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

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

The system displays existing persisted messages, sorted by 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 message in a separate dialog box.