A number identifying a group of persons which have their baggage pooled. The number is unique within the flight. (I.e. all persons belonging to this group have the same BaggagePoolId). Note! BaggagePoolId should not be confused with the term "PassengerGroupId" which is used to group passengers for seating purposes.
The 3-digit IATA allocated code identifying the airline that has issued the bag tag. See BagTagNumber for information about the other parts, and AirlineIATAThreeNumeric for more information about the 3-digit IATA code.
The number of bags that has been checked in at the same time.
The number of bags that has been checked in sequence at the same time. In the context of this service it is for information purposes only. NOTE! In the PRL (RP 1719b) one BagTag can represent more than one bag. In the PRL the sequenceCount thus indicate the number of bags represented by one element in the interface. This is NOT allowed in the setIPI operation. All bags shall have its own bagtag element.
A code identifying the card issuing company. What this code actually is depends on the type of card. In the issuer's domain the cart itself is identified by the CardNumber.
A unique card number within the Issuers domain. What the card number actually is depends on the type of card. The issuer is identified by the CardIssuerCode.
FlightId typically identifies a flight to the majority of systems, but it is not unique across time. It's unique only in conjunction with FlightDepartureDate.
Exception: Some airlines use their ICAO code (OperatingAirlineICAO) instead of OperatingAirlineIATA. This might be because they aren't an IATA member or because they just prefer the ICAO code. Regardless, this means that it is allowed to use OperatingAirlineICAO as part of FlightId.
The scheduled date (based on UTC) of departure of flight. For flights with multiple legs this is the departure of the first leg. This date must not change once set as it is used to make the FlightIds unique.
One element for each of the passengers checked baggage. Note! if passenger is part of a baggage pool, the CheckedBaggageData elements will only be present for the "head of pool".
Identifies the outbound flight the passenger will depart on. (Only relevant for transfer passengers.) The inbound FlightLegIdentifier is given separately and is of course common for all inbound passengers on the same flight.
If the passenger started his travel before the flight this InboundPassengerData is for, information about any additional previous flight legs may be given here. (One element for each leg).
NOTE! The PRL (RP1719b) defines that several information elements shall not be repeated for passengers belonging to the same passenger group, even though they applies to all passengers in the group. In the Inbound Passenger Information Service all these information elements MUST be repeated for all passengers in the passenger group.
ResponseStatusCode indicates if the operation succeeded or failed, and if it failed - why. ResponseStatusText is a textual description of ResponseStatusCode. For all operations the set of response codes must be defined. The actual set is dependent upon the context.
"OK": Operation succeded.
"ERR01":
"ERR02":
"":
"":
"ERR99": Other error. "statusText" should describe the error.
Identifier that can be used to correlate messages, transactions, log entries etc. The identifier should be unique across all relevant systems. It is the responsibility of the creator of the message/transaction/log entry/... to guarantee uniqueness. The CorrelationId can for instance be a GUID, or something shorter based on site specific rules.
Name of the organization/company that created the original data. This will typically be an airline company or an handler. The value set are site specific.
The sequence number of the passengers boarding pass.
However, identification of a passenger based on his boarding pass may alternatively be done by comparing PassengerName, FlightLegIdentifier and OperatingCarrierPnrCode with the information read from the boarding pass 2D barcode.
The issuer code and masked credit card number. Can be used to identify a passenger by his credit card. A masked credit card number is not unique in the world, but is highly likely to be unique in any relevant setting.
Must be given if passenger should be identified by his credit card.
The issuer code and card number of a frequent flyer card. Can be used to identify a passenger by his frequent flyer card. Must be given if passenger should be identified by his frequent flyer card.
Should be present. However, identification of a passenger based on his "ticket document" may alternatively be done by comparing PassengerName, FlightLegIdentifier and OperatingCarrierPnrCode with the information read from the ticket 2D barcode.