Originally Posted by
UAL123
The AS ticket shows as John Smith and that is what shows on the CX website when looking up the booking as well. I sent a twitter message to CX asking about the middle name and they stated that the ticket needs to match my passport exactly. Apparently they did put a note on my booking to mention my middle name. That is all they could do since it was ticketed with AS and they did say that they couldn't guarantee there won't be issues at check-in.
I then called AS. They said they don't put middle names on the ticket and they couldn't do anything for me there. I even asked if they could add my middle name to the first name field, but in order to do that I would have to cancel and rebook which would potentially risk me loosing the award space. They did say that they added my middle name (Peter) to the secure flight information. They said that that is what the airline looks at anyway and I would have no troubles. We'll see and I will keep monitoring this thread before my flight.
My first post on this topic (#9 above) was the same situation. AS was the "partner award" I was referring to. (Many on this board hyperventilate at the mention of AS redemptions, so I avoid directly using their name when possible.
) It's strange AS told you they don't use middle names because I directly discussed with them the whole middle-name CX drama. They confirmed my middle name was there, and they walked through and OLCI with me (both of us independently and simultaneously walking it through online). It was during that walk-though that I saw the warning message during OLCI, but there was a button that allowed me to proceed anyway (which I did). The full story is in #9 , so I won't repeat here.
Anyway, CX is causing needless anxiety. Hat tip to seawolf for what I think this is probably the best explanation:
Originally Posted by
seawolf
Please keep the following in mind.
- CX systems (Amadeus) only have two name fields; LAST and GIVEN. BA is the same as they use Amadeus.
- AA systems (SABRE) have three name fields; LAST, FIRST, and MIDDLE. When passenger provide MIDDLE name on AA.com or via AAdvantage profile, the MIDDLE name gets dropped when the CX/BA PNR is created and thus causing a mismatch with passport
- Based on datapoInts reported, it appears a mismatch will cause OLCI to fail but passenger should have no problem at airport.
I think AA/AS DOES transmit middle names, but the middle name DOES NOT not get dropped by CX, and maybe THAT is what is causing the problem. I just checked both my profiles. The AS profile does indeed have three separate name fields, and my MPC profile has only two. In my MPC profile, I have only my first name entered for my GIVEN NAME. So, if AA/AS only transmitted all name, and CX only accepted the FIRST NAME (and compared it) to my GIVEN NAME, then all would match.
Alternatively, (or likewise?) if I set my GIVEN NAME in my CX profile to First and Middle, then it would not match with the info coming from SABRE, because in those profiles I have the first, middle, and last fields entered appropriately. AA/AS would transmit my first name only, and CX would accept it (and compare it) to my GIVEN NAME and FAIL the compare.
Now having seen this, I wonder if changes are appropriate? Maybe the thing to do is to do first and middle in GIVEN NAME field in CX, and the first and middle in the FIRST NAME field for all others. Do it now, while I don't have any booked travel.