Record Key (1-100) (Oracle EDI Gateway Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Record Key (1-100)

The following table describes the Oracle data file record key which occupies the first 100 characters of each record in every transaction. This area facilitates any visual audit and research into the file.

Note: The content of the first 100 characters on the control (0010) record is defined the same as every other record in the interface file.

Some of the transaction data in the record key may be truncated so the EDI translator should refer to the full transaction data in the data area (positions 101-512) of the record.

The data in Key 1 through Key 3 varies by the transaction and the record level within the transaction.

Attention: The record number should allow the EDI translator to uniquely identify a record layout within the transaction. Do not rely on the record layout code and record layout qualifier to uniquely identify a record.

Record Key Data Element Summary

Seq.	Data Element	Position	Length	Note
1	TRADING PARTNER CODE (short)	1-25	25	This is the trading partner code for this transaction as defined by the EDI translator. This field may be truncated from the full Trading Partner Code in positions 149-183 on the Control 0010 Record.
2	KEY 1 (Primary Key)	26-47	22	This is the Primary Key from the transaction. It may be the purchase order number, invoice number or shipper number for corresponding transactions. Full primary document key is written in positions 114-148.
3	KEY 2	48-69	22	This is the second level key for the given transaction, e.g., detail level with item as a key.
4	KEY 3	70-91	22	This is the third level key for the given transaction.
5	RECORD NUMBER	92-95	4	This is a four position number to identify the record in this transaction. Use this field to identify what is on the record.
6	RECORD LAYOUT CODE	96-97	2	This is a two character code to identify record content.
7	RECORD LAYOUT QUALIFIER	98-100	3	This is a three character code to identify or qualify the record content especially if the record has a reusable record layout.
Table 1 - 20.

Trading Partner Code (1-25)

This code is the trading partner identifier as defined in the EDI translator. The code identifies the communications method, electronic mailbox, standard, and data maps for the specific transaction. This code is the link between the EDI Gateway and the EDI Translator.

This code is defined as the translator code in the Details region of the Trading Partner window.

Keys 1-3 (26-91)

Keys 1-3 represent key data from the first three levels of the given transaction. This data is for audit or research purposes to facilitate reading the file directly. The data may be truncated.

Key 1 is the Primary Key from the transaction. It may be the purchase order number, invoice number, or shipment number for corresponding transactions. Full primary document key is written in positions 114-148 of the control 0010 record.

Keys 2-3 represents other data at the second and third level within the transaction. A transaction may have more than three levels of data which are not stored in the key area.

Record Number (92-95)

The record number is a unique number within a transaction to identify specific data in a transaction. EDI translators should rely on the record number to uniquely identify a record in the data file.

Data levels in a transaction have record numbers in the thousandth range. A sample of a simple numbering scheme and a larger range numbering scheme are displayed in the following table. Any transaction may use any range of numbers for a data level. The number usually increments by 10 within a data level.

The record numbers are not used consistently across transactions. For example, the record 1050 may contain different data depending upon the transaction.

The X900 series in any range is reserved for EDI Gateway extension tables for consistency.

Sample Record Numbers

Record Number Sample-Simple Transaction	Record Number Sample-Longer Transaction	Content
0010	0010	Control Record
0020-0050	0020-0050	EDI Gateway Flex Fields
1000-1890	1000-4890	Application Header Level
1900-1990	4900-4990	Application Header Level Extension Table (Customized)
2000-2890	5000-5890	Application Detail Level 1
2900-2990	5900-5990	Application Detail Level 1 Extension Table (Customized)
3000-3890	6000-6890	Application Detail Level 2
3900-3990	6900-6990	Application Detail Level 2 Extension Table (Customized)
4000-4890	7000-7890	Application Detail Level 3
4900-4990	7900-7990	Application Detail Level 3 Extension Table (Customized)
et cetera
Table 1 - 21.

Record Layout Code (96-97)

The record layout code is used to indicate the type of data in the record. These codes are particularly useful when reusable records such as addresses and flexfields are used in the file.

Except for reusable records defined by the EDI Gateway, the record layout may have a different meaning across transactions. For example, the record layout IT may contain different data depending upon the transaction.

Record Qualifiers (98-100)

Record qualifier codes qualify what type of data is on the reusable records or any other record in the transaction. For example, an AD address record must be qualified to be a ship-to, bill-to, remit-to, and so on address record for visual purposes.

Other record qualifiers are assigned to every record in the transaction to complete the record key, but they do not necessarily facilitate data mapping since only the record number uniquely identifies a record to the EDI translator.

Sample Record Number, Record Layout, and Record Qualifier

Record Number	Record Layout	Record Qualifier	Content
0010	CT	CTL	Control Record
1010	AD	ST1	Address Record with Ship to Location Data
1040	AD	BT1	Address Record with Bill to Location Data
1060	A1	HD1	Flex Field data with Reusable Record A1 Layout qualified by HD1
1070	A2	HD2	Flex Field data with Reusable Record A2 Layout qualified by HD2
2000	IT	ITM	IT for Item data qualified by ITM to distinguish the data from other IT records in this transaction.
2100	A1	IT1	Flex Field data with Reusable Record A1 Layout qualified by IT1
2110	A2	IT2	Flex Field data with Reusable Record A2 Layout qualified by IT2
et cetera
Table 1 - 22.