Introduction
The new automatic CRS import is available for existing bookings with existing flight services (internal and external). This import is matching the PNR with PNR information and ticket name of a participant in the Genesis booking file.
| Anker | ||||
|---|---|---|---|---|
|
A ticket name following GDS character set (ICAO 9303) is now generated in DaVinci and stored for each participant in the properties.
Remark:
In case of a double name with "-", a blank is set in the last name and middle name, whereas the first names are joined together.
| Anker | ||||
|---|---|---|---|---|
|
| Anker | ||||
|---|---|---|---|---|
|
As a pre-requisite for the automatic CRS import, the filekey needs to be available on the flight services in Genesis. It can be set manually on DaVinci internal flight booking codes (generating a bracket amongst all flight services which belong to the PNR). In case of external flight services, the filekey is already stored in the respective field and displayed in the properties of the service in Genesis.
...
(see Work Package 3)
33Default setting related to import of sales prices from air file to booking file
34Default setting related to import of purchase prices from airfile to booking file
37 System behaviour for creation of new booking sequence with PNR import (needs to be deactivated)
39Default setting for import of participants of PNR as participants in Genesis (needs to be deactivated)
49System behaviour for import of PNR to service where PNR has already been imported (needs to be activated)
50Default setting to import elements of one PNR to several booking files (needs to be activated for group business)
55Default service profile related to PNR import (only needed in case that purchase/sales prices shall be imported)*
*Set up of default service profile is made via Travels – Service/price profile
In the upper part of the frame, the service profile can be created which is linked to be used during PNR import in the system settings.
Additionally, it is necessary to define price profiles for purchase and sales prices in the lower part of the frame. Both a price profile for fare as well as tax need to be created each.
Example of a price template for Fare:
Example of a price template for Tax:
| Anker | ||||
|---|---|---|---|---|
|
| Anker | ||||
|---|---|---|---|---|
|
Important: Link the Price Profiles to a new Point in the Settings on the Level of Flight Interface
Set up of scheduled job
The scheduled job for ticket import is defined in GenVas Dialogue via Extras/Scheduler...Scheduler…
.
Database and Password need to be defined for the scheduled service:
-Db:DSN=DATABASENAME;UID=sa;PWD=
The configuration is defined in the dialogue which can be opened with the 
icon.
The scheduled tasks can be defined in the dialogue which can be opened with the 
icon.
In the task list dialogue, the new scheduled job can be added.
The wizard guides to the list of different tasks which can be scheduled.
External interface needs to be selected
where then Automatic CRS Import can be chosen
The Automatic CRS Import Dialogue is confirmed with OK.
Name of the job and schedule can be defined.
The schedule can now be stored.
Now, the job is available in the task list.
Remark: In case that the ticket-import shall run several times a day, mulitple jobs need to be defined in the task list.
...
| Anker | ||||
|---|---|---|---|---|
|
| Anker | ||||
|---|---|---|---|---|
|
| Anker | ||||
|---|---|---|---|---|
|
| Anker | ||||
|---|---|---|---|---|
|
...