on 09-11-2008 7:31 AM
Hi Gurus,
Actual stock of a material XYZ is only 10 pcs. Some user wrongfully did some 999 supervision movement in WM through LT01 which resulted in stocks in LS24. Now we have about 200 nos. in 922 Post Area interim storage type i.e. reflecting as +200 and -200 nos. in 922 storage type under stock for putaway and pick quantity.
My question is how do I remove these +200 and -200 that are reflecting in 922 storage type so that the actual stock becomes 10 pcs in WM level as well.
Pls feedback urgently..thanks.
Hi Sunny,
Negative stock in 922 may be the result of IM bookings related to stock category change (e.g.). You should have a PCN in LU04 and processing it you will get two TOs. One TO is to m ove +stock from normal bin to eliminate the negative one. Other TO is to move +stock (of which stock category is different from the -stock) from 922 to normal bin.
If you can't find suitable PCN in LU04, or your users did manual transfers, you have to solve this issue manually.
Search for +stock in normal bin that has the same characteristics as the - stock in 922 and move it to 922 by LT01/LT10.
Move yhe positive stock from 922 where it is physically by LT01/LT10.
Regards,
Csaba
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This is strange to me.
How can your user create stock (quants) in WM by LT01? I don't think it is possible...
If your stock in MB52 is 10 nos and you can see in LX02 10 nos in normal bin, and 922 + and - 200, and all your TOs are confirmed, the quants in 922 should result in 0 and disappear...
Are your quants in 922 of the same characteristics (batch, stock type)? What shows LX02? Check the WM movements in LT22 and please report it.
Thanks,
Csaba
Hi Csaba,
Yes MB52 shows 10 pcs stock only. The batch and stock type are the same too. LX02 does show +ve and -ve 200 pcs. All TOs related to this are confirmed. There are about 3 to 4 TOs pertaining to this transaction done by user and WM movement types are 999 and 561.
Pls suggest.
Sunny
Edited by: Sunny on Sep 11, 2008 9:14 AM
when you do the tranfer from the +ve to the -ve quant, you said you get a message that quant is not consistent with other quant (hence there must be a difference between the 2 quants in LQUA), what is the message number ?
double click the message and tell me the message number.
A message like you mentioned earlier does not exist.
I can only find following 2 messages:
L3 018 Quant & not consistent with other transfer order data
and
Quant data not consistent with storage unit management
if it is L3 018, then you made a mistake in TO creation.
the TO item data must match with the quant.
dont look just at quantity and bin number, storage type and area, then quant number itself has to match.
(if you execute LT01 and hit enter,then SAP creates this target item itself, if you then only change storage type and bin and forget to erase the quantnumber, then L3 018 message will come up)
The case where there are no difference in characteristics is actually in the Production system.
I was trying out your suggestion in the Test environment where I got that messsage. Yes, in test, there is a difference in terms of R stock between the two quants. I couldnot find any replica in test where there are no difference in characteristics. Since I have to ultimately resolve this issue in Production I made the comment that there are no difference.
Pls assist.
Hi,
Please use LS26 to see what exactly is in 922 area. Normally, if stock categories are equal, then it should level out. By double clicking on the quantity in LS26, you will zoom in and see what is in 922. Then either move with LT01 the + quantity to the - quantity. In case batch management is active and the batches are different, then use migo to transfer.
Regards,
MdZ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.