Previous	Next		Contents	Index	Navigation	Glossary	Library

• retrieves processing rules defined for the transaction and trading partner

• applies trading partner location cross reference

• extracts information from the Oracle Applications database into EDI Gateway interface tables

• applies code conversion to Oracle Applications internal data to derive external data

• creates a data file that via the EDI translator become the EDI document

• updates the Oracle Applications database that the EDI document has been extracted

Prerequisites

   Create the outbound directory and update the INIT.ORA file. See: Defining Data File Directories.

   To run the extract programs for outbound transactions:

1. Define the ECE: Output file path profile option. See: EDI Gateway Profile Options.

2. Define trading partner and enable EDI transactions for the trading partner. See: Define Trading Partner Data.

3. Define code conversions.

See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.

4. Customize data file layout, if necessary. See: Changing the Data File.

5. From the Navigator, choose Extract Programs.

See Also

Running the EDI Application Advice Outbound Extract Program

Running the EDI Invoice Outbound Extract Program

Running the EDI Purchase Order Outbound Extract Program

Running the EDI Outbound Purchase Order Change Request Extract Program

Running the EDI Outbound Planning and Shipping Schedule Extract Program

Running the EDI Payment Order / Remittance Advice Outbound Extract Program

Viewing the Status of Concurrent Programs

Submitting a Request