Skip to main content
Error Cause Resolution
*PAC  TO VERIFY CORRECT NBR OF ACCTG LINES - THEN ET TO CONTINUE

The number of passengers in the PNR you are trying to commit does not match the number of accounting lines. 

It is a common message after you have exchanged a ticket.

1. This is a soft error (warning) which can be bypassed by sending another End Transaction API call (Passenger Details can be used as well). Please ensure that you do not specify the <Source/> element as part of your subsequent request as enabling it will get your application stuck in a loop as the same warning message will reappear. 

2. Please consider using either Passenger Details or Create Passenger Name Record (SOAP | REST) APIs in your workflow as these soft errors are handled automatically by these services.

DIRECT CONNECT MESSAGES RECEIVED - ENTER *A OR *IM

The airline you have booked sent a direct connect message back to the PNR.

This is common when selling airlines such as Frontier or Delta.

1. This is a soft error (warning) which can be bypassed by sending a Send Sabre Command API call with <HostCommand>*IM</HostCommand>. After you have sent this message you will need to send another End Transaction API call (Passenger Details can be used as well).

2. Please consider using either Passenger Details or Create Passenger Name Record (SOAP | REST) APIs in your workflow as these soft errors are handled automatically by these services.

INFANT DETAILS REQUIRED IN SSR - ENTER 3INFT/...

There is an infant in the reservation but there's no SSR (Special Service Request) element informing the airline the required infant details.

Airlines require additional details such as the infant's date of birth (to validate that the infant's age is < 2 years).

1. Call the Passenger Details API in order to add the required SSR and end the PNR.

2. If already using the Passenger Details or Create Passenger Name Record (SOAP | REST) API to build a PNR, you need to add the element in the payload request.

Note: Not very familiar with Sabre reservations? Check this.

PQ REQUIRED BEFORE END TRANSACTION

The PCC where you are creating a reservation has a configuration requiring that a Price Quote (PQ) record needs to be created in the PNR before allowing End Transaction.

1. PQ creation can be configured within the Orchestrated Air Booking (or  Create Passenger Name Record (SOAP | REST)) API. Enabling the <PriceRequestInformation Retain="true"> in the request will store the fare (PQ) in the PNR.

2. If your business workflow does not require fares to be stored in the PNR, you may want to consider contacting representatives from your organization with access to perform PCC/TJR updates to disable this requirement.

3. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team to get assistance on how to disable the "PQ required" configuration.

Note: Not very familiar with Sabre reservations? Check this.

NEED TICKETING/TIMELIMIT - USE 7 OR 8 Ticketing time limit is missing in the reservation, and this a mandatory element.

1. Call the Passenger Details API to add the ticketing time limit and end the PNR (<Ticketing TicketType="7T-A"/>).

2. If already using the Passenger Details or Create Passenger Name Record (SOAP | REST) API to build a PNR, you need to add the element in the payload request.

Note: Not very familiar with Sabre reservations? Check this.

.PASSENGER TYPE FUNCTION INACTIVE IN TJR

This response occurs when you attempt to store a passenger type code in the PNR and you do not have the "Store Passenger Type In PNR" active in your PCC/TJR.

Most likely you are performing a transaction in brand new PCC where this setting has not been enabled.

1. If representatives from your organization have access to perform PCC/TJR updates, contact them to perform a W/PT‡ON activation on the used PCC.

2. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team.

TICKET/TIMELIMIT MUST PRECEDE TRAVEL DATE-UPDATE TICKET FIELD The ticket time limit element used in the PNR needs reflects a date beyond the date of the first departure flight in the itinerary.

1. Ensure your <Ticketing TicketType/> date is configured for a date prior to the first departure flight.

2. Consider using <Ticketing TicketType="7T-A"/> if you do not need to specify a concrete date.

INCORRECT TIME LIMIT - VERIFY *PQ DATE The stored fare contains an earlier date to purchase than the date in the Ticketing Time Limit field.

Delete the price quote via DeletePriceQuoteLLSRQ and create a new one, via OTA_AirPriceLLSRQ.

In case of pricing issues, reach out to GCSCPricing.Support@sabre.com.

TIME LIMIT IS PRIOR TO CURRENT TIME - MODIFY AND REENTER The Ticketing Time limit (7TAW) field includes a past date.

Correct the Ticketing Time Limit field with the current or future date, via TravelItineraryModifyInfoLLSRQ

See Add Ticketing field in the PNR (7) for additional commands.

INCORRECT TIME LIMIT - VERIFY *PQ DATE - LAST DATE XX The retained fare contains a later Last Day To Purchase Date in the Ticket/Time Limit field than the Last Day To Purchase in the WS field.

Verify stored fare and update Ticket/Time Limit field:

1. Display the stored fare to verify the last date to purchase, via getBooking

2. Update the Ticketing/Time Limit field, via TravelItineraryModifyInfoLLSRQ.

NEED PHONE FIELD - USE 9 The Phone field is missing in the booking.

Add Phone field via PassengerDetailsRQ or TravelItineraryAddInfoLLSRQ prior to end transaction.

See Add Phone field in the PNR (9) for additional commands.

ITINERARY REQUIRED TO COMPLETE TRANSACTION The itinerary is missing in the booking.

Add a valid segment to the PNR such as an OTH segment, via PassengerDetailsRQ prior to end transaction.

See Add a miscellaneous non-air segment to a PNR (0OTH) for additional commands.

SEGMENTS NOT IN DATE ORDER - VERIFY AND REENTER At least one segment is not in a logical date order within the booked itinerary.

The most common cause of this issue is not having the Auto Segment Arrangement flag enabled on affected Pseudo City Code’s Travel Journal Record.

If you are not able to enable the flag visit Sabre Central and select Help.
Under help topics, find Other and type TJR Update in the Subject field.
When selecting a contact method Callback might be useful, since someone will reach out to you directly.

Alternatively contacting webservices.support@sabre.com might work.

Verify the itinerary and move any segments that are not in order (VI* host command) via SabreCommandLLSRQ.
Move any segments that are not in order via SabreCommandLLSRQ, for reference see Move Itinerary Segments in a PNR (/) for additional commands

NUMBER OF SEATS DOES NOT EQUAL NUMBER IN PARTY FOR SEGMENT

An issue with the seats in the booking.

In some cases, a schedule change may cause seats to be assigned twice.

1. Display the seats and determine what seats are under request, via getBooking.
2. Cancel seats by seat and segment number, via AirSeatCancelLLSRQ to correct the problem.
3. Save the changes, via EnhancedEndTransactionRQ.

Note: If you receive the response: CALL PRS CTL - CODE 00, contact the carrier directly.

PSGR NOT ELIGIBLE FOR P SEATS-CXL AND SELECT NEW SEAT Certain travelers are not eligible to select premium seats in the specified section of the aircraft. 1. Display the seats and determine what seats are under request, via getBooking.
2. Cancel the specific premium seats by seat and segment number, via AirSeatCancelLLSRQ to correct the problem.
3. Save the changes, via EnhancedEndTransactionRQ.
NEED CUSTOMER NUMBER - USE DK

The DK number (or client identification code) - which is an important field that links the invoice to the correct client during interface - is missing in the booking.


Agencies use the DK number primarily as an account reference identifier for billing purposes.

1. To add a DK number, use TravelItineraryAddInfoLLSRQ.

2. Save the changes via EnhancedEndTransactionRQ.

Note: This feature requires TJR activation on a PCC. - TJR PNR Optional Edits/Warnings - See Activate.