Ansicht
Dokumentation
ABENOPERAND_TYPE - OPERAND TYPE
TXBHW - Original Tax Base Amount in Local Currency SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Operand Type
An operand position is typed by an operand type, which can be complete or generic and can also be dependent on other operand positions, for example in assignments. When a statement is executed, an operand with a suitable data type is expected. If an operand specified at an operand position has a different data type than the operand type, an attempt is usually made to convert the content of the operand to the operand type according to the conversion rules at read positions, and in the other direction at write positions. Here, it should be noted that every conversion incurs increased runtime costs. If no corresponding conversion rule is defined, or the content cannot be converted, a syntax error occurs or an exception is raised. Deviations from this rule, for example that the operand must exactly match the operand type, or the operand is casted to the operand type regardless of its actual type, are described in the documentation of the individual statements.
Operand Positions with Elementary Data Type
At operand positions for elementary data objects, the following must be specified when the statement is executed, depending on the operand type:
Generically typed formal parameters or field symbols can also be specified statically if they are typed more generally than the expected type.
Flat structures with only character-like components of the types c, n, d, or t can also be used in all operand positions where elementary fields are expected. Such structures are handled in the same way as a single data object of type c (implicit casting).
Operand Positions with Structured Data Type
Structures must be specified at operand positions for structures when the statement is executed. Formal parameters or field symbols of the generic types data or any can also be specified statically.
Operand Positions with Tabular Data Type
Internal tables must be specified at operand positions for internal tables both when the statement is executed. There are also operand positions, where internal tables must be statically recognizable. At these positions, generic formal parameters and field symbols can only be specified if they are typed with at least the generic type any table. Only index tables can be specified at operand positions where index access occurs, and generic formal parameters and field symbols must be typed with at least the generic type index table.
Operand Positions with Reference Data Type
Depending on the operand type, either data or object reference variables must be specified at operand positions for reference variables when the statement is executed. Formal parameters or field symbols of the generic types data or any can also be specified statically.
RFUMSV00 - Advance Return for Tax on Sales/Purchases General Material Data
This documentation is copyright by SAP AG.
Length: 4467 Date: 20240427 Time: 021800 sap01-206 ( 88 ms )
