GetReservationRQ v1.18.0 User Guide

User Guide UpdateReservationRQ

Schema Version 1.18.0

February 2018

Release 1.0

© 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.

User Guide February 2018 Table of Contents iii

Table of Contents

1 G e t t i n g S t a r t e d 1 - 1

1.1 Introduction .................................................................................................................................................... 1-1 1.2 About This Guide ........................................................................................................................................... 1-1 1.3 Customer Identification .................................................................................................................................. 1-1

2 U p d a t e R e s e r v a t i o n R e q u e s t S t r u c t u r e 2 - 1

2.1 Introduction .................................................................................................................................................... 2-1 2.2 Processing Information .................................................................................................................................. 2-1 2.3 Overview of Request and Response Updates ............................................................................................... 2-3

2.3.1 Support for new FOP type AccountCode ............................................................................................... 2-3 2.3.2 Support for Corporate ID with New Payment Card (WS) ....................................................................... 2-3 2.3.3 FCMI functionality - price validation on SellCancel ................................................................................ 2-3 2.3.4 Support for providing optional information during passive segment sell ................................................ 2-4

2.4 UpdateReservation Request Structure .......................................................................................................... 2-4 2.4.1 View Names and Subject Areas ............................................................................................................ 2-5 2.4.2 Parameters for UpdateReservation RQ ................................................................................................. 2-6

3 D o c u m e n t a t i o n U p d a t e s 3 - 1 4

3.1 Updated Design Documents ........................................................................................................................ 3-14

4 E r r o r C o d e s 4 - 1 5

4.1 Introduction .................................................................................................................................................. 4-15 4.2 Fault Errors .................................................................................................................................................. 4-15 4.3 Sample Error Response .............................................................................................................................. 4-17

4.3.1 Invalid “Locator” in RQ message ......................................................................................................... 4-17 4.3.2 Invalid “ViewName” in RQ message .................................................................................................... 4-18 4.3.3 Invalid “RequestType” in RQ message ................................................................................................ 4-18

5 T e c h n i c a l S u p p o r t – T r a v e l A g e n c i e s a n d 3 r d p a r t y d e v e l o p e r s

5 - 1 9

5.1 Introduction .................................................................................................................................................. 5-19 5.2 Phone .......................................................................................................................................................... 5-19 5.3 Email ........................................................................................................................................................... 5-19

6 T e c h n i c a l S u p p o r t – S a b r e H o s t e d A i r l i n e s 6 - 2 0

User Guide February 2018 iv Table of Contents

6.1 Introduction .................................................................................................................................................. 6-20 6.2 Phone .......................................................................................................................................................... 6-20 6.3 Email ........................................................................................................................................................... 6-22

7 G l o s s a r y 1

User Guide February 2018 Table of Contents v

• • •

User Guide February 2018 Introduction 1-1

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

UpdateReservationRQ Web Service. This release covers the XML request and responses which allow

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

UpdateReservationRS message can be returned in STL, respective details can be found in the WSDL

file.

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 for 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, “Getting Started” explains the purpose of the document, details critical information,

and provides a functional overview.

• Chapter 2, “UpdateReservation Request Structure” contains descriptions of the attributes and

elements in the response schema.

• Chapter 3, “Documentation Updates” contains the necessary filenames to run

UpdateReservationRQ.

• Chapter 4, “Error Codes” 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 C u s t o m e r I d e n t i f i c a t i o n

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.

• Third-party customers.

1 Getting Started 1

User Guide February 2018 Customer Identification 1-1

• • •



The Update Itinerary (UpdateReservationRQ) API is used to create, update and delete PNR data

including Ancillaries, Profiles, SSRs, OSIs, Remarks and Pre Reserved Seats.

This chapter includes the following:

• Processing Information (see this page).

• Request Updates (see “Overview of Request Updates,” page 2-3).

• Difference in Schema (see “Difference in Schema,” page Error! Bookmark not defined.).

• Request Structure (see “UpdateReservation Request Structure,” page 2-4).

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 in the Sabre Host, this Web Service offers capabilities allowing Airline

or Agency agents to update Logical Records (Lrec) in a particular PNR using Name and Segment

Associations. Request payload can be further specified by using “ReturnOptions” which determine

response message content.

The UpdateReservationRQ service supports two categories of requests: • Update – operates on the entire PNR Lrec e.g. Air Extra (AE), SSR

• Partial Update – operates on the Lrec part e.g AE’s action code, SSR’s action code. Partial update

enables change without necessity of deleting entire Lrec and creating it once again.

UpdateReservationRQ Web Service allows client applications to retrieve PNR in STL data format.

The PNR will be updated using one of the available request types:

Stateless: • PNR will be retrieved from PNR Reservation Database and unpacked into AAA session;

• After being updated PNR will be committed;

• It is required to provide “Locator” element;

• It is required to provide “ReceivedFrom” element

• Includes UpdateToken from GetReservationRS

Stateful: • This request type assumes that PNR is already in AAA;

• After being updated PNR will not be committed;

2 UpdateReservation Request

Structure

2

2-2 Processing Information User Guide February 2018

• It can be used to perform serial operations

OTA Air Extra (AE) Sell/Cancel functionality

• UpdateReservation will work with either Stateess or Stateful for AE Sell/Cancel functionality.

• When using RequestType = Stateless for OTA AE Cancel functionality you must include an

UpdateToken in your RQ. UpdateToken contains information about PNR version that you had

before sending update. If PSS has newer version of PNR it will return error.

<UpdateReservationRQ Version="1.18" xmlns:ns5="http://webservices.sabre.com/pnrbuilder/v1_18">

<ns5:RequestType>Stateless< /ns5:RequestType>

< /ns5:UpdateToken>4660bda5b6a998426eea20f9c49e12ca38c50e78672e9002< /ns5:UpdateToken>

< ns5:ReservationUpdateList>

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

payload, as well as how those will be formatted.

• When using pnrbuilder files on versions higher than v1.7.8 you will need to be specify the version

number in the namespace

• “isPast” this new attribute has been added to mark air segments where start date is older than 48

hours as past. For the non-air segments (e.g. Car, Rail, Hotel) the flag will be calculated based on

end date. If end date is not available and there is no possibility to calculate it based on duration

time, these will be processed as air segments.

The UpdateReservationRQ service allows users to perform the following operation types on Lrecs:

▪ insert – is used to add new Lrec;

▪ update – is used to update existing Lrec by deleting and creating it once again;

▪ delete – is used to delete existing Lrec;

The following Lrec types can be modified by UpdateReservationRQ:

Create Update Delete

Ancillary Update available not available available

Ancillary Partial Update not available available not available

SSR Update available not available available

SSR Partial Update not available available not available

Profile Update available available available

Pre Reserved Seat Partial Update not available available not available

Remark Update available not available available

If custom made updates are required please request them using

[email protected]

mailto:[email protected]

User Guide February 2018 Overview of Request and Response Updates 2-3

2.3 O v e r v i e w o f R e q u e s t a n d R e s p o n s e U p d a t e s

New schema version for v1.18 was introduced with the following main items included in the

response:

• Support for new FOP type AccountCode

• Corporate ID with New Payment Card (WS)

• FCMI functionality - price validation on SellCancel

• Support for providing optional information during passive segment sell

2.3.1 S u p p o r t f o r n e w F O P t y p e A c c o u n t C o d e

Text data will be allowed as part of the FOP when agent adds the text after the FOP type and

separated the text with an ‘/’.

2.3.2 S u p p o r t f o r C o r p o r a t e I D w i t h N e w P a y m e n t C a r d ( W S )

Added support for the PaymentCardCorporateIDAction element that allows the user to add, update, or

delete the CorporateIDNumber inside a PaymentCard element. Also added validation for the

CorporateIDNumber field when PaymentCard is created or updated via CreateReservation or

UpdateReservation call.

Functionality is available starting from 18.3 release.

2.3.3 F C M I f u n c t i o n a l i t y - p r i c e v a l i d a t i o n o n S e l l C a n c e l

The Direct Connect Platform (DCP) User Community is supposed to price automatically from the

host. If an agent decides to adjust a system priced fare, through the use of discounts, or tax overrides,

etc, the system is able to clearly identify manual intervention from the agent using FCMI (Fare

Calculation Mode Indicator) for this purpose.

For all RQs coming from UpdateReservation to SellCancel - FCMI indicators will be returned. Type

of FCMI being returned is based on price validation and recognized client type.

Clients:

• LA PCCs FCMI value 0, 1, 2

• AS - all other carriers - FCMI value always 0 (despite validation result).

Currently we do not perform price validation on AS channel, it is only present on TN

channel. FCMI functionality could be turned on AS channel, but it needs additional

configuration per client.

• TN path - FCMI value 0, 1, 2

FCMI - "Fare Calculation Mode Indicator" is returned in SellCancelRS:

2-4 UpdateReservation Request Structure User Guide February 2018

• SYSTEM (code 0) - System Priced - price is same after validation

• MANUAL (code 1) - Base Price is different (tax does not matter can be same or

different)

• MANUAL_TAX (code 2) - Taxes are different but base price is same

2.3.4 S u p p o r t f o r p r o v i d i n g o p t i o n a l i n f o r m a t i o n d u r i n g

p a s s i v e s e g m e n t s e l l

Optional information can include the airline agent’s name, agent's sign, or the record locator. As a

green screen entry, it is added with an asterisk (*) after the number of seats.

This Functionality is available starting from 18.4 release

2.4 U p d a t e R e s e r v a t i o n R e q u e s t S t r u c t u r e

The PNR data present in the response payload depends on the parameters used in the request. The

parameters can be used to reduce the number of elements returned.

Following there is a list of request parameters (RQ) which can be combined to create a request

message. Mandatory elements are marked in red.

This section contains the following:

• View Names and Subject Areas (see “View Names and Subject Areas,” page 2-5).

• Parameters (see “Parameters for UpdateReservationRQ”, page 2-6).

This section contains the following:

• Locator (see “Locator,” page 2-6).

• RequestType (see “RequestType,” page 2-6).

• ReturnOptions (see “ReturnOptions,” page 2-7).

• SubjectAreas (see “SubjectAreas,” page 2-7).

• POS (see “POS,” page 2-8).

• Source (see “Source,” page 2-8).

• RequestorID (see “RequestorID,” page 2-9).

• CompanyName (see “CompanyName,” page 2-9).

• ArrangerDetails (see “ArrangerDetails,” page 2-10).

• PersonName (see “PersonName,” page 2-10).

• Telephone (see “Telephone,” page 2-11).

User Guide February 2018 UpdateReservation Request Structure 2-5

• Email (see “Email,” page 2-11).

• BookingChannel (see “BookingChannel,” page 2-11).

• TTYRecordLocator (see “TTYRecordLocator,” page 2-12).

• OAC (see “OAC,” page 2-12).

• Poc (see “Poc,” page 2-13).

• ClientContext (see “ClientContext,” page 2-13).

2.4.1 V i e w N a m e s a n d S u b j e c t A r e a s

The PNR data which will be present in the response payload depends on the View Name used in the

request. The number of data elements returned in each View can be further narrowed by Subject Areas.

If data elements corresponding to a specified Subject Area are not present in the PNR, then those will

not be returned in the response payload. The most common View Names and Subject Areas are listed

below. Custom made Views and Subject Areas may be developed if required.

Subject Areas Description

PRIMARY SUBJECT AREAS

ACCOUNTING_LINE Agency accounting lines stored in the PNR.

ADDRESS Agency address data stored in the PNR.

AFAX All facts stored in PNR.

ANCILLARY Ancillary Items (Air Extra) stored in the PNR.

BSGPROCESSING Block Space Group data stored in the PNR.

CORPORATE_ID Agency ID for Corporate Client stored in the PNR.

CUST_INSIGHT_PROFILE Customer Profile data stored in the PNR.

DK_NUMBER Customer number stored in the PNRagencies use DK number primarily as an account reference identifier for billing purposes.

FARETYPE Fare data stored in the PNR.

FQTV Frequent Flyer details stored in PNR.

GFAX General facts stored in PNR.

HEADER PNR header data.

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

NAME Passenger Name stored in the PNR.

PASSENGERDETAILS Profile data, passenger type, email address, and other details stored in the PNR.


PHONE Phone data stored in the PNR.

PRERESERVEDSEAT Pre reserved seat data stored in the PNR.

RECEIVED Received From Field stored in the PNR.

REMARKS All Remark Fields stored in the PNR.

TICKETING Ticketing information stored in the PNR.

View Names

SIMPLE Always used, regardless of whether it is provided in the request.

Includes: HEADER (Booking and Point of Sale details).

DEFAULT It contains PNR data specified by all ACTIVE SUBJECT AREAS, and

multiple Subject Areas may be specified in the request payload.

Includes: SIMPLE; all PRIMARY SUBJECT AREAS

FULL It contains PNR data specified by all ACTIVE and HISTORY SUBJECT

AREAS, and multiple Subject Areas may be specified in the request payload.

Includes: SIMPLE; all PRIMARY SUBJECT AREAS

2.4.2 P a r a m e t e r s f o r U p d a t e R e s e r v a t i o n R Q

The following descriptions contain basic information about particular elements, though primary source

of knowledge should be corresponding XSD files.

UpdateReservationRQ/Locator

Element Description HOME

Locator Locator is used to identify a particular PNR.

Locator is optional only if RequestType is set to Stateful, in such case information is taken from current user session (AAA).

Web Service design allows to process only one Locator per request. Request containing multiple Locators will not be processed correctly.

UpdateReservationRQ/RequestType


RequestType RequestType is used to define how PNR data will be retrieved. It can be set to: Stateless, Trip, Stateful.

Stateful request mainly deals with PNRs that have not been committed; therefore Locator cannot be mandatory.



Stateless/Trip request deals with PNRs that have been committed and stored in database. This request type requires PNR Locator.

UpdateReservationRQ/ReturnOptions

Element Element Attribute Description HOME

ReturnOptions Return Options are used to define format and data range of response payload.

UnmaskCreditCard ReturnOptions contains the attribute

UnmaskCreditCard and by default the value of

the attribute is false. When a request is made

with this attribute as true the user must have

the EPR keyword 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.

SubjectAreas "SubjectAreas" specifies particular information to be included in response message if they are stored in the PNR.

ViewName The PNR data present in the response payload depends on the specified View Name used in the request (see “View Names and Subject Areas,” page Error! Bookmark not defined.).

Number of data elements returned in each View can be further narrowed using the optional values of RetrievePNR = true/false or

IncludeUpdateDetails = true/false.

ResponseFormat ResponseFormat enables to define how

response payload will be formatted and value

should be STL.

UpdateReservationRQ/ReturnOptions/SubjectAreas

Element Element Description HOME

SubjectAreas SubjectArea "SubjectAreas" specifies particular information to be

included in response message if they are stored in the

PNR (see “View Names and Subject Areas,” page

Error! Bookmark not defined.).

UpdateReservationRQ/POS



POS Source Source holds details regarding the requestor. It may

be repeated to also accommodate the delivery

system.

UpdateReservationRQ/POS/Source

Element Attribute Element Description HOME

Source This holds details regarding the requestor. It may be repeated to also accommodate the delivery systems.

BookingSource Identifies the booking source within the requesting entity.

AgentSine Identifies the party within the requesting entity.

PseudoCityCode An identification code assigned to an office agency by a reservation system.

ISOCountry The country code of the requesting party.

ISOCurrency The currency of the country of the requesting party.

AgentDutyCode An authority code assigned to a

requestor.

AirlineVendorID The IATA assigned airline code.

AirportCode The IATA assigned airport code.

FirstDepartPoint The point of first departure in a trip.

SourceSystem e.g., CSS or CSI

TerminalID The electronic address of the device from

which information is entered.

HomePseudoCityCode An identification code assigned to the office/agency home city by a reservation system.

RequestorID An identifier of the entity making the request e.g., ATA/IATA/ID number, Electronic Reservation Service Provider (ERSP), Association of British Travel

Agents (ABTA).

BookingChannel Specifies the booking channel type and whether it is the primary means of connectivity of the source.

TTYRecordLocator Received via TeleType, the Locator is used to identify a particular PNR.

OAC The Office Account Code defines the agency PCC extension.


UpdateReservationRQ/POS/Source/RequestorID

Element Attribute Element Description

RequestorID An identifier of the entity making the request (e.g. ATA/IATA/ID number, Electronic Reservation Service Provider (ERSP),

Association of British Travel Agents (ABTA)).

URL URL that identifies the location associated with the record identified by the UniqueID.

Type A reference to the type of object defined by the UniqueID element. Refer to OTA Code

List Unique ID Type (UIT).

Instance The identification of a record as it exists at a point in time. An instance is used in update messages where the sender must assure the server that the update sent refers to the most recent modification level of the object being updated.

ID A unique identifying value assigned by the creating system. The ID attribute may be used to reference a primary-key value within a database or in a particular implementation.

ID_Context Used to identify the source of the identifier (e.g., IATA, ABTA).

MessagePassword This password provides an additional level of security that the recipient can use to validate the sending party's authority to use the message.

CompanyName Identifies the company that is associated with the UniqueID.

ArrangerDetails Contact information for the person that makes the arrangements of the PNR.

UpdateReservationRQ/POS/Source/RequestorID/CompanyName

UpdateReservationRQ/POS/Source/BookingChannel/CompanyName

Element Attribute Description HOME

CompanyName Identifies the company that is associated with the

UniqueID.

CompanyShortName Used to provide the company common name.

TravelSector Refers to OTA Code List Travel Sector (TVS).

Code Identifies a company by the company code.


Element Attribute Description HOME

CodeContext Identifies the context of the identifying code, such as

DUNS, IATA or internal code.

Division The division name or ID with which the contact is

associated.

Department The department name or ID with which the contact is

associated.

UpdateReservationRQ/POS/Source/RequestorID/ArrangerDetails


ArrangerDetails Used to identify the details of the requestor.

PersonName Used to identify the contact name details of the

requestor.

Telephone Used to identify the telephone number details of the

requestor.

Email Used to identify the email address details of the

requestor.

UpdateReservationRQ/POS/Source/RequestorID/ArrangerDetails/PersonName


PersonName Used to identify the contact name details of the requestor.

Prefix A salutation of honorific e.g., Mr., Mrs., Ms., Miss., Dr.

Given The given name, first name or names.

Middle The middle name of the person name.

Surname The family name also known as last name

Suffix Holds various name suffixes and letters e.g., Jr., Sr., III., Ret., Esq.

Type Values include ADT or INF

PreferredFirstName Any preferred name for first name used instead of the Given Name.

PreferredSurname Any preferred names for last name used instead of Surname.


UpdateReservationRQ/POS/Source/RequestorID/ArrangerDetails/Telephone


Telephone Used to identify the telephone details of the

requestor.

PhoneUseType Describes the type of telephone number, in the

context of its general use (e.g. Home, Business,

Emergency Contact, Travel Arranger, Day, Evening).

Refer to OpenTravel Code List

Phone Use Type (PUT).

PhoneCountryCode Describes the Country Code for the telephone

number of the requestor.

PhoneCountryName Describes the Country Name for the telephone


PhoneNumber Telephone number assigned to a single location.

UpdateReservationRQ/POS/Source/RequestorID/ArrangerDetails/Email


Email Address of arranger, e.g. [email protected]

UpdateReservationRQ/POS/Source/BookingChannel

Element Attribute Element Description

HOME

Booking Channel

Specifies the booking channel type and whether it

is the primary means of connectivity of the source.

Type The type of booking channel (e.g. Global

Distribution System (GDS), Alternative Distribution

System (ADS), Sales and Catering System (SCS),

Property Management System (PMS), Central

Reservation System (CRS), Tour Operator

System (TOS), Internet and ALL). Refer to OTA

Code List Booking Channel Type

(BCT).

Primary Indicates whether the enumerated booking

channel is the primary means of connectivity used

by the source.


CompanyName Identifies the company that is associated with the

booking channel.

UpdateReservationRQ/POS/Source/TTYRecordLocator


TTYRecordLocator Received via TeleType, the Locator is used to identify

a particular PNR.

CRSLocator If the PNR was received from OAL (from CRS or

OAL), the Record Locator of the PNR in the creating

system. Occurs only for TTY created PNRs. Value

for this optional field can be populated if available.

This optional field is used for information and display

purposes only.

CRSCode Airline Code of the RES System or CRS system that

created this PNR. This optional field is not used in

any processing. This optional field is used for

information and display purposes only.

RecordLocator Used to identify a particular PNR.

AgencyId The booking source arranger.

IataNumber The booking source location IATA number.

AgencyLocation The booking source agent location.

UserType Includes the values of A-Airline, E-ERSP, N-no user

ID assigned by IATA, T-user ID assigned by IATYA

other than ERSP.

CountryCode Describes the Country Code for the telephone


Currency The currency of the country of the requesting party.

DutyCode Duty code of the agent that issued a

ticket/refund/exchange /void.

ERSPUserId The Electronic Reservation Service Provider number.

FirstPointOfDeparture The first point of departure for the booking.

UpdateReservationRQ/POS/Source/OAC


OAC Office Account Code. Defines agency PCC extension.

PartitionId Default partition code from the OAC data



AccountingCityCode The personal account city code associated with the user AAA city during the original PNR create session.

AccountingCode The personal account code associated with

the user AAA city during the original PNR

create session.

AccountingOfficeStationCode The station code from the OAC line used in this PNR Create Session

UpdateReservationRQ/Poc


Poc Point of Commencement is the first point of departure amongst all of segments present in the PNR.

• Poc can be used to explicitly specify journey's

Point of Commencement in case itinerary contains

other segments than air segments as well.

• Provided values will be present in the RS payload

in case they are earlier than those defined by the

first air segment.

Airport Airport name.

Departure Date and Time of departure.

UpdateReservationRQ/ClientContext


ClientContext Will need to provide ClientContext when calling the downline services: Web Check In; Web RES; Interact Check In; Interact RES; Kiosk Check In; TTY; PRS; GSM; SSCI

If context is set in GetReservation request - master PNR is retrieved

Name Allows users to provide information about the caller to the service.

This parameter is currently only available with customization.

3-14 Updated Design Documents User Guide February 2018

Sabre Web Services are currently available on the Sabre Dev Studio site https://developer.sabre.com.

UpdateReservationRQ will be stored in the Trip Management folder as Update Itinerary.

Common schema files listed below are available on the Sabre Dev Studio site

https://developer.sabre.com/docs/read/soap_basics/development_patterns

3.1 U p d a t e d D e s i g n D o c u m e n t s

WSDL UpdateReservation_1.18.0.wsdl

Schema UpdateReservationSTLRQ_v1.18.0.xsd

UpdateReservationSTLRS_v1.18.0.xsd

Common

Schemas

envelope.xsd;

msg-header-2_0.xsd;

wsse.xsd;

xlink.xsd;

xml.xsd;

xmldsig-core-schema.xsd;

Control

Schemas

PNRBuilderTypes_v1.18.0.xsd;

OpenReservation.1.12.0.xsd

Ancillaries.1.12.0.xsd

Pricing.1.12.0

Air.1.12.0.xsd

Payload Design

Documents

Additional

Documentation UpdateReservationRQ_1.18.0_User Guide.pdf

Sample XML

Payloads UpdateReservationRQRS_1.18.0_SamplePayload.xml;

3 Documentation Updates 3

https://developer.sabre.com/docs/read/soap_basics/development_patterns



This chapter contains the list of most common error codes and descriptions.

This chapter contains the following:

• Fault Errors (see this page.)

• Sample Error Response (see “Sample Error Response”, page 4-4).

4.2 F a u l t E r r o r s

Message OTA Code

General PNR error 700001

Invalid PNR locator 700002

Invalid request 700003

Invalid request format 700004

Invalid request view 700005

No PNR was found with the specified record locator 700101

Viewership is restricted for the PNR 700102

No data for the PNR in DB 700103

Error parsing PNR 700104

PNR Connector unknown 700201

PNR Connector communication error 700202

PNR Connector communication timeout error 700203

JAXB marshalling error 700204

JAXB unmarshalling error 700205

Unexpected request type 700206

MOM messaging error 700207

PNRC service invocation error 700208

4 Error Codes 4

4-16 Fault Errors User Guide February 2018

Message OTA Code

Error response from PNRC reaccomodation search service 700209

Unknown response format 700210

OTA parsing error 700211

Cannot unpack request from request root element 700212

Cannot pack response to response root element 700213

Error response from PNRC reaccomodation retrieve service 700214

TPFDF parsing exception 700215

No ATH 700216

Invalid ICE Session 700217

Broken ICE Session 700218

FIT parsing exception 700219

Invalid ICE credentials 700220

Access restricted to flight data 700221

Cannot search past flight data 700222

Access restricted to PNR data 700223

Flight not found 700224

Invalid search options 700225

PNR not found 700226

TVL version not supported 700227

PNR unknown error 700301

PNR communication error 700302

PNR communication timeout error 700303

Unable to read terminal 700404

Unable to Find AAA 700405

Agent not signed in 700406

PNR Locator error 700407

No PNR in AAA 700408

PNR Retrieval error 700409

PSS invalid request 700410

The PNR in the AAA has been modified 700411

Agent is active on a PNR queue 700412

Unable to process in PSS 700414

User Guide February 2018 Sample Error Response 4-17

Message OTA Code

Parsing error 700415

Access restricted to flight data 700418


PSS Communication error 700420

PSS Communication timeout 700421


PNR Restricted 700423

PNR Not Found 700424

PNRC Timeout Error code 700425

PNR Database unavailable 700426

Link Down Error code 700427

Max message size exceeded 700428

System not in NORM state Error code 700429

Unable to Process error code 700430

Invalid subject area 700431

Reservation Orchestration Error 700432

4.3 S a m p l e E r r o r R e s p o n s e

4.3.1 I n v a l i d “ L o c a t o r ” i n R Q m e s s a g e

<ns3:GetReservationRS xmlns:ns3="http://webservices.sabre.com/pnrbuilder"

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

xmlns="http://webservices.sabre.com/triprecord"

xmlns:ns4="http://webservices.sabre.com/sabreXML/2003/07"

xmlns:ns5="http://tds.sabre.com/rules" xmlns:ns6="http://tds.sabre.com/itinerary">

<ns3:Errors>

<ns3:Error>

<ns3:Code>700226</ns3:Code>

<ns3:Message>PNR not found, caused by [PNR not found, code: 100123,

severity: MODERATE]</ns3:Message>

<ns3:Severity>MODERATE</ns3:Severity>

</ns3:Error>

4-18 Sample Error Response User Guide February 2018

</ns3:Errors>

</ns3:GetReservationRS>

4.3.2 I n v a l i d “ V i e w N a m e ” i n R Q m e s s a g e






<ns3:Errors>

<ns3:Error>


<ns3:Message>Invalid request view</ns3:Message>


</ns3:Error>

</ns3:Errors>


4.3.3 I n v a l i d “ R e q u e s t T y p e ” i n R Q m e s s a g e






<ns3:Errors>

<ns3:Error>


<ns3:Message>Invalid request</ns3:Message>


</ns3:Error>

</ns3:Errors>




If you have any questions or need assistance, contact our Sabre Dev Studio Global Customer Support

Center via any of the methods provided in this chapter.

5.2 P h o n e

When reporting production or other critical/time sensitive issues, contact us via telephone as follows:

Location Phone Number

USA 800-678-9460

Canada 682-605-5570

International 598-2-518-6020 or your regional Sabre Software help desk

5.3 E m a i l

Email is monitored 24 x 7 with a response within 24 hours or less. The email address is:

[email protected]

Caution Please include the Sabre Pseudo City Code (PCC) where the issue is occurring.

When reporting an issue with web services, input and output payloads are required. Please attach the

payloads as separate files, and name them clearly. Samples of these files are available at:

https://developer.sabre.com

To help ensure that our environment is free of viruses, our policy mandates that all messages received

by Sabre from external sources follow special file name guidelines. When sending zipped files please

make a note of the following required file naming convention: File names must end in ".sabre.zip" or

the zipped attachment will be removed by the email server (for example, “docs.zip” would need to be

renamed to “docs.sabre.zip”).

If your correspondence is regarding a previously reported issue, please include the service incident

(“SI”) number in the subject line of your message.

5 Technical Support – Travel Agencies

and 3rd

party developers

5


https://developer.sabre.com/

6-20 Introduction User Guide February 2018


If you have any questions or need assistance, contact our SabreSonic Helpdesk via any of the

methods provided in this chapter.

6.2 P h o n e

When reporting production or other critical/time sensitive issues, contact us via telephone as follows:

Dial Option #1 for SabreSonic Select Web Services option

Country Toll free number

Antigua 888-832-4738

Argentina 0800-666-1664

Australia 1-800-081-993

Austria 800-291-705

Bahamas 1-800-389-0417

Bahrain 800-00-002 (WSC 5050)

Belarus 880-0114 PIN 375

Belgium 0800-77-029

Bolivia 800-10-0350

Brazil 0800-891-9210

Brunei 800-013 PIN 673

Canada 1-866-598-1706

Chile 800-412555

China 4001-202-315

Colombia 01-800-954-1326

Cyprus 800-96110

Czech Republic 800-700-117

Denmark 808-85884

6 Technical Support – Sabre Hosted

Airlines

6

User Guide February 2018 Phone 6-21

Egypt - Cairo 7955-770 PIN 5670

El Salvador 800-0000-0011

Estonia 800-12-122 PIN 5047

Finland 0800-914-860

France 0800-909-657

Germany 0800-181-7245

Greece 00800-16-122-055-533

Hong Kong 800-908-742

Iceland 800-8667

India 000-800-100-6116

Indonesia 001-803-016-1722

Ireland 1-800-657-198

Israel 1-809-246-033

Italy 800-787-417

Jamaica 1-866-402-6835

Japan 0053-116-0811

Korea 0030-813-1943

Malaysia 1-800-813-609

Malta 800-90112 PIN 356

Mexico 01-800-123-8537

Netherlands 0800-023-2237

New Zealand 0800-450-960

Norway 800-18-798

Panama 00800-226-0662

Paraguay 009-800-598-1-0004

Peru 0800-52-226

Philippines 1-800-111-00338 or 1-800-111-00339

Poland 800-900-807

Russia 810-800-240-31012

Saudi Arabia 1-800-11 PIN 5671

Singapore 800-101-1651

6-22 Email User Guide February 2018

South Africa 0800-980-981

Spain 900-995-926

Sweden 0200-285-836

Switzerland 0800-894-354

Tahiti 888-832-4738

Thailand 1. Dial 001-999-111-11 (AT&T)

2. Wait for the recording asking for the

number you are dialing.

3. Dial 888-832-4738.

Trinidad and Tobago 888-870-9002

UAE 800-035-702-569

UK 0800-0288446

Uruguay 2518-6642

USA 1-888-421-8889

Venezuela 0800-100-3851

Vietnam 1. Dial 1-201-0288 (AT&T Toll Free

Number).

2. Wait for the recording asking for the

number you are dialing.

3. Dial 866-947-8059.

6.3 E m a i l

Email is monitored 24 x 7 with a response within 24 hours or less. The email address is:

[email protected]

Caution Please include the Sabre Pseudo City Code (PCC) where the issue is occurring.

When reporting an issue with web services, input and output payloads are required. Please attach the

payloads as separate files, and name them clearly. Samples of these files are available at:

https://developer.sabre.com

To help ensure that our environment is free of viruses, our policy mandates that all messages received

by Sabre from external sources follow special file name guidelines. When sending zipped files please

make a note of the following required file naming convention: File names must end in ".sabre.zip" or

the zipped attachment will be removed by the email server (for example, “docs.zip” would need to be

renamed to “docs.sabre.zip”).

If your correspondence is regarding a previously reported issue, please include the service incident

(“SI”) number in the subject line of your message.


https://developer.sabre.com/

User Guide February 2018 Glossary 1

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

Term Description

AAA Agent Assembly Area - refers to the buffer in the Sabre system where content is

retained while a Sabre Host session is active

AS Sabre Airline Solutions

FOID Form Of Identification - is used to advise carrier what identification the passenger will present upon check-in for e-ticket travel

GDS Code for the Global Distribution System. For example:

1S – Sabre

1B – Abacus

1J – Axess

1F – Infini

Locator PNR locator

OAC Office Accounting Code

OSI Other Supplementary Information - can be used when action or reply from carrier is not required

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

SAN Sabre Advance Notification

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

Hotel etc.)

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

STL Sabre XML format

TN Sabre Travel Network

7 Glossary

2 Glossary User Guide February 2018

• • •