Baggage

BAGGAGE TRIP (BT)

• CHECKED PORTIONS OF TRAVEL / STOPOVER - for the purposes of determining checked point, defined as an arrival at a ticket point (including fare break points) that is scheduled to depart later than 24 hours (4 hours for US/CA domestic) after the arrival time (local time).

• ASSESS THE BT DEPENDING ON THE ITINERARY

  1. Wholly domestic itineraries - BTs will be based on stopover connection rules

  2. International itineraries - Determine if IATA Resolution 302 or DOT - US Department of Transportation or CTA - Canadian Transportation Agency applies

MOST SIGNIFICANT CARRIER (MSC)

• Determine which carrier’s baggage data apply to a specific BT

• May be either the marketing or the operation carrier in the itinerary, depending on the airline’s filing within ATPCO

Step 1: Determine the Baggage Trips

The BT is created from origin to first stopover point (BT1); next BT (BT2) is created from arrival of BT1 to next stopover point; process continues until end of itinerary is reached.

 

Step 2: Determine Most Significant Carrier (MSC) for each BT

For wholly domestic itineraries, MSC for each BT will be the FIRST MARKETING CARRIER on the checked portion.

Example:

For journeys within Canada and USA, when determining whose rules apply, use the rules of the FIRST MARKETING CARRIER on the journey.

Example:

STEP 1: Check furthest point of travel

• Furthest point by mileage from journey origin that meets the definition of a checked point.

• TPM for all GI from origin to candidate ‘furthest point’ must be considered.

• If TPM does not exist, MPM/ 1.2 will be used to determine furthest point.

• If no MPM exists, GCM (Great Circle Miles) should be used.

 

STEP 2: Is the origin, destination or further checked point in USA or Canada ?

YES in the US – DOT Reservation applies

YES in Canada – CTA Reservation applies

NO – IATA Reso 302 applies

 

STEP 3: Identify BT and MSC

DOT/CTA Reservation (Baggage rules for origin, destination or furthest point in USA or Canada)

Only 2 BTs are created

• Outbound BT: from origin to furthest checked point

• Inbound BT: furthest checked point to destination

 

MSC - MARKETING carrier defines the MSC on a BT.

ATPCO maintains a list of US DOT CTA carriers that file general rule tariffs applicable for travel to/from the United States and Canada. These lists should be used by subscribers of ATPCO’s Baggage product for determining baggage selection rules for travel to/from the United States.

Carriers must use the FIRST MARKETING carriers baggage rules for the entire journey, provided the first marketing carrier is specified in the DOT’s, respectively CTA’s published list of DOT/CTA carriers.

If the first marketing carrier is not specified in DOT’s respectively CTA’s published list of carriers for journeys to/from USA or Canada, then use the rules of the NEXT CONSECUTIVE MARKETING CARRIER on the journey, and continue until processing finds the next “first” marketing carrier who is specified in DOT/CTA’s list of carriers. Once the first marketing carrier is identified, their baggage rules apply to the entire journey.

 

Example 1:

 

Example 2:

1 AS 219G 20OCT MO GDLLAX MK1 730A 900A/O E

2 JL 61E 20OCT MO LAXNRT MK1 120P 455P#1/O E

3 JL 62E 14NOV FR NRTLAX MK1 505P 1000A/O E

BT SIGNIFICANT

BRDOFF SEGMENT MRK OPR MSC

GDLNRT LAXNRT JL JL AS

NRTLAX NRTLAX JL JL AS

 

IATA Resolution 302 (Baggage rules for origin, destination or furthest point NOT in US/CA)

 

BT

• First BT: from origin to first stopover

• Next BT: from arrival point of previous BT to next stopover

• Continues until last point of itinerary is reached

 

MSC

• MARKETING carrier defines the MSC on a BT

In accordance to the IATA Resolution 302, the MSC (Most Significant Carrier) is:

• For travel between two or more IATA Areas, the carrier performing carriage on the first sector that crosses from one area to another.

Exception: IATA Area 1/2/3 only, the carrier providing carriage on the first sector that crosses between IATA Area 1 and IATA Area 2.

• For travel between IATA Tariff sub-areas, the carrier performing carriage on the first sector that crosses from one sub-area to another.

• For travel within a IATA Tariff sub-area, the carrier performing carriage on the first international sector.

• For travel within a single country, the first carrier on the checked portion

 

Example:

• S5 - Type C

• S7 - Type A

When value “J” i.e. Journey is filed in Byte 133, system is required to match Loc 1 and Loc 2 Geo locations against Origin, Destination as well as furthest point in Loc1 and Loc 2 to determine a match in S7 record.

Use the Direct mileage entry to compare TPMs for furthest point (FL/DUBYYC or 4F/DUB/YYC); it looks for TPM if not found then MPM then GCM.

 

Example : below itinerary (sold in Ireland, ticketed in Ireland):

On the below example, RO deferred to marketing carriers baggage rules:

Only on BUHPAR sector:

Hence on the below itinerary this sequence is not picked, as the BT/sector is IASPAR

 

1.1TEST/M*ADT

1 RO 708L 19MAR WE IASOTP SS1 650P 800P/O $ E

2*AF1257A 20MAR TH OTPCDG SS1 1250P 310P/O $ E

>4PEEUR/RO/RO(

TICKET BASE EUR TX/FEE EUR TKT TTL EUR

ADT01 595.00 93.72 688.72

*TTL 595.00 93.72 688.72

FBC ADT AFFWRO

BAGGAGE ALLOWANCE

ADT

RO IASCDG 3PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

 

BT SIGNIFICANT

BRDOFF SEGMENT MRK OPR MSC

IASCDG OTPCDG AF RO RO

>4PEEUR/RO/RO#DASB*

BAGGAGE ALLOWANCE/CHARGES DIAGNOSTIC

RULE - IATA 08MAR2014

FTP - CDG

ADT CODE TRIP TYP SEQ DEF CHG

RO IASCDG 3PC 0DF TR01 BA 0120000

IASCDG

BAG 1 NO FEE 0GO TR01 B1

BAG 2 NO FEE 0GO TR01 B1

Whereas on the below itinerary the mentioned sequence is applied instead as the sector is BUHPAR:

1.1TEST/M*ADT

1*AF1257A 20MAR TH OTPCDG SS1 1250P 310P/O $ E

>4PEEUR/RO/RO(

TICKET BASE EUR TX/FEE EUR TKT TTL EUR

ADT01 490.00 62.16 552.16

*TTL 490.00 62.16 552.16

FBC ADT AFFWRO

BAGGAGE ALLOWANCE

ADT

AF OTPCDG 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 315.00 RON UPTO50LB/23KG AND UPTO62LI/158LCM

 

BT SIGNIFICANT

BRDOFF SEGMENT MRK OPR MSC

OTPCDG OTPCDG AF RO RO

>4PEEUR/RO/RO#DASB*

BAGGAGE ALLOWANCE/CHARGES DIAGNOSTIC

RULE - IATA 08MAR2014

FTP - CDG

ADT CODE TRIP TYP SEQ DEF CHG

RO OTPCDG 0PC 0DF TR01 BA 0100000 Y

AF OTPCDG 1PC 0DF TR01 BA 0535000

OTPCDG

BAG 1 NO FEE 0GO TR01 B1

BAG 2 315.00 RON 0GO TR01 B2 0367968

FURTHEST CHECKED POINT = When calculating the “furthest checked point” for baggage allowance, the true Global Indicator must be considered.

For example, on the below reported itinerary:

The system is designed to display the baggage allowance per checked portion. This is done to accommodate situations where a carrier has filed charges per checked portion and not per baggage trip.

 

BAG charges filed per travel/direction/BT

When pricing the below itinerary:

1 LY 27N 01DEC MO TLVEWR SS1 0035 0605 /O $ E

2 B61025O 02DEC TU JFKTPA SS1 0835 1134 /O $ E

3 ARNK

4 B6 478U 09DEC TU JAXJFK SS1 1819 2032 /O $ E

5 LY 28U 16DEC TU EWRTLV SS1 1315 0650 #1/O $ E

 

The system is processing the baggage allowance and charges by using US DOT mandate; hence the baggage trips are established from the point of origin (TLV) to the furthest point in the journey (TPA).

In this example, we have:

• 2 BTs: TLVTPA and JAXTLV

• 4 CHECKED PORTIONs: TLVEWR, JFKTPA, JAXJFK and EWRTLV

BAGGAGE ALLOWANCE

LY TLVEWR 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 115.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM <<< Charges are applicable per Baggage trip to furthest point TPA

LY JFKTPA 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM <<< Hence it is not shown with all intermediate sectors within the baggage trip

 

LY JAXJFK 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 115.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM <<< Charges are applicable per Baggage trip to furthest point

 

LY EWRTLV 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM <<< Hence it is not shown with all intermediate sectors within the baggage trip

 

According to the ATPCO filing, the baggage charges for BAG 2 are applicable once per baggage trip from the point of origin (TLV) to the furthest point in the journey (TPA) hence it is not shown with all intermediate sectors within the baggage trip.

ADT CODE TRIP TYP SEQ DEF CHG

LY TLVTPA 1PC 0DF TR01 BA 0427118

TLVEWR

BAG 1 NO FEE 0GO TR01 B1

BAG 2 115.00 USD 0GO TR01 B2 0144218 D

JFKTPA

BAG 1 NO FEE 0GO TR02 B1

BAG 2 NO FEE 0GO TR02 B2 0144218 D

LY JAXTLV 1PC 0DF TR03 BA 0427118

JAXJFK

BAG 1 NO FEE 0GO TR03 B1

BAG 2 115.00 USD 0GO TR03 B2 0144218 D

EWRTLV

BAG 1 NO FEE 0GO TR04 B1

BAG 2 NO FEE 0GO TR04 B2 0144218 D

 

 

LY has filed the BAG 2 charges per direction, not per checked portion:

 

Data apps:

Quote

Fee Application (byte 311)

Value 4: Per Travel. The fee amount is to be charged once per matched Baggage Travel (BT). The fee applies per BT, regardless of the value in Sector/Portion/Journey (byte 133).

Unquote

When the carrier has filed charges per checked portion and not per baggage trip, the system will accordingly show the baggage data on each checked portion:

1.1TEST/M*ADT

1*UA4644V 16NOV SU EWRYHZ MK1 850A 1149A/O E

2*UA5928L 30NOV SU YWGORD MK1 254P 505P/O E

3 UA 972L 30NOV SU ORDBRU MK1 555P 920A#1/O E

BAGGAGE ALLOWANCE

ADT

UA EWRYHZ 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 100.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM

 

UA YWGBRU 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 100.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM

RULE - DOT-TO/FROM 15OCT2014

FTP - BRU

ADT CODE TRIP TYP SEQ DEF CHG

UA EWRBRU 1PC 0DF TR01 BA 0102250

EWRYHZ

BAG 1 NO FEE 0GO TR01 B1

BAG 2 100.00 USD 0GO TR01 B2 0104437 P

YWGBRU

BAG 1 NO FEE 0GO TR02 B1

BAG 2 100.00 USD 0GO TR02 B2 0104437 P

Data apps:

Quote

Fee Application (byte 311)

Value 3: Per Item (each time the service is used/requested).

Unquote

Because there is nothing in the text table 1G cannot parse the text table. NGGF doesn't look further if it cannot parse the text table. Merchandising Engine, on the other hand, tries to return charges if it can it does that because Merchandising Engine also handles check in process, and has the code built in. As the S7 filing exists for the carrier, the system can still interrogate the C type services and return applicable pricing.

• Example 1:

B6 has not filed "Note Text Table 196" in S7 sequence 0085932:

in order to populate the description for BAG1 and BAG2 processing reads the S5 record of C type service and validates the most generic Sub-Code which is filed with a Sub-Group "BLANK" value

Thus 1P system correctly validates and processes the most generic sub-code "0EW" for BAG 1 / BAG 2 descriptions:

RULE - DOT-TO/FROM 27OCT2014

FTP - JNB

ADT CODE TRIP TYP SEQ DEF CHG

B6 IADJNB 23K 0DF TR01 BA 0085932

IADJFK

BAG 1 NO FEE 0EW TR01 B1 0115000 D

BAG 2 NO FEE 0EW TR01 B1 0115000 D

JFKJNB

BAG 1 NO FEE 0EW TR02 B1 0115000 D

BAG 2 NO FEE 0EW TR02 B1 0115000 D

Also, within S7 sequence 85932, B6 has filed Free Pieces with value 2, Weight with value 23 and Unit with value K.

According to ATPCO data apps, when there is data in both pieces and weight, the Weight/Unit value field will appear on the customer’s ticket:

Quote

Baggage Weight/Unit (bytes 275-279)

When the Weight field contains value 0001-9999, processing will put the last two digits of the weight value + the unit value “K” or “L” on the passenger ticket (e.g. 20K). When there is data in the Weight/Unit field AND the Free Pieces (bytes 269-270) field, processing shall put the value in the Weight/Unit field on the passenger ticket.

Unquote

Re-filing options:

1) If B6 intends to have the BAG1 and BAG2 description with 23K then B6 needs to re-file S7 sequence 0085932 to add text “//02/0GO” in Text Table 196. – This will need 1 update in S7 Record

OR

2) As an alternate, B6 can only file 23K as weight allowance and remove 2 pieces from S7 sequence 0085932. – This will also need 1 update in S7 Record

OR

3) Re-file S7 sequence 0085932 to add text “//02/0GO” in Text Table 196 + remove 23K from S7 sequence 0085932 - This will need 2 updates in S7 Record

 

• Example 2

AT expects sequence number 6782 with 23KG each one; Worldspan shows 32KG for each bag (0C6 SEQ 0099902):

>*R

1.1TEST/M*ADT

1 AT 953R 21FEB FR BLQCMN MK1 445P 700P/O E

>4P(

PNR PRICED ON 13FEB FOR TKTG ON 13FEB

* AT ONLY/SUBJECT TO SPCL CONDITIONS

* PRICING RULES VALIDATING CARRIER DEFAULT AT

**CARRIER MAY OFFER ADDITIONAL SERVICES**SEE >4P#DASO(

** 21FEB DEPARTURE DATE/ 21FEB IS LAST DATE TO TICKET

* FARE MAY CHANGE UNLESS TICKETED *

1EUR/1.364442USD

 

TICKET BASE EUR EV USD TX/FEE USD TKT TTL USD

ADT01 87.00 119.00 102.70 221.70

*TTL 87.00 119.00 102.70 221.70

FBC ADT ROW

ADT BLQ AT CAS118.87NUC118.87END ROE.731857 AT XT12.40IT1.10MJ

3.60VT75.00YQ

TX 1.70EX 8.90HB 12.40IT 1.10MJ 3.60VT 75.00YQ

BAGGAGE ALLOWANCE

ADT

AT BLQCMN 2PC

BAG 1 - NO FEE UPTO70LB/32KG

BAG 2 - NO FEE UPTO70LB/32KG

 

>4P#DASB*

BAGGAGE ALLOWANCE/CHARGES DIAGNOSTIC

RULE - IATA 13FEB2014

FTP - CMN

ADT CODE TRIP TYP SEQ DEF CHG

AT BLQCMN 2PC 0DF TR01 BA 0006782

BLQCMN

BAG 1 NO FEE 0C6 TR01 B1 0099902

BAG 2 NO FEE 0C6 TR01 B1 0099902

AT has not filed "Note Text Table 196" in S7 sequence 6782:

The carrier has all their 0C3 filing with restrictions on First/Last Excess Baggage Piece (bytes 271-274). As the allowance is 2, processing will only process subcodes with sequences which do not have any restrictions on first and last excess baggage piece (or first/last piece = 0), as bag1 and bag2 are within the allowance limit.

Hence 0C6 is processed, and we are unable to find a match for 0C3 sequences.

To return details for the 1st check in bag (for an allowance with //01/0C3) Merch Engine will look for 0C3 S5 record to get the description / restrictions for that subcode. If the carrier doesn’t file 0C3 subcode, we will look for all S5 subcodes coded with group BG and subgroup BLANK, and look for corresponding S7 records which either have first / last excess piece BLANK or 0 (to indicate that the sequences are applicable when the bag is within the allowance by pieces limit). Processing S7 will need to match all other restrictions (geo / fare info / cabin etc) in order to return a correct sequence back.

If the carrier doesn’t file text in their S7, Merch Engine will look for all subcodes that are filed with Group Code BG and subgroup code BLANK, and try to match a S7 sequence. It will need to match all the fields within a S7 record (including first/last excess baggage piece). This may result in a non-zero price returned for a bag within an allowance, if the carrier filed it that way.

If processing returns multiple subcodes with a non-zero price, it will return the details corresponding to the lowest price. If all subcodes are zero priced, it will return the most generous allowance, i.e. the subcode with the largest permitted weight.

• Example 1

CY has filed multiple Sub-codes 0IZ, 0D4, 0PW, 0PX and 0PY in Table 196 within S7 sequence 0024684 for 1PC Allowance thus in order to process the Baggage Charges system try to read all these sub-codes in S5 Record and finds the lowest possible charge for BAG 2.

Based on how CY has filed its S5 record, system finds a valid match to a Sub-code 0IZ with no charge [first extra bag].

1.1TEST/M*ADT

1 CY 313W 23NOV SU ATHLCA MK1 1130A 105P/O E

BAGGAGE ALLOWANCE

ADT

CY ATHLCA 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO81LI/208LCM

BAG 2 - NO FEE UPTO50LB/23KG AND UPTO81LI/208LCM

 

CY ATHLCA 1PC 0DF TR01 BA 0024684

ATHLCA

BAG 1 NO FEE 0IZ TR01 B1

BAG 2 NO FEE 0IZ TR01 B2 0100250 <<<<<<<<

Carrier expects baggage charges to be returned as per 0IZ sequence for Bag 1 and 0P2 sequence for Bag 2. To achieve this filing to the 0IZ sequence has been changed as follows:

a. First Pc = 2

b. Last Pc = BLANK

This new data will allow system to process Sub Code “0IZ” for BAG 2 only if it finds that Cxr has also filed the Free Baggage allowance up to 2 PC.

Because, the First Piece value i.e. “2” becomes higher than the actual Free Baggage Allowance value (1 PC)

the processing for BAG 2 will not be assessed within “0IZ” sub-code instead system will now look for a different Sub-code to assess the lowest possible price for BAG 2.

On the other hand with Current Filing:-

a. First Pc = 1

b. Last Pc = 1

Cxr has restricted the free Baggage allowance up to 1 PC only ; therefore system finds a valid match with a Sub-code “0IZ” for BAG 1 to show NO FEE as expected. However, based on the current filing the First Piece value i.e. “1” which is equal to the value of Free Baggage Allowance i.e. “1 Pc” due to this reason system remains within this Sub-code “0IZ” and tries to read on further its Last Piece value to assess NO FEE for BAG 2.

1 CY 313W 23NOV ATHLCA MK1 1130A 105P /O E

 

>4PEEUR/RO/RO(

PNR PRICED ON 25APR FOR TKTG ON 25APR

* VALID CY/ NON-REF//CHNGS RESTR

* PRICING RULES VALIDATING CARRIER DEFAULT CY

**CARRIER MAY OFFER ADDITIONAL SERVICES**SEE >4P#DASO(

** 23NOV DEPARTURE DATE/ 27APR IS LAST DATE TO TICKET

* FARE MAY CHANGE UNLESS TICKETED *

 

TICKET BASE EUR TX/FEE EUR TKT TTL EUR

ADT01 26.00 74.05 100.05

*TTL 26.00 74.05 100.05

FBC ADT WQUICK1

ADT ATH CY LCA35.88NUC35.88END ROE.724488 CY XT5.00WQ0.90JX

41.00YQ

TX 12.00GR 15.15WP 5.00WQ 0.90JX 41.00YQ

BAGGAGE ALLOWANCE

ADT

CY ATHLCA 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO81LI/208LCM

BAG 2 - 30.00 EUR UPTO50LB/23KG AND UPTO81LI/208LCM

ADT CODE TRIP TYP SEQ DEF CHG

CY ATHLCA 1PC 0DF TR01 BA 0024684

ATHLCA

BAG 1 NO FEE 0IZ TR01 B1

BAG 2 30.00 EUR 0P2 TR01 B2 0100000

• Example 2

We are returning 1PC free baggage allowance via ATPCO sequence 0139490, picking type C charges as per 0GO subcode for bag 1 and 0FM subcode (SEQ0099706) for bag 2:

1.1TEST/M

1. TP 351 A 02JUN LHRLIS AK1 0600 0835 MO

2. TP 113 A 02JUN LISMIA AK1 1030 1500 MO

ADT CODE TRIP TYP SEQ DEF CHG

TP LHRMIA 1PC 0DF TR01 BA 0139490

LHRMIA

BAG 1 NO FEE 0GO TR01 B1

BAG 2 65.30 GBP 0FM TR01 B2 0099706 D

Note Text table 196 in S7 sequence 0139490 contain the 0GO subcode:

The airline intent is to have the system matching 0GO subcode sequence 95317 for the 2nd bag.

Why the system does not remain within the 0GO subcode when returning data for the second bag?

The design is to always look for a combination of lowest price + best possible BAG 2 weight allowance.

According to ATPCO data apps for baggage allowance and charges in optional services sub code services record S5:

Quote

Processing shall interrogate the Record S7 with all sub codes and select the least expensive charge.

Unquote

Because the carrier has filed the same amount of charges for both Sub codes 0GO and 0FM the system calculates the lowest best possible out of the 2 sub-codes and finds the below information:

0FM = Allows 32KG <<<<<<<<<<<<<

0GO = Allows 23KG

Out of these two Sub-codes, system picks 0FM because this allows customer to take a 32KG bag at the same cost.

If the carrier's intend is to show 0GO instead of 0FM then, the carrier may need to increase the baggage charge amount for Sub- Code 0FM.

1.1TEST/M*ADT

1 RJ 111J 20DEC SA AMMLHR MK1 1135A 245P/O E

>4P(

PNR PRICED ON 21NOV FOR TKTG ON 21NOV

* RJ ONLY/NONREF/ENDO/RERO

* PRICING RULES VALIDATING CARRIER DEFAULT RJ

**CARRIER MAY OFFER ADDITIONAL SERVICES**SEE >4P#DASO(

** 20DEC DEPARTURE DATE/ 20DEC IS LAST DATE TO TICKET

* FARE MAY CHANGE UNLESS TICKETED *

1JOD/1.416631USD

 

TICKET BASE JOD EV USD TX/FEE USD TKT TTL USD

ADT01 2055.00 2911.00 233.90 3144.90

*TTL 2055.00 2911.00 233.90 3144.90

FBC ADT JLOWJO

ADT AMM RJ LON2901.47NUC2901.47END ROE.70826 RJ XT9.90YQ

158.80YR

TX 56.70HQ 8.50NH 9.90YQ 158.80YR

BAGGAGE ALLOWANCE

ADT

RJ AMMLHR 2PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - NO FEE UPTO66LB/30KG AND UPTO62LI/158LCM

BAGGAGE ALLOWANCE/CHARGES DIAGNOSTIC

RULE - IATA 21NOV2014

FTP - LHR

ADT CODE TRIP TYP SEQ DEF CHG

RJ AMMLHR 2PC 0DF TR01 BA 2000000

AMMLHR

BAG 1 NO FEE 0GO TR01 B1

BAG 2 NO FEE 0FL TR01 B2

Travelport fails to match S7 sequence 460000 because SV did not file any value in Baggage Travel Application, hence processing defaults to the Cabin "Y" (Economy Cabin) that should apply to the most significant sector (CDG-JFK) on the baggage travel.

>*R

1.1TEST/M*ADT

1 SV 127Y 14OCT TU JEDCDG MK1 1255A 610A/O >>>>>economy

2 AF 22S 14OCT TU CDGJFK MK1 820A 1030A/O E >>>>premium economy

3 AF 7S 26OCT SU JFKCDG MK1 810P 830A#1/O E >>>>premium economy

4 SV 126Y 27OCT MO CDGJED MK1 1110A 635P/O >>>>>economy

RULE - DOT-TO/FROM

FTP - JFK

GEN RULE - SV-Y

 

JEDJFK 6371 TPM

 

BT SIGNIFICANT

BRDOFF SEGMENT MRK OPR MSC

JEDJFK CDGJFK AF AF SV

JFKJED JFKCDG AF AF SV

 

Since no match on S7 sequence 460000, our system then reads on further to process the remaining S7 Records but none of the S7 records matches, hence it returns the message CONTACT CARRIER - CHARGES MAY APPLY:

>4PESAR/SA/SA(

PNR PRICED ON 08OCT FOR TKTG ON 08OCT

* PRICING RULES VALIDATING CARRIER DEFAULT AF

**CARRIER MAY OFFER ADDITIONAL SERVICES**SEE >4P#DASO(

** 14OCT DEPARTURE DATE/ 14OCT IS LAST DATE TO TICKET

* FARE MAY CHANGE UNLESS TICKETED *

** TICKETING FEES MAY APPLY - SEE >INFO TKTFEE (

TICKET BASE SAR TX/FEE SAR TKT TTL SAR

ADT01 6250 1551 7801

*TTL 6250 1551 7801

FBC ADT SFFSA

ADT JED SV X/PAR AF NYC M833.24AF X/PAR SV JED M833.24NUC

1666.48END ROE3.75041 AF XT148QX21AY132US19XA27XY21YC

962YR17XF JFK4.5

TX 50UR 154FR 148QX 21AY 132US 19XA 27XY 21YC 962YR 17XF

BAGGAGE ALLOWANCE

ADT

SV JEDJFK CONTACT CARRIER - CHARGES MAY APPLY

MYTRIPANDMORE.COM/BAGGAGEDETAILSSV.BAGG

SV JFKJED CONTACT CARRIER - CHARGES MAY APPLY

MYTRIPANDMORE.COM/BAGGAGEDETAILSSV.BAGG

ATPCO Data Apps:

Quote

Baggage Travel Application

The default application (applying the cabin for the most significant sector) can be overridden with applicable data in Baggage Travel Application (byte 280). Following is an explanation of the application of values in Byte 280 relative to Cabin validation:

Value A: All sectors. The Cabin must validate against all sectors on the BT. Cabin validation is based on the marketing carrier’s booked RBD and corresponding cabin on each sector of the BT. Each sector’s cabin must match the data in the Cabin field in order to match the Record S7.

Value S: At least one sector. The Cabin must validate against at least one sector on the BT. Cabin validation is based on the marketing carrier’s booked RBD and corresponding cabin on at least one sector of the BT. At least one sector’s cabin must match the data in the Cabin field in order to match the Record S7. Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector.

Value M: Most significant sector. This has the same application as the default application for the Cabin field.

Value J: Any sector on the Journey. The cabin must validate against at least one sector of the journey. Cabin validation is based on the marketing carrier’s booked RBD and the corresponding cabin on at least one sector on the whole jouney. At least one sector’s cabin must match the data in the Cabin field in order to match the Record S7. Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector.

Value Blank: Default Application. For Cabin validation, this has the same application as byte 280 value M.

Unquote

For the below itinerary we fail to match sequence #49631:

1.1TEST/M

1. A5 6436 U 12JUL BESNCE AK1 1155 1345 SU

2. AF 4758 U 12JUL NCECLY AK1 1610 1650 SU

OPERATED BY AIR CORSICA

3. AF 7573 M 19JUL CLYORY AK1 0950 1120 SU

4. AF 7366 M 19JUL ORYBES AK1 1300 1410 SU

** FILED FARE DATA EXISTS ** >*FF·

>FQ

P1 TEST/M ADT G 04NOV14 * EUR 513.80

BES A5 X/NCE AF CLY 185.00 AF X/PAR AF BES 230.00 EUR415.00END

FARE EUR415.00 TAX 67.89FR TAX 2.26IZ TAX 28.65QW

TOT EUR513.80

***ADDITIONAL FEES MAY APPLY*SEE>FO1·

S1 FB-UWKFR

BG-CHK NB-12JUL NA-12JUL

S2 FB-UWKFR

BG-CHK NB-12JUL NA-12JUL

S3 FB-MWKFR

BG-1PC NB-19JUL NA-19JUL

The diagnostic shows that we fail RBD

+ 49631 FAILED S7 TBL198 RBD CHECK 1 A A5 +

RBD data in sequence #49631 has two records both with Marketing Carrier A5.

In our Baggage Trip BES – CLY we have two sectors

• 1st Sector BES – NCE is on Marketing Carrier A5 and

• 2nd sector NCE – CLY is on Marketing Carrier AF.

Baggage Travel Application (byte 280) is blank. Therefore default application of RBD table is applicable which states “All Sectors on Baggage Trip must match at least one entry in RBD table”. Second sector on Carrier AF fails RBD matching.

Please see below excerpts from Data Apps:

RBD Table 198 (default) validation is against all sectors on the BT. Each marketing/operating (depending upon the data in Table 198) carrier’s RBD associated to each booked RBD on the BT must match at least one entry in Table 198. The match does not have to be against the same Table 198 RBD/entry; however, each must match at least one Table 198 entry.

• If each marketing/operating carrier’s RBD matches at least one Table 198 entry, then processing matches the record (provided a match is also made to all other match fields).

• If any marketing/operating carrier’s RBD cannot match a Table 198 entry, then processing no matches the record and continues to the next record

Carrier can override this default processing by modifying value in Baggage Travel Application Byte 280. Please see below different values and their interpretation.

Baggage Travel Application (Byte 280)

The default application (validating all sectors on the BT) can be overridden with applicable data in Baggage Travel Application (byte 280). Following is an explanation of the application of values in Byte 280 relative to RBD Table 198 validation:

Value A: All sectors. This has the same application as the default application for the RBD Table 198.

Value S: At least one sector. At least one record (entry) in RBD Table 198 must validate against at least one sector on the BT in order to match the Record S7. Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector.

Value M: Most significant sector. At least one record (entry) in RBD Table 198 must validate against the most significant sector on the BT in order to match the Record S7. Determination of the most significant sector is based on the application detailed for determining the most significant carrier (refer to Baggage Allowance and Charges Overview – Attachment A – Baggage Selection).

Value J: Any sector on the Journey. At least one record (entry) in RBD Table 198 must validate against at least one sector on the journey in order to match the Record S7. Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector.

Value Blank: Default Application. For RBD Table 198 validation, this has the same application as byte 280 value A.

According to the airline the fare class KDOW must have 1PC (15kg) via the sequence 45903:

Galileo shows 25K:

1.1TEST/N

1. UN 253 K 17FEB DMEVNO AK1 0955 0935 MO

FQ1 - S1 AP 12FEB14 NG/AG

>FQ

P1 TEST/N ADT G 12FEB14 * RUB 3652

MOW UN VNO 30.06 NUC30.06END ROE0.731857

FARE EUR22.00 EQU RUB1060 TAX 48RU TAX 1824YQ TAX 720YR

TOT RUB3652

***ADDITIONAL FEES MAY APPLY*SEE>FO1·

S1 FB-KDOW

BG-25K NB-17FEB NA-17FEB

LAST DATE TO PURCHASE TICKET: 13FEB14

>FN1/23

QUOTE01

01 DME-VNO MO-17FEB14 UN NUC 30.06 KDOW

23. MISCELLANEOUS PROVISIONS

FOR K- TYPE FARES

THIS FARE MAY BE USED FOR ADD-ON CONSTRUCTION. THIS FARE

MUST NOT BE USED AS THE HIGH OR THE LOW FARE WHEN

CALCULATING A DIFFERENTIAL. THIS FARE MUST NOT BE USED AS

THE THROUGH FARE WHEN PRICING A FARE COMPONENT WITH A

DIFFERENTIAL.

NOTE -

BAGGAGE ALLOWANCE ON THE SECTOR TO/FROM DME 15 KG -----

Travelport is correct failing to apply sequence 45903:

*-------------TRAP: BAGFAIL - FAILED S7 SEQUENCES--------------*

+ TYPE - A (CHECKED ALLOWANCE), B (CARRY-N ALLOWANCE) +

+ C (CHECKED BAG CHARGES), BC (CARRY-ON CHARGES) +

+SEQNUM PASS/FAIL REASON CODE BTNUM TYPE MSC +

+------- --------------------- ----- ---- --- +

+ 45903 FAILED S7 GEO/STOPCONX CHECK 1 A UN +

This sequence is coded in GEO 1 as DME and fares are filed as MOW.

The airline should be setting the airport tag on this location of DME, if they want the code validated as an airport:

After the airline changed the filing:

1G is applying 1PC via applying sequence 45391:

1.1TEST/N

1. UN 253 K 17MAR DMEVNO AK1 0955 0935 MO

FQ3 - S1 AP 05MAR14 NG/AG

>FQ

P1 TEST/N ADT G 05MAR14 * RUB 3800

MOW UN VNO 30.06 NUC30.06END ROE0.731857

FARE EUR22.00 EQU RUB1100 TAX 50RU TAX 1900YQ TAX 750YR

TOT RUB3800

***ADDITIONAL FEES MAY APPLY*SEE>FO3·

S1 FB-KDOW

BG-1PC NB-17MAR NA-17MAR

LAST DATE TO PURCHASE TICKET: 06MAR14

T S1/CUN/ET/TAXZ4

1*A5 932N 02SEP TU LRTORY MK1 1015A 1125A/O

2 AF7574N 02SEP TU ORYCLY MK1 145P 320P/O E

 

FQ**SRC74

P1 LEGLEUT/ANNETTEMRS SRC74 G 23JUL14 * EUR 156.39

LRT A5 X/PAR AF CLY 108.00 EUR108.00END

FARE EUR108.00 TAX 34.69FR TAX 1.13IZ TAX 12.57QW

TOT EUR156.39

***ADDITIONAL FEES MAY APPLY*SEE>FO1·

S1 FB-NCDFR

BG-CHK NB-02SEP NA-02SEP

S2 FB-NCDFR

BG-CHK NB-02SEP NA-02SEP

NONREF

EVASION SENIOR

For the same, Amadeus is processing A5 sequence 0050055 and applying 1PC

FQQ1

 

01 SE CITIZEN * * 1 * 185.78 *SR *Y

 

LAST TKT DTE 27JUL14 - SEE ADV PURCHASE

------------------------------------------------------------

AL FLGT BK T DATE TIME FARE BASIS NVB NVA BG

LRT

XPAR A5 932 N N 02SEP 1015 NCDFR 02SEP02SEP 1P

CLY AF 7574 N N 02SEP 1345 NCDFR 02SEP02SEP 1P

 

EUR 108.00 02SEP14LRT A5 X/PAR AF CLY107.35EUR107.35

END

EUR 1.13IZ XT EUR 8.72FR EUR 21.40FR EUR 4.57FR EUR

EUR 12.57QW 4.39UI

EUR 39.08XT

EUR 160.78

EUR 25.00 AIRLINE FEES

EUR 185.78 TOTAL

AIRLINE FEES INCLUDED

We are failing to apply the same sequence due to TABLE 186 (actually all sequences are failing TBL 186).

ADT 0DF SEQ FAIL REASON TBL NO PASS DEF

A5 LRTCLY NIL

0000295 CARRIER/FLT TBL 186 5684

0001660 CARRIER/FLT TBL 186 5684

0002440 CARRIER/FLT TBL 186 5684

0002830 CARRIER/FLT TBL 186 5684

0003221 CARRIER/FLT TBL 186 8291

0048293 CARRIER/FLT TBL 186 5684

0048489 CARRIER/FLT TBL 186 5684

0048879 CARRIER/FLT TBL 186 5684

0049269 CARRIER/FLT TBL 186 8754

0049476 CARRIER/FLT TBL 186 5684

0049683 CARRIER/FLT TBL 186 9065

0049695 CARRIER/FLT TBL 186 5684

0049805 CARRIER/FLT TBL 186 5684

0050055 CARRIER/FLT TBL 186 8024

Here is Table 186 nbr 8024 data

It seems 1A is passing this table since considering the Baggage Trip BT which is A5/A5 (no DEI50 loaded on this flight) LRT-CLY.

Whereas we are failing since we need to validate/pass BOTH segments.

So we pass the first one A5/A5 (no DEI50) but we fail on second segment AF/AF (no DEI50) since AF/AF not coded in the 186 Table…

Quote

Service Type Values A, E, P and C (Baggage Allowance, Embargoes, Pre-Paid Baggage and Baggage Charges)

When the value in the Not Available/No Charge (byte 288) field is NOT value D, the carrier/flight requirements in Table 186 match against all sectors on the baggage travel (BT) resulting from Baggage Selection Processing (refer to Optional Services Overview Data Application – Baggage Selection). All sectors within the BT do not have to match the same Table 186 segment; however, all sectors must match at least one segment in Table 186.

• If the carriers/flights on all sectors on the BT match the data in Table 186, then processing matches the record (provided a match is also made to all other match fields).

• If the carrier/flights on all sectors on the BT do not match the data in Table 186, then processing no matches the record and continues to the next record.

Unquote

We are failing 49631 sequence with S7 TBL183 SECURITY CHECK

1.1TEST/M

1. A5 6436 U 12JUL BESNCE AK1 1155 1345 SU

2. AF 4758 U 12JUL NCECLY AK1 1610 1650 SU

OPERATED BY AIR CORSICA

3. AF 7573 M 19JUL CLYORY AK1 0950 1120 SU

4. AF 7366 M 19JUL ORYBES AK1 1300 1410 SU

** FILED FARE DATA EXISTS ** >*FF·

>FQ

P1 TEST/M ADT G 31OCT14 * GBP 404.60

BES A5 X/NCE AF CLY 185.00 AF X/PAR AF BES 230.00 EUR415.00END

FARE EUR415.00 EQU GBP327.00 TAX 53.20FR TAX 1.80IZ

TAX 22.60QW TOT GBP404.60

***ADDITIONAL FEES MAY APPLY*SEE>FO1·

S1 FB-UWKFR

BG-CHK NB-12JUL NA-12JUL

S2 FB-UWKFR

BG-CHK NB-12JUL NA-12JUL

S3 FB-MWKFR

BG-1PC NB-19JUL NA-19JUL

*-----------------TRAP: BAG - VALIDATEBAGGAGE------------------*

+PAX: ADT GEN: () +

+-BT---BTORIG---CX----BTDEST----SEQNUM--DEF--BAG--CAT35BAGIND- +

+----BAG 1FEE---CHG----BAG 1SEQ---BAG 2FEE--CHG---BAG 2SEQ--- +

+ 1 BES A5 CLY NO S7 CHK N +

+ 2 CLY AF BES 535000 N 1PC N +

+ 0.0 EUR - 535000 20.0 EUR D 102625 +

*------------------------EXIT TRAP: BAG------------------------*

+ 49631 FAILED S7 TBL183 SECURITY CHECK 1 A A5 +

It is correctly failing because Cxr has incorrectly filed the security table for APOLLO instead of GALILEO.

Please see the correct format of security table for 1G, 1V and 1P in security table:-

Resolution:- Thus Cxr A5 needs to file the below format for 1G.

Galileo is processing the baggage allowance and charges by using the most significant operating carrier (MSC) for each checked portion.

ATPCO Data Apps:

Quote

For all other journeys (not subject to the US DOT reservation), when determining whose rules apply, use the rules of the most significant operating carrier (MSC) for each checked portion:

Unquote

Baggage trip details:

BT SIGNIFICANT

BRDOFF SEGMENT MRK OPR MSC

CDGLIN CDGLIN AF AF AF

LINORY LINORY AF VE VE <<<<<<<<<<<<<

You have filed DEI50 for AF9787 flight, so VE is considered the most significant carrier on the second BT - LINORY, therefore VE baggage policy applies:

1.1TEST/M

1. AF 1212 N 21SEP CDGLIN AK1 0720 0850 SU

2. AF 9787 N 23SEP LINORY AK1 1725 1845 TU

OPERATED BY ALITALIA C.A.I. S.P.A. <<<<<<<<<<<<<<<<<<<

>WH:CHG AF 9787 CAPTURE·OPEN SSM .

EFF ·23SEP14 DIS ·25OCT14 FREQ ·MO·TU·WE·TH·FR·SA·SU.

LEG-BRD-TM-DEP--DD--DI-OFF-TM-ARR--DD--DI-EQP--S-CHG-OT-E .

·.1·LIN·..·1725 00 ·I ·ORY·W.·1845·00 ·I ·32S ·J ·. ·ET .

OAD ·.. ·ALITALIA C.A.I. S.P.A. FOR C.A.I. SECOND .

<<<DOI ·VE7088 >>> DMI ·...... .

ATPCO data apps:

Quote

The carrier who owns the schedule record (SSIM file) unless that record contains a value in the DEI050 field which identifies the operating carrier of the segment. DEI050 is a data element found in a SSIM file (Standard Schedules and Information Manual). In order to use this product, carriers should file the operating carrier (and operating carrier flight number) in the DEI050 of the schedules record (as opposed to the DEI027). ATPCO will add this recommended practice to the reference manual for this product. If carriers do not file a value in DEI050, systems will assume the marketing carrier and flight number is the same as the operating carrier and flight number

Unquote

Since the airline VE did not file any ATPCO baggage sequence, the system response of BAGGAGE ALLOWANCE DATA NOT AVAILABLE at the time of fare quote:

BAGGAGE ALLOWANCE

ADT

AF PARMIL 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 70.00 EUR UPTO50LB/23KG AND UPTO62LI/158LCM

 

VE MILPAR BAGGAGE ALLOWANCE DATA NOT AVAILABLE <<<<<<<<<<<<<<<<<

From the ATPCO Data Apps

Journeys not to/from/within the US

Journeys not to/from US consist of all other journeys that do not qualify as to/from within the US as defined above.

For all other journeys (not subject to the US DOT reservation), when determining whose rules apply, use the rules of the most significant operating carrier (MSC) for each checked portioniii:

i. For travel between two or more Tariff Conference areas, the carrier performing carriage on the first sector on the checked portion that crosses from one area to another.

Exception: TC123 and TC 321 only, the carrier providing carriage on the first sector on the checked portion that crosses between TC1 and TC2. This exception applies for TC123 and TC321 only and not for TC312, TC231, etc.

ii. For travel between Tariff Conference sub-areas, the carrier performing carriage on the first sector on the checked portion that crosses from one sub-area to another.

iii. For travel within a Tariff Conference sub-area, the carrier performing carriage on the first international sector on the checked portion.

iv. For travel within a single country, the first carrier on the checked portion.

NOTE: Once the most significant operating carrier is identified (as defined in the steps above), process their Allowance Record S7 for Sub Code 0DF (assuming an S5 0DF is matched) to determine if they defer to the rules of the most significant marketing carrier.

The application of charges for these journeys is on a per-checked portion basis. The Baggage Travel (BT) is the checked portion.

It is the responsibility of the rule owning carrier to ensure that all provisions in the interline baggage agreement are provided for in the baggage allowance and charges.

LX filed the 0PC sequence 25075 with a fare class table containing the -NNV6 fare. This means that all sectors within the baggage trip are validated against this requirement.

Baggage travel application has value blank:

Baggage Travel Application

The default application (validating all sectors on the BT) can be overridden with applicable data in Baggage Travel Application (byte 280). Following is an explanation of the application of values in Byte 280 relative to Table 171 validation:

Value A: All sectors. This has the same application as the default application for the Table 171.

Value S: At least one sector. At least one record (entry) in Table 171 must validate against at least one sector on the BT in order to match the Record S7. When matching the one sector (on the BT), processing must validate against:

• The significant (primary) carrier for the fare component encompassing the sector; and

The Resulting Fare Class Code for the sector; and

• The Fare Type Code applicable to the fare component encompassing the sector.

Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector

Value M: Most significant sector. At least one record (entry) in Table 171 must validate against the most significant sector on the BT in order to match the Record S7. When matching the most significant sector of the BT, processing must validate against:

• The significant (primary) carrier for the fare component encompassing the most significant sector; and

• The Resulting Fare Class Code for the most significant sector; and

• The Fare Type Code applicable to the fare component encompassing the most significant sector.

Determination of the most significant sector is based on the application detailed for determining the most significant carrier (refer to Baggage Allowance and Charges Overview – Attachment A – Baggage Selection).

Value J: Any sector on the Journey. At least one record (entry) in Table 171 must validate against at least one sector on the Journey in order to match the Record S7. When matching the one sector (on the journey), processing must validate against:

• The significant (primary) carrier for the fare component encompassing the sector; and

• The Resulting Fare Class Code for the sector; and

• The Fare Type Code applicable to the fare component encompassing the sector.

Validation of applicable data in Cabin, RBD Table 198, Carrier/Resulting Fare Table 171, Ticket Designator Table 173, Tariff, Rule, Cat 19/25/35, and Carrier/Flight Table 186 must be against the same sector

Value Blank: Default Application. For Table 171 validation, this has the same application as byte 280 value A.

 

In case the Fare Class Code on every sector on the BT do not match this table, then we fail picking data from this sequence and processing continues to the next record.

When pricing the reported itinerary, only the first segment within the GVALUG baggage trip is pricing with a –NNV6 fare, hence it is not valid for this sequence:

 

1.1TEST/M

1. LX 356 Q 18DEC GVALHR AK1 1750 1835 TH

2. LX 325 V 19DEC LHRZRH AK1 1700 1940 FR

3. LX 2914 V 19DEC ZRHLUG AK1 2050 2135 FR

OPERATED BY TYROLEAN AIRWAYS

FQ1 - S1-3 AP 18NOV14 56/AG

>FQCLX-GVALIGHT

P1 TEST/M ADT A 18NOV14 * CHF 439.15

GVA LX LON 163.75 LX X/ZRH LX LUG 134.75 NUC298.50END ROE0.931

29

FARE CHF278.00 TAX 41.65CH TAX 20.50GB TAX 50.00UB

TAX 49.00YQ TOT CHF439.15

***ADDITIONAL FEES MAY APPLY*SEE>FO1·

S1 FB-QNNV6SR

BG-1PC NB-18DEC NA-18DEC

ACCT-GVALIGHT

S2 FB-VRC0DSR/OPF

BG-1PC NB-19DEC NA-19DEC

S3 FB-VRC0DSR/OPF

BG-1PC NB-19DEC NA-19DEC

FG GVALON - QNNV6SR 916/NNV6 - TA

FG LONLUG - VRC0DSR 903/LX23/C25 - TA

FARE RESTRICTIONS APPLY

LAST DATE TO PURCHASE TICKET: 18DEC14

T S1-3/CLX/ET

*-----------------TRAP: BAG - VALIDATEBAGGAGE------------------*

+PAX: ADT GEN: () +

+-BT---BTORIG---CX----BTDEST----SEQNUM--DEF--BAG--CAT35BAGIND- +

+----BAG 1FEE---CHG----BAG 1SEQ---BAG 2FEE--CHG---BAG 2SEQ--- +

+ 1 GVA LX LUG 515000 N 1PC N +

+ 0.0 CHF - 515000 90.0 CHF D 163750 +

*------------------------EXIT TRAP: BAG------------------------*

When we price first segment only, we match the 0PC sequence, as the requirement of having a –NNV6 fare on all sectors within the BT has been met:

FQ5 - S1 AP 18NOV14 56/AG

>FQCLX-GVALIGHT/S1

P1 TEST/M ADT A 18NOV14 * CHF 179.75

GVA LX LON 163.21 NUC163.21END ROE0.93129

FARE CHF152.00 TAX 22.75CH TAX 5.00YQ TOT CHF179.75

***ADDITIONAL FEES MAY APPLY*SEE>FO5·

S1 FB-QNNV6OSR

BG-0PC NB-18DEC NA-18DEC

ACCT-GVALIGHT

FG GVALON - QNNV6OSR 916/NNV6 - TA

FARE RESTRICTIONS APPLY

LAST DATE TO PURCHASE TICKET: 18DEC14

T S1/CLX/ET

*-----------------TRAP: BAG - VALIDATEBAGGAGE------------------*

+PAX: ADT GEN: () +

+-BT---BTORIG---CX----BTDEST----SEQNUM--DEF--BAG--CAT35BAGIND- +

+----BAG 1FEE---CHG----BAG 1SEQ---BAG 2FEE--CHG---BAG 2SEQ--- +

+ 1 GVA LX LON 25075 N 0PC N +

+ 100.0 CHF D 40387 100.0 CHF D 40387 +

*------------------------EXIT TRAP: BAG------------------------*

For all other journeys (not to/from/within the US)

For any Baggage Travel, match the point of sale to the geographic location specified in Table 170 Point of Sale field (Table 170 bytes 14-19). (For Baggage Charges, this is the check-in location. For Prepaid Baggage, this is the offer location.) If an exact match is made, then match that Table 170 record and apply the applicable fee amount.

NO NAMES¬

1 LH 710Y 20SEP SU FRANRT MK1 140P 735A|1/O E¬

2*SQ5916Y 23SEP WE NRTJFK MK1 1100A 1045A/O E¬

3*UA8840Y 25SEP FR JFKFRA MK1 355P 530A|1/O E¬

TKG FAX-NOT PRICED FARE TYPE EX ¬

>4P(¬

PNR PRICED ON 12DEC FOR TKTG ON 12DEC ¬

* CHG BA FOC/CNX BA FOC ¬

* PRICING RULES VALIDATING CARRIER DEFAULT LH¬

**CARRIER MAY OFFER ADDITIONAL SERVICES**SEE >4P|DASO(¬

** 20SEP DEPARTURE DATE/ 09AUG IS LAST DATE TO TICKET¬

* FARE MAY CHANGE UNLESS TICKETED *¬

1EUR/0.788643GBP ¬

¬

** TICKETING FEES MAY APPLY - SEE >INFO TKTFEE (¬

¬

TICKET BASE EUR EV GBP TX/FEE GBP TKT TTL GBP¬

ADT01 7024.00 5539.00 468.60 6007.60¬

*TTL 7024.00 5539.00 468.60 6007.60¬

¬

FBC ADT Y77RT*Y2XRT*Y77RT ¬

ADT FRA LH TYO3794.87SQ NYC2723.53UA FRA2580.43NUC9098.83END¬

ROE.771963 LH XT33.30OY26.40RA2.70OI11.00SW3.60AY3.20XA¬

4.50XY3.50YC2.90XF JFK4.5¬

TX 371.00YQ 6.50DE 33.30OY 26.40RA 2.70OI 11.00SW 3.60AY ¬

3.20XA 4.50XY 3.50YC 2.90XF¬

¬

BAGGAGE ALLOWANCE ¬

ADT ¬

LH FRANRT 1PC ¬

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM ¬

BAG 2 - 75.00 EUR UPTO50LB/23KG AND UPTO62LI/158LCM ¬

MYTRIPANDMORE.COM/BAGGAGEDETAILSLH.BAGG ¬

¬

NH NRTJFK 1PC ¬

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM ¬

BAG 2 - 9000 JPY UPTO50LB/23KG AND UPTO62LI/158LCM ¬

MYTRIPANDMORE.COM/BAGGAGEDETAILSNH.BAGG ¬

¬

LH JFKFRA 1PC ¬

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM ¬

BAG 2 - 100.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM ¬

MYTRIPANDMORE.COM/BAGGAGEDETAILSLH.BAGG ¬

Value T in Stopover/Connection/Destination Indicator should not be filed as per ATPCO data apps.

DATA APPLICATION FOR BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7 Page D.03.S7.073 Revised February

2015 4.1.16.6 Geo Spec – Stopover/Connection/Destination Indicator (byte 169)

Quote

Edits only permit value C or S when Service Type (byte 21) is value A, P, or C."

Unquote

ATPCo RBD Answer table

Cxr UX has not filed RBD “A” under Economy Cabin thus 1P is correctly failing to match the baggage allowance for BT2.

>*R

NO NAMES

1 UX1014Q 14DEC MO LGWMAD MK1 1010 1330 /O

2 UX 71Q 14DEC MO MADCCS MK1 1500 1855 /O

3 UX 72A 28DEC MO CCSMAD MK1 2145 1155 #1/O

4 UX1015A 29DEC TU MADLGW MK1 1500 1620 /O

TKG FAX-NOT PRICED FARE TYPE EX

>4PFSR

PNR PRICED ON 28JUL FOR TKTG ON 28JUL

* PRICING RULES VALIDATING CARRIER DEFAULT UX

** 14DEC DEPARTURE DATE/ 31JUL IS LAST DATE TO TICKET

* FARE MAY CHANGE UNLESS TICKETED *

 

** TICKETING FEES MAY APPLY - SEE >INFO TKTFEE (

TICKET BASE GBP TX/FEE GBP TKT TTL GBP

ADT01 160.00 442.76 602.76

*TTL 160.00 442.76 602.76

FBC ADT QPROVE*APROVE

ADT LON UX X/MAD UX CCS176.56UX X/MAD UX LON69.08NUC245.64END

ROE.651331 UX XT276.00YQ18.40JD0.80OG3.40QV30.20AJ

28.70AK1.60EU

TX 71.00GB 12.66UB 276.00YQ 18.40JD 0.80OG 3.40QV 30.20AJ

28.70AK 1.60EU

BAGGAGE ALLOWANCE

ADT

UX LGWCCS 2PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

MYTRIPANDMORE.COM/BAGGAGEDETAILSUX.BAGG

 

UX CCSLGW CONTACT CARRIER - CHARGES MAY APPLY

MYTRIPANDMORE.COM/BAGGAGEDETAILSUX.BAGG

1P process the data form ATPCo RBD Answer table whereas 1G does not consume it that why there is a difference in results. Hence this is working as filed by Cxr in ATPCo Answer Table.

ATPCO RBD Answer Table for Cxr UX