SAP Integration Hub for SAP S/4HANA Cloud Public Edition
SAP Integration Hub is available for SAP S/4HANA Cloud Public Edition as an ABAP Cloud add-on certified by SAP. It is the fourth flavor of SAP Integration Hub, next to the Standard, Cloud, and Combined flavors that are installed with an SAP transport.
You define APIs in the Hub API Designer in Neptune DXP - Open Edition. The add-on stores and executes them in your SAP S/4HANA Cloud Public Edition tenant and serves all of them through a single inbound HTTP endpoint.
Differences from the transport-based flavors
API design, data provider classes, and testing in the Swagger UI work the same way as in the other flavors. The differences are in delivery, setup, and scope.
| Aspect | Standard, Cloud, and Combined flavors | SAP S/4HANA Cloud Public Edition |
|---|---|---|
Installation and updates |
SAP transport imported with transaction |
Pulled with the Git-enabled Change and Transport System (gCTS) from a private GitHub repository, using SAP’s multi-off delivery approach. abapGit is not supported. |
Design time |
Neptune DXP - SAP Edition or Neptune DXP - Open Edition |
Neptune DXP - Open Edition only. There is no SAP Integration Hub user interface in the SAP tenant. |
Hub MCP Designer |
Available with Neptune DXP - Open Edition |
Not available, because SAP’s API policy for SAP S/4HANA Cloud Public Edition does not permit it |
Inbound connectivity |
ICF node |
Communication arrangement on the delivered communication scenario
|
Authorizations |
PFCG roles |
Business role template |
Data provider classes |
ABAP for Cloud Development recommended where the system supports it |
ABAP for Cloud Development required, and the class must be released under contract C1 for use in cloud development |
Release notes |
SAP Integration Hub for SAP S/4HANA Cloud Public Edition release notes |
Delivery
The add-on is available after you have a license extension for Neptune DXP - Open Edition that covers SAP Integration Hub. During onboarding, Neptune Software issues read access to the delivery repository and agrees with you which version to pull.
| Item | Value |
|---|---|
Software component |
|
Namespaces |
|
Delivery repository |
|
Branch |
|
Versioning |
Semantic versioning. The latest released version is actively maintained. |
Footprint |
Approximately 15 MB of objects. No SAP tables are extended. For details, see Sizing SAP Integration Hub in SAP S/4HANA Cloud Public Edition. |
Repository access |
One GitHub fine-grained personal access token per customer, with read-only Contents and Metadata permissions and an explicit expiry date |
You do not modify the delivered objects. Your own data provider classes are created in your customer namespace.
There is no technical means to disable delivered functionality after it has been pulled. The terms under which you can use the add-on are governed by your contract with Neptune Software.
How the components interact
- Installation and updates
-
gCTS in your tenant pulls the add-on from the
mainbranch over HTTPS with your read-only token. Every pull is started by you. Neptune Software never pushes changes into a customer tenant. - Design time
-
The Hub API Designer in Neptune DXP - Open Edition calls the inbound endpoint through a remote system. It lists your released data provider classes and saves API definitions, which are stored as configuration data in the tenant.
- Runtime
-
A consumer calls a REST API in Neptune DXP - Open Edition, which forwards the call over HTTPS to the inbound service
/NEPTUNE/DXP_HTTP. The add-on calls your data provider class, which reads SAP data through released APIs and returns JSON or binary content. If logging is enabled, each call can be logged in the tenant.
All traffic flows from Neptune DXP - Open Edition into the SAP tenant. The add-on makes no outbound connections. It maintains no outbound destinations, no connections to other SAP systems, and no third-party endpoints.
Updates
Releases are published when functionality or fixes are ready, not on a fixed calendar. You decide when to pull a newer version into your tenant, as described in Update the add-on.
If a fix cannot wait for the next planned release, Neptune Software can supply a hotfix against the current released version. The support ticket tells you which commit to pull with gCTS.
Support
Raise incidents, questions, and change requests for the add-on in the Neptune Software support portal. Service levels and ticket categories are defined in the Neptune support plans.
Include the following in a ticket about the add-on:
-
The version you pulled
-
The gCTS log, if the issue relates to an installation, update, or uninstallation
-
The API and operation affected