Reversing Movement Type 344

Hi, Our’s is HU Managed Warehouse and someone tried to block Material ABC which is in a Bin and storage type XXX through MIGO 344 movement type. Delivery is created when MIGO happened and also a TO is created(manually) and confirmed. I am trying to reverse this but couldn’t find a way to do it. Please help.

Thanks,

Murali.

Hi, Our's is HU Managed Warehouse and someone tried to block Material ABC which is in a Bin and storage type XXX through MIGO 344 movement type. Delivery is created when MIGO happened and also a TO is created(manually) and confirmed. I am trying to reverse this but couldn't find a way to do it. Please help. Thanks, Murali.

Reversing Movement Type 344

Very Helpfull

User Rating: Be the first one !
Reviewer Asked on September 29, 2017 in SAP PORTAL.
Add Comment
9 Answer(s)

I replicated issue in my system. It worked perfectly without any error. Here is my take away.

 

1) With MIGO, transfer posting, mvt type 344, material is moved to blocked stock. Outbound delivery is generated with delivery type HTP( Transfer posting delivery). But when you see MMBE at this moment, stock is still placed in Unrestricted stock.)

 

2) Created TO with LT03, confirm the TO( Storage Unit) moved to same bin( Movement type 344 must have tick Post to same bin). (Material moved to 922 with stock category S)

 

And I reversed the whole process in same way. It happened successfully

 

Please check your storage location which you putting..

 

Best regards

 

Shailesh Mishra

Add Comment

Great to know that. Cheers:)

Add Comment

please share screen shot of LS26. Confirmed TO can be revered reversed with LT0G. However, LT0G checks availability of Quants. But, since this is HU managed location, LT0G will fail here. Please share error screen shot also.

Best regards

Shailesh Mishra

Add Comment

Hello Murali,

 

 

 

 

 

 

I demystified the logic of transfer Posting in a HU managed storage location. In my case, there was configuration in background which was conducting TO confirmation and PGI in background. For WM movement type 309, which was assigned to reference movement type 344, with TO creation, 2 business transaction happened.

 

 

 

 

 

 

1)TO confirmation(LT12)

 

 

 

 

 

 

2) and PGI(VL02N) happened in background for HTP delivery type and IM posting triggered from.

 

PGI is posted automatically when the transfer order is confirmed under setting in Customizing under: Logistics Execution–>Warehouse Management–>Interfaces–>Shipping Define Shipping Control–> Activity–>Define Shipping Control at the Movement Type Level. In my system the movement type 309 is set (Set the field Copy WM quantity to the value 2 ( Copy WM quantity as delivery quantity and post GR/GI ).

 

 

 

 

 

 

 

 

 

 

 

 

Hence, when you execute a posting change for the storage bin stock in a {HU+WM} managed storage location, below is the WM HU IM mehanics.

 

 

 

 

 

 

1) MIGO—344— system creates an outbound delivery with delivery type HTP which is called Posting change delivery.

 

 

 

 

 

 

2) 344 IM movement type is assigned to 309 Mvt type, and Transfer Order is automatically created. + and – Quants are generated in 922 interim storage type with stock category S.

 

 

 

 

 

 

3) TO confirmation(LT12)— Positive and negative quants were deleted from 922 interim storage type.

 

 

 

 

 

 

4) Post PGI VL02N which will trigger IM posting , stock will move from Unrestricted to Block.

 

 

 

 

 

 

Great learning !!!

 

 

 

 

 

 

Best regards

 

 

 

 

 

 

Shailesh Mishra

 

Add Comment

Hello,

Since you are in HU managed storage location, things gets complicated.

SAP says below line:

 

https://help.sap.com/saphelp_erp60_sp/helpdata/en/22/8dbf53f106b44ce10000000a174cb4/frameset.htm

–>A posting change delivery is created for posting-change movement types 344 (changing stock status from unrestricted-use to Block). Then, a transfer order is created for this posting-change delivery. Inventory management is changed accordingly when goods issue is posted for this posting-change delivery.

 

Lets wait for experts advice how to correct this. I am not sure about this

Best regards

Shailesh Mishra

Add Comment

343 for reversal. Migo–343—. Post. Outbound delivery generated. LT03—LT12–stock returned to unrestricted.

Best regards

Shailesh Mishra

Add Comment

Please explain how you tried to reverse it, what movement type you used and what “could not find a way” means in particular. Does it mean you got an error? or you could not find a movement type in the F4 list?

Add Comment

Issue is fixed, Delivery was not PGI’ed. I have done the PGI for Delivery which moved stock from Unrestricted to Blocked and then reversed it through MIGO 343, TO and PGI.

Add Comment

so the process is MIGO(344)—LT03—-(LT12)—PGI.. ?

I tested MIGO( Created outbound delivery with HTP delivery ty)–LT03—LT12.. stock moved to blocked.. I don’t know how it worked in your case.

 

Best regards

Shailesh Mishra

Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.