ABAP Keyword Documentation → ABAP - Release-Specific Changes → Changes in Releases 7.5x → Changes in Release 7.52
ABAP SQL in Release 7.52
1. Internal tables as data sources
ORDER BY and
OFFSET in subquery
7. Cardinality in
LEFT OUTER JOIN
FOR ALL ENTRIES and strings in the
9. Strict mode in the syntax check
11. Replacement service for ABAP SQL
7.31 | 7.40 | 7.54
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.
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.
BETWEENis also no longer restricted to numeric data types and SQL expressions can now be specified on the right side.
LIKEis now also supported.
The new type conversion functions
HEXTOBIN make it possible to convert byte strings to character strings (and the other way round) in
SQL expressions, which is not possible with a
The following is now possible for path expressions:
Path expressions can now be split over several source code rows at the blanks in the syntax for parameter passes and filter conditions and also before slashes (
- Associations can now be used whose target data sources are CDS table functions.
- Parameters can now be passed after the associations of a path expression. This makes it possible to specify paths whose associations have CDS entities with input parameters as data sources.
- In path expressions, it is now possible to specify the cardinality and type of the join expression as attributes.
Filter conditions for associations can now be specified in path expressions.
The new addition
WITH PRIVILEGED ACCESS switches
CDS access control off.
ORDER BY and UP TO, OFFSET in Subquery
In a subquery, it is now possible
to use an
ORDER BY clause
and the additions
OFFSET can be used after the clause. It is not possible to execute a subquery with an
ORDER BY clause on all database systems
Cardinality in LEFT OUTER JOIN
In a LEFT OUTER
JOIN, an addition
ONE TO MANY can now be specified for the cardinality. This is evaluated as a note for optimization by
SAP HANA databases.
FOR ALL ENTRIES and Strings in the SELECT List
In the previous strict modes of the syntax check,
FOR ALL ENTRIES
SELECT could not be
specified together with columns of the types STRING and RAWSTRING or LCHR and LRAW in the
SELECT list. This restriction has been removed and now the syntax check simply issues a warning.
Strict Mode in the Syntax Check
If one the new features listed above is used in an ABAP SQL statement, the syntax check is performed in a strict mode, which handles the statement more strictly than the regular syntax check.
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 cross-client access. For this reason, the additions
USING CLIENTand CLIENT SPECIFIED can only be used in ABAP SQL in reads on CDS entities for which access control is switched off using the annotation AccessControl.authorizationCheck.#NOT_ALLOWED or the addition
WITH PRIVILEGED ACCESSin the
FROMclause of an ABAP SQL query.
Path expressions can only be evaluated if automatic
client handling is switched on. This cannot be done using
CLIENT SPECIFIEDin cases where path expressions are used that contain associations whose target data source is client-specific In path expressions in the FROM clause, the source data sources of the associations cannot be client-specific either.