You are on page 1of 2

1.Record - 0 Rules are validated in this record, and Record 0 has other applications.

This record points to the GENERAL RULES that a carrier wants to apply in all circumstances. Carrier design a set of category-specific GENERAL RULES to be applied whenever there are no provisions listed in a category for one of their fares. Automatic processing applies the GENERAL RULES in the absence of data in a specific category. The data is included in the GENERAL RULES applies to all rules within that tariff unless stated otherwise within the fare rule 2.Record 1 This Record contains information regarding fare class, booking code, fare type, market, ticketing code and passenger type. This record makes it possible for the system to auto price the fare based on this information. Information coded in the fare class application (RECORD 1) must not conflict with the data coded in the appropriate categories. 3.Record 2 The containers for each of the sets of information are known as SEQUENCES. Each category has a sequence list screen (RECORD 2), which contains the identification fields and points to the data tables in RECORD 3. Sequences listed in this record follow a HIERARCHY (most specific to least specific) that determines the order in which rules provisions are read during auto pricing. 4.Record 3 The Category Data tables (RECORD 3) screen contains all the specific data regarding fare restrictions. The restrictions are sorted by categories. There are two screen formats. BRIEF (displays only the most commonly coded fields) and EXPANDED (displays all fields for that category). 5.Record 4 The electronic system uses this record to maintain the current data in RECORD 2 while the data is being updated. This record type indicates to the subscriber that a record to in the automated rules product is to be renumbered. The RECORD 4 shows the existing sequence number and the new sequence number for the specified Tariff, Carrier, Rules/Footnotes and Category. The intent of RECORD 4 is to expand the RECORD 2 file and not to change the relative placement or order 6.Record 5 The electronic system uses this record to maintain the current data in RECORD 1 while the data is being updated. RECORD 5 indicates to the subscriber that a RECORD 1 in the automated rules product is to be renumbered. The RECORD 5 shows the existing sequence number and the new sequence number for the specified Tariff, Carrier, Rule and Fare class. The intent of RECORD 5 is to expand RECORD 1 file and not to change the relative placement or order 7.Record 6 RECORD 6 is a source of booking code information. This record states any booking code exceptions to the prime booking code using chart 1 and chart 2. The RECORD 6 contains the identification criteria that must be matched to determine the proper booking code exceptions for that fare. 8.Record 7 RECORD 7 define as a city between the origin and fare component destination of the through International Fare Component that has a higher fare. (O) Origin - Intermediate - The HIP application applies from the origin of the fare component to any ticketed point(s) within the fare component being assessed. (D) Intermediate - Destination - The HIP application applies from a ticketed point to the fare component destination of the fare component being assessed. (I) Intermediate - Intermediate - The HIP application applies between any two ticketed points within the fare component being assessed.

9.Record 8 This record is used to identify the fares that may be used in the fare retrieval process for FARE BY RULE. Category 25 determines the provisions used in conjunction with restrictions coded in Category 25, RECORD 8 indicates the fares (Passenger Types) that can be used in the retrieval process for Fare by Rule. The record contains identification criteria that must be matched to determine the proper provisions to create the Fare By Rule. 10.Record 9 This record defines as a one-way fare that is qualified in its own terms independent of any other fare component. Combination of 2 or more fare components where one or more of the components is dependent upon all of the others to qualify for auto pricing. (Same as IATA term Pricing Unit.)