user guide - sabre

Verison 1.5

August 2019

User Guide

Exchange Shop Web Service

TKT_ExchangeShoppingRQ

Document Edition 1.5 (August 2019)

Template Version 2.0

This documentation is the confidential and proprietary intellectual

property of the Sabre Airline Solutions® business. 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

Airline Solutions is strictly prohibited.

Sabre, the Sabre logo, Sabre Airline Solutions, the Sabre Airline

Solutions logo, Sabre Travel Network, the Sabre Travel Network

logo, AirCentre™, AirVision™, SabreSonic® are trademarks and/or

service marks of an affiliate of Sabre Inc. All other trademarks,

service marks and trade names are the property of their respective

owners.

© 2014 Sabre Inc. All rights reserved.

Document Revision Information

Date Revised by Reason for Revision Revision Control

No.

08/26/2014 Ewa Młyńska

Changed the product name from Exchange Shopping to Exchange Shop.

version 1.1

Added an additional description of system behavior in the transaction where the PTC was not stored in the VCR and “Override Passenger Type Code” pricing parameter was not applied on page 264.

Added “Missing PTC” error to the Table of Common Business Validation Errors on page 459.

Added the Ability to Change Country of Origin section on page 57.

Added the Non-Refundable Fare Amount section on page 311.

04/29/2015 Pawel Karol Kowalke Updated Community Portal information. Version 1.2

Updated Exchange Shop Requirements section (Segments, Shopping Options Returned) on page 6 and page 8.

Added new Error code “Requested number of options larger that the allowed Intellisell limit “ in Business Validation Errors section on page 444.

08/021/2016 Garry Harvie Added Calendar Shopping – 4.3.16

Added Frequent Flyer Tier and Customer Value Score – 4.3.17

Added Enhanced Response – 5.3

Version 1.3

01/31/2019 Komal Khera Updated new attribute @negotiatedFaresOnly added in v1.1.3 in section 4.3.18

Version 1.4

08/26/2019 Komal Khera Updated new attribute @TicketingRule added in v1.1.4 in section 4.3.19

Version 1.5

• • •

Table of Contents

Exchange Shop User Guide v Confidential and Proprietary Sabre Airline Solutions

Table of Contents

1 I n t r o d u c t i o n

1.1 Overview ........................................................................................................................................................ 1 1.2 Purpose of this Guide ..................................................................................................................................... 1 1.3 XML Examples in this Document ................................................................................................................... 1 1.4 Benefits of Exchange Shop ............................................................................................................................ 2 1.5 Access Conditions .......................................................................................................................................... 3 1.6 Authentication with USG ................................................................................................................................ 3 1.7 Sabre Dev Studio ........................................................................................................................................... 4 1.8 Exchange Shop WSDL file ............................................................................................................................. 4 1.9 End Points ...................................................................................................................................................... 4

2 U n d e r s t a n d i n g t h e E x c h a n g e S h o p W e b S e r v i c e

2.1 Introduction .................................................................................................................................................... 5 2.2 Prerequisites for Exchange Shop ................................................................................................................... 5 2.3 Exchange Shop Requirements....................................................................................................................... 5

2.3.1 Eligible Documents .......................................................................................................................... 5 2.3.2 Segments......................................................................................................................................... 6 2.3.3 Passengers ...................................................................................................................................... 7 2.3.4 Shopping Options Returned............................................................................................................. 7

2.4 Essential Terms ............................................................................................................................................. 8 2.4.1 Leg ................................................................................................................................................... 8

2.4.1.1 EXS Xpath .......................................................................................................................... 8 2.4.1.2 Example 1 – Single Segment Legs ..................................................................................... 8 2.4.1.3 Example 2 – Multiple Segments Legs ................................................................................. 8

2.4.2 Segment .......................................................................................................................................... 9 2.4.2.1 Exchange Shop Xpath ........................................................................................................ 9 2.4.2.2 Example 1 ......................................................................................................................... 10 2.4.2.3 Example 2 ......................................................................................................................... 10

2.4.3 Leg Shopped vs. Leg Not Shopped ............................................................................................... 10 2.4.3.1 EXS Xpath ........................................................................................................................ 11 2.4.3.2 Example ............................................................................................................................ 11

3 E x c h a n g e S h o p R e q u e s t X M L

3.1 Introduction .................................................................................................................................................. 13

Table of Contents

Exchange Shop User Guide vi Confidential and Proprietary Sabre Airline Solutions

3.2 Request Attributes ........................................................................................................................................ 13 3.3 Request Elements ........................................................................................................................................ 13 3.4 Chosen Elements of the Exchange Shop Request ...................................................................................... 14

3.4.1 Point of Sale Information................................................................................................................ 14 3.4.1.1 Required Point of Sale Information ................................................................................... 14 3.4.1.2 Optional Point of Sale Information .................................................................................... 16

3.4.2 Passenger Information ................................................................................................................... 16 3.4.2.1 Passenger with an Active PNR ......................................................................................... 16

3.4.2.1.1 Required Information for a Passenger with an Active PNR .................................. 16 3.4.2.1.2 Optional Information for a Passenger with an Active PNR ................................... 18 3.4.2.1.3 Example of XML Request and Response for Passenger with Active PNR ........... 19 3.4.2.1.4 Example of XML Request and Response with Name Mismatch Warning ............ 22 3.4.2.1.5 Example of XML Request and Response with Duplicate Ticket ........................... 33

3.4.2.2 Passenger without Active PNR ......................................................................................... 34 3.4.2.2.1 Required Information for a Passenger without an Active PNR ............................. 34 3.4.2.2.2 Optional Information for a Passenger without an Active PNR .............................. 36 3.4.2.2.3 Example of XML Request and Response for a Passenger without an Active PNR

............................................................................................................................................ 36 3.5 Travel Itinerary information........................................................................................................................... 41

3.5.1 Three Types of Legs in Exchange Shop Request.......................................................................... 41 3.5.1.1 Leg that Is Not Shopped ................................................................................................... 42

3.5.1.1.1 Required Information for Leg that Is not Shopped................................................ 42 3.5.1.1.2 Example of XML Request with Not Shopped Leg ................................................ 44

3.5.1.2 Leg that Is Shopped and “Use Same Connections” Shopping Parameter Is Applied ....... 46 3.5.1.2.1 Information on the Leg Level ................................................................................ 46 3.5.1.2.2 Information on the Segment Level ....................................................................... 47 3.5.1.2.3 Example of XML Request for the Leg that Is Shopped and “Use Same

Connections” Search Parameter Is Applied. ....................................................................... 48 3.5.1.3 Leg is Shopped and “Use Same Connections” Shopping Parameter is NOT Applied ...... 50

3.5.1.3.1 Information on the Leg Level ................................................................................ 50 3.5.1.3.2 Example of XML Request with Shopped Leg for which “Use Same Connections”

Search Parameter Is not Applied ........................................................................................ 50 3.5.2 Removing Segments from Already Ticketed Itinerary .................................................................... 51

3.5.2.1 Example of XML Request where User Wants to Remove Some Portion of Ticketed

Itinerary ......................................................................................................................................... 52 3.5.3 Maximum Number of Legs vs. Maximum Number of Segments .................................................... 53

3.5.3.1 Shopped Leg .................................................................................................................... 53 3.5.3.1.1 Exchange Shop Request Example....................................................................... 53

3.5.3.2 Not Shopped Leg .............................................................................................................. 54 3.5.3.2.1 Exchange Shop Request Example....................................................................... 54

3.5.3.3 Shopped Leg for which “Use Same Connections” Search Parameter Is Applied.............. 55 3.5.3.3.1 Exchange Shop Request Example....................................................................... 56

3.5.4 Ability to Change Country of Origin ................................................................................................ 57

Table of Contents

Exchange Shop User Guide vii Confidential and Proprietary Sabre Airline Solutions

3.5.4.1 Example Scenarios ........................................................................................................... 57 3.5.4.1.1 Shop for Change of Country of Origin .................................................................. 58 3.5.4.1.2 Add Payment Currency Code Override ................................................................ 69

4 E x c h a n g e S h o p S e a r c h i n g a n d P r i c i n g P a r a m e t e r s

4.1 Introduction .................................................................................................................................................. 81 4.2 Required Search Parameters ....................................................................................................................... 81

4.2.1 Origin and Destination City or Airport ............................................................................................ 81 4.2.1.1 Sample XML Request and Response ............................................................................... 82

4.2.2 Departure or Arrival Date or Date and Time .................................................................................. 99 4.2.2.1 Sample XML Request and Response ............................................................................. 101

4.3 Optional Searching and Pricing Parameters .............................................................................................. 123 4.3.1 Search for Alternate Times before and/or after Departure Time .................................................. 123

4.3.1.1 Sample Request and Response XML ............................................................................. 123 4.3.2 Departure or Arrival Time Range ................................................................................................. 128

4.3.2.1 Sample Request and Response XML ............................................................................. 129 4.3.3 Search for Preferred Airline ......................................................................................................... 135

4.3.3.1 Sample Request and Response XML ............................................................................. 135 4.3.4 Exclude an Airline ........................................................................................................................ 149

4.3.4.1 Sample Request and Response XML ............................................................................. 149 4.3.5 Specify Maximum Number of Connections Permitted per Leg..................................................... 163

4.3.5.1 Sample Request and Response XML ............................................................................. 163 4.3.6 Specify Maximum Number of Stops Permitted per Leg ............................................................... 178

4.3.6.1 Sample Request and Response XML ............................................................................. 179 4.3.7 Specify Online Carrier Service Only ............................................................................................ 195

4.3.7.1 Sample Request and Response XML ............................................................................. 196 4.3.8 Specify Interline Carrier Service Only .......................................................................................... 199

4.3.8.1 Sample Request and Response XML ............................................................................. 200 4.3.9 Consider Only These Connection Cities/Airports ......................................................................... 224

4.3.9.1 Sample Request and Response XML ............................................................................. 225 4.3.10 Use Same Connections ............................................................................................................. 235

4.3.10.1 Sample Request and Response XML ........................................................................... 236 4.3.11 Shop by Cabin Class ................................................................................................................. 240

4.3.11.1 Jump Cabin Logic (default) ........................................................................................... 241 4.3.11.1.1 Cabin Specified in the Request ........................................................................ 241 4.3.11.1.2 Cabin not Specified in the Request .................................................................. 242

4.3.11.2 Disable Jump Cabin Logic ............................................................................................ 243 4.3.11.2.1 Cabin Specified in the Request ........................................................................ 243 4.3.11.2.2 Cabin not Specified in the Request .................................................................. 244

4.3.11.3 Sample Request and Response XML ........................................................................... 245 4.3.11.3.1 Sample Request and Response with Cabin Requested and Jump Cabin Logic

Enabled (default) ............................................................................................................... 245

Table of Contents

Exchange Shop User Guide viii Confidential and Proprietary Sabre Airline Solutions

4.3.11.3.2 Sample Request and Response with Cabin Requested and Jump Cabin Logic

disabled............................................................................................................................. 248 4.3.11.3.3 Sample Request and Response without Cabin Requested and Jump Cabin

Logic Disabled .................................................................................................................. 253 4.3.12 Shop by Corporate ID ................................................................................................................ 256

4.3.12.1 Sample Request and Response XML ........................................................................... 257 4.3.13 Shop by Account Code .............................................................................................................. 260

4.3.13.1 Sample Request and Response XML ........................................................................... 261 4.3.14 Override Passenger Type Code ................................................................................................ 264

4.3.14.1 Requests for Infant PTCs Only ..................................................................................... 265 4.3.14.2 Solution Returned in Different Booking Classes for Different PTCs .............................. 265 4.3.14.3 Solution Returned in Different Cabin Classes for Different PTCs ................................. 267 4.3.14.4 Sample Request and Response XML with PTC Override ............................................. 268

4.3.15 Payment Currency Code Override ............................................................................................. 277 4.3.15.1 Sample Request and Response XML ........................................................................... 278

4.3.16 Calendar Shopping .................................................................................................................... 286 4.3.16.1 Sample Request using Days Parameter ....................................................................... 286 4.3.16.2 Sample Request using MinusDays and PlusDays Parameters.................................... 287

4.3.17 Frequent Flyer Tier and Customer Value Score ........................................................................ 288 4.3.17.1 Sample Request with Frequent Flier Tier...................................................................... 289 4.3.17.2 Sample Request with Customer Value Score ............................................................... 289

4.3.18 Shop by Account Code in conjuction with negotiated fares attribute ......................................... 290 4.3.18.1 Sample Request and Response XML ........................................................................... 291

4.3.19 Enable Exchange shopping service for CKIN coupon status ..................................................... 295 4.4 Pricing Parameters Present in Exchange Shop Schema but not Supported .............................................. 299

5 E x c h a n g e S h o p R e s p o n s e X M L

5.1 Introduction ................................................................................................................................................ 301 5.1.1 Response Attributes .................................................................................................................... 301 5.1.2 Response Elements ..................................................................................................................... 301

5.2 Solutions Returned ..................................................................................................................................... 302 5.2.1 Solution Attributes ........................................................................................................................ 302 5.2.2 Solution Elements ........................................................................................................................ 304

5.2.2.1 Information about Itinerary to be Booked ........................................................................ 305 5.2.2.2 Exchange Cost Breakdown per Each Passenger for Returned Itinerary......................... 306 5.2.2.3 Non-Refundable Fare Amount ........................................................................................ 311

5.2.2.3.1 Non-Refundable Amount Example Scenarios .................................................... 313 5.2.2.4 Total Price Difference ..................................................................................................... 347

5.2.3 Example of XML Request and Response with all Itinerary Solutions Booked in the Same Booking

Class and Cabin for all Passengers ...................................................................................................... 349 5.2.4 Example of XML Request and Response Containing Solution that Requires PNR Split to Fulfill

Exchange .............................................................................................................................................. 361

Table of Contents

Exchange Shop User Guide ix Confidential and Proprietary Sabre Airline Solutions

5.2.5 Example of XML Request and Response Containing Itinerary Solution Priced in Different

Currencies for Different Passengers ..................................................................................................... 383 5.3 Enhanced Shopping Response .................................................................................................................. 394

5.3.1 Sample Request with Enhanced Response ................................................................................. 396

6 E x c h a n g e S h o p S c e n a r i o s

6.1 Introduction ................................................................................................................................................ 400 6.2 Fully Un-flown Ticket, One Leg not Shopped, One Leg Shopped Using “Same Connections,” One Leg

Shopped and “Same Connections” not Applied ............................................................................................... 400 6.2.1 Single Passenger, Fully Un-Flown Ticket, Unchanged PNR, One Leg not Shopped, One Leg

Shopped using “Same Connections,” One Leg Shopped and “Same Connections” not Applied .......... 400 6.2.2 Multiple Passengers, Fully Un-Flown Ticket, Unchanged PNR, One Leg not Shopped, One Leg

Shopped using “Same Connections,” One Leg Shopped and “Same Connections” not Applied .......... 421 6.3 Partially Flown Ticket, One Leg not Shopped, One Leg Shopped Using “Same Connections,” One Leg

Shopped and “Same Connections” not Applied ............................................................................................... 442

7 T r o u b l e s h o o t i n g

7.1 Introduction ................................................................................................................................................ 454 7.2 Error Messages by Category...................................................................................................................... 454

7.2.1 Schema Validation Errors ............................................................................................................ 455 7.2.1.1 Sample Request and Response with Schema Validation Error ...................................... 455

7.2.2 Business Validation Errors ........................................................................................................... 457 7.2.2.1 Sample Request and Response with Security Validation Error ...................................... 457 7.2.2.2 Table of Common Business Validation Errors ................................................................ 459

7.3 Errors from Other Subsystems ................................................................................................................... 463 7.3.1 Unable to Verify Interline Coupon Status ..................................................................................... 463 7.3.2 UNABLE TO REPRICE – VOLUNTARY CHANGE RULES FAILED ........................................... 465 7.3.3 UNABLE TO REPRICE – VOLUNTARY CHANGE RULES UNAVAILABLE ............................... 469 7.3.4 UNABLE TO MATCH FARES ...................................................................................................... 471

7.3.4.1 Exchanged Ticket was Priced Manually Using the Fares not Published in the Sabre

System ........................................................................................................................................ 471 7.3.4.2 Exchanged Ticket is a Result of a Previous Exchange Involving Previously Flown

Coupons. .................................................................................................................................... 474

8 C o n t a c t i n g C u s t o m e r C a r e

8.1 About Sabre Airline Solutions Customer Care ........................................................................................... 479 8.1.1 Sabre Community Portal / eService Tool ..................................................................................... 479

8.1.1.1 Registering for Community Portal Access....................................................................... 479 8.1.1.2 Requesting Access to eService ...................................................................................... 480

8.1.2 Telephone .................................................................................................................................... 480

Table of Contents

Exchange Shop User Guide x Confidential and Proprietary Sabre Airline Solutions

8.2 Customer Impact Levels............................................................................................................................. 483 8.2.1 Severity Levels ............................................................................................................................ 484 8.2.2 Product Availability Levels ........................................................................................................... 484

Table of Contents

Exchange Shop User Guide xi Confidential and Proprietary Sabre Airline Solutions

• • •

Introduction

Exchange Shop User Guide 1 Confidential and Proprietary Sabre Airline Solutions

1 Introduction

1.1 Overview

The Exchange Shop web service (TKT_ExchangeShoppingRQ) allows an airline customer (who needs to change a ticketed itinerary) to get information about available alternate itinerary options along with the exchange cost of each. With this solution, the customer will no longer need to go through a series of steps in order to find the most cost effective flight alternative for new desired travel dates and/or

departure/arrival cities or airports.

The Exchange Shop web service can be used by XML based web sites, internet booking engines, front

end GUI web services, kiosk web services, and mobile applications.

The Exchange Shop web service:

• Identifies fares in the ticket to be exchanged and, if all of them have Category 31 (Voluntary Changes) filed, returns available itinerary options that are Category 31 compliant and the exchange

cost for each passenger in the request.

• Does not offer a solution to cancel the old itinerary and book the offered alternate solution after it

comes to actual exchange.

1.2 Purpose of this Guide

The purpose of this guide is to introduce how the web service processes Exchange Shop transactions. It is not a complete reference tool for XML design. Developers should refer to the Sabre Dev Studio for the most complete information. You can find instructions on how to access the Sabre Dev Studio in section

1.6 of this guide.

This introductory guide provides:

• Description of web service features.

• Examples of typical exchange business scenarios.

• Translation between the content in the native Sabre® system and XML request expectations.

• Examples of calls to Exchange Shop.

• Common error messages that may be returned by Exchange Shop along with the explanation as to

why they occur and ways for fixing the problem where applicable.

1.3 XML Examples in this Document

The purpose of the XML examples provided in this document is to present the possible content of the request and response. The XML responses contain a limited number of solutions in order to save room,

but at the same time provide you with a good sampling of responses.

1

Introduction


1.4 Benefits of Exchange Shop

Exchange Shop allows airline customers to shop for available prices and routes when considering an

itinerary change.

Customers are able to consider various itinerary options and review the costs that would apply without

having to alter their confirmed seats.

Exchange Shop provides the following benefits:

• Allows shopping for alternate board points, off points and/or travel dates of a ticketed itinerary.

• Provides a configurable setting to specify the maximum number of itinerary solutions to be returned.

• When there are multiple passengers in the PNR, provides the ability to select all or some of

passengers to be considered during the exchange shopping process.

• Provides ability to initiate Exchange Shop from unchanged PNRs or those that have been modified

(segments added, deleted or changed).

• Provides ability to initiate Exchange Shop when there is no PNR (Example: PNR was purged).

• Provides ability to add legs to the originally ticketed itinerary (Example: Changing it from a one-way

to a round-trip fare).

• Provides ability to remove legs from the originally ticketed itinerary (Example: Changing it from

round trip to one way).

In addition, customers are able to shop using the following optional qualifiers:

• Search for preferred airline.

• Exclude an airline or search with non-preferred airline.

• Specify maximum number of connections.

• Specify maximum number of stops.

• Specify online carrier service only.

• Specify interline carrier service.

• Search by date and time.

• Specify specific connection cities/airports.

• Use same connecting points.

• Shop by cabin class.

• Shop by corporate ID.

• Shop by Account Code.

• Override Passenger Type Code (PTC).

• Override default payment currency.

Introduction


1.5 Access Conditions

The Exchange Shop web service is part of the Advanced Shopping Premium solutions and will require an activation and usage fee. For additional information or to request activation, please contact your Sabre

Account Director.

The following applies:

• Access is based on Employee Profile Record (EPR). No functional accounts can access the Exchange

Shop web service.

• A user who wants to access the Exchange Shop web service must have an EPR with the ExchangeShoppingUser Integrated Computer Environment (ICE) attribute added through the

Identity Manager (IdM) tool.

• It can be added on individual EPR or group level so that all EPRs belonging to this group inherit the ExchangeShoppingUser ICE attribute automatically. If added on the group level, there is also the

option to negate it for chosen EPRs belonging to this group should it be needed.

• To add the ExchangeShoppingUser attribute, either on individual or group level, it must be authorized by your Sabre Account Director. You can also copy the Sabre Provisioning team:

[email protected]

1.6 Authentication with USG

The Exchange Shop web service requires Universal Service Gateway (USG) authorization. The security received from USG determines whether authentication was completed successfully and whether your

session is active.

Note For more specific instructions about setting up the USG session, see the Sabre® Web Services

Guide to Accessing and Consuming Services on the Sabre Dev Studio.

Following are tips on how you can obtain USG authorization:

• Use the SessionCreateRQ web service to authenticate the user in USG. After authenticated

successfully, you will receive a response that contains a security token.

Example:

soap-env:Envelope/soap-env:Header/eb:MessageHeader/eb:Security/eb:BinarySecurityToken)

• Include the received security token in the request to the Exchange Shop web service in the SOAP

Envelope.

Example:

soap-env:Envelope/soap-env:Header/eb:MessageHeader/eb:Security/eb:BinarySecurityToken)

• In the header message, include the service name as TKT_ExchangeShoppingRQ.

• In the body of the request, use operation name: ExchangeShoppingRQ.

• To close the session associated with the token, use the SessionCloseRQ service.

• To keep the session active, use the SessionValidateRQ service.

mailto:[email protected]

Introduction


1.7 Sabre Dev Studio

The Sabre repository for all web service information can be found at Sabre Dev Studio.

It is available to airlines and has documentation including schemas, WSDL files, code samples,

workflows, and Sabre Web Services related information.

It is the most comprehensive reference tool available for XML developers.

Please visit the new site and register for an account if you have not done so already.

1.8 Exchange Shop WSDL file

The WSDL file provides a description of the basic formats of Web Service requests – how the service can

be called, what parameters it expects, and what data structures it returns.

For the latest available links to WSDL files, check the Exchange Shop documentation on the Sabre Dev

Studio.

1.9 End Points

Following are the three end points needed by the development team in test and production environments:

• TSTS/Integration: https://sws-sts.cert.sabre.com/

• CERT/Certification: https://sws-crt.as.cert.sabre.com/

• RES/Production: https://webservices.as.sabre.com/

http://cl.exct.net/?ju=fe1e1076766c007e7c1d73&ls=fdd915727265017d7715727565&m=fe5e157076650174701d&l=fe5715777c65027a7111&s=fe9516757566007a73&jb=ffcf14&t=

https://sws-sts.cert.sabre.com/

https://sws-crt.as.cert.sabre.com/

https://webservices.as.sabre.com/

Understanding the Exchange Shop Web Service


2 Understanding the Exchange Shop

Web Service

2.1 Introduction

This chapter provides the description of Exchange Shop. It provides information about types of transactions that the service supports and points out the ones that are not valid Exchange Shop requests. It also contains an explanation of essential terms associated with the Exchange Shop transactions used

throughout this user guide.

2.2 Prerequisites for Exchange Shop

Following are the prerequisites for airlines intending to use Exchange Shop:

• Must be a Sabre hosted carrier that has all virtual coupon record (VCR) data elements required by

Exchange Shop available in SabreSonic® CSS Ticketing.

• Must use Air Travel Shopping Engine (ATSE) Pricing.

• Must use Automated Exchanges and Refunds (AER). The airline does not need to be an AER web

service customer.

• Must file Category 31 (Voluntary Changes) fare rules.

• Note that inconsistent results may be returned based on CAT 31 fare filing.

2.3 Exchange Shop Requirements

The following information provides the rules and applicability of Exchange Shop.

2.3.1 Eligible Documents

• Exchange Shop applies to flight documents only. Exchange Shop does not apply to non-flight

documents, such as electronic miscellaneous documents (EMDs).

• Flight documents must be electronic (VCRs).

• There must be only one flight document per passenger. Multiple flight documents or a flight

document with a non-flight document exchange (VCR + EMD) does not apply.

• Tickets with OPEN segment coupons are not applicable to Exchange Shop.

• VCRs can include up to 16 coupons.

• VCR coupons must be used in sequence, and at least the last coupon must be in OK status.

• VCR coupons can include any coupon status, except the following:

o PRT – Printed coupon

o RPRT – Re-printed coupon

2



o PPR – Paper ticket

• VCR coupons in CTRL status are applicable for Exchange Shop as long as the system can determine

the true coupon status from the interline partner database. If not, an error message appears.

• Exchange Shop is valid only for tickets issued by Sabre hosted carriers or by the Sabre GDS. The Sabre system must have access to the electronic ticket with all un-flown and flown coupon

information. The following rules apply:

o If all tickets (including original issue and all subsequent exchanges) were issued by the Sabre hosted airline, Exchange Shop will have full access to the necessary details of the document and

will be able to process the transaction correctly.

o It cannot be guaranteed that transactions will be processed correctly where there is no access to all details of all coupons of the document (including flown and previously flown coupons).

Today, the Sabre system is not able to automatically identify if all these details are available.

o For Sabre GDS issued tickets, there is a limitation of handling, especially in the case of

previously flown coupons, as this data is not accessible for processing.

o Exchange Shop can process transactions on tickets issued and exchanged (if the ticket is not original issue) by Sabre hosted airlines. This is because the service will have full access to the

necessary details of the document including previously flown, flown, and un-flown coupons.

o For GDS issued or other airline (OA) issued tickets, there is a limitation of handling, especially in

the case of previously flown coupons as this data is not accessible for processing.

o Airlines have the option to allow or disallow shopping on other airline issued tickets.

• Exchanges or reissues are valid for Exchange Shop. Refunds are not applicable.

• Exchange Shop applies to purchased tickets only. Awards or award shopping does not apply.

• Category 31 rules must be filed for all fares on the ticket being used to shop. If Category 31 is not

available for any one of the fares on the ticket, an error message appears.

• Requests for multiple passengers must involve tickets issued for the exact same itinerary (marketing carrier(s) and flight number(s), booking class(es), board and off cities, travel date(s), coupon

status(es)) and issued in the same currency.

This applies to all un-flown, flown and previously flown coupons (if the ticket is a result of previous

reissue after some coupons were already used).

2.3.2 Segments

Following are requirements pertaining to segments:

• Solutions will be returned as complete itineraries. There will be no split by leg/fare component.

• Coupon must be used in sequence and flown segments must exist in Electronic Document.

• Split by leg/split by fare component is not supported.

• Splitting taxes by fare component is out of scope.

• Exchange Shop applies for one way, round trip, open jaw, 2+ circle trip itineraries, and itineraries

including up to a maximum of one side trip.

• Both online and interline itineraries are allowed.



• Each leg of travel must only involve a single travel date unless Calendar shopping is used. See section

4.3.16 for requesting multiple days.

• When shopping for multiple passengers, all must have the same itinerary.

• The itinerary segments must be one of the following statuses: BK, HK, IK, RR, or SS.

• OPEN segments are not applicable to Exchange Shop.

• The new itinerary can be up to a maximum of 16 segments, including flown segments and surface

sectors (ARNKs). If it is more than that, an error message appears.

It is possible to request maximum 10 portions of travel (legs) that consist of maximum 16 segments.

For more details on this, see “Maximum Number of Legs vs. Maximum Number of Segments,” page

53.

2.3.3 Passengers

Following are requirements pertaining to passengers:

• You can shop for up to nine (9) passengers.

• The passengers can be different passenger types (PTCs). For example, 2ADT and 2CNN.

• Exchange Shop works with all currently processed passenger type codes (PTCs).

Exception − The following standby passenger types do not apply to Exchange Shop: ASB, BUD, AST, NSB, CSB, YSB, SDB, MSB, and YCB.

• A shopping request only for an infant (no seat) is not applicable to Exchange Shop. You can include an infant with accompanying adults. For more information, see “Override Passenger Type Code,”

page 264.

2.3.4 Shopping Options Returned

Following are requirements pertaining to shopping options returned:

• Exchange Shop offers the following response options:

o Basic – Up to 19 options returned.

o Premium – Up to 50 options returned [subject to change].

The airline selects the desired option at the time Exchange Shop is activated.

• The system can return shopping options in different booking classes or in different cabins. When this

occurs, you will see flags advising of this in the XML.

• Exchange Shop does not validate fares that require an accompanying passenger.

• The system checks seat availability for the total number of passengers traveling.

• A maximum of 16 segments is allowed.

• When offline (interline) space is involved, the only options the system returns are those that passed

Interline Electronic Ticketing (IET) agreement validation.

• When checking options for infants (INF), Shopping may return alternate options where there is no seat available in the booking class for the given fare. Because the INF passenger type does not occupy



a seat, Pricing does not verify seats availability to price. For more information, please see “Override

Passenger Type Code,” section of this user guide.

• Itineraries returned in an Exchange Shop response will not include ancillary items (Air Extras).

• Note that some qualifiers cannot be combined which may affect the returned options. For more information see Exchange Shop Searching and Pricing Parameters section of the Exchange Shop User

Guide.

2.4 Essential Terms

Following are terms related to Exchange Shop that may help you understand the rules of forming requests

to the service.

2.4.1 Leg

A Leg is a portion of travel in between two stopover places. A leg can be a single flight or consist of

multiple connecting flights.

In this user guide, you may also see Leg referred to as portion of travel or O&D (Origin and Destination

information).

The Pricing definition of stopover that applies to Exchange Shop transactions is as follows:

• Countries except USA/Canada – A stopover is when a passenger arrives at an intermediate point and

is scheduled to depart later than 24 hours after arrival (local time).

• USA/Canada – A stopover is when a passenger arrives at an intermediate point and is scheduled to

depart later than 4 hours after arrival (local time).

2.4.1.1 EXS Xpath

ExchangeShoppingRQ/OriginDestinationInformation

2.4.1.2 Example 1 – Single Segment Legs

The following itinerary has two legs:

• First leg starting on 18 JAN at SVO and ending in MRV.

• Second leg starting on 23 JAN in MRV and ending at SVO.

1 U01304Y 18JAN J SVOMRV HK1 840A 1050A /E

2 U05371Y 23JAN Q MRVSVO HK1 640A 905A /E

2.4.1.3 Example 2 – Multiple Segments Legs

The following itinerary has two legs:

• First leg starting on 23 JAN at LED and ending at JFK

• Second leg starting on 29 JAN at JFK and ending at LED



1 U0 13Y 23JAN Q*LEDSVO HK1 1220P 135P /E

2 U0 102Y 23JAN Q SVOJFK*HK1 340P 510P /E

3 U0 101Y 29JAN W*JFKSVO HK1 210P 820A 30JAN Q /E

4 U0 12Y 30JAN Q SVOLED*HK1 1005A 1130A /E

Mandatory elements that define all legs are:

Element Description Exchange Shop Path

Start location Departure city/airport of this portion of travel is. Depending on whether the leg is shopped, it can be three-letter city or airport code.

ExchangeShoppingRQ/OriginDestinationInformation/StartLocation

End location Arrival city/airport of this portion of travel. Depending on whether the leg is shopped, it can be three-letter city or airport code.

ExchangeShoppingRQ/OriginDestinationInformation/EndLocation

Departure or arrival date or date & time

Date or date and time of either departure or arrival of given portion of travel. In the case of legs that are not shopped, we recommend using departure date. In the case of legs that are shopped, use the date or date and time search criteria, including additional optional time parameters if required, that meet your needs the best.

For more information about available date or date and time search parameters, see the following sections:

• “Departure or Arrival Date or Date and Time,”

page 99.

• “Search for Alternate Times before and/or after

Departure Time,” page 123.

• “Departure or Arrival Time Range,” page 128.

• ExchangeShoppingRQ/OriginDe

stinationInformation/DateTimeS

election/DepartureDate



election/DepartureDateTime



election/ArrivalDate



election/ArrivalDateTime

Notes

• Depending whether the leg is shopped or not and if shopped, what type of search parameters are used, also segment information with all necessary data may be required. For more information about segments, see the following section, as well as “Three Types of Legs in Exchange Shop Request,”

page 41.

• If there are multiple legs in the Exchange Shop request, they should be sent in chronological order. If lack of chronology is detected by the business validation layer of the Exchange Shop web service, an

error message will be returned and the transaction will be terminated.

2.4.2 Segment

A segment is an air segment that is part of the leg.

2.4.2.1 Exchange Shop Xpath

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment



2.4.2.2 Example 1

There are two legs in the following itinerary, each consisting of one segment:

1 U01304Y 18JAN J SVOMRV HK1 840A 1050A /E

2 U05371Y 23JAN Q MRVSVO HK1 640A 905A /E

• Leg (OriginDestinationInformation) 1: with start location at SVO, end location in MRV and

departure date on 18 JAN

o Segment (RelatedSegment) 1: U0 1304 Y 18JAN SVOMRV HK 840A 1050A

• Leg (OriginDestinationInformation) 2: with start location in MRV, end location in SVO and

departure date on 23 JAN

o Segment (RelatedSegment) 1: U0 5371 Y 23JAN MRVSVO HK 640A 905A

2.4.2.3 Example 2

There are two legs in following itinerary, each consisting of two segments (connecting flights):

1 U0 13Y 23JAN Q*LEDSVO HK1 1220P 135P /E

2 U0 102Y 23JAN Q SVOJFK*HK1 340P 510P /E

3 U0 101Y 29JAN W*JFKSVO HK1 210P 820A 30JAN Q /E

4 U0 12Y 30JAN Q SVOLED*HK1 1005A 1130A /E

• Leg (OriginDestinationInformation) 1: with start location at LED, end location at JFK and departure

date on 23 JAN

o Segment (RelatedSegment) 1: U0 13Y 23JAN LEDSVO HK 1220P 135P

o Segment (RelatedSegment) 2: U0 102Y 23JAN SVOJFK HK1 340P 510P

• Leg (OriginDestinationInformation) 2: with start location at JFK, end location at LED and departure

date on 29 JAN

o Segment (RelatedSegment) 1: U0 101Y 29JAN JFKSVO HK 210P 820A 30JAN

o Segment (RelatedSegment) 2: U0 12Y 30JAN SVOLED HK 1005A 1130A

2.4.3 Leg Shopped vs. Leg Not Shopped

The terms “shopped” or “not shopped” leg are used to indicate whether (for a given portion of travel) the passenger wants to search for alternate itinerary options or leave this part of an already booked trip

unchanged.

In the Exchange Shop request XML, it is communicated by the user in the following attribute:




When the given leg And Then set the

shopIndicator

value to

Notes

Is shopped The Exchange Shop web service should search for alternate itinerary solutions

“true” At least one shopped leg per request is required to qualify for an Exchange Shop transaction. If no leg was chosen to be shopped, an error message will be returned and the transaction terminated.

Is not shopped The Exchange Shop web service should not search for alternate options for this portion of travel, but keep its segments unchanged in all options returned to the customer

“false” • If there are legs that are

not shopped, options

returned will include

exactly the same flight

segments within this leg

(airline, flight number,

date, etc.) except for the

booking class which may

be changed in order to

secure best pricing

solution.

The exception is the

scenario where flights

that were marked as not

shopped has the

corresponding ticket

coupons in checked-in

(“CKIN”) or boarded

(“LFTD”) status. In this

case, when returning

options Exchange Shop

will not propose

rebooking to different

class on these flights.

• If there are any optional

search or pricing

parameters used for the

leg that is not shopped,

they will be ignored

during processing.

2.4.3.1 EXS Xpath

ExchangeShoppingRQ/OriginDestinationInformation/@shopIndicator

2.4.3.2 Example

Mr. Globetrotter bought the ticket for the below itinerary (two legs):

1 U01304Y 18JAN J SVOMRV HK1 0840 1050 /E



2 U05371Y 23JAN Q MRVSVO HK1 0640 0905 /E

His plans have changed and he found out that he needs to return from MRV 1 day earlier (22 JAN),

however he wants to keep his outbound flight (SVO-MRV) unchanged.

In this scenario, the Exchange Shop request needs to contain two legs:

• Leg (OriginDestinationInformation) 1: SVO-MRV departing on 18 JAN, shopIndicator=”false”

When given leg is not shopped, it will require providing full information about booked segment. For

more information, see “Three Types of Legs in Exchange Shop Request,” page 41).

o Segment (RelatedSegment) 1: U01304Y 18JAN SVOMRV HK 840A 1050A

• Leg (OriginDestinationInformation) 2: MRV-SVO departing on 22 JAN, shopIndicator=”true”

Exchange Shop Request XML


3 Exchange Shop Request XML

3.1 Introduction

The purpose of this chapter is to briefly explain the content of the Exchange Shop Request XML. The subsections of this chapter will provide detailed information about those parts of the XML request that may need some additional explanation over and above what is described in general information and schema annotations, and explain specifics of forming Exchange Shop requests in different business

scenarios.

Note This chapter should not be treated as complete information about the Exchange Shop request XML schema, but can be used as additional source of information for the Exchange Shop schema

definition available in the DRC.

3.2 Request Attributes

Following are the request attributes:

Attribute Description Exchange Shop Path

XML version Required in the XML schema. ExchangeShoppingRQ/@Version

Option to allow or inhibit shopping for alternate options for Other Airline (OA) issued tickets

Optional in the XML schema. The default is to allow shopping for OA issued tickets.

For an example of the error message that is returned when a customer inhibits shopping for OA issued tickets, but the user tries to shop for such a ticket anyway, see “Sample Request and Response with Security Validation Error,” page 457.

ExchangeShoppingRQ/@allowOADocumentExchange

3.3 Request Elements

Following are the request elements:


Header Standard header information that helps orchestrate the requests.

ExchangeShoppingRQ/Header

One of optional attributes of Header

Default timeout override

Header element includes the attribute that allows the user to override the default timeout. When sent, it will be the time after which Exchange Shop will try to stop processing the transaction. However if the system is in the middle of processing in one of the subsystems, the timeout may occur after the timeout sent by the user. The service will not be able to timeout in the middle of a process in the given subsystem.

ExchangeShoppingRQ/Header/@ttl

3




Remaining elements of Request XML

Point of Sale (POS)

Information about the point of sale and the agent performing the Exchange Shop transaction. This data must match the data that will be used in the subsequent exchange transaction; otherwise, the cost of the exchange may differ from the returned solution.

ExchangeShoppingRQ/POS

Ticketing provider code

Two-character code of the airline (partition) on whose behalf the Exchange Shop transaction is performed. It is an airline partition on which the subsequent exchange transaction will be performed.

ExchangeShoppingRQ/TicketingProvider

Passenger information

Details about passengers and the flight documents that they want to exchange.

ExchangeShoppingRQ/PassengerInformation

Travel itinerary information

Information about the requested travel itinerary, including portions of travel (and related segments) that the passenger wants to leave unchanged if need be (legs not shopped) and/or those portions of travel for which the traveler wants to search for alternate options (legs shopped).


Travel preferences

Additional shopping criteria that should be used when searching for alternate options. All optional qualifiers, including the ones available under this part of the XML, are described in “Optional Searching and Pricing Parameters,” page 123.

ExchangeShoppingRQ/TravelPreferences

Diagnostic For internal troubleshooting purposes only. ExchangeShoppingRQ/Diagnostic

3.4 Chosen Elements of the Exchange Shop Request

The subsections provide details about chosen elements of the Exchange Shop request and some of their

elements that may require additional explanation.

Note This information should not be treated as complete information about the schema, but only as the

supplement of XML schema documentation published in the DRC.

This section includes the following:

• Point of Sale Information (see this page).

• Passenger Information (see “Passenger Information,” page 16)

3.4.1 Point of Sale Information

This section contains information about required and optional point of sale elements.

3.4.1.1 Required Point of Sale Information

Following is the list of required elements identifying the Point of Sale in an Exchange Shop transaction. They are optional in the XML schema; however, their presence is verified by the service business

validation layer.



Element Description Example Exchange Shop Path

Pseudo City Code Three-letter pseudo city code where the agent performing the Exchange Shop transaction is signed in.

Attributes are optional

JFK ExchangeShoppingRQ/POS/STL:Actual

Agent’s home Pseudo City Code

Three-letter home pseudo city of the agent.

Attributes are optional.

CHI ExchangeShoppingRQ/POS/STL:Home

Agent’s sine Agent’s sine. EMB ExchangeShoppingRQ/POS/STL:Sine

Agent’s duty code Agent’s duty code. 5 ExchangeShoppingRQ/POS/STL:DutyCode

LNIATA LNIATA of the console the agent is signed in to.

This is the LNIATA that you see, for example, as a response for the ‡ J entry in the Sabre system:

5E09D3 ExchangeShoppingRQ/POS/STL:Lniata

‡J

YOUR SET ADDRESS IS 5E09D3 TSTSB FPHLC110

In addition, one of the following is required:


Agent’s station number

Station’s IATA number from where Exchange Shop transaction is performed.

00258799 ExchangeShoppingRQ/POS/StationNumber

Agent’s Office Accounting Code

Note If the airline calling the Exchange Shop web service uses Office Accounting Codes, the appropriate OAC should always be passed in the XML request to secure proper pricing processing.

U0 NYC AI 1234567

ExchangeShoppingRQ/POS/OfficeAccountingCode

Optional OAC attribute:

Default validating carrier code

U0 ExchangeShoppingRQ/POS/OfficeAccountingCode/@defaultValidatingCarrier

Required remaining three attributes forming the OAC:

City code City code. NYC ExchangeShoppingRQ/POS/OfficeAccountingCode/PersonalCityCode

Account code Account code. AI ExchangeShoppingRQ/POS/OfficeAccountingCode/PersonalAccountCode

Station number Station number. 1234567 ExchangeShoppingRQ/POS/OfficeAccountingCode/OfficeCode




Shopping path Allows the point of sale to specify the attribute that is used to determine shopping rules selection. The value of request type attribute passed by Point of Sale identifies the Shopping rule that should be applied during Exchange Shop transaction. If there is no specific Shopping rule that the Point of Sale wants to apply, it is recommended to send the value “ADVEXC”.

ADVEXC ExchangeShoppingRQ/POS/ShoppingPath/@requestType

3.4.1.2 Optional Point of Sale Information

Optional elements identifying the point of sale in an Exchange Shop transaction that are not used at this

time (you can see them in Exchange Shop request XML, but they are not used today):

Element Exchange Shop Path

IATA assigned code for airline or agency ExchangeShoppingRQ/POS/STL:Company

Agent’s pseudo city code (PCC) ExchangeShoppingRQ/POS/STL:Pseudo

Airline partition for multi-host source ExchangeShoppingRQ/POS/STL:MultiHost

3.4.2 Passenger Information

This part of the Exchange Shop XML request was designed to collect information about passengers for

whom the transaction is performed.

Depending on whether it is the scenario where an active PNR is available (for example, it was purged), a

different set of data is required and described in the following sections.

This section includes the following:

• Passenger With an Active PNR (see this page).

• Passenger Without an Active PNR (see “Passenger Without an Active PNR,” page 34).

3.4.2.1 Passenger with an Active PNR

This section contains information about required and optional elements for passengers with an active

PNR.

3.4.2.1.1 Required Information for a Passenger with an Active PNR

The following elements are required when the passenger has an active PNR. There are a maximum of nine passengers allowed per Exchange Shop request; therefore, up to nine repetitions of this set of data

are allowed.




PNR locator It is not required that all passengers in the request have the same PNR locator, however the requirement is exactly the same itinerary for all passengers in the request.

If all passengers are not booked in the same PNR, it is the responsibility of the Point of Sale to handle the rebooking process correctly if the given alternate option is to be chosen.

YTRBDE ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/@pnrLocator

Passenger reference number as in PNR

1.1 ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/@referenceNumber

Passenger name Full first and last name as showing in PNR.

JOHN GLOBETROTTER

• ExchangeShoppingRQ/Pass

engerInformation/Passenger

WithPNR/@firstName

• ExchangeShoppingRQ/Pass

engerInformation/Passenger

WithPNR/@lastName

Number of document

Number of the document that the passenger wants to exchange in this transaction.

If the document in the request is a conjunctive ticket, such as 888-2222222222-23, only the number of the first conjunctive ticket should be passed in the request (888-2222222222 in this scenario).

If during the first call, the Exchange Shop web service identifies if the name sent in the request does not match the name in related document. The transaction will be still processed however when returning the options to the user, a warning will be added regarding name mismatch.

It will be the decision of the point of sale whether to return alternate options to the user in such case or fail the transaction.

8881234567892 ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/DocumentNumber




Optional attribute of the Document Number

Local issue date Local issue date of the document.

It is available to support the scenario where there is more than one document with the requested number active in the documents database. If this is the case, the Exchange Shop web service will return an error which will include a list of duplicate ticket numbers along with the issue dates and passengers’ first and last names.

In order to continue with the Exchange Shop transaction, the customer will need to send the request again adding the issue date of the document in question in order to pull the correct document for further processing.

It is the decision of the point of sale how the information about listed documents and related names will be handled.

Note The passenger should not be presented with the other passenger’s data.

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/DocumentNumber/@localIssueDate

See the example of the Exchange Shop response containing a duplicate document numbers error later in

this document.

3.4.2.1.2 Optional Information for a Passenger with an Active PNR

The Passenger Information section also contains the following two optional elements:


Passenger’s age Passenger’s age (in years). This attribute should be used when the passenger has a discount related to his or her age, for example, child. Applicable to -NN type Passenger Type Codes (PTC), such as CNN.

The passenger’s age can be indicated in two ways:

• As -NN type (PTC), where NN

represents the passenger’s age, for

example, child aged 9 (C09) and it

can be passed in the Exchange

Shop request as the Passenger

Type Code optional pricing

parameter or, if not provided, taken

from the exchanged VCR if the

09 ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/@age




ticket was priced using such a PTC.

For more information, see “Override

Passenger Type Code,” page 264.

• As a separate passenger’s age

element described in this bullet that

has numeric value, such as 09,

which means “9 years old” along

with -NN type PTC.

Passenger Type Code (PTC) override

Pricing parameter that allows overriding the PTC with which the exchanged ticket was issued.

YTH ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/PassengerTypeOverride

Exchange Shop processes these two elements in following way:

1. First, it is attempted to get the passenger’s age from the PTC element, for example, if it is present and NN represents the numeric value (such as C09), the system determines that the passenger’s age is 9

years and processes the request for such a passenger (such as child aged 9).

2. If PTC is present, but the NN does not represent numeric value (such as CNN), system checks the value of passenger’s age element (@Age). If this element is present, the age is taken from there. If there is no passenger’s age element present, the service processes the request as without the age

specified.

3. If both elements are present: PTC where NN represents numeric value for passenger’s age (such as C09) and passenger’s age element (such as 10) value from PTC (such as C09) overrides passenger’s

age (such as 10).

In the scenario when the original ticket was priced with –NN type PTC and NN represented passenger’s age, such as C09, and when calling the Exchange Shop web service passenger wants to override the age, such as child will turn 10 when traveling on new dates, it is necessary that the traveler indicates this using a Passenger Type Code pricing parameter and passing the value C10 or passing it as CNN and also using the age attribute (@Age) with the value of 10. Otherwise, the override will fail as per the logic described

above.

3.4.2.1.3 Example of XML Request and Response for Passenger with Active PNR

Exchange Shop request XML

<ExchangeShoppingRQ

Version="1.0.0"

xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0">

<Header/>

<POS>

<ns1:Pseudo

xmlns:ns1="http://services.sabre.com/STL/v01">MOW</ns1:Pseudo>

<ns2:Actual

xmlns:ns2="http://services.sabre.com/STL/v01">MOW</ns2:Actual>

<ns3:Home

xmlns:ns3="http://services.sabre.com/STL/v01">HDQ</ns3:Home>

<ns4:Sine

xmlns:ns4="http://services.sabre.com/STL/v01">ET3</ns4:Sine>



<ns5:DutyCode

xmlns:ns5="http://services.sabre.com/STL/v01">4</ns5:DutyCode>

<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">40CABA</ns6:Lniata>

<StationNumber>00000055</StationNumber>

<ShoppingPath requestType="ADVEXC"/>

</POS>

<TicketingProvider>U0</TicketingProvider>

<PassengerInformation>

<PassengerWithPNR

firstName="JOHN" lastName=“GLOBETROTTER” pnrLocator="GNEUTV"

referenceNumber="1.1">

<DocumentNumber>8882105167850</DocumentNumber>

</PassengerWithPNR>

</PassengerInformation>

<OriginDestinationInformation

shopIndicator="false">

<DateTimeSelection>

<DepartureDateTime>2014-04-22T08:45:00</DepartureDateTime>

</DateTimeSelection>

<StartLocation>SVO</StartLocation>

<EndLocation>MRV</EndLocation>

<RelatedSegment

bookingClass="Y" bookingDateTime="2013-09-12T15:28:31"

endDateTime="2014-04-22T11:00:00" endLocation="MRV"

marketingFlightNumber="1304" marketingProvider="U0"

operatingProvider="U0" reservationStatus="HK"

startDateTime="2014-04-22T08:45:00"

startLocation="SVO"/>

</OriginDestinationInformation>


shopIndicator="true">

<DateTimeSelection>

<DepartureDateTime

minus="5" plus="5">2014-04-30T07:00:00</DepartureDateTime>


<StartLocation>MRV</StartLocation>

<EndLocation>SVO</EndLocation>


</ExchangeShoppingRQ>

Exchange Shop response XML

<ExchangeShoppingRS

Version="1.0.0" solutions="1"


<Header

messageID="TKTHLI703-24805-1440537980-1391291773384-195-exs"

timeStamp="2014-02-01T15:56:13">

<STL:OrchestrationID seq="2"

xmlns:STL="http://services.sabre.com/STL/v01">TKTHLI703-24805-1440537980-

1391291773384-195-exs</STL:OrchestrationID>

<STL:Results

xmlns:STL="http://services.sabre.com/STL/v01">

<STL:Success>

<STL:System>TKT-WS</STL:System>

<STL:Source>EXS</STL:Source>

</STL:Success>



</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">40CABA</ns6:Lniata>



</POS>

<Solution

passengersInDifferentCabins="false" pricingSequence="1"

requireSplitPNR="false"

sequence="1">

<BookItinerary>

<OriginDestination

elapsedTime="135" endLocation="MRV" segmentQuantity="1"

startLocation="SVO">

<ReservationSegment elapsedTime="135"

electronicTicketingIndicator="true"



marriageGroup="O" operatingProvider="U0"

startDateTime="2014-04-22T08:45:00" startLocation="SVO"

stopQuantity="0">

<PassengerBookingDetails

bookingClass="L" cabin="Y" documentNumber="8882105167850"

fareBasis="LEXRF"

meal="B"/>

</ReservationSegment>

</OriginDestination>

<OriginDestination

elapsedTime="145" endLocation="SVO" segmentQuantity="1"

startLocation="MRV">



endDateTime="2014-04-30T10:50:00" endLocation="SVO"


marriageGroup="O" operatingProvider="D9"

startDateTime="2014-04-30T08:25:00" startLocation="MRV"

stopQuantity="0">


bookingClass="B" cabin="Y" documentNumber="8882105167850"

fareBasis="BRTRF"

meal="L"/>



</BookItinerary>

<PassengerPriceInformation>



<Passenger

documentNumber="8882105167850" firstName="JOHN"

lastName="GLOBETROTTER" type="ADT">

<ResultPriceDifference

differenceType="AddCollect"

lastDayToTicket="2014-02-09">

<FareDifference

currencyCode="RUB"

decimalPlace="0">0</FareDifference>

<TaxDifference

currencyCode="RUB"

decimalPlace="0">1663</TaxDifference>

<SubtotalDifference

currencyCode="RUB"

decimalPlace="0">1663</SubtotalDifference>

<GrandTotalDifference

currencyCode="RUB"

decimalPlace="0">1663</GrandTotalDifference>

<Message

type="Advisory">LAST DATE TO PURCHASE 09FEB14 - 1346)4</Message>

</ResultPriceDifference>

</Passenger>

</PassengerPriceInformation>

<TotalPriceDifference

differenceType="AddCollect">

<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB" decimalPlace="0">1663</GrandTotalDifference>

</TotalPriceDifference>

</Solution>

</ExchangeShoppingRS>

3.4.2.1.4 Example of XML Request and Response with Name Mismatch Warning

Scenario: Ticket 8882104269405 was issued for the name of John White:

VIRTUAL COUPON RECORD

8882104269405 NAME-WHITE/JOHN

TTL NBR OF CPNS- 1 DATE OF ISSUE-28JAN14 PNR-KBUMBX 28JAN14

CPN A/L FLT CLS DATE BRDOFF TIME ST F/B STAT

1 U0 1304 Y 18APR SVOMRV 0855 OK YOWRF OK



FARE RUB 22500 TAX 1500YQ TAX 163YR TOTAL RUB

24163

FARE CALC MOW U0 MRV22500RUB22500END

FCMI-0

FORM OF PAYMENT

FOP-CASH

DATE OF ISSUE-28JAN14 ISSUED AT-MOWTR MOW ET3

ISSUE STATION-00000055

ENDORSEMENTS/RESTRICTIONS-

However, the name that passed in the Exchange Shop request was John Brown:


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">09EDC3</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN MR" lastName="BROWN" pnrLocator="KBUMBX"



</PassengerWithPNR>




<DateTimeSelection>

<DepartureDate>2014-04-25</DepartureDate>








That is why, when returning itinerary solutions, an alert about the name mismatch was added:


<ExchangeShoppingRS Version="1.0.0" solutions="10"


<Header

messageID="TKTHLI703-21588-524832526-1390900477756-9520-exs" timeStamp="2014-

01-28T03:14:37">


xmlns:STL="http://services.sabre.com/STL/v01">TKTHLI703-21588-524832526-1390900477756-

9520-exs</STL:OrchestrationID>

<STL:Results xmlns:STL="http://services.sabre.com/STL/v01">

<STL:Success>



</STL:Success>

<STL:Warning status="Complete" type="Validation">

<STL:Source>Exs</STL:Source>


<STL:SystemSpecificResults>

<STL:ErrorMessage code="31614">The name of the passenger as provided in

the request does not match the name in ticket: 8882104269405</STL:ErrorMessage>

<STL:ShortText>000000 - VCR/TR AND PNR NAME DO NOT MATCH -

1180)4</STL:ShortText>

</STL:SystemSpecificResults>

</STL:Warning>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo xmlns:ns1="http://services.sabre.com/STL/v01">MOW</ns1:Pseudo>

<ns2:Actual xmlns:ns2="http://services.sabre.com/STL/v01">MOW</ns2:Actual>

<ns3:Home xmlns:ns3="http://services.sabre.com/STL/v01">HDQ</ns3:Home>

<ns4:Sine xmlns:ns4="http://services.sabre.com/STL/v01">ET3</ns4:Sine>

<ns5:DutyCode xmlns:ns5="http://services.sabre.com/STL/v01">4</ns5:DutyCode>

<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">09EDC3</ns6:Lniata>



</POS>

<Solution passengersInDifferentCabins="false" pricingSequence="1"

requireSplitPNR="false" sequence="1">

<BookItinerary>

<OriginDestination elapsedTime="135" endLocation="MRV"

segmentQuantity="1" startLocation="SVO">







stopQuantity="0">

<PassengerBookingDetails bookingClass="D" cabin="C"

documentNumber="8882104269405" fareBasis="DOWRF" meal="L"/>



</BookItinerary>




<Passenger documentNumber="8882104269405" firstName="JOHN MR"

lastName="BROWN" type="ADT">

<ResultPriceDifference differenceType="Even" lastDayToTicket="2014-04-18">

<FareDifference currencyCode="RUB" decimalPlace="0">0</FareDifference>

<TaxDifference currencyCode="RUB" decimalPlace="0">0</TaxDifference>

<SubtotalDifference currencyCode="RUB"


<GrandTotalDifference currencyCode="RUB"


<Message type="Advisory">LAST DATE TO PURCHASE 18APR14 -

1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Even">








</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882104269405" fareBasis="DOWRF" meal="B"/>



</BookItinerary>












1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">





</BookItinerary>














1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>







endDateTime="2014-04-25T13:00:00" endLocation="LED"




stopQuantity="0">

<PassengerBookingDetails bookingClass="B" cabin="Y"

documentNumber="8882104269405" fareBasis="BOWRF" meal="L"/>





marketingFlightNumber="643" marketingProvider="FV"

marriageGroup="O" operatingProvider="FV"

startDateTime="2014-04-25T15:40:00" startLocation="LED"

stopQuantity="0">

<PassengerBookingDetails bookingClass="Y" cabin="Y"

documentNumber="8882104269405" fareBasis="YOW" meal="M"/>



</BookItinerary>




<ResultPriceDifference differenceType="AddCollect" lastDayToTicket="2014-

04-19">

<FareDifference currencyCode="RUB"








1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="AddCollect">








</Solution>



<BookItinerary>











stopQuantity="0">


documentNumber="8882104269405" fareBasis="BOWRF" meal="B"/>








stopQuantity="0">





</BookItinerary>





04-19">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-04-25T05:35:00" endLocation="PEE"




stopQuantity="0">











startDateTime="2014-04-25T06:40:00" startLocation="PEE"

stopQuantity="0">








marriageGroup="I" operatingProvider="FV"


stopQuantity="0">





</BookItinerary>





04-19">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-04-25T05:15:00" endLocation="UFA"






stopQuantity="0">









startDateTime="2014-04-25T05:55:00" startLocation="UFA"

stopQuantity="0">








marriageGroup="I" operatingProvider="FV"


stopQuantity="0">





</BookItinerary>





04-19">









1346)4</Message>


</Passenger>










</Solution>




3.4.2.1.5 Example of XML Request and Response with Duplicate Ticket


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">0E1AC7</ns6:Lniata>



</POS>



<PassengerWithoutPNR>


</PassengerWithoutPNR>







<DateTimeSelection>








<ExchangeShoppingRS



<STL:Header


timeStamp="2014-01-28T05:56:56"

xmlns:STL="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0">

<STL:OrchestrationID

seq="2"



<STL:Results




<STL:Error

status="NotProcessed" timeStamp="2014-01-28T05:56:56"

type="Validation">

<STL:Source>EXS-DocValidation</STL:Source>



<STL:ErrorMessage

code="31102">Document validation failed: One or more documents are duplicate.

Please provide document local issue date and request again (failed rule:

TktDocErrorResponseRule)</STL:ErrorMessage>

<STL:ShortText>Document validation failed</STL:ShortText>


</STL:Error>

<STL:Warning

status="Incomplete"

type="BusinessLogic">




<STL:ErrorMessage

code="31102">Details of duplicate document 8882460212639: 2013-04-

04|GLOBETROTTER|SAM, 2013-12-04|TATHARE|NILESH</STL:ErrorMessage>



</STL:Warning>

<STL:Warning

status="Incomplete"

type="BusinessLogic">




<STL:ErrorMessage

code="31102">Details of duplicate document 0482116204504: 2013-04-09|MARK

MR|BROWN, 2013-05-08|GREY|ANN</STL:ErrorMessage>



</STL:Warning>

</STL:Results>

</STL:Header>


3.4.2.2 Passenger without Active PNR

This section contains information pertaining to passenger without an active PNR.

3.4.2.2.1 Required Information for a Passenger without an Active PNR

The following elements are required for the scenario where the passenger has no active PNR, for example, it was purged, but the ticket is still eligible for exchange. The assumption is that all portions of

travel for passengers without an active PNR will be shopped.

There are a maximum of nine passengers allowed per Exchange Shop request; therefore, up to nine

occurrences of this set of data are allowed:




Number of document

Number of document that passenger wants to exchange in this transaction.

If the document in the request is conjunctive ticket, such as 888-2222222222-23, only the number of first conjunctive ticket should be passed in the request (888-2222222222 in this scenario).

Because no active PNR exists, passenger name validation is not performed in the Exchange Shop web service.

8881234567892 ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/DocumentNumber

Optional attribute of the document number

local issue date Local issue date of the document.

The scenario where there is more than one document with requested number active in documents database is supported. If this is the case, the Exchange Shop web service will return an error that will include a list of duplicate ticket numbers along with the issue dates and passengers’ first and last names. In order to continue with the Exchange Shop transaction, the customer will need to send the request again adding the issue date of the document in question in order to pull the correct document for further processing.

It is a Point of Sale decision how the information about listed documents and related names will be handled.

Note The passenger should not be presented with the other passenger’s data.

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/DocumentNumber/@localIssueDate

See the example of Exchange Shop response containing a duplicate document number error earlier in this

document.



3.4.2.2.2 Optional Information for a Passenger without an Active PNR

The following passenger information contains two optional elements:


Passenger’s age Passenger’s age (in years).

This attribute should be used when the passenger has a discount related to his or her age, (such as child). Applicable to -NN type Passenger Type Codes (PTC) (such as CNN).

For more information about the age element, see “Passenger with an Active PNR,” page 16.

09 ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/@age

Passenger Type Code (PTC) override

This is the pricing parameter that allows overriding the PTC with which the exchanged ticket was issued. For more information about PTC override, see “Override Passenger Type Code,” page 264.

YTH ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/PassengerTypeOverride

3.4.2.2.3 Example of XML Request and Response for a Passenger without an Active PNR


<ExchangeShoppingRQ

Version="1.0.0"

xmlns="http://www.Sabre.com/ns/Ticketing/exchangeshop/1.0">

<Header/>

<POS>

<ns1:Pseudo

xmlns:ns1="http://services.Sabre.com/STL/v01">MOW</ns1:Pseudo>

<ns2:Actual

xmlns:ns2="http://services.Sabre.com/STL/v01">MOW</ns2:Actual>

<ns3:Home

xmlns:ns3="http://services.Sabre.com/STL/v01">HDQ</ns3:Home>

<ns4:Sine

xmlns:ns4="http://services.Sabre.com/STL/v01">ET3</ns4:Sine>

<ns5:DutyCode

xmlns:ns5="http://services.Sabre.com/STL/v01">4</ns5:DutyCode>

<ns6:Lniata

xmlns:ns6="http://services.Sabre.com/STL/v01">6768C3</ns6:Lniata>



</POS>














<DateTimeSelection>




<ConnectionLocation>

<Location>KZN</Location>

</ConnectionLocation>

<EndLocation>LED</EndLocation>


<TravelPreferences

interlineIndicator="true"/>

<Diagnostic type="NONE">

<DataText/>

</Diagnostic>



<ExchangeShoppingRS



<Header


timeStamp="2014-01-26T17:12:09">


xmlns:STL="http://services.Sabre.com/STL/v01">TKTHLI703-21588-524832526-


<STL:Results

xmlns:STL="http://services.Sabre.com/STL/v01">

<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution





sequence="1">

<BookItinerary>

<OriginDestination

elapsedTime="525" endLocation="LED" segmentQuantity="2"




endDateTime="2014-04-17T21:45:00" endLocation="KZN"




stopQuantity="0">



fareBasis="BOWRF" meal="S"/>



fareBasis="BOWRF"

meal="S"/>


<ReservationSegment

elapsedTime="155" electronicTicketingIndicator="true"




startDateTime="2014-04-18T02:30:00" startLocation="KZN"

stopQuantity="0">


bookingClass="Y" cabin="Y" documentNumber="8882104266647"

fareBasis="YOW" meal="M"/>



fareBasis="YOW"

meal="M"/>



</BookItinerary>


<Passenger

documentNumber="8882104266647" firstName="TEST" lastName="A"

type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



type="Advisory">LAST DATE TO PURCHASE 11APR14 - 1346)4</Message>


</Passenger>

<Passenger

documentNumber="8882104266648" firstName="TEST" lastName="ELA"

type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination

elapsedTime="310" endLocation="LED" segmentQuantity="2"




endDateTime="2014-04-18T01:30:00" endLocation="KZN"




stopQuantity="0">





fareBasis="BOWRF" meal="S"/>



fareBasis="BOWRF"

meal="S"/>


<ReservationSegment





startDateTime="2014-04-18T02:30:00" startLocation="KZN"

stopQuantity="0">



fareBasis="YOW" meal="M"/>



fareBasis="YOW"

meal="M"/>



</BookItinerary>


<Passenger

documentNumber="8882104266647" firstName="TEST" lastName="A"

type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>

<Passenger

documentNumber="8882104266648" firstName="TEST" lastName="ELA"

type="ADT">




<FareDifference

currencyCode="RUB"




<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


3.5 Travel Itinerary information

This is the part of the XML request that provides information about the requested travel itinerary. The

following sections provide tips on how requests should be formed in various business scenarios.

3.5.1 Three Types of Legs in Exchange Shop Request

Essentially, there are three types of legs (O&Ds) which, depending on whether they are shopped and

whether the shopping search parameter Use Same Connections is applied, require a different set of data to

be passed in the Exchange Shop request.

EXS Xpath:


All three types of legs can be combined within a single Exchange Shop request.

This section focuses on describing mandatory elements of the request depending on Exchange Shop business scenarios and does not cover all optional search and pricing parameters available in this part of XML. For detailed information on these optional parameters, see “Optional Searching and Pricing

Parameters,” page 123.



3.5.1.1 Leg that Is Not Shopped

In the case of a leg that is not shopped, except elements describing the leg, full information about the segment that the passenger has already booked in the PNR and wants to keep in the new itinerary needs to

be passed. The Exchange Shop web service does not access the PNR to read this data but relies on

information passed in Exchange Shop request.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/@shopIndicator=”false”

3.5.1.1.1 Required Information for Leg that Is not Shopped

This section provides information about elements that are required for flight segments being part of leg

that is not shopped.

Information on the Leg Level The following elements need to be passed for the leg that is not shopped:


Airport code for travel start

Three-letter airport code of place where this portion of travel starts.

Note The leg’s departure airport code must match the airport code of the first flight segment belonging to this portion of travel. Otherwise, an error will be returned and transaction terminated.


Airport code for travel end

Three-letter airport code of place where this portion of travel ends.

Note The leg’s arrival airport code must match the airport code of the last flight segment belonging to this portion of travel. Otherwise, an error will be returned and transaction terminated.


Departure or arrival date or date and time when this portion of travel starts or ends

Departure or arrival date or date and time when this portion of travel starts or ends.

Recommendation: use departure date as date information for the leg that is not shopped.

Note If the departure date or departure date and time is used, it must match the departure date or departure date and time of first flight segment belonging to this portion of travel. If arrival date or arrival date and time is used, it must match the arrival date or arrival date and time of last flight segment belonging to this portion of travel. Otherwise, an error will be returned and transaction terminated.

• ExchangeShoppingRQ/OriginD

estinationInformation/DateTime

Selection/DepartureDate



Selection/DepartureDateTime



Selection/ArrivalDate



Selection/ArrivalDateTime

Note If any other optional search or pricing Exchange Shop parameter, such as Use same connections,

are used for the leg that is not shopped, they will be ignored in processing.



Information on the Segment Level If the leg is not shopped, information about all related segments pertaining to this leg is required. If no flight segment information is provided for such a leg, an error message will be returned and transaction

terminated.

If the leg that is not shopped consists of more than one related flight segment, the Exchange Shop business validation layer will verify trip continuity within the leg. If an open jaw is detected within the single leg (arrival airport of the preceding flight segment is different than departure airport of the next segment), even if it is caused by the airport change and time requirements for connection are met (it is not

stopover from time perspective), an error message will be returned and transaction terminated.

Example:

Note This example intends only to illustrate an open jaw scenario and should not be treated as exact

content of XML.

If the passenger has these two flight segments booked and wants to keep them unchanged (not shopped) in the new itinerary, they would need to be sent in the Exchange Shop request as two separate legs because there is an open jaw between New York John F. Kennedy (JFK) and New York LaGuardia

(LGA) airport.

1 U0001Y 18JAN LHRJFK HK1 0840 1650

2 U0002Y 18JAN LGWMIA HK1 1815 2110

The service will also validate whether the segments are sent in chronological order. If they are not, an

error message will be returned and transaction terminated.

The following flight segment information elements as appearing in PNR are required for the leg that is

not shopped:


Operating carrier Two-character alphanumeric code for the operating carrier of the flight segment.

U0 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@operatingProvider

Marketing carrier Two-character alphanumeric code for the marketing carrier of the flight segment.

K0 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@marketingProvider

Flight number Numeric marketing flight number.

Note OPEN flight numbers are not supported at this time and if passed, an error message will be returned and transaction terminated.

001 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@marketingFlightNumber

Departure date and time

Departure date and time of the flight segment.

Note This element is optional in the XML schema, but verified by the business validation layer. If not present, an error message will be returned and transaction terminated.

2014-09-20T06:20:00

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@startDateTime




Arrival date and time

Arrival date and time of the flight segment.


2014-09-20T11:35:00

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@endDateTime

Departure airport Three-character departure airport of the flight segment.

JFK ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@startLocation

Arrival airport Three-character arrival airport of the flight segment.

BOS ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@endLocation

Reservation booking class

Code for the reservation booking class. Y ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@bookingClass

Reservation status

Reservation status as in PNR. HK ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@reservationStatus

3.5.1.1.2 Example of XML Request with Not Shopped Leg

Scenario: there are two passengers who have tickets issued for the following itinerary. They realize that they need to travel additionally from Moscow (SVO) to Saint Petersburg (LED) on 27 April 2014, and they want to see what exchange options they would have if they wanted to add this leg to already booked

flights on route: Moscow (SVO) – Mineralnye Vody (MRV) – Moscow (SVO).

PWPODM

1.1GLOBETROTTER/JOHN 2.1GLOBETROTTER/JANE

1 U01304Y 15APR T SVOMRV HK2 0855 1115 /E

2 U05371Y 20APR S MRVSVO HK2 0825 1050 /E

TKT/TIME LIMIT

1.T-25JAN-MOW4ET3

2.TE 8882104267768 GLOBETROTTER/J MOW4ET3 2045/25JAN

3.TE 8882104267769 GLOBETROTTER/J MOW4ET3 2045/25JAN

Following is an example of what the information about these two legs that are not shopped (SVO-MRV and MRV-SVO) would need to look like in the Exchange Shop request:


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual




<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JANE" lastName="GLOBETROTTER" pnrLocator="PWPODM"



</PassengerWithPNR>

<PassengerWithPNR

firstName="JANE" lastName="GLOBETROTTER" pnrLocator="PWPODM"



</PassengerWithPNR>




<DateTimeSelection>





<RelatedSegment










<DateTimeSelection>





<RelatedSegment






startLocation="MRV"/>




<DateTimeSelection>









3.5.1.2 Leg that Is Shopped and “Use Same Connections” Shopping Parameter Is Applied

If the leg is shopped AND “Use Same Connections” shopping parameter are used for this leg, it means the passenger wants to search itinerary options for the indicated city pair and travel dates but wants the Exchange Shop web service to return flight options for this leg that connect through the same airports as

already booked.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/@shopIndicator=”true”

and

ExchangeShoppingRQ/OriginDestinationInformation/@preserveConnectionsIndicator=”true”

Example:

Note This example is only for illustration purposes and does not depict exact information required in

XML request. You will find example of such an XML request later in this document.

Passenger has the ticket issued for below itinerary

1 U021Y 15APR LHR BOS HK1 0850 1700

2 U035Y 15APR BOS MIA HK1 1830 2115

However, he needs to fly from London (LHR) to Miami (MIA) three days later than he initially planned. He uses the Exchange Shop web service to find an alternate itinerary option for a flight from LHR to MIA on April 18, but wants the service to search for options that connect at the same airport as originally

booked (in this case BOS).

In such a scenario, the Exchange Shop web service expects full segment information that is part of the leg on which passenger wants to change travel date and/or time, similarly to leg that is not shopped described

earlier in this document.

The following sections describe the data that is required to be passed in the Exchange Shop request for

this type of leg.

3.5.1.2.1 Information on the Leg Level

The following elements need to be passed for the leg that is not shopped:


Airport code for travel start

Three-letter airport code of place where this portion of travel starts.

Note The leg’s departure airport code must match the airport code of the first flight segment belonging to this portion of travel. Otherwise, an error will be returned and transaction terminated.





Airport code for travel end

Three-letter airport code of place where this portion of travel ends.

Note The leg’s arrival airport code must match the airport code of the last flight segment belonging to this portion of travel. Otherwise, an error will be returned and transaction terminated.


Requested departure or arrival date or date and time when this portion of travel starts or ends

Departure or arrival date or date and time when this portion of travel starts or ends.

Note Dates or dates and times indicated on leg (O&D) level are not cross checked against dates or dates and times of related flight segments as it happens in case of not shopped legs.

• ExchangeShoppingRQ/Origin

DestinationInformation/DateT

imeSelection/DepartureDate



imeSelection/DepartureDateT

ime



imeSelection/ArrivalDate



imeSelection/ArrivalDateTime

Note All other search and pricing parameters are optional. For detailed information about available options to search for alternate itineraries, see “Optional Searching and Pricing Parameters,” page

123.

3.5.1.2.2 Information on the Segment Level

If the leg is shopped AND the “Use Same Connections” search parameter is used, at least two related segments are expected in the Exchange Shop request for this leg. If information about a minimum of two flight segments is not provided for such a leg, an error message will be returned and transaction

terminated.

Similarly to the leg that is not shopped, related segments continuity within the leg is validated and, if an

open jaw is detected, an error message will be returned and the transaction will be terminated.

The service will also validate whether the segments are sent in chronological order. If they are not, an

error message will be returned and transaction terminated.

The following flight segment information elements, as appearing in PNR, are required for the leg that is

not shopped (exactly the same data as for the leg that is not shopped described earlier in this document):


Operating carrier Two-character alphanumeric code for the operating carrier of the flight segment.

U0 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@operatingProvider




Marketing carrier Two-character alphanumeric code for the marketing carrier of the flight segment.

K0 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@marketingProvider

Flight number Numeric marketing flight number.

Note OPEN flight numbers are not supported at this time and if passed, an error message will be returned and transaction terminated.

001 ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@marketingFlightNumber

Departure date and time

Departure date and time of the flight segment.


2014-09-20T06:20:00

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@startDateTime

Arrival date and time

Arrival date and time of the flight segment.


2014-09-20T11:35:00

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@endDateTime

Departure airport Three-character departure airport of the flight segment.

JFK ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@startLocation

Arrival airport Three-character arrival airport of the flight segment.

BOS ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@endLocation

Reservation booking class

Code for the reservation booking class. Y ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@bookingClass

Reservation status

Reservation status as in PNR. HK ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment/@reservationStatus

3.5.1.2.3 Example of XML Request for the Leg that Is Shopped and “Use Same Connections” Search Parameter Is Applied.

Scenario: Mr. Globetrotter has the ticket issued for the trip from Saint Petersburg (LED) to New Delhi

(DEL) via Moscow (SVO) for departure on 2 April 2014:

KXNJJC

1.1GLOBETROTTER/JOHN MR

1 U0 19Y 02APR W*LEDSVO HK1 420P 535P /E

2 U0 232Y 02APR W SVODEL*HK1 725P 250A 03APR Q /E

TKT/TIME LIMIT



1.T-26JAN-MOW4EMB

2.TE 8882104266640 GLOBE/J MOW4EMB 0136/26JAN

However, his plans have changed and he needs to postpone his trip until 20 April. He does not have any specific time preferences. When calling the Exchange Shop web service, he indicates that he would like to

fly via same connecting airport as originally booked (SVO).

Following is what the Exchange Shop Request would look like for this leg.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.Sabre.com/STL/v01">242A60</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="KXNJJC"



</PassengerWithPNR>



preserveConnectionsIndicator="true"


<DateTimeSelection>



<StartLocation>LED</StartLocation>

<EndLocation>DEL</EndLocation>

<RelatedSegment

bookingClass="Y" endDateTime="2014-04-02T17:35:00"

endLocation="SVO" marketingFlightNumber="19" marketingProvider="U0"



startLocation="LED"/>

<RelatedSegment bookingClass="Y"

endDateTime="2014-04-03T02:50:00" endLocation="DEL"



startDateTime="2014-04-02T19:25:00" startLocation="SVO"/>





3.5.1.3 Leg is Shopped and “Use Same Connections” Shopping Parameter is NOT Applied

In the case of a leg that is shopped but the “Use Same Connections” search parameter is not applied:

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/@preserveConnectionsIndicator=”false” or is not

sent at all

No related flight segment information is required. Even if sent, it will be ignored in processing. All

necessary information is communicated on the leg level.

3.5.1.3.1 Information on the Leg Level

The following elements need to be passed for the leg that is not shopped:


Airport or city code for travel start

Three-letter airport or city code of place where this portion of travel should start.


Airport or city code for travel end

Three-letter airport or city code of place where this portion of travel should end.


Requested departure or arrival date or date and time when this portion of travel starts or ends

Departure or arrival date or date and time when this portion of travel should start or end.

• ExchangeShoppingRQ/OriginDestinatio

nInformation/DateTimeSelection/Depart

ureDate


nInformation/DateTimeSelection/Depart

ureDateTime


nInformation/DateTimeSelection/Arrival

Date


nInformation/DateTimeSelection/Arrival

DateTime

Note All other search and pricing parameters are optional. For detailed information about available options to search for alternate itineraries, see “Optional Searching and Pricing Parameters,” page

123.

3.5.1.3.2 Example of XML Request with Shopped Leg for which “Use Same Connections” Search Parameter Is not Applied

Scenario: Mr. Globetrotter has the ticket issued for the following itinerary. However, his trip to Kiev (KBP) to Mineralnye Vody (MRV) was canceled, and he wants to search for lowest available exchange solutions for flight from Moscow (MOW) to Saint Petersburg (LED) departing on 23 April 2014. He does not specify any additional search or pricing parameters.



PXSVXZ

1.1GLOBETROTTER/JOHN

1 U01805Y 16APR W*KBPSVO HK1 1130A 205P /E

2 U01302Y 16APR W SVOMRV*HK1 540P 755P /E TKT/TIME

LIMIT

1.T-26JAN-MOW4ET3

2.TE 8882104266641 A /T MOW4ET3 0305/26JAN

Following is the sample Exchange Shop request that will present information passed for this leg.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.Sabre.com/STL/v01">717DC6</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName=”GLOBETROTTER” pnrLocator="PXSVXZ"



</PassengerWithPNR>


<OriginDestinationInformation shopIndicator="true">

<DateTimeSelection>



<StartLocation>MOW</StartLocation>




3.5.2 Removing Segments from Already Ticketed Itinerary

If there are segments/legs that the user wants to delete from the booked itinerary, they should be omitted in the request sent to EXS-BSO. The Exchange Shop request should contain only these segments that are

going to be part of the new itinerary.



3.5.2.1 Example of XML Request where User Wants to Remove Some Portion of Ticketed Itinerary

Scenario: Mr. Globetrotter has the ticket issued for the trip from Mineralnye Vody (MRV) to Moscow

(SVO) and back.

1.1GLOBETROTTER/JOHN

1 U05371Y 16APR W MRVSVO HK1 0825 1050 /E

2 U01304Y 26APR J SVOMRV HK1 0855 1115 /E

TKT/TIME LIMIT

1.T-26JAN-MOW4ET3

2.TE 8882104267771 POMPK/F MOW4ET3 2256/26JAN

Due to business plan changes, he needs to fly to Moscow a week earlier, and this is going to be only a one-way ticket because he will have to return by another means of transportation. He uses the Exchange Shop web service to find the lowest available exchange itinerary options for this trip. The XML request sent to the service behind the scenes contains (in this case) only one leg: MRV-SVO for departure on 9

April 2014 and return portion of travel (SVO-MRV) is omitted in the request.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Actual


<ns2:Home


<ns3:Sine


<ns4:DutyCode


<ns5:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName=“GLOBETROTTER” pnrLocator="GCQCGV"



<PassengerTypeOverride>CNN</PassengerTypeOverride>

</PassengerWithPNR>




<DateTimeSelection>









3.5.3 Maximum Number of Legs vs. Maximum Number of Segments

The maximum number of supported legs (O&Ds) is 10. They may still consist of maximum 16 segments.

EXS Xpath for leg:


EXS Xpath for segment:

ExchangeShoppingRQ/OriginDestinationInformation/RelatedSegment

The following sections present the logic of legs and segments count that is applied for Exchange Shop

request validation purposes.

3.5.3.1 Shopped Leg

If the leg is shopped, and the Use Same Connections search parameter is NOT applied, it is counted as

one O&D and one segment at the same time.

3.5.3.1.1 Exchange Shop Request Example

The following request has one O&D, which is counted as one segment at the same time.

At the time the request is sent, it is not known what will be exact itinerary options (of how many flight

segments they will consist) that will be found as applicable for this leg. Therefore, for the request

validation purposes, the service assumes that it is one segment.

<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">242A60</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="EBNVLH"



</PassengerWithPNR>





<DateTimeSelection>



<StartLocation>AER</StartLocation>

<EndLocation>JFK</EndLocation>


<TravelPreferences/>


3.5.3.2 Not Shopped Leg

If the leg is not shopped, it is counted as one O&D and as many flight segments as related to this O&D.


The following request contains two legs (not shopped and shopped). Following is the total count of O&Ds

and segments for this request:

• Two O&Ds:

o One not shopped O&D AER-JFK 2 JUL

o One shopped O&D JFK-AER 16 JUL

• Three segments:

o Two related segments of not shopped O&D AER-JFK 2 JUL (AER-SVO, SVO-JFK)

o Shopped O&D JFK-AER 16 JUL that is counted as one segment

<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR






</PassengerWithPNR>




<DateTimeSelection>





<RelatedSegment


endLocation="SVO" marketingFlightNumber="1129"

marketingProvider="U0" operatingProvider="U0"

reservationStatus="HK" startDateTime="2014-07-02T06:05:00"

startLocation="AER"/>


endDateTime="2014-07-02T12:20:00" endLocation="JFK"







<DateTimeSelection>



<StartLocation>JFK</StartLocation>

<EndLocation>AER</EndLocation>




3.5.3.3 Shopped Leg for which “Use Same Connections” Search Parameter Is Applied

If the leg is shopped and the Use Same Connections shopping qualifier is applied to it, legs and segments

are counted as follows for the purpose of Exchange Shop request validation:

• The number of O&Ds to be counted for this leg is determined by the number of related segments for

this leg. This exception in counting is connected with the way the request to underlying subsystem is built when this qualifier is used. So, O&D with “Use Same Connections” applied that has two related

segments would be counted as two legs.

• The number of segments for this leg is equal to the number of related segments for this leg.

If the maximum number of legs of 10 is exceeded as logic for “Use same connection cities” count was

applied, an error message will be returned and transaction terminated:

“Unable to process – maximum number of supported portions of travel exceeded. Please refine your

search criteria and try again.”

In all other cases, schema validation will be used to determine if the request does not exceed maximum of

10 legs permitted.




The following request contains one leg that is shopped and “Use Same Connections” searching parameter

is applied. Following is the total count of O&Ds and segments for this request:

• Two O&Ds (as there are two related segments for this leg)

• Two segments

<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>





<DateTimeSelection>





<RelatedSegment
















3.5.4 Ability to Change Country of Origin

The airlines that opt for the ability to change the country of origin, resulting in mixed currencies when

exchanging the tickets, will also benefit from this function when using the Exchange Shop web service.

Benefit

If the user wants to exchange the ticket and have the trip originating in a different country, pricing in a different base currency than originally ticketed, Exchange Shop will process exchange calculations automatically and return all options that were correctly calculated. The user will be presented with

available exchange options and their cost.

Prerequisite

The airline needs to have the appropriate switches turned on in Ticketing Options Table for AER transactions in order to benefit from ability to exchange the tickets where base currency is different

between the exchanged ticket and new itinerary.


• This is applicable only to “Exchange” transactions as defined per IATA definition in Resolution

017F.

o Section C: Fully unused ticket where a passenger requests a change to the carrier, flight, date,

class of service or sector of the first flight coupon.

• All other transactions are treated as “Reissue” and will not allow for change of base currency.

• When requesting an itinerary change that involves changing the country of origin, “Payment Currency Code Override” pricing parameters can also be used, so the user can see exchange cost in

the preferred currency.

If the transaction Then

Is a “Reissue,” and the base currency of the new itineraries is different than the base currency in the exchanged ticket

The following messages appears: “CURRENCY CODE MUST MATCH EXCHANGE TICKET.”

On the fully unused ticket results in changing the first coupon (“Exchange”), and it involves a change of base currency

The following error message will no longer appear: “CURRENCY CODE MUST MATCH EXCHANGE TICKET.” Itineraries will be re-priced and options returned to the users provided all other fare rules conditions allow for the requested change.

Note The rules still apply for the currency in which the exchange cost is returned based on the result type of the transactions (Additional Collection, Even Exchange, Refund) described in “Exchange

Cost Breakdown per Each Passenger for Returned Itinerary,” page 306.

3.5.4.1 Example Scenarios

This section includes example scenarios and Exchange Shop XML requests and responses.



3.5.4.1.1 Shop for Change of Country of Origin

Following is a scenario for changing the country of origin.

Mr. Globetrotter has a ticket issued for the trip from Moscow (SVO) to London (LHR):

DNOGIG

1.1SMITH/JOHN

1 U02578Y 27SEP J SVOLHR HK1 1105A 1205P /E

TKT/TIME LIMIT

1.T-09JUL-MOW4TKT

2.TE 8882108083713 GLOBETROTTER/J MOW4TKT 1858/09JUL

The ticket was issued in the base fare EUR:


8882108083713 NAME-GLOBETROTTER/JOHN

TTL NBR OF CPNS- 1 DATE OF ISSUE-09JUL14 PNR-DNOGIG 09JUL14


1 U0 2578 Y 27SEP SVOLHR 1105 OK YNOW OK

FARE EUR 659.00 EQUIV PAID RUB 29000 TAX 1848YQ TAX

163YR TOTAL RUB 31011

FARE CALC MOW U0 LON896.12NUC896.12END ROE0.735385

FCMI-0

FORM OF PAYMENT

FOP-CASH

DATE OF ISSUE-09JUL14 ISSUED AT-MOWTR MOW TKT



IT-

REMARKS-

Now, he decides to change the origin country and search for alternate options for the flight from Delhi (DEL) to Moscow on September 25 and from Moscow to London (LHR) on September 27. This results in the base currency changing to INR as the trip will originate in India now. As the Exchange Shop transaction occurs in Moscow, the exchange cost will be returned in the default payment currency of

Russia – RUB.


• The airline sending the request opted for the ability to exchange documents involving change of base

currency.

• This is fully unflown ticket.

• The transaction results in the change of the first coupon in the ticket.

• All other fare categories allow for the exchange.

Exchange Shop processes the request and returns a list of alternate options to the user, as follows:




<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath

requestType="ADVEXC"/>

</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DNOGIG"



</PassengerWithPNR>




<DateTimeSelection>



<StartLocation>DEL</StartLocation>




<DateTimeSelection>




<EndLocation>LHR</EndLocation>



Exchange Shop Response XML

<ExchangeShoppingRS



<Header


timeStamp="2014-07-17T08:38:43">






<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination


startLocation="DEL">






startDateTime="2014-09-25T04:10:00" startLocation="DEL"

stopQuantity="0">


bookingClass="M" cabin="Y" documentNumber="8882108083713"

fareBasis="MEXOWA"

meal="D"/>



<OriginDestination

elapsedTime="250" endLocation="LHR" segmentQuantity="1"




endDateTime="2014-09-27T08:00:00" endLocation="LHR"




stopQuantity="0">





fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger

documentNumber="8882108083713" firstName="JOHN" lastName="GLOBETROTTER"

type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message

type="Advisory">LAST DATE TO PURCHASE 24JUL14 - 1346)4</Message>


</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination











stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>





<FareDifference



currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="3">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger


type="ADT">






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="4">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination











stopQuantity="0">



fareBasis="MEXOWA"

meal="L"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>



<Solution



sequence="5">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="L"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"




<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="6">

<BookItinerary>

<OriginDestination





endDateTime="2014-09-25T07:15:00" endLocation="FRA"

marketingFlightNumber="761" marketingProvider="LH"

marriageGroup="O" operatingProvider="LH"


stopQuantity="0">



fareBasis="Y77OW"

meal="M"/>


<ReservationSegment





startDateTime="2014-09-25T11:30:00" startLocation="FRA"

stopQuantity="0">



fareBasis="Y77OW"

meal="L"/>



<OriginDestination







endDateTime="2014-09-27T09:55:00" endLocation="DUS"




stopQuantity="0">



fareBasis="BNOW"

meal="B"/>


<ReservationSegment





startDateTime="2014-09-27T11:05:00" startLocation="DUS"

stopQuantity="0">



fareBasis="Y77"

meal="S"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<Message

type="Advisory">LAST DATE TO PURCHASE 21SEP14 - 1346)4</Message>


</Passenger>





<FareDifference

currencyCode="RUB"




<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


3.5.4.1.2 Add Payment Currency Code Override

In the scenario described previously, the passenger also requests to see the exchange cost in USD instead of the default payment currency of his location, which is RUB. The following is a sample request and

response for such a transaction.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DNOGIG"



</PassengerWithPNR>




<DateTimeSelection>










<DateTimeSelection>






<TravelPreferences>

<PriceRequestInformation currencyOverride="USD"/>

</TravelPreferences>



<ExchangeShoppingRS



<Header


timeStamp="2014-07-17T08:52:15">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination











stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="USD"

decimalPlace="2">293.00</FareDifference>

<TaxDifference

currencyCode="USD"

decimalPlace="2">221.30</TaxDifference>

<SubtotalDifference

currencyCode="USD"

decimalPlace="2">514.30</SubtotalDifference>


currencyCode="USD"

decimalPlace="2">514.30</GrandTotalDifference>

<Message



</Passenger>







<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger


type="ADT">






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"



</Solution>

<Solution



sequence="3">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>





<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="B"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"





</Solution>

<Solution



sequence="4">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="L"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"





currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"



</Solution>

<Solution



sequence="5">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="MEXOWA"

meal="D"/>



<OriginDestination









stopQuantity="0">





fareBasis="MEXOWA"

meal="L"/>



</BookItinerary>


<Passenger


type="ADT">




<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"



</Solution>

<Solution



sequence="6">

<BookItinerary>

<OriginDestination











stopQuantity="0">



fareBasis="Y77OW"

meal="M"/>


<ReservationSegment






stopQuantity="0">



fareBasis="Y77OW"

meal="L"/>



<OriginDestination





endDateTime="2014-09-27T09:55:00" endLocation="DUS"




stopQuantity="0">



fareBasis="BNOW"

meal="B"/>


<ReservationSegment





startDateTime="2014-09-27T11:05:00" startLocation="DUS"

stopQuantity="0">



fareBasis="Y77"

meal="S"/>



</BookItinerary>


<Passenger


type="ADT">






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<Message

type="Advisory">LAST DATE TO PURCHASE 21SEP14 - 1346)4</Message>


</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD" decimalPlace="2">3969.90</GrandTotalDifference>


</Solution>



• • •

Exchange Shop Searching and Pricing Parameters


4 Exchange Shop Searching and

Pricing Parameters

4.1 Introduction

The Exchange Shop web service offers a wide range of searching and pricing parameters that passengers or airline agents can use to narrow or widen shopping results. Customers can use all of them or choose the

ones that fit their business needs the best.

The purpose of this chapter is to provide detailed information about these parameters. Depending on the way they can be applied: per passenger, per leg, or per entire request, they are placed respectively in the

following parts of the Exchange Shop request XML:

EXS Xpath:

ExchangeShoppingRQ/PassengerInformation


ExchangeShoppingRQ/TravelPreferences

The following sections provide detailed information about each of them, specifying some business scenarios, describing expected results and referring to exact XML path where given parameters reside. The examples provided for each shopping parameter intend to present how the described qualifier can be

used in the Exchange Shop request XML, but obviously multiple searching qualifiers can be combined

within a single request with exceptions described in this chapter.

4.2 Required Search Parameters

Exchange Shop required parameters are to always be provided in the Exchange Shop request in order to

perform a search for alternate itinerary options.

They are defined per portion of travel in between two stopover places. For the stopover definition, see

“Essential Terms,” page 8.

4.2.1 Origin and Destination City or Airport

This qualifier provides the information about the origin and destination city/airport of given portion of

travel that is applied during Exchange Shop transaction. It needs to be provided if the user:

• Wants to leave the given portion of travel unchanged (leg not shopped).

• Wants to search for alternate options for a given leg (leg shopped), but wants to keep originally

booked airports and change, for example, only the date.

• Wants to search for alternate options for a given leg changing board/off city(ies) or add a new leg to

the already ticketed itinerary.

For more details about shopped and not shopped legs, see the following sections:

4



• “Leg Shopped vs. Leg Not Shopped,” page 10.

• “Three Types of Legs in Exchange Shop Request,” page 41 for additional tips on forming the request

for each type of leg.


• Defined on leg (O&D) level.

• When requesting origin or destination using a city code, such as New York (NYC), the service will

consider all airports belonging to a specified city as per Dynamic Schedule Finder (DSF) settings for

multi-airports city.

• When requesting origin or destination using the airport code, such as EWR (Newark airport), the

service will consider only this airport when searching for the exchange itinerary options.

EXS Xpaths:



4.2.1.1 Sample XML Request and Response

Scenario: Mr. Globetrotter bought for himself (ticket issued for ADT PTC) and his daughter (ticket issued for CNN PTC) a ticket from Mineralnye Vody (MRV) to Moscow (SVO) and back.

DAGSAJ

1.1GLOBETROTTER/JOHN 2.1GLOBETROTTER/ELIZABETH

1 U01304Y 23APR W SVOMRV HK2 845A 1100A /E

2 U05371Y 28APR M MRVSVO HK2 825A 1050A /E

1.T-02FEB-MOW4ET3

2.TE 8882105168050 JOHN/G MOW4ET3 1548/02FEB

3.TE 8882105168051 ELIZA/G MOW4ET3 1548/02FEB

Their plans have changed; however, now they need to do the following:

• Keep their outbound trip unchanged and fly from SVO to MRV on 23 APR as booked (leg 1).

• Change return date from MRV-SVO to 30 APR (leg 2).

• Add flight from Moscow (SVO) to Sankt Petersburg (LED) on 5 MAY (leg 3).

• Search for exchange options using Exchange Shop.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home




<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">242AC4</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName=“GLOBETROTTER” pnrLocator="DAGSAJ"



</PassengerWithPNR>

<PassengerWithPNR

firstName="ELIZABETH" lastName="GLOBETROTTER" pnrLocator="DAGSAJ"



</PassengerWithPNR>




<DateTimeSelection>





<RelatedSegment










<DateTimeSelection>








<DateTimeSelection>












<Header


02-02T05:48:32">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>






<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">242AC4</ns6:Lniata>


<ShoppingPath requestType="ADVEXC"/> </POS>

<Solution passengersInDifferentCabins="true" pricingSequence="1"

requireSplitPNR="true" sequence="1">

<BookItinerary>









stopQuantity="0">



<PassengerBookingDetails bookingClass="M" cabin="Y"

documentNumber="8882105168051" fareBasis="MEXRF" meal="B"/>



<OriginDestination elapsedTime="140" endLocation="SVO"

segmentQuantity="1" startLocation="MRV">







stopQuantity="0">


documentNumber="8882105168050" fareBasis="YOWRF" meal="L"/>

<PassengerBookingDetails bookingClass="L" cabin="Y"



documentNumber="8882105168051" fareBasis="LEXRF/CH25" meal="L"/>



<OriginDestination elapsedTime="80" endLocation="LED"








stopQuantity="0">


documentNumber="8882105168050" fareBasis="YOWRF" meal="B"/>

<PassengerBookingDetails bookingClass="K" cabin="Y"

documentNumber="8882105168051" fareBasis="KEXOWRF/CH25" meal="B"/>



</BookItinerary>


<Passenger documentNumber="8882105168050"

firstName="JOHN" lastName=“GLOBETROTTER” type="ADT">


04-16">








1346)4</Message>


</Passenger>


firstName="ELIZABETH" lastName="GLOBETROTTER" type="CNN">


02-09">







<Message type="Advisory">LAST DATE TO PURCHASE 09FEB14 -

1346)4</Message>


</Passenger>










</Solution>





<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">










1346)4</Message>


</Passenger>


firstName="ELIZABETH" lastName="GLOBETROTTER " type="CNN">


02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>


firstName="ELIZABETH" lastName="GLOBETROTTER " type="CNN">


02-09">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>



firstName="JOHN" lastName=“ GLOBETROTTER” type="ADT">


04-16">










1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">




documentNumber="8882105168051" fareBasis="KEXOWRF/CH25" meal="L"/>



</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>







04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>







04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>


4.2.2 Departure or Arrival Date or Date and Time

This qualifier provides the information about the departure or arrival date or date and preferred time of the given portion of travel that is applied during the Exchange Shop transaction. It needs to be provided

when the user:

• Wants to leave a given portion of travel unchanged (leg not shopped).

• Wants to search for alternate options for a given leg (leg shopped), but wants to keep originally

booked date and change, such as only departure city.

• Wants to search for alternate options for a given leg changing the travel date or add a new leg to the

already ticketed itinerary.

For more details about shopped and not shopped legs, see the following sections:



• “Leg Shopped vs. Leg Not Shopped,” page 10.

• “Three Types of Legs in Exchange Shop Request,” page 41 for additional tips on forming the request

for each type of leg.


• These parameters are applied per leg.

• Either departure OR arrival date or date and time can be requested per single leg.

• If both departure AND arrival date or date and time are requested per the same leg, an error message

will be returned. This is controlled by the Exchange Shop XML schema.

• If there is more than one leg within the request, departure or arrival dates or dates and times can be combined between different legs, for example, on the first leg, departure time is used and on the

second one, arrival date and preferred time.

• The Sabre system can process date requests that are 331 days from the date the request is sent.

• The date/time is considered as local date/time at associated airport/city. For departure date/time, it is

the local date/time at the origin airport/city, for arrival – local date/time at destination airport/city.

• Departure or arrival dates or dates and times are applied respectively to trip origin or destination

city⎯connecting cities are not taken into consideration.

Example:

For the following portion of travel: from Los Angeles (LAX) to Auckland (AKL) via Melbourne

(MEL):

o If using departure date or date and time qualifier, this date or date and time is applied to departure

from LAX.

o If using arrival date or date and time qualifier, this date or date and time is applied to arrival to

AKL.

o MEL (as a connecting city) is not taken into consideration.

• If departure or arrival time is indicated in the request, the Exchange Shop web service will search for

the flights using the requested time as the preferred one.

• If no departure or arrival is sent in the request, the service will check for the flights departing or arriving between 00:00 and 23:59 of the day indicated as departure or arrival date. However, preferred flights will be the ones departing or arriving close to the time set as default time in DSF

profiles.

EXS Xpaths:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDate

or:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDateTime

or:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/ArrivalDate

or:



ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/ArrivalDateTime

4.2.2.1 Sample XML Request and Response

Scenario: Mr. Globetrotter bought for himself and his daughter ticket from Mineralnye Vody (MRV) to

Moscow (SVO) and back.

DAGSAJ

1.1GLOBETROTTER/JOHN 2.1GLOBETROTTER/ELIZABETH

1 U01304Y 23APR W SVOMRV HK2 845A 1100A /E

2 U05371Y 28APR M MRVSVO HK2 825A 1050A /E

1.T-02FEB-MOW4ET3

2.TE 8882105167857 JOHN/G MOW4ET3 1548/02FEB

3.TE 8882105167858 ELIZA/G MOW4ET3 1548/02FEB

However, their plans have changed, and now they need to:

• Keep their outbound trip unchanged and fly from SVO to MRV on 23 APR as booked (leg 1).

• Change return date from MRV-SVO to 30 APR (leg 2) and have no preferences regarding departure

time.

• Add flight from Moscow (SVO) to Saint Petersburg (LED) arriving at LED airport on 5 MAY and

preferably around 18:00 (leg 3).


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">4DBDCB</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName=“GLOBETROTTER” pnrLocator="DTDRUB"



</PassengerWithPNR>

<PassengerWithPNR

firstName="GLOBETROTTER" lastName="ELIZABETH" pnrLocator="DTDRUB"





</PassengerWithPNR>




<DateTimeSelection>





<RelatedSegment










<DateTimeSelection>








<DateTimeSelection>

<ArrivalDateTime>2014-05-05T18:00:00.000</ArrivalDateTime>





<Diagnostic type="NONE"/>





<Header


02-02T06:44:50">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>








<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">4DBDCB</ns6:Lniata>





<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>







04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>



firstName="JOHNR" lastName=“GLOBETROTTER” type="ADT">


04-16">








1346)4</Message>


</Passenger>


firstName="ELIZABTEH" lastName="GLOBETROTTER" type="CNN">


02-09">








1346)4</Message>




</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105167857" fareBasis="BRTRF" meal="B"/>


documentNumber="8882105167858" fareBasis="BRTRF/CH50" meal="B"/>











stopQuantity="0">


documentNumber="8882105167857" fareBasis="YRT"/>


documentNumber="8882105167858" fareBasis="YRT/CH50"/>










stopQuantity="0">


documentNumber="8882105167857" fareBasis="BRTRF" meal="L"/>


documentNumber="8882105167858" fareBasis="BRTRF/CH50" meal="L"/>











stopQuantity="0">




documentNumber="8882105167858" fareBasis="BOWRF/CH50" meal="L"/>



</BookItinerary>





04-17">









1346)4</Message>


</Passenger>




04-17">









1346)4</Message>


</Passenger>












</Solution>


4.3 Optional Searching and Pricing Parameters

Following are available optional searching and pricing parameters that can be applied by the user during

the Exchange Shop transaction to get expected results.

They are taken into consideration in the case of legs that are shopped. If set up for the leg that is not

shopped, they are ignored in transaction processing.

4.3.1 Search for Alternate Times before and/or after Departure Time

This parameter allows searching for alternate itinerary options departing given number of hours before

and/or after departure time specified in the request.


• Applicable per leg.

• The value can be from 001 to 009, which defines a window of 1 to 9 hours around the preferred

departure time.

• “Alternate Times before and/or after Departure time” cannot be combined with Search by Arrival

Date or Arrival Date and Time or Search by Departure/Arrival Time Range within the same leg.

• If the user shops for more than one leg, “Search for Alternate Times Before and/or After Departure Time” can be combined with Preferred Departure/Arrival Time Range, Search by Arrival Date or

Arrival Date and Time between different legs.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDateTime/@minus -

departure given number of hours before departure time specified in the request

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDateTime/@plus -

departure given number of hours after departure time specified in the request

4.3.1.1 Sample Request and Response XML

Scenario: Mr. Globetrotter has the following ticket from Moscow (SVO) to New York (JFK) and back:

DAIMIJ


1 U0 102Y 02JUL W SVOJFK HK1 320P 510P /E

2 U0 103Y 09JUL W JFKSVO HK1 710P 1215P 10JUL Q /E

1.T-03FEB-MOW4EMB

2.TE 8882105168052 GLOBE/J MOW4EMB 0135/03FEB



Due to some changes, he needs to rebook it for two weeks later. He shops for alternate itinerary options for departure on 16 JUL at 12:00 p.m.; however, he may also depart two hours earlier or later. When

returning, he wants to arrive in Moscow on 23 JUL, preferably around 10:00 a.m.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DAIMIJ"



</PassengerWithPNR>




<DateTimeSelection>

<DepartureDateTime

minus="2"

plus="2">2014-07-16T12:00:00</DepartureDateTime>






<DateTimeSelection>

<ArrivalDateTime>2014-07-23T10:00:00</ArrivalDateTime>










<Header




02-02T15:45:07">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>






<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">242A60</ns6:Lniata>





<BookItinerary>

<OriginDestination elapsedTime="605" endLocation="JFK"








stopQuantity="0">

<PassengerBookingDetails bookingClass="H" cabin="Y"

documentNumber="8882105167860" fareBasis="HHEX1" meal="LD"/>




segmentQuantity="1" startLocation="JFK">






startDateTime="2014-07-22T14:20:00" startLocation="JFK"

stopQuantity="0">

<PassengerBookingDetails bookingClass="Q" cabin="Y"

documentNumber="8882105167860" fareBasis="QHPX1" meal="LD"/>



</BookItinerary>


<Passenger documentNumber="8882105167860" firstName="JOHN"



02-05">




<TaxDifference currencyCode="RUB" decimalPlace="0">-216</TaxDifference>



<TotalFee currencyCode="RUB" decimalPlace="0" type="CHG">4550</TotalFee>




1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">

<PassengerBookingDetails bookingClass="N" cabin="Y"

documentNumber="8882105167860" fareBasis="NHPX1" meal="LD"/>









marriageGroup="O" operatingProvider="DL"


stopQuantity="0">


documentNumber="8882105167860" fareBasis="AHPRT" meal="D"/>



</BookItinerary>





02-05">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRT"/>











stopQuantity="0">





</BookItinerary>





02-05">












1346)4</Message>


</Passenger>











</Solution>


4.3.2 Departure or Arrival Time Range

This qualifier allows searching for itinerary solutions by departure or arrival time range.



• The default is to check all flight times.

• This applies to origin/destination only – not to intermediate flights.

Example

For the leg from Larnaca (LCA) to London (LON) via Amsterdam (AMS), the system considers the

departure time range of flights from LCA or arrival time range in LON. AMS as connecting city is

not considered.

• Either departure or arrival time range can be requested for a given leg.

• If departure/arrival time window is requested, both time window start and end must be passed;

otherwise, the time range parameter will be ignored in processing.

• Combining departure or arrival time range with Preferred Departure or Arrival Time or “Alternate Time before/after Departure” searching parameters within a single leg is not allowed and controlled

by the XML schema.

Example 1:

Departure time range from “0600” to “1015” means that only flights departing from the origin city

between 06:00 and 10:15 should be returned as Exchange Shop itinerary options.

Example 2:

Arrival time range from “1200” to “1800” means that only flights arriving to the destination city between

12:00 and 18:00 should be returned as Exchange Shop itinerary options.



EXS Xpaths:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDate/@timeWindowS

tart

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DepartureDate/@timeWindowE

nd

or:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/ArrivalDate/@timeWindowStar

t

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/ArrivalDate/@timeWindowEnd


Scenario: Mr. Globetrotter has the following ticket from Moscow (SVO) to New York (JFK) and back:

DAIMIJ


1 U0 102Y 02JUL W SVOJFK HK1 320P 510P /E

2 U0 103Y 09JUL W JFKSVO HK1 710P 1215P 10JUL Q /E

1.T-03FEB-MOW4EMB


Due to some changes, he needs to rebook it for two weeks later. He shops for alternate itinerary options for departure from SVO on 16 JUL between 08:00 and 12:00 and return to SVO on 23 JUL arriving

between 12:00 and 15:00.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DAIMIJ"





</PassengerWithPNR>




<DateTimeSelection>

<DepartureDate

timeWindowEnd="12:00:00"

timeWindowStart="08:00:00">2014-07-16</DepartureDate>







<DateTimeSelection>

<ArrivalDate

timeWindowEnd="15:00:00" timeWindowStart="12:00:00">2014-07-23</ArrivalDate>










<Header


02-02T16:47:45">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>











stopQuantity="0">


documentNumber="8882105167860" fareBasis="HHEX1" meal="LD"/>











stopQuantity="0">


documentNumber="8882105167860" fareBasis="QHPX1" meal="LD"/>



</BookItinerary>





02-05">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">













stopQuantity="0">





</BookItinerary>





02-05">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRT" meal="LD"/>







endDateTime="2014-07-22T14:34:00" endLocation="MIA"




stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRT" meal="G"/>







startDateTime="2014-07-22T17:00:00" startLocation="MIA"

stopQuantity="0">





</BookItinerary>





02-05">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-05">












1346)4</Message>


</Passenger>











</Solution>


4.3.3 Search for Preferred Airline

The Preferred Airline indicator narrows returned options only to the ones that consist of indicated

carrier(s).



• The default is to check all carriers if carrier application is not restricted by Category 31 rules or other

restrictions of the exchanged fare.

• Up to 20 preferred carriers per leg can be specified.

• The carrier code must be two alphanumeric characters. If any character other than alpha or numeric is

entered or is not a two-character code, an error will be returned.

• This applies only to the marketing carrier. The operating carrier is not taken into consideration.

• If the preferred and non-preferred (see “Exclude an Airline,” page 149) carrier instructions are both

included, the same carrier code should not be found in both. If the same airline is indicated, an error

will be returned:

“Unable to process the request where the same airline: {carrier’s two-character code} is indicated

as preferred and non-preferred carrier. Please amend your request and try again.”

Note For this validation, only the legs that are shopped are taken into consideration.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/IncludeVendor


Scenario: Mr. Globetrotter has the ticket issued for flight from Paris (CDG) via Moscow (SVO) to Delhi

and then from Delhi to Mumbai.

LJGCGG


1 U0 260U 22JUL T*CDGSVO HK1 1145A 520P /E



2 U0 232U 22JUL T SVODEL*HK1 725P 255A 23JUL W /E

3 K0 332H 29JUL T DELBOM HK1 715A 915A /RL9W*DAIAVZ /E

1.T-02FEB-MOW4EMB


However, his business plans have changed⎯flights from CDG to DEL should remain the same, but he needs to fly from DEL to Bangalore (BLR) instead of BOM departing on 30 JUL. His preferred carrier on

this route is Worldwide Air (K0), and he wants to get exchange options on this leg with this carrier only.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="LJGCGG"



</PassengerWithPNR>




<DateTimeSelection>



<StartLocation>CDG</StartLocation>


<RelatedSegment

bookingClass="U" endDateTime="2014-07-22T17:25:00"




startLocation="CDG"/>

<RelatedSegment bookingClass="U"










<DateTimeSelection>




<EndLocation>BLR</EndLocation>

<IncludeVendor>K0</IncludeVendor>






<Header


02-02T13:56:05">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>

<OriginDestination elapsedTime="700" endLocation="DEL"

segmentQuantity="2" startLocation="CDG">






startDateTime="2014-07-22T11:45:00" startLocation="CDG"

stopQuantity="0">

<PassengerBookingDetails bookingClass="U" cabin="Y"

documentNumber="8882105167860" fareBasis="UEXOWA" meal="L"/>








marriageGroup="I" operatingProvider="U0"


stopQuantity="0">


documentNumber="8882105167860" fareBasis="UEXOWA" meal="D"/>



<OriginDestination elapsedTime="150" endLocation="BLR"

segmentQuantity="1" startLocation="DEL">



endDateTime="2014-07-30T23:05:00" endLocation="BLR"

marketingFlightNumber="834" marketingProvider="K0"

marriageGroup="O" operatingProvider="K0"


stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IP" meal="D"/>



</BookItinerary>





02-02">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IP" meal="L"/>



</BookItinerary>





02-02">









1346)4</Message>


</Passenger>











</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IP" meal="S"/>



</BookItinerary>





02-02">









1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IP" meal="B"/>



</BookItinerary>





02-02">











1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">









endDateTime="2014-07-30T09:30:00" endLocation="MAA"




stopQuantity="0">











startDateTime="2014-07-30T12:35:00" startLocation="MAA"

stopQuantity="0">





</BookItinerary>





02-02">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">









endDateTime="2014-07-30T10:10:00" endLocation="BOM"




stopQuantity="0">









startDateTime="2014-07-30T13:10:00" startLocation="BOM"

stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IPJK" meal="L"/>



</BookItinerary>





02-02">










1346)4</Message>


</Passenger>











</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-02">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">












stopQuantity="0">


documentNumber="8882105167860" fareBasis="H2IPJK" meal="S"/>



</BookItinerary>





02-02">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-02">










1346)4</Message>


</Passenger>













</Solution>


4.3.4 Exclude an Airline

The Exclude an Airline indicator narrows returned options only to the ones that do not include non-

preferred carrier(s).


• Applicable per entire request.

• The default is to check all carriers if the carrier application is not restricted by Category 31 rules or

restrictions of any other category of exchanged fare.

• Up to 20 non-preferred carriers per itinerary can be specified.

• The carrier code must be two alphanumeric characters. If any character other than alpha or numeric is

entered or these are not two characters, an error message will be returned.

• This applies only to the marketing carrier. The operating carrier is not taken into consideration.

• If the preferred (see “Search for Preferred Airline,” page 135) and non-preferred carrier instructions

are both included, the same carrier code should not be found in both. If the same airline is indicated,

an error will be returned:

“Unable to process the request where the same airline: {carrier’s two-character code} is indicated

as preferred and non-preferred carrier. Please amend your request and try again.”

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/ExcludeVendor




LJGCGG





1.T-02FEB-MOW4EMB


However, his business plans have changed⎯flights from CDG to DEL should remain the same, but he needs to fly from DEL to Bangalore (BLR) instead of BOM departing on 30 JUL. He does not want to travel on this route with Worldwide Air (K0) carrier, so when calling Exchange Shop, he excludes this

airline.



<ExcludeVendor>K0</ExcludeVendor>






<Header


02-02T14:39:18">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>









stopQuantity="0">










stopQuantity="0">












marketingFlightNumber="807" marketingProvider="XX"

marriageGroup="O" operatingProvider="XX"


stopQuantity="0">





</BookItinerary>





02-03">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">













stopQuantity="0">





</BookItinerary>





02-03">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





02-03">









1346)4</Message>


</Passenger>











</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





02-03">









1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">









endDateTime="2014-07-30T09:30:00" endLocation="MAA"




stopQuantity="0">









startDateTime="2014-07-30T12:35:00" startLocation="MAA"

stopQuantity="0">







</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-03">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">







</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>




4.3.5 Specify Maximum Number of Connections Permitted per Leg

The Maximum Number of Connections indicator allows you to set the maximum acceptable number of

connections allowed per leg in the itinerary. Intermediate stops with no change of plane are not counted as

connections for the purposes of this indicator.


• Applicable per entire request (to all shopped legs). It is not possible to request a different maximum

number of connections per each leg.

• Possible values are: 0, 1, 2, or 3 to indicate the maximum number of connections.

• The default is 3.

• If any other number is entered, an error message will be returned.

• Zero (0) indicates a request for nonstop or direct flights only.

• This qualifier cannot be combined with Use Same Connections and/or Specify Maximum Number of

Stops per Leg.

Example:

The following itinerary includes one connection (in IAH) + one hidden stop (on IAH-SIN flight)

1 U0 519 N 10JUN M DFW IAH 1125A 1235P S80 0 /E

1 K0 61 W 10JUN M IAH SIN 0535P 0545A 77W 1 /E

When the user requests itineraries with Maximum Number of Connections = 1, this itinerary can be

returned as the solution.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/Flight/@maxConnections



(DEL) and then from Delhi to Mumbai (BOM).

LJGCGG





1.T-02FEB-MOW4EMB


However, his business plans have changed⎯flights from CDG to DEL should remain the same, but he needs to fly from DEL to Bangalore (BLR) instead of BOM departing on 30 JUL. He also needs to add a return portion of travel from DEL to CDG on 7 AUG and, for both shopped legs, he wants to get only

direct/non-stop flight offers.





<DateTimeSelection>




<EndLocation>CDG</EndLocation>


<TravelPreferences>

<Flight maxConnections="0"/>






<Header


02-03T07:38:27">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>









stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRTA" meal="L"/>










stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRTA" meal="D"/>











stopQuantity="0">





<OriginDestination endLocation="DEL" segmentQuantity="0"

startLocation="BLR" surfaceSegment="true"/>

<OriginDestination elapsedTime="550" endLocation="CDG"




endDateTime="2014-08-07T18:55:00" endLocation="CDG"

marketingFlightNumber="143" marketingProvider="AI"

marriageGroup="O" operatingProvider="AI"


stopQuantity="0">


documentNumber="8882105167860" fareBasis="YIF" meal="M"/>



</BookItinerary>





02-03">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">







</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">















stopQuantity="0">





</BookItinerary>





02-03">










1346)4</Message>


</Passenger>











</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">





</BookItinerary>







02-03">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRTA" meal="B"/>













stopQuantity="0">


documentNumber="8882105167860" fareBasis="YFF" meal="BM"/>



</BookItinerary>





07-16">









<Message type="Advisory">LAST DATE TO PURCHASE 16JUL14 -

1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">


documentNumber="8882105167860" fareBasis="BNRTA" meal="S"/>













stopQuantity="0">





</BookItinerary>





07-16">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">

















stopQuantity="0">





</BookItinerary>





07-16">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105167860" fareBasis="YIF" meal="L"/>










stopQuantity="0">


documentNumber="8882105167860" fareBasis="YIF" meal="D"/>











stopQuantity="0">















stopQuantity="0">





</BookItinerary>




<ResultPriceDifference differenceType="AddCollect">










</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">







</BookItinerary>














</Passenger>











</Solution>


4.3.6 Specify Maximum Number of Stops Permitted per Leg

This qualifier allows you to set the maximum acceptable number of stops allowed per portion of travel in the itinerary where intermediate stops with no change of plane are counted as connections for the

purposes of this indicator.


• Applicable per entire request (to all shopped legs). It is not possible to request different number of

maximum number of stops per each leg.

• Possible values are: 0, 1, 2, or 3 to indicate the maximum number of stops.

• If any other number than above entered, an error message will be returned.

• Zero (0) indicates a request for nonstop flights only.

• This qualifier cannot be combined with Use Same Connections and/or Specify Maximum Number of

Connections per Leg.

Example:

The following itinerary includes one connection (in IAH) + one hidden stop (on IAH-SIN flight):

1 U0 519 N 10JUN M DFW IAH 1125A 1235P S80 0 /E

1 K0 61 W 10JUN M IAH SIN 0535P 0545A 77W 1 /E



When the user requests itineraries with Maximum Number of Stops Permitted per Leg = 1, this itinerary will not be returned as the solution as it contains one stop with change of plane (IAH) and also one stop

with no change of plane (during IAH-SIN flight).

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/@maxStops




LJGCGG





1.T-02FEB-MOW4EMB


However, his business plans have changed⎯flights from CDG to DEL should remain the same, but he needs to fly from DEL to Bangalore (BLR) instead of BOM departing on 30 JUL. He also needs to add a return portion of travel from DEL to CDG on 7 AUG and, for both shopped legs, he wants to get only

those flight offers that have a maximum of one stop in each leg.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>













<BookItinerary>









stopQuantity="0">


documentNumber="8882105167860" fareBasis="UEXA" meal="L"/>








stopQuantity="0">


documentNumber="8882105167860" fareBasis="UEXA" meal="D"/>











stopQuantity="0">

















stopQuantity="0">


documentNumber="8882105167860" fareBasis="MEXA" meal="D"/>








stopQuantity="0">


documentNumber="8882105167860" fareBasis="MEXA" meal="L"/>



</BookItinerary>





02-04">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">













stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-04">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">

















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-04">










1346)4</Message>


</Passenger>











</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">


documentNumber="8882105167860" fareBasis="DNRTA" meal="D"/>










stopQuantity="0">


documentNumber="8882105167860" fareBasis="DNRTA" meal="L"/>



</BookItinerary>





02-04">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-04">










1346)4</Message>




</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">

















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-04">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>







02-04">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-04">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">















stopQuantity="0">












stopQuantity="0">





</BookItinerary>





02-04">










1346)4</Message>


</Passenger>











</Solution>


4.3.7 Specify Online Carrier Service Only

This parameter allows searching for online (single carrier) itineraries.


• Applied per entire request.

• Each itinerary option will include flights of single (marketing) carrier only.

Note It does not need to be the requesting (validating) carrier.

• Carriers may be different in different options (for example, itinerary option 1 can have flights for XX

carrier, and itinerary option 2 can have flights for YY carrier only).

• The default is to search for both online and interline service itineraries if not restricted otherwise by Category 31 rules. If the user wants to request both online and interline itineraries, online and interline indicators (see “Specify Interline Carrier Service Only,” page 199) should be skipped in the

request.



• If the online indicator (see the following EXS Xpath) is set to “true,” only itineraries on a single-

carrier service are returned if applicable as per Category 31 rules of exchanged fare(s).

• This qualifier cannot be combined with “Specify interline carrier service only.” If both online and

interline indicators are set to “true,” an error will be returned.

• This is applied only to the marketing carrier. Operating carrier is not taken into consideration.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/@onlineIndicator


Scenario: Mr. Globetrotter has the ticket issued from Moscow (SVO) to Geneva (GVA).

DZOYJI


1 U02380Y 02JUL W SVOGVA HK1 1000A 1145A /E

TKT/TIME LIMIT

1.T-06FEB-MOW4EMB


Now, he needs to fly to Zurich (ZRH) instead of GVA, but requests exchange options for a single carrier

(online itineraries) only.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DZOYJI"





</PassengerWithPNR>




<DateTimeSelection>




<EndLocation>ZRH</EndLocation>


<TravelPreferences onlineIndicator="true"/>



<ExchangeShoppingRS



<Header


timeStamp="2014-02-06T06:20:17">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination

elapsedTime="210" endLocation="ZRH" segmentQuantity="1"






endDateTime="2014-07-02T12:35:00" endLocation="ZRH"




stopQuantity="0">



fareBasis="YNOW"

meal="L"/>



</BookItinerary>


<Passenger




differenceType="Even">



<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination











stopQuantity="0">



fareBasis="YNOW"

meal="L"/>



</BookItinerary>


<Passenger







<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


4.3.8 Specify Interline Carrier Service Only

This parameter allows searching for interline (multi-carrier service) itinerary options.




• Applied per entire request.

• If compliant with Category 31 restrictions of exchanged fare(s), each itinerary option will include

flights of multiple carriers (at least two).

• The default is to search for both online and interline itineraries if not restricted otherwise by Category 31 rules. If the user wants to request both online and interline itineraries, online and interline

indicators (see “Specify Online Carrier Service Only,” page 195) should be skipped in the request.

• If the interline indicator (see the following EXS Xpath is set to “true,” only itineraries with multiple-

carrier service are returned if applicable as per Category 31 rules of exchanged fare(s).

• This qualifier cannot be combined with “Specify Interline Carrier Service Only.” If both online and

interline indicators are set to “true,” an error will be returned.

• This is applied only to the marketing carrier. Operating carrier is not taken into consideration.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/@interlineIndicator


Scenario: Mr. Globetrotter has the following ticket issued:

HQBFTU


1 LH1451J 02JUL W DMEFRA HK1 705A 835A /E

2 U02307I 09JUL W FRASVO HK1 1130A 430P /E

TKT/TIME LIMIT

1.T-04FEB-MOW4EMB


Now, he needs to change it and wants to search for alternate options for departure from Moscow (DME) to Frankfurt (FRA) and requires the options to be interline (multiple carrier service) itineraries. Return

flight (FRA-SVO) should remain unchanged.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode




<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="HQBFTU"



</PassengerWithPNR>




<DateTimeSelection>




<EndLocation>FRA</EndLocation>




<DateTimeSelection>



<StartLocation>FRA</StartLocation>


<RelatedSegment

bookingClass="I" endDateTime="2014-07-09T16:30:00"




startLocation="FRA"/>


<TravelPreferences interlineIndicator="true"/>





<Header


02-04T10:14:47">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>













<BookItinerary>

<OriginDestination elapsedTime="205" endLocation="FRA"

segmentQuantity="1" startLocation="VKO">






startDateTime="2014-07-01T19:20:00" startLocation="VKO"

stopQuantity="0">

<PassengerBookingDetails bookingClass="J" cabin="C"

documentNumber="8882105170415" fareBasis="J77" meal="M"/>




segmentQuantity="1" startLocation="FRA">







stopQuantity="0">

<PassengerBookingDetails bookingClass="I" cabin="C"

documentNumber="8882105170415" fareBasis="IBR1"/>



</BookItinerary>




<ResultPriceDifference differenceType="Refund" lastDayToTicket="2014-03-

30">



<SubtotalDifference currencyCode="RUB" decimalPlace="0">-

18</SubtotalDifference>

<GrandTotalDifference currencyCode="RUB" decimalPlace="0">-

18</GrandTotalDifference>

<Message type="Advisory">LAST DATE TO PURCHASE 30MAR14 -

1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Refund">



<SubtotalDifference currencyCode="RUB" decimalPlace="0">-




<GrandTotalDifference currencyCode="RUB" decimalPlace="0">-



</Solution>



<BookItinerary>


segmentQuantity="1" startLocation="DME">






startDateTime="2014-07-01T13:50:00" startLocation="DME"

stopQuantity="0">













stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>





<BookItinerary>









stopQuantity="0">













stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">













stopQuantity="0">





</BookItinerary>












1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-07-01T14:50:00" endLocation="MUC"






stopQuantity="0">








marriageGroup="I" operatingProvider="XX"

startDateTime="2014-07-01T17:00:00" startLocation="MUC"

stopQuantity="0">


documentNumber="8882105170415" fareBasis="J77" meal="S"/>











stopQuantity="0">





</BookItinerary>





03-30">








1346)4</Message>


</Passenger>










</Solution>





<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





03-30">








1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





03-30">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>







03-30">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">







</BookItinerary>





03-30">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">





</BookItinerary>





03-30">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>






marketingFlightNumber="1325" marketingProvider="LX"

marriageGroup="O" operatingProvider="LX"


stopQuantity="0">

<PassengerBookingDetails bookingClass="C" cabin="C"

documentNumber="8882105170415" fareBasis="CIF" meal="B"/>






marriageGroup="I" operatingProvider="LX"

startDateTime="2014-07-01T12:15:00" startLocation="ZRH"

stopQuantity="0">




documentNumber="8882105170415" fareBasis="CIF" meal="M"/>











stopQuantity="0">


documentNumber="8882105170415" fareBasis="DNRT" meal="L"/>



</BookItinerary>





06-24">








<Message type="Advisory">LAST DATE TO PURCHASE 24JUN14 -

1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-07-01T08:20:00" endLocation="GVA"




stopQuantity="0">











startDateTime="2014-07-01T09:35:00" startLocation="GVA"

stopQuantity="0">


documentNumber="8882105170415" fareBasis="CIF" meal="O"/>











stopQuantity="0">





</BookItinerary>





03-30">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





03-30">









1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">













stopQuantity="0">





</BookItinerary>





03-30">









1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>





endDateTime="2014-07-01T12:30:00" endLocation="OSL"

marketingFlightNumber="8711" marketingProvider="SK"



stopQuantity="0">







marketingFlightNumber="3609" marketingProvider="SK"


startDateTime="2014-07-01T13:05:00" startLocation="OSL"

stopQuantity="0">


documentNumber="8882105170415" fareBasis="YIF" meal="O"/>











stopQuantity="0">





</BookItinerary>





06-24">











1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-07-01T16:35:00" endLocation="VIE"

marketingFlightNumber="602" marketingProvider="OS"

marriageGroup="O" operatingProvider="VO"


stopQuantity="0">








marriageGroup="I" operatingProvider="VO"

startDateTime="2014-07-01T17:10:00" startLocation="VIE"

stopQuantity="0">













stopQuantity="0">


documentNumber="8882105170415" fareBasis="CNRT" meal="L"/>



</BookItinerary>







06-25">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">








marriageGroup="I" operatingProvider="VO"


stopQuantity="0">















stopQuantity="0">





</BookItinerary>





06-25">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">





</BookItinerary>





06-25">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">













stopQuantity="0">





</BookItinerary>





06-25">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-07-01T11:50:00" endLocation="WAW"



marketingFlightNumber="5678" marketingProvider="LO"



stopQuantity="0">


documentNumber="8882105170415" fareBasis="CRT"/>







startDateTime="2014-07-01T14:00:00" startLocation="WAW"

stopQuantity="0">


documentNumber="8882105170415" fareBasis="CRT"/>











stopQuantity="0">


documentNumber="8882105170415" fareBasis="JNRT" meal="L"/>



</BookItinerary>













</Passenger>












4.3.9 Consider Only These Connection Cities/Airports

This indicator allows specifying connection cities or airports via which the traveler wants to fly.


• When using city codes indicating connecting points, such as LON (London), Exchange Shop will consider all airports belonging to specified city as per DSF settings for multi-airports city when

searching for itinerary options.

• When using airport code as connecting point, such as LHR (London Heathrow airport), Exchange

Shop will consider only this airport when searching for the exchange itinerary options.

• When defining one connection city, Exchange Shop will consider only this city/airport as connecting

point when searching for exchange itinerary options.

• When defining more than one connection city/airport, Exchange Shop will search for exchange itinerary options where one of the cities/airports is a connecting point or connecting points are constructed from the combination of indicated cities/airport. Options will not include flights via other

cities/airports than indicated in the request.

Example 1:

The traveler searches for exchange itinerary options from Los Angeles (LAX) to New York (NYC)

and indicates CHI (Chicago city code) as a connecting city.

Result: Exchange Shop will return only these exchange itinerary options that have either ORD

(Chicago O’Hare airport) or MDW (Chicago Midway airport) as a connecting airport.

Example 2:

The traveler searches for exchange itinerary options from LAX to NYC and indicates ORD (Chicago

O’Hare airport) as a connecting airport.

Result: Exchange Shop will return only these exchange itinerary options that have (Chicago O’Hare

airport) as a connecting airport.

Example 3:

Traveler searches for exchange itinerary options from LAX to NYC and indicates CHI (Chicago city

code) and DFW (Dallas Fort Worth airport) as connecting points.

Result: Exchange Shop will return only these exchange itinerary options that have either ORD (Chicago O’Hare airport) or MDW (Chicago Midway airport) as a connecting airport, or DFW as a

connecting airport or DFW and either ORD or MDW as connecting airports.

• Direct flights can also be returned if connection locations are requested.

• It can be combined with Use Same Connections searching parameter but not on the same leg. If, for

the same leg, both shopping parameters are used, an error message will be returned.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/ConnectionLocation/Location




Scenario: Mr. Globetrotter has a ticket issued for trip from Sochi (AER) via Moscow (SVO) to Beijing

(PEK):

DDPPJG


1 U01125L 02JUL W*AERSVO HK1 645P 905P /E

2 U0 204L 02JUL W SVOPEK*HK1 1040P 950A 03JUL Q /E

TKT/TIME LIMIT

1.T-06FEB-MOW4EMB


Now, he wants to change it and shop for alternate options for trip from Sochi (AER) to Xiamen (XMN) on 20 JUL; however, he wants to fly via these two connection points only: Moscow (SVO) and/or Beijing

(PEK).


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DDPPJG"



</PassengerWithPNR>



<DateTimeSelection>





<Location>SVO</Location>





<Location>PEK</Location>


<EndLocation>XMN</EndLocation>






<Header


02-06T11:59:44">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>

<OriginDestination elapsedTime="1360" endLocation="XMN"

segmentQuantity="3" startLocation="AER">






startDateTime="2014-07-22T13:55:00" startLocation="AER"

stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1" meal="L"/>




endDateTime="2014-07-23T09:50:00" endLocation="PEK"




stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1" meal="DB"/>






endDateTime="2014-07-23T16:35:00" endLocation="XMN"

marketingFlightNumber="1871" marketingProvider="CA"

marriageGroup="O" operatingProvider="CA"

startDateTime="2014-07-23T13:40:00" startLocation="PEK"

stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1" meal="D"/>



</BookItinerary>





04-20">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">










stopQuantity="0">





</BookItinerary>





04-20">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1" meal="B"/>








stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1" meal="LD"/>








stopQuantity="0">





</BookItinerary>





04-20">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">










stopQuantity="0">







marketingFlightNumber="7191" marketingProvider="HU"

marriageGroup="O" operatingProvider="HU"


stopQuantity="0">


documentNumber="8882105173369" fareBasis="LEXOW1"/>



</BookItinerary>





04-20">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">










stopQuantity="0">





</BookItinerary>





04-20">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">










stopQuantity="0">





</BookItinerary>





04-20">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">










stopQuantity="0">





</BookItinerary>







04-20">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">







marketingFlightNumber="377" marketingProvider="CZ"

marriageGroup="O" operatingProvider="CZ"


stopQuantity="0">

<PassengerBookingDetails bookingClass="V" cabin="Y"



documentNumber="8882105173369" fareBasis="VCN" meal="D"/>



</BookItinerary>





04-20">










1346)4</Message>


</Passenger>











</Solution>


4.3.10 Use Same Connections

This qualifier allows searching for exchange itinerary options using same connecting cities as already

booked/ticketed by the traveler.


• This qualifier cannot be combined with Specify the Maximum Number of Stops per Leg and/or

Specify the Maximum Number of Connections per Leg.

• It can be combined with Consider Only These Connection Cities/Airports, but not on the same leg. If,

for the same leg, both shopping parameters are used, an error message will be returned.

• Exchange Shop may return the options that have also some other connecting cities in addition to the

indicated ones in the request if lower fares are found for such itineraries.

This qualifier cannot be used for transactions without an active PNR as this option requires full

information about segments booked:

EXS Xpath: ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR



• For more information about forming the request using this searching parameter, see “Leg that Is

Shopped and “Use Same Connections” Shopping Parameter Is Applied,” page 46.

EXS Xpath: ExchangeShoppingRQ/OriginDestinationInformation/@preserveConnectionsIndicator=”true”


Scenario: Mr. Globetrotter has the following ticket issued for trip from Sankt Petersburg (LED) via Sochi

(AER) and Moscow (SVO) to Yakutsk (YKS) and then back to Moscow (SVO) directly.

MSFHZA


1 U05317T 02JUL W*LEDAER HK1 100P 410P /E

2 U01125T 02JUL W AERSVO HK1 645P 905P /E

3 U01750T 02JUL W SVOYKS*HK1 1005P 1030A 03JUL Q /E

4 U01751T 10JUL Q YKSSVO HK1 1230P 115P /E

TKT/TIME LIMIT

1.T-06FEB-MOW4EMB


Now, he needs to change departure trip and fly on 1 JUL, but wants to keep the same connection points as

booked. Return flight from YKS to SVO should remain unchanged.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="MSFHZA"





</PassengerWithPNR>





<DateTimeSelection>



<StartLocation>LED</StartLocation>

<EndLocation>YKS</EndLocation>

<RelatedSegment

bookingClass="T" endDateTime="2014-02-06T18:49:59.958Z"

endLocation="AER" marketingFlightNumber="5317"

marketingProvider="U0" operatingProvider="D9"


startLocation="LED"/>

<RelatedSegment bookingClass="T"






<RelatedSegment bookingClass="T"

endDateTime="2014-07-03T10:30:00" endLocation="YKS"








<DateTimeSelection>



<StartLocation>YKS</StartLocation>


<RelatedSegment

bookingClass="T" endDateTime="2014-07-10T13:15:00"



reservationStatus="HK" startDateTime="2014-07-10T12:30:00" startLocation="YKS"/>




<ExchangeShoppingRS



<Header


timeStamp="2014-02-06T13:02:36">




<STL:Results




<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination

elapsedTime="995" endLocation="YKS" segmentQuantity="3"

startLocation="LED">



endDateTime="2014-07-01T15:10:00" endLocation="AER"




stopQuantity="0">


bookingClass="T" cabin="Y" documentNumber="8882105173376"

fareBasis="TPXOWRF"

meal="L"/>


<ReservationSegment






stopQuantity="0">



fareBasis="TPXOWRF"

meal="L"/>


<ReservationSegment




endDateTime="2014-07-02T10:30:00" endLocation="YKS"




stopQuantity="0">



fareBasis="TPXOWRF"

meal="L"/>



<OriginDestination


startLocation="YKS">






startDateTime="2014-07-10T12:30:00" startLocation="YKS"

stopQuantity="0">



fareBasis="TPXOWRF"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"


<TotalFee

currencyCode="RUB" decimalPlace="0"

type="CHG">2500</TotalFee>


currencyCode="RUB"


<Message

type="Advisory">LAST DATE TO PURCHASE 30MAR14 - 1346)4</Message>


</Passenger>






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"


<TotalFee






</Solution>


4.3.11 Shop by Cabin Class

This qualifier allows the customer specifying the cabin in which the itinerary options should be searched.



• There are six cabin classes available:

o Economy

o Premium Economy

o Business

o Premium Business

o First

o Premium First

Jump Cabin Logic is enabled by default; however, depending on the value of Disable Jump Cabin

element in the Exchange Shop request:

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/@jumpCabinLogicDisabled

And/or settings in Intellisell Rules Manager, customer can change the behavior of the web service in

terms of cabins in which options are returned.

The following sections present this in the more detailed way.

EXS Xpath to request specific cabin:

ExchangeShoppingRQ/OriginDestinationInformation/Cabin



4.3.11.1 Jump Cabin Logic (default)

The idea of Jump Cabin Logic is to search for solutions in lower or higher cabin if requested or defaulted

cabin class is not offered or not available on searched itineraries.

4.3.11.1.1 Cabin Specified in the Request

If the cabin is specified in the Exchange Shop request, the following logic applies (for illustration

purposes, it is going to be explained using the example):

Example:

The traveler has the ticket issued (in any cabin class(es)) and now wants to shop for exchange options

searching for solutions in Business class.

Request processing:

• Shopping will check if there is a physical cabin (Business cabin, in this case) offered on the flights on

the route that is shopped.

If Then

There is a Business class compartment, but no inventory is available (flights are sold out)

Exchange Shop will not return any fares.

There is a Business class compartment and there are seats available in Business cabin (there is inventory available)

Exchange Shop will return offers in the requested cabin class (Business) and/or offers in higher (such as First class) if they are the cheapest (jump up).

Note If, for one itinerary, Business class is returned as the cheapest and for the other itinerary, First class is returned, they both will be returned in the response to the user.

There is no Business class compartment offered on flights on given route (the aircraft is not equipped with Business class service)

Shopping will jump down to the first offered lower cabin (such as Premium Economy)

• If there is inventory (seats are available) in the

Premium Economy, then Exchange Shop will

return the lowest available fare in Premium

Economy or any other cabin as long as it is

cheaper than Premium Economy and provided

that Category 31 of exchanged fare(s) allows for

downgrade.

• If there is no inventory (no seats available) in the

Premium Economy, then service will stop and

not return any fares.

• If there is a new leg added to the original ticket,

and the cabin for that leg is specified in the

request, then Shopping will check if there is a

requested cabin offered on the flights and apply

the logic described.



4.3.11.1.2 Cabin not Specified in the Request

If the cabin is not specified in the request, the following logic applies (for the illustration purposes it is

going to be explained using the example):

Example:

The traveler has the ticket issued (in any cabin class, such as Business) and now wants to shop for

exchange options but does not specify the cabin in the request.

Request processing:

• Shopping will not check in which cabin(s) the original ticket was issued and will default to lowest

cabin (Economy).

If Then

There is Economy class compartment but no inventory is available (flights are sold out)


There is an Economy class compartment and there are seats available in Economy cabin (there is inventory available)

Exchange Shop will consider Economy cabin offers + any other higher cabins (jump up) in pricing process.

• If Premium Economy will be the cheapest for the

given itinerary, then that is what Exchange Shop

will return

• If Economy will be the cheapest for given

itinerary, then that is what Exchange Shop will

return

Note If, for one itinerary, it is Economy class that is returned as cheapest and for other it is higher class, such as Premium Economy, they both will be returned in the response to the user.

There is no Economy class compartment offered on flights on given route (the aircraft is not equipped with Economy class service)

Exchange Shop will stop processing and not return any fares.


and the cabin for that leg is specified in the

request, then Shopping will check if there is a

requested cabin offered on the flights and apply

the logic described.


and no cabin for that leg was specified in the

request, then Shopping will search for the

options in the lowest cabin (Economy) – as

described.

• The above applies provided Category 31 rules

of the exchanged ticket allow exchanging to

lower cabin/Economy if the original ticket was

issued in a higher cabin, such as Business.



4.3.11.2 Disable Jump Cabin Logic

The idea of Disable Jump Cabin Logic option (also known as Expand Jump Cabin logic) is to return only

the flight options that have at least one segment in the requested cabin.

Disable Jump Cabin qualifier can be sent in the Exchange Shop request or it can be switched on or off at

the rule level in Intellisell Rules Manager.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/@jumpCabinLogicDisabled

Options in rules settings in Intellisell Rules Manager referring to Disable Cabin Logic settings:

• Default: if the request has a value for this option, then the value from the request is used for

processing; otherwise, the value in the rule is used for processing.

• Constant: the option value in the rule is always used for processing the request.

• Ignore: the value in the request is ignored. No value is sent to the underlying service.

4.3.11.2.1 Cabin Specified in the Request

If the cabin is specified in the request, the following logic applies if Jump Cabin Logic is disabled (for

illustration purposes, it is going to be explained using the example):

Example:

Traveler has the ticket issued (in any cabin class(es)) and now wants to shop for exchange options

searching for solutions in Business class. For this request, jump cabin logic is disabled.

Request processing:

• Exchange Shop will check if there is a physical cabin (Business) on the flights on the route that is

shopped.

If Then

There is a Business class compartment but no inventory is available (flights are sold out)


There is a Business class compartment, and there are seats available in Business cabin (there is inventory available)

Exchange Shop will treat Business cabin as highest permitted and return options with all segments in Business cabin.

The Business class compartment is not offered on some segments within a leg (requested cabin is offered and available on at least one segment)

Exchange Shop will jump down to the first offered lower cabin (such as Premium Economy) on the segments where the requested cabin is not offered (mixed cabin option created).

• If there is inventory (seats are available) for the

mixed cabin option (some segments in Business

cabin + some segments in Premium Economy),

then Exchange Shop will return fares in mixed

cabins for such an itinerary provided it meets

conditions of Category 31 of exchanged fare(s).



• If there is no inventory (seats are sold out) in



• If there is no inventory (seats are sold out) in



The Business compartment is not offered on any segment


Note If there is a new leg added to the original ticket, and the cabin for that leg is specified in the request, then Exchange Shop will check if there is a requested cabin offered on the flights and

apply above logic.

4.3.11.2.2 Cabin not Specified in the Request

If the cabin is not specified in the request, the following logic applies if Jump Cabin Logic is disabled (for

illustration purposes, it is going to be explained using the example):

Example:

Traveler has the ticket issued (in any cabin class, such as business) and now wants to shop for exchange

options, but does not specify cabin in the request.

Request processing:

• Shopping will not check in which cabin(s) original ticket was issued and will default to lowest cabin

(Economy).

If Then

There is an Economy class compartment offered (the aircraft is equipped with Economy class service), but no inventory is available (flights are sold out)


There is an Economy class compartment offered, and there are seats available in Economy cabin (there is inventory available)

Exchange Shop will determine Economy as highest permitted cabin and return options in Economy class only.

An Economy class compartment is not offered (the aircraft is not equipped with Economy class service)

Exchange Shop will stop processing and not return any fares

Notes

• If there is new leg added to the original ticket and no cabin for that leg is specified in the request, then

Shopping will search for the options in the lowest cabin (Economy) as described above.

• The above applies provided Category 31 rules of the original ticket allow exchanging to lower

cabin/Economy if exchanged ticket was issued in higher cabin, such as Business.




Following are examples of XML request and response with cabin class requested in Exchange Shop

query.

4.3.11.3.1 Sample Request and Response with Cabin Requested and Jump Cabin Logic Enabled

(default)

Scenario: Mr. Globetrotter has the following ticket issued for flight from Moscow (SVO) to New York (JFK) and back in Economy class. Now, he wants to change the dates of departure flight and also change

the return flying from New York (JFK) to Sochi (AER) this time and asking for options in Business

cabin.

DLTWED


1 U0 102Y 03JUL Q SVOJFK HK1 320P 510P /E

2 U0 103Y 10JUL Q JFKSVO HK1 710P 1215P 11JUL F /E

TKT/TIME LIMIT

1.T-07FEB-MOW4EMB



<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DLTWED"



</PassengerWithPNR>






<DateTimeSelection>







<DateTimeSelection>





<Cabin>Business</Cabin>




<ExchangeShoppingRS



<Header


timeStamp="2014-02-07T09:47:26">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination

elapsedTime="605" endLocation="JFK" segmentQuantity="1"










stopQuantity="0">



fareBasis="BNRT"

meal="LD"/>



<OriginDestination

elapsedTime="855" endLocation="AER" segmentQuantity="2"

startLocation="JFK">







stopQuantity="0">


bookingClass="C" cabin="C" documentNumber="8882105174934"

fareBasis="CNRT"

meal="LD"/>


<ReservationSegment






stopQuantity="0">


bookingClass="C" cabin="C" documentNumber="8882105174934"

fareBasis="CNRT"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





currencyCode="RUB"


<Message

type="Advisory">LAST DATE TO PURCHASE 25JUN14 - 1346)4</Message>


</Passenger>




<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


4.3.11.3.2 Sample Request and Response with Cabin Requested and Jump Cabin Logic disabled

Scenario: Mr. Globetrotter has below ticket issued for flight from Moscow (SVO) to New York (JFK) and back in Economy class. Now, he wants to change the dates of both: departure and return but requests

options for return flight (JFK-SVO) in Business cabin. Disabling jump cabin logic is also applied.

DLTWED




TKT/TIME LIMIT

1.T-07FEB-MOW4EMB



<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine




<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>




<DateTimeSelection>








<DateTimeSelection>







<TravelPreferences jumpCabinLogicDisabled="true"/>





<BookItinerary>









stopQuantity="0">


documentNumber="8882105174934" fareBasis="YNRT" meal="LD"/>













stopQuantity="0">


documentNumber="8882105174934" fareBasis="DNRT" meal="LD"/>



</BookItinerary>





06-24">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105174934" fareBasis="YNRT" meal="LD"/>













stopQuantity="0">





</BookItinerary>





06-24">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>





endDateTime="2014-07-01T13:45:00" endLocation="TLV"




stopQuantity="0">


documentNumber="8882105174934" fareBasis="BNRT" meal="L"/>





marketingFlightNumber="11" marketingProvider="LY"

marriageGroup="O" operatingProvider="LY"

startDateTime="2014-07-01T16:00:00" startLocation="TLV"

stopQuantity="0">


documentNumber="8882105174934" fareBasis="YIF" meal="BH"/>













stopQuantity="0">


documentNumber="8882105174934" fareBasis="CIF" meal="BH"/>








stopQuantity="0">





</BookItinerary>





06-24">









1346)4</Message>


</Passenger>










</Solution>




4.3.11.3.3 Sample Request and Response without Cabin Requested and Jump Cabin Logic Disabled

Scenario: Mr.Globetrotter has the following ticket issued for a flight from Moscow (SVO) to New York (JFK) and back in Economy class. Now, he wants to change the dates of both departure and return and

does not request any specific cabin. Disabling jump cabin logic is set in the request.

DLTWED




TKT/TIME LIMIT

1.T-07FEB-MOW4EMB



<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>




<DateTimeSelection>








<DateTimeSelection>






fareBasis="BNRT"

meal="L"/>


<ReservationSegment






stopQuantity="0">



fareBasis="YIF"

meal="BH"/>



<OriginDestination


startLocation="JFK">







stopQuantity="0">


bookingClass="D" cabin="C" documentNumber="8882105174934"

fareBasis="DIF"

meal="BH"/>


<ReservationSegment






stopQuantity="0">


bookingClass="D" cabin="C" documentNumber="8882105174934"

fareBasis="DNRT"

meal="L"/>



</BookItinerary>


<Passenger




differenceType="Refund"


<FareDifference

currencyCode="RUB"




<TaxDifference

currencyCode="RUB"

decimalPlace="0">-3960</TaxDifference>

<SubtotalDifference

currencyCode="RUB"

decimalPlace="0">-3870</SubtotalDifference>


currencyCode="RUB"

decimalPlace="0">-3870</GrandTotalDifference>

<Message

type="Advisory">LAST DATE TO PURCHASE 24JUN14 - 1346)4</Message>


</Passenger>



differenceType="Refund">



<TaxDifference

currencyCode="RUB"

decimalPlace="0">-3960</TaxDifference>

<SubtotalDifference

currencyCode="RUB"

decimalPlace="0">-3870</SubtotalDifference>


currencyCode="RUB" decimalPlace="0">-3870</GrandTotalDifference>


</Solution>


4.3.12 Shop by Corporate ID

This qualifier allows searching for negotiated fares using a Corporate ID.


• Applicable per entire request. If the request is for multiple passengers, such as two adults or one adult + one child, and the customer wants to use the Corporate ID to shop for exchange itineraries, this

Corporate ID will be applied for the Exchange Shop search for all passengers in the request.

• Exchange Shop may return the lowest applicable fare combination, but it might not be the negotiated corporate rate. If the negotiated fare filed with Corporate ID is more expensive than cheapest public

fare for this itinerary, it is the public fare that is going to be returned in Exchange Shop.

• If fares filed for a given Corporate ID are eligible for specific PTCs only, an applicable PTC should

be used in the Exchange Shop transaction. For more details about PTC, see “Override Passenger Type

Code,” page 264.

• Only one Corporate ID per transaction is allowed.

• Corporate ID cannot be combined with Account Code within a single request. For more information

about Account Code, see “Shop by Account Code,” page 260.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/PriceRequestInformation/@corporateID





DZOYJI



TKT/TIME LIMIT

1.T-06FEB-MOW4EMB


Now, he needs to fly to Zurich (ZRH) instead of GVA and wants to apply Corporate ID during the search.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>




<DateTimeSelection>






<TravelPreferences>

<PriceRequestInformation corporateID="ABC12"/>






<ExchangeShoppingRS



<Header


timeStamp="2014-02-06T06:20:17">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="YNOW"

meal="L"/>



</BookItinerary>




<Passenger







<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="YNOW"

meal="L"/>



</BookItinerary>




<Passenger







<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


4.3.13 Shop by Account Code

This qualifier allows searching for negotiated fares using an Account Code.


• Applicable per entire request. If the request is for multiple passengers, such as two adults or one adult + one child, and the customer wants to use an Account Code to shop for exchange itineraries, this

Account Code will be applied for the Exchange Shop search for all passengers in the request.

• Negotiated fare with an Account Code requested is going to be returned as an exchange itinerary option only if there is no public fare available for the given itinerary that would be cheaper than the

mentioned private fare

• If the private fare with the Account Code is more expensive than the cheapest public fare for this

itinerary, it is the published fare that is going to be returned by Exchange Shop.

• Only one Account Code per transaction is allowed.

• Account Code cannot be combined with Corporate ID. For more information about Corporate ID see

“Shop by Corporate ID,” page 256.



EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/PriceRequestInformation/@accountCode



DZOYJI



TKT/TIME LIMIT

1.T-06FEB-MOW4EMB


Now, he needs to fly to Zurich (ZRH) instead of GVA and wants to apply the Account Code during the

search.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>




<DateTimeSelection>






fareBasis="YNOW"

meal="L"/>



</BookItinerary>


<Passenger







<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">





fareBasis="YNOW"

meal="L"/>



</BookItinerary>


<Passenger







<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"



</Passenger>






<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"





</Solution>


4.3.14 Override Passenger Type Code

This parameter allows searching for flight itinerary options using specific Passenger Type Code (PTC) for

pricing purposes.


• Applicable per passenger and his/her whole itinerary.

• If for the given itinerary the adult (ADT) fare is cheaper than the fare for specified PTC and requested

PTC is mapped to ADT, a cheaper ADT fare is going to be returned.

• Only one PTC can be specified per given passenger.

• When no PTC is defined in the Exchange Shop Request, the service will default the search to the PTC that was priced with the ticket that is going to be exchanged. If the PTC is not stored in the VCR, the



user will be requested to provide it in the Exchange Shop request. For an example of the error message that is returned when the PTC is missing in the VCR and “Override Passenger Type code” is not applied for the indicated document, see “Table of Common Business Validation Errors,” page

459.

• Maximum of nine different PTCs are allowed per request.

• When checking options for infants (children under age 2 not occupying seats), such as INF, Exchange Shop may return alternate options in the booking class that is not available. Because the infant type passenger type does not occupy a seat, service does not verify availability to price. This is in

accordance with current pricing logic.

EXS Xpath:

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/PassengerTypeOverride

or:

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/PassengerTypeOverride

4.3.14.1 Requests for Infant PTCs Only

Exchange Shop does not support requests for infant PTCs only.

This applies to PTCs overridden in Exchange Shop request using the Shop by Passenger Type Code

parameter or, if not applied, to the default PTC with which the exchanged ticket was priced.

Example:

Shopping for exchange options for:

• INF only

• Two INFs only

• INF +JNF only

will result in an error message returned by the service.

There is a requirement of at least one accompanying non-infant type passenger in the Exchange Shop

query in order to process transaction.

4.3.14.2 Solution Returned in Different Booking Classes for Different PTCs

When Exchange Shop query involves multiple PTCs, such as two adults (ADT) and two youth passengers (YTH), the service might return an alternate itinerary solution in different booking classes for each PTC if

this will secure best pricing solution.

This applies to PTCs overridden in the Exchange Shop request using the Shop by Passenger Type Code

parameter or, if not applied, to the defaulted PTC with which the exchanged ticket was priced.

Note The following example is for illustration purposes only and does not reflect exact content of the

Exchange Shop response XML.

Example:

Solution 1:

U0 811 20 OCT MEL SYD



U0 800 23 OCT SYD MEL

For ADTs, it may be returned in booking class V as this will be the best applicable pricing solution for this passenger type, and for passengers with YTH PTC in “Q” class as this class will offer the best price

for this PTC.

When the solution includes different booking classes for different PTCs, the following flag will be set to

“true” in order to indicate that fulfilling the exchange in offered fares will require splitting PNR:

EXS Xpath:

ExchangeShoppingRS/Solution/@requireSplitPNR

To see a sample response for solutions requiring PNR split, see the XML example in “Example of XML

Request and Response Containing Solution that Requires PNR Split to Fulfill Exchange,” page 361.

Still, the rule of checking seats availability for total number of passengers in the request is applied. In this scenario, it is four, so fares in V and Q class will be returned provided in each of these booking classes

there are at least four seats available. This is designed to secure seats availability in “last seats” scenarios.

Example of “last seats” scenario:

Scenario 1:

There are four adult (ADT) and two youth (YTH) passengers, for a total of six. Now, looking into seats availability for the following flight, it would seem that there are two seats in H class and four seats in S

class. So, the fares in these classes could be offered:

26 MAY

2U0 327 J7 C3 D0 I0 Z0 Y7 K7 B7 N7 S4 H2 M0 T0 W0 L0 *LHRLCA 1000P

435A

However, when we book two seats in H class:

XXXXXX

1.1GLOBETROTTER/JOHN MR 2.1GLOBETROTTER/JANE MS

1 U0 327H 26MAY S LHRLCA HK2 1000P 435A 27MAY M /E

And then, go to seats availability again trying to book the remaining four in S class. You can see that now, in S class, there are only two seats remaining and we will not be able to provide these four

passengers with the fare in S class:

26 MAY


435A

Scenario 2:

We cancel this reservation and two seats are back in inventory. We have again two seats in H class and

four seats in S class:

26 MAY


435A



Now, we book four seats in S class:

XXXXXX

1.1GLOBETROTTER/JOHN MR 2.1GLOBETROTTER/JANE MS

3.1GLOBETROTTER/JAMIE MR 4.1GLOBETROTTER/SOPHIE MS

1 U0 327S 26MAY S LHRLCA HK4 1000P 435A 27MAY M /E

This made the inventory to be changed in the way that S class shows zero seats availability, but at the

same time, two seats from H class have gone, and they are no longer available:

26 MAY

2U0 327 J7 C3 D0 I0 Z0 Y7 K7 B7 N5 S0 H0 M0 T0 W0 L0*LHRLCA 1000P

435A

In such cases, it will no longer be possible to book seats in H class for the remaining two passengers. This

behavior for “last seats” availability is the same across all airlines.

In order to avoid these scenarios, when checking for alternate itinerary options, Exchange Shop will return only the fares in booking classes that secure seats for all passengers in the request. In this scenario, the service would return the fares in lowest applicable fare offering at least six seats available. In this

example, this would be N class.

Note Same or Different PTC Evaluation Logic: Evaluation of same or different PTC is done based on PTC in the Exchange Shop query (PTC coming from Exchange Shop request as PTC override or from exchanged document if not present in Exchange Shop request). Therefore, in the scenario

where there are two passengers, and they are shopped as ADT + YTH, but for the given itinerary, the cheapest solution for both of them is for ADT. When returning options, Exchange Shop may offer fares in different booking classes for these two passengers because they were requested as

different PTCs.

4.3.14.3 Solution Returned in Different Cabin Classes for Different PTCs

When the Exchange Shop request involves multiple PTCs, such as two (adults) ADTs, two (youth) YTHs,

Exchange Shop might return an alternate itinerary solution that has not only different booking classes, but also cabins for each PTC if this will secure the best pricing solution, such as Business for ADTs and

Economy for YTHs.

In the scenario, when an itinerary option returned in the Exchange Shop response has a different cabin on

at least one segment for different PTCs, the solution will contain a flag indicating this (along with the flag

indicating necessity of PNR split described in the previous section):

EXS Xpath:

ExchangeShoppingRS/Solution/@passengersInDifferentCabins="true"

Scenarios where two fares in two different cabins are published with same base amount

When there is a request for two different PTCs, such as ADT and CNN, and the airline filed two fares in different cabins with the same base amount and both meet the criteria of lowest available solution for both passengers (ADT and CNN), they are chosen randomly. Although the option returned is priced for ADT



for both passengers, the proposed fares may be in two different cabins (and consequently booking

classes).

Example:

There are two passengers, and they want to shop for exchange options on the SVO-MRV-SVO route. The Exchange Shop request is for two different PTCs: ADT+CNN. As the result of rule validation, for both

passengers, ADT fares are used with the same amount, but in different booking codes (and cabins in this

scenario):

Requested PTC Fare used

ADT ADT fare YRTRF (Economy cabin fare)

CNN ADT fare DRTRF (Business cabin fare)

This is caused by the fact that two fares are published with the same amount and fares are differently

prioritized for different PTCs in the request:

Fare Quote display:

FQ20JAN14SVOMRV10APR14-U0‡RT

MOW-MRV CXR-U0 THU 10APR14 RUB

U0 MOWMRV 10APR14

V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG

……

13 DRTRF D R 45000 ---- -/‡ -/355 15

14 YRTRF Y R 45000 ---- - -/365 15

Note Should the request be for the same PTC (such as two ADTs), the itinerary solution will be returned in the same booking classes (and consequently, cabins) in order to meet the requirement

of returning the same booking class for the same PTC.

Handling Infants in Terms of Options in Different Cabins

If the itinerary solution includes a fare for infant type PTCs, such as INF, booked on at least one segment within this itinerary in a cabin that is different than for any other non-infant PTC(s), the option will be

discarded from the Exchange Shop response because the infant passenger cannot travel in a different

cabin than the accompanying person.

Note There is no validation of the accompanying passenger for infant type PTCs performed.

4.3.14.4 Sample Request and Response XML with PTC Override

Scenario: Mr. Globetrotter has the ticket for himself and his baby girl Alice is flying as an infant (INF) for

the flight from Moscow (SVO) to New York (JFK) and back in July.

DMVWUQ

1.1GLOBETROTTER/JOHN MR 2.I/1GLOBETTROTTER/ALICE

1 U0 102L 02JUL W SVOJFK HK1 320P 510P /E

2 U0 103L 10JUL Q JFKSVO HK1 710P 1215P 11JUL F /E

TKT/TIME LIMIT

1.T-08FEB-MOW4EMB




3.TE 8882105174966 GLOBE/A MOW4EMB 2221/08FEB

1.OSI U0 INF

2.SSR INFT /GLOBETTROTTER/ALICE/10SEP12 NN1

Now, he needs to change travel dates and fly in October. In October, Alice will turn 2 years old and the INF fare will be no longer applicable – when shopping for exchange options, Mr. Globetrotter will need

to communicate this using the PTC override option in the Exchange Shop request.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DMVWUQ"



</PassengerWithPNR>

<PassengerWithPNR

firstName="ALICE" lastName="GLOBETTROTTER" pnrLocator="DMVWUQ"



<PassengerTypeOverride>C03</PassengerTypeOverride>

</PassengerWithPNR>




<DateTimeSelection>







<DateTimeSelection>













<Header messageID="TKTHLI703-25902-382434532-1392034432941-3-exs"

timeStamp="2014-02-10T06:13:52">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>









stopQuantity="0">


documentNumber="8882105174965" fareBasis="HLEX1" meal="LD"/>


documentNumber="8882105174966" fareBasis="LLEX1/CH25" meal="LD"/>













stopQuantity="0">


documentNumber="8882105174965" fareBasis="ALPRT" meal="LD"/>





</BookItinerary>





06-30">










1346)4</Message>


</Passenger>

<Passenger documentNumber="8882105174966" firstName="ALICE"

lastName="GLOBETTROTTER" type="C03">


06-30">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">

<PassengerBookingDetails bookingClass="A" cabin="S"






</BookItinerary>





06-30">










1346)4</Message>


</Passenger>




06-30">









1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">







</BookItinerary>





06-30">












1346)4</Message>


</Passenger>




06-30">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">









</BookItinerary>





06-30">










1346)4</Message>


</Passenger>




06-30">









1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>





endDateTime="2014-10-01T12:25:00" endLocation="YYZ"






stopQuantity="0">


documentNumber="8882105174965" fareBasis="LLEX1" meal="LD"/>







marketingFlightNumber="8904" marketingProvider="AC"

marriageGroup="O" operatingProvider="AC"

startDateTime="2014-10-01T15:10:00" startLocation="YYZ"

stopQuantity="0">

<PassengerBookingDetails bookingClass="G" cabin="Y"

documentNumber="8882105174965" fareBasis="G10Q5TP"/>









endDateTime="2014-10-10T08:34:00" endLocation="YYZ"

marketingFlightNumber="8901" marketingProvider="AC"

marriageGroup="O" operatingProvider="AC"


stopQuantity="0">











startDateTime="2014-10-10T14:00:00" startLocation="YYZ"

stopQuantity="0">


documentNumber="8882105174965" fareBasis="LLEX1" meal="LD"/>





</BookItinerary>





02-11">












1346)4</Message>


</Passenger>




02-11">









1346)4</Message>


</Passenger>











</Solution>


4.3.15 Payment Currency Code Override

This qualifier allows returning the cost of the exchange itinerary options in alternate payment currency.


• If the exchange results in additional collection to be paid by the passenger, the exchange cost will be

returned in the requested currency.

• If the exchange results in a refund or it is an even exchange, the difference will be returned in the

equivalent currency of the exchanged ticket.

For more information, see “Exchange Cost Breakdown per Each Passenger for Returned Itinerary,”

306.

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/PriceRequestInformation/@currencyOverride




Scenario: Mr. Globetrotter wants to shop for exchange options for the following ticket. The ticket was

paid in INR (equivalent currency).

MVTZXZ


1 U0 233Y 17OCT F DELSVO HK1 410A 905A /E

2 U0 232Y 24OCT F SVODEL HK1 725P 255A 25OCT J /E

TKT/TIME LIMIT

1.T-09FEB-DEL4EMB

2.TE 8882105176193 GLOBE/J DEL4EMB 0139/09FEB

He is currently still in Delhi where the default payment currency is INR, but he wants to get the exchange

cost information in USD.

Note For an exchange resulting in a refund or an even exchange, the difference is calculated in the

equivalent currency of the exchanged tickets, and only those transactions that result in additional collection are returned in requested override currency. This is in line with how exchanges work today. The following example includes all three types of result: refund, even exchange, and

additional collection.

More information about rules for currencies in which the difference exchange cost breakdown can be returned can be found in “Exchange Cost Breakdown per Each Passenger for Returned

Itinerary,” page 306.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo

xmlns:ns1="http://services.sabre.com/STL/v01">DEL</ns1:Pseudo>

<ns2:Actual

xmlns:ns2="http://services.sabre.com/STL/v01">DEL</ns2:Actual>

<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="MVTZXZ"



</PassengerWithPNR>






<DateTimeSelection>








<DateTimeSelection>






<TravelPreferences>







<Header


02-26T05:15:00">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo xmlns:ns1="http://services.sabre.com/STL/v01">DEL</ns1:Pseudo>

<ns2:Actual xmlns:ns2="http://services.sabre.com/STL/v01">DEL</ns2:Actual>









<BookItinerary>





endDateTime="2014-10-15T12:45:00" endLocation="DXB"

marketingFlightNumber="511" marketingProvider="EK"

marriageGroup="O" operatingProvider="EK"




stopQuantity="0">


documentNumber="8882105176193" fareBasis="UEX4MIN1" meal="M"/>







startDateTime="2014-10-15T15:40:00" startLocation="DXB"

stopQuantity="0">













stopQuantity="0">







marketingFlightNumber="512" marketingProvider="EK"

marriageGroup="O" operatingProvider="EK"


stopQuantity="0">


documentNumber="8882105176193" fareBasis="UEX4MIN1" meal="M"/>



</BookItinerary>




<ResultPriceDifference differenceType="Refund" lastDayToTicket="2014-10-

09">

<FareDifference currencyCode="INR" decimalPlace="0">330</FareDifference>

<TaxDifference currencyCode="INR" decimalPlace="0">-6488</TaxDifference>

<SubtotalDifference currencyCode="INR" decimalPlace="0">-


<GrandTotalDifference currencyCode="INR" decimalPlace="0">-


<Message type="Advisory">LAST DATE TO PURCHASE 09OCT14 -

1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Refund" lastDayToTicket="2014-10-09">




<TaxDifference currencyCode="INR" decimalPlace="0">-6488</TaxDifference>

<SubtotalDifference currencyCode="INR" decimalPlace="0">-


<GrandTotalDifference currencyCode="INR" decimalPlace="0">-



</Solution>



<BookItinerary>









stopQuantity="0">

<PassengerBookingDetails bookingClass="Z" cabin="C"

documentNumber="8882105176193" fareBasis="ZBR" meal="D"/>











stopQuantity="0">


documentNumber="8882105176193" fareBasis="CNRT" meal="D"/>



</BookItinerary>






<TaxDifference currencyCode="INR" decimalPlace="0">0</TaxDifference>

<SubtotalDifference currencyCode="INR"


<GrandTotalDifference currencyCode="INR"



1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Even" lastDayToTicket="2014-07-14">


<TaxDifference currencyCode="INR" decimalPlace="0">0</TaxDifference>

<SubtotalDifference currencyCode="INR"




<GrandTotalDifference currencyCode="INR"



</Solution>



<BookItinerary>









stopQuantity="0">

<PassengerBookingDetails bookingClass="T" cabin="Y"

documentNumber="8882105176193" fareBasis="T2LRTGF4" meal="L"/>








stopQuantity="0">













stopQuantity="0">










stopQuantity="0">


documentNumber="8882105176193" fareBasis="T2LRTGF4" meal="D"/>



</BookItinerary>







08-31">

<FareDifference currencyCode="USD"


<TaxDifference currencyCode="USD"


<SubtotalDifference currencyCode="USD"


<GrandTotalDifference currencyCode="USD"


<Message type="Advisory">LAST DATE TO PURCHASE 31AUG14 -

1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="AddCollect" lastDayToTicket="2014-08-

31">

<FareDifference currencyCode="USD" decimalPlace="2">371.00</FareDifference>

<TaxDifference currencyCode="USD" decimalPlace="2">279.90</TaxDifference>






</Solution>



<BookItinerary>









stopQuantity="0">










stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





08-31">









<Message type="Advisory">LAST DATE TO PURCHASE 31AUG14 -

1346)4</Message>


</Passenger>



31">








</Solution>



<BookItinerary>









stopQuantity="0">












stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-26">












1346)4</Message>


</Passenger>



26">








</Solution>


4.3.16 Calendar Shopping

The Exchange Shopping schema version 1.1.2 and later supports calendar shopping. This allows extending the search for solutions to include a number of days before and after the requested departure or

arrival date using a new Date Felxibiltiy element.

New search parameters may be included in the request as follows:

• Days: The number of days before and after the requested date to include in the search.

• Minus Days: The number of days before the requested date to include in the search.

• Plus Days: The number of days to search after the requested date to include in the search


• Days cannot be combined with Minus Days or Plus Days.

• Minus Days of Plus Days can be used together or independently.

EXS Xpath:

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DateFlexibility

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DateFlexibility/@days

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DateFlexibility/@minusDays

ExchangeShoppingRQ/OriginDestinationInformation/DateTimeSelection/DateFlexibility/@plusDays

4.3.16.1 Sample Request using Days Parameter

The following is an example of a request to extend the search to two days before and after the departure

date of 2016-08-15.



<ExchangeShoppingRQ Version="1.1.2" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:STL="http://services.sabre.com/STL/v01"> <Header/> <POS> <STL:Actual>WAG</STL:Actual> <STL:Home>WAG</STL:Home> <STL:Sine>SD1</STL:Sine> <STL:DutyCode>4</STL:DutyCode> <STL:Lniata>1B2AF5</STL:Lniata> <StationNumber>02393274</StationNumber> <ShoppingPath requestType="ADVEXC"/> </POS> <TicketingProvider>ZZ</TicketingProvider> <PassengerInformation> <PassengerWithPNR pnrLocator="FVODQV" referenceNumber="1.1" firstName="JAN" lastName="KOWALSKI"> <DocumentNumber>982130715974</DocumentNumber> </PassengerWithPNR> </PassengerInformation> <OriginDestinationInformation shopIndicator="true"> <DateTimeSelection> <DepartureDate>2016-08-15</DepartureDate> <DateFlexibility days="2"/> </DateTimeSelection> <StartLocation>SYD</StartLocation> <EndLocation>LAX</EndLocation> </OriginDestinationInformation> </ExchangeShoppingRQ>

4.3.16.2 Sample Request using MinusDays and PlusDays Parameters

The following is an example of a request to extend the search to one days before and two days after the

departure date of 2016-08-15.

<ExchangeShoppingRQ Version="1.1.2" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:STL="http://services.sabre.com/STL/v01"> <Header/> <POS> <STL:Actual>WAG</STL:Actual> <STL:Home>WAG</STL:Home> <STL:Sine>SD1</STL:Sine> <STL:DutyCode>4</STL:DutyCode> <STL:Lniata>1FB7F6</STL:Lniata> <StationNumber>02393274</StationNumber> <ShoppingPath requestType="ADVEXC"/> </POS> <TicketingProvider>ZZ</TicketingProvider> <PassengerInformation> <PassengerWithPNR pnrLocator="FVODQV" referenceNumber="1.1" firstName="JAN" lastName="KOWALSKI"> <DocumentNumber>982130715974</DocumentNumber> </PassengerWithPNR>



</PassengerInformation> <OriginDestinationInformation shopIndicator="true"> <DateTimeSelection> <DepartureDate>2016-08-15</DepartureDate> <DateFlexibility minusDays="1" plusDays="2"/> </DateTimeSelection> <StartLocation>SYD</StartLocation> <EndLocation>LAX</EndLocation> </OriginDestinationInformation> </ExchangeShoppingRQ>

4.3.17 Frequent Flyer Tier and Customer Value Score

The Exchange Shopping schema version 1.1.2 and later supports shopping with frequent flier tier codes

and customer value scores.

The customer Frequent Flyer Tier together with the Vendor Code may be added in the request for

passenger with or without PNR to allow search using this information.

EXS Xpath for Frequent Flyer information:

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/FrequentFlyer

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/FrequentFlyer/@tier

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/FrequentFlyer/@vendorCode

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/FrequentFlyer

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/FrequentFlyer/@tier

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/FrequentFlyer/@vendorCode

In addition, a new optional Customer Value Score element is added for future use. The Customer Value Score value together with the vendor code may be added in the request to allow searching using this

information.

EXS Xpaths for Customer Value Score:

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/CustomerValueScore

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/CustomerValueScore/@value

ExchangeShoppingRQ/PassengerInformation/PassengerWithPNR/CustomerValueScore/@vendorCode

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/CustomerValueScore

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/CustomerValueScore/@value

ExchangeShoppingRQ/PassengerInformation/PassengerWithoutPNR/CustomerValueScore/@vendorCod

e



4.3.17.1 Sample Request with Frequent Flier Tier

The following is a request for a passenger with PNR and including the passenger’s Frequent Flier Tier

information.

<ExchangeShoppingRQ Version="1.1.2" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:STL="http://services.sabre.com/STL/v01"> <Header/> <POS> <STL:Actual>WAG</STL:Actual> <STL:Home>WAG</STL:Home> <STL:Sine>SD1</STL:Sine> <STL:DutyCode>4</STL:DutyCode> <STL:Lniata>52E2FA</STL:Lniata> <StationNumber>02393274</StationNumber> <ShoppingPath requestType="ADVEXC"/> </POS> <TicketingProvider>ZZ</TicketingProvider> <PassengerInformation> <PassengerWithPNR pnrLocator="FVODQV" referenceNumber="1.1" firstName="JAN" lastName="KOWALSKI"> <DocumentNumber>9822130715974</DocumentNumber> <FrequentFlyer tier="1" vendorCode=" ZZ"/> </PassengerWithPNR> </PassengerInformation> <OriginDestinationInformation shopIndicator="true"> <DateTimeSelection> <DepartureDate>2016-08-15</DepartureDate> </DateTimeSelection> <StartLocation>SYD</StartLocation> <EndLocation>LAX</EndLocation> </OriginDestinationInformation> </ExchangeShoppingRQ>

4.3.17.2 Sample Request with Customer Value Score

The following is a request for a passenger without PNR and including the passenger’s Value Score

information.

<ExchangeShoppingRQ Version="1.1.2" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:STL="http://services.sabre.com/STL/v01"> <Header/> <POS> <STL:Actual>WAG</STL:Actual> <STL:Home>WAG</STL:Home> <STL:Sine>SD1</STL:Sine> <STL:DutyCode>4</STL:DutyCode> <STL:Lniata>4AFDE0</STL:Lniata> <StationNumber>02393274</StationNumber> <ShoppingPath requestType="ADVEXC"/> </POS> <TicketingProvider>ZZ</TicketingProvider>



<PassengerInformation> <PassengerWithoutPNR> <DocumentNumber>9822130715974</DocumentNumber> <CustomerValueScore value="1" vendorCode="ZZ"/> </PassengerWithoutPNR> </PassengerInformation> <OriginDestinationInformation shopIndicator="true"> <DateTimeSelection> <DepartureDate>2016-08-15</DepartureDate> </DateTimeSelection> <StartLocation>SYD</StartLocation> <EndLocation>LAX</EndLocation> </OriginDestinationInformation> </ExchangeShoppingRQ>

4.3.18 Shop by Account Code in conjuction with negotiated fares attribute

The Excahnge Shopping schema version 1.1.3 and later supports shopping with account code along with

new attribute negotiatedFaresonly.

The new attribute will provide the ability at time of shopping, to enable system to request only fares

having the specified account code (for example private, negotiated fares) considered, even if lower fares

are available.


• Applicable per entire request. If the request is for multiple passengers, such as two adults or one adult and one child, and the customer wants to use an Account Code along with negotiatedFareOnly attribute to shop for exchange itineraries, only Account Code specified in the request will be applied for the Exchange Shop search for all passengers in the request and pricing solutions will be returned

matching the account code.

• If no fares are returned by pricing, matching the account code specified in the request, existing error

will be returned REPRICE - NO CORPORATE NEGOTIATED FARES EXIST.

• negotiatedFareOnly attribute is applied to both exchanges or refunds when specified along with

Account Code in EXS request. Pricing will do validations if account code specified in the request is

valid or not and if all rules/conditions are met, returns successful response .

• negotiatedFareOnly attribute should be used in-conjuction with accountCode attribute, else following error will be returned - “negotiatedFaresOnly should be used in combination with AccountCode or

corporateID. Please amend your request and try again”

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/PriceRequestInformation/@negotiatedFaresOnly






<Header messageID="TKTVLC750-10632-1674098208-1540990764708-155307-exs"

timeStamp="2018-10-31T07:59:24">


xmlns:STL="http://services.sabre.com/STL/v01">TKTVLC750-10632-1674098208-



<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo xmlns:ns1="http://services.sabre.com/STL/v01">REV</ns1:Pseudo>

<ns2:Actual xmlns:ns2="http://services.sabre.com/STL/v01">REV</ns2:Actual>

<ns3:Home xmlns:ns3="http://services.sabre.com/STL/v01">REV</ns3:Home>

<ns4:Sine xmlns:ns4="http://services.sabre.com/STL/v01">WBT</ns4:Sine>

<ns5:DutyCode


<ns6:Lniata




</POS>

<Solution pricingSequence="1" sequence="1">

<BookItinerary>

<OriginDestination elapsedTime="685" endLocation="LAX"

segmentQuantity="1" startLocation="SCL">


electronicTicketingIndicator="true" endDateTime="2019-02-21T06:20:00"

endLocation="LAX" marketingFlightNumber="602" marketingProvider="U0" marriageGroup="O"

operatingProvider="U0" segmentNumber="1" startDateTime="2019-02-20T23:55:00"

startLocation="SCL" stopQuantity="0">

<StartLocationDetails GMTOffset="-3"/>

<EndLocationDetails GMTOffset="-8" terminalID="B"/>

<OperatingProviderDetails flightNumber="111"/>

<Equipment type="789"/>



<OriginDestination elapsedTime="645" endLocation="SCL"

segmentQuantity="1" startLocation="LAX">



endLocation="SCL" marketingFlightNumber="603" marketingProvider="U0" marriageGroup="O"


startLocation="LAX" stopQuantity="0"/>


</BookItinerary>

<Fare passengersInDifferentCabins="false" postCalcIndex="1"

requireSplitPNR="false" valid="true">

<ReservationSegmentDetails segmentNumber="1">

<PassengerBookingDetails bookingClass="O" cabin="Y"

documentNumber="8882175864644" fareBasis="OLESLDWB" meal="DB">

<PrivateFareType>*</PrivateFareType>

<FareComponent directionality="FROM" endLocation="LAX"

startLocation="SCL"/>



</PassengerBookingDetails>

</ReservationSegmentDetails>



documentNumber="8882175864644" fareBasis="NHESL6GB" meal="LD">


<FareComponent directionality="TO" endLocation="SCL"

startLocation="LAX"/>




<Passenger documentNumber="8882175864644" firstName="SHOPPING"

lastName="EXCHNAGE" type="ADT">

<ResultPriceDifference differenceType="Refund"


<FareDifference currencyCode="USD" decimalPlace="2">-

487.00</FareDifference>



<SubtotalDifference currencyCode="USD" decimalPlace="2">-

487.00</SubtotalDifference>

<TotalFee currencyCode="USD" decimalPlace="2"

type="CHG">200.00</TotalFee>

<GrandTotalDifference currencyCode="USD" decimalPlace="2">-

287.00</GrandTotalDifference>


1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Refund" lastDayToTicket="2018-10-

31">












</Fare>

</Solution>


<BookItinerary>





endLocation="LAX" marketingFlightNumber="600" marketingProvider="U0" marriageGroup="O"


startLocation="SCL" stopQuantity="1">







<StopLocation GMTOffset="-5" arrivalDateTime="2019-02-

20T10:50:00" departureDateTime="2019-02-20T12:20:00" duration="90" elapsedTime="230"

equipmentType="788" locationCode="LIM"/>



<OriginDestination elapsedTime="645" endLocation="SCL"

segmentQuantity="1" startLocation="LAX">



endLocation="SCL" marketingFlightNumber="603" marketingProvider="U0" marriageGroup="O"


startLocation="LAX" stopQuantity="0"/>


</BookItinerary>

<Fare passengersInDifferentCabins="false" postCalcIndex="2"

requireSplitPNR="false" valid="true">


<PassengerBookingDetails bookingClass="O" cabin="Y"

documentNumber="8882175864644" fareBasis="OLESLDWB" meal="BL">








documentNumber="8882175864644" fareBasis="NHESL6GB" meal="LD">


<FareComponent directionality="TO" endLocation="SCL"

startLocation="LAX"/>




<Passenger documentNumber="8882175864644" firstName="SHOPPING"

lastName="EXCHNAGE" type="ADT">

<ResultPriceDifference differenceType="Refund"













1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Refund" lastDayToTicket="2018-10-

31">














</Fare>

</Solution>

4.3.19 Enable Exchange shopping service for CKIN coupon status

The Exchange Shopping schema version 1.1.4 and onwards allows shopping for coupons that are in

CKIN status.

The new element TicketingRule, StatusCkinToOk, when specified in shopping request, service will consider CKIN coupon as NOT FLOWN, consequently service will return shopping response/solutions as

applicable.

A new warning message is also added in the response, to make POS aware on CKIN coupon that is being

shopped for corresponding ticket number . The new warning message is illustared below:

Ticket [0882190319644] coupon in CKIN status is shopped as OK

The following conditions applies:

• The new qualifier TicketingRule” will accept maximum of 60 characters.

• The CKIN status will be considered as NOT FLOWN when text StatusCkinToOK is specified in

TicketingRule.

• If any invalid text or qualifier left as Blank in TicketingRule qualifier by user, same will be

ignored and CKIN coupon will be treated as FLOWN.

• Currently Shopping results will be returned for coupon which is requested for shopping in O&Ds’ in EXS RQ. Same behavior will be continue to apply, when specifying the new Ticketing

Rule in request, system will consider only those CKIN coupon as OK , which are specified in O&D.

• If more than 1 passenger is being shopped , where coupon status is CKIN on the ticket, all applicable ticket number will be returned in response with max limit of 9 passenger as currently supported by EXS Web services. Sample message when 3 passengers being shopped in a

request, is illustrated below:

Ticket [0882190319644, 0882190319645, 0882190319646] coupon in CKIN

status is shopped as OK

• The status will not be updated from CKIN to OK for the VCR coupons that are being shopped for in EXS RQ as part of this enhancement.



• The service behavior remains same for LFTD coupons that are being shopped in EXS RQ and is treated FLOWN. No changes have been done as part of this enhancmnet for LFTD/USED status.

• No changes has been done in AER flown as part of this enhancement. Passenger should be offloaded from the segment that is in CKIN status before proceding with AER, if he wishes to opt for solution that is being returned by EXS RQ for CKIN sgements.

• If CKIN coupon is specified in O&D even though with shopIndicator as false and new TicketingRule is specified in EXS RQ, service still sets status of CKIN coupon as NotFlown. Service will return the warning message, and booking code may be changed to a different one in which case the offload of passenger needs to take place for that option when selected to go through Exchange (AER).

• If CKIN coupon is not specified in O&D in EXS RQ, and new TicketingRule is specified in EXS RQ, service will consider status of CKIN coupon as FLOWN only and solutions will be returned by service, in such cases, as it does today with previous version of EXS service.

4.3.19.1 Sample RQ and RS

An example is illustrated below:

Passenger is travelling from Santiago to Lima. He has done web -check-in. He wishes to shop for SCL-LIM. Agent using exchange shopping service and selects new qualifier Ticketing Rule ‘StatusCkinToOK’ and system considers CKIN status of coupon as NOT FLOWN and service will return solutions as

applicable for requested O&D.

*TR2‡E«


TKT-0882190319197 ISSUED-11MAR19 CTY-SCLJE STA-12345678

AGNT-HDQAXX PNR- ZZTCMB/11MAR19 CTRY-CL

OAC- U0 SCL JE 0000110 CRS -U0 SCL

NAME-HANIF/MOHAMMED

TTL NBR OF CPNS- 1

CPN A/L FLT CLS DATE BRDOFF TIME PNR BAG STATUS

1 U0 800 Y 20MAR19 SCLLIM 900A OK 2PC CKIN

F/B-YLESFZ0B

FARE CALC SCL U0 LIM1227.00NUC1227.00END ROE1.00

FCMI-0 TICKETED PSGR TYPE-ADT PRICED PSGR TYPE-ADT FCPI-0

BASE FARE USD 1227.00

EQUIV PAID CLP 813501

TFC TOTAL CLP 27183

TICKET TOTAL CLP 840684

FEE TOTAL CLP 0

GRAND TOTAL CLP 840684



TAXES/FEES/CARRIER-IMPOSED CHARGES-TFC

CLP 17238 ZQ CLP 9945 DY

Sample RQ:

<ExchangeShoppingRQ

Version="1.1.4"


<Header/>

<POS>

<ns1:Pseudo

xmlns:ns1="http://services.sabre.com/STL/v01">TGQ</ns1:Pseudo>

<ns2:Actual

xmlns:ns2="http://services.sabre.com/STL/v01">TGQ</ns2:Actual>

<ns3:Home

xmlns:ns3="http://services.sabre.com/STL/v01">TGQ</ns3:Home>

<ns4:Sine

xmlns:ns4="http://services.sabre.com/STL/v01">WBT</ns4:Sine>

<ns5:DutyCode


<ns6:Lniata




<TicketingRule>StatusCkinToOk</TicketingRule>

</POS>








<DateTimeSelection>



<StartLocation>SCL</StartLocation>

<EndLocation>LAX</EndLocation>


<TravelPreferences>

<PriceRequestInformation

accountCode="ALL25" negotiatedFaresOnly="false"/>



</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Sample RS:

<ExchangeShoppingRS Version="1.1.4" solutions="5" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0">


timeStamp="2019-05-27T07:54:24">





<STL:Success>





</STL:Success>

<STL:Warning status="Complete" type="Validation">




<STL:ErrorMessage>Ticket [0882100350803] coupon in CKIN status is

shopped as OK</STL:ErrorMessage>

<STL:ShortText>TicketingRule StatusCkinToOk

Warning</STL:ShortText>


</STL:Warning>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo xmlns:ns1="http://services.sabre.com/STL/v01">TGQ</ns1:Pseudo>

<ns2:Actual xmlns:ns2="http://services.sabre.com/STL/v01">TGQ</ns2:Actual>

<ns3:Home xmlns:ns3="http://services.sabre.com/STL/v01">TGQ</ns3:Home>

<ns4:Sine xmlns:ns4="http://services.sabre.com/STL/v01">WBT</ns4:Sine>

<ns5:DutyCode


<ns6:Lniata




<TicketingRule>StatusCkinToOk</TicketingRule>

</POS>


<BookItinerary>





endLocation="LIM" marketingFlightNumber="2370" marketingProvider="U0"

marriageGroup="O" operatingProvider="U0" segmentNumber="1" startDateTime="2019-06-

20T04:27:00" startLocation="SCL" stopQuantity="0">


<EndLocationDetails GMTOffset="-5"/>

<OperatingProviderDetails companyShortName="WORLDWIDE AIR"

flightNumber="2370"/>





endLocation="LAX" marketingFlightNumber="600" marketingProvider="LA" marriageGroup="I"


startLocation="LIM" stopQuantity="0">







</BookItinerary>

<Fare mixedBrands="false" passengersInDifferentCabins="false"

postCalcIndex="1" requireSplitPNR="false" valid="true">



documentNumber="0882100350803" fareBasis="YLESFZ0B" meal="B">









documentNumber="0882100350803" fareBasis="YLESFZ0B" meal="LD"/>



<Passenger documentNumber="0882100350803" firstName="NAME"

lastName="TEST" type="ADT">

<ResultPriceDifference differenceType="Even"


<FareDifference currencyCode="BRL"


<TaxDifference currencyCode="BRL"


<SubtotalDifference currencyCode="BRL"


<GrandTotalDifference currencyCode="BRL"



1346)4</Message>


</Passenger>


<TotalPriceDifference differenceType="Even" lastDayToTicket="2019-06-

01">

<FareDifference currencyCode="BRL"


<TaxDifference currencyCode="BRL"


<SubtotalDifference currencyCode="BRL"


<GrandTotalDifference currencyCode="BRL"



</Fare>

</Solution>

4.4 Pricing Parameters Present in Exchange Shop Schema but not

Supported

Government Status pricing qualifiers are currently not supported by Exchange Shop; however, they are

planned to be used in the future after the support for them is implemented in AER. Given that these three

elements can be found in the Exchange Shop schema, they are not available for users at this time.

If a Government Status qualifier is used by the time AER starts supporting it, an error message will be

returned and transaction terminated:

"Unable to process - Government Status qualifier is currently not supported. Please amend your

request and try again".

EXS Xpath:

ExchangeShoppingRQ/TravelPreferences/PriceRequestInformation/GovernmentStatus



5 Exchange Shop Response XML

5.1 Introduction

This section describes business specifics of returned itinerary options in the Exchange Shop response.

The Exchange Shop response (ExchangeShoppingRS) consists of the following attributes and elements.

5.1.1 Response Attributes

Attribute Description Exchange Shop Path

XML version Required in the XML schema. ExchangeShoppingRS/@Version

Number of exchange solutions returned

Required in the XML schema. ExchangeShoppingRS/@solutions

5.1.2 Response Elements


Header Information indicating the result of the service call, orchestration and transaction identifiers, errors, and warnings.

Required in the XML schema.

ExchangeShoppingRS/Header

Point of Sale (POS) Information that is copied from the request upon successful response.

Optional in the XML schema.

ExchangeShoppingRS/POS

Solutions information Detailed information about exchange itinerary options found based on customer’s search criteria.

Optional in the XML schema – it will be populated when at least one exchange itinerary solution is found.

ExchangeShoppingRS/Solution

“Solutions Returned,” page. 302, provides details about some elements in the Exchange Shop response XML that may not be self-explanatory in the XML schema and may require some background information and scenarios when they can appear.

Diagnostic data Used only for internal troubleshooting purposes and will not be populated in the response returned to the customer.

ExchangeShoppingRS/Diagnostic

5



5.2 Solutions Returned

Note This section is not intended to provide information about all elements and attributes in the Exchange Shop response XML, but highlights only some of them that may appear under solution

information.

5.2.1 Solution Attributes

Solutions returned may be marked with the following attributes:

Attribute Description Example Exchange Shop

Path

Exchange Shop response solution sequence number.

Solutions are ordered from lowest to highest total price difference (price for all passengers).

ExchangeShoppingRS/Solution/@sequence

Pricing sequence Pricing sequence number as received from one of the Exchange Shop subsystems (IntelliSell). This attribute is used more for web service troubleshooting purposes.

ExchangeShoppingRS/Solution/@pricingSequence

Required PNR split indicator

Indicator for whether the solution itinerary has different passenger types (PTC) booked in different booking classes, which would require a PNR split to fulfill the exchange transaction.

When the request contains different PTCs, such as two adults (ADT), two youth passengers (YTH), Exchange Shop might return an alternate itinerary solution in different booking classes for each PTC if this will secure best pricing solution.

Solution 1 (this example is only for illustration purposes and does not contain full XML content):

U0 811 20 OCT MEL SYD

U0 800 23 OCT SYD MEL

For ADTs it may be returned in booking class “V” as this will be the best applicable pricing solution for this passenger type:

U0 811 V 20 OCT MEL SYD

U0 800 V 23 OCT SYD MEL

And for passengers with YTH PTC in Q class as this class will offer best price for this PTC:

U0 811 Q 20 OCT MEL SYD

U0 800 Q 23 OCT SYD MEL

When different booking classes are returned for a given itinerary solution, the following flag will be set to “true”:

ExchangeShoppingRS/Solution/@requireSplitPNR




Path

For a sample response with this flag set to “true,” see “Example of XML Request and Response with all Itinerary Solutions Booked in the Same Booking Class and Cabin for all Passengers,” page 349.

Same or different PTC evaluation logic:

Evaluation of same or different PTC is done based on the requested PTC. Therefore, in the scenario where there are two passengers, and they are shopped as ADT and YTH PTCs, but for given itinerary, the cheapest solution for both of them is for ADT passenger type, when returning options, Exchange Shop may offer fares in different booking classes for these two passengers since they were requested as different PTCs.

Passengers booked in different cabins indicator

When the request contains different PTCs, such as two adults (ADT), two youth passengers (YTH), Exchange Shop might return an itinerary solution that not only has different booking classes, but also cabins for each PTC if this will secure best pricing solution, such as Business for ADTs and Economy for YTHs.

In the scenario, when the itinerary option returned in the Exchange Shop response has different cabin on at least one segment for different PTCs, the solution will contain the following flag set to “true” indicating this (along with a flag indicating necessity of PNR split to complete exchange transaction):

ExchangeShoppingRS/Solution/@passengersInDifferentCabins




Path

For more information, see:

• “Sample Request and

Response XML with PTC

Override,” page 268.

• “Example of XML

Request and Response

Containing Solution that

Requires PNR Split to

Fulfill Exchange,” page

361 for sample response

containing above flag set

to “true”.

If the itinerary option returned from Shopping has infant type PTCs, such as INF, booked on at least one segment within this itinerary in a cabin that is different than for any other non-infant PTC(s), such as ADT, CNN, option will be discarded from the Exchange Shop response because an infant passenger cannot travel in different cabin than accompanying person.

There will be no validation of accompanying passenger data required by the fare rules for infant type PTCs performed.

Passengers priced in different currencies

Can be sent in the response for multiple passenger requests only. It indicates that exchange cost differences for passengers are calculated in different currencies and, as a result, Total Price Difference element summing the exchange cost for all passengers cannot be built. In such case, individual passenger's prices should be used.

This attribute is omitted in the response if exchange cost is calculated in the same currency for all passengers.

ExchangeShoppingRS/Solution/@passengersPricedInDifferentCurrencies

5.2.2 Solution Elements

There are three elements that the solution consists of:




Information about the itinerary to be booked

Information about the itinerary to be booked.

ExchangeShoppingRS/Solution/BookItinerary

Exchange price difference information per passenger

Exchange price difference information per passenger.

ExchangeShoppingRS/Solution/PassengerPriceInformation

Total exchange price difference information

Total exchange price difference information.

ExchangeShoppingRS/Solution/TotalPriceDifference

Diagnostic For internal use only in troubleshooting purposes.

ExchangeShoppingRS/Diagnostic

In the following sections, you will find the description of some of elements that you may see in each of them that may help you understand the content and business scenarios when they may appear with given

values.

Note These sections should not be used as the source of information about full content of the Solution element in the Exchange Shop response XML. For complete information, see the Exchange Shop

web service XML schema available on the DRC.

5.2.2.1 Information about Itinerary to be Booked

Itinerary information is split into legs. They are returned in the same order and number as requested in the

Exchange Shop request XML.

Note If the new itinerary contains a surface sector (ARNK) between the portions of travel, such as first leg ends in New Your JFK airport (JFK) and second starts in Boston (BOS), information about

the ARNK segment will be omitted in the Exchange Shop response.

If there are any flown ticket coupons (scenarios with partially used tickets) that are not part of new

itinerary calculation (travel itinerary information part of Exchange Shop request XML), they will be taken

into consideration for re-pricing purposes, but will not be added to the Exchange Shop response.

Also, see an example of the Exchange Shop request and response for partially used ticket in “Partially Flown Ticket, One Leg not Shopped, One Leg Shopped Using “Same Connections,” One Leg Shopped

and “Same Connections” not Applied,” page 442.

EXS Xpath:

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination

Under leg data, the following information appears:




Information about each flight segment pertaining to the leg

The reservation segments that must be booked, priced, and fulfilled if the passenger decides to exchange his/her ticket for this itinerary. If the returned solution contains a surface sector, such as due to the airport change (example: from London Heathrow (LHR) to London Gatwick (LGW)), it will be omitted in the segment information.

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment

Information about flight segment referred to each passenger separately

Place where the booking class and fare basis applicable for a given passenger is presented. All passengers are listed in same order as in the PassengerPriceInformation section of the XML response.

The document number is used to uniquely identify the passenger and his/her booking and price information.

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/PassengerBookingDetails

Note As mentioned earlier in this section, if there are some flown coupons in the shopped ticket(s), they will be considered during the re-pricing processing, but information about them (such as flight details and fare) will not be included in the Exchange Shop response. For a sample request and response for partially used ticket, see “Partially Flown Ticket, One Leg not Shopped, One Leg Shopped Using “Same Connections,” One Leg Shopped and “Same Connections” not

Applied,” page 442.

5.2.2.2 Exchange Cost Breakdown per Each Passenger for Returned Itinerary

Passengers (up to nine) may be in a different order than listed in the Exchange Shop request.

Each passenger is identified by following information:


Ticket number Ticket number. ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/@documentNumber




Passenger Type Code Code with which the itinerary was eventually priced. It can be different than the requested PTC.

Example: The passenger requested Exchange Shop to return alternate solutions using the “Override Passenger Type Code” pricing qualifier and set it to YTH. However, for a given itinerary, the system identified either of the following:

• No fares are available for

YTH.

• Lowest applicable fare is for

regular adult (ADT)

passenger while YTH fare

would be more expensive, or

would not meet the

exchanged ticket fare

conditions.

and returned a fare for ADT. In this case, ADT would be populated as passenger type in the response for this itinerary.

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/@type

Passenger’s first and last name The following applies:

• For requests with active

PNR, the name is the same

as passed in Exchange Shop

request.

• For requests without active

PNR, the name passed in the

response is taken from

exchanged ticket.

• ExchangeShoppingRS/Solution/

PassengerPriceInformation/Pass

enger/@firstName



enger/@lastName

Age (optional) ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/@age

Exchange price difference information per passenger

Detailed information about the cost of exchange to a given itinerary per each passenger.

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/ResultPriceDifference



Some of the attributes that are (or can be) added, depending on the scenario, are:


Exchange result Where possible, options are:

• Additional collection

(AddCollect) – indicates the

passenger needs to pay

some additional amount to

fulfill this itinerary solution.

• Even exchange (Even) –

indicates there is no

additional cost to fulfill this

itinerary solution.

• Refund – indicates there is a

refund due to the passenger

that will be returned when

fulfilling this itinerary solution.

Exchange result is required in XML schema.

Note For scenarios where all three types of result are returned, see “Sample Request and Response,” page 278.

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/ResultPriceDifference/@differenceType

Note In the scenario where there is a payment currency change, currency in which the exchange price

difference is returned may be different depending on result type:

• ADDITIONAL COLLECTION – default currency of country where Exchange Shop transaction is performed or, if the customer used Payment Currency Code Override pricing

parameter, in override (requested) currency.

• EVEN EXCHANGE or REFUND

For The exchange price difference

The first payment currency change Will be returned in the currency in which the exchanged ticket was paid.

Subsequent exchanges with multiple payment currency changes

Will be returned in the default currency of the country where the Exchange Shop transaction is performed or, if the customer used the Payment Currency Code Override pricing parameter, in the override (requested) currency.

Following are examples that illustrate these two scenarios.

Example 1 – single payment currency change

1. Original ticket issued on route: JFK-MOW-LON:

Base currency: USD

Issue place: LON, therefore it is paid in GBP (equivalent currency)



2. When shopping for exchange options for this ticket, the passenger is in MOW (default reissue currency RUB) or he is still in LON, but uses the Payment Currency Code

Override pricing parameter to get exchange cost in RUB.

Therefore, in this scenario:

Base currency: unchanged – USD

Reissue currency: RUB

Similarly to how Automated Exchange and Refunds (AER) works today, depending on the

exchange result type, the exchange price difference is calculated in different currencies:

For The passenger gets exchange cost amounts in

ADDITIONAL COLLECTION RUB (default or override reissue currency).

REFUND or EVEN EXCHANGE GBP (currency in which exchanged ticket was paid (equivalent currency in this case)).

Note For scenarios where all three types of results are returned (first payment currency

change scenario), “Sample Request and Response,” page 278.

Example 2 – Multiple payment currency change over subsequent exchanges

1. Original ticket issued on route: JFK-MOW-LON:

Base currency: USD

Issue place: LON; therefore, the ticket was paid in GBP (equivalent

currency).

2. Ticket reissued in ZRH:

Base currency: USD

Reissue place: ZRH; therefore, reissue (equivalent) currency was CHF.

3. When shopping for exchange options for this ticket, the passenger is in MOW (default reissue currency RUB) or he is still in LON, but uses the Payment Currency Code

Override pricing parameter to get exchange cost in RUB.

Therefore in this scenario:

Base currency: Unchanged – USD

Current reissue currency: RUB

Similarly to how Automated Exchange and Refunds (AER) works today, regardless of result

of exchange (ADDITIONAL COLLECTION, REFUND or EVEN EXCHANGE), the

passenger gets the exchange cost amounts in RUB (default or override reissue currency).




Residual amount forfeited flag Returned for these solutions where new fare is cheaper than the old fare, but the residual amount was forfeited per Category 31 rules of the exchanged fare and is not included in the grand total difference amount. If not applicable for given itinerary, then it is omitted in the response.

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/ResultPriceDifference/@residualAmountForfeited

Exchange price difference elements (elements that are part of exchange cost breakdown)

Amount and currency of difference in fare

Amount and currency of difference in fare between exchanged ticket fare and new itinerary fare.



enger/ResultPriceDifference/Far

eDifference/@currencyCode



enger/ResultPriceDifference/Far

eDifference/@decimalPlace

Amount and currency of difference in taxes

Amount and currency of difference in taxes (sum) between exchanged ticket and new itinerary.



enger/ResultPriceDifference/Tax

Difference/@currencyCode



enger/ResultPriceDifference/Tax

Difference/@decimalPlace

Amount and currency of subtotal difference

Amount and currency of subtotal difference (sum of fare difference and taxes difference).



enger/ResultPriceDifference/Sub

totalDifference/@currencyCode



enger/ResultPriceDifference/Sub

totalDifference/@decimalPlace

Non-refundable fare amount Amount representing the non-refundable fare amount, which will be stored in the new ticket once the exchange is fulfilled through AER, so that it can be used in processing of subsequent exchange and/or refund transaction. For more details, see “Non-Refundable Fare Amount”, page 311.



enger/ResultPriceDifference/Non

RefundableAmount/@currencyC

ode



enger/ResultPriceDifference/Non

RefundableAmount/@decimalPl

ace




Total amount, currency and type of change fee

Total amount, currency and type of change fee applied to exchange. Fee total is split by fee type. Supported types are:

• CHG − Change fees

• OTH − Other fees

Note At this time, only Change Fee is used. If the change fee is not applicable, it is omitted in the response.



enger/ResultPriceDifference/Tot

alFee/@currencyCode




alFee/@decimalPlace




alFee/@type

Total amount and currency of tax on change fee

If not applied, it is omitted in the response.




alFeeTax/@currencyCode




alFeeTax/@decimalPlace

Amount and currency of grand total difference

If the exchange results in additional collection for the passenger, this is a positive amount

If the exchange results in a refund due to the passenger and zero amount if this is an even exchange, this is a negative amount.



enger/ResultPriceDifference/Gra

ndTotalDifference/@currencyCo

de



enger/ResultPriceDifference/Gra

ndTotalDifference/@decimalPlac

e

5.2.2.3 Non-Refundable Fare Amount

As part of the recent AER functionality enhancement, the Exchange Shop web service will support non-refundable fare amount processing. The service will pick up the non-refundable fare amount (stored in the ticket) sent in the Exchange Shop request and use it in processing. If applicable, the service will then return the non-refundable fare amount that was determined for a given exchange itinerary option. This amount will represent the non-refundable fare amount, which will be stored in the new ticket after the

exchange is fulfilled through AER, so that it can be used in the processing of a subsequent exchange

and/or refund transaction.

Benefit

With this information present in the Exchange Shop web service response, the user will be aware of the non-refundable amount applied to the new itinerary already at the shopping step. With this fact taken into

account, the user can make an appropriate decision when choosing an itinerary that best fits their needs.



Prerequisite

The setting in the Ticketing Options Table for AER transactions controls returning the non-refundable

amount. It can be sent in Exchange Shop response only if the carrier has this switch turned on.

Rules of Application

• Determination of the non-refundable amount will be based on fare Category 16 (Penalties) filing and will apply strictly by Fare Component. Returned amount will be the sum of all non-refundable fare

components.

• This is the fare amount only and does not include any non-refundable taxes.

• Supporting this feature will not require an Exchange Shop schema version change as the service will

use existing elements. The non-refundable amount, if applicable, will be returned for exchange

itinerary option:

o Individually for each passenger.

o As a sum of all non-refundable amounts within given itinerary option.

Following are the XML paths of the attributes used to return information about non-refundable fare

amount and currency in the Exchange Shop web service response:

o Exchange Cost Breakdown per Each Passenger:

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/ResultPriceDifference/No

nRefundableAmount/@currencyCode

ExchangeShoppingRS/Solution/PassengerPriceInformation/Passenger/ResultPriceDifference/No

nRefundableAmount/@decimalPlace

o Total Price Difference:

ExchangeShoppingRS/Solution/TotalPriceDifference/NonRefundableAmount/@currencyCode

ExchangeShoppingRS/Solution/TotalPriceDifference/NonRefundableAmount/@decimalPlace

Note The sum of all non-refundable fare amounts will be returned only if the non-refundable fare amounts were returned in the same currency for all passengers within the given

itinerary option.

• The non-refundable fare amount is returned in the reissue currency. This will be one of the following:

o Default reissue currency for the country where Exchange Shop transaction is performed.

o Preferred reissue currency if the “Payment Currency Code Override” pricing parameter was

applied by the user. For more details, see “Payment Currency Code Override,” page 277.

Note In either case, depending on type of exchange result (Additional Collection, Even Exchange, or Refund), rules for reissue currency default described in “Exchange Cost

Breakdown per Each Passenger for Returned Itinerary,” page 306, still apply.

• The non-refundable amount will be returned only if applicable for given option and passenger. If not

applicable, the whole element will be omitted in Exchange Shop response

• If the airline opted also for ability to exchange tickets with mixed base currency (please see section “Ability to Change Country of Origin, page 57), the non-refundable fare amount, if applicable, will be

calculated and return in Exchange Shop response in such transactions.



5.2.2.3.1 Non-Refundable Amount Example Scenarios

This section includes example scenarios and Exchange Shop XML requests and responses.

Non-Refundable Amount in Default Payment Currency

Mr. Globetrotter has the below ticket and now wants to shop for exchange options changing the flight dates. The transaction takes place in Moscow and the exchange cost, including non-refundable fare

amount, for all options is returned in default reissue currency – RUB.


8882108148468 NAME-GLOBETROTTER/JOHN MR ♦

TTL NBR OF CPNS- 2 DATE OF ISSUE-17AUG14 PNR-GRAAZQ 17AUG14


1 U0 260 E 09SEP CDGSVO 1145A OK EPX OK

2O U0 2462 N 22SEP SVOCDG 1240P OK NPX OK


326YR TAX 2293XT TOTAL RUB 21275

FARE CALC PAR U0 MOW248.16SU PAR214.17NUC462.33END ROE0.73538

5

FCMI-0

FORM OF PAYMENT

FOP-CASH

DATE OF ISSUE-17AUG14 ISSUED AT-MOWTR MOW EMB



IT-

REMARKS-


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="GRAAZQ"



</PassengerWithPNR>




<DateTimeSelection>







<DateTimeSelection>








<ExchangeShoppingRS



<Header


timeStamp="2014-08-17T12:32:58">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode




<ns6:Lniata



<ShoppingPath


</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination


startLocation="CDG">







stopQuantity="0">


bookingClass="E" cabin="Y" documentNumber="8882108148468"

fareBasis="EPX"

meal="L"/>



<OriginDestination

elapsedTime="235" endLocation="CDG" segmentQuantity="1"








stopQuantity="0">


bookingClass="N" cabin="Y" documentNumber="8882108148468"

fareBasis="NPX"

meal="B"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"




<SubtotalDifference

currencyCode="RUB"


<NonRefundableAmount

currencyCode="RUB"

decimalPlace="0">14960</NonRefundableAmount>

<TotalFee




currencyCode="RUB"


<Message

type="Advisory">LAST DATE TO PURCHASE 24AUG14 - 1346)4</Message>


</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">





fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"




<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="3">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger








<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="4">

<BookItinerary>

<OriginDestination











stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"




<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="5">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination











stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee






currencyCode="RUB"



</Solution>

<Solution



sequence="6">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="LS"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference



currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="7">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"



meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="BS"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference



currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>


Non-Refundable Amount in Override Currency In the scenario requested described above, Mr. Globetrotter requests to get exchange cost for this transaction in USD instead of default payment currency – RUB. Consequently, non –refundable amounts

are also returned in USD in this situation.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>



<PassengerWithPNR




</PassengerWithPNR>




<DateTimeSelection>




<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="B"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"

decimalPlace="2">453.00</NonRefundableAmount>

<TotalFee

currencyCode="USD" decimalPlace="2"





currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination











stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee






currencyCode="USD"



</Solution>

<Solution



sequence="3">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"




fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"




<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"



</Solution>

<Solution



sequence="5">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="L"/>



</BookItinerary>




<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="NPX"

meal="LS"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"




<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"



</Solution>

<Solution



sequence="7">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="EPX"

meal="L"/>



<OriginDestination











stopQuantity="0">



fareBasis="NPX"

meal="BS"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee




currencyCode="USD"


<Message



</Passenger>





<FareDifference

currencyCode="USD"


<TaxDifference

currencyCode="USD"


<SubtotalDifference

currencyCode="USD"



currencyCode="USD"


<TotalFee






currencyCode="USD"



</Solution>


Non-Refundable Amount in Mixed Currency Scenario For the same ticket as mentioned above, Mr. Globetrotter also wants to check the possible exchange options, if he wanted to change the country of origin of his fully unused ticket and, instead of Paris

(CDG), fly from London (LHR) to Moscow (SVO) and back. This causes the base currency to be changed

from originally ticketed EUR to GBP.

Transaction is processed and Exchange Shop web service returns itinerary options and their cost,

including non-refundable amounts where applicable.

He is still in Moscow and does not request to get exchange cost in any preferred currency, so the options

are calculated in default payment currency for this transaction – RUB.

Note For the scenario involving mixed currency exchange, it is also possible to use “Payment Currency

Override” pricing parameter and get exchange cost in the chosen currency.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>



<PassengerWithPNR




</PassengerWithPNR>






<DateTimeSelection>



<StartLocation>LHR</StartLocation>




<DateTimeSelection>








<ExchangeShoppingRS



<Header


timeStamp="2014-08-17T15:50:15">




<STL:Results


<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



<ShoppingPath


</POS>

<Solution



sequence="1">

<BookItinerary>

<OriginDestination




startLocation="LHR">






startDateTime="2014-10-01T13:25:00" startLocation="LHR"

stopQuantity="0">



fareBasis="TPX"

meal="L"/>



<OriginDestination









stopQuantity="0">


bookingClass="U" cabin="Y" documentNumber="8882108148468"

fareBasis="UEX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"




<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="2">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="TPX"

meal="L"/>



<OriginDestination











stopQuantity="0">



fareBasis="UEX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee






currencyCode="RUB"



</Solution>

<Solution



sequence="3">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="TPX"

meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="UEX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference



currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"



</Solution>

<Solution



sequence="4">

<BookItinerary>

<OriginDestination









stopQuantity="0">



fareBasis="TPX"



meal="L"/>



<OriginDestination









stopQuantity="0">



fareBasis="UEX"

meal="L"/>



</BookItinerary>


<Passenger






<FareDifference

currencyCode="RUB"


<TaxDifference

currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee




currencyCode="RUB"


<Message



</Passenger>





<FareDifference

currencyCode="RUB"


<TaxDifference



currencyCode="RUB"


<SubtotalDifference

currencyCode="RUB"



currencyCode="RUB"


<TotalFee






</Solution>


5.2.2.4 Total Price Difference

This part of the Exchange Shop XML response provides information about the total cost of the exchange (total amount to be paid or refunded to the customer) for all passengers, so the customer knows the final

total exchange cost for a given itinerary solution.

One of the attributes of the total price difference is to provide the difference result again, but this time, it

is calculated based on exchange costs for all passengers.

It can have the following values:

• Additional collection (AddCollect) – indicates that passenger needs to pay some additional amount

to fulfill this itinerary solution for all passengers in the request.

• Even exchange (Even) – indicates that there is no additional cost to fulfill this itinerary solution.

• Refund – indicates that there is a refund due to the passenger that will be returned when fulfilling this

itinerary solution for all passengers in proposed fares.

EXS Xpath:

ExchangeShoppingRS/Solution/TotalPriceDifference/@differenceType

Note Total Price Difference element is returned in itinerary solutions where the exchange cost

difference is calculated in the same currency for all passengers. In scenarios of multiple passenger requests where passengers are priced in different currencies, this element is omitted in the

response and the flag is set to “true” for such itinerary solution:

EXS Xpath:


For more information, see the following:

• “Solution Attributes,” page 302.

• “Exchange Cost Breakdown per Each Passenger for Returned Itinerary,” page 306.

• “Example of XML Request and Response Containing Itinerary Solution Priced in Different

Currencies for Different Passengers,” page 383.



This part of the XML response contains the following Total price difference elements representing sums

for all passengers:


Amount and currency of difference in fare

Amount and currency of difference in fare between exchanged tickets fare and new itinerary fares.


TotalPriceDifference/FareDiffere

nce/@currencyCode


TotalPriceDifference/FareDiffere

nce/@decimalPlace

Amount and currency of difference in taxes

Amount and currency of difference in taxes between exchanged tickets and taxes on new itinerary.


TotalPriceDifference/TaxDifferen

ce/@currencyCode


TotalPriceDifference/TaxDifferen

ce/@decimalPlace

Amount and currency of subtotal difference

Amount and currency of subtotal difference (sum of fare differences and taxes differences).


TotalPriceDifference/SubtotalDiff

erence/@currencyCode


TotalPriceDifference/SubtotalDiff

erence/@decimalPlace

Non-refundable fare amount Total amount of all non-refundable fare amounts for all passengers. For more information see section “Non-Refundable Fare Amount”, page 311


TotalPriceDifference/NonRefund

ableAmount/@currencyCode


TotalPriceDifference/NonRefund

ableAmount/@decimalPlace

Total amount, currency and type of change fees

Total amount, currency, and type of change fees applied to exchange for all passengers. Fees totals are split by fee type. Supported types are:

• CHG - Change fees

• OTH - Other fees

Note At this time, only Change Fee (CHG) is used. If a change fee is not applicable, it is omitted in the response.


TotalPriceDifference/TotalFee/@

currencyCode



decimalPlace



type

Total amount and currency of taxes on change fees

Total amount and currency of taxes on change fees if applicable. If not applied, it is omitted in the response.


TotalPriceDifference/TotalFeeTa

x/@currencyCode


TotalPriceDifference/TotalFeeTa

x/@decimalPlace




Amount and currency of grand total difference

Amount and currency of grand total difference.

If the exchange for all passengers results in an additional collection, t is a positive amount.

If the exchange for all passengers results in a refund due to the customer, it is a negative amount.

If the exchange results in an even transaction (no additional collection or refund due), it is a zero amount.


TotalPriceDifference/GrandTotal

Difference/@currencyCode


TotalPriceDifference/GrandTotal

Difference/@decimalPlace

5.2.3 Example of XML Request and Response with all Itinerary Solutions Booked in the Same Booking Class and Cabin for all Passengers


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">4DBDE0</ns6:Lniata>



</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="PAHQNA"



</PassengerWithPNR>

<PassengerWithPNR

firstName="JANE" lastName="GLOBETROTTER" pnrLocator="PAHQNA"



</PassengerWithPNR>

<PassengerWithPNR

firstName="ALICE" lastName="GLOBETROTTER" pnrLocator="PAHQNA"





</PassengerWithPNR>



<DateTimeSelection>











timeStamp="2014-01-28T09:07:01">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>






<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">4DBDE0</ns6:Lniata>



</POS>



<BookItinerary>









stopQuantity="0">









</BookItinerary>














1346)4</Message>


</Passenger>

<Passenger documentNumber="8882104269422" firstName="JANE"










1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">









</BookItinerary>












1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>












</Solution>



<BookItinerary>









stopQuantity="0">









</BookItinerary>












1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>













1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">









</BookItinerary>












1346)4</Message>


</Passenger>













1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">









</BookItinerary>














1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>











1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">
















stopQuantity="0">









</BookItinerary>





04-19">









1346)4</Message>


</Passenger>




04-19">









1346)4</Message>


</Passenger>




04-19">











1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">














stopQuantity="0">









</BookItinerary>





04-19">











1346)4</Message>


</Passenger>




04-19">









1346)4</Message>


</Passenger>




04-19">









1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">














stopQuantity="0">









</BookItinerary>





04-19">









1346)4</Message>


</Passenger>




04-19">









1346)4</Message>


</Passenger>






04-19">









1346)4</Message>


</Passenger>










</Solution>


5.2.4 Example of XML Request and Response Containing Solution that Requires PNR Split to Fulfill Exchange

The following example contains itinerary solutions (1 through 12) where passengers are booked in different booking classes and, at the same time, they also have the flag indicating that they are booked in different cabins. Solution 13 has the passengers booked in the same booking classes and cabins on all

segments.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata

xmlns:ns6="http://services.sabre.com/STL/v01">4DBDCB</ns6:Lniata>



</POS>






</STL:Success>

</STL:Results>

</Header>

<POS>






<ns6:Lniata xmlns:ns6="http://services.sabre.com/STL/v01">4DBDCB</ns6:Lniata>





<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">









</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>



firstName="JOHNR" lastName=“GLOBETROTTER” type="ADT">


04-16">








1346)4</Message>


</Passenger>


firstName="ELIZABTEH" lastName="GLOBETROTTER" type="CNN">


02-09">










1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>






02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>






02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>




</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">

















stopQuantity="0">







</BookItinerary>





04-16">








1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>





<BookItinerary>









stopQuantity="0">















stopQuantity="0">















stopQuantity="0">







</BookItinerary>





04-16">










1346)4</Message>


</Passenger>




02-09">








1346)4</Message>


</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105167857" fareBasis="BRTRF" meal="B"/>


documentNumber="8882105167858" fareBasis="BRTRF/CH50" meal="B"/>











stopQuantity="0">


documentNumber="8882105167857" fareBasis="YRT"/>




documentNumber="8882105167858" fareBasis="YRT/CH50"/>








stopQuantity="0">


documentNumber="8882105167857" fareBasis="BRTRF" meal="L"/>


documentNumber="8882105167858" fareBasis="BRTRF/CH50" meal="L"/>











stopQuantity="0">




documentNumber="8882105167858" fareBasis="BOWRF/CH50" meal="L"/>



</BookItinerary>





04-17">









1346)4</Message>


</Passenger>




04-17">











1346)4</Message>


</Passenger>










</Solution>


5.2.5 Example of XML Request and Response Containing Itinerary Solution Priced in Different Currencies for Different Passengers

Scenario: Mr. Globetrotter and his daughter Alice have the following tickets for a flight from Frankfurt

(FRA) to London (LCY):

1.1GLOBETROTTER/JOHN MR 2.1GLOBETROTTER/ALICE MS

1 XX 926B 02J L W FRALCY HK2 645A 710A /E

TKT/TIME LIMIT

1.T-06MAR-PAR4EMB

4.TE 8882105205967 GLOBE/J PAR4EMB 1501/06MAR

5.TE 8882105205968 GLOBE/A PAR4EMB 1501/06MAR

He bought the tickets in Paris (France), so they were paid in EUR:


8882105205967 NAME-GLOBETROTTER/JOHN MR

TTL NBR OF CPNS- 1 DATE OF ISSUE-06MAR14 PNR-NIGOXX 06MAR14


1 XX 926 B 02JUL FRALCY 645A OK BFF59OW OK

FARE EUR 442.00 TAX 43.00YQ TAX 6.68DE TAX 35.03XT

TOTAL EUR 526.71

FARE CALC FRA XX LON603.94BFF59OW NUC603.94END ROE0.731857

FCMI-0

FORM OF PAYMENT

FOP-CASH

DATE OF ISSUE-06MAR14 ISSUED AT-PARTO PAR EMB



FL/CNX/CHG RESTRICTED/CHECK FARE NOTE




8882105205968 NAME-GLOBETROTTER/ALICE MS

TTL NBR OF CPNS- 1 DATE OF ISSUE-06MAR14 PNR-NIGOXX 06MAR14


1 XX 926 B 02JUL FRALCY 645A OK BFF59OW OK ♦

FARE EUR 442.00 TAX 43.00YQ TAX 6.68DE TAX 35.03XT

TOTAL EUR 526.71

FARE CALC FRA XX LON603.94BFF59OW NUC603.94END ROE0.731857

FCMI-0

FORM OF PAYMENT

FOP-CASH

DATE OF ISSUE-06MAR14 ISSUED AT-PARTO PAR EMB



FL/CNX/CHG RESTRICTED/CHECK FARE NOTE

When in Moscow (Russia), where default payment is RUB, he checks exchange options for:

• Travel date: 9 JUL

• Destination city: Prague (PRG)

• Cabin: Business

This is the scenario involving a single (first) payment currency change. For more information about payment currency changes and rules applied to the currency in which exchange cost is returned, see

“Exchange Cost Breakdown per Each Passenger for Returned Itinerary,” page 306.

Result: Itinerary solutions 7 and 8 resulted in additional collection for Mr. John Globetrotter and a refund for his daughter Alice. This caused exchange cost for these itinerary options to be returned in different currencies (respectively, in RUB and EUR) for these passengers. To inform about this situation and the fact that it was impossible to calculate Total Price Difference for these solutions (this element is not sent

in such cases), Exchange Shop sent the following flag set to “true” for these two itinerary solutions:

EXS Xpath:


Note Such solutions are returned at the bottom of the Exchange Shop response.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home




<ns4:Sine


<ns5:DutyCode


<ns6:Lniata



</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="NIGOXX"



</PassengerWithPNR>

<PassengerWithPNR

firstName="ALICE" lastName="GLOBETROTTER" pnrLocator="NIGOXX"



<PassengerTypeOverride>CNN</PassengerTypeOverride>

</PassengerWithPNR>



<DateTimeSelection>



<StartLocation>FRA</StartLocation>

<EndLocation>PRG</EndLocation>








<Header


03-06T08:22:36">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>










</POS>



<BookItinerary>

<OriginDestination elapsedTime="630" endLocation="PRG"






marriageGroup="O" operatingProvider="LO"


stopQuantity="0">


documentNumber="8882105205967" fareBasis="ZLOOW03" meal="R"/>


documentNumber="8882105205968" fareBasis="ZLOOW03CH" meal="R"/>




endDateTime="2014-07-09T19:45:00" endLocation="PRG"


marriageGroup="I" operatingProvider="LO"


stopQuantity="0">


documentNumber="8882105205967" fareBasis="ZLOOW03" meal="R"/>


documentNumber="8882105205968" fareBasis="ZLOOW03CH" meal="R"/>



</BookItinerary>




<ResultPriceDifference differenceType="Refund">

<FareDifference currencyCode="EUR" decimalPlace="2">-


<TaxDifference currencyCode="EUR" decimalPlace="2">7.27</TaxDifference>

<SubtotalDifference currencyCode="EUR" decimalPlace="2">-


<GrandTotalDifference currencyCode="EUR" decimalPlace="2">-



</Passenger>


lastName="GLOBETROTTER" type="CNN">










</Passenger>




<TotalPriceDifference differenceType="Refund">

<FareDifference currencyCode="EUR" decimalPlace="2">-171.00</FareDifference>







</Solution>



<BookItinerary>





endDateTime="2014-07-09T11:10:00" endLocation="LJU"

marketingFlightNumber="117" marketingProvider="JP"

marriageGroup="O" operatingProvider="JP"


stopQuantity="0">


documentNumber="8882105205967" fareBasis="DPLUSF" meal="B"/>


documentNumber="8882105205968" fareBasis="DPLUSFCH" meal="B"/>





marketingFlightNumber="568" marketingProvider="JP"

marriageGroup="O" operatingProvider="JP"

startDateTime="2014-07-09T18:00:00" startLocation="LJU"

stopQuantity="0">


documentNumber="8882105205967" fareBasis="ZCLUB"/>


documentNumber="8882105205968" fareBasis="ZCLUBCH"/>



</BookItinerary>





07-02">









1346)4</Message>


</Passenger>






07-02">









1346)4</Message>


</Passenger>



02">








</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105205967" fareBasis="JFF73OW" meal="S"/>


documentNumber="8882105205968" fareBasis="JFF73OW/CH25" meal="S"/>



</BookItinerary>













</Passenger>














</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">







</BookItinerary>













</Passenger>














</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










marriageGroup="I" operatingProvider="CL"


stopQuantity="0">







</BookItinerary>















</Passenger>












</Passenger>










</Solution>



<BookItinerary>









stopQuantity="0">










marriageGroup="I" operatingProvider="CL"


stopQuantity="0">







</BookItinerary>















</Passenger>












</Passenger>










</Solution>

<Solution passengersInDifferentCabins="false"

passengersPricedInDifferentCurrencies="true" pricingSequence="2"


<BookItinerary>









stopQuantity="0">


documentNumber="8882105205967" fareBasis="DLOOW03"/>


documentNumber="8882105205968" fareBasis="DLOOW03CH"/>








stopQuantity="0">




documentNumber="8882105205967" fareBasis="DLOOW03" meal="R"/>


documentNumber="8882105205968" fareBasis="DLOOW03CH" meal="R"/>



</BookItinerary>













</Passenger>












</Passenger>


</Solution>

<Solution passengersInDifferentCabins="false"

passengersPricedInDifferentCurrencies="true" pricingSequence="3"


<BookItinerary>









stopQuantity="0">


documentNumber="8882105205967" fareBasis="DLOOW03"/>


documentNumber="8882105205968" fareBasis="DLOOW03CH"/>








stopQuantity="0">




documentNumber="8882105205967" fareBasis="DLOOW03" meal="R"/>


documentNumber="8882105205968" fareBasis="DLOOW03CH" meal="R"/>



</BookItinerary>













</Passenger>












</Passenger>


</Solution>


5.3 Enhanced Shopping Response

From schema version 1.1.2 and later additional information, when available, will be returned in the

response. The following is a list of the data elements and attributes will be returned when present:

EXS Xpath for data per passenger fare:

ExchangeShoppingRS/Solution/Fare/ReservationSegmentDetails/PassengerBookingDetails/PrivateFareT

ype - new optional element

ExchangeShoppingRS/Solution/Fare/ReservationSegmentDetails/PassengerBookingDetails/FareCompon

ent - new optional element


ent/@startLocation - new optional attribute




ent/@endLocation - new optional attribute


ent/@directionality - new optional attribute

EXS Xpath of data per passenger:

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StartLocationDetai

ls - new optional element


ls/@terminalID - new optional attribute


ls/@GMTOffset - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/EndLocationDetail

s - new optional element


s/@terminalID - new optional attribute


s/@GMTOffset - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/OperatingProvider

Details - new optional element


Details/@flightNumber - new optional attribute


Details/@companyShortName - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Equipment - new

optional element

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Equipment/@type -

new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Equipment/@chan

geOfGauge - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/DisclosureProvide

r - new optional element

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation - new

optional element

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@loc

ationCode - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@arr

ivalDateTime - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@de

partureDateTime - new optional attribute



ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@ela

psedTime - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@du

ration - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@G

MTOffset - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/StopLocation/@eq

uipmentType - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/OnTimePerforman

ce - new optional element


ce/@level - new optional attribute


ce/@percentage - new optional attribute

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Message - new

optional element

ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Message/@text -


ExchangeShoppingRS/Solution/BookItinerary/OriginDestination/ReservationSegment/Message/@type -


5.3.1 Sample Request with Enhanced Response

The following is an example of a request with a response containing several of the new elements and

attributes

Request:

<ExchangeShoppingRQ Version="1.1.2" xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:STL="http://services.sabre.com/STL/v01"> <Header/> <POS> <STL:Actual>WAG</STL:Actual> <STL:Home>WAG</STL:Home> <STL:Sine>SD1</STL:Sine> <STL:DutyCode>4</STL:DutyCode> <STL:Lniata>52E1FE</STL:Lniata> <StationNumber>02393274</StationNumber> <ShoppingPath requestType="ADVEXC"/> </POS> <TicketingProvider>ZZ</TicketingProvider> <PassengerInformation>



<PassengerWithPNR pnrLocator="FVODQV" referenceNumber="1.1" firstName="JAN" lastName="KOWALSKI"> <DocumentNumber>7952130715974</DocumentNumber> <CustomerValueScore value="1" vendorCode="ZZ"/> </PassengerWithPNR> </PassengerInformation> <OriginDestinationInformation shopIndicator="true"> <DateTimeSelection> <DepartureDate>2016-08-15</DepartureDate> </DateTimeSelection> <StartLocation>SYD</StartLocation> <EndLocation>LAX</EndLocation> </OriginDestinationInformation> </ExchangeShoppingRQ>

Response:

The new items in response are highlighted below

<ExchangeShoppingRS xmlns="http://www.sabre.com/ns/Ticketing/exchangeshop/1.0" Version="1.1.2" solutions="5"> <Header messageID="TKTHLI701-1189-1358487543-1469220680071-88172-exs" timeStamp="2016-07-22T15:51:20"> <STL:OrchestrationID xmlns:STL="http://services.sabre.com/STL/v01" seq="2">TKTHLI701-1189-1358487543-1469220680071-88172-exs</STL:OrchestrationID> <STL:Results xmlns:STL="http://services.sabre.com/STL/v01"> <STL:Success> <STL:System>TKT-WS</STL:System> <STL:Source>EXS</STL:Source> </STL:Success> </STL:Results> </Header> <POS> <STL:Actual xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">WAG</STL:Actual> <STL:Home xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">WAG</STL:Home> <STL:Sine xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">SD1</STL:Sine> <STL:DutyCode xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">4</STL:DutyCode> <STL:Lniata xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">52E1FE</STL:Lniata> <StationNumber xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">02393274</StationNumber> <ShoppingPath xmlns:STL="http://services.sabre.com/STL/v01" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" requestType="ADVEXC"/> </POS> <Solution pricingSequence="1" sequence="1"> <BookItinerary> <OriginDestination elapsedTime="900" endLocation="LAX" segmentQuantity="1" startLocation="SYD">



<ReservationSegment elapsedTime="900" electronicTicketingIndicator="true" endDateTime="2016-08-15T07:00:00" endLocation="LAX" marketingFlightNumber="1" marketingProvider="ZZ" marriageGroup="O" operatingProvider="ZZ" segmentNumber="1" startDateTime="2016-08-15T09:00:00" startLocation="SYD" stopQuantity="0"> <StartLocationDetails GMTOffset="10" terminalID="1"/> <EndLocationDetails GMTOffset="-7" terminalID="B"/> <OperatingProviderDetails companyShortName=”SEAGULL EAST INTL" flightNumber="1"/> <Equipment type="77W"/> </ReservationSegment> </OriginDestination> </BookItinerary> <Fare passengersInDifferentCabins="false" postCalcIndex="1" requireSplitPNR="false" valid="true"> <ReservationSegmentDetails segmentNumber="1"> <PassengerBookingDetails bookingClass="Y" cabin="Y" documentNumber="7952130715974" fareBasis="YLX0OVUR" meal="BD"> <FareComponent directionality="FROM" endLocation="LAX" startLocation="SYD"/> </PassengerBookingDetails> </ReservationSegmentDetails> <PassengerPriceInformation> <Passenger documentNumber="9822130715974" firstName="JAN" lastName="KOWALSKI" type="ADT"> <ResultPriceDifference differenceType="Even" lastDayToTicket="2016-07-26"> <FareDifference currencyCode="NZD" decimalPlace="2">0.00</FareDifference> <TaxDifference currencyCode="NZD" decimalPlace="2">0.00</TaxDifference> <SubtotalDifference currencyCode="NZD" decimalPlace="2">0.00</SubtotalDifference> <GrandTotalDifference currencyCode="NZD" decimalPlace="2">0.00</GrandTotalDifference> <Message type="Advisory">LAST DATE TO PURCHASE 26JUL16 - 1346)4</Message> </ResultPriceDifference> </Passenger> </PassengerPriceInformation> <TotalPriceDifference differenceType="Even" lastDayToTicket="2016-07-26"> <FareDifference currencyCode="NZD" decimalPlace="2">0.00</FareDifference> <TaxDifference currencyCode="NZD" decimalPlace="2">0.00</TaxDifference> <SubtotalDifference currencyCode="NZD" decimalPlace="2">0.00</SubtotalDifference> <GrandTotalDifference currencyCode="NZD" decimalPlace="2">0.00</GrandTotalDifference> </TotalPriceDifference> </Fare> </Solution> <Solution pricingSequence="2" sequence="2"> <BookItinerary> <OriginDestination elapsedTime="825" endLocation="LAX" segmentQuantity="1" startLocation="SYD">



<ReservationSegment elapsedTime="825" electronicTicketingIndicator="true" endDateTime="2016-08-15T06:45:00" endLocation="LAX" marketingFlightNumber="6552" marketingProvider="ZZ" marriageGroup="O" operatingProvider="DL" segmentNumber="1" startDateTime="2016-08-15T10:00:00" startLocation="SYD" stopQuantity="0"> <StartLocationDetails GMTOffset="10" terminalID="1"/> <EndLocationDetails GMTOffset="-7" terminalID="B"/> <OperatingProviderDetails flightNumber="40"/> <Equipment type="777"/> <DisclosureProvider>DL</DisclosureProvider> </ReservationSegment> </OriginDestination> </BookItinerary> <Fare passengersInDifferentCabins="false" postCalcIndex="2" requireSplitPNR="false" valid="true"> <ReservationSegmentDetails segmentNumber="1"> <PassengerBookingDetails bookingClass="Y" cabin="Y" documentNumber="7952130715974" fareBasis="YLX0OVUR" meal="D"> <FareComponent directionality="FROM" endLocation="LAX" startLocation="SYD"/> </PassengerBookingDetails> </ReservationSegmentDetails> <PassengerPriceInformation> <Passenger documentNumber="9822130715974" firstName="JAN" lastName="KOWALSKI" type="ADT"> <ResultPriceDifference differenceType="Even" lastDayToTicket="2016-07-26"> <FareDifference currencyCode="NZD" decimalPlace="2">0.00</FareDifference> <TaxDifference currencyCode="NZD" decimalPlace="2">0.00</TaxDifference> <SubtotalDifference currencyCode="NZD" decimalPlace="2">0.00</SubtotalDifference> <GrandTotalDifference currencyCode="NZD" decimalPlace="2">0.00</GrandTotalDifference> <Message type="Advisory">LAST DATE TO PURCHASE 26JUL16 - 1346)4</Message> </ResultPriceDifference> </Passenger> </PassengerPriceInformation> <TotalPriceDifference differenceType="Even" lastDayToTicket="2016-07-26"> <FareDifference currencyCode="NZD" decimalPlace="2">0.00</FareDifference> <TaxDifference currencyCode="NZD" decimalPlace="2">0.00</TaxDifference> <SubtotalDifference currencyCode="NZD" decimalPlace="2">0.00</SubtotalDifference> <GrandTotalDifference currencyCode="NZD" decimalPlace="2">0.00</GrandTotalDifference> </TotalPriceDifference> </Fare> </Solution> </ExchangeShoppingRS>

Exchange Shop Scenarios


6 Exchange Shop Scenarios

6.1 Introduction

The following examples provide sample XML requests and responses for more complex Exchange Shop

transactions including various scenarios presenting the ways in which the web service can be used.

6.2 Fully Un-flown Ticket, One Leg not Shopped, One Leg Shopped

Using “Same Connections,” One Leg Shopped and “Same Connections”

not Applied

Scenario: Mr. Globetrotter bought the tickets for himself and his daughter Alice for the following

itinerary and now, he tries various options to shop for exchange itinerary options.

DKECBR


1 U01129B 02JUL W AERSVO HK2 605A 830A /E

2 U0 100B 10JUL Q*SVOJFK HK2 1015A 1220P /E

3 U04017B 10JUL Q JFKMIA*HK2 430P 757P /E

/OPERATED BY DELTA AIR LINES INC /DL 1373H/

4 U0 111N 18JUL F*MIASVO HK2 500P 1205P 19JUL J /E

5 U01124N 19JUL J SVOAER*HK2 325P 545P /E

TKT/TIME LIMIT

1.T-11FEB-MOW4EMB

2.TE 8882105179555-56 GLOBE/J MOW4EMB 1917/11FEB

3.TE 8882105179557-58 GLOBE/A MOW4EMB 1917/11FEB

6.2.1 Single Passenger, Fully Un-Flown Ticket, Unchanged PNR, One Leg not Shopped, One Leg Shopped using “Same Connections,” One Leg Shopped and

“Same Connections” not Applied

First, he wants to check the exchange options for himself only and wants to shop as follows:

• First leg (AER-SVO) not shopped.

• Second leg (SVO-MIA) shopped with “Use Same Connections” shopping parameter applied; search

by departure date, preferred time and alternate time after departure.

• Third leg (MIA-AER) shopped with the request of SVO as a connection airport and flights in

business class; search by arrival date and time range.

• Also, he wants his Corporate ID (ABC12) to be also applied during search.

6



DKECBR








TKT/TIME LIMIT

1.T-11FEB-MOW4EMB



Here are a few items regarding the response that may be worth mentioning. It contains options that:

• End with AddCollect result for the passenger.

• Have the change fee applied.


<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine


<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR

firstName="JOHN" lastName="GLOBETROTTER" pnrLocator="DKECBR"



</PassengerWithPNR>




<DateTimeSelection>








</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>









stopQuantity="0">


documentNumber="8882105179555" fareBasis="BNRT" meal="B"/>



<OriginDestination elapsedTime="1062" endLocation="MIA"








stopQuantity="0">








marriageGroup="I" operatingProvider="DL"


stopQuantity="0">





<OriginDestination elapsedTime="1005" endLocation="AER"

segmentQuantity="2" startLocation="MIA">









stopQuantity="0">










stopQuantity="0">





</BookItinerary>





03-31">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">













stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





03-31">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">


documentNumber="8882105179555" fareBasis="AHPRT" meal="B"/>











stopQuantity="0">


documentNumber="8882105179555" fareBasis="AHPRT" meal="LD"/>




endDateTime="2014-07-16T03:45:00" endLocation="SJU"

marketingFlightNumber="425" marketingProvider="DL"



stopQuantity="0">




documentNumber="8882105179555" fareBasis="VA14A0VP" meal="D"/>





marketingFlightNumber="1014" marketingProvider="AA"

marriageGroup="O" operatingProvider="AA"

startDateTime="2014-07-16T06:35:00" startLocation="SJU"

stopQuantity="0">


documentNumber="8882105179555" fareBasis="QNE7C0Z1" meal="F"/>











stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-12">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">










stopQuantity="0">










stopQuantity="0">















stopQuantity="0">










stopQuantity="0">





</BookItinerary>





02-12">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">













stopQuantity="0">










stopQuantity="0">


documentNumber="8882105179555" fareBasis="YA2AA" meal="F"/>











stopQuantity="0">










stopQuantity="0">





</BookItinerary>







06-25">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">












stopQuantity="1">


documentNumber="8882105179555" fareBasis="YA0UPAM5" meal="F"/>











stopQuantity="0">










stopQuantity="0">





</BookItinerary>





06-25">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">










stopQuantity="0">













stopQuantity="0">












stopQuantity="0">





</BookItinerary>





06-25">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





06-25">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">










stopQuantity="0">













stopQuantity="0">












stopQuantity="0">





</BookItinerary>





06-25">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">










stopQuantity="0">













stopQuantity="0">










stopQuantity="0">





</BookItinerary>





06-25">












1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">













stopQuantity="0">






endDateTime="2014-07-15T18:35:00" endLocation="ORF"




stopQuantity="0">


documentNumber="8882105179555" fareBasis="KA0UPPM5"/>








marriageGroup="I" operatingProvider="AA"

startDateTime="2014-07-15T19:10:00" startLocation="ORF"

stopQuantity="0">


documentNumber="8882105179555" fareBasis="KA0UPPM5" meal="F"/>











stopQuantity="0">










stopQuantity="0">





</BookItinerary>





06-25">










1346)4</Message>


</Passenger>













</Solution>


6.2.2 Multiple Passengers, Fully Un-Flown Ticket, Unchanged PNR, One Leg not Shopped, One Leg Shopped using “Same Connections,” One Leg Shopped and

“Same Connections” not Applied

Now, it turns out that he will need to rebook the ticket also for his daughter so now he checks for

exchange options for both of them using parameters applied in previous scenario:

• First leg (AER-SVO) not shopped.

• Second leg (SVO-MIA) shopped with “Use Same Connections” shopping parameter applied; search

by departure date, preferred time, and alternate time after departure.

• Third leg (MIA-AER) shopped with the request of SVO as a connection airport and flights in

business class; search by arrival date and time range.

• He wants his Corporate ID (ABC12) to also be applied during search.

Also, he wants to use a PTC override for his daughter and check for options for youth passenger (YTH).

Their original ticketed itinerary is:

DKECBR








TKT/TIME LIMIT

1.T-11FEB-MOW4EMB




<ExchangeShoppingRQ

Version="1.0.0"


<Header/>

<POS>

<ns1:Pseudo


<ns2:Actual


<ns3:Home


<ns4:Sine




<ns5:DutyCode


<ns6:Lniata




</POS>



<PassengerWithPNR




</PassengerWithPNR>

<PassengerWithPNR

firstName="ALICE" lastName="GLOBETROTTER" pnrLocator="DKECBR"



<PassengerTypeOverride>YTH</PassengerTypeOverride>

</PassengerWithPNR>




<DateTimeSelection>





<RelatedSegment










<DateTimeSelection>

<DepartureDateTime




<EndLocation>MIA</EndLocation>

<RelatedSegment


endLocation="JFK" marketingFlightNumber="100"




<RelatedSegment bookingClass="B"



operatingProvider="DL" reservationStatus="HK"


startLocation="JFK"/>






<DateTimeSelection>

<ArrivalDate


timeWindowStart="14:00:00">2014-10-01</ArrivalDate>






<TravelPreferences>







<Header


02-11T10:58:04">





<STL:Success>



</STL:Success>

</STL:Results>

</Header>

<POS>











<BookItinerary>









stopQuantity="0">

















stopQuantity="0">












stopQuantity="0">















stopQuantity="0">


documentNumber="8882105179555" fareBasis="ZBR1" meal="LD"/>










stopQuantity="0">


documentNumber="8882105179555" fareBasis="ZBR1" meal="L"/>





</BookItinerary>







03-31">










1346)4</Message>


</Passenger>




03-31">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">












stopQuantity="0">















stopQuantity="0">












stopQuantity="0">







</BookItinerary>







03-31">










1346)4</Message>


</Passenger>




03-31">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>









stopQuantity="0">

















stopQuantity="0">












stopQuantity="0">












stopQuantity="0">















stopQuantity="0">














stopQuantity="0">







</BookItinerary>





02-12">










1346)4</Message>


</Passenger>




02-12">










1346)4</Message>


</Passenger>











</Solution>



<BookItinerary>











stopQuantity="0">















stopQuantity="0">












stopQuantity="0">












stopQuantity="0">

















stopQuantity="0">












stopQuantity="0">







</BookItinerary>





02-12">










1346)4</Message>


</Passenger>




02-12">










1346)4</Message>


</Passenger>













</Solution>



<BookItinerary>









stopQuantity="0">















stopQuantity="0">












stopQuantity="1">









