3829578 - Why is the CHS hotel not displayed as preferred even though it is set up in Concur?

By connecting to a CHS provider, the application will be disconnected from GDS content. Therefore, rules, policies and settings that reference GDS content (e.g. GDS Property IDs) will no longer work. These settings may include rules linked to Contract Rates, and rules linked to Property IDs and Preferences that are specific to a property and property identification.

Property-level preference settings:

• Preference settings applied under the property-specific Hotel Discount Section in the Concur Travel Discount Admin will not be applied to CHS results.

• Chain preference settings are supported for Travel Configurations that enable CHS connections.
• Super chain codes (e.g. EM – Marriott International) are currently not supported to be sent via the Hotel Service API. Therefore, chain-level preferences set up by an administrator for a super chain will not be applied to CHS search results.
• In a case where both the chain preference is set through Concur Admin and the provider sends preference setting for a specific property to be applied to search results, the chain preference set through Concur Admin will take precedence over the response sent by the provider via the Hotel Service API.
• If the provider-controlled property preference is preferred over the admin controlled chain preference, the recommendation is to remove the chain preference from the Admin section.

This article explains the impact on rules, policies, and preference settings when a Travel Configuration is connected to a CHS (Central Hotel Service) provider in SAP Concur. , KBA , CON-MOB-TRV-HTL , Hotel , Problem