Modeling A2A Interactions

Using A2A interactions you model the message exchange between two process components with the help of asynchronous and synchronous operations. SAP models accesses like these using interface patterns.

Procedure

Decide which interface pattern best suits your use case. Choose from the following interface patterns:
- Asynchronous Interface Patterns:
  - Request Confirmation: Interface pattern for updating data (typical use case: purchase orders).
  - Notification: Interface pattern for target-oriented messages which are expected.
  - Information: Interface pattern for broadcasting events to multiple receivers.
- Synchronous Interface Patterns:
  - Query Business Object in A2A Communication: Interface pattern for reading data using selection criteria.
  - Read Business Object in A2A Communication: Interface pattern for reading data using an ID.
Use the interface pattern to set the names of the operations and service interfaces. Use spaces between the parts of the name to make the names more legible in the modeling.
Example
The standardized name of a service interface of the interface pattern request confirmation is Request <X> Cancellation. The space disappears if you later create the specified service interface for this modeled service interface. The specified service interface in the ES Repository would also be called Request<X>Cancellation.
End of the example.