Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Anchor | ||||
---|---|---|---|---|
|
Table of Contents |
---|
Introduction
KAM is a module that allows the airline to create sub-inventories within the same flight, which are reserved for being commercialize by Tour Operators.
KAM optimizes the commercialization of charter or part-charter flights, where certain places in the inventory are blocked to be exclusively used for one or a group of Tour Operators.
The airline will be able to create two different types of allotments:
- Hard Blocks
- Soft Blocks
Hard Block Allotments are a fixed number of seats agreed between the airline and the tour operator. The total number of seats will remain available for the Tour Operator until the departure date, regardless of whether they have been used or not.
Soft Block Allotments are a fixed number of seats with a deadline time agreed between the airline and the tour operator. After the deadline, unused seats will return to the flight general inventory.
Login Kiu Command and start managing the allotments!
Permission
The keyword KAMADM is required to get access and manage the module.
Settings
Before starting, a few configurations are required in Kiu Click:
Click on "Settings" and will appear two sections:
- General Settings
- Tour Operators
General Settings
In this section the airline will define the general behavior of the module.
General
- Enable Overbooking: Turn on the button to oversell cabin limits when creating allotments.
- Enable with Class Status Closed: Turn on the button to create allotments in classes with status "Closed".
- Enable Closed Limit Sale: Turn on the button to create allotments in classes with Limit Sales in zero.
- Return seats to general inventory after deadline: If turn on the button, after a soft block deadline, unused seats will be released and returned to the flight general inventory.
Fares
- Children and Infants Discounts: Turn on the button if children and infants discounts will be permitted.
- Default Children Discount: Percentage discount that will apply by default for children when creating a fare.
- Default Infants Discount: Percentage discount that will apply by default for infants when creating a fare.
- Show Currency 2 Field: If activated, the "Currency 2" field will be shown in Fares screen. The airline will need a second currency for fare filing, when the quotation IATA area differs from the origin airport IATA area. Activate only if needed.
Issuings
- Hide fare amount on ticket: If activated, when a ticket belonging to an allotment is issued, its fare amount will not be displayed, and the IT indicator will be shown instead.
Info |
---|
Once the settings have been made, remember to click on Save button |
History Button
Click on the "History" button to get historical information about the settings and their changes.
Tour Operators
This section allows the management of Tour Operators. From here, the airline can add a new Tour Operator to the list, or activate/deactivate the existing ones.
Image Modified
Click on "Create" button to add a new tour operator. The 4-character code that identifies a Tour Operator in Kiu will be required.
The Tour Operator have to exist in Kiu in order to be entered in this section.
Create an allotment
Create and add new allotments to a flight entering the following transaction:
VMKAM<FLIGHT>/<DATE><ORIG><DEST>/<ACTION>/<TOUR OPERATOR>-<RBD><ALLOTMENT>,<RBD><ALLOTMENT>.<DEADLINE> |
---|
Example:
VMKAM60/25DECLHRMAD/ADD/A776-C10,B5.1D
Description:
VMKAM | Fixed command |
60 | Flight number |
/ | Slash |
25DEC | Departure date. Format: DDMMM A date range can be created as follows: <START DATE><END DATE> E.g.: 25DEC31DEC |
LHR | City IATA code (Origin) |
MAD | City IATA code (Destination) |
/ | Slash |
ADD | Add is the action to create new allotments. |
/ | Slash |
A776 | 4-character alphanumeric code that identifies the tour operator |
- | Dash |
C | Class or RBD where the allotment will be created. |
10 | Number of seats given to the tour operator. It is the allotment itself. |
, | Comma |
B | Class or RBD where the allotment will be created. |
5 | umber of seats given to the tour operator. It is the allotment itself. |
. | Period. Use this symbol only when creating Soft Blocks. |
1D | Soft Block expiration deadline. Unused seats will return to the general inventory. Number 1 represents the number of days or hours. Valid values: Up to 330 days before departure. After the number type the unit of measure. Available option: D: Days before departure or H: Hours before departure. |
Info |
---|
Up to 20 tour operators can be added in the same transaction. Use a "/" to separate a tour operator from another. Example: |
If the transaction structure and the data entered are correct, the system will respond:
Code Block | ||
---|---|---|
| ||
DONE *** KAM - ALLOTMENTS CREATION OR MODIFICATION IN PROGRESS (THE PROCESS MAY TAKE A FEW MINUTES) *** |
Info |
---|
The process of creating, modifying or deleting allotments might take a few minutes. Check the "Process Status" section in Kiu Click to check the progress. |
The system will create a PNR (reservation) that will identify the allotment.
Main characteristics of an Allotment PNR:
- Ticket/Time Limit section:
- The legend HARD BLOCK KAM will be shown (only for Hard Block types)
- Expiration Date: it is the deadline when the unused seats will be released. It cannot be modified from the PNR.
- Itinerary section:
- The Tour Operator code will be shown after de status.
- It cannot be modified from the PNR.
- Only when the PNR is affected by a schedule change, the .HKALL transaction will be accepted.
- Passenger section:
- The text KAM followed by the Tour Operator code and the number of seats will be shown. This data cannot be modified.
- Contacts / Remarks:
- Contacts and remarks can be added, modified or removed from the reservation.
Modify an allotment
It is possible to modify the following data of an existing allotment:
- Quota: Number of seats already assigned
Modify an existing allotment by entering the following transaction:
VMKAM<FLIGHT>/<DATE><ORIG><DEST>/<ACTION>/<TOUR OPERATOR>-<RBD><ALLOTMENT> |
---|
Example:
VMKAM60/25DECLHRMAD/MOD/A776-C15
Description:
VMKAM | Fixed command |
60 | Flight number |
/ | Slash |
25DEC | Departure date. Format: DDMMM A date range can be created as follows: <START DATE><END DATE> E.g.: 25DEC31DEC |
LHR | City IATA code (Origin) |
MAD | City IATA code (Destination) |
/ | Slash |
MOD | MOD is the action to modify existing allotments. |
/ | Slash |
A776 | 4-character alphanumeric code that identifies the tour operator |
- | Dash |
C | Class or RBD that identifies the allotment to be modified. |
15 | New number of seats given to the tour operator. It is the allotment itself. Options:
|
Delete an allotment
It is possible to delete an existing allotment.
Delete an existing allotment by entering the following transaction:
VMKAM<FLIGHT>/<DATE><ORIG><DEST>/<ACTION>/<TOUR OPERATOR>-<RBD>,<RBD> |
---|
Example:
VMKAM60/25DECLHRMAD/DEL/A776-C,B
Description:
VMKAM | Fixed command |
60 | Flight number |
/ | Slash |
25DEC | Departure date. Format: DDMMM A date range can be created as follows: <START DATE><END DATE> E.g.: 25DEC31DEC |
LHR | City IATA code (Origin) |
MAD | City IATA code (Destination) |
/ | Slash |
DEL | DEL is the action to delete existing allotments |
/ | Slash |
A776 | 4-character alphanumeric code that identifies the tour operator |
- | Dash |
C | Class or RBD that identifies the allotment to be deleted. Several allotments can be deleted in the same transaction, separating the RBD with a "comma". E.g: C,B |
Info |
---|
A used or partially used allotment, cannot be deleted. The system will respond: INVALID ACTION - ALLOTMENT IN USE |
Lists
To get a list of the existing allotments, go to "List" section in Kiu Click.
Process Status
The process of creating, modifying or deleting allotments might take a couple of minutes, so, from the section Process Status, the airline will get access to see the status of each transaction.
Go to Kiu Click and check the status of each process.
Fares
This module allows the airline to manage the fares related to allotments.
When taking a seat from an allotment, the system will quote according to this module (not using the public fares entered in Kiu Fares or ATPCO).
The airline will be able to:
- Create new fares
- Delete existing fares
- Modify existing fares
- Get a list of existing fares
- See historical movements of each fare
Info |
---|
Allotment Fares can only be managed in Kiu Click Module. |
Flight History
All transactions related to the allotments, will be registered in flight history (transaction VIH).
Reservation and Ticketing
Reservation
Start the process by requesting the availability display as follows:
- Tour Operators Users
AT<DATE><ORIG><DEST> |
---|
Example:
AT01JANMXPMAD
System Response:
Code Block | ||
---|---|---|
| ||
AT01JANMXPMAD ** KIU® ALLOTMENT AVAILABILITY ** TO MAD/MADRID, SPAIN FRI 01JAN21 H0000 32D 1 XX 200 Y024 L004 MXPA1 MADB2 10:00 12:00 S 0 773 D 2:00 |
Please note that each class will show the actual and full number of available seats in the allotment, even if there are more than 9 seats available per class.
Seats belonging to allotments will always be confirmed, regardless of wether the reservation has more than 9 seats.
Once the class is selected, continue with the reservation process as usual.
If there are no more seats available, the class will be shown as "Closed".
- Airline Users
On special occasions, airline's users may need to take a seat belonging to an allotment on behalf of the Tour Operator. If necessary, take a seat using the direct sale command by adding the tour operator at the end of the transaction as follows:
0<FLIGHT><CLASS><DATE><ORIG><DEST><STATUS REQUEST><NUMBER OF SEATS>-<TOUR OPERATOR CODE> |
---|
Example:
0200Y01JANMXPMADNN1-A776
System Response:
Code Block | ||
---|---|---|
| ||
0200Y01JANMXPMADNN1-A776 1 XX200 Y 01JAN FR MXPMAD SS1 1000 1200 #A776 |
After this step, continue with the reservation process as usual.
Please note that when an itinerary belongs to an allotment, the Tour Operator Code will be displayed at the end of each itinerary as follows:
Code Block | ||
---|---|---|
| ||
RP/AEP00XX4 - LINEAS AEREAS XX 1.1MILES/PETER »PP123456 1 XX200 Y 01JAN FR MXPMAD HK1 1000 1200 #A776 TKT/TIME LIMIT 1 TX AEP 2200/30NOV-MON CONTACTS 1-MXP 111111 REMARKS 1.»PNR IGNORED BY SYS - TIME OUT ITIN 20:37Z AEP.KIUHELPJF 2044/30NOV20 *XRAJGP |
Ticketing
When issuing a ticket that belongs to an allotment, the Tour Operator Code will be included in the fare basis element after the class:
Code Block | ||
---|---|---|
| ||
ET/9990210029497 TKTT-9990210029497 C1/XRAJGP OD-MXPMAD POI-AEP DOI-30NOV20 IOI-AR000010 0 0 I/ ED-NON END / REF CONDITIONS AND PENALTY APPLY 1.MILES/PETER ADT FOID: PP123456 NIT: /..97 1 MXP XX 200 Y 01JAN 1000 1200 OK Y/A776 20K OPEN FOR USE MAD FARE EUR 100.00 BSR 1.16279 EQUIV USD 116.28 TAX USD TOTAL USD 116.28 TOUR CODE : COMMISSION : /FC MIL XX MAD 100.00EUR100.00END FOP: 116.28 CASH |
Please note that the fare amount will be shown or not, depending on the settings in the "General Settings" section (Kiu Click).
Info |
---|
It will not be possible to quote and issue an itinerary combining general and allotment segments. Allotment itineraries have to be quoted and issued separated. |
There are two different scenarios regarding Tour Operators issuings:
- Non-IATA Tour Operator
- IATA Tour Operator
Non-IATA Tour Operator
If the travel agency has no IATA code, and is issuing tickets through an electronic account (agreement between the airline and the tour operator):
- Tickets belonging to allotments will not debit the amount from the balance.
- Tickets belonging to allotments will not appear in the electronic amount documents display.
- Tickets belonging to allotments will not credit the amount if voided.
- Commissions will not apply.
IATA Tour Operator
- Tickets belonging to allotments will not be included in the RET File.
- Tickets belonging to allotments will not be reported to the BSP.
- Tickets belonging to allotments will be issued with stock provided by the airline (not the one provided by IATA).
- Commissions will not apply.
Sales Report
When retrieving a Sales Report, the system will show an "A" (this letter refers to "Allotment") between the item and the document number.
Passenger List
PNR allotments (the ones automatically created by the system when adding a new block to a flight), and individual PNRs belonging to an allotment (the ones created by the Tour Operators), will be identified in Passenger Lists with a letter "A".
This feature will be shown in both travel agency and airline Passenger Lists.
Fares Display
Type the following transaction to see the allotment fares:
FQD<ORIG><DEST>/D<DATE>/A<AIRLINE CODE>/KA |
---|
The extension KA represents Kiu Allotment.
Example:
FQDMXPMAD/D20DEC/AXX/KA
System Response:
Code Block | ||
---|---|---|
| ||
FQDMXPMAD/D20DEC/AXX/KA * ALLOTMENT FARES * 20DEC2020**20DEC2020/XX MXPMAD LN FARE BASIS OW EUR RT B PEN DATES/DAYS AP MIN MAX 01 C 500 1000 C - - - - - 02 Y 100 200 Y - - - - - |
Queues
The HDQ 39 queue stores PNR of Soft Blocks, whose deadline has expired and their unused seats have been released.
Queue Name: KAM - SOFT BLOCKS RELEASED DUE TO DEADLINE
City: HDQ
Inventory
The allotments and their usage can be checked by displaying VIE information (available for airlines users):
Code Block | ||
---|---|---|
| ||
VIE200/1JAN FLT : 200 773 DATE : 01JAN21 FRI MXP/10:00 /Z1 MAD/12:00 /Z1 32D BRD OFF Cl AC AU BS KAM SA KSS SS AS ABS WL ST MXP MAD C 16 16 0 0 16 0 0 0 0 Y 9 9 0 40 -31 0 0 0 0 M -31 0 0 B -31 0 0 L -31 0 0 A057 - LES AMIS B 10 [ 10] 10 0 A776 - LUCHO TRAVEL Y 25 [ 23] 23 2 L 5 [ 4] 4 1 RELEASE TIME 2020-12-31 10:00 MXP |
If the allotment is a Soft Block, the deadline will be displayed at the end of the appropriate line.
Schedule Change
When a schedule change ocurrs, only the allotment PNRs (those that identify the blocks in the flight), will be displayed to be reaccommodated.
The individual PNRs (those related to the allotment PNRs), will be reaccommodated to the flight where the block PNR is transferred.