Kontakt

Ansicht
Dokumentation

ABENWITH_TABLE_KEY - WITH TABLE KEY

ABENWITH_TABLE_KEY - WITH TABLE KEY

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Effect

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 component specification 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 line found in the internal table, whose values in the column of the table key used correspond with the values in the operands operand1 operand2 ... assigned, is processed. No duplicate or overlapping keys, nor columns that are not components of the table key can be specified.

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 a conversion error occurs here, the exception cannot be handled using CX_SY_CONVERSION_ERROR and the associated runtime error occurs instead. If an arithmetic expression is specified, the calculation type is determined from its operands and the data type of the component. If necessary, the result 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.

Notes

  • The pseudo component table_line can be specified as a component for tables with an unstructured line type and for which the entire table line is defined as a table key.
  • If WITH TABLE KEY is used, it should be noted that the values of incompatible operands operand1, operand2, ... are converted to the data type of the columns before the comparison, and therefore 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 different results.
  • Due to the conversion before the comparison, enumerated objects can be specified as operands for character-like types of type c or string and the corresponding special conversion rules apply, which is not possible in a WHERE condition. Conversions of this type produce a message from the extended syntax check.
  • To avoid unexpected results after a conversion, operand1, operand2, ... must be compatible with the data type of the component.
  • If the line type of the internal table is not known statically, the components of the key can only be specified dynamically and not directly.





RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4331 Date: 20240425 Time: 085156     sap01-206 ( 76 ms )