| Affected Areas: | Booking Import Queue |
| Useful For: | Travel companies sharing a single database but being segregated by branch where one branch makes the GDS booking and another one issues the ticket. |
| Introduced In: | 20.041 |
| Feature ID: | 162906 |
A PNR can have 2 sets of PCC and staff code: one PCC and staff code for the booking agent and one PCC and staff code for the ticketing agent. This scenario is applicable when a travel company does not hold an IATA plate and uses another ticketing agency to issue their tickets.
In this scenario, a travel agent makes the booking and creates a PNR in the GDS and queues it to the ticketing agent PCC for the ticket to be issued. Once the ticket is issued, the ticketing agent queues back the PNR to the booking agent. Finally the booking agent will import the ticketed PNR in the BMM.
To support this specific scenario in the BMM, a new setting has been added to the user interface configuration record called Apply User Name Filter To Original Booker:
If two travel companies that share a single DB but are segregated by branch, and one acts as the booker and the other as the ticketer, this setting will allow both the booking and ticketing staff to only see the PNRs assigned to their respective queue.
If the Apply User Name Filter To Original Booker checkbox is ticked within the user Interface Configuration record for the relevant GDS, the BMM will treat the staff code entered in the User Name Filter field as the booking agent staff code.
To help filtering records in the Booking Import Queue dialog, this dialog now shows two columns to display the issuing staff and the booking staff 3-letter code:
Comments
0 comments
Article is closed for comments.