[Link]
com/
[Link]
[Link]
Synchronous: Sender/source Sends the request to target system and gives the response back to
Sender/source system
Asynchronous: Sender/source Sends the request to target system and did not receive any
response back to sender/source system
External Call:
Send:
In SAP Cloud Platform Integration (CPI), “Send” usually refers to how you deliver a message
from your iFlow to a target system. This is handled through Adapters and Message
Transformers.
Https-------------content modifier-----------------------SFTP/mail
Https---------------Content modifier-------------------------send--------------------SFTP/mail
Request-Reply : Calls an external receiver system synchronously and retrieves a response.
Use Cases: Certain integration scenarios require the Cloud Integration tenant to communicate
with an external service, retrieve data, and further process it. In such cases, you can use the
request-reply step as an exit point to connect to the external service.
Content Enricher:
Function: The content enricher adds the content of a payload with the original message
during an integration process. This process combines the two separate messages into a
single enhanced payload.
Purpose: This feature enables you to make external calls during an integration process to
obtain additional data.
Here two tabs are there
[Link]: we give meaningful name.
[Link]: here we can perform the operations.
Aggregation Algorithm: Here two options presents.
You can choose between two strategies to enrich these two payloads into a single
message:
Combine: Combines the original and lookup messages. You cannot define any rules for
combining messages with this strategy.
Enrich: Enables you to define paths to specific nodes and key elements within the
original and lookup messages. The original message is enriched with data from the
lookup message based on these paths.
Or
Original Message: The first message in the integration flow.
Path to Node: Path to the reference node within the original message.
Key Element: Key element within the original message.
Lookup Message: The message obtained by making an external call during the
integration process.
Path to Node: Path to the reference node within the lookup message.
Key Element: Key element within the lookup message.
Example: Using OData Adapters
OData Adapter: This adapter exchanges data with a remote component that might be
outside the scope of SAP.
[Link]
Scenario: We will use a product catalog as the resource for the original message
(obtained using a request-reply step with an OData adapter) and add to incoming
payload place a supplier list as the resource for the lookup message (also obtained using
a Content enricher step with an OData adapter).
Enrichment Strategy:
First Scenario: Combine
This option simply combines the two payloads without any modification.
Second Scenario: Enrich
This option merges the two payloads into a single payload based on specified conditions.
Poll rich: only works SFTP/FTP
Polling means picks the files from the particular location
Combine: input payload + response payload of SFTP
Replace: input payload data replaced with sftp file data
Concatenate:Concatenate the two payloads(input + SFTP payload)
Throw Exception if no Message Found: if no file exist in SFTP/FTP then display the message like
Local call:
Process call: it is used in Local sub process and Exception sub process[already discussed]
It calls the local integration process one time.
Looping Process Call:
In SAP Cloud Platform Integration (CPI), a “Looping Process Call” is used to repeatedly execute a
local integration process until a condition is met, making it ideal for handling large datasets or
paginated API calls. It works like a do- until loop: the subprocess runs, then the condition is
checked, and the loop continues until the condition evaluates to false.
10 -----------------------4=4
1=5-false 1
2=5false 2
3=5->false 3
4=5false 4
5=5->true exit loop
Purpose
Efficiently process large datasets without exhausting memory.
Fetch paginated data from APIs (e.g., OData services).
Automate repetitive tasks like polling until a status changes.
Idempotent Process Call
In SAP CPI, the Idempotent Process Call ensures that duplicate messages are not processed
multiple times. It checks whether a message with the same ID has already been successfully
executed and, if so, skips or marks the duplicate. This is critical for “at-most-once” or “exactly-
once” delivery scenarios.
What It Does
Duplicate Detection: Uses the idempotent repository to store message IDs that have
already been processed.
Skip or Mark: If a duplicate arrives (e.g., retry from sender), the subprocess can be
skipped or flagged.
Reliability: Prevents issues like duplicate sales orders, repeated invoices, or multiple file
uploads.
Retention: Message IDs are stored for 90 days by default; after that, duplicates may not
be detected.
CSRF:
It is getting value from get call and pass the values in different methods
Step1:
Step2: Save the application and deploy
Step3: when we are hitting the service and we are getting error like for forbidden
Step4: First getting CSRF token value and using get call
Step5:
The value displayed response headers of the get call
Step6: Same value passed in the remaing calls of the header
Note:
1)CSRF(OData is enabaled)Already fetching the CSRF token from get and no get call required
2)Http Adapterno CSRF option
3)Https AdapaterCSRF option[get CSRF token and passed in different methods]