Category: Implementation


Sage 200 2016 SP2

Sage 200 2016 SP2 has been out for a while now.

One key issue that impacted users in Sage 200 2016 were the restrictions on Accounts which were placed ‘On Hold’.

There is an issue with entering Memo’s and also it is not possible to allocate transactions.

SP2 fixed the Memo issue. It didn’t fix the allocations but after I did some communicating with Sage support they did a great job and there is actually a Hotfix now available.

It still isn’t possible to import transactions which is something else we have come up against, however my opinion on this is that for Invoices in particular it is probably working by design. I would be interested to know other people’s thoughts on this.

Sage 200 Extra and Sage 200 Extra Online 2016 have now been released. If you are considering updating or want further information send your details to sagemarketing@smithcooper.co.uk

Whilst it is not, perhaps, as drastic an update as the 2015 version, which had a whole change to the UI amongst other features. The 2016 version has some game changing additions with new integrations for payments.

There are also some nice additions from the wish lists and a new connector which integrates Sage 200 to stand alone Sage CRM (not Sage 200 CRM).

Below are some details of what’s new!

Sage Integrated Payments (SIPS)

Integration with Sage Payments allows for an easier and secure way to pay suppliers.

A Sage Payments account is a virtual wallet (e-wallet) similar to PayPal. You can add funds to your Sage Payments account and then use this to make payments directly from Sage 200.

NB. A Sage Payments account is required

Bank Feeds

Sage 200 is now able to use the Yodlee bank feed. This gathers information from your bank, and downloads bank transaction details for display in Sage 200 so you can match them to transactions in Sage 200, or create new transactions.

When you confirm the transactions as matched they are flagged ready for your next bank reconciliation.

NB. Subscription to Bank feeds is required.

Sage Pay – Get Paid Faster

Sage 200 now includes the Sage Pay ‘Get Paid Faster’ functionality.

If you are using Sage Pay, you can use the ‘Pay Now’ button on your layouts such as invoices, statements and chase letters that you send as PDF files by email.

When your customer opens the PDF attachment they can click the ‘Pay Now’ button to make a payment straight away through Sage Pay.

Commitment reporting

Commitment reporting allows you report on purchase orders as a committed cost before the order has been received or invoiced.

This makes it easier to view actual costs and committed costs to establish committed spend.

Report Category budget grouping

It is now possible to hold a budget against a reporting category which offers much more flexibility in assigning and reporting on budget areas.

New Bank Reconciliation screen

A new bank reconciliation screen has been introduced with a split screen view separating matched and unmatched transactions. This brings the functionality in line with that of Sage 50 and presents the information in a clearer way.

Create Return from Order

The ability to create a Sales Return from an existing Sales Order has been eagerly awaited for many versions gone by. It’s finally happened!

You can select a Sales Order then select ‘New Return from order’ which will populate the Return details.

Within the Sales Return screen you can also select Copy Order and the Return screen will be populated with the return data based on the selected Sales Order.

It makes it much quicker to enter a return and removes the need to re-key information but be aware there is no link created, it just copies the information.

Predictive text in Rapid Order Entry

On the Rapid Order Entry, predictive text is now available to filter the selection list of available stock items as the item is typed.

Override Negative Stock option (Rapid Order Entry)

When raising a Sales Order via Rapid Order Entry, it is now possible allow the stock to go in to a negative allocation if the required quantity is not available.

The Product Group now has a flag ‘Can over allocate stock’.

Stock Analysis Codes

Stock records have been extended to include 20 Analysis Codes. Report Categories still exist, but the analysis codes allow for further analysis in line with SOP/POP/ It is also possible to import these when importing item records.

Support for Barcodes

Stock records have been extended to include a Barcode. These can be imported as part of the Stock Item Import.

Limited Price Bands

My particular favourite!

New Price Bands can be created as ‘Limited’, allowing the customer to select which Stock items they want to add to a Price Band, rather than all stock items being added.

Time Limited Price Lists

Price Bands can be created as Limited or Universal.

Limited Price Bands can be flagged as Active and/or have ‘From’ and ‘To’ dates assigned.

This is great for promotional pricing.

API

An API has been included to offer better flexibility for development and integration to Sage 200 Extra.

CRM

A New connector integrates Sage 200 with Sage CRM. This allows data to be input in ‘real time’ reducing the synchronisation requirements.

Importantly what this will also allow is for upgrades of 200 and CRM to be run separately. This should hopefully make the upgrade requirements easier and more affordable.

 

**As with all new releases compatibility has been removed with for older versions of related Operating systems and linked applications.

Most noticeably is the removal of Citrix Xenapp.

Service pack 3 has now been released for Sage 200 Extra 2015. There are a number fixes included as detailed in Sage 200 Extra 2015 SP3 Issues Fixed .

Sage 200 Manufacturing

Stock Projection Details

Some changes have been made to improve compatibility with Windows 8, Windows 8.1 and Windows Server 2012, these changes also make a consistent look and feel with other areas of Sage 200 Extra.

As a result of these changes, the following graphs are no longer available:

• Graph tab on Stock Projection Item Details

• Graph tab on Monitor Operation Times

• Histogram tab on Monitor Operation Times

The changes also prevents some workspace options (for example, opening, saving, Copy to Clipboard, print and the tools to change the display of the charts).

MRP – Unable to amend the first recommendation on the system

When the user runs MRP within Manufacturing for the first time, the MRP numbering sequence runs from MRP000000, rather than MRP000001.

As a consequence of this, the first recommendation will not be selectable on the MRP Recommendations form.

To renumber the recommendations you must run the MRP twice on a new dataset, before actioning or maintaining any recommendations.

Subsequently, MRP need only be run once.

Sage 200 Suite Tools

Sage 200 2015 SP3 uses a new version of ManufacturingCSVFileConversion.exe

If you attempt to use the previous tool, the following message appears:

Error launching application. Could not load file or assembly ‘Sage. Manufacturing, Version – 17.0.0.1’.

 

Sage have advised Business Partners that Microsoft have announced that as of 9th December 2015, they’ll be removing some of their earlier versions of their REST API, some of which Sage are using to access storage accounts (i.e. blob storage).

Sage have updated Sage 200 2015 to use the latest version and have also included the change within Sage 200 2013 R2 Service Pack 2.

They will not be applying this fix to any other versions of Sage 200 Extra Online, so customers operating any of the versions of Sage 200 Extra Online shown below must be upgraded to Sage 200 2013 R2 SP2 or Sage 200 2015.

  • Sage 200 2013
  • Sage 200 2013 SP1
  • Sage 200 2013 R2

The change is currently planned by Microsoft on 9th December and Sage 200 Online sites must be upgraded no later than 4th December.

Yesterday finally saw the release of the much-anticipated Service Pack 2 for Sage 200 Extra 2015.

One of the key items as part of this is the support of Windows 10 operating system.

There are lots of fixes and some additions as detailed in this document released with the update –

Reports

There are some New Reports to be aware of which are not installed automatically as well as Layout updates too. Check these out with your BP. The introduction of the SOP Profitability reports which include Returns and Credit Notes will be music to some people’s ears, although if you needed this previously you have probably had the report written already.

There also some nice Stock reports, offering different views of Sales by Customer, Product Group and Monthly Sales etc.

Summary Screens

My particular favourite addition in this service pack is the added drill down functionality to the Summary screens. Previously a great visual aid (and Sage Sales Persons dream!) they were not altogether complete from a ‘day to day’ point of view. However we are now able to drill all the way down to the transactional items which makes them much more beneficial as an analysis tool.

Sales Summary Outstanding Debt (Totals)

Sales Summary Outstanding Debt (Totals)

 

Sales Summary Outstanding Debt (Drill down to Customers)

Sales Summary Outstanding Debt (Drill down to Customers)

 

Sales Summary Outstanding Debt (Drill down to Transactions)

Sales Summary Outstanding Debt (Drill down to Transactions)

Installation

Service Pack 2 can be applied to sites running either the Base version of Sage 200 Extra 2015 (all SP1 updates are included) or sites with Sage 200 Extra 2015 Service Pack 1.

As with Service Pack 1 there are two installation files:

  • Sage200v2015SP2ClientPrerequisites.exe
  • Sage200v2015SP2.msp

On client machines, both files must be run in the order listed above.

Sage200v2015SP2ClientPrerequisites.exe checks the client files to ensure the correct registry keys are present on the machine.

Sage 200v2015SP2.msp updates Sage 200 Extra.

NB. On a server, you only need to install the Sage 200v2015SP2.msp file.

As ever this Sage 200 Extra 2015 SP2 Installation and Release Notes document gives all the information needed to install the service pack.

 

Short, important post!

Microsoft have now released Windows 10. Please be aware that this is NOT supported for any current versions of the Sage 200 suite.

All being well Service Pack 2 for Sage 200 Extra 2015 will include Windows 10 compatibility. This is currently scheduled for 30th September 2015.

 

I have hit this issue on my last couple of installations where the Core components fail to install when accessing Sage 200 2015 System Administrator. Sage have identified this as being an issue which relates to virtual environments (which both of my examples were).

When you access System Administration for the first time after install, various messages appear throughout the initialisation, including those referring to the core components and the building of models. You may notice the system freeze during this.

The issue relates to the available resource on the machine. Clearly the virtual environment must meet the minimum System Requirements for Sage 200 2015. For standard single-server environments, this requires at least a dual-core processor and 4GB of RAM.

Interestingly for my examples the servers should have been fine, however the memory was set to be Dynamically allocated and for some reason was remaining below 4GB. Once this was changed to a Static amount, well above the minimum, the core components installed correctly.

After upgrading a Sage 200 site to Sage 200 2015, an error message may be displayed when accessing System Administration for the first time. The message advises of an error in XML document (9, 3).

 

This is caused by not removing any Add-Ons before commencing the upgrade to Sage 200 2015.

Previously, the Add-Ons could be uninstalled in System Administration but when you try to remove the Add-Ons , the below error is displayed.

Exception has been thrown by target of an invocation

This is because in Sage 200 2015, the schema version number has changed so the Add-On trying to be removed does not have the expected schema number assigned to it and so can’t be removed.

In order to complete the upgrade:

Note: You must take a backup of the Sage 200 Configuration Database before proceeding.

  1. Close any errors and select the Add-Ons option in the left pane.
  2. Make a note of the name of each Add-On installed on the site.
  1. Backup the Sage 200 Configuration Database before proceeding.
  1. Open the configuration database in Microsoft SQL Management Studio and open the tblAddon table.
  2. Look for the Add-Ons that were noted in Step 2 in this table. For each add-on, make a note of the AddOnID in the first column.
  3. Remove the entries from the table for each of these add-ons. This should leave only the standard Sage 200 entries in the table, for example, Sage 200 Accounts, Sage 200 Bill of Materials, Sage 200 Accounts Compiled Model.
  4. Close Microsoft SQL Management Studio and re-open Sage 200 System Administrator.
  5. The core components should now install successfully. You will then need to reinstall any applicable Add-Ons, ensuring first that they have been re-compiled for use with Sage 200 2015.

Sage 200 2015 Service Pack 1 is now available.

Business Partners should note the different method of installation on Clients.

This service pack contains two files:

  • Sage200v2015SP1ClientPrerequisites.exe
  • Sage200v2015SP1.msp

On a client PC both files must be run, in that order, to ensure the service pack installs correctly.

Sage200v2015SP1ClientPrerequisites.exe checks the client files and ensures that the correct registry keys are present on the client machines. Sage 200v2015SP1.msp updates Sage 200 Extra. Failure to run the files in this order will cause errors when you try to run Sage 200 Extra 2015.

On a server, you only need to install the Sage 200v2015SP1.msp file.

Sage 200 Extra 2015 SP1 Installation and Release Notes

The following Known Issues have been resolved in Service Pack 1.

Module Issue Tracking System Reference
(where applicable)
Description
Nominal Ledger 5970 Users were unable to import a CSV file with negative budget values.
6318 When importing nominal ledger budgets, a ‘success’ message was displayed but the details were not imported.
6429 The Default Cost Centre drop-down list was not displayed on the Consolidation tab of the Nominal Ledger settings.
Desktop 6389 An ‘Unhandled Exception’ error message appears when trying to add a new feature in Menu Design mode.
6390 Updated the Workspace quick filters to display part searches. Previously, the filter would only search on the entire word (for example, typing AB would only find a customer with the name AB, it wouldn’t find Abbey etc).
6400 User preferences not retained when a user logs out of Sage 200.
6424 Adding reports to the Home Page Favourites now makes the report appear in the Summary screen.
6425 Creating a new folder in Home Page Favourites and adding the report generates an error.
6443 Error in Workspaces where the ‘OR’ filter did not work correctly. In previous versions the OR filter was working like an AND. As a result, no details were being returned by the filter.
6444 Unable to run reports or layouts from favourites.
6487 Non Taxable Receipt launches Taxable Receipt Form.
Purchase Orders 5753 Could copy an order without saving any supplier details.
6480 Multiple Delivery Dates button missing if Project Account Integration not enabled.
Sales Ledger 6451 Save and Allocate button on the Sales Ledger reverse transaction form is now read-only when reversing receipt or payment. This was active in the release version of 2015.
Stock 6455 MRP Replenishment Options missing from the Manufacturing tab on the Stock Item screen when using low screen resolution on some low-spec laptops and PCs.
Timesheets 6469 Enter Timesheet Week – Incorrect Cost rate saved.
Analysis Codes 6470 Issue when editing a newly created analysis code in Sales Order Processing or Purchase Order Processing.
Sage 200 CRM 6432 Ergonomic UI not working as expected after upgrade from 7.1.
Developers 6401 Addon fails to install when contains 2 content parts.

Sage 200 Extra 2015 SP1 Feature Updates and Issues Fixed gives some further details of items included in this update.

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.