Skip to main content

End Transaction

2.1.0
Air
Reservation
SOAP API
Travel Agency
Airline Carrier

Default Errors for SOAP APIs

Text Resolution
USG_AUTHENTICATION_FAILED Verify that your token credentials were set-up properly. Verify your session token is valid.
USG_AUTHENTICATION_NOT_ALLOWED Verify your token credentials are as a binary security token rather than in the request.
USG_INVALID_SECURITY_TOKEN Verify your token credentials.
USG_PASSWORD_NOTFOUND Verify the password for your token credentials.
USG_PASSWORD_CHANGE_REQUIRED Reset your password using the CREATE agent.
USG_AUTHORIZATION_FAILED Verify that your token credentials allow you to call this API. Contact your Sabre account manager to verify access.
USG_CONNECTOR_IS_BUSY

1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API.

2. Wait at least 500 milliseconds and resend the request.

USG_IS_BUSY

1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API.

2. Wait at least 500 milliseconds and resend the request.

USG_SECURITY_ICE_ERROR

1. An internal error prevented the request from being processed.

2. Wait at least 500 milliseconds and resend the request.

3. Contact Sabre Support if the error persists.

USG_INVALID_SESSION Do not attempt simultaneous usage of the same session token/session. Get a new token.
USG_RESOURCE_UNAVAILABLE

1. You have exceeded the maximum number of sessions.

2. Terminate unused active session tokens, wait at least 500 milliseconds and resend the request.

USG_RESOURCE_BLOCKED

1. Session creation blocked for the given user.

2. Contact Sabre.

USG_SERVICE_IS_BUSY

1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API.

2. Wait at least 500 milliseconds and resend the request.

USG_SERVICE_PROVIDER_ERROR Wait at least 500 milliseconds and resend the request.
USG_NO_RESPONSE_FROM_JMSRECEIVER_IN_TIME Wait at least 500 milliseconds and resend the request.
SC_SERVICE_UNAVAILABLE Wait at least 500 milliseconds and resend the request.
USG_COULD_NOT_COMPLETE_REQUEST

1. Your application may be experiencing an internal security error.

2. Wait at least 500 milliseconds and resend the request.

USG_IIOP_OBJECT_NOT_EXIST

1. Your application may be experiencing an internal security error.

2. Wait at least 500 milliseconds and resend the request.

USG_IIOP_TRANSIENT_EXCEPTION

1. Your application may be experiencing an internal security error.

2. Wait at least 500 milliseconds and resend the request.

USG_CONVERSATION_ID_REQUIRED Verify that eb:ConversationId element is in the SOAP header.
USG_INVALID_ACTION Verify the format of your SOAP envelope.
USG_INVALID_EBXML Verify required ebXML element or attribute is valid.
INVALID_VERSION

1. Verify the version number for the specified service action code.

2. Check documentation for the API to ensure you are specifying the correct version.

MISSING_VERSION

1. Include a valid version number.

2. Check documentation for the API to ensure you are specifying the correct version.

USG_SERVICE_VERSION_DEPRECATED

1. The version number for the specified service and given user is deprecated.

2. Contact your Sabre account manager.

USG_MOM_SERVICE_PROVIDER_INFRASTRUCTURE_ERROR

1. An internal error prevented the request to be processed.

2. Wait at least 500 milliseconds and resend the request.

3. Contact Sabre support if the error persists.

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's 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's 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 in order 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 don't need to specify a concrete date.