C_CPI Integration Suite Development Practice Question
An integration developer is configuring a Message Mapping in SAP Cloud Integration. The target structure requires an element named CustomerSegment that must be populated from a source field called Tier, but the mapping must also preserve any whitespace-insensitive value and strip surrounding spaces before assignment. Which step should the developer add in the mapping to achieve this?
⚠ Common exam trap
The trap here is assuming that any string-handling step applied near the mapping will automatically affect the specific field, when only functions wired directly between source and target fields normalize that value.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a standard function and select trim before assigning the source field to the target element.
The trim standard function is the purpose-built mapping function for removing leading and trailing whitespace from a string. Applying it to the Tier source field before it is assigned to CustomerSegment normalizes the value exactly as required. Other approaches either do not target the field, operate outside the mapping context, or unnecessarily post-process the entire message.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a Content Modifier step before the mapping to set a property with the trimmed value.
Why it's wrong here
A Content Modifier operates on message headers, properties, and the body before or after mapping, but it cannot reference individual source fields inside a mapping structure. Trimming a specific field such as Tier must happen within the mapping itself, so placing the logic in a Content Modifier would not target the correct value.
- ✗
Configure a Groovy script step after the mapping that removes whitespace from the target payload.
Why it's wrong here
A Groovy script placed after the mapping could post-process the resulting XML, but it adds unnecessary complexity and operates on the whole payload rather than the specific field. The mapping already provides a dedicated standard function for trimming strings, so introducing a script step is not the appropriate or efficient solution here.
- ✗
Add an ifWithoutElse standard function and map Tier directly to CustomerSegment.
Why it's wrong here
ifWithoutElse is a conditional function that evaluates a boolean expression and returns a value only when a condition is true; it does not perform any string normalization. Mapping Tier directly through it would pass the original value unchanged, including any leading or trailing spaces, so the whitespace requirement would not be met.
- ✓
Add a standard function and select trim before assigning the source field to the target element.
Why this is correct
The trim standard function removes leading and trailing whitespace from a string value during message mapping. Applying it between the source Tier field and the target CustomerSegment element ensures the assigned value is normalized without altering internal characters, which satisfies the requirement to strip surrounding spaces while preserving the value's core content.
About these practice questions
One of 218 original C_CPI practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official SAP exam blueprint
This C_CPI practice question is part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C_CPI exam.