Get Example source ABAP code based on a different SAP table
NO • VERSION 5 IN
ABAP_DDIC - Predefined Types The following predefined DDIC data types are delivered with an AS ABAP. They can be used in ABAP Dictionary, ABAP CDS, and ABAP programs. ITOC • INT1 ABAP_DDIC_PREDEF_TYPE • INT2 ABAP_DDIC_PREDEF_TYPE • INT4 ABAP_DDIC_PREDEF_TYPE • D34N ABAP_DDIC_PREDEF_TYPE • D16N ABAP_DDIC_PREDEF_TYPE • DATN ABAP_DDIC_PREDEF_TYPE • TIMN ABAP_DDIC_PREDEF_TYPE • UTCL ABAP_DDIC_PREDEF_TYPE • GEOM_EWKB ABAP_DDIC_PREDEF_TYPE • GGM1 ABAP_DDIC_PREDEF_TYPE
Data Elements for Built-in Dictionary Types The following data elements are available for built-in DDIC types> of the same name with fixed length.
INT1>>
INT2>>
INT4>>
D16N>>
D34N>>
DATN>>
TIMN>>
UTCL>> (for built-in type UTCLONG >)
GEOM_EWKB>> and GGM1>> (for built-in type GEOM_EWKB>) These data elements allow the built-in DDIC types to be referred by their name.
Latest notes:
Note that the respective built-in types cannot be specified directly in an ABAP program. In ABAP CDS however, there is a syntax ABAP.type> to refer to built-in DDIC types.
There is no data element INT8>, since the respective built-in ABAP type has the same name int8> already. NON_V5_HINTS ABAP_HINT_END • ABAP_BOOLEAN ABAP_DDIC_PREDEF_TYPE • abap_bool ABAP_DDIC_PREDEF_TYPE • abap_true ABAP_DDIC_PREDEF_TYPE • abap_false ABAP_DDIC_PREDEF_TYPE
Data Type for Truth Values There is no built-in ABAP type for the truth values true> or false>. Instead, it is common to use a character field of length 1 with the meaning that a non-initial value means true> and an initial value means false>. The following predefined data element can be used to define these fields:
ABAP_BOOLEAN>> of type CHAR> with length 1. The type pool> ABAP>> contains the following constants to be used as truth values.
abap_true> with value X>
abap_false> with initial value
Latest notes:
The type pool ABAP>> also contains a type abap_bool> of type c> and length 1. But in new programs, the data element ABAP_BOOLEAN> should be used instead.
The disadvantage of using type abap_bool> and the associated constants abap_true> and abap_false> of type pool ABAP>> is that the entire type pool must be loaded, even if only a few types and constants are needed.
Type pool ABAP>> also contains a third constant abap_undefined> with value ->. However, this constant should not be used or in exceptional cases only. NON_V5_HINTS ABAP_HINT_END • ABAP_SORTORDER_TAB ABAP_DDIC_PREDEF_TYPE • MATCH_RESULT ABAP_DDIC_PREDEF_TYPE • MATCH_RESULT_TAB ABAP_DDIC_PREDEF_TYPE • REPL_RESULT ABAP_DDIC_PREDEF_TYPE • REPL_RESULT_TAB ABAP_DDIC_PREDEF_TYPE • SUBMATCH_RESULT ABAP_DDIC_PREDEF_TYPE • SUBMATCH_RESULT_TAB ABAP_DDIC_PREDEF_TYPE • abap_parmbind_tab ABAP_DDIC_PREDEF_TYPE • abap_excbind_tab ABAP_DDIC_PREDEF_TYPE • abap_func_parmbind_tab ABAP_DDIC_PREDEF_TYPE • abap_func_excbind_tab ABAP_DDIC_PREDEF_TYPE
Data Types for Operand Positions and Parameter Passing The following types are used for typing specific operand positions of ABAP statements or for special parameter passing.
Types for Operand Positions
Structures MATCH_RESULT>>, SUBMATCH_RESULT>>, REPL_RESULT>> and table types MATCH_RESULT_TAB>>, SUBMATCH_RESULT_TAB>>, REPL_RESULT_TAB>> for addition RESULT>> of statements FIND>> and REPLACE>>.
Table type ABAP_SORTORDER_TAB>> for dynamic specification of the sort order in statement SORT itab>>.
Types for Parameter Passing
abap_parmbind_tab> and abap_excbind_tab> of type pool ABAP>> for dynamic parameter tables> in the CALL METHOD>> statement.
abap_func_parmbind_tab> and abap_func_excbind_tab > of type pool ABAP>> for dynamic parameter tables> in the CALL FUNCTION>> statement.