I've had this problem with ex-KRT itineraries that I've been trying (trying to convince Mrs pandaperth we should start a RTW from there:rolleyes:). They used to price, but then as is already known fail at the purchase step; but now they won't even price.
To investigate the problem I tried ex-AMM itineraries, starting with either RJ or the AA codeshare AMM-JFK - and they both fail
But itineraries starting in JFK with AA, and in SYD with QF both price up OK
Puzzling...

jbalmuth - where do your work in progress itineraries start from, and with which airlines for their first segments?

My itineraries were also ex-KRT, but then like you I moved the starting point to AMM and had the same result. I then tried ex-NBO expecting to pull up BA's ticketing (rather than RJ/AA's ticketing ex-KRT and ex-AMM), but this also failed (i.e. no pricing). Puzzling, but also very disappointing.:(

Just done a bit of playing with the tool:
ex-LHR with first segment on BA - priced up OK
ex-NBO with first segment on BA - also priced up OK

So jbalmuth, just a thought - are you sure your ex-NBO itinerary was valid? (especially in regard to the allowed extra transit of Europe if you had that in your itinerary)

Yes, a valid itinerary with no review issues or "x"s. Tried it again today, and received no pricing. [First leg is NBO - LHR on BA.]

Have you, or anyone else, succeeded in getting any of your ex-KRT or ex-AMM itineraries to price etc. during the past 4 days? If not, are there any theories as to what's going on?

Well, given that my test itinerary (NBO-LHR-LAX-SYD-JNB) priced up OK, I'm stumped as to why your's isn't

No. I tried my ex-KRT itinerary again last night
- using google chrome I got an error message about the lowest price no longer available
- but with IE8 I got a weird security error message about one web page trying to alter another web page
The url of the page has changed recently - now it's rtw.oneworld...; IIRC it used to be something like innosked....
So maybe they're 'testing in production'?

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)

I noted a similar bug with IB flights from FCO - MAD or MXP - MAD when booking ex-KRT in First. When booking ex-KRT in Business the expected IB flights appear. Is your ex-KRT itinerary not showing the AA YUL - JFK flights in First or Business? Try the other to see if you can now book the AA flights. If so I would hope that OneWorld support would be able to identify (and hopefully address) the issue.....

I'm working on ex-KRT DONE4s
According to KVS, the AA YUL-JFK flights on the dates I'm looking at all have plenty of D (and L) availability
I will test a LONE4 and see if the flights appear in the tool

Edited to add
Tried it as a LONE4 itinerary - still had the same problem regarding AA flights not showing for YUL-JFK

Just an FYI...

Tried to book our ex-KRT DONE4 tickets using the tool
Got right through to pressing "Confirm Trip" after entering my c/c details
Next screen gave the message

ime that "fare for the flights you have selected is no longer available" message comes and goes pretty randomly.

I assert that because I've made 3 separate ex-KRT ticket "purchases" in the past week. Each has progressed from ""Ticketed" to "Purchased" to "On request" on aa.com (where after a few days I've subsequently clicked "cancel itinerary" and the itinerary eventually disappears). None of these "Ticketed" itineraries have resulted in any charges to my credit card(s).

[I haven't yet called AA's RTW desk to set-up alternative ticketing, as I'm currently still happy to play with/improve on the itinerary. I'm also attempting to diagnose what may be causing the automatic ticketing function to fail to stick. (At the moment my primary suspect remains RJ ex-AMM westbound flights connecting from the KRT - AMM flight, but the only alternative westbound flight is BA's 03:15 am departure, which besides wrecking another night's sleep also adds a very large slug of avoidable surcharges...).]

Hope that you succeed on your next attempt!

Error 7820 While booking a Round-The_world Itinerary
 

Hi Everyone,

I am having a hard time in booking a round the world itinerary with the Oneworld explorer website (http://rtw.oneworld.com/). The systems validates all my segments, says I am ready for booking, but when I am trying to book tickets (before payment), the following error occurs: The following error(s) occured
Error message (7820) not found for Language Code 'GB'
"No fare can be found for the flights and/or cabins you selected. Please search again and select another cabin and/or different flights. (5685 - 2201)"

I tried many times, changed my flights, but I cannot fix it. There is no way to directly contact someone in OneWorld (which is quite annoying), and I tried to contact airlines of OneWorld but they don't know what is going wrong, have no contact with OneWorld, and the only thing AA can do for me is making a phone booking for 100 USD...

Did someone encountered similar issue ? Do you know any workaround here ? Any help would be strongly appreciated !!

Thanks !!

Julien

Welcome to FT, Julien. I have merged your thread with the existing topic covering issues with the online tool.

Gardyloo
Oneworld moderator

Have I encountered a bug in the tool or am I missing something in the rules?

I am working up a DONE4 ex-AMM for next year. The tool is completely satisfied with my itinerary and 'Book Now' yields a fare of US$7211 (+ 1243 tax), which is consistent with the JOD 5100 price quoted in various sources.

(I haven't actually tried to enter passenger and credit card info this time because I have met that bug in the past and expect to book this through a Canadian TA.)

Now, I understand the 'you must start and end in the same country' rule, but I also see that one of the exceptions to this rule is when both start and end are 'within the Middle East'. However, when I change only the end-point of my trip from AMM to MCT, something funny happens. The tool is still happy with the routing but 'Book Now' reports a fare of US$8463 (+ 1456 tax). I can understand that the taxes might be different (i.e., more); OK. But in this case it looks like the base fare being quoted is now the ex-Oman price, rather than the ex-Jordan price. But the trip still starts in Jordan!

So ... back to the question with which I began. Any insights appreciated.

cheers,

Henry

To understand this bug a little better, might you be able to change the endpoint to be Cairo instead, to see what impact that has?

Good suggestion. Changing the endpoint to CAI brings the base fare back to US$7211 i.e., the ex-Jordan price -- not the substantially lower ex-Egypt rate!

cheers,

Henry

This same bug was noted earlier in the ex-KRT fare thread. To my knowledge no-one has diagnosed its cause.

It'd be nice if a OneWorld liaison could take a look at these bugs and prioritise them to be fixed.

I cant get it priced up online even removing intra US segments
 

Have been trying to price up a DONE4 for serveral days. As suggested removed inter US segments. Now get a different error as follows:

The following error(s) occured
An error has occurred in our central database. Please contact us for further information. (4002 [141])

Hi Julien,

I got this error today when I plugged in a routing I wanted. I think the trick here is to play with the routing and 'dumb it down'. I found on my routing if I took out some sectors that backtracked through LHR the tool would price up the itinerary without any error.
I think the sage advice from this board is that if you encounter any errors like this book the route that works and then stump up the 125USD change fee once ticketed to get it the way you want.

What was the routing you wanted to book?

The tool appears not to correctly handle the highlighted rule
I was trying an itinerary CPT-LHR...HKG-xLHR-NBO (with a 4hr transit in LHR between HKG and NBO)
and the tool gives me the message

I amended the ex-AMM DONE4 I've been planning, changing it to CAI-...-CAI. The first flight is RJ to AMM so the online tool still sends it to aa.amadeus for pricing. Price is quoted as US$7904, which looks right for the $6700 ex-Egypt fare plus taxes & fees. However -- and here's why I'm posting this, another data point -- when I give my personal details and credit card info, it fails at the very last step (as with the ex-KRT and ex-AMM itineraries reported by others in this thread).

The error message is as follows:

> An error occurred during creation of your booking. Please
> contact your Travel Assistance Desk to check if the booking
> was successful and to obtain further assistance. (9015)

I have not yet called AA RTW about this but it is now over three hours since I tried it and there is still no charge, hold or authorization for any amount on my VISA account, so I'm guessing the booking was not successful. :(

cheers,

Henry

I have an ex-SFO DONE5 I've been trying to get the online tool to let me pay for all week. Initially I was only getting 15012 errors. On Wednesday I called the AA ATW desk and the agent ran through my entire itinerary to check that there was actual D inventory. She suggested one changes and said that would make it though, except it didn't.

Since that time I not only continue to get 15012 errors, but also 9015 and 5685-2201 errors. At one point I was able to flip pretty reliably between 15012 and 9015 by changing my first segment from JL1 to AA5815 (AA codeshare number for same JL operated flight).

I've eliminated all codeshares since some comments upthread and elsewhere seem to correlate that with failures, and I've eliminated all LAN flights due to problems discussed earlier in the fall on the AA forum which I don't know are relevant since that discussion was about award booking.

The tool said the itinerary is validated and every segment has availability every time (including the segment that the AA ATW agent said did not have availability: LA601).

Is the first flight operated by S7, RJ or JL? They are ticketed by AA when booked via the tool and have been causing problems for some time.
When AA is the ticketing carrier, but doesn't operate the first flight (either due to codeshare or S7, RJ or JL sending to AA to ticket) the tool has failed during the booking stage.

???

cheers,

Henry

As I mentioned, the first flight is JL1, so it does invoke the condition where AA tickets but does not operate.

However, as a followup I have now gotten all the way through with some further modification. I was originally traveling ZRH to LIM via MAD, either IB/IB or IB/LA, but with a change in the connection to JFK (AA/LA) and no other modifications it went through.

The first segment is still JL1, so that is not a sufficient condition to cause the booking stage to fail.

At what point does it fail?

Unless it has been fixed in the last few months, this bug allows the booking to go through the entire process before failing on the last page (credit card details) of the booking.

All failures were at the last stage when I put in credit card info and pressed "Confirm fare", just as you describe.

Now that has succeeded, even with a JL flight as the first segment. I have a record locator and the reservation is listed as "Ticketed" status on aa.com.