sap-integration-wiki · diff

git:20261014.55ca1dc to git:20261027.c3d6f64

4 added, 0 removed. Audit A to A.

---

name: sap-integration-wiki

description: >

Guide for integrating external systems (Java, Python, .NET, Node.js,

low-code) with SAP (ECC 6.0, S/4HANA On-Premise/Cloud): OData V2/V4, RFC/JCo,

SOAP-over-HTTP RFC without JCo, IDoc/PI-PO, BAPI, RAP, BTP Integration Suite/iFlow,

Event Mesh, Cloud Connector, Communication Arrangements, FI-AA, AR/AP, Central Finance

(CFIN), Financial Shared Service Center / 财务共享中心 (Kingdee/金蝶, 用友 to SAP).

Activate whenever the user asks to connect to SAP, call a SAP API/BAPI/RFC, read or

create SAP data from outside (purchase/sales/production orders, inventory, financial

documents, AR/AP, assets, material master, business partner), configure JCo

destinations, call RFC/BAPI from Python/Java/Node/Go without SAP libraries, handle

IDocs, set up S/4HANA Cloud Communication Arrangements, implement retry/idempotency,

or troubleshoot SAP HTTP 400/401/403, "CSRF token validation failed", "IDoc status 51",

"/sap/bc/soap/rfc", JCo/RFC destination errors — even when the user never says "SAP"

and only describes symptoms.

---

# SAP Integration Wiki

+ **Runtime requirement: none.** This is a knowledge base — never check for,

+ install, or require the `sap-adt` CLI. (`references/runtime-compatibility.json`

+ declares `not-required`; `references/setup.md` is informational only.)

This skill routes integration questions to the right reference based on your context.

Before loading any reference file, ask the following if not already clear from the

user's message:

## Trigger examples

User phrases that should activate this skill (non-exhaustive): "connect to SAP",

"get data from SAP", "SAP keeps returning 401", "how do I call BAPI from Java",

"how do I call SAP RFC from Python", "call SAP without JCo", "SAP SOAP endpoint",

"SAP OData not working".

Object/endpoint names that signal this skill: `BAPI_PO_CREATE1`,

`API_PURCHASEORDER_PROCESS_SRV`, `BAPI_FIXEDASSET_GETLIST`,

`BAPI_ASSET_ACQUISITION_POST`, `CFIN OData V4`, `API_CFinRpldSupplierInvoice`,

`JCo connection`, `RFC destination`, `BTP iFlow`, `Cloud Connector`,

`SAP Event Mesh`, `Communication Arrangement`.

## Clarifying questions (ask only what is unknown)

1. **SAP version**: ECC 6.0 / S/4HANA On-Premise / S/4HANA Cloud Public Edition / S/4HANA Cloud Private Edition?

2. **Integration direction**: External → SAP (write/trigger) / SAP → External (event/push) / Bidirectional / Read-only query?

3. **Latency requirement**: Synchronous (real-time response needed) / Asynchronous (fire-and-forget or queue)?

4. **Business object**: Purchase Order / Sales Order / Inventory/Stock / Financial Document / Material Master / Business Partner / Production Order / BOM / Other?

5. **Consumer technology**: Java/JVM / Python / .NET / Node.js / Low-code (Zapier, Power Automate) / Other?

---

## Routing logic

After clarifying, follow this decision tree to pick the right reference files:

### Step 1: Pick the scenario file

Read the relevant file from `references/scenarios/` based on the business object:

| Business Object | File |

|---|---|

| Purchase Order (create, read, change, approve) | `references/scenarios/mm-po.md` |

| Inventory / Stock query or reservation | `references/scenarios/mm-stock.md` |

| Sales Order (create, track, confirm) | `references/scenarios/sd-order.md` |

| Financial Document (post GL, read FI docs) | `references/scenarios/fi-doc.md` |

| AR / AP open items, supplier invoice, payment, down payment | `references/scenarios/fi-ar-ap.md` |

| Fixed Asset (read register, acquisition, retirement, transfer) | `references/scenarios/fi-asset.md` |

| Financial Shared Service Center (FSSC) — Kingdee↔SAP, CFIN | `references/scenarios/fi-fssc.md` |

| Material Master / Business Partner / Org Data (cost center, plant) | `references/scenarios/master-data.md` |

| Production Order / BOM / Goods Movement (261/101) / MRP | `references/scenarios/pp-production.md` |

**Always read the scenario file first** before reading any tech file.

The scenario file specifies which integration technology to recommend per version.

### Step 2: Pick the technology file

Read the relevant file from `references/tech/` based on the recommended approach from Step 1:

| Technology | File | Use when |

|---|---|---|

| OData REST V2/V4 | `references/tech/odata.md` | S/4HANA On-Prem or Cloud, standard scenario, HTTP-native client |

| RFC / JCo (Java remote function call) | `references/tech/rfc-jco.md` | ECC (primary), S/4 when no OData exists, bulk operations, Java-only |

| SOAP over HTTP RFC (no JCo) | `references/tech/soap-rfc-http.md` | Call any RFC-FM from non-JVM runtime via HTTPS — Python, Node.js, Go, curl; ECC or S/4 On-Prem |

| IDoc / SAP PI-PO | `references/tech/idoc-pi.md` | Async integration, EDI, partner/supplier message exchange |

| BAPI or RAP | `references/tech/bapi-rap.md` | ECC BAPIs, S/4HANA RAP OData V4 services, decision on which to use |

| Authentication (any technology) | `references/tech/auth.md` | Auth failures, first-time setup, OAuth2, SSL/TLS, ICF activation |

| BTP Integration Suite / iFlow / Cloud Connector / Event Mesh | `references/tech/btp-cloud-integration.md` | BTP-mediated integration, S/4HANA Cloud + BTP, Event Mesh consumers, Communication Arrangements |

| Retry / idempotency / security / monitoring / testing | `references/tech/best-practices.md` | Production hardening, error classification, structured logging, connection pooling, CI patterns |

### Step 3: If there is an error or failure

Read `references/troubleshoot/` based on symptom:

| Symptom | File |

|---|---|

| HTTP 4xx / 5xx from OData endpoint | `references/troubleshoot/odata-errors.md` |

| Login failures / token issues / CSRF errors | `references/troubleshoot/auth-errors.md` |

| IDoc stuck / status 51 / port not configured | `references/troubleshoot/idoc-errors.md` |

| Behavior differs between SAP versions | `references/troubleshoot/version-diff.md` |

---

## Quick technology decision matrix

Use this when the user has not specified a technology preference:

|---|---|---|---|

| ECC 6.0 | Query AR/AP open items | JCo `BAPI_AR_ACC_GETOPENITEMS` / `BAPI_AP_ACC_GETOPENITEMS` | — |

| S/4HANA CFIN | Post from non-SAP (Kingdee) to Central Finance | OData V4 `API_CFinRpldSupplierInvoice` / `API_CFinRpldBillingDocument` (Comm. Arr. SAP_COM_0453) | BTP iFlow + CFIN |

| Any | BTP-mediated integration to S/4HANA Cloud | BTP Integration Suite iFlow + Communication Arrangement | N/A |

---

## Scripts and assets

Point users to these runnable artifacts when they need working code or templates:

| Need | Resource |

|---|---|

| Generate Postman Collection for any OData service | `scripts/gen-odata-postman.js` |

| Generate JCo `.jcoDestination` properties file | `scripts/gen-jco-config.py` |

| Generate IDoc XML skeleton for any message type | `scripts/gen-idoc-template.py` |

| PO creation payload (OData V2 POST body) | `assets/payloads/po-create.json` |

| PO item quantity update (PATCH body) | `assets/payloads/po-update.json` |

| IDoc ORDERS05 XML example | `assets/payloads/idoc-orders05.xml` |

| OAuth2 config template for S/4HANA On-Premise | `assets/configs/oauth-template.json` |

| JCo connection properties template (all properties) | `assets/configs/jco-props.template` |

---

## Response format

When answering an integration question, always structure the response as:

1. **Recommended approach** — one sentence naming the technology and why it fits the user's version and scenario

2. **Prerequisites** — what must be configured on the SAP side first (user roles, service activation, RFC destination, partner profile, etc.)

3. **Implementation steps** — numbered list with working code snippets (curl, Java, Python as appropriate to the user's tech stack)

4. **Common pitfalls** — 2–3 things that typically go wrong and exactly how to avoid or fix them

5. **Reference** — link to SAP API Business Hub or SAP Help Portal page when available

---

## Important SAP concepts for non-SAP developers

- **CSRF token**: SAP OData services require a two-step process for mutating operations (POST/PATCH/DELETE). First GET to fetch the token, then include it in all write calls. Token is tied to a session cookie.

- **BAPI_TRANSACTION_COMMIT**: Every write BAPI call in SAP must be followed by an explicit `BAPI_TRANSACTION_COMMIT` call, or the changes will be rolled back. This is a hard requirement, not optional.

- **OData $batch**: SAP OData supports `$batch` for grouping multiple operations, but has strict ordering and boundary requirements.

- **SAP system number (SYSNR)**: A two-digit instance number (e.g., `00`), not the host port. Do not confuse with port 3300+SYSNR.

- **Client**: SAP is multi-tenanted within a single system. Always specify the client (e.g., `100`, `800`) in every connection.

- **ICF node**: SAP Internet Communication Framework. OData services are only reachable if the corresponding ICF node is activated. Transaction: `SICF`.

- **SOAP over HTTP RFC**: SAP exposes all RFC-enabled function modules via a standard SOAP endpoint at `/sap/bc/soap/rfc`. No SAP-specific client library is required — any HTTP library works. The ICF node for this path must be activated in `SICF`. Use this when JCo is not practical (non-JVM runtimes, containerised workloads, rapid prototyping). Does not support IDoc, tRFC, or qRFC.