sapdev logo background
sapdev logo sapdev logo
Comments

SAP WITH TABLE KEY documentation, setup help and example usage



Return to SAP documentation index


INCLUDE
What does it do? Each component of the table key used must be listed either directly as comp_name1 comp_name2 ... or as a parenthesized character-like data object name1 name2 ... , which contains the name of the component when the statement is executed.
name is not case-sensitive. If name only contains blanks, this specified component is ignored when the statement is executed. An operand operand1 operand2 ...
compatible with the data type of the component or convertible to it must be assigned to every component. The first row of the internal table found, whose values in the column of the table key used correspond with the values in the operands operand1 operand2 ... assigned, is processed. Duplicate or overlapping keys cannot be specified, nor can columns be specified that are not components of the table key.
operand1 operand2 ... are general expression positions . If necessary, the content of the operands is converted to the data type of the components before the comparison. If an arithmetic expression is specified, the calculation type is determined from its operands and the data type of the component and the result, if necessary, is converted to the data type of the component.
If the addition COMPONENTS is not specified, the primary table key is used. If the addition COMPONENTS is specified, the table key specified in keyname is used.

Latest notes: The pseudo component table_line can be specified as a component for tables with an unstructured row type, if their whole table entry is defined as a table key.

If WITH TABLE KEY is used, note that the values of incompatible operands operand1 operand2 ... are converted to the data type of the columns before the comparison. This means that the comparison rules do not apply to incompatible data types. If a WHERE condition is used in the statements LOOP , MODIFY , and DELETE , however, the comparison rules do apply, which can produce differing results.

To avoid unexpected results after a conversion, operand1 operand2 ... must be compatible with the data type of the component.

A Customizing include must not be specified as a component if it is empty.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved




WINDOW_GLOSRY
WORK_AREA_GLOSRY




comments powered by Disqus