If you are eConnect developer, who is curious about Sales Order Processing batch posting options, this article should give you highlights. eConnect as SDK at the end of the way calls encrypted stored procedures, which allow you create, modify, delete so-called master records: customer, vendor, employee, customer address to give you few examples.
Plus it allows you to create so-called work transactions: Sales Invoice, which is especially popular in e-commerce programming and integration scenarios. However it is often the need to push transaction to Microsoft Dynamics GP SQL database all the way through, meaning to post Sales invoices and returns batches from eCommerce application. eConnect out of the box doesn’t post batches and this is the restriction of the architecture, or as it was initially designed:
1. Batch posting technical side. What is really happening in Great Plains when GP user hits post button? Well, GP engine, which is Microsoft Dexterity (former name Great Plains Dexterity), calls its internal procedures and these procedures move Invoice records from work tables: SOP10100 and SOP10200 (there are more tables, we are giving these two for illustration purpose only) into SOP30200 and SOP30300. However this is only part of the story. When posting is done in Sales Order Processing module, Dex transfers posting to Receivable Management module, where it creates records in RM20100 and others. Then it creates Cash Deposit with Receipt in Bank Reconciliation module (if deposit was applied, such as Credit card payment) and even that is not yet the end of the story. Finally it creates (and even posts if settings are to post through GL) General Ledger transactions. You can imagine, that eConnect as being only top of the iceberg, is too light weight SQL scripting collection to do all the GP autoposting business logic
2. But anyway – why GP doesn’t extend eConnect with batch posting logic? Well, the answer is simple – posting is subject for management approval and holdings removal. Plus, posting should have audit trail on who physically pressed posting button and when – eCommerce application is robot and it is probably reasonable to restrict eConnect to transaction creation only
3. Autoposting Server. This application allows you to place created batches into queuing table. Autopost monitor the table and if it finds record there, it initiates GP Dexterity internal posting logic. In this case batch posting process is in control of C# or VB eConnect developer
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
