SAP ITAB KEY SECONDARY RESTRICT

Get Example source ABAP code based on a different SAP table

ABAP_ITAB - 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 where the use of secondary keys does not make sense and is therefore not supported there.
The use of tables with secondary keys causes syntax or runtime errors for the following operand positions:
BEGIN_SECTION VERSION 5 OUT

Internal tables of any table type but without secondary keys are possible for the following:

itab in SEARCH itab for ... (only index tables, no hashed tables).

Actual parameters for a TABLES parameter for RFC.
END_SECTION VERSION 5 OUT

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