OVERVIEW - Sabrefiles.developer.sabre.com/doc/providerdoc/GetThere/... · 1 Itinerary Data Web Service This section will describe the Itinerary Data Web Service and the work flow

OVERVIEW

GetThere ERP WebServices

USER GUIDE

GetThere ERP WebServices – Overview – Error! No text of specified style in document.

DOCUMENT REVISION INFORMATION

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

Project Name GetThere ERP Web Services Feature ID

Prepared by Chris Simiele Date Prepared March 10, 2009

Revised by Andrew Smillie Date Revised September 25

Revision Summary Updates Revision Control No.

Revised by Andrew Smillie Date Revised August 6, 2015

Revision Summary Updates to Itinerary Services Revision Control No.

Revised by Andrew Smillie Date Revised November 18, 2015

Revision Summary Added ConnectionIndicator explanation Revision Control No.

Revised by Date Revised

Revision Summary Revision Control No.













STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved i

GetThere ERP WebServices – Overview – Error! No text of specified style in document. 1 I n t r o d u c t i o n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Objective ........................................................................................................................... 2

1 I t i n e r a r y D a t a W e b S e r v i c e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Features/Functions ........................................................................................................ 3 1.1.1 Retrieve List of Itinerary Locators ................................................................................... 3 1.1.1.1 Retrieve List of Itinerary Locators Data Elements ............................................................ 3 1.1.2 Retrieve Itinerary Data ................................................................................................. 4 1.1.2.1 Retrieve Itinerary Data Elements ................................................................................. 5 1.2 Process Flow ................................................................................................................ 5 1.3 Itinerary Status.............................................................................................................. 6 1.3 Features/Functions Is/Is Not ............................................................................................ 8 1.4 Assumptions and Constraints (includes external dependencies) .............................................. 8 1.5 Dependencies .............................................................................................................. 8

2 T r a v e l e r P r o f i l e S y n c h r o n i z a t i o n S e r v i c e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Features/Functions ........................................................................................................ 9 2.1.1 UDUT – Bulk Uploads .................................................................................................. 9 2.1.2 Profile Synchronization Web Service ............................................................................... 9 2.1.3 Data Examples ........................................................................................................... 9 2.1.4 Sample Web Service Data Examples ............................................................................ 11 2.1 Features/Functions Is/Is Not .......................................................................................... 16 2.2 Assumptions and Constraints (includes external dependencies) ............................................ 16 2.3 Dependencies ............................................................................................................ 16

A p p e n d i x 1 I t i n e r a r y D a t a W e b S e r v i c e F l o w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 7 A p p e n d i x 2 D a t a F i e l d L i s t f o r T r a v e l I t i n e r a r y R e a d . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 8 A p p e n d i x 3 B o o k i n g D a t a S e r v i c e U R L ’ s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 G l o s s a r y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Introduction 1


1 Introduction

O b j e c t i v e

This document will describe the following features: Itinerary Data Web Service – allow read-only access to itinerary data from the GetThere Database. Traveler Profile Synchronization Service – allow the synchronization of Travel Profiles between a customer ERP installation and the GetThere Booking Tool/User Profile.

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Introduction 2


1 Itinerary Data Web Service

This section will describe the Itinerary Data Web Service and the work flow for accessing itinerary detail data in a pseudo-batch mode.

1.1 F e a t u r e s / F u n c t i o n s

The Itinerary Data Web Service will allow read-only access to itinerary data. The GetThere database is the source for the itinerary data.

There will be two web services. Retrieve List of Itinerary Locators will allow the customer ERP installation to

get a list of itinerary locators for itineraries created or updated in a time window. Retrieve Itinerary Data will

get itinerary detail information.

New bookings made online (through the GetThere Booking Tool) and offline bookings made in Sabre, Apollo,

Galileo, Amadeus or Worldspan (if acquired by GetThere) will be supported. The EmployeeNumber will only be

supported for offline bookings (if acquired by GetThere) for Apollo and Sabre GDS customers.

The login credentials required for each customer ERP installation to authenticate with the Itinerary Data Web

Service must be requested from GetThere prior to implementation. As the credentials assigned will allow access

to the appropriate main or subsite, GetThere will determine the User ID.

1 . 1 . 1 R e t r i e v e L i s t o f I t i n e r a r y L o c a t o r s

The customer ERP installation sends a request to read a list of itinerary locators through a GetThere Web

Service. The request contains the site information and start time in a WSDL provided by GetThere. Itinerary

locators for bookings created/updated up to 1 hour after the requested start time or the current time (whichever

comes first) will be returned. The customer ERP installation must track the time start returned by the last

request. The LocatorRead response XML will increment the timestamp passed in the request by one hour and

return that to the provider in the field NextStartTime.

1 . 1 . 1 . 1 R e t r i e v e L i s t o f I t i n e r a r y L o c a t o r s D a t a E l e m e n t s

The following are data elements in the web service request.

Note: Please refer to the XML schema for GT_ERP_TravelItinerarayLocatorReadRQ

Field Name Required Maximum Data Type Maximum Description

Quantity Length

SubSiteName N 1 Alpha / 32 The unique subsite name assigned to numeric the customer.

SystemID N 1 Alpha / 8 External system identifier. numeric

ClientID N 1 Alpha / 3 External client identifier.

numeric

IncludeSubSite N 1 Boolean true or Include all bookings made in the

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Itinerary Data Web Service 3


false subsite.

UtcTime Yes 1 Timestam Time zone of the timestamp is in

p Coordinated Universal Time (UTC).

The following are data elements in the web service response.

Note: Please refer to the XML schema for GT_ERP_TravelItinerarayLocatorReadRS

Note: Itinerary locators for the booking created/updated in the next hour from startTime will be sorted by time.

Field Name Quantity Data Type Maximum Description

Length

UtcTime 1 Timestamp Time zone of the timestamp is in Coordinated Universal Time (UTC).The

start time for the next request. This will be

equal to the startTime in the request plus

one hour.

Count 1 Numeric Number of itinerary locators in the response.

ID 0 to many Alpha / 32 The GetThere assigned record locators for

numeric and the trips.

a slash (/)

SubSiteName 0 to 1 Alpha / 32 The unique subsite name assigned to the numeric customer.

SystemID 1 Alpha / 8 External system identifier.

numeric

ClientID 1 Alpha / 3 External client identifier.

numeric

1 . 1 . 2 R e t r i e v e I t i n e r a r y D a t a

The customer ERP installation sends a request to retrieve itinerary data through a Sabre Web Service interface. The request contains the itinerary locator(s) in a WSDL provided by GetThere.

The following are data elements in the web service request.

Note: Please refer to the XML schema for GT_ERP_TravelItinerarayReadRQ

Note: The number of locators allowed in the request is 10 STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Itinerary Data Web Service 4


Field Name Required Maximum Data Type Maximum Description

Quantity Length

ID Yes 1 to 10 Alpha / 32 The GetThere assigned record locator

numeric for the trip.

1 . 1 . 2 . 1 R e t r i e v e I t i n e r a r y D a t a E l e m e n t s

For data elements in the web service response, please see the XML schema for

GT_ERP_TravelItinerarayReadRS. The Sabre version of the OTA schema has been used as the basis of itinerary

data.

The GetThere database will serve as the master source of the itinerary data. Itinerary data elements include, but are not limited to:

Itinerary Identifier

Air Segments

Car Segments – including approximate total price and currency

Hotel Segments – including hotel room rate and currency

Rail Segments

Passenger Information

Pricing – including base air fare, total taxes, total fare and currency

Travel Policy Compliance

1.1.1.1 ConnectionIndicator

Air Segments are returned in chronological order. As they are processed, when you come across your first

“ConnectionIndicator=O” means you are at the start of a connecting flight. The next value you should see for the

next flight is a ConnectionIndicator=I. The value “I” also indicates that the previous segment is married to it and

it represents the final stop for that segment.

If it’s a nonstop flight you will not see any value for ConnectionIndicator regardless of whether that non stop is a oneway or embedded in a roundtrip or multi-destination.

If it’s a mulit-destination flight again you will see a ConnectionIndicator=O and ConnectionIndicator=I if the flight segment is not a non-stop.

If there is a leg with multi-segments (multi-stops), you will see ConnectionIndicator=I, ConnectionIndicator=IO, and ConnectionIndicator=I.

Oneway with no stops:



No ConnectionIndicator returned Oneway with 1 stop ConnectionIndicator=I, ConnectionIndicator=O Roundtrip with no stops: No ConnectionIndicator returned Roundtrip with 1 stop (either way): ConnectionIndicator=I, ConnectionIndicator=O MultiDestination ConnectionIndicator=I, ConnectionIndicator=O with a leg with 1 stop No connectionindicator if the leg is a non stop If there are 2 stops, ConnectionIndicator=I, ConnectionIndicator=IO, and ConnectionIndicator=I. How do I know where my destination is? If you process Air Items in the XML when you receive an Arrival Airport with no ConnectionIndicator that is the

Destination. If you receive an Arrival Airport with a ConnectionIndicator=O then that is a stop on the inevitable

destination. You will usually receive another Arrival Airport right after with a ConnectionIndicator=I and that

will be the final stop. If you receive an ConnectionIndicator=IO then there will be another Connection = I to

finalize the trip. Multi-Destinations are just that; trips with multi destinations. The traveler has more than destination in the trip. So the same rules apply as above.

1 . 2 P r o c e s s F l o w

The Itinerary Data Web Service process flow is shown in Appendix 1.

1 . 3 I t i n e r a r y S t a t u s

Itinerary status will be returned in the GT_ERP_TravelItineraryRead field called “ItineraryStatus”. The list of

status that can be obtained are below. It is important for the provider to note that PNR’s with either “Past Date”,



Cancelled, Queued, or Archived status will return XML with very little trip data. The reason for that is that GetThere has moved the data to a “historical” table in its database. PNR’s with the status’s of Past Date,

Queued, or Archived can be ignored by the integrating system. PNR’s with a status of Cancelled should be taken

note of as the status is important to be aware of.

Status Meaning

Active A trip that has been “reserved” with the supplier

but not yet ticketed/confirmed.

On Hold A trip that has been placed on hold via the

applicable GT Feature - Hold Trips

Suspended A trip that has been placed on Suspend via the

applicable GT Feature - Suspended Bookings

Ticketed A trip that has been ticketed - based on the

ticketing field in GDS

Queued We are not able to access the PNR successfully.

Archived we can no longer access this PNR in the GDS.

How soon a PNR is archived varies from GDS to

GDS, but definitely after the last departure date.

For these two statuses, no trip detail will be

displayed:

Cancelled A trip that has been cancelled . It could have

been cancelled before or after the PNR was

ticketed

Past Date A trip whose travel dates have passed.



1 . 3 F e a t u r e s / F u n c t i o n s I s / I s N o t

IS IS NOT

A Web Service to retrieve booking data from A web service to update itineraries.

the GetThere Database.

A way to retrieve data from a GDS.

1 . 4 A s s u m p t i o n s a n d C o n s t r a i n t s ( i n c l u d e s e x t e r n a l d e p e n

d e n c i e s )

A1. Support will be for single passenger itineraries only. C1. None identified at this time.

1 . 5 D e p e n d e n c i e s

D1. None identified at this time.



2 Traveler Profile Synchronization

Service This section will describe the GetThere Traveler Profile Synchronization Service.

2 . 1 F e a t u r e s / F u n c t i o n s

The Traveler Profile Synchronization Service will allow the synchronization of Traveler Profiles between a

customer ERP installation and the GetThere Booking Tool/User Profile. When used in conjunction with GetThere

Profile Synchronization, the updates can be sent to profiles in the GDS. The customer ERP installation is

considered the master record for the profiles. There are two processes. The GetThere Traveler Profile Web Service allows the customer ERP installation to

place incremental traveler profile changes into the GetThere Booking Tool User Profile. The GetThere User

Data Upload Tool (UDUT) will allow large batch updates or the initial load during a customer implementation.

Both processes offer add, update and delete functionality. No profile updates are pushed from the GetThere Booking Tool User Profile to the customer ERP installation.

2 . 1 . 1 U D U T – B u l k U p l o a d s

The UDUT (User Data Upload Tool) is available to administrators of a GetThere site who have a security level of SubSite Administrator or higher. The tool is accessible from the GetThere site’s administrative pages. The administrator creates a CSV file, accesses the UDUT through the Site Administration pages of the GetThere

site and uploads the file. The file is processed and an e-mail sent to advise the upload has completed and if any

validation errors were found. Processing times vary depending on the size of the file. Complete instructions and sample templates are available in the Database Uploads section of site’s administrative pages.

2 . 1 . 2 P r o f i l e S y n c h r o n i z a t i o n W e b S e r v i c e

The customer ERP installation can send incremental updates to the GetThere Booking Tool through Sabre Web Services. The request contains the profile data in a WSDL provided by GetThere. The login credentials required for each customer ERP installation to authenticate with the Profile

Synchronization Web Service must be requested from GetThere prior to implementation. As the credentials

assigned will allow access to the appropriate main or subsite, GetThere will determine the User ID.

2 . 1 . 3 D a t a E x a m p l e s

The following are required data fields. STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved 2 Traveler Profile Synchronization Service 9


Web Service UDUT Maximum Range Data Type Maximum Description

Field Name Field Quantity of “n” Length

Name

siteName 1 Alpha / 32 Unique main site name for

numeric the customer

subSiteName sub_site 1 Alpha / 32 Unique subsite to which the

numeric traveler is assigned

LoginID user 1 Alpha / 40 The GetThere user id of the

numeric traveler.

PasswordHash pwd 1 Alpha / 64 The password field is

numeric required by the UDUT to

create/add new users.

However, the web service

will accept an empty string.

UniqueID This 1 0 Alpha / 32 The unique customer

will be numeric identifier.

the CFE

created

on the

site.

Examples of how these fields apply to GetThere: Site/SubSite: Widget Inc. is a corporation with offices in the US, Canada and the UK. They create a main site – widget. Due

to different settings or requirements for different countries, they create three subsites named widgetus, widgetca

and widgetuk. This means there are four sites that can be logged into by a user from one URL. http://wx1.getthere.net/ssologin.act?sitename=widget 1. widget 2. widget: widgetus 3. widget: widgetca 4. widget: widgetuk Upon login the traveler will be directed to the main site or subsite to which they were assigned when their user ID was created. The site name does not have to include the name of the corporation. Widget could have used any name they wanted, provided it is not already in use by another site.

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved 2 Traveler Profile Synchronization Service 10


2 . 1 . 4 S a m p l e W e b S e r v i c e D a t a E x a m p l e s

Incremental Profile changes after an implementation take place using a GetThere provided web service. The login

credentials required for each customer ERP installation to authenticate with the Profile Synchronization Web

Service must be requested from GetThere prior to implementation. The web service passes a standard SOAP

envelope over HTTPS which contains a Traveler Profile Document Upload request. The format of the Traveler

Profile Document Upload request is detailed in a separate WSDL. The following name convention and assignments will be used in the SessionCreate request.

Field Assign

Domain GetThere

Organization The main site name as it appears in the database.

The main site name as it appears in the database if they want

access to bookings or profiles on the main site.

Username

The subsite name as it appears in the database if they want

access to bookings or profiles on the subsite.

GtItineraryListUser – if the Corporate Expense system will be

using the Itinerary Data Web Services.

GtProfileUpdateUser – if the Corporate Expense system will

Security Attributes be using the Traveler Profile Synchronization Service.

USGSessionUser – always assign.

Password Assign a secure password

Profile Service Requests are stateless and do not require the customer ERP installation to create and maintain a session. All action takes place within one request. Example: Widget Inc. wants to send a request to add a new employee’s Travel Profile to the GetThere Booking tool. Frederic Finc is a new employee. His address of 3153 Primus St., Anytown, CA 98000 along with other information is sent to GetThere. SOAP Header (with authentication): <soapenv:Envelope xmlns:soapenv=” http://schemas.xmlsoap.org/soap/envelope/”

xmlns:xsd=” http://www.w3.org/2001/XMLSchema” xmlns:xsi=”

http://www.w3.org/2001/XMLSchema-instance”> <soapenv:Header>

<ns1:MessageHeader xmlns:ns1=” http://www.ebxml.org/namespaces/messageHeader”>


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

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

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

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

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


<ns1:From>

<ns1:PartyId>

org.ebxml.www.namespaces.messageHeader.PartyId@1

</ns1:PartyId>

</ns1:From>

<ns1:To>

<ns1:PartyId>

org.ebxml.www.namespaces.messageHeader.PartyId@1</ns1:PartyId>

</ns1:To>

<ns1:CPAId></ns1:CPAId>

<ns1:ConversationId>SampleSession</ns1:ConversationId>

<ns1:Service>org.ebxml.www.namespaces.messageHeader.Service@1</ns1:Service>

<ns1:Action>SessionCreateRQ</ns1:Action>

<ns1:MessageData>

<ns1:MessageId> mid:20001209-133003-

[email protected]</ns1:MessageId>

<ns1:Timestamp>0108-10-03T09:27:23</ns1:Timestamp>

</ns1:MessageData>

</ns1:MessageHeader>

<ns2:Security xmlns:ns2=” http://schemas.xmlsoap.org/ws/2002/12/secext”>

<ns2:UsernameToken>

<ns2:Username>WidgetID</ns2:Username>

<ns2:Password>WidgetPassword</ns2:Password>

<Organization> Widget </Organization>

<Domain>GetThere</Domain></ns2:UsernameToken>

</ns2:Security> </soapenv:Header> <soapenv:Body>

<SessionCreateRQ xmlns=” http://www.opentravel.org/OTA/2002/11”> <POS> <Source PseudoCityCode="Widget"/> </POS> </SessionCreateRQ>

</soapenv:Body> </soapenv:Envelope>


mailto:org.ebxml.www.namespaces.messageHeader.PartyId@1

mailto:namespaces.messageHeader.Service@1%3c/ns1:Service

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

http://www.opentravel.org/OTA/2002/11

http://www.opentravel.org/OTA/2002/11


SOAP Body (with payload):

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Header>

<ns1:MessageHeader

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

<ns1:From>

<ns1:PartyId>org.ebxml.www.namespaces.messageHeader.PartyId@1</ns1:PartyId>

</ns1:From>

<ns1:To>

<ns1:PartyId>org.ebxml.www.namespaces.messageHeader.PartyId@1</ns1:PartyId>

</ns1:To>

<ns1:CPAId> </ns1:CPAId>

<ns1:ConversationId> </ns1:ConversationId>

<ns1:Service ns1:type="OTA">

org.ebxml.www.namespaces.messageHeader.Service@132fd</ns1:Service>

<ns1:Action>EPS_ProfileUpdateRQ</ns1:Action>

<ns1:MessageData>

<ns1:MessageId>mid:[email protected]</ns1:MessageId>

<ns1:Timestamp>0108-10-03T09:40:22</ns1:Timestamp>

</ns1:MessageData>

</ns1:MessageHeader>

<ns2:Security xmlns:ns2="http://schemas.xmlsoap.org/ws/2002/12/secext">

<ns2:BinarySecurityToken>Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/ STSB!ICESMSLB\/STS.LB!-4372486512836087744!1099129!0</ns2:BinarySecurityToken>





</ns2:Security>

</soapenv:Header>

<soapenv:Body>

<Sabre_OTA_ProfileUpdateRQ IgnoreDataErrors="Y"

UpdateByDataSourceInfo="Y"

Version="1"

xmlns="http://www.sabre.com/eps/schemas">

<ProfileInfo>

<Profile CreateDateTime="2008-11-19T15:40:27.959Z"

UpdateDateTime="2008-11-19T15:40:27.959Z">

<Traveler>

<Customer>

<PersonName>

<GivenName>Frederick</GivenName>

<MiddleName>P</MiddleName>

<SurName>Fink</SurName>

<DataSource PrimaryDS="GT" />

</PersonName>

<Telephone DeviceTypeCode="VC" PurposeCode="ALL">

<FullPhoneNumber>555-232-3232</FullPhoneNumber>


</Telephone>

<Telephone DeviceTypeCode="VC" PurposeCode="ALL">



</Telephone>

<Telephone DeviceTypeCode="FX" PurposeCode="ALL">



</Telephone>

<Email EmailAddress="[email protected]" EmailTypeCode="BUS">


</Email>



<Address>

<AddressLine>3153 Primus St</AddressLine>

<CityName>Anytown</CityName>

<PostalCd>98000</PostalCd>

<StateCode>CA</StateCode>

<CountryCode>US</CountryCode>


</Address>

<Document DocID="6161661661616" DocIssueCountryCode="US" DocTypeCode="PSPT">

<DocHolderName>Frederick Fink</DocHolderName>


</Document>

<CustLoyalty MembershipID="4141441441414" VendorCode="HL" VendorTypeCode="HL">


</CustLoyalty>

<EmploymentInfo>

<EmployeeInfo Company="Bahne Industries" />

</EmploymentInfo>

</Customer>

<TPA_Extensions

/> </Traveler>

</Profile>

</ProfileInfo>

</Sabre_OTA_ProfileUpdateRQ>

</soapenv:Body>

</soapenv:Envelope>



2 . 1 F e a t u r e s / F u n c t i o n s I s / I s N o t

IS IS NOT

The ability for a customer ERP installation to The ability for profile updates made in the

send profile updates to GetThere. GetThere Online Profile to be sent to the customer

ERP installation.

The ability to prohibit or turn off sections of the

GetThere Online Profile.

Any changes to the GetThere User Data Upload

Tool (UDUT).

Any changes to the processing times of the User

Data Upload Tool (UDUT).

Providing Profile Updates from SSO login.

2 . 2 A s s u m p t i o n s a n d C o n s t r a i n t s ( i n c l u d e s e x t e r n a l d e p e n

d e n c i e s )

A1.None identified at this time. C1. None identified at this time.

2 . 3 D e p e n d e n c i e s

D1. None identified at this time.



Appendix 1 Itinerary Data Web Service Flow

Expense System GetThere

Create Session

Request: Read list of itinerary locators

(1 Request)

Request: Read itinerary data

(Multiple requests until itinerary data

for all itinerary locators returned

previously are all retrieved)

Response:

1. Start time for next batch process.

2. Number of itinerary locators in the request.

3. List of itinerary locators for itinerary created/updated in the next hour starts from startTime in the request.

Response:

Itinerary Data.

Close Session STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Appendix 1 Itinerary Data Web Service Flow 17


Appendix 2 Data Field List for

TravelItineraryRead

Section Field Data

General ItineraryRef PNR

General OtherSystemID SAP TAN

General Site SystemID SAP SID

General Client ID SAP CID

General GetThereTripID ITN_Number

General FirstName Firstname

General LastName Lastname

General CustomerIdentifier SAP PID/GERS Country Code

General EmployeeInfo Employee Number

Air ArrivalDateTime Arrival Date/Time

Air DepartureDateTime Departure Date/Time

Air FlightNumber Flight Number

Air NumberinParty Number in Party

Air ResBookDesigCode Booking Code for the Flight

Air StopQuantity # of Stops

Air DepartureAirportCode Departure Airport Code

Air CountryCode Departure Country Code

Air CountryName Departure Country Name

Air AirportName Departure Airport Name

Air CityName Departure City Name

Air StateName Departure State Name

Air StateCode Departure State Code

Air ArrivalAirportCode Arrival Airport Code

Air CountryCode Arrival Country Code

Air CountryName Arrival Country Code

Air AirportName Arrival Airport Name

Air CityName Arrival City Name

Air StateName Arrival State Name

Air State Code Arrival State Code

Air Operating Airline Code Airline IATA Code

Air Company Short Name Airline Name

Air AirEquipType Airline Equipment Type

Air MarketingAirlineCode Marketing Airline Code

Air AirLineRefID Airline Conf Number

Air TravelPolicyViolation Text of Violation

Air FareClass will decode into the cabin

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Appendix 2 Data Field List for TravelItineraryRead 18


Vehicle ConfID ConfirmationID

Vehicle Vendor Code Vendor Code

Vehicle Vendor Name Vendor Name

Vehicle PickUpDateTime PickUpDateTime

Vehicle ReturnDateTime ReturnDateTime

Vehicle PickUp LocationCode PickUp LocationCode

Vehicle PickUp LocationName PickUp LocationName

Vehicle Return Location Code Return Location Code

Vehicle Approximate Total Charge Amount with Currency Code

Vehicle Approximate Total Amount

Vehicle Currency Code Currency Code

Vehicle EquipType Type of Vehicle

Vehicle TravelPolicyViolationText Text of Violation

Vehicle PickUpCityName PickUpCityName

Vehicle PickUpCountryCode PickUpCountryCode

Vehicle PickUpCountryName PickUpCountryName

Vehicle PickUpStateCode PickUpStateCode

Vehicle PickUpStateName PickUpStateName

Vehicle DropOffCityName DropOffCityName

Vehicle DropOffCountryCode DropOffCountryCode

Vehicle DropOffCountryName DropOffCountryName

Vehicle DropOffStateCode DropOffStateCode

Vehicle DropOffStateName DropOffStateName

Hotel RoomTypeCode Room Type

Hotel NumberofUnits Number of Rooms

Hotel AmountBeforeTax Amount Before Tax

Hotel CurrencyCode CurrencyCode

Hotel Guest Count Guest Count

Hotel Start Check In

Hotel end Check Out

Hotel ChainCode ChainCode

Hotel HotelCode GDS Property ID

Hotel HotelCityCode HotelCityCode

Hotel HotelName HotelName

Hotel ConfirmationNumber ConfirmationNumber

Hotel HotelAddress HotelAddress

Hotel CountryCode CountryCode

Hotel PhoneNumber PhoneNumber

Hotel TravelPolicyViolationText Text of Violation



Hotel CityName City Name

Hotel StateCode State Code

Hotel StateName State Name

Hotel CountryCode Country Code

Hotel CountryName Country Name

Rail VendorCode VendorCode

Rail TrainNumber TrainNumber

Rail ResBookDesigCode ResBookDesigCode

Rail LocationCode Departure Location Code

Rail LocationName Departure Location Name

Rail StateCode Departure State Code

Rail StateName Departure State Name

Rail CountryCode Departure Country Code

Rail CountryName Departure Country Name

Rail DepartureTime DepartureTime

Rail LocationCode Arrival Location Code

Rail Point Point

Rail StateCode Arrival State Code

Rail StateName Arrival State Name

Rail CountryCode Arrival Country Code

Rail CountryName Arrival Country Name

Rail ArrivalTime ArrivalTime

Rail ConfirmationNumber ConfirmationNumber

Rail TravelPolicyViolation TravelPolicyViolation

Ticketing TicketTimeLimit TicketTimeLimit

Itinerary BaseFareAmount BaseFareAmount

Itinerary BaseFareCurrency BaseFareCurrency

Itinerary Decimal Places Decimal Places

Itinerary TaxesAmount TaxesAmount

Itinerary TaxesCurrency TaxesCurrency

Itinerary TaxesDecimal TaxesDecimal

Itinerary LowerFareAmount AirFare Lower Fare Amount

Itinerary LowerFareCurrency AirFare LowerFareCurrency

Itinerary LowerFareDecimal AirFare LowerFareDecimal

Itinerary CreateDateTime TimeStamp of the Itin

Itinerary ItineraryStatus Booked,Ticketed, Cancelled

Policy - Air TravelPolicyJustification AirTravelPolicyJustificationText

Policy - Air TravelPolicyJustificationCode AirTravelPolicyJustificationCode



Policy -

Vehicle TravelPolicyJustification VehicleTravelPolicyJustificationText

Policy -

Vehicle TravelPolicyJustificationCode VehicleTravelPolicyJustificationCode

Policy - Hotel TravelPolicyJustification HotelPolicyJustificationText

Policy - Hotel TravelPolicyJustificationCode HotelPolicyJustificationCode

Policy - Rail TravelPolicyJustification RailPolicyJustificationText

Policy - Rail TravelPolicyJustificationCode RailPolicyJustificationCode

Error ErrorsCode

Error ErrorSeverity

Error ErrorMessage STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Appendix 2 Data Field List for TravelItineraryRead 21


Appendix 3 Booking Data Service URL’s

SessionCreate http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCreateRQ.wsdl http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCreateRQ.xsd http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCreateRQRS.xsd http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCreateRS.xsd http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/xmldsig-core-schema.xsd GT Locator Read Definitions: This service will download all the PNR Record Locators since your last request:

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryLocatorRead1.0.0RQ.xsd http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryLocatorRead1.0.0RQRS.xs

d http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryLocatorRead1.0.0RS.xsd

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryLocatorRead1.0.0RQ.wsdl

GT Itinerary Read: This service will download the contents of the booking.

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryRead1.0.0RQ.wsdl

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryRead1.0.0RQRS.xsd

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryRead1.0.0RQ.xsd

http://webservices.sabre.com/wsdl/sabreXML1.0.00/GetThere/GT_ERP_TravelItineraryRead1.0.0RS.xsd

SessionClose http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCloseRQ.wsdl http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCloseRQ.xsd http://webservices.sabre.com/wsdl/sabreXML1.0.00/usg/SessionCloseRQRS.xsd

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Appendix 3 Booking Data 22Service URL’s


Glossary

ACS – Authentication Control System CSV – Comma Separated Values ERP – Enterprises Resource Planning HTTPS - Hypertext Transfer Protocol over Secure Socket Layer ICE – Integrated Computing Environment LCARS – Library Computer Access and Retrieval System MOM – Message Oriented Middleware RPC – Remote Procedure Call SAML – Security Assertion Markup Language SOAP – Simple Object Access Protocol SSO – Single Sign On UDUT – User Database Upload Tool (GetThere tool) USG – Universal Services Gateway UTC – Coordinated Universal Time XSD - XML Schema Definition XSLT – Extensible Stylesheet Language Transformations WSDL – Web Service Definition Language

STUDENT GUIDE GetThere, L.P. Confidential | All Rights Reserved Glossary 23

Documents

OVERVIEW - Sabrefiles.developer.sabre.com/doc/providerdoc/GetThere/... · 1 Itinerary Data Web Service This section will describe the Itinerary Data Web Service and the work flow