User Guide - Sabrefiles.developer.sabre.com/doc/providerdoc/... · This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use,

User Guide GetAncillaryOffersRQRS for Sabre Travel Network

Schema Version 3.0.2

August 2018

© 2012-2018, Sabre GLBL Inc. All rights reserved.

This documentation is the confidential and proprietary intellectual

property of Sabre Inc. Any unauthorized use, reproduction,

preparation of derivative works, performance, or display of this

document, or software represented by this document, without the

express written permission of Sabre Inc. is strictly prohibited.

Sabre Travel Network and the Sabre Travel Network logo design

are trademarks and/or service marks of an affiliate of Sabre Inc.

All other trademarks, service marks, and trade names are owned

by their respective companies.

User Guide August 2018 Table of Contents iii

Table of Contents

1 G e t t i n g S t a r t e d

1.1 About This Guide ................................................................................................................................ 1-1

2 G e t A n c i l l a r y O f f e r s R e q u e s t

2.1 Introduction ......................................................................................................................................... 2-1 2.2 Pre-Ticketed Path/Booking/QueryByItinerary ..................................................................................... 2-2

2.2.1 Request Parameters ................................................................................................................. 2-2 2.3 Pre-Ticketed Path Stateful/Booking/QueryByPassenger .................................................................. 2-20

2.3.1 Request Parameters ............................................................................................................... 2-20 2.4 Pre-Ticketed Path Stateful/Booking/QueryByPassengerType .......................................................... 2-22

2.4.1 Request Parameters ............................................................................................................... 2-22 2.5 Post-Ticketed Path Payload/Booking ................................................................................................ 2-23

2.5.1 Request Parameters ............................................................................................................... 2-24 2.6 Post-Ticketed Path Stateful/Booking/QueryByTicket ........................................................................ 2-27

2.6.1 Request Parameters ............................................................................................................... 2-27

3 G e t A n c i l l a r y O f f e r s R e s p o n s e

3.1 Introduction ......................................................................................................................................... 3-1 3.2 AncillaryDefinition ............................................................................................................................... 3-2 3.3 Ancillary .............................................................................................................................................. 3-3 3.4 Offers .................................................................................................................................................. 3-4 3.5 PassengerOffers ................................................................................................................................. 3-5

3.5.1 Response with OfferRefs – Pre-Ticketed .................................................................................. 3-5 3.5.2 Response with Ticket/Coupon – Post-Ticketed ......................................................................... 3-6

3.6 ResponseOptions ............................................................................................................................... 3-6

4 G e t A n c i l l a r y O f f e r s R e q u e s t E x a m p l e s

4.1 Introduction ......................................................................................................................................... 4-9 4.2 GetAncillaryOffers RQ with Ticket Number Stateful ............................................................................ 4-9 4.3 GetAncillaryOffers RQ with Ticket Number Payload ......................................................................... 4-10 4.4 GetAncillaryOffers RQ Multi-Segment Payload ................................................................................ 4-13 4.5 GetAncillaryOffers RQ Multi-Pax Stateful ......................................................................................... 4-15 4.6 GetAncillaryOffers RQ Multi-Pax Payload ........................................................................................ 4-16 4.7 GetAncillaryOffers RQ Multi-Pax Multi-Segment Multi-Fare Payload ............................................... 4-19

iv Table of Contents User Guide August 2018

5 G e t A n c i l l a r y O f f e r s R e s p o n s e E x a m p l e s

5.1 Introduction ......................................................................................................................................... 5-1 5.2 GetAncillaryOffers RS with Ticket Number Payload ........................................................................... 5-1 5.3 GetAncillaryOffers RS Multi-Segment Payload ................................................................................... 5-4 5.4 GetAncillaryOffers RS Multi-Pax Stateful .......................................................................................... 5-10 5.5 GetAncillaryOffers RS Multi-Pax Payload ......................................................................................... 5-14 5.6 GetAncillaryOffers RS with Multi-Pax, Multi-Segment, Multi-Fare Payload ...................................... 5-20

6 E r r o r M e s s a g e s

6.1 Introduction ......................................................................................................................................... 6-1

User Guide August 2018 About This Guide 1-1

1.1 A b o u t T h i s G u i d e

The purpose of this document is to describe how the GetAncillaryOffers web service works and

provide details for how to create a successful request transaction. This document also provides details

on the response transaction, including any errors returned by GetAncillaryOffers. Each chapter is as

follows:

• Chapter 1, “Getting Started” explains the purpose of the document.

• Chapter 2, “GetAncillaryOffers Request” contains descriptions of the parameters needed to

construct the request schema and architecture for pre-ticketed and post-ticketed paths for the TN

channel for both check-in and booking modes.

• Chapter 3, “GetAncillaryOffers Response” contains descriptions of the parameters returned in

response schema.

• Chapter 4, “GetAncillaryOffers Request Examples” contains request examples.

• Chapter 5, “GetAncillaryOffers Response Examples” contains response examples.

• Chapter 6, “Error Messages” contains descriptions of error messages.

1 Getting Started 1

1-2 About This Guide User Guide August 2018

• • •

User Guide August 2018 Introduction 2-1

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

The GetAncillaryOffers web service is accessible via USG.

Environment USG endpoint

TSTS http://sws-sts.internal.cert.sabre.com

CERT http://sws-crt.internal.cert.sabre.com

PROD https://webservices.sabre.com/websvc

The GetAncillaryOffersRQ (version 3.0.2) service retrieves ancillary offers per individual passenger.

Ancillary offers contain a list of ancillaries (service type F - flight related/all groups) based on

marketing/operating carrier. The Ancillary offer is presented based on specific passenger details such as

frequent flyer, fare, and ticketing information. Ancillaries can be requested in a specific currency. Then,

there is no need for currency conversion in the point of sale application.

Ancillary Offers includes details about inventory. One passenger can receive a specific ancillary and not a

second due to lack of inventory.

Other than F-flight related ancillaries, GetAncillaryOffers is also able to retrieve ancillaries from other

service types dedicated to BG group – Baggage such as:

• A − Allowance

• B − Carry-on allowance

• C − Charges

• D − Disclosure (Includes detail about A-Allowance, B- Carry-on allowance, C-Charges for first and

second bag, E-Embargoes)

This information is retrieved based on most significant carrier.

Information about E − Embargoes is retrieved based on operating carrier.

2 GetAncillaryOffers Request 2

http://sws-sts.internal.cert.sabre.com/

http://sws-crt.internal.cert.sabre.com/

https://webservices.sabre.com/websvc

2-2 Pre-Ticketed Path/Booking/QueryByItinerary User Guide August 2018

This chapter includes the following:

• Pre-ticketed path/payload/booking/QueryByItinerary (see this page).

• Pre-ticketed path/payload/booking/QueryByPassenger (see “Pre-Ticketed

Path/Bookin/QueryByPassenger,” page 2-20).

• Pre-ticketed path/payload/booking/QueryByPassengerType (see “Pre-Ticketed

Path/Bookin/QueryByPassengerType,” page 2-22).

• Post-ticketed path/payload/booking (see “Post-Ticketed Path Payload/Booking,” page 2-23).

• Post-ticketed path/payload/booking/QueryByTicket (see “Post-Ticketed Path

Payload/Bookin/QueryByTicket,” page 2-27).

2.2 P r e - T i c k e t e d P a t h / B o o k i n g / Q u e r y B y I t i n e r a r y

The payload request type requires itinerary details to be specified in the GetAncillaryOffers request. Also,

SSRs, frequent flyer details, and fare details need to be specified in the request for better ancillary pricing.

An Ancillary offer is returned per passenger, so reference to the passenger, itinerary, and segment need to

be outlined in the request.

The search option applicable for payload is QueryByItinerary.

This section includes request parameters.

2.2.1 R e q u e s t P a r a m e t e r s

Request Type Mode Minimum parameters required in request

Payload (itinerary criteria are taken from request)

booking Version

Request type

Request mode

Client context

(client type, AgentCurrencyCode – if ancillaries

need to be priced in a given currency)

AncillaryRequestOptions

QueryByItinerary

QueryPassengerItinerary

RequestOptions

This section includes the following:

• Version (see “Version,” page 2-3).

• RequestType (see “RequestType,” page 2-3).

• RequestMode (see “RequestMode,” page 2-3).

User Guide August 2018 Pre-Ticketed Path/Booking/QueryByItinerary 2-3

• ClientContext (see “ClientContext,” page 2-4).

• AncillaryRequestOptions (see “AncillaryRequestOptions,” page 2-5).

• QueryByItinerary (see “QueryByItinerary,” page 2-7).

• QueryPassengerItinerary (see “QueryPassengerItinerary,” page 2-8).

• RequestOptions (see “RequestOptions” page 2-8).

2.2.1.1 V e r s i o n

Version is always: Version="3.0.2"

2.2.1.2 R e q u e s t T y p e

GAOv3.0.2 RQ should be sent with the following request type:

• Payload – requires itinerary to be provided in QueryByItinerary.

2.2.1.3 R e q u e s t M o d e

GAOv3.0.2 RQ can be sent with the following request mode:

• Booking


2.2.1.4 C l i e n t C o n t e x t

ClientContext includes the following:

• CityCode – Three-character code identifying the physical city (where the agent is located).

• PseudoCityCode – PCC.

• DutyCode –Authority code assigned to a requestor.

• LNIATA – Line Number Interchange Address Terminal Address.

• AirlineCarrierCode – Not applicable for TN.

• AgentCurrencyCode – Currency code for the agent.

• OfficeAccountInformation – Office account information.


- PersonalAccountingCityCode – Personal accounting city code.

- PersonalAccountingCode – Personal accounting code.

- PersonalOfficeCode – Personal office code.

2.2.1.5 A n c i l l a r y R e q u e s t O p t i o n s

• ServiceType:

– A – Free allowance baggage, only applicable for BG-baggage group.

– B – Carry on allowance, only applicable for BG-baggage group.

– C – Charges, only applicable on check-in for BG-baggage group.

– D – Disclosure (structured), only applicable for BG-baggage group.

There are specific service types retrieved for disclosure: A – Free baggage allowance for

registered baggage, B – Carry on allowance, C – Charges (but only for first and second

baggage), E – Embargoes.

– E – Embargoes, only applicable for BG-baggage group

– F – Flight related

– P – Prepaid, only applicable for BG-baggage group

• Group, for F-flight related service type it makes sense to narrow down search criteria based on

groups. List of applicable ancillary groups is as follows:


– BD (Bundled Service), there can be different groups of ancillaries returned in bundles.

– BG (Baggage).

– CO (Carbon Offset).

– FF (Frequent Flyer).

– GT (Ground Transportation and Non-Air Services).

– IE (In-flight entertainment).

– LG (Lounge), MD (Medical).

– ML (Meal/Beverage).

– PT (Pets).

– RO (Rule Override).

– SA (Pre-reserved Seat Assignment), returned only in bundles.

– There is separate process of handling seats via seat map.

– SB (Standby).

– ST (Store).

– TS (Travel Services).

– UN (Unaccompanied Travel (Escort)).

– UU (Unaccompanied Travel (Unescorted)).

– 98.

– 99.

– UP (Upgrades)

• Subcode (three-character ancillary product identifier, for example: 0B5 – seat assignment).

• Ssr (special service request).

When AncillaryRequestOptions is not specified in the GetAncillaryOffers RQ, all service types that are

not restricted in the carrier configuration will be returned.

If an ancillary option is specified, the response will be limited only to the OC requested in the

AncillaryRequestOptions.


2.2.1.6 Q u e r y B y I t i n e r a r y

Data in QueryByItinerary includes:

• “QueryPassengerItinerary” − Contains information about the passenger (element “Passenger”) and its

association to ticket, segments, and fares (element “PassengerItinerary”).

• “Segment” − Contains information about the flight segments (element “FlightDetail”) and how the

itinerary was requested and built in the PNR (elements “InboundConnection” and

“OutboundConnection”).

• “FareInfo” − Contains information about the fare calculation.


2.2.1.7 Q u e r y P a s s e n g e r I t i n e r a r y


2.2.1.8 P a s s e n g e r

• In “QueryPassengerItinerary” attributes passenger id, reference number, association, and infant

companion should be sent. Also, passenger type can be specified, but it must be a passenger type

from pricing such as ADT or CNN used in the ATPCO, Merchandising Manager filing.

• In “PersonName”, last name, first name, and (eventually) title should be sent.



• In the “LoyaltyAccounts” element, information about the frequent flyer should be added.

Loyalty accounts is used for better ancillary pricing. Usually, airlines offer better ancillary prices for their

frequent flyer members.

The attributes are:

• "memberAirline" – Member airline code.

• "tierTag" – Name of the tier level, such as 'GLD', 'PLT'; also known as short text.

• "tierNumber" – Tier level number saved in the PNR.


• “atpcoTierNumber” – ATPCO Tier Number from 1-9 that can be passed to pricing.

• “id” – XML id.

Optional services records created via ATPCO use ATPCO tiers (value from 1-9), which are different than

tiers and tags saved at the PNR level. That is why GAO uses tier mapping, which is stored in the profiles

system.


• PassengerItinerary (see this page).

• PassengerSegment (see this page).

2.2.1.8.1 PassengerItinerary

2.2.1.8.2 PassengerSegment

• In “PassengerSegment,” reference between the passenger and segment need to be sent.


• In “FareBreakAssociation,” only the FareInfoRef attribute needs to be sent.

Side trip indicators are optional. That element specified in which fare component the segment is

included. It contains the reference number attribute.

2.2.1.1 S e g m e n t

In the Segment element, all information about all air segments from the reservation should be sent,

including past and future segments. Sending only part of the trip (for example, only unflown segments)

may cause ancillary taxes to be calculated incorrectly.

• In attributes, “id” and “segment number” should be sent.

• InboundConnection - Indicates if connection from previous flight segment. Example "FALSE".

• OutboundConnection - Indicates if connection to the following flight segment. Example "FALSE".

• DirectConnectLocator - Direct connect locator for external pricing (SOE / SSG carriers only).

• RecordCreateTag - Record create tag (RCRQ). Required for LCC to use external pricing (SOE).



2.2.1.1.1 FlightDetail


FlightDetail includes:

• "Airline" − Marketing airline code.

• "FlightNumber" − Flight number from the marketing airline.

• "DepartureAirport" − Code of the origin airport of the flight.

• "DepartureDate" − Departure date.

• "DepartureTime" − Departure time.

• "ArrivalAirport" − Code of the destination airport of the flight.

• "ArrivalDate" − Arrival date.

• "ArrivalTime" − Arrival time.

• "OperatingAirline" − Operating airline code (may be different from the marketing airline).

• "OperatingFlightNumber" − Flight number of the operating airline (may be different then the

marketing airline).

• "ClassOfService" − Class of service code, single uppercase letter.

• "OperatingClassOfService" − Class of service code, single uppercase letter.

• "Cabin" − Cabin code, single alphanumeric character.

• "Equipment" − Code of the equipment utilized for the flight.

• "ReservationStatus" − Reservation status. This should be the segment status from the PNR.

• "ForcedConnectionInd" − Forced connection indication. It works the same as pricing qualifier Forced

Connection (WPX). In GAO, if it is added with the value “true” at the end of a segment and between

this segment and the next segment, should be stopover according to the IATA standards. Then, it will

be treated as a connection in ancillary pricing.


2.2.1.2 F a r e I n f o


• In “FareInfo” element all information from fare component is added. They are:

– Attribute “id” – should be the reference from “FareInfoRef” in “FareBreakAssociation”

– “FareComponentID”

– "GoverningCarrier"

– "FareAmount"

– "FareBasisCode" – Fare basis code with output ticket designator added after a slash (/).

– "FareType"

– "ATPCO_FareTariff"

– "ATPCO_FareRule"

– "FareIndicator"

– "PrivateTariffIndicator"

– "FareTypeBitmap"

– "FareVendorCode"

– "Brand"

Elements "FareType", "ATPCO_FareTariff", "ATPCO_FareRule", "FareIndicator",

"PrivateTariffIndicator", and "FareTypeBitmap" are rare. They are part of fare pricing. They should be

sent if the carrier uses them also in ancillaries’ records (for example, if a carrier uses private/public fare

indicator in the S7 rules).


2.2.1.3 R e q u e s t O p t i o n s

These are additional fields that can contain information that has influence on pricing ancillaries,

including:

• OriginalPricingCommand – Contains pricing WP entry with all qualifiers. For example,

WPB19JAN18 may cause ancillaries to be returned with the back date instead of the accurate date.

• TicketingPointOverride – Contains ticketing point override used in pricing qualifier.

• SalePointOverride – Contains sale point override used in pricing qualifier.

• priceUsingFillingValidAt – Price ancillaries using filling valid at historical date.

• PriceNiceAndCheap – WPNC/WPNCS.

<RequestOptions>

<OriginalPricingCommand>WPB19JAN18</OriginalPricingCommand>

<TicketingPointOverride>DFW</TicketingPointOverride>

<SalePointOverride>DFW</SalePointOverride>

<priceUsingFillingValidAt></priceUsingFillingValidAt>

<PriceNiceAndCheap>WPNC</PriceNiceAndCheap>

</RequestOptions>

This is mostly applicable to flight-related ancillaries, not baggage.

2-20 Pre-Ticketed Path Stateful/Booking/QueryByPassenger User Guide August 2018

2.3 P r e - T i c k e t e d P a t h

S t a t e f u l / B o o k i n g / Q u e r y B y P a s s e n g e r

QueryByPassenger is used in a stateful request type. The PNR in the work area needs to be available, so

that the system can retrieve PriceQuote data from GetReservationRS. Also, if there are multiple PQs for

multiple passengers, only one PQ per passenger is supported although the schema enables more

flexibility.


Request Type Mode Minimum parameters

required in request

Stateful (itinerary criteria are taken from session)

booking Version

Request type

Request mode

QueryByPassenger


• QueryByPassenger (see “QueryByPassenger” page 2-21).

User Guide August 2018 Pre-Ticketed Path Stateful/Booking/QueryByPassenger 2-21

2.3.1.1 Q u e r y P a s s e n g e r

Data in QueryByPassenger includes:

• Price Quote − Retains the most current fare based on your pricing qualifiers.

- Number (Price Quote Number).

- Attributes reference to passenger (number).

• PassengerRef:

- Attributes PassengerReferenceNumber that has reference to PNR.

- id (XML id).


• Request example (see “Request Example,” page 2-22).

• Response example (see “Response Example,” page 2-22).

2-22 Pre-Ticketed Path Stateful/Booking/QueryByPassengerType User Guide August 2018

2.3.1.1.1 Request Example

<ns9:GetAncillaryOffersRQ version="3.0.0"

xmlns:ns9="http://services.sabre.com/merch/ancillary/offer/v03" >

<ns9:RequestType>stateful</ns9:RequestType>

<ns9:RequestMode>booking</ns9:RequestMode>

<ns9:QueryByPassenger>

</ns9:QueryByPassenger>

</ns31:PassengerOffers>

2.3.1.1.2 Response Example

<ns31:PassengerOffers>

<ns9:PassengerReference passengerType="ADT" nameReferenceNumber="01.01"

nameAssociationId="1" passengerId="2"/>

<ns9:OfferRefs>

offer_ancillary_17 offer_ancillary_16 offer_ancillary_15 offer_ancillary_14




offer_ancillary_4 offer_ancillary_10 offer_ancillary_3

</ns9:OfferRefs>


2.4 P r e - T i c k e t e d P a t h

S t a t e f u l / B o o k i n g / Q u e r y B y P a s s e n g e r T y p e

QueryByPassengerType is used in a stateful request type. The PNR in the work area needs to be

available.

Ancillaries will be priced based on the passenger type specified in the GetAncillaryOffers request.



required in request


booking Version

Request type

Request mode

QueryByPassengerType

User Guide August 2018 Post-Ticketed Path Payload/Booking 2-23


• QueryByPassengerType (see this page).

2.4.1.1 Q u e r y B y P a s s e n g e r T y p e

QueryByPassengerType is used to build a request for a generic passenger type, such as ADT and MIL.

In this case, ticket and PQ data will be ignored.

2.5 P o s t - T i c k e t e d P a t h P a y l o a d / B o o k i n g

This is the path applicable for payload request type and booking mode when ticketing data is available in

the GetAncillaryOffers request. There are two ways of sending ticketing data in the GetAncillaryOffers

request:

• The VCR number needs to be passed in the ticketReferenceNumber attribute from the

PassengerItinerary element. In this scenario, ticketing will be called. In PassengerSegment, the

ticketCouponNumber attribute needs to be passed. Ticketing data (such as passenger type) takes

precedence over data in GetAncillaryOffersRQ.

• The Ticket element, along with coupon details, needs to be passed in GetAncillaryOffersRQ. In this

scenario, ticketing will not be called, and data from those elements will be used to price ancillaries

based on VCR data. In this case, ticketReferenceNumber needs to be empty so that ticketing will not

be called.

2-24 Post-Ticketed Path Payload/Booking User Guide August 2018


Request Type Mode Minimum parameters required in request

Payload (itinerary criteria are taken from request)

booking Version

Request type

Request mode

Client context

(client type, AgentCurrencyCode – if ancillaries

need to be priced in a given currency)

QueryByItinerary

1. ticketReferenceNumber and ticketCouponNr

2. Ticket information in GAO request (Ticket and

Coupon)


• QueryByItinerary/ticketReferenceNumber (see this page).

• QueryByItinerary/Ticket (see “QueryByItinerary/Ticket,” page 2-25).

• QueryByItinerary/Coupon (see “QueryByItinerary/Coupon,” page 2-26).

2.5.1.1 Q u e r y B y I t i n e r a r y / t i c k e t R e f e r e n c e N u m b e r

VCR data (along with ticketCouponNumber) needs to be passed to GetAncillaryOffers request, so that the

system can call ticketing and retrieve data needed for ancillary pricing.

User Guide August 2018 Post-Ticketed Path Payload/Booking 2-25

2.5.1.2 Q u e r y B y I t i n e r a r y / T i c k e t

Sending ticket data in the request:

• The “ticketReferenceNumber” attribute must be empty.

• Under PassengerItinerary in “ticket” element is sent:

2-26 Post-Ticketed Path Payload/Booking User Guide August 2018

– Attributes “id” and “number”.

– IssuanceDate – Date when the ticket was issued. All baggage records including Prepaids are

returned according to this date. For example, if the ticket was issued on 12JAN2018 and a baggage

record was added to the database after that date, that record will not be processed for this

GetAncillaryOffers RQ.

– Agent – Information about who issued the ticket (“WorkLocation”, “TicketingProvider”, “Duty”,

and “SystemProvider").

– “CorporateId”

– "TourCode"

– "AccountCode"

2.5.1.3 Q u e r y B y I t i n e r a r y / C o u p o n

Under “PassengerSegment”, in “Coupon” element, the following coupon data is sent:

• Attributes “id” and “number”, which is a coupon number.

• TicketDesignator – Input ticket designator.

• TicketedAllowance – Allowance issued on a ticket (this is a mandatory element).

User Guide August 2018 Post-Ticketed Path Stateful/Booking/QueryByTicket 2-27

2.6 P o s t - T i c k e t e d P a t h S t a t e f u l / B o o k i n g / Q u e r y B y T i c k e t

This is the path applicable for stateful request type and booking mode. The PNR needs to be available in

the working area, and tickets need to be saved in the PNR. When ticket number is provided in the

GetAncillaryOffers request, the system will retrieve details about a given VCR, and it will be passed to

pricing, so that ancillaries will be priced based on ticketing data.



required in request


booking Version

Request type

Request mode

Client context

(client type,

AgentCurrencyCode – if

ancillaries need to be priced in

a given currency)

QueryByTicket


• QueryByTicket (see this page).

2.6.1.1 Q u e r y B y T i c k e t

QueryByPassengerTicket is used to build a request for a given ticket number in a reservation.

This can be used when there is more than one ticket number in the reservation.

2-28 Post-Ticketed Path Stateful/Booking/QueryByTicket User Guide August 2018

• • •



GetAncillaryOffersRS returns all ancillaries that passed validation to the request according to search

criteria specified in Ancillary Request Options and Carrier configuration.

Each ancillary is represented by four main elements, which are linked together by reference

attributes:

• AncillaryDefinition (see “AncillaryDefinition,” page 3-2).

• Ancillary (see “Ancillary,” page 3-3).

• Offers (see “Offers,” page 3-4).

• PassengerOffers (see “PassengerOffers,” page 3-5).

• ResponseOptions (see “ResponseOptions,” page 3-6).

3 GetAncillaryOffers Response 3

3-2 AncillaryDefinition User Guide August 2018

3.2 A n c i l l a r y D e f i n i t i o n

AncillaryDefinition contains information that defines a subcode (S5 records). In the whole GAO RS,

there will be only one AncillaryDefinition per subcode.

The most important elements are:

• Subcode: <SubCode>0GO</SubCode>

• Airline owning the record: <Airline>K0</Airline>

• Commercial name from S5 record:

<CommercialName>UPTO50LB 23KG AND62LI 158LCM</CommercialName>

• Descriptions from S5 record:

<Description1>

<Description1Code>23</Description1Code>

<Description1Text>UP TO 50 POUNDS/23 KILOGRAMS</Description1Text>

</Description1>

<Description2>

<Description2Code>6U</Description2Code>

<Description2Text>UP TO 62 LINEAR INCHES/158 LINEAR CENTIMETERS</Description2Text>

</Description2>

• Group: <Group>BG</Group>

• SubGroup: <SubGroup>SP</SubGroup>

• Baggage weight and size limits in different units:

<BaggageWeightLimit>

<Weight unit="KILO">23</Weight>

<LimitType>U</LimitType>

</BaggageWeightLimit>

<BaggageWeightLimit>

<Weight unit="POUND">50</Weight>


</BaggageWeightLimit>

<BaggageSizeLimit>

<BaggageSize unit="INCH">62</BaggageSize>


</BaggageSizeLimit>

<BaggageSizeLimit>

<BaggageSize unit="CM">158</BaggageSize>


</BaggageSizeLimit>

• Reason for issuance:

<ReasonForIssuance code="C">BAGGAGE</ReasonForIssuance>

• EMD Type:

<ElectronicMiscDocType code="2">FLIGHT_COUPON_ASSOCIATED</ElectronicMiscDocType>

User Guide August 2018 Ancillary 3-3

3.3 A n c i l l a r y

Ancillary element contains part of the information from S7 record. The most important is:

• Service type: <ServiceType>P</ServiceType>

• Sector/Portion indicator from S7: <SectorPortionInd>P</SectorPortionInd>

• Baggage occurrence from S7:

<BaggageData>

<FirstOccurrence>1</FirstOccurrence>

<LastOccurrence>1</LastOccurrence>

</BaggageData>

• Sequence number from S7: <SequenceNumber>107330</SequenceNumber>

• Travel effective date and Last travel permitted from S7:

<TravelDateEffective>1980-01-01</TravelDateEffective>

<LatestTravelDatePermitted>9999-12-31</LatestTravelDatePermitted

There might be more than one Ancillary element linked to the same AncillaryDefinition. There will

be multiple ancillary elements if different sequence number, service type, or occurrences are returned.

Baggage occurrence is also used in order to return information about the first and second Standard

Bag.

Business logic for returning the first and second Standard Bag is based on the ATPCO sub codes list.

Sub Code Group Description ATPCO Commercial Name RFIC

0CC BG – Baggage B1 - First Bag CHECKED BAG FIRST C

0CD BG – Baggage B2 - Second Bag CHECKED BAG SECOND C

0CE BG – Baggage B3 - Third Bag CHECKED BAG THIRD C

3-4 Offers User Guide August 2018

Sub Code Group Description ATPCO Commercial Name RFIC

0CF BG – Baggage B4 - Fourth Bag CHECKED BAG FOURTH C

0CG BG – Baggage B5 - Fifth Bag CHECKED BAG FIFTH C

0CH BG – Baggage B6 - Sixth Bag CHECKED BAG SIXTH C

0CI BG – Baggage B7 - Seventh Bag CHECKED BAG SEVENTH C

0CJ BG – Baggage B8 - Eighth Bag CHECKED BAG EIGHTH C

0CK BG – Baggage B9 - Ninth Bag CHECKED BAG NINTH C

0EN BG – Baggage B0 - Tenth Bag CHECKED BAG TENTH C

In the case of OW and two segments, information about the standard bag will be returned in the

following order: 0CC, OCD, OCE if the sub codes are available for both segments. Other ATPCO

sub codes (such as 0GO) will be not returned as Standard Bag.

In the case of RT with four segments, separate baggage numeration will be returned for each portion.

3.4 O f f e r s

Element Offers contains information about segments to which the record is returned and the record

price calculation including base price, possible discounts, currency conversions, taxes, and the total

price.

The elements are:

• Origin and destination – as filed in S7 record

<Origin >SPS</Origin>

<Destination >PHX</Destination>

• AncillaryFee – Ancillary fee details for a single ancillary record with discount and ancillary (with

discount and quantity).

– Unavailable – if the fee can be sold to a traveler, it will contain value “false”. However, if in

the S7 record, in the field NOT AVL/CHG (byte 288), there is the value “X” (which means not

available), GetAncillaryOffers will send <Unavailable>true</Unavailable>, and a traveler

is not allowed to buy the record.

– DisplayOnly - Indicates this ancillary can be displayed, but not booked or purchased.

• BaseAncillaryFee – Ancillary fee details for a single ancillary record and an ancillary with

quantity.

• AncillaryRules – Rules defined for an ancillary, such as refundability or form of payment.

• Deal – Information about the Dynamic Retailer rule applied for a given ancillary.

• LinkedAE – Retrieved only for bundles ancillaries.

User Guide August 2018 PassengerOffers 3-5

• Segment – Information about inventory on segment level.

• PurchaseByDate –Latest date this ancillary can be purchased.

• IsDisclosurePart – Retrieved only for baggage group, indicates that this ancillary is part of

disclosure message.

• PaperTicketRequired – Paper ticket required.

3.5 P a s s e n g e r O f f e r s

The PassengerOffers element contains references to all offers returned for the passenger.


<ns9:PassengerReference xmlns:ns9="http://services.sabre.com/merch/ancillary/v03"

passengerType="ADT" passengerId="pax_adt1"/>

<ns9:OfferRefs

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">offer_ancillary_17


offer_ancillary_36 offer_ancillary_25 offer_ancillary_19</ns9:OfferRefs>



• Response with OfferRefs – pre-ticketed (see this page).

• Response with ticket/coupon – post-ticketed (see “Response with Ticket/Coupon – Post-

Ticketed,” page 3-6).

3.5.1 R e s p o n s e w i t h O f f e r R e f s – P r e - T i c k e t e d



nameAssociationId="1" passengerId="2” />

<ns9:OfferRefs>


</ns9:OfferRefs>



<ns9:PassengerReference passengerType="CNN" nameReferenceNumber="02.01"


<ns9:OfferRefs>


</ns9:OfferRefs>



<ns9:PassengerReference passengerType="INF" nameReferenceNumber="03.01"

nameAssociationId="3" passengerId="6„>

<ns9:OfferRefs>


3-6 ResponseOptions User Guide August 2018

</ns9:OfferRefs>


3.5.2 R e s p o n s e w i t h T i c k e t / C o u p o n – P o s t - T i c k e t e d




<ns9:Ticket number="6077015706750">

<ns9:CouponAssociation>

<ns9:OfferRefs>


offer_ancillary_9

</ns9:OfferRefs>

<ns9:Coupon>1</ns9:Coupon>

</ns9:CouponAssociation>


<ns9:OfferRefs>


offer_ancillary_22

</ns9:OfferRefs>



</ns9:Ticket>



<ns9:PassengerReference passengerType="CHD" nameReferenceNumber="02.01"


<ns9:Ticket number="6077015706751">


<ns9:OfferRefs>


offer_ancillary_9

</ns9:OfferRefs>



3.6 R e s p o n s e O p t i o n s

Element RequestOptions contains information about ATTNIndicator, EmptyGroupList, and

InactiveGroupList. This is used only by Liberty in WP*AE display.

The elements are:

• ATTNIndicator – ATTNInidcator

• EmptyGroupList – Information about group of ancillaries that are empty.

• InactiveGroupList – Information about inactive group codes.

User Guide August 2018 ResponseOptions 3-7

3-8 ResponseOptions User Guide August 2018

• • •



This chapter includes the following examples:

• GetAncillaryOffers RQ with ticket number stateful (see this page).

• GetAncillaryOffers RQ with ticket number payload (see “GetAncillaryOffers RQ with Ticket

Number Payload,” page 4-10).

• GetAncillaryOffers RQ multi-segment payload (see “GetAncillaryOffers RQ Multi-Segment

Payload,” page 4-13).

• GetAncillaryOffers RQ multi-passenger stateful (see “GetAncillaryOffers RQ Multi-Pax

Stateful,” page 4-15).

• GetAncillaryOffers RQ multi-passenger payload (see “GetAncillaryOffers RQ Multi-Pax


• GetAncillaryOffers RQ multi-passenger, multi-segment, multi-fare (see “GetAncillaryOffers RQ

Multi-Pax Payload,” page 4-16)

4.2 G e t A n c i l l a r y O f f e r s R Q w i t h T i c k e t N u m b e r S t a t e f u l

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

<soap-env:Header>

<wsse:Security xmlns:wsse="http://docs.oasis-

open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<wsse:BinarySecurityToken EncodingType="http://docs.oasis-

open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"

ValueType="wsse:X509v3">U2hhcmVkL0lETDpJY2VTZXNzXC9TZXNzTWdyOjFcLjAuSURML0NvbW1vb

i8hSUNFU01TXC9TVFNCIUlDRVNNU0xCXC9TVFMuTEIhLTMxNjQzOTYzMTYzMjQzNjk3ODQhMTYzMjAwMS

Ew</wsse:BinarySecurityToken>

</wsse:Security>

<stlh2:SabreHeader

xmlns:stlh2="http://services.sabre.com/STL_Header/v02_01">

<stlh2:Service version="3.0.0"

ttl="20">GetAncillaryOffersRQ</stlh2:Service>

<stlh2:Identification>

<stlh2:CustomerID>K0</stlh2:CustomerID>

<stlh2:ConversationID>[email protected]</stlh2:ConversationID>

<stlh2:MessageID>607845307446990870</stlh2:MessageID>

<stlh2:TimeStamp>2018-03-26T03:32:24-

05:00</stlh2:TimeStamp>

</stlh2:Identification>

<stlh2:Traces>

<stlh2:Trace start="2018-03-26T03:32:24-05:00"

end="2018-03-26T03:32:24-05:00" appInstance="usg-cert-tsts0" host="c233"

role="gateway" key="607845307446990870">USG1</stlh2:Trace>

4 GetAncillaryOffers Request Examples 4

4-10 GetAncillaryOffers RQ with Ticket Number Payload User Guide August 2018

</stlh2:Traces>

</stlh2:SabreHeader>

</soap-env:Header>

<soap-env:Body>

<n18:GetAncillaryOffersRQ

xmlns:n18="http://services.sabre.com/merch/ancillary/offer/v03"

xmlns:n1="http://www.w3.org/1999/xlink"

xmlns:n32="http://services.sabre.com/merch/baggage/v03"

xmlns:n21="http://services.sabre.com/merch/ancillary/v03"

xmlns:n20="http://services.sabre.com/merch/common/v03"

xmlns:n12="http://www.w3.org/2000/09/xmldsig#"

xmlns:n22="http://services.sabre.com/merch/flight/v03" xmlns:n13="urn:schemas-

sabre-com:soap-header-debug"

xmlns:n24="http://services.sabre.com/merch/itinerary/v03"

xmlns:n15="http://stl.sabre.com/Merchandising/diagnostics/v2"

xmlns:stlp2_02="http://services.sabre.com/STL_Payload/v02_01"

xmlns:n17="http://services.sabre.com/merch/passenger/v03"

xmlns:n19="http://services.sabre.com/merch/request/v03"

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

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

<n18:RequestType>stateful</n18:RequestType>

<n18:RequestMode>booking</n18:RequestMode>

<ns9:ClientContext clientType="LIBERTY">

<ns12:CityCode>MEX</ns12:CityCode>

<ns12:PCC>F4X0</ns12:PCC>

<ns12:AgentCurrencyCode>EUR</ns12:AgentCurrencyCode>

<ns12:OfficeAccountInformation>

<ns12:PersonalAccountingCityCode>BER</ns12:PersonalAccountingCityCode>

<ns12:PersonalAccountingCode>CODE</ns12:PersonalAccountingCode>

<ns12:PersonalOfficeCode>BER</ns12:PersonalOfficeCode>

</ns12:OfficeAccountInformation>

</ns9:ClientContext>

<n18:QueryByTicket>

<n18:TicketReferenceNumber>5557049020060</n18:TicketReferenceNumber>

</n18:QueryByTicket>

</n18:GetAncillaryOffersRQ>

</soap-env:Body>

</soap-env:Envelope

4.3 G e t A n c i l l a r y O f f e r s R Q w i t h T i c k e t N u m b e r P a y l o a d

soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">

<soap-env:Header>






i8hSUNFU01TXC9BQ1BDUlREIUlDRVNNU0xCXC9DUlQuTEIhLTMxNjQ0MDc1MTgyNzQxNjM4MzAhNTAxMz

g3ITA=</wsse:BinarySecurityToken>

</wsse:Security>

User Guide August 2018 GetAncillaryOffers RQ with Ticket Number Payload 4-11

<stlh2:SabreHeader






<stlh2:ConversationID>[email protected]</stlh2:ConversationID>


<stlh2:TimeStamp>2018-03-26T02:47:46-



<stlh2:Traces>


end="2018-03-26T02:47:46-05:00" appInstance="usg-cert-certc0" host="c036"


</stlh2:Traces>


</soap-env:Header>

<soap-env:Body>



xmlns:n63="http://services.sabre.com/merch/ticket/v03"






xmlns:n26="urn:schemas-sabre-com:soap-header-debug"



xmlns:n28="http://stl.sabre.com/Merchandising/diagnostics/v2"

xmlns:n17="http://services.sabre.com/merch/flight/v03"




<n11:RequestType>payload</n11:RequestType>












<n11:QueryByItinerary>

<n11:QueryPassengerItinerary>

4-12 GetAncillaryOffers RQ with Ticket Number Payload User Guide August 2018

<n11:Passenger id="p_01.01"

nameReferenceNumber="01.01"/>

<n11:PassengerItinerary

ticketReferenceNumber="0552337014208">

<n11:PassengerSegment

segmentRef="seg_1"/>

</n11:PassengerItinerary>

</n11:QueryPassengerItinerary>

<n11:Segment id="seg_1">

<n15:FlightDetail id="flight_zly">

<n17:Airline>K0</n17:Airline>

<n17:FlightNumber>852</n17:FlightNumber>

<n17:DepartureAirport>FCO</n17:DepartureAirport>

<n17:DepartureDate>2018-05-

20</n17:DepartureDate>

<n17:DepartureTime>11:15:00</n17:DepartureTime>

<n17:ArrivalAirport>SYD</n17:ArrivalAirport>

<n17:OperatingAirline>K0</n17:OperatingAirline>

<n17:OperatingFlightNumber>852</n17:OperatingFlightNumber>

<n17:ClassOfService>Y</n17:ClassOfService>

</n15:FlightDetail>

</n11:Segment>

</n11:QueryByItinerary>


</soap-env:Body>

</soap-env:Envelope>

User Guide August 2018 GetAncillaryOffers RQ Multi-Segment Payload 4-13

4.4 G e t A n c i l l a r y O f f e r s R Q M u l t i - S e g m e n t P a y l o a d

<ns9:GetAncillaryOffersRQ xmlns:ns2="http://www.w3.org/2000/09/xmldsig#"

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

xmlns:ns4="http://www.w3.org/1999/xlink"

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

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

xmlns:ns8="http://services.sabre.com/STL_Payload/v02_01" xmlns:ns7="urn:schemas-

sabre-com:soap-header-debug"

xmlns:ns13="http://services.sabre.com/merch/passenger/v03"

xmlns:ns9="http://services.sabre.com/merch/ancillary/offer/v03"

xmlns:ns12="http://services.sabre.com/merch/request/v03"

xmlns:ns11="http://services.sabre.com/merch/common/v03"

xmlns:ns10="http://services.sabre.com/merch/ancillary/v03"

xmlns:ns17="http://stl.sabre.com/Merchandising/diagnostics/v2"

xmlns:ns16="http://services.sabre.com/merch/flight/v03"

xmlns:ns15="http://services.sabre.com/merch/ticket/v03"

xmlns:ns14="http://services.sabre.com/merch/itinerary/v03">

<ns9:RequestType>payload</ns9:RequestType>

<ns9:RequestMode>booking</ns9:RequestMode>











<ns9:AncillaryRequestOptions>

<ns10:ServiceType>C</ns10:ServiceType>

<ns10:Group>BG</ns10:Group>

<ns10:Subcode>0MJ</ns10:Subcode>

</ns9:AncillaryRequestOptions>


<ns10:ServiceType>F</ns10:ServiceType>

<ns10:Group>UN</ns10:Group>



<ns10:Subcode>0B5</ns10:Subcode>


<ns9:QueryByItinerary>

<ns9:QueryPassengerItinerary>

<ns9:Passenger id="pass_21.19"

accompaniedByInfant="false" type="ADT">

<ns13:PersonName>

<ns13:Prefix>DR</ns13:Prefix>

<ns13:First>MAD</ns13:First>

<ns13:Last>MAX</ns13:Last>

<ns13:Suffix>JR</ns13:Suffix>

4-14 GetAncillaryOffers RQ Multi-Segment Payload User Guide August 2018

<ns13:Raw>MM</ns13:Raw>

</ns13:PersonName>

<ns13:DateOfBirth>2012-10-23</ns13:DateOfBirth>

<ns13:LoyaltyAccounts>

<ns13:LoyaltyAccountWithId id="pass_21.19_ff_1" memberAirline="XX"

memberId="123123123" partnerProgram="XX" eliteStatus="GOLD"

premiumCreditCard="123697456" tierTag="GLD" tierNumber="45862"/>

<ns13:LoyaltyAccountWithId id="pass_21.19_ff_2" memberAirline="K0"

memberId="987654321" partnerProgram="XX" eliteStatus="RUBY"

premiumCreditCard="1122334455" tierTag="RBY" tierNumber="123"/>

</ns13:LoyaltyAccounts>

</ns9:Passenger>

<ns9:PassengerItinerary>

<ns9:PassengerSegment segmentRef="seg_1">

<ns14:FareBreakAssociation FareInfoRef="a9">

<SideTripId>0</SideTripId>

<SideTripStartIndicator>false</SideTripStartIndicator>

<SideTripEndIndicator>false</SideTripEndIndicator>

</ns14:FareBreakAssociation>

</ns9:PassengerItinerary>

</ns9:QueryPassengerItinerary>

<ns9:Segment id="seg_1">

<ns14:FlightDetail id="f5">

<ns16:Airline>K0</ns16:Airline>

<ns16:FlightNumber>789</ns16:FlightNumber>

<ns16:DepartureAirport>MEX</ns16:DepartureAirport>

<ns16:DepartureDate>2018-02-21</ns16:DepartureDate>

<ns16:DepartureTime>09:45:00</ns16:DepartureTime>

<ns16:ArrivalAirport>CUN</ns16:ArrivalAirport>

<ns16:ArrivalDate>2018-02-21</ns16:ArrivalDate>

<ns16:ArrivalTime>11:10:00</ns16:ArrivalTime>

<ns16:OperatingAirline>K0</ns16:OperatingAirline>

<ns16:OperatingFlightNumber>789</ns16:OperatingFlightNumber>

<ns16:ClassOfService>Y</ns16:ClassOfService>

User Guide August 2018 GetAncillaryOffers RQ Multi-Pax Stateful 4-15

<ns16:OperatingClassOfService>Y</ns16:OperatingClassOfService>

<ns16:Cabin>C</ns16:Cabin>

<ns16:Equipment>EQP</ns16:Equipment>

<ns16:ReservationStatus>OK</ns16:ReservationStatus>

<ns16:ForcedConnectionInd>false</ns16:ForcedConnectionInd>

<ns16:ForcedStopoverInd>false</ns16:ForcedStopoverInd>

<ns16:HiddenStopPoint>KRK</ns16:HiddenStopPoint>

<ns16:NewEquipmentType>EQP</ns16:NewEquipmentType>

</ns14:FlightDetail>

</ns9:Segment>

<ns9:FareInfo id="a9">

<FareComponentID>2</FareComponentID>

<GoverningCarrier>XX</GoverningCarrier>

<FareAmount>10</FareAmount>

<FareBasisCode>CODE</FareBasisCode>

<FareType>T</FareType>

<ATPCO_FareTariff>12</ATPCO_FareTariff>

<ATPCO_FareRule>RULE</ATPCO_FareRule>

<FareIndicator>20</FareIndicator>

<PrivateTariffIndicator>true</PrivateTariffIndicator>

<FareTypeBitmap>BITMAP</FareTypeBitmap>

<FareVendorCode>POL</FareVendorCode>

<Brand>CLASSIC</Brand>

</ns9:FareInfo>

</ns9:QueryByItinerary>

</ns9:GetAncillaryOffersRQ>

4.5 G e t A n c i l l a r y O f f e r s R Q M u l t i - P a x S t a t e f u l

soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">

<soap-env:Header>






i8hSUNFU01TXC9BQ1BDUlREIUlDRVNNU0xCXC9DUlQuTEIhLTMxNjYwOTI5Njg2NjgyMTM2MjEhMTc5MD

Y1MSEw</wsse:BinarySecurityToken>

</wsse:Security>

4-16 GetAncillaryOffers RQ Multi-Pax Payload User Guide August 2018

<stlh2:SabreHeader






<stlh2:ConversationID>1-

1521639228820</stlh2:ConversationID>


<stlh2:TimeStamp>2018-03-21T08:33:51-



<stlh2:Traces>




</stlh2:Traces>


</soap-env:Header>

<soap-env:Body>



xmlns:n0="http://services.sabre.com/STL/v02"

xmlns:n1="http://www.OpenTravel.org/ns/OTA2/AppInfo_v01_00"

xmlns:n2="http://opentravel.org/common/message/v02"

xmlns:n3="http://opentravel.org/common/v02"




xmlns:n27="http://services.sabre.com/merch/baggage/v03"








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

xmlns:stlh2="http://services.sabre.com/STL_Header/v02_01" version="3.0.0">

<n11:RequestType>stateful</n11:RequestType>


<n11:QueryByPassengerType>

<n11:PassengerType type="ADT"/>

<n11:PassengerType type="CHD"/>

<n11:PassengerType type="INF"/>

</n11:QueryByPassengerType>


</soap-env:Body>


4.6 G e t A n c i l l a r y O f f e r s R Q M u l t i - P a x P a y l o a d

<soap-env:Header>





User Guide August 2018 GetAncillaryOffers RQ Multi-Pax Payload 4-17


i8hSUNFU01TXC9DRVJURyFJQ0VTTVNMQlwvQ1JULkxCIS0zMTY0NDkzNDc5ODIxNzE2ODUzITEyNTYwMz

AhMCE5</wsse:BinarySecurityToken>

</wsse:Security>

<stlh2:SabreHeader






<stlh2:ConversationID>com.sabre.serviceengine.services.baggage.v3.GetBagga

geInformationBasic_RegularOWNoPaxDetails_Baggage_ee59b808-

5</stlh2:ConversationID>


<stlh2:TimeStamp>2018-03-25T21:01:41-



<stlh2:Traces>




</stlh2:Traces>


</soap-env:Header>

<soap-env:Body>








xmlns:n12="http://services.sabre.com/STL/v3"








<n15:RequestMode>Booking</n15:RequestMode>

<n15:ClientContext clientType="LIBERTY">

<n50:CityCode>ELS</n50:CityCode>


<n50:AgentCurrencyCode>AED</n50:AgentCurrencyCode>

</n15:ClientContext>

<n15:AncillaryRequestOptions>

<n51:ServiceType>D</n51:ServiceType>

</n15:AncillaryRequestOptions>

<n15:QueryByItinerary>


<n15:Passenger id="p1"

nameReferenceNumber="1.1" type="ADT"/>

<n15:PassengerItinerary>

<n15:PassengerSegment segmentRef="SEG13">

<n55:FareBreakAssociation

FareInfoRef="fi_1"/>

</n15:PassengerSegment>


4-18 GetAncillaryOffers RQ Multi-Pax Payload User Guide August 2018




nameReferenceNumber="2.1" type="CHD"/>










nameReferenceNumber="3.1" type="INF"/>








<n15:Segment id="SEG13">

<n55:FlightDetail id="f1">



<n52:DepartureAirport>AUH</n52:DepartureAirport>



<n52:DepartureTime>21:30:00.000</n52:DepartureTime>

<n52:ArrivalAirport>BAH</n52:ArrivalAirport>

<n52:ArrivalDate>2018-03-

27</n52:ArrivalDate>

<n52:ArrivalTime>21:40:00.000</n52:ArrivalTime>


<n52:ClassOfService>V</n52:ClassOfService>

<n52:Cabin>Y</n52:Cabin>

<n52:Equipment>32A</n52:Equipment>

</n55:FlightDetail>

</n15:Segment>

<n15:FareInfo id="fi_1">

<GoverningCarrier>K0</GoverningCarrier>

<FareAmount>0.99</FareAmount>

<FareBasisCode>VSP1OWAE/YS</FareBasisCode>

<FareType>BU</FareType>


<ATPCO_FareRule>K0ST</ATPCO_FareRule>

<FareIndicator>35</FareIndicator>

<PrivateTariffIndicator>false</PrivateTariffIndicator>

<FareVendorCode>ATP</FareVendorCode>

</n15:FareInfo>



</soap-env:Body>


User Guide August 2018 GetAncillaryOffers RQ Multi-Pax Multi-Segment Multi-Fare Payload 4-19

4.7 G e t A n c i l l a r y O f f e r s R Q M u l t i - P a x M u l t i - S e g m e n t

M u l t i - F a r e P a y l o a d


<soap-env:Header>






i8hSUNFU01TXC9TVFNCIUlDRVNNU0xCXC9TVFMuTEIhMTUzMjQxOTk3NzY1OCEyOTgyMjkhMTMxMDczIT

IhRTJFLTE=</wsse:BinarySecurityToken>

</wsse:Security>

<stlh2:SabreHeader





<stlh2:CustomerID>AA</stlh2:CustomerID>

<stlh2:ConversationID>missing conversationId from

PDC</stlh2:ConversationID>


<stlh2:TimeStamp>2018-07-24T03:31:51-



<stlh2:Traces>


end="2018-07-24T03:31:51-05:00" appInstance="usg-cert-tsts0" host="c233"


</stlh2:Traces>


</soap-env:Header>

<soap-env:Body>



xmlns:n1="http://services.sabre.com/merch/ancillary/v03" version="3.0.2">



<n0:ClientContext

xmlns:n12="http://services.sabre.com/merch/request/v03" clientType="PDC">

<n12:AgentCurrencyCode>USD</n12:AgentCurrencyCode>

</n0:ClientContext>

<n0:QueryByItinerary



xmlns:n16="http://services.sabre.com/merch/fare/v03"

xmlns:n15="http://services.sabre.com/merch/passenger/v03">


<n0:Passenger id="passenger_1_clone_1"

type="ADT"/>



segmentRef="segment_1">


FareInfoRef="fareInfo_1_passenger_1"/>






4-20 GetAncillaryOffers RQ Multi-Pax Multi-Segment Multi-Fare Payload User Guide August 2018






type="CNN"/>
















type="INF"/>














<n0:Segment id="segment_1">

<n13:FlightDetail id="flight_segment_1">

<n14:Airline>AZ</n14:Airline>


<n14:DepartureAirport>FCO</n14:DepartureAirport>




<n14:ArrivalAirport>AUH</n14:ArrivalAirport>



<n14:ArrivalTime>19:20:00</n14:ArrivalTime>

<n14:OperatingAirline>AZ</n14:OperatingAirline>

<n14:ClassOfService>H</n14:ClassOfService>


<n14:Equipment>330</n14:Equipment>

<n14:ReservationStatus>OK</n14:ReservationStatus>

</n13:FlightDetail>

<n13:RecordCreateTag/>

User Guide August 2018 GetAncillaryOffers RQ Multi-Pax Multi-Segment Multi-Fare Payload 4-21

</n0:Segment>

<n0:Segment id="segment_2">

<n13:FlightDetail id="flight_segment_2">



<n14:DepartureAirport>AUH</n14:DepartureAirport>




<n14:ArrivalAirport>SYD</n14:ArrivalAirport>



<n14:ArrivalTime>17:50:00</n14:ArrivalTime>


<n14:ClassOfService>Y</n14:ClassOfService>


<n14:Equipment>388</n14:Equipment>

<n14:ReservationStatus>OK</n14:ReservationStatus>

</n13:FlightDetail>

<n13:RecordCreateTag/>

</n0:Segment>

<n0:FareInfo id="fareInfo_1_passenger_1">

<GoverningCarrier>YY</GoverningCarrier>


<FareBasisCode>YIF</FareBasisCode>

<FareType>EU</FareType>


<ATPCO_FareRule>62DD</ATPCO_FareRule>

<FareTypeBitmap>00</FareTypeBitmap>

</n0:FareInfo>


<GoverningCarrier>EY</GoverningCarrier>


<FareBasisCode>YOW11/YF</FareBasisCode>



<ATPCO_FareRule>K0YY</ATPCO_FareRule>


</n0:FareInfo>


<GoverningCarrier>K0</GoverningCarrier>


<FareBasisCode>YIF/CH25</FareBasisCode>





</n0:FareInfo>




<FareBasisCode>YOW11CH75/YF</FareBasisCode>



4-22 GetAncillaryOffers RQ Multi-Pax Multi-Segment Multi-Fare Payload User Guide August 2018



</n0:FareInfo>


<GoverningCarrier>YY</GoverningCarrier>


<FareBasisCode>YIF/IN90</FareBasisCode>





</n0:FareInfo>




<FareBasisCode>YOW11IN10/YF</FareBasisCode>





</n0:FareInfo>


<n0:RequestOptions

xmlns:n12="http://services.sabre.com/merch/request/v03">

<n12:priceUsingFilingValidAt>2018-07-

24</n12:priceUsingFilingValidAt>

<n12:PriceNiceAndCheap>false</n12:PriceNiceAndCheap>

</n0:RequestOptions>


</soap-env:Body>




This chapter includes the following examples:

• GetAncillaryOffers RS with ticket number payload (see this page).

• GetAncillaryOffers RS multi-segment payload (see “GetAncillaryOffers RS Multi-Segment


• GetAncillaryOffers RS multi-pax stateful (see “GetAncillaryOffers RS Multi-Pax Stateful.” page

5-10).

• GetAncillaryOffers RS multi-pax payload (see “GetAncillaryOffers RS Multi-Pax Payload,”

page 5-14).

• GetAncillaryOffers RS multi-passenger, multi-segment, multi-fare (see “GetAncillaryOffers RQ

Multi-Pax Payload,” page 5-20).

5.2 G e t A n c i l l a r y O f f e r s R S w i t h T i c k e t N u m b e r P a y l o a d

<ns31:GetAncillaryOffersRS

xmlns:ns31="http://services.sabre.com/merch/ancillary/offer/v03">

<ns16:ApplicationResults

xmlns:ns16="http://services.sabre.com/STL_Payload/v02_01" status="Complete">

<ns16:Success timeStamp="2018-03-26T02:47:47.918-

05:00"/>

<ns16:Warning timeStamp="2018-03-26T02:47:47.405-

05:00" type="BusinessLogic">

<ns16:SystemSpecificResults>

<ns16:Message

code="WARN.ANCILLARYSERVICES2.CLIENT.INVALID_REQUEST">The following tickets do

not exist in Ticketing: 0552337014208 (SID:1)</ns16:Message>

</ns16:SystemSpecificResults>

</ns16:Warning>

</ns16:ApplicationResults>

<ns31:AncillaryDefinition id="ancillary_1">

<SubCode>0DF</SubCode>

<Airline>K0</Airline>

<CommercialName>FREE BAGGAGE

ALLOWANCE</CommercialName>

<Vendor>ATP</Vendor>

<Group>BG</Group>

<GroupDescription>BAGGAGE</GroupDescription>

<ReasonForIssuance

code="C">BAGGAGE</ReasonForIssuance>

<ElectronicMiscDocType

code="2">FLIGHT_COUPON_ASSOCIATED</ElectronicMiscDocType>

<BookingMethod

code="BLANK">ANY_ALLOWED</BookingMethod>

5 GetAncillaryOffers Response

Examples

5

5-2 GetAncillaryOffers RS with Ticket Number Payload User Guide August 2018

</ns31:AncillaryDefinition>

<ns31:Ancillary ancillaryDefinitionRef="ancillary_1"

ancillaryId="ancillary_ancillary_1">

<ServiceType>A</ServiceType>

<SectorPortionInd>P</SectorPortionInd>

<BaggageAllowance>

<MaxPieces>1</MaxPieces>

<AllowedBaggageTypes>

<NumberOfPieces>1</NumberOfPieces>

<BagTypeAncillaryRef>ancillary_ancillary_2</BagTypeAncillaryRef>

</AllowedBaggageTypes>








<FreeTextSubCodeDetails>THE FOLLOWING

SPORTING EQUIPMENT UP TO 23KG/|WATER

SKI/SUB/GOLF/FISHING/|POLO/BICYCLES/SURF/107CM</FreeTextSubCodeDetails>













<FreeTextSubCodeDetails>MAX WEIGHT OF

75KG INCLUDING KENNEL AND FOOD</FreeTextSubCodeDetails>





<FreeTextSubCodeDetails>WEAPONS AND

MUNITION TOTAL - UP TO 20KG/ BUT|MUNITION CANNOT EXCEED

5KG</FreeTextSubCodeDetails>


</BaggageAllowance>

<SequenceNumber>188437</SequenceNumber>


<LatestTravelDatePermitted>9999-12-

31</LatestTravelDatePermitted>

<Footnote> </Footnote>

</ns31:Ancillary>

<ns31:Offers ancillaryRef="ancillary_ancillary_1"

offerId="offer_ancillary_1">

User Guide August 2018 GetAncillaryOffers RS with Ticket Number Payload 5-3

<ns9:Origin

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">FCO</ns9:Origin>

<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">SYD</ns9:Destination>

<ns9:AncillaryFee

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">

<Unavailable>false</Unavailable>

<TaxExemptIndicator>false</TaxExemptIndicator>

<TotalTaxes/>

<Base>

<ns2:Amount


currency="EUR">0.00</ns2:Amount>

<ns2:EquivAmount


currency="EUR">0.00</ns2:EquivAmount>

</Base>

<TTL_Price>

<ns2:EquivAmount


currency="EUR">0.00</ns2:EquivAmount>

</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules


<FreeOfChargeRules>BOOKING_REQUIRED</FreeOfChargeRules>

<SimultaneousTicketIndicator>X</SimultaneousTicketIndicator>

</ns9:AncillaryRules>

<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" segmentId="seg_1"/>

<ns9:PurchaseByDate

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">2018-03-

27</ns9:PurchaseByDate>

<ns9:IsDisclosurePart

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">true</ns9:IsDisclosureP

art>

<ns9:PaperTicketRequired

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">false</ns9:PaperTicketR

equired>

</ns31:Offers>


<ns9:PassengerReference

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03"

nameReferenceNumber="01.01"

passengerId="p_01.01"

passengerType="ADT"/>

<ns9:OfferRefs


</ns9:OfferRefs>


<ns31:ResponseOptions>

<ns31:EmptyGroupList>99 SA</ ns31:EmptyGroupList>

</ns31:ResponseOptions>

5-4 GetAncillaryOffers RS Multi-Segment Payload User Guide August 2018

5.3 G e t A n c i l l a r y O f f e r s R S M u l t i - S e g m e n t P a y l o a d






05:00"/>



<SubCode>020</SubCode>

<Airline>YY</Airline>

<CommercialName>PET IN HOLD</CommercialName>


<Group>BG</Group>


<SubGroup>PN</SubGroup>

<SubGroupDescription>PET IN HOLD</SubGroupDescription>

<BagType>AVIH</BagType>

<SpecialService>ASVC</SpecialService>

<ReasonForIssuance


<SpecialServiceDetails type="NOTALLOWED"/>



<BookingMethod

code="01">SPECIAL_SERVICE_REQUEST</BookingMethod>

<DisplayOnly>false</DisplayOnly>



<SubCode>0F2</SubCode>

<Airline>YY</Airline>

<CommercialName>MUSICAL INSTRUMENTS

LARGE</CommercialName>


<Group>BG</Group>


<SubGroup>MI</SubGroup>

<SubGroupDescription>MUSICAL

INSTRUMENTS</SubGroupDescription>

<BagType>MUSI</BagType>


<ReasonForIssuance





<BookingMethod





<SubCode>012</SubCode>

<Airline>XX</Airline>

<CommercialName>SHIP MODELS</CommercialName>

<Vendor>MMGR</Vendor>

<Group>BG</Group>


User Guide August 2018 GetAncillaryOffers RS Multi-Segment Payload 5-5

<SubGroup>SI</SubGroup>

<SubGroupDescription>SPECIALTY

ITEM</SubGroupDescription>

<BagType>SHIP</BagType>

<ReasonForIssuance




<BookingMethod




yDefinition>


<SubCode>XBG</SubCode>

<Airline>XX</Airline>

<CommercialName>EXCESS BAGGAGE PER

KILO</CommercialName>


<Group>BG</Group>


<ReasonForIssuance




<BookingMethod




<ns31:Ancillary ancillaryId="ancillary_ancillary_1"

ancillaryDefinitionRef="ancillary_1">

<ServiceType>F</ServiceType>






<AirExtraStatus>PAYMENT_REQUIRED</AirExtraStatus>

<Footnote>/</Footnote>

</ns31:Ancillary>

lary>










<Footnote>/</Footnote>

</ns31:Ancillary>











<Footnote>X</Footnote>

</ns31:Ancillary>










<Footnote>-</Footnote>

</ns31:Ancillary>

<ns31:Offers offerId="offer_ancillary_1"

ancillaryRef="ancillary_ancillary_1">

<ns9:Origin

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">FRA</ns9:Origin>

<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">MCT</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount


currency="KWD">147.550</ns2:EquivAmount>

</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules


<RefundableReissuable>Y</RefundableReissuable>

<FormOfRefund code="1">ORIGINAL</FormOfRefund>

<Commissionable>false</Commissionable>

<Interlineable>true</Interlineable>

<FeeApplicationMethod

code="3">PER_CHECKED_PORTION</FeeApplicationMethod>



<ns9:Segment


<ns9:PurchaseByDate





xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">false</ns9:IsDisclosure

Part>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">MCT</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules





<Interlineable>true</Interlineable>


code="3">PER_CHECKED_PORTION</FeeApplicationMethod>



<ns9:Segment


<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin



<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">BAH</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount


currency="USD">11.00</ns2:Amount>

<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules






code="4">PER_BAGGAGE_TRAVEL</FeeApplicationMethod>

<FeeNotGuaranteeIndicator>true</FeeNotGuaranteeIndicator>



<ns9:Segment


<ns9:Segment


<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">MCT</ns9:Origin>

<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>


<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules






code="5">TICKET</FeeApplicationMethod>




<ns9:Segment


<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" passengerType="ADT"

passengerId="pax_adt1"/>

<ns9:OfferRefs






xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" passengerType="CNN"

passengerId="pax_cnn1"/>

<ns9:OfferRefs







passengerId="pax_cnn2"/>

<ns9:OfferRefs



5-10 GetAncillaryOffers RS Multi-Pax Stateful User Guide August 2018



<ns31:EmptyGroupList>BD PT GT SB MD UN LG

IE</ns31:EmptyGroupList>


</ns31:GetAncillaryOffersRS>

5.4 G e t A n c i l l a r y O f f e r s R S M u l t i - P a x S t a t e f u l






05:00"/>



<SubCode>XW2</SubCode>


<CommercialName>2 KG EXCESS BAGGAGE

VOUCHER</CommercialName>


<Group>BG</Group>


<ReasonForIssuance




<BookingMethod





<SubCode>0BQ</SubCode>


<CommercialName>TRAIN</CommercialName>


<Group>GT</Group>

<GroupDescription>GROUND

TRANSPORTATION</GroupDescription>

<SubGroup>TN</SubGroup>

<SubGroupDescription>TRAIN</SubGroupDescription>

<ReasonForIssuance

code="B">GROUND_TRANSPORT_NON_AIR_SERVICES</ReasonForIssuance>



<BookingMethod





<SubCode>0BV</SubCode>


<CommercialName>STANDBY</CommercialName>

User Guide August 2018 GetAncillaryOffers RS Multi-Pax Stateful 5-11


<Group>SB</Group>

<GroupDescription>STANDBY</GroupDescription>

<ReasonForIssuance

code="B">GROUND_TRANSPORT_NON_AIR_SERVICES</ReasonForIssuance>



<BookingMethod













<Footnote>N</Footnote>

</ns31:Ancillary>




<SectorPortionInd>S</SectorPortionInd>







</ns31:Ancillary>











</ns31:Ancillary>



<ns9:Origin

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">AUH</ns9:Origin>

<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">HYD</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

5-12 GetAncillaryOffers RS Multi-Pax Stateful User Guide August 2018

<ns2:Amount


currency="AED">6000</ns2:Amount>

<ns2:EquivAmount


currency="SAR">6137.00</ns2:EquivAmount>

</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules





code="4">TRAVEL</FeeApplicationMethod>



<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" segmentId="segment_1"

segmentNumber="3"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

User Guide August 2018 GetAncillaryOffers RS Multi-Pax Stateful 5-13

<ns9:AncillaryRules


<RefundableReissuable>R</RefundableReissuable>






<ns9:Segment


segmentNumber="3"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules


<RefundableReissuable>N</RefundableReissuable>






<ns9:Segment


segmentNumber="3"/>

5-14 GetAncillaryOffers RS Multi-Pax Payload User Guide August 2018

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>




nameReferenceNumber="01.01" nameAssociationId="1"/>

<ns9:OfferRefs


offer_ancillary_17 offer_ancillary_16</ns9:OfferRefs>




xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" passengerType="CHD"


<ns9:OfferRefs






xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" passengerType="INF"


<ns9:OfferRefs





<ns31:EmptyGroupList>FF</ns31:EmptyGroupList>



5.5 G e t A n c i l l a r y O f f e r s R S M u l t i - P a x P a y l o a d






05:00"/>



<SubCode>0LN</SubCode>


<CommercialName>CARRYON HAND BAGGAGE



<Group>BG</Group>

User Guide August 2018 GetAncillaryOffers RS Multi-Pax Payload 5-15


<SubGroup>CY</SubGroup>

<SubGroupDescription>CARRY ON HAND

BAGGAGE</SubGroupDescription>

<BagType>CARR</BagType>

<ReasonForIssuance




<BookingMethod




<SubCode>0DF</SubCode>


<CommercialName>FREE BAGGAGE



<Group>BG</Group>


<ReasonForIssuance




<BookingMethod





<ServiceType>B</ServiceType>

<BaggageAllowance>

<MaxWeight unit="KILO">7</MaxWeight>

<MaxWeight unit="POUND">15</MaxWeight>


</BaggageAllowance>






</ns31:Ancillary>





<BaggageAllowance>



</BaggageAllowance>






</ns31:Ancillary>



<ServiceType>B</ServiceType>

<BaggageAllowance>





</BaggageAllowance>






</ns31:Ancillary>





<BaggageAllowance>



</BaggageAllowance>






</ns31:Ancillary>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount


currency="AED">0</ns2:EquivAmount>

</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules





<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" segmentId="SEG13"/>

<ns9:PurchaseByDate






art>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules





<ns9:Segment


<ns9:PurchaseByDate





art>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee





<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules





<ns9:Segment


<ns9:PurchaseByDate





art>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>

</ns9:AncillaryFee>

<ns9:AncillaryRules






<ns9:Segment


<ns9:PurchaseByDate





art>



equired>

</ns31:Offers>




nameReferenceNumber="1.1" passengerId="p1"/>

<ns9:OfferRefs


offer_ancillary_87</ns9:OfferRefs>




xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" passengerType="CHD"


<ns9:OfferRefs








<ns9:OfferRefs





<ns31:EmptyGroupList>FF</ns31:EmptyGroupList>



</soap-env:Body>


5-20 GetAncillaryOffers RS with Multi-Pax, Multi-Segment, Multi-Fare Payload User Guide August 2018

5.6 G e t A n c i l l a r y O f f e r s R S w i t h M u l t i - P a x , M u l t i -

S e g m e n t , M u l t i - F a r e P a y l o a d

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


<soap-env:Header>

<stlh2:SabreHeader





<stlh2:CustomerID>AA</stlh2:CustomerID>

<stlh2:ConversationID>missing conversationId from

PDC</stlh2:ConversationID>


<stlh2:TimeStamp>2018-07-24T03:31:51-



<ns47:ResultSummary

xmlns:ns47="http://services.sabre.com/STL_Header/v02_01">

<ns47:Success/>

</ns47:ResultSummary>


</soap-env:Header>

<soap-env:Body>






05:00"/>


…


<SubCode>0LW</SubCode>


<CommercialName>FAST TRACK</CommercialName>


<Group>TS</Group>

<GroupDescription>TRAVEL SERVICES</GroupDescription>

<SubGroup>SY</SubGroup>

<SubGroupDescription>SECURITY</SubGroupDescription>


<ReasonForIssuance

code="E">AIRPORT_SERVICES</ReasonForIssuance>




<BookingMethod



…


<SubCode>0B0</SubCode>


<CommercialName>UNACCOMPANIED MINOR FEE

INTL</CommercialName>


<Group>UN</Group>

User Guide August 2018 GetAncillaryOffers RS with Multi-Pax, Multi-Segment, Multi-Fare Payload 5-21

<GroupDescription>UNACCOMPANIED TRAVEL

ESCORT</GroupDescription>

<SubGroup>MR</SubGroup>

<SubGroupDescription>UNACCOMPANIED

MINOR</SubGroupDescription>

<ReasonForIssuance

code="E">AIRPORT_SERVICES</ReasonForIssuance>



<BookingMethod



…


<SubCode>0B5</SubCode>


<CommercialName>COMFORT SEAT</CommercialName>


<Group>SA</Group>

<GroupDescription>SEAT ASSIGNMENT</GroupDescription>

<SpecialService>RQST</SpecialService>

<ReasonForIssuance

code="A">AIR_TRANSPORTATION</ReasonForIssuance>




<BookingMethod



…


<SubCode>GX3</SubCode>


<CommercialName>GX3 0DD 0B5 seat

bundle</CommercialName>


<Group>BD</Group>

<GroupDescription>BUNDLED SERVICES</GroupDescription>

<ReasonForIssuance

code="A">AIR_TRANSPORTATION</ReasonForIssuance>



<BookingMethod



…










<Footnote>@</Footnote>

</ns31:Ancillar

…












</ns31:Ancillary>

…









<AirExtraStatus>NO_AE</AirExtraStatus>

<Footnote>*</Footnote>

</ns31:Ancillary>









<AirExtraStatus>CONFIRMED</AirExtraStatus>


</ns31:Ancillary>

…

<ns31:Offers offerId="offer_ancillary_3" ancillaryRef="ancillary_ancillary_3">

<ns9:Origin


<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">AUH</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



<ns2:EquivAmount


currency="USD">132.50</ns2:EquivAmount>

</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>


</ns9:AncillaryFee>


<ns9:AncillaryRules










<ns9:LinkedAE


offer_ancillary_10</ns9:LinkedAE>

<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" inventoryLevel="150"

segmentId="segment_1"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03">SYD</ns9:Destination>

<ns9:AncillaryFee




<TotalTaxes/>

<Base>

<ns2:Amount



</Base>

<TTL_Price>

<ns2:Amount



</TTL_Price>


</ns9:AncillaryFee>

<ns9:AncillaryRules










<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" segmentId="segment_2"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>

…



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee


<Unavailable>true</Unavailable>

<DisplayOnly>true</DisplayOnly>

</ns9:AncillaryFee>

<ns9:AncillaryRules





<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" inventoryLevel="150"

segmentId="segment_1"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>



<ns9:Origin


<ns9:Destination


<ns9:AncillaryFee




<TotalTaxes/>

<Base>


<ns2:Amount



<ns2:EquivAmount



</Base>

<TTL_Price>

<ns2:EquivAmount



</TTL_Price>


</ns9:AncillaryFee>

<ns9:AncillaryRules


<RefundableReissuable>R</RefundableReissuable>


<Interlineable>false</Interlineable>




<ns9:Segment

xmlns:ns9="http://services.sabre.com/merch/ancillary/v03" segmentId="segment_1"/>

<ns9:PurchaseByDate





Part>



equired>

</ns31:Offers>




passengerId="passenger_1_clone_1"/>

<ns9:OfferRefs






















<ns9:OfferRefs





















<ns9:OfferRefs


















<ns31:EmptyGroupList>FF SB</ns31:EmptyGroupList>

<ns31:InactiveGroupList>UU 99 ST BF CO RO T1

T2</ns31:InactiveGroupList>



</soap-env:Body>




This chapter includes GetAncillaryOffers error messages and descriptions.

Code Message Reason Type

NO_REQUESTED_TRAVELERS You must provide name reference number or name association id in the request for all passengers asked

CLIENT_INVALID_ REQUEST

Validation

REQUESTED_TRAVELERS_NOT_IN_ RESERVATION

Not all passengers exist in reservation


BusinessLogic

ALL_REQUESTED_TRAVELERS_NOT_IN_RESERVATION

Requested passengers not found in

reservation


BusinessLogic

ALL_REQUESTED_TICKETS_NOT_IN_ RESERVATION

Requested tickets not found in reservation


BusinessLogic

NO_MATCHED_PASSENGER_FROM_ TKT

Could not match passenger from ticketing


BusinessLogic

NO_TKTS_WITH_VALID_COUPON At least one ticket with a valid coupon is required for a passenger


BusinessLogic

NO_MATCHED_PASSENGER_FROM_ TKT_SEFCI

There is discrepancy in data between segments eligible for checking and ticketing segments


BusinessLogic

6 Error Messages 6

6-2 Introduction User Guide August 2018


PNR_LOCATOR_REQUIRED PNR Locator is required for stateless request


Validation

REQUEST_TYPE_REQUIRED Proper request type is required


Validation

REQUEST_MODE_REQUIRED Proper request mode is required

CLIENT_INVALID_REQUEST

Validation

QUERY_ITINERARY_REQUIRED Itinerary query is required


Validation

QUERY_PNR_LOCATOR_REQUIRED Locator query is required


Validation

QUERY_PASSENGER_TICKET_OR_ TYPE_REQUIRED

One of passenger query, passenger type query or ticket query is required


Validation

QUERY_TICKET_NUMBER_REQUIRED

In QueryByTicket mode at least one ticket number should be provided


Validation

CLIENT_CONTEXT_REQUIRED Proper client context is required


Validation

REQUEST_TYPE_AND_CONTENTS_ DONT_MATCH

Request type and context

don't match


Validation

PAX_REQUIRED At least one passenger is required


Validation

SEGMENT_REQUIRED At least one segment is

required


Validation

SEGMENT_ELIGIBLE_NOT_IN_ RESERVATION

Segments eligible are not subset of the segments in reservation


BusinessLogic

PASSENGER_ID_NOT_PROVIDED Passenger id is required


Validation



SEGMENT_ID_OR_NUMBER_REQUIRED Segment must contain segmentId or segmentNumber


Validation

PASSENGER_NAME_REF_NUMBER_NOT_PROVIDED

Passenger name reference number is required


Validation

SEGMENTS_WITH_FLIGHT_NUMBER_AND_NO_DEPARTURE_DATE

All segments with a flight number must also contain a departure date


Validation

PASSENGER_HAS_MORE_THAN_ONE_PQ

Passenger has more than one PQ assigned


Validation

PQ_WITHOUT_PASSENGER_REF PQ contains no passenger ref and both PQs and Passengers present in the request


Validation

PASSENGER_WITHOUT_ASSIGNED_PQ At least one passenger has no PQ assigned and both PQs and Passengers present in the request


Validation

REQUESTED_PQ_NOT_ACTIVE Requested PQ is not active.


Validation

INVALID_ITINERARY_PARTS_PROVIDED Invalid itinerary parts - all segments should have single itinerary

part assigned


Validation

INVALID_PQ_DATA_IN_REQUEST Invalid PQ data in request


Validation

NO_MAPPING_AND_AMBIGUOUS_PQS Failed to map PQs to passengers - passenger types are ambiguous and no mapping was provided

INVALID_PROVIDER_RESPONSE

Validation



MORE_THAN_ONE_PQ_WITH_THE_SAME_TYPES

More than one Price Quota with the same passenger type in reservation


Validation

MORE_PASSENGERS_THAN_PQ_QUANTITY

More passengers than Price Quote quantity in the

reservation


Validation

REQUESTED_PQ_NOT_IN_RESERVATION

Requested PQ is not present in reservation


Validation

BOTH_TYPE_AND_PASSENGER_QUERIES_IN_REQUEST

BOTH_TYPE_AND_PASSENGER_QUERIES_IN_REQUEST


Validation

BOTH_TICKET_DATA_IN_REQUEST Both Ticket and TicketReferenceNumber in request - only one can present


Validation

BOTH_COUPON_DATA_IN_REQUEST Both Coupon and TicketCouponNumber in request - only one can present


Validation

NO_COUPON_DATA_WHEN_TICKET_EXIST_IN_REQUEST

Coupon doesn't exist when Ticket available in request - both must be

present


Validation

NO_TICKET_DATA_WHEN_COUPON_EXIST_IN_REQUEST

Coupon doesn't exist when Ticket available in request - both must be present


Validation

ALL_COUPONS_FOR_REQUESTED_TICKETS_HAVE_INCORRECT_STATUS

Incorrect coupon status for all requested tickets


Validation

Endpoints identification retrieved in ANCS error messages such as SID-1, SID-2:

Endpoint number Endpoint name

1 Ticketing


Endpoint number Endpoint name

2 Reservation

3 Pricing

4 Dynamic Retailer

5 Inventory

6 Profiles

7 PPP

8 SOE


• • •

Documents

User Guide - Sabrefiles.developer.sabre.com/doc/providerdoc/... · This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use,