Overview
Merge to PNR rules define how ClientBase sends client profile information to Travelport+. Almost all profile information can be used to create Merge to PNR rules to suit your agency’s unique needs. This article explains how to set up Merge to PNR for your agency and includes examples of the most common rules.
Note: The format for Galileo Interface ID will need to be updated from the current format in ClientBase. Click here for the correct format.
Setting up Merge to PNR
The Traveler name format must be updated in Global Defaults > Merge to PNR Defaults > PNR Settings. Click on the Traveler Name Format tab:
Traveler Name Insert Fields must be updated to look like this:
N.«No. Of Travelers»«Last Name»/«First Name»[ «Middle Name»] [«Courtesy Title»]
On the General Tab:
- Click on Global Defaults > Merge to PNR Defaults > PNR Settings
- There are two modes for sending profile information to Travelport+:
- Use API: This is the recommended option. Client profile information will be automatically transferred to the active Travelport+ PNR.
- Use Clipboard: There is a limitation when using Clipboard where you can only cut and paste up to 15 lines at a time. If you exceed 15 lines you will need to merge more than once. If accessing one of the two programs (ClientBase Windows or Travelport+) via Terminal Services or remote desktop you will be limited to the Clipboard option only.
- If using the API, we recommend unselecting (removing the checkmark next to) "Send as one transmission".
Adding or modifying Merge to PNR Rules
- Click on Global Defaults > Merge to PNR Defaults > PNR Rules.
- In the GDS drown down, select “Galileo”.
- To add a new Merge to PNR Rule, click Add.
- To modify an existing Merge to PNR Rule, highlight the rule you wish to change and click Modify.
PNR Rule Details
The Merge to PNR rule details screen allows you to set up the specific formats ClientBase will use to transmit profile information to Travelport+. Each Merge to PNR Rule consists of the following options:
- GDS: This will be pre-populated with the GDS selected on the previous screen
- Description of Rule: A brief description of the PNR entry. It is displayed on the Merge to PNR screen
- Field Groups: Select the category of fields that will be used to create this rule. The category controls which fields can be included in the format.
- Always Move this Rule: If selected (checked), this rule will be pre-selected when merging to PNR.
- Display on Selection Screen: By default, ClientBase users can choose whether or not to merge a particular rule when merging to PNR. For “Aways Move” rules, selecting this box will hide the option to unselect the rule during merge to PNR.
- Available Fields: The various fields in the field group selected are shown. Highlight the desired field and click “Insert” to include it in the rule
- Special Keys: Travelport+ characters that are not part of the normal Windows keyboard are shown. Click the character to include it in the merge to PNR rule.
-
PNR Custom Rule: This is the format that ClientBase will send to the GDS. The PNR entry will be formatted exactly as entered, apart from merge fields and square brackets (“[“ and “]”).
- Note on the use of square brackets: Enclosing text in square brackets will only be included if the merge fields are not blank. In the example, the “Company Name” will only be transmitted if the profile has a company name.
Example Merge to PNR Rules
The following examples include the most common Merge to PNR Rules. Many are pre-configured in your ClientBase database. To create a rule using the examples, you can copy and paste the entries in the gray boxes. Be sure to include all characters, including any leading or trailing brackets.
Profile Level PNR Entries
Bill-To Address
Field Group: Bill To Address
W.[«Company Name»*][[«Title» ]«First Name» «Last Name»*]«Address Line 1»[ «Address Line 2»][ «Apt/Suite»]*«City» «State»P/«Zip»
Ship-To Address
Field Group: Bill To Address
D.[«Company Name»*][[«Title» ]«First Name» «Last Name»*]«Address Line 1»[ «Address Line 2»][ «Apt/Suite»]*«City» «State»P/«Zip»
Interface ID
Field Group: Miscellaneous
Interface ID using DI-FT.AN
DI.FT-AN«Interface ID»
Phone Numbers
Field Group: Phone
Note: We recommend enter the city code followed by type of telephone number in ClientBase as it should be merged to the GDS, for example, DTWH or LAXB.
P.«First Four Character Description»*«Area Code»-«Prefix/Suffix»
Frequent Flyer Numbers
Field Group: Frequent Flyer
M.P«NAME FIELD POS»/«Code»«Number»
Credit Cards
Field Group: Credit Card
F.«Code»«Number»/D«Expiration»
Traveler-Level PNR Entries
Traveler Identification
- All entries requiring a country use the traveler’s Citizenship
- Citizenship must be entered using two-character country code (e.g., “US”, “CA”, “MX”)
- See CTC, DOC and PCTC – Revised merge to PNR rules for IATA requirements effective March 2023 for more information about entering country codes in traveler profiles
Field Group: Traveler Miscellaneous
Date of Birth
[SI.P«NAME FIELD POS»/SSRDOCSYYHK1/////«Birthdate»/«Gender»//«Last Name»/«First Name»[/«Middle Name»]]
Passport
[SI.P«NAME FIELD POS»/SSRDOCSYYHK1/P/«Issuing Country»/«Passport No.»/«Citizenship»/«Birthdate»/«Gender»/«Passport Expiration Date»/«Last Name»/«First Name»[/«Middle Name»]]
Known Traveler Number
[SI.P«NAME FIELD POS»/SSRDOCOYYHK1//K/«Known Traveler Number»///«Citizenship»]
Redress Number
[SI.«NAME FIELD POS»/SSRDOCOYYHK1//R/«Redress Number»///«Citizenship»]
Traveler Contact Information Airlines IROPS
- Uses the traveler’s primary telephone number and email address
- Does not work with profile-level communications
- Does not work with non-primary communications entries
Field Group: Traveler Miscellaneous
Traveler Email
[SI.P«NAME FIELD POS»/SSRCTCEYYHK1/«Traveler Contact Primary E-Mail»]
Traveler Phone
[SI.P«NAME FIELD POS»/SSRCTCMYYHK1/«Traveler Contact Primary Phone»]
Emergency Contact
- Uses information from Traveler’s emergency contact information
- Requires a country code, so pulls in the traveler’s citizenship
Field Group: Traveler Miscellaneous
[SI.SSRPCTCYYHK1/«Emergency Contact Name»/«Citizenship»«Emergency Contact Phone Country Code» «Emergency Contact Phone Area Code» «Emergency Contact Phone Prefix/Suffix Without Dash»-«Traveler Number»«Last Name»/«First Name»]