ABAP Keyword Documentation →  ABAP - Reference →  Processing External Data →  ABAP Database Accesses →  Open SQL →  Open SQL - Overview →  Open SQL - Release-Dependent Syntax Check Modes 

Strict Mode in Release 7.40, SP05

• Conditions for the Strict Mode

• Rules for the Strict Mode

Other versions: 7.31 | 7.40 | 7.54

Conditions for the Strict Mode

The strict mode of the syntax check in Release 7.40, SP05 applies to all Open SQL statements that use one of the following attributes introduced in Release 7.40 SP05:

• Listings of operands as comma-separated lists

• Escape character @ in front of host variables

• SQL expressions

• Addition USING CLIENT

• Joins:

• ON conditions without a column from a database table or view specified on the right side as an operand.

• Explicit parentheses around multiple consecutive joins where a join expression (and not a database table or view) is on the right side of a join expression.

• Use of RIGHT OUTER JOIN

• Fields from the right side specified in LEFT OUTER JOIN or from the left side in RIGHT OUTER JOIN in the WHERE condition.

• Access to CDS views using SELECT.

Rules for the Strict Mode

The strict mode of the syntax in Release 7.40, SP05 checks whether the following additional rules are followed:

• Any errors that would normally be displayed as syntax warnings are reported as syntax errors.

• All lists of operands must be comma-separated lists. This affects the following:

• In the statement SELECT, columns, aggregate expressions, or SQL expressions specified in the SELECT list and columns specified after GROUP BY and ORDER BY.

• In the statement UPDATE, change expressions specified after SET.

• Host variables must be prefixed with the escape character @.

Comma-separated lists of operands and the escape character @ can only be used in Unicode programs in which the program attribute fixed point arithmetic is activated.