SAP WM- Process, Functionality, Scope, Benefits, Advantages, Disadvantage-Complete Reference-Part 11 (Stock Movement between HU Managed/Non-HU Managed/WM Managed/Non WM Managed/ No HU-Non WM/ HU-WM Managed Locations.

Many times we need to came across Dilemma/Critical situation while moving the stock from WM-HU Location/IM-HU Location/ Non HU WM Location/Non WM -HU location. what step to be followed or what transaction to get user to post the Stock movement when WM/HU/IM and it’s combination of locations involved. During my initial Days I got stuck how to approach it. so I decided to frame a blog based on the movement of stocks between the locations and hope it is useful to all consultants. I have summarized the locations movements in table format also. Please comment if anything given here is mentioned wrongly, it is highly appreciated. 🙂 🙂

When can we say HU managed location and having partner location defined ?

perfect answer would be for each storage location, We maintain the handling unit requirement and the default values for creating a delivery. We can override the default settings at plant level with more specific default settings at storage location level. When We set the HU requirement indicator for a storage location, We can only make stock postings if you specify the handling unit. If We do not specify the handling unit, the system does not create a material document when We make the posting but creates a delivery document. Since the stock in a storage location that is subject to a handling unit requirement is packed in principle, We must maintain a partner storage location for transactions such as unpacking. Use a storage location in the same plant as the partner storage location that has the same or no warehouse number.

Partner storage location of the handling unit- storage location that is used in the standard system for stock transfers from or to a storage location that has handling unit requirement. If we want to increase or reduce the stock of a handling unit in a storage location that has handling unit requirement, this storage location is used as a partner storage location if we do not specify another storage location.

Handling unit requirement- a handling unit requirement applies to this storage location. If we set this indicator for a storage location, the system does not create a material document when it carries out a posting, but creates a delivery via Shipping.

SPRO- Logistics general- Handling unit management- Basics-Materials management- Inventory Management- HU Requirement for storage locations and Default Value for Deliveries.

 

Process steps for Moving Material within the Different Storage locations

Scenario 1- Moving stock from HU+ WM location to HU+ WM Location.

use VLMOVE and create Delivery
Create TO for the Delivery
Confirm TO
VL32N- PGR Delivery

Scenario 2- Moving from HU+WM Location to Non HU+WM

Post MB1B, system create outbound delivery
Create TO (LT03)
Confirm TO(LT12)
Post PGI for outbound delivery created step 1. 311 – Material doc is Posted.
LT06- Create TO for this Material Doc in Step 4
LT2- Confirm TO

Scenario 3- Moving stock from HU+WM to HU+Non- WM

Please use VLMOVE to move the stock from HU+WM to HU+Non- WM

Scenario 4- Moving stock from HU+WM Location to Non HU+Non WM Location.

VLMOVE
Delete the HU

Scenario 5- Moving stock from Non-HU +WM location to HU+WM Location

MB1B- Destination storage location should be the partner storage location of HU Managed Location.
LT06- TO created for Material document
LT12- Confirming the TO.
HU02- pack the Material
VLMOVE- to move from partner location to the HU managed Location and click the Delivery.
LT03- for creation of TO with reference to Delivery.
LT2- TO Confirmation.
VL32N- Post the PGR.

Scenario 6- Moving stock from Non HU+WM location to Non HU=WM location.

MB1B-  Creating movement will generate Material document.
LT06-  Creating TO with reference to Material document.
LT12- Confirm TO.
If you want to do bin to bin transfer within the same Warehouse use LT09 Transaction.

Scenario 7- Moving stock from Non HU+WM location to HU + Non WM Location.

MB1B- System creates Outbound delivery.
VL02N- Pack the Delivery
LT03- for creation of TO with reference to Delivery.
LT12- TO Confirmation.
VL02N- Post the PGI.

Scenario 8- Moving stock from Non HU+WM location to Non HU+ Non WM Location.

MB1B- moving the stock from Non HU+WM location to Non HU+ Non WM Location will create Material document.
LT06- TO created for Material document
LT12- Confirming the TO.
—————————————————————————————–

Scenario 9- Moving stock from HU+ Non WM location to HU+WM Location

VLMOVE to create Delivery
LT03- Creating TO reference to Delivery
LT12- Confirm TO

Scenario 10- Moving stock from HU+Non WM location to Non HU+ WM Location

HU02- Unpack the HU. the stock will get posted to Non-HU/Non-Wm Managed location (Partner SLOC).
Follow the process of (Non HU+ Non-WM) to (Non HU+WM) Process.

Scenario 11- Moving stock from HU+ Nom WM location to HU+ non WM Location.

In VLMOVE- Click Post Material.

 

Scenario 12- Moving stock from HU+ Non WM Location to Non HU+ Non WM Location.

Transact the Movement using VLMOVE
In HU02 delete the HU.
—————————————————————————————–

Scenario 13- Moving the stock from Non HU+ Non WM Location to   HU+WM location

In MB1B -system create Inbound delivery when try to move the stock.
LT03- Creating TO with reference to Delivery.
LT12- Confirming TO.

 

Scenario 14- Moving the stock form Non HU+ Non WM location to Non HU+WM Location

In MB1B -system create Material document when try to move the stock.
LT03- Creating TO with reference to Material document.
LT12- Confirming TO.

Scenario 15- Moving the stock from Non HU + Non WM Location to HU+ Non WM Location.

In HU02 Please pack the HU in source Storage location
then do VLMOVE

Scenario 16- Moving the Stock form Non HU+ Non WM Location to Non HU+ Non WM Location.

Please post transaction in MB1B to move the stock from Non HU+ Non WM Location to Non HU+ Non WM Location.

 

I hope the details shared in this blog is more useful and i am normally facing this kind of Question from our friends and bloggers. Actually from the point of my self interest i have tried to move the stock between the location that helps me to write this blog.

Please find my earlier blogs in SAP WM. I hope it is more useful to SAP MM WM SD LE PP QM PM Consultants and new consultant who wish to pursue their career in SAP WM and LE and Business Persons who really interested in SAP Learning. Thanking you All and to SAP for presenting a platform to share the knowledge. Great !!! 🙂 🙂

 

https://blogs.sap.com/2017/03/31/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-1/

 

https://blogs.sap.com/2017/04/02/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-2/

 

https://blogs.sap.com/2017/04/04/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-3/

 

https://blogs.sap.com/2017/04/06/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-4/

 

https://blogs.sap.com/2017/04/07/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-5/

 

https://blogs.sap.com/2017/04/19/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-6-cut-over-activities-details/

 

https://blogs.sap.com/2017/04/20/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-7-comparing-4.6-c-ecc-6.0-wm-screens/

 

https://blogs.sap.com/2015/01/20/sap-warehouse-managementstep-by-step-configuration-document/

 

https://blogs.sap.com/2017/04/21/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-8-questionnaire-for-wm-requirements-understanding-understanding-clients-business-process/

 

https://blogs.sap.com/2017/04/16/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-9/

 

https://blogs.sap.com/2017/04/26/sap-wm-process-functionality-scope-benefits-advantages-disadvantage-complete-reference-part-10-idocs-used-in-sap-wm/

 

 

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply