Chapter 1

The variant can be called and it automatically feeds on the data stored using the
variant. From the standard report, we can call the variant by clicking on Get Variant
(or pressing Shift + F5) and choosing the variant name. We can do this if we want
to get the Test variant for example. We saved this variant in the previous step. The
demonstration is shown in the following screen:

The ad hoc query is a useful tool to pull any data from tables and is accessed via the
S_PH0_48000512 T-code. The standard /SAPQUERY/HR_APP infoset can be used to set
the selection and output. If the standard report doesn't meet the requirement of the
client, this ad hoc query function can be utilized.

From the different elds available, Selection and Output need to be agged, and
the preview of the output can also be viewed at the bottom of the screen. This is
demonstrated in the following screenshot. Finally, click on the Save button to access
the query when required.

[ 17 ]
End User Transactions

The name and title of the query need to be entered when saving. Click on Query,
select Open (or press F6), and then select the query name to execute the saved query,
as shown in the following screenshot. There is also a date and time stamp when the
query is saved.

As seen in the following screenshot, the selection and the output saved in the query
gets displayed automatically when we open the query.

We can display the output by clicking on the Output button or by pressing the
F8 key.

Transaction SERP and SARP can be used to display and maintain

the standard report tree. HR00 needs to selected, then click on
Display (F5) to start the report.

[ 18 ]
 Chapter 1

Organizational Management
The OM reports can be accessed by navigating to SAP Easy Access | Human
Resources | Organizational Management | Infosystem | Organization Unit. The
backbone of OM is the SPOCK object types, and there are plenty of standard reports
to display them individually. There are many standard reports provided by SAP to
display the object types and their description. The S_AHR_61016491 function is used
to display the organizational units with their start and end dates, along with their
object IDs and description.

The existing positions can be seen via the S_AHR_61016502 T-code. The output is
similar to what is displayed for an organizational unit. All the existing jobs, along
with their descriptions, are accessed via the S_AHR_61016497 T-code.

The structure hierarchy is displayed via the RHSTRU00 report. This report uses the object
ID that is entered as the root of a tree structure, and using the speci ed evaluation path,
it fetches the object and its related object type. The display depth in the report tells us
how far the object and its relationship need to be displayed in the output.

The evaluation path gives instructions to the system to look

for the object types and relationships and is maintained in the
T778A table or via the OOAW T-code.

The graphic interface is also supported by SAP; the structure can be displayed in a
graphical format. The S_AHR_61016530 T-code is used to display the structure in a
graphical form. They can be downloaded on to the system for further analysis.

The reporting infotype is a functionality given to run reports based on infotypes.

Normally, 1000-1999 are OM infotypes, and in this report, we can give the infotype
number and execute the report. The S_AHR_61016532 T-code is used to execute
the report.

The authorization for objects based on a user can be fetched using the Authorized
Objects per User/Pro le report and is accessed via the RE_RHAUTH00 T-code. When
the user ID is entered and executed, the system displays all the authorization objects
to which the user has access.

Relationship is a key concept in OM; it's like A and B, where A is bottom up and
B is top down. We can nd the missing relationships for object types using this
report. The Display and Create Missing Inverse Relationships report helps
nd the missing relationships between object types, and it is accessed via the
RE_RHCHECKV T-code.

The object types and relationships can be exported to different clients using the
Manual Transport Link report, which is accessed via the RE_RHMOVE30 T-code.
[ 19 ]