关于Sabre BargainFinderMax按价格分组返回结果的技术咨询

Great question! Yes, Sabre's BargainFinderMax (OTA_AirLowFareSearchRQ) does support grouping identical-price itineraries into consolidated "price point" structures, just like TravelPort's behavior when you set SolutionResult="false". Here's exactly how to implement this for your use case:

Key Request Parameters to Enable Grouping #

To trigger price-based grouping, you need to add specific configuration to your OTA_AirLowFareSearchRQ request:

• GroupByPrice: Set this to true within the <SearchPreferences> section of your request. This tells Sabre to aggregate itineraries that share the same total fare, fare basis codes, booking classes, and core fare rules.
• Response Type Compatibility: You mentioned you're already working with OTA and GIR response types—good news, grouping works with both. The GIR format will give you the most direct parallel to TravelPort's PricePoint structure, while OTA will group itineraries under shared pricing containers.

What the Grouped Response Looks Like #

For GIR Responses #

This is the closest match to TravelPort's grouped results. You'll see top-level <PricePoint> elements, each containing:

• Pricing details (total fare, taxes, fare basis codes)
• A list of <ItineraryRef> entries that point to all individual itineraries (with different segments) that share this exact price point.

For OTA Responses #

Instead of separate <AirItinerary> entries for each itinerary, you'll find shared <AirItineraryPricingInfo> elements that wrap multiple <AirItinerary> objects. All itineraries under the same pricing info element are guaranteed to have identical pricing and fare rules.

Important Notes #

• Grouping Logic: Sabre doesn't just group by total price—it also considers fare components, booking codes, and ticketing eligibility. So two itineraries with the same price but different fare rules won't be grouped together, which helps avoid mixing incompatible options.
• API Version Check: If you're using an older version of BargainFinderMax, confirm that GroupByPrice is supported (it's included in all recent stable releases, but it's worth verifying against your specific API version's documentation).
• Fare Filters: If you want to refine grouping further, you can add fare basis code filters or other search preferences to narrow down which itineraries are eligible for grouping.

内容的提问来源于stack exchange，提问作者Darab Javaid