A tour number that may be printed on the ticket or override an existing tour number in the PNR.
When true, indicates the message is being re-sent after a failure. It is recommended that this attribute is used (i.e., set to TRUE) only when a message is retransmitted.
URL that identifies the location associated with the record identified by the UniqueID.
The ticket designator code for the discount.
Provides a pricing instruction number to be used for pricing the itinerary at the time of issuing the ticket.
Indicates the number of decimal places for a particular currency. This is equivalent to the ISO 4217 standard "minor unit". Typically used when the amount provided includes the minor unit of currency without a decimal point (e.g., USD 8500 needs DecimalPlaces="2" to represent $85).
An identifier specifying the queue on which the booking file resides in the system.
Used to identify the source of the identifier (e.g., IATA, ABTA).
An additional identifier to determine the exact queue on which a reservation record should be placed
The division name or ID with which the contact is associated.
The PNR record locator for which a ticket is requested.
The category of the queue.
Specifies the purpose of the trip, i.e., business, personal. Refer to OTA Code List Travel Purpose (TVP).
When true, the fare stored in the booking record should be used instead of any stored pricing instructions.
A container of document instructions.
A placeholder in the schema to allow for additional elements and attributes to be included if required, per Trading Partner Agreement (TPA).
When true, a bulk ticket applies.
A unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction).
Information to specify the queue on which a PNR should be placed after the ticket is isssued.
Used to provide the company common name.
The identification of a record as it exists at a point in time. An instance is used in update messages where the sender must assure the server that the update sent refers to the most recent modification level of the object being updated.
Encoded data relating to the fare agreement with the airline.
A unique identifying value assigned by the creating system. The ID attribute may be used to reference a primary-key value within a database or in a particular implementation.
The code specifying a monetary unit. Use ISO 4217, three alpha code.
Provides a ticketing record number to be used in the ticketing of the itinerary.
A reference to the type of object defined by the UniqueID element. Refer to OTA Code List Unique ID Type (UIT).
Specifies the type of amount being sent.
Indicates the creation date and time of the message in UTC using the following format specified by ISO 8601; YYYY-MM-DDThh:mm:ssZ with time values using the 24 hour clock (e.g. 20 November 2003, 1:59:38 pm UTC becomes 2003-11-20T13:59:38Z).
The department name or ID with which the contact is associated.
Identifies the airline and/or system where the queue resides. If this is omitted, the airline and/or system code (AirlineVendorID) contained in the point of sale information should be used.
A reference for additional message identification, assigned by the requesting host system. When a request message includes an echo token the corresponding response message MUST include an echo token with an identical value.
Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes.
Specifies the information necessary for the issuer of the ticket to issue the ticket.
An instruction for pricing the itinerary at the time of issuing a ticket.
The destination code for the itinerary. Required for Canada and Bermuda BSP's.
When true, use the primary stored document instruction in ticketing.
Identifies a company by the company code.
A number specifying a range of days (e.g., today plus 3, today plus 6) for the queue on which the PNR is to be placed.
Refer to OTA Code List Travel Sector (TVS).
When true, the stored document instructions should not be used in ticketing.
The dollar amount or percentage of discount that should be applied.
Identifies the context of the identifying code, such as DUNS, IATA or internal code, etc.
Used to indicate whether the request is for the Test or Production system.
Used to identify the sequence number of the transaction as assigned by the sending system; allows for an application to process messages in a certain order or to request a resynchronization of messages in the event that a system has been off-line and needs to retrieve messages that were missed.
The information needed when a passenger presents a discount/promotional coupon for a dollar/percentage of the fare or when a passenger qualifies for a percentage discount such as a senior discount.
The month and day of the queue on which the PNR is to be placed.
This indicates where this message falls within a sequence of messages.
For all OTA versioned messages, the version of the message is indicated by a decimal value.
Used to specify the carrier agreement code, also known as a contract code.
Identifies the company that is associated with the UniqueID.
Identifes the primary language preference for the message. The human language is identified by ISO 639 codes.
Provides the capability of requesting that a company responsible for ticket fulfillment, such as a GDS, issue an electronic ticket and/or automated miscellaneous charge order (MCO). The ticket fulfillment company would then issue the ticket using the current EDIFACT message.
When true, all ticket numbers should be returned.
The agency information to be printed on the printed itinerary and/or invoice.
The ATA/IATA airport/city code, office code, pseudo city code, etc. of the queue.