I just pulled up the booking I made (planned, booked and issued) without problem a few months ago, ICN-HKG-JFK-MIA-SEA-ORD-LAX-IAH-ORD-AMM-MAD-LHR-DXB-LHR-SIN-HND-GMP. It came back with an error

error message using online booking tool
 

I attempted to ticket an ex-EZE LONE6 using the online tool today and got an errror message on the last step. The first segment is on AA to DFW so the booking carrier was shown to be AA.

I don't want to go through the AA RTW desk as the price (as I understand it) would be $5K more (US vs. Argentina prices for my particular reservation).

As an alternative should I call one of the list ticket offices in BA? Can I just give them the list of flights and have them ticket it?

There have been many reports of issues with the online tool - they have been reported in the xONEx online tool bugs thread

But IIRC your's is the first report of problems with an ex-EZE itinerary (most of the problems reported have been to do with ex-KRT itineraries and/or with the first flight being a codeshare)

I have just tried a very simple itinerary (EZE-DFW-NRT-LHR-EZE)
and it priced up OK and when I completed the (spurious) payment details - it failed with the message "We are having difficulty accepting the credit card details provided. Please validate and try again. This may be due to an invalid credit card type, in which case please provide another one (4613 - 201)"

Can you post your itinerary for us to check?

My report, posted in the bugs thread, was for ex-ICN, CX flight, CX ticket. Booked and issued without problem 3 months ago, bug only showing up now with the tools new URL.

I'm merging this with the existing "online tool bugs" sticky thread. Please continue the discussion there.

Gardyloo
Oneworld moderator

Back in post #160 I said I was trying out various ex-KRT itineraries to try to convince Mrs pandaperth that we should buy one. Well she's agreed:eek:, and so I am trying even harder to get the tool to price things up. (though I fully expect in the end I will have to use a Canadian TA to ticket)

Thought I'd share what I've been finding out. Maybe others can contribute what they've learnt too.

OK my basic itinerary is: KRT-xAMM-YUL,YYZ-xHKG-PER-HKG-XIY,IKT-DME-AMM-KRT. The first part (KRT...PER) is to get us home from our African holiday next March/April. Then the second part is to get us to Xian (terracotta warriors) and Russia for Mrs pandaperth's birthday trip next August. Ending up back in KRT, and hopefully starting another RTW from there.

S7 has not loaded its schedules beyond March next year, so I have removed the IKT-DME segment and all being well will add that later (paying the change fee)
The good news is that the above itinerary (minus the IKT-DME segment) prices up in the online tool.

Now it gets tricky
There are some segments left over and when I add them, sometimes it prices up, sometimes it doesn't
It seems to me that if you return to the same airport after some intra-continental segments then the tool fails (whereas inter-continental returns do not fail - in the itinerary I have HKG-PER-HKG and that works)

So adding PER-BME-PER or PER-BNE-ADL-PER to the above causes failure
So does HKG-PNH-HKG and HKG-NRT-ICN-HKG
But adding PER-BNE-MEL-SYD-CNS works
As does adding SIN-NRT-ICN-HKG

Note: all the testing I have done has been on ex-KRT itineraries, so it's AA that does the pricing (the url is http://americanairlines.eu.amadeus.com)
YYMV with other ticketing airlines
Note also that I of course have not tried to actually pay for any of these - and it is known that failure can occur at that point too

Update: trying other starting points, and hence other ticketing airlines

BA ticketing (basic itinerary NBO-LHR-LAX-SYD-JNB)
Same symptoms!
Adding LAX-DFW-LAX or SYD-MEL-SYD causes failure
But having LAX-JFK-DFW worked as does having BNE-ADL-SYD
(ticketing url in this case is http://wftc2.e-travel.com)

Edited to add:
CX ticketing (basic itinerary YYZ-xHKG-PER-HKG-XIY,DME-AMM-KRT-AMM-YUL)
Almost the same symptoms!
Adding segments in SWP had the same symptoms (adding PER-BME-PER failed, but adding PER-SYD-BNE worked)
But in Asia adding HKG-PNH-HKG worked!
(and the ticketing url is the same as that for BA:confused:)

Eureka! When I removed my multiple intra-continental returns to JFK, suddenly my many wip ex-KRT itineraries began pricing again (after failing every day for a week or longer).

[Like you, I had no problems when I made multiple trips through HKG.]

Many thanks for tirelessly investigating/diagnosing this new bug. ^^ It's a shame that it's there ---- but better to know how to work with it than not be able to price anything at all.....

If one resigns oneself to paying the $125 change fee for rerouting, I guess the only remaining hesitation is in regard to the date of the first flight (KRT - AMM). Other than that, everythng else can be changed later. ;)

Now that everything is pricing again (with removals of intra-continental repeat cities other than HKG), I tried to buy a pair of tickets ---- and received an error at the very end. AA put a Euro 1 charge through to AMEX, and there's plenty of credit headroom there. I called AMEX and they swear that they did not reject any additional charges...that they received nothing from AA over and above the 1 euro. I love the AA RTW desk once everything is ticketed and I need their help to make changes, but absolutely hate dealing with intermediaries before ticketing is finalized..... I wish the online tool worked. :mad:

Re: Error message (7820) not found for Language Code 'GB'

As stated in previous posting, the error message on Oneworld RTW planner seems to pop up only when booking internal flights within Asia (I think it is due to Cathay's new reservation system). When I specifically listed Hong Kong as a stopover (three times in the itinerary) for intra-regional travel in Asia on CX (i.e. HK-Bangkok-HK-Tokyo-HK-Los Angeles), I received the error. However, when I booked the routing as direct routes (i.e. HK-Bangkok-Tokyo-Los Angeles) but selecting the CX routes that all changeover in Hong Kong, there was no error and I received the RTW ticket price from the system. I will book my routes this way then call reservations to move the dates so I will have extended stays each time I land in Hong Kong without incurring the change in routing penalty.

Welcome to FT ABH

Just a word of caution
Changing a transit to a stopover will likely require a re-pricing of the ticket which can trigger its own set of issues
(re-pricing because many government charges are not imposed on transit passengers, but are imposed on stopover passengers)

Clarity on this subject would be appreciated.

I think that what you saying is that changing a connection into a stopover will attract both a $125 change fee and a recalculation of taxes and surcharges. I would agree with that. However, I do not think that changing a connection into a stopover could/should have the impact of causing a reprice of the base xONEx fare. If you believe the latter, I'd appreciate understanding why that is so (and where this action is supported in the fare rules). TIA!

No, no. You have it right jbalmuth. Didn't mean to over state the issue; my bad:(

Just a quick update on the issue with pricing up itineraries that include an intra-continental return to the same airport

I have reported the 'bug' to oneworld (via the link at the bottom of the faq page for the booking tool)

I received a response from one of the team overnight asking for more details. So they are looking into it at least. I will post again when I get more information back.

and the latest bug is...

the tool does not show any AA flights YUL-JFK
it does show the codeshare that LA has one of the daily AA-metal flights
but if you choose that, the tool displays an message saying you have to choose an AA flight!
(this is on an ex-KRT itinerary. YMMV on other points of origin)