Sabre Segment Status Code: The status code associated to segments in an itinerary can be grouped into the following 3 categories: Action Code, Status Code, and Reply Code.
Besides travel agents, airlines may make changes to the PNR. These will be reflected in the Reply Code of the segment concerned. If an airline has taken over the ownership of a PNR, changes made in the airline system will not be reflected in the Sabre system. This is one of the causes of the PNR non-synchronization.
Sabre Segment Status Code
Sabre Segment Action Code
Explanation: Used when selling segment.
Commonly used codes | DESCRIPTION |
---|---|
NN | Need segment |
LL | Waitlist segment |
DS | Desires Segment – used for open dated segment |
GK | Passive Confirmed segment |
GL | Passive Waitlisted segment |
Sabre Segment Status Code
Explanation: Used by system to reflect the current status of the segment.
Commonly used codes | DESCRIPTION |
---|---|
SS | Seat Sold |
HK | Holding Confirmed |
LL | Seat Waitlisted |
HL | Holding Waitlist |
US | Unable to accept sale, has been waitlisted |
UU | Unable to confirm, has been waitlisted |
PN | Pending Need |
HN | Holding Need |
UC | Unable to confirm or waitlist |
UN | Unable, flight not operating |
Sabre Segment Reply Code
Explanation: Used by airlines advising changes to the segment.
Commonly used codes | DESCRIPTION |
---|---|
KK | Carrier confirmed the requested segment |
KL | Confirmed from waitlist |
TK | Schedule change for confirmed segment showing new schedule |
TL | Schedule change for waitlisted segment |
SC | Schedule change – applicable only for AA (American Airlines) |
HX | Segment was cancelled by carrier. |
NO | No action was taken on the segment. Some airlines use NO to inform that a specific segment has been cancelled in the airline system. |
Example:
![](https://sabrecommand.com/wp-content/uploads/2023/11/image-18-1024x170.png)