SITA Departure Control Services Check-In Supervisor Guide: Revision 11.0 Revision Date: 2015-Aug-31

SITA Departure Control Services
Check-in Supervisor Guide
Revision 11.0
Revision Date: 2015-Aug-31
Copyright © SITA Information Networking Computing USA Inc. 2010 - 2015. Confidential. All Rights Reserved.
Copyright and Trademarks
Copyright © SITA Information Networking Computing USA Inc 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 Direct, AirlineConnect, Maestro,AirportConnect, Runway,
AirportVision, SITA – The Sky is Not the Limit, CUTE, SITAPlus, DesktopConnect, SITATEX,
FleetWatch, Skyform, Graflite, WorldTracer, Horizon.
Trademarks of SITA subsidiaries: OnAir, Champ.
Revision History
Version Date Changes
7.1.1 26 Mar 2008 Deleted APL section.
Added xml section.
7.1.2 26 Mar 2008 01 Apr Replaced ETL section.

2008 Added Boarding Pass Inhibit section.
Replaced PIM examples.
Removed sections 24.2 – 24.7.
Added JL:AG
Corrected Appendix PA to Appendix ITCI EDIFACT.
7.1.3 15 Apr 2008 Reformatted sections/page breaks.
7.2 27 Mar 2008 Footer correction.
7.3 30 Apr 2008 Customer release.
7.3.1 16 Jun 2008 Section 19.4 – Update to passenger manifest generation

options to include List of Passenger Names Not Boarded,
but with Bag Tags.
7.3.2 10 Jul 2008 Section 19.4 – Update to Sorted Passenger Manifest, new
JL option added: OV. Section 27.13 Monthly PCI Summary
Report – Example updated.
7.3.3 07 Aug 2008 Section 2.2 – Flight Data Modification and Update (CSM /
CSU) CSM Output MSG table – new message TPL added
to table.
Section 19.2.3 1 COM Revised to include space 1 COM.
Section 19.4 – Sorted Passenger Manifest Generation (JL)
– New entries added to Segment Entry Options: JL:XX,
JL:OVR.
7.4 29 Aug 2008 Customer release.
7.4.1 30 Apr 2009 Section 16.3 – Flight release and PAX Message Dispatch
warning message intervals updated.
8.0 30 Apr 2009 Finalized changes to Section 16.3 for publication.
8.0.1 24 Nov 2009 CAT section: Updated lists of all valid special meal codes
(SPML) that may be listed on a PNL.
8.1 31 Dec 2009 Customer release.
SITA Departure Control Services Check-in Supervisor Guide

Revision History
Revision Date: 2015-Aug-31, Revision 11.0 Copyright © SITA Information Networking Computing
USA Inc.
2010 - 2015. Confidential. All Rights Reserved.
Page i
Version Date Changes
9.0 31 Jan 2011 Moved EDIFACT Flights / Interline Thru Check-in from
Section 26 to Section 23.
Added sub-sections: ESTA Codes for ITCI and ITCI
EDIFACT to Section 23.
Added CBP and ESTA to Glossary section.
9.0.1 17 Feb 2012 Updated Segment Data field for: Flight Data Modification
and Update (CSM/ CSU).
Added following new sections to Chapter 2: Schedule
Flight Display:
n Edits of DOCS elements.
n CSD Update to support NOT requiring APIS DOCS
information.
n CSD Update to support requiring APIS DOCS
information.
Updated branding.
9.1 29 Feb 2012 Customer release.
10.0 31 Dec 2013 Added “Accepted” response to FUI input
11.0 14 Aug 2015 Updated Reassign AEC Passengers Original Seats (REA)
topic with 'PAID' seats transaction.
Updated Bulk Recheck Accepted Passengers (BRC)
section.
Updated Bulk Recheck not Checked-in Passengers (BRN)
section.

Revision History
Copyright © SITA Information Networking Computing Revision Date: 2015-Aug-31, Revision 11.0
USA Inc.
Page ii
Table of Contents
1. Introduction 1
General Information 1
Objectives 1
2. Schedule Flight Data Display 3
Created Schedule Data (CSD) 3
Flight Data Modification and Update (CSM / CSU) 4
Edits of DOCS Elements 8
CSD Update to Support NOT Requiring APIS DOCS Information 10
CSD Update to Support APIS DOCS Information 11
Unknown Flights for Advanced Passenger Processing (APP) 12
3. Passenger Manifest Display / PNL Creation 15
Passenger Manifest Display (MD) 15
PNL Request from SITA Reservations (PM) 16
Manual PNL/ADL Creation 17
Deleting PNL from Manifest Display (DFL) 20
Passenger Name List (Manifest) Statistics - PM 21
4. Flight Initialization 23
Flight Initialization Transaction (IF) 23
Delete Flight Transaction (DFL) 24
Warning Messages 26
Error Responses 27
5. DCS Office / Message Queues 29
Display Office Queues (QT) 29
Queue Handling Procedures 31
Office Queue Repeat (QR) 34
Office Queue Hardcopy (QH) 35
Error Responses 35
Queue Clear Function XPID / VPID / XQRC 35
6. Flight Controls Using Survey Data Display 39
Assign Check-In Supervisor (AK) 39
Assign Printer for Flight Control Messages (EF) 39
7. Flight / Destination Remarks 41
Flight Remarks Creation (RKC) 41
Destination Remarks Creation (DRC) 42
8. Flight Information Displays and Updates 43
Flight Data Display (FDD) 43
Flight Update Information (FUI) 45
Flight Irregular Operations (FIR) 47
9. Inbound Outbound Passenger Display 53
Inbound Outbound Passengers 53

Table of Contents
Revision Date: 2015-Aug-31, Revision 11.0
Copyright ©SITA Information Networking
Computing USA Inc.
Page i
10. Protective Cover 57
Protective Cover (PO) 57
11. Seat Map Characteristic Changes 59
Seat Map Characteristic Changes (SCC) 59
12. Flight Control Limits 63
GOSHOW Limits (GS) 63
PAD Limits (ID) 65
Numeric Limits (HL) 66
Space Protection Limits (SX) 68
13. Reserving / Blocking Seats 69
Reserve Seats for Individual Passengers (CRS) 69
Reserve Group Seats (RS) 69
Block Seats (BS) 70
Allot Seats (AL) 71
Transit Seats (BX) 73
Releasing Reserved Seats (RA) 74
14. Passenger Standby Acceptance 77
Manual Selective Standby Acceptance (AC) 77
Manual System Standby Acceptance (GS/ID) 77
Automatic Standby Acceptance (GS/ID) 78
Manual Offload Passenger to Standby (AC:-) 78
15. Passenger Notification 79
Passenger Notification (NO) 79
16. Flight Close-Out Procedures 81
Initial Flight Close (CI) 81
Flight Close and Release to LDP (CCL) 82
Flight Release and PAX Message Dispatch (CCF) 83
Unclosed Flights Archived to History (CCH) 83
17. Passenger Excess Baggage Waiver 85
Passenger Excess Baggage Waiver (JEM) 85
18. Agent Cash Drawer / Close (JAD) 87
The Agent Cash Drawer 87
JAD Input 87
JAD Output 88
19. Passenger / Baggage Message Displays 91
Checked-In Passenger Baggage Display (JB) 91
Manual Generation of Departure Messages (LR) 91
Web Server Page Entries 123
Sorted Passenger Manifest Generation (JL) 127
Flight Check-In Agent List (JFL) 131
20. Movable Partition Flights 133
Movable Partition (MP) 133
SITA Departure Control Services Check-in Supervisor

Guide
Table of Contents
Copyright © SITA Information Networking Computing USA
Inc.
2015. Confidential. All Rights Reserved.
Page ii
21. Flight Equipment Type Change 137
Automatic Equipment Change (AEC) 137
AEC Passenger Offload (JAC) 138
Reassign AEC Passengers Original Seats (REA) 139
Assign AEC Passengers New Seats (SEA) 140
Check List for Aircraft Type and Version Change 142
AEC Check List with MP on Multi-Sector Flight 142
AEC Check List with MP On (Free Seating) 143
22. Bulk Recheck Passengers to a New Flight 145
Bulk Recheck Accepted Passengers (BRC) 145
Bulk Recheck Standby Passengers (BR) 146
Bulk Recheck not Checked-In Passengers (BRN) 147
23. Interline Through Check-In (ITCI) 149
Purpose 149
Bilateral Agreements 149
Restrictions 149
Flight Schedules/DFL (NPRO) 150
CSM/CSU/IFM 150
Check Documentation for Transit Stop Flights 152
ETM (EDIFACT Transfer Message) 155
EDIFACT Flights / Interline Thru Check-In 156
Electronic System of Travel Authorization (ESTA) 157
24. Advance Passenger Information System 161
Advance Passenger Information 161
25. Special Passenger Handling Procedures 169
Transit Flights 169
Extra Crew (XXXCREW) 171
Dead Head Crew (XXXDHC) 171
Jump Seat Passengers 171
Stretcher Passengers 172
Ground Handlers Electronic 174
26. Miscellaneous Check-In Operations 177
Location Travel Time 177
Pre-Seat Passenger on Onward Flight 178
Re-Seat Passenger On Onward Flight 178
Turn Around Flights (Round Robin) 179
Check In Override 180
27. Passenger Checked-In Statistics 183
Passenger Statistics (PCI) 183
28. Flight History Journal 189
Flight Journal Help Screen (FJ/H) 189
Flight Journal Help Screen (FJ/H) 189

Table of Contents
Copyright ©SITA Information Networking
Computing USA Inc.
Page iii
FJ Check-In Codes 192
29. Appendix – ITCI EDIFACT Error and Warning Responses 195
30. Glossary 205
31. Index 211

Guide
Table of Contents
Copyright © SITA Information Networking Computing USA
Inc.
2015. Confidential. All Rights Reserved.
Page iv
1. Introduction
General Information
This User Guide presents all the main SITA Departure Control Services (SDCS) check-in
control functions and entries required for a check-in supervisor to carry out their normal
duties. For the usual check-in agent transactions please refer to the 'SDCS Check-In Agent
User Guide'.
Objectives
This guide is designed for Airline Passenger Supervisors. It is assumed that the supervisor
has previous knowledge of either manual check-in or another computer check-in system. The
guide has six main objectives:
1. To give the supervisor a clear understanding of all the basic check-in control functions and
entries with system responses.
2. To reserve/block and/or subsequently release seats for individuals, special passengers, or
groups.
3. To add any special information by flight or destination, and to action any re-seating of
passengers as a result of any aircraft type or version change.
4. To selectively onload standby passengers before initial flight close by increasing, or
overriding, the limits.
5. To initially close flights, notify any accepted standby passengers, and to subsequently
release flight control to Load Planning. Also, after any final passenger adjustments, to
release and dispatch all downline passenger messages.
6. To give the supervisor the confidence to deal with any situation, and to be prepared to take
the necessary action to solve it with the least disruption to passengers.

1. Introduction
Revision Date: 2015-Aug-31, Revision 11.0 Copyright ©SITA Information Networking Computing
USA Inc.
Page 1
Guide
Copyright © SITA Information Networking Computing 1. Introduction
USA Inc 2010 - 2015. Confidential. All Rights Reserved. Revision Date: 2015-Aug-31, Revision 11.0
Page 2
2. Schedule Flight Data Display
Created Schedule Data (CSD)
The CSD (Created Schedule Data) transaction provides an informative display of the FDC
flight schedule data for a specific flight or flight schedule period. Specified fields on the screen
will default to the CW weight table number 1, CX table 0 and NAMSS (Name check-in with
seat selection) for each city in the schedule unless a modification (CSM) is made.
Modifications are usually made immediately following the creation of master schedules.
The CSD gives information such as the office message address table number (CX), whether
the flight will be initialized on receiving the PNL (DF NO), or if it will be deferred for manual
initialization (DF YES). It also contains:
n scheduled time of departure (STD)
n passenger boarding time (BDT)
n aircraft type and version (EQ)
n weight table number used (WTN)
n aircraft configuration (CFG)
n Type of check-in (name, numeric, etc.)
n seat assignment designation
n Passenger messages (MSG) required for this flight.
Enter:
CSD:FLIGHT/DATE
CSD Response
Other display examples:
CSD:FLIGHT/START DATE / END DATE / CSD:XS100/15APR/04OCT/X35

FREQUENCY
CSD:FLIGHT/START DATE / OPEN CSD:XS100/15APR98/OPEN

USA Inc.
Page 3
CSD:FLIGHT/DATE CSD:XS100/15APR
Note: When displaying the CSD by date range it must correspond to the master schedule.
Use FPD:FLIGHT to display the master schedule.
The CSD of a Code share Flight will have an indicator of a marketing flight displayed.
CSD for a Code share Flight with a Marketing Indicator:
Flight Data Modification and Update (CSM / CSU)

The schedule flight data can be amended for a particular date or for a flight date range. One of
the most frequent errors occurs when a multi-segment schedule is built and the default fields
are not modified. An example is the NAMSS field. If this field is not changed to NONSS for a
non-mechanized city the system will not initialize the flight because it requires a PNL for that
city to process.
The entry for one particular date is:
CSM:FLIGHT/DATE
The entries for a flight date range are:
CSM:FLIGHT/START DATE/END DATE
CSM:FLIGHT/START DATE/OPEN
CSM:FLIGHT/START DATE/END DATE/CITY/FREQUENCY (X67)

Guide
Copyright © SITA Information Networking Computing 2. Schedule Flight Data Display
Page 4
CSM Output (CSU):
Explanation
Field Explanation
CTL-OFFC The number entered here refers to the message address number created in the
CX:CITY table, and determines the address where the requested messages are sent.
WTN The number refers to the Passenger weight table created in the CW:AIRLINE
table, and determines whether Gender input is required at check-in.
Note: WTN (weight table) cannot be updated once the flight is initialized.
CWT This is the check-in weight allowance. If no restricted weight is entered then the system
defaults to 262143.
TCKI This specifies whether 'through' transfer check-in is allowed onto another flight for
those stations connected to DCS downline. System defaults to TCI. (This field cannot
be changed after flight initialization).

USA Inc.
Page 5
Field Explanation
TYPE This is the type of check-in and the seating conditions for this flight. There are five
types of check-in:
NAM - NAME check-in. (Passenger's names on PNL)
NUM - NUMERIC check-in. (No names on PNL)
PNM - PARTIAL NAME check-in. (Special passengers only)
NON - NON-AUTOMATED station. (Non-SITA DCS user)
TCL - TECHNICAL LANDING only. (No check-in or offload is allowed. This is
usually a scheduled refueling stop).
(Type of check-in cannot be upgraded after check-in is initialized, for example:
NON to NUM, PNM, NAM; NUM to PNM, NAM or PNM to NAM)
There are two types of seating options:
SS - SEAT SELECTION (seat numbers used).
NS - NO SEAT SELECTION (free seating).
It is possible to have seat selection in one class and free seating in another class.
In this case use the NS entry to specify the class where free seating is used
(example NSY) and the system defaults to seating in the other class (or classes)
on this flight.
If any station is NS then subsequent downline stations must also be NS. If a flight
is SS, then a valid seat map for the version must exist or the flight will not
initialize.
Seat options cannot be upgraded after check-in is initialized (i.e., NS to SS or
NSY to SS).
GO-SHOWS This field denotes the planned number of passengers available for disembarkation
(PAD) by class. The system default is the class group followed by the number
511. The number 511 has no real significance other than meaning no PAD
passengers are planned. The maximum number of classes is five. If a figure is
entered here it is allocated to the ID figures on the SDD screen (by class). If an
attempt is made to update the GO-SHOW field on the CSM after the flight is
initialized the response "FLT INIT-NO GOSHO UPDATE" is returned. PAD
figures are updated on the SDD manually (ID XS846Y4).
The SDD Limits control the number of Goshows and PADS that can be accepted.

Guide
Page 6
Field Explanation
MSG After the final close (CCF), the Check-In messages listed below are dispatched. If
any of these message types are not required they must be deleted. The CX CITY
table number shown in the CTL-OFFC field for each flight leg contains the
message delivery addresses.
The message types are:
PTM Passenger Transfer Manifest (dispatched to all stations having transfer).
TPM Teletype Passenger Manifest (dispatched to all stations).
PIL Passenger Information List (originating station only).
PSM Passenger Service Message (dispatched to all stations).
COM Close Out (final) Message (dispatched to all stations).
IDM Industry Discount Message (dispatched to next downline station on Multi-
sector flights).
SOM Seats Occupied Message (dispatched to next downline station).
PFS Passenger Final Sales message (originating station only).
BTM Baggage Transfer Message (dispatched to all stations).
IFM Interline (EDIFACT flights) Fallback Message (dispatched to all stations).
FTL Frequent Traveler List (dispatched to originating station).
PRL Passenger Reconciliation List (dispatched to originating station).
ETM EDIFACT Transfer Message (ITCI partner listed from departure city LH
only).
API Advanced Passenger Information (dispatched to appropriate government
agency).
ETL Electronic Ticket List (dispatched based on flight routing to originating
station).
PIM Passenger Information Message (dispatched to all stations).
CAT – Catering Message, Special Meals.
TPL – Paperless Ticket List (originating Station only)

USA Inc.
Page 7
Field Explanation
SEGMENT Field for entering any special information or restrictions on the flight. The most
DATA common ones are:
NLT NO LOCAL TRAFFIC check-in allowed traffic for this segment (no traffic
rights).
NLD NO LOCAL TRAFFIC except ID passengers allowed.
NAV NO LIVE ANIMALS allowed.
BPI NON-POOLED Baggage Indicator.
These are entered as:
SEGMENT/NLD (example: MIALAX/NLD)
To remove enter as:
SEGMENT/-NLD (example: MIALAX/-NLD)
XAP NO APIS DATA REQUIRED

SEGMENT/XAP (example: CDGBOM/XAP)
To remove enter as: SEGMENT/-XAP (example: CDGBP/-XAP)
Note: Although these are entered via the CSM/CSU screen, they are only
displayed on the CSD screen. So always check the CSD screen if in doubt.
Use the TAB key to move the cursor to fields that can be changed and enter the
appropriate information. Once the changes are entered the system responds with
'ACCEPTED'.
CSM/CSU If the changes are for a flight period the system may respond with 'ACCEPTED'
followed by 'ACTIVE DATES ARE'. This indicates only the non-active flights are
updated, so the active flights must be updated individually. This prevents updates to
active flights in case the changes do not apply. If the changes do apply, they must be
entered individually.
Edits of DOCS Elements

When the PNL/ADL is processed, the DOCS elements are created with no validation of the
elements. This can result in incomplete DOCS required for APIS. At check-in for an APIS
flight, the system is enhanced to verify all the required elements for DOCS are present. If not,
check-in is completed and a boarding number assigned but NO Boarding Pass will be issued
until the required DOCS elements are present.

Guide
Page 8
Example of Batch table indicating APIS require.
In this example, I inbound only.
Passenger Record with incomplete DOCS
PDD:1
Check-in and response to inhibit Boarding Card
»PA:1,1/10,M2
Note:
If DOCS needs correction, follow the current procedures to PW and add the correct
DOCS. Once the passenger record is corrected, the BC command can be used to issue
the boarding pass.

USA Inc.
Page 9
Remove Docs
PW#1,DOCS
CSD Update to Support NOT Requiring APIS DOCS

Information
SDCS has been enhanced to support Flight Data Modification (CSM / CSU) that will by-pass
the requirement to inhibit printing of boarding passes. If complete, DOCS are not present in
the PDD record for each passenger.
Example:
Agent to update CSM with segment information.
Example:
CSM:FLIGHT/DATE
SEGMENT DATA CDGBOM/XAP
The entry to remove XAP:

SEGMENT DATA - CDGBOM/-XAP

Guide
Page 10
CSD Update to Support APIS DOCS Information
An airline has the option to collect APIS DOCS information for a flight that does not fall under
APIS country rules. The Segment Data of the CSD is used to support this requirement.
Note: Current Functionality.
Error Responses
Response Explanation
CLASS Error with class groups used.
CONTROL MSG Type not NAM, so remove TPM, PIL, and PSM.
DATE Invalid date entered.
ERR-MANUAL Check-in application not specified in BF:T.

CHECK-IN
FLT CANCELLED Specified flight is cancelled.
FLT INIT Flight initialized so field cannot be updated.
FLT NBR Flight number format entry is incorrect.
FORMAT Invalid format entry.
GO-SHOW Invalid entry or exceeds compartment capacity.
SEAT SELECTION Invalid option entered or SS follows a NS segment.
SEGMENT Invalid segment entry or NLD/NLT entered together.
SKED-CHANGE Schedule change (BF:T) is in progress and must be cleared before

displaying.

USA Inc.
Page 11
Unknown Flights for Advanced Passenger Processing (APP)
Flights operating into, out of and through countries using the Advanced Passenger
Processing (APP) system must be registered with the Australia Department of Immigration
and Indigenous Affairs. Normally the OAG tape will register the flight.
Note: For code share flights APP requires only the operating flight number, not the marketing
flight number.
When the flight is not found in the APP system, an error response is returned advising that the
flight is not recognized, and the airline will need to submit a TIETAYT A transaction to load the
flight into the Australia Department of Immigration and Indigenous Affairs database to allow
processing.
Input:
Explanation:
TIETAYT Function identifier.
A Required option (A = Add).
XS888 Flight to add.
01JUN06 Effective date.
30OCT06 Discontinue date.
13567 Frequency of the flight:

1 - Monday (2 = Tuesday, 3 = Wednesday, 4 = Thursday, 5 = Friday, 6
= Saturday, 7 = Sunday) This flight will operate on Monday,
Wednesday, Friday, Saturday and Sunday.
LAX Originating station. Intermediate ports are allowed for a flight.
1235 Local departure time from the originating station.
1047 Local arrival time at the next port.
+1 Date variation (if any). Required only when the date differs fro the date
of departure from the origin port.
SYD First arrival port.
1115 Local departure time from this airport.
1305 Local arrival time at the next port.

Guide
Page 12
The APP system database is updated every Friday at 03:00 Atlanta time. Any manually
maintained flight schedules will be overwritten and deleted. The airline must reload the
schedule if it is required beyond the weekly cycle. There is no provision to update or delete a
manually entered flight, carefully enter the data on the command line before transmitting the
flight entry.
Airlines can load and display flights that either it or its code share partners operate.

USA Inc.
Page 13
Guide
Page 14
3. Passenger Manifest Display / PNL Creation
Passenger Manifest Display (MD)
The Manifest Display (MD) transaction shows the text portion of the passenger name list
(PNL) and the add / delete list (ADL) messages received from a reservations system. The
SDCS CKI manifest file stores the data and saves it for subsequent display. The MD also
displays name lists entered via manual backup transactions MBP / MBA and the text of
unsolicited Seats Occupied Messages (SOMs).
The MD may be displayed from the sign-in airport or a specified airport. The display can be
requested to start and / or end at a specified line number or start with a specific surname.
The entry to display a PNL and determine if it has been sent to a particular flight and whether
it has been processed at the sign-in airport is:
MD:FLIGHT NUMBER/DATE MD:XS100/18APR
MD Request for the Sign In Airport
When the MD transaction is transmitted the PNL/ADL lists are displayed from the manifest
file. The passenger name data is marked with a header 'NOT PROCESSED' if the list is not
useable, not complete or the flight is not initialized. The system also adds this header if
additional PNLs for other cities have not yet been requested or are in the process of being
received from the Reservation System.
The '+' at the bottom right of the display signifies there are more pages to the PNL. Enter PN
to access the next page.

USA Inc.
Page 15
Other Manifest Display entries:
To display PNL/ADL data received for XS 506 departing today from MEX:
MD:XS506/./MEX
To display PNL/ADL data lines 1 through 8 on XS506:
MD:XS506/23JUL/MEX//8
Note: // is the default value of start line.
To display PNL/ADL data for a specific passenger:
MD:XS506/./MEX/SMITH
Where LUX is departure city.
MD:XS506/23JUL/LUX/SMITH
It is also possible to display a SOM sent to DCS on a transit flight from a non-mechanized city.
Enter:
MD:SOM/FLIGHT/DATE/STATION
To display the parts of a PNL received in DCS, enter:
MBPNL/FLIGHT/DATE
Example:
MBPNL/XS506/.
CITY ATL ALL PARTS RECEIVED
or
CITY ATL MORE PARTS 1 RECEIVED
(which indicates more parts are still to come)
The MD is limited to display 1000 lines. If a PNL contains more than 1000 lines the MD can be
displayed in parts with the following entry:
MD:XS506/./1001/2000
When the PNL has more than 1000 lines, it may be necessary to continue with the following
entry to display additional PNL lines:
MDXS506/./2001/3000
It is also possible to display an MD by using only selected lines with the following entry:
MDXS506/./25/30
Note: All PNL and ADL parts will display even if some have been rejected to queue. If any
ADL shows “NOT PROCESSED” all subsequent ADLs will not process.
PNL Request from SITA Reservations (PM)

All PNLs and ADLs are sent to the processing address HDQCR__(Host Airline Code) and
converted to the DCS PS list for check-in.

Guide
Copyright © SITA Information Networking Computing 3. Passenger Manifest Display / PNL Creation
Page 16
Normally SITA Reservations sends all PNLs and ADLs through the IMD file. It is possible,
however to request a PNL from the SITA Reservations System if either a PNL has not arrived
for a flight or if it has been deleted.
Note: DCS only accepts one PNL for a flight and will reject all others.
Enter:
M:C/FLT/DATE/CITY/H/HDQCR**
Note: ** designates Host Airline Code. This transaction can only be used by authorized
personnel. The PM:C entry tells the system that this is the last PNL requested and to Close
SITA Reservations for any further PNL requests. If an airline does not have immediate ADL
processing (IADL) the ADL may be requested with the entry:
PM:A/FLT/DATE/CITY/H/HDQCR**. If another PNL is required after PM:C is used, then
before PM:C can be re-entered, the RELEASE entry (PM:R/FLT/DATE/CITY) must be
activated for each Departure city.
The Supervisor should display the MD for each departure city on the itinerary to verify if the
PNL is processed, and review the KR queue for reasons if a PNL was not processed before
requesting another PNL.
When the SITA DCS system is used by an Airport Ground Handling Company the PNL
processing address differs from that of an airline.
All Airport Ground Handling Companies are grouped under the code 7X or XH and assigned
a two-numeric identification code by the SITA SYS group to distinguish them.
PNLs coming from a non-SITA Reservation System or SITATEX messages cannot be
processed using the two-numeric code (example 16). The Airport Handling Company must
apply for a special two letter code from SITA Paris to use with the designator 7X or XH
(Ground Handling Agent). The SITA Account Manager will assist with this two-letter code
when SITA connection requests are made. The code is added to the SYS processing table to
use with the 7X / XH code.
If the code is not added to this processing table or used correctly, messages are rejected to
SITA Office ATL001 CN queue, never processed and return an error response " ADDRESS
ERROR ORIGIN'.
Manual PNL/ADL Creation

For charter flights, training flights or testing purposes, it is possible to manually create a
PNL/ADL and send it to a flight. There are two methods for manually sending the PNL/ADL:
n Teletype format: PNL/ADL; or
n Manual Backup Generation PNL/ADL.
By Teletype Format
The teletype format follows IATA rules and the destination address is the SDCS host system
address where the PNL is to be sent.
PNL Teletype Format

USA Inc.
Page 17
Note: Class order is important but the names do not have to be entered in alphabetical order.
Note: Non-airline handling agents with a numeric code have a specific address other than
HDQCR.
A Nil PNL Entry

Guide
Page 18
ADL Teletype Format
Note: Use ADD to add names, DEL to remove names, and CHG to change or add items for a
previously booked passenger.
By Using the MBP Entry

MBP Entry
Note: Enter the names in alphabetical order when using the MBP entry. Also the system
uses different programs between the Teletype format and MBP to load the PNL; and is more
restrictive in the use of MBP. Therefore if a test PNL using the MBP entry is rejected from
going onto a flight, it is better to try sending it by Teletype before contacting DCS Customer
Support. One example of this is the ZZ entry for blocked seats for a stretcher passenger. By
using the MBP entry the system inhibits the PNL dispatch (it responds 'Block seats first'),
however by Teletype it works correctly, and sends a message to the office queue with a
warning about blocking the required seats on the seat map.
A Nil PNL Sent via MBP
MBP:FLIGHT/DATE/CITY
NO PNL
The system only accepts one PNL, but it can accept any number of ADLs. It is possible to
send a manual ADL by using a MBA function code and the same format as the MBP except
that ADD, DEL or CHG is entered on the line following the destination and class.
PNL for an Infant not Occupying a Seat

USA Inc.
Page 19
The age of the infant is included as part of the infant entry on the PNL.
ADL Via MBA
Note: Some elements such as .C/ are not accepted with the MBP transaction.
Deleting PNL from Manifest Display (DFL)

Sometimes it is necessary to delete a PNL from a manifest display. This may be for any of the
following reasons:
n A change of equipment is made after flight initialization and prior to passenger check-in.
(After check-in the AEC transaction should be used.)
n Not all parts of the PNL were received in the system (perhaps the system went down for a
few seconds during the loading) and if another PNL is requested the system will reject it.
n A wrong PNL is loaded (this can happen with a manually created PNL and not a system
created PNL).
n There was a change to class or destination after the PNL was loaded.
DFL
Care must be taken before entering a DFL (Delete Flight) transaction. The possibility for the
loss of information is great. Due to Electronic Ticketing and the use of EDIFACT messaging
with interline thru check-in more restrictions are placed on the use of DFL transactions. The
Delete Flight Transaction (DFL) sub-section, in Flight Initialization, describes the DFL
transaction.

Guide
Page 20
If a flight is not initialized, use the following entry to remove the PNL:
DFL:FLIGHT/DATE/PNL DFL:XS100/18APR/PNL
The response is 'ACCEPTED' and another PNL may be requested.
If a flight has been initialized the removal of the PNL and a request for another PNL can cause
a duplication of names on the PS list. For this reason, the flight now must be de-initialized and
the PNL removed. If an attempt is made to DFL the PNL after flight initialization a warning
message is returned:
'UNABLE - PNL PROCESSED - MUST DO "NPRO" FIRST'
The entry to de initialize the flight would be:
DFL:FLIGHT/DATE/NPRO DFL:XS100/18APR/NPRO
This transaction clears all changes made to the seat map and erases all boarding numbers
and seat numbers from the passenger record.
The response to the transaction is 'ACCEPTED'. The PNL can then be removed.
Note: If any check-in has already taken place, then the response is “PAX ALREADY
CHECKED_IN. CONFIRM Y OR N’. Enter ‘Y’ to accept or ‘N’ to ignore it.
If this is followed by the entry: MD:FLIGHT/DATE, the response should be 'NIL'.
Another PNL is then requested. For flight schedules built with the ‘K’ option, the schedule
must be retransmitted. For flights built with the ‘D’ option, then the ‘IF’ transaction must also
be used.
To display times when PNLs and ADLs were sent from SITA Reservations a DCS Supervisor
should be aware of a type of SITA Reservations transactions that provides this history. The
Inventory History transaction is a SITA Reservations restricted function that must be
specifically added to a Unique Defined User Group or Security Table for use within the DCS
application. The transaction allows a supervisor to display inventory changes made against a
specific flight on a specific date. The function code is RH.
Note: After a PNL is processed it cannot be deleted without deleting the flight record. See the
Flight Initialization section.
Passenger Name List (Manifest) Statistics - PM

The Passenger Manifest Statistics (PM) display is the inventory history type to use with the
RH function code in DCS. It produces a CRT display only unless the print total (PT) function is
used.
Enter:
RH:FLIGHT/DATE/PM RH:260/./PM

USA Inc.
Page 21
Response to RH:260:
Explanation
Field Explanation
ID Passenger Manifest (PNL).
OFFICE Office sending manifest (ATL001).
AGNT Agent requesting manifest or (99--) SITA Reservations Central Site Time Call.
DATE Date manifest generated.
TIME Time (GMT) manifest generated.
CTY City where manifest was sent.
PR Type of manifest requested:

C - Complete Name and Numeric PNL
CN - Complete Name and Numeric PNL. This entry does not set the 'R' indicator.
Use 'CN' when a PNL is needed for information purposes only. The PNL indicator
'R' is placed in the inventory record on the flight leg for the PNL boarding city. The
indicator inhibits any future generation of a PNL (either or demand) unless it is
removed: PM:R/FLIGHT/DATE/CITY.
S - Numeric PNL with special service information.
A - Addition and deletion list (ADL).
N - Numeric PNL.
OLD Input Transaction TC Time Call, automatic PNL generation by SITA Reservations
CRT Request made from CRT.
NEW Output Transaction - CRT/ Printer PID or Processing Address.

Guide
Page 22
4. Flight Initialization
Flight Initialization Transaction (IF)
When a flight schedule is built with a D option (deferred initialization) under the APPL heading
on the BF:T or DFD the flight must be manually initialized for check-in, (maximum 68 hours
prior to departure time).
The manual initialization entry is:
IF:FLIGHT NUMBER/DATE IF:XS100/.
If the entry is accepted the response is: CKI TIME 1020 (local time of transaction).
If the flight is a TRANSIT flight and the previous station is non-automated for DCS, the
response is: SOM REQUESTED, unless a SOM has been received. If no SOM is received
the flight will not initialize until the 'IF' entry has been re-entered THREE times. If it is known
that the SOM is not present the flight may be initialized (avoiding the three IFs) by the entry.
IF:FLIGHT/DATE/PNL IF:XS100/./PNL
The response to either entry is:

CKI TIME 1020
SOM NOT PROCESSED
Note: When a PNL is present the response to the MD or PS entry is “NOT PROCESSED”
until the IF entry is performed.
Error Responses
AIRCRAFT The CND table number was canceled or the aircraft type was
deleted from the fleet.
CLASS Class entered differs from CND table used or CD table for that
airline.
DATE Invalid date entered or flight not active.
FLIGHT ALREADY The flight was built with a 'K' or the 'IF' transaction was already
INITIALIZED entered.
FLT NBR Flight not active or RI index missing (display BF:T for this flight
and date, re-file, and re-activate it to solve this problem).
FORMAT Incorrect entry.
ILLEGAL UPDATE If transaction was attempted on a flight with auto-initialization

(K) option.

USA Inc.
Page 23
PNL PROCESSING IN On a multi-sector flight SCM is incorrectly showing one or
PROGRESS more stations as NAM when they are not a SITA DCS station.
Change to NON.
Delete Flight Transaction (DFL)

The Delete Flight Transaction (DFL) releases and un-links all or specific database records
associated with a precise flight on a precise date. The transaction is restricted to supervisory
staff because of the implications of deleting database records.
For electronic ticket customers this transaction is inhibited after the first e-ticketed passenger
is checked-in. SITA Customer Support can set a parameter that removes this restriction.
Be careful when entering the DFL transaction after check-in starts to limit the number of
messages passed between the SITA DCS system and the ticketing application. Limiting the
number of messages can also prevent discrepancies in the passengers’ coupon status.
Manual Backup Flight Data

Since flight records are released, prior data should be recorded when performing the DFL
transaction. Record any data that is necessary to rebuild a manual backup flight. Make copies
of:
n SDD
n SE
n any related passenger information
n SOM
n unattached bag information
n standby passengers
Capture the data from PNL/ADL manifest records in a script file and/or hard copy list for data
re-entry in cases where manifest data cannot be restored from the serviced reservations
system.

Guide
Copyright © SITA Information Networking Computing 4. Flight Initialization
Page 24
DFL Option Codes
These three option codes perform special functionality as shown below:
Note: Be careful when using PNL or ALL. With a handled carrier, you may need to request a
repeat PNL which time may not permit.
Code Explanation
NPRO Releases all records, except the PNL / ADL records for the flight, and clears the
Manifest Index so a PNL no longer shows processed.
This means the flight becomes de-initialized. All accepted passengers, SBY
passengers, unattached baggage, GS/ID figures, BS, RS, AK, CD and RKC items will
be removed from the initialized flight. The PNL will again show 'NOT PROCESSED'.
PNL Only PNL/ADL records are released for a specific flight/date. The requesting of
manifests and SOMs are again permitted.
The PNL/ADL was removed from the flight and another PNL must be requested. If a
flight is initialized the NPRO option must be entered before the PNL option.
ALL All records are released with the addition of the Flight Check-In and Check-In Flight
Number Records.
The ALL option is a combination of the NPRO and PNL options, plus it deletes the Flight
Check-In and Check-In Flight Number record. The DFD must be re-transmitted
regardless if the APPL option is a D or a K. This option is usually done if there was an
error message returned after the NPRO/PNL options were transmitted. This indicates
the NPRO/PNL option did not fully work. The ALL option clears any remaining files not
released.
DFL:FLIGHT NUMBER/DATE/NPRO DFL:XS100/./NPRO
The response to this transaction is 'ACCEPTED' or a warning message if passengers have

been checked in (Warning Messages sub-section in Flight Initialization section). If this entry is
followed by the entry:
PS:FLIGHT/DATE PS:XS100/.
The response is:

327-NEED INITIALIZE.
Flight Number
After a DFD: entry, the response is either NEED INITIALIZE or PNL PROCESSING IN
PROGRESS.
At this stage the PNL is not canceled but has gone back onto the manifest display
(MD:FLIGHT/DATE) as 'NOT PROCESSED'.

USA Inc.
Page 25
To initialize the flight for 'D' option built flights just enter 'IF:FLIGHT/DATE' and the PNL will
load back onto the flight. For 'K' built flights the BF:T/FLIGHT/DATE must be displayed, re-
filed and activated (!A) or the DFD:FLIGHT/DATE be re-transmitted. The PNL will load back
onto the flight.
If the PNL has to be canceled enter:
DFL:FLIGHT/DATE/PNL DFL:XS100/./PNL
A warning message is received if the flight is initialized. See Warning Messages sub-section
in Flight Initialization section.
Once the PNL is canceled, a new PNL must be requested for each segment:
(PM:R/FLIGHT/DATE/CITY and PM:C/FLIGHT/DATE/CITY/H/HDQCR**).
The final option deletes all records and flight number records. Enter:
DFL:FLIGHT/DATE/ALL
A warning message is given if the flight has passengers checked in. See Warning Messages
sub-section in Flight Initialization section.
If either the PS or SDD entry is entered after this ALL option the response is:
006 - Flight Number
The DFD has to be retransmitted and the PNL is released and requested.
Warning Messages
To prevent mistakes in the DFL entry, a warning message is displayed on any flight having
passengers checked in.
DFL
DFL … NPRO Warning when Passenger Checked In
DFL:400/./NPRO
WARNING - PAX ALREADY CHECKED-IN - PLS CONFIRM DFL
►DFL: XS400/26JUN/NPRO/Y-
Confirm the entry by transmitting after the ‘Y’.
When a PNL is loaded and the flight is initialized the names on the PS list can be duplicated if
the flight is not de-initialized before the PNL is deleted and another PNL requested. To
prevent this from happening, a warning message instructs the supervisor to enter the
DFL:FLIGHT/DATE/NRPO or DFL:FLIGHT/DATE/ALL first.
DFL…PNL Warning after Flight is Initialized
DFL:400/./PNL
UNABLE - PNL PROCESSED - MUST DO "NPRO" FIRST
This response above is returned once a flight is initialized regardless of whether a passenger
is checked-in. If a passenger has been checked in the warning shown above is returned once
the NPRO or ALL option is entered.

Guide
Page 26
If the flight is initialized in LDP, a warning message displays - **WARNING** ACCEPTED
FLIGHT HAS BEEN ACTIVATED IN LDP. This does not affect the DFL process.
Error Responses
Message Explanation
AUTHORITY The agent is not allowed to use this transaction or is not signed
into one of the flight's itinerary cities.
DATE Invalid date entered.
FLT NBR Flight does not exist in the database or the flight has not been
activated.
FORMAT/FUNCTION Invalid format or function entered.
NO ACTION Invalid entry or DFL had already been performed. No action was
taken.
OPTION Option entered is not an allowed code.
UNABLE DFL already processed or the flight is not initialized.

USA Inc.
Page 27
Guide
Page 28
5. DCS Office / Message Queues
Display Office Queues (QT)
The SITA Departure Control System operates by receiving and sending messages between
the following applications:
n check-in (CKI)
n load planning (LDP)
n flight schedules (FDC)
Some messages are sent to the queues for information only, and others go because they are
rejected for some reason. Also, incoming messages either from other computer systems or by
telex, such as PNL, LDM, or SOM are rejected if they cannot attach themselves to a flight.
Before a DCS User starts operating DCS it must be decided which office number to use. It is
important to use a number not used by any other SITA application in that airline (especially if
the airline is a SITA Reservations User).
We recommend using OFFICE 501. This OFFICE will then be consistent with other SDCS
users. Once the number has been decided the user must create the OFFICE file in the
system. Thus, when the agents sign-in they are assigned to that office number, otherwise
some of the messages will go to the wrong queues. Access to the queues is limited according
to User Group authorization.
Enter:
QT
Response of QT Entry
The entry to display the queues is:
QT ALT501
Note: The M above indicates the queue is being refreshed.

Explanation of the following queue codes of where the messages came from and what
application they were trying to access:
General Codes
Code Description
GQ General Queue for any Messages that are not Directed to a Valid Queue Below.

USA Inc.
Page 29
Check-In Codes
Code Description
KS Manually Sent SOM to CKI Reject.
KL Rejected Messages from LDP to CKI (including WAB Messages).
KF Flight Creation (BF:T or DFD) Record.
KR PNL/ADL Rejections to CKI.
CE (Currently not Used.)
WAB Weight and Balance.
MP Merge PNL Reject.
Load Planning Codes
Code Description
LF Rejected ASM (Aircraft Registrations) Messages.
LK Rejected Messages from CKI to LDP (including COM Messages).
LE Rejected LDP teletypes and Aircraft Balance Warnings.
After the code there are two fields. The first field is the number of messages on the queue for
this code, and the second field is the maximum number of messages permitted for this code.
Once the system reaches the specified maximum (or a percentage of the specified maximum
as defined by a system parameter), the messages will print on a designated printer until the
number of messages is again below the maximum.
To display the active queues, enter:
QTA

Guide
Copyright © SITA Information Networking Computing 5. DCS Office / Message Queues
Page 30
Response of QTA Entry
Note: QT and QTA are the most common Check in and Load Planning queues. Other
queues may be shown but are not in use.
Queue Handling Procedures

Display Particular Queue (QS)
After displaying an active queue, various transactions can be entered to review or close the
queue. These transactions follow:
Code Description
QS:KF Display messages on a specific queue (KF).
QD Move to next message but do NOT DELETE this one.
QN Move to next message and DELETE this one.
QDE Exit queue but do NOT DELETE displayed message.
QNE Exit from queue and DELETE displayed message.
QT:ATL501 Display different office queue from sign-in.
QS:KF/ATL501 Display KF queue from different office.
QR Recall an erased Office Queue message.
Correcting a Single Page Message (QB)

Once the rejected message is displayed on the screen, the system adds a SOE (►) followed
by QB: (queue back) on the second line from the top of the screen. If the complete message
displays, the required corrections can be applied, and the screen is transmitted from the last
character displayed.
Note: The PNL (and in all cases with the ADL) will appear on the queue without the system
address and originating address. It is important to insert the correct system address
(HDQCR- -), and a valid origination address on the two lines before the line that says 'PNL'.

USA Inc.
Page 31
Rejected PNL on KR Queue:
Field Explanation
ATL501 CKI-RES (006) The first line displays the reject office number followed by the
explanation that this was a message to CKI from RES that
was rejected, and currently there are six messages on this
queue.
Flight/Date ►QB: The second line displays the reason why it was rejected
followed by the QB entry.
DVC-135 Line 3 indicates the programming PID number that this

message came from.
Lines 4-17 The remaining lines contain the message.
In this example a PNL was rejected by the system because the flight is not yet created in CKI.
Once the flight is created then this part (PART 2) of the PNL can be sent to the flight by:
1. Displaying it on the queue, and without making any changes; or
2. Transmitting the screen after the L of ENDPNL.
The message then disappears from the queue and should now be present under the
MD:FLIGHT/DATE display.
It is possible before transmitting the message to make any changes as required. This includes
changing the flight number, destination, date, class of travel, and even inserting or deleting
lines, as long as the screen is transmitted after the last character displayed.
Note: A PNL part that rejects will show as PNL. An individual name reject displays as an
ADL. Individual name rejects will display on MD.

Guide
Page 32
Correcting a Multi-Page Message (UP)
Some messages, especially long PNL parts, can be longer than one screen display, so a
slightly different procedure using the 'UP' function code has to be used.
Display of Rejected PNL
To correct the first page of a multi-page message:

1. Replaced the QB function code with the UP function code.
2. If not already displayed, add the system and originating addresses.
3. Once the corrections are made, transmit the screen after the last displayed character.
Page 1 Corrections of Rejected PNL
The response is a re-display of the corrected page. If there are no further changes, enter a
SOE (►) followed by the QB: function code at the bottom of the screen.
The response to the ►QB: transaction is either 'Q EMPTY' which means that the message
was re-transmitted to the specified flight and is deleted from the queue, or it is a display of the
next message on the queue. So either correct this next message or exit the queue by entering
'QDE'.

USA Inc.
Page 33
In the above example the PNL has gone on the queue because it is a DUPLICATE. This
means that the system has already received a PNL for the specified flight. However, in this
case, assume the original PNL was deleted from the flight (DFL:FLIGHT/DATE/PNL), and
this one on the queue is going to be used. The QB is replaced by UP and after any changes or
corrections, the screen is transmitted after the '6' of the PNR locator number of passenger
1JACK/A .L/HP8J6. If no further changes are required then enter the ►QB: transaction code
at the bottom of the screen.
Note: Do not include any '+' or '-' characters displayed (indicating more pages forward or
back) when the transmitting of the display. Delete them before transmitting the screen.
Note: If there are no corrections required for the first page, remember to check that the
system and originating addresses are present. If not, then these must be added on the first
page before going to the following pages.
If the second page needs to be corrected, use the PN code to access the page, then insert a
SOE (►) followed by the UP: function code on the first line of text.
QR/QH
Page 2 Corrections of Rejected PNL
Once the corrections are made, transmit the screen after the last displayed character. The
response is a re-display of the corrected page. If there are no further changes, enter a SOE
(►) followed by the QB: function code at the bottom of the screen, and the whole message
part will be re-transmitted onto the specified flight.
The response to the ►QB: transaction is either "Q EMPTY", which means the message was
re-transmitted to the specified flight and was not deleted from the queue, or it displays the
next message on the queue. The next message is either ignored, corrected or the queue is
exited by entering QDE.
Note: Insert ►UP: in the correct place on the first line, otherwise the system inserts an extra
blank line when the screen is transmitted. Also make sure that the '-' character is removed
from the end of the first line, otherwise it inserts the '-' in front of the following name (example -
2LAST/MR/MRS-H2 .L/H3TAR) which causes problems later when trying to load the PNL
onto the flight.
Office Queue Repeat (QR)

If an agent has displayed a message from an office queue, and has erased it from the screen,
it can be recalled by entering: QR
The previous message is only displayed if QD or QN has not been subsequently entered.

Guide
Page 34
Office Queue Hardcopy (QH)
It is possible to get a printout of all the messages contained in an office queue onto the printer
PID associated with that office (check QU:OFFICE CODE).
QH
Enter:
QH:QUEUE/OFFICE NUMBER
QH:LE/ATL501
The response is a start of entry (►) on the following line.
Note: This transaction will empty the queue to a printer.
Error Responses
CITY/OFFICE Invalid CITY or OFFICE specified.
CORRECT VIA UP Change ►QB: to ►UP: before transmitting.
FORMAT/FUNCTION Invalid format or function entered.
ILLEGAL Transaction not allowed.
NO ACTIVE QUEUES All message counts are zero.
NO DISPLAY The entry was not preceded by a queue item.
NO QUEUE The specified queue does not exist.
QUEUE NOT ASSIGNED Invalid code specified in entry.
QUEUE EMPTY Indicates that the specified queue is empty.
QUE PENDING Indicates the agent is assigned to a queue and is not allowed to
sign out of a work area until the queue is ended.
QUEUE TYPE Invalid code specified in entry.
WORKING QUEUE Indicates that the agent is already assigned to a queue. Only one
queue can be worked on at a time.
Queue Clear Function XPID / VPID / XQRC

User Group 121 can clear queues without processing them. The Function code can also be
added to the user unique function codes of the airline or Security Table.

USA Inc.
Page 35
When the sub function XPID or XQRC is used to remove items from queue, an office queue
item is placed on the master control RP Queue indicating a queue clear function has
occurred. If there is no RP queue the item warning is sent to the GS queue.
Removing Messages from a PID (XPID)

1. The PDQ (Physical Device Queuing) for the desired PID is displayed to determine items
on queue by message priority.
2. The queue entry with sub function XPID for PID 40404 / message priority 4/ delete 2 items
is entered. There is no response.
QUE:XPID/40404/4/2

Guide
Page 36
3. The PID may be displayed again to verify the items were removed.
4. A warning message is sent to the Master Queue (CITY 001 FILE) RP queue giving the
date / time / office / Agent / PID number / and transaction. If there is no RP queue the
message goes to the GS (General Queue).
This transaction processes a maximum of 200 messages per entry. It can accept a larger
number in the transaction but will only process a maximum of 200. For security reasons the
XPID sub-function will not work on Ticket and ATB printers nor internal processing PIDs. This
transaction is normally used to remove Boarding Passes and Bag Tags from a printer that has
stopped working or is in a test environment.
View and Print Priority Messages on PID Queue (VPID)

The entry to view and print the messages of a PID on queue is:
QUE:VPID/40404/3/2/H565
Field Explanation
VPID Sub function to view messages on PDQ.
40404 The PID number.
3 The message priority being viewed.
2 The number of messages to view. The maximum that can be processed is 50.
H Hardcopy option.
565 Printer PID number.
If the H565 is not entered the output would go to the requesting CRT screen. If only the H is
input, the output goes to the associated hardcopy printer of the requesting CRT.
A PID may also be viewed with the PDQ:P transaction. For example:
PDQ:P40404/3/2/H565

USA Inc.
Page 37
Removing Messages from the Office Queue (XQRC)
The Office Queuing process monitors the operation of the Departure Control System. If
worked daily the queues can warn of problems before they become critical. The system is
also an important investigative tool pointing to errors and/or possible database problems.
Each customer must maintain the quality of their Departure Control System by having a
dedicated person work the queues daily.
QUE
Sometimes it is necessary to remove all or some of the messages found on a specified queue
of an Office File. This Supervisor has this ability.
The entry to clear the queue is:
QUE:XQRC/ATL501/KF/#MSGS
Field Explanation
XQRC Sub function to clear messages from an Office Queue Reason Code.
ATL501 City and Office Code.
KF Queue Reason Code - Flight Creation Record.
#MSGS A number for the desired amount of messages to remove from the queue. If no
number is input all messages are cleared. The number of messages is optional.
A record of message removal will be sent to the RP queue reason code of the Queue Master
File (usually CITY001) or to the GQ (General Queue) of the Master File if no reason code
exists for office 501.

Guide
Page 38
6. Flight Controls Using Survey Data Display
Assign Check-In Supervisor (AK)
It is possible to enter a supervisor's agent number or telephone extension on the SDD screen
under AK so that anyone looking at the flight would know who to contact. This is useful where
many flights are operating with different supervisors looking after different flights.
Enter:
AK:FLIGHT/NUMBER (Maximum of five numeric) AK:XS645/2317
(For phone extension 2317)

The response is 'ACCEPTED'.
SDD Screen
Note: If only AK:FLIGHT is entered, the system assigns the sign-in agent number under AK
on the SDD screen.
To clear any AK figures, enter:
AK:FLIGHT/0
Error Responses
Field Explanation
FLT CANCELLED The input flight is cancelled.
FLT CLOSED The input flight has already closed for check-in.
PROT COV The input flight is under Protective Cover.
Assign Printer for Flight Control Messages (EF)

Assign a printer PID number (or CRT PID) to the flight on the SDD screen under CD so any
changes made to the flight will be quickly identified by the supervisor controlling the flight.
Examples of these changes include gate number change, new ETD, or an aircraft type or
version change. If no printer PID number is input then these messages go to the assigned
address or default number entered in the CX:DEST table for the message address number
used for this flight.
Note: The code entered is EF and not CD, because the code CD is not available.
Enter:

6. Flight Controls Using Survey Data Display
USA Inc.
Page 39
EF:FLIGHT/PID NUMBER EF:XS835/2956
Flight Control Message on SDD Screen
To clear any CD figures, enter: EF:FLIGHT/0.

Error Responses
Field Explanation
DEVICE Invalid PID number specified.
FLT CANCELLED The input flight has been cancelled.

Guide
Copyright © SITA Information Networking Computing 6. Flight Controls Using Survey Data Display
Page 40
7. Flight / Destination Remarks
Flight Remarks Creation (RKC)
It is possible to add remarks for a particular flight so that it will be displayed to the agents as
they check-in passengers and also on the SDD, SE and PS screens.
Enter:
RKC:FLIGHT/DATE AK:XS645/2317RKC:XS396/24APR06ATL
Note: If no date is entered, the system defaults to today.
RKC Response:
There are two lines of free format up to a maximum of 160 characters. The cursor stops just
after the ► on the second line, and the ► must be erased before entering any remarks. If only
one line of remarks are required they can be entered on either line 1 or line 2 if the ► is
removed before entering the 'TRANSMIT' key.
Remarks Added to RKC:
To display any remarks entered for a flight, enter:

RK:FLIGHT
For catering there is an airline parameter ‘CATE’ that displays the CAT line, for example:
RK with CAT Format:
RK:XS019
It is then possible to enter the number the number of meals by class.

7. Flight / Destination Remarks
USA Inc.
Page 41
To cancel or change any flight remarks, enter:
RKC:FLIGHT
The system erases the previous entry and displays a clear screen again.
Error Responses
Field Explanation
SIZE The remark entry exceeds 160 characters.
Destination Remarks Creation (DRC)

It is possible to add remarks for a particular destination. Destination remarks go on every flight
with this particular destination. Therefore be careful when entering these remarks.
Enter:
DRC:DESTINATION
Response to DRC Entry:
►DRC:XS ATL
The cursor on the second line denotes the beginning of the Destination Remarks line. The
Start of Entry (►) must be erased before entering any remarks. To add a second or third line
of information, the entry must be preceded by a dash (-). The remark line has a maximum of
128 characters.
Entry:
►DRC:XS ATL
CHECK ALL VISA AND PASSPORTS
To display any remarks entered for a destination, enter: DR:DESTINATION
To cancel or change any destination remarks enter: DRC:DESTINATION
The system erases the previous entry and displays a clear screen again.
Error Responses
Field Explanation
SIZE Remarks exceed 128 characters.

Guide
Copyright © SITA Information Networking Computing 7. Flight / Destination Remarks
Page 42
8. Flight Information Displays and Updates
Flight Data Display (FDD)
A flight data display may be entered for any flight that has been 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, includes:
n Routing
n departure and arrival times (in local time)
n the (T) CND table number (for configuration)
n aircraft type and version
Master Flight (FDD:XS587/15MAR)
Explanation
Field Explanation
ATL Originating Station (with departure time of 1410).
JFK Next or Final Station (with arrival time of 1635).
T-32 CND Table Number for aircraft configuration.
737/A Aircraft Type and Version.

USA Inc.
Page 43
An Active Flight (FDD:XS587/.)
Note: The ‘.’ that concludes the FDD:XS587/. transaction indicates today’s date.
Explanation
ADJ 1510 / ETA 1735 Time adjustment from FIR.
1/00 LATE Hours and / minutes of schedule adjustment from FIR or FUI
transaction.
R:G-LMW P Aircraft registration number. Entered via FUI:.
IRREGULAR Location and reason for schedule adjustment. Entered via FIR
OPERATION DETAILS transaction.
SUPPLEMENTAL Entered via FIR transaction.

INFORMATION
Note: The FDD may be updated via the LMVD / FUI / FIR transactions.
A Code share Flight (FDD:711/.)

FDD displays T when the schedule is created in the DCS. For schedules created in SITA
Reservations, the configuration and classes appear (e.g., CDJ12/YBHMQ124). FDD also
displays codeshare flight numbers and days of operation.

Guide
Copyright © SITA Information Networking Computing 8. Flight Information Displays and Updates
Page 44
Explanation
***CODE SHARE*** LH5711 Designates code share flight.
FDDXS 711 Code share partners flight number
ATL 2300 Origination City.
T-195 DH8/C Schedule created in DCS.
MIA 2330 Destination City.
Flight Update Information (FUI)

Use this transaction to enter various items such as aircraft registration, gate number, aircraft
ramp/apron position, new ETD times, and new CND table numbers (for change of
configuration).
Enter:
FUI:FLT NUMBER/DATE/ORIGIN CITY/CODE/DATA
Response:
Accepted
To enter the aircraft registration GDBAH, enter:
FUI:XS587/./ATL/ARN/GDBAH
Note: The aircraft registration must be entered before LDP flight initialization. Also on transit
flights from non-DCS stations, the aircraft registration must be entered from the first
departure station.
To enter a gate number enter: FUI:FLIGHT/DATE/STATION/GATE/NUMBER
To change the gate number, use the same entry with the new number. If a gate number must
be deleted the transaction is:
FUI:FLIGHT/DATE/STATION/GATE/ERS
Note: The FUI transaction accepts any gate number entered, however only the gate
numbers entered in the AZ:STATION file are displayed on the SDD:FLIGHT screen.
Codes followed by * require additional data entry such as Time, Number or Registration.
Other codes/data entered are:

USA Inc.
Page 45
Code Explanation
BDT Enter New Boarding Time.
ETD/*. Enter New Estimated Time of Departure.
ETA/* Enter New Estimated Time of Arrival.
CANCEL Show Flight Cancelled out of a City.
CTN/* Enter New CND Table Number.
CTN/0 Return Flight to Original CND Table Number.
ARN/* Enter Aircraft Registration Number (System verifies if registration is a valid

registration listed in database).
GATE/* Enter Gate or New Gate Number.
POS/* Enter Aircraft Position.
GATE/ERS Erase Gate Number.
ARN/ERS Erase Aircraft Registration.
POS/ERS Erase Aircraft Position.
RTNS Return To Normal Status (put Flight back to original characteristics).
OUT/* Actual Departure Time (must come before OFF).
OFF/* Actual Take-Off Time.
ON/* Actual Landed Time (must come before IN).
OT Reopen Flight Status after LMVD shows Departed. Entered as /ETD/OT.
IN/* Actual Arrival Time (can be entered for all destinations).
NEWTMS/*/* New Estimated Departure/New Estimated Arrival Times. (These times will
override any times entered especially if mistake is made using LMVD message.)
If a new ETD involves a day change then it can be entered via FUI with +1.
FUI:FLT/DATE/STN/ETD/0100+1.
Notes: When changing the CTN number with the FUI after check-in has begun, a warning
message about the change was done will generate for LDP on the KF QUEUE.
RTNS deletes ALL changes made to the FDD display using the FUI, FIR or LMVD
transaction. Be very careful when using this transaction. The RTNS removes an aircraft
registration from the live LDP flight.
FUI Error Responses

Guide
Page 46
CITY Invalid city entered or missing.
DISPLAY/UPDATE User not authorized to display this entry for another station.
NOT ALLOWED
NEED OUT TIMES Attempted to set 'OFF' times before 'OUT' times.
NO CHANGE Entry ignored as not correct.
ORIGIN Attempt to set 'ARRIVAL' time for origin.
SKED CHANGE The BF:T or DFD is being displayed and has not been activated or
ignored.
SYSTEM ERROR There is something wrong with this entry, either re-check the data or
contact SITA Customer Support.
TIME RPTD Attempted to set 'ETD' after 'OUT' time entered.
Flight Irregular Operations (FIR)

The FIR: transaction sends flight irregular operation information, via the FDD display, to all
airline staff. This information is used for planning purposes, record keeping and customer
service.
Note: The FUI and FIR transactions overlap on transactions affecting the FDD: display.
Remember the FUI is used primarily to updates flight times (i.e., out / off, on / in, ETD / ETA,
and ARN / gate numbers). The FIR updates reasons, supplemental information and times
related to delays and diversions.
Enter: FIR:FLIGHT/DATE
Response of FIR Entry
Entering a Flight Delay 'REASON' Code and 'SUPPLEMENTAL INFORMATION'
Response of Returned Display after Transmission

USA Inc.
Page 47
Please note how the entry of the T updated the downline stations times.
Explanation: ARR INFO / DEP INFO
Field Explanation
0030 HHMM Hours and Minutes.
L Late. Maximum value for a late time is 68 hours 15 minutes.
E Early (Not shown in the example).
T Time correction is applied to arrivals and departures for all downline cities. Used in
conjunction with L and E (LT or ET).
INSERT
The INSERT field contains codes that apply to either the codes in the REASON field or to the
DCN entry in the Departure field.
Inserts accepted for valid codes in the REASON field are:
Valid Code Explanation

GMT 0200Z
PSBLD Possible delay
SUBJFD Subject to further delay.
NONE Clears the INSERT field for the city indicated (on same line).
REASON
These codes will appear on the FDD: display under IRREGULAR OPERATION DETAILS.
The city associated with the reason is also displayed.
The system accepts the following reason codes:
Code Explanation
ACCUM Accumulative
ALTNOP Alternate Operation
APTCND Airport Condition

Guide
Page 48
Code Explanation
ATC Air Traffic Control
ATCIN Air Traffic In
ATCOFF Air Traffic Out
ATCWXF Air Traffic and WX
BQ Balance Equipment
C Connection
CIQ Alternate Operation
CTA Crew turn around
CURFEW Curfew
DCN Decision
DEICG De-icing
FOFR See Remarks Supplemental Information
FOG Fog
FRZR Freezing rain
HLDG Holding
LDS Loading
MAINT Maintenance
NONE No Reason Applies
NOS No Stop
OLF Operating limits
ORIG Originating
PAS Passenger accommodation
PD Possible diversion
PNOS Possible No Stop
PSBLD Possible delay
PXLTN Possible Cancellation
Q Equipment

USA Inc.
Page 49
Code Explanation
QATC Equip due ATC
QMAINT Equipment Maintenance
QNEEDS Equipment Needs
QTA Equip turn-around
QWXF Equip due weather
RC Ramp congestion
RDX Ramp damage
RTND Returned
SFCWND Surface winds
SVS Servicing
THRU Late through
THRUT Late through all downline
TSTM Thunderstorms
WAF Winds Aloft
WTGTO Waiting take-off minimums
WXAPT Weather/airport conditions
WXF Weather
XLD Cancelled
The CTN field contains the CND table number (T-nnn) of the aircraft. This field is supplied
from the flight schedule or FUI entry and must agree with the aircraft registration number.

Guide
Page 50
T-10 CND Table number (Configuration) read from FDD display.
R:GS-737 ARN (Aircraft Registration Number) read from FDD: display.
Supplemental Information
At the bottom of the display there are a maximum of 14 lines of free format entries for the
'SUPPLEMENTAL INFORMATION'. This information will appear on the
FDD:FLIGHT/DATE display. Use the 'TAB' key to move the cursor at the correct start of entry
for each line. Please note that the maximum free format lines will decrease by one for every
flight leg over four. Example: four flight legs = 14 lines, five flight legs = 13 and six flight legs
will have 12 lines.
Other FIR Input Examples and Explanations

n NONE or NONET typed over an entry clear it from the FIR screen. This is required for
each manually entered item on the screen. Use the spacebar to remove extra characters.
n DCN. When an arrival or departure time for a transit city is not definite, enter this code in
the Departure field of the transit city in question. The time a decision will be made or
updated about the departure time must be entered in the INSERT field. In the “Entry
Where Decision Is Needed on Departure Transit City” example the insert time shows a
decision will be made at 2200 hrs GMT for possible cancellation MIALAX (PXLTN).
FIR Entry Where Decision Is Needed on Departure Transit City
FIR Response to DCN Entry

USA Inc.
Page 51
In the following examples, the INSERT field shows flight 300 is subject to a further delay.
FIR Entry
FIR Response
Error Responses
CITY Invalid CITY entered or missing.
IRR CODE Incorrect entry of REASON or INSERT code.
TIME Incorrect entry of time. The L may be missing.
NEED OUT TIME Attempted to set 'OFF' time before 'OUT' time.
NO CHANGE Entry ignored as not correct.
ORIGIN Attempted to set 'ARRIVAL' time for origin.
TIME REPEATED Attempted to set 'ESTIMATED' time after 'ACTUAL' time entered.
Note: If a delay time is entered via FIR then the maximum delay that can input is 51 hours.
DCS SITA Reservations Interface

The Flight Information Displays (FDC Function Codes) are available to SITA Reservations
staff. User Group 11 can update both FUI and FIR. All User Groups can display the FDD:
display. Updates to the FUI and FIR are allowed up to 15 days prior to the departure of a
flight. Any update shows as an ‘I’ on the SITA Reservations (AV) availability display, this
alerts Reservation Staff of an informational change on the flight.

Guide
Page 52
9. Inbound Outbound Passenger Display
Inbound Outbound Passengers
The IOD display can be entered for any flight having inbound and outbound flight information.
The IOD display provides information to include inbound and outbound connecting flights,
origin and destination cities, passengers and baggage.
The entry for IOD is:
IOD:XS087
IOD display:
Status Indicator Description

IOD Transaction entry code.
XS087/. Flight number/date.
ATL/4 City and message address table (CX) number (Range 0 - 99).
OP Flight is open for check-in.
Note: For passengers that are through checked, IOD displays a class breakdown.
Other Status Indicators are:
Status Description
Indicator
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.

USA Inc.
Page 53
Status Description
Indicator
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:

NUM Numeric Check-in (no PNL).
PNM Partial Name (same as numeric except passengers with special
requirements displayed in system).
NON Non-Automated station for SITA DCS.
320/A Aircraft type and version.
GTD Passenger gate number.
POS Ramp position (used with bus gates).
BDT Passenger boarding time.
SD Standard time of departure.
ED Estimated time of departure.
Inbound:
Status Description
Indicator
FLT# Inbound Flight Number.
ORG Originating City.
ETA Estimated Time of Arrival that displays for online connections. The time comes
from the PNL.
PAX Number on Inbound Passengers Onboard.
BAGS P/W Inbound Baggage in Pieces and Weight.

Guide
Copyright © SITA Information Networking Computing 9. Inbound Outbound Passenger Display
Page 54
Outbound:
Status Description
Indicator
FLT# Outbound Flight Number.
DST Destination City.
ETD Estimated Time of Departure that displays for online connections. The time
comes from the .O/ element in the PNL.
PAX Number of Outbound Passengers Onboard. The passengers are displayed by

class for online connections only.
BAGS P/W Outbound Baggage in Pieces and Weight.

USA Inc.
Page 55
Guide
Copyright © SITA Information Networking Computing 9. Inbound Outbound Passenger Display
Page 56
10. Protective Cover
Protective Cover (PO)
A supervisor can stop all check-in activity on a flight by entering the following transaction:
PO:FLIGHT NUMBER
Although CI and CCL are accepted while in PO, LDP still shows the flight as CKI open. The
response is: ACCEPTED.
This entry stops all transactions (other than displays) from being done, except by the CRT
entering the PO. The SDD screen displays PC (Protective Cover) in place of OP (Open), so
anyone looking at the display knows supervisory transactions are being done to the flight. The
CFL:S screen also displays a P after the city and before the Arrival time.
SDD and CFL Showing Protective Cover:
SDD
SDD: XS400/30JUN BUD/0 PC/NAM
CFL
Once the changes are completed remove the PO by entering:

PO: - FLIGHT NUMBER
The response is: ACCEPTED.
It a supervisor needs to remove the ‘PO’ from the screen which was entered on another CRT,
this can be done by entering:
POC: - FLIGHT NUMBER
Note: The PO must be removed before Closing or Releasing the flight to LDP otherwise any
passengers checked-in while the PO was on the flight (check-in can only be done on the CRT
that controls the PO) will not be transferred to LDP and thus the loadsheet could be issued
with incorrect passenger figures.

10. Protective Cover
USA Inc.
Page 57
Error Responses
AUTHORITY The CRT removing the PO is different from the CRT that entered it.
FLT The input flight was cancelled.

CANCELLED
OPTION Invalid option specified.
UNABLE The PO has already been entered, or an attempt was made to remove PO when
it was not set.

Guide
Copyright © SITA Information Networking Computing 10. Protective Cover
Page 58
11. Seat Map Characteristic Changes
Seat Map Characteristic Changes (SCC)
It is possible to change the seat map for a specific flight/date with the following seat or row
characteristics.
Note: A seat or row may have multiple characteristics; however, only one characteristic will
appear. Removal of the displayed characteristic may reveal a secondary seat characteristic.
This can cause confusion during check-in because the secondary characteristic (that is not
displayed) may not permit assignment. Also, conflicting characteristics cannot be applied to a
seat. For example, an Emergency Exit (E) seat cannot be assigned for an infant (I).
Row Codes
Code Explanation
Q Quiet row.
S Smoking row.
W Overlooking Wing row.
Y FQTV Tier Row.
Seat Codes
Code Explanation
B Bassinet for infant.
C Last to be Used seat (or MP seat).
D Handicap seat.
E Emergency Exit seat.
H Bulk-Head seat.
I Infant seat.
K Stretcher seats.
L Extra Leg-Room seat.
N No Movie Viewing seat.
R Restricted Recline seat.
U Unaccompanied Minor seat.

USA Inc.
Page 59
After first displaying the seat map (SE:FLIGHT/DATE) the entry to add a seat or row
characteristic is:
SCC:+CODE/SEAT (or ROW), SEAT (or ROW);+CODE/SEAT (or ROW)
A ',' (comma) is inserted between the different seats or rows, and a ';' (semicolon) between
different codes.
SCC:+U/04A,04C;+I/12
To delete a seat characteristic enter:
SCC:-CODE/SEAT (or ROW),SEAT (or ROW);+CODE/SEAT (or ROW)
SCC:-C/23-25
It is possible to add and delete seat or row codes in the same entry.
For example if you need to change the Smoking and No Smoking rows use the following
procedure:
SCC:-S/12-15;+S/16-20
Note: The system defaults all rows to a 'No Smoking' status unless an S is specified for
Smoking. There is no code for No Smoking rows. The N is used for 'No movie viewing seat'.
The system accepts the following seat or row entries:
7A ONE seat 7 A WHOLE row
L7 The LEFT side of one row R7 The RIGHT side of one row
7A-C Seats ABC of one row 7-10 Rows 7, 8, 9 and 10
7-10A Seat A only of rows 7, 8, 9 and 10 7-10A-C Seats ABC of rows 7, 8, 9 and 10
L7-10 The LEFT side of rows 7, 8, 9 and R7-10 The RIGHT side of rows 7, 8, 9 and
10 10

Guide
Copyright © SITA Information Networking Computing 11. Seat Map Characteristic Changes
Page 60
Error Responses
CLEAR BUFFER ZONE VIA C seats being removed are 'MP' seats and not 'last to be used'
MP seats.
CONFLICT The code entered is already present and conflicts with another.
FORMAT Invalid entry.
FLT CLOSED FOR LDP The input flight has already closed for check-in.
FLT CANCELLED The input flight has been cancelled.
NO DISPLAY The seat map (SE) was not displayed first.
NO SEAT SELECT One leg of routing does not have seating.
PROT COVER Flight is under PO.
ROW Invalid row, or sequence of rows, entered.
SEATS The specified seats do not exist on the seat map.
SUD Invalid seat/row code entered.
UNABLE Invalid seat/row area or code X was used.

USA Inc.
Page 61
Guide
Copyright © SITA Information Networking Computing 11. Seat Map Characteristic Changes
Page 62
12. Flight Control Limits
GOSHOW Limits (GS)
The GS or GOSHOW acceptance limits display at the bottom left of the SDD screen. The
control limits set for the acceptance of revenue standby passengers always default to zero.
The GS figures show 0 for each master class up to a maximum of five classes on the SDD. If
no GS acceptance figures are entered, all NOREC and URES revenue passengers go on
standby at check-in time. If GS figures are added after passengers are shown on the standby
list the system accepts according to the priority of the PZ table (providing the automatic
standby acceptance is on).
To add GS acceptance figures, enter:
GS:FLIGHT CLASS NUMBER OF SEATS GS:XS100 Y 10

On multi-sector flights the boarding city must also be entered after the class.
GS:XS945 Y ATL 2
If no date is specified, the system defaults to today's date. However in some cases on multi-
sector flights, if one of the flight segments departs the following day, then it is necessary to
enter that day's date with the GS entry for that segment, otherwise you will get the response
'DATE'.
GS:XS537/+ Y MIA 4
Note: The date comes before the class, and the class comes before the destination.
To delete any GS figures displayed, enter:
GS:FLIGHT CLASS 0
To amend any GS figures displayed, it is possible to do it two ways:
1. Use the same entry as the initial entry, by entering the new figures. This over-writes any
previously entered figures.
GS:XS100 Y 8
2. Use a '+' or '-', and enter the number of seats to add or reduce from the previously entered
figure.
GS:XS100 Y -2

USA Inc.
Page 63
Note: Goshow (GS) on flights must be opened to follow-on cities to carry the revised (GS)
limits.
If GS figures are present on a flight, these figures are decreased as NOREC and URES
passengers are accepted. If the GS figures are adjusted after the passengers have been
accepted, it will have no affect on those accepted passengers. If an accepted GS passenger
is off loaded to standby (using the AC transaction) then the GS figure will increase again,
however if an accepted GS passenger is off loaded (PW) then the GS figures do not get
adjusted.
Note: If there is only one entered for the GS figure and two URES or NOREC passengers
check-in together, the system will not accept one and put the other one on standby, instead
the system assumes they want to travel together so it puts them both on standby. The
supervisor can decide whether to accept one or both of them using the AC transaction. Also if
the GS figures are entered after some URES or NOREC passengers are already on the
standby list (SB:FLIGHT), then the system will onload them in order of priority, up to the GS
figure entered.
GS limits are ignored during and after initial flight close.
Error Responses
AUTHORITY The CRT entering the transaction is not the first boarding airport, or the
previous station has not yet closed and released the flight.
CITY Invalid destination specified.
CLASS Invalid class code specified.
CLASS GROUP Invalid class or sub-class code was entered.
CLASS GROUP Class code is missing.

SPEC REQUIRED
DATE Invalid date specified.
FLT CANCELLED The input flight has been canceled.
FLT NBR Invalid flight number specified.
NO ACTION The limit is already set to the required figure.

INDICATED
NUMBER The number input is too large.
SIZE Input figure is greater than class capacity.

Guide
Copyright © SITA Information Networking Computing 12. Flight Control Limits
Page 64
PAD Limits (ID)
The ID acceptance limits for PAD passengers show at the bottom of the SDD screen. The
functionality is the same as that of the GS acceptance limits. The entry to add ID figures is:
ID:FLIGHT CLASS NUMBER OF SEATS ID:XS100 Y 10
The response is: ACCEPTED

On multi-sector flights the BOARDING CITY must also be entered after the class.
Example:
ID:XS945 Y ATL 2
Note: If no date is specified, the system defaults to today's date. However in some cases on
multi-sector flights, if one of the flight segments departs the following day, then it is necessary
to enter that day's date with the ID entry for that segment, otherwise you will get the response
'DATE'.
ID:XS537/+ Y MIA 4
Note: The date comes before the class, and the class comes before the destination. To
delete all ID figures displayed, enter:
ID:FLIGHT CLASS

USA Inc.
Page 65
To amend any ID figures displayed, it is possible to do it two ways:
1. Use the same entry as the initial entry, by entering the new figures. This will over-write any
previously entered figures. For example:
ID:XS100 Y 8
2. Use a '+' or '-', and enter the number of seats to be added or reduced from the previously
entered figure. For example:
ID:XS100 Y - 2
or
ID:XS100 Y + 2
ID limits are reduced by 2 (-2) for Y class or increased by 2 (+2).
Error Responses
AUTHORITY The CRT entering the transaction is not the first boarding airport, or the
previous ST station has not yet closed and released the flight.

SPEC REQUIRED
DATE Invalid date specified.
NO ACTION The limit is already set to the required figure.

INDICATED
Numeric Limits (HL)

It is possible to put a numeric restriction on the number of passengers to accept at check-in for
a particular class and destination. Any restrictions entered are displayed on the SDD screen.

Guide
Page 66
Enter:
HL:FLIGHT CLASS DESTINATION LIMIT
HL:XS298 Y FRA 88
To delete any HL figures displayed, enter:
HL:FLIGHT CLASS DESTINATION HL:XS298 Y FRA
It is possible to amend the HL by using a '+' or '-', and entering the number of seats to add or
reduce from the previously entered figure.
HL:XS298 Y +2
Note: The manually entered numeric limit cannot be set lower than the number of accepted
passengers or the space protected seat count.
Error Responses
CLASS GROUP SPEC Class code is missing.

REQUIRED
NO ACTION INDICATED The limit is already set to the required figure.
UNABLE A '+' or '-' limit was entered for a non-existent limit.

USA Inc.
Page 67
Space Protection Limits (SX)
When both stations use the SDCS system, it is possible to protect space to limit the number of
passengers to accept at check-in for a particular class and segment. Any restrictions entered
are displayed on the SDD screen, for example:
SX:FLIGHT CLASS SEGMENT LIMIT SX:XS884 Y ATLAMS 10

To release any SX figures displayed, enter:
SX:FLIGHT CLASS SEGMENT 0 SX:XS884 Y ATLAMS 0
It is possible to amend the SX by using a '+' or '-', and entering the number of seats to add or
reduce from the previously entered figure.
SX:XS884 Y ATLAMS -4
Note: The manually entered space protection limit cannot exceed the class capacity.
Error Responses
SPEC REQUIRED Invalid destination specified.

DESTINATION
NO ACTION INDICATED The limit is already set to the required figure.
UNABLE The total amount of space protected exceeds the class capacity.

Guide
Page 68
13. Reserving / Blocking Seats
Reserve Seats for Individual Passengers (CRS)
After a PNL is loaded onto a flight it is possible to reserve seats from the seat map for specific
passengers.
To do this, display the PS list of passengers or the PDD record of a particular passenger and
enter the following:
PU:# ITEM NUMBER, R SEAT NUMBER PU:#1,R7A
The system places a P on the seat map for this seat number and displays CRS (check-in
requested seat) on the passenger record, and at check-in the passenger will be allocated this
seat. It is not possible to use the PU entry for pre-seating more than one entry number at the
same time, however it is possible to do it with the PA entry.
To pre-reserve seats for more than one passenger, enter:
PA# ITEM NUMBER BY RANGE,R SEAT NUMBERS BY PA:#1-4,R17A-D

RANGE
Reserve Group Seats (RS)

It is possible to reserve seats on the seat map for a group of passengers so that as they
check-in they will be allocated seats in this reserved area.
After displaying the seat map (SE:FLIGHT), enter:
RS:SEAT NUMBER or ROW, SEAT NUMBER or ROW, etc.
RS:8-12
Seats reserved by this entry are displayed 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 entry:
PA:ENTRY NUMBER, P/W BAGS, SNRGRP
PA:2,1/12,SNRGRP
If an actual seat number is desired show the seat numbers after the SNRGRP entry:
PA:ENTRY NUMBER,P/W,SNRGRP12A (or SNRGRP12A-C etc.).
The G seats may be pre-assigned also: (PA#1-10,SNRGRP)
To delete any G seats on the seat map, enter:
RS: - SEAT NUMBER or ROW
Error Responses

USA Inc.
Page 69
AUTHORITY Access not allowed.
UNABLE Seat has already been used or blocked.
Block Seats (BS)

It is possible to block seats on the seat map and reduce capacity for any particular class or
segment. This could be for reasons such as a weight restriction or critical balance conditions.
Adjustments are displayed on the SDD screen.
After displaying the seat map (SE:FLIGHT), enter:
BS:SEAT NUMBER
BS:ROW, SEAT NUMBER
BS:ROW etc.
BS:30-35
Seats reserved by this entry will display an X on the seat map. If the flight is free seating then
the BS transaction must contain a class and the number of seats required to be blocked
(example BS:Y4).
To delete any X seats on the seat map, enter:
BS: - SEAT NUMBER or ROW

Guide
Copyright © SITA Information Networking Computing 13. Reserving / Blocking Seats
Page 70
To delete any blocked seats on a free seating flight, enter:
BS: - CLASS NUMBER OF SEATS
Error Responses
Allot Seats (AL)

It is possible to allot area seating for local boarded passengers at check-in for a particular
flight segment and thus prevent other stations from checking-in passengers into these seats.
After displaying the seat map (SE:FLIGHT/.,SEGMENT), enter:
AL:SEAT NUMBER
AL:ROW, SEAT NUMBER
AL:ROW, etc.
AL:17A-C
Note: It is very important to display the correct flight segment; otherwise the wrong
passengers may be allocated these seats. Also, be aware any non-allotted seats out of the
segments origin city will be assigned by the system first.
Seats allotted by this entry will either display as an 'A' or an 'O' on the seat map depending on
the flight segment displayed.
The 'A' indicates that these seats can be used for passengers flying the displayed segment.
Thus, if a flight flew from A - B - C and seats were allotted from B - C the seat map for
segment B - C would show an 'A' on the seat map.
The 'O' indicates that these seat have been allotted for passengers flying a different segment
and therefore should not be assigned (unless forced by an agent using the SNR item with the
PA entry). The 'O' would appear on segment A - B and A - C in the example flight of the
preceding paragraph.

USA Inc.
Page 71
To delete any A seats on the seat map, enter:
AL: - SEAT NUMBER or ROW AL: - 17A-C
Note: Seats that have already been allotted (T), blocked (X), or reserved (V / R / P) cannot
be overridden by the AL transaction.
The SNR entry with a specific seat request is the only entry used to override an allotted seat
request (PA1,SNR12A or PU1,SNR12A).
Error Responses

Guide
Page 72
Transit Seats (BX)
It is possible to enter transit seats on the seat map for transit flights where a SOM from a non-
automated station was not received or to correct a SOM where an adjustment is needed. Any
entries update the SDD screen.
Note: Any transit seats entered on the seat map will be recorded on the
LPAD:FLT/DATE/PAX screen in LDP, but unless LDP receives a LDM, the gender details
must be manually added to the LPAD:FLT/DATE/PAX1 screen (by the load planning agent).
Enter:
BX:FLIGHT CLASS SEGMENT BX:XS777 Y MEXJFK 17A-C,19F,24A,25A-B,25F

SEAT NUMBER or ROW
Response: ACCEPTED.
Seats Reserved by this Entry will Display a T on the Seat Map
To delete any T seats on the seat map, enter:
BX:FLIGHT CLASS SEGMENT - BX:XS777 Y MEXJFK 17A-C,19F,24A,25A-B,25F

SEAT NUMBER or –ROW
BX:XS777 F MEXJFK -03C

Note: When entering the segment details, it is important that you enter the origin city and
destination and not boarding city and destination city. Otherwise the passenger details will get
added to the 'local' checked-in passengers and not in the 'transit' figures on the SDD screen.
On free seating flights, where it is still necessary to enter the transit details, use the same
transaction to add or delete the figures only the actual seat numbers are omitted, for example:
BX:FLIGHT CLASS SEGMENT TOTAL BX:XS777 F MEXJFK 6
Add BX Seats on a Flight with an Aircraft Type Change Downline

To enter BX seats on a multi-sector flight with an aircraft type change downline, two seats for
the same transit passenger must be entered (with a ‘;’ semicolon between the seats) even
though the same seat may exist on both aircraft types, enter:
BX:FLIGHT CLS SEGMENT 2A;2A BX:XS777YMEXJFK 2A;2A

USA Inc.
Page 73
To enter Transit seats for more than one passenger, enter:
BX:FLIGHT CLS SEGMENT BX:100YATLLLW 10A-C,12AB,14C;10A-C,12AB,14C

SEAT,
SEAT,SEAT;SEAT,SEAT,SEAT
Error Responses
CITY Invalid CITY pair entered.
CLASS Invalid class specified.
FLT CLOSED/CANX Flight is closed or canceled.
FLT NBR Invalid flight number.
Releasing Reserved Seats (RA)

The RA transaction allows the supervisor to release reserved seats for use by other
passengers. This may become necessary on an 'overbooked' flight, when near flight close-
out, there are only reserved seats left on the seat map. This can cause booked passengers
(who do not have reserved seats) to be put on standby as they check-in. These can be seats
reserved by CRS (check-in reserved seat), by RES (reservation reserved seat), or by ASR
(advance seat request).
Enter:
RA:FLIGHT CLASS SEGMENT, CODE SEAT NUMBER
Entries are:
Release all R seats:
RA:XS585YATLMIA,RES
Release all P seats:
RA:XS585YATLMIA,CRS

Guide
Page 74
Release all V seats:
RA:XS585YATLMIA,ASR
Release all R/P/V seats:
RA:XS585YATLMIA,ALL
Release R seat 17A:
RA:XS585YATLMIA,RES17A
Release seats 12A,19C:
RA:XS585YATLMIA,CRS12A,19C
Error Responses
CITY Invalid CITY pair entered.
CLASS Invalid class specified.

USA Inc.
Page 75
Guide
Page 76
14. Passenger Standby Acceptance
Manual Selective Standby Acceptance (AC)
If there are no GS or ID figures entered on the SDD screen, NOREC or URES passengers
will go onto the standby list at check-in. The system puts the passengers into priority order
(check PZ:AIRLINE for priority table). At initial flight close, depending on how many open
seats are available, the system onloads the standbys up to aircraft capacity. However, it is
possible for a supervisor to selectively onload and offload standby passengers at any time
during the flight.
The AC transaction must be preceded by a previous passenger list (PS or SB) or passenger
record (PDD) display.
After displaying the required screen, enter:
AC:ENTRY NBR AC:1-4

(a maximum of 20 entry numbers can be (accept entry numbers 1, 2, 3, and 4)
specified)
AC:-ENTRY NBR AC:-1-4
(remove entry numbers 1, 2, 3, and 4)
The response should be a boarding card and seat number for the selected passenger.
The AC transaction overrides any other flight limits and ignores any GS or ID figures.
It is possible to specify a particular seat request with the entry:
AC:ENTRY NBR, SEAT REQUEST AC:2,R17A

or
AC:1,RS
Also it may be necessary to accept or remove a standby passenger into a jump seat.
Enter:
AC:J ENTRY NBR AC:J2
AC:J ENTRY NBR AC:-J2
Manual System Standby Acceptance (GS/ID)

At any time during check-in and before initial flight close, if a supervisor wants to onload some
standby passengers but prefers to let the system do it in priority order, then by setting the
required number of seats in the GS or ID entries, these passengers will be accepted (up to the
specified figures) and issued seat numbers. This is based on the Automatic Standby
Acceptance (ASA) parameter being turned on. Please refer to Section 0 and 0.

14. Passenger Standby Acceptance
USA Inc.
Page 77
Automatic Standby Acceptance (GS/ID)
If a flight is not fully booked, and some GS or ID figures are entered on the SDD screen, then
at check-in, any NOREC, URES, or ID passengers are accepted (up to the specified figures)
and thus prevent these passengers from first going to the standby list.
Manual Offload Passenger to Standby (AC:-)

It may be necessary to offload a checked-in passenger to standby (perhaps a standby ID
passenger was checked-in earlier, and the flight has become full and there are still some
booked revenue passengers to check-in).
The AC transaction must be preceded by a previous passenger list (PS or SB) or passenger
After displaying the required screen, enter:
AC: - ENTRY NBR
Note: This will off-load the passenger to standby. At that time the standby list is checked and
if there are any passengers of a higher boarding priority they will be accepted. If there are still
seats remaining, then the off-loaded passenger will be reaccepted. To prevent this, the "-"
must be followed by an "X" (AC:-X1) to prevent any further reconsideration of this passenger.
Enter:
AC: - X ENTRY NBR
This entry puts the passenger on standby and prevents automatic re-acceptance on the flight.
Setting GS or ID figures or entering the CI entry will not cause acceptance.
The only way to accept this passenger again is by using the AC transaction.
Transit passengers may be removed at the transit point by displaying the PS list from the
origin city to the destination city and offloading the passenger with the (AC:-X ENTRY No.)
transaction. This transaction is performed by staff at the transit city.

Guide
Copyright © SITA Information Networking Computing 14. Passenger Standby Acceptance
Page 78
15. Passenger Notification
Passenger Notification (NO)
When a passenger's check-in record is modified prior to check-in or an entry is made that
could cause the passenger to go on standby the system puts the passenger on the 'NEED
NOTIFICATION' list. The list warns the agent or supervisor this passenger needs to be
advised about the change, and perhaps a new boarding card issued. Examples would be
upgrading/downgrading, assigning seats or messages prior to check-in, or adding a
URES/NREC passenger.
Passengers having URES or NREC classifications may be cleared on to a flight by setting GS
or ID figures. The passengers will have boarding numbers (BN) issued but remain on the
'NEED NOTIFICATION' list until a boarding card is issued (BC) or a (NO) transaction is
performed.
Those passengers accepted with an AC transaction or accepted with a PA transaction (pre-
assigned seats) are removed from the list and have no need for the BC or NO transaction.
Any passengers that go on the notification list appear on the SB:FLT NBR passenger list. The
list must be displayed before the notification or boarding card entry is made.
NEED NOTIFICATION List with SB List
The entry to confirm notification is:

NO:ENTRY NUMBER
The entry to issue the boarding card is:
BC:ENTRY NUMBER
These entries will delete them from the list. It is possible to enter a range of numbers in the
same entry using the notification entry:
NO:1-6
(For entry numbers 1 to 6).
At initial flight close (CI:FLIGHT) the system will display a list of the passengers that need
notification providing the automatic standby acceptance parameter is enabled.
NEED NOTIFICATION LIST When CI Entry Is Made

15. Passenger Notification
USA Inc.
Page 79
Acceptance is subject to seating restrictions (e.g., no available infant seats) and other limits
(e.g., available weight – UAW). If this happens, the message ACCEPTANCE REJECTED is
returned.
Error Responses
GATE ONLY The gate is now in control of the flight.
NO ACTION IND The entry is correct but no action is required.
NO DISPLAY A previous passenger record or list is required.
PSGR ID Invalid passenger entry specified.
TRAVEL TIME Insufficient time between CRT and gate.

Guide
Copyright © SITA Information Networking Computing 15. Passenger Notification
Page 80
16. Flight Close-Out Procedures
Initial Flight Close (CI)
The initial flight close can be entered at any time by the supervisor, enter:
CI:FLIGHT
This transaction does not stop check-in, it onloads any standby passengers, provided the
automatic standby acceptance parameter is set to on and there are open seats available. This
transaction has to be entered even if there is no standby passenger. Once the CI transaction
is entered it overrides any flight limits such as GS or ID figures that were entered earlier.
On initial Flight Close, CI:Flight/date,P the system checks if there are seats in the required
class to accommodate standbys. If seats are available the standbys are onloaded.If seats are
not available the system checks for PAD passengers in the same class of travel and if any
offloads them and onloads the revenue standby passengers. Any remaining standby
passengers will be upgraded and seated in the next level Master class if seats are available or
if PAD is available.
The following transactions may be used when standby passengers are present:
CI:FLIGHT/DATE,R Release all Reserved seats (V,R,P,+) from seat map.
CI:FLIGHT/DATE,P Offload PAD passenger to accept REVENUE passengers.
CI:FLIGHT/DATE,U Accept standby passengers and UPGRADE if required.
CI:FLIGHT/DATE,PU Do both (system does P first then U).
Note: It is possible to delete the Initial Flight Close (CI) and revert the flight to OPEN state
again.
Enter:
CI: - FLIGHT
To close the flight without accepting any standby passengers, enter:
CI:X/FLIGHT
Note: It is possible to re-open the flight (CI:-FLT), and re-enter CI:FLT to allow the system to
accept any standby passengers.
Error Responses
AUTHORITY Agent not signed-into correct station.

USA Inc.
Page 81
FLT INITIALLY CLOSED CI entry has already been entered.
PREVIOUS STN NOT Flight not final closed at previous station.

CLOSED
Flight Close and Release to LDP (CCL)

Once all the passengers have checked-in, the flight must be closed and released to LDP so
the load sheet can be issued, enter:
CCL:FLIGHT
The response is: ACCEPTED/CITY CLOSED FOR LDP.
This transaction inhibits any further check-in on that flight unless the flight close status is
removed.
To remove the flight close status, enter:
CCL: - FLIGHT
Note: Once a flight has been released to LDP, check with LDP before re-opening the flight
for check-in. If the flight has been closed in CKI and LDP, and then the flight is re-opened in
CKI only, any changes to the checked-in passengers or baggage is not transferred to the LDP
application, unless the flight is re-opened in LDP.
Error Responses
AUTHORITY Agent not signed-into correct station.
DOWNLINE STN INITIALLY Check-in re-open is not allowed as the next destination has
CLOSED already entered CI.
FLT INITIALLY CLOSED CI entry has already been entered.

Guide
Copyright © SITA Information Networking Computing 16. Flight Close-Out Procedures
Page 82
NO CCL Check-in not complete at previous station.
NO CI CCL has been entered before a CI entry.
Flight Release and PAX Message Dispatch (CCF)

For flights where Check in is linked to load planning, a warning message is sent at two
intervals. The pre-conditions are:
n The flight has been released in Load planning but final closeout is not done in Check in
(CCF),
n The parameter ‘URALRT’ is set to ‘1’, and
n The new message address ‘FCW’ is specified in the CX table.
Once the flight is released in Load planning, the internal program checks if the final closeout
for the flight is done in Check in (i.e. CCF).
If final closeout for the flight is done, no alert message is generated. However, if the final
closeout is not done, then alert messages are sent at two intervals. The first at 20 minutes
after a Flight is released in LDP and the second at 30 minutes after the Flight is released in
LDP. Both messages are sent to a new address ‘FCW’ specified in the CX table.
FCW added to the CX table below.
After 30 minutes the following message is sent:
After 20 minutes the following message is sent:
Unclosed Flights Archived to History (CCH)

The check-in Complete Close History (CCH) function allows a supervisor or control agent to
close flights for subsequent purging from the system and storage on the CKI history tape
when no CCF function was entered. No other processing is performed and no messages are
generated.

USA Inc.
Page 83
The CCH transaction completes the check-in close process for the flight or flight boarding
airport. An 'ACCEPTED/FLT CLOSED' response is returned if the transaction is for the
entire flight, or 'ACCEPTED/CITY CLOSED' response is returned if the transaction is for a
flight boarding airport. Transactions attempting to modify a flight closed by the CCH
transaction receive a "FLIGHT ARCHIVED” response.
The entry to Complete Close History a flight for all airports is:
CCH:FLIGHT/DATE
The entry to Complete Close History a flight out of a specific airport is:
CCH:FLIGHT/DATE AIRPORT
It is possible to remove the CCH by entering:
CCH: - FLIGHT/DATE
This transaction is needed in case a flight was archived in error. The CCH transaction will not
send any messages.
Note: The CCH transaction is used for past date flights only.

Guide
Copyright © SITA Information Networking Computing 16. Flight Close-Out Procedures
Page 84
17. Passenger Excess Baggage Waiver
Passenger Excess Baggage Waiver (JEM)
The JEM transaction allows the supervisor to increase a passenger's baggage allowance
(before check-in). For example, a courier may have pre-paid the excess baggage. This will
prevent any excess baggage charges at check-in.
The JEM transaction must be preceded by a previous passenger list (PS) or passenger
After displaying the required screen, the entry for XBAG by Weight KGS is:
JEM:# ENTRY NUMBER,XBAG WEIGHT KGS JEM:#1,XBAG 10 KGS
In this example the passenger is allowed to have 10 KGS above his normal allowance.
The entry for XBAG by PCS:
JEM:#ENTRY NUMBER,XBAG PCS JEM:#1,XBAG 2PCS
In the entry, the passenger is allowed two pieces above his normal allowance.
It is possible to specify ALL instead of WEIGHT KGS or PCS, in which case the passenger is
allowed an unlimited amount of excess baggage.
JEM:#1,XBAG ALL
PS List with Passengers Having Excess Baggage Waiver
PDD Having Excess Baggage Waiver
Error Responses

17. Passenger Excess Baggage Waiver
USA Inc.
Page 85
DUP A duplicate input was entered.
ITEM The input code is not XBAG.
PAX STATUS CONFLICT The '#' item was omitted in the entry.
PSGR ID Invalid entry number specified.

Guide
Copyright © SITA Information Networking Computing 17. Passenger Excess Baggage Waiver
Page 86
18. Agent Cash Drawer / Close (JAD)
The Agent Cash Drawer
The collection of airport taxes (APT) and excess baggage charges (EXB) are not always
handled by DCS staff. Some airlines and handling companies collect charges at the check-in
counter. Others process the baggage and send the passenger to a ticket counter or cashier
for payment of the excess baggage or airport tax.
To provide agent accountability for the collection of these charges, a cash drawer is
maintained for each agent sign.
The JAD transaction allows the supervisor to display an agent's cash drawer file and
optionally closeout the cash drawer.
JAD Input
The JAD function is used to collect airport taxes and excess baggage charges. JAD input
format entry is:
JAD: AGNT-NO / TYPE / CLOSE
Field Explanation
JAD: Function designator.
AGNT-NO Agent Identification Number (1-7n).
TYPE Display type:

PT - Airport tax display
XB - Excess baggage display
CLOSE Optional input to closeout the agent cash drawer file.
Request a JAD display for Agent Number 1 for the excess baggage fees.
JAD:1/EXB
Request a JAD display for Agent Number 100 for airport tax fees.
JAD:100/APT
Request a JAD display for Agent Number 88 for excess baggage fees and closeout the
cash drawer.
JAD:88/EXB/CLOSE

USA Inc.
Page 87
JAD Output
The JAD transaction verifies the agent number and then reads the agent record to verify
excess baggage or airport tax information exists.
The airport tax is collected when the agent re-transmits the check-in response:
-EXB:1/3PC/CASH/FOR3 (Supplied by JXD/JCD Tables)
EXCESS BAGGAGE CHARGE/UNIT $ 6.0
BOARDING PASS PRINT INHIBITED
JAD for a Cash Drawer
A tax for an airport is set up when an airline or handling company advises SITA DCS of the
tax and that the airline will collect it. The tax is entered into a programming table, so when the
agent checks in a passenger and enters APT with the PA or PU function the tax shows as
collected. The tax is divided according to adult / child. The currency codes are FOR/USD/DFL
and LUF.
JAD Airport Tax Cash Drawer Display
If the number of flights displayed is more than 16 a SUB-TOTAL line appears followed by the
GRAND TOTAL line.
When using the CLOSE option with the JAD, the screen displays and must be printed. Any
request to redisplay the screen gives the response (052 - NO INFO) because all information is
cleared to zero.

Guide
Copyright © SITA Information Networking Computing 18. Agent Cash Drawer / Close (JAD)
Page 88
Error Responses
ACTION Invalid action (TYPE) code.
AGENT ID Invalid agent number.
FORMAT The input is not the correct input format.
NO INFO The requested agent number has collected no excess baggage or

airport tax fees or the Cash Drawer has been closed and not
recent action.

USA Inc.
Page 89
Guide
Copyright © SITA Information Networking Computing 18. Agent Cash Drawer / Close (JAD)
Page 90
19. Passenger / Baggage Message Displays
Checked-In Passenger Baggage Display (JB)
The JB transaction allows the agent to display the checked-in baggage by weight and class,
plus any transfer baggage, for each flight segment.
Enter:
JB:FLIGHT/DATE JB:XS120/.
JB response:
Note: The 'TRANSFER BAG WEIGHT' is excluded in the F and Y figures, and it is not
specified by class. It is the total amount of baggage of passengers who are transferring to
another flight at their specified destination on this flight.
Error Responses
AUTHORITY Agent not signed-in to correct station.
FLIGHT NUMBER Invalid flight number specified.
Manual Generation of Departure Messages (LR)

The LR transaction allows the agent to manually dispatch a copy of any required passenger
message to a printer PID, VDU, type A or type B address, for example enter:
LR:FLIGHT/DATE/STN/MESSAGE/ADDRESS/ADDR LR:XS589/./ATL/PSM/1390/
ESS VDU
This dispatches a copy of the PSM to PID number 1390 and the requesting VDU. If no
address is specified then the message goes to the VDU inputting the entry.

USA Inc.
Page 91
LR:XS299/./ATL/COM
It is also possible to request all messages with one entry:
LR:FLIGHT/DATE/STN/ALL
Addressing Options (VDU / N / HC)

There are two addressing options other than VDU. The N address option extracts addresses
from the CX table for those airports specified to receive the messages. An HC input uses the
address of the associated PID hard copy printer.
Error Responses
ADDRESS An invalid address is specified or the HC input was used and no
associated hard copy printer address exists for the VDU.
CITY The airport is not a departure airport on the input flight route.
COUNT Too many addresses of the same type were specified.
FLT NBR The flight number field or airline is invalid or the flight requested is
not operational.
MSG TYPE The message type is not one of the check-in departure message
type codes.
TYPE The message type is not valid for the flight's type of check-in.
Passenger Departure Messages

Passenger messages (are dispatched to):
API Advance Passenger Information Message (requesting country).
APL Accepted Passenger List
BSM Baggage Source Message (hard coded in system xxx BS xx,

where xxx = departure city and airline.) NOT ENTERED ON CX
TABLE / NO LR.
BTM Bag Transfer Message (Entered on CX table plus system hard

code).
COM Closeout Message (all stations).
ETL Electronic Ticketing List.
EXB Excess Baggage Charges by Agent

Guide
Copyright © SITA Information Networking Computing 19. Passenger / Baggage Message Displays
Page 92
FTL Frequent Traveler List Message FQTV (accounting system
address of host, handled carrier or code share partner of departing
city table).
IDM Industry Discount Message (all stations).
IFM Interline Fallback Message (ITCI partner listed from departure

city).
PFS Passenger Final Sales (originating station and designated

Reservation address).
PIL Passenger Information List (originating station only).
PIM Passport Information Message (Any station having address on

CX table).
PMI Passenger Manifest Information Message (Per CX table or

Default address).
PRL Passenger Reconcile List Message (Flight station having

address on CX table).
PSM Passenger Service Message (all stations).
PTM Passenger Transfer Message (all stations).
SOM Seats Occupied Message (next downline station).
TPM Teletype Passenger Manifest (all stations).
Codeshare Flights
Use the LR transaction to dispatch messages for a marketing flight. The PFS, FTL and PRL
can be sent to the marketing carrier of a Codeshare flight and contain information on the
marketing passengers only.
LR entry to dispatch a PFS to a marketing carrier:
LR:XS105/./ATL/PFS/M
Explanation of the passenger departure messages. All but BSM are dispatched via LR.
COM
The COM message is the 'Closeout Message' normally sent 'internally' from check-in to load
planning at flight close. It contains all the passenger and baggage details. The load control
agent can use these details to complete a manual load sheet.

USA Inc.
Page 93
COM Message:
Explanation of TTL (Total) Line:
Field Explanation
A Males/Females/Child/Infant gender counts (if there are only three columns then it
is for Adults/Child/Infant counts). Does not include Jumpseats or XXXCREW.
B Piece/Weight of baggage/Weight of any hand baggage.
C F/C/Y class totals.
D PAD class totals.
E Extra crew by gender (M/F).
F Dead Head crew by gender (M/F).
G Extra seats occupied by class.
H Total weight of extra seats occupied by other than passengers (i.e., SOC/MUS,
etc).
J Total passenger check-in weight.
IDM
The 'Industry Discount Message' lists accepted PAD passengers. Use this list when it is
necessary to offload a PAD passenger accepted upline.
IDM Message

Guide
Page 94
Explanation
This message lists the through PAD passengers by:
n Names
n ID code
n class of travel
n seat number occupied
n passenger's destination
SOM
The 'Seats Occupied Message' informs the next downline airport, immediately after flight
departure of seats occupied by destination and information about the occupied seats.
Seats occupied are ordered by destination from the departure airport.
Blocked seats (PROT EX) include those seats having downline seat protection out of an
airport.
Supplementary information (SI). This portion of the message contains seats occupied by
Passengers available for disembarkation (PAD) and any equipment change. The message
also includes those seats occupied by extra crew (XCR) and seats occupied by
cargo/deadload (SOC). If any of the SI items are nil or if PROT EX is nil the sub-headings
(PAD, PROT EX) do not need to be transmitted in the SOM. The ENDSOM is still a
requirement.
SOM
PSM
The 'Passenger Service Message' gives a list of all the passengers requiring special attention
at their destination. This message is only valid for NAM and PNM flights.
PSM

USA Inc.
Page 95
Explanation
This lists the names of the passenger, followed by the item or free format remark, and
additionally, the flight number if the passenger is transferring to another flight.
PTM
The 'Passenger Transfer Message' lists the passengers transferring to other flights at their
transfer point. This list gives the:
n flight number, followed by their final destination
n number of passengers traveling under the same name
n class of travel
n number of bags
n passenger names
If the name is followed by the 'RQ' item, this means that the passenger only has a request
booking on the onward connecting flight.
PTM
TPM
The 'Teletype Passenger Manifest' lists the passengers for all class groups in alphabetical
order. There is no separation by class.
TPM

Guide
Page 96
Explanation
The header line contains the destination, and the names are followed by their initials.
PFS
The 'Passenger Final Sales Message' is sent to a reservations printer PID or processing
address at completion of check-in (CCF). This address or PID is designated by the airline or
handling company when they or their handled carriers are added to the system. The PID or
processing address can be changed by SITA Customer Support at the request of the airline
or ground handling company. The PFS address designated in a CX table is an alternate
address and is used when directed by a flight schedule's CSM.
The request of a PFS with an LR has no effect on the PFS generated to reservations as it is
sent to the address specified on the CX table.
The PFS includes the number of passengers that traveled (called the numeric portion), and a
list of passengers whose name did not appear on the PNL but had confirmed tickets
(NOREC), or those who were on the PNL but did not travel (NOSHOW). Other categories
listed on the PFS are described below.

USA Inc.
Page 97
PFS
Explanation
This flight has one master class (Y), and three equivalent classes (M/K/G). The CND table is
created as YMKG. On the numeric part of this PFS (MIA 27/012/030/002), is the description
of the number of traveled passengers by class: (27Y 12M 30K 2G). There was only one PAD
passenger in Y class.
Note: Although there is a separate count for PAD passengers, they are also included in the
main figures. Therefore in the above example the 27 Y includes 1 PAD passenger.
PFS Categories:
Category Explanation
CFMWL Confirm from waitlist.
CHGCL Change of class from RES booking (upgrade/downgrade).
CHGFL Change of flight due to flight irregularity (recheck).
CHGSG Change of segment from RES booking.
GOSHO Open ticket (URES) passenger.
FQTVN Frequent flyer number changed or added at check-in.
IDPAD Space available staff passenger.
INVOL Upgraded or downgraded to a different compartment involuntarily.
NOREC Booked (OK) ticket but name not on PNL/ADL.

Guide
Page 98
Category Explanation
NOSHO Booked passenger that did not check-in.
OFFLK Booked passenger that was checked-in, then offloaded.
OFFLN NOREC passenger that was checked-in, then offloaded.
PXLST Change to Passenger’s DOCS, DOCA, DOCO.
CAT
The code CAT is part of the ‘MSG’ field of the CSD/CSM screen on flight creation as well as
the applicable CX table. On flight initialization the booked figures from the PNL are sent to the
address as specified on the CX table.
The message uses the PNL to extract the information needed including:
n Airline/Flight
n Date
n Departure City
n Aircraft configuration (if present)
n RBD (if present)
n Total Booking by each Master Class
n List of all booked passengers with special meal requests
n List of Waitlist passengers with special meal requests
n List of all PAD (ID2) passengers with special meal requests

USA Inc.
Page 99
The message would exclude any additional SSR elements that may be associated with the
passenger (such as TKNE, or .I or .O information) and only the locator (.L), and any .R/SPML
associated with that passenger (see Note below)
Note: There may be airlines that allow ‘WL’ (waitlist) and/or ‘SA’ (space available)
passengers to list standby for a flight with a special meal request. Therefore any passengers
that have a ‘WL’ or and ‘ID2’ associated with their name and they have a special meal request
then these must also be listed.
The list of all valid special meal codes (SPML) that might be listed on a PNL are:
AVML BBML BLML CHML DBML FPML GFML HNML KSML LCML
LFML LSML MOML NLML RVML SFML VGML VLML VOML VJML
Catering Message Manually Generated by LR.

When a manual generation of the catering message is required (by use of the LR
transaction), the system recalculates the booked figures versus the accepted and standby
figures. This may be obtained from the SDD screen (The R, C, and SB fields). The list of
special meals must be extracted in the same format as the automatically generated catering
message.

Guide
Page 100
‘LR format:
The destination and class is required because different meals are prepared for different
Master classes.
Any listed standby passengers such as for ‘WL’ or ‘ID2’ that have not checked-in should be
included on this list along with their WL or ID2 code.
Any passengers that have been checked-in but have gone on standby with a special meal
should appear under the heading of ‘STANDBY’ along with the class they are listed.
PIL
The 'Passenger Information List' is for "NAMSS" flights only, so cabin crews may have a list of
passengers on the aircraft with special requests. The list is divided into classes. The first class
contains all passenger names, seat numbers, plus any infant and special information. The
other classes contain only the names and seat numbers of passengers having infants or
special information.

USA Inc.
Page 101
PIL
Explanation
The list contains passengers with any special service information such as:
n Wheelchairs (WCHR/WCHS/WCHC)
n Blind or Deaf passengers (BLND/DEAF)
n Stretcher passengers (STCR)
n Unaccompanied Minor (UM)
n Onward flight connections or blocked seats.
BTM
The 'Baggage Transfer Message' provides the receiving carrier at a transfer station details of
all baggage being transferred to them from an incoming flight. Each Airline having transfer
passengers will receive their own BTM message. Airlines having more than one connecting
flight will receive all the information on one message. The message contains details for:
n Incoming transfer passenger name's
n Additional onward flight connections
n Number of bags
n Tag numbers
n PNR locator numbers

Guide
Page 102
BTM from DL in ATL to BA in JFK
Explanation
The BTM address is made up of the Airport code at the transfer point (JFK), the Office code of
BT (this is hard coded in the system), and the Airline code of the receiving carrier (BA). The
Airlines may also have addresses added to CX table. The system checks the CX table prior to
using the hard-coded airline address.
Field Explanation
BTM Message identifier.
.V/ Transferring baggage at JFK part 1.
.I/ Inbound flight / date / from / class.
.F/ Flight transfer to BA178/ date / class.
.N/ Number on bag tag. Two bags starting with number 034101081.
.O/ Outbound connection/ date / city / class.
.P/ Passenger's name.
.L/ Reservation record locator number.
.W/ Weight details of baggage.
.X/ Screening description of baggage (not used presently).
Note: Further details of the BTM may be found in 'IATA Passenger Services Conference
Resolutions Manual’, Recommended Practice 1745.
Although the BTM can be dispatched using the LR format, there are some additional entries
that should be noted.

USA Inc.
Page 103
Example Explanation
LR:FLIGHT/DATE/STN/ALL Sends ALL messages including the BTM
(BTM goes to all connecting Airlines
downline).
LR:FLIGHT/DATE/STN/BTM Sends the BTM to all connecting Airlines

downline.
LR:FLIGHT/DATE/STN/BTM/AIRLINE Sends the BTM to the specified Airline

downline.
LR:FLIGHT/DATE/STN/BTM/TELEX Sends the BTM to all connecting Airlines

ADDRESS downline and to the specified address.
LR:FLIGHT/DATE/STN/BTM/AIRLINE/TELEX Sends the BTM to the specified Airline

ADDRESS downline and to the specified address.
Note: Every time the BTM is requested via the LR entry, even if it is only to the transmitting
CRT, the message is also dispatched to the downline Airlines.
Error Responses
ADDRESS Invalid address specified.
CITY Invalid CITY specified.
COUNT Too many addresses were specified.
FLT NBR Invalid flight number entered.
MSG TYPE Invalid message type specified.
TYPE Message type not valid for NUM check-in.
BSM
The 'Baggage Source Message' is a computer-to-computer message designed to provide
information for the processing of baggage by automated baggage systems. It can only be
utilized by those Airlines that use BAG TAG printing. This message enables baggage
reconciliation for an automated sortation system at the departure airport. The BSM message
is sent by the boarding Airline to the sortation office at that station so the system can sort the
baggage by flight number and destination. This message is dispatched internally as a Type A
message and is not seen by Airline agents. NOT USED WITH LR ENTRY.

Guide
Page 104
To activate the BSM message, an Airline must:
n Already use Automatic Bag Tag printing.
n Advise SITA DCS/ATL they require the BSM message to be activated and the type (DCS
version 1 or IATA Type B) BSM is not entered on the CSM or CX table.
The BSM message can be sent by one of two methods, SITA DCS:
1. Create and send a BSM message to the sortation office every time a Bag Tag is printed.
This only applies to baggage that is locally checked-in using the DCS system. A BSM
message is not sent for manually entered Bag Tags.
2. Translate data from a BTM created message, and send a BSM message for each
passenger to the sortation office for action.
BSM
Explanation of DCS Version B.
Field Explanation
.V/B The Version number (B) followed by either L for LOCAL or T for
TRANSFER. The last three letters indicate the station of origin.
.N/ The Bag Tag number. The last digit indicates the number of
consecutive Bag Tags issued.
.F/ Departure Flight number / date / destination / class.
.P/ Passenger's surname.
.T/ Bag Tag printer PID that issued the Bag Tag.

USA Inc.
Page 105
Explanation of BSM Version 1.
Field Explanation
.V/1 The Version number (1) followed by either L for LOCAL or T for
Transfer. The last three letters indicate the local airport code.
.F/ Flight information outbound / date /city / class.
.O/ Onward Connection / date / transfer or destination city / class of

travel for bag.
.N/ Number on bag first bag tag / number of consecutive tags.
.S/ Reconciliation data - authority to load (Y/N) / seat number.
.W/ Pieces and weight data - Piece, weight indicator / number /

weight / hand carry.
.P/ Passenger name.
.Y/ Frequent traveler number.
Note: The Office code BS was 'hard coded' as the address for the sortation office. Also the
BSM will not appear on the CSM as they are generated after the issuance of Bag Tags, and
not as a post departure message.
IFM
The 'Interline Fallback Message' is used for EDIFACT flights only. It is sent to the onward
Airline with a list of those passengers on whom a delete (PW) or an update (PU) was
attempted, and was not successful (no response was returned from the EDIFACT flight). The
IFM will not list passengers for whom a PA (with O) was done and no response was received
back.
The IFM message is only dispatched if there is information present; it is not sent when there is
NIL information.
A separate IFM message is sent to the transfer point for each different Airline with Interline
passengers.
An example of an IFM message for a flight of AB378 operating ATL to LHR and passengers
are THRU CHECKED onto flight YZ827 LHR to MAN:

Guide
Page 106
IFM
If there is more than one part, then the message should end with ENDPART1 and the second
message should start with PART2. Data belonging to the same passenger is not split over
two messages.
The various items that can be displayed after a name are:
Item Description
.R/CLS Class of travel on onward flight. If not stored, .R/CLS is not
displayed.
.R/SEAT Seat Number on onward flight. If not stored, .R/SEAT is not

displayed.
.R/REC Boarding Number on onward flight. If not stored, .R/REC is not

displayed.
.R/IREC Boarding Number of originating flight. If not stored, .R/IREC is

not displayed.
.R/SSR SSR codes attached to a passenger's record.
.B/ Baggage details with bag pieces followed by bag weight (1/12).
For pooled bag the display shows '.B/PLD' and if baggage is zero
or missing the display is '.B/0'.

USA Inc.
Page 107
Item Description
.N/ Bag tag number followed by number of bag tags in the range
(even if it is only one), and the final destination of the bag. If the
bag tag numbers are not in sequence then a separate .N is
required for each bag. The system converts the first two numbers
of the Bag Tag into the 'issuing' Airline code for this message,
even though the PDD record may only contain a number.
SI This text is 'hard coded' into the system and it is not possible to
add more text to this topic, or to amend it.
Note: The message is dispatched at the end of the flight when the CCF transaction is
entered, and goes to the addresses specified in the CX message address table for that
destination. This message can also be displayed to the screen or a printer using the 'LR'
transaction.
FTL
The 'Frequent Traveler List Message' lists all passengers having a Frequent Traveler number
attached to their Check-in record. The FTL is attached to the CSM and delivered to the
addresses specified in the CX table of the departing city. The system can process FQTV /
FQTR / FQTU / and FQTS as designations for Frequent Travelers.
Note: The FQTV modification must be entered in a specific manner of transaction: PA or
PU:1,FQTV XS/123456789. The FQTV code must be followed by the airline code and the
slash.
FTL
API
The 'Advance Passenger Information Message' is transmitted to applicable border control
agencies at flight release. It contains passenger passport information entered by reservation
and or check-in staff. The message is compiled if the API option is manually added to the
CSM screen and if the mandatory PSPT remarks meet the minimum mandatory

Guide
Page 108
requirements of the border control agency. These requirements are:
n Passengers full name (as shown on the passport)
n Passport number
n Country of issue
n Date of birth
The API message transmitted from SDCS conforms with EDIFACT formats. The message
will not display on a screen or go to a printer. The LR transaction is only an alternative method
to send the message to the border control agency without reopening the flight. The entry is
restricted to:
LR:FLT/DATE/STN/API/P or C/Country Code
Note: P indicates passenger and C designates crew.
The message is formed and sent which has PSPT remarks meeting the minimum mandatory
requirements on the flight. The message enables passengers to be processed at the port-of-
entry via a line used to expedite the passport control process.
Note: Both the API and PIM are part of the 'Advanced Passenger Information Systems' of
SITA. The API system is offered to all SDCS customers having flights controlled by applicable
border control agencies.
PIM
The 'Passport Information Message' is a translation of the API EDIFACT message. It
contains the passport information as described in the API message. The PIM cannot be
entered on the CSM screen but is now sent to every city in an itinerary when the CX tables
are updated. The PIM contains the passport (PSPT, DOCS, DOCA, and DOCO) information
in the same order as it was input into the passenger’s record.
The PIM is a stand-alone message. The processing is not dependent on the destination of the
flight (as with APIS) and can provide passport information to any airport or government
authority, if required, with flight closing. There is no restriction with the LR entry.
PIM
or
LR:FLT/DATE/STN/PIM
PIM

USA Inc.
Page 109
PRL
The 'Passenger Reconcile List Message' allows the exchange of check-in details for the
automatic update of an airline or handled airline's system.
PRL

Guide
Page 110
Explanation
Row Explanation
1 Message Identifier.
2 Flight / date / City of Departure / Message Part.
3 Total by Class Destination.
4-7 Passenger Name Element with details. Record Locator,

Pieces/Weight Element, Bag Tag Details may be shown,
Inbound / Outbound Connection Detail Element, Seat and
Remarks (All Passengers are listed by class in alphabetical order
and surnames are listed individually.)
8-9 Totals by Class Destination.
10-15 Passenger Name Elements (Same as Item 4-7).
16 End of Text, End of Message.
PMI
The 'Passenger Manifest Information Message' is mandated for every flight segment
operating to or from the United States of America. The message is compiled from those
passengers having either a PCTC or PSPT remark in their Passenger Record. The message
is not shown on the CSM, and no address is specified in the CX table as the PMI is
downloaded to the DFL address of the CX table. The PMI may also be requested via the LR
at any time other than when on Emergency Lock. In the event of an emergency the flight is
placed on Emergency Lock (FUI:FLT/DATE/CITY/LOCK) and removed
(FUI:FLT/DATE/CITY/UNLOCK).
PMI
ETL
The 'Electronic Ticket List' lists passengers who used electronic tickets on a flight. This list
includes the passenger name along with pieces and weights of baggage. The message type
'ETL' must be entered on the CSM screen. An address can also be added to the CX table for
the ETL.
ETL

USA Inc.
Page 111
Targeted ETL for code share partners
The Targeted ETL (Split ETL) is an ETL that contains checked-in E-tickets of a specific code
share partner.
For an e-ticket to appear in this list:
n The CX table must be set up with Targeted (Split ETL) ETL for code share marketing
partner and its address
n The passenger must have code share marketing flight details
n The passenger must be checked-in against an e-ticket.
If above conditions are true, a split (Targeted) ETL is generated at the time of flight close with
CCF or when agent generates a split ETL manually.
It is important to note that split ETL is built using marketing flight number details.
The operating carrier is OC, the code share marketing carrier is MC:
The LR: function can also be used to generate split ETL.

Entry:
LR: flight number/date/departure airport/ETL/W/xx
or
LR: flight number/date/departure airport/ETL/W/xxx
Where,
LR: flight number/date/departure airport/ETL/W/ - Current format to generate ETL
xx (for 2 or xxx for 3 alpha numeric character airline code) – is the code share partner airline
code
MC142 is a marketing code share partner flight and OC1492 is the operating flight.
Entry:
LR:OC1492/./BUD/ETL/W/MC

Guide
Page 112
Response:
ACCEPTED
If the code share table is not defined on the flight, an error is returned when agent attempts to
generate split ETL using LR:.
AC is not specified as a code share partner
Entry:
LR:MA1492/./BUD/ETL/W/AC
Response:
CODE SHARE PARTNER NOT IN FILE
SDCS Check-in Passenger Report in eXtensible Markup Language (XML)

The SDCS Check-in Passenger Report contains a list of passenger details captured before
the flight is purged out of the system. The list is organized by carrier, flight/date, and departure
airport.
All passengers, including passengers that did not check-in, are included in the list. Checked
passengers are identified by the presence of boarding number in their record. Crew and
Unattached baggage details are also included in the list.
The report is provided in extensible mark-up language (xml) to facilitate portability. The xml
format provides an interface facility for customers to programmatically read and search the
report.
The generation of this report is controlled by user parameter URPXML. When the parameter
is set to 1, the report is generated, when set to 0, no report is generated.
The report is kept on the SITA server for 7 days, after which it is deleted. The customer is
expected to down-load the data in the 7 day period.
The SDCS Check-in Passenger Report in xml contains check-in passenger data organized
by carrier, flight number, and departure airport and passenger name. The first carrier on the
list is the host followed by other handled carriers.
Passenger check-in status at the time of data capture and historical updates leading to the
current status are recorded in the report. The report includes all passengers whether they
were accepted or not. Successfully check-in passengers are identified by boarding number.
The report is generated on the day the flight is purged out of the system at the end of check-in
flight life cycle. No recovery is available once a flight is purged.
The file is named as follows:
XXX- DDMMMYY-CKP – where,

USA Inc.
Page 113
n XXX or XX - is the host code (ex: 78, MA, S7, 126, etc.)
n DDMMMYY – Date, Month, Year (ex: 07APR07)
n CKP - Check-in Passenger report (hard-coded)
MA07APR07CKP
S706APR07CKP
12601APR07
Report Structure

Guide
Page 114
USA Inc.
Page 115
Guide
Page 116
USA Inc.
Page 117
Note: The schema will change as more passenger data items are added with the
enhancement of the check-in process.
SDCS Check-in passenger report is downloaded to a server as part of nightly process. To
gain access to the server, please contact Passenger Help Desk at Pss-Helpdesk@sita.aero.
Excess Baggage Charges by Agent (EXBG)

The Excess Baggage Charges by Agent allows an airline to send excess baggage
information of checked-in passengers to an ‘Open’ type systems server where it is stored for
retrieval by the airline. The airline has several options to retrieve this information from a web
site and have it displayed either to the screen or downloaded to a printer.
Pre-Conditions
1. The excess baggage charge tables are in the airline and flight routing (JXD/JCD Tables).
2. SITA Customer Support controls the URM and sets the EXBG parameter when
authorized by the Host Carrier. The parameter is:

Guide
Page 118
a. Default. Do not send any excess baggage information to the Open system’s server.
b. Send excess baggage information to the Open system’s server.
3. When passenger with excess baggage has the charge ‘Accepted’, the system verifies the
URM setting. If URM is set to:
1 - the information process for the data flows are initiated.
0 - no information is sent to Open system.
Passenger Check-in with Excess Baggage

1. Start the check-in process either by selecting a name from the PS list, PDD record, or by
inputting the full check-in entry (flight, name, etc), with baggage details, and if necessary
identify passenger(s) as URES or NOREC and/or ID.
2. On transmission of the entry the system checks the baggage allowance for the passenger
checking-in (class of travel, number of passengers in the group) against the JAD and JCD
tables.
3. If system determines there is not excess baggage, then the Excess Baggage Charge
process ends.
4. If system determines that there is excess baggage, then agent gets a response similar to:
Note: The ‘Boarding Pass Print Inhibit’ is an airline option.

5. The agent can amend the baggage that may result in the baggage no longer being in
excess, in which case the Excess Baggage Charge process ends, or accept the charge.
Note: To accept the charge, the agent must go to the end of the first line (after the money
amount) and transmit the screen.
6. If the agent accepts the charge, the response is:
CHARGE ACCEPTED
7. An internal message is sent to the Open system.
8. As a result of the acceptance, the passenger’s PDD record is appended with a response
similar to the following:
XBC VDT8273 AGT72/21JUN1511
Requesting Excess Baggage Statistics from the WEB

Pre-condition
The airline can access ISNet with valid authority and sign-in code
Three Steps to Retrieve EXBG Information

USA Inc.
Page 119
1. Access the required ISNet WEB site (http://57.255.32.100/exbag/index.html).
2. If necessary, register and wait for a confirmation email message from SITA.
3. Once the customer has confirmation they have signed-in the WEB and can access the
Excess Baggage Statistics for their airline only, they are presented with a search page
listing all available search filters and group by options.
4. The options that are available include any of the following combinations:
Agent ID, Airline ID (Handling Companies only), From Date, To Date, Origin Airport,
Flight Destination Airport.
Include or Exclude: Accepted or Standby Passengers
Excess Baggage Totals Grouped By: Origin Airport, Agent ID, Flight Number, Airline
(Handling Companies Only):
a. After selecting the required option(s), view and optionally print-out the results:
b. Once the request is completed, the airline can request another report or exit the WEB.
c. If another report is required, repeat steps 3 and 4 or log-out.
Standby Passenger with Excess Baggage
Standby passengers are displayed in a separate listing. If they clear the standby list and are
accepted onto the flight they stay on the Standby list and are not transferred to the Accepted
list. They will show accepted on SDCS display.
If the passenger is not accepted on the flight then it has to be assumed that unless he/she is
transferred to another flight, that he/she has their money refunded (outside the control of
DCS).

Guide
Page 120
Additional Baggage after Check-in
n Agent selects the passenger that has excess baggage.
n Agent adjusts the baggage figure (PU) with the new details.
n If the new baggage details result in the baggage being within the allowance for the number
of passengers in the check-in party, class and routing, then no further action is required.
n If the new baggage details still results in the baggage being over the allowance for the
check-in party, class and routing, then the agent must ‘accept’ the charge, and another
internal message is sent to Open systems for the details to include in the excess baggage
statistics.
n The additional baggage charges show as a separate entry and are not added onto the
original charge.

USA Inc.
Page 121
Example Report
The following is an example of the results format shows the standard layout using a Group By
of Date. Airlines are restricted to only their records.

Guide
Page 122
Web Server Page Entries
Enter SITA Web URL, http://57.255.32.100/exbag/index.html, on the Web browser address
bar and the following Website is returned.
EXBG Login
If you already have a User ID and Password you fill in the Airline ID, User ID and Password
and click on Login.
New users must create an account by clicking on Register. An example of the new user
registration form is on the following page. All information must be filled in on this form. When
done, click on Register and a message is sent to a SITA Administrator who will activate your
account and allow you access to your airline’s information. The administrator will advise you
when your ID and Password is active by the email you provide.

USA Inc.
Page 123
EXBG Register
Record your registry information for your records. If you misplace the access information you
may call SITA Customer Support to request the information be emailed or the account closed
so a new account may be created.
EXBG Search
Upon successful login you will get a screen display where you enter the search parameters
for your request. The following example is a handling company request for MA excess
baggage charges collected by all agents, at all airports from 14Sep until 26Sep. For any
individual airline record access is limited to your airline. You can filter the results by using
additional fields.
Entering additional information in one or more search fields further filters the results.
Examples of field entries are given to the right of the fields inside the brackets ().
Field Description
Agent ID Adding an agent ID limits the record to only that agents totals.

Guide
Page 124
Field Description
Airline ID Airlines may leave the airline field blank or add their airline code.
Some handling companies may require access to airline records,
these rights are managed using an access table for each handling
company.
From Date The from date limits the results to that date or later.
To Date The To date limits the result to that date or prior.
Origin Airport The three-digit airport code limits the search to only flights leaving
that airport.
Flight The full airline code and four-digit flight number (e.g., XS1000)
limits the results to a specific flight.
Destination Airport The three-digit airport code limits the search to only flights with a
final destination to that airport.
Include Passengers The Accepted or Standby options include or exclude the selected
passenger types.
Group By The user can select how the excess baggage charges are
totaled. Using any combination of searches and a group by option
produces amount totals for each currency collected.
Note: Your airline must be on SITA DCS at any airport you want to query. Airlines handling
code share or handling agents will have statistics listed under their airline code.

USA Inc.
Page 125
EXBG Results
The following is an example output for a requested search by airport and agent.

Guide
Page 126
The current date appears in the upper right corner. Search criteria are listed in the upper right
showing filters and grouping options selected. Totals are grouped by agent and appear on the
far left column of the report. Totals contain a single currency type for the group selected.
Print the report by selecting Print. The Return option returns the user to the Search page or
the last page displayed.
Sorted Passenger Manifest Generation (JL)

It is possible to print or display various passenger lists at flight close. The reports can be sent
to teletype (TTY) and ZZ addresses.
The basic entry is:
JL:OPTION/FLIGHT (Defaults to present date / all classes / all segments from city of sign in /
VDU).
JL:OPTION/FLIGHT/CLASS/SEGMENT/PRINTER PID
The segment entry is necessary when a specific segment of the flight is required. The various
options are:
Entry Explanation
JL:A List by AGENT number.
JL:AG Total passengers checked in by an agent for a specific day.

Options are: airline/date/origin/agent number or
all/date/origin/agent number.
JL:B List by BOARDING number.
JL:N List by NAME order.
JL:S List by SEAT number.
JL:BX Complete list by BN number. Includes Child and Infant Counts.
JL:NX Complete list in NAME order.
JL:BT Complete List in BN order with Bag Tags.
JL:BI All Bag Tags per Passenger Regardless of Where Issued.
JL:CT List of canceled/deleted bag tags.
JL:FS List in Name Order with Detailed Data per Passenger and Split
Totals.
JL:MS List in Seat Number Order with Special Meal.
JL:MT List by Name and Ticket Number.
JL:NI List of inbound passengers.

USA Inc.
Page 127
Entry Explanation
JL:NN List of Passenger Names Not Boarded, but with Bag Tags.
JL:NO List of outbound passengers.
JL:NT Complete List in NAME order with Bag Tags.
JL:NZ List of all Accepted Passengers Including Ticket Numbers.
JL:NX List in Name Order with Detailed Data.
JL:AB List by SB Number of Not Accepted and Accepted Passengers

with Bag Tag Number.
JL:AS Complete List by SB number with bag tags / Inbound Flight. The
BN and SN are added upon acceptance.
JL:BB Complete list by BN sequence with bag tags / outbounds.
JL:NB Complete List by NAME sequence with Bag tags /outbounds.
JL:P List by Passport Details.
JL:T Complete List by BAG TAG. Send to Printer only.
JL:TI List of Passengers and Bag Tags on Inbound Flights.
JL:TO List of all Manually Issued Tags only at this city.
JL:TT List of all Tags Issued at this City.
JL:TR List by TOP (Tour Operator Code)
JL:NS List of accepted Passengers in Alphabetical Order with Bag Tags

and Deleted Passengers with Date and Time of Cancellation.
JL:PS List by Seat Number with all SSR and PSM Information.
JL:CI List of Passengers on Aircraft by Class in Seat Order, including

Vacant Seats, and PSM information.
JL:OV List of Electronic Ticketed Passengers Check-in with OVR

(override entry).
JL:XX List of XXXCREW and XXXDHC.
Passenger Ticket Lists
Entry Explanation
JL:KK List by Ticket Number order.
JL:NK List in Passenger Name order.

Guide
Page 128
Entry Explanation
JL:NE List in Name Order with Electronic Ticket Number.
JL:ET List in Electronic Ticket Number order.
The complete list gives additional information such as:

n special service information
n inbound or outbound connections
n PNL group code identifiers
n agent number
n amount of baggage checked-in (P/W) with bag tags

USA Inc.
Page 129
JL:NX/XS388/Y/1390
Explanation
Entry Explanation
NAME Name of the passengers in alphabetical order.
BN/SN Boarding number (BN), and Seat number (SN), issued at check-
in.
INBOUND/OUTBOUND Flight number and city of the inbound or outbound connection.
AGT Number of the agent who did the check-in. If there is no agent
number, then the passenger was ITCI from an inbound message.
GI Group identifier. Passengers who have the same identifier have

been booked together in reservations.
BAG Number (P), and weight (W) of baggage checked-in. If a

passenger is checked-in with another passenger, the display
shows the BN (boarding number) of the passenger the baggage is
attached to.
Note: All JL: lists identify all URES and NREC passengers. The URES names have an
asterisk (*) prefix and the NREC passenger names have a pound/hash (#) symbol prefix.

Guide
Page 130
Error Responses
Entry Explanation
PROT COV Flight is under protective cover.
Flight Check-In Agent List (JFL)

This JFL: table displays the number of passengers checked-in by an agent for a particular
flight. Enter:
JFL:FLIGHT/DATE JFL:XS298/.
Display of JFL
Note: Agent number 9999 displays when the system initiates Automatic acceptance of
passenger. This happens when GS/ID figures are entered after passengers are on standby.
Error Responses
NO ENTRY No passenger entries for this airport.
NO INFO No passenger data available for this segment.

USA Inc.
Page 131
Guide
Page 132
20. Movable Partition Flights
Movable Partition (MP)
The MP transaction adjusts a partition between two adjacent compartments to change
seating capacity over a selected flight segment. The segment specified can only be from a
departure to the next arrival airport. The MP transaction is allowed on the lower cabin
compartment defined when the seat map (EQC) was built. A partition cannot be adjusted
over blocked, occupied, ASR or advanced boarding pass seats. The adjustment can be made
before or after flight initialization.
The movable partition transaction allows the change of aircraft configuration without having to
enter an aircraft configuration change, thus preventing any delay to the continuation of
passenger check-in.
The MP transaction must be preceded by the all class seat map display transaction, for
example:
SE:FLIGHT SE:XS396
SE:FLT/./SEGMENT A SEGMENT B SE:XS396/./???
Note: When using the MP transaction on multi-sector flights, it is very important that the MP
entry is done for all flight segments; otherwise the various seat map segments will not match,
and cause seat allocation problems downline.
In the example below a TU3 aircraft has a configuration of C8 M64. Because the seat map is
configured as a MP the C class compartment can adjust from 8 to 72 seats. The M class may
decrease from 64 to 0 seats. To adjust the C class to 16 seats the CM class partition would
have to move from row 2 to row 4.

USA Inc.
Page 133
The following are examples of Movable Partition EQC and Seatmap (SE:400) Display:
Moveable Partition EQC:
Note: If MP is entered for a single segment, the SE for multiple segments will not display
those seats that were changed for MP.
Seat Map Display:
Enter:
MP:CLASS1 CLASS2 ROW (Move Partition C class M class to row 4)
MP:CM4
Thus, in this example, the new configuration is C16 M56.
The MP transaction also updates buffer rows (last to be used seats) that separate the two
compartments as protection for moving the partition. In the above example we may want to
protect the last row in C class (row 4) and the first two rows in M Class (row 5-6). The entry
would be:
MP:CM4/1P2
When the buffer request is omitted from the MP transaction the default is the number of seats
specified in the EQC. In the “Example of a Moveable Partition EQC” there were no buffer
rows set up for row two (2/ 0P0).
It is also possible to increase or decrease the buffer zones without moving the partition.
The entry for the last example is:
MP:CM4/0P3
MP:CLASS1 CLASS2 ROW/NBR (FWD BUFFER ROWS) P NBR (AFT BUFFER ROWS)

Guide
Copyright © SITA Information Networking Computing 20. Movable Partition Flights
Page 134
Example to remove all the buffer rows:
MP:CM4/0P0
(0 = ZERO)
The MP transaction is available for free seating flights. In this case the new configuration is
entered instead of a row number.
Example to change configuration of C12M88 to C18M82 enter:
MP:C18M82
Notes:
The maximum buffer zones that can be created are nine rows forward and nine rows aft.
When the MP transaction is made a check is made to verify the request is for one leg
(segment).
Error Responses
BUFFER ROWS EXCEED Too many buffer zones specified.
COMPARTMENT
COMPARTMENT/CONFIG Invalid class code or configuration specified.
DELIMITER A 'P' does not separate the buffer rows.
ERR-NO SEAT MAP The seat map (SE) was not previously displayed.
ILLEGAL SEGMENT The input is not for a single segment.
INVALID ADJUST Invalid class and rows specified.
MOD NOT POSSIBLE MP transaction not allowed.
MULTIPLE More than one input for the same class entered.
CHANGE/UPDATE
NO SEAT SELECT Row was specified for a free seating flight.
NUMBER/ROW Invalid buffer or partition row number specified.
SEAT Transaction is prevented by blocked / occupied seat.

CONFLICT/OCCUPIED
SIZE The new configuration does not have enough capacity for the
allocated/blocked seats.

USA Inc.
Page 135
Guide
Copyright © SITA Information Networking Computing 20. Movable Partition Flights
Page 136
21. Flight Equipment Type Change
Automatic Equipment Change (AEC)
Sometimes, after check-in begins, it is necessary to substitute the original aircraft with
another having a different seat plan or seat capacity. A new seat map will be required to
correctly board passengers and to reassign seating to those already checked in.
The AEC transaction allows the supervisor to change the type and version of a scheduled
flight's seat map. Use this transaction with equipment changes initiated by the
FUI:FLT/DATE/CITY/CTN transaction. Use the AEC transaction when the new aircraft type
and version have the same classes as the original, but the order and number of
compartments do not have to be the same. SDCS allows equipment changes of different
classes if specific database changes are made. AEC is not allowed on a shared equipment
flight.
Note: It is possible to change one class configuration to a two-class configuration (or two to
three class configuration), but the additional classes must be specified on the CND table used
to create the flight; otherwise, the AEC is rejected.
The FUI transaction sends the configuration change to LDP. AEC does not affect load
planning; errors will result. Before the AEC transaction is entered, the flight must be put under
protective cover for Equipment change (PO:FLIGHT/.,E) so that check-in is inhibited while
the equipment change is implemented.
Print a hardcopy of both the original all class PS list and seat map after the PO entry, but prior
to the AEC transaction. Use the hardcopy print to verify ASR and Reserved seats after REA
transaction (Reassign AEC Passengers Original Seats sub-section in Flight Equipment Type
Change), enter:
AEC:FLIGHT/DATE CITY NEW AIRCRAFT AEC:XS745/. ATL 737/A/F12Y96
TYPE/ VERSION/CONFIGURATION
The processing of the AEC transaction verifies the configuration and aircraft type / version
match. The new equipment's database is checked to see if the compartment capacity is
sufficient to accommodate all passengers before it returns an 'ACCEPTED' response.
The AEC transaction (when no F -free seat indicator- is used) performs a capacity check and
if existing accepted passengers cannot fit on the new equipment, an OVER CAPACITY
warning message is output. This means the accepted passenger capacity must be reduced
(some passengers must be offloaded using the JAC transaction – (AEC Passenger Offload
sub-section in Flight Equipment Type Change) to the new limits before the AEC transaction
can be entered.
If no capacity problem exists, the AEC transaction marks all seated passengers as needing
seat reassignment (AEC). The old seat map is deleted and a new blank seat map is created.

USA Inc.
Page 137
All GO SHOW/PAD limits, if used, are set to (0) zero. Passengers can now be re-seated
either in their original seats using the REA transaction, (Reassign AEC Passengers Original
Seats sub-section in Flight Equipment Type Change) or new seats using the SEA transaction
(Assign AEC Passengers New Seats sub-section in Flight Equipment Type Change).
All Class PS List after AEC
Explanation
The Passenger Display List for all classes (PS745/.) shows how seat numbers of checked-in
passengers are now shown as AEC. The Boarding Numbers (BN) do not change.
Passengers with ASR and reserved seats must have them assigned again.
Free Seating
If the new aircraft type and version would cause too many seat changes, then it is possible to
enter the AEC transaction and specify that the new flight will be 'free seating' by putting F
indicator at the end of the transaction, enter:
AEC:FLIGHT/DATE CITY AIRCRAFT TYPE/VER-
SION/CONFIGURATION/F
AEC:XS745/. ATL 737/A/F12Y96/F
AEC Passenger Offload (JAC)

The JAC transaction manually disembarks passengers from a flight during an AEC entry. It is
used if the AEC transaction causes an over capacity of accepted passengers on the new
equipment.
The entry must be preceded by a passenger list (PS) or passenger record (PDD) display:
JAC:ENTRY NUMBER
JAC:RANGE OF ENTRY NUMBERS (JAC:1-9)JAC

Guide
Copyright © SITA Information Networking Computing 21. Flight Equipment Type Change
Page 138
The system remembers the passenger's original seat numbers in their PDD record. After the
AEC entry, if there are more seats available - perhaps due a Moveable Partition transaction -
the passengers should be onloaded with the AC entry before using the SEA entry. If this was
done after the SEA entry then some original seat numbers belonging to the JAC passengers
may get allocated to passengers that need re-seating.
Error Responses
AIRCRAFT Invalid aircraft type/version or missing.
AUTHORITY The agent is not allowed to enter the transaction.
CITY Invalid city or missing.
CONFIGURATION Invalid configuration specified.
EQUIP CHANGE PO Protective cover is missing.

REQUIRED
FLT CLOSED/CANCELLED Flight is already closed or has been cancelled.
NO ACTION INDICATED Input resulted in no change.
OVER CAPACITY The specified number is over the new aircraft capacity.
PROT COV The flight is under normal protective cover.
SIZE The new seat map record size exceeds parameter.
UNABLE Invalid entry format.
Reassign AEC Passengers Original Seats (REA)

The REA transaction attempts to re-seat transit and local passengers in their original seats
after an AEC aircraft type/version change, enter:
REA:FLIGHT/DATE REA:XS745/.
There are three additional REA transaction that can be used prior to the REA:FLIGHT/DATE
transaction when required, if adding a:
n V after the date (REA:FLIGHT/DATE,V), the system re-allocates only ASR, R and P seats
after the AEC aircraft change. Then enter the normal REA transaction.
n C after the date (REA:FLIGHT/DATE,C), the system re-allocates only the transit
passengers. The normal REA transaction re-allocates both transit and local passengers.

USA Inc.
Page 139
n P after the date (REA:FLIGHT/DATE,P), the system re-allocates passengers with paid
seats first. Following this transaction, the supervisor must check if there are any
unassigned passengers with paid seats (PS:FLIGHT/DATE,AEC,PAID). If there are
passengers with paid seats, the SEA: element is used to manually reassign them.
Error Responses
DATE Invalid city or missing.
FLT CLOSED/CANCELLED Flight is already closed or has been canceled.
OPTION Letter other than C was specified after the date.
Assign AEC Passengers New Seats (SEA)

The SEA transaction re-assigns new seat numbers to passengers after their original seats
were changed due to an AEC aircraft type/version change.
Note: It is suggested that a printed list of all passengers that need new seats be printed so
that the supervisor will know which passengers to advise.

Guide
Page 140
This list can be obtained from the following entry:
PS:FLIGHT/DATE,AEC PS:XS745/.,AEC
A PS:FLIGHT/DATE,AEC display must precede the SEA entry, and the entry numbers must
be for the same class and destination:
SEA:ENTRY NUMBER SEA:1
SEA:RANGE OF ENTRY NUMBERS SEA:1-5
The response is a list of passengers with new seat numbers.

A PS:FLT/DATE,AECX transaction gives a list of all reseated passengers who need
boarding passes due to the AEC.
Note: Use the SEA entry individually for passenger's that have Infants or Extra seats,
otherwise it might cause some seat discrepancies.
It is also possible to select specific seat or seat code (smoking, window, etc.), by adding the
request after the entry number.
SEA:ENTRY NUMBER,RS
SEA:ENTRY NUMBER,R17A
Error Responses
CLASS The passengers are not all in the same class.
CONFLICT Conflict between requested and previous display.
DESTINATION The passengers are not all going to the same destination.
ENTRY NUMBER Invalid entry number.
FLT CLOSED/CANCELLED Flight is already closed or has been canceled.
ITEM Previous display did not specify AEC passengers.
NLT No local passengers allowed to be accepted.
NO DISPLAY Entry was not preceded by a passenger display.
NUMBER Illegal entry number.
PAX STATUS CONFLICT Attempt to re-seat a passenger previously not checked-in on the
flight.

USA Inc.
Page 141
PSGR ID Invalid passenger identified.
SEATS Bad seat area or characteristics selected.
Check List for Aircraft Type and Version Change

1. Put flight under protective cover:
PO:FLIGHT/DATE,E
2. Enter AEC transaction with seating required:
AEC:FLIGHT/DATE CITY AIRCRAFT TYPE/VERSION/CONFIGURATION
or free seating required:
AEC:FLIGHT/DATE CITY AIRCRAFT TYPE/VERSION/CONFIGURATION/F
3. Re-seat passengers into original seats:
REA:FLIGHT/DATE
4. Check and print list of passengers that need new seats:
PS:FLIGHT/DATE,AEC
5. Re-assign new seats for passengers. The following entry must be preceded by a
PS:FLIGHT/DATE,AEC display, and the entry numbers must be for the same class and
destination:
SEA:ENTRY NUMBER
6. Onload any passengers with Infants or Extra seats individually.
7. Remove the protective cover:
PO:-FLIGHT/DATE
AEC Check List with MP on Multi-Sector Flight

1. Put flight under protective cover:
PO:FLIGHT/DATE,E
2. Enter AEC transaction with seating required (Use Master MP configuration).
AEC:FLIGHT/DATE CITY AIRCRAFT TYPE/VERSION/CONFIGURATION CHECK LIST
3. If AEC is prevented because of too many passengers in one class, Offload some
passengers using the JAC entry (Section 0). Example: JAC:1-9. Make a note or print a list
of all offloaded passengers.
4. If step 3 was necessary, then repeat the AEC entry.
5. Enter the required MP entry for each segment. Each segment must be entered
separately.

Guide
Page 142
6. Onload any Offloaded (JAC) passengers first.
7. Re-seat passengers into original seats using REA entry.
8. Re-assign new seats for those passengers who need new seats using the SEA entry.
9. Remove the protective cover (PO:-FLIGHT/DATE).
AEC Check List with MP On (Free Seating)

Multi Sector flights
1. Put flight under protective cover for equipment change:
PO:FLIGHT/DATE,E
2. Enter AEC transaction with Free Seating required (Use Master MP configuration).
AEC:FLIGHT/DATE CITY AIRCRAFT TYPE/VERSION/CONFIGURATION/F
3. Enter the required MP configuration (MP:C40M36) for each segment. Enter each
segment separately.
4. Set GS figures and onload any AEC offloaded passengers.
5. Upgrade or downgrade passengers if necessary.
6. Remove the protective cover (PO:-FLIGHT/DATE).

USA Inc.
Page 143
Guide
Page 144
22. Bulk Recheck Passengers to a New Flight
Bulk Recheck Accepted Passengers (BRC)
The BRC transaction allows the supervisor to transfer CHECKED-IN (accepted not standby)
passengers from one flight to another when the destinations are the same.
This transaction is restricted to a 'Gate CRT'. For those airlines not having gate CRT's there
are two entries available:
1. Display the DPID of the CRT attempting the entry and change the CKZN to 0 (zero). Then
proceed with the BRC entry. If there is still a problem, check if there are any gate numbers
entered on the original flight. If so, remove (FUI:FLIGHT/DATE/STN/GATE/ERS) and try
the entry again.
2. Create a 'dummy' gate on the AZ table with the CRT PID number of the set attempting the
trans-action. Enter this 'dummy' gate on the original flight, and then the transaction entry
can be attempted.
The BRC entry is:
BRC:ORIGINAL FLIGHT;NEW FLIGHT BRC:XS395;XS397
Note: A specific class may also be input. It is possible to transfer the passengers from one
class to another (exampleBRC:XS395Y;XS397M).
It is also possible to transfer specific checked-in passengers from one flight to another by
selecting the entry numbers from a checked-in list (PS:FLIGHT,ACC). The "PS" is required in
the BRC: entry.
Entry after displaying the PS list:
BRC:ENTRY NUMBER PS ,ENTRY BRC:3PS,7PS,8PS;XS405M
NUMBER PS; NEW FLIGHT CLASS
BRC:RANGE OF ENTRY NUMBERS;NEW BRC:3-8PS;XS405M
FLIGHT CLASS
Do not mix classes within a range.

Note: If the item number is known from the original PS list there is no need to redisplay the
name list. By specifying the type of list originally displayed the transactions may continue.
(BRC:40PS,50PS;XS201C).
If the class does not exist on the new flight, then the error CLASS is returned and the
passenger shows as DEB on the original flight.
Check List when Creating and Transferring Passengers to New Flight
1. If necessary, create new DFD flight schedule and amend CSM.
2. Send NIL PNL to newly created flight, and initialize it for check-in.
3. Put ORIGINAL flight under Protective Cover (PO).
4. Enter GS/ID figures to full capacity (or required number) on new flight.

USA Inc.
Page 145
Note: If the new flight also under PO, all passengers will go on standby until PO is
removed.
5. Enter the following transaction to move the checked-in passengers:
BRC:OLD FLIGHT CLASS DEST;NEW FLIGHT CLASS DEST
Note: The DEST is only required for multi-sector flights.
6. Remove Protective Cover.
Bulk Recheck Accepted Passengers with Paid Seats

The BRC transaction with option 'P' allows the supervisor to transfer all checked-in
passengers with the paid seat service fee.
The BRC entry is:
BRC: ORIGINAL FLIGHT/DATE,P;NEW BRC:MH1135/.,P;MH2020/ .
FLIGHT/DATE
It is also possible to transfer an individual passenger with the paid seat service fee. The "PS"
is required in the BRC: entry.
Entry after displaying the PS list with the PAID option:
BRC: ENTRY NUMBER PS, ENTRY BRC:3PS,7PS,8PS;MH2020/.
NUMBER PS, ENTRY NUMBER PS;NEW
FLIGHT
BRC: ENTRY RANGE PS;NEW FLIGHT BRC::1-10PS;MH2020/.
Note: It is advised to add the Go-Show limit to the new flight number to avoid transferring
passengers as standby.
Bulk Recheck Standby Passengers (BR)

The BR transaction allows the supervisor to transfer STANDBY (not accepted) passengers
from one flight to another. This transaction is restricted to 'GATE CRT' only. For those Airlines
that do not have Gate CRTS, then follow the explanation under BRC on how to proceed.
The BR entry is:
BR:ORIGINAL FLIGHT;NEW FLIGHT BR:XS395C;XS397C
Note: A specific class can be input. It is also possible to transfer the passengers from one
class to another (example BR:XS395Y;XS397M).
It is also possible to transfer specific standby passengers from one flight to another by
selecting the entry numbers from a standby list (SB:FLIGHT/.). The "SB:" is required in the
BR: entry.
Entry after display SB list:
BR:ENTRY NUMBER SB,ENTRY NUMBER BR:8SB,12SB,15SB;XS400M
SB; NEW FLIGHT CLASS

Guide
Copyright © SITA Information Networking Computing 22. Bulk Recheck Passengers to a New Flight
Page 146
BR:RANGE OF ENTRY NUMBERS SB;NEW BR:8-15SB;XS405M
FLIGHT CLASS
Bulk Recheck not Checked-In Passengers (BRN)

The BRN transaction allows the supervisor to transfer NOT CHECKED-IN (not accepted or
on standby) passengers from one flight to another. This transaction is restricted to 'GATE
CRT' only. For those airlines that do not have Gate CRTS, follow the explanation under BRC
on how to proceed.
The BRN entry is:
BRN:ORIGINAL FLIGHT;NEW FLIGHT
Transfer all not checked-in passengers from XS395 to XS397:
BRN:XS395C;XS397C
Note: A specific class can be input. It is also possible to transfer the passengers from one
class to another (example BRN:XS395Y;XS397M).
It is also possible to transfer specific not checked-in passengers from one flight to another by
selecting the entry numbers from a passenger list (PS:FLIGHT,NACC). The 'PS' is required
in the BRN: entry.
Entry after display PS list:
BRN:ENTRY NUMBER PS,ENTRY NUMBER PS;NEW FLIGHT CLASS
or
BRN:RANGE OF ENTRY NUMBERS PS;NEW FLIGHT CLASS
Note: The Supervisor and Staff should be familiar with history of Bulk Recheck transaction as
shown in both PDD: display of Original and New flight.
Error Responses
CHECK-IN TIME The new flight is not open for check-in.
CLASS Class not on new aircraft.
CONFLICT A mandatory element is missing.
FLT CLOSED/CANCELLED Flight is already closed or has been cancelled.
FLT NUMBER Invalid original flight number entered.
GATE ONLY Gate CRT must be entered on the original flight.
HOLD A 'hold' exists on one of the flights.

USA Inc.
Page 147
NO ACTION IND There are no passengers to re-check.
NO DISPLAY Entry was not preceded by a passenger display.
PAX ALREADY CHECKED- The selected passengers contain some checked or standby
IN passengers.
PAX STATUS CONFLICT At least one of the passengers identified is canceled off the
flight.
PROT COV One of the flights is under protective cover.
PSGR REQUIRES Modification not allowed as passenger is part of an AEC aircraft

SEATING - AEC type/version change.
RECHECK The flight, class, or destination specified on the original flight

FLIGHT/CLASS/DEST does not exist on the new flight.
Bulk Recheck for Not Accepted Passengers with Paid Seats

The BRN transaction with option 'P' allows the supervisor to transfer all checked-in
passengers with the paid seat service fee.
The BRN entry is:
BRN: ORIGINAL FLIGHT/DATE,P;NEW BRN:MH1135/.,P;MH2020/ .
FLIGHT/DATE
It is also possible to transfer an individual passenger with the paid seat service fee. The "PS"
is required in the BRN: entry.
Entry after displaying the PS list with the PAID option:
BRN: ENTRY NUMBER PS, ENTRY BRN:3PS,7PS,8PS;MH2020/.
NUMBER PS, ENTRY NUMBER PS;NEW
FLIGHT
BRN: ENTRY RANGE PS;NEW FLIGHT BRN::1-10PS;MH2020/.
Note: It is advised to add the Go-Show limit to the new flight number to avoid transferring
passengers as standby.

Guide
Copyright © SITA Information Networking Computing 22. Bulk Recheck Passengers to a New Flight
Page 148
23. Interline Through Check-In (ITCI)
EDIFACT is the acronym used to describe the Electronic Data Interchange for
Administration, Commerce and Transport; and is applied to the format used in transferring
business documentation or transactions in a structured, computer readable style. It is not only
used by airlines but is widely used in all forms of Commercial, Industrial, and Professional
Businesses.
Inter-Airline Thru Check-In (IATCI) comprises all the passenger handling procedures
associated with a passenger traveling on one airline's flight and transferring onto another
airline's flight, using a single check-in transaction entry.
Note: Refer to the SDCS Check-In Agent Guide for ITCI check-in formats.
Purpose
EDIFACT is a translator of transaction exchanges between two or more airlines who operate
different DCS systems and who have a Bilateral Agreement with each other to perform
‘INTER AIRLINE THRU CHECK-IN', (IATCI), passengers on flights from one airline's DCS
system onto the other.
EDIFACT translates DCS messages in a 'Real Time' environment between the two systems
into a format understood by both systems so that passengers can be checked-in, issued Seat
Numbers, Boarding Cards and Baggage Tags for flights on both systems by the same
transaction entry.
Bilateral Agreements
Before IATCI can be implemented for an airline, that airline must have an individual Bilateral
Agreement with every airline with which they plan to utilize IATCI. Each Bilateral Agreement
establishes rules and regulations as agreed between the two airlines involved. These rules
include the types of passengers allowed for ITCI and specifics for processing including the
version of EDIFACT both systems will utilize.
Restrictions
Although passengers may hold 'Boarding Cards' for their onward flight onto another airline
with whom they have a Bilateral Agreement for 'THRU CHECK-IN', the passengers must
retain their 'Flight Coupons' for their onward flight and surrender it to the onward Airline at
their transfer destination.
n IATCI will not handle passengers with extra seats and the system rejects any attempt to
'THRU CHECK-IN' such a passenger.
n IATCI will not handle 'URES OR NOREC PASSENGERS' on the onward flight.
Successful IATCI depends on passenger(s) being booked on both airlines and the ability of

USA Inc.
Page 149
both systems to match a query on their system with the correct passenger name.
n Other restrictions may apply depending on the partner system or bilateral agreements
between the two partners.
Flight Schedules/DFL (NPRO)

Flight Schedules
There is no change to the current procedures for creating, amending, or cancelling flight
schedules.
DFL (NPRO)
Do not use the DFL:FLIGHT/DATE/NPRO transaction after check-in has started when an
EDIFACT flight is involved due to the problems that could occur in reconciling all the
passenger figures. If a situation arises where there is no alternative from doing the DFL, then
any passengers 'THRU CHECKED-IN' should be deleted before the DFL/NPRO transaction
is entered and later checked-in again when the flight is re-created.
CSM/CSU/IFM
CSM/CSU
There is an additional IATA message added to the CSM/CSU display which is the Interline
Fallback Message (IFM). This is found on the MSG line of the CSM/CSU display as follows:
MSG _PTM _COM _PSM _PIL _COM _IDM _SOM _PFS _ FTL _IFM
IFM (Inter Airline Fallback Message)

The IFM provides an IATCI partner at the transfer station a list of details of all passengers with
problems to whom a delete, (PW) or an update, (PU) was attempted, and was not successful
(no response was received back from the partner flight).
This message enables check-in data synchronization for both querying and responding airline
and should be helpful to the check-in agent in passenger and baggage reconciliation.
Passengers on whom a response was received from the partner system, and the surname
does not match the surname stored in our system that initiated the request to check-in,
causing a discrepancy.
The following is an example of an IFM message for a flight of XS378 operating ATL to LHR
and passengers are ‘THRU CHECKED' onto flight YY827 LHR to MAN:

Guide
Copyright © SITA Information Networking Computing 23. Interline Through Check-In (ITCI)
Page 150
The connecting airline should retrieve the individual passenger records and update
accordingly based upon the IFM message.
If there is more than one part, then the message ends with ENDPART1 and the second
message starts with PART2.
The items that can be displayed after a name are:
.R/CLS Class of travel on onward flight. If not stored, .R/CLS is not
displayed.
.R/SEAT Seat Number on onward flight. If not stored, .R/SEAT is not

displayed.
.R/REC Boarding Number on onward flight. If not stored, .R/REC is not

displayed.
.R/IREC Boarding Number of originating flight. If not stored, .R/IREC is

not displayed.
.R/SSR SSR codes attached to a passenger's record.
.B/ Baggage details with bag pieces followed by bag weight (1/12).
For pooled bag the display shows '.B/PLD' and if baggage is
zero or missing the display is '.B/0'.

USA Inc.
Page 151
.N/ Bag tag number followed by number of bag tags in the range
(even if it is only 1), and the final destination of the bag. If the bag
tag numbers are not in sequence then a separate .N/ is shown.
The system converts the three-digit airline code into the issuing
airline two-letter code.
SI This text is 'hard coded' into the system and it is not possible to
add or amend text to this topic.
Use and Restrictions

The IFM notes unsuccessful passenger updates and deletions (PU or PW). The IFM
message is dispatched when information is present; it is not sent when there is no
information. A separate IFM message is sent to the transfer point for each different Airline
with Interline passengers.
Additional Processing
The message is dispatched at the end of the flight when the CCF transaction is entered in the
normal way, and goes to the ITCI partner addresses specified in the CX message address
table for that destination. This message is also displayed to the screen or a printer using the
'LR' transaction.
Errors
There are no specific error responses associated with the IFM, other than error responses
applicable to the LR, CCF, or CX transaction.
Check Documentation for Transit Stop Flights

The SITA Departure Control System will display a warning message if a passenger is
transiting a point(s) between origin and destination. For example, when a passenger is
traveling from Point A to Point D and transiting Point B and Point C that are in different
countries, a warning message: 'Document Check Required-Passenger Transits XXX' is
displayed if the transit country is in the government tables. The flight schedule includes all
points: A, B, C, and D.
Passenger traveling from AMM to SIN where BAH is the transit city.
When the passenger is checked in from AMM to SIN, the system displays 'EDI*DOCUMENT
CHECK REQUIRED – PASSENGER TRANSITS BAH'.

Guide
Page 152
APP/AQQ Codes and ITCI Reponses
APP/AQQ Boarding Description

Return Codes Pass (BP)
in SDCS Status
8501 BP printed Watchlist cleared.
8502 BP inhibited Expected Movement record has not been created. May
be overridden by ‘APPA’ or ‘APPG’.

USA Inc.
Page 153
APP/AQQ Boarding Description
Return Codes Pass (BP)
in SDCS Status
8503 BP inhibited Board if 'DOCS OK'. Passenger record not found in
Government database (applies to KW and ZA only).
8505 NA Cancelled movement. Passenger deleted.
8506 NA Cancellation unsuccessful. Previous record not found.
8507 BP inhibited Duplicate name. Retry APP (applies to AU, NZ, KW,
and BH only).
8508 BP printed Repeated OK to Board. Already boarded the passenger.

Check Travel DOCS (applies to AU And NZ).
8509 BP inhibited Border closed in the event of emergency (applies to NZ

only).
8510 BP inhibited DOCS OK. Contact EOC (Entry Operations Center AU)
(applies to AU).
8516 BP inhibited Insufficient data. Provide complete data.
8517 BP printed Override accepted (applies to AU, NZ, KW, BH, and
ZA).
8519 BOARD with Passenger allowed to board if holding onward ticket

OWT- (applies to NZ and ZA).
8520 BP inhibited DOCS OK. Contact NZIS(Advanced Passenger

screening NZ) (applies to NZ).
8530 BP inhibited DOCS OK. Contact GDPNR (applies to BH).
8540 BP inhibited All required data is available. Check-in agent must seek
advice from CBP.
Watchlist inhibited.
Similar to AQQ ESTA code 1 (applies to US).
8541 BP Boarding pass may be issued. Further security checks

printed/inhibited are required before the passenger can be permitted to
board.
Similar to AQQ ESTA code 2 (applies to US).
8550 BP inhibited DOCS OK. Contact MOI (applies to KW).
8590 BP inhibited DOCS OK. Contact DHA (applies to ZA).

Guide
Page 154
Single Passenger Check-in
When a single passenger is being checked-in and the response is 'UNABLE TO CHECK IN
SECURITY PROFILE RESTRICTION', the passenger is denied a seat.
Multiple Passenger Check-in

When multiple passengers are being checked-in for an ITCI APP flight, the response is
ERD+1:199.
Passenger Already Checked-in

If a passenger is already checked-in, which may include Web checked-in passengers) from
connecting city to destination, the seat assigned is returned as well as the message
'PASSENGER SURNAME ALREADY CHECKED-IN'.
ETM (EDIFACT Transfer Message)

The ETM is an EDIFACT Transfer Message and is the opposite of the IFM message. It gives
a list of all the passengers that have been successfully checked-in from one flight on one DCS
system into an onward flight on another DCS system. The ETM is not an IATA message, but
is provided as a requirement for airlines with a bilateral agreement with Lufthansa.

USA Inc.
Page 155
An example of an ETM message for a flight of XS378 operating ATL to LHR and passengers
are 'THRU CHECKED' onto flights operated by YY out of LHR:
The message contains the following information:

n Transfer flight number/date and destination
n Total number of passengers by class plus total amount of baggage
n Number and family name followed by amount of baggage and boarding numbers held on
the connecting flight
This message can also be displayed to the screen or a printer using the 'LR' transaction.
Processing
One ETM message is sent with all flight connections out of the next onward destination.
The ETM message can be added to the CX destination address table for every destination as
required, using the CMM entry. If there is no address present in the CX table for that
destination, then the message will be sent to the DFL (default) address.
Restrictions
The ETM message is dispatched if there is information present. It is not sent when there is
NIL information. The ETM address is hard-coded by the airline and cannot be added to the
CSM message.
Errors
There are no specific error responses associated with the IFM, other than error responses
applicable to the LR, CCF, or CX transaction.
EDIFACT Flights / Interline Thru Check-In

An Interline Thru Check-In (ITCI) flight is where a passenger was checked-in on a flight by
one airline in their DCS system and 'Through checked' onto an onward connecting flight in
another Airline's DCS system using EDIFACT messaging. A boarding card is issued for both
flights. EDIFACT translates the check-in messages sent between the two airlines so that they

Guide
Page 156
can be translated and read / understood by each airline's own computer system. Before
EDIFACT messaging can be implemented for an airline, they must first obtain a Bilateral
agreement with the airline or airlines they want to utilize the 'Through' check-in procedure
with.
Electronic System of Travel Authorization (ESTA)

Electronic System of Travel Authorization (ESTA) is an automated system used to determine
the eligibility of visitors traveling to the United States under the Visa Waiver Program (VWP)
and whether such travel poses any law enforcement or security risk.
ESTA Codes for ITCI Passengers
ESTA ITCI Error Required Action

Response
SEAT HELD – Boarding Pass Provide proper travel authorization document.
Inhibited
Destination Address, Street, Add details if not updated or missing.

and Number Required
Destination Address, City Add details if not updated or missing.

Name Required
Destination Address, State Add details if not updated or missing.

Required
Destination Address, Post Add details if not updated or missing

Code Required
No ESTA on File ESTA information to be updated. Travel authorization

documents are required to be checked.
ESTA Denied Contact CBP.
Insufficient Data for ESTA Provide proper travel authorization documents.

Verification
ESTA on File Boarding Pass Printed
AQQ – ESTA – CBP Codes and Corresponding ITCI Responses
ESTA-AQQ CBP Code ESTA –AQQ Boarding Description

Return Pass Status
Codes in
SDCS
0X 8560 BP inhibited Insufficient data to provide
ESTA status.

USA Inc.
Page 157
ESTA-AQQ CBP Code ESTA –AQQ Boarding Description
Return Pass Status
Codes in
SDCS
0Z 8561 BP printed Travel Authorization via
ESTA not applicable.
0A 8562 BP printed VWP participant passport.

Approved authorization via
ESTA.
0B 8563 BP inhibited VWP participant passport.

No application for travel
authorization via ESTA on
file.
0C 8564 BP inhibited VWP participant passport.

US authorized travel
document required.
11 8565 BP inhibited Inhibited-ESTA denied.
2X 8566 BP inhibited Insufficient data to provide

ESTA status.
2Z 8567 BP printed Travel authorization via

ESTA not applicable.
2A 8568 BP printed VWP participant passport.

Approved authorization via
ESTA.
2B 8569 BP inhibited VWP participant passport.

No application for travel
authorization via ESTA on
file.
2C 8570 BP inhibited VWP participant passport.

US authorized travel
document required.
Inbound ITCI (SDCS is the Receiver)

For an ITCI query to an AQQ ESTA SDCS connection, ITCI will verify documents entered
and responds with a 'Response on Acceptance' based on the standard ESTA protocol
responses.

Guide
Page 158
Outbound ITCI (SDCS is the Sender)
For a query to an AQQ ESTA partner connection, a 'Response on Acceptance' will be
returned and SDCS will action the response.

USA Inc.
Page 159
Guide
Page 160
24. Advance Passenger Information System
The Advance Passenger Information System, (APIS), is an automated system that enables
foreign governments and passenger carriers, such as airlines and cruise ships, to provide
advance passenger and passport information to Immigration and Passport Control Agencies
at the first port of call of the destination country, to facilitate advance inspection of the
incoming information prior to the arrival of the passengers at that control point.
Passport information is entered into a passenger record at the time the passenger makes the
reservation, or at the time they check in at the point of departure. Passenger carriers can send
passport information for each passenger to Immigration and Passport Control Agencies on
an API Message in EDIFACT format. This message is delivered as type B traffic.
Advance Passenger Information

API Message (Advance Passenger Information)
An API message is sent at departure time as one of the post departure messages. Post
departure messages are built for each flight according to the CSM screen for each flight.
When the flight is built in FDC, the default for the API message is not to appear on the CSM
screen. After a flight is built, the message header API must be added to the message line for
the master flight schedule, or on a daily basis, just as other messages are added or deleted
from the CSM screen if an API message is required for the flight.
CSM/CSU Use and Restrictions

There is no change to the existing CSM/CSU use and restrictions. The only change adds an
option for the API message. API is a default message on CSM but the message is only sent to
countries which require the API message.
CSM/CSU Input
The input of the CSM is not changed. The additional message type of API is allowed on the
message line like other departure messages are entered. An example of API entered on a
CSM format is shown below.
CSM/CSU Processing
This display includes the API message and builds and processes the message within the
guidelines of API requirements.

USA Inc.
Page 161
CSM/CSU Output
There is no change to the existing output.
Error Responses
There are no changes to the existing error responses for CSM/CSU.
Subsequent Processing
All processing not specifically mentioned remains unchanged.
Boarding Pass Inhibit

The ability to inhibit boarding pass printing is available for all countries requiring APIS. The
Helpdesk should be contacted to set the boarding pass inhibit parameter. In addition,
segment data for the segments requiring boarding pass inhibit should be added to the CSM.
CSD for a flight inhibiting boarding pass for routing JFK YYZ and JFK YVR:
Releasing API with the Departure Messages

The API message is sent with the post departure messages. Post departure messages are
sent when the flight is released in CKI with the CCF transaction.

Guide
Copyright © SITA Information Networking Computing 24. Advance Passenger Information System
Page 162
CCF Use and Restrictions
If the API is present on the CSM screen the flight will prepare and build the message.
Passenger information is included in the API message if it has the minimum mandatory
requirements as set forth by the applicable border control agency.These requirements are:
n passenger’s full name (as shown on the passport)
n passport number
n country of issue
n Date of birth
The PA message is sent to the applicable border control agency Data Center when the CCF
transaction is input. If either 50% of the passengers on the flight, or 100 passengers on the
flight, whichever is greater, have PSPT remarks that meet the minimum mandatory
requirements according to the applicable border control agencies.
CCF Input
There is no change to the input of the CCF transaction.
CCF Processing
In addition to the current processing, the API message is sent after all required checks are
made as described in the API Message (Advance Passenger Information) sub-section in
Advance Passenger Information System section.
CCF Output
Current output is not changed. The option to send the API message is available.
Error Responses
All existing error responses are the same for the CCF.
API Message Generation

The API message can be sent to the applicable border control agency at other times than
flight release. This is accomplished with the LR transaction.
LR Use and Restrictions

The existing use and restrictions of the LR transaction apply. The API message is an
additional message type available. The API message is in the EDIFACT format as required
by the border control agencies and is transmitted directly to the agency.

USA Inc.
Page 163
Different countries have different time requirements that APIS is to be sent. Generally, APIS
must be sent within 15 minutes of departure. Some countries may have a different time
requirement for the Crew APIS, but it is usually sent prior to departure.
LR Input
The format of the LR transaction requesting an API message is:
►LR:FLT/DATE/STN/API/P/US/DCSUCCR
To include the crew, enter:
►LR:FLT/DATE/STN/API/C/US/DCSUCCR
XS flight 100 departing LHR arriving in ATL:
►LR:XS100/20AUG/ATL/API/P/US/DCAUCCR
►LR:XS100/20AUG/ATL/API/C/US/DCAUCCR
C indicates Crew, US is the country code, and DCAUCCR is the processing address for the
United States Customs and Border Protection Agency.
Use normal crew manifesting procedures, for example:
LR Processing
The LR for API has certain restrictions and a different format. Although the entry will be
accepted, it will not be sent unless one of the cities on the flight routing requires it. The entry
must also include the type of API and the country code format that is to be used. The LR
format would be as follows:
LR:FLT/DATE/STN/API/P/US/DCAUCCR
This shows that you are requesting an APIS for passenger data (P) in US format (US) to the
U.S. Customs processing address. Other data types are:
C – Crew

Guide
Page 164
PO – Passengers flying over the country with no landing
CO – Crew flying over the country with no landing
CC – Landing with Crew change only
The codes PO and CO can be used to send API to a country which does not require but
desires one anyway.
For a listing of country requirements and processing addresses, see NEWS:3/4/1,
LR Output
The API message transmitted from SDCS to the applicable border control agency conforms
with EDIFACT formats. The API message does not display on a screen or go to a printer. The
LR with the API message is an alternative method to send the message to the applicable
border control agency Data Center without reopening the flight. The address for the Customs
Data Center to process the message for both INS and Customs is DCAUCCR.
Note: Do not add the address DCAUCCR to the message address tables. The API message
is routed to that address.
LR Error Responses
Existing error responses for the LR transaction apply.
LR Subsequent Processing
Passport Information Message (PIM)

SDCS has a Passport Information Message (PIM), which includes the information in the API
message. The PIM is message is non-IATA message and readable.
Use and Restrictions

The PIM can be entered on the CX tables and the PIM is sent with the post-departure
messages when the CCF: transaction is input. The existing use and restrictions of the LR
transaction apply. The PIM message is an additional message type.
PIM Input
The format of the LR transaction requesting a PIM message is:
►LR:FLT/DATE/STN/PIM
XS flight 100 departing LHR arriving in ATL is shown below:

►LR:XS100/20AUG/ATL/PIM

USA Inc.
Page 165
PIM Processing
The LR transaction processing remains the same. The PIM message is added to the list of
message options for this transaction.
PIM Output
A PIM contains the passport (PSPT and DOCS) information in passenger records. The
information is listed in the same order as the PSPT or DOCS input.
PIM
Error Responses
Existing error responses for the LR transaction apply, see Manual Generation of Departure
Messages (LR).
The PIM is a stand-alone message. The processing is not dependent on the destination of the
flight and can be used to provide passport information to any airport or government authority if
required.
All LR: processing not specifically mentioned remains unchanged.
Passenger Manifest with Passport Information

The system has a JL transaction that generates a Passenger Manifest which lists passengers
with any passport information entered for that passenger.
JL Use and Restrictions

The existing use and restrictions of the JL transaction apply. The P option is an additional
message type available.
JL Input
The format for the input of the JL transaction has not changed. An example of a JL transaction
with the Passport option is shown below:

Guide
Page 166
JL Processing
In addition to any current processing, the JL list is generated with a list of passengers and
shows any passport information.

USA Inc.
Page 167
Output
JL list with the P option:
Error Responses
Existing error responses apply to the JL transaction.

Guide
Page 168
25. Special Passenger Handling Procedures
Transit Flights
There are automated and non-automated transit flights from the previous station.
Transit Flight from an Automated Station

If the previous station was automated using the same SITA DCS system (same Host), then
the transit passenger details are added to the SDD and Seat map screens as the passengers
check-in at the upline station. Unless there are some adjustments to these figures (for
example - offload a transit passenger), there is no need for the present station to do anything
with the transit details.
Transit Flight from a Non-Automated Station

If the previous station was non-automated, or it was automated but using a different DCS
system, then the transit passenger details can be read-into the system by receiving a SOM.
The details can also be entered manually with the BX transaction.
The SITA DCS system requires that the following address be used for the SOM so that this
message is read-into the system. The message must be in the correct format:
HDQCS** for SOM
** designates Host Airline
Note: In addition to the system address, the USER should also specify a hardcopy teletype
address in their control office, to help identify error read-in formats and also as a check or
warning when this message has been, or has not been, received on station for a particular
flight.
The SOM (Seats Occupied Message) adds the transit passenger details to the SDD screen
and also places a T on the seat map (SE:FLT/DATE) for used transit seats in the CKI area. It
also enters the area seating position of these transit passengers into the
LPAD:FLIGHT/DATE/PAX screen in LDP.

USA Inc.
Page 169
SOM Routing SFO-LAX-HOU- for Airline XS:
Once a SOM is received, it is possible to accept another corrected SOM (insert a line above
SOM and add the word COR) for any amendments to the original figures. However it is also
possible to enter the corrections manually by using the BX transaction in CKI. The
LPAD:FLT/DATE/PAX screen includes any changes.
Note: If a BX transaction is entered before the SOM is received into the system, then the
SOM will be rejected, so that the rest of the transit seats are also blocked by the BX
transaction.
The system keeps a record of any SOMs that are received (in correct format), and these can
be displayed by entering 'MD:FLT/DATE/SOM/CITY'. Any SOMs that are received in error
are directed to the KS queue of the HOST's DCS office queues. Correct SOMs also go to the
KS queue but only show 'SOM ACCEPTED'.

Guide
Copyright © SITA Information Networking Computing 25. Special Passenger Handling Procedures
Page 170
Extra Crew (XXXCREW)
XXXCrew are relief crew assigned to operate on a flight. If there are extra crew occupying
passenger seats on a flight, and the flight is connected to LDP, it is very important to know
how they have been checked-in, as it can cause incorrect passenger figures for the load
control agent. In SITA DCS there is a specific code (XXXCREW) for extra crew occupying
seats that can be used in check-in. If check-in uses the XXXCREW code, note the following:
n In check-in the XXXCREW are included in the passenger figures on the
SDD:FLIGHT/DATE screen, and are also shown separately under the code XCR on the
same screen.
n In the COM message (sent from CKI to LDP) the XXXCREW are not included in the
passenger figures but are included in the extra crew figures.
n In LDP the XXXCREW are not included on the checked-in passengers, as displayed on
the LPAD:FLIGHT/DATE/PAX2 screen.
n On the LODD:FLIGHT/DATE screen the XXXCREW are shown as extra crew in the crew
figures display, and their weight and index is displayed as an adjustment to the DOW and
DOI.
If extra crew are checked-in using a different code (or their own names), then they are
included in the normal passenger details, and do not appear on the LODD screen. In this case
it is not necessary for the load control agent to be aware of them as they are already included
in all the weight and balance calculations.
Dead Head Crew (XXXDHC)

XXXDHC are crew that are being positioned to a different location and are considered as
passengers. Dead Head Crew differ from Extra Crew as they are included in passenger
weights sent to LDP. In SITA DCS, the code (XXXDHC) checks in dead heading crew. When
using the XXXDHC for check-in, the following should be noted:
n In check-in, the XXXDHC are included in the passenger figures on the
SDD:FLIGHT/DATE screen and are also shown separately under the code DHC on the
same screen.
n In the COM message sent from CKI to LDP, the XXXDHC are included in the passenger
figures and also listed in the dead head crew figures.
n In the LDP, the XXXDHC are included on the checked-in passengers as displayed on the
LPAD: FLIGHT/DATE/PAX2 screen.
Jump Seat Passengers

Jump seat passengers are passengers (usually airline staff) that are seated in crew seats on
the aircraft because the flight is full and there are no passenger seats available.
CKI jumpseats are in the cabin, and cockpit jumpseats are entered with the LODD
transaction. There are two ways a jump seat passenger can be put on a flight:

USA Inc.
Page 171
1. In CKI by checking-in the passenger with the code JMP (for cabin jumpseats).
If the flight is connected to CKI, then these passengers are checked-in with the item JMP, and
are issued a boarding card without a seat number on it. The following should be noted:
Note: Jump Seats will not be accepted on a flight unless JMP is added when the seat map is
created (EQC:).
n In check-in the jump seat passenger is not included in the passenger figures on the
SDD:FLIGHT/DATE screen, but is shown separately under the code J on the same
screen.
n In the COM message (sent from CKI to LDP) the jump seat passenger is not included in
the passenger figures but is included in the total passenger weights.
n In LDP the jump seat passenger is included in both the class and gender totals on the
checked-in passengers, as displayed on the LPAD:FLIGHT/DATE/PAX2 screen.
n On the loadsheet the jump seat passenger is included in the class and gender totals, and
the weight included in the total traffic load.
n The LDM does include the jump seat passenger in the load details.
2. In LDP by adding the name to the LODD screen (for cockpit jumpseats).
The LODD:FLIGHT/DATE screen is displayed and the required name is added to the J/S
line.
Note: The weight and index of the jump seat passenger comes from the
LADD:REGISTRATION/CERT screen and it is added to the DOW/DOI.
In LDP the jump seat passenger is not included in either the class or the gender totals on the
checked-in passengers as displayed on the LPAD:FLIGHT/DATE/PAX2 screen.
On the loadsheet the jump seat passenger is not included in the class and gender totals, and
the weight is not included in the total traffic load, but it is included in the Dry Operating weight.
The LDM does not include the jump seat passenger in the load details but it does display the
following remark under SI: 1 JUMP SEAT RIDER.
Stretcher Passengers
The letter ‘K’ identifies stretcher seats on a seat map. If there are stretcher seats indicated in
the EQC entry and there is a stretcher passenger on the PNL, it is not necessary to block any
seats – the ‘K’ seats are displayed on the seat map. If there are no stretcher passengers on
the PNL, even though there are ‘K’ seats specified on the master seat map, these will not
show on the active seat map.
Stretcher passengers cannot be accepted without K seats on the seat map. Should a
stretcher be placed on Standby and an onload is attempted without K seats, the message
“ACCEPTANCE REJECTED” is returned.
For flights that are connected to CKI, the general procedure for handling a stretcher
passenger in DCS is as follows:

Guide
Page 172
1. PNL/ADL processing does not require that seats be blocked (X) on the seat map for a
stretcher passenger.
2. The check-in entry for passengers with stretcher remains the same.
3. For a passenger that has a STCR specified in the entry, the system searches for a ‘K’ on
the seat map and if it finds one, allocates the seat. The system ‘blanks’ the linked ‘K’ seats
so that they cannot be occupied.
4. A seat number will be allocated for a stretcher passenger prior to check-in; however, after
check-in the seat number will be replaced with STCR and the remaining ‘K’ seats will be
deleted from the seat map.
5. If there are no ‘K’ seats, the check-in is rejected and the passenger is placed on standby
with the reason code ‘STL’.
6. When check-in is attempted for a family where one passenger is identified with STCR, of if
check-in is attempted for a stretcher passenger with other passengers, the system rejects
the entry with the response ‘TOO MANY PASSENGERS’.
7. The system only allows STCR passengers to check-in by themselves (PA:1P1 etc). When
a checked-in STCR passenger is deleted from the flight, the ‘K’ seats are re-instated on
the seat map, and can be removed if necessary with the SCC entry.
Note: If there are no Stretcher passengers on the flight but you need to identify the stretcher
locations, use the RS entry. It is possible to add ‘K’ seats to the seat map using the
SCC:+K/Seat Numbers entry.
K seats cannot be used with an SNR entry. If an attendant is required to sit with the stretcher,
then one of the K seats must be changed to an assignable seat using SCC transaction (-K)
with the attendant pre-seated to that seat.
SE:FLIGHT CLASS It is important to specify the correct class.
RS:STCR Transaction adds the ‘K’ seats to the seat map.
RS:-STCR Transaction removes the ‘K’ seats from the seat map.
Seat Map
When a stretcher passenger is booked on a flight, the seat map indicates the reserved
stretcher area with ‘K’ and the stretcher passenger will have a reserved seat with ‘R’.

USA Inc.
Page 173
At check-in the stretcher passenger is assigned a seat number and boarding number with the
item STCR attached to the record, the PDD will look like the following:
The seat map will look like this:
Note: The stretcher seats disappeared from the display. If later the STCR is deleted from the
flight, the system will return the seats to the display.
Ground Handlers Electronic

Ticket check-in is available for ‘Host’ and ‘Handled’ airlines. For ‘Handled’ airlines there are
two types of methods that are used for check-in: ‘Control’ and ‘Interactive’.
Control Method
With the ‘Control’ method, the database stores all of the ticket information in its database and
has ‘control’ of the coupons. When the check-in is attempted, the ticket validation is sent to the
database and the coupon status is verified from its database.

Guide
Page 174
Interactive Method
With ‘Interactive’ method, the database does not store the ticket information; instead the
‘control’ of the coupon stays with the flight operator. When check-in is attempted, the ticket
validation still goes to the database but instead of verifying the coupon status in its database,
the validation request is sent to the flight operator.
Note: The check-in agent will see no difference between ‘Control’ and Interactive’ methods
during the check-in transaction as all the processes take place internally.
Check In Agent Error Responses
Unable Override was attempted for a denied passenger.
Ticket Not Found The electronic ticket record was not located in the electronic
ticket database of the host airline.
Item Override not allowed by a check in agent.
ERC 150 Occurs when trying to display an ETR. Clear screen and try the
entry again.
Ticket Record Segment Mismatch Flight itinerary does not match ticket itinerary.
Electronic Ticket-Class Does Class must match ticketed RBD.

Not Match

USA Inc.
Page 175
Guide
Page 176
26. Miscellaneous Check-In Operations
Location Travel Time
During passenger check-in, there will be times when the system responds LOCATION
TRAVEL TIME 0'. This will inhibit any further check-in until this response is cleared.
There are three main reasons that can cause this response:
1. STD / ETD
This is the most common one, and occurs when the Scheduled Time of Departure (STD) or
Estimated Time of Departure (ETD) has been reached on the flight. If the flight is delayed and
there are still passengers to check-in, then a new ETD should be entered via the FUI
transaction before check-in can continue.
Note: If the STD or ETD is correct but the system is still giving this response, then check that
the correct GMT adjustment time is entered for the departure city by checking the CITY files.
This can be verified by contacting your Reservations department (this sometimes happens
when the summer/winter time differences are introduced and the city was not updated
correctly).
2. GATE NUMBER
Another common reason is that as soon as a Gate Number is entered for a flight check-in is
not stopped, it is restricted to the gate zone only. This is related to the ZONE number of the
gate being different from the ZONE of the input CRT. Normally the Gate Zones are created
as ZONE 1 (this can be checked by displaying the AZ:CITY table), and therefore this should
correspond to the CKZN entered in the DPID of the CRT. If the CRT shows CKZN as 0, then
change it to 1 (or to the corresponding Gate Zone number), and then check-in should be able
to proceed as normal.
3. THROUGH CHECK-IN
This reason only affects those Airlines that are attempting to 'Through' check-in a passenger
from their station onto a flight at a downline transit station. If check-in is suddenly inhibited, it is
usually because the downline station (transit point) has entered a Gate number and that CITY
is not entered on the first station's LZ table.
For example, if a passenger is being checked-in on flight XS397 operating ATL - JFK, and
being 'through' checked-in on flight XS937 JFK - BOS, and a Gate number (Zone 1) is
entered on flight XS937 out of JFK, the LZ table of ATL should show ATL and JFK and
likewise the JFK LZ table should show JFK and ATL:
Response of Entry LZ:ATL1

USA Inc.
Page 177
If these tables are set-up correctly, then 'Through' check-in can proceed, whether a Gate
number is entered on either flight or not.
Pre-Seat Passenger on Onward Flight

To pre-seat a passenger on an onward flight connection, the PA and not the PU entry must
be used. The maximum number of outbound connections is three (O3).
PA: # ENTRY NBR,O,R12A

PA: # ENTRY NBR,R17A,O,R12A
Note: The above entries will only work provided the passenger is not checked-in on the first
flight. If the passenger has checked-in then it is not possible to pre-seat him on the onward
flight.
Re-Seat Passenger On Onward Flight

It is possible to change the seat number on an onward flight connection after the passenger
has checked-in on both flights. It involves two steps.
Enter:
PDD:FLIGHT STN, BN NBR
PU:1,SNR SEAT NBR

Guide
Copyright © SITA Information Networking Computing 26. Miscellaneous Check-In Operations
Page 178
The entry to change a seat number for a checked-in passenger on the second leg of the same
flight is:
PU:ENTRY NBR, SNR SEAT NBR/SEGMENT
PU:1,SNR17A/ATLMIA
Note: When using the PU entry, use SNR as R will not work.
Turn Around Flights (Round Robin)

A TURN AROUND (or ROUND ROBIN) flight, as defined by IATA, is a flight where the Final
destination is the same as the Origin station, with as many intermediate stations as desired,
providing the intermediate stations do not appear more than once in the itinerary.
For example an acceptable routing could be:
AAA-BBB-CCC-AAA
Routings that are unacceptable are:
AAA-BBB-AAA-CCC
BBB-AAA-CCC-AAA
Flight schedules can be built in the usual way, and all passenger handling transactions will
remain the same. The only restrictions are that the system will inhibit the check-in of
passengers from and to the same station. The SDD screen is slightly different as it displays a
'blinking' warning, the words '** ROUND ROBIN CITY **' (CITY is replaced by the actual
station where the flight starts and ends) on the header line, and the line displaying the
segment booking (R) and checked-in (C) information is omitted for the First to Last segment if
they are the same station. The restriction is that you cannot depart twice from the same
airport.

USA Inc.
Page 179
For example if there is a flight operating ATL-MIA-ATL, the SDD appears as follows:
SDD for Round Robin Flight
When the flight is CLOSED and RELEASED to MIA, the MIA SDD screen shows the same
display except it shows MIA as the departure station and ATL as the destination. It will not
show any TRANSIT line.
The passenger messages dispatched at the end of the flight will not show the First to Last
segment if they are the same station. SDD at the origin station will not show that station as a
destination.
Check In Override
If at any time during the check-in process, there is no response to/from the ‘electronic ticketing
database’, the customer has two choices:
1. Do nothing until a response is received.
2. Complete the check-in using the ‘override’ (OVR) option.
Because the ‘OVR’ function has the potential to accept passengers with invalid coupon
statuses, it is restricted to Supervisor and Control User levels only. This means that if an
agent with an invalid agent level attempts a ‘PA’ entry that contains ‘OVR’, it is rejected with
the error message ‘ITEM’.
A Control Agent or Supervisor can add the item ‘OVR’ with the PA entry for a passenger with
a TKNE in their record. In this case the ticket is not validated from the e-ticket database.
Instead the passenger is accepted on the flight and no update of the coupon status is sent to
the ticketing database. Instead when the ETL message is dispatched at the end of the flight,
this is when the passenger’s coupon status is updated.
Entry using OVR in the check-in entry:
PA:1/10,B,OVR

Guide
Page 180
The following restrictions apply, ‘OVR’:
n Can only be added to the ‘Local’ flight and not to any onward connections.
n Is not allowed with a ‘PU’ entry.
n Is not allowed if the passenger has already had ‘DEN’ attached to their PDD record.
Note: Once the ‘OVR’ is added during the check-in process, it is recorded in the PDD record
display.
PDD Display:
It is possible that a passenger that has been checked-in with the ‘OVR’ item can be deleted
from the flight and then checked-in again without the OVR. In this case, the check-in process
would revert to trying to validate the coupon in the electronic ticket database.

USA Inc.
Page 181
Guide
Page 182
27. Passenger Checked-In Statistics
Passenger Statistics (PCI)
The PCI transaction allows supervisors to display or print various passenger checked-in
statistic reports. There are two methods designed to generate these reports.
The first method uses a formatted menu screen to select reports. Enter:
PCI:
PCI Format Menu Display Method:
Explanation
REPORT TYPE/FORMAT
These reports may be one of the following:
Daily Detail Report

The daily detail report consists of two parts.
1. Part 1 contains the flight number, the number of checked-in passengers by class group,
and the aircraft configuration.
2. Part 2 contains the total passengers checked-in for the selected date.
This report cannot be selected for dates less than three days old (as the statistics have not yet
been compiled by the system), and not for dates more than 90 days old. The report is not
restricted to dates more than 90 days old. It is restricted to 90 days of operation. If a flight does
not operate daily, then the report can go back beyond 90 calendar days.

USA Inc.
Page 183
Daily Summary Report
The daily summary report contains the total passengers checked-in for the selected date. This
report cannot be selected for dates less than three days old (as the statistics have not yet
been compiled by the system), and not for dates more than 90 days old.
Monthly Summary Report

The monthly summary report (detail reports are not available by month only by day) contains
the total passengers checked-in for the selected period. This report cannot be selected for
dates less than three days old (as the statistics have not yet been compiled by the system), or
for dates more than 24 months old.
AIRLINE CODE
The airline code for the report required is entered here. If an airline wants a total number of
passengers checked-in including all handled carriers then 'ALL' is specified in place of an
airline code.
BEGIN/END DATE
For daily reports the actual begin date and end date must be specified (example Begin:01
AUG 06 End:05 AUG 06). For monthly reports only the month and year is specified, if a date
is also specified then the system sends an error response.
SEND REPORT TO/PRINTER PID
The requested report can be sent to either the transmitting CRT (T) or to a printer (P). If the
printer is specified and it is not associated as the printer connected to the transmitting CRT,
then a printer PID number must be entered.
SORT KEYS
Use the SORT key field to specify the order of how the selected report is to be produced. If
this field is not entered then the system uses the following list in default order:
Detail format - D (date), A (airline), C (city), F (flight), P (PCI total).
Summary format - D (date), A (airline), P (PCI total), F (flight), L (number of legs).
Once all the details have been entered and the screen transmitted, if the report has been
requested to the transmitting CRT, the response is:
Response to CRT Screen after Transmission of PCI Entry
The 'MSG WAIT' appears on the screen, and by pressing the 'MSG WAIT' key, the report
displays on the screen.
The second PCI method requires a manual one line entry containing information already
described in method 1. Enter:
PCI:TYPE/FORMAT/ALC/BEGIN DATE/END DATE/DEVICE/PID/OPTIONS

Guide
Copyright © SITA Information Networking Computing 27. Passenger Checked-In Statistics
Page 184
Explanation
PCI: M Function code
TYPE M Report type D = daily

M=
monthly
FORMAT O Report format D=

detailed
S=
summary
ALC O Airline code or 'ALL'
BEGIN DATE O Begin date (day/month)
END DATE O End date (day/month)
DEVICE O Print / display destination device P = printer

T=
terminal
PID O If DEVICE is "P" the printer PID number is required.
OPTION O If FORMAT is "D" sort key options ACDFP may be used if

FORMAT is "S" sort key ADFLP options may be used
(See Formatted Menu Description of Sort Key Options).
Note: M – Mandatory field; O - Optional field.
Manual Entry Method:

PCI:M/S/ALL/AUG/AUG/T
Monthly PCI Summary Report:

USA Inc.
Page 185
The above entry displays a monthly summary report for the host airline for the month of
August. Note the slash (/) must be entered.
PCI:D/D/ALL/01AUG/31AUG/P
The above entry will print a daily detailed report for the date range given to the default printer.
Error Responses
MSG 001 PCI REPORT MENU NOT DISPLAYED - ENTER ►PCI: FIRST - The PCI:
transaction must be entered before the PCIG: display.
ERR 002 INVALID REPORT TYPE - PLEASE ENTER A VALID TYPE - System only
accepts a 'D' or 'M'.
ERR 003 INVALID FORMAT CODE - PLEASE ENTER A VALID CODE - System only
accepts 'D' or 'S'.
ERR 004 FORMAT CODE 'D' ONLY ALLOWED FOR DAILY REPORTS B - Detail
format cannot be requested for monthly report.
ERR 005 INVALID AIRLINE CODE - PLEASE ENTER 2 CHAR ONLY - Only two
character airline code or 'ALL' accepted.
ERR 006 INVALID HOST AIRLINE ENTERED - PLEASE TRY AGAIN - User is signed-
into XS area.

Guide
Page 186
ERR 007 INVALID AIRLINE ENTERED - PLEASE TRY AGAIN - An airline code has
been entered which is not created.
ERR 008 INTERNAL ERROR CONTACT DCS CUSTOMER SUPPORT - Contact

SITA DCS Customer Support to solve this problem.
ERR 009 Not used. Reserved for DCS programming.
ERR 010 END DATE CANNOT BE LESS THAN THE BEGIN DATE - The 'end' date
entered starts before the 'begin' date.
ERR 011 DAY FIELD NOT ALLOWED FOR MONTHLY REPORTS - Only month and
year are entered for monthly reports.
ERR 012 MONTH REQUIRED - PLEASE ENTER A MONTH - Month is missing, enter
correct date.
ERR 013 INVALID MONTH ENTERED - USE STANDARD NOTATION - Only

JAN/FEB/MAR/APR/MAY/JUN/JUL/AUG/SEP/OCT/NOV/DEC accepted.
ERR 014 DAY FIELD REQUIRED FOR DAILY REPORTS - Date is missing for daily
report, enter correct date.
ERR 015 DAY EXCEEDS MAX NUMBER OF DAYS FOR MONTH ENTERED - Check
the 'end' date of month entered.
ERR 016 Not used - Reserved for DCS programming.
ERR 017 INVALID DESTINATION - PLEASE ENTER "P" OR "T" - System only
accepts 'P' or 'T'.
ERR 018 DAILY REPORT MUST GO TO PRINTER OR BE LIMITED TO 1 DAY -

Requested report is too large for CRT, so must be sent to a printer.
ERR 019 PRINTER PID NOT ALLOWED FOR TERMINAL OUTPUT PIDN - number
entry not allowed if report request is to CRT.
ERR 020 NO DEFAULT PRINTER FOR YOUR TERMINAL - ENTER A PID as no

printer associated with CRT, enter printer PID number.
ERR 021 THIS DEVICE IS NOT CONFIGURED - ENTER ANOTHER PID - An invalid
printer PID number was entered.
ERR 022 THIS DEVICE IS NOT A PRINTER - ENTER ANOTHER PID An invalid
printer PID number was entered.
ERR 023 DEVICE HOST MISMATCH - PLEASE TRY AGAIN - Printer PID number
entered does not belong to user.
ERR 024 Not used - reserved for DCS programming.

USA Inc.
Page 187
ERR 025 INVALID KEY ENTERED FOR REPORT FORMAT SELECTED - Check 'sort'
keys selected, as invalid code selected.
ERR 026 DUPLICATE KEY ENTERED - PLEASE TRY AGAIN - The same 'sort' key
has been entered more than once.
ERR 027 EMBEDDED SPACE FOUND - ENTER ALL KEYS TOGETHER - A space is
not allowed between the 'sort' keys selected.
ERR 028 Not used, reserved for DCS programming.

Guide
Page 188
28. Flight History Journal
Flight Journal Help Screen (FJ/H)
The flight history journal is a record of certain transactions that were input on a particular
flight, or of certain CKI database functions that might have affected all flights. All times
specified are in G.M.T. If a supervisor forgets the entry format it is possible to enter the
following:
FJ/H
The response is a display to the screen.
Flight Journal Help Screen
Flight Journal Help Screen (FJ/H)

The flight history Journal can contain various items, depending on the type of report
requested. The two types are:
DETAIL (D)
SUMMARY (S)
The detail report shows the actual transaction entry input, while the summary report only
displays the function code used.
The FLIGHT HISTORY for a flight can be accessed for up to ten (10) days on the 'ON-LINE'
system before it is transferred to 'STORAGE TAPES'. Once the information goes to

USA Inc.
Page 189
'STORAGE TAPES' it can be further accessed for up to Eighty (80) days before it is erased.
The main difference between accessing the 'STORAGE TAPES' and the 'ON-LINE' system
is that it takes longer for the system to process the entry from the tapes, and it is only possible
to get a 'DETAILED' report for the whole flight and not by an individual transaction.
Only a single report can be retrieved, specific transactions cannot be requested. If you
attempt to retrieve more than a single transaction, a ‘TAPE LOADED FLIGHT’ message is
returned.
Detail report request to the transmitting CRT:
FJ:FLIGHT/DATE/D/TRANSACTION CODE
See Section 0 for Transaction Codes
The response to the screen is:
A 'MSG WAIT' appears on the CRT, and the report can be displayed by transmitting the
'MSG WAIT' key.
Note: The response can take longer than normal (depending on the history report entered),
because the system has to review all its records to get the required information.
FJ:XS479/./D/CCL

Guide
Copyright © SITA Information Networking Computing 28. Flight History Journal
Page 190
Flight History Journal
Explanation
1. The Flight History Journal entry requested is repeated.
2. The Journal returns information in the following order: Transaction Date / Time, Agent,
Function Code, Flight Number, Flight Date, City where function entry made, PID number
where function entry made.
3. Actual Function entry.
If the report is required to be sent to a printer, enter:
FJ:FLIGHT/DATE/D/TRANSACTION CODE/P PID NUMBER
FJ:XS479/./D/CCL/P1390
Summary report request entry to the transmitting CRT:
FJ:FLIGHT/DATE/S/TRANSACTION CODE
FJ:XS479/./S/CCL

USA Inc.
Page 191
After the usual response, and transmitting the 'MSG WAIT' key, the report is in the following
format:
Flight Journal Summary
Explanation
The Summary Report only gives the function code used (in this example CCL), but does not
give the actual input entry FJ.
Note: In the Summary Report it is not possible to tell whether the function code was being
'ADDED' to the flight or being 'DELETED'.
The entry to get all the transactions entered on a flight (this will also include all LDP entries) is:
FJ:FLIGHT/DATE/D
FJ:FLIGHT/DATE/S
When no times are entered the default time is the last two days.
FJ Check-In Codes
The following transaction codes are accessed by specifying the flight number in the FJ entry:
FJ:FLIGHT/DATE/D/CODE
FJ:FLIGHT/DATE/S/CODE
FJ:XS992/03JUN/D/GS

Guide
Page 192
Note: FJD/DRC type retrievals are not available from tape. These are limited to a ten day
period.
The following transaction codes are not associated with a flight number and can only be
accessed by entering a time and date in the FJ entry:
FJ:D/CODE/DATE,TIME-DATE,TIME
FJ:D/DRC/01FEB06,0001
or
FJ:D/DRC/01FEB,0001-01FEB06,2359
This transaction is limited to one day only.
Error Responses
DATE The date/time range is invalid.
DEVICE Invalid PID number specified, or belongs to another Host Airline.
OPTION The option specified is not 'S' or 'D'.

USA Inc.
Page 193
Guide
Page 194
29. Appendix – ITCI EDIFACT Error and Warning
Responses
The following Error or Warning Responses may be returned after an attempted ITCI fails:
Number Message System

1 Passenger Surname Not Found
2 Seat Not Available in Requested Class/Zone
3 Invalid Seat Request
4 Baggage Tag Number Details Required
5 Invalid Flight/Date
6 Too Many Passengers with Same Surname
7 Passenger Type Conflict/Gender Conflict
8 More Precise Gender Required
9 Flight Not Open for Through Check-in
10 Location of Arrival Invalid
11 Departure/Arrival City Pair Invalid
12 Unique Name Not Found
13 Invalid Seat Number
14 Airline Code and/or Flight Number Invalid
15 Flight Cancelled
16 Flight Check-in Held or Suspended Temporarily
17 Passenger Surname Already Checked In
18 Seating Conflict - Request Contradicts Facility

Rules
19 Baggage Weight Required
20 Baggage Count Conflict - Weight Update for Non

Existing Bags
21 Seat Not Available For Passenger Type
22 Too Many Connections - Need Manual Baggage

Tag

29. Appendix – ITCI EDIFACT Error and Warning Responses
USA Inc.
Page 195
23 Invalid Baggage Destination - Need Manual
Baggage Tag
24 Passenger Actual Weight Required for This Flight
25 Hand Baggage Details Required
26 No Seat Selection on This Flight
27 Location of Departure Invalid
28 Flight Rescheduled - Through Check-in No Longer

Allowed
29 Flight Full in Requested Class
30 Passenger Surname Offloaded
31 Passenger Surname Deleted/Cancelled from

Flight
32 Baggage Tag Number Invalid
33 Flight Gated - Through Check-in Not Allowed
34 Time Invalid – Minimum Connecting Time for

Through Check-in
35 Flight Closed
36 Passenger Not Accessible in System (Protection)
37 Unique Reference for Passenger Invalid
38 Passenger Party Reference Invalid
39 Booking/Ticketing Class Conflict
40 Reservation Status Does Not Exist
41 Frequent Flyer Number Invalid
42 Booking/Ticketing Class Invalid
43 Passenger Type Conflicts with Seat Held
44 Too Many Passengers
45 Unable - Group Name
46 Unable to Check-in Partial Party
47 Passenger Status Conflict

Guide
Copyright © SITA Information Networking Computing 29. Appendix – ITCI EDIFACT Error and Warning
USA Inc 2010 - 2015. Confidential. All Rights Reserved. Responses
Page 196 Revision Date: 2015-Aug-31, Revision 11.0
48 PNR Record Locator Unknown in Receiving
System
49 Ticket Number Invalid
50 Pool Airline Code Invalid
51 Operating Airline Code Invalid
52 Not Authorized - Company Level
53 Not Authorized - Station Level
54 Not Authorized - Data Level
55 Passenger Regraded
56 Passenger Elsewhere than Requested
57 Seat Not Available in Requested Class
58 Seat Not Available in Requested Zone
59 Specific Seat Not Available
60 Open seating (Free seating) in Requested Class
61 Too Many Infants
62 Smoking Zone Unavailable
63 Non-smoking Zone Unavailable
64 Indifferent Zone Unavailable
65 Check Visa and/or Documentation
66 No Baggage Updates Required for this Flight
67 Gender Weight is Required
68 Item Conflict
69 Item Weight Is Required
70 Modification Not Possible
71 No Common Itinerary
72 Unable to Give Seat
73 Passenger Needs Initial

USA Inc.
Page 197
74 Passenger Needs First Name
75 Collect Second Flight Coupon
76 Check Smallpox Vaccination
77 Check Yellow Fever Vaccination
78 Check Cholera Vaccination
79 Passenger Has Pre-reserved Seat
80 Flight Initialized - Retry Check-in
81 Bag Through-Labeling Not Allowed Beyond This

Station
82 Too Many Bags
83 Flight Operated As
84 Function Not Supported
85 Invalid Reservation Booking Modifier RES
86 Invalid Compartment Designator Code RES
87 Invalid Country Code RES
88 Invalid Source of Business RES
89 Invalid Agents Code RES
90 Requester Identification Required RES
91 Seat Map Display Request Is Outside System RES

Data Range
92 Flight Not Operating Due to Weather, Mechanical RES

or Other Operational Conditions
93 Flight Not Operating on Date Requested RES
94 Flight Not Operating Between Requested Cities RES
95 Schedule Change in Progress RES
96 Repeat Request Updating in Progress RES
97 Flight Has Departed RES
98 Res Seating Closed Due Flight Under Departure RES

Control

Guide
99 Seat Map Not Available for Requested Zone, Seat RES
May be Requested
100 Seat Map Not Available, Request Seat at Check- RES

in
101 Seat Map Contains Conditional Seats, May be RES

Subject to Re-seat
102 Unable to Process RES
185 Use Airline Name DCS
186 Use Passenger Status DCS
187 Flight Changes from Smoking to Non-smoking DCS
188 Flight Changes from Non-smoking to Smoking DCS
189 Passenger has Pre-reserved Exit Seat - Unable DCS

To C/I
190 Passengers cannot be Seated Together DCS
191 Generic Seat Change not Supported DCS
192 Seat Change/Request in Row Range not DCS

Supported
193 API PAX Data Required DCS
194 Passenger Surname not Checked-In DCS
195 Change of Equipment on this Flight DCS
196 Time Out Occurred on Host Three DCS
197 Error in Frequent Flyer Number DCS
198 Class Code Required DCS
199 Check-in Separately DCS
200 FQTV Number not Accepted DCS
201 FQTV Number Already Present DCS
202 Baggage Details not Updated DCS
203 SSR Details not Updated DCS
204 Row Invalid DCS

USA Inc.
Page 199
205 Short Connection Baggage DCS
206 Seat Change Only Supported for Single DCS

Passenger
207 Use Generic Seating Only DCS
208 Update Separately DCS
209 Flight Changes from Seating to Open Seating DCS

(Free Seating)
210 Flight Changes from Open Seating (Free Seating) DCS

to Seating
211 Unable to Through Check - DCS

Complexing/COG/Codeshare Flight
212 API PAX Data Not Supported DCS
213 Time Invalid - Max/Min Connecting Time For DCS

Through Check-in
214 API Date Of Birth Required DCS
215 API Passport Number Required DCS
217 API PAX First Name Required DCS
218 API PAX Gender Required DCS
223 API Infant Data Required DCS
224 Passenger Holds Advanced Boarding Pass DCS
225 Seat Map not Available As Flight Operated by RES

Another Carrier
226 Seat Request not Available As Flight Operated by RES

Another Carrier
227 Seat Change not Possible/Seats Limited in this DCS

Area
228 Exchange Advanced Boarding Pass - New Data DCS
229 Change not Performed on Subsequent Flight DCS
230 Unable to Seat Change - DCS

Complexing/COG/Codeshare Flight
231 Passenger not E.T. Type DCS

Guide
232 Passenger Is E.T. Type - Needs E.T. Indicator DCS
233 Passenger Is E.T. Type - Needs E.T. Number DCS
234 Unable to Through Check - E.T. Passenger DCS
235 Tier Level not Accepted DCS
236 Unable to Process - Code share Flight DCS
237 Forward Seat Due to Connection - No Seat DCS

Change Allowed
238 Australian Visa Required - Use TIETAC Entry DCS

Each Pax
239 Advice of Hand-Carry Baggage Allowance DCS
240 Emergency Contact Information Required for US DCS

Citizens
241 API Nationality Required DCS
242 Offload Separately DCS
243 Unable to Through Check – Additional Charges DCS

May Apply
244 Epass Passenger – Number Differs DCS
245 Epass Passenger – Not Authorized DCS
246 Epass Passenger – Possible Status Discrepancy DCS
247 Message Limit Exceeded DCS
248 Insufficient Upgrade Balance DCS
249 Re-issue Bag Tags to Correct Destination DCS
250 Add API Data - Re-try Check-in DCS
251 Advise Visa and/or Documentation Status DCS
252 Passenger is E.T. Type - Ticket/Reservation DCS

Conflict
253 Passenger is E.T. Type - Ticket Record Not DCS

Accessible
254 Cascaded Query Timed Out DCS
255 Unable to check –in -Security profile restriction DCS

USA Inc.
Page 201
256 Passport number printed on boarding pass DCS
required
257 API Data is present DCS
258 API indicator on boarding pass required DCS
259 Passport / ID document data required DCS
260 Visa or similar document data required DCS
261 Home address required DCS
262 Destination address required DCS
263 Departure address required DCS
264 API PAX data not required DCS
265 Missing or invalid airport check-in identification DCS

(FOID)
266 Not head of pool, bag details not updated DCS
267 Infant name required DCS
268 'E.T. Control Requested – Retry Check-in' DCS
269 Passenger is E.T. type – no unique name found DCS
270 Passenger is E.T. type – number invalid DCS
271 Passenger is E.T. type – not authorized DCS
272 Passenger is E.T. type – invalid cpn status DCS
273 Passenger is E.T. type – duplicate number DCS
274 Passenger is E.T. type – not found DCS
275 Passenger is E.T. type – status change denied DCS
276 API Data Incomplete – Data Not Saved DCS
277 API Document Type Required DCS
278 API Document issuing Country Required DCS
279 API Pax Full Name Required DCS
280 API Document Expiry Date Required DCS

Guide
281 Document Check Required – Passenger Transits DCS
XXX
282 Infant Conflict DCS DCS

USA Inc.
Page 203
Guide
30. Glossary
A
ADL
PNL addition/deletion list
AEC
Automatic Equipment Change
API
Advanced Passenger Information
ASA
Automatic Standby Acceptance
B
BN
Boarding Number
BRC
Bulk Recheck Accepted passengers
BRN
Bulk Recheck Not Checked-In Passengers
BTM
Baggage Transfer Message
C
CBP
U.S. Customs and Border Protection
CKI
Check-in

30. Glossary
USA Inc.
Page 205
CND
Configuration Table Number Display
COM
Close Out (final) Message (Dispatched to all stations)
CRT
Cathode Ray Tube, this is the display
CSD
Created Schedule Data
CSM
Created Schedule Modification
D
DFL
Delete Flight
DOW
Dry Operating Weight
DPID
Entry for Printer/Check-in Zone Information
DRC
Destination Remarks Creation
E
EDIFACT
Electronic Data Interchange for Administration, Commerce and Transport
ESTA
Electronic System of Travel Authorization
ETL
Electronic Ticket List
ETM
EDIFACT Transfer Message (ITCI partner listed from departure city LH only).
F
FDC

Guide
Copyright © SITA Information Networking Computing 30. Glossary
Page 206
Flight Schedule
FDD
Flight Data Display
FIR
Flight Irregular Operations
FTL
Frequent Traveler List
FUI
Flight Update Information
G
GMT
Greenwich Mean Time
I
IDM
Industry Discount Message (Dispatched to next downline station on Multi-sector flights).
IFM
Interline (EDIFACT flights) Fallback Message
L
LDP
Load Planning
M
MD
Manifest Display
N
NAM SS
Name Check-In with Seat Selection
NPRO

30. Glossary
USA Inc.
Page 207
Releases all records, except the PNL / ADL records for the flight, and clears the Manifest
Index so a PNL will no longer show processed.
P
PAD
Passenger Available for Disembarkation
PCI
Passenger Statistics
PCTC
Passenger Contact
PDQ
Physical Device Queuing
PFS
Passenger Final Sales message (Originating station only).
PID
Physical device identifier. Numeric address of a peripheral device that is also known as
position identifier or port identifier.
PIL
Passenger Information List (Originating station only).

Guide
Page 208
PIM
Passenger Information Message
PN
Page Next
PNL
Passenger Name List
PRL
Passenger Reconciliation List
Protected Workstation
Protected 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).
S
SB
Standby Number
SLS
Statistical Load Summary
SOM
Seats Occupied Message (Dispatched to next downline station).
SSR
Special Service Request
STD
Scheduled Time of Departure
SUD
Special Usage Description
U
Unprotected Workstation
Unprotected workstations do not require a personal account number and check letter during
sign-in.

30. Glossary
USA Inc.
Page 209
UTC
Coordinated Universal Time (same as GMT).
Style Symbols
Example Indicator
Start of Entry Indicator

Guide
Page 210
31. Index D
DCS Office / Message Queues 29
A Dead Head Crew (XXXDHC) 171
Advance Passenger Information 161 Delete Flight Transaction (DFL) 24
Advance Passenger Information System 161 Error Responses 27
Warning Messages 26
AEC Check List with MP On (Free Seating) 143
Deleting PNL from Manifest Display (DFL) 20
AEC Check List with MP on Multi-Sector
Flight 142 Destination Remarks Creation (DRC) 42
AEC Passenger Offload (JAC) 138 Display Office Queues (QT) 29
Agent Cash Drawer / Close (JAD) 87
E
Allot Seats (AL) 71
EDIFACT Flights / Interline Thru Check-In 156
Appendix – ITCI EDIFACT Error and Warning
Responses 195 Edits of DOCS Elements 8
Assign AEC Passengers New Seats (SEA) 140 Electronic System of Travel Authorization
(ESTA) 157
Assign Check-In Supervisor (AK) 39
ETM (EDIFACT Transfer Message) 155
Assign Printer for Flight Control Messages
(EF) 39 Extra Crew (XXXCREW) XXX 171
Automatic Equipment Change (AEC) 137
F
Automatic Standby Acceptance (GS/ID) 78
FJ Check-In Codes 192
B Flight / Destination Remarks 41
Bilateral Agreements 149 Flight Check-In Agent List (JFL) 131
Block Seats (BS) 70 Flight Close-Out Procedures 81
Bulk Recheck Accepted Passengers (BRC) 145 Flight Close and Release to LDP (CCL) 82
Bulk Recheck not Checked-In Passengers Flight Control Limits 63
(BRN) 147 Flight Controls Using Survey Data Display 39
Bulk Recheck Passengers to a New Flight 145 Flight Data Display (FDD) 43
Bulk Recheck Standby Passengers (BR) 146 Flight Equipment Type Change 137
Flight History Journal 189
C Flight Information Displays and Updates 43
Check Documentation for Transit Stop Flights152 Flight Initialization 23
Check In Override 180 Flight Initialization Transaction (IF) 23
Check List for Aircraft Type and Version Flight Irregular Operations (FIR) 47
Change 142 Flight Journal Help Screen (FJ/H) 189
Checked-In Passenger Baggage Display (JB) 91 Flight Release and PAX Message Dispatch
CSD 10 (CCF) 83
CSD Transaction 3 Flight Remarks Creation (RKC) 41
CSD Update to Support APIS DOCS Flight Schedules/DFL (NPRO) 150
Information 11 Flight Update Information (FUI) 45
CSD Update to Support NOT Requiring APIS
DOCS Information 10 G
CSM/CSU Transaction 4 General Information 1
CSM/CSU/IFM 150 Glossary 205

31. Index
USA Inc.
Page 211
GOSHOW Limits (GS) 63 Passenger Excess Baggage Waiver 85
Ground Handlers Electronic 174 Passenger Excess Baggage Waiver (JEM) 85
Passenger Manifest Display (MD) 15
I Passenger Manifest Display / PNL Creation 15
Inbound Outbound Passenger Display 53 Passenger Name List (Manifest) Statistics -
Inbound Outbound Passengers 53 PM 21
Initial Flight Close (CI) 81 Passenger Notification 79
Interline Through Check-In (ITCI) 149 Passenger Notification (NO) 79
Introduction 1 Passenger Standby Acceptance 77
Passenger Statistics (PCI) 183
J PNL Request from SITA Reservations (PM) 16
JAD Input 87 Pre-Seat Passenger on Onward Flight 178
JAD Output 88 Protective Cover 57
Jump Seat Passengers 171 Protective Cover (PO) 57
Purpose 149
L
Location Travel Time 177 Q
Queue Clear Functions 35
M
Queue Handling Procedures 31
Manual Generation of Departure Messages
(LR) 91 R
Manual Offload Passenger to Standby (AC Re-Seat Passenger On Onward Flight 178
-) 78
Reassign AEC Passengers Original Seats
Manual PNL/ADL Creation 17 (REA) 139
Manual Selective Standby Acceptance (AC) 77 Releasing Reserved Seats (RA) 74
Manual System Standby Acceptance (GS/ID) 77 Reserve Group Seats (RS) 69
Miscellaneous Check-In Operations 177 Reserve Seats for Individual Passengers
Movable Partition (MP) 133 (CRS) 69
Movable Partition Flights 133 Reserving / Blocking Seats 69
Restrictions 149
N
Numeric Limits (HL) 66 S
Schedule Flight Data Display 3
O
Seat Map Characteristic Changes 59
Objectives 1 Seat Map Characteristic Changes (SCC) 59
Office Queue Error Responses 35 Sorted Passenger Manifest Generation (JL) 127
Office Queue Hardcopy (QH) 35 Space Protection Limits (SX) 68
Office Queue Repeat (QR) 34 Special Passenger Handling Procedures 169
Stretcher Passengers 172
P
PAD Limits (ID) 65 T
Passenger / Baggage Message Displays 91 The Agent Cash Drawer 87
Passenger Checked-In Statistics 183 Transit Flights 169

Guide
Copyright © SITA Information Networking Computing 31. Index
Page 212
Transit Seats (BX) 73
Turn Around Flights (Round Robin) 179
U
Unclosed Flights Archived to History (CCH) 83
Unknown Flights for Advanced Passenger
Processing (APP) 12
W
Web Server Page Entries 123

31. Index
USA Inc.
Page 213
Guide
Copyright © SITA Information Networking Computing 31. Index
Page 214

SITA Departure Control Services Check-In Supervisor Guide: Revision 11.0 Revision Date: 2015-Aug-31

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SITA Departure Control Services Check-In Supervisor Guide: Revision 11.0 Revision Date: 2015-Aug-31

Uploaded by

Copyright:

Available Formats

SITA Departure Control Services

Check-in Supervisor Guide

Revision Date: 2015-Aug-31

7.1.2 26 Mar 2008 01 Apr Replaced ETL section.

7.1.3 15 Apr 2008 Reformatted sections/page breaks.

7.2 27 Mar 2008 Footer correction.

7.3 30 Apr 2008 Customer release.

7.3.1 16 Jun 2008 Section 19.4 – Update to passenger manifest generation

7.4 29 Aug 2008 Customer release.

8.0 30 Apr 2009 Finalized changes to Section 16.3 for publication.

8.1 31 Dec 2009 Customer release.

SITA Departure Control Services Check-in Supervisor Guide

9.1 29 Feb 2012 Customer release.

10.0 31 Dec 2013 Added “Accepted” response to FUI input

SITA Departure Control Services Check-in Supervisor Guide

SITA Departure Control Services Check-in Supervisor Guide

SITA Departure Control Services Check-in Supervisor

SITA Departure Control Services Check-in Supervisor Guide

SITA Departure Control Services Check-in Supervisor

SITA Departure Control Services Check-in Supervisor Guide

Other display examples:

CSD:FLIGHT/START DATE / END DATE / CSD:XS100/15APR/04OCT/X35

CSD:FLIGHT/START DATE / OPEN CSD:XS100/15APR98/OPEN

SITA Departure Control Services Check-in Supervisor Guide

Flight Data Modification and Update (CSM / CSU)

SITA Departure Control Services Check-in Supervisor

SITA Departure Control Services Check-in Supervisor Guide

SITA Departure Control Services Check-in Supervisor

SITA Departure Control Services Check-in Supervisor Guide

XAP NO APIS DATA REQUIRED

Edits of DOCS Elements

SITA Departure Control Services Check-in Supervisor

Passenger Record with incomplete DOCS

Check-in and response to inhibit Boarding Card

SITA Departure Control Services Check-in Supervisor Guide

CSD Update to Support NOT Requiring APIS DOCS

SEGMENT DATA CDGBOM/XAP

The entry to remove XAP:

SITA Departure Control Services Check-in Supervisor

DATE Invalid date entered.

ERR-MANUAL Check-in application not specified in BF:T.

FLT CANCELLED Specified flight is cancelled.

FLT INIT Flight initialized so field cannot be updated.

FLT NBR Flight number format entry is incorrect.

FORMAT Invalid format entry.

GO-SHOW Invalid entry or exceeds compartment capacity.

SEAT SELECTION Invalid option entered or SS follows a NS segment.

SEGMENT Invalid segment entry or NLD/NLT entered together.

SKED-CHANGE Schedule change (BF:T) is in progress and must be cleared before

SITA Departure Control Services Check-in Supervisor Guide

A Required option (A = Add).

XS888 Flight to add.

01JUN06 Effective date.

30OCT06 Discontinue date.

13567 Frequency of the flight:

LAX Originating station. Intermediate ports are allowed for a flight.

1235 Local departure time from the originating station.

1047 Local arrival time at the next port.

SYD First arrival port.

1115 Local departure time from this airport.

1305 Local arrival time at the next port.

SITA Departure Control Services Check-in Supervisor

SITA Departure Control Services Check-in Supervisor Guide