Runtime Error : UNCAUGHT_EXCEPTION

Former Member · ‎03-31-2008

Hi Solman Experts,

While downloading softwares through Maintenace Optimizer ( Solution Manager ),I am getting below error..

First Error :

Function module /SDF/AL_MAP_TRANSID_LOGH does not exist.

The Maintenance Optimizer can automatically determine which files you require to update the ABAP and Java software components of your systems.

The search is performed for all instances of the selected systems flagged as relevant.

I have already checked in service market place and apply the SAP note 1135893 and we have activate the some components (BC Set)

See Note 898614 after that i am getting big problem.

Second Error : ( ABAP Dump )

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_SOCM_NOT_IMPLEMENTED

Date and Time 31.03.2008 15:04:31

-

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.

-

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

-

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

-

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"*


If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

-

System environment

SAP-Release 700

Application server... "ALBE0510"

Network address...... "10.201.180.10"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "ALBE0510"

Database type..... "MSSQL"

Database name..... "SP0"

Database user ID.. "sp0"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Oct 23 2007 00:33:51"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 133

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 41898400

Heap.... 0

Page.... 40960

MM Used. 33604960

MM Free. 4099184

-

User and Transaction

Client.............. 001

User................ "KONS222"

Language key........ "E"

Transaction......... "DSWP "

Transactions ID..... "AE21FFDCBA44F199AB15005056836080"

Program............. "CL_CHM1_CHANGE_REQU_INSTANCE==CP"

Screen.............. "RDSMOP_MAIN 0100"

Screen line......... 5

-

Information on where terminated

Termination occurred in the ABAP program "CL_CHM1_CHANGE_REQU_INSTANCE==CP" -

in "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION".

The main program was "RDSMOP_MAIN ".

In the source code you have the termination point in line 612

of the (Include) program "CL_CHM1_CHANGE_REQU_INSTANCE==CM009".

-

Source Code Extract

-

Line

SourceCde

-

582	conditions_ok = cl_socm_integration=>false.
583	ENDIF.
584	ENDIF.
585
586	WHEN 'S_USER_CHECK'.
587	conditions_ok = cl_socm_integration=>true.
588	CALL METHOD cl_sm_base_sender=>get_assigned_suser
589	EXPORTING
590	i_no_dialogue = 'X'
591	IMPORTING
592	e_suser = e_suser
593	e_partner_no = lv_parnr
594	EXCEPTIONS
595	no_user_assigned = 1
596	no_customer_number = 2
597	OTHERS = 3.
598	IF sy-subrc = 1 OR sy-subrc = 3.
599	conditions_ok = cl_socm_integration=>false.
600	ENDIF.
601	WHEN 'NO_CRTCL_OBJ'.
602	conditions_ok = me->check_crtcl_obj( ).
603	WHEN '0NO'.
604	conditions_ok = cl_socm_integration=>false.
605	WHEN '0YES'.
606	conditions_ok = cl_socm_integration=>true.
607	WHEN '0BREAK'.
608	BREAK-POINT. "#EC NOBREAK
609	WHEN space.
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.
614
615	ENDMETHOD.

Please suggest. Thanks in Advance...

Regards,

Suresh Kumar

Former Member · ‎04-16-2008

Hi,

you were right.

Deleting these entries:

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

solved the problem (dump: CX_SOCM_NOT_IMPLEMENTED). Thanks a lot for this advice.

Best wishes Niklas

Former Member · ‎04-14-2008

and also to the note 1141604, we applied both notes and that did the trick.

Former Member · ‎04-14-2008

Take a look to the note 1135893.

markus_doehr2 · ‎04-14-2008

Do you have installed the latest ST/A-PI addin in your solution manager?

Markus

Former Member · ‎04-14-2008

Hi

i have sent you an e-mail. But the ABAP is dump exactly the same as the one you posted.

BC Sets are activated via transaction SPRO

Best wishes

Niklas

Former Member · ‎04-12-2008

Hi Guys,

Even i am getting the following error message while confirming the items in the download basket.

Function module /SDF/AL_MAP_TRANSID_LOGH does not exist.

The Maintenance Optimizer can automatically determine which files you require to update the ABAP and Java software components of your systems.

The search is performed for all instances of the selected systems flagged as relevant.

Please Help,

Regards,

Former Member · ‎04-11-2008

Hi

"Function module /SDF/AL_MAP_TRANSID_LOGH does not exist." <-- I dont get this error. I only get the ABAP Dump after clicking continue...

Best wishes

Former Member · ‎04-11-2008

Hi

Well i didnt get any error after applying SP15. But i have got the problem in MOPZ. When I selected the logical component and i click Continue i get the same dump as you:

CX_SOCM_NOT_IMPLEMENTED

Best wishes

Former Member · ‎04-11-2008

Hi,

i have installed a SolMan on SPT15. I got the second error that u got as well.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_SOCM_NOT_IMPLEMENTED

I always get this error after I have selected the logical component and clicked Continue or when i try to Withdraw the Maintenance Optimizer transaction.

Have you managed to solve this problem?

Best wishes Niklas

Runtime Error : UNCAUGHT_EXCEPTION

Accepted Solutions (0)

Answers (9)

Answers (9)

Vendor Invoice Screen 'Payment' tab screen field '...

I have data like Date, Net, Gross. I want to deriv...

Re: Re Generate Co files and data files

Re: error during install SAP S/4HANA Server 2022

Re: BODS Job Stored Procedure