A complete guide to the ESX command in Amadeus โ how to cancel security agreements associated with an individual PNR and remove the related access permissions.
PNR security is one of the most important safeguards in Amadeus. When a booking contains sensitive information โ corporate data, VIP traveller details, or confidential fares โ the office can create security agreements that restrict who is allowed to view or modify the PNR. But security agreements do not last forever. When the reason for the restriction no longer applies, when the booking is transferred, or when the PNR is being closed, the agreements must be removed. The ESX command is the Amadeus entry that performs this task. It cancels the security agreements that have been created for an individual PNR, removing the associated access permissions. This guide explains what ESX does, its syntax, and when it should be used.
What Does the ESX Command Do?
ESX is the Amadeus GDS command used to cancel security agreements associated with an individual PNR.
Category: PNR Security.
It cancels the security agreements that have been created for the PNR, removing the associated access permissions.
Once the agreements are cancelled, the PNR returns to the standard office-level access rules. Agents whose access was restricted by the agreement can view and modify the booking again, according to their normal profile permissions.
Syntax
Enter the command on its own while the PNR is retrieved:
ESXThis cancels the security agreements associated with the PNR and removes the access permissions that were set by those agreements.
When to Use ESX
Use ESX when you need to cancel the existing security agreements for an individual PNR. Typical scenarios include:
- A PNR that was protected during handling but no longer requires restricted access.
- Transferring a booking between offices and removing the original security restrictions.
- Closing a booking at the end of a project or contract that required security agreements.
- Correcting a PNR that was accidentally placed under a security agreement.
- Preparing a booking for a task that requires unrestricted agent access.
- Removing outdated restrictions after a change in office policy or client requirements.
How ESX Fits Into Your PNR Management Workflow
A typical session using ESX might look like this:
- Retrieve the PNR with RT and confirm the security agreements currently in place.
- Verify with your supervisor or the responsible office that the restrictions can be removed.
- Enter
ESXto cancel the security agreements on the PNR. - End the transaction to save the change.
- Confirm that the PNR is now accessible according to standard office rules.
- Review the change in the PNR history with RH if required.
How ESX Relates to Other Security Commands
- ES โ displays and manages PNR security agreements.
- ESD โ displays security details for a PNR.
- ESX โ cancels the security agreements associated with an individual PNR.
- RP โ changes the responsible office and related office assignments.
- RH โ displays the PNR history, including security changes.
- RT โ retrieves the PNR before managing its security.
The distinction matters: ES and ESD are used to display and set security agreements; ESX removes them from the PNR.
Important: Cancelling security agreements opens the PNR to standard office access rules. Before using ESX, confirm that the removal is authorised โ particularly for corporate, VIP, or confidential bookings where the restriction may still be required by policy or by the client.
Once cancelled, security agreements cannot be restored in a single step. Recreating them requires the appropriate security commands and the correct permissions from your office profile.
Frequently Asked Questions
What does ESX do in Amadeus?
ESX cancels the security agreements associated with an individual PNR, removing the related access permissions.
Why would I need to cancel a security agreement?
When the reason for the restriction no longer applies โ for example after a booking is transferred, closed, or when the security was created in error.
Does ESX affect the itinerary or passengers?
No. ESX only removes the security agreements and access restrictions. The itinerary, passengers, and ticket data remain unchanged.
How do I check the current security agreements on a PNR?
Use the ES or ESD entries to display and review the security agreements before cancelling them with ESX.
Can I restore a security agreement after using ESX?
Not in a single step. Recreating a security agreement requires the appropriate security commands and permissions. Handle ESX carefully and only after confirming it is authorised.
Conclusion
The ESX command is the Amadeus tool for cancelling security agreements on an individual PNR. Use ESX to remove the access restrictions that were set through security agreements, returning the booking to standard office-level permissions. It is the correct entry when a PNR no longer requires restricted access, when a booking is being transferred, or when a security agreement was created in error. Because ESX opens the booking to normal access, always confirm the removal is authorised before running the command โ especially for corporate, VIP, or confidential bookings. Review the change in the PNR history with RH if you need to verify it. Paired with the display and management entries ES and ESD, and with RP for responsible office changes, ESX completes your PNR security toolkit and keeps every booking protected exactly as long as it needs to be.
Focus Keywords
- ESX command
- Amadeus ESX
- cancel security agreement Amadeus
- PNR security
- PNR access permissions
- ES command
- ESD command
- Amadeus security agreements
- PNR management
- remove PNR restrictions
