SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → Obsolete Language Elements → Obsolete Syntax → Obsolete Operand Positions →Extended Functional Operand Positions
Extended functional operand positions are functional operand positions in which certain predefined functions can be specified alongside data objects, functional method calls, constructor expressions, and table expressions, if a single data object is specified as their argument. The following extended functional operand positions exist:
The predefined functions that can be specified for WHEN and MOVE are:
Note
Extended functional operand positions exist for historical reasons and they have been replaced by operand positions for functions and expressions. In all appropriate places, operand positions in which functional methods or predefined functions could previously also be specified, were replaced by a suitable operand position. In the remaining statements, WHEN and MOVE, this did not take placed, because:
The extended functional operand position should not be used in the case of WHEN. The more general assignment operator = should be used instead of MOVE.
Bad example
Specifies the predefined function lines as the source of the obsolete statement MOVE.
DATA itab TYPE TABLE OF i WITH EMPTY KEY.
DATA lines TYPE i.
...
MOVE lines( itab ) TO lines.
Good example
Uses the general assignment operator =, which enables inline declarations on the left side.
DATA itab TYPE TABLE OF i WITH EMPTY KEY.
...
DATA(lines) = lines( itab ).