on 06-11-2015 10:18 AM
Hi All
For a non WM managed storage location, when user creates an inbound delivery, the putaway quantity filed is disabled
I tried replicate the issue in test with same part and order, but the field was editable
Can anyone suggest, what would be the checks, which trigger the editability of the 'PUTAWAY QTY.' field in an inbound delivery?
Thanks
Yogesh.
Hi,
For WM that's not an issue, it's a feature.
In IM you confirm manually the putaway qty, in WM you do it automatically by confirming TOs.
So basically, in WM, when you create a TO in LT03 for a delivery number, you can confirm the qty picked in WM, and that is transferred back to delivery.
No manual update is possible in case of WM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, I missed the word "non" in non-WM managed location.
That makes sense now...
It used to happen to me in one decentralized WM system, but in the other way, decentralized WM location was offering manual entry of putaway qty.
Changing to another SLoc and reverting back to the initial SLoc didn't resolve the problem. Can't remember at the moment what I did to solve the problem back then.
I guess you tried changing SLoc to another one and then back to the original storage location?
It should help in most cases since the system refreshes all the data and redetermines the SLoc (IM/WM) and should correct the field "editability".
Sorry for the misunderstanding at the start.
Which t-code you are using while creating Inbound delivery?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
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.