SAP ABAP MANAGED DB OBJECTS ASQL



Get Example source ABAP code based on a different SAP table
  



AB-SQL Access to ABAP-Managed Database Objects
AB_SQL includes a set of AB-SQL statements for use in ABAP programs. The database is accessed using the AB-SQL interface of the database interface, which transforms the AB-SQL statements into platform-dependent SQL.
AB_SQL can be used to access ABAP-managed database objects as follows:
Reads and writes on database tables and DDIC database views defined in the ABAP Dictionary. Writes on DDIC database views are restricted.
Reads on the database objects of CDS views, CDS table functions, and CDS hierarchies. When a CDS table function is accessed, the associated AMDP table function is called internally and its result is provided as the result set of the AB-SQL statement.
The most important AB_SQL features are as follows:
AB_SQL is largely platform-independent
AB_SQL is based on the data types defined in the ABAP Dictionary and their possible enhancements.
AB_SQL respects the order of fields defined in the ABAP Dictionary, since this can differ from the order in the database.
AB_SQL checks the compatibility of host variables with the associated dictionary types or database types.
AB_SQL enables conversions between ABAP types and platform-dependent data types in accordance with uniform ABAP-specific rules.
AB_SQL has its own handler for null values.
AB_SQL supports the following ABAP Dictionary and ABAP CDS functions:
Implicit client handling
Table buffering
Evaluating CDS access control
Enhancement categories of DDIC structures are respected
Logging of database tables
AB_SQL accesses a CDS entity using its name and respects all its relevant properties. Access to ABAP_CDS_MNG_VIEWS is obsolete and forbidden in ABAP_STRICT_762 strict mode from ABAP_RELEASE ABAP_762 / .
Implicit client handling depends on how client dependency is defined using the corresponding annotations in the DDL source code.
The CDS roles mapped to the CDS entity are evaluated.
The key fields defined in the CDS entity are respected.
Actual parameters can be assigned to the input parameters of a CDS entity in uniform syntax.
SQL path expressions can be specified for CDS associations.
When AB_SQL is used to access a CDS hierarchy, the additional hierarchy columns can also be read.
All session variables are set correctly on all platforms when AB_SQL is used to access a CDS view entity or ABAP_CDS_V1_VIEW . More specifically, the addition USING CLIENT modifies the session variable client.
When AB_SQL is used to access a CDS table function, the access is transformed to the call of the associated AMDP table function.
Database objects specified statically in AB_SQL are recorded in the where-used list of the ABAP tools. Each time an ABAP-managed database object is modified it is advisable to record it in the where-used list. In this way the effects of the modification can be controlled.
AB_SQL enables dynamic tokens to be specified that are evaluated at runtime of an ABAP program.
DDL statements are not included in AB_SQL . The respective ABAP-managed database objects cannot be modified in AB_SQL and no other database objects can be created or modified.
AB_SQL supports the use of ABAP-managed secondary connections or service connections.
AB_SQL respects the dependency rules defined for a database.
AB_SQL respects data aging by default.



Latest notes:
Some of the semantic properties defined in the ABAP Dictionary or ABAP CDS, such as foreign key relationships or reference fields, are ignored in AB_SQL and are respected only by classic Dynpros, Web Dynpros, and some other frameworks. The latter applies in particular to the evaluation of framework-specific annotations in ABAP CDS.
ABAP_HINT_END