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_7_9

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

PNRBFManagement_7_8, PNRBFBuildModify_7_7_1.

Can this task be performed in a sessionless environment?

No. 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_7_9 supports Direct Sell using flight details.

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

Not applicable.

Section 2: Detailed Description

Request:

For some carriers, the user must emulate an agency. 
 

Required Data: 
  • <Vnd>
  • <FltNum>
  • <OpSuf>
  • <Class>
  • <StartDt>
  • <StartAirp>
  • <EndAirp>
  • <Status>
  • <NumPsgrs>
  • <AvailDispType>
Optional Data: 
  • <StartTm>
  • <EndTm>
  • <DtChg>
  • <StopoverIgnoreInd>
  • <VSpec>
  • <AvailJrnyNum>

 

Prerequisite tasks:

There are no prerequisite tasks.

Expected response:

Description:  Flight data

  • <Vnd>
  • <FltNum>
  • <OpSuf>
  • <Class>
  • <StartDt>
  • <DtChg>
  • <StartAirp>
  • <EndAirp>
  • <StartTm>
  • <EndTm>
  • <Status>
  • <NumPsgrs>
  • <SellType>
  • <SellValidityPeriod>
  • <MarriageNum>
  • <SuccessInd>
  • <COG>
  • <TklessInd>
  • <FareQuoteTkIngInd>
  • <StopoverInd>
  • <AvailyBypassInd>

<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 1G and 1V are in black, 1G are in blue, and 1V are in green.

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

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

<AirSell> tag: 

  • Length
  • Record ID
  • Number of arrays
  • Delimiter character
  • Level number
  • Version number
  • <DisplaySequenceNumber>
  • <Vnd>
  • <FltNum>
  • <OpSuf>
  • <Class>
  • <StartDt>
  • <StartAirp>
  • <EndAirp>
  • <StartTm>
  • <EndTm>
  • <Status>
  • <NumPsgrs>
  • <SellType>
  • <SellValidityPeriod>
  • <MarriageNum>
  • <SuccessInd>
  • <COG>
  • <TklessInd>
  • <FareQuoteTkIgnInd>
  • <StopoverInd>
  • <AvailyBypassInd>

 

<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 1G and 1V are in black, 1G are in blue, and 1V are in green.

1.   Scenario:  System error.

2.   Scenario:  Schedule change active.

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

4.   Scenario:  Filed fares in progress.

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

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

7.   Scenario:  Itinerary contains 99 segments.

8.   Scenario:  Error with the itinerary.

9.   Scenario:  Duplicate segments exist in the itinerary.

10. Scenario:  Invalid carrier code OR flight details.

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

12. Scenario:  Invalid bucket number for UA flight.

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

14. Scenario:  Invalid class code.

15. Scenario:  Connection unavailable.

16. Scenario:  Invalid board or off points.

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

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

19.  Scenario:  Invalid timing.

20.  Scenario:  Invalid date.

21. Scenario:  Flight inhibited.

22. Scenario:  Restricted codeshare flight.

23. Scenario:  Flight departed.

24. Scenario:  Flight cancelled.

25. Scenario:  Flight closed.

26. Scenario:  Restricted flight or itinerary.

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

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

29. Scenario:  Sell of partial journey.

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

31. Scenario:  Embargoed city.

32. Scenario:  Embargoed vendor.

33. Scenario:  Selling out of date range.

34. Scenario:  Link to the vendor is down.

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

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

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

38. Scenario:  Exceeds quote for class.

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

 

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  

<AirSegSellMods>

Terminal Equivalents:

Apollo: e.g., 0

Galileo: e.g.,  0

 

 

Ordering

KLR

Min/Max

XML Tag

 

A

SQS1 1.0

1-99 (1G);

1-1 (1V)

<AirSegSell>

 

Response (Output) Tags

<AirSegSell>

 

 

Ordering

KLR

Min/Max

XML Tag

 

A

SRS1 1.0

1-99 (1G);

1-1 (1V)

<AirSell>

 

B

EROR 1.0

1-99 (1G);

1-1 (1V)

<ErrText>