Overview

The Issue Air Ticket (AirTicketLLSRQ) service is used to issue air tickets. These can be paper, electronic, or paper tickets for airline use only.

Common errors

TEXT	RESOLUTION
ERR.SWS.CLIENT.VALIDATION_FAILED	Is returned when the request of the selected API was not constructed in a proper way.
VALIDATING CARRIER XX DOES NOT HAVE AGREEMENT WITH YY-0322	There is no ticketing agreement on the file between the carriers in the PNR and the carrier selected as the validating carrier.
NEED VAL CARRIER-0166	The error is due to the fact that there is no validating carrier nor in the PQ, nor in the ticketing entry. For the ticket to be issued, it is necessary to have a validating carrier added in the format
AUTH CARRIER INVLD-0166	This error is caused by the lack of authorized carriers listed under the issuing PCC
MANUAL APPROVAL NOT ALLOWED WITH DIRECT FULFILLMENT	This error occurs when attempting to issue an EMD for UA Plus Seats and you append a credit card manual approval code to the Air Extras fulfillment entry. Manual approval code is not allowed
VERIFY SELECTED AE ITEMS - NO ELECTRONIC TICKET ASSIGNED	Tickets are not assigned to the EMD
INVALID PQ NUMBER-0133Â	Invalid PQ, while you were trying to issue the ticket. In this case, what you have to do is try to display the PNR again and verify the correct PQ
FOP RESTRICTED TO CREDIT TYPE ONLY-0076	This error is returned because your PCC is not allowed to issue tickets in a different form of payment than Credit Card
NO COMBINABLE FARES FOR CLASS USED	Fare not available in ticketing PCC
NEED AIRLINE PNR LOCATOR - VERIFY AND ENTER IN SEGMENT	is due to the segments of the booking are missing the record locator. Please note the booking cannot be issued without the record locator
PRICE QUOTE EXPIRED-PLEASE REPRICE OR REENTER TO PROCEED-149	PQ’s are only valid within the same day they were stored

FAQ

What should I know before using the service? Keep in mind that the PCC where you are trying to issue needs to have AUTOVAL ON active in the TJR, also you need to have the plate of the validating carrier added in your tables (Authorized to issue)

Printers are mandatory; you can use the service DesignatePrinterLLSRQ or the Enhanced Air TicketRQ to designated the printers in a single call. https://developer.sabre.com/docs/soap_apis/air/fulfill/enhanced_air_ticket.

Can I issue in a different currency? This option is only active for BSP countries, you also need to be aware of the following:

-Verify if your country allows ticketing in alternate currency W/CURR*

-Display the agency TJR to verify the TJR option for TICKETING IN ALTERNATE CURRENCY ALLOWED  is activated:
W/ALT¥*

TICKETING IN ALTERNATE CURRENCY ALLOWED

- If TICKETING IN ALTERNATE CURRENCY ALLOWED is not activated - and the country allows it, you can activate the option following the steps in https://central.sabre.com/s/article/tjr---ticketing-in-alternate-currency

- Specify the currency at the moment of pricing because you cannot do ticketing.

 

 

What should I do if I receive the following error:

PNR HAS BEEN UPDATED - IGN AND RETRY / SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR

The PNR received modifications while the PNR was displayed in the work area and the system does not allow any further modifications. This means that either there is a system update or an incoming message from the carrier that has come in at the same time the ticketing is being sent

Please keep in mind that you always need to End the transaction (EnhancedEndTransactionRQ) after each ticketing entry to avoid this kind of issue. Another option is to use the service Enhanced Air Ticket https://developer.sabre.com/docs/soap_apis/air/fulfill/enhanced_air_ticket

if you receive the error you can follow these steps:

1)Ignore and retrieve the PNR again

2)Display the PNR and verify if you see the ticket

In this case, after a few minutes, you will not see the ticket. Look in the audit trail report (DQB) to see if the ticket is there, if it is, the ticket has been issued. However, there are carriers that won’t be able to see the ticket ''linked''(they might not receive the TKNE messages). In such situations you can:

a) Contact the carrier to see if they can see the ticket, if they do, then it worked as intended.

b) Void the ticket and issue it again and making sure that End Transaction is made after each ticketing transaction

c) If the ticket cannot be voided, they will need to contact the carrier for alternatives if they cannot see it. The most common solution would be for them to ask for a waiver and proceed to do an even exchange so the ticket appears under *T

Here you can find more information about it  https://central.sabre.com/s/article/simultaneous-changes-to-pnr---use-ir-to-ignore-and-retrieve-pnr