Point-to-Point, Partial Thru, and O&D Faring

The Point-to-Point faring enhancement automatically searches for both Point-to-Point, Partial Through, and Origin/Destination (O/D) availability for applicable carriers on connecting flights. This enhancement has been added to the following transactions:

• FareQuoteFlightSpecific_13 (request and response) and all later versions.
• FareQuoteFlightSpecific_12 and earlier (response only)

Note:

Point-to-Point faring is already available in all versions of FareQuoteSuperBB (response only).
Previously, faring was available only for Origin and Destination availability provided by the carrier. This routing applies a single availability between the initial origin and the final destination, even if the route contains one or more connections or airlines.

However, Point-to-Point availability applies a separate availability for each flight segment in an interline connection (same carrier). Faring process will then give consideration to both the Origin/Destination (O&D) availability and the Point-to-Point availability when validating applicable fares. Carriers can implement Journey Controls, which allow the carrier to provide both O&D and Point-to Point availability, and to control the use of both availabilities.

Carriers can implement Journey Controls, which allow the carrier to provide O/D (Origin and Destination), Partial-Through and Point-to Point availability, and to control the use of all availabilities.

The fare types in the response depend on available faring for the flight connections. When carriers have implemented Journey Controls, the following rules are applied:

• If a valid rebook with an O/D status is available, each of the connecting flights must be rebooked in the same booking code (same class exception).
• If no valid O/D rebook is found, the route is checked to determine if a valid Point-to-Point rebook exists. For Point-to-Point rebooks, each flight must be rebooked in its own unique booking code (mixed class exception).
• In the case of an online double connection, if partial through status is available, then each of the partial-through connecting flights must be rebooked in the same booking code (same class exception), while the other segment that has different booking code must be rebooked by itself.

Faring Point-to-Point, Partial-Through Availability

Point-to-Point and Partial-Through fare functionality is managed differently between FareQuoteFlightSpecific and FareQuoteSuperBB.

FareQuoteSuperBB

All versions of FareQuoteSuperBB, both current and archived, support Point-to-Point, Partial-Through faring. The response returns O/D, or Partial-Through, and or Point-to-Point fares based on availability.

In FareQuoteSuperBB response, it is recommended that the <FltItemCrossRefPerPricingOpt> should be used and can be requested via

    <FareQuoteSuperBB_#>
       <SuperBBMods>
            <GenQuoteInfo>
                <NewFltItemCrossRefInd>

In the response, the <FltItemCrossRefPerPricingOpt> includes a Sell As Connection indicator with each Flight Item Index, <ConnInd> thus eliminate the need to determine faring instruction.

If the <FltItemCrossRefPerPricingOpt> does not work, use the <InsideAvailOption> in the following XML path:

    <FareQuoteSuperBB_#>
        <AirAvail>
            <AvailFlt>
                <InsideAvailOption>

The following values represent availability options available for <InsideAvailOption>:

• Y = Inside (polled) availability option exists.
• N = No Inside (polled) availability option.
• L = Inside (polled) availability option was used on this flight.
• M = Inside (polled) availability was used on this flight, and was obtained on an Origin and Destination basis. Carrier has implemented Journey Controls.

Two additional values, ‘P’ and ‘J’ indicate a Point-to-Point fare.

• P = Inside (polled) availability was used on this flight and was obtained on a Point-to-Point basis. Carrier has not implemented Journey Controls.
• J = Inside (polled) availability was used on this flight and was obtained on a Point-to-Point basis. The carrier has implemented Journey Controls.

FareQuoteFlightSpecific

All versions of FareQuoteFlightSpecific, both current and archived, support Point-to-Point, Partial Through, and O&D faring.

Selling Point-to-Point Fares

After a Point-to-Point, Partial Through, or O&D availability is obtained from FareQuoteFlightSpecific or FareQuoteSuperBB, the flight segment can be sold using the PNRBFManagement transaction. Point-to-Point, Partial Through, and O&D sell functionality is supported in PNRBFManagement_9 and later and later for Apollo customers and PNRBFManagement_13 and later for Galileo customers.

The <AvailJrnyNum> element in the PNRBFManagement request must be correctly populated to ensure an accurate Point-to-Point segment sell. The following examples uses PNRBFManagement_13.

• <AvailJrnyNum> must be left blank for flight options indicated to be Point-to-Point. A blank value is mandatory to correctly sell the flight segments.
  
  <PNRBFManagement_13>
      <AirSegSellMods>
          <AirSegSell>
              <AvailJrnyNum/>

For sell from FareQuoteSuperBB:

• If using the <FltItemCrossRefPerPricingOpt>, then use the Sell As Connection indicator in the Flight Item index, <ConnInd> to sell the segment as point to point or as connection:

<FareQuoteSuperBB_#>
    <FareInfo>
        <FltItemCrossRefPerPricingOpt>
           <FltItemAry>
              <FltItem>
                <ConnInd>

For sell from FareQuoteFlightSpecific:

If the value of the <AvailLinkStatus> is ‘P’ or ‘J’, sell the segment as point to point, which mean set the <AvailJrnyNum> of the flight to 00 or blank value.

The following values in <AvailLinkStatus> will indicate Point to Point flights:

• P = Inside (polled) availability was used on this flight and was obtained on a Point-to- Point basis and the carrier has not implemented journey controls.
• J = Point-to-Point Cache or Linked status was used on this flight which has different O&D status.