Optimize your business processes with Electronic Data Interchange EDI solutions—streamline data exchange, improve accuracy, and enhance efficiency.

Tag Archive for: EDI

The Definitive Checklist For Oracle JDE and EDI Integration Projects

This post was updated to reflect current trends and information.

Article written by Pierre Namroud, EDI Integration Specialist & Business Consultant

I had the pleasure of attending Collaborate17, a Technology and Applications Forum for the Oracle community. This opportunity brought together Oracle professionals, integrators, project managers and IT experts from around the world, who all work in different spaces of integration. It was such a great experience speaking with so many Oracle experts and attending educational sessions.

One of the main points of discussion during the various speaking engagements was on the challenges that professionals were facing when it came to integration projects involving EDI (Electronic Data Interchange) as well as eCommerce data to JDE (JD Edwards). The opinions were unanimous in the sense that Oracle still has more work to be done in order to strengthen and simplify integration with legacy EDI protocols and build simpler integration flows for protocols such as X12, EDIFACT, Rosetta Net, etc.

I’m writing this article, in order to share my own expertise as a data and EDI integrator, where I had the chance to be involved in several eCommerce and EDI integration projects with Oracle JDE. Hopefully it will help inform other Oracle professionals looking to overcome some of these integration challenges.

Challenges currently being faced by Oracle JDE professionals

There are many challenges that any JDE professional might see when it comes to data and systems integration with Oracle ERP software in general, whether for on-premises or cloud systems. [As a side note, Oracle’s cloud systems have their own specific limitations that I recently learned about during one of the Collaborate Sessions].

Below, I have listed some of the most common challenges that not only have I experienced in my own projects with Oracle customers but that others have expressed during the Collaborate conference;

  • Oracle’s JDE does not have a seamless built-in integration with all EDI X12 documents “out of the box”.
  • The current integration process for EDI X12, EDIFACT, HL7 or any other data format now happens by writing into transition tables (or Z files) and then triggering a business function to process those incoming data.
  • Even though Oracle’s JDE system supports business functions, some older versions do not support new API functions, which can cause some headaches.

    Looking to integrate your EDI or eCommerce processes with Oracle JDE enterprise one, look no further, since we have the best integration option where we turn your Oracle JDE system into a modern REST API, that receives https requests and acts accordingly. Learn More>

Integration Project Checklist

Before starting an integration project with your Oracle JDE system, I recommend that you go through the following list of questions. This way, you’ll be able to make the best decisions to move forward with development efforts as efficiently as possible.

  • Who are the Business or Trading Partners you want to exchange electronic data with?
  • Which documents (or types of data) are you requested to exchange from your Business Partners? In normal circumstances, they’ll provide you with the necessary documentation and specifications as a road map and for compliance reasons.
  • The exchanged data will be sent under what format or standard/version? (X12, EDIFACT, RosettaNet, XML, custom format…?)
  • What is the protocol of communication used to send the data back and forth between you and your Business Partner? Is it point-to-point, such as AS2 or sFTP?
  • Is a VAN required in order to transport the data?
  • Do you have the necessary expertise to select the appropriate certified communication software (for first time project implementation)?
  • Do you have the necessary expertise in your development team to decrypt and understand the terminologies of legacy EDI formats?
  • Has your team ever done an EDI integration project, that includes a full certification process?
  • How many partners will you be exchanging with? The more partners you have, the more complex the project can become.
  • Check the specs of all of your partners (when possible) to verify the differences in their requirements. It is well known in the EDI integration world that there can be many distinctions and exceptions found per Business Partner and per document. Every EDI project can be unique.
  • What is the lead-time to complete the certification and testing phase with your business partner before going live?
  • What is the volume of exceptions that your development team can currently handle in the project in order to be on time and within budget?
  • Do you have the necessary integration tools to simplify the EDI syntax in order to work with one format regardless of the format of the data you receive from different sources?
  • Is your team coding directly in Oracle JDE native framework, or are you using any efficient integration tool available today?
  • Will you be doing end-to-end integration using Z tables of Oracle JDE, or you are going to use API (or business functions) of JDE?

Recommendations for a Successful Integration Project

As you might have noticed, data integration projects involving legacy EDI protocols or custom data format exchange are not simple. They are projects that need a lot of expertise and experience in data communication and transportation, data mapping and systems integration into Oracle’s JDE system.

Moreover, at most enterprises that we’ve completed EDI integration projects for, it was evident how stretched and overwhelmed the internal JDE development team was in their own day-to-day operations, support and maintenance of the application and were incapable of learning new standards to respect the strict timeline given by Trading Partners. In these cases, they looked for help from an outside Service Provider, such as EDI2XML.

My recommendations for such projects are as follows:

  • Outsource the EDI part of the project to a reliable Service Provider, who is highly focused on service availability and quality, since EDI is quite sensitive. This will allow your team to continue working on their daily tasks and keep doing what they do best (JDE support and maintenance, for example). This way, you’ll have a simplified and streamlined EDI integration process; you build one tunnel between your EDI provider, where they deal with the exceptions, and your own process.
  • In case your company policy requires you to deploy the EDI integration solution on-premises, make sure to use an efficient EDI conversion tool such as our EDI2XML technology that has the capability to turn the EDI documents from X12 format to a human readable XML format, for example.
  • Equip your team with the right tools for data integration such as Magic xpi, which we have been using for many years in our data and systems integration projects. Leveraging such technologies allowed us to integrate anything-to-anything (JDE to SAP, SAP to Salesforce, EDI to any system as examples).

I sure hope I was able to expose the most common EDI integration challenges and complexities and help you to overcome these obstacles with the above checklist and recommendations.

If you are interested in learning more about this topic or any other issue related to EDI integration projects, please click on the image below and I will be more than happy to contact you personally for a FREE consultation.

 

Free consultation ecommerce JDE integration

 

4 Challenges of EDI and Drop-Ship in eCommerce


This post was updated to reflect current trends and information.

EDI integration projects


The term “drop-ship” has been used quite a lot in recent years by retailers and manufacturers alike. This supply chain management method looks to be gaining in popularity going into 2019 and will likely be in high demand for years to come as well.

Let me first explain the meaning of drop shipping and how it has become so popular…

What is Drop Shipping?

“Drop-ship” is a fulfillment method where a merchant does not carry any inventory on hand. Instead they sell products to consumers via an online store (eCommerce), send the customers’ orders to the manufacturer and have the manufacturer ship the goods directly to the customer. The customer will never know the difference since they pay the merchant and receive their goods in a box with the merchant’s labels. This method eliminates the need for the merchant to handle the goods.

The Rise of Drop-Ship Popularity

Due to the fast evolution of eCommerce, coupled with the continuous challenges that businesses face to reduce costs and increase profitability, the drop-ship method is in high in demand by major retailers. You’ll find that eCommerce giants like Amazon.com, Costco.com, Cabelas.com, Sears.com and others, are increasing the pressure on their supply chain to adopt the drop-ship concept. Of course, they also require their business partners to comply with their EDI requirements and specs for a full automation of the entire sales cycle.

The Complexity behind Drop Shipping

If we take a behind-the-scenes look at drop shipping from 2 perspectives, from the eCommerce retailer, like Amazon or Cabela’s, and from the manufacturer of goods, we’ll find the simplicities and complexities behind each process.

From the perspective of the eCommerce retailer, the drop-ship method allows them to eliminate the need to carry any inventory and to ship their goods. Their process is rather simple, profitable and quick. All they need to do is sell products online and ensure that their partnered manufacturers are EDI and drop-ship ready. Once they sell products from their eCommerce site, they will send the orders via EDI to their manufacturer and the manufacturer takes it from there.

From the perspective of the manufacturer, we’ll find some of the complexities. However, if they are setup correctly from the get-go, then it becomes rather simple and quick. In this case, the drop-shipper (manufacturer or distributer) is entirely in charge of the fulfillment of all incoming eCommerce orders (from the retailer). They need to process the sale all the while complying with the retailer’s business specifications such as EDI. Let’s go over the top 4 challenges a manufacturer must overcome during a drop-ship EDI implementation;

Top 4 Challenges the Drop-Shipper Might Face

If you are a manufacturer and have recently partnered with an eCommerce retailer to sell your products, then you might already know that they will require you to drop ship and automate your sales process through EDI integration. I have listed below the top 4 challenges you might face as a drop shipper;

1.    Ability to submit accurate inventory feed (846) to the eCommerce retailer

When starting a new business relationship with an eCommerce retailer based on the drop-ship method, the first step will be to feed inventory & per-item stock statuses to the retailer in a timely manner. This inventory inquiry/advice document is called EDI 846. Major retailers such as Amazon.com, Cabelas.com, Costco.com and Wal-Mart.com require their Trading Partners to send them an 846 document at least twice a day so that their online store can properly show only available products, based on inventory available to ship. Most of the time, companies either don’t have an accurate inventory system or their stock status is not properly maintained, which can be a great challenge to overcome. Even if companies have accurate inventory statuses, many of their management software systems, even reputable and expensive systems such as JDE, do not have built-in capabilities to send the 846-inventory status in X12 format, as per the requirements of the retailers.

2.    Ability to receive and process EDI orders (850)

Another challenge comes in the form of receiving EDI purchase orders (document 850). Many companies struggle with the capability to receive EDI orders, process them and integrate them quickly into their management system before it is sent to the pick/pack/ship process down the line in the supply chain. Most software systems are still missing this integration capability and require end users to manually key-in orders received in EDI x12 format, to then be able to process and ship. This is a great challenge for many manufacturing and distribution businesses. Dealing with eCommerce Stores, orders are continuously coming in, at all hours, in high volumes. The client (retailer) typically expects the manufacturers to ship within 24 to 48 hours (at the latest!). Moreover, eCommerce retailers are expecting to receive a P/O acknowledgment (document 855) via EDI. Therefore, it’s extremely critical that the drop shipper is equipped with a fully integrated software solution where EDI orders can automatically come through in real-time, so that they are quickly processed.

3.    Ability to fulfill orders within a very short period of time

As previously mentioned, eCommerce retailers expect their partners to ship goods to the end-consumer within a very short time frame (24 to 48 hours). They expect them to package the products, print customized picking/packing slips to send with the goods and complete the shipping process in a very quick manner. In case of failure to comply, there is a risk the vendor will be eliminated from the program. At the logistics level, an important challenge is to have a management system and required resources to process orders, pick, pack and ship in the required time frame. Efficiency in this case is imperative since time is money.

4.    Ability to electronically submit Ship Notices (856) & Invoices (810)

Two other EDI x12 documents are sent out to the eCommerce retailer by the drop shipper; the Advance Ship Notice or ASN (document 856) and of course an invoice (document 810). Most companies don’t currently have the capability to turn those business documents into an x12 EDI format and submit to the Trading Partner, straight from their management system.

Overcoming Drop-Ship Challenges

Our team’s experience with EDI drop-ship has allowed us to overcome the above challenges in an efficient and timely manner. Since every project varies, it’s important to do the following;

  • Surround yourself with experts in EDI who have the experience in dealing with drop-ship projects. It’s important to have enough knowledge and expertise in these methods prior to beginning any EDI drop-ship project. It’s important to get organized internally before any major project.
  • Ask an EDI Provider, who offers flexible and affordable EDI & IT services, to help you streamline your processes and advise you on best practices.
  • Opt for a full EDI integration with your current management software solution, if possible. Of course, such an option is not always possible or provided by your Software provider but if it is, it’s our recommendation to go ahead with this since it will eliminate chargebacks and increase efficiency in your EDI projects so you are best capable of complying with your Trading Partners’ demands. Don’t forget, partner demands and specs can change at any moment. It’s best to ensure you can handle changes at a moment’s notice. (Flexibility is the way to go!)

If you’re looking to complete an EDI Drop-Ship project, contact us today. We’ve got the experts and the EDI2XML service to get you drop-ship ready. Contact us today for your FREE consultation to evaluate your EDI project.

Free EDI consultation

 

EDI, XML or Web Services; what’s Best for eCommerce Integration

This post was updated to reflect current trends and information.



eCommerce platforms have been largely used by small and mid-sized enterprises, to sell their products and services to the booming consumer market (B2C) on the internet. Amazon and eBay for example, are among the most popular eCommerce platforms; for ease of operations and integration they offer different ways to exchange data between the trading partner and the platform. As an example, Amazon offers EDI integration capability, or Web service calls to exchange data or simple XML transactions. The most frequently asked question, by business owners, is: what is the best option to have a quick integration at a minimal cost with a maximum return on investment?

In this post I will explain the different integration mechanisms and share my opinion on how to decide which way to go. As a complementary article to this post, I invite you to read my previous post entitled Tips to Empower your eCommerce with great Supply Chain through EDI Integration to get more detailed advise about eCommerce and EDI integration to be able to build a strong SCM channel.

Let me start by quickly defining each of the above technical terms:

EDI

EDI is the oldest protocol used to exchange data between business partners. It has been standardized and heavily used for decades. It is very well ingrained in the manufacturing and retail verticals. Data in EDI format has a pre-defined format and structure. It is transmitted using different types of secured communication protocols (i.e. VAN, AS2, FTP, sFTP…).

Useful reading: What is EDI? 

 

XML

As defined by the W3Schools website , XML is a markup language much like HTML, meant to carry data, not to display data. It is designed to be self-descriptive, where users define their own XML tags to describe data. XML is a W3C recommendation. XML was created to structure, store, and transport information, in contrast to HTML that is meant only to display data in a web browser.

Since XML has been developed, it quickly became a popular means to transfer very well structured data between business partners. Thanks to its ease of use, and its descriptive aspect of the XML data format, it has been the preferred choice of many software vendors and applications used in integration projects.

Web services

Wikipedia defines a Web service as “a method of communication between two electronic devices over a network. It is a software function provided at a network address over the web with the service always on as in the concept of utility computing”.

Web services are designed to support machine-to-machine interaction over a network, using different protocols, by sending and receiving “messages” using HTTP and XML in addition to other web-related standards.

Now for the technical use and interpretation of Web Services, it is simply triggering the execution of a program or function remotely, using the internet, and returning the result to the caller. In addition, Web services use XML in different formats to send structured data back and forth. The advantage of Web services is that it uses the internet as a communication and transport protocol, in addition to the XML structured language to format the data transmitted back and forth.

If you want to know more about  different types of web services such as SOAP and REST and why EDI developers prefer use RESTful services, read our new article: Seamless EDI implementation through Web Services

Useful reading: What is EDI2XML web Service?

 

eCommerce integration

eCommerce integration means the process of sending data from the eCommerce platform to an external system or platform, and receiving data into the eCommerce platform using an automated process. Integrating your ERP system or a company’s CRM system with the eCommerce platform enables the necessary data to be sent in both directions so that both systems can interact in a seamless way, without the need for human intervention. This will improve efficiency and enterprise capabilities to serve clients faster.

Useful reading: Tips to Empower your eCommerce with great Supply Chain through EDI Integration

How to select an integration method and what is the best option

In my opinion, there is no single rule when selecting an integration method. Any business owner, executive or integration consultant should ask the following technical questions before selecting a technology and protocol to integrate their eCommerce platform with their own system:

  • What’s the expertise of my integration team?
  • Are they familiar with EDI format and protocols as well as its business flow?
  • Are they more familiar with XML and web services?
  • What are the additional technical advantages that the enterprise would gain by selecting one versus the other?
  • Are these advantages important issues for our business?
  • What are the add-on costs for both options?

Basically, the decision comes down to evaluating the level of expertise of the integration team and their zone of technical comfort. From a technical perspective, there isn’t a perfect option. Of course, the business aspect of the decision is a major factor and sometimes, business reasons might outweigh technical reasons.

If you need more information or would like to discuss your eCommerce integration needs, I will be more than happy to provide a free 1-hour consultation.

EDI Web Service for edi integration
/2 Comments

How to solve Shopify eCommerce integration with EDI

,


This post was updated to reflect current trends and information.

 

ECommerce (or online retail) has been a growing trend over the last few years. Due to this, business partners, retailers and suppliers have been transforming their flows and processes in order to better serve today’s well-connected, tech-savvy and wise consumer, who is constantly plugged in to the latest technologies. Read more

Everything you need to know about EDI2XML Translation Service

It’s no secret that our EDI2XML team loves helping businesses increase efficiency, improve partner relationships, accelerate movement of goods to customers and improve shipment accuracy by allowing them to easily exchange documents electronically between Trading Partners (read “Benefits of EDI Communication”).

But, how do they do this and for how much? We want our customers to fully understand the processes involved in our EDI Translation Service and all the costs involved as well. It’s about providing a service for companies that will only benefit them and not cause more hassles, issues or headaches. So, let’s start from the top; Read more

/0 Comments

PROs & CONs of Common EDI Translation Methods for SMEs

This post was updated to reflect current trends and information.

An article on our parent site, Namtek Consulting Services, called “Finding the Middle Ground with EDI Software & Services, ” explains the three most common options Small and Medium Enterprises look into when beginning to use EDI to exchange documents with their Trading Partners.

These 3 options consist of:
  1. Building an EDI translation tool from scratch and doing all communication in-house
  2. Going with a large, reputable EDI Vendor to outsource your EDI
  3. Buy an EDI translation tool, targeted solely to developers

Here are the PROs and CONs for each:

1.    Homegrown EDI Software

With this option, your company must have an in-house IT team, with the necessary EDI knowledge and experience to handle EDI capabilities and requirements.

PRO: The IT team is capable of developing their own EDI translation software to integrate within their ERP system for optimal performance. The whole process will be customized to their exact needs.

CON: This process usually ends up being very expensive and time-consuming for everyone involved. On top of it, many SMEs cannot afford to have their own in-house IT department and EDI experts.

2.    Prominent EDI Vendor

PRO: Large vendors help you connect to the retail industry’s largest network of Trading Partners.

CON: These Vendors are not cheap! Get ready to pay high monthly fees and to wait months at a time to hear back from their Support team.

3.    EDI Translators for Developers

PRO: These tools are affordable to buy, consisting only of a low one-time fee.

CON: Because these translation tools are used and maintained by developers, it requires knowledgeable resources in-house and ongoing support within the company to preserve all EDI capabilities. Your in-house team will need to handle all EDI mapping and requirements for each Trading Partner connection. Therefore, the cost to buy the translation tool may be within budget, but it will cost your company time, effort and in-house IT wages to complete the whole EDI project.

The best option? An EDI Fully Managed Service that is: Affordable, handles ALL EDI mapping, and has a great support team. Take a look at EDI2XML!
Free EDI consultation
/2 Comments

EDI X12, EDIFACT, CSV, XML – Why is a conversion necessary?

,


This post was updated to reflect current trends and information.
x12-to-xmlcsv

EDI formats are not understood or easily read by just anyone. It requires an EDI expert to be able to read the files and dissect them. Many large Trading Partners impose their own rules and requirements on top of those outlined by the standards, which is why, in many cases of translation, it is not always as straightforward as hoped. Most business executives are hesitant to begin trading via EDI because of these complexities.

However, if you find the right EDI Provider, who can handle all translations, all EDI mapping, all Partner configurations and all outbound and inbound communication with your partners, then you have nothing to worry about.

Our very own EDI2XML translation and integration services eliminate all of these complexities for you and you can begin trading electronically in no time. If you have your own in-house EDI and IT integration expert(s), then they can simply use our EDI2XML Web Service.

If you’re looking to meet your Trading Partner’s requirements but also keep your business processes streamlined and integrated internally, then check out EDI2XML. Our team of EDI experts are experienced and flexible enough to work with any EDI format, where specs are readily available, and convert to a format your team or system can work with. It’s about keeping costs low and simplifying the whole EDI communication process. Contact us today!

 

Free EDI Consultation

/0 Comments

Triple Threat: Integration of ERP, eCommerce & EDI

By now, I am sure most business professionals have heard about or have already implemented EDI, ERP Management Systems, and of course eCommerce Stores. If not, here’s a quick explanation of each Read more

/0 Comments

What you need to know about EDI integration in JD Edwards World

EDI integration project into JD Edwards (JDE) system.


The same questions and concerns keep arising when designing the requirements for an EDI integration project into JD Edwards (JDE) system. As I have been involved in my fair share of EDI integration projects, I have witnessed companies struggling with integrating EDI in JDE systems. I’ve decided to share my experience, not as a JDE expert but as an EDI integration expert and consultant, to help those with this kind of project. Let’s begin…

Why EDI integration is important

More and more companies are adopting different communication protocols to exchange business-related messages electronically. Today’s business environments are working harder to be well connected with outside parties for improved communication. It is almost impossible nowadays for a company to trade and do business without having the capability to electronically exchange messages and important documents with its suppliers and customers. This is why EDI has gained tremendous attention in recent years; businesses, no matter how large or small they are, are looking to receive EDI documents (i.e. customer orders) and send out responses such as invoices, or advance shipping notices (ASNs).

On top of this, with the expansion and popularity of eCommerce (electronic commerce), businesses have no choice but to integrate EDI into their systems as consumers expect quick response times in providing more accurate inventory availabilities and quick order processing for better customer service.

All of the above make it almost impossible for any company to ignore electronic processing of sensitive data, all in real-time. However, what’s been challenging for most, is that various business partners adopt different EDI standards, some even choosing a “custom made” version, which all adds new layers of complexity to an EDI integration project in JDE and more pressures to comply with tons of different EDI standards (i.e. X12, EDIFact, XML, CSV,…).

Benefits of integrating EDI into a company’s system

EDI has been around for quite some time now. At this point, there’s no question about the real benefits that come from using this B2B communication method. Companies are seeing more advantages and improvements when they integrate EDI transactions (incoming and outgoing) into their management software system. Some of these EDI integration benefits include:

  • An increase in a company’s response time and a decrease in their fulfillment cycle
  • Increased information integrity and a reduction in errors due to the elimination of manual data entry and human intervention
  • Fast and accurate delivery of goods and services

There’s no doubt that companies gain a competitive advantage by successfully integrating EDI into their management system. They are better equipped to handle more orders and have no problem doing business with large retailers who expect electronic messaging. 

How EDI processing works in JD Edwards

Let me give a quick description of the EDI processing cycle in JDE, as described by Oracle’s own documentation of the JDE system.

“When you receive inbound documents, the translator software retrieves the data using network communications and translates the data from EDI Standard format to JD Edwards World application file format”.

Here is a simple drawing posted in their online documentation:

EDI processing cycle in JDE

In simple terms, when a company running JD Edwards World or its previous version (Enterprise One) needs to process EDI data received from a business partner for example, the data will go through different stages:

  1. A communication software (a third party software) would connect and get incoming EDI files using network communications.
  2. The translator software translates the data from EDI Standard format to JD Edwards World application file format.
  3. Once the above two steps are completed, the system 47 of JD Edwards application, will take the data from the JDE flat format to JD application files.

JDE has its own EDI (Electronic Data & eCommerce) integration module. This module, can be configured to integrate EDI data formatted in JDE acceptable format and turn it into JDE application files. While doing so, tons of automatic triggers are fired up, such as billing address, items and pricing verification. In addition, error reports are generated and email alerts are sent.

Unfortunately, the file format that JDE is capable of processing is still a flat file format. I invite you to read this article where the author had explained a lot about JDE EDI integration and its file format.

It is important to know that the user must complete several tasks in order to customize the Electronic Commerce system to interact with your other applications and to fit your company’s needs, as per JDE’s online documentation.

Challenges with EDI integration in JD Edwards World

As I mentioned at the beginning of this article, there are many challenges that business executives struggle with when deciding to implement EDI and integrate it into their JDE system. I will highlight the most important ones and give my recommendations as an EDI integrator and expert on the topic.

Writing directly in JDE application file or using the EDI interface module

A very good question that comes up regularly is “Should we plan the integration engine to translate and write DIRECTLY inside the JD Edwards World applications files or use the Electronic Commerce module in JDE?

I personally recommend to work with the EDI module of JDE for the following reasons:

  • Out of the box, it works well once the right data in the appropriate format is provided to the engine.
  • Obviously, in the beginning, your JDE team will need to spend some time and effort setting things up; they can either do this all themselves or with the help of your EDI consultants.
  • Out of the box, when set up is completed correctly, the JDE engine is capable of taking the data and passing it through tons of validation steps (i.e. price, items, billing instructions…) prior to moving the clean data to JDE application files, without any human intervention.
  • Please note, however, that if you choose to have the EDI integration engine write directly to the JDE application files, a new JDE update or application upgrade can result in potential damages to this process. Upgrading the JDE application will require a full cycle of QA to make sure the integration engine of EDI into JDE is still working 100% efficiently.

Exchanging and translating XML, JSON, and other non-Flat File formats

The other challenge many have faced is knowing how to enforce JDE with the capability to translate non-standard EDI files such as XML, JSON or any other format given the fact that JDE’s EDI module is only capable of integrating with one single file format (more specifically a Flat file).

My recommendation would be to adopt a strategy where any file no matter its format received from your Trading Partner is automatically translated into a single format that is acceptable by your JDE EDI module, prior to initiating the process in JDE. I know it may seem difficult to achieve for such a mechanism considering the level of limitations provided by JDE, but this option is more feasible than you may think. I will go on to explore this possibility in the following section.

Looking to integrate your EDI or eCommerce processes with Oracle JDE enterprise one, look no further, since we have the best integration option where we turn your Oracle JDE system into a modern REST API, that receives https requests and acts accordingly. LEARN MORE>

What is the best option to integrate EDI in JD Edwards

Having listed the major challenges above, it is clear that the best option for a seamless, simple and quick EDI integration with your Trading Partners or your eCommerce platform is to adopt one single protocol of communication between your outside world and your JDE system.

In fact, Oracle’s JDE team have anticipated for such a protocol. They refer to in their documentation as the “translation software (third party)”.

I understand that managing a third party translation software internally by your team will add another layer of complexity, additional resources and expertise, not accounting for the countless number of EDI file formats found in today’s business world: TXT, CSV, EDIFACT, X12, XML, Json, etc.

You’re in luck though! There are a few companies out there, like Namtek Consulting Services, that can outsource the job of managing your translation software. Our EDI2XML cloud integration platform can act as your translation software; it can turn all your incoming files, no matter its format, into one format that your JDE loves to work with. The opposite works for outgoing files; your JDE-preferred format is easily and automatically converted into the specified format of your Trading Partners.

What challenges have YOU faced regarding EDI integration into your JD Edwards World system?

Free consultation ecommerce JDE integration

/0 Comments

Why EDI is becoming the #1 method for B2B Transactions

B2B communication and EDI

For a while, EDI was not well liked amongst Small & Medium Enterprises. These companies were finding it to be too slow, too complex and way too expensive. They then resorted to a lot of manual data entry for orders as they would receive orders and invoices via email or fax. However, over the years, things have changed…a lot and for the better. Read more

/0 Comments