Electronic Ticketing Formats Guide

Galileo
Electronic Ticketing
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
 Overview of the Galileo procedure on electronic ticketing in GIS........GC*401/46

 SR/QFB group procedure on electronic ticketing in GIS........................GC*SR/19
 BA/DI procedure on electronic ticketing in GIS.....................................GC*BA/290
INTRODUCTION ELECTRONIC TICKETING
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.
ET 2 Galileo Formats January 2001

Printer Linkage
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
BSP Support Document Default & Reporting

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.
Galileo Formats January 2001 ET 3

Support Document Print Table

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

BSP Electronic Ticketing Table

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

Booking File Creation For An Electronic Ticket
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.

Electronic Ticket, Itinerary And MIR Production

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
-------------------------------------

Effects Of Electronic Ticketing On The Booking File

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

Effects Of Electronic Ticketing On The TINS Report
On the TINS report, an electronic ticket is identified by an E following the

airline code. The same form serial numbers are allocated as used for paper
tickets as shown in HMTN/D display.
Example of the TINS report for an OPTAT agency:
GALILEO NEDERLAND TESTROOM TINS REPORT 13 JAN 01

CURRENCY CODE EUR IATA NUMBER 88888881
A/L TKT/STOCK NBR PASSENGER NAME FARE TAX COMM FOP

125E1677108335 ELECTRONIC/AMR 860.00 15.50 9.00 CCC/AX
001 1677108338 PAPER/LOUISMR 1165.00 20.50 9.00 CASH
8411167014
085P1677108336 RABBIT/JOSYMRS 1646.00 82.00 9.00 CASH
8411167013
125E1677108337 SMITH/JOHNMR VOID 13SEP
|
E Electronic ticket type indicator
P Electronic ticket request, reverted to paper
Blank indicates a paper ticket was requested
On the report above, Mr Electronic's ticket is an electronic one. Mr

Paper’s ticket is a paper ticket. An electronic ticket was attempted for
Mrs Rabbit, but there was a failure and the ticket therefore reverted to a
paper one. There was also a failure for Mr Smith, whereas the
electronic ticketing transaction was cancelled. As the ticket number had
already been taken from the ticket number stock, this ticket number is
automatically marked as VOID on the TINS report.
For ATB agents the TINS will be identical with above display, except that
also the stock coupons numbers used for electronic tickets will be listed.
Example of the TINS report for an ATB agency:
A/L TKT/STOCK NBR PASSENGER NAME FARE TAX COMM FOP

085E9900102605 ELECTRONIC/AMR 1465.00 86.50 7.00 CCC/AX
9493952347-349
160 9900102606 PAPER/ALEXMR 3169.00 26.00 7.00 INV
9493952350-354
125P9900102607 RABBIT/JOSYMRS 1003.00 15.50 9.00 INV
9493952355-358
082E9900102608 SMITH/JOHNMR VOID 13SEP

Unsuccessful Electronic Ticket Request

If an electronic ticket request is not successful, the following error
responses are returned.
Galileo Error Responses
ELECTRONIC TICKETING IS NOT AUTHORISED FOR YOUR AGENCY

ELECTRONIC TICKETING NOT AUTHORISED FOR BSP REGION
ELECTRONIC TICKETING NOT AUTHORISED FOR TICKET TYPE
ELECTRONIC TICKETING IS NOT AVAILABLE FOR YY
(where YY is the plating carrier in the ticket request input)
ITINERARY/PLATING CARRIER MISMATCH
Airline Error Responses
If the correct input is made, and Galileo’s initial checks as above are
successful, the electronic ticketing request will be sent by a link to the
validating carrier’s internal electronic ticketing database. Each participating
carrier will determine acceptance or rejection of the request based on their
own criteria. For example, individual airlines may choose to limit the
number of segments they will accept for electronic ticketing and will reject a
request that contains more than their maximum. Similarly, an airline may
reject a request, which contains an open (YY) segment.
If an electronic ticketing request is rejected, an error response is returned
advising why the request failed. The response provides 3 tab stops to
choose if a paper ticket should be issued instead (either to the host agency
or Satellite Ticket Printer as appropriate) or if the ticketing request should
be cancelled.
Sample Error Response:

>*ET
ELECTRONIC TICKETING FAILED
ITINERARY NOT VALID FOR ETKT
TAB AND ENTER TO SELECT OPTION
ISSUE PAPER TICKET TO HOST . TO STP ........
CANCEL TICKETING TRANSACTION .
One of the option must be selected by tabbing to the appropriate prompt

and entering X or the STP IATA number and >ENTER<.

If the option to print a paper ticket is used, the response is the normal ticket
issuance response. This is reported on TINS report by the printed letter P.
If the option to cancel the ticketing request is selected, the response is as

below and the Booking File is end-transacted.
ELECTRONIC TICKETING TRANSACTION CANCELLED

RECORD LOCATOR: 3UE8XG
This is recorded on TINS report by a VOID for the allocated ticket number.
Link Errors
If there are problems with the link to the carrier, the following error
response will be returned.
TICKETING LINK UNAVAILABLE – PLEASE RETRY
Credit Card Authorisation Errors
If a credit card is used as the form of payment for an electronic ticket, the
authorisation request is sent out to the credit card company after Galileo
has made its initial checks, but before the request is sent to the carrier. If a
credit card error response is returned, the ticket request is not sent to the
carrier. You must take the usual action according to the error message. If
manual authorisation is later obtained, this may be input to the Booking File
and a request for electronic ticketing must be repeated.

Electronic Ticket Support Documents

For ATB users the agency, passenger, audit and UCCCF documents will
print in the normal format with the addition of ETKT at the left top corner.
The documents for refunds will print in the same format on your designated
itinerary printer on plain paper.
For OPTAT user all documents will print on your designated itinerary
printer on plain paper and the agent coupon, passenger receipt and
UCCCF have a new format.
Sample of OPTAT Agent Coupon:
ETKT **AGENT COUPON** 88888881 **ITINERARY**

SABENA BELGIAN WORLD A/L 1 OF 1 MD6BHY/1G SN2401C AMSBRU 23MAR
SMITH/JOHNMR Y
13JAN01

EUR 426.00
9.50NL CASH
24.00RN
1.00VV
EUR 460.50
082 1641108378 1 FVVV
7733/ EUR/426.00/-------/ 7.00/ 34.50
Sample of OPTAT Credit Card Charge Form (UCCCF):
ETKT CREDIT CARD CHARGE FORM

SABENA BELGIAN WORLD A/L AMS/BRU SITI GALILEO NEDERLAND TESTROOM
13JAN01 JA HOOFDDORP
88888881 MD6BHY/1G
SMITH/JOHNMR
SIGNATURE X-
I ACKNOWLEDGE RECEIPT OF TICKET(S) AND/OR COUPON(S) FOR RELATED
CHARGES DESCRIBED HEREON AND AM AWARE OF APPLICABLE RESTRICTIONS
AND/OR PENALTIES AS SHOWN ON SUCH TICKET(S) AND/OR COUPON(S)
EUR 426.00
EUR 9.50NL 24.00RN 1.00VV

AX375301500101000 APVL 19294
EUR 460.50 7733/ 082 1641108378 1

Sample of OPTAT Passenger Receipt:
THIS RECEIPT MAY BE REQUIRED AT CHECK-IN AND MUST BE

PRESENTED TO CUSTOMS AND IMMIGRATION IF REQUESTED
NAME: SMITH/JOHNMR ETKT ITINERARY/RECEIPT

GALILEO NEDERLAND TESTROOM 13JAN01
TICKET NO. 082 1641108378 PLACE OF ISSUE: JA HOOFDDORP / NL
ISSUED BY: SABENA BELGIAN WORLD
FARE TAX TAX TAX TOTAL
EUR 426.00 9.50NL 24.00RN 1.00VV EUR 560.50
FORM OF PAYMENT: CASH
CARRIAGE AND OTHER SERVICES PROVIDED BY THE CARRIER ARE

SUBJECT TO CONDITIONS OF CARRIAGE WHICH ARE HEREBY
INCORPORATED BY REFERENCE. THESE CONDITIONS MAY BE
OBTAINED FROM THE ISSUING CARRIER
NOTICE
IF THE PASSENGERS JOURNEY INVOLVES AN ULTIMATE DESTINATION
OR STOP IN A COUNTRY OTHER THAN THE COUNTRY OF DEPARTURE THE
WARSAW CONVENTION MAY BE APPLICABLE AND THE CONVENTION
GOVERNS AND IN MOST CASES LIMITS THE LIABILITY OF CARRIERS
FOR DEATH OR PERSONAL INJURY AND IN RESPECT OF LOSS OF OR
DAMAGE TO BAGGAGE.
CR FLT DATE FROM TO DEP ST CL BG NVB NVA

SN 2402 23MAR AMSTERDAM/ AMS BRUSSELS/ BRU 0810 OK C 30K
On the ATB coupons, the notice is pre-printed on the back of each coupon.

Retransmission Of Support Documents

The normal Fallback and Recovery does apply for electronic tickets. The
HQC does display additionally allocated support documents for electronic
ticketing.
Input: HQC
Response (sample):
DEMAND TOTAL NEXT SEQ
PENDING SENT NUMBER
DOCUMENTS
TKT-OPTAT 0 0 00974
ITN-ITIN 0 0 01313
ACC-MIR 0 0 01068
SUPPORTING PRINT DEMAND TOTAL
DOCUMENTS LATER PENDING SENT
AGT 0 0 1
REC 0 0 0
UCF 0 0 0
Print All Support Documents
If retransmission of all support documents connected with an electronic

ticket is required, a reprint request may be made to the carrier. The input
includes the airline 3 digit code, the ticket number and the check digit.
Input: TSD08516771083851
Note: The document prints with actual date.
Print Selected Support Documents
If only some documents require retransmission (e.g. passenger receipt),

the individual image in the support documents sent buffer may be
displayed.
Sample Input: HQB/REC/DS
If necessary it is possible to move through the buffer with the normal inputs
HQB/MU, HQB/MD, HQB/MD5 etc. The image may then be retransmitted
with the normal retransmission input.
Input: HQNN repeat HQNN after the warning message
Note: Selected retransmission is only possible on the day of issue.

Revalidation Of An Electronic Ticket

Revalidation requests may be made for an electronic ticket following the
tariff and IATA regulations (i.e. same carrier, same routing, etc.) It is not
possible to revalidate past date segments or from a definite flight to an
open segment.
Procedure:
1. Any flight no longer required must be cancelled and the required one
booked in the normal way either in the original or in a new Booking File.
The Booking File must then be end-transacted and redisplayed. It is not
necessary to have a filed fare in the Booking File for revalidation.
2. Only coupons with status OPEN in the electronic ticket record can be
revalidated.
Before revalidation, the electronic ticket record shows the old flight
reservation.
TKT: 082 1677 108371 NAME: SMITH/JOHNMR
ISSUED: 13JAN01 FOP:CASH

PSEUDO: 0XF6 PLATING CARRIER: SN ISO: NL IATA: 88888881
OPEN SN 2402 C 23MAR AMSBRU 0810 OK Y 1

TOTAL: EUR 460.50
3. Revalidate each segment with the appropriate entry to make sure the
passenger can check-in for the new desired flight without any delay.
Input e.g.: TKRETS1/TN0821677108371/C1

Revalidate segment number 1 quoting ticket number
and coupon to be revalidated.
TKRETS2/TNIN0851672108385/C2
To revalidate an infant ticket IN is added after TN.
Response: ELECTRONIC TICKET REVALIDATED
Notes:
• If the electronic ticket record is redisplayed, the new flight is shown.
• If multiple segments require revalidation, they must be done one at a
time.

Automated Refund Of An Electronic Ticket

When a refund request is made, the airline returns data in the form of a fill-
in-format. This fill-in-format can be requested and completed by the issuing
agent. When the final ENTER is made, a refund message is sent to the
airline who may accept or reject it. Please mind that the airline does not
make any verification on the tariff rules or the refund amount. Do enter the
correct data is the agents responsibility.
Input: TRNE08516771083884/20AUG00
Refund electronic ticket number, to include 3 digit airline
code, electronic ticket number with check digit and date
ticket was issued.
Response Refund Screen 1:

>*TRN1 PAGE 1 OF 4
DATE OF REFUND: 13JAN01 ORIGINAL COMM RATE 7.00 CURRENCY EUR
ISSUE DATE OF REFUNDED DOC 08DEC00 AIRLINE SR DOM/INT I
PASSENGER NAME DEJONGE/AMR
DOCUMENT NUMBER 08516771083884 THRU DOC
UNUSED COUPONS FOR DOC1: 1 DOC2: DOC3:
UNUSED COUPONS FOR DOC4: DOC5: DOC6:
CASH AMT EX TAX PAID CASH AMOUNT USED ...1)....
CREDIT AMT EX TAX PAID 733.00 CREDIT AMOUNT USED ...2)...
TOTAL TAX AMOUNT PAID 34.50 CANCELLATION CHARGE ...3)...
UNUSED TAXES TO BE REFUNDED Y/N 4)
Above is the first of four refund screens. Certain fields of the fill-in format
are already completed. Remaining fields should be completed as
necessary.
1) Cash amount used
Complete when form of payment was other than credit card. For full
refund, enter 0.00
2) Credit Amount used
Complete when form of payment was credit card. For full refund,
enter 0.00
 Continued next page.

3) Cancellation Charge
When a cancellation charge is to be applied to the transaction, tab to
this field and enter the appropriate amount converted into EUR; e.g.
100.00
If no cancellation charges is applied, leave blank.
4) Unused Taxes to be refunded
Tab to this field and enter Y or N as appropriate and ENTER.
If an error is made on a refund screen, it may be redisplayed with *TRN.
Previous screens may be redisplayed by inputting the screen number e.g.

*TRN1.
If the first screen is completed correctly, the tax screen is displayed, if you
selected Y for unused taxes to be refunded, otherwise second refund
screen is displayed (see next page).
Refund Tax Screen
>*TRNTAX
TX1 1).... 2). TX2 ....... .. TX3 ....... .. TX4 ....... ..
TX5 ....... .. TX6 ....... .. TX7 ....... .. TX8 ....... ..
TX9 ....... .. TX10 ....... .. TX11 ....... .. TX12 ....... ..
TX13 ....... .. TX14 ....... .. TX15 ....... .. TX16 ....... ..
TX17 ....... .. TX18 ....... .. TX19 ....... .. TX20 ....... ..
BT01 3). 4)..... BT02 ... ....... BT03 ... .......
BT04 ... ....... BT05 ... ....... BT06 ... .......
BT07 ... ....... BT08 ... ....... BT09 ... .......
BT10 ... ....... BT11 ... ....... BT12 ... .......
BT13 ... ....... BT14 ... ....... BT15 ... .......
BT16 ... ....... BT17 ... ....... BT18 ... .......
BT19 ... ....... BT20 ... .......
1) Enter amount of tax as applicable e.g. 9.50

2) Enter the two letter tax code e.g. NL
3) If Breakdown Tax (ZP-tax) has to be refunded, you have to specify the
city code; enter the city code e.g. JFK
4) Enter the USD Breakdown amount e.g. 2.75

If previous screen(s) is completed correctly, the second refund screen will

be displayed:
Refund Screen 2
>*TRN2 A/L AUTHORITY 1).................. PAGE 2 OF 4
REFUNDED PFC AIRPORT CODE AND CHARGE INDICATOR
PFC1 2). 3) PFC2 ... . PFC3 ... . PFC4 ... .
CREDIT CARD CODE AX CARD NUMBER 375301500101000
EXPIRY DATE 1202 REFUND AMOUNT 4)......
CREDIT FOP CODE 5) NUMBER 5)
EXPIRY DATE 5).. REFUND AMOUNT 6)......
COMM PERCENT/AMOUNT ON CANCELLATION CHARGE 7).../ 8)......
TOUR CODE 9) NET Y/N N NET FARE AMT 11)
TOTAL CREDIT REFUND DUE 767.50 
TOTAL CASH REFUND DUE 0.00 10) THIRD SCREEN Y/N 12)
The TOTAL REFUND DUE, calculated from the information on the previous
screen(s), is shown on this screen.
The example above is with a credit card payment, hence the filled-in credit
card details are for illustration in bold print.
1) Airline authority code if such has been obtained.

Maximum 15 characters
2) If applicable, complete with PFC airport code e.g. JFK
3) PFC amount e.g. 3
4) Enter REFUND AMOUNT without currency code for first
credit card used
5) If payment was by 2 credit cards, details of the second
card will automatically be filled in these fields
6) Complete with refund amount for 2nd credit card if used
7) Not applicable (yet) for Dutch market as per BSP
decision. Leave blank
8) Not applicable (yet) for Dutch market as per BSP
decision. Leave blank
9) Automatically completed if TC modifier was originally
entered
10) Automatically completed: N if No Net Fare, Y if Net Fare
is applicable
11) Automatically completed: Net Fare Amount if applicable
12) Access of third screen is only necessary if form of
payment was with three credit cards, by inputting Y. Otherwise input
N

The third refund screen for our example is not relevant, so the N is input.
Response:
AUTOMATED REFUND NOTICE ISSUED

CREDIT CARD AX 375301500101000 AMOUNT 767.50
Refunded Electronic Ticket Record

If the electronic ticket record is displayed after the refund request was
finalised, all coupons will be marked as RFND (refunded) in the USE
column as shown below.
TKT: 085 1677 108388 NAME: DEJONGE/AMR

CC: AX375301500101000
ISSUED: 08DEC00 FOP:AX375301500101000
PSEUDO: 0XF6 PLATING CARRIER: SR ISO: NL IATA: 88888881
RFND SR 785 J 10DEC AMSZRH 0715 OK JOW 1

TOTAL: EUR 767.50
AMS SR(EH)ZRH M480.44JOW NUC 480.44 END ROE2.495587

Refund Screen 3
The top part of the 3rd screen will be completed by the system only when
payment was made with three credit cards.
The display shows in any case the system calculation for the total refund
due either by credit and/or cash.
>*TRN3 PAGE 3 OF 4
CREDIT CARD CODE CARD NUMBER
EXPIRY DATE .... REFUND AMOUNT ........
TOTAL CREDIT REFUND DUE 767.50
TOTAL CASH REFUND DUE 0.00
FOURTH MIR FREETEXT SCREEN Y/N .
Refund Screen 4
This screen is used only if additional data is required for the Refund MIR
(Machinable Interface Record) transfer into a back-office system. Any
required data is completed as free format text as defined by your back-
office provider. For sample inputs see Formats Guide DOCS 21. Please
note that the REFUND must be set to YES on the MIR Options and Type
Table (MMOD, level second only).
>*TRN4 MIR FREEFORM DATA PAGE 4 OF 4

DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
DI- .........................................................
If the screen is accessed by error <ENTER> will complete the function.

Exchange An Electronic Ticket

It is possible to exchange an electronic ticket for either another electronic
ticket or a paper ticket. It is not possible to exchange a paper ticket for an
electronic ticket.
The procedure is much the same as for non-electronic ticketing, in that the
normal exchange fill-in-format is requested with the FEX modifier and then
completed.
The differences are:
• the ticket number must be added to the FEX modifier
• the exchange fill-in-format is partially completed on display
Procedure:
Step 1 Amend flights in the original Booking File or create a
new Booking File as necessary.
Step 2 Obtain and file a fare for the revised itinerary in the
normal way. (Ensure only new taxes required with
regard to exchange ticketing are included.) End the
transaction and redisplay the Booking File.
Step 3 Display the Electronic Ticket Record in another window
in order to record its details in the exchange fill-in-
format.
Step 4 Request the exchange fill-in-format by using the normal
FEX modifier, but adding the ticket number to the input.
To exchange the ticket for an electronic one, ensure the
ET modifier is added. To exchange the ticket for a paper
ticket, omit the ET modifier.
Input e.g.: TMU1FEX1251677108392/DTD/ET
or TKP2P2FEX1251677108403/DTD/ET
Note: It is only possible to reissue one ticket per transaction.

When the BF contains more than one passenger, it is
necessary to deal with each ticket as a separate
transaction. Separate filed fares are required for each
passenger.
Response: (see following page)

Exchange Screen Response:

>*EX **TICKET FOR**: EXCHANGE/EASYMR PSGR 1/ 1
NEW FARE: EUR 1059.00 EQUIV: EUR
TX1: 0.00 TX2: 0.00 TX3: 0.00 TX4: 0.00
*EXCH TICKET*: TICKET NUMBER THRU TICKET NUMBER NO. CPNS
12516771083921 . .............. 01
COUPONS FOR TKT1: 2... TKT2: .... TKT3: .... TKT4: ....
PD TAXES 1: ...... .. 2: ...... .. 3: ...... .. 4: ...... ..
PD TAXES 5: ...... .. 6: ...... .. 7: ...... .. 8: ...... ..
TTL VALUE: ........... BSR: ...... ORIG FOP: ...............
*ORIG ISSUE*: TICKET NUMBER ORG/DES CITY DATE IATA CODE
.............. .../... ... ....... .......
The top part of the fill-in-format is completed as usual with the new fare and
any new taxes (if applicable). In addition, the TICKET NUMBER, NO.
CPNS and COUPONS FOR TKT fields are already completed.
Other fields should be completed exactly as for a non-electronic ticket

exchange.
On ENTER, the usual Additional Collection or Refund fill-in-format will be

presented, and must be completed as normal.
Electronic Ticket Records
Two electronic ticket records will now exist in the carrier’s internal
database. If the original electronic ticket record is displayed, the
exchanged coupons will be recorded as EXCH (exchanged) in the USE
column e.g.
TKT: 125 1677 108392 NAME: EXCHANGE/EASYMR
ISSUED: 19SEP00 FOP:CASH

PSEUDO: 0XF6 PLATING CARRIER: BA ISO: NL IATA: 88888881
USED BA 423 C 10DEC AMSLHR 0715 OK COW1 1
EXCH BA 1474 C 14DEC LHRGLA 0815 OK COW1 2
FARE: EUR 1112.00 TAX: 9.50 NL TAX: 24.50 GB TAX: 10.50 UB

TOTAL: EUR 1156.50
AMS BA LON BA(EH)GLA 5M728.84COW1 NUC 728.84 END ROE2.495667

Voiding An Electronic Ticket

An electronic ticket may be voided on the date of issue if no alterations
have been made. If the voiding request is successful, a positive VOID
response will be received, and the ticket is marked as VOID on the TINS
report.
Input: TRV/08516771083851
Void electronic ticket number, to include 3 digit airline
code, electronic ticket number with check digit.
Response:
TICKET NO. 0851677108385 CHANGED TO VOID STATUS
>TRV/08516771083851
If the Electronic Ticket Record is displayed, all coupons will be recorded as

VOID in the USE column.
TKT: 085 1677 108385 NAME: EXAMPLE/OPTAT
ISSUED: 13SEP00 FOP:CASH

PSEUDO: 0XF6 PLATING CARRIER: SR ISO: NL IATA: 88888881
VOID SR 785 J 10DEC AMSZRH 0715 OK JOW 1

TOTAL: EUR 767.50
AMS SR(EH)ZRH M480.44JOW NUC 480.44 END ROE2.495587

Display Of An Electronic Ticket Record

An electronic ticket record held in an airlines database may be displayed
either from a retrieved Booking File or with no Booking File present.
From A Retrieved Booking File
Input: *HTE
(Sample see on page 9)
With No Booking File Present
Electronic ticket records may be displayed with direct inputs, or with the aid
of a fill-in-format. Individual airlines may choose to support all or some of
the following display inputs.
By Ticket Number
Input: *TE/ 0851677108385
(Entry must include airline code and serial number)
By Airline Code(or Flight Number)/Date/Board/Off-Name

Inputs: *TE/SR/10DEC00AMSZRH-VANDAM
*TE/TP/5606/01JAN01LISAMS-DEVRIES
By Airline Code/Date/Mileage Membership Number

Input: *TE/BA/20DEC00FF00016050
By Airline Code/Date/Credit Card Number-Name

Input: *TE/SN/14DEC00CC375811111111115-JANSEN

By Fill-In-Format
Input: *TE
Response:
>*TEF ELECTRONIC TICKET RECORD RETRIEVAL @-
HELP
**NOT ALL FIELDS REQUIRED**
**SEE @HELP FOR SPECIFIC CARRIER SEARCH CRITERIA**
PLATING CARRIER CODE: ... TICKET NBR: .............
OR
FREQUENT FLYER NBR: ....................
CREDIT CARD NBR: ....................
TELEPHONE NBR: ....................
NAME: .................................
FLIGHT: .... DATE: ....... ORIGIN: ... DESTINATION: ...
Completion of the PLATING CARRIER CODE and one additional field is

mandatory. Fields, which require numbers to be input i.e. FREQUENT
FLYER and CREDIT CARD, are completed solely with the number i.e. FF
and CC should not be included. Help to complete any field may be obtained
by entering the @ symbol in that field.
Redisplay The FIF
Input: *TEF
Either the response to any display input is the electronic ticket record itself
or a ticket record list (see below) if multiple Electronic Ticket Records exist.
Response e.g.:
ELECTRONIC TICKET LIST BY *HTE
NAME TICKET NUMBER
>*TE001 VANHEKEREN/AMR 0854664491022
>*TE002 DEBIE/FMR 0854664491023
END OF LIST
Input: *TE1 or tab to the prompt

Access a record from the list
Input: *TEL
To redisplay the list

History Of An Electronic Ticket

The history of an electronic ticket record may be viewed.
Input: *TEH
Response:
**** HISTORY FOR E-TICKET 125 1677 108371 ****
CP ACTION OLD NEW CR FLT CL DATE BRD OFF

1 ISSUED BA 0435 C 15OCT00 AMS LHR
1G 0XF6 88888881 N007022 26AUG00 07:43Z
CP ACTION OLD NEW CR FLT CL DATE BRD OFF

1 REVAL BA 0439 C 14OCT00 AMS LHR
1G 0XF6 88888881 N007022 27AUG00 20:13Z
A history section for each coupon shows the coupon number, the action
taken (ISSUED, USED, REVAL, EXCHANGED, VOIDED, REFUNDED),
the carrier, flight number, class, date, board and off point.
If a coupon has been exchanged, refunded or voided, the status EXCH,

RFND or VOID is shown in the NEW field colon.
The last line of each history section shows the Galileo code (1G), the
agency Pseudo City, IATA code, sign-on including check digit, and date
and time the message was received.
The example above shows the creation (issue) details of an electronic

ticket. The ticket was subsequently revalidated.
Note:
• Airlines may display history records differently. For details see airline
specific instructions.

Electronic Ticketing Formats Guide

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Electronic Ticketing Formats Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Galileo

 Overview of the Galileo procedure on electronic ticketing in GIS........GC*401/46

INTRODUCTION ELECTRONIC TICKETING

Electronic ticketing is being introduced by increasing numbers of airlines

Electronic ticketing is an additional function, which is available through the

Galileo provides the following functionality to support electronic ticketing:

• Production of electronic ticket records

ET 2 Galileo Formats January 2001

Linkage to OPTAT ticket printed devices remains the same. However

Input e.g.: HMLMC70F7EDIE

Linkage to an OPTAT and designated itinerary printer is shown below.

BSP Support Document Default & Reporting

Galileo Formats January 2001 ET 3

Support Document Print Table

2. GTID to which each document is printed

3. Form type of 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

6. Status of printer U (up) or D (down)

7. Default is set as Y to print documents at TKP

ET 4 Galileo Formats January 2001

BSP Electronic Ticketing Table

DEFAULT KEY: P-PAPER TKT E-ELECTRONIC TKT

1 BSP country indicator 009 and NL

2 Supported electronic ticket types

3 Electronic ticketing support documents types available

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

Galileo Formats January 2001 ET 5

Booking File Creation For An Electronic Ticket

The airlines that participate in electronic ticketing on Galileo may

Initial Sell response

1. SN 2402 C 23MAR AMSBRU HS1 0810 0855 O E FR

Retrieved Booking File

M9CG0Y/JJ AMSNH N007022 AG 81237995 13JAN

The 'E' indicator is also shown on the carrier specific timetable:

SN 2402 FRIDAY 23 MAR 01

ET 6 Galileo Formats January 2001

Name Field & Mileage Membership

In order to assist airlines systems to automatically identify the booking it is

This practice will greatly assist passengers who check in at self-service

With the input of a SSR FOID (Form Of IDentification) an ID may be added

Galileo Formats January 2001 ET 7

Before requesting an electronic ticket, the following should be

2. All booked segments to be ticketed either show an E indicator or are

3. The fare quote is based on eligible segments for the respective

ET 8 Galileo Formats January 2001

Electronic Ticket, Itinerary And MIR Production

TKP1P2/ET Create electronic ticket, print itinerary (if linked), issue

e.g. TMU1ET Add electronic ticket modifier to filed fare number 1.

If the request is accepted by the carrier, an electronic ticket record is

ELECTRONIC TKT GENERATED TTL FARE EUR 460.50

Galileo Formats January 2001 ET 9

Effects Of Electronic Ticketing On The Booking File

• The face of the Booking File

Face Of The Booking File

M9CG0Y/JJ AMSNH N007022 AG 81237995 13JAN

Sample *HTE Display:

FARE: EUR 426.00 TAX: 9.50 NL TAX: 24.00 RN TAX: 1.00VV

AMS SN(EH)BRU M170.70Y NUC 170.70 END ROE2.495587

ET 10 Galileo Formats January 2001

In a multiple-passenger Booking File, *HTE produces a ticket record name

NO HISTORY TIN DATA

ETKT AGENT COUPON 88888881 ITINERARY