Settings: Ticket Modifier Tables

Worldspan: Not available to Worldspan users.

Ticket Modifiers were introduced in the 17.2.2 release in May 2017.

Ticket Modifiers are created and maintained by agency administrators. To access the Ticket Modifier tables, click the Settings tab, then select Ticket Modifier Tables. Click Configure to modify an existing ticket modifier table or to import/export a table.

• The Ticket Modifier Unit update logic is the first process to take place during Advanced Robotic Ticketing. The application of the current commission and form of payment logic during Advanced Robotic Ticketing occurs after the ticket modifiers update.

• All the ticket modifiers are updated as part of the associated filed fares and not as part of the ticketing command.

• The ticket modifiers in the configuration table will be combined and applied on to the filed fare if the conditions in the ticket modifier table match that of the PNR and filed fare. For example: if there is a commission of 2 with a FOP of cheque and a tour code of “12345”, the Ticket Modifier Units of the filed fare will be updated as Ticket Modifier Units 1/Z2/FCK/TC12345. If the Ticket Modifier Unit values are incorrect or non-acceptable as per the host specifications, the PNR will be rejected during robotic ticketing.

• The post ticketing commands are static remarks and do not incorporate extractions of values from the booking file. The post ticketing command runs the command provided in the configuration table every time if the ticket modifier row is selected, regardless of whether the notepad, DI, SI, SSR remarks, or any other value mentioned in the command exists in the booking file or not.

• When the override option is selected for a ticketing modifier, the ticket modifier that exists in the booking file will be overridden. Some NTD (Net ticket data) file fares have values (Commission, BT, IT, Value Code/Net) that cannot be overridden due to host restrictions. In these cases, these restricted values are skipped. Endorsement, Tour code, Deal code, and FOP will be overridden in the filed fare containing NTD if the override option is selected. If NTD data exists, then airline would typically have Endorsement and Tour Code. In this case the value from the table will not be picked up. However, if any of the values for Endorsement or Tour Code are missing in the filed fare, the values from the table must be used.

This topic contains the following sections:

• How Ticketing Modifiers Are Applied

• Add a Ticket Modifier Table

• Ticket Modifier Examples

• Export/Import Ticket Modifier Tables

How Ticket Modifiers Are Applied

When Queue Control Console is comparing the values in a PNR/Filed Fare with the criteria in the Ticketing Modifier table, if multiple rows within the Ticketing Modifier table match on the first priority, Queue Control Console proceeds to the next criteria to look for a match. Refer to the Examples below for illustrations on how Ticketing Modifiers are applied.

Concrete values (e.g., Carrier Code = VA) take precedence over a value of Any.

Add a Ticket Modifier Table

1. Click the Settings tab then select Ticket Modifier Tables.

2. In the Ticket Modifier table list, click Add new item.

3. Enter a name for the ticket modifier table.

4. Click Update.

5. Click Configure to add ticket modifiers.

6. From the Ticket Modifier detail screen, click the New Ticket Modifier button.

7. Select the API type.

8. Complete the Criteria section based on your ticket modifier requirements. Expand a criteria for more information.

   Account in Document Itinerary

   Values: Alpha-numeric value, blank (empty), or select Any

   The Account in Document Itinerary is first in the order of priority for selection of the ticket modifier row.

   • For Travelport Galileo, it is the entire DI.AC PNR value (retrieved by *DI).

     

   • For Travelport Apollo, it is the entire T-CA value (retrieved by *PT).

   • If there is no row with a blank value, the configuration for Any applies.
   • If value is Any, it refers to everything unless there is another value (blank or other).
   Customer ID

   Values: Alpha-numeric value, blank (empty), or select Any

   The Customer ID is second in priority for selection.

   • For Travelport Galileo, Customer ID is the CI. PNR value (retrieved by *CI).

     

   • For Travelport Apollo, it is the C- value (retrieved by *PC).

   Airline Carrier

   Values: Alpha-numeric value or select Any

   The airline is third in priority for selection.

   Carrier identifies the plating carrier as per the filed fare.

   Travelport Galileo:

   

   Account Code in Filed Fare

   Values: Alpha-numeric value, blank (empty), or select Any

   The Account Code is next in priority for selection.

   • If there is no row with a blank value, the configuration for Any applies.
   • If value is Any, it refers to everything unless there is another value (blank or other) at which time Any refers to anything else other than what is specified.

   Travelport Galileo:

   

   Passenger Type Code

   Values: A valid PTC or Any. Cannot be blank.

   The Passenger Type Code is next in priority for selection.

   Select from the list of standard PTC codes or enter a code.

   If there are multiple passengers in the filed fare, the Ticket Modifier Units for the filed fare will get updated appropriate ticket modifier values if and only if the Ticket Modifier Unit values exist for both and are the same for both. It is not possible to update the Ticket Modifier Unit lines for each passenger separately (except the FOP modifier) as the Ticket Modifier Unit modifiers (endorsements, tour codes, etc.) apply for all passengers and cannot be restricted to each passenger.

   Note that PTC code selection is only based on the filed fare. If the PTC code is not present in the filed fare, it is assumed as Adult.

   Travelport Galileo:

   

   Effective/Expiry Date

   For the row to be active, the current date must be between the effective and expiry dates.

9. In the Value section, enter the value of the ticket modifier that will be updated based on the criteria entered above. The ticket modifiers available depend on the API type selected above.

   Override option: When the override option is selected for a ticketing modifier, the ticket modifier that exists in the booking file will be overridden. Some NTD (Net ticket data) file fares have values (Commission, BT, IT, Value Code/Net) that cannot be overridden due to host restrictions. In these cases, these restricted values are skipped. Endorsement, Tour code, Deal code, and FOP will be overridden in the filed fare containing NTD if the override option is selected. If NTD data exists, then airline would typically have Endorsement and Tour Code. In this case the value from the table will not be picked up. However, if any of the values for Endorsement or Tour Code are missing in the filed fare, the values from the table must be used.

   Note: If Override is not selected, existing values will remain in the PNR/filed fare. If you are not sure whether the TMU modifier exists in the PNR but you want the screen values updated, it is recommended that you select the Override option.

   • Form of Payment - Free text. Credit cards are not supported at this time.

   • Commission - Enter a numerical percentage.

   • Tour Code

   • Bulk Tour - Enter the value for bulk tour. For Travelport Galileo, the user must input BT or BST*PC. This field must be blank if Inclusive Tour contains data.

   • Inclusive Tour - Enter the value for inclusive tour. For Travelport Galileo, the user must input IT or IT*PC.
     Note: If this ticket modifier has a value, then Bulk tour must not contain data.

   • Deal or Car Code

   • Value Code or Net Fare

   • Endorsement - Multiple endorsement values can be concatenated by a semicolon (;).  

   • Post Ticketing Command - Enter the actual host command. Multiple values are allowed and can be separated by a semicolon (;).
     Important: Though not part of the ticketing modifiers, this field gives the user the flexibility to add any post ticketing entry command of their choice. Note that override option is not present for this field and hence the command listed here will be executed every time if the ticket modifier row is selected.

10. Click Create.

Examples

The following examples illustrate the logic ticket modifier selection.

 

Export/Import Ticket Modifiers

To export or import a Ticket Modifier,

1. Click the Settings tab then select Ticket Modifier Tables.

2. Click Configure for the Ticket Modifier that you want to export/import.

3. Click the Export or Import button.

Important: When importing a new Ticket Modifier table, the imported file must be formatted exactly as the files are for export.