difference between sap query and sap ad hoc query

[Former Member]

Hello Experts-

Is there any difference between sap query and sap ad hoc query. If yes, I will appreciate if you can provide some input.

Thanks,

[ak_upadhyay]

Hi,

SAP Query

Purpose

The SAP Query application is used to create reports not already contained in the default. It has been designed for users with little or no knowledge of the SAP programming language ABAP.

SAP Query offers users a broad range of ways to define reports and create different types of reports such as basic lists, statistics, and ranked lists.

Features

The SAP Query comprises five components: Queries, InfoSet Query, InfoSets, User Groups and Translation/Query.

Classic reporting- the creation of lists, statistics and ranked lists- are covered by the InfoSet Query and Queries components. Other components’ range of functions cover the maintenance of InfoSets, the administration of user groups and also the translation of texts created in the SAP Query.

All data required by a user for a report can be read from various tables.

To define a report, you first have to enter individual texts, such as titles, and select the fields and options which determine the report layout. In the WYSIWYG mode, you can edit the lists using Drag & Drop and various toolbars.

AD Hoc Query

Definition

A Web item that enables you to create and change queries in a Web application on an ad-hoc basis.

Use

You can use the Ad-hoc Query Designer Web item in the Web Application Designer to structure Web applications in which you create or change queries. The Web item is as a tool for designing ad-hoc queries in a Web environment.

In particular it enables you to:

· Create queries by assigning characteristics from an InfoProvider to rows, columns, filters, and free characteristics, and including key figures from the InfoProvider in the key figure structure of the query.

· Restrict or filter key figures and characteristics

· Use predefined key figure structures and restricted or calculated key figures in the query

· Set or change query properties and key figure/characteristic properties in the query

· Create or change conditions and exceptions

When compared with the BEx Query Designer, the Ad-hoc Query Designer Web item has the following restrictions when creating or changing queries:

· You cannot integrate variables into the query directly.

However, you can use variables in reusable structures, or restricted or calculate key figures, which are used in the Ad-hoc Query Designer

· The query can contain only one structure. This structure has to be the key figure structure and be in the rows or columns of the query.

- You cannot use key figures or key figure structures in the filter.

- You cannot define exception cells, since this requires two structures.

You cannot create the following objects using the Ad-hoc Query Designer Web item:

- Reusable structures

- Reusable restricted key figures

- Reusable calculated key figures

- Local calculated key figures

You can create local, restricted key figures using the Ad-hoc Query Designer Web item.

You can edit existing queries in the Ad-hoc Query Designer Web item, if the queries adhere to the restrictions laid out above The Ad-hoc Query Designer checks these requirements when loading a query. If the query is too complex, the query can be loaded into the Ad-hoc Query Designer but you cannot change it there. You then receive the appropriate message. You can still check and execute the query.

"Ad Hoc" is a Latin phrase which means "for this purpose" and in today's parlance generally means "on the fly," or "spontaneously."

An ad hoc query is a query that is run at the spur of the moment, and generally is never saved to run again. These queries are run using a SQL statement created by a tool or an administrator. So therefore, such a query is one that might suit a situation which is only there for the moment and later on will become irrelevant.

As queries become more complex, it can be difficult to write them correctly ad-hoc. To help with this, one can instead write the knowledge needed for queries as business rules in English, and then use a system called "Internet Business Logic" to automatically generate and run the SQL queries. One can then get explanations of the results, in English, at the business level.

Check these links....

http://help.sap.com/saphelp_nw04/helpdata/en/1f/03223c5f00612be10000000a11402f/content.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bf2f79-021d-2a10-5082-dadc79aa...

http://www50.sap.com/businessmaps/27FEEF3A12444F89A8524CCACAF4F5BF.htm

http://help.sap.com/saphelp_nw70/helpdata/en/15/00a042b443c56ae10000000a155106/content.htm

Reward points if useful....

Regards

AK