UG WBS Ticket DisplayTST 15.1

Web Services User's Guide
Ticket_DisplayTST 15.1
Amadeus SAS
485, Route du Pin Montard
BP 69
06902 Sophia-Antipolis Cedex
Table of Contents
Table of Contents
Preface.................................................................................................................................. 4
1 Purpose of this document..............................................................................................4
2 Intended Audience......................................................................................................... 4
3 Associated Documents.................................................................................................. 4
4 Structure of this document............................................................................................ 4
Function: Ticket_DisplayTST................................................................................................ 6
1 Overview........................................................................................................................ 6
1.1 Supported Operations............................................................................................. 6
1.2 Limitations................................................................................................................6
1.3 Unsupported Operations......................................................................................... 6
1.4 Prerequisites............................................................................................................6
2 Building A Query............................................................................................................8
3 Receiving A Reply....................................................................................................... 10
4 Error Messages............................................................................................................11
4.1 Error Reply............................................................................................................ 12
5 Operations....................................................................................................................13
5.1 Operation: Baggage Allowance Update................................................................ 13
5.1.1 Query Structure........................................................................................................................... 13
5.1.2 Reply Structure............................................................................................................................ 13
5.1.3 Possible Errors............................................................................................................................ 17
5.2 Operation: Display all TST(s)................................................................................18

5.2.1 Query Structure........................................................................................................................... 18
5.2.2 Reply Structure............................................................................................................................ 18
5.2.3 Possible Errors............................................................................................................................ 18
5.3 Operation: Display by Passenger selection.......................................................... 19

5.3.1 Query Structure........................................................................................................................... 19
5.3.2 Reply Structure............................................................................................................................ 19
5.3.3 Possible Errors............................................................................................................................ 19
5.4 Operation: Display by segment selection..............................................................20

i
Table of Contents
5.4.1 Query Structure........................................................................................................................... 20

5.4.2 Reply Structure............................................................................................................................ 20
5.4.3 Possible Errors............................................................................................................................ 20
5.5 Operation: Display by TST selection.....................................................................21

5.5.1 Query Structure........................................................................................................................... 21
5.5.2 Reply Structure............................................................................................................................ 21
5.5.3 Possible Errors............................................................................................................................ 21
5.6 Operation: Display TST Related to Adult only (without infant): example 1............22
5.6.1 Query Structure........................................................................................................................... 22
5.6.2 Reply Structure............................................................................................................................ 22
5.6.3 Possible Errors............................................................................................................................ 22
5.7.1 Query Structure........................................................................................................................... 23
5.7.2 Reply Structure............................................................................................................................ 23
5.7.3 Possible Errors............................................................................................................................ 23
5.8.1 Query Structure........................................................................................................................... 24
5.8.2 Reply Structure............................................................................................................................ 24
5.8.3 Possible Errors............................................................................................................................ 24
5.9 Operation: Display TST related to either adult only or infant only.........................25
5.9.1 Query Structure........................................................................................................................... 25
5.9.2 Reply Structure............................................................................................................................ 25
5.9.3 Possible Errors............................................................................................................................ 25
5.10 Operation: Display TST with non-ticketable fare.................................................26

5.10.1 Query Structure......................................................................................................................... 26
5.10.2 Reply Structure.......................................................................................................................... 26
5.10.3 Possible Errors.......................................................................................................................... 34
5.11 Operation: Display with 2 segments for one Fare Component........................... 35

5.11.1 Query Structure......................................................................................................................... 35
5.11.2 Reply Structure.......................................................................................................................... 35
5.11.3 Possible Errors.......................................................................................................................... 41
5.12 Operation: Display with Fare Component........................................................... 42

ii
Table of Contents
5.12.1 Query Structure......................................................................................................................... 42

5.12.2 Reply Structure.......................................................................................................................... 42
5.12.3 Possible Errors.......................................................................................................................... 49
5.13 Operation: Display with Fare Family name......................................................... 50

5.13.1 Query Structure......................................................................................................................... 50
5.13.2 Reply Structure.......................................................................................................................... 50
5.13.3 Possible Errors.......................................................................................................................... 58
5.14 Operation: Display with Service Component.......................................................59

5.14.1 Query Structure......................................................................................................................... 59
5.14.2 Reply Structure.......................................................................................................................... 59
5.14.3 Possible Errors.......................................................................................................................... 66
5.15 Operation: Scrolling............................................................................................. 67

5.15.1 Query Structure......................................................................................................................... 67
5.15.2 Reply Structure.......................................................................................................................... 67
5.15.3 Possible Errors.......................................................................................................................... 67
iii
Web services User guide for function Ticket_DisplayTST
Preface
1 Purpose of this document
The purpose of this document is to provide basic functional overview descriptions and relevant examples for
a better understanding of the functions.
2 Intended Audience
This document is aimed at those who implement this function.
3 Associated Documents
This document has to be combined to its corresponding Technical Reference Guide and possibly to Product
specifications.
4 Structure of this document

This document is composed of the following parts:
the functional description: overview, supported operations, limitations, unsupported operations,
prerequisites and possibly reference to product specifications
the detailed description to build the query and to retrieve data from the reply
a set of relevant examples
Copyright 1987-2015 Amadeus IT Group SA.
Page 4 of 67
Ticket_DisplayTST
A Transitional Stored Ticket (TST) is a pricing record for a given passenger(s)/itinerary association.
Ticket_DisplayTST is used to display the information on an existing TST.
Page 5 of 67
Function: Ticket_DisplayTST.
1 Overview
A Transitional Stored Ticket (TST) represents the financial part of an itinerary. You can find in the TST
information such as fares, taxes, selling conditions, last date to ticket, creation date, and so on.The TST can
be created automatically via a pricing entry or manually by the user.
A Passenger Name Record (PNR) can contain up to 999 TSTs, and a passenger can be linked to up to 10
TSTs. The message Ticket_DisplayTST allows you to display one or multiple TSTs.
1.1 Supported Operations

The service offers a large panel of selection options to target the appropriate TST(s) to be displayed:
Display every TST:Displayup to 20TSTs appended to aPNR.When there are more than 20 TSTs
appended to the PNR, the message returns the first 20TSTs in the order they were created, as well as a
warning that there are more TSTs.
Display byTST number: Select the tattoos of the TSTs to be displayed; a tattoo is an unique reference
ID assigned to theTST by the system.
Display by passenger selection: Select one or more passengers for whom you want to display the
related TSTs.
Display by segment selection:Display all theTSTs related to the selected segments.
Select passengers without infants:Display all TSTs without the infants ones.
Select infants only: DisplayTSTs for infant passenger(s).
Scrolling: when the display of more than 20 TSTs is requested, only the first 20 are displayed by
increasing order of tattoo number. Be aware that when all theTSTs were not returned, boththe number of
remainingTSTs and the last returned TST's tattoo will be given in the response.
1.2 Limitations
The service returns onlyTST stored content. i.e. it does not return any of the linked elements that belong
to the PNR such the passengers names, the route and the Fare Elements. For instance, commission, form
of payment, tour code, endorsement and original issue/in exchange.
Up to 20 TSTS can be returned in theTicket_DisplayTSTReply. Whenmore than 20 TSTsmeet the

selection criteria, the scrolling functionalitymust be used.
Depending on functionality implemented for the customer who uses this verb, and depending on the
carrier, some information shown in this verb might be empty.
This service does not return a deleted TST.
This service does not return theTST index.
1.3 Unsupported Operations

Display of a deleted TST.
Display of the TST index.
1.4 Prerequisites
A PNR must be active in the context, and contain at least one active TST.
Page 6 of 67
If aTST is confidential, only the office that sets the confidentiality can access, read and update it, unless
access rights have been given beforehand.
Page 7 of 67
2 Building A Query
Two options are available when building a request: the option ALL - to display all TSTs appended to the
current PNR - and the option SEL - to select in a more precise way theTST(s) to be displayed. Use one of
these two options inthe attributeType element.
For example, the following request willdisplay all TSTs
<Ticket_DisplayTST myxmlns="http://xml.amadeus.com/TTSTRQ_14_1_1A">
<displayMode>
<attributeDetails>
<attributeType>ALL</attributeType>
</attributeDetails>
</displayMode>
</Ticket_DisplayTST>
When you use theSEL option, other sub-options are consequently available:
referenceType:to say whether the choice of theTSTsto be displayed are done byTST reference
ID, passenger number, or segments.
uniqueReference to send the tattoo numbers of theselected objects.

For instance, the following request willdisplay only theTST whose tattoo is 1:
<displayMode>
<attributeDetails>
<attributeType>SEL</attributeType>
</attributeDetails>
</displayMode>
<tstReference>
<referenceType>TST</referenceType>
<uniqueReference>1</uniqueReference>
</tstReference>
Additionally the servicecontains:
-"originInformation" toprovide information on the origin of the message;
-"displayMode" toprovide either all TSTs or only the information corresponding to the TST/ passenger selection;
-"pnrLocatorData" for PNR record locator information. This PNR record locator is used for tracking purpose.
Page 8 of 67
-"scrollingInformation" for the scrolling information;

-"tstReference" is used to get TST information for selected TST references.
As we can have up to 10 TSTs per Pax, and that a PNR can contain up to 99 passengers with one infant each,
then the maximum number of TSTs possible is 1980.
-"psaInformation" for passenger/segment references information about TST(s) to retrieve.
- Passenger reference specified : all the TSTs concerning this passenger reference are returned.
- Passenger/segment reference : only the TST having this passenger/segment association is returned.
Page 9 of 67
3 Receiving A Reply
The system returns all TSTs to be displayed by increasing order of tattoo number if there are less than 20
TSTs to be displayed.
Otherwise, the system returns the first 20, the number of remaining TSTsand the tattoo of the lastTST displayed
as follows:
<Ticket_DisplayTSTReply myxmlns="http://xml.amadeus.com/TTSTRR_14_1_1A">
<scrollingInformation>
<nextListInformation>
<remainingInformation>10</remainingInformation>
<remainingReference>20</remainingReference>
</nextListInformation>
The responsecontains:
"scrollingInformation" which provides Scrolling information used for long messages.
There is either the number of TSTs remaining (0 means that there is no more TST), and the last TST
reference in the list retrieved;
The ATR segment contains the reason for manual update, in case of taxes and fees updates.
Error information;
"fareList", which details all the elements of the TST. Please note that the response may have several
TSTs imbedded. The maximum number of TSTs is: maximum number of passenger in a PNR (99) mulitplied
by 2 (each passenger can have an infant) multiplied by the maximum number of TSTs for one passenger
(10). It has been limited to 10 for message size constraint.
Page 10 of 67
4 Error Messages
Error code
Error messages
Explanation
2090
NO TST RECORD EXISTS
User attempts to displaya TST

when noTST is appended to the
PNR.
2075
INVALID TST NUMBER
Tattoo of the request does not

correspond to any TST.
1908
CHECK PASSENGER NUMBER
Tattoo of the request does not

correspond to any Passenger
8311
CHECK SEGMENT NUMBER
Number of the request does not

correspond to any segment
3504
COMBINATION NOT ALLOWED
Associate in the same queryTST

and passenger or TST and
segment selection.
12474
BSR MISSING OR INVALID
The Bankers rate is missing or

invalid.
1856
THIS SCROLLING REQUEST IS

NOT SUPPORTED
When the scrolling requestis not

correct.
11
UNABLE TO PROCESS
For other technical errors.
00477
INVALIDFORMAT
Forwhen theentry isnot

specified.
10620
RESTRICTED-CONFIDENTIAL
when trying to display

aconfidentialTST without rights to
display it.
TST
32350
Example:
INVALID SELECTION NUMBER
If the fare or service

componentspecifieddoesn't exist
Scenario: there is a PNRwith some TSTs appended.

In the query, user tries to display the TSTs number 1 and 8 (tattoos). However,the TST number8 does not exist.
Query
<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<tstReference>
Page 11 of 67
</tstReference>
<tstReference>
</tstReference>
4.1 Error Reply

<Ticket_DisplayTSTReply xmlns="http://xml.amadeus.com/TTSTRR_15_1_1A" >
<errorGroup>
<errorOrWarningCodeDetails>
<errorDetails>
<errorCode>2075</errorCode>
<errorCategory>EC</errorCategory>
</errorDetails>
</errorOrWarningCodeDetails>
<errorWarningDescription>
<freeTextDetails>
<textSubjectQualifier>1</textSubjectQualifier>
<source>M</source>
<encoding>7</encoding>
</freeTextDetails>
<freeText>INVALID TST NUMBER</freeText>
</errorWarningDescription>
</errorGroup>
</Ticket_DisplayTSTReply>
Page 12 of 67
5 Operations
5.1 Operation: Baggage Allowance Update
In case travel Agent perform baggage Allowance modification with TTI or TTK entry, the "*" will be implemented
between TST Pricing indicator and FCPI.
5.1.1 Query Structure

<Ticket_DisplayTST xmlns="http://xml.amadeus.com/TTSTRQ_15_1_1A" >
<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
5.1.2 Reply Structure

<fareList>
<pricingInformation>
<tstInformation>
<tstIndicator>I</tstIndicator>
</tstInformation>
<fcmi>0</fcmi>
</pricingInformation>
<fareReference>
<iDDescription>
<iDSequenceNumber>1</iDSequenceNumber>
</iDDescription>
</fareReference>
<lastTktDate>
<businessSemantic>CRD</businessSemantic>
<dateTime>
<year>2015</year>
<month>6</month>
<day>30</day>
</dateTime>
</lastTktDate>
<lastTktDate>
<businessSemantic>LMD</businessSemantic>
<dateTime>
<year>2015</year>
<month>6</month>
<day>30</day>
Page 13 of 67
</dateTime>
</lastTktDate>
<validatingCarrier>
<carrierInformation>
<carrierCode>7X</carrierCode>
</carrierInformation>
</validatingCarrier>
<paxSegReference>
<refDetails>
<refQualifier>PA</refQualifier>
<refNumber>1</refNumber>
</refDetails>
</paxSegReference>
<fareDataInformation>
<fareDataMainInformation>
<fareDataQualifier>F</fareDataQualifier>
</fareDataMainInformation>
<fareDataSupInformation>
<fareDataQualifier>B</fareDataQualifier>
<fareAmount>1044.00</fareAmount>
<fareCurrency>EUR</fareCurrency>
</fareDataSupInformation>
<fareDataQualifier>712</fareDataQualifier>
<fareDataQualifier>TFT</fareDataQualifier>
</fareDataInformation>
<taxInformation>
<taxDetails>
<taxQualifier>7</taxQualifier>
<taxIdentification>
<taxIdentifier>X</taxIdentifier>
</taxIdentification>
<taxType>
<isoCountry>OY</isoCountry>
</taxType>
<taxNature>CB</taxNature>
</taxDetails>
<amountDetails>
<fareDataQualifier>TAX</fareDataQualifier>
Page 14 of 67
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>DE</isoCountry>
</taxType>
<taxNature>SE</taxNature>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>RA</isoCountry>
</taxType>
<taxNature>EB</taxNature>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<originDestination>
<cityCode>FRA</cityCode>
<cityCode>MAD</cityCode>
</originDestination>
Page 15 of 67
<segmentInformation>
<connexInformation>
<connecDetails>
<connexType>O</connexType>
</connecDetails>
</connexInformation>
<segDetails>
<segmentDetail>
<identification>AIR</identification>
<classOfService>Y</classOfService>
</segmentDetail>
<ticketingStatus>OK</ticketingStatus>
</segDetails>
<fareQualifier>
<fareBasisDetails>
<primaryCode>YIF</primaryCode>
</fareBasisDetails>
</fareQualifier>
<bagAllowanceInformation>
<bagAllowanceDetails>
<baggageWeight>33</baggageWeight>
<baggageType>W</baggageType>
<measureUnit>K</measureUnit>
</bagAllowanceDetails>
</bagAllowanceInformation>
<segmentReference>
<refDetails>
<refQualifier>S</refQualifier>
</refDetails>
</segmentReference>
<sequenceInformation>
<sequenceSection>
<sequenceNumber>1</sequenceNumber>
</sequenceSection>
</sequenceInformation>
</segmentInformation>
<otherPricingInfo>
<attributeDetails>
<attributeType>FCA</attributeType>
<attributeDescription>FRA
7X
ROE0.913391</attributeDescription>
</attributeDetails>
</otherPricingInfo>
<statusInformation>
<firstStatusDetails>
<tstFlag>ADT</tstFlag>
MAD1142.99NUC1142.99END
Page 16 of 67
</firstStatusDetails>
<otherStatusDetails>
<tstFlag>INT</tstFlag>
</otherStatusDetails>
<tstFlag>BAU</tstFlag>
</statusInformation>
<officeDetails>
<originIdentification>
<inHouseIdentification1>AA</inHouseIdentification1>
<inHouseIdentification2>NCE7X0101</inHouseIdentification2>
</originIdentification>
<originatorTypeCode>U</originatorTypeCode>
</officeDetails>
<officeDetails>
<originatorTypeCode>P</originatorTypeCode>
</officeDetails>
<endFareList/>
</fareList>
5.1.3 Possible Errors
Page 17 of 67
5.2 Operation: Display all TST(s)

This example shows how to display all theTSTs in the PNR.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
Page 18 of 67
5.3 Operation: Display by Passenger selection

Situation: User wants to display all the TSTs related to the passenger with the tattoo 6.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
</scrollingInformation>
Page 19 of 67
5.4 Operation: Display by segment selection

Situation: User wants to display all TSTs containing the segment which has the tattoo 6.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<psaInformation>
<refDetails>
</refDetails>
<refDetails>
</refDetails>
</psaInformation>
Page 20 of 67
5.5 Operation: Display by TST selection

Situation: User wants to display the TST with the tattoo 1.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<tstReference>
</tstReference>
Page 21 of 67
5.6 Operation: Display TST Related to Adult only (without infant): example 1
User wants to display all adult TSTs for all passengers and infant TST for the passenger with the tattoo 1.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<psaInformation>
<refDetails>
</refDetails>
<refDetails>
<refQualifier>PI</refQualifier>
</refDetails>
</psaInformation>
Page 22 of 67
Example 2: User wants to display adult TSTs for all passengers and all TST related to passenger with the
tattoo 1.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<psaInformation>
<refDetails>
</refDetails>
<refDetails>
<refQualifier>PI</refQualifier>
</refDetails>
</psaInformation>
Page 23 of 67
Situation: there is a PNR in which passengers are as follows:
1.USERGUIDE/A2.USERGUIDE/AA(INF)3.USERGUIDE/AAA(CHD)
Example 1: User attempts to display all TSTs related to the adult passenger with the tattoo 2 (without the infant).
Note: In this case, the tattoo and the displaynumber are the same (equal to 2). However, they could be different.
To display the TST related to the infant only, the value of the refQualifier should be set to PI.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<psaInformation>
<refDetails>
</refDetails>
</psaInformation>
Page 24 of 67
5.9 Operation: Display TST related to either adult only or infant only
Situation: there is a PNR in which passengers are as follows:
1.USERGUIDE/A2.USERGUIDE/AA(INF)3.USERGUIDE/AAA(CHD)

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<tstReference>
</tstReference>
Page 25 of 67
5.10 Operation: Display TST with non-ticketable fare
Display a TST with thenon-ticketable fare indicator.

This option is not available by default,please contact your account manager for more information.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
<tstReference>
</tstReference>

<fareList>
<tstInformation>
<tstIndicator>M</tstIndicator>
</tstInformation>
<fcmi>1</fcmi>
<fareReference>
<iDDescription>
</iDDescription>
</fareReference>
<fareIndicators>
<fareDetails>
<fareCategory>NTF</fareCategory>
</fareDetails>
</fareIndicators>
<validatingCarrier>
<paxSegReference>
<refDetails>
Page 26 of 67
</refDetails>
</paxSegReference>
<fareCurrency>GBP</fareCurrency>
<fareDataQualifier>E</fareDataQualifier>
<fareAmount>1212700</fareAmount>
<fareCurrency>KRW</fareCurrency>
<fareDataQualifier>TOF</fareDataQualifier>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>QX</isoCountry>
</taxType>
<taxNature>AP</taxNature>
</taxDetails>
<amountDetails>
Page 27 of 67
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>IZ</isoCountry>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>FR</isoCountry>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
Page 28 of 67
<taxIdentification>
<taxType>
</taxType>
<taxNature>TI</taxNature>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>GB</isoCountry>
</taxType>
<taxNature>AD</taxNature>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>UB</isoCountry>
</taxType>
<taxNature>AS</taxNature>
</taxDetails>
<amountDetails>
Page 29 of 67
</amountDetails>
</taxInformation>
<bankerRates>
<firstRateDetail>
<amount>1775.42</amount>
</firstRateDetail>
</bankerRates>
<originDestination>
<cityCode>LON</cityCode>
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<baggageQuantity>1</baggageQuantity>
<baggageType>N</baggageType>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
Page 30 of 67
<sequenceSection>
</sequenceSection>
<connexInformation>
<connecDetails>
<connexType>X</connexType>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
<otherPricingInfo>
<attributeDetails>
<attributeDescription>LON
6X
PAR534.94
</attributeDetails>
6X
LON534.94NUC1069.88END
Page 31 of 67
</otherPricingInfo>
<statusInformation>
<officeDetails>
</officeDetails>
<carrierFeesGroup>
<carrierFeeType>
<selectionDetails>
<option>OB</option>
</selectionDetails>
</carrierFeeType>
<carrierFeeInfo>
<carrierFeeSubcode>
<dataTypeInformation>
<type>T01</type>
</dataTypeInformation>
</carrierFeeSubcode>
<commercialName>
<freeTextQualification>
<textSubjectQualifier>COM</textSubjectQualifier>
</freeTextQualification>
<freeText>TESTTKT</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
<typeQualifier>TIN</typeQualifier>
<amount>44600</amount>
<currency>KRW</currency>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T02</type>
Page 32 of 67
<commercialName>
<freeText>TESTTKT2</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T04</type>
<commercialName>
<freeText>T04GEO8</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T05</type>
<commercialName>
<freeText>TESTB</freeText>
</commercialName>
<feeAmount>
Page 33 of 67
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
</carrierFeesGroup>
<endFareList/>
</fareList>
Page 34 of 67
5.11 Operation: Display with 2 segments for one Fare Component
Situation:a PNR with1 TST. As in a redemption usecase.

In this request, user asks for the display of the TST.
In the answer, theTST tree structure is shown thanks to the fareComponentDetails Group.
Please note that no changeis present in the query with respect to a display without the Fare Component. On
the other hand, in the answer, a new group is present.
In the following example, theTST hasone fare component linked to the two segments. It hasan amount in
Miles and a high Seasonality.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>

<fareList>
<tstInformation>
</tstInformation>
<fcmi>0</fcmi>
<fareReference>
<iDDescription>
</iDDescription>
</fareReference>
<lastTktDate>
<dateTime>
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<lastTktDate>
<dateTime>
Page 35 of 67
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<validatingCarrier>
<carrierCode>KE</carrierCode>
<paxSegReference>
<refDetails>
</refDetails>
</paxSegReference>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>BP</isoCountry>
</taxType>
<taxNature>DP</taxNature>
</taxDetails>
Page 36 of 67
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<originDestination>
Page 37 of 67
<cityCode>SEL</cityCode>
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
<classOfService>C</classOfService>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
<primaryCode>CXR</primaryCode>
<fareBasisCode>T</fareBasisCode>
</fareBasisDetails>
</fareQualifier>
<validityInformation>
<businessSemantic>A</businessSemantic>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
</validityInformation>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
Page 38 of 67
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
<primaryCode>YRT</primaryCode>
</fareBasisDetails>
</fareQualifier>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
<otherPricingInfo>
<attributeDetails>
Page 39 of 67
<attributeDescription>SEL
KE
LON
0.00
KE
SEL
</attributeDetails>
<attributeDetails>
<attributeType>MIL</attributeType>
<attributeDescription>MILEAGE
SEL
SEL8000TOTAL16000</attributeDescription>
</attributeDetails>
</otherPricingInfo>
<statusInformation>
<officeDetails>
<inHouseIdentification2>SELKE0980</inHouseIdentification2>
</officeDetails>
<officeDetails>
</officeDetails>
<mileage>
<mileageTimeDetails>
<totalMileage>16000</totalMileage>
</mileageTimeDetails>
</mileage>
<fareComponentDetailsGroup>
<fareComponentID>
<itemNumberDetails>
<number>1</number>
<type>FAR</type>
</itemNumberDetails>
</fareComponentID>
<monetaryInformation>
<monetaryDetails>
<typeQualifier>MIL</typeQualifier>
0.00
NUC
LHR8000
0.00
END
LHR
Page 40 of 67
<currency>M</currency>
</monetaryDetails>
</monetaryInformation>
<fareComponentServiceAttributes>
<criteriaDetails>
<attributeType>SEA</attributeType>
<attributeDescription>H</attributeDescription>
</criteriaDetails>
</fareComponentServiceAttributes>
<couponDetailsGroup>
<productId>
<referenceDetails>
<type>S</type>
<value>2</value>
</referenceDetails>
</productId>
</couponDetailsGroup>
<productId>
<referenceDetails>
<type>S</type>
<value>3</value>
</referenceDetails>
</productId>
</fareComponentDetailsGroup>
<endFareList/>
</fareList>
Page 41 of 67
5.12 Operation: Display with Fare Component
Situation:a PNR with1 TST.

In the answer, theTST structure shows the fareComponentDetails Group.
Please note that no changes are present in the request with respect to a display without the fare component.
On the other hand, in the answer, a new group is present.
In the example, the TST structure shows two fare components, both with an amount in Miles and a high
Seasonality.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>

<fareList>
<tstInformation>
</tstInformation>
<fcmi>0</fcmi>
<fareReference>
<iDDescription>
</iDDescription>
</fareReference>
<lastTktDate>
<dateTime>
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<lastTktDate>
<dateTime>
Page 42 of 67
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<validatingCarrier>
<paxSegReference>
<refDetails>
</refDetails>
</paxSegReference>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
Page 43 of 67
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<originDestination>
Page 44 of 67
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
Page 45 of 67
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
<otherPricingInfo>
<attributeDetails>
Page 46 of 67
<attributeDescription>SEL
KE
LON
0.00
KE
SEL
</attributeDetails>
<attributeDetails>
<attributeDescription>MILEAGE
SEL
SEL8000TOTAL16000</attributeDescription>
</attributeDetails>
</otherPricingInfo>
<statusInformation>
<officeDetails>
</officeDetails>
<officeDetails>
</officeDetails>
<mileage>
</mileage>
<fareComponentID>
<itemNumberDetails>
<number>1</number>
<type>FAR</type>
</fareComponentID>
<monetaryDetails>
0.00
NUC
LHR8000
0.00
END
LHR
Page 47 of 67
</monetaryDetails>
<criteriaDetails>
</criteriaDetails>
<productId>
<referenceDetails>
<type>S</type>
<value>2</value>
</referenceDetails>
</productId>
<fareComponentID>
<itemNumberDetails>
<number>2</number>
<type>FAR</type>
</fareComponentID>
<monetaryDetails>
</monetaryDetails>
<criteriaDetails>
</criteriaDetails>
<productId>
<referenceDetails>
<type>S</type>
<value>3</value>
</referenceDetails>
</productId>
Page 48 of 67
<endFareList/>
</fareList>
Page 49 of 67
5.13 Operation: Display with Fare Family name
Situation:a PNR with 1 TST. The fare has been previously stored together with the fare family name it belongs
to.
In the response, the TST structure is shown thanks to the fareComponentDetails Group.
Please note that no changeis present in the request with respect to a display without the Fare Component.
In the example, thestructure has one Fare Component with a fare family name and a fare family owner:
Fare family name is found in <fareFamilyDetails> <fareFamilyName>
Fare family owner is found in <fareFamilyOwner><otherCompany>

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>

<fareList>
<tstInformation>
<tstIndicator>M</tstIndicator>
</tstInformation>
<fcmi>1</fcmi>
<fareReference>
<iDDescription>
</iDDescription>
</fareReference>
<validatingCarrier>
<paxSegReference>
<refDetails>
Page 50 of 67
</refDetails>
</paxSegReference>
<fareCurrency>GBP</fareCurrency>
<fareDataQualifier>E</fareDataQualifier>
<fareDataQualifier>TOF</fareDataQualifier>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>QX</isoCountry>
</taxType>
<taxNature>AP</taxNature>
</taxDetails>
<amountDetails>
Page 51 of 67
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
<isoCountry>IZ</isoCountry>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
Page 52 of 67
<taxType>
</taxType>
<taxNature>TI</taxNature>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
Page 53 of 67
</amountDetails>
</taxInformation>
<bankerRates>
<firstRateDetail>
<amount>1775.42</amount>
</firstRateDetail>
</bankerRates>
<originDestination>
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
Page 54 of 67
</sequenceSection>
<connexInformation>
<connecDetails>
<connexType>X</connexType>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
<otherPricingInfo>
<attributeDetails>
<attributeDescription>LON
6X
PAR534.94
</attributeDetails>
</otherPricingInfo>
6X
LON534.94NUC1069.88END
Page 55 of 67
<statusInformation>
<officeDetails>
</officeDetails>
<carrierFeesGroup>
<carrierFeeType>
<selectionDetails>
<option>OB</option>
</selectionDetails>
</carrierFeeType>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T01</type>
<commercialName>
<freeText>TESTTKT</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T02</type>
<commercialName>
Page 56 of 67
<freeText>TESTTKT2</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T04</type>
<commercialName>
<freeText>T04GEO8</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
<carrierFeeInfo>
<carrierFeeSubcode>
<type>T05</type>
<commercialName>
<freeText>TESTB</freeText>
</commercialName>
<feeAmount>
<monetaryDetails>
Page 57 of 67
</monetaryDetails>
</feeAmount>
</carrierFeeInfo>
</carrierFeesGroup>
<fareComponentID>
<itemNumberDetails>
<number>1</number>
<type>FAR</type>
</fareComponentID>
<fareFamilyDetails>
<fareFamilyname>FARE FAMILY NAME</fareFamilyname>
</fareFamilyDetails>
<fareFamilyOwner>
<companyIdentification>
<otherCompany>6X</otherCompany>
</companyIdentification>
</fareFamilyOwner>
<productId>
<referenceDetails>
<type>S</type>
<value>1</value>
</referenceDetails>
</productId>
<productId>
<referenceDetails>
<type>S</type>
<value>2</value>
</referenceDetails>
</productId>
<endFareList/>
</fareList>
Page 58 of 67
5.14 Operation: Display with Service Component
Situation:a PNR with1 TST in anupgrade use case.

In the answer, theTST structure is shown thanks to the fareComponentDetails Group.
Please note that no changeis present in the request with respect to a display without the Fare Component.
In particular, theTST structureshows one Fare Component andone Service component, bothwith an amount
in Miles and with a high Seasonality.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>

<fareList>
<tstInformation>
</tstInformation>
<fcmi>0</fcmi>
<fareReference>
<iDDescription>
</iDDescription>
</fareReference>
<lastTktDate>
<dateTime>
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<lastTktDate>
<dateTime>
Page 59 of 67
<year>2013</year>
<month>2</month>
<day>7</day>
</dateTime>
</lastTktDate>
<validatingCarrier>
<paxSegReference>
<refDetails>
</refDetails>
</paxSegReference>
<fareDataQualifier>R</fareDataQualifier>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxIdentifier>O</taxIdentifier>
<taxType>
</taxType>
</taxDetails>
Page 60 of 67
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<taxInformation>
<taxDetails>
<taxIdentification>
<taxType>
</taxType>
</taxDetails>
<amountDetails>
</amountDetails>
</taxInformation>
<originDestination>
Page 61 of 67
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
Page 62 of 67
<connexInformation>
<connecDetails>
</connecDetails>
<segDetails>
<segmentDetail>
</segmentDetail>
</segDetails>
<fareQualifier>
<fareBasisDetails>
</fareBasisDetails>
</fareQualifier>
<dateTime>
<year>2014</year>
<month>8</month>
<day>15</day>
</dateTime>
<segmentReference>
<refDetails>
</refDetails>
</segmentReference>
<sequenceSection>
</sequenceSection>
<otherPricingInfo>
<attributeDetails>
Page 63 of 67
<attributeDescription>SEL KE LON Q148.00 2759.75KE SEL Q148.00 1483.60NUC4539.35END
</attributeDetails>
<attributeDetails>
<attributeDescription>MILEAGE SEL LHR16000TOTAL16000</attributeDescription>
</attributeDetails>
</otherPricingInfo>
<statusInformation>
<officeDetails>
</officeDetails>
<officeDetails>
</officeDetails>
<mileage>
</mileage>
<fareComponentID>
<itemNumberDetails>
<number>1</number>
<type>FAR</type>
</fareComponentID>
<monetaryDetails>
<typeQualifier>700</typeQualifier>
Page 64 of 67
</monetaryDetails>
<criteriaDetails>
</criteriaDetails>
<productId>
<referenceDetails>
<type>S</type>
<value>2</value>
</referenceDetails>
</productId>
<productId>
<referenceDetails>
<type>S</type>
<value>3</value>
</referenceDetails>
</productId>
<fareComponentID>
<itemNumberDetails>
<number>1</number>
<type>SER</type>
</fareComponentID>
<monetaryDetails>
</monetaryDetails>
<criteriaDetails>
</criteriaDetails>
<productId>
Page 65 of 67
<referenceDetails>
<type>S</type>
<value>2</value>
</referenceDetails>
</productId>
<endFareList/>
</fareList>
Page 66 of 67
5.15 Operation: Scrolling

Situation: A PNR with 30 TSTs numbered from 1 to 30 (tattoos).
In this request, user asks for the display of the two TSTs following TST with the tattoo 25.

<displayMode>
<attributeDetails>
</attributeDetails>
</displayMode>
</scrollingInformation>
Page 67 of 67

UG WBS Ticket DisplayTST 15.1

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

UG WBS Ticket DisplayTST 15.1

Загружено:

Авторское право:

Доступные форматы

Web Services User's Guide

5.2 Operation: Display all TST(s)................................................................................18

5.3 Operation: Display by Passenger selection.......................................................... 19

5.4 Operation: Display by segment selection..............................................................20

5.4.1 Query Structure........................................................................................................................... 20

5.5 Operation: Display by TST selection.....................................................................21

5.10 Operation: Display TST with non-ticketable fare.................................................26

5.11 Operation: Display with 2 segments for one Fare Component........................... 35

5.12 Operation: Display with Fare Component........................................................... 42

5.12.1 Query Structure......................................................................................................................... 42

5.13 Operation: Display with Fare Family name......................................................... 50

5.14 Operation: Display with Service Component.......................................................59

5.15 Operation: Scrolling............................................................................................. 67

Web services User guide for function Ticket_DisplayTST

4 Structure of this document

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

1.1 Supported Operations

Display by segment selection:Display all theTSTs related to the selected segments.

Select infants only: DisplayTSTs for infant passenger(s).

Up to 20 TSTS can be returned in theTicket_DisplayTSTReply. Whenmore than 20 TSTsmeet the

This service does not return a deleted TST.

This service does not return theTST index.

1.3 Unsupported Operations

Web services User guide for function Ticket_DisplayTST

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

uniqueReference to send the tattoo numbers of theselected objects.

Web services User guide for function Ticket_DisplayTST

-"scrollingInformation" for the scrolling information;

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

"scrollingInformation" which provides Scrolling information used for long messages.

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

NO TST RECORD EXISTS

User attempts to displaya TST

INVALID TST NUMBER

Tattoo of the request does not

CHECK PASSENGER NUMBER

Tattoo of the request does not

CHECK SEGMENT NUMBER

Number of the request does not

COMBINATION NOT ALLOWED

Associate in the same queryTST

BSR MISSING OR INVALID

The Bankers rate is missing or

THIS SCROLLING REQUEST IS

When the scrolling requestis not

For other technical errors.

Forwhen theentry isnot

when trying to display

INVALID SELECTION NUMBER

If the fare or service

Scenario: there is a PNRwith some TSTs appended.

Web services User guide for function Ticket_DisplayTST

4.1 Error Reply

Copyright 1987-2015 Amadeus IT Group SA.

Web services User guide for function Ticket_DisplayTST

5.1.1 Query Structure

5.1.2 Reply Structure

Web services User guide for function Ticket_DisplayTST