SAP NEWS-769-ABAP SQL

Get Example source ABAP code based on a different SAP table

AB_SQL in ABAP Release 7.69
ITOC

ABAP_MODIFICATION_NN Internal Tables as Data Sources

An internal table can be specified as a data source data source of a query. This statement cannot be executed on all database systems, if the data from the internal table needs to be passed to the database.

ABAP_MODIFICATION_NN Relational Expressions

The following is now possible for conditions in expressions:

Size comparisons can now be made between character-like data types and are no longer restricted to numeric data types.

The operator BETWEEN is also no longer restricted to numeric data types and SQL expressions can now be specified on the right side.

The operator LIKE is now also supported.

ABAP_MODIFICATION_NN Path Expressions

The following is now possible for path expressions:

CDS associations can now be used whose association targets are CDS table functions.

Parameters can now be passed after the CDS associations of a path expression in the specified columns of queries. Until now, this was only possible in path expressions in the data source of the FROM clause of a query. This makes it possible to specify paths whose CDS associations have CDS entities with input parameters as data sources.

The cardinality and type of the join expression can now be specified as attributes in the square brackets after the CDS associations of a path expression . Until now, only filter conditions were possible.

Attributes can now be specified after the CDS associations of a path expression in the specified columns of queries. Until now, attributes could only be specified in path expressions in the data source of the FROM clause of a query, and only filter conditions were possible.

ABAP_MODIFICATION_NN Access Control

The new addition WITH PRIVILEGED ACCESS disables CDS access control .

ABAP_MODIFICATION_NN ORDER BY and UP TO, OFFSET in Subquery

In a subquery, it is now possible to use an ORDER BY clause and the additions UP TO and OFFSET can be used after the clause. It is not possible to execute a subquery with an ORDER BY clause on all database systems

ABAP_MODIFICATION_NN Addition NOT for BETWEEN and LIKE

The addition NOT can now specified in front of BETWEEN and LIKE in relation expressions for expressions.

ABAP_MODIFICATION_NN Strict Mode in the Syntax Check

If one the new features listed above is used in an AB-SQL statement, the syntax check is performed in a ABAP_STRICT_769 strict mode / , which handles the statement more strictly than the regular syntax check.

ABAP_MODIFICATION_NN Client Handling

The following (stricter) rules for the additions USING CLIENT and CLIENT SPECIFIED now apply when switching and disabling implicit client handling in reads on CDS entities :

CDS access control does not work for client-independent access. For this reason, the additions USING CLIENT and CLIENT SPECIFIED can only be used in AB_SQL in reads on CDS entities for which access control is disabled using the annotation AccessControl.authorizationCheck.#NOT_ALLOWED or the addition WITH PRIVILEGED ACCESS in the FROM clause of an AB-SQL query.

Path expressions can only be evaluated if implicit client handling is enabled. This cannot be done using CLIENT SPECIFIED in cases where path expressions are used that contain CDS associations whose association target is client-dependent In path expressions in the FROM clause, the association source of the CDS associations cannot be client-dependent either.