Software version 2016 -...

Software version 2016

Document Edition #3

This documentation is the confidential and proprietary

intellectual property of the Sabre® 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 is

strictly prohibited.

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

Network logo, Sabre Airline Solutions, the Sabre Airline Solutions

logo, Sabre Hospitality Solutions, the Sabre Hospitality Solutions

logo, are trademarks of Sabre. All other trademarks, service

marks and trade names are the property of their respective

owners.

© 2016 Sabre Inc. All rights reserved.

TN TKT_TravelAgencyReports Table of Contents 1

st September 2016 iii Confidential and Proprietary Sabre Travel Network

Document Revision Information

Project Name Audit Trail Report User Guide

Project Number

Prepared by Stephanie Bidun Date Prepared 1st September

2016

Revised by Date Revised

Revision Reason Revision Control No.














st September 2016 iv Confidential and Proprietary Sabre Travel Network

Table of Contents

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

1.1 Overview........................................................................................................................................................ 6 1.2 Examples in this Document ........................................................................................................................... 6 1.3 Audit Trail operation WSDL file ...................................................................................................................... 6 1.4 Getting Started Guide .................................................................................................................................... 6

2 U n d e r s t a n d i n g t h e A u d i t T r a i l W e b S e r v i c e

2.1 Security Validation ......................................................................................................................................... 8

3 A u d i t T r a i l R e p o r t ( D Q B W S )

3.1 DailySalesSummaryRQ ................................................................................................................................. 9 3.1.1 Search Parameters for an Audit Trail Report .................................................................................. 9 3.1.2 DailySalesSummaryRQ Attributes ................................................................................................ 10 3.1.3 Common RQ Header Attributes .................................................................................................... 11 3.1.4 Common RQ Header Elements ..................................................................................................... 12 3.1.5 DailySalesSummaryRQ SelectionCriteria Attributes ..................................................................... 13 3.1.6 DailySalesSummaryRQ SelectionCriteria Elements ..................................................................... 14

3.2 DailySalesSummaryRS ............................................................................................................................... 16 3.2.1 Common RS Attributes ................................................................................................................. 16 3.2.2 Common RS Header Attributes ..................................................................................................... 17 3.2.3 Common RS Header Elements ..................................................................................................... 18 3.2.4 DailySalesSummarRS header ....................................................................................................... 19 3.2.5 DailySalesSummaryRS Elements ................................................................................................. 20

3.2.5.1 Transaction attributes and elements ................................................................................ 21 3.2.5.2 TotalDailySales attributes and elements .......................................................................... 25

3.3 Duplicated Document Numbers ................................................................................................................... 26 3.4 DailySalesSummaryRQ/RS Examples ........................................................................................................ 26

3.4.1.1 RQ .................................................................................................................................... 26 3.4.1.2 RS .................................................................................................................................... 27

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

4.1 Introduction .................................................................................................................................................. 29 4.2 DQBWS Communication points ................................................................................................................... 29 4.3 Common Error Responses, Reasons and Solution ..................................................................................... 29

4.3.1.1 USG Authentication Errors ............................................................................................... 30 4.3.1.2 USG Invalid Security ........................................................................................................ 30


st September 2016 v Confidential and Proprietary Sabre Travel Network

4.3.1.3 No Branch Access ............................................................................................................ 30 4.3.1.4 Invalid Service Version Specified in XML Request ........................................................... 31 4.3.1.5 Request XML Validation Failed Against Schema ............................................................. 32

TN GetTicketingDocument Introduction

1st September 2016 6 Confidential and Proprietary Sabre Travel Network

1 Introduction

1.1 Overview

The Audit Trail Report (DQBWS) is a web service which provides travel agents an alternate way to retrieve any sale or refund that is currently available today through Sabre Red.

With this solution, customers will create their own custom web application to interface with the data and generate reports in a structured way allowing custom presentation of the data.

The Audit Trail Report operation can be used by XML based web sites, internet booking engines, front end GUI web services, kiosk web services, and mobile applications.

Each DailySalesSummaryRQ(Request) /DailySalesSummaryRS(Response) pair is fully annotated in the TKT_ AsrServices schemas so this user guide will not restate the documentation included in the schemas.

The purpose of this guide is to introduce how the web service processes audit trail reports. It is not a complete documentation of XML design. The Sabre repository for all web service information can be found at Sabre Dev Studio. Please visit the site and register for an account if you have not done so already.

This introductory guide provides:

Description of web service features

Examples of typical Audit Trail request/response

Common error messages that may be returned by the web service along with the explanation as to why they occur and ways for fixing the problem where applicable.

1.2 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 (RQ/RS).

Note: Examples are for illustrative purposes only.

1.3 Audit Trail operation 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 Audit Trail documentation at Sabre Dev Studio.

1.4 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

1

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

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

TN GetTicketingDocument Understanding the Audit Trail Web Service


2 Understanding the Audit Trail Web

Service

This web service provides standalone Request(RQ)/Response(RS) messaging allowing a client to request the audit trail report. 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. TKT_AsrServices.xsd is the core schema which defines all the DailySalesSummaryRQ/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 DailySalesSummaryRQ/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 (except for one case described below) which means there is no set sequence in which messages must flow. Each RQ/RS pair is considered standalone.

The CachedReportRQ message has a prerequisite which requires that a report has already been requested (and was determined by our system to result in a long running query which won’t complete before the web service transaction times-out or that the response would be too large to send in one response). In this scenario the system will cache the report (and break it into chunks if too large) sending back a ReportId to the client. The client can then request the report using CachedReportRQ. Cached reports will remain available in the system for 24 hours after they are created.

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 Audit Trail Reports XML. The subsections of this chapter will provide detailed information about those parts of the XML request that may need some additional explanation over and above what is described in general information and schema annotations.

2

TN GetTicketingDocument Understanding the Audit Trail Web Service


2.1 Security Validation

Security validation is performed to verify whether a user requesting the document is authorized to access it. It protects the documents data from viewing by unauthorized parties, i.e. other Travel Agency.

When a Travel Agency requests a branch location’s document, the system will validate if branch access is allowed. If validation fails, an error message will be returned to the user and the transaction will fail.

TN GetTicketingDocument Audit Trail Report (DQBWS)


3 Audit Trail Report (DQBWS)

The Audit Trail Report displays the requesting travel agency pseudo city sales for the date specified. If no date is specified the information returned will be for current date. The ticketing data needed to populate the audit trail report will be stored in the Sabre’s ticketing database for 13 months.

The following features are offered:

Request a report based on branch PCC utilizing Branch Access Security Ability to request by Settlement Type, Document Type or a Document Number. Additional features allow adding a report date and retrieving information for up to 13 months or

displaying a report by airline code.

3.1 DailySalesSummaryRQ

3.1.1 Search Parameters for an Audit Trail Report

The Audit Trail report available search parameters include:

PseudoCityCode (PCC)

Airline

ReportDate

SettlementType

DocumentType

DocumentNumber

The Web Service will always use a PCC for Travel Agency requests. If the User does not include a PCC in the search criteria (e.g. to access a branch’s document), the User’s Home PCC will be used.

The requesting client can specify one or more filters for the Audit Trail report 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 DailySalesSummaryRS.

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

3



3.1.2 DailySalesSummaryRQ Attributes

Attribute Description

XML version Required in the XML schema.

Option to display the Audit Trail Report Optional in the XML schema.

It is used to retrieve the Audit Trail Report.



3.1.3 Common RQ 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 DQBWS



diagnosticLevel Not used by DQBWS

ttl Not used by DQBWS

3.1.4 Common RQ Header Elements

Elements Description

ConversationId Not used by DQBWS

OrchestrationID Optional. 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 DQBWS

Service Not used by DQBWS

Messaging Not used by DQBWS




Parameters Not used by DQBWS

Security Not used by DQBWS

DiagnosticData Not used by DQBWS

3.1.5 DailySalesSummaryRQ SelectionCriteria Attributes

Attributes of SelectionCriteria - Used to define what should be included in the Audit Trail Report including optional filters. Filters are unique to each report.

Attributes Description

isCacheLateLargeReports Optional. The client can specify if they want the system to cache a report if it is deemed too large to return in one XML document or if the report query runs too long and won't complete before the system timeout. If this is set to true the system will cache the report and the client can retrieve the report at a later time using CachedReportRQ. Suggested size limit is 10MB

clientTimeoutSecs Optional. The client can specify a smaller timeout period which the system will use to determine if a report will be returned late. If the query won't finish in time the system will cache the report and the client can retrieve the report at a later time using CachedReportRQ. The timeout cannot exceed 25 seconds.



3.1.6 DailySalesSummaryRQ SelectionCriteria Elements

Elements of SelectionCriteria Used to define what should be included in the Audit Trail report including optional filters.


PseudoCityCode Optional. 4 alpha numeric travel agency Pseudo City Code for which the report was generated. Only documents issued by this travel agency will be returned. OR Required. If requesting a Branch Pseudo City Code then this field is required. This must match the security settings in the Sabre system.

Airline Optional. 2 letter Airline Carrier Code or 3 numeric Airline Carrier Code for which the report was generated. Only documents issued by this airline will be returned.

ReportDate Optional. The date for which the report is run Only documents issued on the date requested will be returned. If no date is entered the report defaults to current day.

SettlementType Optional. Report data will be limited to the settlement type specified. Available options for this are: TAT, TCH, TKT, STA or KIL Only one settlement type is permitted in the request. If settlement type is not entered all data regardless of settlement type will be returned in the response.



DocumentType Optional. Available options are TKT, EMD, RFND, RFEMD, MCO. Only one document type is permitted in the request. If document type is not entered then all transaction types will be returned in the response.

Code Form Type

TKT Ticket - Any Sale transaction

EMD Electronic Miscellaneous Document

RFND Refund documents

RFEMD Refunded EMD documents

MCO Miscellaneous Charges Order

DocumentNumber Optional. 13 digit document number, maximum of 16 digits. All transaction types associated to the document requested will be returned. If a ticket was issued and subsequently refunded both ticket and refund would be displayed. If requesting a document from a branch location the branch PCC will need to be included in the request. It is recommended when requesting by document number to not include any other search criteria.



3.2 DailySalesSummaryRS

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

3.2.1 Common RS Attributes

Element Description

Version Web Service Version client is using.

isQueryStillRunning

reportId

chunkNumber

maxChunks

These attributes can be returned in any <report>RS.

In some cases the web service transaction may time-out before the requested report can be returned. In this scenario the system will send a response back before the transaction time-out indicating the report is going to be Late by setting <isQueryStillRunning>=true along with a unique <reportId>. Once the system completes the query it will cache the report in the database allowing the client at a later time to request the report using CachedReportRQ.

In some cases a report may be considered too large to return in one XML document and the system will break it up into chunks. In this scenario the system will send a response back including <reportId>, <chunkNumber> and <maxChunks>. The client can then request each chunk using CachedReportRQ.

Suggested size limit is 10MB

messageID Unique transaction ID generated by Ticket Web Services

timeStamp The time stamp of the transaction



3.2.2 Common RS Header Attributes

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

Element Description

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

DSHeader Describes data contained within the whole report.

DailySalesReport Daily Sales Summary report

Diagnostic Internal use only



3.2.3 Common RS Header Elements


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

ConversationID The ConversationID element is a string identifying the set of related messages that make up a conversation between two Parties. The Party initiating a conversation determines the value of the ConversationID element that shall be reflected in all messages pertaining to that conversation. It remains constant for all messages within a conversation.

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 OchestrationID@seq value if it exists.

Operation Operation is the action verb applied to the Service

Service The name of the service being requested. Typically the message subject noun. Service frameworks may use the abstract service name to lookup the actual service provider instance to invoke.

Messaging Messaging section provides an area for each system interacting with the message to record a brief message about their interactions. Service proxies and utility services such as transformation and validation should use this area to record when they processed the message and the



resulting station.

Parameters Generalized name-value pairs. These parameters are intended for integration specific use only during development and testing. These parameters must not be relied upon for production operation

Security

3.2.4 DailySalesSummarRS header

Element Description

PseudoCityCode PseudoCityCode of the requesting agency

AgencyName Agency Name



3.2.5 DailySalesSummaryRS Elements

Element Description

ReportDate Date the report was generated

Transaction Audit Trail details about the document

TotalDailySales Summary of Totals based on Transaction, Settlement and payment type



3.2.5.1 Transaction attributes and elements


nonInteractive Indicated if the document was issued as a non-interactive ticket

electronicDocument Indicated if the document was an Electronic ticket

Itinerarytype Domestic (D) or International (I) indicator based on the itinerary



Element Description

DocumentType Available response based on the RQ is TKT, EMD, RFND, RFEMD, MCO.

Only one document type is permitted in the request. If document type was not entered then all transaction types will be returned in the response.

Code Form Type

TKT Ticket - Any Sale transaction

EMD Electronic Miscellaneous Document

RFND Refund documents

RFEMD Refunded EMD documents

MCO Miscellaneous Charges Order

SettlementType Report data will be limited to the settlement type specified. Available options for this are: TAT, TCH, TKT, STA or KIL

Only one settlement type is permitted in the request.

If settlement type is not entered all data regardless of settlement type will be returned in the response.

If both DocumentType and SettlementType are used in the request then the following error will be sent in the response.

XML request schema validation failed: DocumentType and SettlementType fields are conflicting. Only one of them can be used. Please amend your request and try again

PnrLocator 6 alpha PNR locator for the document.

PassengerName Full name of the passenger

DocumentDetails Contains the details of the document

DocumentNumber – 13 numeric ticket number

LastConjunctiveDocumentNumber – 13 numeric ticket number of the last conjunctive document.

StockType – The stock type used for issuing the document. Ex. AT, AB, GB, 1Y

StockDetails o StockControlNumber – 10 or 13 numeric o LastStockControlNumber – 10 or 13 last conjunctive stock

control number o PrinterLniata - This is the LNIATA of the agent who issued

the ticket o CouponType –

C - CHARGE FORM



T - AGENT COUPON

A - AUDITORS COUPON

F - FLIGHT COUPON

P - PASSENGER RECEIPT

B - BOARDING PASS ONLY /ARC ONLY/

S - MISCELLANEOUS DOCUMENTS TOUR ORDER

E - EXCHANGE COUPON FOR MISC TKT DOCS MCO

DocumentStatusCode

A - Additional collection

E - Even exchange

N - Net remit ticket

P - Printed flight coupons from etkt

R - Regenerated coupons from etkt

SF - Selling fare

V - Void transaction

X – Cancel Refund

TransactionCode SALE – original sale document RFND – refunded document CNCL – No PNR void

AirlineCode 2 alpha airline code or 3 numeric airline code

Commission Commission collected for the document

Amount o amountText o decimalPlace

Percent

Amount and/or Percent are populated based on what was entered at the time of ticketing.

For tickets issued with a Percentage value then both the percent and amount fields will have values.

For EMDs issued with a Percentage value then only the percentage value will be populated and amount element will not be shown.

Commission element will not appear if no commission was entered.

Payments Optional

Payment Information

CurrencyCode

DocumentPayment o PaymentTotal o PaymentDetail

Attributes



Fop – form of payment used in the transaction

category (a secondary payment category is

a denotation of how that fop - which can be

something other than CA or CC - gets

calculated. cardType

PaymentAmount

amountText

decimalPlace

Fees o FeeDetail

feeType cardType amountText decimalPlace

AgentSine 3 character alpha-numeric sine of the agent performing the transaction.

AgencyPseudoCity Optional.

Pseudo city of the agent performing the transaction.

TransactionDate Time The date and time of the transaction.

Payment examples illustrating fop and category usage:

Misc Cash - PAYMNT_INSTMNT_TYP_CD = MS , MISC_PAYMNT_INSTMNT_TYP_CD = CA

<ns2:PaymentDetail fop="MS" category="CA">

Misc Credit - PAYMNT_INSTMNT_TYP_CD = MS , MISC_PAYMNT_INSTMNT_TYP_CD = CC

<ns2:PaymentDetail fop="MS" category ="CC">

Cash - PAYMNT_INSTMNT_TYP_CD = CA , MISC_PAYMNT_INSTMNT_TYP_CD = CA

<ns2:PaymentDetail fop="CA" category="CA">

Credit - PAYMNT_INSTMNT_TYP_CD = CC , MISC_PAYMNT_INSTMNT_TYP_CD = CC

<ns2:PaymentDetail fop="CC" category ="CC">

Government - PAYMNT_INSTMNT_TYP_CD = GT , MISC_PAYMNT_INSTMNT_TYP_CD = CC

<ns2:PaymentDetail fop="GT" category ="CC">

Other - PAYMNT_INSTMNT_TYP_CD = XX , MISC_PAYMNT_INSTMNT_TYP_CD = CA

<ns2:PaymentDetail fop="XX" category ="CA">



3.2.5.2 TotalDailySales attributes and elements


TransactionType TransactionCode

SALE – original sale document

RFND – refunded document

CNCL – No PNR void

SalesBySettlement Sales totaled by SettlementType for a particular transaction



3.3 Duplicated Document Numbers

If a document number is duplicated in the Sabre database the latest document is returned.

3.4 DailySalesSummaryRQ/RS Examples

3.4.1.1 RQ

<DailySalesSummaryRQ

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

version="1.2.0">

<Header />

<SelectionCriteria>

<PseudoCityCode>WD40</PseudoCityCode>

<Airline>

<AirlineNumber>607</AirlineNumber>

</Airline>

<ReportDate>2016-06-08</ReportDate>

<DocumentType>RFEMD</DocumentType>

</SelectionCriteria>

</DailySalesSummaryRQ>

SettlementType Report data will be limited to the settlement type specified. Available options for this are: TAT, TCH, TKT, STA or KIL

Only one settlement type is permitted in the request.

If settlement type is not entered all data regardless of settlement type will be returned in the response. Each settlement type will be totaled separately.

SalesTotals Totals for all transactions for a currency. If multiple currencies exist in the sales report then totals will be listed for per currency.

CurrencyCode

CashTotals o amountText o decimalText o count

CreditTotals o amountText o decimalTest o count

CommissionTotals o amountText o decimalTest o count

RQ with Selection

Criteria



3.4.1.2 RS

<asr:DailySalesSummaryRS

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

version="1.2.0" isQueryStillRunning="false">

<asr:Header messageID="TKTHLI701-31273-116967508-1465924946348-

19928-asrwsDqb">

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

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

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

xmlns:ns4="http://schemas.xmlsoap.org/soap/envelope/"

seq="0">TKTHLI701-31273-116967508-1465924946348-19928-

asrwsDqb</OrchestrationID>

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



xmlns:ns4="http://schemas.xmlsoap.org/soap/envelope/">

<Success>

<System>T2-ASR</System>

</Success>

</Results>

</asr:Header>

<ns2:DSHeader


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



<ns2:PseudoCityCode>WD40</ns2:PseudoCityCode>

<ns2:AgencyName>ADELMAN TRAVEL</ns2:AgencyName>

</ns2:DSHeader>

<ns2:DailySalesReport


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



<ns2:ReportDate>2016-06-08</ns2:ReportDate>

<ns2:Transaction itineraryType="I" electronicDocument="true"

nonInteractive="false">

<ns2:DocumentType>RFEMD</ns2:DocumentType>

<ns2:SettlementType>TKT</ns2:SettlementType>

<ns2:PnrLocator>UAJPZI</ns2:PnrLocator>

<ns2:PassengerName>THOMAS/AMBERCOMBIE</ns2:PassengerName>

<ns2:DocumentDetails>

<ns2:DocumentNumber>6074571751338</ns2:DocumentNumber>

<ns2:StockType>AT</ns2:StockType>

<ns2:DocumentStatusCode>R</ns2:DocumentStatusCode>

<ns2:TransactionCode>RFND</ns2:TransactionCode>

</ns2:DocumentDetails>

<ns2:AirlineCode AirlineNumber="607">EY</ns2:AirlineCode>

<ns2:Payments>

<ns2:CurrencyCode>USD</ns2:CurrencyCode>

<ns2:DocumentPayment>

<ns2:PaymentTotal>10.00</ns2:PaymentTotal>



<ns2:PaymentDetail miscFop="CA" fop="CK">

<ns2:PaymentAmount decimalPlace="2"

amountText="10.00">10.00</ns2:PaymentAmount>

</ns2:PaymentDetail>

</ns2:DocumentPayment>

</ns2:Payments>

<ns2:AgentSine>ATW</ns2:AgentSine>

<ns2:AgentPseudoCity>WD40</ns2:AgentPseudoCity>

<ns2:TransactionDateTime>2016-06-

08T21:11:00.000</ns2:TransactionDateTime>

</ns2:Transaction>

<ns2:TotalDailySales>

<ns2:TransactionType>RFND</ns2:TransactionType>

<ns2:SalesBySettlement>

<ns2:SettlementType>TKT</ns2:SettlementType>

<ns2:SaleTotals>

<ns2:CurrencyCode>USD</ns2:CurrencyCode>

<ns2:CashTotals count="1" decimalPlace="2"

amountText="10.00">10.00</ns2:CashTotals>

<ns2:CreditTotals count="0" decimalPlace="2"

amountText="0.00">0</ns2:CreditTotals>

<ns2:CommissionTotals count="0" decimalPlace="2"

amountText="0.00">0</ns2:CommissionTotals>

</ns2:SaleTotals>

</ns2:SalesBySettlement>

</ns2:TotalDailySales>

</ns2:DailySalesReport>

</asr:DailySalesSummaryRS>

TN GetTicketingDocument Troubleshooting


4 Troubleshooting

4.1 Introduction

When reporting an issue with Web Services, please make sure to provide full XML payload (request and response) or, if it is not possible, at least transaction ID in order to troubleshoot the problem.

Later in this document you will find the examples of common error responses that may help you identify the cause of issue and solve the problem.

4.2 DQBWS Communication points

The steps in Daily Sales Summary Web Service operation are:

Validation of incoming requests against the STL XSD schemas published on Sabre Dev Studio.

Validation with the ICE/ESSM system whether the request comes from the user authorized to use GetTicketingDocument Web Service.

Conversion of XML requests to PSS (Passenger Service System or Sabre host) binary format.

Sending requests to PSS/T2 DMS via MOM (Message Oriented Middleware). MOM infrastructure is based on Message Queue (MQ) technology to handle transaction communication.

Receiving binary response from PSS via MOM.

Converting PSS binary response to XML response.

Providing throttling to reduce negative impact of heavy loads on Ticketing Web Services and subsystems.

If any of these communication points experience a failure, it results in an XML error response returned to the TKT_AsrServices Web Service client.

4.3 Common Error Responses, Reasons and Solution

This section provides examples of common error responses you might come across using DailySalesSummaryRQ Web Service together with the reasons and tips on how to resolve these problems.

4

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



4.3.1.1 USG Authentication Errors

This type of error is returned when authorization to access Web Services fails for user.

Error:

<soap-env:Fault><faultcode>soap-

env:Client.AuthorizationFailed</faultcode><faultstring>Authorization

failed</faultstring><detail><StackTrace>com.sabre.universalservices.ba

se.security.AuthorizationException:

errors.authorization.USG_AUTHORIZATION_FAILED</StackTrace></detail></s

oap-env:Fault>

Reason:

Unauthorized access to the DailySalesSummaryRQ.

Solution:

Before accessing DailySalseSummaryRQ Web Service, USG session needs to be created and correct ICE credentials passed over in XML request. Please make sure requestor has keyword OpenSystemsUser.

4.3.1.2 USG Invalid Security

Error:

<faultcode>soap-env:Server.SystemFailure</faultcode>

<faultstring>Unable to connect to ICE security system :

606</faultstring>

<detail>

<StackTrace>com.sabre.universalservices.base.exception.Application

ICEException:

errors.authentication.USG_SECURITY_ICE_ERROR</StackTrace>

</detail>

</soap-env:Fault>

</soap-env:Body>

</soap-env:Envelope>

Reason:

Unauthorized access to the DailySalesSummaryRQ.

Solution:

Before accessing DailySalseSummaryRQ Web Service, USG session needs to be created and correct ICE credentials passed over in XML request. Please make sure requestor has keyword OpenSystemsUser.

4.3.1.3 No Branch Access

Error:

<DailySalesSummaryRS


isQueryStillRunning="false" version="1.2.0">

<Header messageID="TKTHLI702-15647-1735448981-1465927172478-268-

asrwsDqb" timeStamp="2016-06-14T12:59:32">



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

seq="0">TKTHLI702-15647-1735448981-1465927172478-268-

asrwsDqb</STL:OrchestrationID>

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

<STL:Error status="NotProcessed" timeStamp="2016-06-14T12:59:32"

type="Validation">

<STL:Source>ASR WS</STL:Source>

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

<STL:SystemSpecificResults>

<STL:ErrorMessage code="45100">Request security validation

failed: Agent is not authorized to access the requested

location</STL:ErrorMessage>

<STL:ShortText>Request security validation

failed</STL:ShortText>

</STL:SystemSpecificResults>

</STL:Error>

</STL:Results>

</Header>

</DailySalesSummaryRS>

Reason:

User PCC does not have permission to retrieve from PCC provided in the search – security authorization failed.

Solution:

Verify if the values of search parameters fields are correct and if needed, amend them and try again. If you need additional assistance, use your provided Sabre Web Services contacts. If you are unsure, contact your Sabre Account Director. Please remember to provide your user ID, domain, organization and environment you use.

4.3.1.4 Invalid Service Version Specified in XML Request

Error:







<STL:Error status="NotProcessed" timeStamp="2016-06-14T12:34:38"

type="Validation">




<STL:ErrorMessage code="21212">Invalid service version

specified in XML request: XML schema version 0.0.0 is not

supported</STL:ErrorMessage>

<STL:ShortText>Invalid service version specified in XML

request</STL:ShortText>


</STL:Error>

</STL:Results>



</Header>


Reason:

The XML request sent uses unsupported version of schema.

Solution:

Send the request in one of the supported schema versions. If you need additional assistance, use your provided Sabre Web Services contacts. If you are unsure, contact your Sabre Account Director.

4.3.1.5 Request XML Validation Failed Against Schema

Error:






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

seq="0">TKTHLI701-31273-116967508-1465925763020-20469-

asrwsDqb</STL:OrchestrationID>


<STL:Error status="Incomplete" timeStamp="2016-06-14T12:36:03"

type="Validation">




<STL:ErrorMessage code="21208">XML request schema validation

failed: The value in DocumentType field (or one of its attributes) is

not valid: 'RFEMDa' is not a valid value for

'Code.DocumentTypeForTNReports'. Please amend your request and try

again.</STL:ErrorMessage>

<STL:ShortText>XML request schema validation

failed</STL:ShortText>


</STL:Error>

</STL:Results>

</Header>


Reason:

The XML request sent doesn’t match the DailySalesSummaryRQ schema. The input parameters provided in the search are invalid.

Solution:

Verify XML request with schema version you used and correct it. If you need additional assistance, use your provided Sabre Web Services contacts. If you are unsure, contact your Sabre Account Director.

Date post:	29-Jul-2018
Category:	Documents
Upload:	doandiep
View:	213 times
Download:	0 times

Software version 2016 -...

Documents