Microsoft Dynamics GP is becoming very popular ecommerce ERP and accounting back office. This trend is probably related to success of eConnect SDK, especially for Dynamics GP 10.0 and 9.0 versions.
eConnect allows you, being generic C#, VB.Net programmer with good SQL and XML skills to program Great Plains objects manipulation: Customer, Address, Sales Invoice, Customer Payment and other attributes of ecommerce shopping cart. eConnect, being coded in SQL Server Stored Procedures (they are encrypted, so you probably should not expect to trace SQL code for Great Plains business logic there). In this small publication we would like to share with you ecommerce coding experience and Dynamics GP automatic batch posting from eConnect application directly:
1. Older versions of Great Plains Dynamics GP. If you are on GP 8.0, 7.5, 7.0, 6.0, 5.5, 5.0 or earlier versions, we recommend you to upgrade to Dynamics GP 10.0 as for this version eConnect is really advanced. If you do not have registration key, probably due to the fact of lapsing in Dynamics GP Great Plains annual maintenance program, consider deploying Sales Order Connector, or set of SQL stored procedures, created for ecommerce web developers of older Great Plains version to connect ecommerce shopping cart with GP Sales Order Processing module, please call us for details. If you are on Pervasive SQL or Ctree, your options are very limited, you can still try to program ODBC connection to Pervasive SQL 2000 database, but then you will have to reprogram the logic, which is in fact available in eConnect (if you migrate from Pervasive to Microsoft SQL Server and upgrade to new version GP 10.0)
2. Automatic Batch Posting. Here we often hear from ecommerce programmers the question – why eConnect doesn’t have the tools and logic to post Great Plains SOP Batches (as well as post batches in other Great Plains modules). The answer is in GP architecture (it is pretty common, and you should expect similar restrictions in other ERP and MRP platforms). The concept of ERP business transactions flow suggests you to use three phases of transaction life: work, open and historical. eConnect allows you to create work transactions, in Great Plains these are newly created invoices or sales orders, placed in the batch and submitted for Great Plains user review and posting. In order to trigger Dynamics GP batch posting from eConnect application directly – you have to deploy Great Plains add-on – Alba Spectrum Posting Server
3. Posting Server. It consumes one user license and deploys Dynamics GP Dexterity source code to trigger the same coded logic in Dexterity for batch posting. Autopost is targeted to eCommerce web programmers, plus it post virtually all types of Great Plains Batches: GL, Inventory, Payroll, AP, AR, SOP
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
