SYSTEM_GC_BAD_DATREF SAP ABAP Runtime Error system gc bad datref

SYSTEM_GC_BAD_DATREF 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.

SYSTEM_GC_BAD_DATREF ABAP Runtime Error

The invalid content of the reference variable was possibly caused by the memory in the ABAP application program being exceeded. Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.

The reference to a data object is corrupt. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

During garbage collection the runtime system discovered an invalid data reference.

This is probably an error in program <runtime parameter>. The reference variable was probably destroyed by a memory overwrite. A memory overwrite of this kind is normally caused by one of the following programming errors:

1) A dynamic ASSIGN whose offset and/or length specification was too large, resulting in positioning beyond the end of the source field used in the ASSIGN. Next time write access was made to the associated field symbol, data was written beyond the borders of the source field.

2) A DO ... VARYING loop with incorrect step width or too large a number of runs can also be positioned beyond the limits of the observed structure and be overwritten.

3) Using the ASSIGN ... CASTING statement caused a memory area to be interpreted with a different type and to be overwritten.

Details of the corrupt reference:
Variable : <runtime parameter>
Value of reference: <runtime parameter>
Shared objects ID: <runtime parameter>
Actual lock ID : <runtime parameter>
Test value : <runtime parameter>
Expected test value : <runtime parameter>
In a valid reference, both check values must be identical. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.