This chapter covers the following topics:
Oracle E-Business Suite provides users with the ability to conduct business electronically between trading partners based on Electronic Commerce standards and methodology. One form of Electronic Commerce is Electronic Data Interchange (EDI). EDI is an electronic exchange of data between trading partners. Interface data files are exchanged in a standard format to minimize manual effort, speed data processing, and ensure accuracy. The Oracle e-Commerce Gateway (formerly known as Oracle EDI Gateway) performs the following functions:
Define trading partner groups and trading partner locations.
Enable transactions for trading partners.
Provide general code conversion between trading partner codes or standard codes and the codes defined in Oracle E-Business Suite.
Define interface data files so that application data can integrate with your trading partner's application or an EDI translator.
For inbound transactions, import data into application open interface tables so that application program interfaces (API) can validate and update Oracle E-Business Suite application tables.
For outbound transactions, extract, format, and write application data to interface data files.
Oracle e-Commerce Gateway augments the existing standard paper document capabilities of Oracle E-Business Suite, or adds functionality where no corresponding paper documents exist.
The Oracle e-Commerce Gateway Implementation Manual is written for system administrators, consultants, and any members of your implementation team. This User's Guide is written primarily for the end user.
Oracle e-Commerce Gateway is designed with an open and flexible architecture for easy integration with trading partners and / or EDI translators. The e-Commerce Gateway provides a seamless application to application integration solution. When used for EDI (Electronic Data Interchange) solutions, e-Commerce Gateway integrates with EDI translators to provide specific EDI standard formats and versions.
Oracle e-Commerce Gateway is a file-based integration layer between Oracle E-Business Suite and any other external application. It uses ASCII (American Standard Code for Information Interchange) formatted interface data files.
Transaction data originating from an external trading party is formatted and transmitted to the receiving trading partner. Once received, the data may go through another formatting process, an EDI translator for example, resulting in an interface data file based on the standard layout defined in the e-Commerce Gateway. The e-Commerce Gateway then processes the interface data file and passes the data to the receiving application for additional business rule validation and transaction creation.
Transaction data originating from Oracle E-Business Suite is processed by the e-Commerce Gateway and formatted into a standard interface data file. The e-Commerce Gateway then routes the data to the next step in the process flow. The process flow may include processing by an EDI translator for EDI-specific formatting or may involve transmission to the receiving trading partner. Each of these processing steps are integrated and automated so transaction data can flow seamlessly in either direction from trading partner to trading partner with little if any human intervention.
For inbound transactions, the e-Commerce Gateway does the following:
The e-Commerce Gateway receives a file from any source in the standard transaction interface data file format defined in the e-Commerce Gateway.
The e-Commerce Gateway then processes the data by first validating the trading partner sending the transaction against trading partners defined in e-Commerce Gateway. The e-Commerce Gateway then processes any enabled code conversion, process rules, and column rules.
Transactions that pass process and column rules are mapped and written to specified Oracle E-Business Suite open interface tables for application-specific business rule validation. Transactions that do not pass these validation / code conversion rules remain in the exception module where users can analyze the exceptions. After corrective action in other modules or in the e-Commerce Gateway, the transaction may be resubmitted for re-validation. Alternatively, if your trading partner will re-send the transaction, you may delete the transaction from the exception module.
The base Oracle application continues validating transactions written to the application's open interface tables. All valid transactions are written to the application tables. Invalid transactions remain in the open interface tables subject to the application's standard error handling procedures. All these processes are automated so that transactions with no errors are posted directly to the base application tables with no human intervention.
For outbound transactions, the e-Commerce Gateway does the following:
A user-defined or an application event signals the e-Commerce Gateway to begin the outbound process. User-defined events are set up using the Oracle E-Business Suite Concurrent Manager.
The e-Commerce Gateway extracts data from the application transaction tables and verifies that the receiving trading partner is authorized to receive the transaction. Code conversion rules are applied to the data and the data is mapped and written to the transaction interface data file. The format of this file is based on the standard file layout define in the e-Commerce Gateway.
The following tables show the transactions that are supported:
| ASC X12 | EDIFACT | Transaction Code | Description |
|---|---|---|---|
| 810 | INVOIC | INI | Inbound Invoice. This includes support for the following transactions: Air Freight Details and Invoice (110), Motor Carrier Freight Details and Invoice (210), Rail Carrier Freight Details and Invoice (410), and Grocery Product Invoice (880). |
| 832 | PRICAT | CATI | Inbound Price/Sales Catalog |
| 843 | QUOTES | RRQI | Inbound Response to Request for Quote |
| 856 | DESADV | ASNI | Inbound Ship Notice/Manifest |
| 857 | No equivalent | SBNI | Inbound Shipping and Billing Notice |
| ASC X12 | EDIFACT | Transaction Code | Description |
|---|---|---|---|
| 824 | APERAK | ADVO | Outbound Application Advice |
| 810 | INVOIC | INO | Outbound Invoice. This includes support for the following transactions: Air Freight Details and Invoice (110), Motor Carrier Freight Details and Invoice (210), Rail Carrier Freight Details and Invoice (410), and Grocery Product Invoice (880). |
| 812 | CREADV / DEBADV | CDMO | Outbound Credit Memo / Debit Memo |
| 820 | PAYORD / REMADV | PYO | Outbound Payment Order / Remittance Advice |
| 830 | DELFOR | SPSO | Outbound Planning Schedule |
| 862 | DELJIT | SSSO | Outbound Shipping Schedule |
| 850 | ORDERS | POO | Outbound Purchase Order |
| 860 | ORDCHG | POCO | Outbound Purchase Order Change Request |
| None | CUSDEC | MVSTO | Outbound Movement Statistics |
The following tables show the transactions that are available through other products, specifically, Oracle Process Manufacturing, Oracle Order Management, and Oracle Release Management.
| ASC X12 | EDIFACT | Transaction Code | Long Name |
|---|---|---|---|
| 850 | ORDERS | GPOI | OPM: Inbound Purchase Order |
| 855 | ORDRSP | GPOAO | OPM: Outbound Purchase Order Acknowledgment |
| 856 | DESADV | GASNO | OPM: Outbound Ship Notice/Manifest |
| ASCX12 | EDIFACT | Transaction Code | Long Name |
|---|---|---|---|
| 850 | ORDERS | POI | Inbound Purchase Order |
| 855 | ORDRSP | POAO | Outbound Purchase Order Acknowledgment |
| 856 | DESADV | DSNO | Outbound Ship Notice/Manifest |
| 860 | ORDCHG | POCI | Inbound Purchase Order Change |
| 865 | ORDRSP | POCAO | Outbound Purchase Order Change Acknowledgment |
| 875 | ORDERS | POI | Inbound Grocery Purchase Order |
| ASCX12 | EDIFACT | Transaction Code | Long Name |
|---|---|---|---|
| 830 | SPSI | SPSI | Inbound Planning Schedule |
| 862 | DELJIT | SSSI | Inbound Shipping Schedule |
| 866 | No Equivalent | PSQI | Inbound Production Sequence |
Note: For additional information, see Oracle e-Commerce Gateway Implementation Manual.