Introduction

In version 1029 of DaVinci it is possible to automatically import tickets to existing bookings/services.
For the automatic import the Bewotec Task-Scheduler is needed.
In case automatic import was successfully done, the imported files are moved from import-list to a history-list
In case automatic import was not successfully done, the files are moved from import-list to an error-list.
Workflow-Requirements:
The automatic import requires that a PNR without ticket-information is existing in an existing DaVinci-Booking/Service.
That means a PNR without tickets has to be added to the according service of a booking.
This is necessary as the automatic import checks the filekey of a PNR and identifies the according booking/service with the filekey to add the ticket.
Additionally when using the automatic import it is not possible to add more than one different filkey to a service.

Anker
_Toc106681428 _Toc106681428

Workflow

1. Activate the automatic import for DaVinci.

In Menu: Settings > Settings, Section: CRS > Various

NOTE: If this flag is activated Genesis will only allow to import ONE PNR/Filekey into ONE service. This is necessary to guarantee a definite identification for the ticket that will be imported afterwards. Depending on the unique File-Key the ticket will identify the booking/service to which it has to be imported. This requires the existence of only ONE PNR/Filekey in ONE service.If the setting is not activated, Genesis has no restriction for the number of imported PNRs into a service - – it will work the usual way as it always did.

1. Create folders for the Error-List & History-List.

...

• "File Error List": declare a path here.  Tickets that caused errors during automatic import will be moved into the specified folder
• "File History": declare path here  Tickets that have been correctly imported will be moved into the specified folder
• "Ticket prices": setting to control the price-handling during automatic import
  • "No ticket prices as sales prices": this will cause the import to not import any prices from the ticket into the according service
  • "Ticket price will overwrite sales prices": this will cause the import to overwrite existing sales-prices of the according service
  • "Ticket price will be added to sales prices": this will cause the import to add ticket-prices to existing sales-prices of the service

NOTE:As soon as a path is declared for the Error-List and/or the History-List the view of the already existing PNR-List (Menu: Bookings > PNR-List) will change.

Three Radio-Buttons are appearing now.

...

Setup of Scheduler-Task for the automatic import is similar to the setup of e.g. Batch-Prints (except for the XML-File that is used for prints - – this is not required).
Please refer to the Setup-Description of GenVas-Scheduler

A new item is existing for the ticket-import in task-llist of scheduler.

...

In case the automatic import can not be done correctly, the PNR needs to be moved from import-folder to Error-List.
This is only valid for "real" errors.
In case PNRs (with or without tickets) can not be imported because an according filekey is not yet existing in the database, these files should not be moved to the Error-List.These files should simply be untouched and remain in import-folder.

Anker
_Toc106681429 _Toc106681429

Functional Example

1. Manual import of PNR via Genesis without ticket into existing service of a booking

...