CX_SOCM_NOT_IMPLEMENTED

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

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?

Similar Messages

  • UNCAUGHT_EXCEPTION        CX_SOCM_NOT_IMPLEMENTED

    Hi all,
    i'm getting Dump error in Solution manager 7.0
    while performing maintenance optimizer.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_SOCM_NOT_IMPLEMENTED
    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.
    information on where it got terminated:----
      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.
    Request you to helpme in solving this dump error.
    thanking you in all and anticipation,
    by
    Raghava rao

    Hello Satheesh,
    Please go through the following SAP Note.
    [Note 1242931 - Dump UNCAUGHT_EXCEPTION - CX_SOCM_NOT_IMPLEMENTED|https://websmp230.sap-ag.de/sap/support/notes/1242931]
    Hope it helps
    Regards,
    Satish.

  • Runtime Error : UNCAUGHT_EXCEPTION

    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

    Hi Ruben,
    I have Implemented  both notes now i am getting differt error...
    Error is : Error No customer numbers in transaction AISUSER ...
    Message Number: SOLMAN_SAP_BACKEND016
    Diagnosis
    There are no entries with a customer number in the 'Customer Number' field in the table AISUSER.
    System Response
    You cannot get customer number-specific RFC destinations.
    Procedure
    Maintain these entries manually or start the report
    SMBI_AISUSER_VAR_MIG to copy any existing customer number from the table AISDK_CF_OSS_USR.
    Please suggest..
    Thanks in Advance..
    Regards,
    Suresh Kumar
    Edited by: suresh k on Apr 15, 2008 3:15 PM

  • [ChaRM] Phase Check "Current_Processor"

    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

    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.

  • Condition IMPORT_INTO_TEST_OK in ChaRM

    Dear Experts,
    On my Z Normal Correction I've added the condition IMPORT_INTO_TEST_OK to verify if the transport was imported succesfully in TST before continuing.
    Unfortunately when this condition is checked, I receive a short dump:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SOCM_NOT_IMPLEMENTED
    Date and Time          29.01.2009 10:27:52
    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_REG_CORR_INSTANCE=====CP' has to be
         terminated.
    I've removed the condition now and the short dump is also disappeared.
    Anybody an idea?
    We're using SolMan 7.0 SPS15.
    Any help is appreciated!
    Best regards,
    Roel

    Markus,
    Thanks for your answer.
    I already read this note, however it is focused on MOPZ and my Z transaction is a Change Doc (Normal Correction).
    I can try to change the implementation class the the suggested one in the note, but I'm afraid other functionality will not work any more.
    Best regards,
    Roel

  • EWA on solution manager - short dumps

    Hi there
    I've setup EWA on solution manager for Remote System BWQ, all test etc went fine, but as soon as I start service processing on solman to retrieve the data, a short dump is create as follows:
    Short text
        Syntax error in program "RDSVASAEA_ROOT_____________049 ".
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASAEA_ROOT_____________049
      " in include "RDSVASAEA_ROOT_____________049 " in
    line 87:
    "INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    could anyone please assist me with this.
    Regards,
    Stephan

    Hi
    So i tried to implement the above mentioned notes, but to update the solution manager stack, i have to use maintenance optimizer to approve the stack...
    I have added solution manager 7.0 to the solution overview, and can select it from 'Plan Maintenance' window.. but as soon as i try and go to the second step, another short dump is created.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SOCM_NOT_IMPLEMENTED
    Date and Time          13.06.2008 09:25:45
    |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.                                                                                |
    i then looked at Notes:
    Note 851496 - Exception: CX_SOCM_NOT_IMPLEMENTED missing implementation
    Note 849690 - BC Set Change Management
    But none of them seem relevant to our SOLMAN.

Maybe you are looking for

  • I am replacing my existing SATA hard drive to a Solid State hard drive and want to image the drive, is this possible?

    I am replacing my existing 320 GB SATA hard drive that clicks and makes weird noises to a Solid State hard drive and want to image the drive, is this possible?  I then want to replace the DVD with a secondary large drive for storage. So I am looking

  • Standard output in Web Logic

    Can anyone pls tell me where do all "system.out.println"s go in Web Logic server. I can get to see if it hits any exception, but it doesn't print the standard output there. I checked the Web Logic docs and it says that if I do not use Node manager to

  • Fcp6, Color 1.0.4 on Lion

    Is it possible to run FCP6, and Color 1.0.4 on Lion? Has anyone tried to run earlier versions of FCP on Lion?

  • Warnings when loading dimension members - no members loaded

    Hello, I did the mapping and the interface for loading members for a planning dimension (from csv file), run the 'execute' and have two warnings (on step1 and step7), however no members are loaded - warning for step7: org.apache.bsf.BSFException: exc

  • Macbook won't sync calendar

    When I enter an event into my Macbook, my iPad and iPhone show it in iCal, but when I enter an event into either my iPad or my iPhone, it does not show up in iCal on my Macbook. iCloud is enabled in my accounts, with Refresh Calendars every hour sele