Short dump while loading statistics data - 'CX_RSR_X_MESSAGE'

Hi all,
When I am loading statistics data with Init selection,  system gives short dump error. Below is the message-
The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program 'SAPLRRMS' has to be
terminated.
If anyone know the answer please share with me.
Regards,

Hi Preet,
Please find the details of short dump from ST22-
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
     and therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
Regards,

Similar Messages

  • Short dump while loading master data (0material_attr).

    Hi,
    I am experiencing a short dump while loading 0matrial_attr from R/3.
    Name of the runtime error :
    DBIF_RSQL_SQL_ERROR
    program is generating exception at this point.
    ***Try to insert the records into the ODS table
    INSERT /BIC/B0002905000 FROM TABLE L_T_DATA.
    pls help me.

    Hi,
    I am sure I am looking at the proper dump.
    the code I have pasted is the standard code.. which I get to see in the dump analysis.
    ******************************dump 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 "INSERT_ODS"
    "(FORM)"
    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:
    The exception must either be prevented, caught within the procedure
    "INSERT_ODS"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-14400: inserted partition key does not map to
    any partition"
    Internal call code.........: "[RSQL/INSR//BIC/B0002905000 ]"
    Please check the entries in the system log (Transaction SM21).
    system log in SM 21 is below**************
    After the attempt to access a database table the database system has
    returned an error code which indicates that the operation concerned
    could not be performed successfully.

  • Regarding Short Dump While loading data from DB Connect

    Dear All,
    We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
    Runtime Error          PERFORM_CONFLICT_TAB_TYPE  
    Except.                   CX_SY_DYN_CALL_ILLEGAL_TYPE
    What could be the reason for the error that I am getting

    hi,
    Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
    Summary
    Symptom
    When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
    ("X") The row types of the two tables are incompatible.
    ("X") The table keys of the two tables do not correspond.
    Other terms
    transactional InfoCube, SEM, BPS, BPS0, APO
    Reason and Prerequisites
    The error is caused by an intensified type check in the ABAP runtime environment.
    Solution
    Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
    Apply the attached correction instructions.
    BW 3.0B
    Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
    BW 3.10 Content
    Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
    BW3.50
    Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
    The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
    Header Data
    Release Status: Released for Customer
    Released on: 18.02.2004 08:11:39
    Priority: Correction with medium priority
    Category: Program error
    Primary Component: BW-BEX-OT-DBIF Interface to Database
    Secondary Components: FIN-SEM-BPS Business Planning and Simulation
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SAP_BW 30 30B 30B
    SAP_BW 310 310 310
    SAP_BW 35 350 350
    Support Packages
    Support
    Packages Release Package
    Name
    SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
    Related Notes
    693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
    647752 - SAPBWNews BW 3.0B Support Package 20
    601051 - SAPBWNews BW 3.1 Content Support Package 14
    Corrections Instructions
    Correction
    Instruction Valid
    from Valid
    to Software
    Component Ref.
    Correction Last
    Modifcation
    301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
    Attributes
    Attribute Value
    weitere Komponenten 0000031199
    Thanks
    (Activate ODS/Cube and Transfer rules again..)

  • Short dump while displaying cube data in production

    Hi Folks,
    I'm getting a short dump while displaying cube data in production, please suggest
    Thanks and Regards
    Santhosh

    Hi Santosh,
    I'd suggest to follow as per SAP Note: 568768 - Analysis of SQL Errors causing Shortdumps or Error messages. The Note contains precise steps to analyze such an ABAP dump.
    cheers
    m./

  • Getting dump while loading master data

    Hi,
    i am gettin dump while loading master data genrated by copa,
    that gtwa_not_assigned.
    Best regards,
    dushyant.

    hi,
    see weather that master data contain attribute or not,
    if not than un check master data field from the master data attribute tab,
    and than try to load it again.
    Dushyant.

  • Short dump while loading data

    Hi All,
    I am getting this error message while loading data in BW. The eeror message is below:
    Data not received in PSA Table.
    Diagnosis
    Data has not been updated in PSA Table . The request is probably still running or there was a short dump.
    Procedure
    In the short dump overview in BW, look for the short dump that belongs to your data request. Make sure the correct date and time are specified in the selection screen.
    You can use the wizard to get to the short dump list, or follow the menu path "Environment -> Short dump -> In Data Warehouse".
    Removing errors
    Follow the instructions in the short dump.
    When I checked the short dump it is as below.
    ShrtText                                                                               
    An SQL error occurred when accessing a table.                                                                               
    What can you do?                                                                               
    Make a note of the actions and input which 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.                                                                               
    How to correct the error                          
        Database error text........: "ORA-14400: inserted partition key does not map to any partition"         
        Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"                                 
        Please check the entries in the system log (Transaction SM21).                                                                               
    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:                                                           
    How to correct the error                          
        Database error text........: "ORA-14400: inserted partition key does not map to any partition"       
        Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"                                 
        Please check the entries in the system log (Transaction SM21).                               
        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    
        "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                                     
        "GP12DW003276UZE34XM7O2QXLER" or "GP12DW003276UZE34XM7O2QXLER"                               
        "INSERT_ODS"                                                                               
    Can someone suggest me what should I check?
    Thanks in advance.

    Thanks a lot Manga. I did what you told and it gave me this error message.
    Inconsistency: High value for table /BIC/B0000541000: 0002 ; PARTNO value in RSTSODS: 0022          
    So you mean to say once I click on correct error button, it should be good. So after that if do the loading, it should not give me this problem if I am right.
    But can you tell me what exactly does that error message mean? Also is this not an table space issue. I have to wait to correct that error as DBA is currently looking into it.
    Assigned points. Will assign more points if the issue resolves.

  • Short dump while loading data in to Bw using Process Chain.

    got the problem in the Production System.......... I won't get any confirmation from my customer to debug the program in the Poduction.
    In BW I have to load the data every day using the process chain. in the monitor I can't find any problem every thing is working fine. status is green.. and loads the data into ODS successfully. But the job runs more than 6 Hrs and automatically an E-mail is sent to us that the processing takes long time.But it loads the data successfully into ODS.
    Since 10 days everyday we got a mail with the same problem. My customer asked me tTo analyse the problem.
    I check the short dump there I found that due to some problem the program get intrupted.
    <b>the short dump</b>
    ""Lokale Schnittstelle:
    *" IMPORTING
    *" VALUE(I_INFOCUBE) TYPE RSINFOCUBE
    *" EXCEPTIONS
    *" ILLEGAL_INPUT
    *" REQUEST_NOT_CLOSED
    *" INHERITED_ERROR
    DATA: l_s_cube TYPE rsd_s_cube,
    l_t_dummy TYPE rsdri_t_rfcdata,
    l_s_rsapoadm TYPE rsapoadm,
    l_nothing_found TYPE rs_bool.
    get type of cube
    CALL FUNCTION 'RSD_CUBE_GET_ONLY_DB'
    EXPORTING
    i_infocube = i_infocube
    i_objvers = rs_c_objvers-active
    i_with_atr_nav = rs_c_false
    i_with_message = rs_c_false
    IMPORTING
    e_s_cube = l_s_cube
    EXCEPTIONS
    infocube_not_found = 1
    illegal_input = 2
    OTHERS = 3.
    CASE sy-subrc.
    WHEN 0.
    WHEN 1.
    RAISE illegal_input
    WHEN OTHERS.
    RAISE inherited_error.
    ENDCASE.
    In the short dump I observed that the porgram get intrupted at RAISE illegal_input when sy-subrc = 1.
    I have to analyse this. problem........ whay is so happened...............
    Any one of you face the same problem............... if so please let me give your valuble suggestions regarding this.
    Cheers
    sailekha

    Looks like it  reaches the water mark level thats why you are getting message.

  • Short dump while loading data in ODS

    Hi,
    When i scheduled data load for ODS, a short dump was generated with following error:
    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
    "RULE_BASED_MODIFY_RSMONMESS" "(FORM)"
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "RULE_BASED_MODIFY_RSMONMESS"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-01654: unable to extend index
    SAPBD2.RSMONMESS~AXY by 128 in tablespace PSAPBD2"
    Internal call code.........: "[RSQL/INSR/RSMONMESS ]"
    Please check the entries in the system log (Transaction SM21).
    Please suggest what needs to be done.

    Hi Sneh,
    This is table space issue.
    You need to contact basis guys to get it resolved.
    Take a screen shot of this error and send the information to basis guys.
    Once they clear the problem. repeat the step.
    Hope this helps,
    Sri.....

  • Regarding short dump while loading data

    Hi All,
    I am loading data using 0FI_GL_4. This is a periodic load which was working fine till March. There are lot of postings that happened in April and period was open till 20th. Now when I am trying to load that for 12th period April. I am getting the following error "ABAP/4 processor: DBIF_RSQL_SQL_ERROR" in short dump.
    This is the 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        
    "BWFIR_READ_BSEG_CPUDT_DATA" "(FUNCTION)"                              
    I am tried to load data 5 times till now and every time I am getting the same error. I checked with Basis people for the DB space and it is fine.
    Why I am suddenly getting this error???

    Hi,
    it looks like an internal table overflow in your source system.
    Try reducing the data_package size of your load or ask your basis guys to have a look on short dump and perhaps increase this memory.
    Try RSA3 in the source system and see if it works with your data_package size values from BW and see if it works. If not reduce the number of records...
    On which plugin release is your system running?
    hope this helps,
    Oliviier.

  • Short Dump while loading data into the GL ODS

    Hello Guyz
    I am getting a database error while loading the GL ODS in BW. I am performing an INIT load, and the error occurs during the activation stage:
    Database Error

    Hello Atul,
            PSAPTEMP has nothing to do with PSA. It is a temporary storage space and is present in all systems.
    You can check this in transaction DB02 if you are using Bw 3.x and DB02OLD if you are using BI 7.0. Once in DB02/DB02OLD, you will see a block which says tablespaces. In this block, there is a push button for freespace statistics, click on it and it will take you to a screen which shows the free space for all tablespaces.
    Hope this helps,
    Regards.

  • Getting short dumps while reading bulky data from excel sheet

    Hi all,
    We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
    SQL 2000) into a unicode based system recently. We are facing two peculiar
    problems for last few days.
    *Problem 1 - *Whenever we want to upload the data from excel sheet, the
    system throws a dump after reading about 400 entries, while last week the
    same system used to read about 8000 entries in a single go.
    *Problem 2 - *Also, whenever we realease a transport requst from development
    containing a lot of changes, the request will reach the quality system but
    without the changes. but if i ll try to import the changes into quality
    system after generating more than one request containing small small
    changes, they get reflected in QAS immediately. Is there any size
    constraint in transporting a request fro DEV->QAS->PRD.
    Please suggest some ways.
    I am pasting the dump (that I am getting while data uploading from Excel).
    ~~~~~~~~~~~~~~~~~~
    Runtime errors
    MESSAGE_TYPE_X*
    Occurred on
    22.02.2008 at
    13:21:02*
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    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
    Short text of error message:
    Control Framework : Error processing control
    Technical information about the message:
    Diagnosis
    An error occurred when the system tried to process the commands
    from the Automation Queue on the presentation server.
    There are several possible reasons for this:
    - The installation of the SAP GUI on the presentation server is
    faulty or obsolete.
    - There is an error in the application program
    - There is an error in the SAPGUI or an integrated control
    Procedure
    1. Make sure that you have imported the appropriate Support
    Package, the current kernel, and GUI patch for the release of your
    System
    2. Check whether the error occurs locally on one or a few PCs, or
    generally on all PCs. Note whether the error only occurs for some
    users, for example because of a specific Customizing setting.
    If it only occurs locally, this suggests an installation problem
    with the PC. Check the installation; if necessary, reinstall the
    software. In the dump, search for the SY-MSGLI field, since it may
    point to the cause of the error.
    3. Activate the Automation Trace (in accordance with SAP Note
    158985).
    4.Start the transaction and continue until the screen immediately
    before the dump.
    5. From the System -> Utilities menu, choose Autom. Queue,
    Synchronous Processing.
    The status bar of the GUI displays the text:
    "Automation synchron flush mode on"
    6. If you now proceed with the application, the short dump will
    display the ABAP call that caused the error; the Automation Trace
    will contain the error on the presentation server.
    7. If necessary, load the short dump and trace files on to
    sapservX, so that SAP can analyze them.
    Message classe...... "CNDP"
    Number.............. 006
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" C
    "SAPLOLEA" or "LOLEAU02"
    "AC_SYSTEM_FLUSH"
    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.
    System environment
    SAP Release.............. "620"
    Application server....... "nhbho930"
    Network address.......... "192.168.0.30"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "NHBHO930"
    Database type............ "MSSQL"
    Database name............ "DEV"
    Database owner........... "dev"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 17 2007 00:18:58"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "196"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 300
    User................ "NHBABAP"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "SAPLOLEA"
    Screen.............. "SAPMSDYP 0010"
    Screen line......... 0
    Information on where terminated
    The termination occurred in the ABAP program "SAPLOLEA" in
    "AC_SYSTEM_FLUSH".
    The main program was "ZBDC_CONTRACT ".
    The termination occurred in line 29 of the source code of the (Include)
    program "LOLEAU02"
    of the source code of program "LOLEAU02" (when calling the editor 290).
    ~~~~~~~~~~~~~~~~~~~~~
    Thank you all.
    Cheers.
    Mitra __.____._

    for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
    You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

  • Short dump while loading demo cubes

    HI
    When I am trying to load data from flat file (using standard datasource, and the file being present in the application server) to SAP DEMO Content cubes, I am getting the following short dump.  I could see the data in PSA.The request remains yellow in the monitor.
    I have searched the sdn and could not find the exact match to my issue.
    Find below the short dump content.
    Short text
        An exception occurred that was not caught.

    Error
    Short text
        An exception occurred that was not caught.
    What happened?
        The exception CX_RSR_X_MESSAGE was raised, but it was not caught anywhere
         along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program SAPLRRMS has to be
        terminated.
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.

  • Short dump while loading Hierarchy flat file

    Hi gurus,
    i am trying to load data from flat file to hierarchy, when i am trying to schedule the InfoPackage its giving message  a dump :-
    "ASSIGN_LENGTH_0" C     
    "SAPLRRSV" or "LRRSVU10"
    "RRSV_INT_CHA_VAL_SPLIT"
    These are the steps i followed.
    1 created a ZINREGION
    2. enabled hierarchy of ZINREGION and included ZINCOUNTRY as external characteristics.
    3.and then created infosource and assigned DataSource and created hierarchy and created InfoPackage.
    4. selected the hierarchy in InfoPackage, which was created by clicking the hierarchy structure in DataSource and transfer structure.
    5.when i scheduled the load in InfoPackage i got above short dump message.
    I FOLLOWED THIS BLOG
    /people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
    thanks
    Sathya Pathapati

    Hi Philippe,
    The processing step, as I could see in the status tab of the monitor, is ".Service API" I am not sure if this is what you are asking for. If not, please let me know what you want me to check for. Below is the description I have in the Status Tab.
    InfoIdocs missing; file system
    Diagnosis
    InfoIDocs are missing. With the file system as source system, the IDocs are created in BW. As this did not happen there was probably a short dump in BW.
    System response
    No end-confirmation arrived in the Warehouse from
    Procedure
    Check the short dumps in BW.
    Check the data in the InfoCube.
    Error Correction:
    If the data was correctly updated in the InfoCube, then it is possible that no InfoIDocs were generated.
    Set the data request status manually to "OK" (green traffic light).
    This error has occured in a standard SAP Program.
    Hi Ravi,
    I am not loading the data to the cube but only to the ODS. I have plans to load the data later from ODS to Cube.
    I am not using the process chains to load the data and anyway, as I am not loading to the cube, I auume the index will not come into picture. Please correct me if I am wrong.
    And, what do you mean by "Split the file". Can you please elaborate?
    Thanks,
    RPK.

  • Short Dump while loading Delta from ODS to ODS

    Hi Experts,
    I have run into a short dump error while loading delta from one ODS to another via a process chain.
    Following is the error message:
    Error analysis                                                                               
    Short text of error message:                                                                 
        Request 0000259294 is not completely activated. Please activate it again                     
    Technical information about the message:                                                     
         Diagnosis                                                                               
    Activation of request 0000259294 has terminated, or is not yet                          
             complete.                                                                               
    System response                                                                               
    Procedure                                                                               
    If the process has terminated, all of the requests that the system                      
             was unabe to activate in the most recent activation process have to                     
             be reactivated before the new requests can be activated.                                
             If you are not able to carry out this activation step, delete the                       
             relevant requests from the administration of the ODS object (on the                     
             Requests tabstrip).                                                                     
         Procedure for System Administration                                                         
        Message classe...... "RSM1"                                                                  
        Number.............. 180                                                                     
        Variable 1.......... 0000259294                                                              
        Variable 2.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
    Can someone help me resolve this?
    Thank you

    Check the status of request SID 259294  in ODS, whether the Activation got completed or not. If not wait till the activation completes.
    If there is any problem in the activation process, correct that complete the activation process and load the ne request that you want to load..
    Regards
    VJ

  • ABAP DUMP while loading master data

    hi Gurus,
                  I am trying to load master data but I am getting the following dump , I cannot infer anything from the Dump message, I would be grateful if anyone could throw some light on it..
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC                                                             
    Exception              CX_SY_OPEN_SQL_DB                                                                      
           Occurred on     11/13/2006 at 13:17:57                                                                               
    The ABAP/4 Open SQL array insert results in duplicate database records.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "CL_RSDMD_UPDATE_MASTER_DATA===CP " 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.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    rror analysis                                                                               
    n 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                                                                   
    aught nor passed along using a RAISING clause, in the procedure "_DB_FIRE"
    "(METHOD)"                                                                               
    ince the caller of the procedure could not have expected this exception   
    to occur, the running program was terminated.                             
    he reason for the exception is:                                           
    f you use an ABAP/4 Open SQL array insert to insert a record in           
    he database and that record already exists with the same key,             
    his results in a termination.                                                                               
    With an ABAP/4 Open SQL single record insert in the same error            
    ituation, processing does not terminate, but SY-SUBRC is set to 4.)                                                                               
    ow to correct the error                                                                               
    he exception must either be prevented, caught within the procedure "_DB_FIR
    (METHOD)", or declared in the procedure's RAISING clause.                 
    o prevent the exception, note the following:                              
    se an ABAP/4 Open SQL array insert only if you are sure that none of      
    he records passed already exists in the database.                                                                               
    ou may able to find an interim solution to the problem                    
    n the SAP note system. If you have access to the note system yourself,    
    se the following search criteria:                                                                               
    APSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC                                
    L_RSDMD_UPDATE_MASTER_DATA===CP " or "CL_RSDMD_UPDATE_MASTER_DATA===CM00Y "  
    DB_FIRE"

    one of the response says " In the infopackage set processing as 'Only PSA' and tick the checkboxes for 'Update subsequently in data targets' and 'delete duplicate records'.then try to reload."
    I do not find the Delete duplicate records check box in the IP...cananyonepls tell me where to find thid check box?
    thanks

Maybe you are looking for