Overview
Merge to PNR rules define how ClientBase sends client profile information to Worldspan. 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.
Adding or modifying Merge to PNR Rules
- Click on Global Defaults > Merge to PNR Defaults > PNR Rules.
- In the GDS drown down, select “Worldspan”.
- 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 Worldspan. 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: Worldspan 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
[5-CB«Company Name»#][5-CB[«Title» ]«First Name» «Last Name»#]5-CB«Address Line 1»[ «Address Line 2»][ «Apt/Suite»]#5-CB«City» «State» «Zip»Ship-To Address
Field Group: Bill To Address
[5-CD«Company Name»#][5-CD[«Title» ]«First Name» «Last Name»#]5-CD«Address Line 1»[ «Address Line 2»][ «Apt/Suite»]#5-CD«City» «State» «Zip»
Interface ID
Field Group: Miscellaneous
Interface ID using DI-FT.AN
5-CA«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.
9*«Area Code»-«Prefix/Suffix»-«First Character Description»
Frequent Flyer Numbers
Field Group: Frequent Flyer
3SSRFQTV«Code»HK/«Code»«Number»«NAME FIELD POS»
Credit Cards
Field Group: Credit Card
5$CC«Code»«Number»N«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
[3SSRDOCSYYHK1/////«Birthdate»/«Gender»//«Last Name»/«First Name»[/«Middle Name»]«NAME FIELD POS»]
Passport
3SSRDOCSYYHK1/P/«Issuing Country»/«Passport No.»/«Citizenship»/«Birthdate»/«Gender»/«Passport Expiration Date»/«Last Name»/«First Name»[/«Middle Name»]«NAME FIELD POS»
Known Traveler Number
[3SSRDOCOYYHK1//K/«Known Traveler Number»///«Citizenship»/«NAME FIELD POS»]
Redress Number
[3SSRDOCOYYHK1//R/«Redress Number»///«Citizenship»/«NAME FIELD POS»]
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
[3SSRCTCEYYHK1/«Traveler Contact Primary E-Mail»«NAME FIELD POS»]
Traveler Phone
[3SSRCTCMYYHK1/«Traveler Contact Primary Phone»«NAME FIELD POS»]