amadeus

  • CT RJT: ETKT RJT – NO INTERLINE BETWEEN CARRIERS

    CT RJT: ETKT RJT – NO INTERLINE BETWEEN CARRIERS

    This error occurs when there is no e-ticket agreement between the carriers involved in the itinerary. Possible reasons: Solution: Step 1: Check e-ticket agreements between carriers. Use the command:TGAD-[carrier code]/[carrier code]Example: TGAD-MS/SM Airlines can have the following agreement types: For more information, refer to: HE TGAD Step 2: Choose another validating carrier. If no e-ticket agreements exist between…

  • ETKT FUNCTION NOT SUPPORTED FOR THIS CARRIER

    ETKT FUNCTION NOT SUPPORTED FOR THIS CARRIER

    This error appears when the agent tries to perform an e-ticketing function, such as: Cause: Some airlines do not support all e-ticketing functions in all markets. The function you are trying to perform is not supported by the airline in your specific market. Solution: Also Read: ERROR: NO TAX COULD BE RETRIEVED, PLEASE ADD…

  • ERROR: NO TAX COULD BE RETRIEVED, PLEASE ADD THEM MANUALLY

    ERROR: NO TAX COULD BE RETRIEVED, PLEASE ADD THEM MANUALLY

    When you display the refund record using TRF, the Tax Refund amount shows 0 (zero). By checking further with TRFT, you will find that the system has not stored any tax details for this ticket in the refund record. As a result, the system cannot calculate the refund and prompts you to add taxes manually. Solution: 1.…

  • MESSAGE SIZE EXCEEDED

    MESSAGE SIZE EXCEEDED

    This error occurs for one of the following reasons: Solution: Step 1: Check and correct the passenger name format. For more details, refer to: HE NAME CHANGE Step 2: Issue tickets one passenger at a time. Instead of issuing all passengers together, enter: This reduces the message size and avoids the error. Also Read: CT…

  • ETKT DISALLOWED – MULTIPLE TOUR CODES

    ETKT DISALLOWED – MULTIPLE TOUR CODES

    The PNR contains multiple TSTs (e.g., separate TSTs for adults and children), but the FT (Tour Code) line is entered without specifying which passenger it applies to. Even if all passengers share the same Tour Code, some airlines require the system to know exactly who the FT line belongs to. When it is not associated with a specific passenger…

  • ETKT: MAXIMUM NUMBER OF FLIGHTS/PASSENGERS/TICKETS EXCEEDED

    ETKT: MAXIMUM NUMBER OF FLIGHTS/PASSENGERS/TICKETS EXCEEDED

    This error occurs for one of the following reasons: Solution: If the BSP balance is fine, contact the airline directly to request a new ticket stock. Display the TST and check the number of flights and ARNK (Surface) segments.The e-ticketing system allows a maximum of 16 flights and 2 Surface (ARNK) segments. If the number of segments exceeds 16: Issue tickets one…

  • COMMISSION NOT VALIDATED – RE-ENTER COMMISSION

    COMMISSION NOT VALIDATED – RE-ENTER COMMISSION

    This error appears when the agent tries to issue a ticket using the TTP command. Cause: This error occurs when: When the commission cannot be validated against the CCI settings, the system blocks the issuance. Solution: Step 1: Delete the existing commission (FM) line from the PNR. Step 2: Re-enter the commission (FM) line again. Step 3: Try to…

  • CHECK SSR/NUMBER IN PARTY

    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]

    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

    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…