eRes Amendments to itineraries and the effect on NebulaPMS

eRes Amendments to itineraries and the effect on NebulaPMS

  1. Any amendment message that is sent to eRes from the channels, such as Siteminder, will trigger an increment to the original reservation/confirmation number in the back-end of the database.
  1. So for example reservation #200 would be created on eRes and download as normal to NebulaPMS. When Siteminder amended the itinerary from a 1 night stay to a 2 night stay this change would cause the original itinerary to be cancelled and a new itinerary created for reservation #200-1.
  1. The user would not see this increment but because of the interface logic between eRes and NebulaPMS this is how the system processes changes made to booking itineraries.
  1. That is why the reservation shows the original cancelled itinerary along with the new itinerary block.