Lavishaedtech

Benefits of Low Stock Check: The low stock check is performed during warehouse task confirmation when a bin has minimal stock after a removal. It allows the picker to quickly assess stock levels, saving time on separate counts. This procedure ensures inventory availability, especially when stock is low, maintaining high service levels. SAP EWM automatically generates a PI document during task confirmation. A variant, the zero stock check, confirms the bin is empty and ready for putaway, aiding the putaway operator in ensuring the product will fit. Demerits of Low Stock Check: Testing of Low Stock Check: (Quantity is maintained as 10 in the configurations) Available Stock Situation: Current Position in Difference Analyzer for Product 250014: Please note for the product 250144, the current stock to be cleared in 18EA. Picking Task: Picking on RF: As we proceed next by pressing Enter button couple of times, due to the LSPI settings – system prompts below RF screen: We enter 3 as the Remain.Qty and press F1. This should increase the diff. analayzer stock for 250144 by 2EA to 20EA: And the stock in bin FIXD-02-03-03 is automatically updated to 3 Eaches: Now, we create another picking task for the same bin for 1 EA. Picking this WO 3000000370 using RF now: The system prompts again to enter the remaining quantity, Enter 0 and press F2 EMBn. Let’s refresh the difference analyzer and stock situation: Stock is emptied in the bin. Clear the difference analyzer, log off and log on from the system, to commit the changes and Repeat the process. Increase the stock in same bin FIXD-02-03-03 to 100 and create a Picking Task for 90, now As per the LSPI information provided in SAP help, it should create a PI document for LS only once per bin the financial year We will validate this theory now Stock: Picking Task: Now when I repeat the picking by RF, after entering the source details and scanning it in Pick-HU, the system simply confirms the WT: Difference analyzer for the product 250144 shows nothing now: Thus, we have now confirmed from our testing that LSPI gets triggered only once per storage bin in a given financial year.

YouTube Video Link – IN Progress Configuration Settings Assign the wave determination procedure to the warehouse and document type for replenishment. EWM→ Goods Issue process → Wave management → Wave template determination → Assign procedure to document type. Doc type: Set Automatic Wave Generation for Warehouse Process Type EWM→ Goods Issue→ Wave management → Automatic Wave generation with Warehouse process type This setting will help to automatically generate the Wave and execute it with an open Warehouse request that belongs to the assigned warehouse process type. Master Data Maintain the condition record Path → Easy access screen → EWM → Work scheduling → Wave management → Maintain condition records Wave Template: – Path → Easy access screen → EWM → Work scheduling → Wave management → Maintain Wave Template

SAP EWM CONDITION DETERMINATION PROCEDURE In SAP EWM, there are several condition determination procedures for various business processes like Automatic Packaging, Slotting, etc. Since, there are several such procedures and many of them scattered under different nodes in Customizing (depending on the business process being configured). But it becomes tricky to navigate on to multiple places and remember them on the tip of our tongue. With this document, I have compiled as many condition determination procedures as I could (from my knowledge and research), with the paths mentioned for each of them, and some more details: Transaction codes for condition maintenance – /scwm/dlvppfc /scwm/wdgcm /scwm/gcmc ********************************************************************************** ********************************************************************************** PATH: IMG-SCM EWM-EWM-Master Data-Packaging Specification – Determination of Packaging Specifications – Define Det. Proc. PATH: IMG-SCM EWM-EWM-Int WH Processes-Physical Inventory-Print-Create and Change Det. Proc. PATH: IMG-SCM EWM-EWM-Goods Issue Process-Wave Mgmt. – Wave Template Determination – Define Det. Proc. PATH: IMG-SCM EWM-EWM-Cross Process Settings-Handling Units-Basics-Print-Define Det. Proc. PATH: IMG-SCM EWM-EWM-GR Process-Slotting-Condition Technique-Det. Proc.-Edit Det Proc. For PW Ctrl Ind./Storage Section/Bin Typ. PATH: IMG-SCM EWM-EWM-GR Process-Strategies-Storage Bin Determination for Transit Warehouse-Define Det. Proc. DPP application (PPF) PATH: IMG-SCM EWM-EWM-Cross Process Settings – Delivery Warehouse Request – Actions – Configure Action Scheduling – Assign Determination Procedure REFERENCES: https://blogs.sap.com/2023/03/09/ewm-pick-list-printing-through-post-processing-frameworkppf/ https://blogs.sap.com/2022/09/18/concept-of-condition-technique-sap-ewm/ https://blogs.sap.com/2023/09/16/slotting-process-for-sap-ewm/

WAREHOUSE ORDER CREATION RULE (WOCR) Copyright for the above image belongs to SAP Press. As the name suggests, it is a Rule to bundle various Warehouse tasks into a Warehouse Order. This Rule has some criterions listed down below: SORT RULES LGWT – It has Sort Field WEIGHT (ascending Order) By default, if the checkbox is not ticked – it means ascending. ITEM FILTER FIL1 – It has restrictions of filtering WTs less than or equal to 5KGs LIMIT LIM3 – It will limit the total number of WTs per WO, in our case the same can be less than or equal to 2 WTs per WO. SAP EWM standard gives 3 WOCRs: DEF (Default) – Uses SORT RULE ‘PIPA’ (Field is PATHSEQ in ascending manner) UNDE (Undefined) – Uses SORT RULE ‘PIPA’ (Field is PATHSEQ in ascending manner) MFS (Material Flow System) – Limits a maximum of one WT per WO, makes sense since these WOs would be operated by machines which are capable of only executing one task at one point of time. WOCR Determination: 1) Either it is explicitly specified in the Warehouse Process Type (WPT) 2) It is determined at ‘Define Search Sequence of Creation Rules for Activity areas’ EWM FINDS WOCR AT WPT LEVEL (WCR1) EWM FINDS WOCR AT ACITIVITY AREA LEVEL (WCR1) THE RULE IS SATISIFIED FINAL RULE DETERMINED YES NA YES WCR1 YES NA NO DEF NO YES YES WCR1 NO YES NO UNDE NO NO NA DEF IF THE STORAGE TYPE IS RELEVANT FOR MFS (STORAGE TYPE ROLE ‘J’), THE WAREHOUSE TASKS WOULD HAVE THE MFS FIELD ‘KZSUB’ AS X (MFS RELEVANT). IN THIS CASE, THE WOCR DETERMINED WOULD BE MFS. TEST CASES: We have 6-line items, with respective quantities shown against each: The six-line items are converted in to 7 warehouse tasks (you can ignore why line 50 above is split in two WTs of 3 each, as I am also wondering 😊) Since we have now 7 WTs, with weights as below: WT1 – 101007 1 KG WT2 – 101008 2 KGs WT3 – 101009 3 KGs WT4 – 101010 5 KGs WT5 – 101011 3 KGs WT6 – 101012 3 KGs WT7 – 101013 7 KGs NOW THE WOCR MACHINE WILL START WORKING TO CONVERT THESE 7 WAREHOUSE TASKS INTO WAREHOUSE ORDERS: FIRST A SORT RULE WILL BE APPLIED THAT WOULD ARRANGE THESE WTs in ascending manner: WT1 – 101007 1 KG WT2 – 101008 2 KGs WT3 – 101009 3 KGs WT5 – 101011 3 KGs WT6 – 101012 3 KGs WT7 – 101013 7 KGs WT4 – 101010 5 KGs ITEM Filter would flush out the tasks more than 5 KGs, we would be left with below WTs: WT1 – 101007 1 KG WT2 – 101008 2 KGs WT3 – 101009 3 KGs WT5 – 101011 3 KGs WT6 – 101012 3 KGs WT4 – 101010 5 KGs NOTE: One Correction is in the sequence of above steps 5 and 6. WOCR first applies Item Filters and then SORT Rules. The Limits would create 3 WO now, since each WO can have a maximum of only 2 WTs: WO1 WT1 – 101007 1 KG WT2 – 101008 2 KGs WO2 WT3 – 101009 3 KGs WT5 – 101011 3 KGs WO3 WT6 – 101012 3 KGs WT4 – 101010 5 KGs WO1 WO2 WO3 What will happen to the 7th Warehouse Task – WT7: WT7 – 101013 7 KGs Since this WT is not able to satisfy the WOCR at WPT level EWM FINDS WOCR AT WPT LEVEL (WCR1) EWM FINDS WOCR AT ACITIVITY AREA LEVEL (WCR1) THE RULE IS SATISIFIED FINAL RULE DETERMINED YES NA YES WCR1 YES NA NO DEF NO YES YES WCR1 NO YES NO UNDE NO NO NA DEF IF THE STORAGE TYPE IS RELEVANT FOR MFS (STORAGE TYPE ROLE ‘J’), THE WAREHOUSE TASKS WOULD HAVE THE MFS FIELD ‘KZSUB’ AS X (MFS RELEVANT). IN THIS CASE, THE WOCR DETERMINED WOULD BE MFS. The yellow highlighted line above is satisfied, so the WOCR ‘DEF’ is determined What is this DEF Rule? Ans. It is an in-built SAP EWM Rule named ‘Default’ which ensures that the SORT Rule PIPA is used. The above Include /SCWM/LWHO_MAINF16 in the program /SCWM/SAPLWHO_MAIN is the place where this Default Rule is getting picked up from. To explore more, please put a breakpoint in the program before processing the delivery for warehouse task and order creation. What is SORT Rule PIPA used by DEF and UNDE? Ans. PIPA is a rule that has the field PATHSEQ assigned to it. In this example, we cannot see PIPA in action since PATHSEQ is same for all WTs. Let’s look at the example below, to see the SORT RULE ‘PATHSEQ’ in Action: The yellow highlighted field is ‘PATHSEQ’ which is mentioned in the SORT Rule PIPA (in configuration, see below image) SPRO Path: IMG-SCM EWM-EWM-Cross Process Settings-Warehouse Order-Define Sort Rules for Warehouse Tasks-Define Sort Fields. Now, please see below WO and associated 3 WTs in the GUI screen, check the sequence in which warehouse tasks are arranged to be processed: See, WT 100375 with lowest value of PATHSEQ ‘9’ is shown to be processing as first followed by WT 100376 with next value of PATHSEQ ‘22’ and lastly the WT 100374 with highest value of PATHSEQ ‘34’. What are these PATHSEQ? In the above image, the values against each bin are what is being referred to as the SORT Sequence (Technically in SAP, it referred to as the PATHSEQ). So, to summarize the WOCR’s DEF and UNDE (SAP Defined Warehouse Order Creation Rules) ensure that the Warehouse Tasks are processed by system in the way bins are sorted, from ascending to descending. How are Bins Sorted? They can be sorted during initial creation of bins creation using the transaction /n/scwm/sbst. I think this sorting of bins is dynamic and it keeps changing as the transactions are processed, and bins become empty and filled again. Inbound Sorting Versus WO Sorting (Work