If you're having issues with the booking import queue, this article might provide you with a solution. Please note - these solutions involve updates to configuration in the booking management module and can only be carried out by users with certain administrative privileges.
The process of importing GDS files into the booking management module is made of three steps:
- File generation from the GDS
- File transportation to the download location where Dolphin is instructed to retrieve file data from
- Reading and importing these files into the BMM
Each GDS has its own command to generate a capture of PNR data that can then be read by and imported into Dolphin. This takes the form of PNR/FARE/TICKETING/REFUND/EXCHANGE/EMD data that can be read in to create new, or update existing bookings.
When this seamless process fails there are certain troubleshooting steps that can be taken.
- A first essential step to take is to ensure that your GDS is continuing to send data to the location Dolphin has been instructed to read from. It is very common that Dolphin stops displaying new bookings in the import queue because the GDS doesn't send new information to read and import.
-
-
- You can find the download directory location in the BMM from Options > Interface > select the relevant branch > select and retrieve the relevant interface source > in the Download Path field:
-
-
- For the GDS files to be correctly read and imported into the BMM, they must have the correct file extension. If the desired files are in the download directory but Dolphin doesn't read them, it is possible that the files have the wrong file extension.
-
-
- This is the list of file extension per GDS:
-
-
- GALILEO - MIR;
- AMADEUS - AIR;
- WORLDSPAN - PRT;
- SABRE - PNR.
-
-
- This is the list of file extension per GDS:
-
-
- If the file extension is .TXT it means that the files are being generated incorrectly by your GDS software. In this scenario, each file must be manually updated accordingly.
-
-
- To change the file extension, go to the files location, click on each file record > right-click with the mouse and go to Show more options > Rename and replace 'TXT with:
-
-
- .MIR for Galileo files
- .AIR for Amadeus files
- .PRT for Worldspan files
- .PNR for Sabre files.
-
-
- Once you change the file extension, Dolphin should start reading the file and display the record in the booking import queue.
- Please note that if files are generated incorrectly, it's important you let your GDS know so that they can change configuration and ensure the files come through with the correct extension.
- To change the file extension, go to the files location, click on each file record > right-click with the mouse and go to Show more options > Rename and replace 'TXT with:
-
-
- If files are being downloaded and being read (this is obvious as files are renamed when they are read in to the booking import queue. For example, an Amadeus file sent by Amadeus as ABCDEF.AIR once validated and loaded into the booking import queue, will be renamed as 123456.TXT with the file number being reflected in the booking import queue.
- If this scenario is occurring but the files are not visible to the user in their booking import queue as expected, this will be due to filtering configured in Options > User Security > search for and retrieve the relevant 3-letter code user login > retrieve the record for the relevant interface source:
- When filtering is in place, the booking import queue displays only the files created by the users listed in the User Name Filter field. This means that GDS files generated by another user will not be visible. By removing this filtering temporarily, you should be able to see the files as expected. Once you know that the files are correctly displaying in the booking import queue, you can decide whether filtering should be in place or not. It is worth pointing out that the User Name Filter field accepts multiple GDS users as per below example:
For more tips on how to troubleshoot booking import queue errors, sign in and check the below articles:
Loading next interface queue failed
Could not instantiate a parser queue entry
Comments
0 comments
Article is closed for comments.