Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A splitter divides one integration message into smaller messages. A gather step combines results; error handling determines what happens when only one part fails.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Business Technology Platform, or BTP, provides cloud services for applications, data and integration. A connection needs a route, an identity and permission to perform the intended task.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for Integration Suite splitter and gather: Plan ordering and failure handling
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP Cloud Integration splitter/gather error-handling patterns. Stop-on-exception and exception-subprocess behavior must be checked for the specific flow and runtime.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Keep partial supplier-message failures visible

One part fails, others differ

Original payload: Three order items. Item A: Processed. Item B: Rejected. Item C: Processed
What to notice: The aggregate response must preserve the relevant individual outcomes and configured failure semantics.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Original payload
Three order items
Item A
Processed
Item B
Rejected
Item C
Processed
Words you’ll meet in this guide
Backend
The service or system doing the work behind an interface.
Destination
Named connection settings for another service.
Credential
Access information used to prove an identity.
Subaccount
A BTP scope for applications, services and access settings.
XML
A format that organizes data into named, nested elements.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Original message → Split processing → Gathered result and errors. Conceptual diagram for Integration Suite splitter and gather: Plan ordering and failure handling.
Apply the idea: A manufacturer's integration splits a supplier payload into several items and needs to understand which branch failed and what the gathered result represents.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Keep partial supplier-message failures visible

    A manufacturer's integration splits a supplier payload into several items and needs to understand which branch failed and what the gathered result represents.

  2. Define the bulk outcome before configuring the splitter

    A splitter turns one composite message into smaller processing units; Gather combines their results.

  3. Treat item identity, execution order and output order separately

    Every item needs a stable identity within its parent.

  4. Worked case: three price lines, one invalid value

    Imagine purchase order PO-900 with items 10, 20 and 30.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.