Sabre Schedule Change Web Service User Guide
Sabre Travel NetworkSabre Schedule Change Web Service User GuideEdition 1June 12, 2017Document Edition 1.0 updated 6/12/2017 5:05 PMThis documentation is the confidential and proprietary intellectualproperty of the Sabre business. Any unauthorized use,reproduction, preparation of derivative works, performance ordisplay of this document or software represented by this document,without the express written permission of Sabre is strictlyprohibited.Sabre and the Sabre logo are trademarks and/or service marks. Allother trademarks, service marks and trade names are the propertyof their respective owners. 2017 Sabre Inc. All rights reserved.Sabre Schedule Change Web Service User GuidevTable of ContentsConfidential and Proprietary Sabre Travel Network
Table of Contents1Introduction1.1 Overview . 61.2 Purpose of this Guide . 61.3 XML Examples in this Document . 71.4 Access Conditions. 71.5 Sabre Dev Studio . 71.6 Schedule Change WSDL file . 72Understanding the Sabre Schedule Change Web Service2.1 Introduction . 82.2 Prerequisites . 82.3 Requirements . 82.3.1 Eligible Documents . 82.3.2 The Sabre Schedule Change Even Exchange Process . 92.3.2.1 Fulfill Request . 93Sabre Schedule Change Web Service Request3.1 Introduction . 103.2 Request Attributes. 103.3 Request Elements . 103.3.1 POS Elements . 113.3.1.1 Number of the Ticketing Document . 113.3.1.2 Options . 113.3.1.2.1 Options Elements . 123.4 Sabre Schedule Change Web Service Request Examples . 133.4.1 Example Request to Fulfill a basic Schedule Change Even Exchange with No AdditionalOptions . 133.4.2 Example Request to Fulfill a Schedule Change Even Exchange with additional options . 144Sabre Schedule Change Web Service ResponseSabre Schedule Change Web Service User GuideviTable of ContentsConfidential and Proprietary Sabre Travel Network
4.1 Introduction . 164.2 Response Attribute. 164.3 Response Elements . 164.3.1 Header . 164.3.2 Results elements . 174.3.2.1 Error elements . 175Troubleshooting5.1 Introduction . 205.2 List of Error Messages . 205.3 Example of Error Responses . 225.3.1 USG Authentication Errors. 225.3.1.1 Security Violations . 235.3.1.1.1 No Branch Access. 235.3.2 Timeout . 235.3.3 Throttled Request/Response . 245.3.4 Invalid service version . 255.3.5 Invalid Request XML Format . 255.3.5.1 Request XML Validation Failed Against Schema . 255.3.6 Database Response: Not Found. 265.3.7 Hardcopy printer not assigned . 27Sabre Schedule Change Web Service User GuideivTable of ContentsConfidential and Proprietary Sabre Travel Network
Sabre Schedule Change Web Service User Guide v Table of ContentsConfidential and Proprietary Sabre Travel Network
11Introduction1.1OverviewA new Web service has been developed to deliver the functionality of the Sabre Schedule Changeproduct. This Web service provides a quick and easy way for Sabre users to perform an even exchangetransaction after processing a planned airline schedule change.The Web service will copy all the fare and tax details from the old ticket and automatically transfer thosedetails to the new ticket. Additionally, the following elements will be added to the ticket resulting fromthe schedule change exchange:-“SKCHG” at the beginning of the endorsement field“I-“ at the beginning of the fare calculation line to indicate an involuntary exchangeIn addition, the Web service will allow the service request and response to optionally add a tour code,additional endorsement text and commission in order to comply with specific airline instructions oragency needs.If you do not wish to the resulting ticket to have “SKCHG” at the beginning of the endorsement field and“I-“ at the beginning of the fare calculation line, then this Web service should not be used. In these cases,an alternate method to perform the exchange transaction should be used.The Web service can be used by XML based web sites, online travel agencies, front end GUI Webservices, and mobile applications.This product is available as a new operation within an existing service, TKT ExchangeRefundRQ version1.2.0, using ExchangeRQ .The details of the new operation’s process will be described in following sections.Note1.2To process a planned airline schedule change, the travel agency modifies the PNR to accept thenew itinerary, and advise the airline that the new flight information has been communicated to thepassenger and remove the old flight information. The Web service described in this documentdoes not perform this process, but rather performs an even exchange transaction after that processhas been completed.Purpose of this GuideThe purpose of this guide is to introduce the Sabre Schedule Change Web service. It is not a completereference tool for XML design. Developers should refer to the Sabre Dev Studio for the most completeinformation. You can find instructions on how to access the Sabre Dev Studio in section 1.5 of thisguide.This guide provides: A description of the Web service features Examples of typical planned airline schedule change scenarios and associated even exchangeticketing transactionsSabre Schedule Change Web Service User Guide6Confidential and Proprietary Sabre Travel Network
Examples of requests and responses for Sabre Schedule Change even exchange transactions Common error messages that may be returned by the service along with the explanation as to whythey occur and ways for fixing the problem where applicable1.3XML Examples in this DocumentThe purpose of the XML examples provided in this document is to present possible content of the requestand response.Note: Examples are for illustrative purposes only.1.4Access ConditionsThe Sabre Schedule Change Web service is a billable product. For additional information or to requestactivation, please contact your Sabre Account Director.The following applies: 1.5Access is based on Employee Profile Record (EPR).All EPR groups should be auto provisioned with the required OpenSystemUser attribute and noadditional security provisioning is required.Sabre Dev StudioThe repository for all Sabre Web service information can be found at Sabre Dev Studio.Here you can find documentation including schemas, WSDL files, code samples, workflows, and SabreWeb services related information.Sabre Dev Studio is the most comprehensive reference tool available for XML developers.Please visit the site and register for an account if you have not done so already.1.6Schedule Change WSDL fileThe WSDL file provides a description of the basic formats of Web service requests – how the service canbe called, what parameters it expects, and what data structures it returns.For the latest available links to WSDL files, check the Schedule Change documentation on the Sabre DevStudio.Sabre Schedule Change Web Service User Guide7Confidential and Proprietary Sabre Travel Network
2Understanding the Sabre ScheduleChange Web Service2.12IntroductionThis chapter provides a description of the Sabre Schedule Change Web service for even exchangetransactions. It provides information about types of transactions that the service supports, prerequisitesand the Schedule Change process.This Web service adds new functionality to the TKT RefundExchange XML schema already publishedon Sabre Dev Studios. To utilize the Sabre Schedule Change Web service, you must useTKT RefundExchange version 1.2.0 or higher.2.2PrerequisitesFollowing are the prerequisites for using the Sabre Schedule Change Web service: Sabre Schedule Change must be active for the market in which the subscriber operates Sabre Schedule Change must be activated for the subscriber’s PCC - the subscriber must have theSCFP TJR setting activated by the Sabre Help Desk Have a client to consume the Web service, either Sabre Red Workspace or one that has beendeveloped for your agency Have downloaded all the necessary files from Sabre Dev Studio2.3RequirementsThe following information provides the rules and applicability of Sabre Schedule Change.2.3.1Eligible DocumentsThe Sabre Schedule Change Web service can be used for performing even exchanges for tickets whichmeet the following criteria: The ticket must be an original issue electronic ticket or a previously exchanged electronic ticket The ticket must be in both the Sabre ticket database and the airline carrier’s ticket database The ticket must have at least one coupon with OPEN or ACTL status and available for exchangeThe Sabre Schedule Change Web Service may not be used for: Paper tickets Net remit ticketsSabre Schedule Change Web Service User Guide8Confidential and Proprietary Sabre Travel Network
2.3.2The Sabre Schedule Change Even Exchange ProcessThis section provides a brief description of the Schedule Change process.2.3.2.1 Fulfill RequestThe following is a brief description of the Sabre Schedule Change Web service workflow: The Web service client makes a request call which includes the minimum elements to fulfill therequest, and any additional optional elements. The system will perform validations to determine if the existing ticket is exchangeable and ifsuccessful, the new ticket document will be created in the same manner as all other tickets createdwithin Sabre. The ticket will be simultaneously transmitted to the airline carrier(s) involved in theticketed itinerary. The new ticket will include all the fare and tax details from the old ticket, as wellas “SKCHG” first in the endorsement, and “I-“ preceding the original ticket fare calculation.The exchange transaction is treated like any other even exchange transaction and the data will be sentto the settlement plan, and the PNR will be updated. Optionally, based on TJR settings the PNR maybe ended, ended and retrieved or not ended at all. The Web service response will include a response element to indicate that the transaction wassuccessful. If any errors are detected at any point, the process will be interrupted and the appropriate errormessage returned in the response.Sabre Schedule Change Web Service User Guide9Confidential and Proprietary Sabre Travel Network
3Sabre Schedule Change Web ServiceRequest3.13IntroductionThe purpose of this chapter is to briefly explain the content of the ExchangeRefundRQ/RS XML schemaas it pertains to Sabre Schedule Change Web service functionality.This chapter should not be treated as complete information about the ExchangeRefundRQ/RS XMLschema, but can be used as additional source of information for the ExchangeRQ definition available inthe Sabre DEV Studio.There are items in the TKT ExchangeRefundRQ XML schema not used for schedule change evenexchanges. This guide only covers those items applicable to ExchangeRQ.3.2Request AttributesFollowing is the request attribute for ExchangeRQ:AttributeDescriptionSchedule Change PathExchange RQversionRequired in the XML schema.ExchangeRQ/@version3.3Request ElementsFollowing are the top level request elements:ElementDescriptionSchedule Change PathHeaderStandard header information that helps orchestratethe requestsExchangeRQ/HeaderPOSInformation about the point of sale and the agentperforming the Schedule Change n about the ticket to be exchangedExchangeRQ/TransactionInfoOptionsUp to 5 optional elements may be included inExchangeRQExchangeRQ/TransactionInfo/OptionsThe POS element and the TransactionInfo element are detailed in the following sub sections:Sabre Schedule Change Web Service User Guide10Confidential and Proprietary Sabre Travel Network
3.3.1POS ElementsFollowing is the list of elements identifying the Point of Sale in a Schedule Change even exchangetransaction. They are optional in the XML schema; however, their presence is verified by the servicebusiness validation layer. Although optional elements, the Company and Pseudo elements are requiredfor Schedule Change even exchange transactions.ElementDescriptionExampleSchedule Change PathCompanyThe IATA id assigned code of theGDS - it will be one of the threefollowing seudo1S for Sabre1B for Sabre APAC1F for INFINIPseudoFour-digit home pseudo city of theagent3.3.1.1 Number of the Ticketing DocumentThe ticketing document number is the only required element. It can be in the request as the actual 13 digitticket number or by the ticket reference number in the PNR.ElementDescriptionExampleSchedule Change PathTicketingDocument/Number13 digit document number to /TicketingDocument/NumberTicketingDocument1-2 digit document referencenumber from the PNR to Reference3.3.1.2 OptionsThe Options elements allow the user to include secondary information in the request that is important forproper construction of the new ticket, per airline or agency requirements. Multiple options can be addedin a single request, but each option can only be present once per noEndorsementSabre Schedule Change Web Service User Guide11Confidential and Proprietary Sabre Travel Network
3.3.1.2.1Options ElementsElementDescriptionExampleSchedule Change PathPNRSelect/NameName number from the PNR.Used once per /NamePNRSelect/SegmentSegment number from thePNR. Element is used for eachsegment. Used 1-16 times insingle egmentCommissionAmount of commission. Usedonce per onTourCodeA tour code to be applied to theschedule change evenexchange. Used once per odeEndorsementAn Endorsement to be appliedafter “SKCHG” and before theendorsement from the originalticket. Used once per RQ./Free TextExchangeRQ/TransactionInfo/Options/Endorsement PNRSelect:o Name - When only one person is in the PNR, the PNRSelect/Name option is notnecessary. When more than one person is in the PNR, the PNRSelect/Name option isrequired.oSegment Select – Segment Select only needs to be used if, when the original ticket wasissued, segment selection was used to ticket only certain flight segments in the PNR (andthe other flight segments in the PNR were issued on a different ticket).In these cases, the segment options should be used to reference the proper segmentsneeding to be exchanged, which may or may not be the same segment numbers as thesegments that were selected when the original ticket was issued. Commission Amount – The commission option may be used in the request, however this shouldonly be done if instructed by the carrier to do so. An agency could receive a debit memo ifcommission is entered on an even exchange transaction, without permissionoFor ARC locations, the commission amount from the original ticket will automatically beused in processing the exchange (unless a new commission amount is requested as part ofthe fulfillment request). This is to ensure that ARC’s unique reconciliation process is notdisrupted.oFor BSP and other settlement plan locations, the commission amount on the exchangeticket will default to zero.oNote that certain markets do not support commission amount. If a commission amount isused when it is not supported an error response will be returned.Sabre Schedule Change Web Service User Guide12Confidential and Proprietary Sabre Travel Network
Tour Code – If a tour code exists on the original ticket, it will be automatically carried over tothe new ticket resulting from the Schedule Change even exchange, however, a new tour code maybe requested as part of the fulfillment request. If a new tour code is included in the request, it willreplace the tour code from the original ticket when the new ticket is constructed.The only exception would be if the original ticket is a CAT 35 Net/Selling type of fare with a tourcode. In this case, the tour code for these types of fares cannot be replaced. If a CAT 35 fare hasan existing tour code on the original ticket, and a new tour code is requested in the Fulfillmentrequest, the new tour code will be ignored and the original CAT 35 tour code will appear on thenew ticket that results from the Schedule Change even exchange. Endorsement – Additional optional endorsement data can be included in the request. Thisoptional endorsement will appear on the new ticket after the automatic addition of “SKCHG”, butbefore any endorsements from the original ticket being exchanged.It is strongly recommended that users activate the LRGEND TJR option prior to using the SabreSchedule Change Web service. Doing so expands the endorsement area of the ticket to 999characters.3.4Sabre Schedule Change Web Service Request ExamplesThis section contains schedule change even exchange examples, including examples showing the optionsfrom section 3.3.2.2. The Sabre host view of the tickets to be exchanged are supplied for reference:3.4.1Example Request to Fulfill a Basic Schedule Change EvenExchange with No Additional OptionsTicket to be exchanged:SABRE TICKET :14DEC2016SYD PCC:A4S1 1*XXXX/556MCPN A/L FLT CLS DATEBRDOFF TIME ST F/BSTAT1VA943 V 20FEB SYDBNE 1300 OK VZEV0OPEN2VA950 V 25FEB BNESYD 1305 OK VZEV0OPENFARETOTALAUD360.38 TAXAUD438.0039.82UOTAX7.50WGTAX30.30QRCOMM: 36.04SYD VA BNE180.19VA SYD180.19AUD360.38ENDENDORSEMENT/RESTRICTION:Sabre Schedule Change Web Service User Guide13Confidential and Proprietary Sabre Travel Network
NONREF/RESTRICTIONS APPLY/NONEND/PENALTIES APPLYXML to request to fulfill an even exchange (due to a planned airline schedule change) of this ticket: ExchangeRQ version "1.2.0"xmlns 1.0"xmlns:STL "http://services.sabre.com/STL/v01"xmlns:xsi emaLocation 1.0" POS STL:Company 1S /STL:Company STL:Pseudo WD40 /STL:Pseudo /POS TransactionInfo PNR TicketReference 3 /TicketReference /PNR Options PNRSelect Segment 1 /Segment /PNRSelect /Options /TransactionInfo /ExchangeRQ 3.4.2Example Request to Fulfill a Schedule Change Even Exchangewith Additional OptionsThe following is the request to fulfill an even exchange (due to a planned airline schedule change) of aticket this time with options.Below is the Sabre host presentation of the ticket being exchanged.WTDB*2«SABRE TICKET 921640907ISSUED:05JUN2017MKE PCC:WD40 IATA:52812874NAME:KENNEDY/HENRYFOP:CASHCPN A/L FLT CLS DATEBRDOFF TIME ST F/BSTAT1AF1581 Y 23JUL LHRCDG 1150A OK Y3WK0GB9EXCH2AF1780 Y 30JUL CDGLHR 125P OK Y3WK0GB9EXCHFARETOTALGBP508.00 TAX 16.70GB TAX 31.80UBTAX 14.10QX TAX 1.30IZUSD737.20EQUIV FARE PDTAX19.30FRUSD654.00COMM: 1.11REFUND/CHANGE/RESTRICTIONS APPLYLON AF PAR309.86AF LON309.86NUC619.72END ROE0.819712Sabre Schedule Change Web Service User Guide14Confidential and Proprietary Sabre Travel Network
Below is the Web service request for the Schedule Change even exchange transaction. ExchangeRQ version "1.0.0"xmlns 1.0"xmlns:STL "http://services.sabre.com/STL/v01"xmlns:xsi emaLocation 1.0" POS Company 1S /Company Pseudo WD40 /Pseudo POS TransactionInfo PNR TicketReference 2 TicketReference PNR Options Commission 2.22 Commission PNRSelect Name 1.1 Name Segment 1 Segment Segment 2 Segment PNRSelect TourCode ABC123 TourCode Endorsement /SPECIAL ENDORSEMENT Endorsement Options TransactionInfo /ExchangeRQ Sabre Schedule Change Web Service User Guide15Confidential and Proprietary Sabre Travel Network
4Sabre Schedule Change Web ServiceResponse4.14IntroductionThis section describes business specifics of the Schedule Change even exchange response. It is notintended to supply information of all the elements and attributes. For complete information, please referto schema documentation in Sabre Dev Studio. Examples of responses are include in the scenarios insection 4.2.3. Error! Reference source not found.The Schedule Change response consists of the following attributes and elements.4.2Response AttributeAttributeDescriptionSchedule Change PathExchangeRS versionRequired in the XML schema?ExchangeRS/@version4.3Response ElementsElementDescriptionSchedule Change PathHeaderInformation indicating the result of theservice call, orchestration and transactionidentifiers, errors, and warnings.ExchangeRS/HeaderTransactionInfoContains the text of the message and amessage type t from the message ID and orchestration and transaction identifier the header also contains a Resultselement which contains business messages warnings and errors.ElementDescriptionSchedule Change PathOrchestration IDInformation indicating the result of theservice call, orchestration and transactionidentifiers, errors, and warnings.ExchangeRS/Header/Orchestration IDResultsSuccess, Warnings and ErrorsExchangeRS/Header/ResultsSabre Schedule Change Web Service User Guide16Confidential and Proprietary Sabre Travel Network
4.3.2Results elementsThe results element has two elements that contain the success of the transaction as well warning or errors.The success and Error elements are mutually exclusive, i.e. you can only have one of them in a response,not both.ElementDescriptionSchedule Change PathSuccessContains elements identifying the source(ExchangeServices) and the system (T2).ExchangeRS/Header/Results/SuccessThe success element will be present if theexchange request has been successfulErrorContains elements identifying the source(ExchangeServices) and the system (T2)as well as an element containing the errormessage texts. The error element will bepresent if an error condition has beenencountered and the exchange transactionhas not been successful.ExchangeRS/Header/Results/Error ExchangeRS xmlns:ns2 1.0"xmlns "http://services.sabre.com/STL/v01"version "1.2.0" Header messageID x"timeStamp "2017-06-02T16:22:00.000" OrchestrationID seq "0" TKTHLI700-25800-1014271083-1496438538320-3082arex /OrchestrationID Results Success System TKT-DS /System Source AREX /Source /Success /Results Header TransactionInfo reservationAutoEndProcessed "false"reservationAutoRetrieveProcessed "false" 4.3.2.1 Error elementsThe error elements will contain the SystemSpecificResults element that provides information about thewarning or error. This element has a number of sub elements. Only the following are used for ScheduleChange:ElementDescriptionExampleSchedule Change PathErrorMessageContains the text of themessage and a message codeattributeCOUPONS NOTQUALIFY pecificResults/ErrorMessageSabre Schedule Change Web Service User Guide17Confidential and Proprietary Sabre Travel Network
ElementDescriptionExampleSchedule Change PathShortTextContains text which identifiesthe category of the error.Decimal CheckValidationExchangeRSExchangeRS extErrorMessage AttributeThe ErrorMessage element has one attribute to uniquely identify the warning or error.AttributeDescriptionSchedule Change PathcodeUnique code of the error or temSpecificResults/ErrorMessage@codeA table with possible error messages and codes is given in section 5.2Examples of error responses is provided in section 5.3TransactionInfo elementsElementDescriptionExamplesSchedule Change PathMessageThese transaction messageswill only be present when theexchange has beenprocessed.OK 1860.88ExchangeRS/TransactionInfo/MessageETR EXCHANGEPROCESSEDOK 6.6AttributeDescriptionSchedule Change PathtypeType of message. For ScheduleChange, this will always be “I” typeSabre Schedule Change Web Service User Guide18Confidential and Proprietary Sabre Travel Network
Sabre Schedule Change Web Service User Guide19Confidential and Proprietary Sabre Travel Network
55Troubleshooting5.1IntroductionThis section provides a list of error messages and their causes as well as examples of some of them.There are a few steps that the Sabre Schedule Change Web service makes during transaction processingand, on each of these steps, an error message will be returned if the system detects the problem.These steps are: Determine that a PNR is present in the user’s Sabre session Determine if a hardcopy printer and ticket printer have been designated Validation that the ticket number in the RQ exists both in the airline carrier’s database and the SabreTicket Database Verifying that the electronic ticket coupons being exchanged are eligible for ticketing Verifying that no more than 16 air segments are being presented for ticketing Validation that the default currency of the user attempting the exchange transaction matches thecurrency that the original ticket was issued in Validation that only air segments are being pr
Sabre Schedule Change Web Service User Guide 6 Confidential and Proprietary Sabre Travel Network 1 Introduction 1.1 Overview A new Web service has been developed to deliver the functionality of the Sabre Schedule Change product. This Web service provides a quick and easy way for Sabre users to perform an even exchange transaction after processing a planned airline schedule change.
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.
If the user ID uses the Sabre global distribution system (Sabre system), it also uses Sabre sessions (remember that Sabre sessions are synonymous with TAs). When a client creates a Sabre APIs connection, a Sabre session is allocated simultaneously by the infrastructure for this type of user ID. Most user IDs fall into this category.
Guide to Accessing and Consuming SOAP-Based Services, v1.42 Page 9 Sabre Confidential SOAP-Based Sabre APIs Resources The following resources are all available via the Sabre Dev Studio, located at . SOAP-Based Sabre APIs Documentation Each Web service has an artifact on the Sabre Dev Studio. Each artifact contains: A request design document
Sabre Web Services Errors Sabre Web Services Errors occur within the Sabre Web Services infrastructure. They are caused by fault messages from the web client or problems with the Sabre Profile Web Services connectivity. The infrastructure detects and generates these errors and returns them as SOAP faults, with or without ebXML headers.
Sabre Airline Solutions 3150 Sabre Drive Southlake, Texas 76092 USA Please contact our nearest regional office for more information: Asia / Pacific Tel: 65 6215 9500 Email: contact.apac@sabre.com Europe, Middle East, Africa Tel: 44 208 538 8539 Email: emea.contact@sabre.com The Americas Tel: 1 682 605 6750 Email: contact.americas@sabre.com
Rohn 25G Guyed Tower 44 Rohn 45G Guyed Tower 46 Rohn 55G Guyed Tower 48 Rohn SSV Towers 49 Sabre 1200 TLWD Guyed Tower 50 Sabre 1800 TLWD Guyed Tower 52 Sabre 1800 SRWD Guyed Tower 54 Sabre Series UL Self-Supporting Tower 55 Sabre Series VL Self-Supporting Tower 55 Lightweight Towe
The Sabre 54 Salon Express is the latest model in a the Sabre Hard Top Express series that began with the Sabre 42 and continued with 34 and 38 foot hulls, each to rave reviews from the boating press and from owners alike. The Sabre 54 proudly follows that tradition of style and technology, and the accolades have been exceptional.
Joanne Freeman – The American Revolution Page 3 of 265 The American Revolution: Lecture 1 Transcript January 12, 2010 back Professor Joanne Freeman: Now, I'm looking out at all of these faces and I'm assuming that many of you have
