transferring stock from unrestricted to customer-stock 412 E => WM posting change 922

[Former Member]

Hi

When I transfer stock from unrestricted to customer-stock or vice versa (412 E / 411 E) using MB1B for example,  if the stock happened to be in one single bin, the system does the transfer of quantity properly in MM and preserves the storage-bin in WM.  But if the stock happened to be in multiple bins in WM, then the systems seems to transfer the stock into storage-type 922 (in a dummy bin)

first example that works fine:

Material MMMMM: quantity 10 all in storage-type 940 bin: ABCD

In MB1B I do a movement 412 E for material MMMMM to transfer 6 from unrestricted into customer-stock

response: Material MMMMM: quantity 4 in storage-type 940 bin: ABCD  and now quantity 6 in storage-type 940 bin: ABCD  (with special-stock E)

BUT.... below = example that I want to change:

Material MMMMM: quantity 6 all in storage-type 940 bin: ABCD and quantity 4 all in storage-type 940 bin: EFGH

In MB1B I do a movement 412 E for material MMMMM to transfer 6 from unrestricted into customer-stock

response: Material MMMMM: quantity 4 in storage-type 940 bin: ABCD  and now quantity 6 in storage-type 922 bin: TEMP  (with special-stock E)

Is there a way to preserve the bin/storage type even when the stock happen to lie in multiple bins?

Thank you

Bob

[JL23 · Accepted solution]

I think you are missing an important part, maybe it is setup as an automatic background activity that you do not know about.

Any such movement in MM creates a posting change in WM.

And it will always use the 922 storage type for that to show a positive and negative quant, the positive with the target information, the negative quant with the source information. And along with that a posting change notice that has to be processed with LU04.

If it only 1 bin is affected then an automatic background job can take care about processing of posting change, but if you have multiple bins and partial quantities then a human has to select from which bin is how much material affected, this can't be done automatically by a job.

[Former Member · Accepted solution]

Hi Jürgen L

Thank you for your quick reply.  You are right I am probably missing many important parts when it come to WM.... most of the 20 years I've been consulting for SAP, I pretty much always managed to stay away from WM  😉  

But just to be clear, please let me explain here what was my thinking... All I wanted to do is to "reserve" a few material to a Sales-order... I don't want to physically "move" them from one bin to another... I didn't want a human to have to use a transaction or a RF-gun.

We have a “Z” program that runs a few times a day and based on a few “rules” (like Material availability and today's-date vs the delivery-date on the S/O) it automatically “transfers” certain stock quantity from unrestricted-stock to customer-stock (simply to reserve the material for a given S/O… we don’t actually want a human to move stock around)

This type of “Z” program is something I have done previously at other clients I have worked with but never with WM activated I guess (so I guess I understand what you’re saying thought, it’s a similar problem as if my material was “batch” managed or serialized)

So I guess what I will need to do is put more “smart” in my “Z” program so that when this 922 happens, I can somehow move it out of 922-INTERIM and back into their original storage-type/bin.  Can you please help me with the transactional steps that would be required to do such a thing please… Once I have identified which bins I want to put them back into, do I simply have my “Z” program create a T.O for it and then have my “Z” program confirm the T.O automatically??? Is there another better way to go about all this?

Thank you

Bob

[JL23 · Accepted solution]

SAP differentiates between posting changes and transfer orders. Posting changes are used if nothing has to be moved, while transfer orders are the medium if a human has to move some material between bins.

What you described is a transfer posting, it just changes the ownership or an allocation or even a batch number, but the stock will not be moved physically.

Still SAP has not use the interim storage types to document such kind of transfers (posting changes) within the WM system. SAP does not just exchange a value in a quant.

Actually pretty similar to MM, where you also have 2 items in your material document, a reduction from the general stock and an increase of the sales order stock.

Such posting changes have to be processed in LU04 transaction.

In this LU04 transaction you can also find historic documents, those documents which you did not see in case the stock was from a single bin in your example, but check it, you can see that those also used the 922 storage type.

You need to talk to your WM counterpart to know about your local customizing.

You should also try yourself the LU04 or let the WM guy show it to you, so that you can see what you have to do there, as this is what you would need to replicate with a function module http://help.sap.com/saphelp_46c/helpdata/de/c6/f83a294afa11d182b90000e829fbfe/content.htm