InfoSet Query (Biblioteca SAP

InfoSet Query

Purpose

The InfoSet Query is a useful tool for maintaining queries within the SAP Query and is suitable for developing queries and for ad-hoc reporting.

InfoSet Query is suitable for reporting in all areas of the SAP R/3 system. A special feature is the Human Resources (HR) component. When InfoSet Query is used in HR for ad-hoc reporting, the name Ad-Hoc Query is used instead of InfoSet Query. In addition, due to the data model in HR, the InfoSet Query contains the Object Selection function with which you should work in order to evaluate HR data. You can find further information under HR in the 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.

Integration

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. This also means that the end-user does not have to carry out any SAP Query administration functions, for example assigning him/herself to a user group.

The queries created by InfoSet Query can also be processed with other SAP Query tools. Conversely, queries that have been generated with other SAP Query tools can be processed with InfoSet Query.

Features

When you call InfoSet Query, you are first provided with a more or less detailed template (an InfoSet or an available query) that you can change or adjust however you like. 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.

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. You can find more information under Logging.

Restrictions

Because InfoSet Query uses ALV as its standard output,

every query can only output one list. Queries created by 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 per query.

output can only be in single-level lists. This means that you cannot distribute output fields over several lines.

You cannot define and use local fields with InfoSet Query either.

For this reason you should not process an available query with 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 InfoSet Query, then the parts of the output are shown as described above. These properties 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.

See also:

Maintaining Queries

Calling up InfoSet Query

HR in InfoSet Query