Accepting All Schedule Changes

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. There are options to:

Accepting the schedule changes modifies either the status code of the segment or cancels unnecessary segments.

Schema

Located in Universal.xsd:

How To

  1. To accept all schedule changes within a Universal Record, use AckScheduleChangeReq. Include the minimum information:

    • To accept changes to all segments, regardless of provider, send only @UniversalRecordLocatorCode. All segments associated with that UniversalRecordLocatorCode are modified or canceled based on the business rules.

    • To only accept segments in the PNR matching a particular provider, also include @ProviderCode and @ProviderLocatorCode.

    • If @ReservationLocatorCode is sent without a ProviderLocatorCode, then all segments associated with that ReservationLocatorCode are modified or canceled based on the business rules.

  2. AckScheduleChangeRsp returns the Universal Record with the accepted schedule changes. See Accepting Schedule Changes for a list of the status codes used by each provider for changes and cancellations.

Exceptions

Galileo

Worldspan

Worldspan does not support the status change of individual segments in a reservation. Only the status change of all segments on the reservation is supported by Worldspan.

ACH

RCS

RCS suppliers do not support schedule changes.