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 make, modify, delete so-called master records: customer, vendor, employee, customer address to give you few examples. Plus it allows you to make so-called work transactions: Sales Invoice, which is especially standard in e-commerce programming and integration scenarios. But it is evenly 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 Fantastic Plains when GP user hits post button? Well, GP engine, which is Microsoft Dexterity (former name Fantastic Plains Dexterity), calls its internal procedures and these procedures go 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. But this is only part of the tale. When posting is done in Sales Order Processing module, Dex transfers posting to Receivable Management module, where it makes records in RM20100 and others. Then it makes 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 tale. Irrevocably it makes (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 anyhow – why GP doesn’t proffer 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 confine eConnect to transaction creation only
3. Autoposting Server. This application allows you to place produced 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