Custom PNR Mapping

Benefits and Need to Know

Benefits

• Ability to customize PNR based on company needs, such as custom reporting fields.

Need to Know

• Custom PNR Mapping will clone over from your template. Minimal changes may need to be made.

• Supported GDS

  • Sabre

  • Amadeus

  • Galileo (Apollo)

  • Worldspan

  • Travelport+ (Worldspan)

• XML tags - Available at the top of this article.

• If you need help with a PNR script, please open a Deem Support Case.

• If you need more than one PNR mapping, you will not have the ability to clone. You must manually create the additional PNR mappings.

Example: If you are writing to different PCCs or even more than one GDS, you would need to manually create a second mapping within the site.

• Open the site in a second browser window and then you can copy and paste the information from one mapping to the other. You can make the necessary changes to the second mapping as needed. 

Hint: You can work in more than one browser type at a time. You will need to use two different browser services, such as Google Chrome, Chrome Edge, Firefox etc. (or) work in incognito mode.

• Additional Scripts, please click below links for further information.

  • Custom PNR Mobile Scripts

  • Custom PNR Rail Scripts

  • Custom PNR PTA Scripts

Task

Process and Helpful Hint

PNR Field Type

• The PNR Field Type defines where in the flow each line will write to the PNR. 

• In general practice, the output of the script should coincide with its name. 

Example: if the agency is overriding the ticketing line, then the script(s) that generate the custom ticketing line should generally be associated with PNR field type Ticketing, not Name or Account ID. 

• Used to maintain the appropriate flow of building a PNR. 

• There are times where the ticketing line may need to be entered twice, or perhaps later in the creation/modification of a PNR. If the custom PNR field has a field type set to Ticketing, the line will write appropriately, but if it's set to Name or Account ID, then it may not.

Common PNR Field Types used

• Accounting ID: Standard script line, typically used unless the script involves one of the following line types.

• Remark: Commonly used for Amtrak and SWABIZ.

• Post ER: Script triggers after initial ER.

• Pre Trip Approval: Pre-Trip Approval scripts.

• Profile: Company Profile script or those associated with the profile.

• Received: Received from field.

• Ticketing: Ticketing Lines.

• UDID: Reporting Fields.

PNR Mask

• PNR Mask is located at the bottom of the PNR mapping. You will want to select those field types which you have customized with mapping.

  • To select more than one line item, hold down the Ctrl key on your keyboard and select each line item.

  • In this example I have selected: Address, Agency Phone, Delivery, Email, FOP, Other Phone, Received, Ticketing.

Process and Helpful Hint

Suppressing line from triggering

You can make your template as robust as you would like, and then suspend/suppress a script from writing instead of completely removing it. This can be completed in two separate ways. Please configure based on what works best for you.

Suppress by Changing GDS to one that is not being used in the site.

• Select Edit to the right of the script.

• Select box to the left of the GDS you are not writing to, in this case I am selecting Apollo.

• Un-Check the GDS you are currently mapping to; in this example, I am writing to Sabre therefore I have un-checked the Sabre GDS.

• Select Save.

Suppress using Scripting format.

• Select Edit to the right of the script.

• Enter (/*) to the as the first line of the script.

• Enter comment line as the second line of the scrip, indicating date suppress, your initials and any explanation why. This is freeform but must start with a double slash (//).

• Enter (*/) as the last line of the script. 

• Select Save.

Editing PNR Line

• Select Edit

• Edit line as needed; in the example below, I am changing the line number from 83 to 82. Keep in mind, you can change not only the line number but also the PNR Field Type, the Custom PNR Requirement (script) or even the GDS.

• Select Save.

Add PNR Line

• Select Add PNR Line.

• Customize PNR Line.

  • Enter Line Number.

  • Select PNR Field Type.

  • Customer PNR Requirements: Enter script.

  • Select Requirement Type = Script or Text.

  • Select GDS.

  • Select Save.

Remove PNR Line

• Select Remove to the right of the script/line you would like to remove.

• Select OK to confirm you would like to make the remove the line.

• Mapping will re-display and the line will be gone.

Saving changes

You will need to take the following steps anytime you make a change or update to the mapping.

• Select Save located in the lower right-hand corner.

• Select changes not applied in the upper right-hand corner of your screen.

• Select Commit.

• Test - Always test to insure the changes  you have made are working properly.