...
Error Handling
Release Date: TBC Ongoing
pmsXchange is migrating from the current legacy system to a microservices based new world architecture hosted in AWS. This pmsXchange internal upgradation comes with a set of advantages in terms of performance, scalability, robustness, faster development times, security and flexibility. This document lists the changes related to pmsXchange migration which will impact the PMS partners and an account of how some existing functionalities would behave in the new world.
...
For the following error scenarios, wherein when OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from PMS provider is not processed successfully, pmsXchange responds would fail the message in it's entirety and respond back with a failure RS message which has the details of the error. P.S. refer Notes for the full list of error codes supported by pmsXchange.
...
For the following error scenarios, wherein when the content of a OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from a PMS provider is not processed successfully, PmsXchange would still either partially or in it's entirety, pmsXchange will respond back with a success RS message with no details of the error.Error Scenarios -:
- Invalid Rate Code
- Invalid Room Code
- Room or Rate not found
- Booking Agent Mapping missing
However, pmsXchange will send the details of the error(s) via an automated email to the partner PMS and affected hotels. Details are as follows -
- An email would be generated twice a day at 8.00 am & 4.00 pm (timezone of the PMS partner)
Notes
...
Error Code
...
Error Reason
...
Error Message
...
245
...
Invalid Confirmation Number
...
Could not find Notifications to confirm with notification id XXXX
...
392
...
Invalid Hotel Code
...
Hotel with HotelCode XXXX does not exist
...
375
...
Hotel not Active
...
Hotel with HotelCode XXXX is not enabled for inventory updates
...
249
...
Invalid Rate Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
402
...
Invalid Room Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
783
...
Room or Rate not found
...
No room exists with InvTypeCode XXXX and RatePlanCode XXXX for hotelier XXXX
...
448
...
System error
...
450
...
Unable to process
...
Each RatePlan must have a unique name
...
Description cannot be more than 512 characters long
...
Other error types, such as authentication or missing required fields, will continue to return an error response as we do today.