Microsoft Dynamics GP is open to ecommerce programmer via eConnect SDK, as well as Microsoft SQL Server programmability tools (typically Stored Procedures and Views). Before you dive into technical project of eConnect programming, please, review Great Plains Integration Manager module and its customization options: VBA scripting of Before Document Commit ...
Dynamics GP Integration Manager based (for version 10.0 and future versions 11.0 and up) on eConnect technology (in addition to supporting old OLE Server integrations), meaning that IM integration should be able to achieve the same goal with less efforts. And as you should expect the same limitations for eConnect as you have for Integration Manager - most often manifesting limitation is eConnect and Integration Manager Batch Posting inability. Now straight to the Great Plains eCommerce Developing topic:
1. eConnect is Software Development Kit, written in SQL Stored Procedures (encrypted), it allows you to program GP master records (Customer, Vendor, Employee, GL Account, Inventory Item, Address, Project, Budget, etc.) and so-called Work Transactions: SOP Quote, Order and Invoice, POP Purchase Order, GL Transaction, Employee Paycheck, Inventory Adjustment and Transfer, to give the idea. eConnect is friendly and requires very short learning curve for Microsoft Visual Studio .Net C#, VB and other .Net compliant languages programmers. Additional pluses if you have XML, SQL Scripting skills
2. Sales Order Processing and Inventory Control modules and tables. These two are the most popular in ecommerce integrations. SOP tables have SOP prefix (famous SOP10100 transaction header and SOP10200 lines), and Inventory INV (INV00101 - item master and INV00102 Quantity master) respectively. Sometimes, especially in old Great Plains ecommerce legacy integrations you find Invoicing module (IV prefix)
3. Posting problem. In ecommerce application you often want to do all the way transaction processing: Sales Invoice creation and modification, applying credit card payment deposit, allocating merchandise, approving and posting Sales Order Processing batch (or individual transaction). Here, you will hit the wall and realize that Posting functionality is not included in eConnect or Great Plains Integration Manager. There is no shortcut here (we assume that you are Not Dynamics GP Dexterity software developer with tons of programming experience, including Dexterity Source Code Programming), you will need to purchase Dynamics GP Add-On, we recommend Dynamics GP Posting Server, also known as Autopost
4. Dynamics GP eCommerce SQL Scripting. If you have the opinion that your ecommerce integration routine is very simple and eConnect is too cumbersome and heavy in being considered for deployment, you can always rescue to SQL direct insertion statement. Please review GP table structure: Dynamics GP -> Settings -> Resource Description -> Tables. Or, simply install GP Software Development Kit from CD #2. Dynamics GP Business Logic might be too complex for intuitive programming, so if you will get the buggy situation, consider creating test transaction in GP user interface and review the records in GP tables. If you prefer proven set of stored procedures - we offer them as Order Connector, feeding data into SOP tables
5. Feel free to call us on Microsoft Dynamics GP eCommerce integrations concerns: 1-866-528-0577, help@albaspectrum.com
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
