RAISE_EXCEPTION with exception condition "PARAMETER_INCOMLETE" raised.

Hi,
we are getting this Runtime error daily more than 10 times...please find below details.
Runtime Errors         RAISE_EXCEPTION
Date and Time          2010.09.22 04:04:18
Short text
Exception condition "PARAMETER_INCOMLETE" raised.
Client.............. 700
User................ "TME10X"
Language key........ "V"
Transaction......... "VA01 "
Transactions ID..... "4C97B7A4B90A004DE10080000A281E0C"
Program............. "SAPLZSDCHECK"
Screen.............. "SAPMV45A 4001"
error analysis
   A RAISE statement in the program "SAPLZSDCHECK" raised the exception
   condition "PARAMETER_INCOMLETE".
   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.
Can you please suggest us..
we hope this is related to functional issue.. any suggesions from BASIS end.
regards,
balaram

Hi Balaram,
How did you resolve the problem?Please provide the solution so that I will be helpful for others
Regards
Uday

Similar Messages

  • RAISE_EXCEPTION  with exception condition    "SYSTEM_FAILURE"

    Hi Gurus,
        I got a dump RAISE_EXCEPTION  with exception condition    "SYSTEM_FAILURE" in my system.
        When i check the trace file of the work process dev_w0 , i see the following in it.
    Tue Feb  3 19:47:33 2009
    ABAP Program SAPLOLEA                                .
    Source LOLEAU10                                 Line 352.
    Error Code RAISE_EXCEPTION.
    Module  $Id: //bas/700_REL/src/krn/runt/abfunc.c#16 $ SAP.
    Function ab_jfune Line 2561.
    ** RABAX: level LEV_RX_STDERR completed.
    ** RABAX: level LEV_RX_RFC_ERROR entered.
    ** RABAX: level LEV_RX_RFC_ERROR completed.
    ** RABAX: level LEV_RX_RFC_CLOSE entered.
    ** RABAX: level LEV_RX_RFC_CLOSE completed.
    ** RABAX: level LEV_RX_IMC_ERROR entered.
    ** RABAX: level LEV_RX_IMC_ERROR completed.
    ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    ** RABAX: level LEV_RX_ERROR_SAVE entered.
    ** RABAX: level LEV_RX_ERROR_SAVE completed.
    ** RABAX: level LEV_RX_ERROR_TPDA entered.
    ** RABAX: level LEV_RX_ERROR_TPDA completed.
    ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    ** RABAX: level LEV_RX_END entered.
    ** RABAX: level LEV_RX_END completed.
    ** RABAX: end no http/smtp
    ** RABAX: end RX_GOTO_RABAX
    Exception condition "SYSTEM_FAILURE" raised..
    Could you please guide me what to do when i see the following dump.
    My env is   ECC6 / DB2 /AIX.
    Thanks in Advance,
    Vikram.

    Hi
    i supose this is a GUI Installation error pls install the latest version of SAP GUI version and avalable Patch and clean of the older one
    Thx
    Shilpa

  • APD Failure with  Exception condition "OBJECT_NOT_FOUND" raised.

    Dear All,
    I am executing an APD in my system to clear the contents  of 2 of its Fields in a Master data by loading data to itself and initializing  the 2 fields that needs to be cleared off.
    I have executed the APD  few times and am getting the same error message.
    Any pointers for the same are really helpful.
    Thanks & Regards,
    Ganesh Thota.

    Do a RSRV test for master data object then try to run the APD.

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" 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 "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    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" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    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... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    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. 133 
    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" 
    Memory consumption 
    Roll.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • Runtime error raise_exception (Exception condition "NOT_EXIST" raised)

    Hi,
    I tried to ran a DTP to load data in a Standard DSO. Once I run the DTP ,instantly it is showing me short dump.I tried to ran it 2 times. Every time it shows me dump
    Runtime Errors         RAISE_EXCEPTION
    Short Text : Exception condition "NOT_EXIST" raised.
    Error Analysis : A RAISE statement in the program "SAPLRSSM" raised the exception
    condition "NOT_EXIST".
    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 in advance,
    Regards,
    Snehasish

    Hi,
    This kind of issues occur in BI7.0, the cause is not clear.
    You can once again delete the Data in the DSO using SE14(If Production system, make sure you contact your Basis team for this).
    You will have to use the table names(check the Delete data option & click on Activate and adjust databas)
    Thanks,

  • Exception condition "CONVERSION_ERROR" raised.

    Hi,
    We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.
    Which application raised this exception? Again no clue on the same. Please find the text of the dump.
    Short text
        Exception condition "CONVERSION_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_SWF_CNT_CONTAINER==========CP" raised the
         exception
        condition "CONVERSION_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_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"
        "IF_SWF_CNT_CONVERSION~TO_XML"
        or
        "CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"
        or
        "SAPMSSY1 " "CONVERSION_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... "zacwtbsrv0
        Network address...... "10.27.191.
        Operating system..... "Windows NT
        Release.............. "5.2"
        Hardware type........ "4x AMD64 L
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 9
        Shortdump setting.... "full"
        Database server... "ZACWTBSRV063"
        Database type..... "MSSQL"
        Database name..... "EP1"
        Database user ID.. "ep1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 21 2008 00:12:39"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 157
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 8379680
    Heap.... 0
    Page.... 16384
    MM Used. 8164576
    MM Free. 212256
    User and Transaction
        Client.............. 100
        User................ "WF-BATCH"
        Language Key........ "E"
        Transaction......... " "
      Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"
      Program............. "CL_SWF_CNT_CONTAINER==========CP"
      Screen.............. "SAPMSSY1 3004"
      Screen Line......... 2
      Information on caller of Remote Function Call (RFC):
      System.............. "EP1"
      Database Release.... 700
      Kernel Release...... 700
      Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
      Call Type........... "synchron and transactional (emode 0, imode 0)"
      Inbound TID.........." "
      Inbound Queue Name..." "
      Outbound TID........."0A1BBF4011A4488D408222BD"
      Outbound Queue Name.." "
      Client.............. 100
      User................ "HPRETORIUS"
      Transaction......... " "
      Call Program........."SAPLERFC"
      Function Module..... "ARFC_DEST_SHIP"
      Call Destination.... "WORKFLOW_LOCAL_100"
      Source Server....... "zacwtbsrv064_EP1_00"
      Source IP Address... "10.27.191.64"
      Additional information on RFC logon:
      Trusted Relationship " "
      Logon Return Code... 0
      Trusted Return Code. 0
      Note: For releases < 4.0, information on the RFC caller are often
      only partially available.
    Information on where terminated
        Termination occurred in the ABAP program "CL_SWF_CNT_CONTAINER==========CP" -
         in "IF_SWF_CNT_CONVERSION~TO_XML".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 67
        of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".
    Source Code Extract
    Line  SourceCde
       37     lv_xml_table_req = 'X'.
       38   ENDIF.
       39   IF xml_stream IS REQUESTED.
       40     lv_xml_stream_req = 'X'.
       41   ENDIF.
       42
       43   IF use_xslt NE space.
       44
       45     cl_swf_cnt_conversion_service=>to_xml_xslt(
       46       EXPORTING
       47         container                  = me
       48         include_null_values        = include_null_values
      49         include_initial_values     = include_initial_values
      50         include_change_data        = include_change_data
      51         include_texts              = include_texts
      52         include_extension_elements = include_extension_elements
      53         save_delta_handling_info   = save_delta_handling_info
      54         xml_dom_req                = lv_xml_dom_req
      55         xml_table_req              = lv_xml_table_req
      56         xml_stream_req             = lv_xml_stream_req
      57       IMPORTING
      58         xml_dom                    = xml_dom
      59         xml_table                  = xml_table
      60         xml_stream                 = xml_stream
      61         xml_rendered_size          = xml_rendered_size
      62       EXCEPTIONS
      63         conversion_error           = 1
      64         OTHERS                     = 2
      65            ).
      66     IF sy-subrc <> 0.
    >>>>       RAISE conversion_error.
      68     ENDIF.
      69
      70   ELSE.
      71
      72     cl_swf_cnt_conversion_service=>to_xml_ixml(
      73       EXPORTING
      74         container                  = me
      75         include_null_values        = include_null_values
      76         include_initial_values     = include_initial_values
      77         include_typenames          = include_typenames
      78         include_change_data        = include_change_data
      79         include_texts              = include_texts
    Could you please help me out in resolving this issue?
    Is there any need to apply any OSS notes?
    Thanks in advance. And reward points will be given for the solution..
    Thanks,
    Ravikumar.

    Hi,
    U will receive this error when ever it is not possible to achieve runtime conversion.
    i.e When u r passing the data from one type variable to another type if the conversion is not defined or not possible u will get this dump. Just analyze the dump in ST22.
    Look at this simple example. Here i am trying to assign 101.23 to l_p for which length is not sufficient. So i will get dump. But if u do the same with character variable it will truncate the data.
    DATA: l_p(2) TYPE P DECIMALS 2.
    l_p = '103.23'.
    WRITE l_p.
    So check the place where u r getting the dump. It must be some assignment statement.
    Hope it gave some idea on ur case.
    Thanks,
    Vinod.

  • Exception condition "FAILED" raised.

    My TRM functional consultant has been trying to run end of day processes in the Transaction RKLNACHT but the following dump appears:
    Runtime Errors         RAISE_EXCEPTION                                                             
    Date and Time          16.05.2008 10:33:21                                                         
    Short text                                                                               
    Exception condition "FAILED" 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_POSITIONSERVICE_TRQ========CP" raised the               
         exception                                                                               
    condition "FAILED".                                                                               
    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_POSITIONSERVICE_TRQ========CP" or "CL_POSITIONSERVICE_TRQ========CM00I"                  
        "GET_POSITIONS_BY_DIFF"                                                                               
    or                                                                               
    "CL_POSITIONSERVICE_TRQ========CP" "FAILED"                                                                               
    or                                                                               
    "RKLNACHT " "FAILED"                                                                         
        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... "tetradev"                                                             
        Network address...... "192.168.1.81"                                                         
        Operating system..... "SunOS"                                                                
        Release.............. "5.9"                                                                  
        Hardware type........ "sun4u"                                                                
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "tetradev"                                                                
        Database type..... "ORACLE"                                                                  
        Database name..... "DEV"                                                                     
        Database user ID.. "SAPSR3"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 31 2006 20:59:23"                                                     
        create on........ "SunOS 5.9 Generic_117171-13 sun4u"                                        
        Database version. "OCI_102 (10.2.0.2.0) "                                                                               
    Patch level. 75                                                                               
    Patch text.. " "                                                                               
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."               
        SAP database version. 700                                                                    
        Operating system..... "SunOS 5.9, SunOS 5.10"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 16759392                                                                               
    Heap.... 0                                                                               
    Page.... 180224                                                                               
    MM Used. 10608952                                                                               
    MM Free. 1957592                                                                               
    User and Transaction                                                                               
    Client.............. 300                                                                     
        User................ "DARLINGTON"                                                            
        Language key........ "E"                                                                     
        Transaction......... "KLNACHT "                                                              
        Program............. "CL_POSITIONSERVICE_TRQ========CP"                                      
        Screen.............. "SAPMSSY0 1000"                                                         
        Screen line......... 6                                                                       
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "CL_POSITIONSERVICE_TRQ========CP" -                
         in "GET_POSITIONS_BY_DIFF".                                                                 
        The main program was "RKLNACHT ".                                                                               
    In the source code you have the termination point in line 37                                 
        of the (Include) program "CL_POSITIONSERVICE_TRQ========CM00I".                              
    Source Code Extract                                                                               
    Line       SourceCde                                                                               
    7              l_selector         TYPE REF TO cl_flow_selector_dif,                               
        8      * workarea for table with positions                                                        
        9              l_tab_position     TYPE trqy_position_obj,                                         
       10              l_position         TYPE REF TO if_position_trq,                                    
       11              l_count            type i.                                                         
       12                                                                               
    13      * initialization                                                                               
    14        CLEAR re_tab_position.                                                                   
       15                                                                               
    16      * Get positions for ranges                                                                 
       17        CALL METHOD ca_pos_identifier_dif=>agent->get_persistent_by_range                        
       18          EXPORTING                                                                               
    19            im_context     = trqco_con_trq                                                       
       20            im_ranges      = im_ranges                                                           
       21          RECEIVING                                                                               
    22            re_identifiers = l_tab_identifier.                                                   
       23        CHECK NOT l_tab_identifier IS INITIAL.                                                   
       24                                                                               
    25        LOOP AT l_tab_identifier INTO l_identifier.                                              
       26                                                                               
    27          l_selector = l_identifier->derive_selector( ).                                         
       28                                                                               
    29      *   get TRQ positions for selectors                                                        
       30          CALL METHOD read_positions_by_selector                                                 
       31            EXPORTING                                                                               
    32              im_selector      = l_selector                                                      
       33            RECEIVING                                                                               
    34              re_tab_positions = l_tab_position.                                                 
       35          DESCRIBE TABLE l_tab_position LINES l_count.                                           
       36          IF l_count <> 1.                                                                       
    >>>>>            raise failed.                                                                        
       38          ENDIF.                                                                               
    39          APPEND LINES OF l_tab_position TO re_tab_position.                                     
       40        ENDLOOP.                                                                               
    41                                                                               
    42      ENDMETHOD.                                                                               
    Contents of system fields                                                                        
    Name          Val.                                                                               
    SY-SUBRC      0                                                                               
    SY-INDEX      0                                                                               
    SY-TABIX      2                                                                               
    SY-DBCNT      1                                                                               
    SY-FDPOS      0                                                                               
    SY-LSIND      0                                                                               
    SY-PAGNO      0                                                                               
    SY-LINNO      1                                                                               
    SY-COLNO      1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE      End-of-Day Processing                                                                   
    SY-MSGTY      E                                                                               
    SY-MSGID      64                                                                               
    SY-MSGNO      030                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    SY-MODNO      0                                                                               
    SY-DATUM      20080516                                                                               
    SY-UZEIT      103319                                                                               
    SY-XPROG      SAPLSBAL_DB                                                                             
    SY-XFORM      %_CONTROL_EXIT_DYNPRO                                                                   
    Does anyone have suggestions as to how I can solve this problem?
    Assistance will be appreciated.

    bumping...any suggestions...welcome

  • 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 "PERS_KEY_LOCKED" raised

    Hi All, I'm in entry stage of SD Module, Please help me, I & my computer stuck with a system error
    --Unable to lock Table/view V_TVAK. while going for tcode VOV8 as well as Path.
    --Unable to lock table/view V_TVKO while difining Sales Orgn.
    --Unable....................view T001 while copying co. code.
    not only this 3 but all the screen.
    Unable to open a screen neithor through tcode nor through path, not a single one.
    System suggests some solution but I'm unable to understand it. Please any one guide me. Definitily there is not only reward, award also will nurture. can send solution to my mail Id: [email protected]
    Thanks,
    Sarat
    <b>System shows the error details:</b>
    Run time errors: RAISE_EXCEPTION
    Exception condition "PERS_KEY_LOCKED" raised
    <b>Error analysis:</b>
    A RAISE statement in the program "CL_PERS_ADMIN=============CP" raised the exception Condition "PERS_KEY_LOCKED"
    Since the exception was not intercepted by a superior program in the hierarchy, processing was terminated.
    <b>How to correct the error:</b>
    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
    "CL_PERS_ADMIN=================CP" or "CL_PERS_ADMIN=================CM02"
    "SET_DATA"
    or
    "CL_PERS_ADMIN=================CP" "PERS_KEY_LOCKED"
    or
    "RMOT001K" "PERS_KEY_LOCKED"

    Hi,
    Take a look at the following OSS Notes.
    https://service.sap.com/sap/support/notes/574285
    Hope this helps
    Cheers
    VJ

  • Exception condition "INVALID_POS" raised

    I have thousands of entries stuck in the outbound queue of my ERP system everyday. This is due to a failed transaction. SAP Support told me there is a problem with the P.O. associated with this transaction and that it is OK to delete the offending entry. Once that is done the remaining entries in the queue process until the queue is empty. My question is: "How do I identify the PO transaction that is not working correctly so I can fix the root cause of this problem? Can I correlate the TID from the SMQ1 tcode to a PO number in SRM?
    The entry below shows the error from SQM1 in the ERP system.
    Client  User    Queue     Destination    Date             Time        Status                                                             TID                                              
    123      Batch   QUEUE1 TARGET1       04/10/2015   18:05:19   Exception condition "INVALID_POS" raised. A20915474B805528491F978BD
    Host           Program
    ADBD123   RSM13000
    Next is the partial contents of the corresponding short dump in the SRM system
    Category                ABAP Programming Error
    Runtime Errors         RAISE_EXCEPTION
    ABAP Program           SAPLSXAB
    Application Component  BC-MID-RFC
    Short text
        Exception condition "INVALID_POS" raised.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLBBP_PDH_NOTIFY_FOLLOWON" -
         "BBP_NOTIFY_FOLLOWON_INBOUND".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 66
        of the (Include) program "LBBP_PDH_NOTIFY_FOLLOWONU01".
    Source Code Extract
    Line  SourceCde
       36         i_with_itemdata = ' '
       37       IMPORTING
       38         e_header        = ls_po_header.
       39 *   check for existence and type of PO (extended)
       40     IF ls_po_header IS INITIAL
       41       OR ls_po_header-be_log_system IS INITIAL.
       42       DELETE lt_purch_orders.
       43       lv_invalid_pos = gc_yes.
       44       CONTINUE.
       45     ENDIF.
       46
       47     ls_document_tab-reqno     = &lt;fs_purch_orders>-po_
       48     ls_document_tab-logsys    = ls_po_header-be_log_s
       49     ls_document_tab-core_key  = lv_tst.
       50     ls_document_tab-doc_type  = gc_doc_be_po_call_off
       51     ls_document_tab-guid      = ls_po_header-guid.
       52     ls_document_tab-entrydate = sy-datum.

    Hello Timothy,
    I am dealing with the same issue as I reply to your query using a workaround we got from SAP.
    In addition to what Raghu has added, I want to share that apart from stuck outbound queue in ECC, we also see consistent periodic ABAP dumps in SRM for program SAPLBBP_PDH_NOTIFY_FOLLOWON.
    When I do a search in the ST22 ABAP dump in SRM system, I can find the PO number under the "Chosen Variable" section under the ABAP Developer view. 
    When I display the SRM PO in BBP_PD transaction, I see that field BE_LOG_SYSTEM - Table  BBP_PDBEH is blank and does not have the ECC system value.
    Executing function module BBP_PD_PO_TRANSFER_EXEC by entering SRM PO Header GUID not only updates the missing value in following fields in table BBP_PDBEH
    BE_LOG_SYSTEM
    BE_OBJECT_TYPE
    BE_OBJECT_ID
    but also starts to clear the stuck out bound queue in ECC.
    I am still not sure about the root cause but I know that the problem is because the BE_LOG_SYSTEM field value in SRM table BBP_PDBEH is not updated.
    Regards,
    Mehul

  • Exception condition "TABLE_NOT_EXISTS" raised.

    Hello all,
    when I try to open certain queries in BEx 7.0, I get the following error....
    An error occured while communicating with BI Server.
    As a result of this error, the system has been disconnected from the BI Server.
    Detailed Description:
    Exception condition "TABLE_NOT_EXISTS" raised.
    Any ideas on this? Pls help.
    Thanks,SD

    Laufzeitfehler         RAISE_EXCEPTION
    Datum und Zeit         12.05.2009 14:47:47
    ABAP-Kurzdump ist nicht komplett abgespeichert (zu groß)
    Kurztext
         Ausnahmebedingung "TABLE_NOT_EXISTS" ausgelöst
    Was ist passiert?
         Das laufende ABAP-Programm ist auf eine nicht vorhergesehene Situation
         gestoßen.
    Fehleranalyse
         In dem Programm "SAPLRSDU_PART" wurde durch eine RAISE-Anweisung die Exception
         (Ausnahmebedingung) "TABLE_NOT_EXISTS" ausgelöst.
         Da die Exception nicht durch ein in der Aufrufhierarchie darüber-
         liegendes Programm abgefangen ist, wurde die Verarbeitung abgebrochen.
         Kurztext zur Ausnahmebedingung:
         Tabelle unbekannt
         Eine ausführliche Dokumentation der Ausnahmebedingung finden Sie
         über Transaktion SE37 (Funktionsbibliothek). Den gerufenen
         Funktionsbaustein können Sie der Anzeige der aktiven Aufrufe
         entnehmen.
    Auslösestelle des Laufzeitfehlers
         Programm                                SAPLRSDU_PART
         Include                                 LRSDU_PARTU02
         Zeile                                   47
         Modultyp                                (FUNCTION)
         Modulname                               RSDU_PARTITIONS_INFO_GET
    Ausschnitt Quelltext
    Zeile Quelltext
       17     l_processed       TYPE rs_bool.
       18
       19   l_processed = rs_c_true.
       20
       21 * get name of the DBMS-specific function module .
       22   CALL FUNCTION 'RSDU__FUNCTION_NAME'
       23     EXPORTING
       24       i_function       = 'RSDU_PARTITIONS_INFO_GET'
       25     IMPORTING
       26       e_dbsys_function = l_dbfunc.
       27
       28 * DB-dependent implementation of 'RSDU_PARTITIONS_INFO_GET'
       29   CALL FUNCTION l_dbfunc
       30     EXPORTING
       31       i_tablnm              = i_tablnm
       32     IMPORTING
       33       e_partype             = e_partype
       34       e_partkey             = e_partkey
       35       e_ts_part_info        = e_ts_part_info
       36     CHANGING
       37       c_processed           = l_processed
       38     EXCEPTIONS
       39       table_not_exists      = 1
       40       table_not_partitioned = 2
       41       OTHERS                = rsdu_c_exceptions-inherited.
       42
       43 * generic error handling
       44   CASE sy-subrc.
       45     WHEN 0.
       46     WHEN 1.
    >>>>>       RAISE table_not_exists.
       48     WHEN 2.
       49       RAISE table_not_partitioned.
       50     WHEN OTHERS.
       51       RAISE inherited_error.
       52   ENDCASE.
       53
       54 *----
       55 * DB-independent implementation
       56 *----
       57
       58 ENDFUNCTION.

  • Exception condition "DP_ERROR_GET_DATA" raised.

    Hi All,
    I have a short dump and it looks like this :
    ABAP runtime errors    RAISE_EXCEPTION
           Occurred on     30.10.2008 at 16:46:01
    >> Short dump has not been completely stored. It is too big.
    Exception condition "DP_ERROR_GET_DATA" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    Error analysis
    A RAISE statement in the program "SAPLCNDP " raised the exception
    condition "DP_ERROR_GET_DATA".
    Since the exception was not intercepted by a superior program
    in the hierarchy, 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.
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLCNDP " in
    "DP_CONTROL_GET_TABLE".
    The main program was "SAPLCJSS ".
    The termination occurred in line 118
    of the source code of program "LCNDPU11 " (when calling the editor 1180).
    Source code extract
    000880            TABLES
    000890                 DATA                   = DATA
    000900            CHANGING
    000910                 TABNAME                = TABNAME
    000920            EXCEPTIONS
    000930                 DP_ERROR_INVALID_PARAM = 1
    000940                 DP_ERROR_GET_DATA      = 2
    000950                 DP_ERROR_TYPEMISMATCH  = 3
    000960                 OTHERS                 = 4.
    000970       IF SY-SUBRC NE 0.
    000980         ERRORLEVEL = 3.
    000990       ENDIF.
    001000     ENDIF.
    001010   *CleanUp
    001020     IF NOT SELFCREATED IS INITIAL.
    001030       CALL FUNCTION 'DP_DESTROY'
    001040            CHANGING
    001050                 H_DP   = H_DPLOKAL
    001060            EXCEPTIONS
    001070                 OTHERS = 1.
    001080       IF SY-SUBRC NE 0.
    001090          ERRORLEVEL = 1.
    001100       ENDIF.
    001110     ENDIF.
    001120     CASE ERRORLEVEL.
    001130       WHEN 1.
    001140         RAISE DP_ERROR_CREATE.
    001150       WHEN 2.
    001160         RAISE DP_ERROR_GET_PROPERTY.
    001170       WHEN 3.
    >         RAISE DP_ERROR_GET_DATA.
    001190     ENDCASE.
    001200   ENDFUNCTION.
    Can anyone advice?
    Regards,
    Fred

    Please refer to note 909387...........
    It matches with your Dump......
    Please let me know the outcome.
    Thanks
    Saurabh.

  • 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.

  • Exception condition "T681Z_MISSING" raised

    Hello,
    The SD collegaues are getting following dump while creating an invoice in transaction VF02.I am not able to find any help on SDN or any notes for the same.Please help.
    Short text
    Exception condition "T681Z_MISSING" 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 "SAPLV61Z" raised the exception
    condition "T681Z_MISSING".
    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" " "
    "SAPLV61Z" or "LV61ZF0T"
    "T681Z_SELECT"
    or
    "SAPLV61Z" "T681Z_MISSING"
    or
    "SAPMV60A " "T681Z_MISSING"
    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.
    Regards,

    Hello,
    Thanks for the help.
    I am not an ABAP person but still trying to write what i figured.
    The debugger hints at a sitution wherein a variable "ts_kappl" receives a value 'V' but after an assignment to other variable "available" the value of "available" changes to "0" somewhere.
    This results in a dump on trying to deliver the order for the functional people.
    Can anyone give some idea on this.
    Regards,

  • Short Dump, Exception condition "NOT_EXIST" raised

    Dear Colleagues!
    I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
    I am trying to load data to ODS with full load and filtering via a DTP.
    In the monitoring the load doesn't even get started.
    I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
    I also tried to replicate and active all the rules and objects again.
    And in the source system if I test the extractor it works fine.
    I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
    Hope you can help!
    Regards Silje
    Does anyone have any ideas?
    regards, Uros

    Hi again,
    I tried RSBDELTAREPAIR and it worked!
    Thanks to the forum again!
    Silje

Maybe you are looking for