Get Example source ABAP code based on a different SAP table
Functional Operand Positions Functional operand positions are read positions> that expect appropriate data objects> and functional method calls> or method chainings>, as well as constructor expressions> and table expressions> whose return value or result has a suitable data type. The following functional operand positions exist:
Functional operand positions in ABAP Objects
Operand oref> of the statement
SET HANDLER ... FOR oref>>.
Functional operand positions in relational expressions
Operand ref> of the predicate expression
... ref IS $[NOT$] BOUND ...>>
Functional operand positions in assignments
Operand struc1> of the statement
MOVE-CORRESPONDING struc1 TO ...>>
Operand val> of the statement
CLEAR ... WITH val>>
Functional Operand Positions in String Processing and Byte String Processing
Character-like or byte-like arguments of the built-in functions
dbmaxlen>>, xstrlen>>
Operand itab> of the statement
CONCATENATE LINES OF itab INTO ...>>
Operand itab> of the statement
FIND ... IN TABLE itab ...>>
Functional operand positions in statements for internal tables
Internal table itab> of the statement
READ TABLE itab ...>>
Work area wa> of the statement
READ TABLE ... FROM wa ...>>
Internal table itab> of the statement
LOOP AT itab ...>>
Internal table jtab> of the statement
INSERT LINES OF jtab INTO ...>>
Work area wa> of the statement
COLLECT wa INTO ...>>
Internal table jtab> of the statement
APPEND LINES OF jtab TO ...>>
Work area wa> of the statement
DELETE TABLE ... FROM wa ...>>
Functional operand positions in statements for time stamps
Operand tz> of the statement
CONVERT UTCLONG time_stamp TIME ZONE tz INTO...>>
Operands dat>, tim>, dst>, and tz> of the statement
CONVERT DATE dat TIME tim DAYLIGHT SAVING TIME dst INTO UTCLONG ... TIME ZONE tz>>
Operands time_stamp> and tz> of the statement
CONVERT TIME STAMP time_stamp TIME ZONE tz INTO ...>>
Operands dat>, tim>, dst>, and tz> of the statement
CONVERT DATE dat TIME tim DAYLIGHT SAVING TIME dst INTO TIME STAMP ... TIME ZONE tz>>
Functional operand positions in message processing
Operand oref> of the statement
MESSAGE oref> ...>
Operands dobj1> to dobj4> of the statement
MESSAGE ...WITH dobj1 ... dobj4>>
Functional operand positions in statements for checkpoints
Operands val1 val2> of the statement
ASSERT ... FIELDS val1 val2 ...>>
Operands val1 val2 ...> of the statement
LOG-POINT ... FIELDS val1 val2 ...>>
Latest notes: NON_V5_HINTS
In addition to the standard functional operand positions, there are three extended functional operand positions> that can be used to specify certain built-in functions. These operand positions are obsolete and should not be used.
Special functional operand positions are all places in which a relational expression> can be specified. Here, a single functional method call> can be specified as a predicative method call>. Other expressions with the exception of predicate functions> or single data objects, again with the exception of an obsolete short form>, cannot be specified as predicates> of a relational expression.
In the formatting options> of embedded expressions in string templates, the specification of (dobj)> and expr> for fixed values represents a combination of functional operand positions. ABAP_HINT_END
ABAP_EXAMPLE_VX5 Calls a functional method cl_abap_tstmp=>normalize> in a functional operand position. ABEXA 01042 ABAP_EXAMPLE_END