Task: Rail 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_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. A Rail Seat Map request is only available on the Galileo (1G) CRS.

Industry-specific knowledge required to understand this task.

To request a seat map, rail 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.

Section 2: Detailed Description

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:

Rail detail needs to be supplied for the seat map. See request data in above paragraph.

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

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

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)

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)

6.       Scenario:  Invalid Date

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

7.       Scenario:  Invalid Board Point

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

8.       Scenario:  Invalid Off Point

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

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

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

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
• 201 No Seating This Class
• 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_6_s3

SeatMap_6_s4

SeatMap_6_s5