Galileo
Formats Guide
SUMMARY 
INTRODUCTION ELECTRONIC TICKETING .................... 2
Printer
Linkage.............................................................................................................. 3
BSP
Support Document Default & Reporting.......................................................... 3
Support
Document Print Table................................................................................... 4
BSP
Electronic Ticketing Table.................................................................................. 5
Booking
File Creation For An Electronic Ticket....................................................... 6
Electronic
Ticket, Itinerary And MIR Production...................................................... 9
Effects
Of Electronic Ticketing On The Booking File........................................... 10
Effects
Of Electronic Ticketing On The TINS Report............................................ 12
Unsuccessful
Electronic Ticket Request................................................................ 13
Electronic
Ticket Support Documents.................................................................... 15
Retransmission
Of Support Documents................................................................. 17
Revalidation
Of An Electronic Ticket....................................................................... 18
Automated
Refund Of An Electronic Ticket........................................................... 19
Exchange
An Electronic Ticket................................................................................. 24
Voiding
An Electronic Ticket.................................................................................... 26
Display
Of An Electronic Ticket Record.................................................................. 27
History
Of An Electronic Ticket................................................................................ 29
F Overview of the Galileo
procedure on electronic ticketing in GIS... GC*401/46
F SR/QFB group procedure on
electronic ticketing in GIS................... GC*SR/19
F BA/DI procedure on
electronic ticketing in GIS................................ GC*BA/290
Electronic
ticketing is being introduced by increasing numbers of airlines and is a method
of eliminating physical paper tickets. Alitalia (AZ), British Airways (BA),
Deutsche BA (DI), Crossair (LX), Sabena (SN), Swissair (SR), TAP Air Portugal
(TP) and United Airlines (UA) are the first airlines to offer you electronic
ticketing through the Galileo® system in the Dutch market.
Electronic
ticketing is an additional function, which is available through the Galileo
Document Production system. With electronic ticketing, instead of paper flight
coupons being issued for a passenger when a ticketing command is made, an
electronic ticket record is created in the validating carrier's database. The
passenger is then able to arrive at the airport, simply provide proof of
identity and the appropriate boarding pass will be issued.
Galileo
provides the following functionality to support electronic ticketing:
·
Production of electronic ticket records
·
Issuance of Agent and Passenger Coupons
·
Access to electronic ticket records
held within an airline's system
·
Exchange electronic tickets into
another electronic ticket or into a paper ticket
·
Revalidate electronic ticket records
·
Refund electronic ticket records
·
Void electronic ticket records
With
this brochure, we provide you the formats, which have been developed to support
electronic ticketing.
ATB Agencies
Linkage
for ATB ticketing agencies remains the same and no new special linkage is
necessary by the user.
OPTAT Agencies
Linkage
to OPTAT ticket printed devices remains the same. However support documents
must be directed to the designated itinerary printer. The linkage to the
designated itinerary printer is changed by adding an E to the normal input.
Input e.g.: HMLMC70F7EDIE
(C70F7E is GTID of the
itinerary printer.)
Linkage to
an OPTAT and designated itinerary printer is shown below.
CRT TKT DEV ST FM / ITN DEV
ST FM /
C70F61
C70F7CD U T
C70F7ED U IE
The support documents, such as agent,
passenger receipt, credit card charge form and refund notice may be produced as
required by
BSP-NL and/or the agency.
·
For OPTAT agents the support documents are printed on the agent's
designated itinerary printer.
·
For ATB agents the support documents are printed on ATB coupons and
Stock Control Numbers (SCN) are used in sequential order.
For each electronic ticket issued a
form serial number is used from the same range as with paper tickets. When an
electronic ticketing request fails, an option to revert to a paper ticket or
cancel the ticketing transaction is offered.
All stock numbers and serial numbers
used need to be reported to BSP, whereas in general no hardcopy of documents
need to be attached to the report for electronically issued tickets. Please
revert to BSP-NL documentation for reporting instructions and handling out
Legal Notices and Conditions of Contract to passenger, etc.
The
support document print table is set-up by default according the
BSP-NL requirement. Each agency will have a support document print table, which
can be displayed by all users with the entry HMET. This enables the agency to control which documents will print
which printer they will print to and the printer status.
Input: HMET
Response:
>HMET/ XF6
REQUIRED BY:
COUPON GTID
TYPE BSP AGENCY
STATUS PRINT NOW
AGENT CPN C2979B ITN
Y Y U
Y
PSGR RCPT C2979B ITN
O Y U
Y
CHG FORM C2979B
ITN Y Y
U Y
¦ ¦ ¦ ¦ ¦ ¦ ¦
1 2 3 4 5 6 7
1.
List of support documents (only
those which BSP designates as mandatory or optional are displayed)
2.
GTID to which each document is
printed
3.
Form type of printer
For ATB agents this will be TKT (designated ATB printer)
For OPTAT agents it will be ITN (designated itinerary printer)
4.
BSP print option for each
document as Y (required) or O (optional)
5.
Agency print option for each
document is set to Y as required by BSP and/or the airline.
6.
Status of printer U (up) or D
(down)
7.
Default is set as Y to print
documents at TKP
A
BSP table is set up by Galileo for each BSP. This determines the electronic
ticket types supported by BSP and which electronic support documents are
required by BSP.
The
electronic ticket table provides one source of display to determine what
airlines offer electronic ticketing through Galileo and what their default is.
Input: CGET
Response:
ELECTRONIC TICKETING - 009 NL ï 1
TKT TYPES ï 2
ATB - Y
OPTAT - Y
DOCUMENT
TYPES
AUD - N AGT - Y PAX - O
UCF - Y EXC - N REF – N ï 3
DEFAULT KEY: P-PAPER TKT E-ELECTRONIC TKT
CARRIERS DEFAULT POSACK ELIGIBLE
AZ
P Y N
BA P Y
N
LX P
N N
SN P
N N
SR
P N N
TP P
N N
UA P
Y N
¦ ¦ ¦ ¦
4 5 6 7
ï 1 BSP
country indicator 009 and NL
ï 2 Supported
electronic ticket types
ï 3 Electronic
ticketing support documents types available
4
Participating carriers
5
Ticketing default P (paper) E
(electronic)
6
Positive acknowledgement from
the airline required if set to Y
7
If carrier requires validation
of eligibility of segments prior to ticketing this is set to Y otherwise N
The airlines that participate in
electronic ticketing on Galileo may respond with an 'E' indicator if the sold segment is eligible for electronic
ticketing. All of the segments to be ticketed electronically must be eligible,
whereas they must not necessarily show the 'E' indicator as this is subject to carriers own definition.
Initial Sell
response
1. SN 2402 C
23MAR AMSBRU HS1 0810 0855
O E FR
*NON SMOKING FLIGHT*
……
Retrieved Booking
File
M9CG0Y/JJ AMSNH
N007022 AG 81237995 13JAN
1.1SMITH/JOHNMR
1. SN 2402 C
23MAR AMSBRU HK1 0810 0855
O* E FR
** VENDOR LOCATOR DATA EXISTS ** >*VL
FONE-AMST*023 5675333 GALILEO
TESTBOEKING
TKTG-T*
The 'E' indicator is also shown on
the carrier specific timetable:
TTSN2402/23MAR
|
SN 2402 FRIDAY
23 MAR 01
--------------------------------------------------------------
BRD TIME T D/I
OFF TIME T D/I FLY/GROUND EQP
E
AMS 0810
I BRU 0855 I
:45 321 E
--------------------------------------------------------------
TOTAL FLYING TIME AMS - BRU :45
--------------------------------------------------------------
CLASSES
AMS-BRU J C
D Y M
L H K
B V
|
Name Field &
Mileage Membership
In order to assist airlines systems to
automatically identify the booking it is strongly recommended that the Booking
File name field contains the passengers full
first name.
In
all cases where a Frequent Flyer/Mileage Membership number is entered, the name
must match the name on the card.
This practice will greatly assist
passengers who check in at self-service check-in machines and/or who are using
a Frequent Flyer/Mileage Membership card as the means of identification.
SSR FOID
With the input of a SSR FOID (Form Of
IDentification) an ID may be added as identification at the airport. This is
particularly recommended if the identification the passenger wishes to use
differs from the data in the Booking File; e.g. form of payment is a company CC
and passenger uses personal CC as ID.
SI.P1/SSRFOIDBAHK1/CC375811111111115
Passenger 1 will use credit card as
form of ID for airport identification
Before requesting
an electronic ticket, the following should be checked:
1.
A vendor locator has been
returned to the Booking File (see *VL).
2.
All booked segments to be
ticketed either show an E indicator or are eligible for electronic ticketing.
3. The fare quote is based on eligible segments for the respective
plating/validating carrier.
Notes:
·
Claim PNRs may not have the E indicator
but the flights may be eligible for electronic ticketing
·
Passive segments will not have
the E indicator but may be eligible for electronic ticketing.
·
OPEN and waitlisted segments
will not show an E but may also be eligible for electronic ticketing (no YY
possible)
·
Within the same fare quote a
maximum of four (4) segments incl. ARUNK and eight (8) passenger are selected.
Refer to the individual carrier
briefing for details on the determination of eligible flights.
TKPET Create
electronic ticket, print itinerary (if linked), issue MIR (if linked) and print
support documents from retrieved BF for all passengers on all segments.
TKP1P2/ET Create
electronic ticket, print itinerary (if linked), issue MIR (if linked) and print
support documents using filed fare number 1 for passenger number 2.
Ticket Modifiers
The ticket modifier ET may be used in
random order in association with the ticket modifier entry. Refer to DOCS 7 –
10 of your Formats Guide for a full list of ticket modifier formats.
e.g. TMU1ET Add
electronic ticket modifier to filed fare number 1.
Notes:
·
If the carriers default is set
to paper (see HMET display), you must use the electronic ticket modifier ET to request an electronic ticket.
·
If the carriers default is set
to electronic, no additional formats are required to request an electronic
ticket. If a paper ticket is required instead of an electronic ticket, the
modifier PT must be used.
At TKP, Galileo checks that the segment(s),
ticket type and carrier(s) are applicable for the request, and the plating
carrier in the request matches the (interline) carrier code of all segments
held in the filed fare requested for ticketing. If all checks are positive, an
electronic ticket number is assigned from the TINS table and the request is
sent by a link to the plating/validating carrier’s internal electronic
ticketing database.
If the request is accepted by the carrier,
an electronic ticket record is created and the following response is returned.
ELECTRONIC TKT GENERATED TTL
FARE EUR 460.50
SUPPORTING DOCUMENTS GENERATED
RECORD
LOCATOR: M9CG0Y
-------------------------------------
On retrieval of the Booking File, the fact
that an electronic ticket has been generated is reflected in the following
places:
·
The face of the Booking File
·
Filed Fare
·
History
Face Of The Booking File
M9CG0Y/JJ AMSNH
N007022 AG 81237995 13JAN
1.1SMITH/JOHNMR
1. SN
2402 C 23MAR AMSBRU HK1 0810
0855 O* E FR
** FILED FARE DATA EXISTS ** >*FF
** VENDOR LOCATOR DATA EXISTS ** >*VL
** SERVICE
INFORMATION EXISTS ** >*SI
** TINS REMARKS
EXIST ** >*HTI
** ELECTRONIC
DATA EXISTS ** >*HTE
FONE-AMST*023 5675333 GALILEO
TESTBOEKING
TKTG-T*AMS 13SEP1632Z
JJ AG
Tabbing to the prompt >*HTE, displays the electronic ticket record held in the
validating carriers internal electronic ticketing database.
Sample *HTE Display:
TKT: 082 1641 108382 NAME: SMITH/JOHNMR
ISSUED: 13JAN01 FOP:CASH
PSEUDO: 0XF6 PLATING CARRIER: SN ISO: NL
IATA: 88888881
USE CR FLT CLS
DATE BRDOFF TIME ST F/B FARE
CPN
OPEN SN 2402 C 23MAR AMSBRU 0810 OK Y 1
FARE: EUR 426.00 TAX:
9.50 NL TAX: 24.00 RN TAX:
1.00VV
TOTAL: EUR 460.50
AMS SN(EH)BRU M170.70Y NUC 170.70 END ROE2.495587
The electronic ticket record for a credit
card transaction shows the credit card number and the approval code in FOP
(Form Of Payment) box.
In a multiple-passenger Booking File, *HTE produces a ticket record name
list.
ELECTRONIC
TICKET LIST BY *HTE
NAME TICKET NUMBER
>*TE001
HUIGEN/AMR 0821641491022
>*TE002
DEJONG/FMR 0821641491023
END OF
LIST
Tabbing to the relevant prompt accesses the
electronic ticket record for each passenger. Alternatively the input i.e. *TE1 may be used from anywhere within
the Booking File to access the appropriate electronic ticket record.
Filed Fare
In the filed fare, an E following the fare
status codes as shown below indicates the generation of an electronic ticket.
FQ1 - S1 AP
13JAN01 JJ/AG
P1 SMITH/JOHNMR G E 0821641108382
History
In the *HTI history display, ET indicates
the generation of an electronic ticket.
** NO
HISTORY TIN DATA **
**
CURRENT TIN DATA **
SMITH/JOHNMR-/0821641108382/-EUR/460.50/ET
