Home โ€บ Blog โ€บ Amadeus ER Command: End Transaction & Redisplay

Amadeus ER Command: End Transaction & Redisplay

A complete guide to the ER command in Amadeus โ€” how to end the current transaction, save the PNR, and redisplay it in a single entry.

Every change made to a PNR only becomes permanent when the transaction is ended. Until then, the modifications exist only in the current session and can still be discarded. The ER command is the Amadeus entry that closes the transaction, saves all changes to the PNR, and immediately redisplays the updated record. It is one of the most frequently used commands in daily PNR management, and it plays a central role in almost every booking workflow. This guide explains what ER does, its syntax, and when it should be used.

What Does the ER Command Do?

ER is the Amadeus GDS command used to end the current transaction, save the PNR, and redisplay it.

Category: PNR Management.

It saves all changes made to the PNR, ends the current transaction, and then redisplays the updated PNR.

Two things happen in one entry: the changes are committed to the record, and the PNR appears on screen again so you can confirm the result. This makes ER both the saving command and the review step in a single action.

Syntax

Enter the command on its own after making changes to the PNR:

ER

This ends the current transaction, saves the changes made in the session, and redisplays the PNR so you can verify the result. Any element that was added, modified, or deleted during the session is now permanently saved.

When to Use ER

Use ER after creating or updating a PNR when you want to save your changes and immediately redisplay the PNR. Typical scenarios include:

  • Saving a newly created booking after all required elements have been added.
  • Ending the transaction after adding or modifying segments.
  • Saving passenger names, contact details, or frequent flyer information.
  • Committing seat requests, SSRs, or remarks to the PNR.
  • Saving changes after a rebooking or schedule change update.
  • Ending the transaction after pricing and reviewing the TST.
  • Confirming the result of any PNR modification on screen before moving on.

How ER Fits Into Your PNR Management Workflow

A typical session using ER might look like this:

  • Retrieve the PNR with RT or create a new booking.
  • Make the required changes โ€” add segments, update names, enter SSRs, add contact details, or price the itinerary.
  • Review the entries on screen to confirm they are correct.
  • Enter ER to save the changes and redisplay the PNR.
  • Check the redisplayed record to verify all elements are stored correctly.
  • If something is wrong, correct it with the appropriate entry โ€” for example XE to delete an element โ€” and end the transaction again with ER.

How ER Relates to Other End-of-Transaction Commands

  • ER โ†’ ends and saves the transaction, then redisplays the PNR.
  • ET โ†’ ends and saves the transaction without redisplaying the PNR.
  • ERK โ†’ ends the transaction, updates advice codes, and redisplays the PNR.
  • ETK โ†’ ends the transaction, updates advice codes, and files the PNR.
  • EF โ†’ ends the transaction and files a split PNR.
  • ERX โ†’ confirms AXR cancellation and redisplays the records.
  • ETX โ†’ confirms AXR cancellation and files the records.
  • IR โ†’ ignores the current transaction and redisplays the PNR.
  • IG โ†’ ignores the current transaction without redisplaying.

The distinction matters: ER saves and redisplays, ET saves without redisplaying, IR and IG discard unsaved changes. Choose the entry that matches your intent โ€” save, save silently, or discard.

Important: ER saves the transaction permanently. Once it has been entered, the changes cannot be discarded with IR or IG. If you are unsure whether the changes are correct, review the PNR on screen first โ€” or use IR to discard them before ending the transaction.

To remove a saved element after ER has been entered, use the appropriate deletion entry, such as XE for individual elements or XI for the full itinerary.

Frequently Asked Questions

What does the ER command do in Amadeus?

ER ends the current transaction, saves all changes made to the PNR, and redisplays the updated record.

What is the difference between ER and ET?

Both save the transaction. ET files the PNR without redisplaying it; ER brings the PNR back on screen after saving.

What is the difference between ER and ERK?

ERK also updates the advice codes on the affected segments before redisplaying. ER performs a standard save with redisplay.

Can I undo ER if I made a mistake?

No. ER saves the transaction permanently. You must correct the PNR with a new entry โ€” for example using XE to delete the affected element.

What if I want to discard my changes instead of saving?

Use IR to roll back and redisplay the PNR, or IG to roll back without redisplaying.

Conclusion

The ER command is the standard end-of-transaction tool in Amadeus. Use ER after creating or updating a PNR to save all changes and redisplay the record so you can verify the result. It combines saving and reviewing in a single entry, which makes it the most widely used command in PNR management. Always review the PNR on screen before entering ER โ€” if something is wrong, correct it or use IR or IG to discard the changes instead. Once ER has been entered, the changes are permanent and must be corrected with a new entry. Paired with ET for silent saves, ERK and ETK for advice code updates, EF for split PNRs, ERX and ETX for AXR-linked records, and RH for reviewing the history, the ER command completes your PNR management toolkit and keeps every booking accurate from the first entry to the final save.

Focus Keywords

  • ER command
  • Amadeus ER
  • end transaction Amadeus
  • save PNR Amadeus
  • redisplay PNR
  • ET command
  • ERK command
  • IR command
  • Amadeus PNR management
  • end and redisplay