

        📚 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 ES Command: Create PNR Security Agreement

A complete guide to the ES command in Amadeus — how to create security agreements for an individual PNR and control which offices or IATA numbers can access it.

Every PNR contains sensitive information. Passenger names, passport details, contact numbers, ticket records, and frequently negotiated fares all sit inside a single booking, and not every agent or office should be able to see them. Amadeus handles this through security agreements — rules that define exactly who can view, modify, or manage a specific PNR. The ES command is the entry that creates these agreements. It allows you to grant or restrict access to an individual PNR for another office, multiple offices, or a specific IATA number. This guide explains what ES does, the syntax for each variation, and when it should be used.

What Does the ES Command Do?

ES is the Amadeus GDS command used to create security agreements for an individual PNR.

Category: PNR Security.

It allows you to control who can access or modify a specific PNR by creating a security agreement for another office, multiple offices, or a specific IATA number.

Once a security agreement is in place, only the offices or IATA numbers listed in the agreement — plus the responsible office — can retrieve or update the booking. This is essential for corporate bookings, VIP travel, joint office handling, and any situation where the record must remain private.

Single Security Agreement

Create a security agreement with a specific office:

ESPARWL21**-B

This creates a security agreement with the office identified in the entry. Use it when the PNR is being handled together with a partner office or a branch, and that office needs access to the booking.

Multiple Security Agreements

Create security agreements for multiple offices in one entry:

ESPARWL21**-B,***WL2***-R

This creates security agreements for several offices at the same time, each separated by a comma. It is useful when a booking is shared between multiple branches or departments and every one of them needs access.

Security Agreement for an IATA Number

Create a security agreement for a specific IATA number:

ES/I20239951-B

This creates a security agreement tied to the specified IATA number rather than to an individual office. Use it when access should be granted at agency level rather than per office location — for example in corporate contracts or joint ventures.

When to Use ES

Use ES when you need to grant or restrict access to an individual PNR for another office or IATA number. Typical scenarios include:

Restricting a corporate or VIP booking to authorised offices only.
Sharing a PNR with a partner office or branch for joint handling.
Allowing a specific IATA number to access a booking made under a corporate agreement.
Protecting a booking that contains confidential fares or negotiated rates.
Giving another office access so they can issue the ticket or handle a refund.
Complying with client or internal policy that requires limited access to certain bookings.
Preventing unauthorised agents from viewing or modifying sensitive reservations.

How ES Fits Into Your PNR Security Workflow

A typical PNR security session using ES might look like this:

Retrieve the PNR with RT.
Check the current security structure with ESD before making changes.
Confirm with your supervisor which offices or IATA numbers should have access.
Enter the ES entry with the appropriate office or IATA number.
End the transaction to save the security agreement.
Verify the agreement by displaying it again with ESD.
To remove the agreement later, use ESX.

How ES Relates to Other Security Commands

ES → creates security agreements for an individual PNR.
ESD → displays the security agreements currently associated with a PNR.
ESX → cancels the security agreements on an individual PNR.
RP → changes the responsible office and related office assignments.
RT → retrieves the PNR before managing its security.
RH → displays the PNR history, including security-related changes.

The distinction matters: ES creates, ESD displays, and ESX cancels. Together they form the complete PNR security toolkit in Amadeus.

Important: Creating a security agreement restricts who can access the PNR. Once the agreement is saved, only the offices or IATA numbers listed — plus the responsible office — can retrieve or update the booking. Always confirm the correct entries before saving, and check with your supervisor if you are unsure.

Security agreements are recorded in the PNR history. Use RH to see when the agreement was created and by whom.

Frequently Asked Questions

What does ES do in Amadeus?

ES creates security agreements for an individual PNR, controlling which offices or IATA numbers can access or modify the booking.

How do I check the current security agreements?

Use ESD to display the security agreements on the PNR before making changes.

How do I create an agreement for multiple offices?

Separate the office entries with commas, for example ESPARWL21**-B,***WL2***-R.

How do I create an agreement for an IATA number?

Use the format ES/I20239951-B, replacing the IATA number with your own.

How do I remove a security agreement?

Use ESX to cancel the security agreements on the PNR. Confirm the change is authorised before doing so.

Conclusion

The ES command is the security agreement creation tool in Amadeus. Use ESPARWL21**-B to grant access to a single office, ESPARWL21**-B,***WL2***-R to share a booking with multiple offices, and ES/I20239951-B to grant access at agency level using an IATA number. It is essential for protecting corporate bookings, VIP travel, negotiated fares, and any reservation that requires restricted access. Always check the existing security structure with ESD before creating an agreement, confirm the correct office or IATA number, and remember that you can remove the agreement later with ESX. Paired with RP for responsible office changes and RH for PNR history, the ES command completes your PNR security toolkit and keeps every booking protected according to your office’s policy.