Skip to Content
How to deactivate an enhancement set:

– BADI COMPONENT_LOADING  (UP TO CRM7.0 SP3)

– NOTE 1311966 –> USER PAREMETER: WCF_IGNORE_ENHANCEMT (FROM CRM7.0 SP3)
 

1) Up to CRM7.0 sp3 the enhancement set can be deactivated by debugging, setting a breakpoint inthe implementation of BADI “COMPONENT_LOADING:

Transaction SE18:

BADI  : COMPONENT_LOADING

image 

image 

 

image

Set an external Break Point in RV_RESULT = LS_ASSIGMENT-ENHANCEMENT_SET.

And clear the assigned value to RV_RESULT field:

 

image

 

2) From CRM7.0 SP3: note 1311966

User parameter WCF_IGNORE_ENHANCEMT to value ‘A’  in transaction SU3.

This will disable all customer enhancements in these areas:                       
                                                                        
    o  Enhancement Sets                                                 
                                                                        
    o  UI Configurations                                                
                                                                        
    o  UI Personalizations                                              
                                                                        
    o  Field labels in text repository                                  
                                                                        
    o  Changes in Design Layer (design objects and assignments)         
                                                                        
Keep in mind to remove this user parameter once you are done with the   
analysis!!!!                                                              

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Terrance Runde
    Using the WCF_IGNORE_ENHANCEMT parameter to temporarily deactivate all customer WebUI enhancements works great!

    That said, is there are WCF_IGNORE_ENHANCEMT parameter value that deactivates ‘Enhancement Sets’ only — leaving customer UI Configurations, UI Personalizations, Field labels in text repository, and changes in Design Layer in place?

    Terry Runde
    WW Grainger, Inc.

    (0) 
    1. Belen Ramirez Post author
      Hi Terry,
      no, when introducing this parameter UI Configurations, UI Personalizations, Field labels in text repository, and changes in Design Layer are disable.
      For instance, if you want to “personalize” a view, with this parameter the view is set as the standard. In this case a solution to check the standard behaviour with your personalized view could be de-activate the enhancement set, set the user parameter to the initial value and personalize the view.    
      In this case the application should behave like standard.       
      If you wonder how to de-activate the enhancement set, take into account that the actual active enhancement set is determined by method            
      GET_ACTIVE_ENHANCEMENT_SET of BAdI COMPONENT_LOADING under Enhancement
      Spot COMPONENT_HANDLING. In the default implementation the active    
      enhancement set is taken from maintenance view BSPWDV_EHSET_ASG, where it is associated to a client.So either you introcuce your own BAdI implementation or you change the assignments in BSPWDV_EHSET_ASG.       

      Kind Regards,

      Belén                             

                                                                       

      (0) 

Leave a Reply