CX_SOCM_NOT_IMPLEMENTED

[ken_halvorsen2]

I'm trying to configure the Maintenance Optimizer on a new installation of Solution Manager 7.0 EhP1 on SQL Server 2005.

When I get to the step to create a new Maintenance Optimizer Transaction (in transaction DSWP), selecting Product Version SAP R/3 Enterprise 47X200 and selecting the systems. When I click on the Continue button, I get an UNCAUGHT_EXCEPTION - CX_SOCM_NOT_IMPLEMENTED short dump.

Although following the instructions from note 1242931, trying to enter CL_CHM1_MAINT_OPT_INSTANCE as the 'Class/Interface' of transaction type SLMO (which does not appear to be in the selections), it gives me the error message that that entry already exists.

I've also tried to use the SM_PREP_MAINTENANCE_OPTIMIZER Program suggested in note 990534. But received an error message SAP MOPZ auto-configuration warnings, analysing the application logs only show that Buffers TABL and TABLP were reset?

Maybe I have missed a step somewhere? Any suggestions?

Ken

[Miguel_Ariño]

Sorry, I replied a little too quickly and saw more info in the thread that rendered my comments useless, and now I can't delete my post

[Former Member]

Hello Ken,

The cause of the dump are some new check conditions, which are inserted by the activation of the BC-Set SOLMAN40_MOPZ_001. This BC-Set is activated with the implementation of the IMG acitivity "Configuration of Extended Maintenance Optimizer Functions". So it seems that you have done this activity.

This is needed for the SLM scenario, but this requires that the SLM is installed and fully configured before this activity can be activated. Otherwise a short dump is the result when changing the status in MOPZ.

Therefore; to solve this issue, you need to delete the check conditions manually from view TSOCM_COND_MAPP:

SLMO SLMO0001 E0002 40 SYSTEM_ASSIGNMENT

SLMO SLMO0001 E0006 10 FREED_FROM_LOCKING

SLMO SLMO0001 E0007 10 MOPZ_LU_WITHDRAWN

SLMO SLMO0001 E0007 20 FREED_FROM_LOCKING

Hope this helps you out!

Thanks,

Mark

[ken_halvorsen2]

Thanks Mark

I deleted the check conditions as you suggested and saved.

But am receiving the same short dump when I click on the Continue button when creating a New Maintenance Optiomizer transaction.

Below is extracts from the Short dump.

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_CHANGE_REQU_INSTANCE==CP' has to be terminated.

Missing Handling of Application Exception

Program RDSMOP_MAIN

Trigger Location of Exception

Program CL_CHM1_CHANGE_REQU_INSTANCE==CP

Include CL_CHM1_CHANGE_REQU_INSTANCE==CM009

Row 612

Module type (METHOD)

Module Name IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION

Source code extract

610 * avoid exception since it is the default in table TSOCM_COND_MAPP

611 WHEN OTHERS.

>>>> RAISE EXCEPTION TYPE cx_socm_not_implemented.

613 ENDCASE.

Is there some where I can look to find more information to determine the cause?

[Former Member]

Hi Ken,

Please do the following, but ensure to know what you are changing to change back if something does not go right.

Please execute the transaction SPRO and go to the following the IMG Activity:

SPRO

SAP Solution Manager Implementation Guide

-> SAP Solution Manager

-> Configuration

-> Scenario-Specific Settings

-> Change Management

-> Change Request Management

-> Extended Configuration

-> Change Transaction

-> Change Transaction Types

-> Assign Implementation to Change Transaction Types

You can see that the 'Class/Interface' of Transaction Type SLMO is set as 'CL_SOCM_CHANGE_REQU_INSTANCE' now. Please change 'CL_SOCM_CHANGE_REQU_INSTANCE' to 'CL_CHM1_MAINT_OPT_INSTANCE'.

See if this helps.

Thanks,

Mark

[ken_halvorsen2]

Thank you again Mark

But I believe I have solved the problem.

I went back to the IMG and activated the BC sets again, as per the sequence in table AGSBCSETFC, group key SOLMAN_CONFIG. I must have either missed 1 (or more) or activated them out of sequence the first time.

Although, I was a little worried as many have warnings saying that there was no data.

I am able to go to the next step now.

Thanks, I appreciate the helpful hints.

Ken

[nanda_kumar21]

Hi Ken,

I configured MOPZ in solman 7.0 with EHP 1 and i am getting the same error.

You mentioned that you activated BC sets in a sequence, can u pls describe the sequence or wer i can find that.

When i go to SPRO>IMG activity>SAP solman implementation guide>SAP solution manager>Basic settings>Basic BC sets for configuration>Activate Maintenance Optimizer, it asks

"This program configures the SAP Maintenance

Optimizer. Continue? "

I clicked yes and i got the result, "SAP MOPZ auto configuration with warnings".

Please guide me through this.

Thanks & regards

Nanda

Edited by: Nanda Kumar on Apr 30, 2010 8:15 AM

[ken_halvorsen2]

Hi Nanda

I got the sequence in table AGSBCSETFC, group key SOLMAN_CONFIG. It's actually on the help stuff of "Activate BC Sets" activity.

Ken

[nanda_kumar21]

Thanks.!

[Former Member]

Hi,

I have done sp upgrade from sp14 to Sp16 on solution manager. After the upgrade, when i execute the solution_manager i get the ABAP dump as follows :

Error in the ABAP Application Program |

The current ABAP program "/TMWFLOW/CL_MO_HTML_REQUEST===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/TMWFLOW/CL_MO_HTML_DELTA_EX==CP " in include

"/TMWFLOW/CL_MO_HTML_DELTA_EX==CM01D " in

line 1:

"Method "SPECIAL_INSTANCE_CHECK" is not declared or inherited in class "

""/TMWFLOW/CL_MO_HTML_DELTA_EX". -"

" "

" "

The include has been created and last changed by:

Created by: "BASIS "

Last changed by: "BASIS "

Error in the ABAP Application Program

The current ABAP program "/TMWFLOW/CL_MO_HTML_REQUEST===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

I went to SPro and changed the SLMO class interface from change request instance to Maintenance req instance. still the same error.

Any one can help me on this.

regards,

Prabhu

[Former Member]

Hi,

I have done sp upgrade from sp14 to Sp16 on solution manager. After the upgrade, when i execute the solution_manager i get the ABAP dump as follows :

Error in the ABAP Application Program |

The current ABAP program "/TMWFLOW/CL_MO_HTML_REQUEST===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/TMWFLOW/CL_MO_HTML_DELTA_EX==CP " in include

"/TMWFLOW/CL_MO_HTML_DELTA_EX==CM01D " in

line 1:

"Method "SPECIAL_INSTANCE_CHECK" is not declared or inherited in class "

""/TMWFLOW/CL_MO_HTML_DELTA_EX". -"

" "

" "

The include has been created and last changed by:

Created by: "BASIS "

Last changed by: "BASIS "

Error in the ABAP Application Program

The current ABAP program "/TMWFLOW/CL_MO_HTML_REQUEST===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

I went to SPro and changed the SLMO class interface from change request instance to Maintenance req instance. still the same error.

Any one can help me on this.

regards,

Prabhu