Galileo Notes

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 8.
1
Module 8: Working with Airline Private Fares
Airline Private Fares allows air carriers who file fares with Air Tariff Publishing
Company (ATPCO) to provide you with private fare data directly into the
Galileo 360 Fares database. Airlines control access to the data and Galileo
360 Fares functionality is used for rule validation.
Your agency productivity is increased because less time is required to
maintain your own private fare records.
Module Objective
On completion of this module you will be able to work with Airline Private
Fares.
Working with Airline Private Fares
Airlines are able to file private fares and their corresponding rules and routes
with ATPCO, in the same manner as they file public fares for travel
throughout the world. Galileo 360 Fares receives airline private fare data
from ATPCO via electronic transmission three times a day.
Private fares filed with ATPCO have the same attributes as public fares, and
the only thing that differentiates them from public fares is their restricted use.
Security within ATPCO may limit their use to any of the following:
An agency pseudo city code and CRS code
An agency IATA number
An agency location
8.2 Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0
Using Private and Published Fares in Galileo
The default for fare display and fare quote includes airline supplied
private fares. For example, to display both public and private fares for
United Airlines, enter:
FD LAX SYD 10NOV /UA

Screen response:

Enter MD.

Note: Airline Private Fares are identified by a hyphen preceding the
airline code.
Fare display function identifier
Origin city
Destination city
Travel date
Carrier code
Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 8.3
Using Optional Modifiers
You may use optional modifiers when working with Airline Private Fares,
for both fare display and fare quote. The following modifiers are available
for differentiating between public and private fares.

Modifier: Definition:
:N Request public fares only.
:P Request private fares only.
When to use
Use an optional modifier when you wish to request private or public fares,
and override the system default.
How to use
Take the following step to display only private fares for United Airlines for
travel from Sydney to Los Angeles, and inhibit public fares from the
display. Enter:
FD SYD LAX 01NOV / UA :P

Screen response:

Origin city
Destination city
Travel date
Carrier code
Request private fares only
Using Account Codes
Airlines have the option of filing a private fare with an account code,
which may be used to categorise private fares by client, event or specific
type. An account code has a maximum of 20 characters, and may be
alpha, numeric or a combination of both. If it is assigned, it is required for
all fare display and fare quote requests, and airlines will communicate it
to the appropriate travel agencies.
When to use
Use an account code when an airline has advised you that it is required
for all fare display and fare quote requests.
How to use
Take the following step to display the private fare agreed with Maersk Air
for travel from London to Copenhagen, for account code BO. Enter:
FD LON CPH 01SEP /DM-PRI-BO

Screen response:

Origin city
Destination city
Travel date
Carrier code
Account code
Example Formats Fare Display
The following table illustrates some examples of formats using various
combinations of modifiers, and the fares displayed. Where no passenger
type is noted, adult is assumed.

Format: Fares displayed:
FDDENFRA5NOV-PRI-
SPRING
Public fares.
Airline private fares dates with no account
code.
Agency private fares with input account
code.
FDNYCROM10NOV Public fares.
Airline private fares with no account code.
FDNYCROM10NOV*MM Public and airline private military fares.
FDORDHNL10NOV:P Airline private fares with no account code.
No public fares.
FDPARNYC10NOV:N Public fares only.

Example Formats Fare Quote
The following table illustrates example formats for fare quoting an
itinerary with and without modifiers:

Format: Fares considered:
FQ Public fares and airline private fares with
no account code.
FQFALL Public fares.
Airline private fares with no account
code.
code.
FQBCASIAFARES Public fares.
code.
code.
FQACCT@@CONTRACT Public fares.
code.
code and specific contract.
FQ:P Airline private fares with no account
code.
FQBBACCT:P Airline private fares with no account
code.
code only.
FQBB:N Public fares only.
FQA Public fares and airline private fares with
no account code.
FQS3.4 Public fares and airline private fares with
no account code for segments 3 and 4
only.
FQ*N17 Public fares and airline private fares with
no account code valid for requester and
agency pseudo N17.
FQ*GR Public group fares, and airline private
group fares with no account code.

Net Fares
Airlines are able to advise ATPCO when filing a private fare whether the
amount is a net or selling level fare. The default for fare display and fare
quote includes airline supplied private fares, but a net fare will only be
considered if specifically requested.
The following modifier is available for fare display and fare quote.

Modifier: Definition:
:C Request net fares only.
When to use
Use the optional modifier :C when you wish to request net fares only.
How to use
Take the following step to display only net fares for United Airlines for
travel from Los Angeles to Sydney. Enter:
FD LAX SYD 01DEC / UA :C

Screen response:

Note: If the airline files the net fare with an account code, the account
code must be included with :C on fare display and fare quote inputs.
Origin city
Destination city
Travel date
Carrier code
Request net fares only
Module Review
Use your study guide and the Galileo system as you work, and write down your answers in the space
provided. When finished, check your answers in Appendix A: Answer Key.
1. Write down the entry to request a fare display of private fares only from Los Angeles to Paris for
15
th
of next month for Delta Airlines.
_____________________________________________________________________________
2. Write down the entry to request a fare display of private fares from Miami to Paris for the 15
th
of
next month for American Airlines, specifying account code AAEUR.
_____________________________________________________________________________
3. Write down the entry to fare quote segments 1 and 2 of an itinerary for airline private fares only
with no account code.
_____________________________________________________________________________
4. Write down the entry to display net fares for travel from Rio de Janeiro to Miami for 15
th
of next
month for Varig.
_____________________________________________________________________________

Module 9: Marking Up/Down Airline Private Fares
Agencies who maintain their own agency private fare database and also
receive private fare data directly into the Galileo 360 Fares database via
ATPCO, may manipulate the airline-supplied private fare in the same way
as any other.
By using Agency Private Fares (PF1) and Airline Private Fares in
combination an agency is able to be flexible with their pricing policy, and
also control distribution to other retail locations.
Module Objectives
On completion of this module you will be able to:
Interpret ATPCO Category 35
Mark up or mark down a private fare filed by an airline
Mark up or mark down a net fare filed by an airline
Interpreting ATPCO Category 35
Category 35 in the fare rule filed by ATPCO specifies the criteria for
determining multiple levels of fares as well as the data required for ticket
issuance. An airline can:
Detail the security for the fare and specify who is authorised to use
the fare
Specify the selling and net fare levels
Set parameters for agency created selling level fares
Specify the ticketing requirements such as printing of the baggage
allowance, tour code and ticket designator on all ticket types
Allow other locations access to the fare by group coding or selective
access


Working with Category 35
Within Category 35, an airline may file a net and/or a selling level fare.
An airline also has the option of giving update authority to an agency
location so they can create their own selling level fare using Agency
Private Fares. With this option the airline can specify a:
Minimum selling fare
Maximum selling fare
Selling fare range
Agency Private Fares can be used to create the selling level providing
the agency location has update authority in Category 35.
Minimum and maximum selling fare levels
When a minimum/maximum selling fare or a selling fare range is
specified, the result of the calculation must comply with the selling fare
parameters specified in the category.
Example 1
NET fare = GBP 100.00 and rule category 35 states a selling fare range
of GBP 125.00 GBP 150.00
Agency Private Fares contract states increase fare by 30%
The Agency Private Fare displays and quotes because it falls within the
selling fare range specified by the carrier.
Example 2
NET fare = GBP 100.00 and rule category 35 states a selling fare range
of GBP 125.00 GBP 150.00
Agency Private Fares contract states increase fare by 10%
The Agency Private fare does not display or quote because it does not
fall within the selling fare range specified by the carrier.
Displaying the Detail of Category 35
A follow-up entry is available in Fare Display to display the detail of
Category 35.
When to use
Use the Fare Display follow-up entry to display the detail of Category 35.
How to use
Take the following step to display the detail of Category 35 for the United
Airlines YGALTST7 net fare for travel from LAX to SYD displayed below.

Display the Category 35 detail for the fare on line 2. Enter:
FD*2/NET
Screen response:

Continued on next page

How to use (Cont.)
Screen description:

Entry: Explanation:
1. ATPCO fare references
2. Net fare detail
3. Specified minimum and maximum selling levels
4. Other restrictions
Marking Up or Marking Down a Private Fare Filed by an Airline
Assume your agency has negotiated a discount of 20% off United
Airlines BGALTST2 fare on all routes where it is applicable. This is a
private fare filed by United Airlines directly with ATPCO. All rules and
conditions of the fare apply, and there are no exceptions/overrides.
Example fare - SYD/LAX:

When to use
Create a discount Agency Private Fares record in Apollo when your
agency has negotiated a discount off a private fare filed by an airline.
How to use
Add the account name and account code to the Agency Private Fares
account table. For information, refer to Module 2: Account Names,
Account Codes and Contract Codes. Take the following steps to create
the discount fare in Apollo:
1. Display the first fill-in format, the general information screen. Enter:
$P/DISC

Response:

2. Complete the screen as follows and enter at the cursor after the X:

Private Fares function identifier
Discount fare identifier

How to use (Cont.)
Base Field
Field description:

Entry: Explanation:
P Only airline private fares are to be discounted/marked up
B Both public and airline private fares are to be
discounted/marked up
N Only public fares are to be discounted/marked up
C Only airline net fares are to be discounted/marked up
Screen 2, the first screen of the rules summary, is automatically
displayed.

3. As there are no overrides or waivers to the published rules, input N
and enter at the cursor. Complete the screen as follows:
No
overrides/
waivers
Enter at
the cusror

Note: No inputs need to be made to screen 3.
The city pair screen is automatically displayed.


4. Enter 999 as a world-wide wildcard. Complete the screen as follows
and enter at the cursor after the X:
999 = world-wide
wildcards
Enter at the cursor

5. Response that the Agency Private Fares record and cities are added:


How to use (Cont.)
6. Switch into the Galileo system and check that the fare displays
correctly. Enter:
FDSYDLAX19JAN/UA -PRI-UAPF

Galileo screen response:

Note: The agency private fare is displayed, showing the mark down
of 20%, as well as the original airline private fare filed by ATPCO.
Fare display input
Private Fares identifier
and account code
Marking Up or Marking Down a Net Fare Filed by an Airline
Assume your agency is applying a mark up of 10 per cent on United
Airlines YGALTST6 and YGALTST7 fares on all routes where they are
applicable. These are private fares filed as net fares by United Airlines
directly with ATPCO. All rules and conditions of the fares apply, and
there are no exceptions/overrides.
Example fares - LAX/SYD:

When to use
Create a discount Agency Private Fares record in Apollo when your
agency is marking up a net fare filed by an airline.

How to use
Add the account name and account code to the Agency Private Fares
account table. For information, refer to Module 2: Account Names,
Account Codes and Contract Codes. Take the following steps to create
the discount fare in Apollo:
$P/DISC

Response:


displayed.
Discount fare identifier
How to use (Cont.)
3. As there are no overrides or waivers to the published rules, input N
and enter at the cursor. Complete the screen as follows:
No
overrides/
waivers
Enter at
the cusror

Note: No inputs need to be made to screen 3.
4. Enter 999 as a world-wide wildcard. Complete the screen as follows
and enter at the cursor after the X:



How to use (Cont.)
6. Switch into the Galileo system to display the net fare you have
marked up, enter:
FDLAXSYD1SEP/UA-PRI-UAPF

Galileo response:

Fare display input
Private Fares identifier
and account code
Module Review 1
Use your study guide and the Apollo system as you work. When finished, check your answers in
Appendix A: Answer Key.
Assume your agency has negotiated a discount of 10% off all fares filed by United Airlines with a fare
basis code beginning with B. The discount applies to both public fares and airline private fare filed by
United Airlines directly with ATPCO. All rules and conditions of the fares apply, and there are no
exceptions/overrides.
1. Decide upon a suitable account name and account code and add them to the Agency Private
Fares account table.
2. Decide upon a contract code, and build the discount fare in Apollo.

Module Review 2
Use your study guide and the Apollo system as you work. When finished, check your answers in
Appendix A: Answer Key.
Assume your agency is applying a mark up of USD 200.00 to the airline net fare YGALTST6 filed by
United Airlines for travel from Los Angeles to Sydney. All rules and conditions of the fares apply, and
there are no exceptions/overrides.
1. Decide upon a suitable account name and account code and add them to the Agency Private
Fares account table.
Module 10: Security Setup for Private Fares
As a host agency you may give branch offices and other agency
locations access to your private fares.
Module Objective
On completion of this module, you will be able to:
Identify the security requirements for Agency Private Fares
Identify the security requirements for Airline Private Fares
Identifying the Security Requirements for Agency Private Fares
Galileo agencies input private fares data into the Apollo system using
Global Access. Global access is only required at the workstation where
private fares data is loaded, i.e. the host location.
Apollo
AAT
The AAT of the Apollo pseudo must be set as follows to identify the host
location and CRS which owns the private fares:
PFAR=Y/pcc*1G
STD Security Profile
The user must have a second level sign, and the PFARE field of the third
screen must be set to N Y
Note: Y in the second position permits input of Agency Private Fares.
If the user is required to give authority to other Agency Private Fares
users, the PFARE field must be set to Y Y
Note: Y in the first position allows the user to give Agency Private Fares
authority to other users.
Galileo
AAT
The AAT of the Galileo host and retail pseudo cities must be set as
follows:
PFAR = Y
If agencies are linked by group coding or Selective Access, the PFAR
field can be set up for the retailer with the hosts pseudo city code as
default, and the retailer may access the hosts private fares database
without having to specify the pseudo city code in the input. For example:
PFAR = Y/XC3
Note: Only one pseudo city code may be entered in this field.
Assumed City
In addition, retailers may use the assumed city function to specify two
default host pseudo cities. For example:
HMCT*XX8*XC3/PRI
Screen display:

A maximum of three pseudo city codes may be used with these
functions, i.e. one in the PFAR field in the AAT, and two in the HMCT
field.
Note: The assumed city function may also be used to store a maximum
of two frequently used account codes.
No requirement.
Identifying the Security Requirements for Airline Private Fares
AAT
The AAT of the Galileo pseudo city code must be set as follows:
PFII = Y
PFTA = Y
Note: The PFTA field identifies that the pseudo city code is truly an
agency, and is part of the security requirement for the distribution of
Airline Private Fares by ATPCO to the travel industry.
No requirement.
Redistributing an Airline Private Fare
An airline may give an agency location authorisation to redistribute an
airline private fare to branch offices and other agencies with whom they
have a business relationship. The host agency can control redistribution
within a group coding or Selective Access environment.
Note: If the airline has not given the host agency authorisation to
redistribute an airline private fare, other agencies cannot access it with
fare display or fare quote, regardless of any group coding or Selective
Access relationship.
Accessing Airline Private Fares by Default
If agencies are linked by group coding or Selective Access, then they
may access private fare information from a host agency by default
provided the AAT is set appropriately.
AAT
The PFAR field can be set up for the retailer with the host agencys
pseudo city code as default, and the retailer may access the hosts
private fares database without having to specify the pseudo city code in
the input. For example:
PFAR = Y/XC3
Note: Only one pseudo city code may be entered in this field.
Assumed City
In addition, retailers may use the assumed city function to specify two
additional default host pseudo cities. For example:
HMCT*XX8*XC3/PRI
Screen display:

Note: A maximum of three pseudo city codes may be used with these
functions, i.e. one in the PFAR field in the AAT, and two in the HMCT
field.
Not Using Default Functionality
If default functions are not used, then the pseudo city code of the host
agency must be used with fare display and fare quote inputs.
Example entries:

Requirement: Format:
Fare Display FDLON1SEPDEL/BA-PRI*XG4
Fare Quote FQ*XG4
Important note: If a retail agency has their own specific private fares,
but has the PFAR default set to point to another location/pcc, they must
include their own pseudo city code with fare display and fare quote
entries to access their own agency private fare information.
Module Review
1. What are the two requirements in the Apollo security profile for the individual responsible for
creating and maintaining their agency's private fares database?
_____________________________________________________________________________
_____________________________________________________________________________
2. What are the two security requirements in the Galileo AAT for an agency who wishes to work with
Airline Private Fares?
_____________________________________________________________________________
_____________________________________________________________________________
3. An agency wishes to redistribute an airline private fare to a branch office. What consent must be
in place before this can be done?
_____________________________________________________________________________
_____________________________________________________________________________
Notes

Module 11: Working with Selective Access
As a host agency you may give other agency locations access to your
Airline Private Fares and Agency Private Fares within a Selective Access
environment.
Security must be set up in the Galileo system to allow you to work with
Selective Access files.
Module Objective
Work with Selective Access Files
Working with Selective Access
At the host agency you must set up a Selective Access agreement to
allow your retail locations to access the database you have created.
Selective Access allows you to determine which locations may use your
private fares for fare display, fare quote and ticketing. You may give
permission to another pseudo city code whether or not it is a branch
office location, or to a group of agencies with whom you wish to have a
business relationship.
Adding to the Permission File
When you wish to allow another pseudo city code to access your
negotiated fares, you must add an agreement to your permission file to
put in place the business requirement.
When to use
Set up a Selective Access agreement when you wish to allow another
agency to access your Agency Private Fares database.
Assume you are host agency XXX1 (World Travel) and you wish to
permit pseudo city code YYY2 (Global Tours) to use your negotiated
fares database for fare display, fare quote and ticketing. You are not
group coded, and no other Selective Access agreement is in place with
this agency. Global Tours is not providing your agency with any
functionality.
How to use
Take the following steps in Galileo to set up a Selective Access
agreement to give permission to pseudo city code YYY2 (Global Tours)
to access your agencys Private Fares database.
1. Display the Selective Access agreement file to determine which
agreement number best satisfies your business requirement. Enter:
PAAGR*

Response:
1
2
3
4

Screen description:

Callout: Description:
1 Selective Access agreement numbers.
Note: Y indicates that the agreement number does
allow the functionality listed. N indicates that the
agreement number does not allow the functionality
listed.
2 Selective Access agreement number 9 allows only
Private Fares functionality.
3 Move down to view further agreement numbers
4 Private Fares functionality Y or N.

Selective Access function identifier
Agreement file display

2. Selective Access agreement number 9 permits access only to your
Private Fares database, and no other functionality. Should you wish
to provide additional functionality, scroll through the agreement file
display to select an appropriate agreement number, or display the
Selective Access agreement file find fill-in format to search for a
relevant agreement number. Enter:
PAAGRF

Screen response:

Tab to each field and type Y to allow access to a function or N to
disallow access to a function. Complete all the fields in the fill-in
format as required, and place the cursor to the right of the RUL RMV
tab and enter. If an agreement number exists matching the required
functionality, it will be displayed on the screen. If one does not exist,
your account manager can add one for you.
3. Add agreement number 9 to your Permission File, to allow Global
Tours access to your agencys Private Fares database. Enter:
PAPERA/YYY2 @GLOBAL TOURS/9

Note: The system responds with an asterisk.

Travel agency pseudo city code
Permission file add
Optional travel agency name
Selective Access agreement number
Agreement file find
How to use (Cont.)
4. Global Tours, to whom you gave permission, must add an agreement
to their Permission File to complete the Private Fares agreement,
even though they are not providing your agency with any
functionality. Selective Access agreement number 10 does not allow
any functionality. Enter:
PAPERA/XXX1 @WORLD TRAVEL/10

Points to note:
Selective Access agreements must be in place in each direction
between the two agencies to enable Global Tours to access your
negotiated fares database.
If your agency has an existing Selective Access agreement with
Global Tours, the original Selective Access agreement must be
deleted before the new required Selective Access agreement number
is added to your Permission File. To delete an existing Selective
Access agreement, enter:
PAPERD/YYY2

Permission file add
Selective Access agreement number
Permission File delete

Building Affiliate Files
If you wish to allow a group of agencies to access your negotiated fares,
you may group them under one name and build an affiliate file for faster
processing of permission files. Setting up an affiliate file establishes your
host agency as a headquarters, enabling you to create permission files
on behalf of the affiliated retail agencies.
When to use
Assume you are host agency XXX1 (World Travel) and you wish to
permit pseudo city codes AAA2 (Paris Travel), CCC3 (Oslo Travel), FFF4
(Rome Travel) and GGG5 (Lisbon Travel) to use your negotiated fares
database for fare display, fare quote and ticketing. You do not wish to
allow any other functionality, and will put in place Selective Access
agreement number 9. You are not group coded, and no other Selective
Access agreement is in place with these agencies.
How to use
Take the following steps in the Galileo system to build an affiliate file to
allow this group of agencies to access your Private Fares database.
1. Each of the retail agencies must designate your pseudo city code
XXX1 as the headquarters location. Enter:
PAHDQA/XXX1


Headquarters add
Headquarters pseudo city code
How to use (Cont.)
2. As the host agency, you assign an affiliate name and corresponding
affiliate code to the agency group and build the affiliate file, entering
the pseudo city codes and descriptions (names) of the affiliate
members, each separated by an end item. Partial entry:

PAAFFB/PFARE @PFARES/XXX1@WORLD TRAVEL+AAA2@PARIS TRAVEL

Points to note:
The system responds with an asterisk.
Subsequent agency pseudo city codes and descriptions may be
added to the partial entry above, each separated by an end item.

3. Add the agreement number to the authorisation section of the affiliate
file. Enter:
PAATHA/PFARE/XXX1@PFARE/9


Affiliate file build
Selective access function identifier
Affiliate code
Affiliate description
Affiliate member pseudo city
code and description
Affiliate member pseudo
city code and description

End item precedes each
subsequent affiliate member
pseudo city code and description
Authorisation add
Affiliate code
Headquarters pseudo city
code and affiliate code
Selective Access Agreement number

4. Add details of the agreement to the Permission Files of each of the
affiliate members, using Special Affiliate Processing. Enter:
PASAPA XXX1@PFARE/XXX1@PFARE

Points to note:
Special Affiliate Processing entries are processed at set times each
day. Check your supervisory message queue after processing has
taken place to verify that the procedure has been completed
successfully.
Building Customisers
Selective Access agreements may be customised to allow or disallow
access to specific Private Fares account codes and to specific agency
sign-on codes.
When to use
Assume you wish to allow retail agency Overseas Travel (pseudo city
code JJJ2) limited access to your agencys Private Fares database. You
wish it to access only your account codes DELTA and CARIB, and you
wish to restrict access to one agency member only, sign-on code
ZJJJ2/AB.
Special Affiliate Processing add
How to use
Take the following steps to build a customiser file, and include it with your
permission file entry when you add the agreement number to your
permission file.
1. Build the customiser file. Enter:
PACUSB/OT/FAC DELTA+CARIB/FAI ZJJJ2/AB


2. Provide Overseas Travel with Selective Access agreement number 9,
and include the customiser file reference with your permission file
entry. Enter:
PAPERA/JJJ2@OVERSEAS TRAVEL/9/OT

Customiser file build
Account code identifier
Account codes Delta and Carib
separated by an end item
Customiser file reference
Agency sign-on identifier
Permission file add
Selective access
agreement number

Points to note:
If an affiliate agreement is customised, the customiser reference is
included when the agreement number is added to the authorisation
section of the affiliate file. Example:
PAATHA/PFARE/XXX1@PFARE/9/OT

Additional Selective Access formats

When you wish to Enter...
Display your Permission File PAPER*
Display your Permission File to view
the agreement only with agency
pseudo city code KKK2
PAPER*/KKK2
Delete the agreement with agency
pseudo city code KKK2 from your
Permission File
PAPERD/KKK2
Display historical data for your
Permission File
PAPERH
Display historical data for agency
pseudo city code KKK2
PAPERH/KKK2
Display a list of affiliate files created by
your host agency
PAAFF*
Display authorized users of affiliate
PFARE
PAATH*/PFARE
Delete affiliate members UUU2 and
YYY6 from affiliate PFARE.
Note: Must be used in conjunction
with Special Affiliate Processing
PAAFFD/PFARE/UUU2
+YYY6
To display customiser file reference A1 PACUSD*/A1

Authorisation add
Affiliate code
Agreement number
Module Review
1. Write down the entry to display the Selective Access agreement find fill-in format.
_____________________________________________________________________________
2. You are providing agency pseudo city code RRR2 (Florida Tours) with Selective Access
agreement number 40. Write down the entry to add the agreement to your permission file
_____________________________________________________________________________
3. Write down the four steps that you must take to build an affiliate file.
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
4. Write down the entry to build a customiser file. You wish to allow access only to Private Fares
account code UAEUR and only sign-on code ZRRR2/GF.
_____________________________________________________________________________
5. Write the entry to add Selective Access agreement number 9 to your permission file for agency
pseudo city code SSS2 (Space Travel). Customize the agreement with customiser reference B3.
_____________________________________________________________________________
Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0 A.1

Appendix A: Answer Key
The following are sample answers to the Module Reviews contained in this study guide.
Module 2: Account Names, Account Codes and Contract Codes

1. $P/ACCT/ADD/DELTA/DELTA AIRLINES
2. $P/ACCT/MOD/DELTA/DELTA AIR
3. $P/ACCT/DEL/DELTA

A.2 Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0
Module 3: Building a Discount Rate Agency Private Fares Record

Review 1
Add the account name and account code to the account table:
$P/ACCT/ADD/MOD3/MODULE3
Display the fill-in format:
$P/DISC
Completed screen 1

Completed screen 2

Completed screen 3

Completed city pair screen

Review 2
Completed screen 1

Completed screen 2


Module 4: Working with Wildcards

$P/DISC
Completed screen 1

Completed screen 2


Display the geography table to verify the country code for the United Kingdom
and US state codes:
$P/GEOG/DIS/CO/U
$P/GEOG/DIS/ST

Display the Exception Cities - Add screen:
$P/XCTY/ADD/MOD4/M4/UA/GB/CA-US
Completed exception cities screen:


Display the Exception Cities - Add screen:
$P/XCTY/ADD/MOD4/M4/UA/GB/TX-US
Completed exception cities screen:

Module 5: Working with Zones
Review 1
1. $P/ZONE
Completed screen

2. Display the zone city add screen:

$P/ZONE/ADD/*MOD5

Completed screen

3. $P/ZONE/DEL/*MOD5/DFW

4. $P/ZONE/MOD/*MOD7/NEW DESCRIPTION FOR SOUTHERN USA CITIES
Completed screen

5. $P/ZONE/DEL/*MOD7

Review 2
$P/ZONE
Completed screen:

$P/DISC
Completed screen 1

Completed screen 2

Completed screen 2


Module 6: Managing your Private Fares Records in Apollo

1. 1. Display the existing PFR.
Example entry: $P/DIS/DELTA/DLEUR/DL
2. Over-type relevant fields in screens 1, 2 and 3 with new data as
appropriate.
3. Tab to Add, type X and enter.
4. Complete the city pair screen as appropriate and enter at END.

2.

1. Display the PFR.
Example entry: $P/DIS/DELTA/DLEUR/DL
2. Tab to Delete on screen 1, type X and enter. Tab again to Delete, type X
and enter to confirm deletion.
3. If there are no other contracts associated with this account code, delete
the account from the account table.
Example entry: $P/ACCT/DEL/AMEUR

Module 7: Using Agency Private Fares

1. FDCHILON21JAN-PRI-MILLER
2. FDLAXFRA21JAN-PRI-POWER:P
3. FD15JANIADLON-PRI-DELTAGOLDFILE
4. FN*3/S
5. FQ-POWER
6. FQ-DELTAGOLDFILE
7. FQS1.4-MILLER
8. HMCT


1. FDLAXPAR15JAN/DL:P
2. FDMIAPAR15JAN/AA@AAEUR
3. FQS1.2:P
4. FDRIOMIA15JAN/RG:C


Review 1
Completed screen 1

Completed screen 2

Completed city screen

Review 2
Completed screen 1
Net fares to be
marked up
Mark up of USD
200.00
Currency
code

Completed screen 2

Completed city screen


1. Second level sign
PFARE = N Y
2.

3.

PFII = Y
PFTA = Y
The airline must give the agency location authorization to redistribute the
private fare


1. PAAGRF
2. PAPERA/RRR2/40
3. 1. Each retail agency must designate the headquarters agency:
PAHDQA/XXX1
2. Build the affiliate file, entering the pseudo city codes and descriptions of
each of the affiliate members. Example entry:
PAAFFB/PFARE@PFARES/XXX1@WORLDTRAVEL
+AAA2@ALASKA TRAVEL
3. Add the Selective Access agreement number to the authorization section
of the affiliate file. Example entry:
PAATHA/PFARE/XXX1@PFARE/9
4. Add the detail of the agreement to the permission files of each of the
affiliate members, using Special Affiliate Processing. Example entry:
PASAPA/XXX1@PFARE/XXX1@PFARE

4. Example entry:
PACUSB/UA/FACUAEUR/FAIZZRRR2/GF
5. PAPERA/SSS2/B3/9

Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0 B.1
Appendix B: Building a Flat Rate Agency Private Fares Record
A Private Fares record (PFR) must be created for each flat rate fare that
has been negotiated. A flat rate fare is a fixed amount agreed by your
agency and the airline, and is valid for travel between specific cities.
Each PFR contains three areas for storing contract information. They
are:
General information
Rules summary
City pair data
Module Objective
Build a flat rate PFR in Apollo.

B.2 Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0
Building a Flat Rate Agency Private Fares Record
Assume your agency has negotiated a flat rate fare with American
Airlines for round trip travel originating Miami to points in the Caribbean.
The following is the detail and agreed conditions of the fare:

Detail/Condition: Application/Restriction:
Account name AA CARIBBEAN
Account code CARIB
Contract code CAR2004
Destination cities and fares Antigua: USD 350.00
Barbados: USD 450.00
Kingston: USD 400.00
Port of Spain: USD 525.00
St Maarten: USD 525.00
Application Round trip
Period of application Immediately 30 September 2005
First ticket date Effective immediately
Last ticket date 23 September 2005
Booking class K
Fare basis KCARIB
Tour code number AAMCARIB2004
Minimum/maximum stay SU/30 days
Advance purchase 7 days
Stopovers None
Endorsements/restrictions NONREF/APEX
Refund/cancellation penalty before
departure
USD 100.00
Change of reservation One change of reservation permitted
for outbound and inbound flights at
USD 50.00 each
Restricted travel dates 2, 20 and 24 December 2004
Other restrictions Travel only on American Airlines. No
voluntary rerouting


When to use
Create a flat rate Agency Private fare record in Apollo when your agency
has negotiated a flat rate fare with an airline.
How to use
Be sure the account name and account code have been added to the
Agency Private Fares account table. For information, refer to Module 2:
Account Names, Account Codes and Contract Codes. Take the following
steps to create the flat rate fare in Apollo:
$P/FLAT

Response:
1
2
3
4
5
6
7
8
9
10

Flat fare identifier

How to use (Cont.)

Screen 1 description:

Callout: Screen
Response:
Description:
1 $P Redisplay of Private Fares format entry.
FLAT RATE Private Fares record type.
SCREEN 1 General information screen.
Note: Screen 1 General information. Screen 2 First screen of
rules summary. Screen 3 Second screen of rules summary.
2 CONTRACT
CODE
Mandatory field. Identifies the negotiated agreement.
ACCT CODE Mandatory field. Identifies the account code entered in the account
table.
CX Mandatory field. Airline with which the fare has been negotiated.
3 FIRST TVL First date of travel for the flat rate fare.
Note: Assumed to be the current date when left blank.
LAST TVL Mandatory field. Last date the flat rate fare may be applied.
4 FIRST TKT First date that a ticket may be issued for the flat rate fare.
LAST TKT Last date that a ticket may be issued for the flat rate fare.
Note: When left blank, assumed to be the date entered in the
LAST TVL field.
5 BK CODE Mandatory field. Booking code for the flat rate fare.
Note: You may specify a maximum of four booking codes.
6 TKT FBC/
DESIGNATOR
Fare basis code and ticket designator to be printed on the ticket.
TOUR NBR Tour number to be printed on the ticket (if applicable).
7 ENDORSEMEN
T BOX
Allows for special ticketing requirements. Prints on the ticket when
issued.
8 OSI Other service information. Information entered appears in the rules
summary, and may be easily moved manually into the Booking File.
9 NOTES Freeform text area to store additional information relevant to the
contract.
10 SCREEN 2 When screen 1 is completed, type X and enter to move to screen 2.
SCREEN 3 When the first screen is completed, and if there are no inputs to be
made to screen 2, type X and enter to move to screen 3.
ADD When adding a contract with no rule data, type X and enter.
Note: No overrides are assumed.
MODIFY When modifying an existing Private Fares record, type X and enter.
DELETE When deleting an existing Private Fares record, type X and enter.


displayed.
Response:
1
2
3
4
5
6
7


How to use (Cont.)

Callout: Screen
Response:
Description:
1 $P Redisplay of Private Fares format
entry.
SCREEN 2 First screen of rules summary.
Note: Screen 1 General
information.
Screen 2 First screen of rules
summary.
Screen 3 Second screen of rules
summary.
2 PENALTIES Applicable cancellation penalties.
3
CHANGE/
REISSUE
Conditions relevant to itinerary
changes and ticket reissues.
4 FREQUENT
FLYER
Frequent flyer information.
5 FORM OF
PAYMENT
Applicable forms of payment.
6 NOTES Freeform text area to store
additional information relevant to
the discounted fare contract.
7 SCREEN 1 To return to screen 1, type X and
enter.
SCREEN 3 Second fill-in format screen for
rules summary. Type X and enter.
ADD Type X and enter to move forward
to the city pair fill-in format screen.
MODIFY When modifying an existing PFR,
type X and enter.
DELETE Use when deleting an existing PFR,
type X and enter.


3. Complete the screen as follows and enter at the cursor after X:

Screen 3, the second screen of the rules summary, is automatically
displayed.
Response:
1
2
3
4
5
6
7
8
9
10


How to use (Cont.)

Callout: Screen
Response:
Description:
SCREEN 3 Second screen of rules summary.
Note: Screen 1 General information.
Screen 2 First screen of rules summary.
Screen 3 Second screen of rules
summary.
2 PROHIBIT TVL This field is used to indicate when travel is
prohibited. Prohibited travel dates are
validated within the period of the contract.
The field has two lines the first is for
specific dates, and the second is for a
range of dates.
Note: The date format is day, month,
year.
3 SEASONAL TVL This field allows Galileo 360 Fares to
validate the seasonal application for date
ranges which make up a season.
Seasonality dates are validated within the
period of the contract.
4 FLIGHT APPL Flight applicability may be entered for
specific flight numbers, or for a range of
flight numbers.
5 ROUTINGS
- VIA
- NOT VIA
- CXN
This field is used to specify routing
restrictions, and requires city or airport
codes.
DIRECT
NONSTOP
If routing must be direct or non-stop, enter
a Y. If routing is waived, enter a W. If left
blank, the assumption is that there are no
restrictions.



Callout: Screen
Response:
Description:
6 ADV RES Advance reservation requirement may be
specified as a number of days.
ADV TKT Advance ticketing requirement may be
DAY RSTR
S M T W T F S
Day of the week restrictions apply to the
day(s) of the week that the fare is
applicable. Enter a Y if travel is restricted
to this day. Enter a W if the day of the
week restrictions are waived. The day of
the week restriction is validated. If left
blank, the assumption is that there are no
restrictions.
Note: Restrictions are applicable for both
outbound and inbound travel. When a
fare is valid on a specific day of the week
outbound, and on a different day of the
week inbound, two contracts must be built
which must be directional.
7 MIN
MAX
Minimum and maximum stay
requirements may be shown as a
numeric, or day of the week. Enter a W if
requirements are waived. If using a day
of the week, abbreviations are as follows:
SU, MO, TU, WE, TH, FR, SA.
STOPS Specify permitted stopovers.
8 TIME OF DAY
RSTR
Specify any time of day restriction.
9 NOTES Freeform text area to store additional
information relevant to the discounted fare
contract.
10 SCREEN 1 Type X to return to screen 1.
SCREEN 2 Type X to return to screen 2.
ADD Type X and enter to move forward to the
city pair fill-in format screen.
MODIFY When modifying an existing Private Fares
record, type X and enter.
DELETE When deleting an existing Private Fares
record, type X and enter.


How to use (Cont.)
4. Complete the screen as follows, and enter at the cursor:

Response:


City pair screen description:

Callout: Screen
Response:
Description:
1 $P Redisplay of Private Fares format.
2 CONTRACT
CODE
ACCT CODE
CX
The appropriate contract code,
account code and airline are
repeated here.
3 ORG Origin city. If a city or airport code is
not entered, the system reads from
left to right and repeats the code
from the previous ORG field.
DES Destination city. If a city or airport
code is not entered, the system
reads from left to right and repeats
the code from the previous DES field.
DI Directional indicator N (no) or Y
(yes). The entry from the previous DI
field is repeated when left blank.
Note: If no previous information is
available, it is assumed that the fare
is not directional, and N is entered
automatically.
O/R One way (O) or round trip (R)
indicator.
Note: If the one way or round trip
indicator is not entered, the indicator
from the previous field is repeated.
CUR Mandatory field. The currency code
for the flat fare.
Note: If a currency code is not
entered, the currency code from the
previous field is entered.
AMOUNT Base fare amount.
4 MORE To access additional space, tab to
MORE, type X and enter.
Note: There is no limit to the
number of city pairs for each
contract. A maximum of 7 city pairs
may be entered on each screen.
END Type X and enter to store the Private
Fares record.
ZONE Type X and enter to display the
screen to enter zone code (if
applicable).


How to use (Cont.)
Points to note:
Once you store the PFR, city pairs are placed in alphabetical order
by origin point on subsequent retrievals.
Cities and/or wildcards may be grouped together to speed the
building of your Agency Private Fares database. Refer to Module 4:
Working with Wildcards, and Module 5: Working with Zones.
5. Complete the screen with fare levels shown as follows:

Response that Private Fares record and cities added:

Note: When a negotiated fare has been added to the database, it
must be thoroughly tested to ensure that all rules and conditions
validate correctly.

What is Validated for Flat Rate Fares (International)
Rules and conditions
The following rules and conditions are validated.
Note: The routing of the fare is not validated.
Screen 1
Carrier
Booking code
First travel date/last travel date
First ticketing date/last ticketing date
Screen 2
No fields are validated
Screen 3
All fields are validated, except:
Time of day restrictions
Stopovers
Fare construction principles
No fare construction principles are applied to the fare quote.

What is Validated for Flat Rate Fares (North America)
Screen 1
Carrier
Booking code
Screen 2
Screen 3
Prohibited travel dates
Day of the week restriction
Seasonality
Redisplaying the Screen
You may redisplay the screen for the current Private Fares contract
on which you are working by entering one of the formats below:

When you wish to
redisplay
Enter...
The current screen $P*
Screen 1 $P*1
Screen 2 $P*2
Screen 3 $P*3
City screen $P*C

Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0 C.1
Appendix C: Building a Net-Net Rate Agency Private Fares Record
An Agency Private Fares record (PFR) must be created for each net-net
rate fare that has been negotiated. A net-net rate fare is negotiated as a
single amount between two cities, and then your agency or corporation
adds either a mark-up percentage or mark-up amount to arrive at the
selling price. Occasionally, both a mark-up percentage and a mark-up
amount may be added to arrive at the selling price.
Each PFR contains three areas for storing contract information. They
are:
General information
Rules summary
City pair data
Module Objective
Build a net-net rate PFR in Apollo.

C.2 Working with Agency Private Fares (PF1) and Airline Private Fares Version 1.0
Building a Net-Net Rate Agency Private Fares Record
Assume your agency has negotiated a net-net fare with United Airlines
for round trip travel originating London to cities in the north-east of the
USA. The following is the detail and agreed conditions of the fare:

Account name UA EASTCOAST
Account code UAEAST
Contract code APRMTG
Destination cities and fares Chicago: GBP 250.00
Los Angeles: GBP 300.00
New York: GBP 200.00
Washington: GBP 220.00
Mark-up amount GBP 50.00
Mark-up percentage 10%
Period of application Immediately 31 December 2005
First ticket date Immediately
Last ticket date 24 December 2005
Booking class M
Fare basis MIT7
Tour code number ITUAAPRMTG2004
Minimum/maximum stay SU/30 days
Advance purchase 7 days
Stopovers None
Endorsements/restrictions NONREF
Refund/cancellation penalty before
departure
No refund permitted
Change of reservation One change of reservation permitted
for inbound flights for GBP 50.00
Restricted travel dates 13 16 December 2005
Flight application Outbound travel only permitted on
UA flights 923, 929, 935 and 957
Other restrictions Travel only on United Airlines. No
voluntary rerouting

When to use
Build a net-net rate Agency Private Fares record in Apollo when your
agency has negotiated a net-net rate fare with an airline.
How to use
Be sure the account name and account code have been added to the
Agency Private Fares account table. For information, refer to Module 2:
Account Names, Account Codes and Contract Codes. Take the following
steps to build the net-net rate fare in Apollo:
$P/NET

Response:
1
2
3
4
5
6
7
8
9
10


Net-net fare identifier



Callout: Screen
Response:
Description:
NET-NET RATE Private Fares record type.
SCREEN 1 General information screen.
Note: Screen 1 General information. Screen 2 First screen of
rules summary. Screen 3 Second screen of rules summary.
2 CONTRACT
CODE
Mandatory field. Identifies the negotiated agreement.
ACCT CODE Mandatory field. Identifies the account code entered in the account
table.
CX Mandatory field. Airline with which the fare has been negotiated.
3 FIRST TVL First date of travel for the net-net rate fare.
LAST TVL Mandatory field. Last date the fare may be applied.
4 FIRST TKT First date that a ticket may be issued for the net-net rate fare.
LAST TKT Last date that a ticket may be issued for the fare.
Note: When left blank, assumed to be the date entered in the LAST
TVL field.
5 BK CODE Mandatory field. Booking code for the net-net rate fare.
Note: You may specify a maximum of four booking codes.
6 TKT FBC/
DESIGNATOR
Mandatory field. Fare basis code and ticket designator to be printed
on the ticket.
TOUR NBR Tour number to be printed on the ticket (if applicable).
7 ENDORSEMENT
BOX
Allows for special ticketing requirements. Prints on the ticket when
issued.
8 OSI Other service information. Information entered appears in the rules
summary, and may be easily moved manually into the Booking File.
9 NOTES Freeform text area to store additional information relevant to the
contract.
10 SCREEN 2 When the first screen is completed, type X and enter to move to screen
2.
SCREEN 3 When the first screen is completed, and if there are no inputs to be
made to screen 2, type X and enter to move to screen 3.
ADD When adding a contract with no rule data, type X and enter.
Note: No overrides are assumed.
MODIFY When modifying an existing Private Fares record, type X and enter.
DELETE When deleting an existing Private Fares record, type X and enter.

Screen 2 is automatically displayed.
Response:
1
2
3
4
5
6
7



How to use (Cont.)

Callout: Screen
Response:
Description:
1 $P Redisplay of Private Fares format
entry.
SCREEN 2 First screen of rules summary.
summary. Screen 3 Second screen
of rules summary.
2 PENALTIES Applicable cancellation penalties.
3
CHANGE/
REISSUE
Conditions relevant to itinerary
changes and ticket reissues.
4 FREQUENT
FLYER
Frequent flyer information.
5 FORM OF
PAYMENT
Applicable forms of payment.
information relevant to the discounted
fare contract.
7 SCREEN 1 To return to screen 1, type X and
enter.
SCREEN 3 Second fill-in format screen for rules
summary. Type X and enter.
ADD Type X and enter to move forward to
the city pair fill-in format screen.
MODIFY When modifying an existing PFR, type
X and enter.
DELETE When deleting an existing PFR, type X
and enter.
3. Complete the screen as follows and enter at the cursor after X:

Screen 3 is automatically displayed.
Response:
1
2
3
4
5
6
7
8
9
10



How to use (Cont.)

Callout: Screen
Response:
Description:
SCREEN 3 Second screen of rules summary.
summary. Screen 3 Second screen
of rules summary.
2 PROHIBIT TVL This field is used to indicate when travel
is prohibited. Prohibited travel dates
are validated within the period of the
contract. The field has two lines - the
first is for specific dates, and the
second is for a range of dates.
Note: The date format is day, month,
year.
3 SEASONAL
TVL
This field allows Galileo 360 Fares to
validate the seasonal application for
date ranges which make up a season.
Seasonality dates are validated within
the period of the contract.
4 FLIGHT APPL Flight applicability may be entered for
specific flight numbers, or for a range of
flight numbers.
5 ROUTINGS
- VIA
- NOT VIA
- CXN
This field is used to specify routing
restrictions, and requires city or airport
codes.
DIRECT
NONSTOP
If routing must be direct or non-stop,
enter a Y. If the routing is waived, enter
a W. If left blank, the assumption is that
there are no restrictions.

Callout: Screen
Response:
Description:
6 ADV RES Advance reservation requirement may
be specified as a number of days.
ADV TKT Advance ticketing requirement may be
DAY RSTR
S M T W T F S
Day of the week restrictions apply to the
day(s) of the week that the fare is
applicable. Enter a Y if travel is
restricted to this day. Enter a W if the
day of the week restrictions are waived.
The day of the week restriction is
validated. If left blank, the assumption
is that there are no restrictions.
Note: Restrictions are applicable for
both outbound and inbound travel.
When a fare is valid on a specific day of
the week outbound, and on a different
day of the week inbound, two contracts
must be built which must be directional.
7 MIN
MAX
Minimum and maximum stay
requirements may be shown as a
numeric, or day of the week. Enter a W
if requirements are waived. If using a
day of the week, abbreviations are as
follows: SU, MO, TU, WE, TH, FR, SA.
STOPS Specify permitted stopovers.
8 TIME OF DAY
RSTR
Specify any time of day restriction.
information relevant to the discounted
fare contract.
10 SCREEN 1 Type X to return to screen 1.
SCREEN 2 Type X to return to screen 2.
ADD Type X and enter to move forward to
the city pair fill-in format screen.
MODIFY When modifying an existing PFR, type
X and enter.
DELETE When deleting an existing PFR, type X
and enter.

How to use (Cont.)
4. Complete the screen as follows, and enter at the cursor:

City pair screen response:
1
2
3
4

City pair screen description:

Callout: Screen
Response:
Description:
2 CONTRACT
CODE
ACCT CODE
CX
The appropriate contract code, account code and
airline are repeated here.
3 ORG Origin city. If a city or airport code is not entered,
the system reads from left to right and repeats the
code from the previous ORG field.
DES Destination city. If a city or airport code is not
entered, the system reads from left to right and
repeats the code from the previous DES field.
DI Directional indicator N (no) or Y (yes). The entry
from the previous DI field is repeated when left
blank.
Note: If no previous information is available, it is
assumed that the fare is not directional, and N is
entered automatically.
O/R One way (O) or round trip (R) indicator.
Note: If the one way or round trip indicator is not
entered, the indicator from the previous field is
repeated.
CUR Mandatory field. The currency code for the net-net
rate fare.
Note: If a currency code is not entered, the
currency code from the previous field is entered.
NET AMT Base fare amount.
MRKUP AMT Mark-up amount.
Note: If no amount is entered, the amount from
the previous field is repeated.
MRKUP PCT Mark-up percentage.
Note: If no amount is entered, the percentage
amount from the previous field is repeated.
4 MORE To access additional space, tab to MORE, type X
and enter.
Note: There is no limit to the number of city pairs
for each contract. A maximum of 7 city pairs may
be entered on each screen.
END Type X and enter to store the Private Fares record.
ZONE Type X and enter to display the screen to enter
zone code (if applicable).

How to use (Cont.)
Points to note:
Once you store the PFR, city pairs are placed in alphabetical order
by origin point on subsequent retrievals.
Cities and/or wildcards may be grouped together to speed the
building of your Private Fares database. Refer to Module 4: Working
with Wildcards, and Module 5: Working with Zones.
5. Complete the screen as follows:

Response that Private Fares record and cities added:

Note: When a negotiated fare has been added to the database, it
must be thoroughly tested to ensure that all rules and conditions
validate correctly.
What is Validated for Net-Net Rate Fares (International)
Screen 1
Carrier
Booking code
Screen 2
Screen 3
All fields are validated, except:
Time of day restrictions
Stopovers

What is Validated for Net-Net Rate Fares (North America)
Screen 1
Carrier
Booking code
Screen 2
Screen 3
Prohibited travel dates
Day of the week restriction
Seasonality
Redisplaying the Screen
You may redisplay the screen for the current Agency Private Fares
contract on which you are working by entering one of the formats
below:

When you wish to
redisplay...
Enter...
The current screen $P*
Screen 1 $P*1
Screen 2 $P*2
Screen 3 $P*3
City screen $P*C

Agency Private Fares Formats
Account code = AAAAAA (maximum of 6 alpha or numeric characters. Alpha must be first)
Account name = NNNNNN (maximum 16 alpha, numeric or characters)
Contract code = CCCCCC (maximum 8 alpha or numeric characters)
Airline code = XX
Wildcard = WWWWW
Account Codes and Account Names
Display list
of account
codes
$P/ACCT
Add $P/ACCT/ADD/AAAAAA/NNNNNN
Display a list
of PFRS
associated
to an
account
$P/ACCT/DIS/AAAAAA
Modify $P/ACCT/MOD/AAAAAA/New Account Name
Delete $P/ACCT/DEL/AAAAAA
Agency Private Fares Records
Create $P/NET (To create a Net-Net PFR)
$P/DISC (To create a Discounted PFR)
$P/FLAT (To create a Flat Rate PFR)
Display $P/DIS/AAAAAA/CCCCCC/XX
Modify $P/DIS/AAAAAA/CCCCCC/XX (Make changes and enter X at MODIFY)
Delete $P/DIS/AAAAAA/CCCCCC/XX (Enter X at DELETE, and repeat to confirm)
City Pairs
Add $P/CITY/ADD/AAAAAA/CCCCCC/XX
Display $P/CITY/DIS/AAAAAA/CCCCCC/XX/LON/PAR
Modify $P/CITY/MOD/AAAAAA/CCCCCC/XX/LON/PAR
Delete $P/CITY/DEL/AAAAAA/CCCCCC/XX/LON/PAR
Count per
PFR
$P/CITY/CNT/AAAAAA/CCCCCC/XX
Apollo Encode Entries
City SCTY/MIAMI
State $P/GEOG/DIS/ST
Country $P/GEOG/DIS/CO
Countries
beginning
with letter S
$P/GEOG/DIS/CO/S
Wildcards
Add $P/CITY/ADD/AAAAAA/CCCCCC/XX
Display $P/WILD/DIS/AAAAAA/CCCCCC/XX
Modify $P/CITY/MOD/AAAAAA/CCCCCC/XX/WWWWW/WWWWW
Delete $P/CITY/DEL/AAAAAA/CCCCCC/XX/WWWWW/WWWWW
Exception Wildcard City Pairs
Add $P/XCTY/ADD/AAAAAA/CCCCCC/XX/WWWWW/WWWWW
Display $P/XCTY/DIS/AAAAAA/CCCCCC/XX/WWWWW/WWWWW
Delete $P/XCTY/DEL/AAAAAA/CCCCCC/XX/WWWWW/WWWWW
Zones
Zone Code = ZZZZZZ (Maximum 7 alpha/numeric characters)
Build $P/ZONE
Display list of
zones
$P/ZONE/DIS
Display zone $P/ZONE/DIS/ZZZZZZ
Modify
description
$P/ZONE/MOD/ZZZZZZ/New Description
Add cities and/or
wildcards
$P/ZONE/ADD/ZZZZZZ
Delete cities
and/or wildcards
$P/ZONE/DEL/ZZZZZZ/CLE
Delete Zone $P/ZONE/DEL/ZZZZZZ
Redisplay
Screen 1 $PR (or) $P1
Screen 2 $P2
Screen 3 $P3
Current screen $P
City pair screen $PC
Wildcard screen $PW
Audit Trail
Display audit
history
$P/AUDIT

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 1
Working with Agency Private Fares (PF1) and Airline Private Fares Evaluation
Please complete the following information:
Name
_____________________________________________________
Date
_____________________________________________________
E-mail address (if applicable)
_____________________________________________________
Contact telephone
_____________________________________________________
Title
_____________________________________________________
Manager
_____________________________________________________
Company
_____________________________________________________
Contact address
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
Evaluation
2 Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0
Time Allowed: 90 minutes
Use your study guide and the Apollo and Galileo systems as you work.
1. Which rules and conditions stored in screen 3 of a discount rate PFR are validated for
international travel?
______________________________________________________________________
2. What is the entry to access the help pages for Agency Private Fares in Apollo
______________________________________________________________________
3. What does wildcard AR2 identify?
______________________________________________________________________
4. You regularly work with Agency Private Fares and wish to set up the assumed city
function of your workstation to automatically check for account codes AMEX and ASIA.
Write down your entry.
______________________________________________________________________
5. Write down the Galileo entry to display only Airline Private Fares for travel on 1 June
from New York to London on United Airlines.
______________________________________________________________________
6. Write down the Galileo entry to display airline net fares for travel on 1 June from New
York to London on United Airlines.
______________________________________________________________________
7. What is the maximum number of cities and/or wildcards that may be used to create a
zone?
______________________________________________________________________
Evaluation
Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 3
8. Assume your agency has negotiated a discount of 20% off the BHXEE1 and BHWEE1
fares with Iberia for round trip travel originating Spain to New York, Washington and
Florida. Some overrides apply. The following is the detail of the fare:

Destination cities New York, Washington and the
US state of Florida.
Period of application Effective immediately 31
December 2005
Last ticket date 24 December 2005
Booking class B
Fare basis BHXEE1, BHWEE1
Stopovers None
Restricted travel dates 01 30 June and 1 31 August
2005
Other restrictions Travel only on Iberia. No
voluntary rerouting
Form of payment NONREF AGT
a. Decide upon a suitable zone code (include your initials) and description, and create a
zone comprising the destination cities in the USA (the two specified cities and Florida).
b. Use your own account code, decide upon a contract code, and build the flat fare in
Apollo. Use the zone that you created.
Write down your zone code, and also the account code and contract code of your PFR.
______________________________________________________________________
______________________________________________________________________
Evaluation
4 Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0
9. Assume your agency wishes to apply a mark up of 5% to the YGALTST7 fare with United
Airlines on all routes where it is applicable. This is an Airline Private Fare filed as a net
fare by United Airlines directly with ATPCO. All rules and conditions of the fares apply,
and there are no exceptions/overrides. The last travel date for the discounted fare is 31
December 2005.
Use your own account code, decide upon a contract code and build the discount fare in
Apollo.
Write down the account code and contract code of your PFR.
______________________________________________________________________
______________________________________________________________________
Note: Be sure that you test both fares that you build to make sure that they display correctly
in the Galileo system.

Galileo Notes

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Galileo Notes

Enviado por

Direitos autorais:

Formatos disponíveis

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 8.

Você também pode gostar