When you are facing e-commerce transactions volume growth – typical solution is to remap backoffice ERP system to more scalable. In this small article we consider the case, when you remap eCommerce to Microsoft Great Plains Dynamics GP. If you make your homework and search the internet to understand your options, you will see that several out of the box solutions are out there, however it is typically not what you are looking for: you would like to keep your existing ecommerce solution with shopping cart, checkout and credit card processing. In this case – you way is eCommerce integration to Microsoft Dynamics GP
o Remapping technology. Let’s assume that you had something like SAP Business One, where you deployed SAP B1 SDK and programmed eCommerce to SB1 integration in Microsoft Visual Studio C# project. When you remap to GP – you also use MS Visual Studio and C# programming language and GP integration tools, described in the next section
o eConnect. The core logic of eConnect is realized as a set of SQL stored procedures and you can manipulate such GP objects as Customer, Sales Invoice (or Order if you plan to transfer order to invoice later on)
o Automatic Posting dilemma. Looking back to SAP Business One – there when you create Invoice – it is already “posted”. In the case of Great Plains – Invoice is created in so-called “work” status, then typically placed into the batch for approval and posting by GP operator. eConnect does allow you to create Sales Inovice, but it doesn’t allow you to post it automatically from eCommerce application. This is natural restriction of Great Plains Dexterity architecture
o Posting Server. This solution is available for purchase and it uses Microsoft Dexterity posting engine. What you need to do as eCommerce developer is to place the batch into the table, and so approving it for posting. Posting Server checks the approved batches table every five seconds and posts the content of the table. Alba Spectrum Posting Server requires GP workstation running on separate computer – expect one additional user license
o Excurse to Microsoft Dynamics GP Dexterity. It was designed as a shell, written in C programming language to resolve DB and OS dependency. Dex.exe is the application and it launches dictionaries, such as DYNAMICS.DIC. you can find Dex dictionaries, listed in Dynamics.set file. Programming Dexterity should be left to professionals, as it proprietary and pretty unique scripting language: sanscript – plus dex programmer should be familiar with dex architecture and tables structure. Dexterity enables various customizations, integrations, modifications to existing GP business logic.