sign in sign up
<<
Home , Baggage allowance, Checked baggage, First class (aviation), Premium economy class

DATA APPLICATION ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

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 Tariff Publishing Company All rights reserved.

DATA APPLICATION FOR AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Contents

1.0 OVERVIEW ...... 4

1.1 DATA REQUIREMENTS ...... 5 1.2 BASIC PROCESSING OVERVIEW ...... 6 2.0 DEFINITIONS AND ASSUMPTIONS ...... 7

2.1 DEFINITIONS ...... 7 2.2 ASSUMPTIONS ...... 7 3.0 DETAILED FIELD PROCESSING ...... 8 4.0 PROCESSING ...... 11

4.1 APPLICATION OF DATA FOR RECORD S5 ...... 14 4.1.1 Carrier/Vendor Code (bytes 3-5) ...... 15 4.1.2 Service Code (bytes 6-7) ...... 16 4.1.3 Sub Code (bytes 8-10) ...... 17 4.1.3.1 Baggage Sub Codes ...... 17 4.1.3.2 Generic Baggage Sub Codes ...... 18 4.1.3.3 Multiple Baggage Sub Codes ...... 19 4.1.4 Service Type (byte 21) ...... 21 4.1.5 Sub Code Table No. 163 (bytes 13 - 20) ...... 23 4.1.6 Maintenance / Ticket Dates – First/Last (bytes 30-35, 36-41) ...... 24 4.1.7 Industry/Carrier (byte 42) ...... 25 4.1.8 Attributes (bytes 43-52) ...... 27 4.1.8.1 Group (bytes 43-45) ...... 1 4.1.8.2 Sub Group (bytes 46-48) ...... 2 4.1.8.3 Descriptions 1 & 2 (bytes 49-50, 51-52) ...... 4 4.1.9 Concur (byte 55) ...... 6 4.1.10 RFIC (byte 56)...... 7 4.1.11 SSR Code (bytes 57 – 60) ...... 8 4.1.12 Display Category (bytes 81-82) ...... 9 4.1.13 SSIM Code (byte 84) ...... 10 4.1.14 EMD Type (byte 85) ...... 11 4.1.15 Booking (bytes 86-87) ...... 12 4.1.16 Commercial Name (bytes 88-117) ...... 13

Page E.03.S5.02 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.17 Text Table No. 196 (bytes 128-135) ...... 14 4.1.18 Picture Number (bytes 136-143) ...... 15 5.0 SEGMENT INDICATORS ...... 16 6.0 CODING CONVENTIONS ...... 17

Page E.03.S5.03 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

1.0 OVERVIEW

The Record S5 – Sub Code Services Record provides basic information about the baggage service in terms of who owns it, what it is and how it may be offered. It is validated against conditions defined in the Record S7 – Services Provisions Record to determine when it should be offered and at what price. This process requires a unique identification of every baggage service within a carrier’s data. To this end, every service is uniquely identified by the combination of a Carrier Code (industry standard alphanumeric carrier code), Service Type, and Sub Code (3 byte alphanumeric assigned by ATPCO or by the carrier). The carrier whose Record S5 applies is determined prior to S5 processing (refer to Baggage Allowance and Charges Overview – Attachment A – Baggage Selection).

The data in Record S5 is used for two purposes 1. Display - To display a list or catalog of offered services (e.g. to determine what services may be offered by a carrier); and 2. Pricing - To price a service(s) (note that the pricing process may result in the service being free, e.g. free baggage allowance)

Unless otherwise specified in this document, the processing logic is the same whether the Record S5 is being processed for display or pricing purposes. However, it is possible that all information may not be known at the time of display and processing will need to re- apply (re-price) the data in the record at the time of pricing.

Refer to the Baggage Allowance and Charges Data Application Overview document for a complete overview of Baggage processing, including, but not limited to, a thorough explanation regarding: • Determination of which carrier’s service to apply • Identification of the Baggage Travel (BT) on which the baggage service can be assessed • High-level processing overview of all Services Records

ATPCO assumes that any carrier (or service provider) utilizing Record S5 and all Services records will ensure that all legal requirements are met regarding any resulting fees.

Page E.03.S5.04 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

1.1 Data Requirements

In order to validate Record S5, it is essential to know the following:

• The carrier whose baggage rules apply • Date of passenger ticketing • Date of passenger travel • Type of service being queried (e.g. Service Types A, B, C, E, and/or P) • The type of baggage being checked as well as the weight and size dimensions of that baggage

Page E.03.S5.05 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

1.2 Basic Processing Overview Refer to Section 1.2 Basic Processing Overview in the Baggage Allowance and Charges Overview for a detailed illustration of baggage processing.

Page E.03.S5.06 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

2.0 DEFINITIONS AND ASSUMPTIONS

2.1 Definitions

Term Definition Carrier Airline whose Baggage Rules apply and whose Record S5 is being processed RFIC IATA Reason for Issuance Code. This is a code to specify why an EMD or other miscellaneous document was issued. SSR Special Service Request. For the purposes of Baggage Services, this is a code that must be used when messaging information pertaining to these services. RFISC ATPCO Reason for Issuance Sub Code. This is a code which uniquely identifies a service. This may be a standard industry ATPCO Reason for Issuance Sub Code.

Refer to Baggage Allowance and Charges Overview for additional definitions applicable to Baggage processing.

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.

The assumption is that baggage allowance and charges is applied per passenger.

Page E.03.S5.07 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

3.0 DETAILED FIELD PROCESSING

Byte Location Match / Definition / Processing Action Bytes 1-2 Key Match Indicates the Record Number for which the data is formatted. Record Type Bytes 3-5 Key Match Specifies the carrier providing the service. Carrier/Vendor Code NOTE: Vendor is not applicable for Baggage processing. Bytes 6-7 Key Match Specifies the ATPCO-assigned Service code applicable to the Sub Code identified Service Code in this record (always OC). Bytes 8-10 Key Match Specifies the code for the Sub Code identified in this record. This may be a Sub Code standard industry ATPCO RFISC (Reason for Issuance Sub Code). NOTE: The Sub Code may be used as match criteria for the Record S5 if the system is processing baggage data for a known service and Sub Code. Bytes 11-12 N/A Filler Bytes 13 – 20 Action Not applicable for Baggage processing. Sub Code Table No. 163 Byte 21 Key Specifies whether the Sub Code identified in this record is baggage allowance, Service Type Match/Action carry-on allowance, baggage embargoes, pre-paid baggage or baggage charges Bytes 22-29 N/A Filler Bytes 30-41 Match Specify that the data in this record applies for passenger tickets sold on/after the Maintenance/ Ticket Dates first ticket date and on/before the last ticket date. (First/Last) These dates are used by subscribers to perform database maintenance. Byte 42 Action Specifies whether the Sub Code identified in this record is industry-defined or Ind/Cxr carrier-defined. Byte 43-45 Action Specifies the high-level group applicable to the Sub Code identified in this record. Attributes – Group NOTE: The Group may be used as match criteria for the Record S5 if the system is processing Baggage Services data for a specific Group (e.g. for display purposes).

Page E.03.S5.08 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Byte Location Match / Definition / Processing Action Byte 46-48 Action Specifies the Sub Group (within the specified Group) applicable to the Sub Code Attributes – Sub Group identified in this record NOTE: The Sub Group may be used as match criteria for the Record S5 if the system is processing Baggage data for a specific Sub Group (e.g. for display purposes). Byte 49-50 Action Provides a specific description of the Sub Code identified in this record. Attributes – Description 1 NOTE: The Description(s) may be used as match criteria for the Record S5 if the system is processing Baggage Services data for a specific Description of a service (e.g. for display purposes). Byte 51-52 Action Provides an additional specific description of the Sub Code identified in this Attributes – Description 2 record. NOTE: The Description(s) may be used as match criteria for the Record S5 if the system is processing Baggage Services data for a specific Description of a service (e.g. for display purposes). Bytes 53-54 N/A Filler Byte 55 Action Not applicable for Baggage processing. Concur NOTE: This information is set automatically by ATPCO according to the type of service (based on data in the Service Type field byte 21). Byte 56 Action Specifies the IATA-defined Reason for Issuance Code (RFIC) applicable to the RFIC Electronic Miscellaneous Document (EMD) that will be issued for the Sub Code identified in this record. Bytes 57-60 Action Specifies the IATA-defined Special Service Request (SSR) code applicable to the SSR Code Sub Code identified in this record. Bytes 61-80 N/A Filler Bytes 81-82 Action Specifies when/where the service can be displayed. Display Category Byte 83 N/A Filler Byte 84 Match/Action Not applicable for Baggage processing. SSIM Code

Page E.03.S5.09 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Byte Location Match / Definition / Processing Action Byte 85 Action Specifies the type of Electronic Miscellaneous Document (EMD) that must be EMD Type issued for the Sub Code identified in this record. Bytes 86-87 Action Specifies how and if the Sub Code identified in this record must be booked. Booking Bytes 88-117 Action Specifies the Commercial Name associated to the Sub Code identified in this Commercial Name record. Bytes 118-127 N/A Filler Bytes 128-135 Action A table containing free form text associated to the Sub Code identified in this Text Table No. 196 record. Bytes 136-143 Action A number identifying a picture file associated to the Sub Code identified in this Picture Number record. Bytes 144-159 N/A Filler

Page E.03.S5.010 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.0 PROCESSING

When processing Baggage Services, processing will first identify the carrier whose baggage rules apply. Determination is based on processed detailed in the Baggage Allowance and Charges Overview – Attachment A Baggage Selection. Processing will attempt to match Record S5 data for the carrier whose rules apply based on the match fields identified in Section 3.0 and any additional qualifying data that may be known (e.g. Sub Code, Group, Sub Group, etc.). The relationship among all match fields is AND. All match criteria must be validated in order to match the record.

Only one applicable Record S5 will be in effect for each unique Carrier (bytes 3-5), Service Code (bytes 6-7), Sub Code (bytes 8-10), and Service Type (byte 21) combination. Once processing matches a record for a specific Carrier, Service Code, Sub Code, and Service Type value processing will not attempt to match another record for the same Carrier, Service Code, Sub Code, and Service Type combination. Record S5 data is not sequentially processed. Depending upon any known qualifying data (e.g. Sub Code, Group, Sub Group, Flight Related, Rule Buster, etc.), processing will attempt to match as many unique Service Code, Sub Code and Service Type combinations as possible for a single carrier (carrier whose rules apply). It is possible to match multiple Record S5s for different services (i.e. different combinations of Carrier, Service Code, Sub Code, and Service Type values).

Example 1: If attempting to process all Baggage Services for carrier XX, then processing will attempt to match all XX Record S5s with Service Code OC, Group BG, and with any Sub Code and Service Type value A, B, E, P, or C.

Example 2: Group BG. If attempting to process all Baggage Charges for carrier XX, processing will attempt to match all unique XX Record S5 Service Code and Sub Code combinations with Group BG and Service Type value C.

Page E.03.S5.011 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Example 3: Assume the following Record S5’s exist for carrier XX:

Sub Code Service Type Eff Date Disc Date Desc 1 Commercial Name 0DF A 02FEB11 999999 Blank Baggage Allowance 0FM C 01JAN11 31JAN11 32 - Up to UPTO70LB/32KG AND62LI/158LCM 70lb/32kg 0FM C 01FEB11 999999 32 - Up to UPTO70LB/32KG AND62LI/158LCM 70lb/32kg

0GO P 01JAN11 999999 23 - Up to UPTO50LB/23KG AND62LI/158LCM 50lb/23kg 0GO C 01JAN11 999999 23 - Up to UPTO50LB/23KG AND62LI/158LCM 50lb/23kg 0IN E 20DEC11 10JAN12 BX-Box Boxes

When pricing for carrier XX for a ticket issued on 15FEB11 to determine Baggage Allowance, Baggage Embargoes, Pre-Paid Baggage and Baggage Charges for a passenger with two suitcases that weigh 18 and 55 lbs respectively, processing resolves to the above Record S5 data determines the following records are applicable: • 0DF baggage allowance (Service Type value “A”) • 0FM baggage charges (Service Type value “C”) effective 01FEB11 • 0GO prepaid baggage services (Service Type value “P”) • 0GO baggage charges (Service Type value “C”) • 0IN baggage embargoes (Service Type “E”)

Data in Record S5 can be used for two purposes: 1) displaying offered services; and 2) pricing.

Displaying Offered Services: Separate from pricing, systems may query the Record S5 in order to determine which optional services are offered by a carrier. This information could then be used to display a choice of offered services to a customer. Displaying offered services based on Record S5 data merely provides information regarding what services the carrier may offer and does not provide data regarding availability or when or where the service may be offered (this would be specified in the Record S7). Data in Record S5 Display Category (bytes 81- 82) specifies when/where processing can display the service associated to the Sub Code identified in the record (i.e. at the time of itinerary pricing, in the online store, and/or as a special service).

Page E.03.S5.012 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

It is possible that at the time of display, processing will not have all information necessary to verify a match to the Record S5. In this case, processing may conditionally match Record S5 data until such time that all information is known. For example, processing may be attempting to ascertain all possible baggage services that might be offered by a carrier and may not have any flight information available. However, at the time of pricing, processing must process the Record S5 in its entirety to ensure the data is fully matched and passed.

Pricing Offered Services: At the time of pricing, processing must meet the criteria in all match fields and pass all requirements in the Record S5 in order to price the Sub Code.

Record S5 Data Used in Later Baggage Services Processing Steps Once an applicable Record S5 is matched and passed, the Record S5 Carrier, Sub Code, Service Type, Group, and Sub Group values will be used for further Baggage Services processing, specifically for Record S7 – Services Provisions Record processing as follows: • Processing will attempt to match Record S7 based on the Record S5: o Carrier; and o Sub Code; and o Service Type value

Page E.03.S5.013 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1 Application of Data for Record S5 This section provides a detailed explanation of the data application for each field in Record S5.

Page E.03.S5.014 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.1 Carrier/Vendor Code (bytes 3-5)

This field specifies the carrier providing the service. Data in this field matches against the carrier whose rules apply as determined based on the result of the Baggage Selection process (defined in Baggage Allowance and Charges Overview – Attachment A).

For Baggage processing, edits only permit the standard industry alpha-numeric airline designator values in this field (YY and vendor codes are not valid values in this field). This field will not contain the airline “stock” codes. (For example, for American , the value in this field will be AA and will not be 001.)

Data in this field is used in later processing steps when matching applicable Record S7 – Services Provisions Record data.

Page E.03.S5.015 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.2 Service Code (bytes 6-7)

This field specifies the ATPCO-assigned Service Code applicable to the Sub Code being priced and is a high-level identification of the type of service specified in the record. This field will always be value OC. Processing will match the Record S5 with value OC (provided a match is also made to all other match fields).

Page E.03.S5.016 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.3 Sub Code (bytes 8-10)

The Sub Code is either an industry-defined or carrier-defined code (as specified by Industry/Carrier byte 42) identifying a specific type of service. Industry-defined codes are available for all carriers to use and have standard Attributes (standard definition) defined in Record S5 bytes 43-52. Carrier-defined codes are available for a specific carrier only and are defined by that carrier. Data in this field is used in later processing steps when matching applicable Record S7 Services Provisions Record data.

All industry-defined Sub Codes are maintained by ATPCO (note: these may be referred to in the industry as RFISC’s – Reason For Issuance Sub Codes). Carrier-defined Sub Codes are maintained by each carrier utilizing the code. ATPCO will associate every Sub Code (both ATPCO-defined and carrier-defined) with applicable Attributes data (as specified by the Attributes fields in bytes 43-52).

The Sub Code can be processed as match criteria when interrogating the Record S5 in order to identify the baggage type and applicable attributes for a specific sub code. For example, after processing Records S5 and S7 for Allowance (Service Type A) and Sub Code 0DF, processing will read the formatted text in Record S7 Text Table 196 to identify the sub codes permitted within the free allowance. Those sub codes can be matched to Record S5 in order to identify the baggage type and applicable Attributes (weight and dimensions).

4.1.3.1 Baggage Sub Codes Sub Codes for Baggage Allowance (including checked and carry-on allowance), Baggage Embargoes, Pre-Paid Baggage and Baggage Charges (including checked and carry-on) (Service Types A, B, E, P and C) may be generic or specific bag codes.

Specific bag codes represent the types of bag that a carrier offers to be checked or carry-on. For example, a carrier may offer a regular bag up to 50 lbs and 62 li (sub code = 0GO) and a heavy bag up to 70 lbs and 62 li (sub code = 0FM). Each of these baggage offerings would be represented with a 3 alphanumeric sub code.

Refer to the following section for an explanation of generic bag codes.

Page E.03.S5.017 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.3.2 Generic Baggage Sub Codes ATPCO has defined the following generic baggage codes:

0DF: Sub Code 0DF is the standard sub code to indicate allowance. A carrier must specify a sub code 0DF in order to “offer” a checked baggage allowance. Further, the only sub code permitted in the S5 for Service Type A is a 0DF sub code. Systems can query for sub code 0DF in the S5 to determine whether checked baggage allowance is being offered (i.e. whether a carrier has any checked baggage allowance data).

0DG: Sub Code 0DG is the standard sub code that defines weight system baggage charges. Carriers on the weight system define a charge “per kilo” and “based on a percent of a per kilo” for a passenger’s combined baggage (all bags for a given passenger). To represent this “combined baggage” ATPCO created a generic sub code that can be offered in the S5 to handle weight system charges of this nature.

0LN: Sub Code 0LN is the standard sub code to indicate carry-on baggage allowance. A carrier must specify a sub code 0LN in order to “offer” carry-on baggage allowance. Further, the only sub code permitted in the S5 for Service Type B and Sub Group CY is a 0LN sub code. Systems can query for sub code 0LN in the S5 to determine whether carry-on baggage allowance is being offered (i.e. whether a carrier has any carry-on baggage allowance data).

0ME: Sub Code 0ME is used for Embargoes in order to indicate no excess baggage is permitted. A carrier must specify a sub code 0ME in order to embargo any excess baggage. Edits only permit sub code 0ME when Service Type is value E.

If the only S5 records for a carrier are a 0DF and 0DG, then there is no restriction on the type of checked bags. If the S5 for a carrier has any code in addition to 0DF and/or 0DG, then only these types of bags are permitted to be checked.

Page E.03.S5.018 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.3.3 Multiple Baggage Sub Codes When multiple baggage sub codes exist with Service Type C that can be used to determine if the passenger is in excess (in other words, the passenger’s bag validates against multiple Sub Codes), all sub codes are applicable (standard non special item sub codes are identified with group value BG and sub group value Blank). Processing shall interrogate the Record S7 with all sub codes and select the least expensive charge.

Example 1 Scenario: Passenger is checking two 10 kg bags. 23 is translated to “up to 23kgs” by the Optional Services Attribute Appendix 32 is translate to “up to 32kgs” by the Attribute Appendix Record S5 data: Carrier Sub Code Ind/Cxr Attributes (bytes 43-52) Commercial Name (bytes 88-117) Group Sub Group Desc 1 Desc 2 XX 0GO C BG Blank 23 6U UPTO50LB/23KG AND62LI/158LCM

XX 0FM C BG Blank 32 6U UPTO70LB/32KG AND62LI/158LCM

S7 Baggage Allowance Carrier Sub Code Service Type Free Pieces Baggage Weight/Unit Text Table 196 (byte 21) (bytes 269-270) (bytes 275-279) (bytes 368-375) XX 0DF A 02 Blank Blank //02/0GO Result: Because the S7 formatted text specifies 0GO, processing selects the 0GO for each 10kg bag.

Page E.03.S5.019 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Example 2 Scenario: Passenger is checking two 10 kg bags.

Record S5 data: Carrier Sub Code Ind/Cxr Attributes (bytes 43-52) Commercial Name (bytes 88-117) Group Sub Group Desc 1 Desc 2 XX 0GO C BG Blank 23 6U UPTO50LB/23KG AND62LI/158LCM XX 0FM C BG Blank 02 6U UPTO70LB/32KG AND62LI/158LCM

S7 Baggage Allowance Carrier Sub Code Service Type Free Pieces Baggage Weight/Unit Text Table 196 (byte 21) (bytes 269-270) (bytes 275-279) (bytes 368-375) XX 0DF A 01 Blank Blank //01/0GO Result: Processing selects the 0GO for each 10kg bag to look for a charge. Since there is one bag in excess, processing looks up a charge for the 0GO and the 0FM and returns the best result for the passenger. NOTE: For determining standard excess baggage rates, processing may select sub codes with Group = BG and Sub Group = Blank.

When bytes 8-10 contain baggage allowance specific sub code 0DF, edits require Service Type (byte 21) must be A.

Page E.03.S5.020 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.4 Service Type (byte 21)

This field specifies the type of service applicable to the Sub Code identified in bytes 8-10. Following is an explanation of applicable values:

Value A: Baggage Allowance (checked). The sub code identified in bytes 8-10 will always be 0DF. This sub code represents checked baggage allowance.

An EMD shall not be issued for Baggage Allowance services.

When byte 21 is value A, EMD type (byte 85) must be value 4. When byte 21 is value A, edits require Sub Code (bytes 8-10) must contain baggage allowance specific sub code 0DF. When byte 21 is value A, Booking (bytes 86-87) must be value Blank.

Value B: Carry-on Allowance. The sub code identified in bytes 8-10 will always be 0LN. This sub code represents carry-on baggage allowance.

An EMD shall not be issued for Carry-on Allowance services.

When byte 21 is value B, EMD type (byte 85) must be value 4. When byte 21 is value B, edits require Sub Code (bytes 8-10) must contain carry-on allowance specific sub code 0LN. When byte 21 is value B, Booking (bytes 86-87) must be value Blank.

Value C: Baggage Charges (checked or carry-on). The sub code identified in bytes 8-10 identifies a type of bag for processing baggage charges as well as the Allowance Record S7 formatted text (represented bags permitted within the allowance).

When byte 21 is value C, EMD type (byte 85) must be value 2 or 4.

Value E: Embargoes. The sub code identified in bytes 8-10 identifies a type of bag or a generic bag for embargo processing.

When byte 21 is value E, EMD type (byte 85) must be value 4.

Page E.03.S5.021 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Value P: Pre-Paid Baggage. The sub code identified in bytes 8-10 identifies a type of bag for processing prepaid baggage charges as well as the Allowance Record S7 formatted text (represented bags permitted within the allowance). Pre-Paid Baggage sold as merchandise or not associated to a specific flight(s) on a passenger’s itinerary is sold as an Optional Service (see Optional Services S5 Data Application – Service Type value M)

When byte 21 is value P, EMD type (byte 85) must be value 2 or 4. When byte value is P, Group (bytes 43 – 45) must be values BG (Baggage) or PT (Pets).

Whether or not a Sub Code is identified as, baggage allowance, carry-on baggage, embargo, pre-paid baggage and/or baggage charges is at the discretion of the Record S5 carrier.

• It is possible that the same service might be identified as flight related*, ticket related*, merchandise*, pre-paid baggage, embargo and/or baggage charges and may have different conditions (e.g. a different fee) depending upon whether or not it is bought in conjunction with a ticket. In this case, the same Sub Code will be utilized to identify the service and multiple Record S5s will be created: one for the Sub Code as a flight related service (byte 21 value F); one for the same Sub Code as a ticket related service (byte 21 value T); and another for the same Sub Code but as a merchandise service (byte 21 value M); and another for the same Sub Code but as a Baggage Charge (byte 21 value C); and another for the same Sub Code but as Pre- Paid Baggage Service (byte 21 value P); and another for the same Sub Code but as an Embargo (byte 21 value E).

• It is not possible to define the same industry Sub Code as baggage allowance (checked or carry-on) and flight*, ticket*, merchandise*, embargo, pre-paid baggage and/or baggage charge (checked or carry-on) because baggage allowance services are uniquely identified based on Service Type value A and Sub Code 0DF or Service Type value B and Sub Code 0LN. Likewise, it is not possible for a carrier to define a Sub Code as baggage allowance.

* Flight (Service Type F), Ticket (T) and Merchandise (M) related items are defined with the Optional Services Data Application

Data in this field is used in later Baggage Services processing steps when matching applicable Record S7 – Services Provisions Record data.

Page E.03.S5.022 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.5 Sub Code Table No. 163 (bytes 13 - 20)

Data in this field is not applicable to Baggage Processing. Edits require this field be value 00000000.

Page E.03.S5.023 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.6 Maintenance / Ticket Dates – First/Last (bytes 30-35, 36-41)

These fields specify the First and/or Last Ticket Dates for the record. Processing will use the ticket issue date (ticket issue date or reissue date if the passenger ticket was issued) for the current passenger ticket in hand to validate against these fields. • If the passenger ticket issue date is on/after the First Ticket Date and on/before the Last Ticket Date, then processing matches the record (provided a match is also made to all other match fields). • If the passenger ticket issue date is not on/after the First Ticket Date and on/before the Last Ticket Date, then processing no matches the record and continues to the next record.

A date will always be present in the First Date field (bytes 30-35). The Last Date field (bytes 36-41) may contain a specific date or may contain 999999 signifying there is no restriction on the Last date the record may be displayed/sold/ticketed (subject to the remaining data within the Optional Services records). The Record S5 First/Last Dates may be any date on or after the ATPCO transmission date. Same day effectiveness (defined as a First date that is the same day as the ATPCO transmission date) and future effectiveness (defined as a First date that is later than the ATPCO transmission date) are permitted.

These fields are also used for subscriber database maintenance (similar to Effective and Discontinue Dates in ATPCO Automated Rules records). A change indicator (an indicator that advises subscribers whether or not a record being transmitted in a change file as “new” versus a “change” to an existing record) is not provided on the Record S5; therefore, subscribers must determine if records received are changed or new (based on whether or not there is a match to an existing record in the database based on the key match criteria, as defined in Section 3.0 of this document). For changed records, subscribers must modify the First/Last Dates on existing records as applicable. Refer to the Services Overview document for a detailed explanation of date maintenance.

Page E.03.S5.024 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.7 Industry/Carrier (byte 42)

This field specifies whether the Sub Code identified in this record is industry or carrier-defined. Following is an explanation of applicable values:

Value I: Industry. The Sub Code identified in this record is industry-defined and available for use by all carriers. All Attributes defined in Record S5 bytes 43-52 remain constant (cannot be changed) for all carriers utilizing this Sub Code.

Any bag type that can be used for interline travel must be defined as an Industry Sub Code.

Example Record S5 data: Sub Code Ind/Cxr Attributes (bytes 43-52) Commercial Name (bytes 88-117) Group Sub Group Desc 1 Desc 2 0GO I BG Blank 23 6U UPTO50LB/23KG AND62LI/158LCM 0DF I BG Blank Blank Blank Baggage Allowance

0GO and 0DF are industry-defined Sub Codes. They can be utilized by any carrier and their Attributes will always remain the same. 0GO will always refer to a specific bag to which an embargo, pre-paid baggage offer or baggage charge applies. 0DF will always be Baggage Allowance. (Note, refer to the Sub Code Attributes Appendix for an explanation of applicable Attributes values).

Value C: Carrier. The Sub Code identified in this record is carrier-defined. The Attributes defined in Record S5 bytes 43-52 are only applicable to this unique Carrier and Sub Code combination. It is possible another carrier may utilize this same Sub Code but identify different Attributes to define the Sub Code.

Baggage Allowance services (Service Type A and B) will never be carrier-defined. They will always be industry- defined with Sub Code 0DF or 0LN, respectively.

Page E.03.S5.025 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Embargoes (Service Type E), Prepaid Baggage (Service Type P), and Baggage Charges (Service Type C) may be industry-defined OR carrier-defined. However, any of these services identified by a carrier-defined sub code only apply for online travel. For interline travel, carrier-defined sub codes have no application.

Example 01 is translated to “up to 32kgs” by the Optional Services Attribute Appendix Record S5 data: 02 is translate to “up to 45kgs” by the Attribute Appendix Carrier Sub Code Ind/Cxr Attributes (bytes 43-52) Commercial Name (bytes 88-117) Group Sub Group Desc 1 Desc 2 XX XYZ C BG Blank 23 Blank XX Heavy Bag ZZ XYZ C BG Blank 32 Blank ZZ Heavy Bag XYZ is a carrier-defined Sub Code. The attributes (definition) applicable to XYZ may vary by carrier in this example: • For carrier XX on online travel, XYZ represents a heavy bag (up to 32kg). These attributes shall remain constant for XYZ when used by carrier XX. • For carrier ZZ on online travel, XYZ represents a heavy bag (up to 45kg). These attributes shall remain constant for XYZ when used by carrier ZZ.

The same Sub Code cannot be both industry and carrier-defined. Once a Sub Code is identified as industry defined, it can only be industry-defined. Likewise, once a Sub Code is identified as carrier-defined, it can only be carrier-defined.

Page E.03.S5.026 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.8 Attributes (bytes 43-52) The elements that make up the Sub Code identification are: Carrier Code, Sub Code, and Attributes. Each Sub Code is identified in the Record S5 as carrier or industry defined (Cxr/Ind byte 42) and uniquely classified based on data in one or more of the following Attributes fields: • Group (bytes 43-45) • Sub Group (bytes 46-48) • Description (bytes 49-50, 51-52)

For Industry Defined Sub Codes (Record S5 Ind/Cxr byte 42 value I), ATPCO will identify the attributes. All carriers can use the Industry Sub Codes, but edits prohibit any change to the Attributes.

For Carrier Defined Sub Codes (Record S5 Ind/Cxr byte 42 value C) carriers will identify the attributes at the time of initial creation of the Sub Code. The Sub Code and its associated Attributes is only applicable to the carrier that “creates” the Sub Code. Once the Sub Code is created, edits prohibit that carrier from changing the Attributes on the Record S5. For carrier-defined codes, it is important to realize that the data in the Carrier and Sub Code fields are the unique identifiers for the service. It is possible that the same Sub Code will have different Attributes for different carriers.

For the purposes of Baggage Allowance, Embargoes Pre-Paid Baggage and Baggage Charges processing, systems must process the Sub Code Attributes. At time of passenger ticketing, systems may choose to process the attributes to display the free baggage allowance (see Example on the following page).

Page E.03.S5.027 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

23 is translated to “up to 50lbs” by the Optional Services Attribute Appendix Example 32 is translate to “up to 62lis” by the Attribute Appendix Record S5 data: Carrier Sub Code Ind/Cxr Attributes (bytes 43-52) Commercial Name (bytes 88-117) Group Sub Group Desc 1 Desc 2 ZZ 0GO C BG Blank 23 6U UPTO50LB/23KG AND62LI/158LCM ZZ 0DF A BG Blank Blank Blank Free Baggage Allowance

Record S7 data: Carrier Sub Code Service Type (byte 21) Baggage Allowance Free Pieces Text Table 196 (bytes 368-375) (bytes 269-270) ZZ 0DF A 02 //02/0GO

Processing finds the standard baggage allowance sub code in the S5 (0DF). Then, the system begins baggage allowance processing with Service Type “A” (Allowance) in the S7, where it matches 0DF to an S7 Record that specifies a free baggage allowance of 2 pieces within which 02 0GO’s are permitted. Processing may choose to go back to the S7 to display/determine that the free baggage allowance for a single 0GO is up to 50 lbs and 62 li.

The chart on the following page illustrates the hierarchical relationship among the Attributes fields. For each Attributes field (Group, Sub Group, Descriptions), refer to the Sub Code Attributes Appendix for a current list of up-to-date Attributes values.

Each of the Attributes fields is further described in the sections that follow.

Page E.03.S5.028 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

OPTIONAL SERVICES SUB CODE ATTRIBUTES GROUP SUB GROUP DESCRIPTION ****This flow chart is provided for illustrative purposes in order to show the relationship among Group, Sub Group, and Descriptions. It does not represent a comprehensive list of Attributes. Refer to Sub Code Attributes Appendix for a current list of up-to-date Attributes values***

05 = Up to 5 kg 10 = Up to 10 kg 15 = Up to 15 kg 20 = Up to 20 kg AD = Adult AI = Aisle AL = Alcoholic AR = Arrival BC = BI = Bicycle BX = Box CE = Center CH = Child CL = Cold CO = Continental DI = Diabetic CT = Container DP = Departure CY = Carry-on EC = PP = Pre paid excess EL = Elite SP = Sporting Equipment EX = Executive HT = Hot FC = FF = Flow Rate – Fast BG = Baggage FM = Flow Rate – Medium FS = Flow Rate – Slow KN = Kennel KO = Kosher LG = Large MD = Medium NA = Non-alcoholic S1 = Shirts S2 = Sweatshirt S3 = Polo shirt S4 = T-shirt S5 = Shorts S6 = Pants S7 = Hats S8 = Jackets S9 = Toy Airplane SA = Stuffed Animal SJ = Jewelry PC = PR = Premium SM = Small TR = Transit VG = Vegetarian WD = Window XL = Extra Large

Page E.03.S5.029 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.8.1 Group (bytes 43-45)

Optional Services are organized into groups which are established by ATPCO as industry standard and represented by a 3 byte alphanumeric. They are used to identify like types of services for processing, display, and selection. Groups are defined by the service attributes irrespective of any conditions that must be met for a service to be offered. All groups will be created by ATPCO as required by the industry. Every optional service must have a Sub Code and every Sub Code (whether industry or carrier-defined) must be associated to a Group.

Data in the Group field can be used to filter and/or group services for search and/or display purposes.

NOTE: There will be no duplication of codes between the Group (bytes 43 – 45) and the Sub Group fields (bytes 46 – 48). For example if BG (Baggage) is in use as a Group, it may not be filed as a Sub Group. Subscribers will only receive 3 byte Group or Sub Group codes after all available 2 byte codes are in use. Group and Sub Group codes will initially consist of the first two bytes and a blank in the third byte.

Refer to the Sub Code Attributes Appendix for a list of valid Group Codes.

Page D.03.S5.01 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.8.2 Sub Group (bytes 46-48)

Within each Group, specific Sub Groups may be identified to further describe the Sub Code identified in the Record S5. Like Groups, Sub Groups are established by ATPCO as industry standard and represented by a 3 byte alphanumeric. Edits exist to link the Sub Groups to their associated Group.

Example: Group Code = BG (Baggage)

Within Group Code BG are the following Sub Groups: AD (Assistive Devices) CT (Container) CY (Carry-on) IN (Infant Baggage) MI (Musical Instruments) PP (Pre paid excess baggage) SI (Specialty Item) SP (Sporting Equipment) XS (Baggage Excess)

Each of these Sub Groups are only permitted to be specified in Record S5 when the Group Code is BG.

Record S5 requires that each Sub Code be identified by a specific Group Code. However, the Sub Code does not have to be defined by a specific Sub Group. When Sub Group is blank, then the specified Sub Code applies for all Sub Groups applicable within the specified Group (subject to data in the Description fields bytes 49-52).

Example: For Sub Code BCD, assume: Group Code = BG (Baggage) Sub Group = Blank

In this case, Sub Code BCD applies to all Baggage Services, subject to the data in the Description fields. Note: Baggage Services can be distinguished as either carry-on (CY) or applicable to all checked baggage services (Blank) which includes pre-paid OR baggage allowance OR baggage charges.

Page D.03.S5.02 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Carry-on bags must be identified by Sub Group CY (Carry-on) and Service Type B or C. If the Sub Group is not CY, then the Sub Code represents checked baggage. For example: Sub Code 123 with Service Type C – if the Group is not CY then the Sub Code represents checked baggage.

Data in the Sub Group field can be used to filter and/or group services for search and/or display purposes.

NOTE: There will be no duplication of codes between the Group (bytes 43 – 45) and the Sub Group fields (bytes 46 – 48). For example if BG (Baggage) is in use as a Group, it may not be filed as a Sub Group. Subscribers will only receive 3 byte Group or Sub Group codes after all available 2 byte codes are in use. Group and Sub Group codes will initially consist of the first two bytes and a blank in the third byte.

Refer to the Sub Code Attributes Appendix for a list of valid Sub Groups and their associated Group.

Page D.03.S5.03 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.8.3 Descriptions 1 & 2 (bytes 49-50, 51-52)

The Group and Sub Group may be further defined by up to two Descriptions. Each Description is a 2 byte alphanumeric established by ATPCO as industry standard. All Description codes are valid for use with all Group and Sub Groups.

When data is present in both the Group and Sub Group fields, then the Descriptions further define the Sub Group (within the Group). When data is present in Group and Sub Group is Blank, then the Descriptions further define the Group.

For the purposes of baggage, Descriptions 1 and 2 are used to define the applicable weight and size dimensions for the baggage being checked. The type of bag (e.g. Sporting Equipment) may be expressed via the description attributes.

Example: Group Code = BG (Baggage) Sub Group = Blank Description 1 = 23- up to 23kgs/50 lbs Description 2 = 6U – 62li/158lcm

Result: The sub code identified in the above record is defined as any BAG up to 23kgs/50 lbs and 62li/158licm.

Data in the Description Fields share an AND relationship. Both Descriptions are applicable to the Group and/or Sub Group.

Example: Group Code: BG (Baggage) Sub Group: Blank Description 1: 23 - up to 23kgs/50 lbs Description 2: 6U - up to /62 li/ 158 lcm

Result: The Sub Code identified in the above record is defined as a bag up to 23kgs/ 50 lbs AND up to 62 li/158 lcm .

The application/definition is the same if the Description is reversed – i.e. Description 1 = up to 62 li/ 158 lcm and Description 2 = up to 23kgs/ 50 lbs.

Page D.03.S5.04 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

Example: Group Code: BG (Baggage) Sub Group: Blank Description 1: SP - Sporting Equipment Description 2: 23- up to 23 kgs / 50 lbs

Result: The Sub Code identified in the above record is defined as sporting equipment up to 23 kgs / 50 lbs The application/definition is the same if the Description is reversed – i.e. Description 1 = up to 23 kg / 50 lbs and Description 2 = sporting equipment.

There is no hierarchical application between Description 1 and Description 2. Each Description field has equal stature. The application is the same if the values in Description 1 and 2 are reversed or not.

Example: Group Code = BG (Baggage) Sub Group = Blank Description 1 = 25 (Up to 55lb/25kg) Description 2 = 6B (Up to 80 li/203 lcm)

VS.

Group Code = BG (Baggage) Sub Group = Blank Description 1 = 6B (Up to 80 li/203 lcm) Description 2 = 25 (Up to 55lb/25kg)

Result: There is no difference in the two records above. The Sub Code identified in each of the above records is defined as a bag up to 55lb/25kg and up to 80 li/203 lcm

Data in the Description fields can be used to filter and/or group services for search and/or display purposes.

Refer to the Sub Code Attributes Appendix for a list of valid Description codes.

Page D.03.S5.05 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.9 Concur (byte 55)

This field has no application for Baggage processing. The carrier whose rules apply is defined within Baggage Allowance and Charges Data Application Overview – Attachment A - Baggage Selection.

Edits require this field always be set to value X, as follows:

Value X: Concurrence is not required. Processing will not check any carrier’s Record S6

Page D.03.S5.06 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.10 RFIC (byte 56)

The design of the EMD (Electronic Miscellaneous Document) includes a one byte field to define the IATA Reason for Issuance Code (RFIC). Data in this field specifies the RFIC for the EMD being issued for the Sub Code identified in this record.

The RFIC codes in the Services product are approved by the IATA Joint Passenger Services Resolution (JPSC) meeting.

NOTE: Pricing systems may allow the use of RFIC with other ticketing methods, such as MCO, if appropriate.

The following chart provides guidance for assigning the RFIC according to the type of Group Code used for the Sub Code.

Code Group Type A Air transportation Any type of group that is for the actual transportation of the passenger (such as Upgrade) but not a service provided on the plane (such as meals). B Surface Transportation /Non Any type of group that is used for ground transportation or non Air Services air services (such as parking or an electric cart). C Baggage Any type of group that is considered “baggage,” such as Prepaid Baggage or Pets (pets are part of being transported). D Financial Impact Any type of group that has to do with financial protection of the trip, such as Travel Services. E Services Any type of group that is for services specifically provided at the airport not covered by another group, such as Lounge or Unaccompanied Minor. F Merchandise Any type of group that is not a flight service but can be purchased. G Inflight Services Any type of group that is used for services on the flight, such as in-flight entertainment or meals. I Individual Airline Use Any type of group that is not supported by another RFIC

Page D.03.S5.07 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.11 SSR Code (bytes 57 – 60)

This field specifies an IATA-defined Special Service Request (SSR) code associated to the Sub Code in bytes 8-10. When pricing the Sub Code specified in the record, this SSR code must be used in all messaging relative to the service. (Note, the Booking field in bytes 86-87 will specify whether an SSR is the required booking method.)

Page D.03.S5.08 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.12 Display Category (bytes 81-82)

Data in this field specifies that the Sub Code identified in this record must be displayed at the time of itinerary pricing, in the store, or as a special service. Following is an explanation of applicable values:

Value 01: With Itinerary Pricing. The Sub Code identified in this record must be displayed at the time of itinerary pricing when applicable. The service can be displayed at other places and times but at a minimum it must be displayed with itinerary pricing.

Value 02: Store. The Sub Code identified in this record must be displayed in the store when applicable.

Value 03: Special Service. The Sub Code identified in this record must be displayed as a special service when applicable.

Value Blank: No restrictions. The Sub Code identified in this record does not have to be in any specific display.

Page D.03.S5.09 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.13 SSIM Code (byte 84)

This field is not applicable for Baggage processing. Edits require this field be value Blank.

Page D.03.S5.010 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.14 EMD Type (byte 85)

This field identifies the type of Electronic Miscellaneous Document (EMD) or other document that must be issued for the Sub Code identified in this record. Following is an explanation of applicable values:

Value 2: Associated to a flight coupon of a ticket. When EMD Type (byte 85) is value 2, edits require that Service Type (byte 21) be value C or P.

Value 4: Other than EMD. The subscriber must have received instructions from the Record S5 owning carrier regarding how to document the service. • If the subscriber does not have instructions from the Record S5 owning carrier, then the subscriber will not display, price or sell the service identified in the Record S5. If the subscriber has received instructions from the Record S5 owning carrier, then the subscriber can display and price the service identified in the Record S5.

EMD Type (byte 85) must be value 4 when Service Type (byte 21) is value A, B, or E.

Values 1, 3, and 5 are not applicable to Baggage Processing, and edits prevent their use.

Refer to the Data Application – ATPCO Optional Services – Reservations, Ticketing, Reporting, Accounting and Settlement document for information on applying these values.

Page D.03.S5.011 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.15 Booking (bytes 86-87)

This field specifies how and if the Sub Code identified in this record must be booked. Following is an explanation of applicable values:

Value 01: SSR. The service identified by the Sub Code in this record must be booked via SSR messaging.

Value 02: Auxiliary Segment. The service identified by the Sub Code in this record may be booked via an auxiliary segment.

Value 03: Available for Display and/or Pricing. Contact Carrier for booking method. The service identified by the Sub Code in this record is available for display and/or pricing. The carrier must be contacted for the applicable booking details.

Value 04: No Booking Required. The service identified by the Sub Code in this record is available for display and/or pricing. There is no booking required for the specified service.

Value 05: NOT applicable to Baggage Processing, and edits prevent the use of this value.

Value Blank: No restrictions. There is no specific booking requirement.

Edits require that Booking must be Blank with Service Types A, B, and E.

Page D.03.S5.012 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.16 Commercial Name (bytes 88-117)

This field identifies any Commercial Name associated to the Sub Code specified in this record. Data in the Commercial Name has no automated application for the purposes of pricing Baggage Services. It is possible that subscribers may use data in this field for display and/or customer disclosure.

Page D.03.S5.013 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.17 Text Table No. 196 (bytes 128-135)

Data in this Table is provided for text purposes only and has no impact on automated processing.

When this field is value 00000000, there is no text associated to the Sub Code specified in this record.

Page D.03.S5.014 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

4.1.18 Picture Number (bytes 136-143)

Data in the Picture file identifies any picture(s) associated to the Sub Code specified in this record. This field has no automated application for the purposes of pricing Baggage Services. It is possible that subscribers may use data in this field for display and/or customer disclosure.

When this field is value 00000000, there is no picture associated to the Sub Code specified in this record.

NOTE: Upon initial implementation, value 00000000 is the only acceptable value in this field. A future development phase may include the ability to provide a picture.

Page D.03.S5.015 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

5.0 TRAVEL SEGMENT INDICATORS Travel Segment Indicators (TSIs) are not applicable in Record S5.

Page D.03.S5.016 Revised May 2012

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES SUB CODE SERVICES RECORD S5

6.0 CODING CONVENTIONS

Not applicable.

Page D.03.S5.017 Revised May 2012