|
We are also on 405 CD and we also have parts that are manufactured in one facility and used as raw materials in another, so they are coded as manufactured so that we CAN make them in the right facility. What happens, due to personnel turn-over, is new staff who are not yet comfortable or familiar with our item # type planner code etc. coding systems, at risk of releasing a shop order for either a purchased item, or an item that actually gets made in a different facility. We saw no way to stop the actual creation of the bad shop orders. We modified the program that prints the shop order paperwork SFC520 so that if and when an inappropriate shop order is generated, the paperwork explains the problem and instructs in what is to be done, which includes closing this inappropriate shop order. I do not believe we have had any cases of us trying to place a purchase order for an item that should belong in a shop order, but we have had items that move between purchasing and manufacturing coding because we find one way or the other is less expensive, and it is very easy to mess up the costs in the process.
This question stems from a recent problem. We're on 4.05CD. Recently, an item was entered on a customer order. It was coded as a purchased item, but a shop order was keyed by mistake. The item then disappeared from our home-grown MRP system's reports, since the demand had been met. Is there a place, in BPCS, where I can preclude placing the 'wrong' type of order? In other words, if it's coded as a purchased item, will the system tell me and not allow (or at least flag as an error) a shop order? Thanks - Rob
Al Macintyre BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/ Al at home http://ryze.org/view.php?who=Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
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.