HR Ad Hoc Query/InfoSet Query - New Functions for Ad Hoc Reporting
For this release, HR Ad Hoc Query has been enhanced and integrated with SAP Query. This new tool is called InfoSet Query.
As of this release, the term Ad Hoc Query is only used in Human Resources Management (HR) if InfoSet Query is started from an HR information system in the SAP Easy Access Menu using an HR InfoSet. When Ad Hoc Query is started, default values are written to the query area and user group parameters. You can only perform ad hoc reporting. If you require further information, see Structural Changes in HR Information Systems .
As of this release, SAP Query/InfoSet Query is the general SAP reporting tool that can be used in all R/3 Systems and in the Business Information Warehouse for OLTP reporting. Repositioning SAP Query and InfoSet Query has necessitated the following terminology changes:
- InfoSet replaces functional area
- Field group replaces functional group
- SAP List Viewer replaces interactive list
If you require detailed information on InfoSet Query, see InfoSet Query / SAP Query / Quick Viewer .
As of this release, ad hoc reporting in HR includes the following new functions:
Reporting on Personnel Planning Data
Up to now, Ad Hoc Query only enabled you to select sets of persons. Data on these persons that was retrieved from Personnel Administration and the infotypes of related Personnel Planning objects could then be output. You could not use Personnel Planning data to make your selection.
As of this release, you can also select objects from Personnel Planning. The prerequisite for doing so is that you use an InfoSet specially created for selecting a specific object type, such as business events or positions.
In previous releases, Personnel Planning data could be output for selected sets of persons, but could not be used to make selections. As of this release, this restriction no longer applies. The infotypes of related objects can now be used to select and output data in reports for persons and Personnel Planning objects.
Deactivating Object Selection
You can deactivate object selection (person selection, for example) and work in "basis mode". The advantage is that you can use all basis mode functions (for example, you can select according to texts). Note, however, that you no longer benefit from the performance advantages of object selection.
Drag & Drop
Up to now, you could only select selection and output fields by flagging checkboxes on the InfoSet display screen.
As of this release, you can also use Drag & Drop to select fields. You simply drag one or more selected fields to the required area. They then serve as selection and/or output fields.
Displaying the Last Queries Used
Up to now, you could only load queries using a dialog box accessed by choosing Query -> Open.
This method of loading queries can still be used in this release. The Query menu, however, now includes the last five queries used. A simple mouse click enables you to load them.
Processing Fields With Text
Up to now, you could select entries in separate columns for fields with text to determine whether the value and/or its text was output. You could not make selections according to texts.
In this release, you can also make selections according to texts provided that object selection has been deactivated. To enable you to select fields this way using previous system technology, the InfoSet display screen would have required four columns of checkboxes. Instead, new system technology enables you to select selection and output fields on a user-friendly InfoSet display screen:
- Each InfoSet field is flagged with an icon that indicates whether it is a simple field, or a field with text.
- When you define selection or output on the basis of fields with text, you can use the value of the field, the text on the value, or both. To determine the standard setting (value or text), use the Settings function. This standard setting is used if you select selection and output fields using Drag & Drop or checkboxes. To make a selection using a method other than the method determined in the standard setting, select the field, click the right mouse button to display the context menu, and choose whether to use the value, text, or both.
Outputting Data on the InfoSet Query Screen
Up to now, a preview of output (including example data) was displayed on the Ad Hoc Query screen once output fields had been selected. After the query had been executed, the output list was always displayed on a full screen.
As of this release, the system still displays a preview of output. However, the Update function enables you to start data output on the InfoSet Query screen. The example data is then replaced by real data. The Output function enables you to start output to a full screen, as in previous releases.
Displaying Field Characteristics
The InfoSet Query screen enables you to show an additional screen area containing technical information on a field. If you want to show the screen area for a field or display technical information on a different field, access the context menu for the field in question and choose Display field information.
Up to now, Ad Hoc Query was always started using the standard settings (for example, the basic list was always used as the type of output list).
As of this release, your settings are saved and then reloaded the next time InfoSet Query is started. For example, if you create a statistic, exit InfoSet Query (or log off the system), and then re-access InfoSet Query later, statistics is used again as the type of output list.
Settings for Output/Exports to Crystal Reports
Up to now, output settings and export options for Crystal Reports were accessed by calling the Edit menu and choosing Define output and Special output options.
As of this release, you can choose Edit -> Settings to access a dialog box with various tab pages, and then enter all of the settings you require in a single dialog box.
New Maintenance for HR InfoSets
Up to now, texts on particular field values were presented as additional fields which had to be selected explicitly when a functional area was created.
As of this release, texts are determined automatically. That is, if you select a value field for an InfoSet, its text is automatically selected too.
Furthermore, InfoSet maintenance has been redesigned:
- Infotypes are selected for an InfoSet using checkboxes in a tree control.
- If an InfoSet is created using HR master data (logical database PNP), the HR infotypes are grouped in accordance with the current user group. If a different user group is selected, its grouping applies. The additional infotypes of related objects group includes the infotypes from Personnel Planning. They can also be selected using checkboxes.
- The order of field groups in an InfoSet and the order of fields in a field group can be changed as required.
- The selection of infotypes in an InfoSet can be changed as required later. Up to now, infotypes could only be added. As of this release, it is also possible to remove infotypes later (provided that none of the fields is used in a query).
Up to now, logs were not created when queries were executed using Ad Hoc Query. InfoSet Query allows you to activate a log creation function that records the following information each time a query is executed:
- Query area
- InfoSet used
- Selection fields including selection values and selection options
- Output fields
Furthermore, the AQ_QUERY_PROT business add-in enables you to use your own log function. If you require further information on how to use your own log function, access the IMG for Basis and choose SAP Query -> Logs -> BADI: Define Your Own Logs.
Effects on Existing Data
The new text field technology does not affect your old InfoSets, which you can continue to use without problems occurring. When an InfoSet is loaded into InfoSet Query, a conversion report is started to convert text field processing to the new technology. Once the InfoSet has been loaded, you can use it just as you would use new InfoSets created in this release.
To improve performance, you are advised to regenerate existing InfoSets just once if you want to use them in InfoSet Query. This ensures that the conversion is permanent, which means the InfoSet is not converted each time it is loaded.