This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Since At Your Service won't directly answer our questions regarding our travel policy, can someone help a newbie with the below:
--how the least cost logical fare is determined in Concur, i.e. average of lowest and highest fares?
--does searcher's physical location, traveler preferences (class/seat), season, availability etc. affect results for flight and hotel options?
--can you provide some examples of what your travel policies include/exclude?
Thank you kindly for attention! Have a good day all...
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@Sandra4 for the least cost logical use this link: https://help.sap.com/docs/CONCUR_TRAVEL/178215a2a80f49689f5b7909d51a0e9e/7263eba56da81014b915952c8f7....
As for physical location, I've never heard anything about this being a factor when booking.
I'll let others answer about their travel policies, but some common things are: no first or business class for flights, no pre-pay or deposit required for hotels and for rental cars it is usually nothing larger than an intermediate unless traveling with others.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Kevin,
Is the linked document you referenced still applicable to T2? I ask because of this reference:
All LLF fares are calculated based on results that contain a fare and are returned for the initial search request. That includes only results returned for a Shop by Price request and in flex faring markets also for a Flex Faring search (depending on activation).
For information about how to override this default, refer to the Delayed LLF section in this guide.
A Shop by Schedule request does not yet contain a fare, therefore no LLF is calculated.
When a user selects Shop by Schedule (or multiple segments in the case of a multi-city search), when the selected flights are priced, additional fares are returned that match the LLF definition more closely than the fares provided by the Shop by Price response.
Thanks,
Susan
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@u219981 I pulled this from our Help portal, so I would think it is up to date. I wouldn't think the LLF logic would really change from Legacy to T2.