Free SAP C_S4EWM_2023 Practice Exam with Questions & Answers | Set: 2

Comprehensive and Detailed In-Depth Explanation:

Hotspots in the SAP EWM warehouse management monitor (/SCWM/MON) are interactive links on objects (e.g., warehouse tasks, bins). Option A ("Call the corresponding user interface on the selected object") is correct because clicking a hotspot navigates to the detailed UI for that object (e.g., warehouse task details). Options B, C, and D are incorrect: methods are executed via actions, not hotspots (B); view changes are manual (C); and measurement services are configured separately (D).

Comprehensive and Detailed In-Depth Explanation:

Replication of delivery documents from SAP ERP to EWM relies on integration methods. Option C ("Distribution via Post Processing Framework (PPF) actions") is correct because PPF actions in ERP trigger the creation and transfer of delivery documents to EWM, configured in SPRO: Logistics Execution > Extended Warehouse Management Integration > PPF Actions. Option D ("Immediate distribution at document creation") is correct as it allows real-time replication upon saving the delivery in ERP via qRFC, set up in the output control. CIF (A) is used for master data, not deliveries, and manual distribution (B) is not a standard automated method in EWM integration.

Comprehensive and Detailed In-Depth Explanation:

Waves in SAP EWM group outbound tasks for processing. Option B ("Automatically when an outbound delivery order is created") is correct because wave templates with an "Automatic" release method can trigger wave creation upon ODO creation, configured in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Wave Management > Define Wave Templates. Option D ("Manually during planning in the shipping cockpit") is correct as users can manually create waves in transaction /SCWM/SHCO. Option A (warehouse task) is a downstream step, and option C (PMR) is production-related, not wave-specific.

Comprehensive and Detailed In-Depth Explanation:

In a direct outbound delivery scenario in SAP EWM, the process bypasses ERP delivery creation, but if ERP is involved, option C ("Outbound delivery") is correct. It’s created in ERP (e.g., via VL01N) and distributed to EWM as an outbound delivery order, configured in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Outbound Delivery. Options A (purchase order) and B (inbound delivery) are inbound-related, and option D (sales order) is a preceding document, not the direct result.

Comprehensive and Detailed In-Depth Explanation:

Warehouse order sorting for resource assignment in SAP EWM uses priority criteria. Option A ("By latest starting date") is correct as it ensures timely execution, and option D ("By execution priority") is correct because priority levels (e.g., high, low) influence assignment, both set in SPRO: SCM Extended Warehouse Management > Resource Management > Define Sort Rules. Option B (utilization) and option C (mode) are not standard sorting parameters.

Comprehensive and Detailed In-Depth Explanation:

Yard management in SAP EWM manages vehicle movements. Option B ("Define a storage type for a yard in one of the warehouse numbers, and connect the yard with doors to the other warehouse number") is correct because a single yard storage type (e.g., "YARD") is defined in one warehouse number, and doors link it to the other, configured in SPRO: SCM Extended Warehouse Management > Yard Management > Define Yard Storage Type. Options A, C, and D overcomplicate the setup with unnecessary duplication or incorrect connections (e.g., checkpoints, parking spaces).

Comprehensive and Detailed In-Depth Explanation:

In embedded EWM within SAP S/4HANA Cloud, Private Edition, goods receipt (GR) for external procurement can be posted using two primary methods. Option B ("Use the ERP Inbound Delivery to post goods receipt") is correct because the ERP inbound delivery (created in SAP ERP/S/4HANA MM) serves as the reference document, which is then replicated to EWM for warehouse processing. Option C ("Use the EWM Inbound Delivery to post goods receipt") is also correct because the inbound delivery in EWM, derived from the ERP document, is where the actual GR is confirmed and posted back to ERP via integration. Synchronous GR (options A and D) is not a standard feature in embedded EWM for external procurement, as the process relies on asynchronous communication between ERP and EWM via queued remote function calls (qRFC). The GR posting is finalized in ERP based on EWM confirmation, ensuring inventory alignment.

Comprehensive and Detailed In-Depth Explanation:

Replenishment in SAP EWM moves stock from reserve to picking areas. Option A ("Storage type") is correct because the replenishment method (e.g., automatic, planned) is assigned to a storage type in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Replenishment > Define Replenishment Control per Storage Type. This determines how replenishment is triggered for that area. Options B, C, and D (document-related or process type) are not directly linked to replenishment method assignment.

Comprehensive and Detailed In-Depth Explanation:

To streamline configuration, SAP EWM allows grouping process types. Option A ("Process type group") is correct because it enables multiple process types to share a single storage type search sequence, defined in SPRO: SCM Extended Warehouse Management > Goods Receipt Process > Define Process Type Group. Options B, C, and D (putaway control indicator, storage type group, stock type group) serve other purposes like putaway rules or stock categorization, not process type grouping for search sequences.

Comprehensive and Detailed In-Depth Explanation:

The business system in EWM integration represents the source or target system (e.g., ERP) in the landscape. Option A ("It is connected to a logical system…") is correct because it links to a logical system via RFC, and warehouse requests store the business system for tracking, configured in SPRO: SCM Extended Warehouse Management > Interfaces > Define Business System. Option C ("It can be used to separate materials…") is correct as it differentiates stock origins in multi-system scenarios. Option B is incorrect because RFC parameters are defined separately, and option D is handled by document type mapping, not the business system itself.