pmsXchange v2 Upcoming Changes

Please check this page regularly for upcoming functionality and feature updates to pmsXchange v2.

To be removed / modified / added to the specification.

Error Handling

Release Date: 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.

What's happening now?

For the following error scenarios, wherein when OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from PMS provider is not processed successfully, pmsXchange 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.

Error Scenarios (Error Type = 3) -

  • Room Type not mapped
  • Channel Code not mapped

Error Type

Error Code

Error Reason

Error Message

3

249

Invalid Rate Code

Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’

3

402

Invalid Room Code

Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’

3

783

Room or Rate not found

Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’

3

n/a

Booking Agent Mapping missing

Booking agent mapping missing for HotelCode 'XXXX' and BookingAgentCode 'XXXX' and InvTypeCode 'XXXX'


What's going to change?

For the following error scenarios, wherein the content of a OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from a PMS provider is not processed successfully, either partially or in it's entirety, pmsXchange will respond back with a success RS message with no details of the error:

  • Invalid Rate Code
  • Invalid Room Code
  • Room or Rate not found
  • Booking Agent Mapping missing

Other error types, such as authentication or missing required fields, will continue to return an error response as we do today.