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, in order that the agent can take advantage of automatic ticketing.

Points to note

A manual fare build can only be created in a retrieved Booking File.

Manual fare builds can be created

 

• For all passengers
• For selected passengers
• For all segments
• For selected segments
• With passenger description codes

There are three basic steps in the process :-

• Create the Manual Fare Build FBC
• Update / Amend the data FBU
• File the Manual Fare FBF

Creating the Fare Build Screen.

 

Enter: FBCCXX (XX being your two digit carrier code)

All the entries are made at the bottom of the screen and are then placed automatically by the Galileo system into the appropriate place on the Fare Build Screen.

 

Just like a normal fare quote, the creation of a 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.

 

FBCP5/CXX Fare Build Screen for passenger 5 only

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

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

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

 

It is also possible to create a manual fare build screen for a particular passenger description code.

FBCP5*C08/CXX Fare Build Screen for passenger 5, description as child aged 8 years.

FBCP2*C08.1/CXX Fare Build Screen for passenger 5, description as child aged 8 years, plus passenger 1 adult.

 

If no passenger description codes are used the system will default to adult or infant if specified in the name field.

The @ symbol on the manual fare build screen denotes mandatory fields

They should be self explanatory, but here is a list as a reminder:

FB Fare basis

BG Baggage

FARE Fare (local currency)

ROE IATA Rate of Exchange

TTL Total (Fare plus taxes)

FC Fare construction (NUCs)

If any of these fields are omitted, you will not be able to file the fare

All other fields are optional and may be completed as required by the IATA ticketing standards.

Updating the fare build screen

The Fare Build Screen must be completed using Fare Build Update entries, which can be done one at a time or in string linked by the + key.

Take the following steps to update the Fare Build screen :

Enter: FBU Fare Build Update

Here is a typical entry for one item, updating the Fare Basis:

FBUFB/YAHPX

The system clears the screen when making this response, so you must make a display entry if you want to recall the Fare Build Update screen.

To redisplay the Fare Build screen, take the following steps:-

Enter: *FB Display Fare Build

Note: The Fare Basis has now been filled in and you can continue with the rest of the fields.

Here are some examples of updating the mandatory fields for this Booking File. Entries can be made in any order – not necessarily the order shown on the Fare Build Screen.

 

FBUBG/2PC Baggage

FBUFARE/GBP875.00 Fare

FBUROE/0.685018 IATA rate of exchange

FBUFC/LON NYC LON Fare construction

FBUTTL/958.10 Total (Fare plus taxes)

 

Note: TTL will be added automatically by the system, once fare and taxes have been input. You only need to make an entry in this field if the details are different, i.e. Inclusive Tours etc, or when you amend a previously saved Filed Fare.

 

Any of the entries may also be strung together using the + symbol, e.g.

FBUFB/YAHPX+BG/23K+FARE/GBP409.00

 

Here are some non-mandatory entries:

 

FBUNVB/20JUL07 Not valid before

FBUNVA/26JUL07 Not valid after

FBUTAX1/40.00GB+TAX2/8.40UB+TAX3/5.00YQ+TAX4/1.70AY+TAX5/17.40US+TAX6/3.30YC+TAX7/2.00XF+TAX8/2.10XA+TAX9/3.30XY

Update up to 20 tax boxes. (If more than 8 taxes apply, those from 8 onwards will be grouped together in box 8 with the XT symbol and can be shown individually with a follow up entry, *FBTAX)

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.

FBUEB/NO CHANGE OF RES

 

The FB, NVB, NVA and BG entries can all be segment related,

e.g.: FBUBG1/23K+BG2–3/2PC Baggage is 23K for segment 1, and 2PC for segments 2 and 3

 

Note: The line number used in the segment related entries is the number shown on the far right of the Fare Build Screen, which is not necessarily the segment number in the itinerary. The Fare Build Screen ignores any ARNK segments for numbering purposes.

Passenger Facility Charges

If PFCs apply to the itinerary, they can be added to the fare build screen In addition to the tax entry for the PFC amount (code XF), it is necessary to tell the system to which airports it applies.

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 a FBU string.

The system is not able to validate the city and value or that the PFC entry matches the XF tax entry. It is therefore advisable to consult

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

A maximum of 4 PFCs are allowed. When more than one PFC is to be added to the ticket, all PFCs must be input as a single entry;

e.g. FBUPFC/JFK3BUF3DEN4.50PHL4.50

using the USD amount, no matter where the ticket is being sold.

Any PFCs entered will appear on the Fare Build Screen in the Fare Construction line, but can only be entered after completion of the fare construction and ROE entries.

 

When the fare build screen has been completed, it must be filed in order to save the fare. The action of filing the fare, converts it from being a fare build, to a Filed Fare.

Multiple Passengers / Different Passenger Descriptions

When a Booking File is created for more than 1 passenger, it is important to ascertain what type of passenger description they have, e.g. a child, prior to proceeding to a Manual Fare Build.

The first step is to make the manual fare build entry as standard e.g. FBCCMS

The system has created a Fare Build Screen for each passenger. Note this one has a top line showing P01 (Passenger 1) and 01 of 03 i.e. first of three screens.

 

Once the first screen has been completed and filed (FBF), the next Fare Build Screen would appear automatically for passenger 2 and so on.

This would need to be completed with exactly the same information, which could get tedious if there were seven passengers !

 

However, once the first screen has been completed, all remaining passengers with identical fare information can be filed using one entry

Enter: FBFALL

 

Formats:

Explanation:

FBF

File current passenger screen.

ALL

All passengers

Similar logic applies when the passenger types are different. If there are two types of passenger, you must complete at least two Manual Fare Build screens.

It would appear that if a Booking File contained 3 passengers, the thirds being a child, that the logical entry to arrange Fare Build screens would be:

FBCP1.2.3*C09

However, the system works logically and would show the screen for passenger 1 first. After completing the screen, the entry FBFALL could not be used because passenger 3, a child, requires different Manual Fare Build details than the information used for the other two, adult, passengers. You would need to complete the second screen for the second adult, and finally complete the third screen for the child.

 

So a more effective way to action this scenario is to start the entry with the smallest group of passengers – in this case the child.

FBCP3*C09.1.2

Once this screen has been completed and filed, using the entry FBF, the child’s fare will be filed, and the first adult's (passenger 1) screen will appear.

After completing the first adult screen, the entry FBFALL can be used 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.