Newsletter April 2010

Performance optimization in the structural authorization check

After initial loading of a transaction concerned the structural authorization check stores the number of admissible objects for the duration of the user’s session in SAP memory. In order to optimize access time, you should pay attention to the evaluation paths used:

If possible, try to do without evaluation paths (e.g. if the entire catalog of qualification may be read anyhow):

Use evaluation paths only with specified target objects (e.g. in order to avoid read-in of redundant US or BP type objects):
 

 
If possible, hierarchies should be run through only once = combine evaluation paths:

In case of larger numbers of admissible objects, the limit of acceptable response time will still soon be exceeded. To solve this problem, use the RHBAUS00-program for loading the admissible objects into the SAP memory, per batch.

This is how it is done:

• RHBAUS00 selects all users to be processed with this procedure. You should only select users with already existing or foreseeable performance difficulties.
• Additionally, these users need to be entered in table T77UU. This is done either manually or supported by report RHBAUS02, which uses the number of the admissible objects as a criterion for entry in T77UU.
• RHBAUS00 needs to be scheduled in the batch. When using RHBAUS00, the SAP memory can only be as up-to-date as the most recent RHBAUS00-run; you should therefore decide how often you need this to happen. If need be, starting RHBAUS00 can be made available to own user decentrally.

In case of a larger number of users with significant numbers of admissible objects, SAP memory is in risk of overflowing. In this case, a customized solution may be implemented in BAdI HRBAS00_STRUAUTH.

To read more about the above-mentioned solution as well as on other details of performance optimization, refer to the book Authorizations in SAP ERP HCM, chapters 3.9 and 3.10. 

Martin Esch
31.03.2010
Projektkultur GmbH  

Back to Newsletter 4/2010