on 05-16-2014 5:57 PM
Hello Expert,
I am facing one critical Issue with Storage Unit.
I have one TO which need to confirm. There are 2 batches for the material. Material is reacived from STO.
Now the problem is User created TO for partial quanity as per bacth.
For one batch say ABC it get confirmed and Issue with other Batch say, DCE.
I tried to cancel the TO as well. But it getting ABAP Dump.Message Storage unit already exist.
I checked in LQUA table there are 2 BIN for same SU.
How to rectify the Issue.
Please help!!!
Thanks.
I'm not aware of any standard way to solve this issue / remove the inconsistency, the only thing that crosses my mind is the most dirty method of all (if available on your system) SE16N => &SAP_EDIT for your LQUA table to sort out the quants, and LTAP/LTAK to make this TO confirmed.
Hell yeah, but please search the SCN thoroughly before doing that, try to find some standard solution but I doubt you'll have luck with that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is some confusion in your post, it would be good if you could give more details on those 2 sentences : "I tried to cancel the TO as well. But it getting ABAP Dump.Message Storage unit already exist. I checked in LQUA table there are 2 BIN for same SU."
Do you get the dump when you try to cancel the TO, or when you try to confirm the TO?
The quant table can certainly have several lines with the same storage unit if you have several materials or several batches on one storage unit. see the graphic in Warehouse Management at the Storage Unit Level
Can you attach the dump? Can you show a screen shot from LQUA and from the second TO?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jurgen,
Many Thanks for your quick response.
Yes, I am getting dump for both the two cases ,TO Confirmation as well as Cancellation.
Here is the screen shot attached.TO:5874759 is not getting confirmed.
ABAP DUMP:Storage Unit M54324036 exists already.
However TO:5875137 already Confirmed .
Same SU with 2 storage Bin.
Please help!!
I assume you want move the stock from storage type 910 to storage type 011 (same bin as shown in the screen shot).
but instead of merging the quants (and storage unit) as you might expect, SAP wants to create a new record in the target bin. And a second record in the same bin with the same SU number must not exist because this automatically leads to a dump.
look at it from a physical point of view.
A storage unit number is so to say the number of the pallet where the goods are stored .
you cannot have 2 pallets with the same storage unit number, that is not logical, each pallet has its own unique number. Hence you cannot logically have a pallet with number M54324036 in 2 storage bins.
If you want put a second receipt onto the same pallet then you have to use LT08 Expand storage unit.
Hi Tanmoy,
In standard sap storage type 910 is a 'GI Area General' and NON-SU managed. so ideally the SU number should not be there. if we can focus on why the SU number exist in LQUA for 910 then i think we will be able to get the right answer of your query
1) Can you please check the setting of SU management active/ not-active in SPRO---LE---WM---Master data for storage type 910, is ther any user exit active for that storage type
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
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.