This module covers all the different steps on how to accept passengers on a flight followed by the boarding process
Searching for passengers with connections
When searching for a passenger (PF) the outbound flight information will be displayed if passenger has any.
Only connections scheduled to depart in the next 24 hrs will be displayed. Connecting flights can be confirmed or wait listed but following flight reservation status will not be included: UC, UN, DL, NS.
.I/ Meaning INBOUND connection, i.e. flights arriving within 24 hours before the departure of actual flight.
.O/ Meaning OUTBOUND connection, that is, flights departing in the next 24 hours after the departure of actual flight.
Example:
While accepting passengers on flight XX3136/27AUG from AEP to COR
the columns ITEM, CODE, NAME, FOID, OFF, ST, CC y FF contains the same information as previously described.
The additional information for connecting flights is described below:
.I/ | Indicates there is an INBOUND connection |
HK | Connecting flight segment status |
XX4431Y | Connecting flight number and class of service |
27AUG SA | Connecting flight departure date and day of the week |
MDQAEP | Connecting flight board and off point |
1000 1055 | Connecting flight departure and arrival time |
.O/ | Indicator for OUTBOUND connecting flight |
HK | Connecting flight segment status |
XX0023Y | Connecting flight number and class of service |
27AUG SA | Connecting flight departure date and day of the week |
CORAEP | Connecting flight board and off point |
2350 0050+1 | Connecting flight departure and arrival time |
Details
Bold: Flight being checked-in
Blue: Inbound Flight
Red: Outbound Flight
.I/HK XX4431Y 27AUG SA MDQAEP 1000 1055 .O/HK XX023 Y 27AUG SA CORAEP 2350 0050+1
1 XX4431Y 27AUG SA MDQAEP HK1 1000 1055
2 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
3 XX023 Y 27AUG SA CORAEP HK1 2350 0050+1
.I/HK XX4361Y 27AUG SA MDQAEP 1530 1615
1 XX4361Y 27AUG SA MDQAEP HK1 1530 1615
2 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
<No information – PNR includes a single flight segment>
1 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
.O/HK XX023 Y 27AUG SA CORAEP 2350 0050+1
1 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
2 XX023 Y 27AUG SA CORAEP HK1 2350 0050+1
.O/HK XX023 Y 27AUG SA CORMDQ 2350 0230+1 .O/HK XX4431Y 28AUG SU MDQAEP 1000 1055
1 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
2 XX023 Y 27AUG SA CORMDQ HK1 2350 0230+1
3 XX4431Y 28AUG SU MDQAEP HK1 1000 1055
<no information – following flight departs after 24 hs>
1 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
2 XX023 Y 30AUG TU CORAEP HK1 2350 0050+1
.I/HK XX4431Y 27AUG SA BRCMDQ 0800 0930 .I/HK XX4361Y 27AUG SA MDQAEP 1530 1615
1 XX4431Y 27AUG SA BRCMDQ HK1 0800 0930
2 XX4361Y 27AUG SA MDQAEP HK1 1530 1615
3 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
.O/HK XX023 Y 27AUG SA CORMDQ 2350 0230+1
1 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
2 XX023 Y 27AUG SA CORMDQ HK1 2350 0230+1
.I/HK XX116 Y 27AUG SA MVDAEP 0800 0900
1 XX116 Y 27AUG SA MVDAEP HK1 0800 0900
2 XX3136Y 27AUG SA AEPCOR HK1 1820 1950
PF* - Passenger search by last name in all open flights for the day. Acceptance on the flight.
KIU DCS provides the facility to search for a passenger in all open flights for the actual date by only knowing the last name and boarding airport. The command to use is as follows:
PF*<Passenger last name or surname> |
The input above allows the searching for a passenger using his/her last name initial letter or the full last name. The accuracy will increase by adding more last name letters to the search.
Passenger acceptance for check-in can be done once the passenger is located. The only requirement is to transmit the following command before the corresponding PU entry:
PF<Item> |
See example below:
Two passengers traveling together with same last name:
When there are two or more passengers booked together with different last name but on same PNR, the command PF*<Last Name> of one of them will display all passengers on same PNR so they can be accepted at check-in as they are traveling together (e.g. below)
Three passengers with different last name but on same PNR:
KIU DCS also allows the searching for passengers with different last names, no matter if they are on the same PNR or not. The input is as follows:
PF*<First passenger last name>#<Sencond passenger last name> |
Searching for a passenger in all open flights for the current date and boarding from a different airport is also available using the following input:
PF*<Boarding airport>-<Passenger last name> |
Searching for more than one passenger departing from a different airport and with different last names:
PF*<Boarding airport>-<Passenger last name>#<Second passenger last name> |
APIs available at airline request.
Accepting Passengers
After searching for a passenger in order to accept him/her, the number (ITEM) he/she has on the list should be selected.
Accepting passengers with seats
Use this entry to display the seat map (graphical pop up):
PS{flight}/{date}{Board Point}{Off Point}
This entry allows to display a seat map with the current occupation updated
In addition the seat map can be displayed on native mode by using the following entry:
PV{flight}/{date}{Board Point}{Off Point}
The seat map will be displayed as below
C Y [ [ [ [ [ [ [ [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 F A A A A A I R A/ A A A A A A A B A E A A A R A/ A A A A A A A B A D A A A A A A R A/ A A A A A A A B A » = = C A A A A A A A A A A A/ R A/ A A A A A A A B A B A A A • • A A A/ R A/ A A A A A A A B A A A A A A A I • • A A A/ R A/ A A A A A A A B A
In order to display the reference for each seat code shown on the seat map, add a * sign at the end of the entry.
Example:
PV3416/07FEBAEP*
This entry displays the seat map and also the references for each code as following:
SEAT REFERENCES: • OCCUPPIED I AVAILABLE WITH INFANTS A AVAILABLE B BLOCKED R RESERVED / RECLINE RESTRICTED » CORRIDOR = EMERGENCY EXIT [ WINGS
Assign seats using the entry PU and PE, follow the steps as for accepting passengers without seats (free-seating)
Example:
PU1+2,ST2AB | Assign seats 2A y 2B |
PU1+2,ST2A3B | Assign seats 2A y 3B |
PU1+2,ST2A | If passenger 2 is a lap infant, seat 2A must accept infants otherwise select a seat with the infant indicator |
PU1+2,ST2A | full entry to accept passengers |
PE-1,ST | Edit a seat, system displays the graphic assistant |
PE-1,ST3A | Edits a seat, if seat is free, passenger is accommodated on the new seat, if seat is occupied system opens graphic assistant |
Example:
Search for a passenger
PF4176-M
CHECKIN-M> XX4176 /17MAR AEP ITEM CODE NAME FOID OFF ST CC FF 1 AHWHOS MORES/CARLA DNI 4343233 SLA HK YY #002 TQBSRC MORENO/PAULA DNI 454545 SLA
System displays a similar name list, then use the passenger upload entry (PU)
PU1
If flight initialized including the mandatory seat assignment option on, system displays the graphic seat map automatically:
Once the seat map is displayed click on the seat to select or type the seat number on the "Seat" box (If typing the seat, seat number must be all CAPITAL LETTERS, i.e. 1C not 1c)
In addition, this screen permits to add baggage pieces and weight and tag numbers.
Once all the passenger details were added clic OK
This screen displays the flight details, and the seat references according to it status.
Accepting passengers on available seats (direct entry)
If executing the passenger on load entry and specifying a seat number, passenger is accommodated without displaying the passenger seat map.
PU1-3,ST4ABC
Response:
CHECKIN-> XX4176 /17MAR AEP ORD CODE NAME FOID OFF CC SEAT BAG 003. NSTZDV GOMEZ/SANDRA DNI 44444 SLA YY 4A 0/000 004. NSTZDV GOMEZ/MARIA DNI 54445 SLA YY 4B 0/000 005. NSTZDV GOMEZ/JOSE DNI 45233 SLA YY 4C 0/000
Error when selecting seats occupied or unavailable
If when executing the passenger on load entry seats are not available, system responds and error and re displays the graphic seat map
Example:
PF4176-R
CHECKIN-M> XX4176 /17MAR AEP ITEM CODE NAME FOID OFF ST CC FF 1 VNKZWS ROMERO/LUIS DNI 44343 SLA HK YY 2 ¤ TORRES/LUCIA DNI 434324 SLA HK YY 3 ¤ FERNANDEZ/MARIA DNI 6577 SLA HK YY
PU1-3,ST4ABC
Select available seats and complete baggage details, and other elements.
This graphic display includes a frequent flyer field and for other indicators as ignore control for tickets (Field Other elements)
After selecting seats, click OK, system will proceed to check the passenger in.
Accepting passengers on available seats (Direct acceptance)
Add a seat number to the passenger upload entry, if seat is available passenger is accommodated without displaying the seat map.
PU1-3,ST4ABC
Response:
CHECKIN-> XX4176 /17MAR AEP ORD CODE NAME FOID OFF CC SEAT BAG 003. NSTZDV GOMEZ/SANDRA DNI 44444 SLA YY 4A 0/000 004. NSTZDV GOMEZ/MARIA DNI 54445 SLA YY 4B 0/000 005. NSTZDV GOMEZ/JOSE DNI 45233 SLA YY 4C 0/000
Error when adding occupied or blocked seats to the passenger upload entry (PU)
When executing the passenger upload entry and the selected seats are unavailable system will respond displaying the seat map showing the seats that are available.
Example:
PF4176-R
CHECKIN-M> XX4176 /17MAR AEP ITEM CODE NAME FOID OFF ST CC FF 1 VNKZWS ROMERO/LUIS DNI 44343 SLA HK YY 2 ¤ TORRES/LUCIA DNI 434324 SLA HK YY 3 ¤ FERNANDEZ/MARIA DNI 6577 SLA HK YY
PU1-3,ST4ABC
Click on the selected seats, or type the seat number, add the baggage information and tag number (if applicable)
This screen also permits to add a frequent flyer number and on the field Other Elements add messages, or ignore the flight number and date control.
After selecting the seat and completing the baggage details click OK. System will proceed to accommodate the passenger.
For carriers checking through SITA or ULTRA applications do not enter a number as system will add it automatically.
Accepting with nationality
According to what is specified in a new indicator in the Control Panel of the flights (called NAT) will indicate the obligation to add the nationality of the passengers at the time of checkin.
This new methodology for requiring the entry of the Nationality at the time of checkin is configurable by flight and a new token was created in the checkin configuration table (JJCHK) that by default will initialize the flights for checkin with the new indicator activated/deactivated in Control Panel
At the time of checkin, if this indicator is set to Y, it will require that the nationality must be entered in the PU / PE command.
Activation of the NAT indicator:
The activation (in the checkin configuration table, that is, in the JJCHK table) so that it takes by default the requirement to enter the nationality at the time of checkin is configurable by the client and must be requested from Support.
Entry of nationality at the time of checkin
Entry alternatives - Entry from direct entry
Allows the checkin of multiple passengers:
PU<PASSENGER NUMBER>,NANNN |
|---|
Description:
PASSENGER NUMBER | Can be individual pax or by range |
NA | Nationality indicator |
NNN | Country Code |
Example:
PU1,NAARG
Options
Option 1
Assign the same nationality to all passengers in the specified range
PU<PASSENGER NUMBER 1-PASSENGER NUMBER 2+PASSENGER NUMBER N>,NANNN |
|---|
Example:
PU1-4+7+9,NAARG
Assigns the same nationality specified as ARG to all passengers to check (from 1 to 4, passenger 7 and passenger 9)
Option 2
Assign different nationalities to all specified passengers (the option to specify different nationalities for a range of passengers is not allowed)
PU<PASSENGER NUMBER 1+PASSENGER NUMBER 2+PASSENGER NUMBER 3+PASSENGER NUMBER 4>,NANNN.XXX.YYY.ZZZ |
|---|
Example:
PU1+4+7+9,NAARG.COL.FRA.USA
It assigns ARG to passenger 1, COL to passenger 4, FRA to passenger 7, and USA to passenger 9.
Entrance from the command with seat assignment through the automatic display of the on-screen seat map
You can allow multiple passengers to check in:
After input:
PU<PASSENGER NUMBER>,NANNN |
|---|
Once the map is displayed, in the "Other elements" it appears ", NANNN"
List of checked passengers (PLC)
A new column is added in the display of checked passengers with the Nationality entered in the reservation (in the SSR DOCS), in the API mask or the one entered at the time of checkin.
Example:
PLC5050/27JUNEZ
Response:
** PASSENGERS CHECKED **
FLT: 5050 BRD: EZE THU 27JUN19
STATUS CHECK IN: CLOSE ** POST DEPARTURE ** KIU AUTO-PROCESS **
BOARDING: CLOSE
ORD NAME SEAT BK OFF CODE BOARD NATIONALITY FOID FREQUENT FLYER TICKET MANUAL E-TICKET NUMBER H.BAG BAGGAGE AGENT ID
2. MEC/DISCO 10A Y MIA XGKQGY 0Z Y AR PP66666 9990210009719/1 0/0 KIUHELPMC
#BT:
#DHS: OK TO BOARD
DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
3. ALVAREZ/ENRIQUE 15A Y MIA IILATR 0Z Y ESP PP22222 9990210009738/1 0/0 KIUHELPMC
#BT:
#DHS: OK TO BOARD
DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
4. GONZALEZ/PEDRO 15B Y MIA RJPHLD 0Z Y ESP PP9999 9990210009736/1 0/0 KIUHELPMC
#BT:
#DHS: OK TO BOARD
DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
5. RODRIGUEZ/NESTOR 15C Y MIA RJPHLD 0Z Y ESP PP55555 9990210009737/1 0/0 KIUHELPMC
#BT:
#DHS: OK TO BOARD
DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
The column with the Nationality is also added in the excel spreadsheet that is generated in the option of sending to an EXCEL spreadsheet (PLCxx-EXCEL)
Activation/deactivation indicator by flight in the Control Panel
A new indicator was created in the Control Panel (called NAT) which determines if the entry of the Nationality is mandatory at the time of checkin.
Activate the indicator
PC<FLIGHT NUMBER>/<DATE><ORIGIN>,NATY |
|---|
Examplw:
PC5050/27JUNEZE,NATY
Deactivate the indicator
PC<FLIGHT NUMBER>/<DATE><ORIGIN>,NATN |
|---|
Example:
PC5050/27JUNEZE,NATN
Indicator appears when PC is deployed if enabled, not displayed when disabled
Accepting passengers adding a comment
Add a comment after the passenger upload entry:
PU1,MS FREE TEXT
Descripción:
PU | Passenger upload command |
1 | Item number |
, | Comma separator |
MS | Message/Comment indicator |
TEXTO LIBRE | Free text up to 25 characters |
Passengers list holding a boarding pass that contains a message
MB indicator can be used to filter accepted passengers holding boarding passes that contain a message from a flight list.
PLC<flight>/<date><origin>/MB |
|---|
In the search result the system will return a list of those passengers accepted on the flight holding boarding passes that contain a message under the indicator #MB
The filter / MB can be combined with other filters and extensions of the PLC list
Example:
PLC4444/30DEC/MB ** PASSENGERS CHECKED ** FLT: XX4444 BRD: AEP SAT 30DEC17 FILTER: ONLY PAXS WITH BOARDING REMARKS STATUS CHECK IN: OPEN BOARDING: OPEN PAXS: 22 ORD NAME SEAT BK OFF CODE BOARD 002. ABASOLO/KARIN 6D Y MDQ DEVUQS #MB: PRIORITY BOARD 003. ATERRIZA/PAX 6E Y MDQ DEVUQS #MB:PRIORITY BOARD 005. GAMBOA/DIONISIA 7F Y MDQ DEVUQS #MB:PRIORITY BOARD 006. STIPO/ALVARO 7E Y MDQ DEVUQS #MB:PRIORITY BOARD 007. JVIAJEROUNO/JVIAJERO 7D Y MDQ DEVUQS #MB:PRIORITY BOARD 008. JUREZ/MARIELA MRS 8D Y MDQ DEVUQS #MB:PRIORITY BOARD
CS - Check-in Stop Message
The purpose of CS or check-in stop message is to add a message to passenger record in order to take a specific action involving the passenger at the check-in counter. This CS message can be added before accepting the passenger on a flight or afterwards. The following command is for adding a CS message to the PNR before passenger acceptance on a flight:
4CKIN/STOP/<Free text>/P<Item> |
On PNR, it is like any SSR CKIN message except for the word “STOP” as shown on screenshot below:
Once a passenger with a CS message is accepted on a flight using the PU command, the system displays the following confirmation message: “AT LEAST ONE PASSENGER HAS CHECK-IN STOP MESSAGE. RE-ENTER THE COMMAND WITH /Y TO CHECK-IN THE FOLLOWING PASSENGERS” and displays passenger or passengers involved with their corresponding CS message.
CS or check-in stop message is disabled as soon as a passenger is checked-in on a flight. The same CS message or new one can be added using following command:
PE-<Item>,CS<Free Text> |
To delete a CS message:
PE-<Item>,CSDEL |
And then, confirming deletion by retransmitting the same entry with /Y at the end. See example below:
Only one CS message is allowed per passenger.
The CS message can be updated or modified with following command:
PE-<Item>,CS<Free text> |
As there is a previous CS message on passenger record, the system displays the following message: “AT LEAST ONE PASSENGER HAS A CHECK-IN STOP MESSAGE. RE-ENTER THE COMMAND WITH /Y TO ACCEPT PASSENGER ON THE FLIGHT” and it also displays passenger´s name together with the previous CS message preceded by *CS (example on below screenshot). The PE command with the /Y at the end is also displayed in order to confirm the update or modification of the CS message as it will replace the old CS message as soon as we retransmit the command.
The system will require confirmation for an added CS using the entry with /Y when updating passenger records. Example, re-printing a boarding pass.
Then, the CS message is disabled and it disappears again for check-in but it can be added again when needed.
Different passenger lists are available to display passenger records with a CS or check-in stop message, depending on passenger acceptance. For displaying the list of passengers with a CS message before flight acceptance, the input is as follows:
PLU<Flight>/<Date><Airport>/CS |
Passengers with a CS message can be easily identified on the “non checked-in passengers list or PLU because there is a new -CS- indicator showing a -Y- when a passenger has a CS message on his/her record. The difference with the above list is that the PLU/CS shows only “non-checked-in passengers” with a CS message while the below list shows all “non-checked-in passengers”, no matter if they have a CS or not.
New -CS- indicator will also be on following inputs:
PF*<Last Name Initial or Full Last Name> |
PF<Flight>/<Date><Origin Airport><Destination airport>-<Last name> |
The following entry will display the list of passengers with a CS message added at the check-in counter using the PE-<Item> input.
PLC<Flight>/<Date><Airport>/CS |
Observing above screenshot , three already checked-in passengers have a CS message on their records as -Y- is shown under the -CS- indicator and #check-in stop appears below each passenger name.
Finally, this new CS feature is also available at flight history, PH. Providing updated information for each of the passenger records with a CS or check-in stop message.
CS or check-in stop is not applicable to connectings flights.
GS - Gate Stop
The GS or Gate Stop feature should be used to add a message to passenger record so the boarding agent can take the corresponding action when attempting to board the passenger. Message examples could be if a passenger needs to make a payment before boarding because he checked on the website, verifying passenger documentation or a new seat assignment.
PU<Item>,GS<Free text> |
The GS option for Gate Stop should be added either with the PU entry at check-in acceptance or, once the passenger has been checked-in on a flight, with the PE command:
PE-<Item>,GS<Free text> |
PE example:
If there is a GS message already in passenger record and a new GS is attempted, the system will require confirmation for the action by resending the command with /Y as the new GS will override the old one. The notification message shown is “ THERE IS A GATE STOP ALREADY ASSOCIATED WITH THE PAX. ADD /Y TO REPLACE THE PREVIOUS MESSAGE WITH NEW DATA”.
Retransmitting the new GS command with /Y at the end, will replace the old GS as only one GS is allowed per passenger.
To delete a GS from a passenger record, the input is as follows:
PE-<Item>,GSDEL |
To display the list of all passengers on a flight with GS in their records, the command is as shown below:
PLC<Flight>/<Date><Origin airport/GS |
At the boarding gate and when the agent attempts to board the passenger who has a GS on his/her record, the boarding is not accepted and the system displays the GS message with /Y at the end. Once the agent reenters the PB<BN>/Y command , the system will board the passenger as shown below.:
As soon as flight is assigned to the gate, the list of passengers with GS is available at the boarding gate using the following input:
PBP/GS |
This feature is only available for Duty 5.
APIS available at airline request.
Accepting passengers ignoring the control for flight and date
This functionality permits to ignore the control for flight and date when accepting passengers.
By ignoring the control for flight number and departure date, passengers booked for other flight or date can be accepted without exchanging the ticket or re validating a flight segment.
This function is available for tickets issued in KIU as for tickets issued in another ticket server
Add the following code to the passenger upload entry:
PU1,IC
Description:
PU | Passenger upload command |
1 | Passenger item number |
, | Comma separator (mandatory) |
IC | IC: Ignore Control |
In order to make this entry agent need to have Duty 5 on its agent sign
IC can be combined with others indicators following the PU entry
La opción IC podrá combinarse con los otros indicadores posibles de ingresar al momento de realizar el check-in.
Examples:
PU1,ST8A,IC
PU1,ST8A,1/10,BT12345,IC
PU1,ST,MS**PAX VIP**,IC
If IC is not added to the Passenger upload entry (PU) IC en el Comma separator ndo, it can also be added to the OTHERS ELEMENTS field on the graphic seat map as shown below:
When accepting a passenger and flight segment on the reservation is different from the one issued on the e-ticket, and IC is not indicated, check-in will fail and respond: *** CHECK E-TICKET ITEM / 1 ***
History
System will keep a record of IC on:
Flight History
e-ticket history
Display of e-tickets issued on other systems
Flight
On flight History (PH) entry with IC will display as following:
PU #001 GOMEZ/MARIA DNI 43423432 CC:YY SEAT:3B BAG:0/0 BT: *IC* 9992200022041C1
AEPXX-JF 1408 15MAR10
*IC* shows before the e-ticket number and means flight and/or date control were ignored
e-ticket
e-ticket history will display the transaction as following:
TKTT HISTORY DISPLAY ** 9992200022041 6
CPN FRM/TO FLT CL DATE ST DEVICE SIGN TIME/DATE OBSERVATION
/.41 1 AEPSLA XX4176 Y 15MAR C AEP00XX457 KIUHELPJF 1408 15MAR10 » KIU® CHECK-IN *IC*
XX4112 Y 15MAR O AEP00XX457 KIUHELPJF 1339 15MAR10
*IC* will be displayed under the column OBSERVATION shows before the e-ticket number and means flight and/or date control were ignored at passenger acceptance.
Under FLT displays the original flight segment that the e-ticket was issued for, and the flight segment for which the passenger was accepted.
On the example e-ticket was issued for flight 4112 for 15MAR, but passenger was accepted on flight 4176 on 15MAR.
Once flight is closed (PD) System will update the flight segment to FLOWN and will add a line to the history as shown below:
TKTT HISTORY DISPLAY ** 9992200022041 6
CPN FRM/TO FLT CL DATE ST DEVICE SIGN TIME/DATE OBSERVATION
/.41 1 AEPSLA XX4176 Y 15MAR F AEP00XX457 KIUHELPJF 1433 15MAR10 » KIU® CHECK-IN
XX4176 Y 15MAR C AEP00XX457 KIUHELPJF 1408 15MAR10 » KIU® CHECK-IN *IC*
XX4112 Y 15MAR O AEP00XX457 KIUHELPJF 1339 15MAR10
Electronic Ticket (other systems)
On the e-ticket display issued on another system flight coupon will show as following:
Open for use
-- OTHER SYSTEM TICKET * TNMOEV --
15MAR10/SYS-TTYB - TORRES/SABRINA
CPN FLT RBD DATE SEGMENT
1- XX4112 Y 16MAR AEPSLA
Checked-in/Accepted
-- OTHER SYSTEM TICKET * TNMOEV --
15MAR10/SYS-TTYB - TORRES/SABRINA
CPN FLT RBD DATE SEGMENT
1- XX4112 Y 16MAR AEPSLA-C
The Indicator–C at the end of each flight coupon means passenger was already CHECKED-IN.
Flown
-- OTHER SYSTEM TICKET * TNMOEV --
15MAR10/SYS-TTYB - TORRES/SABRINA
CPN FLT RBD DATE SEGMENT
1- XX4112 Y 16MAR AEPSLA-F
Indicator –F at the end of the coupon segment means FLOWN.
Once passenger is accepted on a flight, flight coupon cannot be used on another flight even if trying to document it with ,IC.
System will always respond *** CHECK E-TICKET ITEM / … ***
Accepting passengers with connecting flights
System permits to accept passengers with connecting flights on the same airline up to the final destination. System will print all the necessary boarding pass and bag tags (when applicable). This function is available to carriers logging to KIU from third party workstations (SITA, ULTRA)
Display of connecting flight information:
Once the passenger search displays the similar name list, If included on the same PNR, system will display the connecting flight information as following:
The connecting flight information display after the outbound flight details. System displays only the flight included on the same record locator. Consider system assumes returning flights for the same date as connections.
For those itineraries including up to two connections the system response to the PF entry will display the connecting flight data, if more than two connections exist, system will add the indicator ./O+ as shown below.
RP/AEP00XX4 - LINEAS AEREAS XX
1.1VERA/OLGA »PP 34130211
1 XX4320Y 28MAY TU AEPMDQ HK1 1100 1145
2 XX4301Y 28MAY TU MDQAEP HK1 1230 1315
3 XX720 Y 28MAY TU AEPMDQ HK1 1800 1850
4 XX4420Y 28MAY TU MDQBRC HK1 1915 2100
PF4320/28MAY-RIN
CHECKIN-M> XX4320 /28MAY AEP
ITEM CODE NAME FOID OFF ST CC FF
1 JNAXDW VERA/OLGA PP0341302 MDQ HK YY .O/HK XX4301Y 28MAY TU MDQAEP 1230 1315 .O/HK XX720 Y 28MAY TU AEPMDQ 1800 1855 .O/+
If itinerary includes an inbound connection, system adds the indicator .I/. If more than two connections exist it also adds the indicator .O/+
Considerations:
In order to accept passengers, all flights on the itinerary must be initialized and the Control Panel updated.
The sequence number will be assigned on each flight independently
A passenger can be accepted with a maximum of three connections, otherwise system displays the following error:
ERROR - MAXIMUM PERMITTED 3 CONNECTING FLIGHTS
System responds with this error message when trying to accept passengers on “Other Airline” flights without interline agreement
INVALID - NO AGREEMENT BETWEEN CARRIERS
Accepting passengers on connecting flights is not available for upgrade or downgrade
Accepting passengers with connecting flights:
In order to accept passengers on connecting flights add the indicator ,O to the Passenger upload entry (PU):
PU<nro. de ítem>,O
Example: PU1,O
Use this entry to accept the passenger on all the connecting flights included on his itinerary
Este formato acepta los calificadores ya conocidos como:
This format accepts the following known combinations:
Accept passenger with comments: PU1-3,O,MSTEXTO
Accept passenger with exact weight: PU1,O,WT90
Accept passenger on a Jump Seat: PU1,O,JMP
Accept passengers with baggage: PU1-2,O,2/15,BT123456/988777
Accept passengers adding baggage individually just in case a piece of baggage needs to be removed lately : PU1,O,1/10+1/15+1/20,ST3A
In order to accept a passenger with more than one connecting flight add the amount of connections
PU<item number>,O<total connecting flights>
Example: PU1,O2
On this example this passenger is accepted on the current flight and two onward connections. Consider the maximum connection accepted is 3, hence, the maximum value for this entry is ,O3
Considerations for seat assignment
The seat number assigned to the first flight is also assigned to the connecting flight. If the same seat number is not available, use the PV entry (native map) for each flight if available to verify the available seats and use the following entry to assign a different seat individually.
Example: PU1,O,ST2C+3C
Separate the seat number for each flight by using a + sign when accommodating multiple passengers on the same transaction assigning them different seats for each flight.
Example:
PU1-2,O,ST6C10C+3C3A
PU1+2+3+4F,O,2/30,BT123456/57,ST3B3C4B4C+8B8C9B9C
Editing passengers on connecting flights
Passenger edit entries must include the indicator ,O in order to apply to the onward connecting flights
Example:
PE262/24OCTCCSAUA-4,ST1A,O
PU1,O,ST<seat flight one>+<seat flight two>
PE303/24OCTAUABON-3,P,O
History display for connecting flights:
Passengers upload entry adds the indicator ,O on the flight history, meaning that passenger was accepted on the current and connecting flights
PU #001 CALIZAYA/ARIANA PP 95188368 CC:YY SEAT:1A BAG:0/0 BT: 9992200038946C1 ,O
AEPXX-GL 1206 21MAY13
PU #002 CALIZAYA/ARIANA PP 95188368 CC:YW SEAT:3D BAG:0/0 BT: 9992200038947C1 ,O2
AEPXX-GL 1216 21MAY13
Example:
PU1-3,O,WT90,MSPAX IN CONNECTION
CHECKIN->XX4421/08MAR BRC
ORD CODE NAME FOID OFF CC SEAT BAG
006. ZVPGDD GUEVARA/CARMEN PP 88719734 AEP YY 4B 3/030 (235689/90/91) WT:90
#PAX IN CONNECTION
007. ZVPGDD URIBE/OLGA JOHANNA PP 07352705 AEP YY 4C 0/000 WT:90
#PAX IN CONNECTION
008. ZVPGDD SALAZAR/LUISA PP 25985676 AEP YY 4A 0/000 WT:90
#PAX IN CONNECTION
CHECKIN->XX4370/08MAR AEP
ORD CODE NAME FOID OFF CC SEAT BAG
003. ZVPGDD GUEVARA/CARMEN PP 88719734 MVD YY 4B 3/030 (235689/90/91) WT:90
#PAX IN CONNECTION
004. ZVPGDD URIBE/OLGA JOHANNA PP 07352705 MVD YY 4C 0/000 WT:90
#PAX IN CONNECTION
005. ZVPGDD SALAZAR/LUISA PP 25985676 MVD YY 4A 0/000 WT:90
#PAX IN CONNECTION
PU1,O,ST5A+3B,WT90,MSPAX IN CONNECTION
CHECKIN->XX4421/08MAR BRC
ORD CODE NAME FOID OFF CC SEAT BAG
009. DDKDRJ ORTEGA/MARCO ANTONIO PP 04079226 AEP YY 5A 0/000 WT:90
#PAX IN CONNECTION
CHECKIN->XX4370/08MAR AEP
ORD CODE NAME FOID OFF CC SEAT BAG
006. DDKDRJ ORTEGA/MARCO ANTONIO PP 04079226 MVD YY 3B 0/000 WT:90
#PAX IN CONNECTION
PU3,O,ST9C+9A,WT90,MSPAX IN CONNECTION,1/29,BT258741
CHECKIN->XX4421/08MAR BRC
ORD CODE NAME FOID OFF CC SEAT BAG
010. DDKDRJ HUACHACA FLORES/FELI PP 41345169 AEP YY 9C 1/029 (258741) WT:90
#PAX IN CONNECTION
CHECKIN->XX4370/08MAR AEP
ORD CODE NAME FOID OFF CC SEAT BAG
007. DDKDRJ HUACHACA FLORES/FELI PP 41345169 MVD YY 9A 1/029 (258741) WT:90
#PAX EN CONEXION
PU2,O,ST2B,WT85,MSPAX IN CONNECTION,1/29,BT258741
CHECKIN->XX4421/08MAR BRC
ORD CODE NAME FOID OFF CC SEAT BAG
011. DDKDRJ SEIJAS/DANIEL MR PP 22712197 AEP YY 2B 1/029 (258741) WT:85
#PAX IN CONNECTION
CHECKIN->XX4370/08MAR AEP
ORD CODE NAME FOID OFF CC SEAT BAG
008. DDKDRJ SEIJAS/DANIEL MR PP 22712197 MVD YY 2B 1/029 (258741) WT:85
#PAX IN CONNECTION
Accepting passengers with contact number
To accept a passenger with a contact number the command is through the SSR PCTC. The structure of the PCTC is:
1PU<item>,PCTC/<CONTACT NAME>/<COUNTRY CODE><PHONE NUMBER>{.<FREE TEXT>}
2PE-<secuence>,PCTC/<CONTACT NAME>/<COUNTRY CODE><PHONE NUMBER>{.<FREE TEXT>}
Example:
PU1,PCTC/JOE SMITH/US12548.PARTNER CONTACT
PU1,PCTC/JOE SMITH/US12548.PARTNER CONTACT
If there is a PCTC in the reservation, and then another one is entered in the PU or PE, the one entered will be informed in the check-in process.
The detailed information of the PCTC is included in the FLT file (version 1.5 onwards)
The PCTC will be displayed in the PE, PH and PLC commands with the /* extension (Example: PLC4176/*, see Passenger Lists)
The use of the contact number depends on the [CTC] PAX CONTACT REQUIRED parameter of the JJCHK table, which allows establishing whether the Check-In system will look for the PCTC information in the PNR or not. The parameter options are:
NO: the system will not look for the PCTC info in the reservation. It will only be included in the PLC and FLT file, if the PCTC is entered in the PU or PE commands.
OPTIONAL: the system will look for the PCTC information in the reservation (SSR PCTC), if it was not entered in the check-in commands. If the PCTC is not entered at check-in, or at the reservation, the check-in can be carried out without inconveniences; it is for this reason that the variable is called Optional.
MANDATORY: the system will look for the PCTC information in the reservation (SSR PCTC), if it was not entered in the check-in commands. If the PCTC is not entered at check-in, or at the reservation, the check-in cannot be performed; it is for this reason that the variable is called Mandatory (this variable is not yet available).
Accept passenger ignoring seat control (not implemented)
Those seats that might have a characteristic that does not allow the passenger to be seated will show a warning message indicating that the seat can’t be assigned, nevertheless the control can be override using different parameters
The airport agent needs to have the keyword CHKSIC assigned on its profile
Ignore Only Adults seats
The parameter is ,XSOA (except seat only adult)
Example:
In this case row 13 doesn’t allow children or infant but when ,XSOA is entered the control is override and the seat is assigned. The action will be reflected on the flight’s history
PV4444/29MAYAEP
F C Y
1 2 3 4 5 6 7 8 9 10 11 12 13 14
F A iA A iA A iA iA A A iA iO O
E A iA A iA iA A A iA iO O
D A iA iA A A iA iO O
» = =
C A iA iA A A iA · O
B A iA iA A iA iA A A iA iO O O
A A iA M$ iA iA A i* + iA A A iA iO O O
PU2-3,XSOA,ST13FE
CHECKIN->XX4444/29MAY AEP
ORD CODE NAME FOID OFF CC PARTY NAT. SEAT H.BAG BAG
011. PGOIDW GOMEZ CHAVARRO/PAULA *CHD PP59231817 MDQ YY AB2 13F 0/000
012. PGOIDW RIVAS/GUILLERMO *CHD PP77864788 MDQ YY AB2 13E 0/000
PH4444/29MAYAEP
PU #011 GOMEZ CHAVARRO/PAULA SOFIA *CHD PP59231817 CC:YY SEAT:13F BAG:0/0 *BZ: ZONE C *XSOA* 9990210033619C1
MBT:CIERR DOMES AEP-MDQ
AEPXX-GL 1528 8MAR21
PU #012 RIVAS/GUILLERMO *CHD PP77864788 CC:YY SEAT:13E BAG:0/0 *BZ: ZONE C *XSOA* 9990210033620C1
MBT:CIERR DOMES AEP-MDQ
AEPXX-GL 1528 8MAR21
Assign infant passenger to any seat
The parameter is ,XSAI (except seat assing infant)
Example:
In this case sear 9A doesn’t allow infants but when ,XSAI is entered the control is override and the seat is assigned. The action will be reflected on the flight’s history
PV4444/29MAYAEP
F C Y
1 2 3 4 5 6 7 8 9 10 11 12 13 14
F A iA A iA A iA iA A A iA iO O
E A iA A iA iA A A iA iO O
D A iA iA A A iA iO O
» = =
C A iA iA A A iA · O
B A iA iA A iA iA A A iA iO O O
A A iA M$ iA iA A i* + iA A A iA iO O O
PU1+4,ST9A,XSAI
CHECKIN->XX4444/29MAY AEP
ORD CODE NAME FOID OFF CC PARTY NAT. SEAT H.BAG BAG
013. GYSOFL GAVIRIA ARROYAVE/CAR PP 77668229 MDQ YY 9A 0/000
014. GYSOFL INF/INF *INF PP22222 MDQ YY 0/000
PH4444/29MAYAEP/PU
** HISTORY **
* FILTER APPLIED *
FLT: XX4444 BRD: AEP SAT 29MAY21
PU #013 GAVIRIA ARROYAVE/CAROLINA PP 77668229 CC:YY SEAT:9A BAG:0/0 *BZ: ZONE A1 *XSAI* 9990210033645C1
MBT:CIERR DOMES AEP-MDQ
AEPXX-GL 1613 8MAR21
PU #014 INF/INF *INF PP22222 CC:YY BAG:0/0 *BZ: ZONE A1 *XSAI* 9990210033648C1
MBT:CIERR DOMES AEP-MDQ
AEPXX-GL 1613 8MAR21
Edit checked passengers
In order to edit passenger information, retrieve the passenger details by sequence number, seat or last name.
Passenger details can be retrieved from the PLC or from the passenger search entry (PF)
The number located after the " - " is the sequence number assigned by the system at the check-in
Search
DCS system will display the passenger that is stored in memory, en case the info is expired or if you want to make sure you have the right passenger you will have to add the complete flight information after command line PE
Example:
PEXX4444/25AUGEZEMIA-<search criteria>
Search by sequence Number
PE-<sequence number>
Description:
PE-11
PE | Passenger Edit Indicator |
|---|---|
- | Dash |
11 | Passenger's sequence number |
Search by seat number
PE-<seat number>
Example:
PE-12A
Search by last name
PE-<last name>
Example:
PE-SMITH
Search by bagtag number
You may search by bagtag number or carrier + bagtag number (6 numeric characters). This type of seacrh works with automatico or semi-automatic bags
PE-BT<bagtag>
Example:
PE-BT005565
PE-BTXX123456
Search by party number
Search using party number
PE-<party number>
Example:
PE-AA4
Search by FOID
You may search using the first characters of foid indication type and space, if it exists.
PE-FO<FOID>
Example:
PE-FOPP12345678Z
Search by frequent flyer
You may search indicating carrier and the firsts characters of frequen flyer
PE-FF<carrier code>/<FF number>
Example:
PE-FFXX/9876
JJDCSOA - lnterline Agreements table for DCS
The command for displaying the DCS table for Interline Agreements between carrier airlines is:
JJDCSOA/*
CARRIER | AIRLINE IATA CODE |
|---|---|
ACC | ACCOUNTING CODE NUMBER |
ACT. | ACTIVE YES OR ACTIVE NO |
ALLOW MANUAL INPUT | ALLOWED TO ENTER MANUAL DATA |
AGREEMENT TYPE | EITHER IATCI OR BAGGAGE ONLY |
This table is complemented with the JJIATCI table which is specifically for IATCI agreements. So far there are no entries for configuring the JJDCSOA/* table but at least, it allows the airlines to check their IATCI and BAGGAGE ONLY agreements. KIU can configure if manual flight connections are allowed for Check-in or if only the command BTOA can be used when the connection flights are in the PNR.
PU and PE commands check on these tables from now on. Attempting a check-in when a carrier airline is not present or it is not active on the JJDCSOA/* table will cause the following message: INVALID - NO AGREEMENT BETWEEN CARRIERS .
Same message will be displayed if the carrier airline has an IATCI agreement but the agreement does not exist or it is not active on the JJIATCI.
The JJDCSOA/* is internally related to the JJIATCI table and so will be to the new BTM table not yet developed but as the management circuit is not yet developed, they may not be manually related by mistake. In order to have the visibility when this happens, following message will be added to airline line * NOT EXISTS SETUP DATA *. The display of the JJIATCI table will be like the display of the BTM table when it is developed but the commands could fail when internally unrelated.
The IATA accounting code (ACC) must be the correct one as the code is added as part of the bag tag number when they are generated by the BTM IN.
BTM
.V/1TJNB
.I/BP201/20OCT/GBE/Y
.F/ET1818/200CT/CPT/Y
.N/0074123512002
.W/K/1/3
.S/Y/3B/C/007
.P/A/JOHNSON/SUSAN MRS
ENDBTM
BTM | Standard Message Identifier (Baggage Transfer Message) |
|---|---|
.V/1TJNB | Transfer baggage at JNB |
.I/BP201/20OCT/GBE/Y | Inbound Flight Number/Date/Boarding Airport/Class Y |
.F/ET1818/20OCT/CPT/Y | Transfer/Connecting Airline Flight Number/Date/Destination Airport, CPT/Class Y |
.N/0074123512002 | 2 Pieces Of Baggage starting with Bag Tag Number 00741235120 and two pieces 2002 |
.P/JOHNSON/SUSAN | Passenger Name |
ENDBTM | End of Message Identifier |
Adding Inbound Baggage Data
Inbound baggage is the luggage that has been tagged in a previous airport in connection with our flight when there is not an IATCI agreement between carriers.
Once the passenger has been accepted on the local flight with the PU command, add the inbound baggage details using the PE command to generate the corresponding BSM as per IATA Recommended Practice 1745:
PE<Flight>/<Date><Route>-<Item or Boarding Number>,+<Number of Bags>/<Kg>/<Inbound Airline Bag Tag Number>, O |
Example:
PE089/18SEPAEPCOR-2,+1/15/LA123456,HB1/5,O
*HB is hand baggage and it is optional . Token BAF on JJCHK needs to be set as 2.
Considerations:
Actually inbound baggage can only be added using the Passenger Edition command (PE).
The token BAGT must be Y as it is not supported when BAGTS nor if BAGTN.
Bags must be individually added when the passenger has several bags as it is not yet supported adding more than one bag per command (i.e. PE-1,+2/30/LA123456/457,O) and neither when adding the baggage individually on same entry (i.e.:PE-1,+1/10+1/14/LA123456/457,O)
The inbound carrier airline must be on JJDCSOA/* table1 with an active baggage agreement
KIU system checks that bag tag number is not duplicated on the flight and when duplicated, the system will display following warning message: “INVALID - AT LEAST ONE BAG TAG EXISTS IN THE CURRENT FLIGHT" .
Combining inbound baggage with local checked-in baggage on the same entry is not supported (i.e. PE-28,+1/15+1/12/DL000522,O) The system will display error: “ADDING INTERLINE AND ONLINE BAGS AT SAME TIME IN SAME ENTRY NOT ALLOWED". It is not possible to mix inbound baggage informed by a received BTM (Baggage Transfer Message) with an online baggage BSM (Baggage Source Message) informing the airport BRS/BSS of a local checked-in baggage.
Pending to develop the process to control that there is not any unaccompanied baggage at CHKCLOSE but all baggage have been associated to a passenger. This control will be developed when the KIU system automatically processes inbound BTM. Meantime KIU system can generate a copy of the received Inbound BTM by e-mail at airline request.
1 JJDCSOA/* displays the DCS table showing airline interline and/or IATCI agreements with other airlines is explained below. Adding Inbound Baggage for a transit passenger is only available if the Inbound Airline is active on this table meaning there is an active baggage agreement.
Example of Baggage Source Message (BSM)
BSM
.V/1LAEP
.F/XX089/18SEP/COR
.N/045345678001
.W/K/1/15
.S/Y/10A/C/009
.P/BLANCO/A
.L/DACHYB
ENDBSM
BSM | Message Identifier |
.V/1LAEP | Boarding Airport |
.F/XX089/18SEP/COR | Airline Flight Number/Date/Destination Airport |
.N/045345678001 | Only one Bag (8001) and Bag Tag Number |
.W/K/1/15 | Weight/ Kg |
.S/Y/10A/C/009 | Reconciliation Data |
.P/BLANCO/A | Passenger |
.L/DACHYB | Record Locator |
ENDBSM | End of Message Identifier |
Deleting Inbound Baggage Data
Once you have searched for the corresponding passenger, use the following entry to delete the previous entered Inbound baggage:
PE<Local Flight Number>/<Date><Route>-<Boarding Number or Item>,-<Number of Bags>/<Exact Number of Kg>/<Inbound Bag Tag Number>,O |
Example:
PE089/1NOVAEPCOR-6,-1/10/LA800457,O
Deleting an inbound piece of baggage will automatically generate a BSM DEL for the Airport BRS/BSS or BHS (Baggage Reconciliation System and Baggage Sortation System) as shown on example below:
BSM
DEL
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008612001
.W/K/1/15
.S/Y/10A/C/002
.P/A/GOMEZ/LUIS
ENDBSM
BSM | Standard Message Identifier |
|---|---|
DEL | Delete |
.V/1LAEP | Boarding Airport is Aeroparque, AEP in Buenos Aires (Argentina) |
.F/XX089/01NOV/COR | Airline Flight Number/Date/Destination Airport |
.O/XX123/01NOV/NQN | Connecting with Airline Flight Number/Date/Destination Airport |
.N/999008612001 | Only one Bag (12001) and Bag Tag Number |
W/K/1/15 | Weight/ Kg/One Bag/15 Kg |
.S/Y/10A/C/002 | Reconciliation Data |
P/GOMEZ/LUIS | Passenger Name |
ENDBSM | End of Message Identifier |
Baggage Messaging History
Generated Baggage messages can be searched using the following input:
PH<Flight Number>/<Date><Boarding Airport>/MSGBAG |
Example:
PHXX089/01NOVAEP/MSGBAG *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BTM FOR LA TO BE USED AT COR CONNECTING AIRPORT |
NOTES:
1 *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:32Z *** (BSM message was generated but could not be sent due to missing BSM destination address or any other configuration data// Date and GMT Time).
2 *** BTM FOR LA TO BE USED AT COR CONNECTING AIRPORT
SENT BY TTY TO FRABM1C // AT 2023-09-07 18:59Z *** (BTM message was generated and sent to the teletype address FRABM1C// Date and GMT Time)
So far there are two filters available for a more accurate baggage message search on the PH history. The first one is the BSM and the second one is the BTM. For more accuracy, both filters can be also combined with the bag tag number or numbers.
For a more accurate search, bag tag numbers can be also added to the command as shown below:
PH<FLIGHT NUMBER>/<DATE><BOARDING AIRPORT>/MSGBAG<6 BAG TAG NUMBERS FOR ONE BAG+ 6 OR10 BAG TAG NUMBERS FOR ANOTHER BAG> |
Example:
PHXX089/01NOVAEP/MSGBAG008612+9990008647
MESSAGES GENERATED FOR BAGGAGE SORTATION/RECONCILIATION
FILTERED FOR BAGTAGS: 008612+999008647
*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:32Z ***
BSM
DEL
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008612001
.W/K/1/15
.S/Y/3A/C/006
.P/A/CORNQN MR
ENDBSM
PH<Flight Number>/<Date><Boarding Airport>/MSGBSM |
The second filter is for BTM message:
PH<Flight Number>/<Date><Boarding Airport>/MSGBTM |
Example:
The type of baggage message can be combined with the bag tag number/s as for more accuracy:
PH<Flight Number>/<Date><Boarding Airport>/MSGBSM<6 Bag Tag Numbers for one bag> +<6 or 10 Bag Tag Numbers for another bag> |
PHXX089/18SEPAEP/MSGBSM123456+0552345670
Accepting baggage in connection with other airlines flights
If an airport agent needs to accept and print a bag tag for a connecting flight with another airline, here are the steps to follow.
Only valid for flights with automatic bag tag printing (check Control Panel BAGT:Y)
In order to activate this feature parameter POA - ALLOW PRINT WITH OTHER AIRLINE SEGMENTS must be turned on at JJCHK table, please contact our helpdesk at host@kiusys.com or contact your account executive. Available configurations are:
Y: it allows to print only those flights that are present in the passenger itinerary.
N: it does not allow to print segments from other airlines
M: it allows manual input of flights from other airlines which are not on passenger itinerary besides the ones that are present in the passenger itinerary.
Accepting baggage in connection with other airlines flights on passenger´s itinerary
An airport agent should follow these steps for issuing bag tags for connecting flights which are present on passenger's itinerary and when there is not an IATCI agreement between the airlines.
Accept the passenger in all the flights but without adding any piece of baggage
Edit the passenger adding the baggage information, this action will add the bags to the online flights as well as those offline . Token is
,BTOAO<amount of connecting segments>Connecting segments are those segments shown as outbound ./O on the passenger search (Command line PC) and without considering the online segments
PE<flight>/<date><route>-<sequence number>,O,BTOAO<number of connecting flights>,+<bag quantity>/<weight>
Example:
PF119/25JULMVDAEP-DE CAMPOS CHECKIN-M> XX 119 /25JUL MVD ITEM CODE NAME FOID OFF ST CC SEAT NAT. BAG.ALLOW KAM FF #009* DRBDFJ DE CAMPOS/CECILIA AEP 11A .O/HK XX006 Y 25JUL SU AEPCOR 0800 1000 .O/HK AR667 Y 26JUL MO CORSCL 0700 0800 .O/HK AR618 Y 26JUL MO SCLLIM 1100 1300
PE119/25JULMVDAEP-9,BTOAO2,+1/20,O
CHECKIN-> XX119/25JUL MVD
ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG
#009. DRBDFJ DE CAMPOS/CECILIA AEP 11A LIM 1/020 (>XX005867)
MBT:CIERRE INTERNAC ALL
-> XX 006/25JUL AEP COR - UPDATED OK
#003 >ST: 11A >BT: 07:00 >GATE:
>ET:
SEGMENTS VALID ONLY FOR BAGTAGS
-> AR 667/26JUL COR SCL ### NO THROUGH CHECK-IN
Bag tag data is saved on flight history with the legend BAG TAG CONNECTION OA SEGMENTS
The BTOA indicator can only be used when checking-in the first bag/s because the KIU system assumes that all bags' final destination is the same as using the same combination. This is the reason why the route is entered only once for checking-in the first bag but additional bags will be automatically addressed to the same destination. Accepting baggage in connection with other airlines generates a BTM or Baggage Transfer Message as per IATA Resolution 709 , RP 1745.
This option can only be used if there is not a previous piece of baggage accepted for that passenger, otherwise the system will respond with the following error message:
INVALID - BAGGAGE ALREADY EXISTS FOR PASSENGER, DELETE AND RETRY
When adding offline flights that create a mismatch because flight arrives and departs from different airports , the system will display the following error message:
INVALID OA SEGMENT - CONNECTION DOES NOT MATCH
Accepting baggage in connection with other airlines flights not included on passenger´s itinerary
Please follow these steps for issuing bag tags for connecting flights that are not present on passenger's itinerary:
Accept the passenger in all the flights but without adding any piece of baggage
Edit the passenger adding the baggage information, this action will add the bags to the online flights as well as those offline (flight segments that are not on passengers itinerary). Token is
,BTOA(bag tag other airlines) followed by carrier code, flight number and destination airport. If needed, multiple connecting flights can be added if separated by a period (.)
PE<flight>/<date><route>-<sequence number>,O,BTOA<carrier code><flight number><destination airport>.<carrier code><flight number><destination airport>
Example:
PE4444/29MAYAEPMDQ-13,O,+1/1,BTOAAR4545LPB.LA41+LIM.LA325MIA.AA1578JFK.AA1945LAX
CHECKIN-> XX4444/29MAY AEP
ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG
#013. GYSOFL GAVIRIA ARROYAVE/CAROL PP 77668229 MDQ 9A LAX 1/001 (>XX005809)
MBT:CIERR DOMES AEP-MDQ
SEGMENTS VALID ONLY FOR BAGTAGS
-> AR4545/29MAY MDQ LPB ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT
-> LA 041/30MAY LPB LIM ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT
-> LA 325/30MAY LIM MIA ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT
-> AA1578/30MAY MIA JFK ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT
-> AA1945/30MAY JFK LAX ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT
Flight number must be between 1 and 4 characters.
Next day flight can be marked by adding a plus sign 
after flight number or a minus sign 
to mark previous day flight. Example PE125/25MARAEPSLA-1,+1/10,O,BTOAAR4545LPB.LA41+LIM.LA325MIA to indicate that flight to LIM is the next day, 26MAR according to the example
Bag tag data is saved on flight history with the legend BAG TAG CONNECTION OA SEGMENTS
The BTOA indicator can only be used when checking-in the first bag/s because the KIU system assumes that all bags' final destination is the same as using the same combination. This is the reason why the route is entered only once for checking-in the first bag but additional bags will be automatically addressed to the same destination. Accepting baggage in connection with other airlines generates a BTM or Baggage Transfer Message as per IATA Resolution 709 , RP 1745.
This option can only be used if there is no previous baggage accepted for that passenger, otherwise the system response will be:
INVALID - BAGGAGE ALREADY EXISTS FOR PASSENGER, DELETE AND RETRY
Up to 6 flight connections, including the online flight segment are accepted. When necessary, two linked bag tags will be issued as otherwise the system will display following error: ERROR BAGTAG - MAXIMUM 6 FLIGHT CONNECTIONS ALLOWED
If any incorrect data for the other airline flight is entered, the system will display an error message related to the wrong data (missin carrier code, non-numeric flight, invalid airport, etc)
INVALID INPUT FOR OTHER AIRLINE SEGMENT
Passenger edition using using 2D/QR scanners
You can use a 2D/QR scanner to invoque and display the information from a passengers boarding pass, the command line is
PE-R
The intimidate response changes according to the environment where it's executed:
CUTE airports (SITA-ULTRA-ARINC-RESA): the command line awaits for the boarding pass to be scanned
PE-R WAITING BOARDING PASS ....
The reader used in the CUTE environment might be overrride using the following commnad line. This action forces the behaviour emulating this functionality on an NON CUTE airport
PE-ROR (other reader)
IMPORTANT: this commnad lines only overrrides the configuration, we can´t guarantee the correct funtionality as the environment is controlled by a common use platform that might reject the use of an external peripheral
NON CUTE airports: the command line executes a pop-up windows that enables the use of the scanner, bare in mind that this pop-up is single use, one scan at the time, instead of multiple scans used at boarding process. Every time the airport agents wants to use the scanner the command line should be triggered. In order to use this feature the agent should be using KIU v1.700.102 or higher and PBR2 option must be set up on the Readers Setup in table JJCHK
The information displayed on the screen is the same for both environments, a search by sequence number is displayed along with a combinad line ready to be used with the variables the airport agent may need
Example:
PE-R CHECKIN-> XX4444/12JUN mad ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG #001.w IYCYKD SMITH/MERY PP21321546 EZE 11C 0/000 MBT:GATE CLOSES 15 MINUTES BEFEORE DEPARTURE ** PRE-CHECKED PASSENGER ** ENTER FOLLOWING COMMAND TO EDIT CHECK-IN INFORMATION PE4444/12JUNMADEZE-1,