ug wbs fare masterpricertravelboardsearch 16.1

8/20/2019 UG WBS Fare MasterPricerTravelBoardSearch 16.1

http://slidepdf.com/reader/full/ug-wbs-fare-masterpricertravelboardsearch-161 1/714

Amadeus SAS485, Route du Pin Montard

BP 6906902 Sophia-Antipolis Cedex

Web Services User's Guide

Fare_MasterPricerTravelBoardSearch16.1



Table of Contents

i

Table of ContentsPreface................................................................................................................................ 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...................................................................................................................... 201.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............................................................................................................744.1 Error Reply............................................................................................................ 78

5 Operations....................................................................................................................79

5.1 Operation: 01 - Search With Mandatory Elements............................................... 79

5.1.1 Quer y Structure........................................................................................................................... 82

5.1.2 Reply Structure............................................................................................................................ 83

5.1.3 Possible Errors............................................................................................................................ 83



Table of Contents

ii

5.2 Operation: 02.01 Flight Option - Airline/Alliance (Include/Exclude).......................875.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............................................... 945.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



Table of Contents

iii

5.10 Operation: 02.082 Flight Option - Exclude Ticketless Access Carriers.............1265.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.................................1305.12.1 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y Structure....................................................................................................................... 140

5.17.2 Reply Structure........................................................................................................................ 141

5.17.3 Possible Errors........................................................................................................................ 141



Table of Contents

iv

5.18 Operation: 02.16 Flight option - Total Maximum layover .................................. 1425.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 segmentlevel................................................................................................................................... 146

5.20.1 Quer y 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 Quer y 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 groundtime at last connecting point............................................................................................ 170

5.23.1 Quer y 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 Quer y 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



Table of Contents

v

5.25.1 Query Structure....................................................................................................................... 1745.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 technicalstop).................................................................................................................................. 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 technicalstops)....................................................................................................... ..........................183

5.28.1 Quer y Structure....................................................................................................................... 183

5.28.2 Reply Structure........................................................................................................................ 188

5.28.3 Possible Errors........................................................................................................................ 188

5.29 Oper ation: 02.28 Flight Option - More Overnights............................................ 189

5.29.1 Quer y Structure....................................................................................................................... 189

5.29.2 Reply Structure........................................................................................................................ 190

5.29.3 Possible Errors........................................................................................................................ 190

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

5.30.1 Quer y 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 Quer y Structure....................................................................................................................... 201

5.32.2 Reply Structure........................................................................................................................ 202



Table of Contents

vi

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 Oper ation: 03.2 Time Option - Time Window................................................... 209

5.35.1 Quer y Structure....................................................................................................................... 210

5.35.2 Reply Structure........................................................................................................................ 211

5.35.3 Possible Errors........................................................................................................................ 212

5.36 Oper ation: 03.3 Time Option - Range Of Dates............................................... 213

5.36.1 Quer y Structure....................................................................................................................... 214

5.36.2 Reply Structure........................................................................................................................ 215

5.36.3 Possible Errors........................................................................................................................ 215

5.37 Oper ation: 03.4 Time Option - Time at destination...........................................216

5.37.1 Quer y Structure....................................................................................................................... 216

5.37.2 Reply Structure........................................................................................................................ 217

5.37.3 Possible Errors........................................................................................................................ 217

5.38 Oper ation: 04.01 Fare Option - Currency Conversion...................................... 218

5.38.1 Quer y Structure....................................................................................................................... 218

5.38.2 Reply Structure........................................................................................................................ 219

5.38.3 Possible Errors........................................................................................................................ 219

5.39 Oper ation: 04.02 Fare Option - Selling Ticketing Cities Override..................... 221

5.39.1 Quer y Structure....................................................................................................................... 221

5.39.2 Reply Structure........................................................................................................................ 222

5.39.3 Possible Errors........................................................................................................................ 223

5.40 Oper ation: 04.03 Fare Option - Price To Beat..................................................224

5.40.1 Quer y Structure....................................................................................................................... 224

5.40.2 Reply Structure........................................................................................................................ 225



Table of Contents

vii

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 Oper ation: 04.06 Fare Option - Unifare............................................................ 233

5.43.1 Quer y Structure....................................................................................................................... 234

5.43.2 Reply Structure........................................................................................................................ 235

5.43.3 Possible Errors........................................................................................................................ 235

5.44 Oper ation: 04.07 Fare Option - Expanded Parameter ...................................... 236

5.44.1 Quer y Structure....................................................................................................................... 236

5.44.2 Reply Structure........................................................................................................................ 237

5.44.3 Possible Errors........................................................................................................................ 237

5.45 Oper ation: 04.08 Fare Option - My Search - Fare Families..............................2 39

5.45.1 Quer y Structure....................................................................................................................... 242

5.45.2 Reply Structure........................................................................................................................ 247

5.45.3 Possible Errors........................................................................................................................ 247

5.46 Oper ation: 04.09 Fare Option - Multi Office IDs - Default Distribution...............249

5.46.1 Quer y Structure....................................................................................................................... 250

5.46.2 Reply Structure........................................................................................................................ 251

5.46.3 Possible Errors........................................................................................................................ 257

5.47 Oper ation: 04.10 Fare Option - Multi Office IDs - Even Distribution..................260

5.47.1 Quer y Structure....................................................................................................................... 260

5.47.2 Reply Structure........................................................................................................................ 262

5.47.3 Possible Errors........................................................................................................................ 262

5.48 Oper ation: 04.11 Fare Option - Multi Office IDs - Weighted Distribution...........263

5.48.1 Quer y Structure....................................................................................................................... 263

5.48.2 Reply Structure........................................................................................................................ 266



Table of Contents

viii

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 recommendationsper Fare Family................................................................................................................ 271

5.51.1 Quer y 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 requestedsegment level....................................................................................................................275

5.52.1 Quer y Structure....................................................................................................................... 275

5.52.2 Reply Structure........................................................................................................................ 277

5.52.3 Possible Errors........................................................................................................................ 277

5.53 Operation: 04.16 Fare Option - My Search - Distribution ratio of recommendationsper Fare Family at requested segment Level.................................................................. 279

5.53.1 Quer y Structure....................................................................................................................... 279

5.53.2 Reply Structure........................................................................................................................ 283

5.53.3 Possible Errors........................................................................................................................ 283

5.54 Operation: 04.17 Fare Option - My Search - Distribution ratio of recommendationsper Fare Family at requested segment level (Usage at itinerary level)............................285

5.54.1 Quer y 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



Table of Contents

ix

5.56 Operation: 04.19 Fare Option - Currency for Fare Selection with CurrencyConversion 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 Oper ation: 04.22 Fare Option - Ticketing date................................................. 316

5.58.1 Quer y Structure....................................................................................................................... 316

5.58.2 Reply Structure........................................................................................................................ 317

5.58.3 Possible Errors........................................................................................................................ 317

5.59 Oper ation: 04.23 Fare Option - Solution Family............................................... 318

5.59.1 Quer y Structure....................................................................................................................... 318

5.59.2 Reply Structure........................................................................................................................ 319

5.59.3 Possible Errors........................................................................................................................ 331

5.60 Oper ation: 04.24 Fare Option - Disable Negotiated Space...............................332

5.60.1 Quer y Structure....................................................................................................................... 332

5.60.2 Reply Structure........................................................................................................................ 333

5.60.3 Possible Errors........................................................................................................................ 333

5.61 Oper ation: 04.25 Fare Option - Open Return................................................... 334

5.61.1 Quer y Structure....................................................................................................................... 334

5.61.2 Reply Structure........................................................................................................................ 335

5.61.3 Possible Errors........................................................................................................................ 353

5.62 Oper ation: 04.26 Fare Option - Alternate Price................................................ 354

5.62.1 Quer y Structure....................................................................................................................... 355

5.62.2 Reply Structure........................................................................................................................ 357

5.62.3 Possible Errors........................................................................................................................ 371

5.63 Oper ation: 04.27 Fare Option - Search by FBA................................................372

5.63.1 Quer y Structure....................................................................................................................... 372

5.63.2 Reply Structure........................................................................................................................ 373



Table of Contents

x

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 Oper ation: 05.3 Cabin Option - Major Cabin.................................................... 380

5.66.1 Quer y Structure....................................................................................................................... 380

5.66.2 Reply Structure........................................................................................................................ 382

5.66.3 Possible Errors........................................................................................................................ 382

5.67 Oper ation: 06.1 Fee Option - Pricing Scheme Reference.................................383

5.67.1 Quer y Structure....................................................................................................................... 383

5.67.2 Reply Structure........................................................................................................................ 385

5.67.3 Possible Errors........................................................................................................................ 393

5.68 Oper ation: 06.2 Fee Option - Form of Payment............................................... 394

5.68.1 Quer y Structure....................................................................................................................... 394

5.68.2 Reply Structure........................................................................................................................ 396

5.68.3 Possible Errors........................................................................................................................ 396

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

5.69.1 Quer y Structure....................................................................................................................... 397

5.69.2 Reply Structure........................................................................................................................ 398

5.69.3 Possible Errors........................................................................................................................ 398

5.70 Oper ation: 06.4 Fee Option - Exempt all airline ticketing fees..........................400

5.70.1 Quer y Structure....................................................................................................................... 400

5.70.2 Reply Structure........................................................................................................................ 401

5.70.3 Possible Errors........................................................................................................................ 401

5.71 Oper ation: 06.5 Fee Option - Add/Exempt airline ticketing fees by sub-code... 402

5.71.1 Quer y Structure....................................................................................................................... 402

5.71.2 Reply Structure........................................................................................................................ 404



Table of Contents

xi

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........................................................................................................................ 4135.74 Operation: 07.2 Distribution Option - Airline Distribution Container: ADC.........414

5.74.1 Quer y 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 Quer y Structure....................................................................................................................... 416

5.75.2 Reply Structure........................................................................................................................ 417

5.75.3 Possible Errors........................................................................................................................ 417

5.76 Oper ation: 07.4 Distribution option - Not DDI: Deactivation of DirectDistribution........................................................................................................................ 418

5.76.1 Quer y 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 Quer y 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 Quer y 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 Quer y Structure....................................................................................................................... 424



Table of Contents

xii

5.79.2 Reply Structure........................................................................................................................ 4255.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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y Structure....................................................................................................................... 486



Table of Contents

xiii

5.87.2 Reply Structure........................................................................................................................ 4875.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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y 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 Quer y Structure....................................................................................................................... 568



Table of Contents

xv

5.103.1 Query Structure..................................................................................................................... 5965.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 Oper ation: 10.09 Ancillary services option - Request a service sub-group.... 601

5.105.1 Query Structure..................................................................................................................... 6015.105.2 Reply Structure...................................................................................................................... 603

5.105.3 Possible Errors...................................................................................................................... 603

5.106 Oper ation: 10.10 Ancillar y 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 Oper ation: 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 Oper ation: 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 Oper ation: 11.1 - OB fees with connections................................................... 626

5.110.1 Query Structure..................................................................................................................... 626

5.110.2 Reply Structure...................................................................................................................... 627



Table of Contents

xvi

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...................................................................................................................... 6315.113 Oper ation: 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 Oper ation: 12.3 Passengers Ref - 1 adult with 1 infant and 1 child, Passenger 3with no age specified........................................................................................................634

5.114.1 Query Structure..................................................................................................................... 634

5.114.2 Reply Structure...................................................................................................................... 635

5.114.3 Possible Errors...................................................................................................................... 635

5.115 Oper ation: 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 Oper ation: 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 Oper ation: 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 Oper ation: 14.1 Free Baggage Allowance with multiple passenger types.......690

5.118.1 Query Structure..................................................................................................................... 690



Table of Contents

xvii

5.118.2 Reply Structure...................................................................................................................... 6925.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...................................................................................................................... 7135.120.3 Possible Errors...................................................................................................................... 713



Web services User guide for function Fare_MasterPricerTravelBoardSearch

Copyright © 1987-2015 Amadeus IT Group SA.

Page 18 of 714

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 Productspecifications.

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





Page 19 of 714

Fare_MasterPricerTravelBoardSearchThis function provides the ability to search the Amadeus fare system for lowest fare recommendations withregards 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 Searchfunction. 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 user has the ability to specify multiple Officeids in addition to the Originator Office id.





Page 20 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 thepotential to receive up to 200 trip recommendations, enabling web-based customers to easily navigate throughmany 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 codesfor 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 returnrecommendations of proposed segments making up a journey for the requested segments of an itinerarywith applicable price information. Thus, allowing the user to navigate through the list of recommendations todetermine the best choice for travel arrangements.

The following is a high level overview of this process:





Page 21 of 714





Page 22 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 operationcorresponds very often to the use of an option. However, in some cases, it describes a scenario that pointsout 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 seatsfor 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 23 of 714

In order to ensure a good overall journey convenience of the response, the Flight Convenience ensures thatthe 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. Themore 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 2-

alphanumeric character airline 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 cityspecified for an origin or a destination. If an origin or destination area is specified, the low fare search processmay consider any city whose flying distance to the specified City or Airport is lower than the specified radiusin the query.

• Ignore Availability

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

• Disable biased reference

When this option is requested, the flight search request is performed in neutral mode independently of theoffice 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 24 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 mixingcarriers exist.

• Interline option

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

• Anchored Search

The user has the ability to freeze one or more requested segments in input in order to get only recommendationsincluding 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 minimumconnections 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 bydeparture 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 consecutiveproposed segments. This minimum time is specified in input with the following format HHMM. Any valuebetween 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 datespecified for a trip segment.





Page 25 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 whichdetermines 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. Non-homogeneous 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 thelow 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 matchingpredefined criteria as "Cheapest Recommendations" or "Non Stop".

• Cabin Options





Page 26 of 714

The user has the ability to specify a desired cabin class for the requested itinerary. There is three differentflavours of process: Mandatory, Recommended and Major Cabin that are described in the correspondingoperations.

• 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 cheapestavailable 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 Airlineticketing fees (OB fees) sub-codes can be specified in order to add or exempt particular fees.

Ancillary services OptionThe user can request ancillary services.

In pushed mode, all or preselected subset of applicable ancillary services and associated prices will be returnedin each recommendation but not considered in the search of the lowest fares. The pushed mode is set as thedefault mode.

In pulled mode, all or preselected subset of ancillary services and associated prices are returned in eachshopping recommendations and considered in the search of the lowest fares.





Page 27 of 714

Distribution options

• Airline Distribution: ADI

When this option is requested, the total number of Recommendations are distributed over 2 sets as thefollowing:

The Airline Diversity Set contains the cheapest recommendation for each online carrier and the cheapestrecommendation for each Mono-Main Carrier.

The Cheapest Recommendations Set contains the cheapest recommendations matching the query that arenot 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 airlinediversity.

The Cheapest Recommendations Set contains the cheapest recommendations matching the query that arenot 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 thepossibility 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 28 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 (thesearch 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 typeof 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 hasthe 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 thequery 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 29 of 714

Depending of the office ID setting, the user has the ability to display the commission in percentage for eachfare 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 daterange.

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 to specify 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 30 of 714

Origin/Destination - Forced LocationThe option to force a location to a city from a previously requested segment search result is not currentlyprocessed. For example, 2nd requested departure city indicated to match the 1st requested arrival city of aproposed 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 faresearch.

Therefore, the code OV is not supported.

1.4 Prerequisites

None





Page 31 of 714

2 Building A QueryEach query follows a given structure. The queries for the function operations are clearly explained with dataelement 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 thebasis for a better understanding on which fields are mandatory for basic operation utilisation. In some cases itis not a full explanation of every field that can be utilised for the operation, but rather a guideline to its use.

ConsiderationsWhen 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 6Parameterized Fare Families can be defined in the Master Pricer query. The parameterized Fare Family canbe 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 ParametersThe optional parameters may apply at the Requested Segment and/or Itinerary level. Applicable Option LevelsThe following table gives the rule for each option in terms of applicable levels.

Options Applies to Segment Applies to Itinerary

Flight Options

Number of recommendations X

Airline X X

Cabin X X

Time Window X

Times Departure/Arrival X

Connecting point X

Expanded Parameter X

Flight Category X X

Selling/Ticketing Cities X

Radius (Origin/Destination areas) X





Page 32 of 714

Multi-city X

No Slice and Dice X

Disabled Biased Reference X

More overnights X

Exclude Low Cost Carriers

Ignore Availability X

Airline Distribution: ADI X

Airline Distribution Container: ADC X

Non-Stop Preferred X

Online X X

Anchored Search X

Point of commencement X

Progressive legs X X

Fare Options

Passenger Type X

Price to Beat X

Unifares X

Parameterized Fare Families X

Split/No Split PNR X

Currency Conversion X

Paper Ticket/Electronic Ticket X

Ticketability pre-check X

Expanded Parameters X

Withhold All Taxes/Surcharges X

Service Fees: Pricing Schemereference

X

Multi-tickets X

Form of payment X

Adding/exempting specific airlineticketing fees

X

Exempt all airline ticketing fees X

Sorting with/without Fees X

Multi Office IDs X

Price only PTC X





Page 33 of 714

Alternate Price X

Date Options

Range of Dates X

Output Options

Identify YQ/YR tax amounts X

Empty Cells Clarification X

Rank in Journey Server X

Ancillary service fees X X

Value Search X X

Optional Data Profile X

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, asspecified in the description of the corresponding option paragraph, then the option specified at the RequestedSegment level takes precedence over the Itinerary option.

Examples:

Request Process1st Requested

Segment2nd Requested

SegmentItinerary 1st Requested

Segment2nd Requested

Segment

Include Airlines: AA,CO

Include Airlines: AA,DL

Include Airlines: AA,CO

Include Airlines: AA,DL

Include Airlines: FL,CO, YY

Exclude Airlines: AA, DL

Include Airlines:FL, CO eventuallycombined with anyairline 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 theuser 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, theentire entry is rejected with the following message:

"OPTION CANNOT BE APPLIED AT ITINERARY LEVEL"





Page 34 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. Theresponsibility lies with the API developer to read the element sections for rules and combinability issues tobuild the applicable messages desired.

As a guideline for the possibility of a more complex message structure, the sample query structure below isgiven, 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 recommendationsreturned

4 - 8 Passenger Types of 2 Adults and 1 Child

9 - 10 DL airlines are to be excluded from anyrecommendations

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 at5pm

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 Flightsfor the recommendations

Item # SearchQuery - Data element Value

0 /Segment/unitNumberDetail[1] /numberOfUnits3

1 /Segment/unitNumberDetail[1] /typeOfUnit

PX

2 /Segment/unitNumberDetail[2] /numberOfUnits

200

3 /Segment/unitNumberDetail[2] /typeOfUnit

RC

4 /paxReference[1]/ ptc ADT





Page 35 of 714

5 /paxReference[1]/traveller[1] /ref 1

6 /paxReference[1]/traveller[2] /ref 2

7a /paxReference[2]/ ptc[1] CH

7b /paxReference[2]/ ptc[2] MIL

8 /paxReference[2]/traveller /ref 3

9 /travelFlightInfo/companyIdentity[2] /carrierQualifier

X

10 /travelFlightInfo/companyIdentity[2] /carrierId

DL

11 /itinerary[3]/requestedSegmentRef /segmentRef 1

12 /itinerary[3]/departureLocalization/departurePoint /locationId

NCE

13 /itinerary[3]/arrivalLocalization/arrivalPointDetails /locationId

HOU

14 /itinerary[3]/timeDetails/firstDateTimeDetail /timeQualifier

TA

15 /itinerary[3]/timeDetails/firstDateTimeDetail /date

200204

16 /itinerary[3]/timeDetails/

firstDateTimeDetail /time

1700

17 /itinerary[4]/requestedSegmentRef /segmentRef

2

18 /itinerary[4]/departureLocalization/departurePoint /locationId

HOU

19 /itinerary[4]/arrivalLocalization/arrivalPointDetails /locationId

NCE

20 /itinerary[4]/timeDetails/firstDateTimeDetail /date

280204

21 /itinerary[4]/flightInfo/

flightDetail /flightType[1]

N

22 /itinerary[4]/flightInfo/flightDetail /flightType[2]

D

Referring to the applicable element sections of this document will provide any specific element informationrequired.





Page 37 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 Value

/electronicTicketing Y

/electronicTicketing Y

Electronic ticketing (e-ticketing) allows sending ticketing information directly to an airline so that passengerscan 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 displayedin the reply.

Notes:

• The amount of time that electronic ticket record remains stored in the airline's system varies amongairlines.• In order for electronic tickets (in other word e-ticketing) to be issued, the office must be authorised toissue e-tickets as defined at the Office Profile level.The flight segments in the itinerary are required to beeligible 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 priceof 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. Thiscontext 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 the3 flights are AB, BC, and CD. Without Slice and Dice process, only O&D availability AD is checked. With theSlice and Dice process, local availabilities AB, BC, CD and Sub O&D availabilities AC and BD (respectivelynamed 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 soldat the same time. In case of Sub O&D, the two corresponding flights must be sold together and in case of localcontext, the corresponding flight has to be sold alone.

In segmentFlightRef, an additional refQualifier with the value "A" (for Recommendation Availability context) isadded with its refNumber

SearchReply - Data element Example Description

segmentFlightRef /referencingDetail / refQualifier

S Reference of Proposed Segment

segmentFlightRef /referencingDetail / refNumber

3 Index to Proposed Segment

segmentFlightRef /referencingDetail / refQualifier

A Reference to availability





Page 38 of 714

segmentFlightRef /referencingDetail / refNumber

1 Index to availability context

The corresponding description for each reference of a recommendation availability context is given in the groupspecificRecDetails. 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 theavailabilityCnxType.

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

SearchReply - Data element Example Description

specificRecDetails /specificRecItem /referenceType

A Availability context

specificRecDetails/specificRecItem/refNumber

1 Availability context index

specificProductDetails/productReferences / paxFareNum

1 Reference to passenger

specificProductDetails/fareContextDetails/requestedSegmentInfo/ segRef

1 Index of Proposed Segment

fareContextDetails/cnxContextDetails[1]/ fareCnxInfo/contextDetails/ availabilityCnxType

LA availability context "local" for firstflight of Proposed Segment

fareContextDetails/cnxContextDetails[2]/ fareCnxInfo/contextDetails/ availabilityCnxType

LA 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 isprovided 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 beenrequested 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 39 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 thatis returned in the reply:

SearchReply - Data element example Description

/ familyInformation /refNumber 1 Reference of the fare family

/ familyInformation /fareFamilyname FFAMILY1 Name of the fare family

/ familyInformation /hierarchy 100 1

• Fare Family Reference of each fare detail:


/ fareDetails / groupOfFares /fareFamiliesRef /referencingDetail/refQualifier

F Reference of the fare family

/ fareDetails / groupOfFares /fareFamiliesRef /referencingDetail/

refQualifier/ refNumber

1 Reference to the Fare Familyreferenced 1 in the family

information node.• Fare Breakpoint returned


/recommendation[2] /paxFareProduct[4] /fareDetails[2] /groupOfFares/ productInformation/breakPoint

Y 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.


priceTicketing/ priceType[1]/ OBV Validating carrier accepts OB fees

priceTicketing/ priceType[2]/ OBA OID accepts OB fees

recPriceInfo/ monetaryDetail/amountType

recPriceInfo/ monetaryDetail/amount





Page 40 of 714

paxFareDetail/ codeShareDetails/transportStageQualifier

V 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/amount

10 Amount

It should be noted that the number of recommendations returned are dispersed between applicable fares andwill be less than or equal to the number recommendations requested in the query. One applicable Fare maycontain 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 recommendationsto a query containing 2 requested segments (1st - Nice to Houston, 2nd - Houston to Nice):

Item # Reply Information

1 Applicable Currency of reply in US Dollars

PROPOSED SEGMENTS APPLICABLE TO 1ST REQUESTED SEGMENT

2 Applicable "Requested" Segment - 1st Requested segment

3 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


34-59 Flight Details for 2nd proposed segment

34-46 1st flt Nice to Paris


60 Applicable "Proposed" Segment - 3rd Proposed segment

61 Total elapsed flying time for proposed segment - 13h50

62-87 Flight Details for 2nd proposed segment

62-74 1st flt Marseille to Paris


PROPOSED SEGMENTS APPLICABLE TO 2ND REQUESTED SEGMENT

88 Applicable "Requested" Segment - 2nd Requested segment

89 Applicable "Proposed" Segment - 1st Proposed segment





Page 41 of 714



93-105 1st flt Houston to London

106-118 2nd flt London to Nice

119 Applicable "Proposed" Segment - 2nd Proposed segment



122-135 1st flt Houston to Paris

136-148 2nd flt Paris to Nice

149 Applicable "Proposed" Segment - 3rd Proposed segment



152-165 1st flt Houston to Paris

166-178 2nd flt Paris to Nice

179 Applicable "Proposed" Segment - 4th Proposed segment



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 Applicable Fare Details

220-238 Fare Details for Adult passengers239-258 Fare Details for Child passenger

259-300 2nd Set of recommendations for an Applicable fare



262-265 Applicable flight combination of - completing recommendation #3






Page 42 of 714


301-330 3rd Set of recommendations for an Applicable fare





NOTE: The reply structure contains all proposed segments listed first followed by associated fare informationfor the proposed segments to complete each recommendation.

Item SearchReply - Data element Value

1 /conversionRate/conversionRateDetail/ currency

USD

PROPOSED SEGMENTS FOR 1st REQUESTED SEGMENT

2 /flightIndex [1] /requestedSegmentRef/ segRef

1

3 /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal[1] / ref

1


1350

5 /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal[2] / unitQualifier

EFT


AF


MCX

8 /flightIndex [1] /groupOfFlights[1] /flightDetails [1] /flightInformation/productDateTime/dateOfDeparture

200202

9 /flightIndex [1] /groupOfFlights[1] /flightDetails [1] /flightInformation/productDateTime/timeOfDeparture

0725

10 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/productDateTime/ dateOfArrival

200202





Page 43 of 714

11 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/productDateTime/ timeOfArrival

0855

12 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/location [1] / locationId

NCE


CDG

14 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/

location [2] / airportCityQualifier

A

15 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/companyId/ marketingCarrier

AF

16 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/companyId/ operatingCarrier

AF

17 /flightIndex [1] /groupOfFlights [1] /flightDetails [1] /flightInformation/flightNumber

7673

18 /flightIndex [1] /groupOfFlights [1] /

flightDetails [1] /flightInformation/productDetail/ equipmentType

320

19 /flightIndex [1] /groupOfFlights[1] /flightDetails [1] /flightInformation/addProductDetail/electronicTicketing

Y


200202

21 /flightIndex [1] /groupOfFlights

[1] /flightDetails [2] /flightInformation/productDateTime/timeOfDeparture

1020


200202


1415





Page 44 of 714


CDG


IAH


CO


companyId/ operatingCarrier

AF


83

29 /flightIndex [1] /groupOfFlights [1] /flightDetails [2] /flightInformation/productDetail/ equipmentType

343


Y


2


1350


EFT

34 /flightIndex [1] /groupOfFlights [1] /propFlightGrDetail/flightProposal

[3] / ref

AF


MCX


200202





Page 45 of 714


0725


200202


0855


flightDetails [1] /flightInformation/location [1] / locationId

NCE


CDG


AF


AF


7673


320


Y


[2] /flightDetails [2] /flightInformation/productDateTime/dateOfDeparture

200202


1020





Page 46 of 714


200202


1415


CDG


location [2] / locationId

IAH


AF


AF


36


flightDetails [2] /flightInformation/productDetail/ equipmentType

343


Y


3


[2] / ref

1350


EFT


AF





Page 47 of 714


MCX


200202


0725


200202


0855


MRS



CDG

69 /flightIndex [1] /groupOfFlights [3] /flightDetails [1] /flightInformation/location [2] / airportCityQualifier

A


AF


AF


flightDetails [1] /flightInformation/flightNumber

7673


320


Y





Page 48 of 714


200202


1020


200202


1415


CDG


IAH


companyId/ marketingCarrier

CO


AF


83


343


[3] /flightDetails [2] /flightInformation/addProductDetail/electronicTicketing

Y

PROPOSED SEGMENTS FOR 2nd REQUESTED SEGMENT

86 /flightIndex [2] /requestedSegmentRef/ segRef

2





Page 49 of 714


1


1215


EFT


[3] / ref

BA


MCX


210302

93 /flightIndex [2] /groupOfFlights[1] /flightDetails [1] /flightInformation/productDateTime/

timeOfDeparture

1625


220302


0710

96 /flightIndex [2] /groupOfFlights [1] /flightDetails [1] /flightInformation/productDateTime/ dateVariation

1


flightDetails [1] /flightInformation/location [1] / locationId

IAH


LGW


BA





Page 50 of 714


BA


2024


747

103 /flightIndex [2] /groupOfFlights[1] /flightDetails [1] /

flightInformation/addProductDetail/electronicTicketing

N


220302


0840


flightDetails [2] /flightInformation/productDateTime/ dateOfArrival

220302


1140


LGW


NCE


BA


BA


2362





Page 51 of 714


737


N


2


propFlightGrDetail/flightProposal[2] / ref

1220


EFT


CO


MCX


210302


1840


220302


1055


1


IAH





Page 52 of 714


CDG


CO


CO


flightNumber

10


777


Y

132 /flightIndex [2] /groupOfFlights[2] /flightDetails [2] /flightInformation/productDateTime/

dateOfDeparture

220302


1235


220302


1400


CDG


NCE


AF





Page 53 of 714


AF


7664


320


flightInformation/addProductDetail/electronicTicketing

Y


3


1220


EFT


CO


MCX


210302


[3] /flightDetails [1] /flightInformation/productDateTime/timeOfDeparture

1840


220302


1055





Page 54 of 714


1


IAH


CDG



AF


CO


35


777



Y


220302


1235


220302


1400


CDG





Page 55 of 714


NCE


AF


AF


flightNumber

7664


320


Y


4


1225


EFT


CO


[3] / unitQualifier

MCX


210302


1850





Page 56 of 714


220302


0955


1



IAH


LGW


CO


CO


flightDetails [1] /flightInformation/flightNumber

4


777


Y


flightInformation/productDateTime/dateOfDeparture

220302


1115


220302





Page 57 of 714


1415


LGW


NCE



BA


BA


2368


AR1



N

RECOMMENDATIONS

1st SET OF RECOMMENDATIONS BASED ON 1 FARE

199 /recommendation [1] /itemNumber/itemNumberId/ number

1

APPLICABLE FARE AMOUNT

200 /recommendation [1] /recPriceInfo/monetaryDetail [1] / amount

1800.11


150.00

1st APPLICABLE JOURNEY - RECOMMENDATION # 1

202 /recommendation [1] /segmentFlightRef [1] /referencingDetail [1] / refQualifier

S





Page 58 of 714

203 /recommendation [1] /segmentFlightRef [1] /referencingDetail [1] / refNumber

1


S


1

2nd APPLICABLE JOURNEY - RECOMMENDATION # 2


S


2


S


3

APPLICABLE FARE DETAILS

210 /recommendation [1] /paxFareProduct [3] /paxFareDetail/paxFareNum

1

211 /recommendation [1] /paxFareProduct [3] /paxFareDetail/totalFareAmount

1100.00

212 /recommendation [1] /paxFareProduct [3] /paxFareDetail/totalTaxAmount

60.00

213 /recommendation [1] /paxFareProduct [3] /paxReference/ptc

ADT

214 /recommendation [1] /paxFareProduct [3] /paxReference/traveller [1] / ref

1


2





Page 59 of 714

216 /recommendation [1] /paxFareProduct [3] /fareDetails[1] /segmentRef/ segRef

1

217 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/cabinProduct/rbd

M

218 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/cabinProduct/cabin

M

218-2 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/cabinProduct/avlStatus

4

219 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/fareProductDetail/ fareBasis

MLXPX

220 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/fareProductDetail/ passengerType

ADT

221 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/fareProductDetail/ fareType

RP

222 /recommendation [1] /

paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/ Breakpoint

N


2

224 /recommendation [1] /paxFareProduct [3] /fareDetails

M





Page 60 of 714

[2] /productInformation/avlProductDetails/ rbd


M

226 /recommendation [1] /paxFareProduct [3] /fareDetails [1] /groupOfFares/productInformation/cabinProduct/avlStatus

4

227 /recommendation [1] /paxFareProduct [3] /fareDetails[2] /productInformation/fareProductDetail/ fareBasis

MLXPX

228 /recommendation [1] /paxFareProduct [3] /fareDetails[2] /productInformation/fareProductDetail/ passengerType

ADT

229 /recommendation [1] /paxFareProduct [3] /fareDetails[2] /productInformation/

fareProductDetail/ fareType

RP

230 /recommendation [1] /paxFareProduct [3] /fareDetails [2] /groupOfFares/productInformation/ Breakpoint

Y


1


700.11


30.00


CH





Page 61 of 714

235 /recommendation [1] /paxFareProduct [4] /paxReference/traveller/ ref

3

236 /recommendation [1] /paxFareProduct [4] /fare/pricingMessage/freeTextQualification/messageQualifier

APM

/recommendation [1] /paxFareProduct [4] /fare/pricingMessage/freeTextQualification/messageCode

5

237 /recommendation [1]/paxFareProduct [4] /fare/pricingMessage/ description [1]

NOT FARED AT PASSENGERTYPE REQUESTED

238 /recommendation [1] /paxFareProduct [4] /fare/pricingMessage/ description [2]

5


1

240 /recommendation [1] /paxFareProduct [4] /fareDetails[1] /productInformation/avlProductDetails/ rbd

M


M

242 /recommendation [1] /paxFareProduct [4] /fareDetails [1] /groupOfFares/

productInformation/cabinProduct/avlStatus

4


Y4WCH


CH





Page 62 of 714

[1] /productInformation/fareProductDetail/ passengerType

245 /recommendation [1] /paxFareProduct [4] /fareDetails[1] /productInformation/fareProductDetail/ fareType

RP


N


paxFareProduct [4] /fareDetails[2] /segmentRef/ segRef

2


M


M

250 /recommendation [1] /paxFareProduct [4] /fareDetails [2] /groupOfFares/productInformation/cabinProduct/avlStatus

4


Y4W


fareProductDetail/ passengerType

ADT


RP


Y





Page 64 of 714


1209.70


70.00


ADT

264 /recommendation [2] /paxFareProduct [3] /paxReference/

traveller [1] / ref

1


2


1


M


TLXAPT3


ADT


fareProductDetail/ fareType

RP


2


M





Page 65 of 714


TLXAPT3


ADT


RP


1


780.00


60.00


paxFareProduct [4] /paxReference/ptc

CH


3


1


avlProductDetails/ rbd

M


TLXAPTCH


CH





Page 66 of 714


RP


2


M


TLXAPTCH


CH


RP

3rd SET OF RECOMMENDATIONS BASED ON 1 FARE

291 /recommendation [3] /itemNumber/itemNumberId/ number

3

APPLICABLE FARE AMOUNT


2350.50


200.00

1st ASSOCIATED JOURNEY - RECOMMENDATION # 5


S


2


S





Page 67 of 714


1

APPLICABLE FARE DETAILS


1


1350.00


70.00


ADT


1


2


1


C


RP


2


D


RP





Page 68 of 714

[2] /productInformation/fareProductDetail/ fareType


1


1000.50


60.00


CH


3


1



C


RP


2



D


RP





Page 69 of 714

Free Baggage Allowance (FBA)

The FBA information describes the free baggage allowed per flight and per passenger type for eachrecommendation. 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 attachedwithin a recommendation. This information is returned by Fare Component or by requested segment. This istriggered 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

1 Movie

2 Telephone

3 Telex

4 Audio programming

5 Television

6 Reservation booking service

7 Duty free sales

8 Smoking

9 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 70 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 kilogramsor 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><freeBagAllowanceGrp>






Page 71 of 714

<freeAllowance>1</freeAllowance><quantityCode>N</quantityCode>




</freeBagAllowanceGrp></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 isapplicable (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 Requestedsegment 2 – Leg 1 and 2)• Free Baggage allowance reference (refNumber 3)

3.2.2 Xml Structure

<serviceFeesGrp><serviceTypeInfo>

<carrierFeeDetails><type>FBA</type>

</carrierFeeDetails></serviceTypeInfo><serviceCoverageInfoGrp>

<itemNumberInfo><itemNumber>

<number>10</number></itemNumber>

</itemNumberInfo><serviceCovInfoGrp>

<paxRefInfo><travellerDetails>

<referenceNumber>1</referenceNumber>





Page 72 of 714

</travellerDetails></paxRefInfo><coveragePerFlightsInfo>

<numberOfItemsDetails><referenceQualifier>RS</referenceQualifier><refNum>1</refNum>

</numberOfItemsDetails><lastItemsDetails>

<refOfLeg>1</refOfLeg></lastItemsDetails>

</coveragePerFlightsInfo><coveragePerFlightsInfo>



<refOfLeg>1</refOfLeg></lastItemsDetails><lastItemsDetails>


</coveragePerFlightsInfo><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 DescriptionThis sub structure contains the reference corresponding to the baggage allowance coverage applicable to thereturned recommendation:

• refQualifier: B• refNumber: 1

3.3.2 Xml Structure

<recommendation>





Page 73 of 714

<itemNumber><itemNumberId>

<number>1</number></itemNumberId>

</itemNumber><recPriceInfo> </recPriceInfo><segmentFlightRef>

<referencingDetail><refQualifier>S</refQualifier><refNumber>1</refNumber>

</referencingDetail><referencingDetail>

<refQualifier>S</refQualifier><refNumber>1</refNumber>


<refQualifier>B</refQualifier><refNumber>1</refNumber>

</referencingDetail></segmentFlightRef>

</recommendation>





Page 74 of 714

4 Error MessagesSpecific error conditions exist for each mandatory and optional parameter in the query. However, as theseerrors may be returned in several instances and it is not always apparent to which operational parameter theyapply, 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 mandatoryvia an association to another optional parameter, the entire entry is rejected.

Common ErrorsIt should be noted here that these messages are returned in the instances when no recommendations canbe found.No Recommendation Found For Requested Itinerary/OptionsWhenever the Lowest Fare Search does not find any recommendation matching the requested options, thequery is rejected with the following message:

"NO RECOMMENDATION FOUND FOR REQUESTED ITINERARY/OPTIONS"No Available Flight Found For The Requested Segment NnIn the current Lowest Fare Search process, when no flight is available (For example, all the flights matchingthe 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 SEGMENTnn"(Where: nn represents the first impacted requested segment number).These messages are returned when there is an error in the Lowest 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 goesbeyond the latest possible date. The corresponding reject message:"LATEST FUTURE DATE POSSIBLE ddmmmyy"Too Many Airline CodesIf more than 99 airline codes are specified at the 'Include Airline' option level, the entire entry is rejected andthe following message is returned:

"TOO MANY AIRLINE CODES"Invalid Value (Coded) - PricingtickinfoThe only valid expanded parameter options applicable to a MP request are NAP, NPE, NR and RF. If anunknown 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 message is returned:

"INVALID VALUE CODED - PRICINGTICKINFO"Too Many Requested SegmentsUp to 3 Requested Segments 'Lowest Fare search' requests are allowed, excluding surface sectors. If thischeck fails, the entire entry is rejected with the following message:

"TOO MANY REQUESTED SEGMENTS"Invalid Value (Coded) - Conversion RateIf an unknown Currency is specified in the Lowest Fare search entry, the entire request is rejected and thefollowing error message is returned:





Page 75 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 messagelevel, the entire entry is rejected and, if no other specific error message exists, the following generic rejectmessage is returned:

"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 avoidoverlapping

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 Segmentlevel

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 76 of 714

937 Invalid time window option

938 Time of Departure/Arrival is mandatory if timewindow 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 andexcluded

943 Invalid - 20 airline codes maximum

944 Invalid flight category945 Non-stop cannot be requested with connect point

option

946 Invalid connecting point

947 Same city/airport code cannot be included andexcluded

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 77 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 FORREQUESTED 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

REQUESTED987 NO FARE FAMILY FOUND FOR REQUESTED

COMMERCIAL FARE FAMILY

988 EXCEEDS MAXIMUM DISCOUNT CODES FOR APASSENGER

993 INVALID TIME AT DESTINATION

994 INVALID ITINERARY POINT OF ORIGIN OPTION

995 NO FARE FOUND FOR REQUESTED FAREFAMILY

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 78 of 714

TOO MANY MATCHING ATTRIBUTES SETSREQUESTED

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 79 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 theTU times and dates.

Up to 2 requested segments may be requested with the same date, or overlapping date ranges, as long asthe 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 musteach include an origin and a destination city/airport code.

One-Way NCE-LONReturn 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 isnot 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 wherethe IATA code is not unique to an airport.

The following table illustrates further the possible scenarios of the origin/destination search process:

Code Entered Specified as City/Airport Applicable point of departure/arrival searched

CHI Not Specified Chicago city, including thefollowing airports:

- O'Hare (ORD)

- Midway (MDW)

CHI City Location Chicago city, including thefollowing airports:





Page 80 of 714

- O'Hare (ORD)

- Midway (MDW)

CHI Airport Location Chicago city, including thefollowing airports:

- O'Hare (ORD)

- Midway (MDW) (because CHIairport code does not exist)

ORD Not specified O'Hare (ORD)

HOU Not Specified Houston city, including thefollowing airports:

- Houston Hobby (HOU)

- G. Bush Intercontinental (IAH)

HOU City location Houston city, including thefollowing airports:

- Houston Hobby (HOU)

- G. Bush Intercontinental (IAH)

HOU Airport location Houston Hobby (HOU) airport onlyOnly 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 samecountry as the selling and the ticketing country location,• for international itineraries, the origin city/airport code of the first international segment (excludingsurface 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 FranceCHI-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 81 of 714

The recommendations returned are applicable to all passengers in the query. All passengers must be travellingtogether.

Associated Passenger Type Codes

As the passenger fares vary for different types of passengers, a passenger type code for any low fare searchis required. Passenger type codes dictate the low fare search to provide recommendations with any qualifyingpassenger fare discounts applicable. All passenger type codes specified must be valid type codes stored withinthe 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 thepossibility 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 thelowest 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, andso 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 82 of 714

Requesting Specified Data

Request by number of seats occupied by passengers PX

# of seats for request 3

Request specific maximum number of recommendations to be returned

RC

Maximum number of recommendations to bereturned

200

Applicable passenger type code for Adult ADT

Passenger reference for 1st seat 1

Passenger reference for 2nd seat 2 Applicable passenger type code for Child CH

Passenger reference for 3rd seat 3

Applicable passenger type code for Infant INF

Passenger reference associated to first Adult seat 1

Infant indicator 1

1st requested segment 1

Departure city of London LON

Arrival city of New York 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>

<numberOfUnits>200</numberOfUnits><typeOfUnit>RC</typeOfUnit>

</unitNumberDetail></numberOfUnit><paxReference>

<ptc> ADT</ptc><traveller>

<ref>1</ref></traveller><traveller>

<ref>2</ref></traveller>





Page 83 of 714

</paxReference><paxReference>

<ptc>CH</ptc><traveller>



<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 84 of 714

Past Date/Time Not AllowedIf 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, theentire 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 requiredparameters 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 whena 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' optionon the chronologically first segment and a 'Time of Departure' on the next segment. This will avoid experiencingnumerous Master Pricer "Near requested travel dates" query failures because of missing mandatory option inthe 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 timedeparture times of the 2 consecutive requested segments (meaning, the latest possible departure time of thefirst requested segment and the earliest possible departure time of the next requested segment) is inferior to12 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 isrejected with the following message:





Page 85 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 requestedsegment. The origin and destination being requested as airport, city, area or multi-city, an overlap is detectedwhen, 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 followingmessage:

"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 messageis returned:

"EXCEEDS MAXIMUM FARE DISCOUNT CODES"

The Number of Non-Infant PTCs Cannot Exceed Number of SeatsThe 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 isrejected 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 andthe following error message is returned:





Page 86 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 thequery and an invalid number of recommendations (higher than 200) in the query is ignored, no system error conditions currently exist for this option.





Page 87 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 optionsmay be specified in the same request. The preferred option can be combined with any other option except thepreferred connecting point. And it cannot be specified at the same level (itinerary, same requested segment)as the include/exclude options.

If a YY carrier code is used in the include option at the same time as a specific airline/alliance, then this specificairline/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 specifiedin 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 aconnection is selected. In case of joint operation, both airline/alliance codes have to be checked. Marketingcarrier and operating carrier will have to be checked.

Preferred airline codes can be used to ensure that proposed segments considered by the system whenbuilding recommendations will include online solutions on those airlines. This option does not ensure thatrecommendations returned by Master Pricer will include such proposed segments as the objective is still topropose the lowest available recommendations.

Alliance codes:

• ONEWORLD *O• SKYTEAM *S• STAR ALLIANCE *A









</paxReference><travelFlightInfo>

<companyIdentity><carrierQualifier>M</carrierQualifier>





Page 89 of 714

</firstDateTimeDetail></timeDetails><flightInfo>

<companyIdentity><carrierQualifier>F</carrierQualifier><carrierId>BA</carrierId>

</companyIdentity></flightInfo>




Invalid Airline CodeThe airline codes are a 2 alpha numeric character code that is defined in the Amadeus System. If the airlinecode 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 OptionYY 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 includeairline code, the entire entry is rejected with the following message:

"INVALID EXCLUDE AIRLINE OPTION"

Example:

Request Process

Include: TW, CO, AA

Exclude: US

Entry rejected.

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 ExcludedIf the same airline code is specified as "Include" and "Exclude", at the same request level, the entire entryis 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 90 of 714

INVALID 3 PREFERRED AIRLINE CODES MAXIMUM• If the Preferred Airline option is requested in combination with the Include/Exclude Airline option, theentry 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 91 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 informationlimitations, 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 liketechnical 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 withthe 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





RC

Maximum # of recommendations requested 200

Adult Passenger type code ADT

Passenger type code applicable to 1st passenger 1

Non-Stop Flight Category request applicable for entire trip

N

Direct Flight Category request applicable for entiretrip

D

Applicable on 1st segment 1

Trip departure city of Paris PAR

Trip arrival city of Miami MIA

Trip Date 20 Dec, 2001 201201





Page 92 of 714

Applicable on 2nd segment 2

Trip departure city of Miami MIA

Trip arrival city of Paris NYC

Trip Date 25January,2002 250102

Direct Flight Category request D



<unitNumberDetail>

<numberOfUnits>1</numberOfUnits><typeOfUnit>PX</typeOfUnit>





<ref>1</ref>

</traveller></paxReference><travelFlightInfo>

<flightDetail><flightType>N</flightType><flightType>D</flightType>

</flightDetail></travelFlightInfo><itinerary>



<departurePoint><locationId>PAR</locationId>

</departurePoint></departureLocalization><arrivalLocalization>

<arrivalPointDetails><locationId>MIA</locationId>

</arrivalPointDetails></arrivalLocalization><timeDetails>





Page 93 of 714



</itinerary><itinerary>



<departurePoint><locationId>MIA</locationId>


<arrivalPointDetails><locationId>NYC</locationId>




<flightDetail><flightType>D</flightType>

</flightDetail></flightInfo>




Invalid Flight CategoryIf an unknown Flight Category is specified in the entry, the entire request is rejected and the followingerror message is returned:

"INVALID FLIGHT CATEGORY"

Invalid Flight CategoryIf an Include Connecting Point is specified at the same time as a Non-Stop Flight Category option, theentire request is rejected and the following error message is returned:

"NON-STOP CANNOT BE REQUESTED WITH CONNECT POINT OPTION"





Page 94 of 714

5.4 Operation: 02.03 Flight Option - Connection PointConnection points must be segment specific. They may be combined with any other option, excluding theNon-Stop flight category - in which, an error message is not returned, but the connection point specified isignored. Connecting points to include may be combined with the connection points to exclude, providing thesame connection points are not used for both categories.

One additional specific combination restriction for preferred connection option: preferred connecting pointoption can be combined with any other option except the Non-Stop flight category option and the preferredairline option.

The connection points are 3-character IATA City or Airport codes. When an include connecting point option isspecified, 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 inthe 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 excludeconnect points are excluded. When two excluded connecting points are specified, any itinerary going throughone 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 systemreturns 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 samecity 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 proposedsegments. Those preferred proposed segments will go via at least one of the preferred connecting pointsrequested. These preferred proposed segments will be considered by the system when building therecommendations. The Change of Gauge and direct flights whose stops are in the requested point are notselected here.

Preferred connecting point can be used to ensure that proposed segments considered by the system whenbuilding recommendations will include online solutions on those connecting points. This option does not ensurethat recommendations returned by Master Pricer will include such proposed segments as the objective is stillto 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 FRAInclude Connecting Point: NYC

Exclude Connecting Point: JFK

Itineraries via, at least, any Airport of NYC exceptJFK

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

Include Connecting Point: LON

Exclude Connecting Point: SIN

Itineraries via, at least, LON and Exclude Direct,Connections and COG that go through SIN





Page 95 of 714

Include Connecting Point: JFK

Exclude Connecting Point: NYC

Entry rejected with the appropriate message

Include Connecting Point: FRA

Type of Flight: Non-Stop

Entry rejected with the appropriate message

Exclude Connecting Point: FRA

Type of Flight: Non-Stop

All Non-Stop from DUS to BER. In that case theExclude connecting point is meaningless

The example below illustrates a low fare search including an optional Connection Point element specified withthe 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





RC





1st Segment departure city PARIS PAR

1st Segment arrival city MIAMI MIA

Trip Date (20 December 2001) 201201

Exclusion indicator X

Location for connection point exclusion LGW

2nd requested segment 2

2nd Segment departure city PARIS MIA

2nd Segment arrival city MIAMI PAR

Trip Date (20 January 2002) 200102

Exclusion indicator X

Location for 1st connection point inclusion NYC





Page 96 of 714

Location for 2nd connection point exclusion LON

Location for preferred connection point JFK



<unitNumberDetail><numberOfUnits>200</numberOfUnits><typeOfUnit>RC</typeOfUnit>






</paxReference><itinerary>

<requestedSegmentRef>

<segRef>1</segRef></requestedSegmentRef><departureLocalization>







<inclusionDetail><inclusionIdentifier>M</inclusionIdentifier><locationId>LGW</locationId>

</inclusionDetail><inclusionDetail>





Page 97 of 714

<inclusionIdentifier>M</inclusionIdentifier><locationId>MAD</locationId>

</inclusionDetail></flightInfo>




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 anExclude Connecting Point and an Airport associated to that city is specified as an Include Connecting Point,the following error message is 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 entirerequest 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 entirerequest 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 entirequery is rejected and the following error message is returned:

"PREFERRED AND INCLUDE/EXCLUDE AIRLINE CANNOT BE MIXED"





Page 98 of 714

5.5 Operation: 02.04 Flight Option - MulticityThe user has the ability to specify alternatives cities or airports as origin and/or destination point of eachrequested 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 requestedsegment.• the multicity option.

When a Multicity option is specified, search is extended to the whole list of cities and airports specified in theentry.

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

Arrival: LON

Search will be done on the following city pairs:

- WAS - LON

- BOS - LON

- NYC - LON

Departure: LON, SOU, GLO

Destination: AMS, EIN, RTM

Search will be done on the following city pairs:

- 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 selectedin 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 99 of 714

Constraint on marketThe 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 requestedpoints (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-PAROnly French cities are processed since therequested journey (according to the first cities, NCE-PAR) is France domestic.

International connecting points (ex: NCE-GVA-PAR)will be considered only if no domestic itinerary exist.

OutboundDeparture: NCE,MIL Arrival: ROMInboundDeparture: ROM Arrival: LON,MIL

Journey is international, as defined by NCE-ROM-LON, the considered cities combinations are thefollowing:- NCE-ROM-LON- MIL-ROM-LON- NCE-ROM-MILMIL-ROM-MIL is not considered

(international connecting journey on domesticrequested points like MIL-GVA-ROM-MIL are notconsidered).

Constraint between Requested Segments

If the requested journey (the journey constructed with the requested point) is Round Trip (RT), only RTitineraries will be processed.





Page 100 of 714

Examples:

Request Process

OutboundDeparture: NCE, MRS, LYS, TLN Arrival: PARInboundDeparture: PAR Arrival: NCE, MRS, LYS, TLN, MPL

The considered cities combinations are the following:- NCE-PAR-NCE- MRS-PAR-MRS- TLN-PAR-TLNNCE-PAR-MRS is not processed since it is not around trip and the requested itinerary is a round trip.

The example below illustrates a low fare search including an optional Multicity element specified with thefollowing information:

Query Requirements:

• 1st segment search multiple departure cities (Paris or Lille) matching multiple arrival cities (FortLauderdale)



# of seats for request 1Request specific maximum number of recommendations to be returned

RC




Applicable 1st segment 1

Multiple departure city 1 of Paris PAR

Multiple departure city 2 of Lille LIL

Multiple arrival city 1 of Miami MIAMultiple arrival city 2 of Fort Lauderdale FLL




<unitNumberDetail><numberOfUnits>1</numberOfUnits>





Page 101 of 714

<typeOfUnit>PX</typeOfUnit></unitNumberDetail><unitNumberDetail>








<depMultiCity><locationId>PAR</locationId>

</depMultiCity><depMultiCity>

<locationId>LIL</locationId></depMultiCity>

</departureLocalization>

<arrivalLocalization><arrivalMultiCity>

<locationId>MIA</locationId></arrivalMultiCity><arrivalMultiCity>

<locationId>FLL</locationId></arrivalMultiCity>



</firstDateTimeDetail>

</timeDetails></itinerary></Fare_MasterPricerTravelBoardSearch>



City/Airports Must be in Same Country





Page 102 of 714

At each Origin/Destination level of each Requested Segments, all Cities and/or Airports must belong tothe same country. If this check fails, the entire entry is rejected with the following error message:

"CITY/AIRPORTS MUST BE IN SAME COUNTRY".





Page 103 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 kilometersmay 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 therequested 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 notinclude MLH)

BSL Basel (airport) - No radius Basel airport

EAP Basel Mulhouse (city) - Radius: 25 km Any airport attached to EAP in Switzerland (does notinclude MLH)

BSL Basel (airport) - Radius: 0 km Any airport attached to EAP in Switzerland (does notinclude 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 areawhose 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 cityare preferred.

Since density and distance are repeated for each city pair, these values may be modified manually to handlespecific 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 notconsidered, since the city of reference is normally always used. However, a manual modification of the densityvalue should allow tuning for specific cases.





Page 104 of 714

When many cities must be considered for both end points of a requested segment, both end point varietymust 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 Process With Example

Departure: NCE and any airport within a radius of 300 km

(=> Considered city order: NCE, MRS, TLN, and soon)

Arrival: PAR

Process in priority solutions:

• 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

(=> Considered city order: NCE, MRS, TLN, and soon)

Arrival: TLS and any Airport within a radius of 300km

(=> Considered city order: TLS, BOD, MPL, and so

on)

Process in priority solutions:

• 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.

The example below illustrates a low fare search including an optional Origin/Destination area element specifiedwith 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.





RC


200






Page 106 of 714

<distanceUnit>K</distanceUnit><locationId>MUC</locationId>


<arrivalPointDetails><distance>100</distance><distanceUnit>K</distanceUnit><locationId>HOU</locationId><airportCityQualifier> A</airportCityQualifier>







<departurePoint><locationId>HOU</locationId>

<airportCityQualifier>C</airportCityQualifier></departurePoint>

</departureLocalization><arrivalLocalization>

<arrivalPointDetails><locationId>MUC</locationId>







Conflicting Multi-City Options





Page 107 of 714

If an Origin/Destination Area option and a Multi-city option are both specified at the same time on the sameOrigin or Destination point, the entire entry is rejected with the following error message:

"CONFLICTING MULTI-CITY OPTIONS".

Conflicting Multi-City OptionsThe radius must be between 0 and 300km. If this check fails, the entire request is rejected with the followingerror message:

"INVALID RADIUS - MAXIMUM ALLOWED 300KM"

Invalid Value - departureLocalization/arrivalLocalizationIf the unit of measure is not specified or is specified as anything other than Kilometers (K), the entire querywill be rejected and depending on whether the radius search was requested on the departure or arrivallocation one of the following applicable error message:

"INVALID VALUE - DEPARTURELOCALIZATION" or "INVALID VALUE - ARRIVALLOCALIZATION"





Page 108 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 withan option in the query.

When this option is requested, Slice and Dice is disabled in the availability request. As no extra availability isreturned, no recommendation with Slice and Dice context will be returned.









</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>







Page 109 of 714














Page 110 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 biasedpreference display setting with an option in the query.

When this option is requested, the flight search request is performed in neutral mode, independently of theoffice settings.











<priceType>RP</priceType><priceType>RW</priceType><priceType>NPF</priceType>











Page 111 of 714














Page 113 of 714

</fareOptions><travelFlightInfo>

<companyIdentity><carrierQualifier>M</carrierQualifier><carrierId>MH</carrierId><carrierId>FD</carrierId>

</companyIdentity></travelFlightInfo><itinerary>



<departurePoint><locationId>HKG</locationId>


<arrivalPointDetails><locationId>HKT</locationId>







<departurePoint><locationId>HKT</locationId>

</departurePoint></departureLocalization>

<arrivalLocalization><arrivalPointDetails><locationId>HKG</locationId>








Page 114 of 714



<Fare_MasterPricerTravelBoardSearchReply xmlns="http://xml.amadeus.com/FMPTBR_16_1_1A" ><replyStatus>

<status><advisoryTypeInfo>FQX</advisoryTypeInfo>

</status></replyStatus><conversionRate>

<conversionRateDetail>

<currency>USD</currency></conversionRateDetail><conversionRateDetail>

<currency>HKD</currency><convertedAmountLink>1</convertedAmountLink>

</conversionRateDetail></conversionRate><flightIndex>


</requestedSegmentRef><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>

<locationId>HKG</locationId>





Page 115 of 714

<terminal>2</terminal></location><location>

<locationId>HKT</locationId><terminal>1</terminal>

</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>


<ref>2</ref>




<ref>MH</ref><unitQualifier>MCX</unitQualifier>


<flightInformation>

<productDateTime><dateOfDeparture>280615</dateOfDeparture><timeOfDeparture>0845</timeOfDeparture><dateOfArrival>280615</dateOfArrival><timeOfArrival>1230</timeOfArrival>


<locationId>HKG</locationId><terminal>1</terminal>

</location>





Page 116 of 714

<location><locationId>KUL</locationId><terminal>M</terminal>


<marketingCarrier>MH</marketingCarrier><operatingCarrier>MH</operatingCarrier>



<electronicTicketing>Y</electronicTicketing><productDetailQualifier>LCA</productDetailQualifier>


</flightDetails><flightDetails>




<locationId>KUL</locationId><terminal>M</terminal>

</location><location>












Page 117 of 714

</flightDetails></groupOfFlights>

</flightIndex><flightIndex>







<ref>FD</ref><unitQualifier>MCX</unitQualifier>



<dateOfDeparture>020715</dateOfDeparture>

<timeOfDeparture>1605</timeOfDeparture><dateOfArrival>020715</dateOfArrival><timeOfArrival>2035</timeOfArrival>





</location>

<companyId><marketingCarrier>FD</marketingCarrier><operatingCarrier>FD</operatingCarrier>



<electronicTicketing>N</electronicTicketing>





Page 118 of 714

<productDetailQualifier>LCA</productDetailQualifier></addProductDetail>

</flightInformation></flightDetails>

</groupOfFlights><groupOfFlights>





<ref>MH</ref><unitQualifier>MCX</unitQualifier>



<dateOfDeparture>020715</dateOfDeparture><timeOfDeparture>1405</timeOfDeparture><dateOfArrival>020715</dateOfArrival>

<timeOfArrival>1635</timeOfArrival></productDateTime><location>





<marketingCarrier>MH</marketingCarrier>

<operatingCarrier>MH</operatingCarrier></companyId><flightOrtrainNumber>795</flightOrtrainNumber><productDetail>



</addProductDetail>





Page 119 of 714

</flightInformation></flightDetails><flightDetails>










<equipmentType>738</equipmentType>

</productDetail><addProductDetail>




</flightIndex><recommendation>


<number>1</number></itemNumberId><priceTicketing>

<priceType>L</priceType></priceTicketing>

</itemNumber><recPriceInfo>

<monetaryDetail><amountType>CR</amountType><amount>266.00</amount>





Page 120 of 714

</monetaryDetail><monetaryDetail>

<amountType>R</amountType><amount>1992</amount>

</monetaryDetail></recPriceInfo><segmentFlightRef>

<referencingDetail><refQualifier>C</refQualifier><refNumber>1</refNumber>

</referencingDetail></segmentFlightRef><segmentFlightRef>




</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>



</paxReference><fare><pricingMessage>

<freeTextQualification><textSubjectQualifier>LTD</textSubjectQualifier><informationType>43</informationType>

</freeTextQualification><description>LAST TKT DTE</description><description>28JUN15</description><description> - FARE DISC THIS DATE</description>





Page 121 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>




<rbd>Z</rbd><cabin>C</cabin><avlStatus>9</avlStatus>

</cabinProduct><fareProductDetail><fareBasis>Z</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>







Page 122 of 714

<bookingClassDetails><designator>C</designator>

</bookingClassDetails></majCabin>

</fareDetails></paxFareProduct>

</recommendation><recommendation>




<monetaryDetail><amount>430.02</amount>


<amount>175.02</amount></monetaryDetail>

</recPriceInfo><segmentFlightRef>





<paxFareDetail><paxFareNum>1</paxFareNum><totalFareAmount>430.02</totalFareAmount><totalTaxAmount>175.02</totalTaxAmount><codeShareDetails>

<transportStageQualifier>V</transportStageQualifier><company>MH</company></codeShareDetails>

</paxFareDetail><paxReference>



</paxReference>





Page 123 of 714

<fare><pricingMessage>

<freeTextQualification><textSubjectQualifier>PEN</textSubjectQualifier><informationType>73</informationType>

</freeTextQualification><description>PENALTY APPLIES</description>

</pricingMessage><monetaryInformation>

<monetaryDetail><amountType>MT</amountType><amount>77.00</amount><currency>USD</currency>

</monetaryDetail></monetaryInformation>

</fare><fare>

<pricingMessage><freeTextQualification>

<textSubjectQualifier>LTD</textSubjectQualifier><informationType>41</informationType>

</freeTextQualification><description>LAST TKT DTE</description><description>28JUN15</description><description> - DATE OF ORIGIN</description>





<rbd>Q</rbd><cabin>M</cabin><avlStatus>9</avlStatus>

</cabinProduct><fareProductDetail><fareBasis>QBC3MHK</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

</fareProductDetail><breakPoint>N</breakPoint>

</productInformation></groupOfFares><groupOfFares>





Page 124 of 714


<rbd>L</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>QBC3MHK</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>



<bookingClassDetails><designator>M</designator>


</fareDetails><fareDetails>
















Page 125 of 714







</recommendation></Fare_MasterPricerTravelBoardSearchReply>






Page 126 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 Accesscarriers 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.



<unitNumberDetail>






<ref>1</ref>

</traveller><traveller>








</traveller></paxReference><fareOptions>


<priceType>XLC</priceType></pricingTicketing>





Page 127 of 714

</pricingTickInfo></fareOptions><itinerary>





<arrivalMultiCity><locationId>NYC</locationId>

</arrivalMultiCity></arrivalLocalization><timeDetails>










Page 128 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 areconsidered as available.




<typeOfUnit>PX</typeOfUnit></unitNumberDetail>

</numberOfUnit><fareOptions>


<priceType>IAV</priceType></pricingTicketing>




<departurePoint><locationId>LON</locationId>












Page 129 of 714






Page 130 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 consideredin 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 withthe following information.

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








<flightDetail><flightType>N</flightType><flightType>D</flightType>











Page 131 of 714













<unitNumberDetail><numberOfUnits>2</numberOfUnits><typeOfUnit>C</typeOfUnit>

</unitNumberDetail></flightInfo>








Page 132 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><paxReference>




</paxReference>

<travelFlightInfo><flightDetail>

<flightType>OL</flightType></flightDetail><unitNumberDetail>

<numberOfUnits>2</numberOfUnits><typeOfUnit>C</typeOfUnit>

</unitNumberDetail></travelFlightInfo><itinerary>



<departurePoint><locationId>BIQ</locationId>


<arrivalPointDetails><locationId>LON</locationId>

</arrivalPointDetails></arrivalLocalization>





Page 133 of 714

<timeDetails><firstDateTimeDetail>

<date>151010</date></firstDateTimeDetail>

</timeDetails></itinerary><itinerary>





<arrivalPointDetails><locationId>BIQ</locationId>







• If at the same level, the Online option is combined with the Include Airline option used on YY airlinecode: 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 solutionsof those specifics airlines).





Page 134 of 714

5.14 Operation: 02.12 Flight Option - Online Option at Requested SegmentLevel

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







<ref>2</ref>

</traveller></paxReference><itinerary>



<departurePoint><locationId>BIQ</locationId>






<flightDetail>





Page 135 of 714

<flightType>OL</flightType></flightDetail>

</flightInfo></itinerary><itinerary>





<arrivalPointDetails><locationId>BIQ</locationId>







See "Error Messages" section.





Page 136 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 marketedby different carriers.










<priceType>INL</priceType></pricingTicketing>














Page 137 of 714









Page 138 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 apercentage (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 isrequested at itinerary level.










<unitNumberDetail><numberOfUnits>120</numberOfUnits><typeOfUnit>P</typeOfUnit>












Page 139 of 714



</timeDetails></itinerary>

</Fare_MasterPricerTravelBoardSearch>








Page 140 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.


<Fare_MasterPricerTravelBoardSearch xmlns="http://xml.amadeus.com/FMPTBQ_16_1_1A" >

<numberOfUnit><unitNumberDetail>





</paxReference>

<travelFlightInfo><unitNumberDetail>

<numberOfUnits>5</numberOfUnits><typeOfUnit>MLH</typeOfUnit>


<numberOfUnits>30</numberOfUnits><typeOfUnit>MLM</typeOfUnit>







</arrivalPointDetails>





Page 141 of 714












Page 142 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 beyondat 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 thespecified requested segment.

In the example below, it is applied at itinerary level.








<unitNumberDetail><numberOfUnits>5</numberOfUnits><typeOfUnit>MSH</typeOfUnit>


<numberOfUnits>30</numberOfUnits><typeOfUnit>MSM</typeOfUnit>











Page 143 of 714












Page 144 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.








</paxReference>

<fareOptions><pricingTickInfo>

<pricingTicketing><priceType>RDI</priceType>

</pricingTicketing></pricingTickInfo>




<departurePoint><distance>300</distance><distanceUnit>K</distanceUnit><locationId>MUC</locationId>


<arrivalPointDetails><locationId>CPH</locationId>






Page 145 of 714












Page 146 of 714

5.20 Operation: 02.18 Flight option - IR: Radius/multicity at requestedsegment levelThe search on a radius is extended to all cities/airports of any country for any requested points with the crossborder option and to all cities/airports in the same country as the city/airport of reference for requested pointswithout 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.










<departurePoint><distance>300</distance><distanceUnit>K</distanceUnit><locationId>MUC</locationId>

</departurePoint><attributeDetails>

<type>IR</type></attributeDetails>


<arrivalPointDetails><locationId>CPH</locationId>







Page 147 of 714






</status></replyStatus>

<conversionRate><conversionRateDetail>

<currency>EUR</currency></conversionRateDetail>

</conversionRate><flightIndex>







<ref>SK</ref><unitQualifier>MCX</unitQualifier>





<locationId>STR</locationId><terminal>1</terminal>

</location>





Page 148 of 714

<location><locationId>CPH</locationId><terminal>3</terminal>


<marketingCarrier>SK</marketingCarrier><operatingCarrier>SK</operatingCarrier>


<equipmentType>CR9</equipmentType></productDetail><addProductDetail>

<electronicTicketing>Y</electronicTicketing><productDetailQualifier> AVR</productDetailQualifier>







<ref>BT</ref><unitQualifier>MCX</unitQualifier>






<locationId>PRG</locationId><terminal>2</terminal>


<locationId>RIX</locationId>





Page 149 of 714


<marketingCarrier>BT</marketingCarrier><operatingCarrier>BT</operatingCarrier>


<equipmentType>DH4</equipmentType></productDetail><addProductDetail>







<locationId>RIX</locationId>


<locationId>CPH</locationId><terminal>2</terminal>


<marketingCarrier>BT</marketingCarrier><operatingCarrier>BT</operatingCarrier>


<equipmentType>DH4</equipmentType>

</productDetail><addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier> AVR</productDetailQualifier>



<propFlightGrDetail>





Page 150 of 714

<flightProposal><ref>3</ref>




<ref> AB</ref><unitQualifier>MCX</unitQualifier>





<locationId>NUE</locationId></location><location>

<locationId>DUS</locationId>


<marketingCarrier> AB</marketingCarrier><operatingCarrier> AB</operatingCarrier>


<equipmentType>DH4</equipmentType></productDetail><addProductDetail>


</addProductDetail></flightInformation></flightDetails><flightDetails>







Page 151 of 714


<locationId>DUS</locationId></location><location>



<marketingCarrier> AB</marketingCarrier><operatingCarrier> AB</operatingCarrier>











<ref>IB</ref><unitQualifier>MCX</unitQualifier>

</flightProposal></propFlightGrDetail>

<flightDetails><flightInformation><productDateTime>



<locationId>ZRH</locationId>





Page 152 of 714

<terminal>B</terminal></location><location>

<locationId>BCN</locationId><terminal>1</terminal>


<marketingCarrier>IB</marketingCarrier><operatingCarrier>VY</operatingCarrier>







<dateOfDeparture>011214</dateOfDeparture><timeOfDeparture>1215</timeOfDeparture>

<dateOfArrival>011214</dateOfArrival><timeOfArrival>1515</timeOfArrival>






<marketingCarrier>IB</marketingCarrier><operatingCarrier>VY</operatingCarrier></companyId><flightOrtrainNumber>5423</flightOrtrainNumber><productDetail>







Page 153 of 714







<ref>VY</ref><unitQualifier>MCX</unitQualifier>





<locationId>ZRH</locationId><terminal>B</terminal>




<marketingCarrier>VY</marketingCarrier><operatingCarrier>VY</operatingCarrier>









Page 154 of 714











<equipmentType>320</equipmentType></productDetail>

<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier> AVR</productDetailQualifier>





<number>1</number>

</itemNumberId></itemNumber><recPriceInfo>




</recPriceInfo>





Page 155 of 714

<segmentFlightRef><referencingDetail>




<transportStageQualifier>V</transportStageQualifier><company>SK</company>

</codeShareDetails><pricingTicketing>

<priceType>OBV</priceType></pricingTicketing>




</paxReference>



</freeTextQualification><description>TICKETS ARE NON-REFUNDABLE</description>

</pricingMessage></fare><fare>


<textSubjectQualifier>LTD</textSubjectQualifier><informationType>45</informationType></freeTextQualification><description>LAST TKT DTE</description><description>25JUL14</description>







Page 157 of 714


<transportStageQualifier>V</transportStageQualifier><company>BT</company>




</paxReference><fare>


<textSubjectQualifier>PEN</textSubjectQualifier><informationType>70</informationType>





</freeTextQualification><description>LAST TKT DTE</description><description>25JUL14</description>




<productInformation><cabinProduct><rbd>K</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>KCZTH9</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>





Page 158 of 714




<rbd>K</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>KCZTH9</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>





</fareDetails>

</paxFareProduct></recommendation><recommendation>





</monetaryDetail>

<monetaryDetail><amount>116.21</amount></monetaryDetail>








Page 159 of 714

<paxFareProduct><paxFareDetail>

<paxFareNum>1</paxFareNum><totalFareAmount>118.21</totalFareAmount><totalTaxAmount>116.21</totalTaxAmount><codeShareDetails>

<transportStageQualifier>V</transportStageQualifier><company> AB</company>









</freeTextQualification>

<description>TICKETS ARE NON-REFUNDABLE</description></pricingMessage>

</fare><fare>




</pricingMessage>

</fare><fareDetails><segmentRef>

<segRef>1</segRef></segmentRef><groupOfFares>


<rbd>W</rbd><cabin>M</cabin>





Page 160 of 714

<avlStatus>4</avlStatus></cabinProduct><fareProductDetail>

<fareBasis>WNCOW</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




<rbd>W</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>WNCOW</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>


</productInformation></groupOfFares>

<majCabin><bookingClassDetails>

<designator>M</designator></bookingClassDetails>

</majCabin></fareDetails>



<number>4</number>





</recPriceInfo>





Page 161 of 714





<transportStageQualifier>V</transportStageQualifier><company>IB</company>






</paxReference>






<textSubjectQualifier>LTD</textSubjectQualifier><informationType>45</informationType></freeTextQualification><description>LAST TKT DTE</description><description>24JUL14</description>







Page 162 of 714



<rbd>P</rbd><cabin>M</cabin><avlStatus>4</avlStatus>


<fareBasis>PRTNVY</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






<fareBasis>QRTNVY</fareBasis>

<passengerType> ADT</passengerType><fareType>RP</fareType>





</fareDetails>





<monetaryDetail>





Page 163 of 714

<amount>151.52</amount></monetaryDetail><monetaryDetail>






<transportStageQualifier>V</transportStageQualifier><company>VY</company>

</codeShareDetails><codeShareDetails>

<company>HR</company></codeShareDetails>

</paxFareDetail>

<paxReference><ptc> ADT</ptc><traveller>






<description>PENALTY APPLIES</description></pricingMessage><monetaryInformation>

<monetaryDetail><amountType>MT</amountType><amount>45.00</amount><currency>EUR</currency>


</fare>





Page 164 of 714










<fareBasis>PRTVY</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






<fareBasis>WRTVY</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>








Page 166 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 multi-airports cities indicated in the query.










<typeOfUnit>NAC</typeOfUnit></unitNumberDetail>

</travelFlightInfo><itinerary>









</itinerary>





Page 167 of 714








Page 168 of 714

5.22 Operation: 02.21 Flight option - No airport change at requested segmentlevel

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



<unitNumberDetail>














<unitNumberDetail><numberOfUnits>1</numberOfUnits><typeOfUnit>NAC</typeOfUnit>

</unitNumberDetail></flightInfo>





Page 169 of 714








Page 170 of 714

5.23 Operation: 02.22 Duplicated recommendations: Keep solutions withmore 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 onlyhave 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 pricethan at least one duplicate recommendation (feeder).









<priceType>RDG</priceType></pricingTicketing>





</departurePoint>





Page 171 of 714













Page 172 of 714

5.24 Operation: 02.23 Duplicated recommendations: Keep the best solutionsper 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 onlyhave one differentiable segment.• their differentiable segments have: same routing, same marketing carrier combination, and a samemajor 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 worsequality 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 pricethan at least one duplicate recommendation (feeder).










<priceType>RDM</priceType></pricingTicketing>









Page 173 of 714













Page 174 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 thesearch.



<unitNumberDetail>






<inclusionDetail>

<inclusionIdentifier>M</inclusionIdentifier><locationId>LAX</locationId><airportCityQualifier>C</airportCityQualifier>

</inclusionDetail></travelFlightInfo><itinerary>



<depMultiCity><locationId>PAR</locationId>


<arrivalMultiCity><locationId>MIA</locationId>








Page 176 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 morerequested segments by providing, for all the anchored requested segments, the following initial travel solutioninformations :

• 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











<priceType>RU</priceType><priceType>RP</priceType>





Page 177 of 714

<priceType> ACS</priceType></pricingTicketing>




<departurePoint><locationId>NCE</locationId>


<arrivalPointDetails><locationId>PAR</locationId>



</firstDateTimeDetail></timeDetails><requestedSegmentAction>

<actionRequestCode>MF</actionRequestCode>

</requestedSegmentAction></itinerary><itinerary>





<arrivalPointDetails><locationId>NCE</locationId></arrivalPointDetails>



</firstDateTimeDetail></timeDetails><flightInfoPNR>





Page 178 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>








Page 179 of 714

5.27 Operation: 02.26 Flight Option - Anchored Search (Full mode withouttechnical stop)When FSParam Gb_AnchoredSearch is set to 1, the user has the possibility to freeze one or morerequested segments by providing, for all the anchored requested segments, the following initial travel solutioninformations, in addition of the information required 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

The example below illustrates the following request:

Mandatory elements:

Parameter Value

Arrival date 20141020

Arrival time 0800

Date variation indicator 0

Aircraft type 320

EFT of the proposed segment 80

Required elements:

Parameter Value

Operating carrier AF

Operational suffix A

Flight portion type E

Elapsed flying time of the flight 80

Terminal of origin W

Terminal of destination 2







Page 181 of 714






<arrivalPointDetails><locationId>NCE</locationId>





<departureDate>20141020</departureDate><departureTime>0640</departureTime>

<arrivalDate>20141020</arrivalDate><arrivalTime>0800</arrivalTime><dateVariation>0</dateVariation>


<trueLocationId>ORY</trueLocationId></boardPointDetails><offpointDetails>

<trueLocationId>NCE</trueLocationId></offpointDetails><companyDetails>

<marketingCompany> AF</marketingCompany>

</companyDetails><flightIdentification><flightNumber>6240</flightNumber><operationalSuffix> A</operationalSuffix>

</flightIdentification><flightTypeDetails>

<flightIndicator>S</flightIndicator></flightTypeDetails>

</travelResponseDetails><terminalEquipmentDetails>





Page 182 of 714

<legDetails><equipment>320</equipment><duration>80</duration>

</legDetails><departureStationInfo>

<terminal>W</terminal></departureStationInfo><arrivalStationInfo>

<terminal>2</terminal></arrivalStationInfo>

</terminalEquipmentDetails><terminalEquipmentDetails>

<legDetails><duration>80</duration>

</legDetails></terminalEquipmentDetails><codeshareData>

<codeshareDetails><transportStageQualifier>O</transportStageQualifier><airlineDesignator> AF</airlineDesignator>

</codeshareDetails></codeshareData>

</flightInfoPNR></itinerary>








Page 183 of 714

5.28 Operation: 02.27 Flight Option - Anchored Search (Full mode withtechnical 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

The example below illustrates the following request: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
















Page 184 of 714

<priceType> ACS</priceType></pricingTicketing>




<departurePoint><locationId>CHC</locationId>


<arrivalPointDetails><locationId>MUC</locationId>




<travelResponseDetails>

<flightDate><departureDate>20141015</departureDate><departureTime>0645</departureTime><arrivalDate>20141015</arrivalDate><arrivalTime>0745</arrivalTime><dateVariation>0</dateVariation>


<trueLocationId>CHC</trueLocationId></boardPointDetails><offpointDetails>

<trueLocationId>BNE</trueLocationId>

</offpointDetails><companyDetails><marketingCompany>EY</marketingCompany>

</companyDetails><flightIdentification>

<flightNumber>6728</flightNumber></flightIdentification><flightTypeDetails>

<flightIndicator>S</flightIndicator><flightIndicator>ET</flightIndicator>





Page 185 of 714

</flightTypeDetails></travelResponseDetails><terminalEquipmentDetails>

<legDetails><equipment>73H</equipment>

</legDetails></terminalEquipmentDetails><terminalEquipmentDetails>

<legDetails><duration>2095</duration>

</legDetails></terminalEquipmentDetails><codeshareData>

<codeshareDetails><transportStageQualifier>O</transportStageQualifier><airlineDesignator>VA</airlineDesignator>


</flightInfoPNR><flightInfoPNR>


<departureDate>20141015</departureDate><departureTime>1245</departureTime><arrivalDate>20141015</arrivalDate>

<arrivalTime>2345</arrivalTime><dateVariation>0</dateVariation>


<trueLocationId>BNE</trueLocationId></boardPointDetails><offpointDetails>

<trueLocationId> AUH</trueLocationId></offpointDetails><companyDetails>

<marketingCompany>EY</marketingCompany></companyDetails>

<flightIdentification><flightNumber>473</flightNumber></flightIdentification><flightTypeDetails>

<flightIndicator>C</flightIndicator><flightIndicator>ET</flightIndicator>


<legDetails>





Page 186 of 714

<equipment>332</equipment></legDetails><mileageTimeDetails>

<elapsedGroundTime>0500</elapsedGroundTime></mileageTimeDetails>

</terminalEquipmentDetails><codeshareData>

<codeshareDetails><transportStageQualifier>O</transportStageQualifier><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>


<departureDate>20141016</departureDate><departureTime>0210</departureTime><arrivalDate>20141016</arrivalDate><arrivalTime>0640</arrivalTime><dateVariation>0</dateVariation>

</flightDate><boardPointDetails><trueLocationId> AUH</trueLocationId>

</boardPointDetails><offpointDetails>

<trueLocationId>MUC</trueLocationId></offpointDetails><companyDetails>

<marketingCompany>EY</marketingCompany></companyDetails>





Page 187 of 714

<flightIdentification><flightNumber>5</flightNumber>

</flightIdentification><flightTypeDetails>

<flightIndicator>E</flightIndicator><flightIndicator>ET</flightIndicator>


<legDetails><equipment>346</equipment>

</legDetails><mileageTimeDetails>

<elapsedGroundTime>0225</elapsedGroundTime></mileageTimeDetails>

</terminalEquipmentDetails><codeshareData>

<codeshareDetails><transportStageQualifier>O</transportStageQualifier><airlineDesignator>EY</airlineDesignator>


</flightInfoPNR></itinerary><itinerary>



<departurePoint><locationId>MUC</locationId>


<arrivalPointDetails><locationId>CHC</locationId>


</arrivalLocalization><timeDetails><firstDateTimeDetail>


</timeDetails><requestedSegmentAction>

<actionRequestCode>MF</actionRequestCode></requestedSegmentAction>

</itinerary>





Page 188 of 714








Page 189 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. Overnightsolutions are solutions with a segment containing a connection with first flight arriving before or at 11:59 PMand second flight starting after or at 5:00 AM.



<unitNumberDetail>






<pricingTickInfo>

<pricingTicketing><priceType>OVN</priceType>





<departurePoint><locationId>BOS</locationId>


<arrivalPointDetails><locationId>GRX</locationId>








Page 190 of 714




<departurePoint><locationId>GRX</locationId>


<arrivalPointDetails><locationId>BOS</locationId>











Page 191 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 solutionson 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 thepossibility 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

DOCDate of commencement (1 April 2015)

010415










<priceType>RP</priceType><priceType>RU</priceType>

</pricingTicketing><journeyOriginPoint>

<locationId>NCE</locationId></journeyOriginPoint>

</pricingTickInfo><feeIdDescription>





Page 192 of 714

<feeId><feeType>DOC</feeType><feeIdNumber>010415</feeIdNumber>

</feeId></feeIdDescription>




<departurePoint><locationId>NYC</locationId>













Page 193 of 714

5.31 Operation: 02.30 Flight Option - Search with CLIDThe corporate recognition is used to identify corporate traveller that travels for business reasons and who canbenefit from special contracts linked to a corporate account. Airlines are able to provide enhanced availabilityfor certain corporate customer. Such biased availability computation relies on the CLID number, a unique IDnumber by carrier.The example below illustrates a Search with a CLID number. Each CLID is described with a company codeand a corporate identifier.



# of seats for request 1 Adult Passenger type code ADT


Include public fares in the search RP

Include unifares in the search RU

LH

C100107371656

Client ID carrier and number

2

Applicable 1st requested segment 1

Departure city of Frankfurt FRA

Arrival city of New York NYC

Trip Date (22 June 2014) 220614

Applicable 2nd requested segment 2

Departure city of New York NYC

Arrival city of Frankfurt FRA

Trip Date (6 July 2014) 060714






<ref>1</ref>





Page 194 of 714




</pricingTicketing></pricingTickInfo><frequentTravellerInfo>

<frequentTravellerDetails><carrier>LH</carrier><number>C100107371656</number><type>2</type>

</frequentTravellerDetails></frequentTravellerInfo>




<departurePoint><locationId>FRA</locationId>

</departurePoint>






</itinerary>

<itinerary><requestedSegmentRef><segRef>2</segRef>








Page 195 of 714

<arrivalPointDetails><locationId>FRA</locationId>





5.31.2 Reply Structure<Fare_MasterPricerTravelBoardSearchReply xmlns="http://xml.amadeus.com/FMPTBR_16_1_1A" >

<replyStatus><status>

<advisoryTypeInfo>FQX</advisoryTypeInfo></status>

</replyStatus><conversionRate>

<conversionRateDetail><currency>EUR</currency>

</conversionRateDetail></conversionRate>

<flightIndex><requestedSegmentRef>

<segRef>1</segRef></requestedSegmentRef><groupOfFlights>





<ref> AF</ref><unitQualifier>MCX</unitQualifier>



<dateOfDeparture>220614</dateOfDeparture><timeOfDeparture>1345</timeOfDeparture>





Page 196 of 714

<dateOfArrival>220614</dateOfArrival><timeOfArrival>1636</timeOfArrival>


<locationId>FRA</locationId><terminal>2</terminal>


<locationId>JFK</locationId><terminal>4</terminal>


<marketingCarrier> AF</marketingCarrier><operatingCarrier>DL</operatingCarrier>


<equipmentType>76W</equipmentType></productDetail><addProductDetail>



</flightDetails>

</groupOfFlights></flightIndex><flightIndex>





<ref>0808</ref><unitQualifier>EFT</unitQualifier></flightProposal><flightProposal>



<flightInformation>





Page 197 of 714

<productDateTime><dateOfDeparture>060714</dateOfDeparture><timeOfDeparture>2012</timeOfDeparture><dateOfArrival>070714</dateOfArrival><timeOfArrival>1020</timeOfArrival><dateVariation>1</dateVariation>






<marketingCarrier> AF</marketingCarrier><operatingCarrier>DL</operatingCarrier>



<electronicTicketing>Y</electronicTicketing>



</groupOfFlights></flightIndex><recommendation>



</itemNumber>

<recPriceInfo><monetaryDetail><amount>560.63</amount>




<referencingDetail>





Page 198 of 714






<transportStageQualifier>V</transportStageQualifier><company> AF</company>


<priceType>OBF</priceType><priceType>OBA</priceType><priceType>OBV</priceType>

</pricingTicketing></paxFareDetail><paxReference>

<ptc> ADT</ptc>

<traveller><ref>1</ref>

</traveller></paxReference><fare>




</pricingMessage>

</fare><fare><pricingMessage>


</freeTextQualification><description>LAST TKT DTE*26FEB14* - SEE ADV PURCHASE</description>

</pricingMessage></fare>





Page 199 of 714

<fareDetails><segmentRef>



<rbd>V</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>VKPR0DE</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>


</productInformation><ticketInfos>

<additionalFareDetails><ticketDesignator>JUX31</ticketDesignator>

</additionalFareDetails></ticketInfos>

</groupOfFares></fareDetails>

<fareDetails><segmentRef>





<fareBasis>VKPR0DE</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>



<additionalFareDetails><ticketDesignator>JUX31</ticketDesignator>

</additionalFareDetails>





Page 200 of 714

</ticketInfos></groupOfFares>








Page 201 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 manydifferent corporations / customers and may wish to apply certain business rules when making travelarrangements for these customers.

These "business rules" can be taken into consideration and validated by Amadeus when returning FareShopping results - provided that the specific customer / rule to apply (if any) has been identified in the inputmessage received from the agency. This identification is made via the "DK" number / customer identificationnumber received.






<ref>1</ref>

</traveller></paxReference><customerRef>

<customerReferences><referenceQualifier>701</referenceQualifier><referenceNumber> AA1234567890123456789Z01234567890</referenceNumber>

</customerReferences></customerRef><itinerary>





<arrivalPointDetails><locationId>PPT</locationId>






Page 202 of 714






<departurePoint><locationId>PPT</locationId>






</itinerary>








Page 203 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 minimumconnections 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 atitinerary level.

The example below illustrates a search with progressive legs range specified at itinerary level.

Requesting Details Specified Data


Number of seats for request 1

Adult passenger type code ADT

Passenger type code applicable to 1st passenger 1Public fares requested RP

0

MIC

1

Progressive legs range with a minimum of 0 connection and amaximum of 1 connection

MAC


Departure city of Denver DEN

Arrival city of Los Angeles LAX

Trip Date (11 December 2015) 1112152 nd requested segment 2

Departure city of Los Angeles LAX

Arrival city of Boston BOS






Page 204 of 714









<priceType>RP</priceType></pricingTicketing>

</pricingTickInfo></fareOptions><travelFlightInfo>

<unitNumberDetail>

<numberOfUnits>0</numberOfUnits><typeOfUnit>MIC</typeOfUnit>


<numberOfUnits>1</numberOfUnits><typeOfUnit>MAC</typeOfUnit>




<departurePoint><locationId>DEN</locationId>


<arrivalPointDetails><locationId>LAX</locationId>






Page 205 of 714






<departurePoint><locationId>LAX</locationId>






</itinerary>








Page 206 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 arange of dates is requested, the TD applies on the first day of the range. The search for flights applies for theperiod between the TD on the first day of the range and 23h59 on the last day of the range like it is describedin 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 arange of dates is requested, search for flights that arrive on the last day of the date range before the requestedtime, or any time the previous day(s).

Examples:

Request Process

Date: 10SEP01

Time of Arrival: 10:00PM

=> Arrives by 10:00PM on the 10SEP01

Select flights that arrive between 00:00AM and10:00PM on the 10SEP01.

Date: 15OCT01

Time of Departure: 10:00PM

=> Depart from 10:00PM on the 15OCT01

Select flights that arrive between 10:00PM and

11:59PM 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 and11:59PM on the 23AUG01 or on the 24AUG01, atany time.



=> Arrive by 06:00PM on the 24AUG01

Select flights that arrive between on 23AUG01 at anytime or on 24AUG before 06:00PM.

The example below illustrates a low fare search including the Times by Arrival and Departure elements specifiedwith the following information.

Query Requirements:

• Departure from origin by 6pm on 23AUG01








Page 207 of 714


RC


200




Departure city of Paris PAR

Arrival city of Miami MIA

Identify search for departure by element TDSpecify date for departure by 23 August 2001 230801

Specify search time for departure by 6pm 1800




</unitNumberDetail>















Page 208 of 714


<firstDateTimeDetail><timeQualifier>TD</timeQualifier><date>200206</date><time>1800</time>





Invalid Time OptionThe 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 Timeof Arrival• If no time is specified after the Time of Departure or the Time of Arrival indicator





Page 209 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 theflights 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 dayto 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


Time Window: 4 hours

=> Arrive around 10:00PM on the 20AUG01

Select flights that arrive between 20AUG01 6:00PMand 21AUG01 02:00AM

Range of dates: 20SEP01 and 21SEP01

Time of Departure: 10:00AM


=> Depart around 10:00AM on the 20SEP01 or onthe 21SEP01

Select flights that depart between 05:00AM and03:00PM on each requested day (20SEP01 and

21SEP01).




=> Arrive around 10:00PM on the 23AUG01 or onthe 24AUG01

Select flights that arrive on 23AUG01 or on24AUG01: between 6:00PM 23AUG01 and 02:00AMon the 24AUG01

Or:

between 6:00PM and 11:59PM on the 24AUG01

NB: Flights between 00:00AM and 02:00AM on the23AUG01 are not considered.


Time of Departure: 02:00AM


=> Depart around 02:00AM on the 23AUG01 or onthe 24AUG01

Select flights that depart on 23AUG01 or on24AUG01: between 00:00AM and 06:00AM on23AUG01

Or:

between 10:00PM on 23AUG01 and 06:00 AM on24AUG01





Page 210 of 714

NB: Flights between 10:00PM and 11:59PM on the24AUG01 are not considered.

The example below illustrates a low fare search including the Times by Arrival and Departure elements specifiedwith 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.





RC


200






Identify time by arrival TA

Specify arrival date by 23AUG01 230801

Specify arrival time by 10pm 2200

Specify applicable time window 4 hours either side of 10pm

4

Identify date range search for Plus P

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 10pm

4

Identify date range search for Minus M

Number of days in date range search 1







Page 211 of 714













<arrivalLocalization><arrivalPointDetails>

<locationId>MIA</locationId></arrivalPointDetails>


<firstDateTimeDetail><timeQualifier>TA</timeQualifier><date>230801</date><time>2200</time><timeWindow>4</timeWindow>


<rangeOfDate><rangeQualifier>M</rangeQualifier><dayInterval>1</dayInterval>

</rangeOfDate></timeDetails>







Page 212 of 714


Invalid Time Window OptionThe time window value varies from 1 to 12 hours. If this check fails, the entire entry is rejected with thefollowing message:

"INVALID TIME WINDOW OPTION"

Time of Departure/Arrival is Mandatory if Time Window RequestedIf 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 MandatoryIf no date is specified, the entire request is rejected with the following error message:

"DATE IS MANDATORY"





Page 214 of 714

Arrival date 22Mar2002 220302

Identify date range search as Minus M

Number of days in range 1




</unitNumberDetail>








<departurePoint><locationId>MRS</locationId>


<arrivalPointDetails><locationId>HOU</locationId>



</firstDateTimeDetail><rangeOfDate>

<rangeQualifier>P</rangeQualifier><dayInterval>1</dayInterval>


</itinerary>





Page 215 of 714

<itinerary><requestedSegmentRef>


<departurePoint><locationId>HOU</locationId>


<arrivalPointDetails><locationId>MRS</locationId>




<rangeQualifier>M</rangeQualifier><dayInterval>1</dayInterval>





Invalid Range of Dates OptionSearch is only allowed on a Range of two days: meaning, the requested Date plus or minus 1 day. If aplus or minus more than 1 day option is specified or if a plus and minus one day option is specified, theentire entry is rejected with the following error message:

"INVALID RANGE OF DATES OPTION".





Page 216 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 theminimum 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 consecutiveproposed segments. This minimum time is specified in input with the following format HHMM. Any valuebetween 0000 and 2359 is accepted.

The example below describes a departure on 20 Dec 2010 with a minimum stay of 5 hours at destination.






<ref>1</ref>










<arrivalPointDetails><locationId>ISB</locationId>






Page 217 of 714




<timeAtdestination>0500</timeAtdestination></rangeOfDate>




<departurePoint><locationId>ISB</locationId>














Page 218 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 ismandatory for any query including the currency conversion option.

It is mandatory that a currency code be specified for the conversion. All price amounts for recommendationsare 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 specifiedwith the following information.

Query Requirements:• Currency to be returned: EUROS





RC




Currency Override CUC

Currency requested for recommendations is Euros EUR


Trip departure city of Paris PAR

Trip arrival city of Miami MIA

Trip date (20 January 2006) 200106






</unitNumberDetail>





Page 219 of 714






<priceType>CUC</priceType></pricingTicketing>

</pricingTickInfo><conversionRate>






<departurePoint>

<locationId>PAR</locationId></departurePoint>









Invalid Currency Conversion





Page 221 of 714

5.39 Operation: 04.02 Fare Option - Selling Ticketing Cities OverrideThe requested selling and/or a ticketing cities are used to determine applicable fares and currency for therecommendations. 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 beutilised, 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 optionsmay be combined together and/or with any other option.The example below illustrates a low fare search including the optional selling/ticketing cities override elementspecified with the following information.

Query Requirements:• Selling city is PAR• Ticketing city is PAR





RC


200



Selling city override location set to Paris PAR

Ticketing city override location set to Paris PAR


Departure city of Marseille MRS










Page 222 of 714

<typeOfUnit>PX</typeOfUnit></unitNumberDetail><unitNumberDetail>






<pricingTickInfo><sellingPoint>

<locationId>PAR</locationId></sellingPoint><ticketingPoint>

<locationId>PAR</locationId></ticketingPoint>




<departurePoint><locationId>MRS</locationId>




<timeDetails><firstDateTimeDetail><date>200106</date>








Page 223 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 isrejected and the following message is returned:

"INVALID TICKETING/SELLING CITY"





Page 224 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. Nodecimal placement is allowed in the input.

The currency of the Price to Beat is the requested Currency of Conversion if specified; otherwise, it is thedefault 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





RC


200



Specified price to beat 3500









<numberOfUnits>200</numberOfUnits>





Page 225 of 714

<typeOfUnit>RC</typeOfUnit></unitNumberDetail>




</paxReference><priceToBeat>

<moneyInfo><amount>3500</amount>

</moneyInfo></priceToBeat><itinerary>





<arrivalPointDetails>








Invalid Price to Beat ValueIf the Price to Beat amount is composed of more than 9 digits, the value is not higher than zero, or adecimal placement is included in the input, the entire request is rejected and the following error messageis returned:

"INVALID PRICE TO BEAT VALUE"





Page 226 of 714

No Recommendation Found with Lower or Equal PriceThe Price to Beat is used as a reference. No recommendation that is returned to the user may have anhigher price. If no lower price recommendation is found, the following error message is returned:

"NO RECOMMENDATION FOUND WITH LOWER OR EQUAL PRICE".





Page 227 of 714

5.41 Operation: 04.04 Fare Option - Split / No Split PNRWhen a user requests fares for several passengers, these passengers may have different Passenger TypeCodes (for example, 1 ZZ and 1 CH). If the No Split PNR option is deactivated, the system returns the cheapestrecommendations even if different booking codes have to be applied to these passengers (non-homogenoussolutions). 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 samebooking 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:





RC




Child Passenger type code CH

Passenger type code applicable to 2nd passenger 2

Public fares included in the search RP

NPSSplit PNR Option activated

0

Applicable to 1st requested segment 1

Trip Departure city of Paris PAR

Trip Arrival city of Miami MIA

Trip Date (12 February 2002) 120202










Page 228 of 714












<feeId><feeType>NPS</feeType><feeIdNumber>0</feeIdNumber>







<arrivalLocalization><arrivalPointDetails><locationId>MIA</locationId>








Page 229 of 714








Page 230 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• EP for 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 accordinglyand 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:





RC


200



Electronic ticket included in the search ET











Page 232 of 714






Page 233 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 Corporaterequests.

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 followinginformation.

Query Requirements:

• Search to include Published Fares, non corporate Unifares and Coporate Fares (Coporate code 12345)





RC


200



Identify Published fares Price type search RP

Identify Corporate Unifares type search RU

Identify the corporate number as Corporate Unifares RW

RW Associated corporate number to Corporate Unifares

012345






Page 234 of 714







</unitNumberDetail>







<priceType>RP</priceType><priceType>RU</priceType><priceType>RW</priceType>













Page 235 of 714









Invalid Value - CorporateIf a valid corporate type is not specified (RW or RC) or if the corporate number specified is not matching thecorporate type requested (RW or RC), then the entire query is rejected with the following error message

"INVALID VALUE - CORPORATE"

Corporate Number Must be SpecifiedIf a corporate type (RC or RW) has been specified, yet no associated corporate number is included in thequery, the entire query is rejected with the following error:

"CORPORATE NUMBER MUST BE SPECIFIED"

Conflicting Options UsedUnifares and Amadeus Nego/Corporate options are not combinable. If this check fails, the entire requestis rejected and the following message is returned:

"CONFLICTING OPTIONS USED"





Page 236 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 thatthe 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 specifiedwith the following information.

Query Requirements:

• Only refundable fares should be returned in the recommendations.




Request specific maximum number of

recommendations to be returned

RC




Expanded Parameter type for Refundable fares RF


Trip departure city Marseille MRS

Trip arrival city Miami MIA











Page 237 of 714







<priceType>RF</priceType></pricingTicketing>














Invalid Value - Pricing / Tick InfoThe only valid expanded parameter options applicable are NAP, NPE, NR and RF. If an unknownExpanded Parameter is specified in the entry, the entire request is rejected and the following error messageis returned:





Page 238 of 714

"INVALID VALUE - PRICING/TICK INFO".

Conflicting Options UsedIt is not possible to combine the No Restriction (NR) Expanded Parameter with any other ExpandedParameter. If this check fails, the entire request is rejected and the following error message is returned:

"CONFLICTING OPTIONS USED".





Page 239 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 to6 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 toensure that combination of Fare Families parameters and other query options does not affect the functionalcoherence 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 M 1

Ranking 1-4 digits M 1

Combinability • Default:combinable or • NOC (Notcombinable)

O 1

Publishing Carrier 2 Alphanumeric O 0-10

Type of Fare • RP: publishedfares• RV: private fares• RN: 1Anegotiated fares• RA: Category 35fares• RD: DDF fares

• RU: Unifares

O 0-5

Prime Booking Code 2 alpha O 0-10

Fare Basis 1-9 characters (0 to 9, Ato Z, -)

O 0-10

Corporate Information CORP / NONCORP or CORPORATE CODE

CORPORATE NAME

O

O

0-6

0-6

(Sum of CORP CODE +CORPNAME <= 6)





Page 240 of 714

Cabin • M (EconomyStandard)• W (EconomyPremium)• Y (Economy)• C (Business)• F (First)

O 0-5

Expanded Parameter - Advance Purchase

• AP (With Advance Purchase)• NAP (No Advance Purchase)

O 0-2

Expanded Parameter -Refundability

• RF (Refundable)• NRE (non-Refundable)

O 0-2

Expanded Parameter -Penalty

• PE (with Penalty)• NPE (withoutPenalty)

O 0-2

Expanded Parameter -Restriction

• R (withRestriction)• NR (NoRestriction)

O 0-2

When publishing carrier criteria is used, the include airline option should also be requested in the query totarget the expected flights.

There is, therefore, up to 10 sets of criteria for each Parameterized Fare Family and this set of criteria maynot be coded negatively.

The example below illustrates a Lowest Fare request including 6 parameterized fare families defined by manyattributes 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 241 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:

◦ publishing carrier AF◦ Corporate Fares◦ Cabin Y

• Attributes Set 2:◦ publishing carrier AF

◦ 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:

◦ publishing carrier AF◦ 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 Description

fareFamilies/ familyInformation Fare Family information





Page 242 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 notcombinable 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

fareFamilies/familyCriteria/fareProductDetail/fareType Prime Booking Code

fareFamilies/familyCriteria/corporateInfo/corporateNumberIdentifier

CORP or NONCORP

fareFamilies/familyCriteria/fareProductDetail/cabinProduct/cabinDesignator

cabin

fareFamilies/familyCriteria/fareProductDetail/cabinProduct/otherCriteria/name

EXP

fareFamilies/familyCriteria/fareProductDetail/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








<ref>1</ref>





Page 243 of 714

</traveller></paxReference><fareFamilies>

<familyInformation><fareFamilyname>FFAMILY1</fareFamilyname><hierarchy>10</hierarchy>

</familyInformation><familyCriteria>

<carrierId> AF</carrierId><fareFamilyInfo>

<fareFamilyQual>NCO</fareFamilyQual></fareFamilyInfo><fareProductDetail>

<fareBasis>NAP30</fareBasis></fareProductDetail><fareProductDetail>

<fareType>RP</fareType></fareProductDetail><fareProductDetail>

<fareType>RA</fareType></fareProductDetail>

</familyCriteria></fareFamilies><fareFamilies>

<familyInformation>

<fareFamilyname>FFAMILY2</fareFamilyname><hierarchy>50</hierarchy>


<carrierId> AF</carrierId><carrierId>KL</carrierId><fareProductDetail>

<fareBasis>NCD</fareBasis></fareProductDetail><fareProductDetail>

<fareBasis>NRT</fareBasis></fareProductDetail>

<fareProductDetail><fareBasis>NRF</fareBasis></fareProductDetail><fareProductDetail>

<fareBasis>LCO</fareBasis></fareProductDetail><fareProductDetail>

<fareBasis>LCD</fareBasis></fareProductDetail>

</familyCriteria>





Page 244 of 714

</fareFamilies><fareFamilies>



<carrierId> AF</carrierId><corporateInfo>

<corporateNumberIdentifier>CORP</corporateNumberIdentifier></corporateInfo><cabinProduct>

<cabinDesignator>Y</cabinDesignator></cabinProduct>

</familyCriteria><otherPossibleCriteria>

<logicalLink><booleanExpression>

<codeOperator>OR</codeOperator></booleanExpression>

</logicalLink><familyCriteria>

<carrierId> AF</carrierId><corporateInfo>

<corporateNumberIdentifier>NONCORP</corporateNumberIdentifier>

</corporateInfo><cabinProduct>

<cabinDesignator>Y</cabinDesignator></cabinProduct><cabinProduct>

<cabinDesignator>C</cabinDesignator></cabinProduct><otherCriteria>

<name>EXP</name><value>NAP</value>

</otherCriteria><otherCriteria>

<name>EXP</name><value>NPE</value></otherCriteria>

</familyCriteria></otherPossibleCriteria><otherPossibleCriteria>







Page 245 of 714


<carrierId>KL</carrierId><cabinProduct>

<cabinDesignator>M</cabinDesignator></cabinProduct><cabinProduct>

<cabinDesignator>W</cabinDesignator></cabinProduct><cabinProduct>

<cabinDesignator>C</cabinDesignator></cabinProduct>

</familyCriteria></otherPossibleCriteria>




<carrierId> AF</carrierId><fareProductDetail>

<fareBasis>NCD</fareBasis></fareProductDetail>

</familyCriteria><otherPossibleCriteria>




<carrierId> AF</carrierId><carrierId>KL</carrierId><fareProductDetail>

<fareBasis>NRT</fareBasis>

</fareProductDetail></familyCriteria></otherPossibleCriteria><otherPossibleCriteria>








Page 246 of 714

<carrierId>KL</carrierId><fareProductDetail>

<fareBasis>-JUNIOR</fareBasis></fareProductDetail>

</familyCriteria></otherPossibleCriteria>




<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><hierarchy>0</hierarchy>

</familyInformation></fareFamilies><fareOptions>


<priceType>RU</priceType><priceType>RP</priceType><priceType>RW</priceType>









Page 247 of 714





<arrivalPointDetails><locationId> AMS</locationId>







<departurePoint>

<locationId> AMS</locationId></departurePoint>









In addition to the standard possible errors checks, the following ones are performed:





Page 248 of 714

PFF - TOO MANY FARE FAMILIESIf 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 REQUESTEDIf for a parameterised fare family, more than 10 matching attributes sets are specified, the entry is rejectedwith the following message:

"PFF - Too many matching attributes sets requested"

PFF - TOO MANY ATTRIBUTE OCCURRENCESIf for any attribute within any set defined in the query, more occurrences than the ones defined in the tablebelow are requested, the entry is rejected with the following message:

"PFF - Too many attribute occurrences requested"

PFF - INVALID FARE FAMILY NAME REQUESTEDIf 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 REQUESTEDIf 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 REQUESTEDIf the Fare Family Combinability is different than "Not Combinable", the whole entry is rejected with themessage:

"PFF - Invalid Fare Family Combinability Requested"

PFF - INVALID CARRIER REQUESTEDIf the specified publishing carrier is invalid, the whole entry is rejected with the message:

"PFF - Invalid Carrier Requested"

PFF - INVALID GENERIC FARE BASIS REQUESTEDIf 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 REQUESTEDIf 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 249 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 Detailssegment, within the same country and with the same modifier type. The system will then find the cheapesttravel solutions among all office ids requested in input (originator office id and additional office ids) withoutany 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 attributesare 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 theOriginator office id from the Originator Details segment. For this requested office id, the process is the sameas 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 sameOffice 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 doneto 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 AirlineTicketing 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 TrueCity Code is mandatory.





Page 250 of 714






</unitNumberDetail>













<arrivalPointDetails><locationId>PHL</locationId>




</itinerary>





Page 252 of 714



<conversionRateDetail><currency>USD</currency>

</conversionRateDetail></conversionRate><officeIdDetails>

<officeIdInformation><officeIdentification>

<agentSignin>MIA1A2100</agentSignin></officeIdentification>

</officeIdInformation><officeIdReference>

<referenceType>O</referenceType><refNumber>1</refNumber>

</officeIdReference></officeIdDetails><officeIdDetails>


<agentSignin>NYC1A2100</agentSignin></officeIdentification>





<agentSignin>DCA1A2200</agentSignin></officeIdentification>

</officeIdInformation>

<officeIdReference><referenceType>O</referenceType><refNumber>3</refNumber>



<agentSignin>NYC1A2200</agentSignin></officeIdentification>





Page 253 of 714





<agentSignin>SAN1A2300</agentSignin></officeIdentification>







<referenceType>O</referenceType>

<refNumber>6</refNumber></officeIdReference>

</officeIdDetails><flightIndex>




<ref>1</ref></flightProposal>

<flightProposal><ref>0628</ref><unitQualifier>EFT</unitQualifier>


<ref>US</ref><unitQualifier>MCX</unitQualifier>






Page 254 of 714




<locationId>LAX</locationId><terminal>1</terminal>


<locationId>LAS</locationId><terminal>1</terminal>


<marketingCarrier>US</marketingCarrier><operatingCarrier>US</operatingCarrier>








</productDateTime>

<location><locationId>LAS</locationId><terminal>1</terminal>


<locationId>PHL</locationId><terminal>B</terminal>


<marketingCarrier>US</marketingCarrier>





Page 255 of 714

<operatingCarrier>US</operatingCarrier></companyId><flightOrtrainNumber>1742</flightOrtrainNumber><productDetail>













<referencingDetail><refQualifier>O</refQualifier><refNumber>1</refNumber>


<refQualifier>O</refQualifier><refNumber>2</refNumber>

</referencingDetail>

<referencingDetail><refQualifier>O</refQualifier><refNumber>3</refNumber>




<refQualifier>O</refQualifier>





Page 256 of 714

<refNumber>5</refNumber></referencingDetail><referencingDetail>






<transportStageQualifier>V</transportStageQualifier><company>US</company>


<ptc> ADT</ptc>






</pricingMessage>

</fare><fareDetails><segmentRef>



<rbd>G</rbd><cabin>M</cabin>





Page 257 of 714


<fareBasis>GXA7NL2Y</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




<rbd>G</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>GJATNL6Y</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






- 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 followingmessage:

"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), thenthe entire entry is rejected with the following message:





Page 258 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 withthe 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 rejectedwith the following message:

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 rejectedwith the following message:

"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 thefollowing 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 requestis rejected with the following message:





Page 259 of 714


- If Multi Office Ids is requested with a complex itinerary (more than 3 requested segments), then the entirerequest is rejected with the following message:

"OPTION NOT PERMITTED WITH COMPLEX ITINERARIES"





Page 262 of 714

<officeIdDetails><officeIdInformation>

<officeIdentification><agentSignin>NYC1A0200</agentSignin>

</officeIdentification></officeIdInformation>

</officeIdDetails><officeIdDetails>


<agentSignin>LAX1A0300</agentSignin></officeIdentification>

</officeIdInformation></officeIdDetails>




- If this option is requested in another product than Master Pricer Travel Board, the entire entry is rejected withthe following message:

INVALID OPTION

- If this option is requested with any option it can't be combined with, then the entire request is rejected withthe following message:

"CONFLICTING OPTIONS USED".





Page 263 of 714

5.48 Operation: 04.11 Fare Option - Multi Office IDs - Weighted DistributionThe user has the ability to request for each office id, a fraction of the total number of recommendations byspecifying 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 requestedrecommendations 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 besold by several office ids, it is counted as one recommendation for each office id. As in standard mode, onlythe 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 moreconsidered 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 notreturned 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 leastone office id.





<numberOfUnits>1</numberOfUnits><typeOfUnit>WT</typeOfUnit>

</unitNumberDetail></numberOfUnit><fareOptions>








Page 264 of 714


<cabinId><cabinQualifier>RC</cabinQualifier><cabin>Y</cabin>

</cabinId><companyIdentity>

<carrierQualifier>X</carrierQualifier><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>




<departurePoint><locationId>YYC</locationId><airportCityQualifier>C</airportCityQualifier>


<arrivalPointDetails><locationId>CAI</locationId><airportCityQualifier>C</airportCityQualifier>


</arrivalLocalization><timeDetails><firstDateTimeDetail>








Page 265 of 714


<departurePoint><locationId>CAI</locationId><airportCityQualifier>C</airportCityQualifier>


<arrivalPointDetails><locationId>YYC</locationId><airportCityQualifier>C</airportCityQualifier>




</itinerary><officeIdDetails>


<agentSignin>LAX1A0100</agentSignin></officeIdentification>

</officeIdInformation>

<nbOfUnits><unitNumberDetail>


</unitNumberDetail></nbOfUnits>

</officeIdDetails><officeIdDetails>


<agentSignin>DTW1A0200</agentSignin></officeIdentification>

</officeIdInformation></officeIdDetails><officeIdDetails>



</officeIdInformation></officeIdDetails><officeIdDetails>





Page 267 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 type in 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 separatelyfrom the other taxes for legal reasons in some countries (for example, US), this option allows to get thoseamounts in output. This option does not have any effect on other returned amounts.

This option is triggered by a setting at office ID level.






</unitNumberDetail>
















Page 268 of 714


















Page 269 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.









</paxReference>

<paxReference><ptc>CH</ptc><traveller>




<priceType>PTC</priceType></pricingTicketing>










Page 270 of 714












Page 272 of 714













<familyInformation><fareFamilyname>FF1</fareFamilyname><hierarchy>100</hierarchy>


<carrierId>QF</carrierId><cabinProduct>










Page 273 of 714


</familyCriteria></fareFamilies><fareOptions>





<companyIdentity><carrierQualifier>R</carrierQualifier><carrierId>120</carrierId><carrierId>100</carrierId><carrierId>00</carrierId><carrierId>01</carrierId><carrierId>50</carrierId>








<firstDateTimeDetail><date>140810</date></firstDateTimeDetail>








Page 274 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 entrywill be rejected. Verify the ratios sent in the request are in the correct format. More importantly, 1-digit ratios arenot accepted by the system, therefore, ensure that no 1-digit ratios are included in the requests. An alternativeto 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-digitsnumeric.

Invalid - 6 Distribution Ratio Maximum

If more than 6 Distribution Ratios are listed in the DR option, the entire entry is rejected with the followingmessage:

"TOO MANY DISTRIBUTION RATIOS REQUESTED"





Page 275 of 714

5.52 Operation: 04.15 Fare Option - My Search - Resulting Fare Families atrequested segment levelWith this option, the Fare Family notion is applied at requested segment level. System returnsrecommendations distributed over combinations of Fare Families per requested segment.

For each recommendation, a resulting Fare Family is determined for each requested segment and for anycombination 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 theother 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 possiblecombinations of Fare Families. If a Fare Family is defined as non-combinable, there is only one possible typeof 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)• FF1 (requested segment 1) + FF2 (requested segment 2)• FF1 (requested segment 1) + FF3 (requested segment 2)• FF2 (requested segment 1) + FF1 (requested segment 2)• FF2 (requested segment 1) + FF2 (requested segment 2)• FF2 (requested segment 1) + FF3 (requested segment 2)• FF3 (requested segment 1) + FF1 (requested segment 2)• FF3 (requested segment 1) + FF2 (requested segment 2)

• FF3 (requested segment 1) + FF3 (requested segment 2)

For each of those 9 fare family combinations, the process must try to return 200/9 = about 22-23recommendations.

The example below shows a query with 2 Fare Families FF1 and FF2 and 2 requested segments.













Page 276 of 714


</traveller></paxReference><paxReference>















<cabinDesignator>Y</cabinDesignator></cabinProduct></familyCriteria>

</fareFamilies><fareOptions>


<priceType>FFS</priceType></pricingTicketing>

</pricingTickInfo>





Page 277 of 714




<departurePoint><locationId>MEL</locationId>


<arrivalPointDetails><locationId>SYD</locationId>






</requestedSegmentRef>

<departureLocalization><departurePoint>

<locationId>SYD</locationId></departurePoint>


<arrivalPointDetails><locationId>MEL</locationId>


<firstDateTimeDetail>

<date>070210</date></firstDateTimeDetail></timeDetails>



5.52.3 Possible Errors- If the Parameterized Fare Family option is not requested, the whole entry is rejected with the message:





Page 278 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 279 of 714

5.53 Operation: 04.16 Fare Option - My Search - Distribution ratio of recommendations per Fare Family at requested segment LevelThis option is the same as the Distribution Ratio of recommendations per Fare Family one except that the ratiosapply 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 processis made by a list of items. Each item is composed of a Fare Family combination and its associated ratio. Thereare 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 lastoccurrence 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,jrepresents the Distribution Ratio associated to Fare Family i combined with Fare Family j and N is the requestednumber 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 FareFamily (requested segment 2)














Page 280 of 714












</familyCriteria>






</familyCriteria>

</fareFamilies><fareOptions><pricingTickInfo>

<pricingTicketing><priceType>FFS</priceType>








Page 281 of 714











<departurePoint><locationId>SYD</locationId>


<arrivalPointDetails><locationId>MEL</locationId>




</itinerary><combinationFareFamilies><itemFFCNumber>

<itemNumberId><number>1</number><type>FAC</type>

</itemNumberId></itemFFCNumber><nbOfUnits>

<unitNumberDetail>





Page 282 of 714


</unitNumberDetail></nbOfUnits><referenceInfo>

<referencingDetail><refQualifier>RS</refQualifier><refNumber>1</refNumber>


<refQualifier>FF</refQualifier><refNumber>1</refNumber>

</referencingDetail></referenceInfo><referenceInfo>




</referencingDetail></referenceInfo>

</combinationFareFamilies>

<combinationFareFamilies><itemFFCNumber>

<itemNumberId><number>2</number><type>FAC</type>

</itemNumberId></itemFFCNumber><nbOfUnits>

<unitNumberDetail><numberOfUnits>20</numberOfUnits><typeOfUnit>WT</typeOfUnit>

</unitNumberDetail>

</nbOfUnits><referenceInfo><referencingDetail>

<refQualifier>RS</refQualifier><refNumber>1</refNumber>








Page 283 of 714

</referenceInfo><referenceInfo>





</combinationFareFamilies></Fare_MasterPricerTravelBoardSearch>



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 rejectedand 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 entryis 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 notincremented 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 284 of 714

If inside at least one Distribution Ratio item, there is not exactly one reference to a Fare Family, the entire entryis 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 isrejected with the message:

"REFERENCE TO REQUESTED SEGMENT IMPOSSIBLE AT ITINERARY LEVEL"





Page 285 of 714

5.54 Operation: 04.17 Fare Option - My Search - Distribution ratio of recommendations per Fare Family at requested segment level (Usage atitinerary level)It is possible to use the distribution ratio per Fare Family at requested segment level to define a distributionratio per Fare Family (meaning at itinerary level). To do so, the FFS flag is not set. In that case, only one FareFamily 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 associatedwith the second Fare Family.






</unitNumberDetail></numberOfUnit>















Page 286 of 714










</familyCriteria></fareFamilies><itinerary>
















Page 288 of 714

</unitNumberDetail></nbOfUnits><referenceInfo>

<referencingDetail><refQualifier> FF</refQualifier><refNumber>2</refNumber>


</combinationFareFamilies></Fare_MasterPricerTravelBoardSearch>







Page 289 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 inputshould 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.



<unitNumberDetail>






<ref>1</ref>


<pricingTickInfo/><conversionRate>

<conversionRateDetail><conversionType>CFS</conversionType><currency>SEK</currency>












Page 290 of 714







If an unknown currency is specified, then the entire request is rejected and the following error message isreturned:

VERIFY CURRENCY OPTION





Page 291 of 714

5.56 Operation: 04.19 Fare Option - Currency for Fare Selection withCurrency 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 Currencyof 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.












<priceType>CUC</priceType></pricingTicketing>

</pricingTickInfo><conversionRate>


</conversionRateDetail><conversionRateDetail>

<conversionType>CFS</conversionType><currency>GPB</currency>

</conversionRateDetail>





Page 292 of 714

</conversionRate></fareOptions><itinerary>












indicatorcurrencyqualifiererrormessagecurrencyqualifierindicatorerrormessagevalueconversionRate





Page 293 of 714

5.57 Operation: 04.20 Fare Option - Multi-TicketThe 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 (thesearch 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 flight that ismore expensive.

All solutions are returned as following:• First all One-Way recommendations that group the independent outbound are returned from thecheapest to the more expensive.

• Then all One-Way recommendations that group the independent inbound are returned from thecheapest to the more expensive.

• And finally, all Round Trip recommendations that group RT recommendations issued with 1 ticket arereturned from the cheapest to the more expensive.











<priceType>RU</priceType><priceType>RP</priceType><priceType>MTK</priceType>





Page 294 of 714



























Page 295 of 714




<conversionRateDetail><currency>GBP</currency>








<ref>KU</ref>

<unitQualifier>MCX</unitQualifier></flightProposal>

</propFlightGrDetail><flightDetails>




<locationId>LHR</locationId><terminal>4</terminal></location><location>

<locationId>KWI</locationId></location><companyId>

<marketingCarrier>KU</marketingCarrier><operatingCarrier>KU</operatingCarrier>

</companyId>





Page 296 of 714

<flightOrtrainNumber>104</flightOrtrainNumber><productDetail>


<electronicTicketing>Y</electronicTicketing><productDetailQualifier> AIP</productDetailQualifier>




<dateOfDeparture>201210</dateOfDeparture><timeOfDeparture>2255</timeOfDeparture><dateOfArrival>211210</dateOfArrival><timeOfArrival>0425</timeOfArrival><dateVariation>1</dateVariation>


<locationId>KWI</locationId></location><location>

<locationId>ISB</locationId></location>

<companyId><marketingCarrier>KU</marketingCarrier><operatingCarrier>KU</operatingCarrier>




</addProductDetail>

</flightInformation></flightDetails></groupOfFlights><groupOfFlights>



<ref>1215</ref>





Page 297 of 714

<unitQualifier>EFT</unitQualifier></flightProposal><flightProposal>

<ref>EY</ref><unitQualifier>MCX</unitQualifier>





<locationId>LHR</locationId><terminal>4</terminal>


<locationId> AUH</locationId><terminal>3</terminal>


<marketingCarrier>EY</marketingCarrier>

<operatingCarrier>EY</operatingCarrier></companyId><flightOrtrainNumber>12</flightOrtrainNumber><productDetail>




</flightDetails>








Page 298 of 714



<locationId>ISB</locationId></location><companyId>

<marketingCarrier>EY</marketingCarrier><operatingCarrier>EY</operatingCarrier>













<ref>GF</ref>

<unitQualifier>MCX</unitQualifier></flightProposal></propFlightGrDetail><flightDetails>







Page 300 of 714







<ref>QR</ref><unitQualifier>MCX</unitQualifier>





<locationId>ISB</locationId></location><location>

<locationId>DOH</locationId></location><companyId>

<marketingCarrier>QR</marketingCarrier><operatingCarrier>QR</operatingCarrier>

</companyId><flightOrtrainNumber>399</flightOrtrainNumber>

<productDetail><equipmentType>333</equipmentType></productDetail><addProductDetail>








Page 302 of 714




<locationId>DOH</locationId></location><companyId>










<locationId>DOH</locationId></location><location>

<locationId>LGW</locationId>

<terminal>N</terminal></location><companyId>








Page 303 of 714

<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier> AIP</productDetailQualifier>
















<marketingCarrier>EY</marketingCarrier><operatingCarrier>EY</operatingCarrier></companyId><flightOrtrainNumber>232</flightOrtrainNumber><productDetail>







Page 304 of 714





















</flightProposal>





Page 305 of 714
















</productDateTime><location><locationId> AUH</locationId><terminal>3</terminal>








Page 306 of 714









<number>1</number><numberType>M</numberType>









<transportStageQualifier>V</transportStageQualifier><company>KU</company>


<company>HR</company>





Page 307 of 714







</freeTextQualification><description>LAST TKT DTE</description><description>20DEC10</description><description> - DATE OF ORIGIN</description>




<productInformation>

<cabinProduct><rbd>M</rbd><cabin>M</cabin><avlStatus>7</avlStatus>


<fareBasis>MHOWGB1</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>


</productInformation>

</groupOfFares><groupOfFares><productInformation>

<cabinProduct><rbd>M</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>MHOWGB1</fareBasis>





Page 308 of 714
















<transportStageQualifier>V</transportStageQualifier>

<company>GF</company></codeShareDetails></paxFareDetail><paxReference>








Page 310 of 714

<cabinProduct><rbd>L</rbd><cabin>M</cabin><avlStatus>7</avlStatus>


<fareBasis>LOWPK5</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>








<monetaryDetail>






<segmentFlightRef><referencingDetail><refQualifier>S</refQualifier><refNumber>3</refNumber>


<paxFareDetail><paxFareNum>1</paxFareNum><totalFareAmount>299.70</totalFareAmount>





Page 311 of 714

<totalTaxAmount>70.70</totalTaxAmount><codeShareDetails>

<transportStageQualifier>V</transportStageQualifier><company>QR</company>









<monetaryDetail><amountType>MT</amountType><amount>22.00</amount><currency>GBP</currency>


</fare><fare>



</freeTextQualification><description>LAST TKT DTE</description><description>20DEC10</description><description> - DATE OF ORIGIN</description>



<textSubjectQualifier>SUR</textSubjectQualifier><informationType>79</informationType>

</freeTextQualification><description>FARE VALID FOR E TICKET ONLY</description>

</pricingMessage>





Page 312 of 714

</fare><fareDetails>




<rbd>H</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>HLOWPK</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>




<rbd>H</rbd>

<cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>HLOWPK</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>



</fareDetails></paxFareProduct></recommendation><recommendation>








Page 313 of 714














<transportStageQualifier>V</transportStageQualifier><company>EY</company>

</codeShareDetails></paxFareDetail>





<textSubjectQualifier>PEN</textSubjectQualifier>





Page 314 of 714

<informationType>70</informationType></freeTextQualification><description>TICKETS ARE NON-REFUNDABLE</description>




</freeTextQualification><description>LAST TKT DTE</description><description>04DEC10</description><description> - SEE ADV PURCHASE</description>





<rbd>H</rbd><cabin>M</cabin>


<fareBasis>HHRTGB</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>




<cabinProduct><rbd>H</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>HHRTGB</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>

</fareProductDetail>





Page 315 of 714

<breakPoint>Y</breakPoint></productInformation>

</groupOfFares></fareDetails><fareDetails>






<fareBasis>QHE6MGB</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>




<cabinProduct><rbd>Q</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>QHE6MGB</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>



</groupOfFares></fareDetails></paxFareProduct>








Page 316 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 hasthe ability to 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 thequery is received, are valid for ticketing on the future ticketing date specified in the input.








<ptc> ADT</ptc>



<pricingTickInfo><ticketingDate>

<date>100311</date></ticketingDate>











Page 317 of 714







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 entirerequest is rejected with the following message:

FUTURE DATE TICKETING NOT PERMITTED





Page 318 of 714

5.59 Operation: 04.23 Fare Option - Solution FamilyThe user has the ability to specify a list of Solution Family names in input.




</unitNumberDetail>





</paxReference><solutionFamily>

<valueQualifier>1</valueQualifier><rateCategory>CHP</rateCategory>

</solutionFamily><solutionFamily>

<valueQualifier>1</valueQualifier><rateCategory>DIR</rateCategory>


<valueQualifier>1</valueQualifier><rateCategory>LWD</rateCategory>

</solutionFamily><fareOptions>











Page 319 of 714


<locationId>NCE</locationId></departurePoint>












<locationId>NCE</locationId></arrivalPointDetails>














Page 320 of 714


</conversionRate><solutionFamily>

<identityNumber>1</identityNumber><rateCategory>CHP</rateCategory>


<identityNumber>2</identityNumber><rateCategory>DIR</rateCategory>


<identityNumber>3</identityNumber><rateCategory>LWD</rateCategory>

</solutionFamily><flightIndex>








</flightProposal><majCabin>W</majCabin>





<locationId>NCE</locationId><terminal>2</terminal>






Page 321 of 714

<locationId>ORY</locationId><terminal>W</terminal>


<marketingCarrier> AF</marketingCarrier><operatingCarrier> AF</operatingCarrier>








<ref>0355</ref>


<ref>XK</ref><unitQualifier>MCX</unitQualifier>

</flightProposal><majCabin>Y</majCabin>








<locationId>BIA</locationId>





Page 322 of 714


<marketingCarrier>XK</marketingCarrier><operatingCarrier>XK</operatingCarrier>


<equipmentType> AT7</equipmentType></productDetail><addProductDetail>







<locationId>BIA</locationId>




<marketingCarrier>XK</marketingCarrier><operatingCarrier> AF</operatingCarrier>











Page 323 of 714








</flightProposal><majCabin>Y</majCabin>


















Page 324 of 714






<ref>XK</ref><unitQualifier>MCX</unitQualifier>

</flightProposal><majCabin>W</majCabin>




</productDateTime>

<location><locationId>ORY</locationId><terminal>W</terminal>


<locationId>CLY</locationId></location><companyId>

<marketingCarrier>XK</marketingCarrier><operatingCarrier> AF</operatingCarrier>










Page 325 of 714




<locationId>CLY</locationId></location><location>



<marketingCarrier>XK</marketingCarrier><operatingCarrier>XK</operatingCarrier>










<monetaryDetail><amount>126.75</amount></monetaryDetail><monetaryDetail>


<amountType>YQ</amountType><amount>0</amount>

</monetaryDetail>





Page 326 of 714

<monetaryDetail><amountType>YR</amountType><amount>0</amount>


<amountType>Q</amountType><amount>0</amount>






<refQualifier>SF</refQualifier><refNumber>1</refNumber>






</codeShareDetails><monetaryDetails>

<amountType>YQ</amountType><amount>0</amount></monetaryDetails><monetaryDetails>

<amountType>YR</amountType><amount>0</amount>

</monetaryDetails><monetaryDetails>






Page 327 of 714

</monetaryDetails><pricingTicketing>








</freeTextQualification><description>LAST TKT DTE*25JUN12</description>





<rbd>E</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>ED3SAPFR</fareBasis><passengerType> ADT</passengerType><fareType>RD</fareType>


</productInformation></groupOfFares></fareDetails><fareDetails>








Page 328 of 714



<fareBasis>ED3SAPFR</fareBasis><passengerType> ADT</passengerType><fareType>RD</fareType>









</monetaryDetail>







<amountType>Q</amountType><amount>0</amount></monetaryDetail>








Page 329 of 714











</monetaryDetails>

<monetaryDetails><amountType>Q</amountType><amount>0</amount>





<ref>1</ref>





</pricingMessage>





Page 330 of 714

</fare><fare>



</freeTextQualification><description>LAST TKT DTE*26JUN12</description>





<rbd>N</rbd><cabin>M</cabin><avlStatus>1</avlStatus>


<fareBasis>NHLOISIR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






<fareBasis>N8POFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




<segmentRef>





Page 331 of 714



<rbd>T</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>T8POFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






<fareBasis>HHLOISIR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>










Page 332 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.








<companyIdentity><carrierQualifier>M</carrierQualifier><carrierId>BA</carrierId>

</companyIdentity><flightDetail>

<flightType>DN</flightType></flightDetail>




<departurePoint><locationId>MAD</locationId>


<arrivalPointDetails><locationId>LHR</locationId>








Page 333 of 714









Page 334 of 714

5.61 Operation: 04.25 Fare Option - Open ReturnThe user has the ability to specify an input option, Open Return, to book a segment without indicating aninbound date.

The user can also specify an optional "period of validity". This "period of validity" can be provided with theinbound date, which is set by default to 1 year (365 days) maximum, if not given in the input.



<unitNumberDetail>






<ref>1</ref>

</traveller></paxReference><paxReference>





<priceType>RU</priceType><priceType>RP</priceType><priceType>OPD</priceType>





<departurePoint>





Page 335 of 714



<arrivalPointDetails><locationId>BOD</locationId>







<departurePoint><locationId>BOD</locationId>



<locationId>PAR</locationId></arrivalPointDetails>















Page 336 of 714















<locationId>BOD</locationId><terminal>B</terminal>


<marketingCarrier> AF</marketingCarrier>

<operatingCarrier> AF</operatingCarrier></companyId><flightOrtrainNumber>6254</flightOrtrainNumber><productDetail>



</addProductDetail>





Page 337 of 714







<ref> A5</ref><unitQualifier>MCX</unitQualifier>




</productDateTime>



<locationId>LRT</locationId></location><companyId>

<marketingCarrier> A5</marketingCarrier><operatingCarrier>DB</operatingCarrier>


<productDetail><equipmentType>CR7</equipmentType></productDetail><addProductDetail>








Page 338 of 714




<locationId>LRT</locationId></location><location>

<locationId>LYS</locationId><terminal>2</terminal>


<marketingCarrier> A5</marketingCarrier><operatingCarrier>YS</operatingCarrier>


<equipmentType>ER4</equipmentType></productDetail><addProductDetail>







<locationId>LYS</locationId><terminal>2</terminal></location><location>

<locationId>BOD</locationId><terminal> A</terminal>







Page 339 of 714


<equipmentType>CRK</equipmentType></productDetail><addProductDetail>











<dateOfDeparture>111213</dateOfDeparture></productDateTime><location>

<locationId>BOD</locationId><terminal>B</terminal>



</location>

<companyId><marketingCarrier> AF</marketingCarrier><operatingCarrier> AF</operatingCarrier>

</companyId></flightInformation>







Page 340 of 714

<ref> A5</ref><unitQualifier>MCX</unitQualifier>




<locationId>BOD</locationId><terminal> A</terminal>







<flightInformation>

<productDateTime><dateOfDeparture>111213</dateOfDeparture>




<locationId>LRT</locationId></location><companyId>

<marketingCarrier> A5</marketingCarrier>

<operatingCarrier>DB</operatingCarrier></companyId></flightInformation>








Page 341 of 714

<locationId>LRT</locationId></location><location>


















</segmentFlightRef><paxFareProduct><paxFareDetail>



</codeShareDetails>





Page 342 of 714

<pricingTicketing><priceType>OBF</priceType><priceType>OBA</priceType><priceType>OBV</priceType>










<textSubjectQualifier>LTD</textSubjectQualifier>

<informationType>40</informationType></freeTextQualification><description>LAST TKT DTE</description><description>06OCT13</description><description> - SEE ADV PURCHASE</description>




<productInformation><cabinProduct><rbd>R</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>RRD0FR9</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>





Page 343 of 714









<rbd>R</rbd><cabin>M</cabin><avlStatus>8</avlStatus>


<fareBasis>RRD0FR9</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>





</fareDetails></paxFareProduct><paxFareProduct>




<priceType>OBF</priceType>





Page 344 of 714

<priceType>OBA</priceType><priceType>OBV</priceType>












<description>LAST TKT DTE</description><description>06OCT13</description><description> - SEE ADV PURCHASE</description>







<fareBasis>RRD0FR9</fareBasis><passengerType>CH</passengerType><fareType>RA</fareType>






Page 345 of 714


<additionalFareDetails><ticketDesignator>CH0</ticketDesignator>


</groupOfFares><majCabin>









<fareBasis>RRD0FR9</fareBasis><passengerType>CH</passengerType><fareType>RA</fareType>





</groupOfFares>

<majCabin><bookingClassDetails><designator>M</designator>




<itemNumber>





Page 346 of 714

<itemNumberId><number>2</number>















</pricingTicketing></paxFareDetail>





<textSubjectQualifier>PEN</textSubjectQualifier>





Page 347 of 714

<informationType>70</informationType></freeTextQualification><description>TICKETS ARE NON-REFUNDABLE</description>




</freeTextQualification><description>LAST TKT DTE</description><description>06OCT13</description><description> - SEE ADV PURCHASE</description>





<rbd>R</rbd><cabin>M</cabin>


<fareBasis>RSRFR9</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




<cabinProduct><rbd>E</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>ESRFR9</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






Page 349 of 714

















<totalTaxAmount>125.27</totalTaxAmount><codeShareDetails><transportStageQualifier>V</transportStageQualifier><company> AF</company>



</pricingTicketing>





Page 350 of 714














<textSubjectQualifier> APM</textSubjectQualifier><informationType>5</informationType>

</freeTextQualification><description>NOT FARED AT PASSENGER TYPE REQUESTED </description><description>5</description>


<fareDetails><segmentRef><segRef>1</segRef>








Page 351 of 714








<fareBasis>ESRFR9</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType>



<additionalFareDetails>

<ticketDesignator>CH</ticketDesignator></additionalFareDetails>

</ticketInfos></groupOfFares><groupOfFares>




<fareBasis>ESRFR9</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType>



<additionalFareDetails><ticketDesignator>CH</ticketDesignator>

</additionalFareDetails>





Page 352 of 714

</ticketInfos></groupOfFares><majCabin>















<fareBasis>RSRFR9</fareBasis><passengerType> ADT</passengerType>

<fareType>RP</fareType></fareProductDetail><breakPoint>Y</breakPoint>



<rbd>R</rbd><cabin>M</cabin>





Page 353 of 714










- "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 354 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 cheapestavailable 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 familiesmust be flagged as ALT to distinguish them from the "standard" fare families used for MySearch. The highestranking 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 FamilyFare 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

Total amount: 1900.00 $

Alternate price: 2000.00 $ (Groupof recommendation 2)

Group of recommendation 1

Req Seg 1, Prop Seg 1


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 355 of 714

Total amount: 2000.00 $Recommendation 4 LAX-SYD UA838 FFFFF

SYD-LAX UA840 FFFFF





Recommendation 5 LAX-SYD UA838 FFFFF

SYD-LAX UA841 FFFFF











</paxReference><fareFamilies>



<fareFamilyInfo><fareFamilyQual> ALT</fareFamilyQual>

</fareFamilyInfo><corporateInfo>

<corporateName>NET</corporateName></corporateInfo><corporateInfo>

<corporateName>PKG</corporateName></corporateInfo>


<familyInformation><fareFamilyname>FF2</fareFamilyname>





Page 356 of 714

<hierarchy>10</hierarchy></familyInformation><familyCriteria>

<fareFamilyInfo><fareFamilyQual> ALT</fareFamilyQual>

</fareFamilyInfo><fareProductDetail>

<fareType>RV</fareType></fareProductDetail><fareProductDetail>

<fareType>RP</fareType></fareProductDetail>

</familyCriteria></fareFamilies><fareOptions>











<firstDateTimeDetail><date>170215</date></firstDateTimeDetail>








Page 357 of 714



<arrivalPointDetails><locationId>LAX</locationId>








</status></replyStatus>

<conversionRate><conversionRateDetail>

<currency>USD</currency></conversionRateDetail>

</conversionRate><familyInformation>

<refNumber>1</refNumber><fareFamilyname>FF1</fareFamilyname><hierarchy>20</hierarchy>

</familyInformation><familyInformation>

<refNumber>2</refNumber><fareFamilyname>FF2</fareFamilyname><hierarchy>10</hierarchy>

</familyInformation><flightIndex>




<ref>1</ref>





Page 358 of 714




<ref>UA</ref><unitQualifier>MCX</unitQualifier>







<locationId>SYD</locationId>

<terminal>1</terminal></location><companyId>

<marketingCarrier>UA</marketingCarrier><operatingCarrier>UA</operatingCarrier>




<productDetailQualifier>IAV</productDetailQualifier></addProductDetail></flightInformation>








Page 359 of 714










<locationId>SYD</locationId><terminal>1</terminal>





<electronicTicketing>Y</electronicTicketing><productDetailQualifier>IAV</productDetailQualifier>

</addProductDetail></flightInformation></flightDetails>








Page 360 of 714











</location>

<location><locationId>LAX</locationId><terminal>B</terminal>





<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier>IAV</productDetailQualifier>








Page 361 of 714











<locationId>LAX</locationId>

<terminal>B</terminal></location><companyId>





<productDetailQualifier>IAV</productDetailQualifier></addProductDetail></flightInformation>




<number>1</number>





Page 362 of 714

</itemNumberId></itemNumber><fareFamilyRef>

<referencingDetail><refQualifier>F</refQualifier><refNumber>1</refNumber>


<refNumber>1</refNumber></referencingDetail>

</fareFamilyRef><recPriceInfo>




<amountType>YQ</amountType><amount>680.00</amount>


<amountType>YR</amountType><amount>0.00</amount>


<amountType>Q</amountType><amount>0.00</amount>




<refQualifier>S</refQualifier><refNumber>1</refNumber></referencingDetail><referencingDetail>

<refQualifier>P</refQualifier><refNumber>2</refNumber>


<paxFareDetail>





Page 363 of 714


<transportStageQualifier>V</transportStageQualifier><company>UA</company>







</monetaryDetails></paxFareDetail><paxReference>






</freeTextQualification><description>TICKETS ARE NON REFUNDABLE AFTER DEPARTURE</description>


<pricingMessage>


</freeTextQualification><description>LAST TKT DTE 27JAN15 - SEE ADV PURCHASE</description>







Page 365 of 714

<corporateId>085513</corporateId><breakPoint>Y</breakPoint>


<additionalFareDetails><ticketDesignator>54DC</ticketDesignator>






</itemNumber><fareFamilyRef>



<refNumber>2</refNumber>

</referencingDetail></fareFamilyRef><recPriceInfo>





</monetaryDetail><monetaryDetail><amountType>YR</amountType><amount>0.00</amount>



</monetaryDetail></recPriceInfo>





Page 366 of 714










<paxFareDetail><paxFareNum>1</paxFareNum><totalFareAmount>2000.00</totalFareAmount><totalTaxAmount>830.00</totalTaxAmount>

<codeShareDetails><transportStageQualifier>V</transportStageQualifier><company>UA</company>





</monetaryDetails>

<monetaryDetails><amountType>Q</amountType><amount>0.00</amount>








Page 367 of 714








</freeTextQualification><description>LAST TKT DTE 14JAN15 - SEE SALES RSTNS</description>







<fareBasis>LLX41EM5</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>



</groupOfFares></fareDetails><fareDetails>




<rbd>L</rbd>





Page 369 of 714


</segmentFlightRef><segmentFlightRef>














<ptc> ADT</ptc>

<traveller><ref>1</ref></traveller>









Page 370 of 714

<description>TICKETS ARE NON-REFUNDABLE</description></pricingMessage>

</fare><fare>



</freeTextQualification><description>LAST TKT DTE 14JAN15 - SEE SALES RSTNS</description>







<fareBasis>FFFFF</fareBasis>

<passengerType> ADT</passengerType><fareType>RA</fareType>






<productInformation><cabinProduct><rbd>L</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>FFFFF</fareBasis><passengerType> ADT</passengerType><fareType>RA</fareType>





Page 371 of 714










Page 372 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 allowancein piece or weight concept.

Only recommendations with free baggage allowance (>0) are returned in the output for all therecommendations.

Activation :

<feeIdDescription>

<feeId> <feeType>SBF</feeType>

<feeIdNumber>1</feeIdNumber>

</feeId>

</feeIdDescription>

There is no change in the output structure.









<priceType>BAG</priceType></pricingTicketing>


<feeId><feeType>SBF</feeType><feeIdNumber>1</feeIdNumber>





Page 373 of 714





<departurePoint><locationId>ORY</locationId>


<arrivalPointDetails><locationId>MAD</locationId>









<arrivalPointDetails><locationId>IBZ</locationId>










Page 374 of 714






Page 375 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 servicein the case where it has been requested to do so and at least one flight of the proposed segment containsthe 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 andthe 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 therequested Cabin. Non-Stops, Directs, Connecting and Change of Gauges for which the cabin is not definedor not available are not selected.

The cabin option applies to the entire trip and must be specified at the itinerary level of the request. Requestedcabin 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 notdefined or closed - the other cabins may be considered by the system. This process is only applied when in atleast one of the flights of a Proposed segment on the requested cabin exists. Whenever a Proposed segmentmay 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 flightbetween Paris/NewYork/Chicago, the systemproposed segment will not be returned in therecommendations.

If Cabin Class (F) is only available on the systemproposed segment only from Paris/NewYork, default

cabin classes will be processed for NewYork/Chicago segments.

If Cabin Class (F) is only available on the systemproposed 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 followinginformation.





Page 376 of 714

Query Requirements:

• Requested cabin service: F• No cabin defaulting, requested cabin must be on entire trip recommendation





RC




First cabin service requested at itinerary level F




Itinerary Date (12 February 2006) 120206










<cabinId><cabin>F</cabin>

</cabinId></travelFlightInfo>





Page 377 of 714












Invalid Cabin CodeIf the cabin code does not exist, the following error message is returned:

"INVALID CABIN CODE"

Option Cannot be Applied at Requested Segment LevelIf the cabin code is not requested at the itinerary level, the following error message is returned:






Page 378 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 followinginformation.

Query Requirements:

• Requested cabin service: F• 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 cabinin order to be eligible.





RC




Requested Cabin can be defaulted RC





Itinerary Date (12 February 2006) 120206







<ptc> ADT</ptc>





Page 379 of 714


</traveller></paxReference><travelFlightInfo>

<cabinId><cabinQualifier>RC</cabinQualifier><cabin>F</cabin>

</cabinId></travelFlightInfo><itinerary>













"INVALID CABIN CODE"







Page 380 of 714

5.66 Operation: 05.3 Cabin Option - Major CabinThe example below illustrates a low fare search including an optional Major Cabin element specified with thefollowing information.

Query Requirements:

• Requested cabin service: F• With the Major Cabin option, the transaction replies with recommendations that are mostly flown in therequested cabin for each requested segment.





RC




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






</unitNumberDetail>





Page 381 of 714









<cabinId><cabinQualifier>MC</cabinQualifier><cabin>F</cabin>

</cabinId></travelFlightInfo><itinerary>




<locationId>SYD</locationId></departurePoint>









<departurePoint>





Page 382 of 714

<locationId>NCE</locationId></departurePoint>










"INVALID CABIN CODE".


"OPTION CANNOT BE APPLIED AT REQUESTED SEGMENT LEVEL".





Page 383 of 714

5.67 Operation: 06.1 Fee Option - Pricing Scheme ReferenceThe 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.






Passenger type code applicable to 2nd passenger 2

Child Passenger type code CH

Passenger type code applicable to 3rd passenger 3

Pricing Scheme reference 12345


Departure city of Tel Aviv TLV

Trip Arrival city of Vienna VIE

Trip Date (2 June 2016) 020616


Departure city of Vienna VIE

Arrival city of Tel Aviv TLV

Trip Date (8 June 2016) 080616










Page 384 of 714







<pricingTickInfo/><ticketingPriceScheme>

<referenceNumber>12345</referenceNumber></ticketingPriceScheme>




<departurePoint><locationId>TLV</locationId>


<arrivalPointDetails><locationId>VIE</locationId>




</itinerary><itinerary><requestedSegmentRef>


<departurePoint><locationId>VIE</locationId>






Page 385 of 714


<locationId>TLV</locationId></arrivalPointDetails>











</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 386 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>





<ref>0350</ref>


<ref>6X</ref><unitQualifier>MCX</unitQualifier>







Page 387 of 714



<locationId>TLV</locationId><terminal>3</terminal>


<locationId>VIE</locationId></location><companyId>

<marketingCarrier>6X</marketingCarrier><operatingCarrier>6X</operatingCarrier>



















Page 388 of 714




<locationId>VIE</locationId></location><location>

<locationId>TLV</locationId><terminal>3</terminal>






<productDetailQualifier> AIP</productDetailQualifier></addProductDetail>





</itemNumber>





<referencingDetail>





Page 389 of 714






<transportStageQualifier>V</transportStageQualifier><company>6X</company>



</pricingTicketing></paxFareDetail><feeRef>

<referencingDetail>

<refQualifier>R</refQualifier><refNumber>1</refNumber>

</referencingDetail></feeRef><paxReference>












Page 390 of 714



</freeTextQualification><description>LAST TKT DTE*02JUN16* - DATE OF ORIGIN</description>







<fareBasis>LRT</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>


<breakPoint>Y</breakPoint></productInformation>






</segmentRef><groupOfFares><productInformation>



<fareBasis>LRT</fareBasis>





Page 391 of 714










<priceType>OBF</priceType><priceType>OBA</priceType>


</paxFareDetail><feeRef>

<referencingDetail><refQualifier>R</refQualifier><refNumber>2</refNumber>

</referencingDetail></feeRef><paxReference>


<ref>3</ref></traveller></paxReference><fare>








Page 392 of 714




</freeTextQualification><description>LAST TKT DTE*02JUN16* - DATE OF ORIGIN</description>







<fareBasis>LRT</fareBasis><passengerType>CH</passengerType>






<bookingClassDetails>

<designator>M</designator></bookingClassDetails></majCabin>









Page 393 of 714



<fareBasis>LRT</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType>
















Page 394 of 714

5.68 Operation: 06.2 Fee Option - Form of PaymentThe form of payment option may be combined with any other option. A maximum of 3 forms of payment maybe 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




Applicable on 1st trip 1Trip departure city of Paris 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









Page 395 of 714








</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>













Page 396 of 714





Two FOP must not be provided without any amounts. If done, the whole request is rejected and the following

message is returned:

"CHECK FORMAT"

Three FOP must not be provided without any amounts. If done, the whole request is rejected and the followingmessage is returned:

"CHECK FORMAT"

Three FOP must not be provided with only one amount. If done, the whole request is rejected and the followingmessage is returned:

"CHECK FORMAT"

Three FOP must not be provided with three amounts. If done, the whole request is rejected and the following

message is returned:"CHECK FORMAT"

More than three FOP cannot be entered. If done, the whole request is rejected and the following messageis returned:

"CHECK FORMAT"

A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, thewhole request is rejected and the following message is returned:






Page 397 of 714

5.69 Operation: 06.3 Fee Option - Sorting with/without FeesThis 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.









</paxReference>


<pricingTicketing><priceType>RU</priceType><priceType>RP</priceType>

</pricingTicketing></pricingTickInfo><feeIdDescription>

<feeId><feeType>SORT</feeType><feeIdNumber>NOFEE</feeIdNumber>











Page 398 of 714


<locationId>NCE</locationId></arrivalPointDetails>




</itinerary><feeOption>

<feeTypeInfo><carrierFeeDetails>

<type>OB</type></carrierFeeDetails>

</feeTypeInfo><feeDetails>

<feeInfo><dataTypeInformation>

<subType>T02</subType><option>EX</option>

</dataTypeInformation></feeInfo>

</feeDetails>

<feeDetails><feeInfo>

<dataTypeInformation><subType>FC4</subType><option>IN</option>

</dataTypeInformation></feeInfo><associatedAmounts>

<monetaryDetails><typeQualifier>C</typeQualifier><amount>20.00</amount>

</monetaryDetails>

</associatedAmounts></feeDetails></feeOption>



5.69.3 Possible ErrorsFees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected andthe following message is returned:





Page 399 of 714

"ENTRY NOT AUTHORISED"Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and thefollowing message is returned:

"ENTRY NOT AUTHORISED"





Page 400 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.




<typeOfUnit>RC</typeOfUnit></unitNumberDetail><unitNumberDetail>




















Page 401 of 714



</timeDetails></itinerary><feeOption>


<type>OB</type><optionInformation>EX</optionInformation>

</carrierFeeDetails></feeTypeInfo>

</feeOption></Fare_MasterPricerTravelBoardSearch>



Fees cannot be exempted if OB Global Activation setting is OFF. If done, the whole request is rejected andthe following message is returned:


Fees cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected and thefollowing message is returned:


A specific fee can not be both added and exempted in input. If done, the whole request is rejected and thefollowing message is returned:






Page 402 of 714

5.71 Operation: 06.5 Fee 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.

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 exemptedsubcode nor ticketing sub-code), an amount can be optionally specified.

If 1 FOP sub-code is added, the amount 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 cardwith a bin number starting with 4

FC4:IN

Amount paid with credit card with a bin number starting with 4 is 20.00 [1]

20.00

[1] Fees from FCA sub-code may apply also.
















Page 403 of 714












<subType>T02</subType>

<option>EX</option></dataTypeInformation>

</feeInfo></feeDetails><feeDetails>


<subType>FC4</subType><option>IN</option>

</dataTypeInformation></feeInfo><associatedAmounts>

<monetaryDetails><typeQualifier>C</typeQualifier><amount>20.00</amount>

</monetaryDetails></associatedAmounts>

</feeDetails></feeOption>






Page 404 of 714



A sub-code cannot be added if OB Global Activation setting is OFF. If done, the whole request is rejected andthe following message is returned:


It is not allowed to enter an amount with an addition of a Ticketing sub-code. If done, the whole request isrejected and the following message is returned:

"CHECK FORMAT"

FCA cannot be added in combination with another Form Of Payment sub-code. If done, the whole request isrejected and the following message is returned:

"CHECK FORMAT"

Three Form Of Payment sub-codes must not be added with only one amount. If done, the whole request isrejected and the following message is returned:

"CHECK FORMAT"

Three Form of Payment sub-codes must not be added with three amounts. If done, the whole request is rejectedand 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 rejectedand the following message is returned:


A sub-code cannot be exempted if OB Exemption setting is OFF. If done, the whole request is rejected andthe following message is returned:


A Form of Payment sub-code cannot be added in combination with a Form of Payment in input. If done, thewhole request is rejected and the following message is returned:

"CONFLICTING OPTIONS USED" A specific fee can not be both added and exempted in input. If done, the whole request is rejected and thefollowing message is returned:






Page 405 of 714

5.72 Operation: 06.6 Fee Option - Estimated FOP feesWhen 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 wasrequested. For example, if we request minimum any card, minimum debit card, maximum debit card, maximumcredit card and maximum any card in input, we will have minimum any card, minimum debit card, maximumdebit card, maximum credit card in output.

In the example below, we request the minimum fee amount for any type of card (FON) and the maximum feeamount 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.










<priceType>RU</priceType><priceType>RP</priceType><priceType>FON</priceType><priceType>FOX</priceType>






Page 406 of 714























<status>





Page 407 of 714












</flightProposal>






</location><location><locationId>ORY</locationId><terminal>W</terminal>








Page 408 of 714

<productDetail><equipmentType>320</equipmentType>
















</productDateTime>





<marketingCarrier>6X</marketingCarrier>





Page 409 of 714

<operatingCarrier>6X</operatingCarrier></companyId><flightOrtrainNumber>6244</flightOrtrainNumber><productDetail>












<amountType>OB</amountType><amount>21032.88</amount>


<amountType>XOB</amountType><amount>276.50</amount>


<amountType>FON</amountType>


<amountType>FOX</amountType><amount>19675.76</amount>


<referencingDetail><refQualifier>S</refQualifier>





Page 410 of 714







<amountType>OB</amountType><amount>10516.44</amount>


<amountType>XOB</amountType><amount>138.25</amount>


<priceType>OBI</priceType><priceType>OBF</priceType><priceType>OBA</priceType><priceType>OBV</priceType>












Page 411 of 714







<fareBasis>RSAPFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>









<fareBasis>RSAPFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

</fareProductDetail><breakPoint>Y</breakPoint></productInformation>


</paxFareProduct></recommendation>







Page 412 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 onanother 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 returnedonly 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 AirlineDiversity recommendations set.

In order to have more airline diversity within this set, the process guarantees that no more than 50% of therecommendation has the same combination of main carriers over the itinerary.









<priceType> ADI</priceType></pricingTicketing>







Page 413 of 714















Page 414 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 all the different carriers ensuring at least the cheapest recommendationfor each online carrier and the cheapest recommendation for each 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 onlinerecommendation, the cheapest recommendation on which this carrier is also the main carrier is also returnedonly 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 AirlineDiversity Container.

In order to have more airline diversity within this set, the process guarantees that no more than 50% of thecheapest recommendations set have the same combination of main carriers over the itinerary.









<priceType> ADC</priceType></pricingTicketing>






Page 415 of 714
















Page 416 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 directdistribution 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 cheapestrecommendations. 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 thedirect recommendations in the returned solutions up to 20% of the requested number if they exist.






<ref>1</ref>



<priceType>DDI</priceType></pricingTicketing>












Page 417 of 714




















Page 418 of 714

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

Direct Distribution can be deactivated using the option NDD.










<priceType>NDD</priceType></pricingTicketing>














Page 419 of 714


















Page 420 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.









<priceType>NAD</priceType>











</itinerary>





Page 421 of 714









Page 422 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 whichone will be selected is not predictable.

Cheapest Recommendation Set

This set contains all the cheapest recommendations matching the client’s query that are not included in therecommendations set built by the Mono-Main carrier distribution.

In order to have more airline diversity within this set, the process guarantees that no more than 50% of thecheapest recommendations have the same combination of main carriers over the itinerary.









<priceType>MCD</priceType></pricingTicketing>





</departurePoint>





Page 423 of 714













Page 424 of 714

5.79 Operation: 07.7 Distribution Option - Ratios for WeightedRecommendationsThis 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 themixed 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).






</unitNumberDetail>

<unitNumberDetail><numberOfUnits>20</numberOfUnits><typeOfUnit>OWO</typeOfUnit>


<numberOfUnits>50</numberOfUnits><typeOfUnit>OWI</typeOfUnit>


<numberOfUnits>30</numberOfUnits><typeOfUnit>RT</typeOfUnit>






<priceType>MTK</priceType>





Page 425 of 714







<arrivalPointDetails><locationId> ATH</locationId>







<departurePoint><locationId> ATH</locationId>












Page 426 of 714






Page 427 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 arefavoured. 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 flightrecommendations, 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%.







<numberOfUnits>50</numberOfUnits><typeOfUnit>RNP</typeOfUnit>






<priceType>RP</priceType><priceType>RU</priceType><priceType>DNP</priceType>


</fareOptions>





Page 428 of 714



<departurePoint><locationId>BOS</locationId>


<arrivalPointDetails><locationId>CHI</locationId>







<departurePoint><locationId>CHI</locationId>





</firstDateTimeDetail></timeDetails></itinerary>








Page 429 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 localsolution 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, thecorresponding 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 inthe output message as it is the case for the default behaviour when this option is not activated.



















Page 430 of 714

<priceType>ECC</priceType></pricingTicketing>




















Page 431 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 Solutionsreturned by Journey Server (numbering starts to 1) per requested segment.














<priceType>RJS</priceType></pricingTicketing>










Page 432 of 714













Page 433 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 defaultweight must be specified.

The user can simultaneously request up to 20 criteria by default.

Query description

List of supported criteria:

Designation Code Attributes Influence UnitNumber of Connection

CNX None Penalty Price per connection

Online MarketingCarrier

OCX None Bonus Price

Change of Airport COA None Penalty Price per change of airport

Total Trip Time EFT None Penalty Price per hour

OvernightConnection

OVC None Penalty Price per overnight

Ground Time GRT None Penalty Price per hour

Preferred Carrier PCX List of Carriers Bonus Price per 100% EFTflown

UnpreferredCarriers

UCX List of Carriers Penalty Price per 100% EFTflown

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 aconnection

RMC None Penalty Price

Interline carrier ICX None Bonus Price

Distance torequested date

DRD None Penalty Price per day of difference to

Unpreferred TLA ULC None Penalty Price per 100% EFTflown

Number of stops STP None Penalty Price per stop

Preferred alliance PAL List of Alliances Bonus Price per 100% EFTflown





Page 434 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 list is forward sorted.











<conversionRateDetail><conversionType>COV</conversionType><currency>EUR</currency>



<companyIdentity>





Page 435 of 714

<carrierQualifier>X</carrierQualifier><carrierId>6X</carrierId><carrierId>7X</carrierId><carrierId>2X</carrierId><carrierId>7S</carrierId><carrierId>7X</carrierId><carrierId>8X</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>


<value>40</value><attribute>EC</attribute><attribute>IB</attribute><attribute>OS</attribute>

</criteriaDetails></valueSearch>

<valueSearch><criteriaCode>FLX</criteriaCode><value>250</value>

</valueSearch><itinerary>



<departurePoint>





Page 436 of 714

<locationId>ROM</locationId></departurePoint>












<locationId>ROM</locationId></arrivalPointDetails>















Page 437 of 714








<ref>BA</ref><unitQualifier>MCX</unitQualifier>





<locationId>FCO</locationId><terminal>3</terminal>




<marketingCarrier>BA</marketingCarrier>

<operatingCarrier>BA</operatingCarrier></companyId><flightOrtrainNumber>555</flightOrtrainNumber><productDetail>



</addProductDetail>





Page 438 of 714







<ref> AZ</ref><unitQualifier>MCX</unitQualifier>




</productDateTime>

<location><locationId>FCO</locationId><terminal>1</terminal>




<marketingCarrier> AZ</marketingCarrier><operatingCarrier> AZ</operatingCarrier>

</companyId>

<flightOrtrainNumber>210</flightOrtrainNumber><productDetail><equipmentType>320</equipmentType>




</flightDetails>





Page 439 of 714











<locationId>FCO</locationId>


<locationId>LGW</locationId><terminal>N</terminal>








</flightIndex>





Page 440 of 714

<flightIndex><requestedSegmentRef>















<marketingCarrier>BA</marketingCarrier><operatingCarrier>BA</operatingCarrier>









Page 441 of 714






<ref> AZ</ref><unitQualifier>MCX</unitQualifier>









<marketingCarrier> AZ</marketingCarrier><operatingCarrier> AZ</operatingCarrier>


<productDetail><equipmentType>32S</equipmentType></productDetail><addProductDetail>








Page 442 of 714

<groupOfFlights><propFlightGrDetail>

























Page 443 of 714












<refQualifier>V</refQualifier><refNumber>2</refNumber>



<transportStageQualifier>V</transportStageQualifier><company>BA</company>


<priceType>OBV</priceType></pricingTicketing></paxFareDetail><paxReference>








Page 445 of 714







<rbd>O</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>OAP2V1H</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>



<majCabin><bookingClassDetails>





<number>2</number>





</recPriceInfo>





Page 446 of 714









<transportStageQualifier>V</transportStageQualifier><company> AZ</company>











</freeTextQualification><description>LAST TKT DTE*21JUL16* - SEE ADV PURCHASE</description>

</pricingMessage>





Page 447 of 714







<fareBasis>WSP8C</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>










</cabinProduct>

<fareProductDetail><fareBasis>LSP8C</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>








Page 448 of 714



















<transportStageQualifier>V</transportStageQualifier><company>VY</company>



</paxFareDetail>





Page 449 of 714






</freeTextQualification><description>LAST TKT DTE*24DEC15* - SEE ADV PURCHASE</description>





<rbd>D</rbd><cabin>M</cabin><avlStatus>4</avlStatus>


<fareBasis>DRTBIZ</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




</bookingClassDetails></majCabin></fareDetails><fareDetails>








Page 451 of 714

5.84 Operation: 08.04 Output Option - Value Search at requested segmentlevel At requested segment level, the user has the possibility to evaluate the more convenient solutions, dependingof 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 defaultweight must be specified.

Note that in this case, the value returned in output for each recommendation is computed for the whole itinerary.








<ptc> ADT</ptc>




<conversionRateDetail><conversionType>COV</conversionType><currency>EUR</currency>











Page 452 of 714




</firstDateTimeDetail></timeDetails><valueSearch>

<criteriaCode>OCX</criteriaCode><value>30</value>

</valueSearch></itinerary><itinerary>









</firstDateTimeDetail></timeDetails><valueSearch>

<criteriaCode>PCX</criteriaCode><value>10</value><criteriaDetails>

<value>20</value><attribute> AF</attribute></criteriaDetails><criteriaDetails>

<value>30</value><attribute> AA</attribute>


<attribute>BA</attribute></criteriaDetails>





Page 453 of 714

</valueSearch></itinerary>











<ref>1</ref>




<ref>VA</ref><unitQualifier>MCX</unitQualifier>





<locationId>CDG</locationId><terminal>2C</terminal>

</location>





Page 455 of 714





<locationId>BNE</locationId><terminal>D</terminal>




<marketingCarrier>VA</marketingCarrier><operatingCarrier>VA</operatingCarrier>


<equipmentType>73H</equipmentType>






<ref>2</ref>

</flightProposal><flightProposal><ref>2355</ref><unitQualifier>EFT</unitQualifier>


<ref>KE</ref><unitQualifier>MCX</unitQualifier>






Page 456 of 714

<flightDetails><flightInformation>

<productDateTime><dateOfDeparture>200116</dateOfDeparture><timeOfDeparture>2100</timeOfDeparture><dateOfArrival>210116</dateOfArrival><timeOfArrival>1555</timeOfArrival><dateVariation>1</dateVariation>


<locationId>CDG</locationId><terminal>2E</terminal>


<locationId>ICN</locationId></location><companyId>

<marketingCarrier>KE</marketingCarrier><operatingCarrier>KE</operatingCarrier>








<dateVariation>1</dateVariation></productDateTime><location>

<locationId>ICN</locationId></location><location>







Page 458 of 714


<marketingCarrier>VA</marketingCarrier><operatingCarrier>VA</operatingCarrier>











<locationId>CDG</locationId><terminal>2A</terminal>


<marketingCarrier>VA</marketingCarrier><operatingCarrier>EY</operatingCarrier>


<productDetail><equipmentType>77W</equipmentType></productDetail><addProductDetail>








Page 459 of 714






<ref>KE</ref><unitQualifier>MCX</unitQualifier>







<locationId>ICN</locationId></location><companyId>

<marketingCarrier>KE</marketingCarrier><operatingCarrier>KE</operatingCarrier>



<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier>LCA</productDetailQualifier>









Page 460 of 714






<marketingCarrier>KE</marketingCarrier><operatingCarrier> AF</operatingCarrier>





</flightDetails>






</monetaryDetail>

<monetaryDetail><amount>491.64</amount></monetaryDetail>








Page 461 of 714






<transportStageQualifier>V</transportStageQualifier><company>VA</company>





<ref>1</ref>






<pricingMessage><freeTextQualification><textSubjectQualifier>LTD</textSubjectQualifier><informationType>40</informationType>

</freeTextQualification><description>LAST TKT DTE*28DEC15* - SEE ADV PURCHASE</description>


<pricingMessage>





Page 462 of 714

<freeTextQualification><textSubjectQualifier>SUR</textSubjectQualifier><informationType>79</informationType>








<fareBasis>LKRFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>






<fareBasis>LKRFR</fareBasis><passengerType> ADT</passengerType>

<fareType>RP</fareType><fareType>ET</fareType></fareProductDetail><breakPoint>N</breakPoint>



<rbd>L</rbd>





Page 463 of 714



<fareBasis>LKRFR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>











<fareBasis>VZRFRS</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>



</groupOfFares><groupOfFares><productInformation>

<cabinProduct><rbd>V</rbd><cabin>M</cabin><avlStatus>6</avlStatus>


<fareBasis>VZRFRS</fareBasis>





Page 464 of 714

<passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>











</monetaryDetail>






</referencingDetail><referencingDetail><refQualifier>V</refQualifier><refNumber>2</refNumber>







Page 465 of 714

<totalTaxAmount>468.78</totalTaxAmount><codeShareDetails>

<transportStageQualifier>V</transportStageQualifier><company>KE</company>









<monetaryDetail><amountType>MT</amountType><amount>234.00</amount><currency>EUR</currency>


</fare><fare>



</freeTextQualification><description>LAST TKT DTE*13JAN16* - SEE ADV PURCHASE</description>










Page 466 of 714


<fareBasis>QLXAPKE</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>




<rbd>Y</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>YEEKZ</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>









<rbd>D</rbd><cabin>C</cabin><avlStatus>9</avlStatus>


<fareBasis>DBIZKR</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






Page 467 of 714





<fareBasis>QLXAPKE</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






</recommendation>

<value><ref>1</ref><value>1469.64</value>

</value><value>

<ref>2</ref><value>3327.78</value>

</value></Fare_MasterPricerTravelBoardSearchReply>






Page 468 of 714

5.85 Operation: 08.05 Output Option - Display Minimum/Maximum StayThe user has the possibility to display the minimum and the maximum stay at fare component level with theMST option in the query.









</paxReference>


<pricingTicketing><priceType>MST</priceType>














Page 469 of 714







</status>


<conversionRateDetail><currency>INR</currency>









<ref>FI</ref><unitQualifier>MCX</unitQualifier>










Page 470 of 714


<locationId>KEF</locationId></location><companyId>

<marketingCarrier>FI</marketingCarrier><operatingCarrier>FI</operatingCarrier>









<locationId>KEF</locationId></location><location>

<locationId>EWR</locationId><terminal>B</terminal>



</companyId>

<flightOrtrainNumber>623</flightOrtrainNumber><productDetail><equipmentType>75W</equipmentType>




</flightDetails>





Page 471 of 714





<monetaryDetail><amount>40253</amount>


<amount>23648</amount></monetaryDetail><monetaryDetail>





<amountType>Q</amountType>

<amount>0</amount></monetaryDetail>





<totalFareAmount>40253</totalFareAmount><totalTaxAmount>23648</totalTaxAmount><codeShareDetails>

<transportStageQualifier>V</transportStageQualifier><company>FI</company>



</monetaryDetails>





Page 472 of 714

<monetaryDetails><amountType>YR</amountType><amount>13076</amount>













</freeTextQualification><description>LAST TKT DTE</description><description>20FEB14</description><description> - SEE ADV PURCHASE</description>


<segmentRef>









Page 474 of 714

<dateAndTimeDetails><qualifier>MSC</qualifier><date>05OCT14</date>

</dateAndTimeDetails><dateAndTimeDetails>

<qualifier>MSP</qualifier><date>05DEC14</date>

</dateAndTimeDetails></dateInfo>

</mnrDetails></mnrGrp>







Page 475 of 714

5.86 Operation: 08.07 Output Option - Fare Family informationDepending 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

value

1 2 3

FF name at farecomponent level

x x x

Resulting FF name atrequested segment level

x x

Services of the resultingFF

x

For each service, the output should include commercial description (text) filed in by the airline as well as theOC 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 476 of 714

◦ Commercial description: CHNG BEF DEP














<feeId><feeType>FFI</feeType><feeIdNumber>3</feeIdNumber>



<companyIdentity><carrierQualifier>M</carrierQualifier><carrierId>6X</carrierId>




<departurePoint>





Page 477 of 714

<locationId>LON</locationId></departurePoint>












<locationId>LON</locationId></arrivalPointDetails>















Page 478 of 714

</conversionRate><familyInformation>

<refNumber>1</refNumber><fareFamilyname>VALUE</fareFamilyname><description>ECONOMY VALUE</description><services>

<reference>1</reference><status>INC</status>

</services><services>

<reference>3</reference><status>CHA</status>

</services></familyInformation><familyInformation>

<refNumber>2</refNumber><fareFamilyname>BASIC</fareFamilyname><description>ECONOMY BASIC</description><services>



<reference>2</reference><status>NOF</status>

</services></familyInformation><flightIndex>








<flightInformation>





Page 479 of 714





















</flightProposal>





Page 480 of 714


















<number>1</number></itemNumberId></itemNumber><fareFamilyRef>








Page 481 of 714

</referencingDetail></fareFamilyRef><recPriceInfo>















<codeShareDetails><transportStageQualifier>V</transportStageQualifier><company>VS</company>




<amountType>YR</amountType>





Page 482 of 714

<amount>0.00</amount></monetaryDetails><monetaryDetails>














</freeTextQualification><description>LAST TKT DTE</description><description>27APR14</description><description> - SEE ADV PURCHASE</description>


<pricingMessage><freeTextQualification><textSubjectQualifier>SUR</textSubjectQualifier><informationType>79</informationType>



<segmentRef>





Page 483 of 714





<fareBasis>OLXMGE</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>


</productInformation><fareFamiliesRef>


</referencingDetail></fareFamiliesRef>










<fareBasis>OLXMGE</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>






Page 484 of 714

<breakPoint>Y</breakPoint></productInformation><fareFamiliesRef>







</recommendation><serviceFeesGrp>


<type>OC</type></carrierFeeDetails>

</serviceTypeInfo><globalMessageMarker/><serviceDetailsGrp>

<serviceOptionInfo><dataTypeInformation>

<subType>LMS</subType></dataTypeInformation>

</serviceOptionInfo><feeDescriptionGrp>

<itemNumberInfo><itemNumberDetails>

<number>1</number><type>SD</type>


<commercialName><freeTextQualification><textSubjectQualifier>3</textSubjectQualifier>

</freeTextQualification><freeText>LIGHT MEAL SNACK</freeText>

</commercialName></feeDescriptionGrp>

</serviceDetailsGrp><serviceDetailsGrp>

<serviceOptionInfo>





Page 487 of 714



<departurePoint><locationId>SFO</locationId>


<arrivalPointDetails><locationId>IAD</locationId>










<conversionRateDetail><currency>GBP</currency>







</flightProposal>





Page 488 of 714

<flightProposal><ref>UA</ref><unitQualifier>MCX</unitQualifier>





<locationId>IAD</locationId></location><location>

<locationId>SFO</locationId><terminal>3</terminal>






<electronicTicketing>Y</electronicTicketing><productDetailQualifier>IAC</productDetailQualifier>

</addProductDetail><attributeDetails>

<attributeType>EFT</attributeType><attributeDescription>0600</attributeDescription>

</attributeDetails></flightInformation>

</flightDetails></groupOfFlights></flightIndex><flightIndex>








Page 489 of 714




<ref> AA</ref><unitQualifier>MCX</unitQualifier>





<locationId>SFO</locationId><terminal>2</terminal>


<locationId>DFW</locationId>


<marketingCarrier> AA</marketingCarrier><operatingCarrier> AA</operatingCarrier>




</addProductDetail><attributeDetails><attributeType>EFT</attributeType><attributeDescription>0315</attributeDescription>








Page 490 of 714



<locationId>DFW</locationId></location><location>

<locationId>IAD</locationId></location><companyId>






<attributeType>EFT</attributeType>

<attributeDescription>0250</attributeDescription></attributeDetails>





</itemNumber>





<referencingDetail>





Page 491 of 714








<company> AA</company></codeShareDetails>



<ref>1</ref>






<pricingMessage><freeTextQualification><textSubjectQualifier>SUR</textSubjectQualifier><informationType>79</informationType>



<segmentRef>





Page 493 of 714



<fareBasis>OA21ERA1</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>












Page 494 of 714

5.88 Operation: 08.09 Output Option - Commission returnedThe 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 farecomponent.








</paxReference>


<pricingTicketing><priceType>RW</priceType>







<departurePoint><locationId>SEL</locationId>






Page 495 of 714






</companyIdentity></flightInfo>





</status>










<ref>6x</ref><unitQualifier>MCX</unitQualifier>

</flightProposal>





Page 496 of 714



















<flightInformation>





Page 497 of 714




<locationId>PRG</locationId><terminal>1</terminal>






</addProductDetail>





<locationId>PRG</locationId>





</companyId>





Page 498 of 714












<amount>123.773</amount><currency>YQ</currency>






<referencingDetail>

<refQualifier>S</refQualifier><refNumber>1</refNumber></referencingDetail>

</segmentFlightRef><paxFareProduct>






Page 499 of 714













</paxReference>



</freeTextQualification><description>LAST TKT DTE</description><description>22OCT14</description>


<pricingMessage>

<freeTextQualification><textSubjectQualifier> APM</textSubjectQualifier></freeTextQualification><description>CORPORATE NAME XX07</description>



</segmentRef>





Page 500 of 714

<groupOfFares><productInformation>

<cabinProduct><rbd>Y</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>COMM</fareBasis><passengerType> ADT</passengerType><fareType>RC</fareType>

</fareProductDetail><corporateId>123456</corporateId><breakPoint>Y</breakPoint>


<discountDetails><fareQualifier>CM</fareQualifier><percentage>13.34</percentage>

</discountDetails></ticketInfos>












</monetaryDetail>





Page 501 of 714

<monetaryDetail><amountType>YR</amountType><amount>104.28</amount>























Page 502 of 714



</freeTextQualification><description>LAST TKT DTE</description><description>22OCT14</description>



<textSubjectQualifier> APM</textSubjectQualifier></freeTextQualification><description>CORPORATE NAME XX07</description>





<rbd>Y</rbd>



<fareBasis>COMM</fareBasis><passengerType> ADT</passengerType><fareType>RC</fareType>

</fareProductDetail><corporateId>123456</corporateId><breakPoint>N</breakPoint>


<groupOfFares><productInformation><cabinProduct>



<fareBasis>COMM</fareBasis><passengerType> ADT</passengerType>





Page 504 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













<locationId>NYC</locationId></arrivalPointDetails>









Page 505 of 714












<ref>1115</ref>










</location>





Page 506 of 714

<companyId><marketingCarrier>6X</marketingCarrier><operatingCarrier>6X</operatingCarrier>





<attributeType>TPM</attributeType><attributeDescription>641</attributeDescription>



















Page 507 of 714

<attributeType>TPM</attributeType><attributeDescription>3463</attributeDescription>
























Page 508 of 714













<pricingMessage>


</freeTextQualification><description>LAST TKT DTE*01MAR15</description>




</freeTextQualification><description>FARE VALID FOR E TICKET ONLY</description></pricingMessage>









Page 509 of 714



<fareBasis>W2EO</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>




<rbd>W</rbd><cabin>W</cabin><avlStatus>9</avlStatus>


<fareBasis>W2EO</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

<fareType>ET</fareType></fareProductDetail><breakPoint>Y</breakPoint>


<bookingClassDetails><designator>W</designator>









Page 510 of 714

5.90 Operation: 08.11 Output option - Return Airline AllianceThe 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)








<ptc> ADT</ptc>







<companyIdentity><carrierQualifier>M</carrierQualifier><carrierId>LH</carrierId><carrierId>LA</carrierId>








Page 511 of 714


<locationId>SCL</locationId></departurePoint>










</status>










<ref>LH</ref><unitQualifier>MCX</unitQualifier>

</flightProposal>





Page 512 of 714





<locationId>SCL</locationId></location><location>

<locationId>GRU</locationId><terminal>3</terminal>


<marketingCarrier>LA</marketingCarrier><operatingCarrier>LA</operatingCarrier>

</companyId><flightOrtrainNumber>O</flightOrtrainNumber><productDetail>


<lastSeatAvailable>Y</lastSeatAvailable></addProductDetail>




</productDateTime><location><locationId>GRU</locationId><terminal>3</terminal>








Page 513 of 714

<marketingCarrier>LH</marketingCarrier><operatingCarrier>LH</operatingCarrier>














<transportStageQualifier>V</transportStageQualifier><company>LH</company>


<company>LA</company></codeShareDetails><pricingTicketing>



<ptc> ADT</ptc>





Page 514 of 714







<monetaryDetail><amountType>MT</amountType><amount>182</amount><currency>EUR</currency>


</fare><fare>








<cabinProduct><rbd>S</rbd><cabin>M</cabin><avlStatus>7</avlStatus>


<fareBasis>HLRCOWCL</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>






Page 515 of 714

<breakPoint>N</breakPoint></productInformation>

</groupOfFares><groupOfFares>




<fareBasis>HLRCOWCL</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>












Page 516 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 recommendationsattached 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 involvesmandatory 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>

<feeType>FFI</feeType>


</feeId>

<feeId>

<feeType>UPH</feeType>


</feeId>

</feeIdDescription>





Page 518 of 714

<refQualifier>U</refQualifier>



<referencingDetail>




<referencingDetail>

<refQualifier>B</refQualifier>



</segmentFlightRef>

<segmentFlightRef>

Same travel solution for elligible and different fare family for the elligible and upsell recommendations : thisrecommendation has an upsell which is the 8th recommendation and its fare family are : 0 / 1

<itemNumberId>

<number>2</number>

</itemNumberId>

</itemNumber>





Page 519 of 714

<fareFamilyRef>

<referencingDetail>

<refQualifier>F</refQualifier>



<referencingDetail>



</fareFamilyRef>

<recPriceInfo>

<monetaryDetail>

<amount>745.92</amount>

</monetaryDetail>

<monetaryDetail>


</monetaryDetail>

</recPriceInfo>

<segmentFlightRef>

<referencingDetail>

<refQualifier>S</refQualifier>



<referencingDetail>







Page 520 of 714


<referencingDetail>




This recommendation is the upsell from the above recommendation. We can see that the travel solution is thesame (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 521 of 714


</monetaryDetail>

</recPriceInfo>

<segmentFlightRef>

<referencingDetail>




<referencingDetail>




<referencingDetail>




</segmentFlightRef>

<segmentFlightRef>

<referencingDetail>




<referencingDetail>







Page 522 of 714






</unitNumberDetail>






<priceType>RW</priceType><priceType>RP</priceType>

<priceType>RU</priceType><priceType>ET</priceType><priceType>RDI</priceType><priceType>PSB</priceType><priceType>TAC</priceType><priceType>XLC</priceType>



</corporateId></corporate><feeIdDescription>


</feeId><feeId>

<feeType>UPH</feeType><feeIdNumber>6</feeIdNumber>

</feeId>





Page 523 of 714

</feeIdDescription></fareOptions><travelFlightInfo>

<companyIdentity><carrierQualifier>U</carrierQualifier><carrierId>ZZ</carrierId>




<departurePoint><locationId>MUC</locationId><airportCityQualifier>C</airportCityQualifier>


<arrivalPointDetails><locationId>CGK</locationId><airportCityQualifier> A</airportCityQualifier>







<departurePoint><locationId>CGK</locationId>

<airportCityQualifier> A</airportCityQualifier></departurePoint></departureLocalization><arrivalLocalization>

<arrivalPointDetails><locationId>MUC</locationId><airportCityQualifier>C</airportCityQualifier>






Page 524 of 714








<subType>FCA</subType><option>IN</option>










Page 525 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 recommendationsattached 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 eachbound.

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 eligiblerecommendation level.

Input activation :

UPB option :

<feeIdDescription>

<feeId>

<feeType>FFI</feeType>


</feeId>

<feeId>

<feeType>UPB</feeType>


</feeId>

</feeIdDescription>





Page 526 of 714

A list of marketing carriers for which upsell must be processed (optional). By default, if not specified, upsellprocess applies on all the eligible marketing carriers in output :

<travelFlightInfo>

<companyIdentity>

<carrierQualifier>U</carrierQualifier>

<carrierId>ZZ</carrierId>

<carrierQualifier>U</carrierQualifier>

<carrierId>XX</carrierId>

</companyIdentity>

</travelFlightInfo>

In output :

U qualifier in RefQualifier field (this recommendation has 2 upsells) :

<segmentFlightRef>

<referencingDetail>




<referencingDetail>








Page 527 of 714

<referencingDetail>




<referencingDetail>




<referencingDetail>




</segmentFlightRef>

<segmentFlightRef>

Same travel solution for elligible and different fare family for the elligible and upsell recommendations : thisrecommendation has an upsell which is the 8th recommendation and its fare family are : 0 / 1

<itemNumberId>

<number>2</number>





Page 528 of 714

</itemNumberId>

</itemNumber>

<fareFamilyRef>

<referencingDetail>




<referencingDetail>



</fareFamilyRef>

<recPriceInfo>

<monetaryDetail>


</monetaryDetail>

<monetaryDetail>


</monetaryDetail>

</recPriceInfo>

<segmentFlightRef>

<referencingDetail>




<referencingDetail>






Page 529 of 714



<referencingDetail>




This recommendation is the upsell from the above recommendation. We can see that the travel solution is thesame (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 530 of 714

<monetaryDetail>


</monetaryDetail>

</recPriceInfo>

<segmentFlightRef>

<referencingDetail>




<referencingDetail>




<referencingDetail>




</segmentFlightRef>

<segmentFlightRef>

<referencingDetail>




<referencingDetail>







Page 531 of 714






</unitNumberDetail>






<priceType>RW</priceType><priceType>RP</priceType>

<priceType>RU</priceType><priceType>ET</priceType><priceType>RDI</priceType><priceType>PSB</priceType><priceType>TAC</priceType><priceType>XLC</priceType>



</corporateId></corporate><feeIdDescription>


</feeId><feeId>

<feeType>UPB</feeType><feeIdNumber>6</feeIdNumber>

</feeId>





Page 532 of 714

</feeIdDescription></fareOptions><travelFlightInfo>

<companyIdentity><carrierQualifier>U</carrierQualifier><carrierId>ZZ</carrierId>




<departurePoint><locationId>MUC</locationId><airportCityQualifier>C</airportCityQualifier>


<arrivalPointDetails><locationId>CGK</locationId><airportCityQualifier> A</airportCityQualifier>







<departurePoint><locationId>CGK</locationId>

<airportCityQualifier> A</airportCityQualifier></departurePoint></departureLocalization><arrivalLocalization>

<arrivalPointDetails><locationId>MUC</locationId><airportCityQualifier>C</airportCityQualifier>






Page 533 of 714








<subType>FCA</subType><option>IN</option>










Page 534 of 714

5.93 Operation: 09.01 Output Option - Change Of GaugeThis 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 IB6173between MAD and SJO. Traveller stops in MIA and changes of equipment Boeing 747 => Airbus 319.

Item SearchReply - Data element Value

0 /replyStatus/status/advisoryTypeInfo

FQX

1 /conversionRate/conversionRateDetail/currency

USD

2 /flightIndex/requestedSegmentRef/segRef

1

3 /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[11] /ref

1


1305

5 /flightIndex/groupOfFlights[11] /

propFlightGrDetail/flightProposal[21] /unitQualifier

EFT


S3

7 /flightIndex/groupOfFlights[11] /propFlightGrDetail/flightProposal[31] /unitQualifier

MCX

8 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/productDateTime/dateOfDeparture

200703

9 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/productDateTime/timeOfDeparture

1200

10 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/productDateTime/dateOfArrival

200703

11 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/productDateTime/timeOfArrival

1500





Page 535 of 714

12 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/location[11] /locationId

MAD

13 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/location[11] /terminal

1


CCS

15 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/

companyId/marketingCarrier

S3

16 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/companyId/operatingCarrier

S3

17 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/flightNumber

1333

18 /flightIndex/groupOfFlights[11] /flightDetails[11] /flightInformation/productDetail/equipmentType

D10


flightDetails[11] /flightInformation/addProductDetail/electronicTicketing

N


200703


1615


200703


1705


CCS





Page 536 of 714


SJO

26 /flightIndex/groupOfFlights[11] /flightDetails[21] /flightInformation/companyId/marketingCarrier

LR


LR

28 /flightIndex/groupOfFlights[11] /flightDetails[21] /

flightInformation/flightNumber

611


320

30 /flightIndex/groupOfFlights[11] /flightDetails[21] /flightInformation/addProductDetail/electronicTicketing

N


2


propFlightGrDetail/flightProposal[21] /ref

1415


EFT


IB


MCX

36 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDateTime/dateOfDeparture

200703

37 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDateTime/timeOfDeparture

1215





Page 537 of 714

38 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDateTime/dateOfArrival

200703

39 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDateTime/timeOfArrival

1830

40 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/location[11] /locationId

MAD

41 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/

location[11] /terminal

1

42 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/location[21] /locationId

SJO

43 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/companyId/marketingCarrier

IB

44 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/companyId/operatingCarrier

IB


flightDetails/flightInformation/flightNumber

6173

46 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDetail/equipmentType

747

47 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/addProductDetail/electronicTicketing

Y

48 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/productDetail/techStopNumber

1

49 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[11] /dateQualifier

AA

50 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[11] /date

200703





Page 538 of 714

51 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[11] /firstTime

1540

52 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[11] /locationId

MIA

53 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[21] /dateQualifier

AD

54 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/

stopDetails[21] /date

200703

55 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[21] /firstTime

1645

56 /flightIndex/groupOfFlights[21] /flightDetails/technicalStop/stopDetails[21] /equipmentType

319

57 /flightIndex/groupOfFlights[21] /flightDetails/flightInformation/addProductDetail[21] //electronicTicketing

N


propFlightGrDetail/flightProposal[11] /ref

3


2505


EFT


AA


MCX


200703





Page 539 of 714


1655


200703


1815


location[11] /locationId

MAD


1


LHR


2


flightDetails[11] /flightInformation/companyId/marketingCarrier

IB


IB


3166


752


Y


200703





Page 540 of 714


2005


200703


2250



LHR


3


JFK


8


flightDetails[21] /flightInformation/companyId/marketingCarrier

AA


AA


141


777


N


210703





Page 541 of 714


0640


210703


1000



JFK


2


SJO

96 /flightIndex/groupOfFlights[31] /flightDetails[31] /flightInformation/companyId/marketingCarrier

LR


flightDetails[31] /flightInformation/companyId/operatingCarrier

LR


663


320


N

101 /recommendation[11] /itemNumber/itemNumberId/number

1

102 /recommendation[11] /recPriceInfo/monetaryDetail[11] /amount

734.60


9.60





Page 542 of 714

104 /recommendation[11] /segmentFlightRef/referencingDetail/refQualifier

S

105 /recommendation[11] /segmentFlightRef/referencingDetail/refNumber

1

106 /recommendation[11] /paxFareProduct/paxFareDetail/paxFareNum

1

107 /recommendation[11] /paxFareProduct/

paxFareDetail/totalFareAmount

734.60

108 /recommendation[11] /paxFareProduct/paxFareDetail/totalTaxAmount

9.60

109 /recommendation[11] /paxFareProduct/paxReference/ptc

ADT

110 /recommendation[11] /paxFareProduct/paxReference/traveller/ref

1


fare/pricingMessage/freeTextQualification/messageQualifier

LTD

112 /recommendation[11] /paxFareProduct/fare/pricingMessage/freeTextQualification/messageCode

40

113 /recommendation[11] /paxFareProduct/fare/pricingMessage/ description[11]

LAST TKT DTE

114 /recommendation[11] /paxFareProduct/fare/

pricingMessage/description[21]

20FEB03

115 /recommendation[11] /paxFareProduct/fare/pricingMessage/description[31]

- SEE ADV PURCHASE

116 /recommendation[11] /paxFareProduct/fareDetails/segmentRef/segRef

1

117 /recommendation[11] /paxFareProduct/fareDetails/

M





Page 543 of 714

productInformation[11] /avlProductDetails/rbd

118 /recommendation[11] /paxFareProduct/fareDetails/productInformation[11] /avlProductDetails/avlStatus

4

119 /recommendation[11] /paxFareProduct/fareDetails/productInformation[11] /fareProductDetail/fareBasis

MHOW

120 /recommendation[11] /

paxFareProduct/fareDetails/productInformation[11] /fareProductDetail/passengerType

ADT

121 /recommendation[11] /paxFareProduct/fareDetails/productInformation[11] /fareProductDetail/fareType

RP

122 /recommendation[11] /paxFareProduct/fareDetails/productInformation[21] /avlProductDetails/rbd

Y


7


MHOW

125 /recommendation[11] /paxFareProduct/fareDetails/productInformation[21] /fareProductDetail/passengerType

ADT


RP


2





Page 544 of 714


973.10


8.10


S


2


1

133 /recommendation[21] /paxFareProduct/paxFareDetail/totalFareAmount

973.10


8.10


ADT


1

137 /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/freeTextQualification/messageQualifier

PEN

138 /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/freeTextQualification/messageCode

71

139 /recommendation[21] /paxFareProduct/fare[11] /pricingMessage/description

TICKETS ARE NON-REFUNDABLE AFTERDEPARTURE

140 /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/freeTextQualification/messageQualifier

LTD


40





Page 545 of 714

fare[21] /pricingMessage/freeTextQualification/messageCode

142 /recommendation[21] /paxFareProduct/fare[21] /pricingMessage/description[11]

LAST TKT DTE


06FEB03


- SEE ADV PURCHASE


1

146 /recommendation[21] /paxFareProduct/fareDetails/productInformation/avlProductDetails/rbd

B

147 /recommendation[21] /paxFareProduct/fareDetails/productInformation/avlProductDetails/avlStatus

9

148 /recommendation[21] /paxFareProduct/fareDetails/productInformation/fareProductDetail/fareBasis

BHSXOW

149 /recommendation[21] /paxFareProduct/fareDetails/productInformation/fareProductDetail/passengerType

ADT

150 /recommendation[21] /paxFareProduct/fareDetails/productInformation/fareProductDetail/fareType

RP


3


1001.22


26.22





Page 546 of 714


S


3


1


paxFareDetail/totalFareAmount

1001.22


26.22


ADT


1


fare[11] /pricingMessage/freeTextQualification/messageQualifier

PEN


71

163 /recommendation[31] /paxFareProduct/fare[11] /pricingMessage/description

TICKETS ARE NON-REFUNDABLE AFTERDEPARTURE


fare[21] /pricingMessage/freeTextQualification/messageQualifier

LTD


40


LAST TKT DTE





Page 547 of 714


06FEB03


- SEE ADV PURCHASE


1

170 /recommendation[31] /paxFareProduct/fareDetails/

productInformation[11] /avlProductDetails/rbd

K


9


KHSXOW

173 /recommendation[31] /

paxFareProduct/fareDetails/productInformation[11] /fareProductDetail/passengerType

ADT


RP


K


7


KHSXOW





Page 548 of 714


ADT


RP


Z


7


KHSXOW


ADT


RP












Page 549 of 714







<arrivalPointDetails><locationId>SJO</locationId>












Page 550 of 714

5.94 Operation: 09.02 Output Option - Fare CalculationThis option allows the user to request the entire fare calculation.

When the FS Parameter Gb_Fare_Calculation is set, the following information is 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.



















Page 551 of 714












<currency>EUR</currency></conversionRateDetail><conversionRateDetail>

<conversionType>FCC</conversionType><currency>NUC</currency><rate>0.595825</rate>

</conversionRateDetail><conversionRateDetail>

<currency>GBP</currency><rate>1.259213</rate>






<ref>1420</ref>





Page 552 of 714


<ref>EI</ref><unitQualifier>MCX</unitQualifier>





<locationId>LGW</locationId><terminal>S</terminal>


<locationId>DUB</locationId><terminal>2</terminal>


<marketingCarrier>EI</marketingCarrier>

<operatingCarrier>EI</operatingCarrier></companyId><flightOrtrainNumber>233</flightOrtrainNumber><productDetail>




</flightDetails>




<locationId>DUB</locationId>





Page 553 of 714




<marketingCarrier>EI</marketingCarrier><operatingCarrier>EI</operatingCarrier>







<ref>2</ref>




<ref>EI</ref><unitQualifier>MCX</unitQualifier>


<flightInformation>




</location>





Page 554 of 714

<location><locationId>DUB</locationId><terminal>2</terminal>
























Page 555 of 714















<marketingCarrier>BA</marketingCarrier><operatingCarrier>EI</operatingCarrier>










Page 556 of 714








<marketingCarrier>BA</marketingCarrier><operatingCarrier> AA</operatingCarrier>




<productDetailQualifier> AIP</productDetailQualifier></addProductDetail>





<ref>0740</ref>









Page 557 of 714







<marketingCarrier>BA</marketingCarrier><operatingCarrier>BA</operatingCarrier>




</addProductDetail>






<monetaryDetail>









Page 558 of 714





<transportStageQualifier>V</transportStageQualifier><company>EI</company>





<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>


<rate>16.95</rate><countryCode> AS</countryCode><type>UP</type>





Page 559 of 714


<rate>7.50</rate><countryCode>DO</countryCode><type>UQ</type>


<rate>4.05</rate><countryCode> AE</countryCode><type>YC</type>


<rate>12.88</rate><countryCode> AS</countryCode><type>US</type>


<rate>3.68</rate><countryCode>CO</countryCode><type>XA</type>


<rate>5.15</rate><countryCode>CR</countryCode><type>XY</type>

</taxDetails></passengerTaxDetails><fare>






</freeTextQualification><description>LAST TKT DTE*10JUL14* - SEE ADV PURCHASE</description>


<segmentRef>





Page 560 of 714



<rbd>Z</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>ZLWGDS13</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>


</productInformation><fareCalculationCodeDetails>

<qualifier>FCA</qualifier><amount>46.99</amount>

</fareCalculationCodeDetails></groupOfFares><groupOfFares>


<rbd>V</rbd>



<fareBasis>VLW1GDS</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>


</productInformation><fareCalculationCodeDetails>

<qualifier>FCA</qualifier>

<amount>397.7</amount></fareCalculationCodeDetails><fareCalculationCodeDetails>

<qualifier>Q</qualifier><amount>101.98</amount><locationCode>DUB</locationCode><otherLocationCode>JFK</otherLocationCode>

</fareCalculationCodeDetails></groupOfFares><majCabin>





Page 561 of 714




















</paxReference><passengerTaxDetails>





Page 562 of 714





<rate>13.93</rate><countryCode> AS</countryCode><type>UB</type>


<rate>2.53</rate><countryCode> AS</countryCode><type>UP</type>


<rate>7.50</rate><countryCode>DO</countryCode><type>UQ</type>

</taxDetails>

<taxDetails><rate>4.05</rate><countryCode> AE</countryCode><type>YC</type>


<rate>12.88</rate><countryCode> AS</countryCode><type>US</type>


<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>





Page 563 of 714



</freeTextQualification><description>LAST TKT DTE*05DEC14* - DATE OF ORIGIN</description>









<rbd>Y</rbd>



<fareBasis>Y1JB</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>






<fareBasis>Y1JB</fareBasis><passengerType> ADT</passengerType>





Page 565 of 714







</paxReference><passengerTaxDetails>





<rate>55.93</rate><countryCode> AS</countryCode><type>UB</type>


<rate>4.05</rate><countryCode> AE</countryCode><type>YC</type>


<rate>12.88</rate><countryCode> AS</countryCode>

<type>US</type></taxDetails><taxDetails>

<rate>3.68</rate><countryCode>CO</countryCode><type>XA</type>


<rate>5.15</rate><countryCode>CR</countryCode>





Page 566 of 714

<type>XY</type></taxDetails>

</passengerTaxDetails><fare>



</freeTextQualification><description>LAST TKT DTE*05DEC14* - DATE OF ORIGIN</description>







</segmentRef>

<groupOfFares><productInformation>



<fareBasis>Y1JB</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>

</fareProductDetail><breakPoint>Y</breakPoint></productInformation><fareCalculationCodeDetails>

<qualifier>FCA</qualifier><amount>1481.97</amount>

</fareCalculationCodeDetails><fareCalculationCodeDetails>

<qualifier>M</qualifier></fareCalculationCodeDetails>





Page 567 of 714












Page 568 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.















<locationId>NYC</locationId></arrivalPointDetails></arrivalLocalization><timeDetails>








Page 569 of 714


<Fare_MasterPricerTravelBoardSearchReply xmlns="http://xml.amadeus.com/FMPTBR_16_1_1A" ><conversionRate>










<ref>FI</ref><unitQualifier>MCX</unitQualifier>







<locationId>KEF</locationId></location><companyId>







Page 570 of 714

<equipmentType>75T</equipmentType></productDetail><addProductDetail>







<locationId>KEF</locationId></location><location>



<marketingCarrier>FI</marketingCarrier>

<operatingCarrier>FI</operatingCarrier></companyId><flightOrtrainNumber>613</flightOrtrainNumber><productDetail>




</flightDetails>

</groupOfFlights><groupOfFlights><propFlightGrDetail>




</flightProposal>





Page 571 of 714

<flightProposal><ref> AA</ref><unitQualifier>MCX</unitQualifier>










</companyId>






</flightIndex>

<recommendation><itemNumber><itemNumberId>




</monetaryDetail>





Page 572 of 714













<transportStageQualifier>V</transportStageQualifier><company>FI</company>





<amount>147</amount></monetaryDetails><monetaryDetails>








Page 573 of 714





</freeTextQualification><description>SUBJ TO CANCELLATION/CHANGE PENALTY</description>




</freeTextQualification><description>LAST TKT DTE</description><description>01FEB12</description>





<rbd> A</rbd><cabin>W</cabin><avlStatus>6</avlStatus>


<fareBasis> AQO3PLUS</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

</fareProductDetail><breakPoint>N</breakPoint><contextDetails>

<availabilityCnxType>N</availabilityCnxType></contextDetails>







Page 574 of 714

<rbd> A</rbd><cabin>W</cabin><avlStatus>4</avlStatus>


<fareBasis> AQO3PLUS</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

</fareProductDetail><breakPoint>Y</breakPoint><contextDetails>














<amount>0</amount></monetaryDetail><monetaryDetail>








Page 575 of 714




<transportStageQualifier>V</transportStageQualifier><company> AA</company>







</monetaryDetails></paxFareDetail>







<description>LAST TKT DTE</description><description>26FEB12</description></pricingMessage>









Page 576 of 714

<cabinProduct><rbd>H</rbd><cabin>M</cabin><avlStatus>7</avlStatus>


<fareBasis>H2</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

</fareProductDetail><breakPoint>Y</breakPoint><contextDetails>










Page 577 of 714

5.96 Operation: 09.04 Output Option - In-Flight ServicesThe 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).










<priceType>IFS</priceType></pricingTicketing>














Page 578 of 714






















<locationId>LHR</locationId>





Page 579 of 714






</addProductDetail></flightInformation><flightCharacteristics>

<inFlightSrv>18</inFlightSrv><inFlightSrv>16</inFlightSrv><inFlightSrv>5</inFlightSrv><inFlightSrv>12</inFlightSrv>

</flightCharacteristics></flightDetails>








<monetaryDetail><amountType>YQ</amountType><amount>0.00</amount>









Page 580 of 714

























Page 581 of 714




</freeTextQualification><description>LAST TKT DTE 15NOV14</description>





<rbd>M</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>MWKWFR</fareBasis><passengerType> ADT</passengerType>












Page 582 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".








<companyIdentity><carrierQualifier>M</carrierQualifier><carrierId>IB</carrierId>




<departurePoint><locationId>BCN</locationId>











Page 583 of 714





<subType> A</subType></dataTypeInformation>

</feeInfo></feeDetails>









Page 584 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 lowestrecommendations: this is the pulled mode POL option. In the Pushed mode, PUS option, the ancillary servicesare displayed but not taken into account in the determination of the lowest recommendations.






















Page 585 of 714



<type>OC</type></carrierFeeDetails><otherSelectionDetails>

<option>POL</option></otherSelectionDetails>



<subType> A</subType></dataTypeInformation>










Page 586 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.












<departurePoint><locationId> ALC</locationId>


<arrivalPointDetails><locationId>VLC</locationId>









Page 587 of 714



<departurePoint><locationId>VLC</locationId>


<arrivalPointDetails><locationId> ALC</locationId>







</feeTypeInfo>


<dataTypeInformation><subType> AAA</subType>











Page 588 of 714

5.100 Operation: 10.04 Ancillary Services option - Inclusion/Exclusion optionThis option allows to include or exclude one sub-code. Inclusion is the default mode, and can be omitted.




</unitNumberDetail>






</companyIdentity>




<departurePoint><locationId> ALC</locationId>












Page 589 of 714




<arrivalPointDetails><locationId> ALC</locationId>









<subType> AAA</subType><option>IN</option>


</feeDetails><feeDetails>


<subType>BBB</subType><option>EX</option>

</dataTypeInformation></feeInfo></feeDetails>



5.100.3 Possible ErrorsSee "Error Messages" section.





Page 590 of 714

5.101 Operation: 10.05 Ancillary Services option - pulled/pushed mode atsub-code levelThis operation allows to specify for each service request if it should be processed in a pushed (informativemode) 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.




















Page 591 of 714





<type>OC</type></carrierFeeDetails><otherSelectionDetails>

<option>PUS</option></otherSelectionDetails>



<subType> AAA</subType><option>IN</option>

</dataTypeInformation><dataInformation>

<indicator>POL</indicator></dataInformation>

</feeInfo>



<subType>BBB</subType></dataTypeInformation><dataInformation>



<feeInfo><dataTypeInformation><subType>CCC</subType>


<indicator>PUS</indicator></dataInformation>






Page 592 of 714


<subType>DDD</subType><option>IN</option>


<indicator>PUS</indicator></dataInformation>



<subType>EEE</subType></dataTypeInformation>









Page 593 of 714

5.102 Operation: 10.06 Ancillary Services option - Service coverage optionThis 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.





<numberOfUnits>1</numberOfUnits><typeOfUnit>INV</typeOfUnit>















Page 594 of 714


<locationId>FRA</locationId></arrivalPointDetails>
















</feeTypeInfo>

<feeDetails><feeInfo><dataTypeInformation>

<subType> AAA</subType></dataTypeInformation><dataInformation>

<indicator>COF</indicator></dataInformation>






Page 595 of 714


<dataTypeInformation><subType>BBB</subType>


<indicator>COI</indicator></dataInformation>



<subType>CCC</subType></dataTypeInformation><dataInformation>

<indicator>COB</indicator></dataInformation>



<subType>DDD</subType></dataTypeInformation>

<dataInformation><indicator>CIS</indicator>

</dataInformation></feeInfo>



<subType>EEE</subType></dataTypeInformation><dataInformation>

<indicator>CIB</indicator>

</dataInformation></feeInfo></feeDetails>








Page 596 of 714

5.103 Operation: 10.07 Ancillary Services option - coverage option and pulledmodeThis example shows how to combine coverage option and pulled mode option at service level.

NOTE: the pulled mode option is not yet available.










<carrierId>IB</carrierId></companyIdentity>










</itinerary>





Page 597 of 714














<subType> AAA</subType></dataTypeInformation><dataInformation>

<indicator>COF</indicator></dataInformation><dataInformation>


</feeInfo></feeDetails></feeOption>









Page 598 of 714

5.104 Operation: 10.08 Ancillary Services option - Request a service groupThis example shows how to request an entire service group.

A group contains several sub-groups, which contain several ancillary services themselves.























Page 599 of 714












</feeTypeInfo>


<dataTypeInformation><subType>UNK</subType>

</dataTypeInformation></feeInfo><feeDescriptionGrp>


<number>1</number></itemNumberDetails>

</itemNumberInfo>

<serviceDescriptionInfo><serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceGroup>UN</serviceGroup>

</serviceRequirementsInfo></serviceDescriptionInfo>

</feeDescriptionGrp></feeDetails>






Page 600 of 714








Page 601 of 714

5.105 Operation: 10.09 Ancillary services option - Request a service sub-groupThis example shows how to request a service sub-group.























Page 602 of 714












</feeTypeInfo>


<dataTypeInformation><subType>UNK</subType>




</itemNumberInfo>

<serviceDescriptionInfo><serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceSubGroup> AS</serviceSubGroup>








Page 603 of 714








Page 604 of 714

5.106 Operation: 10.10 Ancillary services option - Request combining servicegroup, sub-group and sub-codeThis request shows how to include UN group, exclude AS sub-group and include CCC sub-code.























Page 605 of 714












</feeTypeInfo>


<dataTypeInformation><subType>UNK</subType><option>IN</option>




</itemNumberInfo><serviceDescriptionInfo><serviceRequirementsInfo>

<serviceClassification>F</serviceClassification><serviceGroup>UN</serviceGroup>


</feeDescriptionGrp></feeDetails><feeDetails>





Page 606 of 714


<subType>UNK</subType><option>EX</option>




</itemNumberInfo><serviceDescriptionInfo>

<serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceSubGroup> AS</serviceSubGroup>




<subType>CCC</subType><option>IN</option>











Page 608 of 714

















<subType>UNK</subType></dataTypeInformation>

</feeInfo><feeDescriptionGrp><itemNumberInfo>


</itemNumberDetails></itemNumberInfo><serviceDescriptionInfo>

<serviceRequirementsInfo><serviceClassification>UNK</serviceClassification>





Page 609 of 714

<serviceGroup>SA</serviceGroup></serviceRequirementsInfo><seatDetails>

<seatCharacteristics>W</seatCharacteristics><seatCharacteristics>E</seatCharacteristics>

</seatDetails></serviceDescriptionInfo>










Page 610 of 714

5.108 Operation: 10.12 Ancillary Services option - Multi Passengers requestIn case of a multi passenger request, it is important to note that the monetary information will be returned bypassenger type and not by passenger.

So the data returned in the Passenger Reference Information of the Service Fee are not relevant, only thePassenger Reference Information for which the service apply is meaningful.



<unitNumberDetail>







</traveller><traveller>




<ptc>MIL</ptc><traveller>









Page 611 of 714



<departurePoint><locationId>PMI</locationId>









</feeTypeInfo>


<dataTypeInformation><subType>TDA</subType>


<indicator>PUS</indicator></dataInformation><dataInformation>


</feeInfo>

</feeDetails></feeOption></Fare_MasterPricerTravelBoardSearch>




</status>





Page 612 of 714















<locationId>PMI</locationId></location><location>

<locationId>MAD</locationId>


<marketingCarrier>IB</marketingCarrier><operatingCarrier>IB</operatingCarrier>







Page 613 of 714














<locationId>PMI</locationId></location><location>

<locationId>MAD</locationId><terminal>4</terminal>


<marketingCarrier>IB</marketingCarrier><operatingCarrier>IB</operatingCarrier></companyId><flightOrtrainNumber>797</flightOrtrainNumber><productDetail>







Page 614 of 714


















<refQualifier>OC</refQualifier><refNumber>1</refNumber></referencingDetail>

</segmentFlightRef><segmentFlightRef>







Page 615 of 714

<refQualifier>OC</refQualifier><refNumber>1</refNumber>










</monetaryDetails>






<traveller><ref>4</ref></traveller><traveller>








Page 616 of 714






</freeTextQualification><description>LAST TKT DTE 22SEP10</description>











<fareBasis>NDU7OW</fareBasis>

<passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>








Page 617 of 714










<ptc>MIL</ptc><traveller>

<ref>6</ref>







</freeTextQualification><description>LAST TKT DTE</description><description>22SEP10</description>






Page 618 of 714


<textSubjectQualifier> APM</textSubjectQualifier><informationType>5</informationType>

</freeTextQualification><description>NOT FARED AT PASSENGER TYPE REQUESTED </description><description>5</description>











<fareBasis>NDU7OW</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>



</groupOfFares></fareDetails></paxFareProduct>




</serviceTypeInfo>





Page 619 of 714

<serviceFeeRefGrp><refInfo>

<referencingDetail><refQualifier>OC</refQualifier><refNumber>1</refNumber>


<refQualifier>OCM</refQualifier><refNumber>1</refNumber>


<refQualifier>OCC</refQualifier><refNumber>1</refNumber>


</serviceFeeRefGrp><serviceCoverageInfoGrp>


<number>1</number><type>OCC</type>

</itemNumber></itemNumberInfo><serviceCovInfoGrp>

<paxRefInfo>

<travellerDetails><referenceNumber>2</referenceNumber>

</travellerDetails></paxRefInfo><coveragePerFlightsInfo>




</coveragePerFlightsInfo><refInfo><referencingDetail>



</serviceCovInfoGrp></serviceCoverageInfoGrp><globalMessageMarker/>





Page 620 of 714

<serviceFeeInfoGrp><itemNumberInfo>

<itemNumber><number>1</number><type>OCM</type>

</itemNumber></itemNumberInfo><serviceDetailsGrp>

<refInfo><referencingDetail>


</referencingDetail></refInfo><serviceMatchedInfoGroup>


<referenceNumber>2</referenceNumber></travellerDetails>

</paxRefInfo><pricingInfo>

<fareDetails><passengerTypeQualifier>MIL</passengerTypeQualifier>

</fareDetails></pricingInfo>

<amountInfo><monetaryDetail>

<typeQualifier>PU</typeQualifier><amount>8.00</amount>

</monetaryDetail></amountInfo>

</serviceMatchedInfoGroup></serviceDetailsGrp>

</serviceFeeInfoGrp><serviceDetailsGrp>


<subType>TDA</subType></dataTypeInformation><dataInformation>




<number>1</number>





Page 621 of 714

<type>SD</type></itemNumberDetails>

</itemNumberInfo><serviceAttributesInfo>

<attributeDetails><attributeType>SSR</attributeType><attributeDescription>IEVG</attributeDescription>

</attributeDetails></serviceAttributesInfo><serviceDescriptionInfo>

<serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceNumberOfInstances>1</serviceNumberOfInstances><serviceMarketingCarrier>IB</serviceMarketingCarrier><serviceGroup>IE</serviceGroup><serviceSubGroup>VG</serviceSubGroup>


</feeDescriptionGrp></serviceDetailsGrp>

</serviceFeesGrp></Fare_MasterPricerTravelBoardSearchReply>







Page 622 of 714

5.109 Operation: 10.13 Ancillary Services option - Combination of all possibleoptionsThis example shows a complex request with all available options.























Page 623 of 714












</feeTypeInfo>


<dataTypeInformation><subType>UNK</subType><option>IN</option>


<indicator>COF</indicator></dataInformation>

</feeInfo><feeDescriptionGrp>

<itemNumberInfo>

<itemNumberDetails><number>1</number></itemNumberDetails>


<serviceRequirementsInfo><serviceClassification>UNK</serviceClassification><serviceGroup>UN</serviceGroup>






Page 624 of 714



<subType>PCC</subType><option>EX</option>




<subType>UNK</subType><option>EX</option>


<indicator>COB</indicator></dataInformation>

</feeInfo><feeDescriptionGrp>




<serviceRequirementsInfo><serviceClassification>UNK</serviceClassification><serviceSubGroup>MR</serviceSubGroup>




<subType>SEA</subType></dataTypeInformation><dataInformation>

<indicator>CBS</indicator></dataInformation>







Page 625 of 714








Page 626 of 714

5.110 Operation: 11.1 - OB fees with connections

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









</paxReference>

<travelFlightInfo><flightDetail>

<flightType>N</flightType><flightType>D</flightType>













Page 627 of 714












<typeOfUnit>C</typeOfUnit></unitNumberDetail>

</flightInfo></itinerary>









Page 628 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 solutionswon't be returned in output.














<unitNumberDetail><numberOfUnits>1</numberOfUnits><typeOfUnit>NRA</typeOfUnit>





</departurePoint>





Page 629 of 714
























Page 630 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


<Fare_MasterPricerTravelBoardSearch xmlns="http://xml.amadeus.com/FMPTBQ_16_1_1A" ><passengerInfoGrp>

<passengerReference><segmentControlDetails>

<quantity>1</quantity></segmentControlDetails>

</passengerReference><psgDetailsInfo>

<discountPtc><valueQualifier> ADT</valueQualifier><value>39</value>

</discountPtc><flequentFlyerDetails>

<frequentTravellerDetails><carrier>FRR</carrier><tierDescription>SENIO</tierDescription>

</frequentTravellerDetails><frequentTravellerDetails>

<carrier>FRR</carrier><tierDescription>ESCA</tierDescription>

</frequentTravellerDetails>

</flequentFlyerDetails></psgDetailsInfo><psgDetailsInfo>

<discountPtc><valueQualifier>IN</valueQualifier><value>0</value>

</discountPtc></psgDetailsInfo>

</passengerInfoGrp></Fare_MasterPricerTravelBoardSearch>





Page 631 of 714







Page 632 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.

• Passenger 1 (adult with infant):◦ ADT◦ 39 years old◦ with infant of 10 months => no seat◦ Rail Card Senior ◦ Rail Card Escapade

• Passenger 2 (child)◦ CH◦ 2 years old



<passengerReference>

<segmentControlDetails><quantity>1</quantity>

</segmentControlDetails></passengerReference><psgDetailsInfo>






</frequentTravellerDetails></flequentFlyerDetails>

</psgDetailsInfo><psgDetailsInfo>

<discountPtc><valueQualifier>IN</valueQualifier>





Page 633 of 714

<value>0</value></discountPtc>

</psgDetailsInfo></passengerInfoGrp><passengerInfoGrp>




<discountPtc><valueQualifier>CH</valueQualifier><value>2</value>









Page 634 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).

• Passenger 1 (adult with infant):

◦ 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















Page 635 of 714

</frequentTravellerDetails></flequentFlyerDetails>

</psgDetailsInfo><psgDetailsInfo>

<discountPtc><valueQualifier>IN</valueQualifier><value>1</value>


</passengerInfoGrp><passengerInfoGrp>




<discountPtc><valueQualifier>CH</valueQualifier><value>2</value>


</passengerInfoGrp><passengerInfoGrp>

<passengerReference>

<segmentControlDetails><quantity>3</quantity>

</segmentControlDetails></passengerReference><psgDetailsInfo>

<discountPtc><valueQualifier>MIL</valueQualifier>


<frequentTravellerDetails><carrier>FRR</carrier><tierDescription>ESCA</tierDescription>

</frequentTravellerDetails></flequentFlyerDetails></psgDetailsInfo>








Page 636 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 OfficeID 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 Familyname at requested segment level are returned.• When option 3 is requested, Fare Family name at Fare component level and resulting Fare Familyname 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 doesn’t 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 samecontrolling 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: Bag-Seat – 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 nameand description at requested segment level.

The reply illustrates 1 recommendation with 2 requested segments and 3 fare components. First requestedsegment 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 Familyreference

Fare Family name Fare Family carrier

NCE-NYC NCE-NYC 1 FFAM1 6X

NYC-LON 2 FFAM2 6XNYC-LON-NCE

LON-NCE 3 FFAM3 6X

Resulting Fare family name at requested segment level (fareFamilyRef)





Page 637 of 714

Requested segment Fare Family reference Fare Family name Fare Family carrier

NCE-NYC 1 FFAM1 6X

NYC-LON-NCE 2 FFAM2 6X

Fare family description (familyInformation) and list of services (serviceFeesGrp)

Fare Family reference 1 2

Fare family Name FFAM1 FFAM2

Fare Family carrier 6X 6X

Short description FARE FAMILY 1 FARE FAMILY 2List of services

Service reference

Sub code

Group

Classification

Commercial name

1

0AT

ML - Meal/Beverage

F - Flight related

SNACK

Included Included

Service reference

Sub code

Group

Classification

Commercial name

2

SS1

SA - Seat

F - Flight related

SEAT SELECTION

Included At charge

Service reference

Sub code

Group

Classification

Commercial name

3

0C3

BG - Baggage

F - Flight related

UPTO50LB 23KG

BAGGAGE

Included Not offered

Service reference

Sub code

Group

Classification

Commercial name

4

NRF

TS - Travel Services

F - Flight related

NOT REFUNDABLE

Included





Page 638 of 714






</unitNumberDetail>





















Page 639 of 714


















</conversionRateDetail></conversionRate><familyInformation>

<refNumber>1</refNumber><fareFamilyname>FFAM1</fareFamilyname><description>FARE FAMILY 1</description><carrier>6X</carrier><services>

<reference>1</reference>





Page 640 of 714

<status>INC</status></services><services>







<refNumber>2</refNumber><fareFamilyname>FFAM2</fareFamilyname><description>FARE FAMILY 2</description><carrier>6X</carrier><services>



<reference>2</reference><status>CHA</status>


<reference>3</reference><status>NOF</status>


<refNumber>3</refNumber><fareFamilyname>FFAM3</fareFamilyname><carrier>6X</carrier>

</familyInformation><flightIndex><requestedSegmentRef>








Page 641 of 714











</location>





</addProductDetail>

</flightInformation></flightDetails></groupOfFlights>









Page 642 of 714











</location>

<location><locationId>LHR</locationId><terminal>3</terminal>




<equipmentType>76W</equipmentType></productDetail>

<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier>LCA</productDetailQualifier>









Page 643 of 714

















<referencingDetail><refQualifier>F</refQualifier>





</monetaryDetail>





Page 644 of 714

















<company>7X</company>

</codeShareDetails><monetaryDetails><amountType>YQ</amountType><amount>28.00</amount>








Page 645 of 714














</freeTextQualification><description>LAST TKT DTE</description><description>14JUL14</description><description> - SEE ADV PURCHASE</description>



</segmentRef>




<fareBasis>FB1</fareBasis><passengerType> ADT</passengerType>





Page 646 of 714












<rbd>Y</rbd>



<fareBasis>FB2</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>



<referencingDetail>

<refQualifier>F</refQualifier><refNumber>2</refNumber></referencingDetail>

</fareFamiliesRef></groupOfFares><groupOfFares>


<rbd>B</rbd><cabin>M</cabin>





Page 647 of 714














</serviceTypeInfo><globalMessageMarker/><serviceDetailsGrp>


<subType>0AT</subType></dataTypeInformation>

</serviceOptionInfo>

<feeDescriptionGrp><itemNumberInfo><itemNumberDetails>



<serviceRequirementsInfo><serviceClassification>F</serviceClassification>





Page 648 of 714

<serviceGroup>ML</serviceGroup></serviceRequirementsInfo>

</serviceDescriptionInfo><commercialName>


</freeTextQualification><freeText>SNACK</freeText>




<subType>SS1</subType></dataTypeInformation>





<serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceGroup>SA</serviceGroup>

</serviceRequirementsInfo></serviceDescriptionInfo><commercialName>


</freeTextQualification><freeText>SEAT SELECTION</freeText>


</serviceDetailsGrp><serviceDetailsGrp><serviceOptionInfo>

<dataTypeInformation><subType>0C3</subType>

</dataTypeInformation></serviceOptionInfo><feeDescriptionGrp>






Page 649 of 714



<serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceGroup>BG</serviceGroup>

</serviceRequirementsInfo></serviceDescriptionInfo><commercialName>


</freeTextQualification><freeText>UPTO50LB 23KG BAGGAGE</freeText>




<subType>NRF</subType></dataTypeInformation>





<serviceRequirementsInfo><serviceClassification>F</serviceClassification><serviceGroup>TS</serviceGroup>


<commercialName><freeTextQualification><textSubjectQualifier>3</textSubjectQualifier>

</freeTextQualification><freeText>NOT REFUNDABLE</freeText>


</serviceDetailsGrp></serviceFeesGrp>






Page 650 of 714


informationinformationproduct

faredescriptionmessage

informationoptionmessage





Page 651 of 714

5.116 Operation: 13.2 Airline Fare Family name and descriptionIn this example, the user requests Fare Family name at Fare component level and resulting Fare Family nameat requested segment level.

In case all or some flights within a proposed segment are not matching any airline fare family, no resultingairline fare family information is returned for the whole proposed segment.

Recommendation PAR-HEL HEL-PAR

1 No resulting fare family No resulting fare family

2 No resulting fare family Resulting fare family BASIC

3 Resulting fare family BASIC Resulting fare family CLASSIC

4 Resulting fare family BASIC No resulting fare family










<pricingTickInfo/><feeIdDescription>










Page 652 of 714




<arrivalPointDetails><locationId>HEL</locationId>







<departurePoint><locationId>HEL</locationId>









<Fare_MasterPricerTravelBoardSearchReply xmlns="http://xml.amadeus.com/FMPTBR_16_1_1A" ><conversionRate>


</conversionRateDetail></conversionRate><familyInformation>






Page 653 of 714

<fareFamilyname>BASIC</fareFamilyname><carrier>6X</carrier>

</familyInformation><familyInformation>

<refNumber>2</refNumber><fareFamilyname>CLASSIC</fareFamilyname><carrier>7X</carrier>

</familyInformation><flightIndex>








</flightProposal>





<locationId>CDG</locationId><terminal>2D</terminal>

</location><location><locationId>HEL</locationId><terminal>2</terminal>








Page 654 of 714

















<locationId>HEL</locationId><terminal>2</terminal></location><companyId>








Page 655 of 714
















<locationId>HEL</locationId><terminal>2</terminal>

</location><companyId><marketingCarrier>7X</marketingCarrier><operatingCarrier>6X</operatingCarrier>







Page 656 of 714













<flightDetails><flightInformation>




</location>

<location><locationId>CDG</locationId><terminal>2D</terminal>








Page 657 of 714

<equipmentType>E90</equipmentType></productDetail><addProductDetail>










<flightInformation>





<locationId>CDG</locationId>

<terminal>2D</terminal></location><companyId>








Page 658 of 714

<addProductDetail><electronicTicketing>Y</electronicTicketing><productDetailQualifier> AIP</productDetailQualifier>
















</location>









Page 660 of 714

<codeShareDetails><transportStageQualifier>V</transportStageQualifier><company>7X</company>

















<pricingMessage>


</freeTextQualification><description>LAST TKT DTE 31JUL14 - SEE ADV PURCHASE</description>







Page 661 of 714

















</fareProductDetail><breakPoint>Y</breakPoint></productInformation>




</fareDetails>





Page 662 of 714

















</monetaryDetail></recPriceInfo>

<segmentFlightRef><referencingDetail><refQualifier>S</refQualifier><refNumber>2</refNumber>








Page 663 of 714












</paxFareDetail>







<description>TICKETS ARE NON-REFUNDABLE</description></pricingMessage></fare><fare>



</freeTextQualification><description>LAST TKT DTE</description>





Page 664 of 714

<description>29JUL14</description><description> - SEE ADV PURCHASE</description>
















<rbd>O</rbd>

<cabin>M</cabin><avlStatus>4</avlStatus></cabinProduct><fareProductDetail>








Page 665 of 714

<fareFamiliesRef><referencingDetail>


















<monetaryDetail><amountType>YQ</amountType><amount>0.00</amount>









Page 666 of 714

















</paxFareDetail><paxReference><ptc> ADT</ptc><traveller>








Page 667 of 714

















</referencingDetail></fareFamiliesRef></groupOfFares><majCabin>








Page 668 of 714


















</itemNumber><fareFamilyRef><referencingDetail>




</fareFamilyRef>





Page 669 of 714

<recPriceInfo><monetaryDetail>















<company>6X</company></codeShareDetails><monetaryDetails>




</monetaryDetails>





Page 670 of 714












<pricingMessage>






<productInformation><cabinProduct><rbd>Z</rbd><cabin>M</cabin><avlStatus>9</avlStatus>







Page 671 of 714












<rbd>O</rbd><cabin>M</cabin>






<designator>M</designator></bookingClassDetails></majCabin>








Page 672 of 714

5.117 Operation: 14.0 Free Baggage AllowanceThis feature of Master Pricer provides the information about the free baggage allowed for eachrecommendation.

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:

Free baggage allowed Applicability

First recommendation with sameFBA for the whole itinerary

BCN-MAD 23 Kg

MAD-IBZ-VLC 23 Kg

23 kg on Requested segment 1 – Leg 1

23 kg on Requested segment 2 – Leg 1 and 2

Second recommendation with

different FBA

BCN-MAD 1PC

MAD- VLC 2 PC

1P on Requested segment 1 – Leg

1

2P on Requested segment 2 – Leg1

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 allowancereference)• 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:

Passenger type reference Flight coverage Reference to FBA

Baggage coverage #1 1 Requested segment 1 – Leg 1

Requested segment 2 – Leg 1 and 2

FBA #1





Page 673 of 714

Baggage coverage #2 1 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











<pricingTickInfo/><feeIdDescription>

<feeId><feeType>FBA</feeType><feeIdNumber>1</feeIdNumber>










Page 674 of 714












</departurePoint>






</itinerary>










Page 675 of 714

















</location><companyId><marketingCarrier>6X</marketingCarrier><operatingCarrier>6X</operatingCarrier>







Page 676 of 714

<electronicTicketing>Y</electronicTicketing></addProductDetail>
















<marketingCarrier>6X</marketingCarrier>

<operatingCarrier>6X</operatingCarrier></companyId><flightOrtrainNumber>1511</flightOrtrainNumber><productDetail>



</flightInformation>





Page 677 of 714

















<locationId>IBZ</locationId></location><companyId>

<marketingCarrier>6X</marketingCarrier><operatingCarrier>7X</operatingCarrier></companyId><flightOrtrainNumber>8910</flightOrtrainNumber><productDetail>







Page 678 of 714





<locationId>IBZ</locationId></location><location>

<locationId>VLC</locationId></location><companyId>









<ref>0055</ref>









Page 679 of 714
















</monetaryDetail>









Page 680 of 714











<codeShareDetails><transportStageQualifier>V</transportStageQualifier><company>6X</company>





</monetaryDetails>





<ptc> ADT</ptc>





Page 681 of 714









</freeTextQualification><description>LAST TKT DTE 05OCT13</description>









<cabinProduct><rbd>O</rbd><cabin>M</cabin><avlStatus>9</avlStatus>


<fareBasis>ODSV</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>





Page 682 of 714











<fareBasis>PD</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType>

<fareType>ET</fareType></fareProductDetail><breakPoint>Y</breakPoint>




</cabinProduct>

<fareProductDetail><fareBasis>PD30</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>







Page 683 of 714


















</referencingDetail><referencingDetail><refQualifier>S</refQualifier><refNumber>2</refNumber>








Page 684 of 714












</paxFareDetail>







<description>TICKETS ARE NON-REFUNDABLE</description></pricingMessage></fare><fare>








Page 685 of 714











<fareBasis>ODSV</fareBasis><passengerType> ADT</passengerType>

<fareType>RP</fareType><fareType>ET</fareType>





</fareDetails>




<rbd>S</rbd><cabin>M</cabin><avlStatus>9</avlStatus>





Page 686 of 714


<fareBasis>SDA8OW</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>









</serviceTypeInfo><serviceCoverageInfoGrp>






</paxRefInfo><coveragePerFlightsInfo>





<numberOfItemsDetails>





Page 687 of 714

<referenceQualifier>RS</referenceQualifier><refNum>2</refNum>







</serviceCovInfoGrp></serviceCoverageInfoGrp><serviceCoverageInfoGrp>









<refOfLeg>1</refOfLeg>

</lastItemsDetails></coveragePerFlightsInfo><refInfo>



</serviceCovInfoGrp><serviceCovInfoGrp>





Page 688 of 714










</serviceCovInfoGrp></serviceCoverageInfoGrp><globalMessageMarker/><freeBagAllowanceGrp>

<freeBagAllownceInfo>

<baggageDetails><freeAllowance>23</freeAllowance><quantityCode>W</quantityCode><unitQualifier>K</unitQualifier>




</freeBagAllowanceGrp>

<freeBagAllowanceGrp><freeBagAllownceInfo><baggageDetails>








Page 689 of 714


</freeBagAllowanceGrp><freeBagAllowanceGrp>













Page 690 of 714

5.118 Operation: 14.1 Free Baggage Allowance with multiple passenger typesIn case of different passenger types are requested in the query of Master Pricer, the free baggage allowancealways provide the information of the ADT passenger type if present in the query. If no ADT passenger type isrequested, 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 Free baggage allowed Applicability

Recommendation withmultiple passenger types

ADT

CH

BCN-MAD 1P

MAD-IBZ-VLC 1P

1 piece on Requestedsegment 1 – Leg 1 and1 pice on Requestedsegment 2 – Leg 1 and 2

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 allowancereference )• Baggage allowance coverage reference at recommendation level

Baggage Allowance is detailed in freeBagAllowanceGrp:

FBA #1 1 pieceBaggage coverage is detailed in serviceCoverageInfoGrp:

Passenger type reference Flight coverage Reference to FBA

Baggage coverage #1 1 (ADT) Requested segment 1 – Leg 1

Requested segment 2 – Leg 1 and 2

FBA #1

Recommendation details:

Reference to Baggage coverage











Page 691 of 714














<locationId>BCN</locationId></departurePoint>









<departurePoint>





Page 692 of 714

<locationId>MAD</locationId></departurePoint>

























Page 693 of 714








<marketingCarrier>IB</marketingCarrier><operatingCarrier>IB</operatingCarrier>




<productDetailQualifier> AVR</productDetailQualifier></addProductDetail>






<flightProposal><ref>1</ref></flightProposal><flightProposal>








Page 694 of 714







<locationId>IBZ</locationId></location><companyId>

<marketingCarrier>IB</marketingCarrier><operatingCarrier>YW</operatingCarrier>


<equipmentType>CRK</equipmentType></productDetail>







<locationId>IBZ</locationId></location><location>


<marketingCarrier>IB</marketingCarrier>





Page 695 of 714

<operatingCarrier>YW</operatingCarrier></companyId><flightOrtrainNumber>8441</flightOrtrainNumber><productDetail>

















<amount>0.00</amount></monetaryDetail></recPriceInfo><segmentFlightRef>








Page 696 of 714

























Page 697 of 714














<fareBasis>ODSV</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>



</groupOfFares><majCabin><bookingClassDetails>








Page 698 of 714





<fareBasis>QD</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>






<fareBasis>PD30</fareBasis><passengerType> ADT</passengerType><fareType>RP</fareType><fareType>ET</fareType>




</bookingClassDetails>

</majCabin></fareDetails></paxFareProduct><paxFareProduct>







Page 699 of 714

<company>IB</company></codeShareDetails><monetaryDetails>

















<textSubjectQualifier>LTD</textSubjectQualifier>

<informationType>45</informationType></freeTextQualification><description>LAST TKT DTE 10OCT13</description>








Page 700 of 714








<fareBasis>ODSV</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType><fareType>ET</fareType>



<additionalFareDetails>

<ticketDesignator>CH</ticketDesignator></additionalFareDetails>

</ticketInfos></groupOfFares><majCabin>




<segmentRef>









Page 701 of 714

<fareBasis>QD</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType><fareType>ET</fareType>





</groupOfFares><groupOfFares>




<fareBasis>PD30</fareBasis><passengerType>CH</passengerType><fareType>RP</fareType><fareType>ET</fareType>







</bookingClassDetails></majCabin></fareDetails>

</paxFareProduct></recommendation><serviceFeesGrp>







Page 702 of 714

</serviceTypeInfo><serviceCoverageInfoGrp>











<numberOfItemsDetails><referenceQualifier>RS</referenceQualifier>

<refNum>2</refNum></numberOfItemsDetails><lastItemsDetails>




<referencingDetail><refQualifier>F</refQualifier>

<refNumber>1</refNumber></referencingDetail></refInfo>

</serviceCovInfoGrp></serviceCoverageInfoGrp><globalMessageMarker/><freeBagAllowanceGrp>


<freeAllowance>1</freeAllowance>





Page 703 of 714

<quantityCode>N</quantityCode></baggageDetails>

</freeBagAllownceInfo><itemNumberInfo>










Page 704 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/pricingprocess (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 pricefor one additional KG.

Recommendation 1 Recommendation 2 Recommendation 3 Recommendation 4

Airline in piece concept Airline in piece concept Airline in piece concept Airline in weight concept

FBA = 0 FBA = 1 FBA = 2 FBA >= 0

AAS bag occurrence 1 &2 returned*

AAS bag occurrence 1returned

No AAS bag returned Pricer per KG returned

FBA & AAS type P/C processed in Master Pricer are compliant with IATA resolution 302 & USDOT that regulate

the calculation of baggage (quantity and fees).* Important: only 1 occurrence of AAS baggage will be displayed until the activation of occurrence process incatalogue 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 thequery.

Free Baggage information will be automatically processed when baggage option is requested (even if FBA isnot activated). C.f. Free Baggage Allowance.

Each recommendation could be cut into several BTU (portion of travel on which one given carrier defines theunique applicable Baggage allowance and charges policy). In that case, FBA and AAS information will bereturned 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 705 of 714

AAS bag occurrence 1 is 10 euros& occurrence 2 is 12 euros

AAS bag occurrence 1 is 5 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 andbook/price Ancillary Services. This catalogue query should be limited to the portions of the itinerary where theat-charge baggage is necessary.

Example of itinerary Paris-London-Mexico:

Paris - London London – Mexico Airline in piece concept Airline in piece concept

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>

<priceType>BAG</priceType>

</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 onlyavailable until a certain time before the check-in. An AAS will be returned in type P only if the conditions arestill applicable. In service classification C, the baggage price will be the same at check-in time.





Page 706 of 714

• Recommendation

<referencingDetail>

<refQualifier>OC</refQualifier>

<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

<serviceCoverageInfoGrp>

<itemNumberInfo>

<itemNumber>

<number>2</number> <- AAS coverage reference

</itemNumber>

</itemNumberInfo>

<serviceCovInfoGrp>

<paxRefInfo>

<travellerDetails>





Page 707 of 714

<referenceNumber>1</referenceNumber> <- Passenger reference </travellerDetails>

</paxRefInfo>

<coveragePerFlightsInfo>

<numberOfItemsDetails>

<referenceQualifier>RS</referenceQualifier>

<refNum>1</refNum> <- Requested segment number

</numberOfItemsDetails>

<lastItemsDetails>

<refOfLeg>1</refOfLeg> <- Leg applicability: 1,2,3

</lastItemsDetails>

<lastItemsDetails>


</lastItemsDetails>

<lastItemsDetails>


</lastItemsDetails>

</coveragePerFlightsInfo>

<refInfo>

<referencingDetail> <refQualifier>F</refQualifier> <- AAS baggage reference



</refInfo>

</serviceCovInfoGrp>

</serviceCoverageInfoGrp>

• Price

<serviceMatchedInfoGroup>

<paxRefInfo>

<travellerDetails>

<referenceNumber>1</referenceNumber> <- AAS amount reference

</travellerDetails>

</paxRefInfo>

<pricingInfo>

<fareDetails>





Page 708 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>

</itemNumberDetails>

</itemNumberInfo>

<serviceAttributesInfo>

<attributeDetails>

<attributeType>RFIC</attributeType> <- RFIC

<attributeDescription>C</attributeDescription>

</attributeDetails>

<attributeDetails>

<attributeType>BKM</attributeType> <- Booking method

<attributeDescription>04</attributeDescription>

</attributeDetails>

</serviceAttributesInfo>

<serviceDescriptionInfo>





Page 709 of 714

<serviceRequirementsInfo> <serviceClassification>P</serviceClassification> <- Service classification

<serviceNumberOfInstances>1</serviceNumberOfInstances>

<serviceMarketingCarrier>BE</serviceMarketingCarrier> <- Service carrier

<serviceGroup>BG</serviceGroup> <- Service group

<serviceFreeText>B3</serviceFreeText> <- Service description

</serviceRequirementsInfo>

</serviceDescriptionInfo>

<commercialName>

<freeTextQualification>

<textSubjectQualifier>3</textSubjectQualifier>


<freeText>PREPAID MERCHO</freeText> <- Commercial Name

</commercialName>











<priceType>BAG</priceType></pricingTicketing>

</pricingTickInfo></fareOptions><travelFlightInfo>






Page 710 of 714

<carrierId>6X</carrierId></companyIdentity>

























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.








</paxReference>


<pricingTicketing><priceType>RP</priceType><priceType>RU</priceType>


<feeId><feeType>OPTDP</feeType><feeIdNumber>OPT MPLITE</feeIdNumber>



