V2
User’s Guide
|
|
|
ABOUT THE POWERED PNR REPLY STRUCTURE
Two types of information about the PNR may be returned in the Structured PNR Reply;
|
· |
Active PNR Data - Data Elements which currently exist in the PNR |
|
· |
Historical PNR Data - A record of data elements which have been changed in the PNR. |
The Powered PNR Reply structure is returned for queries received from the following API interfaces;
POWERED PNR CREATE
When an element is added to the PNR, the contents of the PNR reflecting the new element(s) are returned.
POWERED PNR RETRIEVE
When a request to retrieve a PNR is made, if an exact match for the PNR requested is found in the system, the contents of the requested PNR is returned.
However, if no exact match is found then the PNR Reply structure is not returned. A similar name list will be returned first from which the exact PNR must be chosen before the contents are returned.
POWERED PNR CANCEL
When an element is canceled in the PNR, the remaining contents of the PNR are returned.
POWERED PNR SPLIT
Each time a split operation is made, the entire contents of the PNR is returned for the split PNR information to allow for split modifications. After which, the remaining contents of the original PNR is then returned for the split finalization.
An exact match on the PNR data must exist when requesting the contents of a PNR, or an error will be received.
Active PNR data pertains to all current information within the PNR. The active data will be returned, regardless of whether the record has been filed in the Amadeus system or is being newly created.
Each Amadeus PNR may contain up to 99 active elements. The contents of these elements are returned via the POWERED PNR Reply Structure when requested.
Only flight segments that contain a departure date not more than 2 days of the current date are considered active PNR data.
2.1.1.2. All other PNR Elements
All other elements existing in the PNR are considered active elements at all times.
Where elements have been changed, only the new information from the last change taken place will be considered as active data.
Any canceled elements will not be considered as active PNR data elements from the time of cancellation.
At this time, MCO information within a PNR will not be returned in the Powered PNR Reply structure.
The TSTdata element is restricted from being used in the PNRReply function. The equivalent functionality can be obtained from the PoweredTicket interface, using the function DisplayTST.
Any queries via the Amadeus API Cryptic interface will not receive the Powered PNR Reply structure.
An active PNR in the session must exist or an exact match on the PNR data must exist when requesting the contents of a PNR.
A PNR contains many different elements holding travel information and accommodations for passengers. Each element is referenced in the PNR storage as a "segment" and qualified with a "tattoo" referencing the relation to the type of segment it is in the PNR. After which, each tattooed item then is assigned a tattoo reference number used for element associations and modifications.
To simplify the PNR storage structure, the PNR elements are broken down and separated into categories within this document.
2.4.1.1. Categories and Tattoos
The reply elements are categorized and tattooed as follows:
2.4.1.1.1. PNR header elements
All elements pertaining to the overall PNR structure, identity, and security. These elements do not contain a segment tattoo, as they are not referencing a particular segment type in the PNR.
|
PNR Header Elements |
Non Tattoo Elements |
|
· |
Company ID |
|
· |
PNR Record Locator |
|
· |
Date and Time Stamp |
|
· |
PNR Security Elements |
|
· |
Special PNR Remarks |
All elements containing name information. These elements contain a passenger tattoo, as they are in direct relation to passenger name segments.
|
NAME ELEMENTS: |
Passenger Tattoo (PT) Elements |
|
· |
Group Name Element |
|
· |
Passenger Name Elements |
All elements holding a reservation for passengers (I.e., cars, hotels, flights, miscellaneous, etc.). These elements contain a segment tattoo, as they are in direct relation to any itinerary segments.
|
ITINERARY ELEMENTS: |
Segment Tattoo (ST) Elements |
|
· |
Automated Car Auxiliary Segment Elements |
|
· |
Automated Hotel Auxiliary Segment Elements |
|
· |
Ferry Segment Elements |
|
· |
Flight Segment Elements |
|
· |
Ground Transportation Segment Elements |
|
· |
Non-Automated Air Taxi Auxiliary Segment Elements |
|
· |
Non-Automated Car Auxiliary Segment Elements |
|
· |
Non-Automated Hotel Auxiliary Segment Elements |
|
· |
Non-Automated Miscellaneous Auxiliary Segment Elements |
|
· |
Non-Automated Tour Auxiliary Segment Elements |
|
· |
Cruise Segment Element |
|
· |
Tour Source Segment Elements |
|
· |
Tour Segment Elements |
|
· |
Train (Amtrak) Segment Elements |
|
· |
Train (SNCF) Segment Elements |
All elements containing information and instructions for generating PNR documents. These elements contain an other tattoo, as they are in relation to segments other than itinerary or passenger relation segments.
|
DOCUMENT ELEMENTS: |
Other Tattoo (OT) Elements |
|
· |
Automated Invoice Number Elements |
|
· |
Billing Address Elements |
|
· |
Invoice Adjustment Remark Element |
|
· |
Invoice Remark Elements |
|
· |
Invoice and Itinerary Remark Elements |
|
· |
Itinerary Remark Elements |
|
· |
Invoice Service Fee Remark Elements |
|
· |
Mailing Address Elements |
|
· |
Manual Documentation Registration Elements |
|
· |
Mini Office Profile Invoice Agency Billing Information Remark Elements |
|
· |
Mini Office Profile Due Date and Agency Billing Remark Element |
|
· |
Mini Office Profile Itinerary Remark Elements |
|
· |
Mini Office Profile Invoice Remark Elements |
|
· |
Miscellaneous Charges Order Element |
|
· |
Miscellaneous Ticketing Information Elements |
|
· |
Original Issue/Issue in Exchange For Element |
|
· |
Override Invoice Total Amount Remark Element |
|
· |
Ticketing Carrier Designator Elements |
|
· |
Ticket Number for Automated Tickets Elements |
|
· |
Transmission Control Number Element |
All elements containing information and instructions regarding the pricing and payment of the PNR itinerary elements. These elements contain an other tattoo, as they are in relation to segments other than itinerary or passenger relation segments.
|
FARE ELEMENTS: |
Other Tattoo (OT) Elements |
|
· |
Fare Commission Elements |
|
· |
Fare Discount Elements |
|
· |
Fare Endorsement/Restriction Elements |
|
· |
Fare Print Override elements |
|
· |
Form of Payment Elements |
2.4.1.1.6. Information elements
All elements containing information for viewing only. These elements contain an other tattoo, as they are in relation to segments other than itinerary or passenger relation segments.
|
INFORMATIONAL ELEMENTS: |
Other Tattoo (OT) Elements |
|
· |
Address Verification Elements |
|
· |
Confidential Remark Elements |
|
· |
Contact Elements |
|
· |
Individual PNR Security Elements |
|
· |
Miscellaneous Information Elements |
|
· |
Option Element |
|
· |
Other Special Information Elements |
|
· |
Travel Assistance Elements |
|
· |
Tour Code Elements |
|
· |
Train Pending Acknowledgement Elements |
2.4.1.1.7. Accounting elements
All elements containing information and instructions for back office accounting systems. These elements contain an other tattoo, as they are in relation to segments other than itinerary or passenger relation segments.
|
ACCOUNTING ELEMENTS: |
Other Tattoo (OT) Elements |
|
· |
Accounting Information Elements |
|
· |
AIR Sequence Number Elements |
|
· |
Back Office Information Elements |
|
· |
Shadow AIR Sequence Number Elements |
|
· |
Shadow Destination Elements |
When navigating through the reply structures, the elements are indexed and sub-indexed. Repetitive information is identified by "[N] " after the field identifier.
The following partial structure illustrates the indexing method used. Notice that there are 3 passenger names each indexed [1] - [3] with associated sub-indexing on name [1], followed by two itinerary elements [1] - [2] with associated sub-indexing in both.
|
INDEXING |
Powered PNR Reply - Data Elements |
Data |
|
Name 1 |
/travellerInfo [1]/elementManagementPassenger/reference/qualifier |
PT |
|
/travellerInfo [1]/elementManagementPassenger/reference/number |
3 |
|
|
/travellerInfo [1]/elementManagementPassenger/segmentName |
NM |
|
|
/travellerInfo [1]/elementManagementPassenger/lineNumber |
3 |
|
|
/travellerInfo [1]/travellerInformation/traveller/surname |
LEAVEY |
|
|
/travellerInfo [1]/travellerInformation/traveller/quantity |
2 |
|
|
/travellerInfo [1]/travellerInformation/passenger[1]/firstName |
KIM |
|
|
/travellerInfo [1]/travellerInformation/passenger[1]/infantIndicator |
1 |
|
|
/travellerInfo [1]/travellerInformation/passenger[2]/firstName |
MICHAEL |
|
|
/travellerInfo [1]/travellerInformation/passenger[2]/type |
INF |
|
|
Name 2 |
/travellerInfo [2]/elementManagementPassenger/reference/qualifier |
PT |
|
/travellerInfo [2]/elementManagementPassenger/reference/number |
5 |
|
|
/travellerInfo [2]/elementManagementPassenger/segmentName |
NM |
|
|
/travellerInfo [2]/elementManagementPassenger/lineNumber |
4 |
|
|
/travellerInfo [2]/travellerInformation/traveller/surname |
SMITH |
|
|
/travellerInfo [2]/travellerInformation/traveller/quantity |
1 |
|
|
/travellerInfo [2]/travellerInformation/passenger/firstName |
JOHN |
|
|
/travellerInfo [3]/elementManagementPassenger/reference/qualifier |
PT |
|
|
/travellerInfo [3]/elementManagementPassenger/reference/number |
6 |
|
|
Name 3 |
/travellerInfo [3]/elementManagementPassenger/segmentName |
NM |
|
/travellerInfo [3]/elementManagementPassenger/lineNumber |
5 |
|
|
/travellerInfo [3]/travellerInformation/traveller/surname |
SMITH |
|
|
/travellerInfo [3]/travellerInformation/traveller/quantity |
1 |
|
|
/travellerInfo [3]/travellerInformation/passenger/firstName |
KARIN |
|
|
/travellerInfo [3]/travellerInformation/passenger/type |
CHD |
|
|
/travellerInfo [3]/travellerInformation/passenger/identificationCode |
ID23784 |
|
|
Itinerary Element 1 |
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/reference/qualifier |
ST |
|
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/reference/number |
1 |
|
|
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/segmentName |
CCR |
|
|
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/lineNumber |
6 |
|
|
/originDestinationDetails/itineraryInfo [1]/travelProduct/product/depDate |
220701 |
|
|
/originDestinationDetails/itineraryInfo [1]/travelProduct/product/arrDate |
250701 |
|
|
/originDestinationDetails/itineraryInfo [1]/travelProduct/boardpointDetail/cityCode |
NCE |
|
|
/originDestinationDetails/itineraryInfo [1]/travelProduct/companyDetail/identification |
AI |
|
|
/originDestinationDetails/itineraryInfo [1]/travelProduct/productDetails/identification |
EBMN |
|
|
/originDestinationDetails/itineraryInfo [1]/itineraryMessageAction/business/function |
2 |
|
|
/originDestinationDetails/itineraryInfo [1]/relatedProduct/quantity |
01 |
|
|
/originDestinationDetails/itineraryInfo [1]/relatedProduct/status |
HK |
|
|
/originDestinationDetails/itineraryInfo [1]/selectionDetails/selection/option |
P10 |
|
|
Sub-Index 1 |
/originDestinationDetails/itineraryInfo [1]/generalOption[1]/optionDetail/type |
BS |
|
/originDestinationDetails/itineraryInfo [1]/generalOption[1]/optionDetail/freetext |
00000000 |
|
|
Sub-Index 2 |
/originDestinationDetails/itineraryInfo [1]/generalOption[2]/optionDetail/type |
ARR |
|
/originDestinationDetails/itineraryInfo [1]/generalOption[2]/optionDetail/freetext |
0800 |
|
|
Sub-Index 3 |
/originDestinationDetails/itineraryInfo [1]/generalOption[3]/optionDetail/type |
RC |
|
/originDestinationDetails/itineraryInfo [1]/generalOption[3]/optionDetail/freetext |
SD-BASIC |
|
|
Sub-Index 4 |
/originDestinationDetails/itineraryInfo [1]/generalOption[4]/optionDetail/type |
RG |
|
/originDestinationDetails/itineraryInfo [1]/generalOption[4]/optionDetail/freetext |
FRF 179.00- .00 UNL DY |
|
|
Sub-Index 5 |
/originDestinationDetails/itineraryInfo [1]/generalOption[5]/optionDetail/type |
RT |
|
/originDestinationDetails/itineraryInfo [1]/generalOption[5]/optionDetail/freetext |
1600 |
|
|
/originDestinationDetails/itineraryInfo [1]/referenceForSegment/reference/qualifier |
PT |
|
|
/originDestinationDetails/itineraryInfo [1]/referenceForSegment/reference/number |
1 |
|
|
Itinerary Element 2 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/qualifier |
ST |
|
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/number |
2 |
|
|
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/segmentName |
HHL |
|
|
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/lineNumber |
7 |
|
|
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/depDate |
220701 |
|
|
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/arrDate |
250701 |
|
|
/originDestinationDetails/itineraryInfo [2]/travelProduct/boardpointDetail/cityCode |
NCE |
|
|
/originDestinationDetails/itineraryInfo [2]/travelProduct/companyDetail/identification |
RB |
|
|
/originDestinationDetails/itineraryInfo [2]/itineraryMessageAction/business/function |
3 |
|
|
/originDestinationDetails/itineraryInfo [2]/relatedProduct/quantity |
01 |
|
|
/originDestinationDetails/itineraryInfo [2]/relatedProduct/status |
HK |
|
|
/originDestinationDetails/itineraryInfo [2]/selectionDetails/selection/option |
P10 |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/providerName |
RESORT BOOKINGS |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/code |
326 |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/name |
CITADINES AV DES FLEURS APARTHOTEL |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/occupancy |
1 |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/typeCode |
T** |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/negotiated/rateCode |
RAC |
|
|
/originDestinationDetails/itineraryInfo [2]/hotelProduct/otherHotelInfo/currencyCode |
EUR |
|
|
/originDestinationDetails/itineraryInfo [2]/rateInformations/ratePrice/rateAmount |
80.00 |
|
|
/originDestinationDetails/itineraryInfo [2]/rateInformations/rateInfo/ratePlan |
DY |
|
|
Sub-Index 1 |
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/type |
DP |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/freetext |
CCVI4974830544671492EXP0901 |
|
|
Sub-Index 2 |
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/type |
TTL |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/freetext |
EUR240.00 |
|
|
Sub-Index 3 |
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/type |
NGT |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/freetext |
03 |
|
|
Sub-Index 4 |
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/type |
NAM |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/freetext |
CITADINES AV DES FLEURS APARTHOTEL |
|
|
Sub-Index 5 |
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/type |
BS |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/freetext |
01234567 |
|
|
Sub-Index 6 |
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/type |
CF |
|
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/freetext |
............ |
|
|
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/qualifier |
PT |
|
|
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/number |
1 |
2.5. ELEMENT: PNR HEADER ELEMENTS
The PNR header elements pertain to elements identifying the PNR record and security. These elements are either entered by the agent or automatic system elements that are added to the PNR at the time of creation.
The company ID identifies the reservation company code responsible for creating the PNR.
Generally, the company ID code will reflect Amadeus (1A) as the system responsible.
The following is an extract of the POWERED PNR Reply structure to illustrate the PNR Company ID element content outlined below:
|
Parameter |
Information |
|
Company ID |
1A |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/pnrHeader/reservationInfo/reservation/ |
1A |
2.5.2. PNR Record Locator Element
A unique six-character system Identification is assigned to each PNR at creation time. This record locator is returned with each PNR.
The following is an extract of the POWERED PNR Reply structure to illustrate the PNR record locator element content outlined below:
|
Parameter |
Information |
|
Record Locator |
X2RHZR |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/pnrHeader/reservationInfo/reservation/ |
1A |
|
/PoweredPNR_PNRReply/pnrHeader/reservationInfo/reservation/ |
X2RHZR |
2.5.3. Date and Time Stamp Element
At End of Transaction, the date and time that the PNR was filed are automatically stored as part of the PNR header.
The following is an extract of the POWERED PNR Reply structure to illustrate the date and time stamp element content outlined below:
|
Parameter |
Information |
|
Last EOT Date |
170501 |
|
Last EOT Time |
0754 |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/pnrHeader/reservationInfo/reservation/ |
170501 |
|
/PoweredPNR_PNRReply/pnrHeader/reservationInfo/reservation/ |
0754 |
At the time of creation, the following elements are stored in the PNR to clearly identify the ownership of the record;
|
Parameter |
Information |
|
Agent Id |
Mandatory PNR information entered by the agent to identify the agent responsible for the creation or change to the PNR. |
|
Office ID |
Office ID responsible for the ownership of the PNR. This parameter is automatically stored as the office ID of the creating location. |
|
Queuing Office ID |
Office ID responsible for managing the PNR. If no queuing office ID is specified the default ID of the creating location is automatically stored. |
|
City Code |
3 character city code where the PNR is created |
|
Creation office ID |
Office ID responsible for the creation of the PNR. This parameter is automatically stored from the creating session system identification. |
|
Agent signature |
Full agent system sign in automatically stored from the creating session sign in. |
|
Creation Date |
Date the PNR was created in the system. |
2.5.4.1. Specific Structural Elements
The PNR security elements are grouped together and identified as PNR Responsibility Parameters (RP) elements. [I.e., /PoweredPNR_PNRReply/securityInformation/
responsibilityInformation/typeOfPnrElement]
The following is an extract of the POWERED PNR Reply structure to illustrate the security element contents outlined below:
|
Parameter |
Information |
|
Agent Id |
AFRM |
|
Office ID |
VSTNA2150 |
|
Queuing Office ID |
VSTNA2150 |
|
City Code |
VST |
|
Creation office ID |
VSTNA2150 |
|
Agent signature |
0001AA |
|
Creation Date |
170501 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/securityInformation/ |
RP |
|
1 |
/PoweredPNR_PNRReply/securityInformation/ |
AFRM |
|
2 |
/PoweredPNR_PNRReply/securityInformation/ |
VSTNA2150 |
|
3 |
/PoweredPNR_PNRReply/securityInformation/ |
VSTNA2150 |
|
4 |
/PoweredPNR_PNRReply/securityInformation/cityCode |
VST |
|
5 |
/PoweredPNR_PNRReply/securityInformation/ |
VSTNA2150 |
|
6 |
/PoweredPNR_PNRReply/securityInformation/ |
0001AA |
|
7 |
/PoweredPNR_PNRReply/securityInformation/ |
170501 |
2.5.5. Special PNR Header Remarks
At the time of creation, special remarks may be automatically stored in the header area to identify anything special about the PNR. (I.e., if it is a split PNR, etc) Coinciding with the special remark system limitations, a maximum of 9 remark codes may be returned.
2.5.5.1. Specific Structural Elements
2.5.5.1.1. Element Identifiers
2.5.5.1.1.1. Subject qualifier and type
The PNR special remark elements are grouped together as free text data identified with a special subject qualifier and type:
|
Free Flow Subject Qualifier |
3 - literal text |
|
Free Flow Text Type |
P12 - tag line in PNR header |
|
Remark Code |
Special remark code stored in the PNR |
The following codes may be returned identifying special conditions in the PNR;
|
Code |
Description |
|
AXR |
Split Party Record |
|
HFR |
Historical fare record |
|
MRG |
Merged PNR retrieval |
|
MSC |
Married segment condition |
|
NHP |
Non-homogeneous PNR |
|
PTA |
Pre-paid ticket |
|
RLP |
Record was created from a customer Profile and the profiles is associated to the PNR. |
|
RLR |
Record locator returned |
|
TPM |
Telepayment |
|
TC-XXX |
The record has been created from a customer Profile using travel choice. XXX representing the 3 character trip purpose. |
|
TST |
Transitional Stored Ticket |
The following is an extract of the POWERED PNR Reply structure to illustrate a special remark identifying the special remark code of RLR in the PNR header information.
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/freetextData/freetextDetail/ |
3 |
|
/PoweredPNR_PNRReply/freetextData/freetextDetail/type |
P12 |
|
/PoweredPNR_PNRReply/freetextData/longFreetext |
--- RLR --- |
Name elements pertain to the passenger names stored in the PNR. Coinciding with the minimum and maximum restrictions for name elements in a PNR,
|
· |
The minimum number of name elements returned in the Powered PNR Reply structure is 1 and the maximum is 99. |
|
· |
Each name item may contain a maximum of 60 characters, including Passenger Type Code, ID code, and Special Passenger association. |
Name elements can be simple elements containing only the last name and first name of the passenger, complex elements containing passenger type codes and/or Ids, or group name elements.
2.6.1. Specific Structural Elements
The following structural elements are specific to the name elements when they are returned in the Powered PNR Reply Structure;
Each name element is identified with a reference qualifier and segment name ID.
2.6.1.1.1. Reference Qualifier
2.6.1.1.1.1. Normal name elements
Each name element is identified with a reference qualifier [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/2.6.1.1.1.2. Group Name Elements
Each group name element is identified with a reference qualifier [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/However, the individual names associated to the group name hold true to the normal qualifier type of PT.
2.6.1.1.2.1. Normal Name Elements
Each name element is identified with a segment name ID [I.e.,/travellerInfo
[2]/elementManagementPassenger/segment name] of NM in the reply structure.2.6.1.1.2.2. Group Name Elements
Each group name element is identified with a segment name ID [I.e.,/travellerInfo
[2]/elementManagementPassenger/segment name] of NG in the reply structure.However, the individual names associated to the group name hold true to the element segment name ID of NM.
Each name element has an associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This item tattoo number indicating the order in which the names are stored within the Amadeus PNR. (Generally, the names are stored in alphabetical order.) It is used to identify the specific name element for any subsequent modifications or cancellations.Each name element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the names were created within the Amadeus PNR.Each surname element has an associated quantity element [I.e., /PoweredPNR_PNRReply/travellerInfo
[1]/travellerInformation/
A simple name element in this situation is pertaining to a name element containing only the following parameters;
|
Surname |
|
|
First name |
|
The following is an extract of the POWERED PNR Reply structure to illustrate the simple name element outlined below:
|
Parameter |
Information |
|
Reference Number |
5 |
|
Line Number |
4 |
|
Surname |
SMITH |
|
Quantity |
1 |
|
First name |
JOHN MR |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/travellerInfo [4]/elementManagementPassenger/reference/qualifier |
PT |
|
/PoweredPNR_PNRReply/travellerInfo [4]/elementManagementPassenger/reference/number |
5 |
|
/PoweredPNR_PNRReply/travellerInfo [4]/elementManagementPassenger/segmentName |
NM |
|
/PoweredPNR_PNRReply/travellerInfo [4]/elementManagementPassenger/lineNumber |
4 |
|
/PoweredPNR_PNRReply/travellerInfo [4]/travellerInformation/traveller/surname |
SMITH |
|
/PoweredPNR_PNRReply/travellerInfo [4]/travellerInformation/traveller/quantity |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [4]/travellerInformation/passenger/firstName |
JOHN MR |
A complex name element in this situation pertains to a simple name element with any of the following additional optional name parameters;
|
Passenger Type Code |
|
|
Passenger ID Code |
|
|
Special Passenger Associations (i.e., Infant, Extra Seat, etc) |
Three letter passenger type codes may be included with a name to indicate the type of passenger.
The system uses the passenger type code for fare pricing and to create special information elements that identify the status of a passenger. Coinciding with the PNR restrictions, the maximum number of passenger type codes returned in the Powered PNR Reply structure is 1, except when using passenger type codes of INF or CHD. In which case, a maximum number of two are allowed.
The following code set is applied to passenger type codes returned in the Powered PNR Reply Structure;
Amadeus passenger types
|
ACC |
Accompanied Person |
|
ACP |
Test data |
|
ADT |
Adult |
|
AGT |
Agent |
|
Ann (1) |
Companion |
|
ASB |
Adult Standby |
|
ASF |
Air-Sea Fare |
|
BAG |
Excess Baggage |
|
BLD |
Blind Passenger |
|
BRV |
Bereavement |
|
BUD |
Airline Buddy Standby Fare |
|
CHD (2) |
Child |
|
CLG |
Clergy |
|
CMA |
Adult with Companion |
|
CMM |
Commuter |
|
CMP |
Companion |
|
CMX |
ANN - CMP - CMA - Blended |
|
Cnn (1) |
Accompanied Child |
|
CNV |
Convention |
|
CPN |
Coupon Discount Passenger |
|
CTZ |
Category Z Passenger |
|
DOD |
Department Of Defense Passenger |
|
EMI |
Emigrant |
|
Enn (1) |
Group Inclusive tour Child |
|
FDT |
Head of Family |
|
FFY |
Frequent Flyer |
|
Fnn (1) |
Family Plan Child |
|
FTF |
Frequent Flyer |
|
GCF |
Government Contract |
|
GCT |
City/Council Government Passenger |
|
GDP |
Government Employee Dependent |
|
GEX |
GovernmentExchange Passenger |
|
GIT |
Group Inclusive Tour Passenger |
|
GMZ |
GOV / CT / MIL / CATZ |
|
Gnn (1) |
Group Child |
|
GOV |
GVT Blended |
|
GRP |
Group Passenger |
|
GTF |
Government Travel |
|
GST |
State Government |
|
GVM |
GOV / GOVCT / CATZ |
|
GVT |
Government Travel |
|
GVZ |
Government / GOVCT / CATZ |
|
HOF |
Head of Family |
|
HCR |
Adult Charter |
|
HNN |
Children Charter |
|
ICP |
Incentive Certificates |
|
IIT |
Individual Inclusive Tour Passenger |
|
INF (2) |
Infant not Occupying a Seat |
|
Inn (1) |
Individual Inclusive Tour Child |
|
INS |
Infant Occupying a Seat |
|
ITX |
Individual Inclusive Tour Passenger |
|
JOB |
Job Corps |
|
LBR |
Laborer / Worker |
|
MBT |
Military - basic Training Graduate |
|
MCR |
Military Charter |
|
MDP |
Spouse and Dependent Children of Military Personnel |
|
MED |
Patients Travel for Medical treatment |
|
MFM |
Military Immediate family |
|
MIL |
Military Confirmed passenger |
|
MIR |
Military Reserve on Active Duty |
|
MIS |
Missionary |
|
MLZ |
Military / Cat. Z |
|
Mnn (1) |
Military Child |
|
MPA |
Military Parents / Parents in Law |
|
MRE |
Retired military and Dependent |
|
MSB |
Military Standby |
|
MUS |
Military DOD based in USA |
|
MSG |
Multi State Government |
|
MXS |
Military DOD not based in USA |
|
NAT |
NATO |
|
NSB |
Non Revenue Standby |
|
OTS |
Passenger Occupying two seats |
|
PCR |
Adult Charter |
|
Pnn (1) |
Children Charter |
|
PFA |
Private Fare |
|
PFB |
Private Fare |
|
PFC |
Private Fare |
|
PFD |
Private Fare |
|
PFE |
Private Fare |
|
PFF |
Private Fare |
|
PFG |
Private Fare |
|
PFH |
Private Fare |
|
PFI |
Private Fare |
|
PFJ |
Private Fare |
|
PFK |
Private Fare |
|
PFL |
Private Fare |
|
PFM |
Private Fare |
|
PFN |
Private Fare |
|
PFO |
Private Fare |
|
PFP |
Private Fare |
|
PFQ |
Private Fare |
|
PFR |
Private Fare |
|
PFS |
Private Fare |
|
PFT |
Private Fare |
|
PFU |
Private Fare |
|
PFV |
Private Fare |
|
PFW |
Private Fare |
|
PFX |
Private Fare |
|
PFY |
Private Fare |
|
PFZ |
Private Fare |
|
REC |
Military Recruit |
|
REF |
Refugee |
|
SDB |
Student Standby |
|
SEA |
Seaman |
|
Snn (1) |
Senior Citizen |
|
SPS |
Spouse |
|
SRC |
Senior Citizen |
|
STR |
State Resident |
|
STU |
Student |
|
Tnn (1) |
Frequent Flyer Child |
|
TUR |
Tour Conductor |
|
UAM |
Unaccompanied Minor |
|
Unn (1) |
Unaccompanied Child |
|
UNV |
University Employee |
|
VAC |
Visit Another Country Adult |
|
VAG |
Visit Another Country Adult |
|
VFR |
Visit Friends Relatives |
|
Vnn (1) |
Visit Another Country Child |
|
YCB |
Senior Citizen Standby |
|
YCD |
Senior Citizen |
|
YCL |
Clergy |
|
YCR |
Youth Charter |
|
YMZ |
Category Z Passenger |
|
Ynn (1) |
Government Travel Child |
|
YSB |
Youth Standby |
|
YTH |
Youth Confirmed |
|
Znn (1) |
Group Visit Another |
(1) NN = Maximum of two numeric following the first Alpha character in the passenger type. Example - (S03)
These passenger types generate automatically an OSI in the face of the PNR which is transmitted to the corresponding airline via teletype
The following is an extract of the POWERED PNR Reply structure to illustrate a complex name element with a Passenger Type Code as outlined below:
|
Parameter |
Information |
|
Reference Number |
2 |
|
Line Number |
2 |
|
Surname |
JONES |
|
Quantity |
1 |
|
First name |
JIM |
|
Passenger Type Code |
CHD (child) |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/travellerInfo [2]/elementManagementPassenger/reference/qualifier |
PT |
|
/PoweredPNR_PNRReply/travellerInfo [2]/elementManagementPassenger/reference/number |
2 |
|
/PoweredPNR_PNRReply/travellerInfo [2]/elementManagementPassenger/segmentName |
NM |
|
/PoweredPNR_PNRReply/travellerInfo [2]/elementManagementPassenger/lineNumber |
2 |
|
/PoweredPNR_PNRReply/travellerInfo [2]/travellerInformation/traveller/surname |
JONES |
|
/PoweredPNR_PNRReply/travellerInfo [2]/travellerInformation/traveller/quantity |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [2]/travellerInformation/passenger/firstName |
JIM |
|
/PoweredPNR_PNRReply/travellerInfo [2]/travellerInformation/passenger/type |
CHD |
The passenger ID Code is a special type of passenger code used for entering an ID number for identification purposes. Such information could include staff number, or date of birth.
The ID code may be returned in combination with any passenger type code element.
2.6.3.2.1. Reply Structure of Passenger ID Code
The following is an extract of the POWERED PNR Reply structure to illustrate a complex name element with a Passenger ID Code as outlined below:
|
Parameter |
Information |
|
Reference Number |
1 |
|
Line Number |
1 |
|
Surname |
CASEY |
|
Quantity |
1 |
|
First name |
BILL |
|
Passenger ID Code |
ID251874 |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/travellerInfo [1]/elementManagementPassenger/reference/qualifier |
PT |
|
/PoweredPNR_PNRReply/travellerInfo [1]/elementManagementPassenger/reference/number |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [1]/elementManagementPassenger/segmentName |
NM |
|
/PoweredPNR_PNRReply/travellerInfo [1]/elementManagementPassenger/lineNumber |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [1]/travellerInformation/traveller/surname |
CASEY |
|
/PoweredPNR_PNRReply/travellerInfo [1]/travellerInformation/traveller/quantity |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [1]/travellerInformation/passenger/firstName |
BILL |
|
/PoweredPNR_PNRReply/travellerInfo [1]/travellerInformation/passenger/identificationCode |
ID251874 |
2.6.3.3. Special Passenger Associations
There is a special passenger type code (INF) for infants travelling with an adult passenger. This type code is exceptional, as it is entered with the accompanying adult passenger and triggers appropriate messages to be sent to the associated airlines.
Additionally, a name may be returned with the infant passenger type code to identify the name of the infant.
The infant information may be returned in combination with any other normal passenger type code, including an ID code, for the associated passenger.
When an infant association exists for a passenger, in the PNR Reply structure the associated name is tagged with an infant indicator [/PoweredPNR_PNRReply/travellerInfo
[3]/travellerInformation/2.6.3.3.1.1. Reply Structure of Associated Infant Passenger
The following is an extract of the POWERED PNR Reply structure to illustrate a complex name element with an Associated Infant Passenger as outlined below:
|
Parameter |
Information |
|
Reference Number |
3 |
|
Line Number |
3 |
|
Surname |
LEAVEY |
|
Quantity |
2 |
|
First name |
KIM |
|
Infant name |
MICHAEL |
|
Passenger Type Code |
INF |
|
PoweredPNR_PNRReply - Data element |
Value |
|
/PoweredPNR_PNRReply/travellerInfo [3]/elementManagementPassenger/reference/qualifier |
PT |
|
/PoweredPNR_PNRReply/travellerInfo [3]/elementManagementPassenger/reference/number |
3 |
|
/PoweredPNR_PNRReply/travellerInfo [3]/elementManagementPassenger/segmentName |
NM |
|
/PoweredPNR_PNRReply/travellerInfo [3]/elementManagementPassenger/lineNumber |
3 |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/traveller/surname |
LEAVEY |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/traveller/quantity |
2 |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/passenger[1]/firstName |
KIM |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/passenger[1]/infantIndicator |
1 |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/passenger[2]/firstName |
MICHAEL |
|
/PoweredPNR_PNRReply/travellerInfo [3]/travellerInformation/passenger[2]/type |
INF |
2.6.3.3.1.2. Reply Structure of Associated Infant Passenger and Passenger with ID Code
The following is an extract of the POWERED PNR Reply structure to illustrate a complex name element with an Associated Infant Passenger combined with a passenger with an ID code as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
1 |
|
3 |
Line Number |
1 |
|
4 |
Surname |
ERICSSON |
|
5 |
Quantity |
2 |
|
6 |
First name |
ANITA |
|
7 |
Passenger ID Code |
ID24JAN75 |
|
9 |
Infant name |
HANS |
|
10 |
Passenger Type Code |
INF |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/travellerInfo/elementManagementPassenger/reference/ |
PT |
|
1 |
/travellerInfo/elementManagementPassenger/reference/number |
1 |
|
2 |
/travellerInfo/elementManagementPassenger/segmentName |
NM |
|
3 |
/travellerInfo/elementManagementPassenger/lineNumber |
1 |
|
4 |
/travellerInfo/travellerInformation/traveller/surname |
ERICSSON |
|
5 |
/travellerInfo/travellerInformation/traveller/quantity |
2 |
|
6 |
/travellerInfo/travellerInformation/passenger [1]/firstName |
ANITA |
|
7 |
/travellerInfo/travellerInformation/passenger [1]/infantIndicator |
1 |
|
8 |
/travellerInfo/travellerInformation/passenger [1]/identificationCode |
ID24JAN75 |
|
9 |
/travellerInfo/travellerInformation/passenger [2]/firstName |
HANS |
|
10 |
/travellerInfo/travellerInformation/passenger [2]/type |
INF |
When a PNR is created for large parties of between 10 and 99, a group PNR may be created.
A group name is created to reserve the segment space in the reservation for the total number of seats required, before actually having the associated names for the group. Individual names may be added when they are received and therefore, the number of individual names returned in the Powered PNR Reply structure will not always match the total number in the group name elements.
Coinciding with group PNR rules, a maximum of one group name containing the following parameters may be returned in the Powered PNR Reply Structure;
|
Group Name |
|
|
Number in party |
|
|
Individual Name elements |
If the reply structure containing a group name is returned during the initial creation phase (i.e., prior to PNR storage), it is possible to receive "NO NAME" in the Group name parameter.
The following is an extract of the POWERED PNR Reply structure to illustrate a group name element as outlined below:
|
Item # |
Parameter |
Information |
|
3 |
Group Name |
SPECIAL TOURS |
|
5 |
Number in Party |
15 |
|
6-12 |
Passenger Name Element 1 |
Surname: CHILDS First name: Lisa |
|
13-19 |
Passenger Name Element 2 |
Surname: JOHNSON First name: John |
|
19-26 |
Passenger Name Element 3 |
Surname: SMITH First name: John |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
1 |
/travellerInfo [1]/elementManagementPassenger/segmentName |
NG |
|
2 |
/travellerInfo [1]/elementManagementPassenger/lineNumber |
0 |
|
3 |
/travellerInfo [1]/travellerInformation/traveller/surname |
SPECIAL TOURS |
|
4 |
/travellerInfo [1]/travellerInformation/traveller/qualifier |
G |
|
5 |
/travellerInfo [1]/travellerInformation/traveller/quantity |
15 |
|
6 |
/travellerInfo [2]/elementManagementPassenger/reference/qualifier |
PT |
|
7 |
/travellerInfo [2]/elementManagementPassenger/reference/number |
2 |
|
8 |
/travellerInfo [2]/elementManagementPassenger/segmentName |
NM |
|
9 |
/travellerInfo [2]/elementManagementPassenger/lineNumber |
1 |
|
10 |
/travellerInfo [2]/travellerInformation/traveller/surname |
CHILDS |
|
11 |
/travellerInfo [2]/travellerInformation/traveller/quantity |
1 |
|
12 |
/travellerInfo [2]/travellerInformation/passenger/firstName |
LISA |
|
13 |
/travellerInfo [3]/elementManagementPassenger/reference/qualifier |
PT |
|
14 |
/travellerInfo [3]/elementManagementPassenger/reference/number |
4 |
|
15 |
/travellerInfo [3]/elementManagementPassenger/segmentName |
NM |
|
16 |
/travellerInfo [3]/elementManagementPassenger/lineNumber |
2 |
|
17 |
/travellerInfo [3]/travellerInformation/traveller/surname |
JOHNSON |
|
18 |
/travellerInfo [3]/travellerInformation/traveller/quantity |
1 |
|
19 |
/travellerInfo [3]/travellerInformation/passenger/firstName |
JOHN |
|
20 |
/travellerInfo [4]/elementManagementPassenger/reference/qualifier |
PT |
|
21 |
/travellerInfo [4]/elementManagementPassenger/reference/number |
3 |
|
22 |
/travellerInfo [4]/elementManagementPassenger/segmentName |
NM |
|
23 |
/travellerInfo [4]/elementManagementPassenger/lineNumber |
3 |
|
24 |
/travellerInfo [4]/travellerInformation/traveller/surname |
SMITH |
|
25 |
/travellerInfo [4]/travellerInformation/traveller/quantity |
1 |
|
26 |
/travellerInfo [4]/travellerInformation/passenger/firstName |
JOHN |
Notice that the segment name, item number 1 above, for the group name "Special Tours" has been tagged as NG and the qualifier, item number 4 above, has been set to G, to indicate that it is a group name element. Whereas, the passenger name elements, items 8, 15, and 22, are tagged with the normal segment name of NM and qualifier of PT.
2.7. ELEMENT: ITINERARY ELEMENTS
Itinerary elements pertain to any elements stored in the PNR which detail a travel arrangement (I.e., Air, Car, Hotel, etc). Coinciding with the minimum and maximum restrictions for itinerary elements in a PNR, the minimum number of itinerary elements returned in the Powered PNR Reply structure is 1 and the maximum is 99.
The information returned in the Powered PNR Reply structure is dependent upon the type of itinerary element.
2.7.1. Specific Structural Elements
The following structural elements are specific to the itinerary elements when they are returned in the Powered PNR Reply Structure;
2.7.1.1.1. Reference Qualifier
Each itinerary element is qualified [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/
Each itinerary element is identified with a segment name ID [I.e.,/travellerInfo
[2]/elementManagementPassenger/segment name] that reflects the type of itinerary element returned in the reply structure:
|
Segment name ID |
Description |
|
CCR |
Automated Car Auxiliary Segment Elements |
|
HHL |
Automated Hotel Auxiliary Segment Elements |
|
FRR |
Ferry Segment Elements |
|
AIR |
Flight Segment Elements |
|
SUR |
Ground Transportation Segment Elements |
|
AU |
Non-Automated Air Taxi Auxiliary Segment Elements |
|
CAR |
Non-Automated Car Auxiliary Segment Elements |
|
HTL |
Non-Automated Hotel Auxiliary Segment Elements |
|
CRU |
Cruise Segment Elements |
|
MIS |
Non-Automated Miscellaneous Auxiliary Segment Elements |
|
TUR |
Non-Automated Tour Auxiliary Segment Elements |
|
TTO |
Tour Source Segment Elements |
|
TOU |
Tour Segment Elements |
|
TRN |
Train (Amtrak) Segment Elements |
|
TRN |
Train (SNCF) Segment Elements |
Each itinerary element has an associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This line item number is an indication to the order in which the itinerary elements are stored within the Amadeus PNR. (Generally, the itinerary elements are stored in ascending date order.) It is used to identify the specific itinerary element for any subsequent modifications or cancellations.
Each itinerary element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the names were created within the Amadeus PNR.
2.7.1.3.1. Business Function Type
Each itinerary element is identified with business function type [I.e., /PoweredPNR_PNRReply/originDestinationDetails/
itineraryInfo
|
Business Function Type |
Description |
|
1 |
Air provider |
|
2 |
Car provider |
|
3 |
Hotel provider |
|
5 |
Cruise |
|
6 |
Rail |
|
7 |
Tour |
|
8 |
Hotel, requested through airline |
|
9 |
Car, requested through airline |
|
10 |
Air taxi |
|
11 |
Tour, requested through airline |
|
12 |
Surface |
|
13 |
Tour, requested through tour operator |
|
29 |
Insurance |
|
32 |
Miscellaneous |
2.7.2. Automated Car Auxiliary Elements
An automated car auxiliary element pertains to any car auxiliary segment reserved via the Amadeus car availability system. This includes any cars that were sold from an availability display or via a direct entry to the car company system bypassing the availability retrieval.
2.7.2.1.1. Standard Mandatory Car Element Parameters
|
Parameter |
Description |
|
Automated Car Identifier |
CCR |
|
Business function type |
2 for Car provider |
|
Car company code |
Company Identification |
|
Status |
Status of car reservation (I.e., HK, UC) |
|
Number of cars |
QUANTITY |
|
City code |
City of car rental location |
|
Pick-Up date |
Date of car reservation to begin |
|
Return date |
Date of car reservation to end |
|
Car type |
Car vendor identification code for the car type reserved |
|
Past indicator (PAST) |
Indicating that the reservation pick up date is previous to the current date · B for flown/used |
|
Type of sell access made to reserve the car |
· P10 for basic booking(Used for CCR segment Standard Access) ·
P4 for Last seat availability etc. ·
P2 for Seamless sell |
2.7.2.1.2. Optional Car Element Parameters
Numerous options may exist for the car element. Each element is identified with the option code followed by free flow text;
|
Parameter |
Description |
|
Option code |
Type of optional information |
|
Option value |
Free flow or formatted text for the option |
|
Passenger association |
· PT |
|
Associated Passenger Reference number |
|
Code Identifier |
Description |
|
ARR |
Arrival time when picking up car |
|
BA |
Booking agent |
|
BN |
Billing number |
|
BR |
Billing reference |
|
BS |
Booking source |
|
CA |
Complete Access Plus |
|
CD |
Corporate ID |
|
CF |
Confirmation number |
|
CK |
Car Voucher Print acknowledement |
|
CO |
Car company code |
|
COL |
Collection information |
|
DC |
Drop off charge |
|
DD |
Drop off date |
|
DEL |
Delivery information |
|
DI |
Distance information |
|
DO |
Drop off vendor location code |
|
DT |
Pick up and drop off date |
|
EST |
Estimated total rate |
|
FC |
Foreign currency code |
|
FP |
Form of payment |
|
FT |
Frequent traveler number |
|
G |
Guarantee information |
|
ID |
Customer ID |
|
IT |
Inclusive tour number |
|
LC |
Location address |
|
LO |
Location address |
|
MI |
Mileage option information |
|
MK |
Inter city distance |
|
NM |
Name |
|
PUP |
Pick up location |
|
RB |
Base rate |
|
RC |
Rate code category |
|
RI |
Rate Identifier |
|
RO |
Rate override |
|
RQ |
Rate Quoted |
|
RT |
Return time when dropping off car |
|
SI |
Supplementary information |
|
SQ |
Special equipment requested |
|
TK |
Tracking information |
|
VT |
Vehicle type code |
|
VV |
Voucher value |
|
** |
Agency Accounting information |
2.7.2.1.3. Optional parameters returned by Car Providers:
The following optional parameters will are available when the reply structure is returned for a new car segment (i.e., during the intiial car segment creation) or for an existing car segment (during a modification) that have been returned via Complete Access or Complete Access Plus:
|
Parameter |
Description |
|
Marketing message text from Provider |
3 for literal text |
|
Free flow marketing message, maximum of 384 characters |
|
|
Other services message from the Provider |
3 for literal text |
|
Free flow other service message of 192 characters |
2.7.2.1.4. Information returned by the Amadeus Car System
The following optional parameters are available when the reply structure is returned for a new Car segment (I.e., during the initial car segment creation) or for an existing car segment (during a modification) that have been returned via standard access or complete access from the Amadeus car database:
|
Parameter |
Description |
|
Car terms from the Amadeus Car database |
3 for literal text |
|
Free flow text for car rules and car policies within the Amadeus database. |
2.7.2.2. Standard Reply Structure
The following is an extract of the POWERED PNR Reply structure to illustrate an automated car auxiliary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
14 |
|
3 |
Line Number |
17 |
|
2 |
Segment Name ID |
CCR |
|
4 |
Car Pick Date |
100202 |
|
5 |
Car Drop Off Date |
110202 |
|
6 |
Car Rental Location |
RUN |
|
7 |
Car Rental Company |
SX |
|
8 |
Car Rental Type |
ECMN |
|
9 |
Business Function |
2 - Car Provider |
|
10 |
Number of Cars |
1 |
|
11 |
Segment status |
HK |
|
12 |
Type of Sell made to reserve the car |
P10 - basic booking |
|
13-14 |
Booking Source |
12345675 |
|
15-16 |
Arrival time |
1145 |
|
17-18 |
Return time |
1145 |
|
19-20 |
Rate category/rate plan - rate code |
SE-WET |
|
21-22 |
Rate quote from car company |
FRF890.32-.99 UNL WE 296.77 UNL XD |
|
23-24 |
Passenger Association |
Passenger reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
14 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
CCR |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
17 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
100202 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
110202 |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
RUN |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SX |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ECMN |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
2 |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
01 |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
P10 |
|
13 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
BS |
|
14 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
12345675 |
|
15 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ARR |
|
16 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1145 |
|
17 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
RC |
|
18 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SE-WET |
|
19 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
RQ |
|
20 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
FRF 890.32- .00 UNL WE 296.77- UNL XD |
|
21 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
RT |
|
22 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1145 |
|
23 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
PT |
|
24 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1 |
2.7.3. Automated Hotel Auxiliary Elements
An automated hotel auxiliary element pertains to any hotel auxiliary segment reserved via the Amadeus hotel availability system. This includes any hotels that were sold from an availability display or via a direct entry to the hotel chain system bypassing the availability retrieval.
2.7.3.1.1. Standard Hotel Element Parameters
|
Parameter |
Description |
|
Automated Hotel Identifier |
HHL |
|
Business Function Type |
3 for Hotel provider (HHL) |
|
Chain code |
Hotel Company Identification |
|
Provider name |
Hotel Company name |
|
Status code |
Status of reservation (I.e., HK, UC,etc) |
|
Number of rooms |
Number of rooms reserved |
|
City code |
3Character city code of hotel location |
|
Check-In date |
Date reservation begins |
|
Check-out date |
Date reservation ends |
|
Occupancy |
Number of people |
|
Room type |
Hotel vendor room type codes |
|
Rate Code |
Special rate information |
|
Past indicator (PAST) |
Indicating that the check-out date is previous to the current date · B for flown/used |
|
Currency |
Currency code |
|
Rate value |
Monetary amount |
|
Total or Daily indicator |
Rate plan used |
|
Property ID |
Hotel vendor system identification code |
|
Property name |
Hotel property name |
|
Type of sell access made displayed in G option. |
Option ·
P10 for basic booking ·
P4 for Last seat availability etc. ·
P2 for Seamless sell |
2.7.3.1.2. Optional Hotel Element Parameters
Numerous options may exist for the hotel element. Each element is identified with the option code followed by free flow text;
|
Parameter |
Description |
|
Option code |
Option identifier |
|
Option update indicator |
Confirmation indicator |
|
Option value |
Long free text |
|
Passenger association |
· PT |
|
Associated Passenger Reference number |
2.7.3.1.2.1. Option Codes by the user
The following option codes may be stored in the hotel element, by the user, at the time the reservation is requested;
|
Code Identifier |
Description |
|
AO |
Amount Override |
|
AP |
Meal Plan - American plan |
|
BC |
Booking code |
|
BS |
Booking source |
|
CD |
Corporate discount number |
|
CK |
Voucher number |
|
CR |
Crib request |
|
DD |
Change check out date |
|
DP |
Deposit advice to the hotel |
|
DT |
Change check-in date or both check-in and check-out dates |
|
FA |
Family American Plan - 3 meals per day per family |
|
FM |
Modified Family American Plan - 2 meals instead of 3 |
|
FT |
Frequent Traveller information |
|
G |
Guarantee of payment information |
|
ID |
Customer ID |
|
MA |
Modified American Plan - 2 meals a day per person |
|
NM |
Name of reservation |
|
NR |
Number of rooms |
|
RA |
Roll away bed for adult |
|
RC |
Roll away bed for a child |
|
RG |
Rate Guarantee |
|
RO |
Room override to sell a room not in availability |
|
RQ |
Rate Quotes |
|
RT |
Room types |
|
SF |
Safety information |
|
SI |
Supplementary information |
|
SR |
Special rate information |
|
W |
Written confirmation |
2.7.3.1.2.2. Option Codes by the hotel vendor
In addition to the optional codes that can be specified by the user when making a hotel reservation, the following optional codes may be placed in the hotel element by the hotel vendor at the time the hotel reservation is made;
|
Code Identifier |
Description |
|
ADV |
Advance booking requirements |
|
BGV |
Booking via information |
|
CAT |
Hotel Category |
|
CF |
Confirmation number |
|
CHK |
Check out date restrictions |
|
CNM |
Company Name |
|
COM |
Commission information |
|
CX |
Cancellation number |
|
CXL |
Cancellation policy |
|
DEP |
Deposit rules |
|
DES |
Description of rate |
|
DIN |
Dining information |
|
EX |
Charge for extra persons |
|
EXT |
Extra charges |
|
FAC |
Facilities |
|
FRQ |
Frequent stay information |
|
GNT |
Guarantee Information |
|
HLD |
Holding information for the reservation |
|
LOC |
Location information |
|
MEA |
Meal information |
|
MEE |
Meeting facilities |
|
NAM |
Hotel name |
|
NGT |
Number of nights the room is reserved |
|
OTH |
Other miscellaneous information |
|
POL |
Policy Information |
|
PRI |
Price information |
|
ROO |
Room information |
|
RTT |
Rate type |
|
SAV |
Saving amount between sold rate and normal public rate |
|
SFY |
Safety information |
|
STA |
Minimum/maximum stay rules |
|
SVC |
Service charge information |
|
TAX |
Tax information |
|
TRA |
Transportation |
|
TTL |
Total reservation amount |
2.7.3.1.3. Optional parameters returned prior to PNR storage:
The following optional parameters will only be available if the reply structure is returned for a PNR that has not yet been stored in the Amadeus system. (I.e., during the initial PNR creation):
|
Parameter |
Description |
|
Marketing message text from Provider |
3 for literal text |
|
Free flow text up to 512 characters |
2.7.3.2. Standard Reply Structure
The following is an extract of the POWERED PNR Reply structure to illustrate an automated hotel auxiliary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
2 |
|
3 |
Line Number |
4 |
|
2 |
Segment Name ID |
HHL |
|
4 |
Check in date |
080701 |
|
5 |
Check out date |
100701 |
|
6 |
City Location |
NCE |
|
7 |
Hotel chain code |
HI |
|
8 |
Business function |
3 - hotel provider |
|
9 |
Quantity reserved |
1 |
|
10 |
Status of reservation |
HK |
|
11 |
Type of sell made for reservation |
P4 - last seat availability |
|
12 |
Hotel provider name |
HOLIDAY INN |
|
13 |
Hotel vendor property code |
397 |
|
14 |
Hotel property name |
HI RESORT NICE-PORT ST. LAURENT |
|
15 |
Occupancy |
2 persons |
|
16 |
Room type code |
A2T |
|
17 |
Rate code |
RAC |
|
18 |
Currency code |
EUR |
|
19 |
Rate amount |
211.90 |
|
20 |
Rate Plan |
DY - Daily |
|
21-22 |
Credit card guarantee |
CCAX888888190311007EXP1200 |
|
23-24 |
Stay restrictions |
1 DAY MINIMUM 99 DAY MAXIMUM |
|
25-26 |
Total rate |
EUR423.80 |
|
27-28 |
Number of nights reserved |
2 |
|
29-30 |
Name of hotel property |
HI RESORT NICE-PORT ST. LAURENT |
|
31-32 |
Booking source |
12345675 |
|
33-34 |
Confirmation number |
61611431 |
|
35-36 |
Company name |
HOLIDAY INN |
|
37-38 |
Price information |
08JUL 211.9002 |
|
39-40 |
Description of rate |
REGULAR RACK RATE |
|
41-42 |
Cancellation policy |
MUST CANCEL RESERVATIONS BY 1800 HOST HOTEL TIME UP TO 30 DAYS IN ADVANCE TO AVOID BILLING SEE HP RULES FOR EXACT CANCEL POLICY |
|
43-44 |
Passenger association |
Associated to passenger reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/qualifier |
ST |
|
1 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/number |
2 |
|
2 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/segmentName |
HHL |
|
3 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/lineNumber |
4 |
|
4 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/depDate |
080701 |
|
5 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/arrDate |
100701 |
|
6 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/boardpointDetail/cityCode |
NCE |
|
7 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/companyDetail/identification |
HI |
|
8 |
/originDestinationDetails/itineraryInfo [2]/itineraryMessageAction/business/function |
3 |
|
9 |
/originDestinationDetails/itineraryInfo [2]/relatedProduct/quantity |
01 |
|
10 |
/originDestinationDetails/itineraryInfo [2]/relatedProduct/status |
HK |
|
11 |
/originDestinationDetails/itineraryInfo [2]/selectionDetails/selection/option |
P4 |
|
12 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/providerName |
HOLIDAY INN |
|
13 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/code |
397 |
|
14 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/name |
HI RESORT NICE-PORT ST. LAURENT |
|
15 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/occupancy |
2 |
|
16 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/typeCode |
A2T |
|
17 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/negotiated/rateCode |
RAC |
|
18 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/otherHotelInfo/currencyCode |
EUR |
|
19 |
/originDestinationDetails/itineraryInfo [2]/rateInformations/ratePrice/rateAmount |
211.90 |
|
20 |
/originDestinationDetails/itineraryInfo [2]/rateInformations/rateInfo/ratePlan |
DY |
|
21 |
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/type |
G |
|
22 |
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/freetext |
CCAX888888190311007EXP1200 |
|
23 |
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/type |
STA |
|
24 |
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/freetext |
1 DAY MINIMUM 99 DAY MAXIMUM |
|
25 |
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/type |
TTL |
|
26 |
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/freetext |
EUR423.80 |
|
27 |
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/type |
NGT |
|
28 |
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/freetext |
02 |
|
29 |
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/type |
NAM |
|
30 |
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/freetext |
HI RESORT NICE-PORT ST. LAURENT |
|
31 |
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/type |
BS |
|
32 |
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/freetext |
12345675 |
|
33 |
/originDestinationDetails/itineraryInfo [2]/generalOption[7]/optionDetail/type |
CF |
|
34 |
/originDestinationDetails/itineraryInfo [2]/generalOption[7]/optionDetail/freetext |
61611431 |
|
35 |
/originDestinationDetails/itineraryInfo [2]/generalOption[8]/optionDetail/type |
CNM |
|
36 |
/originDestinationDetails/itineraryInfo [2]/generalOption[8]/optionDetail/freetext |
HOLIDAY INN |
|
37 |
/originDestinationDetails/itineraryInfo [2]/generalOption[9]/optionDetail/type |
PRI |
|
38 |
/originDestinationDetails/itineraryInfo [2]/generalOption[9]/optionDetail/freetext |
08JUL 211.9002 |
|
39 |
/originDestinationDetails/itineraryInfo [2]/generalOption[10]/optionDetail/type |
DES |
|
40 |
/originDestinationDetails/itineraryInfo [2]/generalOption[10]/optionDetail/freetext |
REGULAR RACK RATE |
|
41 |
/originDestinationDetails/itineraryInfo [2]/generalOption[11]/optionDetail/type |
CXL |
|
42 |
/originDestinationDetails/itineraryInfo [2]/generalOption[11]/optionDetail/freetext |
MUST CANCEL RESERVATIONS BY 1800 HOST HOTEL TIME UP TO 30 DAYS IN ADVANCE TO AVOID BILLING SEE HP RULES FOR EXACT CANCEL POLICY. |
|
43 |
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/qualifier |
PT |
|
44 |
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/number |
1 |
A Flight element pertains to any airline segments reserved via the Amadeus airline reservation system. This includes any segments that were sold via availability or via a direct entry to the Airline reservation system bypassing the availability retrieval. Coinciding with the flight element limitations, a maximum of 99 flight elements may be returned.
2.7.4.1. Connecting and Married Flight Elements
All flight element parameters are identified in the same manner for non-connecting, connecting, and married flight elements. Connecting and married flight elements are further defined in a grouping category after all flight element information in the returned information structure. A grouping code is used to specify a connection or a married situation, after which the reference numbers of the associated connecting or married flight elements are listed.
The grouping of the itinerary elements does not follow the standard use of element qualifiers (ST,OT,PT), as it is not considered as a true element within the PNR.
2.7.4.2.1. Standard Parameters
|
Parameter |
Description |
|
Automated flight identifier |
AIR |
|
Airline code |
2 character company Identification |
|
Flight number |
Flight number reserved |
|
Class of service |
Class of service reserved |
|
Departure date |
Flight departure date |
|
Day of the week |
Days of operation(1 = Monday to 7) |
|
Boarding point |
Originating city code for the flight |
|
Off point |
Destination city code for the flight |
|
Status code |
Status of the air segment reserved (i.e., HK, HL, UC) |
|
Number in party |
Number of seats reserved |
|
Check in time |
Check-in details (hhmm) |
|
Terminal of departure information |
Related place/location one identification |
|
Departure time |
Flight departure time |
|
Arrival time |
Flight arrival time |
|
Level of access used for selling the flight |
· P10 for basic booking(Used for Air segment sell on Amadeus Inventory) ·
P2 for Seamless sell ·
P4 for Last seat availability etc. ·
P3 for Last seat availability etc. |
|
Passive segment airline reference |
Airline Company code in which a passive segment is held for the space reserved via the amadeus system. |
|
Airline Record locator |
Reservation control number in the airline company system. |
2.7.4.2.2. Optional Parameters
Optional parameters that may be included in the flight element:
|
Parameter |
Description |
|
Second airline code for joint flight number |
2 character company Identification |
|
Flight number alpha suffix |
(A-E) |
|
Night (N) indicator |
Identifying that the flight is classified as a night flight · N for Night class |
|
Flown indicator (FLWN) |
Indicates if the flight departure date is greater than the current date. · B for flown/used |
|
Day change indicator |
Indication of the number days + or - or any arrival date variations. |
|
Connection information (not in the display) |
· CNX for Connection |
|
Connection reference |
Reference number of the connecting segment |
|
Married segment Id |
· Mxx for Marriage |
|
Married segment qualifier |
· D for Dominant segment in a marriage· N for Non dominant segment in a marriage |
|
Married segment reference |
Reference number of the segment |
|
Electronic ticketing indicator (ET*) (after EOT only) |
Indicates if flight is available for electronic ticketing. · ET for Electronic ticket candidate |
|
Passenger association |
· PT for passenger reference number |
|
Reference number of the passenger associated |
2.7.4.2.3. Optional Parameters Prior to PNR Storage
The following optional parameters will only be available if the reply structure is returned for a PNR that has not yet been stored in the Amadeus system. (I.e., during the initial PNR creation):
|
Parameter |
Description |
|
Equipment code |
Equipment code description of the aircraft for the flight |
|
Entertainment code (E) |
Indication of entertainment services · E for entertainment |
|
Number of stops |
Number of stops for the flight |
|
Meal Service Identifier |
· M for meal service |
|
Meal code |
Indication of what type of meals provided (I.e., S - snack, D - dinner) |
|
Airline comment line |
|
|
Airline comment identifier |
3 for literal text |
|
Comment text |
FREE TEXT maximum of 60 characters |
|
Amadeus comment line |
|
|
Amadeus Comment identifier |
3 for literal text |
|
Comment text |
FREE TEXT maximum of 60 characters |
|
Warning line |
· ZZZ for no number provided |
|
Code list qualifier |
· WEC for Warning code |
|
Code list responsible agency |
· 1A for Amadeus |
|
Warning identifier |
· 3 for literal text |
|
Warning text |
FREE TEXT maximum of 60 characters |
2.7.4.3. Reply Structure After PNR Storage
2.7.4.3.1. Standard flight element
The following is an extract of the POWERED PNR Reply structure to illustrate an automated flight element, after the PNR has been stored, containing the parameters outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
1 |
|
2 |
Automated flight identifier |
AIR |
|
3 |
Line Number |
7 |
|
4 |
Flight departure date |
121001 |
|
5 |
Flight departure time |
1305 |
|
6 |
Flight arrival date |
121001 |
|
7 |
Flight arrival time |
1545 |
|
8 |
Flight originating city |
ARN |
|
9 |
Flight destination city |
CDG |
|
10 |
Airline code |
SK |
|
11 |
Flight number |
575 |
|
12 |
Class of service booked |
C |
|
13 |
Electronic ticket indicator |
ET |
|
14 |
Business function type |
1 - Air provider |
|
15 |
Business company ID |
SK |
|
16 |
Airline Record Locator |
AP427 |
|
17 |
Number of seats reserved |
4 |
|
18 |
Segment status |
HK |
|
19 |
Weekday of flight operation |
5 |
|
20 |
Departure Terminal Number |
5 |
|
21 |
Type of sell made to reserve the air segment |
P2 - seamless sell(Amadeus access) |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
AIR |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
7 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
121001 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1305 |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
121001 |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1545 |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ARN |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
CDG |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SK |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
575 |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
C |
|
13 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ET |
|
14 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1 |
|
15 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SK |
|
16 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
AP427 |
|
17 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
4 |
|
18 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
19 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
5 |
|
20 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
5 |
|
21 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
P2 |
2.7.4.3.2. Connecting Flight Element
The following is an extract of the POWERED PNR Reply structure to illustrate two groups of connecting flight elements defined in the returned structure as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Grouping code identifying the first group of connecting flight elements |
CNX - Connecting segments |
|
2 |
Flight element reference number of the first connecting flight previously defined in the returned structure |
6 |
|
3 |
Flight element reference number of the second connecting flight previously defined in the returned structure |
7 |
|
4 |
Grouping code identifying the second group of connecting flight elements |
CNX - Connecting segments |
|
5 |
Flight element reference number of the first connecting flight previously defined in the returned structure |
10 |
|
6 |
Flight element reference number of the second connecting flight previously defined in the returned structure |
11 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
1 |
/segmentGroupingInfo [1]/groupingCode |
CNX |
|
2 |
/segmentGroupingInfo [1]/marriageDetail[1]/tatooNum |
6 |
|
3 |
/segmentGroupingInfo [1]/marriageDetail[2]/tatooNum |
7 |
|
4 |
/segmentGroupingInfo [2]/groupingCode |
CNX |
|
5 |
/segmentGroupingInfo [2]/marriageDetail[1]/tatooNum |
10 |
|
6 |
/segmentGroupingInfo [2]/marriageDetail[2]/tatooNum |
11 |
Note that the connecting relation identification is not included in the itinerary element structure, but instead is broken out as indexed segment grouping information [segmentGroupingInfo
[1]/groupingCode] after the itinerary element information returned in the structure. These are not considered as true elements of the PNR, but rather only as informational data for associated itinerary elements. Therefore, they are not identified with an element qualifier, such as ST used for the itinerary elements.
2.7.4.3.3. Married Flight Element
The following is an extract of the POWERED PNR Reply structure to illustrate grouping of married flight elements defined in the returned structure as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Grouping code |
MTR - married segments |
|
2 |
Marriage qualifier |
N - non dominant element |
|
3 |
Flight element reference number of non dominant flight previously defined in the returned structure |
6 |
|
4 |
Marriage qualifier |
D - dominant element |
|
5 |
Flight element reference number of dominant flight previously defined in the returned structure |
7 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
1 |
/segmentGroupingInfo [3]/groupingCode |
MTR |
|
2 |
/segmentGroupingInfo [3]/marriageDetail[1]/marriageQualifier |
N |
|
3 |
/segmentGroupingInfo [3]/marriageDetail[1]/tatooNum |
6 |
|
4 |
/segmentGroupingInfo [3]/marriageDetail[2]/marriageQualifier |
D |
|
5 |
/segmentGroupingInfo [3]/marriageDetail[2]/tatooNum |
7 |
Note that the married relation identification is not included in the itinerary element structure, but instead is broken out as indexed segment grouping information [segmentGroupingInfo
[3]/groupingCode] after the itinerary element information returned in the structure. This is not considered as a true element of the PNR, but rather only as informational data for associated itinerary elements. Therefore, it is not identified with an element qualifier, such as ST used for the itinerary elements.
2.7.5. Ground Transportation Elements
A PNR may contain a ground transportation element to identify a specific non-air service.
The following parameters may be returned for a ground transportation element;
|
Ground transportation identifier |
SUR |
|
Business function code |
12 for Surface |
|
Pseudo-airline code |
2 character Company Identification |
|
Status code |
Status of surface element |
|
Number of passengers |
QUANTITY |
|
City / Airport code |
Place/Location Identification |
|
Date |
Date for surface service |
|
Transportation type |
Product identification for transportation |
|
Pick-up time |
Time of service |
|
Departure code ‘A’ or ‘D’ |
Product Identification Characteristic A = arrival D = departure |
|
Segment number along with ‘A’ or ‘D’ works like segment association |
ST for Segment reference number |
|
Reference number |
|
|
Transportation zone number |
Sequence number |
|
Past indicator (PAST) |
Indicating if date of service is previous to the current date B for flown/used |
|
Passenger address |
3 for literal text |
|
Information type |
2 for Address (home or hotel) |
|
Free form text maximum of 60 characters |
|
|
Passenger phone contact |
3 for literal text |
|
Information type |
5 for Telephone nature not known |
|
Free form text maximum of 40 characters |
|
|
Free flow text |
3 for literal text |
|
Free form text maximum of 40 characters |
|
|
Passenger association |
PT for Passenger reference number |
|
Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a ground transportation element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
2 |
|
2 |
Segment name Id |
SUR |
|
3 |
Line Number |
6 |
|
4 |
Surface departure date |
121001 |
|
5 |
Surface departure time |
1200 |
|
6 |
Departure City Code |
ARN |
|
7 |
Associated airline to the Surface |
SK |
|
8 |
Type of surface service |
TAXI |
|
9 |
Subtype of service |
D - departure |
|
10 |
Business function type |
12 - surface |
|
11 |
Number of passengers for the service |
4 |
|
12 |
Status of the surface element |
HK |
|
14 |
Additional information |
STOBY,GATUADRESS/0000-0000000/INFO |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
2 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SUR |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
6 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
121001 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1200 |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ARN |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
SK |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
TAXI |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
D |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
01 |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
12 |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
4 |
|
13 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
14 |
/PoweredPNR_PNRReply/originDestinationDetails/ subjectQualifier |
3 |
|
15 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
STOBY,GATUADRESS/0000-0000000/INFO |
2.7.6. Non-Automated Car Auxiliary Elements
A non-automated car auxiliary element pertains to any segment associated to an airline to request car rental services or to a passive car segment reflecting a car booked outside the Amadeus system. These segments are not reserved via the Amadeus Car availability system. If an associated airline exists in the element, it is responsible for making the reservation request.
The following parameters are returned for a non-automated car auxiliary element:
|
Parameter |
Description |
|
Non automated Car Auxiliary Identifier |
CU |
|
Business Function Type |
9 for Car requested through airline rather than car operator (CAR) |
|
The airline to take action |
2-character airline code or the amadeus system code (1A) in the case of a passive car element. |
|
Element status |
Status of the car element (i.e., HK, HL, UC) |
|
Number of cars |
QUANTITY |
|
Pick-up point city |
3 character city code |
|
Pick-up date |
Date the car will be picked up |
|
Drop-off date |
Date the car will be returned |
|
Car type |
Car vendor identification code for the type of car reserved (I.e., ECAR, ECMN) |
|
Past indicator |
Identifies if the pick up date for the car is previous to the current date. B for flown/used |
|
Free flow text identifier |
3 for literal text |
|
Free flow text |
Free flow text maximum of 199 characters |
|
Passenger association |
PT |
|
Associated Passenger Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a non-automated Car Auxiliary element for a car reserved outside the Amadeus system as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
12 |
|
2 |
Segment name Id |
CU |
|
3 |
Line Number |
16 |
|
4 |
Pick-Up date |
030202 |
|
5 |
Drop-Off date |
130202 |
|
6 |
Pick-Up point city |
CLD |
|
7 |
Associated airline to the Surface |
1A |
|
8 |
Type of car reserved |
CCAR |
|
9 |
Business function type |
9 - Car requested through airline |
|
10 |
Number of passengers for the service |
1 |
|
11 |
Status of the element |
HK |
|
12 |
Information identifier |
3 - literal text |
|
13 |
Additional information |
BS-80202522/BS-49677725/CCZI |
|
14-15 |
Passenger Association |
Passenger reference number 5 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
12 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
CU |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
16 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
030202 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
130202 |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
CLD |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1A |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
CCAR |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
9 |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1 |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
3 |
|
13 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
BS-80202522/BS-49677725/CCZI |
|
14 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
PT |
|
15 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
5 |
Note that the reply structure is the same for a non-automated car auxiliary element associated to an airline, in which instance the 2 character airline code will replace the 1A amadeus system code in item number 7 above.
2.7.7. Non-Automated Hotel Auxiliary Elements
A non-automated hotel auxiliary element pertains to any segment associated to an airline to request hotel reservation services or to a passive hotel segment reflecting a hotel reservation booked outside the Amadeus system. These segments are not reserved via the Amadeus hotel availability system. If an associated airline exists in the element, it is responsible for making the reservation request.
The following parameters may be returned for a non-automated hotel auxiliary element:
|
Parameter |
Description |
|
Non-automated hotel auxiliary identifier |
HU |
|
Business function type |
8 for Hotel requested through airline rather than hotel/motel |
|
The airline to take action |
2 character airline code, or the amadeus system code (1A) in the case of a passive car element |
|
Element status |
Status of the hotel element (i.e., HK, HL, UC) |
|
Number of rooms |
QUANTITY |
|
Check-in city |
3 character city code of hotel location |
|
Check-in date |
Date the reservation begins |
|
Check-out date |
Last date of the reservation |
|
Past indicator |
Indicating that the check-in date is previous to the current date. B for flown/used |
|
Optional text identifier |
3 for literal text |
|
Free flow text information |
Maximum of 199 characters |
|
Passenger association qualifier |
PT |
|
Associated Passenger Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a non-automated Hotel Auxiliary element for a hotel reserved with American Airlines (AA) as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
11 |
|
2 |
Segment name Id |
HU |
|
3 |
Line Number |
15 |
|
4 |
Check-In date |
200102 |
|
5 |
Check-Out date |
240102 |
|
6 |
Check-In city |
LAS |
|
7 |
Associated airline to the hotel |
AA |
|
9 |
Business function type |
8 - Hotel requested through airline |
|
10 |
Number of passengers for the service |
4 |
|
11 |
Status of the element |
HK |
|
12-13 |
Additional information |
EXCALIBUR |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
11 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HU |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
15 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
200102 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
240102 |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
LAS |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
AA |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
8 |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
4 |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
3 |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
EXCALIBUR |
Note that the reply structure is the same for a non-automated hotel auxiliary element for a reservation made outside the amadeus system, in which instance the 2 character airline code will be replaced with the 1A amadeus system code in item number 7 above.
2.7.8. Non-Automated Miscellaneous Auxiliary Elements
A non-automated miscellaneous auxiliary element pertains to any segment detailing miscellaneous services reserved outside the Amadeus system. (I.e., theatre tickets, etc) These segments are not reserved via the Amadeus system, but can be included in the reservation for informational purposes.
The following parameters may be returned for a non-automated miscellaneous auxiliary element:
|
Parameter |
Description |
|
Non-automated miscellaneous auxiliary identifier |
RU |
|
Business function type |
32 for Miscellaneous |
|
Amadeus System Code |
1A |
|
Status of the element |
HK |
|
Number of services required |
QUANTITY |
|
City of Service |
City code for service location |
|
Date for service required |
Date of request |
|
Past indicator |
Indicating that the service date is previous to the current date B for flown/used |
|
Free flow text identifier |
3 for literal text |
|
Free flow text information |
Maximum of 199 characters |
|
Passenger association |
PT |
|
Associated Passenger Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a non-automated Miscellaneous Auxiliary element for a miscellaneous service reserved outside the Amadeus system as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
15 |
|
2 |
Segment name Id |
RU |
|
3 |
Line Number |
19 |
|
4 |
Date of Service |
260402 |
|
5 |
City of Service |
TPA |
|
6 |
Amadeus system code |
1A |
|
7 |
Business function type |
32 - Miscellaneous service requested outside Amadeus |
|
8 |
Number of passengers for the service |
1 |
|
9 |
Status of the element |
HK |
|
10-11 |
Additional information |
30APR/FUNJET |
|
12-13 |
Passenger association |
Passenger reference number 3 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
ST |
|
1 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
15 |
|
2 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
RU |
|
3 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
19 |
|
4 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
260402 |
|
5 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
TPA |
|
6 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1A |
|
7 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
32 |
|
8 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
1 |
|
9 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
HK |
|
10 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
3 |
|
11 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
30APR/FUNJET |
|
12 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
PT |
|
13 |
/PoweredPNR_PNRReply/originDestinationDetails/ |
3 |
A Cruise element pertains to any cruise line segment reserved via a cruise line reservation system.
Cruise elements present in this message provide information about cruise booking done in a cruise line reservation system.
The following is an extract of a POWERED PNR Reply structure to illustrate the Cruise element in the Amadeus system.
Please note that the items shown below in grey will not be used by Cruise in the near future.
|
Item # |
Parameter |
Information |
|
0 |
Qualifier for Segment Tattoo |
ST |
|
1 |
Reference Number |
3 |
|
2 |
Segment Name ID |
CRU |
|
3 |
Line Number |
3 |
|
4 |
Departure Date |
110404 |
|
5 |
Boarding Point |
SJU |
|
6 |
Off Point |
SJU |
|
7 |
Cruise Code |
RCC |
|
8 |
Business function type |
5 |
|
9 |
Number of service |
1 |
|
10 |
Segment status |
HO |
|
11 |
Qualifier for Number of days |
700 |
|
12 |
Sailing duration (expressed in days) |
7 |
|
13 |
Qualifier for literal text |
3 |
|
14 |
Qualifier for Ship Name |
P30 |
|
15 |
Text |
Adventure of the sea |
|
16 |
Qualifier for Booking Number |
CF |
|
17 |
Text |
2410 |
|
18 |
Qualifier for Cruise Passenger |
NM |
|
19-20 |
Passenger information |
Mr. & Mrs. Durana |
|
21 |
Ship code as in the Cruise specific database ship's table |
AD |
|
22 |
Ship name |
Adventure of the Seas |
|
23 |
Cruise line provider code |
RCC |
|
24 |
Cruise industry business code |
CRU |
|
25 |
Context in which the code applies (not used) |
ZZ |
|
26 |
Cruise line code |
RCC |
|
27 |
Cruise line name |
Royal Caribbean International |
|
28-29 |
Embarkation and disembarkation port codes |
SJU-SJU |
|
30-32 |
Sailing departure date |
11Apr2004 |
|
33-35 |
Sailing end date |
18Apr2004 |
|
36-41 |
Cruise Passenger details |
Mr. & Mrs. Durana |
|
42 |
Cruise line Booking number |
2410 |
|
43 |
Cruise booking reference |
2 : Booking number X : Cancellation number |
|
44 |
Qualifier for Group code |
GPN |
|
45 |
Group code number |
0783538 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/originDestinationDetails/itineraryInfo/ |
ST |
|
1 |
/originDestinationDetails/itineraryInfo/ |
3 |
|
2 |
/originDestinationDetails/itineraryInfo/ |
CRU |
|
3 |
/originDestinationDetails/itineraryInfo/ |
3 |
|
4 |
/originDestinationDetails/itineraryInfo/travelProduct/ |
110404 |
|
5 |
/originDestinationDetails/itineraryInfo/travelProduct/ |
SJU |
|
6 |
/originDestinationDetails/itineraryInfo/travelProduct/ |
SJU |
|
7 |
/originDestinationDetails/itineraryInfo/travelProduct/ |
RCC |
|
8 |
/originDestinationDetails/itineraryInfo/ |
5 |
|
9 |
/originDestinationDetails/itineraryInfo/relatedProduct/ |
1 |
|
10 |
/originDestinationDetails/itineraryInfo/relatedProduct/ |
HO |
|
11 |
/originDestinationDetails/itineraryInfo/selectionDetails/ |
700 |
|
12 |
/originDestinationDetails/itineraryInfo/selectionDetails/ |
7 |
|
13 |
/originDestinationDetails/itineraryInfo/ |
3 |
|
14 |
/originDestinationDetails/itineraryInfo/ |
P30 |
|
15 |
/originDestinationDetails/itineraryInfo/ |
ADVENTURE OF THE SEAS |
|
16 |
/originDestinationDetails/itineraryInfo/generalOption[1]/ |
CF |
|
17 |
/originDestinationDetails/itineraryInfo/generalOption[1]/ |
2410 |
|
18 |
/originDestinationDetails/itineraryInfo/generalOption[2]/ |
NM |
|
19 |
/originDestinationDetails/itineraryInfo/generalOption[2]/ |
DURANA/EDMOND MR |
|
20 |
/originDestinationDetails/itineraryInfo/generalOption[2]/ |
DURANA/SOPHIE MRS |
|
21 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
AD |
|
22 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
ADVENTURE OF THE SEAS |
|
23 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
RCC |
|
24 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
CRU |
|
25 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
ZZ |
|
26 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
RCC |
|
27 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
ROYAL CARIBBEAN INTERNATIONAL |
|
28 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
SJU |
|
29 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
SJU |
|
30 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
2004 |
|
31 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
4 |
|
32 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
11 |
|
33 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
2004 |
|
34 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
4 |
|
35 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
18 |
|
36 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
DURANA |
|
37 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
EDMOND |
|
38 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
MR |
|
39 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
DURANA |
|
40 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
SOPHIA |
|
41 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
MRS |
|
42 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
2410 |
|
43 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ |
2 |
|
44 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ sailingGroupInformation/referenceType |
GPN |
|
45 |
/originDestinationDetails/itineraryInfo/typicalCruiseData/ sailingGroupInformation/uniqueReference |
0783538 |
2.8. ELEMENT: DOCUMENT ELEMENTS
Document elements pertain to any elements stored in the PNR, which are specific to a document produced for the PNR (I.e., Ticket, Invoice, etc).
The information returned in the Powered PNR Reply structure is dependent upon the type of document element.
2.8.1. Specific Structural Elements
The following structural elements are specific to the document elements when they are returned in the Powered PNR Reply Structure;
Each itinerary element is qualified [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/Each document element has a associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This line item number is an indication to the order in which the document elements are stored within the Amadeus PNR. It is used to identify the specific document element for any subsequent modifications or cancellations.Each document element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the elements were created within the Amadeus PNR.
2.8.2. Automated Invoice Number Elements
When an automated invoice is issued for the PNR, the invoice number given to the PNR is automatically stored in the PNR. The Automated invoice number element will return the invoice number from the PNR as a special type (P16) of free form text.
The following parameters are returned for an automated invoice number element:
|
Parameter |
Description |
|
Automated invoice number identifier |
FI |
|
Free form text identifier |
3 for literal text |
|
Type of free form text |
P16 for Automated Invoice Number |
|
Passenger type and invoice number |
Free form text |
|
Segment association |
Reference qualifier SR for Segment Client- request-message-defined reference number SS for Segment Tattoo+SubTattoo reference number ST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
Reference qualifier PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an automated Invoice Number Element associated to a specific passenger and specific itinerary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Reference Number |
8 |
|
2 |
Segment name Id |
FI |
|
3 |
Line Number |
5 |
|
4 |
Passenger type, AIR number and invoice number |
PAX 1500008646 INV 0000501153 |
|
5 |
Passenger association |
Passenger reference number 1 |
|
6 |
Segment association |
Itinerary element reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
8 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
FI |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
5 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/type |
P16 |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/longFreetext |
PAX 1500008646 INV 0000501153 |
|
7 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/number |
1 |
|
9 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/qualifier |
ST |
|
10 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/number |
1 |
Note that if the AIR number has not been stored in the PNR, only the Passenger type and Invoice number will be returned.
2.8.3. Invoice Remark Elements
Remarks may be stored in the PNR to customize the printouts of the invoice. Such remarks are returned as invoice remark elements.
Coinciding with the invoice remark element limitations, a maximum of 127 elements may be returned each containing a maximum of 64 characters.
The following parameters may be returned for an invoice remark element.
|
Parameter |
Description |
|
Invoice remark identifier |
RI |
|
Invoice remark type |
RI |
|
Invoice remark category |
F |
|
Free flow remark text |
Maximum of 64 characters. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
2.8.3.1. Reply Structure associated to all passengers and all segments
The following is an extract of the POWERED PNR Reply structure to illustrate an invoice remark element associated to all passengers and all segments as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
28 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Remark line number |
38 |
|
4 |
Invoice remark type |
RI |
|
5 |
Invoice and itinerary remark category |
F |
|
6 |
Free flow remark text |
THANK YOU FOR SELECTING TOUR-MANIA AGENTS |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/reference/number |
28 |
|
2 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/lineNumber |
38 |
|
4 |
/dataElementsMaster/dataElementsIndiv [20]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [20]/miscellaneousRemarks/remarks/category |
F |
|
6 |
/dataElementsMaster/dataElementsIndiv [20]/miscellaneousRemarks/remarks/freetext |
THANK YOU FOR SELECTING TOUR-MANIA AGENTS |
2.8.3.2. Reply Structure for associated to specific passengers
The following is an extract of the POWERED PNR Reply structure to illustrate an invoice remark element associated to only one passenger and all segments as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
28 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Remark line number |
38 |
|
4 |
Invoice remark type |
RI |
|
5 |
Invoice and itinerary remark category |
F |
|
6 |
Free flow remark text |
THANK YOU FOR SELECTING TOUR-MANIA AGENTS |
|
7-8 |
Passenger association |
Associated to passenger reference number 3 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/reference/number |
29 |
|
2 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/lineNumber |
39 |
|
4 |
/dataElementsMaster/dataElementsIndiv [21]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [21]/miscellaneousRemarks/remarks/category |
F |
|
6 |
/dataElementsMaster/dataElementsIndiv [21]/miscellaneousRemarks/remarks/freetext |
VIP ACCOUNT HAS REACHED AWARD STATUS |
|
7 |
/dataElementsMaster/dataElementsIndiv [21]/referenceForDataElement/reference/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [21]/referenceForDataElement/reference/number |
3 |
2.8.4. Invoice and Itinerary Remark Elements
Single Remarks may be stored in the PNR to customize the printouts of both the invoice and itinerary. Such remarks are returned as invoice and itinerary remark elements.
Coinciding with the invoice and itinerary remark element limitations, a maximum of 127 elements may be returned each containing a maximum of 64 characters.
The following parameters may be returned for an invoice remark element.
|
Parameter |
Description |
|
Invoice remark identifier |
RI |
|
Invoice and Itinerary remark type |
RI |
|
Invoice and itinerary remark category |
I |
|
Free flow remark text |
Maximum of 64 characters. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
2.8.4.1. Reply Structure associated to all passengers and all segments
The following is an extract of the POWERED PNR Reply structure to illustrate an invoice and itinerary remark element associated to all passengers and all segments as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
13 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Remark line number |
33 |
|
4 |
Invoice remark type |
RI |
|
5 |
Invoice and itinerary remark category |
I |
|
6 |
Free flow remark text |
YOUR VIP ACCOUNT |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
13 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RI |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
33 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RI |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
I |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
YOUR VIP ACCOUNT |
2.8.5. Invoice Service Fee Remark Elements
A remark may be stored in the PNR to print a service fee amount on invoice documents. Such remarks are returned as invoice service fee remark elements.
|
Parameter |
Description |
|
Invoice remark identifier |
RI |
|
Itinerary/invoice remark type |
RI |
|
Invoice and itinerary remark category |
S |
|
Free flow remark text |
Maximum of 64 characters, identifying · 3 character currency code, · Positive or negative currency amount · Free flow text explanation about the service fee. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
2.8.5.1. Reply Structure for associated to all passengers
The following is an extract of the POWERED PNR Reply structure to illustrate a service fee remark element associated to all passengers and all segments as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
26 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Remark line number |
34 |
|
4 |
Invoice remark type |
RI |
|
5 |
Invoice service remark category |
S |
|
6 |
Free flow remark text |
· Currency Code-USD · Negative Amount-<25.00> · Free text-REFUND ON TAXIS SERVICE |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/reference/number |
26 |
|
2 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/lineNumber |
34 |
|
4 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/category |
S |
|
6 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/freetext |
USD-25.00-REFUND ON TAXIS SERVICE |
2.8.6. Itinerary Remark Elements
A remark may be stored in the PNR to customize the printouts of itinerary documents. Such remarks are returned as Itinerary remark elements.
|
Parameter |
Description |
|
Itinerary remark identifier |
RI |
|
Itinerary/invoice remark type |
RI |
|
Itinerary remark category |
R |
|
Free flow remark text |
Maximum of 64 characters. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
2.8.6.1. Reply Structure for associated to specific passenger and segment
The following is an extract of the POWERED PNR Reply structure to illustrate an itinerary remark element associated to a specific passenger and a specific segment as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
30 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Remark line number |
37 |
|
4 |
Remark type |
RI |
|
5 |
Itinerary remark category |
R |
|
6 |
Free flow text |
ALLOW 2HOURS FOR CUSTOMS |
|
7-8 |
Passenger association |
Passenger reference number 1 |
|
9-10 |
Segment association |
Segment reference number 3 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/reference/number |
30 |
|
2 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/lineNumber |
37 |
|
4 |
/dataElementsMaster/dataElementsIndiv [19]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [19]/miscellaneousRemarks/remarks/category |
R |
|
6 |
/dataElementsMaster/dataElementsIndiv [19]/miscellaneousRemarks/remarks/freetext |
ALLOW 2HOURS FOR CUSTOMS |
|
7 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference[1]/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference[1]/number |
1 |
|
9 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference[2]/qualifier |
ST |
|
10 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference[2]/number |
3 |
2.8.7. Manual Documentation Registration Elements
If ticket numbers have been manually stored in a PNR because the tickets were not automatically generated or for some reason had to be re-entered in the PNR, they are returned in the manual documentation registration elements.
The following parameters may be returned for manual documentation registration elements:
|
Parameter |
Description |
|
Manual documentation registration identifier |
FH |
|
Free form text identifier |
3 for literal text |
|
Type of free form text |
P15 for Manual Document |
|
Free form text of information: |
Free form text |
|
Passenger type |
Indicating the type of passenger for the ticket |
|
Numeric airline code |
3 digit code identifying the airline responsible for the ticket endorsement |
|
Ticket number |
Ticket number (with or without a check digit) |
|
Last conjunction ticket number |
Last two digits of a conjunctive ticket number plus the check digit |
|
Miscellaneous text |
Any other information stored (I.e., Invoice number) |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a manual document registration element as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Remark reference number |
16 |
|
2 |
Invoice remark identifier |
FH |
|
3 |
Remark line number |
14 |
|
4 |
Free form text information for manual document registration information: |
|
|
5 |
Pax Type |
INF |
|
6 |
Numeric airline code |
057 |
|
7 |
Ticket number (with check digit) |
12345678903 |
|
8 |
Last conjunction ticket number |
914 |
|
9 |
Miscellaneous text: Invoice Number |
//INV - 0000612345 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/reference/qualifier |
OT |
|
|
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/reference/number |
16 |
|
|
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/segmentName |
FH |
|
|
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/lineNumber |
14 |
|
|
/dataElementsMaster/dataElementsIndiv [7]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
|
/dataElementsMaster/dataElementsIndiv [7]/otherDataFreetext/freetextDetail/type |
P15 |
|
|
/dataElementsMaster/dataElementsIndiv [7]/otherDataFreetext/longFreetext |
INF 057-12345678903-914//INV - 0000612345 |
2.8.8. Miscellaneous Ticketing Information Elements
A miscellaneous ticketing information element may be stored in the PNR to record data for accounting purposes. Two types of miscellaneous ticketing information elements may be stored:
|
· |
Information with split transitional stored ticket (TST) |
|
· |
Information with out split transitional stored ticket (TST) |
The following parameters may be returned for the miscellaneous information element:
|
Parameter |
Description |
|
Miscellaneous ticketing information element identifier |
FS - information with TST split FZ - information no TST split |
|
Free form text identifier |
3 - literal text |
|
Type of free form text |
17 - ticketing information |
|
Miscellaneous information |
Free flow text |
The following is an extract of the POWERED PNR Reply structure to illustrate a miscellaneous ticketing information element as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Miscellaneous ticketing information element reference number |
16 |
|
2 |
Miscellaneous ticketing information element identifier for split TST |
FS |
|
3 |
Miscellaneous ticketing information line number |
37 |
|
4 |
Information identifier |
3 |
|
5 |
Information subtype |
17 |
|
6 |
Miscellaneous ticketing information |
SK CMPSCA003FI |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
16 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
FS |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
37 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
17 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
SK CMPSCA003FI |
Note that the reply structure remains the same with a miscellaneous ticketing information element for a non split TST, in which case the element identifier would be FZ in item number 2 above.
2.8.9. Original Issue/Issue in Exchange For Elements
An original issue / issue in exchange for element will be stored in the PNR when a new ticket is exchanged for an MCO, airline voucher or another ticket. The information can identify an original document issued, or the original document information as well as the new document issued for the original document being exchanged.
The following elements may be returned for an original issue/issue in exchange for element:
|
Parameter |
Description |
|
Original issue/issue in exchange for element identifier |
FO |
|
Free form text identifier |
3 for literal text |
|
Type of free form text |
45 for Original issue information |
|
Free form text of information: |
Free form text |
|
Passenger type |
|
|
Voucher/Certificate indicator |
|
|
RN indicator |
|
|
Original issue |
|
|
Numeric airline code |
3 digit code identifying the airline responsible for the original document |
|
Document number of the original issue document |
10 digit ticket number (with or without a check digit) and 1 digit check digit of the original document |
|
Coupon identifier |
C = Coupon E = Exchange |
|
Coupon number |
1 to 4 digit number of coupon used in exchange |
|
Original last conjunctive number |
Last two digits of last conjunctive ticket number with check digit of original document |
|
City |
City code of original issue |
|
Date |
Date of the original issue |
|
IATA number after tag / |
IATA number of agency for original document issued |
|
Issue in exchange |
|
|
New issuing airline code |
3 digit code identifying the airline responsible for the new document |
|
New document number |
10 digit ticket number (with or without a check digit) and 1 digit check digit of the new document |
|
Coupon number identifier |
C = Coupon E = Exchange |
|
Coupon number |
1 to 4 digit number of coupon used in exchange |
|
New last conjunction document |
Last two digits of last conjunctive ticket number with check digit of new document |
|
City |
City code of new document |
|
Date |
Date of the new issue |
|
IATA number after tag / |
IATA number of agency for new document issued |
|
Value of document |
Currency code and value of document taken in exchange: Currency Code Amount Base fare Amount Total tax Amount Penalty Amount |
|
Miscellaneous information |
Any other free form text |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
Please note that the information returned is free form text. Therefore, all of the information identified in the structure above is not mandatory. The type of information returned is dependent upon what has been stored in the PNR by the agent issuing the exchange.
2.8.9.1. Reply Structure of single exchange documents
The following is an extract of the POWERED PNR Reply structure to illustrate an original issue/issue in exchange element identifying an original document issued for an infant passenger as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Original issue element reference number |
17 |
|
2 |
Original issue element identifier |
FO |
|
3 |
Original issue element line number |
18 |
|
4-6 |
Original issue Information: |
|
|
Passenger type |
INF |
|
|
Numeric airline code |
117 |
|
|
Document number of the original issue document |
1234567890 |
|
|
City code of new document |
LON |
|
|
Date of the original issue |
29JUN01 |
|
|
Miscellaneous information |
INFANT TICKET |
|
Item |
PoweredPNR_PNRReply - Data element |
|
|
0 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/number |
17 |
|
2 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/segmentName |
FO |
|
3 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/lineNumber |
18 |
|
4 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/freetextDetail/type |
45 |
|
6 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/longFreetext |
INF117-1234567890LON29JUN01//INFANT TICKET |
2.8.10. Override Invoice Total Amount Remark Elements
A remark may be stored in the PNR to override the total amount on invoice documents. Such remarks are returned as override invoice total amount remarks.
The following parameters are returned for the override invoice total amount remark element:
|
Parameter |
Description |
|
Invoice remark identifier |
RI |
|
Invoice remark type |
RI |
|
Invoice remark category |
T |
|
Free flow remark text |
Maximum of 64 characters, identifying; · 3 character currency code · Positive or negative currency amount · Miscellaneous information |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
The following is an extract of the POWERED PNR Reply structure to illustrate a remark to override the total invoice amount printed on the invoice document as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Override total amount on invoice element reference number |
18 |
|
2 |
Invoice remark identifier |
RI |
|
3 |
Override total amount on invoice line number |
11 |
|
4 |
Invoice remark type |
RI |
|
5 |
Invoice remark category |
T |
|
6 |
Override information: |
|
|
Currency code |
EUR |
|
|
Positive currency amount |
320.10 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
18 |
|
2 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
11 |
|
4 |
/dataElementsMaster/dataElementsIndiv [4]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [4]/miscellaneousRemarks/remarks/category |
T |
|
6 |
/dataElementsMaster/dataElementsIndiv [4]/miscellaneousRemarks/remarks/freetext |
EUR320.10 |
2.8.11. Ticketing Carrier Designator Elements
A validating airline code may be stored in the PNR to identify the airline accounting office used for validation of the tickets issued. Such information is returned as a ticketing carrier designator element.
The following parameters are returned for the ticketing carrier designator element:
|
Parameter |
Description |
|
Ticketing carrier designator identifier |
FV |
|
Information identifier |
3 - literal text |
|
Information sub type |
P18 - Ticketing Carrier |
|
Airline Code |
2 character airline code identifying the validating airline. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
The following is an extract of the POWERED PNR Reply structure to illustrate a ticketing carrier designator element as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Ticketing carrier designator element reference number |
15 |
|
2 |
Ticketing carrier designator element identifier |
FV |
|
3 |
Ticketing carrier line number |
38 |
|
4 |
Information identifier |
3 - literal text |
|
5 |
Information subtype |
P18 |
|
6 |
Carrier Code |
SK |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
15 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
FV |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
38 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
P18 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
SK |
2.8.12. Ticket Number for Automated Tickets Elements
The Amadeus system stores a unique ticket number for each passenger in the PNR when a ticket is issued. The ticket numbers are returned in the ticket number for automated tickets element.
The following parameters will be returned for a ticket number for automated tickets element:
|
Parameter |
Description |
|
Automated ticket number element identifier |
FA |
|
Free form text identifier |
3 for literal text |
|
Type of free form text |
P06 for Automated Ticket |
|
Automated ticket information: |
Free form text |
|
Passenger type |
Code identifying the passenger type on the ticket |
|
Numeric airline code |
3 digit code identifying the airline responsible for the ticket endorsement |
|
10 digit ticket number |
Ticket number |
|
Last conjunction document |
Last two digits of a conjunctive ticket number |
|
Electronic ticket carrier |
Carrier code for electronic ticket |
|
Electronic ticket reservation confirmation number |
RCI followed by the confirmation number |
|
Free text from the Ticket Answer message |
Miscellaneous text |
|
Currency code |
3 character currency code identifying the currency of the ticket issued |
|
Amount |
Total ticket amount |
|
Date |
Local ticketing date |
|
Office ID |
Amadeus Office ID issuing the ticket |
|
IATA |
Office issuing the ticket |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an automated ticket number element associated to a specific passenger and specific itinerary element as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Automated ticket number element reference number |
15 |
|
2 |
Automated ticket number element identifier |
FA |
|
3 |
Automated ticket number line number |
5 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
P06 - automated ticket number |
|
6 |
Automated ticket number information: |
|
|
Passenger type code |
PAX |
|
|
3 digit airline code |
125 |
|
|
10 digit document number |
7028232108 |
|
|
Currency code |
USD |
|
|
Total ticket amount |
100.00 |
|
|
Date |
15MAY01 |
|
|
IATA |
05899843 |
|
|
Office ID |
SFO1S2101 |
|
|
7-8 |
Passenger association |
Passenger reference number 1 |
|
9-10 |
Segment association |
Itinerary element reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
15 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
FA |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
5 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/type |
P06 |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/longFreetext |
PAX125-7028232108/USD100.00/15MAY01/SFO1S2101/05899843 |
|
7 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/number |
1 |
|
9 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/qualifier |
ST |
|
10 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/number |
1 |
2.8.13. Transmission Control Number Elements
The Amadeus system stores a transmission control number for each passenger in the PNR when a ticket is issued. The transmission control numbers are returned in the transmission control number element.
The following parameters may are returned for the transmission control number element:
|
Parameter |
Description |
|
Transmission control element identifier |
FN |
|
Free text identifier |
3 for literal text |
|
Type of free text |
P17 for Control number |
|
Transmission control information: |
Free form text |
|
Passenger type |
Code identifying the passenger type on the ticket |
|
Amadeus system provider code |
7906 |
|
Transmission control number |
11 digit control number |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Association passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a transmission control number element associated to a specific passenger and specific itinerary element as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Transmission control number element reference number |
13 |
|
2 |
Transmission control number element identifier |
FN |
|
3 |
Transmission control number line number |
7 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
P17 for control number |
|
6 |
Transmission control number information: |
|
|
Passenger type |
PAX |
|
|
Amadeus system provider code |
7906 |
|
|
Transmission control number |
13537190315 |
|
|
7- 8 |
Passenger association |
Passenger reference number 1 |
|
9-10 |
Segment association |
Itinerary element reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/number |
13 |
|
2 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/segmentName |
FN |
|
3 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/lineNumber |
7 |
|
4 |
/dataElementsMaster/dataElementsIndiv [5]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [5]/otherDataFreetext/freetextDetail/type |
P17 |
|
6 |
/dataElementsMaster/dataElementsIndiv [5]/otherDataFreetext/longFreetext |
PAX790613537190315 |
|
7 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[1]/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[1]/number |
1 |
|
9 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[2]/qualifier |
ST |
|
10 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[2]/number |
1 |
Fare elements pertain to any elements stored in the PNR, which are specific to fare calculations for the PNR (I.e., Fare Discounts, Commissions, etc).
The information returned in the Powered PNR Reply structure is dependent upon the type of fare element.
2.9.1. Specific Structural Elements
The following structural elements are specific to the itinerary elements when they are returned in the Powered PNR Reply Structure;
Each fare element is qualified [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/Each fare element has an associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This line item number is an indication to the order in which the fare elements are stored within the Amadeus PNR. It is used to identify the specific document element for any subsequent modifications or cancellations.Each fare element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the elements were created within the Amadeus PNR.2.9.1.4. Information Type qualifier
The information in each element is returned as free form text and classified with a subject qualifier of 3 - literal text [/PoweredPNR_PNRReply/dataElementsMaster/
dataElementsIndiv
2.9.1.4.1. Information Sub Type Codes
The following identifies the possible subtype classifications for fare elements:
|
Subtype |
Description |
|
10 |
Endorsement information |
|
11 |
Commission information |
|
16 |
Form of payment information |
|
P04 |
Fare Discount |
|
P05 |
Fare Print Override |
2.9.2. Fare Commission Elements
An element identifying the amount of commission earned by the agency for the ticket fare amount can be stored in the PNR. This information is returned in a fare commission element.
2 formats exist for storing the fare commission amount:
|
· |
Commission by percentage (with or without decimals) |
|
· |
Commission actual amount |
The following type codes may be returned for the fare commission element stored:
|
Code |
Description |
|
A |
Actual commission amount specified |
|
C |
System generated commission, including auto-capping |
|
CR |
Reuse of system generated commission |
|
M |
Manual commission |
|
N |
Net remit commission |
|
P |
Commission through manual capping or semi-auto capping |
|
PR |
Reuse of manual capping or semi-auto capping |
|
XO |
Old commission amount |
|
XP |
Penalty commission |
The following parameters may be returned for the fare commission element:
|
Fare commission identifier |
FM |
|
Free text identifier |
3 for literal text |
|
Type of free text |
11 for Commission information |
|
Fare commission information: |
Free form text |
|
Passenger type |
Code identifying the passenger type on the ticket |
|
Commission indicator |
Type of commission (M,C,P,CR,PR) |
|
Commission |
|
|
Percentage |
Maximum of 2 decimals |
|
Amount indicator |
A |
|
Amount |
Actual Amount of commission |
|
VAT indicator |
V |
|
Net remit indicator |
N |
|
Old commission identifier |
XO |
|
Percentage |
Maximum of 2 decimals |
|
Amount identifier |
A |
|
Amount |
Actual amount of commission |
|
VAT indicator |
V |
|
Manual capping identifier |
C |
|
Amount |
Amount for commission capping |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
2.9.2.3. Reply Structure of simple commission element
The following is an extract of the POWERED PNR Reply structure to illustrate a fare commission element associated to a specific passenger and specific itinerary element as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Fare commission element reference number |
10 |
|
2 |
Fare commission element identifier |
FM |
|
3 |
Fare commission line number |
7 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
11 for commission |
|
6 |
Fare commission information: |
|
|
Manual commission type code |
M |
|
|
Commission percentage |
8 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
10 |
|
2 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
FM |
|
3 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
7 |
|
4 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/type |
11 |
|
6 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/longFreetext |
*M*8 |
A fare discount code may be stored in the PNR to facilitate proper discount pricing for a PNR. The fare discount information is returned in the fare discount element. Coinciding with the fare discount system limitations, a maximum of 3 fare discounts per passenger or itinerary element may be returned.
The following parameters may be returned for a fare discount element:
|
Parameter |
Description |
|
Fare discount element identifier |
FD |
|
Free text identifier |
3 for literal text |
|
Type of free text |
P04 for Fare Discount |
|
Fare discount information: |
Free form text |
|
Passenger type |
Code identifying the passenger type on the ticket |
|
Discount code |
Code identifying the type of discount |
|
Discount percentage |
Percentage amount for discount |
|
Status code |
Status Code of element |
|
Date of birth |
Date of birth for infant/child/senior discounts |
|
Age |
Age of infant or child |
|
Airline code |
Airline code for applicable discount |
|
Numeric value |
Amount of discount |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
The following status codes may be returned in the fare discount reply structure:
|
Status code |
Description |
|
N1, R1, S1 |
If the PNR is already stored |
|
N2, R2, S2 |
If the PNR is in creation mode and not yet stored. |
The following fare discount codes may be returned in the reply structure:
|
Code |
Description |
|
AD |
Agent discount |
|
CD |
Senior discount |
|
CG |
Tour conductor discount |
|
CH |
Child discount |
|
CL |
Clergy discount |
|
CN |
Adult with companion discount |
|
CP |
Companion discount |
|
DB |
Seriously disabled passenger discount |
|
DG |
Government official discount |
|
DL |
Labor discount |
|
DT |
Teacher discount |
|
EM |
Emigrant discount |
|
GC |
Group discount |
|
GP |
School group discount |
|
GV |
Group - inclusive tour discount |
|
ID |
Air industry employee discount |
|
IN |
Infant discount |
|
IT |
Individual inclusive tour discount |
|
MM |
Military discount |
|
PD |
Family discount |
|
PH |
Family - head of family discount |
|
RG |
General sales agent discount |
|
RP |
Regular passenger discount |
|
SC |
Seaman discount |
|
SD |
Student discount |
|
SE |
Special event discount |
|
SH |
Spouse discount |
|
ST |
Spouse - accompanying discount |
|
UU |
Standby discount |
|
ZS |
Youth discount - student certificate required |
|
ZZ |
Youth discount |
2.9.3.2. Reply Structure for simple military discount
The following is an extract of the POWERED PNR Reply structure to illustrate a fare discount element identifying a military passenger discount as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Fare discount element reference number |
21 |
|
2 |
Fare discount element identifier |
FD |
|
3 |
Fare discount line number |
15 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
P04 for fare discount |
|
6 |
Fare discount information: |
|
|
Passenger type code |
PAX |
|
|
Discount code |
MIL |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/reference/number |
21 |
|
2 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/segmentName |
FD |
|
3 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/lineNumber |
15 |
|
4 |
/dataElementsMaster/dataElementsIndiv [8]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [8]/otherDataFreetext/freetextDetail/type |
P04 |
|
6 |
/dataElementsMaster/dataElementsIndiv [8]/otherDataFreetext/longFreetext |
PAX MIL |
2.9.3.3. Reply Structure for infant discount with date of birth and age
The following is an extract of the POWERED PNR Reply structure to illustrate a fare discount element identifying an infant discount identifying the infant's date of birth and age for the discount as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Fare discount element reference number |
24 |
|
2 |
Fare discount element identifier |
FD |
|
3 |
Fare discount line number |
16 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
P04 for fare discount |
|
6 |
Fare discount information: |
|
|
Passenger type code |
INF |
|
|
Discount code |
IN |
|
|
Infant's date of birth |
19APR01 |
|
|
Infant's age |
02MTH |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/reference/number |
24 |
|
2 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/segmentName |
FD |
|
3 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/lineNumber |
16 |
|
4 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/freetextDetail/type |
P04 |
|
6 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/longFreetext |
INF IN19APR01/02MTH |
2.9.4. Fare Endorsement/Restriction Elements
An endorsement or restriction identifying any restrictions, airline comments or rules that apply to the ticket may be stored in the PNR. This information is returned in the fare endorsement/restriction element.
The fare endorsement/restriction information may be manually stored in the PNR or automatically placed in the PNR by the Amadeus fare server. Manually stored information is identified with M.
The following parameters may be returned for a fare endorsement/restriction element:
|
Parameter |
Description |
|
Fare endorsement/restriction identifier |
FE |
|
Free text identifier |
3 for literal text |
|
Free text type |
10 for Endorsement information |
|
Fare endorsement/restriction information |
Maximum of 126 characters free form text |
|
Passenger type |
Code identifying the passenger type on the ticket |
|
Airline discount certificate |
Specific airline restriction/endorsements |
|
Airline code |
3 digit numeric airline identifier |
|
Certificate number |
Certificate number being used |
|
Check digit |
Check digit for certificate |
|
Free flow text |
Miscellaneous information/rules |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a manually stored fare endorsement/restriction element identifying that the ticket is not refundable as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Fare endorsement/restriction element reference number |
22 |
|
2 |
Fare endorsement/restriction element identifier |
FE |
|
3 |
Fare endorsement/restriction line number |
17 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
10 for endorsement information |
|
6 |
Fare endorsement/restriction information: |
|
|
Passenger type code |
PAX |
|
|
Manually stored information indicator |
M |
|
|
Endorsement information |
NOT REFUNDABLE |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/reference/number |
22 |
|
2 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/segmentName |
FE |
|
3 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/lineNumber |
17 |
|
4 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/freetextDetail/type |
10 |
|
6 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/longFreetext |
PAX M NOT REFUNDABLE |
2.9.5. Form of Payment Elements
2.9.5.1. Form of payment for itinerary segments element
A form of payment may be stored in the PNR to indicate how tickets are to be paid for. This element is processed when issuing a ticket. Coinciding with the form of payment for itinerary segment element processing, each element may contain mixed partial forms of payment.
Three forms of payment may exist:
|
· |
Cash |
|
· |
Check |
|
· |
Credit Card |
2.9.5.1.1. Form of payment as Cash or Check
The following parameters may be returned for a cash or check form of payment for itinerary segments element:
|
Parameter |
Description |
|
Credit card form of payment identifier |
FP |
|
Free text identifier |
3 for literal text |
|
Free text type |
16 for form of payment |
|
Form of payment information |
Free Text |
|
Cash form |
CASH |
|
Check form |
CHECK |
|
Currency code |
Currency code being used |
|
Currency amount |
Amount to be paid for with the form of payment indicated. |
|
Segment association |
SS for Segment Tatoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a cash form of payment element as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Credit Card form of payment element reference number |
9 |
|
2 |
Credit Card form of payment element identifier |
FP |
|
3 |
Credit Card form of payment line number |
8 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
16 for form of payment |
|
6 |
Form of payment information: |
CASH |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/reference/number |
9 |
|
2 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/segmentName |
FP |
|
3 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/lineNumber |
8 |
|
4 |
/dataElementsMaster/dataElementsIndiv [6]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [6]/otherDataFreetext/freetextDetail/type |
16 |
|
6 |
/dataElementsMaster/dataElementsIndiv [6]/otherDataFreetext/longFreetext |
*CASH |
2.9.5.1.3. Form of payment as credit card
The following parameters may be returned for a credit card form of payment for itinerary segments element:
|
Parameter |
Description |
|
Credit card form of payment identifier |
FP |
|
Free text identifier |
3 for literal text |
|
Free text type |
16 for form of payment |
|
Credit card form of payment information |
Free form text |
|
Credit card identifier |
CC |
|
Credit card number |
Number of credit card |
|
Expiry date |
Date of expiration for credit card number |
|
Manual approval code identifier |
N |
|
Manual approval code number |
Number of approval received |
|
Currency code |
Currency code being used |
|
Currency amount |
Amount to be paid for with the form of payment indicated. |
|
Segment association |
SS for Segment Tattoo+SubTattoo reference numberST for Segment Tattoo reference number |
|
Associated itinerary element reference number |
|
|
Passenger association |
PT for Passenger Tattoo reference number |
|
Associated passenger reference number |
2.9.5.1.4. Reply structure of single credit card form of payment
The following is an extract of the POWERED PNR Reply structure to illustrate a credit card form of payment as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Credit Card form of payment element reference number |
31 |
|
2 |
Credit Card form of payment element identifier |
FP |
|
3 |
Credit Card form of payment line number |
20 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Type of free text |
16 for form of payment |
|
6 |
Credit Card form of payment information: |
|
|
Credit card identifier |
CC |
|
|
Credit card number |
VI4974830544671492 |
|
|
Expiry date |
0300 |
|
|
Manual approval code identifier |
N |
|
|
Manual approval code number |
605664 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/reference/number |
31 |
|
2 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/segmentName |
FP |
|
3 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/lineNumber |
20 |
|
4 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/freetextDetail/type |
16 |
|
6 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/longFreetext |
CCVI4974830544671492/0300/N605664 |
2.9.5.2. Form of payment for auxiliary segments element
A form of payment may be stored in the PNR to indicate how auxiliary elements are to be paid for. This element is informational, and is processed when issuing an invoice.
The following parameters are returned for a form of payment for auxiliary segments element:
|
Parameter |
Description |
|
Invoice remark identifier |
RI |
|
Itinerary/invoice remark type |
RI |
|
Invoice and itinerary remark category |
U |
|
Free flow remark text |
Maximum of 64 characters, identifying · Form of payment type, · Positive or negative currency amount · Free flow text explanation about the form of payment. |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference numbers |
The following is an extract of the POWERED PNR Reply structure to illustrate an auxiliary form of payment associated to a passenger name as outlined below:
|
Item # |
Parameter |
Parameter Information |
|
0 |
Element Qualifier |
OT |
|
1 |
Auxiliary form of payment element reference number |
10 |
|
2 |
Invoice remark identifier for Auxiliary form of payment element identifier |
RI |
|
3 |
Auxiliary form of payment line number |
5 |
|
4 |
Invoice remark type for auxiliary form of payment element |
RI |
|
5 |
Invoice remark category for auxiliary form of payment |
U |
|
6 |
Auxiliary form of payment information: |
CHECK DEPOSIT 150.00 REMAINDER UPON DELIVERY |
|
7- 8 |
Passenger association |
Passenger reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
10 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
RI |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
5 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/miscellaneousRemarks/remarks/type |
RI |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/miscellaneousRemarks/remarks/category |
U |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/miscellaneousRemarks/remarks/freetext |
CHECK DEPOSIT 150.00 REMAINDER UPON DELIVERY |
|
7 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/number |
1 |
2.10. ELEMENT: INFORMATIONAL ELEMENTS
Informational elements pertain to any elements stored in the PNR which have no bearing on how documents are produced, how fares are calculated, or on specific reservations held. But rather, are informational elements to be printed on documents or referenced by other agents.
The information returned in the Powered PNR Reply structure is dependent upon the type of informational element.
2.10.1. Specific Structural Elements
The following structural elements are specific to the itinerary elements when they are returned in the Powered PNR Reply Structure;
Each informational element is qualified [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/Each informational element has an associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This line item number is an indication to the order in which the elements are stored within the Amadeus PNR. It is used to identify the specific element for any subsequent modifications or cancellations.Each informational element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the elements were created within the Amadeus PNR.2.10.1.4. Information Type qualifier
The information in each element is classified with a subject qualifier of 3 - literal text [/PoweredPNR_PNRReply/dataElementsMaster/
dataElementsIndiv
2.10.1.4.1. Information Sub Type Codes
The following identifies the possible subtype classifications for informational elements:
|
Subtype |
Description |
|
2 |
Address (home or hotel) |
|
3 |
Business phone |
|
4 |
Home phone number |
|
5 |
Telephone nature not known |
|
6 |
Travel agent telephone number |
|
12 |
Tour number |
|
28 |
Other Service Information (OSI) |
|
P01 |
Fax number |
|
P02 |
E-mail address |
|
P03 |
Internet address |
|
P08 |
Mailing address |
|
P09 |
Address verification |
|
P10 |
AK - Train pending information |
|
P15 |
Manual Document |
|
P19 |
Miscellaneous information |
|
P21 |
Option information |
|
P24 |
Home address for mailing address |
|
P25 |
Delivery address for mailing address |
|
P26 |
For Tour operator name (PNRBCS message) |
|
P27 |
For Other Special information free text - OS lines. |
2.10.2. Billing Address Elements
A billing address may be stored in the PNR to indicate where an invoice document is to be sent. Such an address is returned in billing address element.
Two forms of the address may be returned:
|
· |
Free Form Address text |
|
· |
Structured Address text |
2.10.2.1. Free Form Address Text
The following parameters may be returned for a billing address element stored with free form address text:
|
Parameter |
Description |
|
Billing Address Element Identifier |
AB |
|
Free form text identifier |
3 - literal text |
|
Free form text type |
2 - address home or hotel |
|
Address |
Free flow text of maximum 126 characters |
|
Passenger association |
PT |
|
Associated Passenger Reference Number |
2.10.2.1.1. Reply Structure for free form text
The following is an extract of the POWERED PNR Reply structure to illustrate a billing address element in free form style as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Billing address reference number |
19 |
|
2 |
Billing address identifier |
AB |
|
3 |
Billing address line number |
39 |
|
4- 6 |
Billing address |
2308 ERIN LANE |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
19 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
AB |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
39 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
2 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
2308 ERIN LANE |
2.10.2.2. Structured Address Text
Each structured address information item is stored individually associated with a code identifying the type of billing information that it is. The following parameters may be returned for a billing address element stored with structured address text:
|
Parameter |
Code |
Description |
|
Billing Address Element Identifier |
AB |
|
|
Information qualifier |
3 - literal text |
|
|
Information subtype |
2 - address home or hotel |
|
|
Company name |
CY |
Maximum 30 characters |
|
Name |
NA |
Maximum 30 characters |
|
Address line one |
A1 |
Maximum 50 characters |
|
Address line two |
A2 |
Maximum 50 characters |
|
Post office box |
PO |
Maximum 8 characters |
|
Postal zip code |
ZP |
Maximum 20 characters |
|
City |
CI |
Maximum 30 characters |
|
State |
ST |
Maximum 25 characters |
|
Country |
CO |
Maximum 25 characters |
|
Type of address |
H = HOME D = DELIVERY M = MISCELLANEOUS |
|
|
Passenger association |
Identifies a particular passenger to which the address is associated. |
|
2.10.2.2.1. Reply Structure for structured text
The following is an extract of the POWERED PNR Reply structure to illustrate a structured billing address element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Billing address reference number |
5 |
|
2 |
Billing address identifier |
AB/ |
|
3 |
Billing address line number |
6 |
|
4 |
Structured billing address type of information |
2 |
|
5 - 6 |
Company name |
YABA DABA COMPANY INC |
|
7- 8 |
Traveler name |
MR JOHNSON |
|
9-10 |
Address line 1 |
155 CORNER RD |
|
11-12 |
Postal code |
46515 |
|
13-14 |
City |
GOSHEN |
|
15-16 |
Country |
UNITED STATES |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
5 |
|
2 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
AB/ |
|
3 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
6 |
|
4 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/informationType |
2 |
|
5 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[1]/option |
CY |
|
6 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[1]/optionText |
YABA DABA COMPANY INC |
|
7 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[2]/option |
NA |
|
8 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[2]/optionText |
MR JOHNSON |
|
9 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[3]/option |
A1 |
|
10 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[3]/optionText |
155 CORNER RD |
|
11 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[4]/option |
ZP |
|
12 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[4]/optionText |
46515 |
|
13 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[5]/option |
CI |
|
14 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[5]/optionText |
GOSHEN |
|
15 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[6]/option |
CO |
|
16 |
/dataElementsMaster/dataElementsIndiv [4]/structuredAddress/address[6]/optionText |
UNITED STATES |
Note that a structured billing address is not identified as free form text [3-literal text], but only rather only as a structured billing address [/dataElementsMaster/dataElementsIndiv
[4]/structuredAddress/
2.10.3. Confidential Option Elements
Confidential option elements may be stored in the PNR that have limited retrieval access to only designated offices. Such elements are returned as confidential option elements.
Two types of confidential option elements exist:
|
· |
Automatic Cancel |
Coinciding with confidential option element limitations, a maximum of 1 confidential option element consisting of a maximum of 124 characters may be returned.
2.10.3.1. Automatic Cancel Option Element
On the specified date/time the air elements belonging to the airline that added the automatic cancel option element would be cancelled automatically unless the element is removed from the PNR before the specified date/time.
The following parameters may be returned for an automatic cancel confidential option element:
|
Parameter |
Description |
|
Option Element Identifier |
OP |
|
Free form text identifier |
3 - literal text |
|
Free form text type |
P21 for Option information |
|
Automatic queue information: |
Free form text |
|
Receiving office id |
One Amadeus office ID |
|
Cancel PNR indicator |
X |
|
Cancellation queue date |
Maximum of 1 date |
|
Cancellation queue Time |
Maximum of 1 time |
|
Queue Number and Category |
Maximum of 1 queue and category. *Default value of Q3C0 for non-group PNRs and Q87C12 for group PNRs.* |
|
Miscellaneous Free form text |
Maximum of 83 characters |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an automatic cancel option element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Automatic queue element reference number |
18 |
|
2 |
Automatic queue identifier |
OP |
|
3 |
Automatic queue line number |
6 |
|
4 |
Free form text identifier |
3 |
|
5 |
Free form text type |
P21 |
|
6 |
Automatic queue information: |
|
|
Receiving office id |
MUC1A0701 |
|
|
Cancel PNR indicator |
X |
|
|
Cancellation date |
07JUL |
|
|
Miscellaneous queue text |
CANCEL TICKET |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
18 |
|
2 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
OP |
|
3 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
6 |
|
4 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/type |
P21 |
|
6 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/longFreetext |
MUC1A0701/15MAY/X7JUL/CANCEL TICKET |
A PNR must include a contact element to indicate where passenger can be contacted.
Coinciding with the contact element limitations, a maximum of 127 contact elements can be returned.
The following parameters may be returned for a contact element:
|
Parameter |
Description |
|
Contact Element Identifier |
AP |
|
Free form text identifier |
3 - literal text |
|
Free form type of text(type of Contact) |
3= business 4= home 5 = unknown type 6= agency P01= fax |
|
Contact information: |
|
|
City Code |
3 character city location of the number |
|
Contact Information |
Free form text |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a contact element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Contact reference number |
6 |
|
2 |
Contact identifier |
AP |
|
3 |
Contact line number |
20 |
|
4 |
Free form text identifier |
3 |
|
5 |
Free form text type |
5 - unknown type |
|
6 |
Contact information: |
|
|
City code |
CHI |
|
|
Telephone number |
773 772 5050 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
6 |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
AP |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
20 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
5 |
|
7 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
CHI 773 772 5050 |
2.10.5. Individual PNR Security Elements
Amadeus individual PNR security elements may exist in a PNR to allow or restrict one or several other offices access to the PNR regardless of other securities in place. Coinciding with the individual PNR security element limitations, a maximum of 5 offices may be returned.
The following parameters are returned for individual PNR security elements:
|
Parameter |
Description |
|
Individual PNR Security Element Identifier |
ES |
|
Office ID |
Office ID receiving access |
|
Access mode given |
R =read onlyB=both read and write N=No access regardless |
|
Creation date for access |
Date access was given |
|
Agent sign code for access given |
2 character agent system sign followed by 2 character system duty code |
|
Owner ID |
Office ID owning the PNR |
|
Receiver type |
Type of office id(s) being specified G=global core office ID I=IATA number P=Psuedo office ID |
2.10.5.1. Reply Structure of single office access
The following is an extract of the POWERED PNR Reply structure to illustrate an individual PNR security element as outlined below:
|
Item # |
Parameter |
Information |
|
0 |
Security element identifier |
ES |
|
1 |
Receiving Office ID |
MIA1S1101 |
|
2 |
Access mode given |
20 |
|
3 |
Creation date for access |
N - no access regardless |
|
4 |
Agent sign code for access given |
AASU |
|
5 |
Owner ID |
MUC1A0701 |
|
6 |
Receiver type |
G - global core |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/segmentName |
ES |
|
1 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/security/identification |
MIA1S1101 |
|
2 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/security/accessMode |
N |
|
3 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/securityInfo/creationDate |
150501 |
|
4 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/securityInfo/agentCode |
AASU |
|
5 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/securityInfo/officeId |
MUC1A0701 |
|
6 |
/dataElementsMaster/dataElementsIndiv [8]/pnrSecurity/indicator |
G |
2.10.6. Mailing Address Elements
A mailing address may be stored in the PNR to indicate where the travel documents are to be sent. Such an address is returned in a mailing address element.
Two forms of the address may be returned:
|
· |
Free Form Address text |
|
· |
Structured Address text |
2.10.6.1. Free Form Address Text
The following parameters may be returned for a mailing address element stored with free form address text:
|
Parameter |
Description |
|
Mailing Address Element Identifier |
AM |
|
Free form text identifier |
3 - literal text |
|
Type of free form text |
P08 - Mailing address |
|
Address information |
Free flow text of maximum 126 characters |
|
Passenger association |
PT Associated passenger reference number |
2.10.6.2. Structured Address Text
Each structured address information item is stored individually associated with a code identifying the type of billing information that it is. The following parameters may be returned for a mailing address element stored with structured address text:
|
Parameter |
Code |
Description |
|
Mailing Address Element Identifier |
AM |
|
|
Free form text identifier |
3 - literal text |
|
|
Type of free form text |
P08 - Mailing address |
|
|
Company name |
CY |
Maximum 30 characters |
|
Name |
NA |
Maximum 30 characters |
|
Address line one |
A1 |
Maximum 50 characters |
|
Address line two |
A2 |
Maximum 50 characters |
|
Post office box |
PO |
Maximum 8 characters |
|
Postal zip code |
ZP |
Maximum 20 characters |
|
City |
CI |
Maximum 30 characters |
|
State |
ST |
Maximum 25 characters |
|
Country |
CO |
Maximum 25 characters |
|
Type of address |
H = HOME D = DELIVERY M = MISCELLANEOUS |
|
|
Passenger association |
PT Associated passenger reference number |
|
2.10.6.3. Reply Structure for free form text
The following is an extract of the POWERED PNR Reply structure to illustrate a mailing address element in free form style as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Mailing address reference number |
20 |
|
2 |
Mailing address identifier |
AM |
|
3 |
Mailing address line number |
40 |
|
4 |
Free text identifier |
3 |
|
5 |
Type of free text |
P08 - mailing address |
|
6 |
Mailing address |
RICK LARSON |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
20 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
AM |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
40 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
P08 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RICK LARSON |
2.10.6.4. Reply Structure for structured text
The following is an extract of the POWERED PNR Reply structure to illustrate a structured billing address element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Mailing address reference number |
6 |
|
2 |
Mailing address identifier |
AM/ |
|
3 |
Mailing address line number |
7 |
|
4 |
Structured Mailing address type of information |
P08 |
|
5 - 6 |
Company name |
ABBY INTL |
|
7- 8 |
Traveler name |
MR JOHNSON |
|
9-10 |
Address line 1 |
12 TINY DR |
|
11-12 |
Postal code |
BS7890 |
|
13-14 |
City |
NEWTON |
|
15-16 |
Country |
UNITED STATES |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/number |
6 |
|
2 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/segmentName |
AM/ |
|
3 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/lineNumber |
7 |
|
4 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/informationType |
P08 |
|
5 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[1]/option |
CY |
|
6 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[1]/optionText |
ABBY INTL |
|
7 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[2]/option |
NA |
|
8 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[2]/optionText |
MR JOHSON |
|
9 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[3]/option |
A1 |
|
10 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[3]/optionText |
12 TINY DR |
|
11 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[4]/option |
ZP |
|
12 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[4]/optionText |
BS7890 |
|
13 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[5]/option |
CI |
|
14 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[5]/optionText |
NEWTON |
|
15 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[6]/option |
CO |
|
16 |
/dataElementsMaster/dataElementsIndiv [5]/structuredAddress/address[6]/optionText |
UNITED STATES |
Note that a structured mailing address is not identified as free form text [3-literal text], but only rather only as a structured mailing address [/dataElementsMaster/dataElementsIndiv
[4]/structuredAddress/
2.10.7.1. Automatic Queue Option Element
On the designated date/time, the PNR will be queue placed to the office ID stored in the ‘Receiving Office ID’ field.
The following parameters may be returned for an automatic queue confidential remark element:
|
Parameter |
Description |
|
Option Element Identifier |
OP |
|
Free form text identifier |
3 - literal text |
|
Free form text type |
P21 for Option information |
|
Automatic queue information: |
Free form text |
|
Receiving office id |
One Amadeus office ID |
|
Queue date |
Maximum of 1 date |
|
Queue Time |
Maximum of 1 time |
|
Queue Number and Category |
Maximum of 1 queue and category. *Default value of Q3C0 for non-group PNRs and Q87C12 for group PNRs.* |
|
Miscellaneous Free form text |
Maximum of 83 characters |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an automatic queue option element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Automatic queue element reference number |
17 |
|
2 |
Automatic queue identifier |
OP |
|
3 |
Automatic queue line number |
5 |
|
4 |
Free form text identifier |
3 |
|
5 |
Free form text type |
P21 |
|
6 |
Automatic queue information: |
|
|
Receiving office id |
MUC1A0701 |
|
|
Queue date |
07JUL |
|
|
Miscellaneous queue text |
ISSUE TICKET |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
17 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
OP |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
5 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/freetextDetail/type |
P21 |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/otherDataFreetext/longFreetext |
MUC1A0701/07JUL/ISSUE TICKET |
2.10.8. Other Service Information Elements
Other service information remarks may be stored in a PNR identifying special information for an airline regarding a passenger or group of passengers in the PNR. Coinciding with other service information elements, a maximum of 127 elements may be returned.
The following parameters may be returned for an other service information element:
|
Parameter |
Description |
|
Other service information Element Identifier |
OS |
|
Free form text identifier |
3 - literal text |
|
Type of free form text |
28 - Other service information |
|
Associated airline to receive information |
Airline code or YY for airlines in the PNR |
|
Other service information |
Free form text |
|
Passenger association |
PT Associated passenger reference number |
|
Segment association |
ST Associated itinerary element reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an other service information element identifying all airlines (YY) of a child passenger as follows:
|
Item # |
Parameter |
Information |
|
1 |
Other service information reference number |
4 |
|
2 |
Other service information identifier |
OS |
|
3 |
Other service information line number |
27 |
|
4 |
Free text identifier |
3 - literal text |
|
5 |
Free text type |
28 - other service |
|
6 |
Associated airline for information |
YY (all airlines in PNR) |
|
7 |
Other service information: |
1 CHD |
|
8-9 |
Passenger association |
Passenger reference number 2 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
4 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OS |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
27 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
3 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
28 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
YY |
|
7 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
1CHD |
|
8 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
PT |
|
9 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
2 |
Three types of remark elements may be stored in the PNR;
|
· |
General Remark Elements |
|
· |
Corporate Remark Elements |
|
· |
Confidential Remark Elements |
2.10.9.1. General Remark Elements
A general remark may be stored in the PNR and can be viewed by any office ID that has permission to view the PNR. The user may categorize these remarks with an identifying letter for ordering purposes. Coinciding with remark element limitations, a maximum of 255 remark elements each consisting of a maximum of 124 characters may be returned.
The following parameters may be returned for a general remark element:
|
Parameter |
Description |
|
Remark Element Identifier |
RM |
|
Remark Type identifier |
RM |
|
Remark Category (OPTIONAL) |
Any letter from A to Z |
|
Remark Text |
Free form text |
|
Segment Association |
ST Associated itinerary element reference numbers |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a general remark element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Remark reference number |
12 |
|
2 |
Remark identifier |
RM |
|
3 |
Remark line number |
32 |
|
4 |
Remark type identifier |
RM |
|
5 |
Remark category |
C |
|
5 |
Remark information |
CORPORTE BOOKING BY ANDY |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
12 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RM |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
32 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RM |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
C CORPORATE BOOKING BY ANDY |
2.10.9.2. Confidential Remark Elements
A confidential remark may be stored in the PNR that has limited retrieval access to only designated offices. Such remarks are returned as a confidential remark element.
The confidential remarks may be associated to a single office id, multiple office id's (maximum of 3), a range of office id's or a corporate family which is defined by a corporate ID code and it's associated group of corporate ID codes stored in the Amadeus system.
Authorization to edit the confidential remark may be specified with a read/write optional element.
Coinciding with confidential remark element limitations, a maximum of 127 confidential remark elements each consisting of a maximum of 124 characters may be returned.
The following parameters may be returned for a confidential remark element:
|
Parameter |
Description |
|
Confidential Remark Element Identifier |
RC |
|
Corporate Family Identifier |
-F if office ids specified are designated corporate family Ids. |
|
Creating office ID |
The office Id creating the confidential remark is automatically stored to allow access. |
|
Designated office Ids |
Amadeus office ids in addition to the creation id that are allowed to access the confidential remark (max of 3) |
|
Access Mode |
-W if read/write access is granted |
|
Remark Text |
Free form text |
|
Segment association |
ST Associated itinerary element reference numbers |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a confidential remark element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Remark reference number |
23 |
|
2 |
Remark identifier |
RC |
|
3 |
Remark line number |
30 |
|
4 |
Remark type identifier |
RC |
|
5 |
Remark text |
VIP CLIENTS |
|
6 |
Creating Office ID |
VSTNA2150 |
|
7 |
Designated Office ID |
MUC1A0701 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/number |
23 |
|
2 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/segmentName |
RC |
|
3 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/lineNumber |
30 |
|
4 |
/dataElementsMaster/dataElementsIndiv [11]/miscellaneousRemarks/remarks/type |
RC |
|
5 |
/dataElementsMaster/dataElementsIndiv [11]/miscellaneousRemarks/remarks/freetext |
VIP CLIENTS |
|
6 |
/dataElementsMaster/dataElementsIndiv [11]/miscellaneousRemarks/remarks/officeId[1] |
VSTNA2150 |
|
7 |
/dataElementsMaster/dataElementsIndiv [11]/miscellaneousRemarks/remarks/officeId[2] |
MUC1A0701 |
* Please note that no office ids will be returned and only the remark text "RESTRICTED" will be returned if the requesting office id is not granted access rights to the data.
2.10.10. Special Service Request Elements
Requests may be stored in the PNR indicating special services required for a specific passenger or group of passengers. Each request is associated to an airline of which the service is requested. Such requests are returned in the special service request element.
As there are numerous special service codes, each containing its' own specific parameter information, it is impossible to cover all special service information parameters that can be returned in this document. Therefore, the following 3 most common forms of special service request types are outlined in this section;
|
· |
Basic Special service remark |
|
· |
Frequent Traveler special service remark |
|
· |
Seats special service remark |
2.10.10.1.1. Special service codes
Each special service remark is identified with an associated special service code. The following special service remark codes may be returned:
|
Code |
Description of service |
|
ADTK |
ADVISE IF TICKETED (PNR WILL BE PLACED IN QUEUE 1, CATEGORY 6 OF THE RESPONSIBLE OFFICE) |
|
AVIH |
ANIMAL IN HOLD, SPECIFY NUMBER, TYPE AND PEDIGREE, AND CONTAINER WEIGHT AND DIMENSIONS (SEE BELOW) |
|
AVML |
ASIAN VEGETARIAN MEAL |
|
BBML |
INFANT/BABY FOOD |
|
BIKE |
BICYCLE IN HOLD, SPECIFY NUMBER (SEE BELOW) |
|
BLML |
BLAND MEAL |
|
BLND |
BLIND, SPECIFY WHETHER OR NOT ACCOMPANIED BY GUIDE DOG |
|
BSCT |
BASSINET/CARRYCOT/BABY BASKET |
|
BULK |
BULKY BAGGAGE, SPECIFY NUMBER, WEIGHT AND DIMENSIONS |
|
CBBG |
CABIN BAGGAGE REQUIRING SEAT(S), SPECIFY NUMBER, WEIGHT AND SIZE (SEE BELOW) |
|
CHML |
CHILD MEAL |
|
CKIN |
INFORMATION FOR AIRPORT PERSONNEL |
|
CLID |
CORPORATE CLIENT CODE USED BY ALL GDSS |
|
COUR |
COMMERCIAL COURIER, SPECIFY WEIGHT AND COURIER COMPANY |
|
CRUZ |
CRUISE PASSENGER |
|
DBML |
DIABETIC MEAL |
|
DEAF |
DEAF, SPECIFY IF ACCOMPANIED BY A GUIDE DOG |
|
DEPA |
DEPORTEE, ACCOMPANIED BY AN ESCORT |
|
DEPU |
DEPORTEE, UNACCOMPANIED |
|
EXST |
EXTRA SEAT (SEE BELOW) |
|
FOID |
FORM OF ID |
|
FPML |
FRUIT PLATTER |
|
FQTR |
FREQUENT FLYER MILEAGE PROGRAM REDEMPTION |
|
FQTS |
FREQUENT FLYER SERVICE REQUEST |
|
FQTU |
FREQUENT FLYER UPGRADE AND ACCRUAL |
|
FQTV |
FREQUENT FLYER MILEAGE PROGRAM ACCRUAL |
|
FRAG |
FRAGILE BAGGAGE, SPECIFY NUMBER, WEIGHT AND DIMENSION |
|
FRAV |
FIRST AVAILABLE |
|
GFML |
GLUTEN-FREE MEAL |
|
GPST |
GROUP SEAT REQUEST, SPECIFY NUMBER AND PREFERRED location |
|
GRPF |
GROUP FARE, SPECIFY FARE CODE |
|
GRPS |
PSGRS TRAVELING TOGETHER USING A COMMON IDENTITY |
|
HFML |
HIGH FIBRE MEAL |
|
HNML |
HINDU MEAL |
|
KSML |
KOSHER MEAL |
|
LANG |
LANGUAGES SPOKEN |
|
LCML |
LOW CALORIE MEAL |
|
LFML |
LOW CHOLESTEROL/ LOW FAT MEAL |
|
LPML |
LOW PROTEIN MEAL |
|
LSML |
LOW SODIUM, NO SALT ADDED MEAL |
|
MAAS |
MEET AND ASSIST, SPECIFY DETAILS SUCH AS ELDERLY PERSON, HANDICAPPED PASSENGER OR PREGNANT LADY |
|
MEDA |
MEDICAL CASE. CAN BE USED FOR DISABLED PASSENGERS NEEDING SPECIAL ATTENTION. FOLLOW IATA MEDA PROCEDURES |
|
MOML |
MOSLEM MEAL |
|
NAME |
NAME - WHEN AIRLINE HOLDS RESERVATION UNDER A DIFFERENT NAME |
|
NLML |
NON LACTOSE MEAL |
|
NSSA |
NO SMOKING AISLE SEAT |
|
NSSB |
NO SMOKING BULKHEAD SEAT |
|
NSST |
NO SMOKING SEAT (SEAT NUMBER MAY BE INCLUDED) |
|
NSSW |
NO SMOKING WINDOW SEAT |
|
ORML |
ORIENTAL MEAL |
|
OTHS |
OTHER SERVICE NOT SPECIFIED BY ANY OTHER SSR CODE |
|
PCTC |
EMERGENCY CONTACT DETAILS FOR PASSENGER (SEE BELOW) |
|
PETC |
ANIMAL IN CABIN, SPECIFY NUMBER, TYPE AND PEDIGREE,AND CONTAINER WEIGHT AND DIMENSION (SEE BELOW) |
|
PRML |
LOW PURIN MEAL |
|
PSPT |
PASSPORT (SEE BELOW) |
|
RQST |
SEAT REQUEST-INCLUDE SEAT NUMBER OR PREFERENCE |
|
RVML |
RAW VEGETARIAN MEAL |
|
SEAT |
PRERESERVED SEAT WITH BOARDING PASS ISSUED OR TO BE ISSUED |
|
SEMN |
SEAMAN - SHIP'S CREW |
|
SFML |
SEA FOOD MEAL |
|
SLPR |
BED/BERTH IN CABIN |
|
SMSA |
SMOKING AISLE SEAT |
|
SMSB |
SMOKING BULKHEAD SEAT |
|
SMST |
SMOKING SEAT (SPECIFIC SEAT NUMBER MAY BE INCLUDED) |
|
SMSW |
SMOKING WINDOW SEAT |
|
SPEQ |
SPORTS EQUIPMENT |
|
SPML |
SPECIAL MEAL, SPECIFY FOOD ITEMS |
|
STCR |
STRETCHER PASSENGER |
|
TKNA |
TICKET NUMBER IN FA ELEMENT |
|
TKNC |
TICKET NUMBER TRANSMISSION |
|
TKNE |
E-TICKET NUMBER IN FA ELEMENT |
|
TKNM |
TICKET NUMBER IN FH ELEMENT |
|
TKTL |
TICKETING TIME LIMIT |
|
TWOV |
TRANSIT OR TRANSFER WITHOUT VISA |
|
UMNR |
UNACCOMPANIED MINOR, SPECIFY AGE |
|
VGML |
VEGETARIAN MEAL (NON-DAIRY) |
|
VLML |
VEGETARIAN MEAL (LACTO-OVO) |
|
WCBD |
WHEELCHAIR - DRY CELL BATTERY |
|
WCBW |
WHEELCHAIR - WET CELL BATTERY |
|
WCHC |
WHEELCHAIR - ALL THE WAY TO SEAT |
|
WCHR |
WHEELCHAIR - FOR RAMP |
|
WCHS |
WHEELCHAIR - UP AND DOWN STEPS |
|
WCMP |
WHEELCHAIR - MANUAL POWER (US CARRIERS ONLY) |
|
WCOB |
WHEELCHAIR - ON BOARD |
|
XBAG |
EXCESS BAGGAGE, SPECIFY NUMBER, WEIGHT AND DIMENSION |
2.10.10.2. Basic Special Service Request
A basic special service remark pertains to any special service remark that returns minimal information for the special service request.
The following outlines the standard reply structure for all Frequent Flyer special service requests:
|
Parameter |
Description |
|
Special Service Request Indentifier |
SSR |
|
Original status code |
Not transmitted |
|
Special Service Type code |
Special requirement type code (VGML, etc) |
|
Airline code |
Airline Company identification |
|
Status code |
Status of special request |
|
Number of passengers |
Quantity |
|
Free flow text |
Free text |
|
Segment association |
SS for Segment Tatoo+SubTatoo reference numberST for Segment Tatoo reference number |
|
Reference number |
|
|
Passenger association |
PT for Passenger Tatoo reference number |
|
Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a basic special service request for a vegetarian meal on a specific itinerary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Special service reference number |
17 |
|
2 |
Special service identifier |
SSR |
|
3 |
Special service line number |
5 |
|
4 |
Special service type code identifier |
VGML |
|
5 |
Special service request status |
HN |
|
6 |
Quantity of request |
1 |
|
7 |
Associated Airline for service |
AF |
|
8-9 |
Segment association |
Itinerary element reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
17 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
SSR |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
5 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/type |
VGML |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/status |
HN |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/quantity |
001 |
|
7 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/companyId |
AF |
|
8 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/qualifier |
ST |
|
9 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/number |
1 |
2.10.10.3. Frequent Flyer Special Service Request
A special service request may be associated to each passenger for each itinerary flight element identifying a frequent traveler number for a particular airline.
The frequent flyer number can be validated or non-validated number from the Amadeus System. If the number has been validated, an indicator will be present in the reply structure.
4 types of Frequent Flyer Special Service Requests may exist. Each type is identified with a specific code found in the reply structure. The following outlines the 4 different types of requests and their associated codes;
|
Frequent Flyer Type Code |
Description |
|
FQTV |
Request frequent traveller mileage accrual |
|
FQTR |
Requests redemption of accrued miles from the account |
|
FQTS |
Requests frequent traveller service benefits |
|
FQTU |
Requests frequent traveller accrual of miles and a class of service upgrade |
The following outlines the standard reply structure for all Frequent Flyer special service requests:
|
Parameter |
Description |
|
Special service request identifier |
SSR |
|
Original status code |
Status code not transmitted |
|
Frequent Flyer type code identifier |
Frequent Flyer requirement type (FQTV, FQTR, FQTS, FQTU) |
|
Airline code |
Associated Airline identification |
|
Status code |
Status of frequent flyer request |
|
Number of passengers |
Quantity |
|
Validated Service Indicator |
P02 indicates Validated Frequent Flyer SSR |
|
Frequent flyer account number |
|
|
Airline code of the frequent flyer account |
Company identification |
|
Number of the frequent flyer account |
Frequent traveler identification code |
|
System or airline priority number |
Membership level of the frequent flyer account |
|
Free flow text |
Free text from airline (teletype, etc) |
|
Segment association |
SS for Segment Tatoo+SubTatoo reference numberST for Segment Tatoo reference number |
|
Reference number |
|
|
Passenger association |
PT for Passenger Tatoo reference number |
|
Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate a frequent flyer special service request for a vegetarian meal on a specific itinerary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Special service reference number |
28 |
|
2 |
Special service identifier |
SSR |
|
3 |
Special service line number |
11 |
|
4 |
Special service type code identifier |
FQTV |
|
5 |
Special service request status |
HK |
|
6 |
Associated airline for service |
BA |
|
7 |
Airline of Frequent traveler number |
BA |
|
8 |
Frequent traveler number |
1287992837463 |
|
9-10 |
Passenger association |
Passenger reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
28 |
|
2 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
SSR |
|
3 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
11 |
|
4 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/type |
FQTV |
|
5 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/status |
HK |
|
6 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/companyId |
BA |
|
7 |
/dataElementsMaster/dataElementsIndiv [3]/frequentTravellerInfo/frequentTraveller/company |
BA |
|
8 |
/dataElementsMaster/dataElementsIndiv [3]/frequentTravellerInfo/frequentTraveller/membershipNumber |
1287992837463 |
|
9 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/qualifier |
PT |
|
10 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference/number |
1 |
2.10.10.4. Seats Special Service Request
A special service request may be associated to each passenger for each itinerary flight element identifying seat preferences or actual seat numbers reserved.
The following outlines the standard reply structure for all seat special service requests:
|
Parameter |
Description |
|
Special service request identifier |
SSR |
|
Original status code |
Not transmitted |
|
Seat Special Service Type Code |
Special requirement type (ADST, NSSA, NSSB, NSST, NSSW, RQST, SEAT, SMSA, SMSB, SMST, SMSW, CBBG, EXST, etc) |
|
Airline code |
Airline Company identification |
|
Status code |
Status of seat request |
|
Number of passengers |
Quantity |
|
Boarding point |
City code of originating location |
|
Off point |
City code of destination |
|
Date for change of gauge |
Date |
|
Up to 2 seat area preferences |
· A for Aisle seat(Amadeus code A) · K for Bulkhead seat(Amadeus code B) · W for Window seat(Amadeus code W) |
|
Passenger type for seat request |
· I for Infant(Amadeus code I) · U for Unaccompanied minor(Amadeus code U) · H for Handicapped(Amadeus code H) · MA for Medically OK(Amadeus code M) |
|
Seat assignment information |
|
|
Seat Location |
Seat number and row |
|
Smoking / non-smoking indicator |
· N for No smoking seat(Amadeus code N) · S for Smoking seat(Amadeus code S) |
|
Passenger to whom the seat is assigned |
PT Passenger reference number |
|
Boarding-pass / change of gauge indicator (RB, RC, RG, RS, RZ) 1. RB boarding passes may not be issued before a certain predetermined time 2. RC an equipment change occurs and boarding passes may not be issued 3. RG an equipment change occurs, boarding passes may be issued 4. RS boarding passes may not be issued 5. RZ an equipment change occurs and boarding passes may not be issued before a certain predetermined time |
Processing indicator B for Boarding pass may not be issued until the mutually agreed time period NB for No a boarding pass may not be issued Y for Yes a boarding pass may be issued NB for No a boarding pass may not be issued B for Boarding pass may not be issued until the mutually agreed time period |
|
Processing indicator PS for Partial segment indicator with change of guage/equipment |
|
|
Boarding-pass issued indicator (BP ISSUED) |
Not transmitted |
|
Free flow text |
Free text |
|
Segment association |
SS for Segment Tatoo+SubTatoo reference numberST for Segment Tatoo reference number |
|
Reference number |
|
|
Passenger association |
PT for Passenger Tatoo reference number |
|
Reference number |
2.10.10.4.2. Reply Structure simple seat
The following is an extract of the POWERED PNR Reply structure to illustrate a seats special service request for a vegetarian meal on a specific itinerary element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Special service reference number |
29 |
|
2 |
Special service identifier |
SSR |
|
3 |
Special service line number |
23 |
|
4 |
Special service type code identifier |
RQST |
|
5 |
Special service request status |
HN |
|
6 |
Quantity of request |
1 |
|
7 |
Associated Airline for service |
AA |
|
8 |
Flight origin |
SDQ |
|
9 |
Flight destination |
SJU |
|
10 |
Specific seat number requested |
01F |
|
11-12 |
Passenger association |
Passenger reference number 5 |
|
13-14 |
Segment association |
Itinerary element reference number 5 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
29 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
SSR |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
23 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
RQST |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
HN |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
001 |
|
7 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
AA |
|
8 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
SDQ |
|
9 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
SJU |
|
10 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
01F |
|
11 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
PT |
|
12 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
5 |
|
13 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
ST |
|
14 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
5 |
2.11. ELEMENT: ACCOUNTING ELEMENTS
Accounting elements pertain to any elements stored in the PNR, which are specific to back office accounting system processing.
The information returned in the Powered PNR Reply structure is dependent upon the type of accounting element.
2.11.1. Specific Structural Elements
The following structural elements are specific to the itinerary elements when they are returned in the Powered PNR Reply Structure;
Each accounting element is qualified [I.e.,/travellerInfo
[2]/elementManagementPassenger/reference/Each accounting element has an associated line item number [I.e., /travellerInfo
[2]/elementManagementPassenger/lineNumber]. This line item number is an indication to the order in which the elements are stored within the Amadeus PNR. It is used to identify the specific element for any subsequent modifications or cancellations.Each accounting element has an associated reference item number [I.e., /travellerInfo
[1]/elementManagementPassenger/reference/number] This reference item number is an informational indication to the order in which the accounting elements were created within the Amadeus PNR.
2.11.2. Accounting Information Elements
Accounting information elements may be stored in a PNR for ticketing or back office accounting system usage.
The following parameters may be returned in an accounting information element:
|
Parameter |
Description |
|
Accounting information identifier |
AI |
|
Account number information |
Account Number |
|
Cost center information |
Cost center |
|
IATA company number |
IATA company number |
|
Client Reference number |
Client Reference number |
|
Segment association |
ST |
|
Associated Itinerary Element Reference number |
|
|
Passenger association |
PT |
|
Associated Passenger Reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an accounting information element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
Accounting Information reference number |
9 |
|
2 |
Accounting Information identifier |
AI |
|
3 |
Accounting Information line number |
29 |
|
4 |
Account Number |
74711925 |
|
5 |
Cost Center |
DV123 |
|
6 |
IATA Company Identifier |
DEC038FR |
|
7 |
Client Reference number |
123456789 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
OT |
|
1 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
9 |
|
2 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
AI |
|
3 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
29 |
|
4 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
74711925 |
|
5 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
DV123 |
|
6 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
DEC038FR |
|
7 |
/PoweredPNR_PNRReply/dataElementsMaster/ |
123456789 |
2.11.3. AIR Sequence Number Elements
The Amadeus system stores a unique accounting interface record (AIR) sequence number for each passenger in the PNR when a transitional stored ticket (TST) is created. The sequence numbers are returned in the AIR number element.
The following parameters will be returned for a ticket number for automated tickets element:
|
Parameter |
Description |
|
Ticket number for automated tickets element identifier |
FB |
|
Free form text identifier |
3 - literal text |
|
Type of free form text |
P07 - AIR sequence number |
|
Passenger type code |
Code identifying the passenger type on the ticket |
|
AIR sequence number |
10 digit number |
|
Ticket process identifier |
How the ticket was issued in the Amadeus system (I.e., TTP) |
|
Miscellaneous ticketing information |
Any information related to the ticketing process |
|
Segment association |
ST Associated itinerary element reference numbers |
|
Passenger association |
PT Associated passenger reference number |
The following is an extract of the POWERED PNR Reply structure to illustrate an AIR sequence number element as outlined below:
|
Item # |
Parameter |
Information |
|
1 |
AIR sequence number reference number |
12 |
|
2 |
AIR sequence number identifier |
FB |
|
3 |
AIR sequence number line number |
6 |
|
4 |
Free text identifier |
3 |
|
5 |
Type of free text |
P07 - AIR sequence number |
|
6 |
AIR sequence number information |
|
|
Passenger type code |
PAX |
|
|
AIR sequence number |
1500073984 |
|
|
Ticket process identifier |
TTP/XED1/PT/RT |
|
|
Miscellaneous ticketing information |
OKPROCESSED |
|
|
7-8 |
Passenger association |
Passenger reference number 1 |
|
9-10 |
Segment association |
Itinerary element reference number 1 |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
1 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
12 |
|
2 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
FB |
|
3 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
6 |
|
4 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
5 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/freetextDetail/type |
P07 |
|
6 |
/dataElementsMaster/dataElementsIndiv [4]/otherDataFreetext/longFreetext |
PAX1500073984TTP/XED1/PT/RTOKPROCESSED |
|
7 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[1]/qualifier |
PT |
|
8 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[1]/number |
1 |
|
9 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[2]/qualifier |
ST |
|
10 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[2]/number |
1 |
2.12. FULL POWERED PNR REPLY STRUCTURE - ACTIVE DATA
Below is an illustration of the contents returned in the Powered PNR Reply structure for a PNR containing the following information:
|
Item # in reply structure |
Type of Element |
Contents of Element |
|
0 - 14 |
PNR Header Elements |
Company ID, Record locator, Date and time stamp, Security information, Special PNR Header Remarks |
|
15 - 22 |
Name Element |
Complex name with passenger ID code |
|
23 - 30 |
Name Element |
Complex name with passenger type code |
|
31 - 40 |
Name Element |
Complex name with infant association |
|
41 - 47 |
Name Element |
Simple name |
|
48 - 56 |
Name Element |
Complex name with passenger type and ID Code combination |
|
57 - 81 |
Itinerary Element |
Automated Car reservation |
|
82 - 120 |
Itinerary Element |
Automated Hotel reservation |
|
121 - 143 |
Itinerary Element |
Flight element |
|
144 - 165 |
Itinerary Element |
Flight element |
|
166 - 187 |
Itinerary Element |
Flight element |
|
188 - 200 |
Itinerary Element |
Non-automated Air Taxi Service element |
|
201 - 218 |
Itinerary Element |
Non-automated Hotel element |
|
219 - 231 |
Itinerary Element |
Non-automated Miscellaneous element |
|
232 - 247 |
Itinerary Element |
Non-automated car element |
|
248 - 250 |
Itinerary Element |
Connecting flight element associations |
|
251 - 257 |
Informational Element |
Contact information |
|
258 - 264 |
Document Element |
Ticketing Arrangement |
|
265 - 280 |
Informational Element |
Special Service Request (Single Seat) |
|
281 - 308 |
Informational Element |
Special Service Request (Multiple Seats) |
|
309 - 344 |
Informational Element |
Special Service Request (Basic meal - multiple flight elements) |
|
345 - 355 |
Informational Element |
Special Service Request (Frequent Traveler) |
|
356 - 375 |
Informational Element |
Other Service Information (Multiple Passengers) |
|
376 - 382 |
Informational Element |
Confidential Option (Automatic Queue) |
|
383 - 389 |
Informational Element |
Confidential Option (Automatic Cancel) |
|
390 - 398 |
Accounting Element |
Accounting Information |
|
399 - 406 |
Informational Element |
Confidential Remark |
|
407 - 412 |
Informational Element |
General Remark |
|
413 - 421 |
Fare Element |
Form of Payment - Auxiliary |
|
422 - 432 |
Fare Element |
Fare Discount |
|
433 - 439 |
Fare Element |
Commission |
|
440 - 448 |
Fare Element |
Form of Payment - Cash |
|
449 - 457 |
Fare Element |
Form of Payment - Credit Card |
|
458 - 466 |
Fare Element |
Form of Payment - Check |
|
467 - 485 |
Informational Element |
Billing Address - Structured |
|
486 - 513 |
Informational Element |
Mailing Address - multiple non-structured |
|
514 - 520 |
Informational Element |
Individual PNR Security |
|
Item |
PoweredPNR_PNRReply - Data element |
Value |
|
0 |
/pnrHeader/reservationInfo/reservation/companyId |
1A |
|
1 |
/pnrHeader/reservationInfo/reservation/controlNumber |
X2Q59K |
|
2 |
/pnrHeader/reservationInfo/reservation/date |
160501 |
|
3 |
/pnrHeader/reservationInfo/reservation/time |
1001 |
|
4 |
/securityInformation/responsibilityInformation/ |
RP |
|
5 |
/securityInformation/responsibilityInformation/agentId |
DLRM |
|
6 |
/securityInformation/responsibilityInformation/officeId |
MUC1A0701 |
|
7 |
/securityInformation/queueingInformation/queueingOfficeId |
MUC1A0701 |
|
8 |
/securityInformation/cityCode |
DAP |
|
9 |
/securityInformation/secondRpInformation/creationOfficeId |
MUC1A0701 |
|
10 |
/securityInformation/secondRpInformation/agentSignature |
0001AA |
|
11 |
/securityInformation/secondRpInformation/creationDate |
160501 |
|
12 |
/freetextData/freetextDetail/subjectQualifier |
3 |
|
13 |
/freetextData/freetextDetail/type |
P12 |
|
14 |
/freetextData/longFreetext |
--- RLR --- |
|
15 |
/travellerInfo [1]/elementManagementPassenger/reference/qualifier |
PT |
|
16 |
/travellerInfo [1]/elementManagementPassenger/reference/number |
1 |
|
17 |
/travellerInfo [1]/elementManagementPassenger/segmentName |
NM |
|
18 |
/travellerInfo [1]/elementManagementPassenger/lineNumber |
1 |
|
19 |
/travellerInfo [1]/travellerInformation/traveller/surname |
CASEY |
|
20 |
/travellerInfo [1]/travellerInformation/traveller/quantity |
1 |
|
21 |
/travellerInfo [1]/travellerInformation/passenger/firstName |
BILL |
|
22 |
/travellerInfo [1]/travellerInformation/passenger/identificationCode |
ID251874 |
|
23 |
/travellerInfo [2]/elementManagementPassenger/reference/qualifier |
PT |
|
24 |
/travellerInfo [2]/elementManagementPassenger/reference/number |
2 |
|
25 |
/travellerInfo [2]/elementManagementPassenger/segmentName |
NM |
|
26 |
/travellerInfo [2]/elementManagementPassenger/lineNumber |
2 |
|
27 |
/travellerInfo [2]/travellerInformation/traveller/surname |
JONES |
|
28 |
/travellerInfo [2]/travellerInformation/traveller/quantity |
1 |
|
29 |
/travellerInfo [2]/travellerInformation/passenger/firstName |
JIM |
|
30 |
/travellerInfo [2]/travellerInformation/passenger/type |
CHD |
|
31 |
/travellerInfo [3]/elementManagementPassenger/reference/qualifier |
PT |
|
32 |
/travellerInfo [3]/elementManagementPassenger/reference/number |
3 |
|
33 |
/travellerInfo [3]/elementManagementPassenger/segmentName |
NM |
|
34 |
/travellerInfo [3]/elementManagementPassenger/lineNumber |
3 |
|
35 |
/travellerInfo [3]/travellerInformation/traveller/surname |
LEAVEY |
|
36 |
/travellerInfo [3]/travellerInformation/traveller/quantity |
2 |
|
37 |
/travellerInfo [3]/travellerInformation/passenger[1]/firstName |
KIM |
|
38 |
/travellerInfo [3]/travellerInformation/passenger[1]/infantIndicator |
1 |
|
39 |
/travellerInfo [3]/travellerInformation/passenger[2]/firstName |
MICHAEL |
|
40 |
/travellerInfo [3]/travellerInformation/passenger[2]/type |
INF |
|
41 |
/travellerInfo [4]/elementManagementPassenger/reference/qualifier |
PT |
|
42 |
/travellerInfo [4]/elementManagementPassenger/reference/number |
5 |
|
43 |
/travellerInfo [4]/elementManagementPassenger/segmentName |
NM |
|
44 |
/travellerInfo [4]/elementManagementPassenger/lineNumber |
4 |
|
45 |
/travellerInfo [4]/travellerInformation/traveller/surname |
SMITH |
|
46 |
/travellerInfo [4]/travellerInformation/traveller/quantity |
1 |
|
47 |
/travellerInfo [4]/travellerInformation/passenger/firstName |
JOHN |
|
48 |
/travellerInfo [5]/elementManagementPassenger/reference/qualifier |
PT |
|
49 |
/travellerInfo [5]/elementManagementPassenger/reference/number |
6 |
|
50 |
/travellerInfo [5]/elementManagementPassenger/segmentName |
NM |
|
51 |
/travellerInfo [5]/elementManagementPassenger/lineNumber |
5 |
|
52 |
/travellerInfo [5]/travellerInformation/traveller/surname |
SMITH |
|
53 |
/travellerInfo [5]/travellerInformation/traveller/quantity |
1 |
|
54 |
/travellerInfo [5]/travellerInformation/passenger/firstName |
KARIN |
|
55 |
/travellerInfo [5]/travellerInformation/passenger/type |
CHD |
|
56 |
/travellerInfo [5]/travellerInformation/passenger/identificationCode |
ID23784 |
|
57 |
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/reference/qualifier |
ST |
|
58 |
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/reference/number |
1 |
|
59 |
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/segmentName |
CCR |
|
60 |
/originDestinationDetails/itineraryInfo [1]/elementManagementItinerary/lineNumber |
6 |
|
61 |
/originDestinationDetails/itineraryInfo [1]/travelProduct/product/depDate |
220701 |
|
62 |
/originDestinationDetails/itineraryInfo [1]/travelProduct/product/arrDate |
250701 |
|
63 |
/originDestinationDetails/itineraryInfo [1]/travelProduct/boardpointDetail/cityCode |
NCE |
|
64 |
/originDestinationDetails/itineraryInfo [1]/travelProduct/companyDetail/identification |
AI |
|
65 |
/originDestinationDetails/itineraryInfo [1]/travelProduct/productDetails/identification |
EBMN |
|
66 |
/originDestinationDetails/itineraryInfo [1]/itineraryMessageAction/business/function |
2 |
|
67 |
/originDestinationDetails/itineraryInfo [1]/relatedProduct/quantity |
01 |
|
68 |
/originDestinationDetails/itineraryInfo [1]/relatedProduct/status |
HK |
|
69 |
/originDestinationDetails/itineraryInfo [1]/selectionDetails/selection/option |
P10 |
|
70 |
/originDestinationDetails/itineraryInfo [1]/generalOption[1]/optionDetail/type |
BS |
|
71 |
/originDestinationDetails/itineraryInfo [1]/generalOption[1]/optionDetail/freetext |
00000000 |
|
72 |
/originDestinationDetails/itineraryInfo [1]/generalOption[2]/optionDetail/type |
ARR |
|
73 |
/originDestinationDetails/itineraryInfo [1]/generalOption[2]/optionDetail/freetext |
0800 |
|
74 |
/originDestinationDetails/itineraryInfo [1]/generalOption[3]/optionDetail/type |
RC |
|
75 |
/originDestinationDetails/itineraryInfo [1]/generalOption[3]/optionDetail/freetext |
SD-BASIC |
|
76 |
/originDestinationDetails/itineraryInfo [1]/generalOption[4]/optionDetail/type |
RG |
|
77 |
/originDestinationDetails/itineraryInfo [1]/generalOption[4]/optionDetail/freetext |
FRF 179.00- .00 UNL DY |
|
78 |
/originDestinationDetails/itineraryInfo [1]/generalOption[5]/optionDetail/type |
RT |
|
79 |
/originDestinationDetails/itineraryInfo [1]/generalOption[5]/optionDetail/freetext |
1600 |
|
80 |
/originDestinationDetails/itineraryInfo [1]/referenceForSegment/reference/qualifier |
PT |
|
81 |
/originDestinationDetails/itineraryInfo [1]/referenceForSegment/reference/number |
1 |
|
82 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/qualifier |
ST |
|
83 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/reference/number |
2 |
|
84 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/segmentName |
HHL |
|
85 |
/originDestinationDetails/itineraryInfo [2]/elementManagementItinerary/lineNumber |
7 |
|
86 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/depDate |
220701 |
|
87 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/product/arrDate |
250701 |
|
88 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/boardpointDetail/cityCode |
NCE |
|
89 |
/originDestinationDetails/itineraryInfo [2]/travelProduct/companyDetail/identification |
RB |
|
90 |
/originDestinationDetails/itineraryInfo [2]/itineraryMessageAction/business/function |
3 |
|
91 |
/originDestinationDetails/itineraryInfo [2]/relatedProduct/quantity |
01 |
|
92 |
/originDestinationDetails/itineraryInfo [2]/relatedProduct/status |
HK |
|
93 |
/originDestinationDetails/itineraryInfo [2]/selectionDetails/selection/option |
P10 |
|
94 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/providerName |
RESORT BOOKINGS |
|
95 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/code |
326 |
|
96 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/property/name |
CITADINES AV DES FLEURS APARTHOTEL |
|
97 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/occupancy |
1 |
|
98 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/hotelRoom/typeCode |
T** |
|
99 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/negotiated/rateCode |
RAC |
|
100 |
/originDestinationDetails/itineraryInfo [2]/hotelProduct/otherHotelInfo/currencyCode |
EUR |
|
101 |
/originDestinationDetails/itineraryInfo [2]/rateInformations/ratePrice/rateAmount |
80.00 |
|
102 |
/originDestinationDetails/itineraryInfo [2]/rateInformations/rateInfo/ratePlan |
DY |
|
103 |
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/type |
DP |
|
104 |
/originDestinationDetails/itineraryInfo [2]/generalOption[1]/optionDetail/freetext |
CCVI4974830544671492EXP0901 |
|
105 |
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/type |
TTL |
|
106 |
/originDestinationDetails/itineraryInfo [2]/generalOption[2]/optionDetail/freetext |
EUR240.00 |
|
107 |
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/type |
NGT |
|
108 |
/originDestinationDetails/itineraryInfo [2]/generalOption[3]/optionDetail/freetext |
03 |
|
109 |
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/type |
NAM |
|
110 |
/originDestinationDetails/itineraryInfo [2]/generalOption[4]/optionDetail/freetext |
CITADINES AV DES FLEURS APARTHOTEL |
|
111 |
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/type |
BS |
|
112 |
/originDestinationDetails/itineraryInfo [2]/generalOption[5]/optionDetail/freetext |
01234567 |
|
113 |
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/type |
CF |
|
114 |
/originDestinationDetails/itineraryInfo [2]/generalOption[6]/optionDetail/freetext |
............ |
|
115 |
/originDestinationDetails/itineraryInfo [2]/generalOption[7]/optionDetail/type |
CNM |
|
116 |
/originDestinationDetails/itineraryInfo [2]/generalOption[7]/optionDetail/freetext |
RESORT BOOKINGS |
|
117 |
/originDestinationDetails/itineraryInfo [2]/generalOption[8]/optionDetail/type |
PRI |
|
118 |
/originDestinationDetails/itineraryInfo [2]/generalOption[8]/optionDetail/freetext |
22JUL 80.0003 |
|
119 |
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/qualifier |
PT |
|
120 |
/originDestinationDetails/itineraryInfo [2]/referenceForSegment/reference/number |
1 |
|
121 |
/originDestinationDetails/itineraryInfo [3]/elementManagementItinerary/reference/qualifier |
ST |
|
122 |
/originDestinationDetails/itineraryInfo [3]/elementManagementItinerary/reference/number |
3 |
|
123 |
/originDestinationDetails/itineraryInfo [3]/elementManagementItinerary/segmentName |
AIR |
|
124 |
/originDestinationDetails/itineraryInfo [3]/elementManagementItinerary/lineNumber |
8 |
|
125 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/product/depDate |
250701 |
|
126 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/product/depTime |
1315 |
|
127 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/product/arrDate |
250701 |
|
128 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/product/arrTime |
1450 |
|
129 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/boardpointDetail/cityCode |
NCE |
|
130 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/offpointDetail/cityCode |
CDG |
|
131 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/companyDetail/identification |
AF |
|
132 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/productDetails/identification |
7703 |
|
133 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/productDetails/classOfService |
C |
|
134 |
/originDestinationDetails/itineraryInfo [3]/travelProduct/typeDetail/detail |
ET |
|
135 |
/originDestinationDetails/itineraryInfo [3]/itineraryMessageAction/business/function |
1 |
|
136 |
/originDestinationDetails/itineraryInfo [3]/itineraryReservationInfo/reservation/companyId |
AF |
|
137 |
/originDestinationDetails/itineraryInfo [3]/itineraryReservationInfo/reservation/controlNumber |
24RWLR |
|
138 |
/originDestinationDetails/itineraryInfo [3]/relatedProduct/quantity |
5 |
|
139 |
/originDestinationDetails/itineraryInfo [3]/relatedProduct/status |
HK |
|
140 |
/originDestinationDetails/itineraryInfo [3]/flightDetail/productDetails/weekDay |
3 |
|
141 |
/originDestinationDetails/itineraryInfo [3]/flightDetail/departureInformation/departTerminal |
2 |
|
142 |
/originDestinationDetails/itineraryInfo [3]/flightDetail/timeDetail/checkinTime |
1255 |
|
143 |
/originDestinationDetails/itineraryInfo [3]/selectionDetails/selection/option |
P2 |
|
144 |
/originDestinationDetails/itineraryInfo [4]/elementManagementItinerary/reference/qualifier |
ST |
|
145 |
/originDestinationDetails/itineraryInfo [4]/elementManagementItinerary/reference/number |
4 |
|
146 |
/originDestinationDetails/itineraryInfo [4]/elementManagementItinerary/segmentName |
AIR |
|
147 |
/originDestinationDetails/itineraryInfo [4]/elementManagementItinerary/lineNumber |
9 |
|
148 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/product/depDate |
250701 |
|
149 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/product/depTime |
1600 |
|
150 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/product/arrDate |
250701 |
|
151 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/product/arrTime |
1805 |
|
152 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/boardpointDetail/cityCode |
CDG |
|
153 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/offpointDetail/cityCode |
ORD |
|
154 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/companyDetail/identification |
AF |
|
155 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/productDetails/identification |
54 |
|
156 |
/originDestinationDetails/itineraryInfo [4]/travelProduct/productDetails/classOfService |
C |
|
157 |
/originDestinationDetails/itineraryInfo [4]/itineraryMessageAction/business/function |
1 |
|
158 |
/originDestinationDetails/itineraryInfo [4]/itineraryReservationInfo/reservation/companyId |
AF |
|
159 |
/originDestinationDetails/itineraryInfo [4]/itineraryReservationInfo/reservation/controlNumber |
24RWLR |
|
160 |
/originDestinationDetails/itineraryInfo [4]/relatedProduct/quantity |
5 |
|
161 |
/originDestinationDetails/itineraryInfo [4]/relatedProduct/status |
HK |
|
162 |
/originDestinationDetails/itineraryInfo [4]/flightDetail/productDetails/weekDay |
3 |
|
163 |
/originDestinationDetails/itineraryInfo [4]/flightDetail/departureInformation/departTerminal |
2F |
|
164 |
/originDestinationDetails/itineraryInfo [4]/flightDetail/timeDetail/checkinTime |
1515 |
|
165 |
/originDestinationDetails/itineraryInfo [4]/selectionDetails/selection/option |
P2 |
|
166 |
/originDestinationDetails/itineraryInfo [5]/elementManagementItinerary/reference/qualifier |
ST |
|
167 |
/originDestinationDetails/itineraryInfo [5]/elementManagementItinerary/reference/number |
5 |
|
168 |
/originDestinationDetails/itineraryInfo [5]/elementManagementItinerary/segmentName |
AIR |
|
169 |
/originDestinationDetails/itineraryInfo [5]/elementManagementItinerary/lineNumber |
10 |
|
170 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/product/depDate |
280701 |
|
171 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/product/depTime |
0610 |
|
172 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/product/arrDate |
280701 |
|
173 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/product/arrTime |
0915 |
|
174 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/boardpointDetail/cityCode |
ORD |
|
175 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/offpointDetail/cityCode |
ATL |
|
176 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/companyDetail/identification |
DL |
|
177 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/productDetails/identification |
1245 |
|
178 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/productDetails/classOfService |
Y |
|
179 |
/originDestinationDetails/itineraryInfo [5]/travelProduct/typeDetail/detail |
ET |
|
180 |
/originDestinationDetails/itineraryInfo [5]/itineraryMessageAction/business/function |
1 |
|
181 |
/originDestinationDetails/itineraryInfo [5]/itineraryReservationInfo/reservation/companyId |
DL |
|
182 |
/originDestinationDetails/itineraryInfo [5]/itineraryReservationInfo/reservation/controlNumber |
DHRKRF |
|
183 |
/originDestinationDetails/itineraryInfo [5]/relatedProduct/quantity |
5 |
|
184 |
/originDestinationDetails/itineraryInfo [5]/relatedProduct/status |
HK |
|
185 |
/originDestinationDetails/itineraryInfo [5]/flightDetail/productDetails/weekDay |
6 |
|
186 |
/originDestinationDetails/itineraryInfo [5]/flightDetail/departureInformation/departTerminal |
3 |
|
187 |
/originDestinationDetails/itineraryInfo [5]/selectionDetails/selection/option |
P2 |
|
188 |
/originDestinationDetails/itineraryInfo [6]/elementManagementItinerary/reference/qualifier |
ST |
|
189 |
/originDestinationDetails/itineraryInfo [6]/elementManagementItinerary/reference/number |
6 |
|
190 |
/originDestinationDetails/itineraryInfo [6]/elementManagementItinerary/segmentName |
AU |
|
191 |
/originDestinationDetails/itineraryInfo [6]/elementManagementItinerary/lineNumber |
11 |
|
192 |
/originDestinationDetails/itineraryInfo [6]/travelProduct/product/depDate |
280701 |
|
193 |
/originDestinationDetails/itineraryInfo [6]/travelProduct/boardpointDetail/cityCode |
ATL |
|
194 |
/originDestinationDetails/itineraryInfo [6]/travelProduct/offpointDetail/cityCode |
MEM |
|
195 |
/originDestinationDetails/itineraryInfo [6]/travelProduct/companyDetail/identification |
AF |
|
196 |
/originDestinationDetails/itineraryInfo [6]/itineraryMessageAction/business/function |
10 |
|
197 |
/originDestinationDetails/itineraryInfo [6]/relatedProduct/quantity |
5 |
|
198 |
/originDestinationDetails/itineraryInfo [6]/relatedProduct/status |
HN |
|
199 |
/originDestinationDetails/itineraryInfo [6]/itineraryFreetext/freetextDetail/subjectQualifier |
3 |
|
200 |
/originDestinationDetails/itineraryInfo [6]/itineraryFreetext/longFreetext |
JET SERVICE TO MEMPHIS |
|
201 |
/originDestinationDetails/itineraryInfo [7]/elementManagementItinerary/reference/qualifier |
ST |
|
202 |
/originDestinationDetails/itineraryInfo [7]/elementManagementItinerary/reference/number |
8 |
|
203 |
/originDestinationDetails/itineraryInfo [7]/elementManagementItinerary/segmentName |
HU |
|
204 |
/originDestinationDetails/itineraryInfo [7]/elementManagementItinerary/lineNumber |
12 |
|
205 |
/originDestinationDetails/itineraryInfo [7]/travelProduct/product/depDate |
280701 |
|
206 |
/originDestinationDetails/itineraryInfo [7]/travelProduct/product/arrDate |
030801 |
|
207 |
/originDestinationDetails/itineraryInfo [7]/travelProduct/boardpointDetail/cityCode |
MEM |
|
208 |
/originDestinationDetails/itineraryInfo [7]/travelProduct/companyDetail/identification |
AF |
|
209 |
/originDestinationDetails/itineraryInfo [7]/itineraryMessageAction/business/function |
8 |
|
210 |
/originDestinationDetails/itineraryInfo [7]/relatedProduct/quantity |
2 |
|
211 |
/originDestinationDetails/itineraryInfo [7]/relatedProduct/status |
HN |
|
212 |
/originDestinationDetails/itineraryInfo [7]/itineraryFreetext/freetextDetail/subjectQualifier |
3 |
|
213 |
/originDestinationDetails/itineraryInfo [7]/itineraryFreetext/longFreetext |
BOBS BED AND BREAKFAST ON 21 ELM STR |
|
214 |
/originDestinationDetails/itineraryInfo [7]/referenceForSegment/reference[1]/qualifier |
PT |
|
215 |
/originDestinationDetails/itineraryInfo [7]/referenceForSegment/reference[1]/number |
1 |
|
216 |
/originDestinationDetails/itineraryInfo [7]/referenceForSegment/reference[2]/qualifier |
PT |
|
217 |
/originDestinationDetails/itineraryInfo [7]/referenceForSegment/reference[2]/number |
3 |
|
218 |
/originDestinationDetails/itineraryInfo [8]/elementManagementItinerary/reference/qualifier |
ST |
|
219 |
/originDestinationDetails/itineraryInfo [8]/elementManagementItinerary/reference/number |
9 |
|
220 |
/originDestinationDetails/itineraryInfo [8]/elementManagementItinerary/segmentName |
RU |
|
221 |
/originDestinationDetails/itineraryInfo [8]/elementManagementItinerary/lineNumber |
13 |
|
222 |
/originDestinationDetails/itineraryInfo [8]/travelProduct/product/depDate |
280701 |
|
223 |
/originDestinationDetails/itineraryInfo [8]/travelProduct/boardpointDetail/cityCode |
MEM |
|
224 |
/originDestinationDetails/itineraryInfo [8]/travelProduct/companyDetail/identification |
1A |
|
225 |
/originDestinationDetails/itineraryInfo [8]/itineraryMessageAction/business/function |
32 |
|
226 |
/originDestinationDetails/itineraryInfo [8]/relatedProduct/quantity |
1 |
|
227 |
/originDestinationDetails/itineraryInfo [8]/relatedProduct/status |
HK |
|
228 |
/originDestinationDetails/itineraryInfo [8]/itineraryFreetext/freetextDetail/subjectQualifier |
3 |
|
229 |
/originDestinationDetails/itineraryInfo [8]/itineraryFreetext/longFreetext |
JET SERVICE PREPAID |
|
230 |
/originDestinationDetails/itineraryInfo [8]/referenceForSegment/reference/qualifier |
PT |
|
231 |
/originDestinationDetails/itineraryInfo [8]/referenceForSegment/reference/number |
1 |
|
232 |
/originDestinationDetails/itineraryInfo [9]/elementManagementItinerary/reference/qualifier |
ST |
|
233 |
/originDestinationDetails/itineraryInfo [9]/elementManagementItinerary/reference/number |
7 |
|
234 |
/originDestinationDetails/itineraryInfo [9]/elementManagementItinerary/segmentName |
CU |
|
235 |
/originDestinationDetails/itineraryInfo [9]/elementManagementItinerary/lineNumber |
14 |
|
236 |
/originDestinationDetails/itineraryInfo [9]/travelProduct/product/depDate |
300701 |
|
237 |
/originDestinationDetails/itineraryInfo [9]/travelProduct/product/arrDate |
030801 |
|
238 |
/originDestinationDetails/itineraryInfo [9]/travelProduct/boardpointDetail/cityCode |
MEM |
|
239 |
/originDestinationDetails/itineraryInfo [9]/travelProduct/companyDetail/identification |
AF |
|
240 |
/originDestinationDetails/itineraryInfo [9]/travelProduct/productDetails/identification |
ECAR |
|
241 |
/originDestinationDetails/itineraryInfo [9]/itineraryMessageAction/business/function |
9 |
|
242 |
/originDestinationDetails/itineraryInfo [9]/relatedProduct/quantity |
1 |
|
243 |
/originDestinationDetails/itineraryInfo [9]/relatedProduct/status |
HN |
|
244 |
/originDestinationDetails/itineraryInfo [9]/itineraryFreetext/freetextDetail/subjectQualifier |
3 |
|
245 |
/originDestinationDetails/itineraryInfo [9]/itineraryFreetext/longFreetext |
PICK UP CAR AT HERTZ SITE |
|
246 |
/originDestinationDetails/itineraryInfo [9]/referenceForSegment/reference/qualifier |
PT |
|
247 |
/originDestinationDetails/itineraryInfo [9]/referenceForSegment/reference/number |
1 |
|
248 |
/segmentGroupingInfo/groupingCode |
CNX |
|
249 |
/segmentGroupingInfo/marriageDetail [1]/tatooNum |
3 |
|
250 |
/segmentGroupingInfo/marriageDetail [2]/tatooNum |
4 |
|
251 |
/dataElementsMaster/dataElementsIndiv [1]/elementManagementData/reference/qualifier |
OT |
|
252 |
/dataElementsMaster/dataElementsIndiv [1]/elementManagementData/reference/number |
18 |
|
253 |
/dataElementsMaster/dataElementsIndiv [1]/elementManagementData/segmentName |
AP |
|
254 |
/dataElementsMaster/dataElementsIndiv [1]/elementManagementData/lineNumber |
15 |
|
255 |
/dataElementsMaster/dataElementsIndiv [1]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
256 |
/dataElementsMaster/dataElementsIndiv [1]/otherDataFreetext/freetextDetail/type |
3 |
|
257 |
/dataElementsMaster/dataElementsIndiv [1]/otherDataFreetext/longFreetext |
NCE0492947900-B |
|
258 |
/dataElementsMaster/dataElementsIndiv [2]/elementManagementData/reference/qualifier |
OT |
|
259 |
/dataElementsMaster/dataElementsIndiv [2]/elementManagementData/reference/number |
11 |
|
260 |
/dataElementsMaster/dataElementsIndiv [2]/elementManagementData/segmentName |
TK |
|
261 |
/dataElementsMaster/dataElementsIndiv [2]/elementManagementData/lineNumber |
16 |
|
262 |
/dataElementsMaster/dataElementsIndiv [2]/ticketElement/ticket/indicator |
OK |
|
263 |
/dataElementsMaster/dataElementsIndiv [2]/ticketElement/ticket/date |
160501 |
|
264 |
/dataElementsMaster/dataElementsIndiv [2]/ticketElement/ticket/officeId |
MUC1A0701 |
|
265 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/qualifier |
OT |
|
266 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/reference/number |
38 |
|
267 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/segmentName |
SSR |
|
268 |
/dataElementsMaster/dataElementsIndiv [3]/elementManagementData/lineNumber |
17 |
|
269 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/type |
RQST |
|
270 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/status |
UC |
|
271 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/quantity |
001 |
|
272 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/companyId |
AF |
|
273 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/boardpoint |
NCE |
|
274 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssr/offpoint |
CDG |
|
275 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssrb/data |
12C |
|
276 |
/dataElementsMaster/dataElementsIndiv [3]/serviceRequest/ssrb/seatType |
N |
|
277 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/qualifier |
PT |
|
278 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[1]/number |
1 |
|
279 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/qualifier |
ST |
|
280 |
/dataElementsMaster/dataElementsIndiv [3]/referenceForDataElement/reference[2]/number |
3 |
|
281 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/qualifier |
OT |
|
282 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/reference/number |
39 |
|
283 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/segmentName |
SSR |
|
284 |
/dataElementsMaster/dataElementsIndiv [4]/elementManagementData/lineNumber |
18 |
|
285 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/type |
NSST |
|
286 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/status |
KK |
|
287 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/quantity |
004 |
|
288 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/companyId |
AF |
|
289 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/boardpoint |
NCE |
|
290 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssr/offpoint |
CDG |
|
291 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[1]/data |
05A |
|
292 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[1]/seatType |
N |
|
293 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[2]/data |
05C |
|
294 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[2]/seatType |
N |
|
295 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[3]/data |
05D |
|
296 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[3]/seatType |
N |
|
297 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[4]/data |
05F |
|
298 |
/dataElementsMaster/dataElementsIndiv [4]/serviceRequest/ssrb[4]/seatType |
N |
|
299 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[1]/qualifier |
PT |
|
300 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[1]/number |
2 |
|
301 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[2]/qualifier |
PT |
|
302 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[2]/number |
3 |
|
303 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[3]/qualifier |
PT |
|
304 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[3]/number |
5 |
|
305 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[4]/qualifier |
PT |
|
306 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[4]/number |
6 |
|
307 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[5]/qualifier |
ST |
|
308 |
/dataElementsMaster/dataElementsIndiv [4]/referenceForDataElement/reference[5]/number |
3 |
|
309 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/qualifier |
OT |
|
310 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/reference/number |
21 |
|
311 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/segmentName |
SSR |
|
312 |
/dataElementsMaster/dataElementsIndiv [5]/elementManagementData/lineNumber |
19 |
|
313 |
/dataElementsMaster/dataElementsIndiv [5]/serviceRequest/ssr/type |
VGML |
|
314 |
/dataElementsMaster/dataElementsIndiv [5]/serviceRequest/ssr/status |
KK |
|
315 |
/dataElementsMaster/dataElementsIndiv [5]/serviceRequest/ssr/quantity |
001 |
|
316 |
/dataElementsMaster/dataElementsIndiv [5]/serviceRequest/ssr/companyId |
AF |
|
317 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[1]/qualifier |
PT |
|
318 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[1]/number |
3 |
|
319 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[2]/qualifier |
ST |
|
320 |
/dataElementsMaster/dataElementsIndiv [5]/referenceForDataElement/reference[2]/number |
3 |
|
321 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/reference/qualifier |
OT |
|
322 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/reference/number |
22 |
|
323 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/segmentName |
SSR |
|
324 |
/dataElementsMaster/dataElementsIndiv [6]/elementManagementData/lineNumber |
20 |
|
325 |
/dataElementsMaster/dataElementsIndiv [6]/serviceRequest/ssr/type |
VGML |
|
326 |
/dataElementsMaster/dataElementsIndiv [6]/serviceRequest/ssr/status |
KK |
|
327 |
/dataElementsMaster/dataElementsIndiv [6]/serviceRequest/ssr/quantity |
001 |
|
328 |
/dataElementsMaster/dataElementsIndiv [6]/serviceRequest/ssr/companyId |
AF |
|
329 |
/dataElementsMaster/dataElementsIndiv [6]/referenceForDataElement/reference[1]/qualifier |
PT |
|
330 |
/dataElementsMaster/dataElementsIndiv [6]/referenceForDataElement/reference[1]/number |
3 |
|
331 |
/dataElementsMaster/dataElementsIndiv [6]/referenceForDataElement/reference[2]/qualifier |
ST |
|
332 |
/dataElementsMaster/dataElementsIndiv [6]/referenceForDataElement/reference[2]/number |
4 |
|
333 |
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/reference/qualifier |
OT |
|
334 |
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/reference/number |
23 |
|
335 |
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/segmentName |
SSR |
|
336 |
/dataElementsMaster/dataElementsIndiv [7]/elementManagementData/lineNumber |
21 |
|
337 |
/dataElementsMaster/dataElementsIndiv [7]/serviceRequest/ssr/type |
VGML |
|
338 |
/dataElementsMaster/dataElementsIndiv [7]/serviceRequest/ssr/status |
KK |
|
339 |
/dataElementsMaster/dataElementsIndiv [7]/serviceRequest/ssr/quantity |
001 |
|
340 |
/dataElementsMaster/dataElementsIndiv [7]/serviceRequest/ssr/companyId |
DL |
|
341 |
/dataElementsMaster/dataElementsIndiv [7]/referenceForDataElement/reference[1]/qualifier |
PT |
|
342 |
/dataElementsMaster/dataElementsIndiv [7]/referenceForDataElement/reference[1]/number |
3 |
|
343 |
/dataElementsMaster/dataElementsIndiv [7]/referenceForDataElement/reference[2]/qualifier |
ST |
|
344 |
/dataElementsMaster/dataElementsIndiv [7]/referenceForDataElement/reference[2]/number |
5 |
|
345 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/reference/qualifier |
OT |
|
346 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/reference/number |
24 |
|
347 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/segmentName |
SSR |
|
348 |
/dataElementsMaster/dataElementsIndiv [8]/elementManagementData/lineNumber |
22 |
|
349 |
/dataElementsMaster/dataElementsIndiv [8]/serviceRequest/ssr/type |
FQTV |
|
350 |
/dataElementsMaster/dataElementsIndiv [8]/serviceRequest/ssr/status |
HK |
|
351 |
/dataElementsMaster/dataElementsIndiv [8]/serviceRequest/ssr/companyId |
AF |
|
352 |
/dataElementsMaster/dataElementsIndiv [8]/frequentTravellerInfo/frequentTraveller/company |
AF |
|
353 |
/dataElementsMaster/dataElementsIndiv [8]/frequentTravellerInfo/frequentTraveller/membershipNumber |
1222074194 |
|
354 |
/dataElementsMaster/dataElementsIndiv [8]/referenceForDataElement/reference/qualifier |
PT |
|
355 |
/dataElementsMaster/dataElementsIndiv [8]/referenceForDataElement/reference/number |
5 |
|
356 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/reference/qualifier |
OT |
|
357 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/reference/number |
4 |
|
358 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/segmentName |
OS |
|
359 |
/dataElementsMaster/dataElementsIndiv [9]/elementManagementData/lineNumber |
23 |
|
360 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
361 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/freetextDetail/type |
28 |
|
362 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/freetextDetail/companyId |
YY |
|
363 |
/dataElementsMaster/dataElementsIndiv [9]/otherDataFreetext/longFreetext |
1CHD |
|
364 |
/dataElementsMaster/dataElementsIndiv [9]/referenceForDataElement/reference/qualifier |
PT |
|
365 |
/dataElementsMaster/dataElementsIndiv [9]/referenceForDataElement/reference/number |
2 |
|
366 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/reference/qualifier |
OT |
|
367 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/reference/number |
5 |
|
368 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/segmentName |
OS |
|
369 |
/dataElementsMaster/dataElementsIndiv [10]/elementManagementData/lineNumber |
24 |
|
370 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
371 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/freetextDetail/type |
28 |
|
372 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/freetextDetail/companyId |
YY |
|
373 |
/dataElementsMaster/dataElementsIndiv [10]/otherDataFreetext/longFreetext |
1CHD |
|
374 |
/dataElementsMaster/dataElementsIndiv [10]/referenceForDataElement/reference/qualifier |
PT |
|
375 |
/dataElementsMaster/dataElementsIndiv [10]/referenceForDataElement/reference/number |
6 |
|
376 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/qualifier |
OT |
|
377 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/reference/number |
36 |
|
378 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/segmentName |
OP |
|
379 |
/dataElementsMaster/dataElementsIndiv [11]/elementManagementData/lineNumber |
25 |
|
380 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
381 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/freetextDetail/type |
P21 |
|
382 |
/dataElementsMaster/dataElementsIndiv [11]/otherDataFreetext/longFreetext |
MUC1A0701/20JUL/ISSUE TICKETS |
|
383 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/reference/qualifier |
OT |
|
384 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/reference/number |
37 |
|
385 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/segmentName |
OP |
|
386 |
/dataElementsMaster/dataElementsIndiv [12]/elementManagementData/lineNumber |
26 |
|
387 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
388 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/freetextDetail/type |
P21 |
|
389 |
/dataElementsMaster/dataElementsIndiv [12]/otherDataFreetext/longFreetext |
MUC1A0701/16MAY/X/MIA1S1101/25JUL |
|
390 |
/dataElementsMaster/dataElementsIndiv [13]/elementManagementData/reference/qualifier |
OT |
|
391 |
/dataElementsMaster/dataElementsIndiv [13]/elementManagementData/reference/number |
20 |
|
392 |
/dataElementsMaster/dataElementsIndiv [13]/elementManagementData/segmentName |
AI |
|
393 |
/dataElementsMaster/dataElementsIndiv [13]/elementManagementData/lineNumber |
27 |
|
394 |
/dataElementsMaster/dataElementsIndiv [13]/accounting/account/number |
DEC001029 |
|
395 |
/dataElementsMaster/dataElementsIndiv [13]/accounting/account/costNumber |
DV123 |
|
396 |
/dataElementsMaster/dataElementsIndiv [13]/accounting/account/companyNumber |
DEC038FR |
|
397 |
/dataElementsMaster/dataElementsIndiv [13]/referenceForDataElement/reference/qualifier |
PT |
|
398 |
/dataElementsMaster/dataElementsIndiv [13]/referenceForDataElement/reference/number |
5 |
|
399 |
/dataElementsMaster/dataElementsIndiv [14]/elementManagementData/reference/qualifier |
OT |
|
400 |
/dataElementsMaster/dataElementsIndiv [14]/elementManagementData/reference/number |
25 |
|
401 |
/dataElementsMaster/dataElementsIndiv [14]/elementManagementData/segmentName |
RC |
|
402 |
/dataElementsMaster/dataElementsIndiv [14]/elementManagementData/lineNumber |
28 |
|
403 |
/dataElementsMaster/dataElementsIndiv [14]/miscellaneousRemarks/remarks/type |
RC |
|
404 |
/dataElementsMaster/dataElementsIndiv [14]/miscellaneousRemarks/remarks/freetext |
HANDLE WITH CARE VIP CLIENTS |
|
405 |
/dataElementsMaster/dataElementsIndiv [14]/miscellaneousRemarks/remarks/officeId[1] |
MUC1A0701 |
|
406 |
/dataElementsMaster/dataElementsIndiv [14]/miscellaneousRemarks/remarks/officeId[2] |
MIA1S1101 |
|
407 |
/dataElementsMaster/dataElementsIndiv [15]/elementManagementData/reference/qualifier |
OT |
|
408 |
/dataElementsMaster/dataElementsIndiv [15]/elementManagementData/reference/number |
26 |
|
409 |
/dataElementsMaster/dataElementsIndiv [15]/elementManagementData/segmentName |
RM |
|
410 |
/dataElementsMaster/dataElementsIndiv [15]/elementManagementData/lineNumber |
29 |
|
411 |
/dataElementsMaster/dataElementsIndiv [15]/miscellaneousRemarks/remarks/type |
RM |
|
412 |
/dataElementsMaster/dataElementsIndiv [15]/miscellaneousRemarks/remarks/freetext |
REMEMBER TO OFFER VOUCHER FOR NEXT TRIP |
|
413 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/reference/qualifier |
OT |
|
414 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/reference/number |
8 |
|
415 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/segmentName |
RI |
|
416 |
/dataElementsMaster/dataElementsIndiv [16]/elementManagementData/lineNumber |
30 |
|
417 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/type |
RI |
|
418 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/category |
U |
|
419 |
/dataElementsMaster/dataElementsIndiv [16]/miscellaneousRemarks/remarks/freetext |
CHECK |
|
420 |
/dataElementsMaster/dataElementsIndiv [16]/referenceForDataElement/reference/qualifier |
PT |
|
421 |
/dataElementsMaster/dataElementsIndiv [16]/referenceForDataElement/reference/number |
1 |
|
422 |
/dataElementsMaster/dataElementsIndiv [17]/elementManagementData/reference/qualifier |
OT |
|
423 |
/dataElementsMaster/dataElementsIndiv [17]/elementManagementData/reference/number |
12 |
|
424 |
/dataElementsMaster/dataElementsIndiv [17]/elementManagementData/segmentName |
FD |
|
425 |
/dataElementsMaster/dataElementsIndiv [17]/elementManagementData/lineNumber |
31 |
|
426 |
/dataElementsMaster/dataElementsIndiv [17]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
427 |
/dataElementsMaster/dataElementsIndiv [17]/otherDataFreetext/freetextDetail/type |
P04 |
|
428 |
/dataElementsMaster/dataElementsIndiv [17]/otherDataFreetext/longFreetext |
PAX CD |
|
429 |
/dataElementsMaster/dataElementsIndiv [17]/referenceForDataElement/reference[1]/qualifier |
PT |
|
430 |
/dataElementsMaster/dataElementsIndiv [17]/referenceForDataElement/reference[1]/number |
2 |
|
431 |
/dataElementsMaster/dataElementsIndiv [17]/referenceForDataElement/reference[2]/qualifier |
PT |
|
432 |
/dataElementsMaster/dataElementsIndiv [17]/referenceForDataElement/reference[2]/number |
6 |
|
433 |
/dataElementsMaster/dataElementsIndiv [18]/elementManagementData/reference/qualifier |
OT |
|
434 |
/dataElementsMaster/dataElementsIndiv [18]/elementManagementData/reference/number |
9 |
|
435 |
/dataElementsMaster/dataElementsIndiv [18]/elementManagementData/segmentName |
FM |
|
436 |
/dataElementsMaster/dataElementsIndiv [18]/elementManagementData/lineNumber |
32 |
|
437 |
/dataElementsMaster/dataElementsIndiv [18]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
438 |
/dataElementsMaster/dataElementsIndiv [18]/otherDataFreetext/freetextDetail/type |
11 |
|
439 |
/dataElementsMaster/dataElementsIndiv [18]/otherDataFreetext/longFreetext |
9 |
|
440 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/reference/qualifier |
OT |
|
441 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/reference/number |
10 |
|
442 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/segmentName |
FP |
|
443 |
/dataElementsMaster/dataElementsIndiv [19]/elementManagementData/lineNumber |
33 |
|
444 |
/dataElementsMaster/dataElementsIndiv [19]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
445 |
/dataElementsMaster/dataElementsIndiv [19]/otherDataFreetext/freetextDetail/type |
16 |
|
446 |
/dataElementsMaster/dataElementsIndiv [19]/otherDataFreetext/longFreetext |
CASH |
|
447 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference/qualifier |
PT |
|
448 |
/dataElementsMaster/dataElementsIndiv [19]/referenceForDataElement/reference/number |
1 |
|
449 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/reference/qualifier |
OT |
|
450 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/reference/number |
27 |
|
451 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/segmentName |
FP |
|
452 |
/dataElementsMaster/dataElementsIndiv [20]/elementManagementData/lineNumber |
34 |
|
453 |
/dataElementsMaster/dataElementsIndiv [20]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
454 |
/dataElementsMaster/dataElementsIndiv [20]/otherDataFreetext/freetextDetail/type |
16 |
|
455 |
/dataElementsMaster/dataElementsIndiv [20]/otherDataFreetext/longFreetext |
CCVI4974830544671492/0801/FRF15000 |
|
456 |
/dataElementsMaster/dataElementsIndiv [20]/referenceForDataElement/reference/qualifier |
PT |
|
457 |
/dataElementsMaster/dataElementsIndiv [20]/referenceForDataElement/reference/number |
3 |
|
458 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/reference/qualifier |
OT |
|
459 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/reference/number |
28 |
|
460 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/segmentName |
FP |
|
461 |
/dataElementsMaster/dataElementsIndiv [21]/elementManagementData/lineNumber |
35 |
|
462 |
/dataElementsMaster/dataElementsIndiv [21]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
463 |
/dataElementsMaster/dataElementsIndiv [21]/otherDataFreetext/freetextDetail/type |
16 |
|
464 |
/dataElementsMaster/dataElementsIndiv [21]/otherDataFreetext/longFreetext |
CHECK |
|
465 |
/dataElementsMaster/dataElementsIndiv [21]/referenceForDataElement/reference/qualifier |
PT |
|
466 |
/dataElementsMaster/dataElementsIndiv [21]/referenceForDataElement/reference/number |
6 |
|
467 |
/dataElementsMaster/dataElementsIndiv [22]/elementManagementData/reference/qualifier |
OT |
|
468 |
/dataElementsMaster/dataElementsIndiv [22]/elementManagementData/reference/number |
17 |
|
469 |
/dataElementsMaster/dataElementsIndiv [22]/elementManagementData/segmentName |
AB/ |
|
470 |
/dataElementsMaster/dataElementsIndiv [22]/elementManagementData/lineNumber |
36 |
|
471 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/informationType |
2 |
|
472 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[1]/option |
CY |
|
473 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[1]/optionText |
INTEGRA |
|
474 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[2]/option |
NA |
|
475 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[2]/optionText |
MR CASEY |
|
476 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[3]/option |
A1 |
|
477 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[3]/optionText |
1200 RUE MEDECINE |
|
478 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[4]/option |
ZP |
|
479 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[4]/optionText |
49112 |
|
480 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[5]/option |
CI |
|
481 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[5]/optionText |
VALBONNE |
|
482 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[6]/option |
CO |
|
483 |
/dataElementsMaster/dataElementsIndiv [22]/structuredAddress/address[6]/optionText |
FRANCE |
|
484 |
/dataElementsMaster/dataElementsIndiv [22]/referenceForDataElement/reference/qualifier |
PT |
|
485 |
/dataElementsMaster/dataElementsIndiv [22]/referenceForDataElement/reference/number |
1 |
|
486 |
/dataElementsMaster/dataElementsIndiv [23]/elementManagementData/reference/qualifier |
OT |
|
487 |
/dataElementsMaster/dataElementsIndiv [23]/elementManagementData/reference/number |
13 |
|
488 |
/dataElementsMaster/dataElementsIndiv [23]/elementManagementData/segmentName |
AM |
|
489 |
/dataElementsMaster/dataElementsIndiv [23]/elementManagementData/lineNumber |
37 |
|
490 |
/dataElementsMaster/dataElementsIndiv [23]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
491 |
/dataElementsMaster/dataElementsIndiv [23]/otherDataFreetext/freetextDetail/type |
P08 |
|
492 |
/dataElementsMaster/dataElementsIndiv [23]/otherDataFreetext/longFreetext |
BILL CASEY |
|
493 |
/dataElementsMaster/dataElementsIndiv [24]/elementManagementData/reference/qualifier |
OT |
|
494 |
/dataElementsMaster/dataElementsIndiv [24]/elementManagementData/reference/number |
14 |
|
495 |
/dataElementsMaster/dataElementsIndiv [24]/elementManagementData/segmentName |
AM |
|
496 |
/dataElementsMaster/dataElementsIndiv [24]/elementManagementData/lineNumber |
38 |
|
497 |
/dataElementsMaster/dataElementsIndiv [24]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
498 |
/dataElementsMaster/dataElementsIndiv [24]/otherDataFreetext/freetextDetail/type |
P08 |
|
499 |
/dataElementsMaster/dataElementsIndiv [24]/otherDataFreetext/longFreetext |
2252 JEAN MED AVE |
|
500 |
/dataElementsMaster/dataElementsIndiv [25]/elementManagementData/reference/qualifier |
OT |
|
501 |
/dataElementsMaster/dataElementsIndiv [25]/elementManagementData/reference/number |
15 |
|
502 |
/dataElementsMaster/dataElementsIndiv [25]/elementManagementData/segmentName |
AM |
|
503 |
/dataElementsMaster/dataElementsIndiv [25]/elementManagementData/lineNumber |
39 |
|
504 |
/dataElementsMaster/dataElementsIndiv [25]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
505 |
/dataElementsMaster/dataElementsIndiv [25]/otherDataFreetext/freetextDetail/type |
P08 |
|
506 |
/dataElementsMaster/dataElementsIndiv [25]/otherDataFreetext/longFreetext |
VALBONNE 45654 |
|
507 |
/dataElementsMaster/dataElementsIndiv [26]/elementManagementData/reference/qualifier |
OT |
|
508 |
/dataElementsMaster/dataElementsIndiv [26]/elementManagementData/reference/number |
16 |
|
509 |
/dataElementsMaster/dataElementsIndiv [26]/elementManagementData/segmentName |
AM |
|
510 |
/dataElementsMaster/dataElementsIndiv [26]/elementManagementData/lineNumber |
40 |
|
511 |
/dataElementsMaster/dataElementsIndiv [26]/otherDataFreetext/freetextDetail/subjectQualifier |
3 |
|
512 |
/dataElementsMaster/dataElementsIndiv [26]/otherDataFreetext/freetextDetail/type |
P08 |
|
513 |
/dataElementsMaster/dataElementsIndiv [26]/otherDataFreetext/longFreetext |
FRANCE |
|
514 |
/dataElementsMaster/dataElementsIndiv [27]/elementManagementData/segmentName |
ES |
|
515 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/security/identification |
MIA1S1101 |
|
516 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/security/accessMode |
N |
|
517 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/securityInfo/creationDate |
160501 |
|
518 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/securityInfo/agentCode |
AASU |
|
519 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/securityInfo/officeId |
MUC1A0701 |
|
520 |
/dataElementsMaster/dataElementsIndiv [27]/pnrSecurity/indicator |
G |