Exception reporting

["Milt Habeck" <mhabeck@xxxxxxxxxx>]

Dear Mr. Dau,

 

We have a "Bells & Whistles" product for BPCS called "PaperSaver Exception Report." It has been designed to address the issues you raised. It provides more functionality than many user-programmed solutions because it does not sort through the spool file to generate a report ... rather ... it is a complete substitute for MRP200. 

 

Hot-link to product description:  http://www.unbeatenpathintl.com/B&WPapSv.htm

 

Hot-links to some customer reference letters can be found at the bottom of this web-page: http://www.unbeatenpathintl.com/bells.html

 

Warm regards,

 

Milt Habeck

Managing Partner

Unbeaten Path International

 

Toll free North America:  (888) 874-8008

Voice:  (414) 681-3151
FAX:  (414) 681-3525

e-mail:  mhabeck@execpc.com

web home page:  www.unbeatenpathintl.com

 

 

 

-----Original Message-----
From: dddau@lozier.com
To: bpcs-l@midrange.com

Date: Friday, September 24, 1999 3:19 PM
Subject: Exception reporting

I would like to know if other users are using alternative programming or
bolt-ons to generate   exception reports.

MRP200 reports are taking a great deal of time to generate and sort through.
Our line schedulers are dealing with printing and reading reams of paper
daily.  We would like to condense the information down into concise
reporting by planner/buyer code, item number, etc.  We would like the users
to decide what type and date range of action messages they could view.
Any information, suggestions, or comments would be greatly appreciated.

We are using client/server BPCS 6.004 , September cum on an HP9000 unix
platform.

Thanks,   Dwight Dau