LISTDS_TOO_SHORT SAP ABAP Runtime Error listds too short

LISTDS_TOO_SHORT 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: I - Internal Kernel 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.

LISTDS_TOO_SHORT ABAP Runtime Error

The internal table <runtime parameter> should be adapted to the length of structure LISTDS using ... LIKE LISTDS. 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.

If the length of structure LISTDS is actually wrong (discrepancy between Dictionary length and the length according to header file listds.h), this is reported in Transaction SICK. Unable to load the "list level stack". Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

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.

You attempted to load the "list level stack" into internal table <runtime parameter> with SYSTEM-CALL LOAD LIST PAGE DESCRIPTION ... This internal table is too "narrow" for this, i.e. the length of a table row (<runtime parameter>) is shorter than structure LISTDS (<runtime parameter>). An internal table does not have the expected structure to receive the contents of list level administration in the list processor. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.