The Airline has the ability to change an Order without the need to reshop. This capability is validated based on updating Passenger details.
The Seller has the ability to request a change to an Order without the need to reshop. This capability is validated based on updating Passenger details.
Capability: Seller-initiated Change to an Order, Variant 2: https://standards.atlassian.net/wiki/spaces/EASD/pages/574554168
Concept: Modification of an Order: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619782
Concepts: Offers & Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574750733 and https://standards.atlassian.net/wiki/spaces/EASD/pages/574717963
Capabilities: Offers & Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574750721 and https://standards.atlassian.net/wiki/spaces/EASD/pages/574259560
Worked Examples: Offers & Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574881865 and https://standards.atlassian.net/wiki/spaces/EASD/pages/574619770
For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages:
Updating passenger details works by providing the old data together with the new data it is meant to replace within the following function of OrderChangeRQ:
If only new data is being appended to the passenger’s profile, then the “Current” must be provided, but only for the PaxID (no other details required).
Updating passenger details requires the following steps:
Seller enters reference ID of the passenger (as it appears in OrderViewRS) in the “Current” element:
and includes the passenger details that are required to change under DataLists/PaxList/Pax:
Seller enters a Seller-generated Passenger reference ID (this is temporary and used only within a single XML API transaction):
and includes the new passenger details intended to replace the details earlier provided under the “Current” structure.
The Airline’s OrderViewRS should then reflect the modified and/or appended details. Note: The PaxID returned should still be the same as per previous OrderViewRSs.
This function is not intended for modifications to a passenger’s name - use the “Names changes/corrections through reshopping“ capability instead.
e.g. correcting a contact phone number:
... <ChangeOrder> <UpdatePax> <Current> <PaxRefID>PAX001</PaxRefID> </Current> <New> <PaxRefID>112233</PaxRefID> </New> </UpdatePax> </ChangeOrder> ... <DataLists> <PaxList> <ContactInfoList> <ContactInfo> <ContactInfoID>CTC123</ContactInfoID> <Phone> <PhoneNumber>+1 222 333 444</PhoneNumber> </Phone> </ContactInfo> <ContactInfo> <ContactInfoID>CTC456</ContactInfoID> <Phone> <PhoneNumber>+1 555 666 777</PhoneNumber> </Phone> </ContactInfo> </ContactInfoList> <Pax> <ContactInfoRefID>CTC123</ContactInfoRefID> <PaxID>PAX001</PaxID> </Pax> <Pax> <ContactInfoRefID>CTC456</ContactInfoRefID> <PaxID>112233</PaxID> </Pax> </PaxList> </DataLists> ... <Order> <OrderID>ORD12345</OrderID> <OwnerCode>XB</OwnerCode> </Order> ...