For Event Driven Architecture (EDA), SAP recommends the following products:
• SAP Event Broker for SAP cloud applications
• SAP Event Mesh (Event Mesh capability of SAP Integration Suite)
• SAP Integration Suite, Advanced Event Mesh
If you would just like to try out event-driven architecture in a small scope, you can use direct push-based integration.
Introduction
With direct push-based integration, you can connect neighboring ABAP Systems (for example SAP S/4HANA Public/Private Cloud, SAP S/4HANA On-Premise or SAP BTP ABAP environment tenants) with each other. In this scenario, the connected systems exchange data (like business events) by calling each other directly via RFC.
The advantages of this functionality are simpler setup and faster connectivity. This integration can also be used to try out event-driven architecture in a small scope.
Availability
• SAP S/4HANA Cloud Public Edition 2408
• SAP S/4HANA Cloud Private Edition and SAP S/4HANA 2023 SP 02
• SAP S/4HANA Cloud Private Edition and SAP S4/HANA 2022 SP 04
• SAP BTP ABAP environment Release 2408
Architecture
Direct push-based integration connects two ABAP systems/clients with each other. One of the systems acts as a sender of information, the other system acts as the receiver.
For the communication between the systems, the RFC protocol is used either over CPI-C or over WebSockets, depending what release the systems are running on.
The information can be exchanged between the connected systems in real time, when certain changes like business events occur in the sender system, the receiver is therefore informed immediately. This can replace API-based polling for changes in certain scenarios.
A connection from sender to receiver is represented by a sender channel in the sending system and a receiver channel in the receiving system. The channel holds the configuration of the connection and the allowlist of the information to be pushed.
It is possible to connect multiple sender channels with one receiver channel (n:1).
To connect one sending system with multiple receiving systems, a sender channel is required for each receiving system (1:n).
In the receiver channel you can configure which information you are interested in by maintaining the consumers for the channel.
The sending system must fetch the consumer configuration from the receiver channel to determine which information should be pushed to a receiving system.
If the producers of the required information are available in the sending system, the sender only sends information the receiver is interested in.
Recommendations
Direct push-based integration is recommended for integrations between ABAP systems in the following situations:
- The systems to be connected are in the same location or in the same subaccount
- Public exposure of the systems is not wanted
- Systems should react to the changes in other systems and
- If direct API-based communication is not wanted or
- If a polling mechanism is not wanted
- If IDocs cannot be used
- For prototyping of event-driven use-cases in general, before introducing event-driven patterns on a larger scale.
Note:
Direct push-based integration can only be used between ABAP systems. An ABAP system in this context can be a tenant of SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, SAP S/4HANA, or SAP BTP, ABAP environment.
Further Information:
Direct Push-Based Integration | SAP Help Portal
