Quote from GasGiant on 06/30/11 at 13:48:15:One thing that happens to us (too often) is people killing a process in the middle of a WO-I transaction. We use Lot or Serial numbers on nearly every finished good. If the user tries to run WO-I and then get's to the Lot/Serial entry section and does not have the information, we have had issue with people using CTRL-ALT-DELETE and ending the task. At that point in the process the UOH has been updated with the full quantity entered as completed, but the transaction has not been posted. We have trained our users, over and over, never to end task in the middle of a transaction, but it keeps happening.
If you have duplicate entries in MTICMSTR then you need to use Maintain Database to remove the superfluous entry. The system cannot tell which one is erroneous.
Resurrecting an old thread as this is still haunting me. After years of trying to figure it out we eventually did find a repeatable issue. If we go to produce a work order and someone else has that item open in another screen we get a message that the record is locked by another user with the option to cancel or retry. Even if we hit cancel, it adds the amount the work order is for to the master level but not the transaction level. If we try again later and still get the record locked error, cancelling will again add that amount to master but not transaction.
I have to run SM-J-C often on items which is time consuming. My predecessor once accidentally ran it on everything which created a bunch of other issues so I like to only run it on single items (unless I'm only doing report mode).
I end up in here for hours on a Saturday or firing it up in the evening and walking away, having someone close it out when they get in in the morning.
Anyone know if there is a way to fix it through maintain database or is it touching so many tables that doing this would make things worse?
Even if it would stop creating the master level quantity when we get the message and cancel out would solve a lot of the problems.