Error Messages

Operation: Accounting Information

The example below illustrates a request to add an accounting element with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Confidential Remark

The example below illustrates a request for a confidential remark.

Query Structure

Reply Structure

Possible Errors

Operation: Connection Flight

The following example below illustrates a request to reserve connection flight:

Query Structure

Reply Structure

Possible Errors

Operation: Contact Information

The example below illustrates the request for an agency contact element with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Creating an OSI with Mandatory Airline Code

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

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: E-mail

The example below illustrates the request for an EMAIL contact elementwith the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Extra Seat

The example below illustrates a simple name request for an extra seat with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Fare Discount for a child

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

Query Structure

Reply Structure

Possible Errors

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.

Query Structure

Reply Structure

Possible Errors

Operation: Fare Discount for senior citizen

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

Query Structure

Reply Structure

Possible Errors

Operation: Fax Number

The example below illustrates the request for a fax contact element with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Form of Payment

Used to specify the form of payment for a ticket.

Query Structure

Reply Structure

Possible Errors

Operation: Frequent Flyer Numbers

The example below illustrates a request for a frequent flyer number with the following information

Query Structure

Reply Structure

Possible Errors

Using the YY as company id results in an error "UNABLE TO PROCESS", you must enter a valid airline code.

Operation: General Remarks

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

Query Structure

Reply Structure

Possible Errors

Operation: Group Name

The example below illustrates a group name with 2 travelers containing the following information:

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.

Query Structure

Reply Structure

Possible Errors

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.

Query Structure

Reply Structure

Possible Errors

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.

Query Structure

Reply Structure

Possible Errors

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

Query Structure

Reply Structure

Possible Errors

Operation: Name With ID Code

The example below illustrates a simple name request with thefollowing information:

Note: Two identification codes are supported they are 'ID' andor 'CR'. The ID codes are individually assigned and can form part of aclient's department name and or even a description, however it has to remain 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.

Query Structure

Reply Structure

Possible Errors

Operation: Name With Passenger Type Code

The example below illustrates a simple name request with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Original exchange document

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

Query Structure

Reply Structure

Possible Errors

Operation: Query with Connection Flight

This query demonstrates a sole passenger traveling from Nice to London with a connection flight at Charles de Gaule airport in Paris.

The example below illustrates a request with the following combination of information:

Note: it is important to note that each of the flight segment values must be entered independently

Query Structure

Reply Structure

Possible Errors

Operation: Received From Information

The example below illustrates a received from information element:

Query Structure

Reply Structure

Possible Errors

Operation: Seat Request

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

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Service Fee

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

Query Structure

Reply Structure

Possible Errors

Operation: Simple Name

The example below illustrates a simple name request with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Simple Return Flight

The benefit of using this powered interface is the ability to create a combination of many passenger elements with one function call.

The example below illustrates a request with the following combination of information:

Query Structure

Reply Structure

Possible Errors

Operation: Single Flight

The following example below illustrates a request to reserve a flight with the following information:

Query Structure

Reply Structure

Possible Errors

Operation: Special A.I.R remark

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

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Structured Mailing

The example below illustrates a structured mailing address element including the following optional address information:

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.

Query Structure

Reply Structure

Possible Errors

Operation: Ticketing Arrangement Element

The example below illustrates a request for a ticketing element with the following information:

Query Structure

Reply Structure

Possible Errors

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:

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.

Query Structure

Reply Structure

Possible Errors

Function: AddRedemption

Overview

The AddRedemption function is used to create one or several SSR FQTR. The SSR FQTR elementindicates that the passenger will be redeeming miles which were accrued under that card numberfor the segments to be flown.

For airlines which store their frequent flyer database within the Amadeus Global Core systemthe frequent flyer number is validated against the card owning airline's database but there isno validation of the name since a card holder may redeem his points in favor of someone else.If the airline does not store the frequent flyer database within Amadeus Global Core system,the SSR FQTR is stored in the PNR without validation.

For airlines which are users of the AF group Customer Application, the card number validationis performed in the Customer Application. The Customer Application may respond to the user withan FD element which will be added to the PNR.

For airlines which are users of interactive validation application,the validation of theredemption is performed in the Loyalty System of the airline asking for this interactive validation(it can be target airline or card owner airline or the both). In this case, the SSR FQTR is storedin the PNR only if it is approved by the interactive validation: if an error is returned by Loyaltysystem of the airline concerned by interactive validation, the SSR FQTR is not added in the PNR.

Supported Operations

Not applicable.

Limitations

Not applicable.

Unsupported Operations

Not applicable.

Prerequisites

A PNR must be present in the AAA:
If the user works on an existing PNR that has already been end-transacted, the PNR has tobe previously retrieved. This can be done via the verb PoweredPNRRetrieve.

If he works on a new PNR, name elements and segments must be present in the PNR. Thiscan be done via the verb PoweredPNRAddMultiElements.

The context must be kept between the different transactions.

Building A Query

Input parameters:

Only the input parameters containing the frequent traveler information are mandatory.

Input parameters involved in the Frequent Traveler Verification:

• action request: see fqtvData in the codesets
• airline code: Frequent Flyer Card owning airline
• frequent flyer number
• In the context of interactive validation, the certificate number:this field contains a number, delivered by card owner airline, which identifies the contentof upgrade request in card owner airline system. (passenger name, flights, dates..)

Input parameters involved in the Related Product Information

• The status code that will be used for the SSR FQTR added

Input parameters involved in the Interactive Free Text

• Free text: can contain a reason for the redemption

Input parameters involved in the Reservation Control Information

• reservation control number: this field contains the Amadeus record locator

Input parameters involved in the Traveler Information

• The passenger surname
• The passenger given name
• The traveler reference number: this field contains the tattoo number of the passengerthat will be associated to the SSR FQTV. It has been transmitted in a previous response message.

Input parameters involved in the Travel Product Information

• The segment reference number: this field contains the tattoo number of the segment thatwill be associated to the SSR FQTR. It has been transmitted in a previous response message.

Receiving A Reply

If the process is successful

• For airlines users of the AF group Customer Application:
  • One or several validated SSR FQTR elements are created.
  • And/Or an FD element is created.
  • And/Or Warning messages are displayed.
  • SSR FQTR elements, warnings, FD element are sent in the reply message.
  
  
• For other airlines
  • One or several SSR FQTR elements are created. They may be validated or not.
  • SSR FQTR elements are sent in the reply message.
  
  

If the process is not successful: an error is sent in the reply message

Remark: This transaction does not save the PNR. The update will become effective after aCommit transaction. Therefore a context must be kept between the different transactions.

Error Reply Structure

A generic reply can contain

• a record locator
• a generic error containing:
  • An error code: the Amadeus canned message number corresponding to the error
  • An error category for either a Mutually defined warning (code WZZ) or a Mutually defined error (code ZZZ)
  • An error code owner (always 1A)
  
  
• A generic error message
• One or several Travel Product Information containing:
  • The segment reference
  
  
• A Traveler Information containing:
  • The passenger surname
  • The passenger given name
  • The passenger reference
  
  
• One Frequent Traveler Verification per SSR FQTR created containing:
  • The alliance tier description
  • The Frequent Flyer Card owning airline
  • The target airline
  • The Frequent Flyer number
  • The category: set to PAX if the element is an FD
  • The certificate number
  • The airline priority code or tier level
  • The award code
  
  
• A Related Product Information containing:
  • The status code of the SSR / FD
  
  
• A Free Text containing:
  • The reason for the redemption
  
  
• A Frequent Flyer error containing:
  • An error code: the Amadeus canned message number corresponding to the error
  • An error category for either a Mutually defined warning (code WZZ) or a Mutually defined error (code ZZZ)
  • An error code owner (always 1A)
  
  
• A Frequent Flyer error message

Note: this is only a generic reply. In reality, all these fields can not be present atthe same time.

In case of error, see the "Error Message" section.

Generic reply containing Passenger information:

Error Messages

Generic Edifact error

The reply contains only the error information and the error message.

Generic errors

In these cases, the reply contains the record locator if given in the request,the error information and the error message.

Errors linked to the Frequent Flyer Add process

In these cases, the reply contains the record locator if given in the request,the Frequent Traveler Verification given in the request, the error information and the error message.

Errors linked to the Interactive validation process

In these cases, the reply contains the record locator, the errorinformation returned by the airline loyalty system (the airline which was asking for aninteractive validation) and the error message.

Note:

• The messages below are just examples. The list is not an exhaustive list.
• These error messages are returned by the loyalty system of the airline which is askingfor an interactive validation. Do not forget it could be target airline or card owner airline.

Errors linked to the Interactive validation process

In these cases, the reply contains the record locator, the errorinformation returned by the airline loyalty system (the airline which was asking for aninteractive validation) and the error message.

Note:

• The messages below are just examples. The list is not an exhaustive list.
• These error messages are returned by the loyalty system of the airline which is askingfor an interactive validation. Do not forget it could be target airline or card owner airline.

Operation: Add an SSR FQTR

There must be a PNR retrieved with record locator XXXXXX or in creation in the AAA.

The example shows the message required to add an SSR FQTR specified by the following data:

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Add an SSR FQTR with associations

There must be a PNR retrieved with record locator XXXXXX or in creation in the AAA.

The example shows the message required to add an SSR FQTR specified by the following dataand associations:

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Add an SSR FQTR with certificate number for interactive validation

There must be a PNR retrieved with record locator XXXXXX or in creation in the AAA.

The example shows the message required to add an SSR FQTU specified by the following dataand associations, with a certificate number:

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Generic Reply

Query Structure

Possible Errors

Function: Cancel

Overview

The Cancel is used to cancel selected elements from a PNR. A PNR contains all the elements (details) pertaining to a passenger's trip and reservation.

With the cancel function single and multiple elements are cancelled and moved to the PNR history. The cancel function is also used to cancel all active itinerary elements, except certain rail segments and all non-mandatory PNR elements. Itinerary flight segments that are marked as flown, or auxiliary segments that are marked as past, cannot be canceled from a PNR.

Multiple instances of the cancel structure to cancel different types and or same types are not allowed. For example to cancel a combination of name elements and itinerary elements or using two instances to cancel more than one of the same element type is not allowed. However, multiple instances of the same element type are supported in a single instance of the structure with multiple instances of the element i.e. multiple OT elements shouldbe identified under the same cancel structure as multiple instances the following are examples of a valid entries.

Note:

Repetition factors

The cancelElements/entryType below are used to cancel elements. The structure is limited to a repetition of '1':

For group PNRs, depending on the way your office profile is set up, the effect that thisl function has upon non-mandatory PNR elements is that it may cancel all elements with the exception of Air remark elements, however these can be removed separately. Alternatively, it may keep all remark elements.

A PNR must contain the following five elements:

• Name element

A passenger name.

• Itinerary element

A booking for a flight or other service.

• Contact element

Telephone number or contact information for the person making the booking.

• Ticketing element

A indication of the arrangements for issuing a ticket for the booking.

• Received from element

The name of the person who has made the booking.

Each PNR that is created is assigned a six Character code called a Record Locator, which is the unique identifier for the PNR andcan be used to retrieve the PNR. For more information regarding other methods and the rules for retrieving a PNR, please refer to the Retrieve function in this document.

Supported Operations

Following is a list of examples showing some of the supported operations:

• Single Data Element

This operation cancels a data element from a PNR to the PNR history.

• Multiple Data Elements

Multiple data elements are canceled from the active PNR and placed in the PNR history.

• Cancel Elements in Retrieved PNR

This operation cancels data elements from a retrieved PNR to the PNR history.

• Cancel Elements and End Transaction

This operation permits the deletion of multiple data elements from an active PNR andends the transaction.

• Cancel Elements and End Transaction (Automatic add of Receive From)

This operation permits the deletion of multiple data elements from an active PNR andfiles and closes the PNR with the end transaction action.Thereafter, automatically adding a received from element that identifies the person responsible for performing the modification the PNR.

• Cancel the entire Itinerary

This operation removes the entire Itinerary from an active PNR to the PNR history.

• Cancel the entire Itinerary and other Elements

This operation removes the whole Itinerary from an active PNR and other data elementsto the PNR history.

• Cancel Itinerary and End Transaction

This operation removes an Itinerary and other data elements from an active PNR followed by an End of Transaction action that files and closes the PNR.

The action return line numbers and the end transaction action are automatically built into the reply feature of the cancel function.

Name Integration

A group name element in a PNR specifies the collective name and the number of members (a group of people) traveling together. The Name Integration operation reduces the space that has already been booked for agroup by canceling named or unnamed group members from the group element.

Future

• Canceling seat elements
• Override all End Transaction warnings
• End transaction with retrieve

Exceptions to the supported functions

These features are special cases as they are supported however they are incorporated directly into the function action.

• Outbound display not required
• Ignore
• Ignore and retrieve

The 'Received From' element is a mandatory element following a cancelled (modified) element, it is used to identify who has made the modification. This is automatically administered and you can not personalize this element with a user's identification. The option to personalize this element could be a future enhancement.

Limitations

Following is a list of some limitations using certain operations in the Cancel PNR element:

• Billing element

Removes the element to the PNR history and renumbers the remaining elements

• Confidential remark

Removes the element to the PNR history and renumbers the remaining elements

• Contact element

Removes the element to the PNR history and renumbers the remaining elements

• Fare elements

Removes the element to the PNR history and renumbers the remaining elements

• General remarks

Removes the element to the PNR history and renumbers the remaining elements

• Group name

The group name element can not be cancelled; however, you can reduce the group size.

• Itinerary elements

When all the itinerary elements are cancelled, the segments will remain in the PNR until the end transaction. All Special Service Requests are then canceled from the PNR and any remaining Other Service Information elements will need to be cancelled before the end transaction. Itinerary flight segments that are marked as flown or auxiliary segments that are marked aspast can not be canceled or canceled from a PNR.

Important: any elements associated to the cancelled itinerary will also be cancelled simultaneously following this action.

Mailing address

Removes the element to the PNR history and renumbers the remaining elements

Name element

The name element can be canceled with no reverberation as long as the PNR has not beenSaved.Once a PNR has been save it can not exist without at least one name element, if anattempt is made to cancel the last remaining name element an error will be received.

Important: any elements associated to the cancelled name will also be cancelled simultaneouslyfollowing this action.

Option element

Removes the element to the PNR history and renumbers the remaining elements

Other Service Information

Removes the element to the PNR history and renumbers the remaining elements

Special Service Request

When added during the current session the cancelled element is removed and the remaining elementsare renumbered

Ticketing element

Removes the element to the PNR history and renumbers the remaining elements

Unsupported operations

• End transaction and queue place
• Cancel MCO sub-elements
• Cancel segment but do not transmit to airline

Unsupported Operations

Not applicable

Prerequisites

Prior to using the function Cancel, it is necessary to have a PNR that has just been created and or a PNR that has just been retrieved.

This example is a query request to retrieve a PNR by Record Locator and is used throughout this chapter and is NOT part of the PNR cancel function. For more information about the function Retrieve, please refer to its user's guide.

Building A Query

Receiving A Reply

For each PNR query cancel presented, there is a corresponding reply structure returned. The following is an extract of a typical reply returned from a retrieved PNR, it shows some different elements and segments that are encountered.

Note: the reply structure has not been provided in each example case.

Error Reply Structure

Error Messages

The following errors can be returned while trying to use the cancel function.

No Match for Record Locator

This error message is returned when the control number (PNR record locator) entered can not be found, therefore ensure that the PNR being referenced is valid, refer to the function Retrieve for further methods of retrieving a PNR.

1931 - NO MATCH FOR RECORD LOCATOR

Invalid format

This error message is received if the identifier for the action is missing and the data element to be canceled is present. The solution is to return to the query and add the missing information.

0 - INVALID FORMAT/NOT ENTERED/>XE

Operation: 1 - PNR used as example

The sample PNR scenarios consist of the following elements:

• Record locator (XXXXXX)
• 3 passenger names
• 2 flights
• 1 phone
• 1 ticket
• 1 Service information

Query Structure

Possible Errors

Operation: Cancel element number 9

This query is a request to cancel element number 9, which happens to be a contact element from the sample PNR.

Outline of the query structure using smart names for deleting a single element. The control number is the PNR Record locator number, followed by theaction code 0 (Zero). The value 'E' in line 2 declares the type of cancel entry, hence to cancel an element. The 'OT' value signifies the type of element (other) and the last item line 4, indicates the reference number of the element to be cancelled.

As a result only 154 items are listed in the reply, indicating that for a cancellation to be successful, for each canceled element and or segment there will be a reduction in the reply dispensed, which is equal in number to the lines associated to the contact element canceled.

Listed are the items that have been removed from the original PNR.

Query Structure

Reply Structure

Possible Errors

1895 - CHECK ELEMENT NUMBER

If no data elements are matching the element value entered in the query, the system will ask for you to check the value entered.

Operation: Cancel Elements in PNR

This query is a request to cancel two elements, this illustration signifies that the PNR is an active PNR and or is in current session.

This query is a request to cancel elements and to save the changes.

The reply returned is the same as the example Cancel Element ; the only difference being is the query uses a Record Locator to retrieve the PNR.

Query Structure

Reply Structure

Possible Errors

1935 - ELEMENT CONFLICT

If different element types are added in a single cancellation entry, such as Other data elements and Name elements then there is a possibility that an error indicating an element conflict is listed.

Operation: Cancel Elements, End Transaction

The Receive From element indicates who has made or updated a reservation. The element is mandatory after a creation or modification of a PNR and is recorded in the PNR history.

The PNR action code value 10 indicates that regardless of the operation on the PNR and End of transaction command will be automatically performed by the application.

Query Structure

Reply Structure

Possible Errors

3350 - RESTRICTED/NAME ELEMENT PREVIOUSLY CANCELLED

If a name element had been cancelled in the current session. The next action must be a Received From action and an End of Transaction operation before proceeding. In other words you must perform two steps, cancel the name and save the CHANGES in the PNR and then your next operation.

Operation: Cancel Entire Itinerary

To recapitulate - an itinerary is a list of a passenger's travel arrangements. It can include flight information, hotel and car rental information, and any other miscellaneous information.

This query is a request to cancel the entire itinerary from the PNR and place the segments in the PNRs history. Evidently, the value used to cancel an itinerary is the letter 'I'.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Cancel Itinerary

This query is a request to cancel an itinerary and to End the Transaction. To recapitulate - the End Transaction entry is the last mandatory entry for creating anew PNR or modifying a retrieved PNR.

The PNR optionCode value 10 signals that following the deletion of the itinerary the End of transaction command will be performed by the application.

This is the reply given after removal of the itinerary closely followed by the operation to End of transaction.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Cancel Name Element

This query is a request to cancel a name element, Passenger Tattoo

This illustration signifies that the PNR is an active PNR and or is in current session, hence as the record has not been stored, no Record Locator exists; however manipulation of the PNR can be performed. Important: A PNR must have at least one name element.

The following is an extract of the items that are removed from the returned reply, indicating the canceled passenger name.

Query Structure

Reply Structure

Possible Errors

1959 - NEED PNR

This error is produced when an entry has been made to cancel all the name elements in a PNR. Every PNR must contain at least one name element; hence you are not permitted to perform this action if no name elements are remaining in the PNR.

Operation: Name Integration for Group PNR

This query is a request to cancel a group name element. The group name element can be a maximum of 53 characters in length. The maximum group size is 99 passengers; the group name element can only be entered and modified during PNR creation.

Two name counters appear in the group name: Element to show the number of unnamed and named group members:Unassigned names counter shows how many group members have not yet been named. This decreases as individual name elements are entered. Individual name counter shows how many group members have been named using name element entries. The combination of named and unnamed counters is equal to the total number in the group.

Note: once you have entered the group name, you cannot change the number of passengers in the group name element.

This query is a request to cancel a group name element for one of the travelers.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Remove particular data

The control number is the PNR Record locator number, followed by the action code 0 (Zero).The value 'E' in line 2 declares the type of cancel entry, hence to cancel an element. The 'OT' value signifies the type of element (other). This query is a request to cancel elements with the value 7 and 12, which are both Other elements.

The following is an extract of the data that should be removed from the original PNR depicting the items that have been removed following the cancellation action.

Query Structure

Reply Structure

Possible Errors

1939 - DUPLICATE ELEMENT

If the same data element number has been included more than Once in a cancellation entry, then the duplicate element error is produced.

Function: ChangeElement

Overview

This function provides the element change feature corresponding with the Central System one.

In order to use this interface correctly, user should already be familiar with the Amadeus element change product. This product is used through the element change cryptic entry.

PNR change parameters:

• Element Number (Mandatory)
• New Element Data (Optional)
• New Segment Association (Optional)
• New Passenger Association (Optional)

At least one optional parameter should be filled.

Supported Operations

PNR change element:

• Content element modification
• Segment association modification
• Passenger association modification

Limitations

Not applicable

Unsupported Operations

Not applicable

Prerequisites

User must be Amadeus system user. Record must be held in AAA.

Building A Query

The query should contains a free text according to the relevant change cryptic entry.

The cryptic entry have to match the following format

[element_number]/[new_data]/[segment_association]/[passenger_association]

Receiving A Reply

The reply is a structured message showing new PNR details.

Error Reply Structure

For further information see Retrieve function on PoweredPNR interface.

Error Messages

Operation: PNR Element Change

Here is an example of query modifying the content and the passenger-segment association for the element at the line 5.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section

Function: CreateTSM

Overview

The function CreateTSM creates a TSM with at least:

• one passenger association
• a MD or TSM type (M,E,F,P)

and other data when specified (date, accounting data, reason for issuance code, reason for issuance description, international sales indicator, VAT country).

The presence of some data depends on the market/carrier and the MD type.

This transaction returns the tattoo of the created TSM or an error.

Supported Operations

The TSM creation for a passenger or an infant is not supported.

Limitations

It is only possible to create up to 127 active TSM.

TSM type M,E,F are single passenger associated. Multiple passenger associations are only allowed for TSM type P.

Unsupported Operations

Prerequisites

It is necessary to have an active PNR in the session with at least a passenger name.

Building A Query

Following data are mandatory in the query message:

• passenger tattoo (/mcoData /paxTattoo)
• MD/TSM type (/mcoData /mceDocData /tktNumber /documentDetails /type)

Receiving A Reply

The reply consists in the confirmation of the TSM creation (with passenger and TSM tattoo number) or an error.

Error Reply Structure

 

Error Messages

Operation: Create TSM type E

This query requests the creation of a TSM type E, for an AY ATO/CTO.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type F, BA ATO/CTO

This query requests the creation of a TSM type F, for a BA ATO/CTO.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type F, TASF

This query requests the creation of a TSM type F, TASF, on CH market.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type F, US market

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type M, FR market

This query requests the creation of a TSM type M, for a Travel Agency on French market.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type M, LH ATO/CTO, infant

This query requests the creation of a TSM type M for an infant, for a LH ATO/CTO.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type M, LH ATO/CTO, VAT country DE, RFIC Q for emco

This query requests the creation of a TSM type M, for a LH ATO/CTO, with a VAT country DE, and international indicator Domestic.

Query Structure

Reply Structure

Possible Errors

Operation: Create TSM type P

This query requests the creation of a TSM type P

Query Structure

Reply Structure

Possible Errors

Function: DeleteTSM

Overview

The function DeleteTSM allows deleting:

• all TSM of a given PNR
• all TSM associated to given passenger(s) tattoo
• given TSM(s) based on the TSM tattoo.

Supported Operations

Delete all TSM of an active PNR.
Delete given TSM thanks to their tattoo.
Delete all TSM associated to given passenger(s).

Limitations

TSM tattoo and passenger tattoo cannot be combined.

Unsupported Operations

Prerequisites

Prior to using the function operations, it is necessary to have an active PNR in the session with at least a passenger name.

Building A Query

No data is mandatory to build the query. The criteria to DeleteTSM are optional: passenger tattoo, TSM tattoo.

Receiving A Reply

The reply consists in the confirmation of the deletion with deleted TSM tattoos, or an error.

Error Reply Structure

Error Messages

Operation: Delete all TSM of a PNR

The query is used to delete all existing TSMs of a given PNR: 37L35E'.

Query Structure

Reply Structure

Possible Errors

Operation: Delete by passengers tattoo

The query deletes all TSM for passenger 1 and 3

Query Structure

Reply Structure

Possible Errors

Operation: Delete by TSM tattoo

The query deletes TSMs with tattoo 5 and 7

Query Structure

Reply Structure

Possible Errors

Function: DisplayHistory

Overview

The DisplayHistory function is used to retrieve the history of a PNR.

It is possible to retrieve all the PNR history, or a filtered view of it by using predicates in the query.

Supported Operations

PNR history retrieve.

Limitations

Not applicable.

Unsupported Operations

Not applicable.

Prerequisites

Not applicable.

Building A Query

Following data is mandatory in the query message:

in the Reservation Control Information (/pnrInfo /reservation):

• controlNumber: Amadeus PNR record locator
• date: the date when the PNR has been created.
  The format is: 4 digits for year, 2 digits for month, 2 digits for day
• time: the time when the PNR has been created.
  The format is: 2 digits for hours, 2 digits for minutes

in /redundantElements /selectionDetails:

• option indicating whether redundant elements (as robotic tool looping updates) have to be filtered out or not from the PNR display.

It is also possible to add up to 20 filter options (named predicate) in order to filter the PNR history lines that will be returned.

There are different types of filter options: they can be used to select certain history lines matching a criterion, or they can be used to exclude history lines matching a criterion. The filter options can be combined.

Each filter option is consisting of a:

• selectionDetails segment to indicate the type of filter

and one of the following:

• rangeDetails segment to indicate a range of envelope to match
• predicateElementType segment to indicate a type of element to match
• predicateFreeText Information segment to indicate a freetext to match

/predicate /predicateDetails /selectionDetails segment:

Mandatory:

• option

• optionInformation

Optional:

• option

• optionInformation

/predicate /predicateDetails /rangeDetails segment:

At least one of the two min and max value needs to be set, corresponding to the minimum and maximum envelope number to match.

/predicate /predicateDetails /predicateElementType Segment:

Mandatory:

• segmentName

Optional:

It is also possible to precise the tattoo number to get history lines corresponding to a particular element.

• reference /qualifier

• reference / tattoo number

Here are some examples of possible filter options:

• To select a range of history envelope, by giving the minimum and/or the maximum envelope number.

  selectionDetails segment

  • option: SEL
  • optionInformation: 0

  rangeDetails segment

  • min envelope number: 5
  • max envelope number: 15
• To select history lines concerning one or several element types.

  selectionDetails segment

  • option: SEL
  • optionInformation: 0

  a group of predicateElementType Segments (all remarks)

  • RM
  • RC
  • RX
  • RI
  • RQ
• To filter queuing lines.

  selectionDetails segment

  • option: FIL
  • optionInformation: 0
  • option: QUE
  • optionInformation: 1
• To select history lines containing some specific text.

  selectionDetails segment

  • option: FND
  • optionInformation: 0
  
  

  /predicateFreeText /freeText Information segment

  • TEST

It is possible to combine these predicates to have complex queries.

Receiving A Reply

• If the process is successful, the PNR history is returned in a structured way. A follow-up mechanism is in place if the history display is too long to enter in one reply message: in this case, resending the same query with the reference number of the last item retrieved will give the rest of the history display.
• If the process is not successful, an error is sent in the reply message.

Error Reply Structure

The reply will contain:

• the PNR record locator and creation date
• the PNR history lines in PNH segments
• the number of remaining lines and the reference of the last line sent.

In case of error, see the "Error Message" section.

Generic reply with 2 history envelopes

Error Messages

For generic errors the reply contains the record locator if given in the request, the error information and the error message.

Operation: Display a Simple History

This corresponds to PNR history without the queuing actions.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Display all the history

This corresponds to displays the entire PNR history.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Display the history for a range of envelope

This corresponds to displays the PNR history beginning at envelope 3.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Display the History for the Remark elements

This corresponds to display only the PNR history lines concerning the Remark elements (RM, RC, RX, RI), without the queuing actions.

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Operation: Display the history with a freetext filter

This corresponds to display the PNR history lines that contain the freetext 'TEST'

Query Structure

Reply Structure

Possible Errors

See "Error Messages" section.

Function: DisplayTSM

Overview

The function DisplayTSM retrieves all TSM data based on a TSM tattoo number.

The response sends the full data of the TSM. In particular, the Ticketed status is showing whether the TSM has been issued or not.

Supported Operations

Display any existing TSM type M, E, F (TASF only) or P in anactive PNR.

Limitations

The display is for one TSM only.

Unsupported Operations

TSM type F for US market and BA ATO/CTO can't be displayed.

Prerequisites

Prior to using the function operations, it is necessary to have an active PNR in the session with at least a passenger name.

The TSM tattoo is required in case of multi TSM in the PNR.

Building A Query

Following data are mandatory in the query message:

• passenger name (except for TSM type P)
• TSM tattoo

The query has the same format for all TSM types.

Receiving A Reply

The reply consists in the display of TSM data or an error.

Error Reply Structure

 

Error Messages

Operation: Display a TSM

This query requests the display of the TSM 3. The query is the same for all TSM types.

Query Structure

Reply Structure

Possible Errors

Function: ListTSM

Overview

The function ListTSM proposes a list of all the TSM contained in a PNR (all types). A TSM is indexed with its tattoo, its type and its passenger association(s). It can be filtered by passenger tattoo or type and/or by MDtype.
The list is not sorted.

Deleted TSM are not taken into account.

Supported Operations

Display all TSMs of an active PNR.
Display list of TSMs for a given passenger and/or with agiven type.
Display list of TSMs for a given passenger type and/or witha given type.

Limitations

The number of TSM that can be displayed is limited to 127. Deleted TSMs don't appear in the list.

Unsupported Operations

Display list of TSMs for several passengers.

Prerequisites

Prior to using the function operations, it is necessary to have an active PNR in the session with at least a passenger name.

Building A Query

No data is mandatory to build the query. The criteria to list TSM are optional: passenger tattoo, passenger type, MD/TSM type.

Receiving A Reply

The reply consists in the display of a TSM list with passenger association, MD/TSM type and tattoo, or an error.

Error Reply Structure

Error Messages

Operation: List all the TSM contained in PNR

The query is to list all existing TSMs of agiven PNR: 37L35E.