*---------------------------------------------------------*
This statement is only for
!!! Internal use in SAP Basis development !!!
Even within SAP Basis, it may only be used in programs within the ABAP+GUI development group.
Its use is subject to various restrictions, not all of which may be listed in the documentation. This documentation is intended for internal SAP use within the Basis development group ABAP+GUI.
Changes and further development, which may be incompatible, may occur at any time, without warning or notice!
*---------------------------------------------------------*
1. SYSTEM-CALL ITAB_DELETE_LIST TABLE itab1 INDEX-LIST itab2
[NO-CHECK].
2. SYSTEM-CALL ITAB_INFO TABLE itab1 OPCODE op
{VALUE f|PROTOCOL itab2}.
SYSTEM-CALL ITAB_DELETE_LIST TABLE itab1 INDEX-LIST itab2
[NO-CHECK].
The system deletes the lines of internal table itab1 whose line numbers are specified in internal itab2.
The table of line numbers itab2 must have the same type as
I and the numbers of the lines that are to be deleted
must be unique and in ascending order. That is, itab2
must follow a strict order from line 1 to line n (where line n is the final line of internal table
itab2). Otherwise, the system returns a runtime error.
If you declare the optional
additionNO-CHECK the calling program is responsible for
guaranteeing that itab2 contains only valid line numbers in ascending order.
SYSTEM-CALL ITAB_INFO TABLE itab1 OPCODE op
{VALUE f|PROTOCOL itab2}.
The system provides information from the header of the internal table itab1.
It determines which information is providedfrom the header using the OPCODE field. According to OPCODEthe results are stored either in the field
f or in the log table itab2.
The field f must be of type
I and itab2 must be a table of the line type C with length 72.
At present, the system supports the following OPCODEs: