SAP
SAP exposes several different integration surfaces, and the right one depends on your SAP edition and the kind of traffic you're moving. MaestroHub covers them with separate connectors rather than one catch-all.
Available now
SAP IDoc
The native asynchronous document interface — goods movements, deliveries, production orders, orders and invoices as IDoc-XML over HTTP. Targets SAP ECC, S/4HANA on-premise, and S/4HANA private cloud (RISE). No SAP SDK to license and no side-car to run.
SAP Event Mesh
Consumes SAP business events, such as "sales order created" or "goods movement posted", as CloudEvents 1.0 and starts a pipeline run for each one. Connects over durable AMQP 1.0 (the default) or MQTT 3.1.1 with OAuth2 authentication. It only receives events; it does not send them.
SOAP APIs
For SAP services published as SOAP/WSDL web services. Import the WSDL, browse its operations, and call them with templated parameters.
OData APIs
SAP's OData services are HTTP/JSON APIs and can be called with the REST connector today. This is the recommended path for S/4HANA Cloud, public edition, which does not support transactional IDocs.
Choosing a door
| Your system | Recommended connector |
|---|---|
| SAP ECC / S/4HANA on-premise / RISE private cloud, document-style traffic | SAP IDoc |
| S/4HANA Cloud, public edition | REST (OData) or SOAP |
| Any edition, a service published as WSDL | SOAP |
| Any edition, a service published as OData | REST |
| Business events from SAP's cloud event bus | SAP Event Mesh |
A native SAP OData connector with metadata-driven entity browsing is under development and will arrive in an upcoming release. Classic tRFC/BAPI access over SAP's RFC protocol is not currently supported.