AS User Guide Template - Sabrefiles.developer.sabre.com/doc/providerdoc/Ticketing/cert-Ticketing... · Name of Product Introduction 20 November 2017 5 Confidential and Proprietary

I

Document Edition 1.1

July 28, 2017

User Guide TicketingProfile Webservices

Document Revision Information

Date Revised by Reason for Revision Revision

Control No.

15 March 2017 Stephanie Bidun Initial create V1.0

28th July 2017 Sujat Jain New operations GetAgencyProfile and UpdateAgencyProfile is added.

Merged the StationProfile user guide with the two new opeartions to call it TicketingProfile User Guide

V1.1

Document Edition 1.0

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.

© 2016 Sabre Inc. All rights reserved. 02_2016

Name of Product Introduction

20 November 2017 2 Confidential and Proprietary Sabre Airline Solutions

Table of Contents

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

1.1 Overview................................................................................................................................................. 4 1.2 Purpose of this Guide ............................................................................................................................. 4 1.3 Sabre Dev Studio ................................................................................................................................... 4 1.4 Ticketing Profile Service WSDL file ........................................................................................................ 5 1.5 Getting Started Guide ............................................................................................................................. 5

2 U n d e r s t a n d i n g G e t P r o f i l e S e r v i c e

3 G e t S t a t i o n P r o f i l e

3.1 Security Validation .................................................................................................................................. 7 3.2 GetStationProfileRQ ............................................................................................................................... 7

3.2.1 GetStationProfileRQ Attributes ................................................................................................. 8 3.2.2 GetStationProfileRQ Elements ................................................................................................. 9

3.2.2.1 Header Attributes ........................................................................................................ 9 3.2.2.2 Point Of Sale attributes ............................................................................................. 11 3.2.2.3 Search Paramaters ................................................................................................... 13

3.3 GetStationProfileRS ............................................................................................................................. 13 3.3.1 GetStationProfileRS Attributes ............................................................................................... 14

3.3.1.1 Header ...................................................................................................................... 15 3.3.1.2 Results ...................................................................................................................... 16

3.3.2 GetStationProfileRS Elements ............................................................................................... 17 3.3.2.1 StationInfo ................................................................................................................. 17 3.3.2.2 Station elements ....................................................................................................... 18 3.3.2.3 Office Account Code elements .................................................................................. 20 3.3.2.4 Ticketing Options ...................................................................................................... 21 3.3.2.5 DailyAuto Close ......................................................................................................... 22 3.3.2.6 Currency .................................................................................................................... 23 3.3.2.7 Fraud and Payment Options ..................................................................................... 24

3.4 Example Web Service XML .................................................................................................................. 24 3.4.1 Station Profile ......................................................................................................................... 24

3.5 Troubleshooting Station Profile ............................................................................................................. 28 3.5.1 Get Station Common Error Responses, Reasons and Solution ............................................. 28

3.5.1.1 Station corruption ...................................................................................................... 28 3.5.1.2 Security validation error............................................................................................. 29

4 G e t A g e n c y P r o f i l e a n d U p d a t e A g e n c y P r o f i l e S e r v i c e



4.1 Understanding GetAgency and UpdateAgency profile WS ................................................................... 31 4.1.1 Introduction ............................................................................................................................ 31 4.1.2 Prerequisites for Ticketing Profile Web Service ..................................................................... 31 4.1.3 XML Examples in this Document ........................................................................................... 31 4.1.4 Access Conditions .................................................................................................................. 31 4.1.5 Authentication with USG ........................................................................................................ 32 4.1.6 Ticketing Profile Web Service WSDL file ............................................................................... 32 4.1.7 End Points .............................................................................................................................. 32

4.2 GetAgencyProfileRQ ............................................................................................................................ 33 4.2.1 Request Attributes .................................................................................................................. 33 4.2.2 Request Elements .................................................................................................................. 34 4.2.3 Selected Request Elements ................................................................................................... 34

4.2.3.1 Search Parameters ................................................................................................... 34 4.2.3.1.1 Search Parameters Request Attributes ........................................................ 34 4.2.3.1.2 Search Parameters Request Elements ........................................................ 35

4.2.4 Response Elements ............................................................................................................... 35 4.2.5 Response Attributes ............................................................................................................... 37

4.3 UpdateAgencyProfileRQ....................................................................................................................... 38 4.3.1 Request Attributes .................................................................................................................. 38 4.3.2 Request Elements .................................................................................................................. 38 4.3.3 Selected Request Elements and attributes ............................................................................ 39

4.3.3.1 CreditLimitOptions ..................................................................................................... 39 4.3.3.2 Agency Options ......................................................................................................... 39

4.3.3.2.1 Agency Options element/attributes ............................................................... 39 4.4 Ticketing Profile Web Service XML examples ...................................................................................... 40

4.4.1 GetAgencyProfileRQ Sample request and response XML ..................................................... 40 4.4.1.1 Detail Result Type Search ......................................................................................... 40 4.4.1.2 Custom Result Type Search Parameters – Airline Profile ......................................... 43 4.4.1.3 Custom Result Type Search Parameters – Agency Number search ......................... 45 4.4.1.4 Custom Result Type Search Parameters – Agency Number search ......................... 47 4.4.1.5 Custom Result Type Search Parameters – Agency Number and Airline profile ........ 50 4.4.1.6 History Details for Airline and Agency Profile ............................................................ 52 4.4.1.7 History details of an Agency ...................................................................................... 59

4.4.2 UpdateAgencyProfile Sample request and response XML .................................................... 66 4.4.2.1 UpdateAgencyProfile action to set Airline Profile ...................................................... 66 4.4.2.2 UpdateAgencyProfile action to set Airline Profile ...................................................... 68

4.5 TroubleShooting GetAgencyProfile and UpdateAgencyProfile ............................................................. 70 4.5.1 Overview ................................................................................................................................ 70 4.5.2 Error Messages by Category .................................................................................................. 70

4.5.2.1 WS Validations .......................................................................................................... 70 4.5.2.2 Database(DMS) Validations ...................................................................................... 71



1 Introduction

1.1 Overview

TicketingProfileServices currently offers 4 functions:

- Display station table information (GetStationProfileRQ) – Available for airline

- Change fee collection method (GetProviderProfileRQ) – Available for Travel Agent

(Subscriber)

- Display Airline and Agency Profile (GetAgencyProfileRQ) – Available for airline

- Update Airline and Agency Profile (UpdateAgencyProfileRQ) – Available for airline

1.2 Purpose of this Guide

The purpose of this guide is to introduce how the Ticketing Profile web service processes different

operations’ RQ/RS. It is not intended to be a complete reference tool for XML design. Developers

should refer to Sabre Dev Studio for the most complete information. You can find instructions on

how to access Sabre Dev Studio later in this document.

Important Note About Web Services in this Guide

Always refer to Sabre Dev Studio for the latest version and examples of any of these web services.

In addition, the process used to complete each transaction may not be the method your airline wishes

to use. Consult with your Sabre contacts when designing your web service.

1.3 Sabre Dev Studio

Sabre Dev Studio 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.

Sabre Dev Studio is located at the following web address: https://developer.sabre.com/

If you do not have access to this web site contact your airline’s Sabre Account Director.

Make sure you are using an updated version of Internet Explorer or Google Chrome to be able to

download all resources available.

Dev Studio resources link: TicketingProfileWS resources

https://developer.sabre.com/

https://developer.sabre.com/docs/read/sabre_sonic_apis/soap/ticketing/station_profile/resources



1.4 Ticketing Profile Service WSDL file

The WSDL file provides a description of the basic formats of Web Service requests – how the service can be called, what parameters it expects, and what data structures it returns.

For the latest available links to WSDL files, check the Tciketing Profile Service documentation at Sabre Dev Studio. WSDL

1.5 Getting Started Guide

For information on how to connect and create a session, please register at Sabre Dev Studio and see the documentation at the following link: Getting Started


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

Name of Product Understanding GetProfileService


2 Understanding GetProfileService

This web service provides standalone Request(RQ)/Response(RS) messaging allowing a client to request the TicketingProfile WS. The report utilizes a RQ/RS in order to clearly differentiate what selection criteria (filter) is available for the data returned.

The schemas which define the messaging in this web service consist of three schemas:

1. TicketProfileServices is the core schema which defines all the GetProfileService RQ/RS messages. This schema imports two additional schemas which define common elements used by many of the RQ/RS messages.

2. SabreTypeLibrary.xsd which defines common elements used by many Sabre systems

3. TicketingTypeLibrary.xsd which defines common elements used by Sabre Ticketing systems.

Points to remember regarding GetProfileService RQ/RS service:

Only returns raw data. The client is responsible for all presentation.

Order is not guaranteed except when paging data in multiple requests. The client is responsible for sorting of the data.

Is not providing controls for the maximum number of records returned. The client must be able to consume large sets of data in the RS.

There is no state between messages which means there is no set sequence in which messages must flow. Each RQ/RS pair is considered standalone.

Overall usage of the RQ/RS is described below. For descriptions of individual elements refer to the XML schemas which define each element.

The purpose of this chapter is to briefly explain the content of the Ticketing Profile XML. The subsections of this chapter will provide detailed information about different operations of the service.

Name of Product GetStationProfile


3 GetStationProfile

The Station Profile displays the list of ticketing locations or stations for an airline. The table contains

the unique station number and the foundational ticketing abilities for each location.

3.1 Security Validation

The security attribute required for access to the Station Profile service is TktStationProfileUser.

Security validation is performed to verify whether a user requesting the report is authorized to access it. It protects the data from viewing by unauthorized parties.

When an airline requests a station profile, the system will validate if access is allowed. If validation fails, an error message will be returned to the user and the request will fail.

3.2 GetStationProfileRQ

The Station Profile available search parameters include:

Station Number

City

If a station number or city is not used in the search criteria all ticketing locations will display.

The requesting client can specify one or more filters by filling in the optional elements and attributes under the <SelectionCriteria> element. The Boolean filters are defined as attributes to <SelectionCriteria> while the more complex filter elements are defined as child elements. A description of each element (required/optional including annotations) is included in the annotated XML schema. Only those documents matching the selection criteria will be returned in the GetProfileService RQ.

The following pages display expanded view of the GetProfileService RQ with a description of the associated attributes and elements.



3.2.1 GetStationProfileRQ Attributes

Attribute Description

version Required in the XML schema.

Header Header information indicating result of the service call, errors and warnings.

POS Point of Sale information that is copied from the request upon successful response

SearchParamaters Elements required to request data

Diagnostic Diagnostic information



3.2.2 GetStationProfileRQ Elements

3.2.2.1 Header Attributes


Header Header information indicating result of the service call, errors and warnings.

messageID Optional. The MessageId element is a globally unique identifier for each message [see RFC2822]. It is a unique message identifier that refers to a particular version of a particular message. The uniqueness of the message identifier should be guaranteed by the host that generates it. This message identifier is intended to be machine readable and not necessarily meaningful to humans. A message identifier pertains to exactly one instantiation of a



particular message; subsequent revisions to the message each receive new message identifiers.

Length: 1-255 characters

version Optional. Should match the version of the schema.

Length: 1-255 characters

timeStamp Optional. Date and Time when the result record was created

customerID Not used by Station Profile WS

diagnosticLevel Not used by Station Profile WS

ttl Not used by Station Profile WS



Elements Description

ConversationId Not used by Station Profile WS

OrchestrationID The OrchestrationID may be used to track a set of service invocations and the sequence in which they are invoked. To track an orchestration, the orchestrator assigns a unique value to the identifier and sets the sequence number to 0. Service providers are expected to increment the OrchestrationID@seq value if it exists.

Operation Not used by Station Profile WS

Service Not used by Station Profile WS

Messaging Not used by Station Profile WS

Parameters Not used by Station Profile WS

Security Not used by Station Profile WS

DiagnosticData Not used by Station Profile WS

3.2.2.2 Point Of Sale attributes

Point of Sale and Agent information.



Element Description

Company Not used by Station Profile WS

Pseudo Not used by Station Profile WS

MultiHost 2 character Airline code

Actual Not used by Station Profile WS

Home Not used by Station Profile WS

Sine Not used by Station Profile WS

DutyCode Not used by Station Profile WS

Lniata Not used by Station Profile WS



3.2.2.3 Search Paramaters

Elements of SearchParameters - Used to define what should be included in the Station Profile Request including optional filters.

Element Description

StationNumber At least 1 number and up to nine digits for the station number (7-digit station plus check digit). 9th character is for future enhancement

City Office designator or station code for the ticketing location. It consists of the 3-letter city code plus 2-letter office code. Must enter 3 or 5.

3.3 GetStationProfileRS

The GetStationProfileRS will return the matching requested data in the following elements.



3.3.1 GetStationProfileRS Attributes


Version Web Service Version client is using.

Stations Number of returned stations

Header Header information indicating result of the service call, orchestration and transaction identifiers, errors and warnings

POS Point of Sale information that is copied from the request upon successful response



3.3.1.1 Header


ConversationId Not used by Station Profile WS

OrchestrationID The OrchestrationID may be used to track a set of service invocations and the sequence in which they are invoked. To track an orchestration, the orchestrator assigns a unique value to the identifier and sets the sequence number to 0. Service providers are expected to increment the OrchestrationID@seq value if it exists.

Operation Not used by Station Profile WS

Service Not used by Station Profile WS

Messaging Not used by Station Profile WS

Parameters Not used by Station Profile WS

Security Not used by Station Profile WS

DiagnosticData Not used by Station Profile WS



3.3.1.2 Results

Results are used to exchange information about the nature of a failure or success. This record must be

provided in successful service responses. It may also contain system specific error, result and

diagnostic data.


Success Success is an empty element with no children which indicates that the request was processed successfully

Error Error will be populated when the entire response fails. Details will be provided in the element and child elements as to the source or system of the error reporting. This section will contain error codes, text, elements or records if applicable.

Warning Warning will be populated when there is a partial failure in the response. Details will be provided in the element and child elements as to the source or system of the error reporting. This section will contain error codes, text, elements or records if applicable.



3.3.2 GetStationProfileRS Elements

3.3.2.1 StationInfo

Element Description

StationInfo

Station Station Details

OfficeAccountingCode Office Account Code Details

TicketingOptions Ticketing Options

FraudOptions Fraud Provider Options

PaymentOptions Payment Options



3.3.2.2 Station elements



Element Description

Station Station elements included in response.

Number Seven-digit station number plus the check digit.

Code Office designator or station code for the ticketing location. It consists of the 3-letter city code plus 2-letter office code.

Channel Channel or OAC type:

ATO Airport Ticket Office

CTO City Ticket Office

TBM Tickets By Mail

GSA General Sales Agent

WEB Website

IVR Interactive Voice Recognition

RES Reservation

Name Optional – to further identify stations airlines can add a station name. If defined it will appear in this field.



3.3.2.3 Office Account Code elements

Element Description

OfficeAccountingCode Will have information if the airline activated Office Account Code

(OAC) in their partition

City Office designator or station code for the ticketing location. It consists

of the 3-letter city code plus 2-letter office code.

validatingProvider 2 letter airline code – Validating Carrier Default

accountingCode Accounting Code (office account code) 1- 15

officeid Office ID 1 -10 characters – first 7 characters of station number

viewershipRestricted Access to OACs in specific administrative PCCs are restricted



3.3.2.4 Ticketing Options

Element Description

TicketingOptions

ticketingAllowed Tickets or documents are generated through the Sabre system.

Same as TKT in WJ* display.

neutralTicketing Allows the Sabre system to assign and print ticket numbers at the time of issuance.

Same as NTKT in WJ* display.

commisionProtectTicketing No longer available in the Sabre system. Commission Protected Ticketing is different from Commission Ticketing which Sabre supports today.

Same as CPT in WJ* display.

ATAC_active Automated Ticket Agent Check-Out (ATAC)

Same as ATAC in WJ* display.

Not applicable to Agent Sales Report users



3.3.2.5 DailyAuto Close

Element Description

SalesReport

active Indicates if ASR is active

DailyAutoClose

Type Daily Auto Close station type.

Possible values are: WEB, KSK, RCC and DAC

DAC Daily Auto Close

KSK Kiosk Station

RCC Reservation Call Center

WEB Web Station

Active Advises if Daily Auto Close is active for stations.

hourTime Defines the Auto close time for the Station.

Values from 0000 to 2400.

nextDay Auto Close takes place on Next Day:

If true, Daily Auto Close takes place Next Day at the time you specified.

If false, Daily Auto Close takes place today at the time you specified.



3.3.2.6 Currency

Element Description

CurrencyInfo

CurrencyAllowed Displays a list of allowable currencies

Currency 3 character currency code

CurrencyNotAllowed Currencies listed here are restricted from use

Currency 3 character currency code



3.3.2.7 Fraud and Payment Options

Element Description

FraudOptions

FraudProvider Two-letter code for the Fraud Provider used to screen credit card sales. If there is no provider selected, this field indicates NONE.

PaymentOptions

acceleratedCreditCardBilling ACCB is a process that allows credit card charges to be billed directly to the client’s bank.

electronicCommerceIndicator The Electronic Commerce Indicator is not used at this time.

3.4 Example Web Service XML

3.4.1 Station Profile

Example RQ/RS with a single station included in RQ. RQ



<?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:PartyId>123123</ns1:PartyId> </ns1:To> <ns1:CPAId>IPCC</ns1:CPAId> <ns1:ConversationId>SYSTEM-T2DAILY-SYSTEM</ns1:ConversationId> <ns1:Action>GetTicketingProfileRQ</ns1:Action> <ns1:MessageData> <ns1:MessageId>1000</ns1:MessageId> <ns1:Timestamp>2001-02-15T11:15:12Z</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!-3298008765470601343!1233536!0</ns1:BinarySecurityToken> </ns1:Security> </SOAP-ENV:Header> <SOAP-ENV:Body> <GetStationProfileRQ

Version="1.0.0" xmlns="http://www.sabre.com/ns/Ticketing/Profiles"> <Header/> <POS/> <SearchParameters> <StationNumber>24485705</StationNumber> </SearchParameters> </GetStationProfileRQ> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

RS


xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <GetStationProfileRS

http://schemas.xmlsoap.org/soap/envelope/

http://www.w3.org/2001/XMLSchema

http://www.w3.org/2001/XMLSchema-instance

http://www.ebxml.org/namespaces/messageHeader

http://schemas.xmlsoap.org/ws/2002/12/secext

http://www.sabre.com/ns/Ticketing/Profiles




Stations="1" Version="1.0.0"

xmlns="http://www.sabre.com/ns/Ticketing/Profiles" xmlns:ns2="http://services.sabre.com/STL/v01" xmlns:ns3="http://www.sabre.com/ns/Ticketing/TTL/1.0" xmlns:ns4="http://services.sabre.com/STL/Catalog/v01" xmlns:ns5="http://schemas.xmlsoap.org/soap/envelope/"> <Header messageID="ds-station-profile-15"> <ns2:Results> <ns2:Success> <ns2:System>T2-DS</ns2:System> </ns2:Success> </ns2:Results> </Header> <POS> <ns2:MultiHost>AA</ns2:MultiHost> </POS> <StationInfo> <Station channel="ATO" code="ACCGA" number="24485705"/> <OfficeAccountingCode accountingCode="GA" city="ACC" officeId="2448570" validatingProvider="AA" viewershipRestricted="false"/> <TicketingOptions ATAC_active="false" commisionProtectTicketing="false" neutralTicketing="true" ticketingAllowed="true"> <SalesReport active="true"/> <CurrencyInfo allowed="ONLY"> <Currency>TJS</Currency> <Currency>SZL</Currency> <Currency>TRY</Currency> <Currency>TND</Currency> <Currency>SLL</Currency> <Currency>STD</Currency> <Currency>SRD</Currency> <Currency>WST</Currency> <Currency>VND</Currency> <Currency>XPF</Currency> <Currency>XCD</Currency> <Currency>UAH</Currency> <Currency>TWD</Currency> <Currency>UZS</Currency> <Currency>USD</Currency> <Currency>TMT</Currency> <Currency>THB</Currency> <Currency>TTD</Currency> <Currency>TOP</Currency> <Currency>SOS</Currency> <Currency>SYP</Currency> <Currency>SSP</Currency> <Currency>XAF</Currency>


http://services.sabre.com/STL/v01

http://www.sabre.com/ns/Ticketing/TTL/1.0

http://services.sabre.com/STL/Catalog/v01




<Currency>VUV</Currency> <Currency>YER</Currency> <Currency>XOF</Currency> <Currency>UGX</Currency> <Currency>TZS</Currency> <Currency>VEF</Currency> <Currency>UYU</Currency> </CurrencyInfo> </TicketingOptions> <FraudOptions/> <PaymentOptions acceleratedCreditCardBilling="false" electronicCommerceIndicator="false"/> </StationInfo> </GetStationProfileRS> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

Request

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:eb="http://www.ebxml.org/namespaces/messageHeader"

xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext">

<SOAP-ENV:Header>

<eb:MessageHeader eb:version="2.0">

<eb:From>

<eb:PartyId />

</eb:From>

<eb:To>

<eb:PartyId />

</eb:To>

<eb:ConversationId>SOME_OTHER</eb:ConversationId>

<eb:Action>GetTicketingProfileRQ</eb:Action>

</eb:MessageHeader>

<wsse:Security>

<wsse:BinarySecurityToken>Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/STSA

!ICESMSLB\/STS.LB!-3300531971363514234!1882872!0!1!E2E-1</wsse:BinarySecurityToken>

</wsse:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<GetStationProfileRQ xmlns="http://www.sabre.com/ns/Ticketing/Profiles"

Version="1.0.0">

<Header />

<POS />

<SearchParameters>

<StationNumber>24485705</StationNumber>

</SearchParameters>

</GetStationProfileRQ>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Response

<DesignatePrinterRS

AltLangID="en-us" EchoToken="String" PrimaryLangID="en-us"

SequenceNmbr="1" Target="Production" TimeStamp="2011-11-15T18:30:46"

Version="2003A.TsabreXML1.1.1"



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

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

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

<Success/>

<TPA_Extensions>

<HostCommand>W*2ABBCA7890100010</HostCommand>

</TPA_Extensions>

</DesignatePrinterRS>

3.5 Troubleshooting Station Profile

3.5.1 Get Station Common Error Responses, Reasons and Solution

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.

This section provides examples of common error responses you might come across using

GetStationProfileRQ Web Service together with the reasons and tips on how to resolve these

problems.

3.5.1.1 Station corruption

In the case of a station that is corrupted or unable to be returned in the response due to a system error

the stations in error will appear at the top of the response. Continuing below that display will be the

response with valid stations and their information.

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header />

<SOAP-ENV:Body>

<GetStationProfileRS xmlns="http://www.sabre.com/ns/Ticketing/Profiles"

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

xmlns:ns3="http://www.sabre.com/ns/Ticketing/TTL/1.0"

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

xmlns:ns5="http://schemas.xmlsoap.org/soap/envelope/" Stations="0" Version="1.0.0">

<Header messageID="ds-station-profile-1">

<ns2:Results>

<ns2:Error status="Incomplete">

<ns2:System>T2-DS</ns2:System>

<ns2:SystemSpecificResults>

<ns2:ErrorMessage>Data Error. The following 1 stations could not be

processed</ns2:ErrorMessage>

</ns2:SystemSpecificResults>

<ns2:SystemSpecificResults>

<ns2:ErrorMessage>02090550</ns2:ErrorMessage> this will repeat for each

station that failed

</ns2:SystemSpecificResults>

</ns2:Error>

</ns2:Results>

</Header>









<POS>

<ns2:MultiHost>AA</ns2:MultiHost>

</POS>

<StationInfo> this is the start of the stations that are ok

<Station channel="ATO" code="SYDTS" number="02090546" />

<OfficeAccountingCode accountingCode="TS" city="SYD" officeId="0209054"

validatingProvider="AA" viewershipRestricted="false" />

<TicketingOptions ATAC_active="true" commisionProtectTicketing="false"

neutralTicketing="true" ticketingAllowed="true">

<SalesReport active="false" />

</TicketingOptions>

<FraudOptions />

<PaymentOptions acceleratedCreditCardBilling="true" electronicCommerceIndicator="false"

/>

</StationInfo>

<StationInfo>

3.5.1.2 Security validation error

This type of error is returned when a user does not possess the correct credentials to access the station profile service.

Error:

Security Validation Error

Response:


xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns2:GetStationProfileRS

Stations="0" xmlns="http://services.sabre.com/STL/v01" xmlns:ns2="http://www.sabre.com/ns/Ticketing/Profiles" xmlns:ns3="http://www.sabre.com/ns/Ticketing/TTL/1.0" xmlns:ns4="http://services.sabre.com/STL/Catalog/v01" xmlns:ns5="http://schemas.xmlsoap.org/soap/envelope/"> <ns2:Header> <Results> <Error status="Incomplete"> <System>T2-DS</System> <SystemSpecificResults> <ErrorMessage>Security Validation Error: User does not have the necessary keywords to use this service.</ErrorMessage> <ShortText>Error processing StationProfileRQ</ShortText> </SystemSpecificResults> </Error> </Results> </ns2:Header> </ns2:GetStationProfileRS> </SOAP-ENV:Body>










Name of Product GetAgencyProfile and UpdateAgencyProfile Service


4 GetAgencyProfile and

UpdateAgencyProfile Service

4.1 Understanding GetAgency and UpdateAgency profile WS

4.1.1 Introduction

This chapter provides the description of Profile Web Service. It provides information about types of

operations that the service supports and points out the ones that are not valid GetAgencyProfileRQ and

UpdateAgencyProfile requests.

The subsections of this chapter will provide detailed information about those portions of the XML

request or response that may need some additional explanation over and above what is described in

general information and schema annotations. XML samples in this document are for explanatory

purposes to give high overview of forming requests in different business scenarios

4.1.2 Prerequisites for Ticketing Profile Web Service

Following are the prerequisites for airlines and subscribers intending to use Ticketing Profile Web

Service:

• Must be a Sabre hosted carrier or a Sabre subscriber.

• Must have Profile Web Service activated in Airline partition.

4.1.3 XML Examples in this Document

The purpose of the XML examples provided in this document is to present the possible content of the

request and response. The XML responses contain a limited number of solutions in order to save room,

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

Note Examples are for illustrative purposes only.

4.1.4 Access Conditions

Attributes needed in the EPR to use the below two operations -

GetTicketingProfileRQ – OpenSystemsUser and SRW_User

UpdateTicketingProfileRQ - TktUpdateProfileUser



4.1.5 Authentication with USG

The TicketingProfile Web Service requires Universal Service Gateway (USG) authorization. The

security received from USG determines whether authentication was completed successfully and

whether your session is active.

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

Guide to Accessing and Consuming SOAP-Based Sabre APIs available at dev studio.

Following are tips on how you can obtain USG authorization:

• Use the SessionCreateRQ Web Service to authenticate the user in USG. After authenticated

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

Example:

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

• Include the received security token in the request to the Ticketimg Profile Web Service in the SOAP

Envelope.

Example:

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

• In the header message, include the service name as GetTicketingProfileRQ for

GetAgencyProfileRQ and UpdateTicketingProfileRQ for UpdateAgencyProfileRQ

• In the body of the request, use operation name GetAgencyProfileRQ for GetAgencyProfile and

UpdateAgencyProfileRQ for UpdateAgencyProfile.

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

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

4.1.6 Ticketing Profile Web Service WSDL file

WSDL stands for Web Services Definition Language and uses a common format to describe and

publish the formats, operations, and protocols of a Web Service. WSDL elements describe data using

XML schemas. The schema is passed to the Web Service. The description of the data tells the receiver

how to process the data, and the binding to a protocol or transport instructs the sender how to send the

data.

For the latest available links to WSDL files, please check for Ticketing Profile Web Service

documentation at TicketingProfileWS resources

There are two different WSDLs for the below two operations-

GetAgencyProfile: TicketingProfileServices

UpdateAgencyProfile: UpdateTicketingprofileServices

4.1.7 End Points

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

environments:

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

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


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

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



Res/Production: https://webservices-as.havail.sabre.com/xx

Note: (xx is carrier code similar to existing URLs used by carriers today)

4.2 GetAgencyProfileRQ

GetAgencyProfileRQ operation allows the users to search for details about Airline and Agency profiles.

Either all available details or specific Agency details can be retrieved. Different types of search

parameters are provided in the subsequent sections.

Below is the list of different get RQ options that GetAgencyProfileRQ provides:

Read the complete detail of an Airline and Agency Profile- This gives the complete

information on Airline profile in response, like Accounting Code, Form Code, Point of Sale,

Form of payment and GDSs and also Agency profile like IATA numbers, whether ticketing is

blocked or not and the Form of payment applicable at that agency level.

Read only the Airline Profile- This gives the information on Airline profile in response, like

Accounting Code, Form Code, Point of Sale, Form of payment and GDSs.

Read only a specific Agency/Agencies Profile- This gives the information on the agency/s

profile whether ticketing is blocked or not and the Form of payment applicable at that agency

level.

Read all the Agencies profile- This gives the information on all the agenies of the airline

whether ticketing is blocked or not and the Form of payment applicable to each of the

agencies.

Read the Airline profile along with specific Agencies Profile- This gives the complete

information on Airline profile in response, like Accounting Code, Form Code, Point of Sale,

Form of payment and GDSs and also the information on IATA numbers requested for,

whether ticketing is blocked or not and the Form of payment applicable at that agency level.

Read the complete Airline and Agency profile history- This gives information on the

changes made to the exception table. This will contain the history of airline profile changes as

well as all the agencies of that airline. It contains history of last 13 months and can be used

for audit purposes.

Read the Airline and specific Agency profile history- This gives information on the

changes done at airline profile and for the particular agency the WS user has requested for. It

contains history of last 13 months and can be used for audit purposes.

Note: How the request for each of the above cases needs to be generated is provided in the section

webservice xml examples. Example will also have the information on how the response looks.

4.2.1 Request Attributes

Following are the request attribute:

Attribute Description Example Web Service Path

XML version Required. Version of the service the consumer wishes to use.

1.1.0 GetAgencyProfileRQ/@version

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




Minimum version required to use this operation is 1.1.0

4.2.2 Request Elements

Following are the request elements:

Element Description Web Service Path

Header Required. Standard header information that helps orchestrate the requests.

GetAgencyProfileRQ/Header

Search parameters

Required. Search parameters that allow selecting what information from the Database is requested by the agent

GetAgencyProfileRQ /SearchParameters

Diagnostic Optional. For internal troubleshooting purposes only.

GetAgencyProfileRQ/Diagnostic

4.2.3 Selected Request Elements

The subsections provide details about selected elements of GetAgencyProfileRQ request that may

require additional explanation.

This section includes the following search parameters:

4.2.3.1 Search Parameters

This section contains information about Search Parameters elements/attributes along with the

description of the options available in GetAgencyProfileRQ.

4.2.3.1.1 Search Parameters Request Attributes

Following are the Search parameters request attribute:


Result type

Required. A mandatory code that represents the format of a response to be returned in a GetAgencyProfile transactions. The valid codes are:

D- Detail result type

If result type ‘D’ is specified both Airline and all Agency information is provided.

C- Custom result type

If result type ‘C’ is specified then selected sections need to be defined in CustomDetails and

D GetAgencyProfileRQ/SearchParameters/@resultType




requested information is returned in GetAgencyProfile response.

H- History result type

If result type ‘H’ is specified then history of the Airline and Agency transactions can be retrived from GetAgencyProfileRQ

4.2.3.1.2 Search Parameters Request Elements

Following are the Search parameters request sub-elements:

Element Description Example GetAgencyProfile Path

Custom details Optional. If Custom result type attribute is specified, then requested data sections need to be defined in this element. Each section required to be specified as a separate Custom details element.

For version 1.1.0 or higher, GetAgencyProfileRQ will have two options, CreditLimitOptions and Agency

Agency GetAgencyProfileRQ/SearchParameters/CustomDetails

AgencyNumber Optional. For the custom result type for an Agency, WS user can provide the specific agency number they want the details for.

99999992 GetAgencyProfileRQ/SearchParameters/AgencyNumber

4.2.4 Response Elements

Following are the reponse elements of Get requests:


CreditLimitOptions

This provides the airline profile information.

GetAgencyProfileRS/AgencyInfo/CreditLimitOptions

Accounting Codes This will have the accounting code for which the airline wants to create profile for.

045 GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/AccountingCodes

Form Numbers This will have the list of form codes for which airline wants to create profile for.

821 GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/FormNumbers

System Providers This will have the list of GDSs for which airline wants to create profile for.

1S GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/SystemProviders




PointofSale Point of sale will have the information on country and form of payments applicable at airline level.

GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/PointOfSale

PaymentCodes This will have the list of form of payments for which the airline wants to block ticketing for.

CA GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/PointOfSale/PaymentCodes

Agency This provides the agency profile information on which IATA is blocked for which FOP

GetAgencyProfileRS/AgencyInfo/Agency

CreditLimitOptions

This provides information on whether ticketing is blocked or not and for which FOP

GetAgencyProfileRS/AgencyInfo/Agency/CreditLimitOptions

BlockTicketing This gives information or whether ticketing is blocked or not.

True GetAgencyProfileRS/AgencyInfo/Agency/CreditLimitOptions/BlockTicketing

PaymentCodes This gives information on FOP for which ticketing is blocked.

FOP blocked is a union of FOP at airline level and Agency level.

CA GetAgencyProfileRS/AgencyInfo/Agency/CreditLimitOptions/PaymentCodes

HistoryInfo This gives information on the transactions that were made by agents or system.

GetAgencyProfileRS/HistoryInfo

AgentInfo This gives information about the agent who made the changes to agency or airline profile.

GetAgencyProfileRS/HistoryInfo/AgentInfo

Transaction Time This gives information on the transaction date and time the profile table was updated.

2017-07-26T04:45:18.614-05:00

GetAgencyProfileRS/HistoryInfo/AgentInfo/TransactionDateTime

Home Location This gives information on the agent home location from where the transaction was done.

GetAgencyProfileRS/HistoryInfo/AgentInfo/HomeLocation

Work Location This gives information on the agent work location

GetAgencyProfileRS/HistoryInfo/AgentInfo/WorkLocation

LocalDateTime This gives information on the transaction date and time the agent requested for profile table update.

2017-07-26T04:45:18.000-05:00

GetAgencyProfileRS/HistoryInfo/AgentInfo/LocalDateTime

Profile Information Information about what profile parameters and attributes were changed

GetAgencyProfileRS/HistoryInfo/ProfileInfo

Credit Limit Options

This will have information on the changes that were done at airline profile

GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions

Form Numbers This will have information on the changes that were done on form codes

821 GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions/FormNumbers




System Providers This will have information on the changes that were done on GDSs

1S GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions/SystemProviders

Point Of Sale This will have information on the changes that were done on country and form of payment at airline level

GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions/PointOfSale

Payment Codes This will have information on the changes that were done on form of payment at airline level

CA GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions/PointOfSale/PaymentCodes

Agency This will have information on the changes that were done on agency level

99999992 GetAgencyProfileRS/HistoryInfo/ProfileInfo/Agency

CreditLimitOptions

This will have information on the changes that were done on agency level whether ticketing was blocked/unblocked

GetAgencyProfileRS/HistoryInfo/ProfileInfo/Agency/CreditLimitOptions

BlockTicketing This will have information on the changes that were done on agency level whether ticketing was blocked/unblocked for an agency

True GetAgencyProfileRS/HistoryInfo/ProfileInfo/Agency/CreditLimitOptions/BlockTicketing

PaymentCodes This will have information on the changes that were done on form of payment for that agency

CA GetAgencyProfileRS/HistoryInfo/ProfileInfo/Agency/CreditLimitOptions/PaymentCodes

4.2.5 Response Attributes

Below is the list fo all the attributes in get response


Country

This will have information on the PointOfSale country for which airline wants to create profile for adding into exception table

BR GetAgencyProfileRS/AgencyInfo/CreditLimitOptions/PointOfSale/@country

IATA Number This will have the agency number for which ticketing needs to be blocked

99999992 GetAgencyProfileRS/AgencyInfo/Agency/@number

Agent Sine Agent sine in code 4AK GetAgencyProfileRS/HistoryInfo/AgentInfo/@sine

Agent duty Agent duty code 5 GetAgencyProfileRS/HistoryInfo/AgentInfo/@duty

Agent employee ID

Agent employee ID 2201079 GetAgencyProfileRS/HistoryInfo/AgentInfo/@employeeID

Agent Name Agent full name Jon Snow GetAgencyProfileRS/HistoryInfo/AgentInfo/@name




Country This will give the information on the changes that were done on the point of sale country

BR GetAgencyProfileRS/HistoryInfo/ProfileInfo/CreditLimitOptions/PointOfSale/@country

Number This will give the information on the agency number on which any changes were done.

99999992 GetAgencyProfileRS/HistoryInfo/ProfileInfo/Agency/@number

4.3 UpdateAgencyProfileRQ

UpdateAgencyProfileRQ operation:

• Allows an Agent to update Airline profile with

• FormNumbers

• SystemProviders

• Country

• FOP

• Allows an Agent to block or unblock agencies for the FOPs they want to take action on.

Note: WS User can either update Airline profile or Agency Profile and NOT both in one request.

For each element/attribute which are editable, there is an attribute “action” which can take value “set”

or “remove”. Set means adding new data and remove means removing the existing data. The “values”

element will have the value of that particular element.

4.3.1 Request Attributes

Following are the request attributes:


XML version Required. Version of the service the consumer wishes to use.

1.1.0 UpdateAgencyProfileRQ/@Version

4.3.2 Request Elements

Following are the request elements:


Header Required. Standard header information that helps orchestrate the requests.

UpdateAgencyProfileRQ/Header

AgencyInfo Required. User can either select CreditLimitOptions or Agency to update.

UpdateAgencyProfileRQ/AgencyInfo




Diagnostic Optional. For internal troubleshooting purposes only. UpdateAgencyProfileRQ/Diagnostic

4.3.3 Selected Request Elements and attributes

The subsections provide details about selected elements of UpdateAgencyProfile request that may

require additional explanation.

This section includes the following:

• CreditLimitOptions- Allows to update the Airline profile

• Agency- Allows to update the Agency/Agencies profile

Note: For all valid request, WS user will get a success response. Response is shown in the sample xml.

4.3.3.1 CreditLimitOptions

The subsection contains information about CreditLimitOptions element/attributes of

UpdateAgencyProfile section.

Element/A

ttribute

Name

Description Example Web Service Path

FormNumbers

Optional. Form Codes of EMD and Tickets needs to be provided.

21 UpdateAgencyProfileRQ/AgencyInfo/CreditLimitOptions/FormNumbers

SystemProviders

Optional. The GDS for which the ticketing needs to be blocked needs to be provided.

1S UpdateAgencyProfileRQ/AgencyInfo/CreditLimitOptions/SystemProviders

PointOfSale- Country

Optional. The country in which and the form of payment for which ticketing needs to be blocked needs to be provided.

BR

UpdateAgencyProfileRQ/AgencyInfo/CreditLimi

tOptions/PointOfSale/@country

PaymentCode

Optional. The FOP for which ticketing needs to be blocked.

CA, CK UpdateAgencyProfileRQ/AgencyInfo/CreditLimi

tOptions/PointOfSale/PaymentCodes

4.3.3.2 Agency Options

The subsection contains information about Agency options sub-element/attributes of

UpdateAgencyProfileRQ.

4.3.3.2.1 Agency Options element/attributes

Following is the update agency info request sub-element details:



Attribute/Elem

ents

Description Example Web Service Path

Number Required. IATA number of the agency for which ticketing needs to be blocked needs to be provided.

99999992 UpdateAgencyProfileRQ/AgencyInfo/Agency/@number

BlockTicketing Optional. Boolean value (True or False) to indicate whether ticketing is blocked or not.

True UpdateAgencyProfileRQ/AgencyInfo/Agency/CreditLimitOptions/BlockTicketing

PaymentCodes Optional. This is the FOP for which the user wants to restrict ticketing at agency number level

CA UpdateAgencyProfileRQ/AgencyInfo/Agency/CreditLimitOptions/PaymentCodes

4.4 Ticketing Profile Web Service XML examples

4.4.1 GetAgencyProfileRQ Sample request and response XML

Below there are GetAgencyProfile request and response examples in the different business scenarios.

Note: All XML examples are provided in this guide for demonstration purposes only.

The initial examples created for the below use cases use version 1.1.0.

4.4.1.1 Detail Result Type Search

Scenario: An Agent sends request to search for Detail Agency Profile information which will respond

with all the current details of the airline along with agency information.

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"


<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>GetTicketingProfileRQ</ns1:Service>



<ns1:Action>GetTicketingProfileRQ</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/!ICE

SMS\/STSA!ICESMSLB\/STS.LB!-

3249901503802601842!1530312!0</ns1:BinarySecurityToken>

</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<GetAgencyProfileRQ

Version="1.1.0"

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

<Header/>

<SearchParameters resultType="D"/>

</GetAgencyProfileRQ>

</SOAP-ENV:Body>


Response:


<SOAP-ENV:Envelope

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header/>

<SOAP-ENV:Body>

<n1:GetAgencyProfileRS

version="1.1.0"

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

<STL:STL_Header.RS

customerID="" diagnosticLevel="" messageID="" timeStamp=""

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

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

xmlns:n2="http://www.sabre.com/ns/Ticketing/Profiles/Internal">

<STL:Results>

<STL:Success>

<System

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

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


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


xmlns:ns6="http://schemas.xmlsoap.org/soap/envelope/">T2-DMS</System>

</STL:Success>

</STL:Results>

</STL:STL_Header.RS>

<n1:AgencyInfo

provider="LA">

<n1:CreditLimitOptions>

<n1:AccountingCodes>

<n1:Values>957</n1:Values>




</n1:AccountingCodes>

<n1:FormNumbers>










</n1:FormNumbers>

<n1:SystemProviders>

<n1:Values>1S</n1:Values>

<n1:Values>1A</n1:Values>

</n1:SystemProviders>

<n1:PointOfSale

country="BR">

<n1:PaymentCodes>

<n1:Value>CA</n1:Value>

</n1:PaymentCodes>

</n1:PointOfSale>

</n1:CreditLimitOptions>

<n1:Agency

number="57530163">

<CreditLimitOptions>

<n1:BlockTicketing>false</n1:BlockTicketing>

<n1:PaymentCodes>

<n1:Values>CA</n1:Values>

</n1:PaymentCodes>

</CreditLimitOptions>

</n1:Agency>

<n1:Agency

number="22018620">



<n1:PaymentCodes>

<n1:Values>**</n1:Values>

<n1:Values>CK</n1:Values>

</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57551163">



<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57545143">


<n1:BlockTicketing>true</n1:BlockTicketing>

<n1:PaymentCodes>




</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57550835">



<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

<n1:Agency number="57512545">




</n1:Agency>

</n1:AgencyInfo>

</n1:GetAgencyProfileRS>

</SOAP-ENV:Body>


4.4.1.2 Custom Result Type Search Parameters – Airline Profile

Scenario: An Agent sends request to search for only Airline Profile information which will respond

with all the current details of the airline and not show Agency level data.

ResultType= “C” and CustomDetails would be equal to “CreditLimitOptions”

Note: SOAP envelope is removed to keep the user guide compact.

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>

<SearchParameters resultType="C">

<CustomDetails>CreditLimitOptions</CustomDetails>

</SearchParameters>


</SOAP-ENV:Body>


Response

<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System







</STL:Success>

</STL:Results>


<n1:AgencyInfo

provider="LA">








<n1:FormNumbers>










</n1:FormNumbers>





<n1:PointOfSale country="BR">

<n1:PaymentCodes>


</n1:PaymentCodes>

</n1:PointOfSale>


</n1:AgencyInfo>


</SOAP-ENV:Body>


4.4.1.3 Custom Result Type Search Parameters – Agency Number search

Scenario: An Agent sends request to search for only Agency level Profile information which will

respond with all the current details of the agency and not show Airline Profile data.

CustomDetails would be “Agency” and result type would be “C” and Agency Number/s whose details

the user wants to check. Below is the sample RQ/RS.

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>


<AgencyNumber>57530163</AgencyNumber>

<CustomDetails>Agency</CustomDetails>

</SearchParameters>


</SOAP-ENV:Body>


Response


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System







</STL:Success>

</STL:Results>




<n1:AgencyInfo

provider="LA">




<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

</n1:AgencyInfo>


</SOAP-ENV:Body>


4.4.1.4 Custom Result Type Search Parameters – Agency Number search

Scenario: An Agent sends request to search for only Agency level Profile information which will

respond with all the current details of all the agencies in that profile and not show Airline Profile data.

CustomDetails would be “Agency” and result type would be “C. Below is the sample RQ/RS.

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>



</SearchParameters>


</SOAP-ENV:Body>


Response


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System







</STL:Success>

</STL:Results>


<n1:AgencyInfo

provider="LA">

<n1:Agency

number="57530163">



<n1:PaymentCodes>




</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="22018620">



<n1:PaymentCodes>


<n1:Values>CK</n1:Values>

</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57551163">



<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57545143">



<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

<n1:Agency

number="57550835">



<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>





</n1:Agency>

</n1:AgencyInfo>


</SOAP-ENV:Body>




4.4.1.5 Custom Result Type Search Parameters – Agency Number and Airline profile

Scenario: An Agent sends request to search for Airline profile and Agency level Profile information

which will respond with all the current details of that agency and Airline Profile data.

CustomDeatils would be “Agency” and “CreditLimitOptions” and result type would be “C” and

Agency Number whose details the user wants to check. Below is the sample RQ/RS.

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>


<AgencyNumber>57530163</AgencyNumber>

<CustomDetails>CreditLimitOptions</CustomDetails>


</SearchParameters>


</SOAP-ENV:Body>




Response


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System







</STL:Success>

</STL:Results>


<n1:AgencyInfo

provider="LA">






<n1:FormNumbers>










</n1:FormNumbers>





<n1:PointOfSale

country="BR">

<n1:PaymentCodes>


</n1:PaymentCodes>

</n1:PointOfSale>







<n1:PaymentCodes>


</n1:PaymentCodes>


</n1:Agency>

</n1:AgencyInfo>


</SOAP-ENV:Body>


4.4.1.6 History Details for Airline and Agency Profile

Scenario: An Agent sends request to search for History for all the transactions that were done.

WS user sends result type as “H” to retrieve the historical data of last 13 months with only those Airline

profile and agency profile data which were updated.

The response will also have information on who made the changes to the exception/profile table. The

agent information with transaction date and time will be available.

Below is the RQ/RS.

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>

<SearchParameters resultType="H"/>


</SOAP-ENV:Body>


Response


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System






xmlns:ns6="http://schemas.xmlsoap.org/soap/envelope/">T2-

DMS</System>

</STL:Success>

</STL:Results>


<n1:HistoryInfo>

<n1:AgentInfo

duty="5" employeeID="899790" name="I HUSSAIN "

sine="4AK">

<n1:TransactionDateTime>2017-07-26T04:45:18.614-

05:00</n1:TransactionDateTime>

<n1:WorkLocation/>

<n1:LocalDateTime>2017-07-26T04:45:18.000-05:00</n1:LocalDateTime>

</n1:AgentInfo>

<n1:ProfileInfo>



<n1:Value



action="set">1S</n1:Value>

<n1:Value

action="set">1A</n1:Value>


<FormNumbers>

<n1:Value

action="set">10</n1:Value>

<n1:Value


<n1:Value


<n1:Value

action="remove">488</n1:Value>

</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo

duty="5" employeeID="899790" name="I HUSSAIN"

sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>

<n1:CreditLimitOptions/>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>



<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>




<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>




<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<n1:PointOfSale

action="set" country="BR"/>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:AgentInfo sine="LA" duty="4" employeeID="220109" name="Jamie

Lannister">

<n1:TransactionDateTime>2001-12-

17T09:30:47Z</n1:TransactionDateTime>

<n1:HomeLocation>RIO</n1:HomeLocation>

<n1:WorkLocation>RIO</n1:WorkLocation>

<n1:LocalDateTime>2001-12-

17T09:30:47Z</n1:LocalDateTime>

</n1:AgentInfo>

<n1:ProfileInfo>

<Agency number="11111111" action="set">


<BlockTicketing

action="set">true</BlockTicketing>

<PaymentCodes>

<Value action="set">CA</Value>

<Value action="set">IN</Value>

</PaymentCodes>


</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo sine="LA" duty="4" employeeID="220110"

name="Tyrion Lannister">







</n1:AgentInfo>

<n1:ProfileInfo>





<BlockTicketing

action="set">false</BlockTicketing>


</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>









</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>


name="Jamie Lannister">



<n1:HomeLocation>SCL</n1:HomeLocation>

<n1:WorkLocation>SCL</n1:WorkLocation>



</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>











</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>


</SOAP-ENV:Body>


4.4.1.7 History details of an Agency

Scenario: An Agent sends request to search for transaction History for an agency.

WS user sends result type as “H” and agency number to retrieve the historical data of last 13 months

of an agency.

Note: The response will contain the airline profile history along with the specific agency that the WS

user requested for.

Below is the RQ/RS –

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>

<GetAgencyProfileRQ

Version="1.1.0"


<Header/>

<n1:SearchParameters resultType="H">

<n1:AgencyNumber>11111111</n1:AgencyNumber>

</n1:SearchParameters>


</SOAP-ENV:Body>

Response


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>


version="1.1.0"


<STL:STL_Header.RS





<STL:Results>

<STL:Success>

<System






xmlns:ns6="http://schemas.xmlsoap.org/soap/envelope/">T2-

DMS</System>

</STL:Success>

</STL:Results>


<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>




</n1:AgentInfo>

<n1:ProfileInfo>



<n1:Value

action="set">1S</n1:Value>

<n1:Value

action="set">1A</n1:Value>


<FormNumbers>

<n1:Value


<n1:Value


<n1:Value


<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo

duty="5" employeeID="899790" name="I HUSSAIN"

sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>

<n1:CreditLimitOptions/>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo




sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">





<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">





<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<FormNumbers>

<n1:Value


</FormNumbers>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>

<n1:AgentInfo


sine="4AK">



<n1:WorkLocation/>


</n1:AgentInfo>

<n1:ProfileInfo>


<n1:PointOfSale

action="set" country="BR"/>


</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:AgentInfo sine="LA" duty="4" employeeID="220109" name="Jamie

Lannister">







</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing

action="set">true</BlockTicketing>

<PaymentCodes>

<Value action="set">CA</Value>

<Value action="set">IN</Value>

</PaymentCodes>


</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>











</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>









</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>

<n1:HistoryInfo>









</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>



</n1:HistoryInfo>

<n1:HistoryInfo>









</n1:AgentInfo>

<n1:ProfileInfo>



<BlockTicketing



</Agency>

</n1:ProfileInfo>

</n1:HistoryInfo>


</SOAP-ENV:Body>


4.4.2 UpdateAgencyProfile Sample request and response XML

Below are UpdateAgencyProfileRQ request and response examples in the different business scenario.

User can either update airline profile or agency profile and not both as part of one request.

4.4.2.1 UpdateAgencyProfile action to set Airline Profile

To update Airline profile, WS user needs to choose CreditLimitOptions and “set” or “remove” whatever

elements/attributes they want to edit in airline profile. Eg- FOP, Form Codes, Country or GDS/.

Below is the RQ/RS-

Request:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""




<ns1:From>


</ns1:From>

<ns1:To>


</ns1:To>



<ns1:Service>UpdateTicketingProfileRQ</ns1:Service>

<ns1:Action>UpdateTicketingProfileRQ</ns1:Action>

<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>


<ns1:Security





</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<UpdateAgencyProfileRQ

Version="1.1.0"


<Header>

<ns1:Operation

xmlns:ns1="http://services.sabre.com/STL/v01">UpdateTicketingProfileRQ</n

s1:Operation>

<ns2:Service

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

s2:Service>

</Header>

<n1:AgencyInfo>


<n1:FormNumbers>

<n1:Value action="set">021</n1:Value>

<n1:Value action="remove">822</n1:Value>

</n1:FormNumbers>


<Value action="set">1P</Value>


<n1:PointOfSale action="set" country="BR">

<n1:PaymentCodes>

<n1:Values action="remove">CK</n1:Values>

<n1:Values action="set">CA</n1:Values>

</n1:PaymentCodes>

</n1:PointOfSale>


</n1:AgencyInfo>

</UpdateAgencyProfileRQ>

</SOAP-ENV:Body>




Response:


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>

<n1:UpdateAgencyProfileRS

version="1.1.0"


<STL:STL_Header.RS



xmlns:ns2="http://www.sabre.com/ns/Ticketing/Profiles/Internal">

<STL:Results>

<STL:Success>

<System






</STL:Success>

</STL:Results>


</n1:UpdateAgencyProfileRS>

</SOAP-ENV:Body>


4.4.2.2 UpdateAgencyProfile action to set Airline Profile

To update Agency profile, WS user needs to choose “Agency” and “set” or “remove” whatever

elements/attributes they want to edit or block/unblock ticketing.

Below is the RQ/RS-

Request:


<SOAP-ENV:Envelope




<SOAP-ENV:Header>

<ns1:MessageHeader

ns1:version=""


<ns1:From>




</ns1:From>

<ns1:To>


</ns1:To>



<ns1:Service>UpdateTicketingProfileRQ</ns1:Service>


<ns1:MessageData>

<ns1:MessageId/>

<ns1:Timestamp/>

</ns1:MessageData>


<ns1:Security





</ns1:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<UpdateAgencyProfileRQ

Version="1.1.0"


<Header/>

<AgencyInfo>

<Agency

number="57530163">


<BlockTicketing


<PaymentCodes>

<Value action="remove">**</Value>

</PaymentCodes>


</Agency>

</AgencyInfo>

</UpdateAgencyProfileRQ>

</SOAP-ENV:Body>


Response:


<SOAP-ENV:Envelope


<SOAP-ENV:Header/>

<SOAP-ENV:Body>

<n1:UpdateAgencyProfileRS

version="1.1.0"


<STL:STL_Header.RS



xmlns:ns2="http://www.sabre.com/ns/Ticketing/Profiles/Internal">



<STL:Results>

<STL:Success>

<System






</STL:Success>

</STL:Results>


</n1:UpdateAgencyProfileRS>

</SOAP-ENV:Body>


4.5 TroubleShooting GetAgencyProfile and UpdateAgencyProfile

4.5.1 Overview

This section provides examples of the most common error messages, their causes, and recommended

solutions where applicable.

There are several steps that Ticketing Profile Web Service makes during transaction processing and,

on each of these steps, an error message can be returned if the system detects the problem.

These steps are:

• USG Universal Service Gateway authorization validation

• Validation of incoming request against XSD schema.

• Business validation of incoming request. This validation is performed by the exception table.

4.5.2 Error Messages by Category

4.5.2.1 WS Validations

Use case Error: Short message (WS) Error: Long Message (WS)

ResultType (if the user enters

result type other than “C”, “D”

or “H”)

XML request schema

validation failed

Unsupported Result Type

values. Valid Search

parameters are: "C", "D", "H"

CustomDetail Values (If the

user provides customdetail

values other than

"CreditLimitOptions",

"Agency”)

XML request schema

validation failed

Unsupported Custom Detail

values. Valid Search

parameters

are:"CreditLimitOptions",

"Agency”.



Country Code (If the user

enters anything other than 2

letter country code)

XML request schema

validation failed

Invalid Country Code

GDS (If the user enters

anything other than 2

alphanumeric GDS)

XML request schema

validation failed

Invalid System Provider

Form Number (if user enters

anything more than 3 digit

form number)

XML request schema

validation failed

Invalid Form Number

FOP (if user enters anything

other than 3 letters)

XML request schema

validation failed

Invalid Form of Payment

IATA Number ( if the user

enters anything other than 8

digit)

XML request schema

validation failed

Invalid Agency Number

Note:

1. When updating ticketing blocked or not for an agency, if the user just removes the Boolean

value, it will take the other value. Eg: For an IATA, the WS user, using action type “remove”

removes “true” from Is ticketing blocked?, database will automatically change it to “false”. Is

ticketing blocked field can’t be NULL.

2. On similar lines, if the WS user, doesn’t remove “true” from Isticketingblocked? and sets it to

“false”, database will update it to “false” and remove true. Isticketingblocked will be single

property field.

3. All WS service related errors will have error code 99003

4.5.2.2 Database(DMS) Validations

Below are few business validations to be applied on DMS side and the error messages if the request

fails the validation.

Use case Error:Short message Error:Long Message

Country Code (If the user

enters anything other than the

list of country code maintained

in ticketing database)

Request business validation

failed

Incorrect Country Code

GDS (If the user enters

anything other than the list of


failed

Incorrect System Provider



GDSs maintained in ticketing

database )

Form Number (if user enters

anything other than the list of

form numbers maintained in

ticketing database)


failed

Incorrect Form Number

FOP (if user enters anything

other than the list of FOPs

maintained in ticketing

database)


failed

Incorrect Form of Payment

Note:

1. All Database related (business validation failures) will have error code 75000

Name of Product


AS User Guide Template - Sabrefiles.developer.sabre.com/doc/providerdoc/Ticketing/cert-Ticketing... · Name of Product Introduction 20 November 2017 5 Confidential and Proprietary

Documents