SAP Integration Suite Interview Questions
Integration Suite Overview
What is SAP Integration Suite, and what does it replace?
Integration Suite is SAP's BTP-based integration platform as a service, succeeding SAP PI/PO for cloud and hybrid scenarios. It bundles Cloud Integration (message flows), API Management, Event Mesh, Integration Advisor, and Open Connectors. The strategic message: new integrations go to Integration Suite; PI/PO stays for legacy on-premise maintenance.
What are the main capabilities inside the suite?
Cloud Integration designs and runs iFlows — the successor to PI/PO message mappings. API Management exposes and governs APIs with policies and developer portals. Event Mesh provides event-driven messaging across systems. Integration Advisor suggests mappings using machine learning. Know all four by name and one-line purpose.
How is Cloud Integration licensed and structured in 2026?
Cloud Integration runs on BTP as a subscribed service with message-based metering. Development happens in the web-based Integration Flow designer; deployment targets the Cloud Integration runtime tenant. Avoid quoting specific prices in interviews — pricing models change; instead show you understand the message-volume concept.
Key takeaway: Integration Suite = iPaaS on BTP. Cloud Integration is the iFlow engine; API Management, Event Mesh, and Integration Advisor orbit it.
iFlows: Design and Mapping
What is an iFlow, and what are its core building blocks?
An iFlow is a graphical integration flow: sender adapter, message processing steps, and receiver adapter. Core steps include Content Modifier (headers, properties, body), Message Mapping (structure transformation), Groovy scripting, Router (conditional branching), and Request-Reply for synchronous calls. If you can sketch an iFlow on a whiteboard, you pass the practical bar.
How does message mapping work in Cloud Integration?
The graphical Message Mapping editor transforms source to target structures with drag-and-drop and standard functions (concat, formatDate, constants). Complex logic goes to Groovy scripts or XSLT mappings attached as mapping steps. Integration Advisor can propose mappings from its knowledge base of B2B and SAP interfaces.
When do you use Groovy script instead of graphical mapping?
Groovy handles logic the mapper cannot: dynamic lookups, complex string manipulation, JSON parsing edge cases, and custom validation. Keep scripts small and testable — a 300-line Groovy step is a maintenance liability. Interviewers like hearing that you prefer the mapper for structure and Groovy for logic.
// Groovy: read a header and set a property for routing
def message = message;
def region = message.getHeader("Region", String);
message.setProperty("TargetSystem",
region == "EU" ? "S4_EU" : "S4_US");
return message;What is the difference between synchronous and asynchronous iFlows?
Synchronous flows use Request-Reply with sender adapters like HTTPS or SOAP waiting for the response — used for real-time lookups. Asynchronous flows use polling or event-based senders (SFTP, IDoc, JMS) with guaranteed delivery through the messaging system. The choice affects error handling, timeouts, and exactly-once semantics.
Adapters and Connectivity
Which adapters matter most, and when is each used?
HTTPS/SOAP for web services and synchronous calls, SFTP for file transfer, IDoc and RFC for SAP backend connectivity, OData for S/4HANA APIs, JMS for messaging, and Mail for email alerts. The Cloud Connector bridges on-premise systems to the BTP tenant securely. Name the adapter by scenario, not from memory of a list.
How do you connect Cloud Integration to an on-premise S/4HANA system?
Install the Cloud Connector in the corporate network, define the accessible backend hosts and ports, and reference the virtual host in the iFlow's receiver channel. Authentication typically uses basic auth, client certificates, or OAuth2 via a destination in BTP. The Cloud Connector initiates outbound TLS, so no inbound firewall holes are needed.
What is a JMS queue's role in reliable integration?
JMS queues decouple sender and receiver with persistent, transactional messaging — the backbone of exactly-once processing in async scenarios. Failed messages land in dead-letter handling for analysis and replay. When an interviewer asks about guaranteed delivery, JMS persistence is the core of the answer.
Key takeaway: Adapters are chosen by scenario; the Cloud Connector is the on-premise bridge; JMS gives you reliability guarantees async HTTP cannot.
Security, Monitoring, and Operations
How is security handled in Cloud Integration artifacts?
Credentials live in the Security Material section as User Credentials, OAuth2 credentials, or keystore entries — never hardcoded in flows. PGP encryption, message-level signatures, and HTTPS/TLS cover transport and payload protection. Certificate expiry monitoring is an operational duty interviewers love to probe.
How do you monitor and troubleshoot iFlows?
The Monitor section shows message processing logs with per-step trace, payloads (where logging is enabled), and error details. Enable trace selectively — full payload logging in production is a performance and compliance risk. Common triage: check the failed step, inspect the payload at that step, then verify connectivity and credentials.
What is exception handling best practice in an iFlow?
Use Exception Subprocesses to catch errors per integration process or per step, route failures to alerting (mail, ticket creation), and persist the failed payload for replay. Design for idempotent receivers so replays don't duplicate business documents. "It just fails and someone checks the monitor" is not an acceptable answer.
What does API Management add on top of Cloud Integration?
API Management governs API exposure: rate limiting, quota policies, API keys and OAuth scopes, developer portal for discovery, and analytics on usage. Cloud Integration implements the integration logic; API Management productizes the resulting API for consumers. In interviews, keep the separation crisp: build vs govern.
How does Event Mesh fit into an integration architecture?
Event Mesh provides asynchronous event brokering — systems publish business events (order created, goods issued) and subscribers react without point-to-point coupling. It complements iFlows: use events for decoupled notifications, iFlows for orchestrated transformations. S/4HANA business events flowing to BTP apps is the canonical 2026 scenario.
Facing an Integration Suite interview? Drop your hardest scenario in the comments.
Read more →