Error .....SAPSQL_ARRAY_INSERT_DUPREC

Hi All,
In our developement system,I am facing an error SAPSQL_ARRAY_INSERT_DUPREC in one of the Z program , which when ran in backgrond in goes to dump (job gets canceled) & the dump states the above error.
In my program I am just uploading the data to a custom table, the dump points towards the INSERT statement in the below code.
Later, assuming that there might be duplicate entries getting populated, I used  DELETE ADJACENT DUPLICATES FROM it_toolkit COMPARING ALL FIELDS statement to avoid duplicate entries & then used INSERT statement as below. It worked. But later again after two days the same error occured.
The surprising thing is that, the job gets canelled but at the same time custom table gets updated also. The code as follows :-
IF p_sys_id = c_ck04 OR
   p_sys_id = c_ck02.
  IF c_cntl_complt = c_2 AND ztsifcntl-btchstatus = c_a.
    SORT it_toolkit BY sl_no.
    DELETE ADJACENT DUPLICATES
    FROM it_toolkit
    COMPARING ALL FIELDS.
    INSERT zmm_toolkit FROM TABLE it_toolkit.
    COMMIT WORK.
  ENDIF.
ENDIF.
Could anybody shed light on this ?
Regards
Abhii
Edited by: Abhii on May 3, 2010 12:06 PM

Use
sort it_toolkit by the key fields.
DELETE ADJACENT DUPLICATES
    FROM it_toolkit
    COMPARING ALL FIELDS. "Instead of all fields specify the key fields of the table
modify zmm_toolkit FROM TABLE it_toolkit.
Edited by: Keshav.T on May 3, 2010 3:42 PM

Similar Messages

  • FI-SL error SAPSQL_ARRAY_INSERT_DUPREC during direct posting to the SL.

    I am working on FI- Special Ledger and currently encountering an error:
    I am trying to post journals to the special purpose ledger using a local file where I am encountering the following error:
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC  
    Except.                CX_SY_OPEN_SQL_DB           
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught 
      in                                                                           
    procedure "INS_XXXXXA" "(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:                                              
    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.                                                
    XXXXXA is the custom database table name.
    The form mentioned is a item table for one the special ledger which has been custom defined.
    I have debugged the code and found out the following:
    1. There are two records which needs to be updated to the items table of the ledger.
    2. When I checked the items table the key value (which needs to be updated) doesn't exist currently.
    3. I saw some resolution on the number range definition which i tried to apply but not fruitful.
    Although the new records which needs to be inserted to the database table is not there I am getting the error SAPSQL_ARRAY_INSERT_DUPREC.
    Please let me know of any suggestion to resolve the issue.
    I might have not correctly implemented the solution for the number range.
    Your valuable suggestions will be awarded accordingly.
    Also let me know if anymore clarity is required.
    Kind Regards,
    himansu roy

    Hello everyone,
    Got the issue and resolution.
    The problem was in the custom code the ledger update was happening twice so the duplicate entries were giving dump during the COMMIT.
    Regards,
    Himansu Roy

  • Update terminate : error SAPSQL_ARRAY_INSERT_DUPREC

    We are getting error "SAPSQL_ARRAY_INSERT_DUPREC" while using tcode : VK12 ME13 ME11,
    Error is in function module 'RV_KONDITION_SICHERN_VK13' , form 'KONH_CHANGE" in program "SAPLV13A". I checked OSS notes also but didnot find anything.We using ECC6. Can anybody tell what could be the reason and how to eliminate this.

    Hi Meena ,
    are u running out of Number series ?, i had this kind of errors while i'm creating Delivery documents , then i found out Number ranges are missing ,thats y i got that errors, in ur case , i never seen number ranges for CONDITION records , but still u can cross check with ur function consultants.
    regards
    Prabhu

  • Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

    When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
    [20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
    In sm21 shows message:
    AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
    AB1 > Short dump "070316 205056 sapnw ELDA " generated
    Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
    We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
    The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
    The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
    When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
    Best Regards,
    Rogério

    Hi Ajith
    I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
    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
      "LOG_INSERT_DB" "(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:
    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.)
    Thanks, Raj

  • Runtime error SAPSQL_ARRAY_INSERT_DUPREC  during migo

    Hi Friends,
    When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
    I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
    Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
    Regards,
    Wasim.

    Hello Wasim,
    The common cause of this termination is the material document             
    number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.                                                                               
    So please check if the current numbers are synchronized with the          
    database tables:                                                                               
    OMBT trx x MKPF table                                                     
    OMH6 trx x EKKO table                                                                               
    If it has the same number range the sort dump should not be raised        
    anymore.                                                                               
    The main root causes are:                                                 
    -> when you are transporting number ranges from one client to another;                                                                               
    -> when you face a shut down in your system and you have defined a        
    buffer application server tolerance in transaction SNRO;                                                                               
    -> when you are doing the posting by using BAPI's and for some reason     
    the BAPI failed.                                                                               
    I hope it helps you.                                                      
    Best Regards,
    Fábio Almeida
    MM Consultant

  • Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC in t-code KO02

    Hi Guru,
    I got runtime error in transaction KO02, below i given all the details.
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    (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
        Use an ABAP/4 Open SQL array insert only if you are sure that none of
        the records passed already exists in the database.
        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:
        "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
        "SAPLA02S" or "LA02SF00"
        "INSERT_ENTRIES"
        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.
    The exception must either be prevented, caught within proedure
    "INSERT_ENTRIES" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    Information on where terminated
        Termination occurred in the ABAP program "SAPLA02S" - in "INSERT_ENTRIES".
        The main program was "RSM13000 ".
        In the source code you have the termination point in line 132
        of the (Include) program "LA02SF00".
        The program "SAPLA02S" was started in the update system.
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "INSERT_ENTRIES" "(FORM)", but it was neither handled locally nor
         declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLA02S "; its source code begins in line
        85 of the (Include program "LA02SF00 ".
    Plz tell me if some one have idea to solve this problem,
    Thanks,
    Namdev

    Hi,
    check in the OSS and see if there is any note available:
    e.g.
    Note 78466 - RA_ASSET_MODIFIKATION - SAPSQL_ARRAY_INSERT_DUPREC
    https://service.sap.com/sap/support/notes/78466
    Best regards.

  • Error SAPSQL_ARRAY_INSERT_DUPREC executing infopackages

    Hi,
    When we execute any infopackage with source system R3 the following runtime error is generated:
    Category               ABAP Programming Error   
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB        
    ABAP Program           SAPLEDI1                 
    Short text                                                                         
        The ABAP/4 Open SQL array insert results in duplicate database records.        
    Error analysis                                                                   
        An exception occurred that is explained in detail below.                     
        The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
         in                                                                               
    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(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:                                             
        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.)        
    The line code with the error in this FORM is:
      >>>  INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
    We have simulated correctly all datasources in the source system using t-code RSA3, then we think that the problem is BW and not in the source system.
    Also we removed the PSA and executed the infopackage again, but the same error is showed.
    Please, could you help us?
    Thanks in advance,
    Regards,
    Edited by: dbenitez on Feb 29, 2012 8:58 AM

    Hi Kiran,
    I have checked your links but the problem has not been solved. I think that the problem could be the IDOCs because the line code with error is (program SAPLEDI1):
    >>> INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
    The table EDID4 contents all IDOCs of the system (this table is very big (>150.000.000 records))
    could be a memory space problem? but the messate error is by Duplicated records... I don't know...
    please, could anyone help me?
    Thanks!
    Regards,

  • PR creation ERROR: SAPSQL_ARRAY_INSERT_DUPREC via PS

    When I create a Purchase Requisition via project systems, I get this error ERRO info 00671: Abap/4 processor: SAPSQL_ARRAY_INSERT_DUPREC. I configured a new PR document type and assigned a number range to it, I transported it o QAS and then PRD, I didnt test PS in detail, when I use base unit % there is not problem, but when I use PC and ROL, then I get an Update was terminated ERROR. How do i fix this?
    Please give directive on which transactions or path I have to use to fix it.
    Thank you.

    Hi,
    If you are using some badi or exit, check the process by de activating the same.
    If same results are coming, then check OSS notes applicability in your case. (e.g. 148828, 193580 etc)
    Other wise take help from OSS message, since this problem mainly occures due to program error.
    Regards,
    Manoj

  • Dump error - SAPSQL_ARRAY_INSERT_DUPREC while executing Curr trans task

    Hi all,
    While executing currency translation task in SEM BCS, we are getting short dump - SAPSQL_ARRAY_INSERT_DUPREC. This error appears only for few consolidation units.
    we are on BI7 - SP 17.
    Please help me to sort out this issue.
    Thanks,
    Harry

    Hi,
    Usually, such kinds of errors are either
    1. consequences of inconsistencies )) in the data basis/ConsArea
    or
    2. program bugs.
    If you thoroughly searched for OSS notes and found nothing relevant,
    then,
    most likely, the guilty party is #1 == in this case, regenerate everything that may be relevant for the issue,
    starting from the data streams, data basis, ConsArea and so on.

  • Getting runtime error SAPSQL_ARRAY_INSERT_DUPREC In production

    Hi,
    can somebody help me regarding below issue.i am abaper.
    During SAP technical monitoring it has been noticed
    that there are many System dumps SAPSQL_ARRAY_INSERT_DUPREC other terms in the dump file are SALLZED7, LZED7F01, and UPDATE_TORGUE_TABLE. The user is WF-BATCH and is in a dialogue session. Error Message : SAPSQL_ARRAY_INSERT_DUPREC
    Report : SAPLZED7

    Hello ,
    Thanks for ur reply.
    i am providing detailed dump information , please guide me if anything u get.
    What happened?    The database system detected a deadlock and avoided it by rolling back
        your transaction.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
         in
        procedure "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(FUNCTION)", 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:
        The database system recognized that your last operation on the database
        would have led to a deadlock.
        Therefore, your transaction was rolled back
        to avoid this.
        ORACLE always terminates any transaction that would result in deadlock.
        The other transactions involved in this potential deadlock
        are not affected by the termination.
    How to correct the error
        Database error text........: "ORA-00060: deadlock detected while waiting for
         resource"
        Internal call code.........: "[RSQL/DELE//TOPFLOW/BTANM ]"
        Please check the entries in the system log (Transaction SM21).
        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:
        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "/TOPFLOW/SAPLBDE_ZPRM" or "/TOPFLOW/LBDE_ZPRMU25"
        "/TOPFLOW/BDE_ZPRM_VERBUCHER"
        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
    Information on where terminated    Termination occurred in the ABAP program "/TOPFLOW/SAPLBDE_ZPRM" - in
         "/TOPFLOW/BDE_ZPRM_VERBUCHER".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 26
        of the (Include) program "/TOPFLOW/LBDE_ZPRMU25".
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(FUNCTION)", but it was neither
         handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "/TOPFLOW/SAPLBDE_ZPRM "; its source code begins in
         line
        1 of the (Include program "/TOPFLOW/LBDE_ZPRMU25 ".

  • Runtime errors SAPSQL_ARRAY_INSERT_DUPREC

    Hi Team,
    We are facing daly batch jobs failure while  planned to production order conversion (Programe-PPIO_Entry).I can found following analysis in ST22.Pleas help me to solve this problem.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
         in
        procedure "HEADER_POST" "(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:
        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.
    Can anybody suggest what corrective action do i need to take.
    Thanks in advance

    Hi
    The dump may happen due to incorrect current number in the number range interval.
    e.g. the number range of produciton order, the highest number in the order table, e.g. AKFO, is 1000, but the current number assigned to the number range interval is 900, then the system will assign a new number 901 = 900 + 1 to the new order then the dump comes as the number 901 already exist in table AFKO. Please change the current number to the one higher than the highest number of table, e.g. 1001 then no dump will happen.
    While creating the produciton order, several number range objects other than order number is called so you need check them as well. The SAP note 24097 includes a report which can get the hightest number of tabls for the objects can be checked.
    Here is the detail of the note and the report for your reference.
    Long text
    Symptom
    When you create a production order, the system generates error message:
    "ERROR DURING STATUS_UPDATE" The update was canceled
    ABAP processor: SAPSQL_ARRAY_INSERT_DUPREC;
    The termination occurred in the ABAP/4 program "SAPLBSVU"
    Additional key words
    CO01, CO40, CO41, MD04, VA01, COR1, Create order
    Cause and prerequisites
    The copying of sales order data between clients means that objects were
    transferred with numbers that are higher than the current status of the
    respective number range objects in the target client. When a new order
    is created, number assignment according to the status of the number
    range objects results in double entries.
    Solution
    You must adapt the status of the number range objects according to the
    copied data: In the configuration menu of Master Planning (Transaction
    OLPF) under Master Data -> Order -> Number ranges (Transactions CO80,
    CO81, CO82, CO83, CY89).
    You can transport the statuses of the number range objects from the
    source client of your copied sales order data into the target client.
    However, you should always be careful when changing the number ranges
    since multiple assignment of the same numbers can result in IRREPARABLE
    inconsistencies in your system.
    You should only ever INCREASE the current status of a number range
    object !!!
    You can determine the highest number status of the respective objects
    with attached selection report. For the order numbers, you must note
    that the highest current number status can only be determined correctly
    if no external number assignment was used.
    REPORT DETMAXNO.
    This report determines the highest numbers of order dependent number *
    ranges like order number, confirmation number, reservation number,   *
    operation number, capacity requirement number.                       *
    Attention: the maximum order number determined by this report is     *
               only valid if you only use internal numbers
    TABLES: AUFK, AFKO, AFVC, RESB, KBED.
    DATA:  ORD_MAX   LIKE AUFK-AUFNR,
            CONF_MAX  LIKE AFKO-RUECK,
            CONF_MAX1 LIKE AFKO-RUECK,
            RSNUM_MAX LIKE RESB-RSNUM,
            AUFPL_MAX LIKE AFVC-AUFPL,
            BEDID_MAX LIKE KBED-BEDID.
                                                                      Page 3
    maximum order number
       SELECT MAX( AUFNR ) FROM AUFK INTO ORD_MAX.
       IF SY-SUBRC IS INITIAL.
         WRITE: / 'Max. of order numbers: ', ORD_MAX.
       ENDIF.
    maximum confirmation number
       SELECT MAX( RUECK ) FROM AFVC INTO CONF_MAX.          "operation conf.
       SELECT MAX( RUECK ) FROM AFKO INTO CONF_MAX1.            "header conf.
       IF SY-SUBRC IS INITIAL.
         IF CONF_MAX1 > CONF_MAX.
           CONF_MAX = CONF_MAX1.
         ENDIF.
         WRITE: / 'Max. of confirmation numbers: ', CONF_MAX.
       ENDIF.
    maximum reservation number
       SELECT MAX( RSNUM ) FROM RESB INTO RSNUM_MAX.
       IF SY-SUBRC IS INITIAL.
         WRITE: /'Max. of reservation number: ', RSNUM_MAX.
       ENDIF.
    maximum operation number
       SELECT MAX( AUFPL ) FROM AFVC INTO AUFPL_MAX.
        IF SY-SUBRC IS INITIAL.
          WRITE: /'Max. operation number: ', AUFPL_MAX.
        ENDIF.
    maximum capacity requirement number
        SELECT MAX( BEDID ) FROM KBED INTO BEDID_MAX.
        IF SY-SUBRC IS INITIAL.
          WRITE: /'Max. capacity requirement number: ', BEDID_MAX.
        ENDIF.

  • ABAP runtime errors    SAPSQL_ARRAY_INSERT_DUPREC

    Hi,
    Its a production dump.I know the functionality of this dump.
    But my question is  program [SAPLZED7] in the dump doesn't exist in the system.I am also forwarding details below replated to dump.Please give some hint how to solve it??
    The ABAP/4 Open SQL array insert results in duplicate database records.       
    What happened?
    The current ABAP/4 program "SAPLZED7 " had to be terminated because           
    one of the statements could not be executed.                                                                               
    This is probably due to an error in the ABAP/4 program.                       
    What can you do?
    Note the actions and input that caused the error.                                                                               
    Inform your SAP system administrator.                                                                               
    You can print out this message by choosing "Print". Transaction ST22          
    allows you to display and manage termination messages, including keeping      
    them beyond their normal deletion date.                                      
    Error analysis
    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
    Use an ABAP/4 Open SQL array insert only if you are sure that none of         
    the records passed already exists in the database.                                                                               
    If the error occurred in a non-modified SAP program, you may be               
    able to find a solution in the SAP note system.                               
    If you have access to the note system yourself, use the following             
    search criteria:                                                                   
    "SAPSQL_ARRAY_INSERT_DUPREC"                                                      
    "SAPLZED7 " or "LZED7F01 "                                                   
    "UPDATE_TORQUE_TABLE"                                                        
    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.

    Sometimes, the DUPREC is due to SNRO problem.
    if you have several document type link to the same object number, the program could tries to insert a number already taked
    (I don't look your program)
    Regards

  • CV01n Duplicate entry into kssk error - SAPSQL_ARRAY_INSERT_DUPREC

    I am trying to create a document using cv01n transaction .Upon saving, we get the message saying 'This change is not allowed' and this is followed by an update termination saying SAPSQL_ARRAY_INSERT_DUPREC into table kssk. Any insight into this issue is well appreciated.
    thanks,
    Shareen

    Hi Shareen,
    regarding the mentioned error message please see the SAP note 980124 and 1251623 for help. Further the report RCCLZUOB with table DRAW and class type 017 could be useful to find and correct existing classification inconsistencies.
    Best regards,
    Christoph

  • Update termination error SAPSQL_ARRAY_INSERT_DUPREC with transaction f110

    Hi ,
      When we executed the transaction F110 for payment runs it gave an update termination error "Express document 'update was terminated' ".
    Update was terminated
    Error Info  00671: ABAP/4 Processor : SAPSQL_ARRAY_INSERT_DUPREC
    Could you please anyone suggest me how to overcome this express document error.
    Thanks,
    Saran

    Hi,
    I think u r getting this exception as ur trying to INSERt a record which ia already existing, so try to change the data and Run the tcode.
    Revert back if any issues,
    Reward with points if helpful ,
    Regards,
    Naveen

  • UPDATE ERROR -"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC

    DEAR ALL!
    I am facing the following error while posting goods issue through VL01N and stock posting through MB1C ( m.type 521 without production order ).
    Table COBK is not updated wile doing those trasactions, this cause the runtime error.how to solve this issue?
    I searched SAP notes but problem not yet solved.Kindly go through the following error and give your suggestions.
    Thanks in advance. 
    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
         "INSERT_TABLES" "(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:
        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.)
    Sivasubramaniam,
    SD consultant.

    Hi Siva,
    I am not sure but check your number range assignment for Material doc no. it might have exhausted.
    The menu path is IMG> Materials Management> Inventory Management and Physical Inventory>Number Assignment>Define Number Assignment for Material and Phys. Inv. Docs. (check for your material doc type
    REWARD if it helps you!!
    Regards,
    Ajinkya

  • Runtime Error: sapsql_array_insert_duprec

    Hi Everybody,
    we are working on Trainingsystem for SAP FSCM.
    We are using an IDES System with EhP4 for this purpose.
    We are facing a Runtime Error when creating a new Collection Worklist. TC: UDM_GENWL
    I have found the SAP note: 952367 which fits perectly to our issue.
    But this note is valid only for FINBASIS 600.
    We are working on FINBASIS 604.
    Has anybody an Idea, what we con do here
    Or has experience with this error?
    Thanks a lot in advanced
    Kind Regards
    Oliver

    I think you are trying to insert the record in the table for which there is already an entry exists in the table with the primary key specified.

Maybe you are looking for

  • GR IR ISSUE

    Hi Guru;s Could you please explain me the  procedures to be used for clearing the un cleared open GR/IR balances from the GR/IR account? Thanks Sunitha

  • GL account substitution

    Can GL account be substituted at line item level, using T-code GGB1. I mean the boolean statement doesnt gives the option to select GL account for substitution at 'Line item level', and even if we have added a user exit it is not working for us. Any

  • Home Mac Mini Yosemite Server and Time Capsule

    Hello again, I''m looking to have a Mac Mini Yosemite home server with my dot com pointed to my fixed IP. I have a laptop, an iPad 2 and an iPhone 6 to manage in the beginning. It's mostly to practice skills for employment purposes. If I get the late

  • Cannot synchronise with E61i - tried all the tricks posted on web

    I just got my second Nokia E61i but when I try to synchronise it with my contacts and iCal via Bluetooth I get an error message 'Device is not available or synchronization was cancelled. Close dialogs and applications on the phone and try again". The

  • When openong photoshop cs4- could not complete your request because wrong kind of document

    Hi I've just installed the free trial of photoshop cs4.. with much difficulty! Firstly it was saying please install adobe file exe? which I don't have a clue how to do. But I managed to install photoshop and thought I was getting somewhere, but now i