Learn SAP CPI
From Zero Experience to Consultant-Ready.
Master SAP Cloud Integration — iFlow design, adapters, message mapping, Groovy scripting, routing and splitting, exception handling, security, monitoring, IDoc/OData/B2B integration, Enterprise Integration Patterns, and the new MCP Gateway for AI agent connectivity. Trained exactly the way a consultant builds and supports integrations on a live project.
What you will know and do after this course
Practical, measurable capabilities verified through live SAP Integration Suite work — not theoretical knowledge you'll forget.
Built for people entering SAP integration & middleware careers
SAP CPI is a functional-technical role — logical thinking matters more than prior coding experience, since Groovy scripting is taught from the fundamentals. Whether you come from a technical or non-technical background, this is your structured route into one of the most consistently in-demand SAP specialisations.
19 modules — integration fundamentals to capstone project
Each module: concept overview, live iFlow exercises on the GIM Corp case study, and real interview guidance built in from the start.
Freshers often confuse CPI with SAP PI/PO or treat it as a single adapter rather than a full integration platform. This module establishes the correct scope and vocabulary.
- CPI naming history: Cloud Platform Integration → Cloud Integration
- SAP Integration Suite capabilities: iFlows, API Management, Event Mesh
- Comparison with legacy SAP PI/PO
- CPI tenant architecture: multi-tenant cloud infrastructure
- Deployment models: Cloud-only vs Hybrid with Cloud Connector
- SAP Business Accelerator Hub overview
- iFlow as the core building block
- CPI's role within BTP
- C_CPI_14 certification
- 2026 landscape: BambooHR adapter, Outlook adapter, MCP Gateway
Understanding the design environment before coding prevents wasted effort — many freshers build iFlows in the wrong package or deploy to the wrong tenant.
- CPI tenant architecture: runtime, designer, monitoring
- Provisioning CPI from BTP Cockpit
- Web UI navigation: Design, Monitor, Operate
- Integration Packages as logical containers
- iFlow artifacts: mappings, value mappings, scripts
- Web-based Integration Designer: canvas, palette
- Sender → Processing Steps → Receiver pattern
- Artifact versioning and locking
- Design-time vs runtime
- Externalized parameters for environment configuration
The Message Exchange — body, headers, properties — is the central concept governing every subsequent step in CPI. Getting this wrong causes systematic errors later.
- iFlow anatomy: Sender → Channel → Process → Channel → Receiver
- Integration Process canvas: Start/End events
- Sender and Receiver participant shapes
- Channels as communication bridges
- Message Exchange: body, headers, properties
- Message body: XML, JSON, plain text, binary
- Message headers vs Exchange properties
- iFlow execution lifecycle
- Local Integration Process (reusable subprocess)
- iFlow deployment and status checking
Adapter selection is the first decision in every new iFlow — choosing the wrong adapter causes unnecessary complexity and missing features.
- Sender: HTTPS, SOAP, IDoc, OData, Scheduler
- Sender: JMS, SFTP, AS2/AS4
- Receiver: HTTP/HTTPS, SOAP, OData
- Receiver: SFTP/FTP, IDoc, RFC
- Receiver: JDBC, Mail, Kafka
- Receiver: AS2/AS4, ProcessDirect
- 2026: BambooHR adapter
- 2026: Microsoft Outlook Sender/Receiver adapter
- Adapter selection criteria and trade-offs
- Common misconfigurations and troubleshooting
- OData pagination and error handling advantages
- 50+ adapters covering major enterprise protocols
Message mapping is the most technically complex and most frequently required CPI skill — incorrect field mappings are the most common cause of integration errors in production.
- Mapping editor: source and target structure definition
- Standard mapping functions: string, date, arithmetic, node
- 1:1, 1:N, N:1 field mappings
- Constant values and fixed mappings
- Conditional mapping (if/then/else)
- Context change for cardinality
- Custom mapping functions in Java or Groovy
- Testing mappings with sample payloads
- Value Mapping for code conversion tables
Groovy scripting is the most powerful tool in CPI — nearly every production iFlow includes at least one Groovy script.
- XSLT Mapping for complex XML-to-XML scenarios
- When to use XSLT vs graphical mapping vs Groovy
- XSLT structure: templates, match patterns, loops
- Groovy Script step for custom logic
- Message object in Groovy: body, headers, properties
- Common Groovy patterns: JSON parsing, HTTP calls
- Script Collection for reusable functions
- JavaScript scripting as an alternative
- Error handling within Groovy: try/catch
These steps form the operational vocabulary of iFlow development — used in nearly every practical integration.
- Content Modifier: body, headers, properties
- Filter: extracting XML nodes via XPath
- Converter steps: XML-to-JSON, CSV-to-XML, EDI
- Encoder/Decoder: Base64 for binary data
- Message Digest for integrity verification
- Data Store Write/Read/Delete
- Variables: global state across executions
- Request-Reply: mid-flow external service calls
- Send step: fire-and-forget delivery
Real business integrations almost always involve conditional logic or bulk message handling — Router and Splitter are among the most frequently used steps in production.
- Router: condition-based branching
- Default route fallback
- Multicast: parallel copy delivery
- Sequential Multicast
- Splitter: breaking multi-record messages
- General vs IDoc vs Iterating Splitter
- Aggregator: collecting split messages
- Gather step: collecting multicast branches
- Combining Router, Splitter, and Aggregator
An iFlow without an Exception Subprocess is not production-ready — silent failures are one of the most dangerous production issues in integration.
- Exception Subprocess: the primary error handling mechanism
- Error End event
- Escalation End event
- Successful End event
- Patterns: retry, dead letter, notification, compensation
- MPL error payload capture
- Error notification emails
- Dead Letter Queue via JMS
- Retry configuration: attempts, interval, backoff
- Custom, business-friendly error messages
Credential leakage and unauthorized access to integration endpoints are serious risks — every production iFlow must use the Security Material store, never hardcoded credentials.
- Security Material: keystore-based credential storage
- Credential Store: User Credentials, OAuth2, Secure Parameter
- Certificate-based authentication (mTLS)
- OAuth2 flows: Client Credentials, Auth Code, JWT Bearer
- Basic Authentication
- CSRF Token handling for OData writes
- PGP encryption/decryption for files
- Message-level encryption: XML Digital Signature
- Principal Propagation
- Inbound authentication restrictions
Monitoring is what separates a deployed iFlow from a production-ready integration — without it, failures go undetected until a business process breaks.
- Message Processing Log (MPL): the audit log
- MPL status levels: Completed, Failed, Retry, Escalated
- MPL attachments for custom payloads
- Trace mode for step-by-step debugging
- Integration Content Monitor
- Data Store Monitor
- Message Queues Monitor
- Alerting rules for error patterns
- Custom logging with Groovy
- MPL retention (30-day default)
Always check the Accelerator Hub before building from scratch — pre-built packages can reduce a 3-day build to a 3-hour configuration.
- Browsing and evaluating pre-built packages
- Package types: SAP-standard, partner, community
- Copying and adapting packages for customization
- Common packages: SuccessFactors → S/4HANA, Ariba → S/4HANA
- Evaluating compatibility and version requirements
- Configuring endpoints, credentials, field mappings
- Managing version upgrades
High-volume integrations must be asynchronous — synchronous patterns at scale overload both CPI and target systems.
- Synchronous vs Asynchronous integration
- JMS adapter: queues vs topics
- JMS Queue: guaranteed delivery, persistence
- JMS Topic: publish-subscribe
- Reliable messaging: retry, dead letter
- Two-phase asynchronous pattern
- Quality of Service: EOIO, At Least Once, Best Effort
- Decoupling sender/receiver availability
- SAP Event Mesh integration
IDocs remain the most common format for SAP-to-SAP data exchange — freshers without IDoc knowledge can't effectively work on brownfield integration projects.
- IDoc structure: control, data, status records
- Common IDoc types: ORDERS05, INVOIC02, DEBMAS, MATMAS
- CPI IDoc Sender adapter
- CPI IDoc Receiver adapter
- RFC adapter for BAPIs/Function Modules
- IDoc-to-XML and XML-to-IDoc transformation
- IDoc splitting for multi-record packets
- Partner profiles and logical systems (overview)
- Troubleshooting via WE02, WE05, WE09
OData is the dominant API standard for S/4HANA Cloud and SuccessFactors — freshers who don't understand query options and CSRF handling hit systematic, hard-to-diagnose failures.
- OData protocol: entities, navigation properties, query options
- OData V2 vs V4
- CPI OData Receiver: GET, POST, PUT, PATCH, DELETE
- OData Sender: exposing CPI as an OData service
- Pagination: $skiptoken and nextLink
- REST HTTP adapter for generic APIs
- JSON-to-XML and XML-to-JSON conversion
- CSRF Token handling
- OAuth2 for OData APIs
- Error handling for OData responses
B2B integration is a specialized, high-value skill area — organizations with supply chain, retail, or financial operations frequently need EDI/AS2 capability.
- B2B concepts: trading partners, message standards
- AS2 adapter: non-repudiation, encryption
- EDI standards: EDIFACT, X12
- Integration Advisor for B2B mappings
- Trading Partner Management (TPM)
- Message Interchange patterns
- SWIFT adapter for banking
- B2B security: signing, encryption, MDN
A CPI developer who knows only tools but not patterns cannot communicate effectively with architects or explain design choices to clients.
- Message Routing patterns: Content-Based Router, Recipient List
- Message Transformation patterns: Translator, Content Enricher
- Message Endpoint patterns: Polling, Event-Driven Consumer
- Messaging Channel patterns: Point-to-Point, Pub-Sub, Dead Letter
- Message Construction patterns
- Correlation ID pattern
- Idempotent Consumer pattern
- Implementing EIP patterns in CPI
2026 marks the convergence of integration and AI — CPI is no longer just middleware for moving data, but the governed tool-connectivity layer for enterprise AI agents.
- Integration Suite MCP Gateway: governed API exposure to Joule agents
- Creating MCP-compliant tool definitions
- Access control for MCP tools
- BambooHR adapter for employee lifecycle data
- Microsoft Outlook Sender/Receiver adapter
- AI-powered integration design assistance via Joule
- SAP Event Mesh and Advanced Event Mesh integration
- Integration Suite on RISE with SAP
Capstone module — a complete Procure-to-Pay integration consolidating adapters, mappings, routing, error handling, security, monitoring, and MCP exposure into one realistic engagement.
- End-to-end application of the complete CPI capability stack
- Integration of adapters, mappings, routing, error handling, security, monitoring
- Professional iFlow design following EIP
- Stakeholder-ready documentation and presentation
What learners say after finishing this course
This rating is specific to the SAP CPI program above — not an average across Upskeeling's other courses. We show the breakdown as collected rather than just the headline number, because the detail tells you more than the average does.
The 5-star reviews consistently mention the same thing: deploying real iFlows on a live tenant and watching the Message Processing Log light up made the concepts click in a way slides never had. The 4-star group was happy overall but wanted more repetition time on the harder modules — Groovy Scripting and Security came up most. The 3-star reviews were the most useful to us internally: the recurring note was that the jump from graphical mapping to Groovy scripting feels steep for non-technical joiners. We've since added an extra scripting-fundamentals session before Module 6 to bridge that gap.
Where this programme takes you
- SAP CPI / Integration Suite Trainee
- Junior SAP Integration Developer
- SAP Integration Support Consultant
- Middleware Developer (SAP BTP)
- SAP CPI / Integration Suite Consultant
- SAP Integration Architect
- SAP BTP Integration Lead
- Enterprise Integration Platform Architect
Your trajectory over time
Entry Level
- SAP CPI Trainee
- Junior SAP Integration Developer
- SAP Integration Support Consultant
- Middleware Developer (SAP BTP)
Mid Level
- SAP CPI / Integration Suite Consultant
- SAP Integration Architect
- SAP BTP Integration Lead
- Enterprise Integration Platform Architect
Advanced
- SAP Integration Practice Lead
- Freelance SAP Integration Architect
- Enterprise Integration Programme Manager
- SAP BTP Platform Owner
What SAP CPI consultants earn globally
SAP CPI certification delivers a 40–60% salary premium over non-certified peers with identical academic records.
We stay with you throughout your journey
During Training
- Live sessions on latest Integration Suite version
- Session recordings after every class
- Free SAP Integration Suite tenant for practice
- Detailed notes and study documents
- SAP Press books for reference
- Real-time project simulations
- Interview guidance at each module
Post-Training
- 1 month additional tenant access
- 1 year study material availability
- Job references provided
- Interview scheduling assistance
- C_CPI_14 certification prep support
- Post-implementation knowledge base
Career Support
- Professional CV and resume review
- Mock interview sessions
- Career consultancy and role guidance
- Community access with peers
- Freelance and contract guidance
- Ongoing mentor availability
Already trained, or learning elsewhere? Rent a tenant on its own.
For consultants who already know SAP CPI and just need a live Integration Suite tenant to practice on, or learners following another course who want real hands-on access — without enrolling in the full program.
- Dedicated SAP Integration Suite tenant access — not shared or queued
- Integration support included for technical or configuration issues
- Practice iFlows, adapters, mapping, and security at your own pace
Corporate & Team Training
Programmes
Training your entire SAP integration team at once? We deliver bespoke corporate batches for IT firms, manufacturing and retail enterprises, and organisations consolidating integration onto SAP Integration Suite — with custom schedules, dedicated trainers, and progress reporting.
- Custom batch scheduling — weekday, weekend, or blended
- Dedicated trainer assigned to your organisation
- Team progress dashboards and completion certificates
- Module customisation for your specific integration landscape
- Volume pricing — significant discounts for teams of 5+
- Post-training support for the entire project lifecycle
What you need before starting
- No prior professional coding experience required — Groovy scripting is taught from the fundamentals in Module 6
- Basic familiarity with XML/JSON helpful but not mandatory
- A laptop or desktop with a stable internet connection
- Motivation to practise on the live SAP Integration Suite tenant regularly between sessions
- Any graduate can join — B.Tech, BCA, MCA, B.Sc, or equivalent, with a logical/technical aptitude
Questions before you enrol
Three ways to get your question answered
The integration consultants hired next quarter
are enrolling right now.
Every week you wait is a week someone with the same background — but an SAP CPI certification — pulls ahead. One message. Zero commitment.