Show TOC

Background documentationRequest Confirmation Locate this document in the navigation structure


Use the following interface pattern for bi-directional, asynchronous A2A interactions:

This graphic is explained in the accompanying text.

A typical use case for this interface pattern is the request and update of an order.

You model the service interfaces <Interaction> Out and <Interaction> In of the A process component (analog: process component B) separately, because for technical reasons later you will also need to create two specific service interfaces in the ES Repository (one outbound and one inbound service interface). Aside from distinguishing from Out and In , you use the same names because they belong to the same interaction, from a semantic point of view.

Further comments:

  • Request <X>

    This operation starts the message exchange. In most cases you can derive the message type name as a substantiation from this operation. This is not mandatory.

  • Maintain <BO_2>

    Instead of modeling an operation to create and an operation to edit data, SAP works mostly with this operation. If, however, it is only possible to create data but not to edit it, the name of the operation can also be Create <BO_2>. The main thins is that the name represents the type of data access and not the receipt of the message, as this would be less meaningful.

  • Request <X> Cancellation

    Normally a separate operation is modeled to request a cancellation because the semantics of the other operations are often very different and because the message structure needed to a cancellation is normally small.

  • Cancel <BO_2>

    This is actually the cancellation operation for <BO_2>.

  • Confirm <X>

    Operation to confirm one of the previous requests (create, edit and cancel). A Confirm operation is normally enough for different request types.

  • Change <BO_1> based on <X> Confirmation

    This operation facilitates changes to <BO_1> that are triggered by the received <X> Confirmation message. The name of the operation must show this. <BO_1> based on <X> Confirmation is a suggestion.