Show TOC

Procedure documentationChecking the Status of a Business Transaction

 

As a business supporter, you can verify that a business transaction (technically, a message flow instance) has been successful. For example, if you send a purchase order to a business partner, you can check whether your business partner has received it.

Depending on the configuration of the PI landscape, you can check whether

  • the purchase order has left your system landscape

  • you have received a technical acknowledgement which is automatically generated by the B2B adapter on the business partner system. The acknowledgement confirms that the purchase order was received.

  • you have received an order confirmation. Technically, this is a separate message flow related to the purchase order message flow. It is a so called “related instance”.

Prerequisites

Procedure

Drill down to the message flow for the business transaction.

  1. Open the Message Flow Monitoring application on the launch pad.

  2. Select a flow group from the Scope Selection. You can see the selected flow groups on the Application Overview section. By default, the data displayed in the flow group applies only to the message flows of today and the day before. By choosing the Time Range icon, you can change the time range.

  3. You can expand a flow group to view the flow types.

  4. Click the relevant message flow. It navigates to the Message Flows tab page. You can view the details , for example, Acknowledgement Status, Technical Acknowledgment, Payload, and Instance ID.

  5. Click the message flow. The Message Flow screen appears. The following tabs are available on the screen:

    • General: You view the details of Status, Support, Time, Flow group candidates and Flow Candidates.

    • Business Attributes: You can view the details of Payload and EDI attributes.

    • Flow Track: You can view the details of the flow track either in a graphical or tabular format. The details include the Status, Time, system details, and the Payload for the corresponding systems.

    • Acknowledgement: You can view details such as start date and time of the acknowledgement, Type, Namespace, Presence Type, Status and Status Code.

    Note Note

    Note that the tabs pages are only visible when the relevant information is available for your selection

    End of the note.

    The acknowledgement of the message flow is categorized as follows:

    • Green (the process is successful)

      • ACCEPTED_SENT ("Sent - Accepted or acknowledged")

      • ACCEPTED_NOT_SENT ("Not Sent - Accepted or acknowledged")

      • ACCEPTED_GENERATED ("Generated - Accepted or acknowledged")

      • ACK_NOT_REQUESTED ("Acknowledgement not requested from partner")

      • ACK_NOT_SOLICITED ("Acknowledgement not solicited by partner")

    • Red (the process failed or failed partially)

      • REJECTED_RECV ("Received and validated - Rejected")

      • REJECTED_SENT ("Sent - Rejected")

      • REJECTED_NOT_SENT ("Not Sent - Rejected")

      • REJECTED_GENERATED ("Generated - Rejected")

    • Yellow (the process is intermediary)

      • PARTIALLY_ACCEPTED_RECV ("Received and validated - Partially accepted")

      • PARTIALLY_ACCEPTED_SENT ("Sent - Partially accepted")

      • PARTIALLY_ACCEPTED_NOT_SENT ("Not Sent - Partially accepted")

      • PARTIALLY_ACCEPTED_GENERATED ("Generated - Partially accepted")

      • RECEIPT_PEINDING ("Acknowledgement pending from partner")

      • ACK_SOLICITED ("Acknowledgement solicited by partner")

      • ACK_RECEIVED ("Acknowledgement received from partner")

      Example Example

      The Received from Partner presence type status is Successful: The business partner system confirms that your purchase order has been received.

      The Received from Partner presence type status is Pending: The business partner system has not yet sent an acknowledgement that your purchase order has been received; however, no error has occurred. Check again later.

      For more information about displaying acknowledgement information, see SAP Help Portal at Start of the navigation path http://help.sap.com/nw731Information published on SAP site Next navigation step Application Help Next navigation step Function-Oriented View Next navigation step <Language> Next navigation step Process Integration Next navigation step Advanced Adapter Engine Next navigation step Monitoring the Advanced Adapter Engine Next navigation step Monitoring Messages Next navigation step Reviewing Search Results. End of the navigation path

      End of the example.

    • Related Instances: You can view the details including the status, flow name, start date, start time, duration of the related instance, and the UDS attributes. If configured, the status of the message flow instance related to your initial message flow is displayed. One of the following statuses is displayed, for example:

      • Successful

        Note Note

        The possible status descriptions of successful message flow instances (for example, Successful, Delivered, Application Document Posted) depend on the B2B protocol adapter used for the business transaction. Message Flow Monitoring supports the AS2, X400, and OFTP B2B protocol adapters.

        End of the note.

      • In Process: The message flow instance has not yet passed all PI systems (middleware components). If the In Process status lasts for a longer time period, an error may have occurred.

        Note Note

        Depending on the message flow type, an end-to-end message flow can take between a minute and several hours.

        End of the note.

If the business transaction failed, do the following:

  • If you know the name of the application supporter, choose Create Notification.

  • To create a support message, choose Create Incident.