OBJECTS_L_CLASS_NO_LOAD_OK SAP ABAP Runtime Error objects l class no load ok

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

OBJECTS_L_CLASS_NO_LOAD_OK ABAP Runtime Error

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 activate local class <runtime parameter> in the wrong context. Local classes can only be activated at certain positions (top of abextri). This should be triggered by a special CCB or other top-level OO language element (CREATE OBJECT, CALL METHOD).

The most likely cause of the error is: First access to a class attribute of a local class. At this point, the CLASS_CONSTRUCTOR should run. This is not possible in ejection, IF, parameter entry and so on. Normally, a special CCB (ABOO) is generated that performs the activation beforehand. This CCB obviously has not been generated or has not been processed.

Workaround: Another way of circumventing this error is for the first 'use' of a class use to be by calling a method or CREATE OBJECT rather than by a class attribute. Internal error! A local class has been activated 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.