docs.websky.tech - User contributions [en]

Nemo Connect search request router

2021-03-21T17:28:37Z

I shaletin: /* Enabling the Nemo Connect search router */

==Purpose==
The search request router is used to automate the selection of requisite packages for [[Search (Air Tickets)|search]] based on search query parameters.<br>
The agency can set up a profitable search scheme for:
* searching across [[GDS]] in multiple zones,
* issuing more varied fares with minimal search transaction costs.

It is possible to bind requisite packages to a certain geography, for example, so that [[GDS Sirena Travel]] could search only domestic Russian flights.

== Working Principle ==

[[Nemo Connect search router|Routing]] search requests in Nemo Connect is configured in [[Nemo Connect search router|Enable Nemo Connect search router]].

===Blocking and prioritizing rules===
Using the router in the classic version assumes that if more than one rule fits the request, all rules are triggered and the request is routed to all triggered packages. <br />Via the Nemo Connect router, you can set up rules in such a way that '''when rules intersect, only one triggers'''. To do this, rules are assigned the '''blocking''' status.
*If there is at least one blocking rule among the rules suitable for the request, the router will choose one rule by priority.
*If there are '''no blocking rules''' among the rules suitable for the request, then '''all rules will be applied'''.

Rule priority is determined by the rule number (ID), or assigned manually using the ''Rule Priority'' parameter. The higher the number, the higher the priority. (see section [[Nemo Connect Search Router#Search request routing parameters in Nemo Connect|Search request routing parameters in Nemo Connect]]).
*If there is a '''blocking''' rule among those suitable for the request, and '''manual priority''' is set for each triggered rule, then the rule for triggering is '''chosen according to the manual priority'''.
*If there is a '''blocking rule''' among those that match the request, and if manual priority is not '''set for at least one triggered rule''', then the rule is '''chosen by rule number'''.

== Features of sending requests when the Nemo Connect router is running ==

'''Attention!''' Once the Nemo Connect router is turned on, do not use geographic restrictions in Websky packets.

With the Nemo Connect router turned on, packet requests are distributed to the Nemo Connect router outside of Websky, so Websky's '''fine-tuning''' package usage restriction is no longer triggered. The search request passes through the connection requisites of the package selected in the fine-tuning to the Nemo Connect router, which distributes the request into packets according to its own rules.

'''Attention!''' For Websky's connection to Nemo Connect to be realized, at least 1 package must be included in the fine-tuning. This is a prerequisite, because Websky's requisites specify the details of the connection to Nemo Connect.

== Enabling the Nemo Connect search router ==
To enable the search request router for an agency you must:
<br>
To '''Websky''':

'''Manager''':
# Go to '''Product control → Airlines → Processes → Search Process → Fine Tuning'''.
# '''Enable''' the ''Use Nemo Connect router'' option.
# In the '''Requisites from which package will be used for the search request to Nemo Connect''', select the requisite package.

'''Administrator''' (specify which settings the system will look at when searching):
# Go to '''For tech support → Nemo Connect Web Services → Interaction settings'''.
# Activate the '''Router settings''' option under '''Use settings in the Air Server from Nemo 1 for partitions'''.
In '''Nemo Connect''':
# Go to Avia Settings → Search Settings → Router Settings
# Enable the '''Use Air Router''' option.

It is prohibited to make routing rules in Websky. Websky search router is recommended to be disabled.

== Creating a search routing rule on the Nemo Connect side ==

To create a routing rule:

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule''' button.
# Enable the rule.
# Set the rule parameters (see [[Search request router#Search router parameters in Nemo Connect|Search router parameters in Nemo Connect]]):
#* Specify the conditions for applying a rule - search request parameters under which the search will be performed by this rule.
#* Specify one or several [[Nemo Connect requisite packages]] which will be searched when the rule is applied.
#* Set the additional parameters that will be applied to the search request when applying the package.
# Click the '''Save''' button.

'''Attention!''' You can create routing rules not only on the Nemo Connect side, but also on the Websky side (see [[Nemo Connect search request router#Adding a search request routing rule for Nemo Connect on the Websky side|Adding a search request routing rule for Nemo Connect on the Websky side]]).

==Search request routing parameters in Nemo Connect==

* '''Rule name''' - the name for easy work with rules.
* '''Rule enabled''' - enables the rule.
* '''Packet IDs to be searched''' - the numbers of the requisite packages ''from Nemo2.0'' (see "Fine-tuning", first column), which will be searched for when the rule is triggered. '''Attention!''' The field is mandatory. It is forbidden to contain the numbers of production and test packages of the requisites at the same time.

'''''Conditions of rule application'''''
* '''List of departure countries''' - the countries of departure at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Arrival countries list''' - arrival countries, at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Departure cities list''' - IATA codes of departure cities, which will trigger this requisite package.
* '''Arrival City List''' - IATA codes of arrival cities, which will trigger this requisite package.
* '''Arrival Airport List''' - IATA codes of arrival airports, which will trigger the requisite package.
* '''Departure Airport List''' - IATA codes of departure airports which will trigger this requisite package.
* '''Disallow complex routes (more than 2 segments in the request)'''- for the complex routes search, the rule will be triggered only if there are no more than two segments in the route.
* '''All flight segments must satisfy route requirements''' - the rule is triggered if every flight segment satisfies the rule parameters. If this option is disabled, at least one segment must satisfy the conditions of the filter rule.
* '''RT-Flights Only''' - the rule applies to roundtrip flights only.
* '''Reverse rule logic''' - includes inversion of the rule's geographical restrictions (logic like ''everything but''). <br /> For example, if the ''RU'' country is specified in the ''List of Departing Countries'' parameter when this option is enabled, the rule will apply to all flights except those departing from Russia.
* '''Invert departure/arrival countries''' - enables the inversion only by arrival/departure countries (logic like ''all except''). <br/> For example if the ''List of Departing Countries'' parameter is set to ''AU'' then all the flights except the ones departing from Australia will be inverted.
* '''Invert departure/arrival cities''' - enables the inversion only by arrival/departure cities (logic like ''everything but''). <br/> For example if the ''List of departure cities'' parameter is set to ''VOZ'', all the flights except for the ones from Voronezh will be included.
* '''Invert departure/arrival airports''' - switches on the inversion by arrival/departure airports only (logic like ''everything but''). <br/> For example if you have ''BWI'' in the ''Arrival airports list'' option checked, then all flights except the Baltimore/Washington area will be affected, and flights from Washington DC will not be affected.

* '''Required tags for this rule to trigger''' - mandatory tags in the search request for the rule to trigger. [[Nemo Connect Search Router#Tags in Nemo Connect|Tags in Nemo Connect]].
* '''Tags for which rule is not allowed to trigger''' - if there are tags from this list in the request, the rule will not be applied.

* '''Rule uniqueness feature''' - assigns blocking status to a rule. If this option is enabled and if there is at least one blocking rule among the rules suitable for the request, the router will select one rule by priority. If there are no matching rules, all the rules will be applied (see section [[Nemo Connect search request router#Blocking and priority of rules|Blocking and priority of rules]]).
* '''Rule priority''' - works only for rules with '''Blocking rule''' option enabled. Assigns priority to a rule - the higher the number, the higher the priority. When blocking rules, the one with the highest priority is triggered (see section [[Nemo Connect search request router#Blocking and prioritizing rules|Blocking and prioritizing rules]]).
* '''Maximum number of days to departure date on all legs''' - if the setting is enabled, the rule is not triggered if the set value is exceeded.
* '''List of allowed days to start search''' - the serial number of the day of the week (starting from 1), on which it is allowed to start search.
* '''Strategy of processing rules with matching packets''' - determines the way of action when two or more rules with identical search packages are triggered, if any of these rules contains priority/undesirable airlines (parameters "Airlines for transfer as obligatory in GDS" and "airlines to be excluded from issuing"). The parameter can take three values:
**'''Constrict''' - narrowing the search results, it is the default value and corresponds to the logic of rule processing BEFORE adding this parameter. In this mode, if there is a pair of "Common rule without filtering by airlines" + "Private rule with filter", it is the private rule that will trigger; the common rule will be ignored in favor of the private one. If at least one of the triggered rules is set to Constrict, then all rules will be narrowed.
**'''Expand''' is an expansion of search results. In this mode, if there is such a pair, both rules will trigger, and GDS will send parallel requests with and without filtering by airlines. If there are rules with the same requisite package for each package, the parameters of the rules are merged. If there are several matching rules with the airlines filter, all the filters are merged. The airlines that are required to be sent to the GDS are merged. If there are lists of excluded airlines, their values are removed from the list of mandatory airlines. If there are no obligatory airlines, only the list of excluded airlines will be filled in.
**'''Independent''' - rules are not merged under any circumstances. Rules with this option are processed separately from all other rules and are added to the applied ones. Thus one more search is added and such rules are excluded from the association logic in matched packages.
*'''Work also for reverse segments''' - if this option is enabled, the departure/arrival points specified in the rule will be allowed for the route with departure/arrival points in reverse - cities are checked both for OW requests there and OW - requests in the opposite direction from the specified one, including RT. The button will allow, within the framework of the departure/arrival city list rule, flights in the opposite direction as well (arrival points are checked as departure points, and departure points as arrival points).
'''Attention!''' The '''Include return segments''' setting is currently unstable, please do not use it temporarily.

'''Attention!''' Enabling departure city inversion and arrival city inversion within the same rule will NOT invert the direction of the flight, you will need to enable the inverse rule logic to invert the direction.

''''' Adding additional parameters to the request in GDS '''''
* '''Airlines to pass as mandatory to GDS''' - The airlines listed are passed as mandatory in the request to GDS. When attempting to limit a search request to certain airlines, you should consider whether the specified airlines are contained in the list of mandatory airlines for transmission to GDS in the router's rules. If the specified airlines are contained in the obligatory list in router rules, then the intersection of airlines from two lists (from router rules and from the request to the air server) is sent to the request. If the list of mandatory airlines is missing in the rule, the airlines are taken from the request.
* '''Airlines required to be excluded from search results''' - the airlines that are in the list are marked as undesirable for the search results while requesting from GDS.
'''Attention!''' The options "Airlines to be passed as obligatory to GDS" and "Airlines that should be excluded from search results" are not supported by all aviation content providers. The following does not support this: [[API_AviaCenter|My Agent (Aviacenter)]]
* '''Enables replacement of economy/premium economy class in the query with All''' - enables search by all [[Service class|classes]] if economy or premium economy class is specified in the request.

* '''Add premium version of the requested class''' - enables additional requests for the premium version of the class specified in the search.
* '''Override preferred flight class''' - the flight class, specified by the user in the search parameters, will be changed to the preferred class when requesting to GDS.
* '''Maximum number of flights in GDS response''' - the number of flights from each GDS in the search results:
**for GDS Sabre only fixed values can be used: 50/100/200,
**for GDS Galileo the parameter does not work,
**for GDS Amadeus, Sirena Travel, uAPI you can specify any positive integer number.
* '''Search for minimum and minimum returnable fares''' - adds a parameter that asks for return fares with minimum price along with minimum fares. If the [[Search_minimum_return_fares|option is enabled]]], more return fares are displayed in the search results.
* '''Request public fares only''' - this option is available for GDS Sabre only. Allows you to additionally retrieve and display to the client in search results not only the basic fares of the airline, which are usually private, but also more expensive public fares. An example of the settings usage - search for the BASIC and FLEX fare families at S7 Airlines in case if the agent has an access to them for the RCC, as by default the GDS will return only the cheapest BASIC fares for each flight.
* '''Restrict requesting only for direct flights''' - allows you to disallow searching for flights without connections to specific destinations. If this option is enabled and the user has requested a direct flight, and at least one of the requested segments fits the rule, then the rule is not considered to work and the search is not started.
* '''Maximum number of connections''' - allows you to limit the maximum number of connections in the search results. The restriction applies to each requested shoulder. It is possible to limit the number of connections from 0 (direct flights) to 3 (flights with given or less number of connections). The functionality is implemented for GDS Amadeus, Sabre, Galileo and Galileo uAPI.
'''Attention!''' If two rules are triggered simultaneously for searching in the same packet, one of which specifies "Airlines for transfer as mandatory to GDS" and "Airlines to be excluded from issuance", only "Airlines for transfer as mandatory to GDS" will be sent to the provider.

== Tags in Nemo Connect ==
A '''Tag''' is a label that serves to identify the category or group to which an item belongs.

Tags in Websky are only used for the Nemo Connect router.

When the Nemo Connect router is enabled, tags corresponding to the request parameters are automatically added to the request from Websky to Nemo Connect.

Tags are sent to the router along with the request. They indicate request data, such as: the type of user making the search request (manager - ''mgr'', agent - ''agt'' or anonymous user - ''anon''), the type of search (agent API - ''api'' , meta-search - ''meta'').
Possible tags:
*''b2b'' - search request from a B2B account,
*''b2c'' - search request from a B2C account,
*''usr'' - search request as a registered user,
*''exp'' - search request on behalf of an expert,
*''mgr'' - search request on behalf of a manager,
*''agt'' - search launched by the user of the root agency,
*''corp'' - search launched by the corporate client of the agency,
*''subagt'' - search launched by the user of the subagency,
*''anon'' - search request launched by an anonymous user,
*''api'' - the search is launched through the agency API,
*''meta'' - the search is launched through the meta-search,
as well as tags containing:
*''user number'' - the user who launched the search,
*''number of the group'' whose user launched the search,
*''number of the subagency and agency'' of the user who started the search.

== Adding a search routing rule for Nemo Connect on the Websky side ==

To create a routing rule:

# Go to '''Product control → Airlines → Processes → Search Process → Router Settings'''.
# Select the desired user, group or agency '''Edit'''.
# Click '''Create a new entry'''.
# Set the parameters of the rule (see [[Nemo Connect search request router#Search routing parameters in Nemo Connect|Search routing parameters in Nemo Connect]]:
#* Specify conditions for applying a rule - search request parameters, under which the search will be performed by this rule.
#* Specify if you want to invert one or another search request parameter (country/city/arrival or departure airport).
#* Specify one or more [[Nemo Connect requisite packages]] to be searched when applying the rule.
#* Specify additional parameters that will be applied to the search request when applying the package.

#* Select the type of rule, Constrict or Expand or Independent, it will determine what the airline filter will be used for.
# Click the '''Save''' button.


'''Attention!''' If rules are set on a particular user/group, then only the rules of the user/group will be used.<br> And if there are other rules higher in the nesting hierarchy, for example on the agency, then those rules will be ignored.<br> In case a user/group has no rules of its own, then the first rules in the hierarchy above will be used.<br>

===Import search query routing rules into Websky ===
In addition to creating rules, you can import rules from the admin panel of Nemo Connect. The system will completely transfer all the settings from the associated Nemo Connect agency to the selected user or Nemo Travel group.
'''Attention!''' When you import settings, your current router rules are deleted. <br>
The associated agency is set under the administrator in ''''For tech support → Nemo Connect Web Services → Interaction settings'''. There you need to fill in the following fields:
* User ID in Nemo Connect.
* User login in Nemo Connect.
* User password in Nemo Connect.
* The .net server environment being used.

== Features of the Websky side displaying the router settings table==


* A row in the table corresponds to one router rule.
* The columns correspond to the settings of the router. For details, see [[Search_router_Nemo Connect#Search routing settings in Nemo Connect|Search routing settings in Nemo Connect]]
* Column ''''Intersection with''' shows identifiers of rules that either exactly match the rule (whose string we are considering), or our rule is a special case of the rules specified in the column. The "Intersection with" column helps you to see the intersection of rules and gives you a better understanding of the total mass of router rules.

'''Example'''

{| class="wikitable" border="2"
|-
|'''Rule ID'''|| '''Intersects with'''|| '''Search Parameters'''
|-
| 001 || || Flights from France
|-
| 002 || 001 || Flights from Paris
|}

== Examples of routing rules in Nemo Connect ==

====Rules for including P subclass in search results ===

For Azerbaijan Airlines (J2) subclass P is the budget subclass of economy class, while for most airlines P is first class. Since Websky recognizes this subclass as first class, it is by default not available for Economy class flights.

To get flights in this subclass in the output, you need to have the system ask for both business and economy class, and then filter the results. The Nemo Connect router provides the necessary settings to adjust the request to GDS to obtain the desired rendition.

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule ''' button.
# Check the '''Rule Enabled ''' checkbox to activate the rule.
# Enter the numbers (id) of the prop packets in Nemo Connect that will be affected by the rule in the '''IDs of packages to be searched ''' field.
# Check the '''Enable Economy/Premium Economy Class Substitution in the request for All ''' checkbox.
# Enter the '''Rule Name''' for your convenience.
# Click the '''Save''' button.

The rule replaces ''Economy'' and ''Premium Economy'' class in the GDS request with ''All'' for the specified packages. Thus when requesting economy class fares, GDS will send flights of all classes. Unwanted results can be filtered out with [[Search results filters (Air tickets)| search results filters]].

== See also ==
*[[Search request router]]
*[[Websky search request router]]
*[[Search (Air tickets)]]
*[[GDS|Global Distribution System]]
*[[Websky requisite packages]]
*[[Search request filters (Air tickets)]]
*[[Search result filters (Air tickets)]]
*[[Search result mixer (Air tickets)]]
*[[Currency]]

Nemo Connect search request router

2021-03-21T17:28:14Z

I shaletin: /* Enabling the Nemo Connect search router */

==Purpose==
The search request router is used to automate the selection of requisite packages for [[Search (Air Tickets)|search]] based on search query parameters.<br>
The agency can set up a profitable search scheme for:
* searching across [[GDS]] in multiple zones,
* issuing more varied fares with minimal search transaction costs.

It is possible to bind requisite packages to a certain geography, for example, so that [[GDS Sirena Travel]] could search only domestic Russian flights.

== Working Principle ==

[[Nemo Connect search router|Routing]] search requests in Nemo Connect is configured in [[Nemo Connect search router|Enable Nemo Connect search router]].

===Blocking and prioritizing rules===
Using the router in the classic version assumes that if more than one rule fits the request, all rules are triggered and the request is routed to all triggered packages. <br />Via the Nemo Connect router, you can set up rules in such a way that '''when rules intersect, only one triggers'''. To do this, rules are assigned the '''blocking''' status.
*If there is at least one blocking rule among the rules suitable for the request, the router will choose one rule by priority.
*If there are '''no blocking rules''' among the rules suitable for the request, then '''all rules will be applied'''.

Rule priority is determined by the rule number (ID), or assigned manually using the ''Rule Priority'' parameter. The higher the number, the higher the priority. (see section [[Nemo Connect Search Router#Search request routing parameters in Nemo Connect|Search request routing parameters in Nemo Connect]]).
*If there is a '''blocking''' rule among those suitable for the request, and '''manual priority''' is set for each triggered rule, then the rule for triggering is '''chosen according to the manual priority'''.
*If there is a '''blocking rule''' among those that match the request, and if manual priority is not '''set for at least one triggered rule''', then the rule is '''chosen by rule number'''.

== Features of sending requests when the Nemo Connect router is running ==

'''Attention!''' Once the Nemo Connect router is turned on, do not use geographic restrictions in Websky packets.

With the Nemo Connect router turned on, packet requests are distributed to the Nemo Connect router outside of Websky, so Websky's '''fine-tuning''' package usage restriction is no longer triggered. The search request passes through the connection requisites of the package selected in the fine-tuning to the Nemo Connect router, which distributes the request into packets according to its own rules.

'''Attention!''' For Websky's connection to Nemo Connect to be realized, at least 1 package must be included in the fine-tuning. This is a prerequisite, because Websky's requisites specify the details of the connection to Nemo Connect.

== Enabling the Nemo Connect search router ==
To enable the search request router for an agency you must:
<br>
To '''Websky''':

'''Manager''':
# Go to '''Product control → Airlines → Processes → Search Process → Fine Tuning'''.
# '''Enable''' the ''Use Nemo Connect router'' option.
# In the '''Requisites from which package will be used for the search request to Nemo Connect''', select the requisite package.

'''Administrator''' (specify which settings the system will look at when searching):
# Go to '''For tech support → Nemo Connect Web Services → Interaction settings'''.
# Activate the '''Router settings''' option under '''Use settings in the Air Server from Nemo 1 for partitions''.
In '''Nemo Connect''':
# Go to Avia Settings → Search Settings → Router Settings
# Enable the '''Use Air Router''' option.

It is prohibited to make routing rules in Websky. Websky search router is recommended to be disabled.

== Creating a search routing rule on the Nemo Connect side ==

To create a routing rule:

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule''' button.
# Enable the rule.
# Set the rule parameters (see [[Search request router#Search router parameters in Nemo Connect|Search router parameters in Nemo Connect]]):
#* Specify the conditions for applying a rule - search request parameters under which the search will be performed by this rule.
#* Specify one or several [[Nemo Connect requisite packages]] which will be searched when the rule is applied.
#* Set the additional parameters that will be applied to the search request when applying the package.
# Click the '''Save''' button.

'''Attention!''' You can create routing rules not only on the Nemo Connect side, but also on the Websky side (see [[Nemo Connect search request router#Adding a search request routing rule for Nemo Connect on the Websky side|Adding a search request routing rule for Nemo Connect on the Websky side]]).

==Search request routing parameters in Nemo Connect==

* '''Rule name''' - the name for easy work with rules.
* '''Rule enabled''' - enables the rule.
* '''Packet IDs to be searched''' - the numbers of the requisite packages ''from Nemo2.0'' (see "Fine-tuning", first column), which will be searched for when the rule is triggered. '''Attention!''' The field is mandatory. It is forbidden to contain the numbers of production and test packages of the requisites at the same time.

'''''Conditions of rule application'''''
* '''List of departure countries''' - the countries of departure at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Arrival countries list''' - arrival countries, at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Departure cities list''' - IATA codes of departure cities, which will trigger this requisite package.
* '''Arrival City List''' - IATA codes of arrival cities, which will trigger this requisite package.
* '''Arrival Airport List''' - IATA codes of arrival airports, which will trigger the requisite package.
* '''Departure Airport List''' - IATA codes of departure airports which will trigger this requisite package.
* '''Disallow complex routes (more than 2 segments in the request)'''- for the complex routes search, the rule will be triggered only if there are no more than two segments in the route.
* '''All flight segments must satisfy route requirements''' - the rule is triggered if every flight segment satisfies the rule parameters. If this option is disabled, at least one segment must satisfy the conditions of the filter rule.
* '''RT-Flights Only''' - the rule applies to roundtrip flights only.
* '''Reverse rule logic''' - includes inversion of the rule's geographical restrictions (logic like ''everything but''). <br /> For example, if the ''RU'' country is specified in the ''List of Departing Countries'' parameter when this option is enabled, the rule will apply to all flights except those departing from Russia.
* '''Invert departure/arrival countries''' - enables the inversion only by arrival/departure countries (logic like ''all except''). <br/> For example if the ''List of Departing Countries'' parameter is set to ''AU'' then all the flights except the ones departing from Australia will be inverted.
* '''Invert departure/arrival cities''' - enables the inversion only by arrival/departure cities (logic like ''everything but''). <br/> For example if the ''List of departure cities'' parameter is set to ''VOZ'', all the flights except for the ones from Voronezh will be included.
* '''Invert departure/arrival airports''' - switches on the inversion by arrival/departure airports only (logic like ''everything but''). <br/> For example if you have ''BWI'' in the ''Arrival airports list'' option checked, then all flights except the Baltimore/Washington area will be affected, and flights from Washington DC will not be affected.

* '''Required tags for this rule to trigger''' - mandatory tags in the search request for the rule to trigger. [[Nemo Connect Search Router#Tags in Nemo Connect|Tags in Nemo Connect]].
* '''Tags for which rule is not allowed to trigger''' - if there are tags from this list in the request, the rule will not be applied.

* '''Rule uniqueness feature''' - assigns blocking status to a rule. If this option is enabled and if there is at least one blocking rule among the rules suitable for the request, the router will select one rule by priority. If there are no matching rules, all the rules will be applied (see section [[Nemo Connect search request router#Blocking and priority of rules|Blocking and priority of rules]]).
* '''Rule priority''' - works only for rules with '''Blocking rule''' option enabled. Assigns priority to a rule - the higher the number, the higher the priority. When blocking rules, the one with the highest priority is triggered (see section [[Nemo Connect search request router#Blocking and prioritizing rules|Blocking and prioritizing rules]]).
* '''Maximum number of days to departure date on all legs''' - if the setting is enabled, the rule is not triggered if the set value is exceeded.
* '''List of allowed days to start search''' - the serial number of the day of the week (starting from 1), on which it is allowed to start search.
* '''Strategy of processing rules with matching packets''' - determines the way of action when two or more rules with identical search packages are triggered, if any of these rules contains priority/undesirable airlines (parameters "Airlines for transfer as obligatory in GDS" and "airlines to be excluded from issuing"). The parameter can take three values:
**'''Constrict''' - narrowing the search results, it is the default value and corresponds to the logic of rule processing BEFORE adding this parameter. In this mode, if there is a pair of "Common rule without filtering by airlines" + "Private rule with filter", it is the private rule that will trigger; the common rule will be ignored in favor of the private one. If at least one of the triggered rules is set to Constrict, then all rules will be narrowed.
**'''Expand''' is an expansion of search results. In this mode, if there is such a pair, both rules will trigger, and GDS will send parallel requests with and without filtering by airlines. If there are rules with the same requisite package for each package, the parameters of the rules are merged. If there are several matching rules with the airlines filter, all the filters are merged. The airlines that are required to be sent to the GDS are merged. If there are lists of excluded airlines, their values are removed from the list of mandatory airlines. If there are no obligatory airlines, only the list of excluded airlines will be filled in.
**'''Independent''' - rules are not merged under any circumstances. Rules with this option are processed separately from all other rules and are added to the applied ones. Thus one more search is added and such rules are excluded from the association logic in matched packages.
*'''Work also for reverse segments''' - if this option is enabled, the departure/arrival points specified in the rule will be allowed for the route with departure/arrival points in reverse - cities are checked both for OW requests there and OW - requests in the opposite direction from the specified one, including RT. The button will allow, within the framework of the departure/arrival city list rule, flights in the opposite direction as well (arrival points are checked as departure points, and departure points as arrival points).
'''Attention!''' The '''Include return segments''' setting is currently unstable, please do not use it temporarily.

'''Attention!''' Enabling departure city inversion and arrival city inversion within the same rule will NOT invert the direction of the flight, you will need to enable the inverse rule logic to invert the direction.

''''' Adding additional parameters to the request in GDS '''''
* '''Airlines to pass as mandatory to GDS''' - The airlines listed are passed as mandatory in the request to GDS. When attempting to limit a search request to certain airlines, you should consider whether the specified airlines are contained in the list of mandatory airlines for transmission to GDS in the router's rules. If the specified airlines are contained in the obligatory list in router rules, then the intersection of airlines from two lists (from router rules and from the request to the air server) is sent to the request. If the list of mandatory airlines is missing in the rule, the airlines are taken from the request.
* '''Airlines required to be excluded from search results''' - the airlines that are in the list are marked as undesirable for the search results while requesting from GDS.
'''Attention!''' The options "Airlines to be passed as obligatory to GDS" and "Airlines that should be excluded from search results" are not supported by all aviation content providers. The following does not support this: [[API_AviaCenter|My Agent (Aviacenter)]]
* '''Enables replacement of economy/premium economy class in the query with All''' - enables search by all [[Service class|classes]] if economy or premium economy class is specified in the request.

* '''Add premium version of the requested class''' - enables additional requests for the premium version of the class specified in the search.
* '''Override preferred flight class''' - the flight class, specified by the user in the search parameters, will be changed to the preferred class when requesting to GDS.
* '''Maximum number of flights in GDS response''' - the number of flights from each GDS in the search results:
**for GDS Sabre only fixed values can be used: 50/100/200,
**for GDS Galileo the parameter does not work,
**for GDS Amadeus, Sirena Travel, uAPI you can specify any positive integer number.
* '''Search for minimum and minimum returnable fares''' - adds a parameter that asks for return fares with minimum price along with minimum fares. If the [[Search_minimum_return_fares|option is enabled]]], more return fares are displayed in the search results.
* '''Request public fares only''' - this option is available for GDS Sabre only. Allows you to additionally retrieve and display to the client in search results not only the basic fares of the airline, which are usually private, but also more expensive public fares. An example of the settings usage - search for the BASIC and FLEX fare families at S7 Airlines in case if the agent has an access to them for the RCC, as by default the GDS will return only the cheapest BASIC fares for each flight.
* '''Restrict requesting only for direct flights''' - allows you to disallow searching for flights without connections to specific destinations. If this option is enabled and the user has requested a direct flight, and at least one of the requested segments fits the rule, then the rule is not considered to work and the search is not started.
* '''Maximum number of connections''' - allows you to limit the maximum number of connections in the search results. The restriction applies to each requested shoulder. It is possible to limit the number of connections from 0 (direct flights) to 3 (flights with given or less number of connections). The functionality is implemented for GDS Amadeus, Sabre, Galileo and Galileo uAPI.
'''Attention!''' If two rules are triggered simultaneously for searching in the same packet, one of which specifies "Airlines for transfer as mandatory to GDS" and "Airlines to be excluded from issuance", only "Airlines for transfer as mandatory to GDS" will be sent to the provider.

== Tags in Nemo Connect ==
A '''Tag''' is a label that serves to identify the category or group to which an item belongs.

Tags in Websky are only used for the Nemo Connect router.

When the Nemo Connect router is enabled, tags corresponding to the request parameters are automatically added to the request from Websky to Nemo Connect.

Tags are sent to the router along with the request. They indicate request data, such as: the type of user making the search request (manager - ''mgr'', agent - ''agt'' or anonymous user - ''anon''), the type of search (agent API - ''api'' , meta-search - ''meta'').
Possible tags:
*''b2b'' - search request from a B2B account,
*''b2c'' - search request from a B2C account,
*''usr'' - search request as a registered user,
*''exp'' - search request on behalf of an expert,
*''mgr'' - search request on behalf of a manager,
*''agt'' - search launched by the user of the root agency,
*''corp'' - search launched by the corporate client of the agency,
*''subagt'' - search launched by the user of the subagency,
*''anon'' - search request launched by an anonymous user,
*''api'' - the search is launched through the agency API,
*''meta'' - the search is launched through the meta-search,
as well as tags containing:
*''user number'' - the user who launched the search,
*''number of the group'' whose user launched the search,
*''number of the subagency and agency'' of the user who started the search.

== Adding a search routing rule for Nemo Connect on the Websky side ==

To create a routing rule:

# Go to '''Product control → Airlines → Processes → Search Process → Router Settings'''.
# Select the desired user, group or agency '''Edit'''.
# Click '''Create a new entry'''.
# Set the parameters of the rule (see [[Nemo Connect search request router#Search routing parameters in Nemo Connect|Search routing parameters in Nemo Connect]]:
#* Specify conditions for applying a rule - search request parameters, under which the search will be performed by this rule.
#* Specify if you want to invert one or another search request parameter (country/city/arrival or departure airport).
#* Specify one or more [[Nemo Connect requisite packages]] to be searched when applying the rule.
#* Specify additional parameters that will be applied to the search request when applying the package.

#* Select the type of rule, Constrict or Expand or Independent, it will determine what the airline filter will be used for.
# Click the '''Save''' button.


'''Attention!''' If rules are set on a particular user/group, then only the rules of the user/group will be used.<br> And if there are other rules higher in the nesting hierarchy, for example on the agency, then those rules will be ignored.<br> In case a user/group has no rules of its own, then the first rules in the hierarchy above will be used.<br>

===Import search query routing rules into Websky ===
In addition to creating rules, you can import rules from the admin panel of Nemo Connect. The system will completely transfer all the settings from the associated Nemo Connect agency to the selected user or Nemo Travel group.
'''Attention!''' When you import settings, your current router rules are deleted. <br>
The associated agency is set under the administrator in ''''For tech support → Nemo Connect Web Services → Interaction settings'''. There you need to fill in the following fields:
* User ID in Nemo Connect.
* User login in Nemo Connect.
* User password in Nemo Connect.
* The .net server environment being used.

== Features of the Websky side displaying the router settings table==


* A row in the table corresponds to one router rule.
* The columns correspond to the settings of the router. For details, see [[Search_router_Nemo Connect#Search routing settings in Nemo Connect|Search routing settings in Nemo Connect]]
* Column ''''Intersection with''' shows identifiers of rules that either exactly match the rule (whose string we are considering), or our rule is a special case of the rules specified in the column. The "Intersection with" column helps you to see the intersection of rules and gives you a better understanding of the total mass of router rules.

'''Example'''

{| class="wikitable" border="2"
|-
|'''Rule ID'''|| '''Intersects with'''|| '''Search Parameters'''
|-
| 001 || || Flights from France
|-
| 002 || 001 || Flights from Paris
|}

== Examples of routing rules in Nemo Connect ==

====Rules for including P subclass in search results ===

For Azerbaijan Airlines (J2) subclass P is the budget subclass of economy class, while for most airlines P is first class. Since Websky recognizes this subclass as first class, it is by default not available for Economy class flights.

To get flights in this subclass in the output, you need to have the system ask for both business and economy class, and then filter the results. The Nemo Connect router provides the necessary settings to adjust the request to GDS to obtain the desired rendition.

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule ''' button.
# Check the '''Rule Enabled ''' checkbox to activate the rule.
# Enter the numbers (id) of the prop packets in Nemo Connect that will be affected by the rule in the '''IDs of packages to be searched ''' field.
# Check the '''Enable Economy/Premium Economy Class Substitution in the request for All ''' checkbox.
# Enter the '''Rule Name''' for your convenience.
# Click the '''Save''' button.

The rule replaces ''Economy'' and ''Premium Economy'' class in the GDS request with ''All'' for the specified packages. Thus when requesting economy class fares, GDS will send flights of all classes. Unwanted results can be filtered out with [[Search results filters (Air tickets)| search results filters]].

== See also ==
*[[Search request router]]
*[[Websky search request router]]
*[[Search (Air tickets)]]
*[[GDS|Global Distribution System]]
*[[Websky requisite packages]]
*[[Search request filters (Air tickets)]]
*[[Search result filters (Air tickets)]]
*[[Search result mixer (Air tickets)]]
*[[Currency]]

Nemo Connect search request router

2021-03-21T17:27:51Z

I shaletin: /* Working Principle */

==Purpose==
The search request router is used to automate the selection of requisite packages for [[Search (Air Tickets)|search]] based on search query parameters.<br>
The agency can set up a profitable search scheme for:
* searching across [[GDS]] in multiple zones,
* issuing more varied fares with minimal search transaction costs.

It is possible to bind requisite packages to a certain geography, for example, so that [[GDS Sirena Travel]] could search only domestic Russian flights.

== Working Principle ==

[[Nemo Connect search router|Routing]] search requests in Nemo Connect is configured in [[Nemo Connect search router|Enable Nemo Connect search router]].

===Blocking and prioritizing rules===
Using the router in the classic version assumes that if more than one rule fits the request, all rules are triggered and the request is routed to all triggered packages. <br />Via the Nemo Connect router, you can set up rules in such a way that '''when rules intersect, only one triggers'''. To do this, rules are assigned the '''blocking''' status.
*If there is at least one blocking rule among the rules suitable for the request, the router will choose one rule by priority.
*If there are '''no blocking rules''' among the rules suitable for the request, then '''all rules will be applied'''.

Rule priority is determined by the rule number (ID), or assigned manually using the ''Rule Priority'' parameter. The higher the number, the higher the priority. (see section [[Nemo Connect Search Router#Search request routing parameters in Nemo Connect|Search request routing parameters in Nemo Connect]]).
*If there is a '''blocking''' rule among those suitable for the request, and '''manual priority''' is set for each triggered rule, then the rule for triggering is '''chosen according to the manual priority'''.
*If there is a '''blocking rule''' among those that match the request, and if manual priority is not '''set for at least one triggered rule''', then the rule is '''chosen by rule number'''.

== Features of sending requests when the Nemo Connect router is running ==

'''Attention!''' Once the Nemo Connect router is turned on, do not use geographic restrictions in Websky packets.

With the Nemo Connect router turned on, packet requests are distributed to the Nemo Connect router outside of Websky, so Websky's '''fine-tuning''' package usage restriction is no longer triggered. The search request passes through the connection requisites of the package selected in the fine-tuning to the Nemo Connect router, which distributes the request into packets according to its own rules.

'''Attention!''' For Websky's connection to Nemo Connect to be realized, at least 1 package must be included in the fine-tuning. This is a prerequisite, because Websky's requisites specify the details of the connection to Nemo Connect.

== Enabling the Nemo Connect search router ==
To enable the search request router for an agency you must:
<br>
To '''Websky''':

'''Manager''':
# Go to '''Sales Management → Airlines → Processes → Search Process → Fine Tuning''.
# '''Enable''' the ''Use Nemo Connect router'' option.
# In the '''Requisites from which package will be used for the search request to Nemo Connect''', select the requisite package.

'''Administrator''' (specify which settings the system will look at when searching):
# Go to '''For tech support → Nemo Connect Web Services → Interaction settings'''.
# Activate the '''Router settings''' option under '''Use settings in the Air Server from Nemo 1 for partitions''.
In '''Nemo Connect''':
# Go to Avia Settings → Search Settings → Router Settings
# Enable the '''Use Air Router''' option.

It is prohibited to make routing rules in Websky. Websky search router is recommended to be disabled.

== Creating a search routing rule on the Nemo Connect side ==

To create a routing rule:

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule''' button.
# Enable the rule.
# Set the rule parameters (see [[Search request router#Search router parameters in Nemo Connect|Search router parameters in Nemo Connect]]):
#* Specify the conditions for applying a rule - search request parameters under which the search will be performed by this rule.
#* Specify one or several [[Nemo Connect requisite packages]] which will be searched when the rule is applied.
#* Set the additional parameters that will be applied to the search request when applying the package.
# Click the '''Save''' button.

'''Attention!''' You can create routing rules not only on the Nemo Connect side, but also on the Websky side (see [[Nemo Connect search request router#Adding a search request routing rule for Nemo Connect on the Websky side|Adding a search request routing rule for Nemo Connect on the Websky side]]).

==Search request routing parameters in Nemo Connect==

* '''Rule name''' - the name for easy work with rules.
* '''Rule enabled''' - enables the rule.
* '''Packet IDs to be searched''' - the numbers of the requisite packages ''from Nemo2.0'' (see "Fine-tuning", first column), which will be searched for when the rule is triggered. '''Attention!''' The field is mandatory. It is forbidden to contain the numbers of production and test packages of the requisites at the same time.

'''''Conditions of rule application'''''
* '''List of departure countries''' - the countries of departure at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Arrival countries list''' - arrival countries, at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Departure cities list''' - IATA codes of departure cities, which will trigger this requisite package.
* '''Arrival City List''' - IATA codes of arrival cities, which will trigger this requisite package.
* '''Arrival Airport List''' - IATA codes of arrival airports, which will trigger the requisite package.
* '''Departure Airport List''' - IATA codes of departure airports which will trigger this requisite package.
* '''Disallow complex routes (more than 2 segments in the request)'''- for the complex routes search, the rule will be triggered only if there are no more than two segments in the route.
* '''All flight segments must satisfy route requirements''' - the rule is triggered if every flight segment satisfies the rule parameters. If this option is disabled, at least one segment must satisfy the conditions of the filter rule.
* '''RT-Flights Only''' - the rule applies to roundtrip flights only.
* '''Reverse rule logic''' - includes inversion of the rule's geographical restrictions (logic like ''everything but''). <br /> For example, if the ''RU'' country is specified in the ''List of Departing Countries'' parameter when this option is enabled, the rule will apply to all flights except those departing from Russia.
* '''Invert departure/arrival countries''' - enables the inversion only by arrival/departure countries (logic like ''all except''). <br/> For example if the ''List of Departing Countries'' parameter is set to ''AU'' then all the flights except the ones departing from Australia will be inverted.
* '''Invert departure/arrival cities''' - enables the inversion only by arrival/departure cities (logic like ''everything but''). <br/> For example if the ''List of departure cities'' parameter is set to ''VOZ'', all the flights except for the ones from Voronezh will be included.
* '''Invert departure/arrival airports''' - switches on the inversion by arrival/departure airports only (logic like ''everything but''). <br/> For example if you have ''BWI'' in the ''Arrival airports list'' option checked, then all flights except the Baltimore/Washington area will be affected, and flights from Washington DC will not be affected.

* '''Required tags for this rule to trigger''' - mandatory tags in the search request for the rule to trigger. [[Nemo Connect Search Router#Tags in Nemo Connect|Tags in Nemo Connect]].
* '''Tags for which rule is not allowed to trigger''' - if there are tags from this list in the request, the rule will not be applied.

* '''Rule uniqueness feature''' - assigns blocking status to a rule. If this option is enabled and if there is at least one blocking rule among the rules suitable for the request, the router will select one rule by priority. If there are no matching rules, all the rules will be applied (see section [[Nemo Connect search request router#Blocking and priority of rules|Blocking and priority of rules]]).
* '''Rule priority''' - works only for rules with '''Blocking rule''' option enabled. Assigns priority to a rule - the higher the number, the higher the priority. When blocking rules, the one with the highest priority is triggered (see section [[Nemo Connect search request router#Blocking and prioritizing rules|Blocking and prioritizing rules]]).
* '''Maximum number of days to departure date on all legs''' - if the setting is enabled, the rule is not triggered if the set value is exceeded.
* '''List of allowed days to start search''' - the serial number of the day of the week (starting from 1), on which it is allowed to start search.
* '''Strategy of processing rules with matching packets''' - determines the way of action when two or more rules with identical search packages are triggered, if any of these rules contains priority/undesirable airlines (parameters "Airlines for transfer as obligatory in GDS" and "airlines to be excluded from issuing"). The parameter can take three values:
**'''Constrict''' - narrowing the search results, it is the default value and corresponds to the logic of rule processing BEFORE adding this parameter. In this mode, if there is a pair of "Common rule without filtering by airlines" + "Private rule with filter", it is the private rule that will trigger; the common rule will be ignored in favor of the private one. If at least one of the triggered rules is set to Constrict, then all rules will be narrowed.
**'''Expand''' is an expansion of search results. In this mode, if there is such a pair, both rules will trigger, and GDS will send parallel requests with and without filtering by airlines. If there are rules with the same requisite package for each package, the parameters of the rules are merged. If there are several matching rules with the airlines filter, all the filters are merged. The airlines that are required to be sent to the GDS are merged. If there are lists of excluded airlines, their values are removed from the list of mandatory airlines. If there are no obligatory airlines, only the list of excluded airlines will be filled in.
**'''Independent''' - rules are not merged under any circumstances. Rules with this option are processed separately from all other rules and are added to the applied ones. Thus one more search is added and such rules are excluded from the association logic in matched packages.
*'''Work also for reverse segments''' - if this option is enabled, the departure/arrival points specified in the rule will be allowed for the route with departure/arrival points in reverse - cities are checked both for OW requests there and OW - requests in the opposite direction from the specified one, including RT. The button will allow, within the framework of the departure/arrival city list rule, flights in the opposite direction as well (arrival points are checked as departure points, and departure points as arrival points).
'''Attention!''' The '''Include return segments''' setting is currently unstable, please do not use it temporarily.

'''Attention!''' Enabling departure city inversion and arrival city inversion within the same rule will NOT invert the direction of the flight, you will need to enable the inverse rule logic to invert the direction.

''''' Adding additional parameters to the request in GDS '''''
* '''Airlines to pass as mandatory to GDS''' - The airlines listed are passed as mandatory in the request to GDS. When attempting to limit a search request to certain airlines, you should consider whether the specified airlines are contained in the list of mandatory airlines for transmission to GDS in the router's rules. If the specified airlines are contained in the obligatory list in router rules, then the intersection of airlines from two lists (from router rules and from the request to the air server) is sent to the request. If the list of mandatory airlines is missing in the rule, the airlines are taken from the request.
* '''Airlines required to be excluded from search results''' - the airlines that are in the list are marked as undesirable for the search results while requesting from GDS.
'''Attention!''' The options "Airlines to be passed as obligatory to GDS" and "Airlines that should be excluded from search results" are not supported by all aviation content providers. The following does not support this: [[API_AviaCenter|My Agent (Aviacenter)]]
* '''Enables replacement of economy/premium economy class in the query with All''' - enables search by all [[Service class|classes]] if economy or premium economy class is specified in the request.

* '''Add premium version of the requested class''' - enables additional requests for the premium version of the class specified in the search.
* '''Override preferred flight class''' - the flight class, specified by the user in the search parameters, will be changed to the preferred class when requesting to GDS.
* '''Maximum number of flights in GDS response''' - the number of flights from each GDS in the search results:
**for GDS Sabre only fixed values can be used: 50/100/200,
**for GDS Galileo the parameter does not work,
**for GDS Amadeus, Sirena Travel, uAPI you can specify any positive integer number.
* '''Search for minimum and minimum returnable fares''' - adds a parameter that asks for return fares with minimum price along with minimum fares. If the [[Search_minimum_return_fares|option is enabled]]], more return fares are displayed in the search results.
* '''Request public fares only''' - this option is available for GDS Sabre only. Allows you to additionally retrieve and display to the client in search results not only the basic fares of the airline, which are usually private, but also more expensive public fares. An example of the settings usage - search for the BASIC and FLEX fare families at S7 Airlines in case if the agent has an access to them for the RCC, as by default the GDS will return only the cheapest BASIC fares for each flight.
* '''Restrict requesting only for direct flights''' - allows you to disallow searching for flights without connections to specific destinations. If this option is enabled and the user has requested a direct flight, and at least one of the requested segments fits the rule, then the rule is not considered to work and the search is not started.
* '''Maximum number of connections''' - allows you to limit the maximum number of connections in the search results. The restriction applies to each requested shoulder. It is possible to limit the number of connections from 0 (direct flights) to 3 (flights with given or less number of connections). The functionality is implemented for GDS Amadeus, Sabre, Galileo and Galileo uAPI.
'''Attention!''' If two rules are triggered simultaneously for searching in the same packet, one of which specifies "Airlines for transfer as mandatory to GDS" and "Airlines to be excluded from issuance", only "Airlines for transfer as mandatory to GDS" will be sent to the provider.

== Tags in Nemo Connect ==
A '''Tag''' is a label that serves to identify the category or group to which an item belongs.

Tags in Websky are only used for the Nemo Connect router.

When the Nemo Connect router is enabled, tags corresponding to the request parameters are automatically added to the request from Websky to Nemo Connect.

Tags are sent to the router along with the request. They indicate request data, such as: the type of user making the search request (manager - ''mgr'', agent - ''agt'' or anonymous user - ''anon''), the type of search (agent API - ''api'' , meta-search - ''meta'').
Possible tags:
*''b2b'' - search request from a B2B account,
*''b2c'' - search request from a B2C account,
*''usr'' - search request as a registered user,
*''exp'' - search request on behalf of an expert,
*''mgr'' - search request on behalf of a manager,
*''agt'' - search launched by the user of the root agency,
*''corp'' - search launched by the corporate client of the agency,
*''subagt'' - search launched by the user of the subagency,
*''anon'' - search request launched by an anonymous user,
*''api'' - the search is launched through the agency API,
*''meta'' - the search is launched through the meta-search,
as well as tags containing:
*''user number'' - the user who launched the search,
*''number of the group'' whose user launched the search,
*''number of the subagency and agency'' of the user who started the search.

== Adding a search routing rule for Nemo Connect on the Websky side ==

To create a routing rule:

# Go to '''Product control → Airlines → Processes → Search Process → Router Settings'''.
# Select the desired user, group or agency '''Edit'''.
# Click '''Create a new entry'''.
# Set the parameters of the rule (see [[Nemo Connect search request router#Search routing parameters in Nemo Connect|Search routing parameters in Nemo Connect]]:
#* Specify conditions for applying a rule - search request parameters, under which the search will be performed by this rule.
#* Specify if you want to invert one or another search request parameter (country/city/arrival or departure airport).
#* Specify one or more [[Nemo Connect requisite packages]] to be searched when applying the rule.
#* Specify additional parameters that will be applied to the search request when applying the package.

#* Select the type of rule, Constrict or Expand or Independent, it will determine what the airline filter will be used for.
# Click the '''Save''' button.


'''Attention!''' If rules are set on a particular user/group, then only the rules of the user/group will be used.<br> And if there are other rules higher in the nesting hierarchy, for example on the agency, then those rules will be ignored.<br> In case a user/group has no rules of its own, then the first rules in the hierarchy above will be used.<br>

===Import search query routing rules into Websky ===
In addition to creating rules, you can import rules from the admin panel of Nemo Connect. The system will completely transfer all the settings from the associated Nemo Connect agency to the selected user or Nemo Travel group.
'''Attention!''' When you import settings, your current router rules are deleted. <br>
The associated agency is set under the administrator in ''''For tech support → Nemo Connect Web Services → Interaction settings'''. There you need to fill in the following fields:
* User ID in Nemo Connect.
* User login in Nemo Connect.
* User password in Nemo Connect.
* The .net server environment being used.

== Features of the Websky side displaying the router settings table==


* A row in the table corresponds to one router rule.
* The columns correspond to the settings of the router. For details, see [[Search_router_Nemo Connect#Search routing settings in Nemo Connect|Search routing settings in Nemo Connect]]
* Column ''''Intersection with''' shows identifiers of rules that either exactly match the rule (whose string we are considering), or our rule is a special case of the rules specified in the column. The "Intersection with" column helps you to see the intersection of rules and gives you a better understanding of the total mass of router rules.

'''Example'''

{| class="wikitable" border="2"
|-
|'''Rule ID'''|| '''Intersects with'''|| '''Search Parameters'''
|-
| 001 || || Flights from France
|-
| 002 || 001 || Flights from Paris
|}

== Examples of routing rules in Nemo Connect ==

====Rules for including P subclass in search results ===

For Azerbaijan Airlines (J2) subclass P is the budget subclass of economy class, while for most airlines P is first class. Since Websky recognizes this subclass as first class, it is by default not available for Economy class flights.

To get flights in this subclass in the output, you need to have the system ask for both business and economy class, and then filter the results. The Nemo Connect router provides the necessary settings to adjust the request to GDS to obtain the desired rendition.

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule ''' button.
# Check the '''Rule Enabled ''' checkbox to activate the rule.
# Enter the numbers (id) of the prop packets in Nemo Connect that will be affected by the rule in the '''IDs of packages to be searched ''' field.
# Check the '''Enable Economy/Premium Economy Class Substitution in the request for All ''' checkbox.
# Enter the '''Rule Name''' for your convenience.
# Click the '''Save''' button.

The rule replaces ''Economy'' and ''Premium Economy'' class in the GDS request with ''All'' for the specified packages. Thus when requesting economy class fares, GDS will send flights of all classes. Unwanted results can be filtered out with [[Search results filters (Air tickets)| search results filters]].

== See also ==
*[[Search request router]]
*[[Websky search request router]]
*[[Search (Air tickets)]]
*[[GDS|Global Distribution System]]
*[[Websky requisite packages]]
*[[Search request filters (Air tickets)]]
*[[Search result filters (Air tickets)]]
*[[Search result mixer (Air tickets)]]
*[[Currency]]

Nemo Connect search request router

2021-03-21T17:27:41Z

I shaletin: Created page with "==Purpose== The search request router is used to automate the selection of requisite packages for search based on search query parameters.<br> The age..."

==Purpose==
The search request router is used to automate the selection of requisite packages for [[Search (Air Tickets)|search]] based on search query parameters.<br>
The agency can set up a profitable search scheme for:
* searching across [[GDS]] in multiple zones,
* issuing more varied fares with minimal search transaction costs.

It is possible to bind requisite packages to a certain geography, for example, so that [[GDS Sirena Travel]] could search only domestic Russian flights.

== Working Principle ==

[[Nemo Connect search router|Routing]] search requests in Nemo Connect is configured in [[Nemo Connect search router#Enable Nemo Connect search router]].

===Blocking and prioritizing rules===
Using the router in the classic version assumes that if more than one rule fits the request, all rules are triggered and the request is routed to all triggered packages. <br />Via the Nemo Connect router, you can set up rules in such a way that '''when rules intersect, only one triggers'''. To do this, rules are assigned the '''blocking''' status.
*If there is at least one blocking rule among the rules suitable for the request, the router will choose one rule by priority.
*If there are '''no blocking rules''' among the rules suitable for the request, then '''all rules will be applied'''.

Rule priority is determined by the rule number (ID), or assigned manually using the ''Rule Priority'' parameter. The higher the number, the higher the priority. (see section [[Nemo Connect Search Router#Search request routing parameters in Nemo Connect|Search request routing parameters in Nemo Connect]]).
*If there is a '''blocking''' rule among those suitable for the request, and '''manual priority''' is set for each triggered rule, then the rule for triggering is '''chosen according to the manual priority'''.
*If there is a '''blocking rule''' among those that match the request, and if manual priority is not '''set for at least one triggered rule''', then the rule is '''chosen by rule number'''.

== Features of sending requests when the Nemo Connect router is running ==

'''Attention!''' Once the Nemo Connect router is turned on, do not use geographic restrictions in Websky packets.

With the Nemo Connect router turned on, packet requests are distributed to the Nemo Connect router outside of Websky, so Websky's '''fine-tuning''' package usage restriction is no longer triggered. The search request passes through the connection requisites of the package selected in the fine-tuning to the Nemo Connect router, which distributes the request into packets according to its own rules.

'''Attention!''' For Websky's connection to Nemo Connect to be realized, at least 1 package must be included in the fine-tuning. This is a prerequisite, because Websky's requisites specify the details of the connection to Nemo Connect.

== Enabling the Nemo Connect search router ==
To enable the search request router for an agency you must:
<br>
To '''Websky''':

'''Manager''':
# Go to '''Sales Management → Airlines → Processes → Search Process → Fine Tuning''.
# '''Enable''' the ''Use Nemo Connect router'' option.
# In the '''Requisites from which package will be used for the search request to Nemo Connect''', select the requisite package.

'''Administrator''' (specify which settings the system will look at when searching):
# Go to '''For tech support → Nemo Connect Web Services → Interaction settings'''.
# Activate the '''Router settings''' option under '''Use settings in the Air Server from Nemo 1 for partitions''.
In '''Nemo Connect''':
# Go to Avia Settings → Search Settings → Router Settings
# Enable the '''Use Air Router''' option.

It is prohibited to make routing rules in Websky. Websky search router is recommended to be disabled.

== Creating a search routing rule on the Nemo Connect side ==

To create a routing rule:

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule''' button.
# Enable the rule.
# Set the rule parameters (see [[Search request router#Search router parameters in Nemo Connect|Search router parameters in Nemo Connect]]):
#* Specify the conditions for applying a rule - search request parameters under which the search will be performed by this rule.
#* Specify one or several [[Nemo Connect requisite packages]] which will be searched when the rule is applied.
#* Set the additional parameters that will be applied to the search request when applying the package.
# Click the '''Save''' button.

'''Attention!''' You can create routing rules not only on the Nemo Connect side, but also on the Websky side (see [[Nemo Connect search request router#Adding a search request routing rule for Nemo Connect on the Websky side|Adding a search request routing rule for Nemo Connect on the Websky side]]).

==Search request routing parameters in Nemo Connect==

* '''Rule name''' - the name for easy work with rules.
* '''Rule enabled''' - enables the rule.
* '''Packet IDs to be searched''' - the numbers of the requisite packages ''from Nemo2.0'' (see "Fine-tuning", first column), which will be searched for when the rule is triggered. '''Attention!''' The field is mandatory. It is forbidden to contain the numbers of production and test packages of the requisites at the same time.

'''''Conditions of rule application'''''
* '''List of departure countries''' - the countries of departure at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Arrival countries list''' - arrival countries, at which this requisite package will be triggered. The list of countries is set in '''ISO alpha 2''' format, for example '''RU'''.
* '''Departure cities list''' - IATA codes of departure cities, which will trigger this requisite package.
* '''Arrival City List''' - IATA codes of arrival cities, which will trigger this requisite package.
* '''Arrival Airport List''' - IATA codes of arrival airports, which will trigger the requisite package.
* '''Departure Airport List''' - IATA codes of departure airports which will trigger this requisite package.
* '''Disallow complex routes (more than 2 segments in the request)'''- for the complex routes search, the rule will be triggered only if there are no more than two segments in the route.
* '''All flight segments must satisfy route requirements''' - the rule is triggered if every flight segment satisfies the rule parameters. If this option is disabled, at least one segment must satisfy the conditions of the filter rule.
* '''RT-Flights Only''' - the rule applies to roundtrip flights only.
* '''Reverse rule logic''' - includes inversion of the rule's geographical restrictions (logic like ''everything but''). <br /> For example, if the ''RU'' country is specified in the ''List of Departing Countries'' parameter when this option is enabled, the rule will apply to all flights except those departing from Russia.
* '''Invert departure/arrival countries''' - enables the inversion only by arrival/departure countries (logic like ''all except''). <br/> For example if the ''List of Departing Countries'' parameter is set to ''AU'' then all the flights except the ones departing from Australia will be inverted.
* '''Invert departure/arrival cities''' - enables the inversion only by arrival/departure cities (logic like ''everything but''). <br/> For example if the ''List of departure cities'' parameter is set to ''VOZ'', all the flights except for the ones from Voronezh will be included.
* '''Invert departure/arrival airports''' - switches on the inversion by arrival/departure airports only (logic like ''everything but''). <br/> For example if you have ''BWI'' in the ''Arrival airports list'' option checked, then all flights except the Baltimore/Washington area will be affected, and flights from Washington DC will not be affected.

* '''Required tags for this rule to trigger''' - mandatory tags in the search request for the rule to trigger. [[Nemo Connect Search Router#Tags in Nemo Connect|Tags in Nemo Connect]].
* '''Tags for which rule is not allowed to trigger''' - if there are tags from this list in the request, the rule will not be applied.

* '''Rule uniqueness feature''' - assigns blocking status to a rule. If this option is enabled and if there is at least one blocking rule among the rules suitable for the request, the router will select one rule by priority. If there are no matching rules, all the rules will be applied (see section [[Nemo Connect search request router#Blocking and priority of rules|Blocking and priority of rules]]).
* '''Rule priority''' - works only for rules with '''Blocking rule''' option enabled. Assigns priority to a rule - the higher the number, the higher the priority. When blocking rules, the one with the highest priority is triggered (see section [[Nemo Connect search request router#Blocking and prioritizing rules|Blocking and prioritizing rules]]).
* '''Maximum number of days to departure date on all legs''' - if the setting is enabled, the rule is not triggered if the set value is exceeded.
* '''List of allowed days to start search''' - the serial number of the day of the week (starting from 1), on which it is allowed to start search.
* '''Strategy of processing rules with matching packets''' - determines the way of action when two or more rules with identical search packages are triggered, if any of these rules contains priority/undesirable airlines (parameters "Airlines for transfer as obligatory in GDS" and "airlines to be excluded from issuing"). The parameter can take three values:
**'''Constrict''' - narrowing the search results, it is the default value and corresponds to the logic of rule processing BEFORE adding this parameter. In this mode, if there is a pair of "Common rule without filtering by airlines" + "Private rule with filter", it is the private rule that will trigger; the common rule will be ignored in favor of the private one. If at least one of the triggered rules is set to Constrict, then all rules will be narrowed.
**'''Expand''' is an expansion of search results. In this mode, if there is such a pair, both rules will trigger, and GDS will send parallel requests with and without filtering by airlines. If there are rules with the same requisite package for each package, the parameters of the rules are merged. If there are several matching rules with the airlines filter, all the filters are merged. The airlines that are required to be sent to the GDS are merged. If there are lists of excluded airlines, their values are removed from the list of mandatory airlines. If there are no obligatory airlines, only the list of excluded airlines will be filled in.
**'''Independent''' - rules are not merged under any circumstances. Rules with this option are processed separately from all other rules and are added to the applied ones. Thus one more search is added and such rules are excluded from the association logic in matched packages.
*'''Work also for reverse segments''' - if this option is enabled, the departure/arrival points specified in the rule will be allowed for the route with departure/arrival points in reverse - cities are checked both for OW requests there and OW - requests in the opposite direction from the specified one, including RT. The button will allow, within the framework of the departure/arrival city list rule, flights in the opposite direction as well (arrival points are checked as departure points, and departure points as arrival points).
'''Attention!''' The '''Include return segments''' setting is currently unstable, please do not use it temporarily.

'''Attention!''' Enabling departure city inversion and arrival city inversion within the same rule will NOT invert the direction of the flight, you will need to enable the inverse rule logic to invert the direction.

''''' Adding additional parameters to the request in GDS '''''
* '''Airlines to pass as mandatory to GDS''' - The airlines listed are passed as mandatory in the request to GDS. When attempting to limit a search request to certain airlines, you should consider whether the specified airlines are contained in the list of mandatory airlines for transmission to GDS in the router's rules. If the specified airlines are contained in the obligatory list in router rules, then the intersection of airlines from two lists (from router rules and from the request to the air server) is sent to the request. If the list of mandatory airlines is missing in the rule, the airlines are taken from the request.
* '''Airlines required to be excluded from search results''' - the airlines that are in the list are marked as undesirable for the search results while requesting from GDS.
'''Attention!''' The options "Airlines to be passed as obligatory to GDS" and "Airlines that should be excluded from search results" are not supported by all aviation content providers. The following does not support this: [[API_AviaCenter|My Agent (Aviacenter)]]
* '''Enables replacement of economy/premium economy class in the query with All''' - enables search by all [[Service class|classes]] if economy or premium economy class is specified in the request.

* '''Add premium version of the requested class''' - enables additional requests for the premium version of the class specified in the search.
* '''Override preferred flight class''' - the flight class, specified by the user in the search parameters, will be changed to the preferred class when requesting to GDS.
* '''Maximum number of flights in GDS response''' - the number of flights from each GDS in the search results:
**for GDS Sabre only fixed values can be used: 50/100/200,
**for GDS Galileo the parameter does not work,
**for GDS Amadeus, Sirena Travel, uAPI you can specify any positive integer number.
* '''Search for minimum and minimum returnable fares''' - adds a parameter that asks for return fares with minimum price along with minimum fares. If the [[Search_minimum_return_fares|option is enabled]]], more return fares are displayed in the search results.
* '''Request public fares only''' - this option is available for GDS Sabre only. Allows you to additionally retrieve and display to the client in search results not only the basic fares of the airline, which are usually private, but also more expensive public fares. An example of the settings usage - search for the BASIC and FLEX fare families at S7 Airlines in case if the agent has an access to them for the RCC, as by default the GDS will return only the cheapest BASIC fares for each flight.
* '''Restrict requesting only for direct flights''' - allows you to disallow searching for flights without connections to specific destinations. If this option is enabled and the user has requested a direct flight, and at least one of the requested segments fits the rule, then the rule is not considered to work and the search is not started.
* '''Maximum number of connections''' - allows you to limit the maximum number of connections in the search results. The restriction applies to each requested shoulder. It is possible to limit the number of connections from 0 (direct flights) to 3 (flights with given or less number of connections). The functionality is implemented for GDS Amadeus, Sabre, Galileo and Galileo uAPI.
'''Attention!''' If two rules are triggered simultaneously for searching in the same packet, one of which specifies "Airlines for transfer as mandatory to GDS" and "Airlines to be excluded from issuance", only "Airlines for transfer as mandatory to GDS" will be sent to the provider.

== Tags in Nemo Connect ==
A '''Tag''' is a label that serves to identify the category or group to which an item belongs.

Tags in Websky are only used for the Nemo Connect router.

When the Nemo Connect router is enabled, tags corresponding to the request parameters are automatically added to the request from Websky to Nemo Connect.

Tags are sent to the router along with the request. They indicate request data, such as: the type of user making the search request (manager - ''mgr'', agent - ''agt'' or anonymous user - ''anon''), the type of search (agent API - ''api'' , meta-search - ''meta'').
Possible tags:
*''b2b'' - search request from a B2B account,
*''b2c'' - search request from a B2C account,
*''usr'' - search request as a registered user,
*''exp'' - search request on behalf of an expert,
*''mgr'' - search request on behalf of a manager,
*''agt'' - search launched by the user of the root agency,
*''corp'' - search launched by the corporate client of the agency,
*''subagt'' - search launched by the user of the subagency,
*''anon'' - search request launched by an anonymous user,
*''api'' - the search is launched through the agency API,
*''meta'' - the search is launched through the meta-search,
as well as tags containing:
*''user number'' - the user who launched the search,
*''number of the group'' whose user launched the search,
*''number of the subagency and agency'' of the user who started the search.

== Adding a search routing rule for Nemo Connect on the Websky side ==

To create a routing rule:

# Go to '''Product control → Airlines → Processes → Search Process → Router Settings'''.
# Select the desired user, group or agency '''Edit'''.
# Click '''Create a new entry'''.
# Set the parameters of the rule (see [[Nemo Connect search request router#Search routing parameters in Nemo Connect|Search routing parameters in Nemo Connect]]:
#* Specify conditions for applying a rule - search request parameters, under which the search will be performed by this rule.
#* Specify if you want to invert one or another search request parameter (country/city/arrival or departure airport).
#* Specify one or more [[Nemo Connect requisite packages]] to be searched when applying the rule.
#* Specify additional parameters that will be applied to the search request when applying the package.

#* Select the type of rule, Constrict or Expand or Independent, it will determine what the airline filter will be used for.
# Click the '''Save''' button.


'''Attention!''' If rules are set on a particular user/group, then only the rules of the user/group will be used.<br> And if there are other rules higher in the nesting hierarchy, for example on the agency, then those rules will be ignored.<br> In case a user/group has no rules of its own, then the first rules in the hierarchy above will be used.<br>

===Import search query routing rules into Websky ===
In addition to creating rules, you can import rules from the admin panel of Nemo Connect. The system will completely transfer all the settings from the associated Nemo Connect agency to the selected user or Nemo Travel group.
'''Attention!''' When you import settings, your current router rules are deleted. <br>
The associated agency is set under the administrator in ''''For tech support → Nemo Connect Web Services → Interaction settings'''. There you need to fill in the following fields:
* User ID in Nemo Connect.
* User login in Nemo Connect.
* User password in Nemo Connect.
* The .net server environment being used.

== Features of the Websky side displaying the router settings table==


* A row in the table corresponds to one router rule.
* The columns correspond to the settings of the router. For details, see [[Search_router_Nemo Connect#Search routing settings in Nemo Connect|Search routing settings in Nemo Connect]]
* Column ''''Intersection with''' shows identifiers of rules that either exactly match the rule (whose string we are considering), or our rule is a special case of the rules specified in the column. The "Intersection with" column helps you to see the intersection of rules and gives you a better understanding of the total mass of router rules.

'''Example'''

{| class="wikitable" border="2"
|-
|'''Rule ID'''|| '''Intersects with'''|| '''Search Parameters'''
|-
| 001 || || Flights from France
|-
| 002 || 001 || Flights from Paris
|}

== Examples of routing rules in Nemo Connect ==

====Rules for including P subclass in search results ===

For Azerbaijan Airlines (J2) subclass P is the budget subclass of economy class, while for most airlines P is first class. Since Websky recognizes this subclass as first class, it is by default not available for Economy class flights.

To get flights in this subclass in the output, you need to have the system ask for both business and economy class, and then filter the results. The Nemo Connect router provides the necessary settings to adjust the request to GDS to obtain the desired rendition.

# Go to '''Avia Settings → Search Settings → Router Settings'''.
# Click the '''Add Router Rule ''' button.
# Check the '''Rule Enabled ''' checkbox to activate the rule.
# Enter the numbers (id) of the prop packets in Nemo Connect that will be affected by the rule in the '''IDs of packages to be searched ''' field.
# Check the '''Enable Economy/Premium Economy Class Substitution in the request for All ''' checkbox.
# Enter the '''Rule Name''' for your convenience.
# Click the '''Save''' button.

The rule replaces ''Economy'' and ''Premium Economy'' class in the GDS request with ''All'' for the specified packages. Thus when requesting economy class fares, GDS will send flights of all classes. Unwanted results can be filtered out with [[Search results filters (Air tickets)| search results filters]].

== See also ==
*[[Search request router]]
*[[Websky search request router]]
*[[Search (Air tickets)]]
*[[GDS|Global Distribution System]]
*[[Websky requisite packages]]
*[[Search request filters (Air tickets)]]
*[[Search result filters (Air tickets)]]
*[[Search result mixer (Air tickets)]]
*[[Currency]]

Search request router

2021-03-21T16:14:42Z

I shaletin: /* Routing in Websky and Nemo Connect */

'''Router''' is a plugin of the Air tickets component of the Websky system.

== Purpose==
The search request router is used to automate the selection of requisite packages for a search based on search request parameters.
The agency can set up an advantageous search scheme for you:
* search in different GDS in several zones,
* issue more diverse fares at minimal expenses for search transactions.

You can bind requisite packages to a certain geography, for example, so that the searches of '''GDS Sirena Travel''' would only be carried out for domestic Russian flights.

==Principle of Operation==
Search request router is a combination of rules that distributes search requests to different requisite packages.

'''Search request routing''' - a function of selecting suitable requisite packages for search.

'''Search request router''' - a set of routing rules.

'''Routing rule''' - requisite package and a set of conditions under which a search request will be executed in the specified requisite package.

* Routing rule condition - a set of parameters and specified values.

* Condition parameter - a sign by which the search request will be checked during routing.

* Condition value - one or several specific parameter objects for comparison with the search request: specific continents, countries, airports, etc. If several values are specified, they are considered as alternative in the condition.

In general, one request corresponds to several suitable requisites.

The router compares the specified parameters of a search request with the rules of search request routing and defines suitable rules:
* If suitable rules are found, the system sends parallel requests to all suitable packages and performs a search by the requisites specified in them.
* If no suitable rules are found, the system will generate a message that the results are not found.

For the router to select a rule, the '''all parameters''' of the search query must match the '''all conditions''' of the rule.

== Routing in Websky and Nemo Connect ==
Routing is configured via one of two plugins:
* in '''Websky''' (see [[Websky search request router]]),
* in '''Websky Nemo Connect''' (see [[Nemo Connect search request router]]).

It is recommended to use the router in Websky Nemo Connect because it supports a more flexible mechanism for setting up rules for selecting packages and has more parameters for setting conditions in routing rules. For example, it allows you to create separate rules for different users, search and meta search APIs, and rules are created directly for packages of Websky Nemo Connect requisites without using Websky 1 requisite packages.

'''Attention!''' When using Websky Nemo Connect router, geographical restrictions of Websky 1 packages '''do not work'''.

==Examples of search request routing rules==

{| class="wikitable" border="2"
|-
|'''Rules'''||'''Search parameters'''||'''Result'''
|-
| Search for flights from France to Russia in Galileo <br/> Search for flights from France to Austria in Sabre || Flight from Paris to Moscow || Search will be performed in Galileo's flight requisites package
|}

For the '''"Round-trip"''' flights, the requisites packages are selected as follows:

{| class="wikitable" border="2"
|-
|'''Rules'''||'''Search parameters'''||'''Result'''
|-
| Search for flights from France to Russia in Galileo || Moscow-Paris-Moscow || Search will be performed in Galileo's flight requisites package
|-
| Search for flights from Russia to France in Galileo || Paris-Moscow || The search will not be performed, as there are no suitable requisite packages.
|}

For the '''Complex routes''', the requisites package is selected if the parameters of each flight segment in the search request correspond to the routing rule for the given package:

{| class="wikitable" border="2"
|-
|'''Rules'''||'''Search parameters'''||'''Result'''
|-
| Search for flights from France or Moscow to Italy or Ukraine in Galileo || Moscow - Paris - Milan || Search will be performed in Galileo's flight requisites package
|-
| Search for flights from France or Moscow to Italy or Ukraine in Galileo || Moscow - Paris - St. Petersburg || The search will not be performed, as there are no suitable requisite packages.
|}

'''Attention!''' If a package with non-working requisites is selected for search, the user will receive a message: "No matching requisites found. Check the settings".

== See also ==
*[[Websky search request router]].
*[[Nemo Connect search request router]].
*[[Search (Air Tickets)]].
*[[Global Distribution System]].
*[[Websky requisite packages]].
*[[Search requests filters (Air tickets)]].
*[[Search result filters (Air tickets)]].
*[[Search results mixer (Air Tickets)]].

Endorsement

2021-03-14T18:45:56Z

I shaletin: Created page with "'''Endorsement''' is a remark that can be added automatically or manually to an airline ticket. It is used for special information related to the specifics of using a particul..."

'''Endorsement''' is a remark that can be added automatically or manually to an airline ticket. It is used for special information related to the specifics of using a particular ticket or coupon. Examples: transfer of carriage rights from one airline to another, restrictions (e.g. Non-Refundable), additional information (such as passport number), etc.

Different suppliers have their own endorsement requirements and restrictions associated with their use.

== Endorsement requirements in Galileo ==

For a given supplier, you can enter passport details and other information in the endorsement. The total limit on the number of characters per endorsement is 147, which can be reduced depending on the airline. A maximum of 3 endorsements can be added to 1 PNR, separated by "* >".

'''Attention!''' Passport information for this supplier is entered into the Websky when booking via SSR DOCS.

Passport data entered through SSR DOCS in the endorsement is not automatically substituted. Only data entered by the airline in the 18th fare point (TICKET ENDORSEMENT) is automatically added to the endorsement; you cannot change this data.

Entry examples:

<pre>TMU1EBPSPTxxxxxxxxxxxxxxxxx VALID SU ONLY NO REROUTING</pre>

During ticketing:

<pre>TKP1EBPSPTxxxxxxxxxxxxxxx VALID SU ONLY NO REROUTING</pre>

'''Attention!''' The maximum endorsement length limit is 147 characters. An error will occur if it is exceeded. If the airline limit is less than 147 characters, the endorsement will simply cut down on the last allowed character if it exceeds the allowable length. There is no minimum length restriction. There are also no requirements on the order of precedence. The endorsement from the fare rules will always be shown first in the ticket.

== Endorsement requirements in Sabre ==

The basic information in the "endorsement" field gets automatically through the PQ record from the 18th fare point (which is the same name: TICKET ENDORSEMENTS).

'''Attention!''' The passport details for this supplier are entered into the Websky when you book via SSR DOCS.

The passport number goes into the endorsement field automatically through SSR DOCS. The date of birth does not automatically get into the endorsement. It can be added through the qualifier "‡DOB" (the system will drag the date of birth from SSR DOCS). When using a qualifier, the information is added to an existing endorsement, and the endorsement changes completely. The maximum number of characters in an endorsement is 51.<br>
The Websky is designed to add the endorsement specified in the agency settings to the automatically generated endorsement. If needed, the client can request Sabre to support longer endorsements of up to 999 characters.

== Endorsement requirements in Amadeus ==

There are 3 types of endorsements:
* ordinary, they can be viewed by everyone
* confidential, only the agency has access to them
* itinerary printout remarks

'''Attention!''' When preparing itinerary receipts, you may add free text through RIZ element (added to PNR). For example you can enter: the name of the agent, travel tips and other information - this text will be located in the ITR after the information about the ticket price.

Example command:

<pre>RIZ YOUR PERSONAL AGENT: JOHN SMITH MR</pre>

Each remark is limited to 64 characters. There is no limit to the number of remarks. This element can be entered to the booking even after the e-ticket is issued.

By default, RIZ element applies to all passengers in the booking and will be printed in all ITR; if you want it can be assigned to some (not all) passengers using /P option (no segment assignment is possible).

It is up to the carrier to decide what information to add automatically to the remarks.

== Endorsement requirements in Sirena ==

Endorsements for orders are displayed only in the Sirena terminal.

'''Attention!''' Endorsements cannot be added to the itinerary receipt.

== See also ==
* [[Remarks]]
* [[GDS]]
* [[Travelport (Galileo)|Galileo]]
* [[Amadeus]]
* [[Sabre]]
* [[Sirena Travel]]

Electronic ticket

2021-03-14T18:05:25Z

I shaletin: Created page with "'''Electronic ticket''' (e-ticket) is a digital agreement between a passenger and an airline for the provision of air transportation services. All information about such an ag..."

'''Electronic ticket''' (e-ticket) is a digital agreement between a passenger and an airline for the provision of air transportation services. All information about such an agreement from the moment of booking goes to the carrier's database and is stored in the form of an electronic record. The [[Itinerary receipt]] serves as proof of the agreement.

== Electronic tickets processing ==

Electronic tickets processing takes place on special web-sites with access to airline resources. The option of online booking depends on [[GDS]] chosen by the portal for connection. Information about e-tickets goes to the airport computer database, so passenger data is already available at the check-in desk by the time of his arrival. The electronic ticket, like its paper predecessor, does not give the right to board, the passenger must still have a boarding pass. Now it is issued not only in the traditional way - at the check-in desk. Often the passenger can print out the ticket himself after the online registration procedure (on his own printer or at a special kiosk in the airport terminal). Thus, a person traveling with only hand luggage, for example, has the opportunity to go straight to the airport for boarding upon arrival.

== First steps ==

The Americans are pioneers in the transition to electronic ticketing. The first developments in this area date back to the mid-1980s, and the world's first electronic ticket was registered in 1990 on a United Airlines flight. The patent for the invention of the e-ticket is held by Joel Gohin (JRG Airlines, Florida), who is also recognized as a philosopher, writer, poet, painter and author of 150 songs.

In Russia the trial operation of the first electronic ticketing system started in December 2006. The airline that issued the new type of travel documents was UTair from Tyumen. The carrier used the services of domestic GDS Sirena Travel, and the first passengers were UTair employees. The registration for the UTair flight UT464 Tyumen - Moscow was held on December 4 2006 at the Roschino airport. Major Russian airlines Aeroflot, Transaero and S7 were waiting for the spring when the bureaucratic machine gave the e-ticket an official pass into the world of air transportation.

The emergence of e-ticketing was predetermined by the creation of [[GDS]], which shifted the main booking functions into numerical mode. With the transition to the system of electronic ticketing, air carriers received benefits in the form of:
* ease of storage and use of information as a result of eliminating paper forms
* elimination of costs for paper and the creation of systems of protection against fraud
* elimination of costs associated with automated ticket printing and delivery to the point of sale
* simplifying the process of concluding a contract of carriage with a passenger

With the proliferation of the electronic method of making deals for air transportation, the passenger has been able to:
* plan their own travel without having to go to the airline office or ticket office
* to see complete information about flights, comparing prices and flight conditions
* to spend only a few seconds for registration of the ticket, receiving confirmation by e-mail
* not to think about losing or getting theft the ticket
* exchange or refund the ticket online or by phone, if necessary
* letting someone else handle the purchase of the ticket

IATA members changed over to electronic ticketing on June 1, 2008.

== Websky e-ticketing module ==

'''The module has the following features:'''

* E-ticketing on flights for which ET mode is available.
* The administrative part of the module allows you to enter restrictions on the checkout with respect to the creation date, departure date and airlines.
* In the administrative part the '''Airline commissions''' reference book is available, which allows you to automate the entry of the element '''airline commission''' into the ticket mask.
* Information about the issued tickets is stored in the "Orders" database, which allows you to retrieve the necessary information in xml formats.

== E-ticket in Websky settings ==

To configure booking of only e-tickets in Websky you can use the '''Ticket type in search results''' option in the section: '''Avia tickets → Search → Search restrictions'''. It allows you to filter out from the search results the flights with the absence of the e-ticket attribute in the supplier's response (or if there is no clear indication that the ticket is e-ticket).

Nevertheless, there may be situations when an error like: "Segments cannot be combined with e-ticket and paper ticket (PT NOT COMBINABLE WITH ET)". This means that one of the segments does not support an e-ticket.

Possible reasons for the error:
* You have the "Ticket Type in Search Results" option set to: "Show routes with any ticket type". In this case, you need to change the setting.
* The settings are correct, but your requisites on the provider side are incorrectly configured. In this case, you need to contact your Galileo sales agent to update your settings and get further instructions.

If all these actions did not help and the error still occurs, you should contact Websky technical support and describe the problem in detail.

== Terms and their meanings ==

{| collspadding="10" border="1" class="wikitable"
! Term !! Meaning
|-
! Stock
| The available SAFs (strictly accountable forms) for issuing a ticket.
|-
! Ticketing
| Ticketing procedure.
|-
! Itinerary receipt
| A document emulating [[ticket]]. It contains data about passengers, fares, taxes, flights, route, electronic ticket number. [[Itinerary receipt]] is a document of an arbitrary type, but with a set of minimum data.
|-
! Validating carrier
| Carrier stocks of which are used for issuing of tickets for this carriage.
|-
! Electronic ticket
| A non-documentary form of ticket in which an [[itinerary receipt]] is issued in a prescribed form and the passenger is accepted for carriage on the basis of his/her civil documents.
|-
! Ticket mask (PQ)
| Data associated with a PNR (named passenger record or reservation file) that reflects fares, fees, commission, ticket number, etc.
|-
! Transmission record (Conjunction, Endorcement)
| An entry in the ticket specifying a series of information (e.g. Non Ref). Conjunction entries are divided into standard and non-standard. Standard ones are taken from PQ, non-standard ones from applications, but must match the format of the data entry in the transfer record.
|-
! STN (Stock control number)
| Ticket number in the stock.
|-
! TGTN (Ticketing generated ticket number).
| Ticket number assigned at the time of ticketing.
|-
! Prefix of the airline ticket
| Prefix of the validating carrier.
|-
! Interline
| The ability to issue one carrier's carriage on another carrier's letterhead.
|-
! APIS (Advanced Passenger Information System)
| APIS (Advanced Passenger Information System) is a system of additional information about passengers (required by several countries and must be shown on the ticket).
|}

== See also ==
* [[Ticketing]]
* [[GDS]]
* [[IATA]]
* [[PNR]]
* [[Comission]]
* [[Ticket’s mask]]
* [[Ticketing#Terms of e-ticket issue|Terms of e-ticket issue]]

== Useful links ==
* [http://www.tch.ru/doc/72 TCH e-ticket]

Ticket

2021-03-14T17:13:47Z

I shaletin: Created page with "'''Ticket''' is a personal document of standard pattern, confirming the fact of transportation purchase and thus securing the passenger's right to use a paid service - travel..."

'''Ticket''' is a personal document of standard pattern, confirming the fact of transportation purchase and thus securing the passenger's right to use a paid service - travel by any means of transport.

== Airline tickets ==

Air tickets are issued by agents or the carrier himself. In modern practice, two types of tickets are used:
* Paper;
* Electronic.

Electronic tickets are increasingly replacing paper tickets.

A paper ticket is a set of several documents stapled together in the form of a book. This set includes: control coupon, report coupon, flight coupons, passenger coupon, insert.

=== Information provided on the airline ticket: ===
* Passenger's name, surname, patronymic;
* Information about the airline company performing the flight;
* Information about the agency which made the ticket;
* Flight data: number, departure and arrival date, booking class, price.

== Functionality of Air Ticket Providers ==

{| width="100%" border="1" class="wikitable"
|- bgcolor="#cccccc"
! class="col0" | Description
! class="col1" | Galileo
! class="col2" | Sabre
! class="col3" | Sirena
! class="col4" | Amadeus
! class="col5" | Avianova
|- class="row1"
| class="col0" | Maximum number of simultaneously open sessions
| class="col1" | not limited
| class="col2" | 50 standard, extensions of 25 sessions
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row2"
| class="col0" | Possibility of booking and ticketing via BSP
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row3"
| class="col0" | Returnable fare types
| class="col1" | Public, Nego
| class="col2" | Public, Nego
| class="col3" | Public
| class="col4" |
| class="col5" |
|- class="row4"
| class="col0" | Content through WS
| class="col1" | BSP, TCH (partially)
| class="col2" | BSP
| class="col3" | TCH
| class="col4" | BSP
| class="col5" | Own
|- class="row5"
| class="col0" | Possibility to search by neighboring dates
| class="col1" | -
| class="col2" | +-1, 3 days
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row6"
| class="col0" | Possibility to search by neighboring airports
| class="col1" | -
| class="col2" | up to 160 km
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row7"
| class="col0" | Possibility to search with a price limit
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row8"
| class="col0" | Passengers List support
| class="col1" |
| class="col2" |
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row9"
| class="col0" | Returning the Refundable attribute in search results
| class="col1" |
| class="col2" | BFM
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row10"
| class="col0" | Returning the e-ticket attribute in search results
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row11"
| class="col0" | Returning the ticketing deadline in search results
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row12"
| class="col0" | Maximum number of segments in a complex route
| class="col1" | 8
| class="col2" |
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row13"
| class="col0" | Validating carrier in search results
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row14"
| class="col0" | Checking interlines in the output
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row15"
| class="col0" | Cancellation through the application
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row16"
| class="col0" | VOID through application
| class="col1" |
| class="col2" |
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row17"
| class="col0" | SSR DOCU/DOCO/APIS/FOID
| class="col1" |
| class="col2" |
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row18"
| class="col0" | SSR Seat map
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row19"
| class="col0" | SSR Meal
| class="col1" |
| class="col2" |
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row20"
| class="col0" | SSR Baby coat
| class="col1" | -
| class="col2" | -
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row21"
| class="col0" | Booking INS Infant seat
| class="col1" | +
| class="col2" | +
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row22"
| class="col0" | Booking Military, Students
| class="col1" | -
| class="col2" | -
| class="col3" |
| class="col4" |
| class="col5" |
|- class="row23"
| class="col0" | Maximum number of passengers of all types in the search request
| class="col1" | 9
| class="col2" | 32
| class="col3" | 9
| class="col4" | -
| class="col5" | -
|- class="row24"
| class="col0" | Number of passengers of the same type in the request
| class="col1" | 9
| class="col2" | 8
| class="col3" | 9
| class="col4" | -
| class="col5" | -
|}

== See also ==
* [[Electronic ticket]]
* [[Ticketing]]
* [[Ticket printer]]
* [[Airline]]
* [[Agency]]
* [[Ticket operations]]
* [[Ticket’s mask]]
* [[Itinerary receipt]]

ATSS (Air Transportation Settlement Service)

2021-03-14T17:02:47Z

I shaletin: /* List of ATSS participant airlines in the Galileo - TCH project */

'''ATSS''' (Air Transportation Settlement Service) is an aggregation of market representatives established to standardize the sale of passenger air transportation by accredited agencies and to ensure full, timely settlement of transactions with airlines. The executive governing body of the ATSS is the [[Transport Clearing House (TCH)]].
The main members of the system are air carriers officially registered and operating scheduled flights. The positive side of such membership is business expansion due to the increase of distribution network and reduction of financial risks under conditions of transparent reporting. First of all ATSS activity is focused on protecting the interests of air carriers, but accredited agencies, which have entered into standard agreements with the Transport Clearing House, can also become members of the system.

The history of ATSS began in late 1991, when at a conference with the participation of airlines, agencies and representatives of science industry, the concept with the basic principles of the organization of the settlement was adopted. Currently ATSS is at the stage of transition to large-scale implementation of electronic technologies in the processes of ticketing and interaction between the system participants.

== ATSS objectives: ==

* Simplification of air transportation sales procedures.
* Control over cash flow from accredited agencies to airlines.
* Reduction of airlines' expenses for the maintenance of their own air transportation sales networks.
* Reducing the terms of settlements between airlines and their counterpart companies.
* Informing airlines about the availability and expenditures of revenue.
* Reducing risks of revenue losses due to financial insolvency of Mutual Settlement System participants.

== ATSS statistics==

As of November 3, 2011, the Air Transportation Settlement System has:

* 103 scheduled airlines.
* 322 accredited carriage sales agencies.
* more than 7,100 accredited points of sale.
* over 20,800 sales cashiers (operators).
* more than 16,900 terminals of accredited airline distribution reservation system.
* 28 training centers are accredited, including their branches.
* 6 training centers are accredited.
* 17 accredited ABS owners/operators.

== List of ATSS participant airlines in the Galileo - TCH project ==

List of ATSS member airlines available for sale on the NSAW-TCH SPD
in ABS Galileo (as of 12/27/12):

1. 6H ISRAIR AIRLINES AND TOURISM LTD<br>
2. 7W "ROSA VETROV AVIATION COMPANY" LLC<br>
3. 9U/9U STATE ENTERPRISE "AIR MOLDOVA"<br>
4. A3 AEGEAN AIRLINE S.A.<br>
5. AB "AV AIR BERLIN"<br>
6. BT "AIR BALTIC CORPORATION"<br>
7. HG NIKI LUFTFAHRT<br>
8. HR HAHN AIR<br>
9. J2 AZERBAIJAN XABA YOLLARY<br>
10. KC JSC "AIR ASTANA"<br>
11. LY "EL AL ISRAEL AIRLINES"<br>
12. MU CHINA'S EAST AIRLINES<br>
13. B2 "NATIONAL AIR COMPANY "BELAVIA"<br>
14. DD/XF OJSC "VLADIVOSTOK AVIA"<br>
15. GG/A9 "GEORGIAN AIRWAYS" LLC <br>
16. Z6/Z6 OJSC "DNEPRAVIA"<br>
17. LA/YC YAMAL AIRPORT COMPANY <br>
18. HH/NN LLC "VIM-AVIA" <br>
19. PL/FV OJSC "AIRLINE "RUSSIA"<br>
20. PS/PS of PJSC "AVIATION COMPANY "INTERNATIONAL AIRLINES OF UKRAINE"<br>
21. P2/R2 OJSC "ORENBURG AIRLINES"<br>
22. U6/U6 "URAL AIRLINES"<br>
23. U8/U8 "ARMAVIA" LLC <br>
24. U9/U9 "TATARSTAN" AVIATION COMPANY, OJSC <br>
25. UU/VV ZAO AVIATION COMPANY "AEROSVIT"<br>
26. HI/HY NATIONAL AIR COMPANY "UZBEKISTON XABO YULLARY"<br>
27. UT/UT OJSC "UTAIR AVIATION COMPANY"<br>
28. YUK/GW OJSC "KUBANI AIRLINES"<br>
29. EY ETD 607 ETIHAD AIRWAYS

== See also ==
*[[Transport Clearing House (TCH)]]
*[[Travelport (Galileo)|Galileo]]
*[[Airline]]
*[[Ticket]]

== Useful links: ==

*[https://www.tch.ru/ru-ru/ATSS/Pages/Aim-and-purpose.aspx The ATSS page on the TCH website]

ATSS (Air Transportation Settlement Service)

2021-03-14T17:02:34Z

I shaletin: Created page with "'''ATSS''' (Air Transportation Settlement Service) is an aggregation of market representatives established to standardize the sale of passenger air transportation by accredite..."

'''ATSS''' (Air Transportation Settlement Service) is an aggregation of market representatives established to standardize the sale of passenger air transportation by accredited agencies and to ensure full, timely settlement of transactions with airlines. The executive governing body of the ATSS is the [[Transport Clearing House (TCH)]].
The main members of the system are air carriers officially registered and operating scheduled flights. The positive side of such membership is business expansion due to the increase of distribution network and reduction of financial risks under conditions of transparent reporting. First of all ATSS activity is focused on protecting the interests of air carriers, but accredited agencies, which have entered into standard agreements with the Transport Clearing House, can also become members of the system.

The history of ATSS began in late 1991, when at a conference with the participation of airlines, agencies and representatives of science industry, the concept with the basic principles of the organization of the settlement was adopted. Currently ATSS is at the stage of transition to large-scale implementation of electronic technologies in the processes of ticketing and interaction between the system participants.

== ATSS objectives: ==

* Simplification of air transportation sales procedures.
* Control over cash flow from accredited agencies to airlines.
* Reduction of airlines' expenses for the maintenance of their own air transportation sales networks.
* Reducing the terms of settlements between airlines and their counterpart companies.
* Informing airlines about the availability and expenditures of revenue.
* Reducing risks of revenue losses due to financial insolvency of Mutual Settlement System participants.

== ATSS statistics==

As of November 3, 2011, the Air Transportation Settlement System has:

* 103 scheduled airlines.
* 322 accredited carriage sales agencies.
* more than 7,100 accredited points of sale.
* over 20,800 sales cashiers (operators).
* more than 16,900 terminals of accredited airline distribution reservation system.
* 28 training centers are accredited, including their branches.
* 6 training centers are accredited.
* 17 accredited ABS owners/operators.

== List of ATSS participant airlines in the Galileo - TCH project ==

List of ATSS member airlines available for sale on the NSAW-TCH SPD
in ABS Galileo (as of 12/27/12):

1. 6H ISRAIR AIRLINES AND TOURISM LTD<br>
2. 7W "ROSA VETROV AVIATION COMPANY" LLC<br>
3. 9U/9U STATE ENTERPRISE "AIR MOLDOVA"<br>
4. A3 AEGEAN AIRLINE S.A.<br>
5. AB "AV AIR BERLIN"<br>
6. BT "AIR BALTIC CORPORATION"<br>
7. HG NIKI LUFTFAHRT<br>
8. HR HAHN AIR<br>
9. J2 AZERBAIJAN XABA YOLLARY<br>
10. KC JSC "AIR ASTANA"<br>
11. LY "EL AL ISRAEL AIRLINES"<br>
12. MU CHINA'S EAST AIRLINES<br> <br>
13. B2 "NATIONAL AIR COMPANY "BELAVIA"<br>
14. DD/XF OJSC "VLADIVOSTOK AVIA"<br>
15. GG/A9 "GEORGIAN AIRWAYS" LLC <br>
16. Z6/Z6 OJSC "DNEPRAVIA"<br>
17. LA/YC YAMAL AIRPORT COMPANY <br>
18. HH/NN LLC "VIM-AVIA" <br>
19. PL/FV OJSC "AIRLINE "RUSSIA"<br>
20. PS/PS of PJSC "AVIATION COMPANY "INTERNATIONAL AIRLINES OF UKRAINE"<br>
21. P2/R2 OJSC "ORENBURG AIRLINES"<br>
22. U6/U6 "URAL AIRLINES"<br>
23. U8/U8 "ARMAVIA" LLC <br>
24. U9/U9 "TATARSTAN" AVIATION COMPANY, OJSC <br>
25. UU/VV ZAO AVIATION COMPANY "AEROSVIT"<br>
26. HI/HY NATIONAL AIR COMPANY "UZBEKISTON XABO YULLARY"<br>
27. UT/UT OJSC "UTAIR AVIATION COMPANY"<br>
28. YUK/GW OJSC "KUBANI AIRLINES"<br>
29. EY ETD 607 ETIHAD AIRWAYS

== See also ==
*[[Transport Clearing House (TCH)]]
*[[Travelport (Galileo)|Galileo]]
*[[Airline]]
*[[Ticket]]

== Useful links: ==

*[https://www.tch.ru/ru-ru/ATSS/Pages/Aim-and-purpose.aspx The ATSS page on the TCH website]

Ticketing Web Service

2021-02-27T20:29:37Z

I shaletin:

'''Attention!''' The system implements an improved API-project "Nemo Connect", we strongly recommend to connect using the scheme described in the documentation at [https://docs.nemo.travel/en link].

== Information ==

The agency ticketing API allows you to determine the validating carrier and the commission value from the airline for the booking, and to run the ticketing procedure.

As a rule for ticketing it is enough to have a "Paid" status. If the option '''For successful bookings do processing: automatically after changing the status to ''Paid" ''' from the '''For technical support → Outdated settings → Booking settings''' section is activated, the ticket will be automatically issued after the payment. However, this is a prerequisite only for users, it is possible to get a ticket that does not require payment, for this you need to have API user rights. For example, API account must be created for the agency manager.

Additionally the '''Allowed IP addresses''' setting is implemented in the section '''System settings → Integration → Nemo 1.0 (SOAP API)''' , defining a range of IP addresses for additional protection of accounts under which a ticket is issued without paying or fixing the payment. IP-addresses have the following acceptable format: <syntaxhighlight lang="text" enclose="none" style="font-size: 1em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">125.125.25.5/8</syntaxhighlight>, that is possible to specify with the subnet mask.

'''Attention!''' When the Websky system does not have the booking locator data in the airline system, the ticketing operation is not possible. That's why in response to Ticketing request you may get an error message like "The requested operation is not allowed for this object".
If GDS doesn't have data about a booking locator in the airline's system, an empty value will be returned in the response to the BookFlight request in the Segments.Segment.SupplierCode parameter. In this case you need to send an [[Additional_requests_API_airline tickets#.D0.97.D0.B0.D0.BF.D1.80.D0.BE.D1.81_.D0.BD.D0.B0_.D0.BE.D0.B1.D0.BD.D0.BE.D0.B2.D0.BB.D0. B5.D0.BD.D0.B8.D0.B5_.D0.B7.D0.B0.D0.BA.D0.B0.D0.B7.D0.B0 | UpdateBook]] request several times until GDS side receives information about booking locator in the airline system. Websky system will then receive this value from GDS. The ticketing request can only be sent after a non-zero value is received in the Segments.Segment.SupplierCode parameter in the response from the Websky Agent API.

In Nemo Connect, additional settings have been added to the agent service (the interface to the booking server) for ticketing. The new version of the API allows you to:

* report the VC (validating carrier) for a given combination
* inform the commission for the given combination;
* report the endorsements for the given combination;
* accept ticketing requests;
* check the availability of the booking in the GDS;
* synchronize the booking;
* perform ticketing;
* transmit additional information in the remarks;
* perform voiding for tickets.

== General format of ticketing request/response ==
This request is launched after the payment for the order, it can be launched either manually - by a user who has rights for it - or automatically. It is possible to make a ticketing for unpaid order via Websky only from certain IP addresses, the list of which is configured in the settings section described above. When the ticketing request is triggered, the order update process is also launched, during which the price and other parameters of the order are checked, as well as its relevance is checked. Orders with an expired time limit cannot be ticketed.

WSDL: http://CLIENT_DOMAIN/nemoflights/wsdl.php?for=Ticketing

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Request ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DTicketing">
<soapenv:Header/>
<soapenv:Body>
<ver:Ticketing>
<RequestBin>
<Request>
<Ticketing>
<BookID>?</BookID>

<ValCompany>?</ValCompany>

<Comission Amount="?" Percent="?" CurrencyCode="?"/>




<PassengerFops>

<PassengerFop>
<PassengerId>?</PassengerId>

<Fops>

<Fop>
<Type>?</Type>

<Money Currency="?">?</Money>


<VendorCode>?</VendorCode>

<Number>?</Number>

<ExpireDate>?</ExpireDate>

<ManualApprovalCode>?</ManualApprovalCode>

</Fop>
</Fops>
</PassengerFop>
</PassengerFops>
<DataItems>

<DataItem>
<Type>Remark</Type>

<Remark>
<Type>?</Type>

<Text>?</Text>

</Remark>
</DataItem>
</DataItems>
</Ticketing>
</Request>
<Source>
<ClientId>?</ClientId>

<APIKey>?</APIKey>
<! --APIKey - the secret access key to Websky API. You can see / add it in the section
"System Settings → Integration → Nemo 1.0 (SOAP API).-->
<Language>?</Language>

<Currency>?</Currency>

</Source>
</RequestBin>
</ver:Ticketing>
</soapenv:Body>
</soapenv:Envelope>
</syntaxhighlight>
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">

==== Response ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DTicketing" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:TicketingResponse>
<ResponseBin>
<Response>
<Ticketing ID="?" Status="?" Code="?">



<QueryPlace xsi:nil="true"/>

<Flight FlightId="?">

<WebService>?</WebService>

<ValCompany>?</ValCompany>

<URL>?</URL>

<Segments>
<Segment SegNum="?" SegGroupNum="?">


<SupplierCode>?</SupplierCode>

<DepAirp CodeType="IATA">?</DepAirp>

<DepTerminal>?</DepTerminal>

<ArrAirp CodeType="IATA">?</ArrAirp>

<ArrTerminal>?</ArrTerminal>

<OpAirline>?</OpAirline>

<MarkAirline>?</MarkAirline>

<MarkAirlineName>?</MarkAirlineName>

<FlightNumber>?</FlightNumber>

<AircraftName>?</AircraftName>

<AircraftType>?</AircraftType>

<DepDateTime>?</DepDateTime>

<ArrDateTime>?</ArrDateTime>

<StopNum>?</StopNum>

<StopPoints>

<StopPoint>
<AirportCode>?</AirportCode>

<UTC>?</UTC>

<ArrDateTime>?</ArrDateTime>

<DepDateTime>?</DepDateTime>

</StopPoint>
</StopPoints>
<BookingCodes>
<BookingCode ClassType="?">

<BookingCode>?</BookingCode>

</BookingCode>
</BookingCodes>
<FlightTime>?</FlightTime>

<TimeZone Departure="?" Arrival="?"/>


<ETicket>?</ETicket>

<isCharter>?</isCharter>

<BaggageAllowances>

<BaggageAllowance>
<PassengerType>?</PassengerType>

<Value>?</Value>

<Measurement>?</Measurement>

</BaggageAllowance>
</BaggageAllowances>
</Segment>
</Segments>
<PricingInfo Refundable="?">

<PassengerFare Type="?" Quantity="?">


<BaseFare Currency="?" Amount="?"/>

<EquiveFare Currency="?" Amount="?"/>

<TotalFare Currency="?" Amount="?"/>

<Taxes>
<Tax CurCode="?" TaxCode="?" Amount="?"/>

</Taxes>
<Tariffs>
<Tariff Code="?" SegNum="?"/>

</Tariffs>
<FareCalc>?</FareCalc>
<!-FareCalc - price calculation line-->
<LastTicketDateTime>?</LastTicketDateTime>

<TotalPrice Currency="?">?</TotalPrice

</Flight>
<Agency Name="?">
<!-Name - agency name-->
<Telephone Type="?">


<PhoneNumber>?


<CountryAccessCode>?
<!-CountryAccessCode - country code-->

<AreaCityCode>?

</Telephone>
<Address City="?" State="?" StreetAddress="?" PostalCode="?" CountryCode="?"/>
<!-City - city-->
<!-State - state-->


<!-CountryCode - country code (RU, UA etc)-->
</Agency>
<ItinReceipts Encoding="?" Format="?">

<FareStored xsi:nil="true"/>
<PaymentTransactions>
<Transaction>
<Id>?</Id>

<Status>?</Status>

<GatewayName>?</GatewayName>
<!-GatewayName - name of the payment gateway-->
<MoneyPaid Currency="?">?</MoneyPaid>

<!-Currency - currency-->
<PaymentDateTime>?</PaymentDateTime>
<!-PaymentDateTime - payment date and time-->
<CreateDateTime>?</CreateDateTime>

<Description/>
</Transaction>
</PaymentTransactions>
<PaymentStatus>?</PaymentStatus>
<!-PaymentStatus - payment status:
not_paid - not paid
partly_paid - paid, partly
fully_paid - paid in full-->
<Travellers>

<Traveller Type="?" IsContact="?" LinkedTo="?" Num="?" TravellerId="?">





<Meal>?</Meal>

<PersonalInfo DateOfBirth="?" Nationality="?" Gender="?">
<!-DateOfBirth - date of birth in DD.MM.YYYY format (for example 12/31/2000)-->


<FirstName>?</FirstName>

<LastName>?</LastName>


<MiddleName>?</MiddleName>

</PersonalInfo>
<LoyaltyCard OpCode="?" Number="?"/>


<ContactInfo>

<EmailID>?</EmailID>






<Ticket TicketNum="?">

<VisaInfo Num="?" IssueCountry="?" IssuePlace="?" BirthCountry="?" BirthCity="?" IssueDate="?"/>






<ArrAddress City="?" State="?" StreetAddress="?" PostalCode="?" CountryCode="?"/>
<!-City - city-->


<!-PostalCode - postal code-->
<!-CountryCode - country code-->
<PreferedPlace SmokingAllowed="?" Location="?" RowNumber="?" PlaceNumber="?" SegNumber="?"/>




<!-PlaceNumber - seat number-->

<DocStringFormats>

<DocStringFormat>?</DocStringFormat>

</DocStringFormats>
</Traveller>
</Travellers>
<AutoCancelDate> </AutoCancelDate>

<TimeLimits>
<TicketingTimeLimit>?</TicketingTimeLimit>

<PriceTimeLimit>?</PriceTimeLimit>

<AdvancedPurchaseTimeLimit>?</AdvancedPurchaseTimeLimit>

<AgencyTimeLimit>?</AgencyTimeLimit>
<!-AgencyTimeLimit - The time limit of the settings in the format YYYYY-MM-DDTCH:MM:SS-->
</TimeLimits>
</Ticketing>
<Requisites/>
<RequestType xsi:nil="true"/>
<UserID xsi:nil="true"/>
<Error Code="?">Error message</Error>
</Response>
</ResponseBin>
</ns1:TicketingResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</syntaxhighlight>
</div>
</div>

== General format of the request / response of the voiding==
This request is launched after the ticket is issued, if it is necessary to cancel it.

WSDL: http://CLIENT_DOMAIN/nemoflights/wsdl.php?for=VoidTicket

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Request ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DVoidTicket">
<soapenv:Header/>
<soapenv:Body>
<ver:VoidTicket>
<RequestBin>
<Request>
<VoidTicket>
<BookID>?</BookID>

</VoidTicket>
</Request>
<Source>
<ClientId>?</ClientId>

<Language>?</Language>

<Currency>?</Currency>

</Source>
</RequestBin>
</ver:VoidTicket>
</soapenv:Body>
</soapenv:Envelope>
</syntaxhighlight>
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Response====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DVoidTicket" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:VoidTicketResponse>
<ResponseBin>
<Response>
<VoidTicket BookID="?">

<Result Success="?"/>

</VoidTicket>
<Requisites/>
<RequestType xsi:nil="true"/>
<UserID xsi:nil="true"/>
<Error Code="?">Error message</Error>
</Response>
</ResponseBin>
</ns1:VoidTicketResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</syntaxhighlight>
</div>
</div>

== See also ==

* [[Air Tickets Agency API]]
* [[Booking]]
* [[Additional Air Tickets API requests]]

Ticketing Web Service

2021-02-27T20:28:56Z

I shaletin: Created page with "'''Attention!''' The system implements an improved API-project "Nemo Connect", we strongly recommend to connect using the scheme described in the documentation at [http://docs..."

'''Attention!''' The system implements an improved API-project "Nemo Connect", we strongly recommend to connect using the scheme described in the documentation at [http://docs.nemo.travel/ link].

== Information ==

The agency ticketing API allows you to determine the validating carrier and the commission value from the airline for the booking, and to run the ticketing procedure.

As a rule for ticketing it is enough to have a "Paid" status. If the option '''For successful bookings do processing: automatically after changing the status to ''Paid" ''' from the '''For technical support → Outdated settings → Booking settings''' section is activated, the ticket will be automatically issued after the payment. However, this is a prerequisite only for users, it is possible to get a ticket that does not require payment, for this you need to have API user rights. For example, API account must be created for the agency manager.

Additionally the '''Allowed IP addresses''' setting is implemented in the section '''System settings → Integration → Nemo 1.0 (SOAP API)''' , defining a range of IP addresses for additional protection of accounts under which a ticket is issued without paying or fixing the payment. IP-addresses have the following acceptable format: <syntaxhighlight lang="text" enclose="none" style="font-size: 1em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">125.125.25.5/8</syntaxhighlight>, that is possible to specify with the subnet mask.

'''Attention!''' When the Websky system does not have the booking locator data in the airline system, the ticketing operation is not possible. That's why in response to Ticketing request you may get an error message like "The requested operation is not allowed for this object".
If GDS doesn't have data about a booking locator in the airline's system, an empty value will be returned in the response to the BookFlight request in the Segments.Segment.SupplierCode parameter. In this case you need to send an [[Additional_requests_API_airline tickets#.D0.97.D0.B0.D0.BF.D1.80.D0.BE.D1.81_.D0.BD.D0.B0_.D0.BE.D0.B1.D0.BD.D0.BE.D0.B2.D0.BB.D0. B5.D0.BD.D0.B8.D0.B5_.D0.B7.D0.B0.D0.BA.D0.B0.D0.B7.D0.B0 | UpdateBook]] request several times until GDS side receives information about booking locator in the airline system. Websky system will then receive this value from GDS. The ticketing request can only be sent after a non-zero value is received in the Segments.Segment.SupplierCode parameter in the response from the Websky Agent API.

In Nemo Connect, additional settings have been added to the agent service (the interface to the booking server) for ticketing. The new version of the API allows you to:

* report the VC (validating carrier) for a given combination
* inform the commission for the given combination;
* report the endorsements for the given combination;
* accept ticketing requests;
* check the availability of the booking in the GDS;
* synchronize the booking;
* perform ticketing;
* transmit additional information in the remarks;
* perform voiding for tickets.

== General format of ticketing request/response ==
This request is launched after the payment for the order, it can be launched either manually - by a user who has rights for it - or automatically. It is possible to make a ticketing for unpaid order via Websky only from certain IP addresses, the list of which is configured in the settings section described above. When the ticketing request is triggered, the order update process is also launched, during which the price and other parameters of the order are checked, as well as its relevance is checked. Orders with an expired time limit cannot be ticketed.

WSDL: http://CLIENT_DOMAIN/nemoflights/wsdl.php?for=Ticketing

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Request ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DTicketing">
<soapenv:Header/>
<soapenv:Body>
<ver:Ticketing>
<RequestBin>
<Request>
<Ticketing>
<BookID>?</BookID>

<ValCompany>?</ValCompany>

<Comission Amount="?" Percent="?" CurrencyCode="?"/>




<PassengerFops>

<PassengerFop>
<PassengerId>?</PassengerId>

<Fops>

<Fop>
<Type>?</Type>

<Money Currency="?">?</Money>


<VendorCode>?</VendorCode>

<Number>?</Number>

<ExpireDate>?</ExpireDate>

<ManualApprovalCode>?</ManualApprovalCode>

</Fop>
</Fops>
</PassengerFop>
</PassengerFops>
<DataItems>

<DataItem>
<Type>Remark</Type>

<Remark>
<Type>?</Type>

<Text>?</Text>

</Remark>
</DataItem>
</DataItems>
</Ticketing>
</Request>
<Source>
<ClientId>?</ClientId>

<APIKey>?</APIKey>
<! --APIKey - the secret access key to Websky API. You can see / add it in the section
"System Settings → Integration → Nemo 1.0 (SOAP API).-->
<Language>?</Language>

<Currency>?</Currency>

</Source>
</RequestBin>
</ver:Ticketing>
</soapenv:Body>
</soapenv:Envelope>
</syntaxhighlight>
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">

==== Response ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DTicketing" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:TicketingResponse>
<ResponseBin>
<Response>
<Ticketing ID="?" Status="?" Code="?">



<QueryPlace xsi:nil="true"/>

<Flight FlightId="?">

<WebService>?</WebService>

<ValCompany>?</ValCompany>

<URL>?</URL>

<Segments>
<Segment SegNum="?" SegGroupNum="?">


<SupplierCode>?</SupplierCode>

<DepAirp CodeType="IATA">?</DepAirp>

<DepTerminal>?</DepTerminal>

<ArrAirp CodeType="IATA">?</ArrAirp>

<ArrTerminal>?</ArrTerminal>

<OpAirline>?</OpAirline>

<MarkAirline>?</MarkAirline>

<MarkAirlineName>?</MarkAirlineName>

<FlightNumber>?</FlightNumber>

<AircraftName>?</AircraftName>

<AircraftType>?</AircraftType>

<DepDateTime>?</DepDateTime>

<ArrDateTime>?</ArrDateTime>

<StopNum>?</StopNum>

<StopPoints>

<StopPoint>
<AirportCode>?</AirportCode>

<UTC>?</UTC>

<ArrDateTime>?</ArrDateTime>

<DepDateTime>?</DepDateTime>

</StopPoint>
</StopPoints>
<BookingCodes>
<BookingCode ClassType="?">

<BookingCode>?</BookingCode>

</BookingCode>
</BookingCodes>
<FlightTime>?</FlightTime>

<TimeZone Departure="?" Arrival="?"/>


<ETicket>?</ETicket>

<isCharter>?</isCharter>

<BaggageAllowances>

<BaggageAllowance>
<PassengerType>?</PassengerType>

<Value>?</Value>

<Measurement>?</Measurement>

</BaggageAllowance>
</BaggageAllowances>
</Segment>
</Segments>
<PricingInfo Refundable="?">

<PassengerFare Type="?" Quantity="?">


<BaseFare Currency="?" Amount="?"/>

<EquiveFare Currency="?" Amount="?"/>

<TotalFare Currency="?" Amount="?"/>

<Taxes>
<Tax CurCode="?" TaxCode="?" Amount="?"/>

</Taxes>
<Tariffs>
<Tariff Code="?" SegNum="?"/>

</Tariffs>
<FareCalc>?</FareCalc>
<!-FareCalc - price calculation line-->
<LastTicketDateTime>?</LastTicketDateTime>

<TotalPrice Currency="?">?</TotalPrice

</Flight>
<Agency Name="?">
<!-Name - agency name-->
<Telephone Type="?">


<PhoneNumber>?


<CountryAccessCode>?
<!-CountryAccessCode - country code-->

<AreaCityCode>?

</Telephone>
<Address City="?" State="?" StreetAddress="?" PostalCode="?" CountryCode="?"/>
<!-City - city-->
<!-State - state-->


<!-CountryCode - country code (RU, UA etc)-->
</Agency>
<ItinReceipts Encoding="?" Format="?">

<FareStored xsi:nil="true"/>
<PaymentTransactions>
<Transaction>
<Id>?</Id>

<Status>?</Status>

<GatewayName>?</GatewayName>
<!-GatewayName - name of the payment gateway-->
<MoneyPaid Currency="?">?</MoneyPaid>

<!-Currency - currency-->
<PaymentDateTime>?</PaymentDateTime>
<!-PaymentDateTime - payment date and time-->
<CreateDateTime>?</CreateDateTime>

<Description/>
</Transaction>
</PaymentTransactions>
<PaymentStatus>?</PaymentStatus>
<!-PaymentStatus - payment status:
not_paid - not paid
partly_paid - paid, partly
fully_paid - paid in full-->
<Travellers>

<Traveller Type="?" IsContact="?" LinkedTo="?" Num="?" TravellerId="?">





<Meal>?</Meal>

<PersonalInfo DateOfBirth="?" Nationality="?" Gender="?">
<!-DateOfBirth - date of birth in DD.MM.YYYY format (for example 12/31/2000)-->


<FirstName>?</FirstName>

<LastName>?</LastName>


<MiddleName>?</MiddleName>

</PersonalInfo>
<LoyaltyCard OpCode="?" Number="?"/>


<ContactInfo>

<EmailID>?</EmailID>






<Ticket TicketNum="?">

<VisaInfo Num="?" IssueCountry="?" IssuePlace="?" BirthCountry="?" BirthCity="?" IssueDate="?"/>






<ArrAddress City="?" State="?" StreetAddress="?" PostalCode="?" CountryCode="?"/>
<!-City - city-->


<!-PostalCode - postal code-->
<!-CountryCode - country code-->
<PreferedPlace SmokingAllowed="?" Location="?" RowNumber="?" PlaceNumber="?" SegNumber="?"/>




<!-PlaceNumber - seat number-->

<DocStringFormats>

<DocStringFormat>?</DocStringFormat>

</DocStringFormats>
</Traveller>
</Travellers>
<AutoCancelDate> </AutoCancelDate>

<TimeLimits>
<TicketingTimeLimit>?</TicketingTimeLimit>

<PriceTimeLimit>?</PriceTimeLimit>

<AdvancedPurchaseTimeLimit>?</AdvancedPurchaseTimeLimit>

<AgencyTimeLimit>?</AgencyTimeLimit>
<!-AgencyTimeLimit - The time limit of the settings in the format YYYYY-MM-DDTCH:MM:SS-->
</TimeLimits>
</Ticketing>
<Requisites/>
<RequestType xsi:nil="true"/>
<UserID xsi:nil="true"/>
<Error Code="?">Error message</Error>
</Response>
</ResponseBin>
</ns1:TicketingResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</syntaxhighlight>
</div>
</div>

== General format of the request / response of the voiding==
This request is launched after the ticket is issued, if it is necessary to cancel it.

WSDL: http://CLIENT_DOMAIN/nemoflights/wsdl.php?for=VoidTicket

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Request ====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DVoidTicket">
<soapenv:Header/>
<soapenv:Body>
<ver:VoidTicket>
<RequestBin>
<Request>
<VoidTicket>
<BookID>?</BookID>

</VoidTicket>
</Request>
<Source>
<ClientId>?</ClientId>

<Language>?</Language>

<Currency>?</Currency>

</Source>
</RequestBin>
</ver:VoidTicket>
</soapenv:Body>
</soapenv:Envelope>
</syntaxhighlight>
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
==== Response====
<div class="mw-collapsible-content">
<syntaxhighlight lang="xml" line enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://CLIENT_DOMAIN/nemoflights/?version%3D1.0%26for%3DVoidTicket" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:VoidTicketResponse>
<ResponseBin>
<Response>
<VoidTicket BookID="?">

<Result Success="?"/>

</VoidTicket>
<Requisites/>
<RequestType xsi:nil="true"/>
<UserID xsi:nil="true"/>
<Error Code="?">Error message</Error>
</Response>
</ResponseBin>
</ns1:VoidTicketResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</syntaxhighlight>
</div>
</div>

== See also ==

* [[Air Tickets Agency API]]
* [[Booking]]
* [[Additional Air Tickets API requests]]

Global Distribution System (GDS)

2021-02-27T08:54:07Z

I shaletin: /* See also */

The '''Global Distribution System''' (GDS) is a specialized computer reservation system (CRS) designed for [[Search (Air tickets)|search]], [[Booking|booking]] and sale of services. Initially, GDSs were developed by [[Airline|airlines]] for their own needs, but as the market developed, they spread among travel agencies, becoming an important tool for real-time sales of services. Modern GDSs have the ability to sell air and rail [[Ticket|tickets]], provide services for arranging insurance contracts, hotel bookings, car rentals, etc.

== GDS in Websky ==

Websky unifies work with various GDS and other air content providers, automates the majority of template operations, adds customizable management options and logic for working with suppliers like:
* [[Sabre|GDS Sabre]]
* [[Travelport (Galileo)|GDS Travelport (Galileo, Galileo uAPI)]]
* [[Amadeus|GDS Amadeus]]
* [[Mystifly|GDS Mystifly]]
* [[Sirena Travel|GDS Sirena Travel]]
* S7 Siberia Airlines booking system (hosted by [[SITA Gabriel]])
* [[API AviaCenter (Special fares)]]
* [[API Travelfusion]]
* [[Nemo Inventory]]

== How to connect to the GDS ==

For searching, booking and other [[agency]] operations, the agency must contract with one or more GDSs and obtain connection IDs from them.

The agency connects to the GDS through the '''Nemo Connect''' server, which unifies access to content from different airline providers and provides a single set of features for flight searches and bookings. GDS connection requisites are set and stored directly in Nemo Connect. [[User#User types in Websky|Administrator]] in Websky creates an agency account, enters the connection requisites for working with the GDS in Nemo Connect, informs the agency of the '''Login''', '''Password''', '''UserID''' for connecting to the Nemo Connect project and the numbers of [[Nemo Connect requisite packages|requisite packages]] for working with the GDS.

To connect an agency to GDS:

# Establish a contract with GDS for a list of supported services and their settings. GDS generates [[PCC]] and other identifiers and sends them to the agency.
# Pass the PCC identifier and specific GDS interaction settings (region of operation, [[currency]], GDS requests and versions, restrictions, etc.) to the Websky administrator. Based on this data in Nemo Connect, Websky staff will enter [[Nemo Connect GDS connection requisites]] and [[Nemo Connect requisite packages]]. It is assumed that at this point, Websky administrators have created an agency account and given you [[Login]], [[Password]] and [[UserId]] (agency ID number).
# Set up Websky [[GDS connection requisites in Websky#Creating Websky connection requisites|GDS connection requisites]] via the ''Nemo Connect'' connector, using the profile identifiers in Nemo Connect. You can learn about how to properly create connection requisites in [[GDS connection requisites in Websky]]
# Create a [[Websky requisite packages#Creating Websky requisite packages|requisite package in Websky]] where you select the GDS connection requisites for the search, booking and ticketing process you created in step #3.
# Select the requisite packages for searching (for the whole agency or for an individual user) in the section '''Product control → Avia tickets→ Processes→ Search process → Fine tuning'''.

== See also ==
* [[GDS connection requisites in Websky]]
* [[Websky requisite packages]]
* [[GDS connection requisites in Nemo Connect]]
* [[Nemo Connect requisite packages]]
* [[Connection requisites]]
* [[Amadeus]]
* [[Sabre]]
* [[Sirena Travel]]
* [[Travelport (Galileo)]]
* [[SITA Gabriel]]

== Useful links ==
* [http://www.amadeus.com Amadeus]
* [http://www.travelport.com/lob/gds/galileo.aspx Travelport (Galileo)]
* [http://www.sabre-holdings.com/ Sabre]
* [http://www.sirena-travel.ru/ Sirena Travel]
* [http://www.sita.aero/ru SITA Gabriel]

Global Distribution System (GDS)

2021-02-27T08:53:41Z

I shaletin: Created page with "The '''Global Distribution System''' (GDS) is a specialized computer reservation system (CRS) designed for search, booking and sale of ser..."

The '''Global Distribution System''' (GDS) is a specialized computer reservation system (CRS) designed for [[Search (Air tickets)|search]], [[Booking|booking]] and sale of services. Initially, GDSs were developed by [[Airline|airlines]] for their own needs, but as the market developed, they spread among travel agencies, becoming an important tool for real-time sales of services. Modern GDSs have the ability to sell air and rail [[Ticket|tickets]], provide services for arranging insurance contracts, hotel bookings, car rentals, etc.

== GDS in Websky ==

Websky unifies work with various GDS and other air content providers, automates the majority of template operations, adds customizable management options and logic for working with suppliers like:
* [[Sabre|GDS Sabre]]
* [[Travelport (Galileo)|GDS Travelport (Galileo, Galileo uAPI)]]
* [[Amadeus|GDS Amadeus]]
* [[Mystifly|GDS Mystifly]]
* [[Sirena Travel|GDS Sirena Travel]]
* S7 Siberia Airlines booking system (hosted by [[SITA Gabriel]])
* [[API AviaCenter (Special fares)]]
* [[API Travelfusion]]
* [[Nemo Inventory]]

== How to connect to the GDS ==

For searching, booking and other [[agency]] operations, the agency must contract with one or more GDSs and obtain connection IDs from them.

The agency connects to the GDS through the '''Nemo Connect''' server, which unifies access to content from different airline providers and provides a single set of features for flight searches and bookings. GDS connection requisites are set and stored directly in Nemo Connect. [[User#User types in Websky|Administrator]] in Websky creates an agency account, enters the connection requisites for working with the GDS in Nemo Connect, informs the agency of the '''Login''', '''Password''', '''UserID''' for connecting to the Nemo Connect project and the numbers of [[Nemo Connect requisite packages|requisite packages]] for working with the GDS.

To connect an agency to GDS:

# Establish a contract with GDS for a list of supported services and their settings. GDS generates [[PCC]] and other identifiers and sends them to the agency.
# Pass the PCC identifier and specific GDS interaction settings (region of operation, [[currency]], GDS requests and versions, restrictions, etc.) to the Websky administrator. Based on this data in Nemo Connect, Websky staff will enter [[Nemo Connect GDS connection requisites]] and [[Nemo Connect requisite packages]]. It is assumed that at this point, Websky administrators have created an agency account and given you [[Login]], [[Password]] and [[UserId]] (agency ID number).
# Set up Websky [[GDS connection requisites in Websky#Creating Websky connection requisites|GDS connection requisites]] via the ''Nemo Connect'' connector, using the profile identifiers in Nemo Connect. You can learn about how to properly create connection requisites in [[GDS connection requisites in Websky]]
# Create a [[Websky requisite packages#Creating Websky requisite packages|requisite package in Websky]] where you select the GDS connection requisites for the search, booking and ticketing process you created in step #3.
# Select the requisite packages for searching (for the whole agency or for an individual user) in the section '''Product control → Avia tickets→ Processes→ Search process → Fine tuning'''.

== See also ==
* [[GDS connection requisites in Websky]]
* [[Websky requisite packages]]
* [[GDS connection requisites in Nemo Connect]]
* [[Nemo Connect requisite packages]]
* [[Connection requisites]]
* [[Amadeus]]
* [[Sabre]]
* [[Сирена Трэвел]]
* [[Travelport (Galileo)]]
* [[SITA Gabriel]]

== Useful links ==
* [http://www.amadeus.com Amadeus]
* [http://www.travelport.com/lob/gds/galileo.aspx Travelport (Galileo)]
* [http://www.sabre-holdings.com/ Sabre]
* [http://www.sirena-travel.ru/ Sirena Travel]
* [http://www.sita.aero/ru SITA Gabriel]

Airline

2021-02-26T20:34:38Z

I shaletin: /* See also */

'''Airline''' is an air transportation company that provides services in passenger and cargo transportation. With both scheduled and charter flights, airlines occupy key positions in the modern transport infrastructure. Websky system uses the terms "carrier" and "air carrier" as synonyms of the concept "airline".

Two main organizations, the International Civil Aviation Organization (ICAO) and the International Air Transport Association (IATA), regulate airlines. ICAO and IATA codes are actively used in directories of airlines, cities and airports used by Websky. In most cases, transportation sales are made through [[GDS]], a kind of exchange where airlines upload data on fares and availability. However, there are carriers, especially in the segment of low-cost transportation, whose resources are not represented in the GDS and whose membership in IATA is incomplete.

Airlines can operate both independently and on the basis of partnership programs (e.g. codeshare and interline agreements), as well as alliances. The most famous alliances uniting major carriers are: SkyTeam, Oneworld and Star Alliance.

== Airline data in Websky ==

The system operates the data of passenger airlines operating scheduled flights and represented in Global Distribution Systems. Thus, the list of carriers available in Websky is limited by the possibilities of GDS chosen by the client for connection, as well as by peculiarities of sales of one or another airline within the clearing zone.

Airline in Websky is an entity with the following characteristics:
* IATA code
* ICAO code
* TAC code
* Name
* Country of Origin

The list of airlines is downloaded from the IATA and TCH (Transport Clearing House) directories. The actuality of the database is checked every six months during regular updates of the system.

The directory also contains information about the airline, which can be displayed in the form of search results (depending on client settings):
* logo
* city in which the headquarters of the airline are located
* website

The airline directory in Websky is editable and can be changed by the customer at his discretion.

'''Attention!''' When editing an airline name in the directory, only the first letter of the word (at the beginning of the name or before the space) becomes capitalized, the rest are lowercased.

== Airline information on Websky forms ==

Airline information - basically the airline IATA code and a short name - is present on all Websky forms associated with the sale of airline tickets:
* a form to view the selected flight combination
* booking confirmation form
* ticketing confirmation form
* form of itinerary receipt inquiry form

By default, the airline specific search filter is disabled in the ticket search form in the standard design, but it is possible to make it available. Activation of this filter allows to show in search results transportation options of only those airlines which have been marked by the user.

== Airline information in Websky search results ==

In the standard design theme, the airline search results form contains an airline name and logo. General data about it can be viewed by clicking on the link with the carrier name (provided that the airline data transfer to the search results form is enabled) or the logo (provided that the '''Link to airline logo on search results'' option is enabled in '''Product control → Air tickets → Processes → Search form'').

Besides the name of the airline whose [[fare]] is displayed in search results you can also specify ''[[operating carrier]]'' - the airline that actually flies the given route.

== Websky settings that can be set depending on the airlines ==

* search presets
* search lists
* checkout lists
* lists for interlines
* surcharges
* discounts
* subagent commissions
* airline commissions
* passenger data formats settings

== Airline blacklists and whitelists ==

"Black" and "white" lists of airlines are introduced in order to be able to manage the search results. For example, to show only flights of certain airlines (from the "white" list) or all airlines except for some airlines (from the "black" list). The '''Airlines in search results''' option in '''Product control → Avia tickets → Outdated settings → Search restrictions''' is responsible for managing the display of results.

=== Configuring the fields of the "Blacklist of airlines" ===

* '''Airline''' - this field is intended for entering the name of the airline to be blacklisted.
* '''Allowed types''' - this option allows you to set the type of flight for which the airline will be blacklisted. Two options are available:
** '''IF''' - international flight;
** '''DF''' - domestic flight.

== Interline Partners ==

The '''Interline Partners''' page configures the airlines whose carriage can be booked and written out on other airlines' forms under interline agreements.

* '''Interline Partners''' - airline whose carriage is written out on the letterhead of another company.
* '''Contract airline''' - an airline whose letterhead is used for issuing interline partner tickets.
* '''Currently available''' - allows you to temporarily disable this interline.

'''Attention!''' Interlines will not be selected if a contract company is not added for them.

If more than one interline is available for the same carrier, all other things being equal, the interline with the highest commission will be selected.

'''Attention!''' If the airline to be discharged by interline is in the contract directory, the discharge will go by direct contract.

== Airline Directory ==

The '''Airlines''' directory allows you to enter, edit and delete information about airlines, which is used to visualize the ''Airline'' object in the '''Ticket Search and Booking''' module. The directory allows you to store: the name, the actual data about the airline, IATA code, etc. It comes in a standard filling.

== See also ==
* [[Transport Clearing House (TCH)]]

Transport Clearing House (TCH)

2021-02-26T20:31:21Z

I shaletin: Created page with "'''TCH''' (Transport Clearing House) is a participant and executive management body in Air Transportation Settlement Service (ATSS), established by airlines of Russia and..."

'''TCH''' (Transport Clearing House) is a participant and executive management body in [[Air Transportation Settlement Service (ATSS)]], established by airlines of Russia and CIS countries. The main purpose of the House is to ensure the settlement of revenues between agencies and air carriers in the transition to market methods of economic management. TCH concludes contracts with entities, both those wishing to become members and those already participating in the system of mutual settlements.

In the Websky system, when specifying the search requisites, it is possible to select the type of contract and specify the list of airlines for booking and ticketing. The option can be found in: '''Air tickets → GDS connection requisites'''.

'''Attention!''' The Websky system does not apply commission rules for TCH airlines.

== See also ==
* [[Air Transportation Settlement Service (ATSS)]]
* [[Sirena Travel]]
* [[Sirena Travel#Type of itinerary receipt recommended by TCH for Internet sales outlets|Type of itinerary receipt recommended by TCH for Internet sales outlets]]
* [[GDS]]
* [[PCC]]
* [[Air Transportation Settlement Service (ATSS)#List of airlines participating in ATSS in the Galileo project - TCH|List of airlines participating in ATSS in the Galileo project - TCH]]
* [[Galileo#Connecting to Galileo|Connecting to Galileo]]

== Useful links: ==
* [http://www.tch.ru Official TCH Website]

Airline

2021-02-26T20:20:49Z

I shaletin: /* Configuring the fields of the "Blacklist of airlines" */

'''Airline''' is an air transportation company that provides services in passenger and cargo transportation. With both scheduled and charter flights, airlines occupy key positions in the modern transport infrastructure. Websky system uses the terms "carrier" and "air carrier" as synonyms of the concept "airline".

Two main organizations, the International Civil Aviation Organization (ICAO) and the International Air Transport Association (IATA), regulate airlines. ICAO and IATA codes are actively used in directories of airlines, cities and airports used by Websky. In most cases, transportation sales are made through [[GDS]], a kind of exchange where airlines upload data on fares and availability. However, there are carriers, especially in the segment of low-cost transportation, whose resources are not represented in the GDS and whose membership in IATA is incomplete.

Airlines can operate both independently and on the basis of partnership programs (e.g. codeshare and interline agreements), as well as alliances. The most famous alliances uniting major carriers are: SkyTeam, Oneworld and Star Alliance.

== Airline data in Websky ==

The system operates the data of passenger airlines operating scheduled flights and represented in Global Distribution Systems. Thus, the list of carriers available in Websky is limited by the possibilities of GDS chosen by the client for connection, as well as by peculiarities of sales of one or another airline within the clearing zone.

Airline in Websky is an entity with the following characteristics:
* IATA code
* ICAO code
* TAC code
* Name
* Country of Origin

The list of airlines is downloaded from the IATA and TCH (Transport Clearing House) directories. The actuality of the database is checked every six months during regular updates of the system.

The directory also contains information about the airline, which can be displayed in the form of search results (depending on client settings):
* logo
* city in which the headquarters of the airline are located
* website

The airline directory in Websky is editable and can be changed by the customer at his discretion.

'''Attention!''' When editing an airline name in the directory, only the first letter of the word (at the beginning of the name or before the space) becomes capitalized, the rest are lowercased.

== Airline information on Websky forms ==

Airline information - basically the airline IATA code and a short name - is present on all Websky forms associated with the sale of airline tickets:
* a form to view the selected flight combination
* booking confirmation form
* ticketing confirmation form
* form of itinerary receipt inquiry form

By default, the airline specific search filter is disabled in the ticket search form in the standard design, but it is possible to make it available. Activation of this filter allows to show in search results transportation options of only those airlines which have been marked by the user.

== Airline information in Websky search results ==

In the standard design theme, the airline search results form contains an airline name and logo. General data about it can be viewed by clicking on the link with the carrier name (provided that the airline data transfer to the search results form is enabled) or the logo (provided that the '''Link to airline logo on search results'' option is enabled in '''Product control → Air tickets → Processes → Search form'').

Besides the name of the airline whose [[fare]] is displayed in search results you can also specify ''[[operating carrier]]'' - the airline that actually flies the given route.

== Websky settings that can be set depending on the airlines ==

* search presets
* search lists
* checkout lists
* lists for interlines
* surcharges
* discounts
* subagent commissions
* airline commissions
* passenger data formats settings

== Airline blacklists and whitelists ==

"Black" and "white" lists of airlines are introduced in order to be able to manage the search results. For example, to show only flights of certain airlines (from the "white" list) or all airlines except for some airlines (from the "black" list). The '''Airlines in search results''' option in '''Product control → Avia tickets → Outdated settings → Search restrictions''' is responsible for managing the display of results.

=== Configuring the fields of the "Blacklist of airlines" ===

* '''Airline''' - this field is intended for entering the name of the airline to be blacklisted.
* '''Allowed types''' - this option allows you to set the type of flight for which the airline will be blacklisted. Two options are available:
** '''IF''' - international flight;
** '''DF''' - domestic flight.

== Interline Partners ==

The '''Interline Partners''' page configures the airlines whose carriage can be booked and written out on other airlines' forms under interline agreements.

* '''Interline Partners''' - airline whose carriage is written out on the letterhead of another company.
* '''Contract airline''' - an airline whose letterhead is used for issuing interline partner tickets.
* '''Currently available''' - allows you to temporarily disable this interline.

'''Attention!''' Interlines will not be selected if a contract company is not added for them.

If more than one interline is available for the same carrier, all other things being equal, the interline with the highest commission will be selected.

'''Attention!''' If the airline to be discharged by interline is in the contract directory, the discharge will go by direct contract.

== Airline Directory ==

The '''Airlines''' directory allows you to enter, edit and delete information about airlines, which is used to visualize the ''Airline'' object in the '''Ticket Search and Booking''' module. The directory allows you to store: the name, the actual data about the airline, IATA code, etc. It comes in a standard filling.

== See also ==
* [[TCH (Transport Clearing House)]]

Airline

2021-02-26T20:20:29Z

I shaletin: Created page with "'''Airline''' is an air transportation company that provides services in passenger and cargo transportation. With both scheduled and charter flights, airlines occupy key posit..."

'''Airline''' is an air transportation company that provides services in passenger and cargo transportation. With both scheduled and charter flights, airlines occupy key positions in the modern transport infrastructure. Websky system uses the terms "carrier" and "air carrier" as synonyms of the concept "airline".

Two main organizations, the International Civil Aviation Organization (ICAO) and the International Air Transport Association (IATA), regulate airlines. ICAO and IATA codes are actively used in directories of airlines, cities and airports used by Websky. In most cases, transportation sales are made through [[GDS]], a kind of exchange where airlines upload data on fares and availability. However, there are carriers, especially in the segment of low-cost transportation, whose resources are not represented in the GDS and whose membership in IATA is incomplete.

Airlines can operate both independently and on the basis of partnership programs (e.g. codeshare and interline agreements), as well as alliances. The most famous alliances uniting major carriers are: SkyTeam, Oneworld and Star Alliance.

== Airline data in Websky ==

The system operates the data of passenger airlines operating scheduled flights and represented in Global Distribution Systems. Thus, the list of carriers available in Websky is limited by the possibilities of GDS chosen by the client for connection, as well as by peculiarities of sales of one or another airline within the clearing zone.

Airline in Websky is an entity with the following characteristics:
* IATA code
* ICAO code
* TAC code
* Name
* Country of Origin

The list of airlines is downloaded from the IATA and TCH (Transport Clearing House) directories. The actuality of the database is checked every six months during regular updates of the system.

The directory also contains information about the airline, which can be displayed in the form of search results (depending on client settings):
* logo
* city in which the headquarters of the airline are located
* website

The airline directory in Websky is editable and can be changed by the customer at his discretion.

'''Attention!''' When editing an airline name in the directory, only the first letter of the word (at the beginning of the name or before the space) becomes capitalized, the rest are lowercased.

== Airline information on Websky forms ==

Airline information - basically the airline IATA code and a short name - is present on all Websky forms associated with the sale of airline tickets:
* a form to view the selected flight combination
* booking confirmation form
* ticketing confirmation form
* form of itinerary receipt inquiry form

By default, the airline specific search filter is disabled in the ticket search form in the standard design, but it is possible to make it available. Activation of this filter allows to show in search results transportation options of only those airlines which have been marked by the user.

== Airline information in Websky search results ==

In the standard design theme, the airline search results form contains an airline name and logo. General data about it can be viewed by clicking on the link with the carrier name (provided that the airline data transfer to the search results form is enabled) or the logo (provided that the '''Link to airline logo on search results'' option is enabled in '''Product control → Air tickets → Processes → Search form'').

Besides the name of the airline whose [[fare]] is displayed in search results you can also specify ''[[operating carrier]]'' - the airline that actually flies the given route.

== Websky settings that can be set depending on the airlines ==

* search presets
* search lists
* checkout lists
* lists for interlines
* surcharges
* discounts
* subagent commissions
* airline commissions
* passenger data formats settings

== Airline blacklists and whitelists ==

"Black" and "white" lists of airlines are introduced in order to be able to manage the search results. For example, to show only flights of certain airlines (from the "white" list) or all airlines except for some airlines (from the "black" list). The '''Airlines in search results''' option in '''Product control → Avia tickets → Outdated settings → Search restrictions''' is responsible for managing the display of results.

=== Configuring the fields of the "Blacklist of airlines" ===

* '''Airline''' - this field is intended for entering the name of the airline to be blacklisted.
* '''Allowed types''' - this option allows you to set the type of flight for which the airline will be blacklisted. Two options are available:
** '''MVL''' - international flight;
** '''VBL''' - domestic flight.

== Interline Partners ==

The '''Interline Partners''' page configures the airlines whose carriage can be booked and written out on other airlines' forms under interline agreements.

* '''Interline Partners''' - airline whose carriage is written out on the letterhead of another company.
* '''Contract airline''' - an airline whose letterhead is used for issuing interline partner tickets.
* '''Currently available''' - allows you to temporarily disable this interline.

'''Attention!''' Interlines will not be selected if a contract company is not added for them.

If more than one interline is available for the same carrier, all other things being equal, the interline with the highest commission will be selected.

'''Attention!''' If the airline to be discharged by interline is in the contract directory, the discharge will go by direct contract.

== Airline Directory ==

The '''Airlines''' directory allows you to enter, edit and delete information about airlines, which is used to visualize the ''Airline'' object in the '''Ticket Search and Booking''' module. The directory allows you to store: the name, the actual data about the airline, IATA code, etc. It comes in a standard filling.

== See also ==
* [[TCH (Transport Clearing House)]]

Nemo Inventory

2021-02-26T07:09:31Z

I shaletin: /* Changing the schedule */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

=== "Flight" table ===
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
| Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
| 23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
| +value<br/>-value
| +2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
| Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
| Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

=== Table Combinations ===
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

=== Fare Table ===
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

=== Changing the schedule ===


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T07:09:23Z

I shaletin: /* Fare Table */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

=== "Flight" table ===
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
| Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
| 23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
| +value<br/>-value
| +2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
| Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
| Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

=== Table Combinations ===
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

=== Fare Table ===
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T07:09:01Z

I shaletin: /* Table Combinations */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

=== "Flight" table ===
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
| Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
| 23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
| +value<br/>-value
| +2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
| Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
| Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

=== Table Combinations ===
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

==== Fare Table ====
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T07:08:38Z

I shaletin: /* "Flight" table */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

=== "Flight" table ===
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
| Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
| 23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
| +value<br/>-value
| +2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
| Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
| Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

==== Table Combinations ====
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

==== Fare Table ====
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T07:08:00Z

I shaletin: /* "Flight" table */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

==== "Flight" table ====
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
| Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
| 23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
| +value<br/>-value
| +2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
| Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
| Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

==== Table Combinations ====
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

==== Fare Table ====
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T07:00:10Z

I shaletin: /* Content Management */

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:
#*[[File:Flight empty.xls]],
#*[[File:Combination empty.xls]],
#*[[File:Tariff ow empty.xls]].
# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

==== "Flight" table====
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
|Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
|23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
|+value<br/>-value
|+2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
|Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
|Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

==== Table Combinations ====
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

==== Fare Table ====
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Nemo Inventory

2021-02-26T06:59:04Z

I shaletin: Created page with "'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors..."

'''Nemo Inventory''' is a seat resource and fare (content) management system that enables online sales of air services (flights) not available through conventional connectors (GDS) via the Websky Distribution Booking System.

Developed in accordance with IATA recommendations, Nemo Inventory helps you fully control and plan resources and seats, providing tools to enable carriers to manage their own seat resources in order to maximize revenue when selling air transportation.

== Examples of use ==
* The sale of block (block charter) seats on scheduled or charter flights, when seats on flights of a certain airline on a certain route and with a certain schedule are purchased by the customer (charterer);
* A contractual fare that exists on paper but is not in the GDS. In this case the seats are taken from the usual public block of seats in the GDS;
* A negotiated fare, the bookings for which are made by the airline company in its own hosting according to a separate procedure;
* Other cases in which it is not possible to organize online sales through the GDS.

== Benefits of using Nemo Inventory ==
Using Nemo Inventory allows you to organize online sales of your exceptional content as easy and effective as sales of flights from classic sources (GDS). Your customers, whether they are travelers buying tickets on your personal website or sub-agents specializing in distributing your travel services, see no difference in buying a flight from Inventory or from a GDS.

Nemo Inventory provides in the general rendition of available air transportation content that was previously unavailable, by expanding the range of special fares offered and the sale of charter transportation (classic charters, block charters on scheduled flights etc).

For travel companies, chartering significant volumes of seats Inventory is an opportunity to effectively sell remaining seats, sell "hot" seat balances, sell empty runs on inbound and outbound flights (so called "empty lanes") at the beginning and end of the charter program.

Inventory can be seen as a tool to expand the range and increase the profitability of sales on your online resource. It is important to note that the content you have created can be used both on your own site and via an API it can be fed to other online resources (third party applications, meta-search engines, etc.). Such features make Inventory an indispensable, highly effective tool for the successful sale of special rates through all possible sales channels.

The '''Nemo Inventory''' component is connected by the Websky system administrator. To connect, contact [http://helpdesk.nemo.travel project tracker] of Websky technical support service.

==Nemo Inventory principle of operation==

In the system architecture, Nemo Inventory acts as a content provider similar to classic GDSs. The system interacts with Nemo Inventory in a way similar to a GDS. Nemo Inventory provides all the necessary functionality for sales through the standard Websky functionality, i.e. it supports searching, booking and cancellation methods. At the same time you have a wide range of opportunities for creating and managing your seats and fares.

For easy creation and management of flights Nemo Inventory supports the following types of content:
* flight,
* seat resource,
* flight combination,
* fare,
* taxes.

==Configuring the Nemo Inventory component==

You can configure the component in the section '''Working with orders → Nemo Inventory'''. The section consists of three subsections:
* Content Management
* Flight monitor
* Ticket numbers setup.

=== Content Management ===

The ''Content Management'' section provides the following options:
* setting up flight itinerary,
* setting up flight schedule,
* seat resource management,
* setting fare information,

The data are set by a table in XLS format file. The '''Content Management''' window is a form for importing and exporting the created data in XLS format.
# Fill in the following files: '''flight''', '''flight''', '''tariff_ow''' with data. Templates of files to fill in:

# Import the data table to enter the information into the system:
#* select the type of file to import,
#* press the '''Browse''' button, select the file that corresponds to the type,
#* Click the '''Upload ''' button.



To change the data in the tables:
# Export file(s) - click the button with the appropriate type.
# Edit the content of the file(s).
# Import the modified files back into the system.

This is necessary to control the version date of the files. Thus, when trying to load into the system a file with an earlier modification date than the one that is already in the system, the warning ''You cannot overwrite the newer data with the specified obsolete '' appears and offers you two choices:
* forcibly overwrite the data
* refuse to load.



'''Attention!''' All cells in the file must be in text format. No extra spaces are allowed.

==== "Flight" table====
'''Flight''' is a content type that contains information about the flight for which the agency sells seats. It includes information about:
* flight type (charter/regular),
* activity attribute,
* flight number, companies,
* marketing and operating airlines,
* schedule,
* and more.

To unload the form to fill in the flight data, click the '''Flight''' button.

{| class="wikitable mw-collapsible mw-collapsed"
!colspan = 4|Format to fill in the parameters of the file for entering flight information
|-
! scope="col" | Title
! scope="col" | Description
! scope="col" | Allowable values
! scope="col" | Examples
|-
|<span id="id">id</span>
| Unique number of the flight record which is assigned by the system. <br/> By default it is not filled in during uploading of the file; it is filled in during unloading. <br/> Editing the rule with the specified id leads to changing the already created rule, if the field is empty - the new rule will be created.
| Empty or system number
| 30<br/>48
|-
|<span id="active">active</span>
| Parameter which defines participation or nonparticipation of the given flight in formation of variants output<br/>
| 1 - active <br/> 0 - inactive <br/> -1 - deletion of the flight <br/> empty - inactive
| 1 <br/> 0 <br/> -1
|-
| <span id="VC">marketing company</span>
| Name or code of the marketing airline providing the flight service<br/>
| Text string
| UT <br/> UN
|-
| <span id="VC">freighter</span>
| Name of the travel company that offers seats on this flight <br/>
| Text string
| UT <br/> UN <br/>S7
|-
|span id="airline">airline</span
| IATA code of the airline operating the flight <br/>
| A code
| SU<br/>UN
|-
|span id="departure">departure</span>
| IATA code of the airport of departure, aggregating airports are allowed <br/>
| code
| MOW <br/>VKO
|-
|span id="arrival">arrival</span>
| IATA code of arrival airport, aggregating airports are allowed <br/>
| Code
| MOW <br/>VKO
|-
|span id="landing">landing</span>
| IATA airport code for technical landing point, aggregating points are allowed<br/>
| Code
| MOW <br/>VKO
|-
| <span id="flight number">flight number</span>
| unique flight number<br/>
|Numbers, Latin letters are acceptable
| 203<br/>11
|-
| <span id="departure terminal">departure terminal</span>
| Departure airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="arrival terminal">arrival terminal</span>
|Arrival airport terminal code or number<br/>
| Latin letters or numbers
| А<br/>С
|-
| <span id="departure time"> departure time</span
| Flight departure time in time zone of departure airport<br/>
| HH:MM
|23:04<br/>11:15
|-
| <span id="arrival time">arrival time</span
| Arrival time of flight in time zone of arrival airport<br/>
| HH:MM
| 22:05<br/>09:15
|-
| <span id="next day">next day</span>
| Attribute of arrival on the previous or next day for airports with a significant difference in time zones. <br/>Set in the number of days difference.
|+value<br/>-value
|+2 ( arrival after 24 hours)<br/>-1 (arrival on the previous day)
|-
|span id="days of the week">days of the week</span>
| Days of the week on which the flight is performed. Odd week days are set by figures from 1 to 7, even days - from 8 to 14.<br/>
| Numbers from 1 to 14, separated by comma.
| 2,4,6,9,11,13 (Tuesday, Thursday, Saturday on even and odd weeks) <br/>8,9,10,11,12,13,14 (all days on even weeks)
|-
| <span id="flight season start">flight season start</span>
|Start date of the flight period <br/>
| DD.MM.YYYY
| 01.01.2014<br/>02.08.2015
|-
| <span id="flight season end">flight season end</span>
| End date of the flight period<br/>
| DD.MM.YYYY
| 01.01.2015<br/>02.08.2016
|-
| <span id="type of flight">type of flight</span>
| Type of aircraft performing the flight.<br/>To receive the information about the aircraft from the directory, you must specify the three-digit code of the aircraft.
| Text string
| 139<br/>747
|-
| <span id="economy">economy</span>
| Number of seats available on the flight in basic Economy class for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| subclass liters + number of seats (without separator)
|Y9,T13,N9<br/>L17,M20
|-
| <span id="business">business</span>
| Number of seats available on the flight in basic Business class for each booking subclass.<br/>Included as a combination of the subclass letter and number of seats.
| subclass + number of seats (without separator)
| J9,C12,D9<br/>C12,D10
|-
| <span id="first">first</span>
| Number of seats available on the flight in base class "First" for each booking subclass.<br/>Included as a combination of the subclass letter and the number of seats.
| Subclass literal + number of seats (without separator). Combinations are separated by comma.
| F15,P2<br/>A10
|}

Some information about the flight is discussed in more detail:
* '''Freighter''' is the owner (agent/tour operator) of the block of seats to be sold on a given flight. The charterer is a mandatory parameter when specifying the flight type ''charter''.
* '''Marketing airline''' provides the flight,
* '''Operating airline''' performs it.
''Example.'' The ''MOW-LED'' flight is provided by the ''SU'' airline, but is operated by the ''FV'' airline. <br />
The owner of seats and fares for a given flight is determined as follows: for charters it is the freighter, for scheduled flights it is the marketing airline.

* '''Flight Schedule''' is defined as a list of days within a two-week period that is set for a particular season, the two-week period starts at the beginning of the first flight season.
Several flight seasons can be defined in the schedule, each of which can have its own schedule. Flight seasons can not overlap, i.e. if the flight is from May 1st to December 20th for one day, and from September 1st to November 1st for another, then there must be 3 seasons - from May 1st to August 31st, from September 1st to December 1st, from September 1st to December 1st, and from November 2nd to December 20th.
* '''Flight classes and number of seats''. The classes of a flight are set up in the form of letters grouped according to basic classes (Business, First, Economy); for each letter the total number of seats initially available for sale in the given class is set.

* '''Breakpoints''' (technical landings). More than 1 stop may be specified on a flight. A landing is considered a stopover and not a connection if there is no flight number change. Even if the aircraft lands, passengers are unloaded, loaded onto another plane and sent on their way, without a flight number change it still remains a technical landing, which is displayed as a technical landing on one single flight segment.

* '''Flight Changes''' allows you to finely manage flight information for certain dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, change the flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule. What makes a flight unique is the combination of the flight number and the seat owner code on it.

==== Table Combinations ====
'''Flight Combination''' - provides the ability to set various combinations of flights.

The ''Combinations'' button, unloading the corresponding form, provides the possibility to set various combinations of flights. <br />The detailed file format is described here: [[Manage combinations in Nemo Inventory|'''File format for combination entries''']]. <br />

'''Attention!''' <u>Fares are bound and applied exclusively to flight combinations</u>, so even OW flights from a single flight must be specified as combinations from a single flight.

Also the '''Combinations''' file can specify multiple flights for the same trip in different configurations, whether it is a one-way or round trip flight, as well as specify different departure dates. Between consecutive pairs of flights, you can specify restrictions on the allowed travel duration as a list of the number of days between the departure dates of the first and second flight in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Maximum 4 flights can be specified in the combination. Information about each flight in the combination includes the following data:
* flight number,
* airline code,
* class letter,
* flight start date,
* date the flights ended,
* days between flights.

Restrictions on the allowed travel duration can be set between consecutive pairs of flights in the form of a list of the number of days between the departure dates of the first and second flights in the pair. The travel duration is calculated as a direct subtraction of the departure dates of the first and second flights in the pair (12.02 - 10.02 = 2 days travel duration). If not specified, no restrictions apply for this flight pair.

Also in the combination you can specify a list of fares that apply to this combination and the type of flight destination within this combination, these fields are only informative at the moment and do not affect the logic of binding tables to each other.

==== Fare Table ====
The Fare table describes the rules of price formation for a certain set of flights in the Combinations file.
To add and edit fare information in the form file provided, click on the '''Fare''' button ( for details, see [[Managing Fares in Nemo Inventory| '''File format for entering fare information'']]).

=== Flight monitor ===


In this section you can get information on flight statistics. The upper part of the flight monitor window shows the names of marketing companies and the number of flights provided by this company, contained in the flight statistics for the selected period. Depending on the selected time interval:
* Day
* Three days
* One week
* Two weeks
* Month

The Flight Monitor window looks like a table with flight information for the selected time range. It is available to switch for the next and previous month, week, etc via buttons.

Each cell of the table displays the flight route, its marketing company and flight number. By clicking on a cell, additional information about the particular flight is displayed: the number of seats available, booking class and number of tickets sold. There is also a possibility to change the flight information for certain days. Changes can be made by clicking on the "Change Schedule" link.

==== Changing the schedule ====


Flight changes allow you to finely manage flight information for specific dates that may or may not be part of the schedule. This allows you, for example, to close sales for a given flight on a certain day, change the departure/arrival time, flight number, reschedule the flight, or even add new departure days that are not included in the main flight schedule.

The following set of data can be set to change in the flight:
* Flight activity
* Departure/arrival airport
* Departure/arrival terminal
* Departure/arrival time
* Flight number
* Arrival on the next day
* Type of aircraft
* Landing

== Use of content in flight sales ==
The order and logic of using different types of content when searching, booking and ticketing.

=== Search ===

In order to book and ticket a flight, it must first be found. Within Inventory, the procedure for processing a search request consists of the following steps:
# '''Construct a route for each of the requested segments'''. At the moment, the maximum route length for a requested segment is limited to 1 segment. If a route could not be built for one of the requested segments, the search is aborted and Inventory returns an error: '''Unable to build a route for the requested segment''' with the corresponding segment specified.
# '''Search for suitable flights for the constructed routes, taking into account their schedules, connection times, filters by airline and the availability of seats in the required classes and constructing full flights from them.''' If no suitable flights could be found for one of the requested segments, the search is terminated and Inventory returns the error: ''Could not find a schedule satisfying the specified criteria for the segment'' with the indication of the corresponding segment. <br />If no complete flight could be constructed from the flights found, then the search is aborted and Inventory returns the error: ''Unable to construct a complete flight meeting the specified criteria''.<br />If none of the flights constructed have the required number of seats, then the search is aborted and Inventori returns the error: ''No required number of seats available on the flights meeting the specified criteria''.
# '''Applying Flight Combinations to Built Flights.''' At this point, flights of more than 4 segments are discarded within this procedure. A suitable flight combination is searched for each of the constructed flights. <br />If no flight combination can be found for a flight that fully matches it, then a separate matching combination is searched for each segment in the flight. <br />If no suitable flight combinations can be found for any of the flights, the search is aborted and Inventori returns an error '''No valid flight combinations that meet the given criteria''.
# '''Evaluation of the obtained flights.''' For each of the flights, ''a set of fares is generated" which provide the lowest price for the given flight. The following sequence of actions is performed:
## the system considers each combination that has been applied to the flight.
## the system retrieves all fares for the seat owner on the first flight of the examined combination.

For each '''fare''', the following set of checks is performed:
# the fare is checked for applicability to the current flight combination (by its ID)
# the fare is checked if the first flight of the combination can be sold at the given fare - in this case it is checked
* the current date is in one of the fare's selling seasons (SalesDates) and the season does not end in one hour
* the date of departure of the first flight in the combination is in one of the fare service seasons (ServiceDates).
# the fare is checked for restrictions for minimum time before departure and maximum number of days before departure

# access to the fare, if it is private, and restrictions on preferred fare types from search request are checked
# for the fare entered to the passenger type other than ADT, the fare is checked for the applicability to any of the requested passenger types. <br />If the fare passed all the checks, then it is considered applicable to the given combination of flights. If no suitable fares could be found, examination of the given flight is terminated and it will not appear in the search results.
# The one with the lowest total effective fare (taking into account the combination price and the types of passengers requested) is selected from all eligible fares.
If there are no suitable prices for any of the flights, the search is terminated and Inventory returns the error: "Failed to find the prices that match the criteria set''.<br/> Flights for which prices were found are displayed in the search output.

=== Booking ===
When booking a flight,
# the system checks:
#* availability of the flights to be booked,
#* availability of the required number of seats on them.
# The system evaluates the booked flight in the same way as in the search.
# Based on all received data, a PNR object is created in the Inventory system. <br />If the price could not be obtained due to any reason, the seats taken are returned to the pool of available seats for booking and the booking is cancelled with a corresponding error.

The booking can be
*refreshed (to get its current status and price),
*canceled,
*ticketed.

=== Ticketing ===
The ticketing is carried out in two steps:
# The ticketing triggered after the receipt of payment from the client. The '''electronic documents (ED)''' are generated for the provision of the ticketing service by the airline. The booking gets the status "pending ticketing".
#Addition of airline tickets - currently, Inventory does not support automatic transfer of the created bookings to GDS or inventory systems for automatic issuing of airline tickets, so an authorized agent representative manually transfers the bookings to the appropriate systems and issues airline tickets in them once a certain period of time. Then he\she enters the issued tickets to the necessary PNR in the Inventory. After the tickets are entered for all passengers, the booking in Inventory takes the status ''ticketed''.<br />The EDs generated at the previous stage are deactivated with the status ''used''.

The booking can be activated for a certain period of time after it has been ticketed (but before the tickets have been inserted by the airline). In this case the ED for airline tickets issuance is deactivated with the status "cancelled". The deletion of airline tickets is not supported at the moment.

=== Ticket numbers setup ===


This section displays the orders waiting for ticket numbers to be inserted. The section can be accessed by the manager and the agency expert.

When an order is issued, the ticketing will not be completed until the ticket numbers are entered in the '''Ticket numbers assignment''' section (''See Sending a Ticket Order for the ticketing'').
To perform the order ticketing, you need to transfer the bookings created in the inventory to the GDS or airline (where the block of seats is stored) and issue the statement. Then the received numbers of the ticket are entered in the section "Ticket numbers assignment". After the numbers are assigned, you need to return to the order and start the statement.

The section is a sequence of forms with the date of departure (several booked flights on the same date of departure are located on one form). Clicking on one of the tabs opens a form with a list of departure directions. If you click on a particular direction, a field for entering the ticket number is displayed.

If one ticket number has been issued, the number for the round trip direction is entered only in the first window. If there are two numbers, you need to enter the second ticket number in the second window.

Service packages

2021-02-25T08:07:29Z

I shaletin: /* Adding a new service package */

'''Service packages''' is a module of the Websky system that allows an agency to increase profitability from each ticket sold by adding packages that can be selected by passengers during the ticket purchase process.

== Service packages in Websky ==
In order to connect the Service Packages module in Websky the agency must have the '''Ancillary Services''' component enabled and the '''Service Packages''' module enabled.

The module is paid and must be enabled by the administrator of the Websky system.

'''Attention!''' Service Packages functionality is not supported for charter providers.

== Getting started using the module ==
In order to activate the Service Packages module, you need to go to the Settings section '''Product control → Avia Tickets → Additional Services → Service Packages → User Settings''' and check the '''Packages are enabled for the selected user''' checkbox.

== Adding a new service package ==
In order to proceed to creating/editing service packages, you need to go to the Administration Panel section '''Sales Management → Flight Management → Additional Services → Service Packages → Management'''.

To create a new service package, you need to click on the link "Create a new entry".

* '''Package enabled''' - this setting must be enabled in order for the service package to be displayed on the site.
* '''Price type''' - defines in which value the price of the package will be set: in absolute or relative. If you select "Percentage", the fields "Percentage of the price of the order" and "Rounding accuracy" become available; if you select "Value", only the field "Price per passenger" becomes available.
** '''Price per single passenger''' is a mandatory field. Here you enter the price of a package of services for one passenger. When the ticket is issued on the booking form, the total price of the package for all passengers is displayed here.
** '''Percentage of the price of the order''' - the percentage of the price of the order, according to which the price of the service package will be calculated. The price of the service package for one passenger is calculated as the price in percent of the price of the flight (without fees and ancillary services), divided by the number of passengers with a seat.
** '''Rounding accuracy''' - determines the rounding accuracy of the package price.
* '''Minimum Order Value Limit''' - the lower limit of the flight price (without fees and ancillary services), starting from which the service package will be displayed on the booking form.
* '''Maximum Order Value Limit (inclusive)''' - the upper limit of the flight cost (without charges and ancillary services), after reaching which the service package will not be displayed on the booking form.
* '''Applies to the classes''' - defines for which classes of service the service package will be displayed.
* '''Package name''' - name of the service package.
* '''Short description''' - a brief description of the service package.
* '''Full description''' - a full description of the service package. You can go to it from the order page by clicking the special link.

For the '''Package name''', '''Short description''' and '''Full description''' fields, if there are several versions of the site in different languages, it is possible to add translation of the names/text on the corresponding tabs.

* '''Allowable transition source''' - identifier of the transition source from the Metrics module, at transition from which this service package will be shown.
* '''Transition source for price override''' - identifier of the transition source from the Metrics module. When switching from the specified source the price of the service package will be changed in accordance with the value of the following field.
* '''Override price for the transition source specified above''' - the field for entering the overridden price of the package for the transition source specified above. Also, the currency in which the specified price will be displayed is specified here.

'''Attention!''' Since the user should be able to refuse from paid service packages by selecting the "default" package with the zero price, for the correct work of the module it is necessary to have a service package with zero price. If such a package is not created, the following warning message will be displayed: "Error: The default package is not defined, create a package with zero price".

'''Attention!''' It is not possible to delete a service package that has already been created, as it is assumed that the service package could have been selected earlier in an order that has already been placed.

== Adding services to a package ==

In order to add the services themselves to the created service packages, you need to click on the ''Add Service'' button.
* '''Service name''' - name of the corresponding service.
* '''Short description''' - a brief description of the service.
* '''Full description''' - a full description of the service. The transition to this description from the order page is made by clicking the special link.

For all the above-mentioned fields, if several versions of the site are available in different languages, it is possible to add translations of the names/text on the corresponding tabs.

* '''Service price per passenger (optional field)''' - in this field, it is possible to specify the price of the service for an individual passenger. For example, it can be the agent's charge for returning or exchanging the ticket.

== Default Service Packages ==
It is possible to select the service packages that will be marked on the booking form by default. At the same time, you can specify both the default service package which will always be selected by default and the service package which will be selected on the booking form subject to transition from a specific source created in the Metrics module.
To configure this functionality you need to go to the settings section '''Sales management → Airline tickets → Additional services → Service packages → User settings'''.

* '''Default selected package''' - select the service package that will be marked by default on the booking form
* '''To override the default package select the source''' - select the source that will set the package selected below as the default package when you switch from it.
* '''Default Select Source Package''' - The default service package that is selected for the transition source specified above.

The default package is always the one with the lowest price.

== Display on Personal Account page==


There is a special queue in the Personal Account (Service Packages), where all actual (booked and not cancelled) bookings with packages of services are placed. Only packages with a non-zero value go into this queue.

It is possible to filter orders that contain certain service packages. To do this, select the name of the required service package in the relevant drop-down list in the Filter of Orders of the Personal Account.

== Display on the booking form ==

Service package options are displayed on the booking form in accordance with the selected user language.

According to the settings, depending on the transition source, the price of packages may change, as well as which packages will be displayed to the user.

When the user selects a package, the price of the order and the payment charge are recalculated without refreshing the page.

'''Attention!''' Service packages can only be selected for adult passengers and children. Infants/children with a seat do not count towards the total price of the service packages included in the order.

Service package selection/re-selection is available both before and after the booking. Service package selection is blocked after payment or cancellation.



== Notifications ==

The possibility to add information about the service packages included in the order to the texts of notifications has been implemented.

For this purpose a special variable <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_INFO%</syntaxhighlight>, which includes the description of the selected service package, displayed according to the specified template. It is available for use in the settings section '''System Settings → Notifications and Documents → Email Templates''' for the "Flight Booking" and "Ticketing" templates.

%SERVICE_PACK_INFO% (Information about the selected service package)

To create a template to display a description of a service package, you need to go to the settings '''System settings → Notifications and documents → Documents → Documents for avia → Documents for additional services''' and select the appropriate type of document "Service packages".

The following variables are available when creating the template:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %SERVICE_PACK_NAME%
| Name of the service package
|-
| %SERVICE_PACK_PRICE%
| Service package price for a single passenger
|-
| %SERVICE_PACK_DESC_SHORT%
|Short description of the service package
|-
| %SERVICE_PACK_DESC_FULL%
|Full description of the service package
|}

The group <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_ITEMS%</syntaxhighlight> is used to display information about all services that are part of the package. The following variables are available for use within this group:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %ITEM_NAME%
| Service name
|-
| %ITEM_PRICE%
| The price of the service for an individual passenger
|-
| %ITEM_DESC_SHORT%
| Short description of the service
|-
| %ITEM_DESC_FULL%
| Full description of the service
|}

Remember that in this case the group only combines other variables, so in order to correctly display the list of services included in the service package, you need to specify the group variable both at the beginning and at the end. Example:

%SERVICE_PACK_ITEMS%
%ITEM_NAME%
%ITEM_PRICE%
%ITEM_DESC_SHORT%
%ITEM_DESC_FULL%
%SERVICE_PACK_ITEMS%

== Itinerary Receipt ==
For the information about the service package included in the order to be displayed in the itinerary receipt, in the settings section '''System settings → Notifications and documents → Documents → Documents for aviation → Itinerary receipt''', by analogy with notification templates, it is possible to use a variable that includes a description of the service package, displayed in accordance with the template specified in the settings section '''System settings → Notifications and documents → Documents for avia → Documents for additional services''':

%SERVICE_PACK_INFO% (Information about the selected service package)

Service packages

2021-02-25T08:05:00Z

I shaletin:

'''Service packages''' is a module of the Websky system that allows an agency to increase profitability from each ticket sold by adding packages that can be selected by passengers during the ticket purchase process.

== Service packages in Websky ==
In order to connect the Service Packages module in Websky the agency must have the '''Ancillary Services''' component enabled and the '''Service Packages''' module enabled.

The module is paid and must be enabled by the administrator of the Websky system.

'''Attention!''' Service Packages functionality is not supported for charter providers.

== Getting started using the module ==
In order to activate the Service Packages module, you need to go to the Settings section '''Product control → Avia Tickets → Additional Services → Service Packages → User Settings''' and check the '''Packages are enabled for the selected user''' checkbox.

== Adding a new service package ==
In order to proceed to creating/editing service packages, you need to go to the Administration Panel section '''Sales Management → Flight Management → Additional Services → Service Packages → Management'''.

To create a new service package, you need to click on the link "Create a new entry".

* '''Package enabled''' - this setting must be enabled in order for the service package to be displayed on the site.
* '''Price type''' - defines in which value the price of the package will be set: in absolute or relative. If you select "Percentage", the fields "Percentage of the price of the order" and "Rounding accuracy" become available; if you select "Value", only the field "Price per passenger" becomes available.
** '''Price per single passenger''' is a mandatory field. Here you enter the price of a package of services for one passenger. When the ticket is issued on the booking form, the total price of the package for all passengers is displayed here.
** '''Percentage of the price of the order''' - the percentage of the price of the order, according to which the price of the service package will be calculated. The price of the service package for one passenger is calculated as the price in percent of the price of the flight (without fees and ancillary services), divided by the number of passengers with a seat.
** '''Rounding accuracy''' - determines the rounding accuracy of the package price.
* '''Minimum Order Value Limit''' - the lower limit of the flight price (without fees and ancillary services), starting from which the service package will be displayed on the booking form.
* The upper limit of the price of the flight (without fees and ancillary services) above which the service package will not be displayed on the booking form.
* '''Applies to the classes''' - defines for which classes of service the service package will be displayed.
* '''Package name''' - name of the service package.
* '''Short description''' - a brief description of the service package.
* '''Full description''' - a full description of the service package. You can go to it from the order page by clicking the special link.

For the '''Package name''', '''Short description''' and '''Full description''' fields, if there are several versions of the site in different languages, it is possible to add translation of the names/text on the corresponding tabs.

* '''Allowable transition source''' - identifier of the transition source from the Metrics module, at transition from which this service package will be shown.
* '''Transition source for price override''' - identifier of the transition source from the Metrics module. When switching from the specified source the price of the service package will be changed in accordance with the value of the following field.
* '''Override price for the transition source specified above''' - the field for entering the overridden price of the package for the transition source specified above. Also, the currency in which the specified price will be displayed is specified here.

'''Attention!''' Since the user should be able to refuse from paid service packages by selecting the "default" package with the zero price, for the correct work of the module it is necessary to have a service package with zero price. If such a package is not created, the following warning message will be displayed: "Error: The default package is not defined, create a package with zero price".

'''Attention!''' It is not possible to delete a service package that has already been created, as it is assumed that the service package could have been selected earlier in an order that has already been placed.

== Adding services to a package ==

In order to add the services themselves to the created service packages, you need to click on the ''Add Service'' button.
* '''Service name''' - name of the corresponding service.
* '''Short description''' - a brief description of the service.
* '''Full description''' - a full description of the service. The transition to this description from the order page is made by clicking the special link.

For all the above-mentioned fields, if several versions of the site are available in different languages, it is possible to add translations of the names/text on the corresponding tabs.

* '''Service price per passenger (optional field)''' - in this field, it is possible to specify the price of the service for an individual passenger. For example, it can be the agent's charge for returning or exchanging the ticket.

== Default Service Packages ==
It is possible to select the service packages that will be marked on the booking form by default. At the same time, you can specify both the default service package which will always be selected by default and the service package which will be selected on the booking form subject to transition from a specific source created in the Metrics module.
To configure this functionality you need to go to the settings section '''Sales management → Airline tickets → Additional services → Service packages → User settings'''.

* '''Default selected package''' - select the service package that will be marked by default on the booking form
* '''To override the default package select the source''' - select the source that will set the package selected below as the default package when you switch from it.
* '''Default Select Source Package''' - The default service package that is selected for the transition source specified above.

The default package is always the one with the lowest price.

== Display on Personal Account page==


There is a special queue in the Personal Account (Service Packages), where all actual (booked and not cancelled) bookings with packages of services are placed. Only packages with a non-zero value go into this queue.

It is possible to filter orders that contain certain service packages. To do this, select the name of the required service package in the relevant drop-down list in the Filter of Orders of the Personal Account.

== Display on the booking form ==

Service package options are displayed on the booking form in accordance with the selected user language.

According to the settings, depending on the transition source, the price of packages may change, as well as which packages will be displayed to the user.

When the user selects a package, the price of the order and the payment charge are recalculated without refreshing the page.

'''Attention!''' Service packages can only be selected for adult passengers and children. Infants/children with a seat do not count towards the total price of the service packages included in the order.

Service package selection/re-selection is available both before and after the booking. Service package selection is blocked after payment or cancellation.



== Notifications ==

The possibility to add information about the service packages included in the order to the texts of notifications has been implemented.

For this purpose a special variable <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_INFO%</syntaxhighlight>, which includes the description of the selected service package, displayed according to the specified template. It is available for use in the settings section '''System Settings → Notifications and Documents → Email Templates''' for the "Flight Booking" and "Ticketing" templates.

%SERVICE_PACK_INFO% (Information about the selected service package)

To create a template to display a description of a service package, you need to go to the settings '''System settings → Notifications and documents → Documents → Documents for avia → Documents for additional services''' and select the appropriate type of document "Service packages".

The following variables are available when creating the template:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %SERVICE_PACK_NAME%
| Name of the service package
|-
| %SERVICE_PACK_PRICE%
| Service package price for a single passenger
|-
| %SERVICE_PACK_DESC_SHORT%
|Short description of the service package
|-
| %SERVICE_PACK_DESC_FULL%
|Full description of the service package
|}

The group <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_ITEMS%</syntaxhighlight> is used to display information about all services that are part of the package. The following variables are available for use within this group:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %ITEM_NAME%
| Service name
|-
| %ITEM_PRICE%
| The price of the service for an individual passenger
|-
| %ITEM_DESC_SHORT%
| Short description of the service
|-
| %ITEM_DESC_FULL%
| Full description of the service
|}

Remember that in this case the group only combines other variables, so in order to correctly display the list of services included in the service package, you need to specify the group variable both at the beginning and at the end. Example:

%SERVICE_PACK_ITEMS%
%ITEM_NAME%
%ITEM_PRICE%
%ITEM_DESC_SHORT%
%ITEM_DESC_FULL%
%SERVICE_PACK_ITEMS%

== Itinerary Receipt ==
For the information about the service package included in the order to be displayed in the itinerary receipt, in the settings section '''System settings → Notifications and documents → Documents → Documents for aviation → Itinerary receipt''', by analogy with notification templates, it is possible to use a variable that includes a description of the service package, displayed in accordance with the template specified in the settings section '''System settings → Notifications and documents → Documents for avia → Documents for additional services''':

%SERVICE_PACK_INFO% (Information about the selected service package)

Service packages

2021-02-25T08:04:28Z

I shaletin: Created page with "'''Service packages''' is a module of the Websky system that allows an agency to increase profitability from each ticket sold by adding packages that can be selected by passen..."

'''Service packages''' is a module of the Websky system that allows an agency to increase profitability from each ticket sold by adding packages that can be selected by passengers during the ticket purchase process.

== Service packages in Websky ==
In order to connect the Service Packages module in Websky the agency must have the '''Ancillary Services''' component enabled and the '''Service Packages''' module enabled.

The module is paid and must be enabled by the administrator of the Websky system.

'''Attention!''' Service Packages functionality is not supported for charter providers.

== Getting started using the module ==
In order to activate the Service Packages module, you need to go to the Settings section '''Product control → Avia Tickets → Additional Services → Service Packages → User Settings''' and check the '''Packages are enabled for the selected user''' checkbox.

== Adding a new service package ==
In order to proceed to creating/editing service packages, you need to go to the Administration Panel section '''Sales Management → Flight Management → Additional Services → Service Packages → Management'''.

To create a new service package, you need to click on the link "Create a new entry".

* '''Package enabled''' - this setting must be enabled in order for the service package to be displayed on the site.
* '''Price type''' - defines in which value the price of the package will be set: in absolute or relative. If you select "Percentage", the fields "Percentage of the price of the order" and "Rounding accuracy" become available; if you select "Value", only the field "Price per passenger" becomes available.
** '''Cost per single passenger''' is a mandatory field. Here you enter the cost of a package of services for one passenger. When the ticket is issued on the booking form, the total price of the package for all passengers is displayed here.
** '''Percentage of the price of the order''' - the percentage of the cost of the order, according to which the price of the service package will be calculated. The price of the service package for one passenger is calculated as the price in percent of the price of the flight (without fees and ancillary services), divided by the number of passengers with a seat.
** '''Rounding accuracy''' - determines the rounding accuracy of the package price.
* '''Minimum Order Value Limit''' - the lower limit of the flight price (without fees and ancillary services), starting from which the service package will be displayed on the booking form.
* The upper limit of the price of the flight (without fees and ancillary services) above which the service package will not be displayed on the booking form.
* '''Applies to the classes''' - defines for which classes of service the service package will be displayed.
* '''Package name''' - name of the service package.
* '''Short description''' - a brief description of the service package.
* '''Full description''' - a full description of the service package. You can go to it from the order page by clicking the special link.

For the '''Package name''', '''Short description''' and '''Full description''' fields, if there are several versions of the site in different languages, it is possible to add translation of the names/text on the corresponding tabs.

* '''Allowable transition source''' - identifier of the transition source from the Metrics module, at transition from which this service package will be shown.
* '''Transition source for cost override''' - identifier of the transition source from the Metrics module. When switching from the specified source the price of the service package will be changed in accordance with the value of the following field.
* '''Override price for the transition source specified above''' - the field for entering the overridden price of the package for the transition source specified above. Also, the currency in which the specified price will be displayed is specified here.

'''Attention!''' Since the user should be able to refuse from paid service packages by selecting the "default" package with the zero price, for the correct work of the module it is necessary to have a service package with zero price. If such a package is not created, the following warning message will be displayed: "Error: The default package is not defined, create a package with zero price".

'''Attention!''' It is not possible to delete a service package that has already been created, as it is assumed that the service package could have been selected earlier in an order that has already been placed.

== Adding services to a package ==

In order to add the services themselves to the created service packages, you need to click on the ''Add Service'' button.
* '''Service name''' - name of the corresponding service.
* '''Short description''' - a brief description of the service.
* '''Full description''' - a full description of the service. The transition to this description from the order page is made by clicking the special link.

For all the above-mentioned fields, if several versions of the site are available in different languages, it is possible to add translations of the names/text on the corresponding tabs.

* '''Service price per passenger (optional field)''' - in this field, it is possible to specify the price of the service for an individual passenger. For example, it can be the agent's charge for returning or exchanging the ticket.

== Default Service Packages ==
It is possible to select the service packages that will be marked on the booking form by default. At the same time, you can specify both the default service package which will always be selected by default and the service package which will be selected on the booking form subject to transition from a specific source created in the Metrics module.
To configure this functionality you need to go to the settings section '''Sales management → Airline tickets → Additional services → Service packages → User settings'''.

* '''Default selected package''' - select the service package that will be marked by default on the booking form
* '''To override the default package select the source''' - select the source that will set the package selected below as the default package when you switch from it.
* '''Default Select Source Package''' - The default service package that is selected for the transition source specified above.

The default package is always the one with the lowest price.

== Display on Personal Account page==


There is a special queue in the Personal Account (Service Packages), where all actual (booked and not cancelled) bookings with packages of services are placed. Only packages with a non-zero value go into this queue.

It is possible to filter orders that contain certain service packages. To do this, select the name of the required service package in the relevant drop-down list in the Filter of Orders of the Personal Account.

== Display on the booking form ==

Service package options are displayed on the booking form in accordance with the selected user language.

According to the settings, depending on the transition source, the price of packages may change, as well as which packages will be displayed to the user.

When the user selects a package, the price of the order and the payment charge are recalculated without refreshing the page.

'''Attention!''' Service packages can only be selected for adult passengers and children. Infants/children with a seat do not count towards the total price of the service packages included in the order.

Service package selection/re-selection is available both before and after the booking. Service package selection is blocked after payment or cancellation.



== Notifications ==

The possibility to add information about the service packages included in the order to the texts of notifications has been implemented.

For this purpose a special variable <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_INFO%</syntaxhighlight>, which includes the description of the selected service package, displayed according to the specified template. It is available for use in the settings section '''System Settings → Notifications and Documents → Email Templates''' for the "Flight Booking" and "Ticketing" templates.

%SERVICE_PACK_INFO% (Information about the selected service package)

To create a template to display a description of a service package, you need to go to the settings '''System settings → Notifications and documents → Documents → Documents for avia → Documents for additional services''' and select the appropriate type of document "Service packages".

The following variables are available when creating the template:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %SERVICE_PACK_NAME%
| Name of the service package
|-
| %SERVICE_PACK_PRICE%
| Service package price for a single passenger
|-
| %SERVICE_PACK_DESC_SHORT%
|Short description of the service package
|-
| %SERVICE_PACK_DESC_FULL%
|Full description of the service package
|}

The group <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">%SERVICE_PACK_ITEMS%</syntaxhighlight> is used to display information about all services that are part of the package. The following variables are available for use within this group:

{| style="width: 800px" class="wikitable"
|-
! scope="col" width="200" | Variable
! scope="col" width="300" | Description
|-
| %ITEM_NAME%
| Service name
|-
| %ITEM_PRICE%
| The price of the service for an individual passenger
|-
| %ITEM_DESC_SHORT%
| Short description of the service
|-
| %ITEM_DESC_FULL%
| Full description of the service
|}

Remember that in this case the group only combines other variables, so in order to correctly display the list of services included in the service package, you need to specify the group variable both at the beginning and at the end. Example:

%SERVICE_PACK_ITEMS%
%ITEM_NAME%
%ITEM_PRICE%
%ITEM_DESC_SHORT%
%ITEM_DESC_FULL%
%SERVICE_PACK_ITEMS%

== Itinerary Receipt ==
For the information about the service package included in the order to be displayed in the itinerary receipt, in the settings section '''System settings → Notifications and documents → Documents → Documents for aviation → Itinerary receipt''', by analogy with notification templates, it is possible to use a variable that includes a description of the service package, displayed in accordance with the template specified in the settings section '''System settings → Notifications and documents → Documents for avia → Documents for additional services''':

%SERVICE_PACK_INFO% (Information about the selected service package)

Payment Gateway API

2021-01-29T17:33:03Z

I shaletin: /* Format of requests/responses */

Payment Gateway API is a protocol for connecting payment gateways. This service allows you to connect any existing payment gateway with minimal time and resources using a single connection scheme. The advantage of the method is that the development of integration works on the customer side, which means that the customer plans the timing of integration independently and independently manages the resource for it.

=Connection procedure of Payment Gateway API module=

The Payment Gateway API module is optional. To connect to Websky via this protocol, contact the commercial department at connect@nemo.travel.

To connect the payment service using the method presented, the agency must:
# Contact the commercial department of Websky at connect@nemo.travel with an application to connect the product, sign documents to operate the service
# Create a ticket in the Websky project tracker for the service connection. You will get an access to "UniversalNemoPay" service in the "Access to payment methods" section (available only for Websky admins)
# Perform integration with Websky via Payment Gateway API protocol, using technical documentation on integration ([[Payment Gateway API#Technical documentation on integration with Payment Gateway API|Technical documentation on integration with Payment Gateway API]])
# Set up the payment method ([[Payment Gateway API#Setting up Payment Gateway in Websky|Set up Payment Gateway]]) and provide details for interaction between Websky and payment gateway in the ticket (set: URL, login, password) to complete the payment method setup by Websky technical support
# Test the connection before starting live operation
# Notify in the ticket that you are ready to switch to product mode. Provide service support contacts for accepting payments and test details for further service support

==Special features==
The service does not support fiscalization of payments according to the Federal Law 54.

==Setting up Payment Gateway in Websky==

# Under '''Finance and payments → Payment methods → Access to payment methods''' open access to UniversalNemoPay payment method for users/groups/companies (see [[Payment methods in Websky]] for details on configuring)
# In '''Finance and payments → Payment methods → Gateway management''' create a payment method "UniversalNemoPay" (see [[Payment methods in Websky]] for details on how to configure it)
# Open the "Requisites" section of the created payment method and set up access to the payment gateway (see [[Payment methods in Websky]] for more information on setting up):
#* "Client server URL for requests'' - the address of requests to access the Service, for example http://test.com/test
#* ''API login'' - access requisite to the payment gateway, issued by the payment gateway
#* ''Password'' - payment gateway access requisite, issued by the payment gateway
#* ''Currency'' - currency under the agreement with the payment gateway
#* ''Use two-stage payment'' - if the parameter is on, the scheme of requests with preauthorization will be used. If it is disabled - the scheme of requests without preauthorization.
#* ''Allow payment by Visa Electron and MasterCard Maestro cards only''.
#* ''Add locator to the beginning of payment identifier when transmitting to payment gateway'' - locator prefix will be added to orderNumber.
#* ''Display frame with payment page on the order info page'' - to pay in a frame on the order page without going to the payment gateway page
#* ''Frame height with payment page'' - set the frame height

=Technical documentation on integration with Payment Gateway API=

'''Terms used in this section:'''
* ''Websky system'' - Websky booking system,
*''Service'' - payment acceptance service.

==Query description==

{| class="wikitable"
! Request name !! Description !! Features
|-
| register.do || Order registration request (without preauthorization)|| -
|-
|registerPreAuth.do || Order registration request with preauthorization || -
|-
| deposit.do || Request to complete the payment of the order || -
|-
| reverse.do || Request to cancel the payment of the order || -
|-
| refund.do || Request for a refund of the order payment || -
|-
| getOrderStatusExtended.do || Extended order status request|| -
|-
|}

* Requests used for two-stage payment (with preauthorization): registerPreAuth.do, deposit.do.
* Requests used for one-stage payment (without preauthorization): register.do.
* Requests reverse.do, refund.do and getOrderStatusExtended.do can be used for any payment scheme.
* When a refund is required, the Websky system sends an order update request to the payment gateway. If the received order status is orderStatus=1, then a reverse.do request is sent, if orderStatus=2, then refund.do is sent.

==Procedure of interaction between the Websky System and the Service==

===Payment with preauthorization===
#When initiating a payment, Websky System sends an Order Registration Request registerPreAuth.do.
#Websky System redirects the user to the url that the Service specified in the response to the registration request to perform an acquiring transaction on the Service side.
#Websky System periodically sends a getOrderStatusExtended.do request to get the order status until the Service specifies 1 or 6 as the orderStatus when the errorCode value is zero. If orderStatus = 6, the payment procedure in the Websky System is terminated as unsuccessful. If orderStatus = 1, the procedure continues.
#Service redirects the customer back to the order page (returnUrl in the registerPreAuth.do request) in parallel with the completion of the transaction. As a result of the operation Websky System additionally sends a getOrderStatusExtended request to get the current payment status. If orderStatus = 6, the payment procedure in Websky System is terminated as unsuccessful. If orderStatus = 1, the procedure continues.
##Websky System performs the order processing.
##If the checkout is successful, Websky System initiates a deposit.do request to complete the acquiring operation on the Service side;
##If the checkout is unsuccessful, Websky will initiate a reverse.do request;
##Payment procedure completed.

===Payment without preauthorization===
#When payment is initiated, Websky sends a register.do request.
#Websky System redirects the user to the url that the Service specified in the response to the registration request to perform an acquiring operation on the Service side.
#Websky System periodically sends a getOrderStatusExtended.do request to get the order status until the Service specifies 2 or 6 as the orderStatus when the errorCode value is zero. If orderStatus = 6, the payment procedure in the Websky System is terminated as unsuccessful. If orderStatus = 2, the procedure continues.
#Service redirects the customer back to the order page (returnUrl in the register.do request) in parallel with the transaction completion. As a result of the transaction, Nemo System additionally sends a getOrderStatusExtended request to get the current payment status.
#If orderStatus=2 and errorCode=0, the Websky system executes the order.

===Refunds===
For a refund, Websky System sends getOrderStatusExtended.do.
*If the received orderStatus=1, Websky System sends a reverse.do request,
*If orderStatus=2, Websky sends a refund.do request.

==Format of requests/responses==

Universal API for connecting payment gateways is implemented with HTTP requests/responses using POST method.

* register.do
<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderNumber, amount, returnUrl, currency, description, language, jsonParams
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| amount || Payment amount || Payment amount in pennies (or cents)
|-
| returnUrl || Address to which you want the user to be redirected in case of successful payment. The value must be an absolute link. || Example: "http://test.com/universal_nemo_pay__after_authorisation?billing_id=111111111".
|-
| currency || Currency || Payment currency code ISO 4217.
|-
|| description || Free-form description of the order || Example: "Payment for order #586578 (1X96WD) from http://test.com".
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
| jsonParams || Block for transferring additional parameters of the merchant. || Example of data transferred by Websky: {"onlyMaestro": "false", "email": "test@mutelab.com", "phone": "79270099000"}
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: orderId, formUrl, errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| formUrl || URL of the payment form to which the client's browser should be redirected. || -
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the request. || -
|-
|}
</div></div>

* registerPreAuth.do
<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderNumber, amount, returnUrl, currency, description, language, jsonParams
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Store password obtained by connection
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| amount || Payment amount || Payment amount in pennies (or cents)
|-
| returnUrl || Address to which you want the user to be redirected in case of successful payment. The value must be an absolute link. || Example: "http://test.com/universal_nemo_pay__after_authorisation?billing_id=111111111".
|-
| currency || Currency || Payment currency code ISO 4217.
|-
|| description || Free-form description of the order || Example: "Payment for order #586578 (1X96WD) from http://test.com".
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
| jsonParams || Block for transferring additional parameters of the merchant. || Example of data transferred by Websky: {"onlyMaestro": "false", "email": "test@mutelab.com", "phone": "79270099000"}
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: orderId, formUrl, errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| formUrl || URL of the payment form to which the client's browser should be redirected. || -
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter in the "language" request. || -
|-
|}
</div></div>

* deposit.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId, amount.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || store login received when connecting
|-
| password || store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| amount || Payment amount in pennies (or cents)
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* reverse.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password ||Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
|- errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
|| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* refund.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* getOrderStatusExtended.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId, language, orderNumber.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage, orderStatus and cardAuthInfo(expiration, cardholderName, approvalCode, pan).
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
| orderStatus || Order status in the payment system. ||
* 0 - Order registered but not paid
* 1 - Preauthorized amount is locked (for two-stage payments)
* 2 - Full authorized amount of the order is passed
* 6 - Authorization denied
|-
| cardAuthInfo || Payment attribute tag. ||
* expiration - Card expiration date in the format YYYYMM.
* cardholderName - Name of the cardholder.
* approvalCode - Payment authorization code. Fixed length field (6 characters), can contain numbers and Latin letters.
* pan - Masked number of the card which was used for payment.
|-
|}
</div></div>

=See also=
*[[Payment gateway]]
*[[Payment methods in Websky]]

Payment Gateway API

2021-01-29T17:29:47Z

I shaletin: Created page with "Payment Gateway API is a protocol for connecting payment gateways. This service allows you to connect any existing payment gateway with minimal time and resources using a sing..."

Payment Gateway API is a protocol for connecting payment gateways. This service allows you to connect any existing payment gateway with minimal time and resources using a single connection scheme. The advantage of the method is that the development of integration works on the customer side, which means that the customer plans the timing of integration independently and independently manages the resource for it.

=Connection procedure of Payment Gateway API module=

The Payment Gateway API module is optional. To connect to Websky via this protocol, contact the commercial department at connect@nemo.travel.

To connect the payment service using the method presented, the agency must:
# Contact the commercial department of Websky at connect@nemo.travel with an application to connect the product, sign documents to operate the service
# Create a ticket in the Websky project tracker for the service connection. You will get an access to "UniversalNemoPay" service in the "Access to payment methods" section (available only for Websky admins)
# Perform integration with Websky via Payment Gateway API protocol, using technical documentation on integration ([[Payment Gateway API#Technical documentation on integration with Payment Gateway API|Technical documentation on integration with Payment Gateway API]])
# Set up the payment method ([[Payment Gateway API#Setting up Payment Gateway in Websky|Set up Payment Gateway]]) and provide details for interaction between Websky and payment gateway in the ticket (set: URL, login, password) to complete the payment method setup by Websky technical support
# Test the connection before starting live operation
# Notify in the ticket that you are ready to switch to product mode. Provide service support contacts for accepting payments and test details for further service support

==Special features==
The service does not support fiscalization of payments according to the Federal Law 54.

==Setting up Payment Gateway in Websky==

# Under '''Finance and payments → Payment methods → Access to payment methods''' open access to UniversalNemoPay payment method for users/groups/companies (see [[Payment methods in Websky]] for details on configuring)
# In '''Finance and payments → Payment methods → Gateway management''' create a payment method "UniversalNemoPay" (see [[Payment methods in Websky]] for details on how to configure it)
# Open the "Requisites" section of the created payment method and set up access to the payment gateway (see [[Payment methods in Websky]] for more information on setting up):
#* "Client server URL for requests'' - the address of requests to access the Service, for example http://test.com/test
#* ''API login'' - access requisite to the payment gateway, issued by the payment gateway
#* ''Password'' - payment gateway access requisite, issued by the payment gateway
#* ''Currency'' - currency under the agreement with the payment gateway
#* ''Use two-stage payment'' - if the parameter is on, the scheme of requests with preauthorization will be used. If it is disabled - the scheme of requests without preauthorization.
#* ''Allow payment by Visa Electron and MasterCard Maestro cards only''.
#* ''Add locator to the beginning of payment identifier when transmitting to payment gateway'' - locator prefix will be added to orderNumber.
#* ''Display frame with payment page on the order info page'' - to pay in a frame on the order page without going to the payment gateway page
#* ''Frame height with payment page'' - set the frame height

=Technical documentation on integration with Payment Gateway API=

'''Terms used in this section:'''
* ''Websky system'' - Websky booking system,
*''Service'' - payment acceptance service.

==Query description==

{| class="wikitable"
! Request name !! Description !! Features
|-
| register.do || Order registration request (without preauthorization)|| -
|-
|registerPreAuth.do || Order registration request with preauthorization || -
|-
| deposit.do || Request to complete the payment of the order || -
|-
| reverse.do || Request to cancel the payment of the order || -
|-
| refund.do || Request for a refund of the order payment || -
|-
| getOrderStatusExtended.do || Extended order status request|| -
|-
|}

* Requests used for two-stage payment (with preauthorization): registerPreAuth.do, deposit.do.
* Requests used for one-stage payment (without preauthorization): register.do.
* Requests reverse.do, refund.do and getOrderStatusExtended.do can be used for any payment scheme.
* When a refund is required, the Websky system sends an order update request to the payment gateway. If the received order status is orderStatus=1, then a reverse.do request is sent, if orderStatus=2, then refund.do is sent.

==Procedure of interaction between the Websky System and the Service==

===Payment with preauthorization===
#When initiating a payment, Websky System sends an Order Registration Request registerPreAuth.do.
#Websky System redirects the user to the url that the Service specified in the response to the registration request to perform an acquiring transaction on the Service side.
#Websky System periodically sends a getOrderStatusExtended.do request to get the order status until the Service specifies 1 or 6 as the orderStatus when the errorCode value is zero. If orderStatus = 6, the payment procedure in the Websky System is terminated as unsuccessful. If orderStatus = 1, the procedure continues.
#Service redirects the customer back to the order page (returnUrl in the registerPreAuth.do request) in parallel with the completion of the transaction. As a result of the operation Websky System additionally sends a getOrderStatusExtended request to get the current payment status. If orderStatus = 6, the payment procedure in Websky System is terminated as unsuccessful. If orderStatus = 1, the procedure continues.
##Websky System performs the order processing.
##If the checkout is successful, Websky System initiates a deposit.do request to complete the acquiring operation on the Service side;
##If the checkout is unsuccessful, Websky will initiate a reverse.do request;
##Payment procedure completed.

===Payment without preauthorization===
#When payment is initiated, Websky sends a register.do request.
#Websky System redirects the user to the url that the Service specified in the response to the registration request to perform an acquiring operation on the Service side.
#Websky System periodically sends a getOrderStatusExtended.do request to get the order status until the Service specifies 2 or 6 as the orderStatus when the errorCode value is zero. If orderStatus = 6, the payment procedure in the Websky System is terminated as unsuccessful. If orderStatus = 2, the procedure continues.
#Service redirects the customer back to the order page (returnUrl in the register.do request) in parallel with the transaction completion. As a result of the transaction, Nemo System additionally sends a getOrderStatusExtended request to get the current payment status.
#If orderStatus=2 and errorCode=0, the Websky system executes the order.

===Refunds===
For a refund, Websky System sends getOrderStatusExtended.do.
*If the received orderStatus=1, Websky System sends a reverse.do request,
*If orderStatus=2, Websky sends a refund.do request.

==Format of requests/responses==

Universal API for connecting payment gateways is implemented with HTTP requests/responses using POST method.

* register.do
<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderNumber, amount, returnUrl, currency, description, language, jsonParams
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| amount || Payment amount || Payment amount in pennies (or cents)
|-
| returnUrl || Address to which you want the user to be redirected in case of successful payment. The value must be an absolute link. || Example: "http://test.com/universal_nemo_pay__after_authorisation?billing_id=111111111".
|-
| currency || Currency || Payment currency code ISO 4217.
|-
|| description || Free-form description of the order || Example: "Payment for order #586578 (1X96WD) from http://test.com".
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
| jsonParams || Block for transferring additional parameters of the merchant. || Example of data transferred by Websky: {"onlyMaestro": "false", "email": "test@mutelab.com", "phone": "79270099000"}
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: orderId, formUrl, errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| formUrl || URL of the payment form to which the client's browser should be redirected. || -
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the request. || -
|-
|}
</div></div>

* registerPreAuth.do
<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderNumber, amount, returnUrl, currency, description, language, jsonParams
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Store password obtained by connection
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| amount || Payment amount || Payment amount in pennies (or cents)
|-
| returnUrl || Address to which you want the user to be redirected in case of successful payment. The value must be an absolute link. || Example: "http://test.com/universal_nemo_pay__after_authorisation?billing_id=111111111".
|-
| currency || Currency || Payment currency code ISO 4217.
|-
|| description || Free-form description of the order || Example: "Payment for order #586578 (1X96WD) from http://test.com".
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
| jsonParams || Block for transferring additional parameters of the merchant. || Example of data transferred by Websky: {"onlyMaestro": "false", "email": "test@mutelab.com", "phone": "79270099000"}
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: orderId, formUrl, errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| formUrl || URL of the payment form to which the client's browser should be redirected. || -
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter in the "language" request. || -
|-
|}
</div></div>

* deposit.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId, amount.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || store login received when connecting
|-
| password || store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| amount || Payment amount in pennies (or cents)
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* reverse.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password ||Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !!! Description !!! Features
|-
|- errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
|| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* refund.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
|}
</div></div>

* getOrderStatusExtended.do

<div class="toccolours mw-collapsible mw-collapsed">
Request parameters: userName, password, orderId, language, orderNumber.
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| userName || API login || Store login received when connecting
|-
| password || Password || Store password obtained by connection
|-
| orderId || Order number in the payment system. Unique within the system. || -
|-
| orderNumber || Order number (identifier) in the store system, unique for each store within the system || Billing number
|-
| language || Language in ISO 639-1 encoding. || Example: "ru".
|-
|}
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
Response parameters: errorCode, errorMessage, orderStatus and cardAuthInfo(expiration, cardholderName, approvalCode, pan).
<div class="mw-collapsible-content">
{| class="wikitable"
! Parameter name !! Description !! Features
|-
| errorCode || Error code. || Any value other than "0" is treated by our system as an unsuccessful response.
|-
| errorMessage || Error description in the language passed in the parameter language in the query. || -
|-
| orderStatus || Order status in the payment system. ||
* 0 - Order registered but not paid
* 1 - Preauthorized amount is locked (for two-stage payments)
* 2 - Full authorized amount of the order is passed
* 6 - Authorization denied
|-
| cardAuthInfo || Payment attribute tag. ||
* expiration - Card expiration date in the format YYYYMM.
* cardholderName - Name of the cardholder.
* approvalCode - Payment authorization code. Fixed length field (6 characters), can contain numbers and Latin letters.
* pan - Masked number of the card which was used for payment.
|-
|}
</div></div>

=See also=
*[[Payment gateway]]
*[[Payment methods in Websky]]

SITA Gabriel

2021-01-29T07:26:04Z

I shaletin: Created page with "'''SITA Gabriel''' is a global distribution system developed in the early 1970s by SITA, the world leader in airline communications services. == Description == SITA Gabriel..."

'''SITA Gabriel''' is a global distribution system developed in the early 1970s by SITA, the world leader in airline communications services.

== Description ==

SITA Gabriel is a comprehensive passenger bookings and seat availability management solution for airlines.

SITA Gabriel has interactive connections with all the major GDSs, including Abacus, Amadeus, Galileo, Sabre, Worldspan and Russian systems Sirena Travel and Sirin. Real-time information about availability of seats in these GDSs allows the airline to interact with travel agencies worldwide.

As of today, there are about 150 airline companies in the world that use the system.

== General capabilities ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and general'''
<div class="mw-collapsible-content">
* Search by nearest dates - conditional[[#FAQ for GDS/API SITA Gabriel|<sup>[1]</sup>]]
* Search by public + private rates
* Search for private fares
* Search by schedule
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From requisites/settings
** Adding a passenger title
* Additional operations with requisites/settings
** Reading fare rules
** Checking availability
** Updating the price
** Getting the currency rate
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking updating (synchronization)
** Importing bookings by PNR locator
** Modifying passenger name and patronymic
** Modification of bookings content
** Adding content
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Ticketing on airline stock [[#FAQ on GDS/GDS/API SITA Gabriel|<sup>[2]</sup>]]
* Airline server .NET operations/requests
** Ticketing for all bookings
** Additional ticketing for all passengers
** Filling in airline commission at ticketing
** Commission for passenger type
** Filling in endorsements
** Voiding
</div>
</div>

== Connecting to SITA Gabriel GDS in Websky==
# In the Websky system, it is currently possible to connect to SITA Gabriel. In order to do that the agency needs to
#* Conclude a contract with the airline, in the process of which you should '''request requisites for online connection''' to the Gabriel system, and receive the '''validator'''.
# After the agent contacts the airline, an agency office is created in the SITA system.
# When the office number becomes available, Websky developers create a certificate for that office and send it to the airline (If the airline makes the certificate themselves, Websky developers will need the certificate the private key they created it with as well).
# The airline's representatives send the certificate to SITA, and SITA developers download the certificate (either in a test or immediately in a production environment) and provide the airline with a full set of agent requisites, namely:
#* Ticketing validator
#* OFFC (Office)
#* Agent SI (Agent Sign-In) - username/password/user group
#* TerminalID
#* TerminalPassword
#* IATA code of the city the office is located in
#* AXI RequestorID - necessary for billing of flights
#* Shopping RequestorID (If search is also needed)
# The airline sends these data to Websky developers, who create a requisite package for the agency in Websky.

=== Connection features ===

# If the airline has not bought a native search in SITA Gabriel, its emulation in Websky is implemented through multiplication of the flights of this airline from other GDS in SITA Gabriel packages - depending on which GDS is already used by the agency in Websky. The booking and issuing of the replicated flights is performed in Gabriel.
# After you set up your account package in Websky you need to create a correct [[https://docs.websky.tech/websky/Search_results_mixer_(Air_tickets)|mixer rule]] (to route airline flights to a specific package).

== Features of working with SITA Gabriel in Websky ==

*In Websky [[Booking form (Airline tickets)|booking form]] prevents booking errors related to violation of SITA Gabriel limitations on the number of characters allocated for the passenger's last name:
The maximum number of characters for the last name and first name in total is 40.

*Tickets via SITA Gabriel Web Services are issued exclusively with manual fare calculation and manual mask.

'''Attention!''' SITA does not allow you to set TimeLimit less than 15 minutes from the current time.

== Frequently Asked Questions on Interaction with SITA Gabriel GDS ==
# Unfortunately it is hard to call the search for Nearest Dates in SITA Gabriel fully functional, because it does not return all the necessary information about the flight, at least as of 12/02/2013.
# Gabriel is an inventory system, so the statement is on the airline's stock by system definition.
# Technically, SITA Gabriel supports both types of GDS processing, but not all airlines are authorized to use this functionality there.

== Possible errors when interacting with GDS SITA Gabriel ==
=== Search errors ===
Supplier-independent:
{| class="wikitable"
|-
! align="center" width="50%"|«SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR»
|There is a parallel change of PNR in the work with the booking. In this case you need to start the operation anew.
|-
! align="center" width="50%"|«Invalid search request object»
|This error occurs when an invalid search result is accessed. Possible causes:
# incorrect search link;
# search result may be out of date.
|-
|}

=== Errors when booking ===
{| class="wikitable"
|-
! align="center" width="50%"|«579 - NEED TEXT»
|For some types of power supply, for example (SPML), it is required to specify an additional text description.
|-
! align="center" width="50%"|«010 - TIME»
|An error occurs when the timelimit set at the time of booking takes the value of already elapsed time.
|-
|}

=== Ticketing errors ===
{| class="wikitable"
|-
! align="center" width="50%"|«TICKET ALLOCATION DEPLETED -CONTACT CARRIER»
|Ticket stock ran out. The agent must contact the airline's credit control group to replenish the stock.
|-
|-
! align="center" width="50%"|«TKT092 TICKET ALLOCATION STOPPED-CTC CARRIER»
|The stock of forms on the validator has run out. The agent must contact the credit control team to replenish the stock.
|-
|}

== Contact information ==

* [https://secure.sita.aero/ SITA official website]

== See also ==
* [[GDS]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[Sirena Travel]]
* [[Amadeus]]
* [[Search 2.0]]

API Travelfusion

2021-01-29T06:50:44Z

I shaletin: /* Related settings to get started in Websky */

Travelfusion is one of the leading content aggregators for OTA, providing direct access to the resources of numerous air, rail and hotel suppliers. In addition to its direct functions, GDS has its own payment tool for mutual settlements (TF.Pay), as well as ready-to-use services (both for B2B and B2C models) for effective business management. It specializes mainly in low-cost suppliers.

The company was founded in 2000. Travelfusion is headquartered in London, UK, and has offices in Shanghai, China.
Resource: about 220 airlines and rail carriers. A full list of supported suppliers is available on Travelfusion's official website: [https://www.travelfusion.com/corporate/supplier]
Distribution: predominantly Europe.

== The process of connecting to Travelfusion at Websky ==

# In the Websky system, you can currently implement a connection to Travelfusion only to work with the "Air tickets" component. To do this, the agency needs to contact the Travelfusion sales department and sign a contract. You should also specify in the letter that the agency is going to work with Travelfusion through Websky.
# After signing the contract, the account manager sends the agent a file with requisites (username and password) to connect (Travelfusion Welcome Pack) and a checklist form to fill out.
# The agency provides the details to Websky tech support through a ticket in the project tracker. The tech support staff helps fill out the questionnaire, and the agent sends it to Travelfusion.
# After Travelfusion officially confirms and authorizes you to get started, the tech support team starts and configures the Websky requisite package for the agent.

== Related settings to get started in Websky ==
After completing the requisites configuration, the agent also needs to make the following settings:
# Enter the necessary rules for the companies to be billed through the Travelfusion Connector into the pricing file. Commission values are not transmitted to the provider when they are discharged, so you can specify zero commission for all such airlines and assign your agency fees if necessary. (See [[Pricing (air tickets)]])
# Add an itinerary receipt template for the supplier Travelfusion (see [[Itinerary receipt]]).
# Check that all fields are filled in under '''Avia Settings → Agency Profile''' in the '''Nemo Connect''' settings.
# If you wish, you can implement the output of additional information text in a pop-up window (next to the checkbox agreeing to the booking rules and the public offer on the order page in the same block). You can enter the text in the settings section "Site management" → "Domains and protocols" → "Additional transport rules". To display a pseudo-reference to the popup with this text you need to change the value of the language variable ''new-passinfo-footer__agreementText'' (see [[Localization]]) by adding html code: <br>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
<u>'''Example'''</u>
<div class="mw-collapsible-content">
I have read and agree to <a href="/booking__policy" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Booking Rules'}">booking rules</a>, <a href="/booking__additional_flight_rules" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'title you need'}">rules for ancillary services</a>, <a href="[%-faresurl-%]" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Rate Terms'}">the fare rules</a> and <a href="/booking__policypd" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title:'Rights of the subject of personal data'}">the rights of the subject of personal data</a>. I agree and confirm the consent of third parties, specified by me in the booking, to the processing of personal data, including their transfer to third parties providing or servicing the transportation, as well as the cross-border transfer of personal data.
</div>
</div>

== Ordering process in Websky ==

After selecting a Travelfusion flight and filling in passenger information on the booking page in Websky, the customer clicks the "Book" button. In this case the booking is not created in the airline. The booking object is created only in the Travelfusion system itself, but no seats are actually reserved, and passenger data is not transmitted to the airline.
After successful payment, Websky launches a ticketing request (at this point the airline is already creating a booking). But even after successful processing of the request, the order page will initially display the "Tickets are being processed" inscription, since in the response to the statement request the provider initially does not send ticket numbers, since the airline booking is not confirmed immediately. Websky then automatically updates the order (at a frequency of once every 7 minutes), and during the update already receives the ticket number from the supplier. The itinerary receipt will be automatically sent to the customer's email.
<br>The text of the ''Tickets are being issued'' message can be changed in the localization, via the ''ticketed_without_tickets'' language variable.

==Features of Travelfusion==

* Travelfusion requires an agent's personal account on the side in order to debit the creation of bookings with the airline.
* Due to Travelfusion's focus on low-cost suppliers, airline bookings are only created when they are ticketed in Websky. When booking in Websky, a pseudo-booking is created on the Travelfusion side, nothing is created on the airline side and no seats are blocked.

'''Attention!''' Because of this, before the ticketing in Websky, there is no guarantee that the booking will be successfully made. In the case of a situation where a booking is made, payment passed, and there is no ticketing after launch, the only way to perform ticketing for the reservation is to reissue the entire booking, starting with a search.

Also, due to Travelfusion's focus on low-cost suppliers, there may not be a ticket after ticketing in Websky, often Travelfusion has a booking code in the airline system with which passengers need to go to the airline site for ticketing.
Once a booking is made in the airline's system, Travelfusion does not synchronize it; accordingly, Websky does not receive information about flight changes, flight changes need to be tracked by the passenger.
* Due to the specifics of Travelfusion receiving data from the airlines, at different stages of the purchase (search, updating and booking in Websky) price of the flight and booking can be different - usually due to rounding errors in calculating the total amount on the side of Travelfusion and Websky.
* It is obligatory to enter the client's contact information, as passengers might have problems with the check-in for the flight if they do not have this information. Information important for the agent will be sent to these contact details.
* Websky returns problem statuses received from Travelfusion. In case of problem statuses, the agent should follow the instructions and contact Travelfusion technical support.
* Travelfusion has a protection against duplicate bookings, in such cases an error is returned. If an error occurs, no new booking will be created in Websky.
* Due to the frequent updating of requirements for agents to connect to Travelfusion, the connection process can be lengthy.

== Features of working with Travelfusion in Websky ==
# Currently, Websky allows you to work with Travelfusion only with TF Prepay Method: the agency opens a personal account in Travelfusion for a certain amount, and when the customer makes a booking on the site, the price of the flight is deducted from the agent's balance to the Travelfusion account. Then Travelfusion independently transfers the funds to the account of the airline. '''Attention!''' Payment directly to the airline is not possible at this time with the customer's card.
# '''Attention!''' Currently Websky does not implement:
#* search by nearest dates (planned in the future);
#* search by nearest airports (planned in the future);
#* sales of optional services (baggage, meals and seat selection);
#* search by complex route (ST) - not supported by Travelfusion;
#* supplementing and modifying bookings (passport and visa information, loyalty card) - not supported by Travelfusion;
#* cancellation of unissued bookings and updating of issued bookings - not supported by Travelfusion;
#* voiding, exchanging and refunding bookings (not supported by Travelfusion). The customer must contact the airline directly for this.
#All fares are treated as non-refundable.
# Airlines send their own confirmation letter (i.e. their itinerary receipt) to the customer's e-mail address that was provided at the time of booking. This itinerary receipt will show the net price of the flight, i.e. the customer will see the price without agency extra charges.
# If the flight/schedule is changed after the booking is issued, the changed data is not displayed in Travelfusion, i.e. synchronization after the booking is not possible, and this data will only be available at the airline directly.
# The default booking page for a low-cost flight displays ''Attention! This flight is provided by a low-cost airline. Meals are not available on board! The text of this message can be changed in the localization, by the ''no_meal_for_LowCost'' language variable. You can completely hide the output of this message by using css styles.
# '''Currently it is enough to specify the deposit currency in the requisites to the GDS, in the package it is optional.'''
# The base price of flights from Travelfusion when searching can come in any currency - it depends on the airline, and there can be prices in different currencies (fare in euros, and fares in dollars, for example) for the same flight in the supplier's response. Websky then requests the Travelfusion exchange rates from their system and converts the entire cost of the flight according to that rate into the currency of the requisition. Translation of prices on the agent site into other currencies will be according to the rates set in the agency currency directory ('''System Settings → Currencies and rates → Directory of currencies and rates, see [[Currency]]. [[Currencies]]).
# Travelfusion can send negative tax values (i.e. discount rates) or no taxes at all, or the taxes can be already included in the fare.
# Supplier side booking time limit is 15 minutes and can't be longer.
# Travelfusion does not allow booking a separate seat for an infant. Warnings about this are displayed on the results page and on the booking page in the form of the caption: ''Booking a separate seat for an infant is not allowed by the carrier.'' You can change the warning text on the results page by setting the ''flightsGroup__flightWarnings__insBookingNotAllowedBySupplier'' variable translation in the localization settings, on the booking page - ''ins_booking_not_allowed_by_supplier''.
# '''As required by Travelfusion, you must be sure to set up routing according to their schedule.''' See [[Search request filters (Air tickets)]]
# Along with the address information from '''Avia Settings → Agency Profile''' in the '''Nemo Connect''' settings, the name of the agency in Nemo Connect is passed to Travelfusion as the company name. To change the name of the company transferred to Travelfusion, you must change the name of the agency in the Nemo Connect settings. To do this, you need to create a request to the technical support team: [http://helpdesk.nemo.travel helpdesk.nemo.travel].
# One of the requirements of Travelfusion is to have the <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">PointOfSale </syntaxhighlight> parameter in StartRouting and ProcessTerms requests to the provider. <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">PointOfSale </syntaxhighlight> is for certification and correct operation. The value of this parameter is changed in the ''Nemo Connect'' settings in the ''Avia Settings → Agency Profile → Agency Country Code'' field.
# The ProcessTerms request uses fields:
#* Company name - in the XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Company</syntaxhighlight>
#* Office - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Flat</syntaxhighlight>
#* House - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">BuildingNumber</syntaxhighlight>
#* Street - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Street</syntaxhighlight>
#* City - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">City</syntaxhighlight>
#* Region - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Province</syntaxhighlight>
#* Postal code - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Postcode</syntaxhighlight>
#* Country - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">CountryCode</syntaxhighlight>

You can change the values of these parameters in the settings of the '''Websky adminitration panel''' in '''Account Management → Agents and Users → Company Profiles'''.

== Possible errors and their causes ==

* '''Your branch cannot perform booking through the TF.Payment Service''' - means that the Travelfusion account is not activated.
* '''Supplier does not support payments through the TF.Payment Service''' - the airline does not support the TF.Pay payment method. Disabling the issuance of flights of this airline is possible on the side of Travelfusion, by contacting their technical support. <br>
* '''Temporary supplier error''' - problems on the side of the supplier. It is recommended to repeat the action later. If the error continues to occur frequently, you should contact Travelfusion Technical Support. <br>
* '''The supplier is too busy''' - similarly, temporary problems on the supplier side due to a high load on the Travelfusion system.
* '''Internal server error''' - an internal error on the Travelfusion servers.
* '''RequestValidationError''' - agency profile (address and contact information) is not filled in the Nemo Connect admin panel.
* '''Title missing''' - the ''Automatically add passenger's title'' setting is not enabled in the Travelfusion package booking requisites in the Nemo Connect administration panel.
* '''Address postal code is required for this journey''' - no address information has been entered in '''Avia Settings → Agency Profile''' in the Nemo Connect settings.

== Contact Information ==
* [https://www.travelfusion.com Official Travelfusion website]
* [https://www.travelfusion.com/corporate/page/contact-us Contacts for inquiries]

== See also ==
* [[GDS]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[Sirena Travel]]
* [[Amadeus]]
* [[SITA Gabriel]]

API Travelfusion

2021-01-29T06:50:13Z

I shaletin: Created page with "Travelfusion is one of the leading content aggregators for OTA, providing direct access to the resources of numerous air, rail and hotel suppliers. In addition to its direct f..."

Travelfusion is one of the leading content aggregators for OTA, providing direct access to the resources of numerous air, rail and hotel suppliers. In addition to its direct functions, GDS has its own payment tool for mutual settlements (TF.Pay), as well as ready-to-use services (both for B2B and B2C models) for effective business management. It specializes mainly in low-cost suppliers.

The company was founded in 2000. Travelfusion is headquartered in London, UK, and has offices in Shanghai, China.
Resource: about 220 airlines and rail carriers. A full list of supported suppliers is available on Travelfusion's official website: [https://www.travelfusion.com/corporate/supplier]
Distribution: predominantly Europe.

== The process of connecting to Travelfusion at Websky ==

# In the Websky system, you can currently implement a connection to Travelfusion only to work with the "Air tickets" component. To do this, the agency needs to contact the Travelfusion sales department and sign a contract. You should also specify in the letter that the agency is going to work with Travelfusion through Websky.
# After signing the contract, the account manager sends the agent a file with requisites (username and password) to connect (Travelfusion Welcome Pack) and a checklist form to fill out.
# The agency provides the details to Websky tech support through a ticket in the project tracker. The tech support staff helps fill out the questionnaire, and the agent sends it to Travelfusion.
# After Travelfusion officially confirms and authorizes you to get started, the tech support team starts and configures the Websky requisite package for the agent.

== Related settings to get started in Websky ==
After completing the requisites configuration, the agent also needs to make the following settings:
# Enter the necessary rules for the companies to be billed through the Travelfusion Connector into the pricing file. Commission values are not transmitted to the provider when they are discharged, so you can specify zero commission for all such airlines and assign your agency fees if necessary. (See [[Pricing (Air tickets)]])
# Add an itinerary receipt template for the supplier Travelfusion (see [[Itinerary receipt]]).
# Check that all fields are filled in under '''Avia Settings → Agency Profile''' in the '''Nemo Connect''' settings.
# If you wish, you can implement the output of additional information text in a pop-up window (next to the checkbox agreeing to the booking rules and the public offer on the order page in the same block). You can enter the text in the settings section "Site management" → "Domains and protocols" → "Additional transport rules". To display a pseudo-reference to the popup with this text you need to change the value of the language variable ''new-passinfo-footer__agreementText'' (see [[Localization]]) by adding html code: <br>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
<u>'''Example'''</u>
<div class="mw-collapsible-content">
I have read and agree to <a href="/booking__policy" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Booking Rules'}">booking rules</a>, <a href="/booking__additional_flight_rules" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'title you need'}">rules for ancillary services</a>, <a href="[%-faresurl-%]" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Rate Terms'}">the fare rules</a> and <a href="/booking__policypd" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title:'Rights of the subject of personal data'}">the rights of the subject of personal data</a>. I agree and confirm the consent of third parties, specified by me in the booking, to the processing of personal data, including their transfer to third parties providing or servicing the transportation, as well as the cross-border transfer of personal data.
</div>
</div>

== Ordering process in Websky ==

After selecting a Travelfusion flight and filling in passenger information on the booking page in Websky, the customer clicks the "Book" button. In this case the booking is not created in the airline. The booking object is created only in the Travelfusion system itself, but no seats are actually reserved, and passenger data is not transmitted to the airline.
After successful payment, Websky launches a ticketing request (at this point the airline is already creating a booking). But even after successful processing of the request, the order page will initially display the "Tickets are being processed" inscription, since in the response to the statement request the provider initially does not send ticket numbers, since the airline booking is not confirmed immediately. Websky then automatically updates the order (at a frequency of once every 7 minutes), and during the update already receives the ticket number from the supplier. The itinerary receipt will be automatically sent to the customer's email.
<br>The text of the ''Tickets are being issued'' message can be changed in the localization, via the ''ticketed_without_tickets'' language variable.

==Features of Travelfusion==

* Travelfusion requires an agent's personal account on the side in order to debit the creation of bookings with the airline.
* Due to Travelfusion's focus on low-cost suppliers, airline bookings are only created when they are ticketed in Websky. When booking in Websky, a pseudo-booking is created on the Travelfusion side, nothing is created on the airline side and no seats are blocked.

'''Attention!''' Because of this, before the ticketing in Websky, there is no guarantee that the booking will be successfully made. In the case of a situation where a booking is made, payment passed, and there is no ticketing after launch, the only way to perform ticketing for the reservation is to reissue the entire booking, starting with a search.

Also, due to Travelfusion's focus on low-cost suppliers, there may not be a ticket after ticketing in Websky, often Travelfusion has a booking code in the airline system with which passengers need to go to the airline site for ticketing.
Once a booking is made in the airline's system, Travelfusion does not synchronize it; accordingly, Websky does not receive information about flight changes, flight changes need to be tracked by the passenger.
* Due to the specifics of Travelfusion receiving data from the airlines, at different stages of the purchase (search, updating and booking in Websky) price of the flight and booking can be different - usually due to rounding errors in calculating the total amount on the side of Travelfusion and Websky.
* It is obligatory to enter the client's contact information, as passengers might have problems with the check-in for the flight if they do not have this information. Information important for the agent will be sent to these contact details.
* Websky returns problem statuses received from Travelfusion. In case of problem statuses, the agent should follow the instructions and contact Travelfusion technical support.
* Travelfusion has a protection against duplicate bookings, in such cases an error is returned. If an error occurs, no new booking will be created in Websky.
* Due to the frequent updating of requirements for agents to connect to Travelfusion, the connection process can be lengthy.

== Features of working with Travelfusion in Websky ==
# Currently, Websky allows you to work with Travelfusion only with TF Prepay Method: the agency opens a personal account in Travelfusion for a certain amount, and when the customer makes a booking on the site, the price of the flight is deducted from the agent's balance to the Travelfusion account. Then Travelfusion independently transfers the funds to the account of the airline. '''Attention!''' Payment directly to the airline is not possible at this time with the customer's card.
# '''Attention!''' Currently Websky does not implement:
#* search by nearest dates (planned in the future);
#* search by nearest airports (planned in the future);
#* sales of optional services (baggage, meals and seat selection);
#* search by complex route (ST) - not supported by Travelfusion;
#* supplementing and modifying bookings (passport and visa information, loyalty card) - not supported by Travelfusion;
#* cancellation of unissued bookings and updating of issued bookings - not supported by Travelfusion;
#* voiding, exchanging and refunding bookings (not supported by Travelfusion). The customer must contact the airline directly for this.
#All fares are treated as non-refundable.
# Airlines send their own confirmation letter (i.e. their itinerary receipt) to the customer's e-mail address that was provided at the time of booking. This itinerary receipt will show the net price of the flight, i.e. the customer will see the price without agency extra charges.
# If the flight/schedule is changed after the booking is issued, the changed data is not displayed in Travelfusion, i.e. synchronization after the booking is not possible, and this data will only be available at the airline directly.
# The default booking page for a low-cost flight displays ''Attention! This flight is provided by a low-cost airline. Meals are not available on board! The text of this message can be changed in the localization, by the ''no_meal_for_LowCost'' language variable. You can completely hide the output of this message by using css styles.
# '''Currently it is enough to specify the deposit currency in the requisites to the GDS, in the package it is optional.'''
# The base price of flights from Travelfusion when searching can come in any currency - it depends on the airline, and there can be prices in different currencies (fare in euros, and fares in dollars, for example) for the same flight in the supplier's response. Websky then requests the Travelfusion exchange rates from their system and converts the entire cost of the flight according to that rate into the currency of the requisition. Translation of prices on the agent site into other currencies will be according to the rates set in the agency currency directory ('''System Settings → Currencies and rates → Directory of currencies and rates, see [[Currency]]. [[Currencies]]).
# Travelfusion can send negative tax values (i.e. discount rates) or no taxes at all, or the taxes can be already included in the fare.
# Supplier side booking time limit is 15 minutes and can't be longer.
# Travelfusion does not allow booking a separate seat for an infant. Warnings about this are displayed on the results page and on the booking page in the form of the caption: ''Booking a separate seat for an infant is not allowed by the carrier.'' You can change the warning text on the results page by setting the ''flightsGroup__flightWarnings__insBookingNotAllowedBySupplier'' variable translation in the localization settings, on the booking page - ''ins_booking_not_allowed_by_supplier''.
# '''As required by Travelfusion, you must be sure to set up routing according to their schedule.''' See [[Search request filters (Air tickets)]]
# Along with the address information from '''Avia Settings → Agency Profile''' in the '''Nemo Connect''' settings, the name of the agency in Nemo Connect is passed to Travelfusion as the company name. To change the name of the company transferred to Travelfusion, you must change the name of the agency in the Nemo Connect settings. To do this, you need to create a request to the technical support team: [http://helpdesk.nemo.travel helpdesk.nemo.travel].
# One of the requirements of Travelfusion is to have the <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">PointOfSale </syntaxhighlight> parameter in StartRouting and ProcessTerms requests to the provider. <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">PointOfSale </syntaxhighlight> is for certification and correct operation. The value of this parameter is changed in the ''Nemo Connect'' settings in the ''Avia Settings → Agency Profile → Agency Country Code'' field.
# The ProcessTerms request uses fields:
#* Company name - in the XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Company</syntaxhighlight>
#* Office - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Flat</syntaxhighlight>
#* House - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">BuildingNumber</syntaxhighlight>
#* Street - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Street</syntaxhighlight>
#* City - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">City</syntaxhighlight>
#* Region - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Province</syntaxhighlight>
#* Postal code - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">Postcode</syntaxhighlight>
#* Country - in XML field <syntaxhighlight lang="text" enclose="none" style="font-size: 1.2em; padding: 0 3px; background: #F0F0F0; border: 1px dashed #2F6FAB;">CountryCode</syntaxhighlight>

You can change the values of these parameters in the settings of the '''Websky adminitration panel''' in '''Account Management → Agents and Users → Company Profiles'''.

== Possible errors and their causes ==

* '''Your branch cannot perform booking through the TF.Payment Service''' - means that the Travelfusion account is not activated.
* '''Supplier does not support payments through the TF.Payment Service''' - the airline does not support the TF.Pay payment method. Disabling the issuance of flights of this airline is possible on the side of Travelfusion, by contacting their technical support. <br>
* '''Temporary supplier error''' - problems on the side of the supplier. It is recommended to repeat the action later. If the error continues to occur frequently, you should contact Travelfusion Technical Support. <br>
* '''The supplier is too busy''' - similarly, temporary problems on the supplier side due to a high load on the Travelfusion system.
* '''Internal server error''' - an internal error on the Travelfusion servers.
* '''RequestValidationError''' - agency profile (address and contact information) is not filled in the Nemo Connect admin panel.
* '''Title missing''' - the ''Automatically add passenger's title'' setting is not enabled in the Travelfusion package booking requisites in the Nemo Connect administration panel.
* '''Address postal code is required for this journey''' - no address information has been entered in '''Avia Settings → Agency Profile''' in the Nemo Connect settings.

== Contact Information ==
* [https://www.travelfusion.com Official Travelfusion website]
* [https://www.travelfusion.com/corporate/page/contact-us Contacts for inquiries]

== See also ==
* [[GDS]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[Sirena Travel]]
* [[Amadeus]]
* [[SITA Gabriel]]

Passenger Name Record (PNR)

2021-01-28T19:18:12Z

I shaletin: Created page with "'''Passenger Name Record''' (abbreviated PNR) is a record in GDS or CRS database in accordance with the existing standards, containin..."

'''Passenger Name Record''' (abbreviated PNR) is a record in [[GDS]] or [[CRS (Computer Reservation System)|CRS]] database in accordance with the existing standards, containing information about the service, route, passenger, group of passengers (or service users). It has a five or six digit numeric locator of the form 1XXX2Y, assigned automatically as a result of the booking procedure, and which then remains unchanged regardless of the transformation of the route. PNRs relating to a cancelled or completed flight are to be stored in computer systems and will be available for a long period of time.

If sections of the route are not operated by the PNR owner, a copy of the record is forwarded to the operating carrier (or several in the case of interline agreements). Many airlines have their CRS in the field of one of the GDSs, allowing them to share PNR information.

PNRs were invented for air travel, but are now used in hotel, train ticket and car rental bookings.

== Main PNR Points ==

There are five basic PNR items that are required to make a booking:

* Name of passenger(s) and remarks;
* Contact information of the agency that made the booking;
* Ticket details (date of sale information that is used by the agent to sell or cancel in a timely manner);
* Itinerary details (flight segments);
* Name of the person at whose request the booking was made, changed, or cancelled.

However, there are other details often requested by airlines and travel agents. For example, fare details and restrictions, the form of payment used, special service requests (SSRs), passenger disability information, etc. In order to prevent terrorist threats and crime, some governments also require airlines to provide traveler details such as date and place of birth, gender, nationality, home and work phone numbers, credit card details, IP (when booking online), another person's details for emergency contact, etc. Individual private organizations have expressed concern about the fact that the information contained in the PNR is exceptionally detailed.

Websky transmits the phone numbers of all passengers when making reservations to promptly inform the airline of any changes to the flight.

== PNR Modification ==

The GDS provides the ability to modify elements of the PNR. If a modification of the PNR elements may violate the homogeneity principle (all passengers whose information is recorded on the PNR are travelling together in one direction) a PNR division (split) shall be applied in this case.

The procedure for modifying elements is defined by the rules of the particular GDS and is contained in the relevant booking instructions.

A change in passenger data is possible only if the airline's rules for booking and sale of air transportation allow such a change.

Changes to the time limit can only be made by specially authorized employees of the agencies by permission of the carrier.

'''Attention!''' <u>When modifying data in the PNR through the terminal</u>, as well as when manually (through the terminal) deleting passengers, the data and service remarks in Websky with these passengers' data must also be changed/deleted.

== Procedure for creating a group PNR ==

The group of passengers is assigned a name - any name formed according to the rules of the particular booking system. In some cases the group additionally receives a five-digit alphanumeric registration number (in order to simplify the agency's work and to control transportations).

When booking a large number of seats (usually more than 9), the time of confirmation by the airline of the requested number of seats may be longer than usual.

If the group is a transit group, it is necessary to enter an arrival segment (information segment about the method and time of arrival of the group to the point of departure).

A separate ticket is issued for each member of the group when air transportation is arranged.

Modification of group PNRs in CRS is carried out according to the rules of individual PNR modification.

== See also ==
* [[Locator]]
* [[Automatic PNR export]]
* [[Integration]]
* [[CRS (Computer Reservation System)]]
* [[GDS]]
* [[Electronic ticket]]
* [[Booking]]
* [[Operating carrier]]
* [[PNR terminal view]]

Travelport (Galileo)

2021-01-28T13:08:12Z

I shaletin: /* Connecting to Galileo GDS in Websky */

'''Travelport (Galileo)''' is one of the largest [[GDS]]s 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 ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and general'''
<div class="mw-collapsible-content">

* 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)

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">

* From the requisites/settings
** Hide the price on the GDS website
** Adding passenger title (not supported by uApi)
** RebookForLowestPrice[[#FAQ on GDS/API Galileo|<sup>[1]</sup>]]
** 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
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Ticketing on airline stock[[#FAQ on GDS/API Galileo|<sup>[2]</sup>]]
* 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
</div>
</div>

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

# Sign a contract with Travelport company:
## Contact the local Travelport office.
## Request a sample contract request form.
## 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.
# 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. <br />
# In the contract application, you must also state that you need masterGTIDs for all online offices (except for the TCH office).
# 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.<br />
# 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).
# 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.

*'''Travelport HAP (Host Access Profile) ordering questionnaire''' [[File:UAPI_Requirements_Questionnaire.doc]]

# '''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.

*'''Travelport questionnaire to order WAB (Work Area Branch)''' [[File:UAPI Requirements Questionnaire.doc]]

==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:

# Checking the status of the set price.
# 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).
# 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:
# deleting the old one;
# 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#Galileo|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:
*# The fare is calculated for reference only.
*# 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===
* The airline [http://www.flyuia.com/rus/main.html Ukraine International Airlines] (UIA airline)
<syntaxhighlight lang="text" enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
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
</syntaxhighlight>.

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 (Airline tickets)|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 "techservices-russia@travelport.com" - 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==
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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.
|-
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|What are the restrictions on the number of passengers in FQSBB requests?
|-
|
# Up to 9 passengers. More than 9 is a group. You can use up to 4 different PTC codes.
# Infants must always travel with an adult.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|How do I add an endorsement in PNRBFManegement?
|-
|
You can add an endorsement to the PNRBFManegement like this:
<pre><EndorsementBox>
<Endors1>VALID ON AI IC ONLY</Endors1>
<Endors2>NON END PENALTIES APPLIES</Endors2>
<Endors3>NON RE ROUTABLE</Endors3>.
</EndorsementBox></pre>.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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 '''
<pre><FareNumInfo>
<FareNumAry>
<FareNum>1</FareNum>
</FareNumAry>
</FareNumInfo></pre>

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

''' Example '''
<pre><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></pre>

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:

* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/PNRBFManagement_21_s113.xml http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/PNRBFManagement_21_s113.xml]
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/Archived_XML_Samples/DocProdFareManipulation_11_s28.xml http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/Archived_XML_Samples/DocProdFareManipulation_11_s28.xml]
It is also recommended to go through the API developer notes and see "Issuing ticket on Galileo/Apollo CRS" by the following links:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheGalileoCRS.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheGalileoCRS.pdf]
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheApolloCRS_v1.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheApolloCRS_v1.pdf]

|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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:

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

Response:
<pre><LocalDateTimeCT_6_0>
<LocalDateTime>
<Dt>20100917 </Dt>
<Tm>1744 </Tm>
</LocalDateTime>
</LocalDateTimeCT_6_0></pre>
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.

|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/GalileoWebServicesHostSessions_v1.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/GalileoWebServicesHostSessions_v1.pdf]
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | Is there any way to increase the speed of responses in the GDS Galileo web services?
|-
|

Useful link:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.h GWS help pages]
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | How do I request and then use private fares?
|-
|
Information on how to request private fares can be found here:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.htm http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.htm]
Transition to Goto XML Select Service > API Developer Notes
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|-
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|-
|}

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS Galileo ==
<div class="mw-collapsible-content">
''' Errors at the beginning of the session: '''
{| class="wikitable"
! Error
! Explanation
! A way of a possible solution
|-
|width="30%"| «ELECTRONIC AGENCY-LINKAGE PROHIBITED» (BeginSession reques)
|width="40%"| The error may occur if the AAT table is set incorrectly.
|width="40%"| You need to contact your local Travelport technical support service.
|}

''' Errors in the search '''
{| class="wikitable"
! Error
! Explanation
! A way of possible solution
|-
|width="30%"|Could not locate Session Token Information Session May Have Timed Out.
|width="40%"| Session limit exceeded.
|width="40%"|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:
{| class="wikitable"
! Error
! Explanation
! A way of possible solution
|-
|width="30%"|SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
|width="40%"|There is a parallel change in the PNR while working with bookings.
|width="40%"| 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: '''
{| class="wikitable"
|-
!align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"REDISPLAY REVIEW BOOKING DATA"
| May occur if two times are added to the <QMinderQual> section (queue minder).
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO VALID FARE FOR INPUT CRITERIA
|- "NO VALID FARE FOR INPUT CRITERIA" may occur if there is no fare that applies to the route with the specified class of service. The error sometimes occurs even if a PNR is created and its locator received.
|-
! align="center" width="50%"|"Error of Frequent Flyer Number"
| The error appears when trying to add the "Frequent Flyer Card" option to an infant booking.
|-
! align="center" width="50%"|"NEED PHONE"
|Error appears if you need to add an agency phone number when completing a booking.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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: '''
{| class="wikitable"
|-
{ "align="center" width="50%"|"INTERLINE ELECTRONIC TICKET AGREEMENT NOT FOUND - CHECK DT/IAT TABLE FOR MORE INFORMATION" [Incident: 101006-000400]
|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.
|-
! align="center" width="50%"|"UNAUTHORISED/INVALID PLATING CARRIER CODE"
|Error occurs if the validating carrier is incorrectly defined.
|-
! align="center" width="50%"|"FILED FARE HAS BEEN INVALIDATED"
|Occurs if automatic fare recalculation is not possible.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO VALID FARE FOR INPUT CRITERIA"
|Indicates a mismatch between the PNR and the Galileo database.
|-
! align="center" width="50%"|"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."
|-
! align="center" width="50%"|"NO ITINERARY EXISTS FOR FARE QUOTATION"
|Indicates that a reservation or segment has been cancelled.
|-
! align="center" width="50%"|"ZA INVALID MODIFIER"
|Indicates that the wrong printer is being used for ticketing.
|-
! align="center" width="50%"| "Z INVALID FORMAT DATA"
|Appears if commissions for TCH-flights are not set correctly.
|-
! align="center" width="50%"|"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).
|-
! align="center" width="50%"|"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 ).
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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).
|-
! align="center" width="50%"|"TICKETING NOT ALLOWED - CHECK AAT"
|Appears when the airline is not authorized for ticketing on this HAP.
|-
! align="center" width="50%"|"REQUESTED FILED FARE NOT FOUND"
|Appears when a fare is no longer available. It is removed by the airline.
|-
! align="center" width="50%"| "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.
|-
! align="center" width="50%"|"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.
|-
align="center" width="50%"CONFIRM SEGMENT 01
|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.
|-
|- "IMU IL DUPLICATE MODIFIER" align="center" width="50%"
|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.
|-
align="center" width="50%"|"TICKETING LINK UNAVAILABLE - PLEASE RETRY"
|- "TICKETING LINK UNAVAILABLE - PLEASE RETRY" means that communication between host and airline has been lost and you can try to issue the ticket later.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO AGREEMENT EXISTS FOR AGENCY"
|- An error occurs when attempting to retrieve a PNR (second step of the ticketing process) in a HAP other than the HAP where the booking was made. You must have a valid agreement (on paper) with Travelport to be able to retrieve the PNR in another HAP.
|-
! align="center" width="50%"|"REQUESTED FILED FARE EXPIRED"
|- The error means that the fare is no longer valid. Only the airline whose ticket is being issued can guarantee the fare.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|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.
|-

'''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.
<pre><PNRBFManagement_x>
<PNRBFRetrieveMods>
<PNRAddr>
<FileAddr/>
<CodeCheck/>
<RecLoc>VXXXLM</RecLoc>
</PNRAddr>
</PNRBFRetrieveMods>
<CancelStoredFareMods>
<FareNumInfo>
<FareNumAry>
<FareNum>001</FareNum>
</FareNumAry>
</FareNumInfo>
</CancelStoredFareMods></pre>
|-
|}

''' Errors when cancelling ticketing: '''
{| class="wikitable"
|-
! align="center" width="50%"|«TKT NUMBER NOT FOUND OUTSIDE VOIDING PERIOD»
|The error occurs if there is a time limit for voiding.
|-
! align="center" width="50%"|«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 '''
{| class="wikitable"
|-
! align="center" width="50%"|«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:

<pre>"Note: Some of these errors overlap with the unvoid and spoiled tasks:"</pre>.
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:
# refund;
# 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.

</div>
</div>

== See also ==
* [[GDS]]
* [[TCH (Transport Clearing House)]]
* [[BSP]]
* [[Stopover]]
* [[Error#Galileo|Errors in working with Galileo]]
* [[Ticket printer#Galileo ticket printers|Galileo ticket printers]]
* [[Endorsement#Requirements for endorsements in Galileo|Requirements for endorsements in Galileo]]
* [[Ticket#Functional capabilities of airline ticket suppliers|Functional capabilities of airline ticket suppliers]]
* [[Processing#Airlines that accept credit card payments through GDS|Airlines that accept credit card payments through GDS]]
* [http://www.flyuia.com/agents/ADM.html Penalties of IUA with the application of the ADM procedure]
* [[PNR]]
* [[Sabre]]
* [[Amadeus]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

== Useful links ==
* [http://www.travelport.com/lob/gds/galileo.aspx GDS Galileo page on the Travelport website]
* [http://www.travelport.com/russia?sc_lang=ru-RU Site of Travelport representative office in Russia]
* [http://www.tch.ru/rus/products/1g/ Steps to ensure the possibility of issuing e-tickets NSAV TCH through the ASB "Galileo" in accredited agencies]
* [http://www.galileo.com.ua/m1/ru/tourists/06871841/ticketing Information page on the Travelport - Ukraine website]

Travelport (Galileo)

2021-01-28T13:07:05Z

I shaletin: Created page with " '''Travelport (Galileo)''' is one of the largest GDSs offering airline, hotel, travel and car rental booking services. Along with the global distribution system Worldspan..."

'''Travelport (Galileo)''' is one of the largest [[GDS]]s 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 ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and general'''
<div class="mw-collapsible-content">

* 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)

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">

* From the requisites/settings
** Hide the price on the GDS website
** Adding passenger title (not supported by uApi)
** RebookForLowestPrice[[#FAQ on GDS/API Galileo|<sup>[1]</sup>]]
** 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
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Ticketing on airline stock[[#FAQ on GDS/API Galileo|<sup>[2]</sup>]]
* 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
</div>
</div>

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

# Sign a contract with Travelport company:
## Contact the local Travelport office.
## Request a sample contract request form.
## 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.
# 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. <br />
# In the contract application, you must also state that you need masterGTIDs for all online offices (except for the TCH office).
# 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.<br />
# 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).
# 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.

*'''Travelport HAP (Host Access Profile) ordering questionnaire''' [[File:GWS Questionnaire.doc]]

# '''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.

*'''Travelport questionnaire to order WAB (Work Area Branch)''' [[File:UAPI Requirements Questionnaire.doc]]

==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:

# Checking the status of the set price.
# 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).
# 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:
# deleting the old one;
# 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#Galileo|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:
*# The fare is calculated for reference only.
*# 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===
* The airline [http://www.flyuia.com/rus/main.html Ukraine International Airlines] (UIA airline)
<syntaxhighlight lang="text" enclose="div" style="font-size:9pt;background: #F9F9F9; border: 1px dashed #2F6FAB; padding: 10px 5px; margin: 10px 0;">
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
</syntaxhighlight>.

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 (Airline tickets)|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 "techservices-russia@travelport.com" - 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==
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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.
|-
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|What are the restrictions on the number of passengers in FQSBB requests?
|-
|
# Up to 9 passengers. More than 9 is a group. You can use up to 4 different PTC codes.
# Infants must always travel with an adult.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|How do I add an endorsement in PNRBFManegement?
|-
|
You can add an endorsement to the PNRBFManegement like this:
<pre><EndorsementBox>
<Endors1>VALID ON AI IC ONLY</Endors1>
<Endors2>NON END PENALTIES APPLIES</Endors2>
<Endors3>NON RE ROUTABLE</Endors3>.
</EndorsementBox></pre>.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;"|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 '''
<pre><FareNumInfo>
<FareNumAry>
<FareNum>1</FareNum>
</FareNumAry>
</FareNumInfo></pre>

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

''' Example '''
<pre><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></pre>

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:

* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/PNRBFManagement_21_s113.xml http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/PNRBFManagement_21_s113.xml]
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/Archived_XML_Samples/DocProdFareManipulation_11_s28.xml http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/XML_Samples/Archived_XML_Samples/DocProdFareManipulation_11_s28.xml]
It is also recommended to go through the API developer notes and see "Issuing ticket on Galileo/Apollo CRS" by the following links:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheGalileoCRS.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheGalileoCRS.pdf]
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheApolloCRS_v1.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/IssuingATicketOnTheApolloCRS_v1.pdf]

|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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:

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

Response:
<pre><LocalDateTimeCT_6_0>
<LocalDateTime>
<Dt>20100917 </Dt>
<Tm>1744 </Tm>
</LocalDateTime>
</LocalDateTimeCT_6_0></pre>
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.

|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/GalileoWebServicesHostSessions_v1.pdf http://testws.galileo.com/GWSSample/Help/GWSHelp/mergedProjects/TRANSACTIONHELP/1API_Dev_Notes/GalileoWebServicesHostSessions_v1.pdf]
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | Is there any way to increase the speed of responses in the GDS Galileo web services?
|-
|

Useful link:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.h GWS help pages]
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | How do I request and then use private fares?
|-
|
Information on how to request private fares can be found here:
* [http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.htm http://testws.galileo.com/GWSSample/Help/GWSHelp/gws.htm]
Transition to Goto XML Select Service > API Developer Notes
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|-
|}
{| class="wikitable mw-collapsible mw-collapsed"
|-
! style="text-align:left; width: 1400px;" | 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.
|-
|}

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS Galileo ==
<div class="mw-collapsible-content">
''' Errors at the beginning of the session: '''
{| class="wikitable"
! Error
! Explanation
! A way of a possible solution
|-
|width="30%"| «ELECTRONIC AGENCY-LINKAGE PROHIBITED» (BeginSession reques)
|width="40%"| The error may occur if the AAT table is set incorrectly.
|width="40%"| You need to contact your local Travelport technical support service.
|}

''' Errors in the search '''
{| class="wikitable"
! Error
! Explanation
! A way of possible solution
|-
|width="30%"|Could not locate Session Token Information Session May Have Timed Out.
|width="40%"| Session limit exceeded.
|width="40%"|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:
{| class="wikitable"
! Error
! Explanation
! A way of possible solution
|-
|width="30%"|SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
|width="40%"|There is a parallel change in the PNR while working with bookings.
|width="40%"| 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: '''
{| class="wikitable"
|-
!align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"REDISPLAY REVIEW BOOKING DATA"
| May occur if two times are added to the <QMinderQual> section (queue minder).
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO VALID FARE FOR INPUT CRITERIA
|- "NO VALID FARE FOR INPUT CRITERIA" may occur if there is no fare that applies to the route with the specified class of service. The error sometimes occurs even if a PNR is created and its locator received.
|-
! align="center" width="50%"|"Error of Frequent Flyer Number"
| The error appears when trying to add the "Frequent Flyer Card" option to an infant booking.
|-
! align="center" width="50%"|"NEED PHONE"
|Error appears if you need to add an agency phone number when completing a booking.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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: '''
{| class="wikitable"
|-
{ "align="center" width="50%"|"INTERLINE ELECTRONIC TICKET AGREEMENT NOT FOUND - CHECK DT/IAT TABLE FOR MORE INFORMATION" [Incident: 101006-000400]
|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.
|-
! align="center" width="50%"|"UNAUTHORISED/INVALID PLATING CARRIER CODE"
|Error occurs if the validating carrier is incorrectly defined.
|-
! align="center" width="50%"|"FILED FARE HAS BEEN INVALIDATED"
|Occurs if automatic fare recalculation is not possible.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO VALID FARE FOR INPUT CRITERIA"
|Indicates a mismatch between the PNR and the Galileo database.
|-
! align="center" width="50%"|"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."
|-
! align="center" width="50%"|"NO ITINERARY EXISTS FOR FARE QUOTATION"
|Indicates that a reservation or segment has been cancelled.
|-
! align="center" width="50%"|"ZA INVALID MODIFIER"
|Indicates that the wrong printer is being used for ticketing.
|-
! align="center" width="50%"| "Z INVALID FORMAT DATA"
|Appears if commissions for TCH-flights are not set correctly.
|-
! align="center" width="50%"|"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).
|-
! align="center" width="50%"|"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 ).
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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).
|-
! align="center" width="50%"|"TICKETING NOT ALLOWED - CHECK AAT"
|Appears when the airline is not authorized for ticketing on this HAP.
|-
! align="center" width="50%"|"REQUESTED FILED FARE NOT FOUND"
|Appears when a fare is no longer available. It is removed by the airline.
|-
! align="center" width="50%"| "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.
|-
! align="center" width="50%"|"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.
|-
align="center" width="50%"CONFIRM SEGMENT 01
|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.
|-
|- "IMU IL DUPLICATE MODIFIER" align="center" width="50%"
|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.
|-
align="center" width="50%"|"TICKETING LINK UNAVAILABLE - PLEASE RETRY"
|- "TICKETING LINK UNAVAILABLE - PLEASE RETRY" means that communication between host and airline has been lost and you can try to issue the ticket later.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"NO AGREEMENT EXISTS FOR AGENCY"
|- An error occurs when attempting to retrieve a PNR (second step of the ticketing process) in a HAP other than the HAP where the booking was made. You must have a valid agreement (on paper) with Travelport to be able to retrieve the PNR in another HAP.
|-
! align="center" width="50%"|"REQUESTED FILED FARE EXPIRED"
|- The error means that the fare is no longer valid. Only the airline whose ticket is being issued can guarantee the fare.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|"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.
|-
! align="center" width="50%"|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.
|-

'''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.
<pre><PNRBFManagement_x>
<PNRBFRetrieveMods>
<PNRAddr>
<FileAddr/>
<CodeCheck/>
<RecLoc>VXXXLM</RecLoc>
</PNRAddr>
</PNRBFRetrieveMods>
<CancelStoredFareMods>
<FareNumInfo>
<FareNumAry>
<FareNum>001</FareNum>
</FareNumAry>
</FareNumInfo>
</CancelStoredFareMods></pre>
|-
|}

''' Errors when cancelling ticketing: '''
{| class="wikitable"
|-
! align="center" width="50%"|«TKT NUMBER NOT FOUND OUTSIDE VOIDING PERIOD»
|The error occurs if there is a time limit for voiding.
|-
! align="center" width="50%"|«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 '''
{| class="wikitable"
|-
! align="center" width="50%"|«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:

<pre>"Note: Some of these errors overlap with the unvoid and spoiled tasks:"</pre>.
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:
# refund;
# 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.

</div>
</div>

== See also ==
* [[GDS]]
* [[TCH (Transport Clearing House)]]
* [[BSP]]
* [[Stopover]]
* [[Error#Galileo|Errors in working with Galileo]]
* [[Ticket printer#Galileo ticket printers|Galileo ticket printers]]
* [[Endorsement#Requirements for endorsements in Galileo|Requirements for endorsements in Galileo]]
* [[Ticket#Functional capabilities of airline ticket suppliers|Functional capabilities of airline ticket suppliers]]
* [[Processing#Airlines that accept credit card payments through GDS|Airlines that accept credit card payments through GDS]]
* [http://www.flyuia.com/agents/ADM.html Penalties of IUA with the application of the ADM procedure]
* [[PNR]]
* [[Sabre]]
* [[Amadeus]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

== Useful links ==
* [http://www.travelport.com/lob/gds/galileo.aspx GDS Galileo page on the Travelport website]
* [http://www.travelport.com/russia?sc_lang=ru-RU Site of Travelport representative office in Russia]
* [http://www.tch.ru/rus/products/1g/ Steps to ensure the possibility of issuing e-tickets NSAV TCH through the ASB "Galileo" in accredited agencies]
* [http://www.galileo.com.ua/m1/ru/tourists/06871841/ticketing Information page on the Travelport - Ukraine website]

File:UAPI Requirements Questionnaire.doc

2021-01-28T13:06:33Z

I shaletin:

Sabre

2021-01-24T15:49:55Z

I shaletin: /* Connection features */

'''Sabre Travel Network''' (Sabre) — a part of the group of companies Sabre Holdings (USA), serving travel agencies, travel service providers, corporations and government agencies in 59 countries around the world.

== Description ==
Sabre processes more than 19,000 transactions per second - about 2 billion transactions every day.

Mute Lab Software is an official certified developer on Sabre Web Services.

Booking system [https://websky.aero/ Websky] supports ticket sales through Sabre global distribution system.

== Key Features ==

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">

* Search by nearest dates
* Search by public + private fares
* Search for private fares
* Search by schedule
* Search by J-types.
* Sending terminal commands
* Search with limited prices
* Returning the Refundable attribute in search results - BFM
* Return e-ticket attribute in search results
* Returning a ticketing deadline in search results
* Validating carrier in search results
* Checking interlines in search results
* Maximum number of passengers of all types in the search request is 32
* Number of passengers of one type in the request is 8

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">

* From the requisites/settings
** Hiding the price on the GDS site
** Adding a passenger title
** RebookForLowestPrice[[#FAQ on GDS/GDS/API Sabre|<sup>[1]</sup>]]
** Remarks (in requisites) for booking entries
** Working with AAA PCC
** Repeating of seats taking when getting NN status
* Additional operations with requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat assignment
** Receiving a Seat Map
** Updating the price
** Getting a list of available credit cards
** Getting a currency rate
** Maximum number of simultaneous sessions - 50 standard, extensions of 25 sessions
** Returning fare types - Public, Nego
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Ticket availability check outside of NDP
** Import of bookings via NDP locator
** Retrieving booking history from the NDP
** Modification of name and patronymic
** Modifying selected booking content
** Adding content
** Content through WS - BSP
** Ability to book and check out BSP
** Booking for an infant seat
** Cancellation via app
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">

* From the props/settings.
** Adding a general purpose passive segment (misc segment)
** Discharge on airline stock
** Discharge runoff management
** AAA PCC handling
** Private commission authorization
** Airline server operations/requests
** Ticket issuance for the whole booking
** Additional ticketing for passengers who are on hold
** Checking airline commission at checkout
** Commission per passenger type
** Depositing endorsements
** Ticketing tour codes
** Ticket-designator setup
** GDS processing
** Multi-FOP GDS processing
** Proxying of GDS processing through the Payment Gateway
** Voiding
</div>
</div>

== Working Principle ==
Websky makes an update at every booking operation, and the PNR is automatically re-priced, except for the following situations:
*booking is cancelled
*booking is ticketed
Once a statement is requested, a transaction confirmation is performed so that the issued tickets are included in the PNR.
In case Websky may have problems while updating bookings, a check with DQB (sales report in GDS Sabre) will be made and tickets issued by PNR but not included in the PNR. If for some reason they are not entered, the booking will be marked as problematic and such bookings will need to be processed manually by the agent in the terminal.

== Connecting to GDS Sabre in Websky ==

In order to connect a Websky airline unit that works with Sabre system, the agency must have an agreement for Sabre system use. If the agency does not have such an agreement, it is necessary to contact the local Sabre office and enter into an agreement to use the system.

If the agency has a Sabre connection agreement, it means that the agency can use the Sabre system via terminals installed in the agency and create/cancel/modify bookings, control booking queues, calculate fares and issue tickets, book services of other suppliers (such as hotels, car rentals, etc).

The procedures of creating a configuration, setting up offices, ordering additional terminal addresses and printers are specified in the "Agreement for connection and access to Sabre information resources" and in the "Regulations of interaction between users of Sabre information resources and the Russia Sabre Help Desk" (both documents are available at [http://www.airts.ru www.airts.ru] in the "SabreOrder" section.

Sabre connects to the Websky system through a specially configured agency office called IPCC (Internet PCC - [[IPCC]]), which is ordered through a local Sabre representative office.

If the agency is not licensed to use the Sabre web service, it must:

# Write a letter to Sabre confirming that the agency intends to use the Websky system developed by LLC "Novaya Studiya" for online activity. At the same time, LLC "Novaya Studiya" should write a letter to Sabre confirming its readiness to provide the agency with such a service.

# Sign an additional contract with the local Sabre representative office for IPCC Downline Agency IPCC, pay for all the services mentioned in that contract and get the IPCC, login and password from Sabre, after that give the IPCC number, login and password to LLC "Novaya Studiya" for the connection details.

'''Attention!''' If the agency has its own Sabre web service license, the agency can obtain an IPCC as part of that license by contacting the local Sabre office. The IPCC number, username and password obtained should be given to "Novaya Studiya" to be entered into the connection requisites.

'''Attention!''' To ensure correct operation, the agency must order a LNIATA PRT TA - e-ticket or itinerary receipt printer address - if the booking and ticketing occurs in the IPCC and in the BSP environment.

If the agency plans to issue ETAT tickets (airline e-tickets) online, an additional terminal (for booking control work) and printer (for ETAT issuance) must also be ordered from Sabre.

If there is a sub-agency relationship with an agency which has an agreement with the airline to issue ETATs, a letter must be sent to the local Sabre office, signed and stamped on the agency letterhead, with a request to prescribe in the PCC where the ETATs will be issued the details of this agency as indicated in the agreement with the airline, namely: validator, company name and its address.

The PCC for ETAT can be ordered either by the agency or by a sub-agency.

If an agency or sub-agency orders a PCC to issue an ETAT, written confirmation from the airline must be obtained in order for that PCC to be activated. This letter may be sent by the airline directly to the local Sabre office or to the agency for onward transmission to Sabre.

Ordering additional PCCs, as well as printers, is done by filling out applications in SabreOrder, and linking of printers is carried out by Sabre support staff after creating and configuring PCCs.

'''Attention!''' For agencies located in Moscow, the parameter LOR (Location Of Request) in PCC must be set to MOW - this affects the correctness of work with some Russian airlines. For example, in the case of the value of SVO may not be confirmed seats on the airline SkyExpress.

==How to receive Sabre connection requisites to work in Websky==
To interact with GDS Sabre through Websky:
# Send a connection request to Sabre, get approval, create a ticket in [http://helpdesk.nemo.travel| project tracker] in which you provide the requisites you received (the ticket must be assigned to _SUPPORT RECEPTION).
# After you set up the requisites and successfully test the search, booking, and cancellation, Websky staff will return the ticket to the agency employee for testing the statement and entering in the set up details.

To interact with GDS Sabre through Websky, the agency must complete the following steps:
# Sign an agreement with Sabre and obtain a PCC.
# After getting the PCC, order online requisites to work with via Websky - IPCC. To do this, fill out an application form and send it to Sabre.
# After reviewing the application, Sabre will issue a username and password to connect to your IPCC. Provide them to Websky via [http://helpdesk.nemo.travel| project tracker] to set up your Sabre connection requisites in Websky.
# Additionally, you must order the BFM lookup option from Sabre. A separate questionnaire is filled out for this (the template is attached in the ''Sabre BFM Questionnaire'' section). The BFM opens for one month, until then only the LFS search is available.

To set up the ticketing process, you need to ask the Sabre helpdesk to do the settings for your BFM.

=== Sabre BFM Questionnaire ===
Sabre vendor has two search options: LFS and BFM. To obtain BFM requisites, you are asked to fill out the following questionnaire: [[File:BFM questionnaire.pdf]].

The questionnaire contains a total of 17 questions, some of which are required as background information. When filling out the questionnaire, you should pay attention to the following questions:
* Question #2, which specifies whether the reservation and checkout will take place on the same PCC.
* Question #3, which specifies the number of searches and their planned changes.
* Question #7, which specifies the planned number of transactions per day in test and environment and real mode.

An example of a completed questionnaire: [[File:BFM_questionnaire_example.pdf]]

=== Ticketing settings in Sabre ===

In order to run an electronic ticket checkout, the Ticketing Agency must write a letter to the Sabre Helpdesk (sabre.helpdesk@airts.ru) that reads as follows:
# Please open branch access level B,C between IPCC ''XXXX'' and PCC ''XXXX''
# Please add the key SUBAA for EPR 7971 (7972) for IPCC ''XXXX''
'''Attention!''' EPR is the agency account that matches the login listed in the established credentials. EPR 7971 (7972) is relevant for Sabre Russia. You can find the necessary EPR by the login, which is specified in the Nemo Connect '''Avia Settings - GDS Connection Settings - GDS Requisites - Sabre Requisites''' for the particular PCC.

Settings to check before running automatic ticketing from the agency website on the GDS side of Sabre:

# Option Store Passenger Type in PNR in TJR PCC/IPCC must be enabled.
# Option Auto Segment Arrange in TJR PCC/IPCC must be enabled.
# Option Auto Validation in TJR PCC/IPCC must be enabled.
# Option Russian Ticketing Platform in TJR PCC/IPCC must be enabled.
# Option Full Branch Access between booking IPCC and PCC must be configured.
# Option ETICKET IN EMAIL in TJR PCC/IPCC must be enabled.
# Option PRICE TICKETING ALERT in the TJR PCC/IPCC must be disabled.
# SUBAAA keyword must be present in the EPR of all agents/cashiers that handle reservations to be able to transition between PCC/IPCC.
# The presence of a printer terminal address (PTR TA) is required for issuing the PCC.
# IATA validator is required when using it as the primary for ticketing. Also, checking the carrier list against the IATA license. If own validator of carrier is used, for example Aeroflot, then it is necessary to order additional PCC for it.

The settings must be activated in all Sabre sections: TSTS, CERT, CUSTOMER ACCEPTANCE and PRODUCTION.

These settings must be verified at all PCC/IPCCs where you intend to book and issue tickets. To do this, contact the Sabre Helpdesk: sabre.helpdesk@airts.ru

And the obligatory point: it is necessary that in PCC (if IPCC will be used for issuing, ask to make settings for it), there should be carriers available for issuing with validator and its code. This is done through a service (it is a request system, each client has a login and password to it) sabreorder@airts.ru

=== Connection features===
* In Sabre, while setting up the PCC for the ticketing, the stock on the ticketing is specified. It means that it is crucial to specify who the validator is. In Websky settings, the printer is specified according to the stock.
*At the same time, the client performs all items specified [http://support.mute-lab.com/ru/Сейбр#.D0.9D.D0.B0.D1.81.D1.82.D1.80.D0.BE.D0.B9.D0.BA.D0.B8_.D0.B2.D1.8B.D0.BF.D0.B8.D1.81.D0.BA.D0.B8_.D0.B1.D0.B8.D0.BB.D0.B5.D1.82.D0.B0_.D0.B2_Sabre here] on his part.
*In the default settings, the printer type is OPTAT for the BSP stock. This means that the printer is assigned with the command: RU
*When the ticketing is performed on the stock of SU (Aeroflot) airline, printer type must be set to: Specialixed E-TAT, which means that the printer is controlled by the command 1R
*When the ticketing is performed on the stock of S7 (Siberia), U6 (Ural Airlines) airlines runoff the printer type must be set to Generic E-TAT, which means that the printer is assigned to a command: 1Y
*When checking out on Ukrainian RCC the printer is also assigned by another command, you must put the printer type: ATB, which means that the printer is assigned by the command: AT
* '''Attention!''' Make sure that the '''DivideInParty''' option is disabled '''on the supplier side'''. If the option is enabled, you will see a large number of price increases when you switch to booking.
*'''Attention!''' The '''Audit trail''' value in the Sabre-side PCC settings must be set to '''Regular audit trail'''.

== Features of working with Sabre==
* Strict requirements to agency names. If you violate the name requirements when booking services, you get errors of the following kind: '''Input data error'''.
** The agency name must not contain punctuation marks and Cyrillic characters; only Latin letters and spaces are allowed.
<br />"If you want the name to begin with numbers, set the first character to be a space - this will help you avoid the error."

* On the booking confirmation page, in the '''In the currency of the booking system''' column, prices are displayed in the currency of the airline fare.
* In response to the search request, the cheapest variants appear. So the '''2 adults + 1 child''' request may return the response '''3 adults'''.
* Sabre will reply to your search request with information about the baggage allowance.
* Bookings at GDS Sabre are strictly available for no more than 331 days in advance of the booking date. Sabre will return an error message like this: <code>SYSTEM UNABLE TO PROCESS: INVALID DATE</code>.
* In Sabre, when you issue a ticket for a child with the ''Birth Certificate'' document type, the itinerary receipt shows the document type ''Substitute Document'', because Sabre does not support the ''Birth Certificate'' document type.
* When searching for Business class tickets, if there are no suitable Business class flights, Sabre can send you Economy class flights. However, the system may also send first class fares if their price is equal or less than business class fares.
* In GDS Sabre, there are situations when the airline removes successfully taken seats immediately after the booking is made (including using the ''RebookForLowest'' option).
* In GDS Sabre, there are situations when it is obligatory to pay by credit card for the seats or ancillary services in the booking; in this case, the following error message will be shown at the ticketing stage: UNABLE - ONLY CREDIT CARD FORM OF PAYMENT ALLOWED.
* In GDS Sabre, there are the following limitations on the length of characters in the name in the PNR:
** Maximum number of characters for last name and first name combined is 58.
** Maximum number of characters for last name, first name and middle name in total - 57.
** If the passenger is female, the above values are reduced by 1.
** Maximal number of characters for last name is 30. <br />Websky [[Booking Form (Air Tickets)|booking form]] limits number of characters for passenger's last name in order to meet the above limitations and avoid mistakes in booking.
** Maximal number of characters for name on SU airline is 29.
** '''Attention!''' Spaces are also symbols and count in the calculation.
** The number of passengers per online booking is limited. The airline itself determines the maximum number of passengers per booking. For example, on Aeroflot - 7 passengers, on Ural Airlines - 5 passengers. To prevent errors, the agency can limit the number of passengers in an order for all airlines in Websky using the ''Maximum number of people in a search request'' parameter in the '''Product control → Flight tickets → Outdated settings → Search restrictions''' section.
* If there are a large number of flight price increases when you switch to a booking, make sure that the '''DivideInParty'' option is disabled '''on the supplier side'''.
* If, when a ticket is being issued, the following message is received: '''The order contains issued tickets that are not presented in the PNR''' and there are 2 ticket numbers for one passenger in the order - a common case when working in Sabre/<br />To manage cases of double ticketing, Nemo Connect has the option ''Action with valid tickets not in the PNR'' (in '''Profiles → User Profiles'''):
** ''Mark as Problematic'' - in this case the manager will receive a notification about the problem booking;
** ''Auto-voiding'' - a ticket not in the PNR (''extra'') will be entered, while the integrity of the order will be preserved.
* '''Accounting for changes in GDS.''' In order to, when multiplying flights and when using the results of searches from the cache (see [[Cache Server]]) when amounts need to be converted correctly, exchange rates from GDS Sabre must have the BSRDSP keyword in EPR for all PCCs (settings on the Sabre side, contact GDS support for setup), see [[Cache Server#Accounting for fare changes in GDS|Accounting for fare changes in GDS]].

== Agency Commission Display in GDS Sabre ==

Agency commission is assigned to the agency by the airline in accordance with the contract. The commission can be the same for any transportation, but may differ by destinations, countries, types of flights.

In any case, the commission is not displayed neither in the e-ticket, nor in the itinerary receipt.

For the booking created in Sabre the informational price of the flight is displayed on the screen by the PQ command. When working with the terminal, the agent can calculate the price of the flight with the commission, since while creating the booking he can know on which carrier's form the transportation will be performed. In this case the commission is displayed in the PQ command results.

When working online, the commission parameters are determined only at the ticketing step, so the informational price of transportation in our case does not include the commission. It means that the PQ command displays the total price of the flight.

In Sabre terminal the commission for a particular booking can be viewed by displaying the booking on the screen and opening the Accounting Data section with the *PAC command - all the information on the ticket, which includes data on the commission, is displayed.

The [[commission]] is not printed on the [[electronic ticket]], you can only see it in the prototype of the paper ticket on the basis of which the [[electronic ticket]] is issued. In the itinerary receipt the commission is also not displayed.

In addition to the ability to see the airline commission in the booking by *PAC command, the agent can call the DQB* sales report, in which you can see the amount of commission for the booking you are interested in.

==Supported features==

GDS Sabre supports the following options implemented in Websky:

* '''Rebooking for the lowest price''' (''RebookForLowestPrice'', ''rebookForLowest'') - the option allows you to get the current booking/flight price not for the specified flight class letters (seats that may run out; or the price might be unavailable or might not be the cheapest), but to generally get the cheapest available price for the given flight within the same base class (Economy/Business/Premium Economy, etc.) as the original literature, with the GDS automatically checking the availability of the required number of vacant seats.

*[[Synchronization of orders]] - synchronization module for GDS Sabre supplier is implemented.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors when working with Sabre ==
<div class="mw-collapsible-content">

=== Search errors ===
{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" |'''Common errors for all GDSs'''
|-
|<code> SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR</code>
| width="70%"| In the boooking operation, there is a parallel change of PNR. In this case you have to start the operation again.
|-
|<code> Possible IC throttle Text: java.util.NoSuchElementException: Pool exhausted </code>
|width="70%"| This error occurs because of active work. It's worth noting that the error is not critical and occurs to block traffic and prevent overloading on the GDS side.
|-
| <code>Invalid search reguest object</code>
|This error occurs when an invalid search result is accessed. Possible causes:
# invalid search link;
# search result may be out of date.
|-
|}

=== Ticketing errors ===

{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" | '''For the PROD environment'''
|-
| <code>AUTH CARRIER INVLD-0166</code> (<code>auth_error</code>)
|width="70%"| On the GDS side, the specified validating carrier is not in the list of authorized carriers for the ticketing. Or, the settings mentioned above (3 points) are not performed in full!
|-
|<code>"TICKETING IN ALTERNATE CURRENCY NOT ALLOWED-0106" and "SEE W/CURR*-CANNOT TICKET IN CURRENCY REQUESTED-0106</code>"
|Restriction of ticketing in the specified currency.
|-
|<code> 9999.99 IS THE MAXIMUM AMOUNT OF COMMISSION-0265</code>
| Incorrect rounding of commissions.
|-
|<code>NO COMBINABLE FARES FOR CLASS USED53</code?
|It is impossible to calculate the fare (in the Websky system such situations cannot be handled).
|-
|<code>Error response received. The error was: CODE - HX SEG STATUS NOT ALLOWED</code>.
|The flight contains segments cancelled by the airline.
|-
|<code>VALIDATING CARRIER XW DOES NOT HAVE AGREEMENT WITH D9-0322</code>
|No interline agreement between airlines (cannot be processed by Websky at this time).
|-
|<code>EACH PASSENGER MUST HAVE SSR FOID-0052</code>
|No FOID data transmitted, connection requisites for TCP flights need to be checked.
|-
|<code>validation_error (VALIDATING CARRIER UN DOES NOT HAVE AGREEMENT WITH S7-0322)</code>
| There is no interline agreement between the airlines flying, such tickets can only be issued separately.
|-
|<code>TERM NOT HARDCOPY</code>.
|The Websky LNIATA PRT TA (e-ticket printer address) in the ticketing settings is incorrect.
|-
|<code>153 NAME DOES NOT MATCH NAME IN AIRLINE SYSTEM</code>
|Exceeded allowed number of characters in passenger's name
|-
!colspan="2" |'''For CERT environment'''
|-
|<code>UNABLE TO PROCESS ETR-CORRECT/RETRY OR ISSUE PAPER TICKET-368 AGENCY NOT ALLOWED TO ISSUE ELECTRONIC TICKETING</code>
|Error comes from the supplier and may be due to the fact that the work takes place in different environments (CERT, TSTS). To test in a CERT environment, you must use one of the following carriers: AA, SU, B6, KM, IT, HA,WS.
|-
|<code>NEED AIRLINE PNR LOCATOR - VERIFY AND ENTER IN SEGMENT-0052</code>
|The error occurs because a CERT environment is being used.
|-
|<code>VERIFY TKT TTL RUB 1663 - PQ TTL RUB 1563 TICKET? ENTER Y or N<.></code>
|In Sabre, there is a price comparison at the booking and at the checkout.
|-
|}

===Cancellation mistakes ===
{| class="wikitable"
|-
! Error
! Description
|-
|<code>OTH RESTRICTIONS APPLY-REBOOK OTH NO LATER THAN 04MAY</code>
|width="70%"|The error is due to the features of the rules for creating OTH segments in GDS Sabre. As of June 5, 2017, new rules for creating OTH segments (which are used to extend the lifetime of a booking in the system after all flights have been completed) were introduced, the essence of which is that it is prohibited to add OTH segments with a date the departure date of the last active segment in the booking by 180 days, and if there are no active segments in the booking, but they are in the history, it is prohibited to add an OTH segment with a date 180 days higher than the current date (for example, the booking was made on November 5, 2017, then the clearance date plus 180 days - turns out to be May 4).
|-
|}
</div>
</div>

== Airline ancillary services ==
In Sabre additional services are available for any PCC by default, no additional settings are required from Sabre.<br>
To enable work with advanced services in Websky you have to enable the checkbox "Enable work with advanced services in this package" in the "Airline settings" -> "Airline packages" section of the Sabre "Airline details package". <br>
'''Attention!''' To display additional services on your website, you need to fill in the section "Additional services" in the Guide in the Administration panel of Websky 2.0. Only Websky system administrator can fill it in.

== Contact info ==

Sabre Russian representative office: 125009, Moscow, Tverskaya str. 16, bld.3, office 14, tel: (499) 929 5080.

Sales Department: (499) 929-5080 or (499) 929-5090

Technical Support and Helpdesk Russia: +7 495 974-8951

== See also ==
*[[IPCC]]
*[[Endorsement#Requirements for endorsements in Sabre|Requirements for endorsements in Sabre]]
*[[GDS|Data on resources and the Sabre distribution network]]
*[[Ticket printer#Sabre ticket printer|Sabre ticket printers]]
*[[Statistics#Supplier statistics|Supplier statistics]]
*[[Ticket#Functional capabilities of airline ticket suppliers| Functional capabilities of airline ticket suppliers]]
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Amadeus]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[API VIP Service]]
* [[Nemo Inventory (component)]]

== Useful links ==
*[http://www.sabre.com Sabre Holdings website]
*[http://www.sabretravelnetwork.ru/home Sabre Travel Network website]
*[http://www.sabretravelnetwork.ru/home/products_services/product_index Sabre products]
*[http://www.tch.ru/rus/products/1s/ Steps to enable electronic and automated issuance of NSAW TCH tickets through Sabre (GDS Sabre) at accredited agencies]
*[http://support.mute-lab.com/ru/%D0%9F%D1%80%D0%BE%D1%86%D0%B5%D1%81%D1%81%D0%B8%D0%BD%D0%B3#.D0.90.D0.B2.D0.B8.D0.B0.D0.BA.D0.BE.D0.BC.D0.BF.D0.B0.D0.BD.D0.B8.D0.B8.2C_.D0.BF.D1.80.D0.B8.D0.BD.D0.B8.D0.BC.D0.B0.D1.8E.D1.89.D0.B8.D0.B5_.D0.BE.D0.BF.D0.BB.D0.B0.D1.82.D1.83_.D0.BA.D1.80.D0.B5.D0.B4.D0.B8.D1.82.D0.BD.D1.8B.D0.BC.D0.B8_.D0.BA.D0.B0.D1.80.D1.82.D0.B0.D0.BC.D0.B8_.D1.87.D0.B5.D1.80.D0.B5.D0.B7_GDS List of airlines that accept credit card payments through GDS Sabre]

Sabre

2021-01-24T15:47:41Z

I shaletin: /* See also */

'''Sabre Travel Network''' (Sabre) — a part of the group of companies Sabre Holdings (USA), serving travel agencies, travel service providers, corporations and government agencies in 59 countries around the world.

== Description ==
Sabre processes more than 19,000 transactions per second - about 2 billion transactions every day.

Mute Lab Software is an official certified developer on Sabre Web Services.

Booking system [https://websky.aero/ Websky] supports ticket sales through Sabre global distribution system.

== Key Features ==

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">

* Search by nearest dates
* Search by public + private fares
* Search for private fares
* Search by schedule
* Search by J-types.
* Sending terminal commands
* Search with limited prices
* Returning the Refundable attribute in search results - BFM
* Return e-ticket attribute in search results
* Returning a ticketing deadline in search results
* Validating carrier in search results
* Checking interlines in search results
* Maximum number of passengers of all types in the search request is 32
* Number of passengers of one type in the request is 8

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">

* From the requisites/settings
** Hiding the price on the GDS site
** Adding a passenger title
** RebookForLowestPrice[[#FAQ on GDS/GDS/API Sabre|<sup>[1]</sup>]]
** Remarks (in requisites) for booking entries
** Working with AAA PCC
** Repeating of seats taking when getting NN status
* Additional operations with requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat assignment
** Receiving a Seat Map
** Updating the price
** Getting a list of available credit cards
** Getting a currency rate
** Maximum number of simultaneous sessions - 50 standard, extensions of 25 sessions
** Returning fare types - Public, Nego
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Ticket availability check outside of NDP
** Import of bookings via NDP locator
** Retrieving booking history from the NDP
** Modification of name and patronymic
** Modifying selected booking content
** Adding content
** Content through WS - BSP
** Ability to book and check out BSP
** Booking for an infant seat
** Cancellation via app
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">

* From the props/settings.
** Adding a general purpose passive segment (misc segment)
** Discharge on airline stock
** Discharge runoff management
** AAA PCC handling
** Private commission authorization
** Airline server operations/requests
** Ticket issuance for the whole booking
** Additional ticketing for passengers who are on hold
** Checking airline commission at checkout
** Commission per passenger type
** Depositing endorsements
** Ticketing tour codes
** Ticket-designator setup
** GDS processing
** Multi-FOP GDS processing
** Proxying of GDS processing through the Payment Gateway
** Voiding
</div>
</div>

== Working Principle ==
Websky makes an update at every booking operation, and the PNR is automatically re-priced, except for the following situations:
*booking is cancelled
*booking is ticketed
Once a statement is requested, a transaction confirmation is performed so that the issued tickets are included in the PNR.
In case Websky may have problems while updating bookings, a check with DQB (sales report in GDS Sabre) will be made and tickets issued by PNR but not included in the PNR. If for some reason they are not entered, the booking will be marked as problematic and such bookings will need to be processed manually by the agent in the terminal.

== Connecting to GDS Sabre in Websky ==

In order to connect a Websky airline unit that works with Sabre system, the agency must have an agreement for Sabre system use. If the agency does not have such an agreement, it is necessary to contact the local Sabre office and enter into an agreement to use the system.

If the agency has a Sabre connection agreement, it means that the agency can use the Sabre system via terminals installed in the agency and create/cancel/modify bookings, control booking queues, calculate fares and issue tickets, book services of other suppliers (such as hotels, car rentals, etc).

The procedures of creating a configuration, setting up offices, ordering additional terminal addresses and printers are specified in the "Agreement for connection and access to Sabre information resources" and in the "Regulations of interaction between users of Sabre information resources and the Russia Sabre Help Desk" (both documents are available at [http://www.airts.ru www.airts.ru] in the "SabreOrder" section.

Sabre connects to the Websky system through a specially configured agency office called IPCC (Internet PCC - [[IPCC]]), which is ordered through a local Sabre representative office.

If the agency is not licensed to use the Sabre web service, it must:

# Write a letter to Sabre confirming that the agency intends to use the Websky system developed by LLC "Novaya Studiya" for online activity. At the same time, LLC "Novaya Studiya" should write a letter to Sabre confirming its readiness to provide the agency with such a service.

# Sign an additional contract with the local Sabre representative office for IPCC Downline Agency IPCC, pay for all the services mentioned in that contract and get the IPCC, login and password from Sabre, after that give the IPCC number, login and password to LLC "Novaya Studiya" for the connection details.

'''Attention!''' If the agency has its own Sabre web service license, the agency can obtain an IPCC as part of that license by contacting the local Sabre office. The IPCC number, username and password obtained should be given to "Novaya Studiya" to be entered into the connection requisites.

'''Attention!''' To ensure correct operation, the agency must order a LNIATA PRT TA - e-ticket or itinerary receipt printer address - if the booking and ticketing occurs in the IPCC and in the BSP environment.

If the agency plans to issue ETAT tickets (airline e-tickets) online, an additional terminal (for booking control work) and printer (for ETAT issuance) must also be ordered from Sabre.

If there is a sub-agency relationship with an agency which has an agreement with the airline to issue ETATs, a letter must be sent to the local Sabre office, signed and stamped on the agency letterhead, with a request to prescribe in the PCC where the ETATs will be issued the details of this agency as indicated in the agreement with the airline, namely: validator, company name and its address.

The PCC for ETAT can be ordered either by the agency or by a sub-agency.

If an agency or sub-agency orders a PCC to issue an ETAT, written confirmation from the airline must be obtained in order for that PCC to be activated. This letter may be sent by the airline directly to the local Sabre office or to the agency for onward transmission to Sabre.

Ordering additional PCCs, as well as printers, is done by filling out applications in SabreOrder, and linking of printers is carried out by Sabre support staff after creating and configuring PCCs.

'''Attention!''' For agencies located in Moscow, the parameter LOR (Location Of Request) in PCC must be set to MOW - this affects the correctness of work with some Russian airlines. For example, in the case of the value of SVO may not be confirmed seats on the airline SkyExpress.

==How to receive Sabre connection requisites to work in Websky==
To interact with GDS Sabre through Websky:
# Send a connection request to Sabre, get approval, create a ticket in [http://helpdesk.nemo.travel| project tracker] in which you provide the requisites you received (the ticket must be assigned to _SUPPORT RECEPTION).
# After you set up the requisites and successfully test the search, booking, and cancellation, Websky staff will return the ticket to the agency employee for testing the statement and entering in the set up details.

To interact with GDS Sabre through Websky, the agency must complete the following steps:
# Sign an agreement with Sabre and obtain a PCC.
# After getting the PCC, order online requisites to work with via Websky - IPCC. To do this, fill out an application form and send it to Sabre.
# After reviewing the application, Sabre will issue a username and password to connect to your IPCC. Provide them to Websky via [http://helpdesk.nemo.travel| project tracker] to set up your Sabre connection requisites in Websky.
# Additionally, you must order the BFM lookup option from Sabre. A separate questionnaire is filled out for this (the template is attached in the ''Sabre BFM Questionnaire'' section). The BFM opens for one month, until then only the LFS search is available.

To set up the ticketing process, you need to ask the Sabre helpdesk to do the settings for your BFM.

=== Sabre BFM Questionnaire ===
Sabre vendor has two search options: LFS and BFM. To obtain BFM requisites, you are asked to fill out the following questionnaire: [[File:BFM questionnaire.pdf]].

The questionnaire contains a total of 17 questions, some of which are required as background information. When filling out the questionnaire, you should pay attention to the following questions:
* Question #2, which specifies whether the reservation and checkout will take place on the same PCC.
* Question #3, which specifies the number of searches and their planned changes.
* Question #7, which specifies the planned number of transactions per day in test and environment and real mode.

An example of a completed questionnaire: [[File:BFM_questionnaire_example.pdf]]

=== Ticketing settings in Sabre ===

In order to run an electronic ticket checkout, the Ticketing Agency must write a letter to the Sabre Helpdesk (sabre.helpdesk@airts.ru) that reads as follows:
# Please open branch access level B,C between IPCC ''XXXX'' and PCC ''XXXX''
# Please add the key SUBAA for EPR 7971 (7972) for IPCC ''XXXX''
'''Attention!''' EPR is the agency account that matches the login listed in the established credentials. EPR 7971 (7972) is relevant for Sabre Russia. You can find the necessary EPR by the login, which is specified in the Nemo Connect '''Avia Settings - GDS Connection Settings - GDS Requisites - Sabre Requisites''' for the particular PCC.

Settings to check before running automatic ticketing from the agency website on the GDS side of Sabre:

# Option Store Passenger Type in PNR in TJR PCC/IPCC must be enabled.
# Option Auto Segment Arrange in TJR PCC/IPCC must be enabled.
# Option Auto Validation in TJR PCC/IPCC must be enabled.
# Option Russian Ticketing Platform in TJR PCC/IPCC must be enabled.
# Option Full Branch Access between booking IPCC and PCC must be configured.
# Option ETICKET IN EMAIL in TJR PCC/IPCC must be enabled.
# Option PRICE TICKETING ALERT in the TJR PCC/IPCC must be disabled.
# SUBAAA keyword must be present in the EPR of all agents/cashiers that handle reservations to be able to transition between PCC/IPCC.
# The presence of a printer terminal address (PTR TA) is required for issuing the PCC.
# IATA validator is required when using it as the primary for ticketing. Also, checking the carrier list against the IATA license. If own validator of carrier is used, for example Aeroflot, then it is necessary to order additional PCC for it.

The settings must be activated in all Sabre sections: TSTS, CERT, CUSTOMER ACCEPTANCE and PRODUCTION.

These settings must be verified at all PCC/IPCCs where you intend to book and issue tickets. To do this, contact the Sabre Helpdesk: sabre.helpdesk@airts.ru

And the obligatory point: it is necessary that in PCC (if IPCC will be used for issuing, ask to make settings for it), there should be carriers available for issuing with validator and its code. This is done through a service (it is a request system, each client has a login and password to it) sabreorder@airts.ru

=== Connection features===
* In Sabre, while setting up the PCC for the ticketing, the stock on the ticketing is specified. It means that it is crucial to specify who the validator is. In Websky settings, the printer is specified according to the stock.
*At the same time, the client performs all items specified [http://support.mute-lab.com/ru/Сейбр#.D0.9D.D0.B0.D1.81.D1.82.D1.80.D0.BE.D0.B9.D0.BA.D0.B8_.D0.B2.D1.8B.D0.BF.D0.B8.D1.81.D0.BA.D0.B8_.D0.B1.D0.B8.D0.BB.D0.B5.D1.82.D0.B0_.D0.B2_Sabre here] on his part.
*In the default settings, the printer type is OPTAT for the BSP stock. This means that the printer is assigned with the command: RU
*When the ticketing is performed on the stock of SU (Aeroflot) airline, printer type must be set to: Specialixed E-TAT, which means that the printer is controlled by the command 1R
*When the ticketing is performed on the stock of S7 (Siberia), U6 (Ural Airlines) airlines runoff the printer type must be set to Generic E-TAT, which means that the printer is assigned to a command: 1Y
*When checking out on Ukrainian RCC the printer is also assigned by another command, you must put the printer type: ATB, which means that the printer is assigned by the command: AT
* '''Attention!''' Make sure that the '''DivideInParty'' option is disabled '''on the supplier side'''. If the option is enabled, you will see a large number of price increases when you switch to booking.
*'''Attention!''' The '''Audit trail''' value in the Sabre-side PCC settings must be set to '''Regular audit trail'''.

== Features of working with Sabre==
* Strict requirements to agency names. If you violate the name requirements when booking services, you get errors of the following kind: '''Input data error'''.
** The agency name must not contain punctuation marks and Cyrillic characters; only Latin letters and spaces are allowed.
<br />"If you want the name to begin with numbers, set the first character to be a space - this will help you avoid the error."

* On the booking confirmation page, in the '''In the currency of the booking system''' column, prices are displayed in the currency of the airline fare.
* In response to the search request, the cheapest variants appear. So the '''2 adults + 1 child''' request may return the response '''3 adults'''.
* Sabre will reply to your search request with information about the baggage allowance.
* Bookings at GDS Sabre are strictly available for no more than 331 days in advance of the booking date. Sabre will return an error message like this: <code>SYSTEM UNABLE TO PROCESS: INVALID DATE</code>.
* In Sabre, when you issue a ticket for a child with the ''Birth Certificate'' document type, the itinerary receipt shows the document type ''Substitute Document'', because Sabre does not support the ''Birth Certificate'' document type.
* When searching for Business class tickets, if there are no suitable Business class flights, Sabre can send you Economy class flights. However, the system may also send first class fares if their price is equal or less than business class fares.
* In GDS Sabre, there are situations when the airline removes successfully taken seats immediately after the booking is made (including using the ''RebookForLowest'' option).
* In GDS Sabre, there are situations when it is obligatory to pay by credit card for the seats or ancillary services in the booking; in this case, the following error message will be shown at the ticketing stage: UNABLE - ONLY CREDIT CARD FORM OF PAYMENT ALLOWED.
* In GDS Sabre, there are the following limitations on the length of characters in the name in the PNR:
** Maximum number of characters for last name and first name combined is 58.
** Maximum number of characters for last name, first name and middle name in total - 57.
** If the passenger is female, the above values are reduced by 1.
** Maximal number of characters for last name is 30. <br />Websky [[Booking Form (Air Tickets)|booking form]] limits number of characters for passenger's last name in order to meet the above limitations and avoid mistakes in booking.
** Maximal number of characters for name on SU airline is 29.
** '''Attention!''' Spaces are also symbols and count in the calculation.
** The number of passengers per online booking is limited. The airline itself determines the maximum number of passengers per booking. For example, on Aeroflot - 7 passengers, on Ural Airlines - 5 passengers. To prevent errors, the agency can limit the number of passengers in an order for all airlines in Websky using the ''Maximum number of people in a search request'' parameter in the '''Product control → Flight tickets → Outdated settings → Search restrictions''' section.
* If there are a large number of flight price increases when you switch to a booking, make sure that the '''DivideInParty'' option is disabled '''on the supplier side'''.
* If, when a ticket is being issued, the following message is received: '''The order contains issued tickets that are not presented in the PNR''' and there are 2 ticket numbers for one passenger in the order - a common case when working in Sabre/<br />To manage cases of double ticketing, Nemo Connect has the option ''Action with valid tickets not in the PNR'' (in '''Profiles → User Profiles'''):
** ''Mark as Problematic'' - in this case the manager will receive a notification about the problem booking;
** ''Auto-voiding'' - a ticket not in the PNR (''extra'') will be entered, while the integrity of the order will be preserved.
* '''Accounting for changes in GDS.''' In order to, when multiplying flights and when using the results of searches from the cache (see [[Cache Server]]) when amounts need to be converted correctly, exchange rates from GDS Sabre must have the BSRDSP keyword in EPR for all PCCs (settings on the Sabre side, contact GDS support for setup), see [[Cache Server#Accounting for fare changes in GDS|Accounting for fare changes in GDS]].

== Agency Commission Display in GDS Sabre ==

Agency commission is assigned to the agency by the airline in accordance with the contract. The commission can be the same for any transportation, but may differ by destinations, countries, types of flights.

In any case, the commission is not displayed neither in the e-ticket, nor in the itinerary receipt.

For the booking created in Sabre the informational price of the flight is displayed on the screen by the PQ command. When working with the terminal, the agent can calculate the price of the flight with the commission, since while creating the booking he can know on which carrier's form the transportation will be performed. In this case the commission is displayed in the PQ command results.

When working online, the commission parameters are determined only at the ticketing step, so the informational price of transportation in our case does not include the commission. It means that the PQ command displays the total price of the flight.

In Sabre terminal the commission for a particular booking can be viewed by displaying the booking on the screen and opening the Accounting Data section with the *PAC command - all the information on the ticket, which includes data on the commission, is displayed.

The [[commission]] is not printed on the [[electronic ticket]], you can only see it in the prototype of the paper ticket on the basis of which the [[electronic ticket]] is issued. In the itinerary receipt the commission is also not displayed.

In addition to the ability to see the airline commission in the booking by *PAC command, the agent can call the DQB* sales report, in which you can see the amount of commission for the booking you are interested in.

==Supported features==

GDS Sabre supports the following options implemented in Websky:

* '''Rebooking for the lowest price''' (''RebookForLowestPrice'', ''rebookForLowest'') - the option allows you to get the current booking/flight price not for the specified flight class letters (seats that may run out; or the price might be unavailable or might not be the cheapest), but to generally get the cheapest available price for the given flight within the same base class (Economy/Business/Premium Economy, etc.) as the original literature, with the GDS automatically checking the availability of the required number of vacant seats.

*[[Synchronization of orders]] - synchronization module for GDS Sabre supplier is implemented.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors when working with Sabre ==
<div class="mw-collapsible-content">

=== Search errors ===
{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" |'''Common errors for all GDSs'''
|-
|<code> SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR</code>
| width="70%"| In the boooking operation, there is a parallel change of PNR. In this case you have to start the operation again.
|-
|<code> Possible IC throttle Text: java.util.NoSuchElementException: Pool exhausted </code>
|width="70%"| This error occurs because of active work. It's worth noting that the error is not critical and occurs to block traffic and prevent overloading on the GDS side.
|-
| <code>Invalid search reguest object</code>
|This error occurs when an invalid search result is accessed. Possible causes:
# invalid search link;
# search result may be out of date.
|-
|}

=== Ticketing errors ===

{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" | '''For the PROD environment'''
|-
| <code>AUTH CARRIER INVLD-0166</code> (<code>auth_error</code>)
|width="70%"| On the GDS side, the specified validating carrier is not in the list of authorized carriers for the ticketing. Or, the settings mentioned above (3 points) are not performed in full!
|-
|<code>"TICKETING IN ALTERNATE CURRENCY NOT ALLOWED-0106" and "SEE W/CURR*-CANNOT TICKET IN CURRENCY REQUESTED-0106</code>"
|Restriction of ticketing in the specified currency.
|-
|<code> 9999.99 IS THE MAXIMUM AMOUNT OF COMMISSION-0265</code>
| Incorrect rounding of commissions.
|-
|<code>NO COMBINABLE FARES FOR CLASS USED53</code?
|It is impossible to calculate the fare (in the Websky system such situations cannot be handled).
|-
|<code>Error response received. The error was: CODE - HX SEG STATUS NOT ALLOWED</code>.
|The flight contains segments cancelled by the airline.
|-
|<code>VALIDATING CARRIER XW DOES NOT HAVE AGREEMENT WITH D9-0322</code>
|No interline agreement between airlines (cannot be processed by Websky at this time).
|-
|<code>EACH PASSENGER MUST HAVE SSR FOID-0052</code>
|No FOID data transmitted, connection requisites for TCP flights need to be checked.
|-
|<code>validation_error (VALIDATING CARRIER UN DOES NOT HAVE AGREEMENT WITH S7-0322)</code>
| There is no interline agreement between the airlines flying, such tickets can only be issued separately.
|-
|<code>TERM NOT HARDCOPY</code>.
|The Websky LNIATA PRT TA (e-ticket printer address) in the ticketing settings is incorrect.
|-
|<code>153 NAME DOES NOT MATCH NAME IN AIRLINE SYSTEM</code>
|Exceeded allowed number of characters in passenger's name
|-
!colspan="2" |'''For CERT environment'''
|-
|<code>UNABLE TO PROCESS ETR-CORRECT/RETRY OR ISSUE PAPER TICKET-368 AGENCY NOT ALLOWED TO ISSUE ELECTRONIC TICKETING</code>
|Error comes from the supplier and may be due to the fact that the work takes place in different environments (CERT, TSTS). To test in a CERT environment, you must use one of the following carriers: AA, SU, B6, KM, IT, HA,WS.
|-
|<code>NEED AIRLINE PNR LOCATOR - VERIFY AND ENTER IN SEGMENT-0052</code>
|The error occurs because a CERT environment is being used.
|-
|<code>VERIFY TKT TTL RUB 1663 - PQ TTL RUB 1563 TICKET? ENTER Y or N<.></code>
|In Sabre, there is a price comparison at the booking and at the checkout.
|-
|}

===Cancellation mistakes ===
{| class="wikitable"
|-
! Error
! Description
|-
|<code>OTH RESTRICTIONS APPLY-REBOOK OTH NO LATER THAN 04MAY</code>
|width="70%"|The error is due to the features of the rules for creating OTH segments in GDS Sabre. As of June 5, 2017, new rules for creating OTH segments (which are used to extend the lifetime of a booking in the system after all flights have been completed) were introduced, the essence of which is that it is prohibited to add OTH segments with a date the departure date of the last active segment in the booking by 180 days, and if there are no active segments in the booking, but they are in the history, it is prohibited to add an OTH segment with a date 180 days higher than the current date (for example, the booking was made on November 5, 2017, then the clearance date plus 180 days - turns out to be May 4).
|-
|}
</div>
</div>

== Airline ancillary services ==
In Sabre additional services are available for any PCC by default, no additional settings are required from Sabre.<br>
To enable work with advanced services in Websky you have to enable the checkbox "Enable work with advanced services in this package" in the "Airline settings" -> "Airline packages" section of the Sabre "Airline details package". <br>
'''Attention!''' To display additional services on your website, you need to fill in the section "Additional services" in the Guide in the Administration panel of Websky 2.0. Only Websky system administrator can fill it in.

== Contact info ==

Sabre Russian representative office: 125009, Moscow, Tverskaya str. 16, bld.3, office 14, tel: (499) 929 5080.

Sales Department: (499) 929-5080 or (499) 929-5090

Technical Support and Helpdesk Russia: +7 495 974-8951

== See also ==
*[[IPCC]]
*[[Endorsement#Requirements for endorsements in Sabre|Requirements for endorsements in Sabre]]
*[[GDS|Data on resources and the Sabre distribution network]]
*[[Ticket printer#Sabre ticket printer|Sabre ticket printers]]
*[[Statistics#Supplier statistics|Supplier statistics]]
*[[Ticket#Functional capabilities of airline ticket suppliers| Functional capabilities of airline ticket suppliers]]
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Amadeus]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[API VIP Service]]
* [[Nemo Inventory (component)]]

== Useful links ==
*[http://www.sabre.com Sabre Holdings website]
*[http://www.sabretravelnetwork.ru/home Sabre Travel Network website]
*[http://www.sabretravelnetwork.ru/home/products_services/product_index Sabre products]
*[http://www.tch.ru/rus/products/1s/ Steps to enable electronic and automated issuance of NSAW TCH tickets through Sabre (GDS Sabre) at accredited agencies]
*[http://support.mute-lab.com/ru/%D0%9F%D1%80%D0%BE%D1%86%D0%B5%D1%81%D1%81%D0%B8%D0%BD%D0%B3#.D0.90.D0.B2.D0.B8.D0.B0.D0.BA.D0.BE.D0.BC.D0.BF.D0.B0.D0.BD.D0.B8.D0.B8.2C_.D0.BF.D1.80.D0.B8.D0.BD.D0.B8.D0.BC.D0.B0.D1.8E.D1.89.D0.B8.D0.B5_.D0.BE.D0.BF.D0.BB.D0.B0.D1.82.D1.83_.D0.BA.D1.80.D0.B5.D0.B4.D0.B8.D1.82.D0.BD.D1.8B.D0.BC.D0.B8_.D0.BA.D0.B0.D1.80.D1.82.D0.B0.D0.BC.D0.B8_.D1.87.D0.B5.D1.80.D0.B5.D0.B7_GDS List of airlines that accept credit card payments through GDS Sabre]

Sabre

2021-01-24T15:47:04Z

I shaletin: Created page with "'''Sabre Travel Network''' (Sabre) — a part of the group of companies Sabre Holdings (USA), serving travel agencies, travel service providers, corporations and government ag..."

'''Sabre Travel Network''' (Sabre) — a part of the group of companies Sabre Holdings (USA), serving travel agencies, travel service providers, corporations and government agencies in 59 countries around the world.

== Description ==
Sabre processes more than 19,000 transactions per second - about 2 billion transactions every day.

Mute Lab Software is an official certified developer on Sabre Web Services.

Booking system [https://websky.aero/ Websky] supports ticket sales through Sabre global distribution system.

== Key Features ==

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">

* Search by nearest dates
* Search by public + private fares
* Search for private fares
* Search by schedule
* Search by J-types.
* Sending terminal commands
* Search with limited prices
* Returning the Refundable attribute in search results - BFM
* Return e-ticket attribute in search results
* Returning a ticketing deadline in search results
* Validating carrier in search results
* Checking interlines in search results
* Maximum number of passengers of all types in the search request is 32
* Number of passengers of one type in the request is 8

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">

* From the requisites/settings
** Hiding the price on the GDS site
** Adding a passenger title
** RebookForLowestPrice[[#FAQ on GDS/GDS/API Sabre|<sup>[1]</sup>]]
** Remarks (in requisites) for booking entries
** Working with AAA PCC
** Repeating of seats taking when getting NN status
* Additional operations with requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat assignment
** Receiving a Seat Map
** Updating the price
** Getting a list of available credit cards
** Getting a currency rate
** Maximum number of simultaneous sessions - 50 standard, extensions of 25 sessions
** Returning fare types - Public, Nego
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Ticket availability check outside of NDP
** Import of bookings via NDP locator
** Retrieving booking history from the NDP
** Modification of name and patronymic
** Modifying selected booking content
** Adding content
** Content through WS - BSP
** Ability to book and check out BSP
** Booking for an infant seat
** Cancellation via app
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">

* From the props/settings.
** Adding a general purpose passive segment (misc segment)
** Discharge on airline stock
** Discharge runoff management
** AAA PCC handling
** Private commission authorization
** Airline server operations/requests
** Ticket issuance for the whole booking
** Additional ticketing for passengers who are on hold
** Checking airline commission at checkout
** Commission per passenger type
** Depositing endorsements
** Ticketing tour codes
** Ticket-designator setup
** GDS processing
** Multi-FOP GDS processing
** Proxying of GDS processing through the Payment Gateway
** Voiding
</div>
</div>

== Working Principle ==
Websky makes an update at every booking operation, and the PNR is automatically re-priced, except for the following situations:
*booking is cancelled
*booking is ticketed
Once a statement is requested, a transaction confirmation is performed so that the issued tickets are included in the PNR.
In case Websky may have problems while updating bookings, a check with DQB (sales report in GDS Sabre) will be made and tickets issued by PNR but not included in the PNR. If for some reason they are not entered, the booking will be marked as problematic and such bookings will need to be processed manually by the agent in the terminal.

== Connecting to GDS Sabre in Websky ==

In order to connect a Websky airline unit that works with Sabre system, the agency must have an agreement for Sabre system use. If the agency does not have such an agreement, it is necessary to contact the local Sabre office and enter into an agreement to use the system.

If the agency has a Sabre connection agreement, it means that the agency can use the Sabre system via terminals installed in the agency and create/cancel/modify bookings, control booking queues, calculate fares and issue tickets, book services of other suppliers (such as hotels, car rentals, etc).

The procedures of creating a configuration, setting up offices, ordering additional terminal addresses and printers are specified in the "Agreement for connection and access to Sabre information resources" and in the "Regulations of interaction between users of Sabre information resources and the Russia Sabre Help Desk" (both documents are available at [http://www.airts.ru www.airts.ru] in the "SabreOrder" section.

Sabre connects to the Websky system through a specially configured agency office called IPCC (Internet PCC - [[IPCC]]), which is ordered through a local Sabre representative office.

If the agency is not licensed to use the Sabre web service, it must:

# Write a letter to Sabre confirming that the agency intends to use the Websky system developed by LLC "Novaya Studiya" for online activity. At the same time, LLC "Novaya Studiya" should write a letter to Sabre confirming its readiness to provide the agency with such a service.

# Sign an additional contract with the local Sabre representative office for IPCC Downline Agency IPCC, pay for all the services mentioned in that contract and get the IPCC, login and password from Sabre, after that give the IPCC number, login and password to LLC "Novaya Studiya" for the connection details.

'''Attention!''' If the agency has its own Sabre web service license, the agency can obtain an IPCC as part of that license by contacting the local Sabre office. The IPCC number, username and password obtained should be given to "Novaya Studiya" to be entered into the connection requisites.

'''Attention!''' To ensure correct operation, the agency must order a LNIATA PRT TA - e-ticket or itinerary receipt printer address - if the booking and ticketing occurs in the IPCC and in the BSP environment.

If the agency plans to issue ETAT tickets (airline e-tickets) online, an additional terminal (for booking control work) and printer (for ETAT issuance) must also be ordered from Sabre.

If there is a sub-agency relationship with an agency which has an agreement with the airline to issue ETATs, a letter must be sent to the local Sabre office, signed and stamped on the agency letterhead, with a request to prescribe in the PCC where the ETATs will be issued the details of this agency as indicated in the agreement with the airline, namely: validator, company name and its address.

The PCC for ETAT can be ordered either by the agency or by a sub-agency.

If an agency or sub-agency orders a PCC to issue an ETAT, written confirmation from the airline must be obtained in order for that PCC to be activated. This letter may be sent by the airline directly to the local Sabre office or to the agency for onward transmission to Sabre.

Ordering additional PCCs, as well as printers, is done by filling out applications in SabreOrder, and linking of printers is carried out by Sabre support staff after creating and configuring PCCs.

'''Attention!''' For agencies located in Moscow, the parameter LOR (Location Of Request) in PCC must be set to MOW - this affects the correctness of work with some Russian airlines. For example, in the case of the value of SVO may not be confirmed seats on the airline SkyExpress.

==How to receive Sabre connection requisites to work in Websky==
To interact with GDS Sabre through Websky:
# Send a connection request to Sabre, get approval, create a ticket in [http://helpdesk.nemo.travel| project tracker] in which you provide the requisites you received (the ticket must be assigned to _SUPPORT RECEPTION).
# After you set up the requisites and successfully test the search, booking, and cancellation, Websky staff will return the ticket to the agency employee for testing the statement and entering in the set up details.

To interact with GDS Sabre through Websky, the agency must complete the following steps:
# Sign an agreement with Sabre and obtain a PCC.
# After getting the PCC, order online requisites to work with via Websky - IPCC. To do this, fill out an application form and send it to Sabre.
# After reviewing the application, Sabre will issue a username and password to connect to your IPCC. Provide them to Websky via [http://helpdesk.nemo.travel| project tracker] to set up your Sabre connection requisites in Websky.
# Additionally, you must order the BFM lookup option from Sabre. A separate questionnaire is filled out for this (the template is attached in the ''Sabre BFM Questionnaire'' section). The BFM opens for one month, until then only the LFS search is available.

To set up the ticketing process, you need to ask the Sabre helpdesk to do the settings for your BFM.

=== Sabre BFM Questionnaire ===
Sabre vendor has two search options: LFS and BFM. To obtain BFM requisites, you are asked to fill out the following questionnaire: [[File:BFM questionnaire.pdf]].

The questionnaire contains a total of 17 questions, some of which are required as background information. When filling out the questionnaire, you should pay attention to the following questions:
* Question #2, which specifies whether the reservation and checkout will take place on the same PCC.
* Question #3, which specifies the number of searches and their planned changes.
* Question #7, which specifies the planned number of transactions per day in test and environment and real mode.

An example of a completed questionnaire: [[File:BFM_questionnaire_example.pdf]]

=== Ticketing settings in Sabre ===

In order to run an electronic ticket checkout, the Ticketing Agency must write a letter to the Sabre Helpdesk (sabre.helpdesk@airts.ru) that reads as follows:
# Please open branch access level B,C between IPCC ''XXXX'' and PCC ''XXXX''
# Please add the key SUBAA for EPR 7971 (7972) for IPCC ''XXXX''
'''Attention!''' EPR is the agency account that matches the login listed in the established credentials. EPR 7971 (7972) is relevant for Sabre Russia. You can find the necessary EPR by the login, which is specified in the Nemo Connect '''Avia Settings - GDS Connection Settings - GDS Requisites - Sabre Requisites''' for the particular PCC.

Settings to check before running automatic ticketing from the agency website on the GDS side of Sabre:

# Option Store Passenger Type in PNR in TJR PCC/IPCC must be enabled.
# Option Auto Segment Arrange in TJR PCC/IPCC must be enabled.
# Option Auto Validation in TJR PCC/IPCC must be enabled.
# Option Russian Ticketing Platform in TJR PCC/IPCC must be enabled.
# Option Full Branch Access between booking IPCC and PCC must be configured.
# Option ETICKET IN EMAIL in TJR PCC/IPCC must be enabled.
# Option PRICE TICKETING ALERT in the TJR PCC/IPCC must be disabled.
# SUBAAA keyword must be present in the EPR of all agents/cashiers that handle reservations to be able to transition between PCC/IPCC.
# The presence of a printer terminal address (PTR TA) is required for issuing the PCC.
# IATA validator is required when using it as the primary for ticketing. Also, checking the carrier list against the IATA license. If own validator of carrier is used, for example Aeroflot, then it is necessary to order additional PCC for it.

The settings must be activated in all Sabre sections: TSTS, CERT, CUSTOMER ACCEPTANCE and PRODUCTION.

These settings must be verified at all PCC/IPCCs where you intend to book and issue tickets. To do this, contact the Sabre Helpdesk: sabre.helpdesk@airts.ru

And the obligatory point: it is necessary that in PCC (if IPCC will be used for issuing, ask to make settings for it), there should be carriers available for issuing with validator and its code. This is done through a service (it is a request system, each client has a login and password to it) sabreorder@airts.ru

=== Connection features===
* In Sabre, while setting up the PCC for the ticketing, the stock on the ticketing is specified. It means that it is crucial to specify who the validator is. In Websky settings, the printer is specified according to the stock.
*At the same time, the client performs all items specified [http://support.mute-lab.com/ru/Сейбр#.D0.9D.D0.B0.D1.81.D1.82.D1.80.D0.BE.D0.B9.D0.BA.D0.B8_.D0.B2.D1.8B.D0.BF.D0.B8.D1.81.D0.BA.D0.B8_.D0.B1.D0.B8.D0.BB.D0.B5.D1.82.D0.B0_.D0.B2_Sabre here] on his part.
*In the default settings, the printer type is OPTAT for the BSP stock. This means that the printer is assigned with the command: RU
*When the ticketing is performed on the stock of SU (Aeroflot) airline, printer type must be set to: Specialixed E-TAT, which means that the printer is controlled by the command 1R
*When the ticketing is performed on the stock of S7 (Siberia), U6 (Ural Airlines) airlines runoff the printer type must be set to Generic E-TAT, which means that the printer is assigned to a command: 1Y
*When checking out on Ukrainian RCC the printer is also assigned by another command, you must put the printer type: ATB, which means that the printer is assigned by the command: AT
* '''Attention!''' Make sure that the '''DivideInParty'' option is disabled '''on the supplier side'''. If the option is enabled, you will see a large number of price increases when you switch to booking.
*'''Attention!''' The '''Audit trail''' value in the Sabre-side PCC settings must be set to '''Regular audit trail'''.

== Features of working with Sabre==
* Strict requirements to agency names. If you violate the name requirements when booking services, you get errors of the following kind: '''Input data error'''.
** The agency name must not contain punctuation marks and Cyrillic characters; only Latin letters and spaces are allowed.
<br />"If you want the name to begin with numbers, set the first character to be a space - this will help you avoid the error."

* On the booking confirmation page, in the '''In the currency of the booking system''' column, prices are displayed in the currency of the airline fare.
* In response to the search request, the cheapest variants appear. So the '''2 adults + 1 child''' request may return the response '''3 adults'''.
* Sabre will reply to your search request with information about the baggage allowance.
* Bookings at GDS Sabre are strictly available for no more than 331 days in advance of the booking date. Sabre will return an error message like this: <code>SYSTEM UNABLE TO PROCESS: INVALID DATE</code>.
* In Sabre, when you issue a ticket for a child with the ''Birth Certificate'' document type, the itinerary receipt shows the document type ''Substitute Document'', because Sabre does not support the ''Birth Certificate'' document type.
* When searching for Business class tickets, if there are no suitable Business class flights, Sabre can send you Economy class flights. However, the system may also send first class fares if their price is equal or less than business class fares.
* In GDS Sabre, there are situations when the airline removes successfully taken seats immediately after the booking is made (including using the ''RebookForLowest'' option).
* In GDS Sabre, there are situations when it is obligatory to pay by credit card for the seats or ancillary services in the booking; in this case, the following error message will be shown at the ticketing stage: UNABLE - ONLY CREDIT CARD FORM OF PAYMENT ALLOWED.
* In GDS Sabre, there are the following limitations on the length of characters in the name in the PNR:
** Maximum number of characters for last name and first name combined is 58.
** Maximum number of characters for last name, first name and middle name in total - 57.
** If the passenger is female, the above values are reduced by 1.
** Maximal number of characters for last name is 30. <br />Websky [[Booking Form (Air Tickets)|booking form]] limits number of characters for passenger's last name in order to meet the above limitations and avoid mistakes in booking.
** Maximal number of characters for name on SU airline is 29.
** '''Attention!''' Spaces are also symbols and count in the calculation.
** The number of passengers per online booking is limited. The airline itself determines the maximum number of passengers per booking. For example, on Aeroflot - 7 passengers, on Ural Airlines - 5 passengers. To prevent errors, the agency can limit the number of passengers in an order for all airlines in Websky using the ''Maximum number of people in a search request'' parameter in the '''Product control → Flight tickets → Outdated settings → Search restrictions''' section.
* If there are a large number of flight price increases when you switch to a booking, make sure that the '''DivideInParty'' option is disabled '''on the supplier side'''.
* If, when a ticket is being issued, the following message is received: '''The order contains issued tickets that are not presented in the PNR''' and there are 2 ticket numbers for one passenger in the order - a common case when working in Sabre/<br />To manage cases of double ticketing, Nemo Connect has the option ''Action with valid tickets not in the PNR'' (in '''Profiles → User Profiles'''):
** ''Mark as Problematic'' - in this case the manager will receive a notification about the problem booking;
** ''Auto-voiding'' - a ticket not in the PNR (''extra'') will be entered, while the integrity of the order will be preserved.
* '''Accounting for changes in GDS.''' In order to, when multiplying flights and when using the results of searches from the cache (see [[Cache Server]]) when amounts need to be converted correctly, exchange rates from GDS Sabre must have the BSRDSP keyword in EPR for all PCCs (settings on the Sabre side, contact GDS support for setup), see [[Cache Server#Accounting for fare changes in GDS|Accounting for fare changes in GDS]].

== Agency Commission Display in GDS Sabre ==

Agency commission is assigned to the agency by the airline in accordance with the contract. The commission can be the same for any transportation, but may differ by destinations, countries, types of flights.

In any case, the commission is not displayed neither in the e-ticket, nor in the itinerary receipt.

For the booking created in Sabre the informational price of the flight is displayed on the screen by the PQ command. When working with the terminal, the agent can calculate the price of the flight with the commission, since while creating the booking he can know on which carrier's form the transportation will be performed. In this case the commission is displayed in the PQ command results.

When working online, the commission parameters are determined only at the ticketing step, so the informational price of transportation in our case does not include the commission. It means that the PQ command displays the total price of the flight.

In Sabre terminal the commission for a particular booking can be viewed by displaying the booking on the screen and opening the Accounting Data section with the *PAC command - all the information on the ticket, which includes data on the commission, is displayed.

The [[commission]] is not printed on the [[electronic ticket]], you can only see it in the prototype of the paper ticket on the basis of which the [[electronic ticket]] is issued. In the itinerary receipt the commission is also not displayed.

In addition to the ability to see the airline commission in the booking by *PAC command, the agent can call the DQB* sales report, in which you can see the amount of commission for the booking you are interested in.

==Supported features==

GDS Sabre supports the following options implemented in Websky:

* '''Rebooking for the lowest price''' (''RebookForLowestPrice'', ''rebookForLowest'') - the option allows you to get the current booking/flight price not for the specified flight class letters (seats that may run out; or the price might be unavailable or might not be the cheapest), but to generally get the cheapest available price for the given flight within the same base class (Economy/Business/Premium Economy, etc.) as the original literature, with the GDS automatically checking the availability of the required number of vacant seats.

*[[Synchronization of orders]] - synchronization module for GDS Sabre supplier is implemented.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors when working with Sabre ==
<div class="mw-collapsible-content">

=== Search errors ===
{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" |'''Common errors for all GDSs'''
|-
|<code> SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR</code>
| width="70%"| In the boooking operation, there is a parallel change of PNR. In this case you have to start the operation again.
|-
|<code> Possible IC throttle Text: java.util.NoSuchElementException: Pool exhausted </code>
|width="70%"| This error occurs because of active work. It's worth noting that the error is not critical and occurs to block traffic and prevent overloading on the GDS side.
|-
| <code>Invalid search reguest object</code>
|This error occurs when an invalid search result is accessed. Possible causes:
# invalid search link;
# search result may be out of date.
|-
|}

=== Ticketing errors ===

{| class="wikitable"
|-
! Error
! Description
|-
!colspan="2" | '''For the PROD environment'''
|-
| <code>AUTH CARRIER INVLD-0166</code> (<code>auth_error</code>)
|width="70%"| On the GDS side, the specified validating carrier is not in the list of authorized carriers for the ticketing. Or, the settings mentioned above (3 points) are not performed in full!
|-
|<code>"TICKETING IN ALTERNATE CURRENCY NOT ALLOWED-0106" and "SEE W/CURR*-CANNOT TICKET IN CURRENCY REQUESTED-0106</code>"
|Restriction of ticketing in the specified currency.
|-
|<code> 9999.99 IS THE MAXIMUM AMOUNT OF COMMISSION-0265</code>
| Incorrect rounding of commissions.
|-
|<code>NO COMBINABLE FARES FOR CLASS USED53</code?
|It is impossible to calculate the fare (in the Websky system such situations cannot be handled).
|-
|<code>Error response received. The error was: CODE - HX SEG STATUS NOT ALLOWED</code>.
|The flight contains segments cancelled by the airline.
|-
|<code>VALIDATING CARRIER XW DOES NOT HAVE AGREEMENT WITH D9-0322</code>
|No interline agreement between airlines (cannot be processed by Websky at this time).
|-
|<code>EACH PASSENGER MUST HAVE SSR FOID-0052</code>
|No FOID data transmitted, connection requisites for TCP flights need to be checked.
|-
|<code>validation_error (VALIDATING CARRIER UN DOES NOT HAVE AGREEMENT WITH S7-0322)</code>
| There is no interline agreement between the airlines flying, such tickets can only be issued separately.
|-
|<code>TERM NOT HARDCOPY</code>.
|The Websky LNIATA PRT TA (e-ticket printer address) in the ticketing settings is incorrect.
|-
|<code>153 NAME DOES NOT MATCH NAME IN AIRLINE SYSTEM</code>
|Exceeded allowed number of characters in passenger's name
|-
!colspan="2" |'''For CERT environment'''
|-
|<code>UNABLE TO PROCESS ETR-CORRECT/RETRY OR ISSUE PAPER TICKET-368 AGENCY NOT ALLOWED TO ISSUE ELECTRONIC TICKETING</code>
|Error comes from the supplier and may be due to the fact that the work takes place in different environments (CERT, TSTS). To test in a CERT environment, you must use one of the following carriers: AA, SU, B6, KM, IT, HA,WS.
|-
|<code>NEED AIRLINE PNR LOCATOR - VERIFY AND ENTER IN SEGMENT-0052</code>
|The error occurs because a CERT environment is being used.
|-
|<code>VERIFY TKT TTL RUB 1663 - PQ TTL RUB 1563 TICKET? ENTER Y or N<.></code>
|In Sabre, there is a price comparison at the booking and at the checkout.
|-
|}

===Cancellation mistakes ===
{| class="wikitable"
|-
! Error
! Description
|-
|<code>OTH RESTRICTIONS APPLY-REBOOK OTH NO LATER THAN 04MAY</code>
|width="70%"|The error is due to the features of the rules for creating OTH segments in GDS Sabre. As of June 5, 2017, new rules for creating OTH segments (which are used to extend the lifetime of a booking in the system after all flights have been completed) were introduced, the essence of which is that it is prohibited to add OTH segments with a date the departure date of the last active segment in the booking by 180 days, and if there are no active segments in the booking, but they are in the history, it is prohibited to add an OTH segment with a date 180 days higher than the current date (for example, the booking was made on November 5, 2017, then the clearance date plus 180 days - turns out to be May 4).
|-
|}
</div>
</div>

== Airline ancillary services ==
In Sabre additional services are available for any PCC by default, no additional settings are required from Sabre.<br>
To enable work with advanced services in Websky you have to enable the checkbox "Enable work with advanced services in this package" in the "Airline settings" -> "Airline packages" section of the Sabre "Airline details package". <br>
'''Attention!''' To display additional services on your website, you need to fill in the section "Additional services" in the Guide in the Administration panel of Websky 2.0. Only Websky system administrator can fill it in.

== Contact info ==

Sabre Russian representative office: 125009, Moscow, Tverskaya str. 16, bld.3, office 14, tel: (499) 929 5080.

Sales Department: (499) 929-5080 or (499) 929-5090

Technical Support and Helpdesk Russia: +7 495 974-8951

== See also ==
*[[IPCC]]
*[[Endorsement#Requirements for endorsements in Sabre|Requirements for endorsements in Sabre]]
*[[GDS|Data on resources and the Sabre distribution network]]
*[[Ticket printer#Sabre ticket printer|Sabre ticket printers]]
*[[Statistics#Supplier statistics|Supplier statistics]]
*[[Ticket#Functional capabilities of airline ticket suppliers| Functional capabilities of airline ticket suppliers]]
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Amadeus]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[API ВИП Сервис (Vip Service)]]
* [[Nemo Inventory (component)]]

== Useful links ==
*[http://www.sabre.com Sabre Holdings website]
*[http://www.sabretravelnetwork.ru/home Sabre Travel Network website]
*[http://www.sabretravelnetwork.ru/home/products_services/product_index Sabre products]
*[http://www.tch.ru/rus/products/1s/ Steps to enable electronic and automated issuance of NSAW TCH tickets through Sabre (GDS Sabre) at accredited agencies]
*[http://support.mute-lab.com/ru/%D0%9F%D1%80%D0%BE%D1%86%D0%B5%D1%81%D1%81%D0%B8%D0%BD%D0%B3#.D0.90.D0.B2.D0.B8.D0.B0.D0.BA.D0.BE.D0.BC.D0.BF.D0.B0.D0.BD.D0.B8.D0.B8.2C_.D0.BF.D1.80.D0.B8.D0.BD.D0.B8.D0.BC.D0.B0.D1.8E.D1.89.D0.B8.D0.B5_.D0.BE.D0.BF.D0.BB.D0.B0.D1.82.D1.83_.D0.BA.D1.80.D0.B5.D0.B4.D0.B8.D1.82.D0.BD.D1.8B.D0.BC.D0.B8_.D0.BA.D0.B0.D1.80.D1.82.D0.B0.D0.BC.D0.B8_.D1.87.D0.B5.D1.80.D0.B5.D0.B7_GDS List of airlines that accept credit card payments through GDS Sabre]

File:BFM questionnaire example.pdf

2021-01-24T14:47:55Z

I shaletin:

Amadeus

2020-12-27T08:22:38Z

I shaletin: /* Errors in interaction with GDS/GDS/API Amadeus */

[[File:Logo Amadeus.png|200px|right]]
[[File:450px-Amadeus.jpg|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field'''''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" | PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200" |
|-
| width="300" | Service Password
| width="200" |
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

=== Errors in interaction with GDS/GDS/API Amadeus ===

<div class="mw-collapsible-content">
'''Search errors'''<br />
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

Amadeus

2020-12-27T08:22:25Z

I shaletin: /* Errors in interaction with GDS/GDS/API Amadeus */

[[File:Logo Amadeus.png|200px|right]]
[[File:450px-Amadeus.jpg|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field'''''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" | PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200" |
|-
| width="300" | Service Password
| width="200" |
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

=== Errors in interaction with GDS/GDS/API Amadeus ===

<div class="mw-collapsible-content">
'''Search errors'''<br />.
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

Amadeus

2020-12-27T08:21:42Z

I shaletin: /* Gateway setup in Websky */

[[File:Logo Amadeus.png|200px|right]]
[[File:450px-Amadeus.jpg|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field'''''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" | PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200" |
|-
| width="300" | Service Password
| width="200" |
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS/GDS/API Amadeus==

<div class="mw-collapsible-content">
'''Search errors'''<br />.
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

Amadeus

2020-12-27T08:21:04Z

I shaletin:

[[File:Logo Amadeus.png|200px|right]]
[[File:450px-Amadeus.jpg|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200"
|-
| width="300" | Service Password
| width="200"
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS/GDS/API Amadeus==

<div class="mw-collapsible-content">
'''Search errors'''<br />.
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

Amadeus

2020-12-27T08:19:54Z

I shaletin:

[[File:Logo Amadeus.png|200px|right]]
[[File:450px-Amadeus|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200"
|-
| width="300" | Service Password
| width="200"
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS/GDS/API Amadeus==

<div class="mw-collapsible-content">
'''Search errors'''<br />.
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

Amadeus

2020-12-27T08:19:13Z

I shaletin: Created page with "right Amadeus headquarters building in Madrid Amadeus, one of the world's largest GDS, provides airl..."

[[File:Logo Amadeus.png|200px|right]]
[[File:Amadeus.jpg|150px|thumb|right|Amadeus headquarters building in Madrid]]
Amadeus, one of the world's largest [[GDS]], provides airline, hotel, car, train, ferry, cruise and insurance bookings.

== Description ==
Founded by Air France, Iberia, Lufthansa and SAS in 1987 as an alternative system to the American GDS [[Sabre]].

Amadeus tops the list of global distribution systems by the number of travel agencies that use GDS technology in their professional activities.

The company is headquartered in Madrid.

Amadeus interests in Russia, Armenia and Belarus are represented by the company "Amadeus - Information Technology".

Amadeus interests in Ukraine and Moldova are represented by the company "Amadeus Ukraine".

Amadeus interests in Kazakhstan, Kyrgyzstan, Georgia, Azerbaijan, Uzbekistan and Tajikistan are represented by the company "Amadeus in Central Asia and Transcaucasia".

== Key Features ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">
'''Search and General'''
<div class="mw-collapsible-content">
* Search by nearest dates
* OJ tariffing.
* Search by public + private fares
* Search for private fares
* Search by neighboring airports
* Schedule search
* Sending terminal commands - conditionally [[#FAQ on GDS/GDS/API Amadeus|<sup>[1]</sup>]]
* Maximum number of passengers of all types in search request - not limited
* Number of passengers of one type in request - not limited
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Booking'''
<div class="mw-collapsible-content">
* From the requisites/settings
** Hiding the price on the GDS site
* Additional operations using requisites/settings
** Reading fare rules
** Checking availability
** Checking availability via seat takeover
** Getting a seat map
** Price update
* Airline server operations/requests
** Flight booking
** Cancellation
** Booking update (synchronization)
** Import of bookings via PNR locator
** Receiving of bookinghistory from the GDS
** Changing the content of a booking
** Adding content to booking
** Content through WS - BSP
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:10px;">
'''Ticketing'''
<div class="mw-collapsible-content">
* From requisites/settings
** Statement on airline stock
** Management of the ticketings stock
* .NET airline server operations/requests
** Ticket issuance for all bookings
** Depositing airline commission at ticketing
** Commission per passenger type
** Endorsements
** GDS processing
** Multi-FOP GDS processing
** Voyaging
** GDS-specific functionality
** Remote Office ticketign via ATS/RTS.
</div>
</div>

== Connecting to Amadeus Web Services in Websky==
[[File:amadeus_schema.png|884px|thumb|center|Scheme for choosing connection license to Amadeus Web Services]]

=== Websky license connection ===
The easiest, fastest and cheapest way to connect to Amadeus and get the full available functionality is to connect using Websky license, which eliminates the need to pay for the license and wait for certification time slots.
To start the connection procedure, you need to create a ticket in the tracker with a request to connect to Amadeus and specify the necessary data:
* Office ID of the Agency for online work in Amadeus.
* Client Name - the official name of the Agency as a client in Amadeus.
* Signs for the given office. Usually, by default, the sign is 9999WS, and duty code (a role code that defines the rights for working with the office) SU (supervisor). If these values are different for the Agency office, you need to provide them as well.
* Approximate expected number of segments ticketed per month through this office.
The following nuances must also be considered:
* By the time the application is submitted, the Agency office must be set up for Low Fare Search (Master Pricer Travelboard / Master Pricer Calendar / Complex Itinerary) and online ticketing.
* It is desirable to order virtual Office IDs (also called online offices, with an eight as the seventh character, for example MOWR228XY) - this is desirable, but not obligatory (for example, if the Agency wants to use the main offline office online, where special fares are already loaded and there is no time to do it all over again).
Websky technical support will order a WSAP (access point for working with the office via Amadeus web services) for the Agency's Office ID based on the data from the client. Under Websky's contract with Amadeus, the allocation of a separate WSAP is subject to a support charge. Amadeus will bill Websky once a working WSAP has been created. This invoice will be re-invoiced to the Agency as soon as Websky technical support has verified that the WSAP is functioning correctly.

It typically takes up to two weeks to create a WSAP in a live environment.

If the office is owned by the Consolidator, the Consolidator must agree in writing to its use within the Subagent-owned engine.

If the office is owned by the Consolidator, and you want to automate online checkout via Consolidator offices (as well as low fare search/PNR creation), the Consolidator must notify Amadeus in writing that they are ok with it (since all MP/WBS transactions in this case will be paid by the Consolidator).

Connecting additional functionality or upgrading requests required only by one particular customer is carried out at that customer's expense.

=== Connection under an agent license ===
In order to connect Amadeus connector in the aviation component of the Websky system, [[Agency|agency]] must have a license agreement signed for using Amadeus Web Services (WBS), as well as an agency agreement must be signed.
For purchasing a license and signing the agreement the agency may contact the regional Amadeus representative office.

By purchasing a license, the agency receives an implementation slot from Amadeus, including:
* Kick-off Meeting;
* Implementation period.

When the agency has everything ready, certification to Amadeus is performed (in the general case of a paid process).

Before starting the certification process, Amadeus may ask the agency to answer the following questions (in English):
{| class="wikitable"
! List of questions
|-
| 1. What is the volume of the transactions you plan to generate?
|-
| 2. How many bookings do you estimate to perform monthly or yearly.
|-
| 3. Taking into consideration above — are you able to estimate the transactions per second? You may ignore this question if you provided answers to the previous one, we will calculate this basing on the answers from previous two questions.
|-
| 4. Which programming language (framework) uses your application ?
|-
| 5. Do you multiplex sessions over sockets, that is — is your framework/application able to maintain many sessions over one TCP/IP connection?
|-
| 6. Do you have any information about planned number of simultaneous sessions (important in case of threaded applications?
|-
| 7. What are your estimations for the near future concerning the amount of bookings/transactions?
|-
| 8 IP range
|-
| 9.Customer Network responsible Name and Phone number?
|-
| 10. SOAP version going to be used?
|}

The answers to questions 1-3 and 7 should be given by the agency, as they largely depend on the planned sales volume. For answers to the remaining questions you can contact Websky technical support.

As part of the certification process, Amadeus provides information about the project, as well as the test results, on the basis of which Amadeus makes a decision on passing the agency certification.

After the certification report is obtained, Amadeus allocates WSAP under the agent license. Mutual settlements take place directly between the agency and Amadeus.

'''Attention!''' In order to be able to connect the Websky system's Amadeus connector under the license agent, you need to have a certified set of web services for the agency, similar to those used in Websky.

'''Attention!''' Adding new services or updated versions of the requests means you need to get re-certified by Amadeus.

=== Connection to Amadeus Web Services in Central Asia and Transcaucasia ===
For connecting to Amadeus Web Services the Agency needs to contact a regional Amadeus office, where it is possible to obtain information about the procedure and the necessary application forms and agreements.

In general, the process will be as follows:
# The agency enters into an agreement with Amadeus to connect to Master Pricer Transactions and Amadeus Web Services Transactions within the application in use (CAU).
# For the convenience of the agency and adhering to Amadeus policy on Office IDs, Amadeus strongly recommends to use a dedicated '''Internet Office ID''' in the applications (do not use the usual '''Offline Office ID''' of the agency, in which the agency works all the time). To obtain it, the agency sends an application to Amadeus - request for the creation of Internet Office ID.
# After receiving the Internet Office ID, the agency fills the second form - the questionnaire to set up the office(s) for ticketing, search, master pricer and so on. It is completed by the agency after step 2. The processing period is 10-15 business days.
# After completing the previous steps, the agency should contact Amadeus Kazakhstan to connect the Office ID to the Websky application. If the agency does not have its own license on Amadeus Web Services, after fulfillment of previous requests it is necessary to appeal to Karim Kasenov (kkasenov@amadeus.kz) to connect agency's Office ID to WSAP company BMS, which has its own license on Amadeus Web Services. Karim creates a request (work order) to the head office to join Office ID to WSAP (BMS).
# After completing the configuration, Amadeus informs Websky and the agency of the need to test the search / booking / checkout in this Office ID, using the Websky application and continue to further configure the office.

=== Connection of foreign Amadeus consoles in Central Asia and Transcaucasia ===
In order to connect a foreign Amadeus desk or another GDS, the agency should coordinate it with the Amadeus office in Almaty or with the local office in Bishkek and inform Websky about details of coordination.

If you connect a foreign desk, the agency must decide with Amadeus Almaty the issue of <u>data of foreign desk</u> being delivered to Websky:
* Office ID;
* WSAP CAU, which must be compatible with the certified BMS configuration;
and describe the <u>principle connection scheme</u>:
* in which console the booking will be (local or foreign);
* in which console the tickeitng will be (local or foreign).

=== Gateway setup in Websky ===
After passing the certification process, the agency receives from Amadeus the combat credentials to work online.

The received credentials need to be transferred to Websky for the formation of the combat configuration of the connection.

RCC is configured by Amadeus specialists, the agency only needs to form an application to configure e-ticketing at [http://my.amadeus.ru customer service site "My Amadeus"].

Necessary details for the correct setup of RCC in Websky:
{| style="background-color:000000;" class="wikitable"
|-
| width="300" align="center"| '''Name of the field''
| width="200" align="center"| '''Default value'''
|-
| width="300" | Agency ID in Amadeus
| width="200" |
|-
| width="300" PCC (Office ID)
| width="200" |
|-
| width="300" | Agent login / Service User Name
| width="200"
|-
| width="300" | Service Password
| width="200"
|-
| width="300" | Maximum number of open sessions
| width="200" align="center"|- 5
|-
| width="300" | Type of agent's access to the system / Duty Code
| width="200" align="center"| SU – Supervisor
|-
|}

== Features of working with Amadeus in Websky ==
# Provider returns search results only 361 days in the future. To avoid errors, you need to set this restriction in the search form settings.
# By default, the search request in Websky asks for both private and public fares available in the client's RSS.
# Retrieving fare rules from the past is only available for discharged reservations.
# Provider provides a separate request to read PNR history. In Websky, you can view the [[PNR]] history in Amadeus on the order page, for all orders after booking.
# Like in other GDSs, Amadeus has a limit on the maximum number of open sessions with the GDS. It does not apply to the agent's office, but to the entire WSAP (Web Service Access Point). (For example, for sub-agents of the Aviacenter, the maximum number of simultaneous sessions in Amadeus is 250). Therefore, the session limit is divided by all agents working in the same WSAP.
# The current version of search requests in Amadeus supports displaying baggage in the search results.
# Amadeus does not return the operating carrier code in the PNR information. A special Air_FlightInfo request must be certified to retrieve it. In case the operating carrier data was not obtained from GDS at the time of booking or booking update, the operating airline code from the search results is inserted into the PNR.
# Amadeus returns only the total amount of fares in the search results. Detailed tax information with its codes and values is available only after the booking. That's why, on the search results and the order page before booking, the total amount of fares is marked with the code XT.
# When configuring Amadeus requisite packages in Websky, it should be taken into account that due to the specifics of this GDS search requests containing airports with Cyrillic codes do not return results and lead to a number of errors. For this reason, you need to configure the pre-routing of the package, excluding such airports from the search. The full list with the codes is contained in the file [[File:Cyrillic_airports.docx]]
# GDS robot adds the 5th segment to bboked orders, which according to the documentation means "Non-automated Miscellaneous auxiliary segment", in order to hold the booking (i.e. so that the order is not cancelled too early). Websky implemented handling of such segments.
# After ticketing, PNR will display agency fees divided per passenger, proportional to the fares.
# In Websky [[Booking form (Air tickets)|booking form]] prevents booking errors related to violation of Amadeus restrictions on the number of characters allocated to passenger information:
#* Minimum number of characters for last name or first name is 2.
#* Maximum number of characters allocated for surname, first name and document number together - 41.
#* If there is a patronymic, the maximum number of characters allotted for the surname, first name and document number together is 39.
# There is no possibility of checking out unconfirmed infants in Amadeus GDS for agents from Central Asia.
# During the search, the supplier returns baggage allowance only for ADT, for other types of passengers, no information on baggage allowance is returned.
# HX status is a withdrawal of seats by the airline; as a rule, it has nothing to do with availability. Usually this problem is due to non-compliance with the time limit from the airline. SSR "XXLD DUE NO TKT" indicates that the airline has withdrawn seats after the time limit has expired. In this case it is necessary to contact the airline and find out the reason for the withdrawal.
# For KC airline, at the stage of search, due to nonstandard fare filing by KC airline, the child discount cannot be applied, it is applied at the stage of pricing. Due to this, the price is reduced at the transition to the order.
# Terminal commands that correspond to the Fare_PricePNRWithLowerFares request, to match the transaction in Websky with the action in the terminal:
#* FXB - Rebook to the lowest available fare and create a TST
#* FXR - Rebook to the lowest available fare without TST creation
#* FXA - Display a list of lower available fares
The FXB command is the most suitable, but the choice of command depends on the expected result.

=== Search by the nearest dates in Amadeus ===
Amadeus engine supports the ability to search by the nearest dates (flex search):
* To search for ± 1 day, the main search request is used.
* To search for ± 2-3 days you need to use an additional request.
* It must necessarily be provided in the list of requests for certification, otherwise it will not be available for use in combat mode.
=== Search for flights of non-BSP/ARC member airlines ===
For GDS Amadeus, Websky supports search for flights of non-BSP/ARC member airlines with ticket issuance on these airlines' stock.

=== Synchronization of bookings with Amadeus system ===
In order to update the orders in Websky and take into account the changes made in [[PNR]] in the Amadeus system terminal, you may use [[Synchronization of bookings|order synchronization module]].

=== Specifics of ATS-RTS operation ===
Special Ticketing Robot automates the process of issuing e-tickets. After booking in one office the robot moves the booking to the office for ticketing and issues e-tickets. The robot processes the queue once in every 5 minutes. Because of this, the system does not receive ticket numbers immediately, but only some time after the PNR is updated, when the robot has already processed the queue. In the interval between sending a request for checkout and receiving a response indicating that the booking has been successfully sent to the queue, the order is given the status "Checked out, tickets are being processed". Websky provides automatic refreshing of such orders which checks whether the tickets are available in PNR. The refresh period varies from 16 to 23 minutes after ticketing. After receiving the numbers of issued tickets, an itinerary receipt will be automatically sent to the client's e-mail.

=== Ways to optimize search execution ===
* Limit searches by carriers or destinations using [[Nemo Connect| Websky 2.0 search request router]] or [[Search request filters (Air tickets)| search request filters]].
* Use the NAD (Disable airline diversity) option in the Amadeus GDS request, thus reducing the proportion of airline diversity in the output.

==Supported additional GDS Amadeus options==

===Airline ticket exchange or refund===

The '''Ticket Exchange and Returns''' module automates the acceptance of customer requests and their processing in manual or auto mode by a manager or an agency/sub-agency expert. <br>.
For more information see the article [[Ticket exchange and refund]].

=== Queues===
'''Queues''' are sections of the booking system into which bookings are automatically or manually placed with notifications (e.g. time changes, segment cancellations, notifications from airline or agency supervisor, waitlist confirmations, SSR requests, etc.). Queues are designed to control the bookings created and assume their subsequent processing by the agent.

Using queues, the agent gets a convenient arrangement of bookings that helps to notify passengers of changes in a timely manner, correspond with the carrier via [[Vendor-remark|vendor-remark]] or OSI message, set reminders, generate passenger lists, recall bookings from the archive, and contact other agency offices or branches to transfer bookings.
Reservations are distributed in queues automatically, or the agent moves them manually. For more information on queues, see [[Queue]].

====Amadeus queue bank====
Each office in the Amadeus system has its own queue bank.<br>
Automatically activated queue bank for the agency:
<pre>
Queue number Purpose
0 General - this queue receives messages that
do not correspond to any other queue types
1 Confirmation - this queue receives confirmations
from the airlines (for example, on SSR elements)
2 Waitlist Clearance - Confirmation from Waitlist
3 Options - PNR with OP elements
4 Responsibility Change - PNRs sent to your agency come in this queue,
7 Schedule Change - information about schedule changes
8 Ticketing/Time Limit
9 Other Airline Control
12 Expired TKTL - only for your control: PNR
With expired TKTL, ticket is not redeemed
23 RQR (Request for Reply Queue) - for PNRs on SSR elements
for which the airline has not responded within 24 hours
80 Prepaid Ticket - only for airlines
87 Groups - general queue for group PNR
94 Message - customer profile
96 Message - bookings from the archive
97 Message - for text messages
</pre>

==== Queues in Websky====
Websky supports work with GDS Amadeus queues.

* You can track placed orders in queues in the '''Queues for checking by suppliers''' section of the Nemo Connect administration panel.
* To set the default queue where booked orders are sent, specify the queue number in the '''GDS queue number where to place the booking created''' parameter in the '''Air Settings → Air packages'' section.

===Rebooking for the lowest price===

The option is enabled by the ''''Use overbooking for the lowest price''' option in the booking details in the Amadeus package (see [[Nemo Connect requisite packages]]).

With this option enabled the air server asks for the lowest available booking price for the given flight, on the basis of the given pricing parameters (validating carrier, currency, passenger types, private/non-private fares etc.). The lowest price search is performed within the same base class (economy, premium economy, business, etc.) to which the segments/fares of the original priced flight belong. The "Use rebooking for the lowest price" option is executed when the price for the flight is updated (when checking availability), when fare rules for the flight are obtained (if this is used for pricing) and also when pricing is performed during booking operations.

===Fare families===
Fare families divide fares into groups (brands) according to the level of service applied. See the [[Fare families]] article for details.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; margin-bottom:12px;">

== Errors in interaction with GDS/GDS/API Amadeus==

<div class="mw-collapsible-content">
'''Search errors'''<br />.
Provider-independent:
{| class="wikitable"
! width="220"|Error
! width="280" | Explanation
! width="280"| Possible solution
|-
| SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR
| There is a parallel change in the PNR in the booking operation. In this case you have to start the operation over again.
|
|-
| Invalid search request object
|This error occurs when an invalid search result is requested. Possible causes:
* an invalid search link;
* The search result may be out of date.
|
|}

'''Booking errors'''
{| class="wikitable"
! width="220"| Error
! width="280" | Explanation
! width="280" | Possible solution
|-
| ITEM TOO LONG / NOT ENTERED
|Appears when you try to book a flight for an adult and an infant without a seat. In GDS Amadeus, an infant without a seat is bound to an adult in one field. The length of the name field is limited to 57 characters.
| When booking a flight for an adult and an infant without a seat, you need to keep within this limit, for example, without specifying the middle names of the passengers.
|-
|PRICING OPTION DISALLOWED FOR LOCATION
|Means that the pricing option (fare calculation) is disallowed for this office. Appears in the case if on the GDS side the office settings were carried out incompletely / incorrectly.
|Contact the technical support of the GDS and ask to correct the settings.
|}

'''Ticketing errors '''
{| class="wikitable"
! width="220" | Error
! width="280" | Explanation
! width="280" | Possible solution
|-
|TICKETING INHIBITED - CONTACT AMADEUS HELP DESK
| Customer´s office is not configured for checkout or the airline is not allowed to checkout at the BSP stock.
|
|-
|<nowiki>284|Application|SECURED PNR</nowiki>
| Usually occurs when booking a flight at one office and ticketing - at the another (e.g. when ticketing on a direct airline stock).
| To solve the problem, the client must send to the technical support of Amadeus GDS a request for opening of access between these offices (set the transparency). It is also possible to transfer PNR from the bookings office to the checkout office via the ES command, in this case PNR will be available in both the bookings office and the ticketing office.
|-
| PROHIBITED TICKETING CARRIER - RE-ENTER TICKETING CARRIER
| This means that the validated ticketing carrier is not allowed to be ticketed at this online office.
| Contact the account manager in GDS Amadeus in order to add this airline to the list of authorized carriers for ticketing.
|-
|MANDATORY SSRFOID MISSING FOR CARRIER
| It means that for this airline it is mandatory to include SSR in PNR in FOID format.
| Mandatory inclusion is enabled in the static of this airline. Please contact technical support to include an SSR to PNR in FOID format for this airline.
|-
|VERIFY TOTAL AMOUNT CURRENCY
| Means that this office is not allowed to issue a ticket in the selected currency.
|
|-
|CT RJT: TKTG INHIBITED - NO ALLOCATION FOR XX
| (Where xx is airline code) Means that the quota of e-tickets allocated by this airline for the given sales period is exhausted.
|
|-
| INVALID VALIDATING CARRIER OPTION USED WITH AIRLINE STOCK
| Means that this Amadeus office is not authorized to issue flights on this airline's direct stock
| Contact your account manager at GDS Amadeus
|-
|LOCATION NOT VALID FOR ETKT
| OID does not have the right to issue electronic carriage documents
| In order to make the necessary adjustments to the profile of the office, the owner of the office should make a corresponding request through the website my.amadeus.ru
|-
|GTW/ETS: EDIFACT MESSAGE SIZE EXCEEDED
| For TK (Turkish Airlines). TK has limited the number of e-tickets that can be issued to more than 3 passengers.
| In statics for the airline, there is a maximum number of passengers that can be checked out and we take it into consideration. Set the maximum number of passengers for the airline.
|-
|Host error during ticket issue. ELECTRONIC TICKET NOT ISSUED VENDOR LOCATOR REQUIRED FOR SU
| Means that PNR locator was not received from the airline.
|Since it is not possible to check out without a vendor locator, Websky has implemented a ticketing ban in case of its absence. As a rule, the locator can still be obtained during subsequent updates of the order.
|}
</div>
</div>

== Contact Information ==
==== Amadeus - information technologies ====
Russia, Moscow, Maly Golovin per. 5, 2nd floor Business Center

Tel: +7 (495) 797-90-99

==== Amadeus Ukraine ====
Ukraine, Kiev, 04080 Nizhneurkivska Str. 45a

Tel: +3 80 44 490 22 35 or 0-800-302-333 (free from fixed phones in Ukraine)

==== Amadeus in Kazakhstan ====
48 Auezov St., Almaty, Kazakhstan, 050008 (4th floor)

Tel: + 7 727 349-42-49; toll-free number: +7 751 144 0751 (for Kazakhstan, except Almaty and Astana)

Representative Office in Astana: 14 Beybitshilik Str., 010000, Shakhnaz Business Center, offices 703-704, Almaty, Kazakhstan

Phone: +7 7172 787-297

== Useful Links ==
* [http://www.amadeus.ru Official site of "Amadeus - information technologies"]
* [http://www.amadeus.com/ua/x46748.html Official site "Amadeus Ukraine"]
* [http://www.amadeus.com/amadeus/amadeus.html Amadeus Resources for OTA]
* [http://my.amadeus.ru "My Amadeus" customer service site]

== See also ==
* [[GDS]]
* [[PNR]]
* [[Travelport (Galileo)]]
* [[Sabre]]
* [[SITA Gabriel]]
* [[Sirena Travel]]
* [[API Travelfusion]]
* [[Nemo Inventory (component)]]

File:Logo Amadeus.png

2020-12-25T13:41:16Z

I shaletin:

File:Amadeus schema.png

2020-12-25T13:41:07Z

I shaletin:

File:450px-Amadeus.jpg

2020-12-25T13:40:33Z

I shaletin: