travelitineraryreadrqrs v3 10 0...

PNR Services Web Service Technical Guide

User Guide TravelItineraryReadRQ

Schema Version 3.10.0

November 2017

Release 1.0

PNR Services Web Service Technical Guide

© 2012-2018, Sabre Inc. All rights reserved.

This documentation is the confidential and proprietary intellectual

property of Sabre Inc. Any unauthorized use, reproduction, preparation

of derivative works, performance, or display of this document, or

software represented by this document, without the express written

permission of Sabre Inc. is strictly prohibited.

Sabre Travel Network and the Sabre Travel Network logo design are

trademarks and/or service marks of an affiliate of Sabre Inc. All other

trademarks, service marks, and trade names are owned by their

respective companies.

Sabre Inc. Confidential/All Rights Reserved Web Service Technical Guide

D O C U M E N T R E V I S I O N I N F O R M A T I O N

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

Project Name PNR TIR Services Project Number TIR 3.10.0

Prepared by PNR SVC team Date Prepared November 2017

Revised by Date Prepared

Revision Reason

Revised by Date Prepared

Revision Reason

Revised by

Revision Reason

Revised by

Revision Reason

Sabre Inc. Confidential/All Rights Reserved Web Service Technical Guide

T a b l e o f C o n t e n t s

D O C U M E N T R E V I S I O N I N F O R M A T I O N

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i i

P r o c e s s O v e r v i e w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1. Introduction................................................................................................................................... 4 1.2. About This Guide .......................................................................................................................... 4 1.3. Availability .................................................................................................................................... 4 1.4. High level design .......................................................................................................................... 5 1.5. New Features Added to TravelItineraryReadRQ_3.10.0 Versions of the Service ........................ 6

T r a v e l I t i n e r a r y R e a d R e q u e s t a n d R e s p o n s e s t r u c t u r e . . . . . . . . . . . . . . . . 7

2.1 Introduction ........................................................................................................................................ 7 2.2 Processing Information ....................................................................................................................... 7 2.4 Service version and Response formats .............................................................................................. 7 2.1 Request and response structure .................................................................................................. 8 2.1.1 TravelItineraryReadRQ request message (RQ) ....................................................................... 8 2.1.2 (RQ)Subject Areas ................................................................................................................... 9 2.1.3 (RQ)UniqueID ........................................................................................................................ 11 2.1.4 (RQ) ReturnOptions ............................................................................................................... 11 2.2 (RS) Response message ........................................................................................................... 11 2.3 Service Security ......................................................................................................................... 22

D e f i n e d E r r o r s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3

3.1 Error List ..................................................................................................................................... 23

T e c h n i c a l S u p p o r t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 6

4.1 Who should I contact for query help ........................................................................................... 26 4.2 First Level Support ..................................................................................................................... 26

G l o s s a r y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7

Sabre Inc. Confidential/All Rights Reserved Process Overview 4

Process Overview

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

This guide is for architects and developers to learn how to compose XML formatted requests for

TravelItineraryRead Requests. This release covers the XML request and responses which allow client

applications to retrieve PNR data including Itinerary, Passenger information, etc. (details below).

1 . 2 . A b o u t T h i s G u i d e

The purpose of this document is to describe how the web service works and provide details how to

create a successful request transaction. This document also provides details on the response

transaction, including any errors. Each chapter is as follows:

• Chapter 1, “Processing Information” explains the purpose of the document, details critical

information, and provides an high level overview on the API.

• Chapter 2, “TravelItineraryRead Request and Response structure” contains descriptions of the

attributes and elements in the response schema.

• Chapter 3, “Defined Errors” contains error codes and descriptions.

• Chapter 5, “Technical Support” contains information on where to get help.

• The “Glossary” provides a glossary of terms used in this document.

1 . 3 . A v a i l a b i l i t y

This service can be used by:

• Sabre Dev Studio subscribers.

• Sabre Travel Network customers – travel agencies working on Sabre® Red Workspace™ and other

Sabre user interfaces.

• Airlines

• Third-party customers.

Both internal and external consumers can take benefits from TravelItineraryReadRQ as a part of Sabre

API. The service runs in 24x7 mode. In case of any planned maintenance windows, we send the wide

standard notifications in advance.

1


Specific service capabilities may require dedicated activations.

In case of any doubts, we recommend contacting our Technical Support. Please contact us also if you

plan to start using the service intensively with a high volume of requests, so that we will be able to tune

the service fit for your purposes and ensure the search process will always run smoothly.

1 . 4 . H i g h l e v e l d e s i g n

Once a PNR has been created on the Sabre Host, this web service offers functionality to allow the Airline

or Agency to search for and retrieve particular PNR data directly from AAA session. If PNR is not unpacked

into AAA already then PNR Locator can be provided into request to specify which PNR should be unpacked

and retrieved.


1 . 5 . N e w F e a t u r e s A d d e d t o T r a v e l I t i n e r a r y R e a d R Q _ 3 . 1 0 . 0 V e r s i o n s o f

t h e S e r v i c e

The following are new features that have been added to 3.10.0 versions of TravelItineraryReadRQ

Service:

Feature Description

Retrieve the owning agency PCC along with profile index from TravelItineraryRead

Feature for users of TravelItineraryRead service to retrieve the owning agency PCC along with profile index when retrieving a PNR.

Implementation of full TravelItineraryReadRQ flow with RBD

Implementation of support for new AIR_CABIN subject area in TravelItineraryReadRQ requests. Using it triggers the functionality for RBD i.e. decorating products with extended cabin class info. The new RBD (Reservation Booking Designator) Answer Table provides subscribers the IATA default for RBD cabin mapping stated in Resolution 728 using the industry carrier code YY, as well as carriers’ exceptions listing their RBDs and associated cabin (Premium First, First, Premium Business, Business, Premium Economy, and Economy).

Extend insurance product for annual multi trip

Added ability for users to enter shop criteria which are required for AMT product to be returned. Added functionality for NSRW users to shop and save Annual Multi-Trip product/quote. The extension contains update of schemas that contain additional filed MaxDurationDays in InsuranceProduct.

PriceCache OpenReservationElement Support for PriceCache OpenReservationElement used to store pricing parameters

Sabre Inc. Confidential/All Rights Reserved TravelItineraryRead Request and Response structure 7

2 TravelItineraryRead Request and Response structure

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

The Get Itinerary (TravelItineraryReadRQ) API is used to retrieve and display a passenger name record

(PNR) and data that are related to PNR.

This chapter includes the following:

• Processing Information (see this page).

• Overview of Request and Response Updates (see “Overview of Request and Response Updates”).

• Service version and response formats (see “Service version and response formats “).

• Request and Response structure (see “Request and Response structure”).

• Service security (see “Service security”).

2 . 2 P r o c e s s i n g I n f o r m a t i o n

Once a PNR has been created on the Sabre Host, this Web Service offers capabilities allowing Airline or

Agency to retrieve PNR data using PNR Locator as a search criterion. Request payload can be specified by

using “ReturnOptions” which determine response message content.

“ReturnOptions” element can be used to specify which data elements will be present in response

payload, as well as how those will be formatted:

– XML “ResponseFormat” – specifies in what format the response should be returned (OTA or TVL)

– “SubjectAreas” – specifies what kind of information should be returned in response (Itinerary,

Pricing Information, etc.)

2 . 4 S e r v i c e v e r s i o n a n d R e s p o n s e f o r m a t s

The correct TravelItineraryReadRQ request needs version and Unique ID ID.


< TravelItineraryReadRQ Version="{SupportedVersion}" ... >

<MessagingDetails>

<SubjectAreas>

<SubjectArea>FULL</SubjectArea>

</SubjectAreas>

</MessagingDetails>

<UniqueID ID="DJGQOI"/>

<EchoToken/>

</TravelItineraryReadRQ>

You should specify 3.10.0 as {SupportedVersion}. The version attribute value should not contain any

additional prefixes nor suffixes. Only digits and dots should be provided as version attribute value.

Please note that according to Sabre Versioning Policy only the last five versions of the service is

supported, so it is recommended to always use the most recent version.

2 . 1 R e q u e s t a n d r e s p o n s e s t r u c t u r e

PNR data will be returned depending on the SubjectAreas selected. Information from Subject Areas will

be provided in response message if the data is present in the PNR.

For more details please review the following:

• Subject Areas (see “Subject Areas,” page Error! Bookmark not defined.).

2 . 1 . 1 T r a v e l I t i n e r a r y R e a d R Q r e q u e s t m e s s a g e ( R Q )

An overview on the TravelItineraryReadRQ service design, with the key XML sections highlighted, is

presented below. For more information please refer to next paragraphs as well as to the corresponding

WSDL and XSD files.


HEADER:

It contains e.g. BinarySecurityToken obtained when authorizing user’s web service session.

BODY:

< TravelItineraryReadRQ> required block, some its attributes like Version are required too.

<Version> is required attribute

< TimeStamp > optional attribute

<UniqueID> is optional block

<ID> required attribute

<SnapshotID> optional attribute

<CreateDate> optional attribute, Pnr creation date used for retrieving inactive pnr

<MessagingDetails> this element is used as a container for defining data range in response message.

< SubjectAreas > required block - "SubjectAreas" is used as a container for "SubjectAreas" which can be used within “View”.

< RerurnOptions > is optional block

<UnmaskCreditCard>

<ShowTicketStatus> ShowTicketStatus" is for specifying whether user wants status for each ticket or not.

<Language> "Language" is used to translate attributes (like Cabin name).

<EchoToken>

2 . 1 . 2 ( R Q ) S u b j e c t A r e a s

Container: SubjectAreas

- “SubjectAreas” specify particular information to be included in response payload if they are stored in the

PNR and can be used to range amount of data returned.

PNR data which will be present in response payload depends on list of Subject Areas used in the request.

Subject Areas could be used to narrow down number of elements returned. Following Subject Areas are

available:

Subject Areas Description

PRIMARY SUBJECT AREAS

ACCOUNTING_LINES Agency accounting lines stored in PNR.

AGENCY_ADDRESS Agency address data stored in PNR.

AIR_CABIN Extended cabin class information about the product.


DK_NUMBER Customer number stored in PNR– agencies use DK number primarily as an account reference identifier for billing purposes.

DSS Additional information about flight retrieved from Sabre scheduling system (DSS).

FREQUENT_FLYER Frequent Flyer details stored in PNR.

GENERAL_FACTS General facts stored in PNR.

HEADER PNR header data.

HOSTED_FACTS Hosted facts stored in PNR.

ITINERARY Full itinerary data stored in the PNR including Air, Rail, Car, Hotel, etc.

NAME Passenger Name stored in the PNR.

PASSENGER_DETAILS Profile data, passenger type, email address etc. stored in PNR.

PAY_INFO Form of payment data stored in PNR.

PRICING_INFORMATION Pricing data stored in PQ record.

PRERESERVED_SEAT Pre reserved seat data stored in PNR.

PRICE_QUOTE1 PQ data received from PQ web service.

PROFILE_INDEX Customer Profile data stored in PNR.

RECEIVED_FROM Received From Field stored in PNR.

TICKETING Ticketing information stored in PNR.

TTY_RECORD_LOCATOR PNR Record locator (rloc)

AGGREGATED SUBJECT AREAS

SIMPLE It is always used regardless it is provided in the request or not. Includes: HEADER (Booking and Point of Sale details); NAME (Name Field data); ITINERARY (itinerary data); BAS_EXTENSION (extended information attached to Air segment);

DEFAULT It will be used if no Subject Area is provided in the RQ payload. Includes: SIMPLE; all ACTIVE SUBJECT AREAS2 except PRICING_INFORMATION;

FULL Includes: SIMPLE; all PRIMARY Subject Areas;

1 PriceQuote Web Service is enhanced to support search and display Price Quote Records functionality.

PriceQuote Web Service will return all the PQ records based on the search parameters in the request. The

service is applicable for all price quote users (basic and enhanced PQ).

The service returns the generic response in a standard XML format which is not different based on the

requestor’s GDS. The service will send the data display to the client and it is the client’s application which

is responsible for formatting and presenting the data as required to the end user.

The various fare levels are as below:

• Adjusted Selling Fare data

• Net Fare data (i.e. *PQ#N data), when the user has NETFQD EPR keyword

• Original Fare data (i.e. *PQ#O data), when the user has ORGFQD EPR keyword


• Retailer Fare data (i.e. *PQ#R data), when the user has AGYRET EPR keyword.

For more information please go to PriceQuote Web Service User Guide, where you can read wide

description of the PQ Web Service. The documentation mentioned above is the most up-to-date

description that is available on dev studio.

User Guide of PriceQuote Web Service (linked above) provides information about types of operations that

the service supports and points out the ones that are not valid PriceQuoteServicesRQ requests. It also

contains an explanation of essential terms associated with the PriceQuote Web Service transactions.

2 Active Subject Areas contain information such as: Header, Name, Agency address, Itinerary, Record

LocatorPhone, Ancillary, Passenger details, Frequent Traveller information, Customer number, General

facts, Hosted facts, Prereserved seat, Remarks, Ticeting information, accounting lines, Subscription Card,

Group planner, Travel policy, Corporate ID, Customer profile, Received From, Descriptive billing Info, VCR.

2 . 1 . 3 ( R Q ) U n i q u e I D

Element: UniqueID

- “UniqueID” is optional because on default PNR data are taken from current user session (AAA). If provided

then data for particular PNR will be retrieved regardless if there is other PNR in AAA or not. However if PNR

in AAA has already been modified then request with ‘UniqueID’ will be rejected.

2 . 1 . 4 ( R Q ) R e t u r n O p t i o n s

Element: ReturnOptions

- “ReturnOptions” is optional element it contains the attribute UnmaskCreditCard. By default the value of

the attribute is false. When a request is made with this attribute as true by the user having the EPR

keywords CCVIEW, in the response the credit card information will be presented in unmasked format, else

the credit card information will always be in masked format

2 . 2 ( R S ) R e s p o n s e m e s s a g e

The response message consists of elements and attributes, defined in the Schema.

The response is an XML file that contains data stored in PNRs that was requested. PNR data which might

be present in response message depends also on the security defined by viewership rules (for more

information please review Service Security).

Below you can find a sample of request and response corresponding.

http://webservices.sabre.com/drc/providerdoc/pnrservices/TravelItineraryReadRQRS_v3_5_0_UserGuide.pdf


Sample request:

<TravelItineraryReadRQ Version="3.10.0" TimeStamp="2012-09-19T10:00:00-06:00"

xmlns="http://services.sabre.com/res/tir/v3_10" xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dd="http://webservices.sabre.com/dd2">

<MessagingDetails>

<SubjectAreas>

<SubjectArea>FULL</SubjectArea>

<SubjectArea>AIR_CABIN</SubjectArea>

</SubjectAreas>

</MessagingDetails>

<UniqueID ID="VKSLRM"/>

<EchoToken/>

</TravelItineraryReadRQ>

Sample response:

<tir310:TravelItineraryReadRS Version="3.10.0" xmlns:tir310="http://services.sabre.com/res/tir/v3_10"

xmlns:stl="http://services.sabre.com/STL/v01" xmlns:or110="http://services.sabre.com/res/or/v1_11">

<stl:ApplicationResults status="Complete">

<stl:Success timeStamp="2018-01-24T05:36:43.578-06:00"/>

</stl:ApplicationResults>

<tir310:TravelItinerary>

<tir310:CustomerInfo>

<tir310:ContactNumbers>

<tir310:ContactNumber LocationCode="DFW" Phone="8856663321-H"

RPH="001" Id="5"/>

</tir310:ContactNumbers>

<tir310:PersonName WithInfant="false" NameNumber="01.01" PassengerType="ADT"

RPH="1" elementId="pnr-3.1">

<tir310:GivenName>IRON</tir310:GivenName>

<tir310:Surname>MAIDEN</tir310:Surname>

</tir310:PersonName>

</tir310:CustomerInfo>

<tir310:ItineraryInfo>

<tir310:ItineraryPricing>

<tir310:PriceQuote RPH="1">

<tir310:MiscInformation>

<tir310:SignatureLine ExpirationDateTime="00:00"

Source="SYS" Status="ACTIVE">

<tir310:Text>B4T0 HDQ *VLZ

0713/23JAN18</tir310:Text>

</tir310:SignatureLine>

</tir310:MiscInformation>

<tir310:PricedItinerary DisplayOnly="false" InputMessage="WP"

RPH="1" StatusCode="A" TaxExempt="false" ValidatingCarrier="JQ" StoredDateTime="2018-01-23T07:13">


<tir310:AirItineraryPricingInfo>

<tir310:ItinTotalFare>

<tir310:BaseFare Amount="1330.30"

CurrencyCode="AUD"/>

<tir310:EquivFare Amount="1064.00"

CurrencyCode="USD"/>

<tir310:Taxes>

<tir310:Tax Amount="27.10"

TaxCode="XT"/>

<tir310:TaxBreakdownCode

TaxPaid="false">19.40QR</tir310:TaxBreakdownCode>

<tir310:TaxBreakdownCode

TaxPaid="false">7.70WG</tir310:TaxBreakdownCode>

</tir310:Taxes>

<tir310:TotalFare Amount="1091.10"

CurrencyCode="USD"/>

<tir310:Totals>

<tir310:BaseFare

Amount="1330.30"/>

<tir310:EquivFare

Amount="1064.00"/>

<tir310:Taxes>

<tir310:Tax

Amount="27.10"/>

</tir310:Taxes>

<tir310:TotalFare

Amount="1091.10"/>

</tir310:Totals>

</tir310:ItinTotalFare>

<tir310:PassengerTypeQuantity Code="ADT"

Quantity="01"/>

<tir310:PTC_FareBreakdown>

<tir310:Endorsements>

<tir310:Endorsement

type="PRICING_PARAMETER">

<tir310:Text>WP</tir310:Text>

</tir310:Endorsement>

<tir310:Endorsement

type="WARNING">

<tir310:Text>VALIDATING

CARRIER - JQ</tir310:Text>


<tir310:Endorsement

type="WARNING">

<tir310:Text>CAT 15 SALES

RESTRICTIONS FREE TEXT FOUND - VERIFY RULES</tir310:Text>


<tir310:Endorsement

type="SYSTEM_ENDORSEMENT">

<tir310:Text>CARRIER

RESTRICTIONS APPLY/PENALTIES APPLY</tir310:Text>



</tir310:Endorsements>

<tir310:FareBasis Code="YLOW/YLOW"/>

<tir310:FareCalculation>

<tir310:Text>SYD JQ

PER665.15YLOW JQ SYD665.15YLOW AUD1330.30END</tir310:Text>

</tir310:FareCalculation>

<tir310:FareSource>ATPC</tir310:FareSource>

<tir310:FlightSegment ConnectionInd="O"

DepartureDateTime="03-29T20:30" FlightNumber="988" ResBookDesigCode="Y" SegmentNumber="1"

Status="OK">

<tir310:BaggageAllowance

Number="30K"/>

<tir310:FareBasis Code="YLOW"/>

<tir310:MarketingAirline Code="JQ"

FlightNumber="988"/>

<tir310:OriginLocation

LocationCode="SYD"/>

<tir310:ValidityDates>

<tir310:NotValidAfter>2019-03-29</tir310:NotValidAfter>

</tir310:ValidityDates>

</tir310:FlightSegment>

<tir310:FlightSegment ConnectionInd="O"

DepartureDateTime="04-13T00:05" FlightNumber="989" ResBookDesigCode="Y" SegmentNumber="2"

Status="OK">

<tir310:BaggageAllowance

Number="30K"/>

<tir310:FareBasis Code="YLOW"/>

<tir310:MarketingAirline Code="JQ"

FlightNumber="989"/>


LocationCode="PER"/>

<tir310:ValidityDates>

<tir310:NotValidAfter>2019-03-29</tir310:NotValidAfter>

</tir310:ValidityDates>


<tir310:FlightSegment>


LocationCode="SYD"/>


<tir310:FareComponent

FareBasisCode="YLOW" FareDirectionality="FROM" Amount="66515" TicketDesignator="" GoverningCarrier="JQ"

FareComponentNumber="1">

<tir310:Location Origin="SYD"

Destination="PER"/>

<tir310:Dates

DepartureDateTime="03-29T20:30" ArrivalDateTime="03-29T22:35"/>

<tir310:FlightSegmentNumbers>

<tir310:FlightSegmentNumber>1</tir310:FlightSegmentNumber>

</tir310:FlightSegmentNumbers>


</tir310:FareComponent>

<tir310:FareComponent

FareBasisCode="YLOW" FareDirectionality="TO" Amount="66515" TicketDesignator="" GoverningCarrier="JQ"

FareComponentNumber="2">

<tir310:Location Origin="PER"

Destination="SYD"/>

<tir310:Dates

DepartureDateTime="04-13T00:05" ArrivalDateTime="04-13T06:20"/>

<tir310:FlightSegmentNumbers>

<tir310:FlightSegmentNumber>2</tir310:FlightSegmentNumber>

</tir310:FlightSegmentNumbers>

</tir310:FareComponent>

<tir310:ResTicketingRestrictions>LAST DAY

TO PURCHASE 28JAN/2359</tir310:ResTicketingRestrictions>

<tir310:ResTicketingRestrictions>GUARANTEED FARE APPL IF PURCHASED BEFORE

28JAN</tir310:ResTicketingRestrictions>

</tir310:PTC_FareBreakdown>

</tir310:AirItineraryPricingInfo>

</tir310:PricedItinerary>

<tir310:ResponseHeader>

<tir310:Text>FARE - PRICE RETAINED</tir310:Text>

<tir310:Text>FARE USED TO CALCULATE

DISCOUNT</tir310:Text>

<tir310:Text>FARE NOT GUARANTEED UNTIL

TICKETED</tir310:Text>

</tir310:ResponseHeader>

<tir310:PriceQuotePlus DomesticIntlInd="I" PricingStatus="S"

VerifyFareCalc="false" ItineraryChanged="false" ManualFare="false" NegotiatedFare="false" SystemIndicator="S"

NUCSuppresion="false" SubjToGovtApproval="false" IT_BT_Fare="BT" DisplayOnly="false" DiscountAmount="0">

<tir310:PassengerInfo PassengerType="ADT">

<tir310:PassengerData

NameNumber="01.01">MAIDEN/IRON</tir310:PassengerData>

</tir310:PassengerInfo>

<tir310:TicketingInstructionsInfo/>

</tir310:PriceQuotePlus>

</tir310:PriceQuote>

<tir310:PriceQuoteTotals>

<tir310:BaseFare Amount="1330.30"/>

<tir310:EquivFare Amount="1064.00"/>

<tir310:Taxes>

<tir310:Tax Amount="27.10"/>

</tir310:Taxes>

<tir310:TotalFare Amount="1091.10"/>

</tir310:PriceQuoteTotals>

</tir310:ItineraryPricing>

<tir310:ReservationItems>

<tir310:Item RPH="1">

<tir310:FlightSegment AirMilesFlown="2040" ArrivalDateTime="03-

29T22:35" DayOfWeekInd="4" DepartureDateTime="2018-03-29T20:30" SegmentBookedDate="2018-01-

23T06:23:00" ElapsedTime="05.05" eTicket="true" FlightNumber="0988" NumberInParty="01"


ResBookDesigCode="Y" SegmentNumber="0001" SmokingAllowed="false" SpecialMeal="false" Status="HK"

StopQuantity="00" IsPast="false" CodeShare="false" Id="6">

<tir310:DestinationLocation LocationCode="PER"

Terminal="TERMINAL 3 DOMESTIC" TerminalCode="3"/>

<tir310:Equipment AirEquipType="320"/>

<tir310:MarketingAirline Code="JQ" FlightNumber="0988">

<tir310:Banner>MARKETED BY JETSTAR

AIRWAYS</tir310:Banner>

</tir310:MarketingAirline>

<tir310:OperatingAirline Code="JQ" FlightNumber="0988"

ResBookDesigCode="Y">

<tir310:Banner>OPERATED BY JETSTAR


</tir310:OperatingAirline>

<tir310:OperatingAirlinePricing Code="JQ"/>

<tir310:DisclosureCarrier Code="JQ" DOT="false">

<tir310:Banner>JETSTAR AIRWAYS</tir310:Banner>

</tir310:DisclosureCarrier>

<tir310:OriginLocation LocationCode="SYD"


<tir310:SupplierRef ID="ABRQ"/>

<tir310:UpdatedArrivalTime>03-

29T22:35</tir310:UpdatedArrivalTime>

<tir310:UpdatedDepartureTime>03-

29T20:30</tir310:UpdatedDepartureTime>

<tir310:Cabin Code="Y" SabreCode="Y" Name="ECONOMY"

ShortName="ECONOMY" Lang="EN"/>


<tir310:Product>

<or110:ProductDetails productCategory="AIR">

<or110:ProductName type="AIR"/>

<or110:Air>

<or110:DepartureAirport>SYD</or110:DepartureAirport>

<or110:DepartureTerminalName>TERMINAL

2 DOMESTIC</or110:DepartureTerminalName>

<or110:DepartureTerminalCode>2</or110:DepartureTerminalCode>

<or110:ArrivalAirport>PER</or110:ArrivalAirport>

<or110:ArrivalTerminalName>TERMINAL 3

DOMESTIC</or110:ArrivalTerminalName>

<or110:ArrivalTerminalCode>3</or110:ArrivalTerminalCode>

<or110:EquipmentType>320</or110:EquipmentType>

<or110:MarketingAirlineCode>JQ</or110:MarketingAirlineCode>

<or110:MarketingFlightNumber>988</or110:MarketingFlightNumber>

<or110:MarketingClassOfService>Y</or110:MarketingClassOfService>


<or110:Cabin code="Y" sabreCode="Y"

name="ECONOMY" shortName="ECONOMY" lang="EN"/>

<or110:ElapsedTime>305</or110:ElapsedTime>

<or110:AirMilesFlown>2040</or110:AirMilesFlown>

<or110:FunnelFlight>false</or110:FunnelFlight>

<or110:ChangeOfGauge>false</or110:ChangeOfGauge>

<or110:DisclosureCarrier Code="JQ"

DOT="false">

<or110:Banner>JETSTAR

AIRWAYS</or110:Banner>

</or110:DisclosureCarrier>

<or110:AirlineRefId>ABRQ*</or110:AirlineRefId>

<or110:Eticket>true</or110:Eticket>

<or110:DepartureDateTime>2018-03-

29T20:30:00</or110:DepartureDateTime>

<or110:ArrivalDateTime>2018-03-

29T22:35:00</or110:ArrivalDateTime>

<or110:FlightNumber>988</or110:FlightNumber>

<or110:ClassOfService>Y</or110:ClassOfService>

<or110:ActionCode>HK</or110:ActionCode>

<or110:NumberInParty>1</or110:NumberInParty>

</or110:Air>

</or110:ProductDetails>

</tir310:Product>

</tir310:Item>

<tir310:Item RPH="2">

<tir310:FlightSegment AirMilesFlown="2040" ArrivalDateTime="04-

13T06:20" DayOfWeekInd="5" DepartureDateTime="2018-04-13T00:05" SegmentBookedDate="2018-01-

23T06:23:00" ElapsedTime="04.15" eTicket="true" FlightNumber="0989" NumberInParty="01"

ResBookDesigCode="Y" SegmentNumber="0002" SmokingAllowed="false" SpecialMeal="false" Status="HK"

StopQuantity="00" IsPast="false" CodeShare="false" Id="7">

<tir310:DestinationLocation LocationCode="SYD"


<tir310:Equipment AirEquipType="320"/>

<tir310:MarketingAirline Code="JQ" FlightNumber="0989">

<tir310:Banner>MARKETED BY JETSTAR


</tir310:MarketingAirline>

<tir310:OperatingAirline Code="JQ" FlightNumber="0989"

ResBookDesigCode="Y">

<tir310:Banner>OPERATED BY JETSTAR


</tir310:OperatingAirline>

<tir310:OperatingAirlinePricing Code="JQ"/>

<tir310:DisclosureCarrier Code="JQ" DOT="false">


<tir310:Banner>JETSTAR AIRWAYS</tir310:Banner>

</tir310:DisclosureCarrier>

<tir310:OriginLocation LocationCode="PER"


<tir310:SupplierRef ID="ABRQ"/>

<tir310:UpdatedArrivalTime>04-

13T06:20</tir310:UpdatedArrivalTime>

<tir310:UpdatedDepartureTime>04-

13T00:05</tir310:UpdatedDepartureTime>

<tir310:Cabin Code="Y" SabreCode="Y" Name="ECONOMY"

ShortName="ECONOMY" Lang="EN"/>


<tir310:Product>

<or110:ProductDetails productCategory="AIR">

<or110:ProductName type="AIR"/>

<or110:Air>

<or110:DepartureAirport>PER</or110:DepartureAirport>

<or110:DepartureTerminalName>TERMINAL

3 DOMESTIC</or110:DepartureTerminalName>

<or110:DepartureTerminalCode>3</or110:DepartureTerminalCode>

<or110:ArrivalAirport>SYD</or110:ArrivalAirport>

<or110:ArrivalTerminalName>TERMINAL 2

DOMESTIC</or110:ArrivalTerminalName>

<or110:ArrivalTerminalCode>2</or110:ArrivalTerminalCode>

<or110:EquipmentType>320</or110:EquipmentType>

<or110:MarketingAirlineCode>JQ</or110:MarketingAirlineCode>

<or110:MarketingFlightNumber>989</or110:MarketingFlightNumber>

<or110:MarketingClassOfService>Y</or110:MarketingClassOfService>

<or110:Cabin code="Y" sabreCode="Y"

name="ECONOMY" shortName="ECONOMY" lang="EN"/>

<or110:ElapsedTime>255</or110:ElapsedTime>

<or110:AirMilesFlown>2040</or110:AirMilesFlown>

<or110:FunnelFlight>false</or110:FunnelFlight>

<or110:ChangeOfGauge>false</or110:ChangeOfGauge>

<or110:DisclosureCarrier Code="JQ"

DOT="false">

<or110:Banner>JETSTAR

AIRWAYS</or110:Banner>

</or110:DisclosureCarrier>

<or110:AirlineRefId>ABRQ*</or110:AirlineRefId>


<or110:Eticket>true</or110:Eticket>

<or110:DepartureDateTime>2018-04-

13T00:05:00</or110:DepartureDateTime>

<or110:ArrivalDateTime>2018-04-

13T06:20:00</or110:ArrivalDateTime>

<or110:FlightNumber>989</or110:FlightNumber>

<or110:ClassOfService>Y</or110:ClassOfService>

<or110:ActionCode>HK</or110:ActionCode>

<or110:NumberInParty>1</or110:NumberInParty>

</or110:Air>

</or110:ProductDetails>

</tir310:Product>

</tir310:Item>

</tir310:ReservationItems>

<tir310:Ticketing RPH="01" TicketTimeLimit="TAWB4T025JAN009/0400A/"/>

</tir310:ItineraryInfo>

<tir310:ItineraryRef AirExtras="false" CustomerIdentifier="1234567890" ID="VKSLRM"

InhibitCode="U" PartitionID="AA" PrimeHostID="1S">

<tir310:Source AAA_PseudoCityCode="HDQ" CreateDateTime="2018-01-23T06:23"

CreationAgent="VLZ" HomePseudoCityCode="HDQ" PseudoCityCode="B4T0" ReceivedFrom="ZAMOJ"

LastUpdateDateTime="2018-01-23T06:23" SequenceNumber="1"/>

</tir310:ItineraryRef>

<tir310:SpecialServiceInfo RPH="001" Type="GFX" Id="11">

<tir310:Service SSR_Code="SSR" SSR_Type="OTHS">

<tir310:Airline Code="JQ"/>

<tir310:Text>AX11482755558239001EXP 21 11</tir310:Text>

</tir310:Service>

</tir310:SpecialServiceInfo>





</tir310:Service>





<tir310:Text>CH PROND BYL</tir310:Text>

</tir310:Service>






</tir310:Service>





<tir310:Text>AX3403 513885 71610EXP 09 19</tir310:Text>


</tir310:Service>





<tir310:Text>AX3XXXXXXXXXX1610EXP 03 19</tir310:Text>

</tir310:Service>






</tir310:Service>




<tir310:Airline Code="YY"/>


</tir310:Service>





<tir310:Text>VI4XXXXXXXXXXX5251EXP 03 19</tir310:Text>

</tir310:Service>





<tir310:Text>VI4XXXXXXXXXXX5251EXP 3 19</tir310:Text>

</tir310:Service>


<tir310:OpenReservationElements>

<or110:OpenReservationElement id="6" elementId="pnr-or-6"/>




<or110:OpenReservationElement id="11" type="SRVC" elementId="pnr-11">

<or110:ServiceRequest airlineCode="JQ" code="OTHS" serviceType="SSR"

ssrType="GFX">

<or110:FreeText>AX11482755558239001EXP 21 11</or110:FreeText>

<or110:FullText>OTHS JQ AX11482755558239001EXP 21

11</or110:FullText>

</or110:ServiceRequest>

</or110:OpenReservationElement>



ssrType="GFX">



21</or110:FullText>






ssrType="GFX">

<or110:FreeText>CH PROND BYL</or110:FreeText>

<or110:FullText>OTHS JQ CH PROND BYL</or110:FullText>





ssrType="GFX">



19</or110:FullText>





ssrType="GFX">

<or110:FreeText>AX3403 513885 71610EXP 09 19</or110:FreeText>

<or110:FullText>OTHS JQ AX3403 513885 71610EXP 09

19</or110:FullText>





ssrType="GFX">

<or110:FreeText>AX3XXXXXXXXXX1610EXP 03 19</or110:FreeText>

<or110:FullText>OTHS JQ AX3XXXXXXXXXX1610EXP 03

19</or110:FullText>





ssrType="GFX">


<or110:FullText>OTHS JQ AX3XXXXXXXXXX1610EXP 03

19</or110:FullText>




<or110:ServiceRequest airlineCode="YY" code="OTHS" serviceType="SSR"

ssrType="GFX">


<or110:FullText>OTHS YY AX3XXXXXXXXXX1610EXP 03

19</or110:FullText>





ssrType="GFX">

<or110:FreeText>VI4XXXXXXXXXXX5251EXP 03 19</or110:FreeText>

<or110:FullText>OTHS YY VI4XXXXXXXXXXX5251EXP 03

19</or110:FullText>






ssrType="GFX">

<or110:FreeText>VI4XXXXXXXXXXX5251EXP 3 19</or110:FreeText>

<or110:FullText>OTHS YY VI4XXXXXXXXXXX5251EXP 3

19</or110:FullText>



</tir310:OpenReservationElements>

</tir310:TravelItinerary>

</tir310:TravelItineraryReadRS>

2 . 3 S e r v i c e S e c u r i t y

PNR related data retrieving options are available only to authorized users that provided a valid token in

the web service request. For most of available data, the TravelItineraryReadRQ supports branch access

and global branch access rules in a consistent manner as the native Sabre application. Users can retrieve

data only from the partitions and/or PCCs they have access to. In a common case, it means that a user of

given Airline cannot access data of any other carrier unless it is allowed in the native Sabre system.

Viewership rules suppress the display of PNR or specific information connected to the PNR. The data

viewership rules are based on:

• PNR ownership

• Who is trying to view the data (Business Area AS / TN)

As PNR viewership are controlled at a PCC level it is not the subject of this User Guide. For more

information about particular viewership rules please contact your Accounting manager.

Sabre Inc. Confidential/All Rights Reserved Defined Errors 23

Defined Errors

3 . 1 E r r o r L i s t

There is a list of most common error messages that are returned presented below.

Error Code Message

700001 General PNR error

700002 Invalid PNR locator

700003 Invalid request

700004 Invalid request format

700005 Invalid request view

700101 No PNR was found with the specified record locator

700102 Viewership is restricted for the PNR

700103 No data for the PNR in DB

700104 Error parsing PNR

700201 PNR Connector unknown

700202 PNR Connector communication error

700203 PNR Connector communication timeout error

700204 JAXB marshalling error

700205 JAXB unmarshalling error

700206 unexpected request type

700207 MOM messaging error

700208 PNRC service invocation error

700209 error response from PNRC reaccomodation search service

700210 unknown response format

700211 OTA parsing error

700212 Cannot unpack request from request root element

700213 Cannot pack response to response root element

700214 error response from PNRC reaccomodation retrieve service

700215 TPFDF parsing exception

700216 No ATH

700217 Invalid ICE Session

700218 Broken ICE Session

700219 FIT parsing exception

700220 Invalid ICE credentials

700221 Access restricted to flight data

3


700223 Access restricted to PNR data

700224 Flight not found

700225 Invalid search options

700226 PNR not found

700227 TVL version not supported

700301 PDC unknown error

700302 PDC communication error

700303 PDC communication timeout error

700304 Profile (CI) Database Connection Error Database is down or configuration is invalid

700305 Profile (CI) Database Error - Database returned error while performing some operation

700306 Invalid XML Error - Request that PDC received was not valid according to the schema for that service

700307 ICE authentication error - Either no ICE session ID was provided with the request, or user who created that session does not have required credentials

700308 ICE authorization error - User is not allowed to access requested profiles

700309 Unable to locate service provider via Meridian NS

700310 CORBA No permission condition raised.

700311 Communication with service provider interrupted

700312 Unable to obtain authorization via ICE - Should never appear - ICE authorization/authentication is handled by PDC

700313 Uncategorized error - Any error that doesn't fit into existing categories

700314 P3 timeout error - No response from P3

700315 PNR Unknown error

700401

700402 PNR Communication error

700403 PNR Communication timeout

700404 Unable to read terminal

700405 Unable to Find AAA

700406 Agent not signed in

700407 PNR Locator error

700408 No PNR in AAA

700409 PNR Retrieval error

700410 PSS invalid request

700411 The PNR in the AAA has been modified

700412 Agent is active on a PNR queue

700414 Unable to process in PSS

700415 Parsing error

700418 Access restricted to flight data


700420 PSS Communication error

700421 PSS Communication timeout


700423 PNR Restricted


700424 PNR Not Found

700425 PNRC Timeout Error code

700426 PNR Database unavailable

700427 Link Down Error code

700428 Max message size exceeded

700429 System not in NORM state Error code

700430 Unable to Process error code

700431 Invalid subject area

200107 Unable to Process - invalid version number 200108 Unable to Process - version not allowed

Sabre Inc. Confidential/All Rights Reserved Technical Support 26

Technical Support

4 . 1 W h o s h o u l d I c o n t a c t f o r q u e r y h e l p

Should you require any additional information about this service please send email to

[email protected] for help. When sending requests to Sabre Web Services Support Desk,

please consider the specific information contained in our support site http://myhelp.sabre.com/wbsvc/ .

In case of pressing issues you can reach the Sabre Webservices team by phone at (800) 678-9460 (USA),

(682) 605-5570 (Canada), +598 (2) 518-6020 (International)

4 . 2 F i r s t L e v e l S u p p o r t

First Level Support will be provided by the Sabre Webservices Team who will contact Application

Development On Call if required.

4

mailto:[email protected]

http://myhelp.sabre.com/wbsvc/

Sabre Inc. Confidential/All Rights Reserved Glossary 27

Glossary

Term Explanation

AAA Agent Assembly Area – refers to the buffer in the Sabre system where

content is retained while a Sabre Host session is active.

AE Air Extras – ancillary service item

Locator PNR locator

PCC Pseudo City Code uniquely identifies travel agency in the same way that a

city code identifies a city

PNR Passenger Name Record

POS Point of Sale

PSS Passenger Service System also known as Sabre Host

Segment Itinerary field of a Passenger Name Record holding actual booking (Air, Car,

Hotel etc.)

SSR Special Service Request is used when action or response from carrier is

required

EPR Employee Profile Record

5

travelitineraryreadrqrs v3 10 0...

Documents