Structure of the Order Change Notification
  • Updated on 18 May 2020
  • 2 minutes to read
  • Contributors
  • Print
  • Dark
    Light

Structure of the Order Change Notification

  • Print
  • Dark
    Light

Use Cases

Passenger initiated changes

"The passenger contacts the Airline (ORA) directly and makes a change in the Order instead of contacting the travel agent. The Airline (ORA) needs to communicate the changes to the Order.”

In this use case, the following scenario is covered:

• Notification of name and/or phone contact detail changes

Airline (ORA) initiated changes

"The Airline (ORA) makes changes to the Order. The Airline (ORA) needs to communicate the changes to the Order."

In this use case, the following scenario is covered:

• Notification of payment status changes

Airline (ORA) performs schedule change

"The Airline (ORA) performs a schedule change. The Airline (ORA) needs to communicate the changes to the Order. The Airline (ORA) notifies the following indicators/data: Airline URI, whether an acceptance is needed, a time limit to accept the changes, consequence of inaction, and fare waiver details (if applicable)."

In this use case, the following scenarios are covered:

• Notification of flight segment time changes (schedule change)
• Notification of flight segment number changes (schedule change)
• Notification of flight segment arrival and/or departure changes (schedule change)
• Notification of flight equipment changes (schedule change)
• Notification of flight cancellation (schedule change)
• Notification of flight changes (schedule change)
• Notification of Airline URI
• Notification of schedule change acceptance
• Notification of schedule change time limit
• Notification of schedule change consequence of inaction
• Notification of schedule change fare waiver (if applicable)

Business Functions

01. Inform Seller of passenger name and/or contact details changes

02. Inform seller of payment status changes

03. Inform seller of flight segment time changes - schedule Change

04. Inform Seller of flight number changes - Schedule Change

05. Inform Seller of flight arrival and/or departure changes - Schedule Change

06. Inform Seller of flight equipment changes - Schedule Change

07.Inform Seller of flight cancellation - Schedule Change

08.Inform seller of flight changes

Message Flow

Passenger or Airline (ORA) initiated changes

image.png

This message flow applies to the following business functions:

• Inform Seller of passenger name and/or contact details changes
• Inform Seller of payment status changes

Airline (ORA) performs schedule change

image.png

This message flow applies to the following business functions:

• Inform Seller of flight segment time changes (Schedule Change)
• Inform Seller of flight arrival and/or departure changes (Schedule Change)
• Inform Seller of flight equipment changes (Schedule Change)
• Inform Seller of flight cancellation (Schedule Change)
• Inform Seller of flight changes (Schedule Change)

Technical Capability

Multiple change operations in a group

Allows the notification of multiple change operations in separate groups. This allows implementers to batch multiple change operations.

  1. Implementers may send a single Order change per OrderChangeNotifRQ
  2. Implementers may send multiple Order changes in a single group per OrderChangeNotifRQ
  3. Implementers may send multiple groups of Order changes per OrderChangeNotifRQ

Triggers to batch change operations are not defined in this document.

Include Order snapshot (before or after an Order change is committed)

Allows the notification of the Order before (or after) an Order change has occurred. This allows implementers to provide contextual data to receiving systems that cannot store Order details.

  1. Implementers may send an Order change update without the Order snapshot
  2. Implementers may send an Order change update with the Order snapshot