Ansicht
Dokumentation

ABENOPEN_SQL_OVIEW - OPEN SQL OVIEW

ABENOPEN_SQL_OVIEW - OPEN SQL OVIEW

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

- Overview

defines the subset of ABAP statements that enable direct access to data from the standard database of the current AS ABAP. The statements form the DML part of SQL in ABAP, which is supported by all database systems. The statements of are converted to database-specific SQL in the interface of the database interface. They are then transferred to the database system and executed there. By default, statements use implicit client handling to access only the data of the current client. To improve performance when accessing the database, table buffering can be activated for individual DDIC database tables, DDIC database views, or CDS views to avoid accessing the database directly each time.

is closely associated with ABAP Dictionary and ABAP CDS. statements can be used only to access DDIC database tables of the ABAP Dictionary, dictionary views, and non-abstract CDS entities. These items are specified directly in statements without specifying a database schema. By default, the interface of the database interface accesses the associated database objects in the ABAP database schema of the standard database.

The interface of the database interface respects the fact the order of the columns in the data source in the database system can differ from the order in the definition of the data source in ABAP Dictionary. If is used, the order in ABAP Dictionary applies and the database interface performs a transformation if necessary. The function SQL Trace of the Performance Trace tool (transaction ST05) can be used to analyze the SQL statements actually passed to the database by the database interface.

Each non-buffered statement is synonymous with an access to the database. This applies in particular with SELECT statements that end in ENDSELECT. Data to be read and to be modified is transported in packages between the database server and the current . The size of the packages can be configured using profile parameters (for example, the default value for Oracle is 65 KB).

In , ABAP SQL statements are checked in the most strict syntax check mode that is currently available, This is different to , where the strict modes of the syntax check are coupled to the usage of features introduced in different releases.

Note

If more than approximately 2^32 entries are addressed in a single database access, the behavior of the database is undefined.






Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4951 Date: 20240329 Time: 142440     sap01-206 ( 65 ms )