sapdev logo background
sapdev logo sapdev logo
Comments

ABAP MODIFY ITAB Statement syntax, information and example SAP source code



Return to Statement index



MODIFY itab

Short Reference

ABAP Syntax MODIFY { itab_line
| itab_lines }.

What does it do? This statement changes the content of one or more rows itab_line or itab_lines , specified using a table key or a table index.
The following limitations apply when modifying key fields of the primary and secondary table key s:
The administration of unique secondary keys is updated directly after a modification using MODIFY , and produces an unhandleable exception if duplicate entries were to result. The non-unique secondary keys are updated when the secondary table key is next used explicitly (
lazy update ).

System Fields
sy-subrc Meaning
0At least one row was changed.
4No rows were changed, since no suitable row was found during the search using a table key or in the logical expression, or the specified index was greater than the current number of rows for the search using a table index.
The system field sy-tabix is not set.

Latest notes: Apart from using the MODIFY statement, the content of an individual table row can be changed using assignments to field symbols and dereferenced data references that point to the table row.



Runtime Exceptions

Catchable Exceptions
CX_SY_ITAB_DYN_LOOP
Reason for error: Error in a dynamic WHERE condition
Runtime error: DYN_WHERE_PARSE_ERROR

Non-catchable Exceptions

Reason for error: Invalid dynamic specification of a row component
Runtime error: ITAB_ILLEGAL_COMPONENT
Reason for error: Unzul�ssige Schl�sselkomponente in der TRANSPORTING
-Liste.
Runtime error: ITAB_ILLEGAL_TRANSP_COMP
A read-only secondary table key would be overwritten
Runtime error: ITAB_ACTIVE_KEY_VIOLATION
Reason for error: Memory area violated when TABLES parameter accessed
Runtime error: ITAB_STRUC_ACCESS_VIOLATION
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved




MODIFY_DBTAB_OBSOLETE
MODIFY_ITAB_INDEX




comments powered by Disqus