C_S4EWM_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Extended Warehouse Management Questions and Answers

Comprehensive and Detailed In-Depth Explanation:

Tailored measurement services in SAP EWM are custom metrics for monitoring. Option A ("They use basic measurement services for the key figures") is correct because they build on predefined basic services, extended via configuration in SPRO: SCM Extended Warehouse Management > Monitoring > Define Tailored Measurement Services. Option D ("They can be displayed in the graphical warehouse layout") is correct as they integrate with visualization tools like the graphical warehouse layout. Option B relates to SAP BW, not EWM directly, and option C is incorrect as tailored services are not based on calculated services but are custom-built.

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:

Direct outbound delivery orders (ODOs) in SAP EWM bypass ERP delivery creation. Option B ("Issue to cost center") is correct for internal consumption, option D ("Scrapping") is correct for stock disposal, and option E ("Direct sales") is correct for immediate sales, all initiated via transaction /SCWM/DIRO or SPRO: SCM Extended Warehouse Management > Goods Issue Process > Direct Outbound Delivery. Option A (Kanban) and option C (replenishment) are internal processes, not direct ODOs.

Comprehensive and Detailed In-Depth Explanation:

For a new EWM document type in an inbound process, integration with SAP ERP is critical. Option C ("Define the SAP ERP document type mapping to the delivery document type") is correct because you must map the ERP document type (e.g., "EL" for inbound delivery) to the EWM document type in SPRO: SCM Extended Warehouse Management > Interfaces > ERP Integration > Map Document Types. Options A, B, and D are either predefined (document category) or not mandatory (item type, delivery type determination) for basic inbound setup.

Comprehensive and Detailed In-Depth Explanation:

Explicit counting in the Quality Inspection Engine (QIE) in SAP EWM involves a deliberate count of stock during an inspection, often triggered by quality requirements. Option B ("Sampling procedure") is correct because it defines how many items are inspected (e.g., percentage or fixed number), configured in the quality management (QM) system and linked to EWM. Option C ("Inspection rule") is correct as it specifies the inspection process, including whether explicit counting is required, and is maintained in EWM under SPRO: SCM Extended Warehouse Management > Quality Management > Inspection Rules. Work center (A) is relevant for production processes, not QIE counting, and QM integration (D) is a prerequisite for QIE but not a direct requirement for explicit counting itself.

Comprehensive and Detailed In-Depth Explanation:

The Notification of Expected Goods Receipt (EGR) in SAP EWM anticipates incoming stock. Option C ("Purchase Order") is correct as it’s a common reference for external procurement EGRs, and option D ("Production Order") is correct for production-related EGRs, both configured in SPRO: SCM Extended Warehouse Management > Goods Receipt Process > Expected Goods Receipt. Option A (Inbound Delivery) is a downstream document, and option B (Sales Order) is outbound-related.

Comprehensive and Detailed In-Depth Explanation:

For batch-managed materials, the batch must exist before processing begins. Option A ("Before the inbound delivery is distributed from SAP ERP to SAP EWM") is correct because the batch is created in ERP (e.g., via MIGO or material master) and included in the inbound delivery before distribution to EWM via qRFC. Options B, C, and D occur too late in the process as the batch must already be specified in the inbound delivery.

Comprehensive and Detailed In-Depth Explanation:

A VAS order in SAP EWM supports additional services during processing. Option A ("Assemble a kit") is correct as kitting is a common VAS activity. Option B ("Consume auxiliary products") is correct because VAS often uses materials like packaging, and option D ("Capture time required") is correct as Labor Management tracks VAS execution time, all configured in SPRO: SCM Extended Warehouse Management > Value-Added Services. Option C (quality inspection) is a separate QM process, and option E (costs) is tracked indirectly, not directly via VAS orders.

Comprehensive and Detailed In-Depth Explanation:

Stock in SAP EWM is assigned ownership attributes. Option B ("Owner") is correct as it identifies the stock’s legal owner (e.g., company), and option D ("Party entitled to dispose") is correct because it specifies who can manage the stock (e.g., a customer), both maintained in the product master and stock data. Option A (resource) is temporary during handling, and option C (shipping point) is ERP-specific, not EWM stock assignment.

Comprehensive and Detailed In-Depth Explanation:

In decentralized EWM, some document categories can be bypassed, but option A ("An outbound delivery order and an outbound delivery") is mandatory because the outbound delivery order (ODO) is created in EWM from an ERP outbound delivery request, and the outbound delivery is completed after processing, configured in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Outbound Delivery. Other combinations (B, C, D) can be optional or situational.

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:

Creating warehouse tasks in SAP EWM requires foundational configuration. Option B ("Warehouse process type determination") is correct because it defines how the system assigns a process type (e.g., putaway, picking) to a delivery item, configured in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Warehouse Task > Define Warehouse Process Type Determination. Option D ("Warehouse process types") is correct as it specifies the process flow (e.g., "PICK" for picking), set up in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Warehouse Task > Define Warehouse Process Type. Option A (indicators) influences task execution but isn’t a prerequisite for creation, and option C (order creation rules) applies to warehouse orders, not tasks directly.

Comprehensive and Detailed In-Depth Explanation:

Packing profiles in SAP EWM control pick-HU creation. Option B ("Consider length, width, and height") is correct for dimensional checks, option C ("Use a simple algorithm, a complex algorithm, or a BAdI") is correct as it offers packing logic options, and option D ("Limit the number of items") is correct for capacity control, all configured in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Packing > Define Packing Profile. Option A (split task) and option E (delivery items) are not standard profile features.

Comprehensive and Detailed In-Depth Explanation:

The early capacity check in SAP EWM ensures bins can accommodate stock before task execution. Option C ("It happens during the warehouse task creation") is correct as it occurs when tasks are generated, and option D ("It is based on capacities of bin types") is correct because it uses bin type capacity data, both configured in SPRO: SCM Extended Warehouse Management > Goods Receipt Process > Capacity Check. Option A (mobile devices) is incorrect as it’s not device-specific, and option B (during putaway) is too late for an “early” check.

Comprehensive and Detailed In-Depth Explanation:

Mobile devices enhance physical inventory in SAP EWM. Option A ("You can use collective counting for bulk storage") is correct because RF devices support collective counting, allowing multiple bins to be counted together, configured via transaction /SCWM/RFUI. Option D ("It is optional to block bins") is correct as mobile counting allows flexibility in bin blocking, unlike desktop processes where blocking may be mandatory, set in SPRO: SCM Extended Warehouse Management > Physical Inventory > RF Settings. Option B is incorrect as recounting may still be needed, and option C (SAP Fiori app) is not standard for EWM PI.

Comprehensive and Detailed In-Depth Explanation:

In SAP EWM, resources (e.g., forklifts, workers) are assigned attributes for task execution. Option A ("Resource type") is correct as it defines the resource’s capabilities (e.g., forklift), and option C ("Resource group") is correct because it groups resources for assignment rules, both configured in SPRO: SCM Extended Warehouse Management > Resource Management > Define Resource Type and Define Resource Group. Option B (bin access type) is bin-related, and option D (handling unit type) is HU-specific, neither directly assigned to resources.

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:

Evaluation points in SAP EWM are used within the resource management framework to prioritize and assign warehouse orders to resources (e.g., warehouse workers or equipment). Option A ("Influence which warehouse order is assigned to a resource") is correct because evaluation points are calculated based on factors like order urgency, resource proximity, or queue assignment, configured in SPRO: SCM Extended Warehouse Management > Resource Management > Define Evaluation Points. This influences the system’s decision on resource allocation. Option B is incorrect as item picking sequence is determined by picking strategies (e.g., FIFO), not evaluation points. Option C relates to storage type search sequences, not evaluation points. Option D is a broader warehouse efficiency goal but not adirect function of evaluation points.

Comprehensive and Detailed In-Depth Explanation:

Process-oriented storage control (POSC) in SAP EWM manages complex warehouse processes with rule-based determination. Option B ("To determine the destination storage bin") is correct because POSC uses rules to dynamically assign bins for steps like putaway, configured in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Process-Oriented Storage Control > Define Storage Process. Options A, C, and D (WOCR, source bin, process type) are determined by other mechanisms like warehouse process types or stock removal strategies, not POSC rule-based logic.

Comprehensive and Detailed In-Depth Explanation:

External exception codes in SAP EWM handle deviations. Option B ("A business context") is correct as it defines where the code applies (e.g., picking), and option C ("An internal exception code") is correct because it maps the external code to an internal action, both configured in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Exception Handling > Define Exception Codes. Option A (workflow) is optional, and option D (execution step) is not a standard assignment.

Comprehensive and Detailed In-Depth Explanation:

Semi-system-guided processing in SAP EWM (via RF, e.g., /SCWM/RFUI) provides flexibility. Option A ("Select the warehouse order to be processed") is correct as users can choose from a list of orders, configured in SPRO: SCM Extended Warehouse Management > Mobile Data Entry > Define Semi-System-Guided Processing. Options B, C, and D are either system-driven or not standard in this mode.