

        📚 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 EX Command: Explode SSRs Before End

A complete guide to the EX command in Amadeus — how to explode SSR elements in a PNR before ending the transaction so the requested services are processed correctly.

Special Service Requests are the elements that tell the airline what a passenger needs on a flight — a special meal, wheelchair assistance, an extra baggage allowance, a pet in the cabin, or any other service that must be arranged in advance. These SSRs are entered individually in the PNR, but before the transaction is closed, they sometimes need to be exploded so the system can process each request correctly. The EX command is the Amadeus entry that performs this step. This guide explains what EX does, its syntax, and when it should be used.

What Does the EX Command Do?

EX is the Amadeus GDS command used to explode SSRs before ending the transaction.

Category: Special Service Requests (SSR).

It expands the SSR elements in the PNR before the transaction is ended, allowing the requested services to be processed correctly.

When several SSRs are entered together — particularly when they have been added as a group or when they apply to multiple passengers and segments — the system may hold them as a compact entry until the transaction is closed. Exploding them with EX separates each request into its own element, so every service can be matched to the correct passenger and flight.

Syntax

Enter the command before ending the transaction:

EX

This explodes the SSR elements in the PNR so each request is processed correctly. Once the SSRs have been exploded, end the transaction to save the change.

When to Use EX

Use EX before ending the transaction when you need to explode the SSRs entered in the PNR. Typical scenarios include:

Adding several SSRs at once and needing each request processed separately.
Entering SSRs for multiple passengers where each traveller must have their own service element.
Recording a request that applies to more than one segment and needs to be split.
Ensuring special meal, wheelchair, baggage, or medical requests reach the airline individually.
Adding group SSRs where the requests must be confirmed per passenger.
Correcting an SSR element that was entered as a compact entry and needs to be exploded for validation.
Preparing the PNR for the airline’s SSR confirmation before ticketing.

How EX Fits Into Your PNR Management Workflow

A typical session using EX might look like this:

Retrieve the PNR with RT and review the SSR elements that have been added.
Confirm that all required SSRs are present — meals, assistance, baggage, or other services.
Enter EX to explode the SSRs into individual elements.
Verify the display shows each SSR as a separate entry, correctly linked to the right passenger and segment.
End the transaction to save the change.
Review the PNR history with RH if you need to confirm the order of events.

How EX Relates to Other SSR and PNR Commands

SR → creates the SSR elements in the PNR.
EX → explodes the SSR elements before ending the transaction.
XE → deletes an SSR or any other PNR element.
RT → retrieves the PNR so you can review SSRs.
RH → displays the PNR history, including SSR entries and changes.
ST → requests seats, another type of passenger service.
STG → requests seats for group PNRs.

The distinction matters: SR creates the SSR elements, EX explodes them into individual entries, and XE removes them when they are no longer needed.

Important: EX must be entered before ending the transaction. If the PNR is closed first, the SSRs remain in their compact form and may not be processed correctly by the airline.

Always review the SSR display after running EX to confirm that every request has been exploded correctly and is linked to the right passenger and segment. If any SSR is missing or incorrect, correct it before ending the transaction.

Frequently Asked Questions

What does the EX command do in Amadeus?

EX explodes the SSR elements in the PNR before the transaction is ended, allowing each request to be processed correctly.

When should I use EX?

Use EX before ending the transaction, whenever several SSRs have been entered and each request must be processed separately by the airline.

What happens if I end the transaction without using EX?

The SSR elements may remain in a compact form and the airline may not process them correctly. Enter EX before ending to avoid the issue.

How do I verify the SSRs were exploded correctly?

Redisplay the PNR after entering EX. Each SSR should appear as a separate element linked to the correct passenger and segment.

Can I delete an SSR after using EX?

Yes. Use XE with the line number of the SSR element you want to remove.

Conclusion

The EX command is the SSR explosion tool in Amadeus. Use EX before ending the transaction to explode the SSR elements in the PNR, so each special service request is processed correctly by the airline. It matters most when multiple SSRs have been entered together — meals, wheelchair assistance, baggage, medical requests, or group services — and each one must be confirmed individually. Always review the SSR display after running EX and correct any incorrect or missing elements before saving. Paired with SR to create the SSRs, XE to delete them, RT to retrieve the PNR, and RH to review the history, the EX command completes your SSR toolkit and ensures every special service request reaches the airline correctly.