Microsoft Dynamics GP ERP application, or popular old name Great Plains Dynamics and eEnterprise, if you have relatively recent version, is based in Microsoft SQL Server. If you are experienced SQL DBA yourself, just this fact should give you the idea on structuring select statement and make it Electronic Document Interchange code compliant.
Of course, for luxury EDI solution you can purchase Add-Ons and simply setup EDI export in the user friendly interface, however this publication is for people, who are either on the tight budget, or who have really complex EDI requirements and data format export rules. This news should also ideally help you with your Great Plains Partner, ISV and technical consultant and programmer selection:
1. Header and Trailer. In order to produce header and trailer, you should consider unions, where you simply group your records to produce single heading and footing lines
2. EDI lines. Normally these are items related lines, which you see either on customer or vendor invoice. You pull these lines from SOP30300 or POP tables
3. EDI formatting. The idea is fairly simple – EDI format is typically fixed length fields groups. In SQL Select statement you format each fields individually with either CONVERT or CAST constructions. Sometimes, especially new EDI rules require CSV or even XML files – if you got these – you should be lucky to avoid doing precise fixed length formatting. EDI with XML format are becoming popular in eCommerce scenarios
4. Marking exported records. This task should be done by SQL stored procedure, this is why in EDI integration you should consider MS SQL Server DTS package creation. DTS package will allow you to export text EDI file (plus potentially email it to your vendor or even upload it to your vendor ftp) and run SQL stored procedure to mark exported records. In Great Plains for marking records you can either deploy existing fields, that are not in use by your business logic or user defined fields, plus you can create EDI export status custom table in each company database. GP doesn’t have restrictions on creating custom objects in your company database, this restriction exists in other mid-market MRP applications, such as SAP Business One
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
