EDI of Electronic Document Interchange sometimes considered by IT department as something complex, and in order to implement EDI integration for your ERP system, you have to purchase expensive EDI add-ons. We would like to offer you this small publication, that should try to bust this myth.
Traditional EDI code is fixed length fields code structure with document header, lines or body and document trailer. Newer EDI (or something that maybe processed similar to EDI scenarios on the high level 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 story:
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 good chunk of EDI document scripting in SQL. This code was implemented in real Great Plains EDI integration situation and it should give you good start or help you out to finish EDI for Great 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 create Purchase Orders in Great Plains POP module, then read and mark it as read in SQL Stored Procedure, which saves the resulting row set in EDI compliant fixed length 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 creates SOP Sales Order or Invoice in Dynamics GP Sales Order Processing module. Here if you are creating 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 Great 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
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
