JD Edwards EDI Headaches?
DCS Can Help!

DCS has in-depth experience integrating EDI with the JD Edwards (JDE) EnterpriseOne^TM, World^TM, and PeopleSoft

• EnterpriseOne^TM version 8 has new interface formats that require re-mapping. This is also the time to add new fields (elements) and connect to public warehouses, truckers, and parcel carriers.
• DCS also has in-depth experience with R47 programs and writing directly to F47 tables, including activity rules and UDCs.

Overview

Integration with JDE is a significant task. Properly integrating files can be complex and difficult to tackle. For example, user exits, activity rules, or UDC scripts are frequently used when mapping to/from an intermediate, positional (“flat”) file or ODBC mapping.

EDI too often is an afterthought during the upgrade or suddenly comes up 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 to ensure best business practices are being followed, since futere development is built on this foundation.

Here are the necessary deliverables you must provide:

Planning

• 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.

EDI Development

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

JDE Development

• Set up the document types and processing rules.
• Check the address book to ensure all customer locations and their part numbers have been added.
• Set up the F47 tables required to receive/send (UDC codes, Partner Cross-References, Partner Profiles, etc.).

Implementation

• 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 production down support and system monitoring.

A Note on Fusion's Impact on EDI

Since 2000 Oracle has purchased several application software vendors, including JD Edwards. Now, Oracle has announced a migration path to a new platform: Fusion^TM, that will be released in 2008. If you choose to migrate, it will be difficult because it is a completely redesigned suite and will rely upon Business Process Execution Language for Web Services (BPEL4WS).

If you use JD Edwards or PeopleSoft, you should consider a migration plan. Your choices are:
1. Migrate now to gain the greatest process automation savings.
2. Defer migration until the cost of “hot” talent begins to decline and bugs are squashed.
3. Do nothing – “If it ain’t broke don’t fix it.” You can wait many years until a change is necessary.

The EDI perspective is clear: the EDI gateways of Oracle, PeopleSoft, and JD Edwards are robust and reliable. The new gateway is unknown, but hopefully not troublesome. The key task is to maintain undisturbed production mode EDI during the Fusion conversion.

Conclusion

Let DCS help you build your EDI foundation or add more process automation. Since setting up JD Edwards EDI is straight forward but not trivial, we recommend DCS Grow™ development service. Your mapping will be thorough, quick, and economical due to our many years of JDE EDI experience. Having DCS develop the first few Trading Partners and communication parameters lowers the cost of implementation and hastens payback.

• Most of the US companies requiring X12 or EDIFACT EDI are well known to us.
• Popular EDI 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. You may also consider 3PL EDI (94x series) and Transportation EDI (21x series).
• DCS experience extends to the add-ons for JD Edwards created by the above EDI systems.
• Connections using EDI INT AS2 or FTP over a VPN reduce cost by elimination of pricey Value Added Networks.
• Finally, DCS has helped many companies convert their EDI from lesser MRP systems to JD Edwards (JDE).

With experienced professionals, you can avoid common pitfalls and headaches when implementing EDI with your E1 World or Enterprise application. Your first step is easy, email DCS for your Free Assessment. For further reading, check out a success story regarding a JDE EDI Integration.