How to Address a Functionality Gap in Dynamics GP

When you have a functionality gap between what Microsoft Dynamics GP offers and what you need the software to do, you will need to pick one of three ways to address the issue. The first is to adjust your procedures such that standard Dynamics GP functionality can address the requirement. This “work-around” approach is the least amount of out of pocket money upfront, and is a good approach as long as it doesn’t cause procedural in-efficiencies that can come at a price tag over time. The second option is to explore having a customization written to address the functional gap. Dynamics GP Customizations can be pricey but are justified if the added functionality is essential to the software ultimately meeting the company’s needs.  The third option for addressing a functionality gap is to look at what are called 3rd party products. These products are designed by independent firms, and exist specifically to enhance the Dynamics GP offering. 3rd party products most of the time will have the same look and feel as your version of GP, are upgraded in line with Microsoft’s scheduled upgrades of GP, and are usually priced affordably.

On a recent project we were faced with 2 functional gaps that we addressed with 2 different 3rd party products. The customer wanted to account for all 20 of their companies in one Dynamics GP database. Putting the companies under one database allows them to share vendor and customer accounts, centralize cash disbursements, and stay in one database file instead of constantly logging in and out of the different databases all day long. One requirement they had was the need to book transactions between companies that would result in automatic intercompany postings. This was a challenge with all companies being in one database. Dynamics GP has a module called Interfund that came close to meeting their needs, but ultimately fell short. We ended up deploying Nolan Business Solutions 3rd party product called Intercompany Postings. It comes with functionality that addresses what they call “Intra-company” postings when the companies are in the same database. This module gave our customer the functionality they needed to get the correct intercompany entries booked automatically.

The second challenge we faced was that their customers could buy from the different companies in Dynamics GP, and they wanted GP to book all debits and credits for the sale to that locations general ledger accounts (sales, accounts receivable, inventory, and cost of sales). Setting up Inventory Sites for each company, and assigning the appropriate company code to the site, gave them all the right general ledger postings for sales, cost of sales, and inventory, but not accounts receivable. The accounts receivable account didn’t default to the correct company code. We deployed a 3rd party product from KTL Solutions called SOP/POP Advanced Distribution that allowed us to default the correct company code to the accounts receivable account.

The products from Nolan and KTL Solutions mentioned above were reasonably priced, easy to deploy, and met our customer’s business requirements.

 

This post was written by Andrew Warner, Solutions Consultant at Tridea Partners, a CA, UT, CO Dynamics GP Partner 

Leave a Reply

Your email address will not be published. Required fields are marked *