

        📚 GDS Academy

        
            
                
                    Amadeus GDS Commands & Lessons | GDS Hub
                    35
                

            
                
                    Galileo GDS Commands & Lessons | GDS Hub
                    27
                

            
                
                    Sabre GDS Commands & Lessons | GDS Hub
                    20
                

                    

        
            🛠 Tools
            Airport Taxes Database
            Airports Database
            Farebase Generator
            Tax Checker
            Airline Special Services

Amadeus IR Command: Ignore Transaction & Redisplay

A complete guide to the IR command in Amadeus — how to ignore the current transaction, discard unsaved changes, and redisplay the PNR in its previous saved state.

Every agent makes mistakes. A segment is entered incorrectly, a name is misspelled, an SSR is added for the wrong passenger, or a remark is added that should not be there. What matters is not avoiding every error, but being able to undo changes cleanly and get back to a safe state. The IR command is the Amadeus entry that does this. It discards all changes made during the current transaction and redisplays the PNR in its previous saved state. This guide explains what IR does, its syntax, and when it should be used.

What Does the IR Command Do?

IR is the Amadeus GDS command used to ignore the current transaction and redisplay the PNR.

Category: PNR Management.

It discards all changes made during the current transaction and then redisplays the PNR in its previous saved state.

The key word is discards. Anything entered since the last saved transaction is rolled back, and the PNR returns to the state it was in before the current session began. The redisplay shows you exactly what the record looks like now, so you can confirm the changes are gone and start again.

Syntax

Enter the command on its own while the PNR is open:

IR

This ignores the current transaction, discards any unsaved changes, and redisplays the PNR in its previous saved state. Use it whenever you want to undo everything you have done in the current session and start over.

When to Use IR

Use IR when you want to discard your current changes and immediately redisplay the PNR. Typical scenarios include:

A segment was added with the wrong date, class, or routing.
A passenger name was entered incorrectly and needs to be re-entered from scratch.
An SSR or remark was added for the wrong passenger or segment.
A pricing entry was made that should not be stored.
Multiple mistakes were made during the current session and starting over is faster than correcting each one.
A change was made before realising the customer had not yet confirmed it.
Testing a series of entries where nothing should be saved.

How IR Fits Into Your PNR Management Workflow

A typical session using IR might look like this:

Retrieve the PNR with RT and begin making the required changes.
Notice that something has gone wrong — a wrong entry, an incorrect SSR, or a pricing that should not be stored.
Enter IR to discard all changes made in the current transaction and redisplay the PNR.
Verify the PNR is back in its previous state.
Start again with the correct entries.
Once everything is correct, end the transaction normally with ER or the appropriate save entry.

How IR Relates to Other PNR Management Commands

IR → ignores the current transaction and redisplays the PNR.
IG → ignores the current transaction without redisplaying the PNR.
XE → deletes an individual element from a saved PNR.
RH → displays the PNR history, including transactions that were saved.
RT → retrieves the PNR again if needed.

The distinction matters: IR discards changes and redisplays the PNR, while IG discards changes without redisplaying the record. Use IR when you want to see the PNR after rolling back, and IG when you are done with the session and simply want to move on.

Important: IR only discards changes made in the current transaction. If the transaction was already saved with an end-of-transaction entry, those changes are permanent and IR cannot undo them.

To remove a saved element, use XE on the specific line, or reprocess the entry as required. IR is the safety net for the current session — not a global undo.

Frequently Asked Questions

What does the IR command do in Amadeus?

IR ignores the current transaction, discards all unsaved changes, and redisplays the PNR in its previous saved state.

What is the difference between IR and IG?

IG ignores the current transaction without redisplaying the PNR. IR also ignores the transaction but brings the PNR back on screen.

Can IR undo changes that were already saved?

No. IR only discards changes made in the current transaction. Once a transaction has been saved, changes must be removed individually, for example with XE.

Does IR affect the whole PNR or only the current entries?

Only the entries made in the current, unsaved transaction. Everything that was previously saved remains unchanged.

When should I use IR instead of correcting the entries individually?

Use IR when multiple mistakes have been made, or when starting over is faster than correcting each element. For a single wrong element, XE may be more efficient.

Conclusion

The IR command is the transaction rollback tool in Amadeus. Use IR to discard all changes made during the current transaction and redisplay the PNR in its previous saved state. It is the fastest way to undo multiple mistakes at once — whether a segment was entered with the wrong date, a name was misspelled, an SSR was added for the wrong passenger, or the entire session needs to be started over. Remember that IR only affects the current unsaved transaction: anything already saved must be corrected individually, typically with XE. Paired with IG for exiting without redisplaying, RT for retrieval, and RH for reviewing the PNR history, the IR command completes your PNR management toolkit and gives you a safe way to recover from errors in every session.