neptunesoftware-dxp-mcp-goods-receipt
Goods Receipt MCP Template
Table of Contents
- Overview
- Prerequisites
- Neptune DXP SAP Integration Hub Prerequisites
- Neptune DXP Open Edition Prerequisites
- Neptune DXP Version Compatibility
- Neptune DXP SAP Integration Hub Version
- Neptune DXP Open Edition Version
- Recommended Naming Conventions & Namespaces
- Manual Steps Guide for Neptune DXP Open Edition + SAP (with SAP Integration HUB installed)
- Step 1. Import the included transport file to your SAP system
- Step 2. Access the Hub MCP Designer in your Neptune DXP Open Edition instance
- Step 3. Configure a remote system connection in Neptune DXP Open Edition
- Step 4. Navigate to the Agent tool in your Neptune DXP Open Edition instance
Overview
This bundle demonstrates a SAP Goods Receipt workflow, providing a simple reference implementation for interacting via an AI Agent with production orders and posting goods receipts to the SAP backend.
If you're interested in using this marketplace template with AI-powered editors and assistants, for example, Claude Code, Claude Desktop, Cursor, and Windsurf, manage your design-time artifacts directly through natural-language instructions...This documentation MCP Server explains how to connect a supported MCP client, how authorization works for end users, which artifacts you can manage through MCP, and how to resolve common connection issues. Instructions are intended for developers, designers, and administrators who use Neptune DXP - Open Edition.
Features
The bundle supports the following use cases:
📋 View Production Orders
- Retrieve and display production orders from SAP.
❓ Answer Questions About Production Orders
- Provide information about production order details, status, materials, and quantities.
✍️ Enter Goods Receipt Quantities
- Guide users through entering the quantities received for a production order.
✅ Post Goods Receipts
- Submit the goods receipt to SAP once the quantities have been confirmed.
Prerequisites
Before implementing this integration scenario, ensure that the following prerequisites are met.
Neptune DXP SAP Integration Hub Prerequisites:
- Neptune DXP SAP Integration Hub - Minimum version 1.1.0
- A valid Neptune Subscription License is active.
- The SAP user must have the required SAP authorizations to access, create & activate custom ABAP artifacts, including data provider classes ('ZCL') and using the transaction 'SE24'.
- The SAP user must be authorized to read and write data in the SAP backend system through Function Modules and BAPIs that are consumed by the custom ABAP logic.
- The SAP user must have the required SAP authorizations to import Transport Order files to their SAP system.
- Neptune DXP – SAP Integration Hub is installed and configured in your SAP system -> You can read more on how to install Neptune DXP - SAP Integration Hub here.
Neptune DXP Open Edition Prerequisites:
- Neptune DXP Open Edition - Minimum version 24.15.0
- A valid Neptune Subscription License is active.
- A connection to your SAP system has been configured using the Remote Systems tool in Neptune DXP Open Edition.
- In Neptune DXP Open Edition, the user must have Role based access to create and maintain artifacts, including 'MCP server connections' via the Hub MCP Designer and agents via the Agents.
- The user must have role based access to create and maintain Proxy Authentication artifacts that need to be added to a remote system connection in Neptune DXP Open Edition.
Neptune DXP Version Compatibility
While the Neptune DXP - SAP Integration Hub and Open Edition cater to different user environments and have unique requirements, leveraging this bundle with an end-to-end solution across both versions in mind, requires understanding their compatibility.
Users can only import the MCP Goods Receipt bundle into DXP version 24.15.0 of Neptune DXP Open Edition
Neptune DXP SAP Integration Hub Version
Recommended Version: Neptune DXP SAP Integration Hub 1.1.0Released: Q2/2026
Neptune DXP Open Edition Version
Recommended Version: Neptune DXP - Open Edition 24.15.0Released: Q2/2026
Recommended Naming Conventions & Namespaces
To ensure a streamlined and consistent import process for the provided source files that implement the exposure of ABAP-based business logic in the SAP backend system, it is recommended to retain the naming conventions and namespaces as defined in the included artifacts of the Transport Order file.
The included transport order file for SAP includes the implementation of an ABAP Data Provider Class, which serves as the central integration component for the MCP Server connection (this MCP Server connection is also included in the SAP package & created via the Hub MCP Designer in Neptune DXP Open Edition).
Manual Steps Guide for Neptune DXP Open Edition + SAP (with SAP Integration HUB installed)
This guide provides a step-by-step walkthrough for manually configuring and unlocking the full capabilities of this Marketplace template with Neptune DXP Open Edition and SAP (with SAP Integration Hub installed).
To complete the setup successfully, follow each step in order. During this process, you will:
- Verify that an MCP remote system connection has been configured.
- Import the included SAP transport request (.zip file).
- Navigate to the Hub MCP Designer to explore the Marketplace template's MCP server connection.
- Open the Agent tool to explore the included AI Agent and its capabilities.
Step 1. Import the included transport file to your SAP system
Begin by dowloading the included transport file transport_K_R_996120.zip located at the root of the repository.In this .zip file, you'll find a "K996120.NAI" and a "R996120.NAI" file to be imported to your SAP system.These will contain the custom ABAP Data Provider Class (TCode SE24) and an MCP server connection (will be visible in the Hub MCP Designer in your Neptune DXP Open Edition instance)
Step 2. Access the Hub MCP Designer in your Neptune DXP Open Edition instance
After successfully importing the included transport order .zip file to your SAP system... Navigate to your Neptune DXP Open Edition cockpit and access the Hub MCP Designer tool.
In this tool, you can create & maintain your own MCP server connections, configuring the tools that you want the AI agent to use - to send & get data from your SAP system.
Ensure that you enable / disable the tools available from this marketplace template to be used via an AI Agent.
Step 3. Configure a remote system connection in Neptune DXP Open Edition
Now that the MCP server connection was configured (in the previous step), the next step is to condfigure a remote system connection in your Neptune DXP Open Edition via the Remote Systems tool.
This bundle comes with a preconfigured Model Context Protocol (MCP) remote connection (You will still need to add a URL and Authentication):
Copy the SAP Path that's included in the Hub MCP Designer from the previous step:
Paste the SAP Path in the Remote System URL:
Ensure that you add authentication to this remote system connection:
You can then verify if the connection is successful after the authentication is added:
Finally, press the "Import Tools" button & Save:
NOTE: Ensure that this newly configured remote system connection is targeting the SAP system that has SAP Integration Hub installed and it's the same system where you'll import the included transport file. (details provided in Step. 1)
Step 4. Navigate to the Agent tool in your Neptune DXP Open Edition instance
With the MCP server in place, the next step is to validate the included AI agent that will leverage the SAP business logic exposed through your MCP tools.
NOTE: Ensure to assign a Model to this AI Agent, you will need to manully configure this step in order to fully leverage the AI Agent capabilities
To create your own Reference AI Model, you read more in our public documentation about Models
Within the agent configuration, you can define instructions that guide how the agent should interact with users and when it should invoke MCP tools. These instructions help the agent determine which information needs to be collected from the user, how to pass that information to SAP, and how to present the results returned from SAP.
The final step of the Ai Agent configuration, is to configure the Remote MCP Connections. The included agent will have the Remote MCP Connection already applied, you'll need to press the Test Connection button to validate the configuration from Step 3:
Once the connection is validated, press the Tool Selection button:
For this example, select all the tools:
Now you can test the Agent via the Playground tab:
