Contact us today: (866) 4-WEBSAN (932726)                Get Instant Support

As of April 1, 2013, the Government of Prince Edward Island is implementing the Harmonized Sales Tax (HST). The combined HST rate in PEI will be 14%, of which 5% will represent the federal part and 9% the provincial part. Further, the Government of British Columbia will be eliminating the HST and reinstating PST and GST on taxable services provided in British Columbia. As of April 1, 2013, you will be taxed GST at a rate of 5% and PST at a rate of 7%.

To create the ability to track these changes in Dynamics GP, one must utilize Tax Details and
Tax Schedules.  Tax Details identify specific taxes and their rate of taxation.  These are then assigned to & grouped on Tax Schedules for processing transactions in GP.  Tax Schedules can be assigned to Customers, Vendors, Items, etc.

Setting up Tax Details

  • Enter a Tax Detail ID and a Description.
  • It is important to set the Type properly as Tax Details can apply to either Sales (to a Customer) or Purchases (from a Vendor) exclusively.
  • Set a default GL Account to distribute tax transactions to in order to capture values in the general ledger.
  • Set both the Based On & Round values depending on the tax.  For HST & PST, these should be set to Percent of Sale / Purchase & To the Nearest Currency Decimal Digit respectively.
  • Set the Percentage for the Tax Detail.  For HST PEI, this is 14%.  For PST BC, this is 7%.

Tax detail maintenance 1

Setting up Tax Schedules

The Tax Schedule Maintenance window contains two list boxes:

  • The Available Tax Detail IDs list box displays a list of all the tax details entered.
  • The Selected Tax Detail IDs list box displays the details added to this schedule.
  • To add tax details to a tax schedule, highlight a detail in the Available Tax Detail IDs list and click Insert. The detail is inserted in the Selected Tax Detail IDs list and is included in this tax schedule. Continue selecting and inserting details until the complete tax schedule is created.

Tax detail maintenance 2

Assigning Tax Schedules to Customers/Vendors

Once tax schedules have been created and saved, the last step in the process is to assign the tax schedule to a customer or vendor, etc.  If a new tax schedule is to be applied to a customer, navigate to the Sales > Cards > Customer.  Then, select the appropriate customer & enter the appropriate value in the Tax Schedule field.  To assign the tax schedule to a vendor, navigate to Purchasing > Cards > Vendor.

For more information contact us at This email address is being protected from spambots. You need JavaScript enabled to view it., WebSan Solutions Inc., a Canadian Certified Microsoft Partner

Published in WebSan Blog

Learn more about Dynamics GPView Dynamics GP PricingFree Dynamics GP Training

There are a number of recorded issues with Microsoft Dynamics GP 10.0 and 2010 when attempting to reference VBA code on 64-bit machines. Both Office 2010 and Crystal Reporting are known culprits in causing this issue to occur, as their installations update some system registry keys for VBA 6 incorrectly. Office 2010 references VB7, thus it should not be affecting keys it does not require. Registry Keys are used by the system as container objects, similar to folders, that can store values or further keys. If the value of a registry key is changed without the knowledge of an application that references its value, problems can arise. This would be the case for the VBA 6 file not being found.

I recently had a client of whom we were aiding implement an on-premise installation of GP and needed to deploy the software, along with any customized forms and reports we had designed, to a dozen workstations. After completing the deployment steps without any issue on the first three workstations, it was not until the forth that the system administrator eventually encountered the “File not found: VBA6.dll” error. The error can occur either on login to GP or when accessing custom VBA code through ‘Modifier’, if installed. Upon discussion, I was told that both Office 2010 and Crystal Reporting resided on the machine (Crystal was later removed, however the effects its installation has on registry keys can remain even after its removal).

To resolve the issue, there are two steps that need to be confirmed and/or completed to allow GP to properly reference the system dll:

(NOTE: Making changes to system registry keys is only advisable for advanced users, as incorrectly performing any steps can corrupt the system if care is not taken. Contact your system administrator for help.)
1. Ensure that Dynamics GP is not running.

2. We need to ensure that ‘VBA 6 Core components’ is installed on the workstation. This can be found in the following path: C:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA6\VBE6.dll

If the file or path does not exist, then the VBA6 folder can be copied from another workstation that has it on their system. Otherwise, the VBA 6 Core Components will need to be downloaded and run on the machine to install the correct files. This can be accessed from: https://mbs2.microsoft.com/fileexchange/downloadfile.aspx?fileid=2208ac6f-d575-4f34-8b19-40340fe3d20c(the download will require either a CustomerSource or PartnerSource login). The file can be obtained through other means, but you need to ensure that the file is coming from a trusted site as dll files, along with any system files, can be dangerous to your system if they are not genuine.

3. Once the path and the dll file exist on the workstation, we will need to update a registry key to point to the new path:

a. Click on the Windows start button and in the search box, type: regedit and hit enter

b. This will open the Registry Editor window.

From here, you will need to navigate on the left side of the window to: HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0\9\win32

and ensure the path for the key is set to: C:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA6\VBE6.dll

Registry Editor

c. If the path specified above does not exist in the System Registry, then we will need to create a registry file to add the appropriate node.

i. Open ‘Notepad’ and copy the copy the following text into the blank document:
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0]

@="Visual Basic For Applications"

[HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0\9]

[HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0\9\win32]

@="C:\\Program Files\\Common Files\\Microsoft Shared\\VBA\\VBA6\\VBE6.DLL"

[HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0\FLAGS]

@="0"

[HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.0\HELPDIR]

@="C:\\Program Files\\Common Files\\Microsoft Shared\\VBA\\VBA6\\"

ii. Save the Document as a .reg file. Now, double-click on the registry file you just created and click ‘OK’ to add it to the system registry.

4. Start GP and enter your credentials. Now proceed to perform whatever task was notifying you of the error.

With the dll file in place and the path correctly pointing to the file, the error message should disappear. Hopefully, Business Objects, and especially Microsoft, ensure that their products do not affect any registry files that do not pertain to the particular application themselves.

Brandon Germaine is an Application Specialist at WebSan Solutions Inc, a Microsoft Dynamics GP Silver Partner & 2012 Microsoft Impact Awards Finalist. Brandon can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it. or 416-499-1235 ext 219.

Published in WebSan Blog

Learn more about Dynamics GPView Dynamics GP PricingFree Dynamics GP Training

If you have ever created any customized reports from within Microsoft Dynamics GP, then you are quite aware of how reporting can be a useful tool in extracting the exact information needed to increase your productivity and make effective business decisions. While there are a number of different reporting methods that can be utilized (such as SQL Server Reporting Services (SSRS), SmartLists, and Word Templates), the most popular and basis for reporting within GP is Report Writer.

While exceptionally powerful, Report Writer is not the easiest application to operate without prior knowledge or experience. However, the following is a trick that one can use to have Report Writer work for you.

A few weeks ago, a client had requested a Purchase Order form for a new company that they had just recently added to GP. The formatting of the PO form was to resemble that of an existing company, the only difference being a change in logo in the top-left corner of the report. Should be easy. However, Report Writer will only allow two versions of the same type of report: either the original GP standard or the modified version. When a report is 'modified', it will print in place of the standard version of the report. Although there are both 'Copy' and 'Duplicate' options when choosing a report to customize in Report Writer, these secondary versions of the report will only be accessible through (Reports → Customized) within GP and cannot be printed or displayed, for example, from the 'Purchase Order Entry' window.

Luckily, the Purchase Order form has two documents types: the Blank form or Other form. This way, both companies can utilize their own type of purchase order form. However, if the client requests the POP Purchase Order Other Form to be a copy of the POP Purchase Order Blank Form, the latter having numerous formatting changes and functions created; the replication of this report can be a lengthy process. There must be a better way, right? Well, there is.

Through the (Microsoft Dynamics GP → Tools → Customize → Customization Maintenance) menu, you can export a package file of the report you wish to copy. Package files are XML formatted and contain all the modifications and fields used on the report. Due to their text-based nature, these files can be manipulated within a simple text editing program, such as Notepad, without ever having to access Report Writer itself. After exporting the POP Purchase Order Blank Form as a package file (the form we would like to replicate) we can open the file and copy all text between the Report “POP Purchase Order Blank Form” line and the closing </Component>line.

1

2

This can then be pasted into an exported POP Purchase Order Other Form package file, in the exact same location of the text document (between Report “POP Purchase Order Other Form” and the closing </Component>).

Once saved, the POP Purchase Order Other Form package file can be imported back into GP through the Customization Maintenance window. The only step remaining is to replace the logo in Report Writer with that of the new company. Simple.

When importing packages into GP, it is important that all users, other than yourself, are logged out as the package will not import correctly and problems can occur. Backing up existing packages files is always a good idea in the case that something goes awry. Access will also need to be granted to the users who wish to view or print the modified report.

Tricks like this one can save you a lot of time and stress when dealing with reporting in GP, and if a particular task appears as though it will take more work than warranted, then it is likely that there is an easier way of accomplishing it.

Brandon Germaine is an Application Specialist at WebSan Solutions Inc, a Microsoft Dynamics GP Silver Partner & 2012 Microsoft Impact Awards Finalist. Brandon can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it. or 416-499-1235 ext 219.

Published in WebSan Blog

There are several different elements that need to be well thought-out in order to receive a good ERP quote. Enterprise Resource Planning by definition is a system that integrates information across a company using services such as: finance/accounting, manufacturing, sales, customer relationship management (CRM) and more. You want to make sure that you get a quote that’s in your budget, but you don’t want to sacrifice the essentials to stay within your budget either. Make some room in your budget for fluctuation and negotiation to ensure that you get the best quote.

Modules

There are a number of modules that are offered in an ERP system, it’s up to you to choose which ones best fit your company. For example if you are a consulting company maybe you only need CRM, Finance and the Sales module. Save money on modules that you don’t need and get the one’s that you do need. You have the option of getting standard or advanced modules. Advanced modules offer more variety of features but are usually used for larger businesses. There needs to be research done to explore what particular capabilities you need.

Number of Users

The number of user’s plays an important role when determining the price. It is important to have a firm estimate of the amount of user’s that you need. Plan in advance to avoid unanticipated cost and to get a more accurate quote.

Training and Customizations

Training can sometimes be overlooked when budgeting for an ERP solution. Even though training could be included in the ERP quote, keep in mind the degree of training they offer. If you know that your staff is going to need more training than what’s offered, suggest to the vendor that you need more training. If you want a feature that is not available but can be done as a customization then that could increase your budget as well.

Natalie Williams, Marketing Coordinator, WebSan Solutions Inc., a Canadian Certified Microsoft Partner

Published in WebSan Blog