Where can you configure a static payload?

A static payload is fixed content (e.g., XML/JSON) set during iFlow design. Let’s locate where this is possible:

Step 1: Static Payload Concept- It’s predefined data, not dynamically fetched or altered.

Step 2: Evaluate Options-

A. Content Modifier (Message Body tab): Set a static payload (e.g., test) in the "Message Body" tab with "Constant" source type.

B. Groovy script: Use message.setBody('test') to assign a static payload programmatically.

C. General Splitter: Splits existing payloads, doesn’t configure them.

D. OData adapter: Configures connectivity, not static content.

Step 3: Practical Use- Content Modifier is for design-time static data; Groovy offers runtime flexibility.

Step 4: Official Verification- The SAP Help Portal’s "Defining Content Modifier" and "Defining Groovy Scripts" confirm these components for static payload configuration.

Conclusion: Options A and B are 100% verified per SAP documentation.References:

SAP Help Portal: "Defining Content Modifier" (SAP Cloud Integration)

SAP Help Portal: "Defining Groovy Scripts"