Originally Posted by
entropy
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...
I wonder what the spec is here. Is this spec for a "PNRGOV message" relevant?
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.)