Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An integration message carries content plus supporting information. A header may travel with a message, while a process property can hold information used inside a flow; each component’s behavior matters.

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 Cloud Integration header versus exchange property: Choose by message scope
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 message headers, bodies and exchange properties. Adapter-specific handling and external header restrictions remain scenario dependent.

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

Preserve meaning across a supplier-message flow

Inside the flow or sent outside?

Business value: Order reference 1001. Flow property: Available inside processing. Outbound header: Transport-dependent. Receiver evidence: Inspect the actual request
What to notice: A value held by one integration step may not automatically cross the receiver boundary.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Business value
Order reference 1001
Flow property
Available inside processing
Outbound header
Transport-dependent
Receiver evidence
Inspect the actual request
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.
HTTP
The request-and-response protocol used by web applications and APIs.
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.

Message content → Header or property → Receiver boundary. Conceptual diagram for Cloud Integration header versus exchange property: Choose by message scope.
Apply the idea: A manufacturer's supplier integration moves context through processing steps and an external receiver that do not all preserve headers and properties identically.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. Preserve meaning across a supplier-message flow

    A manufacturer's supplier integration moves context through processing steps and an external receiver that do not all preserve headers and properties identically.

  2. Choose storage by who should see the value

    Use an exchange property for temporary internal processing state and a message header when the supported receiver contract needs a header.

  3. Understand the exchange and message lifecycles

    A message has its body and headers, while the exchange provides a container for additional processing state.

  4. Worked case: route an order internally and publish one correlation value

    Imagine a flow receiving order ORD-1001 for sales area NORTH with quantity 4.

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.