|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] I recommend developing queries off the order and planned order file and have the schedulers go to MRP300 for details. Unless a company has money for an army of schedulers, using vanilla BPCS MPS/MRP reports are hard to achieve goals. Mike Hoffman Senior Manufacturing Specialist Crowe, Chizek & Company, LLP http://www.crowechizek.com/scg phone: 440.460.1318 fax: 440.460.1302 "Rob Stagis" <stagis@fansteelvrwesson.com> Sent by: bpcs-l-admin@midrange.com 12/11/2002 04:33 PM Please respond to bpcs-l To: <bpcs-l@midrange.com> cc: Subject: RE: MPS - Customer Demand and General ECL Date Questions No solutions, Paul - sorry. I'll watch this thread wwith interest. I'm tunring on MPS/MRP as we speak.....my exception reports are hundreds of pages as I clean data up. What reports do your scheduling people use? The 'detail' and 'exception' reports are hugemongous. (MRP200 and -240) -----Original Message----- From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On Behalf Of Paul LaFlamme Sent: Wednesday, December 11, 2002 11:57 AM To: bpcs-l@midrange.com Subject: MPS - Customer Demand and General ECL Date Questions We're using BPCS V405CD(ptf2) and getting ready to begin using MPS/MRP. We're a discrete order job shop Die Cast manufacturer (Order Policy H on MPS items) and will rely on Customer Orders to drive the MPS. I see that it is the LRDTE field (Request Date) in ECL (Order line file) that feeds to the MPS. The order entry department will back the transit (shipping) time from our shipping dock to the customer's location and enter that date in the LRDTE field. The challenge I have is that Shop order due dates, and planned order due dates as they appear in the MPS system are the same date as the REQDATE. This means that the system won't plan the shop orders to be finished till some time during the day that the order is supposed to ship out. Is the REQDATE really meant to be a "Request to complete manufacturing" or a "Request to Ship?" If it is in fact, a request to complete manufacturing, would I simply back the date up by one day. I'd love to hear from other BPCS users as to how their system is communicating customer requirements to manufacturing's MPS. Another way I thought I could handle it is by adding a 1 day std move time to the last operation. But this would mean changing the router of EVERY Item and every alternate router as well. Lead time is for purchase order items, correct? Also, how are the Schedule Ship Date LSDTE & Schedule Receive Dates LSCDT used by the system? Should these be updated after an MPS committment? If so, by whom? Thank You! Paul LaFlamme Manager of MIS Kennedy Die Castings, Inc. 508-752-5234 X3044 _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l or email: BPCS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l or email: BPCS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message may contain privileged or confidential information. If you are not the intended recipient of this message, you may not make any use of, or rely in any way on, this information, and you should destroy this message and notify the sender by reply email. Any opinions or advice contained in this email are subject to the terms and conditions in any applicable client engagement letter or service agreement.
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.