CRM_IC - SAPLTHFB "Raise_exception"

I need your help, my CRM_IC don't run send me this error, mi services are activate, but the page cannot displayed, please send me information about this.
Thanks every body
Alejandro
Mexico City

Hi KZ,
i've run the CRMS_IC_CHECK and i got following message:
Check System Settings and Status
TIME:      09:33:53
   Configuration summary
   Domain:                                       sapdemo.local
   Context Area Style Sheet:
   Scratch Pad Style Sheet:
   Broadcast Style Sheet:
   General
      Server domains are compatible.
      Logical system: CROCLNT100
The J2EE and HTTP service is running. the CRM_IC is activated. I even got same error when i test the CRM_IC from sicf. Not sure how i can progress further.
Thanks

Similar Messages

  • Crm_ic created raised exception

    Hello,
    I tried to run tcode crm_ic but I got following error message from the internet explorer:
    <b><b><b>The following error text was processed in the system CRO : Exception
    condition "COMMUNICATION_ERROR" raised.
    The error occurred on the application server sap1770_CRO_01 and in the
    work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CREATE_SESSION of program CL_SAM_BSP_SESSION_LAUNCHER===CP
    Method: START_WORKER_SESSION of program CL_ICWC_SESSION_REGISTRY======CPMethod: ONCREATE of program CLO23UTXK1DHIM8WX0QZD2TBW2KZ9CP
    Method: %_ONCREATE of program CL_O23UTXK1DHIM8WX0QZD2TBW2KZ9CP
    Method: DO_INIT of program CL_BSP_PAGE===================CP
    Method: GET_PAGE_CONTEXT_CURRENT of program
    CL_BSP_CONTEXT================CP
    Method: ON_REQUEST_ENTER of program CL_BSP_RUNTIME================CP
    Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program
    CL_HTTP_EXT_BSP===============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP</b></b></b>
    Below is the abap dump message:
    Runtime Errors         RAISE_EXCEPTION
    Date and Time          14.05.2007 04:05:51
    Short text
    Exception condition "COMMUNICATION_ERROR" raised.
    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 "CL_SAM_BSP_SESSION_LAUNCHER===CP" raised the
    exception
    condition "COMMUNICATION_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-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_SAM_BSP_SESSION_LAUNCHER===CP" or "CL_SAM_BSP_SESSION_LAUNCHER===CM002"
    "CREATE_SESSION"
    or
    "CL_SAM_BSP_SESSION_LAUNCHER===CP" "COMMUNICATION_ERROR"
    or
    "SAPMHTTP " "COMMUNICATION_ERROR"
    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... "sap1770"
    Network address...... "217.67.56.37"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "SAP1770"
    Database type..... "MSSQL"
    Database name..... "CRO"
    Database user ID.. "cro"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jan 15 2006 23:05:36"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 41
    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"
    Memory consumption
    Roll.... 8176
    EM...... 4180896
    Heap.... 0
    Page.... 24576
    MM Used. 3736976
    MM Free. 442176
    User and Transaction
    Client.............. 100
    User................ "DIAGBASIS"
    Language Key........ "E"
    Transaction......... " "
    Program............. "CL_SAM_BSP_SESSION_LAUNCHER===CP"
    Screen.............. "SAPMHTTP 0010"
    Screen Line......... 2
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. "172.27.104.12"
    Caller Port........... 8001
    Universal Resource Id. "/sap/bc/bsp/sap/ic_base/main.htm"
    Information on where terminated
    Termination occurred in the ABAP program "CL_SAM_BSP_SESSION_LAUNCHER===CP" -
    in "CREATE_SESSION".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 23
    of the (Include) program "CL_SAM_BSP_SESSION_LAUNCHER===CM002".
    Source Code Extract
    Line
    SourceCde
    1
    method CREATE_SESSION .
    2
    3
    data: rfcdest     type rfcdest.
    4
    data: status      type i.
    5
    data: http_client type ref to if_http_client.
    6
    7
    rfcdest = destination.
    8
    cl_http_client=>create_by_destination( EXPORTING destination = rfcdest IMPORTING client =
    9
    10
    http_client->request->set_header_field( name = '~request_uri'     value = uri
    11
    http_client->request->set_header_field( name = '~request_method'  value = 'GET'
    12
    http_client->request->set_header_field( name = if_http_header_fields=>user_agent value = s
    13
    http_client->send( exporting timeout = 10 ).
    14
    http_client->receive(  ).
    15
    data = http_client->response->get_data( ).
    16
    http_client->response->get_status( importing code = status ).
    17
    http_client->close( ).
    18
    19
    data: s type string.                                      "#EC NEEDED
    20
    s = cl_sam_toolkit=>x2s( data ).
    21
    22
    if ( status <> 200 ).
    >>>>>
    raise communication_error.
    24
    endif.
    25
    26
    27
    endmethod.
    Not sure how to solve this since couldn't find any relevant notes.
    Thanks

    Hi KZ,
    i've run the CRMS_IC_CHECK and i got following message:
    Check System Settings and Status
    TIME:      09:33:53
       Configuration summary
       Domain:                                       sapdemo.local
       Context Area Style Sheet:
       Scratch Pad Style Sheet:
       Broadcast Style Sheet:
       General
          Server domains are compatible.
          Logical system: CROCLNT100
    The J2EE and HTTP service is running. the CRM_IC is activated. I even got same error when i test the CRM_IC from sicf. Not sure how i can progress further.
    Thanks

  • 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

  • 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

  • Runtime error:  RAISE_EXCEPTION while release invoice doc to accounting

    Hi guys,
    System going to dump (Run time error:  RAISE_EXCEPTION) while releasing  invoice document to accounting.
    In VF02 screen after giving billing document as input value and if you try to release it to accounting then system is going dump and giving the above error. I have checked accounting document number ranges also, apart from this could you pls let me know any clue(functional point of view).
    Thx in advance....regards.......Divakaran.....

    Hi,
    please check whether the latest version (Version 6 from 28.07.2008)
    of SAP Note 1039154 is contained in your system.
    You can check this via transaction SE37 for the function module:
    FI_WT_COPY_DOWNP_INFO.
    The source code should look as follows:
    CALL FUNCTION 'FI_WT_READ_WT_INFO'
      EXPORTING
        I_BUKRS     = i_bukrs
        I_BELNR     = i_belnr
        I_GJAHR     = i_gjahr
        I_BUZEI     = i_rebzz
      TABLES
        T_WITH_ITEM = l_with_item
      EXCEPTIONS
        NOT_FOUND   = 1
        OTHERS      = 2.
    Please ensure that the coding in your system is the same as per the
    source code in note 1039154 if changes cannot be done via snote, then
    the code should be manually added.
    This has solved this issue for others in the past.
    The dump might also caused by FI validation.
    Could you try to deactivate the FI validation by transaction OB28 and retest on the
    issue.
    Cheers,
    Alex

  • Error while executing Tranx CRM_IC

    Hi All,
    I am getting following error while executing  CRM_IC
    The runtime repository could not be interpreted
    An exception occurred during the internal HTTP communicationException Class CX_BSP_WD_HTTP_RESPONSE_ERROR
    Text: The HTTP Response Had the Status 401.
    Additional Info: Unauthorized
    Program: CL_BSP_WD_STREAM_LOADER=======CP
    Include: CL_BSP_WD_STREAM_LOADER=======CM002
    Source Text Row: 131
    Has anybody encountered this problem before.
    Thanks and regards
    Atul Anand

    Hi Atul,
    the following SAP Notes might be helpful:
    [1260445|https://service.sap.com/sap/support/notes/1260445] Response display for errors in internal HTTP communication
    [1144511|https://service.sap.com/sap/support/notes/1144511] Blank screen when starting CRM WebClient or IC WebClient
    [1118327|https://service.sap.com/sap/support/notes/1118327] Exception CX_BSP_WD_HTTP_RESPONSE_ERROR when starting the IC
    Best regards,
      Andreas

  • Urgent :crm_ic web client adding new field - customer external number-BPEXT

    HI
    I want to add the field <b>customer external number(data element- bpext)</b> is available as a standard  field in  <b>bp transaction</b> , under indentification tab I am trying to bring the same field into the <b>identify account-CRM-IC BSP Application</b>
    when I am trying to do this , I nee to know the below information
    <b>Attribute name
    property name
    context class</b>
    can you help me in Identifying this values which I feel is must for adding the field to the bsp application CRM_IC.
    thanks in advance
    Message was edited by: madhu satya rajasekhar bobbadi

    Hi,
    Following are the steps to add new fields to the existing view.
    - Create a new controller class (ZCL..) with original view class as super class
    - Create new BSP application with View and Controller
    - Attach the above Z class to the view and controller created and activate the BSP appln.
    - Go to transaction BSP_WD_WORKBENCH and type your BSP appln.
    - Expand your controller and at the Context class use Wizard to create new context node and bind this to Custom Controller class available.
    This whole process requires complte understanding of View, Controller, Custom controller and basic custom modifications to IC Web Frame work.
    Kunda Krishna Kishore

  • Runtime Dump: FRONTEND_ERROR : RAISE_EXCEPTION

    Hi,
    We are getting a Runtime Dump RAISE_EXCEPTION in production.
    I know this error, but the error is occuring in function module "WS_QUERY".
    It is raised at line 265..
    It seems to be some error with the Operating system. I am not sure.
    Below is the extract from dump:
    Error analysis
        A RAISE statement in the program "SAPLGRAP" raised the exception
        condition "FRONTEND_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.
    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" " "
    "SAPLGRAP" or "LGRAPU32"
    "WS_QUERY"
    or
    "SAPLGRAP" "FRONTEND_ERROR"
    or
    "RAIMRECH " "FRONTEND_ERROR"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
      Program............. "SAPLGRAP"
      Screen.............. "SAPMSSY0 1000"
      Screen line......... 6
    Information on where terminated
        Termination occurred in the ABAP program "SAPLGRAP" - in "WS_QUERY".
        The main program was "RAIMRECH ".
        In the source code you have the termination point in line 266
        of the (Include) program "LGRAPU32".
    I have searched on OSS Notes, but could not find any related notes.
    Please guide.

    Hello,
    Are you scheduling any program in background which is calling ws_query? WS_QUERY is only used to excute files in the presentation server and will not work in the background
    Vikranth

  • RAISE_EXCEPTION

    Hi ,
    We are getting the runtime error " RAISE_EXCEPTION" in BW3.5 production server.
    Error analysis
        A RAISE statement in the program "SAPLSDD1" raised the exception
        condition "DB_ERROR".
        Since the exception was not intercepted by a superior program
        in the hierarchy, processing was terminated.
        Short description of exception condition:
        Error when creating on the database.
        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
        You may able to find an interim solution to the problem
        in the SAP note system. If you have access to the note system yourself,
        use the following search criteria:
        "RAISE_EXCEPTION" C
        "SAPLSDD1" or "LSDD1U02"
        "DD_CREATE_INDEX"
        or
        "SAPLSDD1" "DB_ERROR"
        or
        "RSPROCESS " "DB_ERROR"
        If you cannot solve the problem yourself and you wish to send
        an error message to SAP, include the following documents:
    Could you please let me know how to rectify the error.
    Thanks in advance.
    Cheers,
    Jena.
    Edited by: Subhadip Jena on Jul 29, 2009 9:54 PM

    Hi Subhadip,
    I think OSS Note Link: [1049615 - Exception condition "DD_ERROR" in RSDU_CLUSTER_FACT_ADA] is relevent for your problem.
    As per SAP Note SP 21 resolves this issue.
    Thanks,
    Digesh Joshi

  • Regarding CRM_IC

    hi
    i got the dump error in my production server i.e runtime error ITAB_DUPLICATE_KEY while accessing CRM_IC
    SAP-Release 700
    Application server... "idescrm"
    Network address...... "172.17.80.100"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "IDESCRM"
    Database type..... "ORACLE"
    Database name..... "IDC"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jun 11 2007 00:13:41"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 114
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
      NT 6.0"
    we are not able to access ICWC through the t-code CRM_IC
    we have the IE-7
    plz do the need full
    with regards
    shankar

    Hello Shankar,
    You get this dump probably because you have duplicate entries in one of your Design Time (DT) or RunTime (RT) XML files.
    The XML files are used to define all navigational links, views, viewsets and so on.
    Check those files for duplicate entries (e.g. A navigational link was declared twice).
    Check your runtimeprofile and see the starting point of your RT definition (by default this is in CRM_IC_RT_REP BSP application, file CRM_IC.XML) and run through all the XML includes and look for duplicates.
    I had exactly the same problem a while ago, I do remember finding the name of the incorrect XML file through debug. (Check the dump file to find a location from where to start debugging)
    Hope this solves your problem!
    Regards,
    Joost

  • Inbox Search of Status for Service Order in CRM_IC

    Hi all,
    When I am searching for a Service Order status in Inbox search in CRM_IC in the Result List it is not displaying Service Orders which are in same Status. It is displaying the list of Service Orders with different Status like Open, Inprocess, Not Completed etc., Can any body please........with details.
    Points will be rewarded for currect answer
    Thanks,
    Shrik.

    I have never used this function module before, but looking at the coding, I don't think this will serve your purpose.
    I think it might be better to use method(s) from class CL_CRM_DOCUMENTS.
    Via the GET_INFO method you can retrieve the documents you need and using the DELETE method should delete these object. I did use the GET_INFO method etc. but we haven't deleted any objects. But according to the name of the method, it should DELETE the documents.

  • Runtime Errors RAISE_EXCEPTION in "SAPLTAX1" due to  "INPUT_INCONSISTENT"

    Hi Gurus,
    Here i got dump which is Runtime Errors RAISE_EXCEPTION in program "SAPLTAX1" due to  "INPUT_INCONSISTENT",
    will you people please help me to resolve this problem.
    here i past error details,
    Short text
        Exception condition "INPUT_INCONSISTENT" raised.
    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 "SAPLTAX1" raised the exception
        condition "INPUT_INCONSISTENT".
        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.
    Thanks,
    Namdev.

    That message appears to come from FM CHECK_JURISDICTION_ACTIVE.
    It may be a configuration piece is missing:
    IF I_LAND IS INITIAL.
      SELECT SINGLE * FROM T001 WHERE BUKRS = I_BUKRS.
      SELECT SINGLE * FROM T005 WHERE LAND1 = T001-LAND1.
    ELSEIF I_BUKRS IS INITIAL.
      SELECT SINGLE * FROM T005 WHERE LAND1 = I_LAND.
    ELSE.
      SELECT SINGLE * FROM T001 WHERE BUKRS = I_BUKRS.
      IF T001-LAND1 <> I_LAND.
        RAISE INPUT_INCONSISTENT.
      ELSE.
        SELECT SINGLE * FROM T005 WHERE LAND1 = I_LAND.
      ENDIF.
    ENDIF.

  • Runtime errors "Raise_Exception" occur when running crystal report

    Dear all expert,
    I had develop a CR. It is fine and I can run it. but in our remote system, there is a runtime error "RAISE_EXCEPTION" with exception condition "EXECUTION_HALTED". There is no error show to me at CR side where the report is running fine. But I wonder why the is a runtime error in the remote system.
    Thank You.

    Hi Ingo,
    I had check the transport folder in my integration solution installer kit folder. There is only Folder with name "ansi" and "unicode_compatible".
    The readme for my transport file are as below:
    There are two sets of transport files, which can be used with BusinessObjects Enterprise Integration Kit for SAP. One set is ANSI and the other set is Unicode enabled.
    The set of transports you must use depends on the BASIS system your SAP system is running on. Additionally, each transport consists of a data file and a cofile, which are listed in brackets behind the transport names.
    If your SAP system is running on a BASIS system earlier than 6.20, you must use the files listed below:
    (These files are ANSI.)
    Open SQL Connectivity transport (K900084.r22 and R900084.r22)
    Info Set Connectivity transport (K900085.r22 and R900085.r22)
    Row-level Security Definition transport (K900086.r22 and R900086.r22)
    Cluster Definition transport (K900093.r22 and R900093.r22)
    Authentication Helpers transport (K900088.r22 and R900088.r22)
    If your SAP system is running on a 6.20 BASIS system or later, you must use the files listed below:
    (These files are Unicode enabled.)
    Open SQL Connectivity transport (K900574.r21 and R900574.r21)
    Info Set Connectivity transport (K900575.r21 and R900575.r21)
    Row-level Security Definition transport (K900576.r21 and R900576.r21)
    Cluster Definition transport (K900585.r21 and R900585.r21)
    Authentication Helpers transport (K900578.r21 and R900578.r21)
    The following files must be used on an SAP BW system:
    (These files are Unicode enabled.)
    Content Administration transport (K900579.r21 and R900579.r21)
    Personalization transport (K900580.r21 and R900580.r21)
    MDX Query Connectivity transport (K900581.r21 and R900581.r21)
    ODS Connectivity transport (K900582.r21 and R900582.r21)
    The dump "raise_exception" occur when in the Crystal Report Designer.
    Thank You.

Maybe you are looking for