One of the most popular modules for Dynamics GP ISV Dexterity add-ons, EDI, eCommerce, Sales Carts and Barcode scanner batch or real time upload, integrations with Microsoft Dynamics CRM, Microsoft Retail Management System (MS RMS) is Sales Order Processing module in Microsoft Dynamics GP (formerly GP was known as Great Plains Software Dynamics, eEnterprise and in late 1980 as its predecessor Great Plains Accounting for Windows, DOS and Mac).
Roughly 30% of the Dynamics GP modification,
integration and custom reporting requests from GP customers are related to SOP module, its programming in eConnect, Dexterity, Modifier with VBA, Integration Manager batch or real time integrations. In this small publication we would like to review SOP functionality, technology layers and customization, integration and reporting tools:
1. Brief excurse into SOP business logic. Here you have the options to have negotiation workflow, starting with Quotation, then move it to Sales Order and then to Sales Invoice. You can also have Sales Return and Back Order. SOP has several items fulfillment options - on the fly (referred as By Line Item), as separate fulfillment process by batch or via separate Fulfillment Order mechanism (Quotation doesn't participate in fulfillment process). Sales Order or Invoice could have Customer Deposit/Payment (typically used in eCommerce Shopping cart invoice for Credit Card Payments). SOP Document (Quote, Order, Invoice, etc.) can pull items from Inventory Control module as Sales Items, Kits, Services, Miscellaneous Charges, etc. Plus you can enable non inventory items (simply enter brief description into item id and continue in Description field on Sales Document line). SOP Documents flow could be controlled via Holds (Transferring, Posting, Fulfilling, Printing, etc.). Plus for advanced fulfillment you can setup Fulfillment workflow: Ready to Print Picking Ticket, Unconfirmed Pick, Confirm Pick/Ready to Pack, Unconfirmed Pack, Shipped, Ready to Print/Post. Inventor Items could be also serialized or lot numbered if required. This is just brief SOP logic review, so if you do not see you question answered, feel free to check with us
2. Technology Layers. SOP Transaction Entry form is coded in Dynamics GP Dexterity (proprietary software development tool with Sanscript programming language and data access technology). Table structure could be reviewed in Dynamics GP SDK (install it from GP CD#2), or via Dynamics GP->Tools->Resource Descriptions->Tables. To be sure that you are getting the right direction, please review first SOP10100 (Sales document work header table), then SOP10200 (Sales line work table). We recommend you to use table structure knowledge for reports building only (Crystal Reports, SSRS, Report Writer reports), if you are about to feed data into SOP tables, please consider Dynamics GP Integration Manager (which you could customize via VBA scripting, adding custom scripts to integration events, such as Before Integration, Before Document, Before Document Commit, etc), or via eConnect programming in Microsoft Visual Studio .Net C# or VB projects. eConnect was introduced for Great Plains version 7.0 as SDk for ecommerce programmers to open GP as back office ERP application for ecommerce integration. In our opinion eConnect came to its maturity in Dynamics GP 9.0 and 10.0 (current version, October 2009). If you are on earlier Great Plains Dynamics version: 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 4.0, 3.2, please consider upgrade to Dynamics GP 10.0 - check with your Microsoft Dynamics GP Partner on upgrade path and availability for your organization (if you do not know who is your Dynamics GP Reseller, feel free to call or email our office)
3. Special Considerations to Dynamics GP Integration Manager. In IM you can deploy such powerful mechanisms as Queries, based on Advanced ODBC, allowing you to base the query on Microsoft SQL Server (2008, 2005, 2000, 7.0) view, where SQL view could be cross platform, linking MS SQL Server Database to Oracle, Linux/PHP/MySQL, MS Access, Pervasive SQL, Ctree/Faircom, Foxpro, IBM DBII, and other non-Microsoft platforms, which are compliant to ODBC convention. We are comfortable to recommend Advanced ODBC in Electronic Document Interchange (EDI) integration to Sales Order Processing Orders or Invoices (or in Purchasing through EDI partners or vendors channels)
4. Special Considerations to Microsoft Dexterity extensions to Sales Order Processing. Dexterity is semi proprietary (meaning that it is not feasible to force your internal IT programmers to begin coding in Dexterity over night, over week, over month or in short term perspective, as Dex requires year long extensive learning curve) and it is not recommended for in-house programming. However, if you need SOP Document interface modified Dexterity might be optional tool, as it is naturally integrates into GP Security realm and it looks as native GP interface (you should grant user, who is supposed to use Dex modification so called Dynamics GP Alternative Forms) 5. Modifier with VBA. This is another option to modify SOP Entry form (you should have customization site enabler license to have access to VBA modifications). Modifier allows you to place new buttons and editable fields on existing GP forms and VBA scripts could animate these fields. In order to manipulate existing GP tables from modifier fields, consider traditional ADO connection to MS SQL Server database
6. How to get help? Please, feel free to call us: 1-866-528-0577, outside of USA: 1-630-961-5918 or email us help@albaspectrum.com We are very technical and real Dynamics GP Dexterity, SAP Business One SDK and Microsoft CRM programming gurus. We have Great Plains Software Development Factory and could support unlimited Dynamics GP Customization and Programming needs. Plus we speak English, Chinese, Spanish, Portuguese, Russian, and not only as native speaking sales folks, but as real technical consultants. If you prefer skype: albaspectrum
