BTP & Integrationbeginner

BTP Integration Suite Part 3: Build and Deploy Your First iFlow

Key takeaway

Build a working integration flow step by step: create a package and iFlow, configure an HTTPS sender, use a Content Modifier and a Request-Reply to an OData receiver, map the response, deploy, call the endpoint with Postman, and read the message processing log.

Explanation

📌 KEY POINTS
✅ iFlows live in integration packages; each flow has sender, integration process steps and receivers.
✅ HTTPS sender exposes an endpoint; OData/HTTP/SOAP/IDoc adapters connect receivers.
✅ Content Modifier sets headers/properties/body; Request-Reply calls a system and continues with the response.
✅ After deployment, test the endpoint and check the message processing log (MPL).
⚠️ Hard-coding URLs and credentials inside the iFlow blocks reuse across environments — externalize parameters.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 set up the tenant. Now your first flow.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PACKAGE & IFLOW

Create, name, describe.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SENDER

HTTPS adapter; address; authorization.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PROCESSING

Content Modifier, Request-Reply, mapping.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RECEIVER

OData adapter with credential alias.

━━━━━━━━━━━━━━━━━━━━
▶ 5. DEPLOY & TEST

Endpoint URL; MPL.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create package and iFlow.
Configure HTTPS sender and OData receiver.
Deploy, call with Postman, check MPL.

✅ CHECKPOINT: MPL shows Completed and response returns data.

Code example

ABAP Code

===== FLOW =====Sender (HTTPS /orders) → Content Modifier (set header SAP_ApplicationID = ${header.orderId}) → Request-Reply → Receiver (OData API_SALES_ORDER_SRV) → Message Mapping → End ===== EXTERNALIZED PARAMETERS ====={{receiver_url}} | {{credential_alias}} | {{page_size}} ===== TEST =====POST /http/orders with Bearer token → Monitor → Message Processing → status Completed

Real project scenario

A new integration developer built an iFlow with a hard-coded test URL; after transport to production it still called test. Externalizing the URL and configuring it per tenant fixed it.

Common mistakes

Hard-coded URLs.
Trace left on.
No MPL check.
Credentials in scripts.
No naming conventions.

Best practices

Externalize parameters.
Short trace windows.
Check MPL after tests.
Use security material.
Naming standards.

Interview angle

Questions: "Walk through building an iFlow", "What is Request-Reply?", "How do you test an iFlow?"
Strong answer: package/iFlow, adapters, steps, externalization, testing/MPL.

Practice this lesson

Quick check

1. A team proposes hard-coding the test receiver URL in the iFlow to save time. What happens after transport?

2. Which step calls a back end and continues processing with its response?

3. Where should environment-specific receiver URLs normally be handled in an Integration Suite iFlow?

Interview questions

1. How would you apply Integration Suite in a real SAP project? Walk through the design or implementation approach.

Answer it in your own words first, then compare.

2. What is the difference between message body, header and exchange property in a Cloud Integration iFlow?