SAP NetWeaver AS ABAP Release 750, ©Copyright 2016 SAP AG. All rights reserved.
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
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
- ON conditions without a column from a database table or view specified on the right side as an operand.
- Multiple consecutive joins where a join expression (and not a database table or view) is on the right side of a join expression.
- Fields from the right side specified in LEFT OUTER JOIN or from the left side in RIGHT OUTER JOIN in the WHERE condition.
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 UPDATE,
change expressions specified after SET.
- If an explicit comma-separated list is specified without the addition
DISTINCT in the SELECT
list, all columns of the results set defined here must exist as identically named components in
a structure or table specified after INTO CORRESPONDING FIELDS.
- If the addition FOR ALL ENTRIES
is used, no database fields of the predefined types STRING and RAWSTRING plus LCHR and LRAW can occur in the SELECT list.
Comma-separated lists of operands and the escape character @ can only be
used in programs in which the program attribute fixed point arithmetic is activated.