× 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.



We are using BPCS 6.1. Currently once a month we run MPS/MRP and then a Batch 
Purchase Order Release program to create hundreds of Purchase Orders for the 
suppliers. Often there is a problem with the BOM or Customer Order or something 
before I run it. But once MPS/MRP and Purchase Orders are created, then the 
supply chain department checks them and determines they are wrong. We use SQL 
to delete the hundreds of PO's that were just created.

So my two questions are:
1. Does anyone else have a similar procedure and how do you handle it once the 
Purchase Orders are created and they are wrong?
2. Does BPCS include an option to do a MASS PO Close before I write a program 
to close out the POs it instead of deleting them with SQL?
3. And at what point does the PO's effect the On Order Quantities and other 
files. Is it at the point of when Supply Chain prints out the PO's or As soon 
as they are created. Just wondering how much harm we are doing to the system by 
deleting the purchase orders after a bad PO run.

Thanks in advance


 
____________________________________________________________________________________
Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/

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.