

        📚 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 IG Command: Ignore Current Transaction

A complete guide to the IG command in Amadeus — how to ignore the current transaction, discard all unsaved changes, and return the PNR to its previously saved state.

Not every session ends the way it was planned. Sometimes an entry is made in error, a segment is added to the wrong PNR, or an agent realises halfway through a change that the customer has not yet confirmed it. When that happens, the safest response is to abandon the transaction entirely and return the PNR to its previous state. The IG command is the Amadeus entry that performs this task. It cancels the current transaction without saving any of the changes made since the last end transaction. This guide explains what IG does, its syntax, and when it should be used.

What Does the IG Command Do?

IG is the Amadeus GDS command used to ignore the current transaction and discard all changes made since the last end transaction.

Category: PNR Management.

It cancels the current transaction without saving the changes and returns the PNR to its previous state.

The effect is the same as IR in terms of what is discarded — but IG does not redisplay the PNR after rolling back. It simply exits the transaction. Use IG when you already know what the PNR looked like before and simply want to move on.

Syntax

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

IG

This ignores the current transaction, discards every change made since the last saved transaction, and returns the PNR to its previously saved state — without redisplaying it on screen.

When to Use IG

Use IG when you want to discard the changes made during the current transaction and return to the previously saved PNR. Typical scenarios include:

A segment, SSR, or remark was added in error and should not be saved.
A pricing entry was made that the customer has not yet confirmed.
Multiple mistakes were made during the current session and starting over is faster than correcting each element.
An agent has finished working with the PNR and no further action is needed.
A test entry was made to check how the system would respond and should not be stored.
The PNR was retrieved accidentally and no work is required on it.
The customer cancelled the request before the changes were saved.

How IG Fits Into Your PNR Management Workflow

A typical session using IG might look like this:

Retrieve the PNR with RT and begin making changes.
Realise that the changes should not be saved — wrong entry, wrong PNR, or unconfirmed request.
Enter IG to discard all changes made in the current transaction.
The system exits the transaction and returns to the command prompt.
If you need to see the PNR again, retrieve it with RT.
If you want to see the PNR immediately without a separate retrieval, use IR instead.

How IG Relates to Other PNR Management Commands

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

The distinction between IG and IR is one of the most commonly confused points in Amadeus. Both discard unsaved changes, but only IR brings the PNR back on screen. If you want to see the PNR after rolling back, use IR. If you simply want to exit and move on, use IG.

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

To remove a saved element, use XE on the specific line. IG is a safety net for the current session, not a global undo.

Frequently Asked Questions

What does the IG command do in Amadeus?

IG ignores the current transaction, discards all unsaved changes, and returns the PNR to its previously saved state without redisplaying it.

What is the difference between IG and IR?

Both discard unsaved changes. IR also redisplays the PNR, while IG exits without bringing the record back on screen.

Can IG undo changes that were already saved?

No. IG only affects the current, unsaved transaction. Once a transaction has been saved, changes must be removed individually, for example with XE.

After using IG, how do I retrieve the PNR again?

Use RT with the record locator or any other retrieval criteria.

When should I use IG instead of IR?

Use IG when you are finished with the session and do not need to see the PNR after rolling back. Use IR when you want to see the PNR immediately after discarding the changes.

Conclusion

The IG command is the transaction rollback tool in Amadeus. Use IG to discard all changes made in the current, unsaved transaction and return the PNR to its previous state — without redisplaying it. It is the fastest way to abandon a session that has gone wrong, whether a wrong entry was made, a PNR was retrieved accidentally, or the customer cancelled the request before the changes were saved. Remember that IG only affects the current unsaved transaction: anything already saved must be corrected individually, typically with XE. Paired with IR for rollback with redisplay, RT for retrieval, and RH for reviewing the PNR history, the IG command completes your PNR management toolkit and gives you a clean, reliable way to recover from errors in every session.