|
I got my engineers to take a look at the BOM on my list of 35 parts which had a UM of EA & item class that I thought should be whole numbers but were not & the word came back that there is nothing wrong with BOM on these parts & it was suggested that I check out a particular shop order ... well sure enough, a month ago someone entered a labor transaction via JIT600 claiming that we made 7.5 sub-assemblies, and the BOM dutifully consumed 16 sub-components generating a slew of lower items now not in whole numbers. We are assuming this was either a reporting or keying error. While this does not explain all 35 problems, it does open another can of worms. It transfers the focus ,,, we will look at lot sizes & order policies, although I am sure there are other factors influencing whatever values we have there now ... I sure hate to add another report to the infinity of LIST THIS SCENARIO TO SEE IF WE HAD GARBAGE IN that needs to be cleaned out ... in this case, list all labor transactions that reported something other than whole numbers, when we really want to prevent the input of fractional labor ... I guess I could modify SFC600 if a relevant co-worker will tell me how I can tell when this is valid input ... I figure that we have a FEW exceptions, I just don't know what they all are. The only one that is obvious to me right now is a transaction to fix the 7.5 while this order is still open. The particular order is for 510 units. Operation 100 shows 492.5 made so far, with operations 200 & 300 made 509 ... when we look at the summary picture it looks like the order is about ready for closure, somewhat concealing the idiot fraction. I have a vague recollection of some kind of WIP pull-through deal, where the artificial intelligence recognizes that labor transactions can be reported in the wrong sequence or go missing, in which the only way operation 200 could have made 509 was for operation 100 to make 509, so we need some input to fill the gap between 492.5 and 509, but perhaps that only applies to the labor & not the inventory. Also I had to write a fix program a few weeks ago for some wrong default settings in some files, so it is remotely conceivable we turned off this built-in repair system before the garbage arrived. Thanks for the great insight. Al +--- | 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.