UG WBS Fare MasterPricerTravelBoardSearch 16.1

Web Services User's Guide
Fare_MasterPricerTravelBoardSearch
16.1
Amadeus SAS
485, Route du Pin Montard
BP 69
06902 Sophia-Antipolis Cedex
Table of Contents
Table of Contents
Preface................................................................................................................................ 18
1 Purpose of this document............................................................................................18
2 Intended Audience....................................................................................................... 18
3 Associated Documents................................................................................................ 18
4 Structure of this document...........................................................................................18
Function: Fare_MasterPricerTravelBoardSearch................................................................20
1 Overview...................................................................................................................... 20
1.1 Supported Operations........................................................................................... 22
1.2 Limitations..............................................................................................................29
1.3 Unsupported Operations....................................................................................... 29
1.4 Prerequisites..........................................................................................................30
2 Building A Query..........................................................................................................31
3 Receiving A Reply....................................................................................................... 36
3.1 Reply Sub Structure: Free Baggage Allowance 1 - freeBagAllowanceGrp........... 70
3.1.1 Description................................................................................................................................... 70
3.1.2 Xml Structure............................................................................................................................... 70
3.2 Reply Sub Structure: Free Baggage Allowance 2 - serviceCoverageInfoGrp..... 71

3.2.1 Description................................................................................................................................... 71
3.2.2 Xml Structure............................................................................................................................... 71
3.3 Reply Sub Structure: Free Baggage Allowance 3 - segmentFlightRef..................72

3.3.1 Description................................................................................................................................... 72
3.3.2 Xml Structure............................................................................................................................... 72
4 Error Messages............................................................................................................74
4.1 Error Reply............................................................................................................ 78
5 Operations....................................................................................................................79
5.1 Operation: 01 - Search With Mandatory Elements............................................... 79
5.1.1 Query Structure........................................................................................................................... 82
5.1.2 Reply Structure............................................................................................................................ 83
5.1.3 Possible Errors............................................................................................................................ 83
i
Table of Contents
5.2 Operation: 02.01 Flight Option - Airline/Alliance (Include/Exclude).......................87

5.2.1 Query Structure........................................................................................................................... 87
5.2.2 Reply Structure............................................................................................................................ 89
5.2.3 Possible Errors............................................................................................................................ 89
5.3 Operation: 02.02 Flight Option - Flight Category.................................................. 91

5.3.1 Query Structure........................................................................................................................... 92
5.3.2 Reply Structure............................................................................................................................ 93
5.3.3 Possible Errors............................................................................................................................ 93
5.4 Operation: 02.03 Flight Option - Connection Point............................................... 94

5.4.1 Query Structure........................................................................................................................... 96
5.4.2 Reply Structure............................................................................................................................ 97
5.4.3 Possible Errors............................................................................................................................ 97
5.5 Operation: 02.04 Flight Option - Multicity............................................................. 98

5.5.1 Query Structure......................................................................................................................... 100
5.5.2 Reply Structure.......................................................................................................................... 101
5.5.3 Possible Errors.......................................................................................................................... 101
5.6 Operation: 02.05 Flight Option - Origin Destination Area................................... 103

5.6.1 Query Structure......................................................................................................................... 105
5.6.2 Reply Structure.......................................................................................................................... 106
5.6.3 Possible Errors.......................................................................................................................... 106
5.7 Operation: 02.06 Flight Option - No Slice and Dice............................................108

5.7.1 Query Structure......................................................................................................................... 108
5.7.2 Reply Structure.......................................................................................................................... 109
5.7.3 Possible Errors.......................................................................................................................... 109
5.8 Operation: 02.07 Flight Option - Disable Biased Preference.............................. 110

5.8.1 Query Structure......................................................................................................................... 110
5.8.2 Reply Structure.......................................................................................................................... 111
5.8.3 Possible Errors.......................................................................................................................... 111
5.9 Operation: 02.081 Flight Option - Ticketless Access Carriers recommendation.. 112
5.9.1 Query Structure......................................................................................................................... 112
5.9.2 Reply Structure.......................................................................................................................... 114
5.9.3 Possible Errors.......................................................................................................................... 125
ii
Table of Contents
5.10 Operation: 02.082 Flight Option - Exclude Ticketless Access Carriers............. 126
5.10.1 Query Structure....................................................................................................................... 126
5.10.2 Reply Structure........................................................................................................................ 127
5.10.3 Possible Errors........................................................................................................................ 127
5.11 Operation: 02.09 Flight Option - Ignore Availability.......................................... 128

5.11.1 Query Structure....................................................................................................................... 128
5.11.2 Reply Structure........................................................................................................................ 128
5.11.3 Possible Errors........................................................................................................................ 129
5.12 Operation: 02.10 Flight Option - Number of Connections................................. 130

5.12.1 Query Structure....................................................................................................................... 130
5.12.2 Reply Structure........................................................................................................................ 131
5.12.3 Possible Errors........................................................................................................................ 131
5.13 Operation: 02.11 Flight Option - Online Option at Itinerary Level..................... 132
5.13.1 Query Structure....................................................................................................................... 132
5.13.2 Reply Structure........................................................................................................................ 133
5.13.3 Possible Errors........................................................................................................................ 133
5.14 Operation: 02.12 Flight Option - Online Option at Requested Segment Level...134
5.14.1 Query Structure....................................................................................................................... 134
5.14.2 Reply Structure........................................................................................................................ 135
5.14.3 Possible Errors........................................................................................................................ 135
5.15 Operation: 02.13 Flight option - Interline.......................................................... 136

5.15.1 Query Structure....................................................................................................................... 136
5.15.2 Reply Structure........................................................................................................................ 137
5.15.3 Possible Errors........................................................................................................................ 137
5.16 Operation: 02.14 Flight option - Maximum EFT................................................ 138

5.16.1 Query Structure....................................................................................................................... 138
5.16.2 Reply Structure........................................................................................................................ 139
5.16.3 Possible Errors........................................................................................................................ 139
5.17 Operation: 02.15 Flight option - Maximum layover per connection................... 140
5.17.1 Query Structure....................................................................................................................... 140
5.17.2 Reply Structure........................................................................................................................ 141
5.17.3 Possible Errors........................................................................................................................ 141
iii
Table of Contents
5.18 Operation: 02.16 Flight option - Total Maximum layover.................................. 142

5.18.1 Query Structure....................................................................................................................... 142
5.18.2 Reply Structure........................................................................................................................ 143
5.18.3 Possible Errors........................................................................................................................ 143
5.19 Operation: 02.17 Flight option - RDI: Radius/multicity at itinerary level............ 144
5.19.1 Query Structure....................................................................................................................... 144
5.19.2 Reply Structure........................................................................................................................ 145
5.19.3 Possible Errors........................................................................................................................ 145
5.20 Operation: 02.18 Flight option - IR: Radius/multicity at requested segment

level................................................................................................................................... 146
5.20.1 Query Structure....................................................................................................................... 146
5.20.2 Reply Structure........................................................................................................................ 147
5.20.3 Possible Errors........................................................................................................................ 165
5.21 Operation: 02.20 Flight option - No airport change at itinerary level................. 166
5.21.1 Query Structure....................................................................................................................... 166
5.21.2 Reply Structure........................................................................................................................ 167
5.21.3 Possible Errors........................................................................................................................ 167
5.22 Operation: 02.21 Flight option - No airport change at requested segment level. 168
5.22.1 Query Structure....................................................................................................................... 168
5.22.2 Reply Structure........................................................................................................................ 169
5.22.3 Possible Errors........................................................................................................................ 169
5.23 Operation: 02.22 Duplicated recommendations: Keep solutions with more ground
time at last connecting point............................................................................................ 170
5.23.1 Query Structure....................................................................................................................... 170
5.23.2 Reply Structure........................................................................................................................ 171
5.23.3 Possible Errors........................................................................................................................ 171
5.24 Operation: 02.23 Duplicated recommendations: Keep the best solutions per major
flight...................................................................................................................................172
5.24.1 Query Structure....................................................................................................................... 172
5.24.2 Reply Structure........................................................................................................................ 173
5.24.3 Possible Errors........................................................................................................................ 173
5.25 Operation: 02.24 Flight option - City or Airport Indicator at itinerary level......... 174
iv
Table of Contents
5.25.1 Query Structure....................................................................................................................... 174

5.25.2 Reply Structure........................................................................................................................ 175
5.25.3 Possible Errors........................................................................................................................ 175
5.26 Operation: 02.25 Flight Option - Anchored Search (Basic mode)..................... 176
5.26.1 Query Structure....................................................................................................................... 176
5.26.2 Reply Structure........................................................................................................................ 178
5.26.3 Possible Errors........................................................................................................................ 178
5.27 Operation: 02.26 Flight Option - Anchored Search (Full mode without technical
stop).................................................................................................................................. 179
5.27.1 Query Structure....................................................................................................................... 179
5.27.2 Reply Structure........................................................................................................................ 182
5.27.3 Possible Errors........................................................................................................................ 182
5.28 Operation: 02.27 Flight Option - Anchored Search (Full mode with technical
stops).................................................................................................................................183
5.28.1 Query Structure....................................................................................................................... 183
5.28.2 Reply Structure........................................................................................................................ 188
5.28.3 Possible Errors........................................................................................................................ 188
5.29 Operation: 02.28 Flight Option - More Overnights............................................ 189

5.29.1 Query Structure....................................................................................................................... 189
5.29.2 Reply Structure........................................................................................................................ 190
5.29.3 Possible Errors........................................................................................................................ 190
5.30 Operation: 02.29 Flight Option - Search with Point of Commencement............191

5.30.1 Query Structure....................................................................................................................... 191
5.30.2 Reply Structure........................................................................................................................ 192
5.30.3 Possible Errors........................................................................................................................ 192
5.31 Operation: 02.30 Flight Option - Search with CLID...........................................193

5.31.1 Query Structure....................................................................................................................... 193
5.31.2 Reply Structure........................................................................................................................ 195
5.31.3 Possible Errors........................................................................................................................ 200
5.32 Operation: 02.31 Flight Option - DK number (customer identification)..............201

5.32.1 Query Structure....................................................................................................................... 201
5.32.2 Reply Structure........................................................................................................................ 202
v
Table of Contents
5.32.3 Possible Errors........................................................................................................................ 202
5.33 Operation: 02.32 Flight Option - Progressive legs............................................ 203

5.33.1 Query Structure....................................................................................................................... 204
5.33.2 Reply Structure........................................................................................................................ 205
5.33.3 Possible Errors........................................................................................................................ 205
5.34 Operation: 03.1 Time Option - Time of Departure/Arrival................................. 206

5.34.1 Query Structure....................................................................................................................... 207
5.34.2 Reply Structure........................................................................................................................ 208
5.34.3 Possible Errors........................................................................................................................ 208
5.35 Operation: 03.2 Time Option - Time Window................................................... 209

5.35.1 Query Structure....................................................................................................................... 210
5.35.2 Reply Structure........................................................................................................................ 211
5.35.3 Possible Errors........................................................................................................................ 212
5.36 Operation: 03.3 Time Option - Range Of Dates............................................... 213

5.36.1 Query Structure....................................................................................................................... 214
5.36.2 Reply Structure........................................................................................................................ 215
5.36.3 Possible Errors........................................................................................................................ 215
5.37 Operation: 03.4 Time Option - Time at destination........................................... 216

5.37.1 Query Structure....................................................................................................................... 216
5.37.2 Reply Structure........................................................................................................................ 217
5.37.3 Possible Errors........................................................................................................................ 217
5.38 Operation: 04.01 Fare Option - Currency Conversion...................................... 218

5.38.1 Query Structure....................................................................................................................... 218
5.38.2 Reply Structure........................................................................................................................ 219
5.38.3 Possible Errors........................................................................................................................ 219
5.39 Operation: 04.02 Fare Option - Selling Ticketing Cities Override..................... 221
5.39.1 Query Structure....................................................................................................................... 221
5.39.2 Reply Structure........................................................................................................................ 222
5.39.3 Possible Errors........................................................................................................................ 223
5.40 Operation: 04.03 Fare Option - Price To Beat.................................................. 224

5.40.1 Query Structure....................................................................................................................... 224
5.40.2 Reply Structure........................................................................................................................ 225
vi
Table of Contents
5.40.3 Possible Errors........................................................................................................................ 225
5.41 Operation: 04.04 Fare Option - Split / No Split PNR.........................................227

5.41.1 Query Structure....................................................................................................................... 227
5.41.2 Reply Structure........................................................................................................................ 229
5.41.3 Possible Errors........................................................................................................................ 229
5.42 Operation: 04.05 Fare Option - Type of Ticket (Electronic/Paper Ticket)..........230

5.42.1 Query Structure....................................................................................................................... 230
5.42.2 Reply Structure........................................................................................................................ 231
5.42.3 Possible Errors........................................................................................................................ 232
5.43 Operation: 04.06 Fare Option - Unifare............................................................ 233

5.43.1 Query Structure....................................................................................................................... 234
5.43.2 Reply Structure........................................................................................................................ 235
5.43.3 Possible Errors........................................................................................................................ 235
5.44 Operation: 04.07 Fare Option - Expanded Parameter...................................... 236

5.44.1 Query Structure....................................................................................................................... 236
5.44.2 Reply Structure........................................................................................................................ 237
5.44.3 Possible Errors........................................................................................................................ 237
5.45 Operation: 04.08 Fare Option - My Search - Fare Families..............................239

5.45.1 Query Structure....................................................................................................................... 242
5.45.2 Reply Structure........................................................................................................................ 247
5.45.3 Possible Errors........................................................................................................................ 247
5.46 Operation: 04.09 Fare Option - Multi Office IDs - Default Distribution...............249
5.46.1 Query Structure....................................................................................................................... 250
5.46.2 Reply Structure........................................................................................................................ 251
5.46.3 Possible Errors........................................................................................................................ 257
5.47 Operation: 04.10 Fare Option - Multi Office IDs - Even Distribution..................260
5.47.1 Query Structure....................................................................................................................... 260
5.47.2 Reply Structure........................................................................................................................ 262
5.47.3 Possible Errors........................................................................................................................ 262
5.48 Operation: 04.11 Fare Option - Multi Office IDs - Weighted Distribution...........263
5.48.1 Query Structure....................................................................................................................... 263
5.48.2 Reply Structure........................................................................................................................ 266
vii
Table of Contents
5.48.3 Possible Errors........................................................................................................................ 266
5.49 Operation: 04.12 Fare Option - Identify YQ/YR tax amounts in Output.............267
5.49.1 Query Structure....................................................................................................................... 267
5.49.2 Reply Structure........................................................................................................................ 268
5.49.3 Possible Errors........................................................................................................................ 268
5.50 Operation: 04.13 Fare Option - Price only PTC................................................269

5.50.1 Query Structure....................................................................................................................... 269
5.50.2 Reply Structure........................................................................................................................ 270
5.50.3 Possible Errors........................................................................................................................ 270
5.51 Operation: 04.14 Fare Option - My Search - Distribution ratio of recommendations

per Fare Family................................................................................................................ 271
5.51.1 Query Structure....................................................................................................................... 271
5.51.2 Reply Structure........................................................................................................................ 273
5.51.3 Possible Errors........................................................................................................................ 274
5.52 Operation: 04.15 Fare Option - My Search - Resulting Fare Families at requested
segment level....................................................................................................................275
5.52.1 Query Structure....................................................................................................................... 275
5.52.2 Reply Structure........................................................................................................................ 277
5.52.3 Possible Errors........................................................................................................................ 277

per Fare Family at requested segment Level.................................................................. 279
5.53.1 Query Structure....................................................................................................................... 279
5.53.2 Reply Structure........................................................................................................................ 283
5.53.3 Possible Errors........................................................................................................................ 283

per Fare Family at requested segment level (Usage at itinerary level)............................ 285
5.54.1 Query Structure....................................................................................................................... 285
5.54.2 Reply Structure........................................................................................................................ 288
5.54.3 Possible Errors........................................................................................................................ 288
5.55 Operation: 04.18 Fare Option - Currency for Fare Selection option..................289
5.55.1 Query Structure....................................................................................................................... 289
5.55.2 Reply Structure........................................................................................................................ 290
5.55.3 Possible Errors........................................................................................................................ 290
viii
Table of Contents
5.56 Operation: 04.19 Fare Option - Currency for Fare Selection with Currency
Conversion option............................................................................................................. 291
5.56.1 Query Structure....................................................................................................................... 291
5.56.2 Reply Structure........................................................................................................................ 292
5.56.3 Possible Errors........................................................................................................................ 292
5.57 Operation: 04.20 Fare Option - Multi-Ticket......................................................293

5.57.1 Query Structure....................................................................................................................... 293
5.57.2 Reply Structure........................................................................................................................ 294
5.57.3 Possible Errors........................................................................................................................ 315
5.58 Operation: 04.22 Fare Option - Ticketing date................................................. 316

5.58.1 Query Structure....................................................................................................................... 316
5.58.2 Reply Structure........................................................................................................................ 317
5.58.3 Possible Errors........................................................................................................................ 317
5.59 Operation: 04.23 Fare Option - Solution Family............................................... 318

5.59.1 Query Structure....................................................................................................................... 318
5.59.2 Reply Structure........................................................................................................................ 319
5.59.3 Possible Errors........................................................................................................................ 331
5.60 Operation: 04.24 Fare Option - Disable Negotiated Space...............................332

5.60.1 Query Structure....................................................................................................................... 332
5.60.2 Reply Structure........................................................................................................................ 333
5.60.3 Possible Errors........................................................................................................................ 333
5.61 Operation: 04.25 Fare Option - Open Return................................................... 334

5.61.1 Query Structure....................................................................................................................... 334
5.61.2 Reply Structure........................................................................................................................ 335
5.61.3 Possible Errors........................................................................................................................ 353
5.62 Operation: 04.26 Fare Option - Alternate Price................................................ 354

5.62.1 Query Structure....................................................................................................................... 355
5.62.2 Reply Structure........................................................................................................................ 357
5.62.3 Possible Errors........................................................................................................................ 371
5.63 Operation: 04.27 Fare Option - Search by FBA................................................372

5.63.1 Query Structure....................................................................................................................... 372
5.63.2 Reply Structure........................................................................................................................ 373
ix
Table of Contents
5.63.3 Possible Errors........................................................................................................................ 374
5.64 Operation: 05.1 Cabin Option - Mandatory Cabin.............................................375

5.64.1 Query Structure....................................................................................................................... 376
5.64.2 Reply Structure........................................................................................................................ 377
5.64.3 Possible Errors........................................................................................................................ 377
5.65 Operation: 05.2 Cabin Option - Recommended Cabin..................................... 378

5.65.1 Query Structure....................................................................................................................... 378
5.65.2 Reply Structure........................................................................................................................ 379
5.65.3 Possible Errors........................................................................................................................ 379
5.66 Operation: 05.3 Cabin Option - Major Cabin.................................................... 380

5.66.1 Query Structure....................................................................................................................... 380
5.66.2 Reply Structure........................................................................................................................ 382
5.66.3 Possible Errors........................................................................................................................ 382
5.67 Operation: 06.1 Fee Option - Pricing Scheme Reference.................................383

5.67.1 Query Structure....................................................................................................................... 383
5.67.2 Reply Structure........................................................................................................................ 385
5.67.3 Possible Errors........................................................................................................................ 393
5.68 Operation: 06.2 Fee Option - Form of Payment............................................... 394

5.68.1 Query Structure....................................................................................................................... 394
5.68.2 Reply Structure........................................................................................................................ 396
5.68.3 Possible Errors........................................................................................................................ 396
5.69 Operation: 06.3 Fee Option - Sorting with/without Fees................................... 397

5.69.1 Query Structure....................................................................................................................... 397
5.69.2 Reply Structure........................................................................................................................ 398
5.69.3 Possible Errors........................................................................................................................ 398
5.70 Operation: 06.4 Fee Option - Exempt all airline ticketing fees.......................... 400
5.70.1 Query Structure....................................................................................................................... 400
5.70.2 Reply Structure........................................................................................................................ 401
5.70.3 Possible Errors........................................................................................................................ 401
5.71 Operation: 06.5 Fee Option - Add/Exempt airline ticketing fees by sub-code... 402
5.71.1 Query Structure....................................................................................................................... 402
5.71.2 Reply Structure........................................................................................................................ 404
x
Table of Contents
5.71.3 Possible Errors........................................................................................................................ 404
5.72 Operation: 06.6 Fee Option - Estimated FOP fees........................................... 405

5.72.1 Query Structure....................................................................................................................... 405
5.72.2 Reply Structure........................................................................................................................ 406
5.72.3 Possible Errors........................................................................................................................ 411
5.73 Operation: 07.1 Distribution Option - Airline Distribution: ADI...........................412

5.73.1 Query Structure....................................................................................................................... 412
5.73.2 Reply Structure........................................................................................................................ 413
5.73.3 Possible Errors........................................................................................................................ 413
5.74 Operation: 07.2 Distribution Option - Airline Distribution Container: ADC......... 414
5.74.1 Query Structure....................................................................................................................... 414
5.74.2 Reply Structure........................................................................................................................ 415
5.74.3 Possible Errors........................................................................................................................ 415
5.75 Operation: 07.3 Distribution option - Direct Distribution DDI.............................416

5.75.1 Query Structure....................................................................................................................... 416
5.75.2 Reply Structure........................................................................................................................ 417
5.75.3 Possible Errors........................................................................................................................ 417
5.76 Operation: 07.4 Distribution option - Not DDI: Deactivation of Direct

Distribution........................................................................................................................ 418
5.76.1 Query Structure....................................................................................................................... 418
5.76.2 Reply Structure........................................................................................................................ 419
5.76.3 Possible Errors........................................................................................................................ 419
5.77 Operation: 07.5 Distribution option - Deactivation of ADI distribution................420

5.77.1 Query Structure....................................................................................................................... 420
5.77.2 Reply Structure........................................................................................................................ 421
5.77.3 Possible Errors........................................................................................................................ 421
5.78 Operation: 07.6 Distribution option - Mono-Main Carrier Distribution................422

5.78.1 Query Structure....................................................................................................................... 422
5.78.2 Reply Structure........................................................................................................................ 423
5.78.3 Possible Errors........................................................................................................................ 423
5.79 Operation: 07.7 Distribution Option - Ratios for Weighted Recommendations.. 424
5.79.1 Query Structure....................................................................................................................... 424
xi
Table of Contents
5.79.2 Reply Structure........................................................................................................................ 425

5.79.3 Possible Errors........................................................................................................................ 426
5.80 Operation: 07.8 Distribution Option - Non-Stop Preferred................................ 427

5.80.1 Query Structure....................................................................................................................... 427
5.80.2 Reply Structure........................................................................................................................ 428
5.80.3 Possible Errors........................................................................................................................ 428
5.81 Operation: 08.01 Output Option - Empty Cells Clarification..............................429

5.81.1 Query Structure....................................................................................................................... 429
5.81.2 Reply Structure........................................................................................................................ 430
5.81.3 Possible Errors........................................................................................................................ 430
5.82 Operation: 08.02 Output Option - Rank in Journey Server............................... 431

5.82.1 Query Structure....................................................................................................................... 431
5.82.2 Reply Structure........................................................................................................................ 432
5.82.3 Possible Errors........................................................................................................................ 432
5.83 Operation: 08.03 Output Option - Value Search at itinerary level..................... 433
5.83.1 Query Structure....................................................................................................................... 434
5.83.2 Reply Structure........................................................................................................................ 436
5.83.3 Possible Errors........................................................................................................................ 450
5.84 Operation: 08.04 Output Option - Value Search at requested segment level... 451
5.84.1 Query Structure....................................................................................................................... 451
5.84.2 Reply Structure........................................................................................................................ 453
5.84.3 Possible Errors........................................................................................................................ 467
5.85 Operation: 08.05 Output Option - Display Minimum/Maximum Stay................. 468

5.85.1 Query Structure....................................................................................................................... 468
5.85.2 Reply Structure........................................................................................................................ 469
5.85.3 Possible Errors........................................................................................................................ 474
5.86 Operation: 08.07 Output Option - Fare Family information............................... 475

5.86.1 Query Structure....................................................................................................................... 476
5.86.2 Reply Structure........................................................................................................................ 477
5.86.3 Possible Errors........................................................................................................................ 485
5.87 Operation: 08.08 Output Option - Return flight duration at segment level.........486
5.87.1 Query Structure....................................................................................................................... 486
xii
Table of Contents
5.87.2 Reply Structure........................................................................................................................ 487

5.87.3 Possible Errors........................................................................................................................ 493
5.88 Operation: 08.09 Output Option - Commission returned...................................494

5.88.1 Query Structure....................................................................................................................... 494
5.88.2 Reply Structure........................................................................................................................ 495
5.88.3 Possible Errors........................................................................................................................ 503
5.89 Operation: 08.10 Output Option - Ticketing Point Mileage................................504

5.89.1 Query Structure....................................................................................................................... 504
5.89.2 Reply Structure........................................................................................................................ 505
5.89.3 Possible Errors........................................................................................................................ 509
5.90 Operation: 08.11 Output option - Return Airline Alliance.................................. 510

5.90.1 Query Structure....................................................................................................................... 510
5.90.2 Reply Structure........................................................................................................................ 511
5.90.3 Possible Errors........................................................................................................................ 515
5.91 Operation: 08.12 Output Option : Homegeneous Upsell...................................516

5.91.1 Query Structure....................................................................................................................... 522
5.91.2 Reply Structure........................................................................................................................ 524
5.91.3 Possible Errors........................................................................................................................ 524
5.92 Operation: 08.13 Output Option : Upsell per bound..........................................525

5.92.1 Query Structure....................................................................................................................... 531
5.92.2 Reply Structure........................................................................................................................ 533
5.92.3 Possible Errors........................................................................................................................ 533
5.93 Operation: 09.01 Output Option - Change Of Gauge....................................... 534

5.93.1 Query Structure....................................................................................................................... 548
5.93.2 Reply Structure........................................................................................................................ 549
5.93.3 Possible Errors........................................................................................................................ 549
5.94 Operation: 09.02 Output Option - Fare Calculation.......................................... 550

5.94.1 Query Structure....................................................................................................................... 550
5.94.2 Reply Structure........................................................................................................................ 551
5.94.3 Possible Errors........................................................................................................................ 567
5.95 Operation: 09.03 Output Option - Negotiated Space Availability Indicator........ 568
5.95.1 Query Structure....................................................................................................................... 568
xiii
Table of Contents
5.95.2 Reply Structure........................................................................................................................ 569

5.95.3 Possible Errors........................................................................................................................ 576
5.96 Operation: 09.04 Output Option - In-Flight Services......................................... 577

5.96.1 Query Structure....................................................................................................................... 577
5.96.2 Reply Structure........................................................................................................................ 578
5.96.3 Possible Errors........................................................................................................................ 581
5.97 Operation: 10.01 Ancillary Services option - Request All Fees.........................582

5.97.1 Query Structure....................................................................................................................... 582
5.97.2 Reply Structure........................................................................................................................ 583
5.97.3 Possible Errors........................................................................................................................ 583
5.98 Operation: 10.02 Ancillary Services option - Global pulled mode..................... 584
5.98.1 Query Structure....................................................................................................................... 584
5.98.2 Reply Structure........................................................................................................................ 585
5.98.3 Possible Errors........................................................................................................................ 585
5.99 Operation: 10.03 Ancillary Services option - Request a service sub-code........ 586
5.99.1 Query Structure....................................................................................................................... 586
5.99.2 Reply Structure........................................................................................................................ 587
5.99.3 Possible Errors........................................................................................................................ 587
5.100 Operation: 10.04 Ancillary Services option - Inclusion/Exclusion option......... 588

5.100.1 Query Structure..................................................................................................................... 588
5.100.2 Reply Structure...................................................................................................................... 589
5.100.3 Possible Errors...................................................................................................................... 589
5.101 Operation: 10.05 Ancillary Services option - pulled/pushed mode at sub-code

level................................................................................................................................... 590
5.101.1 Query Structure..................................................................................................................... 590
5.101.2 Reply Structure...................................................................................................................... 592
5.101.3 Possible Errors...................................................................................................................... 592
5.102 Operation: 10.06 Ancillary Services option - Service coverage option............593

5.102.1 Query Structure..................................................................................................................... 593
5.102.2 Reply Structure...................................................................................................................... 595
5.102.3 Possible Errors...................................................................................................................... 595
5.103 Operation: 10.07 Ancillary Services option - coverage option and pulled
mode................................................................................................................................. 596
xiv
Table of Contents
5.103.1 Query Structure..................................................................................................................... 596

5.103.2 Reply Structure...................................................................................................................... 597
5.103.3 Possible Errors...................................................................................................................... 597
5.104 Operation: 10.08 Ancillary Services option - Request a service group........... 598
5.104.1 Query Structure..................................................................................................................... 598
5.104.2 Reply Structure...................................................................................................................... 600
5.104.3 Possible Errors...................................................................................................................... 600
5.105 Operation: 10.09 Ancillary services option - Request a service sub-group.... 601
5.105.1 Query Structure..................................................................................................................... 601
5.105.2 Reply Structure...................................................................................................................... 603
5.105.3 Possible Errors...................................................................................................................... 603
5.106 Operation: 10.10 Ancillary services option - Request combining service group,
sub-group and sub-code...................................................................................................604
5.106.1 Query Structure..................................................................................................................... 604
5.106.2 Reply Structure...................................................................................................................... 606
5.106.3 Possible Errors...................................................................................................................... 606
5.107 Operation: 10.11 Ancillary Services option - Seat characteristic request........ 607
5.107.1 Query Structure..................................................................................................................... 607
5.107.2 Reply Structure...................................................................................................................... 609
5.107.3 Possible Errors...................................................................................................................... 609
5.108 Operation: 10.12 Ancillary Services option - Multi Passengers request.......... 610
5.108.1 Query Structure..................................................................................................................... 610
5.108.2 Reply Structure...................................................................................................................... 611
5.108.3 Possible Errors...................................................................................................................... 621
5.109 Operation: 10.13 Ancillary Services option - Combination of all possible

options...............................................................................................................................622
5.109.1 Query Structure..................................................................................................................... 622
5.109.2 Reply Structure...................................................................................................................... 625
5.109.3 Possible Errors...................................................................................................................... 625
5.110 Operation: 11.1 - OB fees with connections................................................... 626

5.110.1 Query Structure..................................................................................................................... 626
5.110.2 Reply Structure...................................................................................................................... 627
xv
Table of Contents
5.110.3 Possible Errors...................................................................................................................... 627
5.111 Operation: 12.0 Rail Option - Prohibit Rail solutions.......................................628

5.111.1 Query Structure..................................................................................................................... 628
5.111.2 Reply Structure...................................................................................................................... 629
5.111.3 Possible Errors...................................................................................................................... 629
5.112 Operation: 12.1 Passengers Ref - 1 adult with 1 infant.................................. 630

5.112.1 Query Structure..................................................................................................................... 630
5.112.2 Reply Structure...................................................................................................................... 631
5.112.3 Possible Errors...................................................................................................................... 631
5.113 Operation: 12.2 Passengers Ref - 1 adult with 1 infant and 1 child................ 632
5.113.1 Query Structure..................................................................................................................... 632
5.113.2 Reply Structure...................................................................................................................... 633
5.113.3 Possible Errors...................................................................................................................... 633
5.114 Operation: 12.3 Passengers Ref - 1 adult with 1 infant and 1 child, Passenger 3
with no age specified........................................................................................................634
5.114.1 Query Structure..................................................................................................................... 634
5.114.2 Reply Structure...................................................................................................................... 635
5.114.3 Possible Errors...................................................................................................................... 635
5.115 Operation: 13.1 Airline Fare Family name and description............................. 636
5.115.1 Query Structure..................................................................................................................... 638
5.115.2 Reply Structure...................................................................................................................... 639
5.115.3 Possible Errors...................................................................................................................... 650
5.116 Operation: 13.2 Airline Fare Family name and description............................. 651
5.116.1 Query Structure..................................................................................................................... 651
5.116.2 Reply Structure...................................................................................................................... 652
5.116.3 Possible Errors...................................................................................................................... 671
5.117 Operation: 14.0 Free Baggage Allowance...................................................... 672

5.117.1 Query Structure..................................................................................................................... 673
5.117.2 Reply Structure...................................................................................................................... 674
5.117.3 Possible Errors...................................................................................................................... 689
5.118 Operation: 14.1 Free Baggage Allowance with multiple passenger types.......690
5.118.1 Query Structure..................................................................................................................... 690
xvi
Table of Contents
5.118.2 Reply Structure...................................................................................................................... 692

5.118.3 Possible Errors...................................................................................................................... 703
5.119 Operation: 14.2 Baggage................................................................................ 704

5.119.1 Query Structure..................................................................................................................... 709
5.119.2 Reply Structure...................................................................................................................... 710
5.119.3 Possible Errors...................................................................................................................... 711
5.120 Operation: 15.1 Optional Data Profile............................................................. 712

5.120.1 Query Structure..................................................................................................................... 712
5.120.2 Reply Structure...................................................................................................................... 713
5.120.3 Possible Errors...................................................................................................................... 713
xvii
Web services User guide for function Fare_MasterPricerTravelBoardSearch
Preface
1 Purpose of this document
The purpose of this document is to provide basic functional overview descriptions and relevant examples for
a better understanding of the functions.
2 Intended Audience
This document is aimed at those who implement this function.
3 Associated Documents
This document has to be combined to its corresponding Technical Reference Guide and possibly to Product
specifications.
4 Structure of this document

This document is composed of the following parts:
the functional description: overview, supported operations, limitations, unsupported operations,
prerequisites and possibly reference to product specifications
the detailed description to build the query and to retrieve data from the reply
a set of relevant examples
Copyright 1987-2015 Amadeus IT Group SA.
Page 18 of 714
Fare_MasterPricerTravelBoardSearch
This function provides the ability to search the Amadeus fare system for lowest fare recommendations with
regards to specified trip requirements.
The parameterized fare families option is supported meaning that fare families can be defined at input time.
The Slice and Dice process is also supported meaning that Slice and Dice output is returned for the Search
function. The Slice and Dice process can be disabled by the No Slice and Dice option.
The Multi office id search process is also supported, meaning the userhas the ability to specify multiple Office
ids in addition to the Originator Office id.
Page 19 of 714
Function: Fare_MasterPricerTravelBoardSearch.
1 Overview
This function is designed to facilitate a wide range of options, ensuring that customers can narrow down or
broaden the fare search, in order to precisely match their request. The flexibility of this function provides the
potential to receive up to 200 trip recommendations, enabling web-based customers to easily navigate through
many choices.
A basic low fare search is composed of the following mandatory elements:
Itinerary geographical information (Origins/Destinations)
Itinerary date information
Passenger information (Number of passenger seats required and associated passenger type codes
for travelling passengers)
Number of Recommendations to be returned

In providing maximum flexibility to narrow or broaden the lowest fare search recommendations returned,
optional elements may be included in a request. Optional elements may apply to the flight search or fare search.
The ability to request segments for travel with optional filter parameters is provided and the system will return
recommendations of proposed segments making up a journey for the requested segments of an itinerary
with applicable price information. Thus, allowing the user to navigate through the list of recommendations to
determine the best choice for travel arrangements.
The following is a high level overview of this process:
Page 20 of 714
Page 21 of 714
1.1 Supported Operations

What is an "Operation"?
In this document, an "operation" describes, in general, a possible query scenario. More precisely, this operation
corresponds very often to the use of an option. However, in some cases, it describes a scenario that points
out to a feature that needs further clarification.
Search with Only Mandatory Elements
Specifying only the mandatory elements allows for the search possibilities of a specified date and city pair.
Itinerary Date
A date of travel must be specified for a low fare search query.
Origin / Destination
At least one origin and one destination must be specified for a low fare search query.
Passenger Information
Number of Passenger Seats
The number of seats required for the travelling passengers must be specified for a low fare search. This number
may not always be equal to the total number of passengers travelling.
For example, 3 adults and 1 infant, as an infant does not occupy a seat, this request requires only 3 seats
for 4 travelling passengers.
Associated Passenger Type Codes for Travelling Passengers
Each travelling passenger must be associated to a Passenger Type Code (PTC) for a low fare search.
Number of Recommendations
The user must specify the maximum number of recommendations to be returned.
Multi-Office id search process
The user can specify up to 19 Office ids in addition to the Originator Office id of the Originator Details segment,
within the same country and with the same modifier type. The system will then find the cheapest travel solutions
amongst all office ids requested in input (originator office id and additional office ids) without any preference.
Flight Convenience
The following criteria are applied to measure the convenience of each journey:
- The proportion of the Ground Time with regards to the Total Flying Time,
- The ratio between the Total Flying Time and the shortest possible flying time,
- The Overnight connections proportion regarding the other journeys.
If a journey fails against these criteria, it is considered as a Low Convenience Journey.
Page 22 of 714
In order to ensure a good overall journey convenience of the response, the Flight Convenience ensures that
the total number of returned Low Convenience journeys does not exceed 5% of the requested number of
recommendations.
Search with Optional Elements
Specifying additional optional elements in the search request will narrow the recommendations returned. The
more optional elements included in the search request, the more precise the search recommendations will be.
Flight Options
Airline (Include/Exclude)
The user has the ability to include and/or exclude up to 99 Airlines in the Low Fare Search using a 2alphanumeric characterairline code.
Flight Category
The user has the ability to request Non-Stop, Direct or Connecting flights or a combination of these categories.
Connecting Point
The user has the ability to include and/or exclude up to 2 connecting points for the requested Low Fare Search.
The user has also the ability to include up to 2 preferred connecting points.
Multicity
The user has the ability to specify up to 20 Cities or Airports as Origin and/or Destination of each Requested
Segment.
Origin/Destination Area
The user has the ability to extend the low fare search up to 300 kilometers surrounding the airport or city
specified for an origin or a destination. If an origin or destination area is specified, the low fare search process
may consider any city whose flying distance to the specified City or Airport is lower than the specified radius
in the query.
Ignore Availability
The user has the ability to ignore the real availability for flight selection: all returned booking codes are
considered as available.
Disable biased reference
When this option is requested, the flight search request is performed in neutral mode independently of the
office settings.
More overnights
The user has the ability to request more overnight solutions if they are part of the cheapest solutions.
No Slice and Dice
The user has the ability to disable Slice and Dice process with an option in the query.
Page 23 of 714
Exclude Low Cost Carriers
The user has the possibility via this option to exclude TLA Recommendations.
Online
This option forces the process to return online travel solutions only, even if cheaper recommendations mixing
carriers exist.
Interline option
The user has the ability to request only interline solutions, meaning recommendations built with flights marketed
by different carriers.
Anchored Search
The user has the ability to freeze one or more requested segments in input in order to get only recommendations
including those travel solutions. Full mode or basic mode is triggered by OID setting.
Point of commencement
The user can specify the real point of commencement when the first requested segment is not the real origin.
Progressive legs
Progressive legs enables the user to request a range of number of connections relative to the minimum
connections that exist on Journey Server.
Date/Time Options
Time of Departure/Arrival
Per requested segment, the user has the ability to specify one of the following:
- A time of departure: the earliest time that a recommended flight may "depart from".
- A time of arrival: the latest time that a recommended flight may "arrive by".
Both options cannot be used at the same time on the same requested segment.
Time Window
The user has the ability to specify an applicable time window range, in terms of hours, to a specified time by
departure or arrival option. Thus, allowing the low fare search to include any flight recommendations that arrive
or depart within the specified number of hours on either side of the specified time by departure or arrival.
Time at Destination
The time at destination is the minimum time between the arrival time and departure time of two consecutive
proposed segments. This minimum time is specified in input with the following format HHMM. Any value
between 0000 and 2359 is accepted.
Range of Date
The user has the ability to request that the low fare search to include the day before or the day after the date
specified for a trip segment.
Page 24 of 714
Fare Options
Currency Conversion
The user has the ability to specify in which currency the fare recommendations must be converted and returned.
Currency of Fare Selection
The user has the ability to only request recommendations with fare filed in a specified currency.
Selling/Ticketing Cities Override
The user has the ability to override the Selling and/or Ticketing Cities.
Price to Beat
The user has the ability to specify a "Price to Beat", a total amount (including taxes) for all passengers which
determines the most expensive recommendation that can be returned by the system.
Split / No Split PNR
The user is able to request that non-homogeneous recommendations are to be returned or not. Nonhomogeneous recommendations require to book passengers on several PNRs.
Paper Ticket / Electronic Ticket
This option offers to the user the capability to process: Paper Ticket only or Electronic Ticket only.
Unifares
By default the low fare searches are applicable only to public fares. However, the user can specify whether the
low fare search applies on Unifares only, on all Public and Unifare fares or Corporate fares.
Expanded Parameters
The user can specify Expanded Parameters that are used to target only some fares (refundable, without penalty,
and so on). Only valid expanded parameter options applicable: NAP, NPE, NR and RF.
My Search - Fare Families
By default any applicable fare can be returned, using My Search option the user can specify which fares are
of interest by using criteria like Fare Basis, Prime booking Code.
Solution Family Distribution
Travel Board solution family distribution is designed to cover the need to show a list of families of
recommendations for a specific itinerary on defined dates. A solution family refers to price results matching
predefined criteria as "Cheapest Recommendations" or "Non Stop".
Cabin Options
Page 25 of 714
The user has the ability to specify a desired cabin class for the requested itinerary. There is three different
flavours of process: Mandatory, Recommended and Major Cabin that are described in the corresponding
operations.
Price only PTC
The process returns strictly recommendations with the requested passenger type, no defaulting is done.
Alternate Price
This function allows returning for each recommendations belonging to the eligible Fare Family, the cheapest
available Alternate recommendation for the exact same journey and cabin.
Service Fees Options
Pricing Scheme reference
The user has the ability to specify a Pricing Scheme Reference for the calculation of a service fee by passenger
of a recommendation.
Form of Payment
A maximum of 3 forms of payment may be specified in the request.
Sorting with/without Fees
This option provides the possibility to sort recommendations in output based on an amount including fees or
excluding fees. It is applied for all passengers of the query.
Exempt all airline ticketing fees
Airline ticketing fees can all be exempted with this option. Add/Exempt airline ticketing fees by sub-code Airline
ticketing fees (OB fees) sub-codes can be specified in order to add or exempt particular fees.
Ancillary services Option
The user can request ancillary services.
Inpushed mode, all or preselected subset of applicable ancillary services and associated prices will be returned
in each recommendation but not considered in the search of the lowest fares. The pushed mode is set as the
default mode.
In pulled mode, all or preselected subset of ancillary services and associated prices are returned in each
shopping recommendations and considered in the search of the lowest fares.
Page 26 of 714
Distribution options
Airline Distribution: ADI
When this option is requested, the total number of Recommendations are distributed over 2 sets as the
following:
The Airline Diversity Set contains the cheapest recommendation for each online carrier and the cheapest
recommendation for each Mono-Main Carrier.
The Cheapest Recommendations Setcontains the cheapest recommendations matching the query that are
not included in the Airline Diversity recommendations set.
Airline Distribution Container: ADC
When this option is requested, the total number of recommendations are distributed over 2 sets as the following:
The Airline Diversity Container:Up to 25% of the Total Number of Recommendation is allocated to the airline
diversity.
The Cheapest Recommendations Setcontains the cheapest recommendations matching the query that are
not included in the Airline Diversity Container.
Non-Stop Preferred
When this option is requested, recommendations with non-stop flights will be favoured. The user has also the
possibility to modify the non-stop distribution weight.
Output options
Empty Cells Clarification
When this option is requested, a fictitious recommendation is returned with the corresponding reason for
segments and/or dates where no recommendation can be returned.
Rank in journey Server
Page 27 of 714
The user has the ability to request the display of the rank of the Flight Solution.
Multi-Ticket option
The Multi-Ticket option allows returning at the same time:

- Recommendations that require one single pricing transaction to be booked.
- Recommendations that require individual pricing transactions per Proposed Segment to be booked (the
search is done on the same office id for the whole itinerary).
Identify YQ/YR separately from other taxes
The purpose of this option is to return separately in the output the total amount of YQ/YR taxes per
recommendation and per passenger type.
Indian Taxes
This option details in the response message Indian tax amounts for each recommendation and for each type
of passengers.
Ticketing date
In order to avoid quoting a fare to a passenger that they are then unable to ticket at a later date, the user has
the ability to specify the intended ticketing date in the request.
This option ensures that the user will only receive recommendations that, if priced on the same day as the
query is received, are valid for ticketing on the future ticketing date specified in the request.
Fare Calculation
Depending of the office ID setting, the user has the ability to request the details of the entire fare calculation line.
Commission
Page 28 of 714
Depending of the office ID setting, the user has the ability to display the commission in percentage for each
fare basis.
Ticketing Point Mileage (TPM)
Depending of the office profile, the user has the ability to display the TPM at flight level.
Value Search
Depending of the criteria profile, the user has the ability to quote the more convenient solutions.
In-Flight Services
Depending of input option, the user has the ability to request the display of the in-flight services for each flight.
1.2 Limitations
The maximum number of recommendations in standard Master Pricer Travelboard is 250.
Range of Dates
It is currently not possible to request more than 1 day forward and/or 1 day backward for the searchable date
range.
Requested Segments
It is not possible to request more than 6 requested segments.
Number of Passengers
It is not possible to request more than 9 passengers.
My Search - Fare Families
It is not possible to request more than 6 fare families.
Multiple Office Ids
It is not possible tospecify more than 19 Office Ids.
1.3 Unsupported Operations

Longitude/Latitude
The ability to specify a search request with a longitude or latitude is not currently processed.
Page 29 of 714
Origin/Destination - Forced Location

The option to force a location to a city from a previously requested segment search result is not currently
processed. For example, 2nd requested departure city indicated to match the 1st requested arrival city of a
proposed segment.
Sequence Number - Overnight Not Allowed
It is currently not possible to indicate that flight combinations with over nights are not allowed for the low fare
search.
Therefore, the code OV is not supported.
1.4 Prerequisites
None
Page 30 of 714
2 Building A Query
Each query follows a given structure. The queries for the function operations are clearly explained with data
element examples in a generic table view.
It is important to note that the examples in each chapter are only illustrations and are meant to provide the
basis for a better understanding on which fields are mandatory for basic operation utilisation. In some cases it
is not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.
Considerations
When building a query it is important to understand the following concepts for the low fare search queries:
What is a Parameterized Fare Family ?
A Parameterized Fare Family is a set of specific parameters directly specified through the request. Up to 6
Parameterized Fare Families can be defined in the Master Pricer query. The parameterized Fare Family can
be combined with any other option as long as the request remains functionally coherent.
What is a Requested Segment?
A 'Requested Segment' is an Origin/Destination/Date segment of the travel requested in the query.
Examples:
CDG to JFK on 26 June,
CDG to JFK on 26 June or 27 June,
LON to BKK on 26 June,
LON or any airport within 100 km to BKK on any date between 26 June and 27 June,
LON to NCE/MRS/MCM ("Cote d'Azur") on any date between 26 June and 27 June.
What is an Itinerary?
An 'Itinerary' is the combination of all the Requested Segments in the order the passenger specified them.
Optional Parameters
The optional parameters may apply at the Requested Segment and/or Itinerary level.
Applicable Option Levels
The following table gives the rule for each option in terms of applicable levels.
Options
Applies toSegment
Applies toItinerary
Flight Options
Number of recommendations
Airline
Cabin
Time Window
Times Departure/Arrival
Connecting point
Expanded Parameter
Flight Category
X
X
Selling/Ticketing Cities
Radius (Origin/Destination areas)
X
X
X
Page 31 of 714
Multi-city
No Slice and Dice
Disabled Biased Reference
More overnights
Exclude Low Cost Carriers

Ignore Availability
Airline Distribution: ADI
Airline Distribution Container: ADC
Non-Stop Preferred
Online
Anchored Search
Point of commencement
Progressive legs
Fare Options
Passenger Type
Price to Beat
Unifares
Parameterized Fare Families
Split/No Split PNR
Currency Conversion
Paper Ticket/Electronic Ticket
Ticketability pre-check
Expanded Parameters
Withhold All Taxes/Surcharges
Service Fees: Pricing Scheme

reference
Multi-tickets
Form of payment
Adding/exempting specific airline

ticketing fees
Exempt all airline ticketing fees
Sorting with/without Fees
Multi Office IDs
Price only PTC
X
Page 32 of 714
Alternate Price
Date Options
Range of Dates
Output Options
Identify YQ/YR tax amounts
Empty Cells Clarification
Rank in Journey Server
Ancillary service fees
Value Search
Optional Data Profile
In-Flight services
X
The input validation of each option is described in the corresponding sections.
Option requested at both requested segment level and itinerary level
If an option applies at both Requested Segment and Itinerary levels and if the request is not rejected, as
specified in the description of the corresponding option paragraph, then the option specified at the Requested
Segment level takes precedence over the Itinerary option.
Examples:
Request
1st Requested
Segment
Process
2nd Requested
Segment
Itinerary
1st Requested
Segment
2nd Requested
Segment
Include Airlines: AA,

CO
Include Airlines: AA, Include Airlines: AA, Include Airlines: AA,

DL
CO
DL
Include Airlines: FL,

CO, YY
Exclude Airlines:
AA, DL
Include Airlines:
FL, CO eventually
combined with any
airline but AA, DL.
Exclude Airlines:
AA, DL
Possible Option Level Errors

Option Cannot be Applied at Requested Segment Level. If an option is only valid at the Itinerary level but the
user has specified it at the Requested Segment level, the entire entry is rejected with the following message:
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL"
Option Cannot be Applied at Itinerary Level
If an option is only valid at the Requested Segment level but the user has specified it at the Itinerary level, the
entire entry is rejected with the following message:
"OPTION CANNOT BE APPLIED AT ITINERARY LEVEL"
Page 33 of 714
Query Structures
The query samples provided in this document are in a table format to easily identify the different levels of
applicable information required in the function.
The repetitions of nodes in the samples provided are identified with brackets and numbers [n].
Each element of the function is explained with a query sample in the applicable sections of this document.
In some cases, the query sample contains only the information applicable to the discussed element. The
responsibility lies with the API developer to read the element sections for rules and combinability issues to
build the applicable messages desired.
As a guideline for the possibility of a more complex message structure, the sample query structure below is
given, identifying a low fare search requesting the following information:
Item #
Requested Information
0-1
Low Fare Search for 3 passengers
2-3
Requesting a maximum of 200 recommendations

returned
4-8
Passenger Types of 2 Adults and 1 Child
9 - 10
DL airlines are to be excluded from any

recommendations
11 - 16
1st requested segment:
Departing airport in Nice (NCE)
Arriving at any airport in the city of Houston

(HOU)
Time specified for arrival by 20 Feb 2004 at

5pm
17 - 22
2nd requested segment:
Departing any airport in city of Houston
Arriving at Nice airport NCE
Departure Date of 28 Feb 2004
Requesting both Non-Stop and Direct Flights

for the recommendations
Item #
SearchQuery - Data element
Value
/Segment/
3
unitNumberDetail[1] /numberOfUnits
/Segment/
unitNumberDetail[1] /typeOfUnit
/Segment/
200
unitNumberDetail[2] /numberOfUnits
/Segment/
unitNumberDetail[2] /typeOfUnit
RC
/paxReference[1]/ ptc
ADT
PX
Page 34 of 714
/paxReference[1]/traveller[1] /ref
/paxReference[1]/traveller[2] /ref
7a
/paxReference[2]/ ptc[1]
CH
7b
/paxReference[2]/ ptc[2]
MIL
/paxReference[2]/traveller /ref
/travelFlightInfo/
X
companyIdentity[2] /carrierQualifier
10
/travelFlightInfo/
companyIdentity[2] /carrierId
11
/itinerary[3]/
1
requestedSegmentRef /segmentRef
12
/itinerary[3]/departureLocalization/
departurePoint /locationId
NCE
13
/itinerary[3]/arrivalLocalization/
arrivalPointDetails /locationId
HOU
14
/itinerary[3]/timeDetails/
firstDateTimeDetail /timeQualifier
TA
15
firstDateTimeDetail /date
200204
16
firstDateTimeDetail /time
1700
17
/itinerary[4]/
2
requestedSegmentRef /segmentRef
18
/itinerary[4]/departureLocalization/
departurePoint /locationId
HOU
19
/itinerary[4]/arrivalLocalization/
arrivalPointDetails /locationId
NCE
20
firstDateTimeDetail /date
280204
21
/itinerary[4]/flightInfo/
flightDetail /flightType[1]
DL
22
/itinerary[4]/flightInfo/
D
flightDetail /flightType[2]
Referring to the applicable element sections of this document will provide any specific element information
required.
Page 35 of 714
3 Receiving A Reply
For each query requested, either an applicable error message or a valid response is returned. Applicable error
message information is provided under each element section within this document.
In case of a valid response, two cases occur. Either the reply message is truncated if it is too big or not.
In case of truncation, a flag is returned with the maximum size of the message (MSG:128k).
In case ancillary services are requested, and the reply message is too big and truncated, the ancillary service
details part appears at the end of the message even if the recommendations don't show any ancillary services.
The reply information will vary depending on the query information provided.
Considerations
When building a query it is important to understand the following concepts for the low fare search queries:
What is a Fare Family?
A Fare Family is a group of Fares sharing the same characteristics. Fare Family details can be defined as a
combination of the following elements, for example:
Publishing carrier
Type of fare (For example, Published, DDF, Amadeus Nego, ATP Nego)
Inclusion of one or several fare basis
Prime booking code

A combinability tag and a ranking are also provided.
The combinability tag prevents fare families from being combined.
The ranking is used to assign a resulting fare family in case where fare families are combined.
What is a Recommendation?
A "Recommendation" is the combination of a fare and its corresponding journeys that are returned as a possible
solution.
The journeys are divided and categorised under applicable fares making up the number of recommendations
requested in the query.
What is a Journey?
A "Journey" is a combination of Proposed Segments covering the requested Itinerary.
What is a Proposed Segment?
A "Proposed Segment" is a combination of flights that matches a Requested Segment. This may result in 3
connecting flights being considered as a single "Proposed segment".
Examples:
Request Segment
Proposed Segment
CDG to JFK on 26 June
AF flight 22 on 26 June
LON to BKK on 26 June
LH flight 4629 LHR to FRA 26 June

LH flight 744 FRA to BKK 26 June
NCE to SBN on 28 July
AF flight 7701 NCE to CDG 28 July

AF flight 050 CDG to ORD 28 July
Page 36 of 714
UA flight 5860 ORD to SBN 28 July

Electronic Ticketing
The Electronic Ticketing indicator field indicates whether a flight is eligible for electronic ticketing (value 'Y' for
Yes) or not (value 'N' for No).
addProductDetail - Data element Value
/electronicTicketing
Value
Y
/electronicTicketing
Y
Electronic ticketing (e-ticketing) allows sending ticketing information directly to an airline so that passengers
can check in at the airport and board flights without requiring printed tickets. When an electronic ticket (e-ticket)
is issued via Amadeus, the system sends the flight coupons as a message to the airline. If the airline accepts
the e-ticket request, the information is stored in the airline's own system as an e-ticket record and displayed
in the reply.
Notes:
The amount of time that electronic ticket record remains stored in the airline's system varies among
airlines.
In order for electronic tickets (in other word e-ticketing) to be issued, the office must be authorised to
issue e-tickets as defined at the Office Profile level.The flight segments in the itinerary are required to be
eligible for 'e-ticketing' and the validating airline must support e-ticketing in Amadeus.
Every airline that supports electronic ticketing in Amadeus has its own conditions.
Slice & Dice
The Slice and Dice process aim is to consider all availabilities that may be used in order to optimise the price
of an itinerary, and to apply the same class combination restrictions as the one applied by the carriers.
When Slice and Dice process is applied, the availability context is returned in the Master Pricer response. This
context will have to be used to book the solution returned by the engine.
Let us consider an example of a 3-segment eligible connection, between the 4 cities A, B, C and D, where the
3 flights are AB, BC, and CD. Without Slice and Dice process, only O&D availability AD is checked. With the
Slice and Dice process, local availabilities AB, BC, CD and Sub O&D availabilities AC and BD (respectively
named Sub O&D 1 and Sub O&D 2) will also have to be checked. This means that in case an O&D context
(default processing, no extra information about availability context), all flights of the connection have to be sold
at the same time. In case of Sub O&D, the two corresponding flights must be sold together and in case of local
context, the corresponding flight has to be sold alone.
In segmentFlightRef, an additional refQualifier with the value "A" (for Recommendation Availability context) is
added with its refNumber
SearchReply - Data element
Example
Description
segmentFlightRef /
referencingDetail / refQualifier
Reference of Proposed Segment
segmentFlightRef /
referencingDetail / refNumber
Index to Proposed Segment
segmentFlightRef /
referencingDetail / refQualifier
Reference to availability
Page 37 of 714
segmentFlightRef /
1
Index to availability context
referencingDetail / refNumber
The corresponding description for each reference of a recommendation availability context is given in the group
specificRecDetails. This group contains the following sub-groups:
the specificRecItem with the referenceType "A" and the refNumber
the specificProductDetails which contains the productReferences with the paxFareNum
the fareContextDetails which contains the requestedSegmentInfo with the segRef
the cnxContextDetails which contains the fareCnxInfo with the contextDetails and the
availabilityCnxType.
Note: Possible values for the availabilityCnxType are:
LA for Local Availability
S1 for Sub O&D 1
S2 for Sub O&D 2
default is the O&D context and in this case no availability context is returned
Example
Description
specificRecDetails /
specificRecItem /referenceType
Availability context
specificRecDetails/
specificRecItem/refNumber
Availability context index
specificProductDetails/
productReferences / paxFareNum
Reference to passenger
specificProductDetails/
fareContextDetails/
requestedSegmentInfo/ segRef
Index of Proposed Segment
fareContextDetails/
LA
cnxContextDetails[1]/ fareCnxInfo/
contextDetails/ availabilityCnxType
availability context "local" for first

flight of Proposed Segment
fareContextDetails/
LA
cnxContextDetails[2]/ fareCnxInfo/
contextDetails/ availabilityCnxType
Availability context "local" for

second flight of Proposed Segment
Reply Structure
As it is not possible to cover every reply structure possible, only a sample of a possible reply structure is
provided as a guideline of the typical reply message expected.
Each reply contains the following:
Fare Families Applicable for the recommendations (in case parameterized fare families have been
requested in the input)
Proposed Flight Segments for each requested segment
Journeys consisting of combinations of proposed flight segments to complete the requested trip
Applicable Fares for journeys
Applicable Fare Details

Page 38 of 714
My Search Reply: Parameterized Fare Families

This is only applicable for the Search Travel Board function.
Only in case the My Search option is used, the following information needs to be returned in the reply:
Fare Family Information: Reference, name and ranking of each fare family
This table presents the XML node familyInformation structure associated to each Fare Family information that
is returned in the reply:
example
Description
/ familyInformation /refNumber
Reference of the fare family
/ familyInformation /
fareFamilyname
FFAMILY1
Name of the fare family
/ familyInformation /hierarchy
100
Fare Family Reference of each fare detail:

example
Description
/ fareDetails / groupOfFares /
F
fareFamiliesRef /referencingDetail/
refQualifier
Reference of the fare family
/ fareDetails / groupOfFares /
1
fareFamiliesRef /referencingDetail/
refQualifier/ refNumber
Fare Breakpoint returned
Reference to the Fare Family

referenced 1 in the family
information node.
example
/recommendation[2] /
Y
paxFareProduct[4] /fareDetails[2] /
groupOfFares/ productInformation/
breakPoint
Description
The fare breakpoint: Y or N
OB fees
In the reply, information is also provided about the fact that OB fees exist for the validating carrier and the office
(OID), the validating carrier used for pricing and the amount of OB fees.
example
Description
priceTicketing/ priceType[1]/
OBV
Validating carrier accepts OB fees
priceTicketing/ priceType[2]/
OBA
OID accepts OB fees
recPriceInfo/ monetaryDetail/
amountType
recPriceInfo/ monetaryDetail/
amount
Page 39 of 714
paxFareDetail/ codeShareDetails/
transportStageQualifier
Type of carrier: validating carrier

used for pricing
paxFareDetail/ codeShareDetails/
company
AA
AA is validating carrier
paxFareDetail/ monetaryDetails/
amountType
OB
Type of Amount: OB fees
paxFareDetail/ monetaryDetails/
10
Amount
amount
It should be noted that the number of recommendations returned are dispersed between applicable fares and
will be less than or equal to the number recommendations requested in the query. One applicable Fare may
contain more than one journey, resulting in a set of recommendations based on the same Fare.
Below is a typical reply structure that can be expected to the query sample provided in the "Building A Query"
section of this document. The sample reply structure contains the following information for 5 recommendations
to a query containing 2 requested segments (1st - Nice to Houston, 2nd - Houston to Nice):
Item #
1
Reply Information
Applicable Currency of reply in US Dollars
PROPOSED SEGMENTS APPLICABLE TO 1ST REQUESTED SEGMENT

2
Applicable "Requested" Segment - 1st Requested segment
Applicable "Proposed" Segment - 1st Proposed segment
4-5
Total elapsed flying time for proposed segment - 13h50
6-30
Flight Details for 1st proposed segment
6-18
1st flt
Nice to Paris
19-30
2nd flt
Paris to Houston
31
Applicable "Proposed" Segment - 2nd Proposed segment
32-33
34-59
Flight Details for 2nd proposed segment
34-46
1st flt
Nice to Paris
47-59
2nd flt
Paris to Houston
60
Applicable "Proposed" Segment - 3rd Proposed segment
61
62-87
Flight Details for 2nd proposed segment
62-74
1st flt
Marseille to Paris
75-87
2nd flt
Paris to Houston
PROPOSED SEGMENTS APPLICABLE TO 2ND REQUESTED SEGMENT

88
Applicable "Requested" Segment - 2nd Requested segment
89
Applicable "Proposed" Segment - 1st Proposed segment

Page 40 of 714
90-92
93-118
93-105
1st flt
Houston to London
106-118
2nd flt
London to Nice
119
Applicable "Proposed" Segment - 2nd Proposed segment
120-121
122-148
122-135
1st flt
Houston to Paris
136-148
2nd flt
Paris to Nice
149
Applicable "Proposed" Segment - 3rd Proposed segment
150-151
152-178
152-165
1st flt
Houston to Paris
166-178
2nd flt
Paris to Nice
179
Applicable "Proposed" Segment - 4th Proposed segment
180-181
182-208
182-195
1st flt
Houston to London
196-208
2nd flt
London to Nice
APPLICABLE RECOMMENDATIONS FOR REQUESTED SEGMENTS

209-258
1st Set of recommendations for an Applicable fare
210
Total Price for all passengers (including taxes)
211
Total Taxes for all passengers
212-215
Applicable flight combination - completing recommendation #1
216-219
Applicable flight combination - completing recommendation #2
220-258
220-238
Fare Details for Adult passengers
239-258
Fare Details for Child passenger
259-300
2nd Set of recommendations for an Applicable fare
260
261
262-265
Applicable flight combination of - completing recommendation #3
266-269
Page 41 of 714
270-300
301-330
3rd Set of recommendations for an Applicable fare
302
303
304-307
308-330
NOTE: The reply structure contains all proposed segments listed first followed by associated fare information
for the proposed segments to complete each recommendation.
Item
1

/conversionRate/
conversionRateDetail/ currency
Value
USD
PROPOSED SEGMENTS FOR 1st REQUESTED SEGMENT

2
/flightIndex [1] /
requestedSegmentRef/ segRef
/flightIndex [1] /groupOfFlights [1] / 1

propFlightGrDetail/flightProposal
[1] / ref

[2] / ref
/flightIndex [1] /groupOfFlights [1] / EFT

[2] / unitQualifier
/flightIndex [1] /groupOfFlights [1] / AF

[3] / ref
/flightIndex [1] /groupOfFlights [1] / MCX

[3] / unitQualifier
/flightIndex [1] /groupOfFlights

200202
[1] /flightDetails [1] /
flightInformation/productDateTime/
dateOfDeparture

0725
timeOfDeparture
10

flightDetails [1] /flightInformation/
productDateTime/ dateOfArrival
Page 42 of 714
11

productDateTime/ timeOfArrival
12
/flightIndex [1] /groupOfFlights [1] / NCE

location [1] / locationId
13
/flightIndex [1] /groupOfFlights [1] / CDG

14
/flightIndex [1] /groupOfFlights [1] / A

location [2] / airportCityQualifier
15

companyId/ marketingCarrier
16

companyId/ operatingCarrier
17

flightNumber
18

productDetail/ equipmentType
19

Y
flightInformation/addProductDetail/
electronicTicketing
20

200202
dateOfDeparture
21

1020
timeOfDeparture
22

23

Page 43 of 714
24

25
/flightIndex [1] /groupOfFlights [1] / IAH

26
/flightIndex [1] /groupOfFlights [1] / CO

27

28

flightNumber
29

30

Y
electronicTicketing
31

[1] / ref
32

[2] / ref
33

[2] / unitQualifier
34

[3] / ref
35

[3] / unitQualifier
36

200202
dateOfDeparture
Page 44 of 714
37

0725
timeOfDeparture
38

39

40

41

42

43

44

flightNumber
45

46

Y
electronicTicketing
47

200202
dateOfDeparture
48

1020
timeOfDeparture
Page 45 of 714
49

50

51

52

53

54

55

flightNumber
56

57

Y
electronicTicketing
58

[1] / ref
59

[2] / ref
60

[2] / unitQualifier
61

[3] / ref
Page 46 of 714
62

[3] / unitQualifier
63

200202
dateOfDeparture
64

0725
timeOfDeparture
65

66

67
/flightIndex [1] /groupOfFlights [3] / MRS

68

69
/flightIndex [1] /groupOfFlights [3] / A

location [2] / airportCityQualifier
70

71

72

flightNumber
73

74

Y
electronicTicketing
Page 47 of 714
75

200202
dateOfDeparture
76

1020
timeOfDeparture
77

78

79

80

81

82

83

flightNumber
84

85

Y
electronicTicketing
PROPOSED SEGMENTS FOR 2nd REQUESTED SEGMENT

86
/flightIndex [2] /
requestedSegmentRef/ segRef
Page 48 of 714
87

[1] / ref
88

[2] / ref
89

[2] / unitQualifier
90
/flightIndex [1] /groupOfFlights [1] / BA

[3] / ref
91

[3] / unitQualifier
92

210302
dateOfDeparture
93

1625
timeOfDeparture
94

95

96

productDateTime/ dateVariation
97

98
/flightIndex [2] /groupOfFlights [1] / LGW

99

Page 49 of 714
100

101

flightNumber
102

103

N
electronicTicketing
104

220302
dateOfDeparture
105

0840
timeOfDeparture
106

107

108

109

110

111

112

flightNumber
Page 50 of 714
113

114

N
electronicTicketing
115

[1] / ref
116

[2] / ref
117

[2] / unitQualifier
118

[3] / ref
119

[3] / unitQualifier
120

210302
dateOfDeparture
121

1840
timeOfDeparture
122

123

124

125

Page 51 of 714
126

127

128

129

flightNumber
130

131

Y
electronicTicketing
132

220302
dateOfDeparture
133

1235
timeOfDeparture
134

135

136

137

138

Page 52 of 714
139

140

flightNumber
141

142

Y
electronicTicketing
143

[1] / ref
144

[2] / ref
145

[2] / unitQualifier
146

[3] / ref
147

[3] / unitQualifier
148

210302
dateOfDeparture
149

1840
timeOfDeparture
150

151

Page 53 of 714
152

153

154

155

156

157

flightNumber
158

159

Y
electronicTicketing
160

220302
dateOfDeparture
161

1235
timeOfDeparture
162

163

164

Page 54 of 714
165

166

167

168

flightNumber
169

170

Y
electronicTicketing
171

[1] / ref
172

[2] / ref
173

[2] / unitQualifier
174

[3] / ref
175

[3] / unitQualifier
176

210302
dateOfDeparture
177

1850
timeOfDeparture
Page 55 of 714
178

179

180

181

182

183

184

185

flightNumber
186

187

Y
electronicTicketing
188

220302
dateOfDeparture
189

1115
timeOfDeparture
190

Page 56 of 714
191

192

193

194

195

196

flightNumber
197
/flightIndex [2] /groupOfFlights [4] / AR1

198

N
electronicTicketing
RECOMMENDATIONS
1st SET OF RECOMMENDATIONS BASED ON 1 FARE
199
/recommendation [1] /itemNumber/ 1

itemNumberId/ number
APPLICABLE FARE AMOUNT

200
/recommendation [1] /recPriceInfo/ 1800.11

monetaryDetail [1] / amount
201

1st APPLICABLE JOURNEY - RECOMMENDATION # 1

202
/recommendation [1] /
segmentFlightRef [1] /
referencingDetail [1] / refQualifier
Page 57 of 714
203
referencingDetail [1] / refNumber
204
205
2nd APPLICABLE JOURNEY - RECOMMENDATION # 2

206
207
208
209
APPLICABLE FARE DETAILS

210
1
paxFareProduct [3] /paxFareDetail/
paxFareNum
211
1100.00
totalFareAmount
212
60.00
totalTaxAmount
213
ADT
paxFareProduct [3] /paxReference/
ptc
214
1
traveller [1] / ref
215
2
traveller [2] / ref
Page 58 of 714
216
paxFareProduct [3] /fareDetails
[1] /segmentRef/ segRef
217
paxFareProduct [3] /
fareDetails [1] /groupOfFares/
productInformation/cabinProduct/
rbd
218
cabin
218-2
avlStatus
219
productInformation/
fareProductDetail/ fareBasis
MLXPX
220
ADT
productInformation/
fareProductDetail/ passengerType
221
productInformation/
fareProductDetail/ fareType
RP
222
productInformation/ Breakpoint
223
224
Page 59 of 714
[2] /productInformation/
avlProductDetails/ rbd
225
cabin
226
avlStatus
227
MLXPX
228
ADT
229
RP
230
231
1
paxFareNum
232
700.11
totalFareAmount
233
30.00
totalTaxAmount
234
CH
ptc
Page 60 of 714
235
3
traveller/ ref
236
fare/pricingMessage/
freeTextQualification/
messageQualifier
APM
freeTextQualification/
messageCode
237
/recommendation [1]/
paxFareProduct [4] /fare/
pricingMessage/ description [1]
NOT FARED AT PASSENGER

TYPE REQUESTED
238
paxFareProduct [4] /fare/
pricingMessage/ description [2]
239
240
241
cabin
242
avlStatus
243
Y4WCH
244
CH
Page 61 of 714
245
RP
246
247
248
249
cabin
250
avlStatus
251
Y4W
252
ADT
253
RP
254
Page 62 of 714
2nd SET OF RECOMMENDATIONS BASED ON 1 FARE

249


250

251

1st APPLICABLE JOURNEY - RECOMMENDATION # 3

252
referencingDetail [1] / refQualifie
253
254
255
2nd APPLICABLE JOURNEY - RECOMMENDATION # 4

256
257
258
259

260
1
paxFareNum
Page 63 of 714
261
1209.70
totalFareAmount
262
70.00
totalTaxAmount
263
ADT
ptc
264
1
traveller [1] / ref
265
2
traveller [2] / ref
266
267
268
TLXAPT3
269
ADT
270
RP
271
272
Page 64 of 714
273
TLXAPT3
274
ADT
275
276
1
paxFareNum
277
780.00
totalFareAmount
278
60.00
totalTaxAmount
279
CH
ptc
280
3
traveller/ ref
281
282
283
TLXAPTCH
284
CH
RP
Page 65 of 714
285
RP
286
287
288
TLXAPTCH
289
CH
290
RP
3rd SET OF RECOMMENDATIONS BASED ON 1 FARE

291


292

293

1st ASSOCIATED JOURNEY - RECOMMENDATION # 5

294
295
296
Page 66 of 714
297

298
1
paxFareNum
299
1350.00
totalFareAmount
300
70.00
totalTaxAmount
301
ADT
ptc
302
1
traveller [1] / ref
303
2
traveller [2] / ref
304
305
306
RP
307
308
309
RP
Page 67 of 714
310
1
paxFareNum
311
1000.50
totalFareAmount
312
60.00
totalTaxAmount
313
CH
ptc
314
3
traveller/ ref
315
316
317
RP
318
319
320
RP
Page 68 of 714
Free Baggage Allowance (FBA)

The FBA information describes the free baggage allowed per flight and per passenger type for each
recommendation. It includes the policy (weight or pieces) and units (kilos or pounds).
In case of multiple passenger types, the FBA is only calculated for the adult passenger type. For example, if
we have an adult, a child and an infant, the FBA returned is the FBA of the adult. In case no adult passenger
type is requested, the FBA returned is the FBA of the first passenger type.
The functionality is triggered by a setting at OID level or by input option.
Airline Fare Family information
This option allows the user to have the Airline Fare Family name, description and ancillary services attached
within a recommendation. This information is returned by Fare Component or by requested segment. This is
triggered by a setting at OID level and by input option.
In-Flight Services
The user has the ability to request the display of the in-flight services at flight level.
This process is activated with the IFS input option.
When activated the process returns up to 10 Ids referring to in-flight services if filed by the airline.
The ids returned are among the following list:
Id
Description
Movie
Telephone
Telex
Audio programming
Television
Reservation booking service
Duty free sales
Smoking
Non-smoking
10
Short feature video
11
No duty free sales
12
In-seat power source
13
Internet access
14
E-Mail
15
In seat Video Player/Library
16
Lie-flat Seat
Page 69 of 714
17
Additional Services
18
Wi-Fi
19
Lie-flat Seat First
20
Lie-flat Seat Business
21
Lie-flat Seat Business Economy
3.1 Reply Sub Structure: Free Baggage Allowance 1 - freeBagAllowanceGrp

3.1.1 Description
This sub structure contains details of the free baggage allowance. It can be a weight or a number of pieces
(for example, W for weight or N for pieces). In case of weight, the unit is returned (for example, K for kilograms
or L for pounds).
The example describes 2 items:
Item 1: 23 kg
Item 2: 1 piece
3.1.2 Xml Structure

<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>FBA</type>
</carrierFeeDetails>
</serviceTypeInfo>
<globalMessageMarker> </globalMessageMarker>
<freeBagAllowanceGrp>
<freeBagAllownceInfo>
<baggageDetails>
<freeAllowance>23</freeAllowance>
<quantityCode>W</quantityCode>
<unitQualifier>K</unitQualifier>
</baggageDetails>
</freeBagAllownceInfo>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberDetails>
</itemNumberInfo>
</freeBagAllowanceGrp>
<baggageDetails>
Page 70 of 714
<quantityCode>N</quantityCode>
</baggageDetails>
<itemNumberInfo>
<itemNumberDetails>
<number>2</number>
</itemNumberInfo>
</serviceFeesGrp>
3.2 Reply Sub Structure: Free Baggage Allowance 2 serviceCoverageInfoGrp

3.2.1 Description
This sub structure contains details of free baggage allowance coverage at recommendation level:
Baggage coverage item (example 10)
Passenger type reference gives the information about the PTC to which the Baggage coverage is
applicable (example 1: first PTC)
Flight coverage: gives the info about the applicability of the baggage coverage, identifying the flights
in which these baggage information is allowed (example Requested segment 1 Leg 1 and Requested
segment 2 Leg 1 and 2)
Free Baggage allowance reference (refNumber 3)
3.2.2 Xml Structure

<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>FBA</type>
</serviceTypeInfo>
<serviceCoverageInfoGrp>
<itemNumberInfo>
<itemNumber>
<number>10</number>
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
<referenceNumber>1</referenceNumber>
Page 71 of 714
</travellerDetails>
</paxRefInfo>
<coveragePerFlightsInfo>
<numberOfItemsDetails>
<referenceQualifier>RS</referenceQualifier>
<refNum>1</refNum>
</numberOfItemsDetails>
<lastItemsDetails>
<refOfLeg>1</refOfLeg>
</lastItemsDetails>
</coveragePerFlightsInfo>
<refNum>2</refNum>
<lastItemsDetails>
</lastItemsDetails>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
<refQualifier>F</refQualifier>
<refNumber>3</refNumber>
</referencingDetail>
</refInfo>
</serviceCovInfoGrp>
</serviceCoverageInfoGrp>
</serviceFeesGrp>
3.3 Reply Sub Structure: Free Baggage Allowance 3 - segmentFlightRef

3.3.1 Description
This sub structure contains the reference corresponding to the baggage allowance coverage applicable to the
returned recommendation:
refQualifier: B
refNumber: 1
3.3.2 Xml Structure

<recommendation>
Page 72 of 714
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo> </recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<refQualifier>S</refQualifier>
<referencingDetail>
<referencingDetail>
<refQualifier>B</refQualifier>
</segmentFlightRef>
</recommendation>
Page 73 of 714
4 Error Messages
Specific error conditions exist for each mandatory and optional parameter in the query. However, as these
errors may be returned in several instances and it is not always apparent to which operational parameter they
apply, this section provides the following general errors that may be returned when building a query.
Local Application Error
If a mandatory element is missing in the query structure, including any elements that are deemed mandatory
via an association to another optional parameter, the entire entry is rejected.
Common Errors
It should be noted here that these messages are returned in the instances when no recommendations can
be found.
No Recommendation Found For Requested Itinerary/Options
Whenever the Lowest Fare Search does not find any recommendation matching the requested options, the
query is rejected with the following message:
"NO RECOMMENDATION FOUND FOR REQUESTED ITINERARY/OPTIONS"
No Available Flight Found For The Requested Segment Nn
In the currentLowest Fare Search process, when no flight is available (For example, all the flights matching
the requested itinerary are set to 0 or closed), the transaction is rejected with the message:
"ERC - CODE SET 9321: VALUE 977 - NO AVAILABLE FLIGHT FOUND FOR THE REQUESTED SEGMENT
nn"
(Where: nn represents the first impacted requested segment number).
These messages are returned when there is an error in theLowest Fare Search input.
Latest Future Date Possible ddmmmyy
A reject message will be produced by the server; indicating that a query is too far into the future when it goes
beyond the latest possible date. The corresponding reject message:
"LATEST FUTURE DATE POSSIBLE ddmmmyy"
Too Many Airline Codes
If more than 99 airline codes are specified at the 'Include Airline' option level, the entire entry is rejected and
the following message is returned:
"TOO MANY AIRLINE CODES"
Invalid Value (Coded) - Pricingtickinfo
The only valid expanded parameter options applicable to a MP request are NAP, NPE, NR and RF. If an
unknown Expanded Parameter is specified in the entry, the entire request is rejected and the following error
message is returned:
"INVALID VALUE (CODED) - PRICINGTICKINFO"
Invalid Value Coded - Pricingtickinfo
If an unknown Unifare option is specified in the entry, the entire request is rejected and the following error
"INVALID VALUE CODED - PRICINGTICKINFO"
Too Many Requested Segments
Up to 3 Requested Segments 'Lowest Fare search' requests are allowed, excluding surface sectors. If this
check fails, the entire entry is rejected with the following message:
"TOO MANY REQUESTED SEGMENTS"
Invalid Value (Coded) - Conversion Rate
If an unknown Currency is specified in the Lowest Fare search entry, the entire request is rejected and the
following error message is returned:
Page 74 of 714
"INVALID VALUE (CODED) - CONVERSION RATE"

Invalid Value (Coded)
If an unauthorised value is specified in a field flagged as 'coded' at the Lowest Fare Search Input message
level, the entire entry is rejected and, if no other specific error message exists, the following generic reject
"INVALID VALUE (CODED) - XXX"
where XXX is the Segment smart name (for example,paxReference).
Note: When a field is flagged as coded, refer to the corresponding code set to check the list of values authorised
No.
Message
118
System unable to process
304
System temporarily unavailable
830
No recommendation found with lower or equal price
910
Transaction closed
915
Fare product unavailable for user
916
EDIFACT version not supported
917
EDIFACT message size Exceeded
918
Number of Requested Segments exceeds three
919
SOTI/SITO/SOTO Requests are not handled
920
Past Date/Time not allowed
921
Date/Time must be in chronological order
922
Maximum 2 Requested Segments with same date
923
Specify Times of Arrival/Departure to avoid

overlapping
924
Overlapping Date/Time ranges
925
Overlapping Origin//Destination Segment
926
Invalid number of passenger
927
Number of passenger exceeds nine
928
Exceeds maximum fare discount codes
929
Option cannot be applied at Requested Segment

level
930
Option cannot be applied at itinerary level
931
No itinerary found for Requested Segment n
932
RG LFS not applicable for this request
934
Invalid radius - maximum allowed 300km
935
Invalid range of date option
936
Invalid time option

Page 75 of 714
937
Invalid time window option
938
Time of Departure/Arrival is mandatory if time

window requested
939
Date is mandatory with time window option
940
Invalid airline code
941
Invalid exclude airline option
942
Airline cannot be at the same time included and

excluded
943
Invalid - 20 airline codes maximum
944
Invalid flight category
945
Non-stop cannot be requested with connect point

option
946
Invalid connecting point
947
Same city/airport code cannot be included and

excluded
948
City/airport must be in same country
950
Invalid City
952
Conflicting options used
953
Invalid Unifare option
954
Service Level option must be requested
955
Invalid passenger type code
956
Exceeds maximum fare discount codes
957
Number of non-infant PTC cannot exceed number of

seats
958
Number of infants cannot exceed number of seats
960
Invalid Ticketing/Selling city
961
Invalid conversion currency
962
Invalid price to beat value
963
INVALID VALUE (CODED) - originator
964
INVALID VALUE (CODED) - numberOfUnit
965
INVALID VALUE (CODED) - paxReference
966
INVALID VALUE (CODED) - pricingTickInfo
967
INVALID VALUE (CODED) - conversionRate
968
INVALID VALUE (CODED) - corporate
969
INVALID VALUE (CODED) - priceToBeat

Page 76 of 714
970
INVALID VALUE (CODED) - taxInfo
971
INVALID VALUE (CODED) - travelFlightInfo
972
INVALID VALUE (CODED) - requestedSegmentRef
973
INVALID VALUE (CODED) - departureLocalization
974
INVALID VALUE (CODED) - arrivalLocalization
975
INVALID VALUE (CODED) - timeDetails
976
INVALID VALUE (CODED) - flightInfo
977
NO AVAILABLE FLIGHT FOUND FOR

REQUESTED SEGMENT NN
978
TOO MANY REQUESTED SEGMENTS
979
INVALID OPTION
980
INVALID TYPE OF ITINERARY
981
NO FARE FOUND FOR REQUESTED ITINERARY
982
SPECIFY AIRLINE
983
TOO MANY AIRLINES
984
SPECIFY A COMMERCIAL FARE FAMILY
985
INVALID COMMERCIAL FARE FAMILY
986
TOO MANY COMMERCIAL FARE FAMILY

REQUESTED
987
NO FARE FAMILY FOUND FOR REQUESTED

COMMERCIAL FARE FAMILY
988
EXCEEDS MAXIMUM DISCOUNT CODES FOR A

PASSENGER
993
INVALID TIME AT DESTINATION
994
INVALID ITINERARY POINT OF ORIGIN OPTION
995
NO FARE FOUND FOR REQUESTED FARE

FAMILY
997
Fare Basis and Prime Booking Code Cannot Be

Mixed
998
Invalid Type of Fare Requested
999
Invalid Fare Family Combinability Requested
997
Invalid Generic Fare Basis requested

INVALID PRIME BOOKING CODE
TOO MANY FARE FAMILIES
Page 77 of 714
TOO MANY MATCHING ATTRIBUTES SETS

REQUESTED
TOO MANY ATTRIBUTE OCCURRENCES
INVALID FARE FAMILY NAME REQUESTED
INVALID CARRIER REQUESTED
836
DATE OVERRIDE OPTION NOT ALLOWED
4.1 Error Reply

<Fare_MasterPricerTravelBoardSearchReply xmlns="http://xml.amadeus.com/FMPTBR_16_1_1A" >
<errorMessage>
<applicationError>
<applicationErrorDetail>
<error>920</error>
</applicationErrorDetail>
</applicationError>
<errorMessageText>
<freeTextQualification>
<textSubjectQualifier>1</textSubjectQualifier>
</freeTextQualification>
<description>Past date/time not allowed</description>
</errorMessageText>
</errorMessage>
</Fare_MasterPricerTravelBoardSearchReply>
Page 78 of 714
5 Operations
5.1 Operation: 01 - Search With Mandatory Elements
Itinerary date
A Date must be specified for each requested segment. Note that times and dates are specified in local time,
at each location.
No past date and/or past time are allowed.
When 2 or more requested segments are specified, dates and times must be in chronological order. Times
and dates are specified in local time, at each location, but the chronological order check must consider the
TU times and dates.
Up to 2 requested segments may be requested with the same date, or overlapping date ranges, as long as
the user specifies both:
"Arrive by" time option for the first requested segment,

"Depart from" time option for the second requested segment.
Origin Destination
A maximum of 3 requested segments is allowed, excluding surface sectors. These requested segments must
each include an origin and a destination city/airport code.
One-Way
NCE-LON
Return trip
NCE-LON-NCE
Multiple segments
NCE-LON-MAD-NCE
Itinerary including surface sector

NCE-LON/MAN-NCE
The origin and destination codes must comply with the standard IATA city/airport codes. If an IATA code is
not unique to a specific airport, but identifies at the same time, a city (for example, CHI) and an airport (for
example, HOU) the three-letter code represents the city unless it is specifically identified as an airport (A) type.
Whenever the request intends to restrict the search only to the airport, this must be specified in the case where
the IATA code is not unique to an airport.
The following table illustrates further the possible scenarios of the origin/destination search process:
Code Entered
CHI
Specified as City/Airport
Not Specified
Applicable point of
departure/arrival searched
Chicago city, including the
following airports:
- O'Hare (ORD)
- Midway (MDW)
CHI
City Location

following airports:
Page 79 of 714
- O'Hare (ORD)
- Midway (MDW)
CHI
Airport Location

following airports:
- O'Hare (ORD)
- Midway (MDW) (because CHI
airport code does not exist)
ORD
Not specified
O'Hare (ORD)
HOU
Not Specified
Houston city, including the

following airports:
- Houston Hobby (HOU)
- G. Bush Intercontinental (IAH)
HOU
City location
Houston city, including the

following airports:
- Houston Hobby (HOU)
- G. Bush Intercontinental (IAH)
HOU
Airport location
Houston Hobby (HOU) airport only
Only Sold in / Ticketed in (SITI) requests are handled. That means that:
for domestic itineraries, the origin city/airport code of the first segment must reside within the same
country as the selling and the ticketing country location,
for international itineraries, the origin city/airport code of the first international segment (excluding
surface segments) must reside within the same country as the selling and the ticketing country location.
Example:
Itinerary
International/Domestic
SITI country
CHI-NYC
Domestic
USA
NCE-PAR -- LON-MAN
Domestic
France
CHI-LON
International
USA
NCE-PAR-NYC
International
France
NCE-PAR-NYC-MEX
International
France
NCE-PAR -- LON-NYC
International
UK
Number of Passenger Seats
The number of passenger seats must be between 1 and 9.
Page 80 of 714
The recommendations returned are applicable to all passengers in the query. All passengers must be travelling
together.
Associated Passenger Type Codes
As the passenger fares vary for different types of passengers, a passenger type code for any low fare search
is required. Passenger type codes dictate the low fare search to provide recommendations with any qualifying
passenger fare discounts applicable. All passenger type codes specified must be valid type codes stored within
the Amadeus system.
A maximum of 6 passenger type codes may be requested.
When more than one Passenger Type is requested, the system must search for the cheapest fares with the
possibility to return non-homogeneous recommendations: different passengers booked in different classes in
order to offer the lowest fare.
In such a case, it becomes mandatory to split the traveling parties into separate records to accommodate the
lowest fare recommendation. This can be accomplished via the Powered PNR interface.
When a non-homogeneous recommendation is proposed, the following warning message is returned:
"SPLIT PNR - DIFFERENT BOOKING CODES REQUIRED FOR LOWEST FARE"
Exception: Infant must travel in the same class as the accompanying "adult" passengers (DT, YTH, MIL, and
so on).
Note: When specifying a PTC 'inf' without a seat, they must be associated to a passenger accompanying a seat.
The user must specify the total number of recommendations to be returned.
The total number of requested recommendations must be a valid number between 1 and 200. If a number higher
than 200 is requested, the query will not be rejected, but no more than 200 recommendations will be returned.
Request Elements
The example below illustrates a low fare search including the mandatory function elements of itinerary date,
origin/destination, and number of passengers with associated types specified with the following information;
Query Requirements:
MANDATORY ORIGIN/DESTINATION INFORMATION FOR 1 REQUESTED SEGMENT
Departure city of London
Arrival city of New York

MANDATORY ITINERARY DATE FOR 1 REQUESTED SEGMENT
Trip departure 14 August 2003

MANDATORY PASSENGER INFORMATION
4 passengers travelling in total - 3 seats required
2 Adults, 1 Children, 1 Infant (associated to ADT passenger 1)

MANDATORY NUMBER OF RECOMMENDATIONS
200 requested recommendations

Page 81 of 714
Requesting
Specified Data
Request by number of seats occupied by passengers PX

# of seats for request
Request specific maximum number of

recommendations to be returned
RC
Maximum number of recommendations to be

returned
200
Applicable passenger type code for Adult
ADT
Passenger reference for 1st seat
Passenger reference for 2nd seat
Applicable passenger type code for Child
CH
Passenger reference for 3rd seat
Applicable passenger type code for Infant
INF
Passenger reference associated to first Adult seat
Infant indicator
1st requested segment
Departure city of London
LON
NYC
Trip Date (14 August 2003)
140803
5.1.1 Query Structure

<Fare_MasterPricerTravelBoardSearch xmlns="http://xml.amadeus.com/FMPTBQ_16_1_1A" >
<numberOfUnit>
<unitNumberDetail>
<numberOfUnits>3</numberOfUnits>
<typeOfUnit>PX</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>RC</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
Page 82 of 714
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
<infantIndicator>1</infantIndicator>
</traveller>
</paxReference>
<itinerary>
<requestedSegmentRef>
<segRef>1</segRef>
</requestedSegmentRef>
<departureLocalization>
<depMultiCity>
<locationId>LON</locationId>
</depMultiCity>
</departureLocalization>
<arrivalLocalization>
<arrivalMultiCity>
<locationId>NYC</locationId>
</arrivalMultiCity>
</arrivalLocalization>
<timeDetails>
<firstDateTimeDetail>
<date>140803</date>
</firstDateTimeDetail>
</timeDetails>
</itinerary>
</Fare_MasterPricerTravelBoardSearch>
5.1.2 Reply Structure

5.1.3 Possible Errors
Itinerary Date
Date is Mandatory
If no date is found in the query structure, the entire entry is rejected with the following message:
"DATE IS MANDATORY"
Page 83 of 714
Past Date/Time Not Allowed

If a past Date and/or past Time are found in the query, the entire entry is rejected with the following message:
"PAST DATE/TIME NOT ALLOWED"
Date/Time Must be in Chronological Order
When 2 or more Requested Segments are specified, if the Dates and Times are not in chronological order, the
entire entry is rejected with the following message:
"DATE/TIME MUST BE IN CHRONOLOGICAL ORDER"
Maximum 2 Requested Segments with Same Date
If more than 2 Requested Segments (excluding surface segments) are found with the same Date, the entire
entry is rejected with the following message:
"MAXIMUM 2 REQUESTED SEGMENTS WITH SAME DATE"
Specify Times of Arrival/Departure to Avoid Overlapping
If 2 requested segments are requested with the same date, or overlapping Date ranges, and the required
parameters are not specified,
"Arrive by" time option for the first Requested Segment
"Depart from" time option for the second Requested Segment
The following error message is returned:
"SPECIFY TIMES OF ARRIVAL/DEPARTURE TO AVOID OVERLAPPING"
Overlapping Date/Time Ranges
The system verifies that there is no overlapping of the requested time ranges. This check also applies when
a time range is requested and time ranges overlap, the time ranges being interpreted according to the time or
time window option definition. If this check fails, the entire entry is rejected with the following message:
"OVERLAPPING DATE/TIME RANGES"
When two consecutive requested air segments have a close (or equal) travel date, add a 'Time of Arrival' option
on the chronologically first segment and a 'Time of Departure' on the next segment. This will avoid experiencing
numerous Master Pricer "Near requested travel dates" query failures because of missing mandatory option in
the Lowest Fare request.
Note: See Certification Guidelines for more detail.
"Near requested travel dates" queries are defined as queries for which the difference between the arrival time
departure times of the 2 consecutive requested segments (meaning, the latest possible departure time of the
first requested segment and the earliest possible departure time of the next requested segment) is inferior to
12 hours.
Origin Destination
Number of Requested Segments Exceeds Three
If more than 3 Requested Segments are found in the query, excluding surface sectors, the entire entry is
rejected with the following message:
Page 84 of 714
"NUMBER OF REQUESTED SEGMENTS EXCEEDS THREE"

Overlapping Origin/Destination Segment N
The system verifies that there is no overlapping between the origin and the destination of any requested
segment. The origin and destination being requested as airport, city, area or multi-city, an overlap is detected
when, for a segment, at least one of the alternate origins corresponds to one of the alternate destinations. If
this check fails, the entire entry is rejected with the following message:
"OVERLAPPING ORIGIN/DESTINATION SEGMENT N"
Where N is the number of the first segment where an overlap is detected
Unknown City/Airport
If an invalid city/airport code is specified in the request, the following reject message will be returned:
"UNKNOWN CITY/AIRPORT"
Invalid Number of Passenger
If the specified number of passengers with seats is 0, the entire entry is rejected with the following message:
"INVALID NUMBER OF PASSENGER".
Number of Passengers Exceeds Nine
If the specified number of passengers with seats exceeds 9, the entire entry is rejected with the following
message:
"NUMBER OF PASSENGERS EXCEEDS NINE"
Invalid Passenger Type Code
Requested Passenger Type Codes are validated against the Amadeus System codes. If the Passenger Type
Code does not exist, the entire request is rejected and the following error message is returned:
"INVALID PASSENGER TYPE CODE"
Exceeds Maximum Fare Discount Codes
If more than 6 Passenger Types are specified, the entire request is rejected and the following error message
is returned:
"EXCEEDS MAXIMUM FARE DISCOUNT CODES"
The Number of Non-Infant PTCs Cannot Exceed Number of Seats
The number of Passenger Types requiring seats (meaning, all Passenger Type Codes with the exception of
IN and INF) cannot exceed the number of seats specified in the input. If this check fails, the entire request is
rejected and the following error message is returned:
"NUMBER OF NON-INFANT PTC CANNOT EXCEED NUMBER OF SEATS"
The Number of Infants Cannot Exceed Number of Seats
The number of Passengers not requiring seats (IN or INF code) cannot exceed the number of seats specified
(as only 1 infant is allowed per passenger having a seat). If this check fails, the entire request is rejected and
the following error message is returned:
Page 85 of 714
"NUMBER OF INFANTS CANNOT EXCEED NUMBER OF SEATS"

As this is a mandatory element which will fail on the local application prior to processing if not included in the
query and an invalid number of recommendations (higher than 200) in the query is ignored, no system error
conditions currently exist for this option.
Page 86 of 714
5.2 Operation: 02.01 Flight Option - Airline/Alliance (Include/Exclude)
The include and exclude options may be combined with any other option. The include and exclude options
may be specified in the same request. The preferred option can be combined with any other option except the
preferred connecting point. And it cannot be specified at the same level (itinerary, same requested segment)
as the include/excludeoptions.
If a YY carrier code is used in the include option at the same time as a specific airline/alliance, then this specific
airline/alliance can be proposed as Non-Stop or Direct flights and in connections with any other airline/alliance.
If the exclude option is specified, the search process may propose any carrier except those carriers specified
in the exclude parameter.
If include option is combined with the exclude option, the include option must contain a YY carrier code for
the processing of the exclude option.
If not specified otherwise, no occurrence of an exclude carrier as Non-Stop, Direct and/or in any part of a
connection is selected. In case of joint operation, both airline/alliance codes have to be checked. Marketing
carrier and operating carrier will have to be checked.
Preferred airline codes can be used to ensure that proposed segments considered by the system when
building recommendations will include online solutions on those airlines. This option does not ensure that
recommendations returned by Master Pricer will include such proposed segments as the objective is still to
propose the lowest available recommendations.
Alliance codes:
ONEWORLD *O
SKYTEAM *S
STAR ALLIANCE *A

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
<carrierQualifier>M</carrierQualifier>
Page 87 of 714
<carrierId>AF</carrierId>
<carrierId>YY</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
<locationId>PAR</locationId>
</depMultiCity>
<arrivalMultiCity>
<locationId>MIA</locationId>
</arrivalMultiCity>
<timeDetails>
<date>201203</date>
</timeDetails>
<flightInfo>
<companyIdentity>
<carrierQualifier>X</carrierQualifier>
<carrierId>AA</carrierId>
</companyIdentity>
</flightInfo>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<arrivalPointDetails>
</arrivalPointDetails>
<timeDetails>
<date>251203</date>
Page 88 of 714
</timeDetails>
<flightInfo>
<companyIdentity>
<carrierQualifier>F</carrierQualifier>
<carrierId>BA</carrierId>
</companyIdentity>
</flightInfo>
</itinerary>

Invalid Airline Code
The airline codes are a 2 alpha numeric character code that is defined in the Amadeus System. If the airline
code specified is invalid, the entire entry will be rejected and the error "Invalid Airline Code" will be returned.
Verify the airline codes specified in the request and resend the request.
Invalid Exclude Airline Option
YY Airline Code Not Present in Combined Include Option
If the "Exclude" option is combined with the "Include" option and the YY code is not used as an include
airline code, the entire entry is rejected with the following message:
"INVALID EXCLUDE AIRLINE OPTION"
Example:
Request
Process
Include: TW, CO, AA
Entry rejected.
Exclude: US
YY Airline Code in Exclude Option
If the YY code is used in the "Exclude" option, the entire entry is rejected with the following message:
"INVALID EXCLUDE AIRLINE OPTION"
Airline Cannot Be At the Same Time Included and Excluded
If the same airline code is specified as "Include" and "Exclude", at the same request level, the entire entry
is rejected with the following message:
"AIRLINE CANNOT BE AT THE SAME TIME INCLUDED AND EXCLUDED"
If more than 3 airline codes are specified, the entire entry is rejected with the following message:
Page 89 of 714
INVALID 3 PREFERRED AIRLINE CODES MAXIMUM
If the Preferred Airline option is requested in combination with the Include/Exclude Airline option, the
entry is rejected with the message:
PREFERRED AND INCLUDE/EXCLUDE AIRLINE CANNOT BE MIXED
If the Preferred Airline option is requested in combination with the Preferred connecting Point option,
the entry is rejected with the message:
PREFERRED AIRLINE AND CONNECTION OPTIONS CANNOT BE MIXED
If an airline code is specified more than once, the entry is not rejected: the second occurrence is just ignored.
Page 90 of 714
5.3 Operation: 02.02 Flight Option - Flight Category

The following flight categories are supported:
Non-Stop: N
Direct: D
Connecting: C
The rules defined in Availability apply regarding the definition of the Change of Gauge (COG) flights:
US market: the COG is considered as a Direct flight,

EU market: the COG is included in the Connecting flights.
This information is usually obtained from the User Office Profile settings. However, due to current information
limitations, the change of gauge will be always considered as a connecting flight within this function.
Warning: High-speed trains are considered as non-stop, but when returned, their stops are provided like
technical stops.
A maximum of 3 flight categories per requested segment may be specified and maybe combined with any other
option, excluding an include connection point with a Non-Stop flight category.
The example below illustrates a low fare search including an optional FlightCategory element specified with
the following information. Query Requirements:
Trip from Paris to New York

Non-Stop and Direct flight categories requested for entire trip
Direct Flight category for 2nd segment connection Miami to New York
Requesting
Specified Data


RC
Maximum # of recommendations requested
200
Adult Passenger type code
ADT
Passenger type code applicable to 1st passenger
Non-Stop Flight Category request applicable for

entire trip
Direct Flight Category request applicable for entire

trip
Applicable on 1st segment
Trip departure city of Paris
PAR
Trip arrival city of Miami
MIA
Trip Date 20 Dec, 2001
201201
Page 91 of 714
Applicable on 2nd segment
Trip departure city of Miami
MIA
Trip arrival city of Paris
NYC
Trip Date 25January,2002
250102
Direct Flight Category request

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<flightDetail>
<flightType>N</flightType>
<flightType>D</flightType>
</flightDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
Page 92 of 714
<date>201210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
<flightInfo>
<flightDetail>
</flightDetail>
</flightInfo>
</itinerary>

Invalid Flight Category
If an unknown Flight Category is specified in the entry, the entire request is rejected and the following
error message is returned:
"INVALID FLIGHT CATEGORY"
Invalid Flight Category
If an Include Connecting Point is specified at the same time as a Non-Stop Flight Category option, the
entire request is rejected and the following error message is returned:
"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION"
Page 93 of 714
5.4 Operation: 02.03 Flight Option - Connection Point
Connection points must be segment specific. They may be combined with any other option, excluding the
Non-Stop flight category - in which, an error message is not returned, but the connection point specified is
ignored. Connecting points to include may be combined with the connection points to exclude, providing the
same connection points are not used for both categories.
One additional specific combination restriction for preferred connection option: preferred connecting point
option can be combined with any other option except the Non-Stop flight category option and the preferred
airline option.
The connection points are 3-character IATA City or Airport codes. When an include connecting point option is
specified, all itineraries returned must at least go via this connecting point. When two include connecting points
are requested, proposed itineraries must at least go via both these connecting points in the order specified in
the entry. The Change of Gauge and direct flights whose stops are in the requested point are not selected there.
Direct flights, Change of Gauge (COG) and connections that have at least one stop at one of the exclude
connect points are excluded. When two excluded connecting points are specified, any itinerary going through
one of those connecting points is excluded.
If an exclude connecting point is specified at the same time as a Non-Stop flight category option, the system
returns Non-Stop flights recommendations and ignores the connecting point requested.
If an airport code is specified as an excluded connecting point, the alternate airports associated to the same
city are candidates to the selection.
If a city code is specified as an excluded connecting point, all airports associated to that city are excluded.
When a preferred connecting point option is specified, the system will use it to build preferred proposed
segments. Those preferred proposed segments will go via at least one of the preferred connecting points
requested. These preferred proposed segments will be considered by the system when building the
recommendations. The Change of Gauge and direct flights whose stops are in the requested point are not
selected here.
Preferred connecting point can be used to ensure that proposed segments considered by the system when
building recommendations will include online solutions on those connecting points. This option does not ensure
that recommendations returned by Master Pricer will include such proposed segments as the objective is still
to propose the lowest available recommendations.
Examples:
Parameter
Information
Include Connecting Point: MAD
Itineraries via, at least, MAD
Include Connecting Points: PAR, JFK
Itineraries via, at least, PAR and JFK in that order
Exclude Connecting Point: FRA
Exclude any Direct, COG and Connections via FRA
Include Connecting Point: NYC
Itineraries via, at least, any Airport of NYC except

JFK
Exclude Connecting Point: JFK

Exclude Connecting Point: LON, ROM
Exclude any Direct, COG, Connections via FRA or

ROM
Include Connecting Point: LON
Itineraries via, at least, LON and Exclude Direct,

Connections and COG that go through SIN
Exclude Connecting Point: SIN
Page 94 of 714
Include Connecting Point: JFK
Entry rejected with the appropriate message
Exclude Connecting Point: NYC

Include Connecting Point: FRA
Entry rejected with the appropriate message
Type of Flight: Non-Stop

Exclude Connecting Point: FRA
All Non-Stop from DUS to BER. In that case the

Exclude connecting point is meaningless
Type of Flight: Non-Stop

The example below illustrates a low fare search including an optional Connection Point element specified with
the following information.
Query Requirements:
Entire Itinerary: Paris - Miami Return

Exclusion of LGW airport for first requested segment
Inclusion of NYC and LON cities for second requested segment
Preferred connecting point specifies JFK airport for second requested segment
Requesting
Specified Data


RC
200
ADT
1st Segment departure city PARIS
PAR
1st Segment arrival city MIAMI
MIA
Trip Date (20 December 2001)
201201
Exclusion indicator
Location for connection point exclusion
LGW
2nd requested segment
2nd Segment departure city PARIS
MIA
2nd Segment arrival city MIAMI
PAR
Trip Date (20 January 2002)
200102
Exclusion indicator
Location for 1st connection point inclusion
NYC
Page 95 of 714
Location for 2nd connection point exclusion
LON
Location for preferred connection point
JFK

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>241108</date>
</timeDetails>
<flightInfo>
<inclusionDetail>
<inclusionIdentifier>M</inclusionIdentifier>
<locationId>LGW</locationId>
</inclusionDetail>
<inclusionDetail>
Page 96 of 714
<locationId>MAD</locationId>
</inclusionDetail>
</flightInfo>
</itinerary>

Invalid Connecting Point
If the city or the airport code does not exist, the following error message is returned:
"INVALID CONNECTING POINT"
Same City/Airport Code Cannot be Included and Excluded
If the same City/Airport code is used in the "Exclude" and in the "Include" list or if a City code is specified as an
Exclude Connecting Point and an Airport associated to that city is specified as an Include Connecting Point,
the followingerrormessageis returned:
"SAME CITY/AIRPORT CODE CANNOT BE INCLUDED AND EXCLUDED"
Non-Stop Cannot be Requested with Connect Point Option
If an Include Connecting Point is specified at the same time as a Non-Stop Flight Category option, the entire
request is rejected and the following error message is returned:
No Itinerary Found for Requested Segment
If no itinerary can be found then the entire itinerary is rejected with the message:
"NO ITINERARY FOUND FOR REQUESTED SEGMENT n"
where n is the number of the first Requested Segment that failed.
Non-Stop Cannot be Requested with Connect Point Option
If a Preferred Connecting Point is specified at the same time as a Non-Stop Flight Category option, the entire
request is rejected and the following error message is returned:
Preferred Connecting Point and Include/Exclude airline cannot be mixed
If a Preferred Connecting Point option is specified at the same time as a preferred airline option, the entire
query is rejected and the following error message is returned:
"PREFERRED AND INCLUDE/EXCLUDE AIRLINE CANNOT BE MIXED"
Page 97 of 714
5.5 Operation: 02.04 Flight Option - Multicity
The user has the ability to specify alternatives cities or airports as origin and/or destination point of each
requested segment.
This option may be combined with any other option except:
the origin/destination area option (radius) on the same origin or destination point of a requested
segment.
the multicity option.

When a Multicity option is specified, search is extended to the whole list of cities and airports specified in the
entry.
The maximum number of origin/destination combinations per requested segment is 6.
When more combinations are possible on a requested segment, a selection is made based on the order
specified by the user.
Examples:
Request
Process
Departure: WAS, BOS, NYC
Search will be done on the following city pairs:
Arrival: LON
- WAS - LON
- BOS - LON
- NYC - LON
Departure: LON, SOU, GLO
Search will be done on the following city pairs:
Destination: AMS, EIN, RTM
- LON - AMS
- LON - EIN
- SOU - AMS
- SOU - EIN
- LON - RTM
- SOU - GLO
The other city pairs will not be considered.

Between the origin/destination combinations considered on a requested segment (meaning, the ones selected
in the limit of 6) no preference is given in the search process.
In case Radius diversity is activated (activation by Office Id configuration):
If the requested journey is a round trip or has only one requested segment: for each main carrier,
the cheapest recommendations are returned with at least one recommendation, if it exists, per city pair
considered in the flight domain.
If the requested journey is an open-jaw: the process returns the cheapest recommendation per itinerary.
Page 98 of 714
Constraint on market
The Multicity option will not change the type of journey of the transaction (domestic/international). The type of
journey is defined by requested points of the transaction (the first city for points where multi-city is requested).
This means that:
If the journey is domestic, Multicity option will consider only cities in the same country than the requested
points (international connecting points will be considered only if no domestic journey exist);
If the journey is international, Multicity option will only propose international journeys.
Examples:
Request
Process
Departure: NCE, MRS, MIL, TLN, LYS

Arrival: PAR, ROM
The considered cities combinations are the following:

-NCE-PAR
-MRS-PAR
-TLN-PAR
-LYS-PAR
Only French cities are processed since the
requested journey (according to the first cities, NCEPAR) is France domestic.
International connecting points (ex: NCE-GVA-PAR)
will be considered only if no domestic itinerary exist.
Outbound
Departure: NCE,MIL
Arrival: ROM
Inbound
Departure: ROM
Arrival: LON,MIL
Journey is international, as defined by NCE-ROMLON, the considered cities combinations are the
following:
- NCE-ROM-LON
- MIL-ROM-LON
-NCE-ROM-MIL
MIL-ROM-MIL is not considered
(international connecting journey on domestic
requested points like MIL-GVA-ROM-MIL are not
considered).
Constraint between Requested Segments

If the requested journey (the journey constructed with the requested point) is Round Trip (RT), only RT
itineraries will be processed.
Page 99 of 714
Examples:
Request
Process
Outbound
Departure: NCE, MRS, LYS, TLN
Arrival: PAR
Inbound
Departure: PAR
Arrival: NCE, MRS, LYS, TLN, MPL
The considered cities combinations are the following:

-NCE-PAR-NCE
-MRS-PAR-MRS
-TLN-PAR-TLN
NCE-PAR-MRS is not processed since it is not a
round trip and the requested itinerary is a round trip.
The example below illustrates a low fare search including an optional Multicity element specified with the
following information:
Query Requirements:
1st segment search multiple departure cities (Paris or Lille) matching multiple arrival cities (Fort
Lauderdale)
Requesting
Specified Data
Request bynumberof seats occupied by passengers PX

Request specific maximumnumberof

RC
200
Adult Passengertypecode
ADT
Passengertypecodeapplicable to 1st passenger
Applicable 1st segment
Multiple departurecity1 of Paris
PAR
Multiple departurecity2 of Lille
LIL
Multiple arrivalcity1 of Miami
MIA
Multiple arrivalcity2 of Fort Lauderdale
FLL
201201

<numberOfUnit>
<unitNumberDetail>
Page 100 of 714
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
</depMultiCity>
<depMultiCity>
<locationId>LIL</locationId>
</depMultiCity>
<arrivalMultiCity>
</arrivalMultiCity>
<arrivalMultiCity>
<locationId>FLL</locationId>
</arrivalMultiCity>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>

City/Airports Must be in Same Country
Page 101 of 714
At each Origin/Destination level of each Requested Segments, all Cities and/or Airports must belong to
the same country. If this check fails, the entire entry is rejected with the following error message:
"CITY/AIRPORTS MUST BE IN SAME COUNTRY".
Page 102 of 714
5.6 Operation: 02.05 Flight Option - Origin Destination Area

A radius of search may be specified on any Origin and/or Destination point of each requested segment.
The units of measure for a radius search must be specified in kilometers. A maximum radius of 300 kilometers
may be specified.
The Area of search is restricted to the cities/airports in the same country as the city/airport of reference.
Whenever the reference point of the area is an airport, all the airports of its city are considered in the request,
as long as they are in the same country.
When an Origin/Destination area option is specified, search is extended to all the cities/airports existing in the
requested area providing these cities/airports belong to the same country as the city/airport of reference.
Examples:
Type Of Request
Process With Example
FLL Fort Lauderdale (city) - No radius
Fort Lauderdale (any airport)
FLL Fort Lauderdale (city) - Radius: 150 km
Fort Lauderdale - Miami
FLL Fort Lauderdale (city) - Radius: 300 km
Fort Lauderdale - Miami - Orlando
LON London (city) - No radius
London (any airport)
LHR Heathrow (airport) - No radius
Heathrow airport
LHR Heathrow (airport) - Radius: 0 km
London (any airport)
LHR Heathrow (airport) - Radius: 5 km
Heathrow airport
EAP Basel Mulhouse (city) - No radius
Any airport attached to EAP in Switzerland (does not

include MLH)
BSL Basel (airport) - No radius
Basel airport
EAP Basel Mulhouse (city) - Radius: 25 km

include MLH)
BSL Basel (airport) - Radius: 0 km

include MLH)
MLH Mulhouse (airport) - Radius: 0 km

Mulhouse in France (ignores BSL)
Technical constraints may lead to a limited search. In such a case, preference is given to the cities of the area
whose density is higher and that are closer to the city of reference.
To do so, a 2-step selection will be used, for technical reasons:
Select the cities within the specified radius.
Select highest density cities by decreasing density. Same density cities closer to the reference city
are preferred.
Since density and distance are repeated for each city pair, these values may be modified manually to handle
specific cases where a city should not be selected, despite its high density, due to its relative inaccessibility.
For example eliminate Bastia from a Nice + 300 Km request. The density of the city of reference is normally not
considered, since the city of reference is normally always used. However, a manual modification of the density
value should allow tuning for specific cases.
Page 103 of 714
When many cities must be considered for both end points of a requested segment, both end point variety
must be handled fairly in the search process: no preference should be given to the variety of cities at Origin,
compared to the variety at destination, and vice versa.
Examples:
Type Of Request
Departure: NCE and any airport within a radius of
300 km
Process With Example

Process in priority solutions:
(=> Considered city order: NCE, MRS, TLN, and so

on)
Arrival: PAR
between NCE and PAR,

then MRS and PAR,
then TLN and PAR.
No Airport in Italy is considered.
Departure: NCE and any airport within a radius of

300 km
Process in priority solutions:
(=> Considered city order: NCE, MRS, TLN, and so

on)
Arrival: TLS and any Airport within a radius of 300
km
between NCE and TLS,

then MRS and TLS,
then NCE and BOD,
then NCE and MPL.
No airport in Italy or in Spain is considered.
(=> Considered city order: TLS, BOD, MPL, and so

on)
The example below illustrates a low fare search including an optional Origin/Destination area element specified
with the following information.
Query Requirements:
First requested segment:

Departure MUC city + 150 km.
Arrival HOU airport + 100 km.
Second requested segment:
Departure from HOU.
Arrival MUC.
Requesting
Specified Data


RC

returned
200
ADT
Page 104 of 714
Specified Search Radius of 150km
150
Specified units of measure for Kilometers
Target departure search city of Munich
MUC
Specified Search Radius of 100km
100
Specified units of measure for Kilometers
Target arrival search city of Houston
HOU
Trip Date 20Dec,2001
201201
Identify Houston as an airport
Applicable 2nd segment
Departure from Houston
HOU
Identify Houston as a city code
Arrival in Munich
MUC
Trip Date 25 January 2002
250102

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<distance>150</distance>
Page 105 of 714
<distanceUnit>K</distanceUnit>
<locationId>MUC</locationId>
</departurePoint>
<locationId>HOU</locationId>
<airportCityQualifier>A</airportCityQualifier>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<airportCityQualifier>C</airportCityQualifier>
</departurePoint>
<timeDetails>
<date>250106</date>
</timeDetails>
</itinerary>

Conflicting Multi-City Options
Page 106 of 714
If an Origin/Destination Area option and a Multi-city option are both specified at the same time on the same
Origin or Destination point, the entire entry is rejected with the following error message:
"CONFLICTING MULTI-CITY OPTIONS".
Conflicting Multi-City Options
The radius must be between 0 and 300km. If this check fails, the entire request is rejected with the following
error message:
"INVALID RADIUS - MAXIMUM ALLOWED 300KM"
Invalid Value - departureLocalization/arrivalLocalization
If the unit of measure is not specified or is specified as anything other than Kilometers (K), the entire query
will be rejected and depending on whether the radius search was requested on the departure or arrival
location one of the following applicable error message:
"INVALID VALUE - DEPARTURELOCALIZATION" or "INVALID VALUE - ARRIVALLOCALIZATION"
Page 107 of 714
5.7 Operation: 02.06 Flight Option - No Slice and Dice

Slice and Dice process is applied by default. The user has the ability to disable Slice and Dice process with
an option in the query.
When this option is requested, Slice and Dice is disabled in the availability request. As no extra availability is
returned, no recommendation with Slice and Dice context will be returned.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RP</priceType>
<priceType>RW</priceType>
<priceType>NSD</priceType>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
<corporateQualifier>RW</corporateQualifier>
<identity>012345</identity>
</corporateId>
</corporate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
Page 108 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>
Page 109 of 714
5.8 Operation: 02.07 Flight Option - Disable Biased Preference

The flight search is performed according to office settings by default. The user has the ability to disable biased
preference display setting with an option in the query.
When this option is requested, the flight search request is performed in neutral mode, independently of the
office settings.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>NPF</priceType>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
Page 110 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>
Page 111 of 714
5.9 Operation: 02.081 Flight Option - Ticketless Access Carriers

recommendation
The user has the possibility to have included in the reply, Ticketless Access carriers recommendations or mixed
of Ticketless Access Carriers and Full Service Carriers recommendations.
The example below describes 2 recommendations. The first recommendation is a Ticketless Access Carrier
recommendation (priceType L) and the second one is a Full Service Carriers recommendation.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RU</priceType>
<priceType>ET</priceType>
<priceType>CUC</priceType>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>FBA</feeType>
<feeIdNumber>0</feeIdNumber>
</feeId>
</feeIdDescription>
<conversionRate>
<conversionRateDetail>
<currency>USD</currency>
</conversionRateDetail>
</conversionRate>
Page 112 of 714
</fareOptions>
<travelFlightInfo>
<companyIdentity>
<carrierId>MH</carrierId>
<carrierId>FD</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>HKG</locationId>
</departurePoint>
<locationId>HKT</locationId>
<timeDetails>
<date>280615</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>020715</date>
</timeDetails>
Page 113 of 714
</itinerary>

<replyStatus>
<status>
<advisoryTypeInfo>FQX</advisoryTypeInfo>
</status>
</replyStatus>
<conversionRate>
<currency>HKD</currency>
<convertedAmountLink>1</convertedAmountLink>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<propFlightGrDetail>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0340</ref>
<unitQualifier>EFT</unitQualifier>
</flightProposal>
<flightProposal>
<ref>FD</ref>
<unitQualifier>MCX</unitQualifier>
</flightProposal>
</propFlightGrDetail>
<flightDetails>
<flightInformation>
<productDateTime>
<dateOfDeparture>280615</dateOfDeparture>
<timeOfDeparture>2110</timeOfDeparture>
<dateOfArrival>280615</dateOfArrival>
<timeOfArrival>2350</timeOfArrival>
</productDateTime>
<location>
Page 114 of 714
<terminal>2</terminal>
</location>
<location>
</location>
<companyId>
<marketingCarrier>FD</marketingCarrier>
<operatingCarrier>FD</operatingCarrier>
</companyId>
<flightOrtrainNumber>525</flightOrtrainNumber>
<productDetail>
<equipmentType>320</equipmentType>
</productDetail>
<addProductDetail>
<electronicTicketing>N</electronicTicketing>
<productDetailQualifier>LCA</productDetailQualifier>
</addProductDetail>
</flightInformation>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0940</ref>
</flightProposal>
<flightProposal>
<ref>MH</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
Page 115 of 714
<location>
<locationId>KUL</locationId>
<terminal>M</terminal>
</location>
<companyId>
<marketingCarrier>MH</marketingCarrier>
<operatingCarrier>MH</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
<electronicTicketing>Y</electronicTicketing>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 116 of 714
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0330</ref>
</flightProposal>
<flightProposal>
<ref>FD</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<marketingCarrier>FD</marketingCarrier>
<operatingCarrier>FD</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
<electronicTicketing>N</electronicTicketing>
Page 117 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0800</ref>
</flightProposal>
<flightProposal>
<ref>MH</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 118 of 714
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
<priceTicketing>
<priceType>L</priceType>
</priceTicketing>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
<amountType>CR</amountType>
<amount>266.00</amount>
Page 119 of 714
</monetaryDetail>
<monetaryDetail>
<amountType>R</amountType>
<amount>1992</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<refQualifier>C</refQualifier>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<paxFareNum>1</paxFareNum>
<totalFareAmount>266.00</totalFareAmount>
<totalTaxAmount>0.00</totalTaxAmount>
<codeShareDetails>
<transportStageQualifier>V</transportStageQualifier>
<company>FD</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<textSubjectQualifier>LTD</textSubjectQualifier>
<informationType>43</informationType>
<description>LAST TKT DTE</description>
<description>28JUN15</description>
<description> - FARE DISC THIS DATE</description>
Page 120 of 714
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<productInformation>
<cabinProduct>
<rbd>Z</rbd>
<cabin>C</cabin>
<avlStatus>9</avlStatus>
</cabinProduct>
<fareProductDetail>
<fareBasis>Z</fareBasis>
<passengerType>ADT</passengerType>
<fareType>RP</fareType>
</fareProductDetail>
<breakPoint>Y</breakPoint>
</productInformation>
</groupOfFares>
<majCabin>
<bookingClassDetails>
<designator>C</designator>
</bookingClassDetails>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Z</rbd>
<cabin>C</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>Z</fareBasis>
</groupOfFares>
<majCabin>
Page 121 of 714
<designator>C</designator>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>MH</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
Page 122 of 714
<fare>
<pricingMessage>
<textSubjectQualifier>PEN</textSubjectQualifier>
<description>PENALTY APPLIES</description>
</pricingMessage>
<monetaryInformation>
<monetaryDetail>
<amountType>MT</amountType>
</monetaryDetail>
</monetaryInformation>
</fare>
<fare>
<pricingMessage>
<description>28JUN15</description>
<description> - DATE OF ORIGIN</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QBC3MHK</fareBasis>
<breakPoint>N</breakPoint>
</groupOfFares>
<groupOfFares>
Page 123 of 714
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
<designator>M</designator>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 124 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 125 of 714
5.10 Operation: 02.082 Flight Option - Exclude Ticketless Access Carriers

The user has the possibility to have included in a traditional Master Pricer response message, Ticketless Access
carriers recommendations or mixed of Ticketless Access Carriers and Full Service Carriers recommendations.
The user has the possibility, via XLC option, to exclude from the response Message TLA Recommendations.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>XLC</priceType>
</pricingTicketing>
Page 126 of 714
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
</depMultiCity>
<arrivalMultiCity>
</arrivalMultiCity>
<timeDetails>
<date>140803</date>
</timeDetails>
</itinerary>
Page 127 of 714
5.11 Operation: 02.09 Flight Option - Ignore Availability

The user has the ability to ignore the real availability for flight selection: all returned booking codes are
considered as available.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>IAV</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>140815</date>
</timeDetails>
</itinerary>

Page 128 of 714
Page 129 of 714
5.12 Operation: 02.10 Flight Option - Number of Connections

A number of connections can be requested for connecting flights category in such case the flights considered
in the process are restricted to connecting flights with exactly the specified number of connections.
The example below illustrates a low fare search including an optional FlightCategory element specified with
Query Requirements:
Trip from Paris to New York

Non-Stop and Direct flight categories requested for entire trip
Connecting flight category for 2nd segment with 2 connections points Miami to New York

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<flightDetail>
</flightDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 130 of 714
<timeDetails>
<date>201210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
<flightInfo>
<unitNumberDetail>
<typeOfUnit>C</typeOfUnit>
</unitNumberDetail>
</flightInfo>
</itinerary>
Page 131 of 714
5.13 Operation: 02.11 Flight Option - Online Option at Itinerary Level

This option forces the process to return online travel solutions only for all requested segments, even if cheaper
recommendations mixing carriers exist.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<flightDetail>
<flightType>OL</flightType>
</flightDetail>
<unitNumberDetail>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>BIQ</locationId>
</departurePoint>
Page 132 of 714
<timeDetails>
<date>151010</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201010</date>
</timeDetails>
</itinerary>
If at the same level, the Online option is combined with the Include Airline option used on YY airline
code: the entire entry is rejected with the following message:
INVALID COMBINATION OF OPTION
Include option used with one or more specific airlines code: the process will only return online travel solutions
of those specifics airlines).
Page 133 of 714
5.14 Operation: 02.12 Flight Option - Online Option at Requested Segment

Level
When this option is only requested on one requested segment, there is no constraint on the other requested
segments, meaning that interline solution may be returned for requested segments on which online option is
not requested.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>151010</date>
</timeDetails>
<flightInfo>
<flightDetail>
Page 134 of 714
<flightType>OL</flightType>
</flightDetail>
</flightInfo>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201010</date>
</timeDetails>
</itinerary>

See "Error Messages" section.
Page 135 of 714
5.15 Operation: 02.13 Flight option - Interline

The user has the ability to request only interline solutions, meaning recommendations built with flights marketed
by different carriers.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>INL</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120202</date>
</timeDetails>
Page 136 of 714
</itinerary>

Page 137 of 714
5.16 Operation: 02.14 Flight option - Maximum EFT

The user can define in input a maximum elapsed flying time (EFT) to be returned. The maximum EFT is a
percentage (100) of the shortest EFT returned by the journey server.
This option can also be requested at requested segment level. In the example below, the maximum EFT is
requested at itinerary level.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>P</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 138 of 714
<timeDetails>
<date>201212</date>
</timeDetails>
</itinerary>

Page 139 of 714
5.17 Operation: 02.15 Flight option - Maximum layover per connection

The user can request a maximum layover per connection (in hours and in minutes).
Each connection of each requested segment has a layover limited to X hours and Y minutes.
This option can also be requested at requested segment level.
In the example below, it is requested at itinerary level.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>MLH</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>MLM</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 140 of 714
<timeDetails>
<date>201208</date>
</timeDetails>
</itinerary>

Page 141 of 714
5.18 Operation: 02.16 Flight option - Total Maximum layover

The user can request a total maximum layover (sum of the layovers of the requested segment) not to go beyond
at itinerary level in hours (MSH) and in minutes (MSM). It will then be applied for each requested segment.
This option can also be requested at requested segment level, and then, it would be applied only for the
specified requested segment.
In the example below, it is applied at itinerary level.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>MSH</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>MSM</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 142 of 714
<timeDetails>
<date>201208</date>
</timeDetails>
</itinerary>

Page 143 of 714
5.19 Operation: 02.17 Flight option - RDI: Radius/multicity at itinerary level

The search on a radius is extended to all cities/airports of any country for any requested point.
Default: When no radius is specified, the process is applied only to requested city/airport.
When the radius is specified with no cross border option, only cities/airports in the same country as the city/
airport of reference are considered.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RDI</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>CPH</locationId>
Page 144 of 714
<timeDetails>
<date>011214</date>
</timeDetails>
</itinerary>

Page 145 of 714
5.20 Operation: 02.18 Flight option - IR: Radius/multicity at requested

segment level
The search on a radius is extended to all cities/airports of any country for any requested points with the cross
border option and to all cities/airports in the same country as the city/airport of reference for requested points
without the cross border option.
When no radius is specified, the process is applied only to requested city/airport.
When the radius is specified with no cross border option, only cities/airports in the same country as the city/
airport of reference are considered.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<attributeDetails>
<type>IR</type>
</attributeDetails>
<timeDetails>
<date>011214</date>
Page 146 of 714
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
<currency>EUR</currency>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0130</ref>
</flightProposal>
<flightProposal>
<ref>SK</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>STR</locationId>
</location>
Page 147 of 714
<location>
</location>
<companyId>
<marketingCarrier>SK</marketingCarrier>
<operatingCarrier>SK</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>CR9</equipmentType>
</productDetail>
<addProductDetail>
<productDetailQualifier>AVR</productDetailQualifier>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0730</ref>
</flightProposal>
<flightProposal>
<ref>BT</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>PRG</locationId>
</location>
<location>
<locationId>RIX</locationId>
Page 148 of 714
</location>
<companyId>
<marketingCarrier>BT</marketingCarrier>
<operatingCarrier>BT</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>DH4</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>RIX</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>BT</marketingCarrier>
<operatingCarrier>BT</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
Page 149 of 714
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>0715</ref>
</flightProposal>
<flightProposal>
<ref>AB</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>NUE</locationId>
</location>
<location>
<locationId>DUS</locationId>
</location>
<companyId>
<marketingCarrier>AB</marketingCarrier>
<operatingCarrier>AB</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
Page 150 of 714
</productDateTime>
<location>
<locationId>DUS</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>AB</marketingCarrier>
<operatingCarrier>AB</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>4</ref>
</flightProposal>
<flightProposal>
<ref>0605</ref>
</flightProposal>
<flightProposal>
<ref>IB</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>ZRH</locationId>
Page 151 of 714
<terminal>B</terminal>
</location>
<location>
<locationId>BCN</locationId>
</location>
<companyId>
<marketingCarrier>IB</marketingCarrier>
<operatingCarrier>VY</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 152 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>5</ref>
</flightProposal>
<flightProposal>
<ref>0605</ref>
</flightProposal>
<flightProposal>
<ref>VY</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>ZRH</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>VY</marketingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 153 of 714
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
Page 154 of 714
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>SK</company>
</codeShareDetails>
<pricingTicketing>
<priceType>OBV</priceType>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>TICKETS ARE NON-REFUNDABLE</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>25JUL14</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
Page 155 of 714
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ODEOWM</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
Page 156 of 714
<codeShareDetails>
<company>BT</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>K</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>KCZTH9</fareBasis>
Page 157 of 714
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>K</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>KCZTH9</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
Page 158 of 714
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>AB</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>W</rbd>
<cabin>M</cabin>
Page 159 of 714
</cabinProduct>
<fareProductDetail>
<fareBasis>WNCOW</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>W</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>WNCOW</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>4</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
Page 160 of 714
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>IB</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
Page 161 of 714
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>PRTNVY</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QRTNVY</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>5</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
Page 162 of 714
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>VY</company>
</codeShareDetails>
<codeShareDetails>
<company>HR</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
<monetaryDetail>
</monetaryDetail>
</fare>
Page 163 of 714
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>PRTVY</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>W</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>WRTVY</fareBasis>
</groupOfFares>
<majCabin>
Page 164 of 714
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 165 of 714
5.21 Operation: 02.20 Flight option - No airport change at itinerary level

This option aims to restrict offering recommendations involving connections with an airport change in the multiairports cities indicated in the query.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>NAC</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201212</date>
</timeDetails>
</itinerary>
Page 166 of 714
Page 167 of 714
5.22 Operation: 02.21 Flight option - No airport change at requested segment

level
This option aims to restrict offering recommendations involving connections with an airport change in the multiairports cities indicated in the query.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201208</date>
</timeDetails>
<flightInfo>
<unitNumberDetail>
<typeOfUnit>NAC</typeOfUnit>
</unitNumberDetail>
</flightInfo>
Page 168 of 714
</itinerary>
Page 169 of 714
5.23 Operation: 02.22 Duplicated recommendations: Keep solutions with

more ground time at last connecting point
When RDG option is indicated in the input, two or more recommendations are defined as duplicated if:
All their proposed segments are exactly the same except one proposed segment, meaning they only
have one differentiable segment.
Their differentiable segments have: three or more legs, same routing, same marketing carrier
combination and same departure time at origin point and arrival time at destination point.
When two recommendations are duplicated as defined above, the solutions with the maximum ground time at
the last connecting point are considered to have better quality.
Among a group of duplicate recommendations defined above, this option compares the price and quality of
their differentiable proposed segment, and remove the ones which have worse quality and higher/equal price
than at least one duplicate recommendation (feeder).

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RDG</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 170 of 714
<timeDetails>
<date>201212</date>
</timeDetails>
</itinerary>
Page 171 of 714
5.24 Operation: 02.23 Duplicated recommendations: Keep the best solutions

per major flight
When RDM option is indicated in the input, two or more recommendations are defined as duplicated if:
all their proposed segments are exactly the same except one proposed segment, meaning they only
have one differentiable segment.
their differentiable segments have: same routing, same marketing carrier combination, and a same
major flight, which is a flight representing at least 60% of total EFT (Elapsed Flying Time).
When two recommendations are duplicated as defined above, this option compares their departure time at
origin point (DP)and arrival time at destination point (AR). Recommendations are considered to have worse
quality if they have same DP and later AR, same AR and earlier DP, and, earlier DP and later AR.
Among a group of duplicate recommendations defined above, this option compares the price and quality of
their differentiable proposed segment, and remove the ones which have worse quality and higher/equal price
than at least one duplicate recommendation (feeder).

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RDM</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
Page 172 of 714
</departurePoint>
<timeDetails>
<date>201212</date>
</timeDetails>
</itinerary>
Page 173 of 714
5.25 Operation: 02.24 Flight option - City or Airport Indicator at itinerary level
This option indicates whether the included or excluded location indicates a city or an airport.
This option is also available at requested segment level. In this example, Los Angeles city is included in the
search.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<inclusionDetail>
<locationId>LAX</locationId>
</inclusionDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
</depMultiCity>
<arrivalMultiCity>
</arrivalMultiCity>
<timeDetails>
<date>201203</date>
Page 174 of 714
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251203</date>
</timeDetails>
</itinerary>
Page 175 of 714
5.26 Operation: 02.25 Flight Option - Anchored Search (Basic mode)

When FSParam Gb_AnchoredSearch is set to 2, the user has the possibility to freeze one or more
requested segments by providing, for all the anchored requested segments, the following initial travel solution
informations :
Departure/Arrival airport
Departure date
Departure time
Marketing carrier
Flight number
The example below illustrates the following request:
Parameter
Value
Departure airport
ORY
Arrival airport
NCE
Departure date
20141020
Departure time
0640
Marketing Carrier
AF
Flight number
6240

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
Page 176 of 714
<priceType>ACS</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>NCE</locationId>
</departurePoint>
<timeDetails>
<date>151014</date>
</timeDetails>
<requestedSegmentAction>
<actionRequestCode>MF</actionRequestCode>
</requestedSegmentAction>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201014</date>
</timeDetails>
<flightInfoPNR>
Page 177 of 714
<travelResponseDetails>
<flightDate>
<departureDate>20141020</departureDate>
<departureTime>0640</departureTime>
<dateVariation/>
</flightDate>
<boardPointDetails>
<trueLocationId>ORY</trueLocationId>
</boardPointDetails>
<offpointDetails>
<trueLocationId>NCE</trueLocationId>
</offpointDetails>
<companyDetails>
<marketingCompany>AF</marketingCompany>
</companyDetails>
<flightIdentification>
<flightNumber>6240</flightNumber>
</flightIdentification>
</travelResponseDetails>
</flightInfoPNR>
</itinerary>
Page 178 of 714
5.27 Operation: 02.26 Flight Option - Anchored Search (Full mode without
technical stop)
When FSParam Gb_AnchoredSearch is set to 1, the user has the possibility to freeze one or more
requested segments by providing, for all the anchored requested segments, the following initial travel solution
informations, in addition of the informationrequired for basic mode:
Arrival date
Arrival time
Date variation indicator
Aircraft type
EFT of the proposed segment
Elapsed ground time (mandatory for connecting flights except on the first leg of the connection)
If available, those informations may be also required:
Operating Carrier
Operational Suffix
Flight portion type
Elapsed flying time of the flight
Terminal of origin/destination
Mandatory elements:
Parameter
Value
Arrival date
20141020
Arrival time
0800
Date variation indicator
Aircraft type
320
EFT of the proposed segment
80
Required elements:
Parameter
Value
Operating carrier
AF
Operational suffix
Flight portion type
Elapsed flying time of the flight
80
Terminal of origin
Terminal of destination

Page 179 of 714
<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>151014</date>
</timeDetails>
Page 180 of 714
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201014</date>
</timeDetails>
<flightInfoPNR>
<flightDate>
<arrivalDate>20141020</arrivalDate>
<arrivalTime>0800</arrivalTime>
<dateVariation>0</dateVariation>
</flightDate>
<boardPointDetails>
<trueLocationId>ORY</trueLocationId>
<offpointDetails>
<trueLocationId>NCE</trueLocationId>
</offpointDetails>
<companyDetails>
<marketingCompany>AF</marketingCompany>
</companyDetails>
<operationalSuffix>A</operationalSuffix>
<flightTypeDetails>
<flightIndicator>S</flightIndicator>
</flightTypeDetails>
<terminalEquipmentDetails>
Page 181 of 714
<legDetails>
<equipment>320</equipment>
<duration>80</duration>
</legDetails>
<departureStationInfo>
<terminal>W</terminal>
</departureStationInfo>
<arrivalStationInfo>
</arrivalStationInfo>
</terminalEquipmentDetails>
<legDetails>
</legDetails>
<codeshareData>
<codeshareDetails>
<transportStageQualifier>O</transportStageQualifier>
<airlineDesignator>AF</airlineDesignator>
</codeshareDetails>
</codeshareData>
</flightInfoPNR>
</itinerary>
Page 182 of 714
5.28 Operation: 02.27 Flight Option - Anchored Search (Full mode with
technical stops)
In case of technical stop, the following items need also to be provided:
Technical stop destination date
Technical stop origin date
Technical stop destination time
Technical stop origin time
Aircraft type of the second flight
City of the stop

Parameter
Value
Technical stop destination date
151014
Technical stop origin date
151014
Technical stop destination time
1905
Technical stop origin time
2020
Aircraft type of the 2nd flight
AF
City of the stop
BKK

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
Page 183 of 714
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>CHC</locationId>
</departurePoint>
<timeDetails>
<date>151014</date>
</timeDetails>
<flightInfoPNR>
<flightDate>
</flightDate>
<boardPointDetails>
<trueLocationId>CHC</trueLocationId>
<offpointDetails>
<trueLocationId>BNE</trueLocationId>
</offpointDetails>
<companyDetails>
<marketingCompany>EY</marketingCompany>
</companyDetails>
<flightTypeDetails>
<flightIndicator>S</flightIndicator>
<flightIndicator>ET</flightIndicator>
Page 184 of 714
<legDetails>
<equipment>73H</equipment>
</legDetails>
<legDetails>
</legDetails>
<codeshareData>
<codeshareDetails>
<airlineDesignator>VA</airlineDesignator>
</codeshareDetails>
</codeshareData>
</flightInfoPNR>
<flightInfoPNR>
<flightDate>
</flightDate>
<boardPointDetails>
<trueLocationId>BNE</trueLocationId>
<offpointDetails>
<trueLocationId>AUH</trueLocationId>
</offpointDetails>
<companyDetails>
</companyDetails>
<flightTypeDetails>
<flightIndicator>C</flightIndicator>
<legDetails>
Page 185 of 714
</legDetails>
<mileageTimeDetails>
<elapsedGroundTime>0500</elapsedGroundTime>
</mileageTimeDetails>
<codeshareData>
<codeshareDetails>
<airlineDesignator>EY</airlineDesignator>
</codeshareDetails>
</codeshareData>
<incidentalStopInfo>
<dateTimeInfo>
<dateTimeDetails>
<qualifier>AA</qualifier>
<date>151014</date>
<time>1905</time>
<reserved2>BKK</reserved2>
</dateTimeDetails>
<dateTimeDetails>
<qualifier>AD</qualifier>
<date>151014</date>
<time>2020</time>
<reserved1>332</reserved1>
</dateTimeDetails>
</dateTimeInfo>
</incidentalStopInfo>
</flightInfoPNR>
<flightInfoPNR>
<flightDate>
</flightDate>
<boardPointDetails>
<trueLocationId>AUH</trueLocationId>
<offpointDetails>
<trueLocationId>MUC</trueLocationId>
</offpointDetails>
<companyDetails>
</companyDetails>
Page 186 of 714
<flightTypeDetails>
<flightIndicator>E</flightIndicator>
<legDetails>
</legDetails>
<mileageTimeDetails>
<elapsedGroundTime>0225</elapsedGroundTime>
</mileageTimeDetails>
<codeshareData>
<codeshareDetails>
<airlineDesignator>EY</airlineDesignator>
</codeshareDetails>
</codeshareData>
</flightInfoPNR>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<locationId>CHC</locationId>
<timeDetails>
<date>201014</date>
</timeDetails>
</itinerary>
Page 187 of 714
Page 188 of 714
5.29 Operation: 02.28 Flight Option - More Overnights

This option (OVN) allows to return more overnight solutions if they are part of the cheapest solutions. Overnight
solutions are solutions with a segment containing a connection with first flight arriving before or at 11:59 PM
and second flight starting after or at 5:00 AM.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>OVN</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>BOS</locationId>
</departurePoint>
<locationId>GRX</locationId>
<timeDetails>
<date>120913</date>
Page 189 of 714
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<locationId>GRX</locationId>
</departurePoint>
<timeDetails>
<date>230913</date>
</timeDetails>
</itinerary>
Page 190 of 714
5.30 Operation: 02.29 Flight Option - Search with Point of Commencement

Some shopping customers are triggering Master Pricer transactions in a context where the real point of
commencement is not the origin of the first requested segment. For example, searching for One-Way solutions
on the return bound.
If chosen solution is not booked in a separated PNR then the airline inventory may reject the booking.
For such shopping customers which can't handle the creation of separated PNRs, it is required to offer the
possibility to indicate the real point of commencement in input of Master Pricer queries, and the search process
to use it for retrieving the appropriate availability context.
The example below illustrates a search for a One-Way from New York to Nice where the real point of
commencement is Nice.
Point of commencement (Nice)
NCE
Date of commencement (1 April 2015)
DOC
010415

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
<journeyOriginPoint>
</journeyOriginPoint>
</pricingTickInfo>
<feeIdDescription>
Page 191 of 714
<feeId>
<feeType>DOC</feeType>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>070415</date>
</timeDetails>
</itinerary>
Page 192 of 714
5.31 Operation: 02.30 Flight Option - Search with CLID
The corporate recognition is used to identify corporate traveller that travels for business reasons and who can
benefit from special contracts linked to a corporate account. Airlines are able to provide enhanced availability
for certain corporate customer. Such biased availability computation relies on the CLID number, a unique ID
number by carrier.
The example below illustrates a Search with a CLID number. Each CLID is described with a company code
and a corporate identifier.
Requesting
Specified Data

ADT
Include public fares in the search
RP
Include unifares in the search
RU
Client ID carrier and number
LH
C100107371656
2
Applicable 1st requested segment
Departure city of Frankfurt
FRA
NYC
Trip Date (22 June 2014)
220614
Applicable 2nd requested segment
Departure city of New York
NYC
Arrival city of Frankfurt
FRA
Trip Date (6 July 2014)
060714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
Page 193 of 714
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<frequentTravellerInfo>
<frequentTravellerDetails>
<carrier>LH</carrier>
<number>C100107371656</number>
<type>2</type>
</frequentTravellerDetails>
</frequentTravellerInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>FRA</locationId>
</departurePoint>
<timeDetails>
<date>220614</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
Page 194 of 714
<timeDetails>
<date>060714</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0851</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 195 of 714
</productDateTime>
<location>
</location>
<location>
<locationId>JFK</locationId>
</location>
<companyId>
<marketingCarrier>AF</marketingCarrier>
<operatingCarrier>DL</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>76W</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0808</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
Page 196 of 714
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<operatingCarrier>DL</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 197 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>AF</company>
</codeShareDetails>
<pricingTicketing>
<priceType>OBF</priceType>
<priceType>OBA</priceType>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*26FEB14* - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
Page 198 of 714
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VKPR0DE</fareBasis>
<fareType>RA</fareType>
<ticketInfos>
<additionalFareDetails>
<ticketDesignator>JUX31</ticketDesignator>
</additionalFareDetails>
</ticketInfos>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VKPR0DE</fareBasis>
<ticketInfos>
<ticketDesignator>JUX31</ticketDesignator>
Page 199 of 714
</ticketInfos>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 200 of 714
5.32 Operation: 02.31 Flight Option - DK number (customer identification)

Travel Management companies / travel agencies (both online and offline) may handle accounts for many
different corporations / customers and may wish to apply certain business rules when making travel
arrangements for these customers.
These "business rules" can be taken into consideration and validated by Amadeus when returning Fare
Shopping results - provided that the specific customer / rule to apply (if any) has been identified in the input
message received from the agency. This identification is made via the "DK" number / customer identification
number received.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<customerRef>
<customerReferences>
<referenceQualifier>701</referenceQualifier>
<referenceNumber>AA1234567890123456789Z01234567890</referenceNumber>
</customerReferences>
</customerRef>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>PPT</locationId>
<timeDetails>
Page 201 of 714
<date>100812</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<locationId>PPT</locationId>
</departurePoint>
<timeDetails>
<date>200812</date>
</timeDetails>
</itinerary>
Page 202 of 714
5.33 Operation: 02.32 Flight Option - Progressive legs

Progressive legs enables the user to request a range of number of connections relative to the minimum
connections that exist on Journey Server. This range of number of connections is the progressive legs range.
Progressive legs is triggered by input options:
Minimum number of progressive connections (MIC),

Maximum number of progressive connections (MAC).
The minimum and maximum number are numeric values from 0 to n.

The range of progressive legs can be specified at itinerary level or at requested segment level. If specified
both at itinerary and requested segment level, the values at requested segment level override the values at
itinerary level.
The example below illustrates a search with progressive legs range specified at itinerary level.
Requesting Details
Specified Data
Request by number of seats occupied by passengers
PX
Number of seats for request
Adult passenger type code
ADT
Public fares requested
RP
Progressive legs range with a minimum of 0 connection and a

maximum of 1 connection
0
MIC
1
MAC
1
Departure city of Denver
DEN
Arrival city of Los Angeles
LAX
111215
2 nd requested segment
2
Departure city of Los Angeles
LAX
Arrival city of Boston
BOS
181215
Page 203 of 714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>MIC</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>MAC</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>DEN</locationId>
</departurePoint>
<timeDetails>
Page 204 of 714
<date>111215</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>181215</date>
</timeDetails>
</itinerary>
Page 205 of 714
5.34 Operation: 03.1 Time Option - Time of Departure/Arrival

The time option can be:
A time of departure (TD)
If no range of dates is requested, search for flights that depart between the requested time and 11:59PM. If a
range of dates is requested, the TD applies on the first day of the range. The search for flights applies for the
period between the TD on the first day of the range and 23h59 on the last day of the range like it is described
in the figure below.
A time of arrival (TA)
If no range of dates is requested, search for flights that arrive between 00:00AM and the requested time. If a
range of dates is requested, search for flights that arrive on the last day of the date range before the requested
time, or any time the previous day(s).
Examples:
Request
Process
Date: 10SEP01
Select flights that arrive between 00:00AM and

10:00PM on the 10SEP01.
Time of Arrival: 10:00PM

=> Arrives by 10:00PM on the 10SEP01
Date: 15OCT01
Select flights that arrive between 10:00PM and

11:59PM on the 15OCT01.
Time of Departure: 10:00PM

=> Depart from 10:00PM on the 15OCT01
Range of dates: 23AUG01 and 24AUG01
Time of Departure: 06:00PM
=> Depart from 06:00PM on the 23AUG01
Select flights that depart between 6:00PM and

11:59PM on the 23AUG01 or on the 24AUG01, at
any time.
Select flights that arrive between on 23AUG01 at any
time or on 24AUG before 06:00PM.
=> Arrive by 06:00PM on the 24AUG01

The example below illustrates a low fare search including the Times by Arrival and Departure elements specified
Query Requirements:
Departure from origin by 6pm on 23AUG01

Requesting
Specified Data

1
Page 206 of 714

RC

returned
200
ADT
Departure city of Paris
PAR
Arrival city of Miami
MIA
Identify search for departure by element
TD
Specify date for departure by 23 August 2001
230801
Specify search time for departure by 6pm
1800

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 207 of 714
<timeDetails>
<timeQualifier>TD</timeQualifier>
<date>200206</date>
<time>1800</time>
</timeDetails>
</itinerary>

Invalid Time Option
The error message "INVALID TIME OPTION" is returned in the following instances:
If an hour is specified without any indication about whether it means a Time of Departure or a Time
of Arrival
If no time is specified after the Time of Departure or the Time of Arrival indicator
Page 208 of 714
5.35 Operation: 03.2 Time Option - Time Window

Valid time range values range between 1 and 12.
The TimeWindow applies either on the Time of Departure or the Time of Arrival to restrict the search on the
flights in the range of hours around (+ and -) the requested date and time.
When requested on a unique departure/arrival date, the time window may overlap to the previous/next day
to fulfil the request.
When requested on a range of dates, the time window is interpreted on each day of the date range.
Consequently, the time window may not extend the requested date range.
Note: The Time of Departure/Arrival option with a specified date is mandatory when using this option.
Examples:
Request
Process
Date: 20AUG01
Select flights that arrive between 20AUG01 6:00PM

and 21AUG01 02:00AM

Time Window: 4 hours
=> Arrive around 10:00PM on the 20AUG01
Range of dates: 20SEP01 and 21SEP01
Time of Departure: 10:00AM
Select flights that depart between 05:00AM and

03:00PM on each requested day (20SEP01 and
21SEP01).
=> Depart around 10:00AM on the 20SEP01 or on

the 21SEP01
=> Arrive around 10:00PM on the 23AUG01 or on
the 24AUG01
Select flights that arrive on 23AUG01 or on

24AUG01: between 6:00PM 23AUG01 and 02:00AM
on the 24AUG01
Or:
between 6:00PM and 11:59PM on the 24AUG01
NB: Flights between 00:00AM and 02:00AM on the
23AUG01 are not considered.

Time of Departure: 02:00AM
=> Depart around 02:00AM on the 23AUG01 or on
the 24AUG01
Select flights that depart on 23AUG01 or on

24AUG01: between 00:00AM and 06:00AM on
23AUG01
Or:
between 10:00PM on 23AUG01 and 06:00 AM on
24AUG01
Page 209 of 714
NB: Flights between 10:00PM and 11:59PM on the

24AUG01 are not considered.
The example below illustrates a low fare search including the Times by Arrival and Departure elements specified
with an optional time Window element with the following information.
Query Requirements:
Arrival on 23AUG01 or plus one day around 10pm with time window of 4 hours.
Requesting
Specified Data


RC

returned
200
ADT
PAR
MIA
Identifytimeby arrival
TA
Specify arrival date by 23AUG01
230801
Specify arrival time by 10pm
2200
Specify applicable time window 4 hours either side of 4

10pm
Identify date range search for Plus
Number of days in date range search

1
Note: Achieving the same results, the time Window could also be specified as:
Specify arrival date by 24AUG01
240801
Specify arrival time by 10pm
2200
Specify applicable time window 4hours either side of 4

10pm
Identify date range search for Minus
Number of days in date range search

Page 210 of 714
<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<timeQualifier>TA</timeQualifier>
<date>230801</date>
<time>2200</time>
<timeWindow>4</timeWindow>
<rangeOfDate>
<rangeQualifier>M</rangeQualifier>
<dayInterval>1</dayInterval>
</rangeOfDate>
</timeDetails>
</itinerary>

Page 211 of 714

Invalid Time Window Option
The time window value varies from 1 to 12 hours. If this check fails, the entire entry is rejected with the
following message:
"INVALID TIME WINDOW OPTION"
Time of Departure/Arrival is Mandatory if Time Window Requested
If no Time of Departure/Arrival is specified, the entire request is rejected with the following error message:
"TIME OF DEPARTURE/ARRIVAL IS MANDATORY IF TIME WINDOW REQUESTED"
Date is Mandatory
If no date is specified, the entire request is rejected with the following error message:
"DATE IS MANDATORY"
Page 212 of 714
5.36 Operation: 03.3 Time Option - Range Of Dates

When a range of plus and/or minus 1 day is specified on a requested segment, search of flights applies on
a range of dates of up to three days - the current day plus and/or minus 1 day. Search is only allowed on a
range of up to three days:
Either requested date plus 2 days maximum.
Or requested date minus 2 days maximum.
Or requested date plus and minus 1 day maximum.

In the search, no preference is given to any of the dates. The only preference factor will be the price and the
carrier variety. A good distribution and variety of recommendations is expected on the different days of the
range.
The example below illustrates a low fare search including the optional range of dates element specified with
Query Requirements:
Search the departure date plus 1 day.
Search the arrival date minus 1 day.

Requesting
Specified Data


RC

returned
200
ADT
Applicable 1st Segment
Departure City Marseille
MRS
Arrival City Houston
HOU
Departure date 02Feb2002
200202
Identify date range search as Plus range
Number of days in range
Applicable 2nd segment
Force departure city same as arrival city in 1st

segment reference
Identify city of Houston for departure city
HOU
Identify arrival city of Marseille
MRS
Page 213 of 714
Arrival date 22Mar2002
220302
Identify date range search as Minus
Number of days in range

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>MRS</locationId>
</departurePoint>
<timeDetails>
<date>200204</date>
<rangeOfDate>
<rangeQualifier>P</rangeQualifier>
</rangeOfDate>
</timeDetails>
</itinerary>
Page 214 of 714
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>220304</date>
<rangeOfDate>
<rangeQualifier>M</rangeQualifier>
</rangeOfDate>
</timeDetails>
</itinerary>

Invalid Range of Dates Option
Search is only allowed on a Range of two days: meaning, the requested Date plus or minus 1 day. If a
plus or minus more than 1 day option is specified or if a plus and minus one day option is specified, the
entire entry is rejected with the following error message:
"INVALID RANGE OF DATES OPTION".
Page 215 of 714
5.37 Operation: 03.4 Time Option - Time at destination

When the user specifies 2 requested segments with close departure dates, he has the ability to specify the
minimum time in hours the user wants to stay at destination.
The time at destination is the minimum time between the arrival time and departure time of two consecutive
proposed segments. This minimum time is specified in input with the following format HHMM. Any value
between 0000 and 2359 is accepted.
The example below describes a departure on 20 Dec 2010 with a minimum stay of 5 hours at destination.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>ISB</locationId>
Page 216 of 714
<timeDetails>
<date>201210</date>
<rangeOfDate>
<timeAtdestination>0500</timeAtdestination>
</rangeOfDate>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
</itinerary>

Page 217 of 714
5.38 Operation: 04.01 Fare Option - Currency Conversion

The currency conversion option may be combined with any other option.
It is mandatory that the ticketing price type be set to "CUC" to indicate a currency conversion request. It is
mandatory for any query including the currency conversion option.
It is mandatory that a currency code be specified for the conversion. All price amounts for recommendations
are converted in the requested Currency. There is no default currency for conversion, it must be specified.
The example below illustrates a low fare search including an optional Currency Conversion element specified
Query Requirements:
Currency to be returned: EUROS

Requesting
Specified Data


RC
200
ADT
Currency Override
CUC
Currency requested for recommendations is Euros
EUR
PAR
Trip arrival city of Miami
MIA
Trip date (20 January 2006)
200106

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
Page 218 of 714
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<conversionRate>
</conversionRate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>200106</date>
</timeDetails>
</itinerary>

Invalid Currency Conversion
Page 219 of 714
If an unknown Currency is specified, the entire request is rejected and the following error message is returned:
"INVALID CONVERSION CURRENCY".
Currency must be specified
If the ticketing price type is set to currency conversion (CUC), yet a currency code is not specified for the
conversion, the entire query is rejected with the following error:
"CURRENCY MUST BE SPECIFIED"
Invalid Value - ConversionRate
If a currency code for conversion is specified, yet the ticketing price type has not be set for the currency
conversion (CUC), the entire query is rejected with the following error message:
"INVALID VALUE - CONVERSION RATE"
Page 220 of 714
5.39 Operation: 04.02 Fare Option - Selling Ticketing Cities Override
The requested selling and/or a ticketing cities are used to determine applicable fares and currency for the
recommendations. The selling and ticketing cities are applied from the requestor's system office ID city settings.
If the selling or ticketing city override option is used, the cities specified will be utilised instead of the requestor
Office id City.
The city code specified must be a valid city code stored in the Amadeus system. Airport codes may not be
utilised, unless the airport and city code are the same.
Examples:
Valid city code for Paris
PAR
Invalid city code to use for Paris
CDG
A maximum of one selling and one ticketing city may be specified applicable to the entire request. These options
may be combined together and/or with any other option.
The example below illustrates a low fare search including the optional selling/ticketing cities override element
specified with the following information.
Query Requirements:
Selling city is PAR
Ticketing city is PAR

Requesting
Specified Data


RC

returned
200
ADT
Selling city override location set to Paris
PAR
Ticketing city override location set to Paris
PAR
Departure city of Marseille
MRS
MIA
200106

<numberOfUnit>
<unitNumberDetail>
Page 221 of 714
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<sellingPoint>
</sellingPoint>
<ticketingPoint>
</ticketingPoint>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>200106</date>
</timeDetails>
</itinerary>

Page 222 of 714

Invalid Ticketing/Selling City
If the requested Selling or Ticketing city are not valid city codes in the Amadeus system, the entire request is
rejected and the following message is returned:
"INVALID TICKETING/SELLING CITY"
Page 223 of 714
5.40 Operation: 04.03 Fare Option - Price To Beat

This option may be combined with any other option.
The Price to Beat amount can be composed of up to 9 digits, and the value must be higher than zero. No
decimal placement is allowed in the input.
The currency of the Price to Beat is the requested Currency of Conversion if specified; otherwise, it is the
default selling currency that is determined as per usual pricing rules.
If no price to beat is specified, all prices will be considered valid as a qualifying recommendation.
The example below illustrates a low fare search including the optional price to beat element specified with the
following information:
Query Requirements:
Price to beat is 3500 Euros

Requesting
Specified Data


RC

returned
200
ADT
Specified price to beat
3500
PAR
MIA
201201

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
Page 224 of 714
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<priceToBeat>
<moneyInfo>
</moneyInfo>
</priceToBeat>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201201</date>
</timeDetails>
</itinerary>

Invalid Price to Beat Value
If the Price to Beat amount is composed of more than 9 digits, the value is not higher than zero, or a
decimal placement is included in the input, the entire request is rejected and the following error message
is returned:
"INVALID PRICE TO BEAT VALUE"
Page 225 of 714
No Recommendation Found with Lower or Equal Price

The Price to Beat is used as a reference. No recommendation that is returned to the user may have an
higher price. If no lower price recommendation is found, the following error message is returned:
"NO RECOMMENDATION FOUND WITH LOWER OR EQUAL PRICE".
Page 226 of 714
5.41 Operation: 04.04 Fare Option - Split / No Split PNR
When a user requests fares for several passengers, these passengers may have different Passenger Type
Codes (for example, 1 ZZ and 1 CH). If the No Split PNR option is deactivated, the system returns the cheapest
recommendations even if different booking codes have to be applied to these passengers (non-homogenous
solutions). This implies to create multiple PNR to finalise the booking.
The default process is the "No Split PNR mode": Fare Search returns recommendations where the same
booking code is applied to all passengers (homogenous solutions).
Here is the syntax to deactivate the No Split PNR option:
Fee Type
NPS
FeeIdNumber
0
The example below illustrates a low fare search including the deactivation of the No-Split PNR option:
Requesting
Specified Data


RC
200
ADT
Child Passenger type code
CH
Passenger type code applicable to 2nd passenger
Public fares included in the search
RP
NPS
Split PNR Option activated
Applicable to 1st requested segment
Trip Departure city of Paris
PAR
Trip Arrival city of Miami
MIA
Trip Date (12 February 2002)
120202

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
Page 227 of 714
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>NPS</feeType>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120202</date>
</timeDetails>
Page 228 of 714
</itinerary>
Page 229 of 714
5.42 Operation: 04.05 Fare Option - Type of Ticket (Electronic/Paper Ticket)

The paper and electronic ticket surcharge concept is driven from fare data filed by the airline.
Three new pricing options are available to allow the user to link the fare priced and the type of Fare required.
Possible values:
PT for paper ticket
ET for electronic ticket
EPfor electronic and paper ticket

Note:Electronic ticketing (ET) is not yet available in all markets or all carriers, for further details contact your
local Amadeus Help Desk for more information, to ensure that the Office Profile has been modified accordingly
and the market where the airlines are situated can benefit from Electronic ticketing (ET).
Examples:
Request
Process
If no options are entered
System will propose both Electronic and Paper

Ticket travel solutions
Request Electronic Ticket (ET) only
Electronic Ticket sent
Request PaperTicket (PT) only

Paper Ticket sent
The example below illustrates a low fare search for Electronic Ticket solutions only.
Query Requirements:
Requesting
Specified Data


RC

returned
200
ADT
Electronic ticket included in the search
ET
PAR
MIA
201205

Page 230 of 714
<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>

Page 231 of 714
Page 232 of 714
5.43 Operation: 04.06 Fare Option - Unifare

If no types of fares are specified, only public fares are searched.
This option may be combined with any other option.
The following Unifares options are supported:
Published fares: RP
Unifares: RU
Corporate Unifares: RW with a mandatory Corporate number xxxxxx
Amadeus Nego: RN
Amadeus Corporate: RC with a mandatory Corporate number xxxxxx
These fare type searches may be combined, with the exception of Unifares (RU) or Corporate Unifares (RW)
with an Amadeus Nego (RN) or Amadeus Nego Corporate (RC) in the same entry.
An associated corporate number must be specified for Corporate Unifares or Amadeus Nego Corporate
requests.
Note: The search is restricted to one corporate id (Corporate identity) Value.
The example below illustrates a low fare search including the optional Unifares element with the following
information.
Query Requirements:
Search to include Published Fares, non corporate Unifares and Coporate Fares (Coporate code 12345)
Requesting
Specified Data


RC

returned
200
ADT
Identify Published fares Price type search
RP
Identify Corporate Unifares type search
RU
Identify the corporate number as Corporate Unifares RW

Associated corporate number to Corporate Unifares
RW
012345
1
Page 233 of 714
PAR
MIA
201205

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 234 of 714
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>

Invalid Value - Corporate
If a valid corporate type is not specified (RW or RC) or if the corporate number specified is not matching the
corporate type requested (RW or RC), then the entire query is rejected with the following error message
"INVALID VALUE - CORPORATE"
Corporate Number Must be Specified
If a corporate type (RC or RW) has been specified, yet no associated corporate number is included in the
query, the entire query is rejected with the following error:
"CORPORATE NUMBER MUST BE SPECIFIED"
Conflicting Options Used
Unifares and Amadeus Nego/Corporate options are not combinable. If this check fails, the entire request
is rejected and the following message is returned:
"CONFLICTING OPTIONS USED"
Page 235 of 714
5.44 Operation: 04.07 Fare Option - Expanded Parameter

The fare type - expanded parameter option may be combined with any other option. With the exception that
the No Restriction parameter (NR) may not be combined with any other expanded parameter.
The following fare type - Expanded Parameters are supported:
Advance purchase (NAP): Search for low fares having no advance purchase.
Penalty information for cancellation (NPE): Search for low fares having no penalty.
No Restriction (NR): Search for low fares having no restrictions.
Refundable fares (RF): Search for low fares that may be refundable.
A maximum of 3 expanded parameters may be requested.

The example below illustrates a low fare search including an optional Expanded Parameter element specified
Query Requirements:
Only refundable fares should be returned in the recommendations.

Requesting
Specified Data


RC
200
ADT
Expanded Parameter type for Refundable fares
RF
Trip departure city Marseille
MRS
Trip arrival city Miami
MIA
200106

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
Page 236 of 714
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RF</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>200106</date>
</timeDetails>
</itinerary>

Invalid Value - Pricing / Tick Info
The only valid expanded parameter options applicable are NAP, NPE, NR and RF. If an unknown
Expanded Parameter is specified in the entry, the entire request is rejected and the following error message
is returned:
Page 237 of 714
"INVALID VALUE - PRICING/TICK INFO".

Conflicting Options Used
It is not possible to combine the No Restriction (NR) Expanded Parameter with any other Expanded
Parameter. If this check fails, the entire request is rejected and the following error message is returned:
"CONFLICTING OPTIONS USED".
Page 238 of 714
5.45 Operation: 04.08 Fare Option - My Search - Fare Families

A Parameterized Fare Family is a set of specific parameters defined at input time in the search query. Up to
6 Parameterized Fare Families can be defined in input. These parameterized fare families are set as options,
relying on a set of criteria and attributes used to match recommendations to Fare Families.
The parameterized Fare Family can be combined with any other option. It is the responsibility of the user to
ensure that combination of Fare Families parameters and other query options does not affect the functional
coherence of the request.
Structure of parameterised Fare Family:
The search option offers the possibility to the user to include up to 6 Fare families in the query.
Each fare family is defined by up to 10 sets of attributes linked logically by OR.
Within each set, attributes are logically linked by AND.
Within each attribute, values are logically linked by OR.
Each set is composed of the following attributes:
Attributes
Format
Mandatory(M)/
Optional(O)
Occurrences
Fare Family Short name

(Mandatory)
1-10 Alphanumeric
Ranking
1-4 digits
0-10
0-5
Combinability
Publishing Carrier
Type of Fare
Default:
combinable or
NOC (Not
combinable)
2 Alphanumeric
RP: published
fares
RV: private fares
RN: 1A
negotiated fares
RA: Category 35
fares
RD: DDF fares
RU: Unifares
Prime Booking Code
2 alpha
0-10
Fare Basis
1-9 characters (0 to 9, A
to Z, -)
0-10
Corporate Information
CORP / NONCORP or
CORPORATE CODE
0-6
0-6
CORPORATE NAME
(Sum of CORP CODE +

CORPNAME <= 6)
Page 239 of 714
Cabin
M (Economy
Standard)
W (Economy
Premium)
Y (Economy)
C (Business)
F (First)
0-5
Expanded Parameter Advance Purchase
AP (With
Advance Purchase)
NAP (No
Advance Purchase)
0-2
Expanded Parameter Refundability
RF (Refundable)
NRE (nonRefundable)
0-2
Expanded Parameter Penalty
PE (with Penalty) O
NPE (without
Penalty)
0-2
Expanded Parameter Restriction
R (with
O
0-2
Restriction)
NR (No
Restriction)
When publishing carrier criteria is used, the include airline option should also be requested in the query to
target the expected flights.
There is, therefore, up to 10 sets of criteria for each Parameterized Fare Family and this set of criteria may
not be coded negatively.
The example below illustrates a Lowest Fare request including 6 parameterized fare families defined by many
attributes sets, each attribute has many occurrences:
Itinerary: Round Trip : NCE-AMS
Date: 01OCT09 - 08OCT09
1 ADT
6 Fare Families
1st Parameterized fare family:
name: FFAMILY1
ranking 10
not combinable (NCO)
Attributes Set 1:
publishing carrier AF
fare basis NAP30
Public fare or Atp Nego fare
2nd Parameterized fare family:
name: FFAMILY2
ranking 50
Attributes Set 1:
Page 240 of 714
publishing carriers AF or KL
fare basis NCD or NRT or NRF or LCO or LCD
3rd Parameterized fare family:
FFAMILY3
ranking 80
Attributes Set 1:
Corporate Fares
Cabin Y
Attributes Set 2:
Non-Corporate Fares
Cabin Y or C
Expanded Parameter NAP (Fares with no advance purchase)
Expanded Parameter NPE (Fares with no penalty)
Attributes Set 3:
publishing carrier KL
Cabin M, W, C
4th Parameterized fare family:
FFAMILY4
ranking 60
Attributes Set 1:
fare basis NCD
Attributes Set 2:
publishing carriers AF,KL
fare basis NRT
Attributes Set 3:
publishing carrier KL
any fare basis including JUNIOR
name: FFAMILY5
ranking 100
Attributes Set 1:
Booking code L, M, N, O, P, Q, R, S, T or U
OTHERS
Ranking 0
The following table describes the Parameterized Fare Family XML fields:
Lowest Fare Search - Data element
fareFamilies/ familyInformation
Description
Fare Family information
Page 241 of 714
fareFamilies/ familyInformation /fareFamilyname
Fare Family Short Name
fareFamilies/ familyInformation /hierarchy
Fare Family Ranking
fareFamilies/familyCriteria/fareFamilyInfo/
fareFamilyQual
Fare Family Combinability (currently "NCO" if not

combinable or no field if combinable)
fareFamilies/familyCriteria
1st Matching attributes Set information
fareFamilies/familyCriteria/carrierId
Fare Publishing carrier
fareFamilies/familyCriteria/rdb
Type of Fare
fareFamilies/familyCriteria/fareProductDetail/
fareBasis
Fare Basis
fareType
Prime Booking Code
fareFamilies/familyCriteria/corporateInfo/
corporateNumberIdentifier
CORP or NONCORP
cabinProduct/cabinDesignator
cabin
cabinProduct/otherCriteria/name
EXP
cabinProduct/otherCriteria/type
Expanded Parameter value
fareFamilies/otherPossibleCriteria/logicalLink /
booleanExpression/codeOperator
Addition of an attribute set within the same fare

family set using the OR logic operator
fareFamilies/otherPossibleCriteria/logicalLink /
booleanExpression/codeOperator/familyCriteria
2nd Matching attributes Set information
etc
etc

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
Page 242 of 714
</traveller>
</paxReference>
<fareFamilies>
<familyInformation>
<fareFamilyname>FFAMILY1</fareFamilyname>
<hierarchy>10</hierarchy>
</familyInformation>
<familyCriteria>
<fareFamilyInfo>
<fareFamilyQual>NCO</fareFamilyQual>
</fareFamilyInfo>
<fareProductDetail>
<fareBasis>NAP30</fareBasis>
<fareProductDetail>
<fareProductDetail>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<carrierId>KL</carrierId>
<fareProductDetail>
<fareBasis>NCD</fareBasis>
<fareProductDetail>
<fareBasis>NRT</fareBasis>
<fareProductDetail>
<fareBasis>NRF</fareBasis>
<fareProductDetail>
<fareBasis>LCO</fareBasis>
<fareProductDetail>
<fareBasis>LCD</fareBasis>
</familyCriteria>
Page 243 of 714
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<corporateInfo>
<corporateNumberIdentifier>CORP</corporateNumberIdentifier>
</corporateInfo>
<cabinProduct>
<cabinDesignator>Y</cabinDesignator>
</cabinProduct>
</familyCriteria>
<otherPossibleCriteria>
<logicalLink>
<booleanExpression>
<codeOperator>OR</codeOperator>
</booleanExpression>
</logicalLink>
<familyCriteria>
<corporateInfo>
<corporateNumberIdentifier>NONCORP</corporateNumberIdentifier>
</corporateInfo>
<cabinProduct>
</cabinProduct>
<cabinProduct>
<cabinDesignator>C</cabinDesignator>
</cabinProduct>
<otherCriteria>
<name>EXP</name>
<value>NAP</value>
</otherCriteria>
<otherCriteria>
<name>EXP</name>
<value>NPE</value>
</otherCriteria>
</familyCriteria>
</otherPossibleCriteria>
<logicalLink>
<booleanExpression>
Page 244 of 714
</logicalLink>
<familyCriteria>
<cabinProduct>
<cabinDesignator>M</cabinDesignator>
</cabinProduct>
<cabinProduct>
<cabinDesignator>W</cabinDesignator>
</cabinProduct>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<fareProductDetail>
<fareBasis>NCD</fareBasis>
</familyCriteria>
<logicalLink>
<booleanExpression>
</logicalLink>
<familyCriteria>
<fareProductDetail>
<fareBasis>NRT</fareBasis>
</familyCriteria>
<logicalLink>
<booleanExpression>
</logicalLink>
<familyCriteria>
Page 245 of 714
<fareProductDetail>
<fareBasis>-JUNIOR</fareBasis>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<rdb>L</rdb>
<rdb>M</rdb>
<rdb>N</rdb>
<rdb>O</rdb>
<rdb>P</rdb>
<rdb>Q</rdb>
<rdb>R</rdb>
<rdb>S</rdb>
<rdb>T</rdb>
<rdb>U</rdb>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<fareFamilyname>OTHERS</fareFamilyname>
</fareFamilies>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
</fareOptions>
<itinerary>
Page 246 of 714
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>AMS</locationId>
<timeDetails>
<date>011009</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<locationId>AMS</locationId>
</departurePoint>
<timeDetails>
<date>081009</date>
</timeDetails>
</itinerary>

In addition to the standard possible errors checks, the following ones are performed:
Page 247 of 714
PFF - TOO MANY FARE FAMILIES

If more than 6 Parameterised Fare Families are specified, the entry is rejected with the following message:
"PFF - Too many fare families"
PFF - TOO MANY MATCHING ATTRIBUTES SETS REQUESTED
If for a parameterised fare family, more than 10 matching attributes sets are specified, the entry is rejected
with the following message:
"PFF - Too many matching attributes sets requested"
PFF - TOO MANY ATTRIBUTE OCCURRENCES
If for any attribute within any set defined in the query, more occurrences than the ones defined in the table
below are requested, the entry is rejected with the following message:
"PFF - Too many attribute occurrences requested"
PFF - INVALID FARE FAMILY NAME REQUESTED
If at least one of the specified Fare Families names is invalid, the whole entry is rejected with the message:
"PFF - Invalid Fare Family name requested"
PFF - INVALID CARRIER REQUESTED
If at least one of the specified publishing carriers is invalid, the whole entry is rejected with the message:
"PFF - Invalid carrier requested"
PFF - INVALID TYPE OF FARE REQUESTED
If the specified type of fare is invalid, the whole entry is rejected with the message:
"PFF - Invalid Type of Fare Requested"
PFF - INVALID FARE FAMILY COMBINABILITY REQUESTED
If the Fare Family Combinability is different than "Not Combinable", the whole entry is rejected with the
message:
"PFF - Invalid Fare Family Combinability Requested"
PFF - INVALID CARRIER REQUESTED
If the specified publishing carrier is invalid, the whole entry is rejected with the message:
"PFF - Invalid Carrier Requested"
PFF - INVALID GENERIC FARE BASIS REQUESTED
If the requested Fare Basis contains more than one dash (-), the whole entry is rejected with the message:
"PFF - Invalid Generic Fare Basis requested"
PFF - INVALID PRIME BOOKING CODE REQUESTED
If the requested Prime Booking code is invalid, the whole entry is rejected with the message:
"PFF - Invalid Generic Fare Basis requested"
See also the "Error Messages" section.
Page 248 of 714
5.46 Operation: 04.09 Fare Option - Multi Office IDs - Default Distribution
The user has the ability to specify up to 19 Office ids in addition to the Originator Office id of the Originator Details
segment, within the same country and with the same modifier type. The system will then find the cheapest
travel solutions among all office ids requested in input (originator office id and additional office ids) without
any preference.
For each additional office id, if one or several of these attributes exist:
IATA number
ARC number
ERSP number
Originator type code
True city code
Country code
LN IATA number
Then, the process for the additional office id is the same as for a mono office id query, when these attributes
are specified in the Originator Details segment for the originator office id.
If one of these attributes is missing for the office id requested, we don't use for this office id the attributes of the
Originator office id from the Originator Details segment. For this requested office id, the process is the same
as for a mono office id query, in case of this same attribute would have been missing in the Originator Details.
Limitations
- Multi Office Id Search can be done on a maximun number of 3 requested segments.
- A recommendation is sold for a given office id only at itinerary level. It is not possible to have one office id for
outbound and another one for the inbound in a Round Trip recommendation.
- In case one of the following options is requested in addition to the Multi office id option: the Multi TPax option,
the Split PNR option or the Multi Passenger Same Booking code options, then for each solution, the same
Office id is used for all passengers
- In case the Multi Ticket option is requested in addition to the Multi office id option, then the search is done
to find the cheapest solution that requires one single pricing transaction or individual pricing transactions per
Proposed Segment to be booked, on one office id.
- Multi office id option cannot be combined with Parameterized Fare Family option (My Search) and Airline
Ticketing Fees (OB fees).
- All office ids in the query (originator and additional) must fulfil all the following conditions:
1. All agent set locations must be in the same country,
2. All Country Code must be the same,
3. Any True City Code (if exist) must be in the associated Country Code,
4. For each office id, if the country code is different than the country of the agent set location, then the True
City Code is mandatory.
Page 249 of 714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>PHL</locationId>
<timeDetails>
<date>171109</date>
</timeDetails>
</itinerary>
Page 250 of 714
<officeIdDetails>
<officeIdInformation>
<officeIdentification>
<agentSignin>MIA1A2100</agentSignin>
</officeIdentification>
</officeIdInformation>
</officeIdDetails>
<officeIdDetails>
<agentSignin>NYC1A2100</agentSignin>
</officeIdDetails>
<officeIdDetails>
<agentSignin>DCA1A2200</agentSignin>
</officeIdDetails>
<officeIdDetails>
</officeIdDetails>
<officeIdDetails>
<agentSignin>SAN1A2300</agentSignin>
</officeIdDetails>
<officeIdDetails>
</officeIdDetails>

<replyStatus>
Page 251 of 714
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<officeIdDetails>
<agentSignin>MIA1A2100</agentSignin>
<officeIdReference>
<referenceType>O</referenceType>
</officeIdReference>
</officeIdDetails>
<officeIdDetails>
<officeIdReference>
</officeIdDetails>
<officeIdDetails>
<officeIdReference>
</officeIdDetails>
<officeIdDetails>
Page 252 of 714
<officeIdReference>
</officeIdDetails>
<officeIdDetails>
<agentSignin>SAN1A2300</agentSignin>
<officeIdReference>
</officeIdDetails>
<officeIdDetails>
<officeIdReference>
</officeIdDetails>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0628</ref>
</flightProposal>
<flightProposal>
<ref>US</ref>
</flightProposal>
<flightDetails>
Page 253 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>LAS</locationId>
</location>
<companyId>
<marketingCarrier>US</marketingCarrier>
<operatingCarrier>US</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>LAS</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>US</marketingCarrier>
Page 254 of 714
<operatingCarrier>US</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<refQualifier>O</refQualifier>
<referencingDetail>
<referencingDetail>
<referencingDetail>
<referencingDetail>
Page 255 of 714
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>US</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>G</rbd>
<cabin>M</cabin>
Page 256 of 714
</cabinProduct>
<fareProductDetail>
<fareBasis>GXA7NL2Y</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>G</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>GJATNL6Y</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>

- If one office id is requested several times, then the entire entry is rejected with the following message:
"OFFICE IDs MUST BE REQUESTED ONLY ONCE"
- If all agent set locations must be in the same country, then the entire entry is rejected with the following
message:
"OFFICE IDs MUST BE IN THE SAME COUNTRY"
- If all office IDs have not the same modifier type, either Travel Agent (modifier 2 or 3) or Airlines (0 or 1), then
the entire entry is rejected with the following message:
Page 257 of 714
"OFFICE IDs MUST HAVE SAME MODIFIER TYPE"

- If the modifier type value of one additional office id is not 0, 1, 2 or 3, then the entire entry is rejected with
the following message:
INVALID OFFICE ID:
where l is indexes of office ids with an invalid format in the list of office ids requested in input.
- If the number of office ids requested is greater than the maximum authorised, then the entire entry is rejected
TOO MANY OFFICE IDs REQUESTED
- If one added office id format is not valid, then the entire entry is rejected with the following message:
"INVALID OFFICE ID: l"
where l is indexes of office ids with an invalid format in the list of office ids requested in input.
- If the originator office id is not authorised to request one or several additional office ids specified in the query,
the entire entry is rejected with the following message:
"OID(S) NOT AUTHORISED: n"
where n is indexes of office ids not authorised in the list of office ids requested in input.
- If for one additional office id, the originator type code is requested in input, then the entire entry is rejected
"ORIGINATOR TYPE CODE NOT AUTHORIZED IN INPUT FOR ADDITIONAL OFFICE IDS"
- If for one additional office id, no identification information is defined, then the entire entry is rejected with the
following message:
"OID(S) NOT IDENTIFIED: m"
where m is indexes of the requested office ids for which identification information is missing.
- If Multi Office Ids is requested with Parameterized Fare Family option (My Search), then the entire request
is rejected with the following message:
Page 258 of 714

- If Multi Office Ids is requested with a complex itinerary (more than 3 requested segments), then the entire
request is rejected with the following message:
"OPTION NOT PERMITTED WITH COMPLEX ITINERARIES"
Page 259 of 714
5.47 Operation: 04.10 Fare Option - Multi Office IDs - Even Distribution
The user has the ability to request an even distribution of the recommendations among the office ids.
The recommendations are evenly distributed among the requested office ids (including the originator office id).
For each recommendation, the list of office ids for which the recommendation is applicable is returned.
The same number of recommendations is allocated to each office id on which the search is performed
(originator or additional office ids). So the targeted number of recommendations to build for each office id is:
Targeted Recommendations = (Nb requested Recommendations/(Nb additional office Ids + 1))
Note: If the requested number of recommendations is not reached because of rounding, the remaining
recommendations are evenly spread over the other offices ids, in the order of the request (the originator office
id being the first).
The transaction returns the cheapest recommendations for each office id. If the same recommendation can be
sold by several office ids, it is counted as one recommendation for each office id. As in standard mode, only
the cheapest recommendation is returned for one journey.
As soon as the targeted number of recommendations for one office id is reached, this office id is no more
considered for the search of the cheapest recommendations. But if a recommendation is found for another
office id and is also applicable for this office, then the recommendation is marked as applicable for both offices.
As a consequence, more recommendations than the number requested can be returned in output.
Limitations
- No recommendation based on a public fare (or a combination of public fares only) is returned for the additional
offices ids.
- As the recommendations are distributed among the offices ids, the Majority Carrier and Time of departure
diversity are not applied.
- Cannot be combined with Weighted Distribution, Airline Distribution and Airline Distribution Container options.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
Page 260 of 714
<priceType>EVD</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>200909</date>
</timeDetails>
</itinerary>
<officeIdDetails>
</officeIdDetails>
<officeIdDetails>
</officeIdDetails>
<officeIdDetails>
<agentSignin>ORD1A0200</agentSignin>
</officeIdDetails>
Page 261 of 714
<officeIdDetails>
</officeIdDetails>
<officeIdDetails>
<agentSignin>LAX1A0300</agentSignin>
</officeIdDetails>

- If this option is requested in another product than Master Pricer Travel Board, the entire entry is rejected with
INVALID OPTION
- If this option is requested with any option it can't be combined with, then the entire request is rejected with
Page 262 of 714
5.48 Operation: 04.11 Fare Option - Multi Office IDs - Weighted Distribution
The user has the ability to request for each office id, a fraction of the total number of recommendations by
specifying a weight.
The recommendations are distributed among the requested office ids (including the originator office id)
according to the weight required.
If a weight is requested for an office id, the targeted number of recommendations for this office id is:
Targeted Recommendations = requested nb recommendations*(weigth/SUM(weigth))
If no weight is requested for an office id, no recommendations are returned for this office id.
Note: The number of recommendations calculated should be rounded down. The missing number of requested
recommendations is then evenly distributed to the other office ids in the order of the request (the originator
office id being the first).
The transaction returns the cheapest recommendations for each office id. If the same recommendation can be
sold by several office ids, it is counted as one recommendation for each office id. As in standard mode, only
the cheapest recommendation is returned for one journey.
As soon as the targeted number of recommendations for one office id is reached, this office id is no more
considered for the search of the cheapest recommendations. But if a recommendation is found for another
office id and is also applicable for this office, then the recommendation is marked as applicable for both offices.
As a consequence, more recommendations than the number requested can be returned in output.
Limitations
- As for the even distribution option, recommendations based on a combination of public fares only are not
returned for the additional office ids.
- This option cannot be combined with Even Distribution, Airline Distribution and Airline Distribution Container
options.
- The Majority Carrier and Time of Departure diversity is not applied when a weight is requested for at least
one office id.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>WT</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
Page 263 of 714
</fareOptions>
<travelFlightInfo>
<cabinId>
<cabinQualifier>RC</cabinQualifier>
<cabin>Y</cabin>
</cabinId>
<companyIdentity>
<carrierId>TZ</carrierId>
<carrierId>AQ</carrierId>
<carrierId>AS</carrierId>
<carrierId>WN</carrierId>
<carrierId>WG</carrierId>
<carrierId>G3</carrierId>
<carrierId>VH</carrierId>
<carrierId>NE</carrierId>
<carrierId>KD</carrierId>
<carrierId>IN</carrierId>
<carrierId>VX</carrierId>
<carrierId>9K</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>YYC</locationId>
</departurePoint>
<locationId>CAI</locationId>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
Page 264 of 714
<departurePoint>
<locationId>CAI</locationId>
</departurePoint>
<locationId>YYC</locationId>
<timeDetails>
<date>201205</date>
</timeDetails>
</itinerary>
<officeIdDetails>
<agentSignin>LAX1A0100</agentSignin>
<nbOfUnits>
<unitNumberDetail>
</unitNumberDetail>
</nbOfUnits>
</officeIdDetails>
<officeIdDetails>
<agentSignin>DTW1A0200</agentSignin>
</officeIdDetails>
<officeIdDetails>
</officeIdDetails>
<officeIdDetails>
Page 265 of 714
<agentSignin>DFW1A0400</agentSignin>
<nbOfUnits>
<unitNumberDetail>
</unitNumberDetail>
</nbOfUnits>
</officeIdDetails>

- If this option is requested with any option it can't be combined with, then the entire request is rejected with
- If a weight is requested without the ODW keyword, the entire entry is rejected with the following message:
"INVALID OPTION"
- If all weights are either undefined or equal to zero, then the entire request is rejected with the following
message:
WEIGHTS SHOULD BE REQUESTED
Page 266 of 714
5.49 Operation: 04.12 Fare Option - Identify YQ/YR tax amounts in Output
The purpose of this option is to separately return the total amount of YQ/YR taxes per recommendation and per
passenger typein output. This includes the fuel surcharge and whatever other surcharge/tax there might be.
There is no way to specifically identify the fuel surcharge among the YQ/YR surcharges.
As YQ/YR are mainly filed for Fuel surcharge application purposes and as they must be displayed separately
from the other taxes for legal reasons in some countries (for example, US), this option allows to get those
amounts in output. This option does not have any effect on other returned amounts.
This option is triggered by a setting at office ID level.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
Page 267 of 714
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120202</date>
</timeDetails>
</itinerary>
Page 268 of 714
5.50 Operation: 04.13 Fare Option - Price only PTC

The process returns strictly recommendations with the requested passenger type, no defaulting is done.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>PTC</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 269 of 714
<timeDetails>
<date>120202</date>
</timeDetails>
</itinerary>
Page 270 of 714
5.51 Operation: 04.14 Fare Option - My Search - Distribution ratio of

recommendations per Fare Family
The user may specify the distribution ratio to be used to compute the targeted number of recommendations for
each fare family processed in the request. This option is to be used in the case the default even distribution
of recommendations over fare families is not expected.
It means that 50% of recommendations could be returned for fare family 1, 30% for fare family 2 and 20%
for fare family 3.
The association of distribution ratio to each fare family considered by the distribution process[1] is made by
considering the list of distribution ratio in input order and the list of fare families from the most restrictive to
the less restrictive (meaning, in ranking decreasing order). First distribution ratio being associated to the most
restrictive fare family, second ratio to second fare family and so on.
In case there is less Distribution Ratio than Fare Family, 0 Ratio is associated remaining Fare Families with
no corresponding Ratio, meaning that no recommendation will be returned for those Fare Families. Fares from
such Fare Family may still be combined with fares from other Fare Families to provide recommendations in
other Fare Families.
In case there is more Distribution Ratio than Fare Family, Ratio not linked to any Fare Family will not be
considered.
As a reminder only up to 6 Fare Families can be considered in one request, the selection is made on Fare
Families linked to at least one valid fare, and in case more than 6 Fare Families exist, only the 6 most restrictive
ones are kept.
The example below illustrates a query including a Distribution Ratio element specified with the following
information:
Query Requirements:
Total trip itinerary from London to New York City.
Two requested fare families:FF1 and FF2
The distribution of recommendations has to be based on the following ratios: 120,100

RequestingDetails
Specified Data
Fare Family
FF1,FF2
Distribution Ratios: 120, 100, 0, 1, 50
120:100:00:01:50
1st Segment departure city
LON
1st Segment arrival city
NYC
Date
14 August 2010

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
Page 271 of 714
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareFamilies>
<familyInformation>
<fareFamilyname>FF1</fareFamilyname>
<familyCriteria>
<carrierId>QF</carrierId>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
Page 272 of 714
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
<carrierQualifier>R</carrierQualifier>
<carrierId>120</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
</depMultiCity>
<arrivalMultiCity>
</arrivalMultiCity>
<timeDetails>
<date>140810</date>
</timeDetails>
</itinerary>
Page 273 of 714

Invalid Ratio Format
The Distribution Ratios are a 2-digit or a 3-digit numeric. If the ratio is not a 2- or 3-digit ratio, the entire entry
will be rejected. Verify the ratios sent in the request are in the correct format. More importantly, 1-digit ratios are
not accepted by the system, therefore, ensure that no 1-digit ratios are included in the requests. An alternative
to this issue is to add a 0 on the left side of each 1-digit ratio when they are requested.
Example:
Ratios Format
Accepted/Rejected
DR: 150,0,20,60,5
Rejected because 0 and 5 are 1-digit numeric.
DR: 150,00,20,60,05
Accepted because all ratios are 2- or 3-digits

numeric.
Invalid - 6 Distribution Ratio Maximum

If more than 6 Distribution Ratios are listed in the DR option, the entire entry is rejected with the following
message:
"TOO MANY DISTRIBUTION RATIOS REQUESTED"
Page 274 of 714
5.52 Operation: 04.15 Fare Option - My Search - Resulting Fare Families at

requested segment level
With this option, the Fare Family notion is applied at requested segment level. System returns
recommendations distributed over combinations of Fare Families per requested segment.
For each recommendation, a resulting Fare Family is determined for each requested segment and for any
combination of Fare Family for outbound and Fare Family for inbound available recommendations are returned.
A same number of recommendations for each combination of Fare Family is returned if available.
The same number of recommendations for all combinations of inbound and outbound Fare Families is targeted.
In case a combination is not fully filled-in, more recommendations than targeted can be returned for the
other Fare Families combinations. Targeted number of recommendations per combination of Fare Families
is determined by the formula: Number of Recommendations requested divided by the number of possible
combinations of Fare Families. If a Fare Family is defined as non-combinable, there is only one possible type
of solution involving it: when this Fare Family is used both on outbound and on inbound.
For example, if 3 Fare Families FF1, FF2 and FF3 are defined, the following combination must be considered:
FF1 (requested segment 1) + FF1 (requested segment 2)

For each of those 9 fare family combinations, the process must try to return 200/9 = about 22-23
recommendations.
The example below shows a query with 2 Fare Families FF1 and FF2 and 2 requested segments.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
Page 275 of 714
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>FFS</priceType>
</pricingTicketing>
</pricingTickInfo>
Page 276 of 714
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>MEL</locationId>
</departurePoint>
<locationId>SYD</locationId>
<timeDetails>
<date>010210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>070210</date>
</timeDetails>
</itinerary>

- If the Parameterized Fare Family option is not requested, the whole entry is rejected with the message:
Page 277 of 714
PARAMETERIZED FARE FAMILY OPTION MISSING

- If the number of requested segments is superior or equal to three, the whole entry is rejected with the message:
TOO MANY REQUESTED SEGMENTS
Page 278 of 714

recommendations per Fare Family at requested segment Level
This option is the same as the Distribution Ratio of recommendations per Fare Family one except that the ratios
apply to the Fare Family combinations per Requested Segment.
In the query, the user provides a list of distribution ratio (2- or 3-digit numeric value).
The association of Distribution Ratio to each Fare Family combination considered by the distribution process
is made by a list of items. Each item is composed of a Fare Family combination and its associated ratio. There
are as many items as Fare Family combinations wanted to appear in the output recommendations. The order
in which the Distribution Ratios are associated to Fare Family combinations has no importance.
Fare Family combinations that are not linked to a ratio will not appear in the output recommendations.
The value 0 is accepted for a ratio. It is the same as not defining the ratio at all.
If a Distribution Ratio associated to the same Fare Family combination is defined several times, only the last
occurrence is considered.
Inside a Distribution Ratio item, Fare Families and Requested Segments are referred by their reference number.
For each Fare Family combination, the targeted number of recommendations is lower or equal to: ri,j * N where:
ri,j = Ri,j / (sum of Ri,j linked to Fare Family combinations considered in distribution process) where Ri,j
represents the Distribution Ratio associated to Fare Family i combined with Fare Family j and N is the requested
number of recommendations.
This option is not combinable with the distribution ratio of recommendations per Fare Family one.
In the example below,
Ratio of weight 10 associated with the combination First Fare Family (requested segment 1) + First Fare Family
(requested segment 2)
Ratio of weight 20 associated with the combination First Fare Family (requested segment 1) + Second Fare
Family (requested segment 2)

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
Page 279 of 714
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>FFS</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
Page 280 of 714
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>010210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>070210</date>
</timeDetails>
</itinerary>
<combinationFareFamilies>
<itemFFCNumber>
<itemNumberId>
<number>1</number>
<type>FAC</type>
</itemNumberId>
</itemFFCNumber>
<nbOfUnits>
<unitNumberDetail>
Page 281 of 714
</unitNumberDetail>
</nbOfUnits>
<referenceInfo>
<referencingDetail>
<refQualifier>RS</refQualifier>
<referencingDetail>
<refQualifier>FF</refQualifier>
</referenceInfo>
<referenceInfo>
<referencingDetail>
<referencingDetail>
</referenceInfo>
</combinationFareFamilies>
<itemFFCNumber>
<itemNumberId>
<number>2</number>
<type>FAC</type>
</itemNumberId>
</itemFFCNumber>
<nbOfUnits>
<unitNumberDetail>
</unitNumberDetail>
</nbOfUnits>
<referenceInfo>
<referencingDetail>
<referencingDetail>
Page 282 of 714
</referenceInfo>
<referenceInfo>
<referencingDetail>
<referencingDetail>
</referenceInfo>

If the Parameterized Fare Family option is not requested, the whole entry is rejected with the message:
"PARAMETERIZED FARE FAMILY OPTION MISSING"
If at least one of the ratios requested in the input is not a 2- or 3-digit numeric value, the entire entry is rejected
and the following error message is returned:
"INVALID RATIO FORMAT"
If at least one ratio is associated to a non-existing Fare Family at Itinerary or Segment level, the entire entry
is rejected with the message:
"REFERENCE TO NON-EXISTING FARE FAMILY"
If in at least one reference to a Fare Family is missing, the entire entry is rejected with the message:
"REFERENCE TO FARE FAMILY MISSING"
Checks when the option is used at Requested Segment level:
If in at least one reference to a Requested Segment is missing, the entire entry is rejected with the message:
"REFERENCE TO REQUESTED SEGMENT MISSING"
If inside at least one combination, the references to the Requested Segments do not start to 1 or are not
incremented at each segment, the entire entry is rejected with the message:
"REQUESTED SEGMENT DEFINITIONS NOT IN ORDER IN DISTRIBUTION RATIO"
If inside at least one combination, the number of references to Requested Segments is not equal to the number
of Requested Segments, the entire entry is rejected with the message:
"INVALID NUMBER OF REF SEGMENTS"
Checks when the option is used at Itinerary level:
Page 283 of 714
If inside at least one Distribution Ratio item, there is not exactly one reference to a Fare Family, the entire entry
is rejected with the message:
"INVALID NUMBER OF REF SEGMENTS"
If in at least one Distribution Ratio item a reference to a Requested Segment is present, the entire entry is
rejected with the message:
"REFERENCE TO REQUESTED SEGMENT IMPOSSIBLE AT ITINERARY LEVEL"
Page 284 of 714

recommendations per Fare Family at requested segment level (Usage at
itinerary level)
It is possible to use the distribution ratio per Fare Family at requested segment level to define a distribution
ratio per Fare Family (meaning at itinerary level). To do so, the FFS flag is not set. In that case, only one Fare
Family per combination group is defined: the resulting Fare Family at itinerary level.
In the example below, a ratio of weight 20 associated with the first Fare Family and ratio of weight 10 associated
with the second Fare Family.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>INF</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareFamilies>
Page 285 of 714
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
<familyCriteria>
<cabinProduct>
</cabinProduct>
</familyCriteria>
</fareFamilies>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>010210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
Page 286 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>070210</date>
</timeDetails>
</itinerary>
<itemFFCNumber>
<itemNumberId>
<number>1</number>
<type>FAC</type>
</itemNumberId>
</itemFFCNumber>
<nbOfUnits>
<unitNumberDetail>
</unitNumberDetail>
</nbOfUnits>
<referenceInfo>
<referencingDetail>
<refQualifier> FF</refQualifier>
</referenceInfo>
<itemFFCNumber>
<itemNumberId>
<number>2</number>
<type>FAC</type>
</itemNumberId>
</itemFFCNumber>
<nbOfUnits>
<unitNumberDetail>
Page 287 of 714
</unitNumberDetail>
</nbOfUnits>
<referenceInfo>
<referencingDetail>
<refQualifier> FF</refQualifier>
</referenceInfo>
Page 288 of 714
5.55 Operation: 04.18 Fare Option - Currency for Fare Selection option
This option allows the user to request that only those fares that are filed in the currency specified in the input
should be returned. Fares filed in any other currency will not be returned in recommendations.
This option can be combined with any other option except Multi-Ticket.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<conversionRate>
<conversionType>CFS</conversionType>
<currency>SEK</currency>
</conversionRate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 289 of 714
<timeDetails>
<date>200106</date>
</timeDetails>
</itinerary>

If an unknown currency is specified, then the entire request is rejected and the following error message is
returned:
VERIFY CURRENCY OPTION
Page 290 of 714
5.56 Operation: 04.19 Fare Option - Currency for Fare Selection with
Currency Conversion option
The Currency of Fare Selection option can be combined with the Currency Conversion (currency of sale) option.
The example below illustrates a low fare search with EUR as currency of sale (CUC) and GBP as Currency
of Fare Selection (CFS).
The CUC option has to be set in pricingTickInfo and the currency code has to be set in first position of
conversionRate without any conversionType.
The currency code of Fare Selection has to be set in second position of conversionRate with CFS in
conversionType.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<conversionRate>
<conversionType>CFS</conversionType>
<currency>GPB</currency>
Page 291 of 714
</conversionRate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>200106</date>
</timeDetails>
</itinerary>

indicatorcurrencyqualifiererrormessagecurrencyqualifierindicatorerrormessagevalueconversionRate
Page 292 of 714
5.57 Operation: 04.20 Fare Option - Multi-Ticket
The Multi-Ticket option allows to return at the same time:
Recommendations that require one single pricing transaction to be booked.
Recommendations that require individual pricing transactions per proposed segment to be booked (the
search is done on the same office id for the whole itinerary).
This option is applicable only on Round Trip recommendations (2 requested segments AB, BA).
In order to target better prices, the user can choose two One-Way flights instead of a Round Trip flightthatis
more expensive.
All solutions are returned as following:
First all One-Way recommendations that group the independent outbound are returned from the
cheapest to the more expensive.
Then all One-Way recommendations that group the independent inbound are returned from the
cheapest to the more expensive.
And finally, all Round Trip recommendations that group RT recommendations issued with 1 ticket are
returned from the cheapest to the more expensive.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>MTK</priceType>
Page 293 of 714
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
</itinerary>

Page 294 of 714
<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
<currency>GBP</currency>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1255</ref>
</flightProposal>
<flightProposal>
<ref>KU</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>LHR</locationId>
</location>
<location>
<locationId>KWI</locationId>
</location>
<companyId>
<marketingCarrier>KU</marketingCarrier>
<operatingCarrier>KU</operatingCarrier>
</companyId>
Page 295 of 714
<productDetail>
</productDetail>
<addProductDetail>
<productDetailQualifier>AIP</productDetailQualifier>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>KWI</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>KU</marketingCarrier>
<operatingCarrier>KU</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>1215</ref>
Page 296 of 714
</flightProposal>
<flightProposal>
<ref>EY</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>AUH</locationId>
</location>
<companyId>
<marketingCarrier>EY</marketingCarrier>
<operatingCarrier>EY</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
Page 297 of 714
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1250</ref>
</flightProposal>
<flightProposal>
<ref>GF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 298 of 714
</productDateTime>
<location>
</location>
<location>
<locationId>BAH</locationId>
</location>
<companyId>
<marketingCarrier>GF</marketingCarrier>
<operatingCarrier>GF</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>BAH</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>GF</marketingCarrier>
<operatingCarrier>GF</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 299 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>1310</ref>
</flightProposal>
<flightProposal>
<ref>QR</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>DOH</locationId>
</location>
<companyId>
<marketingCarrier>QR</marketingCarrier>
<operatingCarrier>QR</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
Page 300 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>1320</ref>
</flightProposal>
<flightProposal>
<ref>QR</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 301 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<terminal>N</terminal>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
Page 302 of 714
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>4</ref>
</flightProposal>
<flightProposal>
<ref>1325</ref>
</flightProposal>
<flightProposal>
<ref>EY</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 303 of 714
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>5</ref>
</flightProposal>
<flightProposal>
<ref>1830</ref>
</flightProposal>
<flightProposal>
<ref>EY</ref>
</flightProposal>
Page 304 of 714
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
Page 305 of 714
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
<numberType>M</numberType>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>KU</company>
</codeShareDetails>
<codeShareDetails>
Page 306 of 714
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>20DEC10</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>M</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>MHOWGB1</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>M</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>MHOWGB1</fareBasis>
Page 307 of 714
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>GF</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
Page 308 of 714
<pricingMessage>
</pricingMessage>
<monetaryDetail>
</monetaryDetail>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LOWPK5</fareBasis>
</groupOfFares>
<groupOfFares>
Page 309 of 714
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LOWPK5</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
Page 310 of 714
<codeShareDetails>
<company>QR</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
<monetaryDetail>
</monetaryDetail>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<textSubjectQualifier>SUR</textSubjectQualifier>
<description>FARE VALID FOR E TICKET ONLY</description>
</pricingMessage>
Page 311 of 714
</fare>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HLOWPK</fareBasis>
<fareType>ET</fareType>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HLOWPK</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>4</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
Page 312 of 714
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>EY</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 313 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description> - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HHRTGB</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HHRTGB</fareBasis>
Page 314 of 714
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QHE6MGB</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QHE6MGB</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 315 of 714
5.58 Operation: 04.22 Fare Option - Ticketing date

In order to avoid quoting a fare to a passenger that they are then unable to ticket at a later date, the user has
the abilityto specify the intended ticketing date in the query.
This option ensures that the user will only receive recommendations that, if priced on the same day as the
query is received, are valid for ticketing on the future ticketing date specified in the input.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<ticketingDate>
<date>100311</date>
</ticketingDate>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 316 of 714
<timeDetails>
<date>100309</date>
</timeDetails>
</itinerary>

If a past date is specified, the entire request is rejected with the following message:
PAST DATE PRICING NOT PERMITTED
If the date specified is later than the date of departure on the first flight segment of the itinerary, the entire
request is rejected with the following message:
FUTURE DATE TICKETING NOT PERMITTED
Page 317 of 714
5.59 Operation: 04.23 Fare Option - Solution Family

The user has the ability to specify a list of Solution Family names in input.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<solutionFamily>
<valueQualifier>1</valueQualifier>
<rateCategory>CHP</rateCategory>
</solutionFamily>
<solutionFamily>
<rateCategory>DIR</rateCategory>
</solutionFamily>
<solutionFamily>
<rateCategory>LWD</rateCategory>
</solutionFamily>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
Page 318 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>010412</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>300412</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
Page 319 of 714
</conversionRate>
<solutionFamily>
<identityNumber>1</identityNumber>
<rateCategory>CHP</rateCategory>
</solutionFamily>
<solutionFamily>
<rateCategory>DIR</rateCategory>
</solutionFamily>
<solutionFamily>
<rateCategory>LWD</rateCategory>
</solutionFamily>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0125</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<majCabin>W</majCabin>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
Page 320 of 714
<locationId>ORY</locationId>
</location>
<companyId>
<operatingCarrier>AF</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0355</ref>
</flightProposal>
<flightProposal>
<ref>XK</ref>
</flightProposal>
<majCabin>Y</majCabin>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>BIA</locationId>
Page 321 of 714
</location>
<companyId>
<marketingCarrier>XK</marketingCarrier>
<operatingCarrier>XK</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>AT7</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>BIA</locationId>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
Page 322 of 714
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0120</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<majCabin>Y</majCabin>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 323 of 714
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0840</ref>
</flightProposal>
<flightProposal>
<ref>XK</ref>
</flightProposal>
<majCabin>W</majCabin>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>CLY</locationId>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
Page 324 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>CLY</locationId>
</location>
<location>
</location>
<companyId>
<operatingCarrier>XK</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amountType>YQ</amountType>
<amount>0</amount>
</monetaryDetail>
Page 325 of 714
<monetaryDetail>
<amountType>YR</amountType>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
<amountType>Q</amountType>
<amount>0</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
<refQualifier>SF</refQualifier>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
Page 326 of 714
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>LAST TKT DTE*25JUN12</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ED3SAPFR</fareBasis>
<fareType>RD</fareType>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
Page 327 of 714
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ED3SAPFR</fareBasis>
<fareType>RD</fareType>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 328 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
Page 329 of 714
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*26JUN12</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>N</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>NHLOISIR</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>N</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>N8POFR</fareBasis>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
Page 330 of 714
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>T</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>T8POFR</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HHLOISIR</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 331 of 714
5.60 Operation: 04.24 Fare Option - Disable Negotiated Space

The user has the ability to deactivate Negotiated Space availability at query level.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
<carrierId>BA</carrierId>
</companyIdentity>
<flightDetail>
<flightType>DN</flightType>
</flightDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>011012</date>
Page 332 of 714
</timeDetails>
</itinerary>
Page 333 of 714
5.61 Operation: 04.25 Fare Option - Open Return

The user has the ability to specify an input option, Open Return, to book a segment without indicating an
inbounddate.
The user can also specify an optional "period of validity". This "period of validity" can be provided with the
inbound date, which is set by default to 1 year (365 days) maximum, if not given in the input.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>OPD</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
Page 334 of 714
</departurePoint>
<locationId>BOD</locationId>
<timeDetails>
<date>111113</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>111213</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
Page 335 of 714
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0105</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 336 of 714
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>1335</ref>
</flightProposal>
<flightProposal>
<ref>A5</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>LRT</locationId>
</location>
<companyId>
<marketingCarrier>A5</marketingCarrier>
<operatingCarrier>DB</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>CR7</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
Page 337 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>LYS</locationId>
</location>
<companyId>
<operatingCarrier>YS</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>ER4</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<terminal>A</terminal>
</location>
<companyId>
Page 338 of 714
</companyId>
<productDetail>
<equipmentType>CRK</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
Page 339 of 714
<ref>A5</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<terminal>A</terminal>
</location>
<location>
</location>
<companyId>
</companyId>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
Page 340 of 714
</location>
<location>
</location>
<companyId>
</companyId>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
Page 341 of 714
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>06OCT13</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>RRD0FR9</fareBasis>
Page 342 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<pricingTicketing>
Page 343 of 714
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<passengerType>CH</passengerType>
Page 344 of 714
<ticketInfos>
<ticketDesignator>CH0</ticketDesignator>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
Page 345 of 714
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 346 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>RSRFR9</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ESRFR9</fareBasis>
Page 347 of 714
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
Page 348 of 714
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
Page 349 of 714
</paxFareDetail>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<textSubjectQualifier>APM</textSubjectQualifier>
<description>NOT FARED AT PASSENGER TYPE REQUESTED </description>
<description>5</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
Page 350 of 714
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
<ticketDesignator>CH</ticketDesignator>
</ticketInfos>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>E</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
Page 351 of 714
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
Page 352 of 714
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>

- "Open return" option conflicts with other option:
CONFLICTING OPTIONS USED
- "Open return" option is requested on One-Way Itinerary:
INVALID OPEN RETURN OPTION
- "Open return" option is requested on more than 2 requested segments:
OPTION NOT PERMITTED WITH COMPLEX ITINERARIES
- "Period of validity exceeds 365 days:
INVALID OPEN RETURN OPTION"
Page 353 of 714
5.62 Operation: 04.26 Fare Option - Alternate Price

This function allows to return for each recommendations belonging to the eligible fare family, the cheapest
available Alternate recommendation for the exact same journey and cabin.
This process is activated with the presence of two specifics Fare Families in input. These two fare families
must be flagged as ALT to distinguish them from the "standard" fare families used for MySearch. The highest
ranking defines the Eligible fare family and the lower ranking defines the Alternate fare family.
The query illustrates two fare families:
Fare Family Eligible
Alternate Fare Family
Fare Family name
FF1
FF2
Fare Family ranking
20
10
Fare Family Flag
ALT
ALT
Corporate codes
NET
PKG
Fare type
Published (RP)
Private (RV)
The reply illustrates 5 recommendations:

Recommendation 1
FF1 & FF1

LAX-SYD UA839 VKXPSEA
SYD-LAX UA840 VKWPSEA
Group of recommendation 1
Req Seg 1, Prop Seg 1
Total amount: 1900.00 $

Alternate price: 2000.00 $ (Group
of recommendation 2)
Recommendation 2
FF2 & FF2

LAX-SYD UA839 LLX41EM5
SYD-LAX UA841 LLW41EM5

Recommendation 3
Alternate of recommendation 1
FF2 & FF2

LAX-SYD UA839 LLX41EM5
SYD-LAX UA840 LLW41EM5
Page 354 of 714

Recommendation 4
LAX-SYD UA838 FFFFF

SYD-LAX UA840 FFFFF
Recommendation 5
LAX-SYD UA838 FFFFF

SYD-LAX UA841 FFFFF

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareFamilies>
<familyInformation>
<familyCriteria>
<fareFamilyInfo>
<fareFamilyQual>ALT</fareFamilyQual>
</fareFamilyInfo>
<corporateInfo>
<corporateName>NET</corporateName>
</corporateInfo>
<corporateInfo>
<corporateName>PKG</corporateName>
</corporateInfo>
</familyCriteria>
</fareFamilies>
<fareFamilies>
<familyInformation>
Page 355 of 714
<familyCriteria>
<fareFamilyInfo>
<fareFamilyQual>ALT</fareFamilyQual>
</fareFamilyInfo>
<fareProductDetail>
<fareType>RV</fareType>
<fareProductDetail>
</familyCriteria>
</fareFamilies>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>170215</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
Page 356 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>280215</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<familyInformation>
<familyInformation>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
Page 357 of 714
</flightProposal>
<flightProposal>
<ref>1500</ref>
</flightProposal>
<flightProposal>
<ref>UA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<marketingCarrier>UA</marketingCarrier>
<operatingCarrier>UA</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
<productDetailQualifier>IAV</productDetailQualifier>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
Page 358 of 714
<flightProposal>
<ref>1500</ref>
</flightProposal>
<flightProposal>
<ref>UA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
Page 359 of 714
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1350</ref>
</flightProposal>
<flightProposal>
<ref>UA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
Page 360 of 714
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>1350</ref>
</flightProposal>
<flightProposal>
<ref>UA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
Page 361 of 714
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
<refQualifier>P</refQualifier>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
Page 362 of 714
<codeShareDetails>
<company>UA</company>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>TICKETS ARE NON REFUNDABLE AFTER DEPARTURE</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 27JAN15 - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
Page 363 of 714
<description>CORPORATE NAME PKG</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VKXPSEA</fareBasis>
<fareType>RB</fareType>
<corporateId>085513</corporateId>
<ticketInfos>
<ticketDesignator>54DC</ticketDesignator>
</ticketInfos>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VKWPSEA</fareBasis>
<fareType>RB</fareType>
Page 364 of 714
<ticketInfos>
<ticketDesignator>54DC</ticketDesignator>
</ticketInfos>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
Page 365 of 714
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
Page 366 of 714
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 14JAN15 - SEE SALES RSTNS</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LLX41EM5</fareBasis>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
Page 367 of 714
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LLW41EM5</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 368 of 714
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 369 of 714

</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 14JAN15 - SEE SALES RSTNS</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>FFFFF</fareBasis>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>FFFFF</fareBasis>
Page 370 of 714
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 371 of 714
5.63 Operation: 04.27 Fare Option - Search by FBA

The search by FBA (SBF) allows to get in output only recommendations that have a free baggage allowance
in piece or weight concept.
Only recommendations with free baggage allowance (>0) are returned in the output for all the
recommendations.
Activation :
<feeIdDescription>
<feeId>
<feeType>SBF</feeType>
</feeId>
</feeIdDescription>
There is no change in the output structure.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>BAG</priceType>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>SBF</feeType>
Page 372 of 714
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>150614</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<locationId>IBZ</locationId>
<timeDetails>
<date>180614</date>
</timeDetails>
</itinerary>

Page 373 of 714
Page 374 of 714
5.64 Operation: 05.1 Cabin Option - Mandatory Cabin

This cabin class applies to the entire requested itinerary. It is only possible to default to other classes of service
in the case where it has been requested to do so and at least one flight of the proposed segment contains
the cabin class specified.
Cabin class may not be specified at individual segment levels. The following cabins may be specified:
First
Business
Economic
For a marketing carrier, the cabin corresponding to each booking code is determined by the booking code and
the first letter based on the Cabin definition stored in Amadeus system (for example, C and CN).
When a Cabin is specified, the lowest fares are proposed using the classes that are identified as matching the
requested Cabin. Non-Stops, Directs, Connecting and Change of Gauges for which the cabin is not defined
or not available are not selected.
The cabin option applies to the entire trip and must be specified at the itinerary level of the request. Requested
cabin options at the segment level will result in an error.
Whenever the user specifies it, and whenever the requested cabin does not exist on someflights - either not
defined or closed - the other cabins may be considered by the system. This process is only applied when in at
least one of the flights of a Proposed segment on the requested cabin exists. Whenever a Proposed segment
may not be booked in the requested cabin on any flight, this Proposed segment is eliminated, even if the user
allows defaulting to other cabins.
Examples:
Request
Process
If Cabin Class (F) for return itinerary:

PARIS/NEW YORK/CHICAGO
If Cabin Class (F) is not available on any flight

between Paris/NewYork/Chicago, the system
proposed segment will not be returned in the
recommendations.
If Cabin Class (F) is only available on the system
proposed segment only from Paris/NewYork, default
cabin classes will be processed for NewYork/
Chicago segments.
If Cabin Class (F) is only available on the system

proposed segment only from NewYork/Chicago,
default cabin classes will be processed for Paris/
NewYork.
The example below illustrates a low fare search including an optional Cabin element specified with the following
information.
Page 375 of 714
Query Requirements:
Requested cabin service: F

No cabin defaulting, requested cabin must be on entire trip recommendation
Requesting
Specified Data


RC
200
ADT
First cabin service requested at itinerary level
PAR
MIA
Itinerary Date (12 February 2006)
120206

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<cabinId>
<cabin>F</cabin>
</cabinId>
</travelFlightInfo>
Page 376 of 714
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120206</date>
</timeDetails>
</itinerary>

Invalid Cabin Code
If the cabin code does not exist, the following error message is returned:
"INVALID CABIN CODE"
Option Cannot be Applied at Requested Segment Level
If the cabin code is not requested at the itinerary level, the following error message is returned:
Page 377 of 714
5.65 Operation: 05.2 Cabin Option - Recommended Cabin

The example below illustrates a low fare search including an optional Cabin element specified with the following
information.
Query Requirements:
Cabin defaulting, when applicable, for flights that do not have the requested cabin service available.
Note, however, that at least one of flight on each requested segment must propose the requested cabin
in order to be eligible.
Requesting
Specified Data


RC
200
ADT
Requested Cabin can be defaulted
RC
PAR
MIA
Itinerary Date (12 February 2006)
120206

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
Page 378 of 714
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<cabinId>
<cabinQualifier>RC</cabinQualifier>
<cabin>F</cabin>
</cabinId>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120206</date>
</timeDetails>
</itinerary>

Invalid Cabin Code
"INVALID CABIN CODE"
Page 379 of 714
5.66 Operation: 05.3 Cabin Option - Major Cabin
The example below illustrates a low fare search including an optional Major Cabin element specified with the
following information.
Query Requirements:
With the Major Cabin option, the transaction replies with recommendations that are mostly flown in the
requested cabin for each requested segment.
Requesting
Specified Data


RC
200
ADT
Requested Cabin can be defaulted
MC
Trip Departure city of Sydney
SYD
Trip Arrival city of Nice
NCE
Trip Date (13 November 2008)
131108
Trip Departure city of Nice
NCE
Trip Arrival city of Sydney
SYD
Trip Date (18 November 2008)
181108

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
Page 380 of 714
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<cabinId>
<cabinQualifier>MC</cabinQualifier>
<cabin>F</cabin>
</cabinId>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>131108</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
Page 381 of 714
</departurePoint>
<timeDetails>
<date>181108</date>
</timeDetails>
</itinerary>

Invalid Cabin Code
"INVALID CABIN CODE".
"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".
Page 382 of 714
5.67 Operation: 06.1 Fee Option - Pricing Scheme Reference
The example below illustrates a low fare search including an optional Pricing Scheme reference number
specified with the following information.
Query Requirements:
Trip itinerary Paris - Miami - New York.
AF is mandatory within the trip and may be combined with any other airline (YY) at itinerary level (for
each requested segment).
Pricing scheme reference provided to calculate Service Fees.

Requesting
Specified Data

ADT
Passenger type code applicable to 2nd passenger
Child Passenger type code
CH
Passenger type code applicable to 3rd passenger
Pricing Scheme reference
12345
Departure city of Tel Aviv
TLV
Trip Arrival city of Vienna
VIE
020616
Departure city of Vienna
VIE
Arrival city of Tel Aviv
TLV
080616

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
Page 383 of 714
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<ticketingPriceScheme>
</ticketingPriceScheme>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>TLV</locationId>
</departurePoint>
<locationId>VIE</locationId>
<timeDetails>
<date>020616</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
Page 384 of 714
<timeDetails>
<date>080616</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<feeDetails>
<feeReference>
<feeRefNumber>1</feeRefNumber>
</feeReference>
<feeInformation>
<feeIdentification>A</feeIdentification>
<feeInformation>
<feeType>T</feeType>
<feeAmountType>F</feeAmountType>
<feeAmount>20.88</feeAmount>
<feeCurrency>USD</feeCurrency>
</feeInformation>
</feeInformation>
<feeParameters>
<feeParameter>
<feeParameterType>VCR</feeParameterType>
<feeParameterDescription>6X</feeParameterDescription>
</feeParameter>
<feeParameter>
<feeParameterType>TKT</feeParameterType>
<feeParameterDescription>ET</feeParameterDescription>
</feeParameter>
Page 385 of 714
</feeParameters>
</feeDetails>
<feeDetails>
<feeReference>
<feeRefNumber>2</feeRefNumber>
</feeReference>
<feeInformation>
<feeIdentification>A</feeIdentification>
<feeInformation>
<feeType>T</feeType>
<feeAmountType>F</feeAmountType>
<feeAmount>19.34</feeAmount>
<feeCurrency>USD</feeCurrency>
</feeInformation>
</feeInformation>
<feeParameters>
<feeParameter>
<feeParameterType>VCR</feeParameterType>
<feeParameterDescription>6X</feeParameterDescription>
</feeParameter>
<feeParameter>
<feeParameterType>TKT</feeParameterType>
<feeParameterDescription>ET</feeParameterDescription>
</feeParameter>
</feeParameters>
</feeDetails>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0350</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 386 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<marketingCarrier>6X</marketingCarrier>
<operatingCarrier>6X</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0325</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
Page 387 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 388 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>6X</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<feeRef>
<referencingDetail>
<refQualifier>R</refQualifier>
</feeRef>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
Page 389 of 714
<fare>
<pricingMessage>
<description>LAST TKT DTE*02JUN16* - DATE OF ORIGIN</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LRT</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 390 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<feeRef>
<referencingDetail>
<refQualifier>R</refQualifier>
</feeRef>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>3</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 391 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*02JUN16* - DATE OF ORIGIN</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
Page 392 of 714
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 393 of 714
5.68 Operation: 06.2 Fee Option - Form of Payment
The form of payment option may be combined with any other option. A maximum of 3 forms of payment may
be specified.
It is optional that the traveller indicates some forms of payment.
Possible values are AGT, CC, CA, CK, GR, MS, NR, PT, SGR, UN.
If one form of payment is specified, the amount is optional.
If two forms of payment are specified, one amount must be specified.
If three forms of payment are specified, two amounts must be specified.
When the form of payment is specified as CC, a 6-digit bin number is required.
The example below illustrates a low fare search including optional form of payment.
Query Requirements:
Requesting Details
Specified Data


RC
200
ADT
Applicable on 1st trip
PAR
Trip arrival city of Nice
NCE
Trip date December, 21, 2007
211207
Form of payment 1
CC
Credit card bin number
123456
Amount applied on form of payment 1
100
Form of payment 2
CC
Credit card bin number
234566
Amount applied on form of payment 2
200

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
Page 394 of 714
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<formOfPayment>
<formOfPaymentDetails>
<type>CC</type>
<chargedAmount>100</chargedAmount>
<creditCardNumber>123456</creditCardNumber>
</formOfPaymentDetails>
<formOfPaymentDetails>
<type>CC</type>
<chargedAmount>200</chargedAmount>
<creditCardNumber>234566</creditCardNumber>
</formOfPaymentDetails>
</formOfPayment>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>211207</date>
Page 395 of 714
</timeDetails>
</itinerary>

Two FOP must not be provided without any amounts. If done, the whole request is rejected and the following
"CHECK FORMAT"
Three FOP must not be provided without any amounts. If done, the whole request is rejected and the following
"CHECK FORMAT"
Three FOP must not be provided with only one amount. If done, the whole request is rejected and the following
"CHECK FORMAT"
Three FOP must not be provided with three amounts. If done, the whole request is rejected and the following
"CHECK FORMAT"
More than three FOP cannot be entered. If done, the whole request is rejected and the following message
is returned:
"CHECK FORMAT"
A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, the
whole request is rejected and the following message is returned:
Page 396 of 714
5.69 Operation: 06.3 Fee Option - Sorting with/without Fees

This optional input allows sorting recommendations considering (or not) fees applying to fares in the ranking.
Possible values for OB fees are SORT: NOFEE or SORT: FEE.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>SORT</feeType>
<feeIdNumber>NOFEE</feeIdNumber>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 397 of 714
<timeDetails>
<date>211207</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OB</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<dataTypeInformation>
<subType>T02</subType>
<option>EX</option>
</dataTypeInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>FC4</subType>
<option>IN</option>
</feeInfo>
<associatedAmounts>
<monetaryDetails>
<typeQualifier>C</typeQualifier>
</monetaryDetails>
</associatedAmounts>
</feeDetails>
</feeOption>

Fees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected and
Page 398 of 714
"ENTRY NOT AUTHORISED"

Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and the
following message is returned:
Page 399 of 714
5.70 Operation: 06.4 Fee Option - Exempt all airline ticketing fees
Airline ticketing fees can all be exempted with this option.
It is optional.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 400 of 714
<timeDetails>
<date>211207</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OB</type>
<optionInformation>EX</optionInformation>
</feeTypeInfo>
</feeOption>

Fees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected and
Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and the
A specific fee can not be both added and exempted in input. If done, the whole request is rejected and the
Page 401 of 714
5.71 Operation: 06.5 Fee Option - Add/Exempt airline ticketing fees by subcode
Airline ticketing fees (OB fees) sub-codes can be specified in order to add or exempt particular fees.
The airline ticketing fees concept is driven from data filed by the airline.
A maximum of 6 sub-codes can be added or exempted. For each added FOP sub-code (neither exempted
subcode nor ticketing sub-code), an amount can be optionally specified.
If 1 FOP sub-code is added, theamount is optional.
If 2 FOP sub-codes are added, the 2 amounts are optional.
If 3 FOP sub-codes are added, 0 or 2 amounts can be specified but neither 1 no 3.
Note: that airline ticketing fees are not yet available in all markets or all carriers, for further details contact your
local Amadeus Help Desk.
Example:
Requesting Details
Specified Data
Exempting airline ticketing fees for sub-code T02
T02:EX
Adding airline ticketing fees applied on a credit card

with a bin number starting with 4
FC4:IN
Amount paid with credit card with a bin number

starting with 4 is 20.00 [1]
[1] Fees from FCA sub-code may apply also.
20.00

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
Page 402 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>211207</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OB</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>T02</subType>
<option>EX</option>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>FC4</subType>
<option>IN</option>
</feeInfo>
<associatedAmounts>
<monetaryDetails>
<typeQualifier>C</typeQualifier>
</monetaryDetails>
</associatedAmounts>
</feeDetails>
</feeOption>
Page 403 of 714

A sub-code cannot be added if OB Global Activation setting is OFF. If done, the whole request is rejected and
It is not allowed to enter an amount with an addition of a Ticketing sub-code. If done, the whole request is
"CHECK FORMAT"
FCA cannot be added in combination with another Form Of Payment sub-code. If done, the whole request is
"CHECK FORMAT"
Three Form Of Payment sub-codes must not be added with only one amount. If done, the whole request is
"CHECK FORMAT"
Three Form of Payment sub-codes must not be added with three amounts. If done, the whole request is rejected
and the following message is returned:
"CHECK FORMAT"
A sub-code cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected
and the following message is returned:
A sub-code cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and
A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, the
whole request is rejected and the following message is returned:
A specific fee can not be both added and exempted in input. If done, the whole request is rejected and the
Page 404 of 714
5.72 Operation: 06.6 Fee Option - Estimated FOP fees
When no Form of Payment is yet known, the user has the possibility to request an estimation of the Form of
Payment fees that may apply.
Any combination of at least 1 up to 6 kinds of fees can be requested in the input:
Minimum fee amount for credit card (FCN) and/or
Maximum fee amount for credit card (FCX) and/or
Minimum fee amount for debit card (FDN) and/or
Maximum fee amount for debit card (FDX) and/or
Minimum fee amount for any type of card (FON) and/or
Maximum fee amount for any type of card (FOX).

In case of redundancy, the system does not return the fees for any type of card in the output even if it was
requested. For example, if werequest minimum any card, minimum debit card, maximum debit card, maximum
credit card and maximum any card in input, we will have minimum any card,minimum debit card, maximum
debit card, maximum credit card in output.
In the example below, we request the minimum fee amount for any type of card (FON) and themaximum fee
amount for any type of card (FOX). In the reply, the minimum and the maximum fee amount for any type of
card (respectively FON and FOX) are returned.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>FON</priceType>
<priceType>FOX</priceType>
</pricingTicketing>
</pricingTickInfo>
Page 405 of 714
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251114</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>031214</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
Page 406 of 714
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0125</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
Page 407 of 714
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0120</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
Page 408 of 714
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amountType>OB</amountType>
</monetaryDetail>
<monetaryDetail>
<amountType>XOB</amountType>
</monetaryDetail>
<monetaryDetail>
<amountType>FON</amountType>
</monetaryDetail>
<monetaryDetail>
<amountType>FOX</amountType>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 409 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
<amountType>OB</amountType>
</monetaryDetails>
<monetaryDetails>
<amountType>XOB</amountType>
</monetaryDetails>
<pricingTicketing>
<priceType>OBI</priceType>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 410 of 714
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>RSAPFR</fareBasis>
</groupOfFares>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>R</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>RSAPFR</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 411 of 714
5.73 Operation: 07.1 Distribution Option - Airline Distribution: ADI

When the Airline distribution option is requested, the total number of recommendations are distributed over
2 sets as following:
Airline Diversity Set
This set contains the cheapest recommendation for each online carrier and the cheapest recommendation for
each Mono-Main carrier.
In case there is a recommendation online on a carrier and this carrier is also the main carrier on
another recommendation, and if the main carrier recommendation is cheaper than the online one,
both recommendations are returned. This means that for a carrier, in addition to the cheapest online
recommendation, the cheapest recommendation on which this carrier is also the main carrier is also returned
only if this recommendation is cheaper than the online one.
Cheapest Recommendations Set
This set contains the cheapest recommendations matching the client's query that are not included in the Airline
Diversity recommendations set.
In order to have more airline diversity within this set, the process guarantees that no more than 50% of the
recommendation has the same combination of main carriers over theitinerary.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>ADI</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
Page 412 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>140803</date>
</timeDetails>
</itinerary>
Page 413 of 714
5.74 Operation: 07.2 Distribution Option - Airline Distribution Container: ADC

When this option is requested, the total number of recommendations are distributed over 2 sets as following:
Airline Diversity Container
Up to 25% of the Total Number of recommendation is allocated to the airline diversity. This set of
recommendations is distributed over allthe different carriers ensuring at least the cheapest recommendation
for each online carrier and the cheapest recommendation for each MainCarrier.
In case there is a recommendation online on a carrier and this carrier is also the main carrier on
another recommendation, and if the main carrier recommendation is cheaper than the online one,
both recommendations are returned. This means that for a carrier, in addition to the cheapest online
recommendation, the cheapest recommendation on which this carrier is also the main carrier is also returned
only if this recommendation is cheaper than the online one.
Cheapest Recommendations Set
This set contains the cheapest recommendations matching the client's query that are not included in the Airline
Diversity Container.
cheapest recommendations set have the same combination of main carriers over the itinerary.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>ADC</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
Page 414 of 714
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>140803</date>
</timeDetails>
</itinerary>
Page 415 of 714
5.75 Operation: 07.3 Distribution option - Direct Distribution DDI

In order to enhance the quality of the recommendations returned by Master Pricer Travel Board, the direct
distribution process has been introduced to favour the recommendations which are direct.
Direct Recommendations can be naturally returned by Master Pricer if they are among the cheapest
recommendations. For example, if 250 recommendations are requested, a part or the total 250 can be direct.
In case there are not or too few direct recommendations, the process of the direct distribution will force the
direct recommendations in the returned solutions up to 20% of the requested number if they exist.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>DDI</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 416 of 714
<timeDetails>
<date>201210</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
</itinerary>

Page 417 of 714
5.76 Operation: 07.4 Distribution option - Not DDI: Deactivation of Direct

Distribution
Direct Distribution can be deactivated using the option NDD.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>NDD</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201210</date>
</timeDetails>
Page 418 of 714
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251210</date>
</timeDetails>
</itinerary>

Page 419 of 714
5.77 Operation: 07.5 Distribution option - Deactivation of ADI distribution

It is possible to deactivate the ADI distribution using the NAD option.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>NAD</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>140803</date>
</timeDetails>
</itinerary>
Page 420 of 714

Page 421 of 714
5.78 Operation: 07.6 Distribution option - Mono-Main Carrier Distribution

The total number of recommendations is distributed over 2 sets as following:
Mono-Main Carrier Diversity Set
This set contains the cheapest Mono-Main recommendation for each carrier.
In case several recommendations have the same amount, no preference is given to any carrier and so which
one will be selected is not predictable.
Cheapest Recommendation Set
This set contains all the cheapest recommendations matching the clients query that are not included in the
recommendations set built by the Mono-Main carrier distribution.
cheapest recommendations have the same combination of main carriers over the itinerary.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>MCD</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 422 of 714
<timeDetails>
<date>140803</date>
</timeDetails>
</itinerary>
Page 423 of 714
5.79 Operation: 07.7 Distribution Option - Ratios for Weighted

Recommendations
This option allows to return a combination of 3 different types of recommendations in output of Master Pricer
TravelBoard Search: One-Way outbound (OWO), One-Way inbound (OWI) and Round Trip (RT).
The user has to specify the Multi-ticket option (MTK) and the 3 ratios for each type of recommendations, X %
for OWO, Y% for OWI and Z % for RT with (X+Y+Z = 100).
Instead of 3 separated queries, the user benefits from this option that only one query is needed to process the
mixed type of 3. The recommendations in output are the cheapest of each type (X% cheapest of OW outbound,
Y% cheapest of OW inbound, Z% cheapest of Round Trip).

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>OWO</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>OWI</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>RT</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>MTK</priceType>
Page 424 of 714
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>ATH</locationId>
<timeDetails>
<date>200913</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<locationId>ATH</locationId>
</departurePoint>
<timeDetails>
<date>290913</date>
</timeDetails>
</itinerary>

Page 425 of 714
Page 426 of 714
5.80 Operation: 07.8 Distribution Option - Non-Stop Preferred

When this option is requested, recommendations made of Non-Stop flights only on the whole itinerary are
favoured. The user has the possibility to specify a weight of Non-Stop recommendations to be returned.
This weight is the percentage of total number of recommendations that could be returned for Non-Stop flight
recommendations, if enough exist and without airline distribution.
A weight equals to 0 deactivates the Non-Stop preferred option.
If not specified, the applicable weight is 75%.
The following example illustrates a Non-Stop distribution request with a weight of 50%.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>RNP</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>DNP</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
Page 427 of 714
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>CHI</locationId>
<timeDetails>
<date>060814</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
<locationId>CHI</locationId>
</departurePoint>
<timeDetails>
<date>130814</date>
</timeDetails>
</itinerary>

Page 428 of 714
5.81 Operation: 08.01 Output Option - Empty Cells Clarification

When searching cheapest solution on a given itinerary on fixed or flexible dates, the search can have no local
solution for the following reasons:
No proposed segments has been found for a requested segment on a date.

No available flight has been found for a requested segment on a date.
No fare has been found for a date combination (for calendar products).
No journey has been found for a date combination (for calendar products).
Cross over in a date combination.
When the Empty Cells Clarification option is activated, and those cases are met during the search, the
corresponding information is returned in the output message.
For dates out of the range of the request, for example when a trip duration is specified, no precision is given in
the output message as it is the case for the default behaviour when this option is not activated.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
Page 429 of 714
<priceType>ECC</priceType>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>120202</date>
</timeDetails>
</itinerary>
Page 430 of 714
5.82 Operation: 08.02 Output Option - Rank in Journey Server

The user has the ability to request the display of the rank of the Flight Solution within the list of Flight Solutions
returned by Journey Server (numbering starts to 1) per requested segment.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RJS</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 431 of 714
<timeDetails>
<date>120202</date>
</timeDetails>
</itinerary>
Page 432 of 714
5.83 Operation: 08.03 Output Option - Value Search at itinerary level

At itinerary level, the user has the possibility to evaluate the more convenient solutions, depending of a list of
criteria defined in input, such as trip time, carrier preference, arrival time, and so on.
For each criteria, a weight must be specified for each attribute. In case of a criteria with no attribute, a default
weight must be specified.
The user can simultaneously request up to 20 criteria by default.
Query description
List of supported criteria:
Designation
Code
Attributes
Influence
Unit
Number of
Connection
CNX
None
Penalty
Price per connection
Online Marketing
Carrier
OCX
None
Bonus
Price
Change of Airport
COA
None
Penalty
Price per change of

airport
Total Trip Time
EFT
None
Penalty
Price per hour
Overnight
Connection
OVC
None
Penalty
Price per overnight
Ground Time
GRT
None
Penalty
Price per hour
Preferred Carrier
PCX
List of Carriers
Bonus
Price per 100% EFT

flown
Unpreferred
Carriers
UCX
List of Carriers
Penalty
Price per 100% EFT

flown
Departure Time
DET
List of Codeset (*)
Bonus
Price
Arrival Time
ART
List of codeset (*)
Bonus
Price
Fully Flexible Fare
FLX
None
Bonus
Price
Risk to miss a
connection
RMC
None
Penalty
Price
Interline carrier
ICX
None
Bonus
Price
Distance to
requested date
DRD
None
Penalty
Price per day of

difference to
Unpreferred TLA
ULC
None
Penalty
Price per 100% EFT

flown
Number of stops
STP
None
Penalty
Price per stop
Preferred alliance
PAL
List of Alliances
Bonus
Price per 100% EFT

flown
Page 433 of 714
Transportation time
RTT
None
Penalty
Price per hour of

time flown
(*) List of codeset for time window:

Name
Code
Range
Early morning
ERL
04:00-06:59
Morning
MRN
07:00-10:59
Midday
MID
11:00-13:59
Afternoon
AFT
14:00-18:59
Evening
EVN
19:00-21:59
Night
NGT
22:00-03:59
Reply Description
A global value is returned for each recommendation. In addition, a flag is also returned if the fare is fully flexible.
Note that, although the recommendations are still sorted by price, the global value listis forward sorted.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<conversionRate>
<conversionType>COV</conversionType>
</conversionRate>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
Page 434 of 714
<carrierId>6X</carrierId>
<carrierId>7S</carrierId>
<carrierId>9S</carrierId>
</companyIdentity>
</travelFlightInfo>
<valueSearch>
<criteriaCode>CNX</criteriaCode>
<value>20</value>
</valueSearch>
<valueSearch>
<criteriaCode>UCX</criteriaCode>
<value>10</value>
<criteriaDetails>
<value>20</value>
<attribute>AF</attribute>
</criteriaDetails>
<criteriaDetails>
<value>30</value>
<attribute>AA</attribute>
</criteriaDetails>
<criteriaDetails>
<attribute>BA</attribute>
<attribute>AY</attribute>
<attribute>TK</attribute>
</criteriaDetails>
<criteriaDetails>
<value>40</value>
<attribute>EC</attribute>
<attribute>IB</attribute>
<attribute>OS</attribute>
</criteriaDetails>
</valueSearch>
<valueSearch>
<criteriaCode>FLX</criteriaCode>
<value>250</value>
</valueSearch>
<itinerary>
<segRef>1</segRef>
<departurePoint>
Page 435 of 714
<locationId>ROM</locationId>
</departurePoint>
<timeDetails>
<date>240716</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<locationId>ROM</locationId>
<timeDetails>
<date>250716</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
Page 436 of 714
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0240</ref>
</flightProposal>
<flightProposal>
<ref>BA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>FCO</locationId>
</location>
<location>
</location>
<companyId>
<marketingCarrier>BA</marketingCarrier>
<operatingCarrier>BA</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 437 of 714
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0250</ref>
</flightProposal>
<flightProposal>
<ref>AZ</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<marketingCarrier>AZ</marketingCarrier>
<operatingCarrier>AZ</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
Page 438 of 714
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>0250</ref>
</flightProposal>
<flightProposal>
<ref>VY</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
Page 439 of 714
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0230</ref>
</flightProposal>
<flightProposal>
<ref>BA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 440 of 714
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0230</ref>
</flightProposal>
<flightProposal>
<ref>AZ</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<marketingCarrier>AZ</marketingCarrier>
<operatingCarrier>AZ</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>32S</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
Page 441 of 714
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>0225</ref>
</flightProposal>
<flightProposal>
<ref>VY</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
Page 442 of 714
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
<refQualifier>V</refQualifier>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>BA</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
Page 443 of 714
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*23DEC15* - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OAP2V1H</fareBasis>
</groupOfFares>
<majCabin>
Page 444 of 714
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OAP2V1H</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
Page 445 of 714
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>AZ</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*21JUL16* - SEE ADV PURCHASE</description>
</pricingMessage>
Page 446 of 714
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>W</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>WSP8C</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LSP8C</fareBasis>
</groupOfFares>
<majCabin>
Page 447 of 714
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>VY</company>
</codeShareDetails>
<codeShareDetails>
</codeShareDetails>
</paxFareDetail>
Page 448 of 714
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>D</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>DRTBIZ</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
Page 449 of 714
<rbd>D</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>DRTBIZ</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<value>
<ref>1</ref>
<value>431.44</value>
<criteriaDetails>
<type>FLX</type>
</criteriaDetails>
</value>
<value>
<ref>2</ref>
</value>
<value>
<ref>3</ref>
</value>
Page 450 of 714
5.84 Operation: 08.04 Output Option - Value Search at requested segment

level
At requested segment level, the user has the possibility to evaluate the more convenient solutions, depending
of a list of criteria defined in input, such as trip time, carrier preference, arrival time, and so on.
For each criteria, a weight must be specified for each attribute. In case of a criteria with no attribute, a default
weight must be specified.
Note that in this case, the value returned in output for each recommendation is computed for the whole itinerary.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<conversionRate>
<conversionType>COV</conversionType>
</conversionRate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 451 of 714
<timeDetails>
<date>200116</date>
</timeDetails>
<valueSearch>
<criteriaCode>OCX</criteriaCode>
<value>30</value>
</valueSearch>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>230116</date>
</timeDetails>
<valueSearch>
<criteriaCode>PCX</criteriaCode>
<value>10</value>
<criteriaDetails>
<value>20</value>
<attribute>AF</attribute>
</criteriaDetails>
<criteriaDetails>
<value>30</value>
<attribute>AA</attribute>
</criteriaDetails>
<criteriaDetails>
<attribute>BA</attribute>
</criteriaDetails>
Page 452 of 714
</valueSearch>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>3920</ref>
</flightProposal>
<flightProposal>
<ref>VA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>CDG</locationId>
<terminal>2C</terminal>
</location>
Page 453 of 714
<location>
</location>
<companyId>
<marketingCarrier>VA</marketingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>BNE</locationId>
<terminal>I</terminal>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 454 of 714
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>BNE</locationId>
<terminal>D</terminal>
</location>
<location>
</location>
<companyId>
<operatingCarrier>VA</operatingCarrier>
</companyId>
<productDetail>
<equipmentType>73H</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>2355</ref>
</flightProposal>
<flightProposal>
<ref>KE</ref>
</flightProposal>
Page 455 of 714
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<terminal>2E</terminal>
</location>
<location>
<locationId>ICN</locationId>
</location>
<companyId>
<marketingCarrier>KE</marketingCarrier>
<operatingCarrier>KE</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
Page 456 of 714
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>2540</ref>
</flightProposal>
<flightProposal>
<ref>VA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
Page 457 of 714
</location>
<companyId>
<operatingCarrier>VA</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<terminal>2A</terminal>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
Page 458 of 714
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>3905</ref>
</flightProposal>
<flightProposal>
<ref>KE</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
Page 459 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 460 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>VA</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
Page 461 of 714
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>LKRFR</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>L</rbd>
Page 462 of 714
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VZRFRS</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VZRFRS</fareBasis>
Page 463 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
Page 464 of 714
<codeShareDetails>
<company>KE</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
<monetaryDetail>
</monetaryDetail>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*13JAN16* - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
Page 465 of 714
</cabinProduct>
<fareProductDetail>
<fareBasis>QLXAPKE</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>YEEKZ</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>D</rbd>
<cabin>C</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>DBIZKR</fareBasis>
Page 466 of 714
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QLXAPKE</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<value>
<ref>1</ref>
</value>
<value>
<ref>2</ref>
</value>
Page 467 of 714
5.85 Operation: 08.05 Output Option - Display Minimum/Maximum Stay

The user has the possibility to display the minimum and the maximum stay at fare component level with the
MST option in the query.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>MST</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<depMultiCity>
</depMultiCity>
<arrivalMultiCity>
</arrivalMultiCity>
<timeDetails>
Page 468 of 714
<date>140814</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
<currency>INR</currency>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1050</ref>
</flightProposal>
<flightProposal>
<ref>FI</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
Page 469 of 714
</location>
<location>
<locationId>KEF</locationId>
</location>
<companyId>
<marketingCarrier>FI</marketingCarrier>
<operatingCarrier>FI</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>EWR</locationId>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
Page 470 of 714
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<totalFareAmount>40253</totalFareAmount>
<totalTaxAmount>23648</totalTaxAmount>
<codeShareDetails>
<company>FI</company>
</codeShareDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
Page 471 of 714
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>20FEB14</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 472 of 714
<fareBasis>HQO3ECON</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HQO3ECON</fareBasis>
<fareFamiliesRef>
<referencingDetail>
<refQualifier>M</refQualifier>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<mnrGrp>
<mnr>
<category>LST</category>
</mnr>
<mnrDetails>
<mnrRef>
<itemNumberDetails>
<number>1</number>
</mnrRef>
<dateInfo>
Page 473 of 714
<dateAndTimeDetails>
<qualifier>MSC</qualifier>
<date>05OCT14</date>
</dateAndTimeDetails>
<dateAndTimeDetails>
<qualifier>MSP</qualifier>
<date>05DEC14</date>
</dateAndTimeDetails>
</dateInfo>
</mnrDetails>
</mnrGrp>
Page 474 of 714
5.86 Operation: 08.07 Output Option - Fare Family information
Depending on Office ID setting and input option (FFI), Master Pricer can return:
The airline fare family name at fare component level and/or at requested segment level.
The airline fare family description per requested segment consistently with airline filling:
The services included in the fare family for free
The services that can be bought at a charge
The services that are not valid for this fare family but that should be displayed to the customer.
Input option: FFI with 3 values (1, 2 or 3)
Fare family information
1
value
FF name at fare
component level
Resulting FF name at
requested segment level
Services of the resulting

x
FF
For each service, the output should include commercial description (text) filed in by the airline as well as the
OC subcode.
In the following example,
At fare component level:
Fare family VALUE is applied on fare component LON-NYC.
Fare family BASIC is applied on fare component NYC-LON.

At requested segment level:
Fare family VALUE is applied on the outbound.
Fare family BASIC is applied on the inbound.

VALUE fare family description:
Fare Family short description:ECONOMY VALUE
Services included:
OC Sub code: LMS
Commercial description: LIGHT MEAL SNACK
Services at a charge:
OC Sub code CB5
Commercial description: CHNG BEF DEP 50 EUR
BASIC Fare family description:
Fare family short description:ECONOMY BASIC
Services included:
OC Sub code: LMS
Commercial description: LIGHT MEAL SNACK
Services not offered:

OC Sub code CB0
Page 475 of 714
Commercial description: CHNG BEF DEP

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>FFI</feeType>
</feeId>
</feeIdDescription>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
Page 476 of 714
</departurePoint>
<timeDetails>
<date>101114</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201114</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
Page 477 of 714
</conversionRate>
<familyInformation>
<fareFamilyname>VALUE</fareFamilyname>
<description>ECONOMY VALUE</description>
<services>
<reference>1</reference>
<status>INC</status>
</services>
<services>
<status>CHA</status>
</services>
<familyInformation>
<fareFamilyname>BASIC</fareFamilyname>
<description>ECONOMY BASIC</description>
<services>
</services>
<services>
<status>NOF</status>
</services>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0755</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
Page 478 of 714
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0655</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
Page 479 of 714
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
Page 480 of 714
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>VS</company>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
Page 481 of 714
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>27APR14</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
Page 482 of 714
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OLXMGE</fareBasis>
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OLXMGE</fareBasis>
Page 483 of 714
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</serviceTypeInfo>
<globalMessageMarker/>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>LMS</subType>
</serviceOptionInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
<type>SD</type>
</itemNumberInfo>
<commercialName>
<freeText>LIGHT MEAL SNACK</freeText>
</commercialName>
</feeDescriptionGrp>
</serviceDetailsGrp>
<serviceDetailsGrp>
<serviceOptionInfo>
Page 484 of 714
<subType>CB0</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>2</number>
<type>SD</type>
</itemNumberInfo>
<commercialName>
<freeText>CHNG BEF DEP</freeText>
</commercialName>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>CB5</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>3</number>
<type>SD</type>
</itemNumberInfo>
<commercialName>
<freeText>CHNG BEF DEP 50 EUR</freeText>
</commercialName>
</serviceFeesGrp>
Page 485 of 714
5.87 Operation: 08.08 Output Option - Return flight duration at segment level
The flight duration can be returned at segment level. This option is triggered by a Fare Search parameter.
In this example:
IAD-SFO UA492: the flight duration is 06H00
SFO-DFW AA 1052: the flight duration is 03H15
DFW-IAD AA 1489: The flight duration is 02H50

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>IAD</locationId>
</departurePoint>
<locationId>SFO</locationId>
<timeDetails>
<date>110514</date>
</timeDetails>
</itinerary>
Page 486 of 714
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>210514</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0600</ref>
</flightProposal>
Page 487 of 714
<flightProposal>
<ref>UA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
<productDetailQualifier>IAC</productDetailQualifier>
</addProductDetail>
<attributeDetails>
<attributeType>EFT</attributeType>
<attributeDescription>0600</attributeDescription>
</attributeDetails>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
Page 488 of 714
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0855</ref>
</flightProposal>
<flightProposal>
<ref>AA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
<locationId>DFW</locationId>
</location>
<companyId>
<marketingCarrier>AA</marketingCarrier>
<operatingCarrier>AA</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
<attributeDetails>
</attributeDetails>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
Page 489 of 714
</productDateTime>
<location>
<locationId>DFW</locationId>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
<attributeDetails>
</attributeDetails>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 490 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<codeShareDetails>
<company>AA</company>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
Page 491 of 714
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>T</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>TAA21IGN</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OA21ERA1</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
Page 492 of 714
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>OA21ERA1</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 493 of 714
5.88 Operation: 08.09 Output Option - Commission returned
The user has the ability to have the commission (in percentage) for each fare basis returnd in output of Master
Pricer. This is triggered by Office ID setting
When the commission is filed directly in percentage, the filed value is returned.
When the commission is filed in amount, the percentage returned is calculated on the filed selling amount.
The example below illustrates recommendations with commission percentage (13.34 %) returned for each fare
component.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>SEL</locationId>
</departurePoint>
Page 494 of 714
<timeDetails>
<date>221014</date>
</timeDetails>
<flightInfo>
<companyIdentity>
</companyIdentity>
</flightInfo>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1200</ref>
</flightProposal>
<flightProposal>
<ref>6x</ref>
</flightProposal>
Page 495 of 714
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>1320</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
Page 496 of 714
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
Page 497 of 714
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<currency>YQ</currency>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
Page 498 of 714
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>CORPORATE NAME XX07</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
Page 499 of 714
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>COMM</fareBasis>
<fareType>RC</fareType>
<ticketInfos>
<discountDetails>
<fareQualifier>CM</fareQualifier>
<percentage>13.34</percentage>
</discountDetails>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
Page 500 of 714
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
Page 501 of 714
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>CORPORATE NAME XX07</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 502 of 714
<ticketInfos>
<discountDetails>
<fareQualifier>CM</fareQualifier>
<percentage>13.34</percentage>
</discountDetails>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 503 of 714
5.89 Operation: 08.10 Output Option - Ticketing Point Mileage

The user has the ability to have the display of the TPM at flight level. This is triggered by Office ID setting.
The example bellow illustrates a reply with TPM returned at flight level:
TPM
NCE-LHR
641
LHR-EWR
3463

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>010315</date>
</timeDetails>
</itinerary>
Page 504 of 714

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1115</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
Page 505 of 714
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
<attributeDetails>
<attributeType>TPM</attributeType>
</attributeDetails>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
<attributeDetails>
Page 506 of 714
<attributeType>TPM</attributeType>
</attributeDetails>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
Page 507 of 714
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>LAST TKT DTE*01MAR15</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
Page 508 of 714
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>W2EO</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>W</rbd>
<cabin>W</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>W2EO</fareBasis>
</groupOfFares>
<majCabin>
<designator>W</designator>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 509 of 714
5.90 Operation: 08.11 Output option - Return Airline Alliance

The user has the ability to have the Airline Alliance code at flight level in the reply.
The functionality is triggered by a setting at OID level.
In the example, 2 Alliances are returned:
LAN: oneworld (*O)
Lufthansa: StarAlliance (*A)

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
<carrierId>LH</carrierId>
<carrierId>LA</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
Page 510 of 714
<departurePoint>
<locationId>SCL</locationId>
</departurePoint>
<timeDetails>
<date>271114</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1750</ref>
</flightProposal>
<flightProposal>
<ref>LH</ref>
</flightProposal>
Page 511 of 714
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>SCL</locationId>
</location>
<location>
<locationId>GRU</locationId>
</location>
<companyId>
<marketingCarrier>LA</marketingCarrier>
<operatingCarrier>LA</operatingCarrier>
</companyId>
<flightOrtrainNumber>O</flightOrtrainNumber>
<productDetail>
</productDetail>
<addProductDetail>
<lastSeatAvailable>Y</lastSeatAvailable>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<locationId>GRU</locationId>
</location>
<location>
</location>
<companyId>
Page 512 of 714
<marketingCarrier>LH</marketingCarrier>
<operatingCarrier>LH</operatingCarrier>
</companyId>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>LH</company>
</codeShareDetails>
<codeShareDetails>
<company>LA</company>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
Page 513 of 714
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
<monetaryDetail>
</monetaryDetail>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>S</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HLRCOWCL</fareBasis>
Page 514 of 714
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>HLRCOWCL</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 515 of 714
5.91 Operation: 08.12 Output Option : Homegeneous Upsell

The Upsell option returns up to 6 (this can be limited due to operational impact) alternative recommendations
attached to higher fare family than the basic recommendation one .
The price of the upsell recommendation is higher than the basic recommendation price.
The homogenous upsell option applies at itinerary level based on the resulting fare family for the whole itinerary
In case of Homogeneous upsell request, eligible recommendations that will propose an upsell involves
mandatory the same marketing carrier cross all bounds and segments
The order of upsell is driven by increasing price of the recommendations and not the tier of the upsell fare family.
A recommendation containing an upsell is called "eligible". If an upsell recommendation has itself an upsell ,
this upsell is moved to the eligible one.
Input activation :
UPH option :
<feeIdDescription>
<feeId>
</feeId>
<feeId>
<feeType>UPH</feeType>
</feeId>
</feeIdDescription>
Page 516 of 714
A list of marketing carriers for which upsell must be processed (optional). By default, if not specified, upsell
process applies on all the eligible marketing carriers in output :
<travelFlightInfo>
<companyIdentity>
<carrierQualifier>U</carrierQualifier>
<carrierId>ZZ</carrierId>
</companyIdentity>
</travelFlightInfo>
In output :
U qualifier in RefQualifier field (this recommendation has 2 upsells) :
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
Page 517 of 714
<refQualifier>U</refQualifier>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
Same travel solution for elligible and different fare family for the elligible and upsell recommendations : this
recommendation has an upsell which is the 8th recommendation and its fare family are : 0 / 1
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
Page 518 of 714
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 519 of 714
<referencingDetail>
This recommendation is the upsell from the above recommendation. We can see that the travel solution is the
same (S2 / S11) but the fare family is different ) 0 / 2 here instead of 0 /1 for the elligible recommendation).
<itemNumberId>
<number>8</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
Page 520 of 714
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 521 of 714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>PSB</priceType>
<priceType>TAC</priceType>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
<feeIdDescription>
<feeId>
</feeId>
<feeId>
<feeType>UPH</feeType>
</feeId>
Page 522 of 714
</feeIdDescription>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>CGK</locationId>
<timeDetails>
<date>110714</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
Page 523 of 714
<date>270914</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OB</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>FCA</subType>
<option>IN</option>
</feeInfo>
</feeDetails>
</feeOption>
Page 524 of 714
5.92 Operation: 08.13 Output Option : Upsell per bound

The Upsell option returns up to 6 (this can be limited due to operational impact) alternative recommendations
attached to higher fare family than the basic recommendation one .
The price of the upsell recommendation must be higher than the basic recommendation price.
The Upsell per Bound option applies at bound level based , meaning that fare family can be different for each
bound.
There may have 2 different marketting carriers in the itinerary , the upsell is still computed.
The order of upsell is driven by increasing price of the recommendations and not the tier of the upsell fare family.
A recommendation containing un upsell is called "eligible". All references to upsells are returned at eligible
recommendation level.
Input activation :
UPB option :
<feeIdDescription>
<feeId>
</feeId>
<feeId>
<feeType>UPB</feeType>
</feeId>
</feeIdDescription>
Page 525 of 714
A list of marketing carriers for which upsell must be processed (optional). By default, if not specified, upsell
process applies on all the eligible marketing carriers in output :
<travelFlightInfo>
<companyIdentity>
<carrierId>XX</carrierId>
</companyIdentity>
</travelFlightInfo>
In output :
U qualifier in RefQualifier field (this recommendation has 2 upsells) :
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 526 of 714
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
Same travel solution for elligible and different fare family for the elligible and upsell recommendations : this
recommendation has an upsell which is the 8th recommendation and its fare family are : 0 / 1
<itemNumberId>
<number>2</number>
Page 527 of 714
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 528 of 714
<referencingDetail>
This recommendation is the upsell from the above recommendation. We can see that the travel solution is the
same (S2 / S11) but the fare family is different ) 0 / 2 here instead of 0 /1 for the elligible recommendation).
<itemNumberId>
<number>8</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
Page 529 of 714
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 530 of 714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>PSB</priceType>
<priceType>TAC</priceType>
</pricingTicketing>
</pricingTickInfo>
<corporate>
<corporateId>
</corporateId>
</corporate>
<feeIdDescription>
<feeId>
</feeId>
<feeId>
<feeType>UPB</feeType>
</feeId>
Page 531 of 714
</feeIdDescription>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>110714</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
Page 532 of 714
<date>270914</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OB</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>FCA</subType>
<option>IN</option>
</feeInfo>
</feeDetails>
</feeOption>
Page 533 of 714
5.93 Operation: 09.01 Output Option - Change Of Gauge

This example illustrates a 'Change Of Gauge' flight solution.
The reply has been limited to 3 units (instead of 200) this is primarily due to the size of the output.
In Proposed segment 2, see the Change Of Gauge (in other words, change of equipment) on flight IB6173
between MAD and SJO. Traveller stops in MIA and changes of equipment Boeing 747 => Airbus 319.
Item
Value
/replyStatus/
status/advisoryTypeInfo
FQX
/conversionRate/
conversionRateDetail/currency
USD
/flightIndex/
requestedSegmentRef/segRef
/flightIndex/groupOfFlights[11] /
propFlightGrDetail/
flightProposal[11] /ref
propFlightGrDetail/
1305
propFlightGrDetail/
flightProposal[21] /unitQualifier
EFT
propFlightGrDetail/
S3
propFlightGrDetail/
MCX
200703
flightDetails[11] /flightInformation/
productDateTime/dateOfDeparture
1200
productDateTime/timeOfDeparture
10
productDateTime/dateOfArrival
200703
11
productDateTime/timeOfArrival
1500
Page 534 of 714
12
location[11] /locationId
MAD
13
location[11] /terminal
14
CCS
15
companyId/marketingCarrier
S3
16
companyId/operatingCarrier
S3
17
flightDetails[11] /
flightInformation/flightNumber
1333
18
productDetail/equipmentType
D10
19
N
addProductDetail/electronicTicketing
20
200703
21
1615
22
200703
23
1705
24
CCS
Page 535 of 714
25
SJO
26
LR
27
LR
28
flightDetails[21] /
611
29
320
30
N
31
propFlightGrDetail/
32
propFlightGrDetail/
1415
33
propFlightGrDetail/
EFT
34
propFlightGrDetail/
IB
35
propFlightGrDetail/
MCX
36
200703
flightDetails/flightInformation/
37
1215
Page 536 of 714
38
200703
39
1830
40
MAD
41
42
SJO
43
IB
44
IB
45
flightDetails/
6173
46
747
47
Y
48
productDetail/techStopNumber
49
flightDetails/technicalStop/
stopDetails[11] /dateQualifier
AA
50
stopDetails[11] /date
200703
Page 537 of 714
51
stopDetails[11] /firstTime
1540
52
stopDetails[11] /locationId
MIA
53
stopDetails[21] /dateQualifier
AD
54
stopDetails[21] /date
200703
55
stopDetails[21] /firstTime
1645
56
stopDetails[21] /equipmentType
319
57
N
addProductDetail[21] //electronicTicketing
58
propFlightGrDetail/
59
propFlightGrDetail/
2505
60
propFlightGrDetail/
EFT
61
propFlightGrDetail/
AA
62
propFlightGrDetail/
MCX
63
200703
Page 538 of 714
64
1655
65
200703
66
1815
67
MAD
68
69
LHR
70
71
IB
72
IB
73
flightDetails[11] /
3166
74
752
75
Y
76
200703
Page 539 of 714
77
2005
78
200703
79
2250
80
LHR
81
82
JFK
83
84
AA
85
AA
86
flightDetails[21] /
141
87
777
88
N
89
210703
Page 540 of 714
90
0640
91
210703
92
1000
93
JFK
94
95
SJO
96
LR
97
LR
98
flightDetails[31] /
663
99
320
100
N
101
itemNumber/
itemNumberId/number
102
/recommendation[11] /recPriceInfo/ 734.60

monetaryDetail[11] /amount
103

Page 541 of 714
104
segmentFlightRef/
referencingDetail/refQualifier
105
segmentFlightRef/
referencingDetail/refNumber
106
paxFareProduct/
paxFareDetail/paxFareNum
107
paxFareProduct/
paxFareDetail/totalFareAmount
734.60
108
paxFareProduct/
paxFareDetail/totalTaxAmount
9.60
109
ADT
paxFareProduct/paxReference/ptc
110
paxFareProduct/paxReference/
traveller/ref
111
LTD
paxFareProduct/
freeTextQualification/messageQualifier
112
40
paxFareProduct/
freeTextQualification/messageCode
113
paxFareProduct/fare/
pricingMessage/ description[11]
LAST TKT DTE
114
pricingMessage/description[21]
20FEB03
115
- SEE ADV PURCHASE
116
paxFareProduct/fareDetails/
segmentRef/segRef
117
Page 542 of 714
productInformation[11] /
avlProductDetails/rbd
118
avlProductDetails/avlStatus
119
fareProductDetail/fareBasis
MHOW
120
fareProductDetail/passengerType
ADT
121
fareProductDetail/fareType
RP
122
123
124
MHOW
125
ADT
126
RP
127
itemNumber/
itemNumberId/number
Page 543 of 714
128

129

130
segmentFlightRef/
131
segmentFlightRef/
132
paxFareProduct/
133
paxFareProduct/
973.10
134
paxFareProduct/
8.10
135
ADT
136
traveller/ref
137
PEN
paxFareProduct/
fare[11] /pricingMessage/
138
71
paxFareProduct/
139
paxFareProduct/fare[11] /
pricingMessage/description
140
LTD
paxFareProduct/
141
paxFareProduct/
TICKETS ARE NONREFUNDABLE AFTER

DEPARTURE
40
Page 544 of 714
142
LAST TKT DTE
143
06FEB03
144
- SEE ADV PURCHASE
145
segmentRef/segRef
146
productInformation/
147
productInformation/
148
productInformation/
BHSXOW
149
productInformation/
ADT
150
productInformation/
RP
151
itemNumber/
itemNumberId/number
152

153

Page 545 of 714
154
segmentFlightRef/
155
segmentFlightRef/
156
paxFareProduct/
157
paxFareProduct/
1001.22
158
paxFareProduct/
26.22
159
ADT
160
traveller/ref
161
PEN
paxFareProduct/
162
71
paxFareProduct/
163
pricingMessage/description
164
LTD
paxFareProduct/
165
40
paxFareProduct/
166
TICKETS ARE NONREFUNDABLE AFTER

DEPARTURE
LAST TKT DTE
Page 546 of 714
167
06FEB03
168
- SEE ADV PURCHASE
169
segmentRef/segRef
170
171
172
KHSXOW
173
ADT
174
RP
175
176
177
KHSXOW
Page 547 of 714
178
ADT
179
RP
180
181
182
KHSXOW
183
ADT
184
RP

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
Page 548 of 714
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<locationId>SJO</locationId>
<timeDetails>
<date>200703</date>
</timeDetails>
</itinerary>

Page 549 of 714
5.94 Operation: 09.02 Output Option - Fare Calculation

This option allows the user to request the entire fare calculation.
When the FS Parameter Gb_Fare_Calculation is set, the following informationis displayed:
Fare Details Information:

The Total amount per fare component (FCA)
The Q surcharges per segment of a fare component (Q)
The Stopover surcharges per segment of a fare component (S)
The Mileage per fare component (M)
Conversion rate information:

The fare calculation currency
The rate of exchange
Passenger information:
The taxes details.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
Page 550 of 714
</departurePoint>
<timeDetails>
<date>051214</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
<conversionType>FCC</conversionType>
<currency>NUC</currency>
<rate>0.595825</rate>
<rate>1.259213</rate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1420</ref>
Page 551 of 714
</flightProposal>
<flightProposal>
<ref>EI</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<terminal>S</terminal>
</location>
<location>
<locationId>DUB</locationId>
</location>
<companyId>
<marketingCarrier>EI</marketingCarrier>
<operatingCarrier>EI</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
Page 552 of 714
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>2125</ref>
</flightProposal>
<flightProposal>
<ref>EI</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
Page 553 of 714
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 554 of 714
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>1955</ref>
</flightProposal>
<flightProposal>
<ref>BA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
Page 555 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>4</ref>
</flightProposal>
<flightProposal>
<ref>0740</ref>
</flightProposal>
<flightProposal>
<ref>BA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 556 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 557 of 714
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>EI</company>
</codeShareDetails>
<codeShareDetails>
</codeShareDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<passengerTaxDetails>
<taxDetails>
<rate>36.55</rate>
<countryCode>AC</countryCode>
<type>YQ</type>
</taxDetails>
<taxDetails>
<rate>86.89</rate>
<countryCode>AD</countryCode>
<type>GB</type>
</taxDetails>
<taxDetails>
<rate>17.49</rate>
<countryCode>AS</countryCode>
<type>UB</type>
</taxDetails>
<taxDetails>
<rate>16.95</rate>
<type>UP</type>
Page 558 of 714
</taxDetails>
<taxDetails>
<rate>7.50</rate>
<countryCode>DO</countryCode>
<type>UQ</type>
</taxDetails>
<taxDetails>
<rate>4.05</rate>
<countryCode>AE</countryCode>
<type>YC</type>
</taxDetails>
<taxDetails>
<rate>12.88</rate>
<type>US</type>
</taxDetails>
<taxDetails>
<rate>3.68</rate>
<countryCode>CO</countryCode>
<type>XA</type>
</taxDetails>
<taxDetails>
<rate>5.15</rate>
<countryCode>CR</countryCode>
<type>XY</type>
</taxDetails>
</passengerTaxDetails>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE*10JUL14* - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
Page 559 of 714
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Z</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ZLWGDS13</fareBasis>
<fareCalculationCodeDetails>
<qualifier>FCA</qualifier>
</fareCalculationCodeDetails>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>VLW1GDS</fareBasis>
<qualifier>Q</qualifier>
<locationCode>DUB</locationCode>
<otherLocationCode>JFK</otherLocationCode>
</groupOfFares>
<majCabin>
Page 560 of 714
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
Page 561 of 714
<taxDetails>
<rate>134.11</rate>
<type>YQ</type>
</taxDetails>
<taxDetails>
<rate>86.89</rate>
<type>GB</type>
</taxDetails>
<taxDetails>
<rate>13.93</rate>
<type>UB</type>
</taxDetails>
<taxDetails>
<rate>2.53</rate>
<type>UP</type>
</taxDetails>
<taxDetails>
<rate>7.50</rate>
<countryCode>DO</countryCode>
<type>UQ</type>
</taxDetails>
<taxDetails>
<rate>4.05</rate>
<type>YC</type>
</taxDetails>
<taxDetails>
<rate>12.88</rate>
<type>US</type>
</taxDetails>
<taxDetails>
<rate>3.68</rate>
<type>XA</type>
</taxDetails>
<taxDetails>
<rate>5.15</rate>
<type>XY</type>
</taxDetails>
<fare>
Page 562 of 714
<pricingMessage>
<description>LAST TKT DTE*05DEC14* - DATE OF ORIGIN</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>Y1JB</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 563 of 714
<qualifier>M</qualifier>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
Page 564 of 714
</codeShareDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<taxDetails>
<rate>134.11</rate>
<type>YQ</type>
</taxDetails>
<taxDetails>
<rate>86.89</rate>
<type>GB</type>
</taxDetails>
<taxDetails>
<rate>55.93</rate>
<type>UB</type>
</taxDetails>
<taxDetails>
<rate>4.05</rate>
<type>YC</type>
</taxDetails>
<taxDetails>
<rate>12.88</rate>
<type>US</type>
</taxDetails>
<taxDetails>
<rate>3.68</rate>
<type>XA</type>
</taxDetails>
<taxDetails>
<rate>5.15</rate>
Page 565 of 714
<type>XY</type>
</taxDetails>
<fare>
<pricingMessage>
<description>LAST TKT DTE*05DEC14* - DATE OF ORIGIN</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<qualifier>M</qualifier>
Page 566 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 567 of 714
5.95 Operation: 09.03 Output Option - Negotiated Space Availability Indicator

In case the Negotiated Space availability complies with the query, a flag is set in the Output field of the
Availability Context.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>050812</date>
</timeDetails>
</itinerary>
Page 568 of 714

<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>2020</ref>
</flightProposal>
<flightProposal>
<ref>FI</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
Page 569 of 714
<equipmentType>75T</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0745</ref>
</flightProposal>
Page 570 of 714
<flightProposal>
<ref>AA</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
Page 571 of 714
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>FI</company>
</codeShareDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
Page 572 of 714
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
<description>SUBJ TO CANCELLATION/CHANGE PENALTY</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>A</rbd>
<cabin>W</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>AQO3PLUS</fareBasis>
<contextDetails>
<availabilityCnxType>N</availabilityCnxType>
</contextDetails>
</groupOfFares>
<groupOfFares>
<cabinProduct>
Page 573 of 714
<rbd>A</rbd>
<cabin>W</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>AQO3PLUS</fareBasis>
<contextDetails>
</contextDetails>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
<monetaryDetail>
<amount>0</amount>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
Page 574 of 714
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
<company>AA</company>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
<monetaryDetails>
<amount>0</amount>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
Page 575 of 714
<cabinProduct>
<rbd>H</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>H2</fareBasis>
<contextDetails>
</contextDetails>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 576 of 714
5.96 Operation: 09.04 Output Option - In-Flight Services

The user has the ability to request by input option (IFS) the display of the in-flight services for each flight.
The example bellow illustrates a query with in-flight services option (IFS) and a reply with Wi-Fi on board (18),
Lie Flat Seat (16), Television (5), In-Seat Power Source (12).

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>IFS</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>151114</date>
</timeDetails>
Page 577 of 714
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>7</ref>
</flightProposal>
<flightProposal>
<ref>0120</ref>
</flightProposal>
<flightProposal>
<ref>AF</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
Page 578 of 714
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
<flightCharacteristics>
<inFlightSrv>18</inFlightSrv>
</flightCharacteristics>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
Page 579 of 714
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 580 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 15NOV14</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>M</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>MWKWFR</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
Page 581 of 714
5.97 Operation: 10.01 Ancillary Services option - Request All Fees

This option allows to request all ancillary services fees within one generic service sub-code "A".

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
<carrierId>IB</carrierId>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<feeOption>
Page 582 of 714
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>A</subType>
</feeInfo>
</feeDetails>
</feeOption>

Page 583 of 714
5.98 Operation: 10.02 Ancillary Services option - Global pulled mode

NOTE: this option is not yet available.
This option allows the ancillary services amounts to be taken into account when determining the lowest
recommendations: this is the pulled mode POL option. In the Pushed mode, PUS option, the ancillary services
are displayed but not taken into account in the determination of the lowest recommendations.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
Page 584 of 714
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
<otherSelectionDetails>
<option>POL</option>
</otherSelectionDetails>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>A</subType>
</feeInfo>
</feeDetails>
</feeOption>

Page 585 of 714
5.99 Operation: 10.03 Ancillary Services option - Request a service sub-code

This option allows to request a single ancillary service sub-code.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
<locationId>ALC</locationId>
</departurePoint>
<locationId>VLC</locationId>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 586 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261110</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>AAA</subType>
</feeInfo>
</feeDetails>
</feeOption>

Page 587 of 714
5.100 Operation: 10.04 Ancillary Services option - Inclusion/Exclusion option

This option allows to include or exclude one sub-code. Inclusion is the default mode, and can be omitted.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 588 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261110</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<option>IN</option>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>BBB</subType>
<option>EX</option>
</feeInfo>
</feeDetails>
</feeOption>


Page 589 of 714
5.101 Operation: 10.05 Ancillary Services option - pulled/pushed mode at

sub-code level
This operation allows to specify for each service request if it should be processed in a pushed (informative
mode) or pulled mode (service amount taken into account in the determination of the lowest recommendations).
The default mode is the pushed mode PUS. It can be specified or not.
In the following example, the two first requests for service AAA and BBB are in pulled mode.
Inclusion mode is the default mode. It can be specified or not.
Requests for CCC, DDD, EEE are all equivalent. PUS (default pushed mode) and IN (default inclusion mode)
can be specified or not.
NOTE: the pulled mode option is not yet available.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 590 of 714
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
<otherSelectionDetails>
<option>PUS</option>
</otherSelectionDetails>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<option>IN</option>
<dataInformation>
<indicator>POL</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<dataInformation>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>CCC</subType>
<dataInformation>
<indicator>PUS</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
Page 591 of 714
<feeInfo>
<subType>DDD</subType>
<option>IN</option>
<dataInformation>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>EEE</subType>
</feeInfo>
</feeDetails>
</feeOption>

Page 592 of 714
5.102 Operation: 10.06 Ancillary Services option - Service coverage option

This option allows the process to match a service depending on its coverage applicability.
The service coverage option can be requested at:
Itinerary level (COI option). This is the default mode.
Flight level (COF option).
Bound level (COB option).
Itinerary level or a sub-coverage of the itinerary (CIS option).
Bound level or a sub-coverage of the bound (CIB option).

Each service request can be associated with a specific coverage option as shown below.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
<typeOfUnit>INV</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 593 of 714
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<dataInformation>
<indicator>COF</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
Page 594 of 714
<feeDetails>
<feeInfo>
<dataInformation>
<indicator>COI</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<dataInformation>
<indicator>COB</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>DDD</subType>
<dataInformation>
<indicator>CIS</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>EEE</subType>
<dataInformation>
<indicator>CIB</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
</feeOption>


Page 595 of 714
5.103 Operation: 10.07 Ancillary Services option - coverage option and pulled
mode
This example shows how to combine coverage option and pulled mode option at service level.
NOTE: the pulled mode option is not yet available.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
Page 596 of 714
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<dataInformation>
</dataInformation>
<dataInformation>
</dataInformation>
</feeInfo>
</feeDetails>
</feeOption>

Page 597 of 714
5.104 Operation: 10.08 Ancillary Services option - Request a service group

This example shows how to request an entire service group.
A group contains several sub-groups, which contain several ancillary services themselves.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 598 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>UNK</subType>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
<serviceDescriptionInfo>
<serviceRequirementsInfo>
<serviceClassification>F</serviceClassification>
<serviceGroup>UN</serviceGroup>
</serviceRequirementsInfo>
</serviceDescriptionInfo>
</feeDetails>
</feeOption>
Page 599 of 714

Page 600 of 714
5.105 Operation: 10.09 Ancillary services option - Request a service subgroup

This example shows how to request a service sub-group.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 601 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
<serviceSubGroup>AS</serviceSubGroup>
</feeDetails>
</feeOption>
Page 602 of 714

Page 603 of 714
5.106 Operation: 10.10 Ancillary services option - Request combining service

group, sub-group and sub-code
This request shows how to include UN group, exclude AS sub-group and include CCC sub-code.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 604 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<option>IN</option>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
</feeDetails>
<feeDetails>
Page 605 of 714
<feeInfo>
<option>EX</option>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>2</number>
</itemNumberInfo>
<serviceSubGroup>AS</serviceSubGroup>
</feeDetails>
<feeDetails>
<feeInfo>
<option>IN</option>
</feeInfo>
</feeDetails>
</feeOption>

Page 606 of 714
5.107 Operation: 10.11 Ancillary Services option - Seat characteristic request

This option allows to request a specific service: seat characteristics in service group SA.
Only one seat characteristic by input request will be processed:
All sequences filed with more than one seat characteristic, can't be matched.
If several seat characteristics are present in one input request, all but the first one will be ignored.
Only one seat characteristic is displayed in the output: for a request where no seat characteristic is specified
the last seat characteristic matched will be the one displayed even if there are different seat characteristic on
the segments of the journey.
This display is independent of the price associated to the seat characteristic and the sequence order in the filing.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 607 of 714
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
<serviceClassification>UNK</serviceClassification>
Page 608 of 714
<serviceGroup>SA</serviceGroup>
<seatDetails>
<seatCharacteristics>W</seatCharacteristics>
<seatCharacteristics>E</seatCharacteristics>
</seatDetails>
</feeDetails>
</feeOption>

Page 609 of 714
5.108 Operation: 10.12 Ancillary Services option - Multi Passengers request
In case of a multi passenger request, it is important to note that the monetary information will be returned by
passenger type and not by passenger.
So the data returned in the Passenger Reference Information of the Service Fee are not relevant, only the
Passenger Reference Information for which the service apply is meaningful.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
<traveller>
<ref>3</ref>
</traveller>
<traveller>
<ref>4</ref>
</traveller>
<traveller>
<ref>5</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>MIL</ptc>
<traveller>
<ref>6</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
Page 610 of 714
<segRef>1</segRef>
<departurePoint>
<locationId>PMI</locationId>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<subType>TDA</subType>
<dataInformation>
</dataInformation>
<dataInformation>
</dataInformation>
</feeInfo>
</feeDetails>
</feeOption>

<replyStatus>
<status>
</status>
Page 611 of 714
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0115</ref>
</flightProposal>
<flightProposal>
<ref>IB</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<operatingCarrier>IB</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
Page 612 of 714
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0120</ref>
</flightProposal>
<flightProposal>
<ref>IB</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 613 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<refQualifier>OC</refQualifier>
</segmentFlightRef>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 614 of 714
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
<traveller>
<ref>2</ref>
</traveller>
<traveller>
<ref>3</ref>
</traveller>
<traveller>
<ref>4</ref>
</traveller>
<traveller>
<ref>5</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 615 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 22SEP10</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>N</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>NDU7OW</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
<paxFareProduct>
Page 616 of 714
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
</paxFareDetail>
<paxReference>
<ptc>MIL</ptc>
<traveller>
<ref>6</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>22SEP10</description>
</pricingMessage>
</fare>
<fare>
Page 617 of 714
<pricingMessage>
<description>NOT FARED AT PASSENGER TYPE REQUESTED </description>
<description>5</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>N</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>NDU7OW</fareBasis>
</groupOfFares>
</fareDetails>
</paxFareProduct>
</recommendation>
<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</serviceTypeInfo>
Page 618 of 714
<serviceFeeRefGrp>
<refInfo>
<referencingDetail>
<referencingDetail>
<refQualifier>OCM</refQualifier>
<referencingDetail>
<refQualifier>OCC</refQualifier>
</refInfo>
</serviceFeeRefGrp>
<itemNumberInfo>
<itemNumber>
<number>1</number>
<type>OCC</type>
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<refNum>1</refNum>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
</refInfo>
Page 619 of 714
<serviceFeeInfoGrp>
<itemNumberInfo>
<itemNumber>
<number>1</number>
<type>OCM</type>
</itemNumber>
</itemNumberInfo>
<serviceDetailsGrp>
<refInfo>
<referencingDetail>
</refInfo>
<serviceMatchedInfoGroup>
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<pricingInfo>
<fareDetails>
<passengerTypeQualifier>MIL</passengerTypeQualifier>
</fareDetails>
</pricingInfo>
<amountInfo>
<monetaryDetail>
<typeQualifier>PU</typeQualifier>
</monetaryDetail>
</amountInfo>
</serviceMatchedInfoGroup>
</serviceFeeInfoGrp>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>TDA</subType>
<dataInformation>
</dataInformation>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
Page 620 of 714
<type>SD</type>
</itemNumberInfo>
<serviceAttributesInfo>
<attributeDetails>
<attributeType>SSR</attributeType>
<attributeDescription>IEVG</attributeDescription>
</attributeDetails>
</serviceAttributesInfo>
<serviceNumberOfInstances>1</serviceNumberOfInstances>
<serviceMarketingCarrier>IB</serviceMarketingCarrier>
<serviceGroup>IE</serviceGroup>
<serviceSubGroup>VG</serviceSubGroup>
</serviceFeesGrp>

Page 621 of 714
5.109 Operation: 10.13 Ancillary Services option - Combination of all possible

options
This example shows a complex request with all available options.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>261010</date>
</timeDetails>
</itinerary>
<itinerary>
Page 622 of 714
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>301010</date>
</timeDetails>
</itinerary>
<feeOption>
<feeTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</feeTypeInfo>
<feeDetails>
<feeInfo>
<option>IN</option>
<dataInformation>
</dataInformation>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
Page 623 of 714
</feeDetails>
<feeDetails>
<feeInfo>
<subType>PCC</subType>
<option>EX</option>
</feeInfo>
</feeDetails>
<feeDetails>
<feeInfo>
<option>EX</option>
<dataInformation>
<indicator>COB</indicator>
</dataInformation>
</feeInfo>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
<serviceSubGroup>MR</serviceSubGroup>
</feeDetails>
<feeDetails>
<feeInfo>
<subType>SEA</subType>
<dataInformation>
<indicator>CBS</indicator>
</dataInformation>
</feeInfo>
</feeDetails>
</feeOption>
Page 624 of 714

Page 625 of 714
5.110 Operation: 11.1 - OB fees with connections

This example describes a Master Pricer query including OB fees with two connections.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<flightDetail>
</flightDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201212</date>
Page 626 of 714
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>251212</date>
</timeDetails>
<flightInfo>
<unitNumberDetail>
</unitNumberDetail>
</flightInfo>
</itinerary>

Page 627 of 714
5.111 Operation: 12.0 Rail Option - Prohibit Rail solutions

The aim of this option is to prevent the process from returning rail recommendations. So, any rail solutions
won't be returned in output.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<unitNumberDetail>
<typeOfUnit>NRA</typeOfUnit>
</unitNumberDetail>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 628 of 714
<timeDetails>
<date>131108</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>181108</date>
</timeDetails>
</itinerary>

Page 629 of 714
5.112 Operation: 12.1 Passengers Ref - 1 adult with 1 infant

The description of this operation will be accessed through office profiling.
Example: A 39 year old person travelling with his 10 months old infant.
The infant and the adult share the same seat.
Passenger 1 (adult with infant):

ADT
39 years old with infant of 10 months => no seat
Rail Card Senior
Rail Card Escapade

<passengerInfoGrp>
<passengerReference>
<segmentControlDetails>
<quantity>1</quantity>
</segmentControlDetails>
</passengerReference>
<psgDetailsInfo>
<discountPtc>
<valueQualifier>ADT</valueQualifier>
<value>39</value>
</discountPtc>
<flequentFlyerDetails>
<carrier>FRR</carrier>
<tierDescription>SENIO</tierDescription>
<tierDescription>ESCA</tierDescription>
</flequentFlyerDetails>
</psgDetailsInfo>
<psgDetailsInfo>
<discountPtc>
<valueQualifier>IN</valueQualifier>
<value>0</value>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>
Page 630 of 714
Page 631 of 714
5.113 Operation: 12.2 Passengers Ref - 1 adult with 1 infant and 1 child
Example: A 39 year old person travelling with his 10 months old infant and his 2 year old child.
The child (considered as a passenger) has his own seat.

ADT
39 years old
with infant of 10 months => no seat
Rail Card Senior
Rail Card Escapade
Passenger 2 (child)
CH
2 years old

<passengerInfoGrp>
<psgDetailsInfo>
<discountPtc>
<value>39</value>
</discountPtc>
</psgDetailsInfo>
<psgDetailsInfo>
<discountPtc>
Page 632 of 714
<value>0</value>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>
<passengerInfoGrp>
<psgDetailsInfo>
<discountPtc>
<valueQualifier>CH</valueQualifier>
<value>2</value>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>
Page 633 of 714
5.114 Operation: 12.3 Passengers Ref - 1 adult with 1 infant and 1 child,
Passenger 3 with no age specified
Example: A 39 year old person travelling with his 10 months old infant and his 2 year old child.
The child (considered as a passenger) has his own seat.
The military has a rail card Escapade with no age specified (will be considered as an adult).

ADT
39 years old
with infant of 10 months => no seat
Rail Card Senior
Rail Card Escapade
Passenger 2 (child)
CH
2 years old
Passenger 3 (Military)
MIL
No age specified
Rail Card Escapade

<passengerInfoGrp>
<psgDetailsInfo>
<discountPtc>
<value>39</value>
</discountPtc>
Page 634 of 714
</psgDetailsInfo>
<psgDetailsInfo>
<discountPtc>
<value>1</value>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>
<passengerInfoGrp>
<psgDetailsInfo>
<discountPtc>
<valueQualifier>CH</valueQualifier>
<value>2</value>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>
<passengerInfoGrp>
<psgDetailsInfo>
<discountPtc>
<valueQualifier>MIL</valueQualifier>
</discountPtc>
</psgDetailsInfo>
</passengerInfoGrp>

Page 635 of 714
5.115 Operation: 13.1 Airline Fare Family name and description

The user has the ability to request fare family information in output. This is triggered by FS Parameter at Office
ID level and by an input option (FFI) with 3 values 1, 2 or 3.
When option 1 is requested, only Fare Family name at Fare component level are returned.
When option 2 is requested, Fare Family name at Fare component level and resulting Fare Family
name at requested segment level are returned.
When option 3 is requested, Fare Family name at Fare component level and resulting Fare Family
name at requested segment level with the list of services are returned.
If a fare component matches one or several fare families, the most restrictive fare family is returned.
If the fare component doesnt match any fare family, no fare family is returned for this fare component.
The resulting fare family is returned only if the requested segment is fully covered by fares with the same
controlling carrier and that match at least one fare family.
In case several fare families involved in the requested segment, the most restrictive one (highest ranking /
lowest tier) is returned except in case several FF have the same ranking.
In that case, the resulting fare family is the one of the longest fare component (number of miles).
By default, Master pricer will return 7 services attached to the resulting fare family, and will give priority on: BagSeat Meal- Travel Services. Number of services can vary from 1 to 20 , this is triggered via FS parameter.
In this example, the user requests Fare Family name at Fare component level and resulting Fare Family name
and description at requested segment level.
The reply illustrates 1 recommendation with 2 requested segments and 3 fare components. First requested
segment is fully covered by 1 fare family. Second requested segment is covered by 2 fare families.
Fare family name at fare component level (fareFamiliesRef)
Requested segment Fare component
Fare Family
reference
Fare Family name
Fare Family carrier
NCE-NYC
NCE-NYC
FFAM1
6X
NYC-LON-NCE
NYC-LON
FFAM2
6X
LON-NCE
FFAM3
6X
Resulting Fare family name at requested segment level (fareFamilyRef)
Page 636 of 714
Requested segment
Fare Family reference
Fare Family name
Fare Family carrier
NCE-NYC
FFAM1
6X
NYC-LON-NCE
FFAM2
6X
Fare family description (familyInformation) and list of services (serviceFeesGrp)

Fare Family reference
Fare family Name
FFAM1
FFAM2
Fare Family carrier
6X
6X
Short description
FARE FAMILY 1
FARE FAMILY 2
Included
Included
Included
At charge
Included
Not offered
List of services
Service reference
Sub code
0AT
Group
ML - Meal/Beverage
Classification
F - Flight related
Commercial name
SNACK
Service reference
Sub code
SS1
Group
SA- Seat
Classification
F - Flight related
Commercial name
SEAT SELECTION
Service reference
Sub code
0C3
Group
BG - Baggage
Classification
F - Flight related
Commercial name
UPTO50LB 23KG
BAGGAGE
Service reference
Sub code
NRF
Group
TS -Travel Services
Classification
F - Flight related
Commercial name
NOT REFUNDABLE
Included
Page 637 of 714

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 638 of 714
<timeDetails>
<date>101114</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>201114</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<familyInformation>
<fareFamilyname>FFAM1</fareFamilyname>
<description>FARE FAMILY 1</description>
<carrier>6X</carrier>
<services>
Page 639 of 714
</services>
<services>
</services>
<services>
</services>
<services>
</services>
<familyInformation>
<description>FARE FAMILY 2</description>
<services>
</services>
<services>
<status>CHA</status>
</services>
<services>
<status>NOF</status>
</services>
<familyInformation>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
Page 640 of 714
<flightProposal>
<ref>0915</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
Page 641 of 714
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>1150</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
Page 642 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
Page 643 of 714
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
Page 644 of 714
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>FB1</fareBasis>
Page 645 of 714
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Y</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>B</rbd>
<cabin>M</cabin>
Page 646 of 714
</cabinProduct>
<fareProductDetail>
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>OC</type>
</serviceTypeInfo>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>0AT</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
<type>SD</type>
</itemNumberInfo>
Page 647 of 714
<serviceGroup>ML</serviceGroup>
<commercialName>
<freeText>SNACK</freeText>
</commercialName>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>SS1</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>2</number>
<type>SD</type>
</itemNumberInfo>
<serviceGroup>SA</serviceGroup>
<commercialName>
<freeText>SEAT SELECTION</freeText>
</commercialName>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>0C3</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
Page 648 of 714
<number>3</number>
<type>SD</type>
</itemNumberInfo>
<serviceGroup>BG</serviceGroup>
<commercialName>
<freeText>UPTO50LB 23KG BAGGAGE</freeText>
</commercialName>
<serviceDetailsGrp>
<serviceOptionInfo>
<subType>NRF</subType>
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>4</number>
<type>SD</type>
</itemNumberInfo>
<serviceGroup>TS</serviceGroup>
<commercialName>
<freeText>NOT REFUNDABLE</freeText>
</commercialName>
</serviceFeesGrp>
Page 649 of 714

informationinformationproduct
faredescriptionmessage
informationoptionmessage
Page 650 of 714
5.116 Operation: 13.2 Airline Fare Family name and description
In this example, the user requests Fare Family name at Fare component level and resulting Fare Family name
at requested segment level.
In case all or some flights within a proposed segment are not matching any airline fare family, no resulting
airline fare family information is returned for the whole proposed segment.
Recommendation
PAR-HEL
HEL-PAR
No resulting fare family
Resulting fare family BASIC
Resulting fare family CLASSIC

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<feeIdDescription>
<feeId>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
Page 651 of 714
<departurePoint>
</departurePoint>
<locationId>HEL</locationId>
<timeDetails>
<date>101014</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>151014</date>
</timeDetails>
</itinerary>

<conversionRate>
</conversionRate>
<familyInformation>
Page 652 of 714
<fareFamilyname>BASIC</fareFamilyname>
<familyInformation>
<fareFamilyname>CLASSIC</fareFamilyname>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0250</ref>
</flightProposal>
<flightProposal>
<ref>7X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
<terminal>2D</terminal>
</location>
<location>
</location>
<companyId>
</companyId>
Page 653 of 714
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0250</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
Page 654 of 714
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>0255</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 655 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0305</ref>
</flightProposal>
<flightProposal>
<ref>7X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
Page 656 of 714
<equipmentType>E90</equipmentType>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0305</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
Page 657 of 714
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>3</ref>
</flightProposal>
<flightProposal>
<ref>0305</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 658 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
Page 659 of 714
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 31JUL14 - SEE ADV PURCHASE</description>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
Page 660 of 714
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>V</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
Page 661 of 714
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
Page 662 of 714
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
Page 663 of 714
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Z</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 664 of 714
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>3</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
Page 665 of 714
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
Page 666 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Z</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
Page 667 of 714
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>4</number>
</itemNumberId>
</itemNumber>
<fareFamilyRef>
<referencingDetail>
<referencingDetail>
</fareFamilyRef>
Page 668 of 714
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
Page 669 of 714
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Z</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 670 of 714
<fareFamiliesRef>
<referencingDetail>
</fareFamiliesRef>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>

Page 671 of 714
5.117 Operation: 14.0 Free Baggage Allowance

This feature of Master Pricer provides the information about the free baggage allowed for each
recommendation.
The functionality is triggered by a setting at OID level or by input option (FBA) with 2 values:
1: allows to return FBA
0: no FBA is returned
The input option overrides the OID setting.
In the example below, the Free Baggage Allowance is requested by input option.
In the reply, we have 2 recommendations with different baggage allowances:
Request segment 1: BCN-MAD
Request segment 2: MAD-VLC

The free baggage allowance is returned with the following information:
First recommendation with same
FBA for the whole itinerary
Second recommendation with

different FBA
Free baggage allowed
Applicability
BCN-MAD 23 Kg
23 kg on Requested segment 1
Leg 1
MAD-IBZ-VLC 23 Kg
BCN-MAD1PC
MAD- VLC 2 PC
23 kg on Requested segment 2
Leg 1 and 2
1P on Requested segment 1 Leg
1
2P on Requested segment 2 Leg
1
Baggage allowance is detailed at 3 levels:
Free Baggage Allowance information (number of pieces or number of kilos)
Baggage allowance coverage (Passenger type reference, flight coverage, baggage allowance
reference)
Baggage allowance coverage reference at recommendation level

Free Baggage Allowance is detailed in freeBagAllowanceGrp:
FBA #1
23 Kilos
FBA #2
1 Piece
FBA #3
2 Pieces
Baggage coverage is detailed in serviceCoverageInfoGrp:
Baggage coverage #1
Passenger type reference Flight coverage
Reference to FBA
FBA #1
Requested segment 1
Leg 1
Requested segment 2
Leg 1 and 2
Page 672 of 714
Baggage coverage #2
Requested segment 1
Leg 1
Requested segment 2
Leg 1
FBA #2
FBA #3
Recommendation details:
Reference to Baggage coverage
Recommendation #1
Baggage coverage #1
Recommendation #2
Baggage coverage #2

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo/>
<feeIdDescription>
<feeId>
<feeType>FBA</feeType>
</feeId>
</feeIdDescription>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
Page 673 of 714
<departurePoint>
</departurePoint>
<timeDetails>
<date>101113</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>171113</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
Page 674 of 714
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0125</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
Page 675 of 714
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0125</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 676 of 714
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0500</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
Page 677 of 714
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
<groupOfFlights>
<flightProposal>
<ref>2</ref>
</flightProposal>
<flightProposal>
<ref>0055</ref>
</flightProposal>
<flightProposal>
<ref>6X</ref>
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
Page 678 of 714
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
Page 679 of 714
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
Page 680 of 714
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
<description>LAST TKT DTE 05OCT13</description>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>ODSV</fareBasis>
Page 681 of 714
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>PD</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>PD30</fareBasis>
</groupOfFares>
<majCabin>
Page 682 of 714
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<recommendation>
<itemNumber>
<itemNumberId>
<number>2</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
<referencingDetail>
</segmentFlightRef>
Page 683 of 714
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
Page 684 of 714
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>S</rbd>
<cabin>M</cabin>
Page 685 of 714
</cabinProduct>
<fareProductDetail>
<fareBasis>SDA8OW</fareBasis>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>FBA</type>
</serviceTypeInfo>
<itemNumberInfo>
<itemNumber>
<number>1</number>
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<refNum>1</refNum>
<lastItemsDetails>
</lastItemsDetails>
Page 686 of 714
<refNum>2</refNum>
<lastItemsDetails>
</lastItemsDetails>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
</refInfo>
<itemNumberInfo>
<itemNumber>
<number>2</number>
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<refNum>1</refNum>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
</refInfo>
<serviceCovInfoGrp>
Page 687 of 714
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<refNum>2</refNum>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
</refInfo>
<baggageDetails>
<quantityCode>W</quantityCode>
<unitQualifier>K</unitQualifier>
</baggageDetails>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
<baggageDetails>
</baggageDetails>
<itemNumberInfo>
<itemNumberDetails>
<number>2</number>
Page 688 of 714
</itemNumberInfo>
<baggageDetails>
</baggageDetails>
<itemNumberInfo>
<itemNumberDetails>
<number>3</number>
</itemNumberInfo>
</serviceFeesGrp>
Page 689 of 714
5.118 Operation: 14.1 Free Baggage Allowance with multiple passenger

types
In case of different passenger types are requested in the query of Master Pricer, the free baggage allowance
always provide the information of the ADTpassenger typeif present in the query. If no ADT passenger type is
requested, the free baggage allowance is provided for the first passenger type.
In this example, we consider 2 PTCs: 1 ADT and 1 CH and one recommendation:
Request segment 1: BCN-MAD
Request segment 2: MAD-VLC

Passenger Type
Recommendation with
ADT
multiple passenger types
CH
Free baggage allowed
Applicability
BCN-MAD 1P
1 pieceon Requested
segment 1 Leg 1 and
1 pice on Requested
segment 2 Leg 1 and 2
MAD-IBZ-VLC 1P
Baggage allowance is detailed at 3 levels:
Free Baggage Allowance information (number of pieces or number of kilos)
Baggage allowance coverage (Passenger type references, flight coverage, baggage allowance
reference )
Baggage allowance coverage reference at recommendation level

Baggage Allowance is detailed in freeBagAllowanceGrp:
FBA #1
1 piece
Baggage coverage is detailed in serviceCoverageInfoGrp:
Baggage coverage #1
Passenger type reference Flight coverage
Reference to FBA
1 (ADT)
FBA #1
Requested segment 1
Leg 1
Requested segment 2
Leg 1 and 2
Recommendation details:
Reference to Baggage coverage
Recommendation #1
Baggage coverage #1

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
Page 690 of 714
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<travelFlightInfo>
<companyIdentity>
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>101113</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
Page 691 of 714
</departurePoint>
<timeDetails>
<date>171113</date>
</timeDetails>
</itinerary>

<replyStatus>
<status>
</status>
</replyStatus>
<conversionRate>
</conversionRate>
<flightIndex>
<segRef>1</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0125</ref>
</flightProposal>
<flightProposal>
<ref>IB</ref>
</flightProposal>
<flightDetails>
Page 692 of 714
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<flightIndex>
<segRef>2</segRef>
<groupOfFlights>
<flightProposal>
<ref>1</ref>
</flightProposal>
<flightProposal>
<ref>0500</ref>
</flightProposal>
<flightProposal>
<ref>IB</ref>
Page 693 of 714
</flightProposal>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
<operatingCarrier>YW</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
<flightDetails>
<flightInformation>
<productDateTime>
</productDateTime>
<location>
</location>
<location>
</location>
<companyId>
Page 694 of 714
<operatingCarrier>YW</operatingCarrier>
</companyId>
<productDetail>
</productDetail>
<addProductDetail>
</addProductDetail>
</flightDetails>
</groupOfFlights>
</flightIndex>
<recommendation>
<itemNumber>
<itemNumberId>
<number>1</number>
</itemNumberId>
</itemNumber>
<recPriceInfo>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
<monetaryDetail>
</monetaryDetail>
</recPriceInfo>
<segmentFlightRef>
<referencingDetail>
<referencingDetail>
Page 695 of 714
<referencingDetail>
</segmentFlightRef>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
Page 696 of 714
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
Page 697 of 714
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<fareBasis>QD</fareBasis>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
<paxFareProduct>
<paxFareDetail>
<codeShareDetails>
Page 698 of 714
</codeShareDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<monetaryDetails>
</monetaryDetails>
<pricingTicketing>
</pricingTicketing>
</paxFareDetail>
<paxReference>
<ptc>CH</ptc>
<traveller>
<ref>2</ref>
</traveller>
</paxReference>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
</pricingMessage>
</fare>
<fare>
<pricingMessage>
Page 699 of 714
</pricingMessage>
</fare>
<fareDetails>
<segmentRef>
<segRef>1</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>O</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
<fareDetails>
<segmentRef>
<segRef>2</segRef>
</segmentRef>
<groupOfFares>
<cabinProduct>
<rbd>Q</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
Page 700 of 714
<fareBasis>QD</fareBasis>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<groupOfFares>
<cabinProduct>
<rbd>P</rbd>
<cabin>M</cabin>
</cabinProduct>
<fareProductDetail>
<ticketInfos>
</ticketInfos>
</groupOfFares>
<majCabin>
</majCabin>
</fareDetails>
</paxFareProduct>
</recommendation>
<serviceFeesGrp>
<serviceTypeInfo>
<carrierFeeDetails>
<type>FBA</type>
Page 701 of 714
</serviceTypeInfo>
<itemNumberInfo>
<itemNumber>
<number>1</number>
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
</travellerDetails>
</paxRefInfo>
<refNum>1</refNum>
<lastItemsDetails>
</lastItemsDetails>
<refNum>2</refNum>
<lastItemsDetails>
</lastItemsDetails>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
</refInfo>
<baggageDetails>
Page 702 of 714
</baggageDetails>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number>
</itemNumberInfo>
</serviceFeesGrp>
Page 703 of 714
5.119 Operation: 14.2 Baggage

With the baggage option, the information on the two cheapest baggage* is returned per recommendation (if
the data is filled). Those baggage could be free (from free baggage allowance filling and returned in FBA fields)
or at charge (from AAS filling and returned in AAS fields).
AAS baggage are processed from ATPCO source, from service classification P/C/F as in the catalogue/pricing
process (only if the Airline has signed an agreement with Amadeus for Ancillary Services distribution).
Service classification P: Prepaid baggage that can be purchased prior to passenger airport check-in
Service classification C: Baggage charges that apply at airport check-in
Service classification F:Other type of baggage
If the airline do not file baggage in piece concept, the number of KG allowed will be returned plus the price
for one additional KG.
Recommendation 1
Recommendation 2
Recommendation 3
Recommendation 4
Airline in piece concept
Airline in weight concept
FBA = 0
FBA = 1
FBA = 2
FBA >= 0
AAS bag occurrence 1 & AAS bag occurrence 1

No AAS bag returned
Pricer per KG returned
2 returned*
returned
FBA & AAS type P/C processed in Master Pricer arecompliant with IATA resolution 302 & USDOTthat regulate
the calculation of baggage (quantity and fees).
* Important: only 1 occurrence of AAS baggage will be displayed until the activation of occurrence process in
catalogue in order to ensure the consistency between shopping & catalogue.
Passenger Type Code process:The AAS is only calculated for the adult passenger type (if any).
For example, if we have an adult, a child and an infant, the AAS returned is the one applicable to the adult.
In case no adult passenger type is requested, the AAS returned is the one of the first passenger type of the
query.
Free Baggage information will be automatically processed when baggage option is requested (even if FBA is
not activated). C.f. Free Baggage Allowance.
Each recommendation could be cut into several BTU (portion of travel on which one given carrier defines the
unique applicable Baggage allowance and charges policy). In that case, FBA and AAS information will be
returned per BTU. The price of the baggage for the entire itinerary can be calculated by adding the price of
the baggage on each BTU.
Example of baggage information returned on a recommendation:
BTU 1
BTU 2
BTU 3
FBA = 0
FBA = 1
FBA = 1
Page 704 of 714
AAS bag occurrence 1 is 10 euros AAS bag occurrence 1 is 5 euros

& occurrence 2 is 12 euros
AAS bag occurrence 1 is 7 euros
The price for the first baggage on the entire itinerary is 10 euros (one baggage already included on BTU 2 & 3).
The price for a second baggage is: 12 + 5 + 7 = 24 euros.
After the flight booking and pricing, it is recommended to send an AAS catalogue/pricing query to retrieve and
book/price Ancillary Services. This catalogue query should be limited to the portions of the itinerary where the
at-charge baggage is necessary.
Example of itinerary Paris-London-Mexico:
Paris - London
London Mexico
FBA = 0
FBA = 1
AAS bag occurrence 1 & 2 returned
AAS bag occurrence 1 returned
If the end user wants to travel with one baggage, an AAS baggage has to be bought on Paris-London part only
(as a baggage is already included on the fare for London-Mexico).
Baggage activation
This option is triggered by a setting at OID level and by the input option BAG in Master Picer query:
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
Baggage information returned in the output
For each AAS baggage, the following information is returned (if filled):
Price / RFIC / RFISC / SSR code / Booking Method / Service classification (P, C or F) / Commercial Name /
Carrier / Group / Subgroup / Description 1 & 2
RFIC/RFISC:Reason For Issuance Code/ Reason For Issuance Sub Code

SSR code:Special Service Request
The service classification P correspond to prepaid baggage, which mean that the returned AAS price is only
available until a certain time before the check-in. An AAS will be returned in type P only if the conditions are
still applicable. In service classification C, the baggage price will be the same at check-in time.
Page 705 of 714
Recommendation
<referencingDetail>
<refNumber>1</refNumber><- AAS reference attached to the recommendation
AAS Reference
<serviceFeeRefGrp>
<refInfo>
<referencingDetail>
<refQualifier>OC</refQualifier> <- AAS reference attached to the recommendation
<referencingDetail>
<refQualifier>OCM</refQualifier> <- AAS amount reference
<referencingDetail>
<refQualifier>OCC</refQualifier><- AAS coverage Reference
</refInfo>
</serviceFeeRefGrp>
Coverage
<itemNumberInfo>
<itemNumber>
<number>2</number> <- AAS coverage reference
</itemNumber>
</itemNumberInfo>
<serviceCovInfoGrp>
<paxRefInfo>
<travellerDetails>
Page 706 of 714
<referenceNumber>1</referenceNumber> <- Passenger reference

</travellerDetails>
</paxRefInfo>
<refNum>1</refNum> <- Requested segment number
<lastItemsDetails>
<refOfLeg>1</refOfLeg><- Leg applicability: 1,2,3
</lastItemsDetails>
<lastItemsDetails>
</lastItemsDetails>
<lastItemsDetails>
</lastItemsDetails>
<refInfo>
<referencingDetail>
<refQualifier>F</refQualifier> <- AAS baggage reference
</refInfo>
Price
<serviceMatchedInfoGroup>
<paxRefInfo>
<travellerDetails>
<referenceNumber>1</referenceNumber><- AAS amount reference
</travellerDetails>
</paxRefInfo>
<pricingInfo>
<fareDetails>
Page 707 of 714
<passengerTypeQualifier>ADT</passengerTypeQualifier><- PTC processed

</fareDetails>
</pricingInfo>
<amountInfo>
<monetaryDetail>
<amountType>PU1</amountType><- AAS Occurrence 1
<amount>10.00</amount><- AAS price
</monetaryDetail>
</amountInfo>
<amountInfo>
<monetaryDetail>
<amountType>PU2</amountType><- AAS Occurrence 2
<amount>12.00</amount><- AAS price
</monetaryDetail>
</amountInfo>
</serviceMatchedInfoGroup>
Description
<feeDescriptionGrp>
<itemNumberInfo>
<itemNumberDetails>
<number>1</number><- AAS baggage reference
<type>SD</type>
</itemNumberInfo>
<serviceAttributesInfo>
<attributeDetails>
<attributeType>RFIC</attributeType><- RFIC
<attributeDescription>C</attributeDescription>
</attributeDetails>
<attributeDetails>
<attributeType>BKM</attributeType><- Booking method
</attributeDetails>
</serviceAttributesInfo>
Page 708 of 714
<serviceClassification>P</serviceClassification><- Service classification
<serviceNumberOfInstances>1</serviceNumberOfInstances>
<serviceMarketingCarrier>BE</serviceMarketingCarrier> <- Service carrier
<serviceGroup>BG</serviceGroup><- Service group
<serviceFreeText>B3</serviceFreeText><- Service description
<commercialName>
<freeText>PREPAID MERCHO</freeText><- Commercial Name
</commercialName>

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<travelFlightInfo>
<companyIdentity>
Page 709 of 714
</companyIdentity>
</travelFlightInfo>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>101113</date>
</timeDetails>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>171113</date>
</timeDetails>
</itinerary>

Page 710 of 714
Page 711 of 714
5.120 Operation: 15.1 Optional Data Profile

The user has the ability to request some specific data profiles at query level via input option.
When optional data profiles are specified in input, they override the standard data profile.
Up to twenty optional data profiles can be requested simultaneously.
The query bellow describes a search with "OPT MPLITE" Optional Data Profile specified.

<numberOfUnit>
<unitNumberDetail>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
</pricingTicketing>
</pricingTickInfo>
<feeIdDescription>
<feeId>
<feeType>OPTDP</feeType>
<feeIdNumber>OPT MPLITE</feeIdNumber>
</feeId>
</feeIdDescription>
</fareOptions>
<itinerary>
<segRef>1</segRef>
<departurePoint>
</departurePoint>
Page 712 of 714
<timeDetails>
<date>190215</date>
<time>0000</time>
</timeDetails>
<flightInfo/>
</itinerary>
<itinerary>
<segRef>2</segRef>
<departurePoint>
</departurePoint>
<timeDetails>
<date>050315</date>
<time>0000</time>
</timeDetails>
<flightInfo/>
</itinerary>

If the optional data profile requested is not attached to the office ID, the query is rejected with the following
error message:
"OPTIONAL DATA PROFILE NOT AUTHORISED"
Page 713 of 714
If two optional data profiles overriding the same FS Parameters are requested, the query is rejected with the
following error message:
"CONFLICTING DATA PROFILES REQUESTED"
Page 714 of 714

UG WBS Fare MasterPricerTravelBoardSearch 16.1

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

UG WBS Fare MasterPricerTravelBoardSearch 16.1

Încărcat de

Drepturi de autor:

Formate disponibile

Web Services User's Guide

3.2 Reply Sub Structure: Free Baggage Allowance 2 - serviceCoverageInfoGrp..... 71

3.3 Reply Sub Structure: Free Baggage Allowance 3 - segmentFlightRef..................72

5.2 Operation: 02.01 Flight Option - Airline/Alliance (Include/Exclude).......................87

5.3 Operation: 02.02 Flight Option - Flight Category.................................................. 91

5.4 Operation: 02.03 Flight Option - Connection Point............................................... 94

5.5 Operation: 02.04 Flight Option - Multicity............................................................. 98

5.6 Operation: 02.05 Flight Option - Origin Destination Area................................... 103

5.7 Operation: 02.06 Flight Option - No Slice and Dice............................................108

5.8 Operation: 02.07 Flight Option - Disable Biased Preference.............................. 110

5.11 Operation: 02.09 Flight Option - Ignore Availability.......................................... 128

5.12 Operation: 02.10 Flight Option - Number of Connections................................. 130

5.15 Operation: 02.13 Flight option - Interline.......................................................... 136

5.16 Operation: 02.14 Flight option - Maximum EFT................................................ 138

5.18 Operation: 02.16 Flight option - Total Maximum layover.................................. 142

5.20 Operation: 02.18 Flight option - IR: Radius/multicity at requested segment

5.25.1 Query Structure....................................................................................................................... 174

5.29 Operation: 02.28 Flight Option - More Overnights............................................ 189

5.30 Operation: 02.29 Flight Option - Search with Point of Commencement............191

5.31 Operation: 02.30 Flight Option - Search with CLID...........................................193

5.32 Operation: 02.31 Flight Option - DK number (customer identification)..............201

5.32.3 Possible Errors........................................................................................................................ 202

5.33 Operation: 02.32 Flight Option - Progressive legs............................................ 203

5.34 Operation: 03.1 Time Option - Time of Departure/Arrival................................. 206

5.35 Operation: 03.2 Time Option - Time Window................................................... 209

5.36 Operation: 03.3 Time Option - Range Of Dates............................................... 213

5.37 Operation: 03.4 Time Option - Time at destination........................................... 216

5.38 Operation: 04.01 Fare Option - Currency Conversion...................................... 218

5.40 Operation: 04.03 Fare Option - Price To Beat.................................................. 224

5.40.3 Possible Errors........................................................................................................................ 225

5.41 Operation: 04.04 Fare Option - Split / No Split PNR.........................................227

5.42 Operation: 04.05 Fare Option - Type of Ticket (Electronic/Paper Ticket)..........230

5.43 Operation: 04.06 Fare Option - Unifare............................................................ 233

5.44 Operation: 04.07 Fare Option - Expanded Parameter...................................... 236

5.45 Operation: 04.08 Fare Option - My Search - Fare Families..............................239

5.48.3 Possible Errors........................................................................................................................ 266

5.50 Operation: 04.13 Fare Option - Price only PTC................................................269

5.51 Operation: 04.14 Fare Option - My Search - Distribution ratio of recommendations

5.53 Operation: 04.16 Fare Option - My Search - Distribution ratio of recommendations

5.54 Operation: 04.17 Fare Option - My Search - Distribution ratio of recommendations

5.57 Operation: 04.20 Fare Option - Multi-Ticket......................................................293

5.58 Operation: 04.22 Fare Option - Ticketing date................................................. 316

5.59 Operation: 04.23 Fare Option - Solution Family............................................... 318

5.60 Operation: 04.24 Fare Option - Disable Negotiated Space...............................332

5.61 Operation: 04.25 Fare Option - Open Return................................................... 334

5.62 Operation: 04.26 Fare Option - Alternate Price................................................ 354

5.63 Operation: 04.27 Fare Option - Search by FBA................................................372

5.63.3 Possible Errors........................................................................................................................ 374

5.64 Operation: 05.1 Cabin Option - Mandatory Cabin.............................................375

5.65 Operation: 05.2 Cabin Option - Recommended Cabin..................................... 378

5.66 Operation: 05.3 Cabin Option - Major Cabin.................................................... 380

5.67 Operation: 06.1 Fee Option - Pricing Scheme Reference.................................383

5.68 Operation: 06.2 Fee Option - Form of Payment............................................... 394

5.69 Operation: 06.3 Fee Option - Sorting with/without Fees................................... 397

5.71.3 Possible Errors........................................................................................................................ 404

5.72 Operation: 06.6 Fee Option - Estimated FOP fees........................................... 405

5.73 Operation: 07.1 Distribution Option - Airline Distribution: ADI...........................412

5.75 Operation: 07.3 Distribution option - Direct Distribution DDI.............................416

5.76 Operation: 07.4 Distribution option - Not DDI: Deactivation of Direct

5.77 Operation: 07.5 Distribution option - Deactivation of ADI distribution................420

5.78 Operation: 07.6 Distribution option - Mono-Main Carrier Distribution................422

5.79.2 Reply Structure........................................................................................................................ 425

5.80 Operation: 07.8 Distribution Option - Non-Stop Preferred................................ 427

5.81 Operation: 08.01 Output Option - Empty Cells Clarification..............................429