AltDate Usage
You can view the following usage information:
One-Way Alt Dates
Flight DFW-MIA 20JUN.
The rule with Alt Dates service has the following values:
- Alt Date Departure Minus=3
- Alt Date Departure Plus=2
Following is a one-way option example:
|
17JUN |
18JUN |
19JUN |
20JUN |
21JUN |
22JUN |
|---|---|---|---|---|---|
|
1 |
1 |
1 |
1 |
1 |
1 |
The Alt Dates service returns 6 options with dates as shown in the table. Search will be performed for ±3 days.
OTA One-Way Request
An example OTA request for NYC-TYO 01SEPT with Alt Dates can appear as follows:
<?xml version="1.0" encoding="UTF-8"?>
<OTA_AirLowFareSearchRQ xmlns:xs="http://www.w3.org/2001/XMLSchema" Target="Production" Version="2.0" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<POS>
<Source PseudoCityCode="W0H3">
<RequestorID Type="0.AAA.X" ID="REQ.ID">
<CompanyName Code="OTAQA"/>
</RequestorID>
</Source>
</POS>
<OriginDestinationInformation RPH="1">
<DepartureDateTime>2008-09-01T08:00:00</DepartureDateTime>
<OriginLocation LocationCode="NYC"/>
<DestinationLocation LocationCode="TYO"/>
<TPA_Extensions>
<DateFlexibility NbrOfDays="2"/>
<SegmentType Code="O"/>
</TPA_Extensions>
</OriginDestinationInformation>
<TravelPreferences>
<TPA_Extensions>
</TPA_Extensions>
</TravelPreferences>
<TravelerInfoSummary>
<SeatsRequested>1</SeatsRequested>
<AirTravelerAvail>
<PassengerTypeQuantity Code="ADT" Quantity="1"/>
</AirTravelerAvail>
<PriceRequestInformation>
<TPA_Extensions>
</TPA_Extensions>
</PriceRequestInformation>
</TravelerInfoSummary>
<TPA_Extensions>
<IntelliSellTransaction Debug="0">
<RequestType Name="ALTDATES"/>
<SabreAth Value="" BinarySecToken="" ConversationID=""/>
</IntelliSellTransaction>
</TPA_Extensions>
</OTA_AirLowFareSearchRQ>
If a rule used by this request has the Alt Dates service turned on, the search will be performed for ±2 days. If a different date range is specified in the rule, it will be discarded, and the setting from the request will be used.
Round-Trip Alt Dates
- Alt Date Departure Minus=3
- Alt Date Departure Plus=2
- Alt Date Return Minus=3
- Alt Date Return Plus=2
Outbound flight DFW-MIA 20JUN and inbound flight MIA-DFW 24JJUN.
Following is a round-trip options example:
|
Return | Departure |
17JUN |
18 JUN |
19JUN |
20JUN |
21JUN |
22JUN |
|---|---|---|---|---|---|---|
|
21JUN |
1 |
1 |
1 |
1 |
X |
X |
|
22JUN |
1 |
1 |
1 |
1 |
1 |
X |
|
23JUN |
1 |
1 |
1 |
1 |
1 |
1 |
|
24JUN |
1 |
1 |
1 |
1 |
1 |
1 |
|
25JUN |
1 |
1 |
1 |
1 |
1 |
1 |
|
26JUN |
1 |
1 |
1 |
1 |
1 |
1 |
For dates 21JUN-21JUN, and 22JUN-22JUN, there are no Alt Dates because flights with the same outbound and inbound dates are not returned.
For dates 22JUN-21JUN, there is no option because the departure date must be before the return date.
In the example, the Alt Dates service returns 33 options.
Search will be performed for ±3 days for each segment.
OTA Round-Trip Example
An example OTA request for NYC-TYO 01AUG-01SEP with Alt Dates can appear as follows:
<?xml version="1.0" encoding="UTF-8"?>
<OTA_AirLowFareSearchRQ xmlns:xs="http://www.w3.org/2001/XMLSchema" Target="Production" Version="2.0" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<POS>
<Source PseudoCityCode="W0H3">
<RequestorID Type="0.AAA.X" ID="REQ.ID">
<CompanyName Code="OTAQA"/>
</RequestorID>
</Source>
</POS>
<OriginDestinationInformation RPH="1">
<DepartureDateTime>2007-08-01T08:00:00</DepartureDateTime>
<OriginLocation LocationCode="NYC"/>
<DestinationLocation LocationCode="TYO"/>
<TPA_Extensions>
<DateFlexibility NbrOfDays="3"/>
<SegmentType Code="O"/>
</TPA_Extensions>
</OriginDestinationInformation>
<OriginDestinationInformation RPH="2">
<DepartureDateTime>2007-09-01T08:00:00</DepartureDateTime>
<OriginLocation LocationCode="TYO"/>
<DestinationLocation LocationCode="NYC"/>
<TPA_Extensions>
<DateFlexibility NbrOfDays="3"/>
<SegmentType Code="O"/>
</TPA_Extensions>
</OriginDestinationInformation>
<TravelPreferences>
<TPA_Extensions>
</TPA_Extensions>
</TravelPreferences>
<TravelerInfoSummary>
<SeatsRequested>1</SeatsRequested>
<AirTravelerAvail>
<PassengerTypeQuantity Code="ADT" Quantity="1"/>
</AirTravelerAvail>
<PriceRequestInformation>
<TPA_Extensions>
</TPA_Extensions>
</PriceRequestInformation>
</TravelerInfoSummary>
<TPA_Extensions>
<IntelliSellTransaction Debug="0">
<RequestType Name="ALTDATES"/>
<SabreAth Value="" BinarySecToken="" ConversationID=""/>
</IntelliSellTransaction>
</TPA_Extensions>
</OTA_AirLowFareSearchRQ>
If a rule used by this request has the Alt Dates service turned on, the search will be performed for ±3 days for each segment. If a different date range is specified in the rule for a given segment, it will be discarded and the setting from the request will be used.
OTA Schema
In the OTA schema, the pricing source is specified in attribute PricingSource of PTCFareBreakdownType element:
<PTCFareBreakdownType PricingSource="ADI1" …>…
The full XPath to this attribute is “OTA_AirLowFareSearchRS/PricedItineraries/PricedItinerary/AirItineraryPricingInfo/@PricingSource”.
Analogously to the XML2 schema example above, the first two options returned by Alt Dates search for a round-trip NYC-TYO 1AUG-1SEP, ±2 days for outbound and inbound, could look like the following in the XML response:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<OTA_AirLowFareSearchRS Version="1.00" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Success/>
<Warnings>
<Warning Type="DEFAULT" Code="RULEID" ShortText="11628"/>
<Warning Type="DRE" Code="RULEID" ShortText="15035"/>
<Warning Type="SERVER" Code="ATSELB07" ShortText="27091"/>
<Warning Type="WORKERTHREAD" Code="TRANSACTIONID" ShortText="5065910493953130497"/>
</Warnings>
<PricedItineraries>
<PricedItinerary SequenceNumber="1">
<AirItinerary DirectionInd="Return">
<OriginDestinationOptions>
<OriginDestinationOption>
<FlightSegment DepartureDateTime="2007-07-30T13:30:00" ArrivalDateTime="2007-07-31T16:20:00" StopQuantity="0" FlightNumber="5" ResBookDesigCode="X">
<DepartureAirport LocationCode="JFK"/>
<ArrivalAirport LocationCode="NRT"/>
<OperatingAirline Code="JL" FlightNumber="5"/>
<Equipment AirEquipType="744"/>
<MarketingAirline Code="JL"/>
<MarriageGrp>O</MarriageGrp>
</FlightSegment>
</OriginDestinationOption>
<OriginDestinationOption>
<FlightSegment DepartureDateTime="2007-08-30T12:00:00" ArrivalDateTime="2007-08-30T11:30:00" StopQuantity="0" FlightNumber="6" ResBookDesigCode="X">
<DepartureAirport LocationCode="NRT"/>
<ArrivalAirport LocationCode="JFK"/>
<OperatingAirline Code="JL" FlightNumber="6"/>
<Equipment AirEquipType="744"/>
<MarketingAirline Code="JL"/>
<MarriageGrp>O</MarriageGrp>
</FlightSegment>
</OriginDestinationOption>
</OriginDestinationOptions>
</AirItinerary>
<AirItineraryPricingInfo PricingSource="ADI1">
<!-- More information follows ... -->
</AirItineraryPricingInfo>
<TicketingInfo TicketType="eTicket"/>
</PricedItinerary>
<PricedItinerary SequenceNumber="2">
<AirItinerary DirectionInd="Return">
<OriginDestinationOptions>
<OriginDestinationOption>
<FlightSegment DepartureDateTime="2007-07-31T13:30:00" ArrivalDateTime="2007-08-01T16:20:00" StopQuantity="0" FlightNumber="5" ResBookDesigCode="X">
<DepartureAirport LocationCode="JFK"/>
<ArrivalAirport LocationCode="NRT"/>
<OperatingAirline Code="JL" FlightNumber="5"/>
<Equipment AirEquipType="744"/>
<MarketingAirline Code="JL"/>
<MarriageGrp>O</MarriageGrp>
</FlightSegment>
</OriginDestinationOption>
<OriginDestinationOption>
<FlightSegment DepartureDateTime="2007-08-30T12:00:00" ArrivalDateTime="2007-08-30T11:30:00" StopQuantity="0" FlightNumber="6" ResBookDesigCode="X">
<DepartureAirport LocationCode="NRT"/>
<ArrivalAirport LocationCode="JFK"/>
<OperatingAirline Code="JL" FlightNumber="6"/>
<Equipment AirEquipType="744"/>
<MarketingAirline Code="JL"/>
<MarriageGrp>O</MarriageGrp>
</FlightSegment>
</OriginDestinationOption>
</OriginDestinationOptions>
</AirItinerary>
<AirItineraryPricingInfo PricingSource="ADI1">
<!-- More information follows ... -->
</AirItineraryPricingInfo>
<TicketingInfo TicketType="eTicket"/>
</PricedItinerary>
In the example, departure dates for the flights (FlightSegment/@DepartureDateTime) used by the options are shown in bold. Also in bold is pricing source (AirItineraryPricingInfo/@PricingSource).