If you are in retail business: deli store, for instance, chances are high that you are deploying Counterpoint Point of Sale and Retail Management application, from where you need to integrate records to your ERP.
We will give you highlights if your back end ERP is Microsoft Dynamics GP or former name Great Plains. We have already described solution which work in the case of GP integration with Microsoft RMS, now is Counterpoint integration review time:
1. Daily sales. In counterpoint you export them as text file, ready to be imported into GP via Great Plains Integration Manager. You will need to purchase GP IM financials software license. In Great Plains integration you should choose General Journal Transaction destination. We recommend you Advanced ODBC source, as it gives you SQL scripting advantages over Simple ODBC or Text Source. As you may already know GL TRX requires Header and Lines Sources, and in the case of Counterpoint export you build them from single file – in the header you simply use group by clause in SQL query
2. Store Purchases. In Counterpoint you normally work with goods ordering and receiving them in stock, however then you would like to see vendor invoices and pay to your vendors in Dynamics GP. Counterpoint exports vendor invoices as flat text file. Here you has no option, but use advanced ODBC source, where you have to produce vendor invoice header and lines
3. Altering Counterpoint Export. Counterpoint deploys Microsoft SQL Server Data Transformation Packages (DTS Packages) to export records from Counterpoint database, also hosted in MS SQL. Each package has the option to be modified, where you need to be pretty familiar with Counterpoint DB and table structure to pick alternative fields, plus you need to be comfortable with SQL stored procedures. Export tailoring is required when you want to see additional counterpoint fields (normally not included in export to GP) on GP GL transactions or Vendor invoices
4. Consolidated Reporting. As both GP and Counterpoint reside in MS SQL Server and are SQL Server D applications, you can deploy cross-server integration stored procedure to pull data into consolidated Crystal Report or MS SQL Server Reporting Services (SRS) report to combine data from Counterpoint and Great Plains. Good example: Counterpoint goods received and sold, but not yet paid to your suppliers
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
