Skip to content
PartnerMCPPartnerMCP

§00Integrations / ERP

All integrations

SAP S/4HANA and SAP Business One integration: Built on SAP's published APIs. Deterministic at runtime.

SAP decides which interfaces it supports, and since April 2026 its API Policy also says how AI may use them. PartnerMCP plans and builds the integration with you on SAP's published APIs; what runs in production is reviewed, pre-defined logic — not an agent exploring your system. For SAP Business One, it works through the Service Layer and, from 10.0 FP 2602, its native webhooks.

Build an IntegrationSalesforce ↔ SAP S/4HANA

How PartnerMCP connects

01Primary path

Published OData APIs (S/4HANA)

Released A2X APIs such as API_BUSINESS_PARTNER, API_SALES_ORDER_SRV and the OData V4 SalesOrder service. In Public Edition each one is activated through a communication arrangement — SAP_COM_0109 for sales orders, for example — with x509, OAuth 2.0 or basic authentication. Every write carries a CSRF token, and updates also carry an ETag.

Product
SAP S/4HANA
Vendor
SAP
Category
ERP
Runs
Cloud · On-prem
Connects through
OData (published APIs)
Detects changes with
business events (SAP Event Mesh)
Product
SAP Business One
Vendor
SAP
Category
ERP
Runs
Cloud · On-prem
Connects through
Service Layer (OData)
Detects changes with
Service Layer webhooks (10.0 FP 2602+) · UpdateDate polling
On this page
  1. 01What you can build
  2. 02Objects and events
  3. 03What it handles
  4. 04Pairings
  5. 05Questions
  6. 06References
§01—What you can build

What you can build.

Each one starts as a sentence. PartnerMCP answers with a plan in SAP’s own objects, then builds it against your systems.

01Salesforce ↔ SAP S/4HANA

“Synchronize accounts, quotations, sales orders, invoices and fulfillment between Salesforce and SAP S/4HANA.”

Build this integration

PartnerMCP will

  1. Map Accounts to business partners through API_BUSINESS_PARTNER, keeping the SAP number on the Account.
  2. Simulate the order with API_SALES_ORDER_SIMULATION_SRV to check pricing and availability.
  3. Create A_SalesOrder with to_Item lines in one deep insert, with PurchaseOrderByCustomer set to the Opportunity reference.
  4. Follow the outbound delivery to goods issue, then read the billing document for invoice status.
  5. Write order, delivery and billing status back to the Opportunity.

02Shopify orders → SAP S/4HANA

“Create SAP orders from Shopify, synchronize inventory, fulfillment, refunds and cancellations.”

Build this integration

PartnerMCP will

  1. Verify each Shopify webhook and drop duplicates by X-Shopify-Webhook-Id.
  2. Map variant SKUs to SAP Material numbers and the buyer to a business partner.
  3. Create the sales order with SalesOrganization, DistributionChannel and OrganizationDivision set for the web channel.
  4. Read A_MaterialStock and push available quantities to Shopify with idempotent inventory adjustments.
  5. Turn Shopify refunds into credit memo requests, held for review before they post.

03Shopify → SAP Business One

“Create Business One sales orders from Shopify and update Shopify when the order is delivered.”

Build this integration

PartnerMCP will

  1. Log in to the Service Layer with a dedicated user and keep ROUTEID for sticky routing.
  2. Find the customer in BusinessPartners, or create it with CardType for a customer.
  3. Create the sales order in Orders, storing the Shopify order ID for duplicate checks.
  4. Subscribe to Orders events through EventSubscriptions (10.0 FP 2602+) — or poll on UpdateDate — and send fulfillment back to Shopify.
§02—Objects and events

Objects and events, by their API names.

The records PartnerMCP reads and writes in SAP, and the events that start a run.

  • Business partner

    API_BUSINESS_PARTNER

    A_BusinessPartner, A_Customer and A_Supplier, with addresses and roles. SAP_COM_0008 in Public Edition.

  • Sales order

    API_SALES_ORDER_SRVA_SalesOrder

    Deep insert through to_Item, to_Partner and to_PricingElement. Header fields include SalesOrderType, SalesOrganization, DistributionChannel, OrganizationDivision, SoldToParty and PurchaseOrderByCustomer.

  • Sales order items

    A_SalesOrderItem

    Material and RequestedQuantity, with schedule lines in A_SalesOrderScheduleLine.

  • Sales order simulation

    API_SALES_ORDER_SIMULATION_SRV

    Pricing, availability and credit checks without saving — PartnerMCP's dry run before a real create.

  • Outbound delivery

    API_OUTBOUND_DELIVERY_SRV_0002

    The Public Edition successor of the deprecated API_OUTBOUND_DELIVERY_SRV. A_OutbDeliveryHeader and A_OutbDeliveryItem, with PostGoodsIssue and ReverseGoodsIssue.

  • Billing document

    API_BILLING_DOCUMENT_SRV

    Read, cancel and PDF only. Invoices are produced by SAP billing from deliveries and orders, not created through this API.

  • Stock

    API_MATERIAL_STOCK_SRV

    A_MaterialStock and A_MatlStkInAcctMod.

  • Credit memos and returns

    API_CREDIT_MEMO_REQUEST_SRVAPI_CUSTOMER_RETURN_SRV

    Credit memo requests and customer returns, for refunds coming from commerce.

  • Business One: business partners

    BusinessPartners

    Customers and vendors in one entity set, told apart by CardType.

  • Business One: sales orders and items

    OrdersItems

    Orders (ObjectType 17) with their events in the Service Layer webhook catalog; exact entity sets are read from each database's $metadata.

Events

  • S/4HANA business events

    Topics such as sap/s4/beh/salesorder/v1/SalesOrder/Created/v1 through SAP Event Mesh or SAP Cloud Application Event Hub, with channel bindings configured in Enterprise Event Enablement. Not every object has every event — sales order deletion events, for one, aren't supported in every scenario.

  • Polling on LastChangeDateTime

    The fallback where an event doesn't exist. On A_SalesOrder, LastChangeDateTime is also the ETag PartnerMCP sends with If-Match.

  • Business One webhooks (10.0 FP 2602+)

    EventSubscriptions on the Service Layer — for example Orders Created, Updated, Closed or Cancelled — delivered by the Webhook Messenger Service with retries, manual replay, ordering attempted per company and HMAC, OAuth or Basic authentication to the endpoint.

  • Business One polling

    For older feature packs: filters on UpdateDate and UpdateTime.

§03—What it handles

What PartnerMCP handles for you.

The details that break SAP integrations in production, and what PartnerMCP does about each one.

  1. 01

    SAP API Policy (April 2026)

    Section 2.2.2 restricts autonomous AI access and large-scale extraction outside SAP's documentation and endorsed architectures. SAP's FAQ places rule-based, pre-defined, deterministic API call sequences outside that section. PartnerMCP's intelligence works at design time; the deployed integration runs the reviewed plan on published APIs, and conversational access can go through your Integration Suite MCP Gateway.

  2. 02

    CSRF tokens and ETags

    Writes need an X-CSRF-Token fetched on a GET first. V4 updates must send If-Match, and V2 sales order ETags live on LastChangeDateTime, so PartnerMCP puts a header change and its item change in one $batch changeset.

  3. 03

    V2 and V4 aren't interchangeable

    The V4 sales order API can't delete whole orders, take an external order number or change schedule lines; V2 has no async mode. PartnerMCP picks the version per operation.

  4. 04

    APIs retire inside the release cycle

    Public Edition deprecates APIs between releases — API_OUTBOUND_DELIVERY_SRV became API_OUTBOUND_DELIVERY_SRV_0002. PartnerMCP tracks API status per release (2602, 2608, …) and proposes the move as a reviewed change.

  5. 05

    Clean core, published APIs only

    SAP's clean-core model rates extensions A to D. Wherever SAP has a released API, PartnerMCP uses it (level A). On private cloud and on-prem, a classic BAPI or IDoc (level B) is used only where no released API covers the step — the plan names it and you approve it. No internal objects, no direct table writes and no ODP-RFC extraction, which SAP now classifies as unpermitted for third-party egress.

  6. 06

    Billing is SAP's job

    API_BILLING_DOCUMENT_SRV reads, cancels and returns PDFs; invoices come from SAP billing. PartnerMCP syncs billing status and never tries to post invoices through the API.

  7. 07

    Business One sessions and paging

    Service Layer sessions time out after 30 minutes (HTTP 401, error 301), and pages default to 20 rows. PartnerMCP logs in again on 401, keeps ROUTEID, sets Prefer: odata.maxpagesize and follows odata.nextLink.

  8. 08

    Throttling without published numbers

    SAP publishes no numeric rate limit for S/4HANA OData APIs but reserves throttling and other controls. PartnerMCP lowers concurrency when SAP pushes back, retries with backoff, and parks what still fails in a dead-letter queue.

§04—Pairings

Pairings, step by step.

Each pair page has the plan, the field mapping and the edge cases for that combination.

§05—Questions

SAP integration questions.

Does SAP's 2026 API Policy allow an AI integration engineer?

The policy requires SAP-endorsed architectures for AI-driven access, and its FAQ says rule-based tools executing pre-defined, deterministic API call sequences without LLM decision-making are outside Section 2.2.2. PartnerMCP is designed for that model: intelligence plans and builds, the runtime executes reviewed calls to published APIs. Your SAP agreement governs, so review it with your SAP team.

Is there an SAP MCP server PartnerMCP connects to?

SAP's endorsed pathways for AI agents are the MCP Gateway in SAP Integration Suite, SAP-provided MCP servers in Joule Studio, and A2A through SAP Agent Gateway. PartnerMCP can route through your MCP Gateway where you run one; its integrations run on published APIs.

Public Edition, private cloud (RISE) or on-prem?

All three. Public Edition works through communication arrangements on published APIs. Private cloud and on-prem add BAPIs and IDocs, and PartnerMCP reaches them through the Edge Agent, so nothing has to be exposed to the internet.

Does it support SAP Business One?

Yes, through the Service Layer (OData V3 or V4). On 10.0 FP 2602 and later, PartnerMCP subscribes to Service Layer webhooks; on older feature packs it polls on UpdateDate.

Can PartnerMCP move SAP data into our warehouse?

Through published APIs and within SAP's documented use. It doesn't use ODP-RFC, which SAP now classifies as unpermitted for third-party extraction.

§06—References

Vendor documentation.

The public documentation behind the technical details on this page.

Product names and logos are trademarks of their respective owners. Their use indicates compatibility only and does not imply endorsement or partnership.

§07Next step

Connect SAP to the rest of your systems.

Describe what should happen. PartnerMCP shows you the plan before anything is built.

Build an IntegrationTalk to an engineer