-
Solutions
-
Airlines
-
Airports
-
Border Authorities
-
Corporate Travel & Expense
-
Integrations
-
Travel Sellers
-
-
Payments & e-invoicing
-
AI at AmadeusDriving integration, scalability, trust and integrity across the travel industry.
Learn more -
-
-
Support & Training
-
Already a customer?Log into My Amadeus Services for product news, learning materials, and customer support.
Login
-
-
-
Transforming travel with AIOur partnership with Microsoft accelerates our Cloud journey and unlocks new, AI‑powered innovations that strengthen and elevate the travel industry.
Learn more -
Landmark partnership between Amadeus and Google CloudLearn how this collaboration strengthens Amadeus' multi-cloud approach and AI innovation to improve efficiency, reliability and growth in travel.
Learn more
-
-
Resources
-
Trending Topics
-
Six travel trends that will redefine how we travel in 2026 and beyondAmadeus, in collaboration with Globetrender, unveils the tech, policy and innovation coming to transform the face of travel.
Discover now -
Airlines in the agentic age: use cases and ideas for getting started with AIBuilt on airline input, with Microsoft support, exploring real AI use cases.
Access whitepaper
-
-
Company
-
About Amadeus
-
Careers
-
Innovation
-
Sustainability
Learn how we’re working to make travel a force for good.
-
Amadeus Global ReportGain insights into Amadeus' 2025 business, financial performance, and sustainability.
Read the report -
-
-
Don’t you sometimes wish you could just step back in time? The good news is that thanks to Amadeus you can do just that… well, for PNRs in any case.
Every PNR that is created in the Amadeus System has associated historical information. The historical information is a record of the creation of the PNR and of any additions, modifications, cancellations, and deletions that you make. The System updates the PNR History at each End Of Transaction (EOT) entry. There is an exception: ''ARNK'' segments (Arrival Not Known) are not transferred to the PNR history.
In this latest Amadeus Tip, we’ll tell you exactly how to display the PNR history
- First, you must display the PNR
- Then you need to enter: RH
- You can choose to display a partial PNR history,by simply entering RH followed by the code for the type of element you want to see (E.g. RHA for air segments only) or you can also use a combination of option codesto retrieve multiple history types (E.g. RHN, J, R for name-phone-remark elements).
Note: for TTR historycryptic entries, refer to the related links section below.
The History display contains:
1. Sequence number for each modification which determines when changes occurred to a PNR
2. Historical code (2 letters) preceding every History element that identifies the actions taken
3. Flown Air and past-dated Auxiliary segments shown at the bottom of the display, numbered as they appear in the PNR
Explanation of the PNR History:
- PNR Header Line which always appears at the top of the PNR History.
- The last line of this display contains the Received From element <RF>. Received From elements reflectchanges made by agent's input, automatic processes or incoming teletype messages.
More examples of PNR History:
Segment cancellation
Changes to the home telephone number, then request a vegetarian meal (VGML)
Display specific elements from the PNR History: RHA (Air segments only)
RHG (OSI, SSR elements only)
When the display is too long...
- When the PNR History istoo long, you may get the following warning message:
- To display the remaining PNR history, enterRHfollowed by the last transaction number (049): RH049
Convert time
- The transaction was processed the 12aug at 13.48z
TO TOP