Dynamics GP Financial Reporting is typically realized in FRx. FRx reporting has direct connector to Great Plains General Ledger, where it uses Accounts Summary table (this is why when you do GL direct SQL transaction feed, you have to reconcile accounts, by doing this – you recalculate Accounts summary table records), potentially it can even drill allow you unposted transactions inclusion (assuming that you posted Sales, Purchasing, Payroll transactions to General Ledger, where they are waiting for review and approval to be posted).
In this small publication we would like to review the most common mistakes and pitfalls with FRx installation in client-server environment:
1. Compatibility with Great Plains Dynamics GP 10.0. FRx should be of the version 6.7 and you must apply Service Pack 9. You can download FRx service pack from Dynamics GP Partner Source, if you are Great Plains VAR or Consultant. Just to be sure, that you will not be able to launch FRx user, if you just have FRx 6.7 CD – Service Pack 9 or newer is required. If you are installing not the first FRx workstation, please apply the same FRx Service pack as you have on other FRx workstations in production environment
2. ODBC name misspelled. Yes, surprisingly enough this is one of the most popular mistakes, especially often done by internal IT people to whom Great Plains Resellers are trying to entrust FRx installation job. Before calling to Microsoft Business Solutions technical support (if you are not on unlimited cases per year in your Deluxe support plan), please open FRx, cancel logging to the company and follow this route: company, information, click on the intended company, switch to system specific information and write down Data Source Name. Then, open control panel, administrative tools, ODBC, System DSN and compare the name in FRx with the ODBC System DSN name (including spaces). If you now see the difference, please do not change the Data Source Name in FRX (if you do this – all the other, old FRx users will lose the connection to the company from their FRx workstations), instead create new system DSN on the new FRx workstation
3. Other support cases are about changing Natural segment to be different from Dynamics GP first account segment, detail level, rebuilding FRx specification set (with catalog, row format, column layout, reporting tree), consolidation, where you eliminate intercompany transactions in P&L, Balance Sheet and Cash Flow Statement
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
