[ChaRM] Phase Check "Current_Processor"

Question

As explained in note 1031029
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1031029
I configured Current_Processor check for a status of new TR-Type, but I get an error message
when docment is changed to the status in crmd_order.
Current_Processor is SAP standard check. Why does this happen?
My solution manager is 7.0 and SP16 is installed.
Error Message
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_SOCM_NOT_IMPLEMENTED
Date and Time          2009/03/03 11:57:40
Short dump has not been completely stored (too big)
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught
      anywhere along
     the call hierarchy.
     Since exceptions represent error situations and this error was not
     adequately responded to, the running ABAP program
      'CL_CHM1_URGNT_CORR_INSTANCE===CP' has to be
     terminated.
Error analysis
     An exception occurred which is explained in detail below.
     The exception, which is assigned to class 'CX_SOCM_NOT_IMPLEMENTED', was not
      caught and
     therefore caused a runtime error.
     The reason for the exception is:
     An exception occurred

Answer 1

Disclaimer
The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.
Liability Disclaimer
In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.
Posting
If you mean by "upgrade" replace the switch's CPU, that's not done.  Generally the whole switch would be upgraded (or on a chassis switch, perhaps a supervisor card).
If's very unusual to see a L2 or L3 switch with a very high CPU except when there's some "issue".  The reason being, L2 and L3 switch off-load almost all data plane forwarding to dedicated ASICs, the CPU normally only deals with control plane needs.
On the 3560/3750 series, if TCAM resources are exceeded, some ASIC processing is then done by the CPU, which can overtax the latter.
What you might first do is search the main Cisco web site for troubleshooting high CPU utilization on the 3560/3750 series switches.