Inventory options
By airport
You can request an inventory from a particular airport on the route: The command is:
Code Block | ||
---|---|---|
|
VIE4900/05NOVCOR
COR indicates only segments from COR
|
Code Block | |
---|---|
|
| |
VIE4900/05NOV
Only if the origin of the terminal you are requesting is AEP, is it not necessary
clarify the departure airport
|
Note |
---|
If the terminal that is requested in the VIE entry is from the origin, it can be ignored. |
From an availability display
You can request the inventory from a previously displayed availability. The command is:
Code Block | ||
---|---|---|
|
VIEA Item number |
Description:
VIE | Fixed command |
A | Availability indicator |
ITEM NUMBER | Item number from the availability display |
In this case,the origin is considered from the origin city of the requested availability.
From an itinerary of a PNR
You can request the inventory from a previously displayed PNR. The command is
Code Block | ||
---|---|---|
|
VIEP Item Number |
Description:
VIE | Fixed command |
P | PNR indicator |
Item number | segment number in PNR |
In this case,the origin is considered from the boarding point of the segment.
Display unconfirmed sales
You can generate a list of unconfirmed sales, that is, those PNRs that are not closed and that aret are in the process of creation.
To check the list, you must enter the following command and you must have duty 8 in your user sign.
In case seats are taken on a flight but the PNR is not recorded yet a difference between the passengers in a list and the seats taken will be found.
Example 1
Example 2
In example 1, there are 39 booked seats (ABS 39), 20 on the AEPMDQ leg and 19 on the AEPBRC leg, but when viewing the list (Example 2), the header of the same indicates that there are 34 (ABS 34), 17 from AEPMDQ and 16 from AEPBRC, to see where the difference comes from , the following command is executed:
Code Block | ||
---|---|---|
|
VIE {flight} / {date} / SS (see Example 3)
|
System displays seats in each route that are being taken at that time but still not recorded in the PNR.
SEGMENT SELL DETAILS
AEP/BRC Y 2
AEP/MDQ Y 3
Example 1
Example 2
Example 3
This example indicates that seats are being taken without recording 2 on the AEPBRC leg and 3 seats on the AEPMDQ leg
Display unconfirmed sales lists
You can generate a list of unconfirmed sales, that is, those PNRs that are not closed and that are in the creation process.
To verify the list, you must enter the following command and you must have Duty 8 in your user signature.
Code Block | ||
---|---|---|
|
VSSLIST |
When performing this command, the system will respond the following information:
Description:
DEVICE | Device that is blocking spaces |
MIN | Minutes since spaces were taken |
ITIN | Flight, class, date, day, section and number of blocked spaces |
Note |
---|
System will show those seats that have been taken for more than 10 minutes and still have not been recorded ,and after 25 to 30 minutes of inactivity will then be released. |
Force Release of Unconfirmed Sales
You can force the release of seats taken by travel agencies using the following process:
Code Block | ||
---|---|---|
|
VSSLIST/I/LIMI028001
|
Description
VSSLIST/I | Fixed command |
/ | Slash |
LIMI028001 | Terminal Number |
Info |
---|
|
Inventory History
Once flights are created, a copy of how it was created and every modification is kept in the flight history. Keep in mind that when a flight is split, the system deletes all indexes placed manually (Space Control VM commands) saving only those that have been placed by schedule change (KS commands).
The command to see the flight history is:
Code Block | ||
---|---|---|
|
VIH{flight}/{date} |
The display shows a copy of the inventory at the time it was created, with the indexes of the equipment . Changes occured in the indicators will be recorded in the history.
Example
There were some changes to the indexes of this flight that are being reflected in the history . For example, In the first change the flight was retrieved to be canceled:
The command made is shown , also the terminal from where it was made and the agent, time and date of the execution. Also the modifications made by space control or flight loading can be seen reflected as follows:
In the changes made with flight loading commands such as the KS, only the index that identifies the change and the rest of the command made, in the space control (VM) appears the
complete command In the end, the agent, time and date of the execution will always be displayed.
The VIH of a flight will remain in the system until 48 hours after the operation of the flight, then will be removed from the system.
Departures and arrivals information
This command allows you to view the departures and arrivals of flights individually or in groups, by airport or by sections, showing the operation with their schedules and occupation by legs.
The options are the following:
Complete Schedule:
Code Block | ||
---|---|---|
|
VLC*ALL |
Code Block | ||
---|---|---|
|
VLC*ALLALL |
By flights:
This command allows you to visualize by flight, operation and occupation.
Code Block | ||
---|---|---|
|
VLC * Flight By flight number, a single flight
VLC * Flight * Flight By flight number, several at a time
VLC * Flight / Optional Date with date of departure (if date is not specified, it defaults to today´s date.)
|
FLT Flight number (Flight) |
This command shows the flights sorted in ascending order by flights numbers .
By segments
This command allows you to visualize by segment, the flights that are operating between the segment requested for a specific day. If no date is indicated the default is the current day.
You can replace one of the airports with the word ALL, this will indicate that the request will be the departures from a specific airport to all possible destinations or vice versa, from all
destinations to a specific airport.
Code Block | ||
---|---|---|
|
VLC*AEPCOR/23MAR |
Unlike the flight option command, a TIME column is shown at the beginning, which indicates the order of the flights by departure time from the requested segment.
In case a request is made from all airports to a specific one, the order will be given by the schedule of arrival at the specific airport. For example:
By airport
This command allows you to visualize all the departures and arrivals of a specific airport. If no date is enter it defaults to the current day.
Code Block | ||
---|---|---|
|
VLC*AEP |
Unlike the command option by segment, it shows an ST column after the TIME column, which indicates whether the flight leaves the requested airport (OUT) or arrives at the airport (IN).
In the case of circular flights, they will be shown twice, once when it takes off and once it lands. See in the example the flights 4134, 4320 and 4390. In the latter you can see that it departs
at 2330 and arrives at 0330 + 1, that is, the next day. The reason is that the commercial date of it is the day of the request. Therefore, it will enter within the requested date and not the next day.
Sales information by class and business parameters
There is a command to view sales inventory by class only. This command gathers characteristics of a flight inventory but only showing sales by classes and their indicators corresponding to the merchandising The command is:
Code Block | ||
---|---|---|
|
VIS {flight} / {date} ALL |
ALL Indicates the entire route |
---|
The header shows the same data as the inventory (VIE) and the indicators are the following:
BRD OFF | Origin and destination |
CL Classes | Classes |
SS | Sold Seats |
WL | Waiting list |
WLL | Waiting list acceptance |
LS | Sales Limit |
LSS | Calculation of the sales limit with nesting |
NG-L | Nesting and Group Level |
OS-LOS | Overselling amount and applied logic |
TSO | Temporary sales opening |
TSC | Temporary sales closure |
ST | Status |
Options:
You can use the minimum input command that would be:
Code Block | ||
---|---|---|
|
VIS{flight} |
Using this command, it defaults to the current day and the origin airport only. It can also be requested by specific airport.
Example
VIS4520/COR |
---|
Total Sales Information per cabin
There is a command to display total sales per cabin. This command shows the partial booked seats by segment and by cabin and the booked per cabin.
Code Block | ||
---|---|---|
|
VIL {flight} / {date} |
Description
FLT: 301 | Flight number |
DATE 30APR18 | Departure Date |
(38D) | Days left for departure |
EQP: 340 | Equipment |
FROM | Origin |
TO | Destination |
DEP | Departure Time |
ARR | Arrival Time |
CAB | Cabin |
AU | Authorized Seats |
AS | Booked by segment |
ABS | Booked by leg |
Options:
You can use the minimum input command:
Code Block | ||
---|---|---|
|
VIL {flight} |
Using this command, it defaults to the current date and the airport of origin only. It can also be requested by specific airport.
Example:
VIL4520/COR |
---|
Catering information
This commands displays amount of services that will have to be provided for a specific flight.
Code Block | ||
---|---|---|
|
VCC {flight} / {date} {route} |
Example:
VCC323 / 27MAR |
---|
Description
BRD-OFF | Origin and destination |
DEP | Departure time |
ARR | Arrival Time |
MEAL | Flight service |
EQP | Equipment |
AC | Total aircraft capacity |
CAB | Cabin Type |
AU | Total authorized per cabin |
ADT | Number of adult passengers |
CHD | Number of children passengers |
MM | Number of passengers subject to space |
TTL | Total services per departure airport |
INF | Number of infant passengers |
HM | Number of" request status passengers |
The options for the request of the lists can be the following:
Code Block | ||
---|---|---|
|
VCC {flight} When no date is specified it defaults to current day.
VCC {flight} / {date} Specific date
VCC {flight} / {date} {BRD} Specific date and origin |
Occupancy per route
Through this command you can see at first glance the number of flights offered by a route by date or by parameter of dates and its general occupancy The input command is:
Code Block | ||
---|---|---|
|
VAF {route} / {date} |
Example:
VAFAEPCOR/01DEC |
---|
Description
DATE | Departure date |
DOW | Day of the week |
FLT | Flight number |
NLG | Flight Legs Number |
CAB | Flight cabins (Economy, Business, First) |
AU | Seats Authorized for sales (number of seats authorized for sales and overbooking logic OS) |
BS | Blocked seats |
OS | Number of seats enabled for overbooking |
SS | Number of seats sold |
ABS | Number of seats sold per leg |
SA | Flight Availability(In this field the values of the mandatory class are shown |
Note |
---|
The order of flights is according to your departure time. |
You can also make the request for a date parameter. The command is:
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} |
Example
VAFAEPCOR/01JAN-09JAN |
The flights order is by date and within the date, by departure schedule.
VAF entry can be requested to verify some flights in particular:
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} * {flight}, {flight} |
Example
VAFAEPCOR/01JAN-09JAN*3136,3140 |
---|
Note |
---|
You can verify up to 5 flights per command and each of them must be separated by commas. |
VAF entry can be requested by verifying the information of a particular cabin only (F: First Class; C: Business Class; Y: Economy Class):
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} * {cabin} |
Example:
VAFAEPCOR/01JAN-09JAN*Y |
VAF entry can be requested by verifying flight information for the specified days of the week:
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} * {day of the week} |
Example
VAFAEPCOR/01JAN-09JAN*MO |
Note |
---|
The indicators of the days of the week are the following: |
MO Monday
TU Tuesday
WE Wednesday
TH Thursday
FR Friday
SA Saturday
SU Sunday
These indicators can be combined to request flight information on some days of the week:
Example: VAFAEPCOR / 01JAN-09JAN * MOFR (flights on Mondays and Fridays).
The different filters can be combined with each other as shown below:
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} * {flights} * {cabin} * {frequency} |
Example
VAFAEPBRC/05NOV-10NOV*3312,4200,9500*Y*MOTUWE |
VAF with primary compartment class closed
You can view if primary compartment classes are closed by adding the /C parameter at the end of the entry.
Code Block | |
---|---|
|
| |
VAFEZEMAD/16FEB/C
|
The / C filter can be used with any of the command combinations (date range, flight specific, days of the week) It also supports export to .CSV format.
The information contained in the VAF can be exported to a CSV file (file separated by commas) adding the extension -CSV at the end of the entry
Code Block | ||
---|---|---|
|
VAF {route} / {date-date} * {flights} * {cabin} * {frequency} -CSV |
Inventory Control
The commands listed below are used for the commercial management of flights. You can apply to particular flights or flight parameters.
Warning |
---|
Keep in mind that any of the actions applied by the Flight loading module, after the inventory control commands, will be reflected replacing the setting previously configured during the flight creation. |
Sales limits Control
Sales limits can be controlled manually from fixed commands. You can set or remove sales limiters on any of the flights that are operational, whether or not they have limits prefixed in the flight load. The indicator will be reflected in the flight inventory under the acronym LS.
The command is:
Set Sales Limits
To set sales limits, the command is as follows:
Code Block | ||
---|---|---|
|
VMLS {flight} {class} {date} {route} {index} |
Example:
VMLS 4118 K 22MAR AEPSLA 10 |
Response
DONE
Remove sales limits
To remove sales limits, the command is similar, adding the words OPEN , GO or ON in the index.
Example
VMLS 4118 K 22MAR AEPSLA OPEN |
Close sales limits
To close the sales limits, the same previous command is executed but adding CLOSE or STOP or OFF, or the digit 0 (zero). in the index.
VMLS 4118 K 22MAR AEPSLA CLOSE |
Options
You can set sales limits to all classes ,or fight segments by date period.
Per period of dates and days of the week
Code Block | ||
---|---|---|
|
VMLS4118K18MAR25MARAEPSLA10MOTUWETHFR |
Note |
---|
Two digit code is used for days of the week. MO Monday,TU Tuesday, WE Wednesday, TH Thursday, FR Friday, SA Saturday and SU Sunday. The start and end dates are added together,then the index, and every single day will limit sales in the specified , together. If the day. If no date is specified the command works for all the operational period of the flight. |
By classes
Code Block | ||
---|---|---|
|
VMLS4118*22MARAEPSLA10MO |
If an asterisk (*) is added instead of the classes will have effect on all classes.
By flight segments
Code Block | ||
---|---|---|
|
VMLS4118K22MARALLALL10MO |
ALLALL is added instead of the segment, thus acting on all segments of the flight.
Note |
---|
You can combine all the options or just some of them. |
Example:
VMLS4118*18MAR25MARAEPALL20 |
All classes, by dates parameter, all flight segments of the departing from AEP and all days of the week.
Wait List Control
The waitlist can be closed, open or limited . The indicators will be reflected in the flight inventory under the acronym WLL. The commands to handle it are:
Close the Waiting List
Code Block | ||
---|---|---|
|
VMWL {Flight} {Class} {date} {route} STOP |
Example:
VMWL4340N10MARAEPMDQSTOP |
Response
DONE
Note |
---|
The STOP or CLOSE or OFF indicator can be used |
Open the waiting list
Code Block | ||
---|---|---|
|
VMWL {flight} {class} {date} {route} GO
|
Example:
VMWL4340N10MARAEPMDQGO |
Note |
---|
The GO or OPEN or ON indicator can be used |
Limit the waiting list
Code Block | ||
---|---|---|
|
VMWL {flight} {class} {date} {route} 10 |
Example:
VMWL4340N10MARAEPMDQ10 |
Response:
DONE
Note |
---|
When closing or when the limit is reached the waiting list will appear in the flight inventory (VIE), next to the WL counter of each class a letter C, which will indicate that it is closed. When it is reopened the letter C disappears. |
Options
The same commands can be loaded for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid loading the indicators one by one.
The combined input command is:
Code Block | ||
---|---|---|
|
VMWL 4118 * 15MAR31JUL ALLALL STOPMOTUWEFR
|
Description
WMWL | Fixed command |
4118 | Flight |
* | All classes |
15MAR | Start Date |
31JUL | Stop Date |
ALLALL | All route /Segments |
STOP | Indicator |
MOTUWEFR | Days of the week |
Inventory adjusment: KK command
Sometimes there may be system or process errors where the inventory does not correctly reflect the number of bookings or the total values resulting from the calculations, such as the LSS, SA, ABS columns of the VIE command. In these cases, the agent that has duty 7 or 8 will be able to execute this command that allows to synchronize the inventory of the flight in the indicated date d. This process only takes action in cases of discrepancies mainly from taken seats without saving or system processes and recorded in the flight history and visualized through the HIV command.
Code Block | ||
---|---|---|
|
KK<flight number>/<date> |
Example:
Code Block | ||
---|---|---|
| ||
KK4114/31JAN
|
Description
KK | Fixed command |
4114 | Flight number |
/ | Slash |
31JAN | Date |
Info |
---|
|
If no date is entered in the command , a list of the flights checked and a summary with the number of flights analyzed and the number of flights to be adjusted will be displayed.
No action responses
NEED DUTY | Agent must have duty code 7 or 8 in his/her signature |
FLIGHT OK - NO ADJUSTMENT REQUIRED | No discrepancy detected on the indicated flight / date |
FLIGHT IGNORED - SPACES TAKEN WITHOUT PNR | No adjustment is applied because there is at least one space taken in the system without generating the corresponding PNR yet |
FLIGHT IGNORED - INVENTORY ADJUSTMENT IN PROGRESS | No adjustment is applied because there is at least one space that was being affected by the processes of the inventory adjustment system |
Response with action
If the indicated flight has some discrepancy that can be adjusted, the system will display the following information:
After confirming the command with / Y, the system will show the following response:
Closure Control and Class Opening
You can close or open the classes of a flight, a particular segment or an entire flight . The function is to hide that class and inhibit the sale. The indicator will be reflected in the inventory of the flight under the symbol ST with a C (Close).
This function does not prevent overbooking or reaccomodation by a schedule change.
Close the class of a flight
Code Block | ||
---|---|---|
|
VMCL {flight} {class} {date} {route} STOP |
Example
VMCL4104V31MARAEPSLASTOP |
Response:
DONE
Note |
---|
The STOP or CLOSE or OFF indicator can be used |
Open the class of a flight
Code Block | ||
---|---|---|
|
VMCL {flight} {class} {date} {route} GO
|
Example
VMCL4104V31MARAEPSLAGO |
Response:
DONE
Note |
---|
The GO or OPEN or ON indicator can be used |
Options
The same commands can be loaded for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid loading the indicators one by one.
The input command is:
Code Block | ||
---|---|---|
|
VMCL 4104 / 31MAR31JUL ALLALL STOPMOTUWEFR |
Description
VMCL | Fixed Command |
4104 | Flight Number |
/ | All classes |
31MAR | Start Date |
31JUL | Stop Date |
ALLALL | All segments |
STOP | Indicator |
MOTUWEFR | Days of the week |
Class requirements Control
A class can be set for request only even though there are seats available . This function allows to control sales orders.Each sales request will be entered with HM code (required) in the PNR and it will automatically be sent to queue 20 or 21.
In availability, the class that is found with this indicator will appear with a letter R. The indicator will be will reflect in the inventory of the flight under the acronym ST with an R (Required)
Set a Class in Request Mode
Code Block | ||
---|---|---|
|
VMRQ {flight} {class} {date} {route} ON
|
Example:
VMRQ4104V31MARAEPSLAON |
Remove a Class in Request mode
Code Block | ||
---|---|---|
|
VMRQ {flight} {class} {date} {route} OFF
|
Example:
VMRQ4104V31MARAEPSLAOFF |
Response
DONE
Note |
---|
The OFF or CLOSE or STOP indicator can be used |
Options
The same commands can be used for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid adding the indicators one by one and setting a
flight or several as request status.
The input command is:
Code Block | ||
---|---|---|
|
VMRQ 4104 / 31MAR31JUL ALLALL ON MOTUWEFR
|
Description
VMRQ | Fixed Command |
4104 | Flight number |
/ | All classes |
31MAR | Start Date |
31JUL | Stop Date |
ALLALL | All segments |
ON | Indicator |
MOTUEWEFR | Days of the week |
Nesting
Class nesting can be controlled by flight. All classes that have a hierarchical order must have sales limits to allow nesting.Several groups of nested classes can be added within the same cabin The number of groups is unlimited.
The indicator will be reflected in the flight inventory under the acronym NG-L (NG: Nesting Group L: Level). G represents and the L the class hierarchy. LSS column will display sales limits calculated on the basis of the sales limits for each class and nesting. The nested classes in each group will be deducted from each other as sales occur.
Set Class hierarchy
Code Block | ||
---|---|---|
|
VMNT {flight} {classes} {date} {route} ADD
|
Example:
VMNT 4600 BHKM 31MAR AEPMDQ ADD |
Response:
DONE
Description:
VMNT | Fixed Command |
4600 | Flight Number |
BHKM | Classes in hierarchy order from highest to lowest B H K and M |
31MAR | Date |
AEPMDQ | Route |
ADD | Add indicator |
The command to add class hierarchy is repeated as many times as many groups are added. Each group will be assigned a number and next to it the class hierarchy.
Remove class hierarchy
Code Block | ||
---|---|---|
|
VMNT {flight} {classes} {date} {route} DEL
|
Example:
VMNT 4600 BHKM 31MAR AEPMDQ DEL |
Response:
DONE
Description:
MNT | Fixed command |
4600 | Flight Number |
BHKM | Classes in hierarchy order from highest to lowest B H K and M |
31MAR | Date |
AEPMDQ | Route |
DEL | Indicator to Remove |
Options
The same commands can be added for all segments, for a range of dates and certain days of the week. This would avoid adding the indicators day by day.
The input command is:
Code Block | ||
---|---|---|
|
VMNT 4104 BHKM 31MAR31JUL ALLALL ADD MOTUWEFR
|
Description:
VMNT | Fixed command |
4104 | Flight number |
BHKM | Classes |
31MAR | Start Date |
31JUL | Stop Date |
ALLALL | All segments |
ADD | Add indicator |
MOTUEWEFR | Days of the week |
Authorization Control
The original authorization of the flights can be modified, increasing or decreasing it even bringing it to zero. Such command can be executed by cabin from its corresponding cabin class (F, C or Y) and by sections or for the whole flight but not by segments, affecting all the classes created in the segment or flight
Increase or decrease the authorization
Code Block | ||
---|---|---|
|
VMAU {flight} {class} {date} {route} {authorization} |
Example:
VMAU4600Y15MAYAEPTUC100 |
Response
DONE
Description:
Increase or decrease an authorization on a flight
You can also increase or decrease the authorization on a flight. One option is to execute the Step 7.1 command for the desired amount. The other option is to execute the following command:
Code Block | ||
---|---|---|
|
VMAU4600Y15MAYAEPTUC15ADD
|
The ADD indicator will order you to increase the authorization in 15 seats more.
To decrease the number of seats of the authorized value is the following command:
Code Block | ||
---|---|---|
|
VMAU4600Y15MAYAEPTUC15DEL
|
The DEL indicator will order that you reduce the authorization in 15 fewer places.
Options
The same commands can be added by date period, for the entire flight and certain days of the week. This would avoid adding the indicators day by day.
The input command is:
Code Block | ||
---|---|---|
|
VMAU4104Y31MAR31JULALLALL70MOTUWEFR |
Description:
Y | Cabin class |
31MAR | Start date |
31JUL | Stop Date |
ALLALL | All segments |
MOTUWEFR | Days of the week |
Block Space
A block can be placed on a flight in such a way that it reduces a certain number of seats by whatever the reason is, crew, technical limitation, etc., called "block space".
The block is done by cabin, using the cabin class and by sections or by the complete flight but not by segments. It must ba taken into account that when segments are blocked, all the segments belonging to such legs are also affected.
Block space on a flight
Code Block | ||
---|---|---|
|
VMBS {flight} {class} {date} {route} {space amount} |
Example:
VMBS4176Y10MAYCORSLA20 |
Response
DONE
Description:
VMBS | Fixed command |
4176 | Flight number |
Y | Cabin Class |
20MAY | Date |
CORSLA | Route |
20 | Leg/Flight authorization |
The change is reflected in the BS inventory column of. The command was executed on the CORSLA leg but it also affects the AEPSLA segment, thus it the BS indicator is modified with a new value of 20 *, the asterisk will indicate that it is being Inadvertently affected In the SA column (available seats) the offer was reduced by 20 seats.
Remove the space block on a flight
Code Block | ||
---|---|---|
|
VMBS {flight} {class} {date} {route} {0 = zero}
|
Example:
VMBS4600Y31MARAEPMDQ0 |
Response:
DONE
Description:
VMBS | Fixed command |
4176 | Flight number |
Y | Cabin Class |
20MAY | Date |
CORSLA | Route |
0 | Removes space block |
The BS column will remain at zero.
Increase or decrease a space block on a flight
You can increase or decrease a space block already made. One option is to execute the command in step 8.1 by the desired amount. The other option is to execute the following command:
Code Block | ||
---|---|---|
|
VMBS4600Y31MARAEPMDQ5ADD |
The ADD indicator will order you to increase the space block in 5 more seats. A block can also be reduced. As in point 8.3, the command can be executed by the desired amount or, the command:
Code Block | ||
---|---|---|
|
VMBS4600Y31MARAEPMDQ12DEL
|
Options
The same commands can be added by date period, for the entire flight and certain days of the week. This would avoid adding the indicators day by day.
The input command is:
Code Block | ||
---|---|---|
|
VMBS4104Y31MAR31JULALLALL10MOTUWEFR
|
Temporary Sales Control
This command is used to temporarily control the opening and closing of classes .The commands allow classes to open and close for sale automatically some time before and after the service departure.
Automatic Class Opening for Sales
Code Block | ||
---|---|---|
|
VMSO {flight} {class} {date} {route} {number of hours}
|
Example
VMSO4600Y15MAYAEPTUC48 |
Response:
DONE
In the TSO column you will see a a value of 2D00 (2 days and 0 hours), This is the time set for the class opening before flight departure.
Automatic Class Closure for Sales
Code Block | ||
---|---|---|
|
VMSC {flight} {class} {date} {route} {number of hours}
|
Example:
VMSC4600Y15MAYAEPTUC400 |
Response
DONE
Below the TSC column the days and hours will be shown as Days/Minutes (E.G 16D16 (16 days and 16 hours),This value will represent the timeframe before the flight departure.
Note |
---|
The indicator is expressed in hours. At the moment of closing the class this indicator will disappear and will be recorded in the flight history and C will appear in the STATUS column meaning class closure. |
Remove Closing or Automatic Opening
Code Block | ||
---|---|---|
|
VMSO {flight} {class} {date} {route} 0 |
Example:
VMSO4600Y15MAYAEPTUC0 |
Response
DONE
Code Block | ||
---|---|---|
|
VMSC {flight} {class} {date} {route} 0
|
Example:
VMSC4600Y15MAYAEPTUC0 |
Response
DONE
Note |
---|
Value 0 will eliminate the automatic closing or opening configuration. |
Options
The same commands can be used for all classes, by date period, for the entire flight and certain days of the week. This would avoid adding the indicators day by day.
The input command would be:
Code Block | ||
---|---|---|
|
VMSC4600*31MAR31JULALLALL12MOTUWEFR |
Overbooking Logic Control
This command is used to apply an overbooking logic by cabins.The logic to be applied are those are added in the OVERBOOKING LOGIC table (KSMCL).
Add an overbooking logic
Code Block | ||
---|---|---|
|
VMOS {flight} {cabin} {date} {route} {logic number}
|
Example:
VMOS4600Y26MAYAEPTUC1 |
Response
DONE
Description:
VMOS | Fixed command |
4176 | Flight number |
Y | Cabin |
26MAY | Date |
AEPSLA | Route |
10 | Logic Number |
When the inventory is retrieved, the number of spaces applied for overbooking added by the user will be displayed in the OS column and in the applicable logic number in the LOS one..
Example:
In the example, logic 10 was applied to cabin Y. (See column LOS). According to the logic corresponding to each cabin, the number of additional spaces offered for sale will appear in the OS column
and will be added to the authorized ones (AU) and to the available seats (SA)
Remove overbooking logic
To remove the overbooking logic you must perform the same command by applying 0 (zero) in place of the logic number
Code Block | ||
---|---|---|
|
VMOS4600Y26MAYAEPTUC0
|
Response
DONE
Options
The same commands can be added for all flight cabins, for all segments, by a range of dates , certain or all days of the week. This would avoid adding the indicator one by one the.
The input command would be:
Code Block | ||
---|---|---|
|
VMOS4600 FCY 26MAY10JUNAEPALL1MOWEFR
|
This command will add overbooking logic 1 applicable for Monday, Wednesday and Friday to flight 4600 from 26MAY to 10JUN for FCY cabins between AEP and all destinations.
Remarks field
This command is used to add a free text Remark to a specific segment and it will appear in the availability request and in the inventory.
The input command would be:
Add a comment
Code Block | ||
---|---|---|
|
VMRM {flight} * {date} {route} / {free text}
|
Example:
Code Block | ||
---|---|---|
|
VMRM4176 * 14FEBAEPSLA / DEPARTING TERMINAL 2B
|
Response
DONE
Description:
VMRM | Fixed command | ||
4176 | Flight Number | ||
* | Asterisk | ||
26MAY | Date | ||
AEPSLA | Route | ||
/ | Slash | ||
| Free Text |
When the inventory command is requested again, a message is shown at the end of the inventory with added text.
Example:
Delete a Remark
The command to delete a comment is similar to the previous one but after the slash no text is entered.
Example:
Code Block | ||
---|---|---|
|
VMRM4176*26MAYAEPSLA/
|
Response
DONE
Options
A comment can be added for all segments in one entry or only for those segments from the origin to all destinations or from all origins to the same destination. In this case, the
ALL indicator is used to replace all. It can also be applied to a range of dates and certain days of the week. This avoids adding one to one the indicators.
The input command is:
Example:
Code Block | ||
---|---|---|
|
VMRM 4176*26MAY26MAYALLALLMOTUFR/VERIFY PASSPORTS
|
In this case the remark will be applied to all segments, from 26MAY to 31MAY and on Monday, Tuesday and Friday.
Add an airport terminal
This command is used to add departure and arrivals terminals The terminals added support up to 2 digits and will appear in the availability request.
The input command is :
Add a departure terminal
Code Block | ||
---|---|---|
|
VMTD {flight} * {date} {airport} / {terminal}
|
Example:
VMTD4176*26MAYAEP / 4A |
Response
DONE
Description:
VMTD | Fixed command | ||
4176 | Flight Number | ||
* | Asterisk | ||
26MAY | Date | ||
AEP | Airport | ||
/ | Slash | ||
| Terminal |
The availbility display will display the following information adjacent to the departure airport code.
Add an arrival terminal
Code Block | ||
---|---|---|
|
VMTA {flight} * {date} {airport} / {terminal} |
Example:
Code Block | ||
---|---|---|
|
VMTA4176*23MAYSLA/T2 |
Response
DONE
Description:
VMTA | Fixed command | ||
4176 | Flight Number | ||
* | Asterisk | ||
26MAY | Date | ||
AEP | Airport | ||
/ | Slash | ||
| Terminal |
The availability display will display the following information adjacent to the arrival airport code.
Delete terminals
The command to delete the added terminals is equal to the previous one, modifying the indicator to departure or arrival.
Example for the departure terminal
Code Block |
---|
VMTD4500*23JULAEP/DEL
|
DEL is the deletion indicator and TD the departure terminal.
Example for the arrival terminal
Code Block | ||
---|---|---|
|
VMTA4500*23JULAEP/DEL |
DEL is the deletion indicator and TA the arrival terminal.
Response
DONE
Catering service load
This command is used to load a new catering service to a specific leg. The service indicator can be up to 3 characters .
Input command is :
Add or modify services
Code Block | ||
---|---|---|
|
VMML {flight} * {date} {route} / {service indicator up to 3 characters} |
Example:
Code Block | ||
---|---|---|
|
VMML4360*20DECAEPMDQ/L
|
Response
DONE
Description:
VMML | Fixed command | ||
4360 | Flight Number | ||
* | Asterisk | ||
20DEc | Date | ||
AEPMDQ | Route | ||
/ | Slash | ||
| Meal Service L Lunch |
To see all available catering service options, use the VMML command? If you use an invalid code the system will respond CHECK CATERING
Options
You can add or remove one to three services for all segments at once or only for segments from the origin to all destinations or from all origins to the same destination. In this
case the ALL indicator is used to replace all. It can also be applied to a range of dates and certain days of the week. This would avoid loading every single service day by day.
Input command is :
Example:
VMML4360*20NOV31DECALLALL/DB |
---|
In this case, it will apply to all segments, from 20NOV to 31DEC and Dinner services and Breakfast
Modify Flight schedules
This command allows you to perform schedule changes for a specific date and flight without performing the regular Schedule Change process. It also updates VIE and VLC entries and the availability, display. You must use VLC command * {flight} / {date} in order to visualize the whole flight .
This action does not modify the schedules in the reservations already made, but all reservations made after the schedules modification will be generated with the new schedule. It must be taken into account that the new flight schedule must always be within the departure day of the flight. same.
Regarding Check-In, if the flight was initialized before the manual time change, the PC schedule (Control Panel) will remain as it originally configured,therefore it should also be changed manually.
In case the flight is initialized after modifying the schedule, the Control Panel will have the new schedules.
It is not necessary that all reservations have the same schedule to perform the Check-In process, It will be done normally, but in case a user wishes to have all the reservations with the same schedule
these should be canceled and rebooked for the system to display new schedule.
The entry to manually modify the schedules is:
Code Block | ||
---|---|---|
|
VMTM458*26MAYAEP/1030/1230 |
Description
VMTM | Fixed Command |
458 | Flight Number |
* | Asterisk |
1SEP | Departure Date |
AEP | Departure Airport |
/ | Slash |
1030 | New Departure Time |
/ | Slash |
1230 | New Arrival Time |
System Response:
The command must be re-added by adding / Y at the end to confirm the change. The entry of midnight hours is not accepted as 0000 or 2400, and must be replaced if needed by 2359 or 0001.
If the arrival time is the following day, the entry to be used is the following
Code Block | ||
---|---|---|
|
VMTM458*26MAYAEP/2330/0050+1
|
In case the flight has more than one leg, the entry would be the following:
Code Block | ||
---|---|---|
|
VMTM4200*2SEPAEP/1030/1230/EQS/1330/1400/BRC/1430/1700
|
In case the flight has a day change during a stop, the following entry should be used:
Code Block | ||
---|---|---|
|
VMTM4200*2SEPAEP/2030/2230/EQS/2330/0005+1/BRC/0130/0300
|
These commands will be recorded in the flight history.
Overbooking Inhibition Control
This control allows to inhibit the overbooking of classes despite having the keywords that enable it (OVERSL, CHKOSL). The indicator will be reflected in the flight inventory of the flight under the ST column with the letters Ox.
This function only allows overbooking in the reaccommodation by schedule change or in massive reaccomodation (VMOVE function).
Inhibit the overbooking of a class
Code Block | ||
---|---|---|
|
VMIO {flight} {class} {date} {route} ON
|
Example:
VMIO4320M22MARAEPMDQON |
Response
DONE
Note |
---|
The ON or OPEN or GO indicator can be used |
Remove the inhibition of overbooking of a class
Code Block | ||
---|---|---|
|
VMIO {flight} {class} {date} {route} OFF |
Ejemplo
VMIO4320M22MARAEPMDQON |
Response
DONE
Note |
---|
The ON or OPEN or GO indicator can be used |
Options
You can load the same commands for all flight classes , segments, range of dates and certain days of the week. This avoids adding the indicators one by one.
The input command is:
Code Block | ||
---|---|---|
|
VMIO4320 / 31MAR31JUL ALLALL MONMOTUWEFR
|
Description
VMCL | Fixed Command |
4320 | Flight Number |
/ | Asterisk |
31MAR | Start Date |
31JUL | Stop date |
ALLALL | All segments |
STOP | Indicator |
MOTUWEFR | Days of the week |
Manual passengers transfer
From a flight to another
This procedure allows you to transfer a list of passengers from one flight to another . The process is to eliminate all passengers in one segment and send them confirmed to another .
Duties 5, 7 or 8 are required. If the user only has duty 5 will also be required to have CHKLV2 keyword and will be able to modify flights departing 48 hours before and / or after the current day
The input command is:
Code Block | ||
---|---|---|
|
VMOVE4420/13APRAEPMDQ#4444/13APRAEPMDQ |
Description
VMOVE | Fixed command |
4420 | Flight number from which passengers are migrated |
/ | Slash |
13APR | Flight departure date |
AEPMDQ | Origin/Destination |
# | Hash sign |
4444 | Flight number to which passenger will be migrated |
/ | Slash |
13APR | Flight Departure Date |
AEPMDQ | Origin/Destination |
Once the command is executed, it requires a double validation, therefore the same command must be entered again with /Y and at the end.
Note |
---|
In case of applying on previous days or past flights, year should be added after the month in a two-digit format. Example, 13APR18 |
Only those passengers with confirmed status (HK, TK, KK or KL) will be migrated. Status MM, HL, TL or HM will not be transferred.
Passengers may be transferred on any other flight, regardless of the route and date.
In case there is no match in the classes of the flight where passengers are being transferred, the system will respond with the corresponding error and should be clarified by the command thatI t is explained below which classes will be transferred. Control of Spaces Version 2.0 47
How to transfer no-match classes
When a class does not match or has no equivalent in the new flight it must be indicated which class will match in the new flight when we transfer these PNRs. A hyphen(-) with the class that cannot be transferred followed by the new class which will correspond. Every single booking class will be separated by a -.
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ-HY-NB |
In the example, flight 4420 class H will be transferred to class Y and class N of flight 4420 will be will transferred to class B of flight 4300.
In case of sending all no-match classes to another, the command would be:
Code Block | |
---|---|
|
| |
VMOVE4420 / 22DECAEPMDQ # 4300 / 22DECAEPMDQ- * Y |
In case of sending all classes (match/no-match) to a single one, the command is:
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ-øY
|
How the change is reflected in the PNR
In the active part of the PNR the new flight with status TK will be displayed. In the historical part of the PNR a canceled flight segment(XS) where the passenger was booked and a sold segment(AS)
next to the sign initials and date when the command made.
How the change in flight history is reflected
In the flight history the command made with the sign initials and date will be recorded.
From a flight to two or three flights
As previously described the same procedure can be carried out by sending the passengers of a flight to two or three different flights.
The command is the following:
Code Block | ||
---|---|---|
|
VMOVE4420/13APRAEPMDQ#4444/13APRAEPMDQ#442/22DECAEPMDQ
|
Description
VMOVE | Fixed command |
4420 | Flight number from which passengers are migrated |
/ | Slash |
13APR | Flight departure date |
AEPMDQ | Origin/Destination |
# | Hash sign |
4444 | Flight number to which passenger will be migrated |
/ | Slash |
13APR | Flight Departure Date |
AEPMDQ | Origin/Destination |
# | Hash Sign |
4424 | Flight number to which passenger will be migrated |
/ | Slash |
13APR | Flight Departure Date |
AEPMDQ | Origin/Destination |
Response:
Once the command is executed, it requires a double validation, therefore the same command must be entered again with /Y and at the end.
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPBRC#4300/22DECAEPMDQ#4444/22DECMDQBRC/Y
|
Note |
---|
Consider applying the same entries when a no-match class occurs in the new flight. This has to be done for each of the flights. |
Example
VMOVE4420/22DECAEPBRC#4300/22DECAEPMDQ-HY-NB#4444/22DECMQDBRC-*Y |
In case there are three flights where passengers are transferred, # is added and the data of the third flight, the same way as with the second flight with respect to the first.
Sending to queues
You can send the list of passengers to queues at the time of transfer.
The command is:
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ/Q222
|
All PNRS will be sent to queue 222 of the city where the terminal is located. The other option is to send it to a queue from another city, with which the command is:
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ/QBRC222
|
After this the system displays the data of the passengers to be transferred requesting the validation to confirm. The same command must be executed with / Y at the end.
Partial passengers transfer
This procedure allows the transfer of a partial passengers list from one flight to another. The process is to eliminate all passengers in one segment and send them confirmed to another flight.
Duties 5, 7 or 8 are requiered. If the user only has duty 5 will also be required to have CHKLV2 keyword. You can modify flights departing 48 hours before and / or after the current day.
The procedure must be done in 2 steps.
The first step displays the list of PNRS for later selection:
Code Block | ||
---|---|---|
|
VMOVE4420/22DECAEPBRC
|
Description:
MOVE | Fixed Command |
4420 | Flight number from which passengers are migrated |
/ | Slash |
22DEC | Flight Date |
AEPBRC | Origin/Destination |
Response
Then, the second step, which is the selection of PNRS from the expanded list, must be executed. This list can be re-displayed as many times as necessary with the VMOVE command *
To select the PNRS, the command is
Code Block | ||
---|---|---|
|
VMOVE.1-2,5#4300/22DECAEPMDQ |
Response
A List of actions is displayed asking to reconfirm by adding /Y at the end of the command.
VMOVE.1-2,5#4300/22DECAEPMDQ/Y |
Note |
---|
The system will move all the passengers of a PNR. It is not possible to select a single passenger. Only transfer PNRS with confirmed status (HK, TK, KL, KK) s. |
OVERBOOKING
Overbooking a flight
To overbooking a fully booked flight or class a command can be used for users with duty code 8 and OVERSL keyword.
Command is OB and can be executed in two different ways
1) Direct Sell
Code Block | ||
---|---|---|
|
04300Y24JANAEPMDQOB1 |
The direct sales command is pone by requesting the flight segment in OB status. The system sells it as OB and, when closing the PNR, this status is modified to HK. That change will be recorded in the PNR history in the following format:
2) From a segment on the waiting list:
The PNR to be confirmed is displayed and the following command is performed:
Code Block | ||
---|---|---|
|
(.) (segment number) OB
|
You can also use this entry
Code Block | ||
---|---|---|
|
(.) (segment number) KL
|
In both cases the system will respond:
1. HL/OB => KL
When closing the PNR, the status will become KL. This change will be recorded in the PNR history:
MS XX4500Y 21NOV MO AEPCOR HL/OB/KL1 07:50 09:00
Group PNR Creation (HM to HK)
To confirm a group in requested status HM s, the PNR must be retrieved . The command for Group segment confirmation is KK and it is executed in the following way:
Code Block | ||
---|---|---|
|
(.) (segment number) KK
|
System response
1 .HM => KK |
---|
After ending the transaction and redisplaying the PNR the segment will be in KK status , which is a warning code and must be modified manually to HK status. Once the group creator has been notified it will be recorded in the PNR history.
Note |
---|
This action will automatically place PNR on queue 45 (CONFIRMED GROUPS) of the city code that created the PNR. |
Confirmation of Requested Individual Segments (HM to HK)
The action of requesting a segment with requested status (HM) generates a message to queue 20 (PNRs of the own airline or agencies) or 21 (PNRs of other OA companies)that generated it and the airline that manages the requested segment.
To confirm the segments that are in requested status (HM) the same procedure is used with the groups. PNR must be retrieved and the command to confirm the requested status must be executed.
Code Block | ||
---|---|---|
|
(.) (segment number) KK
|
System response
1 .HM => KK |
---|
After ending the transaction and redisplaying the PNR the segment will be in KK status , which is a warning code and must be modified manually to HK status. Once the group creator has been notified it will be recorded in the PNR history.
Note |
---|
This action will automatically place PNR on queue 45 (CONFIRMED PNRS) of the city code that created the PNR. |
Segments Subject to space availability Confirmation (MM to HK)
To force the confirmation of segments subject to space ie with MM status, there is a command that can be executed by those users that have the keyword OVERSL
Code Block | ||
---|---|---|
|
(.) (segment number) KK
|
PNR status change will be recorded in the history displaying MM / KK
Note |
---|
This action will automatically place PNR on queue 45 (CONFIRMED PNRS) of the city code that created the PNR. |
Segment Status modification from Requested status to waiting list (HM to HL)
You can update a PNR in the required state (HM) to the waiting list without the need to confirm it.
The command is:
Code Block | ||
---|---|---|
|
(.) (segment number) HL
|
The system will change status HM to HL when recording the PNR. If space is available it will be possible to change segment status HL to KL.
Force a Closed Wait List
In case a closed waiting list is found or has reached the pre-established limit it is possible to force it and add a segment.
To perform this transaction, the user must have the WAITLA Keyword in the signature. The command can be made by direct segment or from a short reservation availability
Description
4420Y22JULAEPMDQLA1 | Drect Sell |
04Y1LA | From a previous availability display. |
Duplicate PNRS
Manual handling of duplicate PNRs
Duplicate PNRs that are generated in the system can be visualized by entering a command that sends the dupes messages to queues.
The system considers dupes all thee surnames that are the same day in a same flight segment. These messages will be sent to queue 151 of the administering city of the system.
The command to execute is:
Code Block | ||
---|---|---|
|
DP / DATE / {SEGMENT}
|
DP / DATE / {SEGMENT} |
---|
When retrieving the message from the queue it will look like this:
The flight, class, date, route, reservation code and surname / passenger name are considered duplicate.
The reservation locator has a link that allows you to retrieve the PNR on the screen or display it on the help screen.
Inventory update in other GDS
The following command allows you to update the flight inventory in other GDS (Global Distribution System).
When executing this command the system sends a message to the other GDSs updating the availability of each class marketed on the flight (opening, closing or adjusting sales limits).
Code Block | ||
---|---|---|
|
VAVS {flight} / {date} |
Example: VAVS4500 / 18FEB
V | Fixed space control command |
AVS | Represents the type of message set by IATA to update inventories AVS (Availability Status Message) |
4500 | Flight number to update |
/ | Mandatory Slash |
18FEB | Flight date to be updated |
Note |
---|
|
VCD (View Count Details)
This command allows to get a numerical detail of the number of passengers, by sections and segments of the flight, grouped according to the type of passenger (adult, minors and infants) and the according to the itinerary status (confirmed, subject to space, to be request, on waiting list), as well as informs if there are unaccompanied minors.
The command that must be entered is the following:
Code Block | ||
---|---|---|
|
VCD {flight} / {date} |
Example: VCD4420 / 04MAY
Description:
VCD | Fixed Command (View Count Details) |
301 | Flight number |
/ | Slash |
21MAY | Date to verfy |
Description
FLT | Flight number |
ALL | Origin Airport indicator |
MON | Day of the week (MON: Monday) |
21MAY18 | Date |
34D | Number of days left for departure |
BRD | Boarding airport |
OFF | Off Point/Arrival Airport |
ADT | Adult passenger |
CHD | Child passenger |
INF | Infant passenger |
ABS | Total confirmed passengers occupying a seat |
MM | Number of passengers subject to space per segment |
#MM | Total passengers subject to space |
HM | Number of passengers with status "RQ" or Request status by segment |
#HM | Total number of passengers with status "RQ" or Request status |
WL | Number of passengers on the waiting list by segment |
#WL | Total passengers on the waiting list |
UMNR | Number of unaccompanied minors |
If the date or the airport is not indicated, the system will default to the current date and the user´s terminal location.
VCD from an availability display
To verify VCD entry from a flight availability display, a flight query must be previously displayed on the screen and then enter the following command:
Code Block | ||
---|---|---|
| ||
VCDA1 |
Description
VCD | Fixed command |
A | A Indicator for the flight data and date to take them from the displayed availability |
1 | Number of flight item in the availability display |
VCD from a PNR
To check the VCD entry from a PNR, you must have previously displayed the booking on the screen and then enter the following command:
Code Block | ||
---|---|---|
|
VCDP1
|
Description
VCD | Fixed command |
P | PNR action indicator(Data will be retrieved from pnr) |
1 | Number of flight item in the reservation |
Connection time control (VCT *)
The VCT * command (Verify Minimum Connecting Times) allows to verify if the minimum connecting times between flights are observing the correct time as configured in the minimum connecting time table between airports.
The information provided is for information and it is not recorded in history.
The command can be executed on an segments itinerary in the process of creation or on an already created one.
To enter, you must have one of the following duties: 2 to 8.
No special keyword is required to verify this information, and they can do it both the users of the airlines and those of the travel agencies
Entry
The command to verify minimum connecting times is as follows:
Code Block | ||
---|---|---|
|
VCT* |
When performing this entry the system will display different responses according to the itinerary that is being checked:
Response 1:
When the minimum connection times apply correctly for the entire itinerary or reservation:
Code Block | ||
---|---|---|
| ||
MINIMUM CONNECTING TIME VALID FOR ALL CONNECTIONS |
Response 2:
When there is no itinerary with connections to apply:
Code Block | ||
---|---|---|
| ||
NO CONNECTIONS TO PERFORM MINIMUM CONNECTING TIME
|
Response 3:
When the minimum connection is not being observed.
Code Block | ||
---|---|---|
| ||
INVALID CONNECTING TIME SEGS 2 AND 3 - MINIMUM IS 120 MINUTES VERIFY ANY REMAINING SEGS
|
When the minimum connection times are not observed, as configured by the airline, the system informs which are the segments between which the minimum connection times is not being observed (2 and 3 in example), and informs the minimum time established (120 minutes in the example). If connecting time fails to comply with the minim system stops verifying the remaining segments of the itinerary.
You can check if the minimum connection times are correct by indicating the segments of the itinerary:
Code Block | ||
---|---|---|
|
VCT*1,3 |
This entry informs if the minimum connection time between segments 1 and 3 is correct
Code Block | ||
---|---|---|
| ||
VCT*2-4 |
This entry informs if the minimum connection time between segments 2 to 4 is correct.
Warning |
---|
The VCT * command applies only between segments with confirmed status (HK, KL, TK, KK, RR). For the system to verify if the minimum connection time is correct, the time between arrival and departure must be less than zero minutes. |
Flights with closed classes list
Definition
This list will display the information of all flights that are closed because all their booking classes are with CLOSED status. Only those flights whose classes are closed in full in all their legs will be included.
Classes can be closed both for flight loading (KSCL) and inventory (VMCL)
The base command is VLCF:
V Inventory command
L List indicator (list)
C Closed indicator
F Flight indicator (flights)
The system will display the information all the flights with all their booking classes closed, 8 per line, and as many flights as flights with all their closed classes exist. Each flight will be composed of 4 digits, in the case that a flight has a single digit, it will be completed with zeros. Example: flight number 6 will be shown as 0006
Display options
Current Date
Code Block | ||
---|---|---|
|
VLCF* |
Example:
Code Block | ||
---|---|---|
| ||
VLCF* |
CLOSED FLIGHTS TTL= 1
2504
System response will include all flights that have all booking classes completely closed. The asterisk indicates the currrent date of the display.
Specified date
Code Block | ||
---|---|---|
| ||
VLCF/date |
Example:
VLCF/22NOV
CLOSED FLIGHTS TTL= 1
2504
The response will include all flights that have all their booking classes closed for a particular date and for all their legs.
Keep in mind that if you need to verify a date in following year it has to be specified.
Example:
Code Block | ||
---|---|---|
| ||
VLCF/08JAN18 |
By origin-destination
Code Block | ||
---|---|---|
| ||
VLCF*origin destination
|
Example:
Code Block | ||
---|---|---|
| ||
VLCF*MVDAEP |
CLOSED FLIGHTS TTL= 2
0504 0049
By not specifying a date, the system will display the flights that have all their booking classes closed, for the route MVD-AEP for the day of the date (today)
By origin-destination with a specified date
Code Block | ||
---|---|---|
|
VLCF*origin destination/ date |
Example:
VLCF*MVDAEP/24DEC
CLOSED FLIGHTS TTL= 1
0049
Keep in mind that if you need to verify a date in following year it has to be specified.
Example:
Code Block | ||
---|---|---|
| ||
VLCF*MVDAEP/08JAN18 |
From a specified origin to all destinations
Code Block | ||
---|---|---|
|
VLCF*origin ALL
|
Example:
Code Block | ||
---|---|---|
| ||
VLCF*UIOALL
|
CLOSED FLIGHTS TTL= 1
2504
By not specifying a date, the system will display the flights that have all their booking classes closed for the current display date.
From a specific origin to all destinations on a specific date
Code Block | ||
---|---|---|
|
VLCF*origin ALL/ date |
Example:
Code Block | ||
---|---|---|
| ||
VLCF*UIOALL/08JAN18
|
CLOSED FLIGHTS TTL= 1
2504
From any origin to a specific destination
Code Block | ||
---|---|---|
|
VLCF*ALL destination
|
Example:
Code Block | ||
---|---|---|
| ||
VLCF*ALLMVD |
CLOSED FLIGHTS TTL= 1
0030
By not specifying a date, the system will display the flights that have all their booking classes closed for the current date
From any origin to a specific destination on a given date
Code Block | ||
---|---|---|
|
VLCF*ALL destination/date
|
Example:
Code Block | ||
---|---|---|
| ||
VLCF*ALLMVD/25DEC
|
CLOSED FLIGHTS TTL= 3
0070 0030 0022
Keep in mind that if you need to verify a date in following year it has to be specified.
Example:
Code Block | ||
---|---|---|
| ||
VLCF*ALLGYE/08JAN18 |
CLOSED FLIGHTS TTL= 1
2504
Export CSV file
All the lists can be exported to a CSV file (file separated by commas), adding the extension -CSV at the end of the entry
Sending a list to an email address
All lists can be sent to a mail address adding a hyphen at the end followed by the required email address
Example:
VLCF*-PASSENGER@GMAIL.COM
OK