Accompanied Travel Enhancements – PA439
What
Allows you to fare quote ‘companions’ without the need for them to be
booked in the same Booking File.
This enhancement to the fares system will provide greater flexibility in
quoting fares for passengers with accompaniment requirements.
The enhancement is in two main parts 1. A new accompaniment modifier in the fare quote entry will
indicate an accompanying passenger in a separate
PNR/Booking File. This will allow a passenger with
accompaniment requirements to be priced separately.
2. The enhancement will also allow passengers with
accompaniment requirements to be priced separately from the
accompanying passengers who are in the same PNR/Booking
File.
Who
All Galileo® Users
Where
Globally
When
Today
OVERVIEW
Currently, when a fare requires accompaniment by another passenger, the 360º Fares system
requires that both passengers be priced at the same time. To override this, the use of a Fare
Identification Code (FIC) modifier was necessary, which in turn resulted in a fare quote that was
not guaranteed.
DETAIL
New Accompanied Modifier in Fare Quote
This enhancement will allow the user to use a new input modifier, “/ACC”, to indicate that an
accompanying passenger is booked on a separate record. This will enable the user to price and
ticket individual passengers on a PNR/Booking File.
Accompaniment Recognition within a PNR/Booking File
In cases where the accompanied fare quote “/ACC” modifier is not used, the system will
automatically recognise any additional passenger(s) in the same PNR/BF and permit any
accompaniment restrictions to pass. This enables the pricing and ticketing of fares that require
accompaniment by another passenger to price separately.
Accompaniment Validation
With the implementation of this enhancement, two types of fare quote entries will result in some
differences in accompanied rule validation:
•
The “accompanied” indicator (/ACC) is used in the fare quote input
•
The /ACC indicator is not used in a fare quote input and the fare quote request is for
specific passengers (not all) the passengers in the PNR
In these types of entries, the accompanying passengers are those either indicated by the /ACC
modifier, or those implicitly recognised as the unselected passengers in the PNR. If the PTC of
these accompanying passengers is not also the same PTC as any of the selected passengers, it
will be assumed that the user has validated the accompaniment rules and the system should
automatically pass certain accompanied travel rules in Category 13 (accompaniment) and 19-22
(discounts) such as:
•
•
CPMT – Which requires that the passenger be accompanied in the same compartment to
qualify for the fare.
Rule – Which requires that the accompanied passenger be travelling on a fare governed
by the same rule.
360º Fares, in these types of fare quote entries, will only validate the PTC, age and number of
accompanying passengers. All other non-passenger specific sections of the accompanied travel
rule will be assumed to have been validated and passed.
If the accompanying passenger(s), as indicated by the /ACC modifier or implicit recognition in the
PNR, have the same PTC as the passenger(s) selected, then all accompaniment rules will be
validated.
Galileo – FCMI and Guarantee Codes
For Galileo, any ticket generated with the resulting fare quote from this enhancement will output
an FCMI of “0”, meaning that the fare is auto-priced.
For Galileo, which also uses a Fare Status Indicator, the resulting fare will have an FSI
(guarantee code) of “G”, meaning auto-priced by Galileo, or “A”, meaning airline private fares are
auto-priced.
Impact to Data Formats
The following are examples of the options associated with using the /ACC modifier in Fare Quote:
Galileo Format
FQP2*C05/ACC
FQ*C05/ACC
FQP1*CMA/ACCCMP
FQP2*CMA/ACCC10
FQP1*C10/ACC2
FQP1*M10.2*M07/ACC2MIL
Description
Fare Quote child, accompanied by an
adult passenger on a separate record
Note: “/ACC” input without any PTC
following defaults to Adult (ADT).
Fare Quote all passengers in PNR/BF
as child, accompanied by an adult
passenger on a separate record.
Fare Quote companion, accompanied
by a companion on a separate record.
nd
Fare Quote 2 passenger as
companion, accompanied by a child on
a separate record.
Fare Quote child, accompanied by 2
adult passengers on a separate record.
Fare Quote military children,
accompanied by 2 military adult
passengers on a separate record.
Note: Multiple accompanying
passengers must be of the same
passenger type.
Note: Galileo passenger names in fare quote are numbered in ascending order starting with first
name in the Booking File.
Entering two or more different PTC’s in conjunction with the /ACC modifier will not be a supported
format.
Although any type of PTC modifiers are permitted with the /ACC modifier, resident modifiers (“E”
modifier for Spanish Residents) and personal geography modifiers (“L” modifier) cannot be
validated for the passenger who resides in a separate PNR.
For example:
Galileo Input:
FQP1/ACCADRLTCI
FQP1/ACCADR30
FQP1*ADRLTCI/ACCADR
Incorrect, location cannot be validated for psgr in
separate Booking File.
Correct, PTC and age can be validated
Correct, location modifier can be used with psgr
selected from primary PNR
Accompaniment modifier and PTC in name remark field
With the implementation of 360º Fares Release 4 enhancement, PTC in Fare Quote, a PTC that
exists in a passenger name remarks field will be used by fare quote, unless it is overridden by
another PTC in the fare quote entry.
Example:
The name remark has a PTC of M05 for military child, age 5:
1.1FRANKLIN/BMISS*P-M05
1 AA 101 H 05NOV LHRJFK SS1
0955 1245
2 AA 142 H 20NOV JFKLHR SS1
0830 2025
To price this passenger using the accompaniment modifier:
Galileo Input:
SU
MO
FQ/ACCMIL
Fare Quote Military Child, accompanied by Military Adult
Or
FQP1/ACCMIL
1.1FRANKLIN/BMISS*P-M05
1 AA 101 H 05NOV LHRJFK SS1
2 AA 142 H 20NOV JFKLHR SS1
0955 1245
0830 2025
SU
MO
If the PTC in name remarks is overridden by a PTC in the fare quote entry:
Galileo Input: FQP1*C05/ACC
Price child with accompanying adult on separate booking
file
Or
FQ*C05/ACC
Maximum Number of PTCS Exceeded in PNR/Booking File
If the number of different PTC’s in the name field remarks in a PNR or Booking File exceeds 4 in
Galileo, a fare quote request without the /ACC modifier will result in a new error message:
TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE
Accompaniment recognition of any un-selected passengers as accompanying passengers in the
same PNR/Booking File, must adhere to the existing maximum number of different PTCs that can
be processed for a fare quote.
Using the /ACC modifier will process only the selected passenger(s) from the PNR, based on the
accompanying passenger(s) indicated by the /ACC modifier.
Galileo Example
With the implementation of PTC in Fare Quote, “P-“ PTC items in name remarks will be used in a
fare quote entry, unless overridden by appending a PTC in the fare quote entry.
The following Booking File contains 5 different PTCS: ADT (default), MIL, M05, C05, SRC
1.1TEST/AMR
2.1SOLDIER/BMR*P-MIL
3.1MILKID/JMISS*P-M05
4.1CHILD/KMISS*P-C05
5.1SENIOR/LMR*P-SRC66
1. BA 2037 Y 15MAY LGWMCO AK5 1105
1520
TU
Current Processing:
Current Processing:
be
New Processing:
New Processing:
New Processing:
FQ - results in error response “Too many passenger descriptions”.
FQP3 - results in best fare for passenger, ADT, since military child must
accompanied.
FQ - results in error response:
TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE
FQP3 - results in error response:
TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE
This is because of accompaniment recognition of all the PTC’s in the
same Booking File, whether selected or not in the fare quote request.
FQP3/ACCMIL - results in a military child fare quote when applicable
Applicability
All fares access paths are applicable for this enhancement. All fare quote products and functions,
with some exceptions, will support the new accompaniment modifier.
Exceptions to products supporting the new accompaniment modifier and enhancements are:
• Calendar Shop (Viewpoint/North American itineraries) for Galileo will not support the
/ACC modifier and PNR recognition, since it already bypasses certain accompaniment
rules.
• Galileo Focalpoint Shopping will not support the /ACC modifier.
Note – Fare Quote Planner (FQP) will support the new /ACC modifier, and already bypasses
certain accompaniment rules, similar to the processing in this enhancement when the /ACC is not
used
NOTE – Galileo Desktop will support implicit recognition of unselected passengers in this
release. However the new /ACC accompaniment modifier will require updates to Galileo
Desktop (Viewpoint screens), scheduled to be loaded with a future update release of
Galileo Desktop.
Structured Data/XML Updates
Structured Data/XML will require updates to activate accompanied travel enhancements.
If the structured data user wishes to include information about passengers to be used only for the
purpose of validating accompanied travel restrictions, this can be added as additional array items
to the GQPA KLR. The 'Last Name Element Number', 'Passenger Element Number' and
'Absolute Name Element ID' data within the GQPA KLR should be set to '00' for these
accompanying passengers to prevent them from being priced and included in the fares returned.
Field Name
Data Type
Length
4
Description
Length
Numeric
Total KLR Length
Record Identifier
AlphaNumeric 4
'GQPA'
Number of Array Items
Numeric
3
Number of Array
Items
Delimiter Character
Alpha
1
Not Used Always 'F'
Level Indicator
Numeric
2
Not Used Always '00'
Version Number
Numeric
2
Version of this
KLR - 4
Field Name
XML Tag
Data Type Length
Passenger Array
<PsgrAry>
Array
Passenger Array
Element
<Psgr>
FieldSet
Description
Last Name Element
Number:
Sequential number
identifying Last
Name
Range Of Possible
Values:
00 - 99
Last Name Element
number
<LNameNum>
Numeric
2
Example:
If the first 3
passengers are all
Smith, and the next
two passenger are
Jones, then the
fourth and fifth
passenger's Last
Name Number
would be '02'
because they have
the second last name
in the group.
What does null data
indicate?
Zero indicates
passenger data not
part of pricing
request to be used
for accompanied
travel restriction
validation only. If
zero is input, it must
be input in all three
data elements: Last
Name Element
Number, Passenger
Element Number,
Absolute Name
Element ID
Passenger element
number:
Unique Sequential
number identifying a
passenger within a
Last Name group
Range Of Possible
Values:
00 - 99
Passenger element
number
<PsgrNum>
Numeric
2
Example:
If the first 3
passengers are all
Smith, and the next
two passenger are
Jones, then the
fourth passenger
would have a 2 in
the previous field,
and a 1 in this field,
since he is the first
Jones in the group.
What does null data
indicate?
Zero indicates
passenger data not
part of pricing
request to be used
for accompanied
travel restriction
validation only. If
zero is input, it must
be input in all three
data elements: Last
Name Element
Number, Passenger
Element Number,
Absolute Name
Element ID
Absolute Name
Element ID:
Unique Sequential
number identifying a
passenger by an
Absolute number, or
a number that is not
relative to last name
groups.
Range of Possible
Values:
00-99
Absolute Name Element
ID
<AbsNameNum>
Numeric
2
Example:
If the first 3
passengers are all
Smith, and the next
two passenger are
Jones, then the
fourth passenger
would have a 4 in
this field, since he is
the fourth passenger
in the group
regardless of last
name.
What does null data
indicate?
Zero indicates
passenger data not
part of pricing
request to be used
for accompanied
travel restriction
validation only. If
zero is input, it must
be input in all three
data elements: Last
Name Element
Number, Passenger
Element Number,
Absolute Name
Element ID