OBJECTS_GLCLASS_NO_LOAD_OK 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.
Please see internal error 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.
An attempt was made to load global class <runtime parameter> in the wrong context.
Loading global contexts is only possible at certain times (top of
abextri) and should be triggered by a special CCB or another top-level
OO language element.
Internal error! Global class loaded in the wrong context.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
OBJECTS_GLCLASS_NO_LOAD_OK - objects glclass no load ok OBJECTS_COMP_NOT_SUPPORTED - objects comp not supported OBJECTS_COMPARE_NOT_SUPPORTED - objects compare not supported OBJECTS_BAD_REF_NODATA - objects bad ref nodata OBJECTS_BAD_REF_DATA - objects bad ref data OBJECTS_ACCESSIBLE_IS_FREE - objects accessible is free