Task: Flight Availability Return More Flights

The Flight Availability Return More Flights is a follow-up task that searches for additional flight availability.

Section 1: Short Answer

Transaction name: 

AirAvailability_17

Can this task be performed in a sessionless environment?

For General Availability and General Timetable, this task can be performed in both a sessioned and a sessionless environment. However, for Carrier Specific Display, this task can only be performed in a sessioned environment.

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

The request and response are identical on both the Apollo and Galileo systems.

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

None.

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

None.

Section 2: Detailed Description

Request:

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

This task uses the selection data in the original request.

NOTE: This follow-up task may be preceded by a general availability request, a general timetable request, or a carrier specific request.

Prerequisite tasks:

An Availability or timetable request must precede this task.

Expected response:

For a general availability follow-up, the responses that may be returned for this request include:

•  <BICAvail> 
•  <FltAvailStatus> 
•  <AvailSummary> 
•  <AvailFlt> 
•  <MoreToken> 
•  <AvailText> 
•  <TSAirVPrefs> 

For a follow-up request for a carrier specific request, the responses returned include:

•  <BICAvail> 
•  <FltAvailStatus> 
•  <AvailSummary> 
•  <AvailFlt> 
•  <MoreToken> 
•  <AvailText> 

For a follow-up request for a general timetable request, the responses returned include:

• <AvailSummary>
• <AvailFlt>
• <MoreToken>

Note: If the AAFI <AvailFlt> / <GenTrafRestriction> element is returned in the 1001 <AirAvail> response, see the Flight Item General Traffic Restriction Codes page.

Error and warning responses:

<AirVPrefs>, an optional air availability request tag, provides the ability to include or exclude air vendors via the array <AirVAry>. <AirVAry> may contain up to 24 <AirVInfo> items. Including more than 24 <AirVInfo> items results in a host error.

1. Unknown availability type
2. No. in party is not numeric
3. Class pref is not 'F', 'C', 'Y'
4. Date is not in YYYMMDD
5. Board is not alpha
6. Off is not alpha
7. Time is not numeric
8. Time modifier not 'A' or 'D'
9. Flight type is not 'N', 'D', 'C' or ' '
10. Airline include not 'I' or 'E'
11. Airline preference count not 0-6
12. Airline preferences not alphanumeric
13. Midpoint include not 'I' or 'E'
14. Midpoint preference count not 0-3
15. Midpoint preferences not alpha
16. Specific flight number not numeric
17. Specific connection indicator not y or n  
18. Bad more availability token
19. General system error
20. No more later flights
21. No displayable flights
22. No city-pair data exists
23. Carrier code not in OGI
24. No link availability for this carrier
25. Date outside system range
26. This carrier link is not operating  
27. Check city-pair requested
28. No more earlier flights
29. Connections being built- retry later 
30. Unable - refresh link availability  
31. Specific flight not found
32. Unauthorized avail display mode
33. Specific legs are non-continuous
34. Nip for specific flight not met
35. Invalid class specified
36. Carrier preference not equal to 1
37. Flight departed
38. Flight cancelled
39. Flight boarding
40. Carrier not available
41. Invalid flight number
42. No direct service between cities
43. Flight not operating
44. Invalid search window start time
45. Invalid search window end time
46. Invalid max journey time
47. Error getting Travel Screen prefs
48. Midpoint/flight type conflict
49. Unsupported input version
50. Travel Screen prefs relaxed
51. Travel Screen prefs relaxed and no more later flights
52. Flight type modifier not 'E', 'U',' '
53. Relax carrier prefs not 'Y' or 'N'  
54. KLR not minimum length
55. Apply business rules indicator not 'A' or ' ‘
56. Multi-airport city indicator not 'Y', 'N', or ' '
57. Travel Screen indicator not 'Y', 'N', or ' '
58. Carrier pref must be included 'I' for carrier specific display, no 'E'    
59. Can't relax carrier preference - CSD
60. Vendor translator error - APO links 
61. Invalid frequency
62. Adequate solutions indicator not 'Y' or 'N'
63. Flight category indicator not 'Y' or 'N'
64. Multiple availability types present  
65. AACP KLR was not followed by AAC1KLR
66. Invalid flight suffix
67. Invalid requested number of flights 
68. Invalid array item size
69. AAMP KLR was not followed by AAM1 KLR
70. Invalid midpoint routing indicator  
71. Invalid similar classes indicator   
72. Invalid sequencing modifier         
73. Business rules apply must be set when connections present
74. Invalid sector number
75. Invalid flight number
76. Invalid flight range
77. Carrier is not a CSD participant    
78. Multiple alliance codes not allowed 
79. Invalid connection specified in flight specific availability request
80. Invalid number of legs specified on connection
81. Invalid max journey time
82. Class of service not offered
83. Market not operated by carrier 
84. Maximum display lines reached  
85. Invalid schedule level carrier indicator
86. At least one flight category must be selected
87. Travel restrictions exist at board point
88. Travel restrictions exist at off point
89. Travel restrictions exist at requested mid point
90. Travel restrictions exist for requested vendor
91. KLR exceeds maximum length  
92. Invalid request KLRs for proc
93. Invalid class type with other input
94. Market operated, no flights returned
95. Class of service not available
96. No more classes exist
97. Invalid adequate solutions indicator
98. Invalid timetable connections indicator
99. Option valid for participating airlines only
100. Invalid exclude trains indicator

Follow-on requests:

This follow-up task may be preceded by a general availability request. a general timetable request, or a carrier-specific request. An additional request for more flights would also be possible.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

AirAvailability_17_s5

AirAvailability_17_s9

AirAvailability_17_s11

AirAvailability_17_s15