SYSTEM_POINTER_PENDING SAP ABAP Runtime Error system pointer pending

SYSTEM_POINTER_PENDING 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_POINTER_PENDING ABAP Runtime Error

Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Internal number of the entry.......: <runtime parameter>. Local result variable used in a control/automation call Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Local variables cannot be used to add a return value in a call to a control or an automation server.
To improve performance, the system collects calls to front-end components like controls in a queue. It then passes them to the front end in what is known as a flush. These calls are processed asynchronously with the calls in the ABAP code. If local variables are used to add return values (the ID of a selected node in a tree for example) during calls to controls, it could be that the local variable no longer exists when the flush takes place. It will then not be possible to transfer the return value to the variable.
It is highly unlikely that further processing will continue correctly without return values. As a precaution, processing is terminated here.
Check your application for local variables that are used for return values of control/automation calls. The variable used here points to to data object"<runtime parameter>" in area "<runtime parameter>". Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.