|
We are running V6.04 April cum with the latest cst500 and cst600 bmr's. I am currently rolling stds for our new year and finding inconsistence in the cpflvl field. On investigation we have been having this problem all year rolling moving stds with set up, run and overheads into the cpflvl on the higher level(material appears fine). The problem appears to be random and affects only a small percentage of our items. I am fast running out of ideas, I have already rebuilt the CMF cost file from cfcbkt 1 ( making sure cfcbkt 0 agress with 1). Has anybody out there any brilliant ideas!!!!!! Steve Packwood I T Manager Taylor Hobson Ltd Leicester England -----Original Message----- From: bpcs-l-request@midrange.com [mailto:bpcs-l-request@midrange.com] Sent: 12 December 2002 13:05 To: bpcs-l@midrange.com Subject: BPCS-L digest, Vol 1 #476 - 5 msgs Send BPCS-L mailing list submissions to bpcs-l@midrange.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/cgi-bin/listinfo/bpcs-l or, via email, send a message with subject or body 'help' to bpcs-l-request@midrange.com You can reach the person managing the list at bpcs-l-admin@midrange.com When replying, please edit your Subject line so it is more specific than "Re: Contents of BPCS-L digest..." Today's Topics: 1. Re: MPS - Customer Demand and General ECL Date Questions (James Barry) 2. RE: MPS - Customer Demand and General ECL Date Questions (Chick Doe) 3. RE: MPS - Customer Demand and General ECL Date Questions (Mike Hoffman) 4. Re: MPS - Customer Demand and General ECL Date Questions (Al Mac) 5. RE: MPS - Customer Demand and General ECL Date Questions (Rob Stagis) --__--__-- Message: 1 From: "James Barry" <zzbpcs@charter.net> Subject: Re: MPS - Customer Demand and General ECL Date Questions To: bpcs-l@midrange.com Date: Wed, 11 Dec 2002 18:54:49 -0500 Reply-To: bpcs-l@midrange.com Hi Paul ! BPCS4.05 CD MPS & MRP uses LRDTE from ECL minus lead time in days from either the IIM or CIC ( if planning by facility)to calculate a suggested release (start) date. SFC500, however, does not give a hoot about lead times. It takes the due date minus appropriate run, setup, machine, move & queue to backward schedule the order. OR it takes start date plus those hours & days to calculate due date. That is why it is so important to have lead times be as "realistic" as your routing times. Jim Barry Belchertown Ma ..................... On Wed, 11 Dec 2002 17:15:15 -0500 "Paul LaFlamme" <laflammep@kennedydc.com> wrote: >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. > --__--__-- Message: 2 Date: Wed, 11 Dec 2002 17:44:15 -0800 From: "Chick Doe" <Cdoe@barton-instruments.com> To: <bpcs-l@midrange.com> Subject: RE: MPS - Customer Demand and General ECL Date Questions Reply-To: bpcs-l@midrange.com 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 cal= culates 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 discrepanc= ies where mrp was planning components for one due date and then suddenly th= at 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 ou= t of snyc again. perhaps this is one contributor to the 200+ page mrp excep= tion reports. as far as the mrp exception reports go they are too voluminous. we wrote ou= r 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 day= s or less from the existing order due date. (mrp stores it's recommended re= schedule date in the FSO and HPH files and you can easily access this and t= he 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. --__--__-- Message: 3 To: bpcs-l@midrange.com Subject: RE: MPS - Customer Demand and General ECL Date Questions From: "Mike Hoffman" <mhoffman@crowechizek.com> Date: Thu, 12 Dec 2002 00:42:54 -0500 Reply-To: bpcs-l@midrange.com 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. --__--__-- Message: 4 Date: Thu, 12 Dec 2002 04:13:58 -0600 To: bpcs-l@midrange.com From: Al Mac <macwheel99@sigecom.net> Subject: Re: MPS - Customer Demand and General ECL Date Questions Reply-To: bpcs-l@midrange.com The MRP reschedule date in FSO HPO ... if it is all zeros that means that it is not reccommending that you change the date if it is all nines that means that it is suggesting that you cancel the order In more technical 400 forums there have been tips about doing date math to get the number of calendar days between two dates to see if it is worth adjusting what MRP suggests we do (after you eliminate the records that are all zero in date), but you may wish to factor in FSC calendar, or just figure on the basis of multiples of 7 days (calendar weeks) to determine which are worth adjusting We cloned the SFC230 shop floor dispatch report to show both the FSO FOD due dates and the MRP reschedule date It is important to realize that if customer order due date changes, and you already released shop order for the due date that used to be in the customer order, and for the various sub-assemblies of that, MRP just suggests the parent shop order date be changed, it does not replan the sub-assemblies, because it is leaving you up to decide whether or not to do the shop order parent item on the new date. Only when you change the parent item due date, and redo MRP, does it go down to the next level and make reschedule dates based on the fact that the parent is now due on a different date. If you enter a brand new item, its effectivity date defaults to the date you entered it, so if you immediately release a customer order on your new part, MRP will not plan components whose dates would go before the date of effectivity, so you have to be careful to enter correct effectivity dates. Another gotcha is that MRP will not plan brand new orders into the past due. If you enter a new customer order in which some component parts would be past due at the instant of release, MRP does not launch them. You have to know your cumulative lead time, recognize that you are releasing something requiring components whose cumulative lead time goes into the past, and manually create whatever orders neccessary to fill MRP blind spot. There are planning fields to get around some of these, which need to be managed as carefully as having accurate lead times, and appropriate levels of safety stock. You can lie to BPCS and tell it that the planning date is so far in the past that past due does not matter. This is a no no at our company. SFC500 can be used to release shop orders, one at a time. MRP or JIT can be used to release all shop orders that MRP thinks are needed, in which you select warehouse, date range, other criteria, then select and deselect from the big collection at will. The difference is that by using MRP or JIT to release shop orders, the amount of human effort per unit shop order is almost microscopic. Releasing shop orders by SFC500 should be exception to the rule. A company operates either globally or by facility. If globally, forget CIC, you just have one set of information from IIM MBM FRT and related files. It sounds to me like Paul's company is not doing things by facility. If by facility, you have to be careful when launching BPCS tasks to not accidentally do them globally. For example, when running MRP500 MRP600 there is a field to specify which facility you doing it for. If your data, in MBM FRT etc. is by facility, and you accidentally run MRP500 MRP600 with the facility field left blank, it won't pick up the facility rules from CIC but rather the global rules from IIM which might not be up to date. CIC gets populated with defaults from IIM as soon as there is activity on item facility combination relevant to MPS/MRP, then you go in with MRP140 to tinker with any exceptions for that facility. There are several kinds of orders in the BPCS system that MPS/MRP can factor into the equation ORD Customer Orders DRP Inter-Facility, which might not be a factor for Paul PUR Purchase Orders SFC Shop Orders Check my links to BPCS documentation http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html Several places sell BPCS manuals. They run in price from about $150.00 to $350.00 each. You can get them for MRP, CST, other topics. See if you have BPCSDOC in your BPCS library list. At V405CD we have BPCS source code, and the HELP text for the MRP programs are accessible without actually running the programs - check what is in QPNLSRC. Several places sell add-on software to help you cope with the MRP exception message volume. Also take a look at OTTO near the bottom of my BPCS documentation directory. http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html I will update this from time to time as people let me know what I have overlooked. Al Macintyre James Barry wrote: >Hi Paul ! >BPCS4.05 CD MPS & MRP uses LRDTE from ECL >minus lead time in days from either the IIM >or CIC ( if planning by facility)to calculate a suggested >release (start) date. >SFC500, however, does not give a hoot about lead times. >It takes the due date minus appropriate run, setup, >machine, move & queue to backward schedule the order. >OR it takes start date plus those hours & days to >calculate due date. >That is why it is so important to have lead times be >as "realistic" as your routing times. >Jim Barry >Belchertown Ma > > >..................... > > "Paul LaFlamme" wrote: >> >>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: Judi Svoboda >> >>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 >> >>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. Al Macintyre BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/ See Al http://www.ryze.com/view.php?who=Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html --__--__-- Message: 5 From: "Rob Stagis" <stagis@fansteelvrwesson.com> To: <bpcs-l@midrange.com> Subject: RE: MPS - Customer Demand and General ECL Date Questions Date: Thu, 12 Dec 2002 08:06:58 -0500 Reply-To: bpcs-l@midrange.com Yep - that problem is ours. We currently generate shop orders, then use that demand to create the PO.....we're starting MRP first with MPS as a secondary 'benefit'. -----Original Message----- From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On Behalf Of Paul LaFlamme Sent: Wednesday, December 11, 2002 5:01 PM To: bpcs-l@midrange.com Subject: RE: MPS - Customer Demand and General ECL Date Questions Hi Rob, We're going to use the MRP240 for MPS. MRP is secondary to us right now, but we'll probably try to run with MRP200. Our MRP240, exception only is about 200 pages! Are you having a problem with MPS suggesting you move shop order due dates to be the same day as the Request Date? -----Original Message----- From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On Behalf Of Rob Stagis Sent: Wednesday, December 11, 2002 4:34 PM To: bpcs-l@midrange.com 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 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) digest 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. End of BPCS-L Digest DISCLAIMER: This message may contain privileged and confidential information. If you think for any reason this message has been addressed in error you must not copy or disseminate it and we would ask you to notify us immediately by return email to postmaster@taylor-hobson.com. Internet emails are not necessarily secure. Taylor Hobson Holdings plc is the holding company for the Taylor Hobson group of companies and is registered in England No. 3230332, with its address at 2 New Star Road, Leicester, LE4 9JQ, England.
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
