E-Ticket Content In Details

Most data displayed in E-Ticket becomes transferred from a PNR (see for details: PNR Data). Please look at described examples below.

Read also: E-Ticket Templates and PNR Data.

The date when corresponding air file was created.

PNR number in a reservation system (Amadeus, WorldSpan, Sabre, Galileo, etc.).

Internal airline system's flight segment booking number. There can be several airline codes when segments are operated by different airlines.

Example

Note
The only record for the first airline is shown when airline references are the same.

Example

Ticketing carrier name.

Passenger's First and Last names, Title, Type.

Examples

Also
Oversized or passenger, needing additional space, gets the word IDEXST added in the name.

Example

Operating carrier (shown as ‘Carrier Code’ in Order).

Usually Arrival and Departure flight dates are equal, that is why only Departure date is displayed in E-Ticket. But when the dates are different 'Arr.' becomes displayed as '+1'.

Note

1. Both Departure and Arrival dates are written in Amadeus:
and WorldSpan airfiles:

But in Sabre airfiles there is departure date only:


'+1' in E-Ticket is defined by rules:

in Sabre
when arrival time earlier than departure time
and flight time > 3 hours,
then the date is 'departure date + 1', i. e. the next day.
For example, here, 30DEC - Departure date, 1120 - Departure time, 0605 - Arrival time, 11.45 - Elapsed Flying Time)

2. OPEN segments (flight date has not been determined yet):

Departure date, but no Arrival date:



Nor Departure, nor Arrival date. In this case the word OPEN is dispalyed instead of dates:

Specified for each flight segment.

In Amadeus and WorldSpan PNRs are written in flight segments’ lines:

In Sabre are written in a separate line:

Note
When there are various passenger types in the same PNR (may occur in WorldSpan or Sabre, not Amadeus) then:
- Baggage restrictions for CHD and ADT are the same;
- Baggage restrictions for INF = 10K.

Example
(2 ADT + CHD+ INF are in a WS file)

In E-Ticket:
- Baggage restrictions for CHD = 30K; Status = OK;
- Baggage restrictions for INF = 10K; Status = NS.

Airline code and ticket number are shown.

Determined based on PNR text by the following logics:

Example

Airline's fare rules. Fare codes start with a letter followed by optional letters and digits.
In a PNR text farebasises are listed in M-line for each segment but in E-Ticket only different Farebasises become displayed.

Example

Specific agreement with an airline. Mostly becomes inserted by CRS (Amadeus or WorldSpan) if we can auto price the PNR; can also be inserted manually.

Examples

Amadeus:

WorldSpan:

Sabre:

Price paid for the ticket to GDS.
By default this price is hidden in E-Ticket : the word ‘NETT’ is shown in Fare and Total lines:

But if you check 'Show Fare prices in E-Ticket' in Invoice form, then prices from PNR become shown:

Examples

Amadeus:

NOTE: Total = Fare + Taxes

Worlspan

Sabre

Taxes list.

Examples

Amadeus:

Note (for WorldSpan and Sabre)
if there are more than 3 taxes then they are not written in one line – the rest taxes beside two are collected under XT tax. XT tax is broken into separate codes/amounts in specific lines.

Examples

WorldSpan:

Sabre:

• E-Ticket is created for EMD (TW loads tickets by pnrsegmentpassengerTravelDoc table and thus not loading ticket related to PNR only.
• Free text is taken from MCORemark field in 'Tax/Fee/Charge' section. It states 'PRE RESERVED SEAT ASSIGNMENT'.

Note

• EMD tickets are not linked to the segments, but directly to PNR.
• Text in invoice line for EMD has no routing, looks like: 'PRE RESERVED SEAT ASSIGNMENT'.

If some taxes are paid already (it often happens for reissued tickets), then these taxes are shown with ‘PD’ letters.

Example

WorldSpan: (PAID taxes come in X-line instead of G-line, XT tax is displayed as one)

A tax can be registrated both as paid and unpaid.

Example

Sabre

Amadeus (O indicates that the tax is paid):

Airline's set of rules for a specific price. Can be descriptive telling about change rules and refunds or laconical. In auto priced ticket it gets always defined by the system (according to what the airline wants to have), in manual ticket it becomes set according to the contracts.

Examples

Amadeus:

WorlSpan:

Sabre:

If a current ticket (075-3789556194-195 on screenshot below) is a REISSUE ticket and if we know which ticket it has been issued instead (075-2096868407-08) then it becomes displayed in ‘Original E-Ticket’ field in E-Ticket:

'Old' ticket number:

Amadeus:

WorlSpan:

where 6929279331332 is a new (reissued) ticket and 1609061120571 is an “old” ticket

Sabre:

where 1756220484 is a new (reissued) ticket

Reference number is taken from OURREF and OURPAXREF parameters. OURPAXREF has higher priority compared to OURREF.

Examples

Amadeus:

WorldSpan: