× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Exception Report - Use an alternative solution
  • From: "Mike Hoffman" <mhoffman@xxxxxxxxxxxxxxx>
  • Date: Fri, 17 Mar 2000 07:35:23 -0500



My recommendation for reading the MRP Exception Report is DON'T. My
recommendation is to develop a new report that includes the open shop orders
(FSOL01), firm planned orders and planned orders (KFP) that includes the
reschedule date from the respective files. This one report would:
     show the current scheduled receipts (shop orders and firm planned orders)
     any new recommendations from MPS/MRP that need to be acted on
     suggestions for rescheduling (get this from the reschedule date that is in
     FSO and KFP files)
     You can even join to your routing file (FRT) or shop order routing detail
     file (FOD) to calculate the expected hours for the order
     put a time frame on how far out to include planned and firm planned orders

The same kind of thing can be done for Purchasing by substituting HPO file for
the FSO file. I have also made the Exception Report a stand-alone report, but it
is one line per item instead of one page per item.

Use MRP300 Planning/Pegging Inquiry to diagnose the reasons for exceptions if
the reschedule out/in date is worth even looking at (i.e. if the dollar value is
not significant and MRP tells you to move it out 2 days -- don't waste your
time)

If you must read the MRP exception report, reference your MRP300 screen --- it
never lies! At least I can't recall a BMR on MRP300 recently.

Mike Hoffman
Senior Manufacturing Specialist
Crowe, Chizek & Company, LLP
http://www.crowechizek.com/scg/
phone: 440.460.1318
fax:       440.460.1302



|--------+----------------------->
|        |          Kusman Lim   |
|        |          <KUSMAN@TAKED|
|        |          A-ID.com>    |
|        |                       |
|        |          03/06/00     |
|        |          06:27 AM     |
|        |          Please       |
|        |          respond to   |
|        |          BPCS-L       |
|        |                       |
|--------+----------------------->
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     BPCSL <BPCS-L@midrange.com>                                  |
  |       cc:     (bcc: Mike Hoffman/CL/CroweChizek/US)                        |
  |       Subject:     Exception Report                                        |
  >----------------------------------------------------------------------------|




Dear BPCS User

We use 6002 plf Cum Mar 98 client/server.

We question for how to read the MRP Exception Report.

Could you please to explain it to us ?

Thanks for your great help.

Regards

Kusman Lim


+---
| 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
+---



+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.