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", "expose an existing BAPI as JSON", "dynamic REST2RFC", "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, /sap/bc/rest2rfc.

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:

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:

Step 3: If there is an error or failure

Read references/troubleshoot/ based on symptom:

Quick technology decision matrix

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

Scripts and assets

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

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.
• Dynamic REST2RFC Gateway: A community pure-ABAP option for exposing registered RFC/BAPIs as JSON through /sap/bc/rest2rfc. Use it on supported ECC/S/4HANA On-Premise systems when no standard OData fits and configuration-driven exposure is preferable to per-interface wrappers. It requires an initial gateway deployment and is not for S/4HANA Cloud Public Edition. Read references/tech/rest2rfc-gateway.md before giving setup, transaction, or security guidance.