--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Integration setup steps for EWM as a Distributed system (from an Application perspective)
.jpg)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Integration setup steps for EWM as an Embedded system (from an Application perspective)
.jpg)
Answer: The following Integration steps are for S/4HANA 2023 Embedded EWM scenario, some of these steps may differ slightly depending on version used and further "Simplification" by SAP for S/4HANA Embedded scenarios.
Steps (some are combined steps):
Pending
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: ERROR in Storage Type determination when create WT for an Outbound Scenario.
Answer: The above ERROR in the in-class exercise, investigated and see the following Blog Post link:
S/4EWM-ECC6 Configuration - Optimize Access Strategies for Storage Types
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Is it possible for a receiving into a single Receive to Dock SLoc to Final Putaway into different Storage Locations (and different EWM Storage Types)?
Answer: Refer to the following Blog Post demonstration which will show that it is possible with some manual interventions at time of WT creation. However, the scenario in the Blog Posts below is to demonstrate the case for Storage Locations for the SAME Plant. However, for a CENTRAL EWM Warehouse to SLoc assigned from different Plants (same or different companies) may required further thought processes albeit perhaps not logistics related but accounting impacts.
S/4EWM-ECC6 Configuration - Receive into SLoc RD06 but Putaway into SLoc AF06, AA06, and AB06
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review relevant navigation in the EWM Monitor.
Answer: The SAP EWM Monitor is a centralized tool for warehouse managers to gain real-time visibility into a warehouse's operations within SAP Extended Warehouse Management (EWM). It provides detailed information on warehouse processes, stock levels, resource utilization, and documents, enabling users to track activities, identify issues using alert monitoring, and take immediate corrective actions. The monitor is highly customizable, allowing users to create personalized views and access specific data points for efficient warehouse management.
• Real-time Overview: Provides a comprehensive view of inbound and outbound processes, stock in bins, and resource status.• Alert Monitoring: Signals actual and potential problems in the warehouse, allowing for timely intervention.
• Exception Handling: Offers tools to correct or manage problematic situations directly within the monitor.
• Direct Action Execution: Enables users to execute various warehouse functions, such as creating or confirming tasks and orders, or blocking bins.
• Document and Process Tracking: Allows users to track the status of various documents, including inbound and outbound deliveries, warehouse tasks, physical inventory, and other warehouse activities.
• Resource Management: Provides insights into the utilization of warehouse labor and resources.
• Customization: Users can customize the monitor by creating custom nodes, saving selection variants for automatic filtering, and hiding unnecessary branches.
• Access: From the SAP Easy Access screen, choose Extended Warehouse Management Monitoring /SCWM/MON - Warehouse Management Monitor. Enter the warehouse number and the monitor name or alternative access will be vai to enter the following t-code /N/SCWM/MON in the Command Box to directly access the monitor.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of EWM Process steps illustrated in class.
_Blogged.jpg)
https://EWM Enterprise Structure
https://Storage Type & Storage Section Configuration
https://Generate Bin from Bin Structure
https://Master Data Integration for EWM
https://Warehouse Monitor Naviation
https://Transfer QI to Unrestricted using MIGO
https://Transfer QI to Unrestricted using EWM t-code
https://GI to Cost Center using EWM t-code
https://Production Supply Area Staging and Backflushing
https://Expected Goods Receipt for Production Order
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What happen when the ERP Cost Center is obsolete and it is Send to Distributed EWM via the Replication Program in EWM?
.jpg)
Answer: It is not possible to delete a Cost Center in the ERP system when the Cost Center has been used in any ERP transactions with transaction history exist for a Cost Center. Deletion of a cost center using transaction KS04 is only possible if no transactions have been posted to it, and in most cases, changing the validity period is the preferred method to "deactivate" a cost center. However, it is possible to change the validity date of a Cost Center in KS02.
According to SAP documentation, if a cost center is deleted in the ERP, the deletion is replicated to SAP Extended Warehouse Management (EWM), and the cost center is marked as deleted or invalid in EWM, preventing its further use.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to find Standard User Exit for an SAP Program?
Answer: Check the following Blog Posts for how the check User Exits for a T-code in SAP.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How is the "Reason Code" for GI directly (t-code /SCWM/ADGI or Post Unplanned Goods Issue) via EWM system is configured and is there a "Replication Program" in the EWM system for ERP "Reason Code" to be replicated to the EWM system, the 3rd question is there any Field Selection for the EWM "Reason Code" for Unplanned GI to match the Field Selection for ERP Movement Type based "Reason Code"?
Answer: There is a 2 part answer to the question for SAP EWM /SCWM/ADGI transaction code:
Replication for Movement Reason and Cost Center.
Movement Reason• Define EWM Movement Reason Configuration: Extended Warehouse Management > Cross-Process Settings > Warehouse Task > Manage Reasons for Goods Movement• Map EWM Reason to ERP Reason: Go to the Customizing activity: Interfaces > ERP Integration > Goods Movements > Define Custom Specific Movement Types > Communication EWM --> ERP custom movement types.• Use the activity Map EWM Reason Code to ERP Reason for Movement.• Ensure the movement reason defined in EWM matches the reason code in SAP ERP for accurate integration and reporting, such as for scrapping or stock corrections.Cost Center• Replication: use t-code /SCWM/ACC_IMP_ERP to replicate ERP Cost Center to the EWM system.• Check Cost Center replicated in Structure "/SCWM/S_ACC_ADD_COSTCENTER" in the EWM system.
• Navigate to Warehouse Task Settings in the EWM IMG via SAP Extended Warehouse Management (EWM) > Cross-Process Settings > Warehouse Task > Go to Manage Reasons for Goods Movement.
• Define or Modify Movement Reasons: In the IMG, you can define or modify specific movement reasons (e.g., Consumption, Scrapping).• Make Fields Mandatory: Goto IMG SAP Extended Warehouse Management (EWM) >Extended Warehouse Management>Interfaces>ERP Integration>Goods Movements>Map EWM Reason Code to ERP Reason for Movement
• Map EWM Reason for Movement to ERP: Map EWM Warehouse + EWM Reason for Movement to ERP Movement Type + ERP Reason for MovementSee the following Blog Post for Configuring "Movement Reason" for /sCWM/ADGI to be Mandatory:
https://froggysap.blogspot.com/2025/09/s4ewm-ecc6-scwmadgi-movement-reason.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the BAPI for /SCWM/ADGI for Movement type
Answer: There isn't a specific BAPI for SAP Extended Warehouse Management (EWM) transaction /SCWM/ADGI; instead, you would use the standard SAP Goods Movement BAPI, BAPI_GOODSMVT_CREATE, and configure it for Movement Type 201 by providing the required cost center and other details. The BAPI-created material document will then reflect the goods issue to the cost center from the warehouse, and a subsequent warehouse task is created and confirmed.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the transaction code for "Change Pointer" for the ERP Material Master (not BD10), to transfer the field changes to /SAPAPO/MAT1?
.jpg)
.jpg)
Answer: Transaction Code BD10 in ERP system can be used to Create the APO Product in the EWM system. AND Transaction Code BD10 in the ERP system can also be used to Change Client-level data in the Material Master to the APO Product in the EWM system as shown in the demo slides above.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Provide a T-code List of SAP EWM system.
Answer: The following is a QUICK Transaction Code for S/4HANA EWM, it is not a complete list and periodically may update to this list when time permits:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.