ABAPDATA_PRIMARY_KEY - DATA PRIMARY KEY

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

DATA, key

Short Reference

... ${ $[UNIQUE $| NON-UNIQUE$]
      ${ ${KEY $[primary_key $[ALIAS alias_name$] COMPONENTS$] comp1 comp2 ...$}
      $| ${DEFAULT KEY$} $}  $}
  $| ${ EMPTY KEY $} ...

Alternatives:

1. ... $[UNIQUE$|NON-UNIQUE$] ${KEY ...$}$|${DEFAULT KEY$}

2. ... EMPTY KEY

Alternative 1

... $[UNIQUE$|NON-UNIQUE$] ${KEY ...$}$|${DEFAULT KEY$}

Effect

Definition of the primary table key of an internal table by specifying components or defines it as a standard key. The syntax and semantics of the additions are the same as for the statement TYPES for standalone table types, except that the primary key of a bound table type must always be fully specified.

• In standard tables, only the addition NON-UNIQUE KEY can be specified. If uniqueness is not specified, this addition is added implicitly. The addition UNIQUE KEY cannot be specified.

• In sorted tables, one of the additions UNIQUE KEY or NON-UNIQUE KEY must be specified.

• In hashed tables, the addition UNIQUE KEY must be specified.
  
  

If no primary key is specified for DATA using WITH, the addition WITH NON-UNIQUE DEFAULT KEY is added implicitly for standard tables. This gives the table a standard key, which can be empty. In sorted tables and hashed tables, the primary key must be specified explicitly and cannot be empty.

If the name of the primary key primary_key is specified explicitly, the obsolete addition WITH HEADER LINE can no longer be specified, even outside the classes.

Note

The declaration of the primary table key as a standard key can be critical for various reasons. It is best to specify key fields explicitly instead. In particular, it must be ensured that the declaration of the standard key is not added by mistake because the key was not specified explicitly.

Example

Definition of a sorted table with a primary key without an explicit name specification.

Example

Definition of a sorted table with a primary key and an explicit name specification.

Example

Definition of a sorted table with a primary key for which an alias name is defined.

Alternative 2

... EMPTY KEY

Effect

Definition of an empty primary key for an internal table. This variant is possible for standard tables only. The syntax and semantics are the same as for the statement TYPES.

Notes

• The addition EMPTY KEY can provide clarity in all situations in which the definition of a table key is not important.

• In general, it is recommended that the addition EMPTY KEY is used instead of not specifying a key definition, since otherwise the standard key is used, which often produces unexpected results.

Example

Declaration of a table with an empty primary key. Using the SORT statement without specifying a sort criterion would have no effect for this table.

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 6162 Date: 20230328 Time: 171716     sap01-206 ( 110 ms )