This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Thursday, March 27, 2025

Q&A in Class (2025-03-28) EWM100

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Is this possible to have S/4HANA integrated to distributed S/4HANA with TM and also integrated to another distributed S/4HANA with EWM ?

Answer: The option for Distributed EWM and Distributed TM seemed to be possible according to Experts on SAP Community. ALSO for the case if the Distributed TM system and Distributed EWM are also on different server Platforms. 

Check the Blog Posts are some of the detail findings:
https://froggysap.blogspot.com/2025/03/blog-post_24.html

Recommendations: It is best to approach SAP for Distributed EWM and Distributed TM for the BEST deployment options, upgradeability and technical difficulties if "Tight integration" between EWM and TM is expected if different S/4HANA versions.  

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: In the context of EWM, what is the difference between Stowage Type Role "D" (Staging Area Group) and Storage Type Role "K" (Production Supply) ?

Answer: It is a common practice to use Storage Type Role "K" (Production Supply) for EWM Storage Types designed as Production Supply Area (ie: Staging location for Backflushing from Production Order). In the context of SAP Extended Warehouse Management (EWM), a Production Supply Area (PSA), which corresponds to a storage type role "K" (Production Supply), is used for staging materials for production, while a staging area group (storage type role "D") serves as an interim storage area for goods before further processing, such as loading or unloading. 

  • Storage Type Role "K" is "interim" storage area before Backflush (GI) to the Production Order.
  • Storage Type Role "D" is "interim" storage area as GR Area to MM Purchase Order Inbound Delivery before Final Putaway.
  • Storage Type Role "D" can also be "interim" storage area as GI Area to SD Outbound Delivery before Final Post Goods Issue.

Production Supply Area (PSA):

  • Definition: A PSA is a specific area within a plant or warehouse where materials are staged before they are used in production.
  • Purpose: It acts as a buffer zone, ensuring materials are readily available at the right time and place for production.
  • Function: PSAs are linked to storage locations in Warehouse Management (WM) and are defined in SAP using transaction code PK05.
  • Example: Imagine a factory floor where raw materials are stored in a central warehouse. The PSA would be a designated area on the floor where those materials are moved to, ready for use by a specific production line.
  • Configuration: 
  • You define PSAs in SAP using transaction code PK05, linking them to storage locations and work centers. 

Staging Area Group "D"
  • Definition: This is the Interim Storage Type for GR to PO and Interim Storage Type for GI Area to the Outbound Delivery. 
  • Purpose: The Interim before final Putaway and Interim before final PGI.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is Data Management and Landscape Transformation (DMLT) and is the "Migration Cockpit" the same thing ?

Answer: SAP Data Management & Landscape Transformation (DMLT) is a Collection of Services provided by SAP for data migration, while the "Migration Cockpit" is a tool within SAP used for managing data migration processes, but they are not the same thing. The "Migration Cockpit"is a tool (Fiori App) that can be used as part of the DMLT services, The Migration Cockpit can be accessed through the Fiori Launchpad

SAP Data Management & Landscape Transformation (DMLT): 
  • DMLT is a broader set of services that helps businesses manage their data and transform their IT landscapes, particularly when migrating to SAP S/4HANA or other SAP systems.
  • DMLT focuses on data migration, data quality, data integration, and ensuring a smooth transition to a new or updated SAP system. 
  • Examples of DMLT services but not limited to the following:
    • Data Migration: Moving data from legacy systems to SAP S/4HANA. 
    • Data Transformation: Converting data formats and structures to match the new system. 
    • Data Cleansing: Identifying and correcting errors and inconsistencies in the data. 
    • Data Validation: Ensuring the accuracy and completeness of the migrated data. 
    • Data Privacy and Compliance: Helping organizations meet data protection regulations. 
    • Landscape Optimization: Optimizing the IT infrastructure to support the new system. 
    • Process Redesign: Supporting business process redesign during the migration to SAP S/4HANA. 
SAP S/4HANA Migration Cockpit:
  • The Migration Cockpit is a tool within the SAP system that helps users manage the data migration process.
  • It provides a user-friendly interface for uploading, validating, and cleansing data before loading it into the SAP system.
  • Features:
    • Supports data migration from various sources, including legacy systems and external data sources. 
    • Allows users to create migration projects and select migration objects. 
    • Provides different migration approaches, such as "Migrate Data Using Staging Tables
See the following Links:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What are the Technical setup for EWM RF ?


Answer: In SAP Extended Warehouse Management (EWM), the Radio Frequency (RF) framework enables warehouse operators to interact with the system wirelessly using mobile devices like handheld scanners, facilitating tasks like picking, put-away, and inventory management with real-time data capture and validation. 
SAP provide good enough documentation as a start for "Working with Mobile RF Devices":
https://help.sap.com/docs/SAP_EWM/Tech Documentation on Radio Frequency Frameworks

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Conversion Guide from ECC with WM to S/4HANA with EWM ?


Answer: There are some tools residing in the SPRO (Customizing) of S/4HANA system (see above) to help convert WM-customizing to EWM-customizing. However, none of these tools are Mandatory as eventually EWM works completely different from WM AND this is even so in a Brown Fields Project scenario.


There is also a Template EWM Warehouse "0001" in S/4HANA EWM Installed Based systems, which contain Template Storage Types, Storage Section, Bin Structure template, Storage Type Group, Activities Areas, Staging Areas etc. This Template Warehouse "0001" can be used to perform "Complex Copy" to the desired new EWM Warehouse, the copied dependent parameters can then be Fine-Tune based on individual EWM Warehouse Requirements. 

Request the Instructor of EWM100 class for the download of Documentations below: 
Migration of SAP ERP WM to SAP EWM

SAP Community and SAP Press etc for EWM experts sharing available via the following link:
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/Migration from LE-WM/b17a9fc66417486b07d70cd468c3b.html 
https://pages.community.sap.com/topics/extended-warehouse-management
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/Warehoue Product Migration/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: As we don't have any exercises on the Serial number for EWM, here is the following setup and demo for Materials with Serialization for EWM processing.


Answer: To use serial numbers in SAP Extended Warehouse Management (EWM), you need to determine a serial number profile for a product, assign it to the product master record, and then specify serial numbers during warehouse task creation or confirmation, depending on the chosen serial number requirement. 

Specific Scenarios:
  • Goods Receipt:
    • EWM copies the serial number from the ERP system and saves it when you make the goods receipt posting in the inbound delivery. 
  • Outbound Deliveries:
    • In EWM, you can work with predetermined serial numbers in outbound deliveries and posting changes. 
  • Printing Delivery Notes:
    • EWM automatically prints serial numbers with the delivery note of the corresponding delivery item. 
  • Monitoring:
    • To display serial numbers at warehouse number level, you can use the "Stock and Bin" functionality in the Warehouse Management Monitor. 
Using Serial Numbers in Warehouse Tasks:
  • Foreground Confirmation:
    • When confirming a warehouse task in the foreground, you can assign serial numbers manually from a list of predetermined serial numbers or by specifying them manually. 
  • Background Confirmation:
    • If confirming a warehouse task in the background, EWM automatically assigns the serial numbers known to the system, provided a complete quant removal occurs and the serial numbers are defined. 
  • Serial Number Ranges:
    • If EWM cannot display a list of serial numbers (e.g., for products with "Serial Numbers for Document Items" or "Serial Numbers at Warehouse Number Level" requirements), you can assign whole serial number ranges to a warehouse task. 
  • Handling Units:
    • If the inbound delivery contains Handling Unit (HU) data, you can change the serial number for the HU data. 
Prerequisites and Configuration:
  • Define Serial Number Profiles:
    • In the ERP system, define warehouse number-independent serial number profiles for EWM that are valid for all warehouses. 
  • Assign Profiles to Products:
    • Assign these profiles to the product master records in the ERP system using the procedure MMSL. 
  • Determine Serial Number Requirement:
    • Define which serial number requirement (serial numbers for document items, at warehouse number level, or in inventory management) EWM uses for each product. 
  • Settings in EWM:
    • In EWM Customizing, ensure the necessary settings are made for serial number management, such as defining work center layouts with the appropriate indicators for assigning serial numbers. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Re-visit the process flow for Batch Determination for Outbound Delivery with EWM scenario. 


Answer: See the following link to Blog Posts for the Outbound Delivery with Batch Determination:
https://froggysap.blogspot.com/2022/06/sap-scm-ewm-batch-determine-for-ewm.html

To perform batch determination for outbound deliveries in EWM, you need to configure batch management in SAP S/4HANA SD Batch Determination conditions: 
  • Batch Determination can be done in the ERP Outbound Delivery and the batch determined can then be transferred to the EWM Outbound Delivery Order for the Picking Warehouse Task. 
  • OR can also leverage the EWM integration to determine batches based on selection criteria sent from ERP, rather than assigning batches directly in ERP Outbound Delivery. 
  • In addition, two Business Add-Ins (BAdIs) are available for you to override the batch determination setting defined in Customizing for each storage location, and to change the batch selection criteria used in the batch determination to meet your individual requirements. For more information, see Customizing for Logistics Execution under SAP EWM Integration  Cross-Process Settings  Enhancements for Batch Management.
  • If you are using SAP Extended Warehouse Management (SAP EWM), you can determine batches directly in SAP EWM instead of using batch determination in SAP S/4HANA. Batch determination in SAP EWM takes into account the warehouse layout in SAP EWM (and can be of use, for example, when optimizing the picking process). In this case, SAP S/4HANA only transfers the characteristics as batch selection criteria to SAP EWM. (However, batch determination to take into account the warehouse layout will have to be simulated first confirm whether it does work). 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the relationship between Labor Management (LM) Processor and the EWM "Resource" ?

Answer: In SAP Extended Warehouse Management (EWM) Labor Management (LM), a Processor represents a warehouse employee, while an EWM Resource can be any asset used in warehouse operations (like RF device, forklifts, equipment, or even a specific storage location). 

Processor:
  • Represents a warehouse employee assigned as a business partner (BP) of type person. 
  • Used to map employees in the warehouse for labor management purposes. 
  • Allows for tracking and managing the performance and workload of individual employees. 
  • Essential for recording time effort and performance data. 
  • Can be created and maintained in the SAP system using the Business Partner function. 
  • The LM Processor is assigned to the SAP User (Warehouse Operation person which will be using the EWM Resource ie: the RF Gun). 
Resource:
  • Represents any asset used in warehouse operations, including RF device (RF Gun), Equipment,  Vehicles etc. 
  • Can be used in conjunction with Processors to track how resources are utilized by employees. In this case, the SAP User assigned to the LM Processor is also assigned to the EWM Resource (RF Gun). 
  • The Resource is used in conjunction with the Processors to track how resources are utilized by the Employees (SAP User) who can use the RF Device (RF Gun) to record WT/WO Confirmation and the Labor Time entries. 
  • Combining LM's Processor and EWM Resource can be used to optimize resource allocation and improve warehouse efficiency by evaluating the KPI of Planned Time from LM to the Actual Time recorded by the Resource assigned to the SAP User. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review of Production Supply with ECC or S4HANA Backend TO Distributed S/4HANA EWM Process Flow as below diagram:

Answer: In SAP S/4HANA with EWM, a Production Supply Area (PSA) is a designated area where materials are staged for production, acting as a bridge between the warehouse and the production line, and is defined and managed via transaction PK05. 

Setup and Configuration:
  • Define PSAs and Storage Location Mapping: 
    • Use transaction PK05 (Define Production Supply Areas) to create and maintain PSAs, linking them to specific storage locations and work centers (in ECC or S/4HANA Backend). 
    • Map storage locations to stock types in EWM. 
    • If using EWM, ensure that the storage location assigned to the PSA is managed by EWM or Inventory Management (MM-IM). 
  • Storage Type Role K: 
    • In the S/4HANA EWM, Assign storage bins created as part of the Storage Type type "K" (Production Supply) to a PSA (note: highly suggested to use the SAME PSA coding in ECC and S/4HANA EWM). 
  • Control Cycles: 
    • In the ECC system, define Control Cycles (using transaction LPK1) to manage replenishment of materials to the PSA, including details like the supply area, source storage location, and replenishment strategy ("Pick Part" for Staging and later Backflushing). 
  • Material Staging and Consumption:  
    • When staging materials for a production order, the system generates deliveries (via EWM Posting Change Document with a Warehouse Task) for stock transfers to the PSA.  
    • Consumption of materials from the PSA is triggered by the confirmation of the Production Order or Process Order or Repetitive Planned Order.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is Expected Goods Receipt for Production Order in EWM ?


Answer: In SAP Extended Warehouse Management (EWM), an Expected Goods Receipt (EGR) for a production order is a temporary document that EWM generates based on data from the production order in SAP ERP, acting as a template for creating inbound deliveries and facilitating goods receipt processing within EWM. 
  • Purpose:
    • EGRs allow EWM to anticipate the arrival of goods from production, enabling efficient warehouse planning and preparation for the goods receipt process. 
  • Functionality:
    • You can use the EGR as a template to create EWM inbound deliveries. 
    • You can adjust quantities and other details in the inbound delivery based on the EGR. 
    • EWM uses the EGR to calculate the expected workload for goods receipt. 
    • EWM posts the goods receipt and transmits the information to SAP ERP, which updates the stock in the production order and the inbound delivery. 
  • Production Order TO Temporary Document for Preparation of Production GR (EGR Document): 
    • When a production order is created in SAP ERP, EWM receives a notification and generates a corresponding EGR. 
    • EWM uses document type IDPD (Inbound Delivery from Production) to differentiate inbound deliveries created from EGRs. 
    • The EGR contains data from the production order, including planned quantities, materials, and expected times. 
    • EGRs are temporary documents and are deleted by EWM when no longer needed. 
    • You cannot change the data in the EGR itself; however, you can change the data in the related inbound delivery. 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review the Process Flow of Opportunistic Cross-Docking as below: 


Answer: In SAP Extended Warehouse Management (EWM), opportunistic cross-docking (OCD) is a strategy that allows goods to be moved directly from inbound to outbound docks, bypassing storage, when an opportunity arises, enhancing efficiency and reducing handling. 

Click here to review the Configuration and an example of Opportunistic Cross-Docking in S/4HANA Embedded EWM: 

How it works:
  • Inbound-Driven: 
    • The system checks if any outbound delivery order (ODO) items exist that match the inbound goods receipt (GR) items regarding quantity and expiration date. 
  • Outbound-Driven: 
    • The system checks if stock in the goods receipt staging area exists that is more adequate for the ODO item than stock from within the warehouse. 
Key Considerations:
  • Configuration: 
    • Requires careful configuration in EWM to define the cross-docking relevance based on warehouse process type, stock type, and product group. 
  • Integration: 
    • Requires seamless integration with inbound and outbound delivery processes. 
  • iF using EWM in SAP APO: 
    • SAP Advanced Planning & Optimization (SAP APO) defines whether an inbound delivery is PD-relevant or PFGR-relevant. 
  • iF using S/4HANA EWM-Triggered (Distributed or Embedded)
    • Opportunistic Cross-Docking This process takes place entirely within EWM, where the system determines if cross-docking is relevant when generating putaway or pick warehouse tasks. 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review the Principles of Yard Management in S/4HANA EWM system.


Answer: In SAP Extended Warehouse Management (EWM), yard management focuses on efficiently managing vehicle and transportation unit (TU) movements within the warehouse yard, including check-in/out, parking, and docking to doors for loading/unloading, all managed using warehouse tasks

Key Concepts:
  • Yard as an Extension of the Warehouse: EWM views the yard as an extension of the warehouse, managing movements within it using warehouse tasks. 
  • Checkpoints: Designated entry and exit points for vehicles and TUs. 
  • Parking Spaces: Temporary parking areas for vehicles when doors are unavailable. 
  • Doors: Where TUs arrive and are loaded/unloaded. 
  • Transportation Units (TUs): The containers or vehicles that carry goods. 
Key Processes:
  • Vehicle Check-in: When a vehicle arrives at the yard, it's checked in at a checkpoint.
  • Moving to Parking: If doors are occupied, the vehicle is moved to a designated parking space using a warehouse task.
  • Docking to Doors: When a door is available, the vehicle is moved to that door using a warehouse task to prepare for loading or unloading.
  • Unloading/Loading: Goods are loaded or unloaded from the TU at the door.
  • Moving to Checkpoint: After loading or unloading, the vehicle is moved back to the checkpoint for check-out.
  • Check-out: The vehicle is checked out of the yard at the checkpoint. 

How EWM Supports Yard Management:
  • Warehouse Tasks: EWM uses warehouse tasks to map movements within the yard, ensuring efficient and controlled operations. 
  • Warehouse Management Monitor: You can monitor your yard activities in the warehouse management monitor. 
  • Integration with Other Modules: EWM integrates with other SAP modules, such as Inventory Management and Delivery Processing, to ensure seamless data flow. 
  • Yard Location Management: EWM helps manage yard locations, including parking spaces and doors. 
  • Yard Movements: EWM tracks and controls movements of vehicles and TUs within the yard. 
  • Yard Stock: EWM provides visibility into stock located in the yard. 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review the Process flow of DAS (Dock Appointment Scheduling)  in S/4HANA EWM system.


Answer: SAP Dock Appointment Scheduling (DAS):
  • When integrated with SAP Extended Warehouse Management (EWM), allows for efficient planning and execution of vehicle arrivals at warehouse doors, optimizing dock utilization and streamlining the flow of goods. 
  • DAS aims to optimize warehouse operations by facilitating the scheduling and management of vehicle arrivals at docks, reducing wait times and improving efficiency. 

Key Features and Functionality:
  • Appointment Creation: Carriers or warehouse operators can create and manage loading appointments, specifying the dock, time slot, and other relevant details. 
  • Real-time Synchronization: DAS and EWM synchronize status changes of loading appointments and their related transportation unit (TU) activities in real-time. 
  • TU Creation: When a loading appointment is created, EWM automatically creates a TU, linking the delivery with the dock appointment. 
  • Status Updates: As the truck progresses through arrival, unloading, and departure stages, the status of the loading appointment and TU is updated in both DAS and EWM. 
  • Yard Management: DAS can be used to manage yard activities, such as assigning trucks to specific docks and tracking their movements. 
  • Collaborative Portal: DAS can serve as a collaborative portal between carriers and warehouse operators, facilitating communication and coordination. 
  • Optimized Resource Utilization: By scheduling appointments, businesses can optimize dock utilization, reduce congestion, and improve the overall flow of goods. 
  • Real-time Visibility: DAS provides real-time visibility into loading and unloading operations, allowing businesses to track all goods entering or leaving their yard. 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is "Pick Face" in the context of Warehousing Operations ? 


Answer: In warehouse management, a "Pick Face" (also called a forward-picking location) is a designated area or shelf where products are stored specifically for picking and fulfilling orders, typically located on the ground level or near the picking area.

Characteristics of "Pick Face":
  • It is also usually referred to Bins in a warehouse usually setup for loose pick activities where it is not full pallets storage bins. 
  • Pickfaces are usually located on the group location of a rack, or it may be located at one or two levels above the ground location. At the ground location, it is easier and more efficient for anyone to perform loose picking by hand. To perform loose picking at a higher level, the picker shall either need to use a forklift or a reach truck to bring down the pallet, pick the required quantity and return the pallet to the original rack location.
  • As products are picked from Pickfaces, they need to be replenished from the main storage area to maintain a sufficient stock level. 
In warehouse management, Dynamic Pick Faces assign products to locations based on real-time demand, while Fixed Pick Faces assign products to specific, unchanging locations. Dynamic Pick Faces offer better space utilization and adaptability, but Fixed Pick Faces are simpler to manage. 
Here's a more detailed comparison:

Dynamic Pick Faces:
  • Definition: Products are stored in locations that are not fixed, but rather assigned based on demand and other factors, allowing for flexible storage and picking.
  • Advantages: 
    • Space Efficiency: Maximizes space utilization by allocating items to locations based on their demand.
  • Adaptability: Easily adjusts to changing inventory levels and seasonal spikes.
  • Scalability: Accommodates growth in inventory or seasonal spikes without significant adjustments.
  • Disadvantages: 
    • Complexity: Requires a robust IT system to manage dynamic assignments and optimize locations based on demand.
    • Initial Setup: Can be more complex to implement than a fixed system. 
Fixed Pick Faces:
  • Definition: Each product is assigned a specific, unchanging location for storage and picking. 
  • Advantages: Simplicity: Easier to manage and understand compared to dynamic systems. 
  • Predictability: Pickers know where to find specific products, which can lead to faster picking times. 
  • Disadvantages: 
    • Space Waste: Can lead to underutilized areas if demand for specific products fluctuates. 
    • Lack of Flexibility: Difficult to adapt to changing inventory levels or seasonal spikes without significant adjustments. 
    • Inefficiency: Can lead to inefficiencies if demand for certain products is high and space is limited. 
"Pick Face" in SAP S/4HANA EWM (as at 2025):
  • SAP EWM doesn't have a dedicated "Pick Face" for Storage Type Role definition.
  • But it is possible to configure and manage picking areas using storage types and other EWM features to achieve similar functionality, in this manner the Storage Bins selected as "Picking Areas" effectively can act as "Pick Face" Storage areas. 
  • It is important to note that it is entire possible to set up replenishment processes to move stock from "Full Palette / Box Storage" Bins  to your designated Picking Areas (Storage Bins for "Pick Faces"). 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
at
Labels:

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Subscribe to: Post Comments (Atom)