SITA Departure Control Services Check in Agent Guide

Passenger Solutions
SITA Departure Control Services
Check In Agent User Guide
Copyright Notice
SITA, 2000 2008
All Rights Reserved
The information contained in this document is the property of SITA. No part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical,
photocopying, recording, or otherwise, without the prior written consent of SITA. Under the law,
copying includes translating into another language or format. Legal action will be taken against any
infringement.
The information contained in this document is subject to change without notice and does not carry any
contractual obligation for SITA. SITA reserves the right to make changes to any products or services
described in this document at any time without notice. SITA shall not be held responsible for the
direct or indirect consequences of the use of the information contained in this document.
Table of Contents
1.
Introduction .................................................................................................................................... 1
1.1. General Information ................................................................................................................................ 1
1.2. Course Objective .................................................................................................................................... 1
2.
System Functions .......................................................................................................................... 3

2.1. Agent Control .......................................................................................................................................... 3
2.1.1 Workstation Information............................................................................................................... 3
2.1.2 Agent Information ........................................................................................................................ 4
2.1.3 Agent Sign-In............................................................................................................................... 4
2.1.4 Agent - Out (AO) Agent - In (AI) .................................................................................................. 6
2.1.5 Sign - Out (SO)............................................................................................................................ 8
2.1.6 Display Area (DA)........................................................................................................................ 9
2.2. Paging................................................................................................................................................... 10
2.3. Paging within Multi-Page Displays ........................................................................................................ 10
2.4. Printing (PC/PT).................................................................................................................................... 10
2.5. Encode/Decode (EX: / DX:) .................................................................................................................. 11
2.5.1 Encode Entry (EX:).................................................................................................................... 11
2.5.2 Decode Transaction (DX:) ......................................................................................................... 12
2.5.3 Time Calculation (TCC:) ............................................................................................................ 14
2.6. SITA Help Facility ................................................................................................................................. 15
3.
Daily Flight List Display............................................................................................................... 17

3.1. Check-In Flight List Display (CFL) ........................................................................................................ 17
4.
Flight Information Displays and Updates ..................................................................................23

4.1. Flight Data Display (FDD) ..................................................................................................................... 23
4.2. Mode of Update .................................................................................................................................... 25
5.
Seat Map Display.......................................................................................................................... 27

5.1. Seat Map (SE) ...................................................................................................................................... 27
5.2. Viewing the Seat Map ........................................................................................................................... 28
5.3. Aircraft Compartment Limits /Control Messages................................................................................... 31
5.4. Seat Map Use ....................................................................................................................................... 31
6.
Passenger Survey Display .......................................................................................................... 33

6.1. Passenger Survey Display (SDD) ......................................................................................................... 33
6.2. SDD with a Zone Entry ......................................................................................................................... 38
SITA Departure Control Services Check In Agent Guide

Table of Contents
29 August 2008 Revision 7.2
Page v
SITA 2008 All Rights Reserved
6.3. SDD for Code share Flights .................................................................................................................. 39

6.4. SDD for an Overweight Flight ............................................................................................................... 41
7.
Passenger Displays ..................................................................................................................... 43

7.1. Booked / Checked-In Display (PS)........................................................................................................ 43
7.2. Standby / Notification Display ............................................................................................................... 49
7.2.1 Standby Display (SB) ................................................................................................................ 49
7.2.2 Need Notification ....................................................................................................................... 49
7.2.3 Transit PAD ............................................................................................................................... 49
7.2.4 Local PAD ................................................................................................................................. 49
7.2.5 Standby ..................................................................................................................................... 49
7.2.6 Need Notification ....................................................................................................................... 50
7.2.7 Standby ..................................................................................................................................... 51
7.3. Individual Passenger Record Display (PDD)......................................................................................... 51
7.4. Search by Bag Tag ............................................................................................................................... 56
7.4.1 Manual Bag Tags ...................................................................................................................... 56
8.
Passenger Acceptance / Modification / Withdrawal .................................................................59

8.1. Introduction ........................................................................................................................................... 59
8.2. Passenger Acceptance (PA) Check-In.................................................................................................. 59
8.2.1 Check-In Procedures................................................................................................................. 60
8.2.1.1 Check in from a Previous PS List Display: .................................................................. 60
8.2.1.2 Check-in Detailed Entry............................................................................................... 61
8.2.2 Gender Required Flights ........................................................................................................... 62
8.2.3 Upgrade/Downgrade Passengers.............................................................................................. 66
8.2.3.1 Pre-Upgrade / Pre-Downgrade.................................................................................... 66
8.2.3.2 Upgrade (UPG)/Downgrade (DNG) Passengers Already Checked-In......................... 66
8.2.3.3 To Cancel Pre-Upgrade/Downgrade ........................................................................... 67
8.2.4 Re-Checking Passengers to a Different Destination.................................................................. 67
8.2.5 Checking In Passengers with Double Oncarriage Segments .................................................... 68
8.2.6 Checking In Passengers on an Overweight Flight ..................................................................... 68
8.2.7 Oncarriage Check-In ................................................................................................................. 69
8.2.8 Checking In Passengers on a Connecting Flight ....................................................................... 70
8.2.9 Through Check-In...................................................................................................................... 70
8.2.9.1 Through Check-in Involving Electronic Tickets on Two Flights ................................... 70
8.2.9.2 Through Check-in Electronic Ticket on One Flight and Paper Ticket on Other Flight71
Table of Contents
Page vi
8.2.10 Examples of Different Check-In (PA) Entries............................................................................. 71

8.2.11 Passenger Manifest Information ................................................................................................ 79
8.2.12 DOCS, DOCA and DOCO Information at Check-In Time .......................................................... 79
8.2.12.1 DOCS Travel Document Information........................................................................ 80
8.2.12.2 Deleting Docs from Passenger Records ..................................................................... 84
8.2.12.3 DOCA - Address Information....................................................................................... 85
8.2.12.4 DOCO (Other Travel Related Information) Information ............................................... 88
8.2.12.5 Entries to List Passengers with DOCS, DOCO or DOCA Information ......................... 90
8.2.12.6 Entries to List Passengers Missing DOCS, DOCO or DOCA Information ................... 91
8.2.12.7 Error Responses for DOCS, DOCA, DOCO................................................................ 92
8.2.13 Passport Information at Check-In Time ..................................................................................... 93
8.2.14 Adding PSPT after Initial Check-in ............................................................................................ 95
8.2.15 PSPT DOB FOR WATCHLIST .................................................................................................. 95
8.2.16 Deletion of PSPT Remark ......................................................................................................... 96
8.2.17 Passenger Handling Displays.................................................................................................... 97
8.2.18 PDD Display .............................................................................................................................. 97
8.2.19 Boarding Pass Inhibit for APIS Flights....................................................................................... 97
8.2.19.1 Crew Mask Entries ...................................................................................................... 97
8.2.20 Advanced Passenger Processing System (APP) .................................................................... 101
8.2.21 Check-In .................................................................................................................................. 102
8.2.21.1 To Check Single Passengers: ................................................................................... 102
8.2.21.2 To Check Multiple Passengers:................................................................................. 102
8.2.21.3 Checking a Passenger without PSPT or DOCS data: ............................................... 102
8.2.21.4 Check-in of Multiple Passengers - Partial Acceptance by CPS System. ................... 104
8.2.21.5 Passenger Cancellation ............................................................................................ 106
8.2.21.6 Limits on Number of Passengers .............................................................................. 106
8.2.21.7 Standbys ................................................................................................................... 107
8.2.21.8 Override .................................................................................................................... 108
8.2.21.9 Re-sending APP Message ........................................................................................ 109
8.2.21.10
Status Codes ....................................................................................................... 109
8.2.21.11
DFL Prohibited ..................................................................................................... 110
8.2.21.12
CREW Check-in................................................................................................... 110
8.2.22 AQQ ........................................................................................................................................ 110

8.2.22.1 Passenger Check-in and Update .............................................................................. 110

Table of Contents
Page vii
8.2.22.2 Passenger cancellation: ............................................................................................ 111

8.2.22.3 Limits on Number of Passengers .............................................................................. 112
8.2.22.4 DFL Prohibited .......................................................................................................... 112
8.2.23 Watchlist .................................................................................................................................. 112
8.2.23.1 ITCI ........................................................................................................................... 115
8.2.23.2 Watch List Query....................................................................................................... 116
8.2.23.3 Boarding Process ...................................................................................................... 116
8.2.23.4 Flight Close Out ........................................................................................................ 117
8.2.23.5 Passenger Updates................................................................................................... 117
8.2.23.6 Passenger Displays (PS) .......................................................................................... 117
8.3. Group Check-In (GRP) ....................................................................................................................... 118
8.4. Standby Check-In (NOREC/URES/PAD) ............................................................................................ 120
8.4.1 NOREC Check-In .................................................................................................................... 120
8.4.2 URES Check-In ....................................................................................................................... 121
8.4.3 PAD Check-In.......................................................................................................................... 121
8.4.4 NOREC/URES Standby Passengers with Oncarriage............................................................. 122
8.4.5 NOREC/URES Passengers with Oncarriage........................................................................... 122
8.4.6 NOREC/URES Passengers with a Marketing Segment on a Code share Flight ..................... 123
8.5. ITCI Passenger Handling Procedures................................................................................................. 124
8.5.1 General Description................................................................................................................. 124
8.5.2 Passenger Acceptance (PA).................................................................................................... 124
8.5.2.1 PA Seat Requests ..................................................................................................... 128
8.5.2.2 PA Subsequent Processing....................................................................................... 128
8.5.3 Passenger Update (PU) .......................................................................................................... 129
8.5.3.1 PU Processing .......................................................................................................... 129
8.5.3.2 PU Use and Restrictions ........................................................................................... 129
8.5.3.3 PU Input/Response ................................................................................................... 129
8.5.3.4 PU Seat Changes ..................................................................................................... 132
8.5.4 Passenger Delete (PW)........................................................................................................... 133
8.5.4.1 PW Input ................................................................................................................... 133
8.5.4.2 PW Use and Restrictions .......................................................................................... 133
8.5.4.3 PW Input/Response .................................................................................................. 133
8.5.5 Standby Check-In (URES/NOREC/ID) .................................................................................... 140
8.5.5.1 URES Check-In ......................................................................................................... 140

Table of Contents
Page viii
8.5.5.2 NOREC Check-In ...................................................................................................... 140

8.5.5.3 ID Check-In ............................................................................................................... 140
8.5.6 URES and NOREC Passengers.............................................................................................. 141
8.5.6.1 URES ........................................................................................................................ 141
8.5.6.2 NOREC ..................................................................................................................... 141
8.5.6.3 Boarding Card Re-Issue (BC) ................................................................................... 141
8.5.7 Passenger Record Display (PDD) ........................................................................................... 142
8.5.7.1 PDD Input.................................................................................................................. 142
8.5.7.2 Restrictions ............................................................................................................... 142
8.5.7.3 Passenger Record Displays (PDD) ........................................................................... 143
8.5.8 Seat Map Display Input / Response ........................................................................................ 143
8.6. Extra Crew Check-In (XXXCREW) ..................................................................................................... 144
8.7. Dead Head Crew Check-In ................................................................................................................. 145
8.8. Unattached Baggage Check-In ........................................................................................................... 145
8.8.1 Check-In Unattached Bags...................................................................................................... 145
8.8.2 Display Unattached Bags ........................................................................................................ 146
8.8.3 Delete Unattached Bags.......................................................................................................... 147
8.8.4 Expedite Bag Tags .................................................................................................................. 147
8.9. Procedure to Delete or Change Onward Connections ........................................................................ 149
8.9.1 Before Check-In....................................................................................................................... 149
8.9.2 After Check-In.......................................................................................................................... 149
8.10. Passenger Notification (NO) ............................................................................................................... 150
8.11. Boarding Pass Issuance / Inhibit (BC) ................................................................................................ 151
8.12. Boarding Pass Inhibit .......................................................................................................................... 152
8.13. Excess Baggage (EXB) ...................................................................................................................... 152
8.14. Bag Tag Issuance (B) ......................................................................................................................... 154
8.14.1 PA Input / Response................................................................................................................ 154
8.14.2 PU Input / Response ............................................................................................................... 156
8.14.3 PW Input / Response............................................................................................................... 157
8.14.3.1 To Display Any Deleted Bag Tags in a Passengers Record..................................... 158
8.14.4 Bag Tag Subsequent Processing ............................................................................................ 160
8.14.5 Bag Tag JL List........................................................................................................................ 160
8.14.6 Baggage Action List (BAL) ...................................................................................................... 161
8.15. Passenger Update (PU) ...................................................................................................................... 162

Table of Contents
Page ix
8.16. Passenger Delete (PW) ...................................................................................................................... 165
9.
Staff Priority Table .....................................................................................................................169

9.1. Staff Priority Table Display (PZ).......................................................................................................... 169
10. Flight Destination / Remarks.....................................................................................................171

10.1. Flight Remarks Display (RK)............................................................................................................... 171
10.2. Destination Remarks Display (DR) ..................................................................................................... 171
11. Flight Default Assignment and Display ...................................................................................173

11.1. Flight Default Display (FDT)................................................................................................................ 173
12. Passenger Boarding Control ....................................................................................................175

12.1. Boarding Status Display (BSD) ........................................................................................................... 175
12.2. Boarding Acceptance by Boarding Number (BAB/BDB) ..................................................................... 176
12.3. Boarding Acceptance / Delete by Seat Number (BAS/BDS) ............................................................... 177
13. Glossary ......................................................................................................................................179

14. Index ............................................................................................................................................183

Table of Contents
Page x
List of Tables
Table 2.1 Sign in entry description ...................................................................................................... 4
Table 2.4 Sign In Error Response Descriptions..................................................................................5
Table 2.5 Agent-In Error Response Descriptions ............................................................................... 7
Table 2.6 Multiple Areas Response Descriptions............................................................................... 8
Table 2.7 Display Area Response Descriptions..................................................................................9
Table 2.8 Paging Command Descriptions .........................................................................................10
Table 2.8 Paging Command Descriptions .........................................................................................10
Table 2.9 Encode/Decode Benefits .................................................................................................... 11
Table 3.1 Check In Flight List Display Options to Limit Size of Display ........................................ 17
Table 3.2 Check In Flight List Display Options to used with Airline or ALL Entries.....................18
Table 3.3 CFL Display Field Descriptions.......................................................................................... 20
Table 3.4 Check In Equipment/Type Errors......................................................................................21
Table 4.1 Flight Data Display Field Descriptions (Master Flight) .................................................... 23
Table 4.2 Flight Data Display Field Descriptions (Active Flight).....................................................24
Table 5.1 Seat Map Viewing ................................................................................................................ 28
Table 5.2 Seat Map Viewing (Aisle) .................................................................................................... 28
Table 5.3 Seat Map Viewing (Special Usage Descriptors) ...............................................................29
Table 5.4 Seat Map Request Descriptions......................................................................................... 30
Table 6.1 Passenger Survey Display Response Explanation (Row 1)............................................ 34
Table 6.2 Passenger Survey Display Status Indicators ...................................................................34
Table 6.9 Passenger Survey Display Response Explanation (Row 10)..........................................37
Table 6.10 Passenger Survey Display Response Explanation (Row 11)........................................37
Table 6.11 Passenger Survey Display Response Explanation (Row 12)........................................38
List of Tables
Page xi
Table 6.12 Passenger Survey Display for Code share Flight with Multiple Partners.................... 39
Table 6.13 Passenger Survey Display for Code share Flight with Marketing Partner Only ......... 40
Table 7.1 Booked/Checked In Response Description ......................................................................44
Table 7.2 Booked/Checked In Display Code Descriptions ..............................................................47
Table 7.3 Passenger Display Request Descriptions ........................................................................48
Table 7.4 Response to Standby Description .....................................................................................50
Table 7.5 Need Notification Example Descriptions ..........................................................................51
Table 7.6 Standby Example Descriptions.......................................................................................... 51
Table 7.7 Passenger Record Code Descriptions ..............................................................................54
Table 8.1 Passenger Handling Transactions.....................................................................................59
Table 8.2 Gender Required Flight Titles ............................................................................................ 62
Table 8.3 Check In SSR and Information Codes ...............................................................................65
Table 8.5 Acceptable Travel Document Types..................................................................................80
Table 8.6 DOCS Entry Edits ................................................................................................................ 81
Table 8.7 DOCA Entry Edits ................................................................................................................ 85
Table 8.8 DOCO Entry Edits ................................................................................................................ 88
Table 8.9 Error Responses for UN Paxlist ......................................................................................... 93
Table 8.10 Passport Information at Check In Error Responses ...................................................... 94
Table 8.11 Passenger Update at Check In Error Responses...........................................................95
Table 8.12 Delete PSPT Remark Error Responses ...........................................................................96
Table 8.13 APP Query Responses....................................................................................................105
Table 8.14 ITCI Valid Seat Request Codes ......................................................................................128
Table 8.15 Valid Entries for a Boarding Card Re-issue..................................................................141
Table 8.16 Bag Tag Delete Error Responses...................................................................................159
Table 8.17 Bag Tag Number Explanation ........................................................................................160
Table 8.18 Baggage Action List Options (CITY Options)...............................................................161
Table 8.19 Baggage Action List Options (Address Options).........................................................161

List of Tables
Page xii
Revision History
Revision
Date
Changes
7.0.1
7.0.2
01 Apr 2008
Added DOCS, DOCA and DOCO Information at Check-In Time

information.
7.0.3
22 Apr 2008
Removed section on checking in passengers with passport

information.
7.1
30 Apr 2008
Customer release.
7.1.1
10 Jul 2008
Section 7 Passenger Displays New Booked/Checked-In with

Override (OVR) code added to Table 7.2.
7.1.2
08 Aug 2008
Section 8.4.2 URES Check-in, transaction for EXST with ETKT

processing for URES added.
Section 8.15 Passenger Update Example added, EXST with
TKNE for a passenger who has not yet checked in.
7.1.3
08 Aug 2008
Section 8.5.4.3 Example of E-Ticket passenger with EXST added.
7.2
29 Aug 2008
Customer release.

Revision History
Page i

Revision History
Page ii
1. Introduction
1.1. General Information
This training manual covers all the main SDCS check-in entries required for a check-in agent to carry
out their normal duties. For more advanced and control transactions please refer to the Check-in
Agent Supervisor User Guide manual.
1.2. Course Objective

This course is designed for Airline Passenger Check-in Agents. The course assumes that the agent
has some previous knowledge of either manual check-in or another computer check-in system.
The course offers the following primary objectives so each staff member can:
Understand the basic check-in entries and system responses.
Display or re-display any specific requested passenger lists.
Distinguish between NOREC and GO-SHOW passengers
Add any special passenger information to a passenger's record either before, during, or after
check-in.
Check-in standby passengers
Add staff ID and dates of joining
Issue boarding cards.
Have the confidence to give the best possible passenger service to the passenger as you check-in,
and supplement it with any specific seat or special passenger handling requests.

Introduction
Page 1

Introduction
Page 2
2. System Functions
2.1. Agent Control
Access to the SITA Departure Control Services system (the System) is by work stations and controlled
by three verification methods.
1. System-stored Workstation and agent information files.
2. A formal sign-in procedure.
3. User groups or Security Tables used to classify transactions.
Usually each staff is assigned one User Group appropriate for their daily work assignments. Staff may
be assigned more than one User Group to perform different tasks or duties. When you sign into a
Workstation and make an entry, the User Group authority is verified on each transaction.
User Groups / Security Tables:
Determine the level of authority on each agent entry.
Permit you to perform additional duties and is included as part of your sign-in entry.
Range from 11 to 144.
2.1.1
Workstation Information
Workstations are classified as either protected or unprotected. Protected workstations require the
inclusion of a personal account number and check letter during sign-in, whereas unprotected work
stations do not.
A workstation can be used by one staff or shared by up to five because it has five work areas (A, B, C,
D, E). Switching between work areas is possible. For example an agent may move from work area A
to D and then back to A without losing any information originally displayed in area A. Only one work
area may be physically in use, (active), at a time.
System control and security is provided by a formal sign-in code. To maintain system integrity, a
series of security checks are routinely performed during each sign-in.
Automatic system checks on the Workstation:
User group restrictions, if any.
Is the workstation restricted to one or more user groups?
City/office restrictions, if any.
Is the workstation restricted to only one city or multiple cities or all?
Dedicated use, if any.
Is the workstation set up for a specific application only, for example, Ticketing?
User airline identity, only valid for multiple user CRTs.

System Functions
Page 3
Agent Information
2.1.2
When an agent begins the sign-in entry, the system performs a series of security checks. The system
checks the information stored in the agent files and access is either granted or denied. Agent files
store all related agent information and the system uses this information to validate an agent's attempt
to sign-in. Agent files are built during the pre-implementation phase of SDCS. Usually the User File
Maintenance" group will coordinate the creation of these files.
Automatic system checks on the agent record are:
User airline identity
Agent number. Verifies agent number is valid.
Personal Account Number (Security Code). Validates account number against agent number.
User Group(s). Determines the transactions that are valid for the agent.
City/office restriction. Validates multiple city access.
Agent Sign-In
2.1.3
Sign-In establishes the relationship between an agent, the workstation and the system. A successful
Sign-In is the result of the entry data matching the stored data for both the workstation and the agent.
Entry:
SI:Agent File Number/Agent User Group Sign-in
SI:44/124/ATL501
(Unprotected sign-in)
Entry
Description
SI
The Function Designator for Sign-In is SI: (the colon ' : ' is optional). The SI is
always the first part of the sign-in entry.
44
Agent file number that tells the system who you are and what User Groups you may
use.
The slash is required.
AGENT
SIGN-IN
The agent sign-in fields follow:

124The user group specifies what type of transaction you will be using. This item is
only required if your agent record contains more than one user group.
/The slash is required.
ATL501Optional. This specifies the city and office you want to sign into. This is
usually established by the CRT as a default, but sometimes you may need to sign-in
for another city or office. This may be required of a control or help desk supervisor
assisting another airport's staff.
Table 2.1 Sign in entry description

Entry:
SI:44/25678A/124/ATL501
Entry
Description

System Functions
Page 4
SI
Function Designator.
Agent
Number
Includes the following:

/25678APersonal Account Number. The host airline may designate a CRT as
"protected" as an additional level of security. The Personal Account Number is your
authorization to work with a "Protected" CRT and is part of an Agent File. The
Personal Account Number consists of one to five numbers plus one letter. If the
code is typed incorrectly your entry into a "Protected" work-station is rejected.
/124User Group.
/ATL501City and office.

Entry:
SI:44/124/D/ATL501
Entry
Description
SI
Sign-In Function Designator.
44
Agent Number, including:

/124User Group.
/DAgent Area D of the CRT screen. Optional, default is the next available screen
area.
/ATL501City and office.

Error and Rejection Responses:
Response
Description
PROT SET
CRT is "Protected". A sign in entry must include a Personal Account Number.
CUSTOMER
NUMBER
Sign in entry/Customer Number in your agent file does not match the Customer
Number used in your sign in entry.
NO RECORD
No record of the agent number you have used in your sign in entry. You
probably have made a typing error.
USER GRP
User Group included with your sign in entry does not match the USER Group in
your agent file.
CITY
City included in your sign in entry is not allowed by the validation controls in your
agent record or the CRT's CONLNK record.
OFFICE
Office included in your sign in entry is not allowed by the validation controls in
your agent record or the CRT's CONLNK record.
FUNCTION
The Function Code received by the System was not intelligible. This can be due
to a typing error or because of interference and static on the circuit connection
from your CRT to the system. If your entry is correct and this continues to occur
you must report this as a communications problem to your local SITA office.
Table 2.4 Sign In Error Response Descriptions

System Functions
Page 5
2.1.4
Agent - Out (AO) Agent - In (AI)
The Agent-Out entry allows you to temporarily release control of the CRT to another agent or to
inactivate control of the screen for a short period of time, for example, to go for a break. You may also
want to go to another screen for information without having to erase the information on your original
screen. The information left on your screen is maintained in the area where you were signed in and is
available to you once you enter the Agent - In entry.
Entry:
AO
Response: Agent C - OUT or Letter of work area leaving AGENT-IN
Error Response:
SI
Indicates you are attempting to enter an Agent Out before signing in. The
Agent-in Entry re-establishes control over a CRT after an Agent-Out Entry
was entered and accepted. If the CRT screen is being shared, the Agent-In
entry performs an Agent-Out for the agent currently in control of the CRT.
The Agent-In entry allows you to return to an area of the CRT previously
being worked and the transaction last being worked.

System Functions
Page 6
Entry: Agent-In without a Personal Account Number:

AIA
Response:
AGENT A IN
Entry: Agent-In with a Personal Account Number:
AIA/44/25678A
The agent sign-in must accompany the Personal Account Number on Protected Sets.
Response:
AGENT A - IN
or if multiple areas of the CRT are signed-in.
AGENT B - OUT / A-IN
SYSTEM
PSA
ONLINE
Error Responses
Response
Description
FORMAT
Invalid agent or personal account number entered.
PROT SET
Security code/personal account number not entered.
SI
An "AI" was entered before you signed into the CRT.
Table 2.5 Agent-In Error Response Descriptions

System Functions
Page 7
2.1.5
Sign - Out (SO)
The Sign-Out (SO) entry ends your association with the current work area. If you are associated with
more than one work area only the current work area is signed out. You are then required to Agent-In
to your next work area before you could continue your sign out process.
If a CRT is left inactive for more than the number of minutes defined in User parameters, the CRT is
signed out. All incomplete transactions are ignored. All work areas must be signed out before leaving
the office.
Entry:
SO
Response:
ATL501
44 signed
out
If multiple areas of the CRT are signed in the response is:

XS
A
C
ATL501
44
44
44
1347
1737
Response
SIGNED
124
129
OUT B
ATL501
ATL501
Description
ATL501
City/Office.
44
Agent Number.
Area signed out.
44
Agent Number.
1602
Time of sign in (GMT).
124
User Group.
ATL501
City/Office.
Table 2.6 Multiple Areas Response Descriptions

Note: To sign out all areas with a single entry, enter XO.

System Functions
Page 8
2.1.6
Display Area (DA)
The Display Area function provides basic information about the current status of the various
workstation areas. The display shows which areas staff is signed-in and those available. The
response to the display also gives the Position Identifier (PID) number of the CRT and the hardcopy
printer device associated with the CRT.
Entry:
DA
Response:
A
AVAIL
B*
44
1222
124
C
AVAIL
D
106 1230
130
E
44
1223
124
PID = 735 HARDCOPY
SYSTEM ON-LINE
ATL501
ATL501
ATL501
= 136
Explanation of the Response:

Response
Description
A, B* 1, C, D, E
Agent Work Areas - Areas B, D, E Controls Computer A and C are Available for Sign-In. The agent is signed into B.
44, 106, 44
Agent Numbers (1-5 Digits).
1222, 1230, 1223
Time(s) of Sign-In (GMT).
124, 130,124
User Group Numbers.
ATL
City Code.
501
Office Code.
PID = 735
Identifying Number of the Computer.
HARDCOPY = 136
Identifying Number of the Printer.
SYSTEM ON-LINE
Signed into the On-Line System.
Table 2.7 Display Area Response Descriptions
* - Indicates that the Agent is working in B.

System Functions
Page 9
2.2. Paging
The paging system allows you to move within a display, when the display is more than one page, or
between displays using specific paging commands. Paging commands are easy to use.
Commands
Definition
Description
PF: or FP:
Page First or First

Page
Displays from the first line of the paged response to the

limits of the lines available on the screen or to the end of the
paged response (First page of the display).
PB: or LP:
Page Back or Last

Page (Previous)
Displays the lines previous to the current display to the limit

of lines available on the screen or to the start of the paged
response. Default is the redisplay of the current page
(Previous page).
PN: or NP:
Page Next or Next

Page
Displays lines following current display to the limits of lines

available on the screen or to the end of the paged response.
Default is the redisplay of the current page (Next page).
PL:
Page Last
Displays from the last line of the paged response to the

limits of lines available on the screen or to the start of the
paged response (Last page).
PG:
Page by Line
Re-displays current display or re-displays a specific number

of lines of the paged response, plus or minus, to the limits of
lines available on the screen or start of the paged response.
Clear Page
Clears the displays and associated page storage.
PG:+5 PG:-10
CP:
Table 2.8 Paging Command Descriptions
2.3. Paging within Multi-Page Displays

A multi-page display is identified by paging indicators. A plus (+) sign at the lower right of the screen
indicates more information is available by paging forward through the display. If no more pages follow,
a minus sign (-) is displayed to the right of the first line of the last page, indicating that more
information is available by paging backward.
2.4. Printing (PC/PT)

Print transactions provide you with the capability of printing display responses held in paging storage.
Paging commands provide control of print transactions to allow either the printing of the page currently
displayed or the entire response. Within the SDCS application there are also special commands for
printing certain DCS documents and messages. Examples include load sheets, boarding cards, bag
tags, passenger departure and LDP messages. These items are discussed in the appropriate
manuals.
Commands
Description
Definition
PC:
Print Current
Prints the Page currently displayed.
PT:
Print Total
Prints all pages at the level of the information currently displayed.
Table 2.8 Paging Command Descriptions

System Functions
Page 10
2.5. Encode/Decode (EX: / DX:)

The Encode/Decode function helps the staff obtain codes and names for cities, airports, airlines,
countries and currencies. Encode/Decode gathers this information and displays it in an easy to
understand format.
Encode/Decode helps you to quickly find information such as:
Information
Description
Airline
Name, code, IATA controlled code duplication and airline code share information.
City
Name, code, airports, heliports, state/province name and code, nation name and
code, local time and date, time difference from Greenwich Mean Time (GMT),
daylight savings observance period, and daylight savings time difference for the
Encode/Decode function helps the staff obtain codes and names for:
Cities
Airports
Airlines
Countries
Currencies
Encode/Decode gathers the information and displays it in a simple format.
Airport
Name and code, city code, state/province name and code, nation name and code,
local time and date, time difference from GMT, daylight savings observance period
and daylight savings time difference from GMT.
Country
Name, country code, and currency code for over 180 countries.
Table 2.9 Encode/Decode Benefits

Note: ENCODE - To convert an airline, country, city or airport name into its standard IATA or ISO
code and display the ISO currency code for a country.
DECODE - To convert a standard ISO country, IATA airline, IATA city/airport code into its full name
and display the ISO currency code for a country.
2.5.1
Encode Entry (EX:)
1. Entry: Encode the "Airline" Air Europa (this entry converts an airline name to code).
EX:A/AIREUROPA
Response:
EX:A/AIREUROPA
UX
* AIR EUROPA LINEAS AEREAS,S.A

System Functions
Page 11
2. Entry: Encode the "City" Madrid (this entry converts a city name to three letter code).
EX:C/MADRID
Response:
EX:C/MADRID
MAD
MADRID, SPAIN
1856/23MAR
Note: Airports are also shown.

3. Entry: Encode the City Madrid with "full" details (this entry converts city/airport name into threeletter code with GMT details).
EX:CF/MADRID
Response:
MAD
.ES
MADRID, SPAIN
1857/23MAR
GMT +01.0 DST EFF 0200 26MAR06-29OCT06 0200 DGMT +02.0
0200 25MAR07-28OCT07 0200
END
4. Entry: Encode the "Nation" Seychelles (this entry converts a country name to ISO country code and
currency code).
EX:N/SEYCHELLES
Response:
EX:N/SEYCHELLES
SC
SEYCHELLES, REPUBLIC OF
SCR
In this example the ISO Country code is (SC) and the ISO Currency code is (SCR).
2.5.2
Decode Transaction (DX:)
1. Entry: Decode the "Airline" code UX (this entry decodes an airlines two letter code).
DX:A/UX
Response:
DX:A/UX
UX
*
AIR EUROPA LINEAS AEREAS,S.A
The asterisk (*) indicates Air Europa shares the operation of some flights.
To see what carriers share operations with UX enter the following entry:

System Functions
Page 12
2. Entry:
DX:AF/UX
(This entry shows code share agreement flights).
Response:
DX:AF/UX
UX
* AIR EUROPA LINEAS AEREAS,S.A
* ADDR CTRA ARENAL-LLUCMAJOR KM21.5 POLIGONO SON NOGUERA
* ADR2 07620 LLUCMAJOR, SPAIN
* TEXT CAT. I - PRIMARY CODE HOLDER
* IATA 996
SHARE
UX 017
CO 063 - CONTINENTAL AIRLINES INC.
UX 018
CO 062 - CONTINENTAL AIRLINES INC.
UX 3001-3004 AF
- AIR FRANCE
UX 3011-3018 AF
- AIR FRANCE
UX 3021-3023 AF
- AIR FRANCE
UX 3024 CDG 15MAR06-25MAR06 X7
AF 5578 - AIR FRANCE
UX 3024 CDG 27MAR06-28OCT06 X7
AF
- AIR FRANCE
UX 3025-3026 AF
- AIR FRANCE
UX 3031-3032 AF
- AIR FRANCE
UX 3036
UX 3037
UX 3038
UX 3039
UX 3041-3042 AF
- AIR FRANCE
UX 3051
CU 471 - CUBANA DE AVIACION
UX 3052
CU 470 - CUBANA DE AVIACION
Note: Both the Airline's address and IATA accounting code are shown.
3. Entry: Decode the "City" code MAD (this entry converts the three-letter city code into the name of a
city).
DX:C/MAD
Response:
DX:C/MAD
MAD
MADRID, SPAIN
1903/23MAR
Entry: Decode the "City" code MOW with "full" details.

DX:CF/MAD
Response:
DX:CF/MAD
MAD
MADRID, SPAIN
1904/23MAR
.ES
GMT +01.0 DST EFF 0200 26MAR06-29OCT06 0200 DGMT +02.0
0200 25MAR07-28OCT07 0200
END

System Functions
Page 13
4. Entry: Decode the "Nation" code SC (this entry converts the two letter ISO code of a country to the
name of the country).
DX:N/SC
Response:
DX:N/SC
SC
SEYCHELLES, REPUBLIC OF
2.5.3
SCR
Time Calculation (TCC:)
1. Entry: Calculate the present time between LLW - Lilongwe and ADD - Addis Ababa.
TCC:LLWADD
Response:
TCC:LLWADD
LLW.... 1635/23DEC
GMT +02.0
+01.0 HOURS DIFFERENCE
ADD.... 1735/23DEC
GMT +03.0
DISTANCE 1623 M
2612 K
Time Conversion
2. Entry: Calculate the time in LLW for today if the current time in ATL is 1800 GMT.
TCC:ATL 1800/. LLW
TCC:ATL1800/23DECLLW
Response:
TCC:ATL1800/. LLW
ATL.... 1800/23DEC
GMT -05.0
+07.0 HOURS DIFFERENCE
LLW.... 0100/24DEC
GMT +02.0
DISTANCE 8354 M 13445 K

System Functions
Page 14
2.6. SITA Help Facility

Many of the Function Designators have been entered into Help. If an agent knows the Function
Designator they can display a description and example of the transaction.
1. Entry: Type the known Function Designator and a question mark (?).
FDD:?
Response:
HELP:/PN
SITA (XS) HELP FACILITY
Last Update
FUNCTION-CODES/FDC-FLT-DATA-CTL/FDD/FDD 2/10/532/1
Function: FDD:
Application: FDC
Description: FDD: is used to display flight schedule information
for all flights built by data load.
Restriction:
22 May 00
The first page provides details of the application and use of the transaction and the second or
subsequent pages for examples may be displayed by placing the cursor after the PN (page next) and
pressing the transmit key. The next page will appear.
HELP:/PN
= Transmit after the PN
Response of Second Page
HELP:/PN
Last Update
22 May
00
Entry:
FDD:HA700/05AUG
Explanation of The Entry:
FDD:
= (M) Function Code
HA700 = (M) Airline/Flight Number
05AUG = (M) Date
** END **

System Functions
Page 15
2. Entry:
PA?
Response:
HELP:/PN
Last Update
22 May 00
FUNCTION-CODES/CKI-CHECK-IN/PA/PA 2/4/484/1
Function: PA:
Application: CKI
+
HELP FACILITY
Description: PA: (Passenger Acceptance) is used to 1) accept or
place a passenger on standby when they check-in,
2) recheck passengers if they haven't checked-in
on the first flight or 3) reserve seats or add
items for not present, not checked-in passengers.
Restriction: 1) After initial close, PA: can only be done at the gate.
2) After final close, PA: is restricted to rechecking passengers at the
gate.
Note: It is optional for two-letter function codes to include the colon (:) (for example, PA:? or PA?) but
the colon is mandatory for three letter designators.

System Functions
Page 16
3. Daily Flight List Display

3.1. Check-In Flight List Display (CFL)
The CFL transaction allows an agent to display a list of flights either departing, arriving, or transiting a
specific airport. It can also display all flights operating over a specific flight segment on a given date.
The entry is:
CFL:AIRLINE/DATE/AIRPORT(SPECIFIC SEGMENTS)/OPTION
A space can be substituted for a slash as a field separator throughout the CFL input.
1
CFL:XS/./DACLHR/S
CFL:XS/./DAC
The airport entered in the CFL transaction can be anywhere on a flight route, including the destination.
If no airport is input, the system defaults to the airport shown in the agents sign in (VDU airport).
When a city pair (segment) is input, both cities must be on the flight route for the flight to display.
It is possible just to enter CFL: as the system defaults to the Host Airline, today's date, and the airport
of the CRT sign in (VDU airport).
Formats
There are two different CFL response formats.
1. The /S option displays flights with all available segment information.
2. Omitting the /S option displays a shorter format having flight numbers only.
Options
Options exist to limit the size of a display and return only needed information.
Option
Description
Flights linked to reservations.
All available SEGMENT information and determines the format of the display.
All OPEN flights.
All CLOSED flights.
All Initialized flights.
All training flights.
All Uninitialized flights.
All Arriving flights.
All Departing flights.
Table 3.1 Check In Flight List Display Options to Limit Size of Display
The CFL transaction can be entered for an airline or all airlines in the Host's SITA Departure Control
Service. All airlines are specified by a code of ALL instead of an airline code. Where the airline code
is omitted, the output is for the host airline.
When a city, city pair (segment) or the following options are entered in a transaction the airline or the
designator ALL must be entered.
ALLList of all Airlines and flights handled by the Host carrier.
Daily Flight List Display
Page 17
Entry:
CFL:AIRLINE/CITY/ OPTION
CFL:ALL/OPTION
Example:
CFL:XS/MIA/I
CFL:ALL/CN
Option
Description
CN
All Cancelled flights.
CL
All SDCS-LDP closed flights.
DI
All Deferred initialized flights.
FD
All flights automatically created from SITA DCS schedules (FDC).
II
All immediate initialization.
MB
All Manually created flights for check-in.
NC
All non-cancelled flights.
NT
All non-training flights.
CL
All flights Closed for Load Planning.
DI
All flights with Deferred initialization.
Table 3.2 Check In Flight List Display Options to used with Airline or ALL Entries
Note: It is possible to request more than one option at the same time but the transaction will be
rejected if the requested options conflict. For instance you cannot request C with O or I with N.
1 CFL Examples
Response to CFL:O (List of all flights open for check-in)
FLIGHT RECORD LISTINGS: XS ** SITA AIRLINE************************
XS259
XS267 XS301
XS456
XS472 XS488 XS490 XS499 XS501 XS544
XS636
XS677 XS685 XS704 XS723 XS737 XS782
XS810
XS820 XS830 XS866 XS923 XS945 XS967
XS1001
XS1007 XS9999
04JUN

Page 18
Response to CFL:C (List of all Closed flights)

CFL:C
CFL:C
FLIGHT RECORD LISTINGS: XS
08OCT
XS090
XS091
XS200
XS215
XS340
XS452
XS486
** SITA
*********************************
Response to CFL:airline/CN (List for all cancelled flights needs airline or ALL)
CFL:XS/CN
XS090
XS200
XS340
Response To CFL:S Entry Where AAA is Default City
CFL:S
FLIGHT RECORD LISTINGS: XS ** SITA AIRLINES *********** 15NOV
XS100 ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0700
0630
CC
67
23
C10M43
737/A
ALP
0910
EQUIP
AAA
0700
0630
CC
45
27
C8M43
734/A
FRA
0915
XS778
ARRIVES DEPARTS BOARDS STAT POS GATE BKD
EQUIP
AAA
0700
0630
OPEN GATE ???? C0Y50
340/B
ATL
0900
1020
0940
OPEN GATE ???? C0Y145
340/A
SJU
1310
XS520
ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0730
0700
CC
74
28
C4M18
CRJ/CRJI
DOH
0900
EQUIP
AAA
0730
0700
CC
78
21
C2M12
734/AGD
MUC
0850
XS490 ARRIVES DEPARTS BOARDS STAT POS GATE BKD
EQUIP
AAA
1130
1100
NINT GATE ????
762/A
JFK
2125
+
TYPE
NAM
TYPE
NAM
TYPE
NAM
NAM
TYPE
NAM
TYPE
NAM
TYPE
NAM
Note: The flights are displayed in TIME order based on the default city or origin city of a segment. It
is also possible to display the list from a particular input time (Example: CFL:S/1800).
An X before the City Code indicates that the flight is cancelled.
1 Example and Explanation of CFL:S Display

XS5100 ARRIVES
TYPE
ATL P
NAM
JFK P
0300
1
2
3
11
DEPARTS
BOARDS
STAT
POS
GATES
BKD
EQUIP
0010
2340
NINT
GATE
B17
F06Y168
767/A
10

Page 19
Explanation:
Field
Description
Flight number and routing (Shows originating station on transit flights).
P means flight is under PROTECTIVE COVER.
Arrival time in local time (E = Estimated arrival time).
Departure time in local time (A = Actual [E = Estimated] departure time).
Aircraft passenger boarding time.
Status of flight. The following status displays are possible:

OPEN Flight is open for passenger check-in.
LOCKFlight is under emergency lock.
HOLD Flight out of the airport is on hold.
CICheck-in initially closed for flight.
CCCheck-in finally closed for flight.
CANCAirport is cancelled for this flight.
RSOM SOM has been requested but not received.
TCL Airport is technical landing only.
PNLR PNL has been requested but not received.
NINT Flight has not yet been initialized for check-in.
Aircraft ramp/apron position at this airport.
Passenger boarding gate number at this airport.
CKDNumber of passengers checked in shown once the flight has been released.
BKDNumber of passengers booked is shown while the flight is open.
10
Aircraft type and version on this segment.
11
Type of check-in out of this airport. It is possible to display the following types:
NAMPassenger name check-in from a PNL.
NUMNumeric check-in.
PNMPartial name check-in for passengers with special requests only.
NONNon SITA DCS check-in. (Manual check-in)
TCLTechnical landing, no check-in allowed.
Table 3.3 CFL Display Field Descriptions

BKD shows the passenger bookings while the flight is open for check-in. CKD shows after the flight
release and (CC) indicates the number of passengers checked in.
Note: For Multi-sector flights the heading 'BKD' displays until the last sector of the flight is released.
Even though 'BKD' is displayed on all segments that are released, the figures displayed as booked
'BKD' will be the final checked-in figures on those segments. Once the flight is released on the final
segment, 'BKD' changes to 'CKD'.
Page 20
When a schedule is built, the default type of Check-In is NAM. If the Control Agent does not change
the NAM to NON for non-mechanized stations the PNL will not process because the system is waiting
on the additional PNLs from the reservation system. The CFL: display allows you to catch errors early.
Error
EQUIP
Correct
TYPE
EQUIP
TYPE
TU5/C3
NAM
TU5/C3
NAM
TU5/C3
NAM
TU5/C3
NON
TU5/C3
NAM
TU5/C3
NON
Table 3.4 Check In Equipment/Type Errors
1 Example of Entry CFL:O/S (All Open Flights with Segment Information).

FLIGHT RECORD LISTINGS: XS ** XS ************************
MCN
2100
2030
NINT GATE ????
ATL
2130
2220
2150
NINT GATE ????
JFK
2355
ATL
2300
2230
NINT GATE ????
MIA
2330
XATL
2300
2230
OPEN GATE ????
XMIA
2330
ATL
2300
2230
NINT GATE ????
MIA
2330
ATL
2300
2230
NINT GATE ????
DCA
2330
ATL
2300
2230
NINT GATE ????
MIA
2350
ATL
2300
2230
NINT GATE ????
MIA
2315
2330
2300
NINT GATE ????
04JUN
737/73S
737/73S
NAM
NAM
EQUIP
737/DF
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
DH8/C
TYPE
NAM
NAM +
No Segment Information
The CFL:S entry may display flight numbers with the response '**NO SEGMENT INFO**'. When this
occurs, there are two possible reasons.
1. The flight has been created with a "D" option and the system will not give the segment information
until the flight is initialized.
2. When the flights are created with a "K" option, the segment should display the segment
information. When it does not, check to see if everything is correct with the seat map and
configuration.

Page 21
1 Example of '**NO SEGMENT INFO**' Response with CFL:S Entry

FLIGHT RECORD LISTINGS: XS
14OCT
* XS206
** NO SEGMENT INFO
* XS211
** NO SEGMENT INFO
* XS224
** NO SEGMENT INFO
* XS326
** NO SEGMENT INFO
** SITA
*********************************
**
**
**
**
A flight schedule may be activated for five days - today plus four consecutive future days. Activation is
part of a nightly maintenance program run by the system. In the example below, a Flight Period
Display shows a schedule is built for a flight from 23 June on till infinity. This transaction is used only
by a DCS Database Specialist but shows that the flight schedule has not been activated for XS206.
Data Base Restricted Entry Shows the Flight Is Not Activated
FPD:206
FPD:XS 0206
->> MASTER PERIODS:
FDD:XS 0206 /23JUN98/MF
->> ACTIVE DATES:
00XXX00 D
If a Check-In Agent enters the transaction to display a seat map the flight is activated normally if the
schedule conflict is corrected. The flight will then appear correctly on the CFL display.
1 Example of Flight Activation When A Seat Map Is Displayed.

SE206/.
CKI TIME 1213
When there is a conflict with the DCS schedule a warning response is displayed after a seat map is
requested. In the example below a warning response, "AIRCRAFT" is returned. This means there is
no seat map to match the type and version of aircraft used in the schedule. The Supervisor or DCS
Database Specialist must be contacted to correct the problem.
Reason Response Preventing Flight Activation with Seat Map Display.
SE206/.
129 - AIRCRAFT

Page 22
4. Flight Information Displays and Updates

4.1. Flight Data Display (FDD)
The entry for a flight data display may be made for any flight created by a schedule entry (BF:T:) or
(DFD:). It either displays a Master flight (with a date range) or an Active flight (one date only),
depending on the date entered. The basic information displayed, apart from the flight number and
date, is:
routing
departure and arrival times (in local time) (T)
CND table number (for configuration)
Aircraft type and version.
1 Example of a Master Flight (FDD:XS587/15MAR)

XS587 11FEB05
1410
1635
ATL
JFK
- 23MAR05
156
T-32
--MASTER-737/A
IRREGULAR OPERATION DETAILS

SUPPLEMENTAL INFORMATION
Field
Description
XS587
Flight Number.
11FEB05 23MAR05
Date Range.
156
Flight frequency:
There are various ways of specifying the frequency as follows:
D - Daily (everyday of the week)
1 - Monday (2 = Tuesday, 3 = Wednesday, 4 = Thursday,
5 = Friday, 6 = Saturday, 7 = Sunday) This flight will operate on Monday, Friday and
Saturday.
ATL
Originating Station (with departure time of 1410). Copied from schedule.
JFK
Next or Final Station (with arrival time of 1635). Copied from schedule.
T-32
CND Table Number for aircraft configuration. Copied from schedule. Can also show
RBD configuration if the schedule was created by SITA Reservations.
737/A
Aircraft Type and Version. Copied from schedule.
Table 4.1 Flight Data Display Field Descriptions (Master Flight)

Flight Information Displays and Updates
Page 23
1 Example of an Active Flight (FDD:XS587/.)

ATL
JFK
XS587 14FEB06
ADJ 1510
ETA 1735
--ACTIVE-1/00 LATE
1/00 LATE
T-32
737/A
R:G-LMWP
IRREGULAR OPERATION DETAILS

ATL SURFACE WINDS
WINDS EXPECTED TO CALM BY 2100GMT
Field
Description
ADJ 1510 / ETA 1735
Time adjustment from FIR, FUI or LMVD transaction.
1/00 LATE
Hours and minutes of schedule adjustment from FIR or FUI

transaction.
R:G-LMWP
Aircraft registration number. Entered via FUI: transaction FDD.
IRREGULAR OPERATION
DETAILS
Location and reason for schedule adjustment. Use the FIR transaction to enter the delay codes.
A Supervisor or Operations Agent will update the FDD
information.
Detailed reason for a delay or details on the protection of

passengers off a cancelled or delayed fight. Entered via FIR
transaction.
Table 4.2 Flight Data Display Field Descriptions (Active Flight)
1 Example of an Active Code share Flight (FDD:XS130/.)

FDD:600/.
***CODE SHARE***SN5144
FDDMA 600 /05APR06
MA 600 05APR06
BUD
0625
BRU
0825
X67
--ACTIVE-20
71
T-518
73G/73GBBR:HALOR
Explanation:
***CODE SHARE***SN5144
Indicates marketing partner and marketing flight number

code sharing with operating flight.
Note: Code share flights now allow up to nine marketing partners between SDCS users and partners.

Page 24
4.2. Mode of Update

The Flight Data Display is updated from the following entries:
Flight Update Information (FUI:).
Flight Irregular Operations (FIR:)
Movement Message (MVT) entered with the LMVD: transaction.

Page 25

Page 26
5. Seat Map Display

5.1. Seat Map (SE)
Any agent can display the seat map for a seat assignment flight.
The entries can include:
SE:FLIGHT NUMBER / DATE
SE:FLIGHT NUMBER CLASS
SE:FLIGHT /SEGMENT
SE:FLIGHT NUMBER/DATE CLASS SEGMENT
1
SE:XS835/17JUN
SE:XS835Y
SE:XS835/ATLMIA
SE:XS835/17JUN Y ATLMIA
Response to SE:835/. Transaction
SE:XS835/17JUN06/ATLMIA
737/A
SE:XS835/17JUN06/MIASJU
F
Y
1 2
3
RF T *
F
F
.
RE T *
E
E
.
RD * V D
D
.
R
= S
=
L
LC
LB
LA
F
:
.
+
.
1
S
*
*
V
2
C
B
A
C
B
A
Y
=
H
R
R
3
4
*
*
*
=
5
T
*
T
=
=
*
*
*
4
=
*
T
T
5
[
6
*
*
*
=
[
7
=
*
*
*
6
[
=
L
L
L
L
=
7
[
[
8
*
*
*
=
[
9
P
P
*
=
1
0
*
*
*
=
[
1
T
T
*
=
[
2
*
*
*
=
=
*
*
*
8
[
=
*
*
*
9
[
=
*
*
P
0
1
=
*
.
.
1
[
=
*
*
T
2
[
3
.
*
.
S
4
.
.
*
S
5
.
*
*
S
6
*
*
*
S
7
*
*
*
S
8
/
/
/
S
S
.
*
T
3
S
*
*
.
4
S
*
*
*
5
S
.
R
R
6
S
R
R
*
7
S
/
/
/
8
FR
ER
DR
R
L
CL
BL
AL
Note: When there is an aircraft change in the route, the default segment is displayed first. The
second segment allows the seat map display for the second aircraft on the flight.

Seat Map Display
Page 27
5.2. Viewing the Seat Map

The Seat Map is viewed as if you are looking down from the left side of the aircraft. The front of the
aircraft is on the agent's left and the rear is on the right.
Code
Definition
RIGHT side of aircraft.
FY
Classes of service
LEFT side of aircraft.
Seat over looking aircraft WING.
+/-
Indicates the seat map has additional rows, press Page Up and Page Down to scroll through
the additional sections of the seat map.
Table 5.1 Seat Map Viewing

The various codes that can be displayed on the aisle of the seat map are:
Code
Definition
Indicates AISLE.
Indicates that an infant is seated on that side of the row on the aircraft.
SMOKING row.
Table 5.2 Seat Map Viewing (Aisle)

The various Special Usage Descriptors (SUDs) that can be displayed on the seat map are:
SUD
Description
Occupied seat (Checked-in passenger).
Available seat for check-in.
Available Restricted Recline seat.
Courtesy seat for Infant or ADSR.
Allotted seat available for check-in this segment.
Available bassinet seat for Infant.
Last to be used available seat.
Handicap seat.
Emergency exit seat.
Seats reserved for group by RS transaction.
Available Bulkhead seat.
Infant seat.
Seat Map Display
Page 28
SUD
Description
Stretcher seats (Designated on EQC: but only appears if .R/STCR is on PNL).
Available Extra Leg room seats.
Available Restricted Film view seat.
Allotted seat not available for check-in this segment.
Seat reserved by CRS (check-in editing) for passengers not checked-in.
Seat automatically reserved for passenger by RES from PNL or ASR on ADL after flight
initialization.
Occupied by Transit passenger (Manual check-in Up line Station only - otherwise shows as a
'.' for Thru-checked-in passengers from an automated Up line Station).
Available seats for Unaccompanied Minor.
Seat automatically reserved for passenger by ASR from PNL.
Blocked seat (unusable).
Table 5.3 Seat Map Viewing (Special Usage Descriptors)

Note: A seat can have multiple SUDs assigned, the seat map displays the most restrictive SUD.
The master seat map may be built with any number of SUDs. Additional SUDs may be added or
removed on an active flight by the Supervisor using the SCC: transaction.

Seat Map Display
Page 29
At check-in it is possible for agents to request specific area seating. The letter R notifies the system a
Request for a specific area on the aircraft is being made.
1 Examples would be:

Code
Description
RS
Smoking seat
RN
Non Smoking seat
RW
Window seat
RSW
Smoking Window seat
REW
Emergency Exit Window seat
RI
Aisle seat
RSI
Smoking Aisle seat
RF
Forward seat
RA
Aft seat
Table 5.4 Seat Map Request Descriptions

Passenger Acceptance (PA) Check-In entries are in Section 9.
1 Example of a seat map on a code share flight SE:XS130/.

SE:XS130/.
***CODE SHARE***YY029
SE:XS130/30SEP06/ ATLJFK
C
M
1 1
2
123456
7890124567890123456
RF ****** F F ***EE**************
RE ****** E E ***EE**************
RD ****** D D ***EE**************
R =====S
================SSS
L =====S
================SSS
LC ****** C C ***EE**************
LB ****** B B ***EE**************
LA ****** A A ***EE**************
123456
7890124567890123456
C
M
1 1
2
320/R
FR
ER
DR
R
L
CL
BL
AL
Indicates marketing partner and marketing flight numbers code sharing

with the operating flight.
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
Note: Seats may have multiple Special Usage Descriptors (SUDs) assigned. The seat map displays
the most restrictive SUD assigned to the seat. Seats with multiple SUDs will display the less restrictive
SUD when a more restrictive SUD is removed from a seat.

Seat Map Display
Page 30
5.3. Aircraft Compartment Limits /Control Messages

Explicit limits may be specified in the database seat map for a class or service or the aircraft. These
limits can be for passengers, aircraft weight, infants and kennels. The jump seat (JMP) defaults to
none so if jump seats are allowed they must be specified on the database seat map. Otherwise a JMP
cannot be checked in.
The number of designated seats (SUDs) on a seat map for infants, wheelchairs/deaf/blind and
stretchers also limit the acceptance of passengers.
Control messages are sent to the addresses specified for the check-in control office of a boarding
airport if capacities are approached or reached during a flights check-in. The addresses are normally
a printer in the Check-in control office or on the check-in counter. Control messages are also attached
to a passenger's check-in record. The passenger is added to the standby list and has a three-letter
code to specify why they were not accepted. The three-letter codes are described in Table 7.6
Standby Example Descriptions
Individual Passenger Record Display (PDD), Section 7. The flight check-in control messages are of
two types: limit warnings and limit advice. The warnings are sent when a capacity is approached. The
advice is sent when a capacity is reached. The SDCS Database User Guide Section 9.4 describes
warning message addresses.
5.4. Seat Map Use

Each seat map appearing on a flight has a master seat map in the SDCS database. If a master seat
map is deleted or has not been built the flight schedule will not be activated and passengers cannot be
checked-in. Every type of aircraft configuration must have a seat map or a file built for the aircraft
configuration to show no seat map is required.
To plan the seating assignments on a flight, check-in and supervisory staff can use the Seat Map
display (SE). The seat map display always appears from the city of sign in to the next city. To display
a seat map to a second or third destination the city pair must be added to the entry. If a flight schedule
was from ATL JFK LHR and the agent wished to see the ATL LHR seat map the entry would be
SE194/.ATLLHR.

Seat Map Display
Page 31

Seat Map Display
Page 32
6. Passenger Survey Display

6.1. Passenger Survey Display (SDD)
Any authorized agent can display the SDD screen, which gives relevant information such as:
schedule departure time
aircraft type
gate number
boarding time
passenger configuration
capacity
Booking details.
The SDD screen controls the acceptance of GO-SHOW passengers and ID passengers. The display
also provides a total of passengers checked-in for a flight, and by individual segment for multi-sector
flights.
The entry is:
SDD:FLIGHT NUMBER/DATE
1
SDD:XS835/.
Note: Class code is not entered.
Response to SDD:XS835/.
1. SDD: XS835/23SEP ATL/1
OP/NAM
2. CWT015000 UWT014885 CAW014406 UAW013281 WTN1 KG TCI
3. 737/a
GTD/G17 POS/GATE BDT1730 SD1800 ED1830
AK07125 CD09127
4. ARN/A1234-AA
CNF/F12Y94 CAP/F12Y94 AV/F12Y81 PADC/C0M0
5. FLIGHT DELAY DUE TO LATE CATERING
6. *ATLMIA R0004/0069 C0000/013
B0013 UM000 WCH00 I00
7.
SB0000/003 B0003
STCR00 PETC00 AVIH00 J00
8.
SA0000/004
EXST00/00 XCR00/00 DHC00/00
9. *ONLY ALLOW ONE PIECE OF HANDLUGGAGE PER PERSON ONBOARD*
10. SX
ATLMIA/F2
11. HL
ATLMIA/Y90
12.
GS
ID
ATL 003/015
001/005

Passenger Survey Display
Page 33
Explanation:
Row 1.
Entry
Explanation
SDD
Transaction entry code.
XS835/.
Flight number/date.
ATL1
City and message address table (CX) number (Range 0 - 99).
OP
Flight is open for check-in.
Table 6.1 Passenger Survey Display Response Explanation (Row 1)

Other status indicators are:
Status Indicator
Explanation
OG
Open for check-in at Gate only.
OE
Open for check-in but AEC passengers need re-seating.
CI
Check-in Initial Close.
CE
Initial Close but AEC passengers need re-seating.
EC
Flight under AEC Protective Cover.
CL
Check-in Closed and released to LDP.
CC
Check-in Completely Closed and Messages dispatched.
PC
Flight under Protective Cover.
XX
Flight Cancelled.
NAM
Flight is name check-in. Other types of check-in are:

NUMFlight is Numeric check-in (no PNL).
PNMFlight Partial Name check-in (same as numeric except passengers with
special requirements displayed in system).
NONNon-Automated station for SITA DCS.
Table 6.2 Passenger Survey Display Status Indicators

Row 2.
Status Indicator
Explanation
CWT
Check-in weight allowance (comes from the CSM and system calculates it using
the average passenger weight from CW).
UWT
Amount under check-in weight allowance.
UWT-
Amount over check-in weight allowance.
CAW
Load planning weight allowance (only comes across to CKI once the estimated
baggage figures are created in LDP).

Page 34
Status Indicator
Explanation
UAW
Amount under load planning weight allowance.
UAW-
Amount over load planning weight allowance.
WTN1
Passenger check-in weight table number used (maximum nine tables).
KG
Weight in kilograms (can also be LB for pounds).
TCI
All feeder and through transfer check-in allowed.

Row 3.
Status Indicator
Explanation
737/A
Aircraft type and version.
GTD
Passenger gate number.
POS
Ramp position that is used fro a Bus Gate.
BDT
Passenger boarding time.
SD
Scheduled time of departure.
ED
Estimated time of departure.
AK
Flight supervisory agent or phone number.
CD
Flight control PID number.

Page 35
Row 4.
Status Indicator
Explanation
ARN
Aircraft registration number.
CNF
Seating configuration of aircraft.
CAP
Seating capacity available on this flight.
AV
Available remaining seats including pre-assigned.
PADC
PAD accepted for flight by class group.

Row 5.
Free format remarks for this flight only.
Row 6.
Status Indicator
Explanation
ATL/MIA
Flight segment.
Booked figures from reservations.

Note: An * before a segment indicates that the segment is available for check in.
An X before a segment indicates that the departure city is cancelled on the flight.
Checked-in passengers.
Number of bags for checked-in passengers.
UM
Number of unaccompanied minors checked-in on flight.
WCH
Number of wheelchair passengers checked-in on flight.
Number of infants checked-in on flight.

Page 36
Row 7.
Status Indicator
Explanation
SB
Number of standbys on the flight.
Number of bags associated with the standby passengers.
STCR
Number of stretcher passengers checked-in on the flight.
PETC
Number of Pet animals checked into the cabin.
AVIH
Number of Pet animals checked into the holds.
Accepted cabin jump seat passengers.

Row 8.
Status Indicator
Explanation
SA
Number of space available (PAD) passengers listed on the PNL.
EXST
Number of Extra Seats occupied on the flight.
XCR
Number of Extra Crew checked-in for the flight.
DHC
Deadhead Crew.

Row 9.
Free format remarks for a specific destination.
Row 10.
Status Indicator
SX
Explanation
Seating restriction.

Row 11.
Status Indicator
HL
Explanation
Numeric limit by class for passenger acceptance, and only displays when set.

Page 37
Row 12.
Status Indicator
Explanation
GS
Number of seats available by class for GO-SHOW (URES) passengers. If it is zero

then these passengers are put on standby at check-in at the departure station.
ID
Number of seats available by class for PAD (ID) passengers. If it is zero then
these passengers are put on standby at the departure station.
6.2. SDD with a Zone Entry

The following is an example of an SDD using a Z entry. The SDD FLT NBR/.,Z allows a user to see
checked-in passengers seated by Zones. The Z entry works when the flight is connected to Load
Planning. The Cargo Screen in LDP must be transmitted before the SDD can be displayed.
1 Example of SDD with a Z Entry for Passengers Seated by Zone:

SDD: XS835/23SEP ATL/0
OP/NAM
CWT0262143 UWT261528 CAW031918 UAW031303 WTN1 KG TCI
767/a
GTD/G17 POS/GATE BDT1930 SD2000 ED2000
AK00000 CD00000
ARN/G-767 CNF/F12C63Y126 CAP/F12C63Y126 AV/F12C62Y122 PADC/F0C0Y0
ZONES 0A/001 OB/001 0C/004
*ATLMIA R0008/0008/0046 C0001/0001/0004
B0018 UM000 WCH01 I00
SB0000/003 B0003
SA0000/0000/0000
EXST00/00/00 XCR00/00/00
DHC00/00/00
*TEST FLIGHT ONLY*
.
GS
ID
ATL 000/000/000
000/000/000

Page 38
6.3. SDD for Code share Flights

The following is an example of an SDD involving an operating carrier with multiple code share
partners:
1 Example of SDD for Code share Flight with Multiple Partners:

sdd:XS084/.
***CODE SHARE***YY9084 ZZ2684 BB9984 **JFK C004 M000
SDD: XS084/05NOV JFK/0 OP/NAM
734/A GTD/???? POS/GATE BDT2130 SD2200 ED2200
AK00000 CD00000
ARN/ CNF/C15M125 CAP/C15MH125 AV/C10MH125 PADC/C0M0
*ATLJFK R0012/0039 C0004/0003
B0003 UM000 WCH00 I01
SB0000/0000 B0000
SA0000/0000
EXST01/00 XCR00/00 DHC00/00
GS
ID
ATL 000/000/000
000/000/000
Explanation:
Field
Description
***CODESHARE ****YY9084
ZZ2684 BB9984
Indicates marketing partners and marketing flight numbers code

sharing with the operating flight.
JFK C004 M000
Indicates the destination city followed by the number of marketing

passengers checked-in for each class.
Table 6.12 Passenger Survey Display for Code share Flight with Multiple Partners

Page 39
The SDD can also be displayed for a marketing carrier only.
1 Example of SDD for Code share Flights of Marketing Partner Only:

SDD:BB9984/.
***CODE SHARE***ZZ2684 **ATL C001 M000
SDD: XS084/05NOV JFK/0 OP/NAM
734/A GTD/???? POS/GATE BDT2130 SD2200 ED2200
AK00000 CD00000
ARN/ CNF/C15M125 CAP/C15MH125 AV/C10MH125 PADC/C0M0
*ATLJFK R0012/0039 C0004/0000
B0003 UM000 WCH00 I01
SB0000/0000 B0000
SA0000/0000
EXST01/00 XCR00/00 DHC00/00
GS
ID
ATL 000/000/000
000/000/000
Field
Description
***CODE SHARE**** ZZ2684
Indicates the marketing partner of a Code share flight XS084.
ATL C001 M000
Indicates the boarding city and the number of passengers

checked-in on marketing flight ZZ2684.
Table 6.13 Passenger Survey Display for Code share Flight with Marketing Partner Only
partners.

Page 40
6.4. SDD for an Overweight Flight

A flight can accept passengers when it is overweight provided the parameters are set to do so. The
following is an example of an SDD when an aircraft is overweight but parameters are set to continue to
accept passengers:
1 Example of an SDD for an Overweight Flight that is Accepting Passengers:

SDD:101
SDD: XS101/06NOV ATL/0
OP/NAM
*** FLIGHT IS OVERWEIGHT ***
CWT262143 UWT252233 CAW006514 UAW-03396 WTN1 KG TCI
757/200
GTD/???? POS/GATE BDT2230 SD2300 ED2300
AK00000 CD00000
ARN/XS-757A
CNF/C54Y174 CAP/C54Y174 AV/C54Y69 PADC/C0Y0
*ATLJFK R0008/0175
C0000/0105
B0118 UM000 WCH00 I00
SB0000/0000 B0000
SA0000/0000
EXST00/00 XCR00/00 DHC00/00
GS
ID
ATL 000/074
000/000
Note: Overweight parameters are controlled by the ATL Customer Support and should be contacted
when needed.
Note: A flight will accept passengers while overweight when parameters are set to do so, but
adjustments must be made by load planning staff to return weights to within limits.
Note: The flight entry may be the marketing flight, but the system displays the operating flight
information.

Page 41

Page 42
7. Passenger Displays
7.1. Booked / Checked-In Display (PS)
Any agent can display the booked/checked-in display. Enter:
PS:FLIGHT
It is possible to enter a particular class, but this displays only those passengers booked in that specific
class.
1
PS:XS735
Response to PS:XS735
PS: XS735/08JUNATL
OP/NAM
737/106C GTD/B17 POS/GATE BTD/1930 SD2000 ED2000 SA2105 FT0105
1.
2ABOTT/LMR
A2
SN17E
M
MIA
INF
PSM
ABOTT/GMRS
A2
SN17F
M
MIA
RES
PSPT
2.
1ADAM/GMST+
BN002
SN2A
C
MIA
UM
RES
3.
2ALLEN/TMR
B2
M
MIA
PSPT TKNE
ALLEN/LMRS
B2
M
MIA
PSPT TKNE
4.
4ANDREWS/DMR
C4
M
MIA
O
MKT
ANDREWS/RMRS
C4
M
MIA
O
MKT
ANDREWS/YMIS+
C4
M
MIA
O
MKT
ANDREWS/RMST+
C4
M
MIA
O
MKT
5.
1BAILEY/DAVI+
SN2D
C
MIA
RES
BLND
6.
1BARNES/EMR
SN1C
C
MIA
RES
WCHR
7.
1BAXTER/TMR
D2
M
MIA
PSPT TKNA
8.
2BROOMFIELD/MR
E2
C
MIA
MKT
TKNM
BROOMFIELD/MRS
E2
C
MIA
O
PSPT
9.
1BRUNSWICK/TMIS+
BN001
SN14D
M
MIA
UM
RES
10. 2BURNETT/FMRS
F2
M
MIA
I
PSPT
BURNETT/SMRS
F2
M
MIA
I
PSPT
11. 1CHAPPELL/MARY
D2
M
MIA
MKT
12. 1COLEMAN/OMR
SB035
M
MIA
PSM
ID SA
13. 1COOPER/DMR
C
MIA
14. 2DIXON/PMRS
G2
M
MIA
PSM
PETC
DIXON/AMIS+
G2
M
MIA
O
15. 1GIBSON/JMRS
K3 BN006
SN12A
M
MIA
MSG
+
1
2
3
4
5
6
7
8
9
10
Note: Passengers booked together with the same surname are not assigned a group code unless
there are passengers with different surnames in the same booking, e.g., 2ABOTT is not assigned A2.

Passenger Displays
Page 43
Field
Explanation
Passenger entry display number.
Number of family passengers with this surname.
Passenger's name. If the surname is more than 12 characters or the initials and title are
more than four characters the system displays a + indicating that the full name or initials and
title has not been displayed. It is possible to see the full name with a passenger record
display (PDD).
PNR party connector code.
Passenger boarding (BN) or standby (SB) number.
Seat number.
Class of booking.
Destination.
Items.
10
The + denotes that there are more pages to the display. Enter PN (NP) where the SOE ()
is displayed to move to the next page.
Table 7.1 Booked/Checked In Response Description

The following lists items that may appear beside a passenger name or can be displayed on request by
the PS entry. More than one item can be requested at the same time if they do not contradict each
other and they are separated either by a ',' or a ' ; ' depending on the items requested.
PS:FLIGHT NUMBER CLASS,ITEM,ITEM
Note: Using a , between items displays a list of passengers having all the listed items in their record.
PS:FLIGHT NUMBER CLASS,ITEM;ITEM
Note: Using a ";" between items displays a list of passengers having any one of the listed items in
their record.
Code
Description
ACC
Accepted Passengers.
ACS
Accepted Standby Passengers.
ADSR
Adjoining Seats.
ADV
Passengers Needing Notification.
AEC
Unseated Passengers Due Aircraft Change.
AECX
New Seat Passengers Due Aircraft Change.
ASR
Advance Seat Reservation.
AVIH
Live Animal in Hold.
BAG
Lists Number of Bags for Each Passenger.

Passenger Displays
Page 44
Code
Description
BLND
Blind Passenger.
BSCT
Bassinet.
CHD
Child.
COUR
Courier with Adjoining Seat.
CRS
Seat Reserved by Check In Edit.
DBI
Involuntary Denied Boarding.
DBV
Voluntary Denied Boarding.
DEAF
Deaf Passengers.
DEL
Deleted Passengers.
DNG
Downgraded Passengers.
EXBG
Excess Baggage Passengers.
EXST
Extra Seats.
FQTV
Frequent Flyer Passenger.
GRI(+REF)
Groups Under Same PNR Reference.
GRP
Groups.
I(FLT NBR)
Inbound Connections (Flight Number is Optional).
ID
PAD Passengers Can also display by ID code: PS:Flt/dte,ID-N2.
INF
Infants + Any Bassinets.
ITCI
Initial check-in via Interline Thru Check-In.
ITCU
Update via Interline Thru Check-In.
ITCX
Cancel via Interline Thru Check-In.
JMP
Jump seat Passengers.
MAAS
Meet and Assist.
MEDA
Medical Case.
MKT
Marketing Passenger on Code share Flight.
MSG
Passengers with Messages.
MUS
Musical Instrument Extra Seats.
NACC
Not Accepted passengers.
NAM
Followed by Passenger Name or Initial.
NREC
NOREC Passenger.
NRS
Non-requested Seat (Display only - cannot be requested by PS transaction).

Passenger Displays
Page 45
Code
Description
O (FLT NBR)
Onward Connecting Passengers (Flight Number is Optional).
OSR
Original Seat Request (Display only - cannot be requested by PS

transaction).
OTHS
Other Information.
OVR
Electronic Ticketed Passenger Check-in with OVR (Override)
PAD
PAD Passengers.
PCTC
Passenger Contact Information.
PDNG
List of Pre-down gradable passengers.
PETC
Pet Animals in Cabin.
PSM
Passengers with Special Messages (see Note below).
PUPG
List of Pre-Upgraded Passengers.
RES
Reservation Reserved Seats.
SA
Space Available Passengers.
SBY
Standby Passengers.
SEMN
Seaman.
SPML
Special Meals Or you can specify individual meal code.
STCR
Stretcher Passengers.
TKNA
Automated Ticket Number.
TKNE
Electronic Ticket Number.
TKNM
Manual Ticket Number.
TOP
Tour Operator Code.
UGPA
Passengers Available for Upgrade.
UM
Unaccompanied Minors.
UPG
Upgraded Passengers.
URES
Unbooked Passengers (GO-SHOWS).
WCH
Wheelchair Passengers.
WL
Waitlisted Passengers.
XBAG
Exempt Excess Bag Passengers.
XRES
Cancelled Reservation Passengers.
Passengers Rechecked from Another Flight.
N Placed before any Other Item Except I, O, Z gives a List Excluding that
Particular Item.
Passenger Displays
Page 46
Code
Description
NACC
List of Not Accepted Passengers.
@Y (COMPARTMENT)
List of Passengers by Aircraft Compartment. @Y must be the first item and

should not be preceded by a comma (,).
Table 7.2 Booked/Checked In Display Code Descriptions

Note: In order for check-in remarks from the PSM to be transmitted on the PSM message, a "/" must
follow PSM before free text is entered.

Passenger Displays
Page 47
1 Examples of various passenger display requests:

Display Request
Description
PS:XS493
All Passengers in All Classes.
PS:XS493/.C
All Passengers in C Class Only.
PS:XS493/.M ATL JFK
All M Passengers for a Specific Segment.
PS:XS493/.,UM
All UM Passengers on the Flight.
PS:XS493/.,ACC
All Accepted Passengers on the Flight.
PS:XS493/.,MSG
All Passengers with Messages.
PS:XS493/.,WCH
All Wheelchair Passengers on the Flight.
PS:XS493/.,GRP
List of All Groups on Flight.
PS:XS493/.,CHD,INF
All Children and Infants on the flight.
PS:XS493/.C,NAMP
All class C Passengers with Names Starting by P.
PS:XS493/.,TKNE
All Electronic Ticket Passengers (TKNE).
PS:XS493/.,O
All Passengers with Outbound Connecting Flights.
PS:XS493/.,I
All Passengers with Inbound Connecting Flights.
PS:XS493/.,MKT
All Passengers Booked on the Marketing Flight of a Code share Flight.
PS:XS493/.,PSPT
All Passengers with Passport Information.
PS:XS493/.@Y
All Passengers Booked in the Economy Compartment of the Aircraft.
PS:XS493/.@C
All Passengers Booked in the Business Compartment of the Aircraft.
PS:XS493/.,NAMWARD;
NAMGILL
All Passengers by the Name of Ward and Gill.
Table 7.3 Passenger Display Request Descriptions

Passenger Displays
Page 48
7.2. Standby / Notification Display

7.2.1
Standby Display (SB)
Any agent can display the standby or passenger notification list.

The entry is:
SB:FLIGHT NUMBER / DATE
1
SB:XS735/.
This list can consist of the following categories of passengers:
7.2.2
Need Notification
These are passengers who may or may have not checked-in but some change has been made to their
passenger record and they need to be notified. For example, a passenger not booked on the flight
may check-in and the system puts him on the standby list. Later due to some change on the flight
some seats become available and the system may automatically accept him. As the passenger may
not be present at the check-in desk at that moment, the system places the name on to the notification
list to remind the agents that this passenger needs to be notified that he has now been accepted on
the flight. Names are listed alphabetically.
7.2.3
Transit PAD
This is a list of all PAD passengers accepted up line on TRANSIT flights. Names are listed in Offload
Priority order with first to be offloaded passengers listed first and last to be offloaded listed last.
7.2.4
Local PAD
This is a list of all accepted PAD passengers at this station. Names are listed in Offload Priority order.
With first to be offloaded passengers listed first and last to be offloaded listed last.
7.2.5
Standby
This is a list of all passengers on STANDBY at this station. Names are listed in Onload Priority order.
With first to be onloaded listed first, and last to be onloaded at the bottom.
Response to SB:XS735.
SB: XS735/08JUNATL
OP/NAM
737/106C
GTD/B17
POS/GATE
FT0105
AV C4M63
PAD C0M0
NEED NOTIFICATION
1. 2BLAKE/MMR
B2
BN002
BLAKE/TMS
B2
BN003
2. 1KELLY/LMRS
BN019
LOCAL PAD
3. 1PORTER/GMRS
BN045
4. 1EDWARDS/YMR
BN023
STANDBY
5. 1CARLTON/N
SB025
6. 3FERGUSON/SMR K3
SB035
FERGUSON/YMRS K3
SB036
FERGUSON/LMIS+K3
SB037
7. 1BOOTH/AMR
SB019
1. 2.
3.
4.
5.
BTD/1930
SD2000
ED2000
SA2105
SN1A
SN1C
SN23D
C
C
M
MIA
MIA
MIA
ACC/SB007
ACC/SB008
PU/NP
SN3C
SN4A
C
C
MIA
MIA
P08 IDN1/MAR71
P05 IDS1/AUG69
PAD
PAD
PAD
PAD
LMTS
6.
M
M
M
M
M
7.
MIA
MIA
MIA
MIA
MIA
8.
P20
P50
P50
P50
P90
9.
IDS2/MAY71
IDN2/APR79
IDN2/APR79
IDN2/APR79
IDR2/SEP85
Explanation:
Field
Explanation

Passenger Displays
Page 49
Field
Explanation
Passenger entry display number.
Number of family passengers with this surname.
Passenger's name. If the surname is more than 12 characters or the initials and title are more
than four-characters the system displays a + indicating that the full name or initials and title
have not been displayed. To see the full name with a passenger record display (enter
PDD:5).
PNR party connector code.
Passenger Boarding (BN) or Standby (SB) Number.
Seat Number or special designator. Possible designators are:

AECAutomatically disembarked due to aircraft change.
CAPAircraft capacity restriction.
DEBDisembarked passenger.
HOFlight on hold.
LMLimit restrictions due to manual/automatic numeric limits or space protection limits.
NAVNo live animals allowed or restricted limit reached.
OFECDisembarked manually using the JAC transaction during an equipment (AEC) change.
OFLOffloaded passenger by AC transaction with X option (to prevent automatic reacceptance).
PADPAD capacity restriction.
PETCAnimal in cabin restriction.
STLSeating limitations (check seat map for available seats).
LMTSNo GO-SHOW or ID figures set.
WTLWeight limitations (Check with Load Planning).
Class of check-in.
Destination.
It is possible to display information from the following sections, Table 7.4 Response to
Standby Description
Need Notification (Section 0) and Table 7.5 Need Notification Example Descriptions
Standby (Section 0).
Table 7.4 Response to Standby Description

7.2.6
Need Notification
Example
Explanation
ACC/SB007
Accepted from standby list with passenger holding this standby number.
DEL/BN038
Passenger deleted with boarding number being held by passenger.
DEL/SB025
Passenger deleted with standby number being held by passenger.
PA/NP
Seat reserved while passenger not present.

Passenger Displays
Page 50
Example
Explanation
PU/NP
Passenger record updated (perhaps new seat number) while passenger not present.
PW/NP
Passenger deleted while not present.
SBY/BN056
Passenger put on standby with boarding number being held by the passenger.
Passenger rechecked by bulk recheck transaction (BR/BRC/BRN) and passenger not

accepted on new flight.
Table 7.5 Need Notification Example Descriptions

7.2.7
Standby
Example
Explanation
P90
Priority Number. Comes from the PZ:AIRLINE table (The higher the number, the lower
the priority).
IDN2/APR79
Priority Code and Date of Joining.
Table 7.6 Standby Example Descriptions
7.3. Individual Passenger Record Display (PDD)

The PDD transaction allows agents to retrieve current and recorded passenger check-in data. Any
authorized check-in agents can use this transaction to display such information as:
Special Services the passenger has requested.
Pre-assigned Seats, Boarding Numbers, Allocated Seats, or Standby Numbers.
Time of passenger check-in and record of Agent/CRT that entered the initial transaction.
Subsequent list of time and Agent/CRT of any additional/modification entries to the passenger
record.
Note: The system lists a record of all the LOCAL times and Agents/CRT that did any entries to a
particular passenger record, and also lists whether the modification was a PU or PW etc.
The PDD transaction is normally entered after a PS or SB display using a passenger display entry
number, but it can also be entered by passenger name, seat number, boarding number, or standby
number.
The entry after a PS or SB display, is: 'PDD:ENTRY NUMBER'.

Passenger Displays
Page 51
To display a PS list, enter:

PS:XS735/.
Response of PS:XS735/.
PS: XS735/08JUNATL
737/106C GTD/B17 POS/GATE
1.
2ABOTT/LMR
A2
ABOTT/GMRS
A2
2.
1ADAM/GMST+
BN002
3.
2ALLEN/TMR
B2
ALLEN/LMRS
B2
4.
BOLTON/JMR
OP/NAM
SD2000 ED2000 SA2105 FT0105
M
MIA
INF
PSM RES
M
MIA
RES
C
MIA
UM
RES
M
MIA
M
MIA
SB1014 LMTS M
MIA
URES
BTD/1930
SN17E
SN17F
SN2A
To display the PDD record of passenger Adam the entry is:

PDD:2
Response of PDD:2
PDD: XS735/08JUNCATL,2
1.
ADAM/GMSTR
BN002
SN1C
C
MIA
RES
AUTO 07JUN1146
ACC
VDT7917 AGT937/08JUN0823
PU
VDT2856 AGT286/08JUN0910/BAG
BAG1/12/0
UM10
To display a SB list:
SB:XS735/.
Response of SB:XS735/.
SB: XS735/09JUN ATL
737/106C GTD/???? POS/GATE BDT1930 SD2000 ED2000
AV C12M98
PAD C0M0
STANDBY
1. 1BRANDON/JMR
SB1014
LMTS Y MIA P3
SA2005
OP/NAM
FT2005
URES
Display a PDD of standby passenger Brandon:

PDD:1
Response of PDD:1
PDD:1
PDD: XS735/09JUNMATL,01
1. BRANDON/JMR
SB1014
LMTS M MIA URES M1/75 BAG1/10/0
BAGTAGS ISSUED: ATL
0149022682/MIA
SBY VDT2110 AGT877/09JUN1628/LMTS

Passenger Displays
Page 52
The following is an example of a PDD from a code share flight:
1 Example of PDD for a Code share Passenger

PDD:1
PDD: XS040/01OCTYJFK,01
1. BRITT/JAMES
BN002 SN17C
LFMLMKT/YY141/01OCT M LHR
ACC VDT2110 AGT877/01OCT1216
PU
VDT2110 AGT877/01OCT1324/LFML
Y LHR M1/75
partners.
The following is an example of a PDD with double oncarriage segments:
1 Example of PDD with Double Oncarriage Segment:

PDD:1
PDD: LG112/04NOVYMUC,01
1. ADAMS/L MR
DP/LG113/04NOV
DP/LG061/04NOV
Y LUX
Y FRA
Y FRA
M1/75
Note: DP indicates the passenger is double-booked on a segment.

The passenger record can contain any of the following codes. Each code is followed by the
workstation (VDT) from where it was transacted, the agent number performing the transaction, the
local date and local time. If the action was an update (PU) or a deletion (PW), the content of the
activity will follow (SNR, BAG, etc.). An action showing agent sign 9999 indicates an action that was
performed by the system as the result of another control transaction. An example would be the
automatic acceptance of a person on standby by increasing the GS limit. The passenger record can
contain any of the following codes:
Code
Explanation
ACC
Accepted (time of check-in).
ADV
Advised (time of passenger notification).
APT
Airport Tax.
ASR
Advance Seat Request from PNL shown as V on seat map.
***CODESHARE**** YY141
Indicates marketing partner and marketing flight number code sharing

with the operating flight.
DEB
De-Boarded passenger.
DEL
Passenger deleted.
ITCI
Passenger checked in on ITCI segment.
ITCU
Passenger record updated with a check-in on the ITCI segment.
ITCX
ITCI segment deleted from a passengers record.
NPA
Not Present - Record modified but passenger not yet checked-in.
OFL
Offloaded passenger by AC transaction with X option.
OFEC
Offloaded due to capacity for AEC change.

Passenger Displays
Page 53
Code
Explanation
NRS
Not reserved seat.
PDN
Pool Baggage Donor (Bag details attached to receiver record).
PRC
Pool Baggage Receiver (Bag details attached to this record).
PU
A 'PU' entry was done to the passenger record.
PW
A 'PW' entry was done to the passenger record.
RES
Reserved Seat Request from PNL and ADL shown as R on seat map.
SBY
Passenger was checked in to Standby.
SEA
Passenger reseated via SEA transaction.
SPC
Special Charge (No excess bag details available for specified

destination or change of class).
Followed by a bag tag number means bag was deleted in a transit

station.
XBC
Excess Baggage Charge accepted.
XPD
Cancelled Pool Baggage Donor.
XPR
Cancelled Pool Baggage Receiver.
Passenger Rechecked from one flight to another.
Prefix on Bag Tag. Bag deleted in origin station.
Prefix on Bag Tag. Onward Bag deleted in connecting station.
Suffix on Bag Tag. Manually entered tag number.
Table 7.7 Passenger Record Code Descriptions

The PDD entry can be displayed by Passenger Name, Seat Number, Boarding Number, or Standby
Number.
A)PDD by Name
The entry is:
PDD:FLIGHT NUMBER CLASS, NBR NAME
1 Example
PDD:XS735Y,1ADAM
Note: If the class is not known, omit class, and if the number of passengers associated with name is
not known enter 1. It is not necessary to enter the full name, but the more details entered, the more
chance the system has of finding the requested name. The system either displays the record of the
passenger requested, or responds with a similar names list (a subsequent PDD transaction can use an
entry number from this response to identify the correct passenger).
B)PDD by Seat Number
The entry is:
PDD:FLIGHT NUMBER, SEAT NUMBER
Passenger Displays
Page 54
1
PDD:XS735,SN17A
C)PDD by Boarding Number
The entry is:
PDD:FLIGHT NUMBER, BOARDING NUMBER
1
PDD:XS735,BN114
D)PDD by Standby Number
The entry is:
PDD:STANDBY NUMBER
1
PDD:SB121
Note: There is no requirement to enter flight number when entering a request by standby number. A
passenger retrieval selection transaction can also be done using an entry number from a PA selection
response, because standby numbers are assigned on an airline basis and not by individual flight. This
allows standby passengers to be moved from one flight to another and keep the same number.
The PDD display entry number can also be used to identify passengers after the following transaction
entries:
PU
Passenger Update
PW
Passenger Delete
NO
Passenger Notification
BC
Boarding Card request
After any initial PDD display from a PS or SB list, it is possible to do further PDD displays without reentering the PS or SB list providing the entry number is known.
The entry is:
PDD:ENTRY NUMBER PS
1
PDD:12PS

Passenger Displays
Page 55
PDD:ENTRY NUMBER SB
1
PDD:5SB
E.) PDD by Ticket Number
PDD:FLT/DATE,TKNE/1234567890123C3
F.) PDD by Frequent Travel Number
PDD:FLT/DATE,FQTV/123456789
G.) PDD by Passport Number
PDD:FLT/DATE,PSPT/A123456
Note: The date may equal a period (.) for the current date, a minus sign () for yesterday, a plus sign
(+) for tomorrow or be in DDMMM format (e.g., 23OCT).
H.)PDD Display for a Passenger from another Station
PDD:FLIGHT/.STN,BN NUMBER
PDD:FLIGHT/.STN,SN NUMBER
PDD:FLIGHT/.STN,1PAX NAME
7.4. Search by Bag Tag

The PDD has a BT option which allows searching for a passenger by flight (plus date if not current
date) using bag tag number. Only one bag tag number may be used in each entry. The bag tag can
be entered with either the two- or three-letter airline code or the airline numeric code, beginning with
0.
1
PDD:XS100, BT XS123456
PDD:XS100,0950123456
Response to PDD:XS100,BT XS123456
PDD:XS100/08JAN ATL,BTXS123456
1.
HUNT/JAMES MR BN008 SN11G
BAGTAGS ISSUED: ATL 1/9
0950123456/MIA
ACC VDT8267 AGT66/08JAN1414
MIA BAG/9/0
Note: If exactly ten numbers are not entered or the bag tag number cannot be found, the system
responds 020-PSGR ID.
7.4.1
Manual Bag Tags
Manual bag tags that are entered with a two- or three-letter airline code are displayed in the PDD with
the numeric airline code (with a +) rather than the letter code.
Passenger Displays
Page 56
1
PA1,1/10,B/XS123456/MIA
PDD:1
Response to PDD:01
PDD:XS170/08JAN Y ATL,1
1. GRANT/MARY
BN025
SN22A Y MIA
0950123456+/MIA
ACC
VDT72846 AGT91/08JAN192
BAG 1/10

Passenger Displays
Page 57
8. Passenger Acceptance / Modification / Withdrawal

8.1. Introduction
This section describes the three primary passenger handling transactions which allow staff to accept
or modify a passengers check-in record. These transactions are:
Transaction
Description
PA
Passenger Acceptance
PU
Passenger or item Update
PW
Passenger or item Withdrawal or delete
Table 8.1 Passenger Handling Transactions

Associated passenger handling transactions dealing with boarding cards / bag tag issuance and
excess baggage are also covered.
8.2. Passenger Acceptance (PA) Check-In

There are three basic types of automated check-in options. They are:
A)
NAME CHECK-IN (NAM)
The passenger name is required for all check-in transactions and all booked passenger names are
checked against a system-held PNL (passenger name list).
B)
NUMERIC CHECK-IN (NUM)
The passengers are checked-in on a first come basis, and the system does not check for names
against a Passenger Name List (PNL).
C)
PARTIAL NAME CHECK-IN (PNM)
This is an extension of numeric check-in, in that the system only checks a PNL for passengers with
special remarks, such as wheelchair required passengers or unaccompanied minors. The other
passengers are checked-in depending on numeric limits rather than on names.
This User Guide mainly describes Name check-in. This means that for any examples shown, it is
assumed that the system does a check against a system-held PNL. Also for those Airlines that use
the BAG TAG (B) printing option, this is explained in the section on Bag Tag Issuance (B) (8.14).

Passenger Acceptance / Modification / Withdrawal
Page 59
8.2.1
Check-In Procedures
There are two MAIN ways to check-in a passenger:

From a Previous PS List Display
or
Detailed Entry
8.2.1.1 Check in from a Previous PS List Display:
Two entries are involved in this check-in process:
1. Display the PS list.
2. Check-in the passenger by using the Item Number on the PS list.
The advantage of this method is all the agent needs to enter is the Bag details (plus any special seat
requests or PSM remarks), as the system already has the other details such as Passenger name,
Gender (for GENDER required flights), Class of Travel, and Destination (required for multi-destination
flights).
1
Passenger MR.L.COOPER who is booked in C class on flight XS593 to JFK today can be checked-in
as follows:
PS:XS593C,NACC,NAMC
This gives a list of all Not Accepted Passengers with Names starting with C.
Response to PS:XS593C,NACC,NAMC
PS:XS593/08JUNCATL,NACC,NAMC
737/106C
GTD/B24
POS/GATE
1.
1CHARLES/JOHN
D2
2.
1COLLIE/TMR
3.
1COOPER/LMR
BTD/0930
SD1000
ED1000
C
JFK
C
JFK
C
JFK
SA1105
OP/NAM
FT0105
By using the correct entry number, in this case number 3, and adding some baggage details (1 piece
at 12 kgs), the entry would be:
PA:3,1/12

Page 60
Response to PA:3,1/12
PA:XS593/08JUNCJFK1COOPER/LMR,1/12
AV C12M54
PAD C0M2
737/106C
GTD/B24
POS/GATE
BTD/0930
1.
COOPER/LMR
BN019
SD1000
SN07A
ED1000
*JFK*
SA1105
FT0105
Passenger is now checked-in and his boarding card issued. The check-in transaction is complete.
The check-in transaction issues a boarding pass with the following exceptions, if:
Excess baggage charges are applied the response shows the amount of excess bag charges to
be assessed with the comment BOARDING PASS PRINT INHIBITED.
API data is required and is not complete the response is BOARDING CARD INHIBITED MISSING
DOCUMENT DATA
To check-in as above and also issue bags tags, the entry would be as follows:
PA:3,1/12,B
The details of the bag tags can be seen in the passenger's PDD.
8.2.1.2 Check-in Detailed Entry
The Detailed Entry involves entering the Flight Number, Class of travel, Destination (for multi-sector
flights only), Number of passengers traveling, the Family Name plus any titles or first names, the
Gender (for GENDER required flights only), the Baggage details plus any additional information such
as special seat requests, Onward connections, PSM remarks etc.
1 Example:
Check-In of a multi sector flight with gender
PA:XS593 C JFK 1COOPER/LMR,M1,1/12,B

Note: It is only necessary to include the destination if the flight is going to more than one destination,
and gender only has to be included on Gender required flights.
Response to PA:XS593 C JFK 1COOPER/LMR,M1,1/12,B
PA:XS593/08JUNCJFK1COOPER/LMR,M1,1/12,B
AV C12M54
PAD C0M2
737/106C
GTD/B24
POS/GATE
BTD/0930
FT0105
1.
COOPER/LMR BN019 SN07A
1 Example:
SD1000
ED1000
SA1105
*JFK*
Check-in for a single sector flight that does not require gender
PA:XS772 Y 1MACKAY/JMR,1/15,B
Response to PA:XS772 Y 1MACKAY/JMR,1/15
PA:XS772/08JUNCMIA1MACKAY/JMR,M1,1/15,B
AV Y075
PAD Y2
727/A GTD/B24
POS/GATE
BTD/1330
SD1400
1.
MACKAY/JR BN035
SN26C
ED1300
SA1405
FT0105
Passenger is now checked-in and the boarding card is issued.

Page 61
8.2.2
Gender Required Flights
For GENDER required flights, the system calculates the genders of each passenger from the PNL,
based on TITLE attached to the name, using the following standards:
Title
Gender
MR, DEFAULT
M (MALE)
MRS,
F (FEMALE)
CHD, MSTR, JNR
CHD (CHILD)
Table 8.2 Gender Required Flight Titles

Note: The GENDER MISS could be either CHILD or FEMALE but, as the system has no way of
knowing it defaults to FEMALE.
A passenger on the PNL with no title will read into SDC, defaulting to a male gender. A parameter has
been created, on gender required flights, making the gender entry mandatory during the PA: process.
This parameter can be activated by contacting pss.helpdesk@sita.aero.
If the check-in method used is the 'QUICK WAY FROM THE PS LIST', there is no need to enter the
GENDER again, unless a change of GENDER is required, as the system has already created a
GENDER item in the passenger's record.
Note: It is not possible to change the GENDER of a passenger after check-in. If the incorrect
GENDER was created, then the passenger should be offloaded (PW) and checked-in again with the
correct GENDER.
If the check-in method used is the 'LONG WAY WITH FULL DETAILS', then the GENDER must be
input with the check-in entry. The way to enter the various GENDER items is as follows:
MALE
Followed by the number (M1 or M2 etc.)
FEMALE
Followed by the number (F1 or F2 etc.)
CHILD
CHD
Followed by the number (CHD1 or CHD2 etc.)
INFANT
INF
Followed by the number AND name (INF1ANN)
Note: For more than one infant, the INF is followed by the total number of infants then the each name
is separated by a + (INF2DAVID+MARY or INF3JANE+IAN+JOHN). This transaction is limited to the
number of infants being equal or less than the number of adults or children at check-in.
When a passenger is checking-in, the system first looks for an EXACT name match, and if it finds it,
then the passenger is checked-in. However if the system cannot find an exact match, or if it finds
SIMILAR names, it responds with a names list, including a NOREC name, and the agent then must
identify the correct passenger.
Note: If the system responds with a name list, this list may include passengers in other classes and
also passengers already checked-in, providing their names correspond to the name entered.

Page 62
1
Check-In for a Non-Gender required flight:
PA:XS593/08JUNMJFK1FLETCHER,1/12,B
Response to PA:XS593/08JUNMJFK1FLETCHER,1/12
PA:XS593/08JUNMJFK1FLETCHER,1/12,B
1.
1FLETCHER/ -NOREC PSGR
2.
1FLETCHER/GMR
3.
2FLETCHER/JMR
D2
FLETCHER/FMRS
D2
4.
1FLETCHER/PETER BN023 SN22D
M
C
C
M
JFK
JFK
JFK
JFK
In this case if the passenger is identified as entry number 2, enter:

PA:2
Response to PA:2
PA:XS593/08JUNMJFK1FLETCHER/GMR,1/12,B
AV C10M34
PAD C0M2
1. FLETCHER/GMR
BN031 SN19C
Passenger has now been checked-in and the boarding card issued. The check-in transaction is
complete.
Note: If you need to check-in another passenger from the PS list and you know the Item number of
the passenger you can check-in without re-displaying the PS list by entering the following entry:
PA3PS,1/10

Page 63
The following SSR and information codes can be input with the check-in entry:
SSR Code
Explanation
ADSR
Adjacent/courtesy seat reserve request.
AVIH (P/W)
Live animal in the hold.
BLND
Blind passenger.
BSCT (NBR)
Bassinet request for infant.
CHD (NBR)
Child gender indicator.
COUR
Courier.
DBI
Denied Boarding Involuntary (PU and PW entries only).
DBV
Denied Boarding Voluntary (PU and PW entries only).
DEAF
Deaf passenger.
EXST
Extra seat request.
F (NBR)
Female gender indicator.
FOID
Form of Identification for Electronic Ticket Passengers.
FQTV
Frequent flier number.
ID
Airline staff indicator followed by status code.
INF (NBR)
Infant gender indicator followed by name.
JMP
Jump-seat passenger.
M (NBR)
Male gender indicator.
MSG
Message indicator followed by text.
MUS (WT)
Extra seat for musical instrument.
NAM (NBR)
Re-name passenger code followed by new name.
Oncarriage with flight, class, date and destination.
PCTC
Personal contact (Telephone contact as may be required.)
PETC (P/W)
Live pet in the cabin.
PSM
Passenger service message indicator followed by /text.
PSPT
Passport information (APIS functionality).
Request a specific seat or seat designator.
SEMN
Seaman indicator followed by / free text.
SNR
Request specific seat override.
SNRGRP
Request specific group seat indicator.
SPML
Special meal code, or actual meal code.

Page 64
SSR Code
Explanation
STCR
Stretcher passenger indicator.
TKNA
Ticket number for Automated Ticket (Up to 14 characters).
TKNE
Ticket number for Electronic Ticket (Up to 14 characters).
TKNM
Ticket number for Manual Ticket (Up to 14 characters).
TOP
Tour Operator Code (Up to 25 alpha/numeric characters).
UM
Unaccompanied minor indicator.
URES
Unbooked passenger indicator.
WCHR
Wheelchair passenger to gate (ramp).
WCHS
Wheelchair to aircraft door (needed for stairs).
WCHC
Wheelchair to aircraft seat (passenger cannot walk).
XBP
Inhibit boarding card issuance.
Recheck passenger to another flight.
(P/W)
Pieces/Weight required.
(NBR)
Number required.
(WT)
Weight required.
Table 8.3 Check In SSR and Information Codes

Note: The difference between R and SNR, is that SNR is more powerful. An R requested seat
determines whether the seat has any system restrictions such as already reserved for another
passenger (or blocked for an infant), and issue a different seat, whereas the SNR seat request will
override any of these restrictions (unless already occupied or blocked by X) and allocated the seat. It
is important to enter the correct code with the check-in request.

Page 65
8.2.3
Upgrade/Downgrade Passengers
Passengers can be upgraded or downgraded before or after check-in. Passenger Upgrades and
Downgrades are subject to standby limits at check-in. It is optional to indicate whether a pre-upgrade
is voluntary "/V" or involuntary "/I" following the upgrade or downgrade entry.
8.2.3.1 Pre-Upgrade / Pre-Downgrade
The entry to pre-upgrade to F class:
PU:#ENTRY NBR,PUPG F/V
1
PU:#1,PUPGF/V
The entry to pre-downgrade to Y class:
PU:#ENTRY NBR,PDNGY/I
1
PU:#1,PDNGY/I
Note: It is not possible to upgrade or downgrade a passenger during the check-in process. It can only
be done before or after check-in.
8.2.3.2 Upgrade (UPG)/Downgrade (DNG) Passengers Already Checked-In
When upgrading or downgrading a checked-in passenger, it is mandatory to indicate whether an
upgrade is voluntary "/V" or involuntary "/I" following the upgrade or downgrade entry.
The entry to downgrade a checked-in passenger to Y class:
PU:ENTRY NBR,DNGY/V
1
PU:1,DNGY/V
The entry to upgrade a checked-in passenger to F class:
PU:ENTRY NBR,UPGF/I
1
PU:1,UPGF/I
Note: There must be some GO-SHOW or ID figures set for the class being requested BEFORE the
transaction can be entered; otherwise, it is rejected with the response: MODIFICATION WOULD
CAUSE STANDBYING LMTS.

Page 66
8.2.3.3 To Cancel Pre-Upgrade/Downgrade

The entry to cancel a pre-upgrade is:
PW:#ENTRY NBR,PUPG
1
PW:#1,PUPG
The entry to cancel a pre-downgrade is:
PW:#ENTRY NBR,PDNG
1
PW:#1,PDNG
Note: When canceling an upgrade (or downgrade), use the PW entry and re-enter the same code that
was originally entered with the PU but this time without the class (Example if the PU entry was
PU#1,PUPGF then the PW entry is PW#1,PUPG).
Note: Passenger upgrade and downgrade limits are subject to the standby limits for check-in.
8.2.4
Re-Checking Passengers to a Different Destination
A passenger can be rechecked to a new flight, or a new destination on the same flight. The entry code
that identifies a recheck is being attempted is a 'Z'.
The PA transaction can recheck a passenger onto a new flight, or it can recheck a passenger to a
different destination on the same flight.
The entry from a PS list is:
PA:ENTRY NBR,Z NEW FLT CLS DEST,P/W
PA:ENTRY NBR,Z FLT NBR CLSS NEW DESTINATION,P/W
1
PA:1,Z387YBBB,1/10
Note: The Z and flight number, class, and destination details must be entered before the baggage
details otherwise the entry is rejected with the response: 015 FORMAT.
PU Entry (Passenger Update)
The PU transaction can recheck a passenger onto a new flight, or it can recheck a passenger short of
their original destination on the same flight. The PU entry does not allow the update check-in of
passengers past their original destination on the same flight.
Note: If after check-in a passenger wishes to check-in to a destination past the original destination,
then offload the passenger (PW) and enter the recheck with the PA entry. If the attempt is done with
the PU entry the response is: 441 - RECHECK FLIGHT-DESTINATION

Page 67
8.2.5
Checking In Passengers with Double Oncarriage Segments
Passengers may be booked with two different segments to the same destination. An agent can select
one of the two segments at check-in.
Example: Passenger Adams is checking in with double oncarriage segments. His PDD appears as
follows:
1 Example of PDD with double oncarriage segments:

PDD:1
PDD: XS112/04NOVYJFK,1
1. ADAMS/L MR
DP/XS113/04NOV
DP/XS061/04NOV
Y JFK
Y LHR
Y LHR
M1/75
If the agent attempts to check in the passenger using PA:1,1/20,O the system responds with the
following error:
596 - DOUBLE ONCARRIAGE - SELECT CONNECTING FLIGHT
The agent needs to select which flight the passenger will travel on with the following entry:
PA:1,1/20,OXS061/04NOVYLHR
The passenger is now checked in for XS061/04NOV.
Note: A duplicate segment must be entered with an ADL.
To delete an outbound segment, enter:
PW:1,O
8.2.6
Checking In Passengers on an Overweight Flight
Passengers can be accepted on an overweight flight provided the URM parameters is set to do so.
Acceptance is done with a normal PA entry as follows:
PA:1,1/10,B
1 Example of a Response to PA1,1/10 on an Overweight Flight:

PA: XS101/06NOVYJFK65ps,2/20,B
*** FLIGHT IS OVERWEIGHT ***
AV C54Y69
PAD C0Y0
757/200
1. XRAY/B
BN105 SN39C
PSM
SA2330
FT0030
Note: Overweight parameters are controlled by the ATL Customer Support group and they should be
contacted when needed.

Page 68
8.2.7
Oncarriage Check-In
If a passenger has oncarriage details in his record, the O need only be inserted if the passenger is to
be through checked-in onto his next flight (PA:ENTRY NUMBER,P/W,O). Provided through check-in
is permitted, two boarding cards will be issued. If the O is left off, he will not be through checked-in,
nor will a second boarding card be issued. If the O is left off in error, and the passenger needs to be
through checked-in, the O can be added later with the PU entry (PU:ENTRY NUMBER,O). SSR and
information codes must precede the ",O". Seat requests on the outbound flight are entered after the
",O".
Note: If a parameter is set and the outbound flight leaves before arrival of the origin flight, an error
message Check Flight Continuity will display.
The system accepts multiple onward flight connections; however, a bag tag is limited to three flights.
Any additional flights will produce additional bag tags. The entry for oncarriage baggage checks is:
PU:FLIGHT CLS DEST,P/W,B/XXX.O FLT CLS DEST,O FLT CLS DEST
Note: The final destination of the bag (B) is mandatory when automated bag tags are issued. A date
is required for the onward flights if they are not for the current date.
1
PU:XS837 Y JFK0,1/10,B/ATH,OYY937MZRH,OAZ518YFCO,OOA826YATH
To delete a bag tag with oncarriage processing, enter:
PW:FLT CLS DEST 0,P/W,B/NUMBER
Note: If bag tags have been issued or manually entered, then it is mandatory for the B/ to be
followed by the position number on the line, for example, B/1 or B/2. The 1 indicates the first tag on
line, and 2 would designate the second bag. The system also accepts the actual bag tag number.

Page 69
8.2.8
Checking In Passengers on a Connecting Flight
When checking in a passenger with connecting segments, the ',O' indicates the onward segment.
Depending on which segment the connection begins, the check-in entry is followed by a ,O or ,O2 or
,O3 etc.
To check in a passenger from the PS list with the next segment on a connecting flight, use the
following entry:
Note: For the Interline through check-in process, the coupon is validated in the electronic ticket
database before the check-in process continues. If the ticket is for an ITCI flight, then the partner
airline validates the coupons before the check-in process continues.
1
PA1,1/12,B,O
To check in a passenger from the PS list with the second outbound segment on an interline thru
check-in flight, use the following entry:
1
PA1,1/10,B,O2
The 'PA' input entry is the same as it is for THRU CHECK-IN' whether the acceptance is from a 'PS'
list, or whether the actual flight number and passenger's name is used in the check-in entry.
Note: In the following examples, O designates an onward or ITCI check-in.
8.2.9
Through Check-In
The following types of Through Check In are available:
Through Check-in involving Electronic Ticket on two Flights
Through Check-In involving Electronic Ticket on one flight and paper ticket on the other flight
8.2.9.1 Through Check-in Involving Electronic Tickets on Two Flights

If the passenger has an e-ticket, the check-in now requires additional processing procedures. The
SITA Departure Control Services system must first verify that the passenger has a valid e-ticket on the
local flight, and then on the onward flight before check-in can be completed.
1 Example of process:
1. Enter:
PA:1,1/12,B/xxx,O (xxx = destination of the bag).
2. A validation message is generated for both flights and if both coupons are valid, check-in is
completed.
Note: If the local flight has a valid coupon but the onward flight it is invalid, then the passenger is only
checked-in on the local flight.

Page 70
8.2.9.2 Through Check-in Electronic Ticket on One Flight and Paper Ticket on Other Flight
If the passenger has an e-ticket and a paper ticket, the check-in requires additional processing
procedures. The SITA Departure Control Services system verifies that the passenger has a valid eticket on the local flights. If it is valid, then the onward flight check-in is completed and the boarding
passes issued for both flights.
1 Example of process:
1. Enter
PA:1,1/12,B/XXX,0 (XXX= destination of the bag).
2. A validation message is generated for the e-ticket flight and if the coupon is valid, check-in is
completed. On the boarding pass for the e-ticket flight ELECTRONIC TICKETED PASSENGER
WITH TICKET NUMBER is printed. On the paper ticket flight the boarding pass will print NOT
VALID WITHOUT FLIGHT COUPON.
8.2.10 Examples of Different Check-In (PA) Entries
Examples of various check-in entries:
1. Check-in booked Y Class passenger Jane Wright who is 8 years old with 1/14 baggage and is
traveling alone, and add the item that she is an Unaccompanied Minor:
PA:XS836Y1WRIGHT/JANE,1/14,CHD1,UM8
Or check-in from the PS list:
PA:ENTRY NBR,CHD1,1/14,UM8
Note: The UM indicator gets added to the PSM message for notification to the destination station.
Also the age gets included on the PSM if it is added along with the UM code.
2. Check in Y class passengers Andersen/A and Sergeant/B traveling together on XS397 with 3/33
bags:
PA:XS377Y1ANDERSEN/A, M1,3/33;SERGEANT/B,F1
Or check-in from the PS list:
PA:ENTRY NBR,3/33;ENTRY NBR
3. Check-in the second passenger from a family of three from entry number 2 with 1/10 baggage.
PA:2P2,M1,1/10
4. Check-in booked Y Class passenger from PS list entry number 4 who is traveling with PS entry
number 12 but who are not booked together and the second passenger has not arrived at check-in yet.
They want to sit together:
PA:4,1/10,R17A;#12,R17B
5. Check-in booked M Class passenger Mr. T.BROOK who is traveling with his wife, his son, and his
baby daughter named Mary on flight XS397:
PA:XS397M3BROOK/MR/MRS/MSTR,M1,F1,CHD1,INF1MARY,3/30
Or check in from the PS list:
PA:ENTRY NBR,3/30,INF1MARY
Note: The infant is not included in the passenger number but a name must be added after the INF1
item.
6. Check-in URES C Class passengers Mr. D.Kent and Mrs. J.Cannon who are traveling together:

Page 71
PA:XS296C1KENT/DMR,M1,2/30,URES;1CANNON/JMRS,F1,URES
7. Check-in booked Y Class passenger Mrs. K.Davidson with 1/12 bags, and add onward flight
KL204YAMS which is not in the passenger record:
PA:XS622Y1DAVIDSON/KMRS,F1,1/12,OKL204YAMS,URES
PA:ENTRY NBR,1/12,OKL204YAMS,URES
Note: The URES at the end denotes that the oncarriage and not the passenger was a new item to the
original passenger record.

Page 72
8. Check-in URES Y Class passenger Mr. T. Simpson with 1/14 bags, with confirmed Onward flight
DL881YLAX:
PA:XS937Y1SIMPSON/TMR,1/14,URES,ODL881/07NOVYLAX
Note: The URES is entered after the baggage details and not at the end of the transaction. If it is
entered at the end, instead of after the baggage, the system would treat the passenger as a NOREC
and the onward connection as the URES.
9. Check-in a PAD passenger (N2) who was not previously listed on a flight and add his Date of
Joining his airline company:
PA:XS118M1HULBERT/LMR,1/12,IDN2/APR79,URES
10. Check-in two Crew in C Class, who are traveling on the flight in passenger seats without any
baggage:
PA:XS633 C 2XXXCREW,0/0,M1,F1
Note: These passengers are included in the total passenger figures but are also displayed separately
under XCR on the SDD display.
11. Check-in passenger from PS display, Entry Number six. Passenger requests an Aisle seat.
PA:6,1/15,RI
Note: The R stands for seat request; the I stands for aisle, and the S for smoking.
12. Check-in booked M Class passenger YORK and add the message for the PSM that he is blind.
PA:XS383M1YORK,1/10,PSM/PLSE MAAS AS PAX IS BLIND
Note: The '/' after the PSM specifies that this message must go on the PSM. If it is omitted, then it will
not be sent. MAAS means meet and assist.
13a. Check-in booked Y class family WATSON who has one child and two infants.
PA:XS927Y3WATSON/MR/MRS/MSTR,3/30,M1,F1,CHD1,INF2IAN+MARY
Note: A '+' is inserted between the infant names.
13b. Check-In two infants with two separate adult entries.
PA1,2/20,INF1JOEY;2,INF1SUSAN
14. Add a Name to a NONAME during check-in:
PA:FLIGHT CLASS 1 NONAME,M1,P/W,NAM(NEW NAME)
PA:XS100Y1NONAME,M1,1/10,NAM1JONES/MR
PA1,NAM1SMITH/JOHN,M1,1/10
15. Y Class passenger GRANT is Booked MIA to JFK on flight XS397 that operates MIA to ATL to
JFK, but now wants to disembark at ATL:
PA:1,ZXS397YATL,1/10
Note: The baggage must be entered after the Z item.

Page 73
16. Check-in booked Y Class Family of four AHMED/MR/MRS/MSTR/MSTR with two Infants, a Pet
Dog in the cabin, 4/50 baggage, an unbooked Onward connection to flight BA854 to LHR, and add
remark for PSM that they need assistance, as they speak no English:
PA:XS761YJFK4AHMED/MR/MRS/MSTR/MSTR,M1,F1,CHD2,INF2ANA+DAR,4/50,
-PETC1/10,PSM/PLEASE MAAS AS PAX SPEAK NO ENGLISH,OBA854YLHR,URES
User modification. PETC and AVIH count and weight will calculate excess baggage charges.
Note: If more than one line is needed, start the second line with a - and always remember to
put the Onward connection as the last item, otherwise the system ignores it.
17. Check-in URES Y class passenger Celina Johnson for the operating carrier of code share flight
XS761 with 1/12 baggage:
PA:XS761YJFK1JOHNSON/CELINA,F1,1/12,URES
18. Check-in URES M Class passenger Mary White for the marketing carrier of code share flight
XS761 marketing with YY761 with 2/24 baggage:
PA:XS761YJFK1WHITE/MARY,F1,2/24,MKTYY761M23ATLJFK,URES
19. Check in booked Y class passenger James Wilson by name for the next day flight with 1/12
baggage:
PA:XS761/+Y1WILSON/ROBERT,M1,1/12
20. Check in booked Y class passenger Allen Adams by name on XS761 with an interline through
check-in segment on YY851 with 1/12 baggage:
PA:XSY761Y1ADAMS/ALLEN,M1,1/12,O
Or from PS list:
PA:ENTRY NBR,1/12,O2
21. Check in booked Y class passenger John Wells by name on XS761 with 2 interline through checkin segments on YY851 and YY950 with 1/12 baggage:
PA:XS761Y1WELLS/JOHN,M1,1/12,O2
Or from PS list:
PA:ENTRY NBR,1/12,O2
22. Check in booked Y class passenger Sandra Smith by name on XS761 connecting to XS319 and
one interline through check-in segment on YY1152 with 2/24 baggage:
PA:XS761Y1SMITH/SANDRA,F1,2/24,O2
Or from the PS list:
PA;ENTRY NBR,2/24,O2
Note: When the interline through check-in segment falls on the third segment of the passengers
itinerary, the letter "O", followed by the Number "2" should be used, indicating the second segment of
the down line flights is the ITCI segment.
23. Check in Y class passenger Johnson/David from PS list on XS100 and change the last name to
the correct spelling of Johanssen with 1/12 baggage:
PA:ENTRY NBR,NAM1JOHANSSEN/DAVID,M1,1/12
24. Check-in Y class passenger Johnson/David with 1/20 BAGS from PS list on XS112 and choose
XS113 as his oncarriage flight to LHR:
Page 74
PA:ENTRY NBR,1/20,OXS113YLHR
25. To enter one or more TKNE elements in the same entry, the format is:
PA:XX857Y2TOMS/J/K,M1,F1,1/10,B,TKNE1/1251234567890C1,
-TKNE2/1251234567891C1,URES
26. To check in two TKNE URES passengers with different names.
PA:XX857Y1TOMS/JACKIE,F1,2/48,B,TKNE/1251234567890C1,URES;
-1SMITH/CAROL,F1,TKNE/1251234567898C1,URES
27. To check-in a TKNE URES passengers with an onward connection.
PA:XX857Y1TOMS/JACKIE,F1,1/10,B,TKNE/1251234567890C1,URES,
-OXS789YMAD,TKNE/1251234567890C2,URES
28. When a passenger checks-in with an infant, and the infant TKNE is already present in the same
PNR, then current check-in procedures apply.
If the passenger is a URES or a TKNE has to be added for an infant during the PA entry, then
the following Infant TKNE check-in format should be used:
PA:XX857Y1TOMS/LYNMRS,F1,INF1BOB,1/10,B,TKNE/1251234567890C1,
-TKNE/1251234567891C1-INF,URES
Note: The INF indicator must be inserted after the TKNE element and the ticket number.

Page 75
29. To check-in an infant not occupying a seat.

-TIJ02Y
2THOMAS/AMR/BMISS .L/PB272
.R/TKNE HK1 0952100004111/1-1THOMAS/AMR
.R/TKNE HK1 0952100004113/1-1THOMAS/BMISS
.R/INFT HK1 5MTHS OCCUPYING SEAT-1THOMAS/BMISS
Note: For infants holding seat the expression - OCCUPYING SEAT is mandatory. If it is missing or is
not correctly input, the infant is read-in as an infant not occupying seat.
30. To check-in an infant occupying a seat.

-TIJ02Y
2THOMAS/AMR/BMISS .L/PB272
.R/TKNE HK1 0952100004111/1-1THOMAS/AMR
.R/TKNE HK1 0952100004113/1-1THOMAS/BMISS
.R/INFT HK1 5MTHS OCCUPYING SEAT-1THOMAS/BMISS
Note: For infants holding seat the expression - OCCUPYING SEAT is mandatory. If it is missing or is
not correctly input, the infant is read-in as an infant not occupying seat.
31. PS List of Infant occupying a seat.
PS6A470/01MAY
-PS: 6A470/01MAY MEX
OP/NAM
72S/200
SA1720
1. 2THOMAS/AMR
Y TIJ PSM TKNE
THOMAS/BMIS+
Y TIJ TKNE
FT0331
32. PS List of Infant not occupying a seat.

PS:470/.
-PS: 6A470/01MAY MEX
OP/NAM
72S/200
SA1720
FT0331
1. 2ROHA/AMR
SN22D
Y TIJ INF PSM RES TKNE
ROHA/BMRS
SN22E
Y TIJ RES TKNE

Page 76
33. Check-in Acceptance - Infant occupying seat

-PDD:1
PDD: 6A470/01MAYYMEX,1
PNR RL PB272
1. THOMAS/AMR
Y TIJ TKNE/6A/0952100004111C1
PSM- /INFT HK1 5MTHS OCCUPYING SEAT-1THOMAS/BMISS
THOMAS/BMISS
Y TIJ TKNE/6A/0952100004113C1
-PA:1,1/10,OVR
-PA: 6A470/01MAYYTIJ1,1/10,OVR
AV Y162
PAD Y0
72S/200
1. THOMAS/AMR
BN001 SN6F
PSM
THOMAS/BMISS
BN002 SN6E
PDD:1
1. THOMAS/AMR
SA1720
FT0331
PNR RL PB272
SN6F
Y TIJ BAG1/10/0
TKNE/6A/0952100004111C1
THOMAS/BMISS
BN002 SN6E
Y TIJ TKNE/6A/0952100004113C1
ACC VDT53640 AGT102/01MAY0920/OVR
BN001
Note: The infant counter on the SDD is not updated by check-in acceptance of seat holding infant. In
other words the weight of the infant is recorded as an adult.
34. Check-in acceptance of infant not occupying seat.
-PA:1,1/10,INF1BABYTWO,OVR
-PA: 6A470/01MAYYTIJ1,1/10,INF1BABYTWO,OVR
AV Y162
PAD Y0
72S/200
1. ROHA/AMR
BN001 SN22D
PSM OSR
ROHA/BMRS
BN002 SN22E
OSR
PSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR
PDD:1
1. ROHA/AMR
BN001
SA1720
FT0331
PNR RL P1272
SN22D
Y TIJ INF1 BAG1/10/0 OSR
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
INF-BABYTWO
PSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR
ROHA/BMRS
BN002 SN22E
Y TIJ OSR OSR
TKNE/6A/0952100004112C1
RES AUTO 01MAY0753
ACC VDT53640 AGT102/01MAY0756/OVR

Page 77
35. PCR (Check-in Record) of infant not occupying seat

PDD:1
1. ROHA/AMR
PNR RL P1272
SN22D
Y TIJ RES INF1
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
INFPSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR

ROHA/BMRS
SN22E
Y TIJ RES TKNE/6A/0952100004112C1
RES AUTO 01MAY0753
36. Group Seating. Seats reserved by this entry display as a G on the seat map. At check-in the
agent must specify the code SNRGRP in the check-in transaction to seat the passenger in the group
designated area. The system then allocates one or more of the G seats.
1 Example check-in entry:

PA:ENTRY NUMBER, P/W BAGS, SNRGRP
PA:2,1/12,SNRGRP
37. Interline check-in with 1/12 bags with no tags, 0 hand carry.
PA:1,1/ 12/0,O
38. Interline check-in with 1/10 bags with tags, 0 hand carry.
PA1,1/10/0,B,O
39. Check in with 2/15 bags with no tags, seat 11A on local flight and Window on onward flight.
PA1,2/15,R11A,O,RW
40. Check-in with 1/10 bags, tags, FQTV number on local flight (FQTV will cascade to connecting
flight, if applicable).
PA1,1/10,B,FQTV XX/1230975,O
Check-in with 1/10 bags, no tags, 1 infant, with onward ITCI flight.
PA1,1/10,INF1JANE,O
Passengers with EXTRA seats (COUR, EXST, MUS, STCR, JMP) are normally not allowed. Check
local procedures.

Page 78
8.2.11 Passenger Manifest Information

The passenger record stores PCTC (Passenger Contact) items in the system. This information
appears n the PDD and PS list as an SSR item.
If the PCTC parameter is set, the PA transaction searches for PCTC information on flights entering or
departing the United States.
1 PA transaction example:
PA1,1/10,B
PCTC REQUIRED
PA1,1/10,B,PCTC/MARIA JONES 770-555-1212
1 PU transaction example:
PU1,PCTC/JOHN SMITH 770-555-1212
PCTC REQUIRED
1 PW transaction example:
PW1,PCTC
A list of passengers with PCTC remarks can be displayed with the following transaction:
PS:XS123/12YY , PCTC
8.2.12 DOCS, DOCA and DOCO Information at Check-In Time

Certain governments collect data that is available in passengers Passport and Visa documents in
addition to address information. The data may be added to the PNR at creation time or on a retrieved
PNR. The data may also be added to a passenger check-in record in SDCS. This information is used
to provide the necessary requirements for API, Paxlist, APP or Watchlist.
The following are formats that provide passport, address and other travel related information:
Travel Document Information (DOCS)
Residence or Destination addresses (DOCA)
Other Travel Related information (DOCO)

Page 79
8.2.12.1DOCS Travel Document Information

Checking in Passengers with Travel Document Information
A country may require travel document information such as passport, military ID, resident alien card
number, refugee status information or other acceptable forms of documentation.
Listed are acceptable travel document types:
Code
Document
Passport
Alien Resident Certification
Permanent Resident Certificate
Re-entry permit/refugee
INS Pass
Military ID
Naturalization Certificate
Boarding crossing card
Facilitation Document
Table 8.5 Acceptable Travel Document Types

Note: The above documents do not pertain to all countries.

Page 80
Edits for the DOCS entry are as follows:

DOCS Entry
Edit
Check-in code
PA or PU
Pax Entry #
Special Service Requirements Code
DOCS
Issuing Country
Two Three letter country

code
Document number
Up to 15 alpha/numerics
Passenger Nationality
Two Three letter country

code
Date of Birth
14AUG65
Gender
M or F
FI or MI (infant indicator)
Expiration date
28JAN09
Surname
BYRD
Given name
MILLY
Middle name
(optional)
Table 8.6 DOCS Entry Edits

Page 81
Below is an example of how to add the DOCS entry to a passengers record:

1. Display the PS list, enter PS Flight/Date:
PS1548/.
The Passenger List for the flight and date entered displays:
ps1548
PS: XS1548/03MAR MEX
D10/123 GTD/???? POS/GATE BDT2130 SD2200 ED2200
1. 1SMITH/JOHN
M ATL
2. 1BYRD/MILL+
M ATL
3. 1CARR/BETT+
M ATL
4. 1DOE/JOHN
M ATL
5. 1WARREN/JAMES+
M ATL
6. 1FIELD/DONA+
F ATL
7. 2LEAHY/RICH+
F ATL
LEAHY/JANE
F ATL
SA2345
FT0045
CC/NAM
2. Display a passengers PDD:

PDD:02PS
The Passenger Record displays:

PDD:02
PDD: XS1548/03MARMMEX,02
1. BYRD/MILLY
PNR RL DI93KD
M ATL M1/80
3. Check-in the passenger with the following entry:

PA1,0/0,docs/p/usa/920881/usa/14aug65/f/28jan09/byrd/milly
4. The PDD displays the following DOCS information:

PDD:01
PNR RL DI93KD
1. BYRD/MILLY
BN001 SN21J
M ATL OKT M1/80
DOCS-P /USA/920881/USA/14AUG65/F /28JAN09/BYRD/MILLY//
ACC VDT2110 AGT877/03MAR1105
Note: When using a facilitation document (DOCS/F), it is possible to have a document with no
expiration date. In this case replace the expiration date with a /.
To enter a document with no expiration date, use the following entry:
PA1,0/0,DOCS/F/CAN/989898/CAN/14AUG65/F//BYRD/MILLY

Page 82
Adding Infants Travel Document Information

An infant requires DOCS information in the passenger record in addition to the adult DOCS
information.
An infant was added to the previous passenger record to demonstrate how to add an infant passport.
The DOCS entry for an infant is almost identical to the adult entry with one exception. The infant
indicator is entered with the gender, using MI or FI to identify the infant.
5. Redisplay the previous passengers PDD:
PDD:01
PDD:01
PNR RL DI93KD
1. BYRD/MILLY
BN001 SN14A
M ATL OKT INF1/10 M1/80
INF-MARY
SCW VDT2110 AGT877/03MAR1105/OKT
PU
VDT2110 AGT877/03MAR1221/INF
6. Add the infant passport with the following entry:
PU1,DOCS/P/USA/923498/USA/14AUG04/FI/17NOV15/BYRD/MARY
7. The PDD now includes DOCS information for the infant:
PDD:01
PNR RL DI93KD
1. BYRD/MILLY
BN001 SN14A
M ATL OKT INF1/10 M1/80
INF-MARY
DOCS-P /USA/923498/USA/14AUG04/FI/17NOV15/BYRD/MARY//
PU
PU
VDT2110 AGT877/03MAR1231/DOCS

Page 83
8.2.12.2Deleting Docs from Passenger Records

To delete DOCS from a single passenger use the following format:
PW1,DOCS
Entry:
PW1,DOCS
Response:
PDD:01
PDD: XS060/11JANCATL,01
PNR RL RQ5MKC
1. JESSE/JULYE
A6 BN008 SN15A
C YYZ M1/88
DOCA-D/USA/111 LEE ST/NEW YORK/NY/123454/
DOCS-P /ROU/765423/ROU/12JUN75/F /20JAN08/JESSE/JULYE//
ACC VDT2110 AGT877/11JAN1111/SN15A
To delete DOCS from a passenger with multiple passengers in the same record:
PW1P2,DOCS
Entry:
PW1P2,DOCS
Response:
PDD:01
PDD: XS060/11JANYATL,01
1. SMITH/ANDY
BN014 SN40K
Y YYZ M5/440
DOCA-D/CAN/TORONTO/
DOCS-P /USA/93493/USA/15NOV61/M /15DEC05/SMITH/ANDY//
SMITH/BETTY
BN015 SN40J
Y YYZ
DOCA-D/CAN/TORONTO/
DOCS-P /USA/99984/USA/15NOV62/F /02JAN06/SMITH/BETTY//
SMITH/CHARLES
BN016 SN40H
Y YYZ
DOCA-D/CAN/TORONTO/
DOCS-P /USA/93495/USA/15NOV90/M /19AUG10/SMITH/CHARLES//
SMITH/DEBRA
BN017 SN40G
Y YYZ
DOCA-D/CAN/10 1ST ST/TORONTO/
DOCS-P /USA/93493/USA/15NOV61/M /22AUG09/SMITH/DEBRA//
SMITH/EDWARD
BN018 SN40F
Y YYZ
DOCA-D/CAN/10 1ST ST/TORONTO/ON/
DOCS-P /USA/99984/USA/15NOV62/M /15APR07/SMITH/EDWARD//
ACC VDT2110 AGT877/11JAN1159/P1/SN40K
ACC VDT2110 AGT877/11JAN1159/P2/SN40J
ACC VDT2110 AGT877/11JAN1159/P3/SN40H
ACC VDT2110 AGT877/11JAN1159/P4/SN40G
ACC VDT2110 AGT877/11JAN1159/P5/SN40F
To delete DOCS for all passengers in the same record:
PW1,DOCS/ALL

Page 84
Entry:
PW1,DOCS/ALL
Response:
PDD:01
PDD: XS060/11JANYATL,01
1. MCCOLM/A MR
BN009 SN35K
Y YYZ M1/88 F1/70
DOCA-D/CAN/222 LEE ST/TORONTO/
DOCS-P /CAN/9483938/CAN/12JUL64/M /15OCT05/MCCOLM/ALLEN//
MCCOLM/B MRS
BN010 SN35J
Y YYZ
DOCA-D/CAN/222 LEE ST/TORONTO/
DOCS-P /CAN/2191929/CAN/12JUL65/F /15OCT05/MCCOLM/BETH//
ACC VDT2110 AGT877/11JAN1117/P1/SN35K
ACC VDT2110 AGT877/11JAN1117/P2/SN35J
Note: The above procedures for deletion are DOCS are the same required for deletion of DOCA and
DOCO.
8.2.12.3DOCA - Address Information
Different governments require UN Paxlist information based upon the passengers residence or
destination address, both residence and destination address, or the passengers country of residence.
The passenger address information is defined in the element type:
Residence Address
Destination Address
Edits for the DOCA entry are as follows:

DOCA Entry
Edit
Check-in code
PA or PU
Pax Entry #
Special Service Requirements (SSR) code
DOCA
Type of address
R = Residence
D = Destination
Destination or Residence of Country
Two Three letter country code
Address Details
10 Peachtree Road
City
Atlanta
State/Province/County
GA
Postal or Zip Code
30330
Infant Indicator
Table 8.7 DOCA Entry Edits

Checking in Passengers with a Destination or Residence Address
8. Accept a passenger on to the flight and redisplay the passenger record:
PDD:01

Page 85
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
9. Add the destination address to this passengers record using the PU entry:
PU1,DOCA/D/USA/10 PEACHTREE ST/ATLANTA/GA/33030
The PDD now includes the destination address in the passenger record.
PDD:01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
PU
VDT2110 AGT877/03MAR1306/DOCA
10. Using the same passenger we will add a country of residence with no additional address
information with the following entry:
PU1,DOCA/R/DEU
Redisplay the passenger record to see it contains the DOCA entry with the country of residence.
PDD:01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
DOCA-R/DEU//
PU
PU
Adding Infants Address Information
Infants may require:
destination address
residence address
country of residence
The DOCA entry for infants is almost identical to adults with one exception. An /I is added to the end
of the entry to identify the infant.
An infant has been added to the previous passenger record in order to demonstrate how to add an
infant passport.
11. Display the passenger record:
PDD:01

Page 86
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN31J S Y ATL OKT INF1/10 M1/80
INF-GRETCHEN
DOCA-R/DEU//
PU
PU
PU
12. The following entry adds a destination address for the infant:
PU1,DOCA/D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
13. An infant destination address now displays in the passenger record:
PDD:01
PNR RL 92K292
1. PETRALLI/INGE
INF-GRETCHEN
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
PU
PU
PU
PU
14. We will also add a country of residence for the infant to the passenger record with the following
entry:
PU1,DOCA/R/DEU/////I
Note: It is mandatory to add five slashes between the country of residence and the infant indicator
when adding country of residence only.
15. Display the passenger record to verify that the infant country of residence was added to the
passenger record, enter:
PDD:01

Page 87
To display:
PNR RL 92K292
1. PETRALLI/INGE
INF-GRETCHEN
DOCA-R/DEU//I
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
PU
PU
PU
PU
PU
8.2.12.4DOCO (Other Travel Related Information) Information

Visa and Place of Birth are elements that may be included as part of Other Travel Related Information.
A Visa is considered a secondary travel document and must be used in conjunction with a primary
document.
Edits for the DOCO entry are as follows:
DOCO Entry
Edit
Check-in code
PA or PU
Pax Entry #
Special Service Requirements code
doco
Passenger Place of Birth
Sydney AUS
Document Type
Document number
Up to 15
alpha/numerics
Document Place of Issue
City where VISA was

issued
Document Date of Issue
15DEC05
Country for which VISA is applicable
Two Three letter

country code
Table 8.8 DOCO Entry Edits

Page 88
Checking in Passengers with Place of Birth and VISA information

16. Accept a passenger on a flight and redisplay the record, enter:
PDD:01
To display:
PDD: XS1548/03MARFMEX,01
PNR RL DK29D2
1. FIELD/DONALD
BN004 SN3J S F ATL OKT M1/80
17. Add place of Birth and VISA information using the following:
PU1,DOCO/SYDNEY AUS/V/AB54321/SYDNEY/15DEC05/USA
18. The PDD now contains Place of Birth and VISA information, enter:
PDD:01
To display:
PNR RL DK29D2
1. FIELD/DONALD
BN004 SN3J S F ATL OKT M1/80
DOCO-SYDNEY AUS/V/AB54321/SYDNEY/15DEC05/USA/
PU
VDT2110 AGT877/03MAR1449/DOCO
Adding Infants Place of Birth and VISA Information
Infants may require a VISA. The DOCO entry for an infant is almost identical to adults with one
exception. An /I is added to the end of the entry to identify the passenger as an infant.
An infant was added to the previous record to demonstrate how to add an infants place of birth and
VISA information.
19. Accept the infant on a flight and redisplay the record, enter:
PDD:01
To display:
PNR RL DK29D2
1. FIELD/DONALD
BN004 SN2D
F ATL OKT INF1/10 M1/80
INF-JOHN
PU
PU
20. The following entry adds place of birth and VISA information to the infant:
PU1,DOCO/SYDNEY AUS/V/CD1234567/SYDNEY/15DEC05/USA/I

Page 89
21. The PDD now displays the infant Place of Birth and VISA information, enter:
PDD:01
To display:
PNR RL DK29D2
1. FIELD/DONALD
BN004 SN2D
F ATL OKT INF1/10 M1/80
INF-JOHN
DOCO-SYDNEY AUS/V/CD1234567/SYDNEY/15DEC05/USA/I
PU
PU
PU
8.2.12.5Entries to List Passengers with DOCS, DOCO or DOCA Information
To identify passengers with travel document information:
DOCS
22. Enter Flight/Date,DOCS.
PS:218/.,DOCS
The response is a list of all passengers with DOCS information.
PS: 2M218/27FEB CDG,DOCS
OP/NAM
757/200
GTD/???? POS/GATE BDT2230 SD2300 ED2300+1 SA0600+1 FT1300
1. 1HERNANDEZ/LMR
BN004 SN36F
Y ATL DOCA DOCS
2. 3MOUSSA/AMR
BN001 SN13C
Y ATL O DOCA DOCO DOCS
MOUSSA/BMR
BN002 SN13B
MOUSSA/CMRS
BN003 SN13A
3. 1YAGO/CRMS
BN005 SN25F
Y ATL DOCA DOCS
DOCA
23. Enter Flight/Date,DOCA.
PS:218/.,DOCA
The response is a list of all passengers with DOCA information.
PS: 2M218/27FEB CDG,DOCA
OP/NAM
757/200
1. 3MOUSSA/AMR
BN001 SN13C
MOUSSA/BMR
BN002 SN13B
MOUSSA/CMRS
BN003 SN13A

Page 90
DOCO
24. Enter Flight/Date,DOCO.
PS:218/.,DOCO
The SITA DCS system provides a listing of passengers on the flight and date who have DOCO travel
document information available. For example:
PS:218/-,DOCO
PS: 2M218/27FEB CDG,DOCO
OP/NAM
757/200
1. 3MOUSSA/AMR
BN001 SN13C
MOUSSA/BMR
BN002 SN13B
MOUSSA/CMRS
BN003 SN13A
8.2.12.6Entries to List Passengers Missing DOCS, DOCO or DOCA Information
To identify passengers missing travel document information:
25. Enter Flight/Date,NDOCS.
PS:1548/.,ndocs
The SITA DCS system displays a listing of passengers on the flight and date who are missing DOCS
travel document information.
ps1548,ndocs
PS: XS1548/06MAR MEX,NDOCS

D10/LORI GTD/???? POS/GATE BDT2130 SD2200 ED2200
SA2345
FT0045
1. 1AKRAWUTTICHA/A M+G2
SN28J
Y ATL RES PSPT
2. 1CLEAVER/WARD
Y ATL PSPT DOCA
3. 1HUYNHBAINHI/MRS
Y ATL PSPT DOCA DOCO
4. 2MCEWAN/JOHN+
Y ATL PSPT DOCA
MCEWAN/LYBE+
Y ATL PSPT DOCA
5. 2MCGARRY/M MR+
Y ATL DOCA
MCGARRY/J MR
Y ATL PSPT DOCA
OP/NAM
To identify passengers missing address information:

26. Enter Flight/Date,NDOCA.
PS1548/.,NDOCA
A list of passengers on the flight and date who are missing DOCA travel document information
displays.
PS: XS1548/06MAR MEX,NDOCA
SA2345
FT0045
1. 1AHMED/MMKY+
Y ATL O DOCS
SN28J
Y ATL RES PSPT
3. 1APPLE/GOLD+
Y ATL PSPT DOCO DOCS
4. 1BASHIR/RAZI+
G2
SN16J
Y ATL RES PSPT DOCS
OP/NAM

Page 91
To identify passengers missing Visa or Place of Birth:

27. Enter Flight/Date,NDOCO
PS1548/.,NDOCO
A list of passengers on the flight and date who are missing DOCO travel document information
displays.
PS: XS1548/06MAR MEX,NDOCO
SA2345
FT0045
1. 2AHMED/CHOW+
Y ATL DOCA DOCS
AHMED/AZWA+
Y ATL DOCA DOCS
2. 1AHMED/MMKY+
Y ATL O DOCS
SN28J
Y ATL RES PSPT
4. 1BAGIROVA/ELVI+
Y ATL DOCA DOCS
5. 1BASHIR/RAZI+
G2
SN16J
Y ATL RES PSPT DOCS
OP/NAM
8.2.12.7Error Responses for DOCS, DOCA, DOCO

Error Message
Definition
ADDRESS CODE REQUIRED
No address type code was entered the DOCA field.
BIRTHDATE REQUIRED
Date of Birth was not entered in the DOCS field.
COUNTRY CODE REQUIRED
An address was entered and no country code was included

in the entry for the DOCA or DOCO field.
DOCUMENT NUMBER REQUIRED
A document number was not entered in either the DOCS or

DOCO field.
EXCEEDS MAXIMUM NUMBER OF

CHARACTERS
The maximum number of characters for a field is exceeded.

The maximum number of characters may vary per field.
EXPIRY DATE REQUIRED
The expiration date of the travel document was not entered

in the DOCS field.
GENDER REQUIRED
The gender of the passenger or crew was not entered in the

DOCS field.
INVALID ADDRESS CODE
A code other than an "R" or "D" was entered the DOCA field.
INVALID COUNTRY CODE
A country/state code was entered that is invalid or does not

exist.
INVALID DOCUMENT CODE
A non-standard IATA document type code was entered in

the DOCO or DOCS field.
ISSUE DATE
A Visa Date of Issue is missing or an invalid date format was

entered in the DOCO field.
ISSUING COUNTRY/STATE
A valid three-letter country code was not entered in the

DOCO field.
NATIONALITY REQUIRED
A three-letter nationality code was not entered n the DOCS

field.
NEED DOCUMENT TYPE CODE
No document type code was entered in the DOCS field.
NEED PLACE OF ISSUE
Place of issue was not entered in the DOCO field.
NEED TRAVEL DOCUMENT GIVEN

NAME
The given name as it appears on the travel document was

not entered in the DOCS field.
Page 92
NEED TRAVEL DOCUMENT

SURNAME
The surname as it appears on the travel document was not

entered in the DOCA or DOCS field.
INFANT INDICATOR
Only I is valid indicator.
INVALID DOCUMENT TYPE (DOCS)
Only P, A, C, I, AC, IP, F are valid types.
INVALID DATE
Date not in format of ddmmmyy (19APR04)
INVALID GENDER
Only F = Female, M = Male, FI = Female Infant, MI = Male

Infant allowed.
Note: U = Unknown is allowed on PNL but is not allowed
during check-in or update.
INVALID VISA CODE
Only V is valid indicator.
Table 8.9 Error Responses for UN Paxlist

8.2.13 Passport Information at Check-In Time
Passport information in a passenger record may be entered at the time a passenger checks in at the
airport. Airport staff may add passport information for passengers that do not have a PSPT item in
their record from reservations in the same transaction used to check in the passenger.
PA Use and Restrictions
The PA transaction may be used to add initial passport information with a PSPT item. If a PSPT item
is already present in a passenger record, a PSPT item is not allowed with a PA transaction.
PA Input
The PSPT item is input with the PA transactions as other passenger handling items in the following
format:
PA:entry nbr,bags,PSPT/passport details
Details for the PSPT item are listed in the order below. All items (numbered 1 thru 8) are followed by
an oblique.
PSPT/
Mandatory
1. passport number
Mandatory
Maximum 35 characters.
2. IATA country code of issue
Mandatory
Two- or three-alpha characters.
3. date of birth
Mandatory
Day/month/year (e.g., 01JAN50).
4. gender code
Mandatory
M-male F-female.
5. surname
Mandatory
6. first name
Mandatory
7. expiration date
Optional
Day/month/year (e.g., 01JAN06).
8. Nationality
Mandatory
Two- or three-alpha characters.
All passport details are followed by an oblique. If the optional field of expiry date is omitted, obliques
will be consecutive. For example a passenger with a PSPT remark where the expiration date is
omitted is input as shown below:
PA1,1/10,B,PSPT/F/P094158760/US/22MAR57/F/SMITH/MARY//US
1 Example of the PSPT item with all details entered.

Page 93
PA:1,1/10,B,PSPT/P/P04126490/US/20AUG65/M/SMITH/JOHN/01JAN06/US
1 Example of an input for a NREC passenger.

PA:XS100F1TOLSON/MR,1/10,B,PSPT/P/P87638121/US/03APR43/M/TOLFSON/JAMES/20D
EC70/US
To input an infant passport, the code PSPTI is required. Using the PSPT code with the I attaches the
passport information to the infant(s). The number of PSPTI remarks cannot exceed the number of
infants in the party. An example of an input for a passenger traveling with an infant is shown below.
PA:1,1/9,B,INF1SUE,PSPT/P12328/US/20JUN57/F/SMITH/MARY/29JAN10/US,PSPTI/P1
2328/US/18JUN07/F/SMITH/SUE/29DEC20/US
To attach passport remarks on specific passengers in a multi-passenger record, the PSPT item may
be used with a number to correspond with the order of the passenger within a single passenger
record.
Example of a multiple passport entries for a family of 2JONES/MR/MRS.
PA1,3/33,B,PSPT1/A1238564/US/20JUN50/M/JONES/MICHAEL/16MAR10/US,PSPT2/A546
3245/US/03JUL57/F/JONES/MARY/19APR12/US
The entry should be in the same order as the first names, i.e., in this case A1238564 is Mr. Jones' and
A5463245 is Mrs. Jones'.
Error Responses
In addition to the existing error responses for the PA transaction, the following error responses apply.
Response
Explanation
Country
The country of issuance or nationality is missing from the PSPT input.
Date
A date is missing from the format of the PSPT input.
Gender Required
The gender is missing from the PSPT input.
Number
The passport documentation number is missing from the input.
Name Required
The surname or given name or both are missing
Nationality Required
Nationality is missing
Table 8.10 Passport Information at Check In Error Responses

.

Page 94
8.2.14 Adding PSPT after Initial Check-in

The PU transaction can add initial passport information to a passenger record with a PSPT item after a
passenger has been accepted on the flight, or to amend existing PSPT information. An OCR
document scanner can accept PSPT information.
PU Use and Restrictions
A PU transaction requires a prior PDD or PS display.
If a PSPT item is already present in a passenger record but needs to be updated with a new PSPT
item, a PW entry will need to be used to delete to the old PSPT item and then updated using the PU
entry.
PU Input
The PSPT item is input with the PU transaction as are other passenger handling items in the following
format:
PU: entry nbr,PSPT/passport details
Details for the PSPT item are listed below. An oblique follows all items (numbered 1 thru 8).
PSPT/
Mandatory
1. passport number
Mandatory
maximum 35 characters
2. IATA country code of issue
Mandatory
Two or three-alpha characters
3. date of birth
Mandatory
da/mon/yr (e.g., 01JAN50)
4. gender code
Mandatory
M - male
F - female
5. surname
Mandatory
6. first name
Mandatory
7. expiration date
Optional
da/mon/yr (e.g., 01JAN06)
8. Nationality
Mandatory
Two or three-alpha characters
Example of the PSPT input on a passenger without an expiry date:

An oblique follows all passport details. If the optional expiry date is omitted, obliques are
consecutive. For example a passenger with a PSPT remark where the expiration date is
omitted:
PU:1,PSPT/P094158760/US/22MAR57/F/SMITH/MARY//US
Example of the PSPT item added with all details entered.
PU:1,PSPT/P04126490/US/20AUG65/M/SMITH/JOHN/01JAN06/US
If an OCR document scanner processes the passports, then the PSPT item is input with the PU
transaction in the following format:
PU:flt nbr/dateSB nbr or BN nbr,PSPT/document type/passport details
PU:XS123/.BN019,PSPT/P/L12345/US/23JUN67/F/JONES/RACHEL/29JUN10/US
Table 8.11 Passenger Update at Check In Error Responses
8.2.15 PSPT DOB FOR WATCHLIST
PSPT DOB is available for use with the US and Canadian watchlist when PSPT or DOCS is not
required but DOB is necessary for Watchlist clearance. The PSPT code B is used when using the
PSPT entry for DOB only.
Page 95
1 Example of the PSPT DOB entry:

PA:1,PSPT/B/20AUG65/SMITH/JOHN
PSPT DOB can also be used for an infant by adding an I after PSPT.
1 Example of the PSPT DOB entry for an infant:

PA:1,PSPTI/B/20AUG65/SMITH/ANGELA
8.2.16 Deletion of PSPT Remark
The PW transaction can delete a PSPT item from a passengers record.
PW Use and Restrictions
The PW transaction is allowed after a prior PS, SB or PDD display.
.
PW Input
A PW transaction can delete a PSPT item from a passengers record with the following format:
PW:1,PSPT/ALL
1 Example of a transaction to delete one of the PSPT items on multi-passenger record.

PW:1,PSPT/1
1 Example of a transaction to delete PSPT items from passengers one, three and four of a
passenger record.
PW:1,PSPT/1/3/4
1 Example of a transaction to delete all the PSPT items from a multi passenger record.
PW:1,PSPT/ALL
Processing
The PSPT item is deleted from the passengers record is included in the PDD transaction for a specific
passenger or passengers. The PDD history includes deletion of the PSPT item, within the current
design of the PDD history.
PW Output
The output for a successfully completed PW transaction is a passenger status response display.
There is no change to the existing response.
Error Responses
Response
Explanation
Format
The format of the PSPT deletion is incorrect.
Modification Not Possible
There is not a PSPT item to delete in this passenger record.
Table 8.12 Delete PSPT Remark Error Responses

Subsequent Processing
All processing not specifically mentioned remains unchanged.

Page 96
8.2.17 Passenger Handling Displays

PS Display
Passengers with passport remarks are easily identified with the PSPT items on the PS display for each
passenger having passport remarks.
PS Input
1 An example of the PS input, with PSPT as the option.

PS:FLT/DATE/CLASS,PSPT
PS Output
1 An example of a PS list sorted with the PSPT item is shown below:

PS: XS500/29AUGXATL,PSPT
DC9/JRAM
GTD/????
POS/GATE
1. 2CHARLES/MR
CHARLES/MRS
2. 2CURIE/PIER+
CURIE/MADA+
3. 1DOUGLAS/KIRK
4. 1EINSTEIN/ALBE+
BDT1730
SD1800
BN002 SN27C
BN003 SN27B
BN001
SN14F
Y
Y
Y
Y
Y
Y
OP/NAM
ED1800
JFK MSG PSPT
JFK PSM
JFK PSPT
JFK PSPT
JFK PSM MSG PSPT
JFK PSPT
8.2.18 PDD Display

Each passenger record shows the PSPT remark, much as the other special remarks or items are
displayed.
1 An example of the output when a PSPT item is present in the passenger record is shown below.
PDD:1
PDD: XS500/26AUGYATL,1
1. CHARLES/MR
BN004 SN10C
Y MSP
CHARLES/MRS
BN005 SN10B
Y MSP
ACC VDT965 AGT1/26AUG1406
PSPT-CHARLES/RAYMR/P123456/GB/01JAN50/M/01JAN06
CHARLES/RAYNELMR
BAG1/10/0
8.2.19 Boarding Pass Inhibit for APIS Flights

The ability to inhibit boarding pass issuance until all required APIS data is entered in the passengers
record is available on all APIS flights. The SITA Helpdesk should be contacted to set the Boarding
Pass Inhibit parameter. In addition, segment data for the city pairs requiring boarding Pass inhibit
should be added to the CSM for each flight requiring this function. For information on adding segment
data to the CSM see the Check-in Supervisor User Guide.
8.2.19.1Crew Mask Entries

Some countries may require travel document and other information for crew members. This
information can be added to the crew mask.
The following entry displays the crew mask:
CREW:XS 1548/.
1 The crew list for the flight and date displays.:

CREW:XS1548/06MAR06 /ATL
Delete crewman:_

Page 97
*Personal Information
Surname:________________________________________
Given/Middle Name:___________________ /_________________________
Gender:_
Nationality:___
Birth date:_______
PCTC: ______________________________________________________________
Residence country:___ Address Details:___________________________
ZIP/Postal Code:____________
City:_________________________________
State/Province/Country:_______________________________
Final Destination:___
Crew Status:___
Birth Place:_____________________________
Crew Title:_________________________
*Document Information
P = Passport
C = US Resident card
M = Military-ID T = US Re-entry permit A = Alien registration card

Document type:___
Expiration date:_______
Country of issue:___
Document Number:__________________________________________
VISA Number:________________________
Issued for country:___
VISA Issue Date:_____ Place of Issue:_____________________________

Airline or Gov Override Indicator (APP only):_
Override Country:___
Authorized By:___________________________________________________
*Pilot Information (UN PAXLST only)
License number:________________

Page 98
1 Add required information to the crew mask for the country you are sending to:
CREW:XS 1548/06MAR06 /ATL
_
Delete crewman:
Surname: SMITH___________________________________
Given/Middle Name: JOHN______________ / _______
Gender: M
Nationality: USA
Birth date: 29JAN65_______
PCTC: 1234567890_____________________________________________________________
Residence country USA
Address Details: 10 ANY ST__________________________
ZIP/Postal Code: 12345__________ City: ATLANTA____________________________
State/Province/Country: GA USA_____________________________
Final Destination: ATL
Birth Place: USA+ATLANTA+GA_____________________
Crew Status: CR1
Crew Title: CAPTAIN_____________________
P = Passport
Document type:
P__
Expiration date: 23AUG08
Country of issue: USA
Document Number: 938498988__________________________
VISA
Number: ________________________________ Issued for country: ___
VISA Issue Date: _____ Place of Issue: ___________________________________
Airline or Gov Override Indicator (APP only): _
Override Country: ___
Authorized by:______________________________________________________________
License number: 9389898_____________
Country of issue: USA
Crew information will vary according to government requirements. Above is an example of a

completed crew mask based on inbound flight requirements for the US.
To display a list of crew members, us the PS entry:
PS:FLT/DTE,CREW
PS:1548/.,CREW
-PS: XS1548/06MAR MEX,CREW

OP/NAM
747/SP
1. 1SMITH/JOHN
SA1400
FT2001
! JFK PSPT PCTC DOCA DOCO DOCS
The crew records can be displayed either by the PDD or the Crew Mask using the following entries:
To display the PDD:
PDD:NBR
PDD:01

Page 99
1 PDD displays as follows:

PDD:01
PDD: XS1548/06MAR!MEX,01
PNR RL CREW
1. SMITH/JOHN
! ATL
PCTC-1234567890
CREW-
/CR1/CAPTAIN
LICENSE-USA/9389898
APP DOCA-R/USA/10 ANY ST/ATLANTA/GA USA/12345/
DOCO-USA+ATLANTA+GA/V/
DOCS-P /USA/938498988/USA/29JAN65/M /23AUG08/SMITH/JOHN//
PSPT-P/938498988/USA/10JAN65/M/SMITH/JOHN/23AUG08/USA
To display the crewmember by mask: CREW:NBR
CREW:XS 1548 /06MAR06 /ATL
Delete crewman:_
Surname:SMITH___________________________________
Given/Middle Name:JOHN______________ /___________________________
Gender:M
Nationality:USA
Birth date:29JAN65
PCTC:1234567890_____________________________________________________
Residence country:USA
Address Details:10_ANY_ST_________________
ZIP/Postal Code:12345_____
City:ATLANTA__________________
State/Province/Country:GA_USA_______________________
Crew Status:CR1
Birth Place:USA+ATLANTA+GA____________
Crew Title:CAPTAIN___________________
P = Passport

Document type:P__ Expiration date:23AUG08
Country of issue:USA
Document Number:938498988__________________________
VISA Number:____________________________
VISA Issue Date:____
Place of Issue:________________________
Airline or Gov Override Indicator (APP only):_Override Country___

Authorized by:______________________________________
License number:9389898____

Page 100
To delete a crewmember, pull up the crew mask by the number on the PS List. Enter Y in the Delete
Crewman line:
CREW:1
CREW:XS 0047 /13SEP07 /JFK
Delete crewman:Y
Surname:SMITH___________
Given/Middle Name:JOHN_______________ /______________________
Gender:M
Nationality:USA
Birth date:10JAN65
PCTC:1234567890_________________________________________________
Residence country:USA
Address Details:10_ANY_ST______________
ZIP/Postal Code:12345______ City:ATLANTA____________________________
State/Province/Country:GA_USA________________
Birth Place:USA+ATLANTA+GA_____________
Crew Status:CR1
Crew Title:CAPTAIN___________________
P = Passport

Document type: P__
Expiration date:23AUG08 Country of issue:USA
Document Number:938498988__________________________
VISA Number:__________________
VISA Issue Date:_______
Place of Issue:__________________________
Airline or Gov Override Indicator(APP only):_ Override Country:___

Authorized by:_________________________________
License number:9389898_______
8.2.20 Advanced Passenger Processing System (APP)

Every passenger traveling into, out of, or through an Advanced Passenger Processing (APP) country
is screened for authorization to board before a boarding pass is issued. This can include travel
inbound to, outbound from or transiting an APP participating country. At this time the participating
countries are Australia, New Zealand, Kuwait and Bahrain. The flight data can include information on a
series of flights and ports on an international itinerary. The APP can involve passengers traveling on
up to three separate flights and four separate ports.
Passengers traveling to, from or through an APP country require a PA transaction to CPS seeking
authorization to board. All messages received by the CPS must be for a flight that is known to
them.
Agents can modify passport data in a passenger record prior to a check-in transaction.
Passengers without authorization to board will not receive a boarding pass and the agent will be
prompted to delete the passenger.
The system checks applicable Passenger Acceptance, Passenger Update, and Passenger Withdrawal
transactions for an APP airline parameter and to which country the travel will involve. The system then
Page 101
determines if either of the city pair (to/from) is in the APP participating country, and if the response is
yes a message for PA, PU, or PW is generated.
8.2.21 Check-In
8.2.21.1 To Check Single Passengers:
Use the PS List, for example:
xs7777,namSMITH
-PS: xs7777/10OCT SGN,NAMSMITH
OP/NAM
320/A
1. 1SMITH/JOHN
Y SYD
-
SA2300
FT0800
The normal passenger check-in entry is:

PA:1, DOCS/P/USA/T67778/USA/12jul67/M/12JUL15/SMITH/JOHN
Note: To trigger the APP query DOCS or PSPT entries can be used.
8.2.21.2 To Check Multiple Passengers:
Use the PS List (e.g., PS:XS123/., NAMBERRY;NAMALVAREZ):
ps123/+,NAMBERRY;NAMALVAREZ
-PS: XS123/11OCT SGN
OP/NAM
320/A
1. 1ALVAREZ/JOSE
Y SYD
2. 1BERRY/JOHN
Y SYD
SA2300
FT0800
-PA1,0/0,DOCS/P/USA/T67778/USA/12jul67/M/12JUL15/ALVAREZ/JOSE;2,
- DOCS/P/USA/T67234/USA/13SEP70/M/13SEP15/BERRY/JOHN
8.2.21.3 Checking a Passenger without PSPT or DOCS data:
If an agent attempts to check in any passenger(s) where PSPT or DOCS data is not present, the
PSPT DATA REQUIRED error response returns.
-PA: XS123/11OCTYSYD3,0/0
AV C12Y135
PAD C0Y0
320/A
1. SMITH/JOHN
BN003 SN21D
SA2300
FT0800
WARNING - APP FLIGHT - PSPT DATA
The PSPT or DOCS data can be added after the passengers is checked-in with the PU
transaction, however this alone does not trigger the APP query; therefore another PU transaction
needs to be done to send the APP query.

Page 102
Ps123/+,NAMSMITH
-PS: xs123/11OCT SGN,NAMSMITH
OP/NAM
320/A
SA2300
1. 1SMITH/JOHN
BN003 SN21D
Y SYD APP
FT0800
-PU:1,DOCS/P/USA/T67778/USA/12JUL67/M/12JUL15/SMITH/JOHN
-PU: XS123/11OCTYSYD1,DOCS/P/USA/Y67778/USA/12JUL67/M/12JUL15/SMITH/JOHN
AV C12Y135
PAD C0Y0
320/A
SA2300
FT0800
1. SMITH/JOHN
BN003 SN21D
ps123/+,NAMSMITH
-PS: XS123/11OCT SGN,NAMSMITH
OP/NAM
320/A
SA2300
1. 1SMITH/JOHN
BN003 SN21D
Y SYD DOCS APP
-PU:1,APP
-PU: XS123/11OCTYSYD1,app
AV C12Y135
PAD C0Y0
320/A
SA2300
1. SMITH/JOHN
BN003 SN21D
APP TRANSACTION IN PROGRESS
AU APP* (0502) OK TO BOARD/BN3
FT0800
FT0800

Page 103
8.2.21.4 Check-in of Multiple Passengers - Partial Acceptance by CPS System.

Boarding pass printing is suppressed for any passenger not receiving authorization to travel.
1 Example: Where one passenger receives OK and the other Not OK:
1.
2.
SMITH/TMR
BN050
SN14A
*Australia APP * OK TO BRD/BN050
TALBOT/KMRS
Australia APP
BN051
SN14B
* DO NOT BRD/BN051
*Australia APP Transaction in Progress

***Delete passenger***
PW-2,APP
In this case, the boarding pass for BN050 is printed, but not for BN051. The response from CPS
System displays under each passenger name.
In addition the symbol PW-2,APP (for second passenger) transaction is presented to delete the
passenger, if necessary.

Page 104
After SDCS sends the APP queries, the CPS system generates an appropriate response from the
following list:
Response
Explanation
OK TO BRD
All data required to assess the passenger is available and the

passenger is granted clearance to board.
DO NOT BRD (D)
All data required to assess the passenger is available but the directive
from the country indicates that the passenger is not permitted to board.
After consultation with a government authority or a determination by the
check-in agent that the passenger conforms to requirements of a
special category of traveler according to the countrys regulations, the
Do Not Board directive may be overridden by the check-in agent.
DO NOT BRD (X)
All data required to assess the passenger is available and the

passenger is denied clearance to board. The check-in agent cannot
override this directive.
Miscellaneous Messages (U)
Unable to determine the passenger status. The passenger identity

cannot be uniquely determined because multiple records match the
supplied data or there is a problem with database. Supply more
specific passenger data to allow the system to assess the passenger. If
this fails, get advice from the government agencies.
Miscellaneous Messages (I)
Insufficient data is available for an assessment. Provide additional

passenger data.
Miscellaneous Messages (E)
Error is detected. Correct the error.
Table 8.13 APP Query Responses

Page 105
8.2.21.5 Passenger Cancellation

Normal DCS processing for a PW applies.
1 Example of cancellation of a previous APP (ok to board) passenger:

-pw:-1
-PW: XS7777/20OCTYSYD-1
AV C12Y138
PAD C0Y0
320/A
1. SMITH/JOSEPH
DELETED
AU APP* (8505) CANCELLED/BN1
SA2300
FT0800
8.2.21.6 Limits on Number of Passengers

The APP application allows queries for up to five passengers at a time. Thus, if the Airline
configuration for APP is set, SDCS will not check in more than five passengers at a time. For PW the
limit is the same.
If more than the limit is attempted, SDCS returns:
(For PA or PU) Country Name APP Flight, 5 passenger maximum group size.
(For PW) Country Name APP Flight, 5 passenger maximum group size.

Page 106
8.2.21.7 Standbys
All PA entries result in an APP message being sent, however, if the passenger is not accommodated,
but placed on standby, he does this with the benefit of being pre-approved. If the APP message is
negative, the agent is notified and can take the appropriate action.
Response (positive) :
* AUSTRALIA APP TRANSACTION IN PROGRESS
PDD: VN516/19JULYHAN,1
1. QUINCY/QUINT
SB0222
APPB-AU /8501/OK TO BOARD
-
LMTS Y MEL URES IDID00S101
Or if the response is negative:

*
AUSTRALIA APP TRANSACTION IN PROGRESS
PDD: VN516/19JULYHAN,1
1. QUINCY/QUINT
SB0222
LMTS Y MEL URES IDID00S101
APPI-AU /8513/DO NOT BOARD - PAX NOT KNOWN
***Uncheck passenger***
PW

Page 107
8.2.21.8 Override
To override Do not board passengers the transaction is the following:
PU:1,APPG/AU/FREE TEXT
PU:1,APPA/AU/FREE TEXT
AV C12Y137
PAD C0Y0
320/A
SA0600+1 FT0400
1. ADAMS/BILL
BN001 SN26C
*SYD* ***PAX:NGOTHANHLAN(TOI PHAM)->GOI CACK--KT KY VSA/PSPT + TIETAB
RATE NOT FOUND. NO JCD TABLE ENTRY FOR THIS DESTINATION: SYD
-EXB:1/SPCH/CASH/VND0.0
AU APP* (8502) DO NOT BOARD/BN1
**Delete -DO NOT BOARD- Passenger(s)
-PW:-pu:1,appg/au/free text
-PU: VN7777/20JULYSYD1,appg/au/free text
AV C12Y137
PAD C0Y0
320/A
SA0600+1 FT0400
1. ADAMS/BILL
BN001 SN26C
*SYD* ***PAX:NGOTHANHLAN(TOI PHAM)->GOI CACK--KT KY VSA/PSPT + TIETAB
AU APP* (8517) MAY BOARD
- OVERRIDE ACCEPTED/BN1
-
Note: To override infants, the transaction is the following:

PU:1,INFAPPG/NZ/FREE TEXT
PU:1,INFAPPA/NZ/FREE TEXT

Page 108
8.2.21.9 Re-sending APP Message

To clear some of the passenger status we can try to re-send the APP message with the following
transaction after PDD display:
PU:1,APP
pu:1,app
-PU: XS781/21JULLMEL1,app
AV C25Y281
PAD C0Y0
777/77C
SA0835
FT1235
1. BRAVO/ROSALYN +B2 BN001 SN16G
SGN PSM
SN31K
MEL
PSM- CTCH-SGN-GRAND HOTEL-04JUL OUT 10JUL CTCH-DLI-EMPRESS HOTEL-10JUL OUT
12JUL CTCH-HOI AN-HOI AN HOTEL-12JUL OUT 15JUL CTCH-HAN-SUNNY HOTELIN
15JUL OUT 21JUL
EQ CHG SGN
AU APP* (8510) DO NOT BOARD - CONTACT EOC/BN1
-PW:-
8.2.21.10 Status Codes

After check-in the passengers can have the following status:
APPB The passenger has been given clearance to board. (Screen message OK to BRD).
APPD The passenger is not to be permitted to board. After a consultation with governments
authorities or a determination by the check-in supervisor that passenger conforms to the
requirements according to the regulation of the country, the boarding directive may be overridden
by the check-in supervisor. (Screen message DO NOT BRD).
APPU Unable to determine the status of the passenger. Multiple records have been found
matching the data supplied. More specific bio-data must be supplied. (Screen message: Will vary
depending on conditions).
APPI Insufficient data is available. (Screen message: Will vary depending on conditions).
APPE An error condition has been detected. All error conditions must be corrected before
processing. (Screen message: Will vary depending on conditions).
APPP The message going or coming back was lost and response is pending. Try to re-send.
Note: If any passenger has status D / U / I / P or E, the check-in supervisor will not be able to close
the flight. All conditions must be corrected before being able to close the flight.

Page 109
8.2.21.11 DFL Prohibited

DFL for any APP flight is prohibited. If a DFL is attempted for an APP flight where check-in has taken
place, the following warning will be displayed:
DFL:781/./ALL
805 - APP FLIGHT - DFL NOT PERMITTED
Note: Contact SITA Helpdesk staff to DFL any APP flight.
8.2.21.12 CREW Check-in
APP will be sent when the crew mask is completed and entered after the required fields. If an override
is necessary the information is entered as shown below in the example:
CREW:MH 0141 /19MAR08 /SYD
Delete crewman:_
Surname: PILOT______ Given/Middle Name: JOHN_ /_____________
Gender: M
Nationality:AUS
Birth date:10JUN65
PCTC: ______________________________________________________________
Residence country: AUS
Address Details:10_ANY_ST____________________
ZIP/Postal Code: 54331____________ City: SYDNEY_______________________
State/Province/Country: AUS___________________
Final Destination: SYD
Birth Place: AUS______________________
Crew Status: CR1
Crew Title: PILOT___________
P = Passport
Document type: P__
Expiration date: 22JUN10
Country of issue:AUS
Document Number: 49842938498________________________
VISA
Number: __________________________ Issued for country: ___
VISA Issue Date: _______ Place of Issue: _____________________________
Airline or Gov Override Indicator (APP only): G
Override Country: AUS
Authorized by:PER_AU_AUTH_221321_______________________________
License number: ____________________
8.2.22 AQQ
AQQ, APIS Quick Query, is currently being introduced by the US Government. AQQ has similarities to
APP as it allows for immediate clearance of passengers upon check-in using a PA or PU entry.
Passengers will receive one of three responses when an agent attempts acceptance of the passenger.
These responses are OK TO BOARD, DO NOT BOARD CONTACT CBP or SELECTEE status.
8.2.22.1Passenger Check-in and Update
Below is an example of an AQQ transaction using Passenger Acceptance (PA) receiving an OK TO
BOARD response:
PS:XS123,NAMSOLE
_PS: XS123/21FEB JFK,NAMSOLE
767/B
SA2200
1. 1SOLENKO/VIKA+
Y KBP ADV-PU/NP DOCA DOCS APP
PA1,0/0
PA: XS123/21FEBYKBP1,0/0
1. SOLENKO/VIKARO
BN012 SN14C
NOTIFIED
NO EXCESS BAGGAGE INFORMATION
_APP_ TRANSACTION IN PROGRESS
US APP* (8501) OK TO BOARD/BN12
OP/NAM

Page 110
Below is an example of an AQQ transaction using Passenger Acceptance with a NO-FLY status:
PS:XS123,NAMALEX
_PS: XS123/21FEB JFK,NAMALEX
767/B
1. 1ALEXANDER/CREW+
Y KBP DOCA DOCS
PA1,0/0
1. ALEXANDER/CREWE
BN001 SN25A
US APP* (8540) DO NOT BOARD - CONTACT CBP (US)/BN1
_PW:-
OP/NAM
SA2200
When receiving a No-FLY response, the agent should contact the US authorities. AQQ does not allow
for an override transaction as is used for APP. If it is determined by the authorities that an OK to
Board will be allowed, the authorization will be received through an Unsolicited Message. The agent
will then need to update the passenger record using a PU1,APP transaction.
An example of a PU1,APP transaction to update passenger status:
PU1,APP
_PU: XS123/21FEBYKBP1,app
AV C19Y192
PAD C0Y0
1. ALEXANDER/CREWE
BN012
US APP* (8501) OK TO BOARD/BN12
SN25A
Below is an example of a passenger receiving a SELECTEE status:

PA1,0/0
_PA: XS123/21FEBYKBP1,0/0
AV C19Y192
PAD C0Y0
767/B
1. DRAGONS/CATALANS
BN013 SN38G
US APP* (8541) SELECTEE/BN13
SA2200
FT2000
8.2.22.2Passenger cancellation:
A passenger may be deleted from an AQQ flight with a Cleared or Selectee status using the PW entry.
1 Below is an example of a passenger being deleted from an AQQ flight:

_pw-1
_PW: XS123/26MARYKBP-1
AV C20Y202
PAD C0Y0
767/B
1. DAVID/SIMON
DELETED
US APP* (8505) CANCELLED/BN1
SA2200
FT2100
If the passenger being deleted is a NoFly passenger, no response will be received upon deletion of
the passenger.

Page 111
8.2.22.3 Limits on Number of Passengers

AQQ allows queries for up to five passengers at a time. Thus, if the Airline configuration for AQQ is
set, SDCS will not check in more than five passengers at a time. For PW the limit is the same.
If more than the limit is attempted, SDCS returns:
(For PA or PU) Country Name APP Flight, 5 passenger maximum group size.
(For PW) Country Name APP Flight, 5 passenger maximum group size.
8.2.22.4 DFL Prohibited

DFL for any AQQ flight is prohibited. If a DFL is attempted for an AQQ flight where check-in has taken
place, the following warning will be displayed:
DFL:781/./ALL
805 - APP FLIGHT - DFL NOT PERMITTED
Note: Contact SITA Helpdesk staff to DFL any AQQ flight.
8.2.23 Watchlist
A Watch List is maintained by the US and Canada to monitor flights entering and leaving. This list is
maintained on the SITA Reservations server and it is accessed during the check-in and pre-check in
processes. The list includes individuals on No Fly and Selectee or No Fly only status for travel. A
passenger on the No Fly list is barred from traveling on the aircraft. A passenger identified as
Selectee will require additional security screening before they are allowed to board the aircraft.
The agent must select the passenger or passengers for check-in and if the flight is going to (or from) a
Watchlist airport, then DOCS or PSPT or Date of Birth must be added to the passenger record on
transmit, and an internal check is made for a name and date of birth match.

Page 112
Example 1:
Normal Check-in
28. Retrieve passenger to check-in:

X PDD:01
PDD: XS475/21MARYYYZ,01
1. ACKERS/JUDY
Y YVR
29. Check-in entry:

X -PA1,1/12,PSPT/B/22JUN70/ACKERS/JUDY
Response:
-PA: XS475/21MARYYVR1,1/12,PSPT/B/22JUN70/ACKERS/JUDY
AV F12C46Y423
PAD F0C0Y0
747/400A GTD/???? POS/GATE BDT1915 SD1945 ED1945
SA2030
1. ACKERS/JUDY
BN001 SN46G
FT0245
30. PDD display:

X PDD:01
PDD: XS475/21MARYYYZ,01
1. ACKERS/JUDY
BN001 SN46G
PSPT-B/22JUN70/ACKERS/JUDY
ACC VDT2110 AGT877/21MAR1000/SN46G
Y YVR OKT BAG1/12/0
Note 1: The item OKT (OK to travel) is attached to the passengers record to identify that a check
was made and there was no match found for this passenger. The action code SCW (Security
Checked Watch List) is also added to the history element.
Note 2: If the check-in does not involve an airport to or froma Watchlist country, then no codes are
attached to the passengers record even if they may be on the Watch List.
Note 3: For passengers with an onward connection, by through check-in, to a flight that involves a
Watchlist airport then the same procedures apply to the onward flight. The check-in agent will get a
warning if a match is found on the Watch List for the onward flight but the passenger will not be
inhibited from checking-in on their flights. However, for NNN and depending on a parameter setting for
SSS, they will be denied a boarding card.

Page 113
Example 2:
Selectee Check-in

X PDD:01
PDD: XS475/21MARYJFK,01
1. SMITH/CHARLES
Y YYZ
32. Check-in entry:

X -PA1,0/0,PSPT/P/5902843/US/10SEP44/M/SMITH/CHARLES/10JAN10/US
Response:
-PA:
XS475/21MARYYYZ1,0/0,PSPT/P/5902843/US/10SEP44/M/SMITH/CHARLES/10JAN10/US
AV F12C46Y422
PAD F0C0Y0
SA1900
FT0200
1. SMITH/CHARLES
BN002 SN37H
WARNING - WATCH LIST MATCH FOUND
33. PDD display:
PDD:01
1. SMITH/CHARLES
BN002 SN37H
Y YYZ SSS
PSPT-P/5902843/US/10SEP44/M/SMITH/CHARLES/10JAN10/US
ACC VDT2110 AGT877/21MAR1128/SN37H
SCW VDT2110 AGT877/21MAR1128/US/S827/SSS
Note: The item SSS denotes Selectee and is attached to the passengers record to identify that a
check was made and a match was found on the Selectee list. A parameter setting determines
whether a boarding card will print with SSS on it, or the print is inhibited. The action code SCW
(Security Checked Watch List) is also added to the history element along with the date/time stamp of
the Watch List that was referenced during the check-in process.

Page 114
Example 3:
No Fly check-in

X pdd:01
1. BENIZAR/SAMMY
Y YYZ
35. Check-in entry:

X PA1,0/0,DOCS/P/US/92349532/US/09FEB67/M/09AUG10/BENIZAR/SAMMY
Response:
XpA:
XS475/21MARYYYZ1,0/0,DOCS/P/US/92349532/US/09FEB67/M/09AUG10/BENIZAR/SAMMY
AV F12C46Y423
PAD F0C0Y0
SA1900
FT0200
1. BENIZAR/SAMMY
BN001 SN25D
WARNING - WATCH LIST MATCH FOUND
36. PDD display:
X PDD:01
1. BENIZAR/SAMMY
BN001 SN25D
Y YYZ NNN
DOCS-P /US /92349532/US /09FEB67/M /09AUG10/BENIZAR/SAMMY//
ACC VDT2110 AGT877/21MAR1044/SN25D
SCW VDT2110 AGT877/21MAR1044/US/N857/NNN
Note: The item NNN (denoting No Fly) is attached to the passengers record to identify that a check
was made and a match was found on the No Fly list. The boarding card issuance is inhibited for a
NNN passenger. The action code SCW (Security Checked Watch List) is also added to the history
element along with the date/time stamp of the Watch List that was referenced during the check-in
process.
8.2.23.1ITCI
When the onward ITCI flight is going to a Watchlist airport, if the check-in process finds a name match
on the ITCI flight, the check-in agent gets the following response:
EDI*UNABLE TO CHECK-IN SECURITY PROFILE RESTRICTION
So passenger will only be checked-in on their local flight and will have to check-in again at the
connection point.

Page 115
8.2.23.2Watch List Query

A Watch List Query can be made at any time. There is no requirement for a flight number, only the
name is needed. If a match is found, no action is taken, as the response is purely informational
perhaps for an advance check for a NOREC or URES passenger or some other reason.
Example:
List Version Search:
37. Enter Passenger Name.

XSCW:
Response:
SCW x.x (List Version)
Example:
Name Search:
38. Enter Passenger Name, Last Name/First Name (No match found):
XSCW:SABEL/RON
Response:
NO MATCH FOUND
Example:
Name Search, Last Name/First Name) Match Found:
39. Enter Passenger Name.

XSCW:BOND/JAMES
Response:
MATCHING NAME FOUND
1.
BOND/JAMES
US/16NOV1543/NNN
2.
BOND/JAMES
US/16NOV1543/SSS
8.2.23.3Boarding Process
There is no change to current boarding process except a new error is displayed if a name marked with
either SSS or NNN has not yet been cleared to travel and tries to board the aircraft.
40. Assign flight to Boarding:
XFDT:XS9016/17NOV
41. Attempt to Board BN12 (Passenger not cleared to travel):
XBAB:12
Response:
1 BOARDING NUMBER NOT ACCEPTED
BN
REASON
12
WATCH-LIST MATCH

Page 116
8.2.23.4Flight Close Out

There is a warning message that appears, similar to APP, when an attempt to close a flight for checkin is applied and there are still some passengers marked as SSS or NNN on the checked-in list.
For example:
42. Flight Close entry:
XCCL:XS9016
Response:
SECURITY LIST DISCREPANCY CLOSING FLIGHT INHIBIT
1. 1BAKER/PAMM+
BN85
SN22D
Y BOS NNN
43. To close flight, use one of the following Options:Delete passenger from flight
XPW:-1Use override entry (if passenger cleared to travel) after retrieving record (PDD:1)
XPU1,OVRW
Note: The OVRW is used for passengers that have been given security clearance to travel and is
restricted by sign-in code. The action/PID number/Agent and time is recorded in passengers PDD
record.
Note: After a passenger override, the boarding card must be printed. Enter BC:1 to print the boarding
card.
8.2.23.5Passenger Updates
If any passenger updates such as Name change or added PSPT or DOCS elements are entered after
the passenger has been checked-in, a new check against the watch list is initiated. If a match is
found, the record is marked with the appropriate NNN or SSS code and even though the boarding card
was previously issued, it is rejected if boarding is attempted.
8.2.23.6Passenger Displays (PS)
It is possible to display passengers by SSS, NNN, or OVRW codes.
Example:
PS SSS List:
PS:XS123/20APR ATL,SSS OP/NAM

767/A GTD/????
POS/GATE
BDT1930 SD2000
1. 1ABDUL/AZZIZMR
BN022
SN11C
2. 1AWAL/AHME+
BN036
SN15C
3. 1HAGUE/TOMMR
BN012
SN23B
4. 1KABIR/ALOM+
BN054
SN14E
ED2000
Y
MIA
Y
MIA
Y
MIA
Y
MIA
SA2100
FT0100
SSS PSPT TKNE
SSS I PSM
SSS NRS ASR TKNM
SSS TKNE

Page 117
8.3. Group Check-In (GRP)

Groups are passengers booked under a Group Name and then each of their separate names are listed
in the PNR. Each name has the same record locator. On the PNL each passenger or family has an
alphanumeric after their name. The letter identifies the group quickly and the number specifies how
many passengers are in the group. The letter is called a group identifier. The group name is shown
as an item on the PS list but always has a zero (0) in front of the name rather than the number in the
party. The group name cannot be used for check-in.
Maximum group size is 99 passengers, except for ITCI and Electronic Ticketing where the maximum
group size is 20 passengers. APP ITCI Max Group size is 5. Minimum group size is ten passengers.
Note: If two or more persons with different names are booked on the same PNR a group identifier is
also assigned by the system. This identifier quickly identifies the passengers for easier check-in.
These passengers will not have a group-booking name, i.e., .C\HUNTGRP.
The number of groups booked on a flight can be displayed by entering:
PS:FLIGHT ,GRP
Response to PS:XS227,GRP
PS:XS227/08JUNATL,GRP
767/A
GTD/A7
POS/GATE
1.0FOOTBALLTEAM
2.0GOLFTEAM
3.0HOLIDAY TOUR
1 2
3
OP/NAM
BTD/0930 SD1000 ED1000 SA1105 FT0105
E15
GROUP Y
JFK
P5
GROUP C
JFK
G25
GROUP Y
JFK
4
5
6
7
Field
Description
List entry number.
The '0' in front of the name signifies that this is a group name and not a passenger. It is not
possible to check-in any names that start with 0.
Name of the group. This display does not list the name of the passengers in the group, only
the group name.
Group identifier followed by the number in the group. This group identifier comes from the
PNL.
This identifies the entry as a group display.
Class of travel the group is booked in.
Destination of the group.
The next step after displaying the list of groups is to display the names for the individual groups. This
is done by making a note of the group identifier, and entering the following:
PS:FLIGHT ,GRI (GROUP IDENTIFIER)
Example to identify the names in group GOLFTEAM (the group identifier is J9), the entry is:
PS:XS227 ,GRI J
Note: Only the letter code of the group identifier is entered, not the number.

Page 118
Response to PS:XS227 ,GRI J

PS:XS227/08JUNXATL,GRIJ
OP/NAM
767/A
GTD/A7
POS/GATE BTD/0930 SD1000 ED1000 SA1105 FT0105
1. 2DAWSON/MR
J9
C
JFK
DAWSON/MRS
J9
C
JFK
2. 0GOLFTEAM
J9
GROUP C
JFK
3. 1MORRISON/D
J9
C
JFK
4. 2MARTIN/KMR
J9
C
JFK
MARTIN/WMRS J9
C
JFK
5. 1OBRIEN/IAN
J9
C
JFK
6. 1PALMER/MR
J9
C
JFK
7. 2REYNOLDS/S
J9
C
JFK
REYNOLDS/T
J9
C
JFK
The passengers can now be checked-in either individually (PA:ENTRY NUMBER,P/W), or they can all
be checked-in together using the range of entry numbers. However notice in this example, the 'group
name' is entry number 2, which means the system does not allow you to enter PA:1-7,P/W (because
you cannot check-in a group name), instead the entry would be 'PA:1,P/W;3-7'. It is possible to
display all the names of a group, without displaying the group name (NGRP), which then makes it
easier for the check-in.
The entry is:
PS:FLIGHT,GRI(GROUP IDENTIFIER),NGRP
1
PS:XS227,GRIJ,NGRP
Response to PS:XS227,GRIJ,NGRP
PS:XS227/08JUNATL,GRIJ,NGRP
OP/NAM
767/A
GTD/A7
POS/GATE BTD/0930 SD1000 ED1000 SA1105 FT0105
1. 2DAWSON/MR
J9
C
JFK
DAWSON/MRS
J9
C
JFK
2. 1MORRISON/D
J9
C
JFK
3. 2MARTIN/KMR
J9
C
JFK
MARTIN/WMRS
J9
C
JFK
4. 1OBRIEN/IAN
J9
C
JFK
5. 1PALMER/MR
J9
C
JFK
6. 2REYNOLDS/S
J9
C
JFK
REYNOLDS/T
J9
C
JFK
By adding the NGRP in the initial entry, this omits the group name from the display, and now the whole
group can be checked-in with one transaction.
If a group has no pre-assigned seats, it is possible for a supervisor to reserve an area on the seat map
(using the RS entry which puts a G on the requested seats), so that at check-in if the agent adds the
code 'SNRGRP' the passengers are allocated this designated area.
Example:
PA:1,P/W,SNRGRP
(individual passenger)
PA:1,P/W,SNRGRP;2;4;5
(range of passengers)
PA:1,P/W,SNRGRP;2-5
(range of passengers or whole group)
Note: The following entry is not allowed: PA:1-6,P/W,SNRGRP. The check-in agents should not use
the transaction above because it causes discrepancies especially when deleting one or more
passengers from the group.

Page 119
8.4. Standby Check-In (NOREC/URES/PAD)

If a passenger checks-in for a flight and their name does not appear on the booked list, the check-in
agent must determine whether the passenger is a URES (open ticket), a NOREC (OK ticket), or a PAD
(airline employee).
8.4.1
NOREC Check-In
If the passenger is a NOREC, the normal check-in entry is used. A NOREC check-in requires two
entries, as the system first checks the booked list to see if it can find the name entered or any similar
names. Then it displays them, and the agent must either identify the NOREC entry or select another
passenger on the list.
Example:
PA:XS679Y1SMITH/D,M1,1/10,B
Response to PA:XS679Y1SMITH/D,M1,1/10
PA:XS679/28JULYMIA1SMITH/D,M1,1/10,B
1. 1SMITH/D -NOREC PSGR
2. 2SMITHSON/MR
K2
Y
MIA
3. SMITHSON/MRS
K2
Y
MIA
M1/78
F1/68
The check-in has not yet been completed, so if an error is made, the screen can be erased, and the
transaction entered is ignored. However if the passenger is a NOREC then enter 'PA:1' and the
system completes the normal check-in. The passenger is either accepted into a seat or put on the
standby list depending on the GS figures entered on the SDD screen.
1
PA:1
In some cases the passenger name entered in the initial check-in entry might be slightly different from
the name registered on the list. If so, the system responds with a NOREC list plus the names of other
passengers who have similar names.
If the check-in agent finds that the passenger is not a NOREC but is one of the passengers on the
similar names list, then the check-in can be completed by entering the PA followed by the entry
number of the correct passenger (PA:ENTRY NUMBER) on this list.
Note: Although the name of the passenger was originally checked-in differently from the name on the
list, the system ignores the check-in entered name and keeps the system displayed name (if the name
is wrong and has to be changed, then correct it with the PU transaction).
The PDD display of a NOREC passenger who has gone on standby shows the code NREC.
1 Example NOREC Passenger

PDD:XS679/28JULYATL,1
1. SMITH/D SB016 LMTS Y
MIA
SBY VDT2967 AGT296/28JUL0815
NREC
M1/78 BAG1/10/0

Page 120
8.4.2
URES Check-In
If the passenger is a URES, the normal check-in entry is followed by the code 'URES'. When the
URES code is used, the system does not check any booked list, and the check-in transaction can be
completed in one entry.
1
PA:XS679Y1SMITH/D,M1,1/10,URES
The check-in is completed normally and the passenger is either accepted into a seat or placed on the
standby list depending on the GS figures entered on the SDD screen.
The PDD display of a URES passenger who has gone on standby shows only URES.
1 Example of URES Passenger

1. SMITH/D SB016 LMTS Y
MIA
URES
M1/78 BAG1/10/0
The transaction for EXST with ETKT processing for URES is:
PA: Flight Date ClassDestination1Last name/First name, 0/0, Gender, EXST,
TKNE/XXXXXXXXXXXXXC1,
TKNE- /XXXXXXXXXXXXXC1-EXST, URES
8.4.3
PAD Check-In
If a PAD passenger is listed on the flight, enter the ID element with the initial check-in entry but the
item URES is not required. If the PAD passenger is not previously listed on the flight, then the URES
item must also be input, otherwise the system responds with the NOREC display.
An example entry for a PAD passenger who has not been previously listed is:
PA:FLIGHT CLASS NBR NAME,GENDER,P/W,ID CODE,URES
1
PA:XS679 Y 1JONES/MR,M1,1/12,ID00N2/JAN88,URES
PA:XS679Y1JONES/MRS, F1,1/12,IDB2,URES
PA:XS679C1JONES/MARY,F1,1/12,IDAD00R1,URES
PA:XS679C1JONES/MARTIN,M1,1/12,IDID1,URES
Note: The ID code depends on the codes entered on the PZ:AIRLINE table. Also the 'date of joining'
is an optional entry. However if the 'date of joining' is entered, then the system can onload by
seniority, for those PAD passengers who have the same ID code. If the 'date of joining' is not entered,
the system will onload in order of check-in (first checked-in, first onloaded).
1 Example of a PDD Display of a URES PAD Passenger who has Gone on Standby:
1. JONES/MR SB020 PAD
Y
MIA
URES
M1/78 BAG1/12/0 IDN2 SA

Page 121
8.4.4
NOREC/URES Standby Passengers with Oncarriage
When checking-in a passenger with valid oncarriage and the passenger goes on standby on the first
flight, the oncarriage check-in is inhibited. Later, if the passenger is accepted on the flight, then the
agent must re-initiate the onward check-in (PS:1,10) to complete the check in process for the
passenger.
8.4.5
NOREC/URES Passengers with Oncarriage
If the GS/ID figures have been updated on the SDD screen, to accept any NOREC or URES
passengers checking-in, and these passengers have oncarriage, it is important the URES item is
inserted in the correct place.
If the following passenger is a URES on the first flight and not a NOREC, and the URES item is
inserted at the end of the transaction the following response is received:
1
PA:XS679Y1JAMES/MRS,F1,1/9,OBA292YLHR,URES
The response is a NOREC List:
PA:XS679/28JULYMIA1JAMES/MRS,F1,1/9,OBA292YLHR,URES
1. 1JAMES/MRS -NOREC PSGR
The system assumes the passenger is booked, and that the oncarriage details are the URES item.
The correct entry is:
PA:XS679Y1JAMES/MRS,F1,1/9,URES,OBA292YLHR,URES
The URES item must be input before the oncarriage details in order for the passenger to be
recognized as a URES on the first flight. Putting URES after the oncarriage indicates the passenger is
a URES on the oncarriage flight only.
Response to URES in Oncarriage:
PA:XS679/28JUNYMIA1JAMES/MRS,F1,1/9,URES,OBA292YLHR,URES
AV F10Y43
PAD F0Y3
747/A GTD/C19 POS/GATE BDT1930 SD2000 ED2000 SA2145 FT0145
1. JAMES/MRS
BN067 SN23A O
TRANSFER MIA BA292/28JUNYLHR CHECK-IN UNAVAILABLE

Page 122
8.4.6
NOREC/URES Passengers with a Marketing Segment on a Code share Flight
Passengers that are NOREC or URES on a marketing segment of a Code share flight can be
checked-in either by checking the passenger in using the marketing flight number OR checking in
using the operating carrier with a marketing indicator.
The following entry is for a NOREC passenger holding a marketing ticket on a code share flight using
the marketing flight for check- in:
1 Example: NOREC Y passenger David Smith holding a ticket on marketing flight YY141
operating as XS040:
PA:YY141Y1SMITH/DAVID,M1,1/10
Note: Checking in a NOREC/URES passenger with the marketing flight adds the MKT item to the
PDD.
The following entry is for a NOREC passenger holding a marketing ticket on a Code share flight using
the operating carrier with a marketing indicator for check-in:
1 Example: NOREC Y passenger David Smith holding a ticket on marketing flight YY141
operating as XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10,MKTYY141Y01ATLJFK
The following entry is for a URES passenger holding a marketing ticket on a Code share flight using
the marketing carrier for check-in:
1 Example: URES Y passenger David Smith holding a ticket on a marketing flight and
checking in for YY141 operating as XS040:
PA:YY141Y1SMITH/DAVID,M1,1/10,URES
The following entry is for a URES passenger holding a marketing ticket on a Code share flight using
the operating carrier with a marketing indicator for check-in:
1 Example: URES Y passenger David Smith holding a ticket on a marketing flight and
checking in for YY141 operating as XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10,MKTYY141Y01ATLJFK,URES
Passengers checking in as NOREC or URES passengers holding a ticket for the operating carrier of a
Code share flight will be checked in as normal NOREC and URES passengers.
1 Example: NOREC Y Passenger David Smith Holding a Ticket on Operating Flight XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10
Or from PS list:
PA:ENTRY NBR,1/10

Page 123
8.5. ITCI Passenger Handling Procedures

8.5.1
General Description
As ITCI deals with passenger handling procedures, these topics are covered in the following sections:
Passenger Acceptance (PA)
Passenger Update (PU)
Passenger Delete (PW)
Standby Check-in (URES/NOREC)
Boarding Card Re-Issue (BC)
Passenger Record Display (PDD)
Seat Map Display (SE)
8.5.2
Passenger Acceptance (PA)
PA Input
The passenger acceptance transaction is the same as Thru Check-In procedures, only the Responses
are different.
Note: To ITCI requires a .0, .02 or .03 indicating where in the line of flight ITCI exchange will take
place.
PA Use and Restrictions
Any Agent with the appropriate authority level can use the PA transaction.
The following restrictions apply for attempting to use ITCI for the Thru Check-In onto another Airline's
flight and DCS system:
Most airlines consider restricting ITCI for the following types of passengers:
ADSR
COUR
EXST
ID2
JMP
MUS
STCR
URES or NOREC passengers are not eligible for ITCI unless advised by the airlines.
Airlines bilaterally agree on the SSR types to be allowed. Some of the SSRs allowed are, but not
limited to:
CHD
INF
BLND
SCST
DEAF
DOCO
Page 124
DOCA
EXBG
FQTV
SDML
PETC
PRML
TKNA
TKNE
TKNO
UMNR
And all WCH requests
PA Input/Response
The 'PA' input entry remains the same as for Thru Check-In whether the acceptance is from a 'PS' list,
or whether the actual flight number and passenger's name is used in the check-in entry.
Responses to a PA transaction where ITCI is attempted from either SDCS or the partner
system/airline. Responses from SDCS are described in the Check-In Functional Specifications. All
processing and error responses apply. Responses from the partner host or partner airline are
preceded by EDI * when displayed to the screen. Other SSR codes are restricted by the connecting
carrier.
The following examples apply to passengers that are being Thru Checked-In onto onward connections
and processed through ITCI.

Page 125
1 A/Example of a 'Normal Response' when 'THRU CHECK-IN' is attempted:

Display passenger PDD:
PDD: XS378/01MARYATL,1
1. ADAMS/AMR
O/XS827/02MAR
PNR RL
H297S
Y LHR M1/77
Y MAN
Check-in with 1/12 baggage:

PA:1,1/12,O
Response:
PA:XS378/01MARYATL,1/12,
OP/NAM
AV F12Y54
PAD F0Y2
D10/A GTD/B24
POS/GATE
BTD/0930 SD1000 ED1000 SA2305 FT0805
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
EDIFACT THRU CHECK-IN IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
At this stage the Bag Tag and the first Boarding card for the flight XS378 will print, and there will be a
short wait and the system should respond. If the attempt is successful, the system responds
TRANSFER followed by the onward flight number and date, and start printing out the onward
boarding card.
1
PA:XS378/01MARYATL,1/12,O
AV F12Y54
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
TRANSFER LHR YY827/02MARJUN MAN
1. ADAMS/AMR
BN009
SN17D
OP/NAM
FT0805
At this stage the check-in transaction is complete.
1 B/Example of a 'Time Out Response' when 'THRU CHECK-IN' is attempted:

1. ADAMS/AMR
O/YY827/02MAR
PNR RL
H297S
Y LHR M1/77
Y MAN

PA:1,1/12,O

Page 126
Response:
AV F12Y54
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
OP/NAM
FT0805
After 20 seconds if the system is unable to complete the transaction, the response is:
- EDIFACT QUERY TIMED OUT
This means that the system was unable to complete the 'THRU CHECK-IN' transaction and so the
second Boarding Card or Boarding Number is not issued. The check-in process stops at this stage
and the passenger must be advised that he must check-in again at his transfer point.
Further attempts to check-in on the onward connection, with a PU1,O could result in the same
response, or could result in a successful check in. Repeated attempts cause unnecessary processing
if the partner system is still not responding.
1 C/Example of an 'Error/WARNING Response' when 'THRU CHECK-IN' is attempted:

1. ADAMS/AMR
O/YY827/02MAR
PNR RL
H297S
Y LHR M1/77
Y MAN

PA:1,1/12,O
Response:
OP/NAM
AV F12Y54
PAD F0Y2
D10/A
GTD/B24 POS/GATE
BTD/0930
SD1000
ED1000
SA2305
FT0805
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
EDIFACT THRU CHECK-IN IN PROGRESS FOR FLIGHT YY827/02JMAR/Y/LHRMAN
If the system cannot complete the transaction, the response is an error or warning response such as:
EDI * FLIGHT NOT OPEN FOR THROUGH CHECK-IN
The system was not able to complete the 'THRU CHECK-IN' transaction for the specified reason, and
so the second Boarding Card or Boarding Number is not issued. The check-in process stops at this
stage and the passenger advised that he must check-in again at his transfer destination.

Page 127
8.5.2.1 PA Seat Requests

When attempting to satisfy a passenger's seating preference ITCI only honors the following valid seat
requests on the 'Onward' flight, and translates them into the following codes for that flight:
Code
Description
Aisle Seat.
Exit Seat.
Front Seat.
Bulkhead Seat.
Legroom Seat.
Left Seat.
Right Seat.
Quiet Zone.
Smoking Seat.
Non Smoking Seat.
Window Seat.
Movie Seat.
Center Seat.
Upper Deck Seat.
Table 8.14 ITCI Valid Seat Request Codes

Any other codes entered are either ignored or the system responds with an error message.
This only applies to the 'Onward' flight, as all the current codes can still be used on the originating
flight.
A typical PA entry is:
PA:ENTRY NBR, P/W, SEAT REQUEST, O, SEAT REQUEST
1 Example entry:
PA:1,2/15,R11A,O,RW
1 Example response:
PA:XS378/01MARYATL,2/15,R11A,O,RW
AV F10Y44
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. GRANT/DMR
BN069
SN11A
O
O/YY827/02MAR
Y MAN
TRANSFER LHR YY827/02MAR MAN
1. GRANT/DMR
BN010
SN23A
FT0805
8.5.2.2 PA Subsequent Processing

If the initial check-in produces a passenger selection response, then the correct passenger can be
identified from this list, and then the transaction can proceed to the next step. However there is no
subsequent processing performed once interline thru check-in transaction message is dispatched to
Page 128
the onward Airline. The transaction will either be accepted or rejected with an error or warning
response.
8.5.3
Passenger Update (PU)
8.5.3.1 PU Processing
The passenger acceptance transaction is same as 'THRU CHECK-IN' procedures, only the
'RESPONSES' are different.
8.5.3.2 PU Use and Restrictions
The PU transaction can be used by any Agent with the appropriate authority level.
The following restrictions apply for attempting to update a passenger's record on a flight, through
EDIFACT, on another Airline's DCS system:
Passengers with EXTRA seats (COUR, EXST, MUS, STCR) are not allowed.
Passenger in JMP seat is not allowed.
ITCI is attempted on the first onward connection in the passenger record only.
Passengers with any SSR items on the Onward flight may not be accepted based on the ITCI
agreement. These include, but are not limited to,
UM/INF/BSCT/DEAF/BLND/FF/SPML/PETC/SNR (seat change requests) and all WCH requests.
8.5.3.3 PU Input/Response
The 'PU' input entry remains the same as it is for 'THRU CHECK-IN' whether the acceptance is from a
PS' list, or the actual flight number and passenger's name is used in the check-in update.
Responses to a PU transaction where ITCI is attempted come from either SDCS or the partner
system/airline. Responses from SDCS are described in the Check-In Functional Specifications. All
processing and error responses apply. Responses from the partner host or partner airline are
preceded by EDI * when displayed to the screen.
The following examples only apply to passengers that have been 'THRU CHECKED-IN' onto onward
flights being processed through EDIFACT.

Page 129
1 A/Example of a 'Normal Response' when a 'PU' is Attempted:

1. COOPER/CMR
BN023
O/YY827/02MAR
BN009
BAGTAGS ISSUED:
0182526553
SN10C
SN06D
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN
Update passenger COOPER with item WCHR:

PU:1,WCHR
Response:
PU: XS378/01MARYATL,1,WCH
OP/NAM
AV F10Y36
D10/A GTD/B24 POS/GATE BDT/0930 SD1000 ED1000 ED1000 SA2305
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
Y MAN
EDIFACT UPDATE IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
FT0805
At this stage there is a short wait and the system should respond with a reply. If the attempt is
successful, the system responds:
PU: XS378/01MARYATL,1,WCHR
OP/NAM
AV F10Y36
D10/A
GTD/B24 POS/GATE BDT/0930 SD1000 ED1000 ED1000 SA2305
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
Y MAN
TRANSFER
LHR YY827/02MAR MAN
1. COOPER/CMR
BN012
SN06D
FT0805
At this stage the passenger update is complete and no further action is required.

Page 130
1 B/Example of a 'Time Out Response' when a 'PU' is Attempted:

1. COOPER/CMR
BN065
O/YY827/02MAR
BN012
BAGTAGS ISSUED:
0182526553
SN10C
SN06D
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN

PU:1,WCHR
Response:
PU: XS378/01MARYATL,1,WCHR
OP/NAM
AV F10Y36
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
Y MAN
FT0805
After 20 seconds if the system cannot complete the transaction, the response is:
EDIFACT QUERY TIMED OUT
This indicates the system cannot complete the 'UPDATE' transaction and the entry process stops.
The passenger must be advised that he must check again at the transfer destination. In this case the
system sends an IFM message in case the transaction reached the onward flight but 'ran out' of time
before a response could be sent.
Note: There is no reason why the 'UPDATE' cannot be attempted again using the PU transaction
although the response could remain the same.

Page 131
1 C/Example of an 'Error/Warning Response' when 'PU' is Attempted:

Display passenger PDD:1
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
BAGTAGS ISSUED:
0182526553
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN

PU:1,WCHR
Response:
PU: XS378/01MARYATL,1,WCH
OP/NAM
AV F10Y36
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
Y MAN
FT0805
If the system cannot complete the transaction, the response is:

EDI * MODIFICATION NOT POSSIBLE
The system could not complete the 'UPDATE' transaction and so the update process stops at this
stage and the passenger is advised that he must check-in at the transfer point.
8.5.3.4 PU Seat Changes
The seat change process for passengers with onward connections is different when the process
involves ITCI. The request for a different seat must be input after the O (outbound indicator).
The entry is:
PU:ENTRY NBR, O, NEW SEAT REQUEST
1 Example entry:
PU:1,O,R6F
1 Example response:
PU:XS378/01MARYATL,O,R6F
OP/NAM
AV F10Y44
PAD F0Y2
D10/A GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
FT0805
1. GRANT/DMR
BN069
SN11A
O
O/YY827/02JMAR
BN010
SN06A
Y MAN
TRANSFER
LHR YY827/02MAR MAN
1. GRANT/DMR
BN010
SN6F

Page 132
8.5.4
Passenger Delete (PW)
8.5.4.1 PW Input
The passenger delete transactions for 'THRU CHECK-IN' passengers are the same as 'PW'
procedures except some of the 'RESPONSES' are different.
8.5.4.2 PW Use and Restrictions
Any agent with the appropriate authority level can use he PW transaction.
The following restrictions apply for attempting to update a passenger's record on a flight, through ITCI,
on another Airline's DCS system:
Only one passenger 'entry number' can be deleted in the same transaction.
A 'NOT CHECKED-IN' passenger cannot be deleted.
When deleting items, the items must be associated with the passenger, and the counts and
weights cannot exceed the original value of the items.
8.5.4.3 PW Input/Response
The 'PW' input entry remains the same for updating passenger records on flights that were processed
for 'THRU CHECK-IN' with ITCI, only some of the responses may differ.
The following examples only apply to passengers that have been 'THRU CHECKED-IN' onto onward
flights being processed through ITCI.

Page 133
1 A/Example of a 'Normal Response' when a 'PW' for a Passengers Item is Attempted:

1. HARRIS/CMR
BN015
SN22F
SPML-ORML
O/YY827/02MAR
BN004
SN22F
BAGTAGS ISSUED:
0182526567
PNR RL
H681G
Y LHR BAG1/12/0 M1/77
Y MAN
Delete item SPML from passenger HARRIS:

PW:1,SPML
Response:
PW XS378/01MARYATL,1,SPML
OP/NAM
AV F10Y36
D10/A GTD/B24 POS/GATE BDT/0930 SD1000 ED1000 SA2305 FT0805
1. HARRIS/CMR
BN015
SN18F
O/YY827/02MAR
BN004
SN18F
Y MAN
Note: Even though the entry was a PW for an item delete, the EDIFACT response shows 'EDI-FACT
UPDATE IN PROGRESS'. However for a passenger delete the response is 'EDIFACT DELETION IN
PROGRESS'.
There is a short wait then the system responds. If the attempt is successful, the system responds:
PW XS378/01MARYATL,1,SPML
OP/NAM
AV F10Y36
1. HARRIS/CMR
BN015
SN18F
O/YY827/02MAR
BN004
SN18F
Y MAN
TRANSFER LHR YY827/02MAR MAN
1. HARRIS/CMR
BN004
SN18F

Page 134
1 B/Example of a 'Time Out Response' when a 'PW' for a Passengers Item is Attempted:
1. HARRIS/C/MR
BN015
SN18F
Y LHR
O/YY827/02MAR BN004
SN18F
BAGTAGS ISSUED:
0182526567 0182526568
Y MAN
PNR RL
H681G
BAG2/22/0 M1/77
WCHR
Delete item WCHR:

PW:1,WCHR
Response:
PW: XS378/01MARYATL,1,WCHR
OP/NAM
AV F10Y36
1. HARRIS/C/MR
BN015
SN18F
O/YY827/02MAR
BN004
SN18F
Y MAN
After 20 seconds if the system cannot complete the transaction, the response is:
- EDIFACT QUERY TIMED OUT
The system cannot complete the 'UPDATE' transaction and the entry process stops at this stage and
the passenger is advised that he must check-in again at his transfer destination. In this case the
system sends an IFM message just in case the transaction reached the onward flight but 'ran out' of
time before a response could be sent.
Note: There is no reason why the 'DELETE' cannot be attempted again using the PW transaction
although the response could remain the same.

Page 135
1 C/Example of an 'Error/Warning Response' when a 'PW' for a Passengers Item is Attempted:

PDD: XS378/01MARJUNYATL,1
1. HARRIS/C/MR
BN015
SN18F
O/YY827/02MAR
BN004
SN18F
BAGTAGS ISSUED:
0182526567 0182526568
Y LHR
Y MAN
PNR RL
H681G
BAG2/20/0 M1/77
Delete item SPML from passenger HARRIS:

PW:1,SPML
Response:
PW: XS378/01MARYATL,1,SPML
OP/NAM
AV F10Y36
1. HARRIS/C/MR
BN015
SN18F
O/YY827/02MAR
BN004
SN18F
Y MAN
If the partner system cannot complete the transaction, the response is:
EDI * MODIFICATION NOT POSSIBLE
The system cannot complete the 'DELETE' transaction for the specified reason, and the update
process stops at this stage and the passenger is advised that he must check-in again at his transfer
destination.

Page 136
1 D/Example of a 'Normal Response' when a 'PW' is Used to Delete a Passenger on the Onward
Flight Only:

1. MORRIS/FMRS
BN049
O/YY827/02MAR
BN019
BAGTAGS ISSUED:
0182526567
PNR RL
SN14A
SN09F
H847I
Y LHR
Y MAN
BAG1/12/0 F1/65
Delete onward flight from Passenger MORRIS:

PW:1,0
Response:
PW XS378/01MARYATL,1,O
AV F060Y22
D10/A GTD/B24 POS/GATE BDT/0930
1. MORRIS/FMRS
BN049
O/YY827/02MAR
BN019
EDIFACT DELETION IN PROGRESS FOR
OP/NAM
SD1000 ED1000 SA2305 FT0805
SN14A
SN09F
Y MAN
FLIGHT YY827/02MAR/Y/LHRMAN
At this stage there is a short wait and the system should respond. If the attempt is successful, the
system responds:
PW XS378/01MARYATL,1,O
OP/NAM
AV F060Y22
1. MORRIS/FMRS
BN049
SN14A
O/YY827/02MAR
BN019
SN09F
Y MAN
EDIFACT DELETION IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER
LHR YY827/02MAR MAN
1. MORRIS/FMRS
DELETED

Page 137
1 E/Example of a 'Normal Response' when a 'PW' is Used to Completely Delete a Passenger from
both Flights:

1. MORRIS/FMRS
BN049
O/YY827/02MAR
BN019
BAGTAGS ISSUED:
0182526567
PNR RL
SN14A
SN09F
H847I
Y LHR BAG1/12/0 F1/65
Y MAN
Delete passenger MORRIS:

PW:-1
Response:
PW XS378/01MARYATL,1,
OP/NAM
AV F060Y22
1. MORRIS/FMRS
DELETED
O/YY827/02MAR
BN019
SN09F
Y MAN
At this stage there is a short wait while the partner system responds. If the attempt is successful, the
partner system responds:
PW XS378/01MARYATL,1,
OP/NAM
AV F060Y22
1. MORRIS/FMRS
DELETED
O/YY827/02MAR
BN019
SN09F
Y MAN
TRANSFER
LHR YY827/02MAR MAN
1. MORRIS/FMRS
DELETED
If the transaction is unsuccessful, then the system sends an Error or Warning response.
Note: If any 'DELETED' passenger is re-accepted on a flight, the system re-issues the same BN
number on the originating flight.
1 F/Example of a 'Normal Response' when a 'PW' is used to Delete an Onward Flight Before and
After Check-In:

Page 138
Before Check-In
1. PHILIPS/MR
O/YY827/02MAR
PNR RL
H847I
Y LHR M1/77
Y MAN
Delete the onward before check-in:

PW:#1,O,XRES
Response:
1. PHILIPS/MR
Y LHR
PNR RL
H847I
ADV-PW/NP M1/77
It is then possible to add a new onward flight with the PA entry providing the URES is added at the end
of the entry (PA:1,1/12,OYZ837YGLA,URES).
After Check-In
Display passenger PDD after check-in:
PNR RL
1. PHILIPS/MR
BN055 SN19K
O/YY827/02MAR
BAGTAGS ISSUED:
0182526583
H847I
Y LHR
Y MAN
1/12/0 M1/77
Delete the onward:

PW:1,O,XRES
Response:
PNR RL
1. PHILIPS/MR
BN055
SN19K
BAGTAGS ISSUED:
0182526583
H847I
Y LHR
1/12/0 M1/77
It is then possible to add a new onward flight, if required, with the PU entry (PU:1,OYZ837YGLA).
Example of E-Ticket passenger with EXST has the EXST removed prior or after check in.
Prior to check in the entry is
PW: #1, EXST
This entry would remove both the EXST and the TKNE associated with it. The status of the EXST
coupon would be changed to OPEN FOR USE.
After check in
PW:-1
Both the passenger and the EXST coupon should have the status changed to OPEN FOR USE.

Page 139
8.5.5
Standby Check-In (URES/NOREC/ID)
8.5.5.1 URES Check-In

If a passenger is holding a confirmed (OK) ticket for a connecting flight then attempt the check-in using
the "O" as normal. If there is no outbound flight shown in the PDD then the system responds:
TRANSFER FLIGHT-NBR
As the coupon shows confirmed, the passenger should be treated as a NREC on the outbound flight.
In this case, the check-in entry would require the flight detail as:
PA1,1/11,OYY827YMAN
If no GS limits were set on the connecting flight, then the check-in response will show the passenger
as a NREC on standby for the connection.
If this is an ITCI connection and the name is not found (which must be an exact match), the response
is:
EDI * PASSENGER SURNAME NOT FOUND
If the outbound coupon is not showing as not confirmed, then the passenger must be treated as a
URES for the connection. In this case the connecting flight detail must be entered followed by URES
as:
PA1,1/11,OYY827YMAN,URES
This responds with a completed standby check-in on the connecting flight (subject to GS limits).
Note: It is important to add the URES after the onward flight; otherwise you will get the response
'TRANSFER STATUS CONFLICT'.
8.5.5.2 NOREC Check-In
If after any attempted ITCI, the system does not find an exact name match to the input passenger's
name, then the entry is rejected with the following response:
EDI * PASSENGER SURNAME NOT FOUND
Their system will not respond with a 'similar name' list, except on the originating flight. Therefore
NOREC check-in is not allowed on onward flights using EDIFACT.
8.5.5.3 ID Check-In
There are two types of ID passengers:
ID1
ID2
ID1 passengers are usually 'booked' staff passengers, and are therefore permitted for 'INTERLINE
THRU CHECK-IN' providing they are also booked on the onward flight, as they are treated as a normal
'OK' passenger. Any 'unbooked' ID1 passengers will not be accepted for the onward flight as the
system rejects any URES or NOREC passengers, unless the name is found on the onward flight.
ID2 passengers are 'unbooked' staff passengers and are inhibited from check-in on the onward flight.

Page 140
8.5.6
URES and NOREC Passengers
The following sections explain the difference between a URES and a NOREC passenger.
8.5.6.1 URES
A URES passenger is any passenger who wants to travel on a flight but who is not 'Booked' (Open
ticket) or Listed for the flight on the passenger name list (PNL). For the PFS (passenger final sales)
report sent to their Reservations Department at the end of a flight, the system treats these passengers
either as GO-SHOW passengers (if they are Full-Fare Revenue passengers), or as ID PAD
passengers if they are Airline staff.
8.5.6.2 NOREC
A NOREC passenger is a passenger who holds a 'Booking' in his ticket for the flight but whose name
is not included on the Passenger Name List (PNL).
Note: At check-in time when a URES passenger is being checked-in, that the agent remembers to
add the item URES to the transaction. Otherwise the system assumes the passenger is a NOREC,
and this causes erroneous information being passed back via the PFS report to the Reservations
department at the end of the flight.
8.5.6.3 Boarding Card Re-Issue (BC)
Entry:
The Boarding Card for the origin flight is printed when the passenger check-in transaction is
completed. The second Boarding card is issued when the return response from the ITCI process is
successful.
If it is necessary to re-issue a Boarding card, the following are the only valid entries:
Entry
Description
BC:1
Re-issue Boarding Card for originating flight only.
BC:1,O
Re-issue Boarding Card for first onward flight only, which is the ITCI flight.
Table 8.15 Valid Entries for a Boarding Card Re-issue

Response:
BOARDING CARD RE-ISSUED
Note: It is not possible to re-issue all Boarding Cards for a passenger, for all his flight sectors, in one
entry.

Page 141
8.5.7
Passenger Record Display (PDD)
8.5.7.1 PDD Input

Although the basic PDD entry/display is the same, there is now an additional entry to allow a
passenger record on the onward flight. This applies to flights that have been 'THRU CHECKED' using
the EDIFACT process.
The entry is (after a previous PS list):
PDD:ENTRY NBR,O
1 Example entry:
PDD:1,O
The response is:
PDD:XS378/01MARYATL,1,O
1. GIBSON/IAN
BN008
SN03D
BN026
SN05C
BAGTAGS ISSUED:
0182526661
EDIFACT PROCESSING IN PROGRESS
Y LHR
Y MAN
PNR RL H337F
BAG1/10/0 M1/77O/YY827/02MAR
If the entry is successful, an example response could be:

PDD:XS378/01MARYATL,1,O
1. GIBSON/IAN
BN008
SN03D
M1/77
O/YY827/02MAR
BN026
SN05C
BAGTAGS ISSUED:
0182526661
EDIFACT PROCESSING IN PROGRESS
TRANSFERLHR YY827/02MAR MAN
1. GIBSON/IAN
BN026
SN05C
PNR RL H337F
Y LHR BAG1/10/0
Y MAN
If the entry is not successful, then a corresponding Error or Warning message is returned to the
screen.
8.5.7.2 Restrictions
The following restrictions apply on attempting to display the PDD:1,O transaction for a passenger
listed on an onward flight using ITCI.
1 1/Passenger 'Not Checked-in' on the Onward Flight

If a PDD:1,O is attempted on a passenger that is not checked-in on his onward flight, the response is:
1. PHILIPS/MR
O/YY827/02MAR
NO THRU EDIFACT ATTEMPTED
PNR RL
H847I
Y LHR M1/77
Y MAN

Page 142
1 2/Passenger 'Deleted' off the Onward Flight

If a PDD:1,O is attempted on a passenger that was 'DELETED' completely off a flight (or just the
onward flight), the response is:
PNR RL
H847I
1. PHILIPS/MR
DELETED
Y LHR M1/77
O/YY827/02MAR
DELETED
Y MAN
DEL VDT10655 AGT299/01MAR0905/BN27
PAX DELETED ON EDIFACT FLIGHT - NO EDIFACT PROCESSING ATTEMPTED
Note: The BN number displayed on the DEL line refers to the originating flight and not the onward
flight.
Remember that the system prevents the PDD:1,O display unless the passenger currently holds a
Boarding Number on the onward flight.
8.5.7.3 Passenger Record Displays (PDD)
PDD:1,O may be entered to determine the passenger status on the partner system if the original
update or deletion failed. Most, but not all, ITCI partners have the ability to support this transaction.
8.5.8
Seat Map Display Input / Response
Although the basic SE entry/display is not changed, there is now an additional entry to display a seat
map for an onward flight. This applies to flights that are 'THRU CHECKED' using the EDIFACT
process.
The entry is:
SE:FLIGHT/DATE ORIG DEST
1 Example entry:
SE:YY827/+LHRMAN
The response is:
EDIFACT SEAT MAP REQUEST SENT FOR FLIGHT YY827/02MAR/LHRMAN

Page 143
If the entry is successful, an example response is:

SE:YY827/02JUN/XLHRMAN
737/A
F
Y
[ [ [ 1 [ [
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
RF .R F F . R . * * . * . * . . . * * .
FR
RE
* * E E . * * * * * * * . * * . * *
ER
RD
* R D D . * . . * * R * * * . * * * . * DR
R
= S = = = = E E = = = = S S S S S S R
L
LC
LB
LA
=
.R
*
*
F
S
F
*
R
=
F
E
D
=
.
E
D
=
R
.
.
=
.
*
*
Y
E
*
*
.
E
*
*
.
= = = = S S S S S S R
. * . * . . . * * .
FR
* * * * . * * . * *
ER
* * R * * * . * * * . * DR
[ [ [ 1 [ [
Although it is possible to display this seat map, it is not possible to revise it.
Note: Some ITCI partners require that the class be input with the SE entry. If the entry is not
successful, then an Error or Warning message is returned to the screen.
8.6. Extra Crew Check-In (XXXCREW)

Extra crew requiring a passenger seat on a flight can be checked-in using the special code
'XXXCREW'. If this code is used then note the following:
1. The XXXCREW are included in the total passenger figures on the SDD screen. The total
XXXCREW checked-in are also entered under XCR on this screen.
2. The XXXCREW are not included under accepted PADC on the SDD screen even if an ID code
has been entered.
3. The XXXCREW are not included in the passengers figures transferred to Load planning, instead
they are included under extra crew on the dry operating weight and index, and their weight and
index is added to the Aircraft Operating weight and Index.
Note: The maximum number of MALE XXXCREW that can be checked-in on a flight is 15, and the
maximum FEMALE XXXCREW is 31 in each class of service. If either of these figures are exceeded it
can cause problems to the EXTRA CREW figures displayed on the LODD:FLIGHT/DATE screen.
1 Example check-in entry of a URES extra crew member:

PA:XS394 C 1XXXCREW,F1,0/0,URES
Note: If a check-in agent does not check-in the crew member with the exact code of XXXCREW, the
system treats the entry as a normal passenger, and the XCR figure on the SDD screen is not updated.
Note: XXXCREW and XXXDHC can be entered with the surname, e.g., XXXCREW/JONES.

Page 144
8.7. Dead Head Crew Check-In

Crew members carried on a specific flight to position them at a different airport can be checked in
using the special code "XXXDHC". When this code is used, note the following:
1. The XXXDHC are included in the total passenger figures on the SDD screen. The total XXXDHC
checked-in are also entered under DHC on this screen.
2. The XXXDHC are not included under accepted PADC on the SDD screen even if an ID code is
entered.
1 Example of a check-in entry of a URES dead heading crew member.

PA:XS394 C 1XXXDHC,M1,1/10,URES
8.8. Unattached Baggage Check-In

It is possible to check-in unattached bags, perhaps missed off a previous flight, without having to
attach them to a particular passenger.
8.8.1
Check-In Unattached Bags
When checking-in the unattached bags, please remember the initial code is PU and not PA.
The entry to check in without bag tags is:
PU:FLIGHT CLASS DEST 0, P/W
1 Example Response without Bag Tags:

PU:XS100/02AUGYMEX0,2/30
AV F14Y58 PAD F0Y0
DC9/A GTD/???? POS/GATE
2 UNATTACHED BAGS ADDED
PU:XS100YMEX0,2/30
BDT1930 SD2000 ED2000
SA2000 FT0200
The entry to check in and assign bag tags is:

PU:FLIGHT CLASS DEST 0,P/W,B/DEST
1 Example Response with Automated Bag Tags:

PU:XS100YMEX0,2/20,B/MEX
PU: XS100/24OCTYMEX0,2/20,B/MEX
AV C9Y93
PAD C0Y0
DC9/A
2 UNATTACHED BAGS ADDED
SA2245
FT0045
The entry to check in with manual bag tags is:

PU:FLIGHT CLASS DEST 0,P/W,B/DEST/XS1234567
1 Example Response with Manual Tags:PUXS100YMEX0,1/10,B/MEX/XS1234321

PU: XS100/25OCTYMEX0,1/10,B/MEX/XS1234321
AV C36M114
PAD C0M0
DC9/A
SA0
Note: The actual class must be specified.

Page 145
Display Unattached Bags
8.8.2
It is possible to display a list of the unattached bags on a flight.

The entry is:
PDD:FLIGHT ,0
1 Example response:
PDD:XS100 ,0
PDD:XS100/02AUGATL,0
MEX 3/42 UNATTACHED BAGS
ACC VDT 1967 AGT286/02AUG1743
ACC VDT 5926 AGT518/02AUG1836
Note: The 0 is numeric zero and not the letter (O).

This display gives the destination of the bags, the number of unattached bags checked-in, and a list of
the agents and CRT PID numbers who did the check-in (ACC), or modified (MOD) the unattached bag
entry (deleted a bag).
To display a list of deleted bags only the entry is:
PDD:1,XB
1 Example response: PDD:1,XB

PDD: XS100/24OCT MEX,1,XB
MEX 3/13 UNATTACHED BAGS
BAGTAGS ISSUED:
*0149022626/MEX
PW
VDT2110 AGT877/24OCT2007/BAG
1/10

Page 146
8.8.3
Delete Unattached Bags
If an unattached bag must be removed from the flight, use the following entries:
To delete bags without bag tag numbers:
PW:FLIGHT CLASS DEST 0, P/W
A record of the bag tag deletion is sent to the KB queue and the Baggage Action List (BAL).
1 Example Response:PW:XS100YMEX0,1/10
PW:XS100/02AUGYMEX0,1/10
AV F14Y58 PAD F0Y0
DC9/A GTD/???? POS/GATE
UNATTACHED BAGS DELETED
BDT1930 SD2000 ED2000
SA2000 FT0200
To delete bags by bag position:

Note: If there are several unattached bags with bag tags listed, then 1 applies to the first listed, 2 to
the second, etc.
1
PW:XS100YMEX0,1/10,B/1
1 Example Response:PW:XS100YMEX0,1/10,B/1
PW: XS100/24OCTYMEX0,1/10,B/1
AV C36M110
PAD C0M0
DC9A
GTD/???? POS/GATE BDT2315 SD2345 ED
To delete bags using a tag number:
PW:FLIGHT CLASS DEST 0,P/W.B/XS1234567
1 Example Response: PWXS100MMEX0,1/10,B/0182050217

PW: XS100/24OCTMMEX0,1/10,B/0182050217
AV C36M110
PAD C0M0
DC9/A
1 UNATTACHED BAGS DELETED
SA0030+1 FT0045
Note: The actual class must be specified.

Whenever a bag is removed from a flight (from a passenger or an unattached bag), the system sends
the following message to the airline's specified location (in the CX table), the KB queue, and BAL.
1 Example response:
DVC-7382 1844 02AUG90
CKI XS100/02AUG ATL REMOVE BAGGAGE
UNATTACHED BAGS
DEST/MEX BAG/1/10 AGT836
This is a security message, so that if there is a baggage figure discrepancy at the aircraft, the
supervisor can quickly identify if any baggage was cancelled from the system after check-in by
checking these warning messages.
8.8.4
Expedite Bag Tags
The system allows the entry and issuance of bag tags for expedite bags where no part of the itinerary
is on a SDCS operated flight.
1
Page 147
EXP:D
EXP:
Expedite Bag Screen
Pieces/Weight
0
Origin/Date BUD/17JUN06
Passenger Last/First Name
Flight/Date
Flight/Date
Flight/Date
/
/
/
/0
/
Destination
Destination
Destination
It is possible to display all unattached baggage details entered for a non-SDCS operated flight out of
the signed in city for the current date.
1
EXP:D
After the initial EXP:D entry, it is possible to select and update baggage details associated with a
specific entry number.
1
EXP:U1
Note: If all Baggage is removed (0/0 entered in Piece/Weight field), then after Transmit, all the
baggage details are also deleted.
If baggage is added, then either a manual bag tag must also be added, or on transmit an automated
bag tag is issued.
If the baggage is being reduced, then the Transmit transaction is ignored unless a corresponding bag
tag is also deleted. There is an additional field displayed at the end of each bag tag where an X is
placed for selected bag tag to be deleted.

Page 148
8.9. Procedure to Delete or Change Onward Connections

There are two different procedures for deleting onward connections:
3. Before Check-in
4. After Check-in
8.9.1
Before Check-In
1.Display the PS or PDD passenger record.

PW: # ENTRY NUMBER,O,XRES
Note: It is not necessary to enter the actual onward details, just the O unless there is more than one
onward flight in the passenger's record. In that case the actual flight number must be input with the O.
2.Check-in the passenger.
PA:ENTRY NUMBER,P/W,O(NEW DETAILS),URES
Note: It is not possible to add new onward details to the passenger record before the passenger is
checked-in. It can only be added during check-in (or later with PU). Also it is important to include the
URES item in the check-in entry, otherwise you will get the response 'TRANSFER STATUS
CONFLICT'.
8.9.2
After Check-In
1. Display the PS or PDD passenger record:

PW:ENTRY NUMBER,O,XRES
2. Enter the new details:
PU:ENTRY NUMBER,O(NEW DETAILS),URES
Examples:
PU:1,OSR946/+CZRH,URES
PU:1,OSR946/17NOVCZRH,URES
The date is required if the onward connection is not for today. Also the date can be entered as a
+ for tomorrow or as an actual date.
Note: Use 'XRES' to prevent the cancelled onward details from being included on the PTM when it is
dispatched at the end of the flight.
For EDIFACT and 'THROUGH' check-in flights it is necessary to add the URES otherwise the
entry is rejected. For other flights the URES is optional. If the new onward details are added at
check-in (PA) using 'URES' the PTM displays '.RQ' after the name, indicating that this onward
connection is only a request booking. If for some reason you do not want the '.RQ' to display on
the PTM, then enter the new onward details without URES, with the 'PU' transaction (this does not
apply to EDIFACT or 'THROUGH' check-in flights).

Page 149
8.10. Passenger Notification (NO)

The passenger notification (NO) transaction allows agents to remove the need notification status from
one or more passengers on a flight.
To see the list of passengers that need notification, display the standby list for the flight.
SB:FLIGHT NUMBER
1
SB:XS735
Response to SB:XS735
SB: XS735/08JUNATL
OP/NAM
AV C4M63
PAD C0M0
NEED NOTIFICATION
1. 2BLAKE/MMR
B2
BN002 SN1A
C
MIA
ACC/SB007
BLAKE/TMS
B2
BN003 SN1C
C
MIA
ACC/SB008
2. 1KELLY/LMRS
BN019 SN23D
M
MIA
PU/NP
LOCAL PAD
3. 1PORTER/GMRS
BN045 SN3C
C
MIA
P08
IDN1/MAR71
4. 1EDWARDS/YMR
BN023 SN4A
C
MIA
P05
IDS1/AUG69
STANDBY
5. 1CARLTON/N
SB025 LMTS
M
MIA
P20
IDS2/MAY71
6. 3FERGUSON/SMR K3
SB035 LMTS
M
MIA
P50
IDN2/APR79
FERGUSON/YMRS K3 SB036 LMTS
M
MIA
P50
IDN2/APR79
FERGUSON/LMIS+K3 SB037 LMTS
M
MIA
P50
IDN2/APR79
7. 1BOOTH/AMR
SB019 LMTS
M
MIA
P90
IDR2/SEP85
The passengers that Need Notification are listed first, followed by the Standby passengers (Accepted
and Listed).
To Action the Notification just enter:
NO:ENTRY NUMBER
1
NO:1-2
This clears the Notification status for 2BLAKES and 1KELLY. This transaction should be entered for
all passengers that Need Notification before the flight closes (CI) for check-in, otherwise the list of all
the Need Notification passengers will be displayed on the screen when the Flight Close (CI) is
attempted.

Page 150
8.11. Boarding Pass Issuance / Inhibit (BC)

Boarding cards print after a passenger's check-in formalities are completed. However, it may be
necessary to re-issue a boarding card. This request can be done by boarding number, seat number,
standby number (only if boarding cards are normally issued for standby passengers, otherwise it is not
possible), group name, or by entry number from a previous display. If necessary, boarding passes can
be reissued after the flight is closed.
The check-in transaction issues a boarding pass with the following exceptions, if:
Excess baggage charges are applied the response shows the amount of excess bag charges to
be assessed with the comment BOARDING PASS PRINT INHIBITED.
API data is required and is not complete the response is BOARDING CARD INHIBITED MISSING
DOCUMENT DATA.
1 Examples:
1.By Boarding Number:
BC:FLIGHT NUMBER CLASS, BN NUMBER
BC:XS496M,BN098
2.By Seat Number:
BC:FLIGHT NUMBER CLASS, SN NUMBER
BC:XS338Y,SN17B
3.By Standby Number:
BC:SB NUMBER (flight number is not required)
BC:SB137
4.By Group Name:
BC:FLIGHT NUMBER CLASS, GROUP NAME
Note: Group names must be entered exactly as displayed on list and even though passengers may
have been checked-in by their own names, issuing boarding cards by group name will only display the
group name on the boarding card.
BC:XS299Y,SUNTOURS
5.
By Entry Number from a Previous Display:

BC:ENTRY NUMBER
BC:12
for a particular entry number
BC:1P2
for a particular passenger from same entry number.
6.
For Passenger with an Onward Flight:

BC:ENTRY NUMBER,O
BC:1,O
Note: The BC entry is not allowed for passengers that have already boarded. If a boarding card has
to be re-issued for a boarded passenger, then they must be de-boarded first.

Page 151
8.12. Boarding Pass Inhibit

To Inhibit the Boarding Card from printing at check-in completion, add the item XBP to the check-in
entry:
Example:
PA:XS829Y1BARNETT/MRS,F1,1/15,WCHR,XBP
8.13. Excess Baggage (EXB)

When a passenger checks-in the system calculates the amount of excess charge that is due, and
either issues a boarding card or inhibits the boarding card (if the inhibit program is loaded for your
airline) from printing until the excess charge is paid.
The following conditions apply for the system to calculate excess baggage at check-in:
Only the weight of baggage, or the number of pieces, depending on which restriction applies, at
the time of check-in is used for the system calculation.
The total number of checked bags (weight or pieces) for a family or group is calculated against the
total allowance for those checking-in at the same time.
Note: An infant has no baggage weight allowance but is allowed one piece of baggage when piece
concept is used.
The system calculates the amount of excess baggage to the passenger's final destination (that
includes oncarriage details if these are entered at the time of check-in) providing that the destination is
entered in the excess baggage destination cost display table (JCD).
Example of a passenger with excess baggage using weight concept without the inhibit boarding card
program being loaded:
PA:XS639YMIA1GRAHAM/FMR,2/25
Response to PA:XS639YMIA1GRAHAM/FMR,2/25
PA:XS639/22JUNYMIA1GRAHAM/FMR,2/25
AV Y75
PAD Y2
737/A
GTD/G07 POS/GATE BTD1635 SD1700 ED1700 SA1930 FT0230
1. GRAHAM/FMR
BN031 SN12F
EXB:1/5KG/CASH/USD65
EXCESS BAGGAGE CHARGE/UNIT $ 13.0
The passenger has to pay USD65 for 5 kgs excess 2. The excess baggage charge in this example is
USD13 per one kg and even though the passenger has excess baggage, the boarding card will print.
Example of same passenger with excess baggage using weight concept but this time the inhibit
boarding card program is loaded:
PA:XS639YMIA1GRAHAM/FMR,2/25
Optionally, the boarding card print can be inhibited.
The charge has to be accepted by transmitting after the 65; otherwise, the excess amount is not
recorded in the excess baggage statistics.
Page 152
Response to PA:XS639YMIA1GRAHAM/FMR,2/25
PA:XS639/22JUNYMIA1GRAHAM/FMR,2/25
AV Y75
PAD Y2
737 A
GTD/G07 POS/GATE BTD1635 SD1700 ED1700 SA1930 FT0230
1. GRAHAM/FMR
BN031 SN12F
EXCESS BAGGAGE CHARGE/UNIT $ 13.0
BOARDING PASS PRINT INHIBITED
The passenger must now pay the excess charge. Once that is completed the boarding card can be
issued. However, this involves four steps:
1.
The agent must re-display the passenger record. This can be retrieved by name, boarding
number, or seat number.
Example:
PDD:XS639Y,BN031
Response PDD:XS639Y,BN031
PDD:XS639/22JUNYMIA,BN031
1. GRAHAM/FMR
BN031
ACC VDT3823 AGT724/22JUN1502
2.
SN12F
Y MIA
BAG2/25/0
Enter EXB followed by the entry number which should be 1, then a / and the system gives the
correct amount of excess due.
EXB:1/
Response to EXB:1/
Note: It is possible to enter a particular type of currency after CASH so that the system converts the
charge to that currency (providing that currency rate of exchange is entered in the JXD table).
Example:
EXB:1/5KG/CASH/UKL
Response to EXB:1/5KG/CASH/UKL
EXB:1/5KG/CASH/UKL39
3.
When the system responds with the cost of the amount to be charged, go to the end of this
entry and re-transmit:
<Transmit>
Response to EXB:1/5KG/CASH/USD65
CHARGE ACCEPTED

Page 153
4.The boarding card can now be issued by entering:

BC:1
Response to BC:1
BOARDING PASS RE-ISSUED
Note: If you try and issue the boarding card (BC:1) before getting the response 'CHARGE
ACCEPTED', the system responds 'BOARDING CARD INHIBITED'.
8.14. Bag Tag Issuance (B)

An agent input starts Bag Tag printing.
System defaults tag issuance to the check-in destination or to the destination specified at the time of
agent input.
8.14.1 PA Input / Response
Other PA functionality remains as it is, whether used to accept a passenger from a prior PS display, or
whether the actual flight number and passenger's name are used in the check-in entry.
O, O2, and O3 check-in and processing remain the same. All examples use O for simplicity.
Options
If baggage information is input, the agent may use any of the following options:
B to print the Bag Tag.
Destination. Unless the check-in is for a single flight only, it is advisable to always enter the Bag
Destination in the check-in entry.
Bag Tag number, to allow the agent to input a manual Bag Tag.
If a manual Bag Tag is input in a passengers record, destination is a mandatory field.
A bag can be marked hot for baggage with close connecting times or other airline reasons.
1
Checks in passenger, issues no Bag Tags.
PA:1,1/10
Checks in passenger, attempts through check-in. Issues no Bag Tags, so EDIFACT check-in is not
attempted.
PA:1,1/10,O
Will check in passenger, and issue Bag Tags to the checked-in destination. If the passenger has an
outbound remark in his record, no through check-in or EDIFACT check-in is attempted, as the input did
not include the O option.
PA:1,1/10,B

Page 154
Will check in passenger, and issue Bag Tags to the destination specified, as long as that destination is
in the passenger's record and at the same time attempting the through check-in or EDIFACT
processing.
PA:1,1/10,B/DEST,O
Will check in passenger, update passenger record with manually entered tag number (so no automatic
Bag Tag is printed); and attempts through check-in or EDIFACT processing.
PA:1,1/10,B/LHR/AA123456,O
An example of how to input manual Bag Tag numbers by range.
PA:1,3/30,B/ATL/AA123456-458
Designate a bag as hot. To utilize the hot feature, the airlines Bag Tag PECTAB must be changed.
Contact SITA Customer Support for assistance.
PA:1,1/10,B/DEST/H,O
Only manually added Bag Tags are allowed without the requirement of a PID number entered for
BTAG on the DPID: display. If the system attempts to print Bag Tags, then the system checks to
make sure a PID number was entered otherwise it provides the following error response:
042 - UNABLE
Note: Online 'through check-in is permitted without Bag Tag information, however EDIFACT
processing is not attempted if bag count and tag counts are not equal.
Error Responses
If no baggage is input with the PA transaction, the previous options are not allowed and a 'FORMAT'
rejection message displays.

Page 155
8.14.2 PU Input / Response

Other PU functionality remains as it is, whether used to modify a passenger record from a prior PS
display, or PDD display.
O, O2, and O3 check in and processing remains the same. These examples use O for simplicity.
1 Examples:
Update passenger record, issue no Bag Tags.
PU:1,1/10
Update passenger's record, and issue Bag Tags to the checked-in destination. If the passenger has
an outbound remarks in his record, no through check-in or EDIFACT check-in is attempted, as the
input did not include the O option.
PU:1,1/10,B
Update passenger record, and issue Bag Tags to the destination specified, as long as that destination
is in the passenger's record. At the same time attempt the through check-in or EDIFACT processing
to issue Bag Tags as far as the Outbound to the first outbound destination while attempting through
check in or EDIFACT processing.
PU:1,1/10,B/DEST,O
Updates passenger record with manually entered Bag Tag numbers, and attempt through check in or
EDIFACT processing.
PU:1,1/10,B/LHR/AA12345678,O
An example of how to input manual Bag Tag numbers by range.
PU:1,3/30,B/ATL/AA12345678-680
Issue Bag Tags for bags already entered in the record providing no Bag Tags are already present (for
example if the agent failed to request the Bag Tags at PA).
PU:1,B
Reissue all Bag Tags in record.
PU:1,BR
Reissue the first and third Bag Tag in the record.
PU:1,BR1/3
Reissue the first five Bag Tags in the record.
PU:1, BR1-5
Note: The system does not allow the re-issue of manually entered and System generated Bag Tags in
the same entry. If the record does contain a mixture, then make sure the re-issue request is either for
only the Manually entered Bag Tags, or System generated Bag Tags, otherwise the entry is rejected.
For reissued bag tags, a user parameter determines if the same tag number or a new tag number is
issued. This parameter is controlled by pss.helpdesk@sita.aero.

Page 156
1 Example of PDD with original and new bag tags listed (the * indicates the original one):
PDD:XS166/16JUN Y ATL,1
PNR RL HE103YD
1. HUNTER/MMRS
BN023 SN10DY MIA TKNA/XS/0952485629412C1
BAG1/10/0 F1/75
0182938473/MIA
*0182938472/MIA
PU VDT27236 AGT97/16JUN1029/BAG
Error Responses
If no baggage is input with the PU transaction, the previous options are inhibited and a 'FORMAT'
rejection message displays.
8.14.3 PW Input / Response
Other PW functionality remains as it is, whether used to modify a passenger record from a prior PS
display, or PDD display.
O, O2, and O3 check-in and processing remain the same. All examples use O for simplicity.
1
PW:1,3/35,B/ALL
Deletes bags and all Bag Tags from passenger's record.
PW:1,1/10,B/1
Deletes bags and the first tag in the record.
PW:1,2/23,B/1/4
Delete bags and the first and fourth tag in the record.
If the passenger has been through checked in or EDIFACT through checked in, the PW cascades
down as it currently does.
If it is necessary to cancel a Bag Tag number, the system deletes it from the passenger's PDD record
but also sends a warning message to the GQ queue with the details of the Bag Tag number deleted,
the flight number, the passengers name, and the BN number associated with that bag. This is for
security reasons to help identify baggage discrepancies.
1 Example of Deleted Bag Tag Number to GQ

ATL501 GENERAL MSG
(0001)
BAG TAG DELETED
XS 0700 17SEP
ATL
ABBA
BN1
VDT11290 AGT295/17SEP1329
0182526828

Page 157
8.14.3.1To Display Any Deleted Bag Tags in a Passengers Record

When displaying the PDD of a passenger's record, DCS displays all Bag Tags. An asterisk (*)
preceding a bag tag number indicates that the bag tag was previously deleted.
The entry is:
PDD:ENTRY NUMBER
1
PDD:1
PDD: XS3227/18MARMATL,1
1. HUNTER/MRS
BN002 SN14C
M MIA BAG1/12/0 F1/75
O/XX935/18MAR
M ZRH
0182001203/MIA
*0182001202/MIA
PU
VDT2766 AGT66/18MAR1009/BAG 1/10
PW
VDT2766 AGT66/18MAR1009/BAG 1/10
PU
VDT2766 AGT66/18MAR1010/BAG 1/12
*** OUTBOUND XX0935 MIAZRH ***

Page 158
Error Responses
If baggage is deleted from a passenger's record, the deletion of corresponding number of Bag Tags is
required.
The following Error Responses may display due to an incorrect entry:
Error Message
Explanation
BAG NUMBER
The input baggage number is invalid.
BAG NUMBER RANGE
The input range of bag numbers is invalid.
BAG NUMBER REPEATED
An input baggage number was repeated.
BAG TAG
The input Bag Tag number is invalid.
BAG TAG RANGE
The input range of Bag Tag numbers is invalid.
BAG TAG REPEATED
An input Bag Tag number was repeated.
BAG TAG CONTENTS
Re-check input Bag Tag numbers.
DUP REF
Bag Tag numbers already entered.
ENTRY NUMBER
The entry number is invalid or does not exist.
FLT CANCELLED
The specified flight/city was cancelled.
FLT CLOSED
The flight is closed.
INV INPUT
Invalid entry number identified for Bag Tag entry.
MAXIMUM BAG NUMBERS

EXCEEDED
The number of bag numbers input is too large.
MAXIMUM BAG TAGS EXCEEDED
The number of Bag Tags input is too large.
NO ACTION
Incorrect entry specified.
NO DISPLAY
Input requires a previous display.
NOT ACCEPTED PASSENGERS
The identified passenger has not checked in.
PASSENGER ALREADY HAS TAGS
The passenger already has Bag Tags.
UNABLE
There is no Bag Tag printer attached to the CRT.
Table 8.16 Bag Tag Delete Error Responses

Page 159
8.14.4 Bag Tag Subsequent Processing

The generated Bag Tag numbers are stored in the passenger's PDD record.
1 Example of PDD with Bag Tag Numbers.

PDD: XS735/08JUNCATL,2 PNR RL
1.
ADAM/GMSTR
BN002 SN1C
C
0182526553
RES AUTO 07JUN1146
MOD VDT2856 AGT286/08JUN0910
H522T
MIA
BAG1/12/0
UM10
Note: The number is made up of ten digits in the following format:

Explanation of Bag Tag Number
Position
1st digit
Explanation
0 - Interline Tag.
1 - Fallback Tag (for sortation systems).
2 - Interline 'Expedite' Tag.
3 - Individual Airline's own use.
2nd to 4th
Three-digit Airline code assigned by ATA/IATA.
5th to 10th
Six-digit number of the Bag Tag (the first number issued will be 000001 up to
999999, then the system starts at 000001 again).
Table 8.17 Bag Tag Number Explanation

8.14.5 Bag Tag JL List
There are two lists that provide a list of all the Bag Tags issued for a flight. This list includes any
manually entered Bag Tags for 'unattached' baggage.
JL:BT/FLIGHT/DATE/CLASS
Lists passengers in Boarding (BN) number order.
JL:NT/FLIGHT/DATE/CLASS
List of passengers in Alphabetical order.

Page 160
8.14.6 Baggage Action List (BAL)

If a passenger is offloaded or does not board the aircraft, it is possible to identify his Bag Tag numbers
by checking the baggage action list (BAL).
BAL
The entry is:
BAL:FLIGHT/DATE
Response to BAL:FLIGHT/DATE
BAU:XS829/06AUGATL
OP/NAM
BAG TAG NUMBER DEST ACTION REASON
DONE? LOCATION
0136038534
MEX REMOVE PAX DEL BY PW N
0136038637
MEX REMOVE PAX DEL BY PW N
<- TRANSMIT HERE FOR UPDATE
There are further displays and transactions that can be entered for the BAL entry:
BAL:FLIGHT CITY,OPTION,ADDRESS
Note: The CITY is an optional entry, as the system defaults to CRT city.
The options are:
Option
Description
AL
All Baggage to Action.
HL
Baggage to Hold.
LD
Baggage to Load.
RM
Baggage to Remove.
XL
Baggage that is Loaded.
XR
Baggage that is Removed.
Table 8.18 Baggage Action List Options (CITY Options)

The address can be any of the following:
Address
Description
DEFAULT
If no address is specified, the system defaults to the CRT.
PRINTER
Any valid printer PID can be specified.
TELEX
Any valid teletype address can be specified.
Table 8.19 Baggage Action List Options (Address Options)

Page 161
8.15. Passenger Update (PU)

The passenger update transaction (PU) allows the agent to modify additions to a passenger's record
before or after check-in.
The following restrictions apply:
The PU transaction cannot be used to check-in a passenger, except to transfer to a new flight or to
through-check a passenger on to connecting flights once he has been checked onto the first flight.
The PU transaction can only be entered using range numbers from a previous display; it cannot be
entered by passenger's name. However a series of range numbers can only be used for items: O,
I, APT, PUPG, PDNG, UGPA, for all other items only one range number per passenger
transaction is permitted.
PU is restricted to gate CRT after initial (CI) close, but only if there is a CRT associated with the
gate entered for the flight.
A PU transaction for a not present (#) passenger cannot contain any of the following items: M, F,
CHD, O, MUS, COUR, EXST, JMP, XRES, UPG, DNG, URES, Z.
The PU transaction cannot be used to change gender for a checked-in passenger. The passenger
must be offloaded (PW), and then checked-in again (PA) with the correct gender.
The PU transaction for a checked-in passenger cannot contain the items: ID, STCR, GRP, and
URES unless the URES is after an O item.
Only MSG, PSM, URES, XRES, SNR, RQST, JMP, INF, BSCT, are allowed after an O item.
The PU transaction can be used to recheck passengers short of their original destination on the
same flight (Example: PU:ENTRY,Z FLT CLS NEW DEST ).

Page 162
1 Examples of Different Passenger Updates (PU)

1.Change a seat number for a checked-in passenger:
PU:4,R21A
The system issues new boarding passes.
2.Leave a Message for a passenger who has not yet checked-in:
PU:#9,MSG PLSE CALL HOME ASAP
3.Correct the spelling of FAMILY MURPHY before check-in:
PU:#1,NAM3MURPHY/DMR/SMRS/CHD
Note: A name change can be done before check-in, but then it must be for all the names
under the same record. After check-in it is possible to change only one name within the same
record (PU:1P2,NAM1MURPHY/TMRS), but DCS will then split the record into two records.
4.Reserve a Seat for a passenger who has not yet checked-in.
PU:#6,R12C
Note: The PU transaction can only be used for a single passenger. If more than one
passenger needs to be pre-seated, then the PA transaction must be used. Example: PA:#14,R17A-D
5.Add Oncarriage details to a checked-in passenger:
PU:1,OIB735MLIS
6. Add a marketing segment to a passengers record on a code share flight:
PU1,MKTXS141Y01ATLJFK
Note: When adding a marketing segment to a passenger's record, it is only necessary to add
the day but not the actual month in the entry.
7.Change WCHS item to WCHR for entry number 4:
PU:4,WCHR,R12A
Note: When changing Wheelchair items, it is necessary to also add the original seat request
(to retain the same seat) otherwise the system automatically allocates a seat.
8.To re-seat a passenger on the second leg of a multi-sector flight:
PU:ENTRY NBR,SNR17A/SEGMENT
Example:
PU:1,SNR17A/ATLMIA
Note: Remember to use SNR when requesting the new seat. If R is used, the system
responds: MODIFICATION NOT POSSIBLE.
9. Add a passport to passenger Lauren Wells after checking her in:
Example:
PU1,PSPT/A12345/US/16DEC71/F/WELLS/LAUREN/19OCT05/US

Page 163
10.
Check in passenger Lauren Wells on a connecting segment after checking in on the first flight
only:
Example:
PU1,O
Example:
PU1,O FLT NBR/DATE CLASS DEST
11. Add a double oncarriage segment to a passengers record after check-in:
Example:
PU1,OXS113YLHR
12. Add denied boarding voluntary remarks to a passenger's record after check-in:
Example:
PU1,DBV/PASSENGER REBOOKED XS111
13. Add denied boarding involuntary remarks to passengers record after check-in:
Example:
PU1,DBI/PASSENGER REBOOKED XS111
Note: Free text up to 25 characters is allowed with DBV and DBI entries.
14.
Add a second connecting flight as double oncarriage, XS133, Y CLASS ATLMIA, to passenger
John Hoffman after he is already checked in:
Example:
PU1,OXS133YMIA
15.
If a passenger checked-in without a TKNE element, which now needs to be added, then the
passenger must first be deleted from the flight, and checked-in again but this time the TKNE
element must be included:
PU:1,O,TKNE/0958476394863C1
16.
Passengers with the following SSRs are allowed to ITCI:

UM,INF,BSCT,DEAF,BLND,FQTV,SPML, PETC, SNR, WCHR,DOCA/DOCS/DOCO,PCTC.
Once ITCI is entered, update transactions are processed just as with Through Check-In:
To add a WCHR to a passenger checked in on an ITCI flight.
PU1,WCHR
To change a seat on the onward flight to 6F.
PU1,O,R6F
17.
Add EXST with TKNE for a passenger who has not yet checked in:
PU#1,EXST,TKNE/XXXXXXXXXXXXXC1-EXST

Page 164
8.16. Passenger Delete (PW)

The passenger delete transaction (PW) allows the agent to modify deletions to a passenger's record
before or after check-in.
Note: A deleted passenger can be re-accepted if required. One or more records can be deleted using
PW in the same entry. Therefore, if a group of passengers are to be offloaded, they can be deleted in
one entry. This does not apply to interline thru check-in. If passengers are ITCI, and do not have the
same surname, then the passengers will need to be deleted separately. For more information see
Checking In Passengers on a Connecting Flight.
1 Examples of PW transactions are:

1.Offload one entry number or a range of entry numbers:
PW:-ENTRY NUMBER
PW:-ENTRY NBR-ENTRY NUMBER
Example:
PW:-3
PW:-3-6
2.Delete some baggage (1/10) from a checked-in passenger:
Example:
PW:1,1/10
3.Delete item MSG from a checked-in passenger:
Example:
PW:1,MSG
4.Offload one checked-in passenger from a group with no bags:
Example:
PW:-1P2,F1,0/0
Note: The gender (F1, M1, CHD1, etc.) is needed on gender-required flights.
5.Offload passenger using Seat Number:
PW:FLIGHT CLASS - SEAT NUMBER
Example:
PW:100Y - SN17A
6.Cancel check-in on down line flight segment from a passenger's record:
Example:
PW1,O
7. Delete a passport from one or all passengers record:
Example:
PW1,PSPT/ALL

Page 165
8.Delete a passport from passengers one and three in a record:

Example:
PW1,PSPT/1/3
9.Delete a passport from a single passenger record:
Example:
PW1,PSPT/1
10.Delete a marketing segment from a passenger's record:
Example:
PW1,MKT
11. Delete an infant from a passenger's record:
Example:
PW1,INF
Note: If deleting one infant where there are two traveling, show the weight.
12.Delete the first person of a party of four on a gender required flight and all bags in his record:
Example:
PW-1P2,M1,3/30,B/ALL
13Delete the second person in a party of four and the first bag in the record:
Example:
PW-1P2,1/10,B/1
14.
There is no change to current processing in using the PW entry except for the TKNE
element. Attempting to remove a TKNE element before or after check-in is inhibited. A
warning message displays if an agent tries to remove a TKNE element.
15.
Delete transactions remain the same as with Through Check-In.

To delete special meal:
PW1,VGML
To delete wheelchair:
PW1,WCHR
To delete passenger on all flights.
PW-1
To delete the onward flight (You can add a new onward flight e.g.,
A1,1/12,OYZ837YGLA,URES). It is important to add the URES after the onward flight;
otherwise the system responds "Transfer Status Conflict".
PW1,O,XRES
A Reconciliation Exist whereby you receive an unsuccessful ITCI attempt. At this point it is likely both
systems are not synchronized.
PDD:1,O
ITCI transaction sends a message to the partner system to return an

update of the passenger record/status.
Page 166
If the entry is successful it displays on the screen. If unsuccessful, a

warning or error message displays.

Page 167
9. Staff Priority Table

9.1. Staff Priority Table Display (PZ)
Any agent can display the staff priority table for their airline. The database staff creates this table for
your airline.
The entry is:
PZ:AIRLINE
Response to PZ Airline
TRAVEL STATUS
CODE
------------REVENUE
S1/
RI
N1
#S2
#R2
#N2
#NON-REV
BOOKED
PRIORITY
-------1
2
4
5
# 30
# 40
# 50
# 90
WAITLISTED
PRIORITY
---------3
6
8
# 9
# 30
# 40
# 50
# 90
UNBOOKED
PRIORITY
--------7
# 10
# 11
# 12
#?60
#?65
#?70
#?99
The lower the number, the higher the priority. If the travel status code is followed by a '/', there is no
requirement to add the date of joining. Those codes which do not have the / indicate the date of
joining is an optional entry. It is entered as three letters for month followed by two numbers for year
(example: JAN89).
The '#' before the number indicates that the passenger is available for disembarkation (PAD) and the
'?' indicates that the passenger has a space available ticket.
1 Example of checking-in a non-listed airline staff passenger:

PA:XS936Y1JACKSON/DMR,1/10,IDR2/FEB81,URES

Staff Priority Table
Page 169

Staff Priority Table
Page 170
10. Flight Destination / Remarks

10.1. Flight Remarks Display (RK)
Any agent can display the remarks for a particular flight. The entry is:
RK:FLIGHT NUMBER
Note: Date and boarding city are further optional entries, and the Entry allows up to 128 characters.
1
RK:XS826/+ MIA
10.2. Destination Remarks Display (DR)

Any agent can display the remarks for a particular destination. The entry is:
DR:DESTINATION
Note: To display the remarks for a handled airline for a particular destination, the airline code must be
inserted before the destination. The entry allows up to 64-characters.
DR:AIRLINE DESTINATION
1
DR:KL JFK

Flight Destination / Remarks
Page 171

Flight Destination / Remarks
Page 172
11. Flight Default Assignment and Display

11.1. Flight Default Display (FDT)
Any check-in agent may assign their sign-in work area to default to a particular flight. The staff can
then enter the default code of (*) in place of the flight number for every check-in entry. This reduces
the amount of data the agent has to enter. The default code is only beneficial for those agents who
are dedicated to one particular flight, and is not recommended for agents who handle multiple flights.
The default code displays as the character *.
The entry to assign the default code to a flight is:
FDT:FLIGHT NUMBER
To display the flight assigned as the default flight enter:
FDT:
The response will either be a flight number and date, or the system displays NO DEFAULT FLIGHT
meaning there is no default flight assigned to this particular CRT.
To clear a CRT of any default flight enter:
FDT:-

Flight Default Assignment and Display
Page 173

Flight Default Assignment and Display
Page 174
12. Passenger Boarding Control

12.1. Boarding Status Display (BSD)
When there are fewer than 50 who have checked-in and who have not yet boarded the aircraft, use
the boarding status display (BSD) screen to see a list of the passenger names with a total number of
checked-in, boarded and not boarded passengers. The entry is:
BSD:FLIGHT CLASS
Response to BSD:XS629Y
BSD:XS629/06AUGATL
OP/NAM
DC9/D GTD/12 POS/GATE BDT1220 SD1300 ED1300 SA1500 FT0350
PASSENGERS CHECKED-IN : Y68
PASSENGERS BOARDED
: Y0
PASSENGERS NOT BOARDED : Y68
1. 1BARNES/F
BN025
SN21A
Y BOS
2. 2LYONS/MR
F2 BN015
SN10E
Y BOS
LYONS/MRS
F2 BN016
SN10D
Y BOS
3. 1MILLER/IAN
BN007
SN19C
Y BOS
4. 1POWELL/MR
BN039
SN15F
Y BOS URES
Explanation:
The 'F2' after the passenger named LYONS is the group identifier, which came from the PNL (this
makes it easier to identify passengers traveling together).
When there are more than 50 passengers checked-in who have not yet boarded the aircraft, the
boarding status display (BSD) provides the total number of passengers checked-in, boarded, and not
boarded on the flight. The entry is:
BSD:FLIGHT/.
Response to BSD:XS629/.
BSD:XS629/15nov
BSD: XS629/15NOV ATL
320/A
GTD/6
POS/GATE BDT1650 SD1720 ED1720
PASSENGERS CHECKED-IN : C12Y89
PASSENGERS BOARDED
: C10Y29
PASSENGERS NOT BOARDED : C02Y60
CC/NAM
SA2100
FT0240
If the list contains fewer than 50, then the actual passenger names display. If the list contains more
than 50 names, then only the total number of passengers still to board displays. The display provides
the names of the passengers, the boarding numbers, seat numbers with class, and destination.
Note: If only one passenger from a 'family' entry number is 'Boarded', the system continues to display
the whole family as 'Not Boarded', until the whole entry has Boarded.

Passenger Boarding Control
Page 175
12.2. Boarding Acceptance by Boarding Number (BAB/BDB)

This transaction either accepts a passenger as boarded or deletes an already boarded passenger by
using the boarding number (BN). The CRT must be assigned to the default flight by the FDT
transaction (if not the response is 'FLT/NBR').
BSD/BAB/BDB
Note: Check that your CRT is defaulting to the correct flight number and date, otherwise the BAB
transaction may board a passenger on the wrong flight.
The acceptance entry is:
BAB:BOARDING NUMBER
Note: More than one boarding number can be specified in the same entry (maximum is 511 boarding
numbers).
Entry:
BAB:1,6,23-30,36,45
The reply to a successful input is the total number of passengers entered followed by the 'BOARDED'
response.
If an invalid boarding number is specified, or a boarding number entered was previously entered the
reply is the number of passengers boarded, followed by the number and reason of the boarding
numbers not accepted.
Response to BAB:1,6,23-30,36,45
BAB:10,17,53
1 BOARDED
2 BOARDING NUMBERS NOT ACCEPTED
BN
REASON
10
PAX ALREADY BOARDED
53
INVALID BN
The BDB transaction offloads an already boarded passenger (using the boarding number) who has
either been previously accepted in error, or has disembarked from the aircraft.
The conditions and procedures are the same as for the BAB transaction. The entry is:
BDB:BOARDING NUMBER
RANGE OF BOARDING NUMBERS
The response is either 'ACCEPTED' or 'BOARDING NUMBERS NOT ACCEPTED' followed by the reason.

Page 176
12.3. Boarding Acceptance / Delete by Seat Number (BAS/BDS)

This transaction either accepts a passenger as boarded, or deletes an already boarded passenger by
using the seat number (SN). The CRT must be assigned to the default flight by the FDT transaction (if
not the response will be 'FLT/NBR').
The acceptance entry is:
BAS:SEAT NUMBER
Note: More than one seat number can be specified in the same entry, provided each seat is entered
individually and separated by a ",".
Example entry:
BAS:21A,10D,10E,23D
Response to BAS:21A,10D,10E,23D
BAS:21A,10D,10E,23D
3 ACCEPTED
1 SEAT NUMBER NOT ACCEPTED
SEAT NO REASON
23D
PAX NOT CHECKED IN
The BDS transaction offloads an already boarded passenger (using the seat number) who has either
been previously accepted in error, or has disembarked from the aircraft. The conditions and
procedures are the same as for the BAS transaction. The entry is:
BDS:SEAT NUMBER
The response is either 'ACCEPTED' or 'SEAT NUMBERS NOT ACCEPTED' followed by the reason.
Note: Use this transaction when gate readers are not used.

Page 177

Page 178
13. Glossary
-AADL - Add/Delete List.
AEC - Automatic Equipment Change.
ALD - Automatic Load Planning.
AO - Agent Out Screen.
API - Advance Passenger Information.
APP - Advanced Passenger Processing System
-BBAB - Boarding Acceptance by Boarding Number screen.
BAS - Boarding Acceptance Screen.
BC - Boarding Card Issuance, Boarding Card Inhibit.
BDS - Boarding Delete Screen.
BI - Basic Index.
BN - Boarding Number.
BRC - Bulk Recheck Accepted passengers.
BRN - Bulk Recheck Not Checked-In Passengers.
BSD - Boarding Status Display screen.
BTM - Baggage Transfer Message.
-CCFL - Check In Flight List Display.
CKI - Check-in.
CND - Configuration Table Number Display.
COM - Close Out (final) Message. (Dispatched to all stations).
CPM - Container/Pallet Message.
CRT - Cathode Ray Tube, this is the display.
CSD - Created Schedule Data.
CSM - Created Schedule Modification.

Glossary
Page 179
-DDA - Display Area.

DFL - Delete Flight.
DOI - Dry Operating Index.
DPID - Entry for Printer/Check-in Zone Information.
DR - Destination Remarks Display Screen.
DRC - Destination Remarks Creation.
DX - Decode Screen.
-EEDIFACT - Electronic Data Interchange for Administration, Commerce and Transport.
EMR - Expected Movement Record.
ETL - Electronic Ticket List.
ETM - EDIFACT Transfer Message (ITCI partner listed from departure city LH only).
EX - Encode Screen.
EXB - Excess Baggage Screen.
-FFDC - Flight Schedule.
FDD - Flight Data Display.
FDT - Flight Default Display screen.
FIR - Flight Irregular Operations.
FLP - Flight Planning.
FTL - Frequent Traveler List.
FUI - Flight Update Information.
-GGMT - Greenwich Mean Time.
-HHELP - SITA Help for the application.

Glossary
Page 180
-IIDM - Industry Discount Message. (Dispatched to next down line station on Multi-sector flights.)
IFM - Interline (EDIFACT flights) Fallback Message.
IOD - Inbound/Outbound Display Screen.
-LLDP - Load Planning.
LDVS - System Selected Deck Version.
-MMD - Manifest Display.
MVT - Movement Message.
-NNAM SS - Name Check-In with Seat Selection.
NPRO - Releases all records, except the PNL / ADL records for the flight, and clears the Manifest
Index so a PNL will no longer show processed.
NOREC - No Record. A passenger with a booking but whose name is not on the PNL.
-PPA - Passenger Acceptance screen.
PAD - Passenger Available for Disembarkation.
PCI - Passenger Statistics.
PCTC - Passenger Contact.
PDD - Individual Passenger Record Display.
PDQ - Physical Device Queuing.
PFS - Passenger Final Sales message. (Originating station only).
PID - Physical device identifier. Numeric address of a peripheral device that is also known as
position identifier or port identifier.
PIL - Passenger Information List. (Originating station only).
PIM - Passenger Information Message.
PN - Page Next.
PNL - Passenger Name List.
PRL - Passenger Reconciliation List.
PS - Passenger Display Screen.
Protected WorkstationProtected workstations require a personal account number and check letter
during sign-in.
PSM - Passenger Service Message. (Dispatched to all stations.)
PTM - Passenger Transfer Manifest. (Dispatched to all stations having transfer.)
PU - Passenger Upgrade.
PW - Passenger or Item Withdrawal or Delete.
PZ - Staff Priority Table Display screen.

Glossary
Page 181
-RRCS - Response Capture System

RK - Flight Remarks Display screen.
-SSB - Standby Number, Standby Display Screen.
SDD - Passenger Survey Display.
SE - Seat Map Display.
SI - Sign in Screen.
SLD - Statistical Load Summary.
SO - Sign Out Screen.
SOM - Seats Occupied Message. (Dispatched to next down line station.)
SSR - Special Service Request.
STD - Scheduled Time of Departure.
SUD - Special Usage Description.
-TTCC - Time Calculation Screen.
TSA - Travel Security Agency.
-UUnprotected WorkstationUnprotected workstations do not require a personal account number and
check letter during sign-in.
URES - A passenger who wants to travel on a flight, but is not booked or listed for the flight on the
PNL.
Style Symbols
1 Example indicator
X Start of Entry indicator

Glossary
Page 182
14. Index
Acceptance
Passenger..................................................59
Access to SITA DCS ..........................................3
Active Code share Flight
Example.....................................................24
Active Flight......................................................23
Example.....................................................24
Adding Infants
Address Information ...............................86
Place of Birth and VISA Information......89
Adding PSPT after Initial Check-in...................95
Address Information
Adding Infants..........................................86
Address Information .........................................85
Advanced Passenger Processing System101, 110
Agent
Automatic System Checks...........................4
Agent Control .....................................................3
Agent Information...............................................4
Agent Number
Agent Sign-In ...............................................5
Agent Sign-In .....................................................4
Cancellation............................................. 106
Check Multiple Passengers..................... 102
Check Single Passenger ......................... 102
Check-in Multiple Passengers................. 104
Passenger Limits.............................106, 112
Standby ................................................... 107
Automated Bag Tags
Check-in Unattached Bags Example ...... 145
Automatic System Checks
Agent ........................................................... 4
Available Restricted Film View Seat
SUD ........................................................... 29
Available Restricted Recline Seat
SUD ........................................................... 28
Available Seat
SUD ........................................................... 28
Available Seat for Unaccompanied Minor
SUD ........................................................... 29
Bag Tag
Expedite................................................... 148
JL List ......................................................160
Manual....................................................... 58
Bag Tag Delete
Agent without a Personal Account Number .......7
Error Responses ..................................... 159

Number Explanation................................ 160
Subsequent Processing ..................157, 160
Bag Tag Delete Input / Response.................. 157
Agent-In..............................................................6
Bag Tag Issuance .......................................... 154
Agent-In/Agent-Out
Error Responses ..................................... 155

Input / Response ..................................... 154
Subsequent Processing .......................... 155
Bag Tag Update
Agent with a Personal Account Number ............7
Error Response............................................6
Agent-Out ...........................................................6
Aircraft Compartment Limits/Control Messages31
Airline
Encode/Decode .........................................11
Airport
Encode/Decode .........................................11
Amount Over Load Planning Weight
Allowance .....................................................35
Error Responses ..................................... 157

Examples................................................. 156
Input / Response ..................................... 156
Baggage Action List ....................................... 161
Bagtag
Search by .................................................. 57
Bassinet Seat
Amount Under Load Planning Weight

Allowance .....................................................35
SUD ........................................................... 28
Blocked Seat
API Paxlist ........................................................79
SUD ........................................................... 29
Boarding Acceptance
APP
Index
Page 183
Boarding Pass Inhibit .....................................152
PAD .................................................120, 121

Passenger Acceptance ............................. 59
Previous PS List Display ........................ 60
Standby ................................................... 120
Unattached Baggage............................... 145
URES...............................................120, 121
Check-In Flight List Display ............................. 17
Boarding Pass Issuance/Inhibit......................151
Check-in Multiple Passengers
Boarding Process
APP ......................................................... 104

Check-In Procedures .................................60, 61
Delete by Seat Number ...........................177

Boarding Acceptance By Boarding Number ..176
Boarding Card Reissue ..................................141
Boarding Control ............................................175
USA Watchlist..........................................116
Boarding Status Display.................................175
Booked Display ................................................43
Check-In Weight Allowance............................. 34
Bulkhead Seat
Checking in Passengers with a Destination

or Residence Address ............................... 85
SUD ...........................................................29
Cancel
Checking in Passengers with Place of Birth

and VISA information................................. 89
APP..........................................................106
CFL Examples..................................................18
Checking-In Passengers on an Overweight

Flight............................................................. 68
CFL Transaction...............................................17
No Segment Information............................21
Check in
ID .............................................................140
NOREC....................................................140
URES.......................................................140
Check In Entry Examples.................................71
Check Multiple Passengers
APP..........................................................102
Check Single Passenger
APP..........................................................102
Checked-In Display ..........................................43
Checked-In Passengers
Upgrade/Downgrade .................................66
Check-in
Unattached Bags .....................................145
Check-In
Dead Head Crew .....................................145
Detailed......................................................61
Detailed Entry...........................................60
Example Check-In of a Multi Sector Flight
with Gender ...............................................61
Example Check-In of a Single-Sector
Flight that does not Require Gender .........61
Example for a Non-Gender Required
Flight ..........................................................63
Gender Required Flights ...........................62
Group.......................................................118
Norec .......................................................120
Oncarriage .................................................69
Checking-In Passengers on ITCI Flight ........... 70

Checking-In Passengers with Double
Oncarriage Segments .................................. 68
City
Agent Sign-In Error Response .................... 5
Encode/Decode......................................... 11
Code share Example
Seat Map ................................................... 30
Code share Flight
NOREC/URES Passengers with a
Marketing Segment ................................. 123
Code share Flight with Marketing Partner Only40
Code share Flight with Multiple Code share
Partners........................................................ 39
Code share Flight, Active
Example..................................................... 24
Code share Flights with SDD........................... 39
Code share Passenger
PDD ........................................................... 54
Code share, Marketing Partners
Maximum ................................................... 30
Course Objective ............................................... 1
Crew Entries .................................................... 98
Currency
Encode/Decode......................................... 11
Customer Number
Index
Page 184
Daily Flight List Display ....................................17

Dead Head Crew Check-In ............................145
Decode .............................................................11
Entry ..........................................................12
Delete
PSPT Remark............................................96
Delete Bag Tag, Example ..............................157
Delete by Seat Number
Boarding Acceptance ..............................177
Delete or Change Onward Connections ........149
After Check-In..........................................149
Before Check-In.......................................149
Delete Passenger...........................................165
Passenger ................................................. 43
PDD by Boarding Number......................... 56
PDD by Name ........................................... 55
PDD by Passenger from another Station .. 57
PDD by Seat Number................................ 56
PDD by Standby Number .......................... 56
PDD for Code share Passenger................ 54
PDD with Double Oncarriage Segment..... 54
Seat Map ................................................... 27
Staff Priority Table................................... 169
Standby ..................................................... 49
Standby/Notification .................................. 49
Display Area....................................................... 9
Display Deleted Bag Tags in Passenger
Record........................................................ 158
Display Paging ................................................. 10
Delete PSPT Remark
Display Unattached Bags .............................. 146
Error Responses........................................96
Processing .................................................96
PW Input ....................................................96
PW Output .................................................96
Use and Restrictions .................................96
Delete Unattached Bags ................................147
DOCA............................................................... 79
Deleting a Bag Tag
DOCS............................................................... 79
Oncarriage .................................................69
Deleting a Passenger Item.............................134
Travel Document Information .................... 80

DOCS, DOCO or DOCA Information
Error/Warning Response .........................136

Deleting a Passenger Item Time Out
Response ...................................................135
Entries to List Passengers......................... 90

Double Oncarriage Segments, Checking-In
Passengers with ........................................... 68
Deleting an Onward Flight
Downgrade Passengers .................................. 66
After Check-in ........................................139

Before Check-in .....................................139
Deleting an Onward Flight Before/After Checkin
Cancel ....................................................... 67
Emergency Exit Seat
Normal Response ....................................138

Destination Remarks Display .........................171
Detailed Check-In.............................................61
Different Destination
Re-Checking Passengers..........................67
Display
Boarding Status .......................................175
Booked.......................................................43
Checked-In ................................................43
Destination Remarks ...............................171
Flight Default Assignment........................173
Flight Remarks.........................................171
Inbound Outbound Passenger...................43
Individual Passenger Record.....................52
DOCA - Address Information ........................... 85

DOCO .............................................................. 79
DOCO (Other Travel Related Information)
Information ................................................... 88
SUD ........................................................... 28
Encode............................................................. 11
Entry .......................................................... 11
Encode/Decode
Airline......................................................... 11
Airport ........................................................ 11
City ............................................................ 11
Currency .................................................... 11
Entries to List Passengers with DOCS, DOCO
or DOCA Information.................................... 90
Entries to List Passengers with Missing
DOCS, DOCO or DOCA Information ........... 91
Error Response
Agent Sign-In/Sign-Out ............................... 6
Error Responses

Index
Page 185
Bag Tag Delete........................................159

Bag Tag Issuance....................................155
Bag Tag Update.......................................157
Delete PSPT Remark ................................96
Passport Information at Check-In Time .....94
UN Paxlist ..................................................92
Example
Check-In for a Non-Gender Required
Flight ..........................................................63
Check-In of a Multi-sector Flight with
Gender.......................................................61
Check-In of a Single Sector flight that does
not Require Gender ...................................61
Code share Flight with Marketing Partner
Only ...........................................................40
Code share Flight with Multiple Code
share Partners ...........................................39
Delete Bag Tag........................................157
DOCA ........................................................85
DOCO ........................................................88
DOCS ........................................................80
Inhibit Boarding Pass...............................151
Need Notification .......................................51
NOREC Passenger .................................120
Passenger Display Request ......................48
Passenger Update ...................................163
SDD for an Overweight Flight that is
Accepting Passengers...............................41
Standby......................................................52
Example of Flight Activation when a Seat Map
is Displayed ..................................................22
Examples
Bag Tag Update.......................................156
Check-In Entries ........................................71
Passenger Update ...................................162
Excess Baggage ............................................152
Expedite Bag Tags.........................................148
Extra Crew Check-in ......................................144
Extra Leg Room Seat
SUD ...........................................................29
Flight Activation when a Seat Map is
Displayed
Example.....................................................22
Flight Close Out Process
USA Watchlist..........................................117
Flight Data Display ...........................................23
Update .......................................................25
Flight Default Assignment and Display ..........173
Flight Default Display .....................................173
Flight Destination/Remarks............................ 171

Flight Information Displays and Updates ......... 23
Flight Irregular Operations ............................... 25
Flight List Display
Check-In .................................................... 17
Flight Remarks Display.................................. 171
Flight Update Information ................................ 25
Format
Agent-In/Agent-Out Error Response ........... 7
Function
Gender Required Flights.................................. 62
General Information ........................................... 1
Group Check-In.............................................. 118
Group Seats, Reserved
SUD ........................................................... 28
Handicap Seat
SUD ........................................................... 28
Help.................................................................. 15
ID Check in .................................................... 140
Infant Courtesy Seat
SUD ........................................................... 28
Infant Seat
SUD ........................................................... 29
Information
General........................................................ 1
Inhibit Boarding Pass ..................................... 151
Boarding Number .................................... 151
Entry Number from Previous Display ...... 151
Group Name............................................ 151
Seat Number ........................................... 151
Standby Number ..................................... 151
Initial Check-in, Adding PSPT after ................. 95
Issue Bag Tag................................................ 154
Issue/Inhibit Boarding Pass ........................... 151
ITCI
Checking in Passengers............................ 70
USA Watchlist ......................................... 115
ITCI Passenger Handling Procedures ........... 124
JL List
Bag Tag ................................................... 160
Last to be Used
Index
Page 186
SUD ...........................................................28
Load Planning Weight Allowance ....................35
Oncarriage
Master Flight
Check-In .................................................... 69
Deleting a Bag Tag.................................... 69
NOREC/URES Passengers .................... 122
NOREC/URES Standby Passengers ...... 122
Oncarriage Segments
Example.....................................................23
Master Flight ....................................................23
Checking in Passengers with Double........ 68

Onward Flight
Missing DOCS, DOCO or DOCA Information
Passenger Not Checked-In ..................... 142

Other Travel Related Information .................... 88
Local PAD ........................................................49

Manual Bag Tag...............................................58
Entries to List Passengers.........................91

Mode of Update................................................25
Other Travel Related information (DOCO) ...... 79
Modification
Over Check-in Weight Allowance .................... 35
Passenger..................................................59
Multi-Page Displays
Overweight Flight
Paging........................................................10
Multiple Areas
Checking in Passengers............................ 68
Overweight Flight with SDD............................. 41
PA Input
Sign-Out.......................................................8
Name Check-in ................................................59
Passport Information at Check-In Time..... 93

PA Seat Requests.......................................... 128
Need Notification..............................................49
PA Subsequent Processing
Example.....................................................51
No Record
Thru Check-In.......................................... 129

PAD Check-In ........................................120, 121
Agent Sign-In Error Response.....................5

No Segment Information
Paging.............................................................. 10
CFL Transaction ........................................21

NOREC ..........................................................141
NOREC Check in ...........................................140
Multi-Page Displays................................... 10
Partial Name Check-in..................................... 59
Passenger
NOREC Passenger ........................................141
NOREC.................................................... 141
URES....................................................... 141
Passenger Acceptance............................59, 124
NOREC/URES Passengers with a Marketing

Segment on a Code share Flight................123
Check-In .................................................... 59
Passenger Boarding Control.......................... 175
NOREC/URES Passengers with Oncarriage.122
Passenger Check-In Weight Table .................. 35
NOREC/URES Standby Passengers with

Oncarriage..................................................122
Passenger Contact Information ....................... 79
Norec Check-In ..............................................120
Normal Response
Deleting a Passenger on an Onward Flight137
Deleting a Passenger on Both Flights .....138
Deleting an Onward Flight Before/After
Check-in...................................................138
Numberic Check-in...........................................59
Passenger Delete ..................................133, 165

Passenger Deleted off the Onward Flight...... 143
Passenger Display ........................................... 43
Passenger Display Request Example ............. 48
Passenger Displays
Occupied Seat
USA Watchlist ......................................... 117

Passenger Handling Display............................ 97
SUD ...........................................................28
Office
Passenger Handling Displays
PS Input..................................................... 97

Index
Page 187
PS Output ..................................................97
Passenger Handling Procedures
PDD Display.......................................52, 97, 142
ITCI ..........................................................124
Passenger Limits
Place of Birth and VISA information
APP..................................................106, 112
Passenger Manifest Information ......................79
PDD Display with Double Oncarriage Segment54

Checking in Passengers with ................ 89
Place of Birth and VISA Information
Passenger Modification....................................59
Adding Infants ......................................... 89

Pre-downgrade Passengers ............................ 66
Passenger Notification ...................................150
Pre-upgrade Passengers................................. 66
Passenger Record Display.............................142
Previous PS List Display
Passenger Survey Display ...............................33
Check-In .................................................... 60
Printing............................................................. 10
Passenger Update ...........................................59

Examples .................................................162
Passenger Update Entry ..................................67
Priority Table, Staff ........................................ 169
Passenger Update, PU ..................................129
Delete PSPT Remark ................................ 96

Prot Set
Passenger Updates
USA Watchlist..........................................117
Passenger Withdrawal .....................................59
Passengers
Cancel Pre-upgrade/Pre-downgrade.........67
Pre-upgrade/Pre-downgrade .....................66
Upgrade/Downgrade .................................66
Passengers Checking-In Passengers on an
Overweight Flight..........................................68
Passengers with a Destination or
Residence Address
Checking in ..............................................85
Passport Information at Check-In Time ...........93
Error Responses........................................94
PA Input .....................................................93
PU Input.....................................................95
Use and Restrictions ...........................93, 95
Paxlist
UN..............................................................79
PCTC Parameter..............................................79
PDD
Input.........................................................142
Restrictions ..............................................142
PDD by Boarding Number................................56
PDD by Name ..................................................55
PDD by Passenger from different Station ........57
PDD by Seat Number.......................................56
PDD by Standby Number.................................56
Processing
Agent-In/Agent-Out Error Response ........... 7

Error Response ........................................... 5
Protected Workstation ....................................... 3
PS Input
Passenger Handling Displays ................... 97
PS Output
Passenger Handling Displays ................... 97
Pspt Remark
Deletion ..................................................... 96
PU
Input and Response ................................ 129
Seat Changes.......................................... 132
Use and Restrictions ............................... 129
PU Input
Passport Information at Check-In Time..... 95
PU Passenger Update ................................... 129
PW
Input......................................................... 133
Input/Response ....................................... 133
Passenger Delete.................................... 133
Use and Restrictions ............................... 133
PW Examples ................................................ 157
PW Input
PW Output
Query, Watchlist............................................. 116
Index
Page 188
Rechecking Passengers to a Different

Destination....................................................67
Stretcner Seats
Recline Seat
SUD ........................................................... 29
System Control and Security ............................. 3
SUD ...........................................................28
Reissue, Boarding Card .................................141
System Functions .............................................. 3
Residence or Destination addresses (DOCA) .79
Through Check-in ............................................ 70
SDD for Code share Flights .............................39
Electronic Ticket on One Flight and Paper

Ticket on Other Flight ................................ 71
Through Check-in - Electronic Ticket on two
Flights........................................................... 70
SDD for Overweight Flight ...............................41
Thru Check In
SDD with Zone Entry........................................38
Seat Codes.............................................. 128

Time Calculation .............................................. 14
SDD for an Overweight Flight that is Accepting

Passengers...................................................41
Search by Bagtag.............................................57
Seat Codes
Thru Check In ..........................................128
Seat Map ..........................................................27
Time Conversion.............................................. 14
Time Out Response ....................................... 135
Transit PAD...................................................... 49
Seat Map Display .....................................27, 143
Travel Document Information .......................... 80
Seat Map, Use .................................................31
Adding Infants ......................................... 83

Travel Document Information (DOCS)............. 79
Seat Map, Viewing ...........................................28

Seat Occupied by Transit Passenger
SUD ...........................................................29
Seat Requests, PA.........................................128
Seat Reserved by CRS
SUD ...........................................................29
SI
Agent-In/Agent-Out Error Response ...........7
Sign-In
Agent ...........................................................4
Sign-Out .............................................................8
Sign-Out Multiple Areas .....................................8
SITA DCS
Access .........................................................3
Special Usage Descriptors...............................28
Staff Priority Table..........................................169
Staff Priority Table Display.............................169
Standby ............................................................49
APP..........................................................107
Example.....................................................52
Standby Check-In...................................120, 140
Standby Display ...............................................49
Standby/Notification Display ............................49
UN Paxlist ........................................................ 79
UN Paxlist Error Responses ............................ 92
Unattached Baggage Check-In...................... 145
Unattached Bags
Check-in .................................................. 145
Delete ...................................................... 147
Display..................................................... 146
Under Check-In Weight Allowance .................. 34
Unprotected Workstation ................................... 3
Update Entry
Passenger ................................................. 67
Upgrade Passengers ....................................... 66
Cancel ....................................................... 67
Upgrade/Downgrade Checked-In Passengers 66
URES ............................................................. 141
URES Check in .............................................. 140
URES Check-In......................................120, 121
URES Passenger........................................... 141
URES/NOREC/ID Check in ........................... 140
USA Watchlist ................................................ 112
Boarding Process .................................... 116
Flight Close Out Process......................... 117
ITCI.......................................................... 115
Passenger Displays................................. 117

Index
Page 189
Passenger Updates .................................117

Use and Restrictions
Seat Map ................................................... 28

Watchlist Query.............................................. 116
Delete PSPT Remark ................................96

Passport Information at Check-In Time93, 95
User Grp
Watchlist, USA ............................................... 112

Using a Seat Map.............................................31
Viewing
Withdrawal
Passenger ................................................. 59
Workstation Information ..................................... 3
Zone Entry with SDD ....................................... 38

Index
Page 190

SITA Departure Control Services Check in Agent Guide - 7.2 - A4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SITA Departure Control Services Check in Agent Guide - 7.2 - A4

Uploaded by

Copyright:

Available Formats

Passenger Solutions

SITA Departure Control Services

Check In Agent User Guide

System Functions .......................................................................................................................... 3

Daily Flight List Display............................................................................................................... 17

Flight Information Displays and Updates ..................................................................................23

Seat Map Display.......................................................................................................................... 27

Passenger Survey Display .......................................................................................................... 33

6.3. SDD for Code share Flights .................................................................................................................. 39

Passenger Displays ..................................................................................................................... 43

Passenger Acceptance / Modification / Withdrawal .................................................................59

29 August 2008 Revision 7.2

8.2.10 Examples of Different Check-In (PA) Entries............................................................................. 71

Status Codes ....................................................................................................... 109

DFL Prohibited ..................................................................................................... 110

CREW Check-in................................................................................................... 110

8.2.22 AQQ ........................................................................................................................................ 110

SITA Departure Control Services Check In Agent Guide

8.2.22.2 Passenger cancellation: ............................................................................................ 111

SITA Departure Control Services Check In Agent Guide

29 August 2008 Revision 7.2

8.5.5.2 NOREC Check-In ...................................................................................................... 140

SITA Departure Control Services Check In Agent Guide

8.16. Passenger Delete (PW) ...................................................................................................................... 165

Staff Priority Table .....................................................................................................................169

10. Flight Destination / Remarks.....................................................................................................171

11. Flight Default Assignment and Display ...................................................................................173

12. Passenger Boarding Control ....................................................................................................175

13. Glossary ......................................................................................................................................179

SITA Departure Control Services Check In Agent Guide

29 August 2008 Revision 7.2

SITA Departure Control Services Check In Agent Guide

29 August 2008 Revision 7.2

Added DOCS, DOCA and DOCO Information at Check-In Time

Removed section on checking in passengers with passport

Section 7 Passenger Displays New Booked/Checked-In with

Section 8.4.2 URES Check-in, transaction for EXST with ETKT

Section 8.5.4.3 Example of E-Ticket passenger with EXST added.

SITA Departure Control Services Check In Agent Guide

SITA Departure Control Services Check In Agent Guide

29 August 2008 Revision 7.2

1.2. Course Objective

Understand the basic check-in entries and system responses.

Display or re-display any specific requested passenger lists.

Distinguish between NOREC and GO-SHOW passengers

Check-in standby passengers

Add staff ID and dates of joining

Issue boarding cards.

SITA Departure Control Services Check In Agent Guide

SITA Departure Control Services Check In Agent Guide

29 August 2008 Revision 7.2

Determine the level of authority on each agent entry.

Range from 11 to 144.

User group restrictions, if any.

Is the workstation restricted to one or more user groups?

City/office restrictions, if any.

Is the workstation restricted to only one city or multiple cities or all?

Dedicated use, if any.

User airline identity, only valid for multiple user CRTs.

SITA Departure Control Services Check In Agent Guide

User airline identity

Agent number. Verifies agent number is valid.