SITA Departure Control Check-In Agent Guide Rev. 12.0 PDF

Passenger Solutions
SITA Departure Control Services

Check-In Agent Guide
Revision:12.0
Revision Date:2015-August-31
Copyright © SITA Information Networking Computing USA Inc 2006 - 2015. Confidential. All Rights Reserved.
Copyright Notice
Copyright © SITA Information Networking Computing USA Inc 2006 – 2015
Confidential Information
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.
The SITA name, the SITA logo and the following marks are trademarks or registered
trademarks owned by the SITA group of companies around the world: SITA®, iBorders®,
Affinity®, iDetect®, AIRCOM®, iTravel®, iTravel Direct®, AirlineConnect®, Maestro®,
AirportConnect®, Runway®, AirportVision®, CUTE®, SITAPlus®, DesktopConnect®,
SITATEX®, FleetWatch®, Skyform®, Graflite®, WorldTracer®, Horizon®, SITA Create
Success. Together®.
Trademarks of SITA subsidiaries: OnAir®, Champ®.
Copyright © SITA Information Networking Computing USA Inc 2006 - 2015. Confidential. All Rights Reserved.
Table of Contents
1. Introduction 1
2. System Functions 3
Agent Control 3
Paging 10
Paging within Multi-Page Displays 11
Printing (PC/PT) 11
Encode/Decode (EX: / DX:) 12
SITA Help Facility 16
3. Check-in Flight List (CFL) Display 19
4. Flight Information Displays and Updates 29
Flight Data Display (FDD) 29
Mode of Update 31
5. Seat Map Display 33
Seat Map (SE) 33
Viewing the Seat Map 33
Aircraft Compartment Limits /Control Messages 37
Seat Map Use 37
6. Passenger Survey Display 39
Passenger Survey Display (SDD) 39
SDD with a Zone Entry 44
SDD for Code Share Flights 45
SDD for an Overweight Flight 46
7. Passenger Displays 47
Standby / Notification Display 54
Individual Passenger Record Display (PDD) 57
Search by Bag Tag 63
8. Passenger Acceptance: Check-in 65
Check-in Procedures 66
Gender Required Flights 68
Upgrade/Downgrade Passengers 70
Re-Checking Passengers to a Different Destination 71
Checking In Passengers with Double Oncarriage Segments 72
Oncarriage Check-in 73
Checking-in Passengers on a Connecting Flight 74
Through Check-In 74
SITA Departure Control Services Check-In Agent Guide

Table of Contents
Revision Date:2015-August-31, Revision 12.0
Copyright © SITA Information Networking Computing
USA Inc 2006 - 2015. Confidential. All Rights Reserved.
Page i
Marketing Carrier Check In Operating Carrier 75
Examples of Different Check-In (PA) Entries 82
Issuing Boarding Pass for Return Check-in Outside 72 Hours 89
Inputs to Issue Boarding Cards 89
Passenger Already in the PS List (Passenger List) 89
Outbound Information Added at the Time of Check-in 90
No Record Passenger Check-in 90
No Record Passenger Check-in - Error 91
Outbound Boarding Card (ORBP) Issuance Processing Rules 91
Summary of ORBP Option Inputs 91
Passenger Manifest Information 92
AUX Element SVC 93
Passenger Check In with PIL Remarks 94
Check-in Passenger with RPIL Remark 94
Add RPIL Remark to passenger record 94
Delete RPIL Remark 95
Generate PIL Message 95
Electronic Miscellaneous Documents (EMD) 96
DOCS, DOCA, and DOCO Information at Check-in Time 102
Passport Information at Check-in Time 118
Adding PSPT after Initial Check-in 120
PSPT DOB FOR WATCHLIST 122
Deletion of PSPT Remark 122
Passenger Handling Displays 124
PDD Display 124
Boarding Pass Inhibit for APIS Flights 125
Advanced Passenger Processing (APP) 129
Check-in 130
AQQ 139
Watchlist 142
Airline Undesirable Passenger List 145
ITCI 155
PDD Update 160
Group Check-in (GRP) 164
Standby Check-in (NOREC/URES/PAD) 167
Passenger Notification (NO) 172
9. Passenger Acceptance: Associated Handling Transactions 175
Extra Crew Check-In (XXXCREW) 175

Table of Contents
USA Inc. 2006 - 2015. Confidential. All Rights Reserved.
Page ii
Dead Head Crew Check-in 176
Unattached Baggage Check-in 176
Deleting / Changing Onward Connections 179
Boarding Pass Issuance / Inheritance (BC) 180
Boarding Pass Inhibit 181
Excess Baggage (EXB) 182
Bag Tag Issuance (B) 184
Passenger Update (PU) 191
Passenger Delete (PW) 194
10. Passenger Acceptance: ITCI Passenger Handling Procedures 197
Passenger Acceptance (PA) 197
Passenger Update (PU) 202
Passenger Delete (PW) 206
Standby Check-in (URES/NOREC/ID) 213
Interline Local Check-in (Onward Connection) 214
URES and NOREC Passengers 220
Passenger Record Display (PDD) 221
Seat Map Display Input / Response 223
ITCI Documentation Check 223
11. Electronic Ticket Check-In 231
12. Staff Priority Table Display (PZ) 233
13. Flight Destination / Remarks 235
Flight Remarks Display (RK) 235
Destination Remarks Display (DR) 235
14. Flight Default Display (FDT) 237
15. Passenger Boarding Control 239
Boarding Status Display (BSD) 239
Boarding Acceptance by Boarding Number (BAB/BDB) 240
Boarding Acceptance / Delete by Seat Number (BAS/BDS) 240
16. Glossary 243
17. Index 249

Table of Contents
Page iii
Table of Contents
USA Inc. 2006 - 2015. Confidential. All Rights Reserved.
Page iv
Revision History
Revision Date Changes
6.0 1 Jun 2006 Added:
n Crew Screen to Section 23.
n ACARS section 7.5.
n ACARS to FJ section 15.3.
n documentation changes in Section 5 for software
revisions.
n Index.
6.1 5 Jun 2007 Re-branded.
7.0 29 Jun 2007 Customer Release.
7.1 29 Aug 2008 Section 4 List of Active Flights revised, other options added.
7.2 31 Dec 2008 n Update to Stretcher Passenger section: update to general

procedures to handle a stretcher passenger in DCS.
n Added Stretcher Information - (PAX7) section.
7.3 31-Dec-2008 Update to Passenger Update (PU) section.
8.0 30-Apr-2009 n Revised Section 1.2 to clarify the objective of the guide.
n Added Passenger Status Change into Section 8.2.9.11
and revised Sections 8.2.30.1 and 8.2.31.6.
8.1 23-Nov-2009 Updated:

n Gender Required Flights
n Special Service / Information Codes
8.2 31-Aug-2010 Added Printing of Selectee Boarding Pass and PDD Update.
9.0 15-Mar-2011 Separated Section 8 - Passenger Acceptance / Modification /

Withdrawal into 3 sections:
n Section 8: Passenger Acceptance: Check-in
n Section 9: Passenger Acceptance: Associated Handling
Transactions
n Section 10: Passenger Acceptance: ITCI Passenger
Handling Procedures
n Renumbered remaining sections.
Added Interline Local Check-in (Onward Connection) to

Passenger Acceptance: ITCI Passenger Handling
Procedures section.
10.0 29-Feb-2012 Updated first paragraph under: Boarding Pass Inhibit for APIS
Flights.

Revision History
Revision Date: 2015-August-31, Revision 12.0
Page v
Revision Date Changes
Added new section in Chapter 8: Marketing Carrier Check In
Operating Carrier.
Added section to Chapter 8:for Airline Undesirable Passenger
List.
Added Section 11: Electronic Ticket Check In.
10.1 2012-Jun-29 Passenger Acceptance (PA) section: Added SSR codes to

this section: WCBL, SVAN, ESAN.
10.2 2012-Oct-31 Added: Electronic Miscellaneous Documents section.
11.0 2013-Apr-30 Added additional information to Electronic Miscellaneous

Documents section.
11.1 2013-Dec-31 n Added new display options for display Passenger

Booked/Checked-In (PS) for Bag, ITCI Inbound and
Outbound, Agent, Boarding Number, Seat and First
Name/Last Name
n Added Remarks to PIL message
n Added ITCI Secure Flight Documentation Check error
messages explanations
n Added bag tag printed with final destination if parameter is
set
11.2 2014-May-30 n Added EMD ASVC/SVC remark to be included on PIL, JL,

PS and Boarding Pass for Merchandising mini-release 1.1
per CCR658.
n Added Korean Immigration Service APP capability
12.0 2015-August-31 n Added Merchandising 2.2 changes to ADL processing for

EMD.

Revision History
Revision Date: 2015-August-31, Revision 12.0
Page vi
1. Introduction
This guide covers all the main SITA Departure Control Services (SDCS) check-in entries
required for a check-in agent to carry out their normal duties. For more advanced and control
transactions, refer to the SITA Departure Control Services Check-in Supervisor Guide.
The guide offers the following primary objectives so each staff member can:
n Understand the basic check-in agent entries and system responses.
n Display or re-display any specific requested passenger lists.
n Distinguish between NOREC and GO-SHOW passengers.
n Add any special passenger information to a passenger's record either before, during, or
after check-in.
n Check-in standby passengers.
n Add staff ID and dates of joining.
n Issue boarding cards.
n 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.

1. Introduction
Page 1
1. Introduction
USA Inc 2006 - 2015. Confidential. All Rights
Reserved.
Page 2
2. System Functions
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:
n Determine the level of authority on each agent entry.
n Permit you to perform additional duties and is included as part of your sign-in entry.
n Range from 11 to 144.
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:
n User group restrictions, if any.
n Is the workstation restricted to one or more user groups?
n City/office restrictions, if any.
n Is the workstation restricted to only one city or multiple cities or all?
n Dedicated use, if any.
n Is the workstation set up for a specific application only, for example, Ticketing?
n User airline identity, only valid for multiple user CRTs.

2. System Functions
Page 3
Agent Information
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:
n User airline identity.
n Agent number. Verifies agent number is valid.
n Personal Account Number (Security Code). Validates account number against agent
number.
n User Group(s). Determines the transactions that are valid for the agent.
n City/office restriction. Validates multiple city access.
Agent Sign-In
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:

124 The 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.
ATL501 Optional. 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.

2. System Functions
Reserved.
Page 4
Entry:
SI:44/25678A/124/ATL501
Entry Description
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.

2. System Functions
Page 5
Error and Rejection Responses:
Response Description
PROT SET CRT is "Protected". A sign in entry must include a Personal Account
Number.
CUSTOMER Sign in entry/Customer Number in your agent file does not match the
NUMBER 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.
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.

2. System Functions
Reserved.
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
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.
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

2. System Functions
Page 7
Response:
ATL501 44 signed out B
If multiple areas of the CRT are signed in the response is:
XS ATL501 44 SIGNED OUT B

A 44 1347 124 ATL501
C 44 1737 129 ATL501
ATL501 City/Office.
44 Agent Number.
A Area signed out.
44 Agent Number.
1602 Time of sign in (GMT).
124 User Group.
ATL501 City/Office.
Note: To sign out all areas with a single entry, enter XO.
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

2. System Functions
Reserved.
Page 8
Response:
A AVAIL
B* 44 1222 124 ATL501
C AVAIL
D 106 1230 130 ATL501
E 44 1223 124 ATL501
PID = 735 HARDCOPY = 136
SYSTEM ON-LINE
Explanation of the Response:

Note: B* below, Indicates that the Agent is working in B.
A, B*, C, D, E Agent Work Areas - Areas B, D, E Controls Computer A and C are

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

2. System Functions
Page 9
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 Displays from the first line of the paged response to the
Page 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 Displays the lines previous to the current display to the
Page (Previous) 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 Displays lines following current display to the limits of
Page 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
PG:+5 PG:-10
the limits of lines available on the screen or start of the
paged response.
CP: Clear Page Clears the displays and associated page storage.

2. System Functions
Reserved.
Page 10
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.
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 Definition Description
PC: Print Current Prints the Page currently displayed.
PT: Print Total Prints all pages at the level of the information
currently displayed.

2. System Functions
Page 11
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:
n Cities
n Airports
n Airlines
n Countries
n 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.
Notes:
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.
Encode Entry (EX:)

1. Entry: Encode the "Airline" Air Europa (this entry converts an airline name to
code).EX:A/AIREUROPA
EX:A/AIREUROPA

2. System Functions
Reserved.
Page 12
Response:
EX:A/AIREUROPA
UX * AIR EUROPA LINEAS AEREAS,S.A
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
three-letter code with GMT details).
EX:CF/MADRID
Response:

.ES 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).
Decode Transaction (DX:)

1. Entry: Decode the 'Airline' code UX (this entry decodes an airline's two letter code).
Enter:
DX: A/UX

2. System Functions
Page 13
Response:
DX:A/UX
The asterisk (*) indicates Air Europa shares the operation of some flights.
To see what carriers share operations with UX enter the following entry.
2. Entry:
DX:AF/UX
(This entry shows code share agreement flights.)

Response:
►DX:AF/UX
* 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 3024 CDG 15MAR06-25MAR06 X7 AF 5578 - AIR FRANCE
UX 3024 CDG 27MAR06-28OCT06 X7 AF - AIR FRANCE
UX 3036 AF 1476 - 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

2. System Functions
Reserved.
Page 14
Response:
►DX:C/MAD
Entry: Decode the "City" code MOW with "full" details.
►DX:CF/MAD
Response:
►DX:CF/MAD
.ES GMT +01.0 DST EFF 0200 26MAR06-29OCT06 0200 DGMT +02.0
0200 25MAR07-28OCT07 0200
END
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 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 ADD.... 1735/23DEC GMT +03.0
+01.0 HOURS DIFFERENCE DISTANCE 1623 M 2612 K

2. System Functions
Page 15
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 LLW.... 0100/24DEC GMT +02.0
+07.0 HOURS DIFFERENCE DISTANCE 8354 M 13445 K
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

22 May 00
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:
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.

2. System Functions
Reserved.
Page 16
Response of Second Page

22 May 00
Entry:
FDD:HA700/05AUG
Explanation of The Entry:

FDD: = (M) Function Code
HA700 = (M) Airline/Flight Number
05AUG = (M) Date
** END **
2: Entry:
PA?
Response:

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.

2. System Functions
Page 17
2. System Functions
Reserved.
Page 18
3. Check-in Flight List (CFL) Display
The Check-in Flight List (CFL) transaction allows an agent to display a list of flights departing,
arriving, or transiting a specific airport. It can also display all flights operating over a specific
flight segment on a given date.
Entry:
CFL:AIRLINE/DATE/AIRPORT(SPECIFIC SEGMENTS)/OPTION
A space can be substituted for a slash as a field separator throughout the CFL input.
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
L Flights linked to reservations.
S All available SEGMENT information and determines the format of the display.
O All OPEN flights.
C All CLOSED flights.
I All Initialized flights.

Page 19
Option Description
T All training flights.
X All Uninitialized flights.
A All Arriving flights.
D All Departing flights.
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.
Entry:
CFL:AIRLINE/CITY/ OPTION
CFL:ALL/OPTION
CFL:XS/MIA/I
CFL:ALL/CN
Option Description
CN All canceled 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.

Reserved.
Page 20
Option Description
NC All non-canceled flights.
NT All non-training flights.
CL All flights Closed for Load Planning.
DI All flights with Deferred initialization.
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 example, cannot request C with O or I with
N.

Page 21
CFL
Response to CFL:O (List of all flights open for check-in)
FLIGHT RECORD LISTINGS: XS ** SITA AIRLINE************************

04JUN
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
Response to CFL:C (List of all Closed flights)
►CFL:C
FLIGHT RECORD LISTINGS: XS ** SITA
********************************* 08OCT
XS090 XS091
XS200 XS215
XS340 XS452 XS486
Response to CFL:airline/CN (List for all cancelled flights needs airline or ALL)
CFL:XS/CN
XS090
XS200
XS340

Reserved.
Page 22
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 TYPE
AAA 0700 0630 CC 67 23 C10M43 737/A NAM
ALP 0910
AAA 0700 0630 CC 45 27 C8M43 734/A NAM
FRA 0915
XS778 ARRIVES DEPARTS BOARDS STAT POS GATE BKD EQUIP TYPE
AAA 0700 0630 OPEN GATE ???? C0Y50 340/B NAM
ATL 0900 1020 0940 OPEN GATE ???? C0Y145 340/A NAM
SJU 1310
AAA 0730 0700 CC 74 28 C4M18 CRJ/CRJI NAM
DOH 0900
AAA 0730 0700 CC 78 21 C2M12 734/AGD NAM
MUC 0850
AAA 1130 1100 NINT GATE ???? 762/A NAM
JFK 2125
+
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.
CFL:S Display
XS5100 ARRIVES DEPARTS BOARDS STAT POS GATES BKD EQUIP

TYPE
ATL P 0010 2340 NINT GATE B17 F06Y168 767/A
NAM
JFK P 0300
1 2 3 4 5 6 7 8 9 10 11

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

n OPEN Flight is open for passenger check-in.
n LOCKFlight is under emergency lock.
n HOLD Flight out of the airport is on hold.
n CICheck-in initially closed for flight.
n CCCheck-in finally closed for flight.
n CANCAirport is cancelled for this flight.
n RSOM SOM has been requested but not received.
n TCL Airport is technical landing only.
n PNLR PNL has been requested but not received.
n NINT Flight has not yet been initialized for check-in.
7 Aircraft ramp/apron position at this airport.
8 Passenger boarding gate number at this airport.
9 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:
n NAMPassenger name check-in from a PNL.
n NUMNumeric check-in.
n PNMPartial name check-in for passengers with special requests only.
n NONNon SITA DCS check-in. (Manual check-in)
n TCLTechnical landing, no check-in allowed.
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 25
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 Correct
EQUIP TYPE EQUIP TYPE
TU5/C3 NAM TU5/C3 NAM
TU5/C3 NAM TU5/C3 NON
TU5/C3 NAM TU5/C3 NON
CFL:O/S (All Open Flights with Segment Information).
FLIGHT RECORD LISTINGS: XS ** XS ************************ 04JUN

N 2100 2030 NINT GATE ???? 737/73S NAM
ATL 2130 2220 2150 NINT GATE ???? 737/73S NAM
JFK 2355
ATL 2300 2230 NINT GATE ???? 737/DF NAM
MIA 2330
XATL 2300 2230 OPEN GATE ???? DH8/C NAM
XMIA 2330
XS718 ARRIVES DEPARTS BOARDS STAT POS GATE BKD EQUIP
TYPE
ATL 2300 2230 NINT GATE ???? DH8/C NAM
MIA 2330
TYPE
DCA 2330
TYPE
MIA 2350
TYPE
MIA 2315 2330 2300 NINT GATE ???? DH8/C NAM
+

Reserved.
Page 26
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.
'**NO SEGMENT INFO**' Response with CFL:S Entry
FLIGHT RECORD LISTINGS: XS ** SITA

********************************* 14OCT
* XS206 ** NO SEGMENT INFO **
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 00XXX00 D
->> ACTIVE DATES:
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.
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.

Page 27
Reason Response Preventing Flight Activation with Seat Map Display.
SE206/.
129 - AIRCRAFT

Reserved.
Page 28
4. Flight Information Displays and Updates
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:
n Routing
n Departure and arrival times (in local time) (T)
n CND table number (for configuration)
n Aircraft type and version
Master Flight (FDD:XS587/15MAR)
XS587 11FEB05 - 23MAR05 156 --MASTER--

ATL 1410 T-32 737/A
JFK 1635
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.

Page 29
Active Flight (FDD:XS587/.)
XS587 14FEB06 --ACTIVE--
ATL ADJ 1510 1/00 LATE T-32 737/A R:G-
LMWP
JFK ETA 1735 1/00 LATE
IRREGULAR OPERATION DETAILS

ATL SURFACE WINDS
SUPPLEMENTAL INFORMATION
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 Location and reason for schedule adjustment. Use the FIR transaction
OPERATION to enter the delay codes.
DETAILS
A Supervisor or Operations Agent will update the FDD information.
SUPPLEMENTAL Detailed reason for a delay or details on the protection of passengers off
INFORMATION a canceled or delayed fight. Entered via FIR transaction.

Reserved.
Page 30
Active Code share Flight (FDD:XS130/.)
►FDD:600/.
***CODE SHARE***SN5144
FDDMA 600 /05APR06
MA 600 05APR06 X67 --ACTIVE--
BUD 0625 20 71 T-518
73G/73GBBR:HALOR
BRU 0825
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.
Mode of Update
The Flight Data Display is updated from the following entries:
n Flight Update Information (FUI:).
n Flight Irregular Operations (FIR:)
n Movement Message (MVT) entered with the LMVD: transaction.

Page 31
Reserved.
Page 32
5. Seat Map Display
Seat Map (SE)
Any agent can display the seat map for a seat assignment flight.
Entries:
SE:FLIGHT NUMBER / DATE
SE:FLIGHT NUMBER CLASS
SE:FLIGHT /SEGMENT
SE:FLIGHT NUMBER/DATE CLASS SEGMENT
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 [ [
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
RF T * F F . * T * * P * T * . . . * * / FR
RE T * E E . * * * L * P * T * * . * * * / ER
RD * V D D . * T * L * * * * * . * * * * / DR
R = S = = = = = = = = = = S S S S S S R
L : S = = = = = = = = = = S S S S S S L
LC . * C C H * * * L * * * * * . * * . R / CL
LB + * B B R * T * L * * * . * * * * R R / BL
LA . V A A R * T * * * P . T T . * R * / AL
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
F Y [ [ [ [ 1 [ [
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.
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.

5. Seat Map Display
Page 33
Code Definition
R RIGHT side of aircraft.
FY Classes of service
L 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.
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.
S SMOKING row.
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.
A Allotted seat available for check-in this segment.
B Available bassinet seat for Infant.
C Last to be used available seat.
D Handicap seat.
E Emergency exit seat.
G Seats reserved for group by RS transaction.
H Available Bulkhead seat.

5. Seat Map Display
Reserved.
Page 34
SUD Description
I Infant seat.
K Stretcher seats (Designated on EQC: but only appears if .R/STCR is

on PNL).
L Available Extra Leg room seats.
N Available Restricted Film view seat.
O Allotted seat not available for check-in this segment.
P Seat reserved by CRS (check-in editing) for passengers not checked-

in.
R Seat automatically reserved for passenger by RES from PNL or ASR

on ADL after flight initialization.
T 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).
U Available seats for Unaccompanied Minor.
V Seat automatically reserved for passenger by ASR from PNL.
X Blocked seat (unusable).
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.
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.
Code Description
RS Smoking seat
RN Non Smoking seat
RW Window seat
RSW Smoking Window seat

5. Seat Map Display
Page 35
Code Description
REW Emergency Exit Window seat
RI Aisle seat
RSI Smoking Aisle seat
RF Forward seat
RA Aft seat
Passenger Acceptance (PA) Check-In entries are in the Passenger Acceptance (PA) Check-
In sub-section.
Seat map on a code share flight SE:XS130/.
SE:XS130/.
***CODE SHARE***YY029
SE:XS130/30SEP06/ ATLJFK
320/R
C M 1 1 2
123456 7890124567890123456
RF ****** F F ***EE************** FR
RE ****** E E ***EE************** ER
RD ****** D D ***EE************** DR
R =====S ================SSS R
L =====S ================SSS L
LC ****** C C ***EE************** CL
LB ****** B B ***EE************** BL
LA ****** A A ***EE************** AL
123456 7890124567890123456
C M 1 1 2
***CODE Indicates marketing partner and marketing flight numbers code sharing
SHARE***YY029 with the operating flight.
Notes:
Code share flights can accept up to nine marketing partners between SDCS users and
partners.
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.

5. Seat Map Display
Reserved.
Page 36
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 flight’s 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 the Standby Example Descriptions.
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.
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.

5. Seat Map Display
Page 37
5. Seat Map Display
Reserved.
Page 38
6. Passenger Survey Display
Passenger Survey Display (SDD)
Any authorized agent can display the SDD screen, which gives relevant information such as:
n schedule departure time
n aircraft type
n gate number
n boarding time
n passenger configuration
n capacity
n 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.
Entry:
SDD:FLIGHT NUMBER/DATE
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

Page 39
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.
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:

n NUMFlight is Numeric check-in (no PNL).
n PNMFlight Partial Name check-in (same as numeric except
passengers with special requirements displayed in system).
n NONNon-Automated station for SITA DCS.

Reserved.
Page 40
Row 2:
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).
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:
737/A Aircraft type and version.
GTD Passenger gate number.
POS Ramp position that is used for 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 41
Row 4:
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:
ATL/MIA Flight segment.
R 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
canceled on the flight.
C Checked-in passengers.
B 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.
I Number of infants checked-in on flight.

Reserved.
Page 42
Row 7:
SB Number of standbys on the flight.
B 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.
J Accepted cabin jump seat passengers.
Row 8:
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:
SIX Seating restriction.
Row 11:
HL Numeric limit by class for passenger acceptance, and only displays

when set.

Page 43
Row 12:
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.
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.
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 STCR00 PETC00 AVIH00 J00
SA0000/0000/0000 EXST00/00/00 XCR00/00/00
DHC00/00/00
*TEST FLIGHT ONLY*
. GS ID
ATL 000/000/000 000/000/000

Reserved.
Page 44
SDD for Code Share Flights
The following is an example of an SDD involving an operating carrier with multiple code share
partners:
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
SA0000/0000 EXST01/00 XCR00/00 DHC00/00
GS ID
ATL 000/000/000 000/000/000
Explanation:
Field Description
***CODESHARE Indicates marketing partners and marketing flight numbers code sharing
****YY9084 with the operating flight.
ZZ2684 BB9984
JFK C004 M000 Indicates the destination city followed by the number of marketing
passengers checked-in for each class.
The SDD can also be displayed for a marketing carrier only.

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
SA0000/0000 EXST01/00 XCR00/00 DHC00/00
GS ID
ATL 000/000/000 000/000/000

Page 45
Field Description
***CODE SHARE**** Indicates the marketing partner of a Code share flight XS084.
ZZ2684
ATL C001 M000 Indicates the boarding city and the number of passengers checked-in on
marketing flight ZZ2684.
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
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:
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
SA0000/0000 EXST00/00 XCR00/00 DHC00/00
GS ID
ATL 000/074 000/000
Notes:
Overweight parameters are controlled by the ATL Customer Support and should be
contacted when needed.
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.
The flight entry may be the marketing flight, but the system displays the operating flight
information.

Reserved.
Page 46
7. Passenger Displays
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.
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.

Page 47
Field Explanation
1 Passenger entry display number.
2 Number of family passengers with this surname.
3 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).
4 PNR party connector code.
5 Passenger boarding (BN) or standby (SB) number.
6 Seat number.
7 Class of booking.
8 Destination.
9 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.
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.

Reserved.
Page 48
Code Description
AEC Unseated Passengers Due Aircraft Change.
AECX New Seat Passengers Due Aircraft Change.
AGT Displays checked in passengers by Check In Agent. Can alos include

Agent Number in request (example AGT1105).
ASR Advance Seat Reservation.
AVIH Live Animal in Hold.
BAG Lists Number of Bags, and Bag Tag Numbers, for Each Passenger.
BLND Blind Passenger.
BRDN Displays passengers with Boarding Numbers in ascending order.
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.

Page 49
Code Description
INF Infants + Any Bassinets.
ITCI Initial check-in via Interline Thru Check-In.
I,ITCI Displays connections with inbound details, including Bag Tag numbers.
O,ITCI Displays connections with outbound details, including Bat Tag

nunmbers.
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).
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.
PAID Paid Seat.
PCTC Passenger Contact Information.

Reserved.
Page 50
Code Description
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.
SEAT Lists passengers in ascending seat number order.
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.

Page 51
Code Description
Z Passengers Rechecked from Another Flight.
N N Placed before any Other Item Except I, O, Z gives a List Excluding

that Particular Item.
NACC List of Not Accepted Passengers.
@Y List of Passengers by Aircraft Compartment. @Y must be the first item

(COMPARTMENT) and should not be preceded by a comma (,).
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.
Any agent can display the booked/checked-in display by passenger Last and First Name.
Enter:
PS:FLIGHT/DATE CITY,1LAST NAME/FIRST NAME
An Agent can display the booked/checked-in dispaly by multiple passenger Last and First
Names by separating each name with a ";".
Enter:
PS:FLIGHT/DATE CITY,1LAST NAME/FIRST NAME;1LAST NAME/FIRST NAME

Reserved.
Page 52
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.
PD:XS493/+,PAID All Passengers with Paid Seats.
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; All Passengers by the Name of Ward and Gill.

NAMGILL

Page 53
Standby / Notification Display
Standby Display (SB)
Any agent can display the standby or passenger notification list.
Entry:
SB:FLIGHT NUMBER / DATE
SB:XS735/.
This list can consist of the following categories of passengers:
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.
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.
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.

Reserved.
Page 54
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

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 PAD M MIA P20 IDS2/MAY71
6. 3FERGUSON/SMR K3 SB035 PAD M MIA P50 IDN2/APR79
FERGUSON/YMRS K3 SB036 PAD M MIA P50 IDN2/APR79
FERGUSON/LMIS+K3 SB037 PAD M MIA P50 IDN2/APR79
7. 1BOOTH/AMR SB019 LMTS M MIA P90 IDR2/SEP85
1. 2. 3. 4. 5. 6. 7. 8. 9.
Explanation:
Field Description
1 Passenger entry display number.
2 Number of family passengers with this surname.
3 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).
4 PNR party connector code.
5 Passenger Boarding (BN) or Standby (SB) Number.
6 Seat Number or special designator. Possible designators are:

n AECAutomatically disembarked due to aircraft change.
n CAPAircraft capacity restriction.
n DEBDisembarked passenger.
n HOFlight on hold.
n LMLimit restrictions due to manual/automatic numeric limits or space
protection limits.
n NAVNo live animals allowed or restricted limit reached.
n OFECDisembarked manually using the JAC transaction during an equipment

Page 55
Field Description
(AEC) change.
n OFLOffloaded passenger by AC transaction with X option (to prevent
automatic re-acceptance).
n PADPAD capacity restriction.
n PETCAnimal in cabin restriction.
n STLSeating limitations (check seat map for available seats).
n LMTSNo GO-SHOW or ID figures set.
n WTLWeight limitations (Check with Load Planning).
7 Class of check-in.
8 Destination.
9 It is possible to display information from the following sections, Response to

Standby Description
(Section Response to Standby Description) and Need Notification Example
Descriptions
(Need Notification Example Descriptions).
Need Notification
Example Explanation
ACC/SIB 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.
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.
Z Passenger rechecked by bulk recheck transaction (BR/BRC/BRN) and

passenger not accepted on new flight.

Reserved.
Page 56
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.
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:
n Special Services the passenger has requested.
n Pre-assigned Seats, Boarding Numbers, Allocated Seats, or Standby Numbers.
n Time of passenger check-in and record of Agent/CRT that entered the initial transaction.
n 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
Entries:
To display a PS List: PS:XS735
Response:
PS: XS735/08JUNATL OP/NAM

1. 2ABOTT/LMR A2 SN17E M MIA INF PSM RES
ABOTT/GMRS A2 SN17F M MIA RES
2. 1ADAM/GMST+ BN002 SN2A C MIA UM RES
3. 2ALLEN/TMR B2 M MIA
ALLEN/LMRS B2 M MIA
4. BOLTON/JMR SB1014 LMTS M MIA URES
To display the PDD record of passenger Adam: PDD:2

Response:

Page 57
PDD: XS735/08JUNCATL,2
1. ADAM/GMSTR BN002 SN1C C MIA BAG1/12/0 UM10
RES AUTO 07JUN1146
ACC VDT7917 AGT937/08JUN0823
PU VDT2856 AGT286/08JUN0910/BAG
To display a SB list: SB:XS735

Response:
SB: XS735/09JUN ATL OP/NAM

737/106C GTD/???? POS/GATE BDT1930 SD2000 ED2000 SA2005 FT2005
AV C12M98 PAD C0M0
STANDBY
1. 1BRANDON/JMR SB1014 LMTS Y MIA P3 URES
Display a PDD of standby passenger Brandon: PDD:1

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

Reserved.
Page 58
PDD for a Code share Passenger
PDD:1
***CODE SHARE***YY141
PDD: XS040/01OCTYJFK,01
1. BRITT/JAMES BN002 SN17C Y LHR M1/75
LFML-
MKT/YY141/01OCT M LHR
ACC VDT2110 AGT877/01OCT1216
PU VDT2110 AGT877/01OCT1324/LFML
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
PDD with Double Oncarriage Segment:
PDD:1
PDD: LG112/04NOVYMUC,01
1. ADAMS/L MR Y LUX M1/75
DP/LG113/04NOV Y FRA
DP/LG061/04NOV Y FRA
Note: DP indicates the passenger is double-booked on a segment.
PDD with Passengers with a Paid Seat:
PDD:1
PDD: MH111/20DECYKUL,5 PNR RL K890P
1. ONE/TWO MR SN25C Y LHR ASR ASVC PAID
ASVC- G/0B5/NSST/CHARGEABLE SEAT/2324560082275C1
Note: PAID indicates the passenger has a paid seat.
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:

Page 59
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.
ASVC Additional Service
***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 passenger’s 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.
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).

Reserved.
Page 60
Code Explanation
X 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.
Z 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.
The PDD entry can be displayed by Passenger Name, Seat Number, Boarding Number, or
Standby Number.
1. PDD by Name
Entry:
PDD:FLIGHT NUMBER CLASS, NBR NAME
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).

Page 61
2. PDD by Seat Number
Entry:
PDD:FLIGHT NUMBER, SEAT NUMBER
PDD:XS735,SN17A
3. PDD by Boarding Number
Entry:
PDD:FLIGHT NUMBER, BOARDING NUMBER
PDD:XS735,BN114
4. PDD by Standby Number
Entry:
PDD:STANDBY NUMBER
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 re-entering the PS or SB list providing the entry number is known.
Entry:
PDD:ENTRY NUMBER PS
PDD:12PS
Entry:
PDD:ENTRY NUMBER SB
PDD:5SB
5. PDD by Ticket Number
PDD:FLT/DATE,TKNE/1234567890123C3
6. PDD by Frequent Travel Number
PDD:FLT/DATE,FQTV/123456789

Reserved.
Page 62
7. 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).
8. PDD Display for a Passenger from another Station
PDD:FLIGHT/.STN,BN NUMBER
PDD:FLIGHT/.STN,SN NUMBER
PDD:FLIGHT/.STN,1PAX NAME
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’.
PDD:XS100, BT XS123456
PDD:XS100,0950123456
Response to PDD:XS100,BT XS123456
PDD:XS100/08JAN ATL,BTXS123456
1. HUNT/JAMES MR BN008 SN11G C MIA BAG/9/0
BAGTAGS ISSUED: ATL 1/9
0950123456/MIA
ACC VDT8267 AGT66/08JAN1414
Note: If exactly ten numbers are not entered or the bag tag number cannot be found, the
system responds “020-PSGR ID”.

Page 63
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.
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 BAG 1/10
0950123456+/MIA
ACC VDT72846 AGT91/08JAN192

Reserved.
Page 64
8. Passenger Acceptance: Check-in
The transactions that allow staff to check-in individual, group, or stand-by passengers are
described in this section. Other passenger acceptance information is contained in the
following sections:
Description Section
Passenger acceptance Passenger Acceptance: Check-in
Passenger or item update Passenger Acceptance: Associated Passenger Handling
Passenger or item withdrawal or Passenger Acceptance: Associated Passenger Handling

delete
Interline Thru Check-in ITCI Passenger Handling Procedures
Note: Associated passenger handling includes baggage, bag tags, boarding passes, excess
baggage, modification, and withdrawal.
There are three basic types of automated check-in options:
1. 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).
2. 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).
3. 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 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 Bag Tag Issuance (B) sub-
section.

Page 65
Check-in Procedures
There are two main ways to check-in a passenger:
n From a Previous PS List Display
or
n Detailed Entry
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).
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
OP/NAM
1. 1CHARLES/JOHN D2 C JFK
2. 1COLLIE/TMR C JFK
3. 1COOPER/LMR C JFK
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

Reserved.
Page 66
Response to PA 1.11/2
PA:XS593/08JUNCJFK1COOPER/LMR,1/12
AV C12M54 PAD C0M2
737/106C GTD/B24 POS/GATE BTD/0930 SD1000 ED1000 SA1105
FT0105
1. COOPER/LMR BN019 SN07A *JFK*
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:
n Excess baggage charges are applied, the response displays the amount of excess bag
charges to be assessed with the comment 'BOARDING PASS PRINT INHIBITED'.
n 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.
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.
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
1. COOPER/LMR BN019 SN07A *JFK*
Check-in for a single sector flight that does not require gender
PA:XS772 Y 1MACKAY/JMR,1/15,B
Response:

Page 67
PA:XS772/08JUNCMIA1MACKAY/JMR,M1,1/15,B
AV Y075 PAD Y2
727/A GTD/B24 POS/GATE BTD/1330 SD1400 ED1300 SA1405 FT0105
1. MACKAY/JR BN035 SN26C
Passenger is now checked-in and the boarding card is issued.
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)
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
PSL.Servicedesk@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.

Reserved.
Page 68
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 M Followed by the number (M1 or M2 etc.)
FEMALE F 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.
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 M JFK
3. 2FLETCHER/JMR D2 C JFK
FLETCHER/FMRS D2 C JFK
4. 1FLETCHER/PETER BN023 SN22D M JFK
In this case if the passenger is identified as entry number 2, enter:
PA:2

Page 69
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.
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.
Pre-Upgrade / Pre-Downgrade
Entry:
To pre-upgrade to F class: PU:#ENTRY NBR,PUPG F/V
PU:#1,PUPGF/V
Entry:
To pre-downgrade to Y class: PU:#ENTRY NBR,PDNGY/I
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.
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.

Reserved.
Page 70
Entry:
To downgrade a checked-in passenger to Y class: PU:ENTRY NBR,DNGY/V
PU:1,DNGY/V
Entry:
To upgrade a checked-in passenger to F class: PU:ENTRY NBR,UPGF/I
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'.
Cancel Pre-Upgrade/Downgrade
Entry:
To cancel a pre-upgrade is: PW:#ENTRY NBR,PUPG
PW:#1,PUPG
Entry:
To cancel a pre-downgrade is: PW:#ENTRY NBR,PDNG
PW:#1,PDNG
Notes:
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).
Passenger upgrade and downgrade limits are subject to the standby limits for check-in.
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

Page 71
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.
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.
Passenger Adams is checking in with double oncarriage segments. His PDD appears as
follows:
PDD with double oncarriage segments:
PDD:1
PDD: XS112/04NOVYJFK,1
1. ADAMS/L MR Y JFK M1/75
DP/XS113/04NOV Y LHR
DP/XS061/04NOV Y LHR
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

Reserved.
Page 72
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
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
Response to PA1,1/10 on an Overweight Flight:
PA: XS101/06NOVYJFK65ps,2/20,B
*** FLIGHT IS OVERWEIGHT ***
AV C54Y69 PAD C0Y0
757/200 GTD/???? POS/GATE BDT2230 SD2300 ED2300 SA2330 FT0030
1. XRAY/B BN105 SN39C PSM
Note: Overweight parameters are controlled by the ATL Customer Support group and they
should be contacted when needed.
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.

Page 73
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.
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.
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.
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.
Through Check-In
The following types of Through Check In are available:
n Through Check-in involving Electronic Ticket on two Flights
n Through Check-In involving Electronic Ticket on one flight and paper ticket on the other
flight
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.

Reserved.
Page 74
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.
Through Check-in – Electronic Ticket and Paper Ticket

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 e-ticket 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. 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”.
Marketing Carrier Check In Operating Carrier

When checking in a passenger with an online connection to a host marketed code share
operating flight, a new user parameter of TCIF determines if an ITCI request is sent to the
operating carrier.
This parameter determines whether to send an ITCI request to the operating carrier when
checking in a passenger connecting to the host marketed code share flight. Values are:
n 0 = Do Not send ITCI request to operating carrier (default)
n 1 = Send ITCI request to operating carrier
This is not a restricted user parameter.
Check In
When checking in a passenger with an onward online connection (host flight number), SITA
DCS checks the user parameter TCIF to determine if an ITCI request should be sent to the
operating carrier. If the parameter is set to 1, SITA DCS checks the Shared Airline
Information (the A9 Table in RES) to determine if it is a code share and retrieve the operating
carrier and flight number. If it is code-share and the host has an ITCI agreement with the
operating carrier, SITA DCS will send an ITCI request to check in the passenger to the flight.
The following steps apply when the connection is an online flight:
n When an attempt to check-in a passenger is for an online host connecting flight, SITA DCS
checks the value in the TCIF parameter. If TCIF is 0, the existing process continues and no

Page 75
further checks are performed. In other words, the passenger is checked in for the online
marketing connecting flight and no ITCI request is sent to the operating carrier.
n If TCIF is 1, SITA DCS checks the Shared Airline Information table to determine if the
onward online flight is a code share marketing flight. If it is not a code share marketing
flight, then the passenger is checked in for the online connecting flight.
n If this is a code share marketing flight, SITA DCS checks the ITCI Agreement table to
determine if there is a bilateral agreement with the operating carrier. If there is an ITCI
bilateral agreement, SITA DCS sends the operating carrier an ITCI request with the
operating carrier and flight number in the request. If there is no agreement, then the
passenger is not checked in for the online marketing connecting flight.
n If there are additional connecting flights, the Bilateral Agreement table is validated for each
to determine if it is permitted to allow for cascading ITCI requests.
Examples
Various Ways an Onward Connection Is Specified at Check-in Time:
The steps above apply to all of these:
Onward flight in passenger record
Onward flight added at check-in
PA:1,OAI5678/24AUGDEN
No record (NOREC) check-in with onward connection
PA:AI1234/23AUGYLAX1LASTNAME/FIRSTNAME,1/10,M1,OAI5678/24AUGDEN
URES check-in with onward connection
PA:AI1234/+YLAX1LASTNAME/FIRSTNAME,1/10,OAI5678/+DEN,URES
URES/NOREC on connecting segment
PA:1,0/0,OAI5678/24AUGDEN,URES

Reserved.
Page 76
Page 77
Response to all of the above entries:
If TCIF parameter is set to 1, AI5678 is a code share marketing flight, and an ITCI bilateral
agreement exists between the host and the operating carrier. An ITCI Request Message is
sent to the operating carrier in an attempt to check-in the passenger. The following response
is displayed to the agent while waiting for a response from the operating carrier:
If the operating carrier does not find the passenger’s reservation on the connecting flight, the
passenger will not be checked in to the connection on the operators side.
If the passenger cannot be checked in to the connecting flight, the response issued to the
agent is:
EDI*PASSENGER SURNAME NOT FOUND

EDI* FURTHER PROCESSING INHIBITED
Onward Connection Added After Check-In

If the onward connection to a host-marketed code share flight is added to the passenger
record after check-in, SDCS shall follow the steps previously defined:
Example:
PU1,OAI5678YDEN

Reserved.
Page 78
Response if TCIF = 1 and an ITCI agreement exists between AI and the operating carrier.
Onward Connection Added Before Check-In

The agent may update the passenger record with the connecting flight information using the
PU not present option. In this case, no check for the operating flight data will be made until the
passenger is checked in with the onward connection.
Example:
PU#1,OAI5678/23AUGYDEN
Response:
Delete Onward Connection:

If the onward connection to a host-marketed codeshare flight, SDCS shall send a check-in
cancellation message to the operating carrier, as currently done for interline through check-in.
Example:
PW:1,0
Response:
Upon receipt of the response to the ITCI cancellation message, the system responds with:

Page 79
Sample ITCI Message

Reserved.
Page 80
Sample PNL with onward connection to code share flight
PNL with Connections to host marketed code-share flights
PNL with Connections to OA flights (for comparison purposes)

Page 81
Examples of Different Check-In (PA) Entries
Various check-in entries:
Check-in booked Y class passenger Jane Wright who is 8 years old with 1/14 baggage,
traveling alone, and add Unaccompanied Minor item. The UM indicator is added to the PSM
message for notification to the destination station. Also, the age is included on the PSM if it is
added with the UM code.
PA Entry: PA:XS836Y1WRIGHT/JANE,1/14,CHD1,UM8
Check-in from PS List: PA:<ENTRY NBR>,CHD1,1/14,UM8
Check-in Y class passengers Andersen/A and Sergeant/B traveling together on XS397 with
3/33 bags.
PA Entry: PA:XS377Y1ANDERSEN/A,M1,3/33;SERGEANT/B,F1
Check-in from PS List: PA:<ENTRY NBR>,3/33;<ENTRY NBR>
Check-in the second passenger from a family of three from entry number 2 with 1/10
baggage.
Check-in from PS List: PA:2P2,M1,1/10
Checked-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. All passengers want to sit together.
Check-in from PS List: PA:4,1/10,R17A;#12,R17B
Checked-in booked M class passenger Mr. T. Brook who is traveling with his wife, son, and
baby daughter Mary on flight XS397. The infant is not included in the passenger number but a
name must be added after the INF1 item.
PA Entry: PA:XS397M3BROOK/MR/MRS/MSTR,M1,F1,CHD1,
INF1MARY,3/30
Check-in from PS List: PA:<ENTRY NBR>,3/30/INF1MARY
Check-in URES C class passengers Mr. D. Kent and Mrs. J. Cannon who are traveling
together.
PA Entry: PA:XS296C1KENT/DMR,M1,2/30,URES;1CANNON/JMRS,
F1,URES

Reserved.
Page 82
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. The URES at the end denotes that the
oncarriage and not the passenger was a new item to the original passenger record.
PA Entry: PA:XS622Y1DAVIDSON/KMRS,F1,1/12,OKL204YAMS,URES
Check-in from PS List: PA:<ENTRY NBR>,1/12,OKL204YAMS,URES
Check-in URES Y class passenger Mr. T. Simpson with 1/14 bags and confirmed onward
flight DL881YLAX. 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.
PA Entry: PA:XS937Y1SIMPSON/TMR,1/14,URES,ODL881/07NOV
YLAX
Check-in a PAD passenger (N2) who was not previously listed on a flight and add his Date of
Joining his airline company.
PA Entry: PA:XS118M1HULBERT/LMR,1/12,IDN2/APR79,URES
Check-in two crew in C class who are traveling on the flight in passenger seats without any
baggage. These passengers are included in the total passenger figures but are also displayed
separately under XCR on the SDD display.
PA Entry: PA:XS633 C 2XXXCREW,0/0,M1,F1
Check-in passenger from PS display, entry number: six. Passenger requests an aisle seat.
The 'R' is the seat request, 'I' is the aisle, and 'S' for smoking.
Check-in from PS List: PA:6,1/15,RI
Check-in booked M class passenger York and add the message for the PSM that he is blind.
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
PA Entry: PA:XS383M1YORK,1/10,PSM/PLSE MAAS AS PAX IS

BLIND
Check-in booked Yclass family Watson who has one child and two infants. A '+' is inserted
between the infant names.
Check-in from PS List: PA:XS927Y3WATSON/MR/MRS/MSTR,3/30,M1,F1,

CHD1,INF2IAN+MARK
Check-in two infants with two separate adult entries.
Check-in from PS List: PA:1,2/20,INF1JOEY;2,INF1SUSAN

Page 83
Add a Name to a NONAME during check-in.
PA Entry: PA:XS100Y1NONAME,M1,1/10,NAM1JONES/MR.
Check-in from PS List: PA:1,NAM1SMITH/JOHN,M1,1/10
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. The baggage must be entered after the Z item.
PA Entry: PA:1ZXS397YATL,1/10
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. User modification.
PETC and AVIH count and weight will calculate excess baggage charges. If more than one
line is needed, start the second line with a '-' and put the onward connection as the last item;
otherwise, the system will ignore it.
PA Entry: PA:XS761YJRK4AHMED/MR/MRS/MST/MSTR,M1,F1,
CHD2,INF2ANA+DAR,4/50,
-PETC1/10,PSM/PLEASE MAAS AS PAX SPEAK NO
ENGLISH, OBA854YLHR,URES
Check-in URES Y class passenger Celina Johnson for the operating carrier of code share
flight XS761 with 1/12 baggage.
PA Entry: PA:XS761YJFK1JOHNSON/CELINA,F1,1/12,URES
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 Entry: PA:XS761YJFK1WHITE/MARY,F1,2/24,MKTYY761M23
ATLJFK,URES
Check in booked Y class passenger James Wilson by name for the next day flight with 1/12
baggage.
PA Entry: PA:XS761/+Y1WILSON/JAMES,M1,1/12
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 Entry: PA:XSY761Y1ADAMS/ALLEN,M1,1/12,O
Check-in from PS List: PA:<ENTRY NBR>,1/12,O2
Check in booked Y class passenger John Wells by name on XS761 with 2 interline through
check-in segments on YY851 and YY950 with 1/12 baggage.

Reserved.
Page 84
PA Entry: PA:XS761Y1WELLS/JOHN,M1,1/12,O2
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. 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.
PA Entry: PA:XS761Y1SMITH/SANDRA,F1,2/24,O2
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.
Check-in from PS List: PA:<ENTRY NBR>,NAM1JOHANSSEN/DAVIE,M1,1/12
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.
Check-in from PS List: PA:<ENTRY NBR>,1/20,OXS113YLHR
Enter one or more TKNE elements in the same entry.
PA Entry: PA:XX857Y2TOMS/J/K,M1,F1,1/10,B,TKNE1/1251234567890C1,
-TKNE2/1251234567891C1,URES
Check in two TKNE URES passengers with different names.
PA Entry: PA:XX857Y1TOMS/JACKIE,F1,2/48,B,TKNE/
1251234567890C1,URES;
-1SMITH/CAROL,F1,TKNE/1251234567898C1,URES
Check-in a TKNE URES passengers with an onward connection.
PA Entry: PA:XX857Y1TOMS/JACKIE,F1,1/10,B,TKNE/
1251234567890C1,URES,
-OXS789YMAD,TKNE/1251234567890C2,URES
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. The ‘INF’ indicator must be
inserted after the TKNE element and the ticket number.

Page 85
PA Entry: PA:XX857Y1TOMS/LYNMRS,F1,INF1BOB,1/10,B,TKNE/
1251234567890C1,
-TKNE/1251234567891C1-INF,URES
Check-in an infant not occupying a seat. 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.
-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
Check-in an infant occupying a seat. 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.
-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
Check-in an infant occupying a seat.
PS6A470/01MAY
-PS: 6A470/01MAY MEX
OP/NAM
72S/200 GTD/???? POS/GATE BDT1519 SD1549 ED1549 SA1720 FT0331
1. 2THOMAS/AMR Y TIJ PSM TKNE
THOMAS/BMIS+ Y TIJ TKNE
PS List of Infant not occupying a seat.
PS:470/.
PS: 6A470/01MAY MEX OP/NAM
1. 2ROHA/AMR SN22D Y TIJ INF PSM RES TKNE
ROHA/BMRS SN22E Y TIJ RES TKNE

Reserved.
Page 86
Check-in Acceptance - Infant occupying seat. 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.
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
1. THOMAS/AMR BN001 SN6F PSM
THOMAS/BMISS BN002 SN6E
PDD:1
PDD: 6A470/01MAYYMEX,1 PNR RL PB272
1. THOMAS/AMR BN001 SN6F Y TIJ BAG1/10/0
TKNE/6A/0952100004111C1
THOMAS/BMISS BN002 SN6E Y TIJ TKNE/6A/0952100004113C1
ACC VDT53640 AGT102/01MAY0920/OVR
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
1. ROHA/AMR BN001 SN22D PSM OSR
ROHA/BMRS BN002 SN22E OSR
PSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR
PDD:1
PDD: 6A470/01MAYYMEX,1 PNR RL P1272
1. ROHA/AMR BN001 SN22D Y TIJ INF1 BAG1/10/0 OSR
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
INF-BABYTWO
ROHA/BMRS BN002 SN22E Y TIJ OSR OSR
TKNE/6A/0952100004112C1
RES AUTO 01MAY0753
ACC VDT53640 AGT102/01MAY0756/OVR

Page 87
PCR (Check-in Record) of infant not occupying seat.
PDD:1
PDD: 6A470/01MAYYMEX,1 PNR RL P1272
1. ROHA/AMR SN22D Y TIJ RES INF1
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
INF-
ROHA/BMRS SN22E Y TIJ RES TKNE/6A/0952100004112C1
RES AUTO 01MAY0753
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.
Check-in from PS List: PA:<ENTRY NBR>, P/W BAGS, SNRGRP

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

Reserved.
Page 88
Issuing Boarding Pass for Return Check-in Outside 72 Hours
Return check-in outside 72 hours allows the issuance of boarding card for onward flights
operating more than three days into the future without actually checking in the passenger.
The functionality can also be used for outbound flights within 72 hours that are not activated in
SDCS. Boarding cards for such flights are issued using the option ORBP (Outbound Return
Boarding Pass).
Inputs to Issue Boarding Cards

The option to print boarding card for return flight is available for passengers already on the
PNL/ADL and those added at Check-in time (No records).
Passenger Already in the PS List (Passenger List)

Entry:
PA:1,1/22,O,ORBP
Response: Passenger Checked-in, Boarding pass issued for both first and outbound flights.
A party of 3 passengers with 1 outbound flight DL135 which is not active in SDCS. In this
case boarding cards are issued for both flights. But check-in is done for DL261 only.
PDD:1
PDD: DL261/19OCTYLGW,1 PNR RL HX6X1
1. CCCCCCC/AA A5 Y SKG
O/DL135/27OCT Y LGW
CCCCCCC/BB A5 Y SKG
O/DL135/27OCT Y LGW
CCCCCCC/CC A5 Y SKG
O/DL135/27OCT Y LGW
»PA:1,3/40,O,ORBP
»PA: DL261/19OCTYLGW1,3/40,O,ORBP
AV J22Y220 PAD J0Y0
342/J230 GTD/???? POS/GATE BDT1000 SD1030 ED1030 SA1600 FT1230
1. CCCCCCC/AA A5 BN001 SN32G O
CCCCCCC/BB A5 BN002 SN32E O
CCCCCCC/CC A5 BN003 SN32C O
O/DL135/27OCT Y SKG

Page 89
Outbound Information Added at the Time of Check-in
If the passenger is on the PS list but does not have outbound flight information in the check-in
record, the agent has the option to add the outbound segment manually and then issue the
boarding card. An option to add the outbound flight and issue boarding card on the same
transaction is also available.
Entry: To add outbound flight XX123/26OCT ATL-MIA (Passenger is already checked-in on
the first flight.)
PU:1,OXX123/26OCTYMIA
PU:1,O,ORBP
Or,
Entry: To issue the boarding card for XX123/26OCT
BC:1,O,ORBP
No Record Passenger Check-in

For no record passengers, the check-in on the first flight needs to be completed before
boarding card for the outbound is attempted.
Entry to issue boarding card for XX123 if go show limit permits. Otherwise the passenger
goes to standby and has to be accepted with AC:1.
PA:XX123/19OCTYATL1NAME/FIRST,1/10,M1,ODL435/27OCTYMIA
Entry: To issue a boarding card for the first flight (XX123)
AC:1
Then,
PU:1,O,ORBP
Or,
Entry: To issue a boarding card for the outbound (DL435/27OCT)
BC:1,O,ORBP

Reserved.
Page 90
No Record Passenger Check-in - Error
A FORMAT error is returned if the ‘O’ is missing when printing a boarding card for an
outbound using the ORBP option.
PU:1,ORBP
015 - FORMAT
>BC:1,ORBP
015 - FORMAT
Outbound Boarding Card (ORBP) Issuance Processing Rules

The option to print boarding pass using ORBP (Outbound Return Boarding Pass) depends
on the following conditions:
1. The outbound flight is not active in SDCS
2. The passenger is assigned the same boarding and seat numbers as the first flight
3. ORBP boarding card is not issued for ITCI flights
4. The boarding card shall contain Passenger name, flight number and date, destination,
boarding and seat numbers.
Summary of ORBP Option Inputs

Input Output
PA:1,1/22,O,ORBP n Passenger (s) check-in and boarding pass issued

for the first flight.
n Only boarding card issued on the outbound flight.
PU:1,OXX123/26OCTYABC Passenger check-in record update after acceptance.
PA:XX123/19OCTYATL1NAME/FIRST, GO show passenger check-in.

1/10,M1,ODL435/27OCTYMIA
BC1,O,ORBP Reprint boarding pass for outbound flight- Passenger

must be accepted on the first flight.
PU:1,O,ORBP Print boarding pass for outbound flight.

Passenger must be accepted on the first flight.

Page 91
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.
PA transaction:
►PA1,1/10,B
PCTC REQUIRED
►PA1,1/10,B,PCTC/MARIA JONES 770-555-1212
PU transaction:
►PU1,PCTC/JOHN SMITH 770-555-1212

PCTC REQUIRED
PW transaction:
►PW1,PCTC
A list of passengers with PCTC remarks can be displayed with the following transaction:
►PS:XS123/12YY , PCTC

Reserved.
Page 92
AUX Element SVC
The AUX element code SVC (per AIRIMP) is the only AUX element that can be included in
DCS messages and can be added to the passenger record. Requirements to add SVC are as
follows:
Number /
Field
Components Type of Example
Required
Character
Element Identifier M 4 or 6 PU:1 or PU#1P1
Service Code M 3 Alpha SVC
Space
Free Flow O 59 TOY

Alpha/Numeric AIRPLANE/8761234567895C1
Agent can add free flow
elements. Elements are
separated by /.
Example: PA
PA:1,1/10,M1,SVC TOY AIRPLANE/8761234567895C1
Examples: PU
PU:1,SVC TOY AIRPLANE/8761234567895C1
PU:1P1,SVC TOY AIRPLANE/8761234567895C1
PU:1,SVC LOUNGE ACCESS/8761233567875C2
Example : PW
PW:1,SVC
PW:1P2,SVC
Notes:
n Only one entry number per transaction is allowed.
n A not-present passenger -cannot- be deleted for SVC.
n PW: is restricted to gate CRT after initial close.

Page 93
Passenger Check In with PIL Remarks
The agent may perform passenger check-in and include remarks which are added to the
Passenger Information List (PIL) message.
Number /
Field
Components Type of Example
Required
Character
Element Identifier M 4 or 6 PU:1 or

PU#1P1
Element Code M 4 Alpha RPIL
Slash M / /
Free Flow O 60 SLOW

Alpha/Numeric WALKER
Agent can add free flow elements. Elements
WITH
are separated by /.
CAST
Check-in Passenger with RPIL Remark

Example: PA
PA:1,1/10,M1,RPIL/SLOW WALKER WITH CAST
Add RPIL Remark to passenger record

Examples: PU
PU:1,RPIL/SLOW WALKER WITH CAST
PU:1P1,RPIL/SLOW WALKER WITH CAST
PU:1,RPIL/SLOW WALKER WITH CAST
Notes:
n Only one entry number per transaction is allowed.
n This entry can be used before check-in (PU#) or after check-in (PU). However if entry is a
family, then the specific family member should be identified (example 1P2), otherwise the
default will be to the first passenger listed in the record.
n The update action replaces any previous entry. It dos not add to any current remarks. The
PDD record will note the agent, time, and location of when the RPIL was added.

Reserved.
Page 94
Delete RPIL Remark
Agent deletes the remark using PW entry.
Example : PW
PW:1,RPIL
Note:
The delete entry can be used before check-in (PW#1,RPIL) or after check-in (PW1,RPIL).
However if the delete entry is for a family, and the RPIL was added to a specific passenger in
that family, the specific family member should be identified (example PW:1P2,RPIL),
otherwise the delete entry will be rejected with the error "452 - Modification Not Possible).
Generate PIL Message

Agent enters the LR transaction to request the PILC.
Example Entry:
LR:HX767/22JAN/HKG/PILC
Result:
PIL is generated to the requested option (Screen, printer or teletype address)
Example:
PIL
HX767/22JAN HKG
CCLASS
8A/BKK MAHESHWARI/LALITMR SPML AVML HK1
8C/BKK CHANDRASEKHA/RAMOORTHY+ KA802J23PVG
8D/ICN KOH/KWANGMINMR
8E/BKK LOPAN/HSIUCHIAO MH797C23KUL
8F/BKK LIN/MEIMEI MH797C23KUL
8H/BKK BHANOTE/BRIJESH MR
8K/BKK SUNDARAM/CHETPAT ARYA AI317Z23DEL
9A/BKK JAIN/ABHISHEK MR
9C/BKK KUOLIU/AWENMRS MH797C23KUL
9H/BKK LEE/YENLING MH797C23KUL
9K/BKK HAN/ANRONG MR
12A/BKK CHEN/SUQING MS

Page 95
INVOL UPGRADE DUE OB
12C/BKK CHEN/GUORONG
12D/BKK ZHENG/ZHIQING MR
12E/BKK ZHENG/XINGHUA MR
12F/BKK JIANG/DANSHENG MR
12H/BKK HE/RUFU MR
12K/BKK CHEN/XIAOFANG MR
14A/BKK GUO/CHENGCHU MR
14C/BKK CHUNG/YICHAO MH797C23KUL
14D/BKK CHUNGCHANG/CHU MH797C23KUL
14E/BKK PATIL/MANISH
14F/BKK XIAO/YONGQING MR
14H/BKK XIAO/YONGWEN MR
14K/BKK SRIVASTAVA/ANKITA MS
YCLASS
18D/BKK LIU/PINGMEIMS MH797L23KUL
18E/BKK WANG/YULIMS MH797L23KUL
19A/BKK HEYD/KRISTIJOY MS
SLOW WALKER WZ CAST
19H/BKK YANG/TSAICHU MH797L23KUL
20C/BKK BAVISHI/AMIT MR SPML AVML HK1
27K/BKK GUAN/XINGHUA MSTR
CHD07
34A/BKK JIANG/DANSHENG MSTR
CHD05
34E/BKK TSENG/CHAOMEI MH797L23KUL
38K/BKK YU/CHENGCHU MH797L23KUL
END OF LIST
Electronic Miscellaneous Documents (EMD)

SDCS supports Electronic Miscellaneous Documents (EMD) by processing the ASVC and
SVC codes:
n Processes ASVC/SVC from reservations systems when received on the PNL/ADL.
n Adds ASVC/SVC to passenger record contained in PNL/ADL.

Reserved.
Page 96
n Updates passenger record with ASVC/SVC via PU and PA.
n Removes ASVC/SVC via PW.
n Displays ASVC/SVC on the Boarding Pass.
n Displays ASVC/SVC on PS list.
n Includes ASVC/SVC on the JL sort category PS.
n Includes ASVC/SVC on PIL.
Notes:
n If SDCS receives an ADL after an agent has modified the passenger's record before
check-in, ASVC will be processed except for seat.
n If SDCS receives an ADL with an ASVC for excess baggage and the excess baggage
information has not been added to the passenger's record, the check-in agent must
manually enter the information.
PNL
The AUX element code SVC (per AIRIMP) is the only AUX element that can be included as
an individual element in DCS messages. The elements of this message include mandatory
and optional elements that can be sent to DCS in the PNL or ADL.
Example:
AMSKMKL
.MADRMIB 042345
PNL
IB881/05MAR AMS PART2
-AGP80Y-PAD05
1SMITH/GEORGEMSTR .R/UMNR HK1 UM08
HK1/P/US/732154364/US/12FEB86/M/21AUG07/GERTMAN/STEFAN/MICHAEL
2MOLEMAN/TOMMR/COURTNEYMRS .R/VGML NN1-1MOLEMAN/COURTNEYMRS
1OPPERSTAL/GINAMRS
1BLACK/JAMESMR .R/SVC HK1 05MAR/LOUNGE ACCESS/8761234567895C1
PDD: Update from PNL

Once the PNL/ADL is processed the Passenger Record (PDD) is updated with the
ASVC/SVC information
Example:

Page 97
PDD: XX263/21JUNUAMM,13 PNR RL 3CTMZ9
1. ABEDALQADER/JAMILMR BN162 SN22C U ORD OKT RQST/SN22C M1
BAG2/34/0 FQTR/TKN E
TKNE/RJ/5122106552971C1
APPB RJ263172CKI0007 US /401100033288134 8561
SVC- HK1 05MAR/LOUNGE ACCESS/8761234567895C1
DOCA-R/USA/////
DOCS-C /USA/061151798/JOR/11FEB85/M
/22JUL20/ABEDALQADER/JAMIL/MUSTAFA/
DOCS-P /JOR/K100803/JOR/11FEB85/M
/21MAR14/ABEDALQADER/JAMIL/MUSTAFA/
PDD –Update SVC with PU

The SVC can be manually added using the current PU entry.
PU Field Requirements are as follows:
Note: The maximum number of characters after SVC is 60.
Components Description Example
Element Identifier Alpha: 4 or 6 PU:1 or PU#1P1

Mandatory
Service Code Alpha: 3 SVC

Mandatory
Space
Free Flow Alphanumeric: 59 TOY AIRPLANE/8761234567895C1

Optional
Examples:
PU:1,SVC TOY AIRPLANE/8761234567895C1
PU:1P1,SVC TOY AIRPLANE/8761234567895C1
PU:1,SVC LOUNGE ACCESS/8761233567875C2
PA – Add SVC with PA

Example:
PA:1,1/10,M1,SVC LOUNGE ACCESS/8761234567895C1
PDD is updated.
Example:

Reserved.
Page 98
***CODE SHARE***US8703 AA7201
PDD: XX263/21JUNUAMM,13 PNR RL 3CTMZ9
1. ABEDALQADER/JAMILMR BN162 SN22C U ORD OKT RQST/SN22C M1
BAG2/34/0 FQTR/TKN E
TKNE/RJ/5122106552971C1
APPB RJ263172CKI0007 US /401100033288134 8561
SVC- TOY AIRPLANE/8761234567895C1
DOCA-R/USA/////
DOCS-C /USA/061151798/JOR/11FEB85/M
/22JUL20/ABEDALQADER/JAMIL/MUSTAFA/
DOCS-P /JOR/K100803/JOR/11FEB85/M /21MAR14/ABEDALQADER/JAMIL/MUSTAFA/
APPS US/RJ263172CKI0007/0Z/
PA VDT18990 AGT694/22JUN1824/SVC LOUNGE ACCESS/8761234567895C1
ACC VDT18990 AGT694/22JUN1933/SN22C
Display ASVC/SVC on Boarding Pass

SITA Departure Control Services will include the ASVC/SVC on the boarding pass when
ASVC/SVC are included in the passenger record. If a passenger has both an ASVC and a
SVC remark, the default priority is for the ASVC remark. If a passenger has more than one
ASVC or SVC, the last one is printed on the boarding pass.
There is a maximum field size of 48 characters for this information. Some subscribers will
have less space due to other items which are included on their boarding pass.
Note:Inclusion of ASVC and SVC remarks on the boarding pass requires the subscriber to
submit a new PECTAB design to SITA.

Page 99
Display ASVC/SVC on PS List
The PS List has been enhanced to include the ASVC/SVC.
Example:
ps:001/.
»PS: XS001/06DEC ATL OP/NAM
747/400A GTD/???? POS/GATE BDT2030 SD2100 ED2100 SA2245 FT0145
1. 1ADAMS/JOHN+ A2 Y MIA PSM ADV-PW/NP
2. 1BAKER/JAME+ A2 Y MIA PSM SFML
3. 1GRANGE/RICH+ Y MIA PSM VIP

4. 1JOHNSONS/JAME+ SN44C Y MIA PSM SVC
Display ASVC/SVC on the PIL

The Passenger information list PIL contains a list of SSR items. The new code SVC will be
included on the PIL. In order to provide an option to the airline to include on not include SVC a
new parameter SVCP will be set.
The SITA helpdesk controls the URM (Airline Parameter) and will set this parameter as
authorized by the Customer:
n 0: Default. Current processing
n 1: Provides functionality to include ASVC/SVC on the PIL, JL, and PSM
n 2: Provides functionality to include ASVC/SVC and all associated remarks on PIL and JL
If URM for SVCP is set to 0, no changes are made.

If URM SVCP is set to 1, then the ASVC/SVC will be included on the PIL. JL, and PSM
IF URMSVCP is set to 2, then ASVC/SVC and all associated remakrs will be included on PIL
and JL.

Reserved.
Page 100
Example:
PID NUMBER 44215 PRIORITY 3 13:49
DVC-44215 1349 24MAY14
PIL
UX6067/24MAY ORY
CCLASS
1C/FRANCES/HMRFQTV AF/ST0
1D/BARON/CMRS
1F/BARON/BMRFQTV AF/ST0
2A/CALLAIS/JMR
2C/STARK/LMRS WCHR ASVC PASSENGER ENTILTLED TO USE LOUNGE AND BE PRE-BOARDED
SVC UPGRADE AUTHORIZED IF SPACE AVAILABLE
SVC BEING MET BY CUSTOMER SERVICES ON ARRIVAL
2D/RED/BIG
2F/1EST/A
3A/ANGERS/GM WCHR VGML ASVC PAID EXCESS BAG/8399585
3C/GIRAS/NMRS
3D/BLUE/NOT SO
3F/YELLOW/FLOWER SVC LOUNGE ACCESS/8761234567895C1
END OF LIST
JL PS Sort Option
The current JL passenger list PS option (List by seat number with all SSR and PSM
information) will include new SVC.

Page 101
Example:
PID NUMBER 44215 PRIORITY 3 13:49
DVC-44215 1349 24MAY14
SITA AIRLINES JL:PS 04-03-14 19:26 PAGE:1
PASSENGER SEATING LIST OK3399/05MAR ACFT REGN
BOARDING CITY/PRG
CLASS Y
SN NAME
11F BLANE/JESSIEMRS SSR: ASVC - FREE UPGRADE TO BUSINESS CLASS IF SPACE
AVAILABLE AT THE GATE SVC - MET BY COURTSEY CAR ON ARRIVAL SVC - ONE EXTRA
PIECE OF LUGGAGE ALLOWED SVC - ACCESS ALLOWED TO BUSINESS LOUNGE
16A GLIDDON/STEVEMR
16B GLIDDON/SUSUANMRS SVC – ACCESS ALLOWED TO BUSINESS LOUNGE
TOTAL/SEG/CL: 3
OVERALL TOTAL: 3 PAXS
SFEB
The SVC element can be added using the SFEB special services box.
Example:
Add text in the special services box.
SVC TOY AIRPLANE/8761234567895C1
Note: The maximum characters in the special services box is 80.
DOCS, DOCA, and DOCO Information at Check-in Time

Certain governments collect data that is available in passenger’s 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.

Reserved.
Page 102
The following are formats that provide passport, address and other travel related information:
n Travel Document Information (DOCS)
n Residence or Destination addresses (DOCA)
n Other Travel Related information (DOCO)
DOCS – 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
P Passport
A Alien Resident Certification
C Permanent Resident Certificate
T Re-entry permit/refugee
I INS Pass
M Military ID
N Naturalization Certificate
B Boarding crossing card
F Facilitation Document
Note: The above documents do not pertain to all countries.

Edits for the DOCS entry are as follows:
DOCS Entry Edit
Check-in code PA or PU
Pax Entry # 1
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

Page 103
DOCS Entry Edit
Date of Birth 14AUG65
Gender M or F
FI or MI (infant indicator)
Expiration date 28JAN09
Surname BYRD
Given name MILLY
Middle name (optional)
Adding the DOCS entry to a passenger’s record. Display the PS list, enter PS Flight/Date:
►PS1548/.
The Passenger List for the flight and date entered displays:
PS1548
►PS: XS1548/03MAR MEX
CC/NAM
D10/123 GTD/???? POS/GATE BDT2130 SD2200 ED2200 SA2345 FT0045
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
Display a passenger’s PDD:
►PDD:02PS
The Passenger Record displays: PDD:02
PDD: XS1548/03MARMMEX,02 PNR RL DI93KD

1. BYRD/MILLY M ATL M1/80

Reserved.
Page 104
Check-in the passenger with the following entry:
►PA1,0/0,docs/p/usa/920881/usa/14aug65/f/28jan09/byrd/milly
The PDD displays the following DOCS information:
►PDD:01
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
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.
Redisplay the previous passenger’s PDD:
PDD:01
The Passenger Record displays:
►PDD:01
1. BYRD/MILLY BN001 SN14A M ATL OKT INF1/10 M1/80
INF-MARY
SCW VDT2110 AGT877/03MAR1105/OKT
PU VDT2110 AGT877/03MAR1221/INF

Page 105
Add the infant passport with the following entry:
►PU1,DOCS/P/USA/923498/USA/14AUG04/FI/17NOV15/BYRD/MARY
The PDD now includes DOCS information for the infant:
►PDD:01
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 VDT2110 AGT877/03MAR1231/DOCS
Deleting Docs from Passenger Records

To delete DOCS from a single passenger, enter:
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, enter:
PW1P2,DOCS

Reserved.
Page 106
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, enter:
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.

Page 107
DOCA - 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:
n Residence Address R
n Destination Address D
Edits for the DOCA entry are as follows:
DOCA Entry Edit
Pax Entry # 1
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 I
Checking in Passengers with a Destination or Residence Address

Accept a passenger on to the flight and redisplay the passenger record:
►PDD:01

Reserved.
Page 108
The Passenger Record displays:
►PDD:01
PDD: XS1548/03MARYMEX,01 PNR RL 92K292
1. PETRALLI/INGE BN003 SN27A Y ATL OKT M1/80
Add the destination address to this passenger’s 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
PDD:01
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
PU VDT2110 AGT877/03MAR1306/DOCA
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
DOCA-R/DEU//

Page 109
Adding Infants – Address Information
Infants may require:
l destination address
l residence address
l 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.
Display the passenger record:
►PDD:01
►PDD: XS1548/03MARYMEX,01 PNR RL 92K292

1. PETRALLI/INGE BN003 SN31J S Y ATL OKT INF1/10 M1/80
INF-GRETCHEN
DOCA-R/DEU//
The following entry adds a destination address for the infant:
►PU1,DOCA/D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I

Reserved.
Page 110
An infant destination address now displays in the passenger record:
PDD:01
INF-GRETCHEN
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
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.
Display the passenger record to verify that the infant country of residence was added to the
passenger record, enter:
►PDD:01

Page 111
To Display:

INF-GRETCHEN
DOCA-R/DEU//I
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
DOCO (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
Pax Entry # 1
Special Service Requirements code doco
Passenger Place of Birth Sydney AUS
Document Type V
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

Reserved.
Page 112
Checking in Passengers with Place of Birth and VISA information
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
Add place of Birth and VISA information using the following:
PU1,DOCO/SYDNEY AUS/V/AB54321/SYDNEY/15DEC05/USA
The PDD now contains Place of Birth and VISA information, enter:
►PDD:01
To display:
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 infant’s place of
birth and VISA information.
Accept the infant on a flight and redisplay the record, enter:
►PDD:01

Page 113
To display:

1. FIELD/DONALD BN004 SN2D F ATL OKT INF1/10 M1/80
INF-JOHN
The following entry adds place of birth and VISA information to the infant:
►PU1,DOCO/SYDNEY AUS/V/CD1234567/SYDNEY/15DEC05/USA/I
The PDD now displays:
►PDD:01
To display:

1. FIELD/DONALD BN004 SN2D F ATL OKT INF1/10 M1/80
INF-JOHN
DOCO-SYDNEY AUS/V/CD1234567/SYDNEY/15DEC05/USA/I
Entries to List Passengers with DOCS, DOCO or DOCA Information

To identify passengers with travel document information, enter Fligh/Date,DOCS:
►PS:218/.,DOCS

Reserved.
Page 114
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 Y ATL O DOCA DOCO DOCS
MOUSSA/CMRS BN003 SN13A Y ATL O DOCA DOCO DOCS
3. 1YAGO/CRMS BN005 SN25F Y ATL DOCA DOCS
DOCA: 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
DOCO: 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
Entries to List Passengers Missing DOCS, DOCO or DOCA Information

To identify passengers missing travel document information, 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.

Page 115
►PS1548,NDOCS
►PS: XS1548/06MAR MEX,NDOCS
OP/NAM
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
To identify passengers missing address information, 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

OP/NAM
1. 1AHMED/MMKY+ Y ATL O DOCS
3. 1APPLE/GOLD+ Y ATL PSPT DOCO DOCS
4. 1BASHIR/RAZI+ G2 SN16J Y ATL RES PSPT DOCS
To identify passengers missing Visa or Place of Birth, enter Flight/Date,NDOCO:
►PS1548/.,NDOCO

Reserved.
Page 116
A list of passengers on the flight and date who are missing DOCO travel document
information displays.
PS: XS1548/06MAR MEX,NDOCO

OP/NAM
1. 2AHMED/CHOW+ Y ATL DOCA DOCS
AHMED/AZWA+ Y ATL DOCA DOCS
2. 1AHMED/MMKY+ Y ATL O DOCS
4. 1BAGIROVA/ELVI+ Y ATL DOCA DOCS
5. 1BASHIR/RAZI+ G2 SN16J Y ATL RES PSPT DOCS
Error 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 The maximum number of characters for a field is

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

Page 117
Error Message Definition
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 The given name as it appears on the travel document
NAME was not entered in the DOCS field.
NEED TRAVEL DOCUMENT The surname as it appears on the travel document

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

Reserved.
Page 118
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 / Optional Description
Passport number Mandatory Maximum 35 characters.
IATA country code of issue Mandatory Two- or three-alpha characters.
Date of birth Mandatory Day/month/year (e.g.,

01JAN50).
Gender code Mandatory M-male F-female.
Surname Mandatory
First name Mandatory
Expiration date Optional Day/month/year (e.g.,

01JAN06).
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
PSPT item with all details entered.
►PA:1,1/10,B,PSPT/P/P04126490/US/20AUG65/M/SMITH/JOHN/01JAN06/US
Input for a NREC passenger.
►PA:XS100F1TOLSON/MR,1/10,B,PSPT/P/P87638121/US/03APR43/M/TOLFSON/JAMES/20DEC
70/US

Page 119
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/P12328/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.
Multiple passport entries for a family of 2JONES/MR/MRS.
►PA1,3/33,B,PSPT1/A1238564/US/20JUN50/M/JONES/MICHAEL/16MAR10/US,PS
PT2/
A5463245/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
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.

Reserved.
Page 120
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 / Optional Description
Passport number Mandatory Maximum 35 characters
IATA country code of issue Mandatory Two or three-alpha characters
Date of birth Mandatory Day/Mon/Year (e.g., 01JAN50)
Gender code Mandatory M - male

F - female
Surname Mandatory
First name Mandatory
Expiration date Optional Day/Mon/Year (e.g., 01JAN06)
Nationality Mandatory Two or three-alpha characters

Page 121
PSPT input on a passenger without an expiry date:
An oblique follows all passport details. If the optional expiry date is omitted, oblique’s 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
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
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.
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.
PSPT DOB entry for an infant:
►PA:1,PSPTI/B/20AUG65/SMITH/ANGELA
Deletion of PSPT Remark

The PW transaction can delete a PSPT item from a passenger’s record.
PW Use and Restrictions
The PW transaction is allowed after a prior PS, SB or PDD display. .

Reserved.
Page 122
PW Input
A PW transaction can delete a PSPT item from a passengers record with the following
format:
►PW:1,PSPT/ALL
Transaction to delete one of the PSPT items on multi-passenger record.
►PW:1,PSPT/1
Transaction to delete PSPT items from passengers one, three and four of a passenger
record.
►PW:1,PSPT/1/3/4
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
Format The format of the PSPT deletion is incorrect.
Modification Not Possible There is not a PSPT item to delete in this passenger record.

Page 123
Subsequent Processing
All processing not specifically mentioned remains unchanged.
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
PS input, with PSPT as the option.
►PS:FLT/DATE/CLASS,PSPT
PS Output
PS list sorted with the PSPT item is shown below:
PS: XS500/29AUGXATL,PSPT
OP/NAM
DC9/JRAM GTD/???? POS/GATE BDT1730 SD1800 ED1800
1. 2CHARLES/MR BN002 SN27C Y JFK MSG PSPT
CHARLES/MRS BN003 SN27B Y JFK PSM
2. 2CURIE/PIER+ Y JFK PSPT
CURIE/MADA+ Y JFK PSPT
3. 1DOUGLAS/KIRK BN001 SN14F Y JFK PSM MSG PSPT
4. 1EINSTEIN/ALBE+ Y JFK PSPT
PDD Display
Each passenger record shows the PSPT remark, much as the other special remarks or items
are displayed.
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 BAG1/10/0
CHARLES/MRS BN005 SN10B Y MSP
ACC VDT965 AGT1/26AUG1406
PSPT-CHARLES/RAYMR/P123456/GB/01JAN50/M/01JAN06
CHARLES/RAYNELMR

Reserved.
Page 124
Boarding Pass Inhibit for APIS Flights
The system will check the government country requirement for APIS, inbound, outbound, or
both. If the flight has an APIS retirement, the system will inhibit the issuance of the boarding
pass if the DOCS element is not complete in the passenger record.
The airline has the ability to by-pass the APIS DOCS requirement by adding APIS non
requirement to the segment data to the CSM. For more information, refer to the
SITA Departure Control Services Check-in Supervisor User Guide.
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/

Page 125
The crew list for the flight and date displays.:
CREW:XS1548/06MAR06 /ATL Delete crewman:_

*Personal Information
Surname:________________________________________
Given/Middle Name:___________________ /________________________
Gender:_ Nationality:___ Birth date:_______
PCTC: _________________________________________________________
Residence country:___ Address Details:_________________________
ZIP/Postal Code:____________ City:____________________________
State/Province/Country:_________________________
Final Destination:___ Birth Place:______________________
Crew Status:___ 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:________________ Country of issue:___

Reserved.
Page 126
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_________________
Document Information
M = Military-ID T = US Re-entry permit A = Alien registration card
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:1548/.,CREW
PS: XS1548/06MAR MEX,CREW OP/NAM

747/SP GTD/???? POS/GATE BDT1000 SD1030 ED2359 SA1400 FT2001
1. 1SMITH/JOHN ! 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, enter the PDD number.
PDD:01

Page 127
PDD Displays as following:
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 crew member by mask, enter the CREW number.
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:___ Birth Place:USA+ATLANTA+GA____________
Crew Status:CR1 Crew Title:CAPTAIN___________________
card
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

Reserved.
Page 128
To delete a crewmember, select 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________________
Final Destination:___ Birth Place:USA+ATLANTA+GA_____________
Crew Status:CR1 Crew Title:CAPTAIN___________________
card
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
Advanced Passenger Processing (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, South Korea, 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.
n 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.
n Agents can modify passport data in a passenger record prior to a check-in transaction.
n Passengers without authorization to board will not receive a boarding pass and the agent
will be prompted to delete the passenger.

Page 129
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 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.
Check-in
Check Single Passengers
Use the PS List, for example:
► xs7777,namSMITH
PS: xs7777/10OCT SGN,NAMSMITH
OP/NAM
320/A GTD/???? POS/GATE BDT1130 SD1200 ED1200 SA2300 FT0800
1. 1SMITH/JOHN Y SYD
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.

Reserved.
Page 130
Check Multiple Passengers
Use the PS List; e.g.; PS:XS123/., NAMBERRY;NAMALVAREZ:
► ps123/+,NAMBERRY;NAMALVAREZ
PS: XS123/11OCT SGN OP/NAM
1. 1ALVAREZ/JOSE Y SYD
2. 1BERRY/JOHN Y SYD
-PA1,0/0,DOCS/P/USA/T67778/USA/12jul67/M/12JUL15/ALVAREZ/JOSE;2,
- DOCS/P/USA/T67234/USA/13SEP70/M/13SEP15/BERRY/JOHN
Checking a Passenger without PSPT or DOCS Data

n 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
1. SMITH/JOHN BN003 SN21D
WARNING - APP FLIGHT - PSPT DATA-
n 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.
PS123/+,NAMSMITH
PS: xs123/11OCT SGN,NAMSMITH OP/NAM
1. 1SMITH/JOHN BN003 SN21D Y SYD APP
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
PS123/+,NAMSMITH
PS: XS123/11OCT SGN,NAMSMITH OP/NAM
1. 1SMITH/JOHN BN003 SN21D Y SYD DOCS APP
PU:1,APP
PU: XS123/11OCTYSYD1,app
AV C12Y135 PAD C0Y0
APP TRANSACTION IN PROGRESS
AU APP* (0502) OK TO BOARD/BN3

Page 131
Check-in of Multiple Passengers - Partial Acceptance by CPS System
Boarding pass printing is suppressed for any passenger not receiving authorization to travel.
Where one passenger receives OK and the other Not OK:
1. SMITH/TMR BN050 SN14A

*Australia APP * OK TO BRD/BN050
2. TALBOT/KMRS BN051 SN14B

Australia APP * 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 ►PW-2,APP (for second passenger) transaction is presented to delete the
passenger, if necessary.

Reserved.
Page 132
After SDCS sends the APP queries, the CPS system generates an appropriate response
from the following list:
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 country’s 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 Unable to determine the passenger status. The passenger identity

Messages (U) 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 Insufficient data is available for an assessment. Provide additional

Messages (I) passenger data.
Miscellaneous Error is detected. Correct the error.

Messages (E)
Passenger Cancellation
Normal DCS processing for a PW applies.
Cancellation of a previous APP (ok to board) passenger:
►PW:-1
PW: XS7777/20OCTYSYD-1
AV C12Y138 PAD C0Y0
1. SMITH/JOSEPH DELETED
AU APP* (8505) CANCELLED/BN1

Page 133
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:
n (For PA or PU) “Country Name APP Flight, 5 passenger maximum group size”.
n (For PW) ”Country Name APP Flight, 5 passenger maximum group size”.
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 LMTS Y MEL URES IDID00S101
APPB-AU /8501/OK TO BOARD
Response (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
Override
To override ‘Do not board’ passengers the transaction is the following:
PU:1,APPG/AU/FREE TEXT
PU:1,APPA/AU/FREE TEXT

Reserved.
Page 134
AV C12Y137 PAD C0Y0
320/A GTD/???? POS/GATE BDT2230 SD2300 ED2300 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 GTD/???? POS/GATE BDT2230 SD2300 ED2300 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
Re-sending APP Message

To clear some of the passenger status and 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 GTD/???? POS/GATE BDT1630 SD1700 ED1700 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 HOTEL-IN
15JUL OUT 21JUL
EQ CHGSGN
AU APP* (8510) DO NOT BOARD - CONTACT EOC/BN1
PW:-

Page 135
Status Codes
After check-in the passengers can have the following status:
n APPB The passenger has been given clearance to board. (Screen message “OK to
BRD”).
n 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”).
n 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).
n APPI Insufficient data is available. (Screen message: Will vary depending on conditions).
n APPE An error condition has been detected. All error conditions must be corrected before
processing. (Screen message: Will vary depending on conditions).
n 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.
Passenger Status Change

After check-in, a passenger with a status changed can be displayed with the following
transaction:
AQPS:Flight/Date
ACCEPTED
767/DD GTD/???? POS/GATE BDT2315 SD2345 ED2345 SA0300+1 FT0315

AV F15C32Y120 PAD F0C0Y0
PAGE: 01
1. 1BOND/JAME+ BN002 SN29C Y YYZ-APPB APPD
2. 1CHECA/CARL+ BN003 SN12G Y YYZ-APPB APPD
3. 1DEPUNIET/RAND+ BN001 SN22G Y YYZ-APPB APPD
4. 1EDWARDS/COLI+ BN008 SN21A Y YYZ-APPD APPB
5. 1FABRIZIO/MICH+ BN004 SN12A Y YYZ-APPB APPD

Reserved.
Page 136
1. Bond/Jane Passenger Name
BN002 Boarding Number
SN29C Seat Number
Y YYZ - Class Destination
APPB Original government status
APPD New government status

Page 137
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.
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___________
M = Military-ID T = US Re-entry permit A = Alien registration card
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: ____________________ Country of issue:___

Reserved.
Page 138
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.
Passenger Check-in and Update

AQQ transaction using Passenger Acceptance (PA) receiving an OK TO BOARD
response:
PS:XS123,NAMSOLE
_PS: XS123/21FEB JFK,NAMSOLE OP/NAM
767/B GTD/???? POS/GATE BDT1830 SD1900 ED1900 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
AQQ transaction using Passenger Acceptance with a NO-FLY status:
PS:XS123,NAMALEX
_PS: XS123/21FEB JFK,NAMALEX OP/NAM
767/B GTD/???? POS/GATE BDT1830 SD1900 ED1900 SA2200
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:-
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.
A PU1,APP transaction to update passenger status:

Page 139
PU1,APP
_PU: XS123/21FEBYKBP1,app
AV C19Y192 PAD C0Y0
1. ALEXANDER/CREWE BN012 SN25A
US APP* (8501) OK TO BOARD/BN12
Passenger receiving a SELECTEE status:
PA1,0/0
_PA: XS123/21FEBYKBP1,0/0
AV C19Y192 PAD C0Y0
767/B GTD/???? POS/GATE BDT1830 SD1900 ED1900 SA2200 FT2000
1. DRAGONS/CATALANS BN013 SN38G
US APP* (8541) SELECTEE/BN13

Reserved.
Page 140
Passenger receiving a SELECTEE status:
PDD:1
PDD: VV1010/14AUGYKBP,1
1. AQUA/ALAN BN005 SN32G Y JFK M1/84
APPB/SSSS/US SELECTEE VV1010226KBP005 US /600800000077828
DOCA-R/US //
DOCS-P /GBR/X4967689/GBR/29NOV64/M /29JAN09/AQUA/ALAN//
ACC VDT44215 AGT694/13AUG1609/SN32G
APP VDT44215 AGT694/13AUG1609/CIRQ/VV1010226KBP005
APP VDT44215 AGT694/13AUG1609/CIRS/5200
PU VDT44215 AGT694/13AUG1612/DOCA
PU VDT44215 AGT694/13AUG1612/APP
APP VDT44215 AGT694/13AUG1612/CIRS/US/8541/EPID600800000077828
Passenger Cancellation
A passenger may be deleted from an AQQ flight with a Cleared or Selectee status using the
PW entry.
Passenger being deleted from an AQQ flight:
_pw-1
_PW: XS123/26MARYKBP-1
AV C20Y202 PAD C0Y0
767/B GTD/???? POS/GATE BDT1830 SD1900 ED1900 SA2200 FT2100
1. DAVID/SIMON DELETED
US APP* (8505) CANCELLED/BN1
If the passenger being deleted is a No–Fly passenger, no response will be received upon
deletion of the passenger.
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:
n (For PA or PU) “Country Name APP Flight, 5 passenger maximum group size”.
n (For PW) ”Country Name APP Flight, 5 passenger maximum group size”.
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

Page 141
Note: Contact SITA Helpdesk staff to DFL any AQQ flight.
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.
'Normal' Check-in
Retrieve passenger to check-in:
PDD:01
PDD: XS475/21MARYYYZ,01
1. ACKERS/JUDY Y YVR
Check-in entry:
PA1,1/12,PSPT/B/22JUN70/ACKERS/JUDY
Response:
PA: XS475/21MARYYVR1,1/12,PSPT/B/22JUN70/ACKERS/JUDY
1. ACKERS/JUDY BN001 SN46G
PDD display:
PDD:01
PDD: XS475/21MARYYYZ,01
1. ACKERS/JUDY BN001 SN46G Y YVR OKT BAG1/12/0
PSPT-B/22JUN70/ACKERS/JUDY
ACC VDT2110 AGT877/21MAR1000/SN46G
Notes:
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.

Reserved.
Page 142
If the check-in does not involve an airport to or from a Watchlist country, then no codes are
attached to the passenger’s record even if they may be on the Watch List.
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.
'Selectee' Check-in
PDD:01
PDD: XS475/21MARYJFK,01
1. SMITH/CHARLES Y YYZ
Check-in entry:
PA1,0/0,PSPT/P/5902843/US/10SEP44/M/SMITH/CHARLES/10JAN10/US

Page 143
Response:
PA:
XS475/21MARYYYZ1,0/0,PSPT/P/5902843/US/10SEP44/M/SMITH/CHARLES/10JA
N10/US
1. SMITH/CHARLES BN002 SN37H
WARNING - WATCH LIST MATCH FOUND
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.
'No-Fly' Check-in:
PDD:01
1. BENIZAR/SAMMY Y YYZ
Check-in entry:
PA1,0/0,DOCS/P/US/92349532/US/09FEB67/M/09AUG10/BENIZAR/SAMMY

Reserved.
Page 144
Response:
PA:
XS475/21MARYYYZ1,0/0,DOCS/P/US/92349532/US/09FEB67/M/09AUG10/BENIZA
R/SAMMY
1. BENIZAR/SAMMY BN001 SN25D
WARNING - WATCH LIST MATCH FOUND
PDD display:
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 passenger’s 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.
Airline Undesirable Passenger List

Airlines send to SITA Open Systems the Airline Undesirable Passenger List in Excel format.
Format of Airline Passenger List
Note: This format must be strictly followed.
ID Last Name First Name Middle Name DOB Gender
4 Numeric 128 Alpha 128 Alpha 128 Alpha dd-mmm-yy 1 Alpha
1000 MOORE TIM 2-FEB-75 M
1001 SMITH SUSANNA 4-DEC-75 F
1002 LE MONTE PEPE JOHN 6-FEB-75 M
1003 JONES RICK 15-MAY-75 M
1004 FEES MIKE 2-AUG-75 M
1005 HUTCHINSON THOMAS PAUS 12-FEB-75 M

Page 145
ID Last Name First Name Middle Name DOB Gender
1006 KING JAMES 5-JAN-75 M
1007 SUNN LORI 19-AUG-75 F
1008 LE VAUGHN JIM 16-DEC-75 M
1009 KUHN KAREN 8-OCT-75 F
1010 ROWE STEPHANIE 20-SEP-75 F
1011 MILLER BOB 21-MAR-75 M
1012 ROBERTS TIM 13-JAN-75 M
1013 KING JOHN 31-JAN-75 M
1004 MUFLER RICK 27-OCT-75 M
1015 KING PAUL 31-JAN-75 M
Example
ID Last Name First Name Middle DOB Gender
1001 GRABLER RICHARD LEE 03-JAN-54 M
DSSW Parameter
The DSSW parameter, if activated, does a name check against the airline undesirable
passenger names.
DSSW =Controls if check-in performs a name check against the airline provided list.
Note: DOCS element will be use for name verification. If no DOCS are present no name
check will be performed.
0 = Does not check names against the DCS Watchlist.
1 = Checks names against the airline undesirable watchlist for all flights for this airline.
SDCS Updates Passenger List

SDCS receives the airline undesirable passenger list from open systems and processes the
list similar to the current process used to compile the US and Canadian Watchlists.
When the list has been processed the airline updated list of names is made available to DCS
Check-in Watchlist Query.
Note: The list is overlaid in the system so a complete list must be sent.

Reserved.
Page 146
SCW Watchlist Query
The current SCW query display is expanded to include the Airline’s list processing details.
SCW Latest Version

Example:
SCW:
Airline A NO FLY 2010-N1460 08-05-10(728)

Airline A SELECTEE 2010-S1429 08-05-10(729)
PPL 2010-P0506 07-28-10
XX NO FLY 2010-N0001 08-05-10
XX = Carrier two letter identifier.
The SCW Query includes in the query of the DCW Watchlist the containing airline provided
names.
Formatted Entry:
SCW:SURNAME/GIVEN NAME/GENDER/DOB
Example no match :
SCW:MUFLER/RICK/M/01JAN65
Response No Match
NO MATCH FOUND
Example Match.
SCW:BOND/JAMES/M/01JAN54

Page 147
Response Match
MATCHING NAMES FOUND

1. BOND/JAMES Airline code /01JAN2543/NNN
Multiple Watchlist Match

A situation could arise in which a Name Match is found for the same passenger name that
was included in the US or CA watchlist in addition to the Airline watchlist of names.. .
Example: BOMYUL
SCW:BOND/JAMES/M/01JAN54
Response Match
MATCHING NAMES FOUND

1. BOND/JAMES XX/01JAN1954/NNN
2. BOND/JAMES CA/01JAN1954/NNN
Note: Multiple match includes airline unique name list and a match on the US or CA list.
When several airlines have unique lists, only the airline requesting the SCW match displays.
At Check-in SDCS performs Watchlist Check against Airline Watchlist Names

There is no change to the current check-in process. The internal check is performed for the
name match against the Airline Watchlist, and if applicable, the US and CA list.
SDCS Updates Passenger Record

Example Normal Check In no Watch List found
1. Display Passenger to check in
PDD:3
PDD: Airline 8016/07AUGYAMM,3 PNR RL JASD3

1. CANE/BRANKO Y YYZ
DOCS-P /USA/304430147/USA/24MAR82/F /27JUN14/CANE/BRANKO//
2. Check-in Entry
PA1,1/10

Reserved.
Page 148
Response:
PA: Airline 8016/07AUGYAMMYYZ1,1/10

AV J18Y137 PAD J0Y0
1. CANE/BRANKO BN003 SN29A
RATE NOT FOUND. NO JCD TABLE ENTRY FOR THIS DESTINATION: YYZ
»EXB:1/SPCH/CASH/JOD0.0
3. PDD Display
pdd:1
PDD: Airline 8016/07AUGYAMM,1 PNR RL JASD3

1. CANE/BRANKO BN003 SN29A Y YYZ OKT BAG1/10/0
DOCS-P /USA/304430147/USA/24MAR82/F /27JUN14/CANE/BRANKO//
APPS US/RJ9017314CKI0022/
ACC VDT44215 AGT694/06AUG1716/SN29A
SCW VDT44215 AGT694/06AUG1716/Airline Code /OKT
Notes:
n The item OKT (OK to travel) is attached to the passenger record to identify that a check
was made and there was not match found for the passenger. The action cods SCW)
Security Checked Watch List) is also added to the history element.
n For passengers with and onward connection by ‘through” check-in, to a flight that involved
a Watch List airport then the same procedures apply to and onward flight. The 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 form checking on the Airline flight.
Example NO Fly check-in
1. Retrieve passenger to be checked-in:
pdd:4ps
PDD: RJ8016/07AUGYAMM,4PS PNR RL JAUD3
1. GANE/BRANKO Y YYZ
DOCS-P /USA/304430147/USA/24MAR82/F /27JUN14/GANE/BRANKO//
2. Check- in Entry:
PA:1,1/10

Page 149
Response:
PA: Airline 8016/07AUGYAMMYYZ1,1/10

AV J18Y136 PAD J0Y0
1. GANE/BRANKO
WARNING WATCH LIST MATCH FOUND
3. PDD Display:
PDD: Airline 8016/07AUGYAMM,1 PNR RL JAUD3
1. GANE/BRANKO BN004 SN28C Y YYZ NNN BAG1/10/0
ACC VDT44215 AGT694/06AUG1738/SN28C
SCW VDT44215 AGT694/06AUG1738/Airline Code/NNN
Note: The item ‘NNN” (NO Fly) is attached to the passenger‘s record to identify that a check
was made and a match was found on the Airline NO Fly list. The boarding pass is inhibited for
a NNN passenger. The action SCW is also added to the history element, along with the
date/time stamp of the Watch List that was reflected during the check-in process.
WPDD Display
The current WPDD display will not be affected by this enhancement and will display the SCW
information in History as it currently does for SWC of Watchlist today.
WPDD – Canadian Watchlist Flight
WPDD:1
WPDD: Airline 4243/03NOVYCUN,1

1. ABARA/JOSEPHMR BN001 SN11F Y YUL OKT BAG1/10/0 M1/80
F1/70
DOCS-P /US /349939339/US /01JAN65/M /01JAN11/ABARA/JOSEPH//
ABARA/KENDRAMRS BN002 SN11E Y YUL OKT
DOCS-P /US /349555339/US /01JAN65/F /01JAN11/ABARA/KENDRA//
PU VDT18990 AGT694/02NOV0716/DOCS
SCW VDT18990 AGT694/02NOV0716/P1/AI/OKT
PU VDT18990 AGT694/02NOV0717/P2/DOCS
ACC VDT18990 AGT694/02NOV0717/P1/SN11F
ACC VDT18990 AGT694/02NOV0717/P2/SN11E
Multiple Watchlist Match

If a flight travels to a country with a Watchlist CA or US, it is possible that multiple watchlist
checks could be present in the PDD Record.

Reserved.
Page 150
Example
PA: AI8016/07AUGYAMMYYZ1,1/10
AV J18Y136 PAD J0Y0
1. GANE/BRANKO
WARNING WATCH LIST MATCH FOUND
PDD Display:
PDD: AI8016/07AUGYAMM,1
1. GANE/BRANKO BN004 SN28C Y YYZ NNN BAG1/10/0

ACC VDT44215 AGT694/06AUG1738/SN28C
SCW VDT44215 AGT694/06AUG1738/Airline code/NNN
SCW VDT44215 AGT694/06AUG1738/CA/NNN
ITCI (Current Processing)

When the onward ITCI flight is going to an ITCI partner Watch list airport, and the check-in
process finds a name match on the ITCI flight, the check-in agent get he following response:
EDI*UNABLE TO CHECK-IN SECURTY PROFILE RESTRICTIONS
Note: The passenger is only checked-in on the local flight and will have to be checked-in
again at the connection point.
Boarding Process Airline Watchlist Match

There is no change to the current boarding process when a name is marked with NNN from
the Airline Watch List.
Attempt to board BN 04 (Passenger not cleared to travel)

Page 151
Response:
1. BOARDING NUMBER NOT ACCEPTED

BN REASON
04 WATCH-LIST MATCH
Flight Close Out

The current boarding pass warning that appears today when an attempt to close a flight for
check-in will be applied to name with a match against the Airline Watchlist if a passenger is
marked as NNN.
Example
CCL:Airline 80126
Response:
SECURITY LIST DISCREPANCY – CLOSING FLIGHT INHIBIT
1. GANE/BRANKO BN004 SN 28C Y YYZ NNN
To close the flight the passenger must be deleted or the current override entry
must be used.
The override is used for passengers that have been give security clearance to travel. Airline
will need to establish a process to provide an override.
Current process Override OVRW
In order to proceed the close out agent has two options:
1. PW:-1 to delete the passenger.
2. PU1, OVRW – override
Note:The OVRW is used for a passenger that has been given security clearance by Airline to
travel. The PDD record will be updated to record the action/PID number/Agent and time the
OVRW was completed.
3. Once the override is performed the print boarding pass entry needs to done BC:1
Passenger Updates – Current Processing

If any passenger updates, such as added PSPG or DOCS element, are entered or updated
after the passenger has been checked-in a new check against the Airline Watchlist is initiated.
If a match is found, the record is marked with NNN code even though the boarding card was
previously issued. When the PDD record is updated, the passenger boarding will be rejected.
Passenger Displays
The current display of passengers designated as NNN or OVRW codes will be expanded to
include NNN and ORVW passengers from the airline list.

Reserved.
Page 152
The current display of passengers designated as NNN or OVRW codes will be expanded to
include NNN and ORVW passengers from the Airline list.
PS Display
PDD:10
PDD: RJ8016/13AUGYAMM,10
1. RANCES/HMR BN001 SN27A Y YYZ OKT BAG1/10/0
FQTV/AF 3456789
DOCS-P /US /93939339/US /01JAN76/M /01JAN11/RANCES/HMR//
ACC VDT44215 AGT694/12AUG1512/SN27A
PU VDT44215 AGT694/12AUG1513/DOCS
SCW VDT44215 AGT694/12AUG1513/xx/NNN
PS:8016/+,NNN
»PS: RJ8016/13AUG AMM,NNN

OP/NAM
10. 1RANCES/HMR BN001 SN27A Y YYZ NNN FQTV DOCS
FPS Display
The current FPS display below does not have an indicator line in the FPS that shows the OKT
from the PDD Line.
Programs that screen scrape the PDD record will have to allow for the adding of the carrier
code in the OKT line of the PDD.
SCW VDT18990 AGT694/17NOV1017/P1/Airline Code/OKT

SCW VDT18990 AGT694/17NOV1017/P2/US/OKT
Example of current FPS for Canadian watchlist flight.

Page 153
PDD:1
PDD: Airline 4243/03NOVYCUN,1

1. ABARA/JOSEPHMR BN001 SN11F Y YUL OKT BAG1/10/0 M1/80
F1/70
ABARA/KENDRAMRS BN002 SN11E Y YUL OKT
PU VDT18990 AGT694/02NOV0716/DOCS
SCW VDT18990 AGT694/02NOV0716/US/P1/OKT
PU VDT18990 AGT694/02NOV0717/Airline /P2/DOCS
SCW VDT18990 AGT694/02NOV0717/P2/OKT
ACC VDT18990 AGT694/02NOV0717/P1/SN11F
ACC VDT18990 AGT694/02NOV0717/P2/SN11E
SCW VDT18990 AGT694/02NOV0717/US/P1/OKT
SCW VDT18990 AGT694/02NOV0717/Airline /P2/OKT
FPS:4443/+
ps:4243/+
FPS:Airline 4243 03NOV10 CUN

OP/NAM
AVL J20Y219 PAD J0Y0
EQP 310/GFAT GTD/???? POS/GATE BDT1830 SD1900 ED1900 SA2300

FT0200
SNM 001. ############################# ABARA
GVN 001. ***************************** JOSEPHMR
STA BN001 SN11F Y YUL
GND M
MSC BAG1/10/0
SNM 001. ABARA
GVN 002. ***************************** KENDRAMRS
STA BN002 SN11E Y YUL
GND F
END-OF-TRANSACTION

Reserved.
Page 154
ITCI
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.
Watchlist Query
A Watchlist 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.
List Version Search:
Enter Passenger Name:
SCW:
Response:
SCW x.x (List Version)
Name Search:
Enter Passenger Name, Last Name/First Name (No match found):
SCW:SABEL/RON
Response:
NO MATCH FOUND
Name Search, Last Name / First Name (Match found):

Enter Passenger Name:
SCW:BOND/JAMES

Page 155
Response:
MATCHING NAME FOUND

1. BOND/JAMES US/16NOV1543/NNN
2. BOND/JAMES US/16NOV1543/SSS
Boarding 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.
Assign flight to Boarding:
FDT:XS9016/17NOV
Attempt to Board BN12 (Passenger not cleared to travel):
BAB:12
Response:
1 BOARDING NUMBER NOT ACCEPTED

BN REASON
12 WATCH-LIST MATCH
Flight Close Out

There is a warning message that appears, similar to APP, when an attempt to close a flight for
check-in is applied and there are still some passengers marked as SSS or NNN on the
checked-in list.
Flight Close entry:
CCL:XS9016
Response:
SECURITY LIST DISCREPANCY – CLOSING FLIGHT INHIBIT
1. 1BAKER/PAMM+ BN85 SN22D Y BOS NNN

Reserved.
Page 156
To close flight, use one of the following options:
1. Delete passenger from flight
PW:-1
2. Use override entry (if passenger cleared to travel) after retrieving record (PDD:1)
PU1,OVRW
Notes:
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 passenger’s
PDD record.
After a passenger override, the boarding card must be printed. Enter BC:1 to print the
boarding card.
Passenger 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.
Passenger Displays (PS)

It is possible to display passengers by SSS, SSSS, NNN, or OVRW codes.
PS SSS List:
PS:XS123/20APR ATL,SSS OP/NAM

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

1. Watchlist shall show SSS for “Selectee”.
2. AQQ shall show SSSS for “Selectee”.
3. It is possible for SSS and SSSS to be on the same PS list.
Printing of Selectee Boarding Pass

An agent transaction is available for printing the Boarding pass for SELECTEEs who are
restricted due to the DSBP parameter set to “2” which imposes “Not to Print Boarding Pass
for SELECTEEs”
The entry to Print Boarding Passes for SELECTEEs is:

Page 157
BC:1,SSS
Or with a Passenger Select:
BC:1PN,SSS
where N is the item number of the passenger.
With the BC: 1, SSS boarding pass is printed.
PDD: 1
PDD: XS122/13JANYFRA,1
1. MINSA/ASTROBN009 SN40C S Y ATL OKT
APPB/SSSS/US SELECTEE XS0122013FRA009 US /600900000005540
DOCA-R/CAN//
DOCS-P /CAN/956284713/CAN/09JUN32/M /18MAY12/MINSA/ASTRO//
SCW VDT16911 AGT400/13JAN1607/OKT
APP VDT16911 AGT400/13JAN1607/CIRQ/XS0122013FRA009
APP VDT16911 AGT400/13JAN1607/CIRS/US/8567/EPID600900000005530
BC:1,SSS
516-BOARDING PASS RE-ISSUED
Boarding Pass Printing for ESTA SELECTEE.:

A SELECTEE with a 8569 response which implies ESTA not filed,reissuance of Boarding
pass is inhibited till the agent enters a PU:1, ESTA and then reissues the Boarding pass.
However, if the DSBP parameter is set to “2” i.e., “Not print the Boarding pass for
SELECTEE “when the agent attempts a BC: 1 after the PU: 1, ESTA it displays an error:
UNABLE”. The boarding pass is reissued with the new entry BC: 1, SSS.

Reserved.
Page 158
Same processing for the response ‘8570’:
1. VOLKER/ROBERTBN008 SN12AY ATL OKT
APPB/SSSS/US SELECTEE/ESTA XS0122013FRA008 US /600900000005537
DOCA-R/NOR/
DOCS-P /NOR/456321789/NOR/07JUL55/M /21SEP12/VOLKER/ROBERT//
BC: 1
409 - PAX STATUS CONFLICT
»pu1, ESTA
»PU: XS122/13JANYFRAATL1,ESTA
AV F12C35Y241PAD F0C0Y0
340/312 GTD/???? POS/GATE BDT1500 SD1530 ED2230 SA1715 FT0045
1. VOLKER/ROBERTBN008 SN39H
»BC: 1
UNABLE
»BC:1,SSS
516 – BOARDING PASS REISSUED
Note: The APPB/SSSS/US SELECTEE will key off the reissuance of boarding pass for
SELECTEE using a BC: 1, SSS and not BC: 1 subject to the condition that the DSBP
parameter is set to ‘2’.

Page 159
PDD Update
The PDD record of the passenger is updated with the BC:1,SSS transaction.
PDD: 1
1. MINSA/ASTROBN009 SN40C S Y ATL OKT
APPB/SSSS/US SELECTEE XS0122013FRA009 US /600900000005540
DOCA-R/CAN//
DOCS-P /CAN/956284713/CAN/09JUN32/M /18MAY12/MINSA/ASTRO//
BC VDT13061 AGT400/13JUN1607/SSS
Error Response
The system checks for the highlighted SELECTEE status in the PDD as below;
‘APPB/SSSS/US SELECTEE XS0122013FRA009 US /600900000005540’
If the above status exists then the BC: 1, SSS gets processed.
If the above SELECTEE status does not exist in the PDD and the agent attempts to do a BC:
1, SSS the system displays an error message: ‘UNABLE-PAX NOT SELECTEE’.
Note: AQQ Interactive Watchlist has precedence over the Normal Watchlist (SCW) with the
exception of the Canadian government where the SCW holds equal importance as the
interactive watchlist.

Reserved.
Page 160
Special Service/Information Codes
The following Special Service and information codes can be input with the check-in entry:
Special Service /
Explanation
Information Codes
ADSR Adjacent/courtesy seat reserve request.
ASVC Additional Services, segment associated
AVIH (P/W) Live animal in the hold.
BIKE Bicycle
BLND Blind passenger.
BSCT (NBR) Bassinet request for infant.
BULK Bulky baggage
CHD (NBR) Child gender indicator.
CKIN Airport check in (no reply)
COUR Courier.
DBI Denied Boarding Involuntary (PU and PW entries only).
DBV Denied Boarding Voluntary (PU and PW entries only).
DCRW Deadhead crew
DEAF Deaf passenger.
DEPA Deportee accompanied
DEPU Deportee unaccompanied
DIPL Diplomatic Courier
DPNA Disabled Passenger Needs Assistance
EMIG Emigrant
EPAY Electronic payment authorization for travel
ETLP Electronic Ticketless List of Passengers

SSR ETLP is non AIRIMP standard and is available for host
bookings only.

Page 161
Special Service /
Explanation
Information Codes
EXST Extra seat request.
F (NBR) Female gender indicator.
FOID Form of Identification for Electronic Ticket Passengers.
FQTV Frequent flier number.
FRAG Fragile baggage
GPST Group seat request
ID Airline staff indicator followed by status code.
INAD Inadmissible passenger
INF (NBR) Infant gender indicator followed by name.
JMP Jump-seat passenger.
LANG Specify language spoken
LEGL/LEGR/LEGB Legs in cast
M (NBR) Male gender indicator.
MAAS Meet and assist
MEDA Medical case/situation
MSG Message indicator followed by text.
MUS (WT) Extra seat for musical instrument.
NAM (NBR) Re-name passenger code followed by new name.
O Oncarriage with flight, class, date and destination.
OXYG Oxygen
PAID Paid seat
PCTC Personal contact (Telephone contact as may be required.)
PETC (P/W) Live pet in the cabin.
PPOC Personal portable oxygen concentrator

Reserved.
Page 162
Special Service /
Explanation
Information Codes
PSM Passenger service message indicator followed by /text.
PSPT Passport information (APIS functionality).
R 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.
SLPR Sleeper berth
SPEQ Sports equipment
STCR Stretcher passenger indicator.
SVC Additional services-Non segmental
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).
TVOW Transit without Visa
UM Unaccompanied minor indicator.
URES Unbooked passenger indicator.
VIP Very Important passenger
WCBD Wheelchair (Dry Cell Battery)
WCBW Wheelchair (Wet Cell Battery)
WCMP Wheelchair (Manual Power)
WCOB Wheelchair (On Board)
WCHR Wheelchair passenger to gate (ramp).

Page 163
Special Service /
Explanation
Information Codes
WCHS Wheelchair to aircraft door (needed for stairs).
WCHC Wheelchair to aircraft seat (passenger cannot walk).
XBP Inhibit boarding card issuance.
Z Recheck passenger to another flight.
(P/W) Pieces/Weight required.
(NBR) Number required.
(WT) Weight required.
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

Reserved.
Page 164
Response to PS:XS227,GRP:
PS:XS227/08JUNATL,GRP OP/NAM
767/A GTD/A7 POS/GATE BTD/0930 SD1000 ED1000 SA1105 FT0105
1.0FOOTBALLTEAM E15 GROUP Y JFK
2.0GOLFTEAM P5 GROUP C JFK
3.0HOLIDAY TOUR G25 GROUP Y JFK
1 2 3 4 5 6 7
Field Description
1 List entry number.
2 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.
3 Name of the group. This display does not list the name of the passengers in the
group, only the group name.
4 Group identifier followed by the number in the group. This group identifier comes
from the PNL.
5 This identifies the entry as a group display.
6 Class of travel the group is booked in.
7 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)
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 165
Response to PS:XS227 ,GRI J:
PS:XS227/08JUNXATL,GRIJ OP/NAM
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.
Entry:
PS:FLIGHT,GRI(GROUP IDENTIFIER),NGRP
PS:XS227,GRIJ,NGRP
Response:
PS:XS227/08JUNATL,GRIJ,NGRP OP/NAM
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.

Reserved.
Page 166
Entry Description
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.
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).
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.
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 M1/78 F1/68
3. SMITHSON/MRS K2 Y MIA
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.
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.

Page 167
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.
NOREC Passenger:
PDD:XS679/28JULYATL,1
1. SMITH/D SB016 LMTS Y MIA NREC M1/78 BAG1/10/0
SBY VDT2967 AGT296/28JUL0815
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.
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.
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
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:

Reserved.
Page 168
PA:FLIGHT CLASS NBR NAME,GENDER,P/W,ID CODE,URES
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).
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
PDD Display with the ID and the seniority date with the year:
PDD: 1
PDD: MH1010/25AUGYKUL,1
1. ALPHA Y SIN IDID00S1-31OCT 98
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.
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.

Page 169
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:
PA:XS679Y1JAMES/MRS,F1,1/9,OBA292YLHR,URES

Reserved.
Page 170
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
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:
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:
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:

Page 171
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:
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.
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
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
SB:XS735

Reserved.
Page 172
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, enter: NO:<ENTRY NUMBER>.
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 173
Reserved.
Page 174
9. Passenger Acceptance: Associated Handling
Transactions
The associated passenger handling transactions that allow staff to check-in passengers are
described in this section. Other passenger acceptance check-in information is contained in
the following sections:
Description Section
Passenger Acceptance Passenger Acceptance: Check-in
Interline Thru Check-in ITCI Passenger Handling Procedures
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.
Check-in entry of a URES extra crew member:
PA:XS394 C 1XXXCREW,F1,0/0,URES
Notes:
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.
XXXCREW and XXXDHC can be entered with the surname, e.g., XXXCREW/JONES.

9. Passenger Acceptance: Associated Handling Transactions
Page 175
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.
Check-in entry of a URES dead heading crew member
PA:XS394 C 1XXXDHC,M1,1/10,URES
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.
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
Response without Bag Tags: PU:XS100YMEX0,2/30:
PU:XS100/02AUGYMEX0,2/30
AV F14Y58 PAD F0Y0
DC9/A GTD/???? POS/GATE BDT1930 SD2000 ED2000 SA2000 FT0200
2 UNATTACHED BAGS ADDED
The entry to check in and assign bag tags is:
PU:FLIGHT CLASS DEST 0,P/W,B/DEST
Response with Automated Bag Tags:
PU:XS100YMEX0,2/20,B/MEX
PU: XS100/24OCTYMEX0,2/20,B/MEX
AV C9Y93 PAD C0Y0
2 UNATTACHED BAGS ADDED
The entry to check in with manual bag tags is:
PU:FLIGHT CLASS DEST 0,P/W,B/DEST/XS1234567

Reserved.
Page 176
Response with Manual Tags:PUXS100YMEX0,1/10,B/MEX/XS1234321:
PU: XS100/25OCTYMEX0,1/10,B/MEX/XS1234321
AV C36M114 PAD C0M0
DC9/A GTD/???? POS/GATE BDT2315 SD2345 ED2345 SA0
Note: The actual class must be specified.
Display Unattached Bags

It is possible to display a list of the unattached bags on a flight.
The entry is: PDD:FLIGHT ,0
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
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
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).

Page 177
Response: PW:XS100YMEX0,1/10:
PW:XS100/02AUGYMEX0,1/10
AV F14Y58 PAD F0Y0
UNATTACHED BAGS DELETED
To delete bags by bag position: enter the following:

PW:XS100YMEX0,1/10,B/1
Note: If there are several unattached bags with bag tags listed, then 1 applies to the first
listed, 2 to the second, etc.
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
Response: PWXS100MMEX0,1/10,B/0182050217:
PW: XS100/24OCTMMEX0,1/10,B/0182050217
AV C36M110 PAD C0M0
DC9/A GTD/???? POS/GATE BDT2315 SD2345 ED2345 SA0030+1 FT0045
1 UNATTACHED BAGS DELETED
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.
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.

Reserved.
Page 178
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.
EXP:D
EXP: Expedite Bag Screen
Pieces/Weight 0 /0
Origin/Date BUD/17JUN06
Passenger Last/First Name /
Flight/Date / 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.
EXP:D
After the initial EXP:D entry, it is possible to select and update baggage details associated
with a specific entry number.
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.
Deleting / Changing Onward Connections

There are two different procedures for deleting onward connections:
1. Before Check-in
2. After Check-in

Page 179
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'.
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.
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).
Boarding Pass Issuance / Inheritance (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:
n Excess baggage charges are applied the response shows the amount of excess bag
charges to be assessed with the comment BOARDING PASS PRINT INHIBITED.
n API data is required and is not complete the response is BOARDING CARD INHIBITED
MISSING DOCUMENT DATA.

Reserved.
Page 180
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.
Boarding Pass Inhibit

To Inhibit the Boarding Card from printing at check-in completion, add the item XBP to the
check-in entry:
PA:XS829Y1BARNETT/MRS,F1,1/15,WCHR,XBP

Page 181
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:
n 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.
n 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).
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. 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.
Note: The charge has to be accepted by transmitting after the 65; otherwise, the excess
amount is not recorded in the excess baggage statistics.
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.

Reserved.
Page 182
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
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.
PDD:XS639Y,BN031
Response PDD:XS639Y,BN031:
PDD:XS639/22JUNYMIA,BN031
1. GRAHAM/FMR BN031 SN12F S Y MIA BAG2/25/0
2. 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/:
EXB:1/5KG/CASH/USD65
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).
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:
EXB:1/5KG/CASH/USD65 <Transmit>

Page 183
Response to EXB:1/5KG/CASH/USD65:
CHARGE ACCEPTED
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'.
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.
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:
n B to print the Bag Tag.
n 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.
n Bag Tag number, to allow the agent to input a manual Bag Tag.
n If a manual Bag Tag is input in a passengers record, destination is a mandatory field.
n A bag can be marked “hot” for baggage with close connecting times or other airline
reasons.
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

Reserved.
Page 184
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
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 Response
If no baggage is input with the PA transaction, the previous options are not allowed and a
'FORMAT' rejection message displays.
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.
Update passenger record, issue no Bag Tags.
►PU:1,1/10

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

Reserved.
Page 186
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 SN10D Y

MIA TKNA/XS/0952485629412C1 BAG1/10/0 F1/75 BAGTAGS ISSUED: ATL 1/10
0182938473/MIA *0182938472/MIA ACC VDT27236 AGT97/16JUN1026 PU
VDT27236 AGT97/16JUN1029/BAG
Error Response
If no baggage is input with the PU transaction, the previous options are inhibited and a
'FORMAT' rejection message displays.
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.
►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.
Deleted Bag Tag Number to GQ:
ATL501 GENERAL MSG (0001)

BAG TAG DELETED
XS 0700 17SEP ATL
ABBA BN1
VDT11290 AGT295/17SEP1329
0182526828

Page 187
Displaying Any Deleted Bag Tags in a Passenger’s 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>
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 ***
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.

Reserved.
Page 188
Error Message Explanation
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.
Bag Tag Subsequent Processing

The generated Bag Tag numbers are stored in the passenger's PDD record.
PDD with Bag Tag Numbers
PDD: XS735/08JUNCATL,2 PNR RL H522T

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

Explanation of Bag Tag Number:
Position Explanation
1st digit 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).

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

Reserved.
Page 190
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.
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:
n 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.
n 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.
n 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.
n 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.
n 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.
n 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.
n Only MSG, PSM, URES, XRES, SNR, RQST, JMP, INF, BSCT, are allowed after an O
item.
n The PU transaction can be used to recheck passengers short of their original destination
on the same flight; e.g.; PU:ENTRY,Z FLT CLS NEW DEST.
n When a valid seat has been assigned during check-in for WCHR, UNMR and INF the PU
entry to add a WCHR, UNMR or INF will retain the previously assigned seat if that
previously assigned seat was a valid seat.

Page 191
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. For example:
PA:#1-4,R17A-D.
5. Add Oncarriage details to a checked-in passenger:
PU:1,OIB735MLIS
6. Add a marketing segment to a passenger’s 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
PU:1,SNR17A/ATLMIA
Note: Remember to use SNR when requesting the new seat. If R is used, the system
responds: 'MODIFICATION NOT POSSIBLE'.

Reserved.
Page 192
9. Add a passport to passenger Lauren Wells after checking her in:
PU1,PSPT/A12345/US/16DEC71/F/WELLS/LAUREN/19OCT05/US
10. Check in passenger Lauren Wells on a connecting segment after checking in on the first
flight only:
PU1,O
PU1,O FLT NBR/DATE CLASS DEST
11. Add a double oncarriage segment to a passengers record after check-in:

PU1,OXS113YLHR
12.Add denied boarding voluntary remarks to a passenger's record after check-in:
PU1,DBV/PASSENGER REBOOKED XS111
13. Add denied boarding involuntary remarks to passengers record after check-in:
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:
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 193
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, refer to Checking In Passengers on a Connecting Flight.
PW transactions are:
1. Offload one entry number or a range of entry numbers:
PW:-ENTRY NUMBER
PW:-ENTRY NBR-ENTRY NUMBER
PW:-3
PW:-3-6
2. Delete some baggage (1/10) from a checked-in passenger:
PW:1,1/10
3. Delete item MSG from a checked-in passenger:
PW:1,MSG
4.Offload one checked-in passenger from a group with no bags:
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
PW:100Y - SN17A

Reserved.
Page 194
6.Cancel check-in on down line flight segment from a passenger's record:
PW1,O
7. Delete a passport from one or all passengers record:
PW1,PSPT/ALL
8. Delete a passport from passengers one and three in a record:
PW1,PSPT/1/3
9.Delete a passport from a single passenger record:
PW1,PSPT/1
10. Delete a marketing segment from a passenger's record:
PW1,MKT
11. Delete an infant from a passenger's record:
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:
PW-1P2,M1,3/30,B/ALL
13. Delete the second person in a party of four and the first bag in the record:
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.
n To delete special meal: PW1,VGML
n To delete wheelchair: PW1,WCHR
n To delete passenger on all flights: PW-1
n To delete the onward flight: PW1,O,XRES

Page 195
A new onward flight, e.g., A1,1/12,OYZ837YGLA,URES can be added. It is important to add
the URES after the onward flight; otherwise the system responds "Transfer Status Conflict".
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.
If the entry is successful it displays on the screen. If unsuccessful, a
warning or error message displays.

Reserved.
Page 196
10. Passenger Acceptance: ITCI Passenger Handling
Procedures
The ITCI (Interline Thru Check-in) passenger handling procedures are described in this
section. Other passenger acceptance information is contained in the following sections:
Description Section
Passenger acceptance Passenger Acceptance: Check-in
Associated passenger handling Passenger Acceptance: Associated Passenger Handling

transactions
The ITCI topics described in this section include:
n Passenger Acceptance (PA)
n Passenger Update (PU)
n Passenger Delete (PW)
n Standby Check-in (URES/NOREC)
n Boarding Card Re-Issue (BC)
n Passenger Record Display (PDD)
n Seat Map Display (SE)
Interline Local Check-in (ILCI) is permitted using ITCI messaging; thus, allowing the
marketing carrier to check-in customers on the operating flight. SITA Departure Control
Services will send an ITCI request to the operating carrier if an ITCI agreement exists with the
operating carrier flight number in the request. This conforms with IATA Recommended
Practice 1708: If the onward connection is for a code share flight, display the operating carrier
and flight number.
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.

10. Passenger Acceptance: ITCI Passenger Handling Procedures
Page 197
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:
n ADSR
n COUR
n EXST
n ID2
n JMP
n MUS
n 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:
n CHD
n INF
n BLND
n SCST
n DEAF
n DOCO
n DOCA
n EXBG
n ESAN
n FQTV
n SDML
n SVAN
n PETC
n PRML
n TKNA
n TKNE
n TKNO
n UMNR
n WCBL
n 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.

Reserved.
Page 198
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.
A 'Normal Response' when 'THRU CHECK-IN' is attempted.
Display passenger PDD:
Check-in with 1/12 baggage:
PA:1,1/12,O
Response:
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.
At this stage the check-in transaction is complete.

A 'Time Out Response' when 'THRU CHECK-IN' is attempted.
PA:1,1/12,O

Page 199
Response:
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.
An 'Error/WARNING Response' when 'THRU CHECK-IN' is attempted.
PA:1,1/12,O
Response:
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.

Reserved.
Page 200
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
I Aisle Seat.
E Exit Seat.
F Front Seat.
H Bulkhead Seat.
X Legroom Seat.
L Left Seat.
R Right Seat.
Q Quiet Zone.
S Smoking Seat.
N Non Smoking Seat.
W Window Seat.
M Movie Seat.
C Center Seat.
U Upper Deck Seat.
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
PA:1,2/15,R11A,O,RW

Page 201
Response:
PA:XS378/01MARYATL,2/15,R11A,O,RW
AV F10Y44 PAD F0Y2
D10/A GTD/B24 POS/GATE BTD/0930 SD1000 ED1000
SA2305 FT0805
1. GRANT/DMR BN069 SN11A O
O/YY827/02MAR Y MAN
« EDIFACT » THRU CHECK-IN IN PROGRESS FOR FLIGHT
YY827/02MAR/Y/LHRMAN
« TRANSFER » LHR YY827/02MAR MAN
1. GRANT/DMR BN010 SN23A
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 the onward Airline. The transaction will either be
accepted or rejected with an error or warning response.
Passenger Update (PU)

PU Processing
The passenger acceptance transaction is same as 'THRU CHECK-IN' procedures, only the
'RESPONSES' are different.
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:
n Passengers with EXTRA seats (COUR, EXST, MUS, STCR) are not allowed.
n Passenger in JMP seat is not allowed.
n ITCI is attempted on the first onward connection in the passenger record only.
n 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.
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.

Reserved.
Page 202
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
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.
A 'Normal Response' when a 'PU' is Attempted
PDD: XS378/01MARYATL,1 PNR RL H522T

1. COOPER/CMR BN023 SN10C Y LHR
BAG1/12/0 M1/77
O/YY827/02MAR BN009 SN06D Y MAN
BAGTAGS ISSUED:
0182526553
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
FT0805
1. COOPER/CMR BN065 SN10C
« EDIFACT »UPDATE IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
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
FT0805
« TRANSFER» LHR YY827/02MAR MAN
1. COOPER/CMR BN012 SN06D
At this stage the passenger update is complete and no further action is required.

Page 203
A 'Time Out Response' when a 'PU' is Attempted

BAG1/12/0 M1/77
BAGTAGS ISSUED:
0182526553
Update passenger COOPER with item WCHR: PU:1,WCHR

Response:
PU: XS378/01MARYATL,1,WCHR OP/NAM

AV F10Y36
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.
An 'Error/Warning Response' when 'PU' is Attempted.
Display passenger PDD:1:

BAG1/12/0 M1/77
BAGTAGS ISSUED:
0182526553

Reserved.
Page 204
Update passenger COOPER with item WCHR: PU:1,WCHR.
Response:
PU: XS378/01MARYATL,1,WCH OP/NAM

AV F10Y36
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.
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.
Entry:
PU:1,O,R6F

Page 205
Response:
PU:XS378/01MARYATL,O,R6F OP/NAM
AV F10Y44 PAD F0Y2
D10/A GTD/B24 POS/GATE BTD/0930 SD1000 ED1000 SA2305
FT0805
O/YY827/02JMAR BN010 SN06A Y
MAN
« EDIFACT » UPDATE IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
1. GRANT/DMR BN010 SN6F
Passenger Delete (PW)

PW Input
The passenger delete transactions for 'THRU CHECK-IN' passengers are the same as 'PW'
procedures except some of the 'RESPONSES' are different.
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:
n Only one passenger 'entry number' can be deleted in the same transaction.
n A 'NOT CHECKED-IN' passenger cannot be deleted.
n When deleting items, the items must be associated with the passenger, and the counts
and weights cannot exceed the original value of the items.
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.
A 'Normal Response' when a 'PW' for a Passenger’s Item is Attempted

Reserved.
Page 206
PDD: XS378/01MARYATL,1 PNR RL H681G
1. HARRIS/CMR BN015 SN22F Y LHR BAG1/12/0
M1/77
SPML-ORML
O/YY827/02MAR BN004 SN22F Y MAN
BAGTAGS ISSUED:
0182526567
Delete item SPML from passenger HARRIS:
PW:1,SPML

Page 207
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
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
A 'Time Out Response' when a 'PW' for a Passenger’s Item is Attempted.
PDD: XS378/01MARYATL,1 PNR RL H681G

1. HARRIS/C/MR BN015 SN18F Y LHR BAG2/22/0 M1/77
WCHR
BAGTAGS ISSUED:
0182526567 0182526568
Delete item WCHR:
PW:1,WCHR

Reserved.
Page 208
Response:
PW: XS378/01MARYATL,1,WCHR OP/NAM

AV F10Y36
1. HARRIS/C/MR BN015 SN18F
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.
An 'Error/Warning Response' when a 'PW' for a Passenger’s Item is Attempted:
PDD: XS378/01MARJUNYATL,1 PNR RL H681G

1. HARRIS/C/MR BN015 SN18F Y LHR BAG2/20/0 M1/77
BAGTAGS ISSUED:
0182526567 0182526568
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
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 209
A 'Normal Response' when a 'PW' is Used to Delete a Passenger on the Onward Flight
Only
PDD: XS378/01MARYATL,1 PNR RL H847I

1. MORRIS/FMRS BN049 SN14A Y LHR BAG1/12/0
F1/65
BAGTAGS ISSUED:
0182526567
Delete onward flight from Passenger MORRIS:
PW:1,0
Response:
PW XS378/01MARYATL,1,O OP/NAM
AV F060Y22
1. MORRIS/FMRS BN049 SN14A
« EDIFACT »DELETION IN PROGRESS FOR 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
1. MORRIS/FMRS DELETED

Reserved.
Page 210
A 'Normal Response' when a 'PW' is Used to Completely Delete a Passenger from both
Flights

1. MORRIS/FMRS BN049 SN14A Y LHR BAG1/12/0
F1/65
BAGTAGS ISSUED:
0182526567
Delete passenger MORRIS:
PW:-1
Response:
PW XS378/01MARYATL,1, OP/NAM
AV F060Y22
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
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.

Page 211
A 'Normal Response' when a 'PW' is used to Delete an Onward Flight Before and After
Check-In:
Before Check-In

1. PHILIPS/MR Y LHR M1/77
O/YY827/02MAR Y MAN
Delete the onward before check-in:
PW:#1,O,XRES
Response:

1. PHILIPS/MR Y LHR 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:

1. PHILIPS/MR BN055 SN19K Y LHR 1/12/0 M1/77
O/YY827/02MAR Y MAN
BAGTAGS ISSUED:
0182526583
Delete the onward:
PW:1,O,XRES
Response:

1. PHILIPS/MR BN055 SN19K Y LHR 1/12/0 M1/77
BAGTAGS ISSUED:
0182526583
It is then possible to add a new onward flight, if required, with the PU entry
(PU:1,OYZ837YGLA).

Reserved.
Page 212
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.’
Standby Check-in (URES/NOREC/ID)

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

Page 213
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.
ID Check-in
There are two types of ID passengers:
n ID1
n 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.
Interline Local Check-in (Onward Connection)

Onward Connection: At Check-in
When checking in a passenger with an onward online connection (host flight number),
SITA Departure Control Services will check if parameter URTCIF is set to 1, which indicates
an ITCI request will be sent to the operating carrier. The processing is as follows:
n The system will determine if it is a code share and retrieve the operating carrier and flight
number.
n If it is a code share and the host has an ITCI agreement with the operating carrier,
SITA Departure Control Services will send an ITCI request to check-in the passenger on
the flight.
n If there is not an ITCI agreement, the passenger is not checked-in for the online marketing
connecting flight.
n If there are additional connecting flight, the ITCI agreements are checked to determine if
the passenger is allowed to be checked-in and an ITCI request sent.
Onward flight in passenger record:
PA:1,OA5678/24AUGDEN
NOREC check-in with onward connection:

PA:XS1234/23AUGYLAX1LASTNAME/FIRSTNAME,1/10,M1,OAI5678/24AUGDEN
URES check-in with onward connection:

PA:XS1234/23AUGYLAX1LASTNAME/FIRSTNAME,1/10,OAI5678/+DEN,URES

Reserved.
Page 214
URES / NOREC on connecting segment:
PA:1,0/0,OAI5678/24AUGDEN,URES
Response to all of the above entries:
If the URTCIF parameter is set to 1, AI5678 is a code-share marketing flight, and an ITCI
bilateral agreement exists between the host and the operating carrier, then an ITCI Request
Message is sent to the operating carrier in an attempt to check in the passenger. The
following response is displayed to the agent while waiting for the response from operating
carrier:
If the operating carrier does not find the passenger's reservation on the connecting flight, the
passenger will not be checked-in to the connection on the operator's side. If the passenger
cannot be checked-in to the connecting flight, the agent receives the following response:
EDI*PASSENGER SURNAME NOT FOUND
EDI* FURTHER PROCESSING INHIBITED
Onward Connection: After Check-in

If the onward connection to a host marketed code share flight is added to the passenger
record after check-in, SITA Departure Control Services will follow the same process defined
in the Check-in sub-section.
PU1,OAI5678YDEN
Response:
If parameter URTCIF is set to 1 and an ITCI agreement exists between host and operating
carriers:

Page 215
Onward Connection: Before Check-in
The agent may be able to update the passenger record with the connecting flight information
using the PU not present option. In this case, no check for the onward connecting flight will be
made until the passenger is checked-in with the onward connection.
PU#1,OAI5678/23AUGYDEN
Response:
Onward Connection: Delete

If the onward connection is to a host marketed code share flight, SITA Departure Control
Services will send a check-in cancellation message to the operating carrier.
PU:1,0
Response:
Upon receipt of the response to the ITCI cancellation message, the system responds as
follows:

Reserved.
Page 216
EDIFACT message:
PNL with connections to host marketed code share flights:

Page 217
Printing Operating Carrier on Bag Tag for Code Share Flight
For outbound connections to a code share flight, SITA Departure Control Services will print
the operating carrier instead of the marketing carrier on the bag tag(s). The system will
retrieve the operating flight information prior to printing the bag tags for the onward operating
flight as follows:
n If bag tags are requested for an onward online connecting flight, SDCS will determine if
the onward online flight is a code share marketing flight before printing the bag tags.
n If it is a code share marketing flight, SDCS will print the actual operating carrier and flight
number on the bag tag. SDCS will send the operating flight retrieved in the data stream to
the bag tag printer for any connecting flight that is a code share marketing flight.
n If bags are checked to additional connecting flight, the same process will apply.
Onward flight in passenger record:

When checking in a passenger with connecting segments, the 'O' (or O2, O3, etc.) indicates
to also check-in to the onward segment.
Connecting flight YX0412 is a code share marketing flight and the operating flight is F9 0412.
SDCS will send flight F9 0412 in the data stream.

Reserved.
Page 218
Bags may be checked to the onward connection without checking the passenger through
to the onward flight.
PA1,1/12,B/DEN
If the passenger is on the PS List but does not have outbound flight information in the check-in
record, the agent can add the outbound segment manually with the check-in entry or with the
PU option.
Onward flight with bags added to check-in entry:
PA:1,1/25,B/DEN,OYX0412/24JULYDEN
Bags added after check-in:

If bags are added after check-in and the passenger has onward connections, the bags will be
checked to the onward destination.
PU:1,B
NOREC passenger check-in:

PA:XS6003/23JULYLAX1NAME/FIRST,1/10,M1,B/DEN,OYX0412/24JULYDEN

Page 219
Bags not checked to onward destination:
PA:1,1/15,B/LAX
URES and NOREC Passengers

The following sections explain the difference between a URES and a NOREC passenger.
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.
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.

Reserved.
Page 220
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.
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.
Passenger Record Display (PDD)

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.
Entry (after a previous PS list):
PDD:ENTRY NBR,O
PDD:1,O
The response is:
PDD:XS378/01MARYATL,1,O PNR RL H337F
1. GIBSON/IAN BN008 SN03D Y LHR BAG1/10/0
M1/77O/YY827/02MAR
BN026 SN05C Y MAN
BAGTAGS ISSUED:
0182526661
« EDIFACT »PROCESSING IN PROGRESS
If the entry is successful, an example response could be:

Page 221
PDD:XS378/01MARYATL,1,O PNR RL H337F
1. GIBSON/IAN BN008 SN03D Y LHR
BAG1/10/0 M1/77
O/YY827/02MAR BN026 SN05C Y MAN
BAGTAGS ISSUED:
0182526661
« EDIFACT »PROCESSING IN PROGRESS
« TRANSFER»LHR YY827/02MAR MAN
1. GIBSON/IAN BN026 SN05C
If the entry is not successful, then a corresponding Error or Warning message is returned to
the screen.
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/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 Y LHR M1/77
O/YY827/02MAR Y MAN
NO THRU EDIFACT ATTEMPTED
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:

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

Reserved.
Page 222
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
Entry:
SE:YY827/+LHRMAN
The response is:
EDIFACT »SEAT MAP REQUEST SENT FOR FLIGHT YY827/02MAR/LHRMAN
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 = S = = = = E E = = = = S S S S S S R
LC .R F F . R . * * . * . * . . . * * . FR
LB * * E E . * * * * * * * . * * . * * ER
LA * R D D . * . . * * R * * * . * * * . * DR
F Y [ [ [ 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.
ITCI Documentation Check

For instances where an Online flight connection is to a United States city, the airline
parameter APCI can be set to verify that all required documents for Non-US Citizens are
present before proceeding with an ITCI check-in request. If all required information is present
the ITCI check-in request proceeds normally. If there is information missing one of the
following responses is shown:

Page 223
Details in Passenger Record Response
DOCS missing Passport/ID Data Required
DOCA "D" missing Destination Address Required
DOCA "R" missing Country of Residence Required
DOCS "P" and DOCA "D" missing Passport/ID Data Required
DOCS "P" and DOCA "R" missing Passport/ID Data Required
DOCS "P", DOCA "D" and DOCA "R" missing Passport/ID Data Required
DOCA "D" and DOCA "R" missing Destination Address Required
Note:
ITCI check in for US citizens will also be inhibited if DOCS is not present in their passenger
record.

Reserved.
Page 224
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:
n ADSR
n COUR
n EXST
n ID2
n JMP
n MUS
n 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:
n CHD
n INF
n BLND
n SCST
n DEAF
n DOCO
n DOCA
n EXBG
n ESAN
n FQTV
n SDML
n SVAN
n PETC
n PRML
n TKNA
n TKNE
n TKNO
n UMNR
n WCBL
n 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.

Page 225
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
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.
A 'Normal Response' when 'THRU CHECK-IN' is attempted.
PA:1,1/12,O
Response:
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.
At this stage the check-in transaction is complete.

A 'Time Out Response' when 'THRU CHECK-IN' is attempted.
PA:1,1/12,O

Reserved.
Page 226
Response:
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.
An 'Error/WARNING Response' when 'THRU CHECK-IN' is attempted.
PA:1,1/12,O
Response:
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 227
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
I Aisle Seat.
E Exit Seat.
F Front Seat.
H Bulkhead Seat.
X Legroom Seat.
L Left Seat.
R Right Seat.
Q Quiet Zone.
S Smoking Seat.
N Non Smoking Seat.
W Window Seat.
M Movie Seat.
C Center Seat.
U Upper Deck Seat.
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
PA:1,2/15,R11A,O,RW

Reserved.
Page 228
Response:
PA:XS378/01MARYATL,2/15,R11A,O,RW
AV F10Y44 PAD F0Y2
D10/A GTD/B24 POS/GATE BTD/0930 SD1000 ED1000
SA2305 FT0805
O/YY827/02MAR Y MAN
« EDIFACT » THRU CHECK-IN IN PROGRESS FOR FLIGHT
YY827/02MAR/Y/LHRMAN
1. GRANT/DMR BN010 SN23A
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 the onward Airline. The transaction will either be
accepted or rejected with an error or warning response.

Page 229
Reserved.
Page 230
11. Electronic Ticket Check-In
For information on Electronic Ticket Check-In, refer to the SITA Ticketing Subscriber Guide.
See the following chapters:
n Electronic Ticket Record (ETR) and Agent Action Options
n Check-In Electronic Tickets

Page 231
Reserved.
Page 232
12. 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 BOOKED WAITLISTED UNBOOKED

CODE PRIORITY PRIORITY PRIORITY
------------- -------- ---------- ---------
REVENUE 1 3 7
S1/ 2 6 # 10
RI 4 8 # 11
N1 5 # 9 # 12
#S2 # 30 # 30 #?60
#R2 # 40 # 40 #?65
#N2 # 50 # 50 #?70
#NON-REV # 90 # 90 #?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.
Checking-in a non-listed airline staff passenger:
PA:XS936Y1JACKSON/DMR,1/10,IDR2/FEB81,URES

Page 233
Reserved.
Page 234
13. Flight Destination / Remarks
Flight Remarks Display (RK)
Any agent can display the remarks for a particular flight.
Note: Date and boarding city are further optional entries, and the Entry allows up to 128
characters.
Entry: RK:FLIGHT NUMBER
RK:XS826/+ MIA
Destination Remarks Display (DR)

Any agent can display the remarks for a particular 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.
Entry: DR:AIRLINE DESTINATION
DR:KL JFK

Page 235
Reserved.
Page 236
14. 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 screen of any default flight enter: FDT:- .

Page 237
Reserved.
Page 238
15. Passenger Boarding Control
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: BDB:<FLIGHT>/.
Response to BSD:XS629/:
BSD:XS629/15nov
BSD: XS629/15NOV ATL
CC/NAM
320/A GTD/6 POS/GATE BDT1650 SD1720 ED1720 SA2100 FT0240
PASSENGERS CHECKED-IN : C12Y89
PASSENGERS BOARDED : C10Y29
PASSENGERS NOT BOARDED : C02Y60
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.

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

Reserved.
Page 240
Note: More than one seat number can be specified in the same entry, provided each seat is
entered individually and separated by a ",".
Entry:
BAS:21A,10D,10E,23D
Response:
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 241
Reserved.
Page 242
16. Glossary
-A-
ADL - Add/Delete List.
AEC - Automatic Equipment Change.
ALD - Automatic Load Planning.
AO - Agent Out Screen.
API - Advance Passenger Information.
APP - Advanced Passenger Processing System.
ASVC - Additional Service.
-B-
BAB - 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.
-C-
CFL - 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.

16. Glossary
Page 243
-D-
DA - 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.
-E-
EDIFACT - 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.
-F-
FDC - 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.
-G-
GMT - Greenwich Mean Time.
-H-
HELP - SITA Help for the application.

16. Glossary
Reserved.
Page 244
-I-
IDM - Industry Discount Message. (Dispatched to next down line station on Multi-sector
flights.)
IFM - Interline (EDIFACT flights) Fallback Message.
IOD - Inbound/Outbound Display Screen.
-L-
LDP - Load Planning.
LDVS - System Selected Deck Version.
-M-
MD - Manifest Display.
MVT - Movement Message.
-N-
NAM 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.
-P-
PA - Passenger Acceptance screen.
PAD - Passenger Available for Disembarkation.
PAID - Paid Seat.
PCI - Passenger Statistics.
PCTC - Passenger Contact.
PDD - Individual Passenger Record Display.
PDQ - Physical Device Queuing.
PECTAB - description for boarding pass printing
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.

16. Glossary
Page 245
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.
-R-
RCS - Response Capture System.
RFIC - Reason For Issuance Code.
RFISC - Reason For Issuance Sub Code.
RK - Flight Remarks Display screen.
-S-
SB - 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.
-T-
TCC - Time Calculation Screen.
TSA - Travel Security Agency.

16. Glossary
Reserved.
Page 246
-U-
Unprotected 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
Example Indicator
► Start of Entry Indicator

16. Glossary
Page 247
16. Glossary
Reserved.
Page 248
17. Index DFL Prohibited 138
Limits on Number of Passengers 134
A Multiple Passengers 131
Override 134
Access to SITA DCS 3
Passenger Cancellation 133
Advanced Passenger Processing 129 Passenger Status Change 136
Agent Re-sending APP Message 135
Automatic System Checks 4 Single Passengers 130
Agent-In 6 Standby 167
Agent-Out 6 Standbys 134
Agent Control 3 Status Codes 136
Agent Information 4 Check-In 130
Agent Sign-In 4 Check-in Flight List Display 19
Aircraft Compartment Check-In Time
Limits and Controls 37 Passport Info 118
Airline City
Encode/Decode 12 Encode/Decode
Encode/Decode 12
Airline Undesirable Passenger List 145
APP 129 Currency
AQQ 139 Encode/Decode 12
DFL Prohibited 141 D
Limits on Number of Passengers 141
Passenger Cancellation 141 Decode 12-13
Passenger Check-in, Update 139 Delete PSPT Remark 122
Associated Handling Transactions 175 Deleting Docs
Automatic System Checks Passenger Records 106
Agent 4 Display
Boarding Status 239
B
Destination Remarks 235
Bag Tag Flight Remarks 235
Issuance 184 Individual Passenger Record 57
Boarding Acceptance Passenger Survery 39
Boarding Number 240 Standby Notification 54
Boarding Acceptance / Delete Seat Number 240 Display Area 8

Boarding Pass Display Paging 10
Inhibit 181 DOCA 102
Inhibit APIS 125 Address Info 108
Issuance/Inheritance 180 DOCO 102
Information 112
C
DOCS 102
CFL Transaction 19 Travel Doc Info 103
No Segment Information 27 DSSW Parameter 146
Check-in
Crew Check-in 138
Detailed Entry 67

17. Index
Page 249
E ITCI Documentation Check 223
Electronic Miscellaneous Document (EMD) 96 L

Electronic Ticket Check-In 231 Local PAD 54
Encode 12
Entry 12 M
Encode/Decode Manual Bag Tags 64
Airline 12
Mode of Update 31
Airport 12
Multi-Page Displays
City 12
Paging 11
Currency 12
Error Responses N
DOCS,DOCA,DOCO 117
Need Notification 54, 56
Excess Baggage 182
No Record Passenger 90-91
F No Segment Information
CFL Transaction 27
FDD 29
NOREC 90
FDT 237
Flight Data Display 29 O
Flight Default Display 237
Onward Connection 214
Flight Destination / Remarks 235
Onward Connections
Flight Information Displays and Updates 29
Delete or Change 179
G Outbound Boarding Card Issuance 91
Outbound Information
Glossary 243
Check-in 90
Group Check-In 164
P
H
Paging 10
Help 16 Multi-Page Displays 11
I Passenger Acceptance
Associated Handling Transactions 175
Inputs to Issue Boarding Cards 89 Check-in 65
Interline Local Check-in 214 Check-in Examples 82
Introduction 1 Check-in Procedures 66
Issuing Boarding Pass for Return Check-in 89 Checking-in Passengers Connecting Flight 74
ITCI Checking-in Passengers Overweight Flight 73
Interline Loca Check-in 214 Checking In
Passenger Acceptance 197 Passengers Double Oncarriage Segments 72
Passenger Delete 206 Dead Head Crew Check-in 176

Passenger Record Display 221 Downgrade/Upgrade 70
Passenger Update 202 Extra Crew Check-in 175
Seat Map Display 223 Gender Reqiured Flights 68
Standby Check-in (URES/NOREC/ID) 213 ITCI Passenger Handling Procedures 197
URES, NOREC Passengers 220 Oncarriage Check-in 73

17. Index
Reserved.
Page 250
Passenger Delete 194 Sign-Out 7
Passenger Update 191 SITA DCS
Re-Checking Passengers Different Access 3
Destination 71
Special Service/Information Codes 161
Through Check-in 74
Staff Priority Table Display 233
Through Check-in, Electronic and Paper 75
Through Check-in, Electronic Tickets 74 Standby 55, 57
Unattached Baggage Check-in 176 Standby Check-in
Watchlist 142 NOREC 167
Passenger Already in PS List 89 NOREC / URES Standby, Oncarriage 169
NOREC / URES, Marketing Segment Code
Passenger Boarding Control 239
Share 171
Passenger Check-In with PIL Remarks 94
NOREC / URES, Oncarriage 169
Passenger Displays 47 PAD Check-in 168
FPS Display 153 URES Check-in 168
PS Display 153 Standby Display 54
Passenger Handling Displays 124 Summary
Passenger Manifest Information 92 ORBP Options 91
Passenger Notification 172 System Control and Security 3
Passenger Survey Display 39 System Functions 3
PDD 57
Display 124 T
Update 160 Time Calculation 15
Printing 11 Time Conversion 16
Protected Workstation 3 Transit PAD 54
PSPT
Adding 120 U
PSPT DOB Unattached Bags
Watchlist 122 Check-in 176
Delete 177
S
Display 177
SCW Watchlist Query 147 Expedite Bag Tags 179
SDD 39 Unprotected Workstation 3
Code Share Flights 45
Overweight Flights 46
W
Zone Entry 44 Watchlist
Search Boarding Process 156
by Bag Tag 63 Flight Close Out 156
Seat Map ITCI 155
Use 37 Passenger Updates 157
Viewing 33 Printing of Selectee Boarding Pass 157
Seat Map (SE) 33 Watchlist Query 155
Seat Map Display 33, 223 Workstation Information 3
Sign-In
Agent 4

17. Index
Page 251
17. Index
Reserved.
Page 252

SITA Departure Control Check-In Agent Guide Rev. 12.0 PDF

Uploaded by

Copyright:

Available Formats

You might also like

SITA Departure Control Check-In Agent Guide Rev. 12.0 PDF

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 Check-In Agent Guide Rev. 12.0 PDF

Uploaded by

Copyright:

Available Formats

Passenger Solutions

SITA Departure Control Services

SITA Departure Control Services Check-In Agent Guide

SITA Departure Control Services Check-In Agent Guide

SITA Departure Control Services Check-In Agent Guide

6.1 5 Jun 2007 Re-branded.

7.0 29 Jun 2007 Customer Release.

7.2 31 Dec 2008 n Update to Stretcher Passenger section: update to general

7.3 31-Dec-2008 Update to Passenger Update (PU) section.

8.1 23-Nov-2009 Updated:

8.2 31-Aug-2010 Added Printing of Selectee Boarding Pass and PDD Update.

9.0 15-Mar-2011 Separated Section 8 - Passenger Acceptance / Modification /

Added Interline Local Check-in (Onward Connection) to

SITA Departure Control Services Check-In Agent Guide

10.1 2012-Jun-29 Passenger Acceptance (PA) section: Added SSR codes to

10.2 2012-Oct-31 Added: Electronic Miscellaneous Documents section.

11.0 2013-Apr-30 Added additional information to Electronic Miscellaneous

11.1 2013-Dec-31 n Added new display options for display Passenger

11.2 2014-May-30 n Added EMD ASVC/SVC remark to be included on PIL, JL,

12.0 2015-August-31 n Added Merchandising 2.2 changes to ADL processing for

SITA Departure Control Services Check-In Agent Guide

SITA Departure Control Services Check-In Agent Guide

SITA Departure Control Services Check-In Agent Guide

/ The slash is required.

AGENT SIGN-IN The agent sign-in fields follow:

SITA Departure Control Services Check-In Agent Guide

Agent Number Includes the following:

SI Sign-In Function Designator.

44 Agent Number, including:

SITA Departure Control Services Check-In Agent Guide

Agent - Out (AO) Agent - In (AI)

Response: Agent C - OUT or Letter of work area leaving AGENT-IN

SITA Departure Control Services Check-In Agent Guide

Entry: Agent-In with a Personal Account Number:

or if multiple areas of the CRT are signed-in.

AGENT B - OUT / A-IN SYSTEM PSA ONLINE

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.

Sign - Out (SO)

SITA Departure Control Services Check-In Agent Guide

ATL501 44 signed out B

If multiple areas of the CRT are signed in the response is:

XS ATL501 44 SIGNED OUT B

A Area signed out.

1602 Time of sign in (GMT).

124 User Group.

Display Area (DA)

SITA Departure Control Services Check-In Agent Guide

Explanation of the Response:

A, B*, C, D, E Agent Work Areas - Areas B, D, E Controls Computer A and C are

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.

FLIGHT RECORD LISTINGS: XS SITA AIRLINE**********************