PNR Acquisition/Sync
- Malissa Olofernes
- Lori Guillory
On this page:
Overview
PNR Synchronization gets offline bookings so that Deem is the central location for all bookings. PNR Synch enables a travel agency to fulfill offline travel bookings for a user by synchronizing the Deem profile data with the travel agency’s GDS. PNR Synch requires a third-party interface partner. TMCs can use the same PNR Synchronization set up for all of their sites.
Need to know
It is recommended to establish a process in your mid-office to queue reservation any time a reservation is ticketed, voided, refunded, or canceled, and or train the agent team to queue the reservation to the PNR acquisition queue.
PNR Synchronization set up is not only used to sync offline bookings and changes to Deem. This set up is also used by Pre-Trip Approval and Open Expense.
You to not have to enable PNR Synchronization on every site. A TMC can create a special PNR Synch site. If they have a single PCC, they can use a single PNR Synch queue for all sites and the unique identifier will match the booking to the appropriate traveler on the appropriate site.
If a PNR is not acquired online, check the following:
Is the Sync ID listed in the PNR?
Was reservation queued to the PNR acquisition/sync queue?
If sent to the queue, has it been picked up and processed?
Did the reservation fall to the failure queue?
Configure PNR Synch
From the partner dashboard home page, select the Settings link for the site you want to modify.
From the top menu, select the Services tab.
Select the Travel Agency link in the Travel list.
Select Agency Settings.
Select the name link of an active settings.
Scroll down the the PNR Configuration section within the Agency Configuration Settings section.
Select Add Synchronization Settings.
Select Acquire off-line PNRs.
Note: When synchronizing an offline PNR, the unique identifier is the only element that Deem looks for to synchronize to a traveler's account.Select the appropriate GDS.
Select the TA Group (will not show for Amadeus).
ExternalApollo for Apollo
ExternalGalileo for Galileo
ExternalSabreNew for Sabre
ExternalWorldspan for Worldspan
Enter the pseudo city from which PNRs are to be acquired.
Enter the first queue to use for offline PNRs.
Enter the pseudo-city code to use for processing if different from acquisition pseudo-city.
Enter the first and second queue to use for offline PNR processing.
Enter the pseudo city for the queue where PNRs that fail acquisition should be placed, if different from the acquisition PCC.
Enter the queue number for failed acquisition PNRs.
Important: It is the agency’s responsibility to monitor failed acquisitions. If there is no failure queue configured, the PNR is removed from the queue. If a failure queue is configured, the PNR will be placed in that queue, but no documentation is added.The owner identification method is set during implementation and there is no need to change it. It is best practice to use a Unique Identifier. Depending on which method is selected, you can add prefatory remarks.
Deem scripts run every hour on the half hour. If scripts are to run more or less frequently, or at a different time, configure the interval.
Note: We recommend setting the interval to no more than every 5-15 minutes.Save your changes.
Example PNR Synch settings
Verify custom PNR field
Your custom PNR field should have been created for you during the creation of your template site. The field will copy over to each site you clone, but you will want to verify that this field is listed under your PNR mapping.
Select the Services tab at the top of the page.
Select Travel Agency.
Select Custom PNR.
Select the name of a custom PNR configuration.
Example
Note: The script below is written for Sabre. Modify as needed for your GDS. Also ensure that you are writing the field in the correct location of the PNR for your TMC.
Script
//UNIQUE ID
if(
(UserPnrData.DataType == "new"||UserPnrData.DataType == "hold")
)
{out.print("5R$synch-" + UserPnrData.User.UserExternalIdSet.ReardenPNRSyncID);}
Verify profile mapping/ETSI
Note: Profile mapping is done in the third-party’s interface, not in the partner dashboard. The example below shows ETSI’s interface for Profile mapping.
Ensure that the sync ID is also written to the client’s offline profiles. This settings should have been configured during the setup of your template, but you will want to validate that this field is present. This field needs to move over into all agent booked reservations to ensure that all agent-booked reservations sync up to the appropriate account within Deem.
ETSI Example
Enterprise Travel Systems, Inc., (ETSI) is Deem’s profile synchronization interface partner. Other third-party interfaces may be different.