|
Back in ver 3.5? we had a problem with backflush transactions randomly being dropped, doubled, tripled etc. We finally tracked it down to 1 operator who moved from terminal to terminal as needed, and transacted at different times of the day. She had programmed her keyboard to enter some static information, but had programmed an extra 'enter'. This set a flag in FLT that said she was reporting by part number because the shop order field was blank. She keyed in the rest of her information, which included a shop order number. The original flag was not reset. Deep in the bowels of the JIT processing, the code stopped processing by a shop order number, and started looking at this flag, and got very very confused. SSA did issue a BMR for this. Don't know if this helps, as every FLT record from the problem record on, was processed with missing, double etc transactions.
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
