Task: Seat Map Request

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.

Section 1: Short Answer

Transaction Name:

SeatMap_5_0

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.

Industry-specific knowledge required to understand this task.

To request a seat map, a flight needs to exist in the booking.

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.

Section 2: Detailed Description

Request:

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

Required Data:

• <AirV>
• <FltNum>
• <OpSuf>
• <BIC>
• <StartDt>
• <StartCity>
• <EndCity>
• <NumSeats>

Optional Data:

• <LName>
• <FreqFlierID>
• <FreqFlierNum>

Prerequisite tasks:

A flight segment needs to exist in the booking.

Expected response:

• <Status>
• <ErrMsg>
• <AirV>
• <FltNbr>
• <OpSuf>
• <BIC>
• <StartDt>
• <StartCity>
• <EndCity>
• <AircraftType>
• <Text>
• <TypeDisp>
• <SectionsAry>
• <ColLabel>
• <RowAry>
• <Num>
• <SeatsAry>
• <ColID>
• <Status>
• <AttribAry>
• <Attrib>

Error and warning responses:

Error responses are returned in the <Status> sub-element of the <SeatMap> 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 and errors for the Apollo system (1V) are green.

1.       Scenario:  Processing Error

• Return code:  50; Status code:  blank;  Error message:  n/a (1G)
• Return code:  11;  Status code:  n/a;  Proc Error:  97;  Text:  SYS ERR OCCURRED

2.       Scenario:  Refresh Link Availability

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)

3.       Scenario:  Invalid Flight Number (e.g., MMMM)

• Return code:  50; Status code:  blank;  Error message:  n/a (1G)
• Return code:  3; Status code:  blank; Error message:  n/a (1V)

4.       Scenario:  Incorrect Flight Number (e.g., one that doesn’t exist for that carrier)

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

5.       Scenario:  Invalid Class Code (e.g., one that doesn’t exist for that carrier)

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

6.       Scenario:  Invalid Date

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

7.       Scenario:  Invalid Board Point

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

8.       Scenario:  Invalid Off Point

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

9.       Scenario:  Seat Map Function Not Available for this Class or Airline

• Return code:  13; Status code:  blank;  Error message:  n/a (1G)
• Return code:  0; Status code:  03; Error message:  200 (1V)

10.   Scenario:  Invalid Number in Party

• Return code:  1; flight details:  vendor code (blank), flight number (zeroes), operational suffix (blank), class code (blank), date (zeroes), board point (blank), off point (blank), number in party (0) – (1V)

11.   Scenario:  Last Name Exists but First Name Does not Exist

• Return code:  1; flight details:  vendor code (blank), flight number (zeroes), operational suffix (blank), class code (blank), date (zeroes), board point (blank), off point (blank), number in party (0) – (1V)

Note: Numerous additional error messages exist:

• 11 Invalid Brd/Off Point
• 26 Seat Map Unavailable
• 100 Invalid BoardPoint
• 101 Invalid Offpoint
• 102 Invalid Date
• 104 Invalid Class Code
• 107 Invalid Airline Code
• 114 Invalid Flight number
• 118 Generic Default Error if error code not found
• 122 Seating Suspended or Map Unavail-Airport Check in
• 197 No Seats Available
• 200 No Seating this Flight
• 201 No Seating This Class
• 225 Seat Mp Unavail - Code share Flt
• 281 Generic Seating Only

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:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

SeatMap_5_0_1

SeatMap_5_0_2