--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the difference between "Physical Stock" vs "Available Stock" in the EWM Monitor?
Answer: See the following Blog Posts or a demonstration and exlanations:
Click link to Blog Posts:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to display a list of Products and Warehouse Products in SAP EWM system ?
_BLogged.jpg)
Answer: Methods of getting a list of Warehouse Products:
- via Query from the Table above (see below link to other EWM tables)
- via the EWM Warehouse Monitor
- Goto folder Product Master Data - Warehouse Attributes (double-click).
- Change Layout to ADD fields desired.
- Export to Spreadsheet.
Click link to Blog Posts for Common Tables for EWM:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review the Process of EWM Inbound Delivery (both Distributed and Embedded EWM).
Answer: The core inbound process steps are fundamentally the same for both Distributed (Decentralized) EWM and Embedded EWM. In both deployment options, the process guides goods from arrival to their final bin using the exact same transactional sequence:
The standard step-by-step process flow is as follows:
- Purchase Order Creation: The process starts in the ERP/SAP S/4HANA core system, a Purchase Order item created with EWM activated Storage Location (Receive in Dock SLoc RD00) and Confirmation Control key relevant for Inbound Delivery.
- LE Inbound Delivery Creation: The process starts in the ERP/SAP S/4HANA core system, which automatically generates an LE inbound delivery document (often based on a Purchase Order or Advanced Shipping Notification).
- Replication (Warehouse Request): The LE inbound delivery document is replicated into the EWM system as a EWM inbound delivery to act as a Warehouse Request.
- Unloading & Deconsolidation (Optional): Goods are received at the door, unloaded, and may be split into smaller units if necessary.
- Goods Receipt (GR) Posting: Goods receipt is posted in EWM and subsequently updated in the ERP system. Best practice is to received into Dock Storage Location (SLoc RD00) which is mapped to EWM GR-ZONE. (if Goods Receipt step is not executed at this point, it can be delayed to the WT confirmation step).
- Warehouse Task (WT) Creation: EWM creates warehouse tasks where the system will determine EWM stock movement from the GR-ZONE to the Final Putaway Storage Type & Storage Bin.
- Putaway & Confirmation: Warehouse workers physically move the items and confirm the putaway in the system. The Stocks is Putaway to teh Final Final Putaway Storage Type & Storage Bin according to the WT. In the ERP/S/4HANA core system, the stocks is transferred to SLoc RD00 (Receive in Dock) to AF00 (Available for Sales/Use).
Click the following for the Process steps:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: The common issue of drag the "Materials" instead of "WT" to a HU in Work Center Bin resulting in disconnected WT and the Material, how to resolve?
Answer: The problem is SAP do not stop user to select "Material" to drag-and-drop it to another HU in Work Center BIN which end-up causing disconnecting the original Material's WT like the above simulation screen. If follow proper step (recommended in the Blog Posts below will auto resolve the issue); however, if the HU still stuck without the WT in the Work Center BIN, then it is recommended to use t-code /SCWM/ADHU to create a manual WT for the Movement. Both resolution method above is found in the following blog posts.
When we wrongly drag the Material instead of the WT out from a HU# to a new HU#, there are 2 options:
- Preferred method:
- In /SCWM/DCONS, do not drag the "lost" WT#200157 back to the material "Hollow Shaft".
- Set complete to both HU# 665 and HU# 10546.
- Go back to the Warehouse Task and Confirm all WTs.
- There should be ONE WT which cannot be confirmed ie: WT#200157 where it does not have any Material and Qty.
- Set the WT#200157 to Cancel status.
- The system should AUTO created a new WT# for the Material "Hollow Shaft" in HU#10546.
- Confirm that new WT should move the HU#10546 from the DECO Bin to the Final Putaway Storage Bin.
- Verify the completed MOVEment of the HU#10546 from the DECO Bin to the Putaway Bin.
- Verify that there is no more HU in the Deconsolidation Work Center in /SCWM/DCONS.
- What if system did not Auto create the new WT for HU#10546:
- Use EWM t-code /SCWM/ADHU to create a new WT manually for the MOVEMENT.
- Load the Product/Material "Hollow Shaft" in /SCWM/ADHU which will show the HU#10546 in the current DECO Bin location.
- Create WT
- Enter Destination Bin as HU#10546, using WPT "9999", Enter the QTY, Enter the Putaway Bin manually.
- SAVE the WT (will also create a WO).
- Then Confirm the manually created WT.
- Verify the completed MOVEment of the HU#10546 from the DECO Bin to the Putaway Bin.
- Verify that there is no more HU in the Deconsolidation Work Center in /SCWM/DCONS.
See the following demo:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of MIGO (Synchronous Goods Receipt) without Inbound document in Embedded EWM scenario for Purchase Order receiving.
Answer: In SAP S/4HANA embedded Extended Warehouse Management (EWM), Synchronous Goods Receipt is a feature that allows you to record physical stock arrivals in both Inventory Management (IM) and EWM simultaneously in real-time, completely eliminating the need to create traditional intermediate inbound delivery documents.
How it Works:
• Delivery-less Processing: Instead of waiting for an inbound delivery document to trigger warehouse tasks, posting a Goods Receipt (e.g., via the Post Goods Movement app or Inventory Management BAPIs) automatically triggers the EWM receipt and creates putaway warehouse tasks at the same time.• Direct Bin Placement: The system determines the putaway destination bin directly from the transaction and triggers the warehouse tasks independently of a warehouse request.• Supported Scenarios: It applies to external procurements (Purchase Orders, scheduling agreements, Stock Transport Orders) and production orders (discrete and process manufacturing).
Key Benefits:
• Simplified Process: Cuts down document clutter by processing without Inbound Delivery documents or warehouse requests.
• Increased Speed: Streamlines the putaway process for simple scenarios (e.g., direct to fixed bin, no Value-Added Services needed), getting stock available faster.
• Real-Time Visibility: Synchronizes IM and EWM financial and physical records instantly without delayed queued processing (aRFC/qRFC).
See the following Blog Posts:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Depict EWM Inspection for MM EWM Inbound Delivery process.
Answer: SAP Extended Warehouse Management (EWM) integrates with the Quality Management (QM) module to automate quality checks during goods receipt, internal stock transfers, and production. When inventory is received, EWM stock is placed in quality status (Q-stock) and a QM inspection lot is triggered automatically for the warehouse team to evaluate.
EWM handles various types of inspections depending on where it integrates with the supply chain with the following Key Inspection Types::
• Counting (IOT 3): Standard 100% quantity verification upon inbound deliver.
• Inbound Deliveries / Goods Receipt (IOT 4): Triggers an inspection (e.g., lot type 1701) automatically as soon as goods are received from a vendor or production.• Returns & Internal Stock (IOT 5): Evaluates products currently stored in the warehouse or when being returned by customers.
See the following Blog Posts:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the "9-series" ERROR in Outbound Queue in EWM, and specifically the Message Action"/SCWM/MSG_DTN_PRD_OUT_SEND" not supported below?
Answer: Deleting a stuck Post Processing Framework (PPF) outbound queue in SAP EWM (SMQ1 or SMQ2) is generally not recommended and unsafe as a first step. Doing so permanently deletes the transactional message, leading to broken document flows, inconsistent delivery statuses between EWM and ERP, and missing deliveries.
Note: However, It is generally safe to delete hung or obsolete printing-related Post Processing Framework (PPF) outbound queues (via SMQ1) or stuck triggers (via SPPFP) in SAP EWM, as it only removes the print command data. This action will not alter your inventory balances or harm your underlying delivery or warehouse documents.
To resolve printing issues with /SCWM/PRD_OUT_LOAD_LIST_PRINT (the smartform/PDF used for the Outbound Loading List in SAP EWM), you must troubleshoot the Post Processing Framework (PPF) condition technique and ensure the associated Adobe Form / SmartForm is correctly mapped and activated.
Resolve the issue by following these steps:
1. Check the PPF Action Profile Configuration:
Ensure the PPF action profile assigned to your outbound delivery or transportation unit is active and configured correctly. [1]Go to the PPF condition configuration using transaction SPPFCADM.Select Application /SCDL/DELIVERY (or your specific TU application).Check the Action Profile for outbound loading and verify that /SCWM/PRD_OUT_LOAD_LIST_PRINT is maintained in the action definition.Ensure the Schedule Condition and Start Condition are met
2. Verify Output Condition Records:
If the system fails to trigger the output, your condition records might be missing or incorrect.Go to the condition maintenance transaction for outbound deliveries: /SCWM/DLV_PRINT or /SCWM/PRDO.Ensure that a valid condition record exists for the print profile, document type, and warehouse number.Verify that the SmartForm / Adobe Form name is correctly mapped in the condition record.
3. Check Spool and Printer Mapping:
If EWM reports that the print job was successfully processed but nothing prints, the issue is likely with the spool generation or device type. [1]Review transaction SP01 or SP02 to see if the spool request was generated.Check if the specific output device (printer) is set to immediately print and ensure the user profile has the correct default printer assigned.
Common Workflow to Fix Stuck Queues:
1. Open SMQ2 (for Inbound) or SMQ1 (for Outbound).2. Double-click the queue name to view the error status.3. Fix the underlying data or configuration issue (e.g., missing storage bin or wrong mapping).4. Select the failed queue line and click Activate (or hit F6) to reprocess it.
Essential T-codes for resolving queue issues include:
1. Queue Monitors
1. Queue Monitors
• SMQ2 (Inbound Queues): View and process queues coming into EWM (or going into ERP) that are blocked or stuck in an error status.• SMQ1 (Outbound Queues): View and manage queues sending data out of EWM to the ERP/Core Interface (CIF).• SMQ3 (Queue Administration): Used to view saved queues or LUWs (Logical Units of Work) that were temporarily parked for later processing.
2. Diagnosis & Logs
• /SCWM/MON (Warehouse Management Monitor): The central hub. Navigate to Tools > Queue Manager to monitor and restart delivery queues directly inside the EWM framework.• SLG1 (Application Log): Analyze error logs to uncover granular details on why an inbound/outbound delivery failed to post or update.
3. System & IDoc Troubleshooting
• ST22 (ABAP Dump Analysis): Investigate short dumps. If an integration queue fails with a system error, a dump is often generated in either EWM or ERP.• WE02 (IDoc List): Use this to display and trace IDoc messages (particularly if your integration with SAP ERP uses decentralized delivery interfaces).
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the method to MASS Delete specific types of EWM Outbound Queue ?
Answer: Methods to Delete Queues:
Direct SMQ1 Manual Mass Deletion:
1. Open transaction SMQ1 (qRFC Monitor for Outbound Queues).2. Enter your specific criteria (e.g., Target Destination, *DLV* in the Queue Name field).3. Press Enter or Execute (F8).4. Go to the menu: Edit -> Select All.5. Click the Delete icon (Shift + F2), or go to Edit -> Delete Selected Objects.6. Confirm the deletion.
Automating Mass Deletion (for large volumes):
If you have thousands of entries and manual deletion is too slow,
1. Go to transaction SE38 or SA38.2. Enter program name RSTRFCQDS.3. Execute.4. Input your specific queue names and destination, then run to safely purge the targeted queues in bulk.
Note: It is not safe to mass delete SAP EWM (Extended Warehouse Management) outbound queues as a first resort. Deleting them permanently removes the transactional data, which breaks document flow and creates severe data inconsistencies (e.g., missing deliveries, broken stock status) between your EWM and ERP/S4H systems.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Who suppose to look into this SMQ2 is it all i.e All modules i.e CPL, FICO, PS, PM ?
Answer: Transaction SMQ2 manages inbound qRFC (Queued Remote Function Call) queues. It is not specific to just one module. Any module (like FICO, PS, PM, or CPL) that relies on asynchronous data replication, interfaces, or IDocs will have its respective module consultants and business teams analyze the stuck queues.
Who is Responsible for Checking SMQ2?
Because SMQ2 acts as a central holding area for incoming data, the responsibility is divided by data ownership, not the system itself:
- Module Consultants (FICO, PS, PM, CPL): They are responsible for understanding the functional errors in the queue. If a queue is stuck due to a missing configuration, wrong master data, or a financial period being closed, the respective functional module expert must investigate.
- Integration / PI / CPI Team: If the queues are backed up because of broken communication channels between systems (e.g., between SAP ECC/S4HANA and EWM/CRM), the integration team steps in.
- BASIS Team: They handle the underlying technical infrastructure, such as resetting the locks, checking RFC destinations, and making sure the queue monitor is actively processing data (e.g., via SMQR).
Responsibility for monitoring and clearing SAP EWM inbound (SMQ2) and outbound (SMQ1) queues is typically a shared process, with distinct roles for business application users (super users) and technical support.
1. Business / Application People (Key Users, Super Users, Functional Analysts):
- Work: They check queues daily using transactions like /SCWM/MON (Warehouse Monitor) or SMQ2. They are responsible for queue entries that fail due to business or master data issues.
- Common Examples: Missing master data (e.g., product weight/volume missing, incorrect packaging specs), unposted Goods Issues, or closed posting periods in ERP
- Action: They fix the underlying business data, then manually restart the stuck queue.
2. Technical People (ABAP Developers, Basis Administrators):
- Work: They step in when errors are tied to system issues or code faults.
- Common Examples: Custom program bugs, RFC communication dropouts, system dumps (e.g., ST22), or lock table conflicts.
- Action: They perform root cause debugging, review short dumps, or apply infrastructure-level fixes.
- Tier 1 (Business Analysts/Super Users): First-line of defense. They should review the queues daily, clear simple data errors, and notify the business.
- Tier 2 (Technical/ABAP): Second-line of defense. Engaged if the super user cannot identify the error or if the failure is a recurring technical issue.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review EWM Physical Inventory.
_0523_PhysicalInventory_Blogged.jpg)
Answer: The standard execution flow relies on designated SAP Transactions codes and Fiori Apps to process, post, and clear inventory adjustments, Step-by-Step EWM Process Flow as below:
- 1. Create and Activate the PI Document:
- T-Code: /SCWM/PI_CREATE
- Action: Select your inventory procedure code (e.g., HL for ad-hoc bin specific or HS for product specific). Input your target search criteria, select the generated item rows, click Set Flag, and change the initial status to Active before saving. User can decide to either set "Posting Block" or "Freeze Inventory" at time of the PI activity.
- 2. Execute the Physical Count:
- Mobile (RF Method):
- Access transaction /SCWM/RFUI. Navigate to 04 Internal Processes ➔ 01 Inventory Counting ➔ 02 Inventory Counting Manually. Scan the bin, verify handling units, and enter the physical quantity directly on your mobile scanner.
- Manual Paper-Driven Method:
- Print the physical selection sheet via /SCWM/PRPI_DOC. Hand the list to a warehouse associate to tally items manually. Once written down, use /SCWM/COUNTLIST or /SCWM/PI_PROCESS to type the actual quantities into the system.
- Fiori App Method:
- Count Physical Inventory - Paper-Driven Counting (App ID: F3340): Allows users to filter, view, and print Physical Inventory documents. It is primarily used to enter count results into the system after physical counting is completed.
- Physical Inventory Document Overview (App ID: F0379A): Provides a comprehensive look at all created physical inventory documents. You can search by storage location or count status and drill down to check item-level counting results.
- External System/ (Spreadsheet):
- /SCWM/PI_DOWNLOAD: Used to export storage bin and stock data to external systems or spreadsheets to facilitate offline inventory plannint.
- /SCWM/PI_UPLOAD): Allows you to upload storage bin data and count results from external systems back into your SAP EWM system.
- 3. Post Differences in EWM:
- T-Code: /SCWM/PI_PROCESS
- Action: Locate your reference document number, review the variance between the book inventory and actual entry, and click Post. This step completes the counting run and adjusts the physical inventory availability balance at the local bin architecture leve
- 4. Clear Differences at ERP / IM Level:
- T-Code: /SCWM/DIFF_ANALYZER
- Action: Discrepancies posted in EWM are held temporarily in a virtual interface component. Execute the Difference Analyzer tool to evaluate value variances against user tolerance groups. Select the item lines and hit Post and Save. This generates the official ERP Material Document (similar to MM's MI07), aligning Inventory Management valuation with the warehouse floor.
Click below to see EWM PI steps:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: PM-EWM integration preview.
%20(1).jpg)
Answer: Integrating SAP Plant Maintenance (PM/EAM) with SAP Extended Warehouse Management (EWM) automates the picking, staging, and issue of spare parts for maintenance orders. This eliminates manual coordination, accelerates repair times, and streamlines inventory visibility for Maintenance, Repair, and Operations (MRO) processes.
See the following Blog Posts on steps:
Notes: the Post only show steps, actual SAP Demo creation will be created in a separate Blog Post as and when the EWM system is available soon in the future.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.