Show TOC

Procedure documentationMonitoring Message Flows and Handling Errors Locate this document in the navigation structure

 

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

Prerequisites

  • The administrator has set up message flow groups and assigned the corresponding 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 in which to correct errors.

Procedure

In the Flow Overview, display statistics about the execution of message flows in the various message flow groups. You have the following options:

  1. To drill down to failed message flow instances, do the following:

    1. Under Flow Status Overview, in the Error column, select the message flow.

      The failed message flow instances are displayed.

    2. Select a message flow instance.

  2. To identify the PI system (middleware component) in which the transmission error occurred, choose the Flow Track tab page.

  3. If an error occurred in a message split PI scenario (a message is split into several fragmented messages, for example) the Pending Instances tab page is displayed. “Pending” means that the system cannot decide for which receiver the failed message instance was to be sent. Via 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 instance can belong. To identify the message flow to which the failed message flow instance 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, to cancel the message (and later ask the business supporter to restart the business transaction), choose the Cancel link.

    3. If the error persists, check whether there is a guided procedure to resolve the issue. To do so, under the Activity (Activity) icon, choose Guided Procedure.

    4. If the error persists, to call the PI system and perform a standard transaction on the system, on the Flow Track tab page, choose the Participant Name link. To resolve, for example, a mapping error, correct the relevant payload attribute value.

  5. If the issue cannot be resolved, create an SAP support message. To do so, under the Activity (Activity) icon, choose Create Incident.

  6. Inform the business supporter that the issue was resolved.

Creating Custom Guided Procedure to Handle Recurring Errors

To handle errors which occur frequently, you can create a custom guided procedure (to do so under the Activity (Activity) icon, choose Guided Procedure). This allows less experienced users, business supporters for example, to resolve an issue.

For more information about creating custom guided procedures, see Guided Procedure Authoring (GPA).