Enhancements & Revisions

Adagio PurchaseOrders 9.2A

December 4, 2015

· Compatible with and required by Adagio JobCost 9.2A (if used).

Problems Fixed

· JobCost cost batches created in PurchaseOrders had blank G/L accounts if the fields were blank in the Phase/Category, rather than using accounts from the Job.

Fixes from previously released Hot Fixes

· The Auto Generate POs from OrderEntry function did not work if you have OrderEntry 9.2A. Orders entered with OE 9.2A will not generate PO’s. Orders entered with a previous version of OE and orders created by transfer from SalesCQ did not have a problem.

This has been corrected but requires that a Data Integrity Check be performed in OE. First you MUST open the data with PurchaseOrders. Errors will be reported for each detail line entered in OE 9.2A. You must do a rebuild and all errors will be corrected without loss of data. The Auto Generate will then work correctly. The next release of OE will correct this problem without requiring a Data Integrity Check and rebuild.

· When emailing documents with an Email Cover Sheet that uses fields from the Payables 9.2A vendor file, there was an error.

· The Import Quick Receipt function did not allow negative quantities.

· Import of partial receipts for Sundry Items did not correctly update backorders or Event Budgets.

· When PurchaseOrders was already running and you selected PO from the Adagio menu or toolbar of another module, instead of switching to the running PO it opened another instance.

· In PurchaseOrders 8.1D (2014.03.10) and later, if you entered a Receipt and reversed a No proration miscellaneous charge allocation from another receipt, the amount of the miscellaneous charge from the second receipt was distributed to the wrong Ledger account in some cases. This resulted in Day End creating incorrect GL transactions to the Ledger Rounding Error accounts instead of the Debit GL account on the Receipt line detail.

· In PurchaseOrders 9.2A, the Outstanding Receipt Invoice List report displayed an error similar to “Cannot open file \\\"\DATA\IRHTnnnnR.DAT\\\". The system cannot find the file specified.” on systems with many Windows users (approximately more than 100).

· Filters were not rebuilt by DataCare for PurchaseOrders 9.2A.

· DataCare displayed an error when opened after installing PurchaseOrders 9.2A if Payables was not 9.2A.

· There was an Access Violation error in DataCare when checking a PO database for a specific type of corruption in fields, likely due to hardware problems. This error is now prevented for DataCare 9.2A (only, not earlier versions). The data may still have corruption in fields that DataCare cannot detect or repair.