C_S4EWM Extended Warehouse Management Practice Question
A company wants to implement a cross-docking process in SAP EWM where received goods are directly transferred from inbound to outbound without putaway. Which prerequisite must be met to enable this process?
⚠ Common exam trap
The trap here is assuming that cross-docking is enabled solely by a process type setting, overlooking the need for a delivery relationship.
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
✓
The inbound delivery and outbound delivery must be linked via a cross-docking relationship.
Cross-docking in SAP EWM requires a direct link between inbound and outbound deliveries to bypass putaway. This link is established through cross-docking relationships, such as assigning a common cross-docking identifier or using a decision function. Without this connection, the system cannot determine that goods should flow directly to outbound, and they would be put away instead. Thus, the correct prerequisite is the delivery link.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The storage type for cross-docking must be configured as a picking storage type.
Why it's wrong here
Cross-docking uses a dedicated storage type, often called a cross-docking storage type, which is configured to allow goods to be moved directly from inbound to outbound. It is not a picking storage type; picking storage types are for regular outbound picking. Configuring it as a picking storage type would conflict with the cross-docking process and likely cause errors in stock movement and availability.
- ✗
The warehouse process type for putaway must be set to 'Cross-Docking'.
Why it's wrong here
While a warehouse process type is involved, it is not simply set to 'Cross-Docking'. Instead, a specific warehouse process type for cross-docking is used, and it is determined based on the cross-docking decision. Simply setting a standard putaway process type to cross-docking is not sufficient; the system must recognize the cross-docking scenario through the delivery link and other configurations.
- ✓
The inbound delivery and outbound delivery must be linked via a cross-docking relationship.
Why this is correct
For cross-docking in SAP EWM, a relationship must be established between the inbound and outbound deliveries to ensure the goods flow directly from receipt to shipping. This is typically done by assigning the same cross-docking identifier or by using a cross-docking decision. Without this link, the system would treat the processes independently and default to putaway, defeating the purpose of cross-docking.
- ✗
The outbound delivery must be created before the inbound delivery is posted.
Why it's wrong here
The sequence of delivery creation can vary. In many cross-docking scenarios, the outbound delivery may be created after the inbound delivery, especially if the outbound demand is known later. The key is not the creation sequence but the existence of a link between the deliveries. Requiring the outbound delivery first would be overly restrictive and not a standard prerequisite.
About these practice questions
This C_S4EWM question is part of Courseiva's 217-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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_S4EWM 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_S4EWM exam.