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 PNR.
The system cannot price this automatically because the surface distance breaks the fare mileage rules.
Q3: How do I check and confirm the mileage?
A: Follow these 2 steps to verify the numbers:
- Check the Surface segment mileage using the
FQMcommand.- Example: If your surface segment is SIN–MNL, type:
>FQM SINMNL - Note the TPM (Ticketed Point Mileage) value.
- Example: If your surface segment is SIN–MNL, type:
- Check all flight segment mileages in your PNR.
- Display the itinerary and look at the TPM column for each flight.
- Find out which flight has the highest TPM.
Example from the article:
| Segment | Type | TPM |
|---|---|---|
| SIN–MNL | Surface (ARNK) | 1476 |
| BKK–SIN | Flight | 889 |
| MNL–BKK | Flight | 1363 (longest flight) |
Here, the Surface segment (1476) is greater than the longest flight (1363).
→ This triggers the *ATTN - ISSUE SEPARATE TICKETS error.
Q4: How do I fix this error?
A: There is no automatic system fix for this itinerary. The Amadeus system cannot price it.
You must:
- Contact the airline directly to confirm the correct fare and routing rules for this special case.
- Manually create the ticket mask (TST) using the fare provided by the airline.
- Issue the ticket manually outside the automatic pricing system.
Also Read: