Ability to provide detailed historical information on orders (for both voluntary and involuntary changes).
Ability to request detailed historical information on orders.
https://guides.developer.iata.org/v213/docs/capord16-historical-information-on-orders
https://guides.developer.iata.org/v213/docs/conord03-order-versioning
https://guides.developer.iata.org/v213/docs/order-history
Following release v19.2, the OrderHistoryRS message resembles OrderChangeNotifRQ very closely in its design. OrderHistoryRS is intended to carry an accumulation of the changes synchronized via OCN. In addition, it should also reflect changes requested by the Seller (voluntary changes), as well as airline-triggered changes.
In theory, understanding and applying all changes that happened in an Order’s lifecycle unto the first original version of the Order (at the time of OrderCreateRQ) should result in the latest snapshot of that Order as it appears in the Airline’s Order Management System.
Versioning of an Order is, therefore, an important new concept for OrderChangeNotifRQ and OrderHistoryRS, as the Seller uses this information to detect whether or not they are out of sync with the Airline’s latest version of an Order and if they have missed any important changes to an Order during its lifecycle.
If a Seller detects, through an OrderRetrieveRQ, that the Order returned by the Airline is unexpectedly several versions higher than they expected, the Seller could resynchronize the missing changes by retrieving the OrderHistoryRS.
Any one of the following message pairs |
---|
OrderHistoryRQ/OrderHistoryRS |
Any one of the following message pairs |
---|
OrderHistoryRQ/OrderHistoryRS |