Ug_wbs_pnr_addmultielements_12.2_194 (3).docx

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

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 10 of 248

Web services User guide for function PNR_AddMultiElements

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:

Copyright © 1987-2013 Amadeus IT Group SA. Page 11 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 12 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 13 of 248

Web services User guide for function PNR_AddMultiElements

• • • • • • • • • •

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 14 of 248

Web services User guide for function PNR_AddMultiElements

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.

Copyright © 1987-2013 Amadeus IT Group SA. Page 15 of 248

Web services User guide for function PNR_AddMultiElements

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 (‘.’, ’-’, ’_’).

Copyright © 1987-2013 Amadeus IT Group SA. Page 16 of 248

Web services User guide for function PNR_AddMultiElements

• 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

Copyright © 1987-2013 Amadeus IT Group SA. Page 17 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 18 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 19 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 20 of 248

Web services User guide for function PNR_AddMultiElements

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 Required

ZS

Date of Birth/Age in Yrs

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.

Copyright © 1987-2013 Amadeus IT Group SA. Page 21 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 22 of 248

Web services User guide for function PNR_AddMultiElements

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 Mr. John Smith, 124 south Hampton, Atlanta GA 30039

Printed Format on Amadeus Generated Documents Mr. John Smith 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.

Copyright © 1987-2013 Amadeus IT Group SA. Page 23 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 24 of 248

Web services User guide for function PNR_AddMultiElements

4 Error Messages IATA error codes and messages 103 102

CHECK ARRIVAL/DEPARTURE DATE 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 Copyright © 1987-2013 Amadeus IT Group SA. Page 25 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 26 of 248

Web services User guide for function PNR_AddMultiElements

6139

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

56 3325

INVALID ACTION CODE 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 1987

INVALID PASSENGER TYPE INVALID PASSENGER/SEGMENT SELECT - PNR OVERLAP Copyright © 1987-2013 Amadeus IT Group SA. Page 27 of 248

Web services User guide for function PNR_AddMultiElements

9381

INVALID PSEUDO OFFICE ID : id

9378

INVALID RECEIVER TYPE. MUST BE : G, I OR P

1929

INVALID RECORD LOCATOR

1919 6362

INVALID REQUEST FOR ELEMENT 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 11648

KEYWORD INACTIVE 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 CREATED FOR THIS AIRLINE

7590

MANUAL TAXI SEGMENTS CANNOT BE CREATED FOR THIS AIRLINE

7587

MANUAL TOUR SEGMENTS CANNOT BE CREATED FOR THIS AIRLINE

6136

MAXIMUM ALLOWED IS 5 RECEIVERS

5443

MAXIMUM FREEFLOW EXCEEDED

11376

MAXIMUM OF 5 SUB TYPE CATEGORIES CAN BE ENTERED

Copyright © 1987-2013 Amadeus IT Group SA. Page 28 of 248

Web services User guide for function PNR_AddMultiElements

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 3550

NEED RECEIVED FROM 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 Copyright © 1987-2013 Amadeus IT Group SA. Page 29 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 30 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 31 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 32 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 33 of 248

Web services User guide for function PNR_AddMultiElements

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 Copyright © 1987-2013 Amadeus IT Group SA. Page 34 of 248

Web services User guide for function PNR_AddMultiElements

9527

WARNING: UNCONFIRMED INSURANCE PRESENT - PLS CONFIRM

21932

WARNING: OA CONTROLLED PNR

4466

WARNING: CHECK QUEUEING OFFICE

2463 Note: TBD stands for to be defined.

WARNING: STATUS WILL REVERT TO NN FOR:

4.1 Error Reply

Copyright © 1987-2013 Amadeus IT Group SA. Page 35 of 248

Web services User guide for function PNR_AddMultiElements

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 0 <elementManagementData> OT 1 <segmentName>AI DEC001029 DV123 DEC038FR LOFKFD122

5.1.2 Reply Structure

1A

Copyright © 1987-2013 Amadeus IT Group SA. Page 36 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 37 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>PRICING 1 <passenger> A ADT <marker2> <elementManagementData> OT 4 Copyright © 1987-2013 Amadeus IT Group SA. Page 38 of 248

Web services User guide for function PNR_AddMultiElements

<segmentName>AI 2 DEC001029 DV123 DEC038FR LOFKFD122 PT 1

5.1.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 39 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.2.1 Query Structure 0 <elementManagementItinerary> <segmentName>AIR <productDetails> ARNK <messageAction> 0

5.2.2 Reply Structure 1A <securityInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 40 of 248

Web services User guide for function PNR_AddMultiElements

RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 41 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementItinerary> ST 1 <segmentName>AIR 1 <productDetails> ARNK <processingIndicator>N 1 <markerRailTour>

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 42 of 248

Web services User guide for function PNR_AddMultiElements

5.3 Operation: Confidential Remark The example below illustrates a request for a confidential remark.

5.3.1 Query Structure 0 <elementManagementData> OT 13 <segmentName>RC <miscellaneousRemark> RC CONFIDENTIAL REMARK FREE TEXT

5.3.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 43 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC Copyright © 1987-2013 Amadeus IT Group SA. Page 44 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 2 <segmentName>RC 1 <miscellaneousRemarks> RC CONFIDENTIAL REMARK FREE TEXT 06686737 B

5.3.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 45 of 248

Web services User guide for function PNR_AddMultiElements

5.4 Operation: Connection Flight The following example below illustrates a request to reserve connection flight: Parameter

Information

Airline

7S

Flight Number (1)

1288

Date

17/05/13

City Pair

AMS/LHR

Class of service

K

Flight Number (2)

1286

Date

17/05/13

City Pair

LHR/LAX

Class of service

B

Airline

6X

Flight Number (3)

4690

Date

17/05/13

City Pair

LAX/SCL

Class of service

Y

Number of seats to reserve

1

5.4.1 Query Structure 0 AMS <destination>SLC <elementManagementItinerary> <segmentName>AIR <product> <depDate>170513 Copyright © 1987-2013 Amadeus IT Group SA. Page 46 of 248

Web services User guide for function PNR_AddMultiElements

AMS LHR 7S <productDetails> 1288 K <messageAction> 1 1 <status>NN <selectionDetailsAir> <selection> 0 <elementManagementItinerary> <segmentName>AIR <product> <depDate>170513 LHR LAX 7S Copyright © 1987-2013 Amadeus IT Group SA. Page 47 of 248

Web services User guide for function PNR_AddMultiElements

<productDetails> 1286 B <messageAction> 1 1 <status>NN <selectionDetailsAir> <selection> 0 <elementManagementItinerary> <segmentName>AIR <product> <depDate>210513 LAX SLC 6X <productDetails> 4690 Y <messageAction> Copyright © 1987-2013 Amadeus IT Group SA. Page 48 of 248

Web services User guide for function PNR_AddMultiElements

1 1 <status>NN <selectionDetailsAir> <selection> 0

5.4.2 Reply Structure 1A <securityInformation> RP CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 49 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 CDG7S0001 A <sbrSystemDetails> <deliveringSystem> 7S CDG <sbrPreferences> <userPreferences> FR <elementManagementItinerary> Copyright © 1987-2013 Amadeus IT Group SA. Page 50 of 248

Web services User guide for function PNR_AddMultiElements

ST 1 <segmentName>AIR 1 <product> <depDate>170513 <depTime>1630 <arrDate>170513 <arrTime>1730 AMS LHR 7S <productDetails> 1288 K <detail>ET 1 1 <status>HL <productDetails> <equipment>77W 0 <weekDay>5 <arrivalStationInfo> Copyright © 1987-2013 Amadeus IT Group SA. Page 51 of 248

Web services User guide for function PNR_AddMultiElements

2 <selectionDetails> <selection> P2 <subjectQualifier>3 SEE RTSVC WARNING - WAIT LIST <markerRailTour> <elementManagementItinerary> ST 2 <segmentName>AIR 2 <product> <depDate>170513 <depTime>1830 <arrDate>170513 <arrTime>2200 LHR LAX 7S <productDetails> 1286 B Copyright © 1987-2013 Amadeus IT Group SA. Page 52 of 248

Web services User guide for function PNR_AddMultiElements

<detail>ET 1 1 <status>HL <productDetails> <equipment>77W 0 <weekDay>5 <departureInformation> <departTerminal>2 <arrivalStationInfo> 2 <selectionDetails> <selection> P2 <subjectQualifier>3 SEE RTSVC WARNING - WAIT LIST <markerRailTour> <elementManagementItinerary> ST 3 <segmentName>AIR 3 Copyright © 1987-2013 Amadeus IT Group SA. Page 53 of 248

Web services User guide for function PNR_AddMultiElements

<product> <depDate>210513 <depTime>0740 <arrDate>210513 <arrTime>1030 LAX SLC 6X <productDetails> 4690 Y 1 1 <status>HK <productDetails> <equipment>CR9 0 <weekDay>2 <departureInformation> <departTerminal>5 <arrivalStationInfo> 2 <selectionDetails> <selection> P2 Copyright © 1987-2013 Amadeus IT Group SA. Page 54 of 248

Web services User guide for function PNR_AddMultiElements

<subjectQualifier>3 6X CONX/QUOTE AS SKYWEST AIRLINES 13\ \ WI-FI 6\ \ SKY PRIORI OPERATED BY SUBSIDIARY/FRANCHISE SEE RTSVC <markerRailTour> <segmentGroupingInfo> CNX <marriageDetail> 1 <marriageDetail> 2 <marriageDetail> 3

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 55 of 248

Web services User guide for function PNR_AddMultiElements

5.5 Operation: Contact Information The example below illustrates the request for an agency contact element with the following information: Parameter

Information

Phone Number

04.92.94.70.00

Agency contact indicator

AGCY

5.5.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>AP <subjectQualifier>3 6 04.92.94.70.00 - AGCY

5.5.2 Reply Structure 1A <securityInformation> RP Copyright © 1987-2013 Amadeus IT Group SA. Page 56 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 57 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 1 <segmentName>AP 1 <subjectQualifier>3 6 04.92.94.70.00 - AGCY

5.5.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 58 of 248

Web services User guide for function PNR_AddMultiElements

5.6 Operation: Creating an OSI with Mandatory Airline Code This example shows how to create an OSI including mandatory airline code 6X:

5.6.1 Query Structure 0 <elementManagementData> <segmentName>OS <subjectQualifier>3 P27 6X 6X FB00S7 B744 UMLAUF71343

5.6.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 59 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 60 of 248

Web services User guide for function PNR_AddMultiElements

DE <marker2> <elementManagementData> OT 1 <segmentName>OS 1 <subjectQualifier>3 28 6X 6X FB00S7 B744 UMLAUF71343

5.6.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 61 of 248

Web services User guide for function PNR_AddMultiElements

5.7 Operation: E-mail The example below illustrates the request for an EMAIL contact element with the following information: Parameter

Information

E-mail Contact

[email protected]

Agency contact indicator

- EMAIL

5.7.1 Query Structure 0 <elementManagementData> <segmentName>AP <subjectQualifier>3 P02 [email protected]

5.7.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 62 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC Copyright © 1987-2013 Amadeus IT Group SA. Page 63 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 2 <segmentName>AP 1 <subjectQualifier>3 P02 [email protected]

5.7.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 64 of 248

Web services User guide for function PNR_AddMultiElements

5.8 Operation: End Of Transaction To end transact the PNR using options mentioned in supported operations paragrah

5.8.1 Query Structure 11 <marker1> <elementManagementData> <segmentName>RF <subjectQualifier>3 P22 RF ADDED VIA PNRADD

5.8.2 Reply Structure 1A 5YEJBW 251012 1005 <securityInformation> RP BMPR MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 65 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 DAP <secondRpInformation> MUC6X0701 1234BM 251012 1005 <subjectQualifier>3 P12 --- RLR --- <sbrPOSDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <sbrCreationPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 66 of 248

Web services User guide for function PNR_AddMultiElements

1A MUC <sbrPreferences> <userPreferences> DE <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <enveloppeNumberData> <sequenceDetails> 1 <currentRecord>0 2013 <month>1 28 Copyright © 1987-2013 Amadeus IT Group SA. Page 67 of 248

Web services User guide for function PNR_AddMultiElements

<elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>GOLD 1 <passenger> GOLD MISS ADT ID1 <elementManagementItinerary> ST 1 <segmentName>AIR 2 <product> <depDate>280113 <depTime>1000 <arrDate>280113 <arrTime>1100 NCE CDG Copyright © 1987-2013 Amadeus IT Group SA. Page 68 of 248

Web services User guide for function PNR_AddMultiElements

6X <productDetails> 9996 Y <detail>ET 1 1 <status>HK <productDetails> <equipment>744 0 <weekDay>1 <selectionDetails> <selection> P2 <markerRailTour> <marker2> <elementManagementData> OT 2 <segmentName>AP 3 Copyright © 1987-2013 Amadeus IT Group SA. Page 69 of 248

Web services User guide for function PNR_AddMultiElements

<subjectQualifier>3 5 CONTACT ADDED VIA PNRADD <elementManagementData> <segmentName>RF <subjectQualifier>3 P22 RF ADDED VIA PNRADD <elementManagementData> OT 4 <segmentName>TK 4 OK 280113 MUC6X0701

5.8.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 70 of 248

Web services User guide for function PNR_AddMultiElements

5.9 Operation: Extra Seat The example below illustrates a simple name request for an extra seat with the following information: Parameter

Information

Traveler Surname

CHIKKLES

Traveler First name

JOHN

Extra Seat Qualifier

E

5.9.1 Query Structure 0 <elementManagementPassenger> PR 1 <segmentName>NM <passengerData> <surname>CHIKKLES E 1 <passenger> JOHN

5.9.2 Reply Structure 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 71 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 72 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>CHIKKLES 1 <passenger> JOHN <elementManagementPassenger> PT 2 <segmentName>NM 2 <passengerData> Copyright © 1987-2013 Amadeus IT Group SA. Page 73 of 248

Web services User guide for function PNR_AddMultiElements

<surname>CHIKKLES 1 <passenger> EXST

5.9.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 74 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.10.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>FD CH 10

5.10.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 75 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A NCE Copyright © 1987-2013 Amadeus IT Group SA. Page 76 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> FR <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>TEST 1 <passenger> PAX CHD <enhancedPassengerData> <enhancedTravellerInformation> 1 CHD UN Y Y <surname>TEST PAX <marker2> <elementManagementData> Copyright © 1987-2013 Amadeus IT Group SA. Page 77 of 248

Web services User guide for function PNR_AddMultiElements

OT 3 <segmentName>FD 2 <subjectQualifier>3 P04 CH10

5.10.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 78 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.11.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>FD CH 010203

5.11.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 79 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A NCE Copyright © 1987-2013 Amadeus IT Group SA. Page 80 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> FR <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>TEST 1 <passenger> PAX CHD <enhancedPassengerData> <enhancedTravellerInformation> 1 CHD UN Y Y <surname>TEST PAX <marker2> Copyright © 1987-2013 Amadeus IT Group SA. Page 81 of 248

Web services User guide for function PNR_AddMultiElements

<elementManagementData> OT 3 <segmentName>FD 2 <subjectQualifier>3 P04 CH01FEB03

5.11.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 82 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.12.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>FD <passengerType>PAX CD 10

5.12.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 83 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A NCE Copyright © 1987-2013 Amadeus IT Group SA. Page 84 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> FR <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>TEST 1 <passenger> PAX <enhancedPassengerData> <enhancedTravellerInformation> 1 UN Y Y <surname>TEST PAX <marker2> <elementManagementData> Copyright © 1987-2013 Amadeus IT Group SA. Page 85 of 248

Web services User guide for function PNR_AddMultiElements

OT 3 <segmentName>FD 2 <subjectQualifier>3 P04 PAX CD10

5.12.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 86 of 248

Web services User guide for function PNR_AddMultiElements

5.13 Operation: Fax Number The example below illustrates the request for a fax contact element with the following information: Parameter

Information

Fax Number

04.92.93.44.99

Agency contact indicator

- FAX

5.13.1 Query Structure 0 <elementManagementData> OT 16 <segmentName>AB <structuredAddress> P01

A1 04.92.93.44.99

5.13.2 Reply Structure 1A <securityInformation> RP Copyright © 1987-2013 Amadeus IT Group SA. Page 87 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 88 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>PRICING 1 <passenger> A ADT <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT UN Y Y <surname>PRICING A Copyright © 1987-2013 Amadeus IT Group SA. Page 89 of 248

Web services User guide for function PNR_AddMultiElements

<marker2> <elementManagementData> OT 4 <segmentName>AB/ 2 <structuredAddress> 2

A1 04.92.93.44.99

5.13.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 90 of 248

Web services User guide for function PNR_AddMultiElements

5.14 Operation: Form of Payment Used to specify the form of payment for a ticket.

5.14.1 Query Structure 0 <marker1> <elementManagementData> <segmentName>FP CC VI 4444333322221111 <expiryDate>1212 1 123

5.14.2 Reply Structure <message type="PNRACC" agency="1A" version="12" release="2" > 1A <securityInformation> RP MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 91 of 248

Web services User guide for function PNR_AddMultiElements

20263051 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 20263051 MUC6X0701 N Copyright © 1987-2013 Amadeus IT Group SA. Page 92 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A PAR <sbrPreferences> <userPreferences> FR <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>TEST 1 <passenger> JRL <enhancedPassengerData> <enhancedTravellerInformation> <marker2> <elementManagementData> OT 3 <segmentName>FP 2 Copyright © 1987-2013 Amadeus IT Group SA. Page 93 of 248

Web services User guide for function PNR_AddMultiElements

<subjectQualifier>3 16 CCVI4444333322221111D1213*CV

5.14.3 Possible Errors 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.

Copyright © 1987-2013 Amadeus IT Group SA. Page 94 of 248

Web services User guide for function PNR_AddMultiElements

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 Parameter

Information

FQTV Airline

QF

Membership Number

QF1117622

Passenger Association

Passenger element number 1

5.15.1 Query Structure 0 <elementManagementData> PT 1 <segmentName>SSR <serviceRequest> <ssr> FQTV QF P01 QF <membershipNumber>QF1117622 Copyright © 1987-2013 Amadeus IT Group SA. Page 95 of 248

Web services User guide for function PNR_AddMultiElements

PT 1

5.15.2 Reply Structure 1A 1A 9D5NU8 F <securityInformation> RP MUC6X0701 12345675 MUC6X0701 <subjectQualifier>3 P12 --- NHP --- <statusInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 96 of 248

Web services User guide for function PNR_AddMultiElements

NHP <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 MUC6X0701 E <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 97 of 248

Web services User guide for function PNR_AddMultiElements

1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>ABOUD 1 <passenger> RUSSEL MR ADT ID1 <enhancedPassengerData> <enhancedTravellerInformation> <elementManagementItinerary> ST 1 <segmentName>AIR 2 Copyright © 1987-2013 Amadeus IT Group SA. Page 98 of 248

Web services User guide for function PNR_AddMultiElements

<product> <depDate>100313 <depTime>1950 <arrDate>110313 <arrTime>0725 1 NRT SYD QF <productDetails> 22 Y <detail>ET 1 2 <status>HK <productDetails> <equipment>744 0 <weekDay>7 <departureInformation> <departTerminal>2 <arrivalStationInfo> 1 Copyright © 1987-2013 Amadeus IT Group SA. Page 99 of 248

Web services User guide for function PNR_AddMultiElements

<selectionDetails> <selection> P2 <subjectQualifier>3 ADV PAX WWW.SMARTRAVELLER.GOV.AU SEE RTSVC <markerRailTour> <marker2> <elementManagementData> OT 3 <segmentName>SSR 3 <serviceRequest> <ssr> FQTV <status>HK 1 QF P02 QF <membershipNumber>1117622 <priorityDetails> 1 <priorityCode>1 CLPO <priorityDetails> Copyright © 1987-2013 Amadeus IT Group SA. Page 100 of 248

Web services User guide for function PNR_AddMultiElements

2 <priorityCode>1 EMER EMERALD PT 1 <elementManagementData> OT 7 <segmentName>SK 4 <serviceRequest> <ssr> ACIM <status>HK 1 QF 61403585400 PT 1

5.15.3 Possible Errors 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 Copyright © 1987-2013 Amadeus IT Group SA. Page 101 of 248

Web services User guide for function PNR_AddMultiElements

5.16 Operation: General Remark The example below illustrates a request for a general miscellaneous remark.

5.16.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>RM <miscellaneousRemark> RM GENERAL REMARK

5.16.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 102 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC Copyright © 1987-2013 Amadeus IT Group SA. Page 103 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 2 <segmentName>RM 1 <miscellaneousRemarks> RM GENERAL REMARK <extendedRemark> <structuredRemark> RM GENERAL REMARK

5.16.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 104 of 248

Web services User guide for function PNR_AddMultiElements

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

Information

Airline

7S

Flight Number (1)

3278

Date

020413

City Pair

CDG/HEL

Class of service

Y

Number of seats to reserve

1

Rloc

5O911

5.17.1 Query Structure 0 CDG <destination>HEL <elementManagementItinerary> SR 1 <segmentName>AIR <product> <depDate>020413 <depTime>1100 <arrDate>020413 <arrTime>1400 Copyright © 1987-2013 Amadeus IT Group SA. Page 105 of 248

Web services User guide for function PNR_AddMultiElements

CDG HEL 7S <productDetails> 3278 Y <messageAction> 1 1 <status>GK <selectionDetailsAir> <selection> 0 5O911

5.17.2 Reply Structure 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 106 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 107 of 248

Web services User guide for function PNR_AddMultiElements

12345675 CDG7S0001 A <sbrSystemDetails> <deliveringSystem> 7S CDG <sbrPreferences> <userPreferences> FR <elementManagementItinerary> ST 1 <segmentName>AIR 1 <product> <depDate>120413 <depTime>1100 <arrDate>120413 <arrTime>1400 CDG HEL 7S <productDetails> 3278 Copyright © 1987-2013 Amadeus IT Group SA. Page 108 of 248

Web services User guide for function PNR_AddMultiElements

Y 1 7S SICVYY 1 <status>GK <productDetails> <equipment>E90 0 <weekDay>5 <departureInformation> <departTerminal>2D <arrivalStationInfo> 2 1015 <selectionDetails> <selection> P10 <subjectQualifier>3 SEE RTSVC <markerRailTour> Copyright © 1987-2013 Amadeus IT Group SA. Page 109 of 248

Web services User guide for function PNR_AddMultiElements



5.17.3 Possible Errors ? 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"

Copyright © 1987-2013 Amadeus IT Group SA. Page 110 of 248

Web services User guide for function PNR_AddMultiElements

5.18 Operation: Group Name The example below illustrates a group name with 2 travelers containing the following information: Parameter

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.

5.18.1 Query Structure 0 <elementManagementPassenger> <segmentName>NG <passengerData> <surname>MARTIEN GROUP G 10 <elementManagementPassenger> PR 1 <segmentName>NM <passengerData> <surname>CHILDS Copyright © 1987-2013 Amadeus IT Group SA. Page 111 of 248

Web services User guide for function PNR_AddMultiElements

1 <passenger> LISA <elementManagementPassenger> PR 2 <segmentName>NM <passengerData> <surname>CHIKKLES 1 <passenger> ROBERT

5.18.2 Reply Structure 1A <securityInformation> RP MUC6X0701 12345675 MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 112 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC Copyright © 1987-2013 Amadeus IT Group SA. Page 113 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> DE <elementManagementPassenger> <segmentName>NG 0 <passengerData> <surname>MARTIEN GROUP G 10 10 BKD 0 CNL 0 SPL <elementManagementPassenger> PT 3 <segmentName>NM 1 <passengerData> Copyright © 1987-2013 Amadeus IT Group SA. Page 114 of 248

Web services User guide for function PNR_AddMultiElements

<surname>CHIKKLES 1 <passenger> ROBERT <enhancedPassengerData> <enhancedTravellerInformation> 1 UN Y Y <surname>CHIKKLES ROBERT <elementManagementPassenger> PT 2 <segmentName>NM 2 <passengerData> <surname>CHILDS 1 <passenger> LISA <enhancedPassengerData> <enhancedTravellerInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 115 of 248

Web services User guide for function PNR_AddMultiElements

1 UN Y Y <surname>CHILDS LISA

5.18.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 116 of 248

Web services User guide for function PNR_AddMultiElements

5.19 Operation: Ignore To ignore the PNR using options mentioned in supported operations paragrah

5.19.1 Query Structure 20 1A <securityInformation> RP MUC6X0701 12345675 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences>

5.19.2 Reply Structure

Copyright © 1987-2013 Amadeus IT Group SA. Page 117 of 248

Web services User guide for function PNR_AddMultiElements

<sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE

5.19.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 118 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.20.1 Query Structure 0 <elementManagementPassenger> PR 2 <segmentName>NM <passengerData> <surname>SMITH 2 <passenger> A MRS ADT 3 <passengerData> <surname>BROWN <passenger> JIMMY INF 10JAN08 Copyright © 1987-2013 Amadeus IT Group SA. Page 119 of 248

Web services User guide for function PNR_AddMultiElements



5.20.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 120 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>SMITH 1 <passenger> A MRS ADT 1 Copyright © 1987-2013 Amadeus IT Group SA. Page 121 of 248

Web services User guide for function PNR_AddMultiElements

<passengerData> <surname>BROWN 1 <passenger> JIMMY INF 706 10012011 <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT 1 UN Y Y <surname>SMITH A MRS <enhancedPassengerData> <enhancedTravellerInformation> 1 INF UN Y Y Copyright © 1987-2013 Amadeus IT Group SA. Page 122 of 248

Web services User guide for function PNR_AddMultiElements

<surname>BROWN JIMMY 706 10012011

5.20.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 123 of 248

Web services User guide for function PNR_AddMultiElements

5.21 Operation: Infant With First Name Only The infant has to be associated to another passenger, and is attached to the same /travellerInfo / passengerData /travellerInformation element,field quantity = 2.

5.21.1 Query Structure 0 <elementManagementPassenger> PR 2 <segmentName>NM <passengerData> <surname>SMITH 2 <passenger> A MRS ADT 2 <passenger> JIMMY INF

5.21.2 Reply Structure 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 124 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 125 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>SMITH 2 <passenger> A MRS ADT 1 <passenger> JIMMY INF <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT Copyright © 1987-2013 Amadeus IT Group SA. Page 126 of 248

Web services User guide for function PNR_AddMultiElements

1 UN Y Y <surname>SMITH A MRS <enhancedPassengerData> <enhancedTravellerInformation> 1 INF UN Y Y <surname>SMITH JIMMY

5.21.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 127 of 248

Web services User guide for function PNR_AddMultiElements

5.22 Operation: Infant With No Information The infant has to be associated to another passenger, andis attached to the same /travellerInfo / passengerData /travellerInformation element,field quantity = 2.

5.22.1 Query Structure 0 <elementManagementPassenger> PR 2 <segmentName>NM <passengerData> <surname>SMITH 2 <passenger> A MRS ADT 1

5.22.2 Reply Structure 1A <securityInformation> RP Copyright © 1987-2013 Amadeus IT Group SA. Page 128 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 129 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>SMITH 1 <passenger> A MRS ADT 1 <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT 1 UN Y Y <surname>SMITH A MRS Copyright © 1987-2013 Amadeus IT Group SA. Page 130 of 248

Web services User guide for function PNR_AddMultiElements



5.22.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 131 of 248

Web services User guide for function PNR_AddMultiElements

5.23 Operation: Infant with own Native firstname The infant has to be associated to another passenger, and is attached to the same /travellerInfo / passengerData /travellerInformation element,field quantity = 2. 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.

5.23.1 Query Structure 0 <elementManagementPassenger> OT 2 <segmentName>NM <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT 2 ID123456 <surname>김 지훈 <enhancedPassengerData> <enhancedTravellerInformation> 1 INF <surname>김 수진 Copyright © 1987-2013 Amadeus IT Group SA. Page 132 of 248

Web services User guide for function PNR_AddMultiElements



5.23.2 Reply Structure 1A <securityInformation> RP SEL1A0980 SEL1A0980 <subjectQualifier>3 P12 --- RCH--- <statusInformation> RCH <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 133 of 248

Web services User guide for function PNR_AddMultiElements

<sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> SEL1A0980 A <sbrSystemDetails> <deliveringSystem> 1A SEL <sbrPreferences> <userPreferences> KR <elementManagementPassenger> PT 1 <segmentName>NM Copyright © 1987-2013 Amadeus IT Group SA. Page 134 of 248

Web services User guide for function PNR_AddMultiElements

1 <passengerData> <surname>KIM 2 <passenger> JI HUN MR ADT 1 ID123456 <passenger> SU JIN INF <enhancedPassengerData> <enhancedTravellerInformation> 1 1 ID123456 NN1 Y Y <surname>김 지훈 RN1 Y N KAR <surname>KIM JI HUN <enhancedPassengerData> <enhancedTravellerInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 135 of 248

Web services User guide for function PNR_AddMultiElements

1 INF NN1 Y Y <surname>김 수진 RN1 Y N KAR <surname>KIM SU JIN

5.23.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 136 of 248

Web services User guide for function PNR_AddMultiElements

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

Information

Airline

7S

Flight Number (1)

735

Date

211212

City Pair

HKG/SIN

Class of service

Y

Number of seats to reserve

1

Depature time

1420

Arrival time

1805

5.24.1 Query Structure 0 HKG <destination>SIN <elementManagementItinerary> SR 1 <segmentName>AIR Copyright © 1987-2013 Amadeus IT Group SA. Page 137 of 248

Web services User guide for function PNR_AddMultiElements

<product> <depDate>211212 <depTime>1420 <arrDate>211212 <arrTime>1805 HKG SIN 7S <productDetails> 735 C <processingIndicator>N <messageAction> 1 1 <status>HK <selectionDetailsAir> <selection> 0

5.24.2 Reply Structure 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 138 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 139 of 248

Web services User guide for function PNR_AddMultiElements

<sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 CDG7S0001 A <sbrSystemDetails> <deliveringSystem> 7S CDG <sbrPreferences> <userPreferences> FR <elementManagementItinerary> ST 1 <segmentName>AIR 1 <product> <depDate>211212 <depTime>1000 <arrDate>211212 <arrTime>1200 HKG SIN 7S Copyright © 1987-2013 Amadeus IT Group SA. Page 140 of 248

Web services User guide for function PNR_AddMultiElements

<productDetails> 735 C <processingIndicator>N 1 1 <status>HK <productDetails> <equipment> <weekDay>5 <selectionDetails> <selection> P10 <markerRailTour>

5.24.3 Possible Errors ? 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"

Copyright © 1987-2013 Amadeus IT Group SA. Page 141 of 248

Web services User guide for function PNR_AddMultiElements

5.25 Operation: Manual Commission The example below illustrates the request to create a manual commission.

5.25.1 Query Structure 0 <marker1> <elementManagementData> OT 1 <segmentName>FM 5

5.25.2 Reply Structure 1A <securityInformation> RP SEL6X0120 12345675 SEL6X0120 Copyright © 1987-2013 Amadeus IT Group SA. Page 142 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 SEL6X0120 A <sbrSystemDetails> <deliveringSystem> 6X SEL Copyright © 1987-2013 Amadeus IT Group SA. Page 143 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> KR <marker2/> <elementManagementData> OT 1 <segmentName>FM 1 <subjectQualifier>3 11 5

5.25.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 144 of 248

Web services User guide for function PNR_AddMultiElements

5.26 Operation: Manual Endorsement The example below illustrates the request to create a manual endorsement.

5.26.1 Query Structure 0 <marker1> <elementManagementData> OT 1 <segmentName>FE E <passengerType>PAX MANUAL ENDORSEMENT

5.26.2 Reply Structure 1A <securityInformation> RP NCE6X0100 91496716 NCE6X0100 Copyright © 1987-2013 Amadeus IT Group SA. Page 145 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 91496716 NCE6X0100 A <sbrSystemDetails> <deliveringSystem> 6X NCE Copyright © 1987-2013 Amadeus IT Group SA. Page 146 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> FR <marker2> <elementManagementData> OT 1 <segmentName>FE 1 <subjectQualifier>3 10 PAX \*M\*MANUAL ENDORSEMENT

5.26.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 147 of 248

Web services User guide for function PNR_AddMultiElements

5.27 Operation: Name With ID Code The example below illustrates a simple name request with thefollowing information: Parameter

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.

5.27.1 Query Structure 0 <elementManagementPassenger> PR 1 <segmentName>NM <passengerData> <surname>DUPONT 1 <passenger> MATHIEU ID1234

5.27.2 Reply Structure Copyright © 1987-2013 Amadeus IT Group SA. Page 148 of 248

Web services User guide for function PNR_AddMultiElements

1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 149 of 248

Web services User guide for function PNR_AddMultiElements

<sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>SMITH 1 <passenger> JOHN ID123456 <enhancedPassengerData> <enhancedTravellerInformation> 1 ID123456 Copyright © 1987-2013 Amadeus IT Group SA. Page 150 of 248

Web services User guide for function PNR_AddMultiElements

UN Y Y <surname>SMITH JOHN

5.27.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 151 of 248

Web services User guide for function PNR_AddMultiElements

5.28 Operation: Name With Passenger Type Code The example below illustrates a simple name request with the following information: Parameter

Information

Traveler Surname

CHIPIE

Traveler First name

WILLIAM

Passenger Type

CHILD (CHD)

5.28.1 Query Structure 0 <elementManagementPassenger> PR 1 <segmentName>NM <passengerData> <surname>DUPONT 1 <passenger> MATHIEU CHD 20MAR00

5.28.2 Reply Structure Copyright © 1987-2013 Amadeus IT Group SA. Page 152 of 248

Web services User guide for function PNR_AddMultiElements

1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 153 of 248

Web services User guide for function PNR_AddMultiElements

<sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>DUPONT 1 <passenger> MATHIEU CHD 20032000 Copyright © 1987-2013 Amadeus IT Group SA. Page 154 of 248

Web services User guide for function PNR_AddMultiElements

<enhancedPassengerData> <enhancedTravellerInformation> 1 CHD UN Y Y <surname>DUPONT MATHIEU 20032000

5.28.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 155 of 248

Web services User guide for function PNR_AddMultiElements

5.29 Operation: Name with title separated from firstname This example illustrate the addition of a name with title separated from firstname.

5.29.1 Query Structure 0 <elementManagementPassenger> PR 1 <segmentName>NM <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT <surname>SURNAME GIVENNAME

5.29.2 Reply Structure 1A <securityInformation> RP MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 156 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> Copyright © 1987-2013 Amadeus IT Group SA. Page 157 of 248

Web services User guide for function PNR_AddMultiElements

<deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>SURNAME 1 <passenger> GIVENNAME MR ADT <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT UN Y Y <surname>SURNAME GIVENNAME Copyright © 1987-2013 Amadeus IT Group SA. Page 158 of 248

Web services User guide for function PNR_AddMultiElements



5.29.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 159 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.30.1 Query Structure 0 <elementManagementPassenger> OT 2 <segmentName>NM <enhancedPassengerData> <enhancedTravellerInformation> 2 ADT 3 ID123456 <surname>김 지훈 <enhancedPassengerData> <enhancedTravellerInformation> 1 INF <surname>이 수진 Copyright © 1987-2013 Amadeus IT Group SA. Page 160 of 248

Web services User guide for function PNR_AddMultiElements



5.30.2 Reply Structure 1A <securityInformation> RP SEL6X0980 SEL6X0980 <subjectQualifier>3 P12 --- RCH--- <statusInformation> RCH <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 161 of 248

Web services User guide for function PNR_AddMultiElements

<userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> SEL6X0980 A <sbrSystemDetails> <deliveringSystem> 1A SEL <sbrPreferences> <userPreferences> KR <elementManagementPassenger> PT 1 Copyright © 1987-2013 Amadeus IT Group SA. Page 162 of 248

Web services User guide for function PNR_AddMultiElements

<segmentName>NM 1 <passengerData> <surname>KIM 1 <passenger> JI HUN MR ADT 1 ID123456 <passengerData> <surname>LEE 1 <passenger> SU JIN INF <enhancedPassengerData> <enhancedTravellerInformation> 1 1 NN1 Y Y <surname>김 지훈 RN1 Y N KAR Copyright © 1987-2013 Amadeus IT Group SA. Page 163 of 248

Web services User guide for function PNR_AddMultiElements

<surname>KIM JI HUN <enhancedPassengerData> <enhancedTravellerInformation> 1 INF NN1 Y Y <surname>이 수진 RN1 Y N KAR <surname>LEE SU JIN

5.30.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 164 of 248

Web services User guide for function PNR_AddMultiElements

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

Information

Airline

6X

Date

050213

City Pair

BKK/LHR

Class of service

Y

Number of seats to reserve

1

5.31.1 Query Structure 0 BKK <destination>LHR <elementManagementItinerary> SR 1 <segmentName>AIR <product> <depDate>050213 BKK LHR Copyright © 1987-2013 Amadeus IT Group SA. Page 165 of 248

Web services User guide for function PNR_AddMultiElements

6X <productDetails> OPEN Y <messageAction> 0

5.31.2 Reply Structure 1A <securityInformation> RP BKK6X0102 BKK6X0102 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 166 of 248

Web services User guide for function PNR_AddMultiElements

<userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> BKK6X0102 A <sbrSystemDetails> <deliveringSystem> 6X BKK <sbrPreferences> <userPreferences> TH <elementManagementItinerary> ST Copyright © 1987-2013 Amadeus IT Group SA. Page 167 of 248

Web services User guide for function PNR_AddMultiElements

1 <segmentName>AIR 1 <product> <depDate>220313 BKK LHR 6X <productDetails> OPEN Y 1 <productDetails> <weekDay>5 <markerRailTour>

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 168 of 248

Web services User guide for function PNR_AddMultiElements

5.32 Operation: Original exchange document This operation describes the addition of an FO element in the PNR.

5.32.1 Query Structure 0 <elementManagementData> OT 9 <segmentName>FO E 220 <documentNumber>2000000112 2 FRA 200508 23491193

5.32.2 Reply Structure 1A <securityInformation> RP MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 169 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> Copyright © 1987-2013 Amadeus IT Group SA. Page 170 of 248

Web services User guide for function PNR_AddMultiElements

<deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 1 <segmentName>FO 1 <subjectQualifier>3 45 220-2000000112FRA20MAY08/23491193/220-20000001125E2

5.32.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 171 of 248

Web services User guide for function PNR_AddMultiElements

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: • Record Locator mandatory • Departure/arrival time mandatory if flight not recorded in 1A • Only for non Altea airlines • PK and PL action codes Example: Parameter

Information

Airline

6X

Flight Number (1)

184

Date

050513

City Pair

JFK/CDG

Class of service

Y

Number of seats to reserve

1

Departure time

1200

Arrival time

1450

Record Locator

PZTX7A

5.33.1 Query Structure 0 JFK <destination>CDG <elementManagementItinerary> <segmentName>AIR <product> <depDate>050513 <depTime>1200 <arrDate>050513 <arrTime>1450 Copyright © 1987-2013 Amadeus IT Group SA. Page 172 of 248

Web services User guide for function PNR_AddMultiElements

JFK CDG 6X <productDetails> 184 Y <messageAction> 1 1 <status>PK <selectionDetailsAir> <selection> 0 PZTX7A

5.33.2 Reply Structure 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 173 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 174 of 248

Web services User guide for function PNR_AddMultiElements

12345675 CDG7S0001 A <sbrSystemDetails> <deliveringSystem> 6X CDG <sbrPreferences> <userPreferences> FR <elementManagementItinerary> ST 1 <segmentName>AIR 1 <product> <depDate>050513 <depTime>1100 <arrDate>050513 <arrTime>1400 JFK CDG 6X <productDetails> 184 Copyright © 1987-2013 Amadeus IT Group SA. Page 175 of 248

Web services User guide for function PNR_AddMultiElements

Y <detail>ET 1 6X PZTX7A 1 <status>PK <productDetails> <equipment>767 0 <weekDay>7 <departureInformation> <departTerminal>3 <arrivalStationInfo> 2E <selectionDetails> <selection> P10 <subjectQualifier>3 SEE RTSVC <markerRailTour> Copyright © 1987-2013 Amadeus IT Group SA. Page 176 of 248

Web services User guide for function PNR_AddMultiElements



5.33.3 Possible Errors ? 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"

Copyright © 1987-2013 Amadeus IT Group SA. Page 177 of 248

Web services User guide for function PNR_AddMultiElements

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

Information

Airline

7S

Flight Number (1)

3278

Date

230512

City Pair

CDG/HEL

Class of service

Y

Number of seats to reserve

1

Rloc

ECJ93

5.34.1 Query Structure 0 CDG <destination>HEL <elementManagementItinerary> SR 1 <segmentName>AIR <product> <depDate>230512 <depTime>1100 <arrDate>230512 <arrTime>1300 CDG Copyright © 1987-2013 Amadeus IT Group SA. Page 178 of 248

Web services User guide for function PNR_AddMultiElements

HEL 7S <productDetails> 3278 Y <messageAction> 1 1 <status>GK <selectionDetailsAir> <selection> 0 ECJ93

5.34.2 Reply Structure <message type="PNRACC" agency="1A" version="12" release="2" > 1A <securityInformation> RP Copyright © 1987-2013 Amadeus IT Group SA. Page 179 of 248

Web services User guide for function PNR_AddMultiElements

CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 CDG7S0001 Copyright © 1987-2013 Amadeus IT Group SA. Page 180 of 248

Web services User guide for function PNR_AddMultiElements

A <sbrSystemDetails> <deliveringSystem> 7S CDG <sbrPreferences> <userPreferences> FR <elementManagementItinerary> ST 1 <segmentName>AIR 1 <product> <depDate>230512 <depTime>0001 <arrDate>230512 <arrTime>0002 CDG HEL 7S <productDetails> 3278 Y Copyright © 1987-2013 Amadeus IT Group SA. Page 181 of 248

Web services User guide for function PNR_AddMultiElements

1 7S ECJ93 1 <status>GK <status>B <productDetails> <equipment>ECJ 0 <weekDay>3 2316 <selectionDetails> <selection> P10 <subjectQualifier>3 DOES NOT MATCH PUBLISHED PASSIVE FLIGHT/CLASS SCHEDULE*WARNING: THIS SEGMENT IS 139 DAYS IN THE PAST <markerRailTour>

5.34.3 Possible Errors 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 Copyright © 1987-2013 Amadeus IT Group SA. Page 182 of 248

Web services User guide for function PNR_AddMultiElements

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

Copyright © 1987-2013 Amadeus IT Group SA. Page 183 of 248

Web services User guide for function PNR_AddMultiElements

5.35 Operation: Received From Information The example below illustrates a received from information element:

5.35.1 Query Structure 0 <elementManagementData> <segmentName>RF <subjectQualifier>3 P22 internet/MUC1A0701

5.35.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 184 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE Copyright © 1987-2013 Amadeus IT Group SA. Page 185 of 248

Web services User guide for function PNR_AddMultiElements

<marker2> <elementManagementData> <segmentName>RF <subjectQualifier>3 P22 INTERNET/MUC6X0701

5.35.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 186 of 248

Web services User guide for function PNR_AddMultiElements

5.36 Operation: Seat Request This example shows a seat request for a non-smoking aisle seat (NSSA).

5.36.1 Query Structure 0 <elementManagementData> <segmentName>STR <seatGroup> <seatRequest> <seat> NSSA PT 1 ST 1

5.36.2 Reply Structure 1A <securityInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 187 of 248

Web services User guide for function PNR_AddMultiElements

RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 188 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>PRICING 1 <passenger> A ADT <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT UN Y Y <surname>PRICING A Copyright © 1987-2013 Amadeus IT Group SA. Page 189 of 248

Web services User guide for function PNR_AddMultiElements

<elementManagementItinerary> ST 1 <segmentName>AIR 2 <product> <depDate>260113 <depTime>1000 <arrDate>260113 <arrTime>1100 NCE CDG 6X <productDetails> 9996 Y <detail>ET 1 1 <status>HK Copyright © 1987-2013 Amadeus IT Group SA. Page 190 of 248

Web services User guide for function PNR_AddMultiElements

<productDetails> <equipment>744 0 <weekDay>6 <selectionDetails> <selection> P2 <markerRailTour> <marker2> <elementManagementData> OT 11 <segmentName>SSR 3 <serviceRequest> <ssr> NSSA <status>NN 1 6X NCE CDG <ssrb> 1 <seatType>N ST 1 PT Copyright © 1987-2013 Amadeus IT Group SA. Page 191 of 248

Web services User guide for function PNR_AddMultiElements

1

5.36.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 192 of 248

Web services User guide for function PNR_AddMultiElements

5.37 Operation: Service Fee This example shows an example of a service fee paid using Master Card.

5.37.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>FP CC 30 CA 5499840000000006 <expiryDate>1205 <currencyCode>EUR <serviceDetails> <statusDetails> SV

5.37.2 Reply Structure 5.37.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 193 of 248

Web services User guide for function PNR_AddMultiElements

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: • Record Locator mandatory • Departure/arrival time mandatory if flight not recorded in 1A • Only for non Altea airlines • Use of HK in RPI segment (in Edifact message) Example: Parameter

Information

Airline

6X

Flight Number (1)

782

Date

010513

City Pair

MIA/JFK

Class of service

Y

Number of seats to reserve

1

Rloc

JM4AZ

5.38.1 Query Structure 0 MIA <destination>JFK <elementManagementItinerary> <segmentName>AIR <product> <depDate>010513 MIA Copyright © 1987-2013 Amadeus IT Group SA. Page 194 of 248

Web services User guide for function PNR_AddMultiElements

JFK 6X <productDetails> 782 Y <messageAction> 1 1 <status>HK <selectionDetailsAir> <selection> 0 JM4AZ

5.38.2 Reply Structure 5.38.3 Possible Errors ? 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"

Copyright © 1987-2013 Amadeus IT Group SA. Page 195 of 248

Web services User guide for function PNR_AddMultiElements

5.39 Operation: Simple Name The example below illustrates a simple name request with the following information: Parameter

Information

Traveler Surname

CHIKKLES

Traveler First name

BENJAMIN

5.39.1 Query Structure 0 <elementManagementPassenger> PR 1 <segmentName>NM <passengerData> <surname>DUPONT 1 <passenger> MATHIEU

5.39.2 Reply Structure 1A <securityInformation> Copyright © 1987-2013 Amadeus IT Group SA. Page 196 of 248

Web services User guide for function PNR_AddMultiElements

RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 197 of 248

Web services User guide for function PNR_AddMultiElements

A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>DUPONT 1 <passenger> MATHIEU <enhancedPassengerData> <enhancedTravellerInformation> 1 UN Y Y <surname>DUPONT MATHIEU Copyright © 1987-2013 Amadeus IT Group SA. Page 198 of 248

Web services User guide for function PNR_AddMultiElements



5.39.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 199 of 248

Web services User guide for function PNR_AddMultiElements

5.40 Operation: Single Flight The following example below illustrates a request to reserve a flight with the following information: Parameter

Information

Airline

7S

Flight Number

3278

Date

05/03/13

City Pair

CDG to HEL

Class of service

Y

Number of seats to reserve

1

5.40.1 Query Structure 0 <elementManagementItinerary> SR 1 <segmentName>AIR <product> <depDate>050313 CDG HEL 7S <productDetails> 3278 Y Copyright © 1987-2013 Amadeus IT Group SA. Page 200 of 248

Web services User guide for function PNR_AddMultiElements

<messageAction> 1 1 <status>NN <selectionDetailsAir> <selection> P10

5.40.2 Reply Structure 1A <securityInformation> RP CDG7S0001 12345675 CDG7S0001 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 201 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 CDG7S0001 A <sbrSystemDetails> <deliveringSystem> 7S CDG <sbrPreferences> <userPreferences> FR Copyright © 1987-2013 Amadeus IT Group SA. Page 202 of 248

Web services User guide for function PNR_AddMultiElements

<elementManagementItinerary> ST 1 <segmentName>AIR 1 <product> <depDate>050313 <depTime>0735 <arrDate>050313 <arrTime>1130 CDG HEL 7S <productDetails> 3278 Y <detail>ET 1 1 <status>HK <productDetails> <equipment>E90 0 Copyright © 1987-2013 Amadeus IT Group SA. Page 203 of 248

Web services User guide for function PNR_AddMultiElements

<weekDay>2 <departureInformation> <departTerminal>2D <arrivalStationInfo> 2 <selectionDetails> <selection> P2 <subjectQualifier>3 SEE RTSVC <markerRailTour>

5.40.3 Possible Errors 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

Copyright © 1987-2013 Amadeus IT Group SA. Page 204 of 248

Web services User guide for function PNR_AddMultiElements

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

5.41.1 Query Structure <message type="PNRADD" agency="1A" version="12" release="2" > 0 <marker1> <elementManagementData> <segmentName>RM <miscellaneousRemark> RM * A.I.R Remark, use category for accounting remarks

5.41.2 Reply Structure <message type="PNRACC" agency="1A" version="12" release="2" > 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> Copyright © 1987-2013 Amadeus IT Group SA. Page 205 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 206 of 248

Web services User guide for function PNR_AddMultiElements

DE <marker2> <elementManagementData> OT 1 <segmentName>RM 1 <miscellaneousRemarks> RM *A.I.R REMARK, USE CATEGORY FOR ACCOUNTING REMARKS <extendedRemark> <structuredRemark> RM * A.I.R REMARK, USE CATEGORY FOR ACCOUNTING REMARKS

5.41.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 207 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.42.1 Query Structure 0 <elementManagementData> <segmentName>AM <structuredAddress> P08

A1 1234 so main street

A2 villa 9 CI Atlanta CO USA Copyright © 1987-2013 Amadeus IT Group SA. Page 208 of 248

Web services User guide for function PNR_AddMultiElements

NA Dave Johnson ST Georgia ZP 30039

5.42.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 209 of 248

Web services User guide for function PNR_AddMultiElements

<userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <elementManagementPassenger> PT 1 Copyright © 1987-2013 Amadeus IT Group SA. Page 210 of 248

Web services User guide for function PNR_AddMultiElements

<segmentName>NM 1 <passengerData> <surname>PRICING 1 <passenger> A ADT <enhancedPassengerData> <enhancedTravellerInformation> 1 ADT UN Y Y <surname>PRICING A <elementManagementItinerary> ST 1 <segmentName>AIR 2 <product> <depDate>260113 <depTime>1000 <arrDate>260113 Copyright © 1987-2013 Amadeus IT Group SA. Page 211 of 248

Web services User guide for function PNR_AddMultiElements

<arrTime>1100 NCE CDG 6X <productDetails> 9996 Y <detail>ET 1 1 <status>HK <productDetails> <equipment>744 0 <weekDay>6 <selectionDetails> <selection> P2 <markerRailTour> <marker2> <elementManagementData> Copyright © 1987-2013 Amadeus IT Group SA. Page 212 of 248

Web services User guide for function PNR_AddMultiElements

OT 9 <segmentName>AM/ 3 <structuredAddress> P08

NA DAVE JOHNSON

A1 1234 SO MAIN STREET

A2 VILLA 9

ZP 30039

CI ATLANTA

ST GEORGIA

CO USA

5.42.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 213 of 248

Web services User guide for function PNR_AddMultiElements

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

5.43.1 Query Structure 0 <marker1> <elementManagementData> OT 10 <segmentName>RM <extendedRemark> <structuredRemark> RM THIS IS A GENERAL REMARK

5.43.2 Reply Structure

1A <securityInformation> RP MUC6X0701

Copyright © 1987-2013 Amadeus IT Group SA. Page 214 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A Copyright © 1987-2013 Amadeus IT Group SA. Page 215 of 248

Web services User guide for function PNR_AddMultiElements

MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 3 <segmentName>RM 1 <miscellaneousRemarks> RM THIS IS A GENERAL REMARK <extendedRemark> <structuredRemark> RM THIS IS A GENERAL REMARK

5.43.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 216 of 248

Web services User guide for function PNR_AddMultiElements

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

5.44.1 Query Structure 0 <marker1> <elementManagementData> OT 10 <segmentName>RM <extendedRemark> <structuredRemark> RM THIS IS A SECURED REMARK

5.44.2 Reply Structure

1A <securityInformation> RP

Copyright © 1987-2013 Amadeus IT Group SA. Page 217 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A Copyright © 1987-2013 Amadeus IT Group SA. Page 218 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 3 <segmentName>RM 1 <miscellaneousRemarks> RM THIS IS A SECURED REMARK <extendedRemark> <structuredRemark> RM THIS IS A SECURED REMARK <securityDetails> O B MUC6X0701

Copyright © 1987-2013 Amadeus IT Group SA. Page 219 of 248

Web services User guide for function PNR_AddMultiElements

5.44.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 220 of 248

Web services User guide for function PNR_AddMultiElements

5.45 Operation: Structured Remark with corporate security The example below illustrates a request for a corporate remark with Unicode characters and a category. 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

5.45.1 Query Structure 0 <elementManagementData> OT 10 <segmentName>RM <extendedRemark> <structuredRemark> RM A MR 김 지 훈 IS A VIP <serviceDetails> <statusDetails> RX

5.45.2 Reply Structure

1A <securityInformation>

Copyright © 1987-2013 Amadeus IT Group SA. Page 221 of 248

Web services User guide for function PNR_AddMultiElements

RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 222 of 248

Web services User guide for function PNR_AddMultiElements

A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 3 <segmentName>RM 1 <miscellaneousRemarks> RM A NOT DISPLAYABLE <extendedRemark> <structuredRemark> RM A MR 김 지 훈 IS A VIP <securityDetails> F B MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 223 of 248

Web services User guide for function PNR_AddMultiElements



5.45.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 224 of 248

Web services User guide for function PNR_AddMultiElements

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

5.46.1 Query Structure 0 <marker1> <elementManagementData> OT 10 <segmentName>RM <extendedRemark> <structuredRemark> RM THIS IS A SECURED REMARK <securityDetails> B NCE6X0980 <securityDetails> F R LON6X0100 Copyright © 1987-2013 Amadeus IT Group SA. Page 225 of 248

Web services User guide for function PNR_AddMultiElements

5.46.2 Reply Structure 1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC Copyright © 1987-2013 Amadeus IT Group SA. Page 226 of 248

Web services User guide for function PNR_AddMultiElements

<sbrPreferences> <userPreferences> DE <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <marker2> <elementManagementData> OT 3 <segmentName>RM 1 <miscellaneousRemarks> RM THIS IS A SECURED REMARK <extendedRemark> <structuredRemark> RM THIS IS A SECURED REMARK Copyright © 1987-2013 Amadeus IT Group SA. Page 227 of 248

Web services User guide for function PNR_AddMultiElements

<securityDetails> O B MUC6X0701 <securityDetails> O B NCE6X0980 <securityDetails> F R LON6X0100

5.46.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 228 of 248

Web services User guide for function PNR_AddMultiElements

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

5.47.1 Query Structure 0 <elementManagementData> OT 10 <segmentName>RM <extendedRemark> <structuredRemark> RM A MR 김 지 훈 IS A VIP <serviceDetails> <statusDetails> TS

5.47.2 Reply Structure

1A

Copyright © 1987-2013 Amadeus IT Group SA. Page 229 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 Copyright © 1987-2013 Amadeus IT Group SA. Page 230 of 248

Web services User guide for function PNR_AddMultiElements

A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 3 <segmentName>RM 1 <miscellaneousRemarks> RM A NOT DISPLAYABLE <extendedRemark> <structuredRemark> RM A MR 김 지 훈 IS A VIP <eltPosDetails> <pointOfSaleInformationType> <pointOfSale> <partyCodeQualifier>UPD <sbrUserIdentification> Copyright © 1987-2013 Amadeus IT Group SA. Page 231 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 SU 0001AA SGN <pointOfSaleDate> LT 2012 <month>1 25 11 <minutes>38

5.47.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 232 of 248

Web services User guide for function PNR_AddMultiElements

5.48 Operation: Ticketing Arrangement Element The example below illustrates a request for a ticketing element with the following information: Parameter

Information

Ticketing Type indicator

Ticket Time Limit (TL)

Date of Ticketing

12/12/12

5.48.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>TK <passengerType>PAX TL 121201

5.48.2 Reply Structure 1A <securityInformation> RP Copyright © 1987-2013 Amadeus IT Group SA. Page 233 of 248

Web services User guide for function PNR_AddMultiElements

MUC6X0701 12345675 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 E Copyright © 1987-2013 Amadeus IT Group SA. Page 234 of 248

Web services User guide for function PNR_AddMultiElements

<sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 1 <segmentName>TK 1 TL 121212 MUC6X0701

5.48.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 235 of 248

Web services User guide for function PNR_AddMultiElements

5.49 Operation: Tour Code in Free Flow Format The example below illustrates the request to create a tour code in free flow format.

5.49.1 Query Structure 0 <marker1> <elementManagementData> OT 1 <segmentName>FT <passengerType>PAX FF TOUR CODE

5.49.2 Reply Structure 1A <securityInformation> RP NCE6X0100 91496716 Copyright © 1987-2013 Amadeus IT Group SA. Page 236 of 248

Web services User guide for function PNR_AddMultiElements

NCE6X0100 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 91496716 NCE6X0100 A <sbrSystemDetails> <deliveringSystem> Copyright © 1987-2013 Amadeus IT Group SA. Page 237 of 248

Web services User guide for function PNR_AddMultiElements

6X NCE <sbrPreferences> <userPreferences> FR <marker2> <elementManagementData> OT 1 <segmentName>FT 1 <subjectQualifier>3 12 PAX \*TOUR CODE

5.49.3 Possible Errors See "Error Messages" section.

Copyright © 1987-2013 Amadeus IT Group SA. Page 238 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.50.1 Query Structure 0 <elementManagementData> OT 1 <segmentName>AMU <subjectQualifier>3 P08 Dave Johnson, 1234 so main street, Atlanta GA 30039, USA

5.50.2 Reply Structure Copyright © 1987-2013 Amadeus IT Group SA. Page 239 of 248

Web services User guide for function PNR_AddMultiElements

1A <securityInformation> RP MUC6X0701 MUC6X0701 <sbrPOSDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> <sbrCreationPosDetails> <sbrUserIdentificationOwn> <sbrSystemDetails> <deliveringSystem> <sbrPreferences> <userPreferences> Copyright © 1987-2013 Amadeus IT Group SA. Page 240 of 248

Web services User guide for function PNR_AddMultiElements

<sbrUpdatorPosDetails> <sbrUserIdentificationOwn> MUC6X0701 A <sbrSystemDetails> <deliveringSystem> 1A MUC <sbrPreferences> <userPreferences> DE <marker2> <elementManagementData> OT 1 <segmentName>AM 1 <subjectQualifier>3 P08 DAVE JOHNSON, 1234 SO MAIN STREET, USA

ATLANTA

GA

30039,

5.50.3 Possible Errors

Copyright © 1987-2013 Amadeus IT Group SA. Page 241 of 248

Web services User guide for function PNR_AddMultiElements

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.

5.51.1 Query Structure 52A345 0 <elementManagementData> <segmentName>SSR <serviceRequest> <ssr> FQTU QF QF1117622/CN-12345

5.51.2 Reply Structure

1A 52A345 311012 1129

Copyright © 1987-2013 Amadeus IT Group SA. Page 242 of 248

Web services User guide for function PNR_AddMultiElements

<securityInformation> RP AASU NYXX02001 12345675 NYXX02001 NYC <secondRpInformation> NYXX02001 1234AA 311012 12345675 1129 <subjectQualifier>3 P12 --- RLR --- <sbrPOSDetails> <sbrUserIdentificationOwn> 12345675 NYXX02001 T <sbrSystemDetails> <deliveringSystem> 1A NYC <sbrPreferences> <userPreferences> US <sbrCreationPosDetails> Copyright © 1987-2013 Amadeus IT Group SA. Page 243 of 248

Web services User guide for function PNR_AddMultiElements

<sbrUserIdentificationOwn> 12345675 NYXX02001 T <sbrSystemDetails> <deliveringSystem> 1A NYC <sbrPreferences> <userPreferences> US <sbrUpdatorPosDetails> <sbrUserIdentificationOwn> 12345675 NYXX02001 T <sbrSystemDetails> <deliveringSystem> 1A NYC <sbrPreferences> <userPreferences> US <enveloppeNumberData> <sequenceDetails> 1 <currentRecord>0 Copyright © 1987-2013 Amadeus IT Group SA. Page 244 of 248

Web services User guide for function PNR_AddMultiElements

2012 <month>12 21 <statusDetails> MOD <elementManagementPassenger> PT 1 <segmentName>NM 1 <passengerData> <surname>ABOUD 1 <passenger> RUSSEL <elementManagementItinerary> ST 1 <segmentName>AIR 2 Copyright © 1987-2013 Amadeus IT Group SA. Page 245 of 248

Web services User guide for function PNR_AddMultiElements

<product> <depDate>211212 <depTime>2137 <arrDate>231212 <arrTime>0517 2 LHR SYD QF <productDetails> 2 Y <detail>ET 1 QF 52A345 1 <status>HK <productDetails> <equipment>388 1 <weekDay>5 <departureInformation> <departTerminal>3 Copyright © 1987-2013 Amadeus IT Group SA. Page 246 of 248

Web services User guide for function PNR_AddMultiElements

<selectionDetails> <selection> P2 <markerRailTour> <marker2> <elementManagementData> OT 3 <segmentName>AP 3 <subjectQualifier>3 5 1234 <elementManagementData> OT 9 <segmentName>TK 4 OK 311012 NYXX02001 Copyright © 1987-2013 Amadeus IT Group SA. Page 247 of 248

Web services User guide for function PNR_AddMultiElements

<elementManagementData> OT 26 <segmentName>SSR 5 <serviceRequest> <ssr> FQTU <status>HK 1 QF QF1117622/QF1117622/CN-12345 ST 1 PT 1

5.51.3 Possible Errors 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

Copyright © 1987-2013 Amadeus IT Group SA. Page 248 of 248