Fares
Fares transactions may be added to a batch by using criteria sets, and strikeover. This topic discusses a third process: manually adding transactions to a new batch (commonly called blank screen).
To create new transactions using blank screen, follow these steps:
Create a batch. For more information, see Create a Batch. The Create New Batch screen will display.
Type fares data in required and optional fields as described in the tables below. You can also copy and paste existing rows. To copy a row, select the row and then right-click the row. Click the Copy command. Place your cursor on a blank row. Right-click the row and then click the Paste command.
By default, 13 rows for fare
transactions are available on a blank screen. If you wish to add
extra rows, type the desired number of rows in the Add
blank lines field and then click the
button. As many as 99 blank rows may be added at one time. To
add one row at a time, you can also right-click on the blank screen
and then click the Insert Row
command. When creating a new batch you can copy multiple rows
and paste them into multiple blank rows.
Click the
button. Fare transactions will be stored with a status of Not
Validated.
You can also store transactions by clicking the Validate, Apply, or Release buttons. Additionally, if you navigate to another screen, the transactions will be automatically saved. For more information, see Validate Batch Transactions, Apply Batch Transactions, and Release a Batch.
Field Name |
Field Description |
Act. Code |
Type the action code N, which indicates "new". |
LOC1/LOC2 |
Type the location codes of the market pair. |
Fare Class |
Type a fare class code. |
OW/RT |
Type 1 to indicate that the fare is for one-way travel. Type 2 to indicate that the fare is for round-trip travel. |
Fare Amount |
Type the fare amount. The format used must match the requirements of the currency code. For example, if you want a fare amount of $100.00 United States dollars, the fare amount must be typed as 100.00 (not 100. or 100). Similarly, if you want the fare amount to be 300,000 Japanese yen, the fare amount must be typed as 300000. (not 300000.00). |
CUR |
Type the currency code of the fare amount. In most cases, the currency of the country of the first city or airport in the market pair, but a different currency could be used. |
FN |
This field is optional. Type a footnote code. In US/CA domestic tariffs and in add-on tariffs, a fare can hold as many as two footnotes but one of those footnotes must be a directional footnote (F or T). |
RTG |
Type a routing number. Routing numbers consist of four digits. To indicate that the fare is mileage based, type the routing number 0000.
|
Eff. Date |
This field is optional; in most cases it is left blank because the transaction will assume the effective date of the batch. If you want to use a different effective date than that of the batch, type a date using the DDMMMYY format. |
Field Name |
Field Description |
Act. Code |
Type the action code N, which indicates "new". |
LOC1/LOC2 |
Type the location codes of the market pair.
|
Fare Class |
Type a fare class code. |
OW/RT |
Type 1 to indicate that the fare is for one-way travel. Type 2 to indicate that the fare is for round-trip travel. |
Base Amount/ Tax Amount/ Fare Amount |
Type the fare amount in either the Base Amount or Fare Amount fields. The difference between the two fields is that when you are using a tariff that is subject to U.S. domestic transportation sales tax, values typed in the Base Amount field will, upon validation, have the tax added automatically with the sum total displaying in the Fare Amount field. Similarly, values typed in the Fare Amount field will, upon validation, have the tax deducted automatically with the sum total displaying in the Base Amount field. Most users prefer to type values only on the Fare Amount field. This is because most carriers prefer that the post-tax fare amount is an even dollar amount and by using the Fare Amount field only they don't have to calculate sums. For example, if you type 100.00 in the Fare Amount field, the Fares program will automatically calculate that the tax is 6.98 and that the base amount is 93.02 (based on a tax of 7.5%). |
CUR |
Type the currency code of the fare amount. Valid currency codes for US/CA fares are CAD (Canadian dollar) and USD (United States dollar). |
FN |
This field is optional. Type a footnote code. In US/CA domestic tariffs and in add-on tariffs, a fare can hold as many as two footnotes but one of those footnotes must be a directional footnote (F or T). |
RTG |
Type a valid routing number. Routing numbers consist of four digits but US/CA fares display the routing numbers as three digits. To solve this, the program will add a leading zero to the routing number when the transaction is saved. For example, if you type 16, the program will store it as 016. However, the actual routing number in the Routing program is 0016. |
Eff. Date |
This field is optional; in most cases it is left blank because the transaction will assume the effective date of the batch. If you want to use a different effective date than that of the batch, type a date using the DDMMMYY format. |
Field Name |
Field Description |
Act. Code |
Type the action code N, which indicates "new". |
LOC1/LOC2 |
Type the location codes of the market pair. |
Fare Class |
Type a fare class code. |
OW/RT |
Type 1 to indicate that the fare is for one-way travel. Type 2 to indicate that the fare is for round-trip travel. |
Fare Amount |
Type the fare amount. The format used must match the requirements of the currency code. For example, if you want a fare amount of $100.00 United States dollars, the fare amount must be typed as 100.00 (not 100. or 100). Similarly, if you want the fare amount to be 300,000 Japanese yen, the fare amount must be typed as 300000. (not 300000.00). |
CUR |
Type the currency code of the fare amount. In most cases, the currency of the country matching the location in the LOC1 field , but a different currency could be used. |
FN |
This field is optional. Type a footnote code. In US/CA domestic tariffs and in add-on tariffs, a fare can hold as many as two footnotes but one of those footnotes must be a directional footnote (F or T). |
RTG |
Type a routing number. Routing numbers consist of four digits. To indicate that the fare is mileage based, type the routing number 0000.
|
Add-On Zone |
Type the three digit add-on zone against which the add-on fare applies. Add-on zones describe the international fares with which they combine. For example, if your carrier has defined add-on zone 200 as "Any point in the United States", add-on fares that hold zone 200 may be combined with fares to or from the United States (other combinability conditions may also apply). |
Eff. Date |
This field is optional; in most cases it is left blank because the transaction will assume the effective date of the batch. If you want to use a different effective date than that of the batch, type a date using the DDMMMYY format. |
Add-on fares do not have rule numbers. Instead, they adopt the rules of the fare with which they combine.
It is possible to perform other actions on a blank screen besides the creation of new fares; you can also cancel or modify fares. However, it is much easier to perform those actions with criteria sets or strikeover.
To cancel or modify a fare with blank screen, you must type all information about the existing fare exactly as it is held in the database including the location codes, fare class code, one-way/round-trip indicator, fare amount, currency, footnote code(s) (if applicable), routing number, and add-on zone (if applicable). Then, you can type an action code in the Act. Code field (X for cancel, I for increase, R for reduction, and blank for any other change). You can then use the change fields (Chg. FN, Chg. RTG., Chg. Add-on) to change the footnote(s), routing number, or add-on zone.
The action codes I and R are not required. If you type a lower fare amount, the program will recognize it as a reduction. If you type a higher fare amount, the program will recognize it as an increase. If you type the wrong action code (for example, I when you are reducing the fare amount), the system will, upon application, return the transaction with a warning message.
This process of cancelling or modifying fares is obviously quite complex and can easily lead to errors; because of this it is recommended that you perform these functions with criteria sets or strikeover instead.
Related Topics