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:

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 a direct function of evaluation points.

Comprehensive and Detailed In-Depth Explanation:

External process steps in SAP EWM’s process-oriented storage control (POSC) are assigned to objects defining the process flow. Option B ("Warehouse process type") is correct as it links external steps (e.g., VAS) to the process, and option D ("Work center") is correct because it’s where external steps are executed, both configured in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Process-Oriented Storage Control. Options A and C are not standard assignment objects for external steps.

Comprehensive and Detailed In-Depth Explanation:

Engineered Labor Standards (ELS) in SAP EWM Labor Management measure task execution times. Option D ("To define the times that are required to execute an activity in the warehouse") is correct, as ELS calculates standard times for activities (e.g., picking), configured in SPRO: SCM Extended Warehouse Management > Labor Management > Engineered Labor Standards. Options A, B, and C relate to resource assignment, travel, or wave planning, not ELS’s primary purpose.

Comprehensive and Detailed In-Depth Explanation:

Yard Management in SAP EWM tracks vehicle movements. Option A ("Doors") is correct as they connect the yard to the warehouse, and option B ("Vehicles") is correct as they are the objects managed, both configured in SPRO: SCM Extended Warehouse Management > Yard Management. Option C (resources) is warehouse-specific, and option D (checkpoints) is optional, not mandatory.

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:

SAP Signavio supports process modeling. Option C ("SAP Signavio Process Manager") is correct because it’s the tool for designing and creating workflows, used in S/4HANA brownfield projects to align with clean core principles. Options A and B focus on analysis, and option D is for governance, not workflow creation.

Comprehensive and Detailed In-Depth Explanation:

Exception codes in RF transactions (e.g., /SCWM/RFUI) trigger background actions. Option B ("Trigger replenishment") is correct as it can initiate stock replenishment, configured in SPRO: SCM Extended Warehouse Management > Cross-Process Settings > Exception Handling. Option C ("Block a bin") is correct because it can lock a bin due to issues. Option E ("Generate workflow process") is correct as it can start a workflow for resolution. Option A (cancel PI document) and D (confirm order) are not standard background functions for exception codes.

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.

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 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:

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:

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:

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:

Automatic assignment of warehouse orders to resources in SAP EWM requires queue linkage. Option C ("The warehouse order must be in a queue that is assigned to the resource either directly or through a resource group") is correct, as queues connect orders to resources, configured in SPRO: SCM Extended Warehouse Management > Resource Management > Assign Queues. Option B is a supporting factor but not the prerequisite, while options A and D are not mandatory conditions.

Comprehensive and Detailed In-Depth Explanation:

Separate storage locations in SAP EWM (mapped from ERP) manage stock purposes. Option D ("Distinguish material that is supplied for production from material which is available for sales") is correct because storage locations can segregate production stock (e.g., “PROD”) from sales stock (e.g., “SALE”), configured via warehouse number mapping in SPRO: SCM Extended Warehouse Management > Interfaces > ERP Integration. Options A, B, and C are managed by stock types or processes, not storage locations.

Comprehensive and Detailed In-Depth Explanation:

Advanced transportation planning integration in SAP EWM offers flexibility. Option C ("Transportation planning always starts in EWM") is correct because it allows EWM to initiate planning, unlike basic integration where ERP drives it, configured in SPRO: SCM Extended Warehouse Management > Transportation Management. Options A, B, and D are incorrect as deliveries are still needed, vehicles are optional, and TUs are typically required.

Comprehensive and Detailed In-Depth Explanation:

Automatic wave creation in SAP EWM groups outbound tasks. Option C ("Wave templates with release method 'Automatic'") is correct as it triggers wave creation automatically, and option D ("Conditions and condition records exist") is correct because conditions (e.g., time, volume) determine when waves are created, both configured in SPRO: SCM Extended Warehouse Management > Goods Issue Process > Wave Management. Option A (job) is for release, not creation, and option B is too vague.

Comprehensive and Detailed In-Depth Explanation:

A warehouse order in SAP EWM is a collection of tasks grouped for execution. Option B ("Warehouse tasks") is correct because a warehouse order always contains one or more tasks (e.g., picking, putaway), created based on warehouse requests. Option D ("Physical inventory items") is correct as warehouse orders can include tasks for physical inventory counts, configured via SPRO: SCM Extended Warehouse Management > Physical Inventory. Option A ("Warehouse requests") is incorrect because requests are the source for tasks, not part of the order itself. Option C ("Wave items") relates to wave management, not directly to warehouse orders.

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.