Order: Historical information on orders [ORDHIS]

Guidance for Schema Version:

20.2

Definition of Capability

Airline

Ability to provide detailed historical information on orders (for both voluntary and involuntary changes).

Seller

Ability to request detailed historical information on orders

NOTE: System Providers will use the above definition that pertains to their customers for Capabilities Verification.

Links to EASD Implementation Guidance

Not available

NOTE: Retailing Capabilities Verification Guidance will align to the published EASD Implementation Guidance at all times. From time to time when new guidance is published this will be updated and supersede any Retailing Capabilities Verification Guidance listed below.

Retailing Capabilities Verification Guidance

Following release v19.2, the OrderHistoryRS message resembles OrderChangeNotifRQ very closely in its design. OrderHistoryRS is intended as an accumulation of change synchronized via OCN. In addition, it should reflect changes requested by the Seller (voluntary 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 now an important new concept for OrderChangeNotifRQ and OrderHistoryRS, as the Seller is able to detect whether or not they are out of sync with the Airline or 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.

Airline

Any one of the following message pairs

OrderHistoryRQ/OrderHistoryRS

Seller

Any one of the following message pairs

OrderHistoryRQ/OrderHistoryRS

NOTE: For all versions prior to that listed above (generally the most recent), the verification will be based on the guidance available for that version. In the case that no guidance is available, verification will be at IATA’s discretion.