EDI Integration with Oracle Cloud

White Paper

EDI Integrationwith Oracle Cloud

©2022 Jade Global Inc. All rights reserved

TM

Introduction

Business Requirements

Solution Approach

Solution Details

Design Architecture

Components Involved

Technical Components

Trading Partner Setup Screens

Technical Activities Involved

Challenges and Resolution

Conclusion

1

2

4

5

7

8

9

10

20

21

23

Table of Contents

White Paper

Introduction


This whitepaper describes the best practices of EDI (Electronic Data Interchange) Integration with Oracle Cloud.

EDI (Electronic Data Interchange) is the computer-to-computer exchange of business documents in a standard electronic format between business partners.

EDI documents can flow straight through to the appropriate application on the receiver’s computer (e.g. the Order Management System) and processing can begin

immediately.

The EDI process looks like this – no paper, no people involved:Prior to Oracle Cloud R13 i.e., Oracle EBS 11i and Oracle Release 12 came with a seeded e-Commerce gateway module formerly known as Oracle EDI Gateway. Oracle EDI

Gateway enables the ability to conduct business electronically between trading partners based on electronic commerce standards and methodologies such as EDI used for

integration.

1

EDI Integration with Oracle Cloud

White Paper

BusinessRequirements

©2022 Jade Global Inc. All rights reserved2

EDI Document Types: Jade Global used following EDI documents using ASC X12 message standard:

Inventory Advice Outbound (846)

PO EDI Document Inbound (850)

PO Order Acknowledgement EDI Document (855)

PO Changes EDI Document Inbound (860)

PO Change Order Acknowledgement EDI Document (865)

Invoices Outbound (810)

Advance Shipment Notice Outbound (856)

Return Authorization Outbound (180)

Currently, Oracle Cloud does not offer an Oracle EDI Gateway module. As a result, a custom solution/module has been implemented which can be used for EDI integration

with Oracle Cloud.

EDI Document/Message Standard: EDIFACT and ANSI X12 and TRADACOMS


White Paper


EDI File Format:


White Paper

SolutionApproach


The following technical components/ software services are used to build EDI integration with Oracle Cloud:

SOACS, DBCS, WebLogic, Oracle Apex, B2B Adaptor, OTBI, Webservices, Oracle Advanced Queuing i.e. AQ & DQ Tables.

SOA B2B Components, BPEL & Fusion Webservices. DB Adaptors & UMS Adaptors

Jade Global created an Integration (both inbound and outbound) to process EDI files between trading partners using Oracle SOACS (SOA Cloud Service), GSX middleware

and Oracle Fusion (Oracle Cloud) to achieve EDI integration with Oracle Cloud.


White Paper

About Jade Global

Jade Global is a Cloud-focused IT services partner specialized in enterprise business application implementations, integrations, software product engineering,

consulting, technology advisory, testing, and managed services. Jade is an Oracle Platinum Cloud Select Partner, Salesforce Silver Partner, Dell Boomi Select

Implementation Partner, and Service Now Silver Partner. Our additional global alliances with NetSuite, Microsoft and Zuora allow us to design robust solutions for

a variety of industries and needs. We are headquartered in San Jose, California with East Coast headquarters in Philadelphia. Jade has been recognized as one

of the fastest-growing companies in North America by Inc. 5000 for 9 consecutive years.

www.jadeglobal.com [email protected]

White Paper

SolutionDetails


Trading Partner used to place EDI file at client network location/directory

GXS middleware process EDI files and merge the different trading partner files into one and generate a position-based flat file

Position-based flat file will be transferred to B2B by GXS middleware

B2B service splits and generate separate files based on trading partners

B2B service will further poll the separated file based on TP agreements defined in B2B

SOA convert B2B payload and stage data for header and line transactions

Data enrichment (Validations & Derivations) will be performed in SOA DB using 'PL/SQL program'

Sync required data into SOA DB from Oracle Fusion Database

Call order web service to interface data and call ESS job to import and create sales orders in FA

Stage data in PaaS DB for record keeping, reporting and future processing


White Paper


Oracle SOA B2B Integration Diagram:


White PaperEDI Integration with Oracle Cloud

DesignArchitecture


The below image provides a snapshot of all components involved in the EDI integration:


ComponentsInvolved


Trading Partners: This EDI integration is developed for more than 90 trading partners such as Walmart, Target, BBB etc.

GSX Server: Middleware server is used to read/process the EDI file format & convert it into flat file format. However, this process can be handled by SOACS service itself.

Oracle SOACS, B2B: Oracle SOA Cloud server (SOACS) Middleware consists of many Oracle components.

The following components are being used:

Oracle SOA Suite: Enables the transformation of complex application integrations into agile and reusable service-based applications to shorten time to market,

respond faster to business requirements, and lower costs.

Oracle B2B: An e-commerce gateway that enables the secure and reliable exchange of business documents between an enterprise and its trading partners.

Oracle Fusion/ Cloud SaaS Application ERP: Oracle ERP Cloud offers a complete solution for organizations of all sizes that want to succeed in the digital economy.

Oracle provides a single Cloud for the entire business


TechnicalComponents


Oracle APEX: Oracle APEX rapid application development toolkit is installed on Oracle SOA Cloud DB instance and custom application so called APEX Pages are built using it.

Users can use this application to create/update/delete the trading partner information.

Custom tables are created in SOA DB and APEX pages are developed based on these tables.


Trading PartnerSetup Screens


1. Trading Partner Group



2. Trading Partner Assignment

3. Trading Partner Detail



2. Trading Partner Assignment

Oracle SOACS – A suite of Cloud services enabling development, execution and governance of integration flows connecting any combination of on-premises and cloud-based

processes, services, applications and data within individual or across multiple organizations.

Using SOACS subscription, organizations don't need to invest in elements such as infrastructure, licensing, installation, tuning, and maintenance. Also, there is no need to

worry about disaster recovery.



Oracle SOACS Middleware: Trading Partners place EDI files at the client network location. The GSX middleware server processes the EDI file and generates a position-based

flat file and places it to SOA ftp location. SOA B2B service splits the flat file into multiple files based on the trading partners. B2B Service further polls the separated files based

on TP agreement and places those files in a location from where the B2B server can select those files.

SOA B2B Server: Trading partners are configured in Oracle SOA B2B server. The server will read the EDI flat file from the directory based on a qualifier of each trading partner,

and convert it into XML format.



a. SOA Convert B2B payload to canonical format and stage data for Sales Order header and line transactions tables

b. SOA DB PL/SQL program - Data Validations, Derivations data enrichments will be performed using SOA DB PL/SQL program. Need to sync required data into SOA local DB

(Required data will be pulled into SOA local database ahead of time using PL SQL, OTBI service)



c. SOA Call Order Web Service “Stage Order” to Interface data and call 'Import Sales Order' ESS job to import and create orders in Oracle Fusion application



PaaS DB: Stage data in PaaS DB for record keeping, reporting and future processing

Oracle AQ/DQ: Advanced queuing provides a database-integrated message queuing functionality in which web-based business

applications communicate with each other, producer applications queue messages, and consumer applications dequeue

messages.

A scheduler is run every minute which checks whether all records from batches are processed. All records are processed and then

generate payload and perform AQ activity. SOA to DQ message and update SOA stage header table.

DBMS Scheduler: DB Scheduler is used for scheduling any action in the database using the following:

Create Scheduling Object - DBMS_SCHEDULER.CREATE_SCHEDULE (schedule_name, start_date, repeat_interval, comments);

Create Program Object - DBMS_SCHEDULER.CREATE_PROGRAM ( program_name,program_type, program_action,

number_of_arguments, enabled, comments);

Create Job Object - DBMS_SCHEDULER.CREATE_JOB (job_name, program_name, schedule_name, enabled, comments);



Oracle BI Report: Jade Global has developed BI reports to extract data (to sync cloud data with SOA DB custom tables) from Oracle Cloud and validate EDI file records against

Cloud database:



Data Model: A data model is an object that contains a set of instructions for BI Publisher to retrieve and structure data for a report:



Error Console: Below error console screen (based on Sales Orders custom tables in SOA DB) using Oracle APEX is developed to track the errors/ success records for a given

order import batch and a mechanism to reprocess the records are failed:


TechnicalActivities Involved


Oracle SOA B2B: Setup is required for all trading partners (includes document, agreement creation and FTP listening channel).

Oracle Apex: APEX Installation in SOA DB, add Fusion certificates in DB Wallet of APEX.

Custom Tables for Trading Partners: Create custom tables to replicate Oracle ERP 11i/R12 seeded ones like ECE_TP_HEADER, ECS_TP_DETAILS

Oracle SOA Cloud Service: Define Data source, JNDI creations and AQ adapter configurations in Admin Console. Import fusion certificate in SOA Environment, Import mail

certificate in SOA Environment, setup email configuration.


Challenges andResolution


Bulk Data Process: Customers existing Oracle 11i system can process EDI PO file to create sales orders with more than 10,000 lines each and wanted to have same working

functionality with Oracle Cloud.

The client requirement was to process the EDI file containing:

Resolution: Oracle 'Import Sales Order' program has a limitation and cannot process if the Sales Order lines are more than 500. Oracle recommendation is to create multiple

orders for the same PO in a batch of 200 or 500 Sales Order lines each. Jade Global confirmed with the client to create multiple Sales Orders. One PO has more than 200 lines,

so Jade Global developed a logic to process batches of 200 lines.

150 to 300 Pos with 6,000 lines (max 200 lines per PO)

1 PO has more than 6,000 lines

Issue Encountered:

Fusion Order Import program failed to load such big payload (1 PO having 6000+ Lines) when using FBDI based on Oracle recommendation

SOA failed while processing a big payload

Orders are created in locked status



Sync Program for Custom Validation: In order to perform PO header/lines data/custom validation (item, item pricelist etc.) the sync program is created to first get/download

all respective data into the SOA database and sync it with the Oracle Fusion database (a schedule program is created and executes the sync program (PL/SQL Procedure)

every 30 minutes).

Issue Encountered: There will be a performance issue and the SOA process will be timed out if any such custom validation is performed directly against the Fusion database

using the Oracle BI report.

Resolution: A custom sync program “PL/SQL Procedure” is scheduled and executes every 30 minutes to sync records from Fusion application database to the SOACS

database. The procedure used to call Oracle BI report using this webservice is named apex_web_service. make_request() API.

See below: https://ehzr-dev1.fa.us2.oraclecloud.com/xmlpserver/services/PublicReportService?WSDL

The report output data will be converted into base64 and loaded into SOACS database custom tables.

Oracle 11i TP Data Migration and Data Cleansing: To migrate Oracle 11i trading partners data, Jade Global must download millions of records from 11i database and then

upload the data into custom tables in SOACS DB. Jade Global deleted all unused and invalid records from the tables and updates them if required.


Conclusion


Unavailability of the EDI module in Oracle Order Management SaaS (Oracle Cloud) solution is addressed by developing a custom PaaS solution using SOACS middleware

and Oracle APEX.

The solution addresses the minimum basic business requirement of integrating Oracle SaaS with systems of trading partners for creating bulk orders in Oracle B2B

environment.

Oracle SOA Cloud server (SOACS) does the exchange of EDI files based on the trading partner agreements defined in B2B. It also takes care of data validations, deriva-

tions, and data sync to address performance requirements in data processing.

Custom GUI developed in Oracle APEX (Development Toolkit) helps users setup trading partners, and validate processed records to check logs. The error console is also

provided to rectify and reprocess erroneous records.

About Jade Global


San Jose | Philadelphia | Toronto | Vienna | Pune | Hyderabad

Jade Global provides enterprise business application implementations, integrations, software product engineering, cloud services, technology advisory, testing,

and managed services across diverse industries. We are head quartered in San Jose, California with U.S. offices in Philadelphia and Los Angeles. Jade Global is

an Oracle Platinum Cloud Select partner, Salesforce Silver Partner, ServiceNow Silver partner, Boomi Elite Partner, Snowflake Select and Microsoft Gold partner.

We have additional strategic partnerships with NetSuite and AWS. Jade Global has been recognized as one of the fastest-growing companies in North America

by Inc. 5000 and was featured on the Fastest Growing Private Companies list in the Silicon Valley Business Journal.

www.jadeglobal.com [email protected]

TM

Documents

EDI Integration with Oracle Cloud