C_CPI Integration Suite Development Practice Question
An integration developer is building an integration flow that must transform an incoming XML message into a flat CSV file for an SFTP receiver. The transformation logic is complex and cannot be achieved with standard mapping functions alone. Which step should the developer use?
⚠ Common exam trap
The trap here is assuming that any transformation must be done in a Message Mapping step, when complex or non-XML output often requires a script.
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
✓
A Groovy Script step that reads the XML payload and writes the CSV content.
Complex transformation logic that produces a flat CSV file is best handled with a Groovy Script step, which allows full procedural control over parsing XML and generating the CSV output. Standard mapping, XSLT, and Content Modifier steps are less suited to this specific task.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A Message Mapping step with a User-Defined Function that builds the CSV string.
Why it's wrong here
A Message Mapping step can include User-Defined Functions, but it is designed for structured XML-to-XML or XML-to-JSON transformations. Producing a flat CSV file with custom delimiters and line breaks is awkward and error-prone in Message Mapping. While possible in some cases, it is not the most suitable step for complex flat-file generation.
- ✗
A Content Modifier step that sets the body to a CSV template with placeholders.
Why it's wrong here
A Content Modifier can set or modify headers, properties, and the body, but it does not parse the incoming XML or dynamically generate rows based on the source data. It is useful for static or simple substitutions, not for complex transformation logic. It cannot produce a variable CSV structure from arbitrary XML input.
- ✓
A Groovy Script step that reads the XML payload and writes the CSV content.
Why this is correct
A Groovy Script step gives full programmatic control over the payload, so the developer can parse the XML and construct a CSV string with the required delimiters, quoting, and line endings. This is the appropriate choice when transformation logic is too complex for standard mapping functions and the target is a flat file rather than structured XML.
- ✗
An XSLT Mapping step that applies a stylesheet to convert XML to CSV.
Why it's wrong here
XSLT is powerful for XML transformations, but generating CSV from XSLT requires careful handling of text output, escaping, and line breaks. It is possible but not the most natural fit for complex flat-file generation, and it lacks the procedural flexibility of a script. The scenario calls for complex logic, which is better served by a scripting step.
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.