is a tool within the SAP Query that you can set as an alternative to component
. This tool for maintaining queries is suitable for both developing queries as well as
The InfoSet query can be used for reporting in all areas of the SAP system, whereby the component
Human Resources (HR) displays a special feature: the InfoSet query contains the function
for reporting the data model in HR You can find further information under
HR in the InfoSet Query
. When the InfoSet query is set in HR for ad-hoc reporting, the name
ad-hoc query is used instead of InfoSet query.
All query information, meaning the selection criteria and output, is available on a single screen. The clear and concise arrangement of screen areas means that even an inexperienced user can quickly get to grips with the process of generating queries. Graphical interface elements and Drag&Drop make the tool easy to use.
The InfoSet query is designed in such a way that it can be called directly from roles with a relevant InfoSet and be used directly by the end-user for reporting within his/her roles. In doing so, it follows that no more SAP Query administration functions are needed for the end-user.
Queries that were created with the InfoSet query can also be edited with other SAP Query tools, for example with the queries component, which offers an alternative possibility for editing when maintaining queries. Conversely, queries that have been generated with other SAP Query tools can be processed with the InfoSet query.
When calling the InfoSet query, a template is assigned first (an InfoSet or an existing query) that suits your needs. You can change the selection fields and selection values used as well as the output fields and output format. These changes are temporary, meaning that all changes are lost when you leave the query (ad-hoc reporting).
The advantage is that several users can use the query as a template at the same time without locking each other out. If you require further information, see Saving Queries .
It is also possible to save changes thereby overwriting the available query or creating a new query (development). The process of creating queries is always the same. An explanation of the differences between using InfoSet Query as an ad-hoc reporting tool or as a development tool can be found in the section Calling the InfoSet Query .
The InfoSet query uses the SAP List Viewer (ALV) as its standard output medium. This means that after executing a query, the output list is displayed in the ALV. There is a whole range of formatting and export options available to you, for example, sorting, filtering, export for word processing and spreadsheet programs. For more information see SAP List Viewer (ALV): Grid Control .
You can log the execution of queries in the InfoSet query if you want to do so. You can find more information under Logging .
Because the InfoSet query uses ALV as its standard output, the following restrictions are valid:
Each query can only output one list.
Queries created by the SAP Query that use a single-level list for output can contain a basic list, up to nine ranked lists, and up to nine statistics for each query.
The output can only be in single-level lists.
This means that you cannot distribute output fields over several lines.
You can neither define nor use local fields.
For this reason you should not process an available query with the InfoSet query if it contains the following objects:
several lists (only the first list is displayed)
a basic list with line groups (the first line of each is displayed)
local fields (local fields are not displayed)
If you do use a query with one of these properties in the InfoSet query, then the parts of the output that are issued in the ALV are shown as described above. The properties that are not displayed are lost if you overwrite the query. These properties are not lost as long as you do not save the query, and you can continue to call and execute the query with all properties using the SAP Query maintenance transaction.
Was this page helpful to you?
Do you have any additional feedback?If you want us to get back to you, please enter your email address.
The following content is not part of SAP product documentation. For more information, see the following disclaimer .