Skip to content
Art2link ESB v2.02 LTS HomeDocumentationBlogContact
Core concepts/Adapters/SAP adapter
Adapter

SAP adapter Enterprise

Bidirectional integration with SAP ECC and SAP S/4HANA. Consumes IDocs pushed from SAP on the Listener side and posts IDocs or invokes BAPI/RFC remote calls on the Caller side.

Enterprise edition only. SAP integration is part of the Enterprise adapter set and is not available in Starter. See the Edition comparison for what each edition includes.
DIRECTION ↓ ↑ Receive & Send MODES One-way · Two-way AUTHENTICATION SAP Authentication EDITION Enterprise

The Art2link ESB SAP adapter speaks the two interfaces SAP has stabilised over decades of integration work: IDocs for asynchronous business document exchange, and BAPI/RFC for synchronous remote calls into ABAP. Both directions are covered by a single adapter, paired with an SAP Authentication carrying the system ID, gateway, client number, and user credentials.

Bound to a receive port, the adapter registers with the SAP gateway as a tRFC destination and waits for IDocs pushed from SAP. Each IDoc is published to the bus as a structured message, ready to be mapped onto the partner format the downstream send port expects.

Bound to a send port, the adapter either posts an IDoc into SAP or invokes a BAPI/RFC function. Two-way mode returns the BAPI response (or the IDoc status) back to the bus so the integration thread can act on it.

The SAP adapter pairs with a dedicated SAP Authentication object. The Authentication carries the connection target and credentials in a form specific to SAP; one Authentication object is reused across Listener and Caller bindings into the same SAP system.

Configuration field set and worked example will be published alongside the Enterprise edition launch listing.

That is the SAP adapter

Bidirectional SAP integration through the standard interfaces, paired with a SAP Authentication object. Enterprise edition only. Back to Adapters.