Ecommerce Posting Solution for Microsoft Great Plains Dynamics GP

If you are eCommerce developer, you probably deploy Great Plains eConnect to incorporate your constituted ecommerce web land site with general practitioner ERP back office. eConnect is great tool, it lets you to make or update client records, including addresses, make gross sales order or bill in Gross Sales Order Processing (SOP) module. eConnect concern logic is realized as a set of stored processes behind the scenes, these processes are encrypted, so you can not directly modify them. You may soon recognize that eConnect lets you to make so-called work transactions, but it doesn't have got posting capabilities. Posting is left to general practitioner operators, who supposed to verify gross sales bill first and then post it in the batch. It is often the lawsuit in eCommerce, that you desire posting to be done automatic in GP, initiated by your e-commerce application logic. In order to widen eConnect with autoposting, you necessitate Alba Spectrum Posting Server:

• Native Microsoft Dexterity posting engine. If you are or would be the old-good-days Microsoft Dexterity developer, you would cognize that you can name Dexterity processes and functions, especially if you reexamine Great Plains Dexterity SDK and analyse DYNAMIC.DIC with beginning codification (not available to general development pool). Posting Waiter phone calls this dex logic and have got Dexterity station "approved" by posting waiter batches

• Approved Batches Table. Yes, you necessitate to put the record for the "approved" batch into this usage tabular array and posting waiter will originate posting from there. It check ups on tabular array position every few seconds, so posting is happening in existent time

• Batches Types. When we are talking about ecommerce programming, then more than likely it is sop module: SOP10100 and SOP10200 tables, where sop bill heading and lines are stored and where eConnect topographic points the work records. However posting waiter is not limited to sop only. It works with all known general practitioner faculties (you may anticipate issues with so-called satellites or 3rd political party modules, such as as Mekorma, Wennsoft, etc.)

• SQL Waiter Shop Procs alternative. This option attack may look consecutive forward, however general practitioner posting minutes flowing is complex and it includes multiple scenarios: different point types, different terms levels, batch or series figure tracking, sophisticated stock list allotment procedure to call a few complications and trying to deter you to plunge into stored processes coding

Business Portal 3.0 for Microsoft Dynamics GP Great Plains - Overview for Consultant

Web interface should, as we believe in the future replace "fat client" modules, such as GL, SOP, POP, RM, PM, and others currently written in Microsoft Dexterity (former Great Plains Dexterity). Microsoft Dynamics GP Business Portal version 3.0 maybe considered as a bit complicated in its installation, customization and deployment. All ERP applications are moving to web interface and thin client technology and this is just the matter of time, when we will enjoy worldwide secured access to our MRP functionality. In this small article we would like to stress some challenges of current BP:

• Back Office ERP restrictions. If you look at Microsoft Dynamics GP, you will realize that US Payroll and HR modules have different terminology on pay codes/time codes. Business Portal HR Management Self Service Suite has to conform to these different approaches and alter its logic accordingly (if you have US Payroll – pay codes, if you have only HR – time codes). This is only one example, we have more, but the article genre restrictions do not allow us to go deeper into the problem

• Extensions Philosophy. At this time, we believe that MBS has to accommodate BP to existing MS Dexterity based modules in GP backoffice. Good example is Requisition Management – this BP module posts its transactions to GP Purchase Order Processing (honoring commitments business logic). This is probably natural way of evolution – Project Green, later renamed into Microsoft Dynamics project could not jump ahead of ERP market and abolish all four ERP applications: Great Plains, Solomon, Axapta, Navision. Instead – what we see is more likely is evolution of mentioned ERP platforms to unified MS Office and Outlook interface, while the MRP core remains original

• Installation Battle. Business Portal deploys MS Sharepoint, eConnect, and as you probably realized it requires you to enter reg key (especially if you are MBS VAR and plan to demo Business Portal in Fabrikam to your prospects)

• Uninstall Dilemma. If you by whatever reason decided to wipe BP out and install it fresh – this is where you decide how deep cleaning up you would need. Our experience indicates the following: uninstall BP, then eConnect, Sharepoint, Sharepoint SQL or SQL Express, reboot computer and start over with BP reinstallation