Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Commercial indicators that allow service management and marketing can be loaded by command regardless of the load that is made in the creation of legs
Keep in mind that the indicators that are loaded for legs will not apply for segments that are generated automatically in the creation of a service.Therefore the only option is to use these commands. It is also worth mentioning that they can be used in the modification of flights.
Take into account that in order to load or modify the indicator it is not necessary to use the KSMODIFY command (see flight modification)
Next you can read about the indicators.
3.1 Authorization control per cabin
The authorization can be modified with a command. It must be considered that the authorization will be the same for all the classes of each cabin and for each leg of the service, that is, it will only be modified per cabin and per leg.
The commands to modify are:
Code Block | ||||
---|---|---|---|---|
| ||||
KSAU/LEG/MANDATORY CLASS/VALUE |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSAU/AEPCOR/Y/100 |
Description:
KS | Fixed command |
AU | Authorization indicator |
AEPCOR | Leg |
Y | Mandatory class |
100 | Authorization value |
System response in both cases is an IMN display with the modified indicators in the AUTH column. The new authorization that affects the leg and the corresponding segments will be displayed.
Example:
No Format |
---|
LEG BRD OFF # M-C AUTH BS 1 AEP TUC 01 Y Y 100 0 02 B 03 H 2 TUC SLA 01 Y Y 124 0 02 B 03 H AEP-SLA 01 Y Y 100 0 02 B 03 H |
The authorization that had 124 in the AEPTUC section was modified to 100, therefore it also affects the AEPSLA segment because the minimum leaving AEP is 100. The TUCSLA sleg will not be affected.
Block Space Control
You can block spaces for various reasons which will be reflected in the flight inventory and will be discounted from the actual capacity , without modifying its authorization.
As in the authorization, the block is made per cabin and per leg only, affecting the segments involved in that leg. The command to execute the "Block Space" is:
Code Block |
---|
KSBS/LEG/MANDATORY CLASS/VALUE |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSBS/AEPCOR/Y/10 |
KS | Fixed Command |
BS | Block space indicator |
AEPCOR | Leg |
Y | Mandatory class |
10 | Block space amount |
The system response is a display of the INM (inventory) with the added indicators. In the BS column the indicator with the number of blocked places in the corresponding leg will be displayed. You will see the same amount of blocked spaces in the affected segments but with an asterisk next to it indicating that this value was unintentionally placed since it is affected by the leg.
Example:
No Format |
---|
LEG BRD OFF # M-C AUTH BS 1 AEP TUC 01 Y Y 124 10 02 B 03 H 2 TUC SLA 01 Y Y 124 0 02 B 03 H AEP-SLA 01 Y Y 124 10* 02 B 03 H |
A space block of 10 was added to the AEPTUC leg, which also affects the AEPSLA segment, consequently the same amount is added but with an asterisk next to it to indicate that it is involuntarily affected by the leg.
To remove the block, the same command is repeated but with value 0 (zero).
Sales limiters
Sales limiters can be placed by schedule in the process of creating a flight or at any other time when necessary. These limiters will overwrite the ones already established if equipment with pre-established limiters has been used.
The commands to place the sales limiters per schedule are the following:
Code Block | ||||
---|---|---|---|---|
| ||||
KSLS / ROUTE / CLASS / LIMIT |
Example:
Code Block |
---|
KSLS/AEPSLA/B/10 |
KS | Fixed command |
LS | Sales limit Indicator |
AEPSLA | Route |
B | Class |
10 | Sales limit |
The system response is a display of the INM (inventory) with the modified indicators in the LS column. To remove sales limits or leave them without limits, the N indicator mut be used instead of the amount.
Example:
Code Block |
---|
KSLS/AEPSLA/Y/N (N= No Sales limit ) |
You can add or modify limits to several classes at the same time. For each class there must be an amount indicator or you can add several classes and a single amount, which will be applied for all added classes .
Examples:
Code Block |
---|
KSLS/AEPSLA/BHK/40.20.10 KSLS/AEPSLA/BHK/30 |
Instead of the route, you can use ALLALL to refer to all the segments or use for example ALLSLA to include all the segments that arrive at SLA or AEPALL to include all the segments originating AEP . This option is applicable to all load indicator commands that will be detailed below
Warning |
---|
When the sales limiters are loaded in 0 (zero), the specified class will remain in the availability display with the value 0 (zero), accepting the waiting list if it is configured |
Nesting
Classes can be nested in order to market the service. The commands for nesting classes are:
Code Block | ||||
---|---|---|---|---|
| ||||
KSNT / ROUTE / CLASSES / INDEX |
Example:
Code Block |
---|
KSNT/AEPSLA/KNMV/ADD |
KS | Fixed command |
NT | Nesting indicator |
AEPSLA | Route |
KNMV | Classes |
ADD | Add action indicator |
To remove nesting settings, the indicator is changed to DEL. It is important to clarify that in order to nest classes, these must have a sales limit. The response in both cases is a display of the INM (inventory) with the modified indicators in columns NG, NL and LSS.
In NG-NL columns , you can see the nesting group to which the specific classes belong (NG: Nesting Group) and each class category (NL: Nesting Level).
The LSS column will indicate the new authorized sales limit according to the class nesting
Example:
No Format |
---|
LEG BRD OFF # M-C AUTH BS LS NG-NL LSS TSO TSC NLOS WLL 1 AEP BHI 01 Y Y 100 0 0 0 0 02 E 10 1-1 45 0 0 0 03 G 10 1-2 35 0 0 0 04 V 25 1-3 25 0 0 0 |
EGV classes were nested in that hierarchy order , therefore NG column will display them with a number 1 meaning that they belong to Group 1. NL is the order of importance of each class. E shows number 1, G 2 and V 3 respectively. Class E has a sales limit of 10, G also of 10 and V of 25 (LS column), but being hierarchical, that limit is modified and will be reflected in the LSS column, therefore E class will have a limit of 45, G of 35 and V of 25 and will be deducted from each other.
Temporary opening and closing of classes
Classes can also be configured to be opened and / or closed automatically with a certain number of hours before flight departure.
The commands are the following:
Automatic opening of classes
Code Block | ||||
---|---|---|---|---|
| ||||
KSSO/ROUTE/CLASS/VALUE |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSSO/AEPJUJ/V/240 |
KS | Fixed commmand |
SO | Sales opening indicator |
AEPJUJ | Route |
V | Class |
240 | Value( Hours. e.g. 240 hours) |
Automatic closing of classes
Code Block | ||||
---|---|---|---|---|
| ||||
KSSC/Route/CLASS/VALUE |
Example :
Code Block | ||||
---|---|---|---|---|
| ||||
KSSC/AEPJUJ/V/240 |
KS | Fixed command |
SC | Sales Closure Indicator |
AEPJUJ | Route |
V | Class |
240 | Value(Applicable in amount of hours e.g. 240 hours) |
System response in both cases is a an IM display (inventory) with the modified indicators. In the TSO column you will see the number of hours before the classes are open for sale and in the TSC the number of hours before closing for sale . If no indicator is added or if you want remove the indicator indicator 0 (zero) will apply.
In the same way that it is applied to the other indicators, the indicator can be set to several classes at the same time, placing the classes together to modify, or apply to all the segments using ALLALL to refer to all of them.
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSSC/AEPMDZ/BHKMN/48 |
Overbooking logic
The criteria to be used to load the overbooking logic is similar to the one used for sales limiters. You must first verify KSMCL table before loading the logic.
The command to load the overbooking logic is as follows:
Code Block | ||||
---|---|---|---|---|
| ||||
KSOS/ROUTE/CABIN/LOGIC |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSOS/AEPSLA/Y/1 |
KSOS | Fixed command |
AEPSLA | Route |
Y | Cabin |
1 | Overbooking logic number |
The answer System response is a display of the INM (inventory) with the modified indicators. In the NLOS column you will see the logic number to apply if you have it or it will be empty in case you do not have any type of overbooking.
To remove the logic, the indicator 0 (ZERO) is used instead of the logic number.
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSOS/AEPSLA/Y/0 |
You can also do the entry to modify or add logic to several cabins at the same time. For each cabin there must be an amount indicator or you can add several cabins and a single amount, which will be applied to all the cabins that were added.
Ejxamples:
Code Block |
---|
KSOS/AEPSLA/FCY/1.5.7 When there are several cabins or logic,a dot should be used to separate from each other |
Code Block |
---|
KSOS/AEPSLA/FCY/6 |
Waiting list limiters
You can limit the waiting list capacity of each class or close it so that it is not accepted.
The command is the following:
Code Block | ||||
---|---|---|---|---|
| ||||
KSWL/ROUTE/CLASS/LIMIT OR INDEX |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSWL/AEPSLA/B/10 |
KS | Fixed Command |
WL | Waiting List |
AEPSLA | Route |
B | Class |
10 | Waiting List acceptance limit |
Waiting list limiters can be used for:
- A certain value to limit acceptance.
- A value 0 (zero) to close it and no passengers acceptance. Availability display will show the class followed by the C indicator
- An index N to open waiting list acceptance without limits.
System response is an INM display with the modified indicators in the WLL column.
Command can be applied to several classes at the same time (see KSLS command).
Examples:
Code Block | ||||
---|---|---|---|---|
| ||||
KSWL/AEPSLA/BHK/40.20.10 |
Code Block | ||||
---|---|---|---|---|
| ||||
KSWL/AEPSLA/BHK/30 |
Instead of the route, you can use ALLALL to refer to all the segments or use for example ALLSLA to apply to all segments arriving SLA or AEPALL to all the segments originating AEP . This option is applicable to all load indicator commands that will be detailed below.
Closure and opening of booking classes
Booking classes can be closed, and will remain in the inventory but can not be viewed in availability or sold.
Booking classes closed with this procedure can be overbooked manually (OB or KK) or by schedule change (in reaccommodaation).
These classes can be opened with the same closing procedure, changing the indicators. The commands are the following:
Class Closure
Code Block |
---|
KSCL/ROUTE/CLASS/INDEX |
Ejemplo:
KS | Fixed command |
CL | Class status indicator |
AEPSLA | Route |
B | Class |
CLOSE | Closing indicator( OFF or STOP can be used) |
Class opening
Code Block | ||||
---|---|---|---|---|
| ||||
KSCL/ROUTE/CLASS/INDEX |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSCL/AEPSLA/B/OPEN |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSCL/ALLALL/BHKMN/OPEN |
KS | Fixed command |
CL | Class status indicator |
AEPSLA | Route |
B | Class |
OPEN | Opening index (ON or GO can be used) |
System response is an INM (inventory) displayed with the modified indicators in the STATUS column. A letter C will be observed in the closed class or it will be empty in case the indicator is removed.
Several classes can be closed or opened at the same time the same way you can do with other indicators.
Code Block | ||||
---|---|---|---|---|
| ||||
KSCL/ALLALL/BHKMN/OPEN |
Booking classes on request
Booking classes can be configured so that they can be on permanent request. Bookings that are generated on these classes will be placed on queue and will generate a warning so the system administrator can check and confirm or reject them.
The command is the following:
Code Block | ||||
---|---|---|---|---|
| ||||
KSRQ/ROUTE/CLASS/INDEX |
Example:
Code Block |
---|
KSRQ/AEPMDZ/V/ON |
KS | Fixed command |
RQ | Booking class request indicator |
AEPMDZ | Route |
V | Booking class |
ON | Class request indicator (OPEN or GO can also be used) |
To remove the booking class from pending request status, the index must be changed to OFF (CLOSE or STOP are also accepted)System response in both cases is an INM display with the modified indicators. In the STATUS column, a letter R will be present adjacent to the booking class or it will be empty in case the indicator is removed.
In the same way that it is applied to the other indicators, you can set several classes on request or remove them all at the same time, placing the classes together to be modified.
Example:
Code Block |
---|
KSRQ/ALLMDZ/BHKMN/ON |
Overbooking inhibition control
This control allows to inhibit the overbooking of classes despite having the keywords that enable overbooking (OVERSL, CHKOSL). The indicator will be reflected in the inventory of the flight under the ST column with the letters Ox. This function only allows overbooking in the rea accommodation by schedule change or through mass reaccommodation (VMOVE function).
Inhibit the class overbooking
Code Block | ||||
---|---|---|---|---|
| ||||
KSIO/ROUTE/CLASS/INDEX |
Example:
Code Block |
---|
KSIO/AEPMDQ/B/ON |
KS | Fixed comnand |
IO | Overbooking inhibition indicator |
AEPMDQ | Route |
B | Class |
ON | Overbooking inhibitor activation index
|
Note |
---|
ON , OPEN o GO can be used |
Remove the overbooking inhibition of a class
Code Block | ||||
---|---|---|---|---|
| ||||
KSIO/ROUTE/CLASS/INDEX |
Example:
Code Block |
---|
KSIO/AEPMDQ/B/OFF |
KS | Fixed command |
IO | Overbooking inhibitor indicator |
AEPMDQ | Route |
B | Class |
OFF | Overbooking inhibitor deactivation index |
Note |
---|
OFF ,CLOSE or STOP can be used |
Options
The parameter can be entered for several classes and several segments.
The input command is:
Code Block |
---|
KSIO/ALLALL/BHKMN/ON |
KS | Fixed command |
IO | Overbooking inhibitor indicator |
ALLALL | Route: ALLALL indicates all flight marketing segments |
BHKMN | Booking Classes |
ON | Overbooking inhibitor activation index |
Note | |||||||
---|---|---|---|---|---|---|---|
Booking clases can be added one after the other or a blank space can be left assuming that it will apply to all classes.
System response is an INM (inventory) displaying the modified indicators in the STATUS column. An Ox indicator will be displayed or it will be blank in case the indicator is removed.
|
Catering service
The catering service can also be modified. It will apply to all classes of the segment
The command to execute is:
Code Block | ||||
---|---|---|---|---|
| ||||
KSML/ROUTE/SERVICE INDICATOR (up to 3 services) |
EjemploExample:
Code Block | ||||
---|---|---|---|---|
| ||||
KSML/AEPJUJ/D |
DescripciónDescription:
KS | Fixed command |
ML | Catering service indicator (meal) |
AEPJUJ | Route |
D | Service Indicator |
To view all available catering service options, use the VMML command.
System response is a display of the INM (inventory) with the added or modified indicator. They will be displayed in the ML column.
Once added, they cannot be modified again. To change, the command must be ignored with KSIR.
3.12 Information field
You can load information fields that will be displayed in an availability request. The loading of the same is done as follows:
Code Block | ||||
---|---|---|---|---|
| ||||
KSRM/ROUTE/FREE TEXT |
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
KSRM/AEPJUJ/BOARDING GATE 12 SECTOR C |
KS | Fixed command |
RM | Information Field indicator (remark) |
AEPJUJ | Route |
BOARDING GATE 12 SECTOR C | Free Text |
System response is an INM display (inventory) with the added text in a REMARK field below each applicable segment
To delete a comment, the entry is repeated without the text. For example, using the previous command, it would be:
Code Block | ||||
---|---|---|---|---|
| ||||
KSRM/AEPJUJ |
In the same way as the other indicators, they can be applied to all segments using ALLALL to refer to all of them.
You can also add a comment, which will be recorded in the reservation and when the e-ticket is printed. The command is the same but placing a double slash after the route.
Example:
Code Block |
---|
KSRM/AEPJUJ//OPERATED BY AIR ZAMBIA |
Note |
---|
If you want to use both remark types you must first enter the remark // (which is included in the PNR and ITR) and then the remark / which is only included in the availability display. |
Departure and Arrival Terminals You can load the departure and arrival terminals by airport. The command supports up to 2 digits as detailed below:
Departure terminal
Code Block | ||||
---|---|---|---|---|
| ||||
KSTD/BRD/TERMINAL (maximum 2 digits) |
EjemploExample:
Code Block | ||||
---|---|---|---|---|
| ||||
KSTD/AEP/C |
DescripciónDescription:
KS | Fixed command |
TD | Departure Terminal |
AEP | Departure airport code |
C | Terminal indicator |
Arrival Terminal
Code Block | ||||
---|---|---|---|---|
| ||||
KSTA/OFF/TERMINAL (maximum 2 digits) |
EjemploExample:
Code Block | ||||
---|---|---|---|---|
| ||||
KSTA/COR/A2 |
DescripciónDescription:
KS | Fixed command |
TA | Arrival terminal indicator |
COR | Arrival airport code |
A2 | terminal indicator |
To delete the terminals that are already assigned the commands are the following:
For departure:
Code Block | ||||
---|---|---|---|---|
| ||||
KSTD/AEP/DEL o bien KSTD/AEP |
DEL (Delete) indicates the deletion by leaving the Departure Terminal (TD) column empty or leaving it blank after the departure airport code.
For arrivals:
Code Block | ||||
---|---|---|---|---|
| ||||
KSTA/COR/DEL o KSTA/COR |
The criteria to be used is the same as with the departure, changing the terminal indicator to the arrival indicator (TA).
Service Type (Regular or Charter)
To modify or add the service type, the following command must be executed
Code Block | ||||
---|---|---|---|---|
| ||||
KSTY/AEPMDQ/<service type> |
Example:
KA*6790
KS.1
KSTY/AEPUSH/C
KSAVE
No Format |
---|
LEG BRD OFF # M-C AUTH BS LS NG-NL LSS TSO TSC NLOS WLL 1 AEP BHI 01 Y Y 100 0 0 0 0 02 E 10 1-1 45 0 0 0 03 G 10 1-2 35 0 0 0 04 V 25 1-3 25 0 0 0 |
Table of Contents |
---|