Below is a list provided by Sage of the fixes included within Sage 200 2015.

System Administrator
5997 & 5998 We have improved the speed of the company database upgrade process.
This affects any database that:

  • uses Analysis codes
  • has large numbers of SOP, POP or Stock records, or
  • has large numbers of BOMs or BOM Lines.
6054 Users were unable to create the MMSUser account on Windows 2012 Essentials when it was integrated with Office 365.
Previously the user would see the error message:‘Cannot add login name_mmsuser to server password validation failed, the password does not meet the requirement of the password filter dll’.
Core 200
Nominal Ledger 1392 Tax type and tax code fields were not displayed on nominal journal templates.Previously, a user would have to set up the template and then enter these details once the template had been recalled prior to processing.
Stock Control 5093 Under certain circumstances, Amend Stock Item Product Group stopped working if outstanding works orders existed.
In some cases, an ‘out of memory’ error appeared.
5424 Removing large amounts of stock history records caused on ‘out of memory’ error.
Project Accounting 5476 Users saw the error message; ‘Failed to run SQL script SchemaMigration’ when accessing Project Accounting settings, using the View Project Accounting Settings screen or when saving a project.
5945 Bills were not generated as part of the Suggested Billing functionality. This issue affected some project item types of ‘stock item’, depending on how the item was set to allow costs and revenue.
Period End 5532 Users saw an exception error when trying to drill-down on a value on the Current Periods Totals screen within the VAT Analysis option.
This occurred for users who had previously migrated data from Sage 50 Accounts.
Purchase Order Processing 5541 In some circumstances, a unique reference number (URN) was used if a free text line was analysed to a project. This resulted in a URN that had no postings in the Nominal Ledger.
6053 Saving a record with a long description on the Confirm Goods Received screen generated a ‘Sage Data Access Error – Cannot set the value of the field’ error.
Sales Order Processing 6066 Users trying to print a quotation for quotations that had been entered via the CRM Form Launcher would see an error message ‘Value does not fall within the expected range’.
6239 Customers, using traceability, received an ‘Out of Memory’ error when processing large amounts of stock after the stock levels had been adjusted.
Sales Ledger 5666 Users saw Out of Memory errors or No Network Connection errors when performing consecutive transaction enquiries.
Nominal Ledger 5924 The details of a held journal were lost when creating another held journal from a template.
Bill of Materials 5767 Overtyping the stock code on Record Built Items could move a quantity into stock for an incorrect item.
5780 Users sometimes received an exception error in the following scenario:
Creating a purchase order within Trial Kitting when the supplier had exceeded their credit limit.
5904 The Reverse (BOM) Build process took a specific quantity of a finished item out of stock and added the stock back in to the components.
Manufacturing
Works Order Processing 4551 Traceable Enquiry functionality did not work after changing the product group on a stock item.
6122 Cost of sales postings were incorrect when components were issued to a works order which was completed before the components were invoiced.
6188 Traceable components were not discarded correctly if the build was cancelled on the Confirm batch/Serial Numbers for Components form.
Estimating 5393 Components held against operations were not converted when estimates were converted to a BOM.
Bill of Materials 6086 Cancelling a BOM build for batch/serial items did not allow any changes to the build, unless the screen was closed and reopened.
6096 The Build Session created a reserved temporary batch/serial number in BOM and an error message appeared, preventing the user from entering a value in the Quantity field.
6172 Cost of sales adjustment postings were sometimes posted to the wrong nominal ledger account when building through sub-assemblies.
Other
Process Maps 5564 Enquiry buttons within process maps were not working.
Workspaces 5601 An exception error occurred if the user opened multiple workspaces. We have reduced the amount of system memory required to open multiple workspaces.
Excel Integration 6004 Refreshing data within Excel Integration was not good. We have made performance improvements in this area.
Advertisements