FCP Ticketing instructions

All fare rules can be found in Amadeus:

FQD HELSTO/R, U123456 to display fare

(123456 is the company’s corporate number example)

FQN line number to display fare rule

 

Inputs in other GDSs

Galileo:

FD MILHEL21DEC/AY-PRI-Corp.nbr:PFN*line number

Worldspan:

4FWAWHELSR-AY/@@Corp.nbr 4F.R line nbr

Sabre:

FQNYCHEL15NOV-AY‡AC*Corp nbr‡PV«

Abacus:

FQHKGHEL19JAN‡UAC*Corp nbr RD + line nbr of the fare

Travel Sky:

XS FSD CANHEL/AY/PRVT/#CCorp nbr/CNY XS FSN+ line nbr of the fare

Infini:

FSD TYOHEL/31MAR08/AY/NEGO/#Ccorp nbr FSN line nbr of the fare

Topas:

same as Amadeus

Axess:

FDTYOHEL10JUN-NET/AY#UI corp code FN*line nbr

Pricing

Pricing entry in Amadeus FXP/R, U123456

IT code will be printed onto the ticket, ITAYCORP123456

Please replace this example by the real corporate number.

 

Inputs in other GDSs

Galileo:

FQ-Corp nbr/CAY

Sabre:

WPAC*Corp nbr‡PNEG OR WPICorp nbr‡ PNEG

Worldspan:

4PFSR|/@@Corp.nbr

Abacus:

WPAAY‡AC*Corp nbr

Travel Sky:

QTE:/AY///#Ccop nbr (PNR pricing)

FSI/AY///#CCorp nbr (pricing without PNR)

Infini:

FQB
FSI/MH/SPCL/#Ccorp nbr

Topas:

Same as Amadeus

Axess:

FQSNN# I corporate code

 

NOTE: When Finnair published fares change, the corporate fare levels loaded in GDSs will change accordingly. The discount percentage vs. the published fare level remains fixed.

Client Code

When pricing with corporate fare, make sure that also client code is added in reservation. Client code is inserted in OS element:

Input in Amadeus:

OS AY CMP ABC000FI or OS AY CMP PK0000FI

1 2 3 4

1 OS Other Service information

2 AY or YY (mandatory)

3 CMP (Company, mandatory) will be followed
by client code

4 Client code: e.g.: ABC000FI or PK0000FI

Client code is needed when there are Finnair flight(s) in PNR and Finnair’s document is issued. Insert the code in reservation once PNR is created. However, it is possible to add a missing client code or modify an existing one as long as there is at least one unflown segment in PNR.

 

Input in other CRSs: In all of these examples airline code may be AY or YY:

Galileo:

SI.AY*CMP client code

Sabre:

OSI AY CMP client code

Worldspan:

3OSI AY CMP client code

Abacus:

3OSI AY CMP client code

Travel Sky:

OSI: AY CMP client code/P1

Infini:

4OSI AY CMP client code

Topas:

3F OSI AY CMP client code

Apollo

=:3OSI AY CMP client code

Axess:

4 OSI AY Client Code

Note that there may be only one Finnair client code per passenger (these examples from Amadeus):

a) When there are several passengers with different client codes, OS elements must be passenger associated

1. MIETTINEN/MARI MS 2. KOIVU/KALLE MR 3. ELO/TEA MS
OS AY CMP ABC123FI/P1
OS AY CMP PK1234FI/P2,3

If only P1 had passenger association and if P2 and 3 were without association, system would assume that OS AY CMP ABC123FI belongs to all passengers. Then P1 would have two client codes and as a consequence purchases would not be reported.

b) If several passengers have the same client code, passenger association is not needed. Code will then apply to all passengers.

1. MIETTINEN/MARI MS 2. KOIVU/KALLE MR 3. ELO/TEA MS
OS AY CMP ABC123FI

c) Travel will be paid by another company than the one that the passenger is associated to in customer profile. In case information is transferred to the PNR both from passenger profile and from separate company profile and the client codes are not the same, the client code that will not be used must be cancelled from the reservation.

If more than one client code is indicated to a passenger, purchases will be missing from corporate report.

1. MIETTINEN/MARI MS
OS AY CMP ABC123FI/P1

information has been transferred from customer profile -> element must be cancelled from PNR

OS AY CMP PK1234FI

information has been transferred from company profile. Because payment will be made by company, this OS element must remain in reservation.