|
> We're on V6.04. Having problems where the total allocated qty in IWI > getting out of sync. Any one else having this problem? Check the archives. This is a systemic problem on most all versions of BPCS which has often come up in discussion. There are ways to erase the appearance of the problem without really fixing the problem. > We are on BPCS 405CD. If someone does order maintance and deletes a line > with allocations, the allocations seem to stay. We are also on BPCS 405 CD. It would be nice if the system parameters about how long we want to keep customer order data really connected to anything, like the BIL900 that existed on BPCS/36. > Also on Shop Orders and FMA, if operation and or order is complete it > would be nice if additional allocations would drop off. It is my understanding that if you do substitutions, you need to do maintenance to the shop order before any reporting of them, which gets to be a royal pain if JIT6 tickets are reported out of sync with the deviations. Our CST900 takes 2 hours if it is soon after SYS120 which takes 3/4 hour dedicated. Our CST900 takes 5 hours if it has been a week since our last SYS120. On BPCS/36 we used to always have to do an allocations reorg after every CST900 because closing shop orders was guaranteed to tangle up the allocations. I had thought that was fixed on BPCS 405 CD, but this was by taking someone's word for it & the someone might not have thoroughly understood the problem. Alister William Macintyre +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
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.