Task: Air Segment Sell via Direct Sell

Air Segment Sell allows for the selling of air segments via Direct Sell using flight details.

Section 1: Short Answer

Transaction Name: 

PNRBFManagement_26

Can any other transaction(s) perform this same task?

Previous versions of PNRBFManagement.

Can this task be performed in a sessionless environment?

A direct sell can be performed within a sessioned environment. Direct sells are more typically performed in a sessionless environment; however, the client must send all mandatory request data required to complete the sell.

Are the request and response identical on both the Apollo and Galileo systems?

Yes.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

PNRBFManagement_26 supports Direct Sell using flight details.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

The inclusion of a <DoNotStopSellProcOnFailure> in a <AirSegSellMods> or <PassiveSegmentSellMods> indicates that Air Segment Sell errors (such as no availability) will not stop the procedure being processed.

• If this tag is included, expect in a Sell failure to return an <ErrText> response as "normal" but with a 0 return code.
• Not including this tag will return the <ErrText> and the usual non-zero code; procedure processing will stop (this is current normal processing).

Section 2: Detailed Description

PNRBFManagement_26 can be used for requesting air segments from the Galileo and Apollo systems. There are several functions that can be performed:

• Direct sell

• Reference sell (via general and carrier specific availabilities)

• Rebook/cancel via direct sell

• Rebook/cancel via reference sell (via general and carrier specific availabilities)

• Point to Point - see Point to Point (P2P), Partial Thru, and O&D Shopping and Faring.

Segments are sold according to the class of service. Generally, it is recommended to store the associated fare quote when the segment is sold, unless the segment is ticketed immediately. (Stored fares are required on Galileo and optional on Apollo). Because fare quotes can change at any time prior to ticketing, storing the fare provides a history of the fare that was quoted to the traveler that can be compared against a later, quoted or ticketed fare.

Air segments can be sold with or without first making an availability request. However, an initial check of a flight's availability can help prevent frustration and confusion. Three basic types of request codes are available for selling a flight:

• NN ('need need') - Considered a "regular sell." The passenger has selected a specific flight on a specific day, and is indicating a confirmed seat is desired. When booking a flight in a regular sell, the passenger must know the airline, flight number, class of service, date of departure, number of travelers in the party, and origin and destination.
• LL ('list list') - This code is used to 'waitlist' a passenger on a flight that is already showing fully booked. It is a request to be put on a list, in the event another traveler cancels his/her flight reservation. Normally, a passenger will follow a waitlist request with a regular sell on an alternate flight as backup. When waitlisting a flight, the passenger must know the airline, flight number, class of service, date of departure, number of travelers in the party, and origin and destination.
• NO ('need open') - This code is used when the passenger knows only the airline, origin, and destination, but is not sure of either the departure date, the departure time, or both the date and time. Because the actual flight can be selected just hours prior to departure, open segments are often booked in the class of service that represents the lowest unrestricted fare available. When this type of air segment is ticketed, the word 'Open' appears where the flight number is normally shown.

PNRBFManagement_26 provides the ability to sell an ARNK segment (arrival unknown) as well as provides an ‘insert after’ function. If an insert after is submitted, the segments are inserted after the specified after. Flight segments are sold and added to the reservation. Additional flight segments may be added to an existing reservation.

To use this transaction, a user should have an agent sign-on. For ‘insert after’, AAT needs to be set up for non-ASP user (SASP field = NO).

Request:

Unless otherwise specified, use ALL CAPS in any request data.

For some carriers, the user must emulate an agency. 

• Direct/Manual Sell
  <AvailSource> node should be kept blank in <AirSegSellMods> / <AirSegSell> record. This is because the availability status source is unknown in case of direct/manual sell.

• Request: Selling after Fares Availability
  • If the sell request is performed after a FareQuoteSuperBB response, the <InsideAvailOption> and the <AvailSource> should be retrieved from the AAFI <AvailFlt> in the 1001 <AirAvail> response. The value in these fields should be used to populate the <AvailLinkStatus> and the <AvailSource> in the SQS1 <AirSegSell> element in the 1060 <AirSegSellMods> record.
  • If the sell request is performed after a FareQuoteFlightSpecific response, the <AvailLinkStatus> and the <AvailSource> should be retrieved from the GFIS <ItinSeg> element in the 1425 <FareInfo> record. The value in this field should be added to the <AirSegSell> element in the <AirSegSellMods> record.
  • If the <AvailLinkStatus> is a P or J value, the availability was obtained on a point-to-point basis. It is mandatory that the <AvailJrnyNum> be left blank in this case to correctly sell the flight segments.

• Request: Selling after General Availability
  If the sell request is performed after an AirAvailability response, the <InsideAvailOption> and the <AvailSource> should be retrieved from the the <AvailFlt> element in the <AirAvail> response record. The values in these fields should be used to populate the <AvailLinkStatus> and the <AvailSource> in the <AirSegSell> element in the <AirSegSellMods> record.

• Request: Availability Journey Number
  In the <AirSegSell> element, the <AvailJrnyNum> node is used to indicate the ‘bundling’ or ‘journey origin and destination’ of flights from an availability display. For example, in a 3 segment connection from Denver to Prague and back, if the outbound and return flights are sold at the same time, then the various flights are tied together (bundled). See sample s110. A direct flight is designated by a blank <AvailJrnyNum>.

Prerequisite tasks:

There are no prerequisite tasks.

Expected response:

Description:  Flight data

<TextMessage> tag:  The <AirSell> tag will be followed by one or more <Txt> tags containing flight data.

Error and warning responses:

<ErrText> tag:  Level number, version number, text.

In the following scenarios, errors or warnings for both Galileo (1G) and and Apollo (1V) are in black, 1G are in blue, and Apollo are in green.

1.  Scenario:  Sell of Secured Sell without emulating an agency (Secured Sell vendors).

• Error:  SELL ON THIS CARRIER ONLY PERMITTED WITH AG DUTY CODE (1G)

2.  Scenario:  Attempting a sell when signed in as a non-agent (e.g., SU duty code).

• Error:  SELL ON THIS CARRIER ONLY PERMITTED WITH AG DUTY CODE (1G)

<AirSell> tag: 

<TextMessage> tag/<ErrText> tag:  Number of arrays, delimiter character, level number, version number, <Err>, <KlrInErr>, <Text>.

In the following scenarios, errors or warnings for both Galileo and Apollo are in black, Galileo are in blue, and Apollo are in green.

1.   Scenario:  System error.

• Error:  SYSTEM ERROR – IGNORE TRANSACTION RECOMMENDED n (1G)
• Error:  UNABLE TO PROCESS (1G)
• Error:  *SYSTEM ERROR* (1G)
• Error:  UNA PROC (1V)
• Error:   SYS ERROR OCCURRED (1V)

2.   Scenario:  Schedule change active.

• Error:  SKED CHG ACT (1V)
• Error:  SCHEDULE CHANGE ACTIVE FOR THIS SEGMENT (1V)
• Error:  NO GROUP ACTION ALLOWED DURING SCHEDULE CHANGE (1V)

3.   Scenario:  AADC (AA Direct Connect) Request.

• Error:  UNABLE—0 SEATS AVAILABLE (1V)

4.   Scenario:  Filed fares in progress.

• Error:  MANUAL FARES IN PROGRESS - FINISH OR IGNORE (1G)

5.   Scenario:  Sell once Super-Guaranteed or Guaranteed sell agreement has expired.

• Error:  IGNORE/END TRANSACT BF BEFORE CONTINUING (1G)
• Error:  UNABLE – SELL OPTION EXPIRED – CHECK ITINERARY (1G)

6.   Scenario:  Option sell has expired with an attempt to sell.

• Error:  UNABLE – SELL OPTION EXPIRED – CHECK ITINERARY (1G)

7.   Scenario:  Itinerary contains 99 segments.

• Error:  CHECK NUMBER / EXCEEDS 99 SEGMENTS (1G)
• Error:  CK NBR/EXCEEDS 99 SEGS (1V)

8.   Scenario:  Error with the itinerary.

• Error:  IGNORE – DATA IN AAA NO LONGER VALID (1G)
• Error:  ERROR – IGNORE AND REENTER (1V)

9.   Scenario:  Duplicate segments exist in the itinerary.

• Error:  UNABLE - DUPLICATE SEGMENT (1G)
• Error:  DUPLICATE SEGMENT NOT PERMITTED (1V)

10. Scenario:  Invalid carrier code OR flight details.

• Error:  *SECURED SELL NOT AVAILABLE* (1G)
• Error:  FLIGHT NOT FOUND – DEP/ARR TIMES REQUIRED (1G)
• Error:  FLIGHT NOT FOUND – CHECK FLIGHT DETAILS (1G and 1V)
• Error:  UNABLE – FLIGHT DOES NOT OPERATE THIS DATE AND/OR CITY PAIR (1G)
• Error:  *UNABLE - FLIGHT NOT FOUND IN VENDOR SYSTEM* (1G)
• Error:  CK FLT NBR (1V)
• Error:  CK FRMT (1V)
• Error:  CARRIER NOT STORED (1V)

11. Scenario:  Attempting to sell UA flight with BK/GK/HK status.

• Error:  BK/GK/HK NOT ALLOWED FOR UA (1V)

12. Scenario:  Invalid bucket number for UA flight.

• Error:  BUCKET INVALID FOR CLASS (1V)

13. Scenario:  Corporation is not in the Corporate Table for a Corporate segment.

• Error:  NOT IN TBL (1V)

14. Scenario:  Invalid class code.

• Error:  CHECK CLASS (1G)
• Error:  CLASS OF SERVICE UNAVAILABLE – RESELECT (1G)
• Error:  *UNABLE – CLASS DOES NOT EXIST FOR THIS FLIGHT* (1G)
• Warning:  CLASS NOT FOUND – WILL REQUEST FROM AIRLINE (1G)
• Error:  CLASS NOT FOUND – PASSIVE PROHIBITED BY AIRLINE (1G and 1V)
• Error:  FLIGHT DATA NOT AVAILABLE – VERIFY YOUR ENTRY (1V)

15. Scenario:  Connection unavailable.

• Error:  *UNABLE – MARKET CONNECTION UNAVAILABLE* (1G)

16. Scenario:  Invalid board or off points.

• Error:  CHECK BOARD/OFF POINT (1G)
• Error:  CK BD PNT (1V)
• Error:  CK OFF PNT (1V)

17. Scenario:  Invalid action code (i.e.:  not NN/AN/AL/AK/BL/BN/BK).

• Error:  CHECK ACTION CODE (1G)
• Error:  CK ACTN CODE (1V)

18. Scenario:  Invalid number in party (i.e., non-numeric).

• Error:  CHECK NUMBER OF SEATS (1G)
• Error:  CHECK NUMBER IN PARTY (1G)
• Error:  CK NBR IN PTY (1V)

19.  Scenario:  Invalid timing.

• Error:  CHECK TIMINGS (1G)
• Error:  CK ARR DPT TIME (1V)

20.  Scenario:  Invalid date.

• Error:  UNABLE – FLIGHT DOES NOT OPERATE THIS DATE AND/OR CITY PAIR (1G)
• Error:  UNABLE – DATE OUTSIDE VENDORS SYSTEM RANGE (1G)
• Error:  CK DATE (1V)

21. Scenario:  Flight inhibited.

• Error:  NO BOARDING THIS CITY – ccc (1V)
• Error:  UNABLE – WAITLIST CLOSED – BLACKOUT DATE FOR cc (1V)
• Error:  FLIGHT DATA NOT AVAILABILE – VERIFY YOUR ENTRY (1V)

22. Scenario:  Restricted codeshare flight.

• Error:  *UNABLE – CODESHARE FLIGHT* (1G)

23. Scenario:  Flight departed.

• Error:  *UNABLE – FLIGHT ALREADY DEPARTED xxx* (1G)
• Error:  FLT DPTD (1V)

24. Scenario:  Flight cancelled.

• Error:  CK FLT NBR aannnn ccc ccc * (1V)
• Error:  NOOP (1V)
• Error:  FLIGHT CANCELLED (1V)

25. Scenario:  Flight closed.

• Error:  *UNABLE – WAITLIST CLOSED xxx TO xxx* (1G)
• Error:  *UNABLE – WAITLIST CLOSED* (1G and 1V)
• Error:  *FLIGHT TOO CLOSE TO DEPARTURE* (1G)
• Error:  0 AVAIL/WL OPEN aannnn ccc ccc * (1V)

26. Scenario:  Restricted flight or itinerary.

• Error:  RESTRICTED (1G and 1V)
• Error:  FLIGHT UNDER AIRPORT CONTROL (1G)
• Error:  UNABLE TO SELL FLIGHT – CONTACT CARRIER (1G)
• Error:  *UNABLE – MULTIPLE TRAFFIC RESTRICTIONS APPLY* (1G)
• Error:  RESTRICTED – TOD PRESENT (1G)
• Error:  FLIGHT NOT OPERATING DUE TO OPERATIONAL CONDITION (1G)
• Error:  NO BOARDING THIS CITY (1G)
• Error:  SIMULTANEOUS BOOKING FILE UPDATE (1G)
• Error:  *UNABLE – TOO MANY CONNECTIONS FOR VENDOR* (1G)
• Error:  *SELL RESTRICTED* (1G)

27. Scenario:  Attempting a sell request on a shuttle flight.

• Error:  SHUTTLE FLIGHT – RESERVATION NOT PERMITTED – ENTER AS OPEN (1G and 1V)

28. Scenario:  Insufficient number of seats for that journey.

• Error:  *UNABLE - INSUFFICIENT SEATS ccc TO ccc* (1G)

29. Scenario:  Sell of partial journey.

• Error:  SELL OF COMPLETE TRAVEL OPTIONS REQUIRED (1G and 1V)

30. Scenario:  Attempted a sell to a restricted country.

• Error:  BOOKING FOR CUBA TRAVEL MUST BE AUTHORISED BY U.S. LAW (1G)

31. Scenario:  Embargoed city.

• Error:  UNABLE TO SELL – EMBARGOED CITY xxx (1G and 1V)
• Error:  UNABLE TO SELL – USER EMBARGOED CITY xxx (1G and 1V)

32. Scenario:  Embargoed vendor.

• Error:  UNABLE TO SELL – EMBARGOED VENDOR xxx (1G and 1V)
• Error:  UNABLE TO SELL – USER EMBARGOED VENDOR xxx (1G and 1V)

33. Scenario:  Selling out of date range.

• Error:  DATE BEYOND GALILEO SYSTEM RANGE (1G)
• Error:  DATE BEYOND GALILEO SYSTEM RANGE – ENTER AS OPEN IF REQUIRED (1G)

34. Scenario:  Link to the vendor is down.

• Error:  *UNABLE – FLIGHT ON REQUEST* (1G)
• Error:  *SECURED SELL NOT AVAILABLE* (1G)
• Error:  LINK BUSY – RETRY IN n MINUTES * (1V)
• Error:  VENDOR LINK NOT AVAILABLE (1V)

35. Scenario:  Sell request of carrier that does not have an agreement or a free-sale agreement.

• Error:  NO SELL AGREEMENT (1G)
• Error:  UNABLE – NO SELLING AGREEMENT – ENTER AS AK/AN/AL (1G)
• Error:  NO FREESALE AGREEMENT FOR THIS CARRIER (1G)

36. Scenario:  Sell request of carrier that has a schedule level agreement.

• Error:  SCHEDULE LEVEL AGREEMENT (1G)
• Error:  SCHEDULE LEVEL AGREEMENT – ENTER AS AK/AN/AL (1G)

37.  Scenario:  Input timings exist in the sell request.

• Warning:  *SYSTEM TIMES USED* (1G)

38. Scenario:  Exceeds quote for class.

• Warning:  EXCEEDS SALES QUOTA LEVEL WILL REQUEST FROM AIRLINE (1G)

39. Scenario:  More than 9 seats requested in sell request.

• Warning:  ENTER G/NAME – GROUP BOOKING REQUIRED (1G)

Flight Information Messages: 

Note:  Those with * before and after the message are directly from the vendor.

OPERATED BY AFFILIATED CARRIER (1G)

NOTE WAITLIST ONLY (1G)

*NOTE WAITLIST ONLY xxx TO xxx* (1G)

ONLINE CONNECTING TRAFFIC ONLY (1G)

SYSTEM CITY CODE USED (1G)

*DESIGNATED NON-SMOKING SERVICE* (1G)

*NOTE NEW WORLD TRAVELLERS PLUS PRODUCT* (1G)

*CHANGE OF GAUGE FLIGHT* (1G)

OPERATED BY cc (1G)

*OPERATED BY cc nnn* (1G)

DEPARTS xxx TERMINAL n – ARRIVES xxx TERMINAL n (1G)

*CHANGE OF GAUGE FLIGHT* (1G)

*PLEASE OFFER SPECIFIC SEAT ASSIGMENT* (1G)

VALID FOR INTL ONLINE STOP/CONNECTIONS ONLY (1G)

*NON-SMOKING FLIGHT ADVISE PAX xxxxx TRAFFIC* (1G)

*NAME CHANGE RESTRICTIONS MAY APPLY IN M CABIN* (1G)

*FLIGHT ELIGIBLE FOR ELECTRONIC TICKET* (1G)

*NO SMOKING FLIGHT* (1G)

*INTERNATIONAL ONLINE CONNECTING OR STOPOVER TRAFFIC ONLY* (1G)

Follow-on requests:

There are no required follow-on requests.

Section 3: Tables

Request (Input) Tags  

Response (Output) Tags

Related Samples

PNRBFManagement_26 _s1

PNRBFManagement_26 _s2

PNRBFManagement_26 _s90

PNRBFManagement_26 _s109

PNRBFManagement_26 _s110

PNRBFManagement_26 _s126