Passenger Acceptance 

Search for passengers

pending to be accepted on the flight

In order to start accepting passengers on the flight, it Flight must be initialized and the CHECK-IN Status status must be OPEN before passengers can be OPEN accepted

Use this entry to search for passengers:

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

Example:

PF4580/26JULAEPCOR-BASUALDO

Description

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

Description

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 the item 3 indicates the PNR is multi-party , meaning which means that PNR contains more than one passenger under the same record locator.

From this list, you can either search or accept entries can be entereda passenger on the flight.

Search for passengers under the same record locator 

In order to To display all the rest of the passengers on the item 3, once the list is displayed enter the following entrypassengers in same PNR, the input is:

PF3

Response:

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:

   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 flight number and departure date are the same as on the previous entry.

Example:

PF-ALVAREZ

the entry The system will search for passenger ALVAREZ on the same flight and date as entered on the last previous PF entry excecutedtransmitted

Search for multiple passengers

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

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) add the outbound connecting flight information at the end of the same entry.Entry will accept passengers on connecting flights only for those scheduled to depart within 24 hs since the originating flight is scheduled to depart. Also. flights segment must 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 (status but following flight reservation status will not be included: UC, UN, DL, NS will NOT be included).

.I/ MeansMeaning INBOUND connection, i.e. flights with arrival times arriving within 24 hours before the departure time of the flight that is being checked inactual flight.

.O/ representsMeaning OUTBOUND connectionsconnection, that is, flights with departure times within departing in the next 24 hours after the departure time of the actual flight being checked in.

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: 

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:

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:

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:

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:

Searching for more than one passenger departing from a different airport and with different last names:

Accepting Passengers

After searching for a passenger accept a passenger by selecting an item from the list displayedin 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 or bagsselection, first search for a the passenger and make the then upload him/her using the PU or passenger upload entrycommand.

 PU1

Description:

Example;

PF4580/26JULAEPCOR-Z
CHECKIN-R>XX4580 /26JUL AEP
ITEM  CODE   NAME                      FOID            OFF ST CC  FF
   1  CYPNSD ZAOMON/A  

PU1
CHECKIN->XX4580 /26JUL AEP
ORD CODE   NAME                FOID            OFF CC SEAT  BAG
001.CYPNSD ZAOMON/A                            COR YB 1A    0/000

Description:

As passengers get 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 assigned assign a new sequence number, correlative to the the last number assigned 

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

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

Accepting passengers

Search for a passenger and from the list displayed use the following entry:

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:

Example:

PU1,2/30,BTAEPCOR789456/123456/57

Response:

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)

Under the column BAG will display the amount of pieces , and the total weight will after a slash followed by the board and off point and the tag number in brackets.

If control panel is configured with the option BAGTS  (semi-automated) tag number and weight and be manually added separating both with a slush ( / ) as shown below:

PU1,2/30/123456/57

This option (BAGTS) has the following considerations: 

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. Si se desean modificar los datos de los equipajes, se deberá utilizar la opción con los símbolos + o –To delete baggage , use the option to decrease baggage by using a – sign. This configuration does not accept the option ,0/BT0For 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 enter 12345add 12345, 12346 y 12347.

Accepting passengers with seats

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

PS{flight}/{date}{Board Point}{Off Point}

This entry allows to display a seat map with the current occupation updated 

In addition the seat map can be displayed on the screen native mode by using the following entry:

PV{flight}/{date}{Board Point}{Off Point} 

Seat map displays on the screen with the following format:The seat map will be displayed as below

C        Y                 [  [  [  [  [  [  [  [                 
   1  2  3  4  5  6  7  8  9  10 11 12 13 14 15 16 17 18 19 20 21 22 
F  A  A  A  A  A  I                 R  A/ A  A  A  A  A  A  A  B  A  
E           A  A  A                 R  A/ A  A  A  A  A  A  A  B  A  
D  A  A  A  A  A  A                 R  A/ A  A  A  A  A  A  A  B  A  
»                                   =     =                          
C  A  A  A  A  A  A  A  A  A  A  A/ R  A/ A  A  A  A  A  A  A  B  A  
B           A  A  A  •  •  A  A  A/ R  A/ A  A  A  A  A  A  A  B  A  
A  A  A  A  A  A  I  •  •  A  A  A/ R  A/ A  A  A  A  A  A  A  B  A 

In order to display the reference to for each seat code used shown on the seat map, add a * sign at the end of the entry.

Example:

PV3416/07FEBAEP*

This entry displays the seat map and also the references for each code as following:

SEAT REFERENCES:
  •           OCCUPPIED
  I           AVAILABLE WITH INFANTS
  A           AVAILABLE
  B           BLOCKED
  R           RESERVED
  /           RECLINE RESTRICTED
  »           CORRIDOR
  =           EMERGENCY EXIT
  [           WINGS

Assign seats using the entry PU and PE, follow the steps as for accepting passengers without seats (free-seating) 

Example:

Example:

Search for a passenger 

PF4176-M

CHECKIN-M> XX4176 /17MAR AEP
ITEM  CODE   NAME                      FOID            OFF ST CC   FF
   1  AHWHOS MORES/CARLA               DNI 4343233     SLA HK YY
#002  TQBSRC MORENO/PAULA              DNI 454545      SLA

System displays a similar name list, then use the passenger upload entry (PU) 

PU1

If flight initialized including the mandatory seat assignment option on, system displays the graphic seat map automatically:

Once the seat map is displayed click on the seat to select or type the seat number on the "Seat" box (If typing the seat, seat number must be all CAPITAL LETTERS, i.e. 1C not 1c) 

In addition, this screen permits to add baggage pieces and weight and tag numbers.

Once all the passenger details were added clic OK

This screen displays the flight details, and the seat references according to it status.

Accepting passengers on available seats (direct entry)

If executing the passenger on load entry and specifying a seat number, passenger is accommodated without displaying the passenger seat map.

PU1-3,ST4ABC

Response:

CHECKIN-> XX4176 /17MAR AEP
  ORD  CODE   NAME                      FOID            OFF CC SEAT   BAG
  003. NSTZDV GOMEZ/SANDRA              DNI 44444       SLA YY 4A     0/000
  004. NSTZDV GOMEZ/MARIA               DNI 54445       SLA YY 4B     0/000
  005. NSTZDV GOMEZ/JOSE                DNI 45233       SLA YY 4C     0/000

Error when selecting seats occupied or unavailable 

If when executing the passenger on load entry seats are not available, system responds and error and re displays the graphic seat map

 Example:

PF4176-R

  CHECKIN-M> XX4176 /17MAR AEP
ITEM  CODE   NAME                      FOID            OFF ST CC   FF
   1  VNKZWS ROMERO/LUIS               DNI 44343       SLA HK YY
   2  ¤      TORRES/LUCIA              DNI 434324      SLA HK YY
   3  ¤      FERNANDEZ/MARIA           DNI 6577        SLA HK YY

PU1-3,ST4ABC

Select available seats and complete baggage details, and other elements.

This graphic display includes a frequent flyer field and for other indicators as ignore control for tickets (Field Other elements)

After selecting seats, click OK, system will proceed to check the passenger in.

Accepting passengers on available seats (Direct acceptance) 

Add a seat number to the passenger upload entry, if seat is available passenger is accommodated without displaying the seat map. 

PU1-3,ST4ABC

Response:

CHECKIN-> XX4176 /17MAR AEP
  ORD  CODE   NAME                      FOID            OFF CC SEAT   BAG
  003. NSTZDV GOMEZ/SANDRA              DNI 44444       SLA YY 4A     0/000
  004. NSTZDV GOMEZ/MARIA               DNI 54445       SLA YY 4B     0/000
  005. NSTZDV GOMEZ/JOSE                DNI 45233       SLA YY 4C     0/000

Error when adding occupied or blocked seats to the passenger upload entry (PU) 

When executing the passenger upload entry and the selected seats are unavailable system will respond displaying the seat map showing the seats that are available. 

Example:

PF4176-R

  CHECKIN-M> XX4176 /17MAR AEP
ITEM  CODE   NAME                      FOID            OFF ST CC   FF
   1  VNKZWS ROMERO/LUIS               DNI 44343       SLA HK YY
   2  ¤      TORRES/LUCIA              DNI 434324      SLA HK YY
   3  ¤      FERNANDEZ/MARIA           DNI 6577        SLA HK YY

PU1-3,ST4ABC

Click on the selected seats, or type the seat number, add the baggage information and tag number (if applicable) 

This screen also permits to add a frequent flyer number and on the field Other Elements add messages, or ignore the flight number and date control.

After selecting the seat and completing the baggage details click OK. System will proceed to accommodate the passenger.

For carriers checking through SITA or ULTRA applications do not enter a number as system will add it automatically. 

Accepting passengers on a jump seat 

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

PU1,JMP

Description:

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

  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:

PU1,FF1234567

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:

PU1,TM9990000001

Descripción:

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:

Description:

Example:

PU1,NAARG

Options

Option 1

Assign the same nationality to all passengers in the specified range

Example:

PU1-4+7+9,NAARG

Assigns the same nationality specified as ARG to all passengers to check (from 1 to 4, passenger 7 and passenger 9)

Option 2

Assign different nationalities to all specified passengers (the option to specify different nationalities for a range of passengers is not allowed)

Example:

PU1+4+7+9,NAARG.COL.FRA.USA

It assigns ARG to passenger 1, COL to passenger 4, FRA to passenger 7, and USA to passenger 9.

Entrance from the command with seat assignment through the automatic display of the on-screen seat map

You can allow multiple passengers to check in:

After input:

Once the map is displayed, in the "Other elements" it appears ", NANNN"

List of checked passengers (PLC)

A new column is added in the display of checked passengers with the Nationality entered in the reservation (in the SSR DOCS), in the API mask or the one entered at the time of checkin.

Example:

PLC5050/27JUNEZ

Response:

** PASSENGERS CHECKED **
FLT: 5050    BRD: EZE    THU 27JUN19

STATUS    CHECK IN: CLOSE         ** POST DEPARTURE ** KIU  AUTO-PROCESS **
          BOARDING: CLOSE

 ORD  NAME                                SEAT BK OFF CODE                BOARD  NATIONALITY  FOID                  FREQUENT FLYER        TICKET MANUAL          E-TICKET NUMBER    H.BAG  BAGGAGE    AGENT ID
   2. MEC/DISCO                            10A Y  MIA XGKQGY       0Z  Y             AR   PP66666                                                            9990210009719/1            0/0       KIUHELPMC
       #BT: 
       #DHS: OK TO BOARD
             DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
   3. ALVAREZ/ENRIQUE                      15A Y  MIA IILATR       0Z  Y             ESP  PP22222                                                            9990210009738/1            0/0       KIUHELPMC
       #BT: 
       #DHS: OK TO BOARD
             DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
   4. GONZALEZ/PEDRO                       15B Y  MIA RJPHLD       0Z  Y             ESP  PP9999                                                             9990210009736/1            0/0       KIUHELPMC
       #BT: 
       #DHS: OK TO BOARD
             DHS - CLEAR / ESTA EVUS - NOT APPLICABLE
   5. RODRIGUEZ/NESTOR                     15C Y  MIA RJPHLD       0Z  Y             ESP  PP55555                                                            9990210009737/1            0/0       KIUHELPMC
       #BT: 
       #DHS: OK TO BOARD
             DHS - CLEAR / ESTA EVUS - NOT APPLICABLE

The column with the Nationality is also added in the excel spreadsheet that is generated in the option of sending to an EXCEL spreadsheet (PLCxx-EXCEL)

Activation/deactivation indicator by flight in the Control Panel

A new indicator was created in the Control Panel (called NAT) which determines if the entry of the Nationality is mandatory at the time of checkin.

Activate the indicator

Examplw:

PC5050/27JUNEZE,NATY

Deactivate the indicator

Example:

PC5050/27JUNEZE,NATN

Accepting passengers adding a comment 

Add a comment after the passenger upload entry:

PU1,MS FREE TEXT 

Descripción:

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

Example:

PU1,MBEARLY BOARDING

Description:

System response:

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:

Example:

PE4444/30DECAEPMDQ-23,MB

Description:

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

Example:

 PE4444/30DECAEPMDQ-89,MBVIP ACCESS

Description:

 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. 

• In the search result the system  will return  a list of those passengers accepted on the flight holding boarding passes that contain a message under the indicator #MB

• The filter / MB can be combined with other filters and extensions of the PLC list

Example:

PLC4444/30DEC/MB
** PASSENGERS CHECKED **
FLT: XX4444 BRD: AEP SAT 30DEC17

FILTER: ONLY PAXS WITH BOARDING REMARKS

STATUS CHECK IN: OPEN 
BOARDING: OPEN PAXS: 22
ORD NAME SEAT BK OFF CODE BOARD
002. ABASOLO/KARIN 6D Y MDQ DEVUQS
#MB: PRIORITY BOARD
003. ATERRIZA/PAX 6E Y MDQ DEVUQS
#MB:PRIORITY BOARD
005. GAMBOA/DIONISIA 7F Y MDQ DEVUQS
#MB:PRIORITY BOARD
006. STIPO/ALVARO 7E Y MDQ DEVUQS
#MB:PRIORITY BOARD
007. JVIAJEROUNO/JVIAJERO 7D Y MDQ DEVUQS
#MB:PRIORITY BOARD
008. JUREZ/MARIELA MRS 8D Y MDQ DEVUQS
#MB:PRIORITY BOARD

CS - Check-in Stop Message

The purpose of CS or check-in stop message is to add a message to passenger record in order to take a specific action involving the passenger at the check-in counter. This CS message can be added before accepting the passenger on a flight or afterwards. The following command is for adding a CS message to the PNR before passenger acceptance on a flight:

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:

To delete a CS message:

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:

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:

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:

The following entry will display the list of passengers with a CS message added at the check-in counter using the PE-<Item> input.

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.

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.

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

Example:

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
language xml
PU<item number>,UPC

Description: 

PU 

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

  Item

Passenger item number
,	Comma separator (mandatory)

UP

Upgrade/Downgrade indicator

C

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

Code Block
language xml
PU<item number>,UPCC

 PU

Passenger upload command

1 

 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:

Image Removed

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

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:

Image Added

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: 

PU1F

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. 

PU1,WT80

Description:

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

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

Accepting multiple passengers with baggage  (Pool) 

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

PU1-2,2/30,BTAEPCOR789456/57

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.

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

Response:

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.

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. 

PU1,CTA

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

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

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 “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

conecting

connecting flights: 

In order to accept passengers on connecting flights add the indicator ,O to the Passenger upload entry (PU):

Code Block
language xml
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 on CUTE platforms (third party vendors)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
language xml
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 sign when accommodating multiple passengers on the same transaction and must assign 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
language xml
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

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: 

 PU1,FOPP20816722 

Description: 

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:

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:

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

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: 

PVF1 

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:

PF<FLIGHT NUMBER>-<LAST NAME>

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

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:

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. 

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: 

PVF1,O

Accepted Passengers 

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

Example:

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:

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.

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

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: 

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: 

 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

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

Deleting accepted baggage

Use the following entry to delete accepted baggage: 

Manual Baggage

PE-<Sequence number>,0/0

Response:

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: 

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

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

Response:

PE4444-2,-1/10/XX003989

CHECKIN-> XX4444/04JUL AEP

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

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. 

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:

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.

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)

PE-1,PBTALL 

• Bag tags on connecting flights 

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

PE-1,PBT<BAGTAG NBR>,O 

Example:

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

agent sign includes