on 01-23-2008 4:10 PM
Dear experts,
We have detected that after flagging for deletion a material at a storage type level with transaction MM06, we're still able to transfer stock to that storage type with transaction LT01.
Is it normal situation?
Do you know any way of avoiding this? Is archiving the material at that storage typthe only way?
Thanks a lot!
Best regards,
Mireia
Hello Mireia,
I'm not an expert at all but we had / have / face similar problems.
Part number changes occure frequently at our company and we mark the material master records (that are out of use) with DF to avoid confusion.
In IM it works, we cannot make (e.g.) inventory for the goods of which material master records are marked with DF but in WM we haven't been able to find any solution to prevent WH-workers from making inventories for such kind of materials.
Please check:
If you succeed in finding something to achieve this or someone could give a good advice I would also welcome...
(I'm afraid there's no exact solution since even Svetja and Frenchy couldn't tell me a solution - and I think their WM knowledge is very high - of course it doesn't mean it cannot be solved / you cannot solve it)
I would also welcome if someone from SAP AG would take care of this thing...
BR
Csaba
Edited by: Csaba Szommer on Jan 24, 2008 7:42 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a workaround solution for this:
1)MM material flagged for deletion takes care of the material only till sloc level.It does not restrict movement of material at storage type level.
2) You can use tcode LS08 to block the storage bin .Find out in which storage bin material is lying by using stock status report by material.
Then block those storage bin using LS08 tcode.
Hi both,
Thanks for the info.
When we flagged for deletion the material with Tcode MM06, we did it at storage type level, not at storage location level...
The wourkaround you propose would work if the bin was uniquely used for this material, but we cannot block the entire bin since it will be used for other materials.
I did not find any other solution than archiving the material at this storage type...
BR,
Mireia
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.