<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Originally posted by Guy Betsy:
FYI - BA's computers, AMADEUS, can handle only something like 12 segments before it has to be handwritten. Only CX's system can handle more than the 24 segments but it requires creative ticketing in that they split the fare calculation and taxes into two seperate tickets. Not exactly kosher and if encountered with a reissue by another Oneworld airline, it will face problems.

[This message has been edited by Guy Betsy (edited 03-05-2003).]</font>

<font face="Verdana, Arial, Helvetica, sans-serif" size="2">"Guidelines for PNRs with More Than 16 Segments
If you need to Manually Price an itinerary that exceeds 16 segments, including ARNKs, the itinerary needs to be broken and two sets of tickets issued. The following guidelines should be used:

1. The customer or airline determines which segments should be issued on the first ticket.

2. Create a Manually Priced Multiple Ticketing Record using segment select (e.g., 4/R-S1-9#TR) to indicate the segments to be issued on the first ticket. When entering the fare calculation information, the fare calculation for the entire itinerary should be shown. The base, tax, and total fare should reflect the cost of the entire itinerary. My Note:--&gt; This is probably the problem! (But can they somehow "condense" the fare calculation or maybe omit a "space" here and there to get it to fit ticket?, or have only a portion of the fare calculation for segments that are NOT on the set of ticket?)

My note: What about using part of the "endorsement" box to squeeze in some tax info? My RTW ticket issued by CX had some creative things like "2XQ4" instead of "Q4.00 Q4.00" in their fare calculation to get it to fit.

3. The remaining segments should be Manually Priced using the same guidelines shown in step 2 above (e.g., 4/R-S10-16#TR), creating a second ticketing record.

4. Issue the first set of tickets using TR1.

5. Issue the second set of tickets using TR2. If the form of payment is credit card, the approval code from the first set of tickets must be used to prevent debiting the credit card a second time.

6. The second ticket should be voided from the DDL/DDP immediately since ARC downloads ticket images to credit card companies nightly. This also prevents the amount from being doubled on the ARC report.
"</font>