Neptune Integration Hub for SAP
| The Neptune Integration Hub for SAP toolset is included and fully functional in the Neptune DXP - Open Edition 25.0 release. To use it, a valid license for Neptune DXP - Open Edition version 25.0 that enables the framework is required. If you do not have a license for Neptune DXP - Open Edition version 25.0 that includes the Neptune Integration Hub for SAP toolset, the Integration Hub for SAP tile group is not available in the Cockpit. |
The SAP Integration Hub provides a unified environment for defining, maintaining, and managing integrations that connect to SAP systems. It extends Neptune DXP - Open Edition’s existing integration capabilities to cover SAP-integrated use cases, where APIs and MCP servers are stored, transported, and executed directly in your SAP back end.
The toolset has achieved SAP Clean Core Level A certification, helping organizations align with SAP-recommended extension and integration practices while supporting upgrade-friendly and maintainable SAP landscapes.
The toolset includes in the following designers:
-
Hub API Designer: for defining and managing APIs backed by ABAP logic in your SAP system.
-
Hub MCP Designer: for exposing ABAP methods as callable MCP tools, enabling AI and agent-based integrations.
Deployment environments
The SAP Integration Hub back end can be installed on SAP systems with or without Neptune DXP - SAP Edition installed and supports the same SAP system versions across on-premise, private cloud, and public cloud deployments. In on-premise and private cloud environments, transports are imported directly and managed locally. In public cloud systems, connectivity and execution are handled through managed runtime services that adhere to SAP’s Clean Core principles. Regardless of the environment, you define and maintain your integrations in the same way from within Neptune DXP - Open Edition.
In SAP S/4HANA Cloud Public Edition, the SAP Integration Hub back end is an ABAP Cloud add-on that you pull with gCTS instead of importing a transport. Neptune DXP - Open Edition is its only design time, and the Hub MCP Designer is not available. To connect Neptune DXP - Open Edition to the add-on, see Connect to Neptune Integration Hub for SAP in SAP S/4HANA Cloud Public Edition. For the installation in the SAP tenant, see SAP Integration Hub for SAP S/4HANA Cloud Public Edition.
Check minimum system requirements
Before installing Neptune DXP - SAP Integration Hub, check the system requirements to confirm you meet the minimum requirements for your system.
Installation flavors
To support a wide variety of SAP back-end system versions and the journey toward SAP’s Clean Core principles, Neptune DXP - SAP Integration Hub can be installed in four flavors depending on your system version and direction of travel. Functionality is consistent across the Standard, Cloud, and Combined flavors. Only the ABAP Language Version and API release state requirements differ between them. The SAP S/4HANA Cloud Public Edition flavor is pulled with gCTS instead of a transport, and the Hub MCP Designer is not available in it.
| Flavor | Minimum system release | Description |
|---|---|---|
Standard |
7.31 (SP30) |
For older SAP systems not yet on a Cloud-compatible release. |
Cloud |
2022 (7.57) |
For systems fully embracing SAP’s Clean Core principles. |
Combined |
2022 (7.57) |
For systems on a Cloud-compatible release that still run non-Cloud-compliant code, supporting a gradual transition toward Clean Core adherence. |
SAP S/4HANA Cloud Public Edition |
SAP S/4HANA Cloud Public Edition |
ABAP Cloud add-on delivered through gCTS. See SAP Integration Hub for SAP S/4HANA Cloud Public Edition. |
System integration and connectivity
All definitions are stored in the connected SAP system and moved between systems through the standard SAP transport mechanism across the development, quality, and production deployment stages.
Remote systems
You connect external SAP systems in the SAP Integration Hub as remote systems that you define with the system type Neptune DXP - SAP Integration Hub in the Remote Systems tool to establish the communication path used by the SAP Integration Hub framework for data exchange. You configure authentication and endpoint details in a system role set as a development environment via the Proxy Authentication tool, upon which you can transport these details forward to other systems.
| To maintain user permissions and traceability, Neptune recommends that you use principal propagation to ensure that each API action reflects the actual user identity during design and runtime. See Enabling principal propagation in Neptune DXP - Open Edition. |