Are you tired of all the SPAM and self-serving information that appears when you search Google for technical information on MAS 90 or MAS 200? What if you could totally eliminate all but the most important Sage sites — and just search what Google has publicly indexed from Sage?

Well now you can. Here’s a quick and dirty Google Custom Search that reviews the public contents of your search results and limits the results only to those coming from Sage’s knowledgebase.

You won’t need to login or provide any other information – just search away!

© 2011, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Sage North America publishes a series of guides that explicitly detail which operating systems and hardware configurations the supported versions of MAS 90 and MAS 200 will reliably operate with.

These handy guides are updated every few months and rather than post the document – which might be out of date by the time you are reading this post – below are the direct links to the relevant documents:

MAS90 SOFTWARE (See links below for MAS 200)

MAS 90 – Version 3.71 to 4.30

http://goo.gl/7xCB

MAS 90 – Version 4.4+

http://goo.gl/rkjR

MAS 200 SOFTWARE

MAS 200 – Version 3.71 to 4.30

http://goo.gl/hYj8

MAS 200 – Version 4.40+

http://goo.gl/5y0c

via: Wayne Schulz Google Buzz

© 2010, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Beginning in 2010 the Sage MAS 90 and 200 products will incorporate all of the Sage EES products and there will no longer be a separate EES package. When that happens more users than ever will be searching for SageCRM support answers.

Sage offers a free online knowledgebase that users of Sage ACCPAC, BusinessVision and Pro can use to research technical support issues free of charge. This knowledgebase also includes support issues related to SageCRM which are not located in the standard Sage MAS 90 knowledgebase used to research accounting related issues.

To access the SageCRM knowledgebase use the link below. There is no login required and you can flag any of the CRM support issues so that you’re notified if they are subsequently updated or changed.

Link: SageCRM Knowledgebase via 90Ninja.com

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Google Wave is the next step beyond email. It allows for real time group conversations where every participant can view a complete history of the discussions. Simple email exchanges often omit large parts of conversations to anyone not on the email distribution list.

Future uses of Google Wave may involve collaborating on workarounds for software issues, real time seminars where participants can comment and add to the topics as well as technical support tracking where more than one company contact could have access to a complete history of the items that have been discussed.

Because Google Wave is in a limited testing preview you must first request an invitation from Google to participate (request).

If you are already on Google Wave you may connect to Wayne Schulz via wayneschulzct@googlewave.com

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Did you update and apply the MAS 90 or MAS 200 Service Update 14 released on 9/29/09? If you did, and you’re a Paperless Office user, then run and grab the latest service update.

Confusingly named with the same version (SU 14) but released on 10/2/09 this fix to the fix re-enables printing of paperless office forms.

Apparently the latest 10/2 fix corrects an issue (Resolution ID 514877 Details Here) where the original SU14 caused all forms in the business framework to print as blanks if they were sent to paperless.

Service Update 14 10/2/09 via Beth Bowers

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Jeffory M. Urquhart who is an ERP Implementation Specialist at Microliance in Florida has started an interesting trivia game over on LinkedIn that asks some tough but fascinating questions about MAS 90.

You’ll need to go way back with the product because Jeff’s questions are not for the beginner.

Jeff’s list of questions appear on the MAS 90 group on LinkedIn (click here to join first). This is not an official Sage forum, rather it’s a spot that fellow users and consultants can gather to exchange information, network — and even play the occasional game of MAS 90 trivia.

Here’s the list of MAS 90 trivia questions.

1. What does M.A.S stand for?
2. What did SOTA stand for?
3. What was 09SAM?
4. What  operating system platform was MAS 90 originally written for?
5. When initially marketed, what was the application language that MAS 90 was written in?
6. In the original versions, how were terminal IDs set?
7. What year was MAS 90 introduced?
8. What was the first version of MAS 90 for Windows?

What’s interesting is several long time Sage employees have added questions like the one Erika Jelovsek poses:

Ahhh, but if you really want to call yourself a historian of all things MAS 90 , you need to be able to define the acryonyms for these release names. And Craig, no jumping in right away…..let the non-Sage folks take a trip in the wayback machine to come up with these answers! ERBY, MERBY, LEFTY, IMSOPO, and, my personal favorite, TAMAN.

For the answers to these questions – and to read several more interesting tidbits of MAS 90 trivia – head over to the MAS 90 LinkedIn group. You’ll have to join the group but membership is free and you can leave anytime.

Link:

MAS 90 -  Trivia Just For Fun

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

I’ve run into this on only a couple of occasions – most of the time in Sales Order.

The symptoms are an Error 88 SY_ReportEngine followed by a line #.

Other sales order forms should print correctly — the problem is usually just one form code — typically a packing list or shipping label.

Check to see that the printer is valid and that you can print other Crystal Forms.

If both of the above check out then I’ve successfully used the fix below:

Listed below is a copy of what SY_ReportSetting.m4t should look like. Yours will be a little different but the field names should be roughly the same.

For the purposes of this error message you only care about the last 4 or 5 fields .

Note that after a user incorrectly accessed the report (not able to track down the exact steps) that fields 38-41 were changed by MAS to bad values.

The values in the field below are what should be used.

Key=[S /O0000000006SO_SHIPPINGLABELS_UI.STANDARD ]
“ModuleCode:CompanyKey:ReportID:ReportSetting”

01 ModuleCode$………… [S/O]
02 CompanyKey$………… [0000000006]
03 ReportID$………….. [SO_SHIPPINGLABELS_UI]
04 ReportSetting$……… [STANDARD]
05 DefaultReport$……… []
06 Description$……….. [1 Across Plain]
07 SettingOptionsType$…. []
08 PrintReportSettings$… []
09 PrinterName$……….. [\\ACCT-KG\UPS THERMAL 2844]
10 SortReportBy$………. []
11 PageBreak$…………. []
12 Collated$………….. [Y]
13 ThreeHolePunch$…….. []
14 DateCreated$……….. [20061020]
15 TimeCreated$……….. [12.34951]
16 UserCreatedKey$…….. [0000000003]
17 DateUpdated$……….. [20061020]
18 TimeUpdated$……….. [12.59368]
19 UserUpdatedKey$…….. [0000000006]
20 NumberOfCopies……… 1.00
21 MultiPart$…………. [N]
22 TemplateDesc$………. [1 Across Plain]
23 Line1Message$………. []
24 Line2Message$………. []
25 EnableFax$…………. []
26 FaxSubject$………… []
27 FaxUseCoverPageFile$… []
28 FaxCoverPageText$…… []
29 FaxCoverPageFile$…… []
30 FaxBillCode$……….. []
31 FaxKeywords$……….. []
32 FaxHold$…………… []
33 FaxUseCreditCard$…… []
34 FaxSendOffPeak$…….. []
35 FaxUseHighResolution$.. []
36 FaxPrinter$………… []
37 FaxPriority………… .00
38 PaperOrientation……. 1.00
39 PaperSize………….. 1.00
40 PaperSource………… 15.00
41 PrinterDuplex………. 1.00

To correct this issue (only after you’ve ruled out the usual suspects like a problem with Crystal or bad print or corrupt form) — I’ve changed field #39 (which may be labeled with a different number) to 1.

In a support case I just had the number 258 was in field #39 instead of 1.

Changing the 258 to a 1 made the problem go away.

Requires familiarity with Data File Display Maintenance as well as a backup of your SY_ReportSetting.

This file is located in the SY_SYSTEM folder.

If any of this sounds scary or unfamiliar – contact your Sage Business partner.

Always backup first.

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

To create country code on MAS90 and MAS 200 forms:

Earlier versions of MAS 90 and MAS 200 (typically prior to version 4.10 or 4.20) did not allow for easy linking of the country code name to the code itself.

While the country code could be placed on forms (Sales Orders, Purchase Orders, Checks) – the name of the country was not as easy to place for a few reasons –mainly that the data file required to pull the name from was not readily linkable.

Below is a workaround solution that you may find useful. It is primarily for MAS90 or MAS200 (it works on both) versions prior to 4.1 – so if you are using a later version you probably don’t need this procedure because Sage has wisely added country name to the tables that your forms are using.

All steps below require using Crystal Report Writer – which is included with your Sage MAS90 or MAS 200 product disks.

These are not beginner instructions – and assume some intermediate level comfort with Crystal Reports. Backup all your

For this example, assume that we are going to create a form for the ship to and bill to codes. The same logic here with slight modification can apply to any form with a bill/ship field.

Note: Technical information on creating a Crystal Sub report that shares variables is available from:

NOTE: Unfortunately links below to Crystal Reports technical documents appear to have been broken since Business Objects was acquired by SAP.

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

1. Create a page header A that is above the main details (Note: It is important that this comes at the top of the page so that the shared variable calculates before the body of the report. If you do not put it at the top the whole thing doesn’t work). You will need to create a new header (Right click in the HEADER section area and select Insert Section Below. Once that section is created, right click on the section area again on the left side and select MOVE – then you can move it up).

2. Create a sub report for each Bill-To/Ship-To code. These will be placed into the page header created above.
a. Cty_ship
b. Cty_bill
c. Note: Link these back to the main table on the report. You’ll probably want to look in the Database – Visual Linking Expert to see what table is being used to hold your address information.

3. Within each of these subreports:

a. Create a formula as follows (Note: Vary the variable name depending on whether you are creating a bill to or ship to)

b. Place the above formula in the body of the subreport in the details section. Once on the report, right click the formula, select format field, then font, change the font to WHITE (or any shade that won’t show on the report)

c. Place the SY_Country.CountryName in the body of the subreport in the details section. Change the font to white so it doesn’t print on the final report.

d. Leave the Details section viewable – all other sections should be suppressed – ie headers/footers. (Note: If you suppress the details section this won’t work – so be sure to leave it viewable. The way to get around seeing the data on the report is to later change the font to white and make the field very tiny).

e. Make sure your subreport is linked from the SO1_SOEntryHeader.ShipToCountry to the SY_Country.CountryCode

f. When you’ve placed both sub reports into the header section you created above, right click on each subreport and de-select the “can grow” checkbox. (Note: If you do not remove the check you may get a “page size exceeded” message)

4. Within the main report create two variables
a. Country_bill
b. Country_ship

5. Now you can put this variable into your main report formula and the value from the subreport is carried over. The following is the example of it being worked into the @ship to address formula which is standard in the Sage SO Order and Invoice form.

6. Sample formula which has been modified with the new variable.

7. Important: Place the new variables onto the report in the main header section (NOT the sub report) – you can make the white fonts so they don’t print. You must make them viewable (Cannot suppress or this does not work).

BACKGROUND NOTES ON THIS ISSUE:

Q: Client wants to display the Country Code in the forms (SO Orders, Invoices, Purchase Orders, Checks).

A: (Prior to version 4.1 and 4.2) There is no simple way to do this in MAS90/MAS200 — though there are two standard approaches.

The first approach to adding MAS90 country names on forms

Use Alias Tables — this would allow for a table to be used in a report more than once. You give each table an “alias” and it would then allow you to link it to separate fields. This would be needed for the Country Code field because it is potentially a different result for either the Bill To or Ship To.

The problem in MAS90 4.x+ with the Alias Tables is that there is a bug of some sort preventing them from linking to the SY_Country field. This is documented in the Sage KB with the workaround to use a subreport (an ok solution but the country name is impossible to properly line up since it is a free floating field).

The better solution is to use shared variables within the report. Basically this involves creating a new section (header) at the top of the report (important because the variable has to be created before the rest of the report). Then you declare the variables as shared and they can be read from the header on down to the main body.

I did this through the SO and it seemed to work.

Here is the link to the Crystal KB article showing how to create shared variables:

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

On the subreport, you have to create a main subreport, a formula (put this on the subreport) and a shared variable (reference this on the main report).

In the main report you have to create a formula, call up the shared variable (see the Crystal KB for syntax) and then use it in the address formula. Do not forget to put the formula itself onto the form or the value won’t compute.

You want to make the font be white on white. Do NOT suppress and printing or the calculation does not work. If you make it very small you can hide it on the form.

IMPORTANT NOTE: This information is being made available “AS-IS”. Prior to making any changes on your system be sure you have a backup of all forms being modified.

Subsequent upgrades to MAS 90 or MAS 200 table structures may render some (or all) of these instructions obsolete. Sage may also fix bugs that we’ve referred to above. These instructions are meant to serve as a starting point for your own use – and not as a detailed step by step guide to resolving any particular issue. We take no responsibility for updating these instructions. We are not able to provide support (except for our own MAS 90 support clients) on implementing these instructions.

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Sage has just issued their officially supported Virtualization configurations. This one page document (copy below for your convenience – be sure to check for updates as they become available) outlines the various virtualization platforms that may now be used to run both MAS 90 and MAS 200.

Benefits of Server Virtualization:

•Provision additional servers without investing in new hardware
•Run multiple operating systems and applications on the same physical server
•Increase the CPU utilization of an underutilized physical server by running multiple virtual environments
•Move virtual machines from one physical server to another without re-configuration
•Capture the entire state of a virtual machine and roll back to that configuration easily

Benefits of Workstation virtualization:

•Run multiple virtual machines on a single PC
•Quickly provision, deploy and reconfigure physical machines
•Run multiple operating systems and applications on a single PC
•Eliminate risk by creating isolated testing environment
•Built-in Snapshots and easy Restore capabilities

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

A virtual platform is a way that computer users might for example run Microsoft Windows while also using an Apple MacBook Pro. These virtual software platforms have evolved from the early days where they were typically very difficult to get working reliably to present day where many companies are able to use virtual computers quite successfully.

We use VMWare internally to run Sage MAS 90 on an Apple MacBook Pro as outlined in this post from May 2008.

We also have several clients using similar technology including one that integrates their iMac computer into the Windows network while running Sage MAS 90.

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Just heard about this issue on Sage MAS 90 and MAS 200 and thought it may help someone in a similar situation.

MAS90 Purchases Clearing Won’t Foot

A client (version 4.3) reported to me that when the report did not tie to GL,
they manually added up the totals on the Purchases Clearing report. Their total
differs from the report total (and does balance to GL). I verified by exporting
the report to Excel and running a total. Sure enough, client is right.

Workaround

No KBA. Sage knows about it, but because it hasn’t verified by Engineering, it
is not available on the KnowledgeBase. Workaround is to run the Purchases
Clearing by Product Line report, which produces an accurate total.

via: Barbara Goldstein – Quanterasystems – San Jose California MAS 90 Reseller

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

When installing upgrades to Sage MAS 90 or MAS 200 it is not uncommon for duplicate or backup copies of the program to remain in place on your network hard drive while a new version is installed.

This is often done so that your company has a way to roll back to the earlier version of Sage MAS 90 or 200 should something go wrong during (or after) the upgrade.

Unfortunately what often happens is that old copies of MAS 90 are left behind and never erased. This can cause confusion down the road if someone attempts to setup a workstation connecting to your older (and now innacurate) MAS 90 or MAS 200 data.

How To Safely Remove Test Versions of MAS 90 or MAS 200

First, determine where your LIVE (good) Sage MAS 90 or MAS 200 is installed. You can refer to the instructions in this post which outline how to find the proper folder.

Once you find the PROPER folder — take care NOT to delete that one as it is the location of your live active data.

Instead search your hard drive for any folders other than the one above which contain the \MAS90 structure.

Once you’ve located \MAS90 folders which you believe are older test versions, I strongly suggest that you:

A. Rename the suspected older folder to \MAS90OLDTOBEDELETED
B. Within the \MAS90OLDTOBEDELETED\HOME folder rename pvxwin32.exe to be pvxwin32.old

What you’ve just done in the above steps is disable your old version of Sage MAS 90 from starting up. I like to do this and let the system stay this way for several days so I can see if there are any people accessing the old MAS 90 program (usually not) – but more importantly renaming the folder will expose any third party applications which might be using data within the old MAS 90 folder structure.

If there are programs such as paperless or FRX or F9 that try to access the old MAS 90 folder (which you renamed to \MAS90OLDTOBEDELETED) then you will receive an error message which then lets you know that you have either the wrong folder or you need to contact your Sage business partner about moving data outside that folder.

I strongly recommend you make a backup of any files PRIOR to deleting them.

Once several days have passed and nobody has received error messages related to the old data folder – it is generally ok to first make a copy of that OLD folder and to delete it. IMPORTANT: BE SURE YOU ARE DELETING THE \MAS90TOBEDELETED FOLDER AND NOT YOUR LIVE DATA. MAKE A BACKUP FIRST.

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

If you are setting up MAS 90 or MAS 200 under Terminal Server/Citrix and attempting to use Paperless Office for your forms/reports you may receive one of the following errors:

1. Unable to process lockfile
2. Unable to initialize PDF Viewer

UPDATE OCTOBER 2011: See this “Best article on solving Sage ERP MAS90 paperless office printing problems” which contains an updated and more complete list of resolutions for the typical  problems encountered while using paperless office within MAS90 or MAS200.

While there may be other resolutions (One possible cure for which is described in the Schulz Consulting Knowledgebase and involves registry entry changes which you should be extremely careful with), we’ve seen the following steps work to eliminate both of the above error conditions:

Unable to initialize PDF Viewer by selecting “run as administrator” for the MAS200 installation. It appears that this only must be done once and that after the initial time of starting the MAS 200 workstation that the proper DLL (we think cdintf.dll) is then registered.

In order to overcome the “unable to process lockfile” try temporarily adding the user to the “power users” group on the Terminal Server. Re-run the setup of paperless office (this is in Company Maintenance – Email – Advanced).

It appears that both issues are user rights related.

Once the above is done you may be able to successfully test the PDF viewer with no errors.

© 2009 – 2011, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

There are some restrictions on what older versions of MAS 90 and MAS 200 are entitled to.

For example, versions 4.20 and earlier no longer receive service updates. Instead if you find an error you’ll have to beg and plead ask for an individual program fix. Also, version 4.05 and lower no longer have the knowledgebase kept up to date – so if you’re looking for a problem report on a version 4.0 issue you’ll probably not have much luck.

Curious what the restrictions are on the supported levels of Sage MAS 90, MAS 200 (and MAS 500 is even thrown in for good luck)?

Here’s the PDF showing all versions starting with 4.30 and their appropriate level of support.

Supported Versions Policy MAS90 MAS200 MAS500

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

Looks as if not all of the daily processing reports in Payroll are being saved when you are using Paperless Office.

While the payroll Register saves, there have been reports that the Payroll Data Entry Audit Report and Pre-Check Register are being over-written each time a new payroll is generated.

This issue has been reported to Sage and they are working on a fix. In the interim if you are using Paperless Office with Sage MAS 90 or MAS 200 payroll you should make sure you have paper copies of all registers.

90Minds via Beth Bowers and Mike Fitzgerald – The Fitzgerald Group

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

I just had one – and I’m going to share my experience with you so that anyone  who runs into the same (or similar problem) can learn from my 8 hours of hair pulling, cursing and confusion mis-fortune.

Background

One of my clients ordered the Sage AP-1063 Extended Solution that enables ACH processing for accounts payable. Think of it as anothe form of direct deposit – only instead of direct depositing employee checks you’ll be depositing vendor payments (aka – wire transfers).

Before I ordered I casually noted that the client was on version 4.05 (first mistake – they were on version 4.1). When Sage sent the Extended Solution I logged in at 7:15 AM remotely with the client and began the installation.

Unfortunately the version 4.05 install routine did not check to make sure it was actually installing to a version 4.05 system – -and dutifully installed itself over my version 4.10 system.

Luckily I caught this and quickly determined that version 4.10 of the Extended Solution was needed. Once I ordered the re-packaged part, Sage was quick to email it over to me.

Here’s where the fun began.

Extended Solutions Say’s “Now Installing Extended Solutions” – Forever

Technically the message did not stay there forever. After three hours the client wisely decided to end task and call.

From there I logged in and we engaged Sage to assist in looking at the issue. Neither of us were able to determine the cause due to the lack of any error messages.

As a final resolution Sage offered to look at the data (all 5 GB) if we would upload to them. Fearing the lengthy upload time (easily a day or two on the clients poky network) I declined to upload.

Luckily the client ran into another error — Error 88 SY_Report.PVC Line 203.

This error message was in the knowledgebase and the cure was very simple. Luckily the cure for the above error also resolved totally my “Now Installing Extended Solutions” hung installation problem.

The Resolution

The fix for both the error message and the hung Extended Solution install routine was to go into the \MAS90\SOA folder and delete any SY_*.PVC files (I suggest you move these somewhere as opposed to outright deleting – just in case).

Once those files were deleted, the Extended Solution installed just fine and all error messages vanished. My theory is that the v4.05 Extended Solution may have dumped those SY_*.PVC files into \MAS90\SOA which in turn caused all my subsequent error conditions.

Hope this is helpful to someone else in the future.

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.

If you receive the message:

“Batch number xxx already exists in the direct deposit transacton file”

While trying to update your payroll register — take the following action:

1. Go to Payroll
2. Direct Deposit Menu
3. Generate Direct Deposit Interface
4. Select the second option on the menu – Purge Direct Deposit Interface Files
5. Select a beginning date that is early enough to remove the offending register number (Tip: In some instances I’ve had to go back as far as 1900 even though I was certain we weren’t using Sage MAS 90 payroll Direct Deposit then…;-)  )

Link: Sage MAS 90 and MAS 200 Direct Deposit Manual (PR-1017)

© 2009, Wayne Schulz. All rights reserved. Sage 50, Sage 100, Sage 300 and Sage 500 are registered trademarks of Sage. Have additional unanswered questions about MAS90? You may contact Schulz Consulting here.

We publish an email newsletter each Tuesday at 3pm – join here.