GDS Message Investigation Information

Problem

Occasionally a we will require more information for a GDS reservation, in the form of finding additional GDS Messages. Below are all of the ways to Search for more information on a GDS reservation. 

Solution

Find GDS Reservation via Advanced Search

Amelia's Advanced search function, allows you to search for a reservation using information other than a Name or Reservation Number. Below are the steps to search VIA Record Locator Number: 

  1. Navigate to Operations > Reservations
  2. Once the reservations screen is open, look at the bottom right corner for the "Advanced Search" button. Click it.
  3. When searching for a reservation by Record Locator, we do not want to be mindful of the dates. The Record locator will allow the reservation to come back, without the assistance of dates. Click the "Ignore Booking Date" check box. Under "Search Type", click "Locator Number". In the blank box at the bottom of the screen, enter in the 6 digit Record Locator number. Click "Search". 
  4. If there are any existing reservations with that Locator Number, it will come up in the Reservations screen. 

Search for ALL messages associated with a specific Record Locator

In the GDS Message interface, you can view ALL messages from a specific locator using the following steps. You can use this to find out what actions have been taken on a reservation via the GDS. 

  1. Open the GDS Message interface by navigating to Operations > GDS > GDS Messaging
  2. Set the Display to "By Locator" 
  3. A box will appear labeled "Locator to Find" in this box put the 6 digit record locator number. Click "Find" 
  4. Now that we've run a quick search, lets bring back ALL messages. Set the "Type" to <All>
  5. Set the "Status" to <All>
  6. Click Find. 
  7. You should now be able to see ALL message with that locator in the GDS message interface. Be sure to search for the locator before setting the Type and Status. Otherwise you will be bringing back "All" messages of "All" types. 

Sabre Segment Status Code Meanings

Sometimes the issue with a GDS message is simply that the agent has not given the appropriate Segment Status codes. Below is a list of many of the segment status codes used within sabre and TTY messaging.

Status CodeDescriptionCurrently Supported
AFAA Advantage ticket
AKConfirmed outside Galileo system
ALWaitlisted outside Galileo system
ANRequested outside Galileo system
BKBooked with carrier
BLWaitlist segment
BNRequested outside Galileo system
CHPassive - Code share holds confirmed
CKAdvance check-in. Boarding pass issued
CSCode share sell segment
DKLink book last seat
DLDeferred waitlist
DSDesires segment
DXPassive - Broken marriage / Active-Authorized partial cancellation within a marriage
EKEMD confirmed
FSFree sale
GFFirm booking
GKGauranteed/Merged. Also used in 1V as Passive - Group confirmed
GLWaitlist with carrier
GNGroup booking
GOOption booking/mrg
HAHave requested. Airline requested one of their own segments
HDHolding confirmed; EMD required
HIHolding confirmed EMD issued (EMD can only be issued if Ticket is Issued)
HKHolds confirmed
HLHolds waitlist
HNHolds need/confirmed
HQSpace prev. request
HSCO changes
HWHave waitlisted. Airline waitlisted one of their own segments
HXCancel confirm hold
IGInvoluntary upgrade
IHInhibit status code
IKInfant no seat
INIf not holding need
ISIf not holding sell
IXIf holding cancelNo
KDIssue EMD
KKCarrier confirmed
KLWaitlist confirmed
LKPassive - Link booking - guaranteed sell
LLAdd to waitlist
MBMove reaccommodation - Pax was on standby status for flight affected
MKNon messaging Passive segment. Also used in 1V as move reaccommodation - Pax was waitlisted/moved to new fight
MLWaitlisted
MNNot available
MOManual override for car/hotel
MRRequested
NANeed alternate
NNRequesting segment
NONo action taken
NSNo show
OBOverbook
OXCancel only if requested segment is available
PAPriority waitlist-emergency travel
PBPriority waitlist
PCPriority waitlist
PDPriority waitlist
PKDiscounted passngr.
PNPending need
PSPassive
PWPriority waitlist
RRReconfirm
SBBoarded standBy
SCSchedule change
SDSchedule change/re-booking; EMD already issued. Document number must be included in the SSR
SPPassive-space protected
SQSpace request - bilateral use
SSSell segment
TKSched. chg. not AA
TLSched. chg. waitlist
TNSched. chg. ReqHld.
UCUnable conf. or wait
UNUnable - no flight
USUnable to sell
UUUnable conf. ReqWait
WKSched. chg. of cnfrm
WLNo longer waitlist
WNWas need/sched. chg.
XBSee BSG sched chg
XICancel itinerary
XKCancel seg with change
XMSegment cancelled
XXCancel segment
YGInvoluntary upgrade
YKHold cnf AL space
ZKPassive - API booking

ameliaRES GDS Message Parsing "Last Error" Error Codes

Error CodeMeaning
5001Unknown Actions/Status Code(s):
5002Locator Already Associated with reservation: ResNum
5003No Fares Found for Given Booking Code
5004Unable to find Flight Segment:
5005No Seats Available
5006No Availability for given booking code
5007Credit card Authorization failed
5008No seats allocated to the given booking code
5009Credit Card is not a valid form of payment and message has CC info attached
5010BSP is not a valid form of payment and CC information is not attached to Msg
5011Unsupported Action Was Sent to Booking Code
5012Unable to Find Original Reservation
5013Unsupported Payment Method Found On the Original Reservation (Only BSP Currently Supported) Dec 10, 2003
5014Travel has already begun on this reservation. Amelia GDS cannot make change to a reservation after a passenger has borded. Unable to change reservation.
5015No allocations exist on this flight.
5016No Segments Were Added (Probably Due to Invalid Airline Idents on the Segment Lines)
5017Not Enough Seat Availability In Public Or Agency Allocation
5018(-6026) Due to business rule settings, no edit/cancels allowed
5019(-6027) New CC payment does not match old. Res already has CC payment and new CC doesn't match that one.
5020Insufficient Credit On Account Mapped to 'On-Account-Agency'
5021Availability Check failed, either no valid fare was found OR one or more of the seat availability are no longer available
5022No infant availability
5023Reservation has multiple payment types. Amelia GDS cannot make changes to a reservation which has used multiple payment types
5024Reservation has multiple CC payments. Amelia GDS cannot make changes to a reservation which has multiple CC payments.
5025Unable to create payment. Company balance check failed in stored procedure.
5026Provided booking date from message is not valid: ### - ##
5998Error Calling GDSBookReservation: ####
5999Error Building Booking XML: ####

Source: amelia\projects\VB\GDS\AmeliaGDS\CRSSpecific\Generic\CParse.cls