Amadeus Quality · PDF file · 2012-08-03Edition 4.0 For Amadeus Quality Control...

Support Information

Amadeus Quality Control

User Guide

YOUR USE OF THIS DOCUMENTATION IS SUBJECT TO THESE TERMS Use of this documentation You are authorized to view, copy, or print the documentation for your personal use only. None of the Amadeus data included in the documentation may be sold, transferred, redistributed, retransmitted, published or commercially exploited in any way without the express advance written permission of Amadeus. This documentation is provided on an “AS IS” basis and Amadeus does not warrant any maintenance or support in using this documentation. Data ownership This documentation is protected by Intellectual Property rights and is the exclusive property of Amadeus. No licence over these Intellectual Property rights is herein being granted. You acknowledge that the documentation is the valuable intellectual property of Amadeus and that if you use, modify or distribute the documentation for unauthorized purposes, you will be liable to Amadeus for any damages it may suffer. The examples in this document are for illustrative purposes only. The naming of particular airlines, hotels, car rental agencies, or other companies in these examples does not constitute an endorsement, express or implied, of Amadeus by these companies or of these companies by Amadeus. Product offers, prices, terms and other information provided herein are subject to change without notice. You should determine the appropriateness of any product for your intended purpose and needs. Amadeus makes no warranty of any kind including but not limited to the implied warranty of merchantability and fitness for a particular purpose. © 2010 Amadeus s.a.s. All Rights Reserved. Edition 4.0 For Amadeus Quality Control 5.1 (Amadeus Selling Platform 6.1) Job Number 2517 FE 0410 Published by: Amadeus Educational Systems and Services e-mail: [email protected] April 2010

© 2010 Amadeus s.a.s. - All rights reserved i

Table of Contents

Before You Start ...................................................................................... 1

Chapter 1 What Is Amadeus Quality Control? ....................................................... 3

Amadeus Quality Control Components ................................................. 4 Workflow: Deploying Amadeus Quality Control ..................................... 5

Chapter 2 What Is Amadeus Quality Control Manager?........................................ 7

Setting and Changing the Quality Control Manager Password ............. 8

Chapter 3 What Is Rule Editor? ............................................................................... 9

How to Start Rule Editor ...................................................................... 10 Common Functionality for RuleFiles, RuleSets and RuleLibraries...... 10

Chapter 4 Creating Rules With Rule Editor .......................................................... 13

Workflow: Creating Rules .................................................................... 13 Creating a Simple Rule........................................................................ 17

If Conditions.................................................................................................21 Where Statements.......................................................................................23 Rule Messages............................................................................................27 Rule Actions ................................................................................................29

Advanced Rules .................................................................................. 31 For Each Conditions ....................................................................................31 Variables......................................................................................................33 Applying Functions on Variables .................................................................37 Variable Conditions .....................................................................................42 Using Special Expressions..........................................................................44

Testing RuleFiles................................................................................. 46

Amadeus Quality Control User Guide

ii Edition 4.0

Chapter 5 Grouping RuleFiles into RuleSets ....................................................... 49

Chapter 6 Publishing RuleFiles and RuleSets in RuleLibraries ......................... 51

Workflow: Publishing Rules ................................................................. 51 How to Create a RuleLibrary and Add Rules....................................... 54 Publishing a RuleLibrary...................................................................... 55

Chapter 7 What Is Administrator? ......................................................................... 59

How to Start Administrator................................................................... 60

Chapter 8 Deploying RuleChecker Settings to the Agents ................................. 61

RuleChecker Configurations................................................................ 61 Inheriting and Copying Settings........................................................... 62

Chapter 9 Configuring RuleChecker in Administrator......................................... 65

Workflow: Deploying RuleChecker Settings ........................................ 65 How to Replicate Changes to RuleChecker Configurations ................ 66 Configuring RuleChecker Bypass........................................................ 66 Selecting Commands to Trigger RuleChecker in Point of Sale Mode . 69

Example: Linking Rules to Triggering Commands ......................................72 Displaying Informative Messages........................................................ 74 Selecting Queues from RuleChecker .................................................. 75 Blocking Commands in RuleChecker .................................................. 75 Customising RuleChecker's Behaviour ............................................... 77

What If no Rule Is Associated to a PNR?....................................................77 What If an Associated Rule is Missing? ......................................................77 Which Rules Apply If Another Office Is Responsible for the PNR? ............78 What If the PNR Has no Active Itinerary? ...................................................79 How to Add RF Elements to Track Checked PNRs ....................................80

Chapter 10 Associating Rules to PNRs .................................................................. 81

What Are the Different Methods of Associating Rules to PNRs? ........ 81 Adding RC Elements in the PNR......................................................... 81 Transferring RC or RX Elements from Profiles.................................... 82 Associating Rules to All PNRs Processed by an Office ...................... 83 Associating Rules to Specific Agents .................................................. 86 Manually Associating Rules in RuleChecker ....................................... 87 Example: Combining Different Methods of Associating Rules to PNRs............................................................................................................. 88

Table of Contents

© 2010 Amadeus s.a.s. - All rights reserved iii

Chapter 11 What Is Amadeus Quality Control RuleChecker?............................... 89

Chapter 12 Checking PNRs with RuleChecker....................................................... 91

Launching RuleChecker ...................................................................... 91 Checking a PNR.................................................................................. 92 Rechecking a PNR .............................................................................. 95 Bypassing RuleChecker ...................................................................... 96 Placing PNRs on Queues.................................................................... 97 Associated RuleFiles/Sets Display ...................................................... 98 Transaction Log................................................................................... 99 Troubleshooting Log.......................................................................... 100 Customising RuleChecker Display Options....................................... 100 Example: Creating a Rule and Testing It in Selling Platform............. 102

Chapter 13 Importing and Exporting RuleFiles.................................................... 109

Importing RuleFiles............................................................................ 109 Exporting RuleFiles ........................................................................... 110

Chapter 14 Displaying PNR/TST Details ............................................................... 113

Appendix A Data Dictionary .................................................................................... 117

Index of Properties by PNR/TST Element ......................................... 119 PNR and TST Elements .................................................................... 134

Index ..................................................................................................... 167

© 2010 Amadeus s.a.s. - All rights reserved 1

Before You Start

Introduction

This user guide describes Amadeus Quality Control, a product option that can be integrated in Amadeus Selling Platform in order to check PNRs and ensure consistency across bookings.

Audience

This document is intended for administrators who will implement Amadeus Quality Control.

The sections on Quality Control RuleChecker are also intended for the travel agents who use RuleChecker in their daily PNR processing.

Prerequisites

You should have an understanding of the distribution system, including a thorough understanding of PNRs and PNR segments.

Objectives

This guide will help you to:

• Understand Amadeus Quality Control and what it does

• Use RuleChecker on a day-to-day basis to ensure that your travel bookings conform to your organisation's quality control (or to traveller or company preferences)

• Create and test quality control rules using the Rule Editor module

• Configure Amadeus Quality Control using the Administrator module


2 Edition 4.0

How to Get Further Help

• Context-sensitive online help

Press F1 in any of the Quality Control screens and windows to access dedicated help related to your current step.

Quality Control Manager also includes helpful information directly on the screen.

• Quality Control support and assistance

If you need support or troubleshooting assistance, your contacts are:

- For a travel agency: Contact your local Amadeus Commercial Organisation (ACO). The ACO may then escalate to the Amadeus Service Management Centre (SMC).

- For an airline: Contact the Amadeus Service Management Centre.

What's New in This Document?

This edition includes the following changes:

Type of Change Area/Topic

New functionality • For Each conditions When you set up rules in the Rule Editor, a new condition type is available: For Each. This condition (available only as the first condition in a rule and only once per rule) will ensure that all elements in a PNR meeting the conditions will be checked. The action of the rule will be carried out each time the conditions are met. See also For Each Conditions on page 31.

Modified sections This user guide has been completely revised in order to provide you with the most relevant information.


Chapter 1

What Is Amadeus Quality Control?

Amadeus Quality Control is a tool for travel agencies to check that PNRs conform with their business practices.

Amadeus Quality Control provides the following key features:

• Customisable - can be fully adapted to the agency’s own business needs and processes.

• Integrated in Amadeus Selling Platform.

• Helps ensure the quality of an agency’s processes, policies and PNR finishing tasks.

• Helps make non-air bookings easier, with features such as automated prompts for ancillary service bookings.

• Provides systematic quality checking of PNRs at time of booking, pricing and ticketing.

• Can be used to check Air, Hotel, Car, Cruise, Insurance and other segments.

• Runs automatically (POS mode) or on demand (OND mode).

• Provides easy writing, maintenance and deployment of rules, using a graphical user interface.

• Automatic installation and configuration setup of Quality Control allows office settings to be centralised in WebConfig, offering a unique interface which is deployed seamlessly through the WAN or LAN. This can be specific for a particular certificate, a travel agency, or a group of offices that are not necessarily based in the same country.

• Storage of rules in a central database called QC Rules Repository allows rules to be quickly replicated, created and updated across terminals.


4 Edition 4.0

Amadeus Quality Control Components Amadeus Quality Control consists of the following components:

Amadeus Quality Control Manager

Amadeus Quality Control Manager allows travel agency administrators to do the necessary setup for RuleChecker.

It provides access to the following modules:

• Rule Editor to set up the rules to be used by RuleChecker.

For more information see What Is Rule Editor? on page 9.

• Administrator to configure RuleChecker-related settings, such as the commands that will automatically trigger RuleChecker.

For more information see What Is Administrator? on page 59.

Amadeus Quality Control RuleChecker

Amadeus Quality Control RuleChecker is used by travel agents to check whether travel reservations comply with the business rules associated with an active PNR.

For more information see What Is Amadeus Quality Control RuleChecker? on page 89.

Overview of the Amadeus Quality Control components and their deployment

Chapter 1 What Is Amadeus Quality Control?


Workflow: Deploying Amadeus Quality Control In order to use Amadeus Quality Control in your office group or office, you need to carry out the following steps:

The rules contain the logical conditions that RuleChecker will check in a PNR. Rules are defined within RuleFiles.See Creating Rules With Rule Editor on page 13. RuleSets contain RuleFiles that logically belong together. See Grouping RuleFiles into RuleSets on page 49. RuleLibraries contain all the RuleFiles and RuleSets that will be used together. See How to Create a RuleLibrary and Add Rules on page 54. Publish the library to the user group that will use the RuleFiles and RuleSets. See Publishing a RuleLibrary on page 55. Set, for example, bypass options, triggering commands and queues. See Deploying RuleChecker Settings to the Agents on page 61 and Configuring RuleChecker in Administrator on page 65 for more information. RuleChecker needs to know which rules have to be checked in a PNR. See Associating Rules to PNRs on page 81. RuleChecker can be launched by the travel agent or automatically to check the PNRs for compliance with the associated rules. See Checking PNRs with RuleChecker on page 91.

.


Chapter 2

What Is Amadeus Quality Control Manager?

Amadeus Quality Control Manager allows travel agency administrators to create rules and manage the deployment of the rules across office groups, offices and certificates.

To activate Quality Control Manager, click on in the Selling Platform main menu bar. A password may be required.

You use the Navigation frame on the left of the Quality Control Manager main window to access the following pages:

• Welcome

From the Welcome page you can set a password to restrict access to Quality Control Manager to only the users in charge of administration tasks. See Setting and Changing the Quality Control Manager Password on page 8.

• Rule Editor

You use Rule Editor to set up the rules to be used by RuleChecker and organise them in RuleFiles, RuleSets and RuleLibraries.

RuleFiles contain the logical conditions that RuleChecker will check in a PNR.

RuleFiles can be grouped in RuleSets that are deployed together.


8 Edition 4.0

A RuleLibrary contains the RuleFiles and RuleSets that are used by an office group, an office or travel agents.

See What Is Rule Editor? on page 9 for details.

• Administrator

You use Administrator to configure RuleChecker-related settings at office-group, office or certificate level, such as the commands that will automatically trigger RuleChecker. See What Is Administrator? on page 59 for details.

You can switch between Administrator and Rule Editor at any time just by clicking on the Launch Administrator or Launch Rule Editor links.

Setting and Changing the Quality Control Manager Password

You can set a password to restrict access to the Quality Control Manager. By default, there is no password protection.

When you set a password, it will apply to the following configuration level:

• To the whole office group if your office belongs to an office group and if no access restrictions are defined.

• Only to your office if your office does not belong to a group or if it belongs to an office with restricted access.

How to Enable Password Protection for Quality Control Manager

1. Click on the link in the Quality Control Manager Welcome page.

2. Enter the password in the Enter New Password field.

3. Confirm the password by entering it in the Confirm New Password field.

4. Click on Change.

5. Communicate the new password to all authorised users.

Once you have set a password, a password pop-up window will be displayed each time an agent starts Amadeus Quality Control Manager.

What If You Have Forgotten Your Password?

If you have lost your password, you need to open an Incident and request that your password is reset.


Chapter 3

What Is Rule Editor?

The Rule Editor component of Amadeus Quality Control Manager allows you to set up and manage the rules that will be used by RuleChecker.

In Rule Editor, you have access to the following tabs:

• All RuleFiles/Sets

This tab displays the list of all available RuleFiles and RuleSets. From here you can create and modify quality control rules.

See also Creating Rules With Rule Editor on page 13 and Grouping RuleFiles into RuleSets on page 49.

• All RuleLibraries

This tab displays the list of all available RuleLibraries. From here you can package RuleFiles and RuleSets into RuleLibraries and publish them to individual travel agents or offices.

See also Publishing RuleFiles and RuleSets in RuleLibraries on page 51.

• Recycle Bin

The Recycle Bin allows you to restore deleted RuleFiles and RuleSets.


10 Edition 4.0

How to Start Rule Editor 1. If Amadeus Quality Control Manager is not yet open, click on in the Selling

Platform main menu.

If a password was set up for your office ID, enter it now and click on OK.

The Amadeus Quality Control Manager screen is displayed.

2. Click on one of the Rule Editor links to open Rule Editor.

The All RuleFiles/Sets tab is displayed. It contains all the RuleFiles and RuleSets that have been defined for your office group or for your office.

Common Functionality for RuleFiles, RuleSets and RuleLibraries

How to Copy

You can save time by using the Save As feature if you wish to create a new RuleFile, RuleSet or RuleLibrary that is only slightly different from an existing one.

1. In Rule Editor, select an existing RuleFile or RuleSet in the All RuleFiles/Sets tab or a RuleLibrary in the All RuleLibraries tab.

2. Click on Open.

3. Select File > Save As and enter the new name in the window that appears.

4. Click on Save to create the new file.

Note: Do not change the name directly in the Name field in the General Information tab. This would change the name of the existing RuleFile but not create a new one.

You can now modify the RuleFile, RuleSet or RuleLibrary as required.

Chapter 3 What Is Rule Editor?


How to Modify

1. In Rule Editor, select an existing RuleFile or RuleSet in the All RuleFiles/Sets tab or a RuleLibrary in the All RuleLibraries tab.

2. Click on the Open button or on .

You can now modify the RuleFile, RuleSet or RuleLibrary as required:

How to Save

When you have entered the necessary information, click on to save. This icon is only accessible if you have entered all the mandatory information.

If you have not yet entered all the mandatory information, you can only save a draft by clicking on .

To save changes to all RuleFiles/Sets/Libraries that are currently open, select File > Save All.

How to Print

1. In Rule Editor, highlight or open a RuleFile, RuleSet or RuleLibrary.

2. Select File > Print. A Print Preview screen is displayed.

3. Click on Print to proceed with the printing.

How to Move RuleFiles and RuleSets to the Recycle Bin

1. From the RuleFiles/Sets tab in Rule Editor, select a RuleFile or RuleSet.

2. Click on Delete. The selected files will be deleted from the list and sent to the Recycle Bin.

How to Restore RuleFiles and RuleSets from the Recycle Bin

You can restore previously deleted RuleFiles and RuleSets from the Recycle Bin:

1. In Rule Editor, click on the Recycle Bin tab.

2. Select the RuleFiles or RuleSets you want to restore.

3. Click on Restore.

How to Permanently Delete RuleFiles and RuleSets

1. In Rule Editor, click on the Recycle Bin tab.

2. Select the RuleFiles and RuleSets you want to delete permanently (they cannot be restored afterwards).

3. Click on Confirm Deletion.

How to Permanently Delete RuleLibraries

Caution: You cannot restore a deleted RuleLibrary. In contrast to RuleFiles and RuleSets, it is not sent to the Recycle Bin but deleted permanently.

1. From the All RuleLibraries tab in Rule Editor, select a RuleLibrary.

2. Click on Delete. You will be asked if you really want to delete the RuleLibrary.

3. Click on Yes.


Chapter 4

Creating Rules With Rule Editor

Workflow: Creating Rules The conditions that you want to check and correct in the PNRs need to be stored in rules. You create rules in the Rule Editor component of Amadeus Quality Control Manager.

See How to Create a RuleFile with a Rule on page 17.

See Testing RuleFiles on page 46.

See Grouping RuleFiles into RuleSets on page 49.

Once you have completed this process, you have to add your RuleFiles and RuleSets to a RuleLibrary and deploy it to the travel agents' terminals. See Workflow: Publishing Rules on page 51 for more information.


14 Edition 4.0

What Is a Rule?

A quality control rule is a combination of logical propositions which allow you to test the presence (or absence) of certain conditions in a PNR.

In the rule you indicate the PNR element you are looking for (If condition) and the properties you want to check (Where statement). You also define RuleChecker's reaction if your condition is not met: RuleChecker can display a message, block the PNR flow and suggest - or automatically perform - a corrective action.

A simple rule consists of at least two elements that are mandatory:

• One If condition

Example: If the PNR contains at least one air segment...

• One message

Example: ... Then display the warning message "Propose a car booking."

You can also add optional elements to a rule, for example Where statements and actions. For more complex rules, Rule Editor allows you to define variables that you can use in your rules.

Here is an example of a rule:

What Is a RuleFile?

Rules are always created within a RuleFile. A RuleFile can contain one or more rules.

Here is an example of a RuleFile:

Chapter 4 Creating Rules With Rule Editor


Before You Start Creating Rules

Before you start creating your rule in Rule Editor, you should think about the objectives of your rule and how you can achieve them.

It can be helpful to write down answers to the following questions:

Question Rule Element

Should all the matching elements in a PNR lead to the application of the rule?

For Each condition: RuleChecker will loop through each element in the PNR to check if it meets the conditions.

Or should the rule be applied on the first element found only?

If condition: RuleChecker will stop checking when it has found the first PNR element meeting the conditions.

Which element do I need to check? If or For Each condition: Select the PNR or TST element you want to check.

And what do I want to review in the element?

Where statement: Select the property of the PNR or TST element you want to check.

Which cases would be a match to my rule? Where statement: Define the number of elements you want to find.

Is this a problem that should interrupt the PNR flow?

Rule message: Choose between error and warning.

How can the problem be fixed? Rule action: Specify manual or automatic actions that will make the PNR compliant.

Which Elements Can I Use in My Rule?

These are the elements that you can use in a rule:

• For Each condition (optional)

For Each conditions allow you to check all the elements of a PNR that have the same characteristic. You can only have one For Each condition in a rule, and it needs to be the first condition in the rule.

See also For Each Conditions on page 31.

• If condition (mandatory)

In the If condition, you select the PNR or TST element that you want to check. For example, you can select Air segment, Car segment or Name element.

A rule must contain at least one If condition. If you want to check different elements in the same rule, you can add a separate condition for each PNR or TST element.

See also If Conditions on page 21.


16 Edition 4.0

• Where statement (optional)

The Where statement contains the property of the element that you want to check. For an air segment, this can be the airline, the class or the off-point (destination airport), for example.

For each If condition, you can enter one or more Where statements to check different properties of the selected element.

See also Where Statements on page 23.

• Rule message (mandatory)

A message is mandatory.

Define the message that will be displayed to the travel agent if the PNR meets the conditions in the rule.

See also Rule Messages on page 27 on page 28.

• Rule action (optional)

You can specify one or more actions to be performed when the conditions of the rule are met.

See also Rule Actions on page 29.

• Variable (optional)

You can use variables in your rule if the property you are looking for depends on the context and does not have a fixed value.

See also Variables on page 33.

• Variable condition (optional)

In some cases you may want to compare the value of a variable with a fixed value or with the value of another variable. You can do this in a variable condition.

See also Variable Conditions on page 42.

If You Don't Know Which Property or Element to Check

If you know which characteristic you want to check in the PNR, but you don't know from which element you can extract this information, you may find help here:

• View PNR/TST Details option

The View PNR/TST Details option in the Tools menu in Rule Editor allows you to display detailed information on the elements in the current PNR.

This can be helpful when you need to know the names of the elements and the properties you can check in your rule. See Displaying PNR/TST Details on page 113 for more information.

• Data Dictionary

See the Data Dictionary on page 117 in this guide for a full list of PNR and TST elements and their properties that you can check.

If you know the property, but don't know in which element you can find it, see the Index of Properties by PNR/TST Element on page 119.



Best Practices for Creating Rules

When you set up rules, you should keep the following guidelines in mind:

• Keep it simple

If you keep the rules as simple as possible it will be easier for yourself and others to locate possible problems and to re-use rules.

• Don't exceed the following numbers:

- A maximum of 10 rules per RuleFile

- A maximum of 20 RuleFiles per RuleSet

- A maximum of 50 RuleFiles or RuleSets per RuleLibrary

- An overall total of 100 RuleFiles

Creating a Simple Rule Here you learn how to create a simple rule containing an If condition, a Where statement, a message and an action.

For information on more complex rules including variables, for example, see Advanced Rules on page 31.

How to Create a RuleFile with a Rule

1. Open Rule Editor.

2. In the RuleFiles/Sets tab, click on the New RuleFile button or click on .

3. In the General Information tab, enter a name and a short description.

Example: Enter 'GP Car upsell rule' as the name and 'Ensure that car segment is in PNR if stay is greater than 2 days' as the description.

4. Enter a validity period (Activation Date and Expiration Date) to indicate the period during which the RuleFile can be used by RuleChecker.


18 Edition 4.0

5. Click on the Rule Details tab to start building your rule.

6. Click on 'To add a new rule, click Here'.

The Add Rule window opens.

7. Click on the blue links to define your rule elements.

A basic rule will usually contain the following elements:

- If conditions (mandatory): See If Conditions on page 21.

- Where statements: See Where Statements on page 23.

- Rule message (mandatory): See Rule Messages on page 27.

- Rule action: See Rule Actions on page 29.

In a more advanced rule, you can use the following additional elements:

- For Each condition: See For Each Conditions on page 31.

- Variables: See Variables on page 33.

- Variable conditions: See Variable Conditions on page 42.



8. When you have completed the rule, click on OK.

9. Click on the Save icon .

10. Click on the blue All RuleFiles link at the top.

The list of All RuleFiles/Sets now shows the new rule.


20 Edition 4.0

When Is a Rule Active?

To deactivate or activate a rule, you select or clear the Deactivate Rule check box in the Add or Modify Rule window.

However, this setting is only taken into account if the RuleFile itself is active.

When Is a RuleFile Active?

When you set up a RuleFile in Rule Editor, you can determine when it is activated and when it expires. By default, it is activated immediately without any further action.

RuleFiles expire when they exceed the specified expiration date. They are then denoted by .

Note: It is possible to modify expired RuleFiles. For example, you can reactivate them by modifying the activation and expiration dates.



If Conditions

What Is an If Condition?

In the If condition, you select the PNR or TST element that you want to check. A rule must contain at least one If condition. You need to add a separate condition for each PNR or TST element you want to check.

How to Create an If Condition

See How to Create a RuleFile with a Rule on page 17 for the full workflow of building a rule.

1. In the Add or Modify Rule window, expand the first condition.

2. Click on 'Specify the element to Check' and select the PNR or TST segment. Example: Air Itinerary Segment

If you are not sure which element you need to check, see the Data Dictionary on page 117.

3. Click on 'I Find' and specify the verb.

4. Click on 'At Least 1' if you need to change the required number of segments in the PNR.


22 Edition 4.0

Options for If Conditions

Click on the blue values to define the following options for an If condition:

Option Possible values

And/Or Not available for the first If condition. AND OR

I Find/I Don't Find FIND DO NOT FIND

How Many Elements? EXACTLY [N] AT LEAST [N] LESS THAN [N] BETWEEN [N-M] NOT BETWEEN [N-M] Where N and M represent the number of elements you are looking for.

Which PNR/TST Element?

Select the PNR or TST element that you want to check.

Click on to open a list of all available PNR and TST elements (see also Data Dictionary on page 117 if you need more information).



Where Statements

What Is a Where Statement?

For each If condition, you can enter one or more Where statements to check different properties of the selected element.

How to Create a Where Statement


1. In the Add or Modify Rule window, click on 'To add a Where statement, click Here'.

2. Select the property of the element you want to check. Example: Days Stay Duration

If you are not sure which property you need to check, see the Data Dictionary on page 117.


24 Edition 4.0

3. Define the verb for the Where statement. Example: Is Greater Than or Equal To

4. Enter the value to be checked. Example: 2



Options for Where Statements

Click on the blue values to define the following options for a Where statement:


And/Or/And Not/ Or NOT

AND AND NOT OR (not available for first Where statement) OR NOT (not available for first Where statement)

Which Property? To select the property of the PNR or TST element that you want to check, click on .

The properties available depend on the element type you selected for the If condition.

Which Verb?

The available Where statement verbs depend on the data type of the property. See the table below for more information.

Which Value?

The available Where statement values depend on the data type of the selected PNR or TST property.

Data Type Which Verb? Which Value?

Character IS CONTAINS

Allows you to find a string, a word or a sentence corresponding to the entered pattern. See How to Enter the Text You Want to Find below for more information.

Boolean IS TRUE FALSE

Numeric, Date or Time

EQUAL TO LOWER THAN LOWER THAN OR EQUAL TO GREATER THAN GREATER THAN OR EQUAL TO BETWEEN

Enter a number, date or time. The date or time format depends on the setting on your terminal. Either enter the value or select a variable. When BETWEEN is selected, two values must be entered. The second value must be greater than or equal to the first value.

How to Enter the Text You Want to Find

If you want to find a string, a word or a sentence in a PNR element

1. Create the Where statement, as described in How to Create a Where Statement on page 23.

2. When you select the verb, select Is or Contains. The Which Value dialog box appears.


26 Edition 4.0

3. Enter the string you are looking for in one of the following ways:

- Enter the text directly in the Enter Value field.

- Enter a string or substring in the Enter a String tab and click on Append.

Your entry is added to any string already shown in the Enter Value field.

- Select a special expression from the list of pre-formatted special expressions and click on Append. For details, see Using Special Expressions on page 44.

Your entry is added to any string already shown in the Enter Value field.

- Select a variable and click on Append. The variable must have been defined before. For details, see Variables on page 33.

The variable is added to the string shown in the Enter Value field.

Note: If you enter the string directly and do not use the Append button, make sure you enter special expressions and variables in square brackets [ ].

Note: Make sure that there are no trailing spaces at the end of the value. Spaces are taken into account when the rule is executed.



Rule Messages

What Is a Rule Message?

The rule message contains the text that will be displayed to the travel agent if the PNR meets the conditions in the rule.

A rule message is a mandatory element.

How to Create a Rule Message


1. In the Add or Modify Rule window, expand the Rule Message section.

2. Select at what time in the PNR processing the rule is checked. Example: Any

3. Specify the severity of the message. Example: Warning


28 Edition 4.0

4. Enter the message text. Example: Propose a car segment.

Options for Rule Messages

Click on the blue values to define the following options for the message:

Dialog box Possible values Explanation

When to apply the rule?

ANY End of Transaction Pricing Ticketing

This determines at what stage during the booking process RuleChecker will be launched to check the PNR against this rule. Example: If you select 'End of Transaction', RuleChecker will check the rule whenever an end-of-transaction command (ET, ER) is processed. This setting only applies if RuleChecker runs in point-of-sale (POS) mode. Note: This setting only becomes effective if you

have configured the triggering commands in the Point of Sale tab in the Administrator module (see Selecting Commands to Trigger RuleChecker in Point of Sale Mode on page 69).

Raise warning or error?

ERROR WARNING

Defines the error severity. Note: This setting determines whether

RuleChecker only displays a warning but continues with the PNR or whether an error is raised halting the PNR flow.

Message to display? Free text Defines the message displayed to the travel agent in the RuleChecker window.



Rule Actions

What Is a Rule Action?

A rule action contains the corrective action that is necessary to fix a PNR that fails the checks. Automatic actions are automatically carried out by RuleChecker. Manual actions are proposed to the travel agent in the RuleChecker window.

Rule actions are optional elements in a rule.

How to Create a Rule Action


1. In the Add or Modify Rule window, expand the Rule Actions section.

2. Decide if you want RuleChecker to automatically carry out the action if the conditions are met, or if you just want to propose the action to the travel agent. Example: Manually

3. Enter the action to be performed. Example: Select 'Send a Cryptic Command' and enter the command 'CAS'.


30 Edition 4.0

Options for Rule Actions


In the Add or Modify Rule window, open the Rule Actions section. Then click on the blue values to define the following options for the action:

Option Values Explanation

Manually/ automatically?

Manually Automatically

Select Manually to propose the action in the Send field in RuleChecker. Select Automatically to let RuleChecker automatically carry out the action if the conditions are true.

Which Action Send a Cryptic Command

Select Send a Cryptic Command, then enter the command. Example: FP CASH

Run a Smartkey Select Run a Smart Key, then enter its name or its shortcut. Example: TST_UPDATE or SHIFT ALT B

Run a Program Use this option to: • Run an .EXE program from its full path name. Example:

C:\Program Files\Microsoft Office\ Office10\ EXCEL.EXE • Open a specific document or website by entering:

[full path of the application] [space]["file name in inverted commas"]

Example: C:\Program Files\ Internet Explorer\ IEXPLORE.EXE "http://www.aa.com" Note: You first need to launch the .EXE file of the program.

You then type a space and enter the full path to the file in inverted commas.

Go to a Tab Select Go to a Tab to automatically open a module such as PNR or Cars from RuleChecker where you can enter missing information. Select the appropriate module from the list. Example: PNR



Advanced Rules More complex rules can contain For Each conditions, variables and variable conditions.

For Each Conditions

What Is a For Each Condition?

With a For Each condition, RuleChecker will check the entire PNR in order to find all the elements that meet the condition.

Even if an element is found that meets the conditions, RuleChecker will continue to check if there are other elements that also meet the rule (in contrast to an If condition where RuleChecker stops checking once the specified number of elements meeting the conditions is found).

This condition is only available as the first condition in a rule and only once per rule. It is optional. As for an If condition, you select the PNR or TST element and then specify Where statements, messages, actions, etc. as required.

Any actions specified in the rule will be performed for each element that meets the condition.

How to Create a For Each Condition


1. In the Add or Modify Rule window, click on the 'To add a new For Each Condition, click Here' link.

2. Click on 'Specify the element to Check' and select the PNR or TST segment.

If you are not sure which element you need to check, see the Data Dictionary on page 117.

Note: In an existing rule, you can convert a For Each condition into an If condition by selecting Edit > Convert Into If Condition from the menu.

How to Add a For Each Condition to an Existing Rule

If you have already created rules using normal If conditions only, and you decide that you want to loop through all the elements in the PNR, you can modify the rule and add a For Each condition at the beginning:

1. In the Add or Modify Rule window, click on the 'To add a new For Each Condition, click Here' link.

2. Select the PNR or TST element you are looking for.


32 Edition 4.0

Example: Using a For Each Condition

You want to build a rule that ensures that all passengers have an SSR DOCS element, which is needed to enter additional passenger information for the APIS (Advance Passenger Information System).

Condition 1 (For Each)

As the PNR can contain several passengers, the element number is stored as a variable.

For Each condition: For each Name element

Create variable: Then I set variable @PAX ASSOC to value Element Number

Condition 2 (If)

If statement: And If I don't find at least one Special Service Request element

Where statement: Where property Passenger Association is [@PAX ASSOC]

Rule message Then apply the rule at time of Any And display Error message Need DOCS element for passenger number [@PAX ASSOC]

If, for example, the PNR contains two passengers, RuleChecker will do the following: • If there is no SSR DOCS element whose passenger association is 2, the

error message 'Need DOCS element for passenger number 2' is displayed.

• Note that, for a variable that belongs to a For Each condition, the value is updated each time the specified element is found: For the first passenger in this example, the value is '1', and for the second passenger, the value is '2'.



Variables

What Is a Variable?

A variable allows you to extract and store a property of a PNR or TST element and then reuse it within the same RuleFile. You can use variables in your rule if the property you are looking for depends on the context and does not have a fixed value.

Any property of a PNR or TST element may be assigned to a Variable. Variables can be used in three ways:

• To dynamically create cryptic commands based on PNR information (rule action)

• To compare different data from the PNR (variable condition)

• To dynamically display PNR information within a rule message

Where and When Is a Variable Defined?

A variable is defined at rule level in an If or a For Each condition. It contains the value of a property in the PNR/TST element checked by the rule. The content of a variable can then be used in Where statements, rule messages and rule actions.

• Variables set up in an If condition can be used in any rule within the RuleFile.

• Variables set up in a For Each condition can only be used within the rule that contains the For Each condition.

Note: The variable must have been created before you can use it in a rule.

Naming Rules for Variables

The variable name:

• Must start with @

• Must be unique within the RuleFile

• Is case-sensitive

• Must be between one and 30 characters

You can use any alphanumeric character (A-Z and 0-9), but space and @ are not allowed.

Note: When you use the content of a variable - in a Where statement, message or action - you have to enter its name between square brackets “[“ and “]” (for example: [@LOCATION]).


34 Edition 4.0

How to Create a Variable


1. In the Add Rule or Modify Rule window, define the condition that has to be met.

2. Under this condition, click on the 'To Add a new variable, click Here' link.

3. To define the variable, click on one of the links in the 'I set variable' line.

4. In the Which Property to Be Stored in the Variable? dialog box that appears, enter the variable name.

Example: @var_airline

5. To define the property that will be stored in the variable, click on and select a property from the list.

6. Optional: If you want to apply a function on the value of the selected property, click on the Advanced button. See How to Apply a Function on a Variable on page 37 for more information.

7. Click on OK. The variable is ready to be used in the RuleFile.

When Is a Variable Initialised?

A variable is initialised if it contains a valid value. This is the case if the condition is met in which the variable is defined.

If a variable is not initialised in a PNR, RuleChecker will stop executing the rule.



Example: Initialising Variables

Condition 1

If statement: If I find exactly one AIR element

Create variable: Then I set variable @LOCATION to value OffPoint

The variable @LOCATION is initialised only if the condition is met (if exactly one AIR element is found).

Condition 2

The variable @LOCATION is used in the Where statement, the rule message and the rule action:

If statement: If I don't find at least one CarSegment element

Where statement: Where property Location is [@LOCATION]

Rule message Then apply the rule at time of Any And display Error message Please book a car at [@LOCATION]

Rule action And Automatically send a Cryptic command RM BOOK A CAR SEGMENT AT LOCATION [@LOCATION]

When a rule is executed, RuleChecker verifies if the variable contains a valid value.

If there is no Air segment in the PNR, condition 1 is not met and @LOCATION is not initialised. There is no possibility (and it is not logical) to verify condition 2.

The rule is checked, but no error/warning message is displayed.

Example: Using Variables

Below is an example rule created to propose a car booking if the outbound flight is found in the PNR and the duration of the stay is greater than three days.

Condition 1

If statement: If I find at least 1 Air Itinerary segment

Where statement And Where property Round Trip is true

Where statement And Where property Days Stay Duration is Greater than 3

Condition 2

A variable is needed because the element number of the outbound flight could vary depending on the number of passengers booked in the same PNR.

If statement: And If I find at least 1 Air segment

Create variable: I set variable @ElementID to Element Number

Rule message Then apply the rule at time of Any And display Warning message Please, propose CAR booking for Air segment [@ElementID]

Rule action And manually send a Cryptic command CAS[@ElementID]


36 Edition 4.0

The variable @ElementID is created to find the element number for the outbound flight. If the outbound flight element is found, a manual car booking transaction is proposed to the travel agent in the Send field.

Clicking on Send in RuleChecker provides the travel agent with a list of car availability.



Applying Functions on Variables

When to Apply a Function on a Variable

You can apply a function on the property value before it is stored in the variable, for example to extract a part of a string.

How to Apply a Function on a Variable


1. In the Add Rule or Modify Rule window, define the condition that has to be met in order to initialise the variable.

2. Under this condition, click on the 'To Add a new variable, click Here' link.

3. Click on one of the links in the 'I set variable' line.

4. In the Which Property to Be Stored in the Variable? dialog box that appears, enter the variable name.

5. To define the property that will be stored in the variable, click on and select a property from the list.

6. Click on the Advanced button.

7. Select the function to apply and enter the parameters.

The result of this calculation will be stored in the variable.


38 Edition 4.0

Options for Variable Functions

Depending on the data type of the PNR or TST property to be stored in the variable, different options will be available in the Apply a Function to the Selected Property dialog box:

Property Data Type

Function to Apply

Parameters

Character Left Specify the number of characters to be extracted from the selected property, starting from the left. Either enter a value directly or select a variable.

Right Enter the number of characters to be extracted from the property, starting from the right.

Substring Extracts a part of the property. Enter the character position from which you want to start and the number of characters to be extracted from there.

Extract Allows you to find a string, a word or a sentence in a property and store it in the variable. The value to be stored must be entered in curly brackets { }.

Either enter the string directly or click on to open a dialog box that helps you generate the string. See How to Extract Text and Store It in a Variable on page 39 for more information.

Add Before Enter a string to be added before the property.

Add After Enter a string to be added after the property.

Numeric / Currency

Add Enter the value to be added to the property or click on to select a variable.

Subtract Enter the value to be subtracted from the property.

Multiply Enter the number with which you want to multiply the value of the property.

Divide Enter the number by which you want to divide the value of the property. It must be different from 0.

Time AddHours Minutes

Add a number of hours and minutes to the time in the property.

Remove HoursMinutes

Subtract a number of hours and minutes from the time in the property.

Date AddDay Month

Add a number of days and months to the date in the property.

RemoveDay Month

Subtract a number of days and months from the date in the property.



How to Extract Text and Store It in a Variable

If you use the Extract function as function to apply, you can extract a string, a word or a sentence in a property and store it in the variable.

1. Follow the steps described in How to Apply a Function on a Variable on page 37 until step 7.

2. In the Apply a Function to the Selected Property dialog box, select Extract.

3. Click on to open the Which Function Param? dialog box.

4. Enter the string you want to extract in any of these ways:

- Enter a string directly in the Enter Regular Expression field.

- Enter a string or substring and click on Append to add it to the Enter Regular Expression field.

- Select a special expression from the list of pre-formatted special expressions and click on Append. For details, see Using Special Expressions on page 44.

- Select a variable and click on Append. The variable must have been defined before.

Consider the following rules:

• The value to be stored must be entered between curly brackets { }.

• If you enter the string directly and do not use the Append button, you must enter special expressions and variables in square brackets [ ].

• Use the Append as Value button if you want to use the value of the variable. This is indicated by curly brackets { }.

Example: To extract the fare value in a general remark (RM*FARExxxx), you can use the following special expression:

*FARE{[NUMERIC(2-6)][ANY_CHAR(1)][NUMERIC(1-2)]}


40 Edition 4.0

Example: Applying a Function on a Variable

You want to extract the home phone number from a Phone element. You can assume that the home phone number in a Phone element consists of 10 digits and is preceded by the text 'APH'.

Set up the following rule:

1. Click on 'To add a new Condition, click Here' and set up a condition:

If I find At Least 1 Phone element(s)

2. Click on 'To add a new Variable, click Here', then click on 'Specify the variable name'.

3. In the 'Which property to Be Stored in the variable?' dialog box that appears, enter @Home as variable name, select Text as property and click on the Advanced button.

4. In the 'Apply a Function to the Selected Property' dialog box that appears, select the function 'Extract' and click on in the Regular Expression field.

5. In the 'Which Function Parameter?' dialog box that appears, enter the following information:

- In the Enter a String tab, enter the text 'APH' and click on Append.

- In the Select a Special Expression tab, select Numeric and set the length to 10, then click on Append as Value.

The Regular Expression field will read as follows:

APH {[NUMERIC(10)]}

Note: Only the part between the curly brackets { } will be stored as the value of the variable.



6. Confirm all dialog boxes with OK until you are back in the Add Rule window.

The variable has now been defined as follows:

I set variable @HOME To Text part between {} when applying APH {[NUMERIC(10)]} regular expression

7. Enter the following rule message:

Then apply the rule at time of Any

And display Warning message The home phone number is: [@HOME].

Result in RuleChecker

In a PNR with the following phone element:

APH: 0102030405

RuleChecker would display the following message:

The home phone number is: 0102030405.


42 Edition 4.0

Variable Conditions

What Is a Variable Condition?

A variable condition is an equation that allows you to compare the value of a variable with either a numeric value or with another variable.

Your rule may require that you extract some values from the PNR, store them in variables, and then process some operations on these variables.

For example, a business rule requires that the lowest fare must always be equal to or lower than the ticketed fare and the highest fare.

Note: The variable(s) you want to compare must have been defined before in the RuleFile. See Variables on page 33 for details.

How to Compare Variables in a Variable Condition

1. In the Add Rule or Modify Rule window, specify the condition that has to be met and define the necessary variables.

See How to Create a Variable on page 34 for more information.

2. To compare variables, click on the 'To add a Variable Condition, click Here' link in the Add or Modify Rule window.

A new condition is added to the rule.

3. Click on the blue values to define the variable condition.

4. Click on OK. The variable condition is ready to be used in the RuleFile.

Options for Variable Conditions

Click on the blue values to define the following options for the variable condition:


And/Or AND OR

Which Variable? Select a variable from the list of variables that have been defined for the RuleFile.

Is/Is Not IS IS NOT

Compared With? EQUAL TO LOWER THAN GREATER THAN LOWER THAN OR EQUAL TO GREATER THAN OR EQUAL TO BETWEEN Either enter a value in the field or select a variable.



Example: Comparing Variables

There is a promotion on car bookings and you have to make sure that your customer will not pay more than a certain maximum amount. This maximum amount is defined in a General Remark element in the PNR (using the format RM PRICE MAX 150, for example).

Condition 1

If statement: If I find At least 1 Car Segment element(s)

Create variable: I set variable @Rate to Rate Guarantee Amount

Condition 2

Select the property Text for this variable, then click on Advanced, choose the Extract function and define the following regulare expression:

If statement: If I find At least 1 General Remark element(s)

Create variable: I set variable @PromoLevel To Text part between {} when applying PRICE MAX {[NUMERIC(1-3)]} regular expression

Condition 3

Click on 'To add a new Variable condition click Here' to compare the two variables:

If statement: And If [@Rate] Is Greater Than [@PromoLevel]

Condition 4

Select the property Rate Guarantee Amount, then click on Advanced and choose the Subtract function:

If statement: And If I find At Least 1 Car Segment element(s)

Create variable: I set variable @Saved To Rate Guarantee Amount - [@PromoLevel]

Actions

Rule message: Then apply the rule at time of Any And display Warning message You will not pay [@Rate] but [@PromoLevel]. You saved :[@Saved]


44 Edition 4.0

Using Special Expressions

What Is a Special Expression?

Special expressions describe sets of strings. They allow you to find specific strings in a text, such as particular characters, words, or patterns of characters.

When to Use Special Expressions

Rule Editor offers a number of preformatted special expressions that you can use to find specific strings or words in a PNR element. These special expressions can be used in:

• Where statements

• Variables (if a function is applied)

For example, you can find a complex string by combining different pre-formatted special expressions and normal characters.

Example 1

To check for a Name element starting with S and ending with H:

If I Find at least 1 Name element(s)

Where Last Name Is S[ANY_CHARACTER(?)]H

Example 2

To match the names “SMITH” and “SOUTH” and “SALTY WATER WASH” (Name element that starts with S, has a T as fourth character and ends with H):

If I Find at least 1 Name element(s)

Where Last Name Is [START_OF_FIELD]S[ALPHA(2)]T [ANY_CHARACTER(?)]H[END_OF_FIELD]

You find a more detailed example under Example: Applying a Function on a Variable on page 40.



List of Pre-formatted Special Expressions

The following table shows the pre-formatted special expressions that RuleChecker allows you to use in a Where statement or when you apply a function on a variable.

Special Expression Value or Length Matches

ALPHA Is (N) Is between (N-M)

Any alphabetic character (A, B, C...)

ALPHA_NUMERIC Is (N) Is between (N-M)

Alphabetic character or number

ALPHA_SYMBOL Is (N) Is between (N-M)

Alphabetic character, symbol (/;*$@#!?) or space

ANY_CHAR Is (N) Is between (N-M)

Alphabetic character, number, symbol (/;*$@#!?) or space

ANY_CHAR(?) 0 or more characters

BLANK Is (N) Is between (N-M)

Spaces

END_OF_FIELD End Of Data - no other data exists behind For example, SMITH[END_OF_FIELD] finds “MR SMITH” but not “MR SMITH JOHN”

START_OF_FIELD Start of data. For example, [START_OF_FIELD]US finds “US 123” but not “123 US”

IN_LIST List of values separated by commas: (A,B,C or 1,2,3)

Any of a set of literal values, separate each value with a comma

NUMERIC Is (N) Is between (N-M)

Number

NUMERIC_SYMBOL Is (N) Is between (N-M)

Number, symbol (/;*$@#!?) or space

SYMBOL Is (N) Is between (N-M)

Symbol (/;*$@#!?) or space

NUMBER Equal (=N) Compare a number from the first number found to the last consecutive one to value N.

Lower or equal (<=N) Finds numbers less than or equal to NN

Lower (<N) Finds numbers less than N

Greater or equal (>=N) Finds numbers greater or equal to N

Greater (>N) Finds numbers greater than N

Between (N-M) Finds numbers between N and M


46 Edition 4.0

Testing RuleFiles

When to Test a RuleFile from Within Rule Editor

Rule Editor allows you to simulate and test RuleFiles as you build them. This runs the rule but does not perform any actions defined in the rule.

You should test any RuleFile from within Rule Editor prior to a assigning it to a RuleSet or RuleLibrary. This helps you ensure that your rules work according to the specifications that you have defined, and that the correct results are returned.

How to Test a RuleFile from Within Rule Editor

1. Retrieve or create a PNR that you can check against your RuleFile.

2. In the RuleFiles/Sets tab in Rule Editor, highlight or open the RuleFile you want to test and click on .

This opens the Test RuleFile results window.

The Test RuleFile window shows the following sections:

• PNR - displays the PNR that was used to test the RuleFile.

• Rules Execution Summary - displays the status of the tested rules as well as the status of the individual rule conditions and elements.

Check these sections to see if they show the expected results.



When to Test a RuleFile in Selling Platform

Before you deploy rules to the travel agents, you should test any new RuleFile in Selling Platform. You should only do this after you have tested the rule in Rule Editor.

How to Test a RuleFile in Selling Platform

1. Associate the new RuleFile to a RuleLibrary that has been published only to your own terminal.

2. To replicate the new RuleFile to your terminal, open the RuleChecker window and select Action > Force QC Replication.

3. In Selling Platform, make sure you work in the Amadeus Training environment.

4. Retrieve or create a PNR that you can check against your RuleFile.

5. To associate the new RuleFile to the PNR, add a confidential remark (RC element) in the following format:

RC Rule-<RuleFile/Set Name>

6. Click on to start RuleChecker in OND mode.

7. Check if RuleChecker responds as expected.

You find an example of the complete workflow under Example: Creating a Rule and Testing It in Selling Platform on page 102.


Chapter 5

Grouping RuleFiles into RuleSets

What Is a RuleSet?

A RuleSet is a group of RuleFiles that logically belong together and that will be simultaneously executed by Quality Control RuleChecker.

Example: The RuleSet Car Bookings contains all the RuleFiles that are used to check car bookings

Here is an example of a RuleSet:

When Should I Use RuleSets?

Grouping RuleFiles into RuleSets is not mandatory, but it facilitates rule management and deployment.

For example, if you want to associate RuleFiles or RuleSets to an office ID for automatic association to all PNRs, it saves time if you can select a few RuleSets per office instead of a long list of individual RuleFiles.

Using RuleSets also speeds up RuleChecker processing at execution time.

When Is a RuleSet Active?

When you set up a RuleSet in Rule Editor, you can determine when it is activated and when it expires. By default, it is activated immediately without any further action.


50 Edition 4.0

RuleSets expire when they exceed the specified expiration date. They are then denoted by .

Note: It is possible to modify expired RuleSets. For example, you can reactivate them by modifying the activation and expiration dates.

How to Create a RuleSet and Add RuleFiles

1. In Rule Editor, click on , or click on New RuleSet in the All RuleFiles/Sets tab.

2. Enter a name and a description for the RuleSet.

3. Enter a validity period (Activation Date and Expiration Date) to indicate the period during which the RuleSet can be used by RuleChecker.

4. To add the required RuleFiles to the RuleSet, click on the RuleFiles Association tab.

5. In the Rule Files Association tab, select the RuleFiles you want to include and click on Add>.

The RuleFile is now displayed on the right under Associated RuleFiles.

Note: If you need to remove a RuleFile from the current RuleSet, select the RuleFile name from the list of Associated RuleFiles and click on Remove.

6. Click on to save the RuleSet.


Chapter 6

Publishing RuleFiles and RuleSets in RuleLibraries

Workflow: Publishing Rules Publishing rules means making them available to the travel agents so that they can use the rules to check PNRs. Once you have created your rules in Rule Editor (and grouped them into RuleSets if appropriate), these rules need to be deployed to the travel agents' terminals.

You need to do go through the following publishing process:

Add all the RuleFiles and RuleSets that you want to publish together to a RuleLibrary. See How to Create a RuleLibrary and Add Rules on page 54. Publish to the user group that will to use the RuleFiles and RuleSets contained in the library. See Publishing a RuleLibrary on page 55. Either wait until the next day for automatic download or force immediate rule replication from RuleChecker. See RuleChecker Configurations on page 61.

Once you have completed this process, your RuleFiles or RuleSets can be associated to PNRs in order for RuleChecker to check them for compliance. See Associating Rules to PNRs on page 81 on page 81 for more information.


52 Edition 4.0

What Is a RuleLibrary?

RuleLibraries are containers that are used to group together and publish the RuleFiles and RuleSets that will be deployed together on travel agent terminals.

They can be published (deployed) to different configuration levels (office group, office or certificate) and therefore allow for flexibility in how quality control rules can be distributed to each travel agent or agency.

The notion of RuleLibraries is not visible to the travel agents who use RuleChecker. They only see the contents of a RuleLibrary, i.e., the RuleFiles and RuleSets belonging to it, but not the RuleLibrary itself.

How Are RuleFiles, RuleSets and RuleLibraries Deployed?

Both RuleFiles and RuleSets can be associated to a RuleLibrary. A RuleLibrary can then be published to different configuration levels.

Chapter 6 Publishing RuleFiles and RuleSets in RuleLibraries


At Which Level Should I Publish a RuleLibrary?

The level to which you publish the RuleLibrary depends on the number of agents who need to use the RuleFiles or RuleSets.

As a general rule, you should publish to the highest possible level in your office hierarchy, because it makes the administration easier. If you publish, for example, at office group or office ID level, the rules will be replicated to all the certificates (CIDs) under that office group or office.

If necessary, you can also create libraries that contain rules you only want to publish to specific CIDs.

• If the RuleFiles and RuleSets in the RuleLibrary are required for all agents in your office, you should publish the RuleLibrary at 'My Office' level (all agents belonging to this office ID).

• If you want the RuleLibrary to be available only for individual agents, you will need to publish it to each of the certificates, one at a time.

In most cases it will be convenient to create a separate library for each configuration level to which you want to publish.

The rules available to the agent are the sum of the rules published to his office group, office ID and certificate.

Example 1

• RuleSet X (containing RuleFiles A and B) packaged in RuleLibrary 1 may be published/deployed to travel agency GoTravel.

• RuleSet Y (containing RuleFiles C and D) packaged in RuleLibrary 2 may be published/deployed to travel agent Smith. This means that all four RuleFiles A, B, C and D are deployed for travel agent Smith: A and B are inherited from the office ID and C and D are directly deployed to his CID.

Example 2

You are an administrator who sets up and tests new rules. You need one library that contains all RuleFiles and RuleSets published at office ID level and another library published only to your CID that contains the new rules you want to test.


54 Edition 4.0

How to Create a RuleLibrary and Add Rules 1. In Rule Editor, click on the All RuleLibraries tab.

2. To create a new library, click on or on the New RuleLibrary button.

3. Enter a name and a description for the RuleLibrary. Example: GP Rule lib

4. Click on the RuleFiles/Sets Association tab to add the required RuleFiles or RuleSets to the RuleLibrary:

5. In the RuleFiles/Sets Association tab, select the existing RuleFiles or RuleSets to be associated to the RuleLibrary, then click on Add>.

The RuleFile is now displayed on the right under Associated RuleFiles/RuleSets.

Note: If you need to remove a RuleFile from the current RuleLibrary, select the RuleFile or Set name from the list of Associated RuleFiles and click on <Remove.

6. Click on to save the RuleLibrary.



Publishing a RuleLibrary You can publish RuleLibraries either directly from Rule Editor or from the RuleFiles/Sets tab in Administrator.

How to Publish a RuleLibrary from the Rule Editor

1. In Rule Editor, click on the All Rule Libraries tab.

2. Select a RuleLibrary and click on Publish.

The Publish Rule Library dialog box is displayed.

3. Select the configuration level that you want to publish the RuleLibrary to.

Choose between:

- My Office Group. This option is only displayed if your office belongs to an office group and if this office group does not have access restrictions.

If your office belongs to an office group with access restrictions, this option is not displayed and you only have access to your own office and its certificates.

- My Office

- My Certificate

- Office. If your office belongs to an office group, you can enter any office ID belonging to your office group. Alternatively, click on to select an office ID from the list.

- Certificate. You can enter any certificate belonging to your office group or office.

4. Select the check box at the bottom of the dialog box if you want to open Administrator once you have clicked on OK.

This will allow you to check the list of RuleLibraries currently published to the selected configuration.

5. Click on OK to publish the selected RuleLibrary.


56 Edition 4.0

How to Publish RuleLibraries from the Administrator

Instead of publishing from Rule Editor you can also activate RuleLibraries in Administrator:

1. Open Administrator for the appropriate configuration level and click on the RuleFiles/Sets tab.

The upper part of the screen shows the list of RuleLibraries that have been published to the current configuration level.

2. To add a new RuleLibrary to the list, click on and select Add from the menu that appears. This will insert a new line. (If you don't see the , click in one of the lines with the existing libraries.)

3. Click in the new line, then open the drop-down list and select the RuleLibrary you want to publish to the current configuration.

The list contains all the RuleLibraries that have been set up in your office group or office. These are the same libraries that you see in the All RuleLibraries tab in Rule Editor.



4. Click on Save.

How to Replicate Changes to RuleFiles, RuleSets and RuleLibraries

If you have made changes to RuleFiles or RuleSets, published new RuleLibraries or added RuleFiles to existing libraries, these changes need to be replicated to the associated terminals.

• Automatic Replication

Any changes will be automatically downloaded form the central rules repository to each terminal on the following day, when RuleChecker is launched for the first time.

• Force Immediate Replication

If rules have been updated and you do not want to wait until the next day for these changes to take effect, you can open the RuleChecker window and select Action > Force QC Replication to download them immediately. This needs to be done on each terminal.

Do I Have to Republish RuleLibraries?

A RuleLibrary only needs to be published to a configuration once.

Afterwards, you can add, remove or modify the RuleFiles contained in it as you like, without having to republish. Any changes will be replicated automatically, either the next day or immediately by forcing Quality Control replication.

How to Remove a RuleLibrary from a Configuration

You can remove published RuleLibraries from all or selected configuration levels. For example, if you published a library to an entire office ID, you can then remove it from one or more certificates if required.

1. Open Administrator for the appropriate configuration level and click on the RuleFiles/Sets tab.

The upper part of the screen shows the list of RuleLibraries that have been published to the current configuration level.

2. To remove a RuleLibrary, click on at the end of the line and select Remove from the menu that appears.

During the next Quality Control replication, all RuleFiles and RuleSets belonging to this library will be automatically removed from the terminals of the selected configuration level.


Chapter 7

What Is Administrator?

The Administrator component of Amadeus Quality Control Manager allows you to configure RuleChecker settings at office group, office and certificate level.

When you open Administrator, you choose which level you want to work on. For more information on configuration levels, see Deploying RuleChecker Settings to the Agents on page 61.

The following tabs are available:

• RuleChecker Bypass to determine if travel agents are allowed to bypass RuleChecker and, if yes, how the bypassed PNRs are tracked.

For details, see Configuring RuleChecker Bypass on page 66.

• Point of Sale to select the transactions at the different stages of PNR processing that will trigger RuleChecker in point-of-sale mode.

For details, see Selecting Commands to Trigger RuleChecker in Point of Sale Mode on page 69.

• Action from RuleChecker to select the queues to which the travel agent can send PNRs and to select transactions that the travel agent is not allowed to enter in RuleChecker.

For details, see How to Define the Queues to Be Used on page 75 and How to Block Cryptic Commands in RuleChecker on page 76.

• RuleFiles/Sets to publish RuleLibraries for the current configuration level.

For details, see How to Publish RuleLibraries from the Administrator on page 56 and Associating Rules to All PNRs Processed by an Office on page 83.

• RuleChecker Execution to define what RuleChecker will do, for example, if no RuleFiles or RuleSets are associated to a PNR.

For details, see Customising RuleChecker's Behaviour on page 77.


60 Edition 4.0

How to Start Administrator 1. In the Selling Platform main menu bar, click on to open Amadeus Quality

Control Manager (you may be asked to enter a password).

2. In the Amadeus Quality Control Manager, click on Launch Administrator.

3. Select the configuration level you want to work on. Choose between:

- My Office Group. This option is only displayed if your office belongs to an office group.

- My Office

- My Certificate

- Office. If your office belongs to an office group, you can enter any office ID belonging to your office group - or click on to select an office ID from the list.

- Certificate. You can enter any certificate belonging to your office group or office.

Note: If your office belongs to an office group with access restrictions, you only have access to your own office and its certificates.

Depending on your selection, the changes you make in Administrator will be automatically inherited by the lower configuration levels (for more information, see also How to Inherit RuleChecker Settings from a Higher Level on page 62).

4. Click on OK. The Administrator screen opens.


Chapter 8

Deploying RuleChecker Settings to the Agents

RuleChecker Configurations

What Is a RuleChecker Configuration?

A RuleChecker configuration contains both the rules and the RuleChecker settings that apply to a specific office group, office or certificate.

When you access the Administrator module, you are asked to select a configuration level.

Everything you then enter or modify in the Administrator session will be applied to the selected level and automatically inherited by any lower levels. See also How to Inherit RuleChecker Settings from a Higher Level on page 62.

You can also copy settings from one configuration to another at the same level. See How to Copy RuleChecker Settings to Another Configuration on page 64 for more information.

Which RuleChecker Configurations Can I Set?

Depending on the setup in WebConfig, you as the administrator have access to the RuleChecker configurations of the following configuration levels:

• Office group

The administrator has access to all rules defined within the office group and to all RuleChecker configurations at office group, office and certificate level.

• Office group with access restrictions

Within an office group, access restrictions can be defined at office level.

If an office is set to restricted access, the administrators only have visibility of the rules and configurations for their specific office.

• Office

If the office does not belong to an office group, the administrator has access to all rules defined within the office group and to all RuleChecker configurations at office and certificate level.


62 Edition 4.0

What If Several Administrators Work on the Same Configuration?

If there are several administrators in your office or office group who are allowed to work with Amadeus Quality Control Manager, it can happen that they work on the same rule or on the same RuleChecker configurations at the same time.

In this case, the last one who saves the changes will overwrite the changes saved before by another administrator.

How to Switch to Another Configuration

If you have finished working on the current configuration (Example: your office ID) and you now want to work on a different one (Example: a travel agent's certificate), follow these steps:

1. Click on Save at the bottom of the screen to save your current changes.

2. Click on the Administrator link on the left-hand side of the screen.

3. Select the configuration you now want to work on and click on OK.

Inheriting and Copying Settings

How to Inherit RuleChecker Settings from a Higher Level

RuleChecker settings can be applied at different levels of the organisational hierarchy: Office group, office and certificate.

When you access the Administrator module, you are asked to select a configuration level.

Everything you then enter or modify in the Administrator session will be applied to the selected level and automatically inherited by any lower levels.

The logic is as follows:

Office Group -> Office -> CID

Example: If you select 'My Office Group' when you access Administrator, all your entries will be applied to the entire office group, including all the offices and all the certificates belonging to it.

The configuration level currently selected is displayed at the top of the screen.

Chapter 8 Deploying RuleChecker Settings to the Agents


At Which Level Should I Configure the Settings?

As a general rule, you should always set up the RuleChecker parameters at the highest possible level in the hierarchy: at office group level, if there is an office group, or at office ID level, if there is no office group.

Always start working at the highest level and configure as much as possible at that level. This concerns, for example, the bypass settings, the triggering commands and the queue settings.

Only set those parameters at office or certificate level that you want to be different from the higher level.

Example: You want all the agents in your office group to be able to bypass RuleChecker. You therefore select the Allow RuleChecker Bypass option at office group level.

However, agent XY is new, and you do not want him to bypass RuleChecker. You then select his certificate and disable the Allow RuleChecker Bypass option.

From Which Level Is a Parameter Inherited?

Each parameter in Administrator is displayed with an icon that shows at which configuration level it was set:

Indicator Name Description

TOP Indicates that a parameter is configured at levels higher than the office group. This can be at vendor or at Amadeus level.

Office Group

Indicates that a parameter is configured at office group level.

Office Indicates that a parameter is configured at office level.

Certificate Indicates that a parameter is configured at CID level.

Example:

The Allow RuleChecker Bypass option is currently configured at office level. The parameter is therefore displayed with the office level icon .

For a specific certificate, you want to disable this option. As soon as you clear the check box, the icon changes to certificate level .


64 Edition 4.0

How to Copy RuleChecker Settings to Another Configuration

When you have set up parameters for an office or a certificate, you can also copy these settings to another configuration within the same level, for example from one office to another office or from one certificate to another certificate:

Note: This is only possible if your office belongs to an office group and if your office is not set to restricted access.

1. Launch Administrator and select the level whose RuleChecker configuration you want to copy. This can either be an office or a certificate.

2. In the Administrator screen, click on the Copy button.

3. In the dialog box that appears, enter the office or the certificate to which you want to copy the current configuration.

Note: You can only copy configurations within the same level.


Chapter 9

Configuring RuleChecker in Administrator

Workflow: Deploying RuleChecker Settings The Administrator module allows you to configure the different RuleChecker settings and deploy them to the agents' terminals.

See: How to Start Administrator on page 60

Configuring RuleChecker Bypass on page 66.

Selecting Commands to Trigger RuleChecker in Point of Sale Mode on page 69

How to Display Informative Messages for a PNR on page 74

How to Define the Queues to Be Used on page 75

How to Block Cryptic Commands in RuleChecker on page 76

How to Publish RuleLibraries from the Administrator on page 56

Associating Rules to All PNRs Processed by an Office on page 83

What If no Rule Is Associated to a PNR? on page 77

What If an Associated Rule is Missing? on page 77

Which Rules Apply If Another Office Is Responsible for the PNR? on page 78

What If the PNR Has no Active Itinerary? on page 79

How to Add RF Elements to Track Checked PNRs on page 80


66 Edition 4.0

How to Replicate Changes to RuleChecker Configurations

Any changes you make in Administrator, with the exception of triggering commands and RuleLibraries, become effective immediately as soon as you click on Save.

Changes to the Triggering Commands and RuleLibraries

• Automatic Replication

Any changes will be automatically updated on each terminal on the following day, when RuleChecker is launched for the first time.

• Force Immediate Replication

If you change the triggering commands, you must close and restart Amadeus Selling Platform twice before RuleChecker will take the changes into account.

If you have made changes to RuleFiles, RuleSets or RuleLibraries and you want them to be replicated immediately, select Action > Force QC Replication from the RuleChecker window,

Configuring RuleChecker Bypass In order to allow travel agents to bypass non-compliant PNRs, the bypass option needs to be enabled in the Administrator module of Amadeus Quality Control.

How to Allow Travel Agents to Bypass RuleChecker

To allow travel agents to bypass RuleChecker and continue to process PNRs even if they are not compliant:

1. Open Administrator for the appropriate configuration level and click on the RuleChecker Bypass tab.

2. Select the Allow RuleChecker Bypass check box.

How to Enforce a Password When Bypassing RuleChecker

To prompt the travel agent for a password when he or she wants to bypass RuleChecker for a non-compliant PNR:

1. Open Administrator for the appropriate configuration level and click on the RuleChecker Bypass tab. Make sure the Allow RuleChecker Bypass check box is selected.

Chapter 9 Configuring RuleChecker in Administrator


2. Select the Set Bypass Password check box.

3. Type the password in the Set Bypass Password field.

How to Track Bypassed PNRs

To be able to track why a PNR was bypassed, you can set one or more of the following tracking options:

Create a General Remark each time RuleChecker is bypassed

1. Open Administrator for the appropriate configuration level and click on the RuleChecker Bypass tab. Make sure the Allow RuleChecker Bypass check box is selected.

2. Select the Create a General Remark check box to automatically create a General Remark element in bypassed PNRs.

3. Insert up to 30 characters of free-flow text.

If you select this option, remarks with the specified text will be automatically inserted in bypassed PNRs. They have the following format:

RM FREE FLOW TEXT/QC/BYPASS/DATE/TIME/OFFICEID


68 Edition 4.0

Send bypassed PNRs to a bypass queue

1. Select the Send Bypassed PNRs to Bypass Queue check box.

2. Select the bypass queue number (or nickname) and category number.

Bypassed PNRs are automatically sent to the specified queue without additional information.

Send a structured message to a message queue

1. Select the Send Messages to Message Queue check box.

2. Enter the message queue number (or nickname) and category number.

Messages are automatically sent to the specified queue in the following format:

QE97 QC/BYPASS/[DATE]/[TIME]/[OFFICEID]/[RECLOC]/ [TRANSACTION CODE]

[BYPASSED RULE FILE]/[BYPASSED RULE IDs]//

If several rule files have been bypassed, the message will contain an additional row for each additional bypassed rule file.

Example:

QE97 QC/BYPASS/15SEP04/1200/NCE1A0900/ABC123/ER

TEST RULE B/1,2,3//

The last row of the above example shows that rules 1, 2 and 3 in RuleFile TEST RULE B were bypassed.

Note: Automatic tracking of bypassed PNRs is not possible if RuleChecker is triggered by a neutral triggering command (see also How to Use Neutral Triggering Commands on page 71).



Selecting Commands to Trigger RuleChecker in Point of Sale Mode

What Are Triggering Commands?

Triggering commands are the transactions that, at the different stages of PNR processing, will automatically launch RuleChecker in point-of-sale mode.

You select these transactions in the Point of Sale tab in Administrator. You can define up to 22 triggering commands.

RuleChecker will be launched automatically as soon as it intercepts one of the triggering commands that you have defined. RuleChecker verifies that the PNR complies with the associated rules and only sends the triggering commands on to the distribution system if the PNR passes the quality checks.

If an error is found, the commands are not sent further on to the distribution system. If, for example, you use TTP as a triggering command, the ticket will not be issued if the PNR contains errors.

Notes:

• If you want to run RuleChecker in point-of-sale (POS) mode, you must define at least one triggering command.

If you do not select any commands, RuleChecker can only be launched in on-demand (OND) mode.

• If you change the triggering commands, you must close and restart Amadeus Selling Platform twice before RuleChecker will take the changes into account. Alternatively, you can wait for the automatic update that takes place every day, when RuleChecker is launched for the first time on a terminal.

• If you want to send the triggering command by a Smartkey, make sure it is the last command in the Smartkey, as only the last command can be intercepted by RuleChecker.

What Are Triggering Command Families ?

The transactions that can be used to trigger RuleChecker are grouped into the following command families:

Command Family Commands

End of Transaction

ER, ET, EF, ETK, ERK,QE, QER, QF, QFR, QM, RR, BT Note: RR can only be used in the command page.

Ticketing TTP, TTR, TTM, INE, INV, IMP, ITR

Pricing FXP, FXU, FXB Note: These commands can only be used in the command

page.

Neutral Any other command that does not belong to the above command families. Note: With neutral triggering commands, the automatic

tracking of bypassed PNRs is disabled (see also Configuring RuleChecker Bypass on page 66).

You can add additional parameters to these commands if required.


70 Edition 4.0

How to Select the Commands to Trigger RuleChecker

1. Open Administrator for the appropriate configuration level and click on the Point of Sale tab.

2. To enter a triggering command, click in the Command field and then either click on to select a command from the list or enter it directly.

The associated category will automatically be displayed in the Command Family field.

If you don't find your command in the list

The drop-down list only contains the commands associated to the End of Transaction, Ticketing and Pricing command families. However, you can enter any other command directly in the Command field, and it will automatically be associated to the 'Neutral' command family.

3. Optional: In the Parameters field, you can enter additional parameters to be added after a triggering command as free-flow text.

4. To add a new line for another command, click on and select Add or Insert from the menu. If you don't see the arrow, click in a field first.

To delete a command, click in the line, then click on and select Remove from the menu.

The same menu also allows you to copy, cut and paste lines.

Note: If you modify triggering commands, you must close and restart Amadeus Selling Platform twice - or wait until the next day - before RuleChecker will take the changes into account.



How to Use Neutral Triggering Commands

A neutral triggering command is any command that does not belong to the pre-defined end-of-transaction, ticketing or pricing command families.

You proceed in the same way as described above, but, instead of selecting one of the commands from the list, you type in the command that you want to use directly in the Command field.

Note: With neutral triggering commands, the automatic tracking of bypassed PNRs does not work (see also How to Bypass RuleChecker on page 96).

How to Use Additional Parameters in a Triggering Command

In the Parameters field in the Point of Sale tab, you can enter additional parameters to be added after a triggering command as free-flow text.

Examples:

• For the command QE, enter the parameter /BRUBB213T/0C0 to launch RuleChecker each time a PNR is sent to queue 0, category 0 of the specified branch office.

• For the command FXP, enter the parameter /R,ET to launch RuleChecker each time a command to exempt taxes is entered.

What Happens If Rules Are Linked to Triggering Commands

In addition to the general triggering commands you select in the Point of Sale tab in Administrator, you can link a specific rule to a triggering command family when you define the rule message in Rule Editor.

This allows a more precise check of the PNR in point-of-sale mode as the warning or error will be displayed at the right time.

If rules linked to the current triggering command fail the check, they will be displayed in the RuleChecker window either with the Error icon (stops the PNR flow) or with the Warning icon (does not stop the PNR flow). Related manual actions are proposed, automatic actions are run.

Rules not linked to the current triggering command will also be checked. But if they fail the check, they will be displayed with the Information icon (provided that the Show Informative Messages check box is selected). Any automatic actions defined will run.


72 Edition 4.0

Note: All rules linked to a PNR are executed when RuleChecker is triggered. Any rule that has an automatic action and is not passed will launch the automatic action, even if the rule is linked to a different triggering command family.

Example: Linking Rules to Triggering Commands The following example illustrates how rules are applied to a PNR, depending on the triggering command.

Note that all the rules linked to a PNR are executed when RuleChecker is triggered. Any rule that has an automatic action and is not passed will launch the automatic action, even if the rule is linked to a different triggering command family.

1. Set up two rules:

- GP Car Upsell Rule, triggered by end-of-transaction commands

- GP - Address Check Rule, triggered by ticketing commands

2. Add these rules to a library that is published to your CID.

3. In the RuleChecker window, select Action > Force QC Replication.

4. Create a PNR and add these rules manually to the PNR:

RC RULE-[RuleFile name]

Result at ET

• Rule GP Car Upsell (triggered by end-of-transaction commands) is displayed as a warning message.

• Rule GP - Address Check (triggered by ticketing commands) is displayed as an informative message. If an automatic action is defined for this rule, it will be carried out.



Result at TTP

• Rule GP - Address Check (triggered by ticketing commands) is displayed as an error message.

• Rule GP Car Upsell (triggered by end of transaction) is displayed as an informative message. If an automatic action is defined for this rule, it will be carried out.

Conclusion

This shows that all the rules linked to a PNR are executed when RuleChecker is triggered. Any rule that has an automatic action and is not passed will launch the automatic action, even if the rule is linked to a different triggering command family.


74 Edition 4.0

Displaying Informative Messages

What Are Informative Messages?

Informative messages are displayed with an in the RuleChecker window.

They show the information relative to a rule associated to the PNR but not associated to the current triggering command that launched RuleChecker.

For more information, see What Happens If Rules Are Linked to Triggering Commands on page 71.

Example:

Rule T is linked to the Ticketing command family. Rule E is linked to the End of Transaction command family.

If RuleChecker is triggered by an end-of-transaction command, RuleChecker will display the warning or error message related to Rule E and run the defined actions. It will also run any automatic actions related to rule T.

If Informative messages are configured to be shown, RuleChecker will display an informative message for rule T associated to the Ticketing command family.

How to Display Informative Messages for a PNR

1. Open Administrator for the appropriate configuration level and click on the Point of Sale tab.

2. Select the Show Informative Messages check box.

3. Click on Save.



Selecting Queues from RuleChecker

When to Define Queues to Be Used from RuleChecker

If you want travel agents to place PNRs on queues directly from RuleChecker, you need to enter these queues in the Administrator module.

The list of queues you define here will be displayed to the agents when they use RuleChecker's Queue PNR functionality (see also Placing PNRs on Queues on page 97).

How to Define the Queues to Be Used

1. Open Administrator for the appropriate configuration level and click on the Action From RuleChecker tab.

2. In the Define Queue To Use From RuleChecker section, enter the queue number, name and category.

3. If the queue is only used by one or more offices in your office group, enter the Office ID.

4. To add another queue, click on .

Note: This action does not create the queue. Make sure that it already exists and that Amadeus Extended Ownership Security (EOS) agreements are set correctly.

Blocking Commands in RuleChecker

When to Block Commands in RuleChecker

You may want to prevent travel agents from entering certain commands in the Send Transaction field in the RuleChecker window.

You can specify different commands depending on the triggering command family.

Note: In addition, any transactions selected as triggering commands (in the Point of Sale tab in Administrator) will automatically be blocked if they are entered manually in the Send Transaction field in RuleChecker.


76 Edition 4.0

How to Block Cryptic Commands in RuleChecker

1. Open Administrator for the appropriate configuration level and click on the Actions From RuleChecker tab.

2. In the Enter Transactions Not Allowed in RuleChecker section, fill in the fields as follows:

- Separate commands using semicolons.

- End of Transaction Command, Pricing Command, Ticketing Command and Neutral Command fields

Specify any commands the travel agent is not allowed to enter whenever RuleChecker is triggered by a command from one of these families.

Example: If RuleChecker is triggered with ER and you want to prevent the travel agent from entering ET and ETK, enter ET; ETK in the End of Transaction Command field.

- Any Command field

Enter the commands that travel agents are never allowed to enter, independent of the command that triggered RuleChecker.

Example: If you want to prevent travel agents from entering AP, no matter which command triggered RuleChecker, enter AP in the Any Command field.



Customising RuleChecker's Behaviour The RuleChecker Execution tab in the Administrator module allows you to define various options for RuleChecker.

What If no Rule Is Associated to a PNR? You can define what RuleChecker will do if no RC RULE element is associated to the PNR and if there is no automatic RuleFile/Set association for the configuration level:

1. Open Administrator for the appropriate configuration level and click on the RuleChecker Execution tab.

2. In the Prompt to Associate RuleFile/Set field, choose between:

- Prompt to display a list of available RuleFiles/Sets to the travel agent. If RuleChecker was triggered in on-demand (OND) mode, the travel agent can then select one or more RuleFiles or RuleSets and recheck the PNR (see also Associated RuleFiles/Sets Display on page 98).

Note: In point-of-sale (POS) mode, the list will be disabled.

- No Prompt to display just an error message, informing the travel agent that a RuleSet or RuleFile must be associated to the PNR.

What If an Associated Rule is Missing? You can define how RuleChecker reacts if a RuleFile or RuleSet associated to the current PNR is missing:


2. In the Prompt When RuleFile/Set Is Missing field, choose between:

- Stop RuleChecker: A system error is displayed and RuleChecker stops


78 Edition 4.0

- Skip but warn: A system error is displayed, but RuleChecker continues checking the PNR.

- Skip: Ignore missing RuleFiles/Sets.

Which Rules Apply If Another Office Is Responsible for the PNR? If you have associated different RuleFiles/Sets to the offices in your office group, you must specify which RuleFiles/Sets will be used by RuleChecker in case of remote sign-in:


2. In the Set RuleFiles/Sets When Another Office Is Responsible For The PNR, choose between:

- Responsible Office to apply the RuleFiles/Sets associated to the office that owns the PNR, i.e. the remote office.

- Current Office to apply the RuleFiles/Sets associated to the office that initiated the remote sign-in.

Note: The RuleFiles and RuleSets need to be available on the terminal when remotely signing in. This means that the RuleLibraries should have been published to both the current and the responsible office.

For more information on rule association, see Associating Rules to All PNRs Processed by an Office on page 83.



What If the PNR Has no Active Itinerary? You can define if RuleChecker processes PNRs that do not contain any itinerary segments:


2. In the Check PNR If It Has No Active Itinerary field, choose between:

- No to prevent RuleChecker from checking PNRs that do not have any active itinerary segments.

This allows the travel agent to file the PNR without passing the checks if, for example, the itinerary has been cancelled.

- Yes to let RuleChecker check all PNRs, even if they do not have an active itinerary.


80 Edition 4.0

How to Add RF Elements to Track Checked PNRs You can automatically add a Received From element whenever RuleChecker checks a PNR. This allows you to check in the PNR history if RuleChecker was executed, even if no error was found in the PNR.


2. Select the Received From check box.

3. Enter free-flow text for the Received From element in the field provided.

Note: An RF Quality Control element will always be added to a PNR, even if you do not select this option, if RuleChecker is bypassed or if RuleChecker is closed in POS mode without correcting the PNR.


Chapter 10

Associating Rules to PNRs

What Are the Different Methods of Associating Rules to PNRs?

RuleChecker needs to know which rules to apply to a given PNR.

Different methods are available for associating rules to PNRs, and you can use any combination of these methods in your office, depending on your requirements (an illustration is shown in Example: Combining Different Methods of Associating Rules to PNRs on page 88).

Rules can be associated to PNRs in the following ways:

• By adding RC elements (Confidential Remarks) directly in the PNR

• By transferring RC or RX elements from profiles

• By associating RuleFiles to all PNRs processed by one or more offices

• By associating RuleFiles to all PNRs processed by specific agents

• By manually selecting RuleFiles in RuleChecker

Adding RC Elements in the PNR

When to Add RC Elements Directly in the PNR

You can add formatted Confidential Remark (RC) elements containing the RuleFile name directly in the PNR.

You use this method if you want to quickly test a new rule.

How to Add Rules Using RC Elements in a PNR

1. Create or retrieve a PNR.

2. Add a Confidential Remark (RC) element, using the following format:



82 Edition 4.0

Transferring RC or RX Elements from Profiles

When to Add Rules Using RC or RX Elements in a Profile

You can also associate RuleFiles to PNRs by adding a remark element to a profile and then creating the PNR from the profile.

You would do this with rules that are specific to a traveller or a company.

You use Confidential Remark elements (RC) for traveller profiles and Corporate Remark elements (RX) for company profiles.

In the RC or RX element, you specify the RuleFile or RuleSet to be applied. When RuleChecker is triggered in the usual way (by an ET for example), the PNR is checked using the specified rules.

You can associate rules or RuleSets to any type of profile, such as a traveller, company, agency, or organization profile.

How to Add a Rule Using Confidential Remarks in a Profile

1. In the Profile module, create or open the required profile.

2. Associate the rules using RC confidential remarks containing the name of the RuleFile or RuleSet to be associated.

Use the following format for the RC remark:


3. Create a PNR for a traveller using the traveller's profile and transfer all data. The RC element with the associated rule will be included in the PNR.

The image below shows a RuleFile associated to a PNR in an RC element:

Chapter 10 Associating Rules to PNRs


Associating Rules to All PNRs Processed by an Office

When to Associate Rules at Office Level

You can select RuleFiles or RuleSets that RuleChecker will automatically apply to all PNRs processed by a specific office or group of offices.

You would use this method:

• If rules need to be run on every single PNR in the travel agencies, regardless of who is travelling.

• If your agency does not use profiles (that could contain RC elements for rule association) or if all PNRs need to be checked for certain rules.

Example: All PNRs processed by a certain agency should never have a TKOK but always a TKTL to ensure that all bookings are systematically placed on a queue. This is not related to the traveller, and there will be no RC element coming from a profile. The rule therefore needs to be associated to all PNRs processed by this office.

There are two parameters that you need to take into account:

• The configuration level to which you publish the RuleLibrary.

• The office IDs to which you associate a RuleFile or RuleSet.

Here are some example combinations:

If you publish a RuleLibrary to:

And you associate a RuleFile from this library to:

The RuleFile will be associated to:

an Office group all offices in the office group all offices in the office group

an Office group one or more offices in the office group

only the selected offices

a Certificate the office to which the certificate belongs

only the selected certificate

How to Associate Rules to all PNRs Processed by One or More Offices

1. Open Administrator at the highest configuration level. Select:

- My Office Group if the office ID is part of an office group, or

- My Office if there is no office group.

2. Click on the Rule Files/Sets tab.

3. To associate the rule, click in the RuleFiles/Sets field in the Association RuleFile/Set - Office ID section.


84 Edition 4.0

4. Select a RuleFile or RuleSet from the list. The list contains all the RuleFiles and RuleSets that have been set up in Rule Editor.

5. Enter the offices that will use the selected RuleFile/Set.

You can associate it to one office ID, or to several office IDs using wildcards (*)(see also How to Use Wildcards when Associating Rules to Offices on page 85).

6. Save the configuration.

7. Check that the selected RuleFile or RuleSet has already been stored in a RuleLibrary:

Click on to display the RuleLibraries to which the selected RuleFile or RuleSet belongs. Make sure that at least one RuleLibrary is shown.

- If the RuleFile or RuleSet does not belong to a RuleLibrary, open Rule Editor and add the RuleFile or RuleSet to a RuleLibrary. See How to Create a RuleLibrary and Add Rules on page 54.



8. Make sure that at least one of the shown RuleLibraries has been published to the correct configuration level.

Example: The RuleLibrary must have been published at office level if it is to be used on all terminals of an office.

Check the list of RuleLibraries at the top of the RuleFiles/Sets tab.

- If the RuleLibrary appears in the list, it has been published at office group level. No further action is required.

- If the RuleLibrary is not shown in the list, but you want it to be available at office group level, add it to the list. See How to Publish RuleLibraries from the Administrator on page 56.

- If the RuleLibrary was published at office or certificate level, you will not see it in the list, because you are currently working at office group level.

To check if the library has been published to the required level, open Administrator for that certificate or office and check again if the library appears in the RuleFiles/Sets tab.

How to Use Wildcards when Associating Rules to Offices

You can use wildcards (*) in the Office ID field in the RuleFiles/Sets tab in Administrator if you want to associate the same rule to more than one office within one office group.

Examples: If you select RuleFile CL Rule1 and enter the office ID NCE1A0***, the RuleFile will be associated to all Amadeus office IDs in Nice.

If you enter the office ID ***1A0***, the RuleFile will be associated to all Amadeus office IDs worldwide.

How to Exclude Offices If Using Wildcards

When you use wildcards to associate certain RuleFiles or RuleSets to several offices, you can exempt offices from this association:

In the Excluded Office ID field in the RuleFiles/Sets tab in Administrator, define one or more offices for which RuleChecker will not check the selected RuleFile or RuleSet.


86 Edition 4.0

Examples:

If you select RuleFile CL Rule1 and enter the office ID NCE1A0*** and the excluded office ID NCE1A0900, the RuleFile will be associated to all Amadeus office IDs in Nice, except for NCE1A0900.

If you enter the office ID ***1A0*** and the excluded office ID MAD1A0***, the RuleFile will be associated to all Amadeus office IDs worldwide, except for the Madrid offices MAD1A0***.

Associating Rules to Specific Agents

When to Associate Rules to All PNRs Processed by Specific Agents

You can publish rules to specific agents only, for example, if they need additional checks, because they are new and less experienced.

Example: Only some new agents of an agency should always have a TKTL, and never a TKOK in their PNRs, whereas the more experienced agents do not need this rule.

How to Associate Rules to All PNRs Processed by Specific Agents

1. Set up the RuleFiles or RuleSets as usual, but add them to a separate RuleLibrary.

2. You then publish this RuleLibrary at certificate level, not at office or office-group level. You need to do this for each certificate separately.

See Publishing a RuleLibrary on page 55 for more information.

3. Open Administrator at office group level, click on the RuleFiles/Sets tab and associate the RuleFile or RuleSet to the offices to which the certificates belong.

See Associating Rules to All PNRs Processed by an Office on page 83 for more information.

Although you have associated the rule to one or more entire offices, it will only be used by those agents to whom you published the RuleLibrary.



Manually Associating Rules in RuleChecker

When to Manually Associate Rules in RuleChecker

If RuleChecker was launched in on-demand (OND) mode, you can open the Associated RuleFiles/Sets window and manually select or deselect RuleFiles or RuleSets.

You can do this if you want to quickly test a rule.

How to Associate Rules to PNRs in RuleChecker

1. In RuleChecker, select View > Associated RuleFiles/Sets or click on .

The Associated RuleFiles/Sets Window opens, displaying all active RuleFiles and RuleSets that have been published to your terminal.

2. Select the RuleFiles or RuleSets you want to run.

Note: This is only possible in OND mode. If RuleChecker was triggered in POS mode, you cannot modify the selection.

3. Click on Save Associations and Recheck.


88 Edition 4.0

Example: Combining Different Methods of Associating Rules to PNRs

The following example shows how the different methods of associating rules to a PNR can be combined:

Rule YYYY is associated to the agency profile, rule XXXX is associated to the traveller profile, and rule ZZZZ is associated at office ID level.

When RuleChecker checks the PNR, it will apply all three rules, display the related messages and perform the defined actions.


Chapter 11

What Is Amadeus Quality Control RuleChecker?

Amadeus Quality Control RuleChecker is an easy-to-use and interactive graphical user interface (GUI) component used by the travel agent to check whether travel reservations comply with the business rules associated with an active PNR.

Here is an example of the RuleChecker window:

Prerequisites for Using RuleChecker

If you want to use RuleChecker you must ensure that:

• Your office has the required authorisation. This is managed by an indicator in your office profile.

• Your platform's certificate ID is deployed with the Amadeus Quality Control product option.

• A PNR is active.

• Rules have been set up and made available to you.

.


Chapter 12

Checking PNRs with RuleChecker

Launching RuleChecker Amadeus Quality Control RuleChecker can be launched manually in on-demand (OND) mode or automatically in point-of-sale (POS) mode.

When to Manually Launch RuleChecker (OND Mode)

You can manually launch RuleChecker to check the active PNR. This is called On Demand Mode (OND).

To manually launch RuleChecker, click on the button in the Selling Platform main menu bar. It can be launched from both the command page and the graphic pages.

When to Launch RuleChecker Automatically (POS Mode)

If triggering commands have been defined for your office, RuleChecker is triggered automatically when you perform certain actions in Selling Platform.

This is called Point-of-sale mode (POS) and is the most common way of using RuleChecker.

Example: For your office, ER and ET have been defined as triggering commands. If you end-transact a PNR, this will automatically launch RuleChecker.


92 Edition 4.0

Checking a PNR Once RuleChecker has been launched, either in point-of-sale mode or in on-demand mode, the PNR is checked against the associated rules.

When RuleChecker has completed its check, the PNR is refreshed and the RuleChecker window opens, displaying the rule messages.

Rule Messages Window in Graphic Mode

Rule Messages Window in Cryptic Mode

Chapter 12 Checking PNRs with RuleChecker


How to Interpret the Rule Messages Display

The Rule Messages window is displayed when RuleChecker has finished checking a PNR.

Rule Messages

The following indicators are used to show the results of a PNR rule check:

Icon Message Type Description

Error Mandatory rule has not been met.

Warning Non-mandatory rule has not been met.

Information Information relative to a rule not associated with the current triggering command family.

Internal Error Internal error or warning caused by the Amadeus system, the RuleFile/Set association, and/or the RuleFile/Set loading.

Success Rule passed successfully.

Associated Actions

These are the number of manual or automatic actions specified in the rule. Depending on the tasks, these may be displayed in the Send Transaction field when you select a rule message.

Send Transaction Field

If RuleChecker finds one or more manual actions to be completed, they are shown in this field. These are suggestions defined in the rule that help you solve the problem in your PNR.

• An Amadeus cryptic command (or part of it, to be completed by you)

• A Smart Key

• An application or a script (.EXE or .DLL programs)


94 Edition 4.0

Note: The list only contains actions to be launched manually. Any automatic actions defined in the rule will be launched automatically when the conditions are met.

See also How to Correct a PNR that Failed the Checks below for more information.

Mode of Operation

The status bar shows the mode in which RuleChecker is working.

• Point-of-Sale mode, when RuleChecker is run automatically. This is the most common mode of functioning.

• On Demand mode, when you manually launch RuleChecker by clicking on in the Selling Platform main menu bar.

Toolbar Icons

The toolbar provides access to the following actions:

Icon Action

Rechecks the PNR. See Rechecking a PNR on page 95 for details.

Displays the rule messages. See How to Interpret the Rule Messages Display on page 93 for details.

Displays the list of available RuleFiles, denoting those already associated to the active PNR. See Associated RuleFiles/Sets Display on page 98 for details.

Allows you to select a queue/category to queue the current PNR. If this button is disabled, no queue has been set by your administrator. See Placing PNRs on Queues on page 97 for details.

Displays the transaction log, showing the automatic transactions sent by RuleChecker and the manual transactions sent by you. See Transaction Log on page 99 for details.

How to Correct a PNR that Failed the Checks

If RuleChecker displays a warning message , we strongly recommend that you correct it before proceeding, even though it is not mandatory to correct warning messages.

If your PNR fails with an error message , you must correct it before you can proceed.

To correct your PNR, you can either go to the corresponding graphic page (for example the PNR tab if you need to correct the Form of Payment), go to the command page, or enter the appropriate cryptic command in the Send Transaction field directly in the RuleChecker window.

Depending on how the rules are defined, some actions may already be carried out automatically by RuleChecker.

Use these guidelines to correct your PNR:

1. Read the failure message and try to understand it. Most messages suggest a course of action.

2. Look in the Send Transaction field: there may be a suggested entry or entries. Click on to see all the suggestions.



Select a transaction from the list and, if necessary, complete it.

Note: To run an .EXE file, you must provide the full directory path. Example: C:\PROGRAM FILES\MYPROG\MYPROG.EXE To open a specific document or website, you need to provide: [full path of the application][space]["file name in inverted commas"]. Example: C:\Program Files\Internet Explorer\IEXPLORE.EXE "http://www.aa.com"

3. Click on Send.

Note: If you receive an error message, you may have entered a transaction that is configured as a triggering command, or your administrator may have defined that this transaction cannot be sent from RuleChecker.

4. Click on to recheck your PNR.

5. Close RuleChecker if it is still open and continue working as usual.

Example of a PNR Failure:

For a PNR with a car rental booking, you get the error message: DRIVER LICENCE NUMBER REQUIRED.

The Send Transaction field contains: RC DRIVER LICENCE XXXX. In this example, enter the customer's driver licence number and click on Send) to send the transaction. The required information will now appear in the PNR.

Rechecking a PNR

When to Manually Recheck a PNR

After you correct the errors or warnings displayed by RuleChecker, the PNR may need to be rechecked to ensure it is now compliant. You can do this either manually or automatically.

How to Manually Recheck a PNR

To manually launch RuleChecker to recheck a PNR, select Action > Recheck or click on .

When to Automatically Recheck PNRs

Automatic rechecking of PNRs is useful if some of your rules include built-in corrective action (automatic actions).

For example, a rule may include an automatic command to add missing information to the PNR.

If automatic rechecking is active, the PNR is rechecked automatically if at least one command was sent automatically as part of the checking process.

This process is repeated one time only to avoid loops in RuleChecker.


96 Edition 4.0

How to Enable Automatically Rechecking

To activate automatic rechecking of PNRs, select Action > Auto Recheck from the RuleChecker window.

Notes: The initial checking process can be triggered in either POS or OND mode. In POS mode only, if you have Warning or Information messages during the first check, they will not appear in the RuleChecker window because the window displays only the latest messages (after the recheck).

Bypassing RuleChecker

When to Bypass PNRs

When RuleChecker displays error messages because mandatory rules are not met, you may want to bypass RuleChecker and continue working without implementing the suggested corrections.

You may need to do this if:

• There are errors in the rule definition

• You do not want to comply with the rule definition

Bypassing PNRs is only allowed if it has been enabled by the administrator.

How to Bypass RuleChecker

1. In the RuleChecker window, select Action > Bypass All.

Note: The Bypass function is only available if:

- It has been enabled by the QC administrator.

- AND if RuleChecker was launched in point of sale mode.

In on demand mode, you cannot bypass RuleChecker.

2. If your administrator has set a bypass password, enter the password in the pop-up window that appears.

The non-compliant rules are ignored and the transaction that triggered RuleChecker is sent to the distribution system.



Placing PNRs on Queues

When to Place PNRs on Queue

If a PNR fails mandatory rules and if further processing is necessary, you can send the active PNR directly from RuleChecker to a queue.

This requires that queues have been selected for use from RuleChecker in the Administrator module (see Selecting Queues from RuleChecker on page 75).

How to Place a PNR on a Queue from RuleChecker

1. In the RuleChecker window, select Action > Queue PNR... or click on . The Queue PNR window is displayed with a default queue automatically selected.

This list only shows the queues that have been selected for use with RuleChecker by the QC administrator.

2. To use another queue, select a queue from the Queue Name drop-down list.

3. Click on Send to place the PNR on the selected queue.


98 Edition 4.0

Associated RuleFiles/Sets Display

How to Check Which Rules Are Associated to a PNR

You can display the list of available RuleFiles and RuleSets and check which RuleFiles/Sets are associated to your PNR:

In RuleChecker, select View > Associated RuleFiles/Sets or click on .

The Associated RuleFiles/Sets window opens, displaying the available RuleFiles and RuleSets. These include all active RuleFiles and RuleSets that have been published to your terminal.

A check mark indicates that the RuleFile or RuleSet is associated to the current PNR.

The office icon is displayed if a RuleFile or RuleSet is automatically associated to all PNRs processed by your office.

RuleFiles or RuleSets displayed with a check mark but without the office icon are associated by means of an RC RULE or RX RULE element.

How to Manually Associate Rules in RuleChecker

If RuleChecker was launched in on-demand (OND) mode, you can display the Associated RuleFiles/Sets window and manually associate RuleFiles or RuleSets to the PNR.

This window will also be displayed if RuleChecker is configured to prompt you with a list in case RuleChecker is launched (in OND or POS mode) but no RuleFile/Set is associated to the current PNR.

1. In RuleChecker, select View > Associated RuleFiles/Sets or click on . The Associated RuleFiles/RuleSets window is displayed.

2. Select the RuleFiles or RuleSets you want to associate to the current PNR.



3. Click on Save Associations and Recheck to recheck the PNR.

Transaction Log

What Is the Transaction Log?

The transaction log displays the list of cryptic commands that were sent internally by RuleChecker when running the attached rules, or that were sent manually by the agent through the Send field in the Rule Messages screen in RuleChecker.

How to Display the Transaction Log

To access the transaction log, select View > Transaction Log in the RuleChecker window.


100 Edition 4.0

Troubleshooting Log

What Is the Troubleshooting Log?

The troubleshooting log provides a trace of Quality Control processing of the attached rules.

When to Display the Troubleshooting Log

If you encounter problems or errors when running RuleChecker and you contact your help desk, you will be asked to send this log.

How to Display the Troubleshooting Log

1. Select Help > QC Troubleshooting Log from the RuleChecker window.

A QC Log file is displayed.

2. Save this file and send it to the relevant person in your help desk.

Customising RuleChecker Display Options The View menu in the RuleChecker window provides various possibilities to configure what you see in the Rule Messages display.



Here is an overview of the settings and their meaning:

You want to Setting Explanation

Display all rule messages, including:

• Errors

• Warnings • Successfully

passed rules

From the View menu, select:

Display All Rule Messages

All successfully passed rules are displayed, in addition to the warnings and errors, which are always shown. If you do not select this option, RuleChecker will only display the warnings and errors.

Display a confirmation message when all rules are met


Display Success Acknowledgement

If you select this option, a confirmation message is displayed when all the associated rules are met and the PNR passes the quality checks If you do not select this option, RuleChecker closes without displaying any confirmation message. If there are any errors or warnings, RuleChecker always displays these regardless of this setting.

Display a 'RuleChecker is processing' message while RuleChecker is checking a PNR:


Display Splash Screen

If you select this option, a message is displayed while RuleChecker checks a PNR.

Once RuleChecker has completed the checks, this message is then replaced by the RuleChecker window, showing the rule messages. If you do not select this option, there is no visual indicator when RuleChecker is checking the PNR. However, you cannot perform any actions in Selling Platform until this process is completed.

Hide RuleChecker unless errors or warnings occur

From the View menu, clear:

Display All Rule Messages

Display Success Acknowledgement

Display Splash Screen

RuleChecker will run invisibly in the background. It will only open in the case of an error or a warning.

Display Informative Messages

The 'Show Informative Messages' option must have been activated for your CID. This is done by the QC administrator.

Information messages will be displayed for the rules associated to the PNR but not associated to the current triggering command that launched RuleChecker.


102 Edition 4.0

Example: Creating a Rule and Testing It in Selling Platform

Here you will find an example of the full workflow that is required to create a rule and test it on a PNR in Selling Platform.

1. Create a rule

2. Publish the rule in a library

3. Force rule replication to your PC

4. Create a PNR from a profile in order to associate a rule included as an RC element in the profile

5. Book an itinerary and check the PNR

In this example, QC is enforcing the form of payment CASH for all flights on BA. If RuleChecker does not find the element FPCASH, it automatically enters the format for the agent.

Step 1: Create a Rule

1. To open the Amadeus Quality Control Manager, click on in your platform's menu bar.

If a password was set up for your office ID, enter it now and click on OK.

The Amadeus Quality Control Manager screen is displayed.

2. Click on Rule Editor to open the Rule Editor component.

3. To start creating a new rule, click on the New RuleFile button or click on .

4. Enter a name for the RuleFile you are creating. Example: BA FOP CASH

5. Enter a brief description. Example: Flights on BA require FOP cash.

6. Click on Rules Details to start creating your RuleFile.

7. Click on Here. The Add Rule window opens.



8. Create your RuleFile based on your requirements, then click on OK.

In this example, QC is enforcing the form of payment CASH for all flights on BA.

If RuleChecker does not find the element FPCASH, it automatically enters the format for the agent.

For more information on building a rule, see also Creating a Simple Rule on page 17.

9. To save the RuleFile, click on .

10. Click on the blue All RuleFiles link at the top.

The list of RuleFiles now shows the new rule.


104 Edition 4.0

Step 2: Publish the RuleFile

To publish the RuleFile, you first need to associate it to a RuleLibrary.

1. In Rule Editor, click on the All RuleLibraries tab.

2. Highlight the appropriate RuleLibrary and click on Open.

(This example assumes that the RuleLibrary exists already.)

3. Click on the RuleFiles/Sets Association tab to associate the rule to the Library.

4. Scroll down, select the RuleFile you want to associate to the RuleLibrary and then click on Add>.

The RuleFile is now displayed under the list of Associated RuleFiles/Sets.

5. To save it, click on .

6. Click on the blue All Rule Libraries link at the top of the screen.



7. You can now publish the RuleLibrary:

Make sure you have the correct RuleLibrary highlighted and click on Publish.

8. In the window that appears, select the configuration to which you want to publish the RuleLibrary, in this case My Certificate.

9. Click on OK to publish the RuleLibrary. The rules in this library can now be used at the selected configuration level.

Step 3: Replicate the New Rule to Your PC

Rules are automatically updated on a terminal when RuleChecker is launched for the first time on a new day. To be able to test your new rule immediately, you need to force the rule replication:

1. Go back to Selling Platform and click on in the main menu bar.

As RuleChecker cannot find the rule that is called by the RC element (because the rule has just been created and is not yet replicated on your PC), the Associated RuleFile/Sets window is displayed.

It does not yet show the rule BA FOP CASH.

2. To download the new rule, select Action > Force QC Replication.


106 Edition 4.0

The new rule is now displayed in the list of Associated RuleFiles/Sets.

Step 4: Create a PNR from a Profile

Add the rule as an RC element to a profile and create a PNR from this profile.

1. In Amadeus Selling Platform, go to the Profile module and click on the Open tab.

2. Enter the name of the profile to be used and click on Send.

3. Select the profile from the list and click on Send.

The profile is displayed.

4. Add the following confidential remark and save the profile:

RC Rule BA FOP CASH

5. Click on the Transfer To PNR icon .

6. Select the options Transfer automatic data and Include Data From Company Profile and click on Send to transfer the data to the PNR.

Step 5: Check the PNR with RuleChecker

1. Book an itinerary using the airline BA.

2. Enter any missing mandatory elements and save and redisplay the PNR (ER).



RFLA 1.TRAINEE TWO/B(ADT) 2 BA1393 B 20FEB 3 MANLHR HK1 3 1310 1415 319 E 0 S SEE RTSVC 3 BA 299 B 20FEB 3 LHRORD HK1 4 1530 1810 777 E 0 M SEE RTSVC 4 AP 132123-M 5 TK OK06FEB/NCE1A0932 6 RC NCE1A0932-W/RULE-LA LF IN V CLASS 7 RC NCE1A0932-W/RULE-LA IB ON B CLASS 8 RC NCE1A0932-W/RULE-BA FOP CASH 9 AM/H A1-AVENUE CHAMPS ELYSEES/CI-PARIS/CO-FR

RuleChecker now checks the PNR.

As it does not find the element FPCASH, the Rule Messages window displays a warning message that the form of payment must be CASH. (The window will only be shown if the display options are set accordingly. See also Customising RuleChecker Display Options on page 100.)

The transaction FPCASH appears automatically in the Send field.

3. Click on Send to add FPCASH to the PNR.

4. Click on to recheck the PNR.

It now passes the checks.


Chapter 13

Importing and Exporting RuleFiles

Importing RuleFiles

When to Import RuleFiles

RuleFiles are set up for a certain office or office group. If they are to be reused by another office or office group, Quality Control allows you to export and import them in .xml format.

RuleFiles can be imported directly into Amadeus Quality Control and stored in the central rules repository for the office group or office. This may be required for example, if you need to update RuleLibraries with RuleFiles created by another office group.

You can either import one RuleFile at a time or a complete folder.

How to Import an Individual RuleFile

1. In Rule Editor, select File > Import RuleFile. An Import window is displayed.

2. Enter the full path and the name of the RuleFile to be imported.

Example: C:\Program Files\Amadeus\Shared\MY_RULEFILE.xml

Alternatively, click on the Browse icon and select a RuleFile from a browser window.

3. Click on Import.

The RuleFile is checked, imported and added to the list of available RuleFiles/Sets.


110 Edition 4.0

How to Import All RuleFiles from a Folder

If you have several RuleFiles to import, you can copy them all into the same folder and then import them in one step. Note, however, that RuleSet and RuleLibrary associations are lost during the import:

1. In Rule Editor, select File > Import RuleFiles by Folder. An Import window is displayed.

2. Enter the full path for the folder that contains the RuleFiles to be imported.

Example: C:\Program Files\Amadeus\Shared

Alternatively, click on the Browse icon and select the folder from a browser window.

3. Click on Import.

The RuleFiles in the selected folder are checked, imported and added to the list of available RuleFiles/Sets.

Note: Any RuleSet or RuleLibrary associations are not transferred during the import. Once you have imported the RuleFiles, you need to group them into RuleSets again (see Grouping RuleFiles into RuleSets on page 49).

Exporting RuleFiles

When to Export RuleFiles

Exporting RuleFiles is required before they can be imported by another office group or office. During the export, the RuleFiles will be downloaded as .xml files from the central rules depository to your local terminal.

You can export individual RuleFiles, all RuleFiles in a RuleSet or all RuleFiles in a RuleLibrary.

How to Export an Individual RuleFile

1. In Rule Editor, select the RuleFile to be exported, then click on Open.

2. From the menu, select File > Export. An Export window is displayed.

3. Enter the full path and the name of the file that will be created. Example: C:\RuleFiles\MyRuleFile.xml.

Chapter 13 Importing and Exporting RuleFiles


Alternatively, click on the Browse icon to select or create a folder from a browser window. Enter the file name, select the file type and click on Save to return to the Export window.

Note: If the file name already exists, the file will be overwritten without any warning.

4. Click on Export.

An .xml file is created in the selected folder.

How to Export a RuleSet

1. In Rule Editor, select the RuleSet to be exported, then click on Open.


3. Enter the full path for the export folder. Example: C:\My_Export

Alternatively, click on the Browse icon to select or create a folder from a browser window.

4. If required, you can change the name of the folder that will be created for the RuleSet. The default naming convention is "RS_[RuleSet name]".

5. Click on Export.

An .xml file is created for each RuleFile in the RuleSet and stored in the selected folder.


112 Edition 4.0

Note: If RuleFiles with the same name already exist in the folder, they are overwritten without any warning.

How to Export a RuleLibrary

1. In Rule Editor, click on the All RuleLibraries tab, select the RuleLibrary to be exported and click on Open.


3. Enter the full path for the export folder. Example: C:\My_Export

Alternatively, click on the Browse icon to select or create a folder from a browser window.

4. If required, you can change the name of the folder that will be created for the RuleLibrary. The default naming convention is "RL_[RuleLibrary name]".

5. Click on Export.

For each RuleSet in the RuleLibrary, a subfolder is created that contains the .xml files for the RuleFiles. The naming convention for the RuleSet folders is "RS_[RuleSet name]". Any existing folders or RuleFiles are not removed.

Note: If RuleFiles with the same name already exist in a folder, they are overwritten without any warning.


Chapter 14

Displaying PNR/TST Details

When to Display PNR or TST Details

The View PNR/TST Details option allows you to display detailed information on the elements in the PNR currently open.

This can be helpful when you are building a rule in Rule Editor, for example, and you need to know the names of the elements and the properties you can check in your rule. Also, when you are testing if a rule works as intended, you may want to check which data can be found in the current PNR.

How to Display PNR Details

1. Make sure that a PNR is open in your current work area in Amadeus Selling Platform and that it contains the elements you are interested in.

2. In Rule Editor, choose Tools > View PNR/TST details from the menu. The View PNR/TST Details window is displayed.

How to Interpret the View PNR/TST Details Window

The View PNR/TST Details window contains the following information:

• A separate section for each category of elements found in the current PNR or TST

Example: [Section1] : Name Elements [Section2] : Air Segment Elements

• A subsection for each element in a category.

Example: For [Section1] : Name Elements, sub-sections are displayed for each passenger in the PNR. For [Section 2] : Air Segments, sub-sections are displayed for each flight segment in the PNR.

• For each element, all properties that can be checked in a rule are listed with their name and with the value found in the current PNR/TST. The value may be empty if it is not filled.

You can expand or collapse the sections as required.

If the window is already open and you load another PNR in your Selling Platform, choose Tools > View PNR/TST Details again to refresh the window with the new data.


114 Edition 4.0

For a full list of PNR and TST elements and their properties, see also Data Dictionary on page 117.

Example: PNR Details

Consider the following PNR:

--- TC-BIZ RLP --- RP/NCE1A0950/ 1.SMITH/VALERIE MRS 2 6X 341 C 15DEC 6 NCELHR DK1 0745 0900 15DEC E 0 320 SEE RTSVC 3 AF2471 C 25DEC 2 LHRCDG DK1 0640 0900 25DEC E 0 321 B SEE RTSVC 4 AP (T) TEL+49 711 123123

The View PNR/TST Details window for this PNR displays the following information:

[Section1] : Name Elements

[Sub-Section1.1] : Name – 1.SMITH/VALERIE MRS Text: 1.SMITH/VALERIE MRS Element Number: 1 Last Name: SMITH Initial: VALERIE MRS ID code: Infant: Infant Initial: Infant Last Name: Passenger Type: Extra Seat: 0 Cabin Baggage:

[Section2] : Air Segment Elements

[Sub-Section2.1] : Air Segment – 6X 341 C 15DEC 6 NCELHR DK1 0745 0900 15DEC E 0 320 SEE RTSVC

Text: 6X 341 C 15DEC 6 NCELHR DK1 0745 0900 15DEC E 0 320 SEE RTSVC Element Number: 2 Airline: 6X Joint Airline: Arrival Time: 0900 Board Point: NCE Checkin Time: 0000 Class: C Departure Date: 1215 Departure Time: 0745 Equipment:320 Flight Number: 341 Meal Svc: Off Point: LHR Status Code: DK Kind: 230 Entertainment: 0 Day Change: 0

Chapter 14 Displaying PNR/TST Details


Day Of Week: 6 Number Of Passengers: 1 Number Of Stops: 0 Airline Reference: Access Sell Tag: 0 Allotment Tag:0 Direct Access: Electronic Ticketing Tag: E Married Segment Identifier: Airport Board Zone: Passenger Association: 0 Segment Association: 0 Arrival Date: 1215 Join Car: 0 Join Hotel: 0 Board Point Country State: FR Off Point Country State: GB

[Sub-Section2.2] : Air Segment – AF2471 C 25DEC 2 LHRCDG DK1 0640 0900 25DEC E 0 321 B SEE RTSVC

Text: AF2471 C 25DEC 2 LHRCDG DK1 0640 0900 25DEC E 0 321 B SEE RTSVC Element Number: 3 Airline: AF Joint Airline: Arrival Time: 0900 Board Point: LHR Checkin Time: 0000 Class: C Departure Date: 1225 Departure Time: 0640 Equipment:321 Flight Number: 2471 Meal Svc:Off Point: CDG Status Code: DK Kind: 230 Entertainment: 0 Day Change: 0 Day Of Week: 2 Number Of Passengers: 1 Number Of Stops: 0 Airline Reference: Access Sell Tag: 0 Allotment Tag:0 Direct Access: Electronic Ticketing Tag: E Married Segment Identifier: Airport Board Zone: Passenger Association: 0 Segment Association: 0 Arrival Date: 1225 Join Car: 1


116 Edition 4.0

Join Hotel: 1 Board Point Country State: GB Off Point Country State: FR

[Section3] : Phone Elements

[Sub-Section3.1] : Phone - 4 AP (T) TEL+49 711 123123 Text: (T) TEL+49 711 123123 Element Number: 4 Element Identifier: AP Free Flow: (T) TEL+49 711 123123 Passenger Association: 0 Segment Association: 0 Contact Type: Contact Free Flow:(T) TEL+49 711 123123

[Section4] : PNR Text Elements

[Sub-Section4.1] : PNR Text - RP/NCE1A0950/ 1.SMITH/VALERIE MRS 2 6X 341 C 15DEC 6 NCELHR DK1 0745 0900 15DEC E 0 320 SEE RTSVC 3 AF2471 C 25DEC 2 LHRCDG DK1 0640 0900 25DEC E 0 321 B SEE RTSVC 4 AP (T) TEL+49 711 123123


Appendix A

Data Dictionary

This appendix contains a comprehensive list of all PNR and TST elements that you can select when you build a rule (If condition):

For each element, all the properties that can be checked in a rule are listed and explained. These are the properties that you select in a Where statement or a variable.

For easy reference, the PNR/TST elements are shown in alphabetical order.

Index of PNR/TST Elements

AB - Billing Address on page 134 AI - Accounting on page 134 Air Itinerary Segment on page 135 AIR - Air Segment on page 137 AM - Mailing Address on page 138 Any Itinerary Segment on page 139 Any PNR Element on page 140 AP - Phone on page 140 ARNK - Arrival Unknown Segment on page 140 ATX - Auxiliary Air Taxi Segment on page 141 CAR - Auxiliary Car Segment on page 141 CCR - Car Segment on page 142 CRU - Cruise Segment on page 144 FA - Auto Ticket Number on page 144 FD - Fare Discount on page 145 FE - Endorsement on page 145 SSR FQTV - Special Service Request Frequent Traveller on page 162 FH - Manual Ticket Number on page 145


118 Edition 4.0

FI - Auto Invoice Number on page 146 FLWN - Air Flown Segment on page 146 FM - Commission on page 146 FO - Original Issue on page 147 FP - Form Of Payment on page 148 FS - Miscellaneous Ticket Information on page 149 FT - Tour Code on page 149 FV - Validating Carrier on page 149 FY - Fare Override on page 150 HHL - Hotel Segment on page 150 HTL - Auxiliary Hotel Segment on page 153 INS - Travel Assistance on page 153 MIS - Miscellaneous Segment on page 154 NG - Group Name on page 154 NM - Name on page 155 OP - Option Queue on page 155 OPEN - Open Air Segment on page 156 OSI - Other Service Information on page 156 PNR Header on page 156 PNR Text on page 157 RC - Confidential Remark on page 157 RI - Unassociated Remark on page 157 RIA - Adjustment Remark Invoice on page 158 RIB - Agency Billing Data on page 158 RIC - Print Agency Due Date on page 158 RID - Agency Due Date on page 158 RIF - Freeflow Invoice Remark on page 159 RII - Invoice Itinerary Remark on page 159 RIM - Profile Itinerary Remark on page 159 RIO - Itinerary Invoice Remark on page 159 RIP - Invoice Remark on page 160 RIR - Itinerary Remark on page 160 RIS - Service Fee Air on page 160 RIT - Override Invoice Total on page 161 RIU - Auxiliary Product Form of Payment on page 161 RIZ - Miscellaneous Ticketing Remark on page 161 RM - General Remark on page 161 RX - Corporate Remark on page 162 SSR - Special Service Request on page 162 ST - Special Service Request Seat on page 163 TK - Ticket on page 163 TRN - Train Segment on page 164 TST - Transitional Stored Ticket on page 164 TST AIR - TST Air Itinerary Segment on page 165 TTO - Amadeus Tour Segment on page 165

Appendix A Data Dictionary


Index of Properties by PNR/TST Element If you know the property name, but you do not know from which PNR or TST element you can extract this property, use the following table as a reference:

Property... ...can be extracted from element:

Access Sell Tag AIR - Air Segment

Account Number AI - Accounting

Action TK - Ticket

Address Data AB - Billing Address AM - Mailing Address

AF Flag TK - Ticket

Agency Accounting Data HHL - Hotel Segment CCR - Car Segment

Airline Code AIR - Air Segment FLWN - Air Flown Segment HTL - Auxiliary Hotel Segment OPEN - Open Air Segment TST AIR - TST Air Itinerary Segment ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment OSI - Other Service Information SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat

Airline Of Frequent Flyer Card SSR FQTV - Special Service Request Frequent Traveller

Airline Reference AIR - Air Segment

Airport Board Zone AIR - Air Segment

Airport Pair ST - Special Service Request Seat

Alliance Airline Code PNR Header

Allotment Tag AIR - Air Segment

American Plan HHL - Hotel Segment

American Plan Amount HHL - Hotel Segment

American Plan Currency Code HHL - Hotel Segment

American Plan Number HHL - Hotel Segment

Amount FA - Auto Ticket Number FO - Original Issue RIA - Adjustment Remark Invoice RIS - Service Fee Air RIT - Override Invoice Total

Amount Indicator FM - Commission

Amount Override HHL - Hotel Segment

Amount Override Amount HHL - Hotel Segment

Amount Override Currency Code HHL - Hotel Segment

AQ Text FP - Form Of Payment


120 Edition 4.0


Arrival Date Air Itinerary segments AIR - Air Segment

Arrival Information CCR - Car Segment

Arrival Port CRU - Cruise Segment

Arrival Time AIR - Air Segment Any Itinerary Segment TRN - Train Segment

Base Fare FO - Original Issue

Base Fare Override FY - Fare Override

Beneficiary Names INS - Travel Assistance

Billing Number CCR - Car Segment

Billing Reference CCR - Car Segment

Board Point AIR - Air Segment Any Itinerary Segment ATX - Auxiliary Air Taxi Segment FLWN - Air Flown Segment OPEN - Open Air Segment TRN - Train Segment

Board Point Country State AIR - Air Segment OPEN - Open Air Segment

Booking Agent Identifier CCR - Car Segment

Booking Source CAR - Auxiliary Car Segment CCR - Car Segment HHL - Hotel Segment HTL - Auxiliary Hotel Segment

Cabin Baggage NM - Name

Capping Amount FM - Commission

Car Base Rate Amount CCR - Car Segment

Car Base Rate Car Company CCR - Car Segment

Car Base Rate Currency CCR - Car Segment

Car Base Rate Free Flow CCR - Car Segment

Car Company CCR - Car Segment

Car Corporate ID Data CCR - Car Segment

Car Estimated Total Amount CCR - Car Segment

Car Estimated Total Currency CCR - Car Segment

Car Estimated Total Data CCR - Car Segment

Car Free Flow CCR - Car Segment

Car Rate Data CCR - Car Segment

Car Type Any Itinerary Segment CAR - Auxiliary Car Segment CCR - Car Segment

Carrier FV - Validating Carrier

Category RM - General Remark




Chain Code HHL - Hotel Segment

Check Digit FH - Manual Ticket Number

Check in Date Any Itinerary Segment Any Itinerary Segment HHL - Hotel Segment

Check in Time AIR - Air Segment

Check out Date Any Itinerary Segment Any Itinerary Segment HHL - Hotel Segment

Check-in City HTL - Auxiliary Hotel Segment

Check-in Date HTL - Auxiliary Hotel Segment

Check-out Date HTL - Auxiliary Hotel Segment

Circle Itinerary Air Itinerary segments

City HHL - Hotel Segment MIS - Miscellaneous Segment

Class of Service AIR - Air Segment FLWN - Air Flown Segment OPEN - Open Air Segment Any Itinerary Segment TRN - Train Segment

Collection CCR - Car Segment

Commission amount or percentage FM - Commission

Commission Indicator FM - Commission

Commission Percentage FM - Commission INS - Travel Assistance

Company CCR - Car Segment

Confirmation Number Any Itinerary Segment CAR - Auxiliary Car Segment CCR - Car Segment HHL - Hotel Segment HTL - Auxiliary Hotel Segment INS - Travel Assistance

Conjuncted Ticket Number FA - Auto Ticket Number FH - Manual Ticket Number

Contact Text AP - Phone

Contact Type AP - Phone

Corporate Identifier HHL - Hotel Segment

Corporate Rate CCR - Car Segment

Cost Center AI - Accounting

Country INS - Travel Assistance

Coverage Amount INS - Travel Assistance

Coverage Currency INS - Travel Assistance

Creation Date PNR Header

Crib HHL - Hotel Segment


122 Edition 4.0


Crib Amount HHL - Hotel Segment

Crib Currency Code HHL - Hotel Segment

Crib Number HHL - Hotel Segment

Cruise Booking Status CRU - Cruise Segment

Cruise Line Code CRU - Cruise Segment

Currency Code FA - Auto Ticket Number HHL - Hotel Segment RIA - Adjustment Remark Invoice RIS - Service Fee Air RIT - Override Invoice Total

Customer Identifier CCR - Car Segment HHL - Hotel Segment

Daily Indicator HHL - Hotel Segment

Data FD - Fare Discount

Date FA - Auto Ticket Number MIS - Miscellaneous Segment OP - Option Queue TK - Ticket

Date Of Birth INS - Travel Assistance

Day Change AIR - Air Segment Any Itinerary Segment TRN - Train Segment

Day Of Week AIR - Air Segment FLWN - Air Flown Segment OPEN - Open Air Segment

Days Advance Book Air Itinerary segments

Days Advance Purchase Air Itinerary segments

Days Stay Duration Air Itinerary segments

Days Stay Of Week Air Itinerary segments

Delivery CCR - Car Segment

Departure Date Air Itinerary segments AIR - Air Segment Any Itinerary Segment ARNK - Arrival Unknown Segment ATX - Auxiliary Air Taxi Segment CRU - Cruise Segment FLWN - Air Flown Segment OPEN - Open Air Segment TRN - Train Segment

Departure Port CRU - Cruise Segment

Departure Time AIR - Air Segment Any Itinerary Segment TRN - Train Segment

Deposit HHL - Hotel Segment

Destination Airport Air Itinerary segments

Destination Country State Air Itinerary segments

Destination Zone INS - Travel Assistance




Direct Access AIR - Air Segment

Discount Code FD - Fare Discount

Document Print Option TK - Ticket

Domestic Air Itinerary segments

Drop off Date Any Itinerary Segment CCR - Car Segment

Drop Off Information CCR - Car Segment

Duplicate Segments Air Itinerary segments

Electronic Ticketing Carrier FA - Auto Ticket Number

Electronic Ticketing Tag AIR - Air Segment

Electronic Tkt Res Confirmation Number

FA - Auto Ticket Number

Element Identifier Any PNR Element AB - Billing Address AI - Accounting AM - Mailing Address AP - Phone ATX - Auxiliary Air Taxi Segment CRU - Cruise Segment FH - Manual Ticket Number FI - Auto Invoice Number FM - Commission FO - Original Issue FP - Form Of Payment FS - Miscellaneous Ticket Information FT - Tour Code FV - Validating Carrier FY - Fare Override INS - Travel Assistance MIS - Miscellaneous Segment OP - Option Queue OSI - Other Service Information RC - Confidential Remark RI - Unassociated Remark RIA - Adjustment Remark Invoice RIB - Agency Billing Data RIC - Print Agency Due Date RID - Agency Due Date RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIM - Profile Itinerary Remark RIO - Itinerary Invoice Remark RIP - Invoice Remark RIR - Itinerary Remark RIS - Service Fee Air RIT - Override Invoice Total RIU - Auxiliary Product Form of Payment RIZ - Miscellaneous Ticketing Remark RM - General Remark RX - Corporate Remark SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TK - Ticket

Element Number AB - Billing Address


124 Edition 4.0

Property... ...can be extracted from element: AI - Accounting Air Itinerary segments AIR - Air Segment AM - Mailing Address Any Itinerary Segment Any PNR Element AP - Phone ARNK - Arrival Unknown Segment ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment CCR - Car Segment CRU - Cruise Segment FA - Auto Ticket Number FD - Fare Discount FE - Endorsement FH - Manual Ticket Number FI - Auto Invoice Number FLWN - Air Flown Segment FM - Commission FO - Original Issue FP - Form Of Payment FS - Miscellaneous Ticket Information FT - Tour Code FV - Validating Carrier FY - Fare Override HHL - Hotel Segment HTL - Auxiliary Hotel Segment INS - Travel Assistance MIS - Miscellaneous Segment NG - Group Name NM - Name OP - Option Queue OPEN - Open Air Segment OSI - Other Service Information RC - Confidential Remark RI - Unassociated Remark RIA - Adjustment Remark Invoice RIB - Agency Billing Data RIC - Print Agency Due Date RID - Agency Due Date RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIM - Profile Itinerary Remark RIO - Itinerary Invoice Remark RIP - Invoice Remark RIR - Itinerary Remark RIS - Service Fee Air RIT - Override Invoice Total RIU - Auxiliary Product Form of Payment RIZ - Miscellaneous Ticketing Remark RM - General Remark RX - Corporate Remark SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TK - Ticket TRN - Train Segment TTO - Amadeus Tour Segment

Entertainment AIR - Air Segment

Equipment AIR - Air Segment Any Itinerary Segment




Equivalent Fare Override FY - Fare Override

ET Airline Code TK - Ticket

Extra Discount Code FD - Fare Discount

Extra Discount Data FD - Fare Discount

Extra Person HHL - Hotel Segment

Extra Person Amount HHL - Hotel Segment

Extra Person Currency Code HHL - Hotel Segment

Extra Person Number HHL - Hotel Segment

Extra Seat NM - Name

Family American HHL - Hotel Segment

Family American Amount HHL - Hotel Segment

Family American Currency Code HHL - Hotel Segment

Family American Number HHL - Hotel Segment

Family Modified HHL - Hotel Segment

Family Modified Amount HHL - Hotel Segment

Family Modified Currency Code HHL - Hotel Segment

Family Modified Number HHL - Hotel Segment

Fare Base Line Base TST - Transitional Stored Ticket

Fare Base Line Currency Code TST - Transitional Stored Ticket

Fare Basis AIR - Air Segment

Fare Calculation Mode Indicator TST - Transitional Stored Ticket

Fare Code AIR - Air Segment

Fare Discount INS - Travel Assistance

Fare Issue Indicator TST - Transitional Stored Ticket

FH Type FH - Manual Ticket Number

Flight No FLWN - Air Flown Segment

Flight Number AIR - Air Segment

Flown Indicator FLWN - Air Flown Segment

Form Of Payment AIR - Air Segment RIU - Auxiliary Product Form of Payment

Form Of Payment Text FP - Form Of Payment


126 Edition 4.0


Free Flow Text/Message AP - Phone ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment FA - Auto Ticket Number FE - Endorsement FH - Manual Ticket Number FO - Original Issue FS - Miscellaneous Ticket Information FT - Tour Code HTL - Auxiliary Hotel Segment MIS - Miscellaneous Segment OP - Option Queue OPEN - Open Air Segment OSI - Other Service Information RC - Confidential Remark RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIR - Itinerary Remark RIS - Service Fee Air RIZ - Miscellaneous Ticketing Remark RM - General Remark SSR - Special Service Request TK - Ticket TTO - Amadeus Tour Segment

Frequent Traveler Code SSR FQTV - Special Service Request Frequent Traveller

Frequent Traveler Number CCR - Car Segment SSR FQTV - Special Service Request Frequent Traveller

Frequent Traveler Priority SSR FQTV - Special Service Request Frequent Traveller

Group Name NG - Group Name

Guarantee HHL - Hotel Segment

Hold Information HHL - Hotel Segment

Hotel Message HHL - Hotel Segment

IATA Company Number AI - Accounting

IATA Number FA - Auto Ticket Number

ID Code NM - Name

Infant NM - Name

Infant Initial NM - Name

Infant Last Name NM - Name

Initial NM - Name

International Air Itinerary segments

Invoice number FI - Auto Invoice Number

Issue By Date Air Itinerary segments

Issued In Exchange Coupon Indicator FO - Original Issue

Issued In Exchange Numeric Airline Code

FO - Original Issue

Issued In Exchange Ticket Number FO - Original Issue




Join Car AIR - Air Segment

Join Hotel AIR - Air Segment

Joint Airline AIR - Air Segment FLWN - Air Flown Segment OPEN - Open Air Segment

Last Date To Ticket TST - Transitional Stored Ticket

Last Name NM - Name

Line Number RIC - Print Agency Due Date RIM - Profile Itinerary Remark RIO - Itinerary Invoice Remark RIP - Invoice Remark

Location Any Itinerary Segment CCR - Car Segment TK - Ticket

Location Code CCR - Car Segment

Married Segment Id AIR - Air Segment

Meal Service Codes AIR - Air Segment

Modified American HHL - Hotel Segment

Modified American Amount HHL - Hotel Segment

Modified American Currency Code HHL - Hotel Segment

Modified American Number HHL - Hotel Segment

Name Of Person Insured INS - Travel Assistance

Nanny Name INS - Travel Assistance

Number in party Any Itinerary Segment INS - Travel Assistance MIS - Miscellaneous Segment SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TRN - Train Segment

Number of Assigned Names NG - Group Name

Number Of Cars CAR - Auxiliary Car Segment CCR - Car Segment

Number Of Lines AB - Billing Address AM - Mailing Address

Number Of Passengers AIR - Air Segment

Number Of Passengers ATX - Auxiliary Air Taxi Segment

Number Of Rooms HHL - Hotel Segment HTL - Auxiliary Hotel Segment

Number of stops AIR - Air Segment

Number of Unassigned Names NG - Group Name

Numeric Airline Code FA - Auto Ticket Number FA - Auto Ticket Number FH - Manual Ticket Number


128 Edition 4.0


Occupancy HHL - Hotel Segment

Office ID and Access Mode RC - Confidential Remark

Office Identifier FA - Auto Ticket Number OP - Option Queue RC - Confidential Remark

Office Of Responsibility PNR Header

Off Point AIR - Air Segment Any Itinerary Segment ATX - Auxiliary Air Taxi Segment FLWN - Air Flown Segment OPEN - Open Air Segment TRN - Train Segment

Off Point Country State AIR - Air Segment OPEN - Open Air Segment

Open Date Segments Air Itinerary segments

Open Jaw Itinerary Air Itinerary segments

Open Tag OPEN - Open Air Segment

Origin Airport Air Itinerary segments

Origin Country State Air Itinerary segments

Original Conjunction Check Digit FO - Original Issue

Original Conjunction Ticket Coupon FO - Original Issue

Original Conjunction Ticket Number FO - Original Issue

Original Document Check Digit FO - Original Issue

Original Document Coupon FO - Original Issue

Original Document Number FO - Original Issue

Original Issued City FO - Original Issue

Original Issued Date FO - Original Issue

Original Issued IATA Number FO - Original Issue

Passenger Association AB - Billing Address AI - Accounting AIR - Air Segment AM - Mailing Address AP - Phone ARNK - Arrival Unknown Segment ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment CCR - Car Segment FA - Auto Ticket Number FD - Fare Discount FE - Endorsement FH - Manual Ticket Number FI - Auto Invoice Number FLWN - Air Flown Segment FM - Commission FO - Original Issue FP - Form Of Payment FS - Miscellaneous Ticket Information FT - Tour Code FV - Validating Carrier FY - Fare Override



Property... ...can be extracted from element: HHL - Hotel Segment HTL - Auxiliary Hotel Segment INS - Travel Assistance MIS - Miscellaneous Segment OP - Option Queue OPEN - Open Air Segment OSI - Other Service Information RC - Confidential Remark RIA - Adjustment Remark Invoice RIB - Agency Billing Data RIC - Print Agency Due Date RID - Agency Due Date RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIM - Profile Itinerary Remark RIO - Itinerary Invoice Remark RIP - Invoice Remark RIR - Itinerary Remark RIS - Service Fee Air RIT - Override Invoice Total RIU - Auxiliary Product Form of Payment RIZ - Miscellaneous Ticketing Remark RM - General Remark SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TK - Ticket TRN - Train Segment

Passenger Name CCR - Car Segment

Passenger Type AI - Accounting FA - Auto Ticket Number FD - Fare Discount FE - Endorsement FH - Manual Ticket Number FI - Auto Invoice Number FM - Commission FO - Original Issue FS - Miscellaneous Ticket Information FT - Tour Code FV - Validating Carrier FY - Fare Override NM - Name RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIR - Itinerary Remark

Past Tag ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment CCR - Car Segment HHL - Hotel Segment HTL - Auxiliary Hotel Segment

Penalty FO - Original Issue

Pickup Date Any Itinerary Segment CCR - Car Segment CAR - Auxiliary Car Segment

Pickup Instructions CCR - Car Segment

Pick-up-point City CAR - Auxiliary Car Segment

PNR Tags PNR Header


130 Edition 4.0


Premium Amount INS - Travel Assistance

Premium Currency INS - Travel Assistance

Pricing Indicator TST - Transitional Stored Ticket

Product INS - Travel Assistance

Property Code HHL - Hotel Segment

Property Name HHL - Hotel Segment

Provider Code INS - Travel Assistance

Provider Indicator MIS - Miscellaneous Segment

Queue Data OP - Option Queue TK - Ticket

Queuing Office PNR Header

Rate HHL - Hotel Segment

Rate Code CCR - Car Segment

Rate Guarantee Any Itinerary Segment CCR - Car Segment

Rate Guarantee Amount CCR - Car Segment

Rate Guarantee Currency CCR - Car Segment

Rate Guarantee Data CCR - Car Segment

Rate Quoted CCR - Car Segment HHL - Hotel Segment

Rate Quoted Amount CCR - Car Segment HHL - Hotel Segment

Rate Quoted Currency Code CCR - Car Segment HHL - Hotel Segment

Rate Quoted Data CCR - Car Segment

Received From PNR Header

Record Locator PNR Header

Request Type ST - Special Service Request Seat

Restricted RC - Confidential Remark

Return Date CAR - Auxiliary Car Segment

Return Time CCR - Car Segment

Rollaway Adult HHL - Hotel Segment

Rollaway Adult Amount HHL - Hotel Segment

Rollaway Adult Currency Code HHL - Hotel Segment

Rollaway Adult Number HHL - Hotel Segment

Rollaway Child HHL - Hotel Segment

Rollaway Child Amount HHL - Hotel Segment

Rollaway Child Currency Code HHL - Hotel Segment

Rollaway Child Number HHL - Hotel Segment

Room Override HHL - Hotel Segment




Room Rate Code Any Itinerary Segment HHL - Hotel Segment

Round Trip Air Itinerary segments

Safety Compliance HHL - Hotel Segment

Scheduled Duration Any Itinerary Segment

Seat Data ST - Special Service Request Seat

Second Issued In Exchange Check Digit

FO - Original Issue

Second Issued In Exchange City FO - Original Issue

Second Issued In Exchange Conj Chk Digit

FO - Original Issue

Second Issued In Exchange Conj Tkt Coupon

FO - Original Issue

Second Issued In Exchange Conjuncted Date

FO - Original Issue

Second Issued In Exchange Conjuncted Ticket Number

FO - Original Issue

Second Issued In Exchange Coupon FO - Original Issue

Second Issued In Exchange Document FO - Original Issue

Second Issued In Exchange Free Flow FO - Original Issue

Second Issued In Exchange IATA FO - Original Issue

Second Issued In Exchange IATA Number

FO - Original Issue

Second Issued In Exchange Numeric Airline Code

FO - Original Issue

Second Issued In Exchange Ticket Number

FO - Original Issue


132 Edition 4.0


Segment Association AB - Billing Address AI - Accounting AIR - Air Segment AM - Mailing Address AP - Phone ARNK - Arrival Unknown Segment ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment CCR - Car Segment FA - Auto Ticket Number FD - Fare Discount FE - Endorsement FH - Manual Ticket Number FI - Auto Invoice Number FLWN - Air Flown Segment FM - Commission FO - Original Issue FP - Form Of Payment FS - Miscellaneous Ticket Information FT - Tour Code FV - Validating Carrier FY - Fare Override HHL - Hotel Segment HTL - Auxiliary Hotel Segment INS - Travel Assistance MIS - Miscellaneous Segment OP - Option Queue OPEN - Open Air Segment OSI - Other Service Information RC - Confidential Remark RIA - Adjustment Remark Invoice RIB - Agency Billing Data RIC - Print Agency Due Date RID - Agency Due Date RIF - Freeflow Invoice Remark RII - Invoice Itinerary Remark RIM - Profile Itinerary Remark RIO - Itinerary Invoice Remark RIP - Invoice Remark RIR - Itinerary Remark RIS - Service Fee Air RIT - Override Invoice Total RIU - Auxiliary Product Form of Payment RIZ - Miscellaneous Ticketing Remark RM - General Remark SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TK - Ticket TRN - Train Segment

Segment Date Any Itinerary Segment

Segment identifier CAR - Auxiliary Car Segment CCR - Car Segment FA - Auto Ticket Number FD - Fare Discount FE - Endorsement HHL - Hotel Segment HTL - Auxiliary Hotel Segment TRN - Train Segment

Segment Type Any Itinerary Segment




Service Information HHL - Hotel Segment

Service Type RIA - Adjustment Remark Invoice

Special Equipment CCR - Car Segment

Special Information CCR - Car Segment

SSR Element Code SSR - Special Service Request

Status Code AIR - Air Segment Any Itinerary Segment ATX - Auxiliary Air Taxi Segment CAR - Auxiliary Car Segment CCR - Car Segment HHL - Hotel Segment HTL - Auxiliary Hotel Segment INS - Travel Assistance MIS - Miscellaneous Segment SSR - Special Service Request SSR FQTV - Special Service Request Frequent Traveller ST - Special Service Request Seat TRN - Train Segment

Stop Overs Air Itinerary segments

Subscriber Address INS - Travel Assistance

Subscriber Name INS - Travel Assistance

Substitute Name INS - Travel Assistance

Supplementary Information INS - Travel Assistance

System Provider TRN - Train Segment

Tax FO - Original Issue

Tax Override FY - Fare Override

Termination Airport Air Itinerary segments

Termination Country State Air Itinerary segments

Text all elements

Ticket Number FA - Auto Ticket Number

Ticket Number as a number. FH - Manual Ticket Number

Ticket Number as a string FH - Manual Ticket Number

Time (Number) TK - Ticket

Time (String) TK - Ticket

Total Collection TST - Transitional Stored Ticket

Total Fare Override FY - Fare Override

Total Value Amount INS - Travel Assistance

Total Value Currency INS - Travel Assistance

Tour code FT - Tour Code

Tour Number CCR - Car Segment

Tour Operator Code INS - Travel Assistance

Tour Type FT - Tour Code


134 Edition 4.0


Tracking Data CCR - Car Segment

Train Number TRN - Train Segment

Trip Arrival Date INS - Travel Assistance

Trip Departure Date INS - Travel Assistance

Trip Type INS - Travel Assistance

Value Added Tax Indicator FM - Commission

Vendor Code Any Itinerary Segment

Voucher Value CCR - Car Segment

Wait List Segments Air Itinerary segments

Written Confirmation HHL - Hotel Segment

Zap Off AIR - Air Segment

PNR and TST Elements

AB - Billing Address

Billing Address Checks AB items in PNR.

Address Data Checks the address portion of an AB or AM item.

Element Number Element Number in the PNR.

Number Of Lines Checks the number of lines in the billing address field.

Text Finds presence of particular data in PNR element.

Element Identifier Returns the element identifier.

Passenger Association Returns the passenger association for each AB element.

Segment Association Returns the segment association for each AB element.

AI - Accounting

Accounting Checks AI items in PNR.




Passenger Type Returns the passenger type indicator (PAX, INF).

Account Number Returns the account number.

Cost Center Returns the cost center.

IATA Company Number Returns the IATA company number.

Passenger Association Returns the passenger association for each AI element.



Accounting Checks AI items in PNR.

Segment Association Returns the segment association for each AI element.

Air Itinerary Segment

Air Itinerary segments Examines the AIR segments as a whole, instead of looking at one AIR segment at a time.

Arrival Date Extracts date of last segment. Example: 14SEP, 14SEP01, 14SEP2001

Days Advance Book Extracts number of days between creation date of PNR and day of first air segment. Example: 9

Days Advance Purchase Extracts number of days between today and date of departure in first segment. Example: 9

Days Stay Duration Returns the total number of days spent at the destination point. It is the difference between date of arrival at and date of departure out of destination city. Example: 9

Days Stay Of Week Return the list of days stay at the destination point, comma separated. Example: 1,2,3,4,5,6,7 (1 is MONDAY)

Departure Date Extracts date of first segment. Example: 14SEP, 14SEP01, 14SEP2001

Destination Airport Extracts destination airport from PNR. Example: NYC. This information is not provided by the distribution system but calculated by QC from air itinerary segments. The following rules are applied: • PNR with one AIR segment:

DESTINATION_AIRPORT=TERMINATION_AIRPORT Example: in ZRH->DEL, DEL is the destination airport.

• PNR with exactly two AIR segments: A one-way trip is identified: DESTINATION_AIRPORT = OFF_POINT of leg 2. Example: in PAR->NCE->LHR, LHR is the destination point. A return trip is identified: DESTINATION_AIRPORT = OFF_POINT of leg 1. Example: in NCE->CDG->NCE, CDG is the destination point.

• PNR with more than two AIR segments You need to manually add an RC element with the format RC DESTINATION-XXX (where XXX is the IATA city code). Without this element, the destination airport cannot be identified. If the location XXX is found in the list of air segments off-point, then DESTINATION_AIRPORT = XXX

• All other cases: DESTINATION_AIRPORT cannot be determined DESTINATION_AIRPORT = NULL

Destination Country State

Extracts destination country code. Example: US

Domestic Checks whether a PNR is domestic.

Duplicate Segments Checks if there are 2 identical air segments with different booking classes.


136 Edition 4.0

Air Itinerary segments Examines the AIR segments as a whole, instead of looking at one AIR segment at a time.


International Checks whether PNR travels are international.

Issue By Date Extracts today date from host. Example: 14SEP, 14SEP01, 14SEP2001

Open Date Segments Checks presence of an OPEN segment in PNR.

Open Jaw Itinerary Checks presence of an OPEN JAW in PNR. Returns true if there is at least 1 air segment whose arrival airport is not the same as the next legs depart. An Open Jaw is a trip similar to a round trip, but where the passenger returns to a city other than that of original departure or returns from a city other than the original destination. Example: NCE->LON, PAR->NCE

Origin Airport Extracts originating airport from PNR. Example: NYC

Origin Country State Extracts originating country code. Example: US

Round Trip Checks whether PNR is round-trip or not Returns true if the Origin and the Termination airports are in the same city (True for ORY and CDG). False else or if only one air segment. A Round trip is a travel that begins and ends in the same city and usually specifies the same routing in both directions. Example: PAR->NCE, NCE->LON, LON->NCE, NCE->PAR

Stop Overs Returns number of STOP-OVERS in PNR.

Termination Airport Extracts airport code of off-point in last segment. Example: NYC

Termination Country State

Extracts country of off-point in last segment. Example: US


Wait List Segments Checks presence of WAIT LISTED segments in PNR.

Circle Itinerary Checks whether PNR itinerary is circular. Returns true if the itinerary is circular. Return false if the itinerary is not circular or if the destination airport is unknown. A Circle trip is a trip that originates and ends in the same city but that has a stop in a city which is not the major destination and requires different routing on the outbound and return portions. Example: MIA->LHR, LHR->BKK, BKK->ICN, ICN->MIA



AIR - Air Segment

Air Segment Checks each AIR segment in the PNR, one at a time.

Airline Extracts IATA airline code for each PNR air segment. Example: AA

Arrival Time Extracts arrival time for each PNR air segment. Example: 1030P, 2230

Board Point Extracts originating airport for each PNR air segment. Example: AMS

Class Extracts booking class for each PNR air segment. Example: C

Day Change Extracts day change indicator from air segment. Example: 1, -1

Departure Date Extracts departure date for each PNR air segments. Example: 14AUG, 14AUG01, 14AUG2001

Departure Time Extracts departure time for each PNR air segments. Example: 1030P, 2230


Equipment Extracts the aircraft equipment code from the air segment. Example: 747

Fare Code Extracts private fare code from TST for air segment. Example: ARN50

Flight Number Extracts flight number for each PNR air segment. Example: 4542

Form Of Payment Extracts the form of payment associated to this air segment from FP line.

Join Car Checks whether a car is booked when PNR includes at least 4 hours.

Join Hotel Checks whether a hotel is booked when PNR includes at least 8 hours and a change of date.

Number Of Passengers Extracts number of names in PNR. Example: 3

Off-Point Extracts destination airport for each PNR air segment. Example: NCE

Fare Basis Extracts private fare basis code from TST for air segment. Example: HPASS

Status Code Extracts status code for each PNR air segment. Example: HK, HL.


Zap Off Extracts ZAP_OFF data from TST for air segment. Example: 9 or 100A

Board Point Country State Returns the country and the state of the originating airport, if available. Example: returns USNY for originating airport JFK

Off Point Country State Returns the country and the state of the destination airport, if available. Example: returns USMA for originating airport BOS

Joint Airline Extracts IATA joint airline code for each PNR air segment. Example: AA


138 Edition 4.0

Air Segment Checks each AIR segment in the PNR, one at a time.

Check in Time Extracts Check in time for each PNR air segment. Example: 2230

Meal Service Codes Extracts the meal service codes if any.

Entertainment Returns true when entertainment exists.

Day Of Week Extracts the day of the week (Monday is 1).

Number of stops Extracts the number of stops for each PNR air segment.

Airline Reference Extracts the airline reference (could be an airline record locator or a reservation agent name).

Access Sell Tag Returns true when segment was sold via Access Sell (*1A/).

Allotment Tag Returns true when segment was sold via an Allotment (LOT*).

Direct Access Extracts direct access code.

Electronic Ticketing Tag Returns the electronic ticketing indicator for each PNR air segment.

Married Segment Id Extracts the married segment ID for each PNR air segment.

Airport Board Zone Extracts the airport zone at board point.

Passenger Association Returns the passenger association for each PNR air segment.

Segment Association Returns the segment association for each PNR air segment.

Arrival Date Extracts the arrival date for each PNR air segment if displayed.

AM - Mailing Address

Mailing Address Checks AM items in PNR.

Address Data Checks the field.


Number Of Lines Checks the number of lines in the field.



Passenger Association Returns the passenger association for each AM element.

Segment Association Returns the segment association for each AM element.



Any Itinerary Segment

Any itinerary segments Checks any type of segment in the itinerary.

Arrival Time Extracts arrival time for each PNR air segment. Example: 1030P, 2230


Car Type Checks the car type code. Example: ECAR

Check in Date Checks the check in date.

Check out Date Checks check out date.

Class Of Service Extracts booking class for each PNR air segment. Example: C

Confirmation Number Checks the confirmation number of the car segment.

Day Change Extracts day change indicator from air segment. Example: 1, -1

Departure Date Extracts departure date for each PNR air segment. Example: 14AUG, 14AUG01, 14AUG2001

Departure Time Extracts departure time for each PNR air segment. Example: 1030P, 2230

Drop off Date Checks the date the car will be dropped off.


Equipment Extracts the aircraft equipment code from the air segment. Example: 747

Location Extracts city code for each automated hotel segment

Number in party Extracts number of names in PNR. Example: 3

Off-point Extracts destination airport for each PNR air segment. Example: NCE

Pickup Date Checks the date the car will be picked up.

Rate Guarantee Checks the rate guarantee.

Room Rate Code Checks the room type.

Segment Date Checks the date of the segment.

Segment Type Checks the type of the segment. Example: AIR, CAR

Status Code Extracts status codes for each PNR air segments. Example: HK, HL.


Vendor Code Extracts Vendor code for each automated car segment.

Check in Date Returns the Check in date for Hotel segments.

Check out Date Returns the Check out date for Hotel segments.

Drop off Date Returns the Drop off date for Car segments.

Scheduled Duration Returns the flights' scheduled duration for Air segments.


140 Edition 4.0

Any PNR Element

Any PNR elements Checks all elements in the PNR.


Element ID Checks the element ID of the PNR element.


AP - Phone

Phone Checks AP items in PNR.



Contact Type Type of phone elements which corresponds to 3rd letter of the tag when present (B for APB, E for APE, X for APX, ...) or empty string when the tag is simply AP (no 3rd letter).

Contact Text Free flow following the 3rd letter of the tag when present or equal to the current "Free flow" property when the tag is simply AP.

Element Identifier Returns the element identifier (AP).

Free Flow Returns the whole free flow message starting after the AP text.

Passenger Association Returns the passenger association for each AP element.

Segment Association Returns the segment association for each AP element.

ARNK - Arrival Unknown Segment

Arrival Unknown Segment

Checks ARNK itinerary items.




Passenger Association Returns the passenger association for each PNR air segment.

Segment Association Returns the segment association for each PNR air segment.



ATX - Auxiliary Air Taxi Segment

Auxiliary Air Taxi Segment

Checks ATX itinerary items in PNR.



Airline Code Returns the airline code.

Status Code Returns the status code.

Number Of Passengers Returns the number of passengers.

Board Point Returns the board point.

Off Point Returns the off point.

Departure Date Returns the departure date.

Free Flow Extracts the free-flow message.

Past Tag Returns PAST if the indicator PAST is found.

Passenger Association Returns the passenger association for each ATX segment.

Segment Association Returns the segment association for each ATX segment.

Element Identifier Returns the element identifier (ATX).

CAR - Auxiliary Car Segment

Auxiliary Car Segment Checks CAR itinerary items in PNR.

Airline Code Extracts Vendor code for each manual car segment.



Segment identifier Extracts the Auxiliary Car segment identifier (CAR).

Status Code Extracts status code for each Hotel segment. Example: HK

Number Of Cars Returns the number of cars confirmed.

Pick-up-point City Extracts the pick-up-point city code.

Pick-up Date Extracts the pick-up date.

Return Date Extracts the return date.

Car Type Extracts the car type.

Free-flow Message Extracts the free-flow message.

Past Tag Returns the past tag if present (PAST).

Booking Source Returns the booking source number.

Confirmation Number Extracts the confirmation number.

Passenger Association Returns the passenger association for each CAR segment.

Segment Association Returns the segment association for each CAR segment.


142 Edition 4.0

CCR - Car Segment

Car Segment Checks CCR items in PNR.

Car Type Checks the car type code. Example: ECAR

Company Extracts Vendor code for each automated car segment.

Confirmation Number Checks the confirmation number of the car segment.

Drop Off Date Checks the date the car will be dropped off.


Location Finds presence of particular data in automated booked car segment.

Pickup Date Checks the date the car will be picked up.

Rate Guarantee Checks the rate guarantee.


Segment identifier Extracts the Car segment identifier (CCR).

Status Code Extracts status code for each Car segment. Example: HK.

Number Of Cars Returns the number of cars confirmed.


Booking Source Extracts the IATA code of the office that made the booking, behind identifier /BS-. Example: 12345675

Booking Agent Identifier Extracts the booking agent identifier, behind identifier /AI-. Example: 12345675

Arrival Information Extracts Car arrival information, behind identifier /ARR-

Drop Off Information Extracts Car drop off information, behind identifier /DO-

Passenger Name Extracts the passenger name, behind identifier /NM-

Corporate Rate Extracts the corporate identifier, behind identifier /CR-

Frequent Traveler Number Extracts the frequent traveller number, behind identifier /FT-

Customer Identifier Extracts the customer number, behind identifier /ID-

Tour Number Extracts the Tour number, behind identifier /IT-

Pickup Instructions Extracts the pick up information, behind identifier /PUP-

Location Code Extracts the location code when non-airport location, behind identifier /LC-

Rate Code Extracts the rate category and plan and provider rate code, behind identifier /RC-

Return Time Extracts the return time, behind identifier /RT-

Special Equipment Extracts the special equipment, behind identifier /SQ-

Rate Quoted Extracts the rate that has been quoted to a client by the car company, behind identifier /RQ-

Rate Quoted Currency Extracts the rate quoted currency from the rate quoted field.

Rate Quoted Amount Extracts the rate quoted amount from the rate quoted field.

Rate Quoted Data Extracts the rate quoted data from the rate quoted field.



Car Segment Checks CCR items in PNR.

Rate Guarantee Currency Extracts the rate guaranteed currency, behind identifier /RG-

Rate Guarantee Amount Extracts the rate guaranteed amount, behind identifier /RG-

Rate Guarantee Data Extracts the rate guaranteed data, behind identifier /RG-

Agency Accounting Data Extracts the agency accounting data, behind identifier /**-

Special Information Extracts the special information, behind identifier /SI-

Delivery Extracts the delivery address, behind identifier /DEL-

Collection Extracts the collection address, behind identifier /COL-

Voucher Value Extracts the voucher value, behind identifier /VV-

Tracking Data Extracts tracking data, behind identifier /TK-

Billing Number Extracts the billing number, behind identifier /BN-

Billing Reference Extracts the billing reference, behind identifier /BR-

Passenger Association Returns the passenger association for each CCR segment.

Segment Association Returns the segment association for each CCR segment.

Car Company Extracts the Company code and access level indicator.

Car Free Flow Extracts the car free flow message.

Car Base Rate Free Flow Extracts the car base rate free flow text, behind identifier /RB-

Car Rate Data Extracts the car base rate data, behind identifier /RB-

Car Base Rate Car Company

Extracts the car base rate car company, behind identifier /RB-

Car Base Rate Currency Extracts the car base rate currency, behind identifier /RB-

Car Base Rate Amount Extracts the car base rate amount, behind identifier /RB-

Car Estimated Total Currency

Extracts the estimated total currency.

Car Estimated Total Amount

Extracts the estimated total amount.

Car Estimated Total Data Extracts the estimated total data.

Car Corporate ID Data Extracts the car corporate ID data (following the /CD- indicator).


144 Edition 4.0

CRU - Cruise Segment

Cruise Segment Checks CRU itinerary items in PNR.

Cruise Line Code Extracts Vendor code for each automated hotel segment.


Departure Date Checks the date the cruise departs.

Departure Port Extracts city code for the cruise segment.

Text Finds presence of particular data in cruise segment.

Element identifier Returns the element identifier (CRU).

Cruise Booking Status Returns the 2-3 letter code booking status.

Arrival Port Returns the arrival port for the cruise segment.

FA - Auto Ticket Number

Auto ticket number Checks FA items in PNR.



Segment Identifier Extracts the Fare segment identifier (FA).


Numeric Airline Code Extracts the three digit airline code.

Ticket Number Extracts the ten-digit ticket number.

Conjuncted Ticket Number

Extracts the last two digits of the last ticket in the set of tickets.

Electronic Ticketing Carrier

Extracts the electronic ticketing carrier, behind identifier /ET

Electronic Tkt Res Confirmation Number

Extracts the electronic ticketing confirmation number, behind identifier /RCI

Currency Code Extracts the currency code.

Amount Extracts the total ticket amount.


Passenger Association Returns the passenger association for each FA element.

Segment Association Returns the segment association for each FA element.

Numeric Airline Code Extracts the three digit airline code and returns them as a string.

Date Extracts the Date of ticket issue.

Office Identifier Extracts the office that issued the ticket.

IATA Number Extracts the Agency IATA number.



FD - Fare Discount

Fare Discount Checks FD items in PNR.



Segment Identifier Extracts the Fare Discount segment identifier (FD).


Discount Code Extracts the last two discount codes.

Data Extracts the discount data.

Extra Discount Code Extracts the extra last two discount codes.

Extra Discount Data Extracts the extra discount data.

Passenger Association Returns the passenger association for each FD segment.

Segment Association Returns the segment association for each FD segment.

FE - Endorsement

Endorsement Checks FE items in PNR.



Segment Identifier Extracts the endorsement/restriction segment identifier (FE).


Free-flow Message

Passenger Association Returns the passenger association for each FE segment.

Segment Association Returns the segment association for each FE segment.

FH - Manual Ticket Number

Manual Ticket Number Checks FH items in PNR.




Numeric Airline Code Extract the three-digit Airline Code.

Ticket Number as a number.

Returns the 10-digit ticket number as a number.

Check Digit Returns the optional ticket number check digit.

Conjuncted Ticket Number

Extracts the last two digits of the last ticket in the set of tickets.


Passenger Association Returns the passenger association for each FH element.

Segment Association Returns the segment association for each FH element.


146 Edition 4.0

Manual Ticket Number Checks FH items in PNR.

Element Identifier Returns the element identifier FH.

Ticket Number as a string Returns the 10-digit ticket number as a string.

FH Type Returns the FH Type (A=AUTOMATED, M=MANUAL, E=ELECTRONIC)

FI - Auto Invoice Number

Auto Invoice Number Checks FI items in PNR.



Element Identifier Returns the FI element identifier.


Invoice number Returns the invoice number.

Passenger Association Returns the passenger association for each FI element.

Segment Association Returns the segment association for each FI element.

FLWN - Air Flown Segment

Air Flown Segment Checks FLWN air segments in the itinerary.




Off Point Extracts destination airport for each PNR air segment. Example: NCE


Airline Extracts IATA airline code. Example: AA

Joint Airline Extracts IATA joint airline code. Example: AA

Class Extracts booking class. Example: C


Flight No Extracts flight number. Example: 4542

Flown Indicator Extracts the flown tag (FLWN).

Passenger Association Returns the passenger association.

Segment Association Returns the segment association.

FM - Commission

Commission Checks FM items in PNR




Commission Checks FM items in PNR

Commission Percent Extracts commission from FM line. When the commission is entered as a percentage, returns the percentage (e.g.: 9 for FM 9). When the commission is entered as a fixed amount, returns the fixed amount without the A indicator (eg:100.00 for FM 100.00A).


Element Identifier Returns the FM element identifier.


Commission Indicator Returns the 1,2-letter code indicator.

Amount Indicator Returns the Amount indicator A. If returns A, then Percentage or amount is an Amount. Else it is a percentage.

Value Added Tax Indicator Returns the Value Added Tax indicator V.

Capping Amount Returns the Capping amount.

Passenger Association Returns the passenger association for each FM element.

Segment Association Returns the segment association for each FM element.

Commission amount or percentage

Returns the percentage or amount of the commission.

FO - Original Issue

Original Issue Checks FO items in PNR.



Element Identifier Returns the element identifier FO.


Original Document Number Returns the original document number.

Original Document Check Digit

Returns the document check digit.

Original Document Coupon Returns the document coupon data.

Original Conjunction Ticket Number

Returns the original conjunction ticket number.

Original Conjunction Check Digit

Returns the original conjunction check digit.

Original Conjunction Ticket Coupon

Returns the original conjunction ticket coupon data.

Original Issued City Returns the original issued city.

Original Issued Date Returns the original issued date.

Original Issued IATA Number

Returns the original issued IATA number.

Second Issued In Exchange Document

Returns the second issued in exchange document.


148 Edition 4.0

Original Issue Checks FO items in PNR.

Second Issued In Exchange Check Digit

Returns the second issued in exchange check digit.

Second Issued In Exchange Coupon

Returns the second issued in exchange coupon.

Second Issued In Exchange Conjuncted Ticket Number

Returns the second issued in exchange conjuncted ticket number.

Second Issued In Exchange Conj Chk Digit

Returns the second issued in exchange conjuncted check digit.

Second Issued In Exchange Conj Tkt Coupon

Returns the second issued in exchange conjuncted ticket coupon.

Second Issued In Exchange Conjuncted Date

Returns the second issued in exchange conjuncted date.

Second Issued In Exchange City

Returns the second issued in exchange city.

Second Issued In Exchange IATA Number

Returns the second issued in exchange IATA number.

Second Issued In Exchange IATA

Returns the second issued in exchange IATA data.

Base Fare Returns the base fare.

Tax Returns the tax.

Penalty Returns the penalty.

Free Flow Returns the Free flow information.

Passenger Association Returns the element association for each FO element.

Segment Association Returns the segment association for each FO element.

Issued In Exchange Numeric Airline Code

Returns the issued in exchange numeric airline code.

Second Issued In Exchange Numeric Airline Code

Returns the second issued in exchange numeric airline code.

Issued In Exchange Ticket Number

Returns the issued in exchange ticket number.

Second Issued In Exchange Ticket Number

Returns the second issued in exchange ticket number.

Amount Returns the amount.

Currency Returns the currency.

Second Issued In Exchange Free Flow

Returns the second issued in exchange free flow text.

Issued In Exchange Coupon Indicator

Returns the issued in exchange coupon indicator.

FP - Form Of Payment

Form of payment Checks FP items in PNR.




Form of payment Checks FP items in PNR.



Passenger Association Returns the passenger association for each FP segment.

Segment Association Returns the segment association for each FP segment.

Form Of Payment Text Returns the sub text ending before AQ indicator in FP text.

AQ Text Returns the sub text starting by AQ in the FP text.

FS - Miscellaneous Ticket Information

Miscellaneous Ticket Information

Checks FS items in PNR.



Element Identifier Returns the FS element identifier.



Passenger Association Returns the passenger association for each FS element.

Segment Association Returns the segment association for each FS element.

FT - Tour Code

Tour code Checks FT items in PNR.



Element Identifier Returns the FT element identifier.


Tour Type Returns the 2 letter code NR Tour type.

Tour code Returns the Tour code.


Passenger Association Returns the passenger association for each FT element.

Segment Association Returns the segment association for each FT element.

FV - Validating Carrier

Validating carrier Checks FV items in PNR.





150 Edition 4.0

Validating carrier Checks FV items in PNR.


Carrier Returns the airline code.

Passenger Association Returns the passenger association for each FV element.

Segment Association Returns the segment association for each FV element.

FY - Fare Override

Fare Override Checks FY items in PNR.





Base Fare Override Returns the base fare override (up to 11 characters).

Equivalent Fare Override Returns the equivalent fare override (up to 11 characters following /E).

Tax Override Returns the tax override (following the /X).

Total Fare Override Returns the total fare override (following the /T).

Passenger Association Returns the element association for each FY element.

Segment Association Returns the segment association for each FY element.

HHL - Hotel Segment

Hotel Segment Checks HHL items in PNR.

Chain Code Extracts Vendor code for each automated hotel segment.

Check in Date Checks the checkin date.

Check Out Date Checks check-out date.

City Extracts city code for each automated hotel segment.

Confirmation Number Checks the confirmation number of the hotel segment.


Guarantee Checks the rate guarantee.

Room Rate Code Checks the room type.


Segment identifier Extracts the Hotel segment identifier (HHL).


Number Of Rooms Returns the number of rooms booked.


Currency Code Extracts the currency code.

Rate Extracts the rate amount.




Property Code Extracts the last three characters of the property code.

Property Name Extracts the Hotel name.

Daily Indicator Returns the daily indicator when daily rate (DLY).

American Plan Extracts the American Plan data, behind identifier /AP-

American Plan Currency Code

Extracts the American Plan extra charge currency code, behind identifier /AP-

American Plan Amount Extracts the American Plan extra charge amount, behind identifier /AP-

American Plan Number Extracts the American Plan number, behind identifier /AP-

Amount Override Extracts the Amount Override data, behind identifier /AO-

Amount Override Currency Code

Extracts the Amount Override currency code, behind identifier /AO-

Amount Override Amount Extracts the Amount Override amount, behind identifier /AO-

Corporate Identifier Extracts the customer corporate identifier, behind identifier /CD-

Hotel Message Extracts the Hotel free flow message.

Crib Extracts rollaway crib option, behind identifier /CR-

Crib Currency Code Extracts the crib extra charge currency code, behind identifier /CR-

Crib Amount Extracts the crib extra charge amount, behind identifier /CR-

Crib Number Extracts the crib number, behind identifier /CR-

Rollaway Adult Extracts the adult rollaway option, behind identifier /RA-

Rollaway Adult Currency Code

Extracts the adult rollaway extra charge currency code, behind identifier /RA-

Rollaway Adult Amount Extracts the adult rollaway extra charge amount, behind identifier /RA-

Rollaway Adult Number Extracts the adult rollaway number, behind identifier /RA-

Deposit Extracts the deposit option, behind identifier /DP-

Rollaway Child Extracts the child rollaway option, behind identifier /RC-

Rollaway Child Currency Code

Extracts the child rollaway extra charge currency code, behind identifier /RC-

Rollaway Child Amount Extracts the child rollaway extra charge amount, behind identifier /RC-

Rollaway Child Number Extracts the child rollaway number, behind identifier /RC-

Extra Person Extracts the extra person option, behind identifier /EX-

Extra Person Currency Code

Extracts the extra person extra charge currency code, behind identifier /EX-

Extra Person Amount Extracts the extra person extra charge amount, behind identifier /EX-

Extra Person Number Extracts the extra person number, behind identifier /EX-


152 Edition 4.0


Family American Extracts the Family American Plan option, behind identifier /FA-

Family American Currency Code

Extracts the Family American Plan extra charge currency code, behind identifier /FA-

Family American Amount Extracts the Family American Plan extra charge amount, behind identifier /FA-

Family American Number Extracts the Family American Plan number, behind identifier /FA-

Family Modified Extracts the Family Modified American Plan option, behind identifier /FM-

Family Modified Currency Code

Extracts the Family Modified American Plan extra charge currency code, behind identifier /FM-

Family Modified Amount Extracts the Family Modified American Plan extra charge amount, behind identifier /FM-

Family Modified Number Extracts the Family Modified American Plan number, behind identifier /FM-

Customer Identifier Extracts the customer identification number option, behind identifier /ID-

Modified American Extracts the Modified American Plan option, behind identifier /MA-

Modified American Currency Code

Extracts the Modified American Plan extra charge currency code, behind identifier /MA-

Modified American Amount

Extracts the Modified American Plan extra charge amount, behind identifier /MA-

Modified American Number

Extracts the Modified American Plan number, behind identifier /MA-

Room Override Extracts the room override option, behind identifier /RO-

Rate Quoted Extracts the rate quote option, behind identifier /RQ-

Rate Quoted Currency Code

Extracts the rate quote currency code, behind identifier /RQ-

Rate Quoted Amount Extracts the rate quote amount, behind identifier /RQ-

Service Information Extracts the supplementary information option, behind identifier /SI-

Safety Compliance Extracts the safety compliancy option, behind identifier /SF-

Written Confirmation Extracts the written confirmation option, behind identifier /W-

Agency Accounting Extracts agency accounting information, behind identifier /**-

Passenger Association Returns the passenger association for each Hotel segment.

Segment Association Returns the segment association for each Hotel segment.

Booking Source Returns the booking source number, behind identifier /BS-

Occupancy Returns the occupancy booked.

Hold Information Extracts the hold information, behind identifier /HLD-



HTL - Auxiliary Hotel Segment

Auxiliary Hotel Segment Checks HTL itinerary items in PNR.



Segment identifier Extracts the Auxiliary Hotel segment identifier (HTL).

Airline Extracts the Airline Code.


Number Of Rooms Returns the number of rooms booked.

Check-in City Extracts the Check-in city code.

Check-in Date Extracts the Check-in date.

Check-out Date Extracts the Check-out date.

Free-flow Text Extracts the free-flow text.


Confirmation Number Extracts the confirmation number.

Booking Source Returns the booking source number.

Passenger Association Returns the passenger association for each HTL segment.

Segment Association Returns the segment association for each HTL segment.

INS - Travel Assistance

Travel Assistance Checks INS itinerary items in PNR.



Element Identifier Returns the product identifier (INS).

Country Returns the country code.


Product Returns the provider product code.

Trip Departure Date Returns the trip departure date.

Destination Zone Returns the destination zone.

Premium Currency Returns the premium currency code (in the /TP- part)

Confirmation Number Returns the confirmation number.

Total Value Currency Returns the currency of the total value.

Subscriber Address Returns the subscriber address.

Date Of Birth Returns the beneficiary date of birth.

Fare Discount Returns the fare discount.

Beneficiary Names Returns the beneficiary names.

Substitute Name Returns the substitute name.


154 Edition 4.0

Travel Assistance Checks INS itinerary items in PNR.

Supplementary Information

Returns the supplementary information.

Tour Operator Code Returns the tour operator code.

Trip Type Returns the trip type.

Name Of Person Insured Returns the insured person name.

Commission Percentage Returns the commission percentage.

Number In Party Returns the number in party.

Trip Arrival Date Returns the trip arrival date.

Premium Amount Returns the premium amount (in the /TP- part)

Provider Code Returns the provider code.

Nanny Name Returns the nanny name.

Total Value Amount Returns the total value amount (in the /TV- part).

Coverage Currency Returns the coverage currency code (in the /CV- part).

Coverage Amount Returns the coverage amount (in the /CV- part).

Subscriber Name Returns the subscriber name.

Passenger Association Returns the passenger association for each INS element.

Segment Association Returns the segment association for each INS element.

MIS - Miscellaneous Segment

Miscellaneous segment Checks MIS items in PNR.



Element Identifier Returns the element identifier (MIS).

Provider Indicator Returns the airline code or the code of the airline to take action.


Number in party Returns the number in party.

City Returns the city from, pick-up city, city code, ...

Date Returns the requested date.


Passenger Association Returns the passenger association for each MIS element.

Segment Association Returns the segment association for each MIS element.

NG - Group Name

Group Name Checks NG items in PNR.





Group Name Checks NG items in PNR.

Number of Unassigned Names

Returns the number of unassigned names.

Group Name Returns the group name.

Number of Assigned Names

Returns the number of assigned names.

NM - Name

Name Checks NM items in PNR.


Initial First initial portion of the name field.

Last Name Last name portion of the name field.


ID Code The id code is a special type of passenger code used for entering an id number for identification purposes.

Infant Infants travelling with an adult passenger (e.g.: (INFBROWN/MICHAEL/10).

Infant Initial Initial of the Infant.

Infant Last Name Last name of the Infant in case it is different from the adult.

Passenger Type Three-letter passenger type codes to the name to indicate the type of passenger (e.g.: YTH).

Extra Seat True if an Extra Seat for personal comfort exists. False else.

Cabin Baggage Returns the code used for Extra Seat for cabin baggage (ex: /CBBG).

OP - Option Queue

Option Queue Checks OP items in PNR.



Element Identifier Returns the element identifier (OP).

Office Identifier Returns the office identifier.

Date Returns the date.

Queue Data Returns the queue number and category.


Passenger Association Returns the passenger association for each OP element.

Segment Association Returns the segment association for each OP element.


156 Edition 4.0

OPEN - Open Air Segment

Open Air segment Checks OPEN air segments in the itinerary.




Off Point Extracts destination airport for each PNR air segment. Example: NCE


Board Point Country State Returns the country and the State if available (for JFK, return USNY) corresponding to the Board Point.

Off Point Country State Returns the country and the State if available (for JFK, return USNY) corresponding to the Board Point.

Airline Extracts IATA airline code for each PNR air segment. Example: AA

Joint Airline Extracts IATA joint airline code for each PNR air segment. Example: AA

Free Flow Returns the Air Open free flow text.

Open Tag Extracts the OPEN tag.

Passenger Association Returns the passenger association.

Segment Association Returns the segment association.

Class Extracts booking class. Example: C


OSI - Other Service Information

Other Service Information

Checks OS items in PNR.



Element Identifier Returns the element identifier (OSI).



Passenger Association Returns the passenger association for each OSI element.

Segment Association Returns the segment association for each OSI element.

PNR Header

PNR Header Checks the text that precedes the names in a PNR display.

Office Of Responsibility Finds presence of particular data in PNR element.



PNR Header Checks the text that precedes the names in a PNR display.

Received From Finds presence of particular data in PNR element.

Record Locator Finds presence of particular data in PNR element.


Queuing Office Returns the queuing office (Office appearing after the second /).

PNR Tags Returns the list of tags.

Alliance Airline Code Returns the airline code appearing after the * in the Receive From line.

Creation Date Returns the creation date of the PNR.

PNR Text

PNR Text Checks the entire body of a PNR display.


RC - Confidential Remark

Confidential Remark Checks RC items in PNR


Office Identifier Checks the office ID of the remark.


Element identifier Returns the office identifier.


Restricted Returns TRUE if the indicator RESTRICTED is found.

Office ID and Access Mode

Returns the list of Office IDs and Access Mode (before the /).

Passenger Association Returns the passenger association for each RC element.

Segment Association Returns the segment association for each RC element.

RI - Unassociated Remark

Unassociated Remarks Checks RI items in PNR.



Element Identifier Returns the element identifier (RIx).


158 Edition 4.0

RIA - Adjustment Remark Invoice

Adjustment Remark Invoice

Checks RIA items in PNR.



Element Identifier Returns the element identifier (RIA).

Currency Code Returns the currency code.


Service Type Returns the service type code (F=Air Service, C=Car Service, M=Auxiliary Service, H=Hotel Service).

Passenger Association Returns the passenger association for each RIA element.

Segment Association Returns the segment association for each RIA element.

RIB - Agency Billing Data

Agency Billing Data Checks RIB items in PNR.



Element Identifier Returns the element identifier (RIB).

Passenger Association Returns the passenger association for each RIB element.

Segment Association Returns the segment association for each RIB element.

RIC - Print Agency Due Date

Print Agency Due Date Checks RIC items in PNR.



Line Number Returns the line number.

Element Identifier Returns the element identifier (RIC).

Passenger Association Returns the passenger association for each RIC element.

Segment Association Returns the segment association for each RIC element.

RID - Agency Due Date

Agency due date Checks RID items in PNR.



Element Identifier Returns the element identifier (RID).

Passenger Association Returns the passenger association for each RID element.

Segment Association Returns the segment association for each RID element.



RIF - Freeflow Invoice Remark

Freeflow invoice remark Checks RIF items in PNR.



Element Identifier Returns the element identifier (RIF).



Passenger Association Returns the passenger association for each RIF element.

Segment Association Returns the segment association for each RIF element.

RII - Invoice Itinerary Remark

Invoice Itinerary Remark Checks RII items in PNR.



Element Identifier Returns the element identifier (RII).



Passenger Association Returns the passenger association for each RII element.

Segment Association Returns the segment association for each RII element.

RIM - Profile Itinerary Remark

Profile Itinerary Remark Checks RIM items in PNR.



Element Identifier Returns the element identifier (RIM).

Line Number Returns the line numbers to be transferred.

Passenger Association Returns the passenger association for each RIM element.

Segment Association Returns the segment association for each RIM element.

RIO - Itinerary Invoice Remark

Itinerary Invoice Remark Checks RIO items in PNR.



Element Identifier Returns the element identifier (RIO).

Line Number Returns the line numbers to be printed.

Passenger Association Returns the passenger association for each RIO element.


160 Edition 4.0

Itinerary Invoice Remark Checks RIO items in PNR.

Segment Association Returns the segment association for each RIO element.

RIP - Invoice Remark

Invoice Remark Checks RIP items in PNR.



Element Identifier Returns the element identifier (RIP).

Line Number Returns the line number to be transferred.

Passenger Association Returns the passenger association for each RIP element.

Segment Association Returns the segment association for each RIP element.

RIR - Itinerary Remark

Itinerary Remark Checks RIR items in PNR.



Element Identifier Returns the element identifier (RIR).



Passenger Association Returns the passenger association for each RIR element.

Segment Association Returns the segment association for each RIR element.

RIS - Service Fee Air

Service Fee Air Checks RIS items in PNR.



Element Identifier Returns the element identifier (RIS).




Passenger Association Returns the passenger association for each RIS element.

Segment Association Returns the segment association for each RIS element.



RIT - Override Invoice Total

Override Invoice Total Checks RIT items in PNR.



Element Identifier Returns the element identifier (RIT).



Passenger Association Returns the passenger association for each RIT element.

Segment Association Returns the segment association for each RIT element.

RIU - Auxiliary Product Form of Payment

Auxiliary Product Form of Payment

Checks RIU items in PNR.



Element Identifier Returns the element identifier (RIU).

Form Of Payment Returns the form of payment.

Passenger Association Returns the passenger association for each RIU element.

Segment Association Returns the segment association for each RIU element.

RIZ - Miscellaneous Ticketing Remark

Misc Ticketing Remark Checks RIZ items in PNR.



Element Identifier Returns the element identifier (RIZ).


Passenger Association Returns the passenger association for each RIZ element.

Segment Association Returns the segment association for each RIZ element.

RM - General Remark

General Remark Checks RM items in PNR.

Category Category of the remark.



Element Identifier Returns the element identifier (RM).



162 Edition 4.0

General Remark Checks RM items in PNR.

Passenger Association Returns the passenger association for each RM element.

Segment Association Returns the segment association for each RM element.

RX - Corporate Remark

Corporate Remark Checks RX items in PNR.



Element Identifier Returns the element identifier (RX).

SSR - Special Service Request

Special Service Request Checks SR items in PNR (SSRs).



Element Identifier Returns the element identifier (SSR).

SSR Element Code Returns the SSR element code (VGML, PSPT, SEAT, ...).





Passenger Association Returns the passenger association for each SSR element.

Segment Association Returns the segment association for each SSR element.

SSR FQTV - Special Service Request Frequent Traveller

SR FQTV Checks FF items in PNR.




Frequent Traveler Code Returns the frequent traveler code.




Airline Of Frequent Flyer Card

Returns the airline code of the frequent flyer card.

Frequent Traveler Number Returns the frequent traveler number.

Frequent Traveler Priority Returns the frequent traveler priority.



SR FQTV Checks FF items in PNR.



ST - Special Service Request Seat

SR Seat ST items in PNR (SSRs).


Text Finds presence of particular data in PNR element


Request Type Returns the seat request type (RQST, NSST, ...).




Airport Pair Returns the airport pair.

Seat Data Returns the seat data (Seat number or free flow).



TK - Ticket

Ticket Checks TK items in PNR.

Action Extracts ticketing action from TK line. Example: OK, TL

Date Extracts ticketing date from TK line. Example: 25 SEP, 25SEP01, 25SEP2001



Element Identifier Returns the element identifier (TK).

Time (Number) Extracts ticketing time from TK line. Example: 1800, as a number.

Location Returns the location.

AF Flag Returns the 6-8 character AF flag data following the slash.

Queue Data Returns the queue number and category.


Document Print Option Returns the document print option.

Passenger Association Returns the passenger association for each TK element.

Segment Association Returns the segment association for each TK element.

ET Airline Code Returns the electronic ticket airline code.

Time (String) Extracts ticketing time from TK line as a string. Example: 1800


164 Edition 4.0

TRN - Train Segment

Train Segment Checks TRN itinerary items in PNR.

Arrival Time Extracts arrival time for each PNR train segment. Example: 1030P, 2230

Board Point Extracts originating airport for each PNR train segment. Example: AMS

Class Of Service Extracts booking class for each PNR train segment. Example: C

Day Change Extracts day change indicator from train segment. Example: 1, -1

Departure Date Extracts departure date for each PNR train segment. Example: 14AUG, 14AUG09, 14AUG2009

Departure Time Extracts departure time for each PNR train segment. Example: 1030P, 2230


Number In Party Extracts number of names in PNR. Example: 3

Off Point Extracts destination airport for each PNR train segment. Example: NCE

Status Code Extracts status codes for each PNR train segments. Example: HK, HL.

System Provider Extracts Vendor code for TRAIN_SEGMENTS items.


Train Number Extracts train number for each PNR train segment. Example: 4542

Segment identifier Returns the segment identifier TRN.

Passenger Association Returns the passenger association for each TRN segment.

Segment Association Returns the segment association for each TRN segment.

TST - Transitional Stored Ticket

Transitional Stored Ticket

Checks TST items in PNR.

Fare Base Line Base Extracts base fare code from TST (i.e. before taxes).

Fare Base Line Currency Code

Extracts currency code from TST.

Text Finds presence of particular data in TST element.

Total Collection Extracts total fare value from TST.

Fare Calculation Mode Indicator

Extracts the fail code indicator (FCMI) from the TST header. It indicates how the itinerary was priced.

Pricing Indicator Extracts the pricing indicator from the TST header (for e.g.: I,A,F,M,N,B,G,T,O).

Fare Issue Indicator Extracts the issue indicator from the TST fare base line (for e.g.: F for First issue or R for Reissue).



Transitional Stored Ticket

Checks TST items in PNR.

Last Date To Ticket Extracts the Last Date To ticket from the TST header Example: TST1 PC NCE1A0900 AK/01MAR M 1 LD 15MAY09 OC MADMAD SI T- AL, Last Date To Ticket is 15MAY09

TST AIR - TST Air Itinerary Segment

TST Air Itinerary Checks Air itinerary elements in TST.

Airline For each Air itinerary segment found in the TST, extracts the IATA Airline code. Example: AA

Text Finds presence of particular data in TST Air Itinerary element.

TTO - Amadeus Tour Segment

Amadeus Tour segment Checks TTO itinerary items in PNR.





Index

A Access restrictions, 61 Action from RuleChecker tab in Administrator, 75, 76 Activating

rule, 20 RuleFile, 20 RuleSet, 49

Administrator launching, 60 overview, 59

All RuleFiles/Sets tab, 9 All RuleLibraries tab, 9 Amadeus Quality Control

components, 4 overview, 3

Amadeus Quality Control Administrator. see Administrator Amadeus Quality Control Manager. see Quality Control Manager Amadeus Quality Control Rule Editor. see Rule Editor Amadeus Quality Control RuleChecker. see RuleChecker Associated actions, 93 Associated RuleFiles/Sets window, 98 Associating RuleFiles to a RuleSet, 50 Associating RuleFiles/Sets to PNRs, 81 Associating RuleFiles/Sets to RuleLibrary, 54 Associating rules

in RuleChecker, 87, 98 RC elements in PNR, 81 RC/RX elements in profile, 82 to agents, 86 to office IDs, 83, 85

Automatic rechecking, 96

B Bypass

automatic PNR tracking, 67 configuration, 66, 67 password, 67

Bypassing RuleChecker, 96

C Checking PNRs without active itinerary, 79 Comparing variables, 42 Confidential remark, 81, 82

Copying in Rule Editor, 10 RuleChecker configuration, 64

Corporate remark, 82 Creating

Rule, 18 RuleFile, 17 RuleLibrary, 54 RuleSet, 50

D Data dictionary, 117 Deleting

RuleFile/Set, 11 RuleLibrary, 11

Deployment overview, 5 RuleChecker configurations, 65 rules, 52

Displaying all rule messages, 101 RuleChecker is processing message, 101 splash screen, 101 success acknowledgement, 101

Displaying associated RuleFiles/Sets, 98

E Element

AB, 134 Accounting, 134 Adjustment Remark Invoice, 158 Agency Billing Data, 158 Agency due date, 158 AI, 134 Air Flown Segment, 146 Air Itinerary segments, 135 Air Segment, 137 AM, 138 Amadeus Tour segment, 165 Any itinerary segment, 139 Any PNR element, 140 AP, 140 ARNK, 140 Arrival Unknown Segment, 140 ATX, 141 Auto Invoice Number, 146 Auto ticket number, 144 Auxiliary Air Taxi Segment, 141 Auxiliary Car Segment, 141 Auxiliary Hotel Segment, 153


168 Edition 4.0

Auxiliary Product Form of Payment, 161 Billing Address, 134 CAR, 141 Car Segment, 142 CCR, 142 Commission, 146 Confidential Remark, 157 Corporate Remark, 162 CRU, 144 Cruise Segment, 144 Endorsement, 145 FA, 144 Fare Discount, 145 Fare Override, 150 FD, 145 FE, 145 FF, 162 FH, 145 FI, 146 FLWN, 146 FM, 146 FO, 147 Form of payment, 148 FP, 148 Freeflow invoice remark, 159 FS, 149 FT, 149 FV, 149 FY, 150 General Remark, 161 Group Name, 154 HHL, 150 Hotel Segment, 150 HTL, 153 INS, 153 Invoice Itinerary Remark, 159 Invoice Remark, 160 Itinerary Invoice Remark, 159 Itinerary Remark, 160 Mailing Address, 138 Manual Ticket Number, 145 MIS, 154 Miscellaneous segment, 154 Miscellaneous Ticket Information, 149 Miscellaneous Ticketing Remark, 161 Name, 155 NG, 154 NM, 155 OP, 155 OPEN, 156 Open Air segment, 156 Option Queue, 155 Original Issue, 147 OS, 156 Other Service Information, 156 Override Invoice Total, 161 Phone, 140 PNR Header, 156 PNR Text, 157 Print Agency Due Date, 158 Profile Itinerary Remark, 159 RC, 157 RI, 157 RIA, 158 RIB, 158 RIC, 158 RID, 158

RIF, 159 RII, 159 RIM, 159 RIO, 159 RIP, 160 RIR, 160 RIS, 160 RIT, 161 RIU, 161 RIZ, 161 RM, 161 RX, 162 Service Fee Air, 160 Special Service Request, 162 SR, 162 SR FQTV, 162 SR Seat, 163 ST, 163 Ticket, 163 TK, 163 Tour code, 149 Train Segment, 164 Transitional Stored Ticket, 164 Travel Assistance, 153 TRN, 164 TST, 164 TST Air Itinerary, 165 TTO, 165 Unassociated Remarks, 157 Validating carrier, 149

End-of-transaction commands, 69 Entering transactions not allowed from RuleChecker, 75, 76 Excluding rules from office IDs, 85 Expired RuleFiles/Sets, 20, 50 Exporting

individual RuleFile, 110 RuleLibrary, 112 RuleSet, 111

F For Each condition

creating, 31 definition, 31 example, 32

Forcing Quality Control replication, 57

I If condition

creating, 21 definition, 21 options, 22

Importing all RuleFiles in folder, 110 individual RuleFile, 109

Informative message definition, 74 displaying, 74

Inheritance, 62, 63 Inheritance level, 63

L Launching

Administrator, 60

Index


Quality Control Manager, 7 Rule Editor, 10 RuleChecker in OND mode, 91 RuleChecker in POS mode, 91

M Modifying

in Rule Editor, 11

N Neutral triggering commands, 69

using, 71

O Office, 61 Office group, 61 Office group with access restrictions, 61 On-demand (OND) mode, 91

P Password

Quality Control Manager, 8 PNR

adding QC Received From element, 80 checking with RuleChecker, 92 correcting, 94 displaying element details, 113 placing on queue from RuleChecker, 97 rechecking, 95, 96

PNR RuleFile/Set association, 81 PNR/TST elements list, 117 Point of Sale tab in Administrator, 69, 74 Point of sale triggering commands, 69 Point-of-sale (POS) mode, 91 Pricing commands, 69 Printing

in Rule Editor, 11 Prompt to associate RuleFile/Set, 77 Prompt when RuleFile/Set is missing, 77 Publishing

RuleLibrary, 53, 55, 56, 57

Q QC Rules Repository, 3 Quality Control Manager

launching, 7 overview, 7 password, 8

Queuing a PNR from RuleChecker, 97

R RC element

adding to PNR, 81 adding to profile, 82

Rechecking a PNR, 95, 96 Recycle Bin tab, 9 Regular expression, 45 Regular expressions, 44 Replication

RuleChecker settings, 66 rules, 57

Restoring

RuleFile/Set, 11 Restricted access, 61 Rule

activating, 20 best practices, 17 creating, 18 creation workflow, 13 definition, 14 overview of elements, 15 publishing workflow, 51 replication, 57

Rule action creating, 29 definition, 29 options, 30

Rule Editor launching, 10 overview, 9

Rule message creating, 27 definition, 27 options, 28

Rule Messages, 93 display, 93 display options, 101

RuleChecker bypassing, 96 checking PNR, 92 correcting PNR, 94 defining prohibited transactions, 75, 76 display options, 100 displaying all rule messages, 101 displaying associated RuleFiles/Sets, 98 displaying splash screen, 101 displaying success acknowledgement, 101 forcing Quality Control replication, 57 manually associating RuleFiles/Sets, 98 on-demand (OND) mode, 91 overview, 89 placing a PNR on queue, 97 point-of-sale (POS) mode, 91 running in background, 101 toolbar, 94 transaction log, 99 troubleshooting log, 100

RuleChecker bypass configuration, 66, 67

RuleChecker Bypass tab in Administrator, 66, 67 RuleChecker configuration

access, 61 copying, 64 definition, 61 inheriting, 62, 63 replication, 66 switching, 62

RuleChecker display in background, 101

RuleChecker Execution tab in Administrator, 77, 78, 79, 80 RuleChecker settings

deployment workflow, 65 RuleFile

activating, 20 associating to a RuleSet, 50 copying, 10 creating, 17


170 Edition 4.0

definition, 14 deleting, 11 deleting permanently, 11 exporting, 110 importing, 109 modifying, 11 printing, 11 replication, 57 restoring, 11 saving, 11 testing in Rule Editor, 46 testing in Selling Platform, 47

RuleFile/Set association to PNRs, 81 RuleFiles/Sets tab in Administrator, 83, 85 RuleLibrary

adding RuleFiles/Sets, 54 copying, 10 creating, 54 deactivating, 57 definition, 52 deleting permanently, 11 modifying, 11 printing, 11 publishing, 53, 57 publishing from Rule Editor, 55 publishing in Administrator, 56 publishing workflow, 51 replication, 57 saving, 11 selecting in Administrator, 56

RuleSet activating, 49 associating RuleFiles, 50 copying, 10 creating, 50 definition, 49 deleting, 11 deleting permanently, 11 details, 50 modifying, 11 printing, 11 replication, 57 restoring, 11 saving, 11

RX element adding to profile, 82

S Saving

in Rule Editor, 11 Send Transactions field, 93 Setting RuleFiles/Sets when another office is responsible for the PNR, 78 Showing informative messages, 74 Special expression, 45 Special expressions, 44

example, 40

Starting Administrator, 60 Quality Control Manager, 7 Rule Editor, 10 RuleChecker in OND mode, 91 RuleChecker in POS mode, 91

Success acknowledgement display, 101

T Testing RuleFiles

in Rule Editor, 46 in Selling Platform, 47

Ticketing commands, 69 Toolbar

RuleChecker, 94 Transaction log, 99 Transactions from RuleChecker, 93 Triggering command family

definition, 69 Triggering commands

defining, 70, 71 definition, 69 linking to rule, 71, 72

Troubleshooting log, 100 TST

displaying element details, 113

V Variable

applying functions, 37, 38, 40 creating, 34 definition, 33 example, 35 initialising, 34 naming conventions, 33

Variable condition comparing variables, 42 definition, 42 example, 43 options, 42

Viewing PNR/TST details, 113

W Where statement

creating, 23 definition, 23 options, 25

Workflow creating rules, 13 deploying Amadeus Quality Control, 5 deploying RuleChecker configurations, 65 publishing rules in RuleLibraries, 51

Amadeus Quality · PDF file · 2012-08-03Edition 4.0 For Amadeus Quality Control...

Documents

Transcript of Amadeus Quality · PDF file · 2012-08-03Edition 4.0 For Amadeus Quality Control...