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.

README.md

≈717 tokens on demand. Your agent reads this file only when SKILL.md points to it.

sap-cloud-integration skill

CPI runtime knowledge for GitHub Copilot: Groovy script API usage, header and property scope across JMS and ProcessDirect, Exception Subprocess status behavior, JMS retry and idempotency patterns, and an MPL-error-to-root-cause map for SFTP, HTTP/OAuth, IDoc, OData, SOAP, AS2, and Cloud Connector.

Install

Copy the whole sap-cloud-integration folder, including references/, into your project's .github/skills/ folder or your personal skills folder. Copilot loads SKILL.md when a request matches its description and reads the references it routes to.

Provenance and maintenance

  • Written and reviewed by Rameshkumar Varanganti, SAP integration architect (20+ years with SAP PI/PO and SAP Integration Suite).
  • Baseline: SAP Cloud Integration on the Cloud Foundry environment (Integration Suite), current as of November 2026. Neo-environment differences are not covered.
  • Each behavior claim is cross-checked against the SAP Help Portal source in SAP-docs/btp-integration-suite; see references/sap-documentation-index.md. Report corrections as issues in the source repository.

Evaluation scenarios

Each scenario compares a capable model without this skill against the same model with it. "Skill-specific" means the point comes from CPI runtime behavior documented in references/, not from general engineering practice.

# Prompt Skill-specific points the answer must contain
1 "My Exception Subprocess catches the HTTP error, builds an error JSON, and ends with an End event. Support says failed messages don't show up as failed. Why?" A Message End event in the Exception Subprocess makes the MPL status Completed; use Error or Escalation End; set CamelHttpResponseCode for a synchronous caller
2 "iFlow A sets property targetSystem, then sends to iFlow B over JMS. In B the property is empty. Fix it." Properties are not propagated over ProcessDirect and are not stored in JMS unless Transfer Exchange Properties is on (not recommended; 4 MB limit for headers plus properties); pass as a header or in the body
3 "Write a Groovy script that logs the full payload for every message to the MPL." Gate the attachment with an externalized LOG_PAYLOAD flag and cap it with getBodySize(); 1 GB/24 h tenant attachment limit; addCustomHeaderProperty for searchable keys; no secrets or PII
4 "IDoc from CPI to S/4HANA arrives with status 56." Start from the status long text; control record vs. WE20 as the most common cause; 56 vs. 51 distinction
5 "In the Exception Subprocess I need the receiver's HTTP status and error body." CamelExceptionCaught; AhcOperationFailedException with getStatusCode() / getResponseBody(); compare by class name

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