Get Example source ABAP code based on a different SAP table
ABAP_MESH - Mesh Path Expressions
ABAP_SYNTAX ... mesh_path> ...>
What does it do? Specifies a mesh path mesh_path>> as a standalone mesh path expression at an operand position. The result of a mesh path expression is a line from the last path node of the mesh path described by the result> of the mesh path and has the corresponding line type. In the square brackets [ ... ]>> of each mesh association, an additional condition can be specified using col1 = ... col2 = ...>>. If a path node contains multiple lines that fit the description, the first line found is read. A mesh path expression is a special type of table expression> and can be used in the same way as a table expression:
Possible operand positions are all read and write positions listed for table expressions>. In a write position, key fields of primary or secondary table keys of the last path node must not be overwritten.
VALUE>> and REF>> can be used to control how the result is passed as in regular table expressions.
A chaining> with the structure component selector (->) can be used to access a component of the read line. If the follow-on node does not contain any lines that meet the condition in the square brackets [ ... ]>>, the response is the same as in regular table expressions. In other words, the exception CX_SY_ITAB_LINE_NOT_FOUND >> is raised, except when used in the statement ASSIGN>>, in the predicate function line_exists>>, or in the table function line_index>>.
Latest notes: Since the lines of a mesh node cannot have tabular components, a mesh path expression cannot have any chainings> to other table expressions. NON_V5_HINTS ABAP_HINT_END