Ansicht
Dokumentation

ABENABAP_MANAGED_DB_OBJECTS_OSQL - ABAP MANAGED DB OBJECTS OSQL

ABAP Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Access to ABAP-Managed Database Objects

includes a set of statements for use in ABAP programs. The database is accessed using the interface of the database interface, which transforms the statements into platform-specific SQL.

can be used to access ABAP-managed database objects as follows:

• Reads and writes on database tables and DDIC database views defined in ABAP Dictionary. Writes on DDIC database views are only possible with restrictions.

• 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 statement.

The most important features are as follows:

• is to a great extent platform-independent

• is based on the data types defined in ABAP Dictionary and any enhancements made to them:

• respects the order of fields defined in ABAP Dictionary, since this can differ from the order in the database.

• checks the compatibility of host variables with the associated dictionary types or database types.

• enables conversions to be made between ABAP types and platform-specific data types in accordance with uniform ABAP-specific rules.

• has its own handler for null values.

• 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

• uses the name of a CDS entity to access the entity and respects all relevant attributes. Access to CDS managed DDIC views is obsolete and forbidden in strict mode from Release .

• Implicit client handling is applied in accordance with how client dependency is defined using the relevant 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 associated with the input parameters of a CDS entity in uniform syntax.

• SQL path expressions can be specified for CDS associations.

• When 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 is used to access a CDS view. More specifically, the addition USING CLIENT modifies the session variable client.

• When is used to access a CDS table function, the access is transformed to the associated AMDP table function.

• Database objects specified statically in are recorded in the where-used list in 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, any consequences of modifying the object can be checked.

• enables dynamic tokens to be specified that are evaluated at runtime of an ABAP program.

• DDL statements are not included in the scope of . The respective ABAP-managed database objects cannot be modified in and no other database objects can be created or modified.

• does not support secondary connections or service connections.

• respects the dependency rules defined for a database.

• respects data aging by default.

Note

Some of the semantic attributes defined in ABAP Dictionary or ABAP CDS, such as foreign key relationships or reference fields, are ignored in and are respected only by classic Dynpros, Web Dynpros, and some other frameworks. This applies in particular to the evaluation of framework-specific annotations in ABAP CDS as well.

CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 8285 Date: 20240426 Time: 044446     sap01-206 ( 87 ms )