INTERNATIONAL FARE RECORD

Transcription

1 DATA APPLICATION INTERNATIONAL FARE RECORD The information contained in this document is the property of ATPCO. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical, photocopying, recording, or otherwise, without the prior written permission of ATPCO. Under the law, copying includes translating into another language or format. Legal action will be taken against any infringement Copyright 2005 by Airline Tariff Publishing Company All rights reserved.

2 Contents 1.0 OVERVIEW DATA REQUIREMENTS BASIC PROCESSING OVERVIEW DEFINITIONS AND ASSUMPTIONS DEFINITIONS ASSUMPTIONS DETAILED FIELD PROCESSING PROCESSING PUBLISHED FARE DATA (BYTES 1-125) Tariff Number (bytes 1-3) Carrier Code (bytes 4-6) Origin/Destination City and Country (bytes 7-11, 12-13, 14-18, 19-20) Fare Class Code (bytes 21-18) Discontinue Date (bytes 35-40) Rule Number (bytes 41-44) Routing Number (bytes 45-48) OW/RT (byte 49) Source (bytes 50-53) Origin/Destination Fare Amount (bytes 54-83) Fare Amount (bytes 54-64, 69-79) Currency Code (65-67, 80-82) Number of Decimals (68, 83) Footnote (bytes ) Directional Indicator (byte 111) Global Indicator (bytes ) Tariff Effective Date (bytes ) MPM (bytes ) CONSTRUCTED FARES DATA (BYTES ) Origin Add-on Information (bytes ) Destination Add-on Information (bytes ) Published Fare Information (bytes ) Sale Dates (bytes ) DATABASE MAINTENANCE (BYTES ) (byte 228) International Fares Page E-02

3 4.3.2 MCN (bytes ) Old MCN (bytes ) Link Number (bytes ) and Sequence Number (bytes ) Change Tag (bytes ) GFS Filing Advice (bytes ) Examples NOT USED CODING CONVENTIONS International Fares Page E-03

4 1.0 OVERVIEW This document describes the application of the International Passenger Fare Record within an itinerary pricing environment. When pricing an itinerary, it is assumed individual pricing systems will determine the scope of the pricing solutions they will attempt to price. Once systems determine the possible pricing solutions, they will attempt to process the individual fare components against the applicable fares and applicable rules/footnotes/routings records. The purpose of this document is to address the pricing of a passenger s itinerary based on the data fields within the International Fare Record. The record is separated into two subscription products: Fares to/from North America. This includes: o International fares between the United States and any point outside the United States or Canada o International fares between Canada and any point outside the United States or Canada All Fares. This includes: o International fares between any country excluding the United States or Canada o Domestic fares within any country excluding the United States or Canada. NOTE: Although the title of this record is International Fares, the subscription record does include domestic fares (sometimes referred to as All Fares Domestic ), provided such domestic fares are not within or between the US and CA. Processing will first determine the fare record availability for pricing. Processing will continue by matching the fare component to the fare record. When the origin and destination points on a fare component on the candidate pricing solution are within the geographic application specified above, processing will select the appropriate International fares per this document. If the origin and/or destination points of a fare component are not within the geographic application specified above (i.e. if the origin and/or destination points are within or between the US and CA), process the US/CA Passenger Fare Record. (Refer to Data Application for the US/CA Passenger Fare Record for further information those fares.) This document describes the match process and the application of the International Fare Fecord for itinerary pricing. When a match is made to an International Fare Record, processing will validate the fare record and all supporting data which governs the fare, including the Fare Class (Record 1), Fare Rule (Category Record 2s/3s), General Rule (Category Record 2s/3s), Footnote/s (Category Record 2s/3s) and Routing. This document will not address processing this record for Constructed Fares, Automated Rules/Footnote Records, or Routings. Refer to Data Application documentation for those records and categories for more information. International Fares Page E-04

5 1.1 Data Requirements In order to validate the fare record available for pricing, it is essential to know the following The sale/ticketing date of the itinerary being priced. Date of departure from the origin of the journey. In order to validate the fare record against an itinerary, it is essential to know the following: The sale/ticketing date of the itinerary being priced. Date of departure from the origin of the journey. The marketing carrier on each sector of the fare component (in order to identify the primary carrier). The origin and destination point of the fare component being priced. The pricing solution in which the fare component is being priced (in order to identify the direction of fare selection) International Fares Page E-05

6 1.2 Basic Processing Overview Pricing Solution Request (Subscriber has determined candidate fare break points) Are the fare break points in one of the following geographic markets? International to/from US/CA (excluding transborder US-CA) International excluding to/from US/CA Yes No Identify the Primary Carrier(s) of the fare component being priced. Does the Primary Carrier(s) have a fare record for the fare break points of the fare being priced? Yes Validate the carrier s fare record No No carrier-specific International Fare Record applies Are the fare break points in the following geographic market? Domestic excluding within/between US/CA Yes Identify the Primary Carrier(s) of the fare component being priced. Does the Primary Carrier(s) have a fare record for the fare break points of the fare being priced? No Does internal system data indicate YY fares should be processed? Yes No Yes Validate the carrier s fare record No No International Fare Record applies Is there a YY fare record for the fare break points of the fare being priced? Yes No Validate the YY fare record No YY International Fare Record applies International Fares Page E-06

7 2.0 DEFINITIONS AND ASSUMPTIONS 2.1 Definitions Term Market Domestic Fare International Fare Owning Carrier Primary Carrier Definition As used within this document, market applies to two fare break points for which the fare is assessed (Bytes 7-11 and 14-18). Fares in the International Fare Record where the fare break points are in the same country code. Exception: Fares between country codes XU and RU are domestic. Fares in the International Fare Record where the fare break points are in different country codes. Exception: Fares between country codes XU and RU are not international. The Carrier Code specified in bytes 4-6 on the International Fare Record. (Also referred to as Publishing Carrier) The marketing carrier on the primary portion of travel for the fare component being priced. For carrier fares (non-yy fares), this is the carrier whose fare will be assessed for the fare component being priced. For international fares, determination of the primary portion of travel and the primary carrier is based on guidelines set forth in IATA Resolutions. (Also referred to as Significant Carrier.) For domestic fares, the primary carrier can be any marketing carrier on the fare component. Refer to the Glossary of Terms for a definition of any other applicable term. 2.2 Assumptions A fare record is available for sale/ticketing as soon as it is released by ATPCO unless otherwise restricted by any footnote, fare rule, and/or general rule data that resolves to the fare. Fares created in Fare By Rule (Category 25) are governed by conditions in Data Application for Category 25. In the absence of a fare record resolving to match criteria, no International fare applies to the carrier and market being validated. International Fares Page E-07

8 3.0 DETAILED FIELD PROCESSING Byte Location Match / Bytes 1-3 Key Match TARIFF NO. Bytes 4-6 Key Match CXR CODE Bytes 7-11 Key Match ORIGIN CITY Bytes Key Match ORIGIN CTRY Bytes Key Match DEST CITY Bytes Key Match DEST CTRY Bytes Key Match/ FARE CLASS CODE Bytes Match EFF DATE Bytes DATES DISC Bytes RULE NO Bytes RTG NO Byte 49 OW/RT Match Definition / Processing Indicates the Tariff number used to identify a specific group of fares based on coding criteria such as geographic areas, fare type, public vs. private tariff type, etc. Specifies the owning/publishing carrier of the fare. Indicates the standard industry alpha city/airport code that matches to a terminal point in the fare break. Identifies the country for the origin city (bytes 7-11) for the fare record. Indicates the standard industry alpha city/airport code that matches to a terminal point in the fare break. Identifies the country for the destination city (bytes 14-18) for the fare record. Indicates the alphanumeric fare class code applicable to the fare. This field will always contain zeros as ATPCO will not provide any data in this field refer to TAR EFF DATE (bytes ) for the effective date of the fare. Processing assumes an automatic match to this field. Indicates the last date on which the fare may be sold and ticketed and the last date which travel may commence from the origin of the journey encompassing the fare being validated unless further restricted by footnote/rule provisions. Indicates the fare rule applicable to the fare record. Indicates the routing number applicable to the fare record. Indicates whether a fare value is published as a one way amount or round trip amount. International Fares Page E-08

9 Byte Location Match / Bytes SOURCE Bytes ORIGIN FARE AMOUNT Bytes ORIGIN CUR CD Byte 68 ORIGIN # DEC Bytes DESTINATION FARE AMOUNT Bytes DESTINATION CUR CD Byte 83 DESTINATION # DEC Bytes OTHER FARE AMOUNT Bytes AIRPORTS Byte FOOTNOTE Byte 111 DI Bytes GLOBAL Definition / Processing Identifies the fare data supplier. Always ATP. Indicates the fare amount applicable from the Origin City (bytes 7-11) to the Destination City (bytes 14-18). [Applicable when the DI field (byte 111) contains value F.] Indicates the currency code applicable to the Origin Fare Amount (bytes 54-64). Indicates the number of decimal places applicable to the Origin Fare Amount (bytes 54-64). Indicates the fare amount applicable to the Origin City (bytes 7-11) from the Destination City (bytes 14-18). [Applicable when the DI field (byte 111) contains value T.] Indicates the currency code applicable to the Destination Fare Amount (bytes 69-79). Indicates the number of decimal places applicable to the Destination Fare Amount (bytes 69-79). N/A Not currently used. Processing ignores these fields. N/A Not currently used. Processing ignores these fields. Indicates the footnote(s) applicable to the fare record. Match Specifies the directional application of the fare relative to the Origin City (bytes 7-11) and Destination City (bytes 14-18). This value will be F from Origin City for International and AllFares. Match Specifies the global indicator (global routing) applicable to the fare record. International Fares Page E-09

10 Byte Location Match / Bytes Match TAR EFF DATE Definition / Processing Indicates the earliest date on which travel may commence from the origin of the journey encompassing the fare being validated unless further restricted by footnote/rule provisions. Indicates the Maximum Permitted Mileage (MPM) associated to travel between the Origin (bytes 7-11) and Destination (bytes 14-18) cities. Not currently used. Processing ignores this field. Bytes MPM Byte 125 CAB The data in bytes are only applicable for constructed fares. This data is not applicable for published fares and is ignored when processing published fares. BYTES Indicates the fare class code applicable to the Origin Add-on. ORIGIN ADD ON FARE CLASS CODE BYTES ORIGIN ADD ON ROUTING BYTES ORIGIN ADD ON FOOTNOTE BYTES ORIGIN ADD ON GATEWAY BYTES ORIGIN ADD ON AMOUNT BYTE 157 ORIGIN ADD ON SIGN Indicates the routing number applicable to the Origin Add-on. Indicates the footnote(s) applicable to the Origin Add-on. Indicates the gateway city applicable to the Origin Add-on. Indicates the fare amount applicable to the Origin Add-on Indicates whether the Origin Add-on Amount is a positive or negative amount. International Fares Page E-010

11 Byte Location Match / BYTES ORIGIN ADD ON CUR BYTE 161 ORIGIN ADD ON # DEC BYTES DESTINATION ADD ON FARE CLASS CODE BYTES DESTINATION ADD ON ROUTING BYTES DESTINATION ADD ON FOOTNOTE BYTES DESTINATION ADD ON GATEWAY BYTES DESTINATION ADD ON AMOUNT BYTE 193 DESTINATION ADD ON SIGN BYTES DESTINATION ADD ON CUR Definition / Processing Indicates the currency code applicable to the Origin Add-on Amount (bytes ). Indicates the number of decimal places applicable to the Origin Add-on Amount (bytes ). Indicates the fare class code applicable to the Destination Add-on. Indicates the routing number applicable to the Destination Add-on. Indicates the footnote(s) applicable to the Destination Add-on. Indicates the gateway city applicable to the Destination Add-on. Indicates the fare amount applicable to the Destination Add-on Indicates whether the Destination Add-on Amount is a positive or negative amount. Indicates the currency code applicable to the Destination Add-on Amount (bytes ). International Fares Page E-011

12 Byte Location Match / BYTE 197 DESTINATION ADD ON # DEC Bytes PUB FARE INFO FOOTNOTE Bytes PUB FARE INFO FARE AMOUNT Bytes PUB FARE INFO CUR Byte 215 PUB FARE INFO # DEC Definition / Processing Indicates the number of decimal places applicable to the Destination Add-on Amount (bytes ). Indicates the footnote(s) applicable to the published fare used in construction. Indicates the fare amount applicable to the published fare used in construction. Indicates the currency applicable to the Pub Fare Info Fare Amount (bytes ). Indicates the number of decimal places applicable to the Pub Fare Info Fare Amount (bytes ). Bytes FIRST SALE DATE Indicates the earliest date of the period for which the IATA exchange rates used for the constructed fare are applicabe. Bytes LAST SALE DATE Indicates the latest date of the period for which the IATA exchange rates used for the constructed fare are applicabe. Data in bytes is used for database maintenance and/or information purposes only. Byte 228 ACTION Indicates the type of action (either insert or replace) to be taken with this fare record. Bytes Indicates the subscription unit of work at ATPCO. MCN Bytes OLD MCN Indicates the previously transmitted subscription unit of work for a given Tariff/Carrier/Market/Fare Class/Link Number Bytes BATCH N/A Identifies the person/carrier that submitted the batch for processing. International Fares Page E-012

13 Byte Location Match / Byte 246 N/A PROP Bytes Key Match LINK NO Bytes Key Match/ SEQUENCE NO Bytes N/A FARE TYPE Bytes CHANGE TAGS Bytes GFS F.A. DATE Bytes GFS F.A. Number Definition / Processing Not currently used (will always contain 0). Processing ignores this field. Indicates the link number assigned to each unique fare record within tariff, carrier, market and fare class. Indicates the sequence number associated with the fare record within a specific Link Number (bytes ). Not currently used. Processing ignores this field. Indicate the relationship (e.g. the change/difference) between one Sequence Number (bytes ) and the previous, lower Sequence Number, within a Link Number (bytes ). Indicates the date the fare record was filed in the Governmenet Filing System (GFS). Indicates a unique alphanumeric code for the GFS filing [made on the specified GFS F.A. Date (bytes )] that included the fare record. International Fares Page E-013

14 4.0 PROCESSING For a single fare component on a candidate pricing solution, processing must identify the following: The origin and destination points and ensure they are within the geographic application of fares in the International Fare Product (as defined in Section 1.0 of this document). The primary carrier(s) on the fare component o For international fares, determination of primary carrier is based on standards set forth in IATA resolutions. o For domestic fares, the primary carrier canbe any marketing carrier on the fare component. There may be multiple possible primary carriers. In this case, fare records for each possibly primary carrier must be processed and any can be considered valid solutions (provided the fare, footnote, routing, and rule conditions are passed). Processing will match the the primary carrier on the fare component to International Fare Records with that exact carrier code and/or with carrier code YY. If a match is found, processing then attempts to match the origin and destination (market) on the fare record to the fare break points on the fare component. Fares will always be transmitted with a directional indicator of F indicating From Origin City. If processing does resolve to a fare record for the carrier and market, processing attempts to match Effective/Discontinue dates on the fare records to the sale/travel dates on the itinerary, measured from the departure from journey origin. If the travel date from the journey origin is on or within the effective/ discontinue dates of the fare record, processing will validate the fare record. Processing will continue until all matched fare records have been found.. If processing cannot resolve to a fare record for the carrier and market, then no International Fare Record applies for the carrier and fare component being priced. Determination of Fare Record Availablity for Pricing Processing will determine if the fare record is in effect for sale and ticketing based on the date/time when the itinerary is priced. Unless otherwise restricted by any footnote, fare rule, general rule data that resolves to the fare, the following applies: A fare is considered available for sale/ticketing on or after its release date/time from ATPCO. This release date/time is held in the Date and Time fields (bytes 19-30) in the ATPCO Header Record of the International Fares Data Subscription file which also contains the fare record. A fare may be available for sale/ticketing prior to the Effective Date (bytes ) on the fare record, if the date in the ATPCO Header Record is an earlier date. International Fares Page E-014

15 The last date on which a fare is available for sale/ticketing is found in the Discontinue Date (bytes 35-40) on the International Fare Record. This field will always be coded with either a specified date in the YYMMDD format or indicating no discontinue date. o If the discontinue date is earlier than today, the fare is not available for sale immediately upon receipt. o If the discontinue date is today or later than today, the fare is not available for sale after midnight of the discontinue date. Comparing the sale/ticketing date to the Discontinue Date on the fare record determines the period a fare record is available for sale/ticketing. If the Discontinue Date in the fare record is , processing will continue validating the fare record. If the date of sale/ticketing is equal to the Discontinue Date, processing will continue validating the fare record. If the date of sale/ticketing is before the Discontinue Date, processing will continue validating the fare record. If the date of sale/ticketing is after the Discontinue Date, processing will no match the fare record. If the sale/ticketing date on the fare record does not fall on or within the Effective Date on the ATPCO Header Record and the Discontinue Date on the fare record, the fare record fails pricing and must not be selected for validation. International Fares Page E-015

16 4.1 Published Fare Data (bytes 1-125) Once fare records available for pricing have been identified, processing will validate fields on the fare record. This section of the document will provide a basic processing overview of the application of the data applicable to published international fares. There is no required order for this match process. Processing will continue until all possible matches have been identified. If no match is found, then no International Fare Record applies for the carrier and fare component being priced. When open segments are permitted, the validation of any open segment is optimistic, but not unrealistic. Open segments cannot be priced if the carrier is not known. Validation will be against the booked segments, passing the open segments until such time that they are booked. Processing will validate all known information pertaining to the fare and may fail processing if there is enough information to ascertain that the open segments would fail when booked. International Fares Page E-016

17 4.1.1 Tariff Number (bytes 1-3) The Tariff Number is the highest level designator organizing all ATPCO fare, rule, footnote and routing data. It is used to sort and distribute data based on geographical location, data ownership, and tariff type. Published International Fares are grouped by geographic area in defined tariffs (refer to Appendix H for a list of published tariffs). Sample International Fare Public Tariffs*: AREA/GLOBAL TARIFF NAME TARIFF NUMBER FARES DATA HELD IN THIS TARIFF AT TAFP 001 Transatlantic US/CA To/From Area 2/3 EH EUAS 004 Europe Area 3 WH WHFD 017 Within Area 1 Central/South America/Mexico & Caribbean EH TPFD 302 Area 3 Domestic *Tariff names and tariff numbers are subject to change. Both public and private tariffs will be matched in the fare selection process. Tariff Number is held for use in further itinerary pricing in order to resolve to applicable rule, footnote, routing, and add-on fare records as applicable. International Fares Page E-017

18 4.1.2 Carrier Code (bytes 4-6) The Carrier Code identifies the owning/publishing carrier of the fare. Following is an explanation of applicable values: Specific Carrier Code: YY Indicates the fare record is a carrier fare that is owned/published by the specified carrier. Indicates the fare record is an industry (IATA) fare. When processing International Fare Records with a specific carrier code (other than YY) in this field, the Carrier Code field is an exach match to the carrier code for the primary carrier on the fare component being priced. If the primary carrier matches the Carrier Code on the fare record, processing will match this field. If the primary carrier does not match the Carrier Code on the fare record, processing will no match the fare record. When processing International Fare Records with carrier code YY in this field, the Carrier Code field is an automatic match. Internal subscriber processes specify whether or not a primary carrier wishes to participate in YY fares and when to processes YY fares (such as, process in addition to carrier fares or only process when a carrier fare does not exist in the market). If the internal subscriber process indicates to process YY fares for the primary carrier and market being priced, processing will match this field. If the internal subscriber process indicates to process YY fares for the primary carrier and market being priced, processing will no match the fare record. International Fares Page E-018

19 4.1.3 Origin/Destination City and Country (bytes 7-11, 12-13, 14-18, 19-20) The Origin City (bytes 7-11) and Destination City (bytes 14-18) define the market in which the fare record is valid for travel; they do not define the direction of travel. International Fare Records are transmitted From Origin City. The directional application is defined by data in the Directional Indicator (byte 111). A multi-airport city code in either field matches to all airports considered part of that city. For example, WAS matches to DCA and IAD. Fare rules and routings ultimately determine if the fare record may be used in pricing. There is no hierarchical application between records to/from an airport vs. records to/from a city. Example 1 (fare published to/from an airport ) Travel is: JFK-LHR When pricing fare records with the Origin/Destination cities specified below, the match/no match application for the cities is: Fare Record Match/No Match application Origin-Destination Cities NYC-LON Match JFK-LON Match LGA-LON No Match International Fares Page E-019

20 Example 2 (fare published to from a city with the same code as an airport code) OSL = city code for Oslo OSL = airport code within Oslo TRF = airport code within Oslo Travel is: TRF - LHR When pricing fare records with the Origin/Destination cities specified below, the match/no match application for the cities is: Fare Record Match/No Match application Origin-Destination Cities OSL-LON Match TRF-LON Match The Origin Country (bytes 12-13) and Destination Country (bytes 19-20) match against the country (nation) code in which the Origin City and Destination City respectively apply. Refer to Section of this document for information on matching the Origin and Destination City/Country Codes based on the value in the Directional Indicator. International Fares Page E-020

21 4.1.4 Fare Class Code (bytes 21-18) This field identifies the Fare Class Code applicable to the fare record being processed. The Fare Class Code is used to match the applicable Automated Rules records. Refer to Data Application documentation for Automated Rules/Footnote Records and Categories for further information on using the Fare Class Code to match and process rules data applicable to the fare. International Fares Page E-021

22 4.1.5 Discontinue Date (bytes 35-40) NOTE: The Effective Date (bytes 29-34) is not used and is ignored by processing. The actual effective date for the record is specified the Tariff Effective Date field (bytes ). The Discontinue Date specifies the last date on which travel may commence from the origin of the journey unless further restricted by any footnote, fare rule, or general rule data that resolves to the fare. International Fares Page E-022

23 4.1.6 Rule Number (bytes 41-44) This field specifies the Rule Number applicable to the fare record being processed. The Rule Number is used to match the applicable Automated Rules records. Refer to Data Application documentation for Automated Rules/Footnote Records and Categories for further information on using the Rule Number to match and process rules data applicable to the fare. International Fares Page E-023

24 4.1.7 Routing Number (bytes 45-48) This field specifies the Routing Number (or map) applicable to the fare record being processed. The map indicates the path for which air travel is permitted between fare break points and/or the published restrictions that apply between those points. When this field is value 0000, then the Maximum Permitted Mileage (MPM) restriction applies to the fare. The Routing Number is used to match applicable Full Map Routing records and apply routing requirements. Refer to Data Application documentation for Full Map Routings for further information on using the Routing Number to match and process routing requirements applicable to the fare. International Fares Page E-024

25 4.1.8 OW/RT (byte 49) This field specifies whether the fare amount (bytes 54-98) is a one way or round trip amount. Additionally, this field specifies whether a one way fare may or may not be doubled for round trip travel. Following is an explanation of applicable values: Value 1: Value 2: Value 3: One Way fare that may be doubled and halved. Also known as a Tag 1 fare. Can only be used within the following types of pricing units: One Way (OW), Round Trip (RT), Circle Trip (CT), and Open Jaw (OJ) pricing units. Any of these pricing units may be combined end-on-end with another pricing unit. The published fare amount (bytes 54-98) is a one way amount. When used in a RT/CT/OJ pricing unit, the published fare amount is doubled and halved and applied to the fare component being priced. When used in a OW pricing unit, the full published fare amount is applied to the fare component on the OW pricing unit. Round Trip fare. Also known as a Tag 2 fare. Can only be used within the following types of pricing units: Round Trip (RT), Circle Trip (CT), and Open Jaw (OJ) pricing units. Any of these pricing units may be combined end-on-end with another pricing unit. The published fare amount (bytes 54-98) is a round trip amount. Half the published fare amount is applied to the fare component being priced. One Way fare that may not be doubled and halved. Also known as a Tag 3 fare. Can only be used within the following types of pricing units: One Way (OW) pricing units. The OW pricing unit may be combined end-onend with another pricing unit. The published fare amount (bytes 54-98) is a one way amount. The full published fare amount is applied to the fare component on the OW pricing unit being priced. Processing will attempt to match the fare component being priced to the OW/RT field by determining the pricing solution and comparing this to OW/RT value on the fare record, as follows. If the pricing solution consists of the fare component being used in a OW pricing unit: Match fare records with OW/RT value 1 or value 3. No match fare records with OW/RT value 2. If the pricing solution consist of the fare component being used in a RT, CT, or OJ pricing unit: Match fare records with OW/RT value 1 or 2. No match fare records with OW/RT value 3. NOTE: Combintions (Category 10) exceptions and/or restrictions may exist in the Automated Rules data that further restrict the possible pricing solutions. International Fares Page E-025

26 4.1.9 Source (bytes 50-53) This field identifies the data supplier providing the fare record. The field will always be populated with ATP in bytes (with byte 53 blank) indicating the fare record is provided by Airline Tariff Publishing Company. International Fares Page E-026

27 Origin/Destination Fare Amount (bytes 54-83) These fields contain the applicable published fare amount for the fare record being processed (or the unpublished amount for contructed fares). Following is an explanation of the applicable fields: Origin Fare fields Fare Amount (bytes 54-64) Currency Code (bytes 65-67) Number of Decimals (byte 68) Destination Fare fields Fare Amount (bytes 69-79) Currency Code (bytes 80-82) Number of Decimals (byte 83) NOTE: Other Fare fields in bytes are not used. Processing ignores these fields. The Origin Fare fields identify the published fare amount when the fare is applicable from the Origin City (bytes 7-11) to the Destination City (bytes 14-18). The Destination Fare fields identify the published fare amount when the fare is applicable from the Destination City (bytes 14-18) to the Origin City (bytes 7-11). The Directional Application of the fare and associated published fare amount is identified based on the Directional Indicator (byte 111), as follows: The fare applies from Origin City to Destination City. Edits require the fare amount be specified in the Origin Fare fields (bytes 54-68). The Destination Fare fields (bytes 69-83) have no application. International Fares Page E-027

28 Fare Amount (bytes 54-64, 69-79) The Fare Amount indicates the actual published fare amount applicable to the fare record being processed. It is possible this field may contain zeros with applicable data in the associated Currency Code (must contain a valid Currency Code and not value Blank)) and Number of Decimal fields to indicate a free amount Currency Code (65-67, 80-82) The Currency Code indicates the currency associated to the corresponding specified Fare Amount (bytes 54-64, 69-79). Fares may be published in any currency. There is no requirement the fare be published in the currency of the origin or destination country. Processing should apply all matched fare records for the fare component being processed, regardless of currency (and provided all applicable rules, footnote, and routing conditions are passed). Currency of Base Fare For international itineraries (i.e. itineraries that involve at least one international fare), refer to IATA resolutions for standards for determining the currency of the Base Fare. For itineraries that involve multiple domestic fares, but no international fares, the currency of the Base Fare is based on the first country of transportation on the ticket. (This application is based on agreements reached at the IATA RADWG meeting in March 2010.) Example: ZRH-GVA /- MIL-ROM Assume the ZHR-GVA fare is published in CHF and the MIL-ROM fare is published in ITL. Since Switzerland is the first country on the ticket, the currency of the base fare is CHF. International Fares Page E-028

29 Number of Decimals (68, 83) This field indicates the number of decimal places associated to the corresponding specified Fare Amount (bytes 54-64, 69-79) Footnote (bytes ) This field specifies the Footnote(s) applicable to the fare record being processed. The Footnote(s) is used to match the applicable Automated Rules/Footnotes records. One to two footnotes can be specified as follows: Single Footnote: Consists of: One alpha (e.g. A indicates single Footnote A) One numeric (e.g. 1 indicates single Footnote 1) Double numeric (e.g. 12 indicates single Footnote 12) Numeric alpha (e.g. 1A indicates single Footnote 1A) NOTE: Edits prevent entering alpha footnote value F or T. Two Footnotes: Consist of: Double alphas (e.g. AB indicates footnote A and footnote B) Alpha numeric (e.g. A1 indicates footnote A and footnote 1) NOTE 1: Edits prevent entering data to reference a single alpha footnote F or T (e.g. AF, AT, TB, FC, FT, TF are not permitted) NOTE 2: Edits prevent entering the same alpha twice in this field (e.g. AA is not permitted) Refer to Data Application documentation for Automated Rules/Footnote Records and Categories for further information on using the Footnote to match and process footnote data applicable to the fare. International Fares Page E-029

30 Directional Indicator (byte 111) Data in this field is required and specifies the directional application of the fare applicable to this fare record: The value in this field will always be the following: Value F: From Origin City. The fare applies from the Origin City (bytes 7-11) to the Destination City (bytes 14-18). The directional application is dependent upon the pricing solution in which the fare is being priced, as follows: International Pricing Unit If the fare is being priced in a pricing unit that contains at least one international fare, then the directional application is dictated based on standards set forth in IATA resolutions. Refer to applicable resolutions for guidelines on determining the directional application. Wholly Domestic Pricing Unit If the fare is being priced in a pricing unit that contains only domestic fares (does not contain any international fares), then the directional application is dependent upon the type of pricing unit in which the fare is being priced, as follows: OW Pricing Unit: Select fares in the direction of travel. RT/CT/OJ Pricing Unit: Select fares in the direction of travel. Exception: Fares on the last fare component of the pricing unit are selected in the opposite direction of travel. This application is further detailed in the chart on the following page. International Fares Page E-030

31 In the chart below, Pricing Unit origins are shown in bold type. Blue arrows indicate fares selected in the opposite direction of travel. Pricing Unit Domestic Fare Selection Rule Directionality Examples Direction of Travel Direction of Fare Selection One Way (OW) Fares are selected in direction of travel. SYD MEL SYD MEL Round Trip (RT) Fares are selected in the direction of travel. SYD MEL SYD MEL Circle Trip (CT) Exception: Fares selected on the last fare component are opposite the direction of travel. SYD MEL SYD MEL BNE BNE Origin Open Jaw (OOJ) SYD MEL SYD MEL BNE BNE Double Open Jaw (DOJ) SYD BNE MEL ADL SYD BNE MEL ADL Turnaround Open Jaw (TOJ) SYD MEL SYD MEL ADL ADL International Fare Selection Rule International Pricing Unit Fare selection is dictated by IATA resolutions. SYD SIN SYD SIN BNE BNE International Fares Page E-031

32 Global Indicator (bytes ) This field identifies the global routing applicable to the fare. Data in this field matches against the route of travel for the fare being priced. Refer to Appendix J for a list of applicable Global Codes. International Fares Page E-032

33 Tariff Effective Date (bytes ) This field specifies the first date on which travel may commence from the origin of the journey unless further restricted by any footnote, fare rule, or general rule data that resolves to the fare. NOTE: The Effective Date (bytes 29-34) is not used and is ignored by processing. The actual effective date for the record is specified in the Tariff Effective Date field (bytes ). International Fares Page E-033

34 MPM (bytes ) This field specifies the Maximum Permitted Mileage (MPM) applicable to the fare. Data is always present in this field whether or not the fare is actually restricted by MPM. Data in the Routing Number (bytes 45-48) field will indicate if the fare is restricted to the MPM and/or any applicable routing map that must be applied. Data in this field has no application (and is ignored) for domestic fares. Refer to Data Application for Full Map Routings for further information. International Fares Page E-034

35 4.2 Constructed Fares Data (bytes ) Data in the following fields only applies if the fare record contains a constructed fare that has been constructed by ATPCO and is being distributed in subscriptions. Data in these fields is not applicable for published fares and is ignored when processing published fares. Data application for these fields is out of scope for the October 2010 Data Application Working Group. The data application will be documented at a later date Origin Add-on Information (bytes ) Data in these fields contains the follwoing information applicable to the origin add-on (if any): Fare Class Code (bytes ) Routing (bytes ) Footnote (bytes ) Gateway (bytes ) Add-on amount, negative/positive sign, currency, decimal (bytes ) Destination Add-on Information (bytes ) Data in these fields contains the follwoing information applicable to the destination add-on (if any): Fare Class Code (bytes ) Routing (bytes ) Footnote (bytes ) Gateway (bytes ) Add-on amount, negative/positive sign, currency, decimal (bytes ) Published Fare Information (bytes ) These fields contain the Footnote(s) and Fare Amount applicable to the published fare being used in the construction. International Fares Page E-035

36 4.2.4 Sale Dates (bytes ) These field contain the First and Last dates relative to the applicable period for the IATA exchange rates used in the construction. Data in these fiels is derived from the dates present in the PI1 (International Currency Level Exchange Rates). International Fares Page E-036

37 4.3 Database Maintenance (bytes ) These fields are used for database maintenance. Data application for these fields is out of scope for the October 2010 Data Application Working Group. The data application will be documented at a later date (byte 228) This field identifies the subscription action being performed with this record. Following is an explanation of applicable values: Value I: Insert the record into the existing database. There are no existing records for the tariff, carirer, market, fare class, and link number. Value R: Replace the existing record for the tariff, carrier, market, fare class, and link number with the new record MCN (bytes ) Data in this field indicates the ATPCO subscription unit of work in which the fare record is transmitted Old MCN (bytes ) Data in this field indicates the previous ATPCO subscription unit of work for a specific tariff, carrier, market, fare class, and link number. International Fares Page E-037

38 4.3.4 Link Number (bytes ) and Sequence Number (bytes ) The Link Number (bytes ) specifies a number assigned to a unique tariff, carrier, market and fare class combination. The Sequence Number (bytes ) indicates a sequential number for a record within a link number. Link Numbers are included in each transaction to distinguish unique records within the Tariff, Carrier, Market, and Fare Class. Successor records containing the same Link Number as a previous record will contain a higher sequence number. The link and sequence numbers are used to establish the relationship between records especially when the effective date of the last transaction is changed Published/Add-on Segments in a Link Segments in a link show the changes made to the link. History of a link can be traced back through sequences. Only one segment is effective for a given day. Link is cancelled by a direct cancellation action. Link may be cancelled once a footnote discontinue date has passed. Segments always have valid subscription tags, which clearly show the nature of changes to the link. LINK SEQ# EFF DISC TAGS JAN08 15MAY08 new 2 16MAY08 15MAY08 increase 3 16MAY08 20OCT08 reduce 4 21OCT08 none ftnt-chg Unpublished Segments in a Link Segments within an unpublished link reflect the variations of the published component and add-on component and the PI1 (currency adjustment formula) component. A component is considered a unit of data that affects the dates of an unpublished record. History of changes to an unpublished link cannot be tracked through the segments. International Fares Page E-038

39 4.3.5 Change Tag (bytes ) This field specifies the relationship of this record to the previous record within a link number (i.e. it specifies what has changed). A record may have more than one tag [e.g. Tag 2 Increased Fare Amount (byte 259) and Tag 6 Routing Number Change (byte 263)]. Tag 10 Effective Date Change (byte 267) is solely used to indicate a change-in-effective date only transaction and is not included when other data is being revised. The following table show the subscription tags that are used for specified (publsihed( fares. The tables show the maximum number of subscription tags that can be set together. Read down each "Possible Combination of Tags" column for applicable tags. For example, Tag 1 New Record New Link Number can be included with Tag 10 Effective Date Change, and Tag 18 Indicates Fare Record is Not Subject to NUC Conversion. On any one record, there will always be at least one subscription tag set. Subscription Tags Used in the Specified Fares File Tag Description Possible Combinations of Tags 1 NEW FARE X 2 INCREASE X 3 REDUCE X 4 NOT USED X X 5 FTNT CHANGE X X 6 RTG CHANGE 7 RESERVED 8 MPM CHANGE X 9 RESERVED 10 EFF DATE CHANGE X X X X X X X 11 REINSTATE X 12 REISSUE X 13 RESERVED 14 Used only in constructed fares 15 CANCEL X 16 Used only in constructed fares 17 CURRENCY CHANGE X X 18 NOT SUBJECT TO NUC X X X X X X X International Fares Page E-039

40 4.3.6 GFS Filing Advice (bytes ) These fields specify the ATPCO Government Filing System (GFS) date and identifier applicable to the fare record. International Fares Page E-040

41 4.3.7 Examples The explanation below and chart that follows provide examples of changes made to specified fares. Example 1: New Fare Example 1 shows a new fare for the following tariff, carrier, market and fare class, 003/XX/SEA-TYO/YMZ for $ being sent with an I (insert) action code and a tag 1. Example 2: Increase and footnote change Example 2 shows an increase and footnote change to the record in Example 1 with a R (replace) action code and tags 2 and 5 turned on. Example 3: Decrease and footnote change Example 3 shows a decrease and footnotes change to the record in Example 2. These records show a Replace action code and tags 3 and 5 turned on. Example 4: Cancellation of a Fare Example 4 shows a cancel being sent with a Replace action code and tag 15 turned on. Two sequences under link 1 relating to this fare are sent in subscriptions to show the previous record as well as the cancel. Link 1 seq. 2 shows a discontinue date of 21OCT07, which is one day earlier than the tariff effective date of the cancelled segment. Example 5: Effective date only change Example 5A shows a new fare which was sent in subscriptions as an Insert action on 11FEB08, with a tariff effective date of 13MAR08. Example 5B shows an effective date change to the record in example 5A, and sent in subscriptions on 15FEB08 with Tags 1 and 10 turned on to show that an effective date change only was made to the new record. International Fares Page E-041

42 Example 6: Multiple Tags are included (2, 5, 13, and 17). TAG 2 = Increase TAG 5 = Footnote change TAG 17 = Currency code change Example 6A shows a new fare being sent in subscriptions on 30NOV07 for the amount of XSD, with an Insert action code. Example 6B shows four changes to the record in example 6A, with two sequences being sent in subscriptions on 18FEB08. Link 1 seq. 2 shows the changed record with the new currency code SDD, a fare increase, and an added footnote. The currency code change came as a result of Sudan changing their currency from XSD to SDD on 18FEB08. The fare was increased to SDD and footnote P was added. International Fares Page E-042

43 Examples Specified Fares TARIFF NUMBER CXR CODE ORIG CITY DEST CITY FARE CLASS *FARE AMOUNTS* **DATES** (CONSTRUCTED) TARIFF EFFECT 1 ST -SALE D/I MPM LINK RTG SUBS TAGS UNPUB CUR EX. NO. ACTION CODE ORIG CTRY DEST CTRY FTNT DISC LAST-SALE OW/ RT GLB SEQ RULE PUBLISHED FARE CUR XX SEA TYO YMZ F I US JP PA USD XX SEA TYO YMZ F R US JP B PA USD XX SEA TYO YNZ F R US JP PA USD XX SEA TYO YMZ F R US JP H PA USD XX SEA TYO YMZ F R US JP B PA USD XY LAX STO KWSMINI F R US SE AT USD XY LAX STO KWSMINI F R US SE AT USD International Fares Page E-043

44 Examples Specified Fares (continued) TARIFF NUMBER CXR CODE ORIG CITY DEST CITY FARE CLASS *FARE AMOUNTS* **DATES** (CONSTRUCTED) TARIFF EFFECT 1 ST -SALE D/I MPM LINK RTG SUBS TAGS UNPUB CUR EX. NO. ACTION CODE ORIG CTRY DEST CTRY FTNT DISC LAST-SALE OW/ RT GLB SEQ RULE PUBLISHED FARE CUR 5A 101 XZ YMQ LON BLMAPCD F CA GB AT GBP 5B 101 XZ YMQ LON BLMAPCD F R CA GB AT GBP 5B 101 XZ YMQ LON BLMAPCD F R CA GB AT GBP 6A 022 YY KRT KLU F F I SD AT EM XSD 6B 022 YY KRT KLU F F R SD AT P EM SDD 6B 022 YY KRT KLU F F R SD AT EM XSD International Fares Page E-044

45 5.0 NOT USED 6.0 CODING CONVENTIONS To be determined. International Fares Page E-045