DCS' many years of in-depth experience with the Dynamics family of accounting products (Including Great Plains™, Axapta™, and Solomon™) shows that EDI configuration is straightforward, but not trivial. Fortunately, the interfaces required for integration are improving. You can now choose from eBRIDGEsoftware, True Commerce, and vSync gateways. We can help you and your customers properly configure EDI using these gateways or provide a custom interface. Additionally, for EDI data not imported into Dynamics, DCS can map it to a Microsoft SQL Server™ table from which you can build an application. We have experience integrating to:

We can help you determine if you can integrate your existing EDI system at a reasonable cost and avoid many of the pitfalls of an integration project.

Here’s how automated EDI works:

• Customer Orders automatically enter the Dynamics Sales Order Module, where they are suspended pending Customer Service approval. The most common corrections before approval are to part-numbers, prices and ship-to addresses.
• Orders that can be automated include INbound Purchase Orders (ANSI X12 850 or EDIFACT ORDERS), Inbound Purchase Order Changes (860 or ORDCHG), INbound Releases (830 or DELFOR), and Shipment Schedules (862 or DELJIT). This means all methods of receiving customer orders come to the same point for Customer Service approval (Your planning schedules are not over-written).
• Shipment Notices (ASN, 856 or DESADV) flow out automatically when the order is closed. Flags may be set to ensure data that could cause a chargeback must be sent.
• Invoices (810 or INVOIC) are also automatically sent.
• Other EDI documents such as price sheets and catalogs can be integrated in a matter of days.
• XML is also possible, but not commonly used by major corporations.

To keep cost low, integration with Dynamics GP™ or AX™ best occurs using a gateway from eBridge Software, vSync, or True Commerce. These incorporate the Functoids, set alerts, and provide ODBC, positional, or delimited interfaces for each Transaction Set and direction. Another challenge is activating the several dozen correct fields among the hundreds available for each document. The interface structure can be complex and difficult to tackle, but process automation is achieved. This means your connection to Microsoft Great Plains is completely integrated: your Customer Service, Purchasing, and Shipping Department will not need access your EDI system.

Dynamics SL™ EDI integration occurs using Edge™, a different EDI system. The processes of EDI integration and operation with Solomon™ are similar. DCS has experience with Edge since its creation in the late 1980's and can help you with Edge EDI challenges.

Automated EDI

EDI too often is an afterthought during the Dynamics conversion, or comes up suddenly as an “on demand” project requested by a key customer that needs to be completed yesterday. In both scenarios you are forced to piece together a workable solution. This is something that you must do well and ensure that the best business practices are being followed, since future development is built upon this foundation.

We work with the three components of reliable and economical EDI:

Here are the necessary deliverables you must provide:

• Identify key resources and opportunities in your environment.
• Develop the project plan with all of its appropriate components (including training).
• Set up your development and test EDI systems.

• Create a comprehensive map for each key Transaction Set, e.g. INbound Purchase Order (850).
• Customize the comprehensive map for each customer.
• Set up and test communications between the EDI system and the interface.
• Set up data transmission testing: setting AS2 or FTP over your VPN to your customers test mailbox. You can use your existing AS2 utility. This is done while working closely with the firewall manager.
• Archive off the old EDI system and data.

• Set up the tables required to receive/send (Data File Structure, Partner Cross-References, Partner Profiles, Code Conversion, etc.). User exits can be written in VB or C#.
• Set up the document types and processing rules. Axapta v. 4.x (or newer) users can use the Application Interface Files.
• Check to ensure all customer locations and their part numbers are loaded.
• Set the inbound control record and record keys (1-100). Many are re-usable.
• Setting Dynamics SL^TM (formerly Soloman) occurs using the Edge Developer^TM EDI module.

• Install and test the finished maps and setup.
• Train users (Customer Service, Accounts Receivable, and more).
• Train I.T. (daily operations and mapping).
• Have help available for support if needed.

These steps will achieve a high level of process automation similar to that of large ERP systems like SAP or JD Edwards. Any company with high transaction levels can achieve good savings from automation of tedious data entry.

Conclusion

You will enjoy a wider fulfillment window when the data entry step is eliminated because Customer Service has more time to check orders. You will also avoid costly, last minute changes and expedited shipments.

• Most of the US companies requiring X12, EDIFACT, or GS1 (standardized XML) are well known to us.
• Popular transaction sets such as Inbound PO's (850), Outbound ASN's (856), Outbound Invoices (810), Inbound Releases (830), and Outbound PO Acknowledgements (855) have been implemented at many of our customers.
• Data transmission using EDI INT AS2 (HTTPS in batch mode) reduce cost by elimination of Value Added Networks. DCS can also help you use your existing AS2 utility.
• Finally, DCS has helped many companies convert their EDI from lesser MRP systems to Dynamics.

Since your business is unique, your time-tested business processes must be carefully adapted to the different requirements of your large customers. Technically, this means that developing the EDI maps is straight forward but not trivial. Having DCS set the first few customers and set up the data transmission will lower the cost of implementation and hastens payback. Since 2006 DCS has assisted over 10 Great Plains users with EDI upgrades.

DCS can help build your EDI foundation or add more process automation using our time-proven DCS NEXT LEVEL™ Conversion service. DCS is eager to work with your Dynamics provider. Our experience is with the EDI/E-C Gateway: we do not seek non-EDI work. Your first step is easy, email DCS for your free assessment.