Useful reports
When we talk about structural profiles, eventually we will need to make choice between automate the profiles attribution or make it manually.
In the case of Herval Group we chose for automate this process and for this automation it is necessary the use of some reports.
These reports does not have a specific transaction but can be executed through transaction SA38 by informing the name of the specific program.
In this document, we will talk about four different reports and its use in order to understand why and when use them.
RHPROFL0:
This is probably the most useful report when talking about structural profile. By executing the RHPROFL0 report, the system creates automatically the structural profiles for each user (this creation done by using infotype 1017 assigned to org. unit or position);
RHBAUS02/ RHBAUS00:
These two reports have the same function. They are responsible for create an index of the users structural profiles. Imagine some manager who has a huge structure below it. Sometimes to execute reports (like employee list) may take time. Whit those indexes, the structure below were create for each user in the memory before he executes the report and this same report will execute faster;
RHSTRU00:
This last report is good for those who need to be sure about the eval. Path configured. It is a good report to test different evaluation paths to see his results;
All those reports listed above can be executed manually through the Tcode SA38 or can be scheduled by job execution (in our examples listed above doesn’t make sense to execute the report RHSTRU00 by scheduled job).
To schedule a job with those reports is imperative to know what data you should inform as constants and then you must create a variant with those constants, then you must ask your basis to create a job informing: the program, the variant, the frequency (x times a day, daily, weekly, monthly, and so on), and the time of execution.
Note: Before schedule a job, be sure you understand what it does and what constants you have to inform in your variant, otherwise you can overload the database processing.
Previous document: http://scn.sap.com/docs/DOC-71662
Next document: http://scn.sap.com/docs/DOC-71580
