Extensible EDI Gateway Architecture
While the Oracle Applications data model is robust enough to meet most needs, you may need additional information for EDI transactions--either now or in the future--as EDI transaction sets change. The extensible EDI Gateway architecture gives you great flexibility to customize your outbound EDI transactions.
Architecture Overview
Extensible EDI Gateway architecture includes:
- Transaction-specific interface tables
- Transaction-specific extension tables
- A table of the interface tables
- A table of the interface columns
Transaction-Specific Interface Tables
A series of tables with names in the format ECE_<Transaction.Name> exist to provide as much information for specific transactions as possible. In addition, each of these tables contain:
- a foreign key to the transaction-specific extension table, called TRANSACTION_RECORD_ID, also resides in this table. The relationship between these two tables is one-to-one.
Transaction-Specific Extension Tables
A series of tables with names in the format ECE_<Transaction.Name>_X exist that hold data from sources other than Oracle Applications.
The primary key for this table is TRANSACTION_RECORD_ID, referenced by the foreign key TRANSACTION_RECORD_ID in the corresponding transaction-specific interface table.
During installation, the table is created with only one column, the TRANSACTION_RECORD_ID column. Simple SQL statements, like the ALTER TABLE command can be used to customize this table. You can add to or modify this table according to your requirements for the transaction.
A Table of Interface Tables
This table, named ECE_INTERFACE_TABLES, stores the starting identifier (number) of each section of the output file. Some notable columns include:
- the composite primary key, TRANSACTION_TYPE and INTERFACE_TABLE_NAME
- TRANSACTION_TYPE, which identifies the transaction; for example, POO (for outbound purchase order), and so on
- INTERFACE_TABLE_NAME, which identifies the transaction-specific interface table
- START_NUMBER, which stores the starting identifier number of each section in the output file
- EXTENSION_TABLE_NAME, which tracks the transaction-specific interface and extension tables that are related
A Table of Interface Columns
Data extract programs need guidelines to write output data in the correct position of the output file. This table, named ECE_INTERFACE_COLUMNS, stores this type of location information. Notable columns:
| INTERFACE_COLUMN_ID
| Primary key.
|
| INTERFACE_TABLE_ID to ECE_INTERFACE_TABLES
| Foreign key.
|
| BASE_TABLE_NAME
| The view from which data is extracted.
|
| BASE_COLUMN_NAME
| The column of the view from which data is extracted.
|
| POSITION
| The relative position on the record in the data file.
|
| INTERFACE_COLUMN_NAME
| The column where the data is temporarily stored in the interface table before being written to the data file.
|
See Also
Technical Overview
Extensible Architecture Example
