Category: Sage 200


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.

I will be striving for more posts about the 2016 version, released last week, but for now here is a video to give you a taster.

It’s not as big or as exciting as 2015, but there are some pleasing additions.

Sage 200 Consultants wanted

At Smith Cooper System Partners we are expanding our brilliant and dedicated team.

Reporting to our implementation manager, we require an experienced Sage 200 consultant to join our busy delivery team. This is NOT a trainee position so the successful candidate should have a proven track record of Sage 200 implementations along with a working knowledge of the add-on market (Draycir, Eureka, Sicon etc.). Customer service is very important to our company, so a customer first attitude and a strong desire to produce quality projects is also essential. Would suit an experienced Sage 200 consultant looking for a new challenge, who wants to work in a positive, forward thinking environment and can “hit the ground running”.

We also have roles for a Support consultant and Account Manager

Smith Cooper Are Hiring For Sage Software Professionals

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

 

2015 in review

The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 27,000 times in 2015. If it were a concert at Sydney Opera House, it would take about 10 sold-out performances for that many people to see it.

Click here to see the complete report.

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.

 

I’m delighted, excited and proud to have been part of the great achievements at Smith Cooper System Partners.

Read more here:

http://goo.gl/lwqs4U

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.