.jpg)
Thursday, July 2, 2026
Question no 4135 : Down Payment creating and processing for Purchase Order
In SAP Material Management, which of the following setup and processing are TRUE about Down Payment processing for Purchase Order ?
(more than one answers)
A) The Down Payment G/L Account is assigned to the Vendor's Reconciliation Account.
B) Each Vendor's Reconciliation Account can only be assigned to one Down Payment G/L Account for each Special G/L Indicator
C) Down Payment can be entered for the Purchase Requisition item and copied to the Purchase Order item.
D) Down Payment can only be entered after at least one Goods Receipt completed for the Purchase Order item.
E) One or more Down Payments can be posted to each Purchase Order item.
Answer: A, B, E
(more than one answers)
A) The Down Payment G/L Account is assigned to the Vendor's Reconciliation Account.
B) Each Vendor's Reconciliation Account can only be assigned to one Down Payment G/L Account for each Special G/L Indicator
C) Down Payment can be entered for the Purchase Requisition item and copied to the Purchase Order item.
D) Down Payment can only be entered after at least one Goods Receipt completed for the Purchase Order item.
E) One or more Down Payments can be posted to each Purchase Order item.
Answer: A, B, E
.jpg)
.jpg)
Wednesday, July 1, 2026
Q&A in Class (2026-07-01) S43000
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of Plant Maintenance Enterprise Structure.
Answer: While the foundational physical PM enterprise structure (such as Maintenance Plants and Planning Plants) remains unchanged,
1. Maintenance Plant
A Logistics (LO) Plant can be used for MM, PP, SD, PS, QM, PM, CS (all Logistics activities). The Logistics (LO) Plant is also the maintenance plant (for PM) is "Location-based". Therefore, a Maintenance Plant is a specific physical site or production facility where technical objects (functional locations and equipment) are located.
Another purpose of the Maintenance Plant (Logistics Plant) is that the Maintenance Work Center is created at the Maintenance Pant (where Technicians are at).
2. Maintenance Planning Plant
It is the planning plant is "Planning-based". It is the organizational unit responsible for organizing and preparing all maintenance tasks, ie: the Planning tasks of Maintenance.
It is important to note that the Maintenance Plant can also be designated as a Planning Plant if it perform planning for itself. However, a specific Logistics Plant can be created as Planning Plant (example a office space of Maintenance Planning where there are technical objects or maintenance work center in that plant), in this case only the planners are that AND this P'anning Plant can be responsible for more than one Maintenance Plant.
Click here to view posts of Planning Plant & Maintenance Plant:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Show the steps to create a Shift Sequence for Plant Maintenance Work Center.
Answer: In SAP S/4HANA Plant Maintenance (PM), a shift sequence defines how daily working times and breaks rotate for a work center. Its significance for scheduling accuracy lies in translating theoretical "calendar days" into precise capacity availability, preventing resource overload, and ensuring alignment between maintenance activities and production schedule.
Click the following the see how a Shift Sequence is created:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: How to create "Variant" of a Standard FIORI app for a specific data filter? PLUS review of the related demonstration on Fiori Apps navigations.
.jpg)
Answer: SAP Fiori is not an acronym and does not stand for anything. It gets its name from the Italian word for "flower". SAP chose this name to symbolize the freshness, simplicity, and natural
beauty they wanted to bring to their software's user interface.
Rather than a specific product, SAP Fiori is the official design system and User Experience (UX) layer for SAP products, Here are the key takeaways about what it does:
- Role-Based: It provides simplified, task-oriented applications tailored to exactly what a specific user needs to do their job.
- Intuitive Design: It replaces clunky, traditional enterprise screens with a modern, consumer-grade interface.
- Cross-Device: Fiori apps are designed to work smoothly on desktops, tablets, and smartphones.
- Design Principles: The system is built on five core pillars: role-based, adaptive, simple, coherent, and delightful.
There are 3 main interfaces for SAP access today:
- SAP GUI: The classic, desktop-based interface. It relies on specific transaction codes and is still widely used for heavy backend configurations and legacy systems.
- SAP Business Client (NWBC): An integration shell that allows users to access both traditional SAP GUI screens and modern web-based applications within a single desktop window.
- SAP Fiori: The standard, web-based UX for modern environments like SAP S/4HANA. It features a role-based, personalized launchpad with specific apps for transactional, analytical, and informational tasks.
Answer: SAP introduced SAP Fiori in 2013. It launched initially at the SAPPHIRE conference with a set of 25 apps, focusing on a mobile-first, role-based user design. Since its release in 2013, the SAP Fiori design system has gone through major updates:
- 2013 (Fiori 1.0): 25 apps initially mainly for mobile-first specifically for example PO approval.
- 2016 (Fiori 2.0): Expanded to ERP scenarios with features like the Fiori Launchpad and enhanced navigation.
- 2019 (Fiori 3): Introduced a unified user experience across the entire suite of SAP products along with the Quartz and Horizon design themes.
Key updates in Fiori 3.0:
SAP Fiori 3 introduces a redesigned, intelligent user experience focused on consistency across all SAP products, featuring- a new "Quartz theme" ( is the default design system and visual theme family for SAP Fiori 3)
- new interface called "Spaces and Pages" layout for improved navigation.
- embedded AI capabilities with Joule (SAP's built-in generative AI copilot embedded within the SAP Fiori Launchpad).
- proactive situation handling (an intelligent framework that automatically detects, tracks, and alerts users about critical business issues).
- a conversational UI (digital assistant).
- enhanced analytics for actionable insights.
The future of SAP Fiori is centered around AI-driven interfaces, cloud-native delivery, and intelligent automation. While Fiori remains the visual foundation for SAP S/4HANA, users will increasingly interact with enterprise data through natural language and autonomous agents rather than traditional click-based navigation.
To help you to understand SAP Fiori, here are some official links:
https://learning.sap-press.com/sap-fiori
To help you to understand SAP Fiori, here are Blog Posts to show the step by steps guides:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Classic vs S/4 FIORI Technical Object creation for SAP Plant Maintenance.
Answer: The FIORI "UX" (User Experience) App "Create Technical Object" is a combined "UX" App to Create either Functional Location or Equipment and therefore combining the classic transaction code of IL01 and IE01. Besides layout changes of the look and feel in the FIORI interface via "Create Technical Object" FIORI App, there is really not much difference comparing this App to IL01 or IE01 in terms of data fields to be entered in the classic GUI transaction or Fiori App.
See link
Another FIORI App for Technical Objects perhaps worth reviewing is the "Find Technical Object" FIORI App ID "F2072"
.jpg)
See the link below for a demonstration of this App:
Some of the key features this App are:
- List Display FL and EQ plus download to Excel.
- Display Installation information for the Technical Object in the Hierarchy.
- Perform Installation and Dismantling.
- Shows details of related Notification and Order for the Technical Object of FL an EQ.
- etc.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: References for SAP documentations on SAP Plant Mainteannce.
.jpg)
Answer: The SAP Plant Maintenance (PM) process is an enterprise asset management lifecycle framework. It helps organizations track, plan, execute, and settle maintenance activities for physical assets. The core workflow spans from initial asset structuring to work execution, order settlement, and continuous historical analysis. SAP PM Process can be described as 5 distinct components:
- Technical Object Structuring:
- Functional Locations - Hierarchical structures representing specific areas or plants where maintenance activities take place (e.g., Hydraulic system room).
- Equipment - Individual physical objects installed to functional locations (e.g., Equipments like Pump, Motor installed to the Functional Location called Hydraulic system room).
- Bill of Materials (Material BOMs) - Spares lists associated with equipment to ensure the right materials are available for repairs.
- Maintenance Notification:
- Breakdown Maintenance- Handles sudden equipment failures to restore operations and document the incident.
- Corrective Maintenance - Breakdown maintenance is emergency, reactive work performed only after an asset fails completely. In contrast, corrective maintenance is typically a proactive or planned approach to fix minor flaws or wear-and-tear before a total failure stops operations, minimizing unplanned downtime.
- Preventive Maintenance - Is a proactive strategy of regularly inspecting, servicing, and repairing equipment before it breaks down in specific intervals. Its main goal is to avoid costly unplanned downtime, extend asset lifespan, and ensure smooth, safe operations.
- Refurbishment - Repair damaged or defective repairable spare parts so they can be reused and returned to warehouse stock. This practice saves significant procurement costs over buying brand-new replacements.
- Inspection Rounding - Is a planned maintenance process where a technician inspects multiple, similar technical objects in a specific sequence (a "round"). Technicians use rounds to record specific measuring point values, such as temperature, pressure, or run hours, and to create subsequent maintenance notifications when required.
- Calibration - SAP Plant Maintenance (PM) integrates with the Quality Management (QM) module to handle equipment calibration. This ensures that measuring and test instruments operate accurately and meet regulatory compliance. The system schedules maintenance, generates calibration orders, tracks measurement results, and updates equipment status automatically.
- Maintenance Planning & Scheduling:
- Operations & Task Lists - Defining the specific steps, time required, and spare parts required to complete the maintenance work and the maintenance work centers (technicians) responsible.
- Maintenance Plan - It can automatically generates maintenance orders, notifications, or service entry sheets at predefined intervals, ensuring equipment is regularly serviced to prevent breakdowns.
- Material Reservations - Checking the availability of spare parts in inventory and reserving them in Material Management as Reservations for the maintenance work.
- Capacity Planning - Scheduling the dates and times to ensure maintenance doesn't severely disrupt daily production or operations.
- Maintenance Execution:
- Permits/Safety - Tagging and safety clearance documents (if applicable) are assigned.
- Goods Issue - Spare parts are physically issued from the warehouse to the specific maintenance order.
- Confirmation - Technicians or supervisors confirm the work is completed, log the actual hours spent, and provide feedback on the machinery's condition.
- Completion, Settlement, Close:
- Technical Completion (TECO) - The order is marked as finished, releasing any unneeded reserved materials and freeing up capacity.
- Costs Settlement - Actual costs incurred (labor, materials, services) are settled against the appropriate cost centers or general ledger accounts.
- Business Completion (CLSD) - The order is locked against further changes, finalizing its history for reporting and predictive analysis.
Click the following for official documentations on SAP Plant Maintenance:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Technical Permits in SAP Maintenance Order.
.jpg)
Answer: A Permit in SAP Plant Maintenance (PM) is a safety and compliance control mechanism. It acts as an operational barrier, ensuring that high-risk maintenance tasks (like hot work or confined space entry) cannot begin until necessary approvals, safety protocols, and regulations are strictly met.
When Technical Permit is assigned to the Technical Object (Functional Location and Equipment), Maintenance Order creation with the Permit will require Permit (issue) approval before the Maintenance Order can be Released, and it is also possible to required Permit approval before the Maintenance Order can be set to TECO.
Click here to view the Presentation:
Click here to view the Presentation:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Demonstrate the LEAN Service Scenario introduced for S/4HANA in both MM and PM process.
_Blogged.jpg)
Answer: Lean Service in SAP S/4HANA Plant Maintenance (EAM) refers to a simplified, Fiori-based approach for procuring and managing external maintenance services. It replaces the older, highly complex MM-SRV framework (ML81N) by streamlining how maintenance planners request, approve, and record supplier-provided services.
Click the following Blog Posts to see the process flow for lean service in S/4HANA:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Outline the key aspects of Corrective Maintenance Steps (BH1 - Standard Process).
See the Blog Posts links to the Step-by-Step illustration from Create Notification to Complete Order.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Outlines the key aspects of Simplified Emergency Maintenance Process in S4 HANA Asset Management (BH2 - Emergency Maintenance).
Answer: Report Malfunction app is designed mainly for technicians for to be used in Emergency Breakdown process.
• Emergency maintenance involves creating a malfunction report, planning repair work, assigning work items and spare parts, and documenting the repair.
• It is included in default role SAP_BR_MAINTENANCE_TECHNICIAN.
• Emergency Maintenance, where all the steps are covered in one Fiori App ID F2023'
• Scope ID BH2 in SAP Best Practices is using this app which contains 3 tiles as below:
• It is included in default role SAP_BR_MAINTENANCE_TECHNICIAN.
• Emergency Maintenance, where all the steps are covered in one Fiori App ID F2023'
• Scope ID BH2 in SAP Best Practices is using this app which contains 3 tiles as below:
1. Report Malfunction Tile - used to create malfunction reports.
2. Manage Malfunction Reports Tile - list of malfunction reports.3. Repair Malfunctions-My Job List Tile - list of work items assigned to Me and My Team.
https://froggysap.blogspot.com/2024/10/sap-pm-malfunction-report-scenario.html
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Outline of Phased-Based Maintenance "Reactive Maintenance" (scope item 4HH) and "Proactive Maintenance" (scope item 4HI) scenarios.
Answer: SAP phase-based maintenance is encompassed within the Reactive Maintenance (scope item 4HH) and Proactive Maintenance (scope item 4HI) scenarios. Phase-Based Maintenance is a structured, 9-stage lifecycle process in SAP S/4HANA Enterprise Asset Management (EAM/PM) that standardizes how work requests are initiated, planned, approved, and executed. It prevents users from jumping steps by requiring the previous phase to be completed before moving to the next.
The nine sequential phases in this lifecycle are:
• Initiation: Creating the maintenance request.
• Screening: Reviewing and approving/rejecting the request.
• Planning: Creating and detailing the maintenance order.
• Approval: Authorizing work.
• Preparation: Securing parts and preparing the work environment.
• Scheduling: Dispatching the technicians.
• Execution: Carrying out the maintenance work.
• Post-Execution: Recording times, confirmations, and failure data.
• Completion: Performing technical and business completion.
Bog Posts step by step:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Measuring Point (Counter) Preventive Maintenance Plan Process flow.
Answer: SAP Preventive Maintenance using counters enables usage-based maintenance, triggering work orders based on actual equipment performance (e.g., running hours, mileage, or cycles) rather than fixed dates. This prevents both over-maintenance and unexpected equipment failures.
Key SAP Transaction Codes• IK01 / IK02 / IK03: Create, Change, or Display Measuring Point/Counter.
• IK11 / IK12 / IK13: Create, Change, or Display Measurement Document (Enter actual usage here).
• IP11: Create/Edit Maintenance Strategy.
• IP11Z: Create/Edit Cycle Sets (useful for grouping multiple counters).
• IP41 / IP42: Create Counter-Based Maintenance Plan.
• IP43: Create Multiple Counter Plan.
• IP10: Schedule Maintenance Plan.
Bog Posts step by step:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review Multi-Counter Performance-based Preventive Maintenance in S/4HANA.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Tuesday, June 30, 2026
Friday, June 26, 2026
Question no 4134 : Discount-in-Kind in MM Purchase Order
In SAP Material Management as at S/4 HANA 2023, what are the prerequisites for "Free Goods" (Discount-in-Kind) in Purchase Order ?
(more than one answers)
A) set "Grant Free Goods" in the General data view of the Purchasing Info Record.
B) set "Grant Free Goods" in the Purchasing Organization data view of the Business Partner Vendor.
C) set "Grant Free Goods" in the Source List for the Vendor and Material combination in the Source List.
D) set "Grant Free Goods" in the Plant data view of the Material Master.
E) Set "Grant Free Goods" in the Plant Parameter in the Configuration.
.
Answer: B, D
.jpg)
.jpg)
(more than one answers)
A) set "Grant Free Goods" in the General data view of the Purchasing Info Record.
B) set "Grant Free Goods" in the Purchasing Organization data view of the Business Partner Vendor.
C) set "Grant Free Goods" in the Source List for the Vendor and Material combination in the Source List.
D) set "Grant Free Goods" in the Plant data view of the Material Master.
E) Set "Grant Free Goods" in the Plant Parameter in the Configuration.
.
Answer: B, D
.jpg)
.jpg)
Thursday, June 25, 2026
Wednesday, June 24, 2026
Question no 4133 : Supply Region in Procurement
In SAP Material Management as at S/4 HAHA 2023, which of the following are functionality provided by the REM Profile assigned to the MRP 4 data view of a Repetitive Manufacturing Product/Material ?
(more than one answers)
A) GI backflush at GR Posting.
(more than one answers)
A) GI backflush at GR Posting.
B) Reporting Point Backflush.
C) Also Post Activities to the Product Cost Collector when Backflushing.
D) Determination of Backflushing and Goods Receipt Storage Location.
E) Determination of Movement Type to be used for Goods Receipt and Goods Issue Movement Type.
Answer: A, B, C, E
.jpg)
.jpg)
.jpg)
Answer: A, B, C, E
.jpg)
.jpg)
.jpg)
Tuesday, June 23, 2026
Monday, June 22, 2026
Q&A in Class (2026-06-26) EWM100
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Subscribe to:
Posts (Atom)