Dynamics GP ISV Partner Newsflash: Great Plains Tables Structure Training

Jun 5
07:57

2009

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

If you have Microsoft Dynamics GP ERP and MRP application implemented in your organization and you are IT programmer, who needs precise training on connecting to Dynamics GP database and reviewing data flow and table structure, we would like to give you short orientation in this publication. We assume that you are familiar with relational databases and SQL Querying technique.

mediaimage

Typically GP DB structure knowledge is required when you are planning to develop real time or batch mode integration from legacy applications,Dynamics GP ISV Partner Newsflash: Great Plains Tables Structure Training  Articles such as Lotus Notes, Oracle Sales Order Processing, MySQL/PHP ecommerce website, or when you plan to design complex Crystal Reports, SSRS.  It is also helpful in custom simple EDI interface design:

 

1.       Where to find tables structure.  There are several options.  First, you can install Dynamics GP SDK from CD #2, where you can find complete picture on the Great Plains architecture.  Second, you can login GP and go to Tools->Resource Description->Tables (also Windows and Fields, if required to understand desired Window or Field association with the set of tables).  Of course, second option doesn’t give you holistic picture of the tables clustering and relations, keep reading on GP data flow

 

2.       Table classification.  In Dynamics GP you have several types of tables: Setup (normally prefix is 4XXX – module setup, such as General Ledger – which account is used for Retained Earnings, to give you the idea on what is there), Master records (normally prefixing with 0XXX: RM00101 is Customer Master table), Work tables (prefix 1XXX, example is SOP10100 – Sales Transaction Header), Open records (when you post work transaction, it goes to open status, prefix 2XXX, example RM20101 – Receivable Open Transaction Files), Historical records (prefix 3XXX, example RM30101 – Receivable Transaction History Files).  Example of data flow in General Ledger module: when you create GL transaction it sits in GL10000 Header and GL10001 Lines, then you post transaction and it moves to GL20000 Year-to-Date transaction Open, and then when you close the Year, GL20000 is moved to GL30000 Account Transaction History

 

3.       Some cautions.  If you think that you can do direct SQL data feeding to GP Tables, think about business logic possible data integrity compromises.  There are great Dynamics GP integration tools and SDK: Great Plains Integration Manager module and eConnect.  Both of them validate business rules and do not allow SQL insert, which compromises the rules.  In our opinion, it is probably more efficient and time consuming way to invest into Dynamics GP IM or eConnect training or self discovery and avoid possible future data corruption and recovery expenses

 

4.       If you need Great Plains and FRx Architecture precise training, please give us a call: 1-866-528-0577, or help@albaspectrum.com In our experience, four hours is very efficient time frame to communicate to you Great Plains architecture, we offer training Worldwide through web session and skype