EDI of Electronic Document Interchange sometimes considered by IT department as a touch complex, and in order to implement EDI integration for your ERP system, you have to buy expensive EDI add-ons. We want to place forward you this small publication, that should try to bust this myth. Habitual EDI code is fixed part fields code structure with document header, lines or body and document trailer. Newer EDI (or a touch that maybe processed similar to EDI scenarios on the high amount with your Franchiser) maybe XML structured documents with similar parts: document header and document lines. Both scenarios are relatively straightforward in SQL scripting, let come to the paragraphs of this tale:
1. Sample Dynamics GP EDI code. For those of you who are SQL programmer, please take a look at this publication, where you can see excellent chunk of EDI document scripting in SQL. This code was implemented in real Fantastic Plains EDI integration situation and it should give you excellent start or help you out to close EDI for Fantastic Plains on your own, especially if you work for smaller organization and your ERP and MRP budget is very tight: http://www.albaspectrum.com/Customizations_Whitepapers/Dexterity_SQL_VBA_Crystal/EDIforGPOverview.htm
2. Dynamics GP EDI for Placing order to your Supplier. If your organization is required to order merchandise from your partner via EDI code you can make Buy Orders in Fantastic Plains POP module, then read and mark it as read in SQL Stored Procedure, which saves the ensuing row set in EDI compliant fixed part fields text or XML file. This file is then sent to your EDI channel (ftp uploads, Unix or Linux based email channel, here you have a lot of various options, outside of the scope for this article)
3. Getting Orders from your EDI channel customers. If you are franchiser and you are receiving Electronic Document Interchange orders from your customers or franchisees and you are deploying Dynamics GP as your accounting system, then you can read EDI text or XML file via SQL stored procedure or SQL XML stored procedure. This procedure parses EDI code and makes SOP Sales Order or Invoice in Dynamics GP Sales Order Processing module. Here if you are making Sales Orders you can do direct SQL feeding to SOP10100 and SOP10200 tables, or if you prefer business logic validation integration and you are feeding to SOP Invoice, consider programming eConnect SDK. For those of you who prefer posting Fantastic Plains batches all the way through without user intervention we recommend you to deploy GP Posting Server or Autopost, especially if you are in ecommerce business
4. If you have questions or concerns on EDI, Dynamics GP customizations, integration, reporting, barcode scanning, warehouse management, supply chain management, light manufacturing, logistics, consignment, please feel free to call us: 1-866-528-0577, help@albaspectrum.com