More and more companies are beginning to use InfoSet Query for day-to-day operational HR reporting. HR analysts in organizations are asked to create, execute, and format numerous reports including cross-functional reporting within HR — for example, a single report that combines Personnel Administration (PA), and Organizational Management (OM) data. Businesses might need this kind of information to report on US job attributes (e.g., Equal Employment Opportunity [EEO] category and exempt and non-exempt jobs along with employee master data).

This type of reporting on PA and OM data remains a concern for most users. By creating an InfoSet with PA and OM data and reporting on this using InfoSet Query, users can eliminate hours of manual intervention and the cost of developing custom ABAP reports. You can use InfoSet Query with all versions of R/3 and SAP ERP Central Component (ECC).

The SAP HR system includes several hundred thousand fields in logical databases and tables. As a result, it is impractical to offer all fields for selection when creating queries. To reduce the number of fields and structure them in a clear way, users create InfoSets. These InfoSets specify the fields that users can report in a query. This is why you create InfoSets prior to queries.

Detailed Instructions

The following steps outline the ways to create an InfoSet to enable reporting across PA and OM data in SAP HR.

Step 1. Create an InfoSet using the PCH database. Go to transaction SQ02. In this step, you’ll use the PCH (Personnel Planning) database as the logical data source. Enter an InfoSet name (e.g., ZPA_OM_DATA) and click on the Create button (Figure 1). In Figure 2, enter a description in the Name field (e.g., PA & OM Data). Click on the Logical database button and enter PCH. Click on the enter icon.

Figure 1

Assign logical database PCH and name your InfoSet

Figure 2

Describe your InfoSet

Step 2. Determine the PA object type. When you use the PCH database to create an InfoSet, you need first to select the object type. This object type might be an org unit, position, or job. In Figure 3, I selected Job (C) as the object type. C is the object code for Job.

Figure 3

Select Job (C) as your object type

Once you have selected your object type (e.g., Job (C)), the relevant infotypes are available for reporting automatically based on the database selected (PCH in this case). The preference for selecting one object over the other depends on the type of query the user wants to create. For the business case I introduced earlier, I chose job first because the users want to report on the US job attributes.

Step 3. Select the infotypes to report on. When users select Job as the primary object, all the infotypes associated with job are available to report on (as in Figure 4). Based on the business scenario, users would select infotypes 1000 (for job title, job code), 1001 (for relationships with other objects like position and organizational unit), and 1610 for US job attributes like EEO category, exempt and non-exempt jobs). Scroll down in the screen in Figure 4 to reach the part of the screen shown in Figure 5.

Figure 4

Infotype selection for the InfoSet (top of screen)

Step 4. Select the PA infotypes to report on. Select the PA infotypes based on the PA object type you selected. As you see in Figure 5, the data associated to the Person object displays the employee master data. Under the Infotypes of related objects>Person folder, I’ve selected two relationships: A017 (Is carried out by) and A069 (Is being edited). These are some sample relationships that you can choose for this step; choose your own based on your requirements. Now, you’ve connected the dots so that you can report on both person and job in the same report.

At this point, you have created an InfoSet with the appropriate objects. Based on the business example above, you have created an InfoSet to capture job reporting along with employee master data.

Step 5. Save and generate the InfoSet. Click on the save icon and then click on the generate icon (Figure 6).

Figure 6

Save and generate the InfoSet

Step 6. Attach the InfoSet to the appropriate user group. Go to transaction code SQ03. As Figure 7 shows, click on the Assign users and InfoSets button. This step allows you to attach the users associated with a user group to the InfoSet. You can start using this InfoSet to report on PA and OM data.

Rishi Agarwal

Rishi Agarwal leads the SAP HCM reporting and analytics team at IBM. He has significant international (US, Australia, and Europe) HR and BW implementation experience. Rishi’s experience includes 10 years of SAP HR experience, including five years of BW for HR experience at Global Fortune 100 companies.

You may contact the author at rishi.agarwal@us.ibm.com.

If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.