PNRRetrieve Documentation Notes

  1. The following is a complete list of segment types. For example, a car segment is different from a manual car segment where the agent might book the car vendor directly over the phone rather than reserving via a host link to the vendor.  Notice that there are three different types of limo segments.

     

    Segment Type KLR  XML Tag Host

    Air

    IT01

    <AirSeg>

    Both

    Open Air Segment

    IT08

    <OpenAirSeg>

    Both

    Hotel

    IT03

    <HtlSeg>

    Both

    Car

    IT05

    <CarSeg>

    Both

    Manual Car (CAR)

    IT07

    <NonAirSeg>

    Both

    Manual Hotel (HTL)

    IT07

    <NonAirSeg>

    Both

    Manual Air Taxi (ATX)

    IT07

    <NonAirSeg>

    Both

    Manual Surface (SUR)

    IT07

    <NonAirSeg>

    Both

    Manual Tour (TUR)

    IT07

    <NonAirSeg>

    Both

    Manual Theatre (THE)

    IT07

    <NonAirSeg>

    Both

    Manual Limo (LIM)

    IT07

    <NonAirSeg>

    Both

    Manual Insurance (INS)

    IT07

    <NonAirSeg>

    1G Only

    Manual Other (OTH)

    IT07

    <NonAirSeg>

    1G Only

    Flyg Shared Airport Taxi (TAXI)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Airport Bus (FBUS)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Airport Bus – Taxi (FBTA)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Personal Limo (ELIM)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Personal Airport Taxi (VTAX)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Shared Limo (LIMO)

    IT10

    <FlygTaxiSeg>

    1G Only

    Flyg Airport Train (RAIL)

    IT10

    <FlygTaxiSeg>

    1G Only

    Tour (Leisure Shopper)

    IT11

    <TourSeg>

    Both

    Cruise

    IT12

    <CruiseSeg>

    Both

    ARNK (Arrival Unknown)

    IT13

    <ARNK>

    Both

    Train

    IT14

    <TrainSeg>

    Both

    Bus

    IT14

    <TrainSeg>

    Both

    DuePaidInfo Due (D)

    IT14

    <TrainSeg>

    1G Only

    DuePaidInfo Paid (P)

    IT14

    <TrainSeg>

    1G Only

    DuePaidInfo Text (T)

    IT14

    <TrainSeg>

    1G Only

     

  2. Segments should be sorted using the <SegNum> tag.

  3. Some KLR blocks (elements) have <SegNum> tag but are not real segments – these KLRs reference a segment for the purpose of association.

  1.  When trying to list all passengers, use the BP12 <FNameInfo>; i.e., there will always be at least 1 <FNameInfo> for each passenger in the PNR.  The BP10 <LNameInfo> may only be listed once for multiple passengers.

  2. The following data lists the correct associations for the return values possible for the <Type> field in the IT10 <FlygTaxiSeg>:

  1.  The BP16 <PhoneInfo> / <Type> element contains the following:

All of the codes except for the “A” (Agency) should be interpreted as existing for the passenger; e.g., the “F” Fax number would be interpreted as the fax number of the passenger and not the fax number of the agency.

  1. The IT10 <FlygTaxiSeg> always displays in tandem with an air/flight segment. The <FlygTaxiSeg> can be reserved or open.
    FlygTaxiSeg: This is a taxi that is reserved in conjunction with a flight segment. The taxi segment is often reserved on a particular time, but can also be open. All segments are quotable in Global Fares.

  2. The IT07 <NonAirSeg> behaves differently than other segment types. Multiple <NonAirSeg> may be returned with a different line of text <Text> that actually refer to the same type of <NonAirSeg>.  For example, a <NonAirSeg> of <Type> TUR (Tour) may return multiple <NonAirSeg> elements with a different <Text> line in each <NonAirSeg>, but each of these <NonAirSeg> elements must be matched and displayed together. The matching logic should use all of the fields except for the <SegNum> and <Text> fields.

  3. The IT09 <DuePaidInfo> tag called <Type> -  the value of this tag references the IT07 <NonAirSeg>.