glbstop(2).gif (1508 bytes)






English Home
Up one level


©2005 Galileo International.
Privacy | Terms of Use

  

HHPR - Pricing Record

Error Responses and Agent Alerts

Basic Steps to Complete a Pricing Record

Requesting Pricing Record Fill-in-Format

Displaying Pricing Record Screens

Cancel Pricing Records

Completing a Name /Itinerary Screen ($NME)

Completing a Tax Breakdown Screen ($TA)

Completing a Fare Construction Screen ($FC)

References

When Apollo does not automatically price an itinerary, you need to complete a Pricing Record. Pricing Records consist of three possible fill-in-format screens:

Name/Itinerary ($NME)
Tax Breakdown ($TA)
Fare Construction ($FC)

This quick reference outlines the basic steps to complete a Pricing Record, including the steps for filling in each of its three screens. It also shows how to display each screen so you can make any necessary changes to a record.

Note: A pricing Record can be completed only after the basic PNR fields (name, phone, received, ticketing, and the itinerary) have been entered.

Basic Steps to Complete a Pricing Record

  1. Request the Pricing Record fill-in-format. Refer to the Requesting Pricing Record fill-in-format section.
  2. Complete the Name/Itinerary screen. Refer to the Completing a Name/Itinerary Screen section.
  3. Fill in the Tax Breakdown screen. Refer to the Completing a Tax Breakdown Screen section.
  4. Store the Pricing Record.

Example of completed Pricing Record.

To Store: Enter:
For a single passenger HBT
For multiple passengers HBTA
  1. If applicable, fill in the Fare Construction screen. Refer to the Completing a Fare Construction Screen section.

  2. Type T:OK to enable ticketing.
  3. End transact the PNR by typing E or ER.

Requesting Pricing Record Fill-in-Format

To Request Without Ticketing Modifiers Enter:
For all passengers HHPR

 

To Request With Ticketing Modifiers: Enter:
For all passengers HHPRZ11
For all passengers in the first name field with a carrier override (CO) and commission of $175.36 HHPRN1/CCO/Z$175.36
For the second name field, first passenger, commission of 10 percent, and ticket designator 1234
Back to Top
HHPRN2-1/Z10/GTD1234

Displaying Pricing Record Screens

You can view and/or change information entered in Pricing Record screens by using the formats described below.

To Display Before E or ER: Enter:
Name/Itinerary $NME

 

To display After E or ER: Enter:
Name/Itinerary screen for the first passenger from a single ATFQ field $NME1
Name/Itinerary screen for the second passenger from a single ATFQ field $NME2
Name/Itinerary screen for the first passenger from the second ATFQ field $NME1/2
More of the name/Itinerary screen $MD or $MU
Tax Breakdown screen for the first passenger $TA1
Tax Breakdown screen for the second passenger From the second ATFQ field $TA2/2
Fare Construction screen for the first passenger $FC1
Fare Construction screen for the second passenger from the first ATFQ field
Back to Top
$FC2/1

Cancel Pricing Records

To cancel: Enter:
All Pricing Records XPR
The second Pricing Record XPR2
The third and fourth Pricing Record XPR3+4

Completing a Name /Itinerary Screen ($NME)

After requesting a Pricing Record, the Name/Itinerary screen appears.

  1. Complete the Name/Itinerary screen ($NME). Refer to the completed screen example and field descriptions below to help you complete it.
  2. After completing the appropriate fields tab to BOOK and press Enter.

If you said yes to DO TAXES APPLY the Tax Breakdown screen appears. If you said not to do taxes apply you will need to store the Pricing Record.

Example:

Field: Description:
F/B Fare basis code for each segment.
VALUE Base value of local or through fare. For connections. Type 0.00 for initial leg(s).
NVB/NVA





Back to Top
Total base fare of ticket in the currency of origin country.
1st set of dots (3) are for the currency code.
2nd set dots (8) are for the fare amount. Type the actual value (i.e. 2644.00) or have Apollo calculate the fares.

 

To Calculate: Type:
Base fare plus 10% US tax A
Base fare only B
DO TAXES APPLY Identifies whether taxes apply Y or N is required

Y – Taxes do apply. Once the $NME screen is complete, the Tax Breakdown Screen appears.

N – Taxes do not apply. The total fare is equal to either FARE or EQUIV FARE.

EQUIV FARE Equivalent fare when payment is made in currency other than currency shown in the FARE filed.
1st set of dots (3) are of the currency code.
2nd set of dots (8) are for the base fare amount.
COMM Commission to be received. The Z modifier can define the commission amount or you can enter the amount at this time.

 

For: Type:
Actual dollar amount $29084 (no decimal)
Percentage amount 11.00/
F CONST Fare construction identifier. If you want to enter linear fare construction date, type "y" before you complete the $NME screen. Otherwise Apollo automatically fills in the data.
TD


Back to Top
Ticket designator area. The GTD modifier can define the ticket designator or you can enter the ticket designator at this time.

Completing a Tax Breakdown Screen ($TA)

  1. Complete the Tax Breakdown screen ($TA). Refer to the completed screen example and field descriptions below to help you complete it.
  2. After completing the appropriate fields press Enter.
    The Tax Breakdown screen automatically appears when you type a "Y" in the
    DO TAXES APPLY field on the name/Itinerary screen.

Example of Tax Breakdown screen:

Note: The FARE field cannot be changed on this screen. If the fare is incorrect, the changes need to be made on the $NME screen.

Field: Description:
TTL Optionally, you may enter the total. Otherwise, Apollo will automatically calculate the total amount (base fares and taxes) after you’ve completed the Tax Breakdown screen.
ROE (optional field) The ROE is the IATA rate of exchange that was used to convert the total NUC amount into the local currency.
TX A minimum of one tax must be entered. A tax code must be entered for all value amounts. Taxes and codes may be entered in any order.

Note: Zero values are not allowed. If an exempt tax is applicable, type an "E" in place of an actual dollar amount in the value field followed by the appropriate tax code

U.S. Passenger Facility Charges (PFC)

Back to Top
When you enter a PFC (Passenger Facility Charge) amount with an XF tax,  you  must fill in the appropriate 3-character airport code(s) and the applicable airport amounts.

Completing a Fare Construction Screen ($FC)

The Fare Construction screen displays automatically when you type HBT or HBTA after completing the $TA screen. The initial request for the Fare Construction screen is made when you type a "Y" in the F CONST field on name/Itinerary screen.

1.  Fill in the Fare Construction screen ($FC). Refer to the
    completed example and field descriptions below to help
    you complete it.

2. After completing the fare construction information tab to the
    right of the tax information and press Enter.

Note: For additional linear examples refer to HELP LINEAR.

Example of Fare Construction screen:

Field: Description:
FC Freeform area to complete the linear fare construction.
Tax data




Back to Top
Breakdown of tax data appears after the word END (if present) The tax data is unchangeable from this screen, however, the data can be changed from the $TA screen.  Tax data could be on one or more lines, or start in the middle of a line.

Error Responses and Agent Alerts

Agent Alert: Cause:
GF not allowed with Pricing Record The free or zero fare ticketing modifier with pricing is not allowed in conjunction with a manual pricing record. Either build a pricing record with zero values or use the GF modifier without building a pricing record.
QEP/Cancel Pricing Record A change to the itinerary that requires the pricing record be cancelled and rebuilt. The PNR can be queued instead to temporarily bypass the pricing record rebuild. The pricing record will have to be rebuilt in order to issue a ticket This applies regardless of the type of itinerary change, air or non-air.

First display your pricing record $NME1.
Make any necessary changes.
Tab to the end of the screen and enter. Type HBT or HBTA.
Type T:OK.

 
Unable - Only one form of payment per ATFQ Only one form of payment is allowed per stored ATFQ, including stored pricing records.
Unable/16 Segment limitation - use segment select

Back to Top

Users are limited to creating pricing records for PNRs that have 16 segments or less.

 

References

To Display: Enter:
All countries that have a table stored $TAX
Tax tables by the country name $TAX-GERMANY
Passenger facility charges by city $PFC-LAX
Passenger facility charges by airline $PFC-TW
Country currency codes by country S*COU/GERMANY

Site Menu / Up One Level / Search / FAQ / Top / Your Feedback