Solman 7.1 With the termination type RABAX_STATE when doing mopz

[Former Member]

Dear Experts,

We encounter the RABAX_STATE error when doing mopz, please advise.

The URL call http://tdssolman.thetempogroup.com:8000/sap/bc/webdynpro/sap/wda_mopz_plan was terminated because of an error.

Note

The followin error text was processed in SM2 the systm: An exception occurred

The error occurred on the application server tdssolman_SM2_00 and in the work process. 2

The termination type was: RABAX_STATE

The ABAP call hierarchy was:

Method: IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION of program CL_CHM1_CHANGE_REQU_INSTANCE==CP

Method: IF_SOCM_INSTANCE~CHECK_STATUS_CONDITION of program CL_CHM1_INSTANCE==============CP

Method: IF_EX_EXEC_METHODCALL_PPF~EXECUTE of program /TMWFLOW/CL_MO_IM_IMPL_SET====CP

Method: IF_EX_EXEC_METHODCALL_PPF~EXECUTE of program /TMWFLOW/CL_MO_IM_IMPL_SET====CP

Method: IF_EX_EXEC_METHODCALL_PPF~EXECUTE of program CL_EX_EXEC_METHODCALL_PPF=====CP

Method: EXECUTE of program CL_METHODCALL_PPF=============CP

Method: IF_MEDIUM_PPF~EXECUTE of program CL_METHODCALL_PPF=============CP

Method: EXECUTE of program CL_TRIGGER_PPF================CP

Method: PROCESS_TRIGGERS_CRM of program CL_CONTEXT_MANAGER_PPF========CP

Method: PROCESS_TRIGGERS_CRM of program CL_MANAGER_PPF================CP

What can you do?

With the termination type RABAX_STATE you will find in the system SM2 in transaction ST22 more information on the cause of the termination.

With termination type ABORT_MESSAGE_STATE you will findon the application server tdssolman_SM2_00 in transaction SM21 more information on the cause of the termination.

With termination type ERROR_MESSAGE_STATE you can scan for further information in the trace file for the work process 2 in transaction ST11 on the application server. tdssolman_SM2_00 It is possible that an analysis of the trace files for the other work processes is necessary.

If you do not yet have a user ID, contact your system adminmistrator.

Error Code: ICF-IE-http -c: 100 -u: SOLMAN_ADMIN -l: E -s: SM2 -i: tdssolman_SM2_00 -w: 2 -d: 20111023 -t: 213527 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION -X: 000C29A8A55702EFAE98226B72E8427A_000C29A8A55702DFAE98226B720ECD51_1 -x: 4EA0565539B9582AE10000000A020147

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

ST22:

Category ABAP Programming Error

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_SOCM_NOT_IMPLEMENTED

ABAP Program CL_CHM1_CHANGE_REQU_INSTANCE==CP

Application Component SV-SMG-CM

Date and Time 23.10.2011 21:30:26

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_CHANGE_REQU_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 no

caught and

therefore caused a runtime error.

The reason for the exception is:

An exception occurred

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"UNCAUGHT_EXCEPTION" "CX_SOCM_NOT_IMPLEMENTED"

"CL_CHM1_CHANGE_REQU_INSTANCE==CP" or "CL_CHM1_CHANGE_REQU_INSTANCE==CM009"

"IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION"

Regards,

Rudi

[former_member560910]

Hi Rudi,

I face the same Issue. Could you please let me know how you resolved it??

[Former Member]

Hi,

Could you also check the SAP Note 1242931? Though the note seems relevant for Solution Manager 700, but the symptoms looks exactly the same.

Also, have you run the solman_setup wizard completely as part of post installation activities.?

Regards,

Srikishan

[Former Member]

Hi Srikishan,

Thanks for the feed back, i have already read note given, however it is not applicable to my release.

I have run solman_setup and all the services has been activated.

Regards,

Rudi

[Former Member]

Hi Rudi,

Unfortunately the only option looks feasible now is to create OSS support message.

Regards,

Srikishan

[Miguel_Ariño]

Hello there,

I wrote the note, I have not checked it yet in Solution Manager 7.1. There is no code to be applied with this note.

Please check SPRO activity

SAP Solution Manager Implementation Guide

-> SAP Solution Manager

-> Capabilities (Optional)

-> Change Management

-> Standard Configuration

-> Change Request Management Framework

· Assign Implementation to Change Transaction Types

You have to make sure that the entry for SLMO is CL_CHM1_MAINT_OPT_INSTANCE in the table that you see when you execute that SPRO activity.

The note is relevant for Solution Manager 7.1 but I still have to change it to make sure the new SPRO path is described in the note.

Best regards,

Miguel Ariñ

[Miguel_Ariño]

No need to open a message yet.

I checked in our Solution Manager 7.1 test systems, the note describes correctly the entry in the table, but the SPRO path is the only thing that changed.

Best regards,

Miguel Ariño

Edited by: Miguel Angel Arino Clarke on Oct 24, 2011 12:02 PM