This task provides a display of an air segment’s seat map.
Note: Seat maps provide a map of currently available seats, but do not allow the seat to be reserved. To assign a selected seat, the segment must be booked using the PNRBFManagement transaction.
Transaction Name:
SeatMap_6
Can any other transaction perform this same task?
No other transaction can perform this task.
Can this task be performed in a sessionless environment?
Yes.
Are the request and response identical on both the Apollo and Galileo systems?
No. The SeatMap_6 transaction is only available on the Galileo (1G) CRS. Apollo (1V) CRS users must still use SeatMap_5_0.
Industry-specific knowledge required to understand this task.
To request a seat map, a flight needs to exist in the booking, and flight segment information must be provided..
Special limits or distinct restrictions to the input data.
The maximum time limit for seating availability for a direct link from the vendor is 362 days. For a non-direct link availability from the host, the maximum time limits is 330 days. However, the actual time limits vary by vendor.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
Required Data:
SMO1 <AirRailSegReq>
- <Vnd>
- <FltNum>
- <BIC>
- <Dt>
- <StartAirp>
- <EndAirp>
- <NumParty>
Optional Data:
SM02 <NameFQTVReq>
- <FName>
- <LName>
- <FFNum>
- <FFVnd>
Prerequisite tasks:
A flight segment needs to exist in the booking.
Expected response:
See Response Table in Section 3.
Error and warning responses:
Error responses are returned in the <Err> sub-element of the <ErrText> element. The status code field is blank and no error message is provided. In the following scenarios, errors or warnings for the Galileo system (1G) are blue.
1. Scenario: Processing Error
2. Scenario: Refresh Link Availability
3. Scenario: Invalid Flight Number (e.g., MMMM)
4. Scenario: Incorrect Flight Number (e.g., one that doesn’t exist for that carrier)
5. Scenario: Invalid Class Code (e.g., one that doesn’t exist for that carrier)
6. Scenario: Invalid Date
7. Scenario: Invalid Board Point
8. Scenario: Invalid Off Point
9. Scenario: Seat Map Function Not Available for this Class or Airline
Note: Numerous additional error messages exist:
If authority is given, a more complete list of error messages can be viewed on Galileo 1G platform with the terminal entry: OV*STSSEATING.
Follow-on requests:
Seat request can be used as a follow-on entry from the seat map display.
<SeatMapMods> |
Terminal Equivalents: |
Apollo 9V/… |
Galileo SA*… or SM*… |
Ordering |
KLR |
Min/Max |
XML Tag |
|
SM01 |
1 – 1 |
<AirRailSegReq> |
|
SM02 |
0 – 99 |
<NameFQTVReq> |
<SeatMap> |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
SM04 |
1 – 1 |
<SegDetails> |
|
SM05 |
0 – 3 |
<AirConfigDetails> |
|
SM06 |
0 – Unlimited |
<AirRowDetails> |
|
SM07 |
0 – Unlimited |
<AirSeatDetails> |