PNR Acquisition/Sync

Task

Process / Helpful Hint

Benefit

• Central location for all bookings

Need to Know

• If PNR has not being 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?

  • Tip: When an error occurs during PNR synchronization, a passive segment can be created if passive segments are enabled (described in the next section).

  • Note:  If a PNR is in the queue and it does not belong to a Deem user,  the PNR is simply removed from the queue (QR) and no additional action is taken

Task

Process / Helpful Hint

Steps to Configure

• Under the Services tab, click on Travel Agency

• Click on Agency Settings

• Click on Setting Name

• Scroll down to PNR Synchronization Settings

• Click Add Synchronization Settings 

• Acquire off-line PNRs: Click on the checkbox to acquire off-line PNRs

  • Note:  When syncing an offline PNR, the unique identifier is the only element that Deem looks for to sync to a travelers account

• Select a GDS: Choose a GDS from the dropdown menu

• TA Group: Click on appropriate GDS

  • ExternalSabreNew for Sabre

  • ExternalApollo for Apollo

  • ExternalGalileo for Galileo

  • ExternalWorldspan for Worldspan

• Acquisition Queues: 

  • Enter the Pseudo-city where PNRs are to be acquired: Enter the pseudo-city code

  • Enter the queue where off-line PNRs are placed for acquisition: Enter the first queue to use for off-line PNRs

  • Enter the Pseudo-city where PNRs are to be processed if different from above: Enter the pseudo-city code to use for processing if different from acquisition pseudo-city

  • Enter the first queue where off-line PNRs are to be processed: Enter the first queue to use for off-line PNR processing

  • Enter the second queue where off-line PNRs are to be processed: Enter the second queue to use for off-line PNR processing

• Acquisition Failure Queue:

  • Enter the pseudo-city for the queue where PNR’s that fail acquisition are placed, if different from the acquisition pseudo-city: Enter the pseudo-city to use for failed sync requests

  • Enter the queue (with queue action if appropriate) where off-line PNRs that fail acquisition are placed: Enter the queue to use for failed sync requests

    • Note: It is the responsibility of the agency 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 on that queue, but no documentation is added.

• Owner Identification:

  • Select the method used to look up the owner of a PNR: This is set during implementation and there is no need to change it. It is a best practice to use a Unique Identifier

• Enter prefatory remarks that precede the traveler’s owner identifier in the PNR

• Hours of Operation: 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 timing here:

• Select the hours of operation for this PNR synchronization configuration: Select Always On or Specific Hours and then set the hours of operation

• Select how frequently PNR synchronization should be attempted: Select the frequency to use for synchronization. 

  • Warning: Each time PNR synchronization is triggered, GDS hits can incur charges. We recommend setting the interval to no more than every 60 minutes.

PNR Mapping

Your custom PNR field should have been created for you, during the creation of your Template site. The field will clone over to each site you clone, but you will want to verify that this field is listed under your PNR mapping.  

• Example:

• Note: Below script is written for Sabre, therefore you will need to change formatting to your GDS formatting. You will also need to ensure 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);} 

Profile Mapping/ETSI

You will need to ensure the sync ID is also written to the client’s offline profiles.  This should have been configured during the setup of your template, but you will want to validate that this field is present.

• This field will need to move over into all agent booked reservations, to ensure all agent booked reservations sync up to the appropriate account within Etta

ETSI Example: