If a schedule change is indicated after a Universal Record is retrieved, the user or client application must determine whether to accept the schedule changes. Schedule or price changes are indicated in AirSolutionChangedInfo.
There are options to:
-
Accept all schedule changes in the Universal Record.
-
Accept individual schedule changes by segment (instructions provided below).
Accepting the schedule changes modifies either the status code of the segment or cancels unnecessary segments.
Schema
Located in Universal.xsd:
- UniversalRecordModifyReq
- UniversalRecordModifyRsp
How To
-
To accept schedule changes for individual segments, use UniversalRecordModifyReq/UniversalModifyCmd/AirUpdate/AirSegment.
-
Include @Key, which is the unique key used to identify the air segment to be updated.
-
Specify the new status code of the air segment using @Status. See Accepting Schedule Changes for a list of the status codes used by each provider for changes and cancellations.
-
-
UniversalRecordModifyRsp is returned with the updated Universal Record. Any response message from the provider or supplier is also returned.
Exceptions
Galileo
-
Any stored fare related to the updated segment is automatically removed.
Note: Samples may not be updated for each release if there are no schema or functionality changes that affect the sample. Always confirm the desired schema version before testing or implementing the sample.
ACH
-
ACH carriers sends an email directly to the traveler in the event of a schedule change.
-
If a reservation is retrieved after a schedule change, the segments are updated.
RCS
RCS suppliers do not support schedule changes.