Ansicht
Dokumentation
ABENDATA_OBJECTS_USAGE - DATA OBJECTS USAGE
General Material Data ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Operand Type
An operand position is typed using an operand type, which can be complete or generic and can also be dependent on other operand positions, for example in statements. When a statement is executed, an operand with a suitable data type is expected. If a data object 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 data object to the operand type according to the conversion rules at write positions, and in the other direction at read positions. 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 data object must exactly match the operand type, or the data object is to be interpreted as an operand type, regardless of its actual type (casting), are described in the individual statements.
Operand Positions for Elementary Data Objects
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 for Structures
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 for Internal Tables
Internal tables must be specified at operand positions for internal tables both when the statement is executed as well as known statically. 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 for Reference Variables
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.
General Material Data rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4387 Date: 20240420 Time: 144548 sap01-206 ( 77 ms )
