Previous	Next		Contents	Index	Navigation	Glossary	Library

Step 1. Define Data File Directories

To use EDI Gateway, you must first create directories where data files, for both inbound and outbound transactions, are stored. You must then specify these in the INIT.ORA file and in the EDI Gateway profile options. See: Defining Data File Directories and EDI Gateway Profile Options.

Step 2. Define Trading Partner Data

First, define a trading partner group and associate all trading partner location (address) entities to this group. Define basic information about the trading partner and associate that to a specific trading partner's location. This is necessary to integrate Oracle Applications and EDI translator software. See: Defining Trading Partner Data.

Step 3. Define Code Conversions

The Oracle EDI Gateway code conversion function provides a method by which trading partner and standard codes can be converted to Oracle Application codes and vice versa. See: Overview of Code Conversion.

1. Define code conversion categories to specify a subset of codes within the code conversion table. See: Defining Code Conversion Categories.

2. For each data element in a transaction that requires code conversion by EDI Gateway, assign one code conversion category. See: Assigning Categories.

3. Enter the actual code conversion values from the internal codes to external codes into the code conversion table. The internal codes are defined in the Oracle Applications. The external codes are the associated values required by the trading partner or chosen EDI standard.

Step 4. Customize Data File Formats

Oracle delivers a standard predefined data file format containing all the data that may be required to support a particular EDI transaction. You may customize this data file to meet specific business needs. See: Changing the Data File.

Step 5. Initiate EDI Transactions

Once data file directories, trading partner information, code conversions, and optional customizations of data files have been performed, use Oracle Applications Standard Request Submission to run extract programs for outbound transactions and import programs for inbound transactions. See: Running the Extract Programs for Outbound Transactions, Running the Import Programs for Inbound Transactions, and Viewing the Status of Concurrent Programs.