Tom's page




Each error message in the CRM system is associated to a degree of details. This degree of details is used to define if an user will be able to see an error message or not. The degree of details associated to an error message can be found in system table CRMC_MESSAGES_S using transaction SE16. You can create your own entries in the customizing table CRMC_MESSAGES. The standard values defined in the system for the degree of details are 1, 3, 6, 8 and 9. The higher the degree is, the more the user is supposed to have technical knowledge about the product. For example 1 is usually used for customers, and 8 for administrators. The parameter CRM_USER_LEVEL maintained for each user in SU3 must be maintained with the adapted value in order to see the expected error messages for each specific user. The message degrees are defined with the constants for GC_MSGLEVEL in include CRM_MESSAGES_CON.


  • BSPWD_USER_LEVEL - For analyses is the value 5 the best starting point
    • 0 = None
    • 1 = Customer
    • 3 = Office-Based Sales Employee
    • 5 = This will generate a tooltip in case you move the mouse pointer over the message text displaying technical data like message class and message number.
    • 6 = Experienced User
    • 8 = Administrator
    • 9 = Only Collect in Trace Mode, display all the message in message area including the technical information in the WEBUI message area itself.
    • X = Testmode is active

Disable Authorization Buffer

For further information please review OSS Note 615670.


If you have adjusted security on a user (removed/added transactions) and want that to reflect in the transaction search you need to do the following steps:

Add an entry to the table SMOFPARSFA
Paramvalue: B

Per user

Then under each user you need to set the parameter id CRM_RF_PERFORMANCE to B. The entry SETTINGS_REPORTING_FRAMEWORK in the table SMOFPARSFA is needed for the user parameter.