TicketIssue request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

NodeDescriptionValuesOccursExample
<TicketIssueRQ>
1
@Version
Version number.
0..1 2.0
@ReValidate
If 'Y', revalidates the Fares before Issuing a Ticket, otherwise ignore.
Default: N.
0..1
@RePrice
Automatically re-price the itinerary in case the stored fare should not be valid any more.
Possible values: Y, N
Default: N
0..1
<FlightReq>
1
<TktFlight>
Flight to be ticketed.1..16
@Element
PNR flight element number. 1 1
</TktFlight>
</FlightReq>
<TravelerReq>
1
<TktTraveler>
1..N
@Element
PNR traveler element number.1 1
@ManualPricingInd
In case of a manual fare, fare validation will not succeed and is omitted / the system response is ignored and ticket issued anyway.
Possible values: Y / N.
0..1 N.
<TktFlight>
Flight to be ticketed. If ommited, request applies to all flights for the traveler.0..16
@Element
PNR flight element number. 1 1
</TktFlight>
</TktTraveler>
</TravelerReq>
<ExchangeReq>
1
@Source
Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. 0..1 1A, 1V, or other.
<TktExchangeRequest>
1
@ExchangeReqNumber
The number of the exchange request to be ticketed as returned by TicketExchangeRS1
</TktExchangeRequest>
</ExchangeReq>
<StoredFareReq>
1
<TktStoredFare>
1
@FareNumber
Number of FareGroup in PNR to be used for ticketing. 1 2
<TktTraveler>
In case the stored fare does not distinctly reference the travelers priced, but only the travelertypes, the travelers to be ticketed can be specified.
If in this case this element is omitted, attempt to ticket all travelers in the PNR will be made.

Currently only supported in WorldspanDIR.
0..N
@Element
PNR traveler element number.1 1
@ManualPricingInd
In case of a manual fare, fare validation will not succeed and is omitted / the system response is ignored and ticket issued anyway.
Possible values: Y / N.
0..1 N.
<TktFlight>
Flight to be ticketed. If ommited, request applies to all flights for the traveler.0..16
@Element
PNR flight element number. 1 1
</TktFlight>
</TktTraveler>
</TktStoredFare>
</StoredFareReq>
<InExchangeFor>
IMPORTANT: currently only supported in Sabre, Abacus - BSP markets only. Only from a PhaseIV.


Instant exchange - assumes all preparation is done all fare information/pricing is stored in PNR and PNR is ready to be used for reissue.
1
<Ticket>
Data of the ticket that is to be exchanged. In case of a conjunctive ticket, all ticket numbers must be supplied with the coupon numbers that are to be exchanged/refunded.
Sabre automatically exchanges all unused coupons.
1..4
@Number
13-digit ticket or document number that you are exchanging. This includes the three-digit airline code and document number as frist 3 digits.
1 0012345467891
<CouponNumber/>
The number of the coupoun to be exchanged.
1..4 1
</Ticket>
<TktStoredFare>
1
@FareNumber
Number of FareGroup in PNR to be used for ticketing. 1 2
@ManualPricingInd
In case of a manual fare, fare validation will not succeed and is omitted / the system response is ignored and ticket issued anyway.
Possible values: Y / N.
0..1 N.
</TktStoredFare>
<TktTraveler>
If you have more than one person in the Passenger Name Record (PNR) you must name select. 1..9
@Element
PNR traveler element number.1 1
</TktTraveler>
<IATA/>
The IATA number of the agency originally issuing the ticket.1
<TktIssueDate/>
Date in ISO 8601 format (yyyy-mm-dd). 1 2001-12-25
<OriginalIssuePlace/>
Three letter IATA code of the town where the ticket originally has been issued.
1 MIA
<FormOfPayment>
Form of payment of the original ticket being exchanged.1
<CreditCard>
0..N
@PartialAmount
(Partial) Amount allocated to this FOP in case of a split payment. 0..1 75000
<CCCode/>
Credit card code. 1 VI
<CCNumber/>
Credit card number. 1 4011236654652341 Can be returned encrypted by GDS/CRS. Example: XXXXXXXXXXXXXXXX
<CCExpiration>
Credit card expiration group1
<Month/>
Credit card expiration month. 1 02 Can be returned encrypted by GDS/CRS. Example: XX
<Year/>
Last two digits of the credit card expiration year. 1 06 Can be returned encrypted by GDS/CRS. Example: XX
</CCExpiration>
</CreditCard>
<Other>
Other payment information. 0..N Check 113 or *CHECK, CASH
@PartialAmount
(Partial) Amount allocated to this FOP in case of a split payment. 0..1 75000
</Other>
</FormOfPayment>
</InExchangeFor>
<RecordLocator/>
The record locator of the PNR for which the ticket(s) are to be issued.
1 XQ23AX
<QualifierGroup>
Data sent in the QualifierGroup supplements or overwrites the content of the PNR, depending on the PNR already containing the respective data or not.0..1
<Commission>
0..1
@Type
Commission type. Values are: P = Percent, A = Amount 1 A
@NumberOfDecimals
Number of decimals for amount value.0..1
</Commission>
<ValidatingCarrier/>
0..1
<FormOfPayment>
Form of Payment Group

Multiple form of payments supported by Sabre and Galileo:

Sabre:
In order to add two forms of payments in your ticketing entry:
- You must be a BSP location.
- Your location must have the two forms of payment indicator active in the
validating carrier table. Only one FOP may be credit card. Note: Sabre does not
accept two credit cards.
- Your location must have the indicator "two forms of payment" active in your
Travel Journal Record (TJR).

Galileo:
- up to 3 form of payments can be added for BSP locations.
0..N
<CreditCard>
1
<CCCode/>
Credit card code. 1 VI
<CCNumber/>
Credit card number. 1 4011236654652341 Can be returned encrypted by GDS/CRS. Example: XXXXXXXXXXXXXXXX
<CCExpiration>
Credit card expiration group1
<Month/>
Credit card expiration month. 1 02 Can be returned encrypted by GDS/CRS. Example: XX
<Year/>
Last two digits of the credit card expiration year. 1 06 Can be returned encrypted by GDS/CRS. Example: XX
</CCExpiration>
<ApprovalCode/>
Credit card approval code. 0..1 996456
</CreditCard>
<Other/>
Other payment information. 1 CHECK, CASH
<Amount>
Sabre:
For second form of payment an amount must be specified. Remaining amount is automatically taken from first form of payment.

Galileo:
For all form of payment an amount must be specified. The sum of amounts of all form of payments must match the price of the ticket.
0..1
@CurrencyCode
Currency code.
1 USD
@NumberOfDecimals
Number of decimals for amount value.1
</Amount>
<Tax>
Sabre supports up to two taxes that can optionally be specified for second form of payment.0..N
@CurrencyCode
Currency code.
1 USD
@NumberOfDecimals
Number of decimals for tax value.1
@Designator
Tax designator.
1 US
</Tax>
</FormOfPayment>
</QualifierGroup>
<DocumentGroup>
If not specified, the GDS specific standard documents are issued.
On Apollo that are: MIR, Itinerary, Ticket, BoardingPass (if possible).
0..1
<Invoice/>
If 'Y', prints Invoice (MIR in Apollo / Galileo) only. Values are: Y = Yes, N = No. [Y] [N] 0..1
<Itinerary/>
If 'Y', prints Itinerary only. Values are: Y = Yes, N = No. [Y] [N] 0..1
<MiniItinerary/>
If 'Y', prints Mini Itinerary only.
TEMP NOTE: according to doc, galileo only supports either or
[Y] [N] 0..1
</DocumentGroup>
<PrinterGroup>
The PrinterGroup specifies the printer(s) to print to.

NOTE: The PrinterGroup is mandatory for all GDS, although it may not be required on other CRS!
0..1
<PrinterDestination>
Documents are printed on this destination. If not given, the default printer is used.
1..5
@Type
The type of printer.

Values:
B .. boarding pass
I .. invoice / itinerary
M .. mini itinerary
T .. ticket printer
H .. hardcopy / accounting printer
PP .. PrinterProfile (Sabre only)

[B] [I] [M] [T] [H] [PP] 1 T
@CountryCode
The ticket printer country code. Needed by Sabre.

0..1 AB
</PrinterDestination>
<STPDestination>
Documents are printed on this STP (Satellite Ticket Printer, means printer located in a different office location) destination.
If not given, then default printer is used.
0..1
@Type
The type of printer.

Values:
B .. boarding pass
I .. invoice / itinerary
M .. mini itinerary
T .. ticket printer
H .. hardcopy / accounting printer

1 T
<AccountID/>
Needed for Sabre1
<PseudoCityCode/>
Agency's pseudo city code. 1 LNJ2
<STPID/>
The printer desination ID (LNIATA in Apollo / Galileo)1
</STPDestination>
</PrinterGroup>
</TicketIssueRQ>

Legend

ColumnDescription
NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server