RaISe_exception CNTL_error

While looking at an employee's details GH1 suddently logged  out.  when trying to log in again i am not able to veiw any transactions and a run time error appears: "exception conditions control_error raised. the current apab-4 program encountered an unexpected situation..."
I restart my computer and the entire system now appears very slow
Please advice/

Ask Your basis people to Solve the problem.

Similar Messages

  • Exception condition "CNTL_ERROR" raised.  in WDA :  smartform to pdf

    Hii, 
    I am using a webdynpro - abap application. I am showing  a smartform as a pdf in one on the windows.
    When the link in the main window is clicked, a secondary window. Instead of the pdf, I get following exception.Kindly help me understand, where would I be going wrong. Let me know if more details required.
    *Exception condition "CNTL_ERROR" raised. *
    Form: PBO_HTML_CONTROL of program SAPLSTXBC
    Module: HTML_CONTROL of program SAPLSTXBC
    Function: SSFCOMP_PDF_PREVIEW of program SAPLSTXBC
    Method: DISPLAYPDF of program /1BCWDY/2TKFRFPNZA4CZYBGEB8F==CP
    Method: IF_COMPONENTCONTROLLER~DISPLAYPDF of program /1BCWDY/2TKFRFPNZA4CZYBGEB8F==CP
    Method: ONACTIONPDF of program /1BCWDY/2TKFRFPNZA4CZYBGEB8F==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/2TKFRFPNZA4CZYBGEB8F==CP
    Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
    Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================CP
    Method: DO_HANDLE_ACTION_EVENT of program CL_WDR_WINDOW_PHASE_MODEL=====CP
    The code in the DISPLAYPDF method is as follows:
    method DISPLAYPDF .
    DATA: I_RS38L_FNAM TYPE  RS38L_FNAM.
    DATA: CTRL TYPE SSFCTRLOP.
    DATA: OUT TYPE  SSFCOMPOP.
    DATA: I_SSFCRESCL TYPE SSFCRESCL.
    DATA: LT_OTFDATA TYPE TABLE OF ITCOO.
    CTRL-GETOTF = 'X'.
    CTRL-NO_DIALOG = 'X'.
    CTRL-PREVIEW = 'X'.
    OUT-TDNEWID = 'X'.
    OUT-TDDELETE = ' '.
    data: i_tsp03 type tsp03.
    clear i_tsp03.
    select single * from tsp03 into i_tsp03.
    *OUT-TDDEST = i_tsp03-PADEST.
    OUT-TDDEST = 'TEP1'.
    ********get context data
      DATA lo_nd_zwebquestionaire TYPE REF TO if_wd_context_node.
      DATA lo_el_zwebquestionaire TYPE REF TO if_wd_context_element.
      DATA ls_zwebquestionaire TYPE wd_this->element_zwebquestionaire.
    * navigate from <CONTEXT> to <ZWEBQUESTIONAIRE> via lead selection
      lo_nd_zwebquestionaire = wd_context->get_child_node( name = wd_this->wdctx_zwebquestionaire ).
    * get element via lead selection
      lo_el_zwebquestionaire = lo_nd_zwebquestionaire->get_element(  ).
    * get all declared attributes
      lo_el_zwebquestionaire->get_static_attributes(
        IMPORTING
          static_attributes = ls_zwebquestionaire ).
    ********get context data ends
    data: itab1 type TCHAR255.
    data: itab2 type TCHAR255.
    data: itab type zprint. "addition by chandani
    data fm_name type rs38l_fnam..
    clear fm_name.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        FORMNAME             = 'ZCPESMARTFORM'
      IMPORTING
        FM_NAME              = fm_name
      EXCEPTIONS
        NO_FORM              = 1
        NO_FUNCTION_MODULE   = 2
        OTHERS               = 3.
    CALL FUNCTION fm_name
    EXPORTING
    *   ARCHIVE_INDEX              =
    *   ARCHIVE_INDEX_TAB          =
    *   ARCHIVE_PARAMETERS         =
       CONTROL_PARAMETERS         = CTRL
    *   MAIL_APPL_OBJ              =
    *   MAIL_RECIPIENT             =
    *   MAIL_SENDER                =
       OUTPUT_OPTIONS             = OUT
       USER_SETTINGS              = ' '
       NAME                       = 'test'
       ZWEBQUESTIONAIRE           = ls_ZWEBQUESTIONAIRE
    IMPORTING
    *   DOCUMENT_OUTPUT_INFO       =
       JOB_OUTPUT_INFO            = I_SSFCRESCL
    *   JOB_OUTPUT_OPTIONS         =
    TABLES                                  "addition by chandani
      itab                         = itab   "addition by chandani
    * EXCEPTIONS
    *   FORMATTING_ERROR           = 1
    *   INTERNAL_ERROR             = 2
    *   SEND_ERROR                 = 3
    *   USER_CANCELED              = 4
    *   OTHERS                     = 5
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    REFRESH LT_OTFDATA.
    LT_OTFDATA[] = I_SSFCRESCL-OTFDATA[].
    CALL FUNCTION 'SSFCOMP_PDF_PREVIEW'
      EXPORTING
        I_OTF                          = LT_OTFDATA
    * EXCEPTIONS
    *   CONVERT_OTF_TO_PDF_ERROR       = 1
    *   CNTL_ERROR                     = 2
    *   OTHERS                         = 3
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    DATA: PDF_DATA TYPE XSTRING,
          PDF_SIZE TYPE I.
    DATA: L_DUMMY TYPE STANDARD TABLE OF TLINE.
    CALL FUNCTION 'CONVERT_OTF'
    EXPORTING
       FORMAT                      = 'PDF'
    *   MAX_LINEWIDTH               = 132
    *   ARCHIVE_INDEX               = ' '
    *   COPYNUMBER                  = 0
    *   ASCII_BIDI_VIS2LOG          = ' '
    *   PDF_DELETE_OTFTAB           = ' '
    IMPORTING
       BIN_FILESIZE                = PDF_SIZE
       BIN_FILE                    = PDF_DATA
      TABLES
        OTF                         = LT_OTFDATA
        LINES                       = L_DUMMY
    * EXCEPTIONS
    *   ERR_MAX_LINEWIDTH           = 1
    *   ERR_FORMAT                  = 2
    *   ERR_CONV_NOT_POSSIBLE       = 3
    *   ERR_BAD_OTF                 = 4
    *   OTHERS                      = 5
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
      DATA lo_nd_pdf TYPE REF TO if_wd_context_node.
      DATA lo_el_pdf TYPE REF TO if_wd_context_element.
      DATA ls_pdf TYPE wd_this->element_pdf.
      DATA lv_sources LIKE ls_pdf-sources.
    * navigate from <CONTEXT> to <PDF> via lead selection
      lo_nd_pdf = wd_context->get_child_node( name = wd_this->wdctx_pdf ).
    * get element via lead selection
      lo_el_pdf = lo_nd_pdf->get_element(  ).
    * get single attribute
      lo_el_pdf->Set_attribute(
        EXPORTING
          name =  `SOURCES`
          value = PDF_DATA ).
    endmethod.

    Hi,
    1) This error generally comes ,when your GUI version is old.Check this point & try to upgrade.
    2) Otherwise if you are running report in background,then check madhu kumar's reply in this link & try like this.
    Dump Error Raise_Exception CNTL_ERROR
    Also search OSS notes.
    Thanks
    Gourav.

  • Exception condition "CNTL_ERROR" raised in class CL_GUI_CFW= UPDATE_VIEW

    There is a report which call a screen and it added the CustomControl to it and used the class   cl_gui_custom_container,  cl_gui_alv_grid,  lcl_event_receiver .
    Actually this report  has the facility to enter the data in the  output  and save it and when the user enter the data in the field and the class CL_GUI_CFW=>UPDATE_VIEW is getting triggered  and error is coming here.
    Exception condition "CNTL_ERROR" raised.
    A RAISE statement in the program "CL_GUI_CFW====================CP" raised the
      exception
    condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    and this issue is coming some times only and  not every time.
        1
        2 METHOD UPDATE_VIEW.
        3 * ...
        4   CALL FUNCTION 'AC_SYSTEM_FLUSH'
        5        exporting CALLED_BY_SYSTEM = called_by_system
        6        EXCEPTIONS
        7             CNTL_SYSTEM_ERROR = 1
        8             CNTL_ERROR        = 2
        9             OTHERS            = 3.
       10
       11   CASE SY-SUBRC.
       12     WHEN 0.
       13     WHEN 1.                            "// system_error
       14       RAISE CNTL_SYSTEM_ERROR.
       15     WHEN 2.                            "// method_call_error
    >>>>>       RAISE CNTL_ERROR.
       17     WHEN 3.                            "// property_set_error
       18       RAISE CNTL_ERROR.
       19     WHEN 4.                            "// property_get_error
       20       RAISE CNTL_ERROR.
       21     WHEN OTHERS.
       22       RAISE CNTL_ERROR.
       23   ENDCASE.
       24
       25 ENDMETHOD.

    Hi,
    1) This error generally comes ,when your GUI version is old.Check this point & try to upgrade.
    2) Otherwise if you are running report in background,then check madhu kumar's reply in this link & try like this.
    Dump Error Raise_Exception CNTL_ERROR
    Also search OSS notes.
    Thanks
    Gourav.

  • GOS vs. Archivelink Viewer - short dump

    Hi Folks,
    I've got a problem with the generic object services (GOS) and the archivelink viewer.
    In my own program (a copy of function group MR1M) the GOS is started at the beginning of the program (at least the GOS-starter is started).
    During the program execution, the function module ARCHIVELINK_FUNCTION is called to show archive documents in an external viewer.
    This works fine, except for this point:
    If the function module ARCHIVELINK_FUNCTION raises an error, this error is catched one level above. This works fine too.
    But with this "errorneous" call, it seems that the system changes something in the flow logic of the transaction.
    At the end of the action, the system flushes all data with the function module AC_SYSTEM_FLUSH (incl. GOS). But it seems, as if this service weren't started yet. But it is!
    => short dump (RAISE_EXCEPTION -> CNTL_ERROR)!
    Background information:
    1.) GOS is started
    a.) with function module SWU_OBJECT_PUBLISH (if there is an document number) or
    b.) at least the GOS-starter with method cl_gos_starter=>display.
    In this case, the complete service will get started later if the document number is known.
    2.) AC_SYSTEM_FLUSH tries to flush "SAPGUI.GOSCONTAINERCTRL.1".
    3.) The reason for this short dump is the "property_get_error"
    You can see this in the gui trace log too:
    <126=Monitor: CSession::ReadDataStream: AgiParseStream called
    <126=Monitor: CSession::ReadDataStream: AgiParseStream done
    <126=Monitor: UpdateUser: user = |EMEUREN|, lang = |DE|, code-page = 1160
    <126=Monitor: Program name     SAPLZRP_MR1M
    <126=(Error):    GET PROPERTY "Nodes" OF [#0]
    Invalid Object handle - this error may be caused by an ABAP programming error
    <126=(Error):                     Error occured at Verb  : Nodes
    <126=(Error):                                      Object: 0
    <126=(Error):    SAPAWRFC leaving RfcFlushOle with RfcRaise(GET_PROPERTY_FAILED)
    <126=Monitor: Double Buffering enabled
    Does anyone have an idea how to find the reason for this behavior?
    Best Regards
    Gerhard
    Message was edited by: Gerhard Meuren
    Message was edited by: Gerhard Meuren

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • Regarding short dump in program  SAPLCNDP with Raise_Exception

    Hi all,
    I am getting short dump "RAISE_EXCEPTION" in my system .
    Exception condition "CNTL_ERROR" raised.
    A RAISE statement in the program "SAPLCNDP " raised the exception
    condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLCNDP " in
    "DP_SYNC_URLS".
    The main program was "SAPLSMTR_NAVIGATION ".
    The termination occurred in line 31
    of the source code of program "LCNDPU40 " (when calling the editor 310).
    Needed reply urgently.
    Thanks in Advance,
    Nagamani

    In the shortdump, look for the value of the feature on which the error occurred.. ie the variable FEATURE_ID & try if you can activate that feature using Tcode PE03.
    ~Suresh

  • Error in F110 transacion - CNTL_ERROR

    We are rececived the following error message when execute the F110 transaction:
    Short text
        Exception condition "CNTL_ERROR" raised.
    Error analysis
        A RAISE statement in the program "CL_GUI_CFW====================CP" raised the
         exception
        condition "CNTL_ERROR".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    How to correct the error
        If the error occures in a non-modifie
        find an interim solution in an SAP No
        If you have access to SAP Notes, carr
        keywords:
        "RAISE_EXCEPTION" " "
        "CL_GUI_CFW====================CP" or
        "UPDATE_VIEW"
        or
        "CL_GUI_CFW====================CP" "C
        or
        "SAPF110O " "CNTL_ERROR"
    Please I need your help.
    Thanks.

    Hello!
    CNTL_ERROR,  this error is described in note:                                                                               
    316243 - Exception CNTL_ERROR or dump in SAPLOLEA                                                                               
    So the error is related to SAP GUI.                                                                               
    So could you please try the followings in one affected workstation :                                                                               
    1 -  remove current SAPGUI from Start -> Control panel -> Add/remove.    
    2 - After this, please make sure that the folder                         
        c:\program files\SAP\Frontend is properly removed. Otherwise delete  
        it manually.                                                         
    3 - Empty the recycle bin and reboot the computer                        
    4 - Re-install the latest GUI patch, refer to note  14751  or  563161.
                                                                                    After this, the dump should not occur.                                   
    REgards,
    REnan

  • Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILU

    Hi All,
    After the custo of the ESSleave request  in the IMG . I made some tests.
    Evrethign is going fine but once i try to enter a leave request during a non wroking day, i'm getting this message
    Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE
    I checked in st22 and they ask to find a sap note with those key words
    "RAISE_EXCEPTION" " "
    "SAPLSPO1" or "LSPO1F01"
    "INSTANTIATE_CONTROL"
    or
    "SAPLSPO1" "CNTL_ERROR"
    or
    "SAPMSSY1 " "CNTL_ERROR"
    I found nothing that can help me in sap service..
    Did someone already encounter such error ?
    Only usefull answers will be rewared .

    Hi Adel,
    Can you test the same application in the content administrator of the respective portal and check if you find the same error or another error.
    Regards,
    Narendra.

  • CNTL_ERROR while running a custom report program in background mode

    Hi,
    I am running a report in background on daily basis. I am using cl_gui_custom_container class here and calling the constructor of this class. I am getting a CNTL_ERROR exception at this point. But if i run the same report directly, it is not throwing any exception. The problem is if i schedule it to background. I am not able to sort it out.
    I've written the following code below:
    I did apply the logic that you'd mentioned.
    I've implemented the code as below.
    IF  gr_container IS INITIAL.
    *** Check whether the program is run in batch or foreground
        IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.
    * Run in foreground
          CREATE OBJECT gr_container
            EXPORTING
              container_name = 'WORK_AREA_CONTAINER'.
          CREATE OBJECT lv_grid
            EXPORTING I_PARENT = gr_container.
        ELSE.
    * Run in background
          CREATE OBJECT lv_grid
            EXPORTING
              I_PARENT = gr_dockcontainer.
          ENDIF.
          ENDIF.
    i_parent_control = gr_dockcontainer.
            CREATE OBJECT m_base_splitter
            EXPORTING
              parent            = i_parent_control
              ROWS              = 1
              columns           = 2
            EXCEPTIONS
              cntl_error        = 1
              cntl_system_error = 2
              OTHERS            = 3.
            CALL METHOD m_base_splitter->get_container
            EXPORTING
              row       = 1
              column    = 2
              RECEIVING
              container = m_splitter_right_part
            EXCEPTIONS
              OTHERS    = 1.
    After I've implemented the above code I'm getting the following error in the batch job:
    Category               ABAP Programming Error
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Except.                CX_SY_REF_IS_INITIAL
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "M_BASE_SPLITTER").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    Would you be able to help me in the above issue?
    Regards,
    Mandeep

    Hi Alexander,
    Yes I'd declared gr_dockcontainer as type ref to CL_GUI_DOCKING_CONTAINER. And I've now replaced the previous code and wwrote the below code :
    gr_container IS INITIAL.
    ***Check whether the program is run in batch or foreground
          IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.
    ***Run in foreground
            CREATE OBJECT gr_container
              EXPORTING
                container_name = 'WORK_AREA_CONTAINER'.
            CREATE OBJECT lv_grid
              EXPORTING
                I_PARENT = gr_container.
          ELSE.
    ***Run in background
            CREATE OBJECT gr_dockcontainer
              EXPORTING
                NAME = 'WORK_AREA_CONTAINER'.
          ENDIF.
        ENDIF.
    = gr_dockcontainer.
        CREATE OBJECT m_base_splitter
          EXPORTING
            parent            = i_parent_control
            ROWS              = 1
            columns           = 2
          EXCEPTIONS
            cntl_error        = 1
            cntl_system_error = 2
            OTHERS            = 3.
        CALL METHOD m_base_splitter->get_container
          EXPORTING
            row       = 1
            column    = 2
          RECEIVING
            container = m_splitter_right_part
          EXCEPTIONS
            OTHERS    = 1.
    But after implementing the above code I'm facing the same issue of CTRL ERROR- " GUI cannot be reached".
    Please guide me through this.
    Regards,
    Mandeep

  • CNTL_ERROR while running a report in background mode

    Hi,
    I am running a report in background on daily basis. I am using cl_gui_custom_container class here and calling the constructor of this class. I am getting a CNTL_ERROR exception at this point. But if i run the same report directly, it is not throwing any exception. The problem is if i schedule it to background. I am not able to sort it out. So please if any body knows, answer this.
    Thanks,
    Kumar

    Hi Nithin,
    I was facing the similar issue in a custom report program. I did apply the logic that you'd mentioned.
    I've implemented the code as below.
    IF  gr_container IS INITIAL.
    *** Check whether the program is run in batch or foreground
        IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.
    * Run in foreground
          CREATE OBJECT gr_container
            EXPORTING
              container_name = 'WORK_AREA_CONTAINER'.
          CREATE OBJECT lv_grid
            EXPORTING I_PARENT = gr_container.
        ELSE.
    * Run in background
          CREATE OBJECT lv_grid
            EXPORTING
              I_PARENT = gr_dockcontainer.
          ENDIF.
          ENDIF.
    i_parent_control = gr_dockcontainer.
            CREATE OBJECT m_base_splitter
            EXPORTING
              parent            = i_parent_control
              ROWS              = 1
              columns           = 2
            EXCEPTIONS
              cntl_error        = 1
              cntl_system_error = 2
              OTHERS            = 3.
            CALL METHOD m_base_splitter->get_container
            EXPORTING
              row       = 1
              column    = 2
              RECEIVING
              container = m_splitter_right_part
            EXCEPTIONS
              OTHERS    = 1.
    After I've implemented the above code I'm getting the following error in the batch job:
    Category               ABAP Programming Error
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Except.                CX_SY_REF_IS_INITIAL
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "M_BASE_SPLITTER").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    Would you be able to help me in the above issue?

  • CNTL_ERROR while calling a function module from Java webdynpro

    I am calling a RFC function module from javawebdynpro app
    which inturn calls a function module performing BDC on CAPP transaction. When I run this from SE37 of the same system or a different system everything works fine. But when called from Java webdynpro app, it raises a CNTL_ERROR exception and creates a short dump.
    Any help on this is highly appreciated

    Good catch, BI Learner. This was exactly it: when assigning the values from SOURCEFIELDS directly to the import/export parameters, you have to make sure that the types are EXACTLY the same, otherwise it will not work (the routine stops with an error when calling the FM, but there is no dump).
    Therefore, to solve my problem, I created the declarations precisely as expected by the FM and assigned the values to these fields:
    DATA:
          SOURCEVAL TYPE  /BIC/OIINVQTY,
          SOURCEUOM TYPE  /BIC/OIUSUOM,
          USITM TYPE  /BIC/OIUSITM,
          TARGETUOM TYPE  /BIC/OIUSUOM,
          CONVERTED_COST TYPE  /BIC/OIINVQTY.
    DATA PRODUCTION_UOM TYPE /BIC/OIUSUOM.
    " get the Production UOM
        SELECT SINGLE I~/BIC/USPRDUOM
          FROM /BIC/PUSITM AS I
          INTO PRODUCTION_UOM
          WHERE I~/BIC/USITM = SOURCE_FIELDS-/BIC/USITM AND I~OBJVERS = 'A'.
        IF ( SY-SUBRC = 4 ). " no records found
          "RAISE PARTNO_NOT_FOUND.
          RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
        ENDIF.
    " load the parameters
        SOURCEVAL = SOURCE_FIELDS-/BIC/USFRZMFC.
        SOURCEUOM = SOURCE_FIELDS-BASE_UOM.
        USITM = SOURCE_FIELDS-/BIC/USITM.
    " then you can call the FM
        CALL FUNCTION 'Z_CA_CONVERT_US_COST'
          EXPORTING
            PSOURCEVAL                = SOURCEVAL
            PSOURCEUOM                = SOURCEUOM
            PUSITM                    = USITM
            PTARGETUOM                = PRODUCTION_UOM
          IMPORTING
            PTARGETVAL                = CONVERTED_COST
          EXCEPTIONS
            CONVERSION_NOT_MAINTAINED = 1
            PARTNO_NOT_FOUND          = 2
            OTHERS                    = 3.
    " ... [do the rest]
    Thanks for your help,
    Dennis

  • Raise_Exception in CL_CGPL_STATUS_MANAGEMENT=====CP

    Hello Expert,
    Please help me with Raise_Exception dump.Customer is facing this problem daily .we have debugged program many time and all but we are not able to find any clue.Its based on Fund plan id and campaign. And i have checked SAP Note-1475108. it doesn't support.Now please tell me valid solution to resolve this problem.
    From this dump analysis i have take fund plan id and all campaign and took web ui screen screen shot.you can find screen shot in attachment. if you need variable details on web ui.
    Category              ABAP Programming Error
    Runtime Errors        RAISE_EXCEPTION
    ABAP Program          CL_CRM_MKTCA_PROCESSMODEL=====CP
    Application Component  CRM-MKT-MPL-CA-MOD
    Date and Time          23.02.2015 01:58:22
    |Short text                                                                                        |
    |    Exception condition "OBJECT_NOT_FOUND" raised.                                                |
    |What happened?                                                                                    |
    |    The current ABAP/4 program encountered an unexpected                                          |
    |    situation.                                                                                    |
    Error analysis                                                                                    |
    |    A RAISE statement in the program "CL_CGPL_STATUS_MANAGEMENT=====CP" raised the                |
    |    exception                                                                                    |
    |    condition "OBJECT_NOT_FOUND".                                                                |
    |    Since the exception was not intercepted by a superior                                        |
    |    program, processing was terminated.                                                          |
    |                                                                                                  |
    |    Short description of exception condition:                                                    |
    |                                                                                                  |
    |    Status Object Does Not Exist                                                                  |
    |                                                                                                  |
    |    For detailed documentation of the exception condition, use                                    |
    |    Transaction SE37 (Function Library). You can take the called                                  |
    |    function module from the display of active calls.
    |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:                                                                                    |
    |                                                                                                  |
    |    "RAISE_EXCEPTION" " "                                                                        |
    |    "CL_CGPL_STATUS_MANAGEMENT=====CP" or "CL_CGPL_STATUS_MANAGEMENT=====CM004"                  |
    |    "STATUS_CHECK"                                                                                |
    |                                                                                                  |
    |    or                                                                                            |
    |                                                                                                  |
    |    "CL_CGPL_STATUS_MANAGEMENT=====CP" "OBJECT_NOT_FOUND"                                        |
    |                                                                                                  |
    |    or                                                                                            |
    |                                                                                                  |
    |    "SAPMSSY1 " "OBJECT_NOT_FOUND"                                                                |
    |    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.
    |Information on where terminated                                                                  |
    |    Termination occurred in the ABAP program "CL_CGPL_STATUS_MANAGEMENT=====CP" -                |
    |    in "STATUS_CHECK".                                                                          |
    |    The main program was "SAPMSSY1 ".                                                            |
    |                                                                                                  |
    |    In the source code you have the termination point in line 12                                  |
    |    of the (Include) program "CL_CGPL_STATUS_MANAGEMENT=====CM004".                              |
    |Source Code Extract                                                                              |
    |Line |SourceCde                                                                                  |
    |    1|METHOD status_check.                                                                        |
    |    2|* ...                                                                                      |
    |    3|  CALL FUNCTION 'CRM_STATUS_CHECK'                                                          |
    |    4|      EXPORTING                                                                            |
    |    5|            objnr            = im_guid                                                    |
    |    6|            status            = im_status                                                  |
    |    7|      EXCEPTIONS                                                                          |
    |    8|            object_not_found  = 1                                                          |
    |    9|            status_not_active = 2.                                                          |
    |  10|  CASE sy-subrc.                                                                            |
    |  11|    WHEN 1.                                                                                |
    |>>>>>|      RAISE object_not_found.                                                              |
    |  13|    WHEN 2.                                                                                |
    |  14|      RAISE status_not_active.                                                              |
    |  15|  ENDCASE.                                                                                  |
    |  16|                                                                                            |
    |  17|ENDMETHOD.                                                                                  |
    |Contents of system fields                                                                        |
    |Name    |Val.                                                                                    |
    |SY-SUBRC|1                                                                                        |
    |SY-INDEX|0                                                                                        |
    |SY-TABIX|6                                                                                        |
    |SY-DBCNT|0                                                                                        |
    |SY-FDPOS|3                                                                                        |
    |SY-LSIND|0                                                                                        |
    |SY-PAGNO|0                                                                                        |
    |SY-LINNO|1                                                                                        |
    |SY-COLNO|1                                                                                        |
    |SY-PFKEY|                                                                                        |
    |SY-UCOMM|                                                                                        |
    |SY-TITLE|CPIC and RFC Control                                                                    |
    |SY-MSGTY|E                                                                                        |
    |SY-MSGID|BS                                                                                      |
    |SY-MSGNO|001                                                                                      |
    |SY-MSGV1|<Unknown Object>                                                                        |
    |SY-MSGV2|001999C211111ED3A39A399B369454CA                                                        |
    |SY-MSGV3|                                                                                        |
    |SY-MSGV4|                                                                                        |
    |SY-MODNO|0                                                                                        |
    |SY-DATUM|20150223                                                                                |
    |SY-UZEIT|015818                                                                                  |
    |SY-XPROG|SAPLRREL                                                                                |
    |SY-XFORM|CONVERSION_EXIT                                                                          |
    |Active Calls/Events                                                                              |
    |No.  Ty.          Program                            Include                            Line  |
    |      Name                                                                                        |
    |  16 METHOD      CL_CGPL_STATUS_MANAGEMENT=====CP    CL_CGPL_STATUS_MANAGEMENT=====CM004    12  |
    |      CL_CGPL_STATUS_MANAGEMENT=>STATUS_CHECK                                                    |
    |  15 METHOD      CL_CRM_MKTCA_PROCESSMODEL=====CP    CL_CRM_MKTCA_PROCESSMODEL=====CM01A    19  |
    |      CL_CRM_MKTCA_PROCESSMODEL=>GET_MESSAGE_TYPE                                                |
    |  14 METHOD      CL_CRM_MKTCA_PROCESSMODEL=====CP    CL_CRM_MKTCA_PROCESSMODEL=====CM012    49  |
    |      CL_CRM_MKTCA_PROCESSMODEL=>CHECK_NODE_POSITIONS                                            |
    |  13 METHOD      CL_CRM_MKTCA_PROCESSMODEL=====CP    CL_CRM_MKTCA_PROCESSMODEL=====CM011    13  |
    |      CL_CRM_MKTCA_PROCESSMODEL=>CHECK                                                            |
    |  12 METHOD      CL_CRM_MKTCA_PROCESSMODELS====CP    CL_CRM_MKTCA_PROCESSMODELS====CM00C    15  |
    |      CL_CRM_MKTCA_PROCESSMODELS=>CHECK                                                          |
    |  11 METHOD      CL_CRM_MKTPL_APPLICATION_MGR==CP    CL_CRM_MKTPL_APPLICATION_MGR==CM012    11  |
    |      CL_CRM_MKTPL_APPLICATION_MGR=>DO_CHECK_BEFORE_SAVE                                          |
    |  10 METHOD      CL_CRM_MKTGS_APPLICATION_MGR==CP    CL_CRM_MKTGS_APPLICATION_MGR==CM003    52  |
    |      CL_CRM_MKTGS_APPLICATION_MGR=>CHECK_BEFORE_SAVE                                            |
    |    9 METHOD      CL_CRM_MKTGS_APPLICATION_MGR==CP    CL_CRM_MKTGS_APPLICATION_MGR==CM00D    17  |
    |      CL_CRM_MKTGS_APPLICATION_MGR=>SAVE_AND_COMMIT                                              |
    |    8 METHOD      CL_CRM_MKTPL_CPG_FM_ERP_FPO===CP    CL_CRM_MKTPL_CPG_FM_ERP_FPO===CM001  265  |
    |      CL_CRM_MKTPL_CPG_FM_ERP_FPO=>POST_ERP_AMOUNTS                                              |
    |    7 METHOD      YWCRM_CL_MKTPL_PURCH_UPD_FUNDSCP    YWCRM_CL_MKTPL_PURCH_UPD_FUNDSCM002    83  |
    |      YWCRM_CL_MKTPL_PURCH_UPD_FUNDS=>PERFORM_EXTERNAL_SETTLEMENT                                |
    |    6 METHOD      YWCRM_CL_MKTPL_PURCH_UPD_FUNDSCP    YWCRM_CL_MKTPL_PURCH_UPD_FUNDSCM003    89  |
    |      YWCRM_CL_MKTPL_PURCH_UPD_FUNDS=>IF_CRM_FM_ACL_JOB~PROCESS_OBJECTS                          |
    |    5 METHOD      CL_CRM_FM_ACL_JOB_PROCESSING==CP    CL_CRM_FM_ACL_JOB_PROCESSING==CM00D    87  |
    |      CL_CRM_FM_ACL_JOB_PROCESSING=>IF_CRM_FM_ACL_JOB_REPORT_IL~EXECUTE_DIRECT_JOB                |
    |    4 FUNCTION    SAPLCRM_FM_ACL_JOB                  LCRM_FM_ACL_JOBU01                    73  |
    |      CRM_FM_ACL_JOB_PARALLEL_EXEC                                                                |
    |    3 FORM        SAPLCRM_FM_ACL_JOB                  LCRM_FM_ACL_JOBU01                      1  |
    |      CRM_FM_ACL_JOB_PARALLEL_EXEC                                                                |
    |    2 FORM        SAPMSSY1                            SAPMSSY1                              167  |
    |      REMOTE_FUNCTION_CALL                                                                        |
    |    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                              35  |
    |      %_RFC_START                                                                                |
    If you want to see full details regarding variable also so please find in attachment.

    Hi Kamal,
    I recommend to open a ticket for SAP with the runtime error attached.
    Best regards,
      Andreas

  • Dump RAISE_EXCEPTION PARTNER_NOT_VALID

    Hi,
    Got a dump in production system.Dont know the cause.Please help in finding solution
    What happened?
        The current ABAP/4 program encountered an unexpected
        situation.
    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
        A RAISE statement in the program "SAPLBBP_BUPA" raised the exception
        condition "PARTNER_NOT_VALID".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    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:
        "RAISE_EXCEPTION" " "
        "SAPLBBP_BUPA" or "LBBP_BUPAU22"
        "BBP_PARTNER_GET_PURCH_DATA_NEW"
        or
        "SAPLBBP_BUPA" "PARTNER_NOT_VALID"
        or
        "SAPLBBP_PO_UI_ITS " "PARTNER_NOT_VALID"
    Contents of system fields
    Name     Val.
    SY-SUBRC 0
    SY-INDEX 0
    SY-TABIX 1
    SY-DBCNT 12
    SY-FDPOS 72
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY
    SY-UCOMM PVIEW
    SY-TITLE Create Purchase Order
    SY-MSGTY E
    SY-MSGID R11
    SY-MSGNO 177
    SY-MSGV1 9000000207
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20100610
    SY-UZEIT 132611
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT
    Regards,
    Shiva

    Hi,
    This error probably happened due to an issue with report BBPUPDVD, this is used to update vendor data (eg address). Check when vendors are getting updated and see if there are any conflicts occuring here.
    Also it would be no harm check for recent notes valid for your release level for BBP_VENDOR_SYNC and BBPUPDVD.
    I hope this helps,
    Lisa

  • RAISE_EXCEPTION condition NO_AUTHORITY

    Hi,
    I am getting the RAISE_EXCEPTION since two day can some please sugget on this issue. these dumps are generating when the job is SM:FILL SD CACHE FOR WORKCENTER is after starting the Step 001 started (program RAGS_WORK_SD_CACHE, variant , user ID SOLMAN_BTC)and job got cancelled with RAISE_EXCEPTION,
    plase checkthe dumps below.
    Short text
        Exception condition "NO_AUTHORITY" raised.
    Error analysis
        A RAISE statement in the program "SAPLDSWP_CI" raised the exception
        condition "NO_AUTHORITY".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    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:
        "RAISE_EXCEPTION" " "
        "SAPLDSWP_CI" or "LDSWP_CIU53"
        "DSWP_CI_GET_CRM_OF_SOLUTION"
        or
        "SAPLDSWP_CI" "NO_AUTHORITY"
        or
        "RAGS_WORK_SD_CACHE " "NO_AUTHORITY"
        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)".
    Information on where terminated
        Termination occurred in the ABAP program "SAPLDSWP_CI" - in
         "DSWP_CI_GET_CRM_OF_SOLUTION".
        The main program was "RAGS_WORK_SD_CACHE ".
        In the source code you have the termination point in line 19
        of the (Include) program "LDSWP_CIU53".
        The program "SAPLDSWP_CI" was started as a background job.
        Job Name....... "SM:FILL SD CACHE FOR WORKCENTER"
        Job Initiator.. "SOLMAN_ADMIN"
        Job Number..... 19070501
    thanks
    saprock
    Edited by: saprock006 on Apr 21, 2010 8:52 AM

    Hi,
    It is a problem of authorization for user SOLMAN_BTC.
    Refer the below note:
    [Note 1314587 - User SOLMAN_BTC missing authorization|https://service.sap.com/sap/support/notes/1314587]
    Follow the instructions given in the note.
    Hope, your problem will get solved.
    Regards.
    Rajesh Narkhede

  • CNTL_ERROR  in job scheduling log

    Hi experts,
                i have developed a report to upload the time event data from multiple text files into  table CC1TEV. My report is having a few standard function modules. And i have scheduled the  program using SM36. Erlier i was getting run-time error CNTL_ERROR 
    but then i uncommented  it in one of the function module now its working fine but data is not getting updated in table CC1TEV.
    please help me.
    Thanks.
    Praveen

    Hello Jery Wang,
                    i got your point.. but my requirement is to read single or multiple files from a directory which is on presentation server,that i am doing with FM 'TMP_GUI_DIRECTORY_LIST_FILES' and then i am performing loop on internal table to read the data of every file into another internal table and then updating the table 'CC1TEV' . Here all the activities have to be performed as background  job.
    But as you suggested me to go with application server. my doubt is can we write presentation server data on application server directory in background job ? If yes ... then how ?
    please guide me ...
    Thanks.
    Praveen.

  • Error 00-341 RAISE_EXCEPTION when using Call Transaction for VA01 in backgr

    Hi,
    I am getting this message when I use call transaction to create a sales order using VA01. Following is the statement I have used.  Note that when i execute the program online, I am not getting any errors. I could create sales order without any problem. I am getting this exception only when I run in background.
          CALL TRANSACTION 'VA01'
                     USING BDC_TAB
                      MODE 'N'
                    UPDATE 'S'
             MESSAGES INTO W_MESS_TAB.
    When I captured message tab, I got following messages.
    DC006 - Control Framework: Fatal error - GUI cannot be reached
    00341 Runtime error RAISE_EXCEPTION has occurred.
    Please help me in this regard.
    Regards
    Kasi

    Some times execution of BDC program in back ground is different from the foreground. Some screens may appear in background and raise error while same will not when executed in foreground.
    Double click the message in Session log to know more details.
    One way is to suppress the screen while executing BDC.
    Alternatively I suggest to use BAPI instead.
    - Sanjay

Maybe you are looking for