ABAP Keyword Documentation →  ABAP − Reference →  Processing Internal Data →  Internal Tables →  Internal Tables - Overview →  Table Keys →  Secondary Table Key 

Restrictions for Secondary Keys

Internal tables with secondary keys can be used in all processing statements for internal tables and other statements that work with internal tables. However, there are also operand positions for internal tables for which it does not make sense to use secondary keys. Secondary keys are therefore not supported for those operand positions.

The use of tables with secondary keys causes syntax or runtime errors for the following operand positions:

• An internal table as an actual parameter for a TABLES parameter for RFC can have any table type but no secondary key.

• Only standard tables without secondary keys are possible for the following:

• rspar in SUBMIT WITH rspar and range_tab in SUBMIT WITH sel IN range_tab

• itab in FIND IN TABLE itab and REPLACE IN TABLE itab

• result_tab in SPLIT INTO TABLE result_tab

• column_syntax in the SELECT list, in GROUP BY, and in ORDER BY

• cond_syntax in WHERE

• source_syntax in SELECT

• target_syntax in INSERT, UPDATE, MODIFY, and DELETE

• expr_syntax in UPDATE

• IN, OUT, INOUT parameters in EXEC SQL - EXECUTE

• itab in EXPORT TO INTERNAL TABLE itab and IMPORT FROM INTERNAL TABLE itab

• itab in GENERATE SUBROUTINE POOL itab, READ REPORT INTO itab, INSERT REPORT FROM itab, and SYNTAX-CHECK FOR itab.

• itab in EDITOR-CALL FOR itab

• itab in WRITE TO itab

Other versions: 7.31 | 7.40 | 7.54