OTI Original Transaction Identification

To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result

Position: OTI-01 · Element: 110 · Name: Application Acknowledgment Code · Type: Identifier (ID) · Requirement: Mandatory · Min: 1 · Max: 2 · Repeat: 1

Code indicating the application system edit results of the business data

Position: OTI-02 · Element: 128 · Name: Reference Identification Qualifier · Type: Identifier (ID) · Requirement: Mandatory · Min: 2 · Max: 3 · Repeat: 1

Code qualifying the Reference Identification

OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification.

Position: OTI-03 · Element: 127 · Name: Reference Identification · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 80 · Repeat: 1

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

OTI03 is the primary reference identification or number used to uniquely identify the original transaction set.

Position: OTI-04 · Element: 142 · Name: Application Sender's Code · Type: String (AN) · Requirement: Optional · Min: 2 · Max: 15 · Repeat: 1

Code identifying party sending transmission; codes agreed to by trading partners

If used, OTI04 through OTI08 will contain values from the original electronic functional group generated by the sender.

Position: OTI-05 · Element: 124 · Name: Application Receiver's Code · Type: String (AN) · Requirement: Optional · Min: 2 · Max: 15 · Repeat: 1

Code identifying party receiving transmission; codes agreed to by trading partners

Position: OTI-06 · Element: 373 · Name: Date · Type: Date (DT) · Requirement: Optional · Min: 8 · Max: 8 · Repeat: 1

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

OTI06 is the group date.

Position: OTI-07 · Element: 337 · Name: Time · Type: Time (TM) · Requirement: Optional · Min: 4 · Max: 8 · Repeat: 1

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

OTI07 is the group time.

Position: OTI-08 · Element: 28 · Name: Group Control Number · Type: Numeric (N0) · Requirement: Conditional · Min: 1 · Max: 9 · Repeat: 1

Assigned number originated and maintained by the sender

Position: OTI-09 · Element: 329 · Name: Transaction Set Control Number · Type: String (AN) · Requirement: Optional · Min: 4 · Max: 9 · Repeat: 1

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

C0908: If OTI-09 is present, then OTI-08 is required

If used, OTI09 through OTI10 will contain values from the original electronic transaction set generated by the sender.

Position: OTI-10 · Element: 143 · Name: Transaction Set Identifier Code · Type: Identifier (ID) · Requirement: Optional · Min: 3 · Max: 3 · Repeat: 1

Code uniquely identifying a Transaction Set

Position: OTI-11 · Element: 480 · Name: Version / Release / Industry Identifier Code · Type: String (AN) · Requirement: Optional · Min: 1 · Max: 12 · Repeat: 1

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

If OTI11 is present, it will contain the version/release under which the original electronic transaction was translated by the receiver.

Position: OTI-12 · Element: 353 · Name: Transaction Set Purpose Code · Type: Identifier (ID) · Requirement: Optional · Min: 2 · Max: 2 · Repeat: 1

Code identifying purpose of transaction set

OTI12 is the purpose of the original transaction set, and is used to assist in its unique identification.

Position: OTI-13 · Element: 640 · Name: Transaction Type Code · Type: Identifier (ID) · Requirement: Optional · Min: 2 · Max: 2 · Repeat: 1

Code specifying the type of transaction

OTI13 is the type of the original transaction set, and is used to assist in its unique identification.

Position: OTI-14 · Element: 346 · Name: Application Type · Type: Identifier (ID) · Requirement: Optional · Min: 2 · Max: 2 · Repeat: 1

Code identifying an application

OTI14 is the application type of the original transaction set, and is used to assist in its unique identification.

Position: OTI-15 · Element: 306 · Name: Action Code · Type: Identifier (ID) · Requirement: Optional · Min: 1 · Max: 2 · Repeat: 1

Code indicating type of action

OTI15 is the type of action indicated or requested by the original transaction set, and is used to assist in its unique identification.

Position: OTI-16 · Element: 305 · Name: Transaction Handling Code · Type: Identifier (ID) · Requirement: Optional · Min: 1 · Max: 2 · Repeat: 1

Code designating the action to be taken by all parties

OTI16 is the action requested by the original transaction set, and is used to assist in its unique identification.

Position: OTI-17 · Element: 641 · Name: Status Reason Code · Type: Identifier (ID) · Requirement: Optional · Min: 3 · Max: 3 · Repeat: 1

Code indicating the status reason

OTI17 is the status reason of the original transaction set, and is used to assist in its unique identification.