|
The contract expiry date is only taken into account when you create the PO Item. All releases thereafter are only limited by the Due Date or Qty of the PO Item which becomes the last due date allowed and not by the contract expiry date. You will need to close the old PO to stop Auto-release using it. Then manually create another PO with an expected qty for that year and last due date on the PO Item. This is poor functionality as you cannot automate the change over to a new PO. When you add on the work involved in creating new contracts and new PO's and manually managing the changeover it is sizable. There are other settings to the Auto release code in the Balance record which will create a new PO but it creates new PO every time you auto release with only the releases required to satisfy the new MRP demand since last run. This is no good if you want to maintain a single PO Num for a year with a supplier. Gordon Thomson MIS Department Dundee Tokheim UK Ltd Tel 00 44 1382 598112 leigh_madden@xxxxxxxxxx Sent by: mapics-l-bounces@xxxxxxxxxxxx 08/12/2005 02:30 Please respond to MAPICS ERP System Discussion To: mapics-l@xxxxxxxxxxxx cc: Subject: [MAPICS-L] MRP Autorelease PO Hi Group, We are running MRP Autorelease PO's with Blanket Purchase Orders (not fixed orders), We are also using contracts in purchasing. We had believed that if we set a contract to expire on a given date (say Dec 31) and create a new contract to start on the following day (Jan 1) that the auto release process would create a new PO and add releases after Jan 1 to the new PO. However in our testing we are not seeing this, it just keeps adding to the existing PO. Is anyone doing a similar thing, have we just misunderstood the functionality ? Thanks Leigh Madden Systems Development Manager PBR International Limited A Pacifica Group Company ph: +61 3 9575 2604 fx: +61 3 9575 2485 mb: 0419 307 567 e-mail : leigh_madden@xxxxxxxxxx www.pbr.com.au ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PBR - Dependability through Innovation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ******* IMPORTANT NOTICE ******** The information contained in this e-mail message and any attached files is confidential and may also be subject to legal professional privilege. It is intended solely for the addressee(s). If you believe you may have received this e-mail by mistake, please notify us immediately by reply e-mail and promptly delete the original e-mail. If you believe you may have received this e-mail by mistake, you are not authorised to use, disclose or copy the e-mail or any attached files. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.
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.