Index of every page on this site: llms.txt
All skills
github avatar

/sap-cloud-integration

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

SAP Cloud Integration (CPI, part of SAP Integration Suite) runtime-specific guidance for building and troubleshooting iFlows. Use when writing or reviewing CPI Groovy scripts, choosing headers vs. exchange properties, designing exception subprocesses, JMS retry, idempotency or data store patterns, or diagnosing adapter errors (SFTP, HTTP/OAuth, SOAP, IDoc, OData, AS2, Cloud Connector) from Message Processing Log (MPL) text. Not for SAP PI/PO, ABAP development, or generic Java/Groovy outside CPI.

  • 7 files
  • 42.5 KB
  • Updated last week
  • GitHub
Use this Skill: https://skilld.dev/gh/github/awesome-copilot/sap-cloud-integration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈131 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈9.4k more on demand in 6 files.

Description uses 6.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈524 characters, or 6.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

SAP Cloud Integration (CPI)

This skill supplies CPI runtime behavior that general models often get wrong: what survives a JMS or ProcessDirect hop, how End events change the monitored status, which Camel and SAP_ headers the runtime reads, how scripts should touch large payloads, and how specific adapter error texts map to root causes.

Required references

Read the matching reference before answering. Resolve paths relative to this file.

Task Read first
Write, review, or optimize a Groovy script references/groovy-scripting.md
Decide header vs. property, write Simple expressions, use SAP_/Camel names references/headers-properties-expressions.md
Exception subprocess, End events, retry, JMS, idempotency, data store references/error-handling-reliability.md
Diagnose an MPL error or adapter failure references/adapter-troubleshooting.md
Need SAP's own wording, a field not covered here, or a source link for the user references/sap-documentation-index.md

Rules that change the answer

  1. Exchange properties stay inside one iFlow. They are not propagated over ProcessDirect. They are not stored in a JMS queue unless the JMS receiver's Transfer Exchange Properties option is on, which SAP does not recommend because of size limits. Pass what a downstream iFlow needs as a header or in the body. Headers that leave the tenant must not carry secrets.
  2. An Exception Subprocess that ends with a Message End event reports the message as Completed. Use an Error End event when the failure must stay visible in monitoring. For synchronous senders, also set CamelHttpResponseCode.
  3. Check message.getBodySize() before reading a body with getBody(String). Treat -1 (size unknown) as too large. For large payloads, use a streaming parser or a streaming splitter. Line-by-line reading only helps for line-delimited formats; minified JSON or XML is often a single line. Never attach payloads to the MPL unconditionally: gate attachments behind an externalized flag and cap their size. Tenants can write at most 1 GB of MPL attachments per 24 hours.
  4. Use SAP_ApplicationID for business keys. It makes messages searchable in Monitor. Do not build custom correlation stores for this.
  5. Reliable delivery needs JMS (or a data store) for retry, and duplicate protection on the receiver side. An Idempotent Process Call skips messages already processed successfully, but if a receiver commits and the acknowledgment is lost, a retry can still duplicate the effect (at least once). A failed synchronous call is not redelivered by the runtime; the caller must retry. To stop retrying after N attempts, route on SAPJMSRetries. The JMS sender sets it only for Non-Exclusive queues.
  6. Read credentials through the Security Material APIs (SecureStoreService), never from externalized parameters or headers. Trust a server certificate chain only after verifying its fingerprints against an independent source, never just because a TLS test returned it, and never disable certificate validation as a fix.
  7. Diagnose from the exact MPL text. Separate evidence (error text, HTTP status, step ID) from hypotheses, and give one concrete check per hypothesis (Connectivity Test, trace, keystore entry, Cloud Connector log).

Output contract

  • Code is complete and runnable in a CPI Script step: imports, null handling, guarded messageLog.
  • Generated code contains no author names, credits, or promotional URLs.
  • Say which iFlow step the code or setting belongs to and what to configure there (adapter field, End event, externalized parameter).
  • Include test steps for the tenant (trace level, expected MPL status and properties).
  • End with Static analysis — not tested on a tenant unless the user confirms a successful test run on their tenant; deployment alone is not enough.
  • If a field name, limit, or behavior is not in these references and you are unsure, say so and point to the matching page in references/sap-documentation-index.md. Do not invent adapter fields, headers, or SAP Note numbers.
  • Before designing a new integration between SAP products, check SAP Business Accelerator Hub for prepackaged integration content and SAP Architecture Center for a reference architecture. Extend standard content rather than rebuilding it.

Authoritative sources

When you cite a source to the user, link the public SAP page (SAP Help Portal, SAP Business Accelerator Hub, SAP Architecture Center, or another official SAP site), not the GitHub Markdown source. When these sources and this skill disagree, the SAP documentation wins. Tell the user about the difference.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for github/awesome-copilot/sap-cloud-integration