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 to open it. Then, click on the cloud symbol in the top right corner of your screen to download, save, 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)

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.

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

Customer PNR Mapping will clone over from your template. Minimal changes may need to be made.
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.

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.

PNR Field Type and Masking

Task

Process and Helpful Hint

PNR Field Type

The PNR Field Type defines where in the flow each line will write to the PNR.
The output of the script should coincide with its field type

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.

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 or Account ID, then it may not.

Common PNR Field Types.

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 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. Click Edit to the right of the script. Select the GDS you are not writing to; In this example 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. Suppress using Scripting format. Select Edit. 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. Click 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. Click Save.
Add PNR Line	Click Add PNR Line. Customize PNR Line. Enter Line Number: Can not use the same line number more then once. Select PNR Field Type: Select one that best represent the function of the line. Customer PNR Requirements: Enter script. Select Requirement Type: Script or Text. Select GDS. Click Save.
Remove PNR Line	Click Remove. Note: Please see above option for Suppressing PNR Line. Click OK to confirm you would like to make the remove the line. Mapping will re-display and the line will be removed.
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 bottom right-hand corner of the screen. Click changes not applied in the upper right-hand corner of your screen. Click Commit. Test - Always test anytime you make an update to the site.