

        📚 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

*ATTN – ISSUE SEPARATE TICKETS

A practical guide for travel agents on fixing the *ATTN — ISSUE SEPARATE TICKETS pricing error in Amadeus when a Surface / ARNK segment breaks the mileage rules.

The *ATTN — ISSUE SEPARATE TICKETS error is a common Amadeus pricing error that appears when an agent tries to price a ticket containing a Surface or ARNK segment. Unlike most pricing errors, this one cannot be fixed with an override or a different command — the itinerary simply breaks the fare mileage rules. The cause is a Surface segment whose mileage is greater than the longest actual flight segment in the same PNR. This article explains why the error happens, how to check and confirm the mileage using FQM, and what your realistic options are when the system refuses to price the itinerary automatically.

What Error Do I See When Pricing?

When you try to price the ticket using the Price command, the system returns this warning:

*ATTN - ISSUE SEPARATE TICKETS

What Causes This Error?

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 PNR.

The system cannot price this automatically because the surface distance breaks the fare mileage rules — the surface portion is effectively “longer” than the actual flight, which makes the fare calculation invalid.

How Do I Check and Confirm the Mileage?

Step 1: Check the Surface segment mileage using FQM

Example: if your surface segment is SIN–MNL, type:

FQM SINMNL

Note the TPM (Ticketed Point Mileage) value shown in the result.

Step 2: Check all flight segment mileages in your PNR

Display the itinerary and look at the TPM column for each flight. Identify which flight has the highest TPM.

Example breakdown:

SIN–MNL — Surface (ARNK) — TPM 1476
BKK–SIN — Flight — TPM 889
MNL–BKK — Flight — TPM 1363 (longest flight)

Here, the Surface segment (1476) is greater than the longest flight (1363). That is exactly what triggers the *ATTN — ISSUE SEPARATE TICKETS error.

How Do I Fix This Error?

There is no automatic system fix for this itinerary. The Amadeus system cannot price it. You must:

1. Contact the airline directly

Confirm the correct fare and routing rules for this special case. The airline may approve a specific fare basis or instruct you to issue separate tickets.

2. Manually create the ticket mask (TST)

Build the TST using the fare provided by the airline, entering the fare, taxes, and fare basis yourself.

3. Issue the ticket manually

Complete the issuance outside the automatic pricing system, using the manual TST you created.

Quick Fix Checklist

Confirm the warning reads *ATTN - ISSUE SEPARATE TICKETS.
Check the Surface segment mileage using FQM.
Note the TPM of the surface segment.
Display the itinerary and find the highest TPM among the actual flights.
Compare: is the surface TPM higher than the longest flight?
If yes, contact the airline for fare and routing rules.
Create the TST manually and issue the ticket outside automatic pricing.

Frequently Asked Questions

Why does the surface segment cause this error?

Because the surface mileage is greater than the longest actual flight segment, which breaks the fare mileage rules and prevents automatic pricing.

Which command checks the surface segment mileage?

Use FQM followed by the city pair, for example FQM SINMNL.

Is there an override to force automatic pricing?

No. There is no automatic system fix. You must contact the airline, create the TST manually, and issue the ticket outside the automatic pricing system.

Conclusion

The *ATTN — ISSUE SEPARATE TICKETS error is one of the few Amadeus pricing errors with no automatic solution. It appears when a Surface / ARNK segment has a higher TPM than the longest flight in the itinerary, breaking the fare mileage rules. The fastest way to confirm the cause is to run FQM on the surface city pair and compare the TPM with the highest flight TPM in the PNR. When the surface mileage wins, automatic pricing cannot proceed. Your path forward is to contact the airline for the correct fare and routing rules, build the TST manually, and issue the ticket outside the automated system. Recognising this error early saves hours of futile attempts to reprice.

🏷 Tags: amadeus Amadeus errors