wordpressrobot.com » Batch

Ecommerce For Dynamics Gp Notes: Econnect Batch Posting

admin — Fri, 05 Mar 2010 00:41:58 +0000

Microsoft Dynamics GP is becoming very popular ecommerce ERP and accounting back office. This trend is probably related to success of eConnect SDK, especially for Dynamics GP 10.0 and 9.0 versions. eConnect allows you, being generic C#, VB.Net programmer with good SQL and XML skills to program Great Plains objects manipulation: Customer, Address, Sales Invoice, Customer Payment and other attributes of ecommerce shopping cart. eConnect, being coded in SQL Server Stored Procedures (they are encrypted, so you probably should not expect to trace SQL code for Great Plains business logic there). In this small publication we would like to share with you ecommerce coding experience and Dynamics GP automatic batch posting from eConnect application directly:1. Older versions of Great Plains Dynamics GP. If you are on GP 8.0, 7.5, 7.0, 6.0, 5.5, 5.0 or earlier versions, we recommend you to upgrade to Dynamics GP 10.0 as for this version eConnect is really advanced. If you do not have registration key, probably due to the fact of lapsing in Dynamics GP Great Plains annual maintenance program, consider deploying Sales Order Connector, or set of SQL stored procedures, created for ecommerce web developers of older Great Plains version to connect ecommerce shopping cart with GP Sales Order Processing module, please call us for details. If you are on Pervasive SQL or Ctree, your options are very limited, you can still try to program ODBC connection to Pervasive SQL 2000 database, but then you will have to reprogram the logic, which is in fact available in eConnect (if you migrate from Pervasive to Microsoft SQL Server and upgrade to new version GP 10.0)2. Automatic Batch Posting. Here we often hear from ecommerce programmers the question – why eConnect doesn’t have the tools and logic to post Great Plains SOP Batches (as well as post batches in other Great Plains modules). The answer is in GP architecture (it is pretty common, and you should expect similar restrictions in other ERP and MRP platforms). The concept of ERP business transactions flow suggests you to use three phases of transaction life: work, open and historical. eConnect allows you to create work transactions, in Great Plains these are newly created invoices or sales orders, placed in the batch and submitted for Great Plains user review and posting. In order to trigger Dynamics GP batch posting from eConnect application directly – you have to deploy Great Plains add-on – Alba Spectrum Posting Server3. Posting Server. It consumes one user license and deploys Dynamics GP Dexterity source code to trigger the same coded logic in Dexterity for batch posting. Autopost is targeted to eCommerce web programmers, plus it post virtually all types of Great Plains Batches: GL, Inventory, Payroll, AP, AR, SOP

Ecommerce For Dynamics Gp Notes: Econnect Batch Posting is a post from: wordpressrobot.com

Great Plains Automatic Batch Posting From Econnect Ecommerce Application

admin — Wed, 10 Feb 2010 00:40:56 +0000

Alba Spectrum Autoposting Server is good enabler for GP batch auto posting from eConnect integration application as well as if you are deploying SQL or PHP coding to integrate your eCommerce web site with Microsoft Dynamics GP Great Plains. Alba Spectrum is about to announce new version of Auto Posting Server release date with the list of new features. This publication is to describe general functionality of Posting Extension:

1.       Batch Posting. It is done via Great Plains Dexterity native code fragments call. Autpopost is Dex add-on. If you are programmer, what you need to do is to insert work transactions in the batch in GP (typically via eConnect, as it has encrypted stored procedures to create customers, vendors, SOP invoices, etc), and then place batch record into Autopost table – this will trigger batch posting process. Autopost checks table status every few seconds and if new record is found, batch posting process is initiated

2.       Batch Origin. If you are thinking from eCommerce perspective – you are probably about SOP Transactions batch. However batch origin might be of any core GP module: POP, AP, AR, GL, Payroll, Inventory, Invoicing, etc. If you need batch posting, originated in add-ons or ISV GP extensions, please check with us, as each GP customization partner makes its own way of batch posting scenario

3.       New Features. New Autopost release will include: email notification, posting error logging and automatic startup. Please check with us in two weeks from now as we plan to release detailed specs for new features

Great Plains Automatic Batch Posting From Econnect Ecommerce Application is a post from: wordpressrobot.com

Automatic Batch Posting in Great Plains Microsoft Dynamics Gp Overview

admin — Tue, 09 Feb 2010 00:43:29 +0000

If you are ecommerce developer and program web site integration with back office accounting system, Microsoft Dynamics GP, then likely you are deploying eConnect SDK software development to move placed orders and customer payments to GP Sales Order Processing module. eConnect does wonderful job – it creates or updates customer record, creates SOP batch and customer invoice with deposit in the batch created. So far everything is beautiful, now you need just as small step to accomplish your work, post the batch created right from your e-commerce application, and here you got surprised by understanding that eConnect doesn’t post batches, it doesn’t has this functionality. We would like to review Autoposting Server, designed and maintained by Alba Spectrum Dexterity development team

1.       GP Dexterity Source code involvement in the batch posting. Dynamics.DIC dictionary has native GP Dexterity functionality to post batch of various origin and in essence all the origins. However it is not obvious, even for Great Plains Dexterity programmer with decent experience in coding on how to design autopost and how to deploy native Dex posting logic. GP Autopost resolves this dilemma and all you need to do as programmer is to place batch record into custom batch posting status table

2.       Posting all the way automatic from your e-commerce website. In GP posting path is defined in posting settings. If you set GP to post SOP invoices all the way through AR module to GP General Ledger – complete automating will be achieved

3.       Third Party Add-Ons batch posting. Add-Ons, designed by GP ISV partners have their own ways to create and post batches within their satellite modules, however when transactions in the posting cycles will reach Great Plains, Dexterity posting process will take over and so there is high chance that Alba Spectrum Autopost will do the job. We encourage you to check with us

4.       Microsoft Dexterity Customizations. If you need customization design, support or upgrade, we are happy to help you with it through our Microsoft Dexterity Software Development Factory

Automatic Batch Posting in Great Plains Microsoft Dynamics Gp Overview is a post from: wordpressrobot.com

Great Plains Autopost: Programmable Batch Posting in Ecommerce Integration

admin — Tue, 02 Feb 2010 00:44:02 +0000

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

Great Plains Autopost: Programmable Batch Posting in Ecommerce Integration is a post from: wordpressrobot.com