| Tariff Display
PrivateFares is designed to integrate private and published fares in one
tariff display The low –to-high display makes it easy for you to choose
between a published and PrivateFares for the best quote to the client.
Negotiated fares are identified by a Dash (-) next to the carrier code.
How it Works
Use any tariff display format and then add
–PRI ACCOUNT CODE to your entry.
Example: $DORDLAX15NOV-PRI-ALPHA
If tariff display modifiers are used, they must precede the –PRI.
Example: $DMIALAX13JUL/PE25+US-PRI-ALPHA
You can use any tariff display modifiers with PrivateFares except:
Category Codes (Ex: -NLA)
Validated tariff (Ex: V15OCT22OCT)
Specific booking class (Ex: Q+AA)
Consult the TARIFF DISPLAY section of this document or HELP PRIVATE for a
listing of tariff display formats.
Back to Top
Additional Information
To lessen the number of keystrokes, use the
assumed city function (HMCT) to store account codes. If a negotiated fare
does not appear in the integrated tariff display, contact the coordinator at
the host location. In the tariff display shown below, the fares on lines one
and three are from the PrivateFares database for host location 6GY. Both
fares are associated with the account code ALPHA but each has its own
contract code. The fare on line one is a flat rate fare with a booking code
of Q. This fare is directional and applies only to travel originating in
Chicago. The fare on line three is a discount off the published YUA fare
with booking codes of Y, C, M and H.
Sample Integrated Tariff Display
|
$DORDLAX15NOV-PRI-ALPHA |
|
CHI - LAX DEPART 15NOV |
|
NORMAL/EXCURSION/PRIVATE FARES FOR 6GY |
|
U.S. PASSENGER FACILITY CHARGES MAY APPLY |
|
USD CONTRACT MIN/ CNL TVL DATES TKT DATES |
|
CX FARE CODE/FBC AP MAX FEE FIRST/LAST
FIRST/LAST |
|
1-AA 110.00R APRMTG. ++ ++/++ ++ -/31DEC
-/31DEC |
|
FLAT FARE BK: Q ACCT: ALPHA 6GY |
|
DIRECTIONAL-CHI/LAX |
|
2 TW 278.00R VNE7NR ++ SU/- NR -/- -/- |
|
3-UA 150.00 MAYMTG ++ ++/++ ++ -/31DEC
-/31DEC |
|
FBC: YUA BK: Y C M H ACCT: ALPHA 6GY |
Back to Top
|
When you want to: |
You enter: |
|
Use the minimum entry without an assumed
account code. |
$DORDMCO12NOV-PRI-ALPHA |
|
Use the minimum entry assumed account code |
$DORDMCO12NOV-PRI |
|
Designate multiple account codes (max. 3) |
$DBOSDEN25DEC-PRI-ALPHA-BETA |
|
Designate a specific account and contract
code |
$DBOSDEN-PRI-ALPHAnn]MAYMTG |
|
Use a follow-on to change normal tariff
display to integrate published and private fares |
$D-PRI-GAMMA |
|
Display only private fares |
$DBOSDEN-PRI-ALPHA-BETA:P |
Display only private fare formulas
Back to Top |
$DBOSDEN-PRI-ALPHA-BETA:F |
Customized
Access
These formats must be used at both the host and retail location when
setting up an agreement to access negotiated fare information through
PrivateFares. Authorization to use this function is given by the host
location.
|
When you want to: |
You Enter:
|
|
Add permission for the host
pseudo |
PAPERA/GK4nHOST/10 |
|
Display permission file |
PAPER* |
|
Delete permission for the
host pseudo |
PAPERD/GK4 |
Account Codes
|
When you want to: |
You Enter: |
|
Display a list of account
codes |
$P/ACCT |
Count the number of city
pairs in a PFR
Back to Top |
$P/CITY/CNT/ALPHA/APRMTG/DL |
Assumed City (HMCT)
To shorten the number of keystrokes, use the assumed city function before
accessing PrivateFares information in a tariff display.
|
When you want to: |
You Enter: |
|
Add pseudo city codes (max.
2) |
HMCT-GK4+J92/PRI |
|
Add an account code (max. 3) |
HMCT-
ALPHA+BETA+GAMMA/ACCT |
|
Cancel pseudo city codes |
HMCTX-PRI |
|
Cancel account code |
HMCTX-ACCT |
|
Cancel all assumed city
initializations including PrivateFares |
HMCTX
|
Rules Display
|
When you want to: |
You Enter: |
|
View rules for a specific
private fare from a $D |
$V1 |
|
View rules for a specific
segment from a fare quote ($B) response (NAFQ) |
$V:S2 |
View rules for a specific
component from a fare quote ($B) response (IFQ)
Back to Top |
FQN then
FN1 |
Pricing
When you want GlobalFares to
consider negotiated fares for a booked itinerary, you include an account
code with your $B input.
Example: $B-ALPHA
GlobalFares considers any
applicable private or published fare before responding with the host fare
for the booked itinerary. When you want to select a specific contract
for fare quote, you add the contract code to your entry. GlobalFares uses
this contract rather than all contracts applicable for the market.
Example: $B-APLHA[][]APRMTG
Consult the FARE QUOTE
section of this quick reference or HELP PRIVATE for a listing of fare quote
formats.
Back to Top
Additional
Information
You must store the
PrivateFares modifiers in an ATFQ field before issuing a ticket. If more
than one passenger exists in a record and only one of these is eligible for
a negotiated fare, use multiple ATFQ fields.
Fare Quote
|
When you want to: |
You Enter: |
|
Use the minimum entry to
price an itinerary at the host location |
$B-ALPHA |
|
Price using name select |
$BN2-1/-ALPHA |
|
Price using segment select |
$BS1*2 |
|
Specify itinerary segments |
$BS1-ALPHA+2 |
|
Specify a contact code
|
$B-ALPHAnnMAYMTG |
|
Specify a contract and fare
basis code (no published fares considered) |
$B-ALPHAnnMAYMTGn]Y9 |
|
Specify a contract and flat
rate fare (no published fares considered) |
$B-ALPHAnnMAYMTGnFLAT |
|
Price an itinerary using
only private fares |
$B-ALPHA/:P |
Specify itinerary segments
and exclude published fares
Back to Top |
$BS1GAMMA+2-ALPHA/:P |
Document Issuance
The normal ticketing entries
apply. A ticket for a negotiated fare may only be issued from an ATFQ field.
At document issuance, ticket designators, tour number or endorsement
information stored applicable to the account code will print on the ticket.
|
