SAP ABAP Data Element R_TTYP_FURTHER_SKEYS (TTYP: Radio Button for 'Further Secondary Keys')

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-DIC-ED (Application Component) Dictionary Maintenance
     ⤷ SEDD (Package) DDIC Editor

Basic Data

Data Element	R_TTYP_FURTHER_SKEYS
Short Description	TTYP: Radio Button for 'Further Secondary Keys'

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	DDBOOL
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	0
Medium	0
Long	0
Heading	0

Documentation

A table type is generic if it has at least one generic property -

• access type is generic (that means index table or not specified)
• if the table key is not fully specified.
  

With the introduction of secondary keys, the concept of complete or generic typing of internal tables in ABAP was augmented.
In ABAP you have the following possibilities for type definition:

• Addition WITH FURTHER SECONDARY KEYS
  
  makes a table (independent of its primary key) generic in terms of its secondary keys.
• Addition WITHOUT FURTHER SECONDARY KEYS
  
  identifies the internal table declared as not generic in terms of its secondary keys.
• If no addition is specified (not specified),
  
  the table is generic in terms of its secondary keys only if it is also generic in terms of its primary key.

Comment:

• If a table is already generic in terms of its primary key, the WITH FURTHER SECONDARY KEYS addition is superfluous but can be specified.
• If a table is not generic in terms of its primary key, the WITHOUT FURTHER SECONDARY KEY addition is superfluous but can be specified.

ABAP Keyword Documentation

table keys

Examples

1. Addition WITH FURTHER SECONDARY KEYS
   
   makes a table (regardless of the primary key) generic regarding the secondary key.
   
   Example:
   types:
   tt1 type sorted table of struc with non-unique key comp1
   with further secondary keys.
   
   field-symbols:
   <fs1> type tt1.
   
   The following (fully typed) table it can, for example, be assigned to the field symbol<fs1>:
   
   data:
   it type sorted table of struc with non-unique key comp1
   with unique hashed key felix components comp2 comp3
   with unique sorted key peter components comp4 comp2.
   
2. The WITHOUT FURTHER SECONDARY KEYS addition
   
   in contrast, indicates that the internal table declared is not generic in relation to the secondary key.
   
   Example:
   types:
   tt2 type index table of struc with non-unique key comp1
   with unique hashed key felix components comp2 comp3
   without further secondary keys.
   
   field-symbols:
   <fs2> type tt2.
   
   The table it cannot be assigned to the field symbol<fs2> now.
3. If no addition is specified (not specified),
   
   the table is generic in relation to its secondary keys when it is generic in relation to its primary key.
   
   Example:
   types:
   tt3 type index table of struc with non-unique key comp1
   with unique hashed key felix components comp2 comp3.
   
   field-symbols:
   <fs3> type tt3.
   
   The table it can be assigned to the field symbol <fs3> in this case because "tt3" is generic in relation to its primary key (because it is declared as an INDEX TABLE) and is therefore also generic in relation to the secondary key.
   
   For this reason, the table it cannot be assigned to the field symbol <fs4>, defined as follows, because tt4 is not generic in relation to the primary key and is therefore also not gerneric in relation to the secondary key.
   
   types:
   tt4 type sorted table of struc with non-unique key comp1
   with unique hashed key felix components comp2 comp3
   
   field-symbols:
   <fs4> type tt4.
   
   

History

Last changed by/on	SAP	20100420
SAP Release Created in	710