Revenue Integrity TTY Reject Process

An Overview

Revision 1.0 Tim Stuart 14 February 2009

 2009, Sabre Inc. All rights reserved. This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Inc. is strictly prohibited. Sabre and the Sabre logo design are trademarks and/or service marks of an affiliate of Sabre Inc. All other trademarks, service marks, and trade names are owned by their respective companies.

Sabre Inc. Confidential/All Rights Reserved

Introduction

When the Sabre host fails to automatically take action on an incoming TTY message, it will be placed on a TTY Reject Queue The Revenue Integrity TTY Reject Process works the messages on the TTY Reject Queue(s) with a view to taking the necessary action on as many of them as possible. The TTY Reject Process differs from the eight original RI processes in two key ways: It comes pre-configured with a default process. This means that, as soon as it is activated, it is equipped to handle the most common actions without the user having to do anything Should the user need to overrule the default process the new specific rules and actions are available.

Sabre Inc. Confidential/All Rights Reserved

2 The Process Flow

The next TTY message is read from the Reject Queue. The process will try and find the host PNR that the message relates to. If necessary, the process will create a new PNR on the host using the data from the TTY message. Any user-configured Segment Action Rules will be evaluated against the segment lines in the TTY message. The associated action will be carried out for those lines that match a userconfigured rule. Any user-configured SSR/OSI Action Rules will be evaluated against the OSI and SSR lines in the TTY message. The associated action will be carried out for those lines that match a userconfigured rule. TTY message lines that match no user-configured rule will use the default process. TTY messages that cannot be processed at all will be placed on a user-defined error queue.

Sabre Inc. Confidential/All Rights Reserved

3 The Default Process Segment Handling

Out of the box the TTY Reject process has been configured with a default process to handle the most common action requests directed by the incoming TTY messages. This default process is invisible to the user, residing in the background of the application. The default process for segment handling is based entirely on the Status Code of the segment in the TTY message. Each of these status codes implies an required action to be taken on the PNR The default process compares the status code of the segment in the TTY message with the status code of the segment in the PNR and aims to keep the host PNR in sync. The default process is quite large and will require a small amount of study time to understand. The TTY Reject Process user guide contains a full description of the default process. However, we will look at a couple of examples here.

Sabre Inc. Confidential/All Rights Reserved

3.1 Default Segment handling example 1

This example applies to host bookings that is, the TTY has come from another GDS or Airline system informing us of a change to a host booking.
If Segment Status Code = UN If Status of matching PNR segment = UN No Action If Status of matching PNR segment = HK or SC or RR Modify Status of PNR Segment that matches TTY Segment ActionCode:UN If Status of matching PNR segment = Other FlagError If No Matching PNR found Or No matching segment in PNR FlagError

Sabre Inc. Confidential/All Rights Reserved

3.2 Default Segment Handling example 2

This is another example that applies to host bookings. If Segment Status Code = TK If Status of matching PNR segment = TK No Action If Status of matching PNR segment = UN Sell TTY Segment in the PNR ActionCode:TK If Status of matching PNR segment = HK or SC or RR Modify Status of PNR Segment that matches TTY Segment ActionCode:UN Sell TTY Segment in the PNR ActionCode:TK If Status of matching PNR segment = Other FlagError If No matching segment in PNR Sell TTY Segment in the PNR ActionCode:TK If No Matching PNR found FlagError

Sabre Inc. Confidential/All Rights Reserved

4 The Default Process SSR/OSI handling

The default process for handling SSR and OSI lines from the TTY Message is very straightforward and can be summarised as follows:
If Message Type = GEN FAX SSR If SSR Status Code = HK, NN, DK, SS Add PNR SSR that matches TTY SSR If SSR StatusCode = XX Cancel PNR SSR that matches TTY SSR Else If Message Type = GEN FAX OSI Add PNR OSI that matches TTY OSI

Note that when Adding an SSR to a PNR, there are various within the host system that apply, (such as the fact that a passenger may only have one meal SSR related to them per segment). All these various rules are handled by the process and are included in the user guide purely as a reference. It is not really necessary to read them all unless you have a LOT of spare time on your hands!

Sabre Inc. Confidential/All Rights Reserved

5 The Segment Action Rule

If you wish to over-rule the default process in any particular circumstance or if you wish to process a segment based on anything other than the segment status code, then you will need to build a Segment Action Rule. All the usual Revenue Integrity parameters are available and this rule is built in the same way as rules throughout the Revenue Integrity application. There are some additional parameters available and they are listed here:
Is Informational Segment Status of matching PNR segment True if the segment in the TTY is purely for informational purposes, such as connection information. Specifies the status code of the segment in the PNR that matches the segment in the TTY message

Is Matching PNR Found True if a PNR has been found in the Sabre system that matches the record locator of the TTY and which matches the passenger names in the TTY Is Matching Segment in PNR Indicates whether or not a segment in the PNR exists which matches the TTY segment in Carrier Code, Flight Number, Class and Departure Date and which has a status code that matches the status code(s) specified True if the history of the PNR shows that the most recent operation on the segment that matched the TTY segment occurred later than when the TTY was created. Segments are matched by Carrier Code, Flight Number, Class and Departure Date

Matching PNR Segment modified after TTY sent

Sabre Inc. Confidential/All Rights Reserved

6 SSR/OSI Action Rule

This rule makes use of the existing Revenue Integrity functionality to target: Message Type SSR Message Code SSR Status Code SSR/OSI Carrier Code Message Text (using regular expression matching)

Sabre Inc. Confidential/All Rights Reserved

10

7 Actions
The Actions screen in the TTY Reject Process has a slightly different look and feel to those in the original Revenue Integrity processes. The Actions here are very specific to TTY message handling and are as follows: No Action This is the Action Type shown above. It simply means that no action will be taken on the TTY element being processed. Flag Error When this Action Type is invoked, the TTY message will be processed no further and the message will be placed on the specified Error Queue. Queue TTY

This Action Type is used to place the TTY Message on a specified Queue. When this option is selected, the window will change to the boxes you can use to enter the City Code, Queue Number and Prefatory used to Queue Place the message. Queue PNR When a TTY Message is processed, we have seen how the process will either retrieve the matching PNR or create a new PNR. This
Sabre Inc. Confidential/All Rights Reserved 11

Action Type is used to place the PNR on a specified Queue. When this option is selected, the window will change to the boxes you can use to enter the City Code, Queue Number and Prefatory used to Queue Place the message. Send Email

This Action Type can be used to send an email. The Distribution List box equates to the email To field and can be used to enter the email address of the intended recipient. Multiple addresses can be entered if separated by a semi-colon. Additional recipients can be added to the CC List and BCC List fields. Finally, there are Subject and Message Text fields. Send TTY NRL The Sabre transaction TTYNRL will be made in the AAA of the loaded PNR. This will result in a TRL message being sent to the booking source specified in the PNR if an RR agreement is in place with the booking source. The Send TTY NRL action will only be performed at the very end of the processing on the PNR and it will only be performed if there were no modifications made to any of the other segments in the PNR. This
Sabre Inc. Confidential/All Rights Reserved 12

means that the TRL message will not be required if other messages are generated back to the booking source. Sell TTY Segment into PNR

This Action Type is used to long sell the TTY segment into the Sabre PNR. With this option selected, the Segment Action Code box becomes visible. Here you should enter the 2-character action code that will be used when selling the segment into the PNR. Cancel PNR Segment that matches TTY Segment When this Action Type is used, the segment in the PNR that matches the segment in the TTY Message will be cancelled with an X1 type transaction. Modify Status of PNR Segment than matches TTY Segment

Sabre Inc. Confidential/All Rights Reserved

13

When this Action Type is invoked, the matching PNR segment will have its status code changed to the action code specified in the Segment Action Code box. Add PNR SSR that matches TTY SSR

Using this Action Type, the TTY SSR will be attempted to be added into the PNR, maintaining any segment or passenger relate elements that may be included. Any values you enter in the Code, Action Code, Carrier Code and Message fields will be used in place of the corresponding values in the original TTY SSR. Add PNR OSI that matches TTY OSI

Sabre Inc. Confidential/All Rights Reserved

14

Using the Action Type, the TTY OSI will be attempted to be added into the PNR. Any values you enter in the Carrier Code and Message fields will be used in place of the corresponding values in the original TTY OSI. Cancel PNR SSR that matches TTY SSR When this Action Type is executed, the PNR SSR that matches the TTY SSR will be attempted to be cancelled from the PNR. Add SSR to PNR

Sabre Inc. Confidential/All Rights Reserved

15

This Action Type can be used to add a new GEN FAX SSR to the PNR, regardless of whether or not there is a matching SSR in the TTY Message. When using this Action Type, you will need to provide the SSR Code, Status Code, Carrier Code and Message Text in the boxes provided. Add OSI to PNR

This Action Type can be used to add a new GEN FAX OSI to the PNR, regardless of whether or not there is a matching OSI in the TTY Message. When using this Action Type, you will need to provide the Carrier Code and Message Text in the boxes provided. Add Remark to PNR

Sabre Inc. Confidential/All Rights Reserved

16

This Action Type is used to add a Remark to the PNR. Enter the Message Text for the Remark in the Text field. Add ApFax SSR to PNR This Action Type can be used to add a new AP FAX SSR to the PNR. When using this Action Type, you will need to provide the SSR Code, Status Code, Carrier Code and Message Text in the boxes provided. Add ApFax OSI to PNR This Action Type can be used to add a new AP FAX OSI to the PNR. When using this Action Type, you will need to provide the Carrier Code and Message Text in the boxes provided. Skip and Queue Using this Action Type causes processing on the TTY Message to be skipped and then places the Message on a Queue as specified in the City Code, Queue Number and Prefatory boxes. It is important to note that this skip action takes priority over all other actions. This means that if just one Segment or SSR/OSI element in the TTY uses this Skip and Queue Action Type, then the whole TTY Message will be skipped and not processed at all. Skip and Remove from Queue This Action Type means the whole message will be skipped, (as in Skip and Queue above). The Message will also be removed from the TTY Reject Queue and no further processing will be performed on it.

Sabre Inc. Confidential/All Rights Reserved

17