Hybrid/Full ATPCO model
- Andrea Sanguinetti
- sescobar
- Marcelo Topolansky
- Alina de los Santos
Specific considerations
- 1 Fare Quote Display
- 2 Kiu fares’s display -KIUF
- 3 Automatic Pricing
- 4 Ticketing
- 5 Exchanges
- 6 Automatic Refunds
- 7 Most common system responses when processing an Exchange/Refund using the ATPCO flow:
Fare Quote Display
ATPCO Fares will be flagged with #50 on the upper right corner of the FQD display
If KIU Fares are the ones configured by the customer, they will be flagged with #01 instead.
New qualifiers will be listed as follows when fares content is pulled from ATPCO:
Kiu fares’s display -KIUF
When the cxr is on full ATPCO model and you need to verify the fares configurated on Kiu fares for the travel agencys that keep on using this model because the Web services you can display those using the -KIUF indicator.
Private Fares
If the indicator /P, /PV or /NF is included in the FQD command, the system will show only private fares.
Otherwise public and private fares will be shown.
In the FQD response private fares filed without an account are displayed with “/” to the left of each fare basis.
Token | Description | Example |
|---|---|---|
/P | Private Fares | FQDLIMMAD/P |
/PV | Private Fares | FQDGBEMUB/PXXX*AC/XXX/PV |
/NF | Private Fares | FQDGBEMUB/PXXX*AC/XXX/NF |
Examples:
FQDLIMMAD/P
FQDGBEMUB/PXXX*AC/XXX/PV
Account codes
In the FQD response private fares filed without an account are displayed with “*” to the left of each fare basis.
Indicator | Description | Example |
|---|---|---|
*AC/ | it will display fares filed with an account code in categories 1, 25 or 35 | FQDGBEMUB*AC/XXX/ABP/PXXX |
Display only public fares
Indicator | Description | Example |
|---|---|---|
PL | it only displays public fares, if there were no available public fares it will not display any fares at all | FQDGBEJNB/CY/PL |
PF | it only displays public fares, if there were no available public fares it will not display any fares at all | FQDGBEJNB/CY/PF |
Display only negotiated fares (category 35)
Indicator | Description | Example |
|---|---|---|
IT |
| FQDGBEMUB/PXXX*AC/XXX/IT
|
Display only private fares filed with account code
Indicator | Description | Examples |
|---|---|---|
XC | It only displays private fares filed with an account code | FQDGBEJNB/CY*AC/XXX/XC |
NFC | It only displays private fares filed with an account code | FQDGBEJNB/CY*AC/XXX/NFC |
Display historical fares
Token | Description | Example |
|---|---|---|
R,(ticketing date) | To retrieve fares available on the requested date | FQDMADLIM/R,04JUN24 |
D(travel date) | To retrieve fares for the requested travel date | FQDMADLIM/D15AUG24 |
R,(ticketing date)/D(travel date) | To retrieve fares available on the requested ticketing and travel date | FQDMADLIM/R,04JUN24/D10JUN24 |
-EXT Indicator
When the hybrid model is configured, the indicator -EXT will be used to display fares filed in ATPCO.
Fare display commands no longer supported with ATPCO Pricing
FNEW*
F*
FMOD
FQT<city><city>
Automatic Pricing
The pricing process with the hybrid model and the full ATPCO is quite similar to the KIU Fares, however, during the development path, some functionalities were added and here below further explained:
Pricing engine indicator
Private Fares
Account codes
Indicator | Description | Example |
|---|---|---|
AC/ | Quotation with Account Code filed in Categories: 1, 25 or 35 | WS*AC/XXX |
Price only public fares
Indicator | Description | Example |
|---|---|---|
PF | it will only price public fares, if there were no available public fares it will not price the itinerary | WS*PF |
PL | it will only price public fares, if there were no available public fares it will not price the itinerary | WS*PL |
Price only private fares
Indicator | Description | Example |
|---|---|---|
NF | it will only price private fares, if there were no available private fares it will not price the itinerary | WS*NF |
PV | it will only price private fares, if there were no available private fares it will not price the itinerary | WS*PV |
With this indicator you will be able to price the following private fares:
cat 15 private fares
private FBR´s
cat 35 fares with account code
cat 35 fares without account code
Price only FBR´s
Indicator | Description | Example |
|---|---|---|
FB | it will only price FBR´s, if there were no available FBR´s it will not price the itinerary | WS*FB |
With this indicator you will be able to price the following private fares:
Public FBR´s
cat 35 FBR´s
FBR´s filed with IF 15 FBR security
Price only negotiated fares (cat 35)
Indicator | Description | Example |
|---|---|---|
IT |
| WS*IT |
Price private fares filed with an account code
Indicator | Description | Example |
|---|---|---|
NFC | It will only price private fares filed with an account code | WS*IT*AC(account code)*NFC |
XC | It will only price private fares filed with an account code | WS*IT*AC(account code)*XC |
Remote Office
Remote office quotation does exist already nevertheless with this development, it will consider as well the configuration of the department code, travel agency, and the office IATA number.
ATPCOS keyword will be needed to access the configuration which will permit to access the Matching Security Table from the Administrator menu. An office ID will be associated with a department code or a travel agency that will be used to match the ATPCO coding.
Token | Description | Example |
|---|---|---|
OF | quote from a remote office | WS*OFXXX |
Q surcharges
It will be not possible to add Q surcharges to the quoting manually when the system pulls ATPCO fares. Surcharges will be quoted automatically if they are coded in Category 12.
Commands no longer supported with ATPCO Pricing
TCODE/*
WS*UB/<tourcode>
WS*UB<tourcode>
WS*UI/<tourcode>
WS*UI<tourcode>
WS*UN<tourcode>
Ticketing
When using a hybrid or full ATPCO model, after issuance, the PNR should be saved with E or ER.
Every issuance process will use ETS.
Commands no longer supported with ATPCO Pricing
WK*FCA*BA2P or 15KG
WK*FCA*DOB/20APR77
Considerations for travel agencies issuing with cxrs in full ATPCO model
When agencies issue / reissue with a cxr that is in full ATPCO model they should add the *A(carrier) indicator to the usual issue command.
WK*FCA*AQC
Otherwise they will receive the message INVALID-ISSUE CARRIER NOT INDICATED.
Exchanges
An automatic exchange will be possible when category 31 has been coded in ATPCO and the change applies to the details coded.
When using the ATPCO pricing engine, quoting the new itinerary will be not necessary.
Here follows the step-by-step:
Modify itinerary
Display ticket to be exchanged with ET/
When using the issuing command WK*FEX#CA the preview with the calculation will be displayed
After the preview display, changes will be ignored if the IR command is entered.
When the change is saved then confirmation is possible.
Example:
OW flight for the 25MAY needs to be rebooked for the 28MAY
1 Itinerary updated
*** UPDATE MODE ***
RP/JNB00BP4 - AIR BOTSWANA
1.1A/A »PP 93682417
1 BP204 Y 25MAY TH JNBGBE HK1 1330 1440
*** ARNK ***
2 BP204 Y 28MAY SU JNBGBE SS1 1355 1455
TKT/TIME LIMIT
1 TKT/OK * 16FEB23/KIUHELPER
2 TKT/ET 6362310001388 * 16FEB23/KIUHELPER - A/A.
FARE - PRICE RETAINED
CONTACTS
1-AEP 999 AUTO PNR GEN V.1
MAIL
2- MAILTO:ANALISIS@KIUSYS.COM
RECEIVED FROM - PNRGEN
JNB.KIUHELPER 1313/16FEB23 *HYWZQK -H~006HYWZQK2 Ticket displayed
ET/2
TKTT-6362310001388 BP/HYWZQK
OD-JNBGBE POI-JNB DOI-16FEB23 IOI-99999999 0 0 #50
ED-NO-SHOW PENALTY APPLIES
1.A/A ADT
FOID: PP 93682417
/..88 1 JNB BP 204 Y 25MAY 1330 OK YFBPOW 30K OPEN FOR USE
GBE
FARE ZAR 1590.00 BSR 1.00000
EQUIV ZAR 1590.00
TAX ZAR 27.54EV 31.05UM 2089.90XT
TOTAL ZAR 3738.49
TOUR CODE :
COMMISSION :
/FC 25MAY23JNB BP GBE Q5.87 87.49YFBPOW NUC93.36END ROE17.029730XT 100.00WC 1788.00YQ 201.90ZA
FOP: 3738.49 CASH3 Issuing command including the new segment
WK*FEX#CA*S2
EXCHANGE DOCUMENT NUMBER 6362310001388 ** PAX NAME: A/A ADT
OLD ITINERARY:
1. BP 0204 JNB/GBE Y 25MAY 1330
NEW ITINERARY:
1. BP 0204 JNB/GBE Y 28MAY 1355
AMOUNTS IN *ZAR* COLLECTABLE OLD TICKET NEW TICKET
EQUIV.FARE < 0> 1590 1590
TAXES < 0> 2148 2148
PENALTY < 0> AS OD TAX CODE
OB FEES < 0>
NEW TICKET ADD COLLECT < 0>
PAID TAXES DETAILS : ZAR PD 27.54EV/PD 31.05UM/PD 100.00WC/PD 201.90ZA/PD 1788.00YQ
NEW TICKET TAXES TO COLLECT :
RE-ENTER FOLLOWING COMMAND TO PROCESS
WK*FEX#CA*S2/Y
4 If change is no longer necessary then it can be ignored but instead, if the exchange needs to be confirmed then it must be saved first:
The reservation is updated and the exchange is executed.
As the final step, the PNR needs to be saved.
Automatic exchanges with account code
If the original ticket was issued with account code, you must also include the account code in the exchange command. Otherwise, it will not be possible to retrieve the original fare.
Command | Description | Example |
|---|---|---|
WK*FEX#CA*AC/(acct code) | It prices the exchange with an account code | WK*FEX#CA*AC/ACCOUNT |
Exchanges with manual mask
If the FOP is not included in the exchange command, a mask will be triggered with the fare and tax amounts calculated according to category 31.
Example
Exchanges with ticketing mask
If category 31 fails or if it is not filed and you wish to process the exchange regardless, you will need to create a ticketing manual mask.
Example:
In order to issue the exchange you will need to include the mask number in the command WK*FEX#(FOP)*M(mask nbr)
Example:
Exchange commands no longer supported with ATPCO Pricing
WK*FEX*Q/AD50/DP50
it is not possible to apply manual discounts to exchanges, the fare difference will be applied as coded in cat 31
WK*FEX*PE*50
it is not possible to apply manual penalties to exchanges, the penalty will be applied as coded in cat 31 o overridden with the indicator OVERPE
WK*FEX*OVEREX
WS*FEX
it is not necessary to price the exchange before accessing the exchange mask, upon executing the exchange mask you will retrieve the exchange preview with the exchange quotation details
Automatic Refunds
An automatic refund will be possible when category 33 is coded in ATPCO and the refund conditions apply to the details codified within the category.
Command | Description | Example |
|---|---|---|
W*RF(document number) | Quotation of the refund | W*RF6362310001393 |
Example:
Issuance should be confirmed
Command | Description | Example |
|---|---|---|
W*RF(document number)/Y | Refund confirmation | W*RF6362310001393/Y |
Example:
Most common system responses when processing an Exchange/Refund using the ATPCO flow:
RESPONSE | MEANING | ACTION/SOLUTION |
|---|---|---|
SOME OF THE FLIGHTS MARKED AS FLOWN ARE IN THE FUTURE | When you try to process a parcial exchange and one of the FLOWN’s cupon had a future date |
|
SOME OF THE FLIGHTS OF THE NEW ITINERARY ARE IN THE PAST | There’s a segment with a past date |
|
THE CHEAPEST JOURNEY SOLUTION IS THE SAME AS THE ORIGINAL TICKETED SOLUTION | There’s no changes between the original ticket and the new one. What ATPCO consider a change?
| You can proceed with a manual exchange W*TKT |
TICKET FARE RULES CANNOT BE LOADED | System is unable to find the originally ticketed fare in order to read CAT 31/33’s conditions |
|
CATEGORY 31/33 NOT FILED | The originally ticketed fare does not have a CAT 31/33 filed | Process the Exchange/Refund manuallly |
RESTRICTIONS ON THE TICKETING DATE OR ON THE TRAVEL DATES NOT SATISFIED |
|
”IN THE EVENT OF CHANGES TO TICKETED FLIGHTS |
RESTRICTIONS ON A PORTION OF THE TRAVEL WERE NOT SATISFIED | System is unable to reprice due to the fact that CAT 31/33 is filed with specific restrictions regarding stopovers/connections or/and changes to the first coupon. |
|
ATUTOMATED CHANGES/REFUNDS ARE NOT PERMITTED | 1 or more conditions on CAT 31/33’s Reissue Table are not being met |
|