Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

ABAPSYSTEM-CALL_ITAB - SYSTEM-CALL ITAB

ABAPSYSTEM-CALL_ITAB - SYSTEM-CALL ITAB

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

SYSTEM-CALL - Editing Internal Tables

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!


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 lines of the internal table itab1 are deleted whose line numbers are specified in the internal table itab2

The line number table itab2 must have the line type i and must contain the numbers of the lines pending deletion in ascending order (and non-duplicated). This means itab2 must contain a strict ascending sequence of numbers from 1 to line number(itab2). If not, a runtime error is raised.

If the optional addition NO-CHECK is specified, the caller is responsible for guaranteeing that the line number table itab2 contains only valid line numbers in strict ascending order.

The optional addition USING KEY can be used to determine the table key that deletes the lines 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 line type c with length 72.

At present, the following OPCODEs are supported:

'IT_OCCU'

Passes the actual value of OCCURS used in the table itab1 to the field f.

'IT_HSDIR'

Passes the value 1 (if internal COLLECT hash management exists for table itab1) or 0 (if it no longer exists or never existed) to the field f.

'IT_FSREGCNT'

Number of field symbols registered for the table.

'IT_LENG'

Length of the table line

'IT_FILL'

Fill level of the table

'IT_GETSTOR'

Writes information about the memory allocated to and used by the table itab1 to the log table itab2.

'IT_TYPE_INFO'

Writes information about the type of the internal table itab1 to the log table itab2. The first three lines contain the CRC64 hash values of the line type, the key definition, and the table type itself. The following three lines contain the values for the table category, the number of key fields, and the uniqueness flag.

'IT_REF_COUNT'

Reference counter to the shared part of the table header






General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5069 Date: 20230207 Time: 091604     sap01-206 ( 110 ms )