The data flow of an Evolvi booking is explained in the configuration section of this documentation, this section picks up from the first point the data hits the Micros|Travel Software. The CRS Queue.
The screenshot below shows a number of Evolvi bookings in the CRS Queue.
As you can see the interface is the same as the CRS, indeed both CRS and Evolvi bookings will appear in this list. The one difference you may notice is the "Issue" Column between the Lead ticket number and the Booking reference. This column can contain any of the below booking types:
P : Preissue, a preissue is a ticket which is similar to a provisional booking, there is no ticket number in the download, nor any tickets at all for that matter.
I : Issue, an issue can override a Preissue, but it can also be the first instance of a booking in Traveller, Issues normally have tickets with them.
C : Cancellation, this will match up against a booking allready in Traveller through the EV0000 reference. Bookings will be automatically cancelled when this is downloaded.
R : Refund, as above, the matching is done through the EV0000 reference. When autopayment is enabled these will automatically be a refund produced for the corrisponding booking.
The bookings in this queue, apart from the above settings are handled in exactly the same as standard CRS downloads.
