C_CPI Integration Suite Development Practice Question
An integration developer is configuring a Message Mapping in SAP Cloud Integration to transform a source XML payload into a target XML structure. The source contains a repeating node called 'Items' with multiple 'Item' elements, and the target requires a flat list of 'Product' elements under a 'Products' root. The developer needs to ensure that each 'Item' is mapped to a separate 'Product' element. Which mapping technique should be used?
⚠ Common exam trap
Watch out — candidates often confuse context change with one-to-many functions or value mappings, which are used for different purposes and do not handle iteration over repeating nodes.
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
✓
Use a one-to-one mapping with a context change to iterate over the 'Item' nodes and map each to a 'Product' element.
To transform a repeating source node into a flat list of target elements, a context change is required in the Message Mapping. This allows the mapping logic to be applied to each occurrence of the repeating node, generating one target element per source occurrence. Other techniques like concatenation or value mapping do not achieve the required structural transformation.
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 user-defined function that concatenates all 'Item' values into a single 'Product' element.
Why it's wrong here
Concatenating all items into one product element would not create separate product elements for each item, violating the target structure. The requirement is to produce a flat list where each item becomes its own product, not a single combined value.
- ✗
Use a standard mapping with a one-to-many function to split the 'Items' node into multiple 'Product' elements.
Why it's wrong here
A one-to-many function can split a single source field into multiple target fields, but it does not automatically iterate over repeating nodes. Without a context change, the mapping would not correctly process each 'Item' occurrence, leading to incorrect output.
- ✓
Use a one-to-one mapping with a context change to iterate over the 'Item' nodes and map each to a 'Product' element.
Why this is correct
A context change in the Message Mapping allows the mapping to process each occurrence of the 'Item' node individually, creating a separate 'Product' element for each. This is the standard approach for converting repeating structures into a flat list in SAP Cloud Integration.
- ✗
Use a value mapping to map each 'Item' to a 'Product' element based on a lookup table.
Why it's wrong here
Value mapping is used for translating codes or values, not for restructuring repeating nodes into a flat list. It does not handle the iteration or context change needed to create multiple target elements from a repeating source node.
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.