Show TOC

Procedure documentationMonitoring Message Flows and Handling Errors

 

As an application supporter, identify the root cause of an error, for example on request of a business power user.

Prerequisites

  • The administrator has set up message flow groups and assigned the relevant message flows.

  • You have started the Message Flow Monitor. For more information, see Starting the Message Flow Monitor.

  • You have authorization for the PI system (middleware componet) in which to correct errors.

Procedure

On the Overview tab page, you can view statistics about the execution of message flows in the various message flow groups. You have the following options:

  1. To drill down to message flows with status System Error, do the following:

    1. On the Message Flow tab page, search for message flow with status Error.

    2. Select a message flow from the search results.

  2. To identify the PI system in which the transmission error occurred, choose the Flow Track tab page. You can choose to view the details either in tabular or graphical format.

  3. If an error occurred in a message split PI scenario (a message is split into several fragmented messages, for example) the Undetermined Flow type is displayed. “Undetermined” means that the system cannot decide for which receiver the failed message flow was to be sent. Using the Flow Candidates and Flow Group Candidates columns you can navigate to the possible message flows and message flow groups to which a message flow can belong. To identify the flow to which the failed message flow belongs, check the payload attributes on the General tab page.

  4. To resolve the issue, do the following:

    1. To resend a failed message, on the Flow Track tab page, select the system in which the error occurred, and choose Resend Message. Resending a message can take several minutes.

    2. If the error persists, choose Navigate to Alert Inbox to check the details of the issues that caused the alerts.

    3. If the error persists, to cancel the message (and later ask the business supporter to restart the business transaction), choose Cancel Message

    4. If the error persists, to call the PI system and perform a standard transaction on the system, on the Flow Track tab page, click Navigateand choose PI Communication Channel Monitor, PI Message Monitoring, or PI IDOC Monitor. To resolve, for example, a mapping error, correct the relevant payload attribute value.

  5. If the error persists, notify someone who can resolve the issue. You can send notifications either by e-mail or SMS. To do so, choose Create Notification.

  6. If the issue cannot be resolved, create an SAP support message. To do so, choose Create Incident.

Analyzing the Message Flow Reports

To analyze the message flow, do the following:

You have the following options to check the message flow statistics:

  1. On the Overview tab page, choose Personalization.

  2. Choose the Add New Tab and rename it Reporting

  3. Drag and drop Metric Viewer from the View Management section to the new tab. By default, no query will be selected. You can use the Filter option to select a query.

  4. Choose the Check Query.

    You have the following options to check the message flow statistics:

    • Number of flows per flow type

    • Number of flows per receiver participant

    • Number of flows per sender participant

    • Average processing per flow type

    • Number of flows with technical acknowledgements

    • Number of flows with functional acknowledgements

  5. Based on your requirement, select the query and choose OK.