AS ABAP Release 758, ©Copyright 2024 SAP SE. All rights reserved.

ABAP - Keyword Documentation →  ABAP - Programming Language →  Processing External Data →  ABAP Database Access →  ABAP SQL →  ABAP SQL - Overview →  ABAP SQL - Release-Dependent Syntax Check Modes → 

ABAP SQL - Strict Mode in ABAP Release 7.54

• Conditions for the Strict Mode
• Rules for the Strict Mode

Conditions for the Strict Mode  

The strict mode of the syntax check in ABAP release 7.54 applies to all ABAP SQL statements that use one of the following properties introduced in ABAP release 7.54:

• Use of aggregate expressions as operands of SQL expressions
• Definition of CTE associations by specifying JOIN TO ONE|MANY in the addition WITH ASSOCIATIONS when defining common table expressions.
• Use of window expressions.
• Use of the aggregate function STRING_AGG.
• Use of the aggregate function COUNT( sql_exp ) without the addition DISTINCT.
• Use of the hierarchy navigator HIERARCHY_DESCENDANTS_AGGREGATE.
• Use of the additions NEW or INDICATORS in the INTO clause.
• Use of the new data types from the ABAP Dictionary in a CAST expression or after the addition AS of the aggregate function AVG.
• Use of the additions USING [ALL] CLIENTS [IN] in queries or in write statements.
• Use of the WITH additions in the hierarchy navigator HIERARCHY_DESCENDANTS_AGGREGATE or of the hierarchy navigator HIERARCHY_ANCESTORS_AGGREGATE.
• Use of the built-in function UUID.
• Use of the window functions LEAD and LAG.
• Evaluation of value tuples in a relational expression using the operator IN.
• Evaluation of LOBs or geodata types in the relational expression IS [NOT] NULL.

Rules for the Strict Mode  

The strict mode in ABAP release 7.54 covers all rules of the strict mode in ABAP release 7.53 plus the following rules:

• An alias name defined using the addition AS for columns of the result set in a SELECT list or for data sources in the FROM clause must comply with the naming conventions for program-internal names and the name table_line cannot be used. More specifically, an alias name must not contain a minus character (-).
• If strict mode is applied to the statement FETCH, it is also applied to the associated statement OPEN CURSOR. If the rules are broken in OPEN CURSOR, an exception of the class CX_SY_DYNAMIC_OSQL_SEMANTICS is raised.
• The obsolete use of the addition CLIENT SPECIFIED is forbidden in the statement SELECT in queries and subqueries.
• The obsolete use of the addition CLIENT SPECIFIED in write statements is forbidden.