Overview of Data File Structure
Oracle EDI Gateway produces an ASCII data file for outbound transactions. For inbound transactions, EDI Gateway processes an ASCII data file produced by the EDI translator software that contains the trading partner's business data.
Each data file consists of several records. Each record has two sections, the record key (positions 1-100) and the application data area (positions 101 to 600).
The structure is shown in the following table:
| Common Key (1-100)
|
|
|
| Trading Partner Code (short)
| 1-25
| 25
|
| Key 1 (primary document identifier)
| 26-47
| 22
|
| Key 2
| 48-69
| 22
|
| Key 3
| 70-91
| 22
|
| Record Number
| 92-95
| 4
|
| Record Number
| 96-97
| 2
|
| Record Qualifier
| 98-100
| 3
|
| Application Data (101 - 512+)
| 101-600
| 500
|
You can customize the data file per your specifications and define any logical record size to be less than 600 bytes.
Reusable Predefined Records
Predefined record layouts such as those for addresses, contacts, and flexfields are defined by the EDI Gateway. However, verify each data element length in the detail record for discrepancies.
Control Record (Record Number 0010)
All transactions begin with a control record that contains transaction identification, trading partner identification, key document numbers, document codes, and batch control numbers. Batch control numbers from the standard transactions are for inbound transactions only since they are received with the transactions.
Record Key
Each record within a transaction has a record key area of 100 characters (positions 1-100). This area contains the trading partner code, one to three key identifiers from the transaction document, and record identification codes. This data should facilitate sorting of the file if data must be regrouped to facilitate alternate data mapping, and audit and research of transactions when needed.
The record number in positions 92-95 is the record identifier to indicate the set of data elements on the record.
Each transaction writes different data in Key-1, Key-2, and Key-3 in positions 26-91. Key-1 should be the primary document identifier, for example, invoice number for the invoice transaction, and purchase order number for the procurement transactions.
Flexfields
The EDI Gateway defines all descriptive flexfields with length of 80 characters instead of their maximum table length of 150 characters. Most flex fields span four interface file records to store 15 flex fields or five interface records for 20 flex fields depending on the application tables. The customer may shorten the fields to actual lengths for their data and fit the flex fields onto fewer records, or even one record if they choose. (Use the Interface File Definition window to make these adjustments.) See: Changing the Data File.
Re-definable Records
You can redefine which records are actually written to the interface file from all the predefined records in the general transaction extract. (Use the Interface File Definition window to make these adjustments.) See: Changing the Data File.
After the records are defined and written to the interface file, all the defined records are written to the interface table even if there is no application data after the record key area. There is no skipping of flexfield records if there is no application data, except in the case where the record is suppressed by removing the data element using the Interface File Definition window. See: Changing the Data File.
