Microsoft Dynamics GP consulting field nowadays typically requires high-end technology expertise and hands-on experience. If you are implementing Microsoft Great Plains in large or mid-size company, you expect your new ERP application to be seamlessly integrated into your existing IT infrastructure: Microsoft Windows domain, probably elements of such non-Microsoft systems as Linux Red Hut and PHP with MySQL (or another Linux brand), Oracle db integration, and things like these
Also take into consideration the needs to switch from unsuccessful implementations of concurring MRP products: Oracle EBusiness Suite, People Soft, PeachTree, Accpac, MAS 90 or 2000 – then the need of technical expertise in ERP data conversion will be even more valuable. We’ll try to keep reasonable balance in ERP consulting requirements expertise, reviewing it in this article
1. Great Plains Dexterity – is more likely the must. Historically in earlier 1990th Great Plains Software Dynamics was designed on GP Dex platform. Dex is in fact C-shell, meaning that C programming language was used in the developing of Dexterity Integrated Development Environment. Of course, currently Microsoft is marketing and positioning GP on MS .Net platform, so Dexterity is kind of legacy, comparing to .Net. However here we have to play Dex apologetic role – if your GP business logic was designed and programmed in Dex, then Dexterity modification upgrade path is critical for you
2. Great Plains data massage, this is related to GP data conversion. ERP data conversion is expected scenario, however this is typically something that is not cheap and you should review all your possible options, prior to diving into full-scale data migration
3. Heterogeneous GP reporting. Microsoft SQL Server allows you to deploy such constructions as SQL linked server, where you can query data (using OPENROWSET command) from non-Microsoft platforms, such as Java, Oracle, Sybase or IBM DBII related
4. eConnect. This tool or SDK was initially dedicated to eCommerce developers and programmers, opening for them Microsoft Dynamics GP objects realm for programming and e-commerce integration. eConnect should be moderate learning lesson for C# or VB.Net MS Visual Studio developer, as it is in its core set of encrypted SQL Stored Procedures
5. SQL Scripting for GP integration. Of course this approach is not “object-oriented” and it is not recommended for somebody who considers himself as GP novice. However, if you are scripting for Great Plains for over 5 years, you should recognize that direct SQL scripting is the most efficient way to gain integration performance
6. GP Reporting. Here you have a choice: Crystal Reports, GP ReportWriter, MS SQL Server Reporting Services or SRS, MS Excel, MS Access, Microsoft Dexterity, FRx – all these tools are in your disposition, and you should make your homework in identifying the best tool for the specific job
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
