

        📚 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

ETKT DISALLOWED – MULTIPLE TOUR CODES

A practical guide for travel agents on fixing the FT Tour Code issuance error in PNRs that contain multiple TSTs for adults and children.

One of the most confusing ticket issuance errors in Amadeus and other GDS systems happens when a PNR contains multiple TSTs — for example, a separate TST for adult passengers and another for child passengers — but the FT (Tour Code) line is entered without specifying which passenger it applies to. Even if every passenger shares the same Tour Code, some airlines still require the system to know exactly who the FT line belongs to. When the FT line is not associated with a specific passenger number, the system rejects the issuance and the tickets cannot be generated. This article explains why the error happens and how to fix it correctly in a few simple steps.

Why the FT Tour Code Error Happens

The core problem: the PNR contains multiple TSTs, but the FT line is not tied to a passenger.

When a PNR has more than one TST — typically one for adults and one for children — the ticketing system must match every FT Tour Code entry to the correct TST. If the FT line is entered without a passenger number, the system cannot determine which TST it belongs to.

Even when all passengers share the same Tour Code, some airlines still require the FT line to be linked to a specific passenger number. Without that association, the issuance is rejected.

How to Fix the FT Tour Code Error

Step 1: Delete the existing FT line

Remove the current FT line that has no passenger association. This clears the invalid entry from the PNR.

Step 2: Re-enter the FT line for each passenger group separately

Add the passenger number at the end of each FT entry using /P followed by the passenger number.

Correct FT Tour Code Examples

For adult passengers (P1):

FM5/P1
FT*TOUR/P1

For child passengers (P2):

FM5/P2
FT*TOUR/P2

By doing this, each passenger is clearly linked to the correct tour code, and the ticket will issue successfully. The system can now match every FT entry to the right TST, so no rejection occurs.

Quick Fix Checklist

Open the PNR and review the TSTs for each passenger type.
Locate the FT Tour Code line and check if it has a passenger number.
Delete the FT line that has no passenger association.
Re-enter the FT line for each passenger group using /P plus the passenger number.
Verify that every TST now has its own linked FT entry.
Re-issue the tickets and confirm successful issuance.

Frequently Asked Questions

Why does the system reject my FT Tour Code?

Because the FT line is not linked to a specific passenger number, and the PNR contains multiple TSTs. The system cannot match the Tour Code to the correct TST.

Do I need to split the FT line if all passengers share the same Tour Code?

Yes. Some airlines require the FT line to be linked to each passenger individually, even when the Tour Code is identical for everyone.

What does /P mean in the FT entry?

It associates the FT Tour Code with a specific passenger number in the PNR, such as /P1 for the first passenger.

Conclusion

The FT Tour Code error is easy to fix once you understand that every FT line must be associated with a passenger number when multiple TSTs exist in the PNR. Delete the unlinked FT entry, re-enter it for each passenger group using /P, and the tickets will issue without rejection. This simple habit saves time, avoids repeated failures, and keeps your ticketing workflow smooth.

🏷 Tags: amadeus Amadeus errors