Get Example source ABAP code based on a different SAP table
AB_SQL - Overview AB_SQL defines the subset of ABAP statements that enable direct access to data in the standard database of the current AS ABAP. The AB-SQL statements represent the DML part of SQL in ABAP, which is supported by all database systems. The statements of AB_SQL are converted to database-specific SQL in the AB-SQL interface of the database interface . They are then transferred to the database system and executed there. By default, AB-SQL 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, BEGIN_SECTION VERSION 5 OUT DDIC database views, END_SECTION VERSION 5 OUT or CDS views to avoid accessing the database directly each time. AB_SQL is closely linked with the ABAP Dictionary and ABAP CDS. AB-SQL statements can be used only to access DDIC database tables of the ABAP Dictionary, BEGIN_SECTION VERSION 5 OUT DDIC views, END_SECTION VERSION 5 OUT and non-abstract CDS entities. These are specified directly in AB-SQL statements without specifying a database schema. By default, the AB-SQL interface of the database interface accesses the associated database objects in the ABAP database schema of the standard database. The AB-SQL interface of the database interface respects the fact that the order of the columns of a data source in the database system can differ from the order in the definition of the data source in the ABAP Dictionary. If AB_SQL is used, the order in the ABAP Dictionary applies and the database interface performs a transformation if necessary. BEGIN_SECTION VERSION 5 OUT 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. END_SECTION VERSION 5 OUT Each non-buffered AB-SQL statement has the same meaning as an access to the database. This applies in particular to SELECT statements that end with ENDSELECT. Data to be read and to be modified is transported in packages between the database server and the current ABAP_ASINSTANCE . BEGIN_SECTION VERSION 5 OUT The size of the packages can be configured using profile parameters (for example, the default value for Oracle is 65 KB). END_SECTION VERSION 5 OUT
