Validating Carrier, Interline, and GSA

Developer Administration Guide August 2014

W Q2

This documentation is the confidential and proprietary intellectual property of Sabre. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Inc. is strictly prohibited.

Sabre and the Sabre logo design and Sabre Travel Network and the Sabre Travel Network logo design are trademarks and/or service marks of an affiliate of Sabre. All other trademarks, service marks, and trade names are owned by their respective companies.

DOCUMENT REVISION INFORMATION

The following information is to be included with all versions of the document.

Project Project Name Number

Prepared by Date Prepared

Revised by Date Revised

Revision Reason Edition No.

Revised by Date Revised

Revision Reason Edition No.

Revised by Date Revised

Revision Reason Edition No.

• • •

Table of Contents

1 Getting Started

1.1 Introduction ...... 1-1 1.2 Summary of Changes ...... 1-1 1.3 About This Guide ...... 1-2

2 Validating Carrier / Interline Agreement Displays

2.1 Introduction ...... 2-1 2.2 Validating Carrier Display ...... 2-1 2.3 Interline Agreement Display...... 2-2 2.4 Plausibility Check ...... 2-3

3 Pricing and Shopping

3.1 Introduction ...... 3-1 3.2 Returning the Lowest Fare ...... 3-2 3.3 Alternate Validating Carrier...... 3-3 3.4 General Sales Agent ...... 3-5 3.5 Single Neutral Validating Carrier ...... 3-9 3.6 Settlement Override Qualifier ...... 3-12 3.7 Category 15 Text ...... 3-14 3.8 No Ticketable Option ...... 3-16 3.9 Validating Carrier Override ...... 3-17 3.10 Third-Party Developers/Online Travel Agencies ...... 3-18

4 Price Quote

4.1 Introduction ...... 4-1 4.2 Alternate Validating Carrier Field ...... 4-1 4.3 Store Price Quote  No Validating Carrier ...... 4-1

5 T i c k e t i n g

5.1 Introduction ...... 5-1 5.2 Removal of Manual Entry of Validating Carrier ...... 5-1 5.3 Ticketing Options with Validating Carrier ...... 5-1 5.4 Ticket from Stored PQ Validating Carrier Override ...... 5-2 5.5 Settlement Type Qualifier (VM) in Fulfillment Commands ...... 5-2

Developer Administration Guide August 2014 Table of Contents v

6 Travel Journal Record

6.1 Introduction ...... 6-1 6.2 TJR Displays ...... 6-1

7 Ticketing Agreement

7.1 Introduction ...... 7-1 7.2 Ticketing Agreement Types ...... 7-1

8 No Ticketable Option

8.1 Introduction ...... 8-1 8.2 Pricing...... 8-1 8.3 Shopping ...... 8-1 8.4 Ticketing ...... 8-1

9 E x c h a n g e s

9.1 Introduction ...... 9-1 9.2 Automated Exchange Shop ...... 9-1 9.3 Non-Flight Documents (WFRM) ...... 9-1 9.4 Non – Database Tickets (WFR) ...... 9-1

G l o s s a r y

vi Table of Contents Developer Administration Guide August 2014

1 Getting Started 1

1.1 Introduction

In order for a travel agent to issue any ticket (paper or electronic) the following validation checks are required:

1. The selected validating carrier participates in ticket issuance settlement plan, such as ARC or BSP. 2. The validating carrier allows for the ticket to be issued with all marketing and operating carriers for the itinerary segments being fulfilled; interline agreements. 3. Agency issuing the ticket has the authority to issue on the carrier’s behalf. Currently, at time of Shopping and Pricing, the only validation check that occurs is item 2 (above); however, at ticket issuance, all three checks are performed. As a result of inconsistent validation checks between Shopping, Pricing, and Ticketing, agents receive fares that ultimately cannot be ticketed. This enhancement aligns the validating carrier logic across Shopping, Pricing, and Ticketing, returning the lowest ticketable fare solution.

Note The final check (number 3) will still be performed only at the time of ticketing. This document provides an overview of the various changes to system entries and responses included in this enhancement to validating carrier logic within Shopping, Pricing, and Ticketing. For any terms that may be unfamiliar to you, please review the Glossary in this guide.

1.2 Summary of Changes

Following is a summary of the major changes for each area included in this document: • Improved validating carrier selection at the time of Shopping, Pricing, and Ticketing to present the lowest ticketable fare option. – Alternate validating carriers offered when appropriate for interline itineraries. – Ability for non-participating settlement member carrier to designate a representative to issue tickets on their behalf by country. – Ability to systematically provide a validating carrier when a validating carrier cannot be assigned due to a lack of interline agreements or to return a message stating no ticketable option can be determined. • New trailer messages for Shopping, Pricing, and Ticketing. • Simplified TJR Carrier data. • Improved Validating Carrier table displays.

Developer Administration Guide August 2014 Introduction 1-1

• Improved Interline Agreement table displays. • XSTI Shopping qualifier functionality will no longer exist

1.3 About This Guide

This guide provides information on the validating carrier, interline, and GSA. Each chapter is as follows: • Chapter 1, “Getting Started” explains the purpose of the document and provides a functional overview and a description of the changes to the system. • Chapter 2, “Validating Carrier / Interline Agreement Displays” – describes displays for Validating Carrier / Interline agreement. • Chapter 3, “Pricing and Shopping” – describes new features of Pricing and Shopping logic. • Chapter 4, “Alternate Validating Carrier” – describes changes to the Price Quote create logic, as well as new information in the response. • Chapter 5, “Ticketing” – describes changes that will impact the fulfillment of tickets. • Chapter 6, “Travel Journal Record” – describes simplification of the Travel Journal Record (TJR). • Chapter 7, “Ticketing Agreement” – describes how the system will verify that valid ticketing agreements exist between the validating carrier and all marketing and operating carriers participating in the itinerary. • Chapter 8, “No Ticketable Option” – describes the No Ticketable options. • Chapter 9, “Exchanges” – describes how the validating carrier cannot be changed on any type of exchange transaction. • Glossary provides a glossary of terms used in this document.

1-2 About This Guide Developer Administration Guide August 2014

2 Validating Carrier / Interline 2 Agreement Displays

2.1 Introduction

The processes and data requirements associated with this enhancement require the creation of a new database to store all of the necessary ticketing agreement data and carrier relationships. As a result, new entries were created to allow the customer insight into this information. This chapter includes the following: • Validating carrier display (see this page). • Interline agreement display (see “Interline Agreement Display,” page 2-2). • Plausibility check (see “Plausibility Check,” page 2-3).

2.2 Validating Carrier D i s p l a y

This new entry is used to display the list of all carriers that can be ticketed in a specific country. Also, prime host (see Glossary) and settlement method can be specified. This entry consolidates the information currently retrieved with the entries W/BSPxx*, W/VC*, and W/BDA*.

2.2.1 E n t r y

The entry is WB*CC/PH/STC.

Entry Code Description

WB* Primary action code.

CC Two-character ISO country code for the point of sale country (required)

PH Two-character prime host (1S = Sabre, 1B = Abacus, or 1F = INFINI; optional qualifier). When not included in the entry, the system will assume the prime host of the agency PCC, found in that location’s TJR profile.

STC Three-character settlement method code (optional)

The entry allows only one value for each element. The optional elements are separated by a slash (/) and must be included in the specified order (prime host/settlement method). The associated web service is PO_ValidatingCarrierTableDisplayRQ. For additional information on this new web service, see Third Party Developers/Online Travel Agencies > Sabre Web Services > Interline Agreement Check/Plausibility Entries.

Developer Administration Guide August 2014 Introduction 2-1

2.2.2 E x a m p l e

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WB*GB/1S 2 SABRE VALIDATING CARRIERS FOR UNITED KINGDOM 3 4 ***BILLING AND SETTLEMENT PLAN*** 5 ELECTRONIC TICKETS ONLY 6 2J 4Q 6H 8M 9B 9F 9U 9W A3 AA AB AC 7 AF AH AI AM AR AS AT AV AY AZ B2 B6 8 BA BD BE BG BI BM BP BR BT BW CA CI 9 CM CX CY CZ DE DL DT DY EI EK ET EY 10 F7 FB FI FJ FV GA GF GR HA HM HR HU 11 HX HY IB IG IY IZ J2 JJ JL JP KC KE 12 KK KL KM KP KQ KU KX LA LG LH LN LO 13 LW LX LY MD ME MH MK ML MS MU NH NX 14 NZ OA OK OM OS OU OV OZ P0 PC PG PK 15 PR PW PX PY PZ QF QR QV R7 RC RJ RO 16 S3 S4 S7 SA SB SE SI SK SN SQ SU SV 17 SW SY T3 T4 T7 TG TK TM TN TP TS TU 18 TX UA UL UN UP US UT UU UX V3 VA VN 19 VR VS VT VX W2 W3 WB WM WY XB XL YM 20 YO ZH ZI 21 22 NEUTRAL VALIDATING CARRIERS 23 AC AF AM HR KL LA MS NZ QR SU UT 24 25 ***RUSSIAN TRANSITIONAL AIRLINE TICKET*** 26 ELECTRONIC TICKETS PREFERRED 27 SU 28 29 ***STUDENT TICKETING SATA*** 30 ELECTRONIC TICKETS PREFERRED 31 2A 3K 4M 9B 9F 9W AB AC AM AR AV AY 32 AZ B6 BA BD BE BI BR BT CI CM CX CZ 33 DL EK ET EY FI FJ FV GF HU JJ JQ KA 34 KE KQ KU LA LO LP LR LY MH MK MS MU 35 NH NZ OA OK OU OZ PG PX PZ QF QR RJ 36 S2 S7 SA SK SQ SU SW T0 TA TG TK TN 37 TP UL US UX VA VF VS WY XF XL

2.3 Interline Agreement Display

This new entry is used to display all interline agreements for the specified validating carrier in the specified country. The system response will also include the agreement type between the carriers. This entry reflects the information currently retrieved with W/*XX‡ALL.

2.3.1 E n t r y

The new entry is WBIA*XX/CC/PH

Entry Code Description

WBIA* Primary action code.

XX Two-character validating carrier’s airline code (required).

2-2 Interline Agreement Display Developer Administration Guide August 2014

Entry Code Description

CC Two-character ISO country code for the point of sale country (required).

PH Two-character prime host (1S, 1B or 1F; optional qualifier). When not included in the entry, the system will assume the prime host of the agency PCC, found in that location’s TJR profile.

The entry allows only one value for each element. The elements must be entered in the specified order and are separated by a slash (/). When the prime host is not included in the entry, the system will assume prime host of the agency pseudo city code (PCC). The associated web service is PO_ValidatingCarrierTableDisplayRQ. For additional information on this new web service, see Third Party Developers/Online Travel Agencies > Sabre Web Services > Interline Agreement Check/Plausibility Entries.

2.3.2 E x a m p l e

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WBIA*BA/GB/1S« 2 SABRE INTERLINE AGREEMENTS - BRITISH AIRWAYS P.L.C. 3 COUNTRY OF TICKET ISSUE - UNITED KINGDOM 4 SEE WETP*BA FOR ELECTRONIC TICKETING FUNCTIONAL CAPABILITIES 5 ***PAPER TICKETS - ONLY*** 6 JQ SS T0 WF XM 5T 7H A9 7 ***ELECTRONIC TICKETS*** 8 BA MUST HAVE ONE SEGMENT IN ITINERARY 9 ET EY FI FJ FV G3 GF GK HA HG HM HU 10 HX IG IR J2 JC JJ JL JP KA KC KE KK 11 KL KM KQ KU KX LA LG LH LI LP LR LX 12 LY ME MH MI MK MS MU MX NH NU NZ OA 13 OK OS OU OV OZ PG PR PW PZ QM QR RB 14 RJ RO S7 SA SN SQ SU SV SW TA TF TG

2.4 Plausibility Check

This new entry is used to determine whether a combination of participating carriers can be ticketed using the specified validating carrier in the specified settlement method and country. This validation does not include alternate or neutral validating carrier verification. For example, this Plausibility Check entry can be used to determine if your specified carrier can validate a manually priced ticket.

2.4.1 E n t r y

The entry is WB*CC‡AXX‡CRXX/XX/XX‡VMSTC‡XETR.

Entry Code Description

WB* Primary action code.

Developer Administration Guide August 2014 Plausibility Check 2-3

Entry Code Description

CC Two-character ISO country code (optional).

A Secondary action code identifying the intended validating carrier (required).

CR Secondary action code identifying the participating marketing and/or operating carriers. If the validating carrier is also participating in the journey, it must be included (required).

XX Two-character carrier airline code (required).

VM Secondary action code - settlement method (optional).

STC Three-character settlement type code (optional).

XETR Paper ticket override (optional).

This entry allows only one value for country code, validating carrier (A), and settlement method (VM). A minimum of one value is required, and a maximum of 32 values will be accepted for participating carrier (CR). When the country code is not included in the entry, the system will assume the requestor’s current location. The associated web service is PO_ValidatingCarrierCheckRQ. For additional information on this new web service, see Third Party Developers/Online Travel Agencies > Sabre Web Services > Interline Agreement Check/Plausibility Entries.

Notes • If the country code is included, it must be the first element following the WB* primary action code. All elements are separated by the Cross of Lorraine symbol (‡). • If the validating carrier (A) also participates in the itinerary, it must be listed as a participating carrier (CR) as well. • When the settlement method is not included in the entry, the system will assume the default settlement method of the requestor’s point of sale.

2.4.2 E x a m p l e

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WB*FR‡AAF‡CRAF/BA/LH‡VMBSP 2 VALIDATING CARRIER SPECIFIED - AF

2-4 Plausibility Check Developer Administration Guide August 2014

3 Pricing and Shopping 3

3.1 Int r o d u c t i o n

New Pricing and Shopping logic will be added in support of validating carrier processing, adding several new features: • Return the lowest fare response even if the required validating carrier is not the one assigned by default. • The ability to offer multiple validating carrier options applicable to the same fare solution. • The ability for the system to assign GSA as the validating carrier when the default validating carrier does not participate in the settlement plan and has identified a carrier to act as a sales agent on their behalf (see GSA in Glossary). • The ability for the system to assign a neutral validating carrier when no other options are applicable; if no neutral validating carrier is found, the system will no longer return a fare option. • A new qualifier to override the default settlement method assigned to the point of sale. • A new message in the response to advise when Category 15 (Sales Restrictions) text is present. • Message Definition Record (MDR) examples (see “Third-Party Developers/Online Travel Agencies,” page 3-18). Sabre Web Services will be sent in a separate document. This chapter includes the following: • Returning the lowest fare (see “Returning the Lowest Fare,” page 3-2). • Alternate validating carrier (see “Alternate Validating Carrier,” page 3-3). • General sales agent (see “General Sales Agent,” page 3-5). • Single neutral validating carrier (see “Single Neutral Validating Carrier,” page 3-9). • Settlement override qualifier (see “Settlement Override Qualifier,” page 3-12). • Category 15 text (see “Category 15 Text,” page 3-14). • No ticketable option (see “No Ticketable Option,” page 3-16). • Validating carrier override (see “Validating Carrier Override,” page 3-17). • Third-party developers/online travel agencies (see “Third-Party Developers/Online Travel Agencies,” page 3-18).

Developer Administration Guide August 2014 Introduction 3-1

3.2 Returning the Lowest Fare

Currently, at the time of Shopping and/or Pricing, the system identifies a single “default” validating carrier using industry-approved guidelines, using that carrier for all rules validation. As a result, lower fare options that require a different validating carrier present in the itinerary may be overlooked. To resolve this, the system will now examine fare solutions using the other marketing carriers present in the itinerary. When it is determined that a lower fare solution is applicable if a validating carrier (other than the default carrier) is used, that solution is returned. All rules associated with the fares in the solution are completely validated using the modified validating carrier to ensure the lowest solution is guaranteed. This section includes lowest fare examples.

3.2.1 Lowest Fare  E x a m p l e s

For example, in this itinerary:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 XX 324Y 10JAN 6 LAXDFW HK1 0600 1105 2 2 YY 943J 10JAN 6 DFWLHR HK1 1845 0935 11AUG 7 3 3 ZZ 491Y 12JAN 1 LHRDUB HK1 0640 0800

Using industry logic, the default validating carrier is carrier YY. The system will also price the itinerary assuming validating carriers XX and ZZ. Validating on ZZ results in a lower total fare amount. Carrier ZZ has valid interline agreements with both XX and YY. The fare solution is returned with trailer message advising that ZZ is the applicable validating carrier. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see “Shopping Response - JR,” page 3-3). • Shopping response – WPNI (see “Shopping Response – WPNI,” page 3-3).

3.2.1.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BASE FARE TAXES TOTAL 2 1- USD7987.00 466.80XT USD8453.80ADT 3 XT 403.00YQ 17.20US 5.00AY 32.60UB 4 9.00XF 5 7987.00 466.80 8453.80TTL 6 ADT-01 YA2XX J1Z1 7 LAX XX DFW Q27.91 921.86YA2XX YY X/LON ZZ DUB M7037.00J1z1 NUC 8 7986.77END ROE1.00 XFLAX4.5DFW4.5 9 VALIDATING CARRIER - ZZ

3-2 Returning the Lowest Fare Developer Administration Guide August 2014

3.2.1.2 Shopping Response - JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 XX2410Y 10JAN 6 LAXDFW SS1 0600 1105 3 1 YY 943j 10JAN 6 DFWLHR SS1 1845 0935 11AUG 7 4 1 ZZ 491Y 12JAN 1 LHRDUB SS1 0640 0800 5 6 1ADT 8453.01 8453.01 7 TOTAL FARE - USD 8453.01 8 VALIDATING CARRIER – ZZ

3.2.1.3 Shopping Response – WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 XX 324 H 10JAN J LAX DFW 0600a 1105a CR7 0 /E 5 1 YY 943 U 10JAN M DFW LHR 0645P 0935a 319 0 /E 6 1 ZZ 491 V 12JAN M LHR DUB 0640a 0800A 332 0 /E 7 1ADT 8453.80 8453.80 8 TOTAL FARE - USD 8453.80 9 VALIDATING CARRIER – ZZ

3.3 Alternate Validating Carrier

After the primary validating carrier has been determined, the system will verify if other marketing carriers participating in the itinerary return the same fare solution. Marketing carriers that participate in the itinerary and return an identical fare solution (same fare basis code, base fare amount, tax amounts and YQ/YR amounts) will be listed in new trailer message as alternate validating carriers. This comparison does not include commissions or OB fees. When multiple alternate validating carriers are determined, they are shown in the trailer message in the order in which they appear in the itinerary. A carrier that appears in the itinerary multiple times will only be listed once. Example:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 VALIDATING CARRIER– XX 2 ALTERNATE VALIDATING CARRIER/S – YY ZZ

Developer Administration Guide August 2014 Alternate Validating Carrier 3-3

3.3.1 Alternate Validating Carrier - E x a m p l e s

In the following itinerary:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 AS 154Y 09AUG 5 ANCLAX SS1 1130 1741 /DCAS /E 2 2 AA2410Y 10AUG 6 LAXDFW SS1 0600 1105 /DCAA /E 3 3 BA 192J 10AUG 6 DFWLHR SS1 1845 0935 11AUG 7 /DCBA

The default validating carrier for this itinerary is BA. Validating on carriers AA and AS returns the same fare basis code, base fare amount, tax, and YQ/YR amounts. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see this page). • Shopping response – WPNI (see this page).

3.3.1.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BASE FARE TAXES TOTAL 2 1- USD8790.00 598.15XT USD9388.15ADT 3 XT 452.00YQ 92.85US 3.90ZP 34.40US 4 7.50AY 7.50XF 5 8790.00 598.15 9388.15TTL 6 ADT-01 YASR1 YA2AA J1OWJB 7 ANC AS LAX619.38YASR1 AA DFW Q27.91 921.86YA2AA BA LON7221.00 8 J1OWJB NUC8790.15END ROE1.00 ZPANC XFANC3LAX4.5 9 VALIDATING CARRIER – BA 10 ALTERNATE VALIDATING CARRIER/S – AS AA

3.3.1.2 Shopping Response – JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 AA 278 W 9AUG T ANC LAX 1135A 0545P 757 0 /E 3 1 AA 1543 W 10AUG W LAX DFW 0600A 1105A S80 0 /E 4 1 BA 730 B 10AUG W DFW LHR 0645P 0750A 333 0 /E 5 1ADT 9388.15 9388.15 6 TOTAL FARE - USD 9388.15 7 VALIDATING CARRIER - BA 8 ALTERNATE VALIDATING CARRIER/S – AS AA

3.3.1.3 Shopping Response  WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 AA 278 W 9AUG T ANC LAX 1135A 0545P 757 0 /E 5 1 AA 1543 W 10AUG W LAX DFW 0600A 1105A S80 0 /E

3-4 Alternate Validating Carrier Developer Administration Guide August 2014

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 6 1 BA 730 B 10AUG W DFW LHR 0645P 0750A 333 0 /E 7 1ADT 9388.15 9388.15 8 TOTAL FARE - USD 9388.15 9 VALIDATING CARRIER - BA 10 ALTERNATE VALIDATING CARRIER/S – AS AA

3.4 General Sales Agent

When a carrier does not participate in a specific settlement method, they often identify another carrier to act on their behalf by operating as their General Sales Agent (GSA). With this enhancement, the system can recognize this condition and automatically assign the GSA carrier as the validating carrier in the response. When this occurs, the system will return a trailer message describing the substitution.

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 VALIDATING CARRIER – XX PER GSA AGREEMENT WITH ZZ

This section contains the following: • General sales agent validating carrier examples (see this page). • Multiple GSA examples (see “Multiple GSA: Examples,” page 3-6). • GSA for alternate validating carriers examples (see “GSA for Alternate Validating Carriers: Examples,” page 3-7).

3.4.1 General Sales Agent: Validating Carrier – E x a m p l e s

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 KL1001Y 10MAY 6 AMSLHR HK1 0715 0740 /DCKL

For the itinerary, the default validating carrier for this itinerary is KL, and the point of sale is Bermuda. KL has elected to not participate in the BSP for Bermuda and has designated DL as their GSA. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see “Shopping Response – JR,” page 3-6). • Shopping response – WPNI (see “Shopping Response – WPNI,” page 3-6).

3.4.1.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BASE FARE EQUIV AMT TAXES/FEES/CHARGES TOTAL 2 1- EUR307.00 BMD405.00 93.80XT BMD498.80ADT 3 XT 54.10YR 16.80CJ 20.30RN 2.60VV

Developer Administration Guide August 2014 General Sales Agent 3-5

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 4 307.00 405.00 93.80 498.80TTL 5 ADT-01 YFFWNL 6 AMS KL LON423.74YFFWNL NUC423.74END ROE0.724488 7 NONENDORSABLE 8 VALIDATING CARRIER - DL PER GSA AGREEMENT WITH KL

3.4.1.2 Shopping Response – JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 KL 1001 Y 10JUN T AMS LHR 0715A 0740A 73J 0 /E 3 1ADT 498.80 498.80 4 TOTAL FARE - USD 498.80 5 VALIDATING CARRIER – DL PER GSA AGREEMENT WITH KL

3.4.1.3 Shopping Response – WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 KL 1001 Y 10MAY T AMS LHR 0715A 0740A 73J 0 /E 5 1ADT 498.80 498.80 6 TOTAL FARE - USD 498.80 7 VALIDATING CARRIER – DL PER GSA AGREEMENT WITH BA

3.4.2 Multiple GSA: Examples

A carrier can designate more than one GSA. When two or more GSA carriers return the same lowest fare solution, the validating carrier trailer message will return BLANK, and the applicable GSA carriers will be listed as alternate validating carriers (in alphabetical order). When this occurs, the pricing result cannot be stored in the PQ record. The itinerary must be re-priced with one of the designated validating carriers. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see “Shopping Response – JR,” page 3-7). • Shopping response – WPNI (see “Shopping Response – WPNI,” page 3-7).

3.4.2.1 Pricing Response

3-6 General Sales Agent Developer Administration Guide August 2014

3.4.2.2 Shopping Response – JR

3.4.2.3 Shopping Response – WPNI

For an example showing attempted PQ creation with BLANK validating carrier, see “Store Price Quote  No Validating Carrier,” page 4-1.

3.4.3 GSA for Alternate Validating Carriers: Examples

If one of the alternate marketing carriers in the itinerary has designated a GSA, and their GSA returns the same fare solution, that GSA will be listed as an alternate validating carrier. When multiple alternate validating carriers apply, the carrier codes will be listed in itinerary order. GSA carriers are listed in the place of the carrier they are representing. A carrier that appears in the itinerary multiple times will only be listed once. For example:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 LA 502Y 09NOV 6 SCLMIA HK1 2345 0630 10NOV 7 /DCLA /E 2 2 AA5907Y 14NOV 4 MIAMAD HK1 2250 1335 15NOV 5 /DCAA /E 3 3 AY3184Y 20NOV 3 MADHEL HK1 1010 1530 /DCAY /E 4 4 AY 831Y 25NOV 1 HELLHR HK1 0800 0910 /DCAY /E 5 5 IB3167Y 30NOV 6 LHRMAD*HK1 1830 2200 /DCIB /E 6 6 IB6833B 01DEC 7 MADSCL*HK1 0020 0955 /DCIB /E

Developer Administration Guide August 2014 General Sales Agent 3-7

The point of sale is SCL. The default validating carrier is AA and using validating carrier AA produces the lowest fare. As described in this section, this fare solution is also checked using the other marketing carriers present in the journey, which determines that this same fare result is applicable using validating carrier AY or IB. Carrier AY has elected to not participate in the BSP for Chile, but has designated BA as their GSA. As a result, BA is offered as an alternate validating carrier even though they are not present in the itinerary.

Note BA must have third-party interline agreements with all marketing and operating carriers in the itinerary. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see this page). • Shopping response – WPNI (see “Shopping Response – WPNI,” page 3-9).

3.4.3.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WP 2 BASE FARE EQUIV AMT TAXES TOTAL 3 1- USD6389.00 EUR4828.00 1059.53XT EUR5887.53ADT 4 XT 578.80YR 238.02YQ 22.67ZQ 4.16YC 5 5.29XY 3.78XA 1.89AY 34.63JD 6 7.91QV 8.46FI 4.30DQ 1.20XU 7 111.46GB 33.56UB 3.40XF 8 6389.00 4828.00 1059.53 5887.53TTL 9 ADT-01 Y1EFFV BIF 10 SCL LA T/MIA AA MAD AY HEL M3398.00Y1EFFV AY LON IB X/MAD IB 11 SCL M2990.50BIF NUC6388.50END ROE1.00 XFMIA4.5 12 VALIDATING CARRIER – AA 13 ALTERNATE VALIDATING CARRIER/S – BA IB

3.4.3.2 Shopping Response – JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 LA 502 Y 09NOV T SCL MIA 1145p 0630A 73J 0 /E 3 1 AA 5907 Y 14NOV T MIA MAD 1050p 0135P 71j 0 /E 4 1 AY 3184 Y 20NOV T MAD HEL 1010A 1530P 53J 0 /E 5 1 AY 831 Y 25NOV T HEL LHR 0800A 0910A 47J 0 /E 6 2 IB 316 Y 30NOV T LHR MAD 0630P 1000A 35J 0 /E 7 2 IB 6833 B 01DEC T MAD SCL 1220A 0955A 64J 0 /E 8 1ADT 5887.53 5887.53 9 TOTAL FARE - USD 5887.53 10 VALIDATING CARRIER – AA 11 ALTERNATE VALIDATING CARRIER/S – BA IB

3-8 General Sales Agent Developer Administration Guide August 2014

3.4.3.3 Shopping Response – WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 LA 502 Y 09NOV T SCL MIA 1145p 0630A 73J 0 /E 5 1 AA 5907 Y 14NOV T MIA MAD 1050p 0135P 71j 0 /E 6 1 AY 3184 Y 20NOV T MAD HEL 1010A 1530P 53J 0 /E 7 1 AY 831 Y 25NOV T HEL LHR 0800A 0910A 47J 0 /E 8 2 IB 316 Y 30NOV T LHR MAD 0630P 1000A 35J 0 /E 9 2 IB 6833 B 01DEC T MAD SCL 1220A 0955A 64J 0 /E 10 1ADT 5887.53 5887.53 11 TOTAL FARE - USD 5887.53 12 VALIDATING CARRIER – AA 13 ALTERNATE VALIDATING CARRIER/S – BA IB

3.5 Single Neutral Validating C a r r i e r

When the marketing carriers in the itinerary or their GSA(s) do not have a valid interline ticketing agreement with all other marketing and operating carriers participating in the itinerary and cannot be used as validating carrier, an attempt will be made to find a ticketable solution using a neutral validating carriers. Neutral validating carriers will vary by country and settlement plan. An attempt to find a neutral validating carrier will only occur when no marketing carrier participating in the itinerary (or their GSA) can be used as a validating carrier because of invalid ticketing agreements. This will not be applied when pricing fails due to fare rule validation (for example, NO COMBINABLE FARES FOR CLASS USED). When only one neutral validating carrier results in the lowest fare solution, that carrier will be returned as the validating carrier in the response. This section contains the following: • Single neutral validating carrier (see this page). • Multiple neutral validating carriers (see “Multiple Neutral Validating Carriers,” page 3-11). • Multiple neutral validating carriers examples (see “Multiple Neutral Validating Carriers – Examples,” page 3-11).

3.5.1 Single Neutral Validating Carrier – E x a m p l e s

When the system finds a single neutral validating carrier, it will be returned as the validating carrier in the pricing response. For example:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 IB7441V 20SEP 5 LHRMAD*HK1 0620 0940 /DCIB /E 2 OPERATED BY BRITISH AIRWAYS 3 2 IB3870V 20SEP 5 MADAGP*HK1 1145 1255 /DCIB /E 4 OPERATED BY IBERIA EXPRESS AIRLINE 5 3 VY5630H 26SEP 4 AGPBCN HK1 0700 0830 /DCIB /E 6 4 IB7470H 26SEP 4 BCNLHR HK1 1015 1135 /DCIB /E

Developer Administration Guide August 2014 Single Neutral Validating Carrier 3-9

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 7 OPERATED BY BRITISH AIRWAYS

In this example, IB is the validating carrier, with BA and VY as possible alternate validating carriers. Neither BA nor IB have an interline agreement with VY. The system finds that carrier HR can issue tickets in London and has an interline ticketing agreement with all other carriers in the itinerary. As a result, the system assigns HR as the validating carrier. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see this page). • Shopping response – WPNI (see this page).

3.5.1.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BASE FARE EQUIV AMT TAXES TOTAL 2 1- GBP1114.00 USD1709.00 260.10XT USD1969.10ADT 3 XT 109.00YQ 26.50YR 19.90GB 43.40UB 4 45.90JD 15.40QV 5 1114.00 1709.00 260.10 1969.10TTL 6 ADT-01 YIF 7 LON IB X/MAD IB AGP M860.18IB X/BCN IB LON M860.18NUC1720.36 8 END ROE0.647533 9 VALIDATING CARRIER – HR

3.5.1.2 Shopping Response - JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 IB 7441 V 20SEP Q LHR MAD 0620A 0940A 321 0 /E 3 OPERATED BY / BRITISH 4 1 IB 3870 V 20SEP Q MAD AGP 1145A 1255p 32S 0 /E 5 OPERATED BY / IBERIA 6 2 VY 5630 H 26SEP F AGP BCN 0700A 0830A 32S 0 /E 7 2 IB 7470 H 26SEP F BCN LHR 1015A 1135A 346 0 /E 8 1ADT 1969.10 1969.10 9 TOTAL FARE - USD 1969.10 10 VALIDATING CARRIER – HR

3.5.1.3 Shopping Response - WPNI

3-10 Single Neutral Validating Carrier Developer Administration Guide August 2014

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 6 OPERATED BY / IBERIA 7 2 VY 5630 H 26SEP F AGP BCN 0700A 0830A 32S 0 /E 8 2 IB 7470 H 26SEP F BCN LHR 1015A 1135A 346 0 /E 9 1ADT 1969.10 1969.10 10 TOTAL FARE - USD 1969.10 11 VALIDATING CARRIER – HR 12

3.5.2 Multiple Neutral Validating Carriers

When two or more neutral validating carriers return the same lowest fare solution, the validating carrier trailer message will return BLANK, and the applicable neutral validating carriers will be listed as optional validating carriers (in alphabetical order). When this occurs, the pricing result cannot be stored in the PQ record. The itinerary must be re-priced with one of the designated validating carriers.

3.5.3 Multiple Neutral Validating Carriers – E x a m p l e s

For example, IB is the validating carrier, with BA and VY as possible alternate validating carriers. Neither BA nor IB have an interline agreement with VY. The system finds that carriers HR and YO can both issue tickets in London, have interline ticketing agreements with all other carriers in the itinerary and the fare amount is the same. As a result, the system does not choose a validating carrier. Instead, the fare response is offered with a message advising the possible validating carriers. This section contains the following: • Pricing response (see this page). • Shopping response – JR (see “Shopping Response – JR,” page 3-12). • Shopping response – WPNI (see “Shopping Response - WPNI,” page 3-12).

3.5.3.1 Pricing Response

Developer Administration Guide August 2014 Single Neutral Validating Carrier 3-11

3.5.3.2 Shopping Response – JR

3.5.3.3 Shopping Response - WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 IB 7441 V 20SEP Q LHR MAD 0620A 0940A 321 0 /E 5 OPERATED BY / BRITISH 6 1 IB 3870 V 20SEP Q MAD AGP 1145A 1255p 32S 0 /E 7 OPERATED BY / IBERIA 8 2 VY 5630 H 26SEP F AGP BCN 0700A 0830A 32S 0 /E 9 2 IB 7470 H 26SEP F BCN LHR 1015A 1135A 346 0 /E 10 1ADT 1969.10 1969.10 11 TOTAL FARE - USD 1969.10 12 VALIDATING CARRIER – 13 OPTIONAL VALIDATING CARRIERS – HR YO

For an example showing attempted PQ creation with BLANK validating carrier, see “Store Price Quote  No Validating Carrier,” page 4-1.

3.6 Settlement Override Qualifier

Some countries offer multiple settlement type methods (for example. BSP, TCH, and GEN). Generally, one settlement type is designated as the default. For example, the default settlement plan for the United States, Puerto Rico and the U.S. Virgin Islands is ARC. If the user wants to ticket through a different settlement plan, a settlement method override will be required. With this enhancement, Sabre is introducing a new pricing qualifier: VM. You can include this qualifier in the pricing entry when a specific settlement method (other than the country default) is desired. The new ticketing method override consists of the new secondary action code VM (Validating Method) and a three-character value to identify the ticketing settlement method. Possible types are:

3-12 Settlement Override Qualifier Developer Administration Guide August 2014

• BSP Billing and Settlement Plan – most common settlement method. • ARC Airline Reporting Corporation – settlement method used in US/PR/VI • TCH Transport Clearing House – settlement method used in RU/XU • GEN Generic Transitional Airline Ticket – direct ticketing using a specific airline’s stock. • RUT Russian Transitional Airline Ticket (TAT) – applicable to Aeroflot (SU) stock only. • PRT Philippines TAT – applicable to Philippine Airlines (PR) stock only. • SAT Student Airline Ticketing Agreement • KRY Student ticketing (Kilroy only). There will be no trailer message indicating the ticketing settlement method. When a settlement method is specified that is not valid for the point of sale, a failure will occur and the following error message will be returned:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 INVALID SETTLEMENT METHOD FOR POINT OF SALE

This section contains settlement override qualifier examples.

3.6.1 Settlement Override Qualifier - E x a m p l e s

For the following itinerary, with WAW as the point of sale:

BSP is the default settlement plan for the point of sale. The agent wants to report this ticket through GENTAT, which is also a valid settlement method for Poland. This section contains the following: • Pricing response example (see this page). • Shopping response example – JR (see “Shopping Response Example - JR,” page 3-14). • Shopping response example – WPNI (see “Shopping Response Example – WPNI,” page 3-14).

3.6.1.1 Pricing Response Example

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WPVMGEN 2 BASE FARE TAXES TOTAL 3 1- PLN27296.00 3024.93XT PLN30320.93ADT 4 XT 1801.04YQ 60.00XW 0.87ND 522.07GB 5 332.03UB 156.94AU 151.98WY

Developer Administration Guide August 2014 Settlement Override Qualifier 3-13

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 6 27296.00 3024.93 30320.93TTL 7 ADT-01 YIF 8 WAW LO LON QF SYD M4207.70YIF QF LON LO WAW M4207.70YIF NUC 9 8415.40END ROE3.24357 10 VALIDATING CARRIER - LO

3.6.1.2 Shopping Response Example - JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 JR.WAW/S-OYLHR10DEC0700/S-OYSYD11DEC2100/S-OYLHR20DEC1700/S-OYWA 2 W22DEC1730/VMGEN 3 ITINERARY OPTION 1 4 1 LO 281 Y 10DEC W WAW LHR 0745A 0935A 734 0 /E 5 2 QF 2 Y 11DEC Q LHR SYD 0930P 0630A 388 1 /E 6 3 QF 1 Y 20DEC W SYD LHR 0520p 0620a 774 0 /E 7 4 LO 280 K 22DEC Q LHR WAW 0550P 0925P 398 1 /E 8 1ADT 30320.93 30320.93 9 TOTAL FARE - USD 30320.93 10 VALIDATING CARRIER – LO

3.6.1.3 Shopping Response Example – WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WPNI‡VMGEN 2 BARGAIN FINDER PLUS IN PROGRESS PLEASE WAIT 3 WPNI‡VMGEN 4 CURRENT ITINERARY-LOWER AVAIL CLASS OF SERVICE FOUND 5 1 LO 281 Y 10DEC W WAW LHR 0745A 0935A 734 0 /E 6 2 QF 2 Y 11DEC Q LHR SYD 0915P 0655A 388 1 /E 7 3 QF 1 Y 20DEC W SYD LHR 0515p 0620a 774 0 /E 8 4 LO 280 K 22DEC Q LHR WAW 0550P 0925P 398 1 /E 9 1ADT 30320.93 30320.93 10 TOTAL FARE - USD 30320.93 11 VALIDATING CARRIER – QF

3.7 Category 15 Text

You can use automated rules Category 15 (Sales Restrictions) to provide various rule restrictions, including validating carrier. If this restriction information is filed within the category as data, the system applies the rule restriction. However, if the carrier files this information as text data only, it cannot be applied to the fare. As a result, the customer can ticket a fare with an incorrect validating carrier. To reduce this risk, the system will check each fare in the Pricing or Shopping response for the presence of Sales Restrictions text. If present on any fare, a trailer message will be returned in the pricing and shopping responses, advising the customer to check the rules display for the fares to be sure an incorrect validating carrier is not used.

Note Not all Sales Restrictions text refers to the validating carrier, and the note will appear any time the text exists, even if it pertains to other Sales Restrictions.

3-14 Category 15 Text Developer Administration Guide August 2014

3.7.1 Category 15 Text Examples

This section contains the following: • Pricing response (see this page). • Shopping response – JR (see this page). • Shopping response – WPNI (see this page).

3.7.1.1 Pricing Response

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BASE FARE TAXES TOTAL 2 1- USD1679.00 576.10XT USD2255.10ADT 3 XT 428.00YQ 34.40US 5.50YC 7.00XY 4 5.00XA 2.50AY 17.80DE 52.80RA 5 14.60UP 4.00LQ 4.50XF 6 1679.00 576.10 2255.10TTL 7 ADT-01 MHX0NCE 8 MIA LH X/FRA LH DUB839.50MHX0NCE LH X/FRA LH MIA839.50MHX0NCE 9 NUC1679.00END ROE1.00 XFMIA4.5 10 NONREF/0VALUAFTDPT/CHGFEE 11 VALIDATING CARRIER - LH 12 CAT 15 SALES RESTRICTIONS FREE TEXT FOUND – VERIFY RULES

3.7.1.2 Shopping Response - JR

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 ITINERARY OPTION 1 2 1 AA 278 W 9AUG T MIA FRA 1135A 0545A 757 0 /E 3 2 LH 1543 W 10AUG W FRA DUB 0600A 1105A S80 0 /E 4 2 LH 730 B 10AUG W DUB MIA 0645P 1150P 333 0 /E 5 1ADT 2255.10 2255.10 6 TOTAL FARE - USD 2255.10 7 VALIDATING CARRIER – LH 8 CAT 15 SALES RESTRICTIONS FREE TEXT FOUND – VERIFY RULES

3.7.1.3 Shopping Response – WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 BARGAIN FINDER PLUS ITINERARY OPTIONS 2 3 OPTION 1 4 1 AA 278 W 9AUG T MIA FRA 1135A 0545A 757 0 /E 5 2 LH 1543 W 10AUG W FRA DUB 0600A 1105A S80 0 /E 6 2 LH 730 B 10AUG W DUB MIA 0645P 1150P 333 0 /E 7 1ADT 2255.10 2255.10 8 TOTAL FARE - USD 2255.10 9 VALIDATING CARRIER – LH 10 CAT 15 SALES RESTRICTIONS FREE TEXT FOUND – VERIFY RULES

Developer Administration Guide August 2014 Category 15 Text 3-15

3.8 No Ticketable Option

When the system has processed all validating carrier options and is not able to return any pricing solution for the selected itinerary using the default validating carrier, a GSA, or a neutral validating carrier, the system will return the following error message:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 NO VALID TICKETING AGREEMENTS FOUND

This message will only be returned when all ticket agreement validation fails. This message does not imply that fare rule validation failed. Shopping will only return ticketable fare options. Ticketing agreement validation is done before fare rule validation. If ticketing agreement validation passes, but fare rule combination fails, the system will return the existing applicable pricing error messages. Example:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 NO COMBINABLE FARES FOR CLASS USED

When Pricing is unable to determine a single primary validating carrier, but finds two or more alternate or optional validating carriers in response to a WPRQ entry, PQ/Enhanced PQ will be inhibited. No fare solution is returned. Instead, the following error message is returned:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 UNABLE TO RETAIN PQ – MULTIPLE VAL CARRIERS APPLY – USE WP.

For example, the point of sale for the following itinerary is Venezuela. DL does not participate in the settlement plan and has designated both KL and AF as their GSA for this point of sale. Validating on both carriers returns the same fare solution.

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 DL 802Y 10MAY 6 CCSATL*SS1 0800 1302 /DCDL /E 2 2 DL 14Y 10MAY 6 ATLFRA*SS1 1630 0755 11MAY 7 /DCDL /E 3 3 DL 15Y 16MAY 5 FRAATL*SS1 1015 1432 /DCDL /E 4 4 DL 781Y 16MAY 5 ATLCCS*SS1 1740 2127 /DCDL /E

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 UNABLE TO RETAIN PQ – MULTIPLE VAL CARRIERS APPLY – USE WP.

The customer must re-price the itinerary, specifying a validating carrier in the entry. The system verifies schedules to ensure marketing and operating carrier information are valid at the time of pricing. If the booked segments are no longer found, pricing will fail, and the system will

3-16 No Ticketable Option Developer Administration Guide August 2014

return an error message indicating the presence of an invalid segment, including the invalid carrier and flight number.

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 INVALID SEGMENT XX1111

If there are multiple invalid flight segments in the itinerary, only the first one is identified. This applies to segments that are not subject to schedule change notifications (such as passive segments).

3.9 Validating Carrier Override

When the validating carrier override entry of Axx is used, the only validations will be participation in the settlement plan, interline agreements, and GSA (if applicable). There will be no attempt to find alternate or neutral validating carriers, and there will be no change to the trailer message currently returned for validating carrier overrides.

3.9.1 Validating Carrier Override Examples

This section contains the following: • Pricing response (see this page). • Shopping response – JR (see this page). • Shopping response – WPNI (see “Shopping Response Example - WPNI,” page 3-18).

3.9.1.1 Pricing Response

For example, the following itinerary is priced using carrier LO as the validating carrier:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 1 LO 281Y 10DEC 2 WAWLHR SS1 0745 0935 /DCLO /E 2 2 QF 2Y 11DEC 3 LHRSYD SS1 2130 0630 13DEC 5 /DCQF /E 3 3 QF 1Y 20DEC 5 SYDLHR SS1 1720 0620 21DEC 6 /DCQF /E 4 4 LO 280Y 22DEC 7 LHRWAW SS1 1750 2125 /DCLO /E 5 6 WPALO 7 BASE FARE TAXES TOTAL 8 1- PLN25561.00 3024.93XT PLN28585.93ADT 9 XT 1801.04YQ 60.00XW 0.87ND 522.07GB 10 332.03UB 156.94AU 151.98WY 11 25561.00 3024.93 28585.93TTL 12 ADT-01 YGOLD01 YIF YGOLD01 13 WAW LO LON537.98YGOLD01 QF SYD3402.14YIF QF LON3402.14YIF LO 14 WAW537.98YGOLD01 NUC7880.24END ROE3.24357 15 RESTRICTIONS APPLY/ PER FARE COMPONENT 16 VALIDATING CARRIER SPECIFIED - LO

3.9.1.2 Shopping Response - JR

There is no JR command for Validating Carrier Override.

Developer Administration Guide August 2014 Validating Carrier Override 3-17

3.9.1.3 Shopping Response Example - WPNI

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WPNI‡LO« 2 BARGAIN FINDER PLUS IN PROGRESS PLEASE WAIT 3 WPNI‡LO 4 CURRENT ITINERARY-LOWER AVAIL CLASS OF SERVICE FOUND 5 1 LO 281Y 10DEC 2 WAWLHR SS1 0745 0935 /DCLO /E 6 2 QF 2Y 11DEC 3 LHRSYD SS1 2130 0630 13DEC 5 /DCQF /E 7 3 QF 1Y 20DEC 5 SYDLHR SS1 1720 0620 21DEC 6 /DCQF /E 8 4 LO 280Y 22DEC 7 LHRWAW SS1 1750 2125 /DCLO /E 9 10 1ADT 28585.00 28585.00 11 TOTAL FARE - USD 28585.00 12 VALIDATING CARRIER SPECIFIED – LO

3.10 T h i r d - Party Developer s / Online Travel Agencies

Changes to multiple web services have taken place to incorporate the Validating Carrier functionality. New response elements have been added. The possible elements are listed below.

Response Elements

VALIDATING CARRIER - XX VALIDATING CARRIER SPECIFIED - XX VALIDATING CARRIER – XX PER GSA AGREEMENT WITH ZZ NO VALID TICKETING AGREEMENTS FOUND ALTERNATE VALIDATING CARRIER/S – XX ZZ ALTERNATE VALIDATING CARRIER/S - XX VALIDATING CARRIER - OPTIONAL VALIDATING CARRIERS – XX ZZ CAT 15 SALES RESTRICTIONS FREE TEXT FOUND – VERIFY RULES INVALID SETTLEMENT METHOD FOR POINT OF SALE XX NOT VALID FOR SETTLEMENT METHOD XX HAS NO INTERLINE TICKETING AGREEMENT WITH ZZ PRICED USING RULE OVERRIDE-FOLLOWING FARE RULES NOT MET SALES RESTRICTIONS INVALID SEGMENT ZZ1234 PAPER TICKET NOT PERMITTED

This section contains the following: • Sabre Web Services (see “Sabre Web Services,” page 3-19). • Sabre Data Source (see “Sabre Data Source,” page 3-21). • Sabre Data Source – ticketing (see “Sabre Data Source  Ticketing,” page 3-22).

3-18 Third-Party Developers/Online Travel Agencies Developer Administration Guide August 2014

3.10.1 S a b r e Web Services

This section contains the following: • Shopping (see this page). • Pricing (see “Pricing,” page 3-20). • Interline agreement check/plausibility entries (see “Interline Agreement Check/Plausibility Entries,” page 3-21).

3.10.1.1 Shopping

This section contains the following: • WPNI (see this page). • JR (see this page). • Bargain Finder Max (see this page).

3.10.1.1.1 WPNI

BargainFinderPlusLLSRQv1.x/v2.x: BargainFinderPlusRS/PricedItineraries/PricedItinerary/HeaderInformation/Text BargainFinderPlusRS/PricedItineraries/PricedItinerary/HeaderInformation/ValidatingCarrier/@Code

3.10.1.1.2 JR

OTA_AirLowFareSearchLLSRQv1.x/v2.x: OTA_AirLowFareSearchRS/PricedItineraries/PricedItinerary/HeaderInformation/Text OTA_AirLowFareSearchRS/PricedItineraries/PricedItinerary/HeaderInformation/ValidatingCarrier/ @Code

3.10.1.1.3 Bargain Finder Max

BargainFinderMaxRQ – v1.7.7 BargainFinderMax_ADRQ – v1.7.7 BargainFinderMax_SAPT – v1.7.7

Developer Administration Guide August 2014 Third-Party Developers/Online Travel Agencies 3-19

New Request / Response elements:

Request/Response Type Format/Example

OTA XML Request Settlement Method OTA_AirLowFareSearchRQ/TravelPreferences/Settl Override ementMethod/Text

OTA XML Response Trailer Message - OTA_AirLowFareSearchRS/PricedItineraries/PricedI OTA Response Tag tinerary/AirItineraryPricingInfo/PTC_FareBreakdown s/PTC_FareBreakdown/PassengerFare/TPA_Exten sions/Messages

Sterilized Alternate and Neutral : Validating Carrier : Serialize alternate validating carrier in a TK separate XML UA element. LO

3.10.1.2 Pricing

This section contains the following: • WP (see this page). • Orchestrated Service Calling Air Price (see this page).

3.10.1.2.1 WP

OTA_AirPriceLLSRQv1.x/2.x: OTA_AirPriceRS/PriceQuote/MiscInformation/HeaderInformation/Text OTA_AirPriceRS/PriceQuote/MiscInformation/HeaderInformation/ValidatingCarrier/@Code

3.10.1.2.2 Orchestrated Service Calling Air Price

EnhancedAirBookRQv2.x EnhancedAirBookRS/OTA_AirPriceRS/PriceQuote/MiscInformation/HeaderInformation/Text EnhancedAirBookRS/OTA_AirPriceRS/PriceQuote/MiscInformation/HeaderInformation/Validating Carrier/@Code

3-20 Third-Party Developers/Online Travel Agencies Developer Administration Guide August 2014

3.10.1.3 Interline Agreement Check/Plausibility Entries

The following table contains descriptions for two new web services:

New Service Description

PO_ValidatingCarrierTableDisplayRQ This new web service provides the ability to identify the carriers that can be ticketed in a specific country or the interline agreements applicable to a specific validating carrier within a country.

PO_ValidatingCarrierCheckRQ This new web service provides the ability to determine if a combination of participating carriers can be ticketed using the specified validating carrier in the specified settlement method and country.

Specific information for both of these web services will be included in the DRC and release notes.

3.10.1.4 Ticketing

All existing ticketing Web Services remain unchanged.

3.10.2 Sabre Data S o u r c e

Any new trailer messages, such as Alternate Validating Carrier, Optional Validating Carrier, Category 15 (Sales Restrictions) text, and GSA will be added as follows:

Message Segment Data Element

PRDATA 00Z7

3.10.2.1 Sabre Data Source – Pricing/Shopping

Example:

Segment Tag – PRDATA

Nesting Level – 1 Existence – Optional Repeat Factor – 1

Tag Type Length Opt Rpt Desc Example

Min Max VALIDATING CARRIER – 00Z7 C 1 250 Y 999 Free XX, ALTERNATE Form VALIDATING CARRIER – YY Text ZZ, CAT 15 SALES RESTRICTIONS FREE TEXT FOUND – VERIFY RULES

Developer Administration Guide August 2014 Third-Party Developers/Online Travel Agencies 3-21

3.10.3 S a b r e D a t a S o u r c e  T i c k e t i n g

There are no applicable Sabre Data Source changes.

3-22 Third-Party Developers/Online Travel Agencies Developer Administration Guide August 2014

4 Price Quote 4

4.1 Introduction

As a result of the new validation and additional data returned from Pricing, there are changes to the Price Quote create logic, as well as new information in the response.

4.2 Alternate Validating Carrier F i e l d

A new field will be added to the Price Quote record when the pricing solution has multiple alternate carriers that can be selected. These carriers will appear in the Alternate Validating Carrier field.

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 PQ 1 2 3 BASE FARE TAXES TOTAL 4 PLN27296.00 2429.50XT PLN29725.50ADT 5 XT 1820.08YQ 60.00XW 0.87ND 229.76UB 6 161.95AU 156.84WY 7 ADT-01 YIF 8 WAW LO X/LON QF SYD M4207.85YIF QF X/LON LO WAW M4207.85YIF 9 NUC8415.70END ROE3.24346 10 VALIDATING CARRIER - QF 11 01 O WAW BA 279Y 10DEC 300P YIF 10DEC14 30K 12 02 X LHR QF 2Y 10DEC 930P YIF 10DEC14 30K 13 03 O SYD QF 1Y 20DEC 520P YIF 10DEC14 30K 14 04 X LHR LO 282Y 21DEC 1035A YIF 10DEC14 30K 15 WAW 16 FARE SOURCE - SITA 17 VALIDATING CARRIER-BA 18 ALTERNATE VALIDATING CARRIER/S – QF LO

The following table describes only the lines that have changed:

Line Position Description

1-17 1-63 Same as current PQ Record.

18 1-32 Label: ALTERNATE VALIDATING CARRIER/S –

18 33-63 List of Alternate Validating Carrier(s) (when applicable).

4.3 Store Price Quote  N o Validating Carrier

Storage of a price quote will be inhibited in the event pricing is unable to determine a single validating carrier.

Developer Administration Guide August 2014 Introduction 4-1

When no validating carrier is returned in the pricing response, a list of optional carriers will be returned. You will need to choose one of the optional carriers before storing the fare.

Description Entry Response

PQ command following a pricing PQ OPTIONAL VALIDATING CARRIER – XX ZZ response with no validating carrier, only optional carriers

Price and retain when no WPRQ UNABLE TO RETAIN PQ - MULTIPLE VAL CARRIERS validating carrier, only optional APPLY - USE WP carriers

4-2 Store Price Quote ( No Validating Carrier Developer Administration Guide August 2014

5 Ticketing 5

5.1 Introduction

As a result of the new validating carrier logic, there are some changes that will impact the fulfillment of tickets. These changes include: • No longer requiring a user to enter a Validating Carrier in the ticketing fulfillment command. (BSP agents only). • The PQ record showing Alternative Carrier(s) that can be used as the Validating Carrier to achieve the same fare level. • Override Validating Carrier in Ticket from stored PQ record. This chapter includes the following: • Removal of manual entry of validating carrier (see this page). • Ticketing options with validating carrier (see this page). • Ticket from stored PQ validating carrier override (see “Ticket from Stored PQ Validating Carrier Override,” page 5-2). • Settlement type qualifier (VM) in fulfillment commands (see “Settlement Type Qualifier (VM) in Fulfillment Commands,” page 5-2).

5.2 Removal of Manual E n t r y o f V a lidating Carrier

For BSP users (except Canada), the ticketing command (W# or FP line) will no longer require the entry of the validating carrier (#Axx). The ticket will issue using the validating carrier either returned from pricing or stored in the fare record (if applicable). The validating carrier instruction will become optional for all users and will be used as an override when included manually in the ticket entry. The qualifier remains mandatory when issuing a ticket or creating an FP line using a manual fare record that does not contain a validating carrier.

5.3 Ticketing Options with Validating Carrier

Condition Example Entry Response

Ticketing entry with no validating carrier override W¥FCASH Ticket issued using validating – pricing is able to return a pricing solution carrier determined by the system

Developer Administration Guide August 2014 Introduction 5-1

Condition Example Entry Response

Ticket entry with no validating carrier override – W¥FCASH MULTIPLE VALIDATING pricing is able to return a pricing solution CARRIER OPTIONS - SQ TG UA however cannot determine a single primary SELECT ONE AND REPRICE validating, but returns two or more alternate or USING ¥A optional validating carriers Note: User must re-enter ticketing entry using one of the carriers shown in pricing response.

Ticketing entry with validating carrier override – W¥FCASH¥ADL Ticket issued using validating pricing is able to return a pricing solution carrier specified in ticketing entry

Ticketing entry with Price quote and validating W¥PQ¥FCASH¥ADL Ticket issued using validating carrier override – pricing returns a solution carrier specified in entry

Ticketing entry with Price quote and validating W¥PQ¥FCASH¥ADL NO VALID TICKETING carrier override – pricing does NOT return a AGREEMENTS FOUND solution

Ticketing a manual stored fare with override W¥PQ¥FCASH¥ADL Ticket issued using validating validating carrier in ticketing entry W¥T¥FCASH¥ADL carrier specified in entry

Ticketing a manual stored fare with no validating W¥PQ¥FCASH NEED VAL CARRIER carrier stored or specified in entry W¥T¥FCASH

5.4 Ticket from Stored PQ Validating Carrier Override

When a stored fare record contains a Validating Carrier and the user includes a Validating Carrier override (‡AXX) qualifier in the ticketing command and this carrier is neither the Validating Carrier nor one of the Alternate Carrier(s), the itinerary will be repriced based on the Validating Carrier entry. If the itinerary can be repriced using the specified carrier, the ticket will be issued at the new fare level with no warning to the user. If the itinerary cannot be repriced using the specified carrier, the system will return the following message:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 NO VALID TICKETING AGREEMENTS FOUND

5.5 Settlement Type Qualifier (VM) in Fulfillment C o m m a n d s

The new settlement type qualifier (#VMaaa) is not valid at time of fulfillment. If the #VM qualifier is used in any fulfillment requests, the following error will be returned:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 W‡ADL‡VMTCH‡KP0« 2 FORMAT - VM NOT VALID FOR TKT REQUESTS-0053

5-2 Ticket from Stored PQ Validating Carrier Override Developer Administration Guide August 2014

Note If the qualifier was used to store the fare at the time of ticketing the stored fare, the qualifier is ignored and no error is returned.

Developer Administration Guide August 2014 Settlement Type Qualifier (VM) in Fulfillment Commands 5-3

• • •

5-4 Settlement Type Qualifier (VM) in Fulfillment Commands Developer Administration Guide August 2014

6 Travel Journal Record 6

6.1 Introduction

The Travel Journal Record (TJR) is being simplified, and the current CARRIERS and ETR CARRIERS sections will be consolidated into a single field. At the time of ticket issuance, the system will validate this new field to ensure your agency has the authority to issue tickets on behalf of the validating carrier.

6.2 TJR Displays

This section contains the following: • Single settlement plan – BSP (authorized carriers) (see this page). • Multiple settlement plans – BSP (authorized carriers) (see “Multiple Settlement Plans – BSP/TAT/TCH (Authorized Carriers),” page 6-2). • Single settlement plan – ARC (restricted carriers) (see “Single Settlement Plan – ARC (Restricted Carriers),” page 6-2).

6.2.1 Single Settlement Plan – B S P ( Authorized Carriers )

The TJR display for an agency participating in a single settlement plan – BSP (authorized carriers) is as follows:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 W/TA*XX12 (Partial Display) 2 ID RECORD 3 PCC- XX12 4 NAME- sabre TRAVEL 5 6 TOTAL ACCESS - ACTIVE 7 DIRECT CONNECT AUX - ACTIVE 8 DIRECT CONNECT AIR - ACTIVE 9 BSP CARRIER - 10 AA AB AC AM AT AY AZ A3 BE BT BW B2 CA CI CY CZ DT DY ET FB 11 FI F7 GR HR HX IB IG IZ JP JU KK KP KX LG LO LX LY MK ML NX 12 NZ OA OM OV PR PY QV RA RO R7 SE SI SK SW SY S3 TM TP TU TX 13 T4 US UX VA VN VX WB W2 YO ZH ZI 2J 7V 8M 8U 9F 9U

Developer Administration Guide August 2014 Introduction 6-1

6.2.2 Multiple Settlement Plans – BSP/TAT/TCH (Authorized C a r r i e r s )

The TJR display for an agency participating in multiple settlement plans – BSP/TAT/TCH (authorized carriers) is as follows:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 W/TA*Xy12 (Partial Display) 2 ID RECORD 3 PCC- Xy12 4 NAME- fast TRAVEL 5 6 TOTAL ACCESS - ACTIVE 7 DIRECT CONNECT AUX - ACTIVE 8 DIRECT CONNECT AIR - ACTIVE 9 BSP CARRIER - 10 AA AB AC AM AT AY AZ A3 BE BT BW B2 CA CI CY CZ DT DY ET FB 11 FI F7 GR HR HX IB IG IZ JP JU KK KP KX LG LO LX LY MK ML NX 12 NZ OA OM OV PR PY QV RA RO R7 SE SI SK SW SY S3 TM TP TU TX 13 T4 US UX VA VN VX WB W2 YO ZH ZI 2J 7V 8M 8U 9F 9U 14 TAT CARRIERS- 15 SU 16 TAT CARRIERS - 17 XX 18 TCH CARRIERS - 19 XX

6.2.3 Single Settlement Plan – A R C ( Restricted Carriers )

The TJR display for an agency participating in single settlement plan – ARC (restricted carriers) is as follows:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 W/TA*XT12 (Partial Display) 2 ID RECORD 3 PCC- XT12 4 NAME- FASTWAY TRAVEL 5 6 TOTAL ACCESS - ACTIVE 7 DIRECT CONNECT AUX - ACTIVE 8 DIRECT CONNECT AIR - ACTIVE 9 ARC CARRIER - 10 KA S2 WN X2

6-2 TJR Displays Developer Administration Guide August 2014

7 Ticketing Agreement 7

7.1 Introduction

The system will verify valid ticketing agreements exist between the validating carrier and all marketing and operating carriers participating in the itinerary. Only operating carriers (as defined by SSIM - DEI50) will be considered for this validation.

7.2 T i c keting Agreement Types

This section contains descriptions of the ticketing agreement types.

7.2.1 Paper Ticket

There are no requirements other than an existing agreement. All paper ticket agreements cover both standard and third-party interline agreements. This applies to paper tickets only.

7.2.2 S t a n d a r d Interline Eticket Agreement ( IET)

The validating carrier must be a marketing carrier on the ticketed itinerary. This applies to electronic tickets only.

7.2.3 T h i r d - P a r t y Interline Eticket ( IET)

The validating carrier is not required to be a marketing carrier on the ticketed itinerary. This applies to electronic tickets only.

Developer Administration Guide August 2014 Introduction 7-1

• • •

7-2 Ticketing Agreement Types Developer Administration Guide August 2014

8 No Ticketable Option 8

8.1 Introduction

This chapter describes the No Ticketable options for Pricing, Shopping, and Ticketing.

8.2 P r i c i n g

When Pricing has processed all validating carrier options and is not able to return any pricing solution for the selected itinerary using the default validating carrier, GSA swap or neutral validating carrier, the system will return the following error message:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WP 2 NO VALID TICKETING AGREEMENTS FOUND

This message will only be returned when ticket agreement validation fails. This message does not imply that fare rule validation failed.

8.3 S h o p p i n g

When Shopping has processed a selected itinerary using the default validating carrier, GSA, or neutral validating carrier logic and is not able to validate the option, Shopping will not return this non-ticketable option. Shopping will replace this option with the next valid ticketable low fare option.

8.4 T i c k e t i n g

This section contains no ticketing options as follows: • Direct Ticketing (see this page). • Ticketing from PQ (see “Ticketing From PQ,” page 8-2). • Ticketing (see “Ticketing,” page 8-2).

8.4.1 Direct Ticketing

When a direct ticketing command is entered and the itinerary booked results in no pricing solution using the default validating carrier, GSA, or a neutral validating carrier.

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 W¥FCASH¥ADL 2 NO VALID TICKETING AGREEMENTS FOUND

Developer Administration Guide August 2014 Introduction 8-1

8.4.2 Ticketing From PQ

When a user tries to issue a ticket from a PQ record using a different validating carrier or alternate validating carrier than the ones displayed in the PQ, and this results in no pricing solution found using this carrier, a GSA, or neutral validating carrier, the system will respond with the following error message: NO VALID TICKETING AGREEMENTS FOUND.

8.4.3 T i c k e t i n g

The mandatory requirement of adding a validating carrier at the time of ticketing, exchange, or refund for non-ARC locations will be removed. The same forms of validations will be used for all settlement types.

8-2 Ticketing Developer Administration Guide August 2014

9 Exchanges 9

9.1 Introduction

The validating carrier cannot be changed on any type of exchange transaction. The system will only validate the settlement method, validating carrier participation, and interline ticketing agreements including ticket type (paper/ETR) for exchange/reissue transactions. There will be no attempt to process alternate validating carriers, GSA swap, or neutral validating carriers. This applies to Exchanges and Refunds, Automated Exchanges, and Exchange Shopping.

9.2 Automated Exchange Shop

Currently, Automated Exchange Shop returns options regardless of the validating carrier. The system will now return only ticketable options that apply to the validating carrier of the ticket to be exchanged.

9.3 N o n - F l ight Documents (WFRM)

A WFRM command for a non-flight document will require a printer to be designated in order to perform the necessary validation services. The printer assignment will allow the system to use ticket stock type of the designated printer for validation. If a printer is not assigned, the system will display the following error:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WFRM0068504765210/USD100.00 2 INVALID-ASSIGN TICKET PRINTER-3—1151

9.4 N o n – Database Tickets (WFR)

Currently, for WFR on a non-database paper or electronic ticket, regardless if requesting a refund or an exchange, the system displays an error on either Screen 10 or 12 requiring a printer assignment. Now, when the ticket is a non-database transaction, the error will be displayed after entry of the command, prior to mask processing. When this occurs, the existing error will be displayed:

1 2 3 4 5 6 123456789012345678901234567890123456789012345678901234567890123 1 WFR6182130077046#ASQ 2 INVALID-ASSIGN TICKET PRINTER-3—1151

Developer Administration Guide August 2014 Introduction 9-1

• • •

9-2 Non – Database Tickets (WFR) Developer Administration Guide August 2014

10 Glossary

Following is a glossary of terms listed in alphabetical order by term:

Term Description

Alternate Validating Carrier A marketing carrier who participates in the itinerary and returns the same fare solution as the default/primary validating carrier

ATPCO Airline Tariff Publishing Company

Automated Exchanges Sabre Exchange product that uses ATPCO’s Category 31 (CAT 31) rules for voluntary rerouting. The Sabre system interrogates these rules within Automated Exchanges at reissue time to determine if the rule allows itinerary changes, which fares you can use for the new ticket, and the change fees that apply. Note: Note available in all markets. This functionality requires a contract and has charges associated with it.

Automated Exchanges Shop Automated Exchanges shop allows you to reprice an itinerary, and in addition, provides a selection of low-fare alternate itineraries that you can select to change the ticket to. Automated Exchanges shop uses familiar, existing shopping qualifiers currently available in the Low Fare Search functionality. You can use a series of qualifiers to widen or narrow a search window when looking for alternate itineraries.

CAT 15/Category 15 Automated fare rule processing for Sales Restrictions. Allows carriers to file specific rules for identifying validating carriers that are permitted/nor permitted, restrict sales locations and specify sales and ticketing dates.

CAT 31/Category 31 Automated fare rule processing for voluntary changes filed through ATPCO. Allows carriers to file specific rules to apply after ticket issue for voluntary changes.

Default Validating Carrier The validating carrier determined by the system using Industry adopted guidelines, identified in the ATPCO Service Fees Overview – section 4.1 and IATA Resolution 852.

Direct Ticketing Subscriber carrier ticketing reported directly to carrier (includes GENTAT/TAT).

ETR Electronic Ticket Record

Exchange Ticket Old ticket to be used in an exchange.

EXCHANGE Transaction Type Wholly unused ticket when a change has been made to the first flight coupon

GSA General Sales Agent - a carrier representing another carrier for ticketing in a specific country and for a specific settlement plan. The GSA must have a third party ticketing agreement with the carrier they are representing and all other carriers participating in the itinerary to be considered a validating carrier.

Developer Administration Guide August 2014 Glossary 1

Term Description

Interline Types Standard – (Formerly Normal) - An interline agreement exists between the validating carrier and the carrier(s) in the itinerary. The validating carrier must be a marketing carrier in the itinerary being Shopped/Priced and Fulfilled. Third Party – (Formerly Hosted and Pseudo) - An interline agreement exists between the validating carrier and the carrier(s) in the itinerary. The validating carrier is not required to be in the itinerary as marketing or operating carrier.

I & I Invoice and Itinerary

Marketing Carrier The airline whose Airline Designator is recorded as the transporting carrier on the flight coupon(s).

MDR Message Definition Record

Neutral Validating Carrier A carrier who does not participate in an itinerary and is not the GSA for any marketing carrier in the itinerary, but has a third-party interline ticketing agreement with all marketing carriers in the ticketed itinerary.

Non-flight document Any document other than a flight document.

Optional Validating Carriers Describes a condition when there are two or more neutral validating carriers that can be assigned to the same lowest fare solution.

PIR Passenger Itinerary Receipt

Plausibility Check This new entry allows the customer to determine if a combination of participating carriers can be ticketed using the specified validating carrier in the specified settlement method and country. This validation does not include alternate or neutral validating carrier verification.

Prime Host A term used in the TJR to define the GDS. Example: Prime Host: Abacus (1B), INFINI (1F), Sabre (1S).

POS Point of Sale

PQ Price Quote record

PQR Price Quote REISSUE record.

Refunds and Exchanges Sabre Refunds and Exchanges product that prompts the user through a series of fill in format screens in which the user enters the applicable exchange or refund data. The system: • Determines the original ticket value and the new ticket value in an exchange transaction. • Compares the original ticket value to any applicable flown segment value. • Calculates the refund or exchange amount due to/from the passenger. • Processes the transaction. • Issues the applicable documents. • Retains the transaction information.

REISSUE Transaction Type Wholly unused ticket when a change has been made to other than the first flight coupon and all partially used tickets.

2 Glossary Developer Administration Guide August 2014

Term Description

Settlement Plan The location to which the agency is reporting the sale. EG: BSP/ARC/TCH

SDS Sabre Data Stream

SWS Sabre Web Services

SVT Sabre Virtually There

TAT Transitional Airline Ticket

TFR Ticket Fare Record (used by Abacus for ticket issuance).

TFSF Ticket From Stored Fare.

TJR Travel Journal Record

Types of Tickets Electronic Ticket - A system generated document that can be printed by an agency or transmitted electronically. Paper Ticket – An accountable document printed by a designated ticket printer and used by the customer at time of check-in.

Validating Carrier The issuing airline whose numeric airline code precedes the document number

Developer Administration Guide August 2014 Glossary 3

• • •

4 Glossary Developer Administration Guide August 2014