CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

In this blog, I try to explain how to find the required values of an authorization object in SAP CRM. In my previous blog  * Full Authorization! Pitfalls., I tried to explain about the ease of using of "*" and the pitfalls to it. Here I will give some inputs that will enable us to figure out the various options which we can choose from and decide which values can be added to an authorization object.

There are two parts to an CRM authorization - UIU and non UIU authorizations. Here I will illustrate the mistakes done and what could have been the ideal way to do it.


Example 1 - UIU component objects. Below is the screen shot of UIU Component objects

Ideally the picture should have been like the one below. But the question is how we know that which value has to be entered as the F4 help doesn’t give you any options in case of UIU :???: . You might figure out the Component name ( which come automatically via upload in the menu using CRMD_UI_ROLE_PREPARE in SE38), but which  inbound plug and Component Window should be used. You might say at this point that Inbound Plug will be create, edit or search or in case of Window name will be Main Window. But many times this might not be the case and we need to figure out what are values in relation to the component.


In case of UIU component  we go to SE16

Add the component name  and execute (alternatively  you can use this table for other use as well, for example using target id, inbound plug to find other parameters).

Here you get the list all combinations which can be used to give UIU authorizations. And add accordingly according to the business requirement.

 

Example 2 – Non UIU component authorization objects


In case of second example we can easily find the various options available via the F4 help.

 

And add the authorization objects accordingly

 

11 Comments