revision history - travelport services · viewtrip e-ticket receipts ... two day course will give...

Revision History

Date Version Authors Reason / Description of Change

March 2014 V9.0 Keith Reynolds

Updated course to include Smartpoint 3.0.

Incorporated EMD into the body of the course.

MCOs removed.

Version Control 9.0

Acknowledgements: All Travelport logos and marks as well as all other proprietary materials depicted herein are the property of

Travelport and/or its subsidiaries. © Copyright 2014. All rights reserved.

Galileo Document Production Course Book v9.0 3

Contents

Contents .............................................................................................................................................. 3

Module 1: Introduction ........................................................................................................................... 9

Prerequisites ....................................................................................................................................... 9

Housekeeping ..................................................................................................................................... 9

Course Length ..................................................................................................................................... 9

Course Materials ................................................................................................................................. 9

Course Objectives ............................................................................................................................. 10

Features and Benefits ....................................................................................................................... 10

Introducing Galileo Document Production ....................................................................................... 11

Fares Help ......................................................................................................................................... 12

Module 2: Issuing E-Tickets ................................................................................................................... 13

Module Objectives ............................................................................................................................ 13

Ticketing Commands ......................................................................................................................... 14

Ticketing Qualifiers ....................................................................................................................... 14

Booking File Details ....................................................................................................................... 15

Viewing an E-Ticket Record ........................................................................................................... 19

TINS Report ....................................................................................................................................... 19

Voiding a Ticket ................................................................................................................................. 22

Ticketing Carrier Guidelines .............................................................................................................. 23

Module 2 Review .............................................................................................................................. 24

Module 3: Specific Passenger/Fare Selection ....................................................................................... 25


Passenger Selection .......................................................................................................................... 25

Issuing a Ticket for Specified Passengers only .............................................................................. 25

Fare Selection ................................................................................................................................ 26

Specific Ticket Modifiers ................................................................................................................... 27

Module 3 Review .............................................................................................................................. 29

Module 4: Ticketing Modifiers .............................................................................................................. 31


Mandatory Ticket Modifiers ............................................................................................................. 31

Form of Payment .......................................................................................................................... 32

Contents

4 Galileo Document Production Course Book v 9.0

Optional Ticketing Modifiers ............................................................................................................ 34

Commission ................................................................................................................................... 34

Endorsements ............................................................................................................................... 35

Net Ticketing ................................................................................................................................. 37

Plating Carrier ............................................................................................................................... 37

Multiple Modifiers ........................................................................................................................ 38

Amending/Deleting Ticket Modifiers ................................................................................................ 39

Amending a Modifier .................................................................................................................... 39

Amending More than One Modifier ............................................................................................. 39

Deleting a Modifier ....................................................................................................................... 39

Module 4 Review .............................................................................................................................. 40

Module 5: Manual Fare Build................................................................................................................ 41


Creating a Manual Fare Build Screen (FBC) ...................................................................................... 41

Updating the Fare Build Screen (FBU) .............................................................................................. 45

Segment Related Entries ............................................................................................................... 49

Baggage ......................................................................................................................................... 49

Taxes ............................................................................................................................................. 49

Passenger Facility Charges ............................................................................................................ 50

Flight Segment Tax (US domestic journeys only) .......................................................................... 51

Endorsements ............................................................................................................................... 51

Filing the Manual Fare (FBF) ............................................................................................................. 52

Multiple Passengers and Passenger Descriptions ............................................................................. 53

Amending a Filed Fare ...................................................................................................................... 55

Deleting a field .............................................................................................................................. 55

Ignoring a Manual Fare Build ............................................................................................................ 56

Restoring a Filed Fare ........................................................................................................................ 56

Module 5 Review .............................................................................................................................. 57

Module 6: Tour Ticketing ...................................................................................................................... 60


Tour Ticketing ................................................................................................................................... 60

Tour Code Modifier (TC) ............................................................................................................... 61

Inclusive Tour Modifier (IT) ........................................................................................................... 61

Bulk Tour Modifier (BT) ................................................................................................................. 61

Commissions ................................................................................................................................. 62

Contents

Galileo Document Production Course Book v 9.0 5

Module 6 Review .............................................................................................................................. 64

Module 7: Net Remit 2 .......................................................................................................................... 65


Modifiers ........................................................................................................................................... 65

Airline Information AI– ................................................................................................................. 66

Value Code VC– ............................................................................................................................. 67

Net Fare NF ................................................................................................................................... 68

General Information ......................................................................................................................... 69

Module 7 Review .............................................................................................................................. 70

Module 8: Ticket Revalidation .............................................................................................................. 71


Revalidation ...................................................................................................................................... 71

Revalidating an E-Ticket after the Passenger has been Divided out ............................................ 73

Revalidating British Airways E-Tickets .......................................................................................... 74

Module 8 Review .............................................................................................................................. 76

Module 9: Exchange Tickets ................................................................................................................. 77


Ticket Exchange or Revalidation ....................................................................................................... 77

Exchange Fill-In Formats ................................................................................................................... 78

Steps to Reissue a Ticket ................................................................................................................... 78

How to Use the Exchange Ticket Fill in Format (FIF) screen ............................................................. 79

Example 1 – No Additional Collection – Unused ticket..................................................................... 79

Example Number 2 - Additional Collection Exchange ....................................................................... 85

Voiding / Cancelling a Reissued ticket .......................................................................................... 89

Alternate Currency Reissues ............................................................................................................. 89

Module 9 Review .............................................................................................................................. 91

Module 10: Automated Refunds .......................................................................................................... 92


Processing a Refund .......................................................................................................................... 92

Re-printing the Refund Notice ...................................................................................................... 96

Cancelling a Refund ....................................................................................................................... 96

Viewing Refunded Tickets on the Payment Report (HMPR) ......................................................... 96

Module 10 Review ............................................................................................................................ 98

Module 11: Itinerary Remarks .............................................................................................................. 99

Contents



Manually Added Remarks ................................................................................................................. 99

Unassociated Remarks .................................................................................................................... 100

Associated Remarks ........................................................................................................................ 101

Check in Remarks ............................................................................................................................ 102

Terminal Information ...................................................................................................................... 103

Displaying Itinerary Remarks .......................................................................................................... 104

Amending and Deleting Itinerary Remarks ................................................................................. 105

Re-associating Itinerary Remarks ................................................................................................ 106

Canned Remarks ............................................................................................................................. 107

Adding Canned Remarks into an Itinerary ...................................................................................... 107

Enhanced Itineraries ................................................................................................................... 107

Galileo Itineraries ........................................................................................................................ 108

ViewTrip Itineraries ......................................................................................................................... 109

ViewTrip E-Ticket Receipts .......................................................................................................... 110

Module 11 Review .......................................................................................................................... 112

Module 12: Linkage and Support Document Set Up .......................................................................... 113

Module Objectives .......................................................................................................................... 113

Setting up Support Document Printing ........................................................................................... 113

Reprinting Support Documentation............................................................................................ 115

Printer Linkage ................................................................................................................................ 115

Linking to an Itinerary Printer (DI) .............................................................................................. 116

Linking to a MIR Device (DI) ........................................................................................................ 117

Displaying your Linkage .............................................................................................................. 117

Bringing the Status Up ................................................................................................................ 118

Delinking ..................................................................................................................................... 118

Module 12 Review .......................................................................................................................... 119

Module 13: Stock Control ................................................................................................................... 120


Displaying E-Ticket Numbers .......................................................................................................... 120

Itinerary Stock Control .................................................................................................................... 121

TINS Report ..................................................................................................................................... 122

Ticket Voiding .................................................................................................................................. 123

Module 13 Review .......................................................................................................................... 124

Contents


Module14: Electronic Miscellaneous Document (EMD) ................................................................... 125


Introduction .................................................................................................................................... 127

Printing and Document Modifiers .............................................................................................. 128

Selection Criteria Modifiers ........................................................................................................ 130

Reason for Issuance Codes (RFIC) and Sub-codes (RFISC) .......................................................... 131

Types of Electronic Miscellaneous Documents .............................................................................. 132

Standalone EMD (EMD-S) ........................................................................................................... 132

Associated EMD (EMD-A) ............................................................................................................ 133

EMD Example 1: Issuing an EMD for a Reservation Change Fee ................................................ 134

Displaying EMD Information in a Booking File ............................................................................ 138

EMD Example 2: Issuing an EMD for a Group Deposit.................................................................... 141

EMD Example 3: Issuing an EMD for a Service Booked for all Passengers on all Flight Segments . 145

EMD Example 4: Issuing an EMD for Multiple Services Booked, for only one Passenger .............. 150

Voiding an EMD ............................................................................................................................... 153

Refunding an EMD .......................................................................................................................... 155

Viewing EMD History ..................................................................................................................... 157

EMD Information on the TINS Report ............................................................................................. 159

Module 15: E-Ticketing Troubleshooting ............................................................................................ 160


Common E-Ticket Problem Scenarios ............................................................................................. 160

Unable to issue a Ticket .................................................................................................................. 160

Unable to Display an E-Ticket Record ............................................................................................. 161

Unable to Revalidate or Exchange an E-Ticket ............................................................................... 161

FAQs - Unable to Revalidate an E-Ticket ..................................................................................... 162

Unable to Void an E-Ticket .............................................................................................................. 163

Unable to Send Automatic TKNE E-Ticket Numbers to the Airline ................................................. 163

Module 16: Fallback and Recovery for Itinerary and MIR .................................................................. 164


Tracking the Flow of a Document ................................................................................................... 164

Transmission Flow of a Document .............................................................................................. 165

Fallback and Recovery Procedures ................................................................................................. 166

Displaying Demand Pending and Sent Buffer Image Counts ...................................................... 166

Displaying Images in the Pending Buffer .................................................................................... 167

Contents


Scrolling through the Demand Pending Buffer ........................................................................... 167

Deleting an Image from the Demand Pending Buffer ................................................................ 167

Bringing the Printer Status Up .................................................................................................... 167

Working with the Printer Buffer ..................................................................................................... 168

Printer Buffer Image Count ......................................................................................................... 168

Displaying the Printer Buffer Image ............................................................................................ 168

Deleting an Image from the Printer Buffer ................................................................................. 169

Quick Starting the Printer ........................................................................................................... 169

Appendix A: Enhanced TINS Reports ................................................................................................ 170

Daily TINS Reports ........................................................................................................................... 170

Basic TINS Reports ...................................................................................................................... 170

Daily Activity Report (DAR) ......................................................................................................... 171

Period Activity Report (PAR) ....................................................................................................... 172

Summary Activity Report (SAR) .................................................................................................. 173

Appendix B: Module Review Answers ............................................................................................... 174

Module 2 Review: Issuing E-Tickets ............................................................................................... 174

Module 3 Review: Specific Passenger/Fare Selection ................................................................... 175

Module 4 Review: Ticketing Modifiers .......................................................................................... 175

Module 5 Review: Manual Fare Build ............................................................................................ 176

Module 6 Review: Tour Ticketing .................................................................................................. 176

Module 7 Review: Net Remit 2 ....................................................................................................... 177

Module 8 Review: Ticket Revalidation ........................................................................................... 177

Module 9 Review: Exchange Tickets .............................................................................................. 177

Module 10 Review: Automated Refunds ....................................................................................... 178

Module 11 Review: Itinerary Remarks ........................................................................................... 178

Module 12 Review: Linkage ........................................................................................................... 178

Module 13 Review: Ticket Stock Control ....................................................................................... 179


Module 1: Introduction

Welcome to the Galileo Document Production (e-ticketing) course. This two day course will give you the ability to produce electronic travel documents and itineraries using the Galileo system.

Prerequisites

You must have a working knowledge of the Galileo system and be able to create and fare quote a Booking File.

Housekeeping

You should note the following details:

Fire exits

Toilets

Start and finish times and breaks

Mobile phone policy

Course Length

The course is designed to last two days.

Course Materials

This course book provides areas to make notes and complete exercises. It is designed to be a learning tool during class and to be used as a reference guide back at your office.

There is a separate module at the end of the course containing answers to exercises.



Course Objectives

At the end of this course you will be able to perform the following functions:

Issue an e-ticket

Add appropriate ticket modifiers

Interpret payment reports for BSP reporting

Add fare elements using Manual Fare Build

Add Tour Code and Net Remit modifiers

Revalidate an e-ticket

Exchange an e-ticket

Refund an e-ticket

Void an e-ticket

Add Itinerary Remarks

Perform printer linkage

Manage stock control

Issue an Electronic Miscellaneous Document (EMD)

Features and Benefits

Galileo Document Production provides:

Improved customer service through automated document production, increasing both accuracy and efficiency

Automated electronic reporting, reducing costly agency overheads

Simultaneous action of the booking and ticketing process, providing the potential for increased revenue



Introducing Galileo Document Production

This course provides you with hands-on experience of issuing electronic tickets, itineraries, MIRs and EMDs in a working environment. The support documentation provides examples and formats covered in the course.

The Galileo Document Production system offers the following:

Electronic ticketing

Itinerary printing

Ticket and Itinerary stock records

Electronic reporting to BSP

The ability to hand off information to back office systems in your agency using the Galileo MIR

EMDs

Successful performance of these tasks is based on the data contained in the Booking File at time of ticketing.

When the request is made to issue documents, the Galileo system checks the Booking File for the following data:

The itinerary is in chronological order

Name fields are present and in correct format

There is a filed fare(s) present, either automatic or manual fare

A plating carrier is present

A form of payment field is present

A vendor locator is present (in most cases)

A received field has been entered

When a ticket is issued, system checks are made to ensure sufficient ticket numbers and itinerary stock (if applicable) are logged into electronic stock records.

When all checks have been made successfully, an electronic ticket is issued and recorded in the airlines Electronic Ticket Server (ETS) and a record of the e-ticket is automatically noted in the Booking File.

The Galileo system amends the ticketing field and ends transaction on the Booking File.

Ticketing data will also be recorded on the TINS report which is subsequently reported to BSP.



Fares Help

When you make the request to issue a ticket, the Galileo system checks that there is a filed fare present, whether it is an automatic fare quote or manual fare.

In addition to the HELP pages found in Galileo, ASK Travelport provides answers to your questions and self -study exercises to help with practice and boost your fares knowledge.

Self-study exercises can be found using the following ASK Travelport answer numbers:

AN9335 - Fare Display

AN9341 - Fare Quote

AN9345 - FS and FQP

Each exercise is approximately 30 minutes in length.


Module 2: Issuing E-Tickets

HELP ETKT

When the Booking File is ready it is possible to produce an e-ticket, itinerary and MIR, if applicable. This module explains the ticketing format, and the various qualifiers which can be added to it.

The term e-ticket is an abbreviation of electronic ticket. It is a paperless electronic document used for ticketing purposes.

When you make the command to issue the ticket, details of the customer’s reservation and ticket number are transmitted directly to the airlines electronic ticket server.

In some instances, you may wish to produce an e-ticket receipt or alternatively the passenger may print their own from the www.viewtrip.com website.

Although airline check-in staff does not usually need a physical document, many passengers do still want to take a physical document to the airport.

Module Objectives

Upon completion of this module you will be able to:

Identify various ticketing commands

Access the TINS payment report

Identify additional data printed on a ticket

Adhere to carrier guidelines



Ticketing Commands

HELP TKP

The Galileo system checks for the presence of a filed fare, plating carrier and form of payment (FOP) when a ticketing request is made. The plating carrier is selected automatically by Galileo in markets/agencies which use Automatic Plating Carrier Logic. Ensure the Booking File has been completed with the mandatory items, plus a filed fare and a form of payment. End and retrieve the Booking File before making the ticketing command.

The most frequently used ticketing entry is: TKP

Format: Explanation:

TKP TicKet Please

This entry will end the Booking File, and issue the e-ticket and any associated documents including itineraries and MIRs.

Example screen response:

Ticketing Qualifiers

HELP TKPI

You can use qualifiers to select which documents are required. For example, it may be necessary to print the itinerary before the ticket is issued.

Example formats:


TKPDID Demand Itinerary Device

TKPDTD Demand Ticket Device

TKPDAD Demand Accounting Device (MIR)

TKPDTDAD Demand Ticket and Accounting Device



Booking File Details

When the ticket is issued, the Booking file is automatically updated.

Refer to the following example Booking File after it has been retrieved.

The ticket field is amended to add the date/time of issue together with the agent's sign on and duty code.

The Filed Fare is updated to show the ticket number:



The system adds two new Quick Access buttons to the Booking File in the PNR Viewer window - *HTI and *HTE

*HTI – Tins Remarks exist


This displays ticket number 9329901891912 and itinerary 000850445 and the total fare charged.

Note: ET indicates that an e-ticket was issued.

*HTE – Electronic Data may exist

All airlines allowing the issue of e-tickets provide access to their e-ticket database. It is possible to display records for any electronic ticket generated by your office or a branch office.

Click the *HTE Quick Access button to display the e-ticket record.




Screen explanation:

Screen: Explanation:

TKT: 932 9901 891912 e-ticket number pre-fixed with the airline 3 digit code 932

NAME: SMITH/JOHNMR Passenger name

PH: 0 126 289 7602 Passenger’s home phone number

ISSUED…..30DEC13 Date that the e-ticket was issued

FOP: CHEQUE Form of payment

PSEUDO: 0EA7 Issuing agency pseudo. A three-character pseudo will always be prefixed with 0

PLATING CARRIER…VS The two letter plating carrier code selected as part of the fare quote process or added as a ticket modifier

ISO: GB ISO code – ticket issued in the UK

IATA 99999992 IATA number of the issuing agency

USE Status of the e-ticket

OPEN – unused and eligible for status updates

USED or FLWN – The journey associated with the e-ticket has been completed

APRT – The operating carrier has secured the e-ticket prior to the scheduled departure

CKIN – The passenger has made his/her presence known to the operating carrier

LFTD – The passenger has boarded the aircraft

UNVL – The validating carrier has determined that the e-ticket is unavailable for use as ticketed and may only be exchanged.

EXCH – The value of the e-ticket has been used as full or part payment for a reissued ticket

RTFC – The Validating Carrier has determined the coupon status is no longer available for use as ticketed and applicable taxes/fees/charges only may be refunded.

RFND – The unused value of the e-ticket has been refunded to the passenger

VOID – The ticket has been made void within the permitted voiding period as defined by BSP




CR Carrier column, in this case VS for Virgin Atlantic Airways

FLT Flight number: 601

CLS Booking class code: Y

DATE Date of segment(s)

BRDOFF Board and off points

TIME Scheduled departure time

ST Status of the reservation

OK – Space confirmed

SA – Stand-by

F/B Fare Basis code: Y2

CPN Coupon number, e.g. 1

FARE GBP 1520.00 Fare expressed in local currency

TAX Tax breakdown

TOTAL Total fare including tax in the currency of the country of issue

EQUIV Any equivalent base fare is shown in the currency of the country of issue

LON VS JNB ……… Fare calculation / construction

RLOC 1G…..T9K0ZI

VS GQMCN0

The booking locator from the Galileo system (1G) and the airline’s hosting system.



Viewing an E-Ticket Record

It is possible to make the following entries from a retrieved Booking File.


*HTE Display Historical Ticketing Electronic data

*TE002 Display record number 2 from Electronic Ticket list when *HTE produces a multiple ticket list

*TEL Redisplay the multiple Ticketing Electronic List

You can make the following entries without retrieving the Booking File.


*TE/125960000078 Display e-ticket data using the ticket number (check digit omitted)

*TE/AA/FF10087654 Display an e-ticket record held in the American Airlines database using the passengers mileage membership number

*TE/LH/CC373900000000000 Display an e-ticket record held in the Deutsche Lufthansa database using the credit card number

*TE/AF/10DEC13PARMRS-LE BLANC

Display an e-ticket record from the Air France database using the date, routing and passenger family name

TINS Report

HELP TINS ASK ANSWER 578

The TINS report displays a list of transactions for each day, and is updated automatically as each ticket is issued, with details of the passenger name, fare, total taxes, commission and form of payment.

It is more commonly referred to as the Payment Report or Daily Activity Report and is forwarded electronically to BSP overnight.

The TINS report provides system generated ticket numbers. This includes any tickets that have been voided either by your agency or automatically during the ticketing process.



Enter: HMPR


Note: TINS records may be displayed for up to 32 historical working days, although the period of time may vary from country to country.

If you need to access an historical TINS report for a previous date, the entry is: HMPR/12AUG

Other TINS formats:


HMPR Display the TINS Report for today for own office

HMPR/XX9 Display the TINS Report for today for branch office XX9

HMPR/E12345 Print the TINS report for today on printer GTD E12345

P-HMPR Print the TINS report for the current day

HMPR/D Display the TINS Report for Domestic Tickets only

HMPR/I Display the TINS Report for International Tickets only

HMPR/02JAN Display the TINS Report for a specific date

HMPR/ALL Display the TINS Report for all transactions

HMPR/TKT Print the TINS Report for ticket transactions only



HMPR/CU-EUR Display the TINS Report in an alternative currency



Voiding a Ticket

HELP VOID ASK ANSWER 570

The period in which you can make a ticket void differs from country to country. For example, in the UK, it is only possible to void a ticket on the day of issue.

Once a ticket has been issued and then made void, it is not possible to reverse the process or “un-void” it.

If an e-ticket has been issued, you may want to void it if perhaps the wrong form of payment was entered.

The entry to void the VS ticket in the example above is:

TRV/ 9329901891912

Entry: Description:

TRV Ticket Report Void function identifier

/ Separator

9329901891912 Ticket number including the airline code. The check digit is optional.

Screen response:



Ticketing Carrier Guidelines

ASK ANSWER 2347

You must adhere to the specified carrier’s criteria before ticketing can take place, and should make these checks before making the ticketing command:

The airline must have an agreement with Galileo, and have signed the Galileo Participation Agreement

The airline must be a BSP participant and the agent must have authorisation to issue tickets for that airline

Note: To enable an agent to issue a ticket through the Galileo system, any carrier for whom your agency is authorized to issue tickets must be listed in the AAT (Agency Account Table).

It is essential for interline travel that every airline in the itinerary must have an agreement with the ticketing airline.

For example, ZB (Monarch Airlines) may not be issued on TP documents.

To check the ticketing agreements between two airlines, make the entry DT/IAT/DISXX (XX represents the ticketing carrier).

Refer to the following example for KLM.

Enter: DT/IAT/DISKL


Note: The table shows those airlines which accept a KL ticket.

When a Y indicator appears next to the interline carrier code, it denotes that the interline carrier may be ticketed against the validating carrier, even if the validating carrier is not present in the itinerary.

If no Y indicator is present next to the interline carrier code, that carrier can only be e-ticketed if a validating carrier segment is included in the filed fare.



Module 2 Review

Use your Course Book, Online Help and ASK Travelport and answer the following questions. Make all reservations in your name unless advised otherwise. 1. What is the entry to issue a ticket only?

2. Create a Booking File using your name, for travel Hong Kong/San Francisco 18 January / July and return on 27 January / July in M class with United Airlines.

Fare quote and add the form of payment as cash. End and retrieve the Booking File and issue a ticket only. Write down your entry.

3. Retrieve the Booking File and make the entry to display the TINS remarks. Write down the

entry. 4. What is the ticket number? 5. What is the entry to display the TINS Report?

6. What is the entry to void ticket number 057 9900035440 1? 7. Can you issue an e-ticket on plating carrier Air France (AF), with a sector on Air Zimbabwe (UM)?


Module 3: Specific Passenger/Fare Selection

The ticket command TKP assumes that tickets are required for all passengers and all filed fares. However, it is possible to identify a specific passenger and/or filed fare for ticketing.

Module Objectives


Issue a ticket for a single passenger from a multiple Booking File

Issue tickets for a specified filed fare in a Booking File

Passenger Selection

It is usually most efficient to make the passenger selection at the time of the fare request, often paired with a segment selection. This determines which passengers and/or segments will be produced at the time of ticketing.

The entry TKP will issue tickets for all passengers in the Booking File, irrespective of the number or type of passengers or different fare quotes. Each passenger is automatically linked to a fare quote.

Issuing a Ticket for Specified Passengers only

You would issue a ticket for specified passengers in a Booking File if the filed fare is for all of the passengers, but you only wish to issue tickets for some of them.

For example, some airlines do not accept e-tickets for infant passengers and therefore it will be necessary to issue tickets for all other passengers except the infant.

Example entry: TKP1P1

Entry: Description:

TKP Issue ticket

1 Filed Fare 1

P1 Passenger 1 only

Module 3: Specific Passenger / Fare Selection


Fare Selection

HELP TKP

Similarly, it is possible to ask for tickets for all passengers linked to a particular filed fare.

This is most likely to be used when you have a number of different fares in the Booking File. For example, a Booking File may contain one fare filed for domestic feeder flights and a separate fare filed for an international journey. You may only wish to issue the tickets for the international sectors.

Example entry: TKP2

Entry: Description:

TKP Issue ticket

2 Filed Fare 2 for all passengers

Whenever you request a ticket for a specific passenger, you must include the filed fare number even if there is only one filed fare in the Booking File.

Other format examples:


TKP3 Issue ticket for filed fare 3 only

TKP1P3 Issue ticket for filed fare 1 passenger 3

TKP1P3-5 Issue ticket for filed fare 1 passengers 3 through to 5

TKP2P2.4 Issue ticket for filed fare 2 passengers 2 and 4 only

Note: In a multiple passenger Booking File, it is not possible to issue tickets for selected passengers against more than one filed fare in one entry.

For example, you may have a Booking File for three passengers, with one filed fare for international flights and a second filed fare for domestic flights.

You can issue tickets for all passengers and all fares (TKP) or all passengers for one fare (TKP2), but you cannot issue tickets for an individual passenger for both fares.

To issue tickets for just one passenger you must either split the passenger from the Booking File, or issue two separate tickets, one for international travel and one for domestic travel.



Specific Ticket Modifiers

ASK ANSWER 2281 HELP TMU

If there is more than one passenger in a Booking File and the passengers are using different forms of payment, or require different ticket endorsements, you must add the information using passenger related ticketing modifiers.

Refer to a Booking File example for two passengers who have the same fare quote.

Passenger 1 will pay by cash and passenger 2 will pay by cheque.

Both have the same plating carrier details. The entries are:

TMU1P1FS Ticket modifier update Fare 1, Passenger 1, form of payment cash

TMU1P2FCK Ticket modifier update Fare 1, Passenger 2, form of payment cheque

Note: Both entries must include the filed fare number, even if there is only one fare in the Booking File.

Booking File Example

The following Booking File for four passengers has two separate fare quotes.

There are two adults (passengers 1 and 2), one child (passenger 3) and one infant (passenger 4).

There are two fare quotes, filed fare 1 (FQ1) being for the international sectors SINDELSIN (S1.4) and filed fare 2 (FQ2) for the domestic sectors DELMAADEL (S2-3).

The domestic carrier 9W does not allow infant e-tickets. (Arrangements must be made directly with the carrier to issue the infant ticket on your behalf.)

The example will help you understand which tickets will be issued for each command.



Entry: Explanation:

TKP1P1-2 Will issue international tickets only for both adults.

TKP2P1-3 Will issue domestic tickets for all passengers except the infant.

TKP1 Issue international tickets (filed fare 1) for all passengers.



Module 3 Review

Use your Course Book, Online Help and ASK Travelport and answer the following questions. Make all reservations in your name unless advised otherwise.

1. What is the entry to issue tickets for the international sectors (only) for all passengers?

2. What is the entry to issue domestic USA tickets for the child?

3. What is the entry to issue international tickets for the Katsarou family?

4. What is the entry to issue tickets for Mrs Christoloudis’ domestic USA ticket only?



5. Create a Booking File for two customers travelling from Frankfurt to Bahrain on your date in Y class with Gulf Air (GF); your passengers wish to travel back 7 days later. Use your name and a friend’s name. Add all mandatory fields and add a fare quote. End the Booking File, noting the Record Locator. Issue the ticket for the first passenger in the Booking File only. Your passenger will be paying for his ticket with an American Express card 374296409071000 which expires 12/16.

You have already obtained an approval code which is A0021. They do not require an itinerary. Make a note of the ticket number.


Module 4: Ticketing Modifiers

The Galileo system checks for the presence of a filed fare, plating carrier and form of payment when a ticketing request is made.

Ticketing Modifiers are stored within the actual filed fare and not the Booking File, and can be viewed by displaying the filed fare breakdown.

They are located in the ‘T’ line at the bottom. Different ticketing modifiers may be entered for each filed fare.

Module Objectives


Identify and add mandatory ticket modifiers

Identify and add optional ticket modifiers

Amend or delete ticket modifiers

Add name remarks

Mandatory Ticket Modifiers

HELP TMU ASK ANSWER 8684

Mandatory ticket modifiers are those that must be present in the Booking File before the Galileo system will allow tickets to be issued. Rather than completing them in the Booking File, it is possible to add the form of payment and plating carrier by using ticketing modifiers.

All ticketing modifiers are prefixed with entry code TMU, followed by the filed fare number:

TMU1 Ticket Modifier Update filed fare 1.

Note: Agencies using Plating Carrier Logic cannot use a ticketing modifier to change the plating carrier.

To override the plating carrier added by the system, you must make a new fare quote entry specifying the required plating carrier, e.g. FQCSQ.



Form of Payment

There are various forms of payment that may be used:


FS Cash

FCK Cheque /check

FINV12345 Invoice Number

FNONREF Non-refundable without reference to issuing agent

F487652221110028*D1216 Credit card with date of expiry (no spaces in the credit card number)

FMSfreetext Miscellaneous payment

Refer to the following example entry:

TMU1FCK

Entry: Description:

TMU Ticketing modifier update

1 Filed fare number 1

F Form of payment entry code

CK Form of payment cheque

Response after *FF1:

The form of payment (CK) and plating carrier (CY) are stored together in one line of the fare quote.



Note: When using a credit card, the vendor code is optional but if it is included the system will check the code against the numeric identifier of the vendor (usually the first 4 numbers).

If there is a mismatch, the system will respond with ‘CHECK CREDIT CARD VENDOR’.

The system will obtain an approval from the credit card company at the time of ticket issue. If credit card approval is obtained outside the system, e.g. by phone, then an inhibitor must be added to the entry to prevent duplicate authorization.

For example, if the non-system approval code is 123456, the entry will be:

TMU1FAX487652221110028*D0916*A123456

Important note: Check the number very carefully as the system does not validate any entry with an authority code inhibitor.

If the reject message ‘CONTACT CREDIT CARD VENDOR’ is received, it is essential that the credit card company is contacted because it could be a stolen card.

Alternatively, there could be an error in the communications link between the Galileo system and the credit card company. It is important to ascertain where the error has occurred. Failure to do so may result in the requested approval amount being set against the customer's credit limit which could lead to embarrassment for the client on subsequent use of the card.

Credit cards which can be used with Galileo document production are:

AX American Express (including Optima)

DC Diners Club

CA MasterCard (including Access/Eurobank)

VI Visa

TP AirPlus/Universal Air Travel Plan

JC JCB

It is vital to ascertain that the airline accepts payment from the credit card company as the system does not check if an agreement is in place.

Credit card information can be found in GC*7.

Note: Please be aware that any form of payment entered as a ticket modifier will override any existing Booking File form of payment (F.) entries.



Optional Ticketing Modifiers

HELP TMU ASK ANSWER 8684

There may be additional information that needs to be added to a ticket other than a form of payment and plating carrier. Two of the optional ticketing modifiers are the commission and endorsement entries.

Tour Codes, Commercial Agreement Number (CAR) codes and Value codes used in net ticketing are also added in this way. (Tour Ticketing and Net Remit Ticketing are covered in later modules.)

Commission

When you issue a ticket, the system will automatically default to the commission rates which are held in the commission table provided by Galileo or stored in your AAT table.

However, there may be occasions when this level needs to be amended if an agency arrangement exists with an airline, or the airline have changed their standard commission but not yet advised Galileo. The entry ensures that the specified commission level appears on both the ticket (BSP remit area) and on the BSP sales return.

The entry is added as a ticket modifier update.

Example entry to add zero commission:

TMU1Z0

Entry: Description:

TMU1 Ticketing modifier update for filed fare number 1

Z Commission entry code

0 Amount of the commission.

Screen response:

Note: This entry may also be made independently or combined with additional ticketing modifiers, and may be entered in any order.

Example entry:

TMU1Z5/FNONREF



Endorsements

ASK ANSWER 1631

Endorsements are used on a ticket to specify restrictions applicable to that document. Within the system, endorsements are classified into two categories:

System generated (programmatic) endorsements, automatically added as part of an FQ response

Agent added (manual) endorsements

Galileo will send a maximum of six lines of endorsements, each with a maximum of 29 characters to the e-ticket vendors. However, only three lines with a maximum of 29 characters each can be added manually using a ticketing modifier entry.

Note: Not all characters will display on the issued e-ticket or in the order entered. All airlines have their own restrictions as to the maximum number of characters visable on an issued e-ticket.

Programmatic endorsements will appear on the ticket first. Any endorsements added as TMU entries will appear after.

Here is an example of how a system endorsement appears in the Booking File after a fare quote has been obtained.

The endorsement ‘VALID CY /NONREF/ appears near the bottom of the quote.

You must add a manual endorsement when special restrictions that must be shown on a ticket have not been added automatically as part of the fare quote.

For example, a transatlantic ticket may need to be issued in conjunction with internal US flights.



To add an additional endorsement, a ticket modifier is used.

Example entry: TMU1EBVALID BA ONLY

Entry: Description:

TMU1 Ticketing modifier update for filed fare number 1

EB Endorsement box entry code

VALID….. Endorsement – free format

The system response is ‘TICKET MODIFIERS UPDATED’ and the endorsement is stored at the bottom of the file fare.

If multiple endorsements are required, they must be input together using an asterisk * as a line separator, but the entry code (EB) must be repeated.

Example entry:

TMU1EB VALID BA ONLY*EB VALID FLTS DATES SHOWN*EBNONREF

If you attempt is make separate entries, the system response will be:



Net Ticketing

If issuing tickets for special negotiated discounted fares for certain airlines it may be necessary to manually build the fare and then add specific ticketing data by means of a ticketing modifier entry.

Manual Fare Build is covered in Module 5, Tour Ticketing in Module 6 and Net Remit Ticketing in Module 7.

Here are some of the common entries.

Each format begins TMUn (filed fare number), followed by:


TC12345 Tour Code 12345

IT*PC Inclusive Tour Modifier

BT*PC Bulk Tour Modifier

AI-1234567 Commercial Agreement Reference (CAR) code

VC-C0020 Value Code (supplementary 20% commission)

NFGBP350.00 Net Fare of GBP350.00

Plating Carrier

In most countries, Plating Carrier Logic ensures that the correct carrier is selected and appended to the filed fare. It is generally not necessary to make this entry.

Entry: TMU1CBA

Entry: Description:



C Plating carrier entry code

BA Two character carrier code

The modifier will be added to the fare quote, but will not be visible on the face of the Booking File.



Display the fare (*FF1) to see the results of your entry.

Multiple Modifiers

Ticketing modifiers can be entered separately, or can be combined using an oblique (/) as the separator.

Example entry: TMU1CAZ/FCK

Entry: Description:



CCY Plating carrier entry code and two character carrier code

/ Separator

FCK Form of payment cheque

The system response is ‘TICKET MODIFIERS UPDATED’

Note: Ticket modifiers can be added to the Booking File in any order. The system may not necessarily display them in the order in which they were entered.



Amending/Deleting Ticket Modifiers

The same logic which is used for amending and deleting Galileo reservations entries also applies to any ticket modifiers.

Amending a Modifier

It is very easy for you to amend an existing ticket modifier.

Example entry:

TMU1EB@VALID FLTS DATES SHOWN

Entry: Description:

TMU1 Ticketing modifier update for filed fare number 1.

EB Entry code of modifier to be changed (Endorsement box in this example).

@ ‘Change’ key.

VALID FLTS… New modifier details (In this example, new endorsement in free format).

Note: If more than one endorsement is present, the system will change them all to reflect the new entry. It is not possible to change just a part of an endorsement.

Amending More than One Modifier

To change more than one modifier in one entry, follow this format:

TMU1Z@1/F@CK

This entry will change the commission to 1% and the form of payment to cheque.

Deleting a Modifier

To delete a modifier, follow the usual logic in the Galileo system.

Entry: TMU1Z@

The system response is ‘TICKET MODIFIERS UPDATED’

Note: You cannot delete ‘system generated' (programmatic) endorsements. You can only amend or cancel programmatic endorsements by using a manual fare build entry. This will be covered later in this course.

mailto:TMU1C@BA/F@CK



Module 4 Review

Create a Booking File in your name. Book flights from Frankfurt to Munich with LH on your date, staying for one week, in Y class. Fare quote; the passenger is paying cash for their ticket. End the Booking File and note the Record Locator.

1. What is the entry to add a ticket modifier showing 12% commission for filed fare 1?

2. Now, retrieve the Booking File made at the beginning of this exercise. The client advises you she/he is now going to pay by cheque for their ticket. Make the amendment and write down the entry you used.

3. Now add a manual endorsement to the ticket…’REFUND RESTRICTED’.

4. Prepare the Booking File with any other necessary entry for ticketing so that when the client

returns with the cheque a simple TKP entry will be all that is required. End the Booking File and note the reference below. Finally, issue the ticket and keep it safe as you will need it later in the course.

5. Create a Booking File in your name. Book flights from Chicago to London on UA on your

date, returning 10 days later in Y class. Quote a fare then end and retrieve the Booking File. Make the shortest possible entries to issue an e-ticket and itinerary. The passenger will pay by American Express card number 373900000000000 with expiry Dec 2016. The authorisation has already been obtained – authorisation number 12345. Write down your entries.


Module 5: Manual Fare Build

The Galileo system is capable of quoting most fares automatically. However, there are occasions when this is not possible or when you may elect to use a non-system fare.

In these situations it is possible to enter the fare manually, so that automatic ticketing can take place.

Module Objectives


Create a Manual Fare Build for a single passenger

Create a Manual Fare Build for a multi-passenger Booking File

File manual fares

Amend filed fares

Restore filed fares

There are three basic steps in the process:

1. Create the Manual Fare Build FBC

2. Update / Amend the data FBU

3. File the Manual Fare FBF

Creating a Manual Fare Build Screen (FBC)

HELP FBC HELP FBU ASK ANSWER 332

You will need to build a manual fare for the following fare types:

Consolidated/Negotiated fares

Fares marked with an X in a Fare Display, such as Round the World

Re-routing fares

Fares obtained from an airline, such as an air pass

When you have created and ended a Booking File, you must create a Manual Fare Build Screen in order to construct a manual fare.



Refer to the following Booking File example:

Assume you have a consolidated fare for this routing. It must be added to the Booking File, using the Manual Fare Build process.

To create a Manual Fare in the Booking File, enter: FBCCBA

Note: It is good practice to include the plating carrier in your entry when you create the Manual Fare Build screen.


Points to note:

This is not a Fill-in Format screen. You make all entries at the bottom of the screen and they are then placed automatically by the Galileo system into the appropriate place on the Fare Build Screen.

It is good practice to enter FQTE-00 in another window to establish tax amounts relevant for the journey.

The creation of the Manual Fare Build screen assumes all passengers and all segments are to be associated to the same fare.



If there are different passenger types, or if the fare is only required for certain segments, the Manual Fare Build screen can be created by passenger and/or segment relating.

Example formats:


FBCP5 Fare Build Screen for passenger 5 only

FBCP3-5 Fare Build Screen for passengers 3 through to 5

FBCS2-3 Fare Build Screen for segments 2 and (through to) 3

FBCP2/S2-3 Fare Build Screen for passenger 2, segments 2 and 3

FBCP2-3/CAA Fare Build Screen for passengers 2 and 3 for plating carrier AA

It is also possible to create a Manual Fare Build screen for a particular passenger description code.

Example formats:


FBCP5*C08 Fare Build Screen for passenger 5, a child aged 8 years.

FBCP2*C08.1 Fare Build Screen for passenger 2, a child aged 8 years, plus passenger 1 adult.

If no passenger description codes are used, the system will default to adult (and also infant if one is included in the Booking File).



Manual Fare Build screen fields

The following fields may be completed. The @ symbol indicates a mandatory field.


FB/TD Fare Basis/Ticket Designator

NVB NVA Not Valid Before / Not Valid After dates

BG Free baggage allowance

FARE Fare in the currency of the country of origin

EQ Equivalent amount paid (if the fare is paid in another currency)

ROE IATA Rate of Exchange

Note: Although this is indicated to be a mandatory field, it is possible to file a fare without including the ROE. However, it is advisable to include it for all international journeys.

TAX Country taxes in the currency of payment

TTL Total of Fare and Taxes.

Note: This field is automatically generated when the Fare and Taxes are added to the Manual Fare Build screen.

FC Fare construction

Note: If any of the mandatory fields are omitted, you will not be able to end the Manual Fare. Optional fields may be completed as required by IATA ticketing standards.



Updating the Fare Build Screen (FBU)

HELP FBU ASK ANSWER 332

The Fare Build Screen must be completed using Fare Build Update entries. You can make individual entries, or link a string of entries using the plus + key.

The format for Fare Build Update is: FBU

Refer to the following example entry to update the Fare Build screen with the Fare Basis YSPCL

Enter: FBUFB/YSPCL

Entry: Description:

FBU Fare Build Update

FB Function identifier (Fare Basis)

/ Separator

YSPCL Information to be entered (the fare basis code)

The system response is:

The system clears the screen when it makes this response. You must make a display entry if you want to recall the Fare Build Update screen.

Enter: *FB




Note: The Fare Basis has been added.



Complete the Manual Fare Build with the following information. It is not necessary to re-display the Manual Fare Build screen, and information can be added in any order.

Fare details:


FBUFB/YSPCL Fare Basis/Ticket Designator

FBUNVB1/01SEP14

FBUNVA1/01SEP14

FBUNVB2/09SEP14

FBUNVB2/09SEP14

Segment 1 Not Valid Before / Not Valid After 1 September 2014


FBUBG/2PC Free baggage allowance 2 pieces

FBUFARE/GBP990.00 Fare in the currency of the country of origin

EQ Equivalent amount paid (if the fare is paid in another currency)

FBUROE/0.610616 IATA Rate of Exchange

Note: Although this is indicated to be a mandatory field, it is possible to file a fare without including the ROE. However, it is advisable to include it for all international journeys.

FBUTAX1/69.00GB+TAX2/39.75UB+TAX3/1.50AY+TAX4/21.20US+TAX5/3.00XA+TAX6/2.70XF+TAX7/4.30XY+TAX8/3.30YC+TAX9/213.00YQ

Country taxes in the currency of payment.

TTL Total of Fare and Taxes.

Note: This field is automatically generated when the Fare and Taxes are added to the Manual Fare Build screen.

FBUFC/LON BA NYC810.65YSPCL BA LON810.65YSPCL NUC1621.30

Fare construction

Note: Use the + symbol to string entries together.



Enter as follows:

FBUBG/2PC+FARE/GBP990.00+ROE/0.610616

FBUNVB1/01SEP14+NVA1/01SEP14

FBUNVB2/09SEP14+NVA2/09SEP14

FBUTAX1/69.00GB+TAX2/39.75UB+TAX3/1.50AY+TAX4/21.20US+TAX5/3.00XA+TAX6/2.70XF+TAX7/4.30XY+TAX8/3.30YC+TAX9/213.00YQ

FBUFC/LON BA NYC810.65YSPCL BA LON810.65YSPCL NUC1621.30

Note: The system clears the screen each time you enter a single item or string of formats.

Enter *FB to recall the Fare Build Update screen.

Note: The TOTAL is automatically when the fare and taxes are added to the screen.



Segment Related Entries

The NVB and NVA dates above are segment related. Fare Basis and Baggage fields can also be segment related.

Example formats:


FBUFB1/YSPCL+FB2/YLXA Fare basis for segment 1 is YSPCL

Fare basis for segment 2 is YLXA

FBUBG1/23K+BG2-3/2PC Free baggage allowance for segment 1 is 23 kilos.

Free baggage allowance for segments 2 and 3 is 2 pieces.

FBUNVB1/01SEP14

FBUNVA1/01SEP14

FBUNVB2/09SEP14

FBUNVB2/09SEP14



Note: The line number used in segment related entries is the number shown on the far right of the Fare Build Screen.

This is not necessarily the segment number in the itinerary. The Fare Build Screen ignores any ARNK segments for numbering purposes.

Baggage

FBUBG/NIL allows you to add nil value for baggage allowance.

Taxes

Eight taxes can be accommodated on the initial Manual Fare Build screen, but the tax field can be expanded if required.

If more than eight taxes apply, those from the eighth tax onwards will be grouped together in Tax field 8 with the code XT.



You can expand the tax field to show a maximum of 20 taxes if required.

Enter: *FBTAX


Note: The two taxes previously combined with the code XT are now displayed individually in Tax fields 8 and 9.

More than 20 Taxes

If you have more than 20 taxes to be added to a fare, contact the ticketing carrier. They may suggest that you combine additional taxes and specify the tax code that you should use.

Enter the detail of each tax at the end of the fare construction. It is not possible to use XT.

Passenger Facility Charges

When you complete the Manual Fare Build Screen, you must pay particular attention to the Passenger Facility Charge (PFC).

The PFC enables airport authorities to collect a user fee from the passenger to fund airport development.

In addition to the tax entry for the PFC amount (code XF), you must specify the airport for which it is applicable.

The entry to add this information is in the same format, but it must be made on its own, it cannot be made as part of an FBU string.

Entry: FBUPFC/JFK4.5

Entry: Description:

FBU Fare Build Update

PFC Code for item to be updated (Passenger Facility Charge)

/ Separator

JFK4.50 The airport code (JFK) for which the tax applies, and the amount in USD (4.50).



The system is not able to validate the airport and the value, or that the PFC entry matches the XF tax entry.

Refer to FTAX*PFC–XXX (where XXX= three letter airport code) for the current amount to be charged for each airport.

A maximum of four PFCs are allowed. When more than one PFC is to be added to the Manual Fare Build, all PFCs must be input as a single entry.

For example: FBUPFC/JFK3BUF3DEN4.50PHL4.50

Note: The PFC amount must be specified in USD, regardless of the point of sale.

The PFC appears on the Fare Build Screen in the Fare Construction line. It can only be entered after completion of the fare construction line:

Flight Segment Tax (US domestic journeys only)

Flight Segment Tax applies in addition to Domestic Transportation Tax. It is levied on each passenger for each flight segment which is subject to Domestic Transportation Tax.

Note: It is levied when payment is made in the USA.

The amount collected must be specified using the tax code is ZP. The tax breakdown is identified against the applicable airports, e.g. LAX and SFO.

Example entry: FBUTB1/ZPLAX2SFO2.50

Endorsements

Endorsements can also be added as part of the fare build process, even though they are not actually part of the FB screen. They must be entered separately from other FBU entries.

Example entry: FBUEB/NO CHANGE OF RES



Filing the Manual Fare (FBF)

When you have completed the Manual Fare Build screen, you must file it in order to store the fare.

There are a number of formats for filing:


FBF File current passenger screen.

FBFALL File current passenger screen and the same details for all remaining passengers. (See next section).

FBFCUA File current passenger screen with plating carrier UA (if not used in FBC entry)

FBFALL/CQF File current and all remaining passengers with plating carrier QF.

Example screen response

:

To display the Filed Fare, enter: *FF1


Note: The status of fare shows B (Manually Built fare).

End the Booking File in the usual way.



Multiple Passengers and Passenger Descriptions

When a Booking File is created for more than one passenger, you must identify each passenger description, such as a child or an infant.

Refer to the following Booking File:

Create the Manual Fare Build screen.

Enter: FBCCBA


The system creates a Manual Fare Build Screen for each passenger. The header line shows P01 (Passenger 1) and 01 of 03, i.e. the first of three screens.

Once you complete the first screen and file it (FBF), the next Fare Build Screen will appear automatically for passenger 2, and then for passenger 3.

However, once the first screen has been completed, you can file identical fare information for all remaining passengers with one entry.

Enter: FBFALL

Entry: Description:

FBF Fare Build File

ALL All passengers

The system response will be: FILED FOR ALL PASSENGERS – TOTAL GENERATED.



Similar logic applies when there are different passenger types in the Booking File.

Refer to the following example where passengers 1 and 2 are adults, and passenger 3 is a 9 year old child.

As there are two passenger types in the Booking File, you must complete at least two Manual Fare Build screens.

You would think that the entry to organize the Fare Build screens would be:

FBCP1.2.3*C09/CBA

However, the system works logically and will display the screen for passenger 1 first.

After you complete the first screen, you could not use the entry FBFALL because passenger 3 (a child), requires a different fare to the two adult passengers.

You would be required to complete the second screen for the second adult, and finally complete the third screen for the child.

The most effective way to action this scenario is to begin the entry with the smallest group of passengers – in this case the child.

Enter: FBCP3*C09.1.2/CBA

The Manual Fare Build screen for the child will be presented first.


When you complete this screen and file it (FBF), the child fare will be filed, and the first adult (passenger 1) screen will be displayed.

When you complete the first adult screen, use the entry FBFALL to file the same Fare Build information for all remaining passengers.

Using this process, all three screens will be stored under one filed fare in just two, rather than three, transactions.



Alternately you can create one Manual Fare Build screen for all passengers, and complete it as if all are adults, and file it with FBFALL.

Then redisplay the Manual Fare Build screen for the child with the entry *FB1P3*C09. Amend it with the child details, and file it with FBF.

Exception

In some cases, such as for Net Remit tickets, separate filed fares must be created as separate ticket modifiers are added for each passenger description.

Enter: FBCP1.2

This will present a Manual Fare Build screen for both adults, known as filed fare 1. This can then be updated and filed.

Enter: FBCP3*C09

This will present a Manual Fare Build screen for the child, filed fare 2, which can then be updated and filed.

Amending a Filed Fare

You can retrieve and amend an automatic fare quote or a manual fare at any time before ticketing.

Fields can be amended or deleted.

Take the following steps to amend a field:

1. Display the Filed Fare. Enter *FB1 to display Fare 1 in Fare Build Format.

2. Use FBU entries as appropriate to amend the existing data.

3. File the Fare Build. Enter FBF.

For example: FBUBG/20K will change the baggage allowance to 20K.

The entry will just ‘overwrite’ the current content in the fare field.

Deleting a field

A field can be deleted by re-entering the first part of the Fare Build Update entry and omitting any data after the oblique (/).

For example: FBUEB/ will delete all endorsements.

Important note: When you amend an automatic fare quote using Manual Fare Build Update, the fare guarantee status code will change from G or C to B.

The Baggage Allowance and Taxes can be changed without losing the guarantee. However any changes to the FBUPFC/ and FBUTB1 entries will cause the guaranteed to change to B.

The Baggage Allowance can also be amended and the original guarantee retained by making the following example entry: FF1BG30K.



Ignoring a Manual Fare Build

If you wish to ignore the current Manual Fare Build screen (maybe you have made an error and wish to begin again), make the following entry:

FBI

The system response is: MANUAL FARE IGNORED.

Restoring a Filed Fare

Situations may occur when you need to issue a ticket for a second time.

When you issue a ticket, the ticket number is stored in the Booking File as part of the filed fare. If you attempt to issue another ticket for the same passenger and journey, the system will respond with:

ERROR 3086 – ALL FILED FARES ARE TICKETED.

To issue the ticket again (after you have voided the original ticket), you must restore the fare in the Booking File.

Enter: FF1@R

Entry: Description:

FF1 Filed Fare number 1

@ Amend or Change

R Restore Status

Note: Restored filed fares are not guaranteed. Once restored, you can make normal ticketing entries.

To restore a filed fare for passenger 2, the entry would be: FF1P2@R



Module 5 Review

Create Booking Files, in 6 months’ time for questions 3 and 4.

1. What is the entry to create a Manual Fare Build screen with plating carrier BA, for passenger 3 of a Booking File?

2. What is the best entry to create Manual Fare Build Screens for four passengers, where

passenger 4 is a child who is 8 years old?

3. Create a Booking File for one passenger, in your name. LHRCDG 21st, CDGFCO 24th, FCOLHR 27th, all in Y class (use AF and AZ). Add mandatory fields, end and retrieve the Booking File. Note the Booking File record locator.

Build a Manual Fare using the following information. Advise your trainer when you have completed the fare. File the fare and End Transaction; do not issue the ticket yet.

Field: Description:

Fare Basis C for segments 1 and 2

YBB for segment 3

Baggage allowance 30K for segments 1 and 2

20K for segment 3

Fare GBP 500.00

ROE 0.61

Fare Construction LON AF PAR AZ ROM M414.42AZ LON M414.42NUC 818.84

Tax 13.00GB

28.74UB

14.20FR

0.80IZ

9.90QX

1.70EX

6.20HB

13.20IT

0.70MJ

2.10VT

74.40YR

Endorsement ROMLON CANCEL PENALTY APPLIES



4. Create a Booking File for three passengers, using your name and 2 others. Passenger 3 is a child aged 10 from FRAIAH 10th return 24th in Y class with Lufthansa (LH). Add mandatory elements, end and retrieve the Booking File.

Build a Manual Fare using the following information:

Field: Description:

Fare Basis Adult: BWKND

Child: BKWND/CHYBB for segment 3

Baggage allowance 2PC

Fare Adult: EUR 599.00

Child: EUR 300.00

ROE 0.73

Fare Construction Adult: FRA LH HOU R414.23LH FRA R414.23NUC818.46

Child: FRA LH HOU R212.11LH FRA R212.11NUC414.22

Tax 5.40DE

34.90OY

26.90RA

1.50AY

21.20US

3.00XA

1.80XF

4.30XY

3.30YC

218.60YQ

Endorsement NO REFUND / NO CHANGES

File the fares and prepare the Booking File for ticketing by adding the mandatory ticket modifiers - you may choose the form of payment. Do not issue tickets. Call your trainer before ending transaction.

End Transaction and make a note of the Booking File reference.



5. Retrieve the Booking File from question 3 of this review.

The fare has changed. It has been reduced by GBP10.00 in each direction and the revised details are as follows:

Fare GBP 480.00

Fare Construction LON AF PAR AZ ROM M393.04AZ LON M393.04NUC 786.08

Make the necessary entries to amend the Filed Fare. Now issue the ticket only, and make a note of the ticket number. We will use it in a later session.


Module 6: Tour Ticketing

Many agencies have special arrangements with airlines whereby they have negotiated discounted air fares that they can sell to their passengers. These generally fall into the categories of Bulk and Inclusive Tour tickets.

In order to sell these fares there are rules that an agency must follow, such as selling the fare in conjunction with accommodation. The money paid by a customer for a Bulk or Inclusive Tour ticket often includes payment for hotel accommodation or tour excursions, in addition to the flights.

There are IATA regulations as to the information that should be printed on the ticket and therefore available to the traveler if they look at their itinerary on ViewTrip.com.

Module Objectives


Add tour code modifiers to issue tickets for Inclusive and Bulk Tours in line with IATA regulations

Tour Ticketing

ASK ANSWER 105

When a tour ticketing agreement is made between a travel agency and an airline, the airline will provide the agency with a contract stating details of the fares and the associated rules. This includes details of the ticketing data required. This information may be kept in paper form or in a fares database.

When you quote and sell one of these fares, it is usual practice to complete the reservation and then build the fare manually into the Booking File ready for ticketing. Due to the nature of these tickets and the information that needs to be shown on the ticket / ViewTrip, additional modifiers need to be added.

Note: Many agencies now obtain fare quotes automatically as the fares have been loaded via Agency Private Fares or are Category 35 Airline Private Fares. These fare types already contain required ticketing data and this cannot be modified

The following ticketing modifiers, prefixed by the TMU field identifier and the filed fare number and linked to a commission modifier, can be used to produce tour tickets.



Tour Code Modifier (TC)

A tour code modifier is issued by an airline in order to identify the deal an agent has been given. The tour code has to be entered into the fare as a ticket modifier in order that both the airline and the local BSP know the source of the fare and that the agency has authority to use it.

The Tour Code modifier is TC, followed by the Tour Code with a maximum of 14 characters.

Example entry: TCXX123456

Inclusive Tour Modifier (IT)

IT identifies an ‘Inclusive Tour’ fare. In order to sell an IT fare, your agency will usually have to have sell accommodation or other ground arrangements, as part of a ‘package’.

European law states that for a product to be sold and marketed as a package, the cost of the individual elements should not be identified to the client.

For example, if a package is sold at a cost of GBP 500.00, it should not be broken down and the passenger advised that the flight element cost GBP 300.00 and the accommodation element cost GBP 200.00.

Because of these restrictions, the fare that is printed on the ticket or available in ViewTrip.com must be inhibited from printing. For this reason the Inclusive Tour modifier IT must be added.

IT will appear in the fare and total fare box regardless of the fare that was charged. The taxes paid will be visible. For automatic fare quotes, the NUC fare values will be replaced by M/IT.

For any manually built fares, the fare construction will print exactly as stored in the fare quote. If no fare values are to be shown they should be omitted from the fare calculation (e.g. LON KL AMS KL LON).

Bulk Tour Modifier (BT)

BT signifies a ‘Bulk Tour’ fare. It is a very similar concept to that of an IT fare. However there is usually not the restriction of accommodation being sold in order to take advantage of the fare.

BT fares are usually given to agencies who book a high volume of seats such as a consolidator or wholesaler.

BT will appear in the fare and total fare box regardless of the Filed Fare. For automatic fare quotes, the NUC fare values will be replaced by M/BT. For any manually built fares, or fares which have been amended by fare build entries the fare construction will print exactly as stored in the fare quote.



Commissions

When selling a BT or IT fare, commission levels are reduced to 0% using the ticket modifier format Z.

Example entry for an Inclusive Tour:

TMU1TC02315478/Z0/IT

Entry: Description:

TMU1 Ticket Modifier Update for filed fare 1

TC Tour Code entry code

02315478 Tour code reference number

/Z0 Separator and Commission percentage (0%)

/IT Separator and code to go in fare and total box of the ticket (Inclusive Tour)

Booking File example:

E-ticket example (automatic fare quote):

Note: The NUC values from the fare construction have been replaced



with M/IT.

Example entry for a Bulk Tour:

TMU1TC02315478/Z0/BT

Fare example:

E-ticket example (manual fare quote):

Note: The fare construction is printed exactly as it was entered in the manual fare build. The Galileo system does not replace fare values with M/BT or M/IT.



Module 6 Review

1. True or false? In order to issue an IT fare, a travel agent usually has to sell the fare in conjunction with accommodation?

2. What entry is used to show BT in the fare and total box of the ticket?

3. In addition to adding a TC and either a BT or IT modifier when issuing a tour ticket, which

other modifier should also be added?

4. You are working in a travel agency that specialises in short breaks to New York. You have negotiated a deal with Virgin Atlantic. They have issued you with a BT contract that enables you to offer extremely reasonable rates to your passengers.

On your date, create the following Booking File

Your date LHR-JFK Y class with Virgin Atlantic, returning five days later. Use your name as the passenger name. Your agency is called USA Experience and the phone number is 01234 567890. Use PAUL as the agent reference. Add all other mandatory fields and end the Booking File, taking a note of your Galileo locator. Build the fare including the following information:

Fare Basis YSPCL

BG 2PC

Fare GBP448.00

ROE 0.547411

Taxes 20.00 GB, 11.90 UB, 1.40 AY, 15.60 US, 2.80 XA, 1.70 XF, 3.90 XY, 2.80 YC, 53.00 YQ

PFC JFK USD 4.5

Fare Construction LON VS NYC 409.19YSPCL VS LON 409.19YSPCL NUC818.38

Endorsements VALID VS ONLY NO CHANGES NO REROUTE

Tour Code VS12345

BT/IT BT

Commission 0%


Module 7: Net Remit 2

A Net Remit fare is a fare that is purchased by a travel agency from an airline at an agreed rate. Once it is sold to the passenger, it is at the discretion of the travel agency as to any additional “mark-up” that is added to the fare.

This type of fare is purchased at a “net” rate by the travel agency. It is then marked up and sold - this is known as a gross or selling fare.

The following information is relevant for tickets issued for route deals and consolidation fares, to ensure accurate electronic reporting to BSP. The data required when creating net remit tickets will be provided by the airlines with which you have agreements.

Note: Many agencies have special arrangements with some carriers, where they are given a special fare and a different fare is often shown on the ticket

Module Objectives


Enter Net Remit modifiers into a Filed Fare

Modifiers

ASK ANSWER 3536

There are three different modifiers which may apply to Net Remit.

AI– Airline Information

VC– Value Code

NF Net Fare

It is mandatory to use the AI– modifier every time a Net Remit fare is built. Optionally, either a VC– or NF modifier can be used.

The airline will advise you what is required when they finalize the agreement with your agency.

The use of the AI– modifier will force the printing of ‘NR’ in the BSP remittance area of the ticket.

Note: Net Remit requirements vary in different countries. For example, BSP requirements for Net Remit tickets issued in the UK may vary from those issued in Denmark.

These entries are made using ticket modifiers (TMU). They are added after a filed fare has been obtained either via an FQ entry or, more usually, from a manual fare build.



Airline Information AI–

This is often referred to as a ‘Deal Number’, although officially it is called a ‘Commercial Agreement Reference’ (CAR). This may be free format of two to eight alpha/numeric characters.

When a deal is agreed between an airline and an agency, the Deal Number is advised to the local BSP. Once electronic reporting takes place, BSP cross checks the deal number with the information supplied by the airline to ensure that the agency is authorized to sell this type of fare.

Normally an airline will provide your agency with the reference number and a base (net) fare will be agreed. The agency then sells on to the public at whatever rate the market can sustain and makes its money from difference between the two. There is no commission on the fare.

Example entry: TMU1AI–45678

Entry: Description:

TMU1 Ticket Modifier Update for filed fare 1

AI– Airline Information entry code

45678 Airline supplied reference number

Note: BA has a 7 numeric number with the seventh character as a check digit. When the AI– modifier is input, a link is activated between BA and the Galileo system to validate the entry. If the modifier is incorrect, the Galileo system will display an error message and the information must be re-entered.

A second check occurs when the tickets are issued. If the AI– number is correct but has not been loaded onto the BA database an error message will display and the ticket will not issue.

System checks are not carried out with all other airlines, and therefore, it is essential that the airline information data is correctly entered.

Fare quote example:



NR Ticket Entry

Whenever the AI– modifier is used, the CAR code will show as a “Tour Code’ in the e-ticket.

Note: The AI– entry may be the only entry required or it may be used in conjunction with VC– or NF.

Value Code VC–

The Value Code is used by some airlines in order that their own revenue accounts department can interpret the type of ‘arrangement’ which the airline has agreed with the agent.

The entry code, VC–, is followed by one of two alpha characters, either K or C. These identifiers indicate different types of arrangement.

The airline will then advise additional numeric or alpha characters to a maximum of 4. (Letters I and O are not normally used as they can be mistaken for 1 or 0).

Note: In some countries with some airlines, this entry is automatically added when the AI– entry is made. In other countries agents must add it as a modifier.

VC-C

VC–C indicates the supplementary percentage commission on a net fare. The net fare is the fare after the deduction of standard commission.

Example: C0020 indicates supplementary 20% commission.

Gross Fare 200.00

Standard 1% commission 2.00

Supplementary 20% commission (on 198.00) 39.60

Total commission 41.60

Amount paid by agent 158.40

Example entry: TMU1AI–45678/VC–C0020



Fare quote example:

Note: The Value Code does not show on the e-ticket record but is transmitted to BSP.

VC-K

VC–K Indicates the supplementary amount of commission due to the agent in local currency.

For example, K0025 indicates supplementary commission of GBP25.00 if tickets were issued in London. The system assumes the currency code based on the country in which the ticket is being issued. The system would assume EUR25.00 if the ticket was issued in Dublin.

Example entry: TMU1AI–45678/VC–K0025

Points to note:

Remember that these codes are supplied by the airline

The airline will send required procedures to the issuing agent specifying what should appear on the ticket

It is important that these instructions are followed carefully and if in any doubt, contact the airline for clarification

Procedures vary in each country and with each airline

Net Fare NF

Using the NF modifier allows a selling fare to be shown in the ‘Fare’ box on the ticket and a different amount shown in the remittance area. This can be achieved using an auto-quote fare or by using a manually built fare.

The commission rate will always remain at the standard level unless entered as a ticketing modifier (e.g. TMU1Z0)

Assume the selling fare is GBP 1325.00 and the net fare is GBP 1200.00.

Example entry: TMU1AI–45678/NFGBP1200.00



Fare quote example:

Note: The ticket will show the selling fare GBP1325.00 in the FARE box and GBP1200.00 in the Remittance area.

General Information

Note the following points:

Net Remit tickets cannot be issued in the system using FEX as the form of payment.

Credit cards are not acceptable forms of payment.

A separate fare quote must be filed for each different passenger description (ADT, CNN and INF), to which ticket modifiers must be added, e.g. TMU1, TMU2, TMU3, etc.

The existence of ‘NR’ in the remittance area will generate a supplementary commission report at the same time as the normal BSP report is produced.

The TINS Report will reflect the amount shown in the fare box followed by a ‘G’ to indicate ‘GROSS’.

If the AI– modifier has been used it will be displayed under the passenger name.



Module 7 Review

1. When creating Net Remit fares modifiers AI, VC- and NF are used. Which of these modifiers are mandatory?

2. What is the difference between the VC–K and VC–C modifiers?

3. When issuing a Net Remit ticket, the cost at which the agency buys the ticket often differs

from the price that they sell it to a passenger. Which modifier allows a different amount to the published fare to be reported to BSP?

4. Your agency has a commercial agreement number G54309X. What is the entry to add a Net

Remit modifier showing an airline Value Code of 15% to filed fare 1?


Module 8: Ticket Revalidation

When a passenger makes a change in his/her flight arrangements it is sometimes possible to alter the ticket he is holding rather than re-issue it completely. This is called revalidation.

Revalidation of tickets is governed by IATA rules. Before proceeding to revalidate a ticket, you should make sure the IATA rules and the fare rules have been followed.

IATA states that travel agents may only revalidate a ticket to the same carrier, fare, class and routing. It is not possible to revalidate any past date segments or to revalidate a closed flight to an open segment.

Module Objectives


Revalidate an e-ticket

Revalidation

ASK ANSWER 401

You can revalidate a ticket when a passenger has changed their booking, but the fare, carrier, class and routing remain the same.

If you forget to revalidate the e-ticket, the reservation in the Galileo system and the airlines hosting system will not match the e-ticket data that is held in the airlines e-ticket server.

Note: Not all airlines permit revalidation, in which case the ticket must be reissued with no additional collection. Refer to Exchange Ticketing Module 9.

No history of Revalidation is available.

To check if an airline supports e-ticket revalidation refer to ASK Travelport answer 8430:

Where can I find e-ticketing functionality information for all carriers participating in Galileo?

In order to proceed with revalidation, retrieve the relevant Booking File and make the necessary amendments for the customer.

Once the Booking File has been displayed and amended, end and retrieve (ER). The revalidation input can then be made.

Note: When the reservation is changed the original filed fare will be cancelled. In a revalidation situation it does not matter that you do not have a filed fare in the booking as in revalidation, the fare must equal that of the original reservation.



Refer to the following example Booking File.

The e-ticket shows the date for the old reservation until the revalidation is made.

Note that segment 1 was originally booked for 1 September, and the ticket number issued was 1259901891920. The Booking File has been displayed, amended, received, ended and retrieved again.

You can now make the revalidation entry:

TKRETS1/TN1259901891920/C1

Entry: Description:

TKR Ticket Revalidate function identifier.

ET Electronic Ticket

S1 Segment 1 of the itinerary

TN1259901891920 Ticket Number including the 3 digit airline code

/ Separator

C1 Coupon 1

The system response is:



The e-ticket record is now revalidated and matches the information in the Booking File.

Note: Check that the *SI field still contains the ticket numbers for each passenger and segment after you have made changes to the Booking File. If not, you must manually re-enter them.

Validity dates

Validity dates can also be appended to the revalidation entry.

Example entry:

TKRETS2/TN1259900542415/C1/NVB02SEP14/NVA02SEP14

Infant tickets

Infant tickets can be revalidated with the addition of the two letter code IN.

Example entry:

TKRETS2/TNIN1259900281382/C2

Revalidating an E-Ticket after the Passenger has been Divided out

A situation may occur when an e-ticket record cannot be displayed in a Booking File and you wish to revalidate it.

This happens when a passenger is divided out of a Booking File after the tickets have been issued. The e-ticket records for all passengers remain with the original Booking File.

However, you are still able to revalidate the ticket.

Make the changes to the divided Booking File, and then enter:

*TE/1259900599315 to display the original e-ticket.

Revalidate in the usual way by making the entry: TKRETS2/TN1259900599315/C2



Revalidating British Airways E-Tickets

ASK ANSWER 402

British Airways allows passengers to check in on line using www.ba.com up to 24 hours in advance of the scheduled flight departure time.

There may be occasions when a passenger has checked in online or used a BA self-service check-in kiosk, and then their plans change and their e-ticket must be revalidated.

Once checked in the status of the e-ticket changes to CKIN. With this status code, the ticket cannot be revalidated.

However, it is possible to make an entry in the Booking File, which enables an automated process at British Airways to change the status to OPEN or APRT. The e-ticket can then be revalidated.

The following format added to the Booking File enables the automated process to take place at British Airways and allows subsequent revalidation to be carried out in your agency.

Example entry:

SI.BA*OFLD.BA005/LHRNRT/28SEP

Entry: Description:

SI. Function identifier

BA* Two letter carrier code for British Airways followed by an asterisk ( * )

OFLD Keyword identifying that you wish the passenger to be ‘offloaded’ from the flight for which they checked in

. Separator

BA005 Flight number

/ Separator

LHRNRT Routing

/ Separator

28SEP Date of travel

The system response is: CHANGE ETKT STATUS RQST ACTIONED

Once you receive the message above, the automated system at British Airways will change the status of the e ticket back to OPEN or APRT and you will be able to process the revalidation for your client. The process usually takes about five minutes.

British Airways Known Error Messages

The table below lists some of the error responses that you may receive



from British Airways, the reason and the subsequent action you need to take in order to revalidate the British Airways e ticket.

Response: Reason: Action:

UNABLE TO CHG ETKT STATUS/PLS SPLIT PNR/CTC TRADE SUPPORT

Multiple passengers are in the Booking File

Split the affected passenger from the Booking File, remove the service information entry and re-enter. If all passengers in the Booking File need their e tickets revalidated contact Trade Support at BA

UNABLE TO CHG ETKT STATUS/DUPLICATE NAME/CTC TRADE SUPPORT

More than one passenger of with the same initial and surname

Contact Trade Support at BA

BAGS CHECKED IN / PAX MUST CTC CHECK IN

Passenger has already checked in their luggage

Passenger must have ticket revalidated by BA staff at the airport

UNABLE TO CHG ETKT STATUS/FLIGHT LOCKED/CTC TRADE SUPPORT

For whatever reason the airport have locked the flight

Remove the service information entry and try again in a few minutes. If this fails, contact Trade Support

UNABLE TO CHG ETKT STATUS/ CTC TRADE SUPPORT

Unable to locate passenger on requested flight or the passenger may have boarded this or a different flight

Check that the keyword, flight number, routing and dates are added correctly. If this fails, contact Trade Support



Module 8 Review

1. What must you check before you revalidate a ticket?

2. You have been handed ticket number 236 440 265 7861 issued on 29 August. What is the

revalidation entry for segment 3, coupon 3?

3. What entry would you use to offload a passenger from BA 107 LHR to DXB on 3 August?


Module 9: Exchange Tickets

Sometimes a passenger will change their plans after their ticket has been issued. They may wish to change their travel dates or itinerary.

Depending on the fare, it may be possible reissue the ticket for your customer, and give them a new one in exchange for the original one.

There are strict IATA rules governing this procedure, which can be learned on Advanced Fares and Ticketing Courses. This module focuses on the procedure to reissue a ticket.

You must refer to the fare notes or the issuing airline to check the rules and regulations in order that you complete the ticket exchange correctly.

Note: Many agencies make a charge for exchanging a ticket, and this can be an important source of revenue.

Module Objectives


Identify when a ticket can be revalidated or when it should be exchanged

Complete a ticket reissue using a fill-in format (FIF)

Reissue tickets with and without an additional collection

Reissue a ticket issued in a different currency

Cancel/Void an incorrectly reissued ticket

Ticket Exchange or Revalidation

HELP EXCHANGE ASK TRAVELPORT > EXCHANGE TICKETING (many examples)

The terms Exchange and Revalidation often get confused. If a passenger changes their dates of travel after the ticket has been issued, but the fare, airline and routing stays the same as that on the original ticket, you may be able to revalidate the ticket.

However, not all airlines support this function. To check if an airline supports revalidation, refer to ASK Travelport answer 8430:


If there is a change to the airline, routing or fare, you must exchange the ticket. You must check the fare rules; the fare may be non-changeable, or there may be a fee to change.

Note: Often a ticket exchange is referred to as a re-issue. When you return to your agency, you will hear colleagues talking about ticket exchange, exchange ticketing or re-issue. They are talking about the same subject.



Exchange Fill-In Formats

The Galileo system has a fill-in format to help you with the procedure to issue a new ticket in exchange for an old one.

The fill-in format is displayed by entering TKPFEX followed by the full ticket number including airline code. A fill-in format appears, although the majority of it is completed automatically by the Galileo system.

For multiple passenger Booking Files a separate fare quote entry or manual fare build must be made for each passenger. Individual TKP entries must completed with the relevant filed fare and original ticket number.

This is an example of the blank exchange screen.

Screen description:

Lines: Explanation:

2 and 3 Detail of the new fare and new taxes for the new document

4 - 9 Detail of the exchanged document

10 - 11 Detail of the original issue

Steps to Reissue a Ticket

Take the following steps to reissue a document:

1. Modify/create the Booking File

2. Quote a fare for the new journey for each passenger

3. End and retrieve the Booking File

4. Enter the form of payment modifier TKPPFEX and the ticket number

5. Complete the exchange fill-in format

6. Complete the additional collection fill-in format as necessary or process a refund

Note: The ticket will issue automatically.



How to Use the Exchange Ticket Fill in Format (FIF) screen

First of all, make the changes to the Booking File and obtain a new fare, either through an automatic fare quote or a manual fare build.

Note: Remove any taxes that have been paid previously on the original ticket or the passenger will be charged for them again.

Helpful hints when exchanging an e-ticket:

Display the filed fare and the full tax breakdown of the original booking before you begin the exchange process (FQ or FQTE-00)

Remove any paid taxes by displaying the relevant filed fare as a fare build (*FB1), regenerate the total and file the fare (FBF)

Example 1 – No Additional Collection – Unused ticket

Refer to the following ticketed Booking File for travel from London to Edinburgh:

The passenger now wishes to fly to and from Glasgow instead.

The original fare was GBP490.00 plus 26.00GB, 38.78UB and 37.00YQ. The fare basis code was JV3RO.

Always refer to paragraph 16 of the fare notes to check that changes can be made at this fare. The rule states:



Take the following steps to reissue the ticket:

1. Make the necessary changes to the booking.

2. Quote a fare for the new journey. Enter FQ

In this example, the fare and taxes are the same, and therefore the taxes must be removed from the new fare, to prevent the customer being charged for them twice.

3. Amend the new fare to remove the paid taxes and amend the Total.

Enter: *FB1


Enter: FBUTAX1/+TAX2/+TAX3/ The taxes have now been removed. Regenerate the TOTAL.

Enter: FBUTTL/



Completed screen example:

4. Re-file the updated fare.

Enter: FBF. Add a Received From field and enter ER

5. Obtain a fill in format (FIF) screen by making a ticketing entry with the Form of Payment as EX followed by the original e-ticket number. The check digit is not required.

6. Enter: TKPEX1259901891924 Example screen response:

Note: The majority of the required fields have been automatically completed by the Galileo system. The top section shows the new fare and any new taxes. Data in this section cannot be amended

The middle section shows the original ticket number and previously paid taxes.



Description of Fields

Item: Explanation:

TICKET FOR Passenger name automatically placed here from the filed fare.

NEW FARE New fare automatically placed here from the filed fare

TX1 to TX4 All taxes from the filed fare displayed here

EQUIV If applicable, the currency codes (not the amount) of the original currency of issue and of the additional collection are shown here from the updated fare. A maximum of three currency codes may be added, with a space between each

TKT NO The ticket number completed automatically

THRU If exchanging conjunction tickets, enter an X. Otherwise leave blank.

TKT NO Enter the last conjunction ticket of the sequence (including the check digit). If not applicable, leave blank.

NO CPNS The number of flight coupons to be exchanged. For example, 02 will be automatically added by the Galileo system.

COUPONS FOR The coupons to be exchanged will be added automatically by the Galileo system. For example, 12 signifies coupons 1 and 2.

PD TAXES All paid taxes shown individually are displayed here. It is not permitted to show a combined total using XT.

TTL VALUE The original fare excluding taxes is shown here together with the currency code, e.g. GBP490.00

BSR If working with different currencies, enter the Bank Selling Rate according to the FZS entry.

Prefix the BSR with an oblique (/) to divide. If the BSR contains more than four numbers, ignore the last one.

ORIG FOP Enter the form of payment used on the original ticket, e.g. NONREF.

If the form of payment was credit card, enter CC.



Item: Explanation:

*ORIG ISSUE* This section relates to the original ticket.

TICKET NUMBER If the ticket being exchanged has previously been reissued, you must show the original ticket number here.

ORG/DES Enter the origin/destination of the whole (new) journey, using city codes (not airport codes).

For example, the ORD/DES codes for an itinerary STN TLV STN would be shown as LONLON.

Note: This field must be manually amended as the system takes the first two city codes from the Booking File.

CITY The city code where the original ticket was issued.

DATE The date the original ticket was issued, using DDMMMYY format.

IATA CODE The IATA number of the original issuing office.

7. Ensure that the INSERT key is switched off, and use the Tab key to move between fields. Enter the original form of payment.


Press ENTER at the end. The ticket will issue.

Note: Do not press ENTER until all required fields are completed.



When you retrieve the Booking File, you will see reference to two e-tickets:

Click on *TE002 to display the reissued ticket.



Example Number 2 - Additional Collection Exchange

If your passenger is upgrading to a higher fare, or an airline charges for changing a reservation, there will be an additional collection.

Refer to the following ticketed Booking File for travel from Manchester to Amsterdam in Y class.

The passenger wishes to upgrade to J class.

Take the following steps to reissue the ticket:

1. Amend the reservation and quote the new fare, and enter to store the fare in the booking.

Note that there is an additional fare of GBP 149.00 plus an additional tax amount of GBP 13.00 (YR).

Any taxes which have been paid when the original ticket was issue must be removed from the new fare quote.



2. Convert to a manual fare build.

Enter: *FB1


Enter: FBUTAX1/13.00GB+TAX2/+TTL/

FBUTTL/

3. File the new fare.

Enter: FBF

R.P+ER

The fare now shows the new fare of GBP 476.00 plus tax GBP 13.00GB.

This is the new fare detail ready for the exchange:

4. Issue the new ticket

Enter: TKP0749901891946




Note that the new fare and additional amount of tax to be paid are shown at the top of the screen.

Previously paid taxes are shown in the middle of the screen.

The system will automatically calculate the additional fare to be paid and the additional tax.

5. Specify the original form of payment NONREF and enter on the last cursor point after the IATA CODE.


You may specify a maximum of three payment types for the additional collection.

If the whole amount is to be paid using one form of payment tab to the first tab stop and enter the appropriate information, e.g. NONREF. Do not enter the amount, only the form of payment code and the Galileo system will assume that you are paying the full amount.

If the additional collection is to be paid using multiple forms of payment, the exact amount, preceded by the $ sign, must be given for each type of payment.

Refer to the following example, where GBP 50.00 is paid using CASH and GBP 112.00 CHECK.



6. Enter the form of payment for the additional collection.

7. Enter at the cursor and the ticket will issue automatically.

Note that the new e-ticket will show the exchange information at the base of the ticket:

Enter: *HTE


The additional collection of GBP149.00A and GBP 13.00 GB tax will appear in the TINS Report (HMPR). A indicates an additional collection.

Example screen display:



Voiding / Cancelling a Reissued ticket

It is possible to void/cancel a reissued ticket. This must be carried out on the same day that it was reissued.

Once voided it cannot be un-voided.

Not all carriers permit a reissued ticket to be voided. Refer to the Airline Functionality listing in ASK Travelport for more information.

Include the airline code. The check digit is optional.

Example entry: TRVE/0749901891947

Alternate Currency Reissues

When the additional collection is being made in a different currency to the original ticket, there is an extra step to take in the calculation. Make this calculation before creating the Exchange fill-in format.

Once the new fare has been calculated in the original currency, compare it to the original fare and calculate the additional collection amount (ADC).

Convert the ADC into the currency in which the customer will be paying.

You must ascertain the appropriate bank selling rate (BSR) between the two currencies in order to complete the Exchange fill-in format screen.

Refer to the following example:

A passenger booked a ticket in Spain for travel Barcelona – London – Barcelona. The ticket was issued in Euro.

When he is in London, the passenger changes his flight to travel back to Malaga instead of Barcelona.

Iberia has provided details of the recalculated (new) fare. Taxes apply, but they are the same as the original ticket and will be shown as 'paid' on the FIF exchange screen.

The new fare has been filed in the Booking File.

Original itinerary: New itinerary:

BCN – LON – BCN

Fare EUR 1102.00

BCN – LON – AGP

Fare EUR 1234.00



Take the following steps:

1. Calculate the additional collection. EUR 1234.00 (new fare) less EUR 1102.00 (old fare) = EUR 132.00

2. Convert EUR into GBP (unrounded): FZSEUR132.00GBP/U

Note: The end result is GBP 108.82

3. The FZS response shows the rate as in the original country, so ascertain the BSR from your country by entering: FZSGBPEUR


Note: You must round the BSR to 1.214 for acceptance on the exchange fill-in format screen.

The BSR of 1.214 has now been obtained and an additional collection amount of GBP 109.00 (rounded to the nearest GBP) is due.

You can now add these figures to the Exchange fill-in format screen.



Module 9 Review

Miguel Garcia has the following ticket which needs to be reissued to return to Malaga instead of Barcelona. The new reservation is in the Booking File, and a new fare has been filed, and the Booking File ended and re-retrieved.

1. What is the entry to display the Exchange Ticket fill-in format screen?

2. You must establish the additional collection needed in Euros and the conversion rate from EUR to GBP before commencing the exercise. The new fare is EUR 1500.00 and there are no new taxes. Make the relevant entries, and then write them down.

3. After you complete the screen and press ENTER, the *MR screen is displayed.

*MR TOTAL ADD COLLECT 90.00 GBP /F ……………………………………………………………………………………………………………………. /F ……………………………………………………………………………………………………………………. /F …………………………………………………………………………………………………………………….

The form of payment for the additional collection will be CASH. What entry will you make on this screen?

4. Finally, how will you complete the transaction?


Module 10: Automated Refunds

Automated Refunds enables you to process refunds for IATA documents electronically. These documents include system electronic tickets for both published fares, tour and net remit tickets.

A mandatory refund notice is printed in support of the transaction. Therefore it is necessary for the agency location to be equipped with either a Galileo itinerary or printability printer. If both printers are present, the default is to print the refund notice on the itinerary printer.

In situations when the printer is not linked, or has a status of 'DOWN', an error response will be generated and the transaction will not be processed.

Be sure to follow your local BSP guidelines on how the refund notice is to be forwarded to them.

Note: If your agency does not print itineraries but need to print refunds, set up a Pkey with a link and de-link itinerary printer entry. This enables you to quickly link and de-link each time you process a refund.

Module Objectives


Refund a totally unused system generated ticket.

View the TINS report for refunds.

Processing a Refund

HELP REFUND ASK ANSWER 502

You can process a refund for an unused or partially used ticket originally issued in your office within the last 32 ticketing days.

Note: Not all airlines support automated refunds. You must contact the airline directly.

Refer to the following example unused ticket that requires a full refund:



First establish that there are no cancellation or service fees to be charged.

To process the refund, you must create a refund notice in the system by making the entry:

TRNE1259901891921/02JAN14

Entry: Description:

TRNE Ticket RefuNd Electronic

1259901891921 Ticket number including airline code and check digit

/ Separator

02JAN14 Date of ticket issue.

Example screen response (Screen 1):

This is the first screen of the refund procedure. Note “Page 1 OF 4” in the top right of the screen. The fare and ticket information on this screen is captured from the electronic ticket details. You must complete all relevant fields before you press ENTER to move on.

CASH AMOUNT USED:

When ticket payment was made by cash or cheque, tab to this field to enter the total value used on the ticket, excluding taxes, i.e. the value of the journey actually travelled. If no sectors were flown, the value will be 0.00

CREDIT AMOUNT USED

When payment for the ticket was made by Credit Card, tab to this field to enter the total value used on the ticket, excluding taxes. If no sectors were flown, the value will be 0.00



CANCELLATION CHARGE:

When a cancellation charge is to be applied to the transaction, tab to this field to enter the appropriate amount. If no cancellation charges apply, leave blank.

UNUSED TAXES TO BE REFUNDED Y/N.

Enter Y if any or all taxes are to be refunded.

Press ENTER and the tax screen is displayed if required.

Refer to the following example tax screen. Any taxes to be refunded must be manually entered here.

Note: If there is a ZP tax to be refunded (US domestic journeys only), the tax must be entered using the tax boxes at the top and the 3-letter code of the airport for which it is charged must be entered in USD in the section starting BT.

Press the Enter key.

Example screen response (Screen 2):

The refund due, calculated from the previous screens, is shown at the bottom of the page.

PFC:

To be used when PFCs (Passenger Facility Charges) are to be refunded. When applicable enter the 3 letter PFC airport code and then tab to enter the appropriate USD amount such as 3, 4, 4.50, etc. If no PFC is to be refunded, leave blank.



REFUND AMOUNT:

The amount to be refunded to a credit card if one was used as the form of payment. If no amount is refundable to a credit card, leave blank.

COMM PERCENTAGE/AMOUNT ON CANCELLATION CHARGE:

When appropriate, enter either a commission percentage or the amount that is due to your agency from any cancellation charge. If no amount is due to your agency, leave blank.

Third Screen Used only when more than one credit card was used for payment. Usually you will enter “N” in this field.

Note: Many BSP authorities will only permit one credit card per passenger. Agents in those countries will only use the first Refund amount field, and never go to the third screen.

ENTER

Screen response:

A refund notice is printed simultaneously and confirms the refund reference number.

The status of the e-ticket will have changed to RFND

Refund a Ticket using a Linear Entry

ASK ANSWER 38009

You are able to refund a ticket using linear entries.



Re-printing the Refund Notice

ASK ANSWER 446

It may be necessary to re-print the refund notice out if the itinerary printer jammed, or the refund notice was lost.

To reprint the notice, enter: TSDR1259901891921/02JAN14

Points to note:

The refund notice can only be re-printed for refunds issued within the last seven days.

The expected response is REFUND NOTICE REPRINTED. If the notice was not printed within the seven day period, or the wrong date is specified the response will be TICKET REFUND NOTICE NOT FOUND.

Cancelling a Refund

ASK ANSWER 467

It is possible to cancel a refund with some carriers.

Check that the carrier accepts the cancel transaction. Refer to the ASK Travelport Ticketing Carrier Functionality Table in answer 8430.

The refund must be cancelled the same day. Include the airline code and check digit.

Make the following example entry to cancel a refund notice:

TRNC12599000482880

Viewing Refunded Tickets on the Payment Report (HMPR)

Make the following entry to view refunded tickets for your agency.

Enter: HMPR/ALL

Note: You must include /ALL in order to display refunded tickets.


HMPR Help Me Payment Report

/ Separator

ALL View ALL transactions including refunds




Note: The ticket number that has been refunded is displayed, with RFND underneath the FARE column.

If you only wish to view refunded tickets, use the following format: HMPR/REF/02JAN-02JAN

Note: The date must be specified twice.


Important note: System generated tickets can be refunded using the procedures detailed in this module provided that they feature on a previous TINS report. TINS records may be displayed for up to 32 historical working days, although the period of time may vary from country to country.

If the ticket was issued outside of this time restriction, you will get the error response: REFUND NOT PERMITTED – TICKET NUMBER NOT IN TINS.

Note: In this case, the passenger may apply to the airline for a refund.



Module 10 Review

Add this year’s date to entries where relevant.

1. Assume today’s date is 13 November. You issued an e-ticket, ticket number 055 765 876 1234 3 on 16 July. What is the entry to create a refund notice in the system for a full refund?

2. You process a full refund of all fares and taxes (no cancellation charge). When you press

ENTER at the end of PAGE 1 of the refund fill-in format, will you be taken to:

PAGE 2

Tax Screen

PFC Screen

3. What is the entry to display the TINS report for refunds only for 09 October?


Module 11: Itinerary Remarks

Itinerary Remarks enable you to add information to the itinerary. There are two different formats for Itinerary Remarks; those which you add manually, and Canned Remarks which are stored in the system.

Itineraries can be printed at the same time as a ticket using the TKP entry. Alternatively if you just wish to print an itinerary, use the entry TKPDID (assuming your workstation is linked to an itinerary printer).

Itinerary Remarks are used most frequently to add information that a passenger can see on a ViewTrip Itinerary at www.viewtrip.com

Module Objectives


Create manual Itinerary Remarks

Amend, re-associate and delete Itinerary Remarks

Add, delete and display Canned Remarks

Manually Added Remarks

HJELP REMARKS ASK ANSWER 2101

There are four categories of Manual Remarks. Unassociated Remarks relate to the whole itinerary.

Associated Remarks are specific to one or more segments. There are three types:

Associated Remarks

Check-In Remarks

Terminal Information Remarks



Unassociated Remarks

These are general remarks which will appear at the foot of the passenger itinerary. There is no restriction on the number of Unassociated Remarks which may be added to an itinerary, and each one may contain a maximum of 70 characters.

Refer to the following example Booking File:

Click on PNR on the menu, and select ‘Create/Edit Booking File Remarks’.


Select the ‘Unassociated’ tab.

Enter the required text in the Remarks text box and click on ‘Add’ and then ‘Save’.



Screen example:

Note: Add further remarks in the same way.

Associated Remarks

These are remarks which refer only to certain segments of a journey, and so are segment related. They will print on the itinerary below the relevant segment of the journey.

Select the ‘Associated’ tab:

Note that the itinerary segments are displayed.

Select the required segment, enter text in the ‘Remarks text’ box and click ‘Add’ and then ‘Save’.



Check in Remarks

These remarks may be used to add check in times to air segments.

Refer to the following example format to add a check-in time relating to a specific segment (2):

RI.S2/CI*75

Entry: Description:

RI Remark Itinerary entry code

. Separator

S2 Segment 2

/ Separator

CI*75 Check in time of 75 minutes (Minimum 30 and maximum 120 minutes)

Other example formats:

Entry: Description:

RI.S1/CI*120+RI.S3/CI*60 To add a different check-in time for segments 1 and 3

RI.CI*120 To add the same check-in time (120 minutes) for all segments



Terminal Information

These remarks may be used to add terminal information to the air segments.

Note: Many times, terminal information is automatically provided by the system.

Refer to the following example format to add departure terminal information for segment 1:

RI.S1/DT* TERMINAL 4

Entry: Description:

RI.S1 Remark Itinerary for segment 1

/ Separator

DT Departure Terminal

* Separator

TERMINAL 4 Free Text

Other example formats:

Entry: Description:

RI.S1/AT*BA TERMINAL To add arrival terminal information for segment 1

RI.S1/DT*TERMINAL 5/AT*BA TERMINAL

To add both departure and arrival terminal information for segment 1.

Note: Segment relation needs only be entered once if information if for the same segment number.



Displaying Itinerary Remarks

Refer to the following example Booking File:

Click the Quick Access button


The following manual formats are also available:

Entry: Description:

*RIU Display only Unassociated Remarks

*RIA Display only Associated Remarks

*RIC Display only check-in times and terminal information

Note: Confirmed seats, meals and special service requirements in the Booking File will automatically be added by the system to the itinerary when it is printed. You do not need to add Itinerary Remarks to the Booking File for these items.



Amending and Deleting Itinerary Remarks

If you wish to amend a remark, simply select the remark and amend the text in the ‘Remarks text’ box and click ‘Save’.

Screen example:

If you wish to delete a remark, select the remark and click ‘Remove’ and then ‘Save’.



Re-associating Itinerary Remarks

When a segment of the itinerary is cancelled, any associated remarks related to that segment will also be cancelled.

If cancelled associated remarks apply to the replacement segment, they can be re-associated.

Refer to the following example where segment 1 for 1 September has been cancelled.

Example system response:

The MAD-BKK flight has been rebooked for 2 September and is the ‘new’ segment 1.

Enter *XRI to display the cancelled Itinerary Remark.

To re-associate this remark to the new segment 1, enter: RIR.1S1

The system responds with an asterisk, and the remark is now associated to the new segment.



Canned Remarks

HELP RPFD ASK ANSWER 2125

A Canned Remark is an Itinerary Remark which is permanently stored in the system. A maximum of 12 Canned Remarks can be selected to use with each Booking File.

Canned Remarks (identified by numbers) can only be created and displayed by a second level authorized user, possibly your office manager or supervisor.

If they exist at your agency location, Canned Remark numbers will be advised to you so that these can be imported into a Booking File. Check with your manager or agency supervisor.

Note: The wording does not appear on the Booking File (just the number), so take care when selecting the numbers.

To display Canned Remarks created in your office (second level authorized user only), enter: RPFD/RMKS


Adding Canned Remarks into an Itinerary

The format to enter a Canned Remark varies dependent on whether your agency location uses Enhanced Itineraries or Galileo Itineraries.

Enhanced Itineraries

Remarks are added in the order requested, in a single entry.

Example entry: IMUCR1.23.2

Entry: Description:

IMU Itinerary Modifier Update function identifier

CR Canned Remarks

1.23.2 Remark numbers 1, 23 and 2 in that order



Amending Canned Remarks

To amend Canned Remarks to appear on the itinerary, the IMU entry must be changed to reflect the Canned Remarks that are now required.

Example entry: [email protected]

Note: This entry will change previously stored Canned Remarks to numbers 23 and 2.

Displaying Canned Remarks

To display the Canned Remarks numbers in a Booking File, enter: IMUD*


Galileo Itineraries

Remarks are added in the order requested, in a single entry.

Example entry: DI.CR1.23.2

Entry: Description:

DI. Document itinerary function identifier

CR Canned Remarks

- Separator

1.23.2 Remark numbers 1, 23 and 2 in that order

Amending Canned Remarks

To amend Canned Remarks to appear on the itinerary, the DI line must be changed to reflect the Canned Remarks that are now required.

Example entry: DI.2@CR–23.2

Note: This entry will change previously stored Canned Remarks to numbers 23 and 2.

Displaying Canned Remarks

To display the Canned Remarks numbers in a Booking File, enter: *DI



ViewTrip Itineraries

ViewTrip Itineraries can be accessed via the website www.viewtrip.com. The passenger must use their Galileo locator and their surname to retrieve the itinerary.

These details are also transmitted when you email an itinerary to a passenger from the Booking File.

Note: Unassociated remarks are visible at the bottom of the itinerary under the ‘Remarks’ heading.

Associated remarks can be viewed for each segment in the ‘Remarks’ area after clicking the ‘Flight Service Information’ under each segment.

http://www.viewtrip.com/



ViewTrip E-Ticket Receipts

Passengers can also access a copy of their e-ticket receipt from the ViewTrip website.



Fare Information

Normally the fare is visible on the e-ticket receipt. Not all agencies want the passenger to see the actual cost of the air fare, as it may have been sold as part of a package, or a service fee added.

It is possible to suppress certain parts of the fare information from the receipt by making a notepad entry in the Booking File.

Example formats:


NP.VIEWTRIPNET Suppresses Fare (IT is shown). Tax breakdown, Fare Basis, Baggage Allowance, Form of Payment and Endorsements are shown.

NP.VIEWTRIPITIN Suppresses Fare, Tax Breakdown, Form of Payment and Endorsements

NP.VIEWTRIPWARSAW Shows standard receipt with Warsaw Convention conditions of contract.



Module 11 Review

1. What is the entry to add a check in time of 90 minutes for segment 3?

2. What is the manual entry to add Unassociated Remark ‘HAVE A PLEASANT FLIGHT’?

3. What is the manual entry to display only Associated Itinerary Remarks?

4. A booking has been changed. Make the entry to re-associate remarks 1 and 2 to new segment 3.

5. Add some Associated and Unassociated Remarks to one of the bookings you have used during the course and then view it on the ViewTrip website.

.


Module 12: Linkage and Support Document Set Up

In order to issue documents using the Galileo system, your workstation must be linked to the relevant document printers. This module explains how to set up your workstation and link to the printers in your office.

Although an e-ticket is paperless, there may still be requirements to issue a receipt, or you may wish to provide your customer with an itinerary.

Also to complete an automated refund you must be linked to an Itinerary printer at the time.

Note: Theoretically sites do not need to be linked to a printer GTID to issue an e-ticket, but it depends on the ticket type field in your Agency Account Table.

Type 41 is e-ticket only and will not need a ticket printer GTID. Types 31 or 33 are ‘old’ ATB sites which still need to be linked to printer GTID in order to issue an e-ticket.

Module Objectives


Link your workstation to relevant document printers

De-link your workstation if required

Ensure that e-ticketing tables are set up correctly for your agency

Setting up Support Document Printing

ASK ANSWER 565

Although the concept of e-ticketing is paperless travel, there are still some requirements for documentation which will vary from country to country. For example, many BSPs require an audit coupon receipt with the Sales Report.

Also for many IATA BSP agreements, it is a requirement for agents equipped with itinerary printers to provide passengers travelling on an e-ticket with a supporting document called the Passenger Itinerary Receipt (PIR).

Your agency printers and workstations must be set up to enable you to print these documents.

The set-up procedure only needs to be performed once for each pseudo city code.

If your agency is equipped with an itinerary printer this should be assigned as the device which will print the Passenger Itinerary / Receipt.



To display the e-ticket Support Document print Table, enter: HMET


You will see a list of the possible support documents which are designated by your BSP as mandatory (Y) or optional (O).

Documents not required by your BSP will not be shown. These will vary from country to country. You may see AUDIT CPN; AGENCY CPN; PSGR RCPT; CHG FORM; EXCH AUTH and/or RFD AUTH.

The example above shows only the AGENT CPN and PSGR RCPT lines.

Note: If you do not wish to print support documents a GTID is still required, but you can set Agency and Print Now to NO.

Take the following steps to complete the table:

Complete the table as follows:

1. Ensure that the insert key is switched off.

2. Tab to the GTID field and type in the GTID of the itinerary printer on which you wish support documents to print.

3. Tab to the AGENCY field and type in Y

4. Tab to the PRINT NOW field and type in Y

Note: Ensure that the entire table is completed before pressing the Enter key.


Note: Once completed, all e-ticket support documentation will print on the designated printer.



Reprinting Support Documentation

ASK ANSWER 2800

It is possible to reprint support documentation at any time after the ticket has been issued on the condition that the ticket record is still available in the airline’s database

Refer to the following example to reprint support documentation for e-ticket 2179901891922.

Enter: TSD2179901891922


TSD Ticket Support Document

2179901891922 Ticket number including the airline code

Note: The Galileo system response will say: SUPPORTING DOCUMENTS ISSUED.

Printer Linkage

HELP HMLM

In addition to the air ticket, you may wish to use the Galileo system to issue additional documents such as an itinerary, or a MIR which sends data to a back office system.

If you attempt to issue a document without linkage to the document printers, the system response will be: INVALID: NO LINKAGE

Every workstation and printer device has its own unique Galileo Terminal IDentifier (GTID).

The GTIDs of all workstations and printers in your agency are recorded in your Agency Account Table (AAT). If any GTID is not recorded in the AAT then access to the Galileo system is denied.

Note: GTIDs are automatically added to the AAT before installation of Galileo in an agency. Each workstation and printer device is usually labelled with the GTID.

Alternatively, you may locate printer and MIR GTIDs by looking at the Galileo Print Manager software within your agency.

To establish the GTID of your workstation, enter: +J




Linking to an Itinerary Printer (DI)

ASK ANSWER 602

Linking to an itinerary printer and any accounting system is normally only required when:

Your agency is set up for document production or

There is an office re-organisation which requires your workstation to be linked to a different printer

To issue a refund notice, your workstation must be linked to the Itinerary printer.

To link your workstation to an itinerary printer, use the following example entry:

HMLMC5F062DI

Entry: Description:

HMLM Link Terminal (Help Me Link Machine)

C5F062 GTID of Ticket Printer

DI Demand Itinerary print

Screen response:

Screen explanation:

Entry: Description:

CRT GTID of workstation

ITN DEV GTID of Itinerary printer C5F062

D = issue on demand

ST Status

U = Up

D = Down

B = Busy

FM Stock or paper type. This designates the type of ‘paper in the printer.

I = Itinerary

B = Blank



Linking to a MIR Device (DI)

ASK ANSWER 603

The same logic applies when you link a MIR device to your workstation. However, the entry differs in that DA is used to Demand Accounts.

Example entry: HMLMC5F57DDA

Alternatively, you can link to more than one document printer at one time.

Refer to the following example entry to link to an Itinerary printer and accounting device:

HMLMC5F062DI/C5F57DDA


Printability

To link to a printability printer to print a screen shot, use the following example format:

HMLMC5D870DX

Displaying your Linkage

ASK ANSWER 599

Once links have been established between your workstation and relevant printers, you can display your linkage at any time.

Enter: HMLD




Bringing the Status Up

ASK ANSWER 600

The response above shows that the status of the itinerary printer is ‘Down’. This must be changed to ‘Up’ status to enable itinerary documents to be produced.

Enter: HMOMC5F062–U

Entry: Description:

HMOM Change Status (Help Me Operate Machine)

C5F062 GTID of Printer Device

–U Separator and UP status

The screen response is: DEVICE C5F062 IS NOW UP

Delinking

ASK ANSWER 606

Occasionally, you may need to delink printers from your workstation. You may need to do this if you linked to the itinerary printer just to issue an automated refund. You now wish to de-link as you do not want an itinerary to be produced each time you issue a ticket.

Make the following entry:

HMLM/DELINK Help Me Link Machine / De-link from all printers.

Screen response:

Alternatively, the following formats can be used to de-link your workstation from a particular printer type.

Entry: Description:

HMLINK/DELINK/I De-link from Itinerary printer only

HMLM/DELINK/A De-link from MIR device (accounting) only



Module 12 Review

1. What entry will link your workstation to an itinerary printer with the GTID, C8743A?

2. What entry will link your workstation to a MIR device with the GTID, C6G43A?

3. What is the entry to display the status of the link between your workstation and printers?

4. Here is the response to the last entry…

Your MIRs are not transmitting. What is the entry to change the status of the MIR printer to ‘UP’?


Module 13: Stock Control

When issuing e-tickets, ticket numbers are assigned automatically by the Galileo system, usually in batches of 250.

When all e-ticket numbers have been used, the Galileo system will automatically assign a new range of ticket numbers.

It is possible, however, for travel agents to create itinerary numbers. These are managed by your agency and not by Galileo.

Module Objectives


Display ticket numbers for usage in your agency

Assign itinerary numbers

Display the TINS report

Void tickets

Displaying E-Ticket Numbers

ASK ANSWER 577 HELP HMTN/D

These are often referred to as CGNs (Computer Generated Numbers). It is possible to view how many ticket numbers your agency currently has left.

Enter: HMTN/D


HMTN/D Help Me Ticket Numbers / Display



ALLOCATED TICKET… Header text

9901891923 The next ticket number that will be issued prefixed with the airlines 3 digit ticket code

9901891999 The last ticket number in the range

77 The number of e-ticket numbers remaining



Itinerary Stock Control

ASK ANSWER 3268 HELP HMIN/D

It is not mandatory for your agency to create an itinerary table within the system. In the absence of a table, the Galileo system assigns a default number to each itinerary as it is issued.

However, it may be preferable to pre-assign itinerary numbers, and these can be allocated from 1 to a maximum of 99999.

The entry to create an itinerary table is as follows:

HMINC5F062–10000/19999/*

Entry: Description:

HMIN Add Itinerary Numbers function identifier (Help Me Itinerary Numbers)

C5F062 Printer GTID

– Separator

10000/19999 First and last itinerary numbers to be used

/ Separator

* Restart at 10000 after 99999 has been reached

Alternatively, you can use any of the following options:

Entry: Description:

HMINC5F062-* Number itineraries automatically from 1 to 99999 and then restart at number 1.

HMINC5F062-14000/14999/1000 Number itineraries from 14000 to 14999.

HMINC5F062-14000/14999/* Number itineraries from 14000 to 14999 and then restart at 14000

If you need to check the itinerary table at any time, enter: HMIN/D


HMIN/D Help Me Itinerary Numbers/Display




TINS Report

HELP HMPR ASK ANSWER 578

The TINS report displays a list of transactions for today, and is updated automatically as each ticket is issued. This is more commonly referred to as the Payment Report or Daily Activity Report.

To display the Tins Report, enter: HMPR

Format: Explanation

HMPR Help Me Payment Report

The TINS report displays system generated ticket numbers. This includes any tickets that have been voided either by your agency or voided automatically during the ticketing process.

Example screen response

TINS records may be displayed for up to 32 historical working days, although the period of time may vary from country to country.

To access an historical TINS report (12 August), enter: HMPR/12AUG

Note: The 32 days are not necessarily consecutive. They may occur during the period of the last 90 days.

Enhanced TINS Report Commands

In addition to the basic TINS Report command, there are commands available which allow you to retrieve specific information from a TINS report.

Refer to Appendix A or H/HMPR



Ticket Voiding

ASK ANSWER 570 HELP VOID

The period in which you can make a ticket void differs from country to country. In the UK, it is only possible to void a ticket on the day of issue.

If you have issued an e-ticket and now want to void it (maybe you specified an incorrect form of payment), use the following example entry:

TRV/ 1259900505183

Entry: Description:

TRV Ticket Report Void function identifier

/ Separator

1259900…. Ticket number including the airline code

The system response is: TICKET NO.1259900505183 CHANGED TO VOID STATUS



Module 13 Review

Assume the GTID of your workstation is: C5H43A

1. What is the entry to check the number of e-ticket numbers available in your agency?

2. What is the entry to void ticket number 0019900505186?

3. What is the entry to view the TINS Report for 29 July?

4. The GTID of your itinerary printer is C5F062. What is the entry to number your itineraries from 1 to 99999 and then restart at 1 again?


Module14: Electronic Miscellaneous Document (EMD)

ASK ANSWER 38621 – What is an EMD? ASK ANSWER 38623 – How do I issue an EMD?

An Electronic Miscellaneous Document (EMD) is used as a fulfillment method for various accounting transactions, such as Airline Ancillary Services. EMD functionality allows payments to be processed more efficiently and cost effectively, and you are able to issue and track EMDs in your own system.

An increasing number of airlines offer Ancillary Services, which are sold in conjunction with their air transportation services. Ancillary Services include items such as excess baggage, seats, meals, travel insurance and lounge access.

Previously, if many of these services were required, they would have been booked directly with the airline.

However, it is now possible to book and pay for these services directly within the Galileo system. You are able to display the service catalogue available in Galileo and sell the required service.

Note: The types of Ancillary Services offered within the Galileo system are dependent on carrier participation and may vary in different countries. Refer to ASK Travelport to verify services offered by airlines.

Once the service has been confirmed and you have taken payment directly from the customer, you must issue an EMD to enable interline settlement between your agency and the airline.

This payment is then processed via BSP, in the same way as a flight ticket.

EMDs can also be issued in order to process payments for additional transactions such as airline reservation change fees and group deposits.

Note: You can also issue an EMD for products and services sold through Travelport Options Integrator. This is a software application which enables you to purchase seat products and services offered by carriers that participate in Travelport’s optional services program.

Airlines may require payment of these services with an EMD.

Agencies will be assigned an allocation of EMD numbers, and each subsequent allocation of EMD numbers will be automatically allocated when a new range is needed.

There are many answers in ASK Travelport, other than those listed above.

Search for category:

Issuing Tickets and Travel Documents>Ticketing>EMD.

Module 14: Electronic Miscellaneous Document (EMD)


To view the EMD numbers allocated to your agency, enter: EDOC


IATA 7777777 XXX

WORLD TRAVEL LONDON

TYPE ASSIGN DATE START NUMBER NEXT NUMBER END NUMBER EMD 04 MAR 8131011050 8131011077 8131011099

Note: You may view your allocation of EMD numbers back at your agency using the EDOC entry. However, this entry is not available for training pseudo city codes.

EMD is the electronic replacement for all standard traffic miscellaneous documents, including:

Miscellaneous Charge Orders (MCO) or virtual MCO (vMCO)

Special Service Tickets (SST)

Prepaid Tickets (PTA)

Multi-Purpose Documents (MPD)

Tour Orders

Excess baggage tickets

Module Objectives


Identify an Associated EMD and a Standalone EMD

Issue Associated and Standalone EMDs

View, Void and Refund EMDs

Display EMDs on the Payment Report (HMPR)

Decode EMD related error messages

Provide Support for EMDs and escalate an incident if required



Introduction

EMD data is included in the Galileo Ticket Invoice Numbering System (TINS Table).

An EMD can only be issued from a Booking File, which contains at least one itinerary segment and the Booking must be ended and retrieved before an EMD Issue entry is used.

The format identifier to issue any EMD is: EMDI

Example formats:

Entry: Description:

EMDI EMD Issue

EMDV EMD Void

EMDD EMD Summary Display (data from the carriers electronic database)

EMDD Refund an EMD from the EMD Summary Display, by selecting the EMD REFUND, using the tab function

EMDL EMD List

EMDH EMD History

EDOC View the allocation of EMD numbers for your agency

There is no limit to the number of EMDs which may be issued within a single Booking File.

The EMDI entry issues EMDs without printing any support documents. In order to print support documents, you must include an appropriate modifier in the EMDI entry.

Depending on which support documents are required, you must specify the printer type and document type code.



Printing and Document Modifiers

The print type options are:

PP- to print to a plain paper printer

PI- to print to an itinerary/invoice printer

The document type modifiers are:

C to print the credit card charge form

R to print the EMD customer receipt.

You may include multiple issue modifiers in the EMDI entry by using the separator (/).

The table below lists all of the issue modifier options:

The

AAsAs When printing The

You can also email the EMD customer receipt to an e-mail address stored within the Booking File. The e-mail version of the EMD customer receipt support document is known as the ‘Additional Services/Fees

Modify/Option: Code: Example:

Commission Z Z9 (9% Commission)

Form Of Payment F FCK or FS

Endorsement ER ERNON-REFUNDABLE

Related Ticket Number IC IC0748899029453 (Issue In Connection with, the 13 digit ticket number)

Document Type C – credit card charge form (or)

R – EMD customer receipt

Printer Type PP –

PI –

PEnn –

(nn = email number within the MT field of the Booking File)

PP – C (Print to plain paper printer - the credit card charge form)

PI – R (Print to itinerary/invoice printer – EMD customer receipt)

PE4-R (select email address number 4)

EMD Even Exchange EXE EXE074489902141



Receipt’.



A separate email version of the Additional Services/Fees Receipt will be sent for each passenger name in the Booking File or that is selected.

Note: Even if all the Additional Services/Fees Receipts are being sent to the same email address, a separate email will be sent for each passenger name.

For more information on printing and emailing support documents refer to Ask Travelport answer 39088.

Selection Criteria Modifiers

The following Selection Criteria Modifiers can be included with the EMDI entry, in order to make the entry more specific. You can issue an EMD for ‘Additional Services’ using an itinerary segment, carrier or passenger name field.

Multiple Selection Criteria modifiers may be used in an entry.

The table below lists some format examples.

T

Services Reason

Selection Criteria Modifier:

Code: Example:

Vendor Select V VAZ (Carrier two letter code)

Segment Select S S1-3 (segments 1 through to 3)

Name Select P P1 or P2 etc.

RFIC Select R RG

SVC Manual Select SM SM2 (manual SVC sector 2)

SVC Automated Select S S3

SSRASVC Number Select G G12



Reason for Issuance Codes (RFIC) and Sub-codes (RFISC)

When you request an Ancillary Service from the Ancillary Service Catalogue an RFIC and RFISC will be added automatically.

When you add a manual SVC segment you must manually input the RFIC as advised by the airline.

Note: Separate EMDs must be issued for each RFIC.

The following RFICs may apply:

A Air Transportation

B Surface Transportation/Non-air Services

C Baggage

D Financial Impact

E Airport Services

F Merchandise

G In-flight Services

‘Reason for Issuance Codes’ are defined by IATA resolution, and Reason for Issuance Sub-codes are maintained by ATPCo.



Types of Electronic Miscellaneous Documents

There are two types of EMD - a Standalone EMD and an Associated EMD.

Standalone EMD (EMD-S)

A Standalone EMD (EMD-S) can be used for any service or fee such as a change fee or group deposit, or any item that is not directly related to a specific flight segment.

EMD-S can be issued for non-flight related services; however some airlines may initially opt to fulfill flight related services on an EMD-S.

In order to issue an EMD-S, a SVC segment must exist within the Booking File, except when an airline requests an EMD-S for fulfillment for flight related services.

If an EMD is required for the fulfillment of a service or transaction fee which is not filed by ATPCO, then you must enter the SVC segment manually.

Travelport have introduced a new SVC segment type, which you can add manually to a Booking File, in order to communicate these service requests.

Refer to the following guidelines:

Before you can issue a Standalone EMD, you must first have a completed Booking File.

An e-ticket must have been issued, unless the booking is for a group deposit.

You must also add a request for the additional service via a manual SVC segment within the itinerary.

When adding a manual SVC segment, a Reason for Issuance Code (RFIC) and a Reason for Issuance Sub Code (RFISC) are required. Each airline can choose which code to use and each airline may have different requirements. Refer to Ask Travelport answer 43782 for details for each airline.

An EMD-S can only be issued for one passenger name at a time. Where an EMD-S is required for more than one passenger, a separate EMD issue entry must be made for each passenger.

The EMD issue entry automatically picks up the original Form of Payment within the Booking File. However you can override it using an issue entry modifier.



Associated EMD (EMD-A)

An Associated EMD (EMD-A) must be issued for all ‘flight-related’ services, such as excess baggage, lounge access, seat assignments, meals, etc.

Refer to the following guidelines:

Before you can issue an EMD-A, you must have a Booking File containing at least one confirmed flight segment. An e-ticket must have been issued and the flight coupons must be Open status (OPEN) or Airport Control (ARPT).

A flight-related service must be sold from the ‘Services Catalogue’. The service will then appear in the Booking File under the Special Service Request code, ASVC. The ASVC SSR communicates flight-related services to the relevant airline.

When flight associated services are booked, the information will appear in the Booking File within the *DAS item.

You can only issue an EMD when the SSR ASVC status code is KD or HD.

When an EMD-A is issued, it must be linked to the flight coupon of an e-ticket, so that the Additional Service is associated to the correct flight.

An EMD-A can only be issued for one passenger name at a time. Where an EMD-S is required for more than one passenger, a separate EMD issue entry must be made for each passenger.

If a passenger requires the same service (SSR ASVC) on multiple flights, such as a meal on both the outbound and return flight, you can issue a single EMD-A. You only need to make one EMDI entry.

If a passenger requires multiple services (SSR ASVC) for a single flight segment, such as checked baggage, internet access and a meal, you must issue a separate EMD-A number for each Additional Service. However, you only need to make one EMDI entry.

The EMD issue entry automatically picks up the original Form of Payment within the Booking File. However you can override it using an issue entry modifier.

Note: For information on displaying and selling flight-related services (Ancillary Services) refer to Ask Travelport answer 42943.



EMD Example 1: Issuing an EMD for a Reservation Change Fee

This example demonstrates how to issue a Standalone EMD (EMD-S) in order to process payment via BSP, for a reservation change fee. The airline may charge for a reservation date change or a name change.

Refer to the following completed Booking File for two passengers. A filed fare exists and e-tickets have already been issued.

The original departure date from London to Sydney was 17 February. However the passengers requested a date change, they now wish to depart on 24 February.

In this example the e-tickets may be changed and there is no fare increase. However, there is a change fee of GBP 150.00 for each ticket.

Although the itinerary has been amended, the original e-ticket records must be updated. This is done using the Exchange or Revalidation process, depending on the requirements of the relevant airline.

Once the Exchange/Revalidation is completed, you must issue the EMD.

Assume the e-tickets in this example have been revalidated for the new dates.

Take the following steps to issue an EMD for the BA reservation change fee.

1. Add a manual SVC segment, for a change fee.

Enter: 0SVCBAEK1LHR24NOV-N1/D/992/CHANGE FEE/150.00

Note: When an EMD is required for a change fee, the date that must be added to the SVC segment is the new travel date, not the original date.



Entry description:

Input: Description:

0SVC Indicator to insert SVC segment into the Booking File

BA Airline two letter code

EK1 Status code and number of items required for EMD

LHR Three letter departure airport code

24NOV New travel date

N1 Passenger name field

D Reason for issue code (D = financial impact)

992 Reason for issue sub code (992 = change fee)

Note: The code 992 is the RFISC for a reservation change fee. However, not all airlines choose to use 992. Refer to answer 43782 in ASK Travelport.

CHANGE FEE Description of EMD item, i.e. change fee

150.00 Fee amount (system defaults to local currency, defined by your agency location.

One EMD-S is required for each applicable change fee. As both passengers have changed their date of travel, one EMD-S is required for each passenger.

2. Enter a second manual SVC segment related to passenger 2 (N2).

Enter: 0SVCBAEK1LHR24NOV-N2/D/992/CHANGE FEE/150.00

The system response confirms that the SVC segment has been created. When you re-display the Booking File, it shows new SVC segments along with the itinerary segments.

3. Add a received from field, then End and Retrieve the Booking File.




Note that segments 1 and 2 are the SVC segments and the flights now appear as segments 3 and 4.

The next stage is to issue the EMDs. Two separate EMDs are required, and they must be issued individually.

You must use the standard EMD Issue entry (EMDI) twice, each time using a modifier to specify the Manual SVC sector for which the EMD is issued.

You must also include the e-ticket number in the entry.

Click on the Quick Access button in the PNR Viewer window.


The response displays the ticket numbers issued for each passenger.

Note: If tickets had been exchanged, then two ticket numbers would show for each passenger – the original number and the reissue ticket number. You must specify the reissued ticket number in your EMD entry.



4. Issue the EMD for SVC segment 1, for passenger RIGBY/PETERMR

Enter: EMDI/SM1/IC1259901891951

Entry description:

Input: Description:

EMDI/ EMD Issue entry

SM1/ Sector Manual 1 (Manual SVC segment number 1)

IC1259901891951 Issued in connection with the 13 digit e-ticket number which was issued.

Note: If a ticket was issued in exchange, enter the reissued ticket number.


Note: No support documents will print unless the relevant print modifiers are used with the EMDI entry.

5. Issue the EMD for SVC segment 2, for passenger WILCOX/KERRYMS

Enter: EMDI/SM2/IC1259901891952

Re-retrieve the Booking File:

Note: The status of each Manual SVC segment has changed from EK1 to HI1, and the EMD number is added to each segment. Also a new EDML field has been created to store the EMD numbers issued in the Booking File.



Displaying EMD Information in a Booking File

The EMDL field lists all EMD numbers which have been issued within a Booking File.

This field is automatically added to a Booking File when the first EMD is issued. All subsequent EMDs will be stored within the EMDL.

If an EMD is voided or refunded, the EMDL information is automatically updated.

To display the EMDL field, click the Quick Access button in the Booking File.

Alternatively, enter: EMDL


In this example, two EMDs have been issued. These appear on numbered lines 1 and 2.

The Electronic Miscellaneous Documents List (EMDL) can store a maximum of 999 numbered line items.

However, only a maximum of 100 items is displayed initially. If a Booking File contains an EMDL with more than 100 items, line numbers 1-99 will display automatically and a tab option will appear after line 99. Use this tab function if you wish to display line items 100 onwards.

Under each EMD number, the status code ‘I’ (original issue) is displayed, together with the date and time stamp for that transaction.

If an EMD has been voided, the status code is ‘V’.

If an EMD has been fully refunded, the status code is ‘RF’.

You can view a Summary screen (EMDD).

Click on the appropriate line number in the EMDL display:

Alternatively, enter: EMDD1 (LINE 1)




Points to note:

The RFISC (992) is displayed

The status shows USED. This is normal when an EMD is issued for a change fee.

The EMD Summary Display retrieves information which is held in the airline’s database. You can view that information in the same way as you do an e-ticket.

The EMD Summary holds details such as the EMD number, passenger name, and type of service purchased and the status of each EMD coupon.

It also enables you to select other processes by tabbing and entering additional information and pressing enter.

For example, at the bottom of the Summary screen, there is an option to void the EMD.

You can also opt to view a Detail Display, which provides a breakdown of the EMD information.

To view the Detailed Display, simply click on EMD DETAIL DISPLAY or alternatively, tab to ‘EMD DETAIL DISPLAY’ and press enter.

Note: The details for the EMD transaction are usually displayed over 2-3 screens. Move down (MD) to view more EMD document details.




Note: At the bottom of the display, you have the option to void the EMD. Also depending on the airline and service, there may be an option to refund the EMD.

Click on EMD REDISPLAY SUMMARY if you wish to redisplay the Summary Display.




EMD Example 2: Issuing an EMD for a Group Deposit

This example demonstrates how to issue a Standalone EMD in order to process payment for a group deposit booking, via BSP.

Refer to the following Booking File.

An EMD cannot be issued against a group name, so you must create a separate Booking File in order to issue an EMD for a group deposit.

You must add a Manual SVC segment containing details of the group deposit.

Take the following steps to issue an EMD for a group deposit for a group reservation.

1. Create a basic Booking File with a Form of Payment and add a manual SVC segment, containing the relevant group deposit information.

Enter: 0SVCAYEK1LHR15NOV-N1/D/997/GROUP DEPOSIT/2500.00



Entry description:

Input: Description:

0SVC Indicator to insert SVC segment into the Booking File

AY Airline two letter code

EK1 Status and number of items code required for EMD

LHR Three letter departure airport code

15NOV Travel date

N1 Passenger name field

D Reason for issue code (D = financial impact)

997 Reason for issue sub code (997 = group deposit)

GROUP DEPOSIT

Description of EMD item, e.g. group deposit

2500.00 Deposit amount (system defaults to your local currency).

Note: No currency code is required, just the deposit amount.

2. End and retrieve the Booking File.


Note: The Manual SVC sector appears as segment number 1.



3. Issue the EMD for manual SVC segment 1

Enter: EMDI/SM1

Entry description:

Input: Description:

EMDI Electronic Miscellaneous Document Issue

/SM1 Sector Manual 1 (refers to the segment number of the manual SVC segment)

Note: IC ticket number is not required when issuing EMDs for group deposit.

Once the EMD has issued, the Booking File will automatically end transact.


Click on the Record Locator to display the Booking File to view the changes.


Note that the manual SVC segment now contains the EMD number and the status has changed from EK1 to HI1. EMDL data also now exists.

Click on the Quick Access button to view EMDL information.

Example scree response:



4. Retrieve the original group booking and add an OSI item to advise the carrier that the deposit has been paid and that fulfilment is via EMD.

Note: The addition of an OSI is a requirement of AY. When you issue an EMD for other airlines, check for any specific requirements in Ask Travelport answer 43782.

Enter: SI.AY*EMD PAID 31JAN 20 PSGRS

In addition enter the number of the EMD.

Enter: SI.AY*EMD 1059992055101

Note: The date specified in the OSI entry is the date that the deposit is paid and the EMD issued.

Click on the Quick Access button to display the detail of the Booking File.


Points to Note:

You can add a Notepad item to each Booking File in order to cross refer them if required.

When the original group booking is ticketed, each ticket must be issued for the full fare amount including taxes. You can then refund the EMD that was issued for the deposit amount.



EMD Example 3: Issuing an EMD for a Service Booked for all Passengers on all Flight Segments

This example shows you how to issue an Associated EMD in order to process payment via BSP for ‘flight related’ Additional Services. Two passengers require the same services for the same flight segments.

Refer to the following completed Booking File for two passengers. E-tickets have been issued. Both passengers have requested extra baggage for the outbound flight on segment 1.

Take the following steps to book extra baggage as an Additional Service and to issue an Associated EMD.

1. Display a list of all available services for the relevant itinerary.

Enter: DAS*


Note: The Service Catalogue displays a list of possible service options. The exact number of services displayed, is dependant of both carrier participation and the booked itinerary segments.

Information displayed in the Service Catalogue is loaded by ATPCO.



Service Catalogue

The services are offered in order of flight segment. For example, the services on lines 1-9 all relate to segment 1 and this is indicated by 01 at the end of the corresponding line number.

Move down (MD) to check if there are more services available for segment 1 or if there are any for segment 2.

Service content may include:

(T) Ticket-related: products or services associated to a passenger’s ticket

(F) Flight-related: products or services associated to specific flights on a passenger’s ticket

(R) Fare-related (Rule Buster Service): associated to a specific fare component on a passenger’s ticket and overrides reissue and/or refund conditions for that fare

(M) Merchandise: products or services unrelated to specific ticket or itinerary

Note: The maximum number of services which can be displayed for each segment is 17. If more than 17 services exist, you may use search parameters to make your search more specific. For example you can search for baggage related services only.

In this example, both passengers are entitled to one checked bag, free of charge. However each passenger needs a Second Checked Bag for the outbound flight.

2. Select a Second Checked Bag from line 1, for each of the passengers

Enter: DAS01L1P1

Enter: DAS01L1P2

Input: Description:

DAS0 Sell

1L1 Quantity (1) of service from line 1

P1 or P2 Passenger relate to passenger 1 or passenger 2

The response to each entry is:

Note: If you are selling the same service for both passengers on all segments, there is no need to passenger relate the DAS0 entry. Simply specify how many of the services are required for each passenger and the service line number, e.g. DAS01L1



3. Add a Received Field and end the Booking File to save the data.


Click on the Quick Access button to display the ASVC information.


Note: The status of each item shows confirmed (KD).

Click on the Quick Access button to display the Additional Service Data.


Note: The display shows the confirmed status (CD) of each DAS item, the currency code, and details of the flight for which the service is applicable.



4. Once the requested service is confirmed, i.e. the *DAS status is CD and *SI status is KD, you can issue the EMD-A.

You must issue an EMD for each passenger individually. The EMDI entry must be passenger related.

Enter: EMDI/IC0559901891955/P1

Input: Description:

EMDI/ EMD Issue Entry

IC0559901891955/ Issued In Connection with the 13 digit E-Ticket number.

P1 Passenger 1


5. Redisplay the Booking file and repeat the EMDI entry for passenger 2.

Enter: EMDI/IC0559901891956/P2


Note: EMDL data now exists in the Booking File. Click on the Quick Access button.




Note that the EMD status in the DAS item has now changed from CD to FD meaning fulfilled.


Note also that the Additional Service SSR ASVC has been updated with the applicable issued EMD number and the status code of the SSR ASVC has changed from KD to HI.



EMD Example 4: Issuing an EMD for Multiple Services Booked, for only one Passenger

This example demonstrates how to issue an Associated EMD for ‘flight related’ Additional Services, where only one out of two passengers requires services for all flight segments.

Refer to the following completed Booking File for two passengers. E-Tickets have already been issued. Passenger two has requested extra baggage for both the outbound and return flights.

Take the following steps to issue an EMD.

1. Display a list of Services from the Service Catalogue.

Enter: DAS*G-BG

Input: Description:

DAS* Display Additional Services

G- Search by group code

BG Baggage Group Code Identifier


The passenger is already entitled to one free checked bag, so the



options are given to select a second or third checked bag as an Additional Service.

The services offered on lines one and two relate to flight segment 1 only and the services on lines three and four apply to segment two.

2. Sell one extra checked bag for segment one and two, for passenger two only.

Enter: DAS01L1P2*1L3P2

Input: Description:

DAS0 Sell

1L1P2 1 service from line 1, for passenger 2 only

*1L3P2 And sell 1 service from line 3, for passenger 2 only


3. Enter a Received from field and end and retrieve the Booking File.


Note: SI and DAS data now appear in the booking.

Click on the Quick Access button.


Note: The second checked bag has been requested for both segments, for passenger 2 HILL/NATASHAMRS only.

Click on the Quick Access button.




4. When the status of the SSR items has changed to confirmed (KD), and the DAS status is confirmed (CD), you can issue the EMD for passenger 2, and print support documents if required.

Enter: EMDI/IC0869901891958/P2/PI-R

Input: Description:

EMDI/ EMD Issue Entry

IC0869901891958/ Issued In Connection with the 13 digit E-Ticket number.

P2/ Passenger 2

PI- Print to Itinerary/Invoice printer

R Customer Receipt




Voiding an EMD

Both Standalone and Associated EMDs can be voided on the day of issue. The EMD number can be voided from the EMD Summary Display and EMD Detail Display.

Take the following steps to void an EMD from the Summary Display.

1. Retrieve the relevant Booking File and click on the Quick Access button to display EMD list.

2. Click on the line number 1 to display the detailed display.


3. Click on the interactive text EMD VOID


The EMD now has a status of V for void within the EMD Summary Display (EMDD), EMD Detail Display (EMDD1) and in EMD list (EDML). The Settlement Authorization Code (SAC number) appears.



Voiding an EMD using a Manual Entry

You can also void an EMD using a manual entry. Refer to the following example format.

Enter: EMDV123456789101112

Input: Description:

EMDV EMD Void

123456789101112 EMD number (13 digits)

Note: There is no entry to un-void an EMD, so be sure to enter the correct number.



Refunding an EMD

Both Standalone and Associated EMDs can be refunded, provided that the relevant carrier supports the refund process.

The refund process is similar to the void process. The EMD number can be refunded from the EMD Summary Display and EMD Detail Display.

For carriers supporting refunds, an EMD REFUND tab prompt will display on the EMD Summary Display and Detailed Display. However this does not necessarily mean that the EMD can be refunded.

You will receive an error response ‘EMD CANNOT BE REFUNDED’ if you attempt to refund a non-refundable service.

An airline who does not support EMD refunds may agree to make an exception if perhaps a flight is cancelled for operational reasons. The airline must process the refund.

Note: It is only possible to issue a full EMD refund and no partial refunds are allowed. All ‘open’ coupons of the EMD number will be refunded.

Take the following steps to refund an EMD.

1. Retrieve the relevant Booking File and click on the Quick Access

button to display the EMD List.




2. Click on the line number to display the EMD Detail Summary.


3. Click on the interactive ‘EMD REFUND’ to refund the EMD.

You may or may not receive a Settlement Authorization Code (SAC).


The EMDL item has now been updated to show the status of RF for refunded.



Viewing EMD History

You can view EMD history after you have displayed the EMD List screen. Information is retrieved from the EMD database. It provides a chronological view of the actions taken on an EMD number, such as issuance, void, and refund.

The EMD History display may be displayed using the EMD HISTORY DISPLAY tab option line from the EMD Summary Display and/or from the EMD Detailed Display.

Take the following steps to display EMD History.

1. Retrieve the relevant Booking File and display EMD List.




2. Display the history for EMD item 1.

Enter: EMDH1


Note: Depending on the length of the history, you may need to move down (MD) to view all of the information.

The History gives details about the type of EMD that has been issued, the transactions made, the commission amount, the associated ticket number, and details which support documents have been printed or emailed.

At the bottom of the History is the option to ‘REQUEST SUPPORT DOCUMENTS’. Click on this interactive prompt to print support documents if required.

You can also display EMD history outside of a Booking File, by specifying the EMD number.

Example entry: EMDH0869992055190

Input Description:

Input: Description:

EMDH EMD History

0869992055190 EMD number (13 digits)



EMD Information on the TINS Report

Any EMD numbers which are issued will appear on the payment report, with the identifier of ‘D’ in-between the 3 digit airline code and the EMD number.

The payment report will show which passenger name for whom the EMD was issued and the amount.

Take the following step to display EMD data on a TINS report/HMPR.

Enter: HMPR


If an EMD has been voided, it will appear as VOID on the HMPR.



Module 15: E-Ticketing Troubleshooting

It is important to note that all airlines have different procedures and requirements when it comes to working with electronic documents. This module looks at some of the more frequently occurring scenarios regarding e-ticket issue.

Module Objectives


Work with commonly occuring e-ticket issues

Identify sources of reference to resolve some of these issues

Common E-Ticket Problem Scenarios

The most commonly reported scenarios are:

Unable to issue a ticket

Unable to display an e-ticket record

Unable to revalidate or exchange an e-ticket

Unable to send automatic TKNE e-ticket numbers to the airline

Unable to issue a Ticket

ASK ANSWER 397

Airlines have their own restrictions in all areas of e-ticket issuance, and it may be that the airline does not allow the functionality that the passenger requires.

Refer to ASK Travelport answer 397: What do I check if I am unable to issue an e-ticket?

Multiple passenger or coupon restrictions

Some airlines restrict the number of passengers in a Booking File for whom an e-ticket can be issued with a single ticketing command (TKP).

Attempt to issue documents for each passenger using a separate ticketing command, e.g. TKP1P1.

https://travelport-english.custhelp.com/app/answers/detail/a_id/397

https://travelport-english.custhelp.com/app/answers/detail/a_id/397



FOID requirements

Although not required by the majority of airlines now, some airlines still require a FOID (Form of Identification) in a Booking File

Check with the airline to establish which FOIDs are acceptable.

Refer to H/FOID for the correct formats to add a FOID into a Galileo system Booking File

If two FOIDS are entered, they may conflict. Remove one from the Booking File, such as mileage membership number.

Check that the Form of Payment in the Booking File is acceptable to the carrier.

Individual carrier functionality can be checked by looking at the spreadsheet in ASK Travelport, answer number 8430:


Unable to Display an E-Ticket Record

When you display an e-ticket record, the data that you are presented with is in fact held in the airlines e-ticket server. This information is retained by each airline for a differing length of time. The industry minimum standards are:

7 days from the last date of intended travel for a wholly used e-ticket record (ETR)

13 months from the first coupon travel date for a partially used ETR

13 months from the date of issue for a wholly used ETR

Note: Some airlines may not permit e-ticket display at all.

Check the carrier functionality spreadsheet in Ask Travelport answer 8430 for the airlines accepted display formats.


Unable to Revalidate or Exchange an E-Ticket

If the airline does not permit an e-ticket to be revalidated, you must amend the Booking File and then exchange the original e-ticket with no additional collection. Alternatively some airlines will revalidate the e-ticket in their system if requested.

Some carriers will only allow you to exchange an e-ticket once. If you need to exchange an e-ticket a second time and the airline do not permit the second exchange of the document through the Galileo system, you must contact the carrier who will process this on your behalf.



Refer to the following FAQs:

FAQs - Unable to Revalidate an E-Ticket

Check: Explanation and Possible Resolution:

What do you do if you are unable to revalidate an e-ticket?

Check the functionality listing. If the airline does not allow revalidation, you must exchange the ticket for a new one, with no additional collection.

Alternatively request the airline to perform the revalidation.

Can you revalidate an e-ticket when the status is CKIN?

CKIN status indicates that flight departure is within 24 hours, and the airline is anticipating that the passenger will be checking in.

You must request the airline to perform the revalidation.

Note: Refer to the exception for BA in Module 8.

How do you revalidate an e-ticket in a divided Booking File if the e-ticket record is not present?

Retrieve the ETR into the divided Booking File. Enter: TE/125960000078.

Revalidate the ticket in the usual way.

Note: Other entries are available to retrieve an ETR. Refer to help pages: H/*TE

What do you do if the itinerary is part travelled and there is no live sector remaining on the original plating carrier?

The airline must revalidate the e-ticket record.

The passenger has changed their flight reservations and will now depart from LHR instead of LGW. Can the ticket be revalidated?

No. The ticket must be re-issued.

How do you revalidate an e-ticket if there is no longer a live Booking File?

Create a new Booking File, and retrieve the ETR into the Booking File with the entry: TE/125960000078.

Revalidate the ticket in the usual way.

Can you revalidate multiple segments with one entry?

No. Each segment and coupon must be revalidated separately.



Unable to Void an E-Ticket

Usually it is only possible to void an e-ticket if the status code of the ticket is OPEN. However, some airlines will allow you to void if the status is APRT. If not, contact the airline and ask them to change the status back to OPEN.

Unable to Send Automatic TKNE E-Ticket Numbers to the Airline

This functionality is set up at the request of the airline.

Many airlines do not require it as they hold the ETR in their own system and have details of the ticket number.

If in doubt, check with the airline.


Module 16: Fallback and Recovery for Itinerary and MIR

The previous module covered some of the errors you may receive when you attempt to issue an e-ticket.

The fallback and recovery procedures detailed in this module are to assist with the production of itineraries and/or MIRs.

This module contains general information on the transmission flow of a document and then continues with step-by-step procedures to resolve different scenarios.

Important note: Print Manager must be up and running to enable itineraries to print, and to transmit a MIR to the back office system.

Module Objectives


Track the flow of a document through the Galileo Central Processor

Work with the Pending and Printer Buffers

Tracking the Flow of a Document

To issue an itinerary or transmit a MIR, make the TKP input.

When you enter TKP, an image of the document travels from your workstation to the Galileo Central Processor in Atlanta. It is then passed on to your agency printer where the document is printed.



Transmission Flow of a Document

Each time an itinerary is issued it goes through an internal process in Denver on its way to the printer.

GALILEO CENTRAL PROCESSOR

Demand Demand Pending Sent Buffer Buffer

Sequence Number Assigned

Agency Printer Terminal Buffer

Agency

Printer

Demand Pending Buffer

A document image enters the Demand Pending buffer in Atlanta and if the printer status is down the image is held in the pending buffer until the status is brought back up.

Demand Sent Buffer

If there are no problems, the image moves to the Demand Sent buffer. A number is assigned to the image as it leaves the Pending buffer and moves to the Sent buffer:

Printer Buffer

From the sent buffer, the image is handed off to the printer buffer, which is a separate communications network located between the Central Processor and the printer.

As long as there are no printer problems, the image passes on to your agency printer where the document is printed.



Fallback and Recovery Procedures

ASK ANSWER 566 ASK ANSWER 45437

Fallback and recovery procedures are required when:

An image is stuck in the pending buffer

An image is stuck in the printer buffer

Displaying Demand Pending and Sent Buffer Image Counts

HELP HQC

You can display the count for the demand pending and sent buffers at any time.

Enter: HQC



ITN-ITIN The number of images in the pending and sent buffers, and the sequence number of the next document to be issued.

ACC-MIR The number of images in the pending and sent buffers, and the sequence number of the next document to be issued.

A count in the Pending buffer indicates that images are stuck and cannot progress to the sent buffer for because the printer status is ‘Down’.

The count in the sent buffer builds up during the day as itineraries and MIRs are issued, and indicates the number of documents.

It is reset to zero at 0400 UTC each day; however the images remain in the buffer for approximately 24 hours and can be displayed throughout this period if required.



Displaying Images in the Pending Buffer

If an image is stuck in the Pending buffer, it may be displayed.

Note: Only one image exists for each Booking File, regardless of the number of passengers it contains.

Entry: Explanation:

HQB/ITN/DP To view itinerary images in the Demand Pending buffer

HQB/ACC/DP To view MIR images in the Demand Pending buffer

Scrolling through the Demand Pending Buffer

Use the following entries to scroll through the Demand Pending buffer to display other images.

Entry: Explanation:

HQB/MD Move down to display the next image in the buffer

HQB/MD3 Move down three images

HQB/MU Move up to display the previous image in the buffer

HQB/MU2 Move up two images

Deleting an Image from the Demand Pending Buffer

If the image is no longer required, it may be deleted.

You must first display the image using the above entries.

To delete the image, enter: HQM/DELETE

Bringing the Printer Status Up

Make the following entry to change the status of the Itinerary/MIR printer (C5F062) to UP.

Enter: HMOMC5F062–U



Working with the Printer Buffer

If there is a problem with the itinerary printer, a document image may be stuck in the printer buffer.

Printer Buffer Image Count

ASK ANSWER 590

Only one image at a time should be held in the printer buffer, therefore the count will be either 1 or 0.

To count images in the itinerary printer buffer (C5F062), enter HQCC5F062


Note: The number refers to the number of Booking Files, not the number of passengers or documents.

Displaying the Printer Buffer Image

ASK ANSWER 591

You can display an image in the Printer buffer and delete it if it is no longer required. Alternatively, the printer may be quick started to drive the image to the itinerary printer.

To display an image in the Printer buffer (C5F062), enter: HQDC5F062




Deleting an Image from the Printer Buffer

ASK ANSWER 592

To delete the image from printer buffer (C5F062), enter: HQXC5F062

The system response is ALL OK

Quick Starting the Printer

You may quick start the printer (C5F062) to drive the image of the itinerary or MIR.

Enter: HQSC5F062.


Appendix A: Enhanced TINS Reports

Enhanced Ticket and Invoice Number System (TINS) holds information regarding Galileo generated documents for a period of between 31 and 90 days.

Note: The actual number of day’s retention is determined by the BSP Reporting Table stored in the Galileo system.

Three types of report are available:

Daily Activity Report (DAR)

Period Activity Report (PAR)

Summary Activity Report (SAR)

In addition, a combined search and sort feature is available for tracking and reporting specific ticket numbers and various items.

Note: Functionality provided by Enhanced TINS Reports is in addition to TINS entries discussed earlier in this course.

Daily TINS Reports

There are two daily TINS Reports:

Basic TINS Report

Daily Activity report (DAR)

Basic TINS Reports

The following example formats may be used.


HMPR Display the TINS report for today for own office

HMPR/XX9 Display the TINS report for today for branch office XX9

HMPR/E12345 Print the TINS report for today on printer GTID E12345

HMPR/02JAN Display the TINS report for a specific date

HMPR/ALL Display the TINS report for all transactions

HMPR/TKT Display the TINS report for ticket transactions only

HMPR/CU-EUR Display the TINS report in an alternative currency



Daily Activity Report (DAR)

ASK ANSWER 16210

The Daily Activity Report provides ticket details on a daily basis.

The basic display entry for the Daily Activity Report is: HMPR*E

The following formats may be used.


HMPR*E Display the Daily Activity Report for today for own office

HMPR*E/XX9 Display the Daily Activity Report for branch office XX9

HMPR*E/02JAN Display the Daily Activity Report for a specific date

HMPR*E/CU-EUR Display the Daily Activity Report in an alternative currency

HMPR*E/T Display totals only for the Daily Activity Report for today for own office

HMPR*E/E12345 Print the Daily Activity Report for today on printer GTID E12345

HMPR*E/E12345/T Print totals only for the Daily Activity Report for today for own office printer GTID E12345

Note: ALL and TKT modifiers are not available as the Search and Sort function may be used to further define the contents of the report.



Period Activity Report (PAR)

ASK ANSWER 16214

There is one Period Activity Report which consolidates data for multiple days as specified in the entry, or for an entire BSP reporting period.

Note: The relevant period is determined by the individual BSP Reporting Table stored in the Galileo system.

The basic display entry for the Period Activity Report is: HMPP



HMPP Display the Period Activity Report for own office

HMPP/XX9 Display the Period Activity Report for branch office XX9

HMPP/E12345 Print the Period Activity Report on printer GTID E12345

HMPP/02JAN Display the Period Activity Report for a specific date

HMPP/02JAN-07JAN Display the Period Activity Report for a specific date range

HMPP/CU-EUR Display the Period Activity Report in an alternative currency

HMPP/T Display totals only for the Period Activity Report for today for own office



Summary Activity Report (SAR)

ASK ANSWER16215

The Summary Activity Report provides a summary listing of ticket and stock control numbers that have been issued or voided during the reporting period.

The basic display entry for the Summary Activity Report is: HMPS



HMPS Display the Summary Activity Report for own office

HMPS/XX9 Display the Summary Activity Report for branch office XX9

HMPS/E12345 Print the Summary Activity Report on printer GTID E12345

HMPS/P Display the Summary Activity Report for the previous period


Appendix B: Module Review Answers

This appendix contains examples of answers to questions in the modules.

Your answers may vary slightly if you have made entries in the system, as your responses are current.

Module 2 Review: Issuing E-Tickets

1. Correct Answer: TKPDTD

Rationale: Ticket please, demand ticket device.

2. Correct Answer: TKPDTD

Rationale: Ticket please

3. Correct Answer: *HTI

Rationale: Display Tins Remarks

4. Correct Answer: Your ticket number here…

Rationale:

5. Correct Answer: HMPR

Rationale: Help Me Payment Report.

6. Correct Answer TRV/05799000354401

Rationale: Transmit a VOID

7. Correct Answer: No

Rationale: Check the carrier’s 2 letter codes (.AE entry) then enter DT/AAR/DIS-AF and Move down. UM is not included on the list.



Module 3 Review: Specific Passenger/Fare Selection

1. Correct Answer: TKP1

Rationale: Fare quote 1 is for segments 1 and 6 FRA JFK FRA

2. Correct Answer: TKP2P3

Rationale: Fare quote 2 is for segments 2–5 domestic USA, and the child is passenger 3.

3. Correct Answer: TKP1P1–3

Rationale: Fare quote 1 passengers 1, 2 and 3.

4. Correct Answer: TKP2P5

5. Correct Answer: TMU1P1F374296409071000*D1216*A0021 ; R.PSGR ; ER ; TKP1P1 or TKP1P1DTD

Rationale: Retrieve the Booking File and add the modifiers. FOP (credit card company code optional) expiry date and approval code. Received from and issue ticket. Note the plating carrier does not need to be passenger related, but the FOP and ticket command must be.

Module 4 Review: Ticketing Modifiers

1. Correct Answer: TMU1Z12

Rationale: Ticket modifier, filed fare 1, commission, percentage.

2. Correct Answer: TMU1F@CK

Rationale: Ticket modifier, filed fare 1, form of payment, change, new FOP.

3. Correct Answer: TMU1EBREFUND RESTRICTED

Rationale: Ticket modifier, filed fare 1, Endorsement in free format.

4. Correct Answer: TKP or TKPDTD Note the Booking File reference.

Rationale:

5. Correct Answer: TMU1F3739000 0000 0000*1216 *12345 # R.PSGR # TKP

Rationale: Ticket modifier for filed fare 1 credit card number/date/authority and plating carrier.



Module 5 Review: Manual Fare Build

1. Correct Answer: FBCP3/CBA

Rationale: Fare Build Create for passenger 3

2. Correct Answer: FBCP4*C08.1–3 or FBCP4*C08.1.2.3

Rationale: Fare Build Create, first screen to be passenger 4, who is a child, then second screen for passengers 1, 2 and 3.

3. Correct Answer: *FB1 ; FBUFARE/GBP500.00 ; FBUFC/ LON AF PAR AZ ROM M414.42AZ LON M414.42NUC 818.84 ; FBUTAX1/…ETC ; FBUTTL/; FBF

Rationale: Display the Filed Fare in Fare Build Format. Manual Update with new fare and new fare construction. A new total (TTL) must be added when making updates as the system will only amend the total automatically as the fare and taxes are initially entered, not on updates. Remember to file the fare.

5. Correct Answer: FBUFARE/GBP480.00; FBUFC/LON AF PAR AZ ROM M393.04AZ LON M393.04NUC 786.08; FBUTTL/ ; FBF ; R.PSGR ; ER ; TKPDTD

Rationale: The Booking File must be ended and retrieved before issuing a ticket.

Module 6 Review: Tour Ticketing

1. Correct Answer: True

Rationale: A travel agent usually has to sell the flight in conjunction with accommodation

2. Correct Answer: BT or BT*PC

3. Correct Answer: Z

Rationale: Commission modifying to 0

4. Correct Answer: FBUFB/YSPCL+BG/2PC+FARE/GBP448.00+ROE/0.547411+TAX1/20.00GB+TAX2/11.90UB+TAX3/1.40AY+TAX4/15.60US+TAX5/2.80XA+TAX6/1.70XF+TAX7/3.90XY+TAX8/2.80YC+TAX9/53.00YQ+FC/LON VS NYC 409.19YSPCL VS LON 409.19YSPCL NUC818.38

FBUPFCJFK4.5

TMU1EBVALID VS ONLY NO CHGE NO RERTE

TMU1TCVS12345/BT/Z0

Rationale: Ensure ticket has printed correctly



Module 7 Review: Net Remit 2

1. Correct Answer: AI–

Rationale: Airline Information

2. Correct Answer:

Rationale: VC–K will produce an actual amount of commission.

VC–C will provide a commission percentage figure.

3. Correct Answer: NF

Rationale: Net Fare

4. Correct Answer: TMU1AI–G54309X/VC–C0015

Rationale: Ticket modifier update, Airline Information code slash and Value Code for Commission.

Module 8 Review: Ticket Revalidation

1. Correct Answer:

Rationale: Tickets must be Galileo issue, The routing, fare and class must be the same as original ticket.

2. Correct Answer: TKRETS3/TN2364402657861/C3

Rationale: Ticket number 236…, segment 3 from booking and coupon 3 of ticket

3. Correct Answer: SI.BA*OFLD.BA107/LHRDXB/03AUG

Rationale:

Module 9 Review: Exchange Tickets

1. Correct Answer: TKP1FEX0759901891948

Rationale: Remember to include the filed fare number and full ticket number

2. Correct Answer: GBP124.00 BSR1.21431 =1.214

Rationale: FZSEUR152GBP FZSGBPEUR

3. Correct Answer: Tab to screen and enter S

Rationale:

4. Correct Answer: Ticket issues automatically.

Rationale:



Module 10 Review: Automated Refunds

1. Correct Answer: TRNE05576587612343/16JUL13

Rationale: It is more than 90 days since the ticket was issued so automatic refund procedure cannot be used.

2. Correct Answer: b. Tax Screen

Rationale: You have to show which taxes are to be refunded.

3. Correct Answer: HMPR/REF/09OCT–09OCT

Rationale: The date must be entered twice.

Module 11 Review: Itinerary Remarks

1. Correct Answer: RI.S3/CI*90

Rationale: Ensure correct segment number. Figure after * is not validated by the system.

2. Correct Answer: RI.HAVE A PLEASANT FLIGHT

Rationale: Free format after RI..

3. Correct Answer: *RIA

Rationale:

4. Correct Answer: RIR.1.2S3

Rationale: Ensure correct segment number and remarks numbers.

Module 12 Review: Linkage

1. Correct Answer: HMLMC8743ADI

Rationale: Help Me Link Machine followed by the printer number and the command for Demand Itinerary

2. Correct Answer: HMLMC6G43ADA

Rationale: As above, but for Demand Accounts

3. Correct Answer: HMLD

Rationale: Help Me Link Display

4. Correct Answer: HMOMC5F43A–U

Rationale: Help Me Operate Machine followed by Itinerary Printer number and U for up.



Module 13 Review: Ticket Stock Control

1. Correct Answer: HMTN/D

Rationale: How’s My Ticket Numbers Doing

2. Correct Answer: TRV/0019900505186

Rationale: Transmit a VOID followed by ticket number

3. Correct Answer: HMPR/29JUL

Rationale:

4. Correct Answer: HMINC5F062-*

Rationale: