sap-btp-integration-suite

Build and troubleshoot SAP Integration Suite iFlows, API proxies, and B2B integrations.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-integration-suite-melik1986
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-btp-integration-suite
Source: https://github.com/Melik1986/axon-erp-api/tree/main/cursor/skills/sap-btp-integration-suite
Command: npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-btp-integration-suite-melik1986

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developing enterprise integrations on SAP BTP requires deep knowledge of Cloud Integration flow steps, 80+ adapters, API Management policies, and B2B standards, and mistakes in package structure or configuration cause failed deployments and broken message processing. ## Core Features & Use Cases - iFlow Development: Guidance for building integration flows with routing, mapping, splitting, scripting, and error handling, including importable HTTPS-to-SFTP package templates. - API Management: Reference for all 34 policy types, proxy endpoint structure, quota and spike arrest configuration, and Developer Hub setup. - B2B and Hybrid Integration: Coverage of Integration Advisor MIG/MAG creation, Trading Partner Management, AS2/AS4/EDI adapters, and Edge Integration Cell Kubernetes deployment. - Use Case: When asked to generate an importable Cloud Integration package, the Skill produces a correctly structured iFlow ZIP layout with externalized placeholders instead of an invalid flat XML file. ## Quick Start Ask the assistant to generate an importable HTTPS-to-SFTP integration flow package for SAP Cloud Integration with externalized connection parameters.

Frequently Asked Questions about sap-btp-integration-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an importable iFlow package for SAP Cloud Integration?▼

An importable iFlow package requires a specific structure: .project file, META-INF/MANIFEST.MF, metainfo.prop, parameters.prop, and the .iflw file under src/main/resources/scenarioflows/integrationflow/. Start from the bundled HTTPS-to-SFTP template and customize only the externalized placeholders.

What adapters does SAP Cloud Integration support?▼

SAP Cloud Integration provides 80+ adapters including protocol adapters (HTTP, SFTP, FTP, SOAP, OData, AMQP, JMS, Kafka, AS2, AS4), application adapters (SuccessFactors, Ariba, Salesforce), JDBC database adapters, and cloud adapters for AWS, Azure, and Google Cloud.

How do I prevent duplicate message processing in an integration flow?▼

Use the idempotent process call pattern with ID mapping to detect duplicate message IDs and return cached responses. Alternatively, combine JMS queues with transactional handling or use data stores to track processed messages for exactly-once delivery.

Does SAP API Management support rate limiting and quotas?▼

Yes, API Management includes Quota policies for limiting calls over time periods, Spike Arrest for preventing traffic bursts, and Concurrent Rate Limit for simultaneous connections. Response Cache policies can also reduce backend load.

Why does my iFlow exception subprocess not catch data store errors?▼

Exception subprocesses cannot catch data store duplicate key errors because the transaction rolls back before handling. Exceptions raised inside local integration processes are also not propagated to the main process exception handler.

What are the limitations of content transport between Integration Suite tenants?▼

Content cannot be transported between Neo and Cloud Foundry environments, draft artifacts are excluded, and access-policy-protected artifacts are restricted. Externalized parameter values remain unchanged during transport and must be updated manually per environment.