|
Yes we did! If I remember correctly, this was caused by text records being left in the text file after running the Work Order Archiving job. The text for archived work orders is left in msp02 and not moved into the archive file (msp02a). At the time we were at v3.3, obviously it has not been fixed in 3.5.2b (I assume that is where Jeff is at). We originally had this problem right after we converted to Sys21 from Mapics. One product line was last to go live and we were creating work orders in Sys21 that paralled the demand in Mapics. A combination of the Mapics numbering system and records being left in msp02 after archiving work orders caused this. Apparently, when the Sys21 work order numbers duplicated a manual number ... BOOM!, Start laying track because the train is coming! (to use Jeff's analogy). We manually removed the orphaned records from msp02 after the runaway job. We now don't allow the planners to create work order numbers off the top of their heads, they use the Sys21 numbers (this is a procedure, not a mod).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
