Oracle eCommerce Gateway Overview

The Oracle Gateway resides between the Oracle Applications and the EDI Translator. The Gateway processes data between Oracle Applications and the EDI Translator using ASCII interface flat files. The EDI Translator accommodates the standards and all the monitoring of transmitting standard formatted data between Trading Partners. For outbound data, the EDI Translator maps data from the Oracle interface flat files to any standards of choice. For inbound data, the EDI Translator maps data from the standards of choice to the Oracle interface flat file. The format and content of this flat file can be easily adjusted using the open interface definition table within the Oracle Gateway, though any changes that are made should also be implemented within the EDI Translator set-up. The Gateway processes data via an interface file which is received from or sent to the EDI Translator. The Gateway is independent of all standard formats since only the business data is found in the Oracle Gateway defined interface files. Additionally, the Oracle Gateway provides general code conversion functions for data such as Unit of Measure, Shipping Codes, Payment Terms, and determines the Trading Partner EDI validation/authorization between the Oracle application and the EDI Translator. Inbound Transactions For inbound transactions Oracle Gateway populates the Application Open Interfaces within the Oracle Application products. All of the necessary application logic to validate and load data is provided by the Application Programming Interface code (APIs), i.e. not by the Gateway. The Gateway only populates the relevant Application Open Interface tables recognized by the APIs for the specific EDI message/transaction. Process Flow The Oracle Gateway performs the following functions during an inbound transaction process after it receives an interface file from the EDI Translator or other process: • Gets Trading Partner validation processing parameters • Applies code conversions (if set up and activated). • Loads valid data into the appropriate Oracle Application Open Interface tables for the transaction. • e-Commerce Gateway captures transaction data exceptions. These exceptions can be reviewed on-line from the staging tables to examine the exception condition. The correction action is performed in a trading partner set up or other application set up. The transaction can then be revalidated. Outbound Transactions For outbound transactions, the Gateway extracts the data from the base Application tables. Also, it may optionally extract data from other files/tables using the built-in extensible architecture using ‘Extension’ tables. The use of Extension tables requires customization of standard code packages provided with the Oracle Gateway if the user has need of this function. Process Flow The Oracle Gateway outbound transaction process creates interface data files to support any EDI Standard that is available from the EDI Translator. The Oracle Gateway collects all of the business data needed to map to a standard EDI transaction/message which the receiving Trading Partner can interpret properly into their receiving application using their equivalent of the Gateway/EDI Translator set up. The Oracle Gateway does the following: • Gets Trading Partner processing parameters, e.g. location codes, allowable/enabled EDI transactions/messages, etc., • Extracts data from the Oracle base applications tables relevant to the EDI transaction/message being processed. • Optionally, retrieves data from customer defined extension tables (requires some customization). • Applies code conversions (when set up and activated). • Populates Oracle Gateway interface tables with all the data gathered. • Sets the data extract flags in the base Oracle Application table to prevent subsequent extraction. • Produces an interface data file for use by the EDI Translator. Note The Oracle Gateway does not have communication software to transmit the standard formatted data between Trading Partners. The Oracle Gateway relies on the EDI Translator being connected to third party communication service providers to transmit data to, or receive data from, Trading Partners after the data is mapped to the desired standard format.