Versions Compared

Old Version 7

changes.mady.by.user Malin Atkins

Saved on

compared with

New Version Current

changes.mady.by.user Luke Bayly

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixing no longer compatible Confluence macro

Overview

The reservation pull delivery model involves the use of 4 OTA messages in 2 request/response exchanges, both initiated by the PMS.

The reservation pull process begins with the PMS sending an OTA_ReadRQ message to PmsXchange and being returned an OTA_ResRetrieveRS. The main payload contents of the OTA_ResRetrieveRS message are HotelReservation elements which contain the details of zero or more reservations. The PMS is expected to process these and then confirm delivery by sending an OTA_NotifReportRQ message to PmsXchange. In response to this message PmsXchange will return an OTA_NotifReportRS message.


Please refer this page for an overview of the reservation delivery process (OTA_ReadRQ ↔  OTA_ResRetrieveRS & ← OTA_NotifReportRQ) - PMS Technical Architectural Diagram

Important Notes

Delivery confirmation is essential

...

As mentioned above, even reservations which are not successfully processed by the PMS must be confirmed as delivered. The OTA_NotifReportRQ structure does not allow for a mixture of successfully and erroneous reservations to be confirmed together. Successfully processed reservations must be confirmed as delivered in OTA_NotifReportRQ messages separate from those that could not be processed. Please see the use case below detailing this scenario.