Two people in my 90 Minds Consulting Group have run across similar tricky issues wehre the icons on the Sage ERP MAS 200 taskbar disappear. Turns out there’s an easy solution related to font sizes that my friend Jim Woodhead at DSD documented on his site. Here’s the fix.
Sage has just re-released their detailed guide to new features to be included in their version 4.50 release when it begins shipping on June 8, 2011.
Significant enhancements have been made to payroll , sales order, and Sage ERP MAS Intelligence financial reporting.
Users of Sage ERP MAS 90 and MAS 200 should consult the following supported platforms listing as issued by Sage prior to installing upgrades or purchasing new hardware or operating systems.
These are the only official platforms supported by Sage. If you attempt o run Sage ERP MAS90 or MAS200 on an unsupported platform – while it may work – you will not be able to obtain any official support to resolve any issues you encounter.
Supported Platform Matrices – MAS90 + MAS200 Version 4.50
Supported Platform Matrices – Version 4.45
Supported Platform Matrices – Version 4.40
Supported Platform Matrices – Version 4.30 and earlier
Important: From time to time Sage updates their supported platforms matrix. While every effort is made to provide current information we cannot guarantee that these are the most current documents from Sage or that there are not other considerations for your specific situation. You are advised to consult with your Sage Business Partner prior to making any purchasing decisions. In no case is Schulz Consulting responsible for any incorrect purchases of hardware or operating systems based on use of these Sage Supported Platform Matrices.
In most cases Sage ERP MAS90 and MAS200 workstation setup will properly setup your computer for use with the popular Paperless Office feature which allows printing reports and forms to PDF.
However some users have reported issues where installation to Windows 7 computers may be troublesome. They report either issues with the paperless drivers not installing or various registration related errors.
Often we find that logging in and running workstation setup as administrator solves the issue.
In some cases you may find that extra measures such as registry tweaks (as advised by Sage) are required. I just noticed on the Sage Community Forums that someone has come up with an easier way to attempt to resolve pesky Windows 7 Paperless Office issues.
This involves using the MAS version 4.4 install files for paperless – and installing them to your version 4.30 system.
First a warning. We’ve not yet tested this – so you’re on your own if something breaks or is damaged. Make a backup before attempting this solution.
Remember that in most cases you can install Paperless Office straight from the workstation setup — with no need for this workaround. You should only use the below tip if you’ve tried to install paperless, have researched the Sage KB for solutions – and still failed.
Paperless Office Setup – MAS90 4.3 Windows 7 – Workaround
UPDATE: Sage have issued an additional knowledgebase article which seems very comprehensive in the number of tips that it provides. If you are having trouble with Paperless Office hanging on Windows 7 or Windows 2008 please review this Sage KB Article.
Here is an interesting tidbit that I just learned (or maybe I knew it before but re-learned it).
The cost field in the MAS90 Sales Order Invoice data entry may not be the true cost so long as the invoice is unposted.
A Client was using FIFO costing for an item that they sold. Noticed that the data entry cost didn’t match with the gross profit journal cost. Turns out the way that the cost is assigned is MAS90 and MAS200 may use last cost within the invoice data entry cost field. (see this link for the Sage explanation)
When the transaction is posted the cost is assigned properly to the invoice history file.
This came about because the client wanted to provide a file of sMAS90 Sales Order invoice data entry transactions (including line item costs) to a third party. My thinking was just take MAS90 Sales Order Invoice Data Entry and do an export.
That worked — except the client noticed the cost per the export I had created did not match to the cost per the Cost Journal for FIFO (and possibly other) cost types.