Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Passenger Acceptance 



Info

This module covers all the different steps on how to accept passengers on a flight followed by the boarding process

Search for passengers pending to be accepted on the flight


Flight must be initialized and CHECK-IN status must be OPEN before passengers can be accepted

Use this entry to search for passengers:

PF<Flight number>/<Date><Boarding airport><Destination airport>-<Passenger last name>

Example:

Code Block
languagexml
PF4580/26JULAEPCOR-BASUALDO

Description

 PF   

 Command for passenger search

 4580   

 Flight Number

 /         

 Slash

 26JUL    

 Date

AEPCOR 

Board and Off point

-

Dash

BASUALDO 

Last Name

Code Block
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC FF
   1  AJYVVN BASUALDO/MARCOS           DNI192839138    COR HK YY

Description

ITEM

Reference number for each passenger listed

CODE 

AJYVVN

Passenger Name Record

NAME  

BASUALDO/MARCOS

Passenger Name

FOID 

DNI192839138

ID Number (Form of ID)

OFF                          

COR

Off point

ST                            

HK

Flight Segment Status (HK: Confirmed)

CC                               

YY

Cabin compartment and class of server

FF

Frequent Flyer (if applicable)

Code Block
PF4580/26JULAEPCOR-B
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC FF
   1  AJYVVN BASUALDO/MARCOS           DNI192839138    COR HK YY
   2  ESMGZC BASUALDO/GABRIEL          DNI22999002     COR HK YY
   3* NCMVAA BELISCCI/ANTONELLA        DNI8222128      COR HK YB
   4  ORIKJU BASILE/ALFREDO            DNI12999002     COR HK YB
   5  TVFSTJ BRITOS/SERGIO             DNI18125458     COR HK YY

The star (*) shown on item 3 indicates the PNR is multi-party which means that PNR contains more than one passenger under the same record locator.

From this list, you can either search or accept a passenger on the flight.




Search for passengers under the same record locator 


To display all the passengers in same PNR, the input is:

Code Block
languagexml
PF3

Response:

Code Block
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC FF
   1  NCMVAA BELISCCI/ANTONELLA        DNI8222128      COR HK YB
   2  ¤      AJUMEN/LORENA             DNI18222128     COR HK YB

Item 2 shows a ¤ sign instead of the record locator, this means locator is shared with the item on top.

When displaying more than one passenger with the same last name under the same locator, system will display the list as below:

Code Block
   PF4580/26JULAEPCOR-SEMINARA
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC FF
   1  SADHHF SEMINARA/EZEQUIEL                         COR HK YY
   2  ¤      CHUBIEK/BARBARA                           COR HK YY
   3  ¤      SEMINARA/FRANCO      *CHD                 COR HK YY
   4  ¤      SEMINARA/MIA         *INF                 COR HK YY
   5  ¤      SEMINARA/RACO        *INF                 COR HK YY

Passenger 2 does not have the same last name but shares the same record locator 


Search for passengers using the short entry (PF) 


This entry must be executed after passenger search was done by entering the flight number and departure date.

System will asume the flight number and departure date are the same as on the previous entry.

Example:

Code Block
languagexml
PF-ALVAREZ

The system will search for passenger ALVAREZ on the same flight and date entered on the previous PF transmitted


Search for multiple passengers


For searching for more than one passenger, you need to add a # to separate one last name from the other. 

Code Block
languagexml
PF3130-GOMEZ#LOPEZ

There is no limit for searching for multiple passengers as long as last names are separated by a #


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>

Info

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 without baggage and without seat selection


In order to accept passengers without baggage nor using seat selection, first search for the passenger and then upload him/her using the PU or passenger upload command.

Code Block
languagexml
 PU1

Description:

PU

Passenger Upload

1

Item number from the list

Example;

Code Block
PF4580/26JULAEPCOR-Z
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC  FF
   1  CYPNSD ZAOMON/A  
Code Block
PU1
CHECKIN->XX4580 /26JUL AEP
ORD CODE   NAME                FOID            OFF CC SEAT  BAG
001.CYPNSD ZAOMON/A                            COR YB 1A    0/000

Description:

ORD 

Sequence Number or boarding number

CODE 

Record Locator

NAME     

Passenger Name

FOID  

Passenger form of identification (travel document)

OFF       

Off point

CC            

Cabin compartment and class of service

SEAT      

Seat assigned at check-in

BAG     

Baggage (pieces and weight)

As passengers are accepted on the flight, the system assigns them a sequence number or boarding number 

Sequence number never changes, meaning that if a passenger gets offloaded it will keep the same number that was assigned when checked in, except if passenger is re-accepted on the flight, in this case the system will assign a new sequence number, correlative to the the last number assigned 

The number of passengers accepted will be in the totals displayed on the control panel (PC) and also in the traffic manifest (PW).

The system updates the E-ticket status from O (OPEN FOR USE) to C (CHECKED IN).


Accepting passengers using manual bag tags 


The number of bags and their total weight after a slash are shown on the screen together with the flight routing and bag tag numbers ( see BAG)

When using the semi-automated option for bag tag issuing available from the Control Panel (BAGTS), passenger acceptance should be done using the entry below:

PU<Item>,<Number of bags>/<Kg>, BT<flight route><Last 6 numbers on the manual bag tag>/<the last 2 numbers if correlatives>

Example:

Code Block
languagexml
PU1,2/30/123456/57

Response:

Code Block
PU1,2/30,BTAEPCOR12120/21
CHECKIN->XX4580 /26JUL AEP
ORD  CODE   NAME             FOID      OFF CC SEAT   BAG
004. VODDNB MENDEZ/JUAN      8378274   COR YY        2/030 (AEPCOR12120/21)

The semi-automated bag tag issuing option (BAGTS) has the following considerations: 

  • System accepts a maximum of 6 bag tag numbers for each bag  

  • When entering more than 6 bag tag numbers, the system response is: CHECK BAG TAG

  • When there is a discrepancy between the number of bags and the number of bag tags entered, the system response is: CHECK BAG TAG

  • When using a bag tag number previously entered, the system response is: CHECK DUPE followed by the bag tag number repeated or duplicated.

  • If a bag tag number starts with a zero (0) DO NOT enter the leading zero 

  • The version for bagagge control, does not permit editing information for the baggage already dispatched. For updating baggage checked a + or - sign should preceed the number of bags ( PE-1,+1/15 or PE-1,-1/15)

  • To delete a piece of baggage , use the - sign to decrease the number. Please be aware that 0/BT0 is not accepted.

  • When entering correlative tag numbers use the following entry to autocomplete: PU1,ST1A,3/30/12345-* This entry is only valid for the PU command, and on the example the system will add 12345, 12346 y 12347.


Accepting passengers with seats


Use this entry to display the seat map (graphical pop up):

Code Block
languagexml
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:

Code Block
languagexml
PV{flight}/{date}{Board Point}{Off Point} 

The seat map will be displayed as below

Code Block
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:

Code Block
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 passenger2 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 

Code Block
languagexml
PF4176-M
Code Block
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) 

Code Block
languagexml
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.

Code Block
PU1-3,ST4ABC

Response:

Code Block
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:

Code Block
languagexml
PF4176-R
Code Block
  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. 

Code Block
languagexml
PU1-3,ST4ABC

Response:

Code Block
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:

Code Block
PF4176-R
Code Block
  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
Code Block
languagexml
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 passengers on a jump seat 


Use the following entry to accommodate passengers on a jump seat:

Code Block
languagexml
PU1,JMP

Description:

PU    

Passenger upload command

1 

 Item number

,

Comma separator

JMP

Jump Seat indicator

System responds with the check-in details, JMP displays under the column SEAT:

Code Block
  PU1,JMP
 CHECKIN-> XX4176 /25SEP AEP
  ORD  CODE   NAME                      FOID            OFF CC SEAT   BAG
  003. AHNUZX ANDERSON/EVANGELINA       DNI 443433      SLA YY JMP    0/000


Accepting passengers adding a frequent flyer number


Add a frequent flyer number after the passenger upload entry:

Code Block
languagexml
PU1,FF1234567

PU

Passenger upload command

1

Item number

,

Comma separator

FF

Frequent flyer indicator

1234567

Frequent flyer number

This entry displays the graphic seat map then complete the check in process as usual 


Accepting passengers using a paper/manual ticket 


Add a ticket  number after the passenger upload entry:

Code Block
languagexml
PU1,TM9990000001

Descripción:

PU 

Passenger upload command

1

Item number

,

Comma separator

TM

manual ticket indicator

9990000001  

Ticket number


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:

Code Block
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:

Code Block
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:

Code Block
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:

Code Block
PLC5050/27JUNEZ

Response:

Code Block
** 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:

Code Block
PC5050/27JUNEZE,NATY

Deactivate the indicator

PC<FLIGHT NUMBER>/<DATE><ORIGIN>,NATN

Example:

Code Block
PC5050/27JUNEZE,NATN
Note

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:

Code Block
languagexml
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 Acceptance with a message in a boarding Pass


  • The text will be printed on all those boarding passes  that are accepted in the command.

  • For connecting flights boarding passes the text will apply for all flights involved

PU1,MB<free text>

Example:

Code Block
PU1,MBEARLY BOARDING

Description:

PU

Fixed command

1

Item number

,

Comma

MB

Text to print indicator

Free Text

Free text of up to 20 alphanumeric characters and / or special characters asterisk and hyphen

System response:

Code Block
PU1,MBEARLY BOARDING
CHECKIN->XX4444/30DEC AEP
 ORD CODE NAME FOID OFF CC PARTY SEAT H.BAG BAG
 002. DEVUQS ABASOLO/KARIN PP 02206766 MDQ YY 6D 0/000
 MB:EARLY BOARDING
 
PU1,MBPRIORITY,O
CHECKIN->XX4444/30DEC AEP
 ORD CODE NAME FOID OFF CC PARTY SEAT H.BAG BAG
 015. EATLSI FLORES/FRANCISCO PP 68685743 MDQ YY AB9 6A 0/000
 MB:PRIORITY

CHECKIN->XX 725/30DEC MDQ
 ORD CODE NAME FOID OFF CC PARTY SEAT H.BAG BAG
 001. EATLSI FLORES/FRANCISCO PP 68685743 USH YY AA9 6A 0/000
 MB:PRIORITY


Delete message in a boarding pass


To delete the boarding pass text, it must be reprinted with the following command:

PE<flight>/<date><route>-<item>,MB

Example:

Code Block
PE4444/30DECAEPMDQ-23,MB

Description:

PE

Fixed command

4444/30DECAEPMDQ

Flight information

-

Hyphen

23

Checked passenger item number

,

Comma

MB

Text indicator. In order to delete the text previously entered MB indicator with no additional text has to be added.

Code Block
PE4444/30DECAEPMDQ-4,MB
 CHECKIN-> XX4444/30DEC AEP
ORD CODE NAME FOID OFF PARTY SEAT H.BAG BAG
 #004. DEVUQS YOUN/KYOUNGJAMS PP 39472709 MDQ AA8 6F 0/000


Modify a message in a boarding pass


To modify a  message printed on a boarding pass, it must be reprinted with the following command

PE<flight>/<date><route>-<item>,MB<new text>

Example:

Code Block
 PE4444/30DECAEPMDQ-89,MBVIP ACCESS

Description:

PE

Fixed command

4444/30DECAEPMDQ

Flight information

-

Hyphen

89

Checked passenger order number

,

Comma

MB

Message indicator

VIP ACCESS

Free text up to 20 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:

Code Block
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.

Info

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 PEcommand:

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 /Yat 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.

Info

APIS available at airline request.


History


All transactions related to messages in boarding pass will be recorded in the flight history.

PH<flight>/<date><origin>

Example:

Code Block
PU #002 ABASOLO/KARIN PP 02206766 CC:YY SEAT:6D BAG:0/0 9990210010518C1
 MB:TEST TEST TEST TEST
 AEPXX-GL 1303 25SEP17
PE #004 MB:<DELETED>
AEPXX-GL 1319 25SEP17
PE #002 MS:PSGRVIP
 AEPXX-GL 1429 25SEP17



Accepting passengers with Upgrade/downgrade 


System supports a logic for UPGRADE or DOWNGRADE of passenger. The aircraft assigned to the flight must have more than one cabin. 

In order to process the UPGRADE or DOWNGRADE check if the control panel is set to control the e-ticket, if yes, before the transaction e-ticket must also be upgraded or downgraded (see the ticket issuing manual) 

Use this entry to Upgrade the cabin: 

Code Block
languagexml
PU<item number>,UPC

Description: 

PU 

Passenger upload command

1  

Item number

,

Comma separator

UP

Upgrade/Downgrade indicator

C

Cabin compartment where the passenger's being accommodated after Up/Downgrade


Code Block
languagexml
PU<item number>,UPCC


 PU

Passenger upload command

 Item number

 Comma separator

UP 

Upgrade/Downgrade indicator

CC 

Cabin compartment where the passenger's being accommodated after Up/Downgrade when flight schedule does not have this cabin available

Cabin compartment where the passenger's being accommodated after Up/Downgrade


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:

Code Block
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:


Note

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: 

Code Block
  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:

Code Block
		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:

Code Block
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.

Note

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 passenger by gender 



Add the gender after te passenger upload entry as shown below: 

Code Block
PU1F

PU 

Passenger Upload

passenger item number

Female gender indicator

When specifying the passenger's gender, the traffic manifest will fed with the default weight for male or female. If not specified system will automatically assume the passenger is an adult male. Passengers added as CHD or INF do not need a gender specification as system defaults to child or infant weight regardless of the gender 

System keeps a record of the passengers accepted with a specific gender by adding GE:F  to the line for the passenger upload entry

Example:

PH21/22APR

PU  #001 PEREZ/LUISA MRS PP 17003190 CC:YY SEAT:1C BAG:0/0 GE:F

GE: Gender Indicator 

F   Female gender indicator 



Accepting passengers adding specific weight 


Add this indicator to the passenger upload entry to specify the passenger's weight. 

Code Block
languagexml
PU1,WT80

Description:

PU

Comma separator ndo fijo de aceptación en el check-in

1

passenger item number

,

comma separator, mandatory

WT

 weight indicator

80

Passenger's weight. Only whole number are accepted and maximum value is 999

This function permits to specify the passenger exact weight at check-in.

When exact weight is not specified (WT) system will default to the values added on the JJCHK table for each passenger type. 

WT function is  combinable as other functions when adding indicators to the passenger upload entry, such us ST ( Seat Selection), FF ( Frequent Flyer), TM ( Manual  Ticket) y baggage details.

Example: PU1,ST10A,WT68,MSPAX VIP

Note

1. The WT Indicator can only be added can only be added when accepting one passenger at a time . I.e. WT cannot me used when accepting more than one passenger on the same transaction (PU1+2,WT100)

2. Al momento de hacer el check-in se visualizará en el Comma separator ndo de respuesta el peso asignado al pasajero luego de los datos del equipaje como se muestra a continuación: After passenger is accepted, system displays the passenger details including the passenger's weight as shown below

No Format
CHECKIN-> XX4176 /29NOV AEP
  ORD  CODE   NAME                      FOID            OFF CC SEAT   BAG
  001. LFKHUR ZALAZAR/MARIANA           DNI 432432      SLA YY 3A     0/000 WT:55


WT indicator displays only when specified on the PU entry, if not specified system will not display the WT indicator on the response



Accepting multiple passengers with baggage  (Pool) 


Use the same entry as for uploading multiple passengers and add the bag information 

Code Block
languagexml
PU1-2,2/30,BTAEPCOR789456/57

PU

Passenger upload command

1-2

passenger item

,

Comma separator

2/30

baggage pieces and weight

,

Comma separator

BT

 Bag Tag indicator

AEPCOR

Board and off point

45562/3

tag number/s

By adding a "-" system assumes passenger item are sequential

When selecting items that are NOT sequential use a + sign after each passenger item.

On the following example, items 1, 3 and 5 are selected from the list.

Code Block
PU1+3+5,2/45,BT45562/3

Response:

Code Block
CHECKIN->XX4580 /26JUL AEP
ORD  CODE   NAME                 FOID        OFF  CC SEAT   BAG
005. TQEJEW DELAVEGA/DIEGO   *CHD            COR  YY        2/045 (AEPCOR45562/3)
006. TQEJEW DELAVEGA/MARTIN  *CHD            COR  YY        0/000

The baggage information will be added to the first passenger accepted. Under the column BAG will display the pieces and weight separated by a slash and the board and off point and tag number in brackets.

Note

INFANT Passengers cannot be check-in individually. INFANT must always be accepted on the same transaction with and ADULT



Accept passengers by category (free text)


El Comma separator ndo es:The system allows to accept passengers by category. Each category is a free text defined by the carrier. 

Code Block
languagexml
PU1,CTA

PU

Passenger upload command

1

passenger Item

,

comma separator

CT

category indicator

A

texto libre de 1 carácter

Example:

PU1,CTA

 CHECKIN-> XX4300 /14JUL AEP

  ORD  CODE   NAME                      FOID            OFF CC SEAT   BAG

  001. CKWQMV PEREZ/LUIS MR             PP 81792962     MDQ YY 5C     0/000 CT:A

System add the /CT indicator at the end of the response. /CT filter can be added to the PLC list:

PLC4300/CT

Code Block
PLC4300/CT
** PASSENGERS CHECKED **
FLT: 4300    BRD: AEP    THU 14JUL11
                    
STATUS    CHECK IN: OPEN     
          BOARDING: OPEN         PAXS:   4
 
 ORD  NAME                        SEAT   BK OFF CODE   BOARD  CT
 001. PEREZ/LUIS MR                5C    Y  MDQ CKWQMV        A
 002. RONDON/JULIANA               9B    Y  MDQ VJAZER
 003. CASTILLO/LEONARDO            11C   Y  MDQ TYQUAY
 004. VERNET/ADA                   8C    Y  MDQ GIAWNR        E

Note

CT indicator is included to the exportable file PLC-SEND and FQTV,


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):

Code Block
languagexml
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

Code Block
languagexml
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

Code Block
languagexml
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 passenger with the SSR CKIN


System will request data validation when accepting a passenger who's record locator includes the SSR CKIN

PU entry will display the information (free text) included on the SSR CKIN letting the agent know the data needed to be verified. This information must ve validated in order to print the boarding pass.

Record locator includes SSR CKIN with residence information:

RP/AEP00XX4 - LINEAS AEREAS XX
 1.1CAPPELLI/ELENA MRS   »PP 04459039
 1  XX030 Y 17APR WE EZELIM HK1  0800 0900
TKT/TIME LIMIT  1 TKT/OK * 16APR13/AEPXX-GL
  2 TKT/ET 9992200038701 * 16APR13/AEPXX-GL - CAPPELLI/E.
FARE - PRICE RETAINED
CONTACTS
  1-AEP  999 AUTO PNR GEN V.1
SSR
  1 CKIN YY HK1/RESIDENT DCDN/12345678Z/350075/123456789-1CAPPELLI/ELENA MRS
RECEIVED FROM - PNRGEN
AEP.KIUHELPGL 1757/16APR13   *BXJKJM -H~006BXJKJM

After searching for the passenger, passenger upload entry responds with the following message:

PF30/17APRAEPMDQ-CA
CHECKIN-M> XX  30 /17APR AEP
ITEM  CODE   NAME                      FOID            OFF ST CC   FF
   1  BXJKJM CAPPELLI/ELENA MRS        PP 04459039     MDQ HK YY

PU1
CKIN 1HK -1CAPPELLI/ELENA MRS
     /RESIDENT DCDN/12345678Z/350075/123456789

In order to let the system know the data contained on the SSR CKIN was validated  repeat the entry adding /Y

Code Block
languagexml
PU1/Y

Once the SSR CKIN element is validated the acceptance process continues as normal, meaning that, seat map is displayed, allowing to add a seat and print boarding passes, etc.

The validation entry can be combined with other basic functions such as:

PU1-2,ST3AB/Y
PU1-2,BT2/123456/123457/Y
PU1,JMP/Y


Accepting passengers reserved as group PNR 


In order to accommodate passengers reserved as group, use the same entries as instructed for individual passengers, consider a maximum of TEN passengers is permitted per transaction. Otherwise system responds: 

INVALID - MAXIMUM PERMITTED 10 PAX PER TRANSACTION

Example:

PF4176/28APR-PEREZ

CHECKIN-M> XX4176 /29APR AEP

ITEM  CODE   NAME                      FOID            OFF ST CC   FF

 GRP  ZSPTVF GRP GRUPO TRAVEL/15                          SLA HK YY

   1  ¤      TORRES/A                  NI43432         SLA HK YY

   2  ¤      TORRES/B                  NI453423        SLA HK YY

   3  ¤      TORRES/C                  NI4553          SLA HK YY

   4  ¤      TORRES/D                  NI565           SLA HK YY

   5  ¤      TORRES/E                  NI54543         SLA HK YY

   6  ¤      MORENO/A                  NI43432         SLA HK YY

   7  ¤      MORENO/B                  NI453423        SLA HK YY

   8  ¤      MORENO/C                  NI4553          SLA HK YY

   9  ¤      MORENO/D                  NI565           SLA HK YY

  10  ¤      MORENO/E                  NI54543         SLA HK YY

  11  ¤      PEREZ/A                   NI43432         SLA HK YY

  12  ¤      PEREZ/B                   NI453423        SLA HK YY

  13  ¤      PEREZ/C                   NI4553          SLA HK YY

  14  ¤      PEREZ/D                   NI565           SLA HK YY

  15  ¤      PEREZ/E                   NI54543         SLA HK YY


PU1-15

INVALID - MAXIMUM PERMITTED 10 PAX PER TRANSACTION


Accept passengers adding a Form of ID (FOID)


Add the ID indicator and the ID number to the passenger upload entry: 

Code Block
 PU1,FOPP20816722 

Description: 

PU  

Passenger upload command

1  

Passenger item number

,   

Comma separator

FO

FOID indicator

PP1234567

Document type and number

System add the FOID at passenger acceptance according to the following priority order:

1º. From SSR FOID, if available

2º. From FOID added to the NAME field on the PNR.

3º. If no SSR FOID or FOID added to the name field, no FOID data is added.

The FO indicator, followed by the document type and number is prioritized over any other SSR FOID or FOID on the name field 

In order to enter the FOID on the graphic seat map add the ,FO indicator followed by the format indicated to the OTHER ELEMENTS field.

If accepting multiple passengers and adding ,FO on the same entry same FOID is added to all passengers included on the transaction. 


Accommodating a passenger with different seats on the same Boarding Pass (multi-leg flight) 


When accepting passengers on flights with 2 or more flight legs same seat may not be available for the whole journey. In this case, seat can be assigned by flight leg, this option must be executed on the passenger upload entry ( PU). This option is not supported by the graphic seat map, thus,once passenger search displays the list, make the following entry:

Code Block
languagexml
PU1,ST7C.1D 

Response 

CHECKIN->XX4500/23APR AEP

ORD CODE NAME FOID OFF CC SEAT BAG

016. LBILLD DEVITO/MARCELO PP383883 BRC YY 7C*1D 0/000 

Description:

PU

Passenger upload command

1

Passenger Item

,

Comma separator

ST

Seat indicator

7C

 Seat number for the first leg

.

Period ( . ) divides one seat from the other

1D

  Seat number for the second leg

This entry includes the seat for the first and second flight leg separated by a "." 

Note

This entry is available only for flights with a maximum of 3 flight legs

Options 

En los casos de 3 tramos el Comma separator ndo a aplicar sería indicando un asiento por tramo. Si el mismo asiento se utilizará en dos tramos se deberá aclarar igualmente. En estos casos deben indicarse los 3 asientos, uno por cada tramo.

Each leg has a different seat:

PU1,ST13A.13B.12C 3

Two out of three legs are the same:

PU1,ST13A.13A.12A 2

This option is also available when accepting multiple passengers, seats must be contiguous and add a period to separate each flight leg seat information. 

Example:

PU1-4,ST13AB17EF.13AB17EF.12ABC13A

Seats 13A, 13B, 17E and 17F are assigned to passengers from 1 to 4 for the first flight leg, Same seats for the second leg and 12A, 12B, 12C y 13A for the third one. 

Seat map display: 

After executing the passenger search entry (PF) and before the passenger upload entry (PU) Native Seat map can be display to verify the seat availability for each flight leg by entering: 

Code Block
PVF1 

FVP 

 Fixed command

passenger Item number displayed by PF

Accepted passenger list display

The Accepted passenger list displays as shown below 

PLC4330/12MAY

** PASSENGERS CHECKED **

FLT: 4330 BRD: AEP WED 14MAY14

STATUS CHECK IN: OPEN

BOARDING: OPEN PAXS: 12

ORD NAME SEAT BK OFF CODE BOARD

002. VILLEGAS/RUBEN 11B Y BHI ODBRGJ

005. AVELAR/SILVIA 14F Y MJR REGKDQ

006. ADA/ADA 14E Y MJR REGKDQ

007. VELARDE/NANCY 15E Y MJR REGKDQ

008. HIGUITA/ANDREAMRA 15F Y MJR REGKDQ

009. ALVARADO/DORA MRS 5A*16B Y MJR REGKDQ

010. WERNET/ANAIS 4A*17A Y MJR REGKDQ

011. DIRKSZ/JESSICA MS 7E*18A Y MJR REGKDQ

012. HERNANDEZ/WILFREDOMR 13A*13A*12A Y BHI ODBRGJ

013. MADURO/EDWIN 13B*13B*12B Y BHI ODBRGJ

014. TEST/TEST 17E*17E*12C Y BHI ODBRGJ

015. SANMARTIN/JESUSA 17F*17F*13A Y BHI ODBRGJ

Seat Change 

1. For those passengers accepted with a different seat per leg is not possible to edit or change the seats. In order to do so, passenger must be offloaded and accepted with the new seats.

2. Mass offload (PEDEL) is not supported. Offload passengers individually 

3. REGISTRATION change does not re accommodate  passengers with different seats by flight leg, passengers are listed on the PLC list and a question mark ( ? ) shows before the seat number (un-honored). Repeat the steps on step #1 to offload.


Accommodating a passenger with different seats on the same Boarding Pass (multi leg flight) and connecting flights 


Same as previous example use the passenger search command for passengers with connecting flights:

Code Block
PF<FLIGHT NUMBER>-<LAST NAME>

Use the following entry to specify multiple seats on multi-leg flight and also a connecting flight:

Code Block
PU1,ST11A.3A+1D,O 

Response:

CHECKIN->XX4330/16JUL AEP

ORD CODE NAME FOID OFF CC SEAT BAG

015. FZALOY ORTIZ/ORLEY PP 55670152 MJR YY 11A*3A 0/000

CHECKIN->XX 432/16JUL MJR

ORD CODE NAME FOID OFF CC SEAT BAG

  1. FZALOY ORTIZ/ORLEY PP 55670152 CPC YY 1D 0/000

Description:

PU

Passenger upload command

1

 passenger item number

,

 comma separator

ST

Seat number indicator

11A

Seat number for the first leg

.

Period ( . ) divides one seat from the other per leg on the same flight

3A

Seat number for the second leg

+

 + sign as separator for seat on connecting flight

1D

Seat number for connecting flight

,

comma separator

O

Outbound connection indicator

This entry specifies the seat for the first and second flight leg separated by a period ( . ) then, a + sign separates the seats on the first flight from the seat on the connecting flight. 

Note

This entry applies to flights with a maximum of three flight legs

Options

The applicable options are the same as the ones mentioned on the previous section by adding a + sign to specify a seat number on the connecting flight and ,O at the end of the entry

Seats are diferente on each on three legged-flight and a connecting flight:

PU1,ST13A.13B.12C+4B,O

This option is also available when accepting multiple passengers, seats must be contiguous and add a period to separate each flight leg seat information, repeat the steps to add outbound connecting flight data.

Example:

PU1-2,ST3BC.11A10A+6A7A,O

Accommodates passenger 1 and 2 on seats 3B and 3C for the first flight leg, then asignes 11A and 10A for the second leg and 6A and 7A to the connecting flight 

Seat Map Display 

After executing the passenger search entry (PF) and before the passenger upload entry (PU) Native Seat map can be display to verify the seat availability for the connecting flight by entering: 

Code Block
languagexml
PVF1,O

PFV

Fixed command

1

Passenger Item (PF)

,

comma separator

O

 Outbound flight indicator


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

Info

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

Note

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

Code Block
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

Code Block
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

Accepted Passengers 


On the Passenger search display, system adds a # followed by the sequence number to identity the passengers that were already accepted.

Example:

Code Block
PF4580/26JULAEPCOR-J
CHECKIN->XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC  FF
   1* SUWDMD JUNES/A                                   COR HK YY
   2* SUWDMD JUNES/D                                   COR HK YY
#010  QUKEZE JUAREZ/NORA                               COR
#011* SUWDMD JUNES/S                                   COR

Passengers 1 and 2 of this list are not yet checked and maintain the order assigned in the Comma separator search, however, passengers identified with # 010 and # 011 are already checked with their corresponding sequence number.


Infant Passengers 


When accepting lap infant passengers (INFOA) they must always be accepted with an adult on the same transaction. Once accepted will be listed as below:

Code Block
languagexml
018. SEMINARA/EZEQUIEL              Y  COR SADHHF      (SEMINARA/RACO)
019. SEMINARA/RACO        *INF      Y  COR SADHHF      (SEMINARA/EZEQUIEL)

The associated passenger will display in brackets on the right hand side.


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


Note

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:

Code Block
languagexml
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

 

Adding or editing checked-in baggage


Make the following entry to add or edit the baggage details of a passenger that's already accepted (BAGT:N):

Code Block
languagexml
PE-11,1/10,BTAEPCOR12121

On this example, a 10kg  baggage was added informing the board and off point and tag number. This entry will add or replace the data specified. the indicators not specified on the entry will not be edited.

Response: 

Code Block
PE-11,1/10,BTAEPCOR12121CHECKIN-C>XX4580 /26JUL AEPORD CODE   NAME                      FOID       OFF SEAT   BAG#011 SUWDMD JUNES/S                             COR        1/010 (AEPCOR12121)

If BAGTS option is ON use the following entry: 

Code Block
languagexml
 PE-1,+2/10/3333/4444

When adding baggage to a passenger, system will verify tag number does not get duplicated ( same verification done at the PU entry). this control applies by passenger and not by flight.

For this version, editing baggage information is not available.

When entering the baggage editing entry (PE-1,1/10,BT123456)  system will respond with the following message

Code Block
AUTOMATIC BAGTAG ENABLE / USE +

On the semi-automated version is not available editing the baggage wheight only for checked in bags: PE-1,+0/5

Is possible to add a new piece without any weight : PE-1,+1/0/55555

Info

Baggage may be edited if the passenger is already boarded, no other editing variable is allowed for boarded passengers. If the airport agent has CHKOXB keyboard excess baggage control might be override


Deleting accepted baggage


Use the following entry to delete accepted baggage: 

Manual Baggage

Code Block
languagexml
PE-<Sequence number>,0/0

Response:

Code Block
languagexml
PE4444-1,0/0
    CHECKIN-> XX4444/04JUL AEP

ORD    CODE   NAME            FOID              OFF  PARTY         SEAT   BAG
#001.  JDPOZD RAIGOSA/CARLOS  PP 36382485       MDQ                  5A    0/000

Under the column BAG the values are 0/000

If the option BAGTS is configured the following entry is available: 

Code Block
PE-<sequence number>,-1/<baggage weight>/<manual tag number>

By making this entry system will update the baggage details and will display a response including the bag tags deleted

BAG DELETED:  2222

Is possible to delete a bag piece and a tag number and not decreasing the passenger's total weight: PE-1,-1/0/55555

If willing to delete all the baggage pieces and weight, add the minus sign ( - ) followed by the total pieces, weight and tag numbers, i.e: PE-2,-3/30/1111/2222/3333

Automated Baggage

Code Block
PE-<sequence number>,-1/10/<automated bag tag number>

Response:

PE4444-2,-1/10/XX003989

Code Block
CHECKIN-> XX4444/04JUL AEP

ORD    CODE   NAME              FOID              OFF  PARTY         SEAT   BAG
#002.  TCNSSN RAIGOSA/JUAN      PP 36382485       MDQ                  5B    0/000
Info

Baggage may be edited if the passenger is already boarded, no other editing variable is allowed for boarded passengers. If the airport agent has CHKOXB keyboard excess baggage control might be override


Re-printing a baggage tag 


Those carriers printing bag tags automatically (BAGT:Y) and using version 2 can re print a specific baggage tag. This functionality requires keyword CHKPBT to be included on Agent's sign.

This functionality is only available when bag tag includes segments for the sabe carrier, if tag includes another airlines segment, re print will not be available.

In order to re print bag tags for connecting flights, is mandatory to add the indicator ,O otherwise, system will respond  INVALID - THIS ACTION MUST BE APPLIED TO ALL CONNECTING FLIGHTS

Re-prints a tag number indicated on the entry. Number can include carrier code, number including leading zeroes, or without them. 

Code Block
languagexml
PE-1,PBT<BAGTAG NBR>

Example:

PE-1,PBTXX000123

PE-1,PBT00123

PE-1,PBT123 

Re-printing multiple bag tags: 

Re prints the tag numbers indicated on the entry, A maximum of 15 bag tags can be included on the same entry.

  • Multiple bagtags:

Code Block
languagexml
PE-1,PBT<BAGTAG NBR>/<BAGTAG NBR>

Example:

PE-1,PBT123456/123457

  • Bag tag range:

Re-prints the bag tag range indicated on the entry.  A maximum of 15 bag tags can be included on the same entry.

Code Block
languagexml
PE-1,PBT<BAGTAG NBR>-<BAGTAG NBR>

Example:

PE-1,PBT123456-123460

  • All bag tags for a passenger:

Re prints all bag tags issued for a passenger (maximum is 15 bag tags, if more, system responds CHECK BAGTAG)

Code Block
languagexml
PE-1,PBTALL 
  • Bag tags on connecting flights 

Re-prints a bag tag indicated on the entry that include a connecting flight.

Code Block
PE-1,PBT<BAGTAG NBR>,O 

Example:

PE-1,PBTXX000123,O (the option ,O applies to all options on the entry)

agent sign includes


Handling Baggage from an Inbound Flight ( No IATCI )

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

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

BAGGAGE MESSAGING HISTORY

Generated Baggage messages can be searched using the following input:

PH<Flight Number>/<Date><Boarding Airport>/MSGBAG

Example:

PHXX089/01NOVAEP/MSGBAG
MESSAGES GENERATED FOR BAGGAGE SORTATION/RECONCILIATION

*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:32Z *** 1

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

*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:45Z ***

BSM
DEL
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008607001
.W/K/1/10
.S/Y/3A/C/006
.P/A/CORNQN MR
.N/999008608001
.W/K/1/15
.S/Y/3A/C/006
.P/A/CORNQN MR
ENDBSM

*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:51Z ***

BSM
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008645001
.W/K/1/10
.S/Y/3A/C/006
.P/A/CORNQN MR
.N/999008646001
.W/K/1/30
.S/Y/3A/C/006
.P/A/CORNQN MR
ENDBSM

*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:59Z ***

BSM
.V/1LAEP
.F/XX089/01NOV/COR
.O/LA1234/01NOV/FRA
.O/LA6478/02NOV/FCO
.N/999008647001
.W/K/1/3
.S/Y/3B/C/007
.P/A/CORNQN MRS
ENDBSM

*** BTM FOR LA TO BE USED AT COR CONNECTING AIRPORT
SENT BY TTY TO FRABM1C // AT 2023-09-07 18:59Z *** 2

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.

Note

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.

  1. Accept the passenger in all the flights but without adding any piece of baggage

  2. 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:

Code Block
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
Code Block
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
Info

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.

Warning

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:

  1. Accept the passenger in all the flights but without adding any piece of baggage

  2. 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:

Code Block
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
Info

Flight number must be between 1 and 4 characters.

Next day flight can be marked by adding a plus sign (plus) after flight number or a minus sign (minus) 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.

Warning

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

Edit baggage when flight is closed


PE entry can be used to add or remove baggage, re-print bag tags,(keyword required) and reprint boarding pass ,even though CHKIN is in CLOSE status. It is mandatory that boarding is OPEN.

Possible scenarios

  • CHK OPEN + BRD OPEN: permitted OK

  • CHK CLOSE + BRD OPEN: permitted OK

  • PAX BOARDED + CHK CLOSE + BRD OPEN: permitteed OK

  • PAX BOARDED + CHK CLOSE + BRD CLOSE: not permitted OK

Ejemples of possible entries

PE203/28JANAEPCOR-1,P

Code Block
languagexml
PE203/28JANAEPCOR-1,PBTALL
PE203/28JANAEPCOR-1,+1/10
PE203/28JANAEPCOR-1,+2/10

Note: You can only add or remove from 1 to 9 pieces of baggage,otherwise the system will respond with an error message. “FLIGHT CLOSED FOR CHECK-IN


Add or edit a seat



To add or edit a seat, or edit a seat assigned at the check-in use the following entry:

Code Block
PE-1,ST5C

Description;

PE

Passenger Edit Indicator

-

Dash

1

Passenger's sequence number

,

Comma separator

ST

 Seat indicator

5C

Seat Number

Response:

Code Block
PE-11,ST5C
 CHECKIN-C>XX4580 /26JUL AEP
  ORD CODE   NAME                 FOID      OFF SEAT   BAG
 #011 SUWDMD JUNES/S                        COR 5C      2/015 (AEPCOR87137264)



Seat Swap


This functionality permits to swap the seat numbers between two passengers that were already accepted on the same flight.

Use the following entry:

Code Block
PE<FLIGHT>-<BP1>,ST-<BP 2>

Example:

PE4176-1,ST-2

On the last example, seat assigned to passenger with sequence number 1 will be assigned to passenger with sequence number 2 and viceversa. 

Description:

PE

Passenger edit indicator

4176

Flight Number

-

Dash

1

Sequence number

,

Comma separator

ST

Seat Indicator

-

Dash

2

Sequence number for passenger willing to swap seats with

It is also possible to swap seats by replacing the sequence number with  seat number willing to swap. entry format is:

Code Block
PE<FLIGHT>-<BP 1>,ST-<SEAT NUMBER>

Example:

PE4176-1,ST-10A

On the last example, the seat assigned to passenger with sequence number 1, will be swapped with seat 10A and viceversa.

Considerations:

Seat swap applied only to the same flight, meaning that will not apply to connecting flights

  • Seat Swap does not apply to passengers with multiple seat assigned to the same flight (multi leg flight) Example: 2A*11C 

  • In case of having lap infants associated to the adult. Seat swap verifies new seat accepts laps infants, otherwise responds: CHECK SEAT

  • After a seat swap, boarding passes are automatically printed 

Flight History

On flight history seat swap will be recorded as below: 

Code Block
PE   #002 ST: 3A -> 12A
AEPXX-JF 1451 7JAN16 



Add or edit passenger's frequent flyer number 


In order to add or modify the passenger's frequent flyer number use the following entry: 

Code Block
languagexml
PE-1,FF547896

Description:

PE

Passenger edit entry

-

Dash

1

Passenger's sequence number

,

Comma separator

FF

Frequent Flyer Indicator

547896

Frequent Flyer number



Add or edit passenger's manual ticket number (paper ticket) 


In order to add or modify the passenger's Manual ticket number use the following entry:

PE-1,TM9990000005

PE 

Passenger edit entry

-

Dash

1

Passenger's sequence number

,

Comma separator

TM 

Manual ticket indicator

9990000005

Manual Ticket Number



Add or edit passenger's comment 


In order to add or modify the passenger's Manual ticket number use the following entry:

Code Block
languagexml
PE-1,MS new text

Description:

PE

Passenger edit entry

-

Dash

1

Número de orden del pasajero a modificar

,

Comma separator

MS

message indicator

Nuevo Texto

New text

This entry will enter a new comment or will replace a previous one. In order to delete a comment, use the same entry by leaving the text field blank, example: 

Code Block
PE-1,MS



Modify a passenger weight 


In order to add or modify the passenger's weight use the following entry:

Code Block
languagexml
PE-3,WT78

This entry will replace the passenger weight entered at check-in (manual or default) 

In order to delete a value manually specified and replace it by default specified on the JJCHK table, add the value 0 to the entry as explained below:

Code Block
languagexml
PE-3,WT0



Edit passenger's gender 


 In order to add or modify the passenger's gender use the following entry:

Code Block
languagexml
PE-2,F

On this example, passenger with sequence number 2, new gender is FEMALE


Edit Passenger's category (Free Tet)


 In order to add or modify the passenger's gender use the following entry:

Code Block
languagexml
PE-3,CTE


PE

Passenger edit entry

-

Dash

3

numero de ítem del listado

,

Comma separator

CT

Category Indicator

E

Free text

Example:

PE-3,CTE

 CHECKIN-> XX4300 /14JUL AEP

  ORD CODE   NAME                      FOID              OFF SEAT    BAG

 #003 TYQUAY CASTILLO/LEONARDO         PP 91338517       MDQ  11C   00/000 CT:E



Delete passenger's category (free text)


Use this entry to delete  passenger's category previously entered: 

Code Block
languagexml
PE-3,CT

PE

Passenger edit entry

-

Dash

3

passenger item

,

Comma separator

CT

category indicator

Leave the free text space blank after the CT indicator 


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

Code Block
PE-R
WAITING BOARDING PASS ....
Info

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:

Code Block
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,

Offloading accepted passengers 


Offload individually

Use the command PE- followed by the sequence number and the Delete indicator to offload a passenger that was accepted on the flights. In addition passenger ser can be performed from the accepted passenger list (PLC) or with the Passenger search entry (PF)  

Code Block
languagexml
PE-10,DEL


PE

Passenger edit indicator

-

Dash (separator)

10

sequence number

,

Comma separator

DEL

Offload indicator

Response:

PE-10,DEL

 CHECKIN-C>XX4580 /26JUL AEP

        * * *   P A X    OFF    L O A D    * * *

  ORD CODE   NAME               FOID         OFF SEAT   BAG

 #010 QUKEZE JUAREZ/NORA                     COR        2/045 (AEPCOR45562/3)

System responds with the following message: 

* * *   P A X    OFF    L O A D    * * *

Passenger is automatically removed from the accepted passenger list

Note

Passenger must NOT be boarded.

For those carriers using the Check-in version 2, will have the option to display a warning message before offloading the passenger, warning will include the passenger's name and last namem, flight, date, off point, record locator, and must be confirm by adding /Y at the end of the entry

Example:

Code Block
languagexml
PE18/28MAYCORAEP-1,DEL
RE-ENTER FOLLOWING COMMAND TO OFF LOAD PSGR BARRA/LARA - XX  18/28MAY COR - JBOMYZ
PE18/28MAYCORAEP-1,DEL/Y

Response:

Code Block
languagexml
PE18/28MAYCORAEP-1,DEL/Y
 CHECKIN-C>XX18 /28MAY AEP
        * * *   P A X    OFF    L O A D    * * *
  ORD CODE   NAME               FOID         OFF SEAT   BAG
 #010 JBOMYZ BARRA/LARA                     COR        2/045 (AEPCOR45562/3)

In order to activate this function, activate the following option [CWO]CONFIRMATION WHEN OFFLOADING PAX on the JJCHK table. Require this activation via email to KIU help desk.


Bulk offload 


There is an entry to do a mass offload to all accepted passengers, Duty 5, 7 or 8 and keyword CHKLV2 are required on agent sign . Entry is only available for flights within 48hs, before or after scheduled departure date.

The CHECK IN status on the flight's control panel must be CLOSE or SUSP and no passengers should be boarded.

Once flight status is CLOSE, SUSP or any status other that OPEN, must execute the following entry:

Code Block
languagexml
PEDEL{flight}/{date}{Board Point}{Off Point}

Example:

Code Block
languagexml
PEDEL4420/24NOVAEPBRC

Response:

Code Block
languagexml
PEDEL4420/24NOVAEPMDQ
TO PROCESS ENTER
PEDEL4420/24NOVAEPMDQ/Y 

System request a confirmation, requiring to re enter the same entry followed by a /Y at the end of the entry, once executed, system responds:

Code Block
languagexml
PEDEL4420/24NOVAEPMDQ/Y
OK. 12 PAX OFF LOAD

This action will offload passengers from the accepted passenger list, returning the e-ticket status to OPEN FOR USE, and a line describing the entry used

Warning

PEDEL entry will not take any action over e-tickets issued by another GDS; in the casi of mass offload, first offload passengers with e-tickets issued on another GDS manually and then use the PEDEL entry.



Offloaded Passenger List 


Use the following entry to display the passenger offloaded list:

Code Block
languagexml
PLC4580/26JULAEP/DEL

Response:

Code Block
PLC4580/26JULAEP/DEL
** PASSENGERS DELETED **
FLT: 4580    BRD: AEP    WED 26JUL06

STATUS    CHECK IN: OPEN      
          BOARDING: CLOSE         PAXS:   3

 ORD  NAME                        SEAT  BK OFF CODE   BOARD
 001. BELISCCI/ANTONELLA                B  COR NCMVAA
 003. ARAGON/ANA                  3A    Y  COR TQEJEW
 010. JUAREZ/NORA                       Y  COR QUKEZE

The display shows passengers kept the same sequence number.

When passenger is offloaded it cannot be on loaded as the passengers that are not listed on the offloaded list.

The system will assign a new sequence number and it will be correlative to the last accepted passenger. 

The PLC/DEL is available before and after flight close.


Reprint a boarding pass


If necessary use the following entry to reprint a boarding pass.

Code Block
languagexml
PE-1,P

Response:

Code Block
CHECKIN-C>XX4580 /26JUL AEP
 ORD CODE   NAME          FOID         OFF SEAT        BAG
#001 HGVPRO BALADO/LUIS   DNI12123123  COR 05C     3/045 (AEPCOR789456/57/98)