Oracle EDI Automation: the usage of the eCommerce Gateway with out a translator
Of all the enterprise ERPs out there, Oracle E-Business Suite (EBS) arguably has the least out-of-the-box functionality when it comes to EDI.
This means that when you buy Oracle you get the platform and the modules, but you’re on your own when it comes to actually integrating and automating EDI transactions into the system.
Oracle’s recommendation: integrate through the e-Commerce Gateway
This sounds simple on the surface until you realize that Oracle also recommends an EDI translator as part of a basic EDI architecture.
Below is Oracle’s recommendation for outbound document flow, where transactions are published by the e-Commerce Gateway as flat files, converted by the EDI translator, and then connected to whatever communication protocol is preferred (VAN, AS2, etc).
The same goes for the inbound document flow, with one added step — the e-Commerce Gateway flows through Oracle Open Interface to pass transactions through to EBS. The Oracle Open Interface isn’t critical to the operation here, though it does provide interfaces that allow users to view and update error transactions and control the import process.
As far as the architectural detail is concerned, Oracle does a decent job explaining how you need to set up EDI for EBS. For organizations with plush IT budgets and robust EDI staff, no big deal, grab yourself a translator and off you go.
Organizations without unlimited resources, however, often end up with shoddy processes because with EDI you don’t know what you don’t know until you get into it.
You also come to find that there are critical orchestration, visibility, and workflow processes and tools essential to automation.
It goes from bad to worse quickly when there are staff or budget cuts during the build, or when a key person decides to move on or retire. All in all, you can end up with an EDI rat’s nest pretty quickly if you aren’t careful.
Full-Service EDI for Oracle EBS
Is there a better way to do it? For organizations looking to outsource the answer is a resounding yes. EDI Here Full-Service EDI for Oracle EBS is one such solution.
EDI provides end-to-end System Automation technology in the cloud, meaning that you don’t have to buy and deploy a translator.
The orchestration, visibility, and workflow tools essential to EDI are all included so you don’t have to build those out in Oracle.
Modifying the Oracle architecture with System Automation for outbound
The architecture is simple because the concept is simple, which is to outsource everything that isn’t a core competency or strategic initiative of your company to a provider like EDI.
Put another way, translation technology can be more effective in the cloud as a full-service solution, where the third party provides the translation, validation, and enrichment of data, along with configurable dashboards, error handling, and workflow tools needed for every role in the organization.
After translation, transactions move through the EDI Universal Network and off to your trading partners.
This means that you connect to EDI once instead of building out hundreds of point-to-point maps that require ongoing updates and maintenance.
Flip it around for inbound …
Here, EDI does all the dirty work in the cloud and sends over a configured EBS file for pickup. Translator? Gone. Point-to-point maps gone, rat’s nest with all the excessive manual keying, slow onboarding, chargebacks and fees, lack of visibility, lack of error handling: all gone.
If you’re embarking on a new Oracle implementation or are struggling to integrate EDI in your current environment, we’d love to talk more about our full-service opportunities.