Ecommerce Programming for Great Plains Dynamics GP – Introduction

If your organization implements Microsoft Dynamics GP Great Plains ERP and you’re thinking of connecting it to your eCommerce site, we’d like to give you an initial introduction: where to start researching GP, tools, integration options, limitations, pros and cons, and other typical. FAQ The current version of Great Plains is 10.0, we assume it’s reasonable to be listed in version 9.0, before starting the e-commerce connection project; otherwise, it will reschedule your integration with the version update. If you have older versions, especially Pervasive SQL 2000/Btrieve or Ctree/Faircom (this could be the case if you have GP 7.5, 7.0, 6.0 or earlier), we recommend that you upgrade to the MS SQL Server based version first (you should contact with your MBS VAR and they will provide you with the migration tool and it is recommended that a professional Great Plains consultant do the conversion)

1. Sales Order Processing Module or SOP. This module is normally integrated with your eCommerce application. In e-commerce, create a SOP order or SOP invoice. The easiest scenario is to create an order or invoice without inventory item allocation, this is especially recommended if you are trying to program the integration in SQL stored procedures.

2. Structure of the Great Plains tables. This is one of the first questions we hear from developers. You need to login to GP, depending on the version, we will give you the path for version 10.0: Microsoft Dynamics GP->Tools->Resource Description->Tables. The tables are grouped by GP series: Financial, Sales, Purchases, Inventory, etc.

3. Microsoft Dexterity technology. You should note that if you populate the GP table records, you should treat the GP business logic accordingly. The most important is GP Dexterity’s business logic treatment, which is validated when the Great Plains client application attempts to read the records, completed by you; if the business logic is violated and cannot be validated, the Dexterity interface will throw an error and make GP ERP inoperable.

4.eConnect. Yes, this is what you should consider using whenever possible in ecommerce. The core of eConnect is a set of SQL stored procedures, which allow you to create, modify, delete GP master records (customer, vendor, inventory item) and work transactions (such as SOP invoices or SOP orders), plus eConnect assigns invoices or order lines. , so the topic one limitation is not an issue here. What eConnect cannot do is publish individual transactions or batches of SOPs – this routine is left to the GP operator by the GP architecture

5. Publishing server. Alba Spectrum Posting Server allows you to combine eConnect with auto posting directly from your eCommerce application. The Publish Server is a GP Dexterity application and must be installed on a separate GP Workstation (or on your GP Server, where you keep the GP Workstation with the Publish Server running). When deploying the publish server, you will need to put the approved batches into custom tables and the publish server will handle the publishing process.