Validating Carrier Automatic Selection & Enforcement
4
The process described does not prevent you from selecting your
preferred validating carriers by:
•
Adding a FV element in the PNR before pricing
•
Requesting it in the pricing input via the /R,VC-XX (denotes
airline two letter code) option. In this case XX is the selected
validating carrier for the pricing calculation.
Fare rules restrictions
Validating Carrier Automatic Selection & Enforcement
Validating carrier enforcement at
ticketing time
This check at ticket issuance by the system (TTP) ensures that the
validating carrier used for pricing is the same as the one currently in
the PNR.
If they are different, the ticket command is rejected and the following
error message is displayed:
Display of a Fare with Fare Rule Restrictions
Resolution:
Delete the TST and price the itinerary again using the carrier in the FV
element or amend the FV back to what it originally was when the PNR
was priced.
What carrier was used at pricing?
You can display the carrier used at pricing time (pricing context) for a
TST in order to know which validating carrier was used for the pricing.
Enter TQC or TQC/Tx
FQN2*SR
Display of a pricing context
OW GBP RT B PEN DATES/DAYS AP MIN MAX R
1569
02 YRTST
FCL: YRTST
(x being the TST number).
TAX MAY APPLY
25JUN09**25JUN09/XX LONCAI/NSP;EH/TPM 2187/MPM 2672
LN FARE BASIS
Validating Carrier
Automatic Selection
& Enforcement
“VALIDATING CARRIERS DO NOT MATCH: REPRICE OR MODIFY FV”.
The validating carrier restrictions coded within the (Category 15) Sales
Restriction in the Fare Quote Note of a fare or a Category 35 fare rule
is also processed. The Sales Restriction filed allows the carriers to
separate sales requirement from validating requirements. Essentially
what this means is that the airlines can specify in ATPCO a second
validating carrier which is different to the one publishing the fare and
therefore not restrict the sale anymore to one airline only.
** RULES DISPLAY **
5
Y
-
-
-
+ -
- -
R
TRF: 22 RULE: 2201 BK: Y
PTC: ADT-ADULT
FTC: EU -ECONOMY UNRESTRICTED
SR.SALES RESTRICT
TICKETS MUST BE ISSUED ON THE STOCK OF XX.
(Please note that this will only apply if the TST is in first issue mode
and the TST indicator is automatic (I, A, F, G or T). This does not apply
for manual TST’s.)
Warning:
If you see a note with the restriction in it is not processed by Amadeus
as the airline has not coded the sales restriction in the fare. For
example:
SR.SALES RESTRICT
NOTE –
Reissues and Exchanges
The validating carrier to be used for Exchange/Reissue must always
be the same as the one of the ticket to be exchanged. Therefore, you
must select this validating carrier for manual Exchange/Reissue.
TICKETS MUST BE ISSUED ON THE STOCK OF XX
Copyright © 2009, Amadeus s.a.s - All Rights Reserved
Quick Card
Validating Carrier Automatic Selection & Enforcement
1
Validating Carrier Automatic Selection & Enforcement helps you save
time in pricing and ticketing steps and reduce ADMs due to entering
the wrong validating carriers.
Validating Carrier Automatic Selection & Enforcement
2
The validating carrier automatically determined and used for the
pricing calculation is displayed in the pricing response when prechecks have passed:
Display of a pricing answer that has passed ticket-ability
Automatic Selection of the Validating
Carrier
pre-checks
Amadeus Recommendation
Validating Carrier Automatic Selection & Enforcement
The table below explains what validating carrier is included within the
FV element :
PNR
before
pricing
No FV
element
It is passenger and segment associated, in order to be fully
consistent with the returned pricing (and with the TST
created at the same time).
One FV element is created per TST generated. This is why one single
pricing request can generate several FV elements in the PNR.
Display of a PNR after a confirmed pricing
How the
validating carrier
is calculated
No VC specified
•
Ticketing
IATA
resolutions
checked
•
ATPCO
validating
carrier
selection
logic
checked
•
Fare Rules
stock
restrictions
in Category
15 and
Category
35 checked
E.g. FXP etc
E.g.
FXP/R,VC – YY
Automatic creation of the FV element
•
Pricing Entry
VC specified
Amadeus recommends that you do NOT manually select the
validating carrier. These enhancements ensure that the preferred
validating carrier is automatically selected according to Industry
standards for pricing and ticketing.
No VC specified
FV XX
After a successful pricing, the corresponding FV element(s) is
automatically added to the PNR
E.g. FXP etc
VC specified
If pricing fails at ticket-ability pre-checks you may receive the
following error messages below:
E.g.
FXP/R,VC – YY
“NO TICKETABLE VALIDATING CARRIER”
If no airline is eligible as a validating carrier and no fare is priced an
error message is returned.
3
PNR After
Pricing
FV created
FV YY created
if passed prechecks
FVXX created
if passed prechecks
FVXX is
entered
however if FV
element is
different to
carrier in
pricing entry
FV is updated.
Resolution : Delete TST and then price each segment individually.
**Please note all FV elements are passenger and segment related. **
“WARNING: VC XX FAILED TICKET-ABILITY PRE-CHECKS”
From the 30th September ticket-ability pre-checks ensure that the
validating carrier determined at pricing is the most appropriate one for
the itinerary, matching the ATPCO validating carrier selection logic, as
well as the ticketing IATA Resolutions. This automatic determination is
processed against the following tables:
•
•
•
.
BSP (TGBD),
Interline Ticketing Agreement (TGAD)
General Sales Agent – GSA (TGGSD)
This is displayed when a PNR is priced entering the validating carrier in the
pricing entry eg FXP/R,VC-XX. The message is displayed to advise that
XX failed the ticket-ability pre-checks, so that this pricing solution may
be rejected at ticket issuance time (TTP).
Resolution: Delete TST. Do not enter FV and reprice or additionally
enter an alternative FV and then reprice.
For further information please refer to the help pages
HEFV or alternatively contact the Amadeus Helpdesk via
e-Support.