Lock-entries in MM02 prevents booking from storage location to storage location

[Former Member]

Hello everybody,

I have the following problem when acknowledging a TA (Transportorder):

Booking from goods receipt (LGORT 100) to high-bay (lgort 10). Because lock entries in the material master (eg. When a user in the MM02 is) the TA is indeed acknowledged, that the material is accurately recorded in the high-bay, but in inventory management remains a positive (WE lgort100) and a negative quant (WE lgort10 ) are on the goods receipt. If no lock entry exists when confirming the booking is fine and the two quants from the goods receipt immediately disappear.

The problem is but the material barrier is very often set in operation, as many staff there daily make changes and I would like to know how it is possible that the transfer is still performed correctly without which they must always be initiated manually afterwards (too many positions per day).

I'm thinking of something which, although the stock remains first on the 100, as described above, and is then adjusted on a regular basis as soon as the material lock is removed. Now Playing existed in store on the 100 getting bigger, although it is incorporated and acknowledged. the file in attachment shows the miss in the incoming goods. The 46 pieces are actually already in the high bay (LGORT 10), but are assigned to lgort 100 in the goods receipt.

Thank you, all the best.

[Former Member · Accepted solution]

First thank you all for your help. Now i am a little bit more prepared to solce the problem!

Got another question that could be the important key for solving the issue:

We use in customizing the "Late Material Block". So that means that only when i press save, the material is blocked for a short moment..ok.

BUT why are there three entries in SM12 (Overview lock entries) just when i open the MM02. That means for me the material is blocked since i opened the MM02. Isnt that a controverse to the configuration "late material block"? Whats wrong with my system, why did it block even when i open MM02? In that case the material is blocked for a very long time since the user closes the MM02, and that could be hours. seems pretty sure that i've got problems to confirm my TO when user block the material for that long time.

best wishes, Jan

[JL23 · Accepted solution]

the late material block is used in goods movements, but is not related to material master maintenance.

e.g. when you start with MIGO and reference a PO with a material then at this very moment the material got locked and another user could not enter a goods movement for the same material. With a late block several users can enter movements in parallel and the material is on blocked when one clicks save. But if someone opens a material master with MM02 then the material is blocked for updates from anybody else. There is no late block for material maintenance.

[Former Member · Accepted solution]

Ah okay, thank you, i didnt know that. But isnt this exactly my issue, the mm02 blocks the movement from 0100 to 010? I think the TO need to make changes in the material master after confirmation and when user block it while they are in the mm02, the quant mocement could not be finished right? I wonder how to solve this conflict. Sure i can finish the uncomplete booking with lq01, but there are thousands booking a day 😕

[JL23 · Accepted solution]

No it is not your case, I said late blocking has to do when people are posting movements for the same material. Late blocking will not resolve issues when somebody blocks the material with MM02.

From my point of view is ongoing material maintenance not a usual approach. Of course it can happen that some fields need to be changed occasionally, or the material has be extended to a new plant, but this should not really lead to daily issues for WM postings

Have you already analyzed what the people change in the material master, maybe they just use MM02 instead of MM03 when they display the material master

[Former Member]

Finally found the reason. The user didn't have the right authorization for the posting from "lagerort to lagerort", thats why it stucks. Thanks for all your supply.

[Former Member]

This is the LS26 after creating the TO from the TB (LT04).

by the way, this link describe exactly what i am trying to do:

Goods Movements from the GR Area - Warehouse Management System (WMS) - SAP Library

The main problem is, when i lock the material with MM02 then, and only then, the negative quant and the prositive quant in 902 doesnt disappear.

In SPRO, is this the right configuration for 0100 (Graphic SPRO attached)?

[JL23]

I am bit confused about this: " My next step now would be to create a TO in WM out of the TR to send the 500 pieces to main storage bin (which is 010 defined in customizing)."

Looking at the LS26 it just tells me that you removed the quantity from storage location 0010

while you actually added it earlier to storage location 0100

this means the TO that you created (screenshot missing) is from location 0010 storage type 902 to location 0010 storage type HRL

I wonder if this TO is really in reference to the TR 120795

And where exactly do you enter the different storage location?

[former_member234835]

This message was moderated.

[former_member234835]

This message was moderated.

[Former Member]

I doubt plant material lock is relevant since it would prevent the MIGO GR from happening. It seems the destination storage location from his 101 is simply different then the source storage location in the TR created from the 101.

perhaps an issue with movement type source/destination.

Wondering what configuration bucket is showing in the "SPRO" screen capture (cannot read that language)...

[Former Member]

I created the TO after the GR 902 is booked. 0010 is the default storage location, so the TR automatically books from 902 0100 to HRL 010, with a negative quant in 902 010.

[Former Member]

Hey, sorry for delayed Answer and thank you for your reply.

Here are the screens of TR and the TO BEFORE TO Confirmation.

[Former Member]

Part 2

[former_member234835]

This message was moderated.

[JL23]

The SPRO entry is from Customizing for Warehouse Management under Interfaces > Inventory Management > Define Storage Location Control > Assignment Control of "Plant/Storage Location – Whse Number"

And I think he is managing the interim storage type 902 in a separate location as described Posting Changes Between Storage Locations - Warehouse Management System (WMS) - SAP Library

And since he starts the process from WM a MM movement has to be created in background.

Since this MM movement needs to change the storage location stock it has to lock table MARD exclusively. If other people maintain material master in exact that time then it is clear that the posting change fails.

I don't think that there are much options to avoid that as a certain time the material master has to be locked.

[Former Member]

I Posted it in your last comment

[Former Member]

Exactly. The transfer to 010 works fine as i did it, but only when somebody locks the material (mm02) at the same time i am confirming the TO, the quants from 902 do not disappear. what i need is something like a background job that clears the negative quant from 902 after the material lock is gone (e.g. the person who locked material in mm02 now closes the transaction). I need something that finish the uncomplete booking asynchrone.

[former_member234835]

This message was moderated.

[JL23]

I have never done this scenario. How do you complete it manually? Knowing this may help to get closer to a solution

[Former Member]

I do this in LQ01, there i can clear the negative quant in 902

[JL23]

I think you should schedule RLLQ0100

[former_member234835]

This message was moderated.

[JL23]

How do you create these  TOs?

It looks like your process starts in WM, while the usual process starts in MM.

[Former Member]

First we create a goods receipt in 902 out of MIGO, then we use the material document in transaction lt06 to create the TO. And confirm the TO with lt12. It works fine if there are no lock entries.

[JL23]

Sorry but that can't be the full story.

In a standard process  you do MIGO into a WM managed storage location  and you get a quant in 902 along with a TR.

You then convert this TR to a TO which removes the quant from 902 and creates a new quant in the target bin.

This does not at all change the storage location from 100 to 010.

[Former Member]

Thanks for your answer. yes, thats right what you wrote. But when i create the TO in 902 appears a negative quant in 010 as you see in the picture, then i confirm the TO and the negative quant disappears, also the positive quant in 100.

In the target bin there appears the quant correctly in 010. But only if MM02 locks the material while i confirm the TO the two quants in 902 do not disappear, in all other cases it does. I dont know why the quants in 902 (46 in 100 and 46- in 010) do not disappear. Sorry for the difficult question 😕

[former_member234835]

This message was moderated.

[JL23]

I saw this picture and that is why I am confused about your scenario in general.

A storage location does not change on its own in WM, you either have to use transaction VLMOVE or the process starts from MM movement 311.

A negative quant is created if you remove something from nothing. (e.g. with a manual TO creation in WM)

It is not even certain that a storage location change has to create a TO. 

If both storage locations are using the same warehouse, then a storage location change without needing a physical movement  can be achieved with a posting change notice (transaction LU04),

So it would be really helpful if you could provide the exact steps (transactions and movement types) taken from the goods receipt till the end.

[Former Member]

So, i made some Screenshots after doing MIGO (902 which is storage location 0100). Movement was 101.

Now the Product is stored in 902 correctly (500 pieces). My next step now would be to create a TO in WM out of the TR to send the 500 pieces to main storage bin (which is 010 defined in customizing).

After confirming this TO I would pretend, that the 500 pieces had disappear in the 902 and will now be in 010 main storage.

I hope the screenshots will help you. I didnt create the TO at this time, just booked MIGO to 902 and the TR was created automatically. So the product is now on storage location 0100. The next step is the storage location movement, because the product goes from 902 (0100) to main storage (010).

Thanks