|
The technical reason why you can't do this is that UA's reservations system enforces constraints for a multi-passenger PNR which require that every passenger must have identical flight numbers and fare codes.... |
Originally Posted by entropy
(Post 20658034)
All res systems have this 'feature'. It makes a lot of sense too. You introduce a lot of oddities if you have people flying different routes, etc. The only limitation where it makes less sense is the uniformity in booking codes, there should be a solution to that...
http://www.wcoomd.org/en/topics/faci...n%20Guide.ashx If I read pages 8 & 9 correctly, the spec allows per-passenger fare information to be stored within a single PNRGOV message, just as it allows per-passenger notes (Other Special Information), ticket numbers, and method of payment information. (This is just the spec for a PNR as given to governments, though, not the base spec for a PNR — it may be that the airline-to-airline PNR is required to store fare class information in the bits of the header that include the flight number that must be the same for every passenger.) |
| All times are GMT -6. The time now is 7:56 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.