User Guide - Sabrefiles.developer.sabre.com/doc/providerdoc/... · Ticketing Document Web Service...

User Guide

Ticketing Document Web Service

Version 1.18

March 01, 2019

Document Edition 1.18

This documentation is the confidential and proprietary intellectual

property of the Sabre Airline Solution® 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 Airline Solutions, the Sabre Airline Solutions logo, Sabre

Holdings, the Sabre Holdings logo, Sabre Travel Network, the

Sabre Travel Network logo, AirCentre, AirCommerce, AirVision,

ASx, MyFares, Qik, Sabre, SabreSonic, Service360 and Virtually

There are trademarks and/or service marks of an affiliate of Sabre

Holdings Corp. All other trademarks, service marks and trade

names are the property of their respective owners.

© 2012 Sabre Inc. All rights reserved. 02_2012

Ticketing Document Web Service Table of Contents 1 March 2019 iii Confidential and Proprietary Sabre Airline Solutions

Document Revision Information

Project Name Ticketing Document Web Service

Prepared by Ewa Młyńska Date Prepared September 7, 2012

Revised by Michał Kułak Date Revised March 12, 2014

Revision Reason Introduced a new Result Type, updated the examples with the newest schema version, added description of getting a real status of interline coupons, added example of a VOU document, described handling of duplicated document numbers

Revision Control No. 1.1

Revised by Louis P. Ott Date Revised June 1, 2014

Revision Reason Renamed document. Updated Table of Contents

Introduced new operation

UpdateTicketingDocumentRQ and RS for xml schema version 3.5.1- section 3.4


Revised by Louis P. Ott Date Revised July 29, 2014

Revision Reason Updated with example of RQ/RS for tour code. Section 3.2.1.3.7


Revised by Louis P. Ott Date Revised Oct. 28, 2014

Revision Reason Updated document with Non-Refundable Fare RQ and RS. Section 3.5


Revised by Louis P. Ott Date Revised Nov. 20, 21014

Revision Reason Updated document with Multiple Forms of Refunds, OB Fees, and Spanish Resident RQ & RS examples. Replaced DRC with Sabre Dev Lab.


Revised by C.Darling Date Revised 5/14/2015

Revision Reason Added 3.9 Canadian Baggage Disclosure Revision Control No. 1.6

Ticketing Document Web Service Table of Contents 1 March 2019 iv Confidential and Proprietary Sabre Airline Solutions

Revised by LP Ott Date Revised 6/4/2015

Revision Reason Added 3.10 Pre-Ticketing Validation Revision Control No. 1.7

Revised by

Varun Aggarwal

Date Revised

9/30/2015

Revision Reason Modified 3.2 to add other DOC types

Added 3.11 TFE Ticket Field Extension

Added 3.12 iEMD CR13 changes

Added 5.3.10 Unsupported Service Version


Revised by Stephanie Bidun

Garry Harvie

Date Revised 12/2/2015

Revision Reason

Added 3.13 Passenger Itinerary Receipt (PIR)

Added 3.2.7 Status of Hosted Validating Carrier Coupons


Revised by

Varun Aggarwal

Date Revised

01/29/2016

Revision Reason Added 3.12.2 Status to track non EMD documents

Added 3.14 VAT for Italy


Revised by

Varun Aggarwal

Garry Harvie

Date Revised

04/04/2016

Revision Reason Added 3.15 Web Mark-up

Added 3.16 Frequent Flyer Tier information

Added 3.17 New Operation – IssueTicketDocument

Added 5.3.11 Credit Card detokenization failure

Added 5.3.12 Multiple payments in a single payment element

Added 5.3.13 Multiple transactions in a single request

Added 3.2.8 Net Tickets and Net Remit Tickets


Revised by

Varun Aggarwal

Date Revised

10/20/2016

Revision Reason Added 3.18 Expansion of length of Remarks element.

Added 3.19 Mark-up any fare-Agency Retailer Project

Added 3.20 GDS Automated Refunds


Revised by

Varun Aggarwal

Date Revised

04/07/2017

Ticketing Document Web Service Table of Contents 1 March 2019 v Confidential and Proprietary Sabre Airline Solutions

Revision Reason Added 3.2.2.1 New VCR search capabilities

Added 3.18 Orchestrated Ticketing functionality

[For Sabre Internal use only]


Revised by

Sujat Jain

Date Revised

11/09/2017

Revision Reason Added 3.3 Search for historical VCR


Revised by

Varun Aggarwal

Date Revised

12/27/2017

Revision Reason Added 3.23 FCMI and FCPI values


Revised by

Varun Aggarwal

Date Revised

03/27/2018

Revision Reason Added 3.14.2 Data Protection Notice


Revised by

Sujat Jain

Date Revised

07/20/2018

Revision Reason Added 3.3 Search for Historical Documents


Revised by

Sujat Jain

Date Revised

03/01/2019

Revision Reason Updated 3.14. PIR

Added 3.24 Involuntary Reroute Information

Added 3.2.4 Additional filter to search EMD

Added 3.2.10 New fields for NDC documents


Ticketing Document Web Service Table of Contents 1 March 2019 vi Confidential and Proprietary Sabre Airline Solutions

Table of Contents

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

Overview................................................................................................................................................. 1 Sabre Dev Studio ................................................................................................................................... 1

2 U n d e r s t a n d i n g T k t D o c W e b S e r v i c e

TktDoc Web Service Description ............................................................................................................ 2

3 F u n c t i o n s o f f e r e d b y T i c k e t i n g D o c u m e n t ( T k t D o c )

Introduction ............................................................................................................................................. 3 Search for document .............................................................................................................................. 3

Result Type .............................................................................................................................. 3 3.2.1.1 Result Types for Airline ............................................................................................... 4 3.2.1.2 Result Types for Travel Agent (Subscriber) ................................................................ 4 3.2.1.3 Examples of Requests and Responses....................................................................... 4

3.2.1.3.1 Example request and response for CustomDetails Result Type with History

and RelatedDocument for Flight Document (TKT) ........................................................ 5 3.2.1.3.2 Example request and response for Details Result Type for Electronic

Voucher (VOU) .............................................................................................................. 8 3.2.1.3.3 Example request and response for Details Result Type for Flight Document

(TKT) ........................................................................................................................... 12 3.2.1.3.4 Example request and response for Abbreviated Result Type for Flight

Document (TKT) .......................................................................................................... 16 3.2.1.3.5 Example request and response for Summary Result Type for Flight

Document (TKT) .......................................................................................................... 17 3.2.1.3.6 Example request and response for Details Result Type for Travel Agent

(Subscriber) ................................................................................................................. 18 3.2.1.3.7 Example request and response for Details Result Type for Flight Document

(TKT) with a tour code ................................................................................................. 21 Possible Search Parameters for Airline .................................................................................. 23

3.2.2.1 Added New VCR Search Capabilities ....................................................................... 24 3.2.2.1.1 Search by VCR Number and Passenger Last Name .................................... 24 3.2.2.1.2 Search by Service Coupon details ............................................................... 33 3.2.2.1.3 Search by Form of Identification ................................................................... 36 3.2.2.1.4 Search by Frequent Flyer Number ............................................................... 37

Possible Search Parameters for Travel Agent (Subscriber) ................................................... 39 Additional Filter for EMD refundability check .......................................................................... 39 Examples of Web Service Calls to Search for Documents ..................................................... 39

Ticketing Document Web Service Table of Contents 1 March 2019 vii Confidential and Proprietary Sabre Airline Solutions

3.2.5.1 Searching by DocumentNumber - Requesting 1 DocumentNumber: ........................ 39 3.2.5.2 Searching by DocumentNumber – Requesting Multiple Documents in One

Transaction. .......................................................................................................................... 46 3.2.5.3 Searching by DocumentNumber and LocalIssueDate ............................................... 46 3.2.5.4 Searching by DocumentNumber and WorkLocation ................................................. 47 3.2.5.5 Searching by DocumentNumber and LocalIssueDate and WorkLocation ................. 47 3.2.5.6 Searching by FrequentFlyer ...................................................................................... 47 3.2.5.7 Searching by DocumentType and FrequentFlyer ...................................................... 47 3.2.5.8 Searching by LastName ............................................................................................ 48 3.2.5.9 Searching by LastName and FirstName.................................................................... 48 3.2.5.10 By LastName and Reservation (PNR locator) ......................................................... 48 3.2.5.11 By LastName and WorkLocation ............................................................................. 49 3.2.5.12 Searching by LastName and LocalIssueDate ......................................................... 49 3.2.5.13 Searching by LastName and LocalIssueDateRange ............................................... 49 3.2.5.14 Searching byDocumentType and LastName ........................................................... 49 3.2.5.15 Searching by DocumentType and LastName and FirstName ................................. 50 3.2.5.16 Searching by DocumentType and LocalIssueDate and WorkLocation .................... 50 3.2.5.17 Searching by LocalIssueDate and WorkLocation .................................................... 50 3.2.5.18 Searching by Reservation ....................................................................................... 51 3.2.5.19 Searching by Reservation and CreateDate ............................................................. 51 3.2.5.20 By Reservation (PNR locator) and WorkLocation ................................................... 51 3.2.5.21 By Reservation (PNR locator) and LocalIssueDate ................................................. 51 3.2.5.22 By Reservation (PNR locator) and LocalIssueDateRange ...................................... 52

A Real Status of Interline Coupons ........................................................................................ 52 Duplicated Document Numbers ............................................................................................. 64 Status of Hosted Validating Carrier Coupons ......................................................................... 69 Net Tickets and Net Remit Tickets ......................................................................................... 79

3.2.10 NDC Documents ................................................................................................................ 80 Search for Historical Document ............................................................................................................ 83

3.3.1 Search Parameters supported for historical .......................................................................... 84 3.3.2 Historical VCR search example for different result types ...................................................... 84

3.3.1.1 Historical VCR Detail Search .................................................................................... 84 3.3.1.2 Historical VCR Summary Search ............................................................................ 105 3.3.1.3 Historical VCR Abbreviated Search ........................................................................ 108 3.3.1.4 Historical VCR Custom Search ............................................................................... 123

Update Service Coupon (Airline only) ................................................................................................. 128 Manual Documents (Airline only) RQ & RS v.3.5.1 ............................................................................ 131 Non-Refundable Fares v3.5.1 (RQ & RS)........................................................................................ 133 Multiple Forms of Refund (MFOR) ...................................................................................................... 142

3.7.1.1 Detail RQ/RS example ............................................................................................ 142 3.7.1.2 Custom Detail RQ/RS example ............................................................................... 149

Airline Ticketing Fees (T and R Types) (Airline path) ......................................................................... 152 Spanish Residents .............................................................................................................................. 159

3.9.1.1 Island Resident Discount RQ/RS example .............................................................. 160

Ticketing Document Web Service Table of Contents 1 March 2019 viii Confidential and Proprietary Sabre Airline Solutions

3.9.1.2 Large Family Discount RQ/RS example .................................................................. 167 3.9.1.3 Large Family and Resident Discount RQ/RS example ............................................ 177

Canadian Baggage Disclosure ......................................................................................................... 186 PQ RQ/RS example ........................................................................................................... 187

Pre-Ticketing Validation .................................................................................................................... 199 Native Sabre ...................................................................................................................... 199 Original Ticket Xml Request (RQ) and Response (RS) ...................................................... 200

Ticket Field Expansion (TFE) ........................................................................................................... 202 Native Sabre ...................................................................................................................... 202 Original Ticket with extended field - XML RQ and RS ........................................................ 203

Interline EMD CR13 Changes (iEMD CR13) .................................................................................... 205 RQ and RS Example .......................................................................................................... 205 Service Coupon Status to track non EMD documents ....................................................... 208 3.13.2.1 RQ and RS example ............................................................................................. 208

Passenger Itinerary Receipt (PIR) .................................................................................................... 215 Search Parameters for PIR document ............................................................................... 216 Result Type ........................................................................................................................ 216 Sample eTicket/EMD PIR................................................................................................... 216 3.14.3.1 PIR RQ/RS for eTKT ............................................................................................. 216 3.14.3.2 PIR RQ/RS for an EMD ......................................................................................... 220 Passenger Notices ............................................................................................................. 225 3.14.4.1 Passenger Notice Translation – Montreal Disclaimer / Data Protection ................ 225 3.14.4.2 Passenger Notice Translation – HAZMAT ............................................................. 226 3.14.4.3 Examples of Passenger Notices in ‘GetTicketingDocumentRQ’ service ............... 227

3.14.4.3.1 Ticket PIR - Example #1 ........................................................................... 227 3.14.4.3.2 Ticket PIR - Example #2 .......................................................................... 229 3.14.4.3.3 EMD – Example #1 .................................................................................. 230

VAT for Italy ...................................................................................................................................... 232 Sample request and response ........................................................................................... 232

Web Mark-up .................................................................................................................................... 239 Sample request and response with Mark-up amount ......................................................... 239 Sample request and response with Mark-up percentage ................................................... 240

Frequent Flyer Tier information ........................................................................................................ 242 Sample request and response ........................................................................................... 242

New operation IssueTicketingDocument (Fare Lock Project) ........................................................... 244 Valid Form of Payments – Single and Multiple FOP (MFOP) ............................................ 245 Sample request and response – MFOP (Credit Card and Cash) ........................................ 245 Sample request and response – MFOP (Tokenized Credit Cards) ..................................... 246 Ticket Issuance .................................................................................................................. 247 3.18.2.1 Ticket Issuance by specifying Baggage Allowance ............................................... 248

Sample request and response .................................................................................. 248 3.18.2.2 Ticket Issuance with Certificate Number ............................................................... 249 Sample request and response ............................................................................................ 249 3.18.2.3 Ticket Issuance with Commission ......................................................................... 250

Ticketing Document Web Service Table of Contents 1 March 2019 ix Confidential and Proprietary Sabre Airline Solutions

Sample request and response ............................................................................................ 250 3.18.2.4 Ticket Issuance with Endorsement ........................................................................ 251 Sample request and response ............................................................................................ 251 3.18.2.5 Ticket Issuance with Need Print ............................................................................ 252 Sample request and response ............................................................................................ 252 3.18.2.6 Ticket Issuance with SAC (Secondary Action Code) ............................................. 253 Sample request and response – DCC (Dynamic Currency Conversion) as SAC ................ 253 3.18.2.7 Ticket Issuance with Tour Code ............................................................................ 254 Sample request and response ............................................................................................ 254 3.18.2.8 Ticket Issuance with Pricing Option ...................................................................... 255 Sample request and response ............................................................................................ 255

Sabre Internal Use Only ................................................................................................................... 256 Fulfillment request .............................................................................................................. 256 3.19.1.1 Form of Payment ................................................................................................... 256 3.19.1.2 Direct Ticketing ..................................................................................................... 257 3.19.1.3 PQ Selection ......................................................................................................... 258

3.19.1.3.1 “LCC” PQ Filter ......................................................................................... 258 3.19.1.3.2 “E-ticket” PQ Filter .................................................................................... 258 3.19.1.3.3 “ALL” PQ Filter ......................................................................................... 259 3.19.1.3.4 “PQ Numbers” Filter ................................................................................. 259 3.19.1.3.5 Maximum number of PQs ......................................................................... 259

Issuance Process ............................................................................................................... 261 3.19.2.1 Interactive Error Responses .................................................................................. 261 3.19.2.2 E-Ticket PQ selection only .................................................................................... 261 3.19.2.3 Low Cost Carrier (LCC) PQ selection only ............................................................ 262 3.19.2.4 Combined E-Ticket and LCC PQ selection ........................................................... 264

Expansion of length of Remarks element ......................................................................................... 267 Sample request and response ........................................................................................... 267

Mark up any fare – Agency Retailer Project ..................................................................................... 273 Example of Adjusted Selling Fare level .............................................................................. 273

GDS Automated Refunds CAT33 ..................................................................................................... 278 Example of “Age” of an unaccompanied minor .................................................................. 278

FCMI and FCPI Values ..................................................................................................................... 285 FCMI Indicator .................................................................................................................... 285 FCPI Indicator .................................................................................................................... 286 Example1 of FCMI and FCPI indicator in ‘GetTicketingDcoumentRQ’ service ................... 286 Example2 of FCMI and FCPI indicator in ‘GetTicketingDcoumentRQ’ service ................... 288

Involuntary Reroute Information ....................................................................................................... 290 Example – INVOL indicator in GetTicketingDocument service........................................... 291 Example – Diversion indicator in GetTicketingDocument service ...................................... 293

4 S e c u r i t y v a l i d a t i o n

Introduction ......................................................................................................................................... 296

Ticketing Document Web Service Table of Contents 1 March 2019 x Confidential and Proprietary Sabre Airline Solutions

Security Validation on Airline path ........................................................................................ 296 Security Validation on Travel Agent (Subscriber) path ......................................................... 296

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

Introduction ......................................................................................................................................... 297 TktDoc Communication points ............................................................................................................ 297 Common Error Responses, Reasons and Solution ............................................................................ 298

USG Authentication Errors ................................................................................................... 298 5.3.1.1 USG Invalid Security Token .................................................................................... 298 5.3.1.2 ESSM Authorization Failed ..................................................................................... 299

Security violation .................................................................................................................. 299 Timeout ................................................................................................................................ 300 Throttled Request/Response - Airline .................................................................................. 300 Throttled Subsystem – Airline .............................................................................................. 301 Throttled Request/Response – Travel Agent (Subscriber) ................................................... 302 Invalid Service Version Specified in XML Request ............................................................... 302 Invalid Request XML Format: Request XML Validation Failed Against Schema .................. 303 Database (T2 or PSS) Response: Not found ....................................................................... 303 Unsupported Service Version Specified in XML Request .................................................. 304 Credit Card detokenization failure ...................................................................................... 305 Multiple payments in a single payment element ................................................................. 305 Multiple transactions in a single request ............................................................................ 306

TicketingDocumentServicesRQ 1 Confidential and Proprietary Sabre Airline Solutions

1 Introduction

Overview

Purpose: Guide to functions offered by Ticketing Document (TktDoc) Web Service for both type of

Customers: Airlines (Airline path) and Travel Agencies (Subscriber path).

It is not a complete documentation of XML design. Developers should refer to Sabre Dev Studio for the

most complete information. The instructions on how to access the site can be found later in this document.

The initial examples created for this guide use version 3.5.0

Audience: TktDoc Web Service users.

This Living document requires updates as the product evolves.

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

.

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



2 Understanding TktDoc Web Service

TktDoc Web Service Description

The TicketingDocumentServiceRQ (TktDoc) Web Service allows XML/SOAP based calls to access

document data stored in the T2 and Hawk database. The databse from which information is retrieved

depends on the type of user who requests the data:

- If the request comes from Airline, the document data: air ticket (TKT) or Electronic

Miscellaneous Document (EMD) is retrieved from the T2 database.

- If the request comes from Travel Agency (Subscriber), the air ticket (TKT) data is retrieved from

the Hawk database.

It also allows Airline to update the status of EMD-S from “OK” to “USED” when the service is

consumed via UpdateServiceCouponRQ and store this change in T2 database.

TktDoc Web Service Description Language documents (WSDL) for supported versions of the

TicketingDocumentServicesRQ webservice are published for users and accessible from dev studio.


3 Functions offered by Ticketing Document

(TktDoc)

Introduction

TktDoc Web Service currently offers 2 functions:

- Search for document (GetTicketingDocumentRQ) - available for Airline and Travel Agent

(Subscriber)

- Update status of EMD-S coupon (UpdateServiceCouponRQ) - available for Airline

Search for document

TktDoc allows to search for following types of travel documents depending on the user type requesting this

information:

- Airline: Air ticket (VCR) or Electronic Miscellaneous Document (EMD) or Electronic Vouchers

also known as EMD-CV (VOU), other document types - MSR, EXB, CCR, XXX, REV, MCO,

RFD, TUR, FIM, MPD, SST, PTA

- Travel Agent: Air ticket (eTKT)

Result Type

There are following Result Types offered by TktDoc Webservice:

Custom Details (available in schema versions: 3.3.0 and higher) – provides customized

information about ticketing document such as:

o Customer

o Affinity

o FlownServiceCoupon

o ServiceCoupon

o Miscellaneous

o Amounts

o Taxes

o Remark

o AffiliatedAgent

o FareCalculation

o RelatedDocument

o PrintCoupon

o Payment

o History


A Customer can request each combination of above elements. The parameters are placed under

CustomResponseDetails element. In case of other Result Type than Custom Details these elemnts

are ignored.

For this Result Type the maximum number of documents returned depends on

CustomResponseDetails elements:

o Without History and RelatedDocument – 10 documents,

o With History – 5 documents,

o With RelatedDocument – 7 documents,

o With History and RelatedDocument – 4 documents.

Details – provides full information about ticketing document including document type, itinerary,

traveler’s name, fare details, station and issuing agent information, document history, etc. .

For this Result Type maximum number of documents returned is 4.

Abbreviated – provides shortened information about the document - it doesn’t contain document

history for example. It includes document type, traveler’ name, itinerary, fare, issuing station and

agent information.

This Result Type can return up to 99 documents. If more than 99 documents match search criteria,

a warning is returned to user.

Summary – provides only basic information about the document which is: document number, local

issue date and time, document type, issuing location, name of traveler, total amount).

This Result Type can return maximum 500 documents. If response is truncated due to more than

500 documents matching search criteria, a warning is returned to user.

3.2.1.1 Result Types for Airline

Available Result Types for Airline path depend on the search parameters used:

- if search parameters include DocumentNumber , available Result Types are: CustomDetails,

Details and Abbreviated.

- if search parameters don’t include DocumentNumber, available Result Types are: Abbreviated and

Summary.

If user does not specify Result Type, the default Result Types are:

- for request including DocumentNumber in search parameters: Details

- for request not including DocumentNumber in search parameters: Summary

3.2.1.2 Result Types for Travel Agent (Subscriber)

Supported Result Type for Travel Agent is Details.

3.2.1.3 Examples of Requests and Responses

This section intends to present sample requests and responses for each result type.


3.2.1.3.1 Example request and response for CustomDetails Result Type with History and RelatedDocument for Flight Document (TKT)

Request:

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

xmlns="http://www.sabre.com/ns/Ticketing/DC" Version="3.5.0">

<STL:STL_Header.RQ/>

<STL:POS/>

<SearchParameters resultType="C">

<TicketingProvider>U0</TicketingProvider>

<DocumentNumber>8888888888888</DocumentNumber>

<CustomResponseDetails>History</CustomResponseDetails>

<CustomResponseDetails>RelatedDocument</CustomResponseDetails>

</SearchParameters>

</GetTicketingDocumentRQ>

Response:

<TT:GetTicketingDocumentRS Version="3.5.0"

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

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

xmlns:TT="http://www.sabre.com/ns/Ticketing/DC"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

xmlns:str="http://sabre.com/ticketing/xslt/strings"

xmlns:xs="http://www.w3.org/2001/XMLSchema">

<STL:STL_Header.RS messageID="TKTHLD700-8690-360750778-1393920558432-103-

tktdoc" timeStamp="2014-03-04T02:09:18">

<OrchestrationID seq="1">TKTHLD700-8690-360750778-1393920558432-103-

tktdoc</OrchestrationID>

<DiagnosticData>Found</DiagnosticData>

<STL:Results>

<Success>

<System>T2</System>

<Source>DocumentServices</Source>

</Success>

</STL:Results>

</STL:STL_Header.RS>

<TT:CustomDetails>

<TT:Agent duty="5" sine="SSW" type="WEB">

<ns2:TicketingProvider checkDigit="0" name="SABRE AIRWAYS"

number="888">U0</ns2:TicketingProvider>

<ns2:StationLocation>VZNWB</ns2:StationLocation>

<ns2:StationNumber>77495250</ns2:StationNumber>

<ns2:WorkLocation>VZN</ns2:WorkLocation>

<ns2:HomeLocation>VZN</ns2:HomeLocation>

<ns2:Lniata>54B1F4</ns2:Lniata>

<ns2:IsoCountryCode>ZA</ns2:IsoCountryCode>

<ns2:CompanyName> SABRE AIRWAYS</ns2:CompanyName>

<ns2:EmployeeNumber>0005129</ns2:EmployeeNumber>

<ns2:ShiftStartDateTime>2014-02-03T11:14:02</ns2:ShiftStartDateTime>

<ns2:Session>

<ns2:AgentOpenType>AGT</ns2:AgentOpenType>

<ns2:AgentCloseType>AUT</ns2:AgentCloseType>

<ns2:StationOpenType>AGT</ns2:StationOpenType>

<ns2:StationCloseType>AUT</ns2:StationCloseType>

</ns2:Session>


</TT:Agent>

<TT:TransactionInfo actionType="" category="C" code="" sequence="1"

type="SALE">

<ns2:TCN>00066751300</ns2:TCN>

<ns2:LocalDateTime>2014-02-03T18:41:20</ns2:LocalDateTime>

<ns2:SystemDateTime>2014-02-03T10:41:20</ns2:SystemDateTime>

<ns2:SystemProvider>U0</ns2:SystemProvider>

<ns2:InputEntry>W$FCA</ns2:InputEntry>

</TT:TransactionInfo>

<TT:Ticket accountingCode="888" checkDigit="6" formNumber="88"

number="8888888888888" serialNumber="88888888" service="A" type="TKT">

<TT:Indicators electronic="true" endorsable="false" exchangeable="false"

historical="false" manualAdd="false" manualUpdate="false" netReporting="false"

penaltyRestriction="false" presentCreditCard="false" refundCalculation="false"

reservarionPurge="false" retransmit="false" reverseVoid="false"

selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2014-02-03T00:00:00"

provider="MN">DUIIQC</TT:Sabre>

</TT:Reservation>

<ns2:SystemCreateDateTime>2014-02-03T10:41:00</ns2:SystemCreateDateTime>

<TT:LocalIssueDateTime useTimeForPricing="true">2014-02-

03T18:41:20</TT:LocalIssueDateTime>

<ns2:LastUpdate>2014-02-03T10:41:00</ns2:LastUpdate>

<ns2:ValidatingProvider checkDigit="0" name=" SABRE AIRWAYS"

number="888">U0</ns2:ValidatingProvider>

<ns2:OriginCity>JNB</ns2:OriginCity>

<ns2:DestinationCity>CPT</ns2:DestinationCity>

<ns2:ItineraryType>D</ns2:ItineraryType>

<ns2:ExchCategory>P</ns2:ExchCategory>

<ns2:FareCalculationMode>0</ns2:FareCalculationMode>

<ns2:TicketingMode>/</ns2:TicketingMode>

<ns2:PriceCheckDigit>2</ns2:PriceCheckDigit>

<ns2:CouponText>FVVV</ns2:CouponText>

</TT:Details>

<TT:History code="EMDA" number="65" sequence="5">

<TT:Agent duty="5" sine="SSW">

<ns2:TicketingProvider>U0</ns2:TicketingProvider>



</TT:Agent>

<TT:TransactionInfo>



<ns2:InputMessage>AUTO DISASSOCIATION</ns2:InputMessage>


<TT:Details>

<ns2:SupportingDocument>8888888888888</ns2:SupportingDocument>

<ns2:OldReservation>DUIIQC</ns2:OldReservation>

<ns2:AffectedCoupons>01</ns2:AffectedCoupons>

</TT:Details>

<TT:RelatedDocumentHistory>

<ns2:Miscellaneous>

<ns2:Number>8888888888888</ns2:Number>


</ns2:Miscellaneous>


</TT:RelatedDocumentHistory>

</TT:History>






</TT:Agent>




<ns2:InputMessage>AUTO ASSOCIATION</ns2:InputMessage>


<TT:Details>




</TT:Details>


<ns2:Miscellaneous>





</TT:History>






</TT:Agent>




<ns2:InputMessage>AUTO ASSOCIATION</ns2:InputMessage>


<TT:Details>




</TT:Details>


<ns2:Miscellaneous>





</TT:History>

<TT:History code="ALTR" number="31" sequence="2">

<TT:Agent duty="$" sine="SYS">


<ns2:WorkLocation>SYS</ns2:WorkLocation>

<ns2:HomeLocation>SYS</ns2:HomeLocation>

</TT:Agent>





<ns2:InputMessage>TAPE WRITE-MORE DATA STORED IN VCR FOR

T2</ns2:InputMessage>


<TT:Details>



</TT:Details>

</TT:History>

<TT:History code="OC" number="9" sequence="1">





</TT:Agent>




<ns2:InputMessage>W$FCA</ns2:InputMessage>


<TT:Details>




</TT:Details>

<ns2:ServiceCouponHistory coupon="1" sequence="1">

<ns2:CurrentStatus>OK</ns2:CurrentStatus>

</ns2:ServiceCouponHistory>

</TT:History>

</TT:Ticket>

</TT:CustomDetails>

</TT:GetTicketingDocumentRS>

3.2.1.3.2 Example request and response for Details Result Type for Electronic Voucher (VOU)

Request:




<STL:POS/>

<SearchParameters fetchInterlineCouponStatus="true" resultType="D"

warnOnDuplication="LATEST">

<TicketingProvider> U0</TicketingProvider>


</SearchParameters>


Response:









<STL:STL_Header.RS messageID="H8460305020468-8284-1620723011-1393857344759-8-


<OrchestrationID seq="1">H8460305020468-8284-1620723011-1393857344759-8-



<STL:Results>

<Success>

<System>T2</System>


</Success>

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

<STL:Source>TktDoc</STL:Source>

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

<STL:SystemSpecificResults>

<STL:ErrorMessage>Compensation Voucher (VOU) document is not fully

supported yet in Details/Custom Details format</STL:ErrorMessage>

<STL:ShortText>Compensation Voucher (VOU) document is not fully

supported yet in Details/Custom Details format</STL:ShortText>

</STL:SystemSpecificResults>

</STL:Warning>

</STL:Results>


<TT:Details>

<TT:Agent duty="4" sine="RSH">



<ns2:StationLocation>TJMAP</ns2:StationLocation>


<ns2:WorkLocation>TJM</ns2:WorkLocation>

<ns2:HomeLocation>HDQ</ns2:HomeLocation>

<ns2:Lniata>553E3C</ns2:Lniata>

<ns2:IsoCountryCode>XU</ns2:IsoCountryCode>

<ns2:Name>R GABRIEL DURAI</ns2:Name>

<ns2:FirstName>R </ns2:FirstName>

<ns2:LastName>GABRIEL DURAI</ns2:LastName>



<ns2:Session>


</ns2:Session>

</TT:Agent>


type="RFND">

<ns2:TCN>10697279601</ns2:TCN>





<TT:Voucher accountingCode="888" checkDigit="4" formNumber="88"

number="8888888888888" serialNumber="8888888" service="A" type="VOU">

<TT:Indicators electronic="false"/>

<TT:Details>

<TT:Reservation>


provider="U0">EXNOZD</TT:Sabre>

</TT:Reservation>



<ns2:LocalIssueDateTime>2013-12-05T21:28:10</ns2:LocalIssueDateTime>

<ns2:ValidatingProvider checkDigit="2" name="SABRE AIRWAYS"


<ns2:ReasonType>OU</ns2:ReasonType>

<ns2:CurrentActivity>RV</ns2:CurrentActivity>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>RRCOO/PAXONE</ns2:Name>

<ns2:FirstName>PAXONE</ns2:FirstName>

<ns2:LastName>RRCOO</ns2:LastName>

</TT:Traveler>

<ns2:Purchaser>

<ns2:Name>RRCOO/PAXONE</ns2:Name>

<ns2:FirstName>PAXONE</ns2:FirstName>

<ns2:LastName>RRCOO</ns2:LastName>

</ns2:Purchaser>

</TT:Customer>

<TT:Amounts>

<TT:New>

<ns2:Base>

<ns2:Amount currencyCode="EUR" decimalPlace="2">1048.00</ns2:Amount>

<ns2:Text>1048.00</ns2:Text>

<ns2:ApplyCreditInd>true</ns2:ApplyCreditInd>

</ns2:Base>

<ns2:Equivalent>

<ns2:Amount currencyCode="RUB" decimalPlace="0">46115</ns2:Amount>

<ns2:Text>46115</ns2:Text>


<ns2:CurrencyConversion/>

</ns2:Equivalent>

<ns2:TotalTax>




</ns2:TotalTax>

<TT:Total>




</TT:Total>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="YQF" exempt="true" sequence="1">




</ns2:Tax>

<ns2:Tax code="HK" exempt="true" sequence="2">




</ns2:Tax>

</TT:New>

</TT:Taxes>


<TT:Remark>

<ns2:OriginalIssue sequence="1">8888888888888</ns2:OriginalIssue>

</TT:Remark>

<TT:RelatedDocument>

<TT:Original sequence="0">


<ns2:CheckDigit>0</ns2:CheckDigit>

<ns2:IssueDate>2013-12-05</ns2:IssueDate>

</TT:Original>

<TT:Refund sequence="1">



<ns2:Coupon>12</ns2:Coupon>

</TT:Refund>

</TT:RelatedDocument>

<TT:PrintCoupon couponType="P" printerType="0" stockType="T">

<ns2:Lniata>BEC33E</ns2:Lniata>

</TT:PrintCoupon>

<TT:Payment sequence="1" type="TV">

<TT:Base>

<TT:Amount currencyCode="RUB" decimalPlace="0">46115</TT:Amount>

<ns2:ApplyCreditInd>false</ns2:ApplyCreditInd>

</TT:Base>

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>VOUCHER</ns2:Remarks>

<TT:Voucher/>

</TT:Payment>


<TT:Agent duty="4" sine="RSH">


<ns2:WorkLocation>TJM</ns2:WorkLocation>


</TT:Agent>



<ns2:SystemProvider>SU</ns2:SystemProvider>


<TT:Details>


<ns2:OldReservation>EXNOZD</ns2:OldReservation>

<ns2:AccountingCode>888</ns2:AccountingCode>

</TT:Details>

</TT:History>

</TT:Voucher>

</TT:Details>



3.2.1.3.3 Example request and response for Details Result Type for Flight Document (TKT)

Request:




<STL:POS/>

<SearchParameters resultType="D" warnOnDuplication="LATEST">



</SearchParameters>


Response:








<STL:STL_Header.RS messageID="H8460305020468-8284-1620723011-1393858230781-

14-tktdoc" timeStamp="2014-03-03T15:50:30">




<STL:Results>

<Success>

<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent sine="A06">



<ns2:StationLocation>SOF</ns2:StationLocation>


<ns2:HomeLocation>MUC</ns2:HomeLocation>

<ns2:Lniata>010000</ns2:Lniata>

<ns2:IsoCountryCode>BG</ns2:IsoCountryCode>

<ns2:IataNumber>09210445</ns2:IataNumber>

<ns2:CompanyName> SABRE AIRWAYS</ns2:CompanyName>

</TT:Agent>


type="SALE">



<ns2:SystemProvider>1A</ns2:SystemProvider>

<ns2:InputEntry>CREATED BY PNL/ADL GH REQUEST</ns2:InputEntry>









selfSale="false"/>

<TT:Details>

<ns2:TourNumber>MM09</ns2:TourNumber>

<TT:Reservation>

<ns2:OtherSystem>7POE46</ns2:OtherSystem>

</TT:Reservation>




<ns2:ValidatingProvider checkDigit="6" name="AMADEUS"

number="790">1A</ns2:ValidatingProvider>

<ns2:OriginCity>SOF</ns2:OriginCity>

<ns2:DestinationCity>SOF</ns2:DestinationCity>

<ns2:ItineraryType>I</ns2:ItineraryType>

<ns2:ExchTransactionDate>2011-01-14</ns2:ExchTransactionDate>




<ns2:CouponText>FFVV</ns2:CouponText>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>RODIN/NIKOLAY MR</ns2:Name>

<ns2:FirstName>NIKOLAY MR</ns2:FirstName>

<ns2:LastName>RODIN</ns2:LastName>

<ns2:Contact>

<ns2:Phone>35928462000</ns2:Phone>

</ns2:Contact>

</TT:Traveler>

</TT:Customer>

<TT:ServiceCoupon coupon="1" entitlement="1">

<ns2:MarketingProvider checkDigit="0" name="SABRE AIRWAYS"

number="888">U0</ns2:MarketingProvider>

<ns2:MarketingFlightNumber>1363</ns2:MarketingFlightNumber>

<ns2:ClassOfService>N</ns2:ClassOfService>

<ns2:FareBasis>NLIGHT</ns2:FareBasis>

<TT:StartLocation>SOF</TT:StartLocation>

<ns2:StartDateTime>2012-04-21T12:45:00</ns2:StartDateTime>

<TT:EndLocation>SVO</TT:EndLocation>

<ns2:BookingStatus>OK</ns2:BookingStatus>

<ns2:CurrentStatus>USED</ns2:CurrentStatus>

<ns2:CurrentControllingProvider

hosted="false">FB</ns2:CurrentControllingProvider>

<ns2:BagAllowance>1PC</ns2:BagAllowance>

<ns2:StopOver>O</ns2:StopOver>

<ns2:CouponUse>F</ns2:CouponUse>

<ns2:Indicators fareBreak="false" sideTripEnd="false"

sideTripStart="false" unchargeableSurface="false" zeroFareAmount="false"/>

<ns2:ValidatingProvider>FB</ns2:ValidatingProvider>

<ns2:StartTimeText>1245P</ns2:StartTimeText>

</TT:ServiceCoupon>



<ns2:MarketingProvider checkDigit="0" name=" SABRE AIRWAYS "



<ns2:ClassOfService>R</ns2:ClassOfService>

<ns2:FareBasis>RLIGHT</ns2:FareBasis>

<TT:StartLocation>SVO</TT:StartLocation>


<TT:EndLocation>SOF</TT:EndLocation>








<ns2:ValidatingProvider>FB</ns2:ValidatingProvider>


</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base>




</ns2:Base>

<ns2:Equivalent>

<ns2:Amount currencyCode="BGN" decimalPlace="2">487.05</ns2:Amount>




</ns2:Equivalent>

<TT:Total>




</TT:Total>

<ns2:Tax code="YQ" exempt="false" sequence="1">




</ns2:Tax>

<ns2:Tax code="BG" exempt="false" sequence="2">




</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>





</ns2:Tax>

<ns2:Tax code="BG" exempt="false" sequence="2">





</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements sequence="1">FB ONLY</ns2:Endorsements>

<ns2:Payment sequence="1">CASH</ns2:Payment>

</TT:Remark>

<TT:AffiliatedAgent>

<TT:Booking sine="A06">

<ns2:WorkLocation>0607M</ns2:WorkLocation>

</TT:Booking>

</TT:AffiliatedAgent>

<ns2:FareCalculation>

<ns2:New>SOF FB MOW183.92FB SOF144.36NUC328.28END ROE0.758475</ns2:New>

</ns2:FareCalculation>

<TT:Payment sequence="1" type="CA">

<TT:Tax>

<TT:Amount currencyCode="BGN" decimalPlace="2">0.00</TT:Amount>


</TT:Tax>

<TT:Total>

<TT:Amount currencyCode="BGN" decimalPlace="2">682.67</TT:Amount>


</TT:Total>

<ns2:Remarks>CASH</ns2:Remarks>

<TT:Cash CashIndicator="true"/>

</TT:Payment>


<TT:Agent>




</TT:Agent>



<ns2:SystemProvider>1A</ns2:SystemProvider>

<ns2:InputMessage>CREATED BY PNL/ADL GH REQUEST</ns2:InputMessage>


<TT:Details>



</TT:Details>







</TT:History>

</TT:Ticket>

</TT:Details>



3.2.1.3.4 Example request and response for Abbreviated Result Type for Flight Document (TKT)

Request:




<STL:POS/>

<SearchParameters fetchInterlineCouponStatus="true" resultType="A"

warnOnDuplication="LATEST">



</SearchParameters>


Response:













<STL:Results>

<Success>

<System>T2</System>


</Success>

</STL:Results>


<TT:Abbreviated>

<TT:Agent sine="A06">



<ns2:StationLocation>SOF</ns2:StationLocation>


<ns2:HomeLocation>MUC</ns2:HomeLocation>

</TT:Agent>

<TT:TicketingDocument accountingCode="888" checkDigit="1" formNumber="88"

number="8888888888888" serialNumber="8888888" type="TKT">

<ns2:Indicators electronic="true" manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:OtherSystem>7POE46</ns2:OtherSystem>

</ns2:Reservation>


</TT:Details>

<ns2:Customer>

<TT:Traveler>

<ns2:Name>RODIN/NIKOLAY MR</ns2:Name>

<ns2:FirstName>NIKOLAY MR</ns2:FirstName>


<ns2:LastName>RODIN</ns2:LastName>

</TT:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon coupon="1">

<ns2:MarketingProvider>U0</ns2:MarketingProvider>


<ns2:ClassOfService>N</ns2:ClassOfService>

<ns2:FareBasis>NLIGHT</ns2:FareBasis>

<ns2:StartLocation>SOF</ns2:StartLocation>


<ns2:EndLocation>SVO</ns2:EndLocation>



</ns2:ServiceCoupon>




<ns2:ClassOfService>R</ns2:ClassOfService>

<ns2:FareBasis>RLIGHT</ns2:FareBasis>

<ns2:StartLocation>SVO</ns2:StartLocation>


<ns2:EndLocation>SOF</ns2:EndLocation>




<ns2:Payment sequence="1" type="CA"/>

</TT:TicketingDocument>

</TT:Abbreviated>


3.2.1.3.5 Example request and response for Summary Result Type for Flight Document (TKT)

Request:




<STL:POS/>

<SearchParameters resultType="S">


<LastName lastName="KULAK" workLocation="ETC"/>

</SearchParameters>


Response:














<Results>

<Success>

<System>T2</System>


</Success>

</Results>


<TT:Summary>

<TT:DocumentNumber>8888888888888</TT:DocumentNumber>

<TT:LocalIssueDateTime>2014-03-03T07:02:07</TT:LocalIssueDateTime>

<TT:DocumentType>TKT</TT:DocumentType>

<TT:IssuingLocation>ETC</TT:IssuingLocation>

<TT:Reservation>IGKKDN</TT:Reservation>

<TT:FirstName>JAN</TT:FirstName>

<TT:LastName>KULAK</TT:LastName>

<TT:TotalAmount currencyCode="USD" decimalPlace="2">1976.90</TT:TotalAmount>

</TT:Summary>


3.2.1.3.6 Example request and response for Details Result Type for Travel Agent (Subscriber)

Request:




<STL:POS/>

<SearchParameters>

<TicketingProvider>1S</TicketingProvider>

<DocumentNumber workLocation="WD40">8888888888888</DocumentNumber>

</SearchParameters>


Response:

<GetTicketingDocumentRS Version="3.5.0"

xmlns="http://www.sabre.com/ns/Ticketing/DC"

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



<OrchestrationID seq="0"

xmlns="http://services.sabre.com/STL/v01">TKTHLD700-8690-360750778-

1393920862391-113-tktdoc</OrchestrationID>

<STL:DiagnosticData>Found</STL:DiagnosticData>

<STL:Results>

<STL:Success>


<STL:Source>TktDocWS</STL:Source>

</STL:Success>

</STL:Results>


<Details>

<Agent duty="*" ordinal="15114" sine="ATW" type="64">

<TicketingProvider checkDigit="1" name=”SABRE AIRWAYS”

number="888">1S</TicketingProvider>


<StationLocation>MKE</StationLocation>

<WorkLocation>WD40</WorkLocation>

<HomeLocation>WD40</HomeLocation>

<Lniata>47610E</Lniata>

<IsoCountryCode>US</IsoCountryCode>

<CompanyName>ADELMAN TRAVEL</CompanyName>

</Agent>

<TransactionInfo>

<TCN>02514069005</TCN>

<LocalDateTime>2014-03-04T02:14:00</LocalDateTime>

<SystemDateTime>2014-03-04T02:14:00</SystemDateTime>

<SystemProvider>1S</SystemProvider>

<InputEntry>W$U0A$KP1$FCA+</InputEntry>

</TransactionInfo>

<Ticket accountingCode="888" number="8888888888888"

serialNumber="8888888888" type="TKT">

<Indicators electronic="true" selfSale="false"/>

<Details>

<Reservation>

<Sabre createDate="2014-03-04T00:00:00" provider="U0" purgeDate="2014-

05-05T00:00:00">EMKIQS</Sabre>

</Reservation>

<SystemCreateDateTime>2014-03-04T02:14:00</SystemCreateDateTime>

<LocalIssueDateTime>2014-03-04T00:00:00</LocalIssueDateTime>

<LastUpdate>2014-03-04T02:14:00</LastUpdate>

<ValidatingProvider checkDigit="1" name="SABRE AIRWAYS"

number="888">U0</ValidatingProvider>

<AgencyBillingNumber>0123456789</AgencyBillingNumber>

<InvoiceNumber>0424504</InvoiceNumber>

<OriginCity>DEN</OriginCity>

<DestinationCity>DFW</DestinationCity>

<ItineraryType>D</ItineraryType>

<ExchCategory>I</ExchCategory>

<FareCalculationMode>0</FareCalculationMode>

<TicketingMode>/</TicketingMode>

<PriceCheckDigit>1</PriceCheckDigit>

<CurrencyOverride>USD</CurrencyOverride>

<PointOfSaleOverride>MKE</PointOfSaleOverride>

<PointOfTicketOverride>MKE</PointOfTicketOverride>

</Details>

<Customer>

<Traveler nameId="1" nameNumber="1.1">

<Name>KOWALSKI/JAN</Name>

<FirstName>JAN</FirstName>

<LastName>KOWALSKI</LastName>

<ExternalNumber>TEST</ExternalNumber>

<PassengerType>ADT</PassengerType>

</Traveler>

</Customer>

<ServiceCoupon coupon="1" entitlement="1" segmentId="2" type="64">

<MarketingProvider name="SABRE AIRWAYS">U0</MarketingProvider>

<MarketingFlightNumber>379</MarketingFlightNumber>

<OperatingProvider name="SABRE AIRWAYS">U0</OperatingProvider>

<OperatingFlightNumber>379</OperatingFlightNumber>

<ClassOfService>Y</ClassOfService>

<FareBasis>YA2AA</FareBasis>

<StartLocation>DEN</StartLocation>


<StartDateTime>2014-05-05T13:25:00</StartDateTime>

<EndLocation>DFW</EndLocation>

<EndDateTime>2014-05-05T16:20:00</EndDateTime>

<NotValidAfterDate>2014-05-05</NotValidAfterDate>

<BookingStatus>OK</BookingStatus>

<CurrentStatus>OK</CurrentStatus>

<Reservation>EMKIQS</Reservation>

<BagAllowance>2PC</BagAllowance>

<BookingDate>2014-03-04</BookingDate>

<CouponUse>F</CouponUse>

<Indicators connectionOverride="false" fareBreak="true" noBreak="false"

sideTripEnd="false" sideTripStart="false" turnaround="false"

unchargeableSurface="false"/>

<ConjunctiveDocNumber>8888888888889</ConjunctiveDocNumber>

<FareBreakAmount>

<Amount decimalPlace="2">912.56</Amount>

</FareBreakAmount>

<BookingClass>Y</BookingClass>

<Equipment>S80</Equipment>

<PricingRecordFareType>EU</PricingRecordFareType>

<FareType>00</FareType>

<FareComponent sequence="0">

<FareProvider>U0</FareProvider>

<Tariff>0</Tariff>

<FareRule>2000</FareRule>

<PricingVendor>ATP</PricingVendor>

</FareComponent>

</ServiceCoupon>

<Amounts>

<New>

<Base>

<Amount currencyCode="USD">940.47</Amount>

</Base>

<TotalTax>

<Amount>81.53</Amount>

</TotalTax>

<Total>


</Total>

</New>

<Net/>

<Other>

<Commission>


<PercentageRate>1</PercentageRate>

</Commission>

<NUC>


</NUC>

</Other>

</Amounts>

<Taxes>

<New>

<Tax code="US" sequence="0" status="N">

<Amount currencyCode="USD" decimalPlace="2">70.53</Amount>

</Tax>

<Tax code="ZP" sequence="0" status="N">



</Tax>

<Tax code="AY" sequence="0" status="N">


</Tax>

<Tax code="XF" sequence="0" status="N">


</Tax>

<Airport code="XF" exempt="false">


<AirportCode>DEN</AirportCode>

</Airport>

<Domestic code="ZP">


<AirportCode>DEN</AirportCode>

</Domestic>

</New>

<Other/>

</Taxes>

<AffiliatedAgent>

<Booking ordinal="15114"/>

</AffiliatedAgent>

<FareCalculation type="132">

<New>DEN U0 DFW Q27.91 912.56USD940.47END ZPDEN XT2.50AY

4.50XFDEN4.5</New>

</FareCalculation>

<Payment sequence="0" type="CA">

<Total>


</Total>

<Cash/>

</Payment>

</Ticket>

</Details>

</GetTicketingDocumentRS>

3.2.1.3.7 Example request and response for Details Result Type for Flight Document (TKT) with a tour code

The Tour Code field has been expanded by two characters, making the field now 15 alpha-numeric

characters. The field can consist of any combinations of alpha and numeric characters. An asterisk (*) and

a space can also be accepted.

U – Tour Ticket

U = When a tour code prefix is not used at ticket issuance, only the 13 characters will be

displayed. This will display the fare and prefix with an IT.

N – Tour Ticket

N =When the UN* is used at ticket issuance 15 characters will be displayed. This will display the fare, but

a prefix is not displayed.

IT – Inclusive Tour


IT = Entry of UI* with a maximum of 13 additional characters and will display the identifier IT

immediately in front of the tour number:

BT – Bulk Tour

BT = Used for bulk fare ticketing. This will suppress the fare information on the electronic or paper

ticket and display a BT in the place of the base fare amount.

Request:

<GetTicketingDocumentRQ xmlns="http://www.sabre.com/ns/Ticketing/DC"

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


<STL:POS/>




</SearchParameters>


Response:

<GetTicketingDocumentRS Version="3.5.1"

xmlns:TT="http://www.sabre.com/ns/Ticketing/DC">

<STL:STL_Header.RS messageID="TKTHLI700-1545-1620828169-1405598516863-

1831-tktdoc" timeStamp="2014-07-17T07:01:56"


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

seq="1">TKTHLI700-1545-1620828169-1405598516863-1831-tktdoc</OrchestrationID>

<DiagnosticData

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

<STL:Results>

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

<System>T2</System>


</Success>

</STL:Results>


<CustomDetails>

< Agent sine="RL1">

< TicketingProvider checkDigit="3" name="SABRE AIRWAYS"

number="888">U0</ TicketingProvider>

<StationLocation>TVP</ StationLocation>

<StationNumber>41000120</StationNumber>

<WorkLocation>SYS</ WorkLocation>

<HomeLocation>TVP</HomeLocation>

<Lniata>F2F206</ Lniata>

<IsoCountryCode>US</IsoCountryCode>

< CompanyName>SABRE AIRWAYS</CompanyName>

</Agent>

<TransactionInfo actionType="" category="C" code="" sequence="1"

type="SALE">

<LocalDateTime>2014-05-06T11:17:00</LocalDateTime>


<SystemProvider>B6</SystemProvider>


< InputEntry>RECEIVED FROM B6</InputEntry>

</ TransactionInfo>

<Ticket accountingCode="888" checkDigit="1" formNumber="88"


<Indicators electronic="true" endorsable="false"

exchangeable="false" historical="false" manualAdd="false" manualUpdate="false"

netReporting="false" penaltyRestriction="false" presentCreditCard="false"

refundCalculation="false" reservarionPurge="false" retransmit="false"

reverseVoid="false" selfSale="false"/>

<Details>

<TourNumber>IT13OCT08 B612A</TourNumber>

<Reservation>

<OtherSystem>LVHLSZ</OtherSystem>

</Reservation>

<SystemCreateDateTime>2014-05-

06T11:17:00</SystemCreateDateTime>



<ValidatingProvider checkDigit="6" name="SABRE AIRWAYS"

number="888">U0</ValidatingProvider>

<OriginCity>LIM</OriginCity>

<DestinationCity>SCL</DestinationCity>

<ItineraryType>D</ItineraryType>

<FareCalculationMode>7</FareCalculationMode>



<CouponText>FVVV</CouponText>

</Details>

</Ticket>

</CustomDetails>


Possible Search Parameters for Airline

When searching for document following sets of parameters are available:

- By DocumentNumber (maximum number of documents requested in one transaction = 4)

o By DocumentNumber and LocalIssueDate*

o By DocumentNumber and WorkLocation*

o By DocumentNumber and LocalIssueDate and WorkLocation*

- By LastName

o By LastName and FirstName

o By LastName and Reservation (PNR locator)

o By LastName and WorkLocation

o By LastName and LocalIssueDate

o By LastName and LocalIssueDateRange

o By DocumentType and LastName

o By DocumentType and LastName and FirstName

o By DocumentType and LocalIssueDate and WorkLocation

o By LocalIssueDate and WorkLocation

- By Reservation (PNR locator)


o By Reservation (PNR locator) and CreateDate (date when PNR was made)

o By Reservation (PNR locator) and WorkLocation

o By Reservation (PNR locator) and LocalIssueDate

o By Reservation (PNR locator) and LocalIssueDateRange

* Currently when searching by DocumentNumber and LocalIssueDate and WorkLocation or

DocumentNumber and LocalIssueDate or DocumentNumber and WorkLocation and searching for more

than 1 document in a single transaction, the WorkLocation and/or LocalIssueDate for all documents is

taken from first searched document and sent to T2. This is to be changed in the future. After this change

WorkLocation and/or LocalIssueDate will be checked for each document separately. The change hasn’t

been scheduled for Release yet.

DocumentType is optional for all sets of parameters. Currently when searching by DocumentNumber and

DocumentType, DocumentType is ignored and only DocumentNumber is sent in the query to T2 database.

It is planned to be changed in the future. After this change a check will be performed in order to verify if

the DocumentType of document retrieved from T2 database is the same as the DocumentType requested.

If it matches the DocumentType requested, it will be returned to user. If it doesn’t, an error message will

be returned advising that “Document (number) was not found”. It will be changed in near future.

It is not possible to search for document using following parameters only:

- FirstName only – this search parameter requires also LastName

- DocumentType only

- WorkLocation only

- LocalIssueDate only

When incorrect set of search parameters are used, an error message is returned.

3.2.2.1 Added New VCR Search Capabilities

TicketingDocumentServices is enhanced to provide more options to the users to search for VCR documents.

This new capability is available as part of TicketingDocumentServices_v.3.15.0 onwards.

This enhancement will help agents to search the correct VCR faster and also they have an option to narrow

down the search by adding additional qualifiers like passenger name, departure date, flight number, status

to the search.

New Capability will include following search options for the TicketingDocumentServices user:

3.2.2.1.1 Search by VCR Number and Passenger Last Name

Airline customers can search by 13 digit VCR number along with the passenger name. VCR number is a

mandatory element whereas passenger last name is optional in the request. In case of multiple documents

that match the search parameters, the latest document [based on the datetimestamp] will be returned as part

of the service response. Default result type is “Detail” if no other result type is mentioned in the request.

Below is an example of search by VCR number and passenger last name

Request:




<STL:STL_Header.RQ />

<STL:POS />

<SearchParameters>


<DocumentNumber lastName="MARSH">8888888888888</DocumentNumber>

</SearchParameters>


Response:

<TT:GetTicketingDocumentRS xmlns:TT="http://www.sabre.com/ns/Ticketing/DC"




xmlns:xs="http://www.w3.org/2001/XMLSchema" Version="3.15.0">

<STL:STL_Header.RS messageID="TKTHLI700-5496-326684371-1485949967328-14875-


<OrchestrationID seq="1">TKTHLI700-5496-326684371-1485949967328-14875-


<DiagnosticData

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Found</DiagnosticData>

<STL:Results>

<Success xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent sine="ASB">

<ns2:TicketingProvider xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

checkDigit="5" name="SABRE AIRWAYS" number="888">U0</ns2:TicketingProvider>

<ns2:StationLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:StationLocation>

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">T95BN</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">F2FA35</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AE</ns2:IsoCountryCode>

<ns2:IataNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">99999999</ns2:IataNumber>

<ns2:CompanyName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE

AIRWAYS</ns2:CompanyName>

</TT:Agent>


type="SALE">

<ns2:LocalDateTime

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2014-12-

08T00:40:13</ns2:LocalDateTime>

<ns2:SystemDateTime


08T00:40:13</ns2:SystemDateTime>

<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1W</ns2:SystemProvider>


<ns2:InputEntry xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CREATED

BY 1W</ns2:InputEntry>








selfSale="false"/>

<TT:Details>

<ns2:TourNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYDR008</ns2:TourNumber>

<TT:Reservation>


provider="EY">HKAWUT</TT:Sabre>

<ns2:OtherSystem

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MEGADQ</ns2:OtherSystem>

</TT:Reservation>

<ns2:SystemCreateDateTime


01T03:02:00</ns2:SystemCreateDateTime>

<ns2:LocalIssueDateTime


01T00:00:00</ns2:LocalIssueDateTime>

<ns2:LastUpdate xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2014-

12-08T00:40:00</ns2:LastUpdate>

<ns2:ValidatingProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" checkDigit="5" name="SABRE

AIRWAYS" number="888">U0</ns2:ValidatingProvider>

<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:OriginCity>

<ns2:DestinationCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FRA</ns2:DestinationCity>

<ns2:ItineraryType

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">I</ns2:ItineraryType>

<ns2:InclusiveTransaction

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IT</ns2:InclusiveTransaction>

<ns2:FareCalculationMode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0</ns2:FareCalculationMode>

<ns2:TicketingMode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">/</ns2:TicketingMode>

<ns2:PriceCheckDigit

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0</ns2:PriceCheckDigit>

<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FFVV</ns2:CouponText>

</TT:Details>

<TT:Customer>

<TT:Traveler nameId="2">

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MARSH/ALAN</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ALAN</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MARSH</ns2:LastName>

<TT:PassengerType>ADT</TT:PassengerType>

</TT:Traveler>


</TT:Customer>


<ns2:MarketingProvider xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

checkDigit="5" name="SABRE AIRWAYS" number="888">U0</ns2:MarketingProvider>

<ns2:MarketingFlightNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">6451</ns2:MarketingFlightNumb

er>

<ns2:OperatingProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VA</ns2:OperatingProvider>

<ns2:OperatingFlightNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">29</ns2:OperatingFlightNumber

>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">B</ns2:ClassOfService>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BKNTOWAU</ns2:FareBasis>

<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:StartLocation>

<ns2:StartDateTime


06T16:05:00</ns2:StartDateTime>

<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:EndLocation>

<ns2:NotValidAfterDate


31</ns2:NotValidAfterDate>

<ns2:BookingStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OK</ns2:BookingStatus>

<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OK</ns2:CurrentStatus>

<ns2:PreviousStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CTRL</ns2:PreviousStatus>



hosted="true">VA</ns2:CurrentControllingProvider>

<ns2:BagAllowance

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">30K</ns2:BagAllowance>

<ns2:CouponUse

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">F</ns2:CouponUse>

<ns2:Indicators xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

fareBreak="false" sideTripEnd="false" sideTripStart="false"

unchargeableSurface="false" zeroFareAmount="false"/>

<ns2:StartTimeText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">405P</ns2:StartTimeText>

</TT:ServiceCoupon>



checkDigit="5" name="SABRE AIRWAYS" number="888">EY</ns2:MarketingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1</ns2:MarketingFlightNumber>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">B</ns2:ClassOfService>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BKNTOWAU</ns2:FareBasis>

<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:StartLocation>


<ns2:StartDateTime



<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FRA</ns2:EndLocation>




<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:StopOver

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">X</ns2:StopOver>

<ns2:CouponUse





<ns2:StartTimeText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">205A</ns2:StartTimeText>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Amount currencyCode="AUD" decimalPlace="2">0.00</ns2:Amount>

<ns2:Text>IT</ns2:Text>

</ns2:Base>

<ns2:Equivalent xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Amount currencyCode="AED" decimalPlace="0">0</ns2:Amount>

<ns2:Text>IT</ns2:Text>


</ns2:Equivalent>

<TT:Total>

<ns2:Amount xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

currencyCode="AED" decimalPlace="0">0</ns2:Amount>

<ns2:Text

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IT</ns2:Text>

</TT:Total>

<ns2:Tax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="AU"

exempt="false" sequence="1">

<ns2:Amount currencyCode="AED" decimalPlace="2">200.00</ns2:Amount>


</ns2:Tax>

<ns2:Tax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="WY"




</ns2:Tax>

</TT:New>

<ns2:InclusiveTour xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Base>



</ns2:Base>


<ns2:Total>

<ns2:Amount currencyCode="AED" decimalPlace="0">0</ns2:Amount>

</ns2:Total>

</ns2:InclusiveTour>

<TT:Other>

<ns2:Commission xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">


<ns2:PercentageRate>0.0</ns2:PercentageRate>


</ns2:Commission>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax code="AU" exempt="false" sequence="1">


currencyCode="AED" decimalPlace="2">200.00</ns2:Amount>

<ns2:Text

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">200.00</ns2:Text>

</TT:Tax>

<TT:Tax code="WY" exempt="false" sequence="2">


currencyCode="AED" decimalPlace="2">100.00</ns2:Amount>

<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

sequence="1">/NON ENDORSABLE/VALID U0 AND U0/U0 ONLY</ns2:Endorsements>

<ns2:Payment xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

sequence="1">CASH</ns2:Payment>

</TT:Remark>

<ns2:FareCalculation xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:New>SYD U0 X/AUH U0 FRA Q SYDFRA/IT /IT

END</ns2:New>


<TT:Payment paymentConfirmation="false" sequence="1" type="CA">

<TT:Total>

<TT:Amount currencyCode="AED" decimalPlace="0">0</TT:Amount>

<ns2:ApplyCreditInd

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">false</ns2:ApplyCreditInd>

</TT:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CASH</ns2:Remarks>


</TT:Payment>

<TT:History code="RTND" number="38" sequence="7">

<TT:Agent>

<ns2:TicketingProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:TicketingProvider>

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYS</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYS</ns2:HomeLocation>

</TT:Agent>



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:SystemProvider>

<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RETURNED BY

VA</ns2:InputMessage>


<TT:Details>

<ns2:SupportingDocument

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">8885211820518</ns2:Supporting

Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">HKAWUT</ns2:OldReservation>

<ns2:AffectedCoupons

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">01</ns2:AffectedCoupons>

</TT:Details>

<ns2:ServiceCouponHistory

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" coupon="1" sequence="1">

<ns2:PreviousControllingProvider>VA</ns2:PreviousControllingProvider>


<ns2:PreviousStatus>CTRL</ns2:PreviousStatus>


</TT:History>

<TT:History code="DETN" number="48" sequence="6">

<TT:Agent>



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">UNABLE TO PROCESS 368NOT

AUTHORIZED</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>

</TT:History>

<TT:History code="MEAL" number="45" sequence="5">

<TT:Agent duty="5" sine="HJS">




<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CRC</ns2:HomeLocation>

</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider



<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>

</TT:History>


<TT:Agent>



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">REMOVED FROM DETAIN AND SENT

TO</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>

</TT:History>


<TT:Agent duty="R" sine="M1S">




<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TTY</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TTY</ns2:HomeLocation>

</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADDED TO DETAIN BY VI/TE

ASSOCIATION DEFERRAL - TO</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>

</TT:History>

<TT:History code="CTRL" number="41" sequence="2">




<ns2:WorkLocation


<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:HomeLocation>

</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">UNSOL CTRL TO

VA</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>



<ns2:CurrentStatus>CTRL</ns2:CurrentStatus>

<ns2:PreviousStatus>OK</ns2:PreviousStatus>


<ns2:CurrentControllingProvider>VA</ns2:CurrentControllingProvider>


</TT:History>





<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">T95BN</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1W</ns2:HomeLocation>

</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1W</ns2:SystemProvider>

<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CREATED BY

1W</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>









</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>

</soap-env:Envelope>

3.2.2.1.2 Search by Service Coupon details

Airline customers can search and display VCR or list of VCRs by service coupon details. Below are the

various combinations which the customers can use.

o Start location


o End location

o Last and first name

o Marketing flight number

o Flight start date or flight start date range

o Open Segment Indicator

o Coupon Status

Note: All the above search parameters are optional. However, there are few business validations that have

been put in place in the system, which are as below:

1. In case requestor mentions the end location in the request, then it is mandatory to add start location.

2. In case requestor mentions the first name in the request then it is mandatory to add the last name.

3. In case requestor mentions the service coupon status in the request, then it is mandatory to add the

Marketing flight number and start date.

4. In case requestor mentions the flight start date or flight start date range and OPEN segment indicator

in the request, then it is mandatory to add the passenger last name and start location.

5. In case requestor mentions the flight start date or flight start date, then it is mandatory to add

passenger last name and marketing flight number.

Below is an example of search criteria: Origin, Destination, Last name, Departure date and Flight number:

Request:




<STL:POS/>

<SearchParameters>


<ServiceCoupon>

<StartLocation>AUH</StartLocation>

<EndLocation>LHR</EndLocation>

<LastName lastName="MARTIN"/>

<MarketingFlight number="11" provider="U0"/>

<FlightStartDate>2017-03-20</FlightStartDate>

</ServiceCoupon>

</SearchParameters>


Response:












<Results>

<Success>

<System>T2</System>



</Success>

</Results>


<TT:Summary>




<TT:IssuingLocation>AUH</TT:IssuingLocation>

<TT:Reservation>QDVPED</TT:Reservation>

<TT:FirstName>ONE</TT:FirstName>

<TT:LastName>MARTIN</TT:LastName>

<TT:TotalAmount currencyCode="AED" decimalPlace="0">9045</TT:TotalAmount>

</TT:Summary>


</soap-env:Body>


Below is an example of search criteria: Origin, Destination, Last name and OPEN segment:

Request:




<STL:POS/>

<SearchParameters>


<ServiceCoupon openSegmentInd="true">

<StartLocation>LHR</StartLocation>

<EndLocation>AUH</EndLocation>

<LastName lastName="COOPER"/>

</ServiceCoupon>

</SearchParameters>


Response:












<Results>

<Success>

<System>T2</System>


</Success>


</Results>


<TT:Summary>




<TT:IssuingLocation>AUH</TT:IssuingLocation>

<TT:Reservation>IRJIFO</TT:Reservation>

<TT:FirstName>NICOLA MRS</TT:FirstName>

<TT:LastName>COOPER</TT:LastName>

<TT:TotalAmount currencyCode="AED"

decimalPlace="0">28980</TT:TotalAmount>

</TT:Summary>


</soap-env:Body>


3.2.2.1.3 Search by Form of Identification

Airline customers can search and display VCR or list of VCRs by FOID number of the passenger. Below

are the combinations which the customers can use.

o Type

o Number

o Country

Note: FOID Type and number must be mentioned in the request as they are mandatory elements.

Below is an example of search criteria: FOID and Date of departure:

Request:




<STL:POS/>

<SearchParameters resultType="S">


<FormOfIdentification type="ID" number="9876543">


</FormOfIdentification>

</SearchParameters>


Response:













<Results>

<Success>

<System>T2</System>


</Success>

</Results>


<TT:Summary>




<TT:IssuingLocation>SYD</TT:IssuingLocation>

<TT:Reservation>OYYEEM</TT:Reservation>

<TT:FirstName>POLLY</TT:FirstName>

<TT:LastName>PASSENGER</TT:LastName>

<TT:TotalAmount currencyCode="AUD"

decimalPlace="2">1624.60</TT:TotalAmount>

</TT:Summary>

<TT:Summary>





<TT:Reservation>OYYEEM</TT:Reservation>

<TT:FirstName>CHILD</TT:FirstName>

<TT:LastName>PASSENGER</TT:LastName>

<TT:TotalAmount currencyCode="AUD"


</TT:Summary>


</soap-env:Body>


3.2.2.1.4 Search by Frequent Flyer Number

Airline customers can search and display VCR or list of VCRs by Frequent Flyer number along with

airline code or date:

o Number

o Provider

o Flight start date/date range

,

Note: Frequent flyer number must be mentioned in the request as it is a mandatory element.

Below is an example of search by Frequent Flyer number and flight start date:

Request:



<ns2:STL_Header.RQ xmlns:ns2="http://services.sabre.com/STL/v01"/>


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

<SearchParameters>


<FrequentFlyer number="100011225263" provider="U0">


</FrequentFlyer>

</SearchParameters>


Response:












<Results>

<Success>

<System>T2</System>


</Success>

</Results>


<TT:Summary>




<TT:IssuingLocation>138661</TT:IssuingLocation>

<TT:Reservation>HWBSBE</TT:Reservation>

<TT:FirstName>BEATRICE</TT:FirstName>

<TT:LastName>YORK</TT:LastName>


</TT:Summary>

<TT:Summary>




<TT:IssuingLocation>138661</TT:IssuingLocation>

<TT:Reservation>HWBSBE</TT:Reservation>

<TT:FirstName>BEATRICE</TT:FirstName>

<TT:LastName>YORK</TT:LastName>


</TT:Summary>


</soap-env:Body>



Possible Search Parameters for Travel Agent (Subscriber)

When searching for document, Travel Agent always needs to provide:

- DocumentNumber and WorkLocation

These two elements are mandatory in order to retrieve the information from Hawk database.

Currently if adding optionally LocalIssueDate to DocumentNumber and WorkLocation, the

LocalIssueDate is ignored as it is not supported by database owner.

Additional Filter for EMD refundability check

An optional field has been added to GetTicketingDocument for EMD search to check the

refund/exchangeability of the EMD to limit the search response to only those EMDs eligible for exchange.

If <n1:AdditionalFilter>EligibleForExchange</n1:AdditionalFilter> is added to the request, only

EMDs with a Y or R Refundability Indicator and at least 1 coupon open for use on a sector EMD (e.g.

seat) or all coupons open for use in case of a portion EMD (e.g. Bag) will be returned in the response.

This is supported in schema version 3.23.0 and above.

Request:

<n1:GetTicketingDocumentRQ Version="3.23.0"


xmlns:n1="http://www.sabre.com/ns/Ticketing/DC"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.sabre.com/ns/Ticketing/DC

TicketingDocumentServices_v.3.23.0.xsd">



<n1:SearchParameters resultType="S">

<n1:TicketingProvider>U0</n1:TicketingProvider>

<n1:DocumentType>EMD</n1:DocumentType>

<n1:LastName firstName="SCHULKO" lastName="STEPH" pnrLocator="THWKPR"/>

<n1:AdditionalFilter>EligibleForExchange</n1:AdditionalFilter>

</n1:SearchParameters>

</n1:GetTicketingDocumentRQ>

Examples of Web Service Calls to Search for Documents

Below there are examples of Web Service calls to search for documents with different sets of search

parameters and example of a response.

3.2.5.1 Searching by DocumentNumber - Requesting 1 DocumentNumber:

Request:





<STL:POS/>

<SearchParameters resultType="D">



</SearchParameters>


Response:













<STL:Results>

<Success>

<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent sine="EAD">



<ns2:StationLocation>XTM</ns2:StationLocation>


<ns2:WorkLocation>SEA</ns2:WorkLocation>

<ns2:Lniata>000000</ns2:Lniata>

<ns2:IsoCountryCode>US</ns2:IsoCountryCode>

<ns2:CompanyName>SABRE AIRWAYS</ns2:CompanyName>

</TT:Agent>


type="SALE">




<ns2:InputEntry>MIGRATED VCR - U0 PNR-

MCTHBL</ns2:InputEntry>


<TT:Ticket accountingCode="888" formNumber="88" number="8888888888888"

serialNumber="88888888" service="A" type="TKT">

<TT:Indicators electronic="true" historical="false" manualAdd="false"

manualUpdate="false" presentCreditCard="false" reservarionPurge="true"

retransmit="false" reverseVoid="false" selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre provider="U0" purgeDate="2013-02-

19T00:00:00">PURGED</TT:Sabre>

<ns2:OtherSystem>MCTHBL</ns2:OtherSystem>


</TT:Reservation>






<ns2:OriginCity>AUH</ns2:OriginCity>

<ns2:DestinationCity>AUH</ns2:DestinationCity>



<ns2:CouponText>FFFFFFVV</ns2:CouponText>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>ALAKHRAS/AHMAD</ns2:Name>

<ns2:FirstName>AHMAD</ns2:FirstName>

<ns2:LastName>ALAKHRAS</ns2:LastName>

<ns2:PassengerType>ADT</ns2:PassengerType>

</TT:Traveler>

</TT:Customer>

<ns2:Affinity>

<ns2:FrequentFlyer>

<ns2:Provider>U0</ns2:Provider>

<ns2:Number>9VE8526</ns2:Number>

</ns2:FrequentFlyer>

</ns2:Affinity>





<ns2:OperatingProvider>BA</ns2:OperatingProvider>

<ns2:ClassOfService>S</ns2:ClassOfService>

<ns2:FareBasis>SLRCME</ns2:FareBasis>

<TT:StartLocation>AUH</TT:StartLocation>


<TT:EndLocation>LHR</TT:EndLocation>

<ns2:NotValidBeforeDate>2008-11-26</ns2:NotValidBeforeDate>

<ns2:NotValidAfterDate>2008-11-26</ns2:NotValidAfterDate>



<ns2:Affinity>

<ns2:FrequentFlyer>




</ns2:Affinity>

<ns2:Indicators fareBreak="false"/>

<ns2:ValidatingProvider>U0</ns2:ValidatingProvider>

<ns2:StartTimeText>235A</ns2:StartTimeText>

</TT:ServiceCoupon>







<TT:StartLocation>LHR</TT:StartLocation>



<TT:EndLocation>ORD</TT:EndLocation>





<ns2:Affinity>

<ns2:FrequentFlyer>




</ns2:Affinity>

<ns2:StopOver>X</ns2:StopOver>




</TT:ServiceCoupon>







<TT:StartLocation>ORD</TT:StartLocation>


<TT:EndLocation>CMH</TT:EndLocation>





<ns2:Affinity>

<ns2:FrequentFlyer>




</ns2:Affinity>





</TT:ServiceCoupon>







<TT:StartLocation>CMH</TT:StartLocation>


<TT:EndLocation>ORD</TT:EndLocation>





<ns2:Affinity>

<ns2:FrequentFlyer>





</ns2:Affinity>




</TT:ServiceCoupon>







<TT:StartLocation>ORD</TT:StartLocation>


<TT:EndLocation>DME</TT:EndLocation>





<ns2:Affinity>

<ns2:FrequentFlyer>




</ns2:Affinity>





</TT:ServiceCoupon>





<ns2:ClassOfService>K</ns2:ClassOfService>


<TT:StartLocation>DME</TT:StartLocation>


<TT:EndLocation>AUH</TT:EndLocation>





<ns2:Affinity>

<ns2:FrequentFlyer>




</ns2:Affinity>





</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>


<ns2:Base>




</ns2:Base>

<TT:Total>

<ns2:Amount currencyCode="USD" decimalPlace="2">0.00</ns2:Amount>

<ns2:Text>NO ADC</ns2:Text>


</TT:Total>

<ns2:Tax code="US" exempt="false" sequence="1">




</ns2:Tax>

<ns2:Tax code="AY" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="AE" exempt="false" sequence="3">




</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="US" exempt="false" sequence="1" status="N">




</ns2:Tax>

<ns2:Tax code="AY" exempt="false" sequence="2" status="N">




</ns2:Tax>

<ns2:Tax code="AE" exempt="false" sequence="3" status="N">




</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements sequence="1">CONDITIONS APPLY/NON ENDORS/VALID U0 ONLY

C01-02</ns2:Endorsements>

<ns2:Payment sequence="1">AX0012147335901000</ns2:Payment>

<ns2:OriginalIssue sequence="1">12SEP08SEA45107355E</ns2:OriginalIssue>

</TT:Remark>


<TT:Booking sine="AAS">

<ns2:WorkLocation>XTM</ns2:WorkLocation>

</TT:Booking>




<ns2:New>AUH U0 X/LON U0 X/E/CHI U0 CMH M387.54SLRCME U0 X/E/CHI U0 X/MOW

U0 AUH M387.54SLRCME NUC775.08END ROE3.67299 XFORD4.5CMH4.5ORD4.5

PD34.70UB16.60RI6.30UH230.00YQ5.50YC7.00XY5.00XA13.50XF</ns2:New>



<ns2:Conjunctive sequence="1">


</ns2:Conjunctive>

<TT:Original sequence="0">


<ns2:Payment>MS EFAX0012147335901000</ns2:Payment>



<ns2:IssueCity>SEA</ns2:IssueCity>


</TT:Original>

<TT:Exchange sequence="1">


<ns2:Payment>MS EFAX0012147335901000</ns2:Payment>

<ns2:CheckDigit>/</ns2:CheckDigit>



<ns2:IssueCity>SEA</ns2:IssueCity>

<ns2:Remark>8888888888888/1</ns2:Remark>

</TT:Exchange>


<TT:Payment sequence="1" type="CC">

<TT:Tax>

<TT:Amount currencyCode="USD" decimalPlace="2">0.00</TT:Amount>


</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>AX0012147335901000</ns2:Remarks>

<TT:Card cardType="AX">

<ns2:MaskedCardNumber>8888888888888</ns2:MaskedCardNumber>

<ns2:ExpireDate>0809</ns2:ExpireDate>

<TT:ApprovalCode>123766</TT:ApprovalCode>

<ns2:CardBinNumber>001214</ns2:CardBinNumber>

</TT:Card>

</TT:Payment>


<TT:Agent sine="AAS">


<ns2:WorkLocation>SEA</ns2:WorkLocation>

<ns2:HomeLocation>U0</ns2:HomeLocation>

</TT:Agent>




<ns2:InputMessage>MIGRATED VCR - U0 PNR-

MCTHBL</ns2:InputMessage>


<TT:Details>



<ns2:OldReservation>PURGED</ns2:OldReservation>


</TT:Details>



















</TT:History>

</TT:Ticket>

</TT:Details>


3.2.5.2 Searching by DocumentNumber – Requesting Multiple Documents in One Transaction.

Request:




<STL:POS/>





</SearchParameters>


3.2.5.3 Searching by DocumentNumber and LocalIssueDate

Request:




<STL:POS/>



<DocumentNumber localIssueDate="2009-02-17">8888888888888</DocumentNumber>

</SearchParameters>



3.2.5.4 Searching by DocumentNumber and WorkLocation

Request:




<STL:POS/>



<DocumentNumber workLocation="AUH">8888888888888</DocumentNumber>

</SearchParameters>


3.2.5.5 Searching by DocumentNumber and LocalIssueDate and WorkLocation

Request:




<STL:POS/>



<DocumentNumber workLocation="AUH" localIssueDate="2009-02-

17">8888888888888</DocumentNumber>

</SearchParameters>


3.2.5.6 Searching by FrequentFlyer

Request:




<STL:POS/>

<SearchParameters>


<FrequentFlyerNumber>C95X692</FrequentFlyerNumber>

</SearchParameters>


3.2.5.7 Searching by DocumentType and FrequentFlyer

Request:





<STL:POS/>

<SearchParameters>


<DocumentType>TKT</DocumentType>

<FrequentFlyerNumber>C95X692</FrequentFlyerNumber>

</SearchParameters>


3.2.5.8 Searching by LastName

Request:




<STL:POS/>

<SearchParameters>


<LastName lastName="KULAK"/>

</SearchParameters>


3.2.5.9 Searching by LastName and FirstName

Request:




<STL:POS/>

<SearchParameters>


<LastName lastName="KULAK" firstName="JAN"/>

</SearchParameters>


3.2.5.10 By LastName and Reservation (PNR locator)

Request:




<STL:POS/>

<SearchParameters resultType="A">


<LastName lastName="KOWALSKI" pnrLocator="MAKKGC"/>

</SearchParameters>



3.2.5.11 By LastName and WorkLocation

Request:




<STL:POS/>



<LastName lastName="KOWALSKI" workLocation="ETC"/>

</SearchParameters>


3.2.5.12 Searching by LastName and LocalIssueDate

Request:




<STL:POS/>



<LastName lastName="KOWALSKI">

<LocalIssueDate>2014-02-12</LocalIssueDate>

</LastName>

</SearchParameters>


3.2.5.13 Searching by LastName and LocalIssueDateRange

Request:




<STL:POS/>



<LastName lastName="KOWALSKI">

<LocalIssueDateRange afterDate="2014-02-11" beforeDate="2014-02-13"/>

</LastName>

</SearchParameters>


3.2.5.14 Searching byDocumentType and LastName

Request:





<STL:POS/>

<SearchParameters>



<LastName lastName="KULAK"/>

</SearchParameters>


3.2.5.15 Searching by DocumentType and LastName and FirstName

Request:




<STL:POS/>

<SearchParameters>



<LastName lastName="KULAK" firstName="JAN"/>

</SearchParameters>


3.2.5.16 Searching by DocumentType and LocalIssueDate and WorkLocation

Request:




<STL:POS/>

<SearchParameters>



<LocalIssueDate workLocation="ETC">2014-03-03</LocalIssueDate>

</SearchParameters>


3.2.5.17 Searching by LocalIssueDate and WorkLocation

Request:




<STL:POS/>

<SearchParameters>


<LocalIssueDate workLocation="ETC">2014-03-03</LocalIssueDate>

</SearchParameters>



3.2.5.18 Searching by Reservation

Request:




<STL:POS/>

<SearchParameters>


<Reservation pnrLocator="IGKKDN"/>

</SearchParameters>


3.2.5.19 Searching by Reservation and CreateDate

Request:




<STL:POS/>

<SearchParameters>


<Reservation pnrLocator="IGKKDN" pnrCreateDate="2014-03-03"/>

</SearchParameters>


3.2.5.20 By Reservation (PNR locator) and WorkLocation

Request:




<STL:POS/>



<Reservation pnrLocator="MAKKGC" workLocation="ETC"/>

</SearchParameters>


3.2.5.21 By Reservation (PNR locator) and LocalIssueDate

Request:





<STL:POS/>



<Reservation pnrLocator="MAKKGC">


</Reservation>

</SearchParameters>


3.2.5.22 By Reservation (PNR locator) and LocalIssueDateRange

Request:




<STL:POS/>



<Reservation pnrLocator="MAKKGC">

<LocalIssueDateRange afterDate="2014-02-11" beforeDate="2014-02-13"/>

</Reservation>

</SearchParameters>


A Real Status of Interline Coupons

Starting from schema version 3.3.0 the TicketingDocumentServiceRQ (TktDoc) Web Service allows to

check real status of interline coupons of an electronic air ticket (VCR). Currently this option is available

for Airline Customers.

To use this option an User has to demand it by setting an attribute fetchInterlineCouponStatus with value

true with details (D) or custom details (C) result type and provide required Point Of Sale (POS)

information such as:

o Pseudo – The work location of an Agent who sends a TktDoc request – in case of a request from

Airline this is going to be 3 character ATA/IATA airport/city code.

o Actual – 3 character ATA/IATA airport/city code – in case of a request coming from Airline this is

the Work Location of an Agent who sends the request (same as in Pseudo).

o Sine – Identifies the agent or party within the requesting entity.

Request




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

<STL:Pseudo>MOW</STL:Pseudo>

<STL:Actual>MOW</STL:Actual>

<STL:Sine>ET3</STL:Sine>

</STL:POS>


<SearchParameters fetchInterlineCouponStatus="true" resultType="D"

warnOnDuplication="ERROR">



</SearchParameters>


A real status of an interline coupon will be placed under the attribute

CurrentControllingProvider/@currentStatus and a status from T2 database is placed under the

CurrentStatus element.

Response:













<STL:Results>

<Success>

<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="5" sine="WBT" type="KSK">



<ns2:StationLocation>ETCHQ</ns2:StationLocation>


<ns2:WorkLocation>ETC</ns2:WorkLocation>

<ns2:HomeLocation>RKT</ns2:HomeLocation>

<ns2:Lniata>5DE520</ns2:Lniata>




<ns2:ShiftStartDateTime>2014-02-03T02:18:09.000</ns2:ShiftStartDateTime>

<ns2:Session>

<ns2:AgentOpenType>DCP</ns2:AgentOpenType>

<ns2:StationOpenType>DCP</ns2:StationOpenType>

</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:LocalDateTime>2014-02-03T02:18:09.000</ns2:LocalDateTime>

<ns2:SystemDateTime>2014-02-03T04:18:09.000</ns2:SystemDateTime>


<ns2:InputEntry>W$VCR$FCA</ns2:InputEntry>









selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2014-02-03T00:00:00.000"

provider="U0">DBAXHM</TT:Sabre>

</TT:Reservation>

<ns2:SystemCreateDateTime>2014-02-

03T04:18:00.000</ns2:SystemCreateDateTime>


03T02:18:09.000</TT:LocalIssueDateTime>

<ns2:LastUpdate>2014-02-03T04:18:00.000</ns2:LastUpdate>



<ns2:OriginCity>LHR</ns2:OriginCity>








<ns2:ExceptionType>D</ns2:ExceptionType>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>KOWALSKI/JAN</ns2:Name>

<ns2:FirstName>JAN</ns2:FirstName>

<ns2:LastName>KOWALSKI</ns2:LastName>


<ns2:Contact>


</ns2:Contact>

</TT:Traveler>

</TT:Customer>





<ns2:ClassOfService>Y</ns2:ClassOfService>

<ns2:FareBasis>YOW</ns2:FareBasis>


<ns2:StartDateTime>2014-04-04T09:40:00.000</ns2:StartDateTime>


<ns2:EndDateTime>2014-04-04T19:35:00.000</ns2:EndDateTime>





<ns2:CurrentControllingProvider currentStatus="OK"

hosted="false">BA</ns2:CurrentControllingProvider>




<ns2:Indicators fareBreak="true" sideTripEnd="false"



<ns2:FareBreakAmount>

<ns2:Amount currencyCode="NUC" decimalPlace="2">1590.19</ns2:Amount>


</ns2:FareBreakAmount>

<TT:FareComponent IATAAuthorisedIndicator="false"

appendNonrefundableIndicator="false" flownIndicator="false"

inboundIndicator="false" oneWayDirectionalIndicator="false"

oneWayIndicator="false" roundTripIndicator="false" sequence="1">

<ns2:AssociatedFareBasis>YOW</ns2:AssociatedFareBasis>

<TT:FareProvider>BA</TT:FareProvider>

<ns2:Tariff>22</ns2:Tariff>

<ns2:FareRule>2201</ns2:FareRule>

<ns2:PricingVendor>ATP</ns2:PricingVendor>

</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base>

<ns2:Amount currencyCode="GBP" decimalPlace="2">971.00</ns2:Amount>


</ns2:Base>

<ns2:Equivalent>




</ns2:Equivalent>

<TT:Total>



</TT:Total>





</ns2:Tax>

<ns2:Tax code="GB" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="XT" exempt="false" sequence="3">




</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NUC>


<ns2:RateOfExchange decimalPlace="9">0.610616000</ns2:RateOfExchange>

</ns2:NUC>

</TT:Other>

</TT:Amounts>


<TT:Taxes>

<TT:New>

<ns2:Tax code="YQF" exempt="false" sequence="1">




</ns2:Tax>

<ns2:Tax code="GB6" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="UB6" exempt="false" sequence="3">




</ns2:Tax>

<ns2:Tax code="ZR" exempt="false" sequence="4">




</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>


</TT:Remark>


<TT:Booking duty="5" sine="WBT">




</TT:Booking>



<ns2:New>LON BA AUH1590.19NUC1590.19END ROE0.610616</ns2:New>


<TT:PrintCoupon couponType="P" printerType="0" quantity="0" stockType="2A">

<ns2:Lniata>BBCA78</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>



</TT:Base>

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>



</TT:Payment>







</TT:Agent>







<TT:Details>


<ns2:OldReservation>DBAXHM</ns2:OldReservation>

</TT:Details>

</TT:History>


<TT:Agent duty="5" sine="WBT">




</TT:Agent>




<ns2:InputMessage>UNSOL CTRL TO BA</ns2:InputMessage>


<TT:Details>




</TT:Details>




<ns2:CurrentControllingProvider>BA</ns2:CurrentControllingProvider>


</TT:History>






</TT:Agent>




<ns2:InputMessage>W$VCR$FCA</ns2:InputMessage>


<TT:Details>




</TT:Details>





</TT:History>

</TT:Ticket>

</TT:Details>


In case of an error with getting the status of an interline coupon a warning message is generated. The data

received from T2 database are not changed.

An example of a response with a warning message in case of abbreviated result type:













<STL:Results>

<Success>

<System>T2</System>


</Success>

<STL:Warning status="Incomplete" type="Application">




<STL:ErrorMessage code="19609">Unable to verify interline coupon status:

change response type to 'D' - details or 'C' - custom

details</STL:ErrorMessage>

<STL:ShortText>Unable to verify interline coupon status: change response

type to 'D' - details or 'C' - custom details</STL:ShortText>


</STL:Warning>

</STL:Results>


<TT:Abbreviated>









<ns2:Session>



</ns2:Session>

</TT:Agent>

<TT:TicketingDocument accountingCode="888" checkDigit="5" formNumber="88"

number="8888888888888" serialNumber="88888888" type="TKT">


<ns2:Indicators electronic="true" manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:Sabre provider="U0">DBAXHM</ns2:Sabre>

</ns2:Reservation>

<TT:LocalIssueDateTime>2014-02-03T02:18:09.000</TT:LocalIssueDateTime>

</TT:Details>

<ns2:Customer>

<TT:Traveler>





</TT:Traveler>

</ns2:Customer>






<ns2:StartLocation>LHR</ns2:StartLocation>


<ns2:EndLocation>AUH</ns2:EndLocation>




<ns2:Payment sequence="1" type="CA"/>


</TT:Abbreviated>


An example of a response with a warning message in case of timeout from an external reservation system:













<STL:Results>

<Success>

<System>T2</System>


</Success>






<STL:ErrorMessage code="19611">Unable to verify interline coupon status

for ticket 8882121855966 and coupon 1: communication

timeout</STL:ErrorMessage>

<STL:ShortText>Unable to verify interline coupon status for ticket

8882121855966 and coupon 1</STL:ShortText>


</STL:Warning>

</STL:Results>


<TT:Details>








<ns2:Lniata>5DE520</ns2:Lniata>




<ns2:ShiftStartDateTime>2014-02-03T02:18:09.000</ns2:ShiftStartDateTime>

<ns2:Session>



</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:LocalDateTime>2014-02-03T02:18:09.000</ns2:LocalDateTime>



<ns2:InputEntry>W$VCR$FCA</ns2:InputEntry>








selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2014-02-03T00:00:00.000"

provider="U0">DBAXHM</TT:Sabre>

</TT:Reservation>


03T04:18:00.000</ns2:SystemCreateDateTime>



<ns2:LastUpdate>2014-02-03T04:18:00.000</ns2:LastUpdate>



<ns2:OriginCity>LHR</ns2:OriginCity>










</TT:Details>

<TT:Customer>

<TT:Traveler>





<ns2:Contact>


</ns2:Contact>

</TT:Traveler>

</TT:Customer>










<ns2:EndDateTime>2014-04-04T19:35:00.000</ns2:EndDateTime>






hosted="false">BA</ns2:CurrentControllingProvider>














<ns2:AssociatedFareBasis>YOW</ns2:AssociatedFareBasis>

<TT:FareProvider>BA</TT:FareProvider>




</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base>

<ns2:Amount currencyCode="GBP" decimalPlace="2">971.00</ns2:Amount>



</ns2:Base>

<ns2:Equivalent>




</ns2:Equivalent>

<TT:Total>



</TT:Total>





</ns2:Tax>

<ns2:Tax code="GB" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="XT" exempt="false" sequence="3">




</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NUC>



</ns2:NUC>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="YQF" exempt="false" sequence="1">




</ns2:Tax>

<ns2:Tax code="GB6" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="UB6" exempt="false" sequence="3">




</ns2:Tax>

<ns2:Tax code="ZR" exempt="false" sequence="4">




</ns2:Tax>

</TT:New>


</TT:Taxes>

<TT:Remark>


</TT:Remark>


<TT:Booking duty="5" sine="WBT">




</TT:Booking>



<ns2:New>LON BA AUH1590.19NUC1590.19END ROE0.610616</ns2:New>



<ns2:Lniata>BBCA78</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>



</TT:Base>

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>



</TT:Payment>






</TT:Agent>







<TT:Details>



</TT:Details>

</TT:History>






</TT:Agent>





<ns2:InputMessage>UNSOL CTRL TO BA</ns2:InputMessage>


<TT:Details>




</TT:Details>




<ns2:CurrentControllingProvider>BA</ns2:CurrentControllingProvider>


</TT:History>






</TT:Agent>




<ns2:InputMessage>W$VCR$FCA</ns2:InputMessage>


<TT:Details>




</TT:Details>




</TT:History>

</TT:Ticket>

</TT:Details>


Duplicated Document Numbers

If a document number is duplicated in the T2 database the latest document is returned. Starting from

schema version 3.3.0, a Client can change the default behavior by using a warnOnDuplication attribute for

the SearchParameters element and set it to one of below values:

LATEST - response includes the latest document in requested format without indicating there is

any duplication. If multiple document numbers are requested, all of them are returned in requested

format with same "latest" selection rule.

ERROR - response includes an error and a warning indicating duplicated document number, date

of issue and passenger first and last name. If multiple document numbers are requested, none is

returned.

WARNING - response includes the latest document in requested format and a warning indicating

duplicated document number, date of issue and passenger first and last name. If multiple


document numbers are requested, all of them are returned in requested format and separate

warning indicates each duplication.

SUMMARY - response includes all duplicate documents in summary format – the resultType

attribute is ingnored – and a warning indicating duplicated document number, date of issue and

passenger first and last name. If multiple document numbers are requested all of them are returned

in summary format.

ALL - response includes all duplicate documents in requested format and a warning indicating

duplicated document number, date of issue and passenger first and last name. If many document

numbers are requested all of them are returned in requested format.

An example of a request with the warnOnDuplication attribute set to ERROR:





<STL:Pseudo>MOW</STL:Pseudo>

<STL:Actual>MOW</STL:Actual>

<STL:Sine>ET3</STL:Sine>

</STL:POS>

<SearchParameters resultType="A" warnOnDuplication="ERROR">



</SearchParameters>


An example of a response for duplicated document with the ERROR:













<STL:Results>

<Error status="Incomplete" type="BusinessLogic">


<System>T2</System>

<SystemSpecificResults>

<ErrorMessage>One or more documents are duplicate. Please refine your

search criteria and request again</ErrorMessage>

<ShortText>DUPLICATE</ShortText>

</SystemSpecificResults>

</Error>

<Warning status="Incomplete" type="BusinessLogic">

<System>T2</System>


<ErrorMessage>There are 5 documents with number 8888888888888 issued on

different dates for different passengers. No documents are returned. Please














<STL:Results>

<Success>

<System>T2</System>


</Success>

<Warning status="Complete" type="BusinessLogic">

<System>T2</System>



different dates for different passengers. All documents are returned. Please



<ShortText>DUPLICATE|SUMMARY|S|8884570011718|2013-02-

25|SECOND|PAX</ShortText>


</Warning>


<System>T2</System>









</Warning>


<System>T2</System>







01|TEST|U0</ShortText>


</Warning>


<System>T2</System>








30|CHINTU|VERMA</ShortText>


</Warning>


<System>T2</System>









</Warning>

</STL:Results>


<TT:Summary>



<TT:DocumentType>EMD</TT:DocumentType>

<TT:IssuingLocation>WD40</TT:IssuingLocation>

<TT:Reservation>FVHZQE</TT:Reservation>

<TT:FirstName>SECOND</TT:FirstName>

<TT:LastName>PAX</TT:LastName>


</TT:Summary>

<TT:Summary>





<TT:Reservation>RTZGZI</TT:Reservation>

<TT:FirstName>KAROLINA</TT:FirstName>

<TT:LastName>MENTLEWICZ</TT:LastName>


</TT:Summary>

<TT:Summary>





<TT:Reservation>SDFMBS</TT:Reservation>

<TT:FirstName>TEST</TT:FirstName>

<TT:LastName>U0</TT:LastName>


</TT:Summary>

<TT:Summary>





<TT:Reservation>IUNIGL</TT:Reservation>

<TT:FirstName>CHINTU</TT:FirstName>

<TT:LastName>VERMA</TT:LastName>


</TT:Summary>


<TT:Summary>





<TT:Reservation>EGORKQ</TT:Reservation>

<TT:FirstName>KAROLINA</TT:FirstName>

<TT:LastName>MENTLEWICZ</TT:LastName>


</TT:Summary>


Status of Hosted Validating Carrier Coupons

Starting from schema version 3.10.0 the TicketingDocumentServiceRQ (TktDoc) Web Service allows

Travel Network customers to fetch the coupon status from the validating Carrier database in case the

Validating Carrier is different from the TicketingProvider and the Validation Carrier is Sabre hosted. .

To use this option a User has to set the attribute fetchValidatingProviderCouponStatus with value true with

details (D) or custom details (C) result type. There is no guarantee that the stauts will be fetched or will

not change.

An example of a request with custom result type:

<GetTicketingDocumentRQ Version="3.10.0"

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

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

<STL:OrchestrationID seq="0">TKTHLI702-16505-1836957550-1446826430782-211-

arex</STL:OrchestrationID>

</STL:STL_Header.RQ>


<STL:Company>1S</STL:Company>

<STL:Pseudo>DR93</STL:Pseudo>

</STL:POS>

<SearchParameters fetchValidatingProviderCouponStatus="true" resultType="C"

warnOnDuplication="ERROR">



<CustomResponseDetails>Customer</CustomResponseDetails>

<CustomResponseDetails>FlownServiceCoupon</CustomResponseDetails>

<CustomResponseDetails>ServiceCoupon</CustomResponseDetails>

<CustomResponseDetails>Amounts</CustomResponseDetails>

<CustomResponseDetails>Taxes</CustomResponseDetails>

<CustomResponseDetails>FareCalculation</CustomResponseDetails>


</SearchParameters>


Example of response:





tktdoc" timeStamp="2015-11-06T10:13:51"



xmlns="http://services.sabre.com/STL/v01">TKTHLI702-16505-1836957550-

1446826430782-211-arex</OrchestrationID>

<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:CustomDetails>

<TT:Agent duty="*" sine="ATW">

<ns2:TicketingProvider checkDigit="0" name="SABRE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1S</ns2:TicketingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">HEL</ns2:StationLocation>

<ns2:StationNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">19209875</ns2:StationNumber>

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DR93</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DR93</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">757A68</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FI</ns2:IsoCountryCode>

<ns2:IataNumber


<ns2:CompanyName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MR.

TRAVEL</ns2:CompanyName>

<ns2:ShiftStartDateTime


27T17:55:00</ns2:ShiftStartDateTime>

</TT:Agent>


type="SALE">

<ns2:TCN

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">14323644906</ns2:TCN>

<ns2:LocalDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

10-27T17:55:00</ns2:LocalDateTime>

<ns2:SystemDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

10-27T10:55:00</ns2:SystemDateTime>

<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1S</ns2:SystemProvider>

<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$FCA$KP3$U0A+</ns2:InputEntr

y>





<TT:Indicators electronic="true" selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2015-10-27T00:00:00" provider="U0"

purgeDate="2015-11-26T00:00:00">EOVGMZ</TT:Sabre>

</TT:Reservation>







<ns2:LastUpdate xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-10-

27T17:55:00</ns2:LastUpdate>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:ValidatingProvider>

<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DFW</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DFW</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">I</ns2:ExchCategory>

<ns2:TicketingMode




<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FFFF</ns2:CouponText>

</TT:Details>

<TT:Customer>

<TT:Traveler nameId="1" nameNumber="1.1">

<ns2:Name xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DUNCE/GEORGE

MR</ns2:Name>

<ns2:FirstName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GEORGE

MR</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DUNCE</ns2:LastName>

<ns2:PassengerType

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADT</ns2:PassengerType>

</TT:Traveler>

</TT:Customer>


<ns2:MarketingProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:MarketingProvider>



er>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:OperatingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2213</ns2:OperatingFlightNumb

er>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y</ns2:ClassOfService>


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YA2AA</ns2:FareBasis>

<TT:StartLocation>DFW</TT:StartLocation>

<ns2:StartDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

11-20T06:40:00</ns2:StartDateTime>

<TT:EndLocation>LGA</TT:EndLocation>

<ns2:EndDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

11-20T10:52:00</ns2:EndDateTime>




<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:ValidatingProviderCouponStatus hosted="true" provider="U0"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OK</ns2:ValidatingProviderCou

ponStatus>

<ns2:Reservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">EOVGMZ</ns2:Reservation>

<ns2:BagAllowance

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">NIL</ns2:BagAllowance>

<ns2:BookingDate xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

10-27</ns2:BookingDate>

<ns2:CouponUse


<ns2:Indicators connectionOverride="false" fareBreak="true"

sideTripEnd="false" sideTripStart="false" unchargeableSurface="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"/>

<ns2:FareBreakAmount xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">




<ns2:PlusUp code="Q" sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">


</ns2:PlusUp>




</ns2:PlusUp>

</TT:ServiceCoupon>






er>





er>

<ns2:ClassOfService


<ns2:FareBasis



<TT:StartLocation>LGA</TT:StartLocation>



<TT:EndLocation>DFW</TT:EndLocation>






<ns2:BookingStatus


<ns2:CurrentStatus




ponStatus>

<ns2:Reservation


<ns2:BagAllowance




<ns2:StopOver

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">O</ns2:StopOver>

<ns2:CouponUse












</ns2:PlusUp>

</TT:ServiceCoupon>






er>





er>

<ns2:ClassOfService


<ns2:FareBasis












<ns2:BookingStatus


<ns2:CurrentStatus




ponStatus>

<ns2:Reservation


<ns2:BagAllowance




<ns2:StopOver


<ns2:CouponUse












</ns2:PlusUp>

</TT:ServiceCoupon>






er>





er>

<ns2:ClassOfService


<ns2:FareBasis












<ns2:BookingStatus


<ns2:CurrentStatus




ponStatus>

<ns2:Reservation


<ns2:BagAllowance




<ns2:StopOver


<ns2:CouponUse












</ns2:PlusUp>




</ns2:PlusUp>

</TT:ServiceCoupon>






er>





er>

<ns2:ClassOfService


<ns2:FareBasis












<ns2:BookingStatus


<ns2:CurrentStatus




ponStatus>

<ns2:Reservation


<ns2:BagAllowance




<ns2:StopOver


<ns2:CouponUse












</ns2:PlusUp>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>




</ns2:Base>

<ns2:Equivalent xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



<ns2:CurrencyConversion>

<ns2:BankerSellingRate

decimalPlace="8">1.10156422</ns2:BankerSellingRate>

</ns2:CurrencyConversion>

</ns2:Equivalent>

<ns2:TotalTax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



</ns2:TotalTax>

<TT:Total>

<ns2:Amount currencyCode="EUR" decimalPlace="2"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">7907.72</ns2:Amount>

<ns2:Text


</TT:Total>


<ns2:Tax code="US" sequence="1" status="N"




</ns2:Tax>

<ns2:Tax code="ZP" sequence="2" status="N"




</ns2:Tax>

<ns2:Tax code="XT" sequence="3" status="N"




</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:Commission xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



</ns2:Commission>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="US" exempt="false" sequence="1" status="N"





</ns2:Tax>

<ns2:Tax code="ZP" exempt="false" sequence="2" status="N"





</ns2:Tax>

<ns2:Tax code="AY" exempt="false" sequence="3" status="N"





</ns2:Tax>

<ns2:Tax code="XF" exempt="false" sequence="4" status="N"





</ns2:Tax>

</TT:New>

</TT:Taxes>


<ns2:New>DFW U0 NYC Q27.91Q18.60 1301.40U0 DFW Q27.91 1301.40U0 NYC

Q27.91 1301.40U0 DFW Q27.91Q18.601301.40U0 NYC Q27.91Q18.60 1301.40U0 DFW

Q27.91 1301.40USD8031.66END ZPDFWLGADFWLGADFWLGA

XFDFW4.5LGA4.5DFW4.5LGA4.5</ns2:New>




<ns2:Conjunctive sequence="1"



</ns2:Conjunctive>


</TT:Ticket>

</TT:CustomDetails>


Net Tickets and Net Remit Tickets

Starting from schema version 3.11.0 the TicketingDocumentServiceRQ (TktDoc) Web Service will return

Net Type information in the response when available. This will allow manual and automated net remit

tickets as well as CAT35 net tickets to be identified.

The net type information will be available in this element:

GetTicketingDocumentRS/Details/Ticket/Details/NetType

Possible values for NetType are M, A and T are as follows:

M – Manual net remit

A – Automated net remit

T – Net ticket

Here is an example of a response for a manual net remit ticket:

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2016-02-26T00:00:00" provider="U0" purgeDate="2016-05-

20T00:00:00">NSBISE</TT:Sabre>

</TT:Reservation>











<ns2:OriginCity



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">LGA</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">I</ns2:ExchCategory>

<ns2:TicketingMode





<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FVVV</ns2:CouponText>

<ns2:CurrentActivity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">N</ns2:CurrentActivity>

<TT:BaggageDisclosure disclosureIndicator="3"/>

<ns2:NetType xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">M</ns2:NetType>

</TT:Details>

3.2.10 NDC Documents

NDC Documents will be retrieved from tktdoc in a similar way as we retrieve documents issued through

traditional path. New NDC fields are being added in the ticketing document response:

OfferType: This field displays the type of document based on transaction. It will display “NDC” for NDC

documents. “ATPCONormalisation” for ATPCO documents and “LCCNormalisation” for LCC documents.

SabreOrderID: This will have the OrderID of the hosted carriers and 1S OrderID in case of TN copy of the

document.

OtherOrderID: This is relevant only for subscribers. This field will have the airline OrderID in TN copy of

the document.

SabreOrderItemID: This field will display the OrderItemID of the airlines for both hosted and 1S

documents.

SabreServiceID: This field will display the ServiceID of the airlines for both hosted and 1S documents.

These fields will be displayed in all different types of response, namely, detail, custom, abbreviated and

summary.

Note: SabreServiceID will not be displayed in summary search.

Below is the detailed response structure of an NDC TKT document:

RS

<ns2:GetTicketingDocumentRS xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

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

<STL_Header.RS messageID="TKTHLI702-31419-1705008183-

1532874146359-2053">

<OrchestrationID seq="1">TKTHLI702-14862-

992514931-1532874146061-2-tktdoc</OrchestrationID>


<Results>

<Success>

<System>T2</System>


</Success>

</Results>

</STL_Header.RS>

<ns2:Ticketing>

<ns2:Agent sine="ATW">



checkDigit="4" name="AA DO NOT TKT" number="795">VA</ns2:TicketingProvider>

<ns2:StationLocation>LYS</ns2:StationLocation>

<ns2:WorkLocation>L27F</ns2:WorkLocation>

<ns2:HomeLocation>LYS</ns2:HomeLocation>

<ns2:Lniata>F2F720</ns2:Lniata>

<ns2:IsoCountryCode>FR</ns2:IsoCountryCode>


<ns2:CompanyName>CWT</ns2:CompanyName>

<ns2:ExtdWorkLocation>L27F</ns2:ExtdWorkLocation>

</ns2:Agent>

<ns2:TransactionInfo category="C" sequence="1"

type="SALE">

<ns2:LocalDateTime>2018-02-


<ns2:SystemDateTime>2018-02-


<ns2:SystemProvider>1W</ns2:SystemProvider>

<ns2:InputEntry>CREATED BY

1W</ns2:InputEntry>

</ns2:TransactionInfo>

<ns2:TicketingDocument accountingCode="795"

checkDigit="1" formNumber="51" number="7955131415353"

numberOfServiceCoupons="4" serialNumber="31415353" service="A" type="EMD">

<ns2:Indicators

OBFeesIncluded="false" electronic="true" endorsable="false"

exchangeable="false" historical="false" manualAdd="false"

manualUpdate="false" netReporting="false" offerType="NDC"

penaltyRestriction="false" presentCreditCard="false"



<ns2:Details>

<ns2:Reservation>

<ns2:Sabre createDate="2018-02-16T00:00:00" provider="VA">YYATUS</ns2:Sabre>

<ns2:OtherSystem>YYASLR</ns2:OtherSystem>

</ns2:Reservation>




<ns2:ValidatingProvider checkDigit="4" name="Sabre Airways"



<ns2:AgencyBillingNumber>L27F201626</ns2:AgencyBillingNumber>

<ns2:OriginCity>LST</ns2:OriginCity>

<ns2:DestinationCity>MEL</ns2:DestinationCity>

<ns2:ItineraryType>I</ns2:ItineraryType>

<ns2:ReasonForIssue/>




<ns2:CouponText>FFFF</ns2:CouponText>

<ns2:FareCalculationPricing>0</ns2:FareCalculationPricing>

<ns2:MandateInfo

type="DataProtectionNotice">

<ns2:Text country="US" language="EN">DATA PROTECTION NOTICE: YOUR PERSONAL

DATA WILL BE PROCESSED IN ACCORDANCE WITH THE APPLICABLE CARRIER’S PRIVACY

POLICY AND, IF YOUR BOOKING IS MADE VIA A RESERVATION SYSTEM PROVIDER

(“GDS”), WITH ITS PRIVACY POLICY. THESE ARE AVAILABLE AT

HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY OR FROM THE CARRIER OR GDS DIRECTLY.

YOU SHOULD READ THIS DOCUMENTATION, WHICH APPLIES TO YOUR BOOKING AND

SPECIFIES, FOR EXAMPLE, HOW YOUR PERSONAL DATA IS COLLECTED, STORED, USED,

DISCLOSED AND TRANSFERRED. (APPLICABLE FOR INTERLINE CARRIAGE)</ns2:Text>

</ns2:MandateInfo>

<ns2:SabreOrderID provider="1S">SAB1SORDR</ns2:SabreOrderID>

<ns2:OtherOrderID provider="1S">1AOTHERORDR</ns2:OtherOrderID>

<ns2:SabreOrderItemID provider="1S">1SSABORDRITEM</ns2:SabreOrderItemID>

</ns2:Details>

<ns2:Customer>

<ns2:Traveler

nameId="1">

<ns2:Name>GUATEMALA/HEADERTEXT</ns2:Name>

<ns2:FirstName>HEADERTEXT</ns2:FirstName>

<ns2:LastName>GUATEMALA</ns2:LastName>

<ns2:Contact>


</ns2:Contact>

</ns2:Traveler>


</ns2:Customer>

<ns2:ServiceCoupon coupon="1"

entitlement="1">

<ns2:MarketingProvider checkDigit="4" name="AA DO NOT TKT"

number="795">VA</ns2:MarketingProvider>


<ns2:ClassOfService>T</ns2:ClassOfService>

<ns2:FareBasis>TZGW2</ns2:FareBasis>

<ns2:StartLocation>LST</ns2:StartLocation>


<ns2:EndLocation>MEL</ns2:EndLocation>







<ns2:Indicators




<ns2:SabreServiceID provider="1S">ServiceID0002</ns2:SabreServiceID>

Search for Historical Document

This functionality will work exactly same as the active document search except that the user will need to

provide in the request an indicator suggesting they are looking for historical tickets. TktDoc WS user can

look for tickets not older than 13 months from the date the VCRs were made historical.

Below are the different result type that will be supported-

1. Detail

2. Abbreviated


3. Summary

4. Custom

NOTE: Minimum version required for this functionality is 3.16.0 and this is applicable only for VCRs

currently.

3.3.1 Search Parameters supported for historical

The different search parameters supported for historical VCR search are same as active VCRs except for

VCR status search.

3.3.2 Historical VCR search example for different result types

3.3.1.1 Historical VCR Detail Search

Below is the example of document number search. Along with the normal request that users send for active

VCRs, a new indicator fetchHistorical="true" needs to be sent to search for historical VCRs.

Similarly in the response, user will get an indicator “historical="true” for historical VCRs.

Request:

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""

xmlns:ns1="http://www.ebxml.org/namespaces/messageHeader">

<ns1:From>

<ns1:PartyId>999999</ns1:PartyId>

</ns1:From>

<ns1:To>


</ns1:To>

<ns1:CPAId>IPCC</ns1:CPAId>

<ns1:ConversationId>ABC123</ns1:ConversationId>

<ns1:Service>TicketingDocumentServicesRQ</ns1:Service>

<ns1:Action>TicketingDocumentServicesRQ</ns1:Action>

<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>

</ns1:MessageHeader>

<ns1:Security


xmlns:ns1="http://schemas.xmlsoap.org/ws/2002/12/secext">

<ns1:BinarySecurityToken>Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS

\/STSA!ICESMSLB\/STS.LB!-

3235107072221328512!1446544!0</ns1:BinarySecurityToken>

</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<GetTicketingDocumentRQ

Version="3.16.0"


<ns1:STL_Header.RQ

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

<ns2:POS


<SearchParameters

fetchHistorical="true" resultType="D">




</SearchParameters>


</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Response:


<soap-env:Envelope

xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">

<soap-env:Header>

<eb:MessageHeader

eb:version="1.0" soap-env:mustUnderstand="1"

xmlns:eb="http://www.ebxml.org/namespaces/messageHeader">

<eb:From>

<eb:PartyId

eb:type="URI">123123</eb:PartyId>

</eb:From>

<eb:To>

<eb:PartyId


</eb:To>

<eb:CPAId>IPCC</eb:CPAId>

<eb:ConversationId>ABC123</eb:ConversationId>

<eb:Service>TicketingDocumentServicesRQ</eb:Service>

<eb:Action>TicketingDocumentServicesRQ</eb:Action>

<eb:MessageData>

<eb:MessageId>1762858482625560610</eb:MessageId>

<eb:Timestamp>2017-09-07T13:24:23</eb:Timestamp>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security

xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext">

<wsse:BinarySecurityToken

EncodingType="wsse:Base64Binary"


valueType="String">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/STSA

!ICESMSLB\/STS.LB!-3235107072221328512!1446544!0</wsse:BinarySecurityToken>

</wsse:Security>

</soap-env:Header>

<soap-env:Body>

<TT:GetTicketingDocumentRS

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




xmlns:utils="java:com.sabre.ticketing.tktdoc.utils.XsltUtils"


<STL:STL_Header.RS

messageID="TKTHLI700-875-1836008397-1504790662726-1929-tktdoc"

timeStamp="2017-09-07T08:24:22">

<OrchestrationID

seq="1">TKTHLI700-875-1836008397-1504790662726-1929-


<DiagnosticData


<STL:Results>

<Success


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent

duty="4" sine="SKV" type="ATO">




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYDAD</ns2:StationLocation>

<ns2:StationNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">99101413</ns2:StationNumber

>

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">HDQ</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">4AFD0A</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AU</ns2:IsoCountryCode>

<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Sabre

Airways</ns2:CompanyName>


<ns2:EmployeeNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0217849</ns2:EmployeeNumber

>



06T23:38:25.000</ns2:ShiftStartDateTime>

</TT:Agent>

<TT:TransactionInfo

actionType="" category="" code="" sequence="3"

type="HPUSH">

<ns2:LocalDateTime


06T23:49:33.000</ns2:LocalDateTime>

<ns2:SystemDateTime


06T08:49:33.000</ns2:SystemDateTime>

<ns2:SystemProvider


<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$F*AXXXXXXXXXXXX5550/1218*

ZX6651$VCR$ER</ns2:InputEntry>


<TT:Ticket

accountingCode="795" checkDigit="4" formNumber="21"

number="7952140588515" serialNumber="40588515" service="A"

type="TKT">

<TT:Indicators ASR="true" electronic="true"

endorsable="false" exchangeable="false" historical="true"

manualAdd="false" manualUpdate="false" netReporting="false"


refundCalculation="false" reservarionPurge="false"

retransmit="true" reverseVoid="false"

selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre

createDate="2017-09-06T00:00:00.000"

provider="U0">IOGSPK</TT:Sabre>

</TT:Reservation>




<TT:LocalIssueDateTime

useTimeForPricing="true">2017-09-


<ns2:LastUpdate



<ns2:OriginCity



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MEL</ns2:DestinationCity>

<ns2:ItineraryType


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">D</ns2:ItineraryType>

<ns2:ExchCategory

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">P</ns2:ExchCategory>



<ns2:TicketingMode




<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FFFFFFFV</ns2:CouponText>

<ns2:AccountCode


<ns2:MandateInfo


<ns2:Disclaimer

country="US"

language="EN">NOTICE

CARRIAGE AND OTHER SERVICES PROVIDED BY THE CARRIER ARE SUBJECT TO

CONDITIONS OF CARRIAGE, WHICH ARE HEREBY INCORPORATED BY REFERENCE. THESE

CONDITIONS MAY BE OBTAINED FROM THE ISSUING CARRIER. PASSENGERS ON A JOURNEY

INVOLVING AN ULTIMATE DESTINATION OR A STOP IN A COUNTRY OTHER THAN THE

COUNTRY OF DEPARTURE ARE ADVISED THAT INTERNATIONAL TREATIES KNOWN AS THE

MONTREAL CONVENTION, OR ITS PREDECESSOR, THE WARSAW CONVENTION, INCLUDING

ITS AMENDMENTS /THE WARSAW CONVENTION SYSTEM/MAY APPLY TO THE ENTIRE

JOURNEY, INCLUDING ANY PORTION THEREOF WITHIN A COUNTRY. FOR SUCH

PASSENGERS, THE APPLICABLE TREATY, INCLUDING SPECIAL CONTRACTS OF CARRIAGE

EMBODIED IN ANY APPLICABLE TARIFFS, GOVERNS AND MAY LIMIT THE LIABILITY OF

THE CARRIER. CHECK WITH YOUR CARRIER FOR MORE INFORMATION.</ns2:Disclaimer>

<ns2:HazardousMaterials

country="US"

language="EN">THE CARRIAGE OF CERTAIN HAZARDOUS MATERIALS, LIKE

AEROSOLS, FIREWORKS, AND FLAMMABLE LIQUIDS, ABOARD THE AIRCRAFT IS

FORBIDDEN. IF YOU DO NOT UNDERSTAND THESE RESTRICTIONS, FURTHER INFORMATION

MAY BE OBTAINED FROM YOUR AIRLINE.</ns2:HazardousMaterials>

</ns2:MandateInfo>

</TT:Details>

<TT:Customer>

<TT:Traveler

nameId="1">

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE/GOLD</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GOLD</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE</ns2:LastName>

<ns2:PassengerType

ordinal="231"



<ns2:Contact



</ns2:Contact>

<ns2:PricedPassengerType

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADT</ns2:PricedPassengerTyp

e>

</TT:Traveler>

</TT:Customer>

<TT:ServiceCoupon

coupon="1" entitlement="1">


name="Sabre Airways"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">800</ns2:MarketingFlightNum

ber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y</ns2:FareBasis>

<ns2:StartLocation

name="SYDNEY"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:StartLocation>

<ns2:StartDateTime


23T06:00:00.000</ns2:StartDateTime>

<ns2:EndLocation

name="MELBOURNE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MEL</ns2:EndLocation>

<ns2:EndDateTime


23T07:35:00.000</ns2:EndDateTime>

<ns2:NotValidBeforeDate


23</ns2:NotValidBeforeDate>




<ns2:BookingStatus

name="CONFIRMED"


<ns2:CurrentStatus


<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:Provider>

<ns2:Number


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">7570011066</ns2:Number>

</TT:FrequentFlyer>

</TT:Affinity>

<ns2:CouponUse


<ns2:Indicators


unchargeableSurface="false"


zeroFareAmount="false"/>

<ns2:StartTimeText


<TT:FareComponent

IATAAuthorisedIndicator="false"



oneWayIndicator="false" roundTripIndicator="false"

sequence="1">

<ns2:AssociatedFareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y</ns2:AssociatedFareBasis>

</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon






xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">5516</ns2:MarketingFlightNu

mber>





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">218</ns2:OperatingFlightNum

ber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis


<ns2:StartLocation

name="MELBOURNE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MEL</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation


name="SINGAPORE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SIN</ns2:EndLocation>

<ns2:EndDateTime









<ns2:BookingStatus

name="CONFIRMED"


<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CTRL</ns2:CurrentStatus>

<ns2:PreviousStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OK</ns2:PreviousStatus>


hosted="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:CurrentControllingP

rovider>

<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators







<ns2:StartTimeText


<TT:FareComponent





sequence="1">




</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon

coupon="3" entitlement="3" type="O">





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OPEN</ns2:MarketingFlightNu

mber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis


<ns2:StartLocation

name="SINGAPORE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SIN</ns2:StartLocation>

<ns2:EndLocation

name="MELBOURNE"


<ns2:CurrentStatus


<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators





<TT:FareComponent





sequence="1">




</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon

coupon="4" entitlement="4" type="O">





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">OPEN</ns2:MarketingFlightNu

mber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis


<ns2:StartLocation

name="MELBOURNE"


<ns2:EndLocation

name="SINGAPORE"


<ns2:CurrentStatus


<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators





<TT:FareComponent





sequence="1">




</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon







mber>





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">207</ns2:OperatingFlightNum

ber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis


<ns2:StartLocation

name="SINGAPORE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SIN</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation

name="MELBOURNE"


<ns2:EndDateTime









<ns2:BookingStatus

name="CONFIRMED"


<ns2:CurrentStatus


<ns2:PreviousStatus




hosted="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:CurrentControllingP

rovider>

<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators







<ns2:StartTimeText


<TT:FareComponent





sequence="1">



</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VA</ns2:MarketingProvider>



ber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis



<ns2:StartLocation

name="MELBOURNE"


<ns2:StartDateTime



<ns2:EndLocation

name="BRISBANE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BNE</ns2:EndLocation>

<ns2:EndDateTime









<ns2:BookingStatus

name="CONFIRMED"


<ns2:CurrentStatus


<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators





<ns2:StartTimeText


<TT:FareComponent





sequence="1">




</TT:FareComponent>

</TT:ServiceCoupon>

<TT:ServiceCoupon







ber>

<ns2:ClassOfService

name="ECONOMY"


<ns2:FareBasis


<ns2:StartLocation

name="BRISBANE"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BNE</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation

name="MELBOURNE"


<ns2:EndDateTime









<ns2:BookingStatus

name="CONFIRMED"


<ns2:CurrentStatus


<TT:Affinity>

<TT:FrequentFlyer>

<ns2:Provider


<ns2:Number


</TT:FrequentFlyer>

</TT:Affinity>

<ns2:StopOver


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">X</ns2:StopOver>

<ns2:CouponUse


<ns2:Indicators

fareBreak="true" sideTripEnd="false" sideTripStart="false"




<ns2:StartTimeText


<ns2:FareBreakAmount


<ns2:Amount

currencyCode="NUC"

decimalPlace="2">23456.78</ns2:Amount>



<TT:FareComponent





sequence="1">



</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base


<ns2:Amount

currencyCode="AUD"



</ns2:Base>

<ns2:TotalTax


<ns2:Amount

currencyCode="AUD"



</ns2:TotalTax>

<TT:Total>

<ns2:Amount

currencyCode="AUD" decimalPlace="2"


<ns2:Text


</TT:Total>

<ns2:Tax

code="YT" exempt="false" sequence="1"


<ns2:Amount


currencyCode="AUD"



</ns2:Tax>

<ns2:Tax

code="IO" exempt="false" sequence="2"


<ns2:Amount

currencyCode="AUD"



</ns2:Tax>

<ns2:Tax

code="XT" exempt="false" sequence="3"


<ns2:Amount

currencyCode="AUD"



</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NUC


<ns2:Amount

currencyCode="NUC"


<ns2:RateOfExchange

decimalPlace="6">1.330112</ns2:RateOfExchange>

</ns2:NUC>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax

code="YT" exempt="false" name="PASSENGER SERVICE CHARGE"

sequence="1">

<ns2:Amount currencyCode="AUD"

decimalPlace="2"


<ns2:Text


</TT:Tax>

<TT:Tax

code="IO" exempt="false"

name="AIRPORT BUILDING CHARGE FOR DEPARTURES"

sequence="2">


decimalPlace="2"


<ns2:Text


</TT:Tax>

<TT:Tax

code="PL" exempt="false" sequence="3">

<ns2:Amount

currencyCode="AUD" decimalPlace="2"



<ns2:Text


</TT:Tax>

<TT:Tax

code="YH" exempt="false" name="EMBARKATION TAX TEBA"

sequence="4">


decimalPlace="2"


<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements

sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">C15-

16</ns2:Endorsements>

<ns2:Payment

sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AXXXXXXXXXXXX5550

1218 X6651</ns2:Payment>

</TT:Remark>

<ns2:FareCalculation

type="70"


<ns2:New>SYD VA MEL VA SIN VA MEL VA SIN VA MEL VA X/BNE VA

MEL23456.78Y NUC23456.78END ROE1.330112</ns2:New>



<ns2:Conjunctive

sequence="1"



</ns2:Conjunctive>


<TT:PrintCoupon

couponType="P" printerType="0" quantity="0"

stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">14CC40</ns2:Lniata>

</TT:PrintCoupon>

<TT:Payment

code="2" missingPayAmtInd="false" paymentConfirmation="false"

sequence="1" type="CC">

<TT:Base>

<TT:Amount

currencyCode="AUD"

decimalPlace="2">31201.00</TT:Amount>

</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>


<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AXXXXXXXXXXXX5550</ns2:Rema

rks>

<TT:Card

accb="*" cardType="AX">

<ns2:MaskedCardNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">XXXXXXXXXXX5550</ns2:Masked

CardNumber>

<ns2:ExpireDate

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1218</ns2:ExpireDate>

<TT:ApprovalCode

type="Z">X6651</TT:ApprovalCode>

<ns2:CardBinNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">372055</ns2:CardBinNumber>

</TT:Card>

</TT:Payment>

<TT:History

code="HIST" number="59"

sequence="3">

<TT:Agent>



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VCR MOVED TO

HISTORY - NFM - 7 DAY RULE</ns2:InputMessage>


<TT:Details>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IOGSPK</ns2:OldReservation>

<ns2:CouponBitMap

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AAAAAA==</ns2:CouponBitMap>


<ns2:DocumentPurgeTypeCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">7DY</ns2:DocumentPurgeTypeC

ode>

</TT:Details>


coupon="1" sequence="1"









































</TT:History>

<TT:History

code="CTRL" number="41" sequence="2">

<TT:Agent duty="4"

sine="SKV">



<ns2:WorkLocation



<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage


SQ</ns2:InputMessage>


<TT:Details>

<ns2:OldReservation


<ns2:CouponBitMap

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SAAAAA==</ns2:CouponBitMap>



</TT:Details>






<ns2:CurrentControllingProvider>SQ</ns2:CurrentControllingProvider>







<ns2:CurrentControllingProvider>SQ</ns2:CurrentControllingProvider>


</TT:History>

<TT:History

code="OC" number="9" sequence="1">

<TT:Agent duty="4"

sine="SKV">



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage


ZX6651$VCR$ER</ns2:InputMessage>


<TT:Details>

<ns2:OldReservation


<ns2:CouponBitMap

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">/gAAAA==</ns2:CouponBitMap>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">01020304050607</ns2:Affecte

dCoupons>

</TT:Details>





































</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>


3.3.1.2 Historical VCR Summary Search

Below is the summary search scenario with Last Name, Departure and Arrival city along with flight start

date range for historical VCRs.

Along with the normal request that users send for active VCRs, a new indicator

fetchHistorical="true" needs to be sent to search for historical VCRs.

Similarly in the response, user will get an indicator “historical="true” for historical VCRs

Request:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>


<ns1:Security






</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.16.0"


<ns1:STL_Header.RQ


<ns2:POS


<SearchParameters

fetchHistorical="true"

resultType="S">


<ServiceCoupon>

<StartLocation>SYD</StartLocation>

<EndLocation>MEL</EndLocation>

<LastName

lastName="SABRE"/>

<FlightStartDateRange

afterDate="2017-08-30" beforeDate="2017-11-15"/>

</ServiceCoupon>

</SearchParameters>


</SOAP-ENV:Body>


Response:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader



<eb:From>

<eb:PartyId


</eb:From>

<eb:To>

<eb:PartyId


</eb:To>





<eb:MessageData>



</eb:MessageData>

</eb:MessageHeader>

<wsse:Security







</wsse:Security>

</soap-env:Header>

<soap-env:Body>








<STL:STL_Header.RS


timeStamp="2017-09-07T08:44:09">

<OrchestrationID

seq="1">TKTHLI700-875-1836008397-1504791849890-1975-



<Results>

<Success>

<System>T2</System>


</Success>

</Results>


<TT:Summary>

<TT:Indicators

historical="true"/>





<TT:Reservation

createDate="2017-09-06T00:00:00.000"

provider="U0">IOGSPK</TT:Reservation>

<TT:FirstName>GOLD</TT:FirstName>

<TT:LastName>SABRE</TT:LastName>

<TT:TotalAmount

currencyCode="AUD"


</TT:Summary>

<TT:Summary>

<TT:Indicators

historical="true"/>





<TT:Reservation

createDate="2017-09-06T00:00:00.000"





<TT:TotalAmount

currencyCode="AUD"


</TT:Summary>

<TT:Summary>

<TT:Indicators

historical="true"/>





<TT:Reservation

createDate="2017-09-06T00:00:00.000"




<TT:TotalAmount

currencyCode="AUD"


</TT:Summary>

<TT:Summary>

<TT:Indicators

historical="true"/>





<TT:Reservation

createDate="2017-09-06T00:00:00.000"




<TT:TotalAmount

currencyCode="AUD" decimalPlace="2">31251.50</TT:TotalAmount>

</TT:Summary>


</soap-env:Body>


3.3.1.3 Historical VCR Abbreviated Search

Below is the abbreviated search scenario with Last Name, Departure and Arrival city along with flight start

date range for historical VCRs.

Along with the normal request that users send for active VCRs, a new indicator

fetchHistorical="true" needs to be sent to search for historical VCRs.


Request



<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>


<ns1:Security





</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.16.0"


<ns1:STL_Header.RQ


<ns2:POS


<SearchParameters

fetchHistorical="true"

resultType="A">


<ServiceCoupon>

<StartLocation>SYD</StartLocation>

<EndLocation>MEL</EndLocation>

<LastName

lastName="SABRE"/>

<FlightStartDateRange

afterDate="2017-08-30" beforeDate="2017-11-15"/>

</ServiceCoupon>

</SearchParameters>


</SOAP-ENV:Body>



Response:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader



<eb:From>

<eb:PartyId


</eb:From>

<eb:To>

<eb:PartyId


</eb:To>





<eb:MessageData>



</eb:MessageData>

</eb:MessageHeader>

<wsse:Security






</wsse:Security>

</soap-env:Header>

<soap-env:Body>








<STL:STL_Header.RS


timeStamp="2017-09-07T09:13:10">

<OrchestrationID

seq="1">TKTHLI701-18013-179163446-1504793590946-1946-



<Results>

<Success>

<System>T2</System>


</Success>

</Results>



<TT:Abbreviated>

<TT:Agent

duty="4" sine="SKV"

type="ATO">


<ns2:StationLocation>SYDAD</ns2:StationLocation>


<ns2:WorkLocation>SYD</ns2:WorkLocation>



</TT:Agent>

<TT:TicketingDocument


number="7952140588521" serialNumber="40588521"

type="TKT">

<TT:Indicators electronic="true"

historical="true"

manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:Sabre

createDate="2017-09-06T00:00:00.000"

provider="U0">IOGSPK</ns2:Sabre>

</ns2:Reservation>


</TT:Details>

<ns2:Customer>

<TT:Traveler>

<ns2:Name>SABRE/GOLD</ns2:Name>

<ns2:FirstName>GOLD</ns2:FirstName>

<ns2:LastName>SABRE</ns2:LastName>

<ns2:PassengerType

ordinal="0"/>

</TT:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon

coupon="1">


name="Sabre Airways">U0</ns2:MarketingProvider>



<ns2:FareBasis>Y</ns2:FareBasis>

<ns2:StartLocation>SYD</ns2:StartLocation>





<ns2:ServiceCoupon

coupon="2">






<ns2:StartLocation>MEL</ns2:StartLocation>


<ns2:EndLocation>SIN</ns2:EndLocation>






<ns2:ServiceCoupon

coupon="3">



<ns2:MarketingFlightNumber>OPEN</ns2:MarketingFlightNumber>



<ns2:StartLocation>SIN</ns2:StartLocation>





<ns2:ServiceCoupon

coupon="4">











<ns2:ServiceCoupon

coupon="5">













<ns2:ServiceCoupon

coupon="6">








<ns2:EndLocation>BNE</ns2:EndLocation>




<ns2:ServiceCoupon

coupon="7">







<ns2:StartLocation>BNE</ns2:StartLocation>






<ns2:RelatedDocument>

<ns2:Original>



</ns2:Original>

<ns2:Exchange

sequence="1">


<ns2:CheckDigit>/</ns2:CheckDigit>


</ns2:Exchange>

</ns2:RelatedDocument>

<TT:Payment

missingPayAmtInd="true" sequence="1"

type="ET">

<TT:Base>

<TT:Amount currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>

<TT:Other/>

</TT:Payment>

<TT:Payment



<TT:Base>

<TT:Amount

currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount


currencyCode="AUD"


</TT:Total>

<ns2:Remarks>CAXXXXXXXXXXXX4444</ns2:Remarks>

<TT:Card

accb="*"

cardType="CA">

<ns2:MaskedCardNumber>XXXXXXXXXXXX4444</ns2:MaskedCardNumber>


<TT:ApprovalCode

type="Z">123456</TT:ApprovalCode>


</TT:Card>

</TT:Payment>


</TT:Abbreviated>

<TT:Abbreviated>

<TT:Agent

duty="4" sine="SKV"

type="ATO">







</TT:Agent>




type="TKT">


historical="true"

manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:Sabre

createDate="2017-09-06T00:00:00.000"


</ns2:Reservation>


</TT:Details>

<ns2:Customer>

<TT:Traveler>




<ns2:PassengerType

ordinal="231"/>

</TT:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon

coupon="1">












<ns2:ServiceCoupon

coupon="2">













<ns2:ServiceCoupon

coupon="3">











<ns2:ServiceCoupon

coupon="4">











<ns2:ServiceCoupon

coupon="5">














<ns2:ServiceCoupon

coupon="6">












<ns2:ServiceCoupon

coupon="7">












<ns2:RelatedDocument/>

<TT:Payment



<TT:Base>

<TT:Amount

currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>

<ns2:Remarks>AXXXXXXXXXXXX5550</ns2:Remarks>

<TT:Card

accb="*"

cardType="AX">

<ns2:MaskedCardNumber>XXXXXXXXXXX5550</ns2:MaskedCardNumber>


<TT:ApprovalCode



</TT:Card>

</TT:Payment>



</TT:Abbreviated>

<TT:Abbreviated>

<TT:Agent

duty="4" sine="SKV"

type="ATO">

<ns2:TicketingProvider>VA</ns2:TicketingProvider>






</TT:Agent>




type="TKT">


historical="true"

manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:Sabre

createDate="2017-09-06T00:00:00.000"


</ns2:Reservation>


</TT:Details>

<ns2:Customer>

<TT:Traveler>




<ns2:PassengerType

ordinal="231"/>

</TT:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon

coupon="1">









<ns2:CurrentStatus>EXCH</ns2:CurrentStatus>



<ns2:ServiceCoupon

coupon="2">














<ns2:ServiceCoupon

coupon="3">












<ns2:ServiceCoupon

coupon="4">












<ns2:ServiceCoupon

coupon="5">













<ns2:ServiceCoupon

coupon="6">














<ns2:ServiceCoupon

coupon="7">














<TT:Payment


sequence="1" type="CA">

<TT:Base>

<TT:Amount

currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>


<TT:Cash

CashIndicator="true"/>

</TT:Payment>


</TT:Abbreviated>

<TT:Abbreviated>

<TT:Agent

duty="4" sine="SKV"

type="ATO">







</TT:Agent>





type="TKT">


historical="true"

manualAdd="false"/>

<TT:Details>

<ns2:Reservation>

<ns2:Sabre

createDate="2017-09-06T00:00:00.000"


</ns2:Reservation>


</TT:Details>

<ns2:Customer>

<TT:Traveler>




<ns2:PassengerType

ordinal="231"/>

</TT:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon

coupon="1">











<ns2:ServiceCoupon

coupon="2">













<ns2:ServiceCoupon

coupon="3">












<ns2:ServiceCoupon

coupon="4">











<ns2:ServiceCoupon

coupon="5">













<ns2:ServiceCoupon

coupon="6">












<ns2:ServiceCoupon

coupon="7">













<TT:Payment




<TT:Base>

<TT:Amount

currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>

<ns2:Remarks>CAXXXXXXXXXXXX4444</ns2:Remarks>

<TT:Card

accb="*"

cardType="CA">

<ns2:MaskedCardNumber>XXXXXXXXXXXX4444</ns2:MaskedCardNumber>


<TT:ApprovalCode



</TT:Card>

</TT:Payment>

<TT:Payment



<TT:Base>

<TT:Amount

currencyCode="AUD"


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="AUD"


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="AUD"


</TT:Total>

<ns2:Remarks>AXXXXXXXXXXXX5550</ns2:Remarks>

<TT:Card

accb="*"

cardType="AX">



<TT:ApprovalCode type="Z">X3312</TT:ApprovalCode>


</TT:Card>

</TT:Payment>


</TT:Abbreviated>



</soap-env:Body>


3.3.1.4 Historical VCR Custom Search

Below is the example of document number search. Along with the normal request that users send for active

VCRs, a new indicator fetchHistorical="true" needs to be sent to search for historical VCRs.


Request:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>


<ns1:Security





</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.16.0"


<ns1:STL_Header.RQ


<ns2:POS



<SearchParameters

fetchHistorical="true" resultType="C">




<CustomResponseDetails>Customer</CustomResponseDetails>

</SearchParameters>


</SOAP-ENV:Body>


Response:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader



<eb:From>

<eb:PartyId


</eb:From>

<eb:To>

<eb:PartyId


</eb:To>





<eb:MessageData>



</eb:MessageData>

</eb:MessageHeader>

<wsse:Security






</wsse:Security>

</soap-env:Header>

<soap-env:Body>









<STL:STL_Header.RS


timeStamp="2017-09-07T10:05:03">

<OrchestrationID

seq="1">TKTHLI700-875-1836008397-1504796703160-2113-


<DiagnosticData


<STL:Results>

<Success


<System>T2</System>


</Success>

</STL:Results>


<TT:CustomDetails>

<TT:Agent

duty="4" sine="SKV" type="ATO">


checkDigit="4" name="Sabre Airways" number="795"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VA</ns2:TicketingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYDAD</ns2:StationLocation>

<ns2:StationNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">99101413</ns2:StationNumber

>

<ns2:WorkLocation


<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">4AFD0A</ns2:Lniata>

<ns2:IsoCountryCode


<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VIRGIN

AUSTRALIA</ns2:CompanyName>

<ns2:EmployeeNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0217849</ns2:EmployeeNumber

>




<ns2:Session




</ns2:Session>


</TT:Agent>

<TT:TransactionInfo

actionType="" category="C" code="" sequence="1"

type="SALE">

<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VA</ns2:SystemProvider>

<ns2:InputEntry


ZX6651$VCR$ER</ns2:InputEntry>


<TT:Ticket



type="TKT">


endorsable="false" exchangeable="false" historical="true"




retransmit="false" reverseVoid="false"

selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre

createDate="2017-09-06T00:00:00"

provider="VA">IOGSPK</TT:Sabre>

</TT:Reservation>





useTimeForPricing="true">2017-09-06T23:39:11</TT:LocalIssueDateTime>

<ns2:LastUpdate




checkDigit="4" name="Sabre Airways" number="795"


<ns2:OriginCity



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MEL</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory





<ns2:TicketingMode




<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FFFFFFFV</ns2:CouponText>

<ns2:MandateInfo


<ns2:Disclaimer

country="US"

language="EN">NOTICE











THE CARRIER. CHECK WITH YOUR CARRIER FOR MORE INFORMATION.</ns2:Disclaimer>

<ns2:HazardousMaterials

country="US"

language="EN">THE CARRIAGE OF CERTAIN HAZARDOUS MATERIALS, LIKE

AEROSOLS, FIREWORKS, AND FLAMMABLE LIQUIDS, ABOARD THE AIRCRAFT IS


MAY BE OBTAINED FROM YOUR AIRLINE.</ns2:HazardousMaterials>

</ns2:MandateInfo>

</TT:Details>

<TT:Customer>

<TT:Traveler

nameId="1">

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE/GOLD</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GOLD</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE</ns2:LastName>


<ns2:Contact



</ns2:Contact>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADT</ns2:PricedPassengerTyp

e>

</TT:Traveler>


</TT:Customer>

</TT:Ticket>

</TT:CustomDetails>


</soap-env:Body>


Update Service Coupon (Airline only)

This function is currently available for Airline path. It allows to update the status of EMD-S ticketing

document from “OK” to “USED” when the service is consumed.

Any trial of update of document other than EMD-S will result in getting an error message: “Invalid-

Document Type Must Be EMD-S: [document number]”.

Error message will also be returned when submitting for update document with status “USED”.

Ticketing System can update up to 99 documents per transaction. This limitation is based on the number of

travellers that can be booked in one reservation record. The default is one ticketing document at a time.

Note: when update is performed on more than 1 document in one transaction and the status update of any

of the documents within this request fails, the whole transaction will fail and error message will be

returned to user.

UpdateServiceCouponRQ also allows the user to add a remark at the time of update that is stored in T2

database history of the document. Currently maximum number of characters allowed in this field is 500.

Following document details are mandatory in order to perform an update via UpdateServiceCouponRQ:

- EMD-S number (max. 99 in one transaction)

- Service coupon number(s) to be updated. It is the number representing the order in which the

coupons are used.

Currently, up to 4 coupons is supported (no conjunctive). However it is planned in the future to

support conjunctive EMD documents which will allow to update up to 16 coupons per EMD.

Optionally following parameters can be added:

- name

- local issue date

- document type

Upon sending the request to T2 database, a validation of received details is performed. If it is not

successful, i.e. DocumentNumber does not match LastName or FirstName provided, an error message is

returned.

An example of an UpdateServiceCoupon request:

<UpdateServiceCouponRQ Version="3.5.0"


<Ticketing>


<Agent duty="5" sine="VT5" type="ATO">


<WorkLocation>VZN</WorkLocation>

</Agent>

<TransactionInfo type="EMD">

<LocalDateTime>2014-02-12T17:02:31+01:00</LocalDateTime>

<SystemProvider>U0</SystemProvider>

</TransactionInfo>

<ConsumeServiceCoupon>

<TicketingDocument number="8888888888888">

<Customer>

<Traveler>

<Name>KOWALSKI/JAN</Name>

<FirstName>JAN</FirstName>

<LastName>KOWALSKI</LastName>

</Traveler>

</Customer>

<ServiceCoupon coupon="1"/>

</TicketingDocument>

</ConsumeServiceCoupon>

</Ticketing>

</UpdateServiceCouponRQ>

An example of an UpdateServiceCoupon response:

<TT:UpdateServiceCouponRS Version="3.5.0"









<Results>

<Success/>

</Results>


<TT:Ticketing>

<ns2:Agent duty="5" sine="VT5" type="ATO">



</ns2:Agent>

<TT:TransactionInfo type="EMD">

<ns2:LocalDateTime>2014-02-12T17:02:31+01:00</ns2:LocalDateTime>



<ns2:ConsumeServiceCoupon>

<ns2:TicketingDocument number="8888888888888">

<ns2:Customer>

<ns2:Traveler>




</ns2:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon coupon="1"/>


</ns2:TicketingDocument>

</ns2:ConsumeServiceCoupon>

</TT:Ticketing>

</TT:UpdateServiceCouponRS>

An example of an error in case of an upade of an EMD-A coupon:

<TT:UpdateServiceCouponRS Version="3.5.0"





<STL:STL_Header.RS messageID="H8460305020468-5132-559856357-1393848610641-2-




<Results>

<Error status="NotProcessed" timeStamp="2014-03-03T06:10:12.002-06:00"

type="Application">


<System>T2</System>


<ErrorMessage>Invalid-Document Type Must Be EMD-S:

1618200883469</ErrorMessage>

<ShortText>Invalid-Document Type Must Be EMD-S:

1618200883469</ShortText>

<RecordID>1618200883469</RecordID>


</Error>

</Results>


<TT:Ticketing>

<ns2:Agent duty="5" sine="VT5" type="ATO">



</ns2:Agent>

<TT:TransactionInfo type="EMD">

<ns2:LocalDateTime>2014-02-12T17:02:31+01:00</ns2:LocalDateTime>



<ns2:ConsumeServiceCoupon>

<ns2:TicketingDocument number="8888888888888">

<ns2:Customer>

<ns2:Traveler>




</ns2:Traveler>

</ns2:Customer>

<ns2:ServiceCoupon coupon="1"/>

</ns2:TicketingDocument>

</ns2:ConsumeServiceCoupon>

</TT:Ticketing>

</TT:UpdateServiceCouponRS>


Manual Documents (Airline only) RQ & RS v.3.5.1

The new UpdateTicketingDocumentRQ/RS operation being introduced with xml schema 3.5.1 will allow

the recording of a manual document, which is a non-standard form, to the Agent Sales Report (ASR).

These manual documents are unique to an airline and do to not reside in the WAF table.

This new operation will allow the transaction to be reported and tracked in the ASR for revenue

accounting purposes. It will allow the remarks to be updated with XX FOP remarks. Up to 8 XX FOP

remarks will be allowed to be added to the ASR. Once the update is completed, these manual documents

will be stored in the T2 database and not in the Ticket (VCR) database.

Note The 2 letter codes used in the xml schema examples below are for illustrative purposes only.

Existing WYM Mask error messages will be used. No new error messages are being introduced by

this new xml operation.

Assumption:

1. Non standard documents will be added through the WYM Mask

2. Existing ASR eidts will be done in Host Sabre. (e.g. valid 2 letter credit card). The new xml

operation will not invoke edits.

a. All fields in this xml operation are optional

3. Any additional edits will be completed by either other existing xml operations, host Sabre, or

GUI. (sample edits are listed below)

a. Electronically issued documents (Yes or No)

b. GDS issued documents (Yes or No)

c. Valid credit card codes

d. Valid remarks

An example of an UpdateTicketingDocument Request:

UpdateTicketingDocumentRQ Version="3.5.1"




<STL:POS>

<STL:Company>LA</STL:Company>

<STL:Actual>SCL</STL:Actual>

<STL:Home>SCL</STL:Home>

<STL:DutyCode>4</STL:DutyCode>

</STL:POS>

<Ticketing>

<Agent>

<TicketingProvider>LA</TicketingProvider>

<StationLocation>SCL</StationLocation>

<StationNumber>75995172</StationNumber>

<WorkLocation>SCL</WorkLocation>

<HomeLocation>SCL</HomeLocation>

</Agent>

<TransactionInfo>

<LocalDateTime>2014-05-22T09:11:17+02:00</LocalDateTime>

<SystemProvider>LA</SystemProvider>


<InputEntry>Via UpdateTicketingDocumentRQ web service</InputEntry>

</TransactionInfo>

<UpdateRemarks>

<TicketingDocument number="8888888888888">

<Details>


</Details>

<Remove>

<Remark type="FOP3"/>

</Remove>

<Set>

<Remark type="FOP1">AD/CLP/1791360/AD</Remark>

<Remark type="FOP2">BC/CLP/2000/BC</Remark>

</Set>


</UpdateRemarks>

</Ticketing>

</UpdateTicketingDocumentRQ>

An example of an UpdateTicketingDocument Response:

<TT:UpdateTicketingDocumentRS Version="3.5.1"





<STL:OrchestrationID seq="1">TKTHLI700-14893-174031089-1400742824959-

16859-tktdoc</STL:OrchestrationID>

<STL:Results>

<STL:Success/>

</STL:Results>


<TT:Ticketing>

<TT:Agent>

<TT:TicketingProvider>U0</TT:TicketingProvider>

<TT:StationLocation>SCL</TT:StationLocation>

<TT:StationNumber>75995172</TT:StationNumber>

<TT:WorkLocation>SCL</TT:WorkLocation>

<TT:HomeLocation>SCL</TT:HomeLocation>

</TT:Agent>


<TT:LocalDateTime>2014-05-22T09:11:17+02:00</TT:LocalDateTime>

<TT:SystemProvider>LA</TT:SystemProvider>

<TT:InputEntry>Via UpdateTicketingDocumentRQ web

service</TT:InputEntry>


<TT:UpdateRemarks>

<TT:TicketingDocument number="8888888888888">

<TT:Details>

<TT:LocalIssueDate>2014-05-22</TT:LocalIssueDate>

</TT:Details>

<TT:Remarks>

<TT:Remark sequence="1"

type="FOP1">AD/CLP/1791360/AD</TT:Remark>

Up to 8 FOP lines

can be added in

sequence

Up to 8 FOP lines

can be added in

sequence


<TT:Remark sequence="2"

type="FOP2">BC/CLP/2000/BC</TT:Remark>

<TT:Remark sequence="1" type="PYMT">AD.BC</TT:Remark>

<TT:Remark sequence="1" type="RMKS">SCL LA MAD Q330.00

3372.00NUC3702.00END ROE</TT:Remark>

</TT:Remarks>


</TT:UpdateRemarks>

</TT:Ticketing>

</TT:UpdateTicketingDocumentRS>

Non-Refundable Fares v3.5.1 (RQ & RS)

With xml schema version 3.5.1, a new NonRefundable element has been created to pass the non-

refundable amount and currency as received from either Ticketing or Pricing WS. This element will be

passed during any future exchange transaction.

No new edit has been introduced for the existing amount.

Request:




<STL:POS/>





</SearchParameters>


Response:








<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="5" sine="SSW" type="WEB">

http://services.sabre.com/STL/v01

http://www.sabre.com/ns/Ticketing/DC








number="795"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WINWC</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WIN</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WIN</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">5DB998</ns2:Lniata>

<ns2:IsoCountryCode


<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VIRGIN

AUSTRALIA</ns2:CompanyName>

<ns2:EmployeeNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0989001</ns2:EmployeeNumber>




<ns2:Session xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">


<ns2:AgentCloseType>AGT</ns2:AgentCloseType>


<ns2:StationCloseType>AGT</ns2:StationCloseType>

</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$F*AXXXXXXXXXXXX5550/0816*ZX9

3501$VCR</ns2:InputEntry>




<TT:Indicators electronic="true" endorsable="false"





<TT:Details>

<TT:Reservation>


provider="VA">KNWCUA</TT:Sabre>


















</TT:Reservation>






<ns2:LastUpdate




number="888"


<ns2:OriginCity



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory




<ns2:TicketingMode




<ns2:CouponText


<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">E</ns2:CurrentStatus>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SPOLSKI/JAN MR</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JAN MR</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SPOLSKI</ns2:LastName>

<ns2:ExternalNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADT</ns2:ExternalNumber>

<ns2:PassengerType


<ns2:Contact



</ns2:Contact>

</TT:Traveler>

</TT:Customer>



number="888"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">810</ns2:MarketingFlightNumbe

r>























xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0</ns2:OperatingFlightNumber>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">S</ns2:ClassOfService>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SSALE</ns2:FareBasis>

<TT:StartLocation>SYD</TT:StartLocation>

<ns2:StartDateTime



<TT:EndLocation>MEL</TT:EndLocation>

<ns2:EndDateTime


20T08:50:00</ns2:EndDateTime>







<ns2:BookingStatus


<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">EXCH</ns2:CurrentStatus>

<ns2:PreviousStatus


<ns2:BagAllowance


<ns2:CouponUse



sideTripStart="false" unchargeableSurface="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" zeroFareAmount="false"/>

<ns2:StartTimeText













xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SSALE</ns2:AssociatedFareBasi

s>

<TT:FareProvider>VA</TT:FareProvider>

<ns2:Tariff

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">302</ns2:Tariff>

<ns2:FareRule

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1120</ns2:FareRule>

<ns2:PricingVendor

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ATP</ns2:PricingVendor>

</TT:FareComponent>

</TT:ServiceCoupon>























number="888"




r>



<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SSALE</ns2:FareBasis>

<TT:StartLocation>MEL</TT:StartLocation>

<ns2:StartDateTime



<TT:EndLocation>SYD</TT:EndLocation>

<ns2:EndDateTime









<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:PreviousStatus


<ns2:BagAllowance


<ns2:StopOver


<ns2:CouponUse





<ns2:StartTimeText













xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SSALE</ns2:AssociatedFareBasi

s>






















<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base





</ns2:Base>

<TT:Total>

<ns2:Amount currencyCode="AUD" decimalPlace="2"


<ns2:Text


</TT:Total>

<ns2:Tax code="UO" exempt="false" sequence="1"






</ns2:Tax>

<ns2:Tax code="QR" exempt="false" sequence="2"






</ns2:Tax>

<ns2:Tax code="XT" exempt="false" sequence="3"






</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NonRefundable





</ns2:NonRefundable>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>












<ns2:Tax code="UO2" exempt="false" sequence="1"






</ns2:Tax>

<ns2:Tax code="QRM" exempt="false" sequence="2"






</ns2:Tax>

<ns2:Tax code="QRS" exempt="false" sequence="3"






</ns2:Tax>

<ns2:Tax code="WG1" exempt="false" sequence="4"






</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RESTRICTIONS

APPLY/NONEND/PENALTIES APPLY</ns2:Endorsements>

<ns2:Payment sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AX372P103A0155550 0816

X93501</ns2:Payment>

</TT:Remark>


<TT:Booking duty="5" sine="SSW">

<ns2:WorkLocation


<ns2:IataNumber


<ns2:HomeLocation


</TT:Booking>




<ns2:New>SYD VA MEL61.72VA SYD61.72AUD123.44END</ns2:New>


<TT:PrintCoupon couponType="P" printerType="0" quantity="0"

stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">35AE80</ns2:Lniata>

</TT:PrintCoupon>













<TT:Payment paymentConfirmation="false" sequence="1" type="CC">

<TT:Base>



<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>



<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>



<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AX372P103A0155550</ns2:Remark

s>

<TT:Card accb="*" cardType="AX">


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">XXXXXXXXXXX5550</ns2:MaskedCa

rdNumber>

<ns2:ExpireDate


<TT:ApprovalCode>X93501</TT:ApprovalCode>

<ns2:CardBinNumber


<ns2:TransactionId

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">02143259X93501T</ns2:Transact

ionId>

</TT:Card>

</TT:Payment>

<TT:History code="EXA" number="3" sequence="3">




<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">*PQRS VIA WEB

SERVICES</ns2:InputMessage>


<TT:Details>


















Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">KNWCUA</ns2:OldReservation>

<ns2:AccountingCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">888</ns2:AccountingCode>



</TT:Details>

<ns2:ServiceCouponHistory coupon="1" sequence="1"










</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TAPE WRITE-MORE DATA STORED

IN VCR FOR T2</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation


</TT:Details>

</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>




















<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$F*AXXXXXXXXXXXX5550/0816*ZX

93501$VCR</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>









</TT:History>

</TT:Ticket>

</TT:Details>


Multiple Forms of Refund (MFOR)

The OriginalPayment element is present only for Details and CustomDetails result types and ‘TKT’

document type. This information will be used by the AER web service (AERRQ) to determine how to

process the refund. For more information on Multiple Forms of Refund, please refer to the AER User

Guide 3 – Refund Scenarios found on the Community Portal.

3.7.1.1 Detail RQ/RS example

Request:





<STL:POS/>

<SearchParameters>












</SearchParameters>


Response: <TT:GetTicketingDocumentRS Version="3.6.0"







<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="4" sine="LIT" type="WEB">

<ns2:TicketingProvider checkDigit="4" name="U0 DO NOT TKT"


<ns2:StationLocation>WINWC</ns2:StationLocation>


<ns2:WorkLocation>WIN</ns2:WorkLocation>


<ns2:Lniata>051CEE</ns2:Lniata>

<ns2:IsoCountryCode>AU</ns2:IsoCountryCode>

<ns2:CompanyName>VIRGIN AUSTRALIA</ns2:CompanyName>



<ns2:Session>





</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN>10508197061</ns2:TCN>



<ns2:SystemProvider>VA</ns2:SystemProvider>

<ns2:InputEntry">WFRTR2</ns2:InputEntry>









selfSale="false"/>

<TT:Details>

<TT:Reservation>


provider="VA">IXWCGG</TT:Sabre>

</TT:Reservation>





<ns2:ValidatingProvider checkDigit="4" name="U0 DO NOT TKT"

number="888">VA</ns2:ValidatingProvider>

<ns2:OriginCity>BNE</ns2:OriginCity>

<ns2:DestinationCity>BNE</ns2:DestinationCity>


<ns2:ExchTransactionType>X</ns2:ExchTransactionType>






<ns2:CurrentActivity>A</ns2:CurrentActivity>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>LISA/DCC</ns2:Name>

<ns2:FirstName>DCC</ns2:FirstName>

<ns2:LastName>LISA</ns2:LastName>


</TT:Traveler>

</TT:Customer>


<ns2:MarketingProvider checkDigit="4" name="U0 DO NOT TKT"



<ns2:OperatingFlightNumber>0</ns2:OperatingFlightNumber>



<TT:StartLocation>BNE</TT:StartLocation>



<ns2:EndDateTime>2014-08-25T07:35:00</ns2:EndDateTime>









<ns2:ValidatingProvider>VA</ns2:ValidatingProvider>

















</TT:FareComponent>

</TT:ServiceCoupon>


<ns2:MarketingProvider checkDigit="4" name="AA DO NOT TKT"






<TT:StartLocation>SYD</TT:StartLocation>


<TT:EndLocation>BNE</TT:EndLocation>











<ns2:ValidatingProvider>VA</ns2:ValidatingProvider>










<ns2:AssociatedFareBasis>Y</ns2:AssociatedFareBasis>





</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base>



</ns2:Base>

<TT:Total>



<ns2:Text>NO ADC</ns2:Text>

</TT:Total>

<ns2:Tax code="UO" exempt="false" sequence="1" status="PD">




</ns2:Tax>

<ns2:Tax code="QR" exempt="false" sequence="2" status="PD">




</ns2:Tax>

<ns2:Tax code="QR" exempt="false" sequence="3" status="PD">




</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:AddCollect>



</ns2:AddCollect>

<ns2:ChangeFee>



</ns2:ChangeFee>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="UO" exempt="false" sequence="1" status="Y">




</ns2:Tax>

<ns2:Tax code="QR" exempt="false" sequence="2" status="Y">




</ns2:Tax>

<ns2:Tax code="QR" exempt="false" sequence="3" status="Y">




</ns2:Tax>

<ns2:Tax code="WG" exempt="false" sequence="4" status="Y">




</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements sequence="1">NON ENDORSABLE</ns2:Endorsements>

<ns2:Payment sequence="3">EF VI4505P10VRD100003</ns2:Payment>

<ns2:OriginalIssue sequence="1">24JUL14WIN99401013</ns2:OriginalIssue>


</TT:Remark>


<TT:Booking duty="$" sine="LIT">




</TT:Booking>



<ns2:New>BNE VA SYD498.29VA BNE498.29AUD996.58END</ns2:New>



<TT:Original paymentConfirmation="false">


<ns2:Payment>EFVI4028P10HRC890008</ns2:Payment>



<TT:IssueTime>03:13:00</TT:IssueTime>

<ns2:IssueCity>WIN</ns2:IssueCity>


<TT:OriginalPayment paymentConfirmation="true" sequence="1" type="CC">

<TT:Tax>

<TT:Amount decimalPlace="0">0</TT:Amount>


</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>EF</ns2:Remarks>

<TT:Card cardType="VI">

<ns2:MaskedCardNumber>4028P10HRC890008</ns2:MaskedCardNumber>




<ns2:TransactionId>209046636672265</ns2:TransactionId>

<TT:DynamicCurrencyConversion>

<ns2:Amount currencyCode="HKD" decimalPlace="2">7447.57</ns2:Amount>


<ns2:Rate decimalPlace="4">7.5659</ns2:Rate>

</TT:DynamicCurrencyConversion>

</TT:Card>

</TT:OriginalPayment>

<TT:OriginalPayment paymentConfirmation="true" sequence="2" type="CC">

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>EF</ns2:Remarks>


<ns2:MaskedCardNumber>4505P10VRD100003</ns2:MaskedCardNumber>





<ns2:TransactionId>211035236672265</ns2:TransactionId>

<TT:DynamicCurrencyConversion>

<ns2:Amount currencyCode="CAD" decimalPlace="2">163.60</ns2:Amount>


<ns2:Rate decimalPlace="4">1.0648</ns2:Rate>

</TT:DynamicCurrencyConversion>

</TT:Card>


</TT:Original>



<ns2:Payment>EFVI4028P10HRC890008</ns2:Payment>




<ns2:IssueCity>WIN</ns2:IssueCity>


</TT:Exchange>



<ns2:Lniata>A38394</ns2:Lniata>

</TT:PrintCoupon>

<TT:Payment sequence="1" type="ET">

<TT:Base>

<TT:Amount currencyCode="AUD" decimalPlace="2">996.58</TT:Amount>


</TT:Base>

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>

<TT:TravelDocument/>

</TT:Payment>

<TT:Payment paymentConfirmation="false" sequence="2" type="CC">

<TT:Base>



</TT:Base>

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>BA40P101F5R0006</ns2:Remarks>

<TT:Card accb="*" cardType="BA">

<ns2:MaskedCardNumber>XXXXXXXXX0006</ns2:MaskedCardNumber>


<TT:ApprovalCode>Z123456</TT:ApprovalCode>



</TT:Card>

</TT:Payment>






</TT:Agent>







<TT:Details>


<ns2:OldReservation>IXWCGG</ns2:OldReservation>

</TT:Details>

</TT:History>


<TT:Agent duty="4" sine="LIT">




</TT:Agent>




<ns2:InputMessage>WFRTR2</ns2:InputMessage>


<TT:Details>


<ns2:OldReservation>IXWCGG</ns2:OldReservation>


</TT:Details>







</TT:History>

</TT:Ticket>

</TT:Details>


3.7.1.2 Custom Detail RQ/RS example

Request: <?xml version="1.0" encoding="UTF-8"?>





<STL:POS/>





</SearchParameters>


Response: <TT:GetTicketingDocumentRS Version="3.6.0"







<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:CustomDetails>

<TT:Agent duty="5" sine="SMA" type="ATO">

<ns2:TicketingProvider checkDigit="4" name="AA DO NOT TKT"


<ns2:StationLocation>BNEAI</ns2:StationLocation>


<ns2:WorkLocation>BNE</ns2:WorkLocation>


<ns2:Lniata>F25902</ns2:Lniata>

<ns2:IsoCountryCode>AU</ns2:IsoCountryCode>

<ns2:CompanyName>VIRGIN AUSTRALIA</ns2:CompanyName>



<ns2:Session>



</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN>00560151106</ns2:TCN>




<ns2:InputEntry>WFRF</ns2:InputEntry>









selfSale="false"/>

<TT:Details>

<TT:Reservation>


provider="VA">HAOIEN</TT:Sabre>

</TT:Reservation>





<ns2:ValidatingProvider checkDigit="4" name="AA DO NOT TKT"


<ns2:OriginCity>BNE</ns2:OriginCity>

<ns2:DestinationCity>BNE</ns2:DestinationCity>


<ns2:ExchTransactionType>X</ns2:ExchTransactionType>







<ns2:CurrentActivity>E</ns2:CurrentActivity>

</TT:Details>


<TT:Original>


<ns2:Payment>EFCASH</ns2:Payment>



<TT:IssueTime>22:43:00</TT:IssueTime>

<ns2:IssueCity>BNE</ns2:IssueCity>


<TT:OriginalPayment paymentConfirmation="false" sequence="1" type="CA">

<TT:Tax>



</TT:Tax>

<TT:Total>



</TT:Total>

<ns2:Remarks>EFCASH</ns2:Remarks>



<TT:OriginalPayment paymentConfirmation="false" sequence="2" type="CC">

<TT:Tax>



</TT:Tax>

<TT:Total>




</TT:Total>

<ns2:Remarks>EFAXXXXXXXXXX5550</ns2:Remarks>

<TT:Card cardType="AX">



<TT:ApprovalCode>1234</TT:ApprovalCode>


</TT:Card>


</TT:Original>



<ns2:Payment>EFCASH</ns2:Payment>




<ns2:IssueCity>BNE</ns2:IssueCity>


</TT:Exchange>


</TT:Ticket>

</TT:CustomDetails>


Airline Ticketing Fees (T and R Types) (Airline path)

TicketingDocumentServiceRQ (TktDoc) Web Service allows a request to retrieve/display an electronic air ticket (VCR) details about Airline Ticketing Fees T-Type (Ticketing charges) and R-Type (Requested Services charges). Requesting information about Airline Ticketing Fees also called OB Ticketing Fees is available for Airline Customers. The new elements OBFee and OBFeesTotal introduced with schema version 3.6.0 provide information about OB Ticketing Fees (R and T Types) collected/waived at the time of ticketing. Airline Ticketing fees are not included in the total ticket value therefore for convenience Grand Total will be provided that will specify the total amount collected at the time of ticketing. Existing combinations for GetTicketingDocumentRQ Search Parameters with Result Types Details and

CustomDetails applies to request an electronic air ticket with OB Ticketing Fees details.

REQUEST:




<STL:POS/>




</SearchParameters>



RESPONSE:








<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="4" sine="H,R" type="ATO">



<ns2:StationLocation>AUHAT</ns2:StationLocation>


<ns2:WorkLocation>AUH</ns2:WorkLocation>

<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">69A3B6</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AE</ns2:IsoCountryCode>



<ns2:EmployeeNumber







</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN






<ns2:SystemProvider


<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$FCA$VCR</ns2:InputEntry>









selfSale="false"/>

<TT:Details>

<TT:Reservation>


provider="U0">DEKDQF</TT:Sabre>

</TT:Reservation>








<ns2:ValidatingProvider checkDigit="5" name="SABRE AIRWAYS" number="888"


<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AUH</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SYD</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory




<ns2:TicketingMode




<ns2:CouponText


</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SMITH/JOHN

MR</ns2:Name>

<ns2:FirstName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JOHN

MR</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SMITH</ns2:LastName>

<ns2:PassengerType


</TT:Traveler>

</TT:Customer>


<ns2:MarketingProvider checkDigit="5" name="SABRE AIRWAYS" number="888"




r>


<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YLOWAE</ns2:FareBasis>

<TT:StartLocation>AUH</TT:StartLocation>









<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">950P</ns2:StartTimeText>








</ns2:PlusUp>






xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YLOWAE</ns2:AssociatedFareBas

is>

<TT:FareProvider>U0</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AEGD</ns2:FareRule>

<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>




</ns2:Base>

<TT:Total>


<ns2:Amount currencyCode="AED" decimalPlace="2"


<ns2:Text


</TT:Total>

<ns2:Tax code="AE" exempt="false" sequence="1"





</ns2:Tax>

<ns2:Tax code="TP" exempt="false" sequence="2"





</ns2:Tax>

<ns2:Tax code="WY" exempt="false" sequence="3"





</ns2:Tax>

</TT:New>

<TT:Other>

<GrandTotal>

<Amount decimalPlace="2" currencyCode="AED">9446.00</Amount>

<Text>9458.00</Text>

<ApplyCreditInd>false</ApplyCreditInd>

</GrandTotal>

<ns2:NUC>



</ns2:NUC>

<ns2:OBFee sequence="1">

<ns2:Amount decimalPlace="2" currencyCode="AED">15.00</ns2:Amount>


<ns2:FeeCode>OBT01</ns2:FeeCode>

<ns2:PricedCode>0</PricedCode>

<ns2:Description>Ticketing Sub Code #1 description text</Description>

</ns2:OBFee>







</ns2:OBFee>






<WaiverCode>01</WaiverCode>


</ns2:OBFee>





<ns2:FeeCode>OBR03</ns2:FeeCode>


<ns2:Description>Tour Package Delivery</Description>

</ns2:OBFee>






<ns2:Description>Tour Package Delivery</Description>

</ns2:OBFee>






<ns2:WaiverCode>03</WaiverCode>

<ns2:Description>Unaccompanied Minor (UMR)</Description>

</ns2:OBFee>

<OBFeesTotal>

<Amount decimalPlace="2" currencyCode="AED">46.00</Amount>

<Text>46.00</Text>

</OBFeesTotal>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="AE" exempt="false" sequence="1">




</ns2:Tax>

<ns2:Tax code="TP" exempt="false" sequence="2">




</ns2:Tax>

<ns2:Tax code="WY" exempt="false" sequence="3">




</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VALID ON U0

ONLY</ns2:Endorsements>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CASH</ns2:Payment>

</TT:Remark>


<TT:Booking duty="4" sine="H,R">

<ns2:WorkLocation



<ns2:IataNumber


<ns2:HomeLocation


</TT:Booking>



<ns2:New>AUH U0 SYD Q5.00 2504.74NUC2509.74END ROE3.67303</ns2:New>



<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">14CCAC</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>

<TT:Amount currencyCode="AED" decimalPlace="2">9220.00</TT:Amount>

<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>


<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>


<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks



</TT:Payment>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TAPE

WRITE-MORE DATA STORED IN VCR FOR T2</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DEKDQF</ns2:OldReservation>


</TT:Details>

</TT:History>


<TT:Agent duty="4" sine="H,R">



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$FCA$VCR</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DEKDQF</ns2:OldReservation>



</TT:Details>





</TT:History>

</TT:Ticket>

</TT:Details>


Spanish Residents

Airlines are required to offer to discounts within Spain in accordance with regulations established by the Spanish Government. Discounts offered are as follows:

Island Resident Discount: Island residents are entitled to a 50% discount when travelling between their island home and the Spanish mainland, as well as travel between the Spanish islands. For example, a resident of Palma de Mallorca can use this discount for trips between Palma de Mallorca and Madrid, but not for trips between Madrid and Barcelona. An automated proof of residency from the Ministerio de Fomento is required.


Large Family Discount: Discounts are available for members of families which are composed of five people or more. It applies to any member of a large family travelling domestically in Spain. It is not a family travel-together discount. There are two levels of discount. There is a 5% discount and a 10% discount. The 5% is the general requirement for family of 5 (with 3 children) and the 10% is for a larger family (with 5 or more children) An automated proof of residency from the Ministerio de Fomento is not required.

3.9.1.1 Island Resident Discount RQ/RS example

REQUEST:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version="1.0">

<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>

<ns1:MessageId>1000</ns1:MessageId>

<ns1:Timestamp>2010-10-16</ns1:Timestamp>

</ns1:MessageData>


<ns1:Security>

<ns1:BinarySecurityToken>Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/

STSB!ICESMSLB\/STS.LB!-3595016674425289951!1094233!0</ns1:BinarySecurityToken>

</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.6.0"


<ns1:STL_Header.RQ>

<ns2:POS>

<SearchParameters>




</SearchParameters>


</SOAP-ENV:Body>



RESPONSE: <?xml version="1.0" encoding="UTF-8"?>

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">

<soap-env:Header>

<eb:MessageHeader eb:version="1.0"


<eb:From>

<eb:PartyId>123123</eb:PartyId>

</eb:From>

<eb:To>


</eb:To>

<eb:CPAId>HDQ</eb:CPAId>

<eb:ConversationId>2009-09-23-15555</eb:ConversationId>


<eb:Action>TicketingDocumentServicesRS</eb:Action>

<eb:MessageData>

<eb:MessageId>mid:20001209-133003-

[email protected]</eb:MessageId>

<eb:Timestamp>2001-02-15T11:15:12Z</eb:Timestamp>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security


<wsse:BinarySecurityToken EncodingType="wsse:Base64Binary"

valueType="String">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/STSB!I

CESMSLB\/STS.LB!-3597530983543867614!1079329!0</wsse:BinarySecurityToken>

</wsse:Security>

</soap-env:Header>

<soap-env:Body>



<STL:STL_Header.RS messageID="TKTHLI700-12828-1012647623-

1416307360275-3008-tktdoc" timeStamp="2014-11-18T04:42:40"





<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="4" sine="K1K" type="GSA">



<ns2:StationLocation>MADST</ns2:StationLocation>


<ns2:WorkLocation>MAD</ns2:WorkLocation>


<ns2:Lniata>35575D</ns2:Lniata>


<ns2:IsoCountryCode>ES</ns2:IsoCountryCode>



<ns2:ShiftStartDateTime>2014-10-


<ns2:Session>


<ns2:AgentCloseType>SUP</ns2:AgentCloseType>


</ns2:Session>

</TT:Agent>

<TT:TransactionInfo actionType="" category="C" code=""

sequence="1" type="SALE">


<ns2:SystemDateTime</ns2:SystemDateTime>


<ns2:InputEntry>W$FCA$VCR</ns2:InputEntry>







refundCalculation="false" reservarionPurge="false" residentDiscount="true"


<TT:Details>

<TT:Reservation>


provider="U0">UNALRH</TT:Sabre>

</TT:Reservation>








<ns2:OriginCity>MAD</ns2:OriginCity>

<ns2:DestinationCity>MAD</ns2:DestinationCity>







<TT:GovernmentStatus type="R">

<ns2:CountryCode>ES</ns2:CountryCode>

<ns2:CityCode>TFN</ns2:CityCode>

</TT:GovernmentStatus>

<TT:ResidentLargeFamilyDiscount>0</TT:ResidentLargeFamilyDiscount>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>FGTTAH/GLCL</ns2:Name>

<ns2:FirstName>GLCL</ns2:FirstName>

<ns2:LastName>FGTTAH</ns2:LastName>


<ns2:PassengerType>ADR</ns2:PassengerType>

<ns2:Contact>


</ns2:Contact>

</TT:Traveler>

</TT:Customer>







<ns2:FareBasis>YD</ns2:FareBasis>

<TT:StartLocation>MAD</TT:StartLocation>


<TT:EndLocation>TFN</TT:EndLocation>


<ns2:TicketDesignator>RC</ns2:TicketDesignator>






hosted="false">IB</ns2:CurrentControllingProvider>




sideTripStart="false" unchargeableSurface="false" zeroFareAmount="false">



<ns2:Amount currencyCode="EUR"









xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YD/RC</ns2:AssociatedFareBasi

s>

<ns2:AssociatedTicketDesignator>RC</ns2:AssociatedTicketDesignator>

<TT:FareProvider>IB</TT:FareProvider>


<ns2:FareRule>ES04</ns2:FareRule>


</TT:FareComponent>

</TT:ServiceCoupon>







<ns2:FareBasis>YD</ns2:FareBasis>

<TT:StartLocation>TFN</TT:StartLocation>



<TT:EndLocation>MAD</TT:EndLocation>


<ns2:TicketDesignator>RC</ns2:TicketDesignator>






hosted="false">IB</ns2:CurrentControllingProvider>





sideTripStart="false" unchargeableSurface="false" zeroFareAmount="false"












<ns2:AssociatedFareBasis>YD/RC</ns2:AssociatedFareBasis>

<ns2:AssociatedTicketDesignator>RC</ns2:AssociatedTicketDesignator>



<ns2:FareRule>ES04</ns2:FareRule>


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base>




</ns2:Base>

<TT:Total>




</TT:Total>

<ns2:Tax code="JD" exempt="false" sequence="1">





</ns2:Tax>

<ns2:Tax code="QV" exempt="false" sequence="2">






</ns2:Tax>

<ns2:Tax code="OG" exempt="false" sequence="3">





</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="JD" exempt="false" sequence="1">





</ns2:Tax>

<ns2:Tax code="QV" exempt="false" sequence="2">





</ns2:Tax>

<ns2:Tax code="OG" exempt="false" sequence="3">





</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements sequence="1">55 CHGS AND REF

PERMITTED</ns2:Endorsements>


</TT:Remark>


<TT:Booking duty="4" sine="K1K">




</TT:Booking>



<ns2:New>MAD IB TCI246.00IB MAD246.00EUR492.00END

*RCDN/10000944S/38/VERIFICADO/001/MFOM2014102110000944S27A5777C67C</ns2:New>



stockType="2A">

<ns2:Lniata>AEF7ED</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>

<TT:Amount currencyCode="EUR"




</TT:Base>

<TT:Tax>




</TT:Tax>

<TT:Total>




</TT:Total>



</TT:Payment>






</TT:Agent>








<TT:Details>


<ns2:OldReservation>UNALRH</ns2:OldReservation>

</TT:Details>

</TT:History>


<TT:Agent duty="4" sine="K1K">




</TT:Agent>





<ns2:InputMessage>UNSOL CTRL TO IB</ns2:InputMessage>


<TT:Details>




</TT:Details>




<ns2:CurrentControllingProvider>IB</ns2:CurrentControllingProvider>








</TT:History>






</TT:Agent>





<ns2:InputMessage>W$FCA$VCR</ns2:InputMessage>


<TT:Details>




</TT:Details>







</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>


3.9.1.2 Large Family Discount RQ/RS example

REQUEST: <?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version="1.0"">

<ns1:From>


</ns1:From>

<ns1:To>



</ns1:To>





<ns1:MessageData>



</ns1:MessageData>


<ns1:Security>



</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.6.0">

<ns1:STL_Header.RQ>

<ns2:POS>

<SearchParameters>




</SearchParameters>


</SOAP-ENV:Body>




<soap-env:Header>



<eb:From>


</eb:From>

<eb:To>


</eb:To>





<eb:MessageData>




</eb:MessageData>

</eb:MessageHeader>

<wsse:Security




valueType="String">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/STSA!I


</wsse:Security>

</soap-env:Header>

<soap-env:Body>









<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MADST</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MAD</ns2:WorkLocation>

<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">373115</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ES</ns2:IsoCountryCode>

<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SABRE


<ns2:EmployeeNumber









</ns2:Session>

</TT:Agent>




<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputEntry








refundCalculation="false" reservarionPurge="false" residentDiscount="false"


<TT:Details>

<TT:Reservation>


provider="U0">JFIZKK</TT:Sabre>

</TT:Reservation>









<ns2:OriginCity>MAD</ns2:OriginCity>

<ns2:DestinationCity>TFN</ns2:DestinationCity>







<ns2:CurrentStatus>E</ns2:CurrentStatus>


</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>TESTING/ONE</ns2:Name>

<ns2:FirstName>ONE</ns2:FirstName>

<ns2:LastName>TESTING</ns2:LastName>


<ns2:Contact>


</ns2:Contact>

</TT:Traveler>

</TT:Customer>




number="888"




er>



<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YD</ns2:FareBasis>


<ns2:StartDateTime




<ns2:EndDateTime






<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:PreviousStatus


<ns2:CurrentControllingProvider hosted="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IB</ns2:CurrentControllingPro

vider>

<ns2:BagAllowance

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1PC</ns2:BagAllowance>

<ns2:CouponUse





<ns2:StartTimeText













xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YD</ns2:AssociatedFareBasis>


<ns2:Tariff



<ns2:FareRule

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">05ES</ns2:FareRule>

<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base





</ns2:Base>

<TT:Total>



<ns2:Text


</TT:Total>

<ns2:Tax code="JD" exempt="false" sequence="1"






</ns2:Tax>

<ns2:Tax code="QV" exempt="false" sequence="2"






</ns2:Tax>

<ns2:Tax code="OG" exempt="false" sequence="3"






</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>







</ns2:Tax>








</ns2:Tax>







</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">55 CHGS AND REF




</TT:Remark>



<ns2:WorkLocation


<ns2:IataNumber


<ns2:HomeLocation


</TT:Booking>




<ns2:New>MAD IB TCI468.00EUR468.00END *F1DN/4561237890C/9

/0064/201/0801</ns2:New>



stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AEF7ED</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>



<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>



<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>



<ns2:ApplyCreditInd


</TT:Total>


<ns2:Remarks



</TT:Payment>

<TT:History code="EXR" number="5" sequence="5">




<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WFRDFN1</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JFIZKK</ns2:OldReservation>

<ns2:AccountingCode


<ns2:CurrentDocumentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">E</ns2:CurrentDocumentStatus>



</TT:Details>






</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider



<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WFRDFN1</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>



<ns2:PreviousControllingProvider>IB</ns2:PreviousControllingProvider>




</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage




<TT:Details>



Document>

<ns2:OldReservation


</TT:Details>

</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage


IB</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>







</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage



<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>






</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>


3.9.1.3 Large Family and Resident Discount RQ/RS example

REQUEST: <?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version="1.0"">

<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>



</ns1:MessageData>


<ns1:Security




</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.6.0">

<ns1:STL_Header.RQ>

<ns2:POS/>

<SearchParameters>




</SearchParameters>


</SOAP-ENV:Body>





<soap-env:Header>



<eb:From>


</eb:From>

<eb:To>


</eb:To>





<eb:MessageData>




</eb:MessageData>

</eb:MessageHeader>

<wsse:Security





</wsse:Security>

</soap-env:Header>

<soap-env:Body>









<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>



number="888"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MADST</ns2:StationLocation>


<ns2:StationNumber


<ns2:WorkLocation


<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">69940D</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ES</ns2:IsoCountryCode>

<ns2:CompanyName



<ns2:EmployeeNumber









</ns2:Session>

</TT:Agent>



<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$PQ1N1.1$FCA$VCR</ns2:InputE

ntry>







refundCalculation="false" reservarionPurge="false" residentDiscount="true"


<TT:Details>

<TT:Reservation>


provider="U0">VVTCYM</TT:Sabre>

</TT:Reservation>







<ns2:LastUpdate




number="888"


<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MAD</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TFN</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory




<ns2:TicketingMode




<ns2:CouponText


<TT:GovernmentStatus type="R">

<ns2:CountryCode>ES</ns2:CountryCode>

<ns2:CityCode>TFN</ns2:CityCode>

</TT:GovernmentStatus>


</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name>TESTING/ONE</ns2:Name>

<ns2:FirstName>ONE</ns2:FirstName>

<ns2:LastName">TESTING</ns2:LastName>


<ns2:Contact>


</ns2:Contact>

</TT:Traveler>

</TT:Customer>



number="888"




er>



<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YD</ns2:FareBasis>


<ns2:StartDateTime





<ns2:EndDateTime



<ns2:TicketDesignator

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RC</ns2:TicketDesignator>




<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:PreviousStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CTRL</ns2:PreviousStatus>

<ns2:CurrentControllingProvider hosted="false"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IB</ns2:CurrentControllingPro

vider>

<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText













xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YD/RC</ns2:AssociatedFareBasi

s>

<ns2:AssociatedTicketDesignator

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RC</ns2:AssociatedTicketDesig

nator>


<ns2:Tariff


<ns2:FareRule

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ES04</ns2:FareRule>

<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base






</ns2:Base>

<TT:Total>



<ns2:Text


</TT:Total>







</ns2:Tax>







</ns2:Tax>







</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>







</ns2:Tax>







</ns2:Tax>







</ns2:Tax>

</TT:New>


</TT:Taxes>

<TT:Remark>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">55 CHGS AND REF




</TT:Remark>



<ns2:WorkLocation


<ns2:IataNumber


<ns2:HomeLocation


</TT:Booking>




<ns2:New>MAD IB TCI197.00EUR197.00END

*RCDN/10000944S/38*F1DN/10000944S/13/0064/201/0801/VERIFICADO/001/MFOM20141024

10000944S4D28460A667</ns2:New>



stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AEF7ED</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>



<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>



<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>



<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks



</TT:Payment>






<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WFRDFN1$N1.1</ns2:InputMessag

e>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VVTCYM</ns2:OldReservation>



</TT:Details>



<ns2:PreviousControllingProvider>IB</ns2:PreviousControllingProvider>




</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage




<TT:Details>



Document>

<ns2:OldReservation



</TT:Details>

</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage


IB</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>







</TT:History>





<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$PQ1N1.1$FCA$VCR</ns2:InputM

essage>



<TT:Details>



Document>

<ns2:OldReservation




</TT:Details>





</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>


Canadian Baggage Disclosure

Airlines are required to disclose the baggage text consisting of the charge for the first and second checked and carry-on bags as well as information regarding embargoes and discounts in the Price Quote and on the passenger’s receipt at time of Pricing and Ticketing. With xml schema v3.7.0 and higher, GetTicketDoc will now include the Canadian Baggage Disclosure which mimics the US D.O.T ruling and provide Baggage Charge information to those who travel within, and to or from Canada.. The Example below is from a PQ entry and is for illustrative purposes: Native Sabre Entry: *PQ«

Respnse:

PRICE QUOTE RECORD - DETAILS

PQ 1 RQ

BASE FARE TAXES/FEES/CHARGES TOTAL

CAD668.00 145.91XT CAD813.91ADT

XT 14.25CA 37.41XG 3.25RC 45.00SQ

46.00YQ

ADT MC10 GC14

LAST DAY TO PURCHASE 11MAY/2359

YVR WS YTO378.00WS YVR290.00CAD668.00END

VALIDATING CARRIER SPECIFIED - WS

NONREF - FEE FOR CHG/CXL

01 O YVR WS 8122M 21MAY 700A MC10 21MAY21MAYNIL

02 O YYZ WS 709G 25MAY 1130A GC14 25MAY25MAYNIL

YVR

BAG ALLOWANCE -YVRYYZ-NIL/WS


1STCHECKED BAG FEE-YVRYYZ-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR

AMS AND UP TO 62 LINEAR INCHES/158 LINEAR CENTIMETERS ‡

MD«

2NDCHECKED BAG FEE-YVRYYZ-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR‡

AMS AND UP TO 62 LINEAR INCHES/158 LINEAR CENTIMETERS

BAG ALLOWANCE -YYZYVR-NIL/WS

1STCHECKED BAG FEE-YYZYVR-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


2NDCHECKED BAG FEE-YYZYVR-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


CARRY ON ALLOWANCE

YVRYYZ YYZYVR-01P/WS

CARRY ON CHARGES

YVRYYZ YYZYVR-WS-CARRY ON FEES UNKNOWN-CONTACT CARRIER

ADDITIONAL ALLOWANCES AND/OR DISCOUNTS MAY APPLY DEPENDING ON

FLYER-SPECIFIC FACTORS /E.G. FREQUENT FLYER STATUS/MILITARY/

CREDIT CARD FORM OF PAYMENT/EARLY PURCHASE OVER INTERNET,ETC./

YVR HDQ 5CJD 1144/11MAY STATUS-ACTIVE PRICE-SYS

PQ RQ/RS example

REQUEST:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>



</ns1:MessageData>


<ns1:Security




ACPCRTC!ICESMSLB\/CRT.LB!-


</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.7.0"


<ns1:STL_Header.RQ


<ns2:POS


<SearchParameters fetchBaggageDisclosureText="true">




</SearchParameters>


</SOAP-ENV:Body>


RESPONSE:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader

eb:version=""


<eb:From>


</eb:From>

<eb:To>


</eb:To>





<eb:MessageData>


<eb:Timestamp>2010-10-16</eb:Timestamp>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security




valueType="String">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/ACPCRT

D!ICESMSLB\/CRT.LB!-3535564741300641760!792483!0</wsse:BinarySecurityToken>

</wsse:Security>

</soap-env:Header>

<soap-env:Body>



Version="3.7.0"


<STL:STL_Header.RS

messageID="TKTHLC604-12282-774271950-1431435842521-61532-tktdoc"

timeStamp="2015-05-12T08:04:02"


<OrchestrationID

seq="1"

xmlns="http://services.sabre.com/STL/v01">TKTHLC604-12282-774271950-


<DiagnosticData


<STL:Results>

<Success

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

<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent

duty="5" sine="CJD" type="DAC">


checkDigit="5" name="SABRE AIRWAYS" number="888"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YVRTO</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YVR</ns2:WorkLocation>

<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">B539F1</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CA</ns2:IsoCountryCode>

<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WESTJET</ns2:CompanyName>

<ns2:EmployeeNumber





<ns2:Session





</ns2:Session>

</TT:Agent>


<TT:TransactionInfo


type="SALE">

<ns2:TCN


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WS</ns2:SystemProvider>

<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$F*BAXXXXXXXXXXXX1111/1218*Z

1234</ns2:InputEntry>


<TT:Ticket



type="TKT">


endorsable="false" exchangeable="false" historical="false"




retransmit="false" reverseVoid="false"

selfSale="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre

createDate="2015-05-11T00:00:00"

provider="WS">RTEGRR</TT:Sabre>

</TT:Reservation>





useTimeForPricing="true">2015-05-11T09:45:03</TT:LocalIssueDateTime>

<ns2:LastUpdate





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WS</ns2:ValidatingProvider>

<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YVR</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YVR</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory





<ns2:TicketingMode




<ns2:CouponText


<TT:BaggageDisclosure

disclosureIndicator="4">BAG ALLOWANCE -YVRYYZ-NIL/WS

1STCHECKED BAG FEE-YVRYYZ-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


2NDCHECKED BAG FEE-YVRYYZ-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


BAG ALLOWANCE -YYZYVR-NIL/WS

1STCHECKED BAG FEE-YYZYVR-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


2NDCHECKED BAG FEE-YYZYVR-CAD25.00/WS/UP TO 50 POUNDS/23 KILOGR


CARRY ON ALLOWANCE

YVRYYZ YYZYVR-01P/WS

CARRY ON CHARGES

YVRYYZ YYZYVR-WS-CARRY ON FEES UNKNOWN-CONTACT CARRIER

ADDITIONAL ALLOWANCES AND/OR DISCOUNTS MAY APPLY DEPENDING ON

FLYER-SPECIFIC FACTORS /E.G. FREQUENT FLYER STATUS/MILITARY/

CREDIT CARD FORM OF PAYMENT/EARLY PURCHASE OVER

INTERNET,ETC./</TT:BaggageDisclosure>

</TT:Details>

<TT:Customer>

<TT:Traveler

nameId="1" nameNumber="1.1">

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GELINAS/RYAN</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RYAN</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GELINAS</ns2:LastName>

<ns2:PassengerType


</TT:Traveler>

</TT:Customer>

<TT:ServiceCoupon







er>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">M</ns2:ClassOfService>

<ns2:FareBasis


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MC10</ns2:FareBasis>

<TT:StartLocation>YVR</TT:StartLocation>

<ns2:StartDateTime



<TT:EndLocation>YYZ</TT:EndLocation>

<ns2:EndDateTime









<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse


<ns2:Indicators





<ns2:StartTimeText




<ns2:Amount

currencyCode="CAD"




<TT:FareComponent





sequence="1">


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MC10</ns2:AssociatedFareBasis

>

<TT:FareProvider>WS</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>


<TT:ServiceCoupon







r>

<ns2:ClassOfService

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">G</ns2:ClassOfService>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GC14</ns2:FareBasis>

<TT:StartLocation>YYZ</TT:StartLocation>

<ns2:StartDateTime



<TT:EndLocation>YVR</TT:EndLocation>

<ns2:EndDateTime









<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:StopOver


<ns2:CouponUse


<ns2:Indicators





<ns2:StartTimeText




<ns2:Amount

currencyCode="CAD"




<TT:FareComponent






sequence="2">


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GC14</ns2:AssociatedFareBasis

>

<TT:FareProvider>WS</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<ns2:Base


<ns2:Amount

currencyCode="CAD"



</ns2:Base>

<TT:Total>

<ns2:Amount

currencyCode="CAD" decimalPlace="2"


<ns2:Text


</TT:Total>

<ns2:Tax

code="CA" exempt="false" sequence="1"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="XG" exempt="false" sequence="2"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="XT" exempt="false" sequence="3"


<ns2:Amount

currencyCode="CAD"





</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NonRefundable


<ns2:Amount

currencyCode="CAD"



</ns2:NonRefundable>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax

code="CA1" exempt="false" sequence="1"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="XG" exempt="false" sequence="2"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="RC1" exempt="false" sequence="3"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="SQ" exempt="false" sequence="4"


<ns2:Amount

currencyCode="CAD"




</ns2:Tax>

<ns2:Tax

code="YQI" exempt="false" sequence="5"


<ns2:Amount

currencyCode="CAD"





</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Endorsements

sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">NONREF - FEE FOR

CHG/CXL</ns2:Endorsements>

<ns2:Payment

sequence="1"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BA4444P20GCHG01111

1218 1234</ns2:Payment>

</TT:Remark>


<TT:Booking

duty="5" sine="CJD">

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">HDQ</ns2:WorkLocation>

<ns2:HomeLocation


</TT:Booking>




<ns2:New>YVR WS YTO378.00WS YVR290.00CAD668.00END</ns2:New>


<TT:PrintCoupon

couponType="P" printerType="0" quantity="0"

stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BBCA78</ns2:Lniata>

</TT:PrintCoupon>

<TT:Payment

paymentConfirmation="false" sequence="1"

type="CC">

<TT:Base>

<TT:Amount currencyCode="CAD"


<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>

<TT:Amount

currencyCode="CAD"


<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>

<TT:Amount

currencyCode="CAD"



<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BA4444P20GCHG01111</ns2:Remar

ks>

<TT:Card

accb="*" cardType="BA">


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">XXXXXXXXXXXX1111</ns2:MaskedC

ardNumber>

<ns2:ExpireDate


<TT:ApprovalCode

type="Z">1234</TT:ApprovalCode>

<ns2:CardBinNumber


</TT:Card>

</TT:Payment>

<TT:History

code="ALTR" number="31" sequence="2">

<TT:Agent duty="$"

sine="SYS">



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TAPE WRITE-MORE DATA

STORED IN VCR FOR T2</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RTEGRR</ns2:OldReservation>

</TT:Details>


</TT:History>

<TT:History


<TT:Agent duty="5"

sine="CJD">



<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YVR</ns2:WorkLocation>

<ns2:HomeLocation


</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$F*BAXXXXXXXXXXXX1111/1218*Z

1234</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RTEGRR</ns2:OldReservation>



</TT:Details>











</TT:History>

</TT:Ticket>

</TT:Details>


</soap-env:Body>



Pre-Ticketing Validation

Airlines can choose to have credit cards validated prior to ticket issuance.by 41st Parameter FraudNet.

When FraudNet returns to payment a code of “Verify”, the Present Credit Card (PC) indicator will be

added to the ticketing entry. The passenger will be requested to present this credit card at time of check-in.

The check-in agent will verify the credit card prior to issuing the boarding pass.

This is in addition to the current post-ticketing validation logic.

Notes :

• This will require activation. Please contact Customer Care for assistance.

• This does not apply to Travel Bank or any local issued credit cards

• *PC is used to indicate present credit card

• *PC indicator will carry forward to subsequent exchanges regardless if the FOP for the add collect is

cash or check

Native Sabre

Issue original ticket:

1.1WHITE/BETTY

1 U0 11L 25JUN Q AUHLHR HK1 255A 735A /E

2 U0 12L 02JUL Q LHRAUH HK1 930A 725P /E

PRICE QUOTE RECORD EXISTS - *PQS

U0 FACTS

1.SSR DOCS U0 HK1/DB/20JUL66/F/WHITE/BETTY

OAC - U0 AUH AO 8649122

AUH-AUH-AO.HDQ4GAI 0916/29MAY15 WYHYEI

W‡F*TPXXXXXXXXXXXX0158/1216*PC*ZAUTHAG«

OK 5265 / 21 2588 2346 6

AUTH AUTHAG

NO BOARDING PASS INFO

VERIFY CARDHOLDER SIGNATURE

Display VCR

ER«

WYHYEI

1.1WHITE/BETTY

1 U0 11L 25JUN Q AUHLHR HK1 255A 735A /E

2 U0 12L 02JUL Q LHRAUH HK1 930A 725P /E

TKT/TIME LIMIT

1.T-29MAY-AUH4GAI

2.TE 6072125882346 WHITE/B AUH4GAI 1822/29MAY

VCR COUPON DATA EXISTS *VI TO DISPLAY


U0 FACTS

1.SSR DOCS U0 HK1/DB/20JUL66/F/WHITE/BETTY

REMARKS

PCC indicator in

ticketing entry


1.XXAUTH/AUTHAG *Z

OAC - U0 AUH AO 8649122

AUH-AUH-AO.HDQ4GAI 0916/29MAY15 WYHYEI H

*TR2«

VIRTUAL COUPON RECORD

6072125882346 NAME-WHITE/BETTY

TTL NBR OF CPNS- 2 DATE OF ISSUE-29MAY15 PNR-WYHYEI 29MAY15

CC-TPXXXXXXXXXXX0158

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

1 U0 11 L 25JUN AUHLHR 255A OK LHEE4MAE OK

2O U0 12 L 02JUL LHRAUH 930A OK LHEE4MAE OK

FARE AED 4530 TAX 75AE TAX 5TP TAX 655XT

TOTAL AED 5265

FARE CALC AUH U0 LON Q54.45Q3.00 585.35U0 AUH Q3.00 585.35NUC

1231.15END ROE3.67301

FCMI-2

FORM OF PAYMENT

FOP-TPXXXXXXXXXXX0158 1216 AUTHA

G

DATE OF ISSUE-29MAY15 ISSUED AT-AUHAO AUH GAI

OAC- U0 AUH AO 8649122

ENDORSEMENTS/RESTRICTIONS-

VALID ON U0 ONLY

IT-

PRESENT CREDIT CARD

REMARKS-

ENTER VCR*CALL TO DISPLAY COUPON DETAILS

ENTER VCR*FC TO DISPLAY FARE CALC WITH TAX SUMMARY

Original Ticket Xml Request (RQ) and Response (RS)

RQ:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>

<ns1:PartyId

ns1:type="urn:x12.org:IO5:01">999999</ns1:PartyId>

</ns1:From>

<ns1:To>

<ns1:PartyId

VCR updated


ns1:type="urn:x12.org:IO5:01">123123</ns1:PartyId>

</ns1:To>



<ns1:Service

ns1:type="OTA">SabreCommandLLSRQ</ns1:Service>

<ns1:Action>SabreCommandLLSRQ</ns1:Action>

<ns1:MessageData>


<ns1:Timestamp>2001-02-15T11:15:12Z</ns1:Timestamp>

<ns1:TimeToLive>2001-02-15T11:15:12Z</ns1:TimeToLive>

</ns1:MessageData>


<ns1:Security



STSA!ICESMSLB\/STS.LB!-3528216953950718720!598888!0</ns1:BinarySecurityToken>

</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<SabreCommandLLSRQ

AltLangID="en-us" EchoToken="String" PrimaryLangID="en-us"

SequenceNmbr="1" Target="Production"

TimeStamp="2001-12-17T09:30:47-05:00" Version="2003A.TsabreXML1.6.1"

xmlns="http://webservices.sabre.com/sabreXML/2003/07">

<Request Output="SCREEN">

<HostCommand>W‡F*BA4005111111111136/1016*PC‡VCR</HostCommand>

</Request>

</SabreCommandLLSRQ>

</SOAP-ENV:Body>


RS:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader



<eb:From>

<eb:PartyId

eb:type="urn:x12.org:IO5:01">123123</eb:PartyId>

</eb:From>

<eb:To>

<eb:PartyId

eb:type="urn:x12.org:IO5:01">999999</eb:PartyId>

</eb:To>



<eb:Service

eb:type="OTA">SabreCommandLLSRQ</eb:Service>

<eb:Action>SabreCommandLLSRS</eb:Action>

<eb:MessageData>

*PC indicator

added to ticketing entry


<eb:MessageId>e58f7f5c-568c-4c9b-a4e2-c851733940f8@176</eb:MessageId>


<eb:RefToMessageId>1000</eb:RefToMessageId>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security




valueType="String">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/STSA!I


</wsse:Security>

</soap-env:Header>

<soap-env:Body>

<SabreCommandLLSRS

AltLangID="en-us" EchoToken="String" PrimaryLangID="en-us"

SequenceNmbr="1" Target="Production" TimeStamp="2015-05-20T07:19:11"

Version="2003A.TsabreXML1.6.1"

xmlns="http://webservices.sabre.com/sabreXML/2003/07">

<Response><![CDATA[OHTVBF

1.1VIJAY/ARUN

1 U0 379Y 08AUG J AUHBAH HK1 310A 325A /E

TKT/TIME LIMIT

1.T-20MAY-ETC5WBT

2.TE 6072125215282 VIJAY/A ETC5WBT 0019/20MAY

VCR COUPON DATA EXISTS *VI TO DISPLAY

PHONES

1.ETC800-555-1212-B


U0 FACTS

1.SSR FOID U0 HK1/IDABC1234

2.SSR DOCS U0 HK1/DB/07JUL2008/M/BABY/ADMAS

OAC - U0 ETC HQ 0005423

ETC-ETC-HQ.RKT5WBT 0219/20MAY15 OHTVBF H]]></Response>

</SabreCommandLLSRS>

</soap-env:Body>


Ticket Field Expansion (TFE)

Airline can issue the ticket with the increased ticket digit limiation to 10/11 Characters to match industry

levels for original issuance ticketing and exchange ticketing from the current amount limit of 8 characters.

Current maximum amount the system can handle is follows:

1. No decimal 2,147,483,647

2 decimal 21,474,836.47

3 decimal 2,147,483.647

Native Sabre

To see *PC

indicator you need to display

the VCR


Issue Original ticket with extended ticket field

• VIRTUAL COUPON RECORD

• TKT-6072126435459 ISSUED-28AUG15 CTY-ZVJHT STA-00051236

• AGNT-HDQHYG PNR- EJJJFQ/28AUG15 CTRY-AE

• OAC- U0 ZVJ HT 0005123 CRS -U0 AUH

• NAME-TEST/TWO

• TTL NBR OF CPNS- 1

• CPN A/L FLT CLS DATE BRDOFF TIME PNR BAG STATUS

• 1 9W 458 Y 29AUG15 HYDBOM 925A OK OK

• F/B-Y

•

• FARE CALC HYD 9W BOM99999999Y INR99999999END

• FCMI-1 TICKETED PSGR TYPE-ADT PRICED PSGR TYPE-ADT

•

• BASE FARE INR 99999999

• EQUIV PAID AED 5531400

• TFC TOTAL AED 1199999988 XT TTL AED 999999990

• TICKET TOTAL AED 1205531388

• FEE TOTAL AED 0

• GRAND TOTAL AED 1205531388

•

• TAXES/FEES/CARRIER-IMPOSED CHARGES-TFC

• AED 99999999 QQ AED 99999999 AA

• AED 99999999 ZZ AED 99999999 SS

Original Ticket with extended field - XML RQ and RS

RQ

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



<STL:POS />

<SearchParameters>

Ticket got issued

with 10 characters




</SearchParameters>


RS


<TT:Base>


<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>


<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>


<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks



</TT:Payment>


<TT:Agent>



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>




<ns2:SystemProvider


<ns2:InputMessage xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RETURNED

BY 9W</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">EJJJFQ</ns2:OldReservation>



</TT:Details>




<ns2:PreviousControllingProvider>9W</ns2:PreviousControllingProvider>




</TT:History>

Interline EMD CR13 Changes (iEMD CR13)

Sabre hosted carriers will be able to retrieve the paper document for AE (Air Extra) items like MSR, EXB

etc..

GetTicketingDocumentRQ/RS Web Service got extended to retrieve other documents types as well, apart

from existing basic primary documents which are TKT, EMD, VOU

Starting from TKTDOC schema 3.9.0, we have added three groups, wich are as below:

• MISC group: MSR, EXB

• Refund group: CCR, XXX, REV, MCO, RFD

• Other group: TUR, FIM, MPD, SST, PTA

RQ and RS Example

RQ




<STL:POS />

<SearchParameters>



</SearchParameters>


RS

TT:OtherDocument accountingCode="888" checkDigit="4" formNumber="88"

number="8888888888888" serialNumber="88888888" type="TUR">

<TT:Indicators

electronic="false" manualAdd="true" manualUpdate="false"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre createDate="2015-09-02T07:00:00" provider="AAT">IIUNTJ</TT:Sabre>

</TT:Reservation>




Through TKTDoc WS,

we are able to retrieve

TUR document


<ns2:LocalIssueDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2015-

09-02T16:17:36</ns2:LocalIssueDateTime>



<ns2:ValidatingProvider checkDigit="5" name="SABRE AIRWAYS" number="888"


<ns2:CouponText


</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOSEKRISHNAJENASANDEEP/JENASA

</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JENASA</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOSEKRISHNAJENASANDEEP</ns2:L

astName>

</TT:Traveler>

<ns2:Purchaser xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Name>BOSEKRISHNAJENASANDEEP/JENASA</ns2:Name>

<ns2:FirstName>JENASA</ns2:FirstName>

<ns2:LastName>BOSEKRISHNAJENASANDEEP</ns2:LastName>

</ns2:Purchaser>

</TT:Customer>

<TT:ServiceCoupon

coupon="1">





r>




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">286</ns2:OperatingFlightNumbe

r>


<ns2:FareBasis


<ns2:StartLocation


<ns2:StartDateTime xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2001-09-


<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BLR</ns2:EndLocation>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TUR</ns2:TicketDesignator>

</TT:ServiceCoupon>


Service Coupon Status to track non EMD documents

To track the status of service coupons of non-EMD docuements like TUR, FIM, MPD etc , below two

elements have been added:

1. Current Status

2. Previous Status

3.13.2.1 RQ and RS example

REQUEST:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>





<ns1:MessageData>


<ns1:Timestamp>2001-02-15T 11:15:12Z</ns1:Timestamp>

</ns1:MessageData>


<ns1:Security




</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>


Version="3.10.0"


<ns1:STL_Header.RQ



<SearchParameters>



</SearchParameters>


</SOAP-ENV:Body>



RESPONSE:


<soap-env:Envelope


<soap-env:Header>

<eb:MessageHeader

eb:version=""


<eb:From>


</eb:From>

<eb:To>


</eb:To>





<eb:MessageData>


<eb:Timestamp>2001-02-15T 11:15:12Z</eb:Timestamp>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security






</wsse:Security>

</soap-env:Header>

<soap-env:Body>


Version="3.10.0"


<STL:STL_Header.RS


timeStamp="2016-02-17T02:14:47"


<OrchestrationID

seq="1"



<DiagnosticData


<STL:Results>

<Success

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

<System>T2</System>


</Success>

</STL:Results>



<TT:Details>

<TT:Agent

duty="5" sine="WBT" type="KSK">





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ETCHQ</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ETC</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">RKT</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0D0312</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">US</ns2:IsoCountryCode>

<ns2:CompanyName



<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">T WEBSERVICE</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">T</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">WEBSERVICE</ns2:LastName>

<ns2:EmployeeNumber





<ns2:Session




</ns2:Session>

</TT:Agent>

<TT:TransactionInfo


type="SALE">

<ns2:TCN


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputEntry


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VIA MISC

WEBSERVICES</ns2:InputEntry>


<TT:MiscellaneousDocument



type="MSR">

<TT:Indicators commisionable="true"

electronic="false" historical="false" interlineable="false"

refundable="R"/>

<TT:Details>

<TT:Reservation>

<TT:Sabre

createDate="2016-02-17T02:08:00"

provider="U0">EQINHD</TT:Sabre>

</TT:Reservation>







<ns2:LastUpdate






<ns2:ReasonForIssue

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">D</ns2:ReasonForIssue>

<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">V</ns2:CurrentStatus>

<TT:GovernmentTaxIdentification

idType="A">

<TT:ValueAddedTax

id="U0VATDEF12345678E"/>

<TT:Disclaimer>

<TT:Text>THIS IS SET FOR DEFAULT - RULE,FOR LONG TEXT VALIDATION

PURPOSE / FOR U0 PARTITION</TT:Text>

</TT:Disclaimer>

</TT:GovernmentTaxIdentification>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOSE/BOSE</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOSE</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOSE</ns2:LastName>

</TT:Traveler>

<ns2:Purchaser


<ns2:Name>BOSE/BOSE</ns2:Name>

<ns2:FirstName>BOSE</ns2:FirstName>

<ns2:LastName>BOSE</ns2:LastName>


</ns2:Purchaser>

</TT:Customer>

<TT:ServiceCoupon

coupon="1">

<ns2:MarketingProvider checkDigit="5"

name="SABRE AIRWAYS" number="888"




r>



<ns2:ClassOfService


<ns2:StartLocation


<ns2:StartDateTime



<ns2:EndLocation


<ns2:CurrentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VOID</ns2:CurrentStatus>

<ns2:PreviousStatus


</TT:ServiceCoupon>

<TT:Miscellaneous>

<TT:Fee

coupon="1" description="BOOKING AND SERVICE FEE DOM"

quantity="1">

<TT:Base>

<TT:Amount

currencyCode="AED"

decimalPlace="0">20</TT:Amount>

<ns2:Text

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">20</ns2:Text>

</TT:Base>

<TT:TotalTax>

<TT:Amount

currencyCode="AED"


<ns2:Text


</TT:TotalTax>

<TT:Total>

<TT:Amount

currencyCode="AED"


<ns2:Text


</TT:Total>


</TT:Fee>

<TT:OptionalService

group="99" journU0Type="S"

reason="986">

<TT:FeeProvider>U0</TT:FeeProvider>

<TT:Indicators

consumed=" " feeOverride="false"

taxExempt="false"/>

</TT:OptionalService>

</TT:Miscellaneous>

<TT:Amounts>

<TT:New>

<ns2:Base


<ns2:Amount

currencyCode="AED"

decimalPlace="0">20</ns2:Amount>



</ns2:Base>

<TT:Total>

<ns2:Amount

currencyCode="AED" decimalPlace="0"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">20</ns2:Amount>

<ns2:Text


<ns2:ApplyCreditInd


</TT:Total>

</TT:New>

</TT:Amounts>

<TT:ValueCalculation/>

<TT:Payment

sequence="1" type="CA">

<TT:Base>

<TT:Amount

currencyCode="AED"


<ns2:ApplyCreditInd


</TT:Base>

<TT:Total>

<TT:Amount

currencyCode="AED"


<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CA</ns2:Remarks>

<TT:Cash


</TT:Payment>

<TT:History



<TT:Agent duty="5"

sine="WBT">



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VIA MISC

WEBSERVICES</ns2:InputMessage>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">EQINHD</ns2:OldReservation>

<ns2:AccountingCode


</TT:Details>

</TT:History>

<TT:History

code="VD" number="22" sequence="1">

<TT:Agent duty="4"

sine="WBT">



<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime




<ns2:SystemProvider



<TT:Details>



Document>

<ns2:CurrentDocumentStatus

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">V</ns2:CurrentDocumentStatus>

</TT:Details>

</TT:History>

</TT:MiscellaneousDocument>

</TT:Details>


</soap-env:Body>


Passenger Itinerary Receipt (PIR)

It is important that passengers traveling on an electronic ticket receive a passenger itinerary receipt for the

following reasons:

As proof of purchase

Airport check-in sometimes requires it

To provide an air itinerary for the passengers’ ticketing flights

To provide a legal document for business expense or tax purposes

To improve security by eliminating the need for paper-based travel documents

PIR data will be available in Sabre’s ticketing database for 13 months after the “Date of Issue” of an

electronic ticket or EMD.

The following features are offered:

Search for a PIR with document number. User can also put additional filters like Local Issue Date,

Work Location and Last Name but document number is a mandatory field.

Provide access to subscriber eTicket/EMD details including baggage disclosure, mandate text,

header text, disclaimer text, US DOT, HAZMAT text, Fiscal and Data Protection Notice.

Branch Access Security For agencies.

Expansion of select elements to improve readability

A PIR can be requested by any agency, including ARC.

If the PIR data is not present in the T2 database when the PIR service is used, an error message will

be returned: “Not found”

When we we fail to get the latest information on Operating carrier we display the warning message

“Internal DSS Call request ended with an error”

Recommended version for PIR is 3.23.0 and above.


Search Parameters for PIR document

The Passenger Itinerary Record search parameters include:

• DocumentNumber o maximum number of documents that can be requested in one transaction is 4.

• DocumentNumber and LocalIssueDate (date when ticket was issued) • DocumentNumber and WorkLocation (PCC) • DocumentNumber and LocalIssueDate and WorkLocation (PCC)

It is not possible to search for a PIR using only the following parameters:

• WorkLocation (PCC) only • LocalIssueDate only

An agency will be able to request a PIR from its own PCC and from authorized branch PCCs.

The Web Service will always use a PCC for Travel Agency requests. If the requestor does not include a PCC in the search criteria (e.g. to access a branch’s document), then the requestor’s home PCC will be used.

Only those documents matching the selection criteria will be returned in the response.

Result Type

To search for a PIR, you must input the Result Type “P”.

PIR – provides full information for a Passenger Itinerary Receipt document, including baggage disclosure text and other mandated text.

For this Result Type, the maximum number of documents returned is 4.

If the User does not specify a Result Type, the default Result Type will be “P”.

Sample eTicket/EMD PIR

3.14.3.1 PIR RQ/RS for eTKT

Below is the sample for a ticket issued from dutch agency and PIR requested from the same with resultType=”P” and search parameter as just document number. RQ





<SearchParameters resultType="P">



</SearchParameters>


RS






xmlns:fn="http://www.w3.org/2005/xpath-functions"








<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:PassengerItineraryReceipt>

<TT:Agent duty="*" sine="HG6">

<ns2:TicketingProvider checkDigit="6" name="SABRE "

number="153"


<ns2:IataNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">4DQ1</ns2:WorkLocation>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">NL</ns2:IsoCountryCode>

<TT:CompanyName>OPPENHEIM TRAVEL</TT:CompanyName>

</TT:Agent>

<TT:Ticket accountingCode="074" number="8882023350558"

numberOfServiceCoupons="1" type="TKT">

<TT:Details>

<TT:Reservation>

<ns2:Sabre createDate="2019-02-20T00:00:00" provider="AA"

purgeDate="2019-02-20T00:00:00"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FIQZQR</ns2:Sabre>

</TT:Reservation>




<TT:ValidatingProvider name="Sabre Airways">U0</TT:ValidatingProvider>

<TT:MandateInfo type="Disclaimer">

<TT:Text language="EN">NOTICE












THE CARRIER. CHECK WITH YOUR CARRIER FOR MORE INFORMATION.</TT:Text>

</TT:MandateInfo>

<TT:MandateInfo type="HazardousMaterials">

<TT:Text language="NL">HET BIJ ZICH HEBBEN VAN GEVAARLIJKE STIFFEN

ZOALS AEROSOLEN, VUURWERK EN ONTVLAMBARE VLOEISTOFFEN, AAN BOORD VAN HET

VLIEGTUIG IS VERBODEN. INDIEN DEZE VOORSCHRIFTEN NIET DUIDELIJK ZIJN,

GELIEVE DAN VOOR MEER INFORMATIE CONTACT OP TE NEMEN MET DE

AIRLINE.</TT:Text>

</TT:MandateInfo>

<TT:MandateInfo type="DataProtectionNotice">

<TT:Text language="EN">DATA PROTECTION NOTICE: YOUR PERSONAL DATA WILL

BE PROCESSED IN ACCORDANCE WITH THE APPLICABLE CARRIER’S PRIVACY POLICY AND,

IF YOUR BOOKING IS MADE VIA A RESERVATION SYSTEM PROVIDER (“GDS”), WITH ITS

PRIVACY POLICY. THESE ARE AVAILABLE AT




DISCLOSED AND TRANSFERRED.</TT:Text>

</TT:MandateInfo>

<ns2:ItineraryType


</TT:Details>

<TT:Customer>


<ns2:Name xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JAIN/SUJAT

MR</ns2:Name>

<ns2:FirstName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SUJAT

MR</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JAIN</ns2:LastName>


</TT:Traveler>

</TT:Customer>

<TT:ServiceCoupon coupon="1">

<TT:MarketingProvider name="Sabre Airways">U0</TT:MarketingProvider>



mber>

<TT:OperatingProvider name="Sabre Airways">U0</TT:OperatingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1017</ns2:OperatingFlightNu

mber>

<ns2:ClassOfService name="ECONOMY"


<Cabin name="ECONOMY" xmlns="http://www.sabre.com/ns/Ticketing/DC"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y</Cabin>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YWKWNL</ns2:FareBasis>

<ns2:StartLocation name="AMSTERDAM"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AMS</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation name="LONDON HEATHROW"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">LHR</ns2:EndLocation>










<ns2:BookingStatus name="CONFIRMED"


<ns2:CurrentStatus


<ns2:Reservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TXCAHS</ns2:Reservation>

<ns2:BagAllowance


</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<TT:Base>



<ns2:Text


</TT:Base>

<TT:TotalTax>



<ns2:Text


</TT:TotalTax>

<TT:Total>



<ns2:Text


</TT:Total>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax code="YQ" exempt="false" sequence="1" status="N">



<ns2:Text


</TT:Tax>

<TT:Tax code="CJ" exempt="false" name="SECURITY SERVICE CHARGE"

sequence="2" status="N">



<ns2:Text


</TT:Tax>

<TT:Tax code="RN" exempt="false" name="PASSENGER SERVICE CHARGE"

sequence="3" status="N">




<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<TT:Endorsements sequence="1">NONENDO/NONREF</TT:Endorsements>

</TT:Remark>

<TT:FareCalculation>

<TT:New>AMS KL LON368.01NUC368.01END ROE0.874972</TT:New>

</TT:FareCalculation>


<ns2:Booking duty="*" sine="HG6"


<ns2:WorkLocation>4DQ1</ns2:WorkLocation>


<ns2:HomeLocation>4DQ1</ns2:HomeLocation>

</ns2:Booking>



<ns2:Total xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



</ns2:Total>

<TT:Remarks>CA</TT:Remarks>

<ns2:Cash CashIndicator="true"


</TT:Payment>

</TT:Ticket>

</TT:PassengerItineraryReceipt>


3.14.3.2 PIR RQ/RS for an EMD

Below is the sample of an EMD PIR RQ


Version="3.23.0"


<ns1:STL_Header.RQ


<ns2:POS





<DocumentType>EMD</DocumentType>


</SearchParameters>


RS





xmlns:fn="http://www.w3.org/2005/xpath-functions"








<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>



<TT:Agent duty="9" sine="HIO">

<ns2:TicketingProvider checkDigit="6" name="SABRE "

number="153"


<ns2:IataNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">D6GI</ns2:WorkLocation>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FR</ns2:IsoCountryCode>

<TT:CompanyName>VERSAILLES VOYAGE</TT:CompanyName>

</TT:Agent>

<TT:ElectronicMiscDocument accountingCode="888" number="8883055642334"

numberOfServiceCoupons="1" type="EMD">

<TT:Details>

<TT:Reservation>

<ns2:Sabre createDate="2019-02-20T00:00:00" provider="U0"

purgeDate="2019-04-07T00:00:00"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">JPKSII</ns2:Sabre>

</TT:Reservation>




<TT:ValidatingProvider name="JET AIRWAYS (INDIA)

LIMI">9W</TT:ValidatingProvider>

<ns2:ElectronicMiscType

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">A</ns2:ElectronicMiscType>


<ns2:ReasonForIssue name="Baggage"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">C</ns2:ReasonForIssue>


<TT:Text language="US">NOTICE

WHERE THIS DOCUMENT IS ISSUED FOR TRANSPORTATION, OR SERVICES OTHER THAN

PASSENGER AIR TRANSPORTATION, SPECIFIC TERMS AND CONDITIONS MAY APPLY. THESE

TERMS AND CONDITIONS MAY BE PROVIDED SEPARATELY OR MAY BE OBTAINED FROM THE

ISSUING COMPANY OR AGENT.</TT:Text>

</TT:MandateInfo>


<TT:Text language="FR">AVIS RELATIF À LA PROTECTION DES DONNÉES :

VOS DONNÉES PERSONNELLES SONT TRAITÉES CONFORMÉMENT À LA POLITIQUE DE

CONFIDENTIALITÉ APPLICABLE DU TRANSPORTEUR ET, SI VOTRE RÉSERVATION A ÉTÉ

EFFECTUÉE VIA UN FOURNISSEUR DE SYSTÈME DE RÉSERVATION (« GDS »), À LA

POLITIQUE DE CONFIDENTIALITÉ DE CELUI-CI. CELLES-CI SONT DISPONIBLES SOUS

HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY OU DIRECTEMENT SUR LE SITE DU

FOURNISSEUR / GDS. VEUILLEZ PRENDRE CONNAISSANCE DE CETTE DOCUMENTATION

S'APPLIQUANT À VOTRE RÉSERVATION ET PRÉCISANT NOTAMMENT LA FAÇON DONT VOS

DONNÉES PERSONNELLES SONT COLLECTÉES, STOCKÉES, UTILISÉES, DIVULGUÉES ET

TRANSFÉRÉES.</TT:Text>

<TT:Text language="EN">DATA PROTECTION NOTICE: YOUR PERSONAL DATA

WILL BE PROCESSED IN ACCORDANCE WITH THE APPLICABLE CARRIER’S PRIVACY POLICY

AND, IF YOUR BOOKING IS MADE VIA A RESERVATION SYSTEM PROVIDER (“GDS”), WITH

ITS PRIVACY POLICY. THESE ARE AVAILABLE AT




DISCLOSED AND TRANSFERRED.</TT:Text>

</TT:MandateInfo>

<ns2:ItineraryType


</TT:Details>

<TT:Customer>


<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DCD/DCD</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DCD</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DCD</ns2:LastName>


</TT:Traveler>

</TT:Customer>

<TT:Miscellaneous>

<TT:Fee coupon="1" description="UPTO33LB 15KG BAGGAGE" quantity="1"/>

<TT:OptionalService group="BG" groupDescription="Baggage"

journeyType="P" reason="0C1">

<ns2:FeeProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:FeeProvider>

</TT:OptionalService>


<TT:MarketingProvider name="Sabre Airways">U0</TT:MarketingProvider>



ber>

<TT:OperatingProvider/>


<ns2:ClassOfService name="ECONOMY"


<Cabin name="ECONOMY" xmlns="http://www.sabre.com/ns/Ticketing/DC"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y</Cabin>

<ns2:StartLocation name="DELHI"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DEL</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation name="MUMBAI"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOM</ns2:EndLocation>

<ns2:EndDateTime



<ns2:BookingStatus name="CONFIRMED"


<ns2:CurrentStatus


</TT:ServiceCoupon>

<TT:AssociatedTicketNumber associationType="A"

couponNumber="1">8882758714839</TT:AssociatedTicketNumber>

</TT:Miscellaneous>

<TT:Amounts>

<TT:New>

<TT:Base>

<ns2:Amount currencyCode="INR" decimalPlace="0"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">5726</ns2:Amount>

<ns2:Text


</TT:Base>

<TT:TotalTax>



<ns2:Text


</TT:TotalTax>

<TT:Equivalent>



<ns2:Text


</TT:Equivalent>

<TT:Total>



<ns2:Text


</TT:Total>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax code="K3" exempt="false" name="GOODS AND SERVICE TAX

INTERIM" sequence="1" status="N">




<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">REFUNDABLE</ns2:Endorsement

s>

</TT:Remark>

<TT:ValueCalculation>

<ns2:New xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DEL 9W

BOM70.82EUR70.82END</ns2:New>

</TT:ValueCalculation>

<TT:Payment sequence="1" type="CC">

<TT:Total>

<TT:Amount currencyCode="EUR" decimalPlace="2">74.36</TT:Amount>

<ns2:ApplyCreditInd


</TT:Total>


<TT:MaskedCardNumber>XXXXXXXXXXXX1110</TT:MaskedCardNumber>

<ns2:ExpireDate


<ns2:ApprovalCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">Y91957</ns2:ApprovalCode>

</TT:Card>

</TT:Payment>


<TT:Agent duty="9" sine="HIO">



<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">D6GI</ns2:WorkLocation>

<ns2:HomeLocation


</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">1S</ns2:SystemProvider>

<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$EMD*AE1$F*VIXXXXXXXXXXXX1

110/XXXX+</ns2:InputMessage>


<TT:Details>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">5893055642334</ns2:Supporti

ngDocument>

</TT:Details>





<ns2:PreviousStatus>RQ</ns2:PreviousStatus>


</TT:History>

</TT:ElectronicMiscDocument>



Passenger Notices

The web service ‘GetTicketingDocumentRQ’ under ‘TicketingDocumentServiceRQ’ will return data

passenger notices when requesting a Passenger Itinerary Receipt (PIR) for Tickets and EMDs.

This feature is available as part of ‘TicketingDocumentServices’ web service schema version V3.23.0

onwards.

The following passenger notices are returned in all GetTicketingDocument service responses where the

requestor has selected result type ‘P’ (PIR Details).

Hazmat (not applicable for EMD)

Montreal Disclaimer

DataProtectionNotice

The x-paths for data disclosure text for eTicket and EMD are:

- GetTicketingDocumentRS/PassengerItineraryReceipt/Ticket/Details/MandateInfo@Type

- GetTicketingDocumentRS/PassengerItineraryReceipt/ElectronicMiscDocument/Details/MandateInfo@Type

3.14.4.1 Passenger Notice Translation – Montreal Disclaimer / Data Protection

The Montreal Disclaimer and the Data Protection notices will be returned in every response. The following

languages are supported by the service:

English

Polish

French

German

Portuguese

Italian

Spanish

The requestor’s PCC country will determine the language(s) returned in the response as per the table below

and the service returns the notice in the language corresponding to PCC country along with the English

language version of the disclaimer.


If the requestor’s PCC country is not configured in the table, it will default to and return English language

only.

The following matrix indicates the country codes and the associated translation.

Country Code Mandate Info Type Language Code

US D,G EN

ES D,G ES

GT D,G ES

MX D,G ES

CL D,G ES

CA D,G FR

FR D,G FR

PL D,G PL

DE D,G DE

IT D,G IT

BR D,G PT

PT D,G PT

Note :- Any country not listed in the “Country Code” column will default to English language.

The “Country Code” associated to the following disclaimer types has been modified to “optional” and is no

longer retuned in the service response:

Montreal Disclaimer

DataProtectionNotice

3.14.4.2 Passenger Notice Translation – HAZMAT

The HAZMAT notice will be returned on all ticketing PIRs. HAZMAT is not returned on EMD PIRs. The

HAZMAT notice is transalted into the following languages:-

English

Dutch

French

German

Portuguese

Italian

Spanish

The requestor’s PCC country will determine the language(s) returned in the response as per the table below

and the service returns the notice in the language corresponding to PCC country.


If the requestor’s PCC country is not configured in the table, it will default to and return English language

only.

The following matrix indicates the country codes and the associated translation.

Country Code Mandate Info Type Language Code

US Z EN

ES Z ES

GT Z ES

MX Z ES

CL Z ES

CA Z FR

FR Z FR

PL Z PL

NL Z NL

DE Z DE

IT Z IT

BR Z PT

PT Z PT

Note :- Any country not listed in the “Country Code” column will default to English language.

The “Country Code” associated to the following disclaimer types has been modified to “optional” and is no

longer retuned in the service response:

HAZMAT

3.14.4.3 Examples of Passenger Notices in ‘GetTicketingDocumentRQ’ service

Below are the examples to illustrate how passenger notices are returned in the PIR service response.

3.14.4.3.1 Ticket PIR - Example #1

Scenario: A PIR is requested for a ticket issued in a USA agency.

GetTicketingDocumentRQ web service - Request and Response

Request


xmlns="http://www.sabre.com/ns/Ticketing/DC" Version="3.23.0>



<STL:POS />




</SearchParameters>


The requestor will receive the data protection disclosure text information in “English language” as the PCC

is based the USA. The service will also return the two letter language code ‘EN’ for English language.

Also note that the “Country Code” field is not returned for the MadateInfo types “Disclaimer” and

“DataProtectionNotice”.

Response

<TT:Details>

<ns2:TourNumber>MANUT4171</ns2:TourNumber>

<TT:Reservation>

<ns2:Sabre createDate="2018-01-03T00:00:00" provider="1S" purgeDate="2018-

02-01T00:00:00">ZGCAZE</ns2:Sabre>

</TT:Reservation>


<TT:ValidatingProvider name="Sabre Airways">1S</TT:ValidatingProvider>

<ns2:AgencyBillingNumber>1234567890</ns2:AgencyBillingNumber>

<ns2:InvoiceNumber>0576565</ns2:InvoiceNumber>

<ns2:MandateInfo type="Disclaimer">

<ns2:Text language="EN">NOTICE

CARRIAGE AND OTHER SERVICES PROVIDED BY THE CARRIER ARE SUBJECT TO CONDITIONS

OF CARRIAGE, WHICH ARE HEREBY INCORPORATED BY REFERENCE. THESE CONDITIONS MAY

BE OBTAINED FROM THE ISSUING CARRIER. PASSENGERS ON A JOURNEY INVOLVING AN

ULTIMATE DESTINATION OR A STOP IN A COUNTRY OTHER THAN THE COUNTRY OF DEPARTURE

ARE ADVISED THAT INTERNATIONAL TREATIES KNOWN AS THE MONTREAL CONVENTION, OR ITS

PREDECESSOR, THE WARSAW CONVENTION, INCLUDING ITS AMENDMENTS /THE WARSAW

CONVENTION SYSTEM/MAY APPLY TO THE ENTIRE JOURNEY, INCLUDING ANY PORTION THEREOF

WITHIN A COUNTRY. FOR SUCH PASSENGERS, THE APPLICABLE TREATY, INCLUDING SPECIAL

CONTRACTS OF CARRIAGE EMBODIED IN ANY APPLICABLE TARIFFS, GOVERNS AND MAY LIMIT

THE LIABILITY OF THE CARRIER. CHECK WITH YOUR CARRIER FOR MORE

INFORMATION.</ns2:Text>

</ns2:MandateInfo>

<ns2:MandateInfo type="DataProtectionNotice">

<ns2:Text language="EN">DATA PROTECTION NOTICE: YOUR PERSONAL DATA WILL BE

PROCESSED IN ACCORDANCE WITH THE APPLICABLE CARRIER’S PRIVACY POLICY AND, IF

YOUR BOOKING IS MADE VIA A RESERVATION SYSTEM PROVIDER (“GDS”), WITH ITS PRIVACY

POLICY. THESE ARE AVAILABLE AT HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY OR FROM

THE CARRIER OR GDS DIRECTLY. YOU SHOULD READ THIS DOCUMENTATION, WHICH APPLIES

TO YOUR BOOKING AND SPECIFIES, FOR EXAMPLE, HOW YOUR PERSONAL DATA IS COLLECTED,

STORED, USED, DISCLOSED AND TRANSFERRED.

</ns2:Text>

</ns2:MandateInfo>

<ns2:MandateInfo type="HazardousMaterials">

<ns2:Text language="EN">THE CARRIAGE OF CERTAIN HAZARDOUS MATERIALS, LIKE

AEROSOLS, FIREWORKS, AND FLAMMABLE LIQUIDS, ABOARD THE AIRCRAFT IS FORBIDDEN.


IF YOU DO NOT UNDERSTAND THESE RESTRICTIONS, FURTHER INFORMATION MAY BE

OBTAINED FROM YOUR AIRLINE.</ns2:Text>

</ns2:MandateInfo>

</TT:Details>

3.14.4.3.2 Ticket PIR - Example #2

Scenario: A PIR is requested for a ticket issued in a French agency.


Request




<STL:POS />



<DocumentNumber> 8885131415321</DocumentNumber> </SearchParameters>


The requestor will receive the passenger notices in both “English language” and “French language” as the

PCC is based the France. The service will also return the two letter language code ‘EN’ for the English

language verbiage and “FR” for the French language verbiage.


“DataProtectionNotice” and “Hazmat”.

Response

<TT:Details>

<TT:Reservation>

<ns2:Sabre createDate="2019-02-20T00:00:00" provider="AA"

purgeDate="2019-05-20T00:00:00"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FHGBAE</ns2:Sabre>

</TT:Reservation>






<TT:Text language="FR">CONDITIONS DU CONTRAT ET AUTRES INFORMATIONS

IMPORTANTES

LE TRANSPORT ET LES SERVICES SUPPLEMENTAIRES FOURNIS PAR LA COMPAGNIE SONT

SOUMIS AUX CONDITIONS DE TRANSPORT PRESENTEES ICI A TITRE DE REFERENCE.

CELLES-CI PEUVENT ETRE OBTENUES AUPRES DE LA COMPAGNIE EMETTRICE. LES

PASSAGERS EFFECTUANT UN VOYAGE VERS UNE DESTINATION FINALE OU INCLUANT UN

ARRET DANS UN AUTRE PAYS QUE CELUI DE DEPART SONT INFORMES QUE LES CONVENTIONS

CONNUES SOUS LE NOM DE COVENTION DE MONTREAL, OU CONVENTION DE VARSOVIE QUI L

A PRECEDEE, INCLUANT SES AMENDEMENTS /LE SYSTEME CONVENTION DE VARSOVIE/

PEUVENT SAPPLIQUER AL ENSEMBLE DU VOYAGE, Y COMPRIS TOUTE PARTIE DE CELUI-CI


EFFECTUEE DANS UN MEME PAYS. POUR CES PASSAGERS, LA CONVENTION APPLICABLE,

INCLUANT LES CONTRATS SPECIFIQUES DE TRANSPORT LIES A TOUT TARIF APPLICABLE,

REGIT ET PEUT LIMITER LA RESPONSABILITE DE LA COMPAGNIE. VEUILLEZ CONSULTER LA

COMPAGNIE AFIN D OBTENIR DES INFORMATIONS COMPLEMENTAIRES.</TT:Text>





ULTIMATE DESTINATION OR A STOP IN A COUNTRY OTHER THAN THE COUNTRY OF

DEPARTURE ARE ADVISED THAT INTERNATIONAL TREATIES KNOWN AS THE MONTREAL

CONVENTION, OR ITS PREDECESSOR, THE WARSAW CONVENTION, INCLUDING ITS

AMENDMENTS /THE WARSAW CONVENTION SYSTEM/MAY APPLY TO THE ENTIRE JOURNEY,

INCLUDING ANY PORTION THEREOF WITHIN A COUNTRY. FOR SUCH PASSENGERS, THE

APPLICABLE TREATY, INCLUDING SPECIAL CONTRACTS OF CARRIAGE EMBODIED IN ANY

APPLICABLE TARIFFS, GOVERNS AND MAY LIMIT THE LIABILITY OF THE CARRIER. CHECK

WITH YOUR CARRIER FOR MORE INFORMATION.</TT:Text>

</TT:MandateInfo>


<TT:Text language="FR">LE TRANSPORT DE CERTAINS PRODUITS DANGEREUX, TELS

QUE LES AEROSOLS, FEUX D'ARTIFICES ET LIQUIDES INFLAMMABLES, EST STRICTEMENT

INTERDIT A BORD DE L'APPAREIL. SI VOUS NE COMPRENEZ PAS CES RESTRICTIONS,

VOTRE COMPAGNIE AERIENNE POURRA VOUS FOURNIR DE PLUS AMPLES

INFORMATIONS.</TT:Text>

</TT:MandateInfo>


<TT:Text language="FR">AVIS RELATIF À LA PROTECTION DES DONNÉES : VOS

DONNÉES PERSONNELLES SONT TRAITÉES CONFORMÉMENT À LA POLITIQUE DE

CONFIDENTIALITÉ APPLICABLE DU TRANSPORTEUR ET, SI VOTRE RÉSERVATION A ÉTÉ

EFFECTUÉE VIA UN FOURNISSEUR DE SYSTÈME DE RÉSERVATION (« GDS »), À LA

POLITIQUE DE CONFIDENTIALITÉ DE CELUI-CI. CELLES-CI SONT DISPONIBLES SOUS

HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY OU DIRECTEMENT SUR LE SITE DU

FOURNISSEUR / GDS. VEUILLEZ PRENDRE CONNAISSANCE DE CETTE DOCUMENTATION

S'APPLIQUANT À VOTRE RÉSERVATION ET PRÉCISANT NOTAMMENT LA FAÇON DONT VOS

DONNÉES PERSONNELLES SONT COLLECTÉES, STOCKÉES, UTILISÉES, DIVULGUÉES ET

TRANSFÉRÉES.</TT:Text>




PRIVACY POLICY. THESE ARE AVAILABLE AT HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY

OR FROM THE CARRIER OR GDS DIRECTLY. YOU SHOULD READ THIS DOCUMENTATION, WHICH

APPLIES TO YOUR BOOKING AND SPECIFIES, FOR EXAMPLE, HOW YOUR PERSONAL DATA IS

COLLECTED, STORED, USED, DISCLOSED AND TRANSFERRED.</TT:Text>

</TT:MandateInfo>

<ns2:ItineraryType


</TT:Details>

3.14.4.3.3 EMD – Example #1

Scenario: A PIR is requested for an EMD issued in a Bolivian agency.


Request





<STL:POS />




</SearchParameters>


The requestor will receive the passenger notices information in “English language” as the PCC is based in

Bolivia and a translated disclosure has not been configured for Bolivia. The service will also return the two

letter language code ‘EN’ for English language.


“DataProtectionNotice”.

Note: The HAZMAT passenger notice is not returned for an EMD Passenger Itinerary Receipt

Response

<TT:Details>

<TT:Reservation>

<ns2:Sabre createDate="2019-02-28T00:00:00" provider="1S"

purgeDate="2019-06-26T00:00:00"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">KOPPUZ</ns2:Sabre>

</TT:Reservation>





<ns2:AgencyBillingNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">8884567890</ns2:AgencyBilling

Number>

<ns2:InvoiceNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0053069</ns2:InvoiceNumber>













WITH YOUR CARRIER FOR MORE INFORMATION.</TT:Text>

</TT:MandateInfo>


<TT:Text language="EN">THE CARRIAGE OF CERTAIN HAZARDOUS MATERIALS,

LIKE AEROSOLS, FIREWORKS, AND FLAMMABLE LIQUIDS, ABOARD THE AIRCRAFT IS


MAY BE OBTAINED FROM YOUR AIRLINE.</TT:Text>

</TT:MandateInfo>






PRIVACY POLICY. THESE ARE AVAILABLE AT HTTP://WWW.IATATRAVELCENTER.COM/PRIVACY

OR FROM THE CARRIER OR GDS DIRECTLY. YOU SHOULD READ THIS DOCUMENTATION, WHICH

APPLIES TO YOUR BOOKING AND SPECIFIES, FOR EXAMPLE, HOW YOUR PERSONAL DATA IS

COLLECTED, STORED, USED, DISCLOSED AND TRANSFERRED.</TT:Text>

</TT:MandateInfo>

<ns2:ItineraryType


</TT:Details>

VAT for Italy

Italian Government implemented a mandate that VAT and Fiscal numbers needs to be displayed on all

printed and electronically transmitted travel and ancillary receipts, including ATB stock. The static message

must be displayed on all printed and electronically transmitted travel and ancillary receipts, except ATB

stock.

VAT ID, Fiscal ID and Static content data get stored in T2-database from PSS (host system). Based on the

query from tktdoc web service to T2-database, the required data associated with the VCR, gets populated in

the tktdoc web service response.

Sample request and response

Request: <GetTicketingDocumentRQ Version="3.11.0" requestType="D"







</SearchParameters>


</SOAP-ENV:Body>


Response: <TT:GetTicketingDocumentRS Version="3.11.0" xmlns:TT="http://www.sabre.com/ns/Ticketing/DC">







<DiagnosticData



<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>


<ns2:TicketingProvider checkDigit="6" name="SABRE AIRWAYS" number="888"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MXPAT</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MXP</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ROM</ns2:HomeLocation>

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2571A8</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IT</ns2:IsoCountryCode>

<ns2:CompanyName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ALITALIA S.A.I

S.</ns2:CompanyName>

<ns2:EmployeeNumber








</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AZ</ns2:SystemProvider>

<ns2:InputEntry

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$FCA$VCR$N1.1/2.1</ns2:Input

Entry>









selfSale="false"/>

<TT:Details>

<TT:Reservation>


provider="AZ">DZCAYY</TT:Sabre>

</TT:Reservation>









number="888"


<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MXP</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FCO</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory




<ns2:TicketingMode




<ns2:CouponText


<TT:BaggageDisclosure disclosureIndicator="6"/>

<TT:GovernmentTaxIdentification idType="A">

<TT:ValueAddedTax id="PI13029381004"/>

<TT:Fiscal id="CF13029381004"/>

<TT:Disclaimer country="IT">

<TT:Text>IVA INCLUSA NEI TERMINI DI LEGGE, OVE DOVUTA / VAT INCLUDED

IF REQUIRED ACCORDING TO LAW CONDITIONS</TT:Text>

</TT:Disclaimer>

</TT:GovernmentTaxIdentification>

</TT:Details>

<TT:Customer>


<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DUCK/DONALD</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DONALD</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DUCK</ns2:LastName>

<ns2:PassengerType


<ns2:Contact xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">


</ns2:Contact>

</TT:Traveler>


</TT:Customer>






er>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YOWFLN1</ns2:FareBasis>

<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MXP</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FCO</ns2:EndLocation>






<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText











xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YOWFLN1</ns2:AssociatedFareBa

sis>

<TT:FareProvider>AZ</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FLX1</ns2:FareRule>

<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>


<TT:New>




</ns2:Base>

<TT:Total>



<ns2:Text


</TT:Total>

<ns2:Tax code="YR" exempt="false" sequence="1"





</ns2:Tax>

<ns2:Tax code="EX" exempt="false" sequence="2"





</ns2:Tax>

<ns2:Tax code="XT" exempt="false" sequence="3"





</ns2:Tax>

</TT:New>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<ns2:Tax code="YRI" exempt="false" sequence="1"





</ns2:Tax>

<ns2:Tax code="EX" exempt="false" sequence="2"





</ns2:Tax>

<ns2:Tax code="IT1" exempt="false" sequence="3"





</ns2:Tax>

<ns2:Tax code="VT" exempt="false" sequence="4"





</ns2:Tax>


<ns2:Tax code="HB" exempt="false" sequence="5"





</ns2:Tax>

<ns2:Tax code="MJ" exempt="false" sequence="6"





</ns2:Tax>

<ns2:Tax code="FN" exempt="false" sequence="7"





</ns2:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AZ ONLY/NOT

ENDO</ns2:Endorsements>



</TT:Remark>


<ns2:New>MIL AZ ROM434.00EUR434.00END IVA INCLUSA</ns2:New>



stockType="2A">

<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BBCA78</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>


<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>


<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>


<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks



</TT:Payment>






<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>


<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage




<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DZCAYY</ns2:OldReservation>

</TT:Details>

</TT:History>





<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MXP</ns2:WorkLocation>

<ns2:HomeLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ROM</ns2:HomeLocation>

</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider


<ns2:InputMessage

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">W$FCA$VCR$N1.1/2.1</ns2:Input

Message>


<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DZCAYY</ns2:OldReservation>



</TT:Details>






</TT:History>

</TT:Ticket>

</TT:Details>


What about the verbiage output for the following :-

GDPR

Heading Text (Guatemala,Bolivia,Ecuador)

Mandated headings (Brazil, France,Mexico, French

Polynesia,Reunion,Singapore,Guatemala,Mexico)

Web Mark-up

The new element (optional) has been added as part of schema v3.11.0 under service coupon as Markup data

containing amount, currency code and decimal place.

Markup can be an amount or percentage stored in T2 database from PSS. Based on the query from tktdoc

web service to T2 database, the markup amount or percentage (not both) information gets populated in

Tktdoc web service response.

Sample request and response with Mark-up amount

Request:

<GetTicketingDocumentRQ Version="3.11.0" requestType="D"







</SearchParameters>


Response:






er>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YRTFLN1</ns2:FareBasis>


<ns2:StartLocation


<ns2:StartDateTime



<ns2:EndLocation







<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText






<TT:Markup>


<TT:Text>123.00</TT:Text>

</TT:Markup>






xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YRTFLN1</ns2:AssociatedFareBa

sis>


<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

Sample request and response with Mark-up percentage

Request:









</SearchParameters>


Response:






er>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YOWFLN1</ns2:FareBasis>

<ns2:StartLocation


<ns2:StartDateTime



<ns2:EndLocation







<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText






<TT:Markup>

<TT:PercentageRate>110.00</TT:PercentageRate>

<TT:Text>110.00</TT:Text>

</TT:Markup>







xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YOWFLN1</ns2:AssociatedFareBa

sis>


<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

Frequent Flyer Tier information

The new element (optional) “Tier” has been added with xml schema 3.11.0 under frequent flyer element.

Frequent flyer tier type gets stored in T2 database from PSS. Based on the query from tktdoc web service to

T2 database, frequent flyer tier type along with the existing frequent flyer data (frequent flyer provider and

frequent flyer number) will get populated in ticketdocumentserviceRS.


Request:








</SearchParameters>


Response:

<TT:Customer> <TT:Traveler nameId="1">

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FLIEGER/PHILS</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">PHILS</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FLIEGER</ns2:LastName>

<ns2:PassengerType


<ns2:Contact xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">


</ns2:Contact>


</TT:Traveler>

</TT:Customer>

<ns2:Affinity xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:FrequentFlyer>

<ns2:Provider>AB</ns2:Provider>


<ns2:Tier>PLT</ns2:Tier>


</ns2:Affinity>






er>




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">24</ns2:OperatingFlightNumber

>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SLRCODE</ns2:FareBasis>

<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DUS</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation










<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:PreviousStatus


<ns2:CurrentControllingProvider hosted="true"

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">U0</ns2:CurrentControllingPro

vider>

<ns2:Affinity xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:FrequentFlyer>

<ns2:Provider>AB</ns2:Provider>


<ns2:Tier>PLT</ns2:Tier>


</ns2:Affinity>

<ns2:BagAllowance



<ns2:CouponUse






xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AB</ns2:ValidatingProvider>

<ns2:StartTimeText











xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SLRCODE</ns2:AssociatedFareBa

sis>

<TT:FareProvider>AB</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

New operation IssueTicketingDocument (Fare Lock Project)

The new IssueTicketingDocumentRQ/RS operation being introduced with xml schema 3.11.0 under

TicketingDocumentServices.

This new operation will be introduced to support issuance of tickets with single and multiple forms of

payments, including tokenized credit card, clear credit card, cash, prepaid ticket and cheque. Ticket issuance

is limited to a single transaction element.

A user authorized to access IssueTicketingDocument Web Service must have an EPR with the TktDocUser

Integrated Computer Environment (ICE) attribute added through the Identity Manager (IdM) tool.

Note - Currently, this service is for airline path only and may get extended for the subscribers in future.

Pre-requisites

Prior to invoking the new ticket issuance web service, the following conditions should be met:

o The Sabre session will already be established

o The agent will be in the proper AAA location

o The agent will be set to the proper duty code

o The agent will already have a ticket printer designated

o The PNR will already be unpacked in the AAA


Once the Ticketing document issuance service is called, it will:

1. Check the form of payment

a. If credit card number is identified as a token, de-tokenize and prepare relevant FOP

section of ticketing XML request

b. Issue tickets using low level service AirTicketLLSRQ (v2.5 and above)

Valid Form of Payments – Single and Multiple FOP (MFOP)

The new operation supports issuance of tickets with single and multiple form of payments, which includes

the following -

1. Clear credit card

2. Tokenized credit card

3. Cash

4. Cheque

5. Prepaid ticket

While using MFOP, different combination of FOP’s are allowed for example - cash and tokenized credit

card, cash and cheque, etc. User should specify the amount that needs to be charged from second FOP and

remainder of the ticket price amount will auto applicable to the first FOP.

User should use minimum of one or a maximum of two forms of payment for the ticket issuance otherwise

system should return an error response.

Sample request and response – MFOP (Credit Card and Cash)

Request:

<IssueTicketingDocumentRQ Version="3.11.0"



<Transaction index="1" returnHostCommand="true">

<Payment manualApprovalCode="123456">

<Card code="IK" expireDate="2016-12" number="5555555555554444"/>

</Payment>

<Payment type="CA">

<Amount currencyCode="EUR" decimalPlace="2">100.00</Amount>

</Payment>

</Transaction>

</IssueTicketingDocumentRQ>

Response:

<TT:IssueTicketingDocumentRS Version="3.11.0"



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




<STL:Results>


<STL:Success>

<STL:System>TPF</STL:System>

<STL:Source>FulfillmentServices</STL:Source>

</STL:Success>

</STL:Results>


<TT:Transaction index="1">

<TT:Ticket>

<TT:RawTPFC status="Complete">

<STL:Success timeStamp="2016-02-02T01:11:06-06:00"



<STL:HostCommand

LNIATA="1C6C92">W?FMPCA****************/1216*Z123456*CA/100.00/0.00XT</STL:Hos

tCommand>


</STL:Success>

</TT:RawTPFC>

<TT:Messages>OK 1165.62/ 21 0000 6661 2</TT:Messages>

<TT:Messages>AUTH 123456</TT:Messages>

<TT:Messages>NO BOARDING PASS INFO</TT:Messages>

<TT:Messages>VERIFY CARDHOLDER SIGNATURE</TT:Messages>

</TT:Ticket>

</TT:Transaction>

</TT:IssueTicketingDocumentRS>

Sample request and response – MFOP (Tokenized Credit Cards)

Request:






file:///C:/T2_Souce_code/tkt_ws_schema/tktdoc/xsd/draft/TicketingDocumentServi

ces_v.3.11.0.xsd">



<Ticket/>


<Card code="VI" expireDate="2016-12" suppress="false"

tokenizedNumber="4601I00IW7LN9733"/>

</Payment>


<Card code="AX" expireDate="2016-12" suppress="false"

tokenizedNumber="372I002V7655550"/>

<Amount currencyCode="EUR" decimalPlace="2">100.00</Amount>

</Payment>

</Transaction>


Response:









<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>





<STL:HostCommand

LNIATA="13BC91">W?FMPVI****************/1216*Z123456*AX372055555555550/1216*Z1

23456/100.00/0.00XT</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>


<TT:Messages>AUTH 123456 123456</TT:Messages>



</TT:Ticket>

</TT:Transaction>


Ticket Issuance

Web Service converts the IssueDocumentService request to the corresponding AirTicketLLSRQ, which in

turn converts the request to the linear entry. Then, the linear entry is used for issuance of the ticket.

Following are the additional qualifiers for ticket issuance through IssueDocumentService.

1. Baggage Allowance

2. Certificate Number

3. Commission

4. Endorsement

5. Need Print

6. SAC (Secondary Action Code)

7. Tour Code

8. Pricing Option

9. Future Line (*It is used for subscriber path only, which is not supported currently)


3.18.2.1 Ticket Issuance by specifying Baggage Allowance

User can specify the baggage allowance on one or more segments on the ticket using pounds, kilos or pieces

in the ticketing entry,

By adding baggage allowance, user is overriding the free baggage allowance filed with ATPCO.

Linear Entry: W‡FCA‡BA*60K


Request :





<Ticket>

<BaggageAllowance weight="60"/>

</Ticket>

<Payment type="CA"/>

</Transaction>


Response:








<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>





<STL:HostCommand LNIATA="77BA99">W?FCA?BA*60K</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>



</TT:Ticket>

</TT:Transaction>



3.18.2.2 Ticket Issuance with Certificate Number

User can issue the ticket with a certificate as a form of payment to collect any fare amounts or taxes due

without having to perform an exchange with an additional collection.

User need to specify 5-13 digits as certificate number.

Linear Entry: W‡CT1234567‡FCA


Request:





<Ticket>

<Certificate number="1234567"/>

</Ticket>


<Card code="CA" expireDate="2016-12" number="5555555555554444"/>

</Payment>

</Transaction>


Response:








<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>





<STL:HostCommand

LNIATA="7C4E9C">W?F*CA****************/1216*Z123456?CT1234567</STL:HostCommand

>


</STL:Success>


</TT:RawTPFC>


<TT:Messages>AUTH 123456</TT:Messages>



</TT:Ticket>

</TT:Transaction>


3.18.2.3 Ticket Issuance with Commission

User can add a commission amount or a commission percent to the ticketing entry.

Linear Entry: W‡FCA‡KP10‡VCR


Request:





<Ticket>

<Commission>

<Percent>10</Percent>

</Commission>

</Ticket>


</Transaction>


Response:








<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>






<STL:HostCommand LNIATA="545B91">W?FCA?KP10</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>



</TT:Ticket>

</TT:Transaction>


3.18.2.4 Ticket Issuance with Endorsement

User can add upto 60 characters of free text in the Endorsements /Restrictions area of the ticket.

Linear Entry: W‡FCA‡EDCOMPANION WITH TKT 42947857847584


Request:





<Ticket>

<Endorsement override="false"> COMPANION WITH TKT

42947857847584</Endorsement>

</Ticket>


</Transaction>


Response:








<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>






<STL:HostCommand LNIATA="52E78D">W?FCA?EDCOMPANION WITH TKT

42947857847584</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>



</TT:Ticket>

</TT:Transaction>


3.18.2.5 Ticket Issuance with Need Print

User can print particular portions of ticket

Linear Entry: W‡NPA (for print auditor coupon) or W‡FCA‡VCR‡NPR (for print passenger receipt)


Request:





<Ticket>

<NeedPrint auditor="true"/>

</Ticket>


</Transaction>


Response:








<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>






<STL:HostCommand LNIATA="1FA18E">W?FCA?NPA</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>



</TT:Ticket>

</TT:Transaction>


3.18.2.6 Ticket Issuance with SAC (Secondary Action Code)

User can specify the alphanumeric character representing the special function requested.

Linear Entry: - W‡FCA*DC*ID0406MCBX11016‡VCR

Sample request and response – DCC (Dynamic Currency Conversion) as SAC

Request:





<Ticket>

<SecondaryActionCode>*DC*ID0404MCBX74105</SecondaryActionCode>

</Ticket>

<Payment manualApprovalCode="X74105">

<Card code="CA" expireDate="2016-12" number="5586520000000008"/>

</Payment>

</Transaction>


Response:








<STL:Results>

<STL:Success>

<STL:System>PSS</STL:System>


</STL:Success>


</STL:Results>



<TT:Ticket>





<STL:HostCommand

LNIATA="2A5186">W¥F*CA****************/1216*ZX74105</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>


<TT:Messages>AUTH X74105</TT:Messages>



</TT:Ticket>

</TT:Transaction>


3.18.2.7 Ticket Issuance with Tour Code

User can use the tour code, when the fare calculation line is usually not printed on the ticket or included in the

VCR. The system places the tour code in the Tour Code / IT field of the VCR

Linear Entry: W‡UBTEST123 ‡FCA


Request:





<Ticket>

<TourCode suppressFareReplaceWithBT="true">TEST123</TourCode>

</Ticket>


</Transaction>


Response:









<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>





<STL:HostCommand LNIATA="2D1693">W?FCA?UB*TEST123</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>



</TT:Ticket>

</TT:Transaction>


3.18.2.8 Ticket Issuance with Pricing Option

User can use PQ entry to save all pricing data for ticketing.

Linear entry: W‡FCA‡VCR‡PQ1


Request:





<Ticket>

<PricingOptions>

<PriceQuote>

<Record number="1"/>

</PriceQuote>

</PricingOptions>

</Ticket>


</Transaction>


Response:









<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>





<STL:HostCommand LNIATA="12DD92">W?PQ1?FCA</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>

<TT:Messages>OK 808.08/ 21 0000 6553-6554 6</TT:Messages>


</TT:Ticket>

</TT:Transaction>


Sabre Internal Use Only

Orchestration of Low Cost Carrier and Traditional Carriers. This is applicable to Travel Network

Customers only.

The IssueTicketingDocumentRQ operation in the TicketingDocumentServicesRQ service may be used

to orchestrate the fulfilment of Traditional and Low Cost carriers in a single transaction.

The service is enhanced for Sabre Travel network customers but it is available to Sabre APAC (1B) and

Infini as designed.

Fulfillment request

3.19.1.1 Form of Payment

The orchestrated service accepts credit card and account code as valid form of payments to fulfill LCC PQ’s

and accepts all other FOP’s which are supported by PSS to fulfill traditional PQ’s.

The service generates calls to AirTicketLLSRQ which generates entries into native Sabre. PSS will reject

any form of payment which is not supported based on current ticketing logic for the ticket type being issued.


Currently, the orchestrated service does not permit multiple form of payment to be input in the request. If a

request is received with a multiple form of payment then the request will be rejected. However, the PQ can

be stored with multiple forms of payment and ticket issuance will be allowed.

3.19.1.2 Direct Ticketing

When a fulfillment request is received without any reference to a PQ then the open systems orchestrator will

pass an issuance request to PSS ticketing. PSS ticketing treats such a transaction as a “Direct Ticket” and

attempt to issue the ticket.

Should the transaction fail due to missing action codes or as a result of any failed business rule applicable

to the issuing PCC then the client will receive a failure response.

If the ticket issues successfully then the client will receive a successful issuance response.

NOTE: Ticket issuance of a low cost carrier requires a PQ.

Below is an example of a Direct Ticketing:

Request





<Ticket validatingCarrier="HV">

<PricingOptions>

<PQFilter all="false" eTkt="false" lowCostCarrier="false"/>

</PricingOptions>

</Ticket>


<Card code="VI" expireDate="2020-12" number="4444333322221111"/>

</Payment>

</Transaction>


Response




xmlns:ns1="http://webservices.sabre.com/sabreXML/2011/10"

xmlns:stl="http://www.sabre.com/ns/Ticketing/DC"


xmlns:xs="http://www.w3.org/2001/XMLSchema"



issuedoc" version="3.15.0">



1487157768696-497-issuedoc</OrchestrationID>

<STL:Results>

<STL:Error status="NotProcessed" type="BusinessLogic">



</STL:Error>


</STL:Results>



<TT:Ticket>

<TT:RawTPFC status="NotProcessed">

<STL:Error timeStamp="2017-02-15T05:22:54-06:00" type="BusinessLogic">


<STL:HostCommand

LNIATA="09ED19">W?F*VI****************/1220*Z123456?AHV</STL:HostCommand>

<STL:Message>WORLDFARE AT PEAK USE - RETRY 8 SEC ‡ 032</STL:Message>

<STL:ShortText>ERR.SWS.HOST.ERROR_IN_RESPONSE</STL:ShortText>


</STL:Error>

</TT:RawTPFC>

</TT:Ticket>

</TT:Transaction>


3.19.1.3 PQ Selection

The orchestration process interrogates each PQ requested to determine its type. The two types are as follows:

E-Ticket

Low Cost Carrier (LCC)

The fulfillment request may include PQ filter parameters to indicate the types of PQ to be ticketed. These

filter parameters are:

LCC – ticket only Low Cost Carrier PQs

E-ticket – ticket only Traditional Carrier PQ

ALL – ticket both Low Cost Carrier and Traditional Carrier PQs

PQ Numbers – ticket only these specified PQs

3.19.1.3.1 “LCC” PQ Filter

A request for fulfillment may include the “LCC” parameter. The LCC parameter instructs the service to

extract only LCC PQs. It cannot be combined with the “E-ticket” parameter.

The “LCC” parameter must be combined with either the “ALL” parameter or the “PQ Numbers” parameter.

If any PQ requested is not an LCC PQ then the orchestrated service ignores such PQs and not pass them to

PSS for fulfilment. These PQs are identified as ignored in the response message.

3.19.1.3.2 “E-ticket” PQ Filter

A request for fulfillment may include the “E-ticket” parameter. The E-ticket parameter instructs the service

to extract only E-ticket PQs. It cannot be combined with the “LCC” parameter.

The “E-ticket” parameter must be combined with either the “ALL” parameter or the “PQ Numbers”

If any PQ requested is not an E-ticket PQ then the orchestrated service ignores such PQs and not pass them

to PSS for fulfilment. These PQs will be identified as ignored in the response message.


3.19.1.3.3 “ALL” PQ Filter

A request for fulfillment may include the “ALL” parameter. When the “ALL” parameter is used alone, it

instructs the service to extract all PQs, regardless of type (LCC and E-ticket).

The “ALL” parameter may be combined with either the “LCC” or “E-ticket” parameter to specify all Low

Cost Carrier PQs or all traditional carrier PQs. In this case, the service will extract all the PQs of the specified

type (LCC or E-ticket).

If any PQ requested is not the specified type then the open system will ignore such PQs and not pass them

to PSS for fulfillment. These PQs will be identified as ignored in the response message.

The “ALL” parameter cannot be combined with both “LCC” and “E-ticket” parameters in the same request.

If the request includes “ALL” and both “LCC” and “E-ticket” parameters (with or without the “PQ Numbers”

parameter), an error will be returned:

3.19.1.3.4 “PQ Numbers” Filter

A request for fulfillment may include selecting one or more PQ numbers. If the PQ Numbers parameter is

included but there is no LCC or E-ticket or ALL parameter, it will instruct the service to extract only the

specified PQs, regardless of type (LCC and E-ticket).

The “PQ Numbers” parameter may be combined with the “LCC” or “E-ticket” parameter. In this case, the

service will extract the specified PQs if they match the specified type (LCC or E-ticket). If the PQ does not

match the specified type, the web service will ignore the PQ and not pass it to PSS for fulfillment. The PQ

will be identified as ignored in the response message.

The “PQ Numbers” parameter cannot be combined with the “ALL” parameter. If the request includes both

the “PQ Numbers” and the “ALL” parameters, an error will be returned:

3.19.1.3.5 Maximum number of PQs

The orchestrated service will only permit selection of up to 9 PQs in a single request. If a request is received

which exceeds the permitted limit then the request will be rejected.

Error Response: Request business validation failed. More than 9 PQs selected. Please amend your request

and try again.

When the ALL parameter is used the system must establish if the number of active PQs is less than or equal

to 9. If greater than 9 the request will be rejected.

When the LCC or E-ticket parameter is used, with or without the ALL parameter, any PQs selected which

are not the specified type will be excluded from the PQ count.

For example:

If 20 PQs are selected with the LCC only parameter and only 8 of the PQs are of LCC type then the

transaction will commence. Rest of the PQs, which are of E-ticket type will returned as “Ignored” PQs in

the response.

If 20 PQs are selected with the E-ticket only parameter and only 8 of the PQs are of E-ticket type then the

transaction will commence.

Below is an example of the error response:

Request:





<Transaction index="1" numResponses="9" returnHostCommand="true">

<Ticket>

<PricingOptions>

<PQFilter eTkt="true"/>

<PriceQuote>











</PriceQuote>

</PricingOptions>

</Ticket>


<Card code="VI" expireDate="2018-08" number="4111111111111111"

securityCode="737" suppress="true"/>

</Payment>

</Transaction>


Response:

<IssueTicketingDocumentRS Version="3.15.0"



issuedoc" timeStamp="2017-03-02T07:23:00"


<STL:OrchestrationID seq="0">TKTHLI702-8065-526022879-1488460980045-4-

issuedoc</STL:OrchestrationID>

<STL:Results>

<STL:Error status="NotProcessed" timeStamp="2017-03-02T07:23:00"

type="Validation">

<STL:Source>IssueDoc</STL:Source>



<STL:ErrorMessage code="120017">Request content violates business

validation rules: More than 9 PQs selected. Please amend your request and try

again.</STL:ErrorMessage>

<STL:ShortText>Request content violates business validation

rules</STL:ShortText>


</STL:Error>

</STL:Results>


</IssueTicketingDocumentRS>


Issuance Process

The orchestration process handles each request in sequence.

The web service will gather data from non-deleted PQs based on the filters in the fulfillment request.

Once the data is gathered, the WS will start sending the messages to PSS.

For LCC only requests, the web service will send one message for all PQs/tickets on a single

validating carrier. If PQs with different LCC validating carriers are requested, a separate message

will be sent for each validating carrier group.

For E-ticket only requests the web service will send one message for all requested PQs.

For mixed LCC/E-ticket requests, the web service will send one message for each LCC validating

carrier, and one message for all E-ticket PQs.

PSS is the final arbiter in all cases when determining if a PQ can be ticketed. Should the transaction fail due

to missing action codes or as a result of any failed business rule applicable to the issuing PCC then the client

will receive a failure response.

3.19.2.1 Interactive Error Responses

Any fulfillment request that results in a system response requiring user input to continue processing will

constitute a “failure”. The orchestration service will not provide a default or input driven action when “user

prompt” message returned.

Examples of such responses are as follows:-

Alert to prevent duplicate ticketing

Stored Fare Expiry response

Back Date qualifier alert

Change of validating carrier alert

Passport data required alert

3.19.2.2 E-Ticket PQ selection only

When a request is received for one or more PQs which are wholly E-ticket, the web service will pass all the

requested PQs in a single ticketing command to PSS. The PQ(s) will be fulfilled together using the Multiple

PQ processing in PSS.

If one PQ in the sequence fails issuance then processing will stop and all remaining PQs will not be fulfilled.

If a PQ has expired or any other prompt requiring additional input is encountered then this will be deemed a

failure. The orchestration service is unable to interrupt processing for responses which require user

intervention.

Note: Currently, the orchestrated service may generate error conditions in case of multiple E-Ticket PQ

records. This feature may be addressed in coming web service releases.

Below is an example for fulfillment of E-Ticket PQ record.

Request:






<Ticket>

<PricingOptions>

<PQFilter eTkt="true"/>

<PriceQuote>


</PriceQuote>

</PricingOptions>

</Ticket>

<Payment>


securityCode="737" suppress="true"/>

</Payment>

</Transaction>


Response:




xmlns:ns1="http://webservices.sabre.com/sabreXML/2011/10">






<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket priceQuote="1">


<STL:Success timeStamp="2017-02-16T06:59:54-06:00">


<STL:HostCommand LNIATA="433331">W?PQ1?F*VI****************/0818-

XN?CVV1/737</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>

<TT:Messages>1OK 39.18</TT:Messages>

</TT:Ticket>

</TT:Transaction>


3.19.2.3 Low Cost Carrier (LCC) PQ selection only

For LCC carriers, if multiple passengers are in the PNR, tickets for all passengers must be issued at the same

time. All passengers must be in one PQ or in separate PQs but ticketed in the same entry.


NOTE: Since all PQs for a single carrier must be issued in the same transaction, the Auto End Transaction

TJR indicator must be disabled.

The web service will group all LCC PQs belonging to a single validating carrier and send a single ticketing

command containing the group to PSS.

Example 1:

LCC itinerary for 2 passengers, 2 PQs: PQ1 = ADT, PQ2 = C08

Web service will send ticketing command: W#PQ1/2

If LCC PQs for multiple validating carriers are requested, the web service will send a separate ticketing

command to PSS for each group.

Example 2:

LCC1 itinerary for 2 passengers, PQ1 = ADT, PQ2 = C08

LCC2 itinerary for 2 passengers, PQ3 = ADT, PQ4 = C08

Web service will send 2 ticketing commands: W#PQ1/2 and W#PQ3/4

Each PQ group (or single PQ if only one is present) will be fulfilled one at a time.

If a PQ within the group fails issuance then all PQs within the group fail.

If a PQ has expired or any other prompt requiring additional input is encountered then this will be deemed a

failure. The orchestration service is unable to interrupt processing for responses which require user

intervention and will continue with ticket issuance for the subsequent specified PQs.

Below is an example for fulfillment of Low Cost Price Quote Record.

Request:

<IssueTicketingDocumentRQ xmlns="http://www.sabre.com/ns/Ticketing/DC"




TicketingDocumentServices_v.3.15.0.xsd" Version="3.15.0">



<Ticket>

<PricingOptions>

<PQFilter lowCostCarrier="true"/>

<PriceQuote>



</PriceQuote>

</PricingOptions>

</Ticket>

<Payment type="CC" manualApprovalCode="123456">

<Card code="VI" securityCode="737" expireDate="2018-08"

number="4111111111111111"/>

</Payment>

</Transaction>


Response:


TT:IssueTicketingDocumentRS xmlns:TT="http://www.sabre.com/ns/Ticketing/DC"




<STL:STL_Header.RS messageID="D681P882-10472-988899102-1488459072659-7-


<OrchestrationID xmlns="http://services.sabre.com/STL/v01" seq="0">D681P882-

10472-988899102-1488459072659-7-issuedoc</OrchestrationID>

<STL:Results>

<STL:Success>



</STL:Success>

</STL:Results>



<TT:Ticket>

<TT:PriceQuote number="1"/>




<STL:HostCommand

LNIATA="61FB39">W¥PQ1¥F*VI****************/0818*Z123456¥CVV1/737</STL:HostComm

and>


</STL:Success>

</TT:RawTPFC>


</TT:Ticket>

<TT:Ticket>





<STL:HostCommand

LNIATA="61FB39">W¥PQ2¥F*VI****************/0818*Z123456¥CVV1/737</STL:HostComm

and>


</STL:Success>

</TT:RawTPFC>


</TT:Ticket>

</TT:Transaction>


3.19.2.4 Combined E-Ticket and LCC PQ selection

When a request is received for a combination of E-ticket and LCC, the web service will group all LCC

PQs belonging to a single validating carrier and send a separate ticketing command for each PQ group to

PSS. The E-ticket PQs will not be sent in a single command. Each LCC and E-ticket PQ will be fulfilled

each at a time. .

If a LCC PQ within a group fails issuance then all PQs within the group fails.

If an E-ticket PQ fails, then the service will proceed to fulfill next E-ticket PQ in the sequence.


If a PQ has expired or any other prompt requiring additional input is encountered then this will be deemed

a failure. The orchestration service is unable to interrupt processing for responses which require user

intervention.

NOTE: When mixed content fulfillment is requested then issuance may return unexpected results. This is

a constraint which the client needs to be aware of to ensure it orchestrates PNR/PQ creation or circumvents

with a recommended practice of using the “all E-ticket” parameter.

Below is an example for fulfillment with mixed content Price Quote records constituting Low Cost and E-

ticket Price Quote Records.

Request:





<Ticket>

<PricingOptions>

<PQFilter all="true"/>

</PricingOptions>

</Ticket>

<Payment>


securityCode="737"/>

</Payment>

</Transaction>


Response






<STL:STL_Header.RS messageID="TKTVLC750-27598-1714867482-1491936414279-

610685-issuedoc" version="3.15.0">


xmlns="http://services.sabre.com/STL/v01">TKTVLC750-27598-1714867482-


<STL:Results>

<STL:Success>



</STL:Success>




</STL:Warning>

</STL:Results>



<TT:Ticket>








<STL:HostCommand LNIATA="6AA41F">W¥PQ1-

3¥F*VI****************/0818¥CVV1/737</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>


</TT:Ticket>

<TT:Ticket>







<STL:HostCommand LNIATA="6AA41F">W¥PQ7-

9¥F*VI****************/0818¥CVV1/737</STL:HostCommand>


</STL:Success>

</TT:RawTPFC>


</TT:Ticket>

<TT:Ticket>





<STL:HostCommand

LNIATA="6AA41F">W¥PQ4¥F*VI****************/0818¥CVV1/737</STL:HostCommand>


</STL:Success>

<STL:Warning type="BusinessLogic">


<STL:Message>* CREDIT VERIFICATION IN PROGRESS</STL:Message>

<STL:ShortText>WARN.SWS.HOST.INTERMEDIATE_RESPONSE

ERR.SWS.HOST.PREVIOUS_ENTRY_ACTIVE

WARN.SWS.HOST.INTERMEDIATE_RESPONSE</STL:ShortText>


</STL:Warning>

</TT:RawTPFC>

<TT:Messages>OK 568.70 X94051</TT:Messages>

<TT:Messages>ETR MESSAGE PROCESSED</TT:Messages>

</TT:Ticket>

<TT:Ticket>


<TT:RawTPFC status="NotProcessed">

<STL:Error timeStamp="2017-04-11T13:47:11-05:00" type="BusinessLogic">


<STL:HostCommand


<STL:Message>? PREVIOUS ENTRY ACTIVE-PLEASE WAIT FOR RESPONSE

?</STL:Message>






</STL:Error>

</TT:RawTPFC>

</TT:Ticket>

<TT:Ticket>





<STL:HostCommand



</STL:Success>

<STL:Warning type="BusinessLogic">


<STL:Message>* CREDIT VERIFICATION IN PROGRESS</STL:Message>





</STL:Warning>

</TT:RawTPFC>

<TT:Messages>OK 77.70 X14182</TT:Messages>

<TT:Messages>ETR MESSAGE PROCESSED</TT:Messages>

</TT:Ticket>

</TT:Transaction>


Expansion of length of Remarks element

Maximum length of remarks field has increased from 120 to 999 characters. This applies to ticket issuance via a direct ticketing command (W#) and referencing a PQ (W#PQ) with or without TFSF active.

This enhancement changes the length of Remarks element in below element fields:

1. TicketingDocument.Remark, 2. TicketingDocument.Remark.EMD, 3. TicketingDocument.Remark.Pir, 4. TicketingDocument.Remark.Refund, 5. UpdateRemarks.Remarks


Request:





<SearchParameters>



<DocumentNumber workLocation="61N1">8888888888888</DocumentNumber>

</SearchParameters>


Response:

<TicketingDocument type="TKT" number="8888888888888" accountingCode="888" formNumber="88"

serialNumber="88888888"

checkDigit="0">

<Indicators electronic="true" selfSale="false"/>

<Details>

<Reservation>

<Sabre provider="U0" purgeDate="2016-01-28T00:00:00"

createDate="2016-01-15T00:00:00">IPQBQB</Sabre>

</Reservation>

<SystemCreateDateTime>2016-01-15T04:01:00</SystemCreateDateTime>



<ValidatingProvider number="888" checkDigit="8" name="SABRE

AIRWAYS ">U0</ValidatingProvider>

<InvoiceNumber>0001173</InvoiceNumber>

<OriginCity>BOM</OriginCity>

<DestinationCity>BOM</DestinationCity>

<ItineraryType>I</ItineraryType>

<CurrentActivity/>

<ExchCategory>I</ExchCategory>



<CouponText>FFVV</CouponText>

<CurrencyOverride>GBP</CurrencyOverride>

<PointOfSaleOverride>LON</PointOfSaleOverride>

<PointOfTicketOverride>LON</PointOfTicketOverride>

<BaggageDisclosure disclosureIndicator="6"/>

</Details>

<Customer>

<Traveler nameId="2" nameNumber="2.1">

<Name>TEST/CHILD CHD</Name>

<FirstName>CHILD</FirstName>

<LastName>TEST</LastName>

<ExternalNumber>C09</ExternalNumber>

<Age>255</Age>

<PassengerType>CNN</PassengerType>

</Traveler>

</Customer>

<ServiceCoupon coupon="1" entitlement="1" segmentId="4">

<MarketingProvider>LH</MarketingProvider>


<OperatingProvider name="LUFTHANSA">LH</OperatingProvider>



<FareBasis>FIXENDO5</FareBasis>

<StartLocation>BOM</StartLocation>


<EndLocation>FRA</EndLocation>






<Reservation>25EDL6</Reservation>




<Indicators fareBreak="true" turnaround="false" noBreak="false"


connectionOverride="false"

sideTripStart="false"

sideTripEnd="false"/>

<FareBreakAmount>

<Amount decimalPlace="2" currencyCode="NUC">1587.80</Amount>


</FareBreakAmount>


<Equipment>744</Equipment>



<OA_OperatingFlightNumber>757</OA_OperatingFlightNumber>

<FareComponent roundTripIndicator="true" oneWayIndicator="false"

oneWayDirectionalIndicator="false"

appendNonRefundableIndicator="false"

InboundIndicator="false"


sequence="1">

<AssociatedFareBasis>FIXENDO5</AssociatedFareBasis>

<FareProvider>LH</FareProvider>

<Tariff>909</Tariff>

<FareRule>004P</FareRule>

<PricingVendor>15X0</PricingVendor>

</FareComponent>

</ServiceCoupon>

<ServiceCoupon coupon="2" entitlement="2" segmentId="2">

<MarketingProvider>LH</MarketingProvider>


<OperatingProvider name="LUFTHANSA">LH</OperatingProvider>



<FareBasis>FIXENDO5</FareBasis>

<StartLocation>FRA</StartLocation>


<EndLocation>BOM</EndLocation>





<Reservation>25EDL6</Reservation>



<StopOver>O</StopOver>


<Indicators fareBreak="true" turnaround="false" noBreak="false"


connectionOverride="false"

sideTripStart="false"


sideTripEnd="false"/>

<FareBreakAmount>

<Amount decimalPlace="2" currencyCode="NUC">1587.80</Amount>


</FareBreakAmount>


<Equipment>744</Equipment>



<OA_OperatingFlightNumber>756</OA_OperatingFlightNumber>

<FareComponent roundTripIndicator="true" oneWayIndicator="false"

oneWayDirectionalIndicator="false"

appendNonRefundableIndicator="true"

InboundIndicator="false"


sequence="2">

<AssociatedFareBasis>FIXENDO5</AssociatedFareBasis>

<FareProvider>LH</FareProvider>

<Tariff>909</Tariff>

<FareRule>004P</FareRule>

<PricingVendor>15X0</PricingVendor>

</FareComponent>

</ServiceCoupon>

<Amounts>

<New>

<Base>

<Amount currencyCode="INR" decimalPlace="0">212100</Amount>

<Text>212100</Text>

</Base>

<Equivalent>

<Amount currencyCode="GBP" decimalPlace="2">2202.00</Amount>


<CurrencyConversion>

<BankerSellingRate

decimalPlace="5">0.01038</BankerSellingRate>

</CurrencyConversion>

</Equivalent>

<TotalTax>


<Text>475.00</Text>

</TotalTax>

<Total>



<RateOfExchange decimalPlace="7">66.7903000</RateOfExchange>

</Total>

<Tax sequence="1" code="YQ" status="N">


<Text>240.20</Text>

</Tax>

<Tax sequence="2" code="XT" status="N">


<Text>234.80</Text>

</Tax>

</New>

<Other>

<Commission>


<Amount decimalPlace="2" currencyCode="GBP">0.00</Amount>

<Text>0.00</Text>

</Commission>

<NUC>

<Amount currencyCode="NUC" decimalPlace="2">3175.60</Amount>


</NUC>

</Other>

</Amounts>

<Taxes>

<New>

<Tax sequence="1" code="YQ" status="N" exempt="false">


<Text>240.20</Text>

</Tax>

<Tax sequence="2" code="YR" status="N" exempt="false">


<Text>12.00</Text>

</Tax>

<Tax sequence="3" code="WO" status="N" exempt="false">


<Text>2.50</Text>

</Tax>

<Tax sequence="4" code="JN" status="N" exempt="false">


<Text>137.40</Text>

</Tax>

<Tax sequence="5" code="F2" status="N" exempt="false">


<Text>4.90</Text>

</Tax>

<Tax sequence="6" code="IN" status="N" exempt="false">


<Text>8.00</Text>

</Tax>

<Tax sequence="7" code="YM" status="N" exempt="false">


<Text>7.00</Text>

</Tax>

<Tax sequence="8" code="DE" status="N" exempt="false">


<Text>6.20</Text>

</Tax>

<Tax sequence="9" code="RA" status="N" exempt="false">


<Text>25.10</Text>

</Tax>

<Tax sequence="10" code="OY" status="N" exempt="false">


<Text>31.70</Text>

</Tax>

</New>

</Taxes>

<Remark>

<Endorsements sequence="1" type="EEO">THIS IS A TEST CASE TO CHECK

ENDORSEMENT CHARACTERS. THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS

THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO


CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO CHECK ENDORSEMENT

CHARACTERS THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A

TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO CHECK

ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS

THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO

CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO CHECK ENDORSEMENT

CHARACTERS THIS IS A TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A

TEST CASE TO CHECK ENDORSEMENT CHARACTERS THIS IS A TEST CASE TO CHECK

ENDORSEMENT CHARACTERS /</Endorsements>

<Payment sequence="1">*VI4444I00G41161111</Payment>

</Remark>

<AffiliatedAgent>

<Booking duty="9" sine="GPS" ordinal="55159">

<WorkLocation>61N1</WorkLocation>

<IataNumber>99999992</IataNumber>

<HomeLocation>7HB7</HomeLocation>

<PseudoCityCode>61N1</PseudoCityCode>

</Booking>

</AffiliatedAgent>

<FareCalculation type="132">

<New>BOM LH FRA1587.80LH BOM1587.80NUC3175.60END ROE66.7903</New>

</FareCalculation>

<Payment sequence="1" type="CC">

<Total>

<Amount currencyCode="GBP" decimalPlace="2">0</Amount>

</Total>

<Remarks>VI4444I00G41161111</Remarks>

<Card cardType="VI">

<MaskedCardNumber>4444I00G41161111</MaskedCardNumber>

<ExpireDate>1019</ExpireDate>

<ApprovalCode>900541</ApprovalCode>

<ExtendedPayment/>

<ApprovalSource>C</ApprovalSource>

</Card>

</Payment>

<History code="OC" number="9" sequence="1">

<Agent duty="9" sine="GPS">


<HomeLocation>HDQ</HomeLocation>

<WorkLocation>61N1</WorkLocation>

</Agent>

<TransactionInfo>


<SystemProvider>1S</SystemProvider>

<InputMessage>W$F*VIXXXXXXXXXXXX1111/XXXX$ALH$KP0$ETR$QFIXENDO5$IPA-

DY:IS$PADT/CNN/INF+</InputMessage>

</TransactionInfo>

<ServiceCouponHistory coupon="1" sequence="1">


</ServiceCouponHistory>

<ServiceCouponHistory coupon="2" sequence="2">


</ServiceCouponHistory>

</History>

<PrintCoupon stockType="AT"/>



</Ticketing>

</TicketingDocument.Objects>

Mark up any fare – Agency Retailer Project

Travel Agencies need a way to integrate a fee for their work in the pricing, shopping and ticketing workflow. With this project, travel agencies can mark-up original fare / Net level fare with an adjusted fee amount, which can be viewed based on the specific keywords in the requestors EPR.

This mark-up data is transportable across channels with original fare level data only for the Airline to view and traveler documentation to reflect the adjusted selling level. This is applicable only for subscribers.

Data elements which are added as part of GetTicketingDocumentRS_v3.13.0 are as below:

Item

Ticketing

Document Data

Description

Ticketing Document Notification XML Element/

Attribute

Element (E) or

Attribute (A)

Optional (O) or

Required (R)

1 Amount

GetTicketingDocumentRS/Details/Ticket/Amo

unts/AdjustedSellingFare E O


unts/Net E O


unts/CommissionDetails E O

2 Taxes

GetTicketingDocumentRS/Details/Ticket/Taxe

s/AdjustedSellingFare E O

GetTicketingDocumentRS/Details/Ticket/Taxe

s/NetFare E O

3 Service Coupon

GetTicketingDocumentRS/Details/Ticket/Servi

ceCoupon/Commission E O


ceCoupon/NetFare E O


ceCoupon/AdjustedSellingFare E O

Example of Adjusted Selling Fare level

Request:


Version="3.13.0">




<TicketingProvider>1B</TicketingProvider>




</SearchParameters>


Response:










<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>



<TT:Agent duty="*" sine="SKV">

<ns2:IataNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">5KAD</ns2:WorkLocation>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SG</ns2:IsoCountryCode>

<ns2:CompanyName xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FARES

SOLUTIONS</ns2:CompanyName>

</TT:Agent>

<TT:Ticket accountingCode="888" number="8888888888888" type="TKT">

<TT:Details>

<ns2:TourNumber

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DOOM</ns2:TourNumber>

<TT:Reservation>

<ns2:Sabre xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

createDate="2016-09-20T00:00:00" provider="AA" purgeDate="2016-10-

20T00:00:00">RIQCZX</ns2:Sabre>

</TT:Reservation>




<TT:ValidatingProvider name="SABRE AIRWAYS”">U0</TT:ValidatingProvider>

<ns2:MandateInfo xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Mandate country="SG">NOTE - SGD6.10 OP (AVIATION LEVY) APPLIES TO

DEPARTURES FROM SINGAPORE</ns2:Mandate>

<ns2:Disclaimer country="US" language="EN">NOTICE

.</ns2:Disclaimer>

<ns2:HazardousMaterials country="US"

language="EN"></ns2:HazardousMaterials>


</ns2:MandateInfo>

</TT:Details>

<TT:Customer>

<TT:Traveler>

<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TEST/AA</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AA</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TEST</ns2:LastName>


</TT:Traveler>

</TT:Customer>


<TT:MarketingProvider name="SABRE AIRWAYS">U0</TT:MarketingProvider>



r>

<TT:OperatingProvider name="SABRE AIRWAYS">U0</TT:OperatingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">211</ns2:OperatingFlightNumbe

r>

<ns2:ClassOfService xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

name="ECONOMY">Y</ns2:ClassOfService>

<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CAT35NTL</ns2:FareBasis>

<ns2:StartLocation xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

name="SINGAPORE">SIN</ns2:StartLocation>



<ns2:EndLocation xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

name="SYDNEY">SYD</ns2:EndLocation>






<ns2:BookingStatus xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

name="CONFIRMED">OK</ns2:BookingStatus>

<ns2:BagAllowance


</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>

<TT:Base>


currencyCode="SGD" decimalPlace="2">475.00</ns2:Amount>

<ns2:Text


</TT:Base>

<TT:TotalTax>



<ns2:Text


</TT:TotalTax>

<TT:Total>




<ns2:Text


</TT:Total>

</TT:New>

<ns2:AdjustedSellingFare xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

manual="true">

<ns2:Base>

<ns2:Amount currencyCode="SGD" decimalPlace="2">550.00</ns2:Amount>


</ns2:Base>

<ns2:Total>



</ns2:Total>

<ns2:Tax code="SG" sequence="1">



</ns2:Tax>

<ns2:Tax code="OO" sequence="2">



</ns2:Tax>

<ns2:Tax code="XT" sequence="3">



</ns2:Tax>

<ns2:AdjustedSelling>



<ns2:ValueCode>ADJT AMT</ns2:ValueCode>

</ns2:AdjustedSelling>

</ns2:AdjustedSellingFare>

<ns2:CommissionDetails xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Category35>

<ns2:Commission provider="1B">

<ns2:Amount decimalPlace="2">50.00</ns2:Amount>


</ns2:Commission>

</ns2:Category35>

</ns2:CommissionDetails>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax code="SG" exempt="false" name="PASSENGER SERVICE AND SECURITY

CHARGE" sequence="1" status="N">



<ns2:Text


</TT:Tax>

<TT:Tax code="OO" exempt="false" name="PASSENGER SECURITY SERVICE CHARGE

PSSC" sequence="2" status="N">




<ns2:Text


</TT:Tax>

<TT:Tax code="OP" exempt="false" name="AVIATION LEVY" sequence="3"

status="N">



<ns2:Text


</TT:Tax>

<TT:Tax code="WY" exempt="false" name="PASSENGER SERVICES CHARGE

DEPARTURE INTERNATIONAL" sequence="4" status="N">



<ns2:Text


</TT:Tax>

<TT:Tax code="YQ" exempt="false" sequence="5" status="N">



<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:FareCalculation>

<ns2:New xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">SIN SQ

SYD350.87NUC350.87END ROE1.35376SIN SQ SYD406.27NUC406.27END

ROE1.35376</ns2:New>

</TT:FareCalculation>


<ns2:Booking xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" duty="*"

sine="-AV">

<ns2:WorkLocation>5KAD</ns2:WorkLocation>


<ns2:HomeLocation>5KAD</ns2:HomeLocation>

</ns2:Booking>



<ns2:Total xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



</ns2:Total>

<ns2:Remarks

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CA</ns2:Remarks>

<ns2:Cash xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"


</TT:Payment>

</TT:Ticket>




GDS Automated Refunds CAT33

CAT33 defines carrier refund rules and policies to automatically calculate refund amounts within the

Automated Exchanges and Refunds web service.

Data elements which got added to GetTicketingDocumentRS_v3.13.0 are as as below:

Item

Ticketing

Document Data

Description

Ticketing Document Notification XML

Element/ Attribute

Element (E)

or Attribute

(A)

Optional (O)

or Required

(R)

1 Age (UMNR)

GetTicketingDocumentRS/Details/Ticket/Cu

stomer/Traveler/Age E O

2 TicketDestination

GetTicketingDocumentRS/Details/Ticket/D

etails/TicketDestination E O

3 TicketTravel

GetTicketingDocumentRS/Details/Ticket/D

etails/TicketTravel E O

4 Miscellaneous

GetTicketingDocumentRS/CustomDetails/Ti

cket/RelatedDocument/Miscellaneous E O

5 plainPaper

GetTicketingDocumentRS/CustomDetails/Ti

cket/Indicators/@plainPaper E O

Example of “Age” of an unaccompanied minor

Request:


Version="3.13.0">







</SearchParameters>


Response:











<DiagnosticData


<STL:Results>


<System>T2</System>


</Success>

</STL:Results>


<TT:Details>

<TT:Agent duty="4" sine="-AV" type="ATO">

<ns2:TicketingProvider xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

checkDigit="1" name="SABRE AIRWAYS" number="888">U0</ns2:TicketingProvider>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YYZTR</ns2:StationLocation>

<ns2:StationNumber


<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YYZ</ns2:WorkLocation>

<ns2:HomeLocation


<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">668F0A</ns2:Lniata>

<ns2:IsoCountryCode

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">CA</ns2:IsoCountryCode>



<ns2:EmployeeNumber







</ns2:Session>

</TT:Agent>


type="SALE">

<ns2:TCN






<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AA</ns2:SystemProvider>

<ns2:InputEntry










selfSale="false"/>

<TT:Details>

<TT:Reservation>


provider="AA">VUOSOE</TT:Sabre>

</TT:Reservation>








<ns2:ValidatingProvider xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

checkDigit="1" name="SABRE AIRWAYS" number="001">AA</ns2:ValidatingProvider>

<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YYZ</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DFW</ns2:DestinationCity>

<ns2:ItineraryType


<ns2:ExchCategory




<ns2:TicketingMode




<ns2:CouponText


<TT:BaggageDisclosure disclosureIndicator="5">BAG ALLOWANCE -YYZDFW-

NIL/AA</TT:BaggageDisclosure>

</TT:Details>

<TT:Customer>


<ns2:Name

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TEST/ONE</ns2:Name>

<ns2:FirstName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ONE</ns2:FirstName>

<ns2:LastName

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">TEST</ns2:LastName>


<Age>08</Age>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">ADT</ns2:PricedPassengerType>

</TT:Traveler>

</TT:Customer>



checkDigit="1" name="SABRE AIRWAYS" number="888">U0</ns2:MarketingProvider>



er>

<ns2:ClassOfService



<ns2:FareBasis


<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YYZ</ns2:StartLocation>



<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DFW</ns2:EndLocation>






<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse





<ns2:StartTimeText






<ns2:PlusUp xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="Q"

sequence="1">


</ns2:PlusUp>






xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YA2AA</ns2:AssociatedFareBasi

s>

<TT:FareProvider>AA</TT:FareProvider>

<ns2:Tariff


<ns2:FareRule


<ns2:PricingVendor


</TT:FareComponent>

</TT:ServiceCoupon>

<TT:Amounts>

<TT:New>




</ns2:Base>

<TT:Total>



currencyCode="CAD" decimalPlace="2">1966.03</ns2:Amount>

<ns2:Text


</TT:Total>

<ns2:Tax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="CA"




</ns2:Tax>

<ns2:Tax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="XG"




</ns2:Tax>

<ns2:Tax xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" code="XT"




</ns2:Tax>

</TT:New>

<TT:Other>

<ns2:NUC xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">



</ns2:NUC>

</TT:Other>

</TT:Amounts>

<TT:Taxes>

<TT:New>

<TT:Tax code="CA1" exempt="false" sequence="1">



<ns2:Text


</TT:Tax>

<TT:Tax code="XG5" exempt="false" sequence="2">



<ns2:Text


</TT:Tax>

<TT:Tax code="RC1" exempt="false" sequence="3">



<ns2:Text


</TT:Tax>

<TT:Tax code="SQ1" exempt="false" sequence="4">



<ns2:Text


</TT:Tax>

<TT:Tax code="US2" exempt="false" sequence="5">




<ns2:Text


</TT:Tax>

<TT:Tax code="YC" exempt="false" sequence="6">



<ns2:Text


</TT:Tax>

<TT:Tax code="XY" exempt="false" sequence="7">



<ns2:Text


</TT:Tax>

<TT:Tax code="XA" exempt="false" sequence="8">



<ns2:Text


</TT:Tax>

</TT:New>

</TT:Taxes>

<TT:Remark>

<ns2:Payment xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

sequence="1">CASH</ns2:Payment>

</TT:Remark>


<ns2:New>YTO AA DFW Q5.81 1381.30YA2AA NUC1387.11END ROE1.29081

XT3.25RC25.00SQ23.41US7.23YC9.20XY5.21XA</ns2:New>



<ns2:Lniata

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">2542AD</ns2:Lniata>

</TT:PrintCoupon>


<TT:Base>

<TT:Amount currencyCode="CAD" decimalPlace="2">1790.50</TT:Amount>

<ns2:ApplyCreditInd


</TT:Base>

<TT:Tax>


<ns2:ApplyCreditInd


</TT:Tax>

<TT:Total>


<ns2:ApplyCreditInd


</TT:Total>

<ns2:Remarks



</TT:Payment>





xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AA</ns2:TicketingProvider>

<ns2:WorkLocation


<ns2:HomeLocation


</TT:Agent>

<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VUOSOE</ns2:OldReservation>

</TT:Details>

</TT:History>


<TT:Agent duty="4" sine="-AV">


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AA</ns2:TicketingProvider>

<ns2:WorkLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YYZ</ns2:WorkLocation>

<ns2:HomeLocation


</TT:Agent>


<ns2:LocalDateTime



<ns2:SystemDateTime



<ns2:SystemProvider

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">AA</ns2:SystemProvider>

<ns2:InputMessage



<TT:Details>



Document>

<ns2:OldReservation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">VUOSOE</ns2:OldReservation>



</TT:Details>





</TT:History>

</TT:Ticket>

</TT:Details>



FCMI and FCPI Values

‘GetTicketingDcoumentRQ’ web service is enhanced to support FCPI and FCMI indicators for VCR and

EMD document stored in T2 database. This feature is available as part of ‘GetTicketingDcoumentRQ’ web

service schema version v3.16.1 onwards.

FCMI and FCPI indicators are returned in GetTicketingDocument service for result type ‘D’ for detail and

‘C’ for custom detail specified by the service user in the request. The logic to derive to the values of these

indicators are based on the business rules which resides in the host system. The service access the document

data including the FCMI and FCPI indicator values from the T2 database.

This enhancement adds the capability to the consumer of the service to identify manual pricing transactions

using FCMI indicator and to indicate the method of pricing using FCPI indicator.

FCMI Indicator

FCMI stands for Fare Calculation Mode indicator. It is used to identify how the ticketed itinerary was

priced. It also helps the airlines to differentiate the auto priced itineraries with manually pricing transaction

using FCMI indicators. The objective is to get the correct FCMI code (IATA Standard) for manual and

auto pricing transactions

With service version 3.16.0 and below, ‘GetTicketingDcoumentRQ’ web service returns FCPI data with

element name ‘FareCalculationMode’. With service version 3.16.1 and above, the logic on the open system

is changed to return the correct FCMI data on the existing element ‘FareCalcuationMode’. The possible

values will be 0, 1 or 2.

Below are the identifier reflecting the method of pricing for this transaction as entered on the ticket/EMD.

0 - Indicates that a fare has been system computer

1 - Identifies a manually built fare

2 - Identifies a fare that was auto-priced, but baggage and/or TFC data has been manipulated.

The x-paths to return the FCMI indicator for a VCR document in result type ‘Detail’ and ‘Custom

Details’ are:

- GetTicketingDocumentRS/Details/Ticket/Details/FareCalculationMode

- GetTicketingDocumentRS/Details/Ticket/CustomDetails/FareCalculationMode

The x-paths to return the FCMI indicator for a EMD document in result type ‘Detail’ and ‘Custom

Details’ are:

- GetTicketingDocumentRS/Details/ElectronicMiscDocument/Details/FareCalculationMode

- GetTicketingDocumentRS/CustomDetails/ElectronicMiscDocument/Details/FareCalculationMode

Note: If the FCMI indicator column does not have data (value) in T2 database for any reasons, service will

return the FCPI values in the FCMI field as part of the service response.


FCPI Indicator

FCPI stands for Fare Calculation Pricing Indicator. It is a single numeric character code which provides the

pricing method to issue the ticket. It provides form of payment and system prices vs agent priced information.

When a ticket is driven, the system determines which pricing code/fare calculation pricing indicator (FCPI)

to put on the ticket based on payment and how it was priced. The industry has defined the fare calculation

pricing indicator (FCPI) as follows:

FARE CALCULATION PRICE INDICATOR 1 ALPHANUMERIC

The identifier reflecting the method of pricing for the transaction as entered on the ticket/document.

0 - System computer priced (without any manual modifications except for baggage allowance)

1 - Manually priced

2 -9 - For individual airline/system provider use

A-Z - Undefined industry use

A new data element ‘Fare Calculation Pricing’ is added in the ‘GetTicketingDcoumentRQ’ web service,

under which the value of FCPI indicator value will be returned to the requestor.

The x-paths to return the FCPI indicator for a VCR document in result type ‘Detail’ and ‘Custom

Details’ are:

- GetTicketingDocumentRS/Details/Ticket/Details/FareCalculationPricing

- GetTicketingDocumentRS/CustomDetails/Ticket/Details/FareCalculationPricing

The x-paths to return the FCPI indicator for a EMD document in result type ‘Detail’ and ‘Custom

Details’ are:

- GetTicketingDocumentRS/Details/ElectronicMiscDocument/Details/FareCalculationPricing - GetTicketingDocumentRS/CustomDetails/ElectronicMiscDocument/Details/FareCalculationPricing

Note: If the FCPI indicator column does not have data (value) in T2 database for any reasons (which is

highly unlikely), service will not return the ‘FareCalculationPricing’ data element indicator as part of the

response.

Example1 of FCMI and FCPI indicator in ‘GetTicketingDcoumentRQ’ service

Below is an example to illustrate how FCMI and FCPI data will be returned as part of the service response.

Scenario: A ticket is generated by a travel agent on Abacus GDS [PCC 5KAD] for system priced itinerary.

A requestor [an airline agent] retrieves the VCR document through GetTicketingDcoumentRQ web service

with the result type ‘D’ [‘D’ refer to Detail] by specifying the VCR document number in the service request.

GetTicketingDcoumentRQ web service returns the FCMI value as ‘0’ and FCPI value as ‘4’ as it was stored

in T2 database.

Extended VCR document display on host system


VCR*5895868308158‡E«


TKT-5895868308158 ISSUED-28AUG17 CTY-SIN STA-99999992

AGNT-SINHUL PNR- EAEMRJ/28AUG17 CTRY-SG

CRS -1B 5KAD

NAME-PONE/TESSSS

TTL NBR OF CPNS- 1

CPN A/L FLT CLS DATE BRDOFF TIME PNR BAG STATUS

1 9W 351 Y 29SEP17 BOMDEL 100P OK 15K OK

F/B-Y2OW

FARE CALC BOM 9W DEL Q1000 Q300 24900INR26200END

FCMI-0 TICKETED PSGR TYPE-ADT PRICED PSGR TYPE-ADT FCPI-4

BASE FARE INR 26200

EQUIV PAID SGD 558.00

TFC TOTAL SGD 78.90 XT TTL SGD 44.90

TICKET TOTAL SGD 636.90

FEE TOTAL SGD 0.00

GRAND TOTAL SGD 636.90

TAXES/FEES/CARRIER-IMPOSED CHARGES-TFC

5.00 WO 29.00 K3

20.60 IN 2.40 YM ‡

MD«

19.20 YQ 2.70 YR ‡

COMMISSION AMT- 111.60 COMMISSION PCT- 2.00

GetTicketingDcoumentRQ web service - Request and Response

REQUEST




<STL:POS/>


<TicketingProvider>9W</TicketingProvider>


</SearchParameters>


RESPONSE

<TT:Details> <TT:Reservation>

<TT:Sabre createDate="2017-08-28T00:00:00" provider="9W">EAEMRJ</TT:Sabre>

<ns2:OtherSystem

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">MIOPNN</ns2:OtherSystem>

</TT:Reservation>










<ns2:ValidatingProvider xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC"

checkDigit="1" name="JET AIRWAYS "

number="589">9W</ns2:ValidatingProvider>

<ns2:OriginCity

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BOM</ns2:OriginCity>


xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">DEL</ns2:DestinationCity>

<ns2:ItineraryType




<ns2:TicketingMode




<ns2:CouponText


<ns2:FareCalculationPricing

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">4</ns2:FareCalculationPricing

>

</TT:Details>

Refer to the attached file below for full request and response:

Full Request and

Response.pdf

Example2 of FCMI and FCPI indicator in ‘GetTicketingDcoumentRQ’ service

Below is an example to illustrate how FCMI and FCPI data will be returned as part of the service response

when FCMI column in the T2 database has no value.

Scenario: A ticket is generated by an IET airline partner [AA in this case] for system priced itinerary. Due

to some reason, FCMI value didn’t get populated in T2 database for this particular ticket. A requestor which

is Sabre hosted airline agent [EY] retrieves the VCR document through GetTicketingDcoumentRQ web

service with the result type ‘D’ [‘D’ refer to Detail] by specifying the VCR document number in the service

request.

GetTicketingDcoumentRQ web service returns the FCPI value in FCMI field and FCPI field, as part of the

service response.

Extended VCR document display on host system


*TR2‡E«


TKT-0012141053323 ISSUED-23SEP17 CTY-HDQ STA-77777770

AGNT-HDQXAV PNR- KNZFMB/23SEP17 CTRY-US

OAC- AA HDQ 7777770 CRS -AA HDQ00

NAME-SAMPLE/TEST

TTL NBR OF CPNS- 3

CPN A/L FLT CLS DATE BRDOFF TIME PNR BAG STATUS

1 AA 80 Y 01DEC17 DFWLHR 505P OK 1PC OK

F/B-Y1E1FO

2 ARNK VOID

F/B-VOID

3O EY 371 Y 05DEC17 AUHBAH 850A OK 1PC OK

F/B-Y1E1FO

FARE CALC DFW AA LON//AUH EY BAH M DFWAUH3909.00Y1E1FO P DFWA

UH DFWBAH176.00 NUC4085.00END ROE1.00 XFDFW4.5

FCMI-0 TICKETED PSGR TYPE-ADT PRICED PSGR TYPE-ADT FCPI-0

Request




<STL:POS/>

<SearchParameters>

<TicketingProvider>AA</TicketingProvider>


</SearchParameters>


Response

<TT:Details> <TT:Reservation>

<TT:Sabre createDate="2017-09-23T00:00:00">KNZFMB</TT:Sabre>

<ns2:OtherSystem

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">GLJPJB</ns2:OtherSystem>

</TT:Reservation>










xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" checkDigit="1" name="AMERICAN

AIRLINES INC." number="001">AA</ns2:ValidatingProvider>

<ns2:OriginCity



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BAH</ns2:DestinationCity>


<ns2:ItineraryType




<ns2:TicketingMode




<ns2:CouponText

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">FVFV</ns2:CouponText>

<ns2:MandateInfo xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">

<ns2:Disclaimer country="US" language="EN">NOTICE











WITH YOUR CARRIER FOR MORE INFORMATION.</ns2:Disclaimer>

<ns2:HazardousMaterials country="US" language="EN">THE CARRIAGE OF

CERTAIN HAZARDOUS MATERIALS, LIKE AEROSOLS, FIREWORKS, AND FLAMMABLE LIQUIDS,

ABOARD THE AIRCRAFT IS FORBIDDEN. IF YOU DO NOT UNDERSTAND THESE RESTRICTIONS,

FURTHER INFORMATION MAY BE OBTAINED FROM YOUR

AIRLINE.</ns2:HazardousMaterials>

</ns2:MandateInfo>

<ns2:FareCalculationPricing

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">0</ns2:FareCalculationPricing

>

</TT:Details>

Refer to the attached file below for full request and response:

Example_2 Full

Request and Response.pdf

Involuntary Reroute Information

GetTicketingDcoumentRQ web service is enhanced to support Involuntary Reroute infoemartion for VCR

stored in T2 database. This feature is available as part of ‘GetTicketingDcoumentRQ’ web service schema

version v3.22.0 onwards.

Involuntary Reroute indicators are returned in GetTicketingDocument service for result type ‘D’ for detail

and ‘C’ for custom detail specified by the service user in the request. The logic to derive to the values of

these indicators are based on the business rules which resides in the host system.


This enhancement provides the capability to the consumer to identify the Reason and description of reroute

performed on a coupon of a VCR under IROPS situation. INVOL Reroute (WFRI) and No coupon INVOL

Exchange (WFRNC) type will be supported from V3.22.0 onwards.

X-paths of data elements, added in GetTicketingDcoumentRS, under ServiceCoupon_InvoluntaryReroute

for result type ‘D’ and ‘C’ are below mentioned in the table:

Item

Ticketing

Document Data

Description

Ticketing Document Notification XML Element/

Attribute

Element (E) or

Attribute (A)

Optional (O)

or Required

(R)

1 Reason

GetTicketingDocumentRS/Details/Ticket/ServiceC

oupon/InvoluntaryReroute/Reason E O

2

RerouteDescrip

tion


oupon/InvoluntaryReroute/RerouteDescription E O

3 Date


oupon/InvoluntaryReroute/Date E O

4 Provider


oupon/InvoluntaryReroute/Provider E O

5 Reason

GetTicketingDocumentRS/CustomDetails/Ticket/

ServiceCoupon/InvoluntaryReroute/Reason E O

6

RerouteDescrip

tion


ServiceCoupon/InvoluntaryReroute/

RerouteDescription E O

7 Date


ServiceCoupon/InvoluntaryReroute/Date E O

8 Provider


ServiceCoupon/InvoluntaryReroute/Provider E O

Example – INVOL indicator in GetTicketingDocument service

Below is an example to illustrate INVOL indicator is returned in GetTicketingDocument service when

Involantry Exchange (WFRI) is being performed by Operating carrier, in case of IET scenarios where

Operating carrier is different from Validating Carrier (VC).

Scenario: A ticket is issued by U0 carrier (VC) and operating carriers are airline K0 and U0. Due to bad

weather airline K0 (OC) has to involuntary reroute the passenger onto another flight. Once ticket is

exchanged by OC, a message will sent to VC invluding INVOL indicator.

U0 retrieves the VCR document through GetTicketingDcoumentRQ web service with the result type ‘D’

[‘D’ refer to Detail] by specifying the VCR document number in the service request.


Request:


Version="3.22.0"


<ns1:STL_Header.RQ


<ns2:POS





</SearchParameters>






Response:


<ns2:MarketingProvider checkDigit="5" name="U0" number="888"




r>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YLOWAE/YF</ns2:FareBasis>

<ns2:StartLocation


<ns2:StartDateTime



<ns2:EndLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">BLR</ns2:EndLocation>

<ns2:EndDateTime




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YF</ns2:TicketDesignator>







<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">F</ns2:CouponUse> <ns2:Indicators fareBreak="true" sideTripEnd="false"



<ns2:InvoluntaryReroute


<ns2:Reason>I</ns2:Reason>

<ns2:RerouteDescription>INVOL</ns2:RerouteDescription>

</ns2:InvoluntaryReroute>

Example – Diversion indicator in GetTicketingDocument service

Below is an example to illustrate DIVERSION indicator is returned in GetTicketingDocument service

when No Copuon Involuntary Exchange (WFRNC) is being performed by carrier.



















Scenario: U0 carrier operates from LHR to AUH with a stop in IST (No change of equipment). An aircraft

goes out of service at IST. All of the VCRs’ for the passengers travelling frm LHR to AUH need to be

reeboked for a flight IST to AUH. As coupon status of VCRs’ show as USED, by using No Coupon

(WFRNC), carrier performs an involuntary exchange.

U0 retrieves the new VCR that is created out of No Coupon Invountary exchange through

GetTicketingDcoumentRQ web service with the result type ‘D’ [‘D’ refer to Detail] by specifying the VCR

document number in the service request.

Request:


Version="3.22.0"


<ns1:STL_Header.RQ


<ns2:POS


<SearchParameters resultType="D"> <TicketingProvider>U0</TicketingProvider>


</SearchParameters>






Response:

<TT:ServiceCoupon coupon="1" entitlement="1"> <ns2:MarketingProvider checkDigit="5" name="WorldWide

AIRWAYS " number="888"



xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">12</ns2:MarketingFlightNumber

>

<ns2:ClassOfService


<ns2:FareBasis

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YOW11</ns2:FareBasis>

<ns2:StartLocation

xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">IST</ns2:StartLocation>

<ns2:StartDateTime



<ns2:EndLocation


<ns2:EndDateTime




xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC">YF</ns2:TicketDesignator>







<ns2:BookingStatus


<ns2:CurrentStatus


<ns2:BagAllowance


<ns2:CouponUse







<ns2:InvoluntaryReroute


<ns2:Reason>D</ns2:Reason>

<ns2:RerouteDescription>DIVERSION</ns2:RerouteDescription

>

</ns2:InvoluntaryReroute>

<ns2:StartTimeText


</TT:ServiceCoupon>





















4 Security validation

Introduction

Security validation is performed in order to verify whether a user requesting given document is authorized

to access it. It protects the documents data from viewing/changing by unauthorized parties, i.e. other

Airline or Travel Agency.

Security Validation on Airline path

In case of Airline path slightly different parameters are checked in terms of security validation depending

on the TktDoc function used:

- GetTicketingDocumentRQ: it is validated if the TicketingProvider (hosted carrier code) in

authentication session is the same as TicketingProvider stored in user’s security profile. If the

TicketingProvider indicated in the XML request does not match the TicketingProvider in the profile, an

error message is returned and transaction fails.

- UpdateServiceCouponRQ: it is validated if the TicketingProvider ( hosted carrier code) in

authentication session is the same as TicketingProvider (hosted carrier code) and SystemProvider (GDS or

airline code that provided the ticketing service). If it is not, an error message is returned and transaction

fails.

Security Validation on Travel Agent (Subscriber) path

In case of Travel Agent path it is checked whether the WorkLocation (PCC) in authentication session is

the same as ESSM City (PCC) or ESSM Home City (PCC of Home Location) stored in user’s security

profile. If the WorkLocation given in XML request does not match ESSM City or ESSM Home City, an

error message is returned to user and transaction fails.


5 Troubleshooting

Introduction

When reporting an issue with Web Services, please make sure to provide full XML payload (request and

response) or, if it is not possible, at least transaction ID in order to troubleshoot the problem.

Later in this document you will find the examples of common error responses that may help you identify

the cause of issue and solve the problem.

TktDoc Communication points

The steps in TktDoc Web Service operation are:

Validation of incoming requests against the STL XSD schemas published on Sabre Dev Studio.

Validation with the ICE/ESSM system whether the request comes from the user authorized to use

TktDoc Web Service.

Conversion of XML requests to:

- PSS (Passenger Service System or Sabre host) binary format in case of request coming from

Subscriber

- internal XML to T2 DMS in case of request coming from Airline

sending requests to PSS/T2 DMS via MOM (Message Oriented Middleware). MOM infrastructure

is based on Message Queue (MQ) technology to handle transaction communication

Receiving binary response from PSS via MOM in case of Travel Agent (Subscriber) path / XML

from T2 in case of Airline

Converting PSS binary response to XML response (Subscriber) / internal XML response received

from T2 to external XML response (Airline)

Providing throttling to reduce negative impact of heavy loads on Ticketing Web Services and

subsystems.

If any of these communication points experience a failure, it results in an XML error response returned to

the TktDoc Web Service client.



Common Error Responses, Reasons and Solution

This section provides examples of common error responses you might come across using TktDoc Web

Service together with the reasons and tips on how to resolve these problems.

USG Authentication Errors

This type of errors is returned when authorization to access Web Services fails for user.

5.3.1.1 USG Invalid Security Token

Error:

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Header> <eb:MessageHeader xmlns:eb="http://www.ebxml.org/namespaces/messageHeader" eb:version="1.0" soap-env:mustUnderstand="1"> <eb:From> <eb:PartyId eb:type="URI">123123</eb:PartyId> </eb:From> <eb:To> <eb:PartyId eb:type="URI">999999</eb:PartyId> </eb:To> <eb:CPAId>IPCC</eb:CPAId> <eb:ConversationId>ABC123</eb:ConversationId> <eb:Service>TicketingDocumentServicesRQ</eb:Service> <eb:Action>ErrorRS</eb:Action> <eb:MessageData> <eb:MessageId>7c292316-49fb-4ab6-af70-97d738b3ea5a@61</eb:MessageId> <eb:Timestamp>2014-03-03T13:24:37</eb:Timestamp> <eb:RefToMessageId>1000</eb:RefToMessageId> </eb:MessageData> </eb:MessageHeader> <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext"/> </soap-env:Header> <soap-env:Body> <soap-env:Fault> <faultcode>soap-env:Client.InvalidSecurityToken</faultcode> <faultstring>Invalid or Expired binary security token: null</faultstring> <detail> <StackTrace>com.sabre.universalservices.base.security.AuthenticationException: errors.session.USG_INVALID_SECURITY_TOKEN</StackTrace> </detail> </soap-env:Fault> </soap-env:Body> </soap-env:Envelope>

Reason:

Unauthorized access to the TktDoc Web Service – no USG session created.

Solution:


Before accessing TktDoc Web Service, USG session needs to be created and correct BinarySecurityToken

passed over in XML request. Please make sure you have correctly created USG session.

5.3.1.2 ESSM Authorization Failed

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="TKTHLD700-7754-533932435-1393852713633-53-tktdoc" timeStamp="2014-03-03T07:18:33" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">TKTHLD700-7754-533932435-1393852713633-53-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T07:18:33" type="Application"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="1013">ESSM authorization failed: ICE SessionException occured</STL:ErrorMessage> <STL:ShortText>ESSM authorization failed</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

Unauthorized access to the TktDoc Web Service – security authorization failed.

Solution:

Contact your Sabre Web Services support. If you are unsure, contact your Sabre Account Director. Please

remember to provide your user ID, domain, organization and environment you use.

Security violation

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-3468-1559757611-1393853597833-54-tktdoc" timeStamp="2014-03-03T14:33:17" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-3468-1559757611-1393853597833-54-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T14:33:17" type="Validation"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="21221">Security violation: Provided TicketingProvider does not match your airline code (failed rule: AirlineSecurityCheck)</STL:ErrorMessage> <STL:ShortText>Security violation</STL:ShortText> </STL:SystemSpecificResults> </STL:Error>


</STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

Unauthorized access to a partition through the TktDoc Web Service – security authorization failed.

Solution:

Contact your Sabre Web Services support. If you are unsure, contact your Sabre Account Director. Please

remember to provide your user ID, domain, organization and environment you use.

Timeout

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-3468-1559757611-1393852240726-52-tktdoc" timeStamp="2014-03-03T14:10:40" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-3468-1559757611-1393852240726-52-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T14:10:40" type="Transport"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage>Downstream system did not respond within time limit: Timeout while receive a message</STL:ErrorMessage> <STL:ShortText>Downstream system did not respond within time limit</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

There are problems receiving response from PSS/T2 DMS via MOM.

Solution:

Wait for a few minutes and try again. If the problem still exists, contact your Sabre Web Services support.

If you are unsure, contact your Sabre Account Director.

Throttled Request/Response - Airline

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-3468-1559757611-1393851080517-3-tktdoc" timeStamp="2014-03-03T13:51:20" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-3468-1559757611-1393851080517-3-tktdoc</STL:OrchestrationID> <STL:Results>


<STL:Error status="NotProcessed" timeStamp="2014-03-03T13:51:20" type="Application"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="1012">Service at peak usage - retry in few seconds: only 3 concurrently processed request(s) are allowed for TktDoc-USG-Airline</STL:ErrorMessage> <STL:ShortText>Service at peak usage - retry in few seconds</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

The service is at peak usage.

Solution:

Wait for a few minutes and try again. If the problem persists, contact your Sabre Web Services support. If

you are unsure, contact your Sabre Account Director.

Throttled Subsystem – Airline

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-5004-1683927888-1393854404619-5-tktdoc" timeStamp="2014-03-03T14:46:44" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-5004-1683927888-1393854404619-5-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T14:46:44" type="Application"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="1012">Service at peak usage - retry in few seconds: only 4 concurrently processed request(s) are allowed for DMS-SearchTicketingDocumentRQ</STL:ErrorMessage> <STL:ShortText>Service at peak usage - retry in few seconds</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

The subsystem is at peak usage.

Solution:




Throttled Request/Response – Travel Agent (Subscriber)

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-3468-1559757611-1393851785025-22-tktdoc" timeStamp="2014-03-03T14:03:05" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-3468-1559757611-1393851785025-22-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T14:03:05" type="Application"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="1012">Service at peak usage - retry in few seconds: only 3 concurrently processed request(s) are allowed for TktDoc-USG-Subscriber</STL:ErrorMessage> <STL:ShortText>Service at peak usage - retry in few seconds</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

The service is at peak usage.

Solution:



Invalid Service Version Specified in XML Request

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-5132-559856357-1393850032005-14-tktdoc" timeStamp="2014-03-03T13:33:52" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-5132-559856357-1393850032005-14-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2014-03-03T13:33:52" type="Validation"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="21212">Invalid service version specified in XML request: Schema version '0.0.0' is not supported. Supported versions: [3.5.0, 3.4.0, 3.3.0, 3.1.0, 3.0.1, 3.0.0, 2.1.4, 1.0.0]</STL:ErrorMessage> <STL:ShortText>Invalid service version specified in XML request</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS>



Reason:

The XML request sent uses unsupported version of schema.

Solution:

Send the request in one of the supported schema versions.

If you need additional assistance, use your provided Sabre Web Services contacts. If you are unsure,

contact your Sabre Account Director.

Invalid Request XML Format: Request XML Validation Failed Against Schema

Error:

<GetTicketingDocumentRS Version="3.5.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="H8460305020468-5132-559856357-1393850031677-13-tktdoc" timeStamp="2014-03-03T13:33:51" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">H8460305020468-5132-559856357-1393850031677-13-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="Incomplete" timeStamp="2014-03-03T13:33:51" type="Validation"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="21208">XML request schema validation failed: The value '8888888888888 123' in DocumentNumber field (or one of its attributes) is too long. Maximum length is 15 characters. Please amend your request and try again.</STL:ErrorMessage> <STL:ShortText>XML request schema validation failed</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </GetTicketingDocumentRS>

Reason:

The XML request sent doesn’t match the TktDoc XSD schema.

Solution:

Verify XML request with XSD schema version you used and correct it.



Database (T2 or PSS) Response: Not found

Error:

<TT:GetTicketingDocumentRS Version="3.5.0" xmlns="http://services.sabre.com/STL/v01" xmlns:STL="http://services.sabre.com/STL/v01" xmlns:TT="http://www.sabre.com/ns/Ticketing/DC" xmlns:ns2="http://www.sabre.com/ns/Ticketing/DC" xmlns:str="http://sabre.com/ticketing/xslt/strings" xmlns:xs="http://www.w3.org/2001/XMLSchema">


<STL:STL_Header.RS messageID="H8460305020468-5132-559856357-1393850030741-12-tktdoc" timeStamp="2014-03-03T13:33:50"> <OrchestrationID seq="1">H8460305020468-5132-559856357-1393850030741-12-tktdoc</OrchestrationID> <DiagnosticData>Not found</DiagnosticData> <STL:Results> <Success> <System>T2</System> <Source>DocumentServices</Source> </Success> </STL:Results> </STL:STL_Header.RS> </TT:GetTicketingDocumentRS>

Reason:

This is actually not error, but database response. The document requested was not found.

Solution:

Verify if the values of search parameters fields are correct and if needed, amend them and try again. If you

need additional assistance, use your provided Sabre Web Services contacts. If you are unsure, contact your

Sabre Account Director.

Unsupported Service Version Specified in XML Request

Error:

<TT:GetTicketingDocumentRS Version="3.8.0" xmlns:TT="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="TKTHLI701-21842-679564063-1443598088346-2193-tktdoc" timeStamp="2015-09-30T02:28:08" xmlns:STL="http://services.sabre.com/STL/v01"> <OrchestrationID xmlns="http://services.sabre.com/STL/v01" seq="1">TKTHLI701-21842-679564063-1443598088346-2193-tktdoc</OrchestrationID> <DiagnosticData xmlns="http://services.sabre.com/STL/v01">Found</DiagnosticData> <STL:Results> <Success xmlns="http://services.sabre.com/STL/v01"> <System>T2</System> <Source>DocumentServices</Source> </Success> <STL:Warning status="Incomplete" type="Application"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage>Unsupported document type EXB with result type D (Details) or C (CustomDetails) for document 6072600002465</STL:ErrorMessage> <STL:ShortText>Unsupported document type</STL:ShortText> </STL:SystemSpecificResults> </STL:Warning> </STL:Results> </STL:STL_Header.RS> </TT:GetTicketingDocumentRS>


Reason:

The request document type is not supported by the schema

Solution:

Send the request in one of the supported schema versions i.e. schema 3.9.0 or above.



Credit Card detokenization failure

Error:

<IssueTicketingDocumentRS Version="3.11.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="TKTHLI701-8492-2060129351-1459916156430-45059-tktdoc" timeStamp="2016-04-05T23:15:56" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">TKTHLI701-8492-2060129351-1459916156430-45059-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="Incomplete" timeStamp="2016-04-05T23:15:56" type="Application"> <STL:Source>TokenizerServices</STL:Source> <STL:System>TKN</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="19801">Token Failure: Detokenization failed due to Errors found in response PAN.<Token>xxxxxxxxxxxx9733</Token><PAN>Error Code: 17 Msg: Wrong token version</PAN></STL:ErrorMessage> <STL:ShortText>Token Failure</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </IssueTicketingDocumentRS>

Reason:

Incorrect token number mentioned in the request

Solution:

Re-check the token number and mention the correct token number in the request.

Multiple payments in a single payment element

Error:

<IssueTicketingDocumentRS Version="3.11.0" xmlns="http://www.sabre.com/ns/Ticketing/DC">


<STL:STL_Header.RS messageID="TKTHLI700-14200-602278729-1459766238993-26429-tktdoc" timeStamp="2016-04-04T05:37:18" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">TKTHLI700-14200-602278729-1459766238993-26429-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="Incomplete" timeStamp="2016-04-04T05:37:18" type="Validation"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="21208">XML request schema validation failed: Unexpected element Card was found, one of: Amount, Tax was expected. Please amend your request and try again.</STL:ErrorMessage> <STL:ShortText>XML request schema validation failed</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </IssueTicketingDocumentRS> </IssueTicketingDocumentRS

Reason:

Multiple payments in a single payment element are not permitted.

Solution:

Specify multiple payments in different payment elements. Also, note that user should use minimum of one

or a maximum of two forms of payment for the ticket issuance.

Multiple transactions in a single request

Error:

<IssueTicketingDocumentRS Version="3.11.0" xmlns="http://www.sabre.com/ns/Ticketing/DC"> <STL:STL_Header.RS messageID="TKTHLI701-8492-2060129351-1459765928417-26315-tktdoc" timeStamp="2016-04-04T05:32:08" xmlns:STL="http://services.sabre.com/STL/v01"> <STL:OrchestrationID seq="0">TKTHLI701-8492-2060129351-1459765928417-26315-tktdoc</STL:OrchestrationID> <STL:Results> <STL:Error status="NotProcessed" timeStamp="2016-04-04T05:32:08" type="Validation"> <STL:Source>TktDoc</STL:Source> <STL:System>TKT-WS</STL:System> <STL:SystemSpecificResults> <STL:ErrorMessage code="19901">Request content violates business validation rules: Multiple transaction elements is not supported. Please amend your request and try again.</STL:ErrorMessage> <STL:ShortText>Request content violates business validation rules</STL:ShortText> </STL:SystemSpecificResults> </STL:Error> </STL:Results> </STL:STL_Header.RS> </IssueTicketingDocumentRS>


Reason:

Multiple Transactions in a single request are not permitted.

Solution:

Perform one transaction in a single request or multiple transactions in different requests.

User Guide - Sabrefiles.developer.sabre.com/doc/providerdoc/... · Ticketing Document Web Service...

Documents

Transcript of User Guide - Sabrefiles.developer.sabre.com/doc/providerdoc/... · Ticketing Document Web Service...