SYSTEM-CALL - Editing Internal Tables
Other versions:
7.31 | 7.40 | 7.54
This statement is intended solely for * Internal use within SAP Basis Development *
Even within SAP Basis, it may be used only in programs within the ABAP+GUI dvelopment groups. Its use is subject to various restrictions, some of which may not be described in the documentation . This documentation is intended for internal SAP use within the Basis development group ABAP+GUI. Changes and further developments, which may be incompatible, can occur at any time without prior notice!SAP Basis, it may be used only in programs within the ABAP+GUI dvelopment groups. . This documentation is intended for internal SAP use within the Basis development group ABAP+GUI.
Variants
1. SYSTEM-CALL ITAB_DELETE_LIST TABLE itab1 INDEX-LIST itab2
[NO-CHECK] [USING KEY key].
2. SYSTEM-CALL ITAB_INFO TABLE itab1 OPCODE op
{VALUE f|PROTOCOL itab2}.
Variant 1
SYSTEM-CALL ITAB_DELETE_LIST TABLE itab1 INDEX-LIST itab2
[NO-CHECK] [USING KEY key].
Effect
The rows of the internal table itab1 are deleted whose row numbers are specified in the internal table itab2
The row number table itab2 must have the row type i
and must contain the numbers of the rows pending deletion in ascending order (and non-duplicated). This
means itab2 must contain a strict ascending sequence of numbers from 1 to row number(itab2). If not, a runtime error is triggered.
If the optional addition NO-CHECK is specified, the caller is responsible
for guaranteeing that the row number table itab2 contains only valid row numbers in strict ascending order.
The optional addition USING KEY can be used to determine the table key that deletes the rows specified in the parameter TABLE t.
Variant 2
SYSTEM-CALL ITAB_INFO TABLE itab1 OPCODE op
{VALUE f|PROTOCOL itab2}.
Effect
Provides information from the header of the internal table itab1. The field
OPCODE is used to define which information is taken from the header. Depending on the setting of OPCODE, the results are passed either to the field
f or to the log table itab2.
The field
f must be of type i and itab2 must be a table across the row type c with length 72.
At present, the following OPCODEs are supported:
'IT_OCCU'OCCURS used in the table itab1 to the field f. 'IT_HSDIR'COLLECT hash management exists for table
itab1) or 0 (if it no longer exists or never existed) to the field f. 'IT_FSREGCNT''IT_LENG''IT_FILL''IT_GETSTOR'itab1 to the log table itab2. 'IT_TYPE_INFO'itab1 to the log
table itab2. The first three rows contain the CRC64 hash values of the row
type, the key definition, and the table type itself. The following three rows contain the values for the table category, the number of key fields, and the uniqueness flag.
'IT_REF_COUNT'