Skip to Content
avatar image
Former Member

Automatically Update the User Parameter from Role personalization

Hello all.

Its just nice to be here with all the fellow SAP security stars :). I am the Security consultant working on an implementation here in the UK and have a question on the user parameter.

We are trying to find a solution where when the role is updated with the personalization values (say like approval limit for Purchasing), the same needs to be automatically updated in the user parameter when the user is assigned that role. This would save a lot of time for us in editing the user parameter and changing the default into the actual authorized values.

Any suggestions/past experiences will be much appreciated.

Many Thanks

Raaj

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Sep 24, 2009 at 09:04 AM

    > This would save a lot of time for us in editing the user parameter and changing the default into the actual authorized values.

    Sounds more like a short-cut not to change user-exits which use PIDs... 😊

    Cheers,

    Julius

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks Julius & Bernard. I'm glad I have got a response for my queries. I will go with SPERS_MAINT as suggested by Bernard.

  • Sep 24, 2009 at 09:47 AM

    Hello Raaj,

    the 3 types of personalization (user,role,system) are completely independent of each other. That means, default values maintained for one type (role in your case) are basically not copied to another type (here user).

    The reason for that behaviour is a missing procedure for merging or accumulating default data for the same personalization key. Since it is possible to maintain default values for the same key but for different types the first question is whether data coming from different types should be accumulated or prioritized. If one decides to prioritize which type (user, role or system) should dominate? If one prefers the accumulation what should happen if default data of different types is contradictionary?

    Therefore, the default data for all types is kept separated from each other, i. e. you have to maintain the personalization data in SPERS_MAINT explicitly for the requested users if you want to see them in SU01.

    Since 7.00 (I think), this has been changed by implementation of the new switch ' Take into account with role changes" .

    So the roles Personalistion value is reflected to the assigned users (but i am not sure about the priorisation, if for the user a different value has been maintained already. You should decide, which kind of maintenance you want to use...)

    b.rgds, Bernhard

    Edited by: Bernhard Hochreiter on Sep 24, 2009 11:51 AM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      By the way, we just tested the behaviour at assignment level. We set value "low" to the personalization key concerned in a role and after assigning role to the users, they automatically got the same value in their key though before the assignmend, value was set to "not defined"...