AMADEUS PNR HISTORY

20 FEBRUARY2009

Amadeus Software Change

Notification

Amadeus PNR history enhancements

Product Name

Amadeus PNR History

Effective Date

3 August 2009

Overview
Amadeus is in the process of implementing several changes in the PNR history functionality. The
PNR history has evolved piece by piece since its creation to include customers' requirements, but
without having a global approach.

Amadeus has therefore worked at optimizing the product in order to have a more consistent
behavior and a clearer view on the actions done in the PNR. This is also an opportunity to solve
several problems that could not be solved in the past (because of technical constraints that do not
exist anymore).

Please find in attachment the list of all changes, with the original behavior along with
description and examples.

These changes only impact the display of the PNR history; the content (actions done in
the PNR and level of information) remains the same.

This notification is intended to inform Amadeus customers and external partners of structural
changes planned to be put in place on the Amadeus PNR history display and changes in
behaviour.

As these changes require some adaptation on impacted scripts/processes, this notification is sent
6 months in advance so that all involved can plan the required work accordingly. Please note that
we will not be able to delay this change, for technical reasons.

Page 1 of 8
Illustration

List of changes

1. Best effort display ....................................................................................................2

2. Security element change .........................................................................................3
3. Segment time change..............................................................................................3
4. Old package: Change segment code + original status code & segment indicators ..3
5. Name update/SSR handling ....................................................................................4
6. Name element change – element association .........................................................4
7. Name update – element association........................................................................5
8. Increase number in party .........................................................................................5
9. SSR FQTV display ..................................................................................................6
10. SSR OTHS – credit card concealment.....................................................................6
11. Infant surname not displayed...................................................................................7
12. Split - names display ...............................................................................................7
13. Name change – associated element........................................................................8

1. Best effort display

For technical reasons the PNR history records could be corrupted.

In case of error the old package does not manage to build the PNR history display. The new
package implements a best effort behaviour, displaying all the valid envelopes and an informative
message for the ones that are corrupted.

New package: Best effort display

Old package: No display

Informative message in blue

RP/MUC1A0701/MUC1A0701 BM/PR 27NOV08/1808Z

26XHB2
000 ON/AAA/PAX BBB/PAX CCC/PAX DDD/PAX
000 OS/6X 560 Y 20DEC 6 LHRMUC LK4 0600 0855/NN *1A/E*
New package 000 RF-MA/DCS-PUSHPAX CR-MUC1A0701 PR 9999BM 27NOV/1808Z
001 MISSING ENVELOPE
002 SP/DDD/PAX CCC/PAX BBB/PAX -26XHB3
002 RF-MA CR-MUC1A0701 PR 9999BM 27NOV/1808Z

Old package NO ELEMENT FOUND

Page 2 of 8
 2. Security element change
When a security element is changed, the new package follows the standard behaviour for change
transactions.

New package:

Change ES code + old value

Add ES code + new value

Old package:

Change ES code + new value

History codes in bold

Previous ES value in red
New ES value in blue

001/002 CE/R NCE1A099S

New package 001/002 AE/B NCE1A099S

Old package 001/002 CE/B NCE1A099S

3. Segment time change

When a schedule time change is detected for the segment, the activity is mapped with the correct
history code TC.

New package: Time change code + new/old schedule

4. Old package: Change segment code + original status code &

segment indicators
History codes in bold
New/old schedule in red
Original status code and segment indicator in blue

New package 000/001 TC/6X 797 C 26DEC 5 HELLHR TK1 1020 1135/ 0920 1035

Old package 000/001 CS/6X 797 C 26DEC 5 HELLHR TK1 1020 1135/HK *1A/E*

Page 3 of 8
 5. Name update/SSR handling
When an agent updates the name element, the standard PNR process does not remove the SSR
associated to element. The old package incorrectly reported an SSR cancellation.

New package:

Change name + old value

Add name + new value

Old package:

Change name + old value

Add name + new value

Cancel SSR code + SSR element

Cancel SSR element in red

000/002 CN/OLD/NAME
New package 000/002 AN/NEW/NAME

000/002 CN/OLD/NAME
Old package 000/002 AN/NEW/NAME
000/002 SX/SSR BIKE7SHN1

6. Name element change – element association

In case the agent changes the passenger name and an element associated to it during the same
transaction, the old package displays a wrong association between the old element value and
new name. The new package corrects this behaviour, displaying the correct association between
old element and old name.

New package:

Change name + old name

Add name + new name

Change element + old value + association to the old name

Add element + new value

Old package:

Change name + old name

Add name + new name

Change element + old value + association to the new name

Add element + new value

Wrong association – new name in red

Right association – old name in blue

000/002 CN/NAME/OLD
000/002 AN/NEWNAME/CHANGED
New package 001/002 CB/AB FREE-TEXT/NAME/TWO NAME/OLD
001/002 AB/AB MODIFIED AB/NAME/TWO

000/002 CN/NAME/OLD
000/002 AN/NEWNAME/CHANGED
Old package 001/002 CB/AB FREE-TEXT/NEWNAME/CHANGED NAME/TWO
001/002 AB/AB MODIFIED AB/NAME/TWO

Page 4 of 8
 7. Name update – element association
In case the agent updates the passenger name using NU entry, the normal PNR process keeps
the association with the linked elements. The old package displays a change in the elements
associated to the passenger. The new package corrects that behaviour, making the display
cleaner.

New package:

Change name + old name

Add name + new name

Old package:

Change name + old name

Add name + new name

Change element + old value

Add element + new value

Fake activity on the associated elements in red

000/002 CN/NAME/OLD
New package 000/002 AN/NEWNAME/CHANGED

000/002 CN/NAME/OLD
000/002 AN/NEWNAME/CHANGED
Old package 000/003 CB/AB MODIFIED AB/NAME/OLD
000/003 AB/AB MODIFIED AB/NEWNAME/CHANGED

8. Increase number in party

The new package corrects the wrong envelope mapping appearing after an increase number in
party in group PNRs. The old package does not the increase the envelope reference when a
segment is updated by an increase number in party.

New package: INP transaction increase the envelope reference

Old package: INP transaction does not increase the envelope reference

Wrong envelope number in red

Correct envelope number in blue

001 IS/6X1981 G 15DEC 1 LHRCDG NN5 0640 0900/SG E*

New package 001 RF-MA CR-MUC1A0701 PR 9999BM 17NOV/1738Z
001/002 XS/6X1981 G 15DEC 1 LHRCDG HN15 0640 0900/SG E*

001 IS/6X1981 G 15DEC 1 LHRCDG NN5 0640 0900/SG E*

Old package 001 RF-MA CR-MUC1A0701 PR 9999BM 17NOV/1738Z
000/002 XS/6X1981 G 15DEC 1 LHRCDG HN15 0640 0900/SG E*

Page 5 of 8
 9. SSR FQTV display
When an agent is allowed to see tier level, alliance and ACV information in the PNR, the new
package displays the same information in the history. In the old package the information was
never displayed.

New package: Display tier level, alliance and ACV information following the PNR format

Old package: Tier level, alliance and ACV information are not displayed

Tier level and ACV in red

New package OR/SSR FQTV6XHK/ 6X900429714/BASI-0/NAME SURNAME

Old package OR/SSR FQTV6XHK/ 6X900429714/NAME SURNAME

10. SSR OTHS – credit card concealment

When the SSR OTHS element contains a credit card number, the sensitive data are not
concealed by the old package. The new package corrects this behaviour, masking credit card
information.

New package: Credit card data masked in the SSR OTHS

Old package: Credit card data in clear in the SSR OTHS

Credit card number in red

Concealed Credit card number in blue

New package 000 OR/SSR OTHS6X CCVIXXXXXXXXXXXX0008/EXP05 13/MR WORKING

Old package 000 OR/SSR OTHSVA CCVI4434260000000008/EXP05 13/MR WORKING

Page 6 of 8
 11. Infant surname not displayed
When a PNR contains an infant passenger having the same surname of the adult passenger, the
new package does not repeat the information. If the infant surname differs from the adult one, it is
displayed.

New package:

The infant surname it is displayed only if it differs from the adult one.

Optional blank characters entered after the adult surname is removed.

Old package:

The infant surname is always displayed.

Optional blank char entered after the adult surname is kept.

Blank characters reported in the old package

Repeated adult/infant surname in red

New package 000 ON/SURNAME/A(INFDIFFERENT/DIFF) SURNAME/B(INF/SAME)

000 ON/SURNAME/A (INFDIFFERENT/DIFF) SURNAME/B(INFSURNAME/

Old package SAME)

12. Split - names display

The old package displays the passenger names of the child PNR in the SP-line of the parent PNR
following the inverse PNR display order. In the new package these names are displayed following
PNR display order.

New package: Names in PNR display order.

Old package: Names in inverse PNR display order.

PNR names display before the split

1.AAA/PAX 2.BBB/PAX 3.CCC/PAX 4.DDD/PAX

The agent splits last 3 passengers

SP2,4,3

New package 001 SP/BBB/PAX CCC/PAX DDD/PAX -26XHB3

Old package 001 SP/DDD/PAX CCC/PAX BBB/PAX -26XHB3

Page 7 of 8
 13. Name change – associated element
In case the agent changes the passenger name, the associated elements are removed by
standard PNR process. If the elements are associated to other passengers, they are kept in the
PNR and the passenger association is updated.

The old package maps it as a removal of the element, displaying only the passenger association
for which it is cancelled. The new package maps it as standard change activity, displaying the
change of the association.

New package:

Change element code + old passengers association

Add element code + new passengers association

Old package:

Remove element code + association to the old name

History codes in bold

Old name for which the association is broken in red

000/001 CN/HELLO/ANITA
000/001 AN/CHANGE/ANNIE
New package 000/001 CR/RM REMARK WITH ASSOC/HELLO/BOB HELLO/ANITA 000/001
AR/RM REMARK WITH ASSOC/HELLO/BOB

000/001 CN/HELLO/ANITA
Old package 000/001 AN/CHANGE/ANNIE
000/001 XR/RM REMARK WITH ASSOC/HELLO/ANITA

Page 8 of 8