Skip to main content

Error Handling

The below table illustrates the current error handling for EnhancedHotelBookRQ:

Location Scenario Error Message
Schema RQ Customer request schema validation has failed, customer provided an invalid input. SOAP Fault in response with schema validation details
Booking key retrieval error Booking key cannot be retrieved or decoded EnhancedHotelBookRS with Business error:
Unable to read Enterprise Shared Cache data - no data for provided key
Unable to read Enterprise Shared Cache data - data content is empty for provided key
Unable to read rateKey - wrong data format returned by Shared Cache
Unable to decode rateKey
Unable to decode rateKey - not supported type of rate key
Unable to use rateKey data - no XXX or empty
Unable to use rateKey data - XXX, "value should be higher then 0
Main business error Main error returned by the SP application. Will be followed by system specific errors generated by the application or the content providers. EnhancedHotelBookRS with Business error:
Unable to perform hotel booking step. See below messages for details
HotelProperty DescriptionLLSRQ GDS as legacy only. Low level error coming from the provider. EnhancedHotelBookRS with Provider error:
Unable to perform HotelPropertyDescriptionLLSRQ call. See below messages for details
HotelPropertyDescriptionLLSRQ Multiple calls GDS as legacy only. Unable to find matching rate within any of the responses from the low-level API. EnhancedHotelBookRS with Business error:
Unable to find a matching room rate code within HotelPropertyDescriptionLLSRQ response
HotelPropertyDescriptionLLSRQ GDS as legacy only. Shopped rate was found but its price does not match the amount decoded from the booking key. EnhancedHotelBookRS with Business error:
The total booking price does not match price returned during shopping
HotelRateDescriptionLLSRQ GDS as legacy only. Low level error coming from the provider. EnhancedHotelBookRS with Provider error:
Unable to perform HotelRateDescriptionLLSRQ call. See below messages for details
OTA_HotelResLLSRQ GDS as legacy only. Low level error coming from the provider. EnhancedHotelBookRS with Provider error:
Unable to perform OTA_HotelResLLSRQ call. See below messages for details
eg.
‡INVALID CARD NUMBER
‡INVLD‡ DEPOSIT NOT ACCEPTED BY THIS PROPERTY.
‡INVLD‡ CREDIT CARD TYPE NOT ACCEPTED BY PROP
OTA_HotelResLLSRQ GDS as legacy only. Low level service returned a success response but with an empty payload. EnhancedHotelBookRS with Provider error:
Hotel segment created successfully but no booking details were retrieved from the provider. Please redisplay the reservation to validate the addition of a new hotel segment.
UpdateReservationRQ All scenarios. Required missing data. EnhancedHotelBookRS with Provider error:
Unable to perform hotel booking step. See below messages for details.
eg.
Agency Address is Required
TravelItineraryReadRQ All scenarios. Final segment status unsuccessful (either UC or NO) EnhancedHotelBookRS with Business error:
Hotel booking segment status is unconfirmed. Please retry the transaction
TravelItineraryReadRQ All scenarios. Confirmation number from the hotel not present EnhancedHotelBookRS with Business warning:
Hotel booking succeeded but was not confirmed by the property. No confirmation number present
Payment card referencing The referenced payment card does not contain full card holder name Unable to reference the payment card. The stored card requires full card holder name.
Payment card referencing The referenced form of payment is not a payment card The referenced form of payment must be a payment card. No other forms of payment can be referenced.
Payment card referencing The Strong Customer Authentication data identifier does not exist "Unable to reference the payment card. ...FormOfPaymentReference/@strongCustomerAuthenticationRef does not match any stored Strong Customer Authentication".