Exception 'CX_OS_OBJECT_STATE' after COMMIT in Persistent Class

Former Member — Mon, 08 Jul 2013 11:22:58 GMT

Dear Experts!

I was asked to improve the performance of a custom program where the main time consuming was in a standard code.

LOOPs over table OBJECT_INFO in CL_OS_CA_COMMON took a significant part of the runtime (~80%).

We posted a message on the SAP support portal and we learned the problem was due to the use of a persistent class which

are not designed for high volume programs (which is the case). The SAP proposed solution (OSS note 1882133) was to include Commit Works instructions frequently to improve the performance; after this change the program is "dumping".

Do you know why this might be happening? what should I do to avoid it?

Thanks a lot and kind regards,

Frineé

Re: Exception 'CX_OS_OBJECT_STATE' after COMMIT in Persistent Class

Former Member — Wed, 10 Jul 2013 14:59:28 GMT

SAP support identified the problem:

Class CA_POSITION_TRL has overwritten method IF_OS_CA_SERVICE~PREPARE_FOR_TOP_TRANSACTION of

superclass CL_OS_CA_COMMON and has deleted all entries in table special_object_info. For this reason, the object services framework is no longer able to find the object instances.

topic Re: Exception 'CX_OS_OBJECT_STATE' after COMMIT in Persistent Class in Application Development and Automation Discussions

Exception 'CX_OS_OBJECT_STATE' after COMMIT in Persistent Class

Re: Exception 'CX_OS_OBJECT_STATE' after COMMIT in Persistent Class