SAP ITAB KEY SECONDARY RESTRICT
Get Example source ABAP code based on a different SAP table
ARTICLE
Restrictions for Secondary Keys
Internal tables with secondary keys can be used in all
The use of tables with secondary keys causes syntax or runtime errors for the following operand positions:
Internal Statements:
SYNTAX-CHECK FOR PROGRAM ... REPLACING progtab
SYNTAX-CHECK FOR PROGRAM ... TRACE-TABLE itab
SYNTAX-CHECK FOR DYNPRO ... TRACE-TABLE itab
SYNTAX-CHECK FOR DYNPRO h f e m ID id
EXPORT DYNPRO h f e m ID id
GENERATE DYNPRO h f e m ID id
IMPORT DYNPRO h f e m ID id
(Interne Tabellen f (Feldliste), e (Ablauflogik), m (matchcode))
EXPORT NAMETAB h f ID id
IMPORT NAMETAB h f ID id
SYSTEM CALL EXPORT NAMETAB h f ID id
SYSTEM CALL IMPORT NAMETAB h f ID id (Interne Tabelle f (Feldliste))
SYSTEM-CALL LOAD LIST PAGE DESCRIPTION INTO itab
SYSTEM-CALL LOAD LIST DESCRIPTION INTO itab
SYSTEM-CALL LOAD LISTLEVEL-STACK INTO itab
SCAN [AND CHECK] ABAP-SOURCE itab
SCAN ABAP-SOURCE ... STATEMENTS INTO itab (Statement-Tabelle)
SCAN ABAP-SOURCE ... TOKENS INTO itab (Token-Tabelle)
SCAN ABAP-SOURCE ... KEYWORDS FROM itab (Keyword-Tabelle)
SCAN ABAP-SOURCE ... LEVELS INTO itab (Level-Tabelle)
SCAN ABAP-SOURCE ... STRUCTURES INTO itab (Strukturen-Tabelle)
SCAN ABAP-SOURCE ... ENHANCEMENTS INTO itab (Erweiterungs-Tabelle)
SCAN ABAP-SOURCE ... IMPLEMENTATIONS FROM itab
SCAN ABAP-SOURCE ... REPLACING itab (Ersetzungs-Tabelle)