Travelport (Galileo)

From docs.websky.tech
Jump to navigation Jump to search

Travelport (Galileo) is one of the largest GDSs offering airline, hotel, travel and car rental booking services. Along with the global distribution system Worldspan, it is part of the Travelport holding company.

Description

Websky is an official certified developer of Galileo Web Services. Websky booking system supports ticket sales on the agency website through the Galileo global distribution system.

At the moment, in order to develop Websky products within the framework of cooperation with Travelport, company integration with a new protocol of interaction with Galileo GDS - Travelport uAPI - was added. It is more efficient and provides more features compared to the previous version of the connector - Galileo Web Services (e.g. fare families). Due to the transition to this more functional protocol for interaction with GDS Galileo, the new functionality will be finalized only for the Travelport uAPI connector and will not be made for Galileo WS.

General features

Search and general

  • Search by nearest dates
  • Search by all classes
  • OJ tariffing
  • Search by public + private fares
  • Search for private fares
  • Sending terminal commands (for uApi, you need to specify the necessity of this functionality in the questionnaire)
  • Return of e-ticket attribute in search results
  • Return of ticketing deadline in search results
  • Maximum number of segments in complex route - 8 (uApi - 6)
  • Validating carrier in search results
  • Checking interlines in search results
  • Maximum number of passengers of all types in a search request - 9
  • Number of passengers of the same type in the request - 9
  • Fare families (not supported by GWS)


Booking

  • From the requisites/settings
    • Hide the price on the GDS website
    • Adding passenger title (not supported by uApi)
    • RebookForLowestPrice[1]
    • Repetition of assigning seats after getting NN status (not supported by uApi)
  • Additional operations with usage of credentials/settings
    • Reading fare rules
    • Checking availability
    • Checking availability via seat assignment (not supported by uApi)
    • Getting a seat map
    • Price update
    • Maximum number of sessions opened at the same time - unlimited
    • Returning fare types - Public, Nego
  • Airline server operations/requests
    • Flight booking
    • Cancellation
    • Booking update (synchronization)
    • Checking for tickets availability outside of PNR
    • Importing bookings from PNR locator
    • Retrieving bookings history from PNR
    • Modification of name and patronymic
    • Modification of bookings content
    • Adding content
    • Content through WS - BSP, partially TCH
    • BSP booking and ticketing capability
    • Bookings for infant seats
    • Cancellation via application

Ticketing

  • From the requisites/settings
    • Ticketing on airline stock[2]
  • Airline server .NET operations/requests
    • Ticketing for the whole booking
    • Additional ticketing for passengers with booking
    • Checking airline commission at checkout
    • Commission per passenger type
    • Depositing endorsements
    • GDS processing (not supported by uApi)
    • Multi-FOP GDS processing (not supported by uApi)
    • Proxy GDS processing via Payment Gateways (not supported by uApi)
    • Voiding
    • Ticket refunds

Connecting to Galileo GDS in Websky

To interact with GDS Galileo through Websky, you need to do the following:

  1. Sign a contract with Travelport company:
    1. Contact the local Travelport office.
    2. Request a sample contract request form.
    3. Fill out the application, indicating that the following PCC (offices) are needed:
      • Office to work offline (i.e., through terminals): service bureau (SVCB), BSP;
      • Office for online work: BSP online, search online office.
      • Features:
      • Attention! If you are a direct TCH agent and plan on working with TCH through Galileo, you also need to order offline/online offices for TCH.
      • If you are not a direct agent of TCH but a subagent of an agency and you plan on working with TCH through Galileo, then the offline/online offices for TCH can be ordered for you by the agency, provided that the agency already has a contract with Travelport.
      • The ordering of an offline TCH office is mandatory because the TCH (Transport Clearing House) authorizes the agency for the offline office and already binds the Internet Point of Sale (IPP) to it for online operation.
      • If you are a direct agent of Aeroflot or S7 and are authorized by them to sell on their electronic forms (ETAT), then you need to order online/offline offices to conduct ticketing for these airlines as well.
      • If you are not a direct agent of Aeroflot or S7 and you work as a sub-agent of an ETAT-authorized agency, and that agency has an agreement with Travelport, then the online/offline ticketing offices for those airlines can be booked by that agency.
      • Attention!If you are a sub-agent, then, if your agency orders offices under TCH and ETAT, all questions about setting them up and ordering masterGTIDs will have to be handled by your agency.
      • As ETAT may be implemented in the Galileo system for other airlines in Russia and CIS countries, we recommend to follow the news of Travelport and contact your account manager for more information.
      • In order to make it easier for you, as an agent, and us, as developers, to understand the purpose of the offices created for you, online offices usually have an OL in their name. For example: OL BSP - office for BSP online, OL SBB - search online office (SBB - Super Best Buy), OL TCH - office for TKP online, OL S7 - online office for S7 ETAT.
  2. If you already have a subscription service contract with Travelport, then, in the contract application, you indicate that you need to prepare an addendum to the contract, and that you only order the online offices you need.
  3. In the contract application, you must also state that you need masterGTIDs for all online offices (except for the TCH office).
  4. If you did not specify in the application that you require masterGTIDs, you can order them after you receive the PCC configurations (PCC) you ordered from Travelport.
  5. The timeframe for ordering new PCCs and the masterGTIDs for them is defined by Travelport's regulations (at least 5 working days after signing the contract/contract addendum by both parties).
  6. After receiving the configuration you have ordered from Travelport, you must submit all online office data to Websky (PCC numbers and masterGTIDs for them, data to access the PCC management admin portal). We will order HAP's (Host Access Profile) from Travelport for you, so you can work with Galileo system via Websky's on-site installation. The minimum time required for Travelport to process your HAP request and create it is 5 business days.

Attention! Without the provided data for access to the PCC administration portal, the order of HAPs/WABs will not be taken into operation.


  1. Attention! The PCCs created are initially "blank" in the sense of basic settings. These PCCs must be set up in order to work properly both offline and online. PCCs are set up by the local Travelport office staff by your letters sent to your account manager:
    • a letter asking to set up office XXX (where XXX is the office number (PCC) from the configuration you received) to work with BSP and add all airlines from BSPLINK settings for your agency - written on agency letterhead signed and stamped, your BSP validator indicated (IATA number, address, name). Once settings are made for an office on BSP, new airlines will be added to it automatically from the data in BSPLINK. A separate letter is written to each of the BSP offices (online and offline).
    • letter asking to set up an XYZ (OL SBB) office for online search - written on agency letterhead, signed and stamped, specifying your BSP validator (IATA number, address, name). The distinctive setup of this office is that if you have ordered an online office for TCH and/or an online office for ETAT of a particular airline, you are asking to add airlines from BSPLINK, airlines participating in Galileo - TCH, and/or airlines that you will work with on ETAT.

The agency must periodically check through your account manager settings of this office in the Galileo system, as airlines participating in the project Galileo-TCH, are not automatically added to the list of airlines in this office (as opposed to the BSP-airlines).

  • In order to work correctly with airlines online it is necessary for the local Travelport office to receive a letter from each airline that you work with via ETAT, confirming that your YYYY office (OL SU, for example) is allowed to issue ETAT to the airline (in our case, SU). In turn, you must send your account manager at Travelport a letter on agency letterhead (signed and stamped) with the validator that will be used when the airline e-ticket is issued, such as 555 1234567.

If you are a sub-agent of an agency which has an ETAT agreement with an airline, then such a letter must be sent to Travelport on behalf of the agency, since it is in the agreement of that agency with the airline that your airline ETAT sales point is spelled out.

  • In order to work correctly online with TCH via Galileo, your online TCH ZZZZZ (OL TCH) office, TCH offline office, terminals and agents (their sign-on) must be authorized by TCH to issue (sell) via Galileo. Otherwise, it will not be possible to conduct ticketing in TCH via Galileo. The appropriate application must be submitted to TCH by you (if you are a direct agent of TCH) or your agency (if you are a subagent). The processing time for the authorization request is governed by TCH internal procedures. Uploading an updated TCH file is done by Travelport on a daily basis.

Connection Features

  • Any sub-agency activity requires ordering separate PCCs for online and offline, no matter ETAT, TCH or BSP. Which means that if you are a BSP subagent for an airline, you need the separate online/offline PCCs for that airline, with the name, address, and BSP validator of that agency.
  • When configuring the offices (PCCs) it is recommended to ask Travelport to set transparency (Selective Access) between all your offices right away - this will allow you to access your created booking from any of your PCCs (the exception is access to the TCH office, where you can only enter under an authorized TCH signature (sign-on). If you are a subagent and the PCC belongs to your agency, a transparency request is sent to Travelport by both you and your agency.
  • ETAT tickets are issued through a printer specifically described in the system configuration. The printer is linked to a specific address (terminal), so first you need to decide which terminal you are going to link the printer to, and then contact Travelport about adding the printer to this or that configuration. The last step in this procedure is to specify in the Websky settings the logical address of the printer added to the Galileo configuration.
  • The above also applies to the printer on which the ET ticket itinerary receipts are output.

In order for the printers to be linked correctly, Travelport recommends that you contact your local office for assistance with these operations.

The last step in this procedure is to specify in the Websky settings the logical address of the printer added in the Galileo configuration and linked in the PCC.

Differences in the Travelport uAPI connection procedure

The connection to Travelport uAPI follows the same script as to Galileo. However, WAB (Work Area Branch) will be used instead of HAP and there is no need for printer numbers when configuring connection requisites.

Features of working with GDS Galileo

Websky and Galileo synchronization

Synchronization of Websky and Galileo involves updating the status of the order and its status in Websky in accordance with changes to the GDS.

Attention! If the ticket was booked in Websky, but is issued in the terminal while updating the order in Websky, the status will change to Issued.

The <Status>cancelled</Status> parameter can take the following values:

  • const STATUS_PENDING is 'pending';
  • const STATUS_PENDING_CONF - 'pending confirmation';
  • const STATUS_WAITING - 'waiting';
  • const STATUS_BOOKED - 'booked';
  • const STATUS_CANCELLED - 'cancelled';
  • const STATUS_TICKET - 'ticket';
  • const STATUS_NEEDCONFIRM - 'needconfirm';
  • const STATUS_REJECT - 'reject';

One or another status is assigned to the parameter in the following situations:

  • pending - order pending for booking, new booking;
  • reject - order is rejected by the supplier;
  • pending confirmation - booking pending confirmation from the supplier;
  • waiting - booking awaiting result from the supplier;
  • need confirmation - booking awaiting manual confirmation from the client;
  • booked - booked and confirmed;
  • ticketed - booked and issued documents;
  • cancelled - the booking is cancelled.

Paid bookings can have only three statuses:

  • booked - booked and confirmed;
  • ticket - booked and issued documents;
  • cancelled - the booking is cancelled.

Attention! The current version of search requests in Galileo supports displaying baggage in search results.

Attention! The order update algorithm in Websky for Galileo GRS takes into account the removal of passengers in the order through the terminal.

Ticketing in Galileo

While ticketing in Galileo, there is a sequential check of the relevance of the existing fare, which involves:

  1. Checking the status of the set price.
  2. If the price status is cancelled or invalid, deletion of the old price record. A "CONFIRM SEGMENT 01" exception is possible here, meaning that the segment has been cancelled (most likely by the airline).
  3. If the old invalid price has been successfully cancelled, a request is made to reset the price. A "NO VALID FARE FOR INPUT CRITERIA" exception is possible here, meaning a "mismatch" between PNR and the Galileo GDS price database.

It means that resetting the price takes place in two steps:

  1. deleting the old one;
  2. setting the new price.

This happens if the price status comes as (from specs):

  • I = Invalid Fare, e.g., due to name/itin change;
  • X = Expired Fare, older than 7 days;
  • V = Reprice (need requote to ticket).

Attention! It is recommended to update the price just before ticketing in case ticketing takes place on a different day.

Error in booking and ticketing in GDS Galileo

Ticket generation

A separate ticket number is generated for every 4 segments of the booking. This is standard Galileo host logic and does not depend on client platform.

Agency commission display in GDS Galileo

The agency commission is assigned to the agency by the airline in accordance with the contract. The agency commission can be the same for all traffic; it can differ for various destinations, countries and flight types.

Attention! Under no circumstances does the commission appear on the e-ticket or on the itinerary receipt.

The commission due to an agent for one or another booking can be seen in Galileo in the TINS / TICKET AND INVOICE NUMBERING SYSTEM REPORT report. This report is displayed on the screen using the HMPR command.

To view the commission amount you can use the extended report - this report is displayed by the HMPR*E command.

Currency rates in GDS Galileo

The currency in which the base price comes from the supplier depends on the flight type. The currency in which the equivalent price arrives depends on the location of the agency. Galileo supports 3 basic bank rates between the currencies in which conversion takes place.

  • The bank selling rate (BSR) - is used when payment is made in the currency of the country where the agency is located and the local currency is accepted as payment. For example, the fare for a flight from Hong Kong (HKG) to Los Angeles (LAX) is HK$23,000 (HKD). If a ticket is issued by an agency in London and payment is made in GBP (British Pounds Sterling) then fare is converted from HKD to GBP using exchange rate (Format: FZSHKD23000GBP). The BSR exchange rate is also used to recalculate commissions.
  • Bank purchase rate (BBR) - applies if the payment is not made in the local currency of the agency's location and a foreign currency is accepted as payment for the ticket. For example, the fare from Copenhagen (CPH) to Kingsford Smith (SYD) is 23,000 Danish kroner (DKK). If the ticket is issued at an agency in London and the payment is taken in Euros (EUR), the conversion of the fare from DKK to EUR will use the BBR - exchange rate (purchase rate, format: FZBDKK23000EUR). In this case you should remember that:
    1. The fare is calculated for reference only.
    2. In most cases only local currency is accepted as payment, and acceptance of foreign currency is prohibited. In this case the BBR rate is not used.
  • The IATA exchange rate (ICH) - the IATA exchange rate is equivalent to the USD exchange rate; it is used in Galileo in the absence of a direct conversion between the two currencies. For example, the fare for a flight from Abidjan (ABJ) is 23,000 francs (XOF). If the ticket is issued in Delhi and payment is accepted in Indian rupees (INR), the francs are converted into U.S. dollars at the IATA exchange rate first and only then into rupees at the selling rate (Format: FZSXOF23000INR)
  • It is possible not to recalculate the fare (even if the exchange rate changes), if it is guaranteed by Galileo technology. When you receive a bill from the airline - send to the group ADM Galileo, so that the money is returned.

Other features

In case the Airline finds and proves violations of the following rules, the Agent agrees to pay the appropriate penalties with the application of the ADM procedure.
Application Date November 15, 2013.

Subject of ADM:
20. Absence of direct contact information of the passenger or contact information of the person authorized by the passenger (including the Agent himself) entered in PNR using SSR field to enable round-the-clock communication between the Carrier and the passenger (passenger's authorized person). Galileo format: SI. PS * CTC 1234567

.

According to the requirement, the PNR with segments of UIA automatically enters the passenger's contacts in the specified format: Other Service Information “SI. PS * CTC 1234567”.

  • Some airlines see only first field from the contacts entered into Galileo, so the contacts are in the following order: client, passenger, agency.
  • If hiding of passenger data is not turned off on the GDS Galileo side, the current date of birth is used after booking. On the test HAP, hiding is not turned off.
  • If some of the original booking segments have been deleted, the tickets remain active but invalid in the PNR. The presence (introduction) of new segments, including completely identical ones, still results in invalid tickets. For example, this situation can occur when an airline accepts schedule changes made by adding a new TC segment and assigns UN status to the old one. Such tickets require reissue (exchange/revalidation) in order for them to be returned to PNR as not only active, but also valid. If active tickets are not in PNR, Websky considers them to require re-ticketing for that PNR, sets a booking status other than "booked", parses those tickets into the booking and returns a warning that re-ticketing is required for that particular booking. An appropriate notification is sent to the agency.
  • In Websky, booking form prevents booking errors related to violation of Galileo's restrictions on the number of characters allocated for the passenger's last name:
    • Maximum number of characters for last name and first name in total - 52.
    • Maximum number of characters for first name, last name and middle name combined is 51.
    • If the passenger is female, the above values are reduced by 1.
    • The maximum number of characters for the first or last name is 30.
    • Attention! It is forbidden to correct the data of the name in the terminal after creating the order. The supplier will not return the corrected data and the original information will be displayed in the order.
  • There are cases when the airline has incorrectly filed the commission in the fare, due to which the commission in the issued ticket does not correspond to the commission indicated in the pricing. We can not change or redefine commission, which the airline has written in the fare. The problem can only be solved by Galileo together with the airline (or by the agent together with the airline).

FSBC option

FSBC is an option that allows you to get fares at a cheaper price, but then you have to book them separately (i.e. in different PNRs). For example, in ADT+CNN situations. It means that for different types of passengers come different booking class letters for the same segments at the minimum price. The reason for this is usually the different values of discounts for the child on the cheapest and more expensive option (25% and 50%). Since Websky does not yet have the ability to share PNRs, this option should be disabled in advance on the supplier side for a particular customer's PCC. It is also incorrect to remove such flights from the output completely, because then some of the content disappears, which is usually unsatisfactory for the clients. To do this, write to Galileo local helpdesk at "[email protected]" - only for Russian locations! For other markets (Germany, Ukraine etc.) customers should contact their account manager. Attention! When creating new NARs / IPCCs, disable this option immediately in advance.

Frequently Asked Questions about GDS Galileo bookings

How do I avoid mistakes when working with commissions filled out in cat35?

If the commission is filled in via cat35 and/or APF, then the following rules should be applied:

  • If the commission information already exists and matches, then it cannot be changed or overwritten.
  • If commission information exists but does not match (e.g. conflicts) then it can be added and modified.
  • If there is no commission, the user can change it and add it, or the system will accept default values depending on the carrier, fare, market.
What are the restrictions on the number of passengers in FQSBB requests?
  1. Up to 9 passengers. More than 9 is a group. You can use up to 4 different PTC codes.
  2. Infants must always travel with an adult.
How are the fares and reservations for children accompanied by an adult?
  • It is not possible to book 2 different classes for different types of passengers. To get children fare, you have to create new PNR and you have to enter data of adult in the child's PNR.
  • The child fare is quoted only if accompanied by an adult on the request.
  • If you want the lowest fare for children, then you can sacrifice the cheapest fare and make a reservation for a child with an adult booking class (in case you want to create only one PNR).

Alternative method

Both passengers are in the same class with the highest fare.

How do I add an endorsement in PNRBFManegement?

You can add an endorsement to the PNRBFManegement like this: 

<EndorsementBox>
			<Endors1>VALID ON AI IC ONLY</Endors1>
			<Endors2>NON END PENALTIES APPLIES</Endors2>
			<Endors3>NON RE ROUTABLE</Endors3>.
		</EndorsementBox>
.
How do I add different endorsements for each passenger?

This can be done by adding different endorsements for each passenger in each booking request. You need to issue one fare at a time.

When ordering a second ticket, you should first retrieve the PNR and enter the completed fare number in the appropriate section.

Example 

<FareNumInfo>
<FareNumAry>
<FareNum>1</FareNum>
</FareNumAry>	
</FareNumInfo>

If you want to make separate rate quotes, you must send 2 <StorePriceMods> blocks in the request.

Example 

<StorePriceMods>
		<SegSelection>
			<ReqAirVPFs>N</ReqAirVPFs>
			<SegRangeAry>
				<SegRange>
					<StartSeg>01</StartSeg>
					<EndSeg>01</EndSeg>
					<FareType>N</FareType>

				</SegRange>
			</SegRangeAry>
		</SegSelection>
		<PassengerType>
			<PsgrAry>
				<Psgr>
					<LNameNum>01</LNameNum>
					<PsgrNum>01</PsgrNum>
					<AbsNameNum>01</AbsNameNum>
					<PTC/>
					<TIC/>
				</Psgr>
			</PsgrAry>
		</PassengerType>
	</StorePriceMods>
	
	<StorePriceMods>
		<SegSelection>
			<ReqAirVPFs>N</ReqAirVPFs>
			<SegRangeAry>
				<SegRange>
					<StartSeg>02</StartSeg>
					<EndSeg>02</EndSeg>
					<FareType>N</FareType>
				</SegRange>
			</SegRangeAry>
		</SegSelection>
		<PassengerType>
			<PsgrAry>
				<Psgr>
					<LNameNum>02</LNameNum>
					<PsgrNum>02</PsgrNum>
					<AbsNameNum>02</AbsNameNum>
					<PTC/>
					<TIC/>
				</Psgr>
			</PsgrAry>
		</PassengerType>
	</StorePriceMods>

If you want to keep 4 different filled fares - one (also with an endorsement) per passenger - you need to make 4 requests.

There is no best practice for adding endorsements. There are different ways to do this, which can be found at these links:

It is also recommended to go through the API developer notes and see "Issuing ticket on Galileo/Apollo CRS" by the following links:

In which system requests can I get information about time zones? For example, MOW +3.

The following transaction is used to determine the local time in a given city: 

<LocalDateTimeCT_6_0>
 <LocalDateTimeMods>
 <ReqCity>MAD</ReqCity>
  </LocalDateTimeMods>
  </LocalDateTimeCT_6_0>

Response: 

<LocalDateTimeCT_6_0>
<LocalDateTime>
<Dt>20100917 </Dt>
<Tm>1744 </Tm>
</LocalDateTime>
</LocalDateTimeCT_6_0>
Why can I receive errors when I try to make a preliminary booking of seats?

The carrier may not be included in the list of airlines participating in the system that allow preliminary booking of seats.

General information about the request for seats in GDS Galileo:

"It is possible to request seat bookings in advance (prior to travel) for most carriers participating in the GDS Galileo. This possibility can be controlled by each airline depending on the current situation. GDS Galileo also offers interactive accommodations. This allows immediate confirmation of the booking made at the time of request, before the end of the transaction.

These services can be offered by the following carriers:

AZ BA CX EI ET FU GJ IW KA KE KL KQ KU LO LP LX MA MH NH OA OM PX QE RD RJ RO RQ SA SN SQ SR SV SW TP TR UA VR XM 2T 6A 9W".

If you receive an error, you should contact your local office for carrier information and make sure that the carrier is indeed not on the list.

Can I check seat availability for the entire flight in one request?

There is an AirAvailability_X request for one segment.

To get information about seat availability for all segments, you need to check the InsideAvailOption element. The answer will show available seats for the whole flight.

If it is necessary to check available status for the whole flight, include corresponding KLRID in FQSBB request: <KlrID>AAB1</KlrID> Using the availability request, you can get available seats for the entire flight.

The number inside the BICStatus is the number of available seats.

What is the maximum number of sessions that can be used simultaneously and what is the session duration?

You can only open one session at a time in the HAP.

The session stays open for 3 minutes if no entries are made.

Useful link:

Is there any way to increase the speed of responses in the GDS Galileo web services?

Useful link:

How do I request and then use private fares?

Information on how to request private fares can be found here:

Transition to Goto XML Select Service > API Developer Notes

How do I get the latest effective date of the fare?

In order to find out the end date of the tariff, you need to check the <LastTkDt> field that is returned in the FQSBB GenQuoteDetails section.

If there is no additional information about the sale (e.g., <AdvTkRsvnTm>0</AdvTkRsvnTm>), the last ticketing date will be the sending date in the FQSBB response.

However, once the sale of valid flights and fare retention is made, GDS Galileo has a seven-day guarantee. Unless there are additional sales rules defining the last possible ticketing date, the date is 7 days from the fare saving or dispatch day.

You can fill in the timelimit field (e.g., <Tk>TAU/07MAY</Tk>) using the <LastTkDt> section returned in FQSBB's GenQuoteDetails section or, alternatively, discuss with the customer what date they would like to use (sometimes agents can use the booking date in all classes).

The booking file will automatically be placed in queue 10 on the ticketing date. When the ticket is issued, the field is automatically updated to show the ticketing date and time.

Do all requests to the Galileo GDS need to be carried out within sessions?

It is recommended to perform all actions related to booking (creation of booking, its modification, removal) in a session. PNR creation can also take place outside the session, but in this case the vendor remark will come in the form of a mask when saving the booking. The point of a session is to transfer data explicitly. At the same time, it is not recommended to use sessions for search and shopping requests because of the increased load on the host.

How do I turn off hiding passenger data in GDS?

Hiding passenger data in the GDS for RCC is done by your account manager at your request.

What should I do to avoid changing the class of service when booking?

You can avoid changing your class of service when booking in the GDS for RCC by contacting your account manager.

Errors in interaction with GDS Galileo

Errors at the beginning of the session:

Error Explanation A way of a possible solution
«ELECTRONIC AGENCY-LINKAGE PROHIBITED» (BeginSession reques) The error may occur if the AAT table is set incorrectly. You need to contact your local Travelport technical support service.

Errors in the search

Error Explanation A way of possible solution
Could not locate Session Token Information Session May Have Timed Out. Session limit exceeded. To increase the power of your CCC PT, you should request a form, fill it out and send it to your CCC PT.
Unable to retrieve enough Dynamic GTIDs for this transaction Ыession limit exceeded. If you want to increase the capacity of your CCC PT, you have to request a form and fill it out and send it to your CCC PT.

Independent of supplier:

Error Explanation A way of possible solution
SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR There is a parallel change in the PNR while working with bookings. In this case you have to start the operation again.
Invalid search reguest object This error occurs when an invalid search result is accessed. Possible causes:
  • an invalid search link;
  • The search result might be out of date.

Booking errors:

"UNABLE - MARKET CONNECTION UNAVAILABLE" Appears if one of the segments on the flight is unavailable, when the chosen booking class is unavailable, so the next segment cannot be booked either. If you select another booking class, the error should not occur.
"INVALID NAME TYPE" (under PNRBFPrimaryBldChgMods in PNRBManagement response) Error may occur when attempting to issue a flight ticket with a validating carrier that is not listed (AUTH field). Only airlines from this list can be available for autocalculation.
"REDISPLAY REVIEW BOOKING DATA" May occur if two times are added to the <QMinderQual> section (queue minder).
"CHECK FORMAT" (when entering a phone number) An error may occur because the city is also required. In the case of mobile numbers that do not have a binding to the region, it may be necessary to specify the default city code for the PCC in which the booking is made. If the problem persists, you should contact your regional tech support.
"INVALID INPUT" Appears when booking tickets with two or more fare codes in the same segment. For example fares for adults and children (or infants). The first letter in the base fare code shows the booking class. It should be the same for all passengers in the PNR. The error occurs because FQSBB returns Fare Basis Codes for the same passenger type. You need to send a different StorePriceMods section for each passenger.
"CHECK NUMBER IN PARTY AGAINST ITINERARY" The reason for the error may be the presence of 3 passenger names when trying to book 2 seats. If there is no infant among the passengers, the number of seats must match the number of passengers.
"CHECK NUMBER OF INFANTS" An error occurs if you try to book an infant seat. For example if the booking is for one adult and one infant, it is necessary to send the request for only one seat.
"NO VALID FARE FOR INPUT CRITERIA
"Error of Frequent Flyer Number" The error appears when trying to add the "Frequent Flyer Card" option to an infant booking.
"NEED PHONE" Error appears if you need to add an agency phone number when completing a booking.
"LISTED SEGMENT IS FOLLOWED BY CONFIRMED SEGMENT". The error appears because there is a "Waiting List" segment following the confirmation segment. Therefore, the system warns of this and recommends accepting the changes by making a second transaction or terminating the booking process.
"0 AVAIL/WL OPEN" Make sure that the <AvailJrnyNum> section is used correctly. If the booking segments are not part of the same route, it is worth using different numbers for each segment. When a passenger changes from one flight to another at a transfer point, you should sell all eligible flights and show that they are part of a transfer route using the <AvailJrnyNum> element. Segments that get the same numbers are part of the same trip.
"0 AVAIL/WL CLOSED" This is usually a temporary problem due to the fact that there are currently no seats available for booking with that class of service. It is possible that the airline will load more seats into Galileo after some time.

Ticking mistakes:

{ "align="center" width="50%"|"INTERLINE ELECTRONIC TICKET AGREEMENT NOT FOUND - CHECK DT/IAT TABLE FOR MORE INFORMATION" [Incident: 101006-000400] align="center" width="50%"CONFIRM SEGMENT 01 align="center" width="50%"|"TICKETING LINK UNAVAILABLE - PLEASE RETRY" Additional information: The check occurs in the <FareGuarCode>X</FareGuarCode> element of the PNRBFManagement response, where X = Expired Fare (more than 7 days). Possible actions: It is necessary to contact the customer, the travel agent, to understand how they wish to proceed in such cases. One option is to resend the Storepricemods section. If there is a valid fare, it will be listed in the itinerary, while the price may be different from the original. The first thing to do is to cancel the "burned out" fare. 
<PNRBFManagement_x>
	<PNRBFRetrieveMods>
		<PNRAddr>
			<FileAddr/>
			<CodeCheck/>
			<RecLoc>VXXXLM</RecLoc>
		</PNRAddr>
	</PNRBFRetrieveMods>
	<CancelStoredFareMods>
		<FareNumInfo>
			<FareNumAry>
				<FareNum>001</FareNum>
			</FareNumAry>
		</FareNumInfo>
	</CancelStoredFareMods>
This ticketing error occurs when there is no interline agreement between the airlines on the flight and the validating carrier. It means that the validating carrier must have interline agreements with all airlines in the flight, including code-share flights. You can check if they exist between the airlines with the DT/IAT/DISYY command.
"UNAUTHORISED/INVALID PLATING CARRIER CODE" Error occurs if the validating carrier is incorrectly defined.
"FILED FARE HAS BEEN INVALIDATED" Occurs if automatic fare recalculation is not possible.
"PT NOT COMBINABLE WITH ET" Appears if one of the segments does not support the e-ticket. It is not possible to issue a combination of segments with an electronic and a paper ticket in Websky, ticketing can only be done in terminal mode. Prerequisite for the error: The system receives the possibility of ticketing an e-ticket from the GDS in the search results. However, if subsequently the system detects a validating carrier other than the one transferred by the GDS, then on some segments the e-ticket may not be available (most often when ticketing interlines). And since this GP override process takes place after selecting the flight, it is impossible to filter out such flights on the search results.
"NO VALID FARE FOR INPUT CRITERIA" Indicates a mismatch between the PNR and the Galileo database.
"FILED FARE PARTIALLY TICKETED" The ticket has already been issued. This is indicated by the field: <PNRBFTicketedInd>Y</PNRBFTicketedInd>. Field description: "Indicates that a PNR or BF (base fare) has been ticketed at least once."
"NO ITINERARY EXISTS FOR FARE QUOTATION" Indicates that a reservation or segment has been cancelled.
"ZA INVALID MODIFIER" Indicates that the wrong printer is being used for ticketing.
"Z INVALID FORMAT DATA" Appears if commissions for TCH-flights are not set correctly.
"ZA NOT COMBINABLE WITH Z" Appears if there is a discrepancy in the choice of the commission format (one section shows the percentage, the other shows the amount).
"Uncaught Service Exception cause:com.cendant.tds.soa.framework.ServiceException: Exception ReturnedERR: AGENT ID - GALILEO |+ " Appears when trying to test ticketing in a test environment (you cannot test ticketing in a test environment ).
"INVALID GTID" GTID" means that GTID you want to link either does not exist or is not registered and therefore no linking is performed. Also check that the printer numbers are correct.
"INVALID FORMAT/DATA NO LINKAGE FOR RQSTD OUTPUT" Indicates either that the RQSTD printer number is not listed in the Galileo requisite package settings in Websky, or if so, that the RQSTD printer linking is not done correctly (online and/or offline).
"TICKETING NOT ALLOWED - CHECK AAT" Appears when the airline is not authorized for ticketing on this HAP.
"REQUESTED FILED FARE NOT FOUND" Appears when a fare is no longer available. It is removed by the airline.
"ELECTRONIC AGENCY - LINKAGE PROHIBITED" Appears when attempting to issue an e-ticket on a paper printer. All created (or newly activated) PCCs prohibit the transmission of a paper printer ID in the ticketing procedure, if the printer itself does not exist. In this case, the "Printer number" field must be left blank. The error is typical for cases where 3 printers are specified in the TCH HAP. According to the Galileo e-ticketing technology, 3 printers (printer, itinerary and MIR) must be specified in the BSP and SU hubs intended for ticketing, 2 printers (itinerary and MIR) in the S7 hub if the PCC description is TYPE=41, or 3 printers if the PCC description is TYPE=09, and 2 printers (Itinerary and MIR) in the TCH HAP.
"NET TICKET DATA MAY NOT BE MODIFIED". Indicates that the airline in question has issued a special fare. These fares are not currently handled by Websky.
Means that the flight segment has been cancelled by the airline. If you have any questions concerning your PCC settings, please call us at: +7 (495) 795 32 76.
Means that the environment is not correctly configured for ticketing tickets (for example, ITN printer linking is not performed correctly), you should contact your local helpdesk for the PCC setup.
"COMMISSION PERCENTAGE MUST BE ENTERED" Means that there is no commission for ticketing. Occurs if the provider side office settings do not allow ticketing without a commission.
"UNAUTHORISED/INVALID PLATING CARRIER CODE" This error may occur if the default validating carrier you selected is not authorized in the PCC where ticketing is attempted. You either need to create a PNR at that PCC (with a change in validating carrier and a corresponding change in price), or you need to issue a ticket at the PCC with that carrier.
"LINKAGE/OPTIONS CHANGED - UPDATE SDPT" This error is common if you have made changes to the printer settings that may have caused the printers to not work correctly. To solve the problem you need to check the linking and make changes if necessary.
"NO AGREEMENT EXISTS FOR AGENCY"
"REQUESTED FILED FARE EXPIRED"
"VENDOR MSG: ITINERARY NOT VALID FOR ETKT" The error comes not from Galileo, but directly from the airline. In Galileo terminals flights with such an error, as a rule, too can not be ticketed. It usually occurs on Aeroflot flights with codeshare and occurs due to the fact that the airline loaded these flights incorrectly, without specifying the sign of the electronic ticket. And it can be detected only when you try to book it, not before. It is recommended in such cases either to wait for about an hour and try to issue the ticket through Websky again, or the agent itself immediately contact the airline directly, and its staff will be able to correct this error and issue such a booking.
"VENDOR MSG: MSG TIME OUT - NO RESP FR VNDR" Airline host did not respond to GDS Galileo host, in this case of an agent must contact their local helpdesk.
No ticket status If the reply from Galileo is NO VALIDATING CARRIER FOUND, then the error means that there is no airline allowed for that HAP.

Contact your account manager at Galileo to add it.

Errors when cancelling ticketing:

«TKT NUMBER NOT FOUND OUTSIDE VOIDING PERIOD» The error occurs if there is a time limit for voiding.
«FILED FARE PARTIALLY TICKETED» This may occur if a ticket has already been issued for the specified fare and that fare cannot be used again for another ticket. The fare must be restored for re-ticketing.

Errors during cancellation

«Uncaught Service Exception cause:com.cendant.tds.soa.framework.ServiceException: Exception ReturnedERR: AGENT ID - GALILEO |+» It occurs in the case of "jamming" of the PCC. For example, when deactivating for a long time, or vice versa when activating. It is necessary to contact Helpdesk to eliminate this "jamming".

Questions related to the GDS Galileo, with which it is recommended to contact the local Travelport Helpdesk

  • PNR tickets voided by a GWS agent. It is necessary to get the IP address or any other data identifying the agent who performed the voiding.

Help is provided by the local helpdesk.

  • 'Cancellation of booking with tickets issued.

This is not your standard situation and is not related to ticketing API. You need to contact your local helpdesk.

Additional information:

If a ticket has been issued, it can then be voided. However, this can only be done on the day of ticketing.

If a Void Ticketing transaction completes successfully, the <DPOK> tag will simply be returned to show a confirmation response.

Responses with errors and warnings: If a Void Ticketing transaction encounters an error, the <ErrText> tag may return the following message: 

"Note: Some of these errors overlap with the unvoid and spoiled tasks:"
.

And then there is a list of possible errors.

If the deadline to enter the ticket has passed, there are two ways to cancel it:

  1. refund;
  2. exchange or revalidation.

It depends on the fare. For example, the fare conditions may not allow a refund.

  • Providing information regarding PNR history with a known locator.

The history of the cancellation and exactly how it was made.

  • Error "ELECTRONIC AGENCY-LINKAGE PROHIBITED" in the BeginSession request.

Came from wrong AAT table settings. Local HELPDESK helps (this is not the responsibility of the global service).

  • Message "VENDOR MSG: ITINERARY NOT VALID FOR ETKT" in DocProdFareManipulation_8 response with the correct actions (e-ticket must be issued).

Agency settings need to be checked. It is recommended to check them in the local helpdesk. You need to keep in mind that the carrier canceled the booking because the ticket was not issued.

  • Error "NO AGREEMENT EXISTS FOR AGENCY.

May be received when attempting to retrieve a PNR through a HAP other than the HAP where the booking was made. Must have a valid contract (on paper) to retrieve a PNR from another PCC. You should contact your local helpdesk with this problem.

See also

Useful links

Retrieved from "https://docs.websky.tech/index.php?title=Travelport_(Galileo)&oldid=300"