Skip to main content
MORE

Amadeus Merge to PNR: Setup and Example Format Rules

  • Updated

Overview

Merge to PNR rules define how ClientBase sends client profile information to Amadeus. 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.

Setting Up Merge to PNR

mceclip0.png

Click on Global Defaults > Merge to PNR Defaults > PNR Settings

  1. From the GDS drop down list, select “Amadeus”
  2. There are two modes listed for sending profile information to Amadeus:
    • Use Clipboard: This option must be selected.
    • Use API: This option is no longer supported when using the web-based version of Amadeus.

Adding or Modifying Merge to PNR Rules

mceclip1.png

  1. Click on Global Defaults > Merge to PNR Defaults > PNR Rules
  2. In the GDS drown down, select “Amadeus”
  3. To add a new Merge to PNR Rule, click Add
  4. To modify an existing Merge to PNR Rule, highlight the rule you wish to change and click Modify

PNR Rule Details

mceclip2.png

The Merge to PNR rule details screen allows you to set up the specific formats ClientBase will use to transmit profile information to Sabre. 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: Sabre 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 Sabre will send to the GDS. The PNR entry will be formatted exactly as entered, with the exception of 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

[AB«Company Name»;][AB[«Title» ]«First Name» «Last Name»;]AB«Address Line 1»[ «Address Line 2»][ «Apt/Suite»];AB«City» «State» «Zip»

Ship-To Address

Field Group: Bill To Address

[AM«Company Name»;][AM[«Title» ]«First Name» «Last Name»;]AM«Address Line 1»[ «Address Line 2»][ «Apt/Suite»];AM«City» «State» «Zip»

Interface ID

Field Group: Miscellaneous

Interface ID using RM*AN

RM*AN«Interface ID»

Interface ID using AIAN

AIAN«Interface ID»

Phone Numbers

Field Group: Phone

AP«Country Code»«Area Code»-«Prefix/Suffix»-«First Character Description»

Frequent Flyer Numbers

Field Group: Frequent Flyer

FFN«Code»«Number»«NAME FIELD POS»

Credit Cards

Field Group: Credit Card

FPCC«Code»«Number»/«Expiration»

Traveler-Level PNR Entries

Traveler Identification

Field Group: Traveler Miscellaneous

Date of Birth

[SR*DOCS-----«BirthdateDDMMMYY»-«Gender»--«Last Name»-«First Name»[-«Middle Name»]«NAME FIELD POS»]

Passport

[SR*DOCS-P-«Issuing Country»-«Passport No.»-«Citizenship»-«BirthdateDDMMMYY»-«Gender»-«Passport Expiration DateDDMMMYY»-«Last Name»-«First Name»[-«Middle Name»]«NAME FIELD POS»]

Known Traveler Number

[SR*DOCO--K-«Known Traveler Number»---«Citizenship»-«NAME FIELD POS»]

Redress Number

[SR*DOCO--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

[SR*CTCE-«Traveler Contact Primary E-Mail»«NAME FIELD POS»]

Traveler Phone

[SR*CTCM-«Traveler Contact Primary Phone»«NAME FIELD POS»]

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

[SR*PCTC-«Emergency Contact Name»/«Citizenship»«Emergency Contact Phone Area Code»«Emergency Contact Phone Prefix/Suffix Without Dash»]

 

Revisions
  • 2022-01-18: Updated SSR to include "*" to explode at ET

Related articles