Switching off customer enhancements in SAP CRM for symptom analysis

Print Friendly

Hi, as much as we prefer to implement clean standard SAP processes at our customers, it's inevitable that sooner or later the customer wants to have the system adapted to his own needs and way of working. As such the implementation team will often need to enhance the customer's SAP CRM system.

Now, during the implementation phase, you"ll probably also encounter a lot of bugs, BSP errors, short dumps when testing the application during Unit Testing and User Acceptance Testing. Now -that's quite normal - but what you"ll be intrested in is to find out if such a problem occurs because of your customer changes or that it might be a problem situated in the SAP Standard solution. In the latter case you"ll probably should look for relevant OSS notes, or even open a customer message at SAP itself using service.sap.com using the famous S-user Account :-) 

Here are some practical tips how you can find out if such a problem is probably caused by changing the SAP Standard or not !

Switching off customer enhancements for symptom analysis

Relevant OSS note: 1311966 


You want to analyze the system behavior of an application using the WebClient UI framework in a customer system. It is not clear whether certain symptoms are caused by customer enhancements / customizing or by the standard SAP delivery.


The attached correction instruction cannot contain all necessary changes. Therefore a preliminary correction is not possible and the Support Package is required. Once the respective Support Package is implemented, set the user parameter WCF_IGNORE_ENHANCEMT to value 'A' to disable all customer enhancements in these areas:

Enhancement Sets • UI Configurations • UI Personalizations • Field labels in text repository • Changes in Design Layer (design objects and assignments) • Table Enhancements (7.0 EhP 1) • Embedded Rapid Applications (7.0 EhP 1) • Mash-ups (7.0 EhP 1)


Keep in mind to remove this user parameter once you are done with the analysis.  :-)

You can set this parameter using the transaction code SU3 for example:



How to switch off customer enhancements without disabling customer UI configurations and personalizations

Please make sure to check out SAP OSS note 1718834


In order to check if an issue is caused by customer enhancements or by the standard SAP delivery, we always set user parameter WCF_IGNORE_ENHANCEMT to value 'A' as per SAP Note 1311966  to switch off customer enhancements. But in some cases, some fields and assignment blocks disappear due to this parameter which makes us unable to follow the reproducing steps.

You don't know how to switch off enhancement set without disabling UI Configurations and Personalizations.

Please note that user parameter WCF_IGNORE_ENHANCEMT is only applicable to CRM 7.0 and higher release.


Using parameter WCF_IGNORE_ENHANCEMT also disables all customer UI Configurations and UI Personalizations.


Clear enhancement set in debugging mode instead of set parameter WCF_IGNORE_ENHANCEMT to value 'A'.

During debugging mode, blank out rv_result in Method IF_BSP_WD_CMP_LOADING_BADI~GET_ACTIVE_ENHANCEMENT_SET of corresponding active implementations of BADI COMPONENT_LOADING.


Davy has been working as an SAP Consultant since 2000 and started working in the SAP IS-U Module , but as of 2002 he has mainly worked as functional SAP CRM consultant and SAP Authorizations consultant.
More about

One thought on “Switching off customer enhancements in SAP CRM for symptom analysis

Leave a Reply