subject: Posting Server Extension To Dynamics Gp: Ecommerce, Manufacturing [print this page] You may have several situations, where batch posting needs automation. One of them is often seen in eCommerce integration scenarios with Great Plains, where eCommerce programmer tries to deploy eConnect and makes the discovery that eConnect can only create, modify or delete so-called work transaction (usually you transform eCommerce shopping cart into Dynamics GP SOP Invoice, which should be reviewed and posted manually by GP operator). Second type of scenarios is more generic. Imagine that you have simple manufacturing order (Microsoft Dynamics GP Manufacturing suit of modules), which you want to automatically create, and fulfill and post all the way to GL. Automation application needs to read MO data from Barcode driven External Assembly system for tracking finished goods and parts quantities. Let's review how these scenarios could be automated with Posting Server:
1.Sales Order Processing Bath posting automation. Posting Server allows you to mark batches as ready for posting directly by ecommerce web site developer and market batch is posted automatically (in quasi real time - Posting Server checks if new batches are market for posting every thirty seconds). You can also optionally transfer any type of SOP transaction into its final document and post. Usually you transfer Sales Order (as image of eCommerce Shopping Cart) to Invoice and then post the batch of Invoices. Batch origin is not a restriction - you can post native GP batches (where Batch business logic sits in Dynamics.dic dictionary file): GL, POP, SOP, AR, AP, US Payroll, Inventory, etc. Plus you can post third party or extended modules originated batches, such as in Project Accounting, Manufacturing, as well as batches in Dynamics GP ISV modules (WennSoft, Horizon, etc.). And on the top of this - you can post batches in multiple Dynamics GP companies from the same Posting Server
2.Advanced Auto Posting Scenario - Manufacturing. With native Dynamics GP logic in order to integrate Manufacturing Orders from external application you would either write Macro (in very simple case, where there is no decision making and user intervention is not required); or put extra button of MO screen, where you initiate import and then save and open all the screens up to the point of posting Manufacturing Order; or in luxury scenario you program Great Plains Dexterity customization to do the job with custom screens and dialogs. With Posting Server it is enabled in Integration Code window, where you can place Dex Sanscript code to open and save Manufacturing windows and even read data from external ODBC compliant data source: Oracle, MySQL, MS Access, Text file. Microsoft Dexterity Sanscript code could be very sophisticated, for example you can call DLL libraries based methods, or call SQL Stored Procedure (which in turn could be Cross-Platform)
3.How to get additional help? Please, call us 1-866-528-0577, 1-630-961-5918 or email us help@albaspectrum.com We would like to hear your case, if it is different from what we described above. We are comfortable in helping international customers, our consultants speak English, Spanish, Portuguese, Chinese, Russian, Arabic
