15.01.2015 Views

2008-01-03 EXST&CBBG requests included in name ... - Amadeus

2008-01-03 EXST&CBBG requests included in name ... - Amadeus

2008-01-03 EXST&CBBG requests included in name ... - Amadeus

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

AMADEUS PNR<br />

3JANUARY<strong>2008</strong><br />

<strong>Amadeus</strong> Product News<br />

Extra seat and cab<strong>in</strong> baggage <strong>requests</strong> <strong><strong>in</strong>cluded</strong> <strong>in</strong> the <strong>name</strong><br />

element<br />

Product Name<br />

<strong>Amadeus</strong> PNR<br />

Effective Date<br />

9 January <strong>2008</strong><br />

Overview<br />

When an extra seat (EXST) or cab<strong>in</strong> baggage (<strong>CBBG</strong>) exists <strong>in</strong> the <strong>name</strong>, at PNR end of<br />

transaction, the system will verify that the correspond<strong>in</strong>g SSR exists for each active flight<br />

segment present <strong>in</strong> the PNR (<strong>in</strong>stead of verify<strong>in</strong>g that there is one SSR exist<strong>in</strong>g for the complete<br />

it<strong>in</strong>erary).<br />

If the PNR does not conta<strong>in</strong> one SSR element per active flight segment present <strong>in</strong> the it<strong>in</strong>erary,<br />

an error message is displayed.<br />

Ma<strong>in</strong> Benefits<br />

This change is <strong>in</strong>troduced to correct an <strong>in</strong>consistency <strong>in</strong> <strong>Amadeus</strong>.<br />

Page 1 of 2


Illustration<br />

Current situation:<br />

When several segments are present <strong>in</strong> the PNR, at end of transaction the system checks whether<br />

one SSR <strong>CBBG</strong>/EXST is present which allows the PNR to be end transacted with one SSR<br />

request for one segment (which is segment and passenger associated) but not for the other<br />

segments:<br />

-- RLR ---<br />

RP/MUC1A07<strong>01</strong>/MUC1A07<strong>01</strong> BM/PR 23MAY07/0806Z ZHFOQU<br />

1.AA/A 2.AA/<strong>CBBG</strong><br />

3 6X34<strong>03</strong> J <strong>01</strong>JUL 7 CDGLHR HK2 2B 0740 0805 *1A/E*<br />

4 7X 302 J 10JUL 2 LHRCDG HK2 4 0620 0825 *1A/E*<br />

5 AP MUC - AMADEUS DEFAULT OFFICE - A<br />

6 TK OK23MAY/MUC1A07<strong>01</strong><br />

7 SSR <strong>CBBG</strong> 6X HN1 FREE TEXT/S3/P1<br />

Future situation (from 9 January 2007):<br />

When an EXST or <strong>CBBG</strong> exists <strong>in</strong> the <strong>name</strong> element, the system will at time of end of transaction<br />

check that the correspond<strong>in</strong>g SSR exists for each active flight segment present <strong>in</strong> the PNR,<br />

otherwise it is rejected with error response:<br />

RESTRICTED: NEED SSR EXST or NEED SSR <strong>CBBG</strong><br />

Information pages<br />

Please refer to the below HELP pages:<br />

<br />

HESSR<br />

Page 2 of 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!