DATA APPLICATION BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7

Transcription

1 DATA APPLICATION BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7 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 2008 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 APPLICATION OF DATA FOR RECORD S Carrier Code (bytes 3-5) Service and Sub Code (bytes 6-10) Service Type (byte 21) Sequence Number (bytes 30-36) Public/Private (byte 37) Maintenance/Ticket Dates (bytes 38-49) Travel Dates (bytes 50-61) Passenger Type (bytes 62-64) Passenger Age Min/Max (bytes 66-67, 68-69) Passenger Occurrence First/Last (bytes 70-72, 73-75) Frequent Flyer Status (byte 76) Account Code Table No. 172 (bytes 85-92) Ticket Designator Table No. 173 (bytes ) Tour Code (bytes ) Security Table No. 183 (bytes ) Geographic Specification (bytes ) Geo Spec Travel Indicator (bytes ) Geo Spec Sector/Portion/Journey (byte 133) Geo Spec From/To/Within (byte 134) Geo Spec Loc 1/Loc 2 (bytes , ) Geo Spec Loc 3 (bytes ) Geo Spec Stopover/Connection/Destination Indicator (byte 169) Geo Spec Exception Stopover Time (bytes ) Cabin and RBD Table 198 (bytes ) Cabin (byte 175) RBD Answer Table Record A Page D.03.S7.01

3 RBD Table 198 (bytes ) Upgrade To Cabin and RBD Table 198 (bytes ) Fare (bytes ) Carrier/Resulting Fare Class Table No. 171 (bytes ) Ticket Designator Table No. 173 (bytes ) Tariff (bytes ) Rule (bytes ) Cat 19/25/35 (byte 216) Start/Stop Time (Bytes ) Day of Week (Bytes ) Carrier / Flight Application Table 186 (bytes ) Equipment Type Table 165 (bytes ) Equipment (bytes ) Advance Purchase (bytes ) Advance Purchase Reservations / Ticketing (bytes ) Advance Purchase Ticket Issue (byte 256) Mileage Minimum / Maximum (bytes , ) Baggage Free Pieces, First/Last Occurrence and Baggage Weight Free Pieces (bytes ) First/Last Excess Baggage Piece (bytes ) Baggage Weight/Unit (bytes ) Baggage Travel Application (byte 280) Service Type Code IATA Application Indicators (bytes ) Refund/Reissue (byte 284) Commission (byte 285) Interline Settlement (byte 286) Form of Refund (byte 287) Not Available / No Charge (byte 288) Specified Service Fee (bytes ) Collect/Subtract (byte 289) Net/Sell (byte 290) AND/OR Indicator (bytes 291) Currency Table 170 (bytes ) Mileage Fee (bytes ) Fee Application (byte 311) Tax Application (byte 312) Availability (byte 329) Customer Index Score Minimum and Maximum (bytes ) Minimum Score (bytes ) Maximum Score (bytes ) Rule Buster Rule Matching Fare Class (bytes ) Text Table 196 (bytes ) Page D.03.S7.02

4 Rule Buster Recurring Segment (bytes ) TRAVEL SEGMENT INDICATORS CODING CONVENTIONS NOT AVAILABLE/NO CHARGE FFY CODING CONVENTION FOR BAGGAGE PROVISIONS OCCURRENCE OF EXCESS Page D.03.S7.03

5 1.0 OVERVIEW Record S7 specifies the qualifying provisions and any applicable fees for: Optional Services (Flight Related, Ticket Related, Rule Buster, and Merchandise); and Baggage Services (Checked and Carry-on Allowance, Embargoes, Pre-Paid Baggage and Checked and Carry-on Charges). Processing Record S7 differs depending upon whether the data is being processed for Optional Services or Baggage Services. This document details the processing for Baggage Services. Refer to the Data Application for Record S7 specific to Optional Services for information on how to process the record for Flight Related, Ticket Related, Rule Buster, and Merchandise. Record S7 provides applicable information for carriers to manage the baggage provisions specified within their contract of carriage. Data is controlled by the carrier whose rules apply as a result of Baggage Selection and the data is applicable to a defined portion of travel defined as the Baggage Travel (BT). Refer to the Baggage Allowance and Charges Data Application Overview document for a complete overview of Baggage Services processing, including, but not limited to, a thorough explanation regarding: Determination of which carrier s baggage rules apply Identification of the Baggage Travel (BT) on which baggage data is being assessed High-level processing overview of all Optional Services Records For Baggage Provisions, the data in Record S7 is processed for the following purposes: 1. To determine the baggage allowance (checked and carry-on); 2. To determine baggage embargoes 3. To determine any pre-paid baggage offers, and 4. To determine the applicable charge for any excess baggage (checked and carry-on). Unless otherwise specified in this document, the processing logic is the same whether the Record S7 is being processed as a display record or a pricing record. For baggage services related to a specific flight, fare and/or ticket, the fare pricing process must be complete in order to fully process all fields in Record S7. If Record S7 is processed before fare pricing is completed (e.g. for display purposes), then the validity of the results are questionable in that the service may not be applicable once fare pricing is complete. It is possible that all information may not be known at the time of displaying the service (e.g. not known if display is done pre-pricing) and processing will need to reapply the data in the record at the time of pricing the service. Page D.03.S7.04

6 100 Series Tables This document details the data application for Record S7 only. The 100 Series Tables used in this record are Services Record 3s. Unless otherwise specified in this document, the data application for Services Record Zone Table No. 178 and Carrier/Flight Table No 186 is the same as the data application for Table 178 and Table 186 in Records S1, S2 and/or S4 (applicable to Fuel and Insurance and Ticketing Fees). Data application for the following Services Record 100 Series tables (as applicable for Record S7) are contained in separate documents: Equipment Type Table No. 165 Currency Table No. 170 Carrier/Resulting Fare Class Code Table No. 171 Account Code Table No. 172 Ticket Designator Table No. 173 Security Table No. 183 RBD Table 198 Sub Code Table 163 NOTE: Processing for Security Table No. 183 is very similar to processing for Automated Rules Security Table No. 983; however, several fields in Table 983 have either been made filler or been redefined for use in Table 183. Subscribers to Baggage Services (Service Types A, B, C, E and P) may receive 100 series tables that are applicable for both Optional Services and Baggage. ATPCO assumes that any carrier utilizing Record S7 will ensure that all legal and tax requirements are met regarding any resulting fees. Any carriers that wish to specify any taxes on Baggage must instruct these within the ATPCO Tax Collection and Distribution product and not within this product. Page D.03.S7.05

7 1.1 Data Requirements DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES Carrier whose baggage provisions are being assessed (Record S5 carrier). Record S5 Sub Code and Service Type value for the baggage being requested/priced. Date the passenger ticket is being issued or was issued Date of departure for each sector of the baggage travel (BT) Date of arrival for each sector of the BT Passenger Type Code on the input command Passenger Age Passenger s frequent flyer status for the Record S7 owning carrier Account Code on the input command Ticket Designator on the input command Tour Code on the ticket Point of ticketing (sale) (to include geographic locations, carrier, GDS, travel agencies, IATA travel agency numbers, department identifiers/codes, ERSP numbers, CRT address, and duty function code) All ticketed points of travel on the BT All fare break, stopover and connection points on the BT Record S7 owning carrier s cabin in which the passenger is booked for each sector on the BT Marketing and operating carriers RBD in which the passenger is booked for each sector on the BT Resulting Fare Class Code for each sector on the BT Fare Type Code for each sector on the BT Significant (primary) carrier of the fare encompassing each sector within the BT Whether the fare for each sector on the BT is created from Categories 19-22, 25, or 35. Ticket Designator (on the ticket) on each sector of the BT ATPCO governing Tariff for each sector of the BT ATPCO governing Rule for each sector on the BT Time of departure for each sector on the BT Time of arrival for each sector on the BT Day of departure for each sector on the BT Day of arrival for each sector on the BT Marketing carrier on each sector on the BT Page D.03.S7.06

8 Operating carrier on each sector on the BT Marketing carrier s flight number on each sector on the BT Operating carrier s Equipment code on each sector on the BT Mileage from the origin to the destination of the BT Whether or not the Record S7 owner s frequent flyer mileage information is available For the journey: o Origin o Destination o Furthest Checked Point o All Ticketed and Unticketed Points Bag information (for baggage charges) o Bag type for each checked and carry-on piece o Total number of checked and carry-on pieces o Total weight (pounds and kilograms) and size (inches and centimeters) of all combined checked and carry-on pieces o Weight (pounds and kilograms) and size (inches and centimeters) for each checked and carry-on piece NOTE: Processing will always take a whole number weight to the S7 to apply a charge. Any decimals are truncated. For example if a passenger has 25.7 kg combined for all bags and the allowance is 20 kg, then this is considered 5 kgs over and processing takes the 5 kg to Record S7. Excess Baggage information (see section Baggage Free Pieces, First/Last Occurrence and Weight) o Occurrences of baggage in excess o Combined weight of baggage in excess Page D.03.S7.07

9 1.2 Basic Processing Overview High Level Processing DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES Match the Record S5 for the Carrier, Service Type (checked allowance, carry-on allowance, embargoes, prepaid charges, charges), and Sub Code being processed Yes Attempt to resolve to an applicable Record S7 for the Carrier, Sub Code, and Service Type identified on the Record S5. Is there a match (based on all defined match criteria)? no Defer Baggage Rules to the Most Significant Marketing Carrier. Process Record S5 for the Most Significant Marketing Carrier Is the MSC the same as the carrier whose Record S7 specifies defer? yes yes Assume a no match to this Record S7 and continue processing to the next record for the same Carrier, Service Type, and Sub Code Do you match to an applicable Record S7 with Not Available/No Charge (byte 288) value D (defer)? NOTE: This only occurs for Service Type A (checked Allowance) no Yes Apply the data in the matched Record S7. Do not continue processing to another Record S7 for the same Carrier, Service Type, and Sub Sode. No No match the Record S7 and continue processing to the next record for the same Carrier, Service Type, and Sub Code See Breakout Processing Flow Chart for Detailed Baggage Charges Processing On the Following Page See Baggage Allowance and Charges Overview for detailed processing flow applicable to Baggage Services Page D.03.S7.08

10 Flow Chart Are you processing excess total weight (exceeding the Weight/Unit fields bytes ), excess total pieces (exceeding the Free PCs field bytes and/or Text Table 196 formatted text bytes ) or both? The following breakout processing provides more details on baggage charges processing based on what is determined in excess Excess Combined Weight (excess total weight of all checked pieces) Excess Weight and Pieces (excess total number of checked pieces AND excess total weight of all checked pieces) Excess Total Pieces (excess total number of checked pieces) AND/OR Excess per piece (number, weight or size) Process Record S7 Sub Code Record for the carrier(s) whose rules apply. Is there a match to a Record S7 applicable to baggage charges services (Service Type byte 21=value C), the weight in excess (if applicable), and sub code 0DG (standard weight system charges sub code) for the service being requested? <-- Process Both --> Process Record S7 Sub Code Record for the carrier(s) whose rules apply and each sub code in excess. Is there a match to a Record S7 applicable to baggage charges services (Service Type byte 21=value C), the Occurrence of excess baggage (if applicable), and the Sub Code in excess for the service being requested? Use the resulting baggage charges for the applicable business purpose (e.g. quote baggage charges OR apply baggage charges at check-in Yes No The baggage charges service is not automated via ATPCO data (use the data of the check-in carrier) Examples Determine Charge for an Excess Bag (sub code ABC) Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C o Occurrence = 1 and o Sub Code = ABC Determine Charge for 5 kilos excess Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C o 5 kilos excess and o Sub Code 0DG Determine Charge for an Excess Bag (sub code ABC) AND 5 kilos Excess Weight Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection), Service Type C, Occurrence 1 and Sub Code ABC AND o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection), Service Type C, 5 excess kilos and Sub Code 0DG. o Accumulate Charges add ABC and 0DG charge together Charge for a Heavy Bag (sub code BCD) Process the S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C and o Sub Code BCD (Note: A Heavy Bag that does not resolve to a Baggage Allowance Record is not assigned an occurrence) Page D.03.S7.09

11 2.0 DEFINITIONS AND ASSUMPTIONS DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES 2.1 Definitions Term Significant (Primary) Carrier Resulting Fare Class Code Most Significant Carrier BT (Baggage Travel) Definition The marketing carrier on the governing/primary sector for the fare associated to the Resulting Fare Class Code and Ticket Designator specified in this record. The alphanumerics up to (but not including) the slash in the Fare Basis Box that will be or already is on the ticket as a result of the itinerary pricing process. For Baggage processing only (Service Types A, B, E, C, and P), this is the carrier resulting from the Baggage Selection process (See Baggage Allowance and Charges Overview Attachment A). For Baggage processing only (Service Types A, B,E, C, and P), this is the travel resulting from the Baggage Selection process (See Baggage Allowance and Charges Overview Attachment A) Refer to Baggage Allowance and Charges Overview for additional definitions applicable to Baggage processing. Page D.03.S7.010

12 2.2 Assumptions Refer to Section 2.2 Assumptions in the Baggage Allowance and Charges Overview for a detailed explanation of the system assumptions when baggage data does not exist or is not matched. Page D.03.S7.011

13 3.0 DETAILED FIELD PROCESSING DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES Byte Location Bytes 1-2 Record Type Bytes 3-5 Carrier Code Bytes 6-10 Service and Sub Code Bytes Filler Byte 21 Service Type Bytes MCN Bytes Sequence Number Bytes 37 Public / Private Indicator Bytes Maintenance/ Ticket Dates (First/Last) Bytes Travel Dates (First/Last) Bytes Passenger Type Code Byte 65 Filler Match / Action Definition / Processing Key Match Indicates the Record Number for which the data is formatted. Key Match Key Match/ Action N/A Key Match/ Action Action Key Match/ Action Action Match Match Match N/A Specifies the carrier whose service is being processed. Data in this field is an exact match to the Carrier Code on the Record S5 for the service being processed. Specifies the ATPCO Service Code and Sub-Code applicable to this record. Data in this field is an exact match to the Service Code and Sub Code on the Record S5 for the service being processed. Indicates the type of service and the scope of travel/geography to which the data in this record applies. Data in this field is an exact match to the Service Type field in the Record S5 for the service being processed. Indicates the subscription unit of work. This is used for data base maintenance only. Specifies the order in which the records must be processed within each unique Carrier, Service Type Code (ATPCO Service Code OC and Sub-Code) and Service Type value combination Specifies whether the data in the record is public or private for ATPCO distribution and viewership and subscriber display. Specify that the data in this record applies for passenger tickets sold on/after the first ticket date and on/before the last ticket date. These dates are used by subscribers to perform database maintenance. Indicates that the departure of the travel that matches the record must be on or within specific dates. Indicates that the data in this record only applies for the specified passenger type. Page D.03.S7.012

14 Byte Location Bytes Passenger Age (Min/Max) Bytes Passenger Occurrence (First/Last) Bytes 76 Frequent Flyer Status Bytes Filler Bytes Account Code Table No. 172 Bytes Ticket Designator Table No. 173 Bytes Tour Code Bytes Security Table No. 183 Bytes Filler Bytes Travel Indicator Byte 132 Geo Spec Filler Byte 133 Geo Spec Sect/Port/Journey Byte 134 Geo Spec From/To/Within Match / Action Definition / Processing Match Indicates the age of the passenger to whom the record applies. Match Match N/A Match Match Match Match N/A Match N/A Match Match Not applicable for Baggage processing. Processing assumes an automatic match to these fields. Indicates the frequent flyer status of the passenger as defined by the Record S7 owning carrier. A table containing the Account Code(s) for which the record is applicable. A table containing the qualifying Ticket Designator(s) for which the record is applicable. Indicates the alphanumeric tour code on the ticket for which the record is applicable. A table containing the viewing (display)/booking/sales location(s) for which the record is applicable. Specifies the Travel Indicator applicable to the travel on which the service applies. Specifies that the data in this record must match against the Baggage Travel or the journey. Specifies the from/to/between directional application of the data in the following Loc 1 & Loc 2 fields or that travel must be wholly within Loc 1. Page D.03.S7.013

15 Byte Location Bytes Geo Spec Loc 1 Byte Geo Spec Filler Match / Action Definition / Processing Match Indicates that the data in this record only applies to travel where at least one end point of the travel is in the specified location or that all travel must be wholly within the specified location (depending upon the data in the From/To/Within field). N/A Bytes Geo Spec Loc 2 Byte Geo Spec Filler Match N/A Indicates that the data in this record only applies to travel where at least one end point of the travel is in the specified location (and the other end point is in the location specified in Loc 1). Bytes Geo Spec Loc 3 Byte 169 Geo Spec Stopover/Connection/ Destination Byte Geo Spec Exception Stopover Time/Unit Byte 174 Geo Spec Filler Byte 175 Cabin Bytes RBD Table No. 198 Match Match Match/Action N/A Match Match Indicates that travel between Loc 1 and Loc 2 must be via a specified location. Indicates that the via point(s) on travel that matches the record must be stopover and/or connection points or that the destination point of the travel must be the first stopover on the travel. Indicates the minimum amount of elapsed time at a point at which the point becomes a stopover. Indicates the Cabin where the passenger is booked on the travel. A table specifying a list of RBD(s) (and the associated carrier) where the passenger must be booked on the travel. Page D.03.S7.014

16 Byte Location Bytes 184 Upgrade To Cabin Bytes Upgrade To RBD Table No. 198 Bytes Carrier/Resulting Fare Class Code Table No. 171 Bytes Ticket Designator Table No. 173 Bytes Tariff Bytes Rule Byte 216 Cat 19/25/35 Bytes Start/Stop Time Match / Action Definition / Processing Match Not applicable for Baggage processing. Processing assumes an automatic match to this field. Match Not applicable for Baggage processing. Processing assumes an automatic match to this field. Match Match Match Match Match Match A table specifying the Resulting Fare Class Code(s) (fare basis code excluding the ticket designator that is or will be reflected on the passenger ticket), fare type code, and associated significant (primary) carrier(s) applicable to the travel on which the service is being priced. A table specifying the Ticket Designator(s) applicable to the travel on which the service is being priced. Indicates the Tariff required on the travel that matches the record. Indicates the Rule required on the travel that matches the record. Indicates that the fare applicable to the travel on which the service is being priced must have been created from Categories 19-22, 25, or 35. Indicates that the departure of the travel that matches the record must be within a specific start/stop time. When Day of Week is also present, indicates whether the Start/Stop times apply daily or as a range. Bytes Day of Week Bytes Carrier/Flight Table No. 186 Bytes Equipment Type Table No. 165 Match Match Match Indicates that the departure of the travel that matches the record must be on a specific day(s) of week. Indicates the flight number(s) and/or marketing carrier(s) required on the travel that matches the record. Indicates the equipment type(s) required on the travel that matches the record. Page D.03.S7.015

17 Byte Location Bytes Equipment Bytes Advanced Purchase Res / Tkt Bytes 256 Advanced Purchase Tkt Issue Bytes Mileage Minimum/Maximum Bytes Free Pieces Bytes First PC Bytes Last PC Bytes Baggage Weight/Unit Match / Action Definition / Processing Match Indicates the equipment required on the travel that matches the record. Match/Action Match N/A Action Match Match Match/ Action Match: Indicates the last time the service may be purchased before departure of the originating flight of the travel that matches the record Action: Specifies that reservations must be made and the EMD must be issued by the specified time before departure of the originating flight of the travel that matches the record. Indicates the service must be purchased at the same time as the passenger s ticket is issued for travel. This field specifies the Ticketed Point Mileage (TPM) for the travel on which the service applies. Indicates the number of checked baggage pieces permitted free per passenger. Indicates the first occurrence of excess baggage to which a charge applies. Indicates the last occurrence of excess baggage to which a charge applies. Indicates the baggage weight and unit applicable to the data in this record. With Service Type A or B, this is the total weight of all baggage permitted free per passenger. This data is applied with an Action application. Byte 280 Baggage Travel Application Byte Filler Match/Action N/A With Service Type C, this is a weight value for all passenger baggage up to which a charge applies. This data is applied with a Match application. Specifies whether the data in the Cabin field, RBD Table, Carrier/Flight Table and Carrier/Resulting Fare Class Table matches at least one provision of the Baggage Travel. Page D.03.S7.016

18 Byte Location Bytes Service Type Code IATA Application Indicators Match / Action Definition / Processing Action Identifies whether the fee for the Service Type Code is refundable/reissuable, commissionable, and/or interlineable. These indicators will be placed after the Sub-code portion of the Service Type Code in order to make up the complete Service Type Code to appear on the receipt. Byte 287 Form of Refund Byte 288 No Charge / Not Available Byte 289 Specified Service Fee Collect/Subtract Byte 290 Specified Service Fee Net/Sell Byte 291 Specified Service Fee AND/OR Indicator Bytes Specified Service Fee Currency Table No. 170 Bytes Specified Service Fee Filler Bytes Specified Service Fee Mileage Fee Action Action Action Action Action Action N/A Match/Action Specifies the form of refund permitted when the Service Type Code is refundable. Indicates data in this record will apply a zero fee amount or that the requested service is not available. Indicates that the fee specified in this record must be collected (charged) separately or discounted (subtracted) from the fare. NOTE: Upon initial implementation, this field must be Blank indicating the fee must be collected (charged) separately. Indicates that the fee specified in this record is a selling or net fee amount. NOTE: Upon initial implementation, this field must be Blank indicating the fee is a selling amount. Specifies whether the fee data in Currency Table No. 170 and the Mileage Fee field has an AND application (must assess both fees) or an OR application (must assess either fee) A table containing a list of specified fees based upon the point of sale or journey origin. Match: Specifies that if access is available to the frequent flyer mileage information for the Record S7 carrier, then the passenger must have the specified number of miles in order to match the record. (Only applicable when data is present in this field and the AND/OR Indicator specifies that a Mileage fee must be assessed.) Action: Identifies a fee expressed in frequent flyer miles applicable to the service that matches this record. Page D.03.S7.017

19 Byte Location Byte 311 Specified Service Fee Fee Application Byte 312 Tax Application Bytes Filler Byte 329 Availability Bytes Rule Buster Rule Matching Fare Class Bytes 338 Filler Bytes Customer Index Score Minimum Score Bytes Customer Index Score Maximum Score Bytes Filler Bytes Text Table No. 196 Bytes Number of Segments Bytes Rule Buster Category Bytes Rule Buster Tariff Bytes Rule Buster Rule Match / Action Definition / Processing Action Specifies whether the Baggage Fee applies per checked portion, baggage travel, as a percentage of the fare per kg, or per kg over the free allowance. Action N/A Action Action N/A Action Action N/A Action Action Action Action Action Specifies whether or not fee amounts are inclusive of applicable taxes. Specifies whether or not processing should check availability (reservation) prior to pricing the service. Not applicable for Baggage processing. Specifies the customer index score. The field identifies the minimum value of the customer index score range. Specifies the customer index score. The field identifies the maximum value of the customer index score range. A table containing free form text applicable to the service specified in the record. Specifies the number of occurrences of the data in the following fields. For baggage, this will always be 00. Not applicable for Baggage processing. Not applicable for Baggage processing. Not applicable for Baggage processing. Page D.03.S7.018

20 Byte Location Bytes Rule Buster Filler Match / Action Definition / Processing N/A Page D.03.S7.019

21 4.0 PROCESSING Prior to processing Records S5 and S7, processing must perform baggage selection (refer to Baggage Allowance and Charges Overview Attachment A Baggage Selection) in order to determine the Baggage Travel (BT) and which carrier s rules apply. Each baggage service is uniquely identified based on the following Record S5 fields: Carrier field (Record S5 bytes 3-5); Sub Code (Record S5 bytes 8-10); and Service Type (Record S5 byte 21) The Service Type value in Record S5 specifies whether the Sub Code identifies a baggage allowance (checked), carry-on allowance, embargoes, pre-paid baggage, or baggage charges. Processing applies the Record S7 data for each unique combination of Carrier, Sub Code, and Service Type as applicable based on the following high-level steps: 1. Determine the type of baggage data (Service Type) to be processed: Checked Allowance (Type A), Carry-on Allowance (Type B), Embargoes (Type E), Prepaid Baggage (Type P), or Charges (Type C). 2. Identify the Baggage Travel (BT), which can differ depending upon the Service Type. 3. Identify the Carrier whose baggage rules apply, which is based upon Service Type and Baggage Travel. 4. Process Sub Code Services Record S5 for the Carrier (identified in Step 3), Service Type being processed, and Sub Code (if known, e.g. 0DF for checked Allowance). If a match is made, then continue processing to Record S7 5. Process Provisions Record S7 for the Baggage Travel (identified in Step 2), Carrier (identified in Step 3), Service Type and Sub Code (identified by the matched Record S5). 6. If a match is made to Record S7, then apply the baggage data in the record based on the Service Type being processed. The following pages provide an explanation of Record S7 processing relative to each Service Type Code. Page D.03.S7.020

22 Service Type A Baggage Allowance (checked) Baggage Allowance for checked baggage is identified by Service Type value A and Sub Code 0DF on the Record S5 Sub Code Record as well as the Record S7. Baggage Allowance services define the baggage allowance that a passenger can check for free. Baggage Allowance services are processed for business purposes including but not limited to the following: Displaying the free baggage allowance prior to passenger ticketing, Displaying the free baggage allowance at time of passenger check-in, Putting the free baggage allowance on the ticket, and Quoting the free baggage rules for a passenger prior to check-in. Processing will first determine baggage selection (carrier and baggage travel) which applies prior to processing Record S5 Sub Code Record. (Refer to Baggage Allowance and Charges Overview - Attachment A Baggage Selection.) Next, processing must use the carrier and baggage travel to process the Record S5 with value A and standard Sub Code 0DF. Once processing resolves to an applicable Record S5 Sub Code Services Record, processing will next attempt to resolve to an applicable Record S7 for the Record S5 Carrier, Sub Code 0DF, and Service Type A being processed. NOTE: For journeys to/from the US, the carrier whose rules apply must be a US DOT Carrier (must publish rules to/from the US). For journeys to/from Canada, the carriers must be a Canadian Transportation Agency (CTA) carrier (must publish rules to/from CA).Refer to Baggage Allowance and Charges Overview - Attachment A Baggage Selection If a match is made to the Record S7, then the unique Record S5 Carrier, Sub Code 0DF and Service Type A value combination is applicable for use. Processing must apply the data in the matched Record S7 to determine the free baggage allowance o Processing will apply the data in Record S7 and will not continue processing to another Record S7 for the same Carrier, Sub Code 0DF and Service Type A (unless otherwise specified below regarding Not Available/No Charge value D). o In order to apply allowance data, processing must use the data in the Baggage Free Pieces ( ), Baggage Weight (bytes ), Not Available/Charge (byte 388) and Text Table 196 (bytes ). o Systems may need access to the Record S5 sub code attributes which describe each bag type (e.g. BAG up to 50 lbs AND 62 li). The descriptions contain individual baggage attribute codes which will need to be translated into dimensions using the ATPCO Attribute Appendix. o Any checked baggage that is not permitted within the free allowance must be processed against Records S5 and S7 as a Prepaid and/or Baggage Charge (Types P and C, respectively). Processing must use the same Carrier and BT for processing Prepaid and Charges data as was used for Allowance. If a match is not made to the Record S7 for the Record S5 Carrier, Sub Code and Service Type value A, then processing will continue to another Record S7 for the same Carrier, Sub Code, and Service Type combination. If processing cannot match a Record S7 for the Carrier, Sub Code, and Service Type combination, then refer to Baggage Allowance and Charges Overview Section 2.2 Assumptions for an explanation of the no data/no match application. Page D.03.S7.021

23 Defer to Most Significant Marketing Carrier (MSC) Not Available/Charge (byte 288) value D (Applicable for journeys to/from the US and applicable for journeys to/from Canada) o If a match is made to the Record S7 (with the unique Record S5 Carrier, Sub Code 0DF and Service Type A value combination) and processing resolves to Not Available/Charge (byte 288) value D, then the Record S7 Carrier defers to the baggage rules of the most significant international marketing carrier (see Baggage Allowance and Charges Overview Appendix A Baggage Selection for an explanation of how to determine the most significant international carrier). If the most significant marketing carrier is different than the Record S7 carrier whose data is being interrogated, processing must defer the baggage rules to the most significant marketing carrier and re-interrogate the Record S5, attempting to match data for the MSC. The MSC s rules will apply for checked baggage Allowance, Pre-Paid Baggage and checked Baggage Charges (Service Types A, P and C). If the most significant marketing carrier is the same as the Record S7 carrier whose data is being interrogated, processing will treat this record as a no match and continue processing to the next Record S7 for the unique Record S5 Carrier, Sub Code 0DF, and Service Type A. The rules of the MSC only apply provided the MSC is specified in ATPCO s published list of US DOT Carriers (defined as carriers who file general rules tariffs to/from the US) for journeys to/from US or ATPCO s published list of Canadian Transportation Agency Carriers (defined as carriers who file general rules tariffs to/from Canada) for journeys to/from Canada. If the MSC is not specified in this list, then the rules of the first marketing carrier apply (Refer to Baggage Allowance and Charges Overview Attachment A Baggage Selection regarding how to identify carrier rules to apply) For journeys not to/from US or not to/from Canada, the value D has no meaning and processing will treat this record as a No match and continue processing to the next S7 for the unique Record S5 Carrier, Sub Code 0DF, and Service Type A. Defer to Most Significant Operating Carrier (MSC) Not Available/Charge (byte 288) value O (Not applicable for journeys to/from US or to/from Canada) o If a match is made to the Record S7 (with the unique Record S5 Carrier, Sub Code 0DF and Service Type A value combination) and processing resolves to Not Available/Charge (byte 288) value O, then the Record S7 Carrier defers to the baggage rules of the most significant international operating carrier (see Baggage Allowance and Charges Overview Appendix A Baggage Selection for an explanation of how to determine the most significant international carrier). If the most significant operating carrier is different than the Record S7 carrier whose data is being interrogated, processing must defer the baggage rules to the most significant operating carrier and re-interrogate the Record S5, Page D.03.S7.022

24 attempting to match data for the MSC. The MSC s rules will apply for checked baggage Allowance, Pre-Paid Baggage and checked Baggage Charges (Service Types A, P and C). If the most significant operating carrier is the same as the Record S7 carrier whose data is being interrogated, processing will treat this record as a no match and continue processing to the next Record S7 for the unique Record S5 Carrier, Sub Code 0DF, and Service Type A. For journeys to/from US or to/from Canada, the value O has no meaning and processing will treat this record as a No match and continue processing to the next S7 for the unique Record S5 Carrier, Sub Code 0DF, and Service Type A Any items that are identified as embargoed are not permitted as part of the passenger s allowance and not permitted for a charge. Page D.03.S7.023

25 Service Type B Carry-on Allowance Carry-on Allowance is identified by Service Type value B on the Record S5 Sub Code Record as well as the Record S7. Carry-on Baggage Allowance services define the baggage allowance that a passenger can carry-on for free. Baggage Allowance services are processed for business purposes including but not limited to the following: Displaying the free carry-on baggage allowance prior to passenger ticketing, Displaying the free carry-on baggage allowance at time of passenger check-in, Quoting the free carry-on baggage rules for a passenger prior to check-in. Processing will first determine baggage selection (carrier and baggage travel) which applies prior to processing Record S5 Sub Code Record. (For Carry-on, the carrier and baggage travel are always the operating carrier on each sector of the journey. Refer to Baggage Allowance and Charges Overview - Attachment A Baggage Selection.) Next, processing must use each carrier and sector on the journey to process the Record S5 with value B and standard Sub Code 0LN. Once processing resolves to an applicable Record S5 Sub Code Services Record, processing will next attempt to resolve to an applicable Record S7 for the Record S5 Carrier, Sub Code 0LN, and Service Type B being processed. If a match is made to the Record S7, then the unique Record S5 Carrier, Sub Code 0LN and Service Type B value combination is applicable for use. Processing must apply the data in the matched Record S7 to determine the free carry-on allowance o Processing will apply the data in Record S7 and will not continue processing to another Record S7 for the same Carrier, Sub Code 0LN and Service Type B. o In order to apply carry-on allowance data, processing must use the data in the Baggage Free Pieces ( ), Baggage Weight (bytes ), and Text Table 196 (bytes ). o Systems may need access to the Record S5 sub code attributes which describe each bag type (e.g. ABC is a bag up to 45 li). The descriptions contain individual baggage attribute codes which will need to be translated into dimensions using the ATPCO Attribute Appendix. o Any carry-on baggage that is not permitted within the free carry-on allowance must be processed against Records S5 and S7 as Baggage Charge (Type C) with Sub Group CY (Carry-on). Processing must use the same Carrier and BT (operating carrier per sector) for processing carry-on Charges data as was used for carry-on Allowance. If a match is not made to the Record S7 for the Record S5 Carrier, Sub Code and Service Type value B, then processing will continue to another Record S7 for the same Carrier, Sub Code, and Service Type combination. If processing cannot match a Record S7 for the Carrier, Sub Code, and Service Type combination, then refer to Baggage Allowance and Charges Overview Section 2.2 Assumptions for an explanation of the no data/no match application. Embargoes (Service Type E) do not apply to carry-on baggage. Page D.03.S7.024

26 Type E Embargoes Baggage Embargoes are identified by Service Type value E on the Record S5 Sub Code Record as well as the Record S7. Baggage Embargoes define the baggage that a passenger cannot check. Data is processed for business purposes including but not limited to the following: Displaying embargoes prior to passenger ticketing, Displaying embargoes at time of passenger check-in, Messaging embargoes between operational systems, and Quoting embargoes to a passenger prior to check-in. Quoting embargoes prior to purchase of prepaid baggage Processing will first determine baggage selection (carrier and baggage travel) which applies prior to processing Record S5 Sub Code Record. (For Embargoes, the carrier and baggage travel are always the operating carrier on each sector of the journey. Refer to Baggage Allowance and Charges Overview - Attachment A Baggage Selection.) Next, processing must use carrier and sector on the journey to process the Record S5 with Service Type E. Once processing resolves to an applicable Record S5 Sub Code Services Record, processing will next attempt to resolve to an applicable Record S7 for the Record S5 Carrier, Sub Code and Service Type E being processed. If a match is made to Record S7 for the Record S5 Carrier, Sub Code and Service Type value E, then processing must apply the data in the matched Record S7 to define the embargo. o When an embargo is identified on the checked portion, the item cannot be checked as free allowance or for a charge. o When an embargo is identified on a down line sector of the journey that is not on the checked portion, the passenger must be informed of the embargo. If a match is not made to the Record S7 for the Record S5 Carrier, Sub Code and Service Type value E, then processing will continue to another Record S7 for the same Carrier, Sub Code, and Service Type combination. If processing cannot match a Record S7 for the Carrier, Sub Code, and Service Type combination, then refer to Baggage Allowance and Charges Overview Section 2.2 Assumptions for an explanation of the no data/no match application. Items identified as embargoed are not permitted to be accommodated through (checked) Allowance, Pre-Paid, or (checked) Charges processing. Page D.03.S7.025

27 Type P Prepaid Baggage Charges Prepaid Baggage Charges are identified by Service Type value P on the Record S5 Sub Code Record as well as the Record S7. Pre- Paid Baggage defines baggage charges that can be purchased (applied) prior to passenger airport check-in. Data is processed for business purposes including but not limited to displaying any Pre-Paid baggage offers at passenger ticketing and/or prior to check-in. Processing must first determine the carrier and travel which applies prior to processing Record S5 Sub Code Record. Refer to Baggage Allowance and Charges Overview - Attachment A Baggage Selection which details how to determine possible pricing solutions for Baggage services including determining the carrier and baggage travel for which the baggage services apply. Next, processing must use the carrier and travel to process the Record S5 to attempt to resolve to the Baggage Allowance (Service Type A) and Sub Code 0DF as well as an offered pre-paid baggage services. Next, processing will attempt to resolve to an applicable Record S7 for the Record S5 Carrier, Sub Code 0DF and Service Type A to determine the free baggage allowance. Upon resolving to the free baggage allowance (including defer to marketing if applicable), processing will attempt to resolve to an applicable Record S7 for the Record S5 Carrier, Sub Code, Service Type P for the pre-paid baggage being offered. Prepaid will be interrogated for baggage that is not permitted under the free allowance. Refer to Section Baggage - for details about how to define excess that exceeds the free baggage allowance and how that excess must be used to match Record S7 for pre-paid baggage). Processing will attempt to match a Record S7 for each (there may be more than one) unique combination of Record S7 Carrier, Sub Code and Service Type P, based on the match fields identified in the previous section. If a match is made to the Record S7 for the Record S5 Carrier, Sub Code and Service Type value P, then the unique Record S5 Carrier, Sub Code and Service Type P value combination is applicable for use. Processing will apply the data in Record S7 and will not continue processing to another Record S7 for the same Carrier, Sub Code and Service Type P If a match is not made to the Record S7 for the Record S5 Carrier, Sub Code and Service Type value P, then processing will continue to another Record S7 for the same Carrier, Sub Code, and Service Type combination. If processing cannot match a Record S7 for the Carrier, Sub Code, and Service Type combination, then refer to Baggage Allowance and Charges Overview Section 2.2 Assumptions for an explanation of the no data/no match application. For the offering of Pre-Paid Baggage, the intent is that processing is the same as for Baggage Charges. Page D.03.S7.026

28 Any items that are identified as embargoed (Service Type E) are not permitted as prepaid. Associated to a Flight Data is always associated to a specific flight(s) on the passenger s ticket. For example, a pre-paid baggage offer of one excess piece is specifically tied to flights/travel on the ticket. Pre-Paid Baggage does not always have to be provided on the flight but does require a specific flight coupon in order to be able to apply the offer. The Prepaid Baggage must be associated to the ticket coupon prior to departure of the flight. The offer is applied after pricing is complete and/or at the same time as pricing and can be purchased before, at the same time, or after ticketing. They must be connected to specific travel on a ticket. An EMD associated document (or non-emd based on data in S5) will be used for these services. Pre-paid Baggage Redemption After Pre-Paid Baggage is purchased and an EMD (or MCO other miscellaneous document) is issued, the Pre-Paid Baggage must be redeemed at time of passenger check-in. Redeeming Pre-Paid Baggage is a process that accepts the pre-paid offer as a form of payment in exchange for the item being presented (Example 1 below). The item must be an exact match to the offer being presented. If not, the pre-paid offer is not accepted and airlines may choose to reissue/refund the pre-paid offer and customers may choose to use the resulting refund as a form of payment towards the applicable fee (Example 2 below). When additional items in excess exist above the pre-paid offer, the pre-paid offer is counted as an excess occurrence for assessing charges (Example 3 below). The carrier redeeming pre-paid baggage may not be the carrier that offered the pre-paid excess baggage (Example 4 below - carriers should code a Carrier/Flight Table on their pre-paid offerings to limit their offers to itineraries that contain carriers that will accept the offer they present to passengers). Example 1 Exact Redemption 1. Passenger is offered Pre-Paid Baggage of an excess piece 0GO - (note: systems must use the applicable steps required to determine the free baggage allowance and then determine applicable pre-paid offers specified in the Record S7 with Service Type P), 2. Passenger purchases Pre-Paid Baggage of an excess piece (EMD is issued associated to the flights), 3. Passenger checks-in with two pieces one 15 lbs and one 20 lbs, 4. System identifies the ticketed baggage allowance applicable to the passenger of 1 piece (Note: This must match the baggage allowance found in step 1 as processing keys off ticket date to ensure the contract of carriage. If there is any discrepancy between the determined baggage allowance and the ticketed baggage allowance, use the baggage allowance on the ticket), Page D.03.S7.027

29 5. System determines one excess piece, 6. System accepts pre-paid baggage as a form of payment in exchange for the excess piece that would normally be charged. 7. Processing proceeds to the applicable fulfillment process. NOTE: Any frequent flier bonus will add an additional bonus to the allowance if the passenger is a frequent flier and exceeds the allowance + the redeemed offer. Example 2 Inexact Redemption 1. Passenger is offered Pre-Paid Baggage of an excess piece 0GO bag up to 50 lbs - (note: systems must use the applicable steps required to determine the free baggage allowance and then determine applicable pre-paid offers specified in the Record S7 with Service Type P), 2. Passenger purchases Pre-Paid Baggage of an excess piece (EMD is issued associated to the flights), 3. Passenger checks-in with one 60 lb bag, 4. System identifies the ticketed baggage allowance applicable to the passenger of Nil (no free allowance). (Note: This must match the baggage allowance found in step 1 as processing keys off ticket date to ensure the contract of carriage. If there is any discrepancy between the determined baggage allowance and the ticketed baggage allowance, use the baggage allowance on the ticket), 5. System determines that one excess piece that is 60 lbs that does not match the sold offer of up to 50 lbs, The pre-paid offer is not accepted as a form of payment. 6. The system, based on airline rules for the offer, may choose to reissue/refund the pre-paid offer. Example 3 Additional Excess Above Pre-Paid Offer 1. Passenger is offered Pre-Paid Baggage of an excess piece 0GO bag up to 50 lbs - (note: systems must use the applicable steps required to determine the free baggage allowance and then determine applicable pre-paid offers specified in the Record S7 with Service Type P ), 2. Passenger purchases Pre-Paid Baggage of an excess piece (EMD is issued associated to the flights), 3. Passenger checks-in with one 28 lb bag and one 32 lb bag, 4. System identifies the ticketed baggage allowance applicable to the passenger of Nil (no free allowance). (Note: This must match the baggage allowance found in step 1 as processing keys off ticket date to ensure the contract of carriage. If there is any discrepancy between the determined baggage allowance and the ticketed baggage allowance, use the baggage allowance on the ticket), 5. System determines that there are two excess pieces. Page D.03.S7.028