Blog
-

CHECK SSR/NUMBER IN PARTY
This error occurs in two main scenarios: 1. SSR Service Count Mismatch:The number of services in your SR entry does not equal the number of passengers in the PNR. Example:SRCTCMSMHK3-123456789If there are only 2 passengers in the PNR but you request 3 services, the system blocks it. 2. MCO Conflict When Canceling Flights (ARC Market):In a…
-
![COMBINATION NOT ALLOWED [TTP]](https://www.gdshub.pro/wp-content/uploads/2026/06/amadeus_errors.jpg)
COMBINATION NOT ALLOWED [TTP]
This error appears when the agent tries to issue a ticket using the TTP command. Solution: Check your TTP entry options – ensure they are combinable. Either use the TST number: TTP/T3/RT Or use passenger/segment association: TTP/P2/S3-4/RTDo not combine both in a way that conflicts. Ensure your ticketing options match the TST – for example, verify that the Passenger Type…
-

CHECK PASSENGER ASSOCIATION
This error occurs when the PNR contains more than one passenger, and the agent enters a command that requires a specific passenger association without specifying the passenger number. Example scenario:When manually creating an EMD using a command like:IUSMNN1PENFSHJThe system does not know which passenger (P1, P2, etc.) this EMD belongs to, so it returns the CHECK PASSENGER…
-

CHECK ITINERARY
The error occurs because one or more flight segments in the PNR have a status other than HK (Confirmed).Possible statuses include: HL (Waitlisted), HN (Requested), UC (Unable to Confirm), or others. Solution: Also Read: CHECK DATE OF BIRTHCANCEL SEAT ITEM OR SPLIT PNR PRIOR TO NAME RE-ENTER*ATTN – ISSUE SEPARATE TICKETS Linkedin
-

CHECK DATE OF BIRTH
This error appears when the agent tries to enter a Date of Birth for a passenger, but the system rejects it. Reason: The Date of Birth was entered in an incorrect format. The Amadeus system requires a specific date structure, and any deviation will trigger this error. Solution: Enter the Date of Birth using the correct…
-

CANCEL SEAT ITEM OR SPLIT PNR PRIOR TO NAME RE-ENTER
This error appears when the agent tries to change a passenger’s name in a Group PNR. Reason: The system blocks the name change because seat assignments have already been made for the passengers in the Group PNR. The PNR must be free of seat requests before any name modification can be processed. Solution: Follow these steps:…
-

BI ETKT:INVALID FARE BASIS
This error appears when the agent tries to issue the ticket, but the system blocks it. Reason: The Fare Basis field inside the TST (Ticket Mask) contains a hyphen “–”.The Amadeus system does not allow any special characters (such as -, /, *, etc.) in the Fare Basis. Only letters, numbers, and spaces are permitted. Solution: Edit the Fare…
-

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…
-

A MESSAGE IS PENDING TO BE SENT
Q1: What error appears when I try to send an email? A: When you attempt to send an email via the Amadeus system to your customer, you may receive this error message:A MESSAGE IS PENDING TO BE SENT Q2: What causes this error? A: This error happens when there is a temporary internet connectivity issue at the exact…
-

*ATTN – ISSUE SEPARATE TICKETS
Q1: What error do I see when pricing? A: When you try to price the ticket using the Price command, the system returns this warning:*ATTN – ISSUE SEPARATE TICKETS Q2: What causes this error? A: The error happens because the mileage (distance) of a Surface / ARNK segment is greater than the mileage of the longest actual flight segment in the same…