Passenger and Airport Data Interchange Standards
Passenger and Airport Data Interchange Standards
Passenger and Airport Data Interchange Standards
INTERCHANGE STANDARDS
Version 14.1
(subject to approval and publication by the WCO API Contact Committee)
NOTICE
Managing Director,
IATA Distribution and Financial Services
International Air Transport Association
800 Place Victoria
P.O. Box 113
Montreal, Quebec
Canada, H4Z 1M1
Passenger and Airport Data Interchange Standards XML Implementation Guide – PNRGOV
PADIS XML Implementation Guide – PNRGOV (version 14.1)
© 2014 International Air Transport Association. All rights reserved.
Montreal — Geneva
Revision History
Version Date Author Section Change History
13.1 29 Jul 2013 M. Zitkova Initial Publication of a document developed by the PNRGOV WG
14.1 22 Jul 2014 M. Zitkova Modification of Bag Destination in 4.11 and 4.35
14.1 31 Jul 2014 M. Zitkova Modifications in section 1.1
PADIS XML Implementation Guide – PNRGOV Message – Table of Contents
1. INTRODUCTION .................................................................................................................................................. 1
1.1 PNRGOV MESSAGE VERSION RELEASE ...................................................................................................... 1
1.1.1 PROGRESSION LISTING 1
1.1.2 ERRATA 1
1.2 DOCUMENT STRUCTURE ................................................................................................................................ 2
1.3 HOW TO USE THIS DOCUMENT ..................................................................................................................... 2
1.4 GUIDELINES AND RULES ................................................................................................................................ 2
1.5 CODE SETS ......................................................................................................................................................... 3
1.6 REFERENCES ..................................................................................................................................................... 3
2 MESSAGE RELATIONSHIP ............................................................................................................................... 4
2.1 PNRGOV .............................................................................................................................................................. 4
3 SCHEMA STRUCTURE ....................................................................................................................................... 4
3.1 MESSAGE SEGMENT DESCRIPTIONS (PNRGOV) .................................................................................................. 4
3.2 PUSH OF PNR DATA TO STATE - (IATA_PNRGOV_NOTIFRQ) ......................................................................... 6
4 MESSAGE DEFINITION ...................................................................................................................................... 7
4.1 IATA_PNRGOV_NOTIFRQ ................................................................................................................................. 8
4.2 ORIGINATOR - SPECIFIES THE SENDER OF THE MESSAGE ...................................................................................... 10
4.3 FLIGHTLEG - THE FLIGHT FOR WHICH PASSENGER DATA IS BEING SENT .............................................................. 11
4.4 PNRS................................................................................................................................................................... 13
4.5 PNR – REPEATS FOR EACH PASSENGER RECORD .................................................................................................. 14
4.6 BOOKINGREFID – THE RECORD LOCATOR FOR THIS PASSENGER RECORD ............................................................ 15
4.7 SSR – SPECIAL SERVICE DATA THAT APPLIES TO ALL PASSENGER/FLIGHTS ......................................................... 17
4.8 OSI – OTHER SERVICE INFORMATION FOR ALL PASSENGERS/FLIGHTS .................................................................. 19
4.9 POS – ORIGINATION OF THE BOOKING ................................................................................................................. 21
4.10 CONTACTINFO – CONTACT INFORMATION (PHONE, ADDRESS, EMAIL) ................................................................. 23
4.11 PREPAIDBAG – PREPAID BAGGAGE AMOUNTS ..................................................................................................... 25
4.12 PASSENGER – PASSENGER SURNAME, GIVEN NAME, PTC CODE (REPEATS FOR EACH PASSENGER) ...................... 26
4.13 CUSTLOYALTY – FREQUENT TRAVELER NUMBERS FOR THE PASSENGER ............................................................. 29
4.14 OSI – OTHER SERVICE INFORMATION FOR A PASSENGER ..................................................................................... 30
4.15 EXCESSBAGGAGE – EXCESS BAGGAGE INFORMATION FOR ALL PASSENGERS/FLIGHTS ........................................ 32
4.16 FAREINFO – FARE AND UNSTRUCTURED FARE CALCULATION INFORMATION ....................................................... 34
4.17 SSR – SPECIAL SERVICE DATA THAT APPLIES TO THE PASSENGER FOR ALL THE FLIGHTS ..................................... 36
4.18 CONTACTINFO – EMERGENCY CONTACT INFORMATION ....................................................................................... 38
4.19 TICKETDOCUMENT – TICKET DOCUMENT NUMBER, DATE AND PLACE OF ISSUE AND REASONS FOR ISSUANCE CODE
AND SUBCODE (EMDS)........................................................................................................................................ 40
4.20 TOTALFARE – TOTAL FARE AMOUNT ................................................................................................................... 42
4.21 PRICEINFO – PRICING DATE, TIME, ISO COUNTRY CODE , AND LOCATION ............................................................ 43
4.22 TAXES/TAX – TAX AMOUNT FOR THE TICKET ...................................................................................................... 44
4.23 PAYMENTINFO – FORM OF PAYMENT, PAYMENT AMOUNT, CREDIT CARD NUMBER AND EXPIRATION DATE AND
SPONSOR INFORMATION ....................................................................................................................................... 46
4.24 DOC_SSR – FORMATTED DOCA, DOCO, AND DOCS SSR INFORMATION ........................................................ 47
4.25 DOCA – FORMATTED PASSENGER ADDRESS SSR INFORMATION ......................................................................... 49
4.26 DOCO – FORMATTED PASSENGER OTHER SUPPLEMENTARY SSR INFORMATION ................................................. 50
4.27 DOCS - FORMATTED TRAVEL DOCUMENT SSR INFORMATION ........................................................................... 51
4.28 FLIGHT – A FLIGHT IN THE ITINERARY FOR THE PASSENGER ................................................................................ 53
4.29 SSR – SPECIAL SERVICE REQUESTS THAT APPLY TO THIS FLIGHT ......................................................................... 55
4.30 BOOKINGREFID – PASSENGER RECORD LOCATOR SPECIFIC TO THIS FLIGHT ........................................................ 57
4.31 OSI – OTHER SERVICE INFORMATION FOR THIS FLIGHT........................................................................................ 59
4.32 CHECKININFO – THE CHECK-IN TIME AND AGENT INFORMATION THAT CHECKED-IN THE PASSENGER ................. 61
4.33 PASSENGER – THE CHECKED-IN NAME ................................................................................................................. 63
4.34 SEATNUMBER – ACTUAL SEAT NUMBER .............................................................................................................. 64
4.35 CHECKEDBAG – CHECKED BAG INFORMATION .................................................................................................... 65
4.36 SPLITPNR – THE NUMBER OF PASSENGERS SPLIT TO/FROM A PASSENGER RECORD AND THE SPLIT RECORD
LOCATORS ........................................................................................................................................................... 67
4.37 OTHERTRAVELSEGMENT – NON- AIR SEGMENT INFORMATION (CAR, HOTEL) ..................................................... 68
PADIS XML Implementation Guide – PNRGOV Message – Table of Contents
1. INTRODUCTION
The purpose of this document is to describe the recommended usage of the Passenger and Airport Data Interchange
Standards PNRGOV XML (Extensible Mark-up Language) Message Standards. These messages are intended to
facilitate the exchange of data relevant to government requirements on PNR data and Airlines reservation systems.
This document was developed, and will be maintained, by the IATA/A4A PNRGOV Working Group in coordination
with the Data Dictionary and Schema Coordination Committee (DDSCC) of IATA Passenger and Airport Data
Interchange Standards Board.
This will be a living document and will be updated as necessary. If there are any changes to the message structure, the
change process defined in the PNRGOV Principles Document shall be followed.
Message structure change requires a new version of the message and new version of the Implementation Guide.
Changes in the text of the Implementation Guide other than message structure changes may also trigger new
release of the Implementation Guide.
Minor changes can be kept in the Errata document attached to a specific release of the Implementation Guide
and eventually incorporated into the next new release and new version of the same.
Any text pending formal approval by the WCO API Contact Committee and/or the PADIS Board will be shaded
in grey.
This table lists all current PNRGOV XML messages and shows in which PNRGOV Implementation Guide document
release a message was modified from its previous publication. A bold version release shows the first publication of that
message or guide.
1.1.2 ERRATA
An ERRATA sheet will be maintained for each release and will be stored on the IATA website along with the
corresponding Implementation Guide.
Each entry in the Errata sheet will include a sequence number, date included in ERRATA, Implementation
Guide paragraph reference, current text and/or problems description for charts, required change in text and/or
change description for charts, reason for change, and who submitted the ERRATA item. .
Once an entry is made in Errata sheet, the PNRGOV group will receive a notification.
The Errata sheet is intended only for minor corrections. Issues which require debate by the group must be
submitted, together with a proposed solution, as formal agenda items to a PNRGOV Working Group meeting.
Once changes are approved by the PNRGOV Working Group, the group will follow the change process
identified in the Principles document to notify WCO of changes being proposed for the PNRGOV
implementation guide.
1
PADIS XML Implementation Guide – PNRGOV Message
Introduction
Contains an overview and guidelines for use of the document.
Message Relationships
Describes the relationship between push (IATA_PNRGOV_NotifRQ) message and the expected response message
(IATA_AcknowledgementRS).
Examples
For every business function listed there will be at least one example of the data to be transmitted.
Link to register for access to the FAL extranet site containing the API-PNR World Tracker:
http://www2.iata.org/registration/getemailpage.aspx?siteurl=facilitation
Appendices
As necessary, appendices will be added to the Implementation Guide.
Appendix A – xxx
Appendix B – xxx
This guide contains a complete description of the Message Schema, elements and attributes with notes and examples.
2. If an 'N/A' appears in the ‘Max Occurs' column, it indicates that the element or attribute is not used for this
message, as not applicable use has been identified.
2
PADIS XML Implementation Guide – PNRGOV Message
3. Where a State’s requirements differ for “Conditional” fields from the standard implementation guide, a separate
supplemental document will be provided by the State(s) detailing which “Conditional” fields are “Mandatory” for
that State. Provisions in paragraphs 1.5.1 and 1.5.2 of the “Principles, Functional and Business Requirements
PNRGOV” shall be respected. These differing requirements will not change the structure of the message.
4. The schema structure indicates whether elements and attributes are required or optional. Where a State’s
requirements differ from the standard implementation guide, a separate supplemental document will be provided
by the State(s). This will not change the structure of the message.
5. In general, dates and times are expressed in local time except where specifically noted; such as where the time will
be expressed in Greenwich Mean Time (GMT) or Universal Time Coordinated (UTC). However, due to different
systems criteria, the subject of date/times in various fields from various sources (e.g., centralized reservations and
DCS for local vs. centralized system) should be addressed in the bilateral discussions between
governments/airlines/system providers.
6. The ”Type” refers to how the element or attribute is defined (i.e. string, a, an). If an element or attribute has been
restricted to a maximum length or a specific length it will also be noted in the “Type” column.
7. The “Comments” column will use consistent wording for the same attribute across the elements if they are used in
the same way.
8. Each element is followed by “Notes” (if applicable) and by element examples. However, “Notes” are only included
if they are necessary to explain the usage.
9. Each element and message will have examples to show the standard usage as defined by the PADIS group.
10. For the purpose of the PNRGOV documentation all Airlines are referred to as Carriers and all governments are
referred to as States.
Codes used in codesets are used to define the values for the relevant business item. All codesets utilized in the PNRGOV
message are defined in the PASSENGER AND AIRPORT DATA INTERCHANGE STANDARDS - Codeset
Directory.
If additional codes are required, requests should be submitted to PADIS through the PNRGOV Working Group for
approval prior to them being submitted in the PADIS Board vote for inclusion in the standards.
1.6 REFERENCES
The following documents may be used as additional references to the PNRGOV XML Iimplementation Guide:
Definitions of common terms used within the airline industry can be found on the IATA website by accessing the IATA
website as follows:
3
PADIS XML Implementation Guide – PNRGOV Message
2 MESSAGE RELATIONSHIP
This Section describes the possible query and response relationship of the message developed for PNRGOV function.
The following convention is used to represent the possible relationships between messages; a solid line ( ______ )
indicates the primary relationship; and a broken line (-------) indicates an optional relationship.
The message diagram depicts the message relationship by showing the query origin in the top box and the response
origin in the bottom box.
IATA_PNRGOV_NotifRQ
IATA_AcknowlegementRS
2.1 PNRGOV
The following messages are used by airlines, airline service suppliers and States to exchange PNR related data
information.
The IATA_AcknowledgementRS message is only sent where there is a Bilateral Agreement between Carrier and State to
do so.
3 SCHEMA STRUCTURE
This document describes the message structure for the approved IATA_PNRGOV_NotifRQ
Within each of the identified elements there may be multiple attributes. While the elements must be in order shown in
the schema structure, attributes within an element can be in any order.
4
PADIS XML Implementation Guide – PNRGOV Message
5
PADIS XML Implementation Guide – PNRGOV Message
PNRGOVMessage
PNR
StructurePNR UnstructurePNR
BookingRefID SSR OSI POS ContactInfo PrepaidBag Passenger DOC_SSR Flight SplitPNR OtherTravelSegments
History History
6
PADIS EDIFACT Implementation Guide – PNRGOV Message
4 MESSAGE DEFINITION
The PNR information available in the PNRGOV message is defined by a set of xml schema files. The remainder of this document
will define and explain the contents of the message and all necessary definitions. The explanation will extensively utilize the
documentation and drawing capabilities of the Altova® XMLSpy software package. See below for a short explanation of how to
read the diagrams.
Following the diagrams will be a matrix containing mapping of the elements within the diagram to their definitions, counts, code
table mapping, common values/formats and a business definition. At the end of each matrix will be samples showing the usage of
the elements being described.
7
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.1 IATA_PNRGOV_NotifRQ
8
PADIS EDIFACT Implementation Guide – PNRGOV Message
IATA_PNRGOV_NotifRQ
Example:
9
PADIS EDIFACT Implementation Guide – PNRGOV Message
Originator (Mandatory)
Data Item Type Max Comments
Occurs
AirlineCode an2..3 1 The airline providing the data.
SystemCode an2..3 1 The system that delivers the message.
AirlineContactInfo string 1 Contact information for the airline sending
the message.
Example:
<Originator AirlineCode="SQ" SystemCode="1A" AirlineContactInfo="1-800-AIR-LINE"/>
10
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.3 FlightLeg - the flight for which passenger data is being sent
11
PADIS EDIFACT Implementation Guide – PNRGOV Message
FlightLeg (Mandatory)
Data Item Type Max Comments
Occurs
CarrierCode an2..3 1 The operating airline for this flight number
FlightNumber n4 1 The flight number being reported on.
DepartureDateTime YYYY-MM- 1 The departure date and/or time of the flight
DDTHH:MM:SS leg.
ArrivalDateTime YYYY-MM- 1 The arrival date and/or time of the flight leg.
DDTHH:MM:SS
OperationalSuffix a1 1 The operational suffix for this flight
DateChangeNbr string 1 Contains the number of days by which the
flights arrival date differs from its departure
date.
CodeContext string 1 Specifies if IATA or ICAO codes
DepartureAirport/ string 1 The IATA departure airport code for the
LocationCode flight
DepartureAirport/ NA
CodeContext
ArrivalAirport/ string 1 The IATA arrival airport code for this flight.
LocationCode
ArrivalAirport/ NA
CodeContext
Example:
12
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.4 PNRs
PNRs (Mandatory)
Data Item Type Max Comments
Occurs
NumberOfPNRs integer 1 The total number of PNRs for this flight.
Example:
<PNRs NumberOfPnrs="6">
PNR (Mandatory)
Data Item Type Max Comments
Occurs
NumberOfPassengers n..3 1 Number of passengers in this PNR.
PNR_TransDate YYYY-MM-DD or 1 The last date the PNR was modified
YYYY-MM-
DDTHH:MM:SS
PNR_CreationDate YYYY-MM-DD or 1 The creation date of the PNR.
YYYY-MM-
DDTHH:MM:SS
LastTktDate YYYY-MM-DD or 1 The last date this PNR was ticketed.
YYYY-MM-
DDTHH:MM:SS
Example:
13
PADIS EDIFACT Implementation Guide – PNRGOV Message
14
PADIS EDIFACT Implementation Guide – PNRGOV Message
15
PADIS EDIFACT Implementation Guide – PNRGOV Message
BookingRefID (Mandatory)
Data Item Type Max Comments
Occurs
URL N/A
Type IATA_CodeType 1 Code identifying type of record reference:
i.e. record locator number, confirmation
number, etc.
Instance N/A
ID string 1 Reference to a reservation record
ID_Context N/A
CompanyName/ N/A
CompanyShortName
CompanyName/ N/A
TravelSector
CompanyName/ string 1 2-3 character airline/CRS code of the record
Code reference
CompanyName/ N/A
CodeContext
Example:
<BookingRefID ID="W9TEND">
<CompanyName Code="TZ"/>
</BookingRefID>
16
PADIS EDIFACT Implementation Guide – PNRGOV Message
17
PADIS EDIFACT Implementation Guide – PNRGOV Message
SSR
Data Item Type Max Comments
Occurs
SSRCode a4 1 The industry code identifying a particular
type of service request.
ServiceQuantity n..2 1 Specifies the number of special services.
Status a..2 1 Status for this special service request.
BoardPoint a3 1 The board city of the segment to which
special service request applies.
OffPoint a3 1 The off city of the segment to which special
service request applies.
RPH string 1 A unique reference for this SSR
SurnameRefNumber string 1 Used to identify and associate travellers with
the same surname.
Airline/CompanyShortName N/A
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying the system to which
special service applies.
Airline/CodeContext N/A
Text string 1 Text for this SSR.
Example:
18
PADIS EDIFACT Implementation Guide – PNRGOV Message
19
PADIS EDIFACT Implementation Guide – PNRGOV Message
OSI
Data Item Type Max Comments
Occurs
Code an..4 1 A proprietary code used between systems to
identify other service information (OSI)
item.
TravellerRefNumber/RPH string 1 A unique reference for the traveller
TravellerRefNumber/ string 1 Used to identify and associate travellers with
SurnameRefNumber the same surname.
Airline/CompanyShortName N/A
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying system to which OSI
applies.
Airline/CodeContext N/A
Text string 1 Text for this OSI.
Example:
<OSI Code="CTC">
<TravelerRefNumber RPH="1234234" />
<Airline Code="TZ"/>
<Text>7732486972</Text>
</OSI>
20
PADIS EDIFACT Implementation Guide – PNRGOV Message
21
PADIS EDIFACT Implementation Guide – PNRGOV Message
POS (Mandatory)
Source/TerminalID N/A
Source/RequestorID/URL N/A
Source/RequestorID/Type an..3 1 Specifies the originator booking type. i.e.
airline, travel agency, etc.
Source/RequestorID/ N/A
Instance
Source/RequestorID/ID n..9 1 IATA travel agency ID number or pseudo
IATA travel agency number.
Source/RequestorID/ N/A
IDContext
Source/RequestorID/ N/A
MessagePassword
Source/RequestorID/ N/A
CompanyName/
CompanyShortName
Source/RequestorID/ N/A
CompanyName/
TravelSector
Source/RequestorID/ an..3 1 Identifies the IATA 2-3 airline/CRS code of
CompanyName/Code the system that originates the message when
different from the delivering system.
Source/RequestorID/ N/A
CompanyName/
CodeContext
Source/Position N/A
Source/BookingChannel N/A
Example:
<POS>
<Source AgentSine="HDQKE2400" PseudoCityCode="MUC" ISOCountry="KR" ISOCurrency="KRW"
AgentDutyCode="3482192" AirlineVendorID="KE" AirportCode="NBE">
<RequestorID ID="123456789">
<CompanyName Code="TZ"/>
</RequestorID>
</Source>
</POS>
22
PADIS EDIFACT Implementation Guide – PNRGOV Message
23
PADIS EDIFACT Implementation Guide – PNRGOV Message
ContactInfo
Example:
24
PADIS EDIFACT Implementation Guide – PNRGOV Message
PrepaidBag
Data Item Type Max Comments
Occurs
IssuerCode an..3 1 Issuer of the bagtag numbers
SerialNumber string 1 Bag tag number
SequenceCount n..2 1 Number of sequential bag tag numbers
BaggagePool IATA_CodeType 1 Specifies head of pool or member of
pool.
UnitOfMeasureQuanity decimal 1 Weight or number of pieces.
UnitOfMeasure N/A
UnitOfMeasureCode IATA_CodeType 1 If quantity is number of pieces or weight.
Amount Decimal 1 Baggage fee
CurrencyCode an..3 1 Currency code for baggage fee. Use
ISO4217.
DecimalPlace N/A
BagDestination an..5 1 Final destination for baggage.
Example:
25
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.12 Passenger – passenger surname, given name, PTC code (repeats for each passenger)
26
PADIS EDIFACT Implementation Guide – PNRGOV Message
Passenger
Data Item Type Max Comments
Occurs
GivenName an..64 1 Given name of the passenger
MiddleName an..64 3 Middle name of the passenger
SurnamePrefix an..16 1 Passenger surname prefix
Surname an..64 1 The family or last name of the passenger
NameTitle an..16 5 The title for the passenger
RPH string 1 A reference for the passenger
SurnameRefNumber string 1 The reference number for passengers with
the same surname.
BoardingStatus IATA_CodeType 1 Specifies boarding status, such as goshow,
noshow
AccompaniedByInfantInd Boolean 1 When true, the passenger is traveling with an
infant
Example:
27
PADIS EDIFACT Implementation Guide – PNRGOV Message
28
PADIS EDIFACT Implementation Guide – PNRGOV Message
CustLoyalty
Data Item Type Max Comments
Occurs
ProgramID string 1 Owner of the Frequent Flyer program
MembershipID string 1 Frequent Flyer Number
LoyalLevel string 1 Airline Status of FF level
VendorCode string 1 Partner/vendor of FF number.
Example:
<CustLoyalty ProgramID="TZ" MembershipID="1234567"/>
29
PADIS EDIFACT Implementation Guide – PNRGOV Message
30
PADIS EDIFACT Implementation Guide – PNRGOV Message
OSI
Data Item Type Max Comments
Occurs
Code an..4 1 A proprietary code used between systems to
identify other service information (OSI)
item.
TravellerRefNumber/RPH string 1 A unique reference for the traveller
TravellerRefNumber/ string 1 Used to identify and associate travellers with
SurnameRefNumber the same surname.
Airline/CompanyShortName N/A
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying system to which OSI
applies.
Airline/CodeContext N/A
Text string 1 Text for this OSI.
Example:
<OSI Code="CTC">
<TravelerRefNumber RPH="1234234" />
<Airline Code="TZ"/>
<Text>7732486972</Text>
</OSI>
31
PADIS EDIFACT Implementation Guide – PNRGOV Message
32
PADIS EDIFACT Implementation Guide – PNRGOV Message
ExcessBaggage
Data Item Type Max Comments
Occurs
IssuerCode an..3 1 Issuer of the bagtag number(s)
SerialNumber string 1 Bag tag number
SequenceCount n..2 1 Number of sequential bag tag number(s)
BaggagePool IATA_CodeType 1 Specifies head of pool or member of pool.
UnitOfMeasureQuantity decimal 1 Weight or number of pieces.
UnitOfMeasure N/A
UnitOfMeasureCode IATA_CodeType 1 If quantity is number of pieces or weight.
Example:
33
PADIS EDIFACT Implementation Guide – PNRGOV Message
34
PADIS EDIFACT Implementation Guide – PNRGOV Message
FareInfo
Data Item Type Max Comments
Occurs
PTC_Code IATA_CodeType 1 Specify the Passenger Type Code
DiscountedFareType IATA_CodeType 1 Discounted fare type for PTC
DiscountPercent Percentage 1 The discount percentage
CountryCode a2 1 The ISO3166 code of the discount
DiscFareClassType IATA_CodeType 1 The discounted fare classification type
FareBasis string 1 The fare basis code for the fare
InHouseFareType an 1 The in-house fare type or corporate contract
number
UnstructuredFareCalc/Type N/A
UnstructuredFareCalc/ an1 1 The method of pricing for this fare
PricingCode calculation
UnstructuredFareCalc an1 1 Secondary identifier of the method of pricing
ReportingCode
UnstructuredFareCalc/Info string N/A The fare calculation area
Example:
35
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.17 SSR – special service data that applies to the passenger for all the flights
36
PADIS EDIFACT Implementation Guide – PNRGOV Message
SSR
Data Item Type Max Comments
Occurs
SSRCode a4 1 The industry code identifying a
particular type of service request.
ServiceQuantity n..2 1 Specifies the number of special services.
Status a..2 1 Status for this special service request.
BoardPoint a3 1 The board city of the segment to which
special service request applies.
OffPoint a3 1 The off city of the segment to which
special service request applies.
RPH string 1 A unique reference for this SSR
SurnameRefNumber string 1 Used to identify and associate travellers
with the same surname.
Airline/CompanyShortName N/A
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying the system to
which special service applies.
Airline/CodeContext N/A
Text string 1 Text for this SSR.
Example:
37
PADIS EDIFACT Implementation Guide – PNRGOV Message
38
PADIS EDIFACT Implementation Guide – PNRGOV Message
ContactInfo
Data Item Type Max Comments
Occurs
FormattedInd boolean 1 Specifies if the associated data is formatted
or not. When true it is formatted; when false,
not formatted.
DefaultInd N/A
UseType N/A
RPH N/A
Type IATA_CodeType 1 Defines the type of address.
StreetNmbr/POBox string 1 The PO box number for this address
Example:
39
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.19 TicketDocument – ticket document number, date and place of issue and reasons for issuance code and
subcode (EMDs)
40
PADIS EDIFACT Implementation Guide – PNRGOV Message
TicketDocument
Data Item Type Max Comments
Occurs
TicketDocumentNbr string 1 Ticket/document number
Example:
41
PADIS EDIFACT Implementation Guide – PNRGOV Message
TotalFare
Data Item Type Max Comments
Occurs
Amount decimal 1 The total ticket/document amount
CurrencyCode a3 1 The currency code for this amount
DecimalPlaces N/A
Example:
42
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.21 PriceInfo – pricing date, time, ISO country code , and location
PriceInfo
Data Item Type Max Comments
Occurs
Date YYYY-MM-DD 1 The date the booked itinerary was priced
Time HH:MM:SS 1 The time the booked itinerary was priced
ISOCountryCode a2 1 The country in which the booked itinerary
was priced
LocationCode a3 1 Airport/city code in which the booked
itinerary was priced
NetReportingCode an 1 The code indicating the transaction is subject
to net reporting arrangement
NonEndorseableInd Boolean 1 When true, the fare is non-endorsable
NonRefundableInd Boolean 1 When true, the fare is non-refundable
PenaltyRestrictionInd Boolean 1 When true, a penalty restriction applies
Example:
44
PADIS EDIFACT Implementation Guide – PNRGOV Message
Taxes/Tax
Data Item Type Max Comments
Occurs
Qualifier IATA_CodeType 1 Specifies if current, paid, additional tax
ISOCountryCode a2 1 ISO country code or special purpose code
Amount decimal 1 The tax amount
CurrencyCode a3 1 The currency code for the tax amount
DecimalPlaces N/A
TaxType an 1 Tax designator code
FiledAmount N/A
FiledCurrencyCode N/A
FiledTaxType N/A
ConversionRate N/A
Usage N/A
Example:
<Taxes>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD" TaxType="BK"/>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD" TaxType="OO"/>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD" TaxType="YY"/>
</Taxes>
45
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.23 PaymentInfo – form of payment, payment amount, credit card number and expiration date and sponsor
information
PaymentInfo
Data Item Type Max Comments
Occurs
PaymentType IATA_CodeType 1 Specifies the type of payment.
PaymentUse IATA_CodeType 1 Specifies if new or old form of payment
PaymentAmount decimal 1 The form of payment amount
VendorCode an 1 The credit card code.
AccountNbr an 1 The credit card account number
ExpiryDate MMYY 1 The expiration date of the credit card
CardHolderName string 1 The name of the cardholder.
Sponsor string 1 Name, address, and telephone number of
purchaser when other than the passenger.
Example:
46
PADIS EDIFACT Implementation Guide – PNRGOV Message
47
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOC_SSR
Data Item Type Max Comments
Occurs
SSRCode a4 1 Specifies DOCA/DOCO/DOCS
ServiceQuanity n..2 1 Number of services for SSR
Status a..2 1 Status information for the SSR
RPH string 1 A unique reference to the traveller
SurnameRefNbr string 1 Used to reference a traveller with the same
surname
FlightInfo/ N/A
CompanyShortName
FlightInfo/TravelSector N/A
FlightInfo/Code an..3 1 Airline code for this SSR
FlightInfo/CodeContext N/A
FlightInfo/BoardingPoint a3 1 City code where passenger boards this flight.
Flightinfo/DePlanningPoint a3 1 City code where passenger deplanes.
FlightInfo/FlightNumber n..4 1 Flight number for this SSR
FlightInfo/ClassOfSvc a1 1 Class of service
FlightInfo/Date an7 1 Flight date in DDMMMYY format
PaxInfo string 1 Passenger associated name and number in
part as contained in the PNR.
Example:
48
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOCA
Example:
49
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOCO
Example:
50
PADIS EDIFACT Implementation Guide – PNRGOV Message
51
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOCS
Example:
52
PADIS EDIFACT Implementation Guide – PNRGOV Message
53
PADIS EDIFACT Implementation Guide – PNRGOV Message
Flight
Data Item Type Max Comments
Occurs
DepartureDateTime YYYY-MM- 1 Departure date and time for the flight
DDTHH:MM:SS or
YYYY-MM-DD or
HH:MM:SS
ArrivalDateTime YYYY-MM- 1 Arrival date and time for the flight
DDTHH:MM:SS or
YYYY-MM-DD or
HH:MM:SS
ResBookDesigCode a..2 1 Specific booking class
NumberInParty integer 1 Number of travellers associated with this
segment
Status an..2 1 Status information for this segment
FlightNumber an..4 1 Flight number of segment
DateChangeNbr string 1 Identifies the number of days the arrival date
differs from the date of departure.
DepartureAirport/ string 1 IATA airport code for departure airport
LocationCode
DepartureAirport/ N/A
CodeContext
ArrivalAirport/ string 1 IATA airport code for arrival airport
LocationCode
ArrivalAirport/CodeContext N/A
OperatingAirline/ N/A
CompanyShortName
OperatingAirline/ N/A
TravelSector
OperatingAirline/Code a..2 1 Code for airline
OperatingAirline/ N/A
CodeContext
OperatingAirline/ n..4 1 Operating flight number
FlightNumber
OperatingAirline/ a..2 1 Reservation booking airline code when it
ResBookDesigCode differs from the operating code.
Equipment/ an3 1 3 character IATA code for aircraft.
AirEquipType
Equipment/ N/A
ChangeofGauge
MarketingAirline/ N/A
CompanyShortName
MarketingAirline/ N/A
TravelSector
MarketingAirline/Code an..3 1 IATA marketing airline code
MarketingAirline/ N/A
CodeContext
Example:
54
PADIS EDIFACT Implementation Guide – PNRGOV Message
55
PADIS EDIFACT Implementation Guide – PNRGOV Message
SSR
Data Item Type Max Comments
Occurs
SSRCode a..4 1 The industry code identifying a particular
type of service request.
ServiceQuantity n..2 1 Specifies the number of special services.
Status a..2 1 Status for this special service request.
BoardPoint a..3 1 The board city of the segment to which
special service request applies.
OffPoint a..3 1 The off city of the segment to which special
service request applies.
RPH string 1 A unique reference for this SSR
SurnameRefNumber string 1 Used to identify and associate travellers with
the same surname.
Airline/CompanyShortName N/A
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying the system to which
special service applies.
Airline/CodeContext N/A
Text string 1 Text for this SSR.
Example:
56
PADIS EDIFACT Implementation Guide – PNRGOV Message
57
PADIS EDIFACT Implementation Guide – PNRGOV Message
BookingRefID
Data Item Type Max Comments
Occurs
URL N/A
Type IATA_CodeType 1 Code identifying type of record reference:
i.e. record locator number, confirmation
number, etc.
Instance N/A
ID string 1 Reference to a reservation record
ID_Context N/A
CompanyName/ N/A
CompanyShortName
CompanyName/ N/A
TravelSector
CompanyName/Code string 1 2-3 character airline/CRS code of the record
reference
CompanyName/ N/A
CodeContext
Example:
<BookingRefID ID="W9TEND">
<CompanyName Code="TZ"/>
</BookingRefID>
58
PADIS EDIFACT Implementation Guide – PNRGOV Message
59
PADIS EDIFACT Implementation Guide – PNRGOV Message
OSI
Data Item Type Max Comments
Occurs
Code an..4 1 A proprietary code used between systems to
identify other service information (OSI)
item.
TravellerRefNumber/RPH string 1 A unique reference for the traveller
TravellerRefNumber/ string 1 Used to identify and associate travellers with
SurnameRefNumber the same surname.
Airline/ N/A
CompanyShortName
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying system to which OSI
applies.
Airline/CodeContext N/A
Text string 1 Text for this OSI.
Example:
<OSI Code="CTC">
<TravelerRefNumber RPH="1234234" />
<Airline Code="TZ"/>
<Text>7732486972</Text>
</OSI>
60
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.32 CheckInInfo – the check-in time and agent information that checked-in the passenger
61
PADIS EDIFACT Implementation Guide – PNRGOV Message
CheckInInfo
Data Item Type Max Comments
Occurs
Time YYYY-MM- 1 The date and/or time the passenger checks
DDTHH:MM:SS in.
or
YYY-MM-DD
or
HH:MM:SS
AgentID string 1 The agent who checked in passenger
BoardingNumber/Number an 1 The boarding or sequence number
BoardingNumber/Type IATA_CodeType 1 Used to specify the type of number either
boarding or check-in
BoardingNumber/RPH string 1
BoardingNumber/ string 1 Identifies and associates travellers with
SurnameRefNumber the same surname.
Example:
62
PADIS EDIFACT Implementation Guide – PNRGOV Message
Passenger
Example:
<Passenger>
<GivenName>KEVINMICHAELMR</GivenName>
<Surname>DENBERG</Surname>
</Passenger>
63
PADIS EDIFACT Implementation Guide – PNRGOV Message
SeatNumber
Example:
<SeatNumber CabinClass="Y">23</SeatNumber>
64
PADIS EDIFACT Implementation Guide – PNRGOV Message
65
PADIS EDIFACT Implementation Guide – PNRGOV Message
CheckedBag
Example:
66
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.36 SplitPNR – the number of passengers split to/from a passenger record and the split record locators
SplitPNR
Data Item Type Max Comments
Occurs
NbrOfPassengers n 1 Number of passengers in the new split out
PNR
VendorCode an 1 The owner of the PNR.
PNR_ID an 1 The PNR identifier.
Example:
67
PADIS EDIFACT Implementation Guide – PNRGOV Message
68
PADIS EDIFACT Implementation Guide – PNRGOV Message
OtherTravelSegment
Example:
69
PADIS EDIFACT Implementation Guide – PNRGOV Message
HotelInfo
Example:
70
PADIS EDIFACT Implementation Guide – PNRGOV Message
CarInfo
Example:
71
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.40 StructuredPNR_History – structured PNR history (repeats for each occurrence of a history credit).
Note: Includes the originator of the change, agent ID, and a time stamp.
72
PADIS EDIFACT Implementation Guide – PNRGOV Message
CreditInfo
Example:
<StructuredPNR_History>
<Credit Type="4" TimeStamp="2013-05-13T18:13:00">
<CompanyName Code="TZ"/>
</Credit>
73
PADIS EDIFACT Implementation Guide – PNRGOV Message
Item
Example:
<Item Action="X">
74
PADIS EDIFACT Implementation Guide – PNRGOV Message
75
PADIS EDIFACT Implementation Guide – PNRGOV Message
Flight
Example:
Passenger
Example:
<Passenger SurnameRefNumber="1">
<GivenName>SEJOON</GivenName>
<Surname>PARK</Surname>
</Passenger>
77
PADIS EDIFACT Implementation Guide – PNRGOV Message
78
PADIS EDIFACT Implementation Guide – PNRGOV Message
SSR
Data Item Type Max Comments
Occurs
SSRCode a4 1 The industry code identifying a particular
type of service request.
ServiceQuantity n..2 1 Specifies the number of special services.
Status a..2 1 Status for this special service request.
BoardPoint a3 1 The board city of the segment to which
special service request applies.
OffPoint a3 1 The off city of the segment to which special
service request applies.
RPH string 1 A unique reference for this SSR
SurnameRefNumber string 1 Used to identify and associate travellers with
the same surname.
Airline/ N/A
CompanyShortName
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying the system to which
special service applies.
Airline/CodeContext N/A
Text string 1 Text for this SSR.
Example:
79
PADIS EDIFACT Implementation Guide – PNRGOV Message
80
PADIS EDIFACT Implementation Guide – PNRGOV Message
OSI
Data Item Type Max Comments
Occurs
Code an..4 1 A proprietary code used between systems to
identify other service information (OSI)
item.
TravellerRefNumber/RPH string 1 A unique reference for the traveller
TravellerRefNumber/ string 1 Used to identify and associate travellers with
SurnameRefNumber the same surname.
Airline/ N/A
CompanyShortName
Airline/TravelSector N/A
Airline/Code string 1 Airline code identifying system to which OSI
applies.
Airline/CodeContext N/A
Text string 1 Text for this OSI.
Example:
<OSI Code="CTC">
<TravelerRefNumber RPH="1234234" />
<Airline Code="TZ"/>
<Text>7732486972</Text>
</OSI>
81
PADIS EDIFACT Implementation Guide – PNRGOV Message
82
PADIS EDIFACT Implementation Guide – PNRGOV Message
Seat
Example:
83
PADIS EDIFACT Implementation Guide – PNRGOV Message
Bag
UnitOfMeasure N/A
Example:
84
PADIS EDIFACT Implementation Guide – PNRGOV Message
85
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOC_SSR
Data Item Type Max Comments
Occurs
SSRCode a4 1 Specifies DOCA/DOCO/DOCS
ServiceQuanity n..2 1 Number of services for SSR
Status a..2 1 Status information for the SSR
RPH string 1 A unique reference to the traveller
SurnameRefNbr string 1 Used to reference a traveller with the same
surname
FlightInfo/ N/A
CompanyShortName
FlightInfo/TravelSector N/A
FlightInfo/Code an..3 1 Airline code for this SSR
FlightInfo/CodeContext N/A
FlightInfo/BoardingPoint a3 1 City code where passenger boards this flight.
Flightinfo/DePlanningPoint a3 1 City code where passenger deplanes.
FlightInfo/FlightNumber n..4 1 Flight number for this SSR
FlightInfo/ClassOfSvc a1 1 Class of service
FlightInfo/Date an7 1 Flight date in DDMMMYY format
PaxInfo string 1 Passenger associated name and number in
part as contained in the PNR.
Example:
86
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOCA
Example:
87
PADIS EDIFACT Implementation Guide – PNRGOV Message
4.50 DOCO – history formatted passenger other supplementary information SSR changes
DOCO
Example:
88
PADIS EDIFACT Implementation Guide – PNRGOV Message
89
PADIS EDIFACT Implementation Guide – PNRGOV Message
DOCS
Example:
90
PADIS EDIFACT Implementation Guide – PNRGOV Message
UnstructuredHistory
Example:
<UnstructuredPNR_History>/130513/TZ X 130528/130529/S/1/HK/6/SIN/OOL/TZ</UnstructuredPNR_History>
91
PADIS EDIFACT Implementation Guide – PNRGOV Message
<IATA_PNRGOV_NotifRQ
EchoToken="123456" TimeStamp="2013-05-27T07:54:00" Target="Production" Version="1.000"
TransactionIdentifier="a8431fd0-e8a7-11e2-91e2-0800200c"
SequenceNmbr="1" TransactionStatusCode="Start" RetransmissionIndicator="false"
CorrelationID="57ab4200-e8a7-11e2-91e2-0800200c9a66"
xsi:schemaLocation="http://www.iata.org/IATA/2007/00 IATA_PNR_GOV_NotifRQ.xsd"
xmlns="http://www.iata.org/IATA/2007/00"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Originator AirlineCode="SQ" SystemCode="1A" AirlineContactInfo="1-800-AIR-LINE"/>
<FlightLeg CarrierCode="SQ" FlightNumber="609" DepartureDateTime="2013-05-27T16:40:00"
ArrivalDateTime="2013-05-28T22:00:00" DateChangeNbr="+1">
<DepartureAirport LocationCode="ICN"/>
<ArrivalAirport LocationCode="SIN"/>
</FlightLeg>
<PNRs NumberOfPnrs="1">
<PNR NumberOfPassengers="2" PNR_TransDate="2013-05-13T21:25:00"
PNR_CreationDate="2013-05-01" LastTktDate="2013-05-13T21:24:00">
<BookingRefID ID="W9TEND">
<CompanyName TravelSector="1" Code="TZ"/>
</BookingRefID>
<SSR SSRCode="OTHS" ServiceQuantity="1" Status="HK" BoardPoint="SIN"
OffPoint="OOL" RPH="1234234">
<Airline Code="TZ" />
<Text>ADV TKT NUMBER BY 03MAY13 1800CO OR WILL CANCEL</Text>
</SSR>
<OSI Code="CTC">
<TravelerRefNumber RPH="1234234" />
<Airline Code="TZ"/>
<Text>7732486972</Text>
</OSI>
<POS>
<Source AgentSine="HDQKE2400" PseudoCityCode="MUC" ISOCountry="KR"
ISOCurrency="KRW" AgentDutyCode="3482192" AirlineVendorID="KE" AirportCode="NBE">
<RequestorID ID="123456789">
<CompanyName Code="TZ"/>
</RequestorID>
</Source>
</POS>
<ContactInfo PhoneNumber="5555555" PhoneType="4" EmailAddress="bob@domain.com">
<StreetNmbr StreetNmbrSuffix="123" StreetDirection="NW"/>
<AddressLine>ANY STREET</AddressLine>
<CityName>LAKE TOWN</CityName>
<PostalCode>55123</PostalCode>
<StateProv StateCode="MN"/>
<CountryName Code="US"/>
</ContactInfo>
<PrepaidBag UnitOffMeasureQuantity="2" UnitOfMeasureCode="700" Amount="26.00"
CurrencyCode="CAD" BagDestination="SIN"/>
<Passenger RPH="1234234" SurnameRefNumber="43576" BoardingStatus="63">
<GivenName>KEVINMICHAELMR</GivenName>
<Surname>DENBERG</Surname>
<CustLoyalty ProgramID="TZ" MembershipID="1234567"/>
<ExcessBaggage IssuerCode="SQ" SerialNumber="0012313122"
SequenceCount="1" BaggagePool="MP" UnitOfMeasureQuantity="20" UnitOfMeasureCode="700"/>
<FareInfo PTC_Code="A" DiscountedFareType="764" DiscountPercent="5"
CountryCode="US" DiscFareClassType="B2" FareBasis="SFLY"/>
<SSR SSRCode="NSSA" ServiceQuantity="1" Status="HN" BoardPoint="ICN"
OffPoint="SIN" RPH="1234234" SurnameRefNumber="1">
<Airline Code="SQ"/>
<Text>MADDOX/MOLLY</Text>
92
PADIS EDIFACT Implementation Guide – PNRGOV Message
</SSR>
<TicketDocument TicketDocumentNbr="121341212311" Type="1"
DateOfIssue="2013-05-13" TicketLocation="SIN" PrimaryDocInd="true">
<TotalFare Amount="1999.99" CurrencyCode="SGD"/>
<PricingInfo Date="2013-05-01" Time="12:15:00" ISOCountryCode="CN"
LocationCode="S1N" NonEndorsableInd="true" NonRefundableInd="true"
PenaltyRestrictionInd="true"/>
<Taxes>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD"
TaxType="BK"/>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD"
TaxType="OO"/>
<Tax Amount="99.99" ISOCountry="CN" CurrencyCode="SGD"
TaxType="YY"/>
</Taxes>
<PaymentInfo PaymentType="CC" PaymentUse="NEW"
PaymentAmount="999.00" VendorCode="MC" ccountNbr="************1344" ExpiryDate="1214"
CardHolderName="KEVIN MICHAEL VON DENBERG"/>
</TicketDocument>
<DOC_SSR SSRCode="DOCA" ServiceQuantity="1" Status="HK">
<FlightInfo Code="TZ"/>
<DOCA AddressType="D" Address="123 Jefferson Ave" CityName="Atlanta"
PostalCode="13445" StateProvCounty="GA" Country="USA"/>
</DOC_SSR>
<DOC_SSR SSRCode="DOCO" ServiceQuantity="1" Status="HK">
<DOCO BirthLocation="USA" TravelDocType="V" TravelDocNbr="1214213"
PlaceOfIssue="CAN" DateOfIssue="02FEB12" CountryState="CAN"/>
</DOC_SSR>
<DOC_SSR SSRCode="DOCS" ServiceQuantity="1" Status="HK">
<DOCS DateOfBirth="04JUL80" ExpiryDate="12JAN19"
FirstGivenName="KEVIN" SecondGivenName="MICHAEL" Surname="VON DENBERG"
Gender="M" IssuingLoc="USA" PaxNationality="USA"
TravelDocNbr="548721687" TravelDocType="P"/>
</DOC_SSR>
</Passenger>
<Flight DepartureDateTime="2013-05-31T22:25:00" ArrivalDateTime="2013-05-29T07:50:00"
ResBookDesigCode="S" NumberInParty="1" Status="HK"
FlightNumber="6">
<DepartureAirport LocationCode="SIN"/>
<ArrivalAirport LocationCode="OOL"/>
<OperatingAirline Code="SQ" FlightNumber="4523" ResBookDesigCode="S"/>
<MarketingAirline Code="TX"/>
<CheckInInfo AgentID="131312" Time="2013-05-27T13:00:00">
<BoardingNumber Number="5">
<Passenger>
<GivenName>KEVINMICHAELMR</GivenName>
<Surname>DENBERG</Surname>
</Passenger>
<SeatNumber CabinClass="Y">23</SeatNumber>
<CheckedBag IssuerCode="SQ" SerialNumber="0012313122"
SequenceCount="1" BaggagePool="MP"/>
</BoardingNumber>
</CheckInInfo>
</Flight>
<SplitPNR NbrOfPassengers="1" VendorCode="SG" PNR_ID="YASDAS"/>
<OtherTravelSegment ServiceID="HTL" StartDate="2013-05-27" EndDate="2013-05-30"
Quantity="1">
<StartLocation LocationCode="ICN"/>
<HotelInfo
CustomerName="Kevin Von Denberg" HotelName="Hilton"
PropertyID="14234" Rate="150.00"/>
</OtherTravelSegment>
93
PADIS EDIFACT Implementation Guide – PNRGOV Message
94