Skip to Content

The concept of Authorization Areas

Authorization areas can protect sub trees of the solution structure. An administrator can assign an authorization area to a structure element. Then only users that have an authorization for authorization object Solution Documentation (SM_SDOC) with this authorization area name in the field Authorization Area (SMUDAREA) for this authorization area are allowed to do activities for this structure element and its children.

Authorization role SAP_SM_SL_ADMIN – copy to customer name space before making changes.

Authorization areas are defined solution specific. An authorization area has a 30 character long technical name and a description.

The default authorization area does not need to be defined. The solution documentation root element and all elements without assignment have the implicit authorization area assignment ‘Default’ by definition. When no authorization areas have been assigned to the elements of a solution yet, every element has authorization area ‘Default’.

The definition of Authorization Areas

You can define an authorization area in transaction SM34, View Vluster SMUD_AUTHG:

Select the solution you want to create the authorization area for:

Create the authorization group you want to assign the authorization area to:

Select the entry with the new authorization group:

Choose the “New Entries” button to add a new entry in the detail screen of the view. Enter an authorization area ID or select it in the value help provided. Select the button “Select Structure Element”:

In the search help you can preselect by element type and by description:

Save.

The usage of Authorization Areas

The authorization group with assigned authorization area can be now used in the authorization object SM_SDOC.

Now, you can modify the authorization object SM_SDOC by assigning the authorization area MOD_CREATE_SALES to the authorization filed SMUDAREA:


The user will only be able to access the sub tree elements defined in the authorization area and authorization groups, in our case DEFAULT (a reduced visibility of the solution content):

Other folders and tree/subtree structures will not be visible to this user. The picture below shows a full visibility of the solution content:

The assignment of a structure element to an authorization area is valid for all branches of a solution in which the assigned elements exists.

The authorization area explicitly assigned to a structure element is valid for the whole subtree rooted by the element excluding all nested subtrees rooted by elements with own authorization area assignments.

Non-structure elements always inherit the authorization area from their structure parents. The authorization area determination is branch specific since the inheritance hierarchy is branch specific: If an element is moved it may inherit a new authorization area from the new parent, so in this case the authorization area of an element may differ in different branches.

To report this post you need to login first.

2 Comments

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

  1. Sylvain CHATEL

    Hi Ewa,

    really helpfull blog (one more 😉 !).

    I tried to set-up Authorization Areas for my soldoc organization, unfortunately the behavior is not exactly what I want.

    my need is; in the same branch I’d like to display (only!) documents from a folder (ex : Planning) and maintain documents in another folder (NEW FOLDER TEST TRS11).

    the result is :

    • folder “NEW FOLDER TEST TRS11” – Auth Area “CVG_TRS11” : change structure, add documents, update current document > OK
    • folder “Planning” – Auth Area “CVG_CORE” : display documents > OK (“edit online” not available) and properties of document and structure are protected (see fig1)
    • subfolder “Planning/WORKBENCH” – Auth Area “CVG_CORE” : display documents properties > OK (error message “Authorization misssing”) (see fig2)
    • subfolder “Planning/WORKBENCH” – Auth Area “CVG_CORE” : display documents > KO; “edit online” available for current documents (see fig2)

    see below setting of SM34 – SMUD_AUTHG; I added line for subfolder “Planning/WORKBENCH”; same result (option “edit online available”)

     

    see below SM_SDOC setting :

     

    fig1

     

    fig2

     

    I don’t know if this behavior is normal… I wish you’ll be able to help me.

    Thank you.

    Regards,

    Sylvain

    (0) 
  2. Andreas Diebold

    Hi Sylvain,

    Ewa is not in the company anymore. Her blog is a bit confusing as she mixes up Authorization Groups and Areas in her screenshots 3 and 4. You need to define an authorization group to protect certain element types as documents and and an authorization area to protect subtrees. Your screenshots do not show the content of group CORE. It seems like it doesn’t contain documents.

    Kind Regards

    Andreas

    (0) 

Leave a Reply