|
SAP BI Java SDK | |||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
IBISapqCommandProcessor | Extension of the
Relational Command Processor
to support Select-Options instead of standard WHERE conditions.
|
IBISapqQueryCall | Simplified contents of the Relational Query Model pre-processed into a form that the BI SAP Query Connector can pass to the SAP Web Application Server. |
IBISapqSelectOption | Record of an ABAP/4 SELECT-OPTIONS table. |
IBISapqSortField | The sorting criteria for SAP Query (basically, column name and sorting direction). |
Class Summary | |
IBISapqSelectOption.Enum | Simple typesafe enumerator. |
IBISapqSelectOption.Kind | Typesafe Enumerator for SELECT-OPTIONS Kind. |
IBISapqSelectOption.Option | Typesafe Enumerator for SELECT-OPTIONS Option. |
IBISapqSelectOption.Sign | Typesafe Enumerator for SELECT-OPTIONS Sign. |
Provides interfaces for data structures relevant to SAP Query. This package documentation contains the following sections:
SAP Query is a reporting tool for systems running SAP Web Application Server, and is also accessible via an ABAP BAPI. This package provides interfaces to the data structures used when accessing SAP Query via this BAPI (Functiongroup RSAQ).
SAP Query uses the following metadata objects:
A functional area describes a data source (field list and methods for data access). The access methods are can be SQL statements, logical databases and ABAP reports and are hidden for users of the functional area.
A query uses a functional area to select the fields which are to read from the data source described by functional area. Each query must use exactly one functional area; a combination of functional areas like joins is not possible. Additionally, a query is connected with a user group.
A user group is a container for queries and an authorization mechanism for using SAP Query. User groups are not used in the BAPI and as support for them will be dropped, their use is not recommended.
These objects have been mapped to the relational model used in the SDK in the following manner:
SAP Query | SDK Relational Model | Description |
---|---|---|
SAPQUERY |
Catalog | placeholder catalog |
SAPQUERY |
Schema | placeholder schema |
Functional Area | Table | |
Functional Area Fields | Column |
Usergroups could have been a potential candidate for either catalog or schema, but as their support will be discontinued, this was not chosen.
As the results of generic queries in SAP Query can be far more complex than the mapping to a relational table would allow (for example, several separate results as the result of one query) this was not feasible within the framework of the relational query model of the SDK. Therefore, Functional Area was chosen as the representation of a relational table instead, still allowing full access to the entities offered within SAP Query, with the restriction however that queries need to be generated for a Functional Area via the SDK.
SAP Query does not support queries involving more than one functional area at once (in other words, JOINs are not possible).
As SAP Query uses the runtime of the underlying SAP Web Application Server and provides access not only to relational tables, but also to Logical Databases and Reports via the same BAPI, query selections and restrictions (specified as WHERE conditions in SQL) are limited to a subset of the expressions permissible in the relational model. Where possible, WHERE conditions are translated to their equivalent representation in SAP Query called SELECT-OPTIONS, or else an exception is raised. Details of the subset are can be found in the SELECT-OPTIONS Semantic document as well as in the SAP online help for the SAP Web Application Server (see For Additional Information, below).
SAP Query query execution supported via the SDK consists of the following phases:
|
SAP BI Java SDK | |||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |