+
+| Creating internal tables with ... | Details/Code Snippet |
+
+
+| Standard table keys |
+
+
+``` abap
+"Standard table without explicit primary table key specification.
+"Note that STANDARD is not explicitly specified.
+"Implicitly, the standard key is used; all non-numeric table fields
+"make up the primary table key.
+DATA it1 TYPE TABLE OF zdemo_abap_flsch.
+
+"Explicitly specifying STANDARD for a standard table.
+"Explicitly specifying the standard table key. The declaration
+"corresponds to it1.
+DATA it2 TYPE STANDARD TABLE OF zdemo_abap_flsch WITH DEFAULT KEY.
+
+"Hashed table with unique standard table key
+DATA it3 TYPE HASHED TABLE OF zdemo_abap_flsch WITH UNIQUE DEFAULT KEY.
+
+"Sorted table with non-unique standard table key
+DATA it4 TYPE SORTED TABLE OF zdemo_abap_flsch WITH NON-UNIQUE DEFAULT KEY.
+```
+
+ |
+
+
+| Primary table keys |
+
``` abap
-"------------------ Standard table key ------------------
-
-"Standard table without explicit primary table key specification. Note that STANDARD
-"is not explicitly specified.
-"Implicitly, the standard key is used; all non-numeric table fields
-"make up the primary table key.
-DATA it1 TYPE TABLE OF zdemo_abap_fli.
-
-"Explicitly specifying STANDARD for a standard table.
-"Explicitly specifying the standard table key. It is the same as it1.
-DATA it2 TYPE STANDARD TABLE OF zdemo_abap_fli WITH DEFAULT KEY.
-
-"Hashed table with unique standard table key
-DATA it3 TYPE HASHED TABLE OF zdemo_abap_fli WITH UNIQUE DEFAULT KEY.
-
-"Sorted table with non-unique standard table key
-DATA it4 TYPE SORTED TABLE OF zdemo_abap_fli WITH NON-UNIQUE DEFAULT KEY.
-
-"Elementary line type; the whole table line is the standard table key
-DATA it5 TYPE TABLE OF i.
-
-"------------------ Primary table key ------------------
-
"Specifying the primary table key
-"Standard tables: only a non-unique key possible
-"The following two examples are the same. NON-UNIQUE can be ommitted but is implicitly added.
-DATA it6 TYPE TABLE OF zdemo_abap_fli WITH NON-UNIQUE KEY carrid.
-DATA it7 TYPE TABLE OF zdemo_abap_fli WITH KEY carrid.
+"In standard tables, only a non-unique key is possible.
+"The following two examples are the same. NON-UNIQUE can be ommitted but
+"is implicitly added.
+DATA it5 TYPE TABLE OF zdemo_abap_flsch WITH NON-UNIQUE KEY carrid.
+DATA it6 TYPE TABLE OF zdemo_abap_flsch WITH KEY carrid.
"Sorted tables: both UNIQUE and NON-UNIQUE possible
-DATA it8 TYPE SORTED TABLE OF zdemo_abap_fli WITH UNIQUE KEY carrid connid.
-DATA it9 TYPE SORTED TABLE OF zdemo_abap_fli WITH NON-UNIQUE KEY carrid connid cityfrom.
+DATA it7 TYPE SORTED TABLE OF zdemo_abap_flsch WITH UNIQUE KEY carrid connid.
+DATA it8 TYPE SORTED TABLE OF zdemo_abap_flsch WITH NON-UNIQUE KEY carrid connid cityfrom.
"Hashed tables: UNIQUE KEY must be specified
-DATA it10 TYPE HASHED TABLE OF zdemo_abap_fli WITH UNIQUE KEY carrid.
+DATA it9 TYPE HASHED TABLE OF zdemo_abap_flsch WITH UNIQUE KEY carrid.
"Explicitly specifying the predefined name primary_key and listing the components.
-"The example is the same as it6 and it7.
-DATA it11 TYPE TABLE OF zdemo_abap_fli WITH KEY primary_key COMPONENTS carrid.
+"The example is the same as it5 and it6.
+DATA it10 TYPE TABLE OF zdemo_abap_flsch WITH KEY primary_key COMPONENTS carrid.
-"The following example is the same as it9.
-DATA it12 TYPE SORTED TABLE OF zdemo_abap_fli
+"The following example is the same as it8.
+DATA it11 TYPE SORTED TABLE OF zdemo_abap_flsch
WITH NON-UNIQUE KEY primary_key COMPONENTS carrid connid cityfrom.
"Specifying an alias name for a primary table key.
"Only possible for sorted/hashed tables.
-DATA it13 TYPE SORTED TABLE OF zdemo_abap_fli
+DATA it12 TYPE SORTED TABLE OF zdemo_abap_flsch
WITH NON-UNIQUE KEY primary_key
ALIAS p1 COMPONENTS carrid connid cityfrom.
-"Specifying a key that is composed of the entire line using the predefined table_line.
-"In the example, an alias name is defined for a primary table key.
-DATA it14 TYPE HASHED TABLE OF zdemo_abap_fli
+"Specifying a key that is composed of the entire line using the
+"predefined table_line.
+"In the example, an alias name is defined for a primary table key.
+DATA it13 TYPE HASHED TABLE OF zdemo_abap_flsch
WITH UNIQUE KEY primary_key
ALIAS p2 COMPONENTS table_line.
+```
-"------------------ Empty key ------------------
+ |
+
-"Empty keys only possible for standard tables
-DATA it15 TYPE TABLE OF zdemo_abap_fli WITH EMPTY KEY.
+
+| Empty keys |
+
-"Excursion: The inline declaration in a SELECT statement produces a standard table with empty key.
-SELECT * FROM zdemo_abap_fli INTO TABLE @DATA(it16).
-"------------------ Secondary table key ------------------
+``` abap
+"Empty keys are only possible for standard tables
+DATA it14 TYPE TABLE OF zdemo_abap_flsch WITH EMPTY KEY.
-"The following examples demonstrate secondary table keys that are possible for all table categories.
-DATA it17 TYPE TABLE OF zdemo_abap_fli "standard table
+"Empty primary table key, secondary table key specified
+DATA it15 TYPE TABLE OF zdemo_abap_flsch WITH EMPTY KEY
+ WITH UNIQUE SORTED KEY cities COMPONENTS cityfrom cityto.
+
+"Excursion: The inline declaration in a SELECT statement
+"produces a standard table with empty key.
+SELECT * FROM zdemo_abap_flsch INTO TABLE @DATA(it16).
+```
+
+ |
+
+
+| Secondary table keys |
+
+
+
+``` abap
+"The following examples demonstrate secondary table keys that are
+"possible for all table categories.
+DATA it17 TYPE TABLE OF zdemo_abap_flsch "standard table
WITH NON-UNIQUE KEY carrid connid "primary table key
WITH UNIQUE SORTED KEY cities COMPONENTS cityfrom cityto. "secondary table key
-DATA it18 TYPE HASHED TABLE OF zdemo_abap_fli "hashed table
+DATA it18 TYPE HASHED TABLE OF zdemo_abap_flsch "hashed table
WITH UNIQUE KEY carrid connid
WITH NON-UNIQUE SORTED KEY airports COMPONENTS airpfrom airpto.
-DATA it19 TYPE SORTED TABLE OF zdemo_abap_fli "sorted table
+DATA it19 TYPE SORTED TABLE OF zdemo_abap_flsch "sorted table
WITH UNIQUE KEY carrid connid
WITH UNIQUE HASHED KEY countries COMPONENTS countryfr countryto.
-"Multiple secondary keys are possible
-DATA it20 TYPE TABLE OF zdemo_abap_fli
+"Multiple secondary keys are possible
+DATA it20 TYPE TABLE OF zdemo_abap_flsch
WITH NON-UNIQUE KEY primary_key COMPONENTS carrid connid
WITH NON-UNIQUE SORTED KEY cities COMPONENTS cityfrom cityto
WITH UNIQUE HASHED KEY airports COMPONENTS airpfrom airpto.
-"Alias names for secondary table keys (and also for the primary table key in the example)
-DATA it21 TYPE SORTED TABLE OF zdemo_abap_fli
- WITH NON-UNIQUE KEY primary_key ALIAS k1 COMPONENTS carrid connid city
+"Alias names for secondary table keys (and also for the primary
+"table key in the example)
+DATA it21 TYPE SORTED TABLE OF zdemo_abap_flsch
+ WITH NON-UNIQUE KEY primary_key ALIAS k1 COMPONENTS carrid connid
WITH NON-UNIQUE SORTED KEY cities ALIAS s1 COMPONENTS cityfrom cityto
WITH UNIQUE HASHED KEY airports ALIAS s2 COMPONENTS airpfrom airpto.
-"Example for using table keys and alias names using a LOOP AT statement.
+"Excursion: Example of using table keys and alias names using a LOOP AT statement.
"All of the statements below are possible.
-"Note that if the secondary table key is not specified (and if the USING KEY addition is not
+"Note that if the secondary table key is not specified (and if the USING KEY addition is not
"used in the example), the primary table key is respected by default.
-"Further ABAP statements, such as READ or MODIFY, are available in which the key can be
+"Further ABAP statements, such as READ or MODIFY, are available in which the key can be
"explicitly specified to process internal tables.
LOOP AT it21 INTO DATA(wa) USING KEY primary_key.
-"LOOP AT it21 INTO DATA(wa) USING KEY k1.
-"LOOP AT it21 INTO DATA(wa) USING KEY cities.
-"LOOP AT it21 INTO DATA(wa) USING KEY s1.
-"LOOP AT it21 INTO DATA(wa) USING KEY airports.
-"LOOP AT it21 INTO DATA(wa) USING KEY s2.
+ "LOOP AT it21 INTO DATA(wa) USING KEY k1.
+ "LOOP AT it21 INTO DATA(wa) USING KEY cities.
+ "LOOP AT it21 INTO DATA(wa) USING KEY s1.
+ "LOOP AT it21 INTO DATA(wa) USING KEY airports.
+ "LOOP AT it21 INTO DATA(wa) USING KEY s2.
...
ENDLOOP.
-```
+```
-As mentioned, the examples above demonstrate internal tables that are created using the structured type of a database table in the DDIC.
+ |
+
+
+
+
+
+
+
+| Subject | Details/Code Snippet |
+
+
+
+| Elementary line types |
+
+
+
+``` abap
+"The whole table line is the standard table key.
+"The following examples use built-in ABAP types. Besides these types,
+"you can also use locally declared elementary types, globally declared
+"elementary types such as DDIC data elements, CDS simple types, types
+"that are declared in the public visibility section of classes/interfaces,
+"etc.. As shown further down, there are released table types with elementary
+"line types.
+DATA it28 TYPE TABLE OF i.
+DATA it29 TYPE TABLE OF string WITH EMPTY KEY.
+DATA it30 TYPE TABLE OF xstring WITH EMPTY KEY.
+DATA it31 TYPE TABLE OF utclong WITH EMPTY KEY.
+"Elementary type declared in an interface
+DATA it32 TYPE TABLE OF zdemo_abap_get_data_itf=>occ_rate WITH EMPTY KEY.
+"Using a DDIC data element
+DATA it_dtel TYPE TABLE OF timestamp WITH EMPTY KEY.
+```
+
+ |
+
+
+
+| Structured types |
+
+
+
+``` abap
+"Apart from the line type of a database table, these types can also
+"be local structured types (as shown below), local structured types declared
+"in the public visibility section of classes/interfaces, DDIC structures, CDS
+"entities, etc.
+
+"CDS view entity
+DATA it33 TYPE TABLE OF zdemo_abap_carr_ve WITH EMPTY KEY.
+"CDS abstract entity
+DATA it34 TYPE TABLE OF zdemo_abap_abstract_ent WITH EMPTY KEY.
+
+```
+
+ |
+
+
+| Table types |
+
+
+
+``` abap
+"As shown above, the table types can be locally declared.
+DATA it35 TYPE TABLE OF zdemo_abap_get_data_itf=>carr_tab.
+"Global table type declared in an interface
+DATA it36 TYPE zdemo_abap_get_data_itf=>carr_tab.
+
+"The following examples use globally available and released table
+"types with elementary lines types.
+DATA it37 TYPE string_table.
+DATA it38 TYPE string_hashed_table.
+DATA it39 TYPE xstring_table.
+```
+
+ |
+
+
+| Deep internal tables |
+
+
+
+``` abap
+"The previous examples mostly demonstrate flat line types.
+"Deep line types are also possible, that is, the line type
+"can include components such as strings, references, structures,
+"and internal tables.
+TYPES: BEGIN OF ls_deep,
+ key_field TYPE i,
+ char TYPE c LENGTH 10,
+ str TYPE string,
+ dref TYPE REF TO i,
+ struct TYPE zdemo_abap_flsch,
+ str_tab TYPE string_table,
+ tab TYPE TABLE OF zdemo_abap_flsch WITH EMPTY KEY,
+ END OF ls_deep.
+
+DATA it40 TYPE TABLE OF ls_deep WITH EMPTY KEY.
+```
+
+ |
+
+
+| References as line types |
+
+
+
+``` abap
+DATA it_ref TYPE TABLE OF REF TO i.
+```
+
+ |
+
+
+
+
+
+
+