

        📚 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

ASSOCIATION NOT ALLOWED IN ELEMENT

A practical guide for travel agents on fixing the ASSOCIATION NOT ALLOWED IN ELEMENT error when entering APIS address information in Amadeus.

The ASSOCIATION NOT ALLOWED IN ELEMENT error is a common Amadeus APIS error that appears when an agent tries to add Address Information (APIS — Advance Passenger Information) into a PNR. The entry looks correct at first glance, the format seems right, and yet the system rejects it. The cause is almost always a single extra element in the command: a segment association that should not be there. This article explains why the error happens, shows the wrong command that triggers it, and gives you the exact corrected format so the APIS information is accepted on the first attempt.

What Error Appears When Adding APIS Information?

When you try to enter Address Information (APIS — Advance Passenger Information) into the PNR, the system returns this error:

ASSOCIATION NOT ALLOWED IN ELEMENT

What Causes This Error?

The error occurs because you have associated the APIS line with a specific segment number in your SRDOCA command, but the system does not allow this type of association for address information.

Example of the wrong command:

SRDOCA MH HK1-D-USA-123 MAIN STREET /P1/S2

If you added a segment association like /S2 or similar, it causes the error. The system expects the APIS document to be applied to the passenger as a whole, not tied to a specific flight segment.

How Do I Fix This Error?

Simply remove the segment association from your command.

Do not specify any segment number. Just enter the APIS details for the passenger directly.

Example of the correct command:

SRDOCA MH HK1-D-USA-123 MAIN STREET /P1

Make sure there is no /S2 or any other segment indicator after the address. The passenger association /P1 is allowed and required — but the segment association is not.

Quick Fix Checklist

Confirm the error appeared on an SRDOCA entry.
Look for any segment indicator in the command, such as /S2 or similar.
Remove the segment association completely.
Keep only the passenger association, such as /P1.
Re-enter the APIS line in the correct format.
Verify the APIS information was added successfully to the PNR.

Frequently Asked Questions

Can I associate an APIS line with a specific segment?

No. Amadeus does not allow a segment association in an APIS entry. The document is applied to the passenger as a whole.

Can I keep the passenger association /P1?

Yes. The passenger association is allowed and needed when the APIS applies to a specific traveller. Only the segment association must be removed.

What is the correct SRDOCA format?

Enter the APIS details with the passenger number and no segment indicator, for example SRDOCA MH HK1-D-USA-123 MAIN STREET /P1.

Conclusion

The ASSOCIATION NOT ALLOWED IN ELEMENT error is not a formatting problem — it is a rule about what can and cannot be linked to an APIS document. Amadeus allows APIS information to be tied to a passenger, but never to a specific segment. If your SRDOCA entry contains a segment indicator such as /S2, remove it, keep the passenger association /P1, and re-enter the command. The APIS information will be accepted immediately. Remembering this rule saves time and prevents repeated rejections when adding advance passenger information to international bookings.

🏷 Tags: amadeus Amadeus errors