Strict Mode in Release 7.50Other versions:
Conditions for the Strict Mode
The strict mode of the syntax check in Release 7.50 applies to all ABAP SQL statements that use one of the following attributes introduced in Release 7.50:
- Access to a global temporary table (GTT).
- Use of
- Use of host expressions
- In a cast expression, other SQL expressions are used as operands or FLTP is not the only data type that can be specified as the target type.
- Use of the numeric function
ROUNDor the string functions
RIGHT, RTRIM, and
- In an
- of any join, an SQL expression is used on the left side,
- of an outer join, the expression
IS [NOT] NULLis used.
- Comparison of columns or expressions
of the types DF16_DEC or DF34_DEC with other numeric types (except with itself) or comparison of columns
of expressions of the type SSTRING with other types (except with itself) in a
- When specified, columns on the right side of an interval condition
- CDS entities used together with database tables or classic views in a
- Implicit pass of a value to an input parameter of a
CDS entity, annotated with
the annotation @Environment.systemField,
Rules for the Strict Mode
The strict mode in Release 7.50 covers all rules of the strict mode in Release 7.40, SP08, plus the following rules:
INTOclause must be specified as the last clause of a
SELECTstatement and the optional additions of the
SELECTstatement must be specified after the
- If an
OPEN CURSORstatement is checked in accordance with the rules of the strict mode from Release 7.50, all host variables must be prefixed with the escape character
@in the statements FETCH and
CLOSE CURSORthat access the open cursor.
- A column can occur only once in a single update
expression after the addition
SET of the statement
- In a
SELECTstatement, it is not possible to access to a CDS database view as an obsolete data source.
If used in the statements
the escape character
@ is ignored by the checks made on the associated statement