UG WBS PNR AddMultiElements 12.2 194

Web Services User's Guide
PNR_AddMultiElements 12.2
Amadeus SAS
485, Route du Pin Montard
BP 69
06902 Sophia-Antipolis Cedex
Table of Contents
Table of Contents
Preface ............................................................................................................................................................ 9
1 Purpose of this document ..................................................................................................................... 9
2 Intended Audience ................................................................................................................................... 9
3 Associated Documents ........................................................................................................................... 9
4 Structure of this document ................................................................................................................... 9
Function: PNR_AddMultiElements ............................................................................................................ 11
1 Overview .....................................................................................................................................................11
1.1 Supported Operations ..................................................................................................................11
1.2 Limitations .........................................................................................................................................14
1.3 Unsupported Operations .............................................................................................................15
1.4 Prerequisites .....................................................................................................................................15
2 Building A Query .....................................................................................................................................16
2.1 Query Sub Structure: .....................................................................................................................17
2.1.1 Description ....................................................................................................................................................................... 17
2.1.2 Xml Structure................................................................................................................................................................... 17
3 Receiving A Reply...................................................................................................................................18
3.1 Reply Sub Structure: ......................................................................................................................24
3.1.1 Description ....................................................................................................................................................................... 24
3.1.2 Xml Structure................................................................................................................................................................... 24
4 Error Messages ........................................................................................................................................25
4.1 Error Reply .........................................................................................................................................35
5 Operations ................................................................................................................................................. 36
5.1 Operation: Accounting Information .........................................................................................36
5.1.1 Query Structure .............................................................................................................................................................. 36
5.1.2 Reply Structure ............................................................................................................................................................... 36
5.1.3 Possible Errors ............................................................................................................................................................... 39
5.2 Operation: ARNK Segment ........................................................................................................ 40
5.2.1 Query Structure ..............................................................................................................................................................40
5.2.2 Reply Structure ...............................................................................................................................................................40
i
Table of Contents
5.2.3 Possible Errors ...............................................................................................................................................................42

5.3 Operation: Confidential Remark .............................................................................................. 43
5.3.1 Query Structure .............................................................................................................................................................. 43
5.3.2 Reply Structure ............................................................................................................................................................... 43
5.3.3 Possible Errors .............................................................................................................................................................. 45
5.4 Operation: Connection Flight ................................................................................................... 46
5.4.1 Query Structure .............................................................................................................................................................. 46
5.4.2 Reply Structure ............................................................................................................................................................... 49
5.4.3 Possible Errors .............................................................................................................................................................. 55
5.5 Operation: Contact Information .............................................................................................. 56
5.5.1 Query Structure .............................................................................................................................................................. 56
5.5.2 Reply Structure ............................................................................................................................................................... 56
5.5.3 Possible Errors .............................................................................................................................................................. 58
5.6 Operation: Creating an OSI with Mandatory Airline Code ............................................ 59
5.6.1 Query Structure .............................................................................................................................................................. 59
5.6.2 Reply Structure ............................................................................................................................................................... 59
5.6.3 Possible Errors .............................................................................................................................................................. 61
5.7 Operation: E-mail ........................................................................................................................... 62
5.7.1 Query Structure .............................................................................................................................................................. 62
5.7.2 Reply Structure ............................................................................................................................................................... 62
5.7.3 Possible Errors .............................................................................................................................................................. 64
5.8 Operation: End Of Transaction ................................................................................................ 65
5.8.1 Query Structure .............................................................................................................................................................. 65
5.8.2 Reply Structure ............................................................................................................................................................... 65
5.8.3 Possible Errors .............................................................................................................................................................. 70
5.9 Operation: Extra Seat ................................................................................................................... 71
5.9.1 Query Structure .............................................................................................................................................................. 71
5.9.2 Reply Structure ............................................................................................................................................................... 71
5.9.3 Possible Errors .............................................................................................................................................................. 74
5.10 Operation: Fare Discount for a child ................................................................................... 75
5.10.1 Query Structure ........................................................................................................................................................... 75
5.10.2 Reply Structure............................................................................................................................................................. 75
ii
Table of Contents
5.10.3 Possible Errors .............................................................................................................................................................78

5.11 Operation: Fare Discount for a child with a birth date................................................. 79
5.11.1 Query Structure ........................................................................................................................................................... 79
5.11.2 Reply Structure............................................................................................................................................................. 79
5.11.3 Possible Errors ............................................................................................................................................................ 82
5.12 Operation: Fare Discount for senior citizen...................................................................... 83
5.12.1 Query Structure ........................................................................................................................................................... 83
5.12.2 Reply Structure............................................................................................................................................................. 83
5.12.3 Possible Errors ............................................................................................................................................................ 86
5.13 Operation: Fax Number ............................................................................................................ 87
5.13.1 Query Structure ........................................................................................................................................................... 87
5.13.2 Reply Structure............................................................................................................................................................. 87
5.13.3 Possible Errors ............................................................................................................................................................ 90
5.14 Operation: Form of Payment.................................................................................................. 91
5.14.1 Query Structure ........................................................................................................................................................... 91
5.14.2 Reply Structure............................................................................................................................................................. 91
5.14.3 Possible Errors ............................................................................................................................................................ 94
5.15 Operation: Frequent Flyer Numbers.................................................................................... 95
5.15.1 Query Structure ........................................................................................................................................................... 95
5.15.2 Reply Structure............................................................................................................................................................. 96
5.15.3 Possible Errors .......................................................................................................................................................... 101
5.16 Operation: General Remark .................................................................................................. 102
5.16.1 Query Structure ........................................................................................................................................................ 102
5.16.2 Reply Structure .......................................................................................................................................................... 102
5.16.3 Possible Errors .......................................................................................................................................................... 104
5.17 Operation: Ghost Segment ................................................................................................... 105
5.17.1 Query Structure ........................................................................................................................................................ 105
5.17.2 Reply Structure .......................................................................................................................................................... 106
5.17.3 Possible Errors .......................................................................................................................................................... 110
5.18 Operation: Group Name ........................................................................................................ 111
5.18.1 Query Structure ........................................................................................................................................................ 111
5.18.2 Reply Structure .......................................................................................................................................................... 112
iii
Table of Contents
5.18.3 Possible Errors .......................................................................................................................................................... 116

5.19 Operation: Ignore ...................................................................................................................... 117
5.19.1 Query Structure ........................................................................................................................................................ 117
5.19.2 Reply Structure .......................................................................................................................................................... 117
5.19.3 Possible Errors .......................................................................................................................................................... 118
5.20 Operation: Infant With First And Last Name And Date of Birth .............................. 119
5.20.1 Query Structure ........................................................................................................................................................ 119
5.20.2 Reply Structure .......................................................................................................................................................... 120
5.20.3 Possible Errors .......................................................................................................................................................... 123
5.21 Operation: Infant With First Name Only .......................................................................... 124
5.21.1 Query Structure ........................................................................................................................................................ 124
5.21.2 Reply Structure .......................................................................................................................................................... 124
5.21.3 Possible Errors .......................................................................................................................................................... 127
5.22 Operation: Infant With No Information ........................................................................... 128
5.22.1 Query Structure ........................................................................................................................................................ 128
5.22.2 Reply Structure .......................................................................................................................................................... 128
5.22.3 Possible Errors .......................................................................................................................................................... 131
5.23 Operation: Infant with own Native firstname ................................................................ 132
5.23.1 Query Structure ........................................................................................................................................................ 132
5.23.2 Reply Structure .......................................................................................................................................................... 133
5.23.3 Possible Errors .......................................................................................................................................................... 136
5.24 Operation: Informational Segment .................................................................................... 137
5.24.1 Query Structure ........................................................................................................................................................ 137
5.24.2 Reply Structure .......................................................................................................................................................... 138
5.24.3 Possible Errors .......................................................................................................................................................... 141
5.25 Operation: Manual Commission ......................................................................................... 142
5.25.1 Query Structure ........................................................................................................................................................ 142
5.25.2 Reply Structure .......................................................................................................................................................... 142
5.25.3 Possible Errors .......................................................................................................................................................... 144
5.26 Operation: Manual Endorsement........................................................................................ 145
5.26.1 Query Structure ........................................................................................................................................................ 145
5.26.2 Reply Structure .......................................................................................................................................................... 145
iv
Table of Contents
5.26.3 Possible Errors .......................................................................................................................................................... 147

5.27 Operation: Name With ID Code.......................................................................................... 148
5.27.1 Query Structure ........................................................................................................................................................ 148
5.27.2 Reply Structure .......................................................................................................................................................... 148
5.27.3 Possible Errors .......................................................................................................................................................... 151
5.28 Operation: Name With Passenger Type Code .............................................................. 152
5.28.1 Query Structure ........................................................................................................................................................ 152
5.28.2 Reply Structure .......................................................................................................................................................... 152
5.28.3 Possible Errors .......................................................................................................................................................... 155
5.29 Operation: Name with title separated from firstname ............................................... 156
5.29.1 Query Structure ........................................................................................................................................................ 156
5.29.2 Reply Structure .......................................................................................................................................................... 156
5.29.3 Possible Errors .......................................................................................................................................................... 159
5.30 Operation: Native name with Native Infant name ....................................................... 160
5.30.1 Query Structure ........................................................................................................................................................ 160
5.30.2 Reply Structure .......................................................................................................................................................... 161
5.30.3 Possible Errors .......................................................................................................................................................... 164
5.31 Operation: Open Segment .................................................................................................... 165
5.31.1 Query Structure ........................................................................................................................................................ 165
5.31.2 Reply Structure .......................................................................................................................................................... 166
5.31.3 Possible Errors .......................................................................................................................................................... 168
5.32 Operation: Original exchange document ........................................................................ 169
5.32.1 Query Structure ........................................................................................................................................................ 169
5.32.2 Reply Structure .......................................................................................................................................................... 169
5.32.3 Possible Errors .......................................................................................................................................................... 171
5.33 Operation: Passive Segment ................................................................................................. 172
5.33.1 Query Structure ........................................................................................................................................................ 172
5.33.2 Reply Structure .......................................................................................................................................................... 173
5.33.3 Possible Errors .......................................................................................................................................................... 177
5.34 Operation: Past Dated Segment ......................................................................................... 178
5.34.1 Query Structure ........................................................................................................................................................ 178
5.34.2 Reply Structure .......................................................................................................................................................... 179
v
Table of Contents
5.34.3 Possible Errors .......................................................................................................................................................... 182

5.35 Operation: Received From Information............................................................................ 184
5.35.1 Query Structure ........................................................................................................................................................ 184
5.35.2 Reply Structure .......................................................................................................................................................... 184
5.35.3 Possible Errors .......................................................................................................................................................... 186
5.36 Operation: Seat Request ........................................................................................................ 187
5.36.1 Query Structure ........................................................................................................................................................ 187
5.36.2 Reply Structure .......................................................................................................................................................... 187
5.36.3 Possible Errors .......................................................................................................................................................... 192
5.37 Operation: Service Fee ..................................................................................................... 193
5.37.1 Query Structure ........................................................................................................................................................ 193
5.37.2 Reply Structure .......................................................................................................................................................... 193
5.37.3 Possible Errors .......................................................................................................................................................... 193
5.38 Operation: Service segment.................................................................................................. 194
5.38.1 Query Structure ........................................................................................................................................................ 194
5.38.2 Reply Structure .......................................................................................................................................................... 195
5.38.3 Possible Errors .......................................................................................................................................................... 195
5.39 Operation: Simple Name ....................................................................................................... 196
5.39.1 Query Structure ........................................................................................................................................................ 196
5.39.2 Reply Structure .......................................................................................................................................................... 196
5.39.3 Possible Errors .......................................................................................................................................................... 199
5.40 Operation: Single Flight .......................................................................................................... 200
5.40.1 Query Structure ........................................................................................................................................................ 200
5.40.2 Reply Structure .......................................................................................................................................................... 201
5.40.3 Possible Errors .......................................................................................................................................................... 204
5.41 Operation: Special A.I.R remark........................................................................................... 205
5.41.1 Query Structure ........................................................................................................................................................ 205
5.41.2 Reply Structure .......................................................................................................................................................... 205
5.41.3 Possible Errors .......................................................................................................................................................... 207
5.42 Operation: Structured Mailing ............................................................................................. 208
5.42.1 Query Structure ........................................................................................................................................................ 208
5.42.2 Reply Structure .......................................................................................................................................................... 209
vi
Table of Contents
5.42.3 Possible Errors .......................................................................................................................................................... 213

5.43 Operation: Structured Remark ............................................................................................. 214
5.43.1 Query Structure ........................................................................................................................................................ 214
5.43.2 Reply Structure .......................................................................................................................................................... 214
5.43.3 Possible Errors .......................................................................................................................................................... 216
5.44 Operation: Structured Remark with basic security ...................................................... 217
5.44.1 Query Structure ........................................................................................................................................................ 217
5.44.2 Reply Structure .......................................................................................................................................................... 217
5.44.3 Possible Errors .......................................................................................................................................................... 220
5.45 Operation: Structured Remark with corporate security ............................................. 221
5.45.1 Query Structure ........................................................................................................................................................ 221
5.45.2 Reply Structure .......................................................................................................................................................... 221
5.45.3 Possible Errors .......................................................................................................................................................... 224
5.46 Operation: Structured Remark with specific security .................................................. 225
5.46.1 Query Structure ........................................................................................................................................................ 225
5.46.2 Reply Structure .......................................................................................................................................................... 226
5.46.3 Possible Errors .......................................................................................................................................................... 228
5.47 Operation: Structured Timestamped Remark ................................................................ 229
5.47.1 Query Structure ........................................................................................................................................................ 229
5.47.2 Reply Structure .......................................................................................................................................................... 229
5.47.3 Possible Errors .......................................................................................................................................................... 232
5.48 Operation: Ticketing Arrangement Element................................................................... 233
5.48.1 Query Structure ........................................................................................................................................................ 233
5.48.2 Reply Structure .......................................................................................................................................................... 233
5.48.3 Possible Errors .......................................................................................................................................................... 235
5.49 Operation: Tour Code in Free Flow Format.................................................................... 236
5.49.1 Query Structure ........................................................................................................................................................ 236
5.49.2 Reply Structure .......................................................................................................................................................... 236
5.49.3 Possible Errors .......................................................................................................................................................... 238
5.50 Operation: UnStructured Mailing and Billing Addresses ........................................... 239
5.50.1 Query Structure ........................................................................................................................................................ 239
5.50.2 Reply Structure .......................................................................................................................................................... 239
vii
Table of Contents
5.50.3 Possible Errors .......................................................................................................................................................... 241
5.51 Operation: Upgrade ................................................................................................................. 242

5.51.1 Query Structure ........................................................................................................................................................ 242
5.51.2 Reply Structure .......................................................................................................................................................... 242
5.51.3 Possible Errors .......................................................................................................................................................... 248
viii
Web services User guide for function PNR_AddMultiElements
Preface
1 Purpose of this document

The purpose of this document is to provide basic functional overview descriptions and relevant examples for
a better understanding of the functions.
2 Intended Audience
This document is aimed at those who implement this function.
3 Associated Documents
This document has to be combined to its corresponding Technical Reference Guide and possibly to Product
specifications.
4 Structure of this document

This document is composed of the following parts:
• the functional description: overview, supported operations, limitations, unsupported operations,
prerequisites and possibly reference to product specifications
• the detailed description to build the query and to retrieve data from the reply
• a set of relevant examples
Copyright © 1987-2013 Amadeus IT Group SA.

Page 9 of 248
PNR_AddMultiElements
This function allows the user to create elements in a new or existing PNR.

Page 10 of 248
Function: PNR_AddMultiElements.
1 Overview
The AddMultiElements function allows a user to make an entire reservation in the Amadeus system with one
transaction, bearing in mind that the full itinerary details mustbe known at the time of the function usage.This
function allows many different elements to be combined into one transaction, thus it is more efficient by reducing
the number of transactions required from the client application.
1.1 Supported Operations

The following operations are supported within this function:
Adding Names
This function may be used to add the following types of traveler names:
• Individual Names
Used for general travelers.
• Infant Name
Used for children under the age of 2 years.
• Child Name
Used for children between the ages of 2-12years.
• Group Name
Used to incorporate a group of travelers.
• Name Element for Cabin Baggage
Used to reserve extra space for excess cabin baggage.
• Name element for Extra Seat requirement
Used to reserve an extra seat in the cabin for a traveler.
Note that the Individual Traveler Name (traveler last name and first name), Adult, Infant, Child Name, can be
entered in Roman (it can then also be called a passport name) or Native characters (it will then be called a
Native name).
Special settings are needed to be able to handle Native characters.
Only Korean characters are supported as Native characters today.
If entered in UTF8 characters, the name must be entered in a dedicated section that supports UTF8 characters.
Please refer to the operations related to Native Names.
The traveler title can also be entered separately from the first name if wished. In that case, a dedicated section
must be used.
Adding Itinerary Elements

When all mandatory details of the itinerary element required for booking are known, this function may be used
to add the following types of itinerary elements:

Page 11 of 248
Air Segments
• Single flight segments
• Connection flight segments
• Open flight segments
• Arrival Unknown segments (ARNK.)
• Ghost segments
• Informational segments
• Passive segments
• Service segments
• Past dated segments
Non Automated Segments
• Air Taxi
• Non-Automated Car
• Non-Automated Hotel
• Miscellaneous Segment
• Surface Segment
• Non-Automated Tour Segment
Hotel Segments
• Automated Hotel Segment
Adding Miscellaneous Data Elements
This function may be used to add the following miscellaneous PNR data elements:
• Accounting Information
Used to send additional information to an agency back office accounting system.
• Confidential Remarks
Used to store comments in the PNR that can only be viewed by the selected agencies specified.
• Contact information
Mandatory PNR element containing contact information.
• Document Remarks
Used to customize information contained on documents such as itineraries or invoices.
• Fare Discount
Used to automatically price the travel itinerary at a discounted rate without the need to specify the fare discount
in a pricing request.
• Fare Endorsements/Restrictions
Used to identify any restrictions, rules or airline comments that may apply to a ticket.
• Fare Print Override
Used to override the fare, tax, and total information printed on a document.
• Form of Commission
Used to identify the specific amount for agency commission on the tickets issued.
• Form of Payment
Used to store the form of payment to be taken into account when issuing the ticket.
• Frequent Flyer Numbers

Page 12 of 248
Used to store applicable frequent flyer numbers for travelers.

• General Remarks
Used to store general remarks in a passenger record.
• General Special Service Requests
Used to send special service request information, such as a special meal, to applicable airlines.
• Individual PNR Security element
Used to specify special security rules regarding the retrieval of traveler PNRs.
• Manual Document Registration
Used to store ticket numbers for tickets not issued via the system.
• Miscellaneous Ticketing Information
Used to store record data for accounting purposes with association to record the ticketing image.
• Original Issue Information
Used when a new ticket is issued in exchange for a coupon, a voucher or another airline ticket.
• Other Special Information
Used to send other special information, such as child indicators, to applicable airlines.
• Queuing Option Information
Used to place a newly created or retrieved PNR to on a specified queue within a specified office ID for a
specified date.
• Received From Information
Mandatory PNR element containing information identifying the agent responsible for creating or modifying the
reservation.
• Shadow Destination
Used to define different destination offices for the accounting interface records from a back office accounting
system.
• Structured and Unstructured Billing Address
Used to store traveler billing address information.
• Structured and Unstructured Mailing Address
Used to store traveler mailing address information.
• Special Keywords (SK)
Used to contain special information about a booking or passenger that can be used by an airline for service
or marketing purposes.
• Ticketing Information
Mandatory PNR Element identifying information regarding the issuance of the ticket, such as a ticketing time
limit, or date for ticket issuance.
• Tour Code
Used to store a tour code when a published tour or special negotiated fare is sold in conjunction with a ticket.
Adding Seat Elements
This function may be used to add the following types of seat elements: PNRdata elements:
• Non Smoking Seat

Page 13 of 248
• Smoking Seat
• Non Smoking Aisle Seat
• Smoking Aisle Seat
• Non Smoking Window Seat
• Smoking Window Seat
• Non Smoking Rear facing Seat
• Smoking Rear facing Seat
• Non Smoking Bulkhead Seat
• Smoking Bulkhead Seat
• Specific Seat Number
End transact
This function may be used to end transact and then to store the newly created PNR in the database (or
modificatiosn in case of a retrieved PNR) with the followings option codes:
Option Code Description

10 End transact (ET)
11 End transact with retrieve (ER)
12 End transact and change advice codes (ETK)
13 End transact with retrieve and change advice codes
(ERK)
14 End transact split PNR (EF)
Those actions may may be combined with the following codes:
Option code Description

30 Show warnings at first EOT
267 Stop EOT if segment sell error
Ignore
This function may be used to ignore an entry with the following codes:
Option code Description

20 Ignore (IG)
21 Ignore with retrieve (IR)
1.2 Limitations
Stand-alone entry (Special Service Request)
Once an SSR (Special Service Request) OTHS ZZ is entered in a PNR it can no longer be updated: an error
message is displayed by the system at the entry input time.In addition it is also not possible to add SSR OTHS
ZZ in a already modified PNR.
Error message:
RESTRICTED: COMBINATION NOT ALLOW WITH SSR OTHS ZZ

Page 14 of 248
Other Service Information (OSI)

If no company ID is provided, an element without company ID is temporarily created and then removed at EOT
time because no airline code of the segments in the itinerary obviously matches the two blank characters.
Record locator length
Record locator is mandatory when user wants to create Ghost segments, Passive segment and Service
segment in this cases : the length of OA record locator have to be from one to seven alpha numeric characters
( from a to z and from 0 to 9).
1.3 Unsupported Operations

The following operations are currently unsupported within this function:
• Airline Staff Names
• Corporate Names
• Multiple Names (Native Name and passport name in Roman characters) for a same passenger
• Extended Form of Payment Information
• Update an already existent FP element
• Add Special FP elements: INS/CAR/HTL
• MCO
• Total Payment Options
• Air Sequence number elements
• Shadow A.I.R. sequence numbers
• Automated Invoice Numbers
• Transmission Control Numbers
• Hotel Segment Reservations
Note: the structures for such operations may already be in place within the message in anticipation of the
functionality, but currently will not function until the Amadeus System Enhancements are completed.
1.4 Prerequisites
Air, Hotel, Non-Automated Auxiliary segments
All mandatory element information must be known for segment reservations prior to using this function. Selling
from previous availability responses is not allowed with this function, as it is not cross-referenced with any
availability processes.
Amadeus system element limitations
This function will forward all requests to the Amadeus system regardless of the content. As this function
allows for numerous operations to be combined the security and limitations of each Amadeus system element
requested within this operation is verified at the time of processing in the Amadeus system. Therefore, functional
errors may be returned to the user at processing time on the Amadeus system however the correct elements
will be created.

Page 15 of 248
2 Building A Query
The queries for the operations are clearly explained with data element examples the Technical Reference
Guide.
It is important to note that the examples given are only illustrations and are meant to provide the basis for a
better understanding on which fields are mandatory for basic operation utilization. It is not a full explanation of
every field that can be utilized for the operation, but rather a guideline to its use.
Note: The Fare Discount element cannot process multiple discounts. If you wish to enter multiple discounts for
a passenger, you should enter several FD elements and associate them to the same passenger.
Note related to Names:
Two structures exist to carry names, one supporting only Roman characters, one supporting possibly
some native and Roman characters.
As an illustration, the individual passenger names can be carried in:
• passengerData section: if the passenger name (last name and firstname) is a passport name (Roman name)
OR
• enhancedPassengerData section: if the individual passenger name (last name and firstname) has a Native
name(and possibly also a passport name) or a passport name (Roman name)(it includes for example case
with a title separated from the firstname in the query).
Remark: addition of multiple names (Native Name and possibly also a passport name) for a same passenger
functionality is not supported today.
Note related to the Contact element:
For type P02 (email), it is possible to restrict its access by entering an office (or range of offices) with a possible
access mode, at the begining of the freetext (separate the offices and the freetext by a /).
For type 5:N (APN), the field containing the freeflow text of the element shall be filled the following:
{XX/}{YYYYYYYYY}{-W}/{X}\+{XXXXXXXX...}{/LG}{/F}
• XX is the airline association:
• (Mandatory) If logged in an ATO/CTO: mandatory association to the ATO/CTO's airline
• (Forbidden) Otherwise: forbidden
• YYYYYYYYY (Optional) is a set of office IDs. If not entered the system defaults to let the APN element
visible and modifiable by any office. Up to a maximum of three (3) office identifications in addition to the creator
office can be entered in each element. Each office ID will be separated by a comma. A valid office ID can
be a complete office ID or a partial office id (e.g. HEL6X0100, ***6X0***, LIS2X0***, ***2X0100). These Ids
have read access to the element. (1)
• W (Optional) is the identification code that indicates if the office ID or the range is able to update/cancel the
element. If the code is not present, the office identification(s) indicated will be able to see but will not have
the ability to update/cancel the element.
• X (Mandatory) is the mandatory code identifier to specify the mean of contact. The supported media are
M (Mobile phone), E (Email). Whenever a media type is chosen, the system will expect a specific address
structure for this media in the following input. Note only one media type can be selected per APN.
• XXXXXXXX... (Mandatory) is the media address to contact the person with. Its type and structure depends
on the media type, selected in the previous input. For the phone number, the process checks at entry time that
the phone number does not start by +00. For the email, it checks that the ‘@’ is present. The email address
should only contain alphanumeric characters and some special symbols (‘.’, ’-’, ’_’).

Page 16 of 248
• LG (Optional) is the preferred language identification code. It refers to the list of ISO language codes.
• F (Optional) is the third-party indicator. In certain use cases, the Agent may have to specify a third-party
contact element that should get notification linked to the passenger’s journey (e.g.: a friend picking him at the
arrival airport).
2.1 Query Sub Structure:
2.1.1 Description
2.1.2 Xml Structure

Page 17 of 248
3 Receiving A Reply
For each query sent, the Reply message structure will be returned with the appropriate PNR information
requested or applicable errors.
Please refer to the Technical Reference Guide for detailed message information.
As each query receives only the Reply message structure, any errors that are returned to the query will be
found in the appropriate section of the Reply .
Reply Structure
Names Elements
When creating a name item within this function the following information should be noted:
• There is no special processing required for adding a name element. Therefore, the mandatory option code
is set to 0.
• The type of element being added is a passenger reference and therefore the /
elementManagementPassenger /reference /qualifier is set to PR.
• Reference numbers of passengers added begin with 1 and should be numbered sequentially when adding.
• The type of passenger reference element being requested is defined as one of the following: NM=Name
or NG=Group Name.
• When requesting a name, a surname and a first name are mandatory elements within the structure.
Passenger type codes, ID codes, etc are optional parameters.
Note that both passengerData and enhancedPassengerData will be filled, except in some error cases.
For individual passengers:
• passengerData contains Romanization in pure Roman characters or Passport name, depending on the
name "active"/"reference" for the passenger in the PNR.
• enhancedPassengerData contains the Native name, Romanized name (romanization) (and possibly also
a passport name) or a passport name. These names are labelled by a nameType. The information related
to the name that is the "active"/reference name in the PNR is provided in referenceName. The information
related to the name(s) that would be displayed in a PNR cryptic display, depending on settings to support
Native name, is provided in displayedName. For Romanized name, the Romanization method is also provided
in romanizationMethod.
Remark: addition of multiple names (Native Name and possibly also a passport name) for a same passenger
functionality is not supported today.
General
A passenger name is mandatory for the creation of a passenger name record (PNR). A minimum of 1 passenger
name must be entered prior to storing the record.
A maximum of 99 names may be added in the passenger name record.
A title for the passenger is not mandatory.
The maximum length of the whole name and name attributes is 59 characters, however this does not mean
that 59 characters can be input into the XML structure as additional attributes may be added.
Passenger Type Codes
A passenger type code is not mandatory. If a passenger type code is not included, the system considers the
passenger is an adult.
A maximum of one passenger type code may be specified, except under some conditions.
Group Names

Page 18 of 248
A maximum of one group name may exist in the passenger name record. A group name may contain a maximum
of 99 individual passengers
Itinerary Elements
Using the Function Message Structure
The following should be noted when using the AddMultiElements function for reserving an itinerary element:
• All of the itinerary details must be known at the time of the segment request. Reserving from an availability
is not allowed with this function.
• There is no special processing required for adding an itinerary element. Therefore, the mandatory option
code is set to 0.
• The type of element being added is a segment reference and therefore the /elementManagementItinerary /
reference /qualifier is set to SR.
• The air auxiliary status code of the request is normally NN for a reservation request.
• The business function is always 1 for airline request.
• The originDestinationDetails element is used to group connecting flights and or married segments.
• When selling an outbound and inbound journey, you must use two different originDestinationDetails
elements (For example: 1 for the outboundflight and 1 for the inbound flight).
AIR / Flight Reservations
The type of element being added is an AIR segment and therefore the elementManagementItinerary Segment
Name is set to AIR.
General
A maximum of 99 itinerary element reservations may be requested. The reservation requests are manual
requests and therefore are processed via the standard Amadeus system processing. i.e., direct access
bookings are not possible.
Miscellaneous Date Elements

Using the Function Message Structure
The following should be noted when using the AddMultiElements function for reserving a miscellaneous data
element:
• There is no special processing required for adding a miscellaneous element. Therefore, the mandatory
option code is set to 0.
• The type of element being added is classified as "other type" and therefore the /
elementManagementItinerary /reference /qualifier is set to OT.
• As the operational information is generally free form text, in most instances a special detail qualifier is
required to identify the type of free form text being entered. Such information can be found under the applicable
section.
Accounting Information
The accounting information is identified with a segment name of AI. Each optional element for the accounting
information is of free flow text.
Accounting information may be stored in the Amadeus Record. This information will be transmitted to the
applicable back office accounting system. The accounting information may contain the following optional
elements:
• Account Number
• Cost Center Number
• Company ID Number
• Client Reference Number

Page 19 of 248
The accounting elements may be passenger and segment associated. A maximum of 1 accounting information
element may be requested for per passenger per segment.
Contact Information
A PNR must contain at least one contact element prior to storage. A maximum of 127 contact elements may be
requested. Each contact element is of free form text and therefore the content is not verified by the Amadeus
System.
The contact information is identified with a segment name of AP and consists of freeflow text. Each type of
contact is qualified with a free form text detail type number in the message structure in conjunction with a free
form indicator following the actual contact number. The common indicators for different contact numbers that
are entered at the end of the contact number and their applicable detail types are as follows:
Type of contact Description Free Form Text Detail Type in
output
Basic contact element Blank blank
Passenger Business Number B 3
Passenger Home Number H 4
Unknown Type Blank 5
Agency Contact Number AGCY 6
Mobile Phone Number Mobile 7
Fax Number FAX P01
E-mail Contact Email P02
Internet Contact URL P03
Force Sent S 5:S
Inhibit Sent X 5:X
Notification Contact Notification 5:N
Fare Discount Element
The fare discount information stored in a passenger record is verified and applied at the time of a pricing
request. Up to 3-fare discount codes per passenger may be stored in the Amadeus system record.
Note: The Fare Discount element cannot process multiple discounts. If you wish to enter multiple discounts for
a passenger, you should enter several FD elements and associate them to the same passenger.
The fare discount information is identified with a segment name of FD and consists of a type of discount
identifying code and any additional information the applicable discount requires.
The following standard fare discounts are applicable in the Amadeus system:
Type of Discount Code Requirements:
Agent AD --
Senior Citizen CD Percentage Discount
Tour Conductor CG Percentage Discount
Child CH Date of Birth/Age in Yrs
Clergy CL Percentage Discount

Page 20 of 248
Adult with Companion CN --

Companion CP Percentage Discount
Seriously Disabled Psgr DB --
Government Officials DG Percentage Discount
Labor DL --
Teacher DT Percentage Discount
Emigrant EM Percentage Discount
Group GC Percentage Discount
School Group GP --
Group - Inclusive Tour GV --
Air Industry Employee ID Percentage Discount/Status Code
Infant IN Date of Birth/Age in Yrs
Individual Inclusive Tour IT --
Military MM Percentage Discount
Family PD --
Family - Head of family PH --
General Sales Agent RG Percentage Discount
Regular Passenter RP Percentage Discount
Seaman SC Percentage Discount or Country
Code
Student SD Date of Birth/Age in Yrs
Special Event SE --
Spouse SH --
Spouse - Accompany ST Percentage Discount
Standby UU --
Youth - Student Certificate ZS Date of Birth/Age in Yrs
Required
Youth ZZ Date of Birth/Age in Yrs
Note: Certain fare discounts require specific parameters to be included in the request for proper processing,
such as; age, birth date, certificate numbers, etc.
The Fare Discount element cannot process multiple discounts. If you wish to enter multiple discounts for a
passenger, you should enter several FD elements and associate them to the same passenger.
Frequent Flyer Information
The frequent flyer information is transmitted to the applicable airlines at the time the record is stored. As this
information is a unique identifier for an individual passenger, it must be passenger associated in the case of
a multiple passenger record.

Page 21 of 248
The frequent flyer information is deemed as a type of special services request, and therefore will utilize the
special services request (/dataElementsMaster /dataElementsIndiv /serviceRequest (SSR)) structure in this
function. The segment name will be requested as an SSR will be have an associated type of FQTV, indicating
frequent traveler information.
Being that this is stored as an SSR item, the applicable airline information for the surrounding SSR structure will
need to be propagated in the structure to indicate which airlines should receive the transmitted frequent traveler
information. Failure to complete the SSR required structure information would result in an error message for
the request.
Note:Some airlines may reject these manual SSR FQTV. These elements are not validated against Amadeus
Frequent Flyer database
General Remark Information
In addition, the RM and RI remark types may contain an additional sub category indicator for system sorting.
i.e., all sub categories of similar type will be grouped together. The Category indicator is not applicable for RC
and RQ remark Types.
Following types of remarks may be requested:
Remark Type Code

Miscellaneous Remark RM
Confidential Remark RC
Invoice Remark RI
Quality Control Remark RQ
Mailing & Billing Address Information

The mailing and billing address information is optional information used for the itinerary and invoice documents.
Two forms of the mailing and billing address information exist:
Type Definition Segment Name Code

Structured Billing---- AB
Structured Mailing---- AM
UnStructured Billing---- ABU
UnStructured Mailing---- ABU
----The billing and mailing address information is structured in a specific manner to identify each element of the
address. This format is typically used in conjunction with a back office accounting system.A structured mailing
or billing address must contain at least 1 address line. Therefore, the A1 option is mandatory in this function.
Each element of the structured mailing or billing address is identified with a specific code.
The following coded structured address elements may be stored in the passenger record:
Code Option Max Number of characters

CY COMPANY NAME 30
NA NAME 30

Page 22 of 248
A1 ADDRESS LINE 1 50
A2 ADDRESS LINE 2 50
PO POST OFFICE BOX 8
ZP POSTAL/ZIP CODE 20
CI CITY 30
ST STATE 25
CO COUNTRY 25
When creating a structured mailing or billing address, the type of address being entered is mandatory. The
following types are applicable for structured addresses:
Type of Address Type Code

Billing Address 2
General Mailing Address P08
Miscellaneous Address P19
Home Mailing Address P24
Delivery Mailing Address P25
---The billing and address information for unstructured format is of free form text. A maximum of 126 characters
may be stored. The information is printed on Amadeus generated itinerary and invoice documentation inline
formats. The start of each new line of information may be indicated by a comma (,) in the freeform text
information for printing purposes.
The maximum number of character per line on an Amadeus generated document is 27. Therefore, a maximum
of 27 characters should be adhered to between commas to avoid any truncation by the Amadeus system when
generating documentation.
The following illustrates a free form text with new line indicators for printing purposes:
Free Form Text Entered Printed Format on Amadeus Generated Documents

Mr. John Smith, 124 south Hampton, Atlanta GA Mr. John Smith
30039
124 south Hampton
Atlanta GA 30039
Received From Information
The received from information is a mandatory element for a passenger name record. This element is of free
form text and is used to identify who has created or updated the passenger name record or who has given the
instruction / authorization for the creation or update to the passenger name record. A maximum of one received
from information element may exist in the record.
Ticketing Information
The ticketing information is a mandatory element prior to record storage. This information details the ticketing
arrangements with the date of when the ticket will be issued. A maximum of one ticketing information element
may exist in the record.

Page 23 of 248
The ticketing information elements are identified with the segment name of TK with an associated sub type
of ticketing information.
A Ticketing Arrangement element may be passenger associated (except TKXL) at any time during the creation
or modification of the PNR.Segment association is only allowed if a TST (Transitional Stored Ticket) has been
created for that segment. Maximum number of Ticket Arrangement Elements per PNR is 127.
The following types of ticketing information elements may be requested:
Ticketing Type Code

Ticketing time limit TL
Domestic Ticket Type DO
International Ticket Type IN
Ticket issued, No Queue Placement required OK
Automatic cancel Date XL
Tickets to be Mailed MA
Tickets to be issued at the airport office AT
Revalidated Ticket TR
3.1 Reply Sub Structure:
3.1.1 Description
3.1.2 Xml Structure

Page 24 of 248
4 Error Messages
IATA error codes and messages
103 CHECK ARRIVAL/DEPARTURE DATE
102 CHECK DATE
303 FLIGHT CANCELLED
411 FLIGHT DOES NOT OPERATE ON DATE
REQUESTED
114 FLIGHT NOT FOUND
134 IMPUT TIMES
130 INVALID ORIGIN AND DESTINATION PAIR
143 INVALID PASSENGER TYPE
104 INVALID RESERVATION BOOKING DESIGNATOR
421 NOT AVAILABLE AND WAITLIST CLOSED
422 NOT AVAILABLE DUE TO TRAFFIC RESTRICTION
118 SYSTEM UNABLE TO PROCESS
118 UNABLE TO PROCESS
Amadeus canned messages
1906 ACTION IDENTIFIER INVALID
6137 A FULL CORPORATE ID MUST BE ENTERED
11647 AIRLINE CODE NOT IN ITINERARY - SK
CANCELLED AT EOT
3499 AIR SEGMENT REQUIRED WITH TICKETING

ARRANGEMENT
3527 AREA OF PREFERENCE ERROR
1942 ASSOCIATION NOT ALLOWED IN ELEMENT
6135 AT LEAST ONE RECEIVER MUST BE ENTERED
3821 CALL AIRLINE
4821 CANCEL SEAT FOR PAX AND RE-REQUEST PAX
AND ASSOCIATED EXST/CBBG
3171 CHECK AGES
1920 CHECK AIRLINE CODE
3608 CHECK BOARDING OR DISEMBARKATION POINT
116 CHECK CODE
7308 CHECK COMPANY CODE

Page 25 of 248
4759 CHECK DATE OF BIRTH

1 CHECK FORMAT
1903 CHECK PASSENGER ASSOCIATION
30000 CHECK TELEPHONE COUNTRY CODE MUST BE
PREFIXED BY +
13123 CLASS DOES NOT ALLOW GROUP BOOKINGS
11650 CODE NOT KNOWN/>
3648 CODES M AND H REQUIRE ADDITIONAL SSR
INFO
4498 COMBINATION OF ELEMENTS NOT ALLOWED
7637 COPY ADDRESS FUNCTION DISALLOWED
12069 CORPORATE FAMILY NOT DEFINED
8041 DATE OVERRIDE NOT PERMITTED
7758 DOCUMENT PRINT OPTIONS NOT ALLOWED
FOR
3081 DOWNLINE TK NOT ALLOWED WITH OTHER TK
1923 DUPLICATE OPTION ITEMS / NO ITEMS
ENTERED
06377 DUPLICATE RECEIVER :
9383 DUPLICATE RECEIVER TYPE
82 DUPLICATE SEGMENT
2011 ENTRY NOT AUTHORISED
7636 ERR CHECK TST SELECTION
2038 ERR INVALID LANGUAGE CODE
8111 ERROR AT END OF TRANSACTION TIME
1897 EXCEED MAXIMUM ELEMENTS
3689 FREEFLOW INFORMATION NOT PERMITTED
5363 GENERIC ASR INHIBITED THIS FLIGHT -
REQUEST SPECIFIC SEAT NUMBER
12495 IF A DATE WAS ENTERED: CHECK IF DATE IS

VALID
25691 INFANT AGE MAY EXCEED FOR SOME
SEGMENTS
1891 INPUT TOO LONG
817 INVALID AIRLINE CODE

Page 26 of 248
6139 INVALID ACCESS MODE. MUST BE R,T,B OR N

56 INVALID ACTION CODE
3325 INVALID ACTION CODE FOR XX (where XX is the
airline)
13114 INVALID BOOKING CLASS CODE
1007 INVALID CATEGORY ENTERED
4493 INVALID CHARACTER IN SSR>
693 INVALID CITY/AIRPORT CODE
2232 INVALID CLASS
11649 INVALID CODE ENTERED IN FREETEXT
6166 INVALID CORPORATE ID
622 INVALID CORPORATE ID NUMBER
425 INVALID DATE
7759 INVALID DOCUMENT PRINT OPTION
9379 INVALID IATA NUMBER : iata_nbr
477 INVALID FORMAT
7795 INVALID FORMAT '...' NOT ALLOWED
AT END OF FREE TEXT
7791 INVALID FORMAT IN CR FIELD
1892 INVALID FORMAT/NOT ENTERED/
1270 INVALID IATA NUMBER
2300 INVALID MEAL CODE
1194 INVALID NUMBER IN PARTY
6164 INVALID OFFICE ID
9517 INVALID OFFICE IDENTIFICATION
1533 INVALID OFFICE IDENTIFICATION CODE
7792 INVALID-ONLY ONE IDENTIFICATION CODE
ALLOWED IN NAME ELEMENT
456 INVALID OR MISSING CAR TYPE
457 INVALID OR MISSING DATE
4725 INVALID PASSENGER ASSOCIATION
0089 INVALID PASSENGER TYPE
1987 INVALID PASSENGER/SEGMENT SELECT - PNR
OVERLAP

Page 27 of 248
9381 INVALID PSEUDO OFFICE ID : id

9378 INVALID RECEIVER TYPE. MUST BE : G, I OR P
1929 INVALID RECORD LOCATOR
1919 INVALID REQUEST FOR ELEMENT
6362 INVALID SECONDARY ACTION CODE, MUST BE
ESD OR ESX : invalid_character
8110 INVALID SSR
811 INVALID STATUS CODE
3505 INVALID TICKETING ARRANGEMENT / NO PTA
PRESENT
4470 INVALID TICKETING DATE
3000 INVALID TRANSACTION - FILE NOT PERMITTED
3007 INVALID TRANSACTION - FILE REQUIRED
2999 INVALID TRANSACTION - SPLIT PNR REQUIRED
463 INVALID TEXT DATA
2298 INVALID TIME
12291 ITEM TOO LONG / NOT ENTERED /
11646 KEYWORD INACTIVE
11648 KEYWORD TABLE NOT FOUND FOR CARRIER -
followed by the invalid carrier code
15818 MANDATORY FIELD MISSING
10238 KEYWORD NAME TOO LONG
7588 MANUAL CAR SEGMENTS CANNOT BE
CREATED FOR THIS AIRLINE
7589 MANUAL HOTEL SEGMENTS CANNOT BE
7590 MANUAL TAXI SEGMENTS CANNOT BE
7587 MANUAL TOUR SEGMENTS CANNOT BE
6136 MAXIMUM ALLOWED IS 5 RECEIVERS
5443 MAXIMUM FREEFLOW EXCEEDED
11376 MAXIMUM OF 5 SUB TYPE CATEGORIES CAN BE
ENTERED

Page 28 of 248
3528 MAXIMUM OF 7 REQUESTS PERMITTED FOR

SEAT AGREEMENT AIRLINE
1922 MAXIMUM OF 8 EXCEEDED/NO ITEMS ENTERED
12196 MEAL NOT CREATED - UNCONFIRMED
RESERVATION
54 MESSAGE TOO LONG
3139 MODIFICATION RESTRICTED TO TK FLAG
11187 MULTIPLE PASSENGER ASSOCIATION NOT
POSSIBLE
1931 NO MATCH FOR RECORD LOCATOR
85 NO NAME
49 NO TRANSACTION PRESENT
315 NEED FORM OF PAYMENT
1980 NEED GROUP NAME
339 NEED NAMES
3500 NEED PASSENGER ASSOCIATION
3638 NEED PASSENGER SEGMENT ASSOCIATION
96 NEED RECEIVED FROM
3550 NEED TELEPHONE FOR PASSENGER XXXXX
where XXXXX shows the element(s) without a
passenger-associated AP
1780 NEED TEXT
385 NEED TICKETING ARRANGEMENT
1911 NEED TICKETING ARRANGEMENT FOR
PASSENGER
1912 NEED TICKETING ARRANGEMENT FOR
SEGMENT
2102 NEED TST
251 NO AIR SEGMENTS
1946 NO INFANT NAME EXISTS
7314 NO SSR ITEM EXIST TO EXPLODE
8043 NOT ALLOWED FOR TST WITH SELECTED
SEGMENTS
24192 NOT VALID FOR SEGMENT DATE
4215 NUMBER IN PARTY EXCEEDS MAXIMUM
1914 OFFICE RESTRICTED

Page 29 of 248
1899 OSI/SSR EXCEED MAXIMUM ELEMENTS

13332 OTHER SEGMENT FROM CONNECTION IN
ERROR
1949 PASSENGER AND/OR SEGMENT DATA NOT
VALID
4698 PASSENGER ASSOCIATION NOT ALLOWED
7025 QUEUE ALTERNATE RESTRICTED FOR
DOWNLINE TK
7024 QUEUE ALTERNATE RESTRICTED FOR TK
3574 QUEUE TICKETING RECORD INACTIVE
3721 REQUEST EXCEEDS 5 LEGS
3526 REQUEST TOTAL NUMBER IN PARTY
20 RESTRICTED
3394 RESTRICTED ACTION CODE
4918 RESTRICTED - ADD NAME ELEMENT FIRST
1951 RESTRICTED CHANGE
1956 RESTRICTED DURING SPLIT PARTY
12063 RESTRICTED FOP FOR PASSENGER
ASSOCIATION OF TKAT
12061 RESTRICTED FOP FOR PASSENGER

ASSOCIATION OF TKMA
3138 RESTRICTED FOR AMADEUS AIRLINE
9410 RESTRICTED NAME
3486 RESTRICTED OFFICE TK
8604 RESTRICTED-OPTION NOT ALLOWED
3560 RESTRICTED PARTIALLY CONFIRMED SEGMENT
4497 RESTRICTED - PNR NEWLY CREATED
3487 RESTRICTED QUEUE CATEGORY
4820 RESTRICTED: REQUEST PAX AND ASSOCIATED
EXST/CBBG
6134 RESTRICTED - YOUR OFFICE IS NOT

RESPONSIBLE FOR THAT PNR
4676 SEAT ITEMS ALREADY EXIST FOR REQUESTED
SEGMENTS
23004 SEAT REQUEST NOT AVAILABLE. REQUEST

SEAT AT CHECK-IN

Page 30 of 248
8079 SEGMENT ASSOCIATION IN TRANSACTION

RESTRICTED DUE TO TK ELEMENT
12366 SEGMENT ASSOCIATION NOT ALLOWED
14 SIGN IN
105 SIMULTANEOUS CHANGES TO PNR - USE WRA/
RT TO PRINT OR IGNORE
13254 SPECIFIC SEAT REQUESTED IS NOT AVAILABLE
13279 SPECIFIC SEAT REQUESTED NOT AVAILABLE -
RESTRICTED
23304 SSR INFT NOT ADDED FOR ALL A/L
21590 SSR INFT NOT AUTHORISED FOR THIS
PASSENGER TYPE
15872 SSR NOT CREATED - DUPLICATE EXISTS
12197 SSR NOT CREATED - DUPLICATE MEAL
12199 SSR NOT CREATED - LATE MEAL REQUEST
12198 SSR NOT CREATED - MEAL UNAVAILABLE FOR
THIS ITINERARY
11651 STATUS CODE NOT PERMITTED IN INPUT
977 TELEPHONE FIELD REQUIRED
1784 TEXT TOO LONG
6138 THE ACCESS MODE MUST BE ENTERED
4540 TOO MANY SEGMENTS REQUESTED
24004 TOO MANY TICKETS ENTERED, MAXIMUM OF 4
ALLOWED PER PAX
15939 TOO MANY TICKETS ENTERED, MAXIMUM OF 40

ALLOWED
3647 TK ALREADY EXISTS FOR PASSENGER/
SEGMENT
8042 TK OPTIONS NOT ALLOWED
3657 TKPT NOT ALLOWED WITH OTHER TK
2820 TRANSACTION CODE NOT SUPPORTED
4360 UNABLE TO PROCESS ADVANCE SEAT
REQUEST
3686 USE FREEFLOW INFORMATION
1896 UNAUTHORISED DUTY CODE
2225 VERIFY CHECK DIGIT

Page 31 of 248
9380 VERIFY CHECK DIGIT : nbre

Error at EOT: Block the EOT process
1436 NEED NAME
3085 RESTRICTED/NEED GROUP NAME
4602 RESTRICTED: NEED SSR CBBG
4603 RESTRICTED: NEED SSR EXST
25691 ERROR - INFANT AGE MAY EXCEED FOR SOME
SEGMENTS
1966 NEED ITINERARY
3218 NEED ITINERARY FOR PASSENGER n
3432 UNABLE TO PROCESS/SERVICES EXCEED
NAMES
1988 NEED PASSENGER/SEGMENT ASSOC.
11677 INVALID SEGMENT STATUS – SEGMENT
11728 AIRLINE DOES NOT ALLOW NON-GROUPS ON
NEGOTIATED SPACE
2463 INDIVIDUAL NAMES REQUIRED WITH NSP FOR:
7948 REDUCE NUMBER IN PARTY.INACTIVE STATUS
IN SEG
12489 NOT ALLOWED : FLIGHT DEPARTED
12490 NOT ALLOWED : FLIGHT BOARDING
82 DUPLICATE SEGMENT n/n
3764 Unable to process segment n - LOCKED FLIGHT -
IGNORE
3765 Unable to process cancelled segment n - LOCKED
FLIGHT - IGNORE
1112 INVALID ITINERARY
15576 DUMMY AIRLINE CODE AND REAL AIRLINE
CODE CAN NOT BE MIXED
5788 PAYMENT INFORMATION MANDATORY - ENTER
SSR EPAY - XX
21821 E-MAIL ADDRESS MANDATORY – ENTER APE
2102 NEED TST
21843 ASSOCIATE FP TO ALL SEGMENTS OF A
TICKETLESS ACCESS CARRIER
315 NEED FORM OF PAYMENT

Page 32 of 248
21707 PLEASE REPRICE BEFORE SAVING

21848 UPDATE NOT ALLOWED – TICKETLESS ACCESS
CARRIER TST
23941 UPDATE NOT ALLOWED – TICKETLESS ACCESS
CARRIER TSM
3536 NEED TELEPHONE
3655 ITINERARY NOT INTERNATIONAL
3656 ITINERARY NOT DOMESTIC
3971 CHECK TICKETING DATE
4470 INVALID TICKETING DATE”
3499 AIR SEGMENT REQUIRED WITH TICKETING
ARRANGEMENT
4975 RESTRICTED
28969 UNCONFIRMED INSURANCE ONLY – CANNOT
END TRANSACT
10684 RESTRICTED : PLS ADD A SSR OTHS ZZ WITH
FREE TEXT
3086 RESTRICTED/NEED GROUP FARE
3987 RESTRICTED/SSR GRPS TCP REQUIRED PER
AIRLINE
11676 NO STAFF BOOKINGS ON CODESHARE -

SEGMENT n
11677 INVALID SEGMENT STATUS - SEGMENT n
11678 ERROR - STAFF PRIORITY (OSI STF) REQUIRED
12280 NEED SK ELEMENT – SEGMENT n
12279 NEED SK ELEMENT – PASSENGER n
12319 INVALID SK ITEM – ELEMENT n
11684 ERROR - STAFF NUMBER (FD SN) REQUIRED
4702 DISCOUNTS NOT COMBINABLE
11718 NEED FT ELEMENT
12277 NEED FT ELEMENT – PASSENGER n
12382 INVALID FT ELEMENT
3420 MODIFICATIONS RESTRICTED
21108 MISSING SSR FQTU FOR PASSENGER n
21809 MISSING SSR FQTR FOR SEGMENT n

Page 33 of 248
2622 NEED KEYWORD

Warning at EOT: A second EOT will be successful
23265 WARNING - INFANT AGE MAY EXCEED FOR
SOME SEGMENTS
23130 WARNING: NAME CHANGED –SEGMENTS WILL

BE CANCELLED: n,n/n-n
23131 WARNING: NAME CHANGED –SEGMENTS WILL
BE WAITLISTED: n,n/n-n
3359 WARNING: CHECK ITINERARY STATUS
15916 WARNING: CHECK SEGMENT CONTINUITY –
SEGMENT n/n
15915 WARNING: CHECK DEPARTURE/ARRIVAL –
SEGMENT n/n
1961 WARNING: CHECK MINIMUM CONNECTION TIME
– SEGMENT n/n
12024 WARNING: PAST DATED SEGMENT REMOVED
3666 WARNING: COMBINE SEGMENTS
15664 WARNING:ENTER PAYMENT INFO TO SECURE
TICKETLESS BOOKING-HE EPAY
15672 WARNING: CHANGES RESTRICTED ONCE

PAYMENT ACCEPTED - XX
22433 WARNING TICKETLESS – ONLY FIRST APE/AB
SENT – SEE AIS PAGES
24389 WARNING USE APM MOBILE PHONE

INTERNATIONAL_FORMAT_11-15_NUM
4503 WARNING:AIRLINE CODE NOT IN ITINERARY -

SSR/OSI CANCELLED AT EOT
3381 WARNING CHECK OSI/SSR STATUS CODE
4503 WARNING: AIRLINE NOT IN ITINERARY- SSR/OSI
CANCELLED AT EOT
28934 WARNING: SECURE FLT PASSENGER DATA

REQUIRED FOR TICKETING PAX [PaxId]
11647 WARNING: AIRLINE NOT IN ITINERARY- SK
CANCELLED AT EOT
11645 WARNING: HOLIDAY BOOKING EXISTS - PLEASE

CHECK DETAILS
12215 WARNING: AIRLINE CODE NOT IN ITINERARY

OPX/OPQ REMOVED

Page 34 of 248
9527 WARNING: UNCONFIRMED INSURANCE

PRESENT - PLS CONFIRM
21932 WARNING: OA CONTROLLED PNR
4466 WARNING: CHECK QUEUEING OFFICE
2463 WARNING: STATUS WILL REVERT TO NN FOR:
Note: TBD stands for to be defined.
4.1 Error Reply

Page 35 of 248
5 Operations
5.1 Operation: Accounting Information
The example below illustrates a request to add an accounting element with the following information:
Parameter Information
Account Number DEC001029
Cost Center Number DV123
Company ID Number DEC038FR
Client Reference Number LOFKFD122
5.1.1 Query Structure

<PNR_AddMultiElements xmlns="http://xml.amadeus.com/PNRADD_12_2_1A" >
<pnrActions>
<optionCode>0</optionCode>
</pnrActions>
<dataElementsMaster>
<dataElementsIndiv>
<elementManagementData>
<reference>
<qualifier>OT</qualifier>
<number>1</number>
</reference>
<segmentName>AI</segmentName>
</elementManagementData>
<accounting>
<account>
<number>DEC001029</number>
<costNumber>DV123</costNumber>
<companyNumber>DEC038FR</companyNumber>
<clientReference>LOFKFD122</clientReference>
</account>
</accounting>
</dataElementsIndiv>
</dataElementsMaster>
</PNR_AddMultiElements>
5.1.2 Reply Structure
<PNR_Reply xmlns="http://xml.amadeus.com/PNRACC_12_2_1A" >
<pnrHeader>
<reservationInfo>
<reservation>
<companyId>1A</companyId>
</reservation>

Page 36 of 248
</reservationInfo>
</pnrHeader>
<securityInformation>
<responsibilityInformation>
<typeOfPnrElement>RP</typeOfPnrElement>
<officeId>MUC6X0701</officeId>
</responsibilityInformation>
<queueingInformation>
<queueingOfficeId>MUC6X0701</queueingOfficeId>
</queueingInformation>
</securityInformation>
<sbrPOSDetails>
<sbrUserIdentificationOwn>
<originIdentification>
<inHouseIdentification1> </inHouseIdentification1>
</originIdentification>
</sbrUserIdentificationOwn>
<sbrSystemDetails>
<deliveringSystem>
<companyId> </companyId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry> </codedCountry>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrCreationPosDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrCreationPosDetails>
<sbrUpdatorPosDetails>

Page 37 of 248
<inHouseIdentification1>MUC6X0701</inHouseIdentification1>
<originatorTypeCode>A</originatorTypeCode>
<sbrSystemDetails>
<deliveringSystem>
<locationId>MUC</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry>DE</codedCountry>
</userPreferences>
</sbrPreferences>
</sbrUpdatorPosDetails>
<travellerInfo>
<elementManagementPassenger>
<reference>
<qualifier>PT</qualifier>
<number>1</number>
</reference>
<segmentName>NM</segmentName>
<lineNumber>1</lineNumber>
</elementManagementPassenger>
<passengerData>
<travellerInformation>
<traveller>
<surname>PRICING</surname>
<quantity>1</quantity>
</traveller>
<passenger>
<firstName>A</firstName>
<type>ADT</type>
</passenger>
</travellerInformation>
</passengerData>
</travellerInfo>
<marker2> </marker2>
<dataElementsIndiv>
<reference>
<number>4</number>
</reference>

Page 38 of 248
<segmentName>AI</segmentName>
<accounting>
<account>
<number>DEC001029</number>
<costNumber>DV123</costNumber>
<companyNumber>DEC038FR</companyNumber>
<clientReference>LOFKFD122</clientReference>
</account>
</accounting>
<referenceForDataElement>
<reference>
<number>1</number>
</reference>
</referenceForDataElement>
</PNR_Reply>
5.1.3 Possible Errors

Page 39 of 248
5.2 Operation: ARNK Segment

When the arrival is unknown, an ARNK is input. Segment indicates that it is not known how the passenger
proceeds from the arrival city of the previous segment to the departure city of the next segment. An ARNK
segment may be passenger associated at input or prior to end transaction. ARNK, without association, applies
to all passenger names in a PNR. When associated to less than the total number of names elements entered,
a non homogeneous condition exists. Itinerary is not valid if an ARNK precedes another ARNK.
<pnrActions>
</pnrActions>
<originDestinationDetails>
<originDestination> </originDestination>
<itineraryInfo>
<elementManagementItinerary>
<segmentName>AIR</segmentName>
</elementManagementItinerary>
<airAuxItinerary>
<travelProduct>
<productDetails>
<identification>ARNK</identification>
</productDetails>
</travelProduct>
<messageAction>
<business>
<function>0</function>
</business>
</messageAction>
</airAuxItinerary>
</itineraryInfo>
</originDestinationDetails>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 40 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 41 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>
<qualifier>ST</qualifier>
<number>1</number>
</reference>
<travelProduct>
<productDetails>
<identification>ARNK</identification>
</productDetails>
<processingIndicator>N</processingIndicator>
</travelProduct>
<itineraryMessageAction>
<business>
</business>
</itineraryMessageAction>
<markerRailTour> </markerRailTour>
</itineraryInfo>
</PNR_Reply>

? If EOT is made with two ARNK following each other, the following message is displayed: INVALID ITINERARY

Page 42 of 248
5.3 Operation: Confidential Remark

The example below illustrates a request for a confidential remark.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>13</number>
</reference>
<segmentName>RC</segmentName>
<miscellaneousRemark>
<remarks>
<type>RC</type>
<freetext>CONFIDENTIAL REMARK FREE TEXT</freetext>
</remarks>
</miscellaneousRemark>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 43 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>

Page 44 of 248
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>2</number>
</reference>
<segmentName>RC</segmentName>
<miscellaneousRemarks>
<remarks>
<type>RC</type>
<freetext>CONFIDENTIAL REMARK FREE TEXT</freetext>
</remarks>
<individualSecurity>
<office>06686737</office>
<accessMode>B</accessMode>
</individualSecurity>
</miscellaneousRemarks>
</PNR_Reply>

Page 45 of 248
5.4 Operation: Connection Flight

The following example below illustrates a request to reserve connection flight:
Airline 7S
Flight Number (1) 1288
Date 17/05/13
City Pair AMS/LHR
Class of service K
Date 17/05/13
City Pair LHR/LAX
Class of service B
Airline 6X
Date 17/05/13
City Pair LAX/SCL
Class of service Y
Number of seats to reserve 1

<pnrActions>
</pnrActions>
<originDestination>
<origin>AMS</origin>
<destination>SLC</destination>
</originDestination>
<itineraryInfo>
<airAuxItinerary>
<travelProduct>
<product>
<depDate>170513</depDate>
</product>

Page 46 of 248
<boardpointDetail>
<cityCode>AMS</cityCode>
</boardpointDetail>
<offpointDetail>
<cityCode>LHR</cityCode>
</offpointDetail>
<company>
<identification>7S</identification>
</company>
<productDetails>
<identification>1288</identification>
<classOfService>K</classOfService>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>NN</status>
</relatedProduct>
<selectionDetailsAir>
<selection>
<option>0</option>
</selection>
</selectionDetailsAir>
</airAuxItinerary>
</itineraryInfo>
<itineraryInfo>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
<cityCode>LAX</cityCode>
</offpointDetail>
<company>

Page 47 of 248
</company>
<productDetails>
<classOfService>B</classOfService>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>NN</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
</airAuxItinerary>
</itineraryInfo>
<itineraryInfo>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
<cityCode>SLC</cityCode>
</offpointDetail>
<company>
<identification>6X</identification>
</company>
<productDetails>
<classOfService>Y</classOfService>
</productDetails>
</travelProduct>
<messageAction>
<business>

Page 48 of 248
</business>
</messageAction>
<relatedProduct>
<status>NN</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>CDG7S0001</officeId>
<iataCode>12345675</iataCode>
<queueingOfficeId>CDG7S0001</queueingOfficeId>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>

Page 49 of 248
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<originatorId>12345675</originatorId>
<inHouseIdentification1>CDG7S0001</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>
<companyId>7S</companyId>
<locationId>CDG</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry>FR</codedCountry>
</userPreferences>
</sbrPreferences>
<itineraryInfo>

Page 50 of 248
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
<depTime>1630</depTime>
<arrDate>170513</arrDate>
<arrTime>1730</arrTime>
</product>
<boardpointDetail>
<cityCode>AMS</cityCode>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
<classOfService>K</classOfService>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HL</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>77W</equipment>
<numOfStops>0</numOfStops>
<weekDay>5</weekDay>
</productDetails>
<arrivalStationInfo>

Page 51 of 248
<terminal>2</terminal>
</arrivalStationInfo>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
<itineraryfreeFormText>
<freetextDetail>
<subjectQualifier>3</subjectQualifier>
</freetextDetail>
<text>SEE RTSVC</text>
<text>WARNING - WAIT LIST</text>
</itineraryfreeFormText>
</itineraryInfo>
<itineraryInfo>
<reference>
<number>2</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
<classOfService>B</classOfService>
</productDetails>
<typeDetail>

Page 52 of 248
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HL</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>77W</equipment>
</productDetails>
<departureInformation>
<departTerminal>2</departTerminal>
</departureInformation>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
<text>WARNING - WAIT LIST</text>
</itineraryInfo>
<itineraryInfo>
<reference>
<number>3</number>
</reference>

Page 53 of 248
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
<cityCode>SLC</cityCode>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
</productDetails>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>CR9</equipment>
</productDetails>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>

Page 54 of 248
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
<text>6X CONX/QUOTE AS SKYWEST AIRLINES 13\</text>
<text>\</text>
<text>WI-FI 6\</text>
<text>\</text>
<text>SKY PRIORI</text>
<text>OPERATED BY SUBSIDIARY/FRANCHISE</text>
</itineraryInfo>
<segmentGroupingInfo>
<groupingCode>CNX</groupingCode>
<marriageDetail>
<tatooNum>1</tatooNum>
</marriageDetail>
<marriageDetail>
</marriageDetail>
<marriageDetail>
</marriageDetail>
</segmentGroupingInfo>
</PNR_Reply>

MAXIMUM NUMBER OF CONNECTING FLIGHTS IS 6 RESTRICTED - USE SAME ACTION CODE FOR
ALL SALES

Page 55 of 248
5.5 Operation: Contact Information

The example below illustrates the request for an agency contact element with the following information:
Phone Number 04.92.94.70.00
Agency contact indicator AGCY

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>AP</segmentName>
<freetextData>
<freetextDetail>
<type>6</type>
</freetextDetail>
<longFreetext>04.92.94.70.00 - AGCY</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 56 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 57 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>6</type>
</freetextDetail>
<longFreetext>04.92.94.70.00 - AGCY</longFreetext>
</otherDataFreetext>
</PNR_Reply>

Page 58 of 248
5.6 Operation: Creating an OSI with Mandatory Airline Code

This example shows how to create an OSI including mandatory airline code 6X:

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<segmentName>OS</segmentName>
<freetextData>
<freetextDetail>
<type>P27</type>
<companyId>6X</companyId>
</freetextDetail>
<longFreetext>6X FB00S7 B744 UMLAUF71343</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>

Page 59 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>

Page 60 of 248
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>OS</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>28</type>
</freetextDetail>
<longFreetext>6X FB00S7 B744 UMLAUF71343</longFreetext>
</PNR_Reply>

See "Error Messages" section.

Page 61 of 248
5.7 Operation: E-mail

The example below illustrates the request for an EMAIL contact element with the following information:
E-mail Contact Lchildrens@Amadeus.net
Agency contact indicator - EMAIL

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<freetextData>
<freetextDetail>
<type>P02</type>
</freetextDetail>
<longFreetext>LCHILDRENS@AMADEUS.NET</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 62 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>

Page 63 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>2</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>P02</type>
</freetextDetail>
<longFreetext>LCHILDRENS@AMADEUS.NET</longFreetext>
</PNR_Reply>

Page 64 of 248
5.8 Operation: End Of Transaction

To end transact the PNR using options mentioned in supported operations paragrah

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<segmentName>RF</segmentName>
<freetextData>
<freetextDetail>
<type>P22</type>
</freetextDetail>
<longFreetext>RF ADDED VIA PNRADD</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>
<controlNumber>5YEJBW</controlNumber>
<date>251012</date>
<time>1005</time>
</reservation>
</reservationInfo>
</pnrHeader>
<agentId>BMPR</agentId>

Page 65 of 248
<cityCode>DAP</cityCode>
<secondRpInformation>
<creationOfficeId>MUC6X0701</creationOfficeId>
<agentSignature>1234BM</agentSignature>
<creationDate>251012</creationDate>
<creationTime>1005</creationTime>
</secondRpInformation>
<freetextData>
<freetextDetail>
<type>P12</type>
</freetextDetail>
<longFreetext>--- RLR ---</longFreetext>
</freetextData>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>

Page 66 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<technicalData>
<enveloppeNumberData>
<sequenceDetails>
<number>1</number>
</sequenceDetails>
</enveloppeNumberData>
<lastTransmittedEnvelopeNumber>
<currentRecord>0</currentRecord>
</lastTransmittedEnvelopeNumber>
<purgeDateData>
<dateTime>
<year>2013</year>
<month>1</month>
<day>28</day>
</dateTime>
</purgeDateData>
</technicalData>
<travellerInfo>

Page 67 of 248
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>GOLD</surname>
</traveller>
<passenger>
<firstName>GOLD MISS</firstName>
<type>ADT</type>
<identificationCode>ID1</identificationCode>
</passenger>
</passengerData>
</travellerInfo>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>NCE</cityCode>
</boardpointDetail>
<offpointDetail>
<cityCode>CDG</cityCode>
</offpointDetail>
<companyDetail>

Page 68 of 248
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>744</equipment>
</productDetails>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
</itineraryInfo>
<dataElementsIndiv>
<reference>
<number>2</number>
</reference>
<otherDataFreetext>
<freetextDetail>

Page 69 of 248
<type>5</type>
</freetextDetail>
<longFreetext>CONTACT ADDED VIA PNRADD</longFreetext>
<dataElementsIndiv>
<otherDataFreetext>
<freetextDetail>
<type>P22</type>
</freetextDetail>
<longFreetext>RF ADDED VIA PNRADD</longFreetext>
<dataElementsIndiv>
<reference>
<number>4</number>
</reference>
<segmentName>TK</segmentName>
<ticketElement>
<ticket>
<indicator>OK</indicator>
<date>280113</date>
</ticket>
</ticketElement>
</PNR_Reply>


Page 70 of 248
5.9 Operation: Extra Seat

The example below illustrates a simple name request for an extra seat with the following information:
Traveler Surname CHIKKLES
Traveler First name JOHN
Extra Seat Qualifier E

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<qualifier>PR</qualifier>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>CHIKKLES</surname>
<qualifier>E</qualifier>
</traveller>
<passenger>
<firstName>JOHN</firstName>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>

Page 71 of 248
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 72 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
</passenger>
</passengerData>
</travellerInfo>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>

Page 73 of 248
<traveller>
</traveller>
<passenger>
<firstName>EXST</firstName>
</passenger>
</passengerData>
</travellerInfo>
</PNR_Reply>

Page 74 of 248
5.10 Operation: Fare Discount for a child

The example below illustrates a request to store a fare discount element for child with 10% dicount.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FD</segmentName>
<fareDiscount>
<discount>
<adjustmentReason>CH</adjustmentReason>
<percentage>10</percentage>
</discount>
</fareDiscount>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 75 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
<locationId>NCE</locationId>
</deliveringSystem>
</sbrSystemDetails>

Page 76 of 248
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>TEST</surname>
</traveller>
<passenger>
<firstName>PAX</firstName>
<type>CHD</type>
</passenger>
</passengerData>
<enhancedPassengerData>
<enhancedTravellerInformation>
<travellerNameInfo>
<type>CHD</type>
</travellerNameInfo>
<otherPaxNamesDetails>
<nameType>UN</nameType>
<referenceName>Y</referenceName>
<displayedName>Y</displayedName>
<givenName>PAX</givenName>
</otherPaxNamesDetails>
</enhancedTravellerInformation>
</enhancedPassengerData>
</travellerInfo>
<dataElementsIndiv>

Page 77 of 248
<reference>
<number>3</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>P04</type>
</freetextDetail>
<longFreetext>CH10</longFreetext>
</PNR_Reply>

Page 78 of 248
5.11 Operation: Fare Discount for a child with a birth date

The example below illustrates a request to store a fare discount element for child with 10% dicount and birth
date 01FEB03.
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<fareDiscount>
<discount>
<adjustmentReason>CH</adjustmentReason>
</discount>
<birthDate>010203</birthDate>
</fareDiscount>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 79 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>

Page 80 of 248
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>CHD</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>CHD</type>
</travellerInfo>
<dataElementsIndiv>

Page 81 of 248
<reference>
<number>3</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>P04</type>
</freetextDetail>
<longFreetext>CH01FEB03</longFreetext>
</PNR_Reply>

Page 82 of 248
5.12 Operation: Fare Discount for senior citizen

The example below illustrates a request to store a fare discount element senior citizen with 10% discount.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<fareDiscount>
<passengerType>PAX</passengerType>
<discount>
<adjustmentReason>CD</adjustmentReason>
</discount>
</fareDiscount>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 83 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>

Page 84 of 248
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
</passenger>
</passengerData>
<travellerNameInfo>
</travellerInfo>
<dataElementsIndiv>
<reference>

Page 85 of 248
<number>3</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>P04</type>
</freetextDetail>
<longFreetext>PAX CD10</longFreetext>
</PNR_Reply>

Page 86 of 248
5.13 Operation: Fax Number

The example below illustrates the request for a fax contact element with the following information:
Fax Number 04.92.93.44.99
Agency contact indicator - FAX

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>16</number>
</reference>
<segmentName>AB</segmentName>
<structuredAddress>
<informationType>P01</informationType>
<address>
<optionA1>A1</optionA1>
<optionTextA1>04.92.93.44.99</optionTextA1>
</address>
</structuredAddress>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 87 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 88 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>
<givenName>A</givenName>

Page 89 of 248
</travellerInfo>
<dataElementsIndiv>
<reference>
<number>4</number>
</reference>
<segmentName>AB/</segmentName>
<structuredAddress>
<informationType>2</informationType>
<address>
<option>A1</option>
<optionText>04.92.93.44.99</optionText>
</address>
</PNR_Reply>

Page 90 of 248
5.14 Operation: Form of Payment

Used to specify the form of payment for a ticket.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<segmentName>FP</segmentName>
<formOfPayment>
<fop>
<identification>CC</identification>
<creditCardCode>VI</creditCardCode>
<accountNumber>4444333322221111</accountNumber>
<expiryDate>1212</expiryDate>
</fop>
</formOfPayment>
<fopExtension>
<fopSequenceNumber>1</fopSequenceNumber>
<newFopsDetails>
<cvData>123</cvData>
</newFopsDetails>
</fopExtension>

<message type="PNRACC" agency="1A" version="12" release="2" >
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 91 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<originatorTypeCode>N</originatorTypeCode>

Page 92 of 248
<sbrSystemDetails>
<deliveringSystem>
<locationId>PAR</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<firstName>JRL</firstName>
</passenger>
</passengerData>
<enhancedTravellerInformation> </enhancedTravellerInformation>
</travellerInfo>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>

Page 93 of 248
<otherDataFreetext>
<freetextDetail>
<type>16</type>
</freetextDetail>
<longFreetext>CCVI4444333322221111D1213*CV</longFreetext>
</message>

INVALID FORM OF PAYMENT: If there are errors in the FOP syntax. For example invalid FOP code. INVALID
ACCOUNT NUMBER: The CC number is not compliant with Luhn algorithm or length restrictions (too short or
too long) CREDIT CARD EXPIRED: if the credit card is expired.

Page 94 of 248
5.15 Operation: Frequent Flyer Numbers

The frequent flyer information is deemed as a type of special services request, and therefore will utilize the
special services request (/dataElementsMaster /dataElementsIndiv /serviceRequest (SSR)) structure in this
function. The segment name will be requested as an SSR will have an associated type of FQTV, indicating
frequent traveler information.
Besides this, it is stored as an SSR item, the applicable airline information for the surrounding SSR structure
will need to be propagated in the structure to indicate which airlines should receive the transmitted frequent
traveler information. Failure to complete the SSR required would result in an error message.
Note:Some airlines may reject these manual SSR FQTV. These elements are not validated against Amadeus
Frequent Flyer database
The example below illustrates a request for a frequent flyer number with the following information
FQTV Airline QF
Membership Number QF1117622
Passenger Association Passenger element number 1

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>SSR</segmentName>
<serviceRequest>
<ssr>
<type>FQTV</type>
<companyId>QF</companyId>
<indicator>P01</indicator>
</ssr>
</serviceRequest>
<frequentTravellerData>
<frequentTraveller>
<membershipNumber>QF1117622</membershipNumber>
</frequentTraveller>
</frequentTravellerData>

Page 95 of 248
<reference>
<number>1</number>
</reference>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<pnrHeader>
<reservationInfo>
<reservation>
<controlNumber>9D5NU8</controlNumber>
<controlType>F</controlType>
</reservation>
</reservationInfo>
</pnrHeader>
<freetextData>
<freetextDetail>
<type>P12</type>
</freetextDetail>
<longFreetext>--- NHP ---</longFreetext>
</freetextData>
<pnrHeaderTag>
<statusInformation>

Page 96 of 248
<indicator>NHP</indicator>
</statusInformation>
</pnrHeaderTag>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<originatorTypeCode>E</originatorTypeCode>
<sbrSystemDetails>
<deliveringSystem>

Page 97 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>ABOUD</surname>
</traveller>
<passenger>
<firstName>RUSSEL MR</firstName>
<type>ADT</type>
</passenger>
</passengerData>
<enhancedTravellerInformation> </enhancedTravellerInformation>
</travellerInfo>
<itineraryInfo>
<reference>
<number>1</number>
</reference>

Page 98 of 248
<travelProduct>
<product>
<dayChangeIndicator>1</dayChangeIndicator>
</product>
<boardpointDetail>
<cityCode>NRT</cityCode>
</boardpointDetail>
<offpointDetail>
<cityCode>SYD</cityCode>
</offpointDetail>
<companyDetail>
<identification>QF</identification>
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
</productDetails>
</flightDetail>

Page 99 of 248
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
<text>ADV PAX WWW.SMARTRAVELLER.GOV.AU</text>
</itineraryInfo>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<serviceRequest>
<ssr>
<type>FQTV</type>
<status>HK</status>
<indicator>P02</indicator>
</ssr>
</serviceRequest>
<frequentFlyerInformationGroup>
<frequentTravellerInfo>
<frequentTraveler>
<company>QF</company>
<membershipNumber>1117622</membershipNumber>
</frequentTraveler>
<priorityDetails>
<qualifier>1</qualifier>
<priorityCode>1</priorityCode>
<tierLevel>CLPO</tierLevel>
</priorityDetails>
<priorityDetails>

Page 100 of 248
<priorityCode>1</priorityCode>
<tierLevel>EMER</tierLevel>
<tierDescription>EMERALD</tierDescription>
</priorityDetails>
</frequentTravellerInfo>
</frequentFlyerInformationGroup>
<reference>
<number>1</number>
</reference>
<dataElementsIndiv>
<reference>
<number>7</number>
</reference>
<segmentName>SK</segmentName>
<serviceRequest>
<ssr>
<type>ACIM</type>
<status>HK</status>
<freeText>61403585400</freeText>
</ssr>
</serviceRequest>
<reference>
<number>1</number>
</reference>
</PNR_Reply>

DUPLICATE EXISTS TARGET AIRLINE MISSING CARD AIRLINE MISSING FF NUMBER MISSING NO AIR
SEGMENTS PASSENGER AND_OR SEGMENT DATA NOT VALID SSR ITEM TOO LONG INVALID ACTION
CODE INVALID NIP (NIP=Number in Party) NO AGREEMENT BETWEEN INVALID TEXT DATA

Page 101 of 248
5.16 Operation: General Remark

The example below illustrates a request for a general miscellaneous remark.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>RM</segmentName>
<remarks>
<type>RM</type>
<freetext>GENERAL REMARK</freetext>
</remarks>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 102 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>

Page 103 of 248
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>2</number>
</reference>
<remarks>
<type>RM</type>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
</PNR_Reply>

Page 104 of 248
5.17 Operation: Ghost Segment

Segment originally booked in another system, or speculative booking. These segments are not reported or
billed to the controlling carrier.
For Ghost segments:
• Record Locator mandatory
• Action codes: GK, GN, GL
• Departure/arrival time mandatory if flight not recorded in 1A
Example:
Airline 7S
Date 020413
City Pair CDG/HEL
Class of service Y
Rloc 5O911

<pnrActions>
</pnrActions>
<originDestination>
<origin>CDG</origin>
<destination>HEL</destination>
<itineraryInfo>
<reference>
<qualifier>SR</qualifier>
<number>1</number>
</reference>
<airAuxItinerary>
<travelProduct>
<product>

Page 105 of 248
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
<cityCode>HEL</cityCode>
</offpointDetail>
<company>
</company>
<productDetails>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>GK</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
<reservationInfoSell>
<reservation>
<controlNumber>5O911</controlNumber>
</reservation>
</reservationInfoSell>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>

Page 106 of 248
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 107 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>

Page 108 of 248
</productDetails>
</travelProduct>
<business>
</business>
<itineraryReservationInfo>
<reservation>
<controlNumber>SICVYY</controlNumber>
</reservation>
</itineraryReservationInfo>
<relatedProduct>
<status>GK</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>E90</equipment>
</productDetails>
<departTerminal>2D</departTerminal>
<timeDetail>
<checkinTime>1015</checkinTime>
</timeDetail>
</flightDetail>
<selectionDetails>
<selection>
<option>P10</option>
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
</itineraryInfo>

Page 109 of 248
</PNR_Reply>

? Record Locator missing: Error Information (ERC) ZZZ and IFT "NEED AGENT SIGN / RECORD LOCATOR" ?
Departure/arrival time missing whereas flight is not recorded in 1A: Error Information (ERC) 134 and Error Free
From Text ( IFT) "INPUT TIMES"

Page 110 of 248
5.18 Operation: Group Name

The example below illustrates a group name with 2 travelers containing the following information:
Group Name MARTIEN GROUP
Traveler1 Surname CHILDS
Traveler1 First name LISA
Traveler2 Surname CHIKKLES
Traveler2 First name ROBERT
Note: the /elementManagementPassenger /reference /qualifier and the /elementManagementPassenger /
reference /number are not set for the group name, but rather only for the individual names entered beneath
the group name title.
<pnrActions>
</pnrActions>
<travellerInfo>
<segmentName>NG</segmentName>
<passengerData>
<traveller>
<surname>MARTIEN GROUP</surname>
<qualifier>G</qualifier>
</traveller>
</passengerData>
</travellerInfo>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>CHILDS</surname>

Page 111 of 248
</traveller>
<passenger>
<firstName>LISA</firstName>
</passenger>
</passengerData>
</travellerInfo>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<firstName>ROBERT</firstName>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 112 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>

Page 113 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<segmentName>NG</segmentName>
<passengerData>
<traveller>
<surname>MARTIEN GROUP</surname>
<qualifier>G</qualifier>
</traveller>
<groupCounters>
<quantityDetails>
<numberOfUnit>10</numberOfUnit>
<unitQualifier>BKD</unitQualifier>
</quantityDetails>
<quantityDetails>
<unitQualifier>CNL</unitQualifier>
</quantityDetails>
<quantityDetails>
<unitQualifier>SPL</unitQualifier>
</quantityDetails>
</groupCounters>
</passengerData>
</travellerInfo>
<travellerInfo>
<reference>
<number>3</number>
</reference>
<passengerData>

Page 114 of 248
<traveller>
</traveller>
<passenger>
<firstName>ROBERT</firstName>
</passenger>
</passengerData>
<travellerNameInfo>
<givenName>ROBERT</givenName>
</travellerInfo>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<firstName>LISA</firstName>
</passenger>
</passengerData>

Page 115 of 248
<travellerNameInfo>
<givenName>LISA</givenName>
</travellerInfo>
</PNR_Reply>

Page 116 of 248
5.19 Operation: Ignore

To ignore the PNR using options mentioned in supported operations paragrah

<pnrActions>
</pnrActions>
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>

Page 117 of 248
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</PNR_Reply>


Page 118 of 248
5.20 Operation: Infant With First And Last Name And Date of Birth
The infant has to be associated to another passenger, and is attached to the same /travellerInfo /
passengerData /travellerInformation element field quantity = 2.

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>
<traveller>
<surname>SMITH</surname>
</traveller>
<passenger>
<firstName>A MRS</firstName>
<type>ADT</type>
<infantIndicator>3</infantIndicator>
</passenger>
</passengerData>
<passengerData>
<traveller>
<surname>BROWN</surname>
</traveller>
<passenger>
<firstName>JIMMY</firstName>
<type>INF</type>
</passenger>
<dateOfBirth>
<dateAndTimeDetails>
<date>10JAN08</date>
</dateAndTimeDetails>
</dateOfBirth>

Page 119 of 248
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>

Page 120 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>

Page 121 of 248
</passenger>
</passengerData>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>INF</type>
</passenger>
<dateOfBirth>
<date>10012011</date>
</dateOfBirth>
</passengerData>
<travellerNameInfo>
<type>ADT</type>
<givenName>A MRS</givenName>
<travellerNameInfo>
<type>INF</type>

Page 122 of 248
<givenName>JIMMY</givenName>
<dateOfBirthInEnhancedPaxData>
<date>10012011</date>
</dateOfBirthInEnhancedPaxData>
</travellerInfo>
</PNR_Reply>

Page 123 of 248
5.21 Operation: Infant With First Name Only

passengerData /travellerInformation element,field quantity = 2.
<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
<passenger>
<type>INF</type>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>

Page 124 of 248
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 125 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
<passenger>
<type>INF</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>

Page 126 of 248
<travellerNameInfo>
<type>INF</type>
<givenName>JIMMY</givenName>
</travellerInfo>
</PNR_Reply>

Page 127 of 248
5.22 Operation: Infant With No Information

The infant has to be associated to another passenger, andis attached to the same /travellerInfo /
<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 128 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 129 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>

Page 130 of 248
</travellerInfo>
</PNR_Reply>

Page 131 of 248
5.23 Operation: Infant with own Native firstname

Native name 김/지훈 will be used for the adult, 수진 for the firstname infant, to be able to illustrate.
In the reply, the header flag RCH is displayed, as Native names are present in the PNR.

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<travellerNameInfo>
<type>ADT</type>
<travellerIdentificationCode>ID123456</travellerIdentificationCode>
<surname>김</surname>
<givenName>지훈</givenName>
<title>MR</title>
<travellerNameInfo>
<type>INF</type>
<givenName>수진</givenName>

Page 132 of 248
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>SEL1A0980</officeId>
<queueingOfficeId>SEL1A0980</queueingOfficeId>
<freetextData>
<freetextDetail>
<type>P12</type>
</freetextDetail>
<longFreetext>--- RCH---</longFreetext>
</freetextData>
<pnrHeaderTag>
<statusInformation>
<indicator>RCH</indicator>
</pnrHeaderTag>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>

Page 133 of 248
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>SEL1A0980</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>
<locationId>SEL</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry>KR</codedCountry>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>

Page 134 of 248
<passengerData>
<traveller>
<surname>KIM</surname>
</traveller>
<passenger>
<firstName>JI HUN MR</firstName>
<type>ADT</type>
</passenger>
<passenger>
<firstName>SU JIN</firstName>
<type>INF</type>
</passenger>
</passengerData>
<travellerNameInfo>
<nameType>NN1</nameType>
<nameType>RN1</nameType>
<displayedName>N</displayedName>
<romanizationMethod>KAR</romanizationMethod>
<givenName>JI HUN</givenName>
<title>MR</title>

Page 135 of 248
<travellerNameInfo>
<type>INF</type>
<givenName>SU JIN</givenName>
</travellerInfo>
</PNR_Reply>


Page 136 of 248
5.24 Operation: Informational Segment

An information flight segment gives details of a non-Altea flight that has not been booked through Amadeus.
Entering this segment may or may not generate a message to the Airline involved, depending on whether
any other element for action by the same airline is enterd in the PNR during the same or a subsequent
transaction.This informational segment is not recognized by the system for pricing or ticketing. Informational
segment can be included in group and non-group PNRs.
For Informational segments:
• Departure/arrival time mandatory
• HK, HL, HN are the only authorized status code
• Only for non Altea airlines
• N will be added at the end of TVL segment (Edifact message)
Example:
Airline 7S
Date 211212
City Pair HKG/SIN
Class of service Y
Depature time 1420
Arrival time 1805

<pnrActions>
</pnrActions>
<originDestination>
<origin>HKG</origin>
<destination>SIN</destination>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<airAuxItinerary>

Page 137 of 248
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>HKG</cityCode>
</boardpointDetail>
<offpointDetail>
<cityCode>SIN</cityCode>
</offpointDetail>
<company>
</company>
<productDetails>
<classOfService>C</classOfService>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>

Page 138 of 248
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 139 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>HKG</cityCode>
</boardpointDetail>
<offpointDetail>
<cityCode>SIN</cityCode>
</offpointDetail>
<companyDetail>
</companyDetail>

Page 140 of 248
<productDetails>
<classOfService>C</classOfService>
</productDetails>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment> </equipment>
</productDetails>
</flightDetail>
<selectionDetails>
<selection>
</selection>
</selectionDetails>
</itineraryInfo>
</PNR_Reply>

? Departure/arrival time missing: Error Information (ERC) 134 and Error Free From Text ( IFT) "INPUT TIMES" ?
Other action code than HK, HL, HN: Error Information (ERC) ZZZ and IFT "INVALID STATUS CODE" ? On
Altea airline: Error Information (ERC) ZZZ and Error Free From Text ( IFT) "RESTRICTED ACTION CODE"

Page 141 of 248
5.25 Operation: Manual Commission

The example below illustrates the request to create a manual commission.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FM</segmentName>
<commission>
<commissionInfo>
</commissionInfo>
</commission>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>SEL6X0120</officeId>
<queueingOfficeId>SEL6X0120</queueingOfficeId>

Page 142 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>SEL6X0120</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>

Page 143 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<marker2/>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FM</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>11</type>
</freetextDetail>
<longFreetext>5</longFreetext>
</PNR_Reply>


Page 144 of 248
5.26 Operation: Manual Endorsement

The example below illustrates the request to create a manual endorsement.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FE</segmentName>
<fareElement>
<generalIndicator>E</generalIndicator>
<freetextLong>MANUAL ENDORSEMENT</freetextLong>
</fareElement>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>NCE6X0100</officeId>
<queueingOfficeId>NCE6X0100</queueingOfficeId>

Page 145 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>NCE6X0100</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>

Page 146 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FE</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>10</type>
</freetextDetail>
<longFreetext>PAX \*M\*MANUAL ENDORSEMENT</longFreetext>
</PNR_Reply>


Page 147 of 248
5.27 Operation: Name With ID Code

The example below illustrates a simple name request with thefollowing information:
Traveler Surname CHIPIE
Traveler First name ROBERT
Passenger ID Code ID12344
Note: Two identification codes are supported they are 'ID' and or 'CR'. The ID codes are individually assigned
and can form part of a client's department name and or even a description. Therefore it may be unique to a
passenger. The CR code can form part of a name element and can reference when a PNR has been created
from a Cruise Application via a specific message.
<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>DUPONT</surname>
</traveller>
<passenger>
<firstName>MATHIEU</firstName>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>

Page 148 of 248
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 149 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
</passenger>
</passengerData>
<travellerNameInfo>

Page 150 of 248
<givenName>JOHN</givenName>
</travellerInfo>
</PNR_Reply>

Page 151 of 248
5.28 Operation: Name With Passenger Type Code

The example below illustrates a simple name request with the following information:
Traveler Surname CHIPIE
Traveler First name WILLIAM
Passenger Type CHILD (CHD)

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>CHD</type>
</passenger>
<dateOfBirth>
<date>20MAR00</date>
</dateOfBirth>
</passengerData>
</travellerInfo>

<pnrHeader>

Page 152 of 248
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>

Page 153 of 248
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>CHD</type>
</passenger>
<dateOfBirth>
<date>20032000</date>
</dateOfBirth>
</passengerData>

Page 154 of 248
<travellerNameInfo>
<type>CHD</type>
<givenName>MATHIEU</givenName>
<dateOfBirthInEnhancedPaxData>
<date>20032000</date>
</dateOfBirthInEnhancedPaxData>
</travellerInfo>
</PNR_Reply>

Page 155 of 248
5.29 Operation: Name with title separated from firstname

This example illustrate the addition of a name with title separated from firstname.

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<travellerNameInfo>
<type>ADT</type>
<surname>SURNAME</surname>
<givenName>GIVENNAME</givenName>
<title>MR</title>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 156 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>

Page 157 of 248
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<firstName>GIVENNAME MR</firstName>
<type>ADT</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>
<givenName>GIVENNAME</givenName>
<title>MR</title>

Page 158 of 248
</travellerInfo>
</PNR_Reply>


Page 159 of 248
5.30 Operation: Native name with Native Infant name

The infant has to be associated to another passenger, and is attached to the same /travellerInfo/
enhancedPassengerData/enhancedTravellerInformation element field quantity = 2.
The infant indicator must be set to 3, meaning that the infant has his proper surname and lastname.
Native name 김/지훈 will be used for the adult, 이/수진 for the infant, for illustration.
In the reply, the header flag RCH is displayed, as Native names are present in the PNR.
<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>2</number>
</reference>
<travellerNameInfo>
<type>ADT</type>
<title>MR</title>
<travellerNameInfo>
<type>INF</type>
<surname>이</surname>

Page 160 of 248
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>SEL6X0980</officeId>
<queueingOfficeId>SEL6X0980</queueingOfficeId>
<freetextData>
<freetextDetail>
<type>P12</type>
</freetextDetail>
<longFreetext>--- RCH---</longFreetext>
</freetextData>
<pnrHeaderTag>
<statusInformation>
<indicator>RCH</indicator>
</pnrHeaderTag>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>

Page 161 of 248
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>SEL6X0980</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>

Page 162 of 248
<passengerData>
<traveller>
</traveller>
<passenger>
<firstName>JI HUN MR</firstName>
<type>ADT</type>
</passenger>
</passengerData>
<passengerData>
<traveller>
<surname>LEE</surname>
</traveller>
<passenger>
<firstName>SU JIN</firstName>
<type>INF</type>
</passenger>
</passengerData>
<travellerNameInfo>

Page 163 of 248
<givenName>JI HUN</givenName>
<title>MR</title>
<travellerNameInfo>
<type>INF</type>
<surname>이</surname>
<surname>LEE</surname>
<givenName>SU JIN</givenName>
</travellerInfo>
</PNR_Reply>


Page 164 of 248
5.31 Operation: Open Segment

An Open Segment (SO) may be entered into the PNR for the purposes of ticketing and faring. No flight inventory
is adjusted. The process checks for format only. An Open segment may be included in both Group and Non
Group PNRs. Open segments are considered valid itinerary only when a PTA is present in the PNR. If no PTA
exists and the PNR contains only Open Segments without SA status code.
Example:
Airline 6X
Date 050213
City Pair BKK/LHR
Class of service Y

<pnrActions>
</pnrActions>
<originDestination>
<origin>BKK</origin>
<destination>LHR</destination>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>BKK</cityCode>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<company>

Page 165 of 248
</company>
<productDetails>
<identification>OPEN</identification>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>BKK6X0102</officeId>
<queueingOfficeId>BKK6X0102</queueingOfficeId>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>

Page 166 of 248
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>BKK6X0102</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>
<locationId>BKK</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry>TH</codedCountry>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>

Page 167 of 248
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>BKK</cityCode>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
<identification>OPEN</identification>
</productDetails>
</travelProduct>
<business>
</business>
<flightDetail>
<productDetails>
</productDetails>
</flightDetail>
</itineraryInfo>
</PNR_Reply>

If no off point is entered an error response is issued: CHECK CITY PAIR

Page 168 of 248
5.32 Operation: Original exchange document

This operation describes the addition of an FO element in the PNR.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>9</number>
</reference>
<segmentName>FO</segmentName>
<originalIssue>
<voucherIndicator>E</voucherIndicator>
<issue>
<airlineCode>220</airlineCode>
<documentNumber>2000000112</documentNumber>
<coupon1>2</coupon1>
<cityCode>FRA</cityCode>
<dateOfIssue>200508</dateOfIssue>
<iataNumber>23491193</iataNumber>
</issue>
</originalIssue>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 169 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>

Page 170 of 248
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FO</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>45</type>
</freetextDetail>
<longFreetext>220-2000000112FRA20MAY08/23491193/220-20000001125E2</longFreetext>
</PNR_Reply>

Page 171 of 248
5.33 Operation: Passive Segment

Passive booking enable you to ticket an itinerary which has been actively booked in a system other than
Amadeus, specifically for the purpose of transmitting the ticket number to the airline
For Passive segments:
• PK and PL action codes
Example:
Airline 6X
Date 050513
City Pair JFK/CDG
Class of service Y
Departure time 1200
Arrival time 1450
Record Locator PZTX7A

<pnrActions>
</pnrActions>
<originDestination>
<origin>JFK</origin>
<destination>CDG</destination>
<itineraryInfo>
<airAuxItinerary>
<travelProduct>
<product>

Page 172 of 248
</product>
<boardpointDetail>
<cityCode>JFK</cityCode>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<company>
</company>
<productDetails>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>PK</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
<reservation>
<controlNumber>PZTX7A</controlNumber>
</reservation>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>

Page 173 of 248
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 174 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>

Page 175 of 248
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<reservation>
<controlNumber>PZTX7A</controlNumber>
</reservation>
<relatedProduct>
<status>PK</status>
</relatedProduct>
<flightDetail>
<productDetails>
</productDetails>
<terminal>2E</terminal>
</flightDetail>
<selectionDetails>
<selection>
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
</itineraryInfo>

Page 176 of 248
</PNR_Reply>

? Record Locator missing: Error Information (ERC) ZZZ and Error Free From Text ( IFT) "NEED AGENT SIGN /
RECORD LOCATOR" ? Departure/arrival time missing whereas flight is not recorded in 1A: Error Information
(ERC) 134 Error Free From Text ( IFT) IFT "INPUT TIMES" ? On Altea airline: Error Information (ERC) ZZZ and
Error Free From Text ( IFT) "INVALID ACTION CODE FOR XX" ? On Ticketless acces carrier: Error Information
(ERC) ZZZ and Error Free From Text ( IFT) "CHECK ACTION CODE"

Page 177 of 248
5.34 Operation: Past Dated Segment

Past dated segment can be added using GK action code and it can be 999 days in the past maximum. Rloc is
not madatory because PAST will be displayed as Rloc in the replay.
Example:
Airline 7S
Date 230512
City Pair CDG/HEL
Class of service Y
Rloc ECJ93

<pnrActions>
</pnrActions>
<originDestination>
<origin>CDG</origin>
<destination>HEL</destination>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>

Page 178 of 248
<offpointDetail>
</offpointDetail>
<company>
</company>
<productDetails>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>GK</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
<reservation>
<controlNumber>ECJ93</controlNumber>
</reservation>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 179 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 180 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
</productDetails>
</travelProduct>

Page 181 of 248
<business>
</business>
<reservation>
<controlNumber>ECJ93</controlNumber>
</reservation>
<relatedProduct>
<status>GK</status>
<status>B</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>ECJ</equipment>
</productDetails>
<timeDetail>
<checkinTime>2316</checkinTime>
</timeDetail>
</flightDetail>
<selectionDetails>
<selection>
</selection>
</selectionDetails>
<itineraryFreetext>
<freetextDetail>
</freetextDetail>
<longFreetext>PASSIVE FLIGHT/CLASS DOES NOT MATCH PUBLISHED
SCHEDULE*WARNING: THIS SEGMENT IS 139 DAYS IN THE PAST </longFreetext>
</itineraryFreetext>
</itineraryInfo>
</message>

If the date specified in the entry is more than 999 days in the past, the application rejects the entry and generates
error message CHECK DATE. If Times have not been included in the input entry, then the input entry is rejected
with the message INPUT TIMES . Warning messages at sell time: "PASSIVE FLIGHT/CLASS DOES NOT

Page 182 of 248
MATCH PUBLISHED SCHEDULE" "WARNING : THIS SEGMENT IS nnn DAYS IN THE PAST" Warning at
end of transaction: ?WARNING : PAST DATED SEGMENT REMOVED?.

Page 183 of 248
5.35 Operation: Received From Information

The example below illustrates a received from information element:

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<freetextData>
<freetextDetail>
<type>P22</type>
</freetextDetail>
<longFreetext>internet/MUC1A0701</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>

Page 184 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>

Page 185 of 248
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<otherDataFreetext>
<freetextDetail>
<type>P22</type>
</freetextDetail>
<longFreetext>INTERNET/MUC6X0701</longFreetext>
</PNR_Reply>

Page 186 of 248
5.36 Operation: Seat Request

This example shows a seat request for a non-smoking aisle seat (NSSA).

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<segmentName>STR</segmentName>
<seatGroup>
<seatRequest>
<seat>
<type>NSSA</type>
</seat>
</seatRequest>
</seatGroup>
<reference>
<number>1</number>
</reference>
<reference>
<number>1</number>
</reference>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 187 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 188 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>

Page 189 of 248
</travellerInfo>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>

Page 190 of 248
<flightDetail>
<productDetails>
</productDetails>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
</itineraryInfo>
<dataElementsIndiv>
<reference>
<number>11</number>
</reference>
<serviceRequest>
<ssr>
<type>NSSA</type>
<status>NN</status>
<boardpoint>NCE</boardpoint>
<offpoint>CDG</offpoint>
</ssr>
<ssrb>
<crossRef>1</crossRef>
<seatType>N</seatType>
</ssrb>
</serviceRequest>
<reference>
<number>1</number>
</reference>
<reference>

Page 191 of 248
<number>1</number>
</reference>
</PNR_Reply>


Page 192 of 248
5.37 Operation: Service Fee

This example shows an example of a service fee paid using Master Card.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<formOfPayment>
<fop>
<identification>CC</identification>
<amount>30</amount>
<creditCardCode>CA</creditCardCode>
<accountNumber>5499840000000006</accountNumber>
<expiryDate>1205</expiryDate>
<currencyCode>EUR</currencyCode>
</fop>
</formOfPayment>
<serviceDetails>
<statusDetails>
<indicator>SV</indicator>
</statusDetails>
</serviceDetails>

Page 193 of 248
5.38 Operation: Service segment

Service segments can be included in a PNR to facilitate the ticketing process, when one or more segments
have been booked outside Amadeus. They are identified by the use of HK Action Code with an OA sign, which
are transmitted to the corresponding airlines when the PNR is filed (EOT), for action and information.
For Service segment:
• Use of HK in RPI segment (in Edifact message)
Example:
Airline 6X
Date 010513
City Pair MIA/JFK
Class of service Y
Rloc JM4AZ

<pnrActions>
</pnrActions>
<originDestination>
<origin>MIA</origin>
<destination>JFK</destination>
<itineraryInfo>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
<cityCode>MIA</cityCode>

Page 194 of 248
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<company>
</company>
<productDetails>
</productDetails>
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<selection>
<option>0</option>
</selection>
<reservation>
<controlNumber>JM4AZ</controlNumber>
</reservation>
</airAuxItinerary>
</itineraryInfo>

? Record Locator missing: Error Information (ERC) ZZZ and Error Free From Text ( IFT) "NEED AGENT SIGN /
RECORD LOCATOR" ? Departure/arrival time missing whereas flight is not recorded in 1A: Error Information
(ERC) 134 Error Free From Text ( IFT) IFT "INPUT TIMES" ? On Altea airline: Error Information (ERC) ZZZ
and Error Free From Text ( IFT) "INVALID ACTION CODE FOR XX"

Page 195 of 248
5.39 Operation: Simple Name

The example below illustrates a simple name request with the following information:
Traveler Surname CHIKKLES
Traveler First name BENJAMIN

<pnrActions>
</pnrActions>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
</passenger>
</passengerData>
</travellerInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 196 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 197 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
</traveller>
<passenger>
</passenger>
</passengerData>
<travellerNameInfo>
<givenName>MATHIEU</givenName>

Page 198 of 248
</travellerInfo>
</PNR_Reply>

Page 199 of 248
5.40 Operation: Single Flight

The following example below illustrates a request to reserve a flight with the following information:
Airline 7S
Flight Number 3278
Date 05/03/13
City Pair CDG to HEL
Class of service Y

<pnrActions>
</pnrActions>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<airAuxItinerary>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<company>
</company>
<productDetails>
</productDetails>

Page 200 of 248
</travelProduct>
<messageAction>
<business>
</business>
</messageAction>
<relatedProduct>
<status>NN</status>
</relatedProduct>
<selection>
</selection>
</airAuxItinerary>
</itineraryInfo>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>

Page 201 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 202 of 248
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
<equipment>E90</equipment>

Page 203 of 248
</productDetails>
<departTerminal>2D</departTerminal>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
<freetextDetail>
</freetextDetail>
</itineraryInfo>
</PNR_Reply>

RESTRICTED ACTION CODE if you try to sell an action code not authorized by the airline. CHECK CLASS
OF SERVICE if you try to sell the restricted class returns the message. CHECK FLIGHT NUMBER INVALID
CITY PAIR

Page 204 of 248
5.41 Operation: Special A.I.R remark

This example shows how to create aspecial A.I.R. remarks (RM*), note that the category isset to '*'.

<message type="PNRADD" agency="1A" version="12" release="2" >
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<remarks>
<type>RM</type>
<category>*</category>
<freetext>A.I.R Remark, use category for accounting remarks</freetext>
</remarks>
</message>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>

Page 205 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>

Page 206 of 248
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<remarks>
<type>RM</type>
<freetext>*A.I.R REMARK, USE CATEGORY FOR ACCOUNTING REMARKS</freetext>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
<category>*</category>
<freetext>A.I.R REMARK, USE CATEGORY FOR ACCOUNTING REMARKS</freetext>
</structuredRemark>
</extendedRemark>
</message>


Page 207 of 248
5.42 Operation: Structured Mailing

The example below illustrates a structured mailing address element including the following optional address
information:
Type Data
Name Dave Johnson
Address Line 1 1234 so. Main street
Address Line 2 Villa 9
City Atlanta
State Georgia
Zip Code 30039
Country USA
Note: a structured billing address will follow the same constraints asa mailing address. By simply changing the
segment name code to AB, the below example will illustrate a structured billing address.
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<segmentName>AM</segmentName>
<structuredAddress>
<address>
<optionA1>A1</optionA1>
<optionTextA1>1234 so main street</optionTextA1>
</address>
<optionalData>
<option>A2</option>
<optionText>villa 9</optionText>
</optionalData>
<optionalData>
<option>CI</option>
<optionText>Atlanta</optionText>
</optionalData>
<optionalData>
<option>CO</option>
<optionText>USA</optionText>
</optionalData>

Page 208 of 248
<optionalData>
<option>NA</option>
<optionText>Dave Johnson</optionText>
</optionalData>
<optionalData>
<option>ST</option>
<optionText>Georgia</optionText>
</optionalData>
<optionalData>
<option>ZP</option>
<optionText>30039</optionText>
</optionalData>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>

Page 209 of 248
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<travellerInfo>
<reference>
<number>1</number>
</reference>

Page 210 of 248
<passengerData>
<traveller>
</traveller>
<passenger>
<type>ADT</type>
</passenger>
</passengerData>
<travellerNameInfo>
<type>ADT</type>
</travellerInfo>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>
<product>

Page 211 of 248
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
</offpointDetail>
<companyDetail>
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
</productDetails>
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
</itineraryInfo>
<dataElementsIndiv>

Page 212 of 248
<reference>
<number>9</number>
</reference>
<segmentName>AM/</segmentName>
<structuredAddress>
<address>
<option>NA</option>
<optionText>DAVE JOHNSON</optionText>
</address>
<address>
<option>A1</option>
<optionText>1234 SO MAIN STREET</optionText>
</address>
<address>
<option>A2</option>
<optionText>VILLA 9</optionText>
</address>
<address>
<option>ZP</option>
<optionText>30039</optionText>
</address>
<address>
<option>CI</option>
<optionText>ATLANTA</optionText>
</address>
<address>
<option>ST</option>
<optionText>GEORGIA</optionText>
</address>
<address>
<option>CO</option>
<optionText>USA</optionText>
</address>
</PNR_Reply>

Page 213 of 248
5.43 Operation: Structured Remark

The example below illustrates a request for a remark creation.
This example is for a general remark (RM) but it applies in the same way for Itinerary and Invoice remarks.
Just replace RM by RIR, RII, RIF or RIZ
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>10</number>
</reference>
<extendedRemark>
<structuredRemark>
<type>RM</type>
<freetext>THIS IS A GENERAL REMARK</freetext>
</structuredRemark>
</extendedRemark>
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 214 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>

Page 215 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<remarks>
<type>RM</type>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
</PNR_Reply>


Page 216 of 248
5.44 Operation: Structured Remark with basic security

The example below illustrates a request for a secured remark creation.
In this example, no office is specified for the security. It means only the creator office will have access to the
remark (in read & write).
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>10</number>
</reference>
<extendedRemark>
<structuredRemark>
<type>RM</type>
<freetext>THIS IS A SECURED REMARK</freetext>
</structuredRemark>
</extendedRemark>
<accessLevel> </accessLevel>
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 217 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 218 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<remarks>
<type>RM</type>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
<accessLevel>
<securityDetails>
<typeOfEntity>O</typeOfEntity>
<inhouseIdentification>MUC6X0701</inhouseIdentification>
</securityDetails>
</accessLevel>
</PNR_Reply>

Page 219 of 248


Page 220 of 248
5.45 Operation: Structured Remark with corporate security

The example below illustrates a request for a corporate remark with Unicode characters and a category.
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>10</number>
</reference>
<extendedRemark>
<structuredRemark>
<type>RM</type>
<category>A</category>
<freetext>MR 김 지 훈 IS A VIP</freetext>
</structuredRemark>
</extendedRemark>
<serviceDetails>
<statusDetails>
<indicator>RX</indicator>
</statusDetails>
</serviceDetails>
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 221 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 222 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<remarks>
<type>RM</type>
<freetext>NOT DISPLAYABLE</freetext>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
<accessLevel>
<securityDetails>
<typeOfEntity>F</typeOfEntity>
</securityDetails>
</accessLevel>

Page 223 of 248
</PNR_Reply>


Page 224 of 248
5.46 Operation: Structured Remark with specific security

The example below illustrates a request for a secured remark creation.
In this example, the security is specified as follows:
- an office Id (NCE6X0980) with read & write access
- a Family (F-LON6X0100) with read access
It means NCE6X0980 and the creator office (MUC1A0701) will have access to the remark in read & write
mode and the Family (offices having FRX EOS agreement with LON6X0100) will have access in read only.
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>10</number>
</reference>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
<accessLevel>
<securityDetails>
<inhouseIdentification>NCE6X0980</inhouseIdentification>
</securityDetails>
<securityDetails>
<accessMode>R</accessMode>
<inhouseIdentification>LON6X0100</inhouseIdentification>
</securityDetails>
</accessLevel>

Page 225 of 248

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>

Page 226 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<remarks>
<type>RM</type>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>

Page 227 of 248
</extendedRemark>
<accessLevel>
<securityDetails>
</securityDetails>
</accessLevel>
<accessLevel>
<securityDetails>
<inhouseIdentification>NCE6X0980</inhouseIdentification>
</securityDetails>
</accessLevel>
<accessLevel>
<securityDetails>
<accessMode>R</accessMode>
<inhouseIdentification>LON6X0100</inhouseIdentification>
</securityDetails>
</accessLevel>
</PNR_Reply>


Page 228 of 248
5.47 Operation: Structured Timestamped Remark

NOTE THAT THIS OPTION IS NOT PART OF THE BASELINE REMARK PACKAGE.
The example below illustrates a request for a Timestamped remark with Unicode characters and a category.
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>10</number>
</reference>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
<serviceDetails>
<statusDetails>
<indicator>TS</indicator>
</statusDetails>
</serviceDetails>
<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 229 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 230 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<remarks>
<type>RM</type>
<freetext>NOT DISPLAYABLE</freetext>
</remarks>
<extendedRemark>
<structuredRemark>
<type>RM</type>
</structuredRemark>
</extendedRemark>
<eltPosDetails>
<pointOfSaleInformationType>
<pointOfSale>
<partyCodeQualifier>UPD</partyCodeQualifier>
</pointOfSale>
</pointOfSaleInformationType>
<sbrUserIdentification>

Page 231 of 248
</sbrUserIdentification>
<agentId>
<internalIdDetails>
<inhouseId>SU 0001AA</inhouseId>
<type>SGN</type>
</internalIdDetails>
</agentId>
<pointOfSaleDate>
<timeMode>LT</timeMode>
<dateTime>
<year>2012</year>
<month>1</month>
<day>25</day>
<hour>11</hour>
<minutes>38</minutes>
</dateTime>
</pointOfSaleDate>
</eltPosDetails>
</PNR_Reply>


Page 232 of 248
5.48 Operation: Ticketing Arrangement Element

The example below illustrates a request for a ticketing element with the following information:
Ticketing Type indicator Ticket Time Limit (TL)
Date of Ticketing 12/12/12

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<ticketElement>
<ticket>
<indicator>TL</indicator>
<date>121201</date>
</ticket>
</ticketElement>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>

Page 233 of 248
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<originatorTypeCode>E</originatorTypeCode>

Page 234 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<ticketElement>
<ticket>
<indicator>TL</indicator>
<date>121212</date>
</ticket>
</ticketElement>
</PNR_Reply>


Page 235 of 248
5.49 Operation: Tour Code in Free Flow Format

The example below illustrates the request to create a tour code in free flow format.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FT</segmentName>
<tourCode>
<freeFormatTour>
<indicator>FF</indicator>
<freetext>TOUR CODE</freetext>
</freeFormatTour>
</tourCode>

<pnrHeader>
<reservationInfo>
<reservation>
</reservation>
</reservationInfo>
</pnrHeader>
<officeId>NCE6X0100</officeId>

Page 236 of 248
<queueingOfficeId>NCE6X0100</queueingOfficeId>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<inHouseIdentification1>NCE6X0100</inHouseIdentification1>
<sbrSystemDetails>
<deliveringSystem>

Page 237 of 248
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>FT</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>12</type>
</freetextDetail>
<longFreetext>PAX \*TOUR CODE</longFreetext>
</PNR_Reply>


Page 238 of 248
5.50 Operation: UnStructured Mailing and Billing Addresses

The example below illustrates an unstructured mailing address element including free form address text
information in the following desired printable format:
Dave Johnson
1234 so main street
Atlanta GA 30039
USA
Note: an unstructured billing address will follow the same constraints as a mailing address. By simply changing
the segment name code to ABU, the below example will illustrate an unstructured billing address.

<pnrActions>
</pnrActions>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>AMU</segmentName>
<freetextData>
<freetextDetail>
<type>P08</type>
</freetextDetail>
<longFreetext>Dave Johnson, 1234 so main street, Atlanta GA 30039, USA</longFreetext>
</freetextData>

<pnrHeader>
<reservationInfo>
<reservation>

Page 239 of 248
</reservation>
</reservationInfo>
</pnrHeader>
<sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>

Page 240 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<dataElementsIndiv>
<reference>
<number>1</number>
</reference>
<segmentName>AM</segmentName>
<otherDataFreetext>
<freetextDetail>
<type>P08</type>
</freetextDetail>
<longFreetext>DAVE JOHNSON, 1234 SO MAIN STREET, ATLANTA GA 30039,
USA</longFreetext>
</PNR_Reply>

Page 241 of 248
5.51 Operation: Upgrade

The example below show a SSR FQTU.
Note:
All the information is added in the freetext (for what concerns edifact respectively XML, no FTI segment
respectively frequentTravellerData tag follows SSR FQTU segment).
In the reply some flights appears to provide a complete example.

<reservationInfo>
<reservation>
<controlNumber>52A345</controlNumber>
</reservation>
</reservationInfo>
<pnrActions>
</pnrActions>
<dataElementsIndiv>
<serviceRequest>
<ssr>
<type>FQTU</type>
<freetext> QF1117622/CN-12345</freetext>
</ssr>
</serviceRequest>
<pnrHeader>
<reservationInfo>
<reservation>
<date>311012</date>
<time>1129</time>
</reservation>
</reservationInfo>
</pnrHeader>

Page 242 of 248
<agentId>AASU</agentId>
<officeId>NYXX02001</officeId>
<queueingOfficeId>NYXX02001</queueingOfficeId>
<cityCode>NYC</cityCode>
<secondRpInformation>
<creationOfficeId>NYXX02001</creationOfficeId>
<agentSignature>1234AA</agentSignature>
<creationDate>311012</creationDate>
<creatorIataCode>12345675</creatorIataCode>
<creationTime>1129</creationTime>
</secondRpInformation>
<freetextData>
<freetextDetail>
<type>P12</type>
</freetextDetail>
<longFreetext>--- RLR ---</longFreetext>
</freetextData>
<sbrPOSDetails>
<inHouseIdentification1>NYXX02001</inHouseIdentification1>
<originatorTypeCode>T</originatorTypeCode>
<sbrSystemDetails>
<deliveringSystem>
<locationId>NYC</locationId>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
<codedCountry>US</codedCountry>
</userPreferences>
</sbrPreferences>
</sbrPOSDetails>

Page 243 of 248
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<sbrSystemDetails>
<deliveringSystem>
</deliveringSystem>
</sbrSystemDetails>
<sbrPreferences>
<userPreferences>
</userPreferences>
</sbrPreferences>
<technicalData>
<enveloppeNumberData>
<sequenceDetails>
<number>1</number>
</sequenceDetails>
</enveloppeNumberData>
<lastTransmittedEnvelopeNumber>
<currentRecord>0</currentRecord>

Page 244 of 248
</lastTransmittedEnvelopeNumber>
<purgeDateData>
<dateTime>
<year>2012</year>
<month>12</month>
<day>21</day>
</dateTime>
</purgeDateData>
<generalPNRInformation>
<statusDetails>
<isPNRModifDuringTrans>MOD</isPNRModifDuringTrans>
</statusDetails>
</generalPNRInformation>
</technicalData>
<travellerInfo>
<reference>
<number>1</number>
</reference>
<passengerData>
<traveller>
<surname>ABOUD</surname>
</traveller>
<passenger>
<firstName>RUSSEL</firstName>
</passenger>
</passengerData>
</travellerInfo>
<itineraryInfo>
<reference>
<number>1</number>
</reference>
<travelProduct>

Page 245 of 248
<product>
<dayChangeIndicator>2</dayChangeIndicator>
</product>
<boardpointDetail>
</boardpointDetail>
<offpointDetail>
<cityCode>SYD</cityCode>
</offpointDetail>
<companyDetail>
<identification>QF</identification>
</companyDetail>
<productDetails>
</productDetails>
<typeDetail>
<detail>ET</detail>
</typeDetail>
</travelProduct>
<business>
</business>
<reservation>
</reservation>
<relatedProduct>
<status>HK</status>
</relatedProduct>
<flightDetail>
<productDetails>
</productDetails>

Page 246 of 248
</flightDetail>
<selectionDetails>
<selection>
<option>P2</option>
</selection>
</selectionDetails>
</itineraryInfo>
<dataElementsIndiv>
<reference>
<number>3</number>
</reference>
<otherDataFreetext>
<freetextDetail>
<type>5</type>
</freetextDetail>
<longFreetext>1234</longFreetext>
<dataElementsIndiv>
<reference>
<number>9</number>
</reference>
<ticketElement>
<ticket>
<indicator>OK</indicator>
<date>311012</date>
<officeId>NYXX02001</officeId>
</ticket>
</ticketElement>
<dataElementsIndiv>

Page 247 of 248
<reference>
<number>26</number>
</reference>
<serviceRequest>
<ssr>
<type>FQTU</type>
<status>HK</status>
<freeText>QF1117622/QF1117622/CN-12345</freeText>
</ssr>
</serviceRequest>
<reference>
<number>1</number>
</reference>
<reference>
<number>1</number>
</reference>
</PNR_Reply>

DUPLICATE EXISTS TARGET AIRLINE MISSING CARD AIRLINE MISSING FF NUMBER MISSING NO AIR
SEGMENTS PASSENGER AND_OR SEGMENT DATA NOT VALID SSR ITEM TOO LONG INVALID ACTION
CODE INVALID NIP (NIP=Number In Party) NO AGREEMENT BETWEEN CN TOO LONG (CN=certificate
number) PC TOO LONG (PC= promotion code) UQ TOO LONG (UQ=upgrade qualifier) AC TOO LONG
(AC=award code) NO EOT UPGRADE CLASS INVALID UPGRADE CLASS MISSING

Page 248 of 248

UG WBS PNR AddMultiElements 12.2 194

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

UG WBS PNR AddMultiElements 12.2 194

Cargado por

Copyright:

Formatos disponibles

Web Services User's Guide

5.2.3 Possible Errors ...............................................................................................................................................................42

5.10.3 Possible Errors .............................................................................................................................................................78

5.18.3 Possible Errors .......................................................................................................................................................... 116

5.26.3 Possible Errors .......................................................................................................................................................... 147

5.34.3 Possible Errors .......................................................................................................................................................... 182

5.42.3 Possible Errors .......................................................................................................................................................... 213

5.50.3 Possible Errors .......................................................................................................................................................... 241

5.51 Operation: Upgrade ................................................................................................................. 242

1 Purpose of this document

4 Structure of this document

Copyright © 1987-2013 Amadeus IT Group SA.

Copyright © 1987-2013 Amadeus IT Group SA.

1.1 Supported Operations

Adding Itinerary Elements

Copyright © 1987-2013 Amadeus IT Group SA.

Copyright © 1987-2013 Amadeus IT Group SA.

Used to store applicable frequent flyer numbers for travelers.

Adding Seat Elements

Copyright © 1987-2013 Amadeus IT Group SA.

Option Code Description

Option code Description

Option code Description

Copyright © 1987-2013 Amadeus IT Group SA.

Other Service Information (OSI)

1.3 Unsupported Operations

Copyright © 1987-2013 Amadeus IT Group SA.

Copyright © 1987-2013 Amadeus IT Group SA.

2.1 Query Sub Structure:

2.1.2 Xml Structure

Copyright © 1987-2013 Amadeus IT Group SA.

Copyright © 1987-2013 Amadeus IT Group SA.

Miscellaneous Date Elements

Copyright © 1987-2013 Amadeus IT Group SA.

Copyright © 1987-2013 Amadeus IT Group SA.

Adult with Companion CN --

Copyright © 1987-2013 Amadeus IT Group SA.

Remark Type Code

Mailing & Billing Address Information

Type Definition Segment Name Code

Code Option Max Number of characters

Copyright © 1987-2013 Amadeus IT Group SA.

Type of Address Type Code

Free Form Text Entered Printed Format on Amadeus Generated Documents

Copyright © 1987-2013 Amadeus IT Group SA.

Ticketing Type Code

3.1 Reply Sub Structure:

3.1.2 Xml Structure

Copyright © 1987-2013 Amadeus IT Group SA.

3499 AIR SEGMENT REQUIRED WITH TICKETING

Copyright © 1987-2013 Amadeus IT Group SA.

4759 CHECK DATE OF BIRTH

12495 IF A DATE WAS ENTERED: CHECK IF DATE IS

Copyright © 1987-2013 Amadeus IT Group SA.

6139 INVALID ACCESS MODE. MUST BE R,T,B OR N

Copyright © 1987-2013 Amadeus IT Group SA.

9381 INVALID PSEUDO OFFICE ID : id

Copyright © 1987-2013 Amadeus IT Group SA.

3528 MAXIMUM OF 7 REQUESTS PERMITTED FOR

Copyright © 1987-2013 Amadeus IT Group SA.

1899 OSI/SSR EXCEED MAXIMUM ELEMENTS

12061 RESTRICTED FOP FOR PASSENGER

6134 RESTRICTED - YOUR OFFICE IS NOT