SAP Cloud Integration Training | SAP CPI Training
                     SAP CPI Architecture – Overview
SAP Cloud Integration (CPI) is an integration platform within SAP Integration Suite.
Connects SAP and non-SAP applications, systems, and APIs.
Supports cloud-to-cloud and cloud-to-on-premise integrations.
Uses Integration Flows (iFlows) to define data movement and processing.
Provides monitoring, security, transformation, and connectivity capabilities.
Key Components: Sender System • SAP CPI • Integration Flow • Receiver System • 
Connectivity & Security
+91-70322905
46
High-Level SAP CPI Architecture
Architecture Flow: Sender System → SAP CPI → Receiver System
Sender: SAP S/4HANA, Salesforce, REST API, third-party application, etc.
CPI Tenant: Receives, processes, transforms, and routes messages.
Receiver: SAP SuccessFactors, S/4HANA, database, API, or external application.
Adapters enable communication between CPI and different systems.
Example: S/4HANA → CPI → Salesforce
+91-70322905
46
SAP CPI Core Architecture Components
Integration Runtime: Executes integration flows and processes messages.
Integration Flow (iFlow): Defines the complete integration logic.
Adapters: Connect using HTTP, SOAP, OData, SFTP, IDoc, and other protocols.
Message Processing: Handles mapping, routing, filtering, and transformations.
Security Material: Stores credentials, certificates, and authentication information.
Monitoring: Tracks message processing, errors, and integration performance.
+91-70322905
46
Sender and Receiver Communication
Sender systems send data to SAP CPI through configured endpoints.
Common sender protocols: HTTPS, SOAP, SFTP, OData, and IDoc.
Receiver systems receive processed data from CPI.
CPI selects the appropriate adapter and endpoint for the target system.
Practical Example:
External application → HTTP request → CPI validation & transformation → S/4HANA 
using OData
+91-70322905
46
Integration Flow – Practical Example
Scenario: Employee data synchronization
Source: SAP SuccessFactors
Middleware: SAP CPI
Target: SAP S/4HANA
iFlow Steps: Receive employee data → Validate → Transform with Message Mapping → Prepare fields 
→ Route → Send to S/4HANA
Result: Employee information is synchronized automatically.
+91-70322905
46
Connectivity & Security in CPI
Connectivity: HTTP/HTTPS • SFTP • SOAP • OData • IDoc • JDBC
Security: Basic Authentication • OAuth 2.0 • Client Certificates • Security Keys • 
Credential Management
On-Premise Integration: SAP Cloud Connector creates a secure connection between CPI 
and on-premise systems.
Cloud Connector helps avoid exposing internal systems directly to the internet.
Example: CPI → Cloud Connector → On-Premise SAP S/4HANA
+91-70322905
46
Monitoring and Error Handling
CPI monitoring tracks message processing status, successful messages, failed messages, 
logs, and traces.
Error Handling Techniques: Exception Subprocess • Retry mechanisms • Error notifications • 
Logging • Custom error messages
Practical Example:
If S/4HANA is temporarily unavailable → CPI captures the error → Exception Subprocess handles it → 
Notification is triggered.
+91-70322905
46
End-to-End Architecture – Summary
Complete Flow: Source Application → Adapter → CPI Integration Runtime → Validation & 
Transformation → Routing & Business Logic → Receiver Adapter → Target Application
CPI acts as the central integration layer.
Adapters enable connectivity between different systems.
iFlows define integration logic.
Mapping and transformation make data compatible.
Cloud Connector supports secure on-premise connectivity.
Example: SAP SuccessFactors → SAP CPI → SAP S/4HANA
+91-70322905
46
Contact
SAP CPI
Address:- Flat no: 205, 2nd Floor,
• Nilgiri Block, Aditya Enclave,
• Ameerpet, Hyderabad-1 
• Ph. No: +91-7032290546 
• Visit: www.visualpath.in 
• E-Mail: [email protected]
+91-70322905
4+691-70322905
46
THANK YOU
                    Visit: www.visualpath.in
+91-70322905
46