EDI 102 Associated Data

Functional Group AC

X12C Communications and Controls Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Associated Data Transaction Set (102) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set may be used to convey associated data. Associated data is defined as an object, a set of functionally-related information not using the usual transaction set structure in segments. The complete set of information constituting an object, including the information necessary to uniquely identify an object, is defined as a package. Objects may include graphic, text, parametric, tabular, image, spectral, audio, etc. data. The character set repertoire of an object is not governed by the character set repertoire identified for any accompanying transaction sets contained in the interchange. Associated data may be linked with other business transactions as an augmentation to other functional data. Therefore, referencing capabilities properly relating the object to the associated transaction set must be provided. Because user preferences require flexibility within the techniques for referring to an object, no particular methodology is specified. The only requirement is the assignment of an object identification number attributable to the object which should be unique for a sufficient time to avoid any confusion. Multiple references to identify all related transaction sets and objects are permitted. The transaction set is not media dependent, is not limited to a specific transmission protocol, and can be linked to other transaction sets. Interchanges may contain functional groups containing transaction sets, packages, or transaction sets and packages. The transaction set may be included in any functional group within an interchange. Only one package may be conveyed within a single occurrence of an Associated Data Transaction Set.

Heading

1. 0100 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

2. 0200 · ORI · Associated Object Reference Identification · Max 1 · Mandatory

   To identify the object identification reference

   The ORI segment shall identify the object identification reference number. This corresponds to the object identification specified in any related applicable transaction set where the REF (or equivalent) segment is used to link the functional data and object(s).

3. 0300 · REF · Reference Identification · Max >1 · Optional

   To specify identifying information

   An occurrence of the REF segment will, if needed, identify a unique application transaction reference number specified in the transaction set associated with the object.

4. 0400 · OOI · Associated Object Type Identification · Max >1 · Mandatory

   To identify attributes and status related to the object

   One occurrence of the OOI segment is mandatory and shall be used for file format identification (Code value "13" in data element 1691).

5. 0500 · BDS · Binary Data Structure · Max 1 · Mandatory

   To transfer binary data in a single data segment, convey a critical filter for transmission and allow identification of the end of the data segment through a count; there is no identification of the internal structure of the binary data in this segment

   The BDS segment shall contain the object.

6. 0600 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)