DYNP_RESIZE_ADMIN_EXHAUSTED SAP ABAP Runtime Error dynp resize admin exhausted

DYNP_RESIZE_ADMIN_EXHAUSTED 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: Y - Error at Screen Runtime

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.

DYNP_RESIZE_ADMIN_EXHAUSTED ABAP Runtime Error

We recommend redesigning the screen using subscreens. Screen name............... <runtime parameter>
Screen number............. <runtime parameter>

Application server....... "<runtime parameter>-WHOST" Network address.......... "<runtime parameter>"
Operating system........ "<runtime parameter>-OPSYS" Release.................. "<runtime parameter>-OPREL" Hardware type............ "<runtime parameter>-MTYPE"

Database server.......... "<runtime parameter>-DHOST" Database type............ "<runtime parameter>-DBTYP" Database name............ "<runtime parameter>-DBNAM" Database user ID......... "<runtime parameter>-DBOWN"

Character set............ "<runtime parameter>-CTYPE"

SAP kernel............... "<runtime parameter>"
Created on................ "<runtime parameter>-COMPI"
Created at............... "<runtime parameter>"
Database version.......... "<runtime parameter>" The screen contains too many objects whose size is modifiable. Please see dynpro error for more details about the possible cause of this runtime error and how it could be avoided.

Further execution of the program is not possible.

The following error occurred: The administration structure of the screen resize can only handle 200 objects of variable size per dimension. Your screen contains more than 200 objects. Please see dynpro error for more details about the possible cause of this runtime error and how it could be avoided.