Exploring Cloud Integration - Part 5 (Creating and Configuring a General Splitter)

The last time, we added a content modifier with payload to the integration flow and traced the process.. However, our objective today is to create and configure a general splitter.

A splitter (iterator) is required to process every productID of the incoming list.

Definition of Term

The General Splitter splits a composite message comprising N messages into N individual messages, each containing one message with the enveloping elements of the composite message. We use the term enveloping elements to refer to the elements above and including the split point.

Task Flow

I performed the following tasks:

1. Logged on to the integration flow DelayedDelivery_Process.
2. Created and configured a General Splitter.
3. Saved as version, deployed, and debugged the integration process.

Prerequisites

The step of creating a Content Modifier with sample data as payload (XML) has been completed in the last article.

Outcome After This Exercise

Environment

Live SAP BTP account.

Steps

1. Logged on to the integration flow DelayedDelivery_Process via Integration Suite.

• Navigated within the Integration Suite Welcome page to Design → Integrations → DelayedDelivery_Package_randomNumber → DelayedDelivery_Process.
• Following the status after the last exercise step.

2. Created and configured a General Splitter.

Got a General Splitter from Routing → Splitter → General Splitter and placed it after the Modify_setPayload component, as described.

• Expanded the General Splitter configuration and changed the name to Splitter_iterateOverProducts.

• Switched to tab Processing and entered the following data:

Table 11: Processing tab data for the splitter

• The element was used in the product list to encapsulate the productIDs. With grouping set to 1, each productID will be processed sequentially.

3. Saved as version, deployed, and debugged the integration process.

i. Performed the following steps.

• Save as version.
• Deploy.
• Jumped to the Overview → Manage Integration Content.
• Set log level to trace.
• Deployed again.
• Jumped again to the Overview → Manage Integration Content.

ii. Navigated to the Integration Flow Model in Overview → Monitor Message Processing → Message Processing Run.

• Chose the Splitter_iterateOverProducts (No. 1:) option and went to the Message Content tab. I was able to view the payload from the previous step, which included three products.

• At No. 2 and No. 3, noticed that the message was being processed twice. I checked the payload at the first End to see the first single product.

• Chose the last End step to see the third product.

• In summary, the General Splitter functioned as expected.

Conclusion

I was able to create and configure a general splitter which is required to process every productID of the incoming list.

Next Article ?

To further expand the integration process, I will create and configure a Content Modifier for the ProductID. This is needed to store the currently processed productID as an Exchange Property for subsequent steps, for each loop.

Previous Article ?

Creating a Content Modifier with Payload (XML)

Thanks for reading !

Reference

SAP (2025). SAP Cloud Integration

SAP (2024). Developing with SAP Integration Suite

? 2024 SAP SE or an SAP affiliate company. All rights reserved. This article references SAP materials for educational purposes, in accordance with SAP's copyright guidelines.