Rapid Reprice Galileo User Guide AUNZ June 2010 - … · Travelport GDS is also able to process...

Travelport Rapid Reprice - Galileo User Guide v5.0 2010

Travelport Rapid Reprice 1

Travelport Rapid Reprice –

Galileo User Guide

Travelport Rapid Reprice – Galileo User Guide v5.0 May 2010

2 Travelport Rapid Reprice

THE INFORMATION CONTAINED IN THIS DOCUMENT IS CONFIDENTIAL AND

PROPRIETARY TO TRAVELPORT

Copyright

Copyright © 2010 Travelport and/or its subsidiaries. All rights reserved.

Travelport provides this document for information purposes only and does not promise that the information

contained in this document is accurate, current or complete. This document is subject to change without

notice.. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form

or any means electronic or mechanical, including photocopying and recording for any purpose other than the

licensee’s personal use without the prior written permission of Travelport and/or its subsidiaries.

Trademarks

Travelport and/or its subsidiaries may have registered or unregistered patents or pending patent applications,

trademarks copyright, or other intellectual property rights in respect of the subject matter of this document.

The furnishing of this document does not confer any right or licence to or in respect of these patents,

trademarks, copyright, or other intellectual property rights.

All other companies and product names are trademarks or registered trademarks of their respective holders.

Travelport Rapid Reprice - Galileo User Guide v5.0 2010


Contents

1. Overview ...................................................................................................................................... 4

2. In / Out of Scope for Reprice Transactions .................................................................................. 5 2.1 In Scope ............................................................................................................................... 5

2.2 Out-of-Scope ........................................................................................................................ 5

3. Accessing Rapid Reprice .............................................................................................................. 6

4. Validate the ETKT ....................................................................................................................... 7

5. Validate the Itinerary .................................................................................................................... 9

6. Selecting the Ticket Numbers .................................................................................................... 11

7. Divided Booking Files ................................................................................................................ 13

8. Select the Pricing Method .......................................................................................................... 13

9. Pricing Options ........................................................................................................................... 16

10. Passenger Type Option ............................................................................................................. 17

11. Calculated Fares ....................................................................................................................... 18

12. Complete the Reprice Request ................................................................................................. 19

13. Rapid Reprice Responses ......................................................................................................... 19

14. Results Screen .......................................................................................................................... 20 14.1 Results Screen – Rapid Reprice Results .......................................................................... 21

14.2 Results Screen – Manual Fare Build Data - FBC............................................................. 23

14.3 Complete Manual Fare Build Screen .............................................................................. 26

14.4 Results Screen – Manual Exchange Screen Data - TMU ............................................... 26

15. Examples of Final Results Screen Layout ................................................................................ 30

15.1 Unused Ticket. ................................................................................................................. 30 15.2 Partially Used Ticket. ....................................................................................................... 31

16. Storing Rapid Reprice Results .................................................................................................. 32

17. Fare Guarantee for Reissued Tickets ........................................................................................ 33

Appendix 1 - Australia ................................................................................................................... 34



1. Overview

This document will provide a complete overview and user guide for Travelport Rapid Reprice on

Galileo.

A desktop Add-on must be installed on the agency desktop. The functionality is available for agency

users who have installed Galileo Desktop 2 (and above).

Note – Effective August 2009 – to enable Travelport Rapid Reprice functionality for all Galileo agency

users a desktop add-on will be made available for agency customers working with Galileo Desktop 1

and Focalpoint3.5.

Rapid Reprice functionality is dependent upon airlines filing of ATPCO Category 31 ‘voluntary

reissues’ data. Travelport Product Management and Airline Account Managers continue to work

with airlines on a global basis to ensure content in Rapid Reprice continues to increase to ensure as

complete participation and usability as possible.

Travelport GDS is also able to process SITA Category 31 ‘voluntary reissues’ data. The ability to

process this data ensures that all airlines have the ability to participate in Rapid Reprice.

Rapid Reprice will automatically calculate the new price for the ‘voluntary’ (Passenger requested)

reissue of an Electronic Ticket on a participating carrier. Rapid Reprice uses historical data, current

fares, and rules to re-price a revised itinerary. It will display results, including any additional

collection (fare and taxes), and change or penalty fee amounts, to assist the agent with completing

the manual pricing and exchange process.

The number of carriers who have agreed to file Category 31 data and are therefore participants in

the Travelport Rapid Reprice Product continues to increase. Please refer to your Account Manager

or ASK Travelport for the latest list of airline participants.

Rapid Reprice is able to process reissue transactions for multiple carrier itineraries and for itineraries

where a marketing code share is on the itinerary (i.e. QF operated aircraft with BA flight number).

For Booking Files with multiple passengers a separate Reprice transaction is required for each

passenger.

Travelport Rapid Reprice - Galileo User Guide v5.0 May 2010


2. In / Out of Scope for Reprice Transactions

2.1 In Scope

• Booking Files that have been created on the Galileo Host system

• Focalpoint 3.5, Galileo Desktop 1 & 2.0, or higher must be installed on the Agency

workstation.

• Features supported by Rapid Reprice, include:

o All fares (public and private) filed via ATPCO and SITA that include Category 31

(Voluntary Changes) data.

o The redistribution of airline private fares when the agencies have a selective access

agreement.

o Applies only to electronic tickets.

o The user must be able to retrieve the ETR (Electronic Ticket Record).

o Includes IT/BT tickets as long as the ETKT is associated to the active booking file.

o Applies to Galileo agency users who use BSP reporting.

2.2 Out-of-Scope

• Functionality not supported by Rapid Reprice, includes:

o Agency Private Fares (including those originally filed via ATPCO and modified

through APFs)

o Carriers who file fares through data supplier SITA (please also refer to Overview in

this document).

o Net remit tickets

o G/ group booking files



3. Accessing Rapid Reprice

To install Rapid Reprice refer to the Travelport Rapid Reprice – Galileo installation guide.

Access in Focalpoint

Rapid Reprice is accessible from Focalpoint within Galileo Desktop. Select the ‘’Companions’’ drop

down menu, select Rapid Reprice.

Access in Viewpoint

Rapid Reprice is accessible from Viewpoint within Galileo Desktop. Select the ‘’Issue Docs’’ drop

down menu, select Rapid Reprice.



4. Validate the ETKT

Rapid Reprice Exchange processing requires that a valid ETKT exists. The ETKT must be retrievable

from the agency desktop.

The ETKT can either be:

• Associated to the currently retrieved Booking File (where the itinerary will be changed and

the new flights booked).

• Or, not associated to the currently retrieved Booking File (where a totally new itinerary will

be booked on a new Booking File).

1. Check to see if there are one or more ETKTs associated to the active Booking File. (*HTE)

When the BOOKING FILE is displayed, the Electronic Ticket Record (ETR) can be accessed with

the following format:

• *HTE

• If more than one ETKT is associated to the Booking File, a list will be displayed, for example:

ELECTRONIC TICKET LIST BY *HTE

NAME TICKET NUMBER

>*TE001 CARVILL/FRANCESM 1764614229504

>*TE002 CARVILL/IAINMR 1764614229503

>*TE003 CARVILL/SARAHMIS 1764614229505

END OF LIST

• The individual ETR is displayed from the list by selecting it using the *TE00x

format.

• If ETKT(s) are present, validate that the ETKT is eligible for exchange.

• Coupons must have a status of OPEN, ARPT, or UNVL.

TKT: 125 4665 884940 NAME: JONES/TIMOTHYMR

CC: VIXXXXXXXXXXXXXXX9 FF: 13846457

ISSUED: 11DEC07 FOP:VIXXXXXXXXXXXXXXXX-XX6409

PSEUDO: 01AO PLATING CARRIER: BA ISO: GB IATA: 91295691

USE CR FLT CLS DATE BRDOFF TIME ST F/B FARE CPN

USED BA 2901 I 22JAN MANLGW 0635 OK ILEUME 1

USED BA 6858 I 22JAN LGWSSH 0915 OK ILEUME 2

ARPT BA 6859 D 26JAN SSHLGW 1745 OK DLEUME 3

OPEN BA 2904 D 27JAN LGWMAN 0820 OK DLEUME 4

FARE GBP 475.00 TAX 80.00 GB TAX 22.70 UB TAX 137.70 XT

TOTAL GBP 715.40

NONREF/EGCGT

• The ETKT must not have been reissued previously. There will be an indicator

at the end of the ETKT display that will tell if the ticket has been exchanged

in an earlier transaction. Note the verbiage EXCHANGED FOR in the screen

shot below.

• Flight Coupons can only be honoured in Sequence. The OPEN coupon

cannot occur prior to a USED Coupon to be eligible for reissue



TKT: 125 9900 048276 NAME: EXCHANGE/RRMR

ISSUED: 03JAN08 FOP:CHECK/CHECK

PSEUDO: 0X8Q PLATING CARRIER: BA ISO: GB IATA: 99999992

USE CR FLT CLS DATE BRDOFF TIME ST F/B FARE CPN

OPEN BA 306 Y 17MAR LHRCDG 0925 OK YFLBA 1

OPEN BA 305 Y 22MAR CDGLHR 0925 OK YFLBA 2

FARE GBP 340.00 TAX 34.80 XT TAX 9.00 FR TAX 8.40 XT

TOTAL GBP 11.90A

LON BA PAR 343.23YFLBA BA LON 343.23YFLBA NUC686.46

END ROE0.495294 XT GBP0.70IZ GBP7.70QX XT PD10.00GB

PD14.30UB PD10.50YQ

EXCHANGED FOR: 1259900048275

ORIGINAL ISSUE: 1259900048275LON03JAN0899999992

RLOC 1G SF448M 1A 4CQIH5



5. Validate the Itinerary

Once it has been determined that the ticket is eligible for a Rapid Reprice Exchange changes may be

made to the existing itinerary or book a new itinerary for the passenger. It is not advisable to cancel

the existing flights – the passenger may decide not to change the booking.

Once the new flights have been booked, launch the Rapid Reprice application as described above

(section 3).

When the Rapid Reprice application is launched, it is important to check that the revised itinerary is

eligible for Rapid Reprice. If the criteria are not met error messages will be displayed.

ITINERARY CONTAINS DUPLICATE AIR

SEGMENTS-SELECT SEGMENT FOR PRICING

If itinerary includes more than one segment with the

same flight on the same date, agent must select one or

the other.

INVALID ITIN If the itinerary includes no Air Segments it is not valid.

CARRIER NOT AN AUTOMATED REISSUE

PARTICIPANT - PROCESS MANUALLY

Rapid Reprice was initiated on a carrier that is not a

Rapid Reprice participant



The Rapid Reprice Exchange Screen is displayed below

Select or de-select segments to be repriced by clicking on the box to the left of the segment in the

Rapid Reprice Exchange screen. In the example below Rapid Reprice will base its calculations on the

flights where the check boxes (green ticks) are selected.

Any flown segments that have not yet dropped from the Booking File will appear in this window

along with the unflown segments. Any flown segments should be de-selected.



6. Selecting the Ticket Numbers

If a valid ETKT exists for the Booking File, that ticket number will appear in the ticket number

window of the “Rapid Reprice Exchange” screen.

If multiple valid ETKTs exist for the Booking File, the screen will display all of the valid ticket numbers

that are eligible for exchange in a drop-down list. Click on the drop-down list to make a selection.

When multiple passengers are included in the Booking File, the drop-down list screen will display the

passenger name that is related to each ticket number:

If there are no valid ETKTs associated to the active Booking File, the ticket number window will be

blank. A valid ETKT number must be entered in the ticket number window of the “Rapid Reprice

Exchange” screen.

• Note: If the ticket is a conjunction ticket, only the first ticket number is required.

• No check digit is required

• It is possible to over-type a ticket number that appears in the window with another

ticket number if necessary.

• When the ETKT number is entered manually, it must also be checked to determine if

the ETKT is valid for exchange. The ETR can be displayed with the following format:

o *TE/nnnnnnnnnnnnn

• The following alerts will be displayed for manually entered ETKT numbers:

o When an Electronic Ticket number with less or more than 13 numeric

characters (no check digit required) is manually entered into the Ticket

Number drop-down, an error response dialog box is returned when the

agent clicks “Continue”.



o This message will also be displayed upon clicking “continue” and the ticket

number window has been left blank.

o When an Electronic Ticket number that is manually entered into the Ticket

Number drop-down is not found or is not valid or eligible for exchange, the

following error response dialog boxes will be returned upon clicking

“Continue”.

Or



7. Divided Booking Files

When a Booking File is divided after the original tickets have been issued, the Rapid Reprice Request

screen will not display the ticket numbers. The ticket number for the passenger must be manually

entered. For Example:

The ticket number can be displayed from the Booking File and Copied, then Pasted into the Ticket

Number cell:

Divide and end the record first, then display the tickets with the *HTE input. All tickets associated to

the original Booking File will be displayed. Highlight the ticket number for the applicable passenger

to be repriced, then copy and paste into the Ticket Number box:

ELECTRONIC TICKET LIST BY *HTE

NAME TICKET NUMBER

>*TE001∑ APPLE/ADAM 1252585658384

>*TE002∑ BROWN/BETTU 1252585658385

>*TE003∑ CHAN/CHARLIE 1252585658386

END OF LIST

Important Note

When a Booking File is divided, the Filed Fares are cancelled, both on the new and the original

record. As Rapid Reprice reads the original fare information from the Filed Fare for BT and IT type

tickets, BT and IT type tickets will not be eligible for Rapid Reprice if the Booking file has been

divided.

8. Select the Pricing Method



Three options are available for pricing. The selection is made with the use of a radio button.

• ‘Price as Best Buy’. (FQBB) lowest available restricted fare. This option is the default. The

reprice response will advise whether or not segments need to be rebooked in a different

booking code.

• ‘Price as booked’ (FQ) booked class of service. This option will quote the reprice exactly as the

itinerary is booked. There must be a valid fare for the booking codes.

• ‘Price with no penalty’ (FQBBPE0) lowest available unrestricted fare. The reprice will be

calculated at the lowest unrestricted fare for the booked itinerary. The reprice response will

indicate if flight segments need to be rebooked in a different booking code.

Re-prices at lowest available restricted fare in the booked cabin

Re-prices in booked class of service. I.e. Booked in ‘B’ class reprice in ‘B’.

Re-prices at lowest available unrestricted fare



The pricing method explanation is displayed in the Status Bar. (see bottom of screen below)



9. Pricing Options

There are 3 pricing option available -

• Public Fares – Only Public Fares will be considered in the reprice transaction.

• Public and Airline Private Fares –Public Fares and Airline Private Fares filed for use by the

requesting Psuedo City Code (PCC )will be considered in the reprice transaction.

• Airline Private Fares – Only Airline Private Fares filed for use by the requesting PCC will be

considered in the reprice transaction.

Airline Private Fares (Private Fares filed by an airline via ATPCO) have ‘security’ associated to them,

this is based on the users Pseudo City Code, Account Code, IATA number and/or country of origin.

The Pseudo City Code and Private Fares Account Code should be entered into the box as displayed

below. The IATA number and city pair are included in the Electronic Ticket Record (ETR) and will be

sent with the reprice request.



10. Passenger Type Option When the selected passenger and ETKT is associated to an active Booking File and the Filed Fare

includes the ticket number, the Passenger Description Box will be pre-populated with the Passenger

Type Code (PTC )from the original fare quote. For Example:

If the ETKT is not associated, the applicable PTC that was used to price the original ticket if the

passenger type is not ADT (default) must be added. Click on the Passenger Description drop-down

list to choose a Passenger Type Code (PTC), or type a Passenger Type Code into the text box.



Upon entering a PTC that is other than ADT, the following dialog box will appear on clicking the

"Continue" button.

11. Calculated Fares Reprice results can be discounted with airline agreement by the following means:

� Discount amount before tax (FA)

� Discount with percent (RP)

� Increase fare by flat amount (IF)



12. Complete the Reprice Request

Click “continue” or “cancel” to continue or discontinue the process

The desktop application will collect the original issue data for each passenger from the ETR, including

flown segment data and the new itinerary data. The reprice request is then sent to the Rapid

Reprice engine.

IT and BT Tickets

For reprice transactions for IT and BT tickets Fare data from the ‘Filed Fare’ in the active booking file

is gathered and sent to the Rapid Reprice engine. The Rapid Reprice engine will usually only

consider net fare levels, however, in instances where an airline has filed sell levels only these will be

considered. Rapid Reprice should not be used to process reissue transactions where an Airline

Private Fare has been amended via Agency Private Fares.

Note – When using Rapid Reprice for the reprice of IT/BT tickets it is important to note that the

original fare information is taken from the Filed Fare within the booking file, the *HTE entry does not

show the original fare value. Users are therefore advised to initiate the Rapid Reprice request prior

to End Transaction. End Transaction prior to initiating Rapid Reprice will force manual processing.

13. Rapid Reprice Responses

The response received from Rapid Reprice may include an Error Message or a Result Reason, instead

of, or in addition to the pricing, change fee and ticketing information that will be displayed in the

final Results Screen.

If Rapid Reprice is unable to process the request, the data included in the “Error Text” will be

displayed in a message box.

Rapid Reprice may also return a qualifying message, but will still provide the new pricing, change fee

information, and ticketing entries. Clicking “OK” will display the final results screen.



14. Results Screen

Assuming errors have not been returned the Results Screen below is returned. The Results Screen

has been divided into 3 sections

• Rapid Reprice Results

• Manual Fare Build Data – FBC

• Manual Exchange Screen Data – TMU



14.1 Results Screen – Rapid Reprice Results

The data displayed in this section is for information purposes only and will be displayed first. This

information will assist in deciding whether or not to proceed with the exchange transaction. This

section also confirms the request by repeating the PTC and Pricing command as well as whether or

not any booking codes need to be changed for the quoted fare, and whether there is an Additional

Collection, No ADC or Refund Due.

Add Collect - Additional Collection

If the recalculation of the fare results in an additional collection, the amount preceded by the

currency code (of the location of the reissue transaction) will be displayed. For example:

Add-Collect – NOADC

If the recalculation of the fare results in the same amount as the original ticket, no additional

collection applies and will be shown as NOADC preceded by the currency code (of the location of the

reissue transaction). For example:

Refund

If the recalculation of the fare results in a partial refund, the words “Refund” plus the amount

preceded by the currency code (of the location of the reissue transaction) will be displayed. For

example:



Change Fee

The change fee is informational only and is not included in the Add-Collect amount. The user must

collect the change fee with a separate transaction (MPD). The amount is shown with the currency

code of the location of the reissue transaction. For example:

Note: The waiver code will be included in the Endorsement Box element and displayed there

.

PTC

This field should contain the PTC (Passenger Type Code) that was included in the original request.

ADT is the default if no other PTC was included

Priced As

This field will repeat back to the user how the price was requested, depending on what they selected

in the Rapid Reprice Exchange Screen.

Best Buy in same cabin

Price as booked

Price with no penalty

Rebook Segments

When the “Price as Best Buy” or “Price with no Penalty” indicator is included in the request, one or

more of the segments in the itinerary may require a rebook in a different booking code, the segment

numbers and booking codes should be displayed here:



PCC/ACCT Code

This will display the PCC (Pseudo City Code and (if applicable) the ACCT Code (Account Code) used

when making the initial Rapid Reprice Exchange Request, for example:

Waiver Applied

If the carrier has issued a waiver, we will receive data in the Waiver Text element. When that exists

in the response, display the data in the “waiver text” element. If no waiver information is received

the word “None” will be displayed in the box.

14.2 Results Screen – Manual Fare Build Data - FBC

The data in this section must be entered to create or update the manual fare build to store the fare

for the new ticket. This must be entered manually into the booking file, but the results screen aids

the user so that the FBU entries can be “copied” and “pasted” directly into the Booking File.

This is an example of the Manual Fare Build screen that must be populated or amended with the

correct data for the new ticket. Note: This is shown here to support the layout and formats in this

section of the results screen. The agent must enter FBC to create their Fare Build.

FBC

P01 TEST/TESTMR *ADT 01 OF 01

X CTY CX FLT CL DATE TIME ST FB / TD NVB NVA BG

. JFK BA 172 Q 20SEP 0820 OK @.............. ..... ..... @.. 1

O LHR BA 302 Y 22SEP 0615 OK @.............. ..... ..... @.. 2

O CDG BA 309 Y 24SEP 1220 OK @.............. ..... ..... @.. 3

O LHR BA 177 N 30SEP 1340 OK @.............. ..... ..... @.. 4

. JFK

FARE @../........ EQ .../........ ROE @...........

TAX 1 ......./.. 2 ......./.. 3 ......./.. 4 ......./..

5 ......./.. 6 ......./.. 7 ......./.. 8 ......./..

TTL (INC TAX) @.......

FC

)>

The layout of the response screen will be such that it can easily be transferred to the Manual Fare

Build screen above. This section displays the data in a format that can easily be “copied” and

“pasted” and appended to the FBU format to update the Manual Fare Build screen.



The elements in this section are explained below

Fare

The new base fare amount shown with the 3-letter currency code of the fare currency on the

original ticket. For example:

EQV

When the currency of the reissue location is different than the currency of original issue, the

currency codes must be shown in the EQ field:

ROE

The IATA rate of exchange must be included in the manual fare. The ROE is displayed including

the decimal point. For example:

Fare Basis

Displays the Fare Basis Code for each unflown fare component. It includes the segment number.

The Fare Basis should include any Ticket Designator as well. For example:

Baggage



The baggage allowance must be entered when building a manual fare, for example:

NVB/NVA

NVB (not valid before) and NVA (not valid after) dates will be received in the data from Rapid

Reprice and will be displayed for each segment when they are applicable, for example:

New Taxes

Only new taxes that have not already been paid on the original ticket are to be entered in the

Manual Fare Build. These taxes should not be displayed with the currency code. It is assumed

that any new taxes are displayed in the currency of the location of the reissue. The 2 letter tax

code is appended to each new tax amount. For example:

Fare Construction

The Fare Construction linear construction is shown from the point of origin and must be added to

the Manual Fare Build.

Endorsement Box

The Endorsement Box will include any data that must be entered by the user in the endorsement

box of the ticket. The data will also include any waiver code that might apply which must also be

entered in the endorsement box of the new ticket by the agent.



14.3 Complete Manual Fare Build Screen

Below is an example of a manually populated fare build screen after the data has been entered by

the user:

Error! Reference source not found.14.4 Results Screen – Manual Exchange Screen Data -

TMU

Once the Fare Build is created, the following data in the TMU section must be entered by the user

into the Exchange Screen Fill-In Format.

Below is an example of the Manual Exchange screen fill-in format that the user must either populate

or amend with the correct data for the exchange transaction. The user must tab thru the fill-in areas

and enter or change the data.

If the following format is used TMU1FEX (INPUT WITHOUT TICKET NUMBER), all of the applicable

data except for the new fare must be filled in by the user.

>*EX **TICKET FOR**: TEST/TESTMR PSGR 1/ 1

NEW FARE: USD 508.00 EQUIV:∑GBP 508.00

TX1: 19.70 UB TX2: 37.00 YQ TX3: 10.80 FR TX4: 8.30 QX

*EXCH TICKET*: TICKET NUMBER THRU TICKET NUMBER NO. CPNS

∑.............. ∑. ∑.............. ∑..

COUPONS FOR TKT1:∑.... TKT2:∑.... TKT3:∑.... TKT4:∑....

PD TAXES 1:∑......∑.. 2:∑......∑.. 3:∑......∑.. 4:∑......∑..

PD TAXES 5:∑......∑.. 6:∑......∑.. 7:∑......∑.. 8:∑......∑..

TTL VALUE:∑........... BSR:∑...... ORIG FOP:∑...............

*ORIG ISSUE*: TICKET NUMBER ORG/DES CITY DATE IATA CODE

∑.............. ∑.../... ∑... ∑....... ∑.......

∑



If the following format (below) is used (including the number of the ticket to be exchanged), some of

the data will be pre-populated, but may need to be amended by the user. For example:

• The XT combined tax must be removed and replaced with itemised taxes that were

included in the XT and their appropriate 2-letter codes.

• The total value may need to be altered if the original ticket included taxes that no longer

apply to the new itinerary.

TMU1FEX12599006383674/CBA (INPUT WITH TICKET NUMBER)

*EX **TICKET FOR**: TEST/TESTMR PSGR 1/ 1




∑12599006383674 ∑. ∑.............. ∑02

COUPONS FOR TKT1:∑12.. TKT2:∑.... TKT3:∑.... TKT4:∑....

PD TAXES 1:∑40.00.∑GB 2:∑19.70.∑UB 3:∑189.00∑XT 4:∑......∑..

PD TAXES 5:∑......∑.. 6:∑......∑.. 7:∑......∑.. 8:∑......∑..

TTL VALUE:∑GBP199.00.. BSR:∑...... ORIG FOP:∑...............


∑.............. ∑JFK/LHR ∑LON ∑15JUL08 ∑9999999 ∑

This section of the response screen will include the information that must be transferred to the

Manual Exchange Screen. This data cannot be entered using formats. The user must tab through

the fill-in and enter the data.

Ticket Number

The original ticket number is entered in the Exchange Screen

BSR

Display the Bankers Selling Rate between the currency of origin and currency of location of

reissue.



Paid Taxes

When the country of issuance is a BSP country, the response from RR will take the taxes that

were provided in the request and show them as paid per the BSP rules.

These are taxes that were paid on the original ticket AND still apply to the new itinerary.

Paid taxes are shown in the original currency of purchase.

Important Note

Travelport Rapid Reprice processes changes to paid taxes in accordance with industry standards.

Depending on the change in itinerary this may mean that there is a reduction in tax on the ‘new’

ticket. This tax reduction will be ‘netted’ out of the Additional Collection. Please pay particular

attention to the Paid Taxes screen to ensure that residual amounts are processed accurately.

Refer also to *HTE to compare original taxes with new taxes.

For example original Taxes 20.00GB 17.40UB 29.00YQ results as below.

Example -

Original Tax Total GBP66.40

New Tax Total (Paid Taxes) GBP34.50

Difference (Residual Tax Amount) GBP31.90

Original Fare GBP100.00

New Fare GBP200.00

Difference (Additional Fare) GBP100.00

The reduction in tax as detailed above may be deducted from any ADD Collect indicated on the results screen.

Example - The additional collection takes in to account the refundable tax value.

ADD Collect Box (Results Screen) GBP68.10



Total Value

This data is not returned by Rapid Reprice. This field must be completed in the Manual Fare

Build screen by the user. The amount that must be entered in the TTL VALUE field by the user is

the Base Fare Amount (or EQV Fare amount if purchased in a different currency other than the

currency of the country of origin) including the currency code from the original ticket plus any

paid taxes that no longer apply to the new itinerary. The following hint is displayed on each

Response Screen:

This is an example of what a manually updated exchange screen fare build screen would look like

after being completed by the agent:

>*EX **TICKET FOR**: TEST/TESTMR PSGR 1/ 1




∑12599006383674 ∑. ∑.............. ∑02

COUPONS FOR TKT1:∑1234 TKT2:∑.... TKT3:∑.... TKT4:∑....

PD TAXES 1:∑40.00.∑GB 2:∑19.70.∑UB 3:∑189.00∑XT 4:∑161.00∑YQ

PD TAXES 5:∑15.40.∑US 6:∑6.30..∑XT 7:∑......∑.. 8:∑......∑..

TTL VALUE:∑GBP199.00.. BSR:∑0.5028 ORIG FOP:∑NONREF.........


∑12599006383674 ∑JFK/LHR ∑LON ∑15JUL08 ∑9999999

∑

>



15. Examples of Final Results Screen Layout

15.1 Unused Ticket.

• Change to return before departure.

• New fare is higher for weekend travel.

• Change Fee applies.

• All applicable taxes paid on original ticket.



15.2 Partially Used Ticket.

Change in routing on return.

New fare is lower, therefore a refund is due.



16. Storing Rapid Reprice Results

When all the qualifying data has been entered into the Fare Build and Exchange Field the user should

click “Close”, Rapid Reprice will generate special notepad remarks fields that will be stored in History

when the booking file is ended at “End Transaction”. These remarks fields will appear in the history

only of the Booking File and will be “locked” so the they cannot be changed or deleted. The notepad

fields will include the following elements from the “Rapid Reprice Results” screen. The numbers

correspond to the numbers used to identify the fields. Each element should be preceded with the

indicator as shown:

1. AC or RF -- Add Collect or Refund due (includes Currency Code and amount) 2. CF -- Change Fee (includes Currency Code and amount) 3. PTC 4. BB, FQ, or PE0 -- Pricing Method 5. Rebook info 6. PCC -- PCC/Account Code 7. Fare -- New Fare 8. EQ -- EQV (if applicable) 9. ROE 10. FB1, FB2 etc -- Fare Basis Codes 11. NT -- New Taxes (if applicable) 12. BG - Baggage 13. NVA/NVB – Not valid before/after 14. FC - Fare Construction Linear 15. EB – Endorsement Box 16. TKT -- Ticket Number 17. BSR – Bank Selling Rate(if applicable) 18. PT -- Paid Taxes

The Historical Notepad Rapid Reprice remarks will also include the flight segments that were

generated to be repriced. The remarks can subsequently be displayed by entering *H. The screen shot below depicts a completed set of Rapid Reprice Historical Notepad Fields as

displayed in history.

XNP HR **********...** RAPID REPRICE RESULTS **........669HV8L 2717JUL1204Z XNP HR **********(1)RFGBP411.00..(2)CFGBP0.00..(3)ADT..(4)BB.............. 2717JUL1204Z XNP HR **********(5)REBOOK1L/2O..(6)PCCEA7..(7)GBP103.00..(9)ROE0.510239.. 2717JUL1204Z XNP HR **********(10)FB1/LVALUE FB2/ONCLON2..(12)BG/1PC..(13)NVB1/16SEP08. 2717JUL1204Z XNP HR **********NVB2/19SEP08 NVA1/16SEP08 NVA2/19SEP08....... 2717JUL1204Z XNP HR **********(14)FCADT MAN BA PAR 169.53BA LON32.33NUC201.86.. XNP HR **********(15)EBNONREF/NONREF/-NCLON2/NON-REFUNDABLE....... 2717JUL1204Z XNP HR **********103.00 GBP..(16)TKT1259900638372..(18)PT10.00GB...... 2717JUL1204Z XNP HR **********13.00UB 37.00YQ 10.80FR 0.80IZ 8.30QX........ 2717JUL1204Z XNP HR **********BA4853Y 16SEP MANCDG 1115 1355............... 2717JUL1204Z XNP HR **********BA309Y 19SEP CDGLHR 1220 1240................ 2717JUL1204Z



17. Fare Guarantee for Reissued Tickets

As Rapid Reprice requires the use of Manual Fare Build Screens a ‘B’ Status code is generated in the

Booking File. The Travelport Fare Guarantee Policy does not make provision for ADMs (Agency

Debit Memo) issued against a ‘B’ status fare. For any ADMs received as a result of a Rapid Reprice

transaction Travelport is pleased to state that these ADMs may be logged and submitted for

research (usual procedures apply) and are covered under the terms of the current Fare Guarantee

Policy.



Appendix 1 - Australia

Detailed below are Australia market examples using local routes flown by Australian carriers.

A/ Domestic Australia example SYD-MEL on Qantas

A PNR has been created and domestic ticket issued with a fare basis OPTWEBU

The ticket issued is displayed as follows:

Galileo entry:-

*HTE



Response below

The passenger has requested a change of date so a new segment is booked into the PNR. Notice the

passenger now wishes to travel on 20th August and the same class of service has been booked.

Rapid Reprice is activated and the new flight requested is selected.

The Rapid Reprice window is activated from the companions drop down menu:-



The green tick identifies the flight now required by the passenger. ‘Continue’ button clicked.

The response from Rapid Reprice is displayed below with the details on the changes made. Notice

the change fee appears in the ‘Change Fee’ box along with the new taxes that are associated to this

fee in this example the UO tax is displayed in the ‘New Taxes’ box.



B/ Trans Tasman example on QF:

Fare display for a SYD to AKL fare on QF



A PNR is created and ticketed for a one-way SYD-AKL using the QREDT fare which allows a date

change at AUD$60.00 and no GST tax applies.

*FF1 to see the fare details

The new segment is booked (date change to 25Oct) and Rapid Reprice is activated and ‘Price as

Booked’ option is selected.



‘Continue’ button is selected and response as follows:



The response from Rapid Reprice indicates the AUD60.00 change fee in the ‘Change Fee’ box and no

GST applies so the ‘New Taxes’ box is blank.



C/ Domestic Australia example – SYD to DBO on Regional Express

Fare display above showing carrier ZL fares SYD to DBO

Passenger is booked for travel SYD to DBO on 19th November returning 25th November. The ticket

issued on Regional Express.

Galileo entry to display ticket:-

*HTE

Response below



The passenger requests a change on the SYD DBO flight to the 20th November and the new flight is

added to the PNR as below:-

Rapid Reprice is activated from the ‘Companions’ drop down menu as below:-



The green ticks are used to identify the required flights for repricing.

The Continue button is selected and the response is shown below:



The response from Rapid Reprice identifies the change fee as AUD30.00 in the ‘Change Fee’ box and

the new associated tax is shown in the ‘New Taxes’ box for the 3.00 UO amount.

Date post:	28-Sep-2018
Category:	Documents
Upload:	vodiep
View:	228 times
Download:	2 times

Rapid Reprice Galileo User Guide AUNZ June 2010 - … · Travelport GDS is also able to process...

Documents