Custom PNR Mapping

The PNR can be customized to contain basic information, such as adding a cost center to a name field, or to control processes, such as ticket exchanges and Pre-Trip Approval. You must be familiar with PNR scripting for the GDS you are using.

To download above documents:

Click on desired document

Click on the cloud symbol in the upper right hand corner of your screen, this will allow you to download, save and or print.

Additional Links

Custom PNR Editor Script Samples for Mobile

Custom PNR Editor Script Samples for Train Service

Custom PNR Editor Script Samples for Pre-Trip Approval (PTA)

Benefits and Need to Know

	Benefits and Need to Know
Benefits	Ability to customize PNR based on company needs, such as custom reporting fields
Need to Know	You may not need to make many changes as Deem designed the PNR mapping within your agency template around your agency specs during the implementation process. Supported GDS Sabre Amadeus Galileo (Apollo) 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 Make sure you are working in either two different browser types, such as Firefox and Google Chrome, or work in incognito mode within one of the browser windows you have opened Additional Scripts Custom PNR Mobile Scripts Custom PNR Rail Scripts Custom PNR PTA Scripts

Updating

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. The reason for this is 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, 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 = Remark Lines Amtrak Lines SWABIZ Lines 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 = 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 in your scripts. 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

Updating PNR Lines

	Process and Helpful Hint
Suppressing line from triggering	You can make your template site as robust as you would like, and then suspend/suppress a script from writing instead of completely removing it Example: You can add reporting fields/UDIDs as a placeholder in your template, and if not needed, you can take the following steps to suspend/suppress the line from writing verses completely removing, as you may need it in the future. This saves you a great deal of time when configuring your mapping for all of your clients. Find line in mapping Click on Edit to the right of the script Check 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 Click Save
Editing PNR Line	Click on Edit to the right of the script 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. Click Save
Add PNR Line	Click on 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 Click on Save
Remove PNR Line	Click on Remove to the right of the script/line you would like to remove. Hint: instead of removing the script you may want to suppress using the script above just in case you would like to use the script later. Click 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 Click Save located in the lower right-hand corner Click on changes not applied in the upper right-hand corner of your screen Click on Commit Test - Always test anytime you make an update