Neptune Integration Hub for SAP S/4HANA Cloud Public Edition 1.0.0 release notes
October 16, 2026
This is the first release of Neptune Integration Hub for SAP S/4HANA Cloud Public Edition. Neptune Integration Hub for SAP is now available as an ABAP Cloud add-on certified by SAP for SAP S/4HANA Cloud Public Edition. It lets developers expose ABAP logic as REST APIs that are designed in Neptune DXP - Open Edition and executed in the SAP tenant.
The add-on is the fourth flavor of Neptune Integration Hub for SAP, next to the Standard, Cloud, and Combined flavors for on-premise and private cloud systems. It is versioned separately from the Neptune Integration Hub for SAP framework Changes to the Hub API Designer in Neptune DXP - Open Edition are listed in the Neptune DXP - Open Edition release notes.
| The add-on is licensed through Neptune DXP - Open Edition. To use it, you need a license for Neptune DXP - Open Edition that covers Neptune Integration Hub for SAP, and Neptune DXP - Open Edition 24.15 or higher. Neptune Software grants access to the delivery repository during onboarding. |
Key capabilities
-
Define APIs in the Hub API Designer of Neptune DXP - Open Edition and test them in the integrated Swagger UI. The API definitions are stored and executed in the SAP S/4HANA Cloud Public Edition tenant.
-
Implement API logic in your own data provider classes in ABAP for Cloud Development, released under contract C1 for use in cloud development.
-
Serve all APIs through one inbound HTTP endpoint. No configuration is needed per API.
-
Expose the endpoint with the delivered communication scenario
/NEPTUNE/DXP_CS_INBNDand its inbound service/NEPTUNE/DXP_HTTP. You do not create your own communication scenario. -
Authenticate inbound calls with basic authentication, OAuth 2.0, or client certificates. Principal propagation is recommended for production, so that each call carries the identity of the calling user.
-
Give administrators access in the tenant with the delivered business role template
/NEPTUNE/DXP_BRT_ADMIN.
Delivery and lifecycle
-
The add-on is delivered with SAP’s multi-off delivery approach. You install, update, and uninstall it with gCTS from the private GitHub repository
neptune-software/dxp-sap-integration-hub-public-s4. abapGit is not supported. -
The
mainbranch carries the released versions. Releases follow semantic versioning, and the latest released version is actively maintained. -
Every pull is started by you, at a time of your choosing. Neptune Software never pushes changes into a customer tenant.
-
The add-on is delivered as software component
ZPARTNERin the namespaces/NEP/and/NEPTUNE/. It has a footprint of approximately 15 MB and does not extend any SAP tables. -
All traffic flows from Neptune DXP - Open Edition into the tenant. The add-on makes no outbound connections.
Known limitations
-
The Hub MCP Designer is not available for SAP S/4HANA Cloud Public Edition.
-
Logging is optional and switched off after installation. There is no automatic deletion of log data yet. If you enable logging, delete log data according to your own retention policy.
Getting started
-
Read Integration Hub for SAP S/4HANA Cloud Public Edition for how this flavor differs from the transport-based flavors.
-
Install and configure the add-on in the SAP tenant, as described in Install and configure Neptune Integration Hub for SAP in SAP S/4HANA Cloud Public Edition.
-
Connect Neptune DXP - Open Edition to the tenant, as described in Connect to Neptune Integration Hub for SAP in SAP S/4HANA Cloud Public Edition.