Professional Documents
Culture Documents
Incentive Ticketing
Published by:
Error: Reference source not found
359522869.doc - 03/07/17 - ii
PREFACE
Document History
References
Amadeus References
DOC NUM TOPIC
A-02-3619-AMD Amadeus Negotiated Fares Processing
A-02-3512-AMD PNR Pricing
A-02-1306-AMD PNR Fare Element
A-02-3507-AMD Carrier Selection
A-02-3500-AMD TST Create and Processing
A-02-3501-AMD Demand and Time Initiated Ticketing
A-02-4205-AMD Amadeus Central Ticketing : Commission tables and processing
A-02-4200-AMD Form Of Payment Validation
TP002-M030 Amadeus Edifact Conventions and Directory
TP002-M052 Amadeus Conversations Fare Server
External References
359522869.doc - 03/07/17 - iv
TABLE OF CONTENTS
359522869.doc - 03/07/17 - vi
AIR - 1........................................................................................................................................................... 10-1
AIR - 5........................................................................................................................................................... 10-1
AIR - 2........................................................................................................................................................... 10-1
10.2. K- LINES.......................................................................................................................................... 10-2
10.3. AIR - 1 . CREATE OLD FORMAT AIR FROM OLD TST.......................................................................10-3
10.3.1. Build L-Line................................................................................................................................................ 10-3
10.4. AIR - 2 . CREATE NEW FORMAT AIR FROM OLD TST......................................................................10-4
10.4.1. Input Data.................................................................................................................................................. 10-4
10.4.2. Output Data................................................................................................................................................ 10-4
10.4.2.1. If TST Pricing Code = B...................................................................................................................... 10-4
10.4.2.2. If TST Pricing Code F or G.................................................................................................................10-4
10.5. AIR - 3 AND AIR - 4 . CREATE OLD FORMAT AIR FROM NEW TST...................................................10-5
10.5.1. If TST Pricing Code = B............................................................................................................................. 10-5
10.5.2. If TST Pricing Code F or G........................................................................................................................ 10-5
10.5.2.1. Build L-Line......................................................................................................................................... 10-5
10.5.2.2. Build FM Line...................................................................................................................................... 10-5
CASE AIR 3............................................................................................................................................... 10-5
CASE AIR 4............................................................................................................................................... 10-5
10.5.2.3. Build FV Line...................................................................................................................................... 10-5
10.5.2.4. Build FT Line...................................................................................................................................... 10-5
10.6. AIR 5 . CREATE NEW FORMAT AIR FROM NEW TST....................................................................10-6
10.6.1. Build L-Line................................................................................................................................................ 10-6
10.6.2. Build FT Line & FV Line............................................................................................................................. 10-6
10.6.3. Build FM-Line............................................................................................................................................. 10-6
10.6.4. Build SIA-Line............................................................................................................................................ 10-6
10.7. EXAMPLES....................................................................................................................................... 10-8
10.7.1. OLD FORMAT A.I.R................................................................................................................................... 10-8
10.7.2. NEW FORMAT A.I.R.................................................................................................................................. 10-9
CHAPTER 11. SPECIFIC DATA AND PROCESSING REQUIREMENTS...................................................11-1
11.1. START TICKETING SPECIFICATIONS................................................................................................... 11-1
11.2. BSP FRANCE TICKETING SPECIFICATIONS.......................................................................................11-1
11.2.1. Negotiated Fares........................................................................................................................................ 11-1
11.2.2. BSP France NET REMIT schemes............................................................................................................11-2
11.3. KL, MP AND KQ ATO/CTO NET REMIT SPECIFICS.............................................................................11-1
CHAPTER 12. CENTRAL TICKETING SERVER - INCENTIVE TICKETING.............................................12-1
12.1. INTRODUCTION................................................................................................................................. 12-1
12.2. GENERIC PROCESSING.................................................................................................................. 12-2
12.2.1. CTS establishes Incentive Method............................................................................................................12-2
12.2.1.1. CTS determines data source..............................................................................................................12-2
12.2.1.2. Nego data source Incentive Methods (IM).........................................................................................12-2
12.2.1.3. Agent data source Incentive Methods (IM).........................................................................................12-2
12.2.2. CTS establishes Value of AEBA (Net Fare)...............................................................................................12-4
12.2.3. CTS establishes Values of T_ADJ and R_ADJ.........................................................................................12-5
12.2.4. CTS establishes Values of NR_TOT, CASH_TOT, CRED_TOT; TAX_TOT..............................................12-6
12.2.5. CTS Ticket Print Module............................................................................................................................ 12-7
12.2.5.1. Remittance Area................................................................................................................................. 12-7
12.2.5.2. TOUR CODE Box Printing..................................................................................................................12-8
12.2.5.3. FARE and TOTAL Boxes Printing.......................................................................................................12-8
12.2.6. CTR Reporting Module.............................................................................................................................. 12-9
12.2.7. CTR Sales Reporting Module....................................................................................................................12-9
Chapter 1. Introduction
1.1. Description
Negotiated fares are special air fares agreed between an individual airline and its appointed agent.
These fares may be used by the agent for all sales or may be restricted to certain of the agents corporate
customers, depending on the type of agreement concluded between the Travel Agent and the individual
airline(s).
Many Bank Settlement Plans now wish to have these sales reported in a way which differs from standard
reporting. Thus additional information is required to be sent at ticketing time to the National Systems whose
local BSP supports such a scheme.
1.2. Prerequisites
Negotiated Fares are stored and maintained in the aMaDEUS Fare Server Database. The Database
structure and maintenance is described in A02-NEGOTIATED FARES IN ENCODED STRUCTURE
documentation.
The Fare Quote Interface is structured to deal with new ticketing data format as well as the old format.
To avoid a situation of difference between the version of the Software in place when the TST is created and
the version of the software in place at TTP time, Global core has to reject the TTP entry in the following
cases :
1.3.1. Processing of new TST with the Old Software (fallback situation)
At TTP Time, in this case, the following error message is displayed :
INVALIDNEGOTST:PLEASEREPRICE
INVALIDNEGOTST:PLEASEREPRICE
359522869.doc - 03/07/17 - 1
aMaDEUS
Chapter 2. General Data and Processing at Pricing Time
The reader should always check the chapter Specific Data and Processing requirements for market/airline
exceptions to general functionality defined in this chapter.
- Fare amount
- Equivalent amount
The first occurrence of these fields determines the published fare, the second the Net fare and the third the
Selling Fare.
The type of information returned to Global Core in the FQIR will differ depending on whether the fare is
associated to a Published fare or not.
In both cases (i.e. when a Published fare is present or not), the fare server will send back one set of tax
information that is to be applied to each fare.
Differences may apply in the way TSTs are created when the Fare Server returns a Negotiated Fare in the
FQIR. In all cases it is the selling fare which is to be displayed in the TST.
The process is detailed in Chapter : TST Creation FARE Information
- The New format is called SIA format (i.e. fares stored using the new XNB transaction)
- The Old format is called BSP format (i.e. fares stored in the old negotiated database)
A new AIR Indicator called SIA NEGO DATA (T14 and B14) was defined in the Office Profile Record and will
be generally sufficient to determine the way the TSTs, PNRs and AIRs have to be built.
Generally T14/B14 set to YES means that NEW format of Negotiated Fares Data is accepted.
If set to NO, this means that only the OLD format is acceptable by the AIR recipient.
However, there are some exceptions, driven by the Ticketing Option data.
This option will disappear when the accepted AIR Version is more recent than V204. In that case, and
starting from Version V205, the NEW Data Format is automatically sent to (and then accepted by) the AIR
recipient.
A02-3279 - 03/07/17 - 2
aMaDEUS
IF Ticketing Option = 1A OR 7A OR 8A
Then
IF AVN AIR Version > 204
Then
Data-Format = NEW
Else
IF T14 = YES
Then
Data-Format = NEW
Else
Data-Format = OLD
End
End
End
IF Ticketing Option = 5A OR 5B
Then
(Determine VSN : Accounting AIR Version)
IF AON NOT = 000000 or Own AMID
Then
VSN taken from TARGET Office
Else
VSN taken from Own Office
End
Where :
A02-3279 - 03/07/17 - 3
aMaDEUS
Chapter 3. TST Creation FARE Information
IMPORTANT
This indicator is determined INDEPENDENTLY of the value of data-format according
to Section 2.5.
- Pseudo-TST Display
FXP/R,NEGO
01TEST/NEGO*
<NEGO>
ALFLGTBKTDATETIMEFAREBASISNVBNVABG
DEL
ZRHSR0001YY01MAR0600TEST3520
DELSR0002YY15MAR0600TEST3520
INR2000001MAR99DELSRZRH249.32SRDEL249.32NUC
498.64ENDROE40.10750SITI
INR500FT
INR446CH
INR20946
>S....
TST00001BOMI22TKTAA/27AUGFODDELDELSISITITKTCARRIERSR.
1.TEST/NEGOMR
CTYCRFLT/CLSDATETIMESTPCF/BTKT/DNVBNVABG
1.DELSR001Y01MAR0600OKTEST35...................20K
2OZRHSR002Y15MAR0600OKTEST35...................20K
.DEL............................
.............................
A02-3279 - 03/07/17 - 1
aMaDEUS
.............................
FAREFINR20000EQUIVALENT.............TAXXINR500FTAD
TAXXINR446CHAETAX..............TAX..............
TOTALINR20946BR...........
A02-3279 - 03/07/17 - 2
aMaDEUS
- TST Display (TQN)
TST00001BOMI22TKTAA/27AUGFODDELDELSISITI
1.TEST/NEGOMR
1DELSR001Y01MAR0600OKTEST3520K
2OZRHSR002Y15MAR0600OKTEST3520K
DEL
PINR30000
NINR10000
FAREFINR20000
TAXXINR500FTADXINR446CHAE
TOTALINR20946
DELSRZRH373.99SRDEL373.99NUC747.98ENDROE40.10750
The TST is created with F as pricing indicator if the Net Updater is an Airline.
The TST is created with G as pricing indicator if the Net Updater is an Agent/Consolidator.
NOTE : The "F" and G indicators are automatic pricing indicators, therefore, no fare Calculation edits take
place on Global Core side.
When the Negotiated Fare is associated to a Published Fare, then the Fare Server returns to Global Core
three Fare data information elements in the following order : Published Fare, Net Fare, Selling Fare.
The Published fare and the Net fare fields are stored and indexed in the TST but they are not displayed in
the normal TST display.
They are however displayable by help desks using the TQN entry as described in A02-4500
Global Core extracts the selling fare data fields from Interface 2 and uses this information to store in the TST.
This information is displayable.
An issue identifier of F (denoting negotiated fare based on published) is then created by Global Core and
stored in the TST.
In all other aspects, TST Create and processing are unchanged (see A02-4500-AMD TST Creation and
Processing).
A02-3279 - 03/07/17 - 3
aMaDEUS
- Pseudo-TST Display
FXP/R,NEGO
01TEST/NEGO
<NEGO>
ALFLGTBKTDATETIMEFAREBASISNVBNVABG
BOM
LONBA0138SS01OCT0210TEST3223
BOMBA0139SS15OCT0955TEST3223
INR3000001OCT98BOMBALON373.99BABOM373.99NUC
747.98ENDROE40.10750SITI
INR500FT
INR1428GB
INR31928
- TST Display
>S....
TST00001BOMI22TKTAA/17JUNFODBOMBOMSISITITKTCARRIERBA.
1.TEST/NEGO
CTYCRFLT/CLSDATETIMESTPCF/BTKT/DNVBNVABG
1.BOMBA138S01OCT0210OKTEST32...................23K
2OLHRBA139S15OCT0955OKTEST32...................23K
.BOM............................
.............................
.............................
FAREIINR30000EQUIVALENT.............TAXXINR500FTAD
TAXXINR1428GBAETAX..............TAX..............
TOTALINR31928BR...........
A02-3279 - 03/07/17 - 4
aMaDEUS
- TST Display (TQN)
TST00001BOMI22TKTAA/27AUGFODBOMBOMSISITI
1.TEST/NEGO
1BOMBA001S01MAR0600OKTEST3223K
2OLHRBA002S12MAR0600OKTEST3223K
BOM
NINR20000
FAREIINR30000
TAXXINR500FTADXINR1401GBAE
TOTALINR31901
BOMBALONM/ITBABOMM/ITEND
The TST is created with F as pricing indicator if the Net Updater is an Airline.
The TST is created with G as pricing indicator if the Net Updater is an Agent/Consolidator.
NOTE : The "F" and G indicators are automatic pricing indicators, therefore, no fare Calculation edits take
place on Global Core side.
Additionally, when a Negotiated Fare is not associated to a published Fare, the Fare Server returns a "/"
indicator in the published Fare field in the Interface.
Therefore, the Fare data information returned from the Fare Server comes in the following order :
'/'(slash), Net Fare, Selling Fare.
Global Core creates the issue identifier of "I" or U (denoting negotiated fare not associated to published
fare) and stores it in the TST together with all the fare, equivalent, tax and total fields associated to the
selling fare.
The Net Fare information returned from the Fare Server is stored and indexed in the TST, but it is not
displayed in the normal TST display.
It is however displayable by help desks using the TQN entry as described in A02-4500.
In all other aspects, TST Create and Processing are unchanged (see A02-4500-AMD TST Creation and
Processing).
A02-3279 - 03/07/17 - 5
aMaDEUS
Chapter 4. TST Creation Preferred Ticketing Carrier
The Preferred Ticketing Carrier sent in the General Information portion of the Fare
Quote Interface is used to automatically generate an FV PNR element, depending on
the value of data-format determined according to Section 2.5 :
Example :
FV*F*BA
The newly created FV*F* element replaces any existing PNR FV element for the TST.
Example :
FVBA
Any manual update to an FV element (with or without type *F*) replaces it with no incidence on the
Negotiated Fare TST pricing indicator.
The current carrier selection process to validate the carrier (either entered by the agent or generated by the
system) in FV element is still required.
A02-3279 - 03/07/17 - 1
aMaDEUS
Chapter 5. TST Creation - SETTLEMENT Information
Data Format :
123
<FMdata>(/)<PaymentRestriction>
Example :
FM9 / CREDIT CARD ACCEPTED
FM10 *CCA* VALID ON LH ONLY
Note : if a valid FM is found but not followed by / or * , it is considered as part of free flow text, and would not
be used as FM data by the system.
123456
{FM}{(nn)|(nnnnnnn)}<.nn>(A)
where :
1 = commission data identifier characters FM-
2 = up to 2 numeric commission percentage (conditional on absence of component 6, or 6 =N)
3 = OR
4 = up to 7 numeric commission amount (conditional on presence of component 6 = A)
5 = optional decimal point and up to 2 numeric decimal places (may apply to a percentage or an amount)
6 = character A indicates that preceding commission data is a commission amount (conditional on the
presence of more than 2 numeric in component 4). When absent, commission percentage is assumed.
6 = character N Indicates that preceding commission data is a commission percentage to be applied on
NET fare (conditional on presence of component 2).
FM9
FM10.25
FM9N
FM500.00A
A02-3279 - 03/07/17 - 1
aMaDEUS
FM1200A
A02-3279 - 03/07/17 - 2
aMaDEUS
123
<CAR>()<VC>
1 = CAR : this represents either a commercial Agreement Reference or an IT/BT tour code. It does not
exceed 16 characters.
2 = - is conditional on the presence of component 3. Used to identify between CAR and VC data.
3 = VC : This data represent either a Value Code or a commission percentage.
If commission percentage, the format is FMnnnn.
Examples :
NRABCDEF-
ABCDEF-D10550
-Z10
ABCDEF-FM9
Data Format :
1234567891011
{SI}<COMV>(COMI)<SCOMV>(SCOMI)<CREDI>(REML)(TOUR)(FTEXT)(CAR)(VC)
I : IT transaction
B : BT transaction
A : IT with NR flag
C : BT with NR flag
N : Net Remit transaction
A02-3279 - 03/07/17 - 3
aMaDEUS
F : Flexible Commission
A02-3279 - 03/07/17 - 4
aMaDEUS
12345678
(PR)(CAR)(/)(VC){*PC*}(FMdata)(/)PRdata)
Convention :
1= Payment Restriction identifier - conditional on use of panel mode TST (this identifier is not used in
cryptic mode).
2= CAR data from FQIR - conditional on presence of CAR component in the FQIR BSP-CAR/VC field.
3= separator - conditional on presence of the -separator in the FQIR BSP-CAR/VC field AND on
the presence of VC data. If the -is followed by VC data in the FQIR input then global core replaces
this with the character in the TST PR line output. If the -is not followed by VC data then it is
ignored for output.
4= VC - conditional upon presence of VC data in FQIR BSP-CAR/VC field its input (and therefore its
output) has a maximum of 6 characters.
5= *PC* preferred ticketing carrier - mandatory output of the two alpha preferred ticketing carrier code
from the FQIR, prefixed and suffixed by the *character.
6, 7 and 8 = These components are all conditional upon their presence in the endorsement/payment
restriction field of the FQIR. There is NO global core editing - they are output as received. (They are
here identified as separate components in order to clarify subsequent processing regarding the
creation of a PNR FM element).
The maximum length of the PR line in the TST (76) means that any excess data received in the FQIR is
truncated.
A02-3279 - 03/07/17 - 5
aMaDEUS
12345678910111213
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc/
Where :
Examples :
1 SIA/N/9.00////N/N///ABCDEFG//
2 SIA/N/7.50////N////ABCDEFG/D1200/
3 SIA/F/12.50//////////
4 SIA/I/////N//IT8AF1ABCDE/ITFARE///
Explanation :
A02-3279 - 03/07/17 - 6
aMaDEUS
FXP
N Y
Data-Format
= NEW (*)
PNR PNR
Create FV Create FM *x*
Create FT (std) Create FT *F*
Create FV *F*
(*) Data-format is NEW or OLD depending on the result of the algorithm described in Section 2.5.
A02-3279 - 03/07/17 - 7
aMaDEUS
A02-3279 - 03/07/17 - 8
aMaDEUS
123
<CAR>()<VC>
123
<FMdata>(/)<PaymentRestriction>
12345678
(PR)(CAR)(/)(VC){*PC*}(FMdata)(/)PRdata)
The dash - character between BSP-CAR and VC fields is changed to a slash / character.
A02-3279 - 03/07/17 - 9
aMaDEUS
- SIA :
1234567891011
{SI}<COMV>(COMI><SCOMV>(SCOMI)<CREDI>(REML)(TOUR)(FTEXT)(CAR)(VC)
- PR :
12345678
(PR)(CAR)(/)(VC){*PC*}(FMdata)(/)PRdata)
The SIA TOUR field OR the SIA CAR field (if not blank) is copied in PR CAR field.
A slash / character is generated if the SIA VC field is not blank.
The SIA VC field (if not blank) is copied in PR VC field.
The preferred carrier (from FQ Interface) is copied with * as prefix and * as suffix.
The SIA COMV and COMI are concatenated and copied in PR FM data field with a / character as suffix.
The PR data (from FQ interface) is copied.
Example 1:
PC = LH
SI = blank
COMV+COMI = 250A
TOUR = blank
CAR = blank
VC = blank
PR data = THIS IS A FLEXIBLE COMMISSION SCHEME
PR Line = *LH*FM250A/THIS IS A FLEXIBLE COMMISSION SCHEME
Example :
PC = BA
SI = I
COMV+COMI = 9
TOUR = IT2IB3TOUR99
CAR = blank
VC = blank
PR data = THIS IS AN IT CASE
PR Line = *BA*FM250A/THIS IS AN IT CASE (see FT PNR Element Generation Chapter)
PC = AF
SI = N
COMV+COMI = 12.5
TOUR = blank
CAR = ABCDEF
VC = D1250
PR data = THIS IS A NR METHOD 1 CASE
PR Line = ABCDEF/D1250*AF*FM12.5/THIS IS NR METHOD 1 CASE
PC = AF
SI = N
A02-3279 - 03/07/17 - 10
aMaDEUS
COMV+COMI = 12.5N
TOUR = blank
CAR = NETREMIT
VC = blank
PR data = THIS IS A NR METHOD 2E CASE
PR Line = NETREMIT *AF*FM12.5N/THIS IS NR METHOD 2E CASE
A02-3279 - 03/07/17 - 11
aMaDEUS
123
<CAR>()<VC>
123
<FMdata>(/)<PaymentRestriction>
Note that field 2 may be a / or a *
- The PR Line:
1
<PaymentRestriction>
12345678910111213
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc
All the data that system may find following a valid FM data (as described in Section 5.1.1) in the
PAYMENT/RESTRICTION data is copied in the PR Line of the TST.
If no valid FM data is found, all PAYMENT/RESTRICTION data is copied as it is in the PR Line of the TST
Else
Move N to SI.
End
End
End
5.5.3.5. Determine the COMMISSION (COMV and COMI)
IF The Endorsement/Payment Restrictions field contains a valid FM data (as described in Section 5.1.1)
Then
Move FM data to COMV (excluding the FM characters)
If FM data alphabetic suffix exists (i.e. N or A, e.g. 10.5N or 125A)
Then
Move FM data alphabetic suffix to COMI
End
Else (no valid FM data in Endorsement/Payment Restrictions field)
IF First characters of BSP-CAR/VC is -FM (valid FM data found in VC field, see Section 5.1.2)
Then
Move FM data to COMV (excluding the FM characters)
Move blank to COMI
Else
Move blank to COMV
Move blank to COMI
End
End
5.5.3.6. Determine the SUPPLEMENTARY COMMISSION (SCOMV/SCOMI)
Move to CREDI
IF SI = N
Then
IF (BSP VC = blank OR BSP VC starts with FM) AND
(BSP CAR strictly = NR OR BSP CAR does not start with NR)
Then
Move N to REML
Else
Move blank to REML
End
End
5.5.3.9. Determine the TOUR CODE (TOUR)
IF SI = I or B
Then
Move BSP CAR to TOUR
A02-3279 - 03/07/17 - 13
aMaDEUS
5.5.3.10. Determine the FARE TEXT (FTEXT)
IF SI = N
Then
Move BSP CAR to CAR.
IF SI = N
Then
IF BSP VC does not start with FM
Then
Move BSP VC to VC.
5.5.3.13. Examples
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc/
EXAMPLE 1:
Input :
BSP CAR-VC = ABCDEF/D1555
PAYMENT RESTRICTION = FM12.5N*NON REFUNDABLE AF ONLY
Output
PR Line = *NON REFUNDABLE AF ONLY
SIA = SIA/N/12.5/N///////ABCDEF/D1555/
EXAMPLE 2:
Input :
BSP CAR-VC = IT2IB3TOUR99
PAYMENT RESTRICTION = NON REFUNDABLE AF ONLY
Output
PR Line = /NON REFUNDABLE AF ONLY
SIA = SIA/I///////IT2IB3TOUR99///
EXAMPLE 3:
Input :
BSP CAR-VC = blank
PAYMENT RESTRICTION = NON REFUNDABLE AF ONLY
Output
PR Line = NON REFUNDABLE AF ONLY
SIA = SIA/F///////////
A02-3279 - 03/07/17 - 14
aMaDEUS
1234567891011
{SI}<COMV>(COMI><SCOMV>(SCOMI)<CREDI>(REML)(TOUR)(FTEXT)(CAR)(VC)
12345678910111213
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc/
The TST SIA line is built directly from the SIA data sent within the Fare Quote Interface Data.
A02-3279 - 03/07/17 - 15
aMaDEUS
5.6. EXAMPLES
- PNR
TSTRLR
RP/BOMI22TKT/BOMI22TKTAA/SU9DEC98/1307ZYGNQMK
1.NEGO/TEST
2SR195Y02MAR2DELZRHHK1202050625
3SR194Y15MAR1ZRHDELHK1A12100020+1
4APNONE
5TKOK09DEC/BOMI22TKT
7FPCASH
- Pseudo-TST Display
FXP/R,NEGO
01TEST/NEGO*
<NEGO>
ALFLGTBKTDATETIMEFAREBASISNVBNVABG
DEL
ZRHSR0195YY02MAR0600TEST3520
DELSR0194YY15MAR0600TEST3520
INR2000001MAR99DELSRZRH249.32SRDEL249.32NUC
498.64ENDROE40.10750SITI
INR500FT
INR446CH
INR20946
CAR12345/D10000
PAYMTVALIDONSRONLY
A02-3279 - 03/07/17 - 16
aMaDEUS
>S....
TST00001BOMI22TKTAA/09DECFODDELDELSISITITKTCARRIER...
1.NEGO/TEST
CTYCRFLT/CLSDATETIMESTPCF/BTKT/DNVBNVABG
1.DELSR195Y02MAR0205OKTEST35...................20K
2OZRHSR194Y15MAR1210OKTEST35...................20K
.DEL............................
.............................
.............................
FAREFINR20000EQUIVALENT.............TAXXINR500FTAD
TAXXINR476CHAETAX..............TAX..............
TOTALINR20976BR...........
COMMISSION12.5.....................TOURCODE.................
FORMOFPAYMENTCASH..........................................................
............................
FARECALCULATIONDELSRZRH348.96SRDEL348.96NUC697.92ENDROE42.98400..........
................................................................................
................................................................................
..........................
EN............................................................................
PRCAR12345/D10000*SR*FM12.5/VALIDONSRONLY..............................
ORIGINALISSUE/INEXCHANGE.....................................................
.........................................................
TST00001BOMI22TKTAA/27AUGFODDELDELSISITI
1.TEST/NEGOMR
1DELSR195Y02MAR0600OKTEST3520K
2OZRHSR194Y15MAR0600OKTEST3520K
DEL
PINR30000
NINR10000
FAREFINR20000
TAXXINR500FTADXINR446CHAE
TOTALINR20946
DELSRZRH373.99SRDEL373.99NUC747.98ENDROE40.10750
CAR12345/D10000*SR*FM12.5N/VALIDONSRONLY
6.FPCASH
7.FVSR
A02-3279 - 03/07/17 - 17
aMaDEUS
>S....
TST00001BOMI22TKTAA/09DECFODDELDELSISITITKTCARRIER...
1.NEGO/TEST
CTYCRFLT/CLSDATETIMESTPCF/BTKT/DNVBNVABG
1.DELSR195Y02MAR0205OKTEST35...................20K
2OZRHSR194Y15MAR1210OKTEST35...................20K
.DEL............................
.............................
.............................
FAREFINR20000EQUIVALENT.............TAXXINR500FTAD
TAXXINR476CHAETAX..............TAX..............
TOTALINR20976BR...........
COMMISSION12.5.....................TOURCODECAR12345/D10000
FORMOFPAYMENTCASH..........................................................
............................
FARECALCULATIONDELSRZRH348.96SRDEL348.96NUC697.92ENDROE42.98400..........
................................................................................
................................................................................
..........................
EN............................................................................
PRVALIDONSRONLY..........................................................
ORIGINALISSUE/INEXCHANGE.....................................................
.........................................................
TST00001BOMI22TKTAA/27AUGFODDELDELSISITI
1.TEST/NEGOMR
1DELSR195Y02MAR0600OKTEST3520K
2OZRHSR194Y15MAR0600OKTEST3520K
DEL
PINR30000
NINR10000
FAREFINR20000
TAXXINR500FTADXINR446CHAE
TOTALINR20946
DELSRZRH373.99SRDEL373.99NUC747.98ENDROE40.10750
VALIDONSRONLY
SIA/N/12.5/////N///CAR12345/D10000/
6.FPCASH
7.FV*F*SR
8.FM*F*12.5
9.FT*F*CAR12345/D10000
A02-3279 - 03/07/17 - 18
aMaDEUS
Chapter 6. PNR FM Element Automatic Generation (Commission)
The commission data received within the Fare Quote Interface Record is used by the system to generate
automatically an PNR FM element, using the Commission Value and Indicator, as well as the Supplementary
Commission Value and Indicator.
Convention :
1234
<COMV>(COMI)<SCOMV>(SCOMI)
{(nn)|(nnnnnnn)}<.nn>(A){(nn)|(nnnnnnn)}<.nn>(B)
1- Commission Value
2- Commission Indicator
3- Supplementary commission Value
4- Supplementary Commission Indicator
123456789
{FM}*X*{(nn)|(nnnnnnn)}<.nn>(A)</SC>(nnnnnnnnn)}<.nn>
Where :
1- FM element indicator
2- Flag for automatic commission (*F* or *G* ).
3- Commission percentage.
4- Commission amount (conditional on presence of 6 set to A).
5- Optional decimal point and 2 decimal digits.
6- Conditional Type of commission (A if commission amount or N if commission percentage on NET Fare).
7- SC Optional Supplementary Commission element Indicator.
8- Conditional on element 8 presence, amount of the supplementary commission.
9- Optional decimal point and 2 decimal digits.
A02-3279 - 03/07/17 - 1
aMaDEUS
6.3.1. COMMISSION
IF COMI = A (amount)
FM*F*COMVA PNR element is generated.
A02-3279 - 03/07/17 - 2
aMaDEUS
The supplementary commission to generate must always be an amount (and never a percentage).
IF SCOMI = A (amount)
Set scamount = SCOMV
NOTES :
The newly created FM*F* or FM*G* element replaces any existing PNR FM element.
Any manual update to an FM element with type *F* or *G* results in the Negotiated Fare TST automatic
pricing indicator "F" or G being changed to manual "B".
6.4. Examples
Example 1:
A02-3279 - 03/07/17 - 4
aMaDEUS
Chapter 7. PNR FT Element Automatic Generation (TOUR CODE)
- For NON US Markets : in case of a valid (IATA Standardised IT/BT TOUR CODE) found in the
CAR field of the Fare Quote Interface.
- For US Market : in case of the CAR field is not blank (no syntax check).
12345
{xx}{n}{xx}{n}{xxxxxxxx}
Where :
1- Tour type always IT or BT (two alpha characters)
2- Last digit of year of in which tour became effective (one numeric character)
3- Two letter Airline code of sponsoring member : One (1) alpha and one (1) numeric (or
vice versa) OR two (2) alpha Characters.
4- One digit conference area approval code
5- Tour identification 1-8 Alpha numeric characters
The Maximum Length 14 of the Tour Code is 14 alpha numeric characters (including the
Tour identifier
ITor BT
NON US MARKETS :
The system interrogates the CAR field for the existence of a standard IT/BT Tour Code according to the
syntax described previously.
If the syntax is OK the system creates a FT PNR fare element which contains the Tour Code data and
remove it from the PR Line. If the syntax is not respected the data is left in the PR Line and no FT element is
created.
US MARKET:
Any data stored in the CAR field, up to 15 characters, are used to create a FT PNR element.
COMMON PROCESS:
If a corresponding FT PNR element (either manually entered or automatically generated) already exists it is
overridden by any new system generated FT element.
A02-3279 - 03/07/17 - 1
aMaDEUS
If a previous system generated FT PNR element (flagged as automatically created) exists and the Fare is re-
priced with a Fare without FT data, the previous system generated FT element is removed.
Any manual update to a system generated FT element results in the Negotiated Fare TST automatic pricing
indicator F or G being changed to B.
7.1.3. Example
Market : NON US
Input: CAR IT8SN1TOUR99
Output: PNR FT element FT IT8SN1TOUR99
Market : US
Input : CAR ABCXYZ
Output : PNR FT element FT ABCXYZ
12345678910111213
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc
There is two placed from where the FT PNR element may be automatically generated :
The PNR FT element is generated with *F* flag indicating that the data was stored in the Negotiated Fares
Database.
The *F* indicates to the user that any change on this data will result in the TST being change to manual (TST
indicator set to B).
FT *F* TOUR
2- If the SI field is equal to N or A OR C, the system interrogated the CAR and the VC fields.
If CAR and VC are not blank, the system builds the FT elements with the following format :
FT *F* CAR/VC
If CAR is NOT blank and VC is blank, the system builds the FT elements with the following format :
FT *F* CAR
If CAR is blank and VC is NOT blank, the system builds the FT elements with the following format :
FT *F* /VC
A02-3279 - 03/07/17 - 2
aMaDEUS
If a corresponding FT PNR element (either manually entered or automatically generated) already exists it is
overridden by any new system generated FT element.
If a previous system generated FT PNR element (flagged as automatically created) exists and the Fare is re-
priced with a Fare without FT data, the previous system generated FT element is removed.
Any manual update to a system generated FT element results in the Negotiated Fare TST automatic pricing
indicator F or G being changed to B.
7.2.2. Examples
Example 1 :
Input: TOUR IT8SN1TOUR99
CAR blank
VC blank
Output: PNR FT element FT *F* IT8SN1TOUR99
Example 2 :
Input: TOUR blank
CAR NR1234ABC
VC D1250
Output: PNR FT element FT *F* NR1234ABC/D1250
Example 3 :
Input: TOUR blank
CAR NR1234ABC
VC blank
Output: PNR FT element FT *F* NR1234ABC
Example 4 :
Input: TOUR blank
CAR blank
VC /C10.5
Output: PNR FT element FT *F* /C10.5
A02-3279 - 03/07/17 - 3
aMaDEUS
8.1. Principle
The TST indicators "F" and "G" are NEGOTIATED FARE automatic pricing indicators.
Any Manual update of Negotiated Fare TST result in the TST indicator being changed to "B".
Refer to A02-3500-AMD 'Manual Stored Ticket TST creation and processing' for further information on TST
modification process.
- At TTI time of a Negotiated Fares TST (F, G or B type), the system performs the following checks :
1. If the Issue Indicator is R or Y AND the System Provider is NOT 00 (Central Ticketing), then
the TST is changed to M (Manual), and all Nego data are lost :
2. If the TST Fare amount is changed to a value which is NOT NUMERIC (e.g. NOFARE, FREE,
CHARTER, ) then the TST is changed to M (Manual), and all Nego data are lost :
3. If the FQ had returned an Equivalent fare, and that Equivalent Fare is deleted from the TST, then
the TST is changed to M (Manual), and all Nego data are lost :
4. If the FQ did not return an Equivalent fare, and an Equivalent Fare is created in the TST, then
the TST is changed to M (Manual), and all Nego data are lost :
- At TTP time of a B type Negotiated Fares TST, the system performs the following checks :
1. If the selling fare is greater than the published fare (IF EXISTS ONLY, otherwise bypass this
check), then the processing stops and an error message is displayed :
INVALIDTSTAMOUNTGREATERTHANPUBLISHEDFARE
A02-3279 - 03/07/17 - 4
aMaDEUS
2. If the selling fare is smaller than the net fare, AND if the issue Indicator is F, I or U then the
processing stops and an error message is displayed :
INVALIDTSTAMOUNTLESSTHANNETFARE
If there is an equivalent fare, then the check is done between the equivalent selling fare and the
equivalent net fare (not shown in TST display). If the equivalent selling fare is smaller than the
equivalent net fare, then the same error message is displayed:
INVALIDTSTAMOUNTLESSTHANNETFARE
3. If the Issue Indicator is F or R AND there is NOT a Published Fare, then the processing stops
and an error message is displayed :
INVALIDISSUEINDICATORWITHNEGOTST(IORY ORUORW)
4. If the Issue Indicator is I, Y, U or W AND there IS a Published Fare, then the processing
stops and an error message is displayed :
INVALIDISSUEINDICATORWITHNEGOTST(FORR)
When the 'PNR CHNG' flag is turned on, the pricing indicator is changed to Manual B and therefore the
processing performed for the Negotiated Fare TST(s), as described in the previous section 'TST Validation
applies.
Refer to A-02-3500-AMD 'Manual Stored Ticket TST Creation and Processing' for additional information on
the 'PNR CHNG' flag process.
A02-3279 - 03/07/17 - 5
Chapter 9. General Data and Processing at Ticketing Time
At TTP time, Global Core checks first the Credit Indicator (CREDI) stored in the SIA Line of the TST.
If CREDI is equal to N (Credit payment not allowed), and a Credit form of payment is found in PNR, then the
system displays the following error message :
CREDITCARDNOTVALIDFORTHISNEGOTIATEDFARE
The Form Of Payment validation is performed against the Selling Fare which is the fare displayed in the TST.
Refer to A02-4200 Form Of Payment Validation for additional information on the FOP validation.
9.2. Commission Processing at TTP Time
9.2.1. Principle
A Negotiated Fare TST is a TST with a Pricing Code F, G or B .
A negotiated fare TST is subject to specific commission processing which may override or generate the FM
element depending on the form of payment.
Actually, in case of IT/BT tickets, the ticket has to be printed and reported at Net Fare level that is the amount
the travel agent has to pay to the airline (probably reduced by a normal commission).
If that ticket is paid with a credit card, the system has to ticket it an report it with the credit card amount which
is in fact the Selling fare (bigger than the Net fare), an therefore the amount that the Airline is going to
receive directly from the passengers credit card company. That is not in the interest of the travel agent which
is expecting to receive the difference between the Selling fare and the Net fare, in addition to his normal
commission calculated on the Net fare.
In this case, the system has to recalculate the commission that it will use to store in the AIR for ticketing, by
increasing the normal commission already given by the fare quote at pricing time and stored in the TST.
Depending on the type of the TST to ticket (Old or New), the system may have to edit the PR Line (for Old
TSTs) or the SIA Line (for New TSTs), to look for Negotiated Fare Commission Data.
12345678
(PR)(CAR)(/)(VC){*PC*}(FMdata)(/)PRdata)
The systems may have to check the existence of valid FM data according to the format described in
Section 5.1.
12345678910111213
SIA/si/comv/comi/scomv/scomi/credi/reml/tour/ftext/car/vc
The system may have to use the SIA Line and determine the FM data according to the process
described in Chapter 6.
9.2.3. System Processing
a. If TST Pricing Indicator is B and a PNR FM element exists which is neither FM *F* nor FM *G*,
then the system uses this FM data as input for the process Commission Re-calculation for Credit
Payment, and uses the output of this process to create the PNR FM element (AIR FM Line).
b. In any other cases, the system edits the PR Line to check if any FM data exists according to the
process described in Chapter 6. Use the FM data found in the PR Line as input for the process
Commission Re-calculation for Credit Payment , and uses the output of this process to create the
PNR FM element (AIR FM Line).
c. If no FM found in the PR Line, then use 0% as input for the process Commission Re-calculation
for Credit Payment, and use the output of this process to create the AIR FM Line.
d. This concludes commission processing for the transaction and no further steps in the commission
process are performed.
b. Edit the PR Line to check if any FM data exists. If FM data exists, the system uses it, as it is, to
create the AIR FM Line.
c. Check if an FM element exists in the PNR. If exists, use it, as it is, to create the AIR FM Line. This
concludes commission processing for the transaction and no further steps in the commission
process are performed.
d. If no FM element found in the PNR, then the system checks the Commission Control Indicator (CCI)
in the Office Profile
e. If the CCI is equal to NONE, then the system concludes commission processing for the transaction
and no further steps in the commission process are performed.
f. If the CCI is not equal to NONE the commission is then subject to Table Processing (as described
in A02-4205 Commission Tables and Processing).
b. In any other cases, the system edits the SIA Line to check if any FM data exists according to the
process described in Chapter 6. Use the FM data found in the SIA Line as input for the process
Commission Re-calculation for Credit Payment , and uses the output of this process to create the
AIR FM Line.
c. If no FM found in the SIA Line, then use 0% as input for the process Commission Re-calculation
for Credit Payment, and use the output of this process to create the AIR FM Line.
d. This concludes commission processing for the transaction and no further steps in the commission
process are performed (i.e. no Table Processing).
a. If the FM element found in the PNR had been generated by Nego Pricing (FM*F* or FM*G*), it is
used to create the AIR FM Line. This concludes the commission processing.
b. If NO FM*F* or FM*G* is found, then the system checks the Commission Control Indicator (CCI) in
the Office Profile
c. If the CCI is equal to NONE, then the system concludes commission processing for the transaction
and no further steps in the commission process are performed.
d. If the CCI is not equal to NONE, the commission is then subject to Table Processing (as described
in A02-4205 Commission Tables and Processing).
Depending on from where this process in invoked, the input commission data for this process may
be :
2- Output data :
This process applies in case of first issue of Negotiated Fare TST (a TST for first issue has the issue
indicators F, I or U).
If there is NO credit card form of payment for the TST then the system recreates the FM element
using the input commission data with *F* flag..
A generic process is designed to cover first issue transactions as well as exchange transactions.
Thus the system calculates D, which represents the possible value of the old ticket in case of
exchange. Obviously, D is equal to zero in case of first issue.
The computation of D varies between NON US markets and US Market, since the exchange process
is different in the US Market :
- For NON US Markets, D is the difference between the selling fare and the total Selling
fares without taxes and OB fees:
D=BC
where B is the Base amount of the old ticket, and C the Cancellation amount, taken from the
FO PNR element. e.g. :
FO0011234567890MIA13APR96*B100.00/X15.00/C20.00
If C is not entered in the FO PNR line, it takes the value of zero in the formula.
If B and C amounts are not entered in the FO PNR Line then the system takes :
a. If the (Credit Amount New Taxes New OB fees) is less than or equal to (Net Fare
D), then the system recreates the FM element using the input commission data. If no
commission have been found, an FM *F* 0 is generated.
b. If the (Credit Amount New Taxes New OB fees) is greater than (Net Fare D), a
commission calculation is done to recreate an FM element. (Note that the FM data -FM
% and FM amt- in the calculations is that contained in the input commission data) :
[(CC amt new taxes new OB fees) (Net Fare D (Net Fare * FM%))] / (CC amt new taxes
new OB fees) * 100 = FM %
e.g.
If the credit card amount is 1010, tax sum is 10, input commission data is 5%, the
Net Fare is 1100, the Selling Fare is 1200 and the Selling Total is (changed to) 1010,
then :
(CC amt new taxes new OB fees) (Net Fare D FM amount) = new FM amount
e.g.
If the credit card amount is 1010, tax sum is 10, input commission data is 55.00A,
the Net Fare is 1100, the Selling Fare is 1200 and the Selling Total is (changed to)
1010, then :
D = 1200 (1010 10) = 200 .
(1010 10) (1100 200 55) = 1000 845 = 155 = New FM amount
The newly created FM element is attributed the commission type *G* and, in case of new TST only,
replaces any existing PNR FM element.
See A02-4205 Amadeus Central Ticketing : Commission Tables and Processing, for further details.
4- Processing at reissue:
This processing applies for all types of FOP and on all the markets, in case of reissue of a
Negotiated TST (a TST for reissue has the issue indicators R, Y or W). If a commission has been
found at reissue, it is kept by the system.
If no commission has been found at reissue, an FM *F* 0 is generated.
At TTP time, if the AVN (Air Version Number) = 00205, and the booked TST is not New Nego, then ticketing
should be rejected with:
OLD NEGO TST NOT SUPPORTED FOR AIR VERSION: PLEASE REPRICE
(En Francais: ANCIENNE TST NEGO NON SUPPORTEE POUR VERSION AIR: MERCI DE RETARIFER)
Chapter 10. AIR Creation
TTP
N Y
NEW
TST
N Y
Data- Data-
format = format =
NEW (*) NEW (*)
Y N
CCI=NONE
(*) Data-format is NEW or OLD depending on the result of the algorithm described in Section 2.5.
10.2. K- Lines
The possibility exists to build and send three K- lines in the AIR. Each line has a unique tag as follows :
a- The published fare is identified by 'K-' and is always the first line.
If no published fare exists, then this line contains a 'Carriage return' sign.
b- The Net Fare is identified by 'KN-' and is always the second line.
c- The Selling Fare is identified by 'KS-' and is always the third line.
2- IATA Standard :
a- The published fare is identified by 'KFL-' and is always the first line.
If no published fare exists, then this line contains a 'Carriage return' sign.
b- The Net Fare is identified by 'KNL-' and is always the second line.
c- The Selling Fare is identified by 'KSL-' and is always the third line.
The "F", G or B Pricing Code is sent in the C-Line ('Servicing Carrier Line') of the AIR.
Refer to 'TP002-M030 : Amadeus Edifact Conventions and Directory' for additional information on the K-
Lines, L-Line and SIA-Line format.
10.3. AIR - 1 . Create OLD Format AIR From OLD TST
12345678
(PR)(CAR)(/)(VC){*PC*}(FMdata)(/)PRdata)
In this case the AIR should be created with manual M Pricing Code in the C- Line, and all Nego data are lost.
L- Line is created directly from the PR line.
In this case the AIR should be created with manual M Pricing Code in the C- Line, and all Nego data are lost.
L- Line is created directly from the PR line.
FT Line and FV Line should be created in the AIR from the PNR/TST without any *F* flags.
123456
{L}(FTdata){*PC*}(FMdata)(/)(PRdata)
Example :
LCAR1234/D1250*LH*FM12.5/VALIDONLHONLY
CASE AIR 3
CASE AIR 4
The AIR FT Line is created from the PNR FT element without *F* indicator.
Example :
Input PNR FT element : FT *F* ABCDEF
Output AIR FT Line : FT ABCDEF
10.6. AIR 5 . Create NEW Format AIR From NEW TST
1234
{SIA}{i}<;r><;xxxxxxx>
Where :
3 = Remittance Level : optional and can only be N or S or blank, has to be taken from REML field of the TST
SIA Line.
4 = Fare box Text : 7 alphanumeric, has to be taken from the FTEXT field of the TST SIA line.
SIA/N/12.5/////N///CAR12345/D10000/
SIAN;N;
Example IT:
SIA/I/12.5///////BULK///
SIAI;;BULK
SIA/F/12.5//////////
- OUTPUT : AIR SIA Line
SIAF;;
10.7. Examples
AMD1900000041
1A549027;1A549027
MUC1AKRTPO5;0101;BOMI22TKT;14999913;BOMI22TKT;14999913;;;;
AAIRINDIA;AI0980
BTTP/CRT
C7906/AASUAASUFN
D980619;980619;980619
GX;SITI;BOMBOM;
H001;002OBOM;MUMBAI;CGK;JAKARTAINTL;AI0476YY02SEP0225A
0120P02SEP;OK01;S;2;310;;;23K;2;;;0925;
H002;003OCGK;JAKARTAINTL;BOM;MUMBAI;AI0475YY09SEP0230P
1020P09SEP;OK01;S;2;310;;;23K;2;;;0920;
KFINR20000;;;;;;;;;;;;INR20500;
KFTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
KNFINR10000;;;;;;;;;;;;INR10500;
KNTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
KSFINR15000;;;;;;;;;;;;INR15500;
KSTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
TAXINR500FT;;;
LCAR12345/D10000*SR*FM12.5/VALIDONSRONLY
MTEST16;TEST16
NNUC249.32;249.32
OXXXX;XXXX
QBOMAIJKT249.32AIBOM249.32NUC498.64ENDROE40.10750
I001;01HBNEGO/TEST;;
T
FPCASH
FVAI
TKOK19JUN/BOMI22TKT
ENDX
ZFOPINCASH;SN1;TPCA;AMINR15500
ZST002;AI0476HK01;AI0475HK01;
10.7.2. NEW FORMAT A.I.R
AMD1900000041
1A549027;1A549027
MUC1AKRTPO5;0101;BOMI22TKT;14999913;BOMI22TKT;14999913;;;;
AAIRINDIA;AI0980
BTTP/CRT
C7906/AASUAASUFN
D980619;980619;980619
GX;SITI;BOMBOM;
H001;002OBOM;MUMBAI;CGK;JAKARTAINTL;AI0476YY02SEP0225A
0120P02SEP;OK01;S;2;310;;;23K;2;;;0925;
H002;003OCGK;JAKARTAINTL;BOM;MUMBAI;AI0475YY09SEP0230P
1020P09SEP;OK01;S;2;310;;;23K;2;;;0920;
KFINR20000;;;;;;;;;;;;INR20500;
KFTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
KNFINR10000;;;;;;;;;;;;INR10500;
KNTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
KSFINR15000;;;;;;;;;;;;INR15500;
KSTF;INR500FTAD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
TAXINR500FT;;;
SIAN;N;
LVALIDONSRONLY
MTEST16;TEST16
NNUC249.32;249.32
OXXXX;XXXX
QBOMAIJKT249.32AIBOM249.32NUC498.64ENDROE40.10750
I001;01HBNEGO/TEST;;
T
FM*G*50;S23;P1
FT*F*CAR12345/D10000
FPCASH
FV*F*AI
TKOK19JUN/BOMI22TKT
ENDX
ZFOPINCASH;SN1;TPCA;AMINR15500
ZST002;AI0476HK01;AI0475HK01;
Chapter 11. Specific Data and Processing Requirements
The BSP FR authorizes two types of Negotiated Fares, the Net Remit fares (NR) and the IT fares (NF).
For both of them there are also two options, known as option 1 and option 2, that will be detailed in the next
Chapter.
We consider that the SIA line provided by the New Nego application has the following format:
SIA/SI/COMV/COMI/SCOMV/SCOMI/CREDI/REML/TOUR/FTEXT/CAR/VC/
The following scheme indicator (SI) values are applicable to the BSP FR:
A : IT with NR flag
N : Net Remit
For these two SI values the following combinations will be allowed, based on the Option:
Examples:
NR fare option 1:
Input: SI N
CREDI N
CAR NR12345
VC blank
Output: PNR FT element FT*F*NR12345
NR fare option 2:
Input: SI N
CREDI blank
CAR NR12345
VC TM0700
Output: PNR FT element FT*F*NR12345/TM0700
IT fare option 1:
Input: SI A
CREDI N
FTEXT IT
CAR IT9AF12345
VC blank
Output: PNR FT element FT*F* IT9AF12345
AIR SIA line SIAA;;IT
IT fare option 2:
Input: SI N
CREDI blank
FTEXT IT
CAR IT9AF12345
VC TM0700
Output: PNR FT element FT*F* IT9AF12345/TM0700
AIR SIA line SIAA;;IT
TST:
TTI/NF-1000 Net Fare Amount
2000 Published Amount (NR) or
1500 Selling Amount (IT)
50 Taxes
PNR:
FPNR+CASH 1550 Selling Amount + Taxes
FTIT0AF1234
TTP
TTPRET
AEBA = 1000
NRID = NR
COTP = blank
CORT =0
TDAM = 1050 AEBA + Taxes
FPTP (1) = CASH
FPAM (1) = 1050 Net Amount + Taxes
FPTP (2)_ = NR only for NR with Published
FPAM (2) = 1000
APBC = 1550 Selling Amount + Taxes
NEGO NR or IT option 1: : (this option disallows CC)
TST:
2000 Published Amount (for NR only)
1500 Selling Amount
1000 Net Amount
50 Taxes
PNR:
FP CASH 1550 Selling Amount + Taxes
FT*F*IT0AF1234
TTP
TTP
RET
AEBA = 1000
NRID = NR
COTP = blank
CORT =0
TDAM = 1050 AEBA + Taxes
FPTP (1) = CASH
FPAM (1) = 1050 Net Amount + Taxes
FPTP (2)_ = NR only for NR with Published
FPAM (2) = 1000
APBC = 1550 Selling Amount + Taxes
Manual NR or IT option 2
TST:
TTI/NF- 1000 Net Fare Amount
2000 Published Amount (NR) or
1500 Selling Amount (IT)
50 Taxes
PNR:
FPNR+CASH 1550 Selling Amount + Taxes
FTIT0AF1234/TM0700
TTP
TTPRET
AEBA = 1500
NRID = NR
COTP =N when there is a TM
CORT = 0700
TDAM = 1550 AEBA + Taxes
FPTP (1) = CASH
FPAM (1) = 1550 Net Amount + Taxes
FPTP (2)_ = NR only for NR with Published
FPAM (2) = 500
APBC = 1550 Selling Amount + Taxes
Nego NR or IT option 2
TST:
2000 Published Amount (for NR only)
1500 Selling Amount
1500 Net Amount
50 Taxes
PNR:
FP CASH 1550 Selling Amount + Taxes
FT*F*IT0AF1234/TM0700
TTP
TTP
RET
AEBA = 1500 (Net Amount = Selling)
NRID = NR
COTP = N when there is a TM
CORT = 0700
TDAM = 1550 AEBA + Taxes
FPTP (1) = CASH
FPAM (1) = 1550 Net Amount + Taxes
FPTP (2)_ = NR only for NR with Published
FPAM (2) = 500
APBC = 1550 Selling Amount + Taxes
11.3. KL, MP and KQ ATO/CTO Net Remit specifics
Those specifics are available for KL, MP, and KQ ATO/CTO only.
In case of Manual Net Remit, and for first issue only, where the input
The currency associated to the amount entered in the NF line of the TST, the one of the
FPNR input, and the one associated to the total amount of the TST (those currency checks
are already performed by default by the system at TTP time, as described in the
A02TKT3501B Chapter 6: SPECIFIC TTP PROCESSING FOR KL, MP and KQ ATO/CTO)
Note: in case of panel TST, if the currency code has not been manually entered in the FPNR and
NF fields, the system will consider the default currency code as filled in the DFC office profile
field(ref A0TST3500). In this mode, the currency is not displayed in the main panel, but is
available for the check. You can see it in the tax panel if needed
The amount entered in the FPNR input, and the amount of the NF line of the TST adding the
taxes.
Example:
TST:
TTI/NF-EUR1000 Net Fare Amount of 1000 EUR
2000 EUR Published Amount (NR)
50 EUR Taxes
PNR:
FPNR+CASH/EUR1050 Net fare amount + Taxes = Selling
Chapter 12. Central Ticketing Server - Incentive Ticketing
12.1. Introduction
What happens to the money a passenger pays for a ticket ? How much does the selling agent earn from the
sale - and how much gets paid back to the provider of the services which the ticket entitles the passenger to
use ? How is this division of the passengers money determined, who does it, and what is aMaDEUS role in
the process?
Most people are familiar with the concept that an agency sells tickets on behalf of a provider in order to earn
commission. In the majority of cases a commission percentage (agreed with the provider) ensures that the
selling agency receives a portion of the fare paid by the customer/passenger.
This is the standard incentive offered by providers to induce agencies to sell tickets on their behalf. In the
drive for increased ticket sales, however, incentives are becoming more sophisticated in their design and
application, so that although the essential principle remains the same (commission to the agency and/or
lower selling prices to increase volume of ticket sales and hence commission for the agency) the process of
ticketing is becoming more complex.
This document aims to provide a brief guide to aMaDEUS ticketing functionality in the area of incentive
ticketing
1. Incentive Ticketing - refers NOT to a separate type of ticketing but to a particular aspect of ticketing i.e.
that aspect which induces an agent to sell a ticket on behalf of a provider - the part concerned with the
generation of commission for the selling agent.
2. Incentive Ticketing Scheme - a single method of commission generation for the selling agent.
3. Settlement - the process of correctly attributing the amount due to the selling agent and the amount due
to the service provider from the sale of a ticket.
Note there are many incentive schemes and settlement processes that exist directly between providers and
agencies or between airlines and their ATO/CTO locations which are outside the scope of this document
since they remain more or less transparent to aMaDEUS.
12.2. GENERIC Processing
IF SI = I OR B OR A OR C
Then
IF ARP = FR
Then
IM = Nego IT for FR.
Else
IM = Nego IT/BT.
End
IF SI = N
Then
IF ARP = FR
Then
IM = Nego NR method for FR
Else IF VC = blank (no value code) AND
SCOMV = blank (no supplementary commission usage) AND
REML = N (Net fare reflected in remittance area)
Then
IM = Nego NR method 2A/2E/6A/6E
End
End
End
IF issue indicator is I U Y or W
Then
IF ARP = FR
Then
IM = agent IT for FR
Else
IM = agent IT/BT
Else
IF FPNR exists in PNR
Then
IF AEBA > 0
Then
IF IM = Agent NR method 2A/2E/6A/6E
Then
T_ADJ = AEBA (K-TOTAL K-NEW-TAXES)
R_ADJ = 0
Else (IM = Nego NR method 2A/2E/6A/6E)
T_ADJ = AEBA (KSTOTAL KS-NEW-TAXES)
R_ADJ = K-FARE/EQUIV KS-FARE/EQUIV
End
Else (AEBA = 0)
IF IM = Nego IT/BT
Then
T_ADJ = KN-FARE/EQUIV KS-FARE/EQUIV
R_ADJ = KN-FARE/EQUIV KS-FARE/EQUIV
Else
IF data source = Agent
Then
T_ADJ = 0
R_ADJ = 0
Else (data source = Nego)
T_ADJ = K-FARE/EQUIV KS-FARE/EQUIV
R_ADJ = K-FARE/EQUIV KS-FARE/EQUIV
End
End
End
12.2.4. CTS establishes Values of NR_TOT, CASH_TOT, CRED_TOT; TAX_TOT
- CASH_TOT is the sum of the values attributed to any cash FOPs and any MS FOPS (with a CA
billing code) in the Z-FOP line
- CRED_TOT is the sum of the values attributed to any credit FOPs and any MS FOPS (with a CC
billing code) in the Z-FOP line
- TAX_TOT is the sum of the values attributed to the K-TAXA fields OR (if no K-Line data) the KN-
TAXA fields
12.2.5. CTS Ticket Print Module
12.2.5.1. Remittance Area
Lets note that these calculations will be skipped for the BSP France (ARP-FR)
Based on the derived values (NR_TOT, CASH_TOT, CRED_TOT, TAX_TOT), the following algorithm can
be used to print the cash and credit collection amounts in the Remittance Area of the ticket:
1 - If indicator = 2 or 3, then
if CC_TOT is not = 0
then
Credit collection = CRED_TOT - TAX_TOT
if Z >= 0
then
Cash collection = Z
Else (Z < 0)
Cash collection = 0
end
else (CC_TOT = 0)
refer to processing 2 below.
end
if Z>= TAX_TOT
then
Cash collection = Z - TAX_TOT
Credit collection = CRED_TOT
else (Z < TAX_TOT)
Cash collection = 0
if Z >= 0
then
Credit collection = CRED_TOT - (TAX_TOT - Z)
else (Z < 0)
Credit collection = CRED_TOT - TAX_TOT
End
End
3 - If indicator = 4 or 5 or 6 or 7, then
This box should show the data contained in the FT line of the AIR.
The system must ignore the indicator *F* if exists.
These box should show the data contained in the FR element of the SIA Line of the AIR.
Example :
SIA Line : SIAI;;FORFAIT
Based on the derived values above, the following algorithm can be used to report the correct values for
AEBA, FPAM(ca), and FPAM(cc) :
- AEBA = the AEBA value passed by the CTS (which has calculated it)
Lets note that the following calculations will be skipped for the BSP France (ARP-FR)