Skip to Content
avatar image
Former Member

Structural Authorization Vs. General Authorization

Hi Experts,

Structural Authorization has been implemented in our current project and it seems like it has affected the system performance. We're currently in TEST phase and most of the Test IDs are granted with top most structural profile which might be one of the reason. Apart from that, troubleshooting gets complicated as SU53 and trace does not give the full picture.

Thus, I'm considering to revert to General Authorization and identifying the pros and cons before propose the next course actions to resolve the performance issue. Restriction by Object ID will no longer effective and we need to look for alternatives. Hope you could share relevant experience and shed some lights in this matter.

Million thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 19, 2011 at 12:26 AM

    If it is possible to fulfil the business requirements without structural authorisations I would do it. The evil truth normally is that you end up needing them some stage anyway; maybe not when project goes live but in the future.

    If structural authorisations are needed and organisation is large it is essential to restrict the profile size to absolut minimum to avoid the performance issues. Top level managers don't need structural profile at all if that returns all objects (ALL profile for users who don't have restrictions). Using exclusion in ECC6 can also help to reduce the size of structural profile if all except one branch should be allowed.

    I also do only the essential with the structurals. If requirement is to limit access to org. structure I only limit objects O, S, P and give full access to other object types without using evaluation paths: start objects and evaluation paths will just unneccessarily explode the size of the profile if there is no requirement to limit qualifications catalog or business event menu. Also using the period parameter and correct evaluation path can reduce the size if historical data is not required to be displayed.

    If above measures leave you only handful of top managers with large profile I would buffer their access. I try make sure that I will never buffer HR professionals; only high-level managers.

    So if your requirement allows you to implement the solution without structurals I would think that option but I wouldn't be surprised if the requirements change when HR gets used to SAP and starts redefine the requirements or want more functionality.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 16, 2011 at 07:13 PM

    Hi

    If many users has the global strucutral profile (contains all objects access) and if they logged into the system more frequently then system performance drastically go down.

    Hence best practices is never assign global profile not to many userids.

    Also try to build Explicit object level strucutural profiles.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 17, 2011 at 08:45 PM

    Are you indexing with RHBAUS00?

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 19, 2011 at 11:33 AM

    Does the indexing (ignoring for now the constraints) resolve the performance issues?

    Add comment
    10|10000 characters needed characters exceeded