几天前,我遇到了其他日期的军刀记录问题,现在终于得到了记录,但记录却少得多,例如当我在7天的时间内搜索往返AD3时,仅有49条路线并从军刀单向AD1 9记录。 XML请求有问题吗?
下面是XML请求
<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header><m:MessageHeader xmlns:m="http://www.ebxml.org/namespaces/messageHeader">
<m:From>
<m:PartyId type="urn:x12.org:IO5:01">http://deluxholidaysnew.local</m:PartyId>
</m:From>
<m:To>
<m:PartyId type="urn:x12.org:IO5:01">https://sws-crt.cert.havail.sabre.com</m:PartyId>
</m:To>
<m:CPAId>****</m:CPAId>
<m:ConversationId>V1@dXIIccWqTWCaYP1Nil099DvScws2Fuy2ufg1d2Zb@5b8aa3bcbfe2c@http://test.local</m:ConversationId>
<m:Service m:type="OTA">BargainFinderMax_ADRQ</m:Service>
<m:Action>BargainFinderMax_ADRQ</m:Action>
<m:MessageData>
<m:MessageId>968799525452240610</m:MessageId>
<m:Timestamp>2018-09-01T15:35:42Z</m:Timestamp>
<m:TimeToLive>2018-09-01T16:35:42Z</m:TimeToLive>
</m:MessageData>
<m:DuplicateElimination/>
<m:Description>BargainFinderMax_ADRQ</m:Description>
</m:MessageHeader>
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext">
<wsse:BinarySecurityToken valueType="String" EncodingType="wsse:Base64Binary">Shared/IDL:IceSess\/SessMgr:1\.0.IDL/Common/!ICESMS\/ACPCRTC!ICESMSLB\/CRT.LB!1535812545543!1815120!65537</wsse:BinarySecurityToken>
</wsse:Security></SOAP-ENV:Header><SOAP-ENV:Body><OTA_AirLowFareSearchRQ xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Target="Production" Version="4.2.0" ResponseType="OTA" ResponseVersion="4.2.0">
<POS>
<Source PseudoCityCode="****">
<RequestorID ID="1" Type="1">
<CompanyName Code="TN" />
</RequestorID>
</Source>
</POS>
<OriginDestinationInformation RPH="1">
<DepartureDateTime>2018-09-08T00:00:00</DepartureDateTime>
<OriginLocation LocationCode="DXB" />
<DestinationLocation LocationCode="KHI" />
<TPA_Extensions>
<DateFlexibility NbrOfDays="3"/>
<SegmentType Code="O" />
</TPA_Extensions>
</OriginDestinationInformation>
<OriginDestinationInformation RPH="2">
<DepartureDateTime>2018-09-15T00:00:00</DepartureDateTime>
<OriginLocation LocationCode="KHI" />
<DestinationLocation LocationCode="DXB" />
<TPA_Extensions>
<DateFlexibility NbrOfDays="3"/>
<SegmentType Code="O" />
</TPA_Extensions>
</OriginDestinationInformation>
<TravelPreferences ValidInterlineTicket="true" >
<CabinPref PreferLevel="Preferred" Cabin="Y" />
<TPA_Extensions>
<TripType Value="Return" />
<LongConnectTime Min="780" Max="1200" Enable="true"/>
<ExcludeCallDirectCarriers Enabled="true"/>
</TPA_Extensions>
</TravelPreferences>
<TravelerInfoSummary>
<SeatsRequested>1</SeatsRequested>
<AirTravelerAvail>
<PassengerTypeQuantity Code="ADT" Quantity="1" />
</AirTravelerAvail>
<PriceRequestInformation CurrencyCode="PKR" >
<TPA_Extensions>
</TPA_Extensions>
</PriceRequestInformation>
</TravelerInfoSummary>
<TPA_Extensions>
<IntelliSellTransaction>
<RequestType Name="AD3"/>
</IntelliSellTransaction>
</TPA_Extensions>
</OTA_AirLowFareSearchRQ></SOAP-ENV:Body></SOAP-ENV:Envelope>
答案 0 :(得分:1)
按照RequestType中的BargainFinderMax_ADRQ的设计,您只能包含以下选项:
<!-- Name="AD1" will return itineraries for up to 9 alternate date combinations (+/-1 day for departure and return date). -->
<!-- Name="AD3" will return itineraries for up to 49 alternate date combinations (up to +/-3 days for departure and return date). -->
当您包含AD1时,它将基于3x3矩阵返回9个选项,该矩阵包括所有不同组合的出站支路的3个选项和入站支路的3个选项。备用日期是为了提示您,如果您选择其他旅行日期,则还有其他选择,可能会降低票价。
如果您有相同的标准,并且有AD3往返请求,我们将为出站提供7个选项(前3天为3个选项,原始日期为1个选项,原始日期为3个选项),之后为7个选项入站。这将基于7x7矩阵总共提供49个选项。
不幸的是,这是BFM替代日期逻辑的局限之一,因为它仅根据请求的日期(AD1中为3x3,AD3中为7x7)生成矩阵。