SAP OPERANDS SPECIFYING
Get Example source ABAP code based on a different SAP table
Specifying Individual Operands
There are three ways to specify the
ITOC
Static Specification
The name of the operand must be specified directly. If the name of a data object is specified, the specified name is used and not the content of the data object.
ABAP_EXAMPLE_VX5
ABEXA 01737
ABAP_EXAMPLE_END
Dynamic Specification in Parentheses
For some statements that normally expect a static specification, there is a syntactic form that allows the name of a character-like data object to be specified in parentheses at the operand position. At the time of execution, the data object must contain the actual name of the operand.
ABAP_EXAMPLE_VX5
ABEXA 01161
ABAP_EXAMPLE_END
For statements that contain lists of operands or full parts of statements, an internal table with a character-like line type can often be specified in parentheses. The table lines must then contain the tokens or the names of the individual operands.
ABAP_EXAMPLE_VX5
ABEXA 01736
ABAP_EXAMPLE_END
Dynamic Specification
At many operand positions, the system expects character-like data objects that contain the actual names of the individual operands at the time of execution. To enable the static specification of these operands, literals must be used.
Latest notes:
In some rare cases, there may be exceptions to these rules, where operands must be set directly in parentheses or quotation marks as literals, but no data objects can be specified. This is noted in the corresponding syntax descriptions.
NON_V5_HINTS
ABAP_HINT_END
ABAP_EXAMPLE_VX5
ABAP_EXAMPLE_END