Instruction manuals

Switching Off Customer Enhancements in SAP CRM for Symptom Analysis

Description
web ui
Published
of 2
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  sapuniversity.eu http://sapuniversity.eu/switching-off-customer-enhancements-in-sap-crm-for-symptom-analysis/ Switching off customer enhancements in SAP CRM for symptom analysis 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 theimplementation 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 dumpswhen testing the application during Unit Testing and User Acceptance Testing. Now -that's quite normal - but whatyou ll be intrested in is to find out if such a problem occurs because of your customer changes or that it might be problem situated in the SAP Standard solution. In the latter case you ll probably should look for relevant OSSnotes, 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 theSAP Standard or not ! Switching off customer enhancements for symptom analysis Relevant OSS note: 1311966 Symptom: 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 thestandard SAP delivery. Solution: The attached correction instruction cannot contain all necessary changes. Therefore a preliminary correction isnot possible and the Support Package is required. Once the respective Support Package is implemented, set theuser 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 DesignLayer (design objects and assignments) ã Table Enhancements (7.0 EhP 1) ã Embedded Rapid Applications (7.0EhP 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 UIconfigurations and personalizations Please make sure to check out SAP OSS note 1718834 Symptom: In order to check if an issue is caused by customer enhancements or by the standard SAP delivery, we always seuser 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 whichmakes 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. Cause: Using parameter WCF_IGNORE_ENHANCEMT also disables all customer UI Configurations and UIPersonalizations. Resolution: Clear enhancement set in debugging mode instead of set parameter WCF_IGNORE_ENHANCEMT to value 'A'.During debugging mode, blank out rv_result in MethodIF_BSP_WD_CMP_LOADING_BADI~GET_ACTIVE_ENHANCEMENT_SET of corresponding activeimplementations of BADI COMPONENT_LOADING. 

09.Nye.pdf

Jul 23, 2017

gender_finance.pdf

Jul 23, 2017
Search
Tags
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks