|
Thanks Chick, your first paragraph describes exactly what I'm seeing in testing. I'm just not sure how we should get it to back the LRDTE up one day. I could do it with Move days, but that means every router of every item (we use a lot of muliple routers for the same part). It would be quite a project and require a LOT of ongoing maintenance. Paul -----Original Message----- From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On Behalf Of Chick Doe Sent: Wednesday, December 11, 2002 8:44 PM To: bpcs-l@midrange.com Subject: RE: MPS - Customer Demand and General ECL Date Questions if i remember properly we ran into a problem with lead times. when mrp (and probably mps) du their planning they use the 'lead time' to determine when the components are due. but when you actual create a shop order sfc500 calculates the due date based upon the shop order due date and the run, setup, move, and queue hours in the routing. this caused us some major discrepancies where mrp was planning components for one due date and then suddenly that due date changed once the real shop order was cut. i know we went through an effort to try to synchronize planning lead times to real routing lead times, but that was some time ago and it's probably out of snyc again. perhaps this is one contributor to the 200+ page mrp exception reports. as far as the mrp exception reports go they are too voluminous. we wrote our own summary version with a filter in it. if we set the filter to 10 days, they won't report any reschedules that mrp is recommending that are 10 days or less from the existing order due date. (mrp stores it's recommended reschedule date in the FSO and HPH files and you can easily access this and the current due date to write you own reports. chick doe barton instrument systems >>> laflammep@kennedydc.com 12/11/02 02:15PM >>> This is a multi-part message in MIME format. -- Hi Judi, To clarify my question - should a lead time set on the end item for an item master (IIM) (not planning by facility) effect the MPS planning for an MPS item? What I'm seeing is that once I say an item is an MPS item using the M code on the Item Master (IIM) the system will not consider the lead time field in the item master. Instead, it looks solely at the BOM and Router to determine when a particular shop order must be started to finish when needed. Now if my BOM components of that end item have lead times, the system may be factoring that in - I didn't get that far yet. Paul -----Original Message----- From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On Behalf Of Judi Svoboda Sent: Wednesday, December 11, 2002 4:38 PM To: bpcs-l@midrange.com Subject: RE: MPS - Customer Demand and General ECL Date Questions Paul, if I understand the question, lead time days is for purchased as well as manufactured items. If you have different levels in your BOM need to enter the lead time for each level according to actual time to produce plus wait move and queue. Judi Svoboda Ridewell -----Original Message----- From: Paul LaFlamme [mailto:laflammep@kennedydc.com] Sent: Wednesday, December 11, 2002 10: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. -- [ winmail.dat of type application/ms-tnef deleted ] -- _______________________________________________ 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.
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
