A high percentage of exception messages are generated by mathematical noise
in BPCS / ERP LX planning. So, if on Tuesday you act on a message to
expedite an order by one day, there's a good chance MRP will tell you to
de-expedite the same order before the end of the week. PaperSaver Exception
Report software enables you to remove non-crucial messages before sending a
report to users; only messages that survive a user-designed "don't show me
unless the move is at least X days" constraint end up on the report. That
creates a planner frame of mind that each and every message on each and
every report merits their full attention.
The software also provides a message that BPCS hasn't invented ---- it
points to purchase orders that have an excess quantity. Example: 3800 pieces
was the right quantity when the PO was released in early July. Delivery is
still needed on August 10th, but now MRP has figured out that only 2650
pieces will be needed. BPCS won't tell you to move the delivery date and it
won't tell you to cancel the order. PaperSaver will tell you the quantity
is excessive in time to slim down the PO. It's a great tool for companies
with tight cash flow management.
More information: http://www.unbeatenpath.com/software/ps/PaperSaver.pdf
Unbeaten Path International
From: Muthukumarasamy Kuppusamy
Sent: Tuesday, July 31, 2012 4:51 AM
Subject: [BPCS-L] MRP Reports in BPCS 6
We want to send the MRP exception Report to the users (Planners) on the
basis of their planner code. Now we have the reports as Spool file in
AS400 which is generated by executing the program MRP200B.
We want to covert the spool files in to PDF format and send the users
(Planners) by Planner code wise.
Any ideas ?
Muthukumara Samy, K
Email : muthukumarasamyk6@xxxxxxxxx