Runtime Error is coming in PA40 transaction

Hi All,
When i recorded PA40 transaction using SHDB. When i run this BDC using SHDB transaction it is working fine. when i converted this BDC into report it is giving runtime error. anybody faced this kind of problem . please help me out in this.
Error : Runtime Error
Thanks,
Maheedhar
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 5:43 PM

Can you please tell me ? what is the runtime error you are getting.
the steps to transfer the recording to the program is .
1) save the recording.
2) press back button.
3) select your recording name.
4) click  Program.
5) give the program name startign with Z
6) check transfer from recording.
7) enter.
this is the steps that you have to follow while recording. even then also if you dont get then . please provide me with the runtime error . it would be help ful for me to help you easier.
Cheers,
Shiva

Similar Messages

  • While excise posting, an error is coming "Balance in Transaction  Currency"

    Dear all
    While capital excise posting, an error is coming "Balance in Transaction  Currency" for the capital goods posting.
    During the excise duty posting J1IEX our clint done some manuvall entry for excise duties so
    at the time its 0.01 diffrence is coming in balance thats why we are not able to post the document.
    so please can any one give the solution for this
    regards
    pramod

    hi
    Check Excsie duties in "Excise Duty" Tab at Item Details level.
    Kindly note that all the duties (BED, ECS and SECess) in case of RG23C Part II posting must be in EVEN numbers.
    For e.g. Check whether SECess is 10.63 (ODD No) then make it either 11.00 or 10.64 or 10.62 i.e. EVEN No otherwise during Part II posting it will always show balance of 0.01
    Check how much piase is the difference. Then you can decide how many values to be rounded off.
    To avoid this type of problem better to ensure all amounts ( BED, Ecess and Hr Ecess) are in Even figures.
    hope it clears
    regards
    kunal

  • Runtime Error in BW, in RSA1 transaction

    Hello Boss,
    Iam getting runtime error while activating the info object in RSA1 transaction.
      I got OSS notes also from our basis consultant, plz give suggestion how to rectify this one.
      Even while executing the program iam getting runtime error.
      In this OSS notes they mentioned while u activating DSO u get this runtime error & solutions r given. iam not activating any DSO, activating info object. plz give ur suggestion.

    Hi,
            check in ST22 what exactly is message.. Ask basis to check server space and bg process.
    Abhi

  • Runtime error when trying to execute transaction OB58

    Hi all,
    We have upgraded from SAP system 4.6c to ECC 6.0 . We are facing one error in the FI transaction OB58.
    When trying to delete any finanicial version or trying to create any new financial version , we are getting a runtime error which
    states that " Error when attempting to IMPORT object "X011F". and its giving short dump at this point .The description of the error is :
    Short text
        Error when attempting to IMPORT object "X011F".
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLFAGL_FSV" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
         not caught in
        procedure "FSV_POSITIONS_CONVERT" "(FORM)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        When importing the object "X011F", the component 1 in the dataset
        had a different length from the corresponding component of the
        target object in the program "SAPLFAGL_FSV".
        The length is 4 in the dataset, but 32 in the program.
    Thanks,
    Sumit

    Hi Sumit,
    We Upgraded our system from 4.6C to ECC 6.0 and
    I am facing same error. We applied note 1544367. After applying not also we are facing issue during
    import x011p to lt_x011p
             i011z to lt_x011z
             x011v to lt_x011v
             x011s to lt_x011s
             x011f to lt_x011f   
    from database rfdt(bs) client p_mandt
                                   id p_versn
                            accepting padding
                             ignoring conversion errors.
    You faced same issue after applying note or if you have any solution please let me know.
    Regards,
    Mahesh

  • Runtime error in KEFC Transaction while uploading CSV format file

    Hi Experts,
    This is regarding Runtime Error while executing the KEFC transaction in R3D.
    It is working successfully while uploading the file in Text format. But there is run time error while uploading in CSV format.
    It showing "The transfer was terminated.However,content errors occured" .
    Please provide the solution.
    Thanks in advance.
    Regards,
    Priya.

    Hi,
    To upload a CSV file it is used FM:
    CALL FUNCTION 'TEXT_CONVERT_CSV_TO_SAP'
    EXPORTING
    i_field_seperator = ';'
    I_LINE_HEADER =
    i_tab_raw_data = lt_file
    i_filename = p_filename
    TABLES
    i_tab_converted_data = p_table
    EXCEPTIONS
    conversion_failed = 1
    OTHERS = 2
    Please check what separetor this fm and your file are using. It should be the same.
    Regards,
    Fernando

  • Runtime error in component :IUICMDC while testing

    Hello Experts,
    While testing the BSP Component :IUICMDC, we have facing errors mention below-
    Cannot display view CRM_UI_FRAME/WorkAreaViewSet of UI Component CRM_UI_FRAME
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View TIUICMDC.MainWindow in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    Initialization of view CRM_UI_FRAME/WorkAreaViewSet of UI Component CRM_UI_FRAME failed
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View BSPWD_BASICS/WorkAreaHostViewSet in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    Cannot display view CRM_UI_FRAME/MainWindow of UI Component CRM_UI_FRAME
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View BSPWD_BASICS/WorkAreaHostViewSet in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    Initialization of view CRM_UI_FRAME/MainWindow of UI Component CRM_UI_FRAME failed
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View CRM_UI_FRAME/WorkAreaViewSet in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    Cannot display view Root.htm of UI Component CRM_UI_FRAME
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View CRM_UI_FRAME/WorkAreaViewSet in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    An error occurred during initialization of the application
    An exception has occurredException Class CX_BSP_WD_RUNTIME_ERROR - View CRM_UI_FRAME/MainWindow in component CRM_UI_FRAME could not be bound
    Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
    Source Text Row: 165
    please advice
    regds
    deb

    Hello Hongyan,
    Thnx for the reply.
    When i tried to open the component in dev system, runtime error is coming but while this component is tried in sandbox this error is not there, can you help to find that diffrence.
    One more observation that, RT repository is not loaded in dev while is it sucessfully loaded in sandbox.
    NB: one more request , here we are trying to add po_box into this component but AET not supported.
    Please advice.
    regards
    deb

  • Runtime error while executing CAT2

    Hi All,
    My user is executing the CAT2 as below:
    Going to CAT2
    Given profile as Z001 which allows the multiple employees
    its is giving another screen as "Personal number selection for fast data entry" screen
    Click on Further selections button
    Selecting the cost ceter and transfer to right side
    Selecting the Cost center 012-0088
    Clicking on execute button
    getting the Runtime error
    If she gives the other cost center as 012-0089 or 012-0090, there is no error is showing to her.
    Even for the Cost center 012-0088, i run with my user id , there is no error.
    Can anybody suggest why this runtime error occurs for this standard transaction ?
    Thanks
    Shankar

    HI Sreekanth,
    I am not able to paste the total Runtime error message. If you provide me your own details, i will send as attachement to you.
    About your second question: We are using the profiles. On the basis of the profiles selection we are selecting the multiple employees. It is the normal way of doing by the client. Going to selection screen first and get the cost center to the screen from the  further selections, then we give the cost center and execute. We get the employee names belonging to that cost center. Selecting the employee name there and will go to the hours input screen.
    Here immediatly after giving the costcenter and executing, the user getting the runtime error. But not me
    shankar

  • Runtime error when testing function module 'RSWR_RFC_SERVICE_TEST'

    Hi,
    I'am integrating BIW 3.5 with EP 6.0 according to the report 'RSPOR_SETUP'.I've carried all the steps,but an error on step 12 : system failure during call of function module 'RSWR_RFC_SERVICE_TEST' is there .When I test the connection with function module 'RSWR_RFC_SERVICE_TEST', a runtime error is coming i.e. "<--Localization failed: ResourceBundle='com.sap.engine.services.rfcengine.RFCR'.
    Any help would be highly appreciated.
    Regards.
    Manoj

    Hi Manoj,
    From this I can understand that a critical resource is missing which is required to start the RFC service in Reporting Services Web Runtime. This might be because of incomplete patch deployment. Deploy all the required software component archives related to com.sap.engine.services component and then retry this... I think this should solve the issue.
    Imran...

  • Runtime Error on CJ20n -- SAPSQL_ARRAY_INSERT_DUPREC

    Hi, would like to ask what is the nature and how to resolve this error we've encountered when we're adding a new wbs element.
    "Runtime error u201CSAPSQL_ARRAY_INSERT_DUPRECu201D usually occurs in transaction CJ20N and as a result , the system creates a pending Update on the sap table. "

    Please refer this Consulting note.
    Note 780035 - CN22: Update Termination SAPSQL_ARRAY_INSERT_DUPREC
    In recent time I faced similar problem. When you use any BADI or User exit  for the project structure, at that time your custom code is Hindering SAP Code, due to it sometimes your PS object not able to get the system status or internal object no. At that time these type of error comes.
    For your reference Please go though below thread.
    No object Status is available
    With Regards
    Nitin P.

  • Runtime error while executing New Hire action in PA40

    Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        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                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        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..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         
      149
    * Wird mit Einfuehrung des Headerobjekts obsolet.                                          
      150
      PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                    
      151
        USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                    
      152
    ENDFORM.                                                                                   
      153
      154
    *       FORM RE588I                                                   *                    
      155
      156
      157
      158
    *  -->  T588I_DHDID                                                   *                    
      159
    *  -->  T588I_MOLGA                                                   *                    
      160
    *  -->  T588I_TCLAS                         

    Implement SAP Note 1004280.. your issue if fixed
    If your issue is resolved request you to close the thread or else free feel to touch base
    BR
    Anil

  • Runtime error in PA40

    Hi all
         i am working with PA40 transaction in HR. In that i am getting a runtime error like this, here u can find the detials.
    <b>program name : SAPFP500
    Include name : FP500EFW<u></b>
    Eroor analysis:</u>
    I am getting a error like this 'In a write src to dest+off [ ( len) ] [index i] statement, '"off" contains a target field offset (3) which is larger then the length of the target field "dest". (2).
    this is not allowed.
    Please guide me to get out of this problm..
    Thanks in advance.

    Hi,
    Have you recently upgraded your system or applied upport packs. As this is a standard transaction you better search in OSS and you will find some note to fix it.
    Regards,
    Atish

  • Runtime error in CRMD_SALES_MASS transaction

    Hi Gurus,
    I have to enhance the transaction CRMD_SALES_MASS to add few custom fields to it.
    I am trying to execute the transaction but I keep getting a runtime error in a standard Function Module CRM_SALESORDER_MASS_SELECT that is meant for the MASS Transaction. I have gone through many notes but I could not find anything which is relevant. Please help me with this! Please find the below dump if it can help.
    Runtime Errors         CREATE_DATA_UNKNOWN_TYPE
    Except.                CX_SY_CREATE_DATA_ERROR
    Date and Time          09.12.2010 05:11:12
    Short text
        CREATE DATA: The specified type "CRMT_SALESORD_MASSUPDATE_ITEM
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLCRM_SALES_MASS_UPDATE" had to be terminated
         because it has
        come across a statement that unfortunately cannot be executed.

    Hi Nisha,
    Thanks for the reply.
    I got to know the issue with the function module before I saw the reply. It has something to do with the type that is used in CREATE DATA statement.  The statement at line 51 should have been as below
    CREATE DATA ls_selecttable_ref type (tabname-name).
    but the type mentioned tabname in standard FM is a structure of type MASSTABLESTAB.
    Now I have another question. If we are to implement MASS transaction for Service contracts in CRM how are we supposed to do it? I am talking about SAP GUI and not the WebUI here.
    Regards,
    Mahesh

  • Portal Runtime Error while checking the Transaction in Portal

    Hi all,
    We r in the phase of setting the configuration of Portal. We did the the template installer but when iam checking the transactions in Portal ( System Administration--> Support--->SAP Apllication) , it is throwing me the following error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Missing Property 'ClassName' in property file for layer'Transaction/WinguiSSOLayer'..
    See the details for the exception ID in the log file
    Can anybody help me in this regard.
    Thank in Advance.

    Hi Niyati,
    I guess check through -->
    Under "Personalize > User Profile" the checkbox "Activate Accessibility Feature" must be unchecked!
    as, people earlier also faced this issue and SAP provided this solution.
    Also an alternative solution for this is like --
    Go to:
    <Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\property\Transaction
    and see the content of the 'WebGuiSSOLayer.properties' file.
    One of the entries is ''ClassName'. The value on a 'valid' portal is: com.sapportals.portal.sapapplication.itsdetection.ITSDetectionLayer
    If it's not the case, then go to:
    <Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
    rename the file 'com.sap.portal.appintegrator.sap.par.bak' to 'com.sap.portal.appintegrator.sap.par' open the par file and edit the file ''WebGuiSSOLayer.properties' (add the relevant entry for ClassName).
    Save the file (still with the par extension)
    Restart the portal (if everything is OK then the bak extension will be added to the filename).
    Just try this, hope it works.
    Reward points if helpful
    Regards,
    Shailesh Nagar
    Edited by: Shailesh Kumar Nagar on Jan 22, 2008 7:16 AM

  • While trying to change a BOM with transaction CS02, a runtime error appears

    While trying to change a BOM with transaction CS02, a runtime error appears.
    In intial screen he entered material ,plant BOM usage and date valid from  after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
    Developer trace
    ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
    Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
    Error Code SAPSQL_ARRAY_INSERT_DUPREC.
    Module  $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
    Function HandleRsqlErrors Line 775.
    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 RX_RFC
    In sm21
    Perform rollback
    Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
         Short dump "090618 110101 donalda 11557 " generated
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     18.06.2009 at   11:01:01
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
    one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "RKE_WRITE_CE4__BPS1" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "RKE_WRITE_CE4__BPS1"
    "(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    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:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
    "RKE_WRITE_CE4__BPS1"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.

    Hi ,
    you are getting beacuse u are trying to do mass update to database.
    Please check that below note are applicable to your system.
    Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
    Note 869534 - AFS MRP doesn't work properly with all BOM item categories
    Thanks Rishi Abrol

  • Runtime Error while opening the transaction ME22N

    Hi,
       when am trying to open the transaction ME22Nin Ecc6.0 its showing the runtime error like Assign with Length 0 in the pgm SAPLTAX1 in the Module FIND_TAX_SPREADSHEET.
    than you in advance.

    post your Dump information with           
    Short text
    What happened?

Maybe you are looking for