Let me first explain you what a Role configuration Key exactly is! Whenever you navigate to a view in the SAP CRM WEBUI, you will probably see the default configuration. In such a case the role key shown will normally be <DEFAULT> if you would take a look at the technical details of an overview page or assignment block as shown below.
Now in many cases you will want to make certain changes to a view, such as:
- Adding certain fields
- Hiding certain fields
- Change a label of a field
- Change the properties of a certain field (e.g. make it output only or a mandatory field).
As soon as you start changing the configuration of a certain view, you should always do this in your custom configuration, using your own defined role configuration key.
Defining a new “configuration key” can be done in Customizing:
SPRO>> Customer Relationship Management >>UI Framework >> Technical Role Definition >> Define Role Configuration Key
A configuration key on its turn is assigned to 1 or more SAP CRM business roles. That is very powerful and I will illustrate it’s use in a concrete example!
Let’s say your company has a dedicated Master Data Team. As such you have setup a Custom SAP CRM Business role that allows people logging on with this particular business role to perform master data cleansing, archive business partners and so on.
As an illustration I will elaborate this example for the view “Employees”. Now, the field “archiving flag”, should be visible for all users, but only maintainable by the Master Data Team.
As you can see this field is not visible yet within the default configuration, so I first will need to add the field.
To establish these requirements, I would need to create:
- 2 business roles:
- 1 for all users
- 1 for the Master Data team
- 2 configuration keys
I first start with the creation of 2 configuration keys:
Next I will create 2 new business roles as a copy of the standard SERVICEPRO business role. This is done in business role Customizing.
SPRO >> Customer relationship Management >>UI Framework >>Business Roles >> Define Business Role
Or via the transaction code CRMC_UI_PROFILE
For the ease of understanding, I once again give these new Business Roles the same name:
OK – so far so good.
The next logical step would be to actually change the relevant View.
In order to find the relevant component/view name I use the F2 button.
This shows me the following details:
So the view that I want to change is called BP_EMPL/EmployeeDetails.
Now that I know these details, I call up the BSP Component workbench, using transaction code BSP_WD_CMPWB.
I enter the relevant component, and press the display button. (The enhancement set is automatically filled , as this has been setup by some other person on my demo system).
I select “Component Structure Browser”, and next take a look at the Views.
By double clicking on the relevant View ‘BP_EMPL/EmployeeDetails the standard configuration will be shown on the right hand side of my screen.
In this case I would like to add the “archiving flag” that normally resides in the “general data”. To check this, I click on the button “Show Available Fields”.
I”ll open the folder “EMPLOYEE” under which I presume this field will be available.
Searching throughout the pages I finally see it.
Now I need to copy the default configuration and for this first example I will copy it for the role configuration key “ZALL_USERS”
I click on the button “Copy configuration”.
In the pop-up I press Yes.
In the above pop-up is where I will actually enter my own “config key”, being ZALL_USERS.
This will create a new “customizing request” as we are doing screen configuration.
Make sure that you are now working in your customer configuration. You can always select it manually using the button “Choose configuration”.
I now repeat the search for the field “Archiving flag” and this time I”ll add it.
Before pressing the “add field” button, I selected the field under which I wanted to add the ‘archiving flag”. I selected the field “Language”. After pressing the add button, I now see that the field “archiving flag” has been added below this field.
I now can SAVE this configuration.
I now quickly want to check if the field is already visible If I logon with the business role ZALL_USERS.
Looking up an employee I now see the field has been added:
Now as I explained, I want this field to be visible for all users, but in this case NOT changeable.
Therefore I need to perform 1 extra step in my screen configuration.
In my screen configuration I now select the field “archiving flag” and next click on the button “Show Field Properties”.
In the field properties I will set a flag for “Display Only”. This will still show my field on the screen, but disables the editing of the field.
I click on the “Apply” button after I set the flag, and next save the changed screen configuration once again.
When I now logon with the business role ZALL_USERS I see this:
The field is still visible, but when I go into Edit mode of this employee, I can not change the value for the field “archiving flag” anymore.
Ok,now we would need to go this same process once again, but this time for the other business role/configuration key, called Z_PRD_TEAM. I am not going to repeat this, as it’s really following the same steps, except the last one, as I DO want the Master Data team to be able to change the value for the field “Archiving flag”.
I hope some of you have learned and understood the usage of the role configuration key.
If it was useful, you are welcome to leave a comment, like the article or use one of the other social buttons such as Google+