Home Blog ASSOCIATION NOT ALLOWED IN ELEMENT

📚 GDS Academy

How to Display Ticket Conditions in AmadeusHow to Book an Infant with a Seat in Amadeus & GDSAmadeus Lesson 12: How to add seat Selection & EMD IssuanceAmadeus Lesson 11: Special Meals & Wheelchair Requests (SSR)Amadeus Lesson 10: How to Change Passenger Name in PNRAmadeus FXD: Essential Commands for Finding the Best AirfareHow to Retrieve a Past Date Booking in AmadeusAmadeus Lesson 9: How to issue ticketAmadeus Lesson 8: How to add FOP, Commission &(FV)Amadeus Lesson 7: How to add passport Information (SR DOCS)Amadeus Lesson 6: How to price a PNR(FXX, FXP, FXR & FXB)Amadeus Lesson 5: How to add a Frequent Flyer Card (FFN & SR)Amadeus lesson 4: how to add Contact Information (AP&SR)Amadeus lesson 3: Ticketing Arrangement & Save PNRAmadeus lesson 2: How to add Passenger Names (NM)Split PNR Commands in Amadeus, Galileo, and SabreHow to clone PNR in Amadeus , Galileo and saberhow to send Itineraries via Amadeus, Galileo, SabreHow to Add a Frequent Flyer in Amadeus, Galileo & SabreHow to add Passport Data in Amadeus Galileo SabreHow to add contact details in Amadeus, Galileo, SabreHow to Master Amadeus Encode & Decode CommandsMinimum Connecting Time (MCT) – Quick GuideHow to Transfer PNR in Galileo, Amadeus & SabreAmadeus Queues : How to Use Them EfficientlyHow to Change a Passenger Name in a PNRAmadeus lesson 1: How to search for a flightThe Ultimate Amadeus Commands GuideRetention Segments: How to Keep Your PNR ActiveHow to Use ARNK in Amadeus, Sabre & GalileoVoid in Amadeus System – Simple Guide for Travel AgentsHow to Process a Manual Refund in Amadeus (Step-by-Step Guide)How to Create a Group PNR in (Amadeus, Galileo & Sabre)How to Create a PNR in Amadeus

ASSOCIATION NOT ALLOWED IN ELEMENT



Q1: What error appears when I try to add APIS information?

A: When you try to enter Address Information (APIS – Advance Passenger Information) into the PNR, the system returns this error:
ASSOCIATION NOT ALLOWED IN ELEMENT


Q2: What causes this error?

A: This 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
(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.


Q3: How do I fix this error?

A: Simply remove the segment association from your command.

Correct command format:
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.)




Also Read:

A MESSAGE IS PENDING TO BE SENT

*ATTN – ISSUE SEPARATE TICKETS

*NO FARES/RBD/CARRIER/PASSENGER TYPE

Linkedin