Task: Air Segment Sell via Reference Sell

Air Segment Sell allows for the selling of air segments via reference sell.

Section 1: Short Answer

Transaction Name:  

PNRBFManagement_39

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

Previous versions of PNRBFManagement, AirSegmentSell_#.

Can this task be performed in a sessionless environment?

No, this task can be performed only in a sessioned environment.

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_39 supports reference sell. The user needs to know the difference between reference sell from a general availability and sell from a carrier specific availability. 

Note:  When reference selling against a general availability, the sell is processed internally as a manual sell, which may result in manual sell type error messages, if some of the flight is data in the availability.

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

When reference selling from a carrier-specific display, the <AvailToken> element is added after each <AirSegSell> element . This record contains the Availability Token information.

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_39 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)

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 may be sold with or without an availability call being made first. 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, and origin and destination required, but may not sure of either the departure date, departure time or both. Because the actual flight might 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_39 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 segment(s) 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 needs to emulate an agency. 

Reference Sell via General Display:

Required Data:  <Vnd> <FltNum> <OpSuf> <Class> <StartDt> <StartAirp> <EndAirp> <Status> <NumPsgrs> <AvailDispType> <AvailJrnyNum>

Optional Data:  <StartTm> <EndTm> <DtChg> <StopoverIgnoreInd> <VSpec> <AvailSource>

Reference Sell via Carrier Specific Display:

Required Data:  <Vnd> <FltNum> <OpSuf> <Class> <StartDt> <StartAirp> <EndAirp> <Status> <NumPsgrs> <AvailDispType> <VSpec> <AvailJrnyNum>

Optional Data:  <StartTm> <EndTm> <DtChg> <StopoverIgnoreInd> <AvailSource>

 

Availability Status Source
The <AvailSource> should be retrieved from the AAFI <AvailFlt> element in the 1001 <AirAvail> record. This value should be added to the <AirSegSell> element in the <AirSegSellMods> request record.

Sell with Availability Token
For some carriers, the user needs to emulate an agency. The user needs to request a <VSpec> prior to making the sell request in order for the <AvailToken> tag to be generated. The <AvailToken> tag cannot function on its own but needs to be appended to an <AirSegSell> tag.

Required data: <Token>.

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:

For a reference sell, PNRBFManagement_39 requires an availability display prior to sell. This would be via AirAvailability_#.

Expected response:

Description:  Flight data.

<TextMessage> tag:  The <AirSell> tag is followed by one or 1.

Error and warning responses:

Description:  Flight data. See fields above.

In the following scenarios, errors or warnings for 1G and 1V are black, 1G are blue, 1V are green.

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

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 (eg: 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>.

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:  Sell against availability display that is old/expired.

• Error:  AVAILABILITY DISPLAY NOT PRESENT (1G)
• Error:  UNABLE – REFRESH LINKED AVAILABILITY DISPLAY (1G)
• Error:  FLIGHT NOT FOUND IN LAST AVAILABILITY DISPLAY – REFRESH AVAILABILITY (1G)
• Error:  REDISPLAY REQUIRED – TIME EXCEEDED (1V)
• Error:  ND  AVBLY DISP (1V)
• Error:  SEGMENT UNAVAILABLE – CHECK AVAILABILITY (1V)

3.   Scenario:  Attempted a reference sell when availability doesn’t exist.

• Error:  AVAILABILITY DISPLAY NOT PRESENT (1G)
• Error:  ND  AVBLY DISP (1V)

4.   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)

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

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

6.   Scenario:  Filed fares in progress

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

7.   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)

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

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

9.   Scenario:  Itinerary contains 99 segments.

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

10. Scenario:  Error with the itinerary.

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

11. Scenario:  Duplicate segments exist in the itinerary.

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

12. Scenario:  Invalid carrier code OR flight details.

• Error:  *SECURED SELL NOT AVAILABLE* (1G)
• Error:  FLIGHT NOT FOUND – CHECK FLIGHT DETAILS (1G and 1V)
• Error:  FLIGHT NOT FOUND – DEP/ARR TIMES REQUIRED (1G)
• 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)

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

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

14. Scenario:  Invalid bucket number for UA flight

• Error:  BUCKET INVALID FOR CLASS (1V)

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

• Error:  NOT IN TBL (1V)

16. Scenario:  Invalid class code

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

17. Scenario:  Connection unavailable.

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

18. Scenario:  Invalid board or off points.

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

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

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

20. 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)

21. Scenario:  Invalid timing.

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

22. 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)

23. 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)

24. Scenario:  Restricted codeshare flight.

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

25. Scenario:  Flight departed

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

26. Scenario:  Flight cancelled.

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

27. 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)

28. 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)

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

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

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

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

31. Scenario:  Sell of partial journey.

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

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

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

33. Scenario:  Embargoed city.

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

34. Scenario:  Embargoed vendor.

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

35. 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)

36. 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)

37. 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)

38. 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)

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

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

40. Scenario:  Exceeds quote for class.

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

41. 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.

For Reference Sell via Carrier Specific Display, the <AvailToken> must follow each <AirSegSell> in the request. 

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

PNRBFManagement_39_s52

PNRBFManagement_39_s104

PNRBFManagement_39_s109

PNRBFManagement_39_s110

PNRBFManagement_39_s125