Dynamics GP accomplice Newsflash: EDI in good Plains

Electronic Document Interchange, or EDI, is often understood as something fairly mysterious and hard in talent in ERP system. Lets declare scenarios and how they could be realized without third party EDI add-on, just in regular great Plains, assuming that you have some familiarity like SQL Server and SQL prefer assertion and GP Integration Manager.

We will rule both situations subsequent to you are customer andyou are replenishing your inventory via EDI long-suffering vendors channel as wellas following you are the vendor to whom purchase Order is placed through EDIchannel:

1. Inventoryrestocking via EDI channel. Here weassume that you are large organization, and you have Dynamics GP as your headquartersERP system. In GP purchase OrderProcessing module, entertain concern purchase Order and save it. after that gate Microsoft SQL Server ManagementStudio 2005 and additional query. construct yournew formatted pick support to extract and form the data from the followingtables: POP10100 (Purchase Order HeaderWork) and POP10110 (Purchase Order lineage Work).Formatted prefer assertion means, that each sports ground you pick when eitherCAST or CONVERT operators. EDI filetypically is saved as complete length text file past header, lines and trailer,you keep your formatted pick support as text file. We recommend you to setup SQL DTS package,which will select new purchase orders, mark them as exported to EDI, save newEDI text file and distribute this file to EDI recipients

2. ReceivingEDI orders from your customer. Here isreverse situation, like you are the vendor in EDI channel for largeorganization. For you EDI demand shouldtranslate into Dynamics GP Sales Order or Invoice. This scenario is slightly more profound and wewill picture you booming scenario.You deploy either good Plains Integration official or eConnect customapplication (which does the similar job but in real time, if this is your goal). In IM you make additional Source as enlightened ODBCand you base this source on MS SQL Server custom View. This custom view reads supplementary EDI file, parsesit to SOP Document Header and Document Lines, later in IM destination you map itto SOP document customer Order, Invoice or Quote is this is your scenario. eConnect programming, if you are usingDynamics GP relation 10.0, you are probably up to date that IM is in process of beingrewritten in eConnect. So, this meansthat you forward-looking IM integration should be lovely thesame to custom eConnectprogramming. At this time, of course,eConnect gives you solution manage exceeding Integration timing and allows you totrigger integration on demand or on issue triggering

3. EDIAdd-Ons. since you hop there, pleasetry to analyze release approach, we tried it several grow old and it works successfullyfor multiple GP customers. If you thinkyou got special case, in our opinion its uniqueness often falls into the needto translate Vendor Item Names from your Catalogue Items, or same smalltranslations and tweaks, in our opinion, it is not the defense to pay tall pricefor tall end EDI add-on

---