ITAB_STRUC_ACCESS_VIOLATION is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Access violation in a STRUCTURE typed table parameter.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Table <runtime parameter>-NAME has been specified as an actual parameter of a STRUCTURE
typed TABLES parameter. With this kind of typing, the actual parameter
can be wider (in its corresponding row length) than the formal
parameter.
In tables statements that allow dynamic specification of components, it
is always the actual parameter which is referred to and, since the
memory area is determined by the shorter formal parameter, the actual
parameter might actually be outside this area. This kind of access
would result in memory violations and is therefore not permitted in the
following statements:
(1) "MODIFY itab FROM wa ... TRANSPORTING (name) ..." if a read access
is made to the memory area after work area "wa" using the component in
variable "name".
(2) "READ TABLE itab INTO wa ... TRANSPORTING (name) ..." if the memory
area is overwritten after output area "wa" using the component in
variable "name".
(3) "READ TABLE itab INTO wa ... COMPARING (name) ..." if a read access
is made to the memory area after work area "wa" using the component in
variable "name".
(4) "APPEND wa TO itab SORTED BY (name)" if a comparison access is made
to the memory area after work area "wa" using the component in variable
"name".
The following statements can also result in memory violations:
(5) "READ TABLE itab INTO wa ... COMPARING ALL FIELDS" if work area
"wa" is smaller than the table because a read access would made to the
memory area after work area "wa".
(6) "COLLECT wa INTO itab" if work area "wa" is smaller than the table.
This would result in a memory area of the same width as the table, and
values from the memory area therefore being transferred to the table
after "wa".
Additional Information:
Name of the component that caused the termination if one of the
scenarios (1) - (4) applies: <runtime parameter>
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
ITAB_STRUC_ACCESS_VIOLATION - itab struc access violation ITAB_SORT_ON_SORTED_TABLE - itab sort on sorted table ITAB_SORT_IN_LOOP - itab sort in loop ITAB_NO_SCND_KEYS_ALLOWED - itab no scnd keys allowed ITAB_NON_NUMERIC_COMPONENT - itab non numeric component ITAB_LINE_NOT_FOUND - itab line not found