ATPCO Category 25 SABRE FILING INSTRUCTIONS MANUAL. Effective November 26, 2007 Version 1.11

Transcription

1 ATPCO Category 25 SABRE FILING INSTRUCTIONS MANUAL Effective November 26, 2007 Version 1.11

2 2003, Sabre Holdings. All rights reserved. This documentation is the confidential and proprietary intellectual property of Sabre Holdings. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Holdings is strictly prohibited. Sabre Holdings and the Sabre Travel Network logo design are trademarks and/or service marks of an affiliate of Sabre Holdings. All other trademarks, service marks, and trade names are owned by their respective companies.

3 TABLE OF CONTENTS SABRE FILING INSTRUCTIONS MANUAL CATEGORY 25 ATPCO CATEGORY GENERAL INFORMATION...1 PURPOSE...1 OVERVIEW OF SABRE HOLDING S CATEGORY 25 OFFERING...1 OPERATIONS DEPARTMENT...1 CONTACTS PRICING INSTRUCTIONS...2 INTRODUCTION...2 CATEGORY 25 TARIFFS...2 RECORD USE OF PASSENGER TYPE CODES...3 ACCOUNT CODE AND CORPORATE ID...4 CUSTOMER ACTION REQUIRED PRIOR TO IMPLEMENTATION...5 USER DEFINED ZONES...5 JOINT CARRIER TABLE TICKET DESIGNATOR PROCESSING...6 SAME CARRIER AND SAME CARRIER/FLIGHT TABLE RECORD RECORD PRIVATE FARES SECURITY...8 RULE OVERRIDE TAGS...9 TABLE CATEGORY 25 CREATION OF CATEGORY 35 FARES...10 ENHANCEMENT CATEGORY 25 PROCESSING OF CATEGORY 35 TICKETING INSTRUCTIONS...11 RESULTING FARE WILDCARD...15 NEW ROUTING DATA...15 DIRECTION FIELDS FARES DISPLAY INSTRUCTIONS SABRE TICKETING INSTRUCTIONS...20 TICKETING A COMBINATION OF FARES...20 SABRE HOLDINGS CORPORATE ID REQUEST FORM...21 PURPOSE...21 Customer Action Required Prior to Implementation:...21 CORPORATE ID REQUEST INSTRUCTIONS:...22 For Sabre subscribers:...22

4

5 1.0 General Information Purpose The purpose of this filing instructions manual is to provide assistance and guidance in filing ATPCO Category 25 automated rules data for processing in Sabre on the ATSE V2 platform. These instructions do not affect any current fares and rules data submitted via the Percent Off Fares Online product. Please disseminate this to all individuals within your organization that are responsible for filing this type of fare. If you need further information please contact your Sabre Representative. Overview of Sabre Holding s Category 25 Offering ATPCO automated Category 25 can be used to create public and private Fare By Rule fares for distribution, sales and ticketing in Sabre. While the basic concepts for creating public or private fares with Category 25 are the same, private Category 25 fares must have security information within the rules to ensure proper distribution and pricing. ATPCO Category 25 is a complex category and it is highly recommended that carriers study the ATPCO online guide to filing Category 25 data. The purpose of this document is to highlight areas of the product where filing errors are more common and areas that might need special consideration due to Sabre processing. Additionally, it highlights some of the differences between this and other automated category processing. Operations Department The Sabre Air Pricing Operations department does not have the ability to manually intervene in the Category 25 data sent to Sabre by ATPCO. If a problem exists and is found to be data related, the data must be re-filed via ATPCO. Contacts The Private Fares Team at Sabre Air Pricing Operations handles questions regarding how Sabre processes Category 25 private fares. Carriers and Sabre agencies filing with ATPCO that have questions not addressed by the information in this document should contact the ATPCO Negotiated Fares Help Desk or Sabre Air Pricing Operations. Confidential and Proprietary Sabre Inc. Page 1 of 13

6 2.0 Pricing Instructions Introduction This section contains information on how to correctly file Category 25 data and highlights areas of processing unique to Sabre. Category 25 Tariffs ATPCO has identified a specific set of tariff numbers to house public and private Category 25 rules. These are identified in the ATPCO Category 25 Filing Instructions Manual. The ATPCO User Manual states that passenger type ADT is a generic passenger type and should not be used in public Fare by Rule Tariffs. Record 8 Unlike other ATPCO automated rules categories, Category 25 (or Fare By Rule) has no associated fare records or Record 1. The entry point for processing Category 25 fares and rules is the Record 8. The Record 8 identifies where the discount is applicable and information that is required to qualify for the discount, such as an account code, ticket designator or status (residency, nationality, ship s registry and employment). Sabre matches the geographic points, passenger type and any other information included by the user in the fares display, pricing or ticketing request to all applicable Record 8s. Sabre does not process the following Record 8 fields: ID, AGE MIN/MAX, FIRST/LAST OCCURRENCE, Joint Carrier Table 997 Passenger Travel Origin (also inhibited by ATPCO) Additional notes regarding Sabre s processing of the Record 8: Recent ATPCO enhancements to the Record 8 for Same Carrier and Carrier/Flight Table 986 are supported according to industry standard. Passenger Status type Residency is supported to the Nation/State level. Recent development has expanded this to include residency processing to the city level as well. Please file this data with a CITY code, not an airport code. Confidential and Proprietary Sabre Inc. 2

7 Each matched Record 8 references one or more Record 2s (Category Control), which in turn, contain the Record 3 (Qualifying Instructions). The Category 25 Record 3 contains a specified fare amount or a calculation method that is applied to a published fare to create the Fare By Rule fare. Other Record 3 data identifies the associated fare rules, booking code, routing, etc. assigned to the resulting fare. This way, the rule dictates the fare instead of the fare being published with accompanying rules. Use of Passenger Type Codes Sabre s Category 25 product works with any ATPCO passenger type code. ATPCO does not allow the user of passenger type code ADT to create Public FBR fares. Private passenger type codes currently filed for use in Sabre that not ATPCO standard should be discussed with Sabre Air Pricing Operations. Sabre supports Record 8 Secondary Passenger Type code processing, used when the FBR fare is valid for further discounting by Category 19, 20, 21 or 22 rules data. For example, to create a FBR fare for an ADT passenger and allow a CNN discount, the Record 8 Primary Passenger Type code field will contain ADT and the Secondary Passenger Type code field will contain CNN. When a CNN type passenger is included in the fares display, pricing or ticketing request, Sabre will create the FBR fare applicable to the Primary Passenger type, then use the Secondary Passenger type code in that Record 8 to locate the applicable Category 19 data and apply the associated discount to the Fare By Rule fare. Consistent with ATPCO, all Category 19 (Child and Infant Discounts), 20 (Tour Conductor Discounts), 21 (Agent Discounts) or 22 (Other Discounts) data needed to create a discount for a Secondary Passenger must be filed in the Fare By Rule Tariff. Confidential and Proprietary Sabre Inc. 3

8 Account Code and Corporate ID The Qualifying Account Code in the Record 8 is a code consisting of 2-20 alphanumeric characters that identifies a specific contract. The Corporate ID is a Sabre proprietary 5 alphanumeric qualifier included in fares display and pricing entries. Ordinarily, the Account Code is assigned by the carrier to identify a specific contract between the carrier and agency or corporate customer. The Corporate ID is used by Sabre agencies to identify negotiated fares for a specific corporate customer. Sabre will support both Account Code and Corporate ID in processing Category 25. The carrier may enter either Account Code or Corporate ID in the Record 8 and it will be processed. Air Pricing Operations must register the Corporate ID in the Sabre database if the Corporate ID is used in the Record 8. Sabre will support an account code of 2-20 alpha-numerical characters. To allow the user to take advantage of the account code, Sabre has introduced a new fares display, pricing and ticketing qualifier to allow user input of the account code. This qualifier is AC* followed by the 2-20 character account code (for example, WPAC*19XB1000). Sabre will match this input account code to the data in the Qualifying Account Code field in the Record 8. Please note, if no Corporate ID has been assigned to the Category 25 fare by Sabre Air Pricing Operations, the fares will only be displayed and auto-priced using the AC (Account Code) identifier. For example: WPAC*ABC12 or FQMIANYC07DEC#AC*ABC12- YY where ABC12 represents the account code and YY refers to an airline code. The account code may also be filed in a Category 01 Record 3 in addition to or in lieu of the Record 8. The Corporate ID has a standard structure of 3 alpha characters followed by 2 numbers (for example, ABC01). A Corporate ID can be used for any valid ATPCO passenger type code. The Corporate ID can be used for locating and creating Category 25 fares. The user inputs the Corporate ID in their fares display; pricing or ticketing entry and this data is matched to data within the Record 8 Qualifying Account Code field. For example: WPIABC12 or FQMIANYC07DECCRP#IABC12-YY In some instances, there is a need to include both an Account Code and Corporate ID in the Category 25 data. This occurs when the carrier filing the Category 25 data needs an Account Code for their internal use and the ticketing agency needs the ability to use Sabre Corporate ID functionality. Since the carrier s Account Code is different from the Corporate ID, it is necessary to cross-reference the two codes as there is only a single field in the Record 8 to accommodate this data. The carrier should file the account code data in the Qualifying Account Code field of the Record 8 and notify Sabre Air Pricing Operations to cross-reference the two. A Corporate ID Request Form must be submitted to Sabre Air Pricing Operations to ensure correct matching of a Corporate ID to account code data in the Record 8. Please refer to the sample of the Corporate ID Request Form located at the end of this document. Confidential and Proprietary Sabre Inc. 4

9 Customer Action Required Prior to Implementation Customers who previously requested and are currently using specific Corporate IDs for fare quote and pricing through Sabre's Percent Off Fares Online product may continue to do so. However, if you intend to utilize these same Corporate IDs for the new automated Fare By Rule product, it is necessary to submit a Corporate ID Request Form(s) for all current Corporate IDs prior to implementation. Sabre has established a new Corporate ID database that will serve both the new Category 25 and the Sabre Percent Off Fares Online product. Any existing codes must be added to the new database if automated Category 25 is used. If a Corporate ID is associated with a specific carrier, tariff and rule where no account code is filed in the Record 8, the carrier, tariff and rule must be identified on the Corporate ID Request Form. If this information is unknown, the agency needs to contact the carrier filing the data for this information. After implementation, customers should continue to use the Corporate ID Request Form for any new Corporate ID requests or updates (i.e. Corporate ID use for another carrier and/or rule and/or tariff). User Defined Zones Like many other records, carrier can file specific ATPCO standard zone codes in lieu of actual geographic points. These zone codes are ATPCO standard for use by all carriers and GDSs and are listed in Appendix C of the Automated Rules Subscription Document. Category 25 Record 8 permits carriers to create non-standard ATPCO zones, or user-defined zones via table 978. Processing this table is supported on the V2 platform. Joint Carrier Table 997 Sabre will not support Joint Carrier Table 997 processing at this time. Confidential and Proprietary Sabre Inc. 5

10 Ticket Designator Processing Currently, Sabre supports using data in the Record 8 Qualifying Ticket Designator field to create Category 25 fares on the Legacy platform. When the user includes a ticket designator qualifier in their pricing/shopping/ticketing entry (WPQ/), it is processed in the Legacy platform and not on the new platform. Sabre validates the ticket designator from the entry against an in-house table containing ticket designators previously filed. If Sabre finds that ticket designator applicable to the carrier being priced, the discount driven by ticket designator is produced via a process outside ATPCO Category 25. If the ticket designator is not found in the in-house table, then Sabre attempts to locate Record 8s for that carrier and ticket designator and, if found, the ATPCO Category 25 process occurs. The current Sabre proprietary ticket designator functionality will not be supported on Sabre s new platform, but will continue to be supported in the Legacy system. On the new platform, Sabre will support Category 25 functionality consistent with ATPCO intent. Ticket designators meant to drive fare creation via Category 25 must be filed in the Record 8 Qualifying Ticket Designator field. Customers utilizing ticket designators to drive discounts must add their ticket designators to ATPCO data before the new platform is activated to ensure seamless functionality. Additionally, customers should note that the Record 8 Qualifying Ticket Designator drives the creation of discounts via Category 25 but does not place a ticket designator on the resulting fare. This is accomplished by filing data in the Category 25 Record 3 resulting ticket designator field. Same Carrier and Same Carrier/Flight Table 986 ATPCO enhanced the Record 8 to include these two new fields. The Same Carrier field allows the carrier to require that all travel on the journey where this fare component is present be via the services of the marketing carrier that owns that Record 8. If any sector of the journey being priced is not via the services of that marketing carrier, the Record 8 is not matched. The Carrier Table 986 field allows the carrier to require that all travel on the journey where this fare component is present be via the marketing and operating carriers specified in the table. Sabre supports these two new Record 8 fields consistent with ATPCO intent. Confidential and Proprietary Sabre Inc. 6

11 Record 2 The Record 2 for Category 25 differs from the ATPCO Record 2 for all other automated rules categories. The Record 8s that are matched to the itinerary and passenger type contain the information necessary to locate the applicable Record 2. It is not matched based on the fare class, fare type, routing or general rule information that is used for the other automated rules categories. While ATPCO will permit any category to be included as a qualifying category to Category 25, Sabre will support only the use of Categories 1 (Eligibility), 3 (Seasonality), 4 (Flight Application), 11 (Blackouts) and 15 (Sales Restrictions) as qualifying categories. If Categories 26 and 27 (Groups and Tours) are attached as a qualifying category, Sabre will ignore the Category 26 or 27 and process only the Category 25 data. Sabre will not process Joint Carrier Table 997. With the implementation of Category 25, Sabre will support User Defined Zones Table 978 in the Record 2 as well as the Record 8. This gives the filing carrier/agency the ability to define non-standard geographic zones tailored to their specific needs in lieu of the standard ATPCO zones. Confidential and Proprietary Sabre Inc. 7

12 Record 3 The Category 25 Record 3 includes data that creates the resulting fare amount, assigns the attributes, such as the resulting fare class/fare basis, fare type, the accepted booking codes, routing, and indicates where the resulting fare rules are located. Sabre processes all existing fare calculation methods and fare comparisons to ATPCO standards. Please note that the Record 3 Ticket Designator field is NOT match criteria, but assigns the resulting ticket designator. If the carrier wants a ticket designator used as match criteria used to correctly drive the discount, it should be filed in the Record 8. Sabre supports all of the recent ATPCO enhancements to the Category 25 Record 3. Sabre does not process the Record 3 fields listed below for pricing. Text describing any data in these fields is provided in the rules display. ID, AGE MIN/MAX, FIRST/LAST OCCURRENCE, Joint Carrier Table 997 Passenger Travel Origin (also inhibited by ATPCO) Due to unresolved account ARC/BSP reporting issues for negotiated fares, Sabre will NOT create a Category 25 fare whose DIS CAT value is T or C. Private Fares Security Either Category 35 or Category 15 rules data may be used to provide security information for the fares created via a specific Category 25 Record 3. If a Record 3 s DIS CAT value is L, then Sabre will only look to Category 35 for security information. The Category 35 data must be filed in the Fare By Rule Tariff. If the fares created from that Category 25 Record 3 data have BOTH Category 35 and Category 15 data present, Sabre will process only the Category 35 security data, ignoring any Category 15 security data. Category 15 rules data concerning conditions other than private fares security will be processed and applied to the resulting fare. If a Record 3 s DIS CAT value is not L, then Sabre will only look to Category 15 for security information. Sabre can apply the security data whether present on the base fare rule, the FBR rule, or both. Confidential and Proprietary Sabre Inc. 8

13 Rule Override Tags On the ATSE V2 platform, Sabre supports all of the Rule Override tags consistent with ATPCO intent, with the exception of Categories 26 (Groups) and Category 27 (Tours). Additionally, at this time, Sabre does not support Category 31 (Voluntary Changes) in conjunction with Category 25 processing. Table 989 Base Fare Creator Table 989 is an imbedded table within the Category 25 Record 3. It is used to retrieve the base fares that will be discounted by the Category 25 Fare Calculation data to produce FBR fares. Base fare amounts can also used for fare comparison purposes (for example, in the market AAA-BBB, retrieve carrier XX s Normal Economy Class fares between and ). Sabre will support the processing of Base Fare Creator Table 989 consistent with ATPCO intent with the following exceptions: Sabre will not support using fares with a Record 1 DIS CAT value of T or C (Category 35 Net fares) as a base fare candidate. Sabre will not support the use of BTW CTY and AND CTY fields to create a FBR fare using base fares for a market other than the one used in the Record 8 match. Sabre will support ATPCO changes to table 989 base fare booking code field when ATPCO implements this change in early This change will allow the carrier to populated the table 989 BK CD 1 or BK CD 2 field with a booking code followed by the special character asterisk (*). With data filed in this manner, Sabre will retrieve base fares with that booking code requirement and apply the CAT 25 discount and any new booking code requirement. Additionally, Sabre will check availability on each flight within the CAT 25 fare component being created. If the booking code from the base fare is available for sale on all flights within fare component, the CAT 25 fare will be created. If the booking code from the base fare is NOT available on all flights within the fare component, the CAT 25 fare will NOT be created. Confidential and Proprietary Sabre Inc. 9

14 For example: CAT 25 R3 data: Calculation is 100 percent of base fare minus USD Resulting fare class is QFBR. Resulting booking code is Q. Base fare table BK CD 1 field data is Y*. Pricing request: Sabre pricing fare component for passenger confirmed in Q inventory. Action: Sabre processes the base fare table and retrieves all fares for the applicable carrier, tariff, rule that have a booking code requirement of Y The CAT 25 R3 indicates that the resulting booking code is Q. The passenger is booked in Q, so the discount is applied. Check availability on all flights within the fare component being created. Y inventory must be available. If Y inventory is available on all flights within the fare component, the CAT 25 fare is created. IF Y inventory is NOT available on all flights within the fare component, the CAT 25 fare is NOT created. Category 25 Creation of Category 35 Fares ATPCO Category 25 can be used to create fares with a resulting DIS CAT value of L, T or C. Fares with these values are: L A selling fare with Category 35 security that defines who can view, sell, price and ticket the fare. Category 35 ticketing instructions may also be present. T A NET fare with Category 35 security that defines who can view, sell, price and ticket the fare. Category 35 Table 979 (Fare Creation) data is present and used to instruct Sabre how to alter the NET fare to create a selling fare. Category 35 ticketing instructions may also be present. C A NET fare with Category 35 security that defines who can view, sell, price and ticket the fare. Category 35 Table 979 (Fare Creation) data is present and is used to instruct a Travel Agency or Airline user the guidelines that they must be used to update the fare to a selling fare amount. At this time, Sabre will support only the resulting value L. This is because unresolved accounting and debit audit trail issues exist that the industry has not yet resolved. Until those issues are addressed, Sabre will not create Category 25 fares with a resulting DIS CAT value of T or C. Confidential and Proprietary Sabre Inc. 10

15 Enhancement Category 25 Processing of Category 35 Ticketing Instructions In December 2005, Sabre enabled their ATPCO Category 25 offering to work in conjunction with their ATPCO Category 35. This means that Sabre now allows Category 35 fares to have more flexibility in the automated ticketing package by allowing a stand-alone tour code or a stand-alone ticket designator and not force IT/ BT ticketing. This also means that Sabre now allows Category 25 fares using Category 35 for security to take advantage of the stand-alone tour code or stand-alone ticket designator and auto-ticketing these filings. Overview of this Enhancement: This new ticket package applies to fares filed as: Record 1 Display Category type L for Category 35 fares that have no associated Fare Creator (979) table The resulting Category 25 fare is Display Category type L with no 979 The resulting Category 25 Display Category is Blank and the base fare Record 1 Display Category is type L Additionally these enhancements will: Not apply to Percent Off Fares Online fares as this data does not use Category 35 processing Applies to both Sabre Air Pricing and the pricing component of the Sabre Air Suite Produce additional text in the rule display (RD paragraph 28) Not affect any automated ticketing already in place for Category 35 fares Continue to pass baggage information filed in the Category 35 rules Continue to process commission filed in the Category 35 rules Details regarding the Ticket Designator capabilities: Ticket Designator information contained in Category 35 / Category 25 is for ticketing purposes only and is not used to drive the fare. Agent input of a ticket designator indicates that a fare obtained by the current ticket designator processing is desired. If a user specifies a ticket designator in the pricing or ticketing entry, bypass all fares using category 35/ category 25. Confidential and Proprietary Sabre Inc. 11

16 Details regarding the Commission capabilities: If the agent inputs a commission value in the ticketing entry and no commission data is filed on the category 35 the manual input data will be used and no trailer will follow. If the agent inputs a commission value in the ticketing entry, and the category 35 commission fields contain data then ignore the manual input and apply the category 35 commission, but supply a trailer message: UNABLE TO OVERRIDE NEGOTIATED DATA FOR COMMISSION. Details regarding the Tour Code capabilities: When ticketing (W entries) a fare created by Category 25 data and Category 35 ticketing instruction data is present on the fare, Pricing will pass any Tour Code/Value Code/CAR Code to ticketing as instructed by the Category 35 ticketing instructions data. If the agent inputs a tour code manually (UI* or UB* or U*) in the ticketing entry, this will bypass Category 35 processing. If Filed Input Then IT1234 W#U (tour code) Use Category 35 tour code data (on Category 25 or Category 35 fare) IT1234 W#UI* (inclusive tour) Bypass Category 35 / Category 25 data and print other fare - ERROR BT1234 W#UB* (bulk inclusive tour) Bypass Category 35 / Category 25 data and print other fare - ERROR 1234 W#UN* (suppress IT from printing in the tour code box) Use Category 35 tour code data (on Category 25 or Category 35 fare) Blank W#U (tour code) Pricing will pass the fare. Ticketing will allow the fare to print with the manual tour code for both Category 25 and Category 35 fares. Blank W#UI* (inclusive tour) Bypass Category 35 / Category 25 data and print other fare - ERROR Blank W#UB* (bulk inclusive tour) Bypass Category 35 / Category 25 data and print other fare - ERROR Blank W#UN* (suppress IT from printing in the tour code box) Pricing will pass the fare. Ticketing will allow the fare to print with the manual tour code for both Category 25 and Category 35 fares. Confidential and Proprietary Sabre Inc. 12

17 Details regarding the Baggage capabilities: If the agent inputs the same baggage allowance as in the Category 35 fields, the ticket will issue using the Category 35 data and no trailer message will follow. If the Category 35 shows blank baggage and the agent inputs baggage allowance in the ticketing entry, the ticket will be issued using the agent input. No trailer will follow. If the Category 35 baggage allowance fields are blank and the agent does not input any baggage allowance in the ticketing entry, current processing applies: If Filed Input Then 02P W#BA*22K Category 35 overrides with trailer and PC will Print from Category 35 02P W#BA*02P No trailer will follow and PC prints on the ticket ( ) blank W#BA*02P Agent input is accepted and PC will print on the ticket 02P W# Category 35 is accepted and PC will print on the ticket () blank W# Need Baggage (for BSP and if the indicator is on in the TJR) If the agent inputs a different baggage allowance than is shown in the Category 35 record, the ticket will issue using the Category 35 data, however a trailer should follow: CARRIER FILED BAGGAGE ALLOWANCE APPLIES Confidential and Proprietary Sabre Inc. 13

18 Fare Filing Instructions: Category 35 with net fares (Category 25 does not create Category 35 NET fares) Record Fare Creator Tour code Text Method Type Ticket Designator Commission Baggage Ticket Result T/C Yes Yes IT/BT Blank Optional Optional Optional IT/BT T/C Yes Yes IT/BT Not blank Optional Optional Optional Fail IT/BT T/C Yes No IT/BT Blank Optional Optional Optional Fail IT/BT T/C Yes Yes Not IT/BT T/C Yes No Not IT/BT Blank Optional Optional Optional Fail IT/BT Blank Optional Optional Optional Fail IT/BT Category 35 with net fares (Category 25 does not process Category 35 with net fares) Record Fare Creator Tour Code Text Method Type Ticket Designator Commission Baggage Ticket Result L Yes Yes IT/BT Blank Optional Optional Optional IT/BT L Yes Yes IT/BT Not blank Optional Optional Optional Fail IT/BT L Yes No IT/BT Blank Optional Optional Optional Tkt without Cat35 data L Yes Yes Not IT/BT L Yes No Not IT/BT Category 35 with or without Category 25 (selling fares only) Record Fare Creator Tour Code Text Blank Optional Optional Optional Fail IT/BT Blank Optional Optional Optional Tkt without Cat35 data Method Type Ticket Designator Commission Baggage Ticket Result L No Yes IT/BT Blank Optional Optional Optional IT/BT L No Yes IT/BT Not blank Optional Optional Optional Fail IT/BT L No No IT/BT Blank Optional Optional Optional Fail IT/BT L No Yes Not IT/BT L No No Not IT/BT L No No Not IT/BT n/a Optional Optional Optional Tkt with Cat35 data n/a Optional Optional Optional Tkt with Cat35 data n/a Blank Blank Blank Tkt without Cat35 data Confidential and Proprietary Sabre Inc. 14

19 Resulting Fare Wildcard Sabre supports the use of both the special characters asterisk (*) and hyphen (-) to create new resulting fare class (fare basis) codes. Users may code this wildcard as long as the F/IND in the Record 3 Cat 25 is not coded as S, K E or F. When the asterisk (*) character is present in the resulting fare class code field, the resulting Category 25 fare class will consist of the first letter of the base fare followed by any data that follows the asterisk in the Resulting Fare Class field. For example, if the fare class of the base fare was YAP6M and the Category 25 Record 3 Resulting Fare Class field contained the data *DISC, the resulting fare class would be YDISC. When the hyphen (-) character is present in the first position of the resulting fare class code field, then the base fare is appended with any data following the character. For example, if the fare class of the base fare was YAP6M and the Category 25 Record 3 Resulting Fare Class field contained the data -DISC, the resulting fare class would be YFBR40DISC. When the hyphen (-) character is present in the last position of the resulting fare class code field, then the first character of the base fare is replaced by everything that precedes the in the resulting fare class field. For example, if the fare class of the base fare was YAP6M and the Category 25 Resulting Fare Class field contained the data B-, then the resulting fare class would be BAP6M. There is no limit to the number of fare basis codes that can be created with a single wildcard transaction. New Routing Data Sabre supports ATPCO routing defaults in the Resulting Fare fields of the Record 3 Cat 25 related to routings. A carrier may decide not to specify a single routing applicable to the FBR fare, intending that any one of their published routings is applied. To facilitate this, ATPCO allows the filing carrier to specify this option in the Category 25 resulting routing fields. The RTG TAR field in this case will be either blank or 000. The RTG NO field will either be (any specified routing on MPM) or (any specified routing). Note: If the Resulting Fare is applicable to travel within any single country or between points in the US and Canada, the value is not allowed in the RTG NO field. Confidential and Proprietary Sabre Inc. 15

20 Applicable to Pricing/Shopping Functionality When the value is present, Sabre will apply any specified routing to the Category 25 fare. If no specified routings for that carrier are applicable to the route of travel, an MPM fare (with correct Global Direction) will be used. Any extra mileage allowance, mileage reduction, mileage surcharge, etc. will be applied where applicable. When the value is present, Sabre will apply any specified routing to the Category 25 fare. Applicable to Fares Display Functionality When the value is present, Sabre will create a single FBR fare with a unique routing number; a description line for that routing number is shown at the bottom of the fares display: ANY VALID ROUTING OR MPM APPLIES When value is present, Sabre will create a single FBR fare with a unique routing number; a description line for that routing number is shown at the bottom of the fares display: ANY VALID ROUTING EXCEPT MPM APPLIES Direction Fields Direction field exists in both the Record 8 and the Record 2. The suggested method of filing uses both the Record 8 and the Record 2. If the fare component matches on the Record 8, it will then attempt to match the direction in the Record 2. Terminology The distinction between Travel Direction and Fare Direction is important. Travel Direction refers to the actual direction the passenger is flying, regardless of how the fares are selected for pricing. Fare Direction is a fare construction principle that determines the order of the cities for fare displays and for pricing. It could also be referred to as fare selection direction. Sample Itinerary: LON-HKG-LON Flight Inbound/Outbound Travel Direction Fare Direction Fare Display LON-HKG Outbound LONHKG LONHKG FQLONHKG HKG-LON Inbound HKGLON LONHKG FQLONHKG Record 8 The Record 8 contains a directional field that can be coded one of three ways: From Loc 1, To Loc 1 or blank. From Loc 1 and To Loc 1 refer to fare direction of the component being to be created. When a Record 8 match is made, Sabre will create Cat 25 fares only in the fare direction specified, then proceed to the Record 2 for more specific direction information. Depending on what system is used to code fares, either an X will be placed next to the directional selection, or a letter (F or T) is input whose value equals one of the choices. Confidential and Proprietary Sabre Inc. 16

21 DIRECTIONAL TRAVEL FROM LOC 1: TO LOC 1: F = Directional Travel From Loc 1 T = Directional Travel To Loc 1 Itinerary: LON-HKG-HKG Loc 1: LON Loc 2: HKG LON-HKG flight HKG-LON flight Coded From Loc 1 LON-HKG (match) HKG-LON (match) Coded To Loc 1 LON-HKG (no match) HKG-LON (no match) When coded as From Loc 1, both flights are a match because the fare direction for both flights is LONHKG. When coded as To Loc 1, there is no match on either flight To Loc 1 could only match if the fare direction was HKGLON. If left blank When the Record 8 direction field is left blank, this provides a match on all fare components. Fares in each direction will pass to the Record 2. Record 2 If a Record 8 match is made, Sabre will then interrogate the direction fields in the Record 2. If a match is made in the Record 2, the Record 3 Category 25 data will be applied to the fare component. It is possible for a component to match on the Record 8, then fail the Record 2. Depending on what system is used to code fares, either an X will be placed next to the directional selection, or a number (1, 2, 3 or 4) is input whose value equals one of the choices. DIRECTIONAL TRAVEL FROM LOC 1: LOC 2: ORIGIN LOC 1: ORIGIN LOC 2: 1 = Travel From Loc 1 to Loc 2 2 = Travel From Loc 2 to Loc 1 3 = Fares Originating Loc 1 4 = Fares Originating Loc 2 Confidential and Proprietary Sabre Inc. 17

22 Directional Travel (Values 1 and 2) These options are based on the direction of travel of the fare component. They disregard the fare direction, or where the itinerary originates. Assume a Record 8 match has been made for this example. Itinerary: MIA-MEM-MIA Loc 1: MIA Loc 2: MEM If Coded As MIA-MEM flight MEM-MIA flight Value 1 Travel From Loc 1 MIA-MEM (match) MEM-MIA (no match) Value 2 Travel From Loc 2 MIA-MEM (no match) MEM-MIA (match) Note: In the above example, a match means a Category 25 fare would display and price for that fare component. International Application Although this coding usually exists for the purpose of domestic travel, it can be used to create an international directional fare. For example, to code a fare valid only from MNL to LAX, disregarding how the fare is selected, the coding would use either Value 1 or Value 2. Itinerary: MNL-LAX-MNL Loc 1: MNL Loc 2: LAX If Coded As MNL-LAX flight LAX-MNL flight Value 1 Travel From Loc 1 MNL-LAX (match) LAX-MNL (no match) Value 2 Travel From Loc 2 MNL-LAX (no match) LAX-MNL (match) Note: In the above example, a match means a Category 25 fare would display and price for that fare component. Origin Loc 1 or 2 (Values 3 and 4) Like the directional options in the Record 8, these two options refer to fare direction. When coded as Origin Loc 1, the Cat 25 fare is eligible for components whose fare direction is from Loc 1 to Loc 2. Assume a Record 8 match has been made for this example. Itinerary: PAR-RIO-PAR Loc 1: PAR Loc 2: RIO If Coded As PAR-RIO flight RIO-PAR flight Value 3 Origin Loc 1 PAR-RIO (match) RIO-PAR (match) Value 4 Origin Loc 2 PAR-RIO (no match) RIO-PAR (no match) Note: In the above example, a match means a Category 25 fare would price for that fare component. When coded as Value 3 (Origin Loc 1) both flights are a match because the fare direction for both flights is PARRIO. When coded as Value 4 (Origin Loc 2), there is no match on either flight value 4 could only match if the fare direction was RIOPAR. Confidential and Proprietary Sabre Inc. 18

23 If left blank When the Record 2 direction field is left blank, this provides a match on all fare components that passed the Record 8 validation. This table lists the possibilities when either the Record 8 or the Record 2 is left blank. Assume data coded in either Record is a match. Record 8 Record 2 Direction Result blank blank Cat 25 fares valid both directions blank Data coded Cat 25 fares valid based on Record 2 direction coding Data coded blank Cat 25 fares valid based on Record 8 direction coding Data coded Data coded Cat 25 fares valid based on Record 8 and Record 2 direction coding. Components not matching on Record 8 will not interrogate the Record Fares Display Instructions Included in the recent changes to Sabre fares display functionality is a revision to the fare types included in the standard, or default fares display request (e.g. FQFRANYC01OCT-XX). In order for a CAT 25 fare to be included in the standard fares display request, the resulting fare type must be one of those listed below: BND BOX BPR BR BRO BRW BU BX EAP EBN EIP END EPR ER ERS ERT ERW ES ET EU FND FOX FPR FR FRO FRW FS FU FX PRO SAP SB SBP SIP XAB XAC XAN XAP XAT XAW XBB XBN XEF XEL XES XEV XEX XND XOX XPB XPC XPF XPL XPN XPO XPS XPV XPX XPY If the fare type assigned to the base fare used to create the Category 25 fare is not listed above and the carrier desires that the resulting fare be included in the default fares display, the Resulting Fare Type field in the Category 25 Record 3 must be populated with one the fare types listed. Confidential and Proprietary Sabre Inc. 19

24 4.0 Sabre Ticketing Instructions Ticketing a Combination of fares ATPCO Combinability Category cannot override industry ticketing procedures. Fares filed with different ticketing instructions will not be combined on the same ticket. In first Quarter 2006 ATPCO provided a new tag on the 107 combinations table that allows combination of fares down to the private/ public tariff level. With that tag and the cat 15 segment tag (byte 31) that allows the carriers to force separate tickets to be issued Sabre has lifted many of the combination restrictions it once adhered to. The following combinations apply when the FBR fare was filed using Category 35 as the security table and as the instrument for providing ticketing instructions. Combination of Different Carriers If the fare combination results in different carriers and all fares have no ticketing information (no tour code, commission or is not IT/ BT) then Sabre will allow the fares to price and be issued on a single ticket. If the fare combination results in different carriers and any 1 fare has a tour code, commission or is IT or BT type then Sabre will allow the combination to pass in pricing but will return a pricing trailer message ISSUE SEPARATE TICKETS. If the user performs a W# entry they will receive the same message ISSUE SEPARATE TICKETS. Combination of Same Carrier When combinations are within the same carrier (alliance is not considered the same in this situation) we will not consider a blank tour code field as being in conflict and allow it to pass validation. If all fares in combination are the same tour code (or any blanks) and within the same carrier this would be considered valid. The Blank can be coming from any type of fare (Cat 15, 35, 25, or public). o o Pricing would pass to ticketing the tour code to be printed on the ticket. If the combination results in multiple (different) tour codes, then separate tickets would still be required. Confidential and Proprietary Sabre Inc. 20

25 Sabre Holdings Corporate ID Request Form Purpose The purpose of this document is to provide assistance in obtaining a Corporate ID used to control pricing. The instructions in this document apply only to ATPCO Category 25 automated rules data for processing in Sabre. These instructions do not affect any current fares and rules data submitted via the Percent Off Fares Online product. Customer Action Required Prior to Implementation: Customers who previously requested and are currently using specific Corporate IDs for fare quote and pricing through Sabre's Percent Off Fares Online product can continue to do so. However, if you intend to utilize these same Corporate IDs for the new automated Fare By Rule product it is necessary to submit Corporate ID Request Form(s) for all current Corporate IDs prior to implementation. *Corporation Name: *Desired Corporate ID:?Account Code:?Applicable Rule Tariff:?Rule Number: *Carrier Code: *Pseudo City Code (Sabre subscribers): *Name of Submitter: *Submitter s Company Name: *Submitter s Phone Number: *Submitter s Address: Additional Information: * Denotes mandatory fields.?account Code or Applicable Rule Tariff / Rule Number fields must be filled in. Confidential and Proprietary Sabre Inc. 21

26 Corporate ID Request Instructions: List the name of the corporation for whom the corporate ID applies. List the desired Corporate ID. Corporate IDs must consist of 3 alpha characters followed by 2 numeric characters (i.e. XYZ Corporation = XYZ01). If the desired Corporate ID is not available Sabre Air Pricing Operations will assign a Corporate ID similar to the one requested. Please be sure to assign a Corporate ID that closely matches the corporation name for whom it is being submitted. If you do not want to suggest a Corporate ID and wish for Sabre to assign one for you please give instructions in the Additional Information field. List the Account Code. This information must be included if the filing carrier has filed one in the ATPCO Category 25 rules data. The Account Code consists of a combination of 2-10 alpha and numeric characters. Please note that only one Corporate ID can be assigned to any Account Code. However, multiple Account Codes can be assigned to a single Corporate ID. If multiple Account Codes will apply to the Corporate ID being requested, please list them all. If unknown, please contact the carrier. At the present time, Sabre is only accepting Corporate ID with a maximum of 5 characters with 3 alpha and two numeric characters. Identify the applicable rule tariffs where the ATPCO Category 25 data has been filed (i.e. public carrier tariff FBRNA or private carrier tariff FBRNAPV). This information must be included if the carrier has not filed an account code. If unknown, please contact the carrier. Identify the rule number(s) associated with the Category 25 data filed by the carrier. This information must be included if the carrier has not filed an account code. If unknown, please contact the carrier. Identify the carrier code for which the filing applies. This information is mandatory or the Corporate ID request cannot be processed. For Sabre subscribers: Identify the home Pseudo City Code (PCC) where this data will apply. The Additional Information field should be used to provide additional provisions or clarifications applicable to the Corporate ID request. The Submitter should fill in this form as an initial request when pricing and fare display is desired for the above-mentioned corporation. Sabre Air Pricing Operations cannot release negotiated fares in Sabre for said Corporate ID until the initial Corporate ID request form is processed and on file. The timeframe for processing Corporate ID requests and updating Sabre with the information is two business days after the request form has been received by Sabre Air Pricing Operations at the address of: apocorpid@sabre.com. Confidential and Proprietary Sabre Inc. Page 22 of 13