This task allows the user to add new seats or change or delete existing seats in a PNR/BF.
Transaction Name:
PNRBFManagement_53
Can this task be performed in a sessionless environment?
This task cannot be performed in a sessionless environment unless the Seat Processing task is combined with the other tasks that create a PNR/BF. The minimum necessary tasks include PNR/BF Maintenance for Primary Fields, Air Segment Sell via Direct Sell, and Finish Active PNR/BF.
Are the request and response identical on both the Apollo and Galileo systems? If not, describe the differences.
Air Seat Assignment is the same for Apollo (1V) and Galileo (1G).
For Rail Seat Assignment, Galileo (1G) CRS users can use PNRBFManagement_25 and above. Rail Seat Assignment is not available on Apollo.
Industry-specific knowledge required to understand this task.
To request a seat, a flight or rail segment needs to exist in the booking.
Special limits or distinct restrictions to the input data.
Seats cannot be added to a PNR/BF until there is at least one Name and one Air Segment present in the PNR/BF.
The maximum time limit for seating for a direct link from the vendor is 362 days. For a non-direct link availability from the CRS, 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.
For Seat requests, <SeatSellMods> (3030 6.0) is required. The type of request dictates the records sent.
Each request has a specified layout. Details of all the various layouts are in the request documentation.
NOTE: The request element must match the type of segment. For example:
Prerequisite tasks:
For Seat data to be changed or deleted, or for Seat data to be added to an existing PNR/BF, the PNR/BF must first be retrieved. For information on this see the Task PNR Retrieve documentation.
A seat map for the flight, if available, can be requested using the SeatMap_5_0 for Apollo (1V) CRS or SeatMap_6 for Galileo (1G) CRS. However, the SeatMap transaction is a stand-alone transaction, and is not a required prerequisite to seat assignment.
Expected response:
The response from a Seat request is always <SeatSell>. A matching response for each request (if multiple types of modifications are requested) are returned. Each response contains the associated request number (from the <SeatSellMods>) and a status for the response. Based on the type of request and the status of the response, additional data may also be returned in the <SeatSell>.
NOTE: The response is based on the type of request segment:
Error and warning responses:
The following are the possible status returns for the <SeatSell>. Not all status returns apply to all types of requests.
00 Modify was successful and flight/seat information follows
01 No segment matching input in PNR/BF
02 Cancel/modify request, but no seats this segment
03 Cancel request failed
04 Seat modify general error
05 Seat modify failed due to new seats not available
06 General seat request error
07 System error occurred
08 Seat request date is out of range
09 Requested seats not available
10 Generic seating no supported on this airline
11 Invalid seat number
12 Invalid seat characteristic
13 No seating this flight
14 Seat data already exists
15 General error occurred
16 Check passenger number
17 Codeshare Flight Seat request stored for this carrier
Note: This list is not complete. Numerous additional error messages
exist. If authority is given, a more complete list of error messages can be
viewed on Galileo (1G CRS) platform with the terminal entry: OV*STSSEATING
Follow-on requests:
To store the requested seat assignment, review the PNR/BF, and submit an <EndTransactionMods> to finish the process.
|
<SeatSellMods> |
Terminal Equivalents: |
Apollo |
Galileo __S., S.@____ |
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||||
|
1 |
SA01 |
1 99 |
<AirRailSegReq> |
||||
|
2 |
SA02 |
0 99 |
<AirRailGenSeatReq> |
||||
|
2 |
SA03 |
0 99 |
<AirSpecificSeatReq> |
||||
|
2 |
SA04 |
0 99 |
<RailSpecificSeatReq> |
||||
|
<SeatSell> |
|
|
||||
|
Ordering |
KLR |
Min/Max |
XML Tag |
||
|
|
SA05 |
1 99 |
<AirRailSegDetails> |
||
|
|
SA06 |
0 99 |
<AirSeatRsvnDetails> |
||
|
|
SA07 |
0 99 |
<RailSeatRsvnDetails> |
||