

        📚 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

CHECK SSR/NUMBER IN PARTY

A practical guide for travel agents on fixing the CHECK SSR/NUMBER IN PARTY error in Amadeus — covering SSR service count mismatches and MCO conflicts when canceling flights.

The CHECK SSR/NUMBER IN PARTY error is a common PNR and ticketing error in Amadeus that appears in two very different situations. In the first, the number of services requested in an SR entry does not match the number of passengers in the PNR. In the second — mainly in the ARC market — the error is triggered by an MCO conflict when canceling flights in a multi-passenger PNR. Because the same message covers two separate scenarios, agents often apply the wrong fix. This article breaks down both cases, explains why each one happens, and gives you the correct commands to resolve them quickly.

Scenario 1: SSR Service Count Mismatch

This happens when the number of services in your SR entry does not equal the number of passengers in the PNR.

Example:

SRCTCMSMHK3-123456789

If there are only 2 passengers in the PNR but you request 3 services, the system blocks the entry and returns the error.

Solution for SSR Count Mismatch

Check the number of passengers in the PNR.
Match the SSR service count to the number of passengers.
For multi-passenger PNRs, if the service applies to a specific passenger, add a passenger association:

SRCTCMSMHK1-123456789/P1

This entry applies the service to Passenger 1 only, which resolves the mismatch when the service is not meant for the entire party.

Scenario 2: MCO Conflict When Canceling Flights (ARC Market)

In a multi-passenger PNR where different MCOs are linked to the same passenger, canceling flights triggers the CHECK SSR/NUMBER IN PARTY error. The system detects a conflict between the MCO elements and the passengers they are attached to.

Solution for MCO Conflict

If you need to cancel flights BUT keep the MCO elements:

Use the XE command to cancel the flights only. The MCOs will remain intact in the PNR.

If you need to cancel flights AND cancel the MCOs:

Use the XI command to cancel the full itinerary, including the MCO elements.

Quick Fix Checklist

Identify which scenario you are facing — SSR count mismatch or MCO conflict.
Count the passengers in the PNR and compare them with the SSR service count.
Match the SSR count to the number of passengers, or add a passenger association like /P1.
For MCO conflicts, decide whether you need to keep the MCOs or not.
Use XE to cancel flights only, keeping the MCOs.
Use XI to cancel flights and MCOs together.
Re-check the PNR to confirm the error is resolved.

Frequently Asked Questions

What causes the CHECK SSR/NUMBER IN PARTY error?

It is caused either by an SSR service count that does not match the number of passengers, or by an MCO conflict when canceling flights in a multi-passenger PNR.

How do I fix the SSR count mismatch?

Match the SSR service count to the number of passengers, and use a passenger association such as /P1 when the service applies to one passenger only.

What is the difference between XE and XI?

XE cancels flights only and keeps the MCOs intact, while XI cancels the full itinerary including the MCO elements.

Conclusion

The CHECK SSR/NUMBER IN PARTY error looks the same in both scenarios, but the fix depends entirely on the cause. If the problem is an SSR service count that does not match the passengers, correct the count or add a passenger association like /P1. If the problem is an MCO conflict in the ARC market, use XE to cancel only the flights while keeping the MCOs, or XI to cancel everything together. Identifying the correct scenario first is the fastest way to clear the error and keep your workflow moving.

🏷 Tags: amadeus Amadeus errors