SAP Cloud Integration

Platform
SAP Cloud Integration 1

Platform
Let’s discuss about SAP Cloud Integration Platform (CPI).
Points We’ll Discuss.

Sr. No Points Page

1. Use Cases
1.1 A2A Integration Scenarios

2. Tools
2.1 BTP, Integration Suite, Postman

3. iFlow Development
3.1
Message Flows:
Sender, Timer (auto time run job) Receiver
3.2 Key Components:
Content Modifier
Groovy Script
Request Reply

4. Adapter & Protocol

4.1 4.2 HTTP, HTTPS, OData Configure
4.3 Endpoints
Adapter Specific Setting
 2

Use Cases:
A2A Integration: A2A (Application to Application) means you are
communicating within same firewall or in same company or same land scape.

For example, if One company ABC has implemented the R/3 & XI and say there
will be several departments (modules like Sales, Material Mgmt. etc..) So if Sale
department is dealing with the Material management department within the
company then you will say it A2A.

Tools:

We’re Using here the

Postman: Used for initial API testing and triggering API calls.
Integration Suite: For iFlow development, testing, monitoring, and deployment.
BTP: Serves as the access layer to reach and manage the Integration Suite.

iFlow Development: in the flow we are using

Timer: The integration flow starts using a Timer event. This is typically used for scheduling
the integration to run at specific intervals (e.g., hourly, daily).

In this Case: It triggers the flow automatically based on the configured time.

Request Reply (For Get SLD URL): This Request Reply is used to set headers,
properties, or body content before proceeding.
Adapter: HTTP

In this Case: It appears to be preparing the request to fetch a URL from the SLD (System
Landscape Directory), possibly setting a required endpoint or parameters.

Groovy Script : Executes a custom Groovy script to process or manipulate message data
dynamically.

In this Case: Likely used to fetch or transform data from the SLD URL response, or to
construct a new message payload or headers based on logic.

SAP CPI
 3

Content Modifier : Used again here to adjust or enhance the message content after
Groovy processing.

In this Case: May set final headers, properties, or the request body before making an
external call to ECC.

Request Reply: This step sends a synchronous request to a target system and waits for a
response.

Adapter: OData

In this Case: The integration flow is sending the prepared message to ECC (SAP ERP) and
waits for a reply to continue further.

SAP CPI
 4

Design the iFlow:

Go to Integration Suite -> Design -> Integration and APIs -> Create new iFlow

SAP CPI
 5

This will be our initial/default iFlow, triggered by a Timer instead of a Start event
(Nav Bar → Event → Scroll Down → Timer).

Add it instead of Start Message. and connect with End.

SAP CPI
This will be our initial/default iFlow, triggered by a Timer instead of a Start event
(Nav Bar → Event → Scroll Down → Timer), followed by adding a Content
Modifier (click the blue connecting line → plus button → Content Modifier).

Open Postman new collection and test this API Endpoint

[Link]

SAP CPI
There are basically three items is there. We’ll go with “Products”. Just add
“/Product” in the URL.

SAP CPI
 7

Copy any of the one payload from response body. And paste with the
mentioned changes in Message Body, Content Modifier.
Change the ID and Description.

The Payload:
<Products>
<Product>
<ID><Change as per yours></ID>
<Name><Change as per yours></Name>
<Description><Change as per yours></Description>
<ReleaseDate>2023-01-01T00: 00: 00</ReleaseDate>
<DiscontinuedDate />
<Rating>4</Rating>
<Price>2.5</Price>
</Product>
</Products>

SAP CPI
SAP CPI
 8

This default iFlow starts with a Timer, followed by a Content Modifier and a
Request Reply for external communication.

Connect to the receiver using the OData adapter; paste the API endpoint from
Postman (excluding “items” for Products), set Proxy to Internet, and
Authentication to None since no authorization is required.

SAP CPI
 9

In the process step, set Operation Details to POST and click on Select.

Leave all configurations unchanged.

SAP CPI
 10

Step 2: Operation: POST

• Select Entity: Products

• Select all fields of Products
• Click the Finish button

SAP CPI
Here is the expected configuration of your OData Adapter process.

SAP CPI
 11

Next, add a Groovy Script to handle the response.

Groovy Script:
import [Link];
def Message processData(Message message) { def body =
[Link]([Link]) as String; def messageLog =
[Link](message); // Assuming messageLogFactory is
available
if (messageLog != null) {
[Link]("DataResponse", body, "text/plain"); }

// Ensure the Message object is returned

return message;
}

SAP CPI
 12

Here is the final result: your iFlow has been successfully deployed and its status is Completed.

There are many more configurations, settings, and changes involved, but at this
initial stage, these steps are quite sufficient to understand the basic working
process of SAP CPI.

To be continued with B2B, B2G, and Hybrid Integration scenarios — along with
many more insights I’ve learned and look forward to sharing with you all.

SAP CPI