System requirements
The AI Context Hub connects Neptune DXP - Open Edition to an SAP system through Neptune DXP - SAP Edition. The following must be in place, in the order shown, before configuring a data source or ingesting a system.
Neptune DXP - Open Edition
-
Neptune DXP - Open Edition version 25.0 or later installed:
The AI Context Hub is included in Neptune DXP - Open Edition from version 25.0. No separate license or license extension is required. Once a version that includes the AI Context Hub is installed, the SAP Data Sources tool is available in Naia Agent Studio in the Cockpit.
-
SAP system connected as a remote system:
The SAP system is connected as a remote system in the Remote Systems tool (Security tool group). When the system is opened there, it shows an AI Context Hub tab, through which the orchestration engine connects and ingests.
-
Database with vector support:
The AI Context Hub stores its catalog embeddings in vector columns, so the Neptune DXP - Open Edition database must support vectors:
- PostgreSQL
-
The pgvector extension is installed and enabled. How you install it depends on how you run PostgreSQL. For example, the pgvector Docker image already includes the extension. See Database configuration.
- Microsoft SQL Server
-
The database runs on SQL Server 2025 or later, which provides the native
VECTORdata type. Earlier versions have no vector support. - SQLite
-
SQLite has no vector support, so the AI Context Hub is unavailable.
Enable vector support before you install or upgrade to a Neptune DXP - Open Edition version that includes the AI Context Hub, version 25.0 or later. The first start of that version creates the AI Context Hub embedding columns. If the database cannot store vectors at that point, the columns are created as text and must be re-created later. See Enabling vector support for the AI Context Hub.
-
Network access to the SAP system opened:
The Neptune DXP - Open Edition host reaches the SAP system’s HTTP endpoints, so a component ingests rather than failing on connection. For the paths a network or firewall configuration must allow, see SAP connectivity and authorizations.
Connected SAP system
-
Neptune DXP - SAP Edition version 21 or higher installed:
This is the platform the orchestration engine connects to and ingests, and it provides the API Designer and API Factory that the later requirements build on.
-
AI Context Hub API transport imported:
This transport adds the bridge API the orchestration engine uses to ingest the artifact types and the application component hierarchy and to read business-object metadata, so the system cannot be ingested until it is imported. After import, the bridge API is present in the API Designer.
The transport is available from the Neptune DXP Portal, under Neptune DXP - SAP Edition → Xtra Add-Ons → Neptune DXP - AI Context Hub.
-
API Factory access granted:
The API Factory is deny-by-default, so policies, or entity sets where an API uses entity references, must give the ingestion and runtime identities access to the artifacts they need. When access is complete, a component ingests without a policy error. For what to grant, and how ingestion and runtime access differ, see SAP connectivity and authorizations and the SAP Edition API Factory Policy documentation.
The following API Factory endpoints are non-executable by default until a policy, or Unrestricted API Engine, is enabled:
Path prefix Used for Phase /neptune/api/dynamic//neptune/cl_dr_lib_src_func_x/…Business objects, function modules, and BAPIs
Ingestion and runtime
/neptune/api/dynamic//neptune/cl_dr_lib_src/…Function-module and function-group search. Also needs the
ffandfentity sets.Ingestion
/neptune/api/dynamic//neptune/cl_dr_lib_ddic_dtel_x/…Data elements
Ingestion and runtime
/neptune/api/dynamic//neptune/cl_dr_lib_ddic_shlp_x/…Search helps
Ingestion and runtime
Grant execute to the runtime identity as well as the ingestion identity. Otherwise ingestion succeeds but every call at runtime fails. The Context Hub, OData, and Neptune Integration Hub for SAP endpoints are not governed by this default. For every method and path, see Endpoint reference.
-
Integration Hub for SAP transport imported (optional):
This transport is needed only for data sources that use Integration Hub for SAP APIs. When it is installed and its ICF path active, its APIs appear during ingestion; when it is absent, ingestion skips them and continues with the other sources.