SAPSQL_ARRAY_INSERT_DUPREC Error

Hello all,
I am getting the dump "SAPSQL_ARRAY_INSERT_DUPREC" in RSA3 (Extract checker) while selecting GL Account hierarchy from F4, can anyone explain me the reason for this?
Where can i see all the GL Account hierarchies in ECC System.
Thanks in Advance.
Sathish T.

HI,
reagrding the second part of your question, tables SETHEADER, SETNODE, SETLEAF store all the group information (hierarchy nodes, hierarchy relationsship, account numbers within hierarchy nodes).
For account groups SETCLASS is 0109.
Best regards, Christian

Similar Messages

Getting "SAPSQL_ARRAY_INSERT_DUPREC" error while creating a new layout

Hi,
I deleted a layout from a level. When I tried to create a new layout with the same technical name, I was getting a run time error.
Name of the error : SAPSQL_ARRAY_INSERT_DUPREC
Exception : CX_SY_OPEN_SQL_DB
I went to ST22 and analyzed the dump. I found that the entries for the layout that I deleted were still present in the following 2 tables:
1) UPP_PARAMT
2) UPP_ELEMT
My questions are:
1) Is there any possibilities that I can retrive the layout that I deleted with the help of the entries present in the above tables?
2) Can I remove the entries from these two tables so that I can create a new layout with the same technical name?
Thanks,
Seetharaman V

Hi Matt
Thanks for your comments. I was getting this error while trying to save the new layout i created and not during the creatiion.
Thanks,
Seetha

IC intermittent SAPSQL_ARRAY_INSERT_DUPREC error after changing business partner

Hello,
after upgrading from CRM5 to CRM7 (Service for Employee), our Interaction Centre users started getting intermittent SAPSQL_ARRAY_INSERT_DUPREC screen dumps when clicking on the 'Save' button after having changed a partner number in the Partners Table of a Service Ticket.
On encountering one of these screen dumps, the user then has to close their IC session and then restart it - after which it is then possible to successfully 'Save' the same change to the same business partner on the same Service Ticket.
I have not been able to reproduce this error due to its intermittent nature.
Details of the source code extract from the ST22 dump is given below.
Has anyone else encountered such an issue themselves?
thanks,
Martin
Category ABAP Programming Error
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
ABAP Program SAPLCOM_PARTNER_DU
Application Component CRM-BF-PD
Date and Time 20.08.2014 11:15:25
Line SourceCde
41 * data definitions
42 DATA: BEGIN OF ls_attribute_record_to_use,
43 partner_guid TYPE crmt_partner_guid,
44 values TYPE text255. "has to be as long as the longest
45 "attribute structure
46 DATA: END OF ls_attribute_record_to_use.
47
48 DATA: lt_attribute_records_to_use LIKE SORTED TABLE OF
49 ls_attribute_record_to_use WITH UNIQUE KEY partner_guid,
50
51 lv_tablename TYPE tabname,
52 ls_attribute_record TYPE crmt_partner_attr_du,
53 lv_name TYPE char64.
54
55 FIELD-SYMBOLS: <values> TYPE ANY,
56 <address> TYPE crmt_partner_address,
57 <fs_insert_record> TYPE crmd_partner,
58 <fs_addr_ref_data> TYPE crmt_partner_address_reference.
59
60 FIELD-SYMBOLS: <wa_to_proceed> TYPE ANY,
61 <table_to_proceed> TYPE ANY TABLE.
62
63 DATA: wa_to_proceed TYPE REF TO data.
64 DATA: lt_wa_table TYPE REF TO data.
65
66 *** MAINTAIN PARTNER RECORDS *******************************************
67
68 *** records to insert
69 IF NOT it_partner_records_to_insert IS INITIAL.
70
>>>>> INSERT crmd_partner FROM TABLE it_partner_records_to_insert.
72 IF sy-subrc NE 0.
73 MESSAGE a002(com_partner) WITH gc_object_name_partner.
74 ENDIF.
75
76 ENDIF.
77
78 *** records to delete
79 IF NOT it_partner_records_to_delete IS INITIAL.
80 DELETE crmd_partner FROM TABLE it_partner_records_to_delete.
81 IF sy-subrc NE 0.
82 MESSAGE a002(com_partner) WITH gc_object_name_partner.
83 ENDIF.

Hello Atul,
thanks for your message. I have had a look at the SAP notes that you have pointed me to, however they unfortunately do not relate to the functionality where we are encountering this problem:
1914117 - Relates to Sales (not Service {Employee})
1823316 - This error occurs in the wrong FM (BUR_BUPR_UPDATE) rather than FM COM_PARTNER_UPDATE_DU.
1809361 - Relevant for the SAP GUI transaction, 'BP', not the Interaction Centre which iswhere this error is occuring.
SAP have not been able to help because of its intermittent nature, it is not possible to create this error on demand, and as I am working on a secure site SAP cannot open a remote connection.
thanks,
Martin

SAPSQL_ARRAY_INSERT_DUPREC error in ST22

Dear all,
We have CI and 2 Dialog instanence in Prod Environment .
Oracle 10g , AIX and Ecc6.0 .
past 2 days i am getting the below error on Application 1 error .
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          05.05.2010 00:30:57
Short text
     The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSLIM_CNT" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
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.
Kindly suggest me
Regards

Hi,
The dump doesn`t point to any job and the client where it's generated is 000:
User and Transaction
    Client.............. 000
    User................ "SAPSYS"
    Language key........ "S"
    Transaction......... " "
    Transactions ID..... "4BF64BEB79450E9BE1000000C0A84866"
    Program............. "SAPLSLIM_CNT"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "SAPLSLIM_CNT" - in
     "SLIM_CNT_CONSOLIDATE_COUNTERS".
    The main program was "RSUVM018 ".
    In the source code you have the termination point in line 106
    of the (Include) program "LSLIM_CNTU02".
    The program "SAPLSLIM_CNT" was started as a background job.
    Job Name....... " "
    Job Initiator.. " "
    Job Number..... " "
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "SLIM_CNT_CONSOLIDATE_COUNTERS" "(FUNCTION)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLSLIM_CNT "; its source code begins in line
    1 of the (Include program "LSLIM_CNTU02 ".
I've observed the dump in alternate days, not all days and without any periodicity.
I've been looking for SAP notes in sapnet and in forums, but I didn't find anything similar.
Thank you very much!!!
BR,
Martina

SAPSQL_ARRAY_INSERT_DUPREC error in PM_PARTNER_MAINTAIN

Hi every one.
My problem is as follow:
I create a Quality notification using function GENERATE_NOTIFICATION,and just before I assing a partner using function PM_PARTNER_MAINTAIN.
The problem come when, after that, I try to change the user status of the quality notification using function IQS4_CHANGE_USR_STAT_NOTIF. This do not make the update since a dumb "SAPSQL_ARRAY_INSERT_DUPREC " occurs (This dump occurs in a new call to PM_PARTNER_MAINTAIN into change status function)
This error no occur if I do not call function IQS4_CHANGE_USR_STAT_NOTIF in the program and then i call it manually from SE37.
Thanks in advance for your help.
Regards.

Hi all,
I finally use the function I_CHANGE_STATUS to change the status. This function do not call the function PM_PARTNER_MAINTAIN so the Dump do not occur now.
Thank all.
PD: The link was not useful, It was look for a needle in a barn.

SAPSQL_ARRAY_INSERT_DUPREC-Error while processing COM_PCAT_IMS_FEED_INIT

Hi
Yesterday I started multiple initial replications (CRM 2007) of the same catalog but with different variants at the same time. Two of the jobs were canceled from the system with the message: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Normally I didn't got any error when I was replication a catalog this way.
Does anybody know why this happened?
Regards,
Rico

HI,
We have the same problem , can you please give me an update relating the way you solve it ?
Thanks in advance
Regards

'SAPSQL_ARRAY_INSERT_DUPREC' error while cancellation of credit memo.

Hi,
I'am cancelling a credit memo created through 'Sales Return'.When I save the document it gives the message that billing document is created, but just after sometime it shows 'Error info...   00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC. I've checked SAP notes:208627,154638 and 6080 regarding the mentioned error.
System behaves normally when I cancel an ordinary billing document(cancellation type S1) but when I cancel credit memo (Billing Cancellation type S2) it shows error.Part of the short dump is:
The termination occurred in the ABAP program "SAPLV60U" in "KONV_BEARBEITEN".
The main program was "RSM13000 ".
The termination occurred in line 28 of the source code of the (Include)
program "LV60UF0K"
of the source code of program "LV60UF0K" (when calling the editor 280).
The program "SAPLV60U" was started in the update system.
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "KONV_BEARBEITEN" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLV60U ". Its source code starts in line 11
of the (Include) program "LV60UF0K ".
Source code extract
000010   ***********************************************************************
000020   * Unterroutinen RV-Fakturierung                                      *
000030   *                                                                     *
000040   *                KONV_BEARBEITEN                                      *
000050   ***********************************************************************
000060
000070
000080   *                                                                     *
000090   *       FORM KONV_BEARBEITEN                                          *
000100   *                                                                     *
000110   FORM KONV_BEARBEITEN.
000120
000130     CHECK: OHNE_KONV = SPACE.
000140     XVBRK_TABIX = 0.
000150     LOOP AT XVBRK WHERE UPDKZ NE UPDKZ_NEW.
000160       DELETE FROM KONV WHERE KNUMV = XVBRK-KNUMV.
000170     ENDLOOP.
000180
000190     LOOP AT XKOMV.
000200       KONV       = XKOMV.
000210       BELEG = XKOMV-KNUMV.
000220       IF BELEG-ID = '$'.
000230         PERFORM VBRK_BELEGNUMMER_ERMITTELN.
000240         XKOMV-KNUMV = XVBRK-KNUMV.
000250       ENDIF.
000260       MODIFY XKOMV.
000270     ENDLOOP.
     >     INSERT KONV FROM TABLE XKOMV.
000290     IF SY-SUBRC NE 0.
000300       MESSAGE A100 WITH 'KONV' SY-SUBRC XKOMV-knumv.
000310     ENDIF.
000320
000330   ENDFORM.
000340   *eject
Please help.
Thanks with Regards.
Manoj

HI,
We have the same problem , can you please give me an update relating the way you solve it ?
Thanks in advance
Regards

00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC error in Production

Dear Experts,
I am facing the   problem, with T-code MIRO.
When we try to complete his activity in MIRO, it terminates with error 00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC, but it gives the billing no. Again when we try to display the billing no, it says that the doc no is does not exist.
I have checked with number ranges in FBN1 also, How to change the status to "0" in FBN1 ? Wont it be a problem if we change the status to "0" now in production server..!!!
the update error as follows
1     CKML_F_POST_INDEX     V1 (no retry)     Initial
2     POST_DOCUMENT     V1     Initial
3     FI_WT_POST     V1     Initial
4     K_PARKED_DOCUMENT_DELETE     V1     Initial
5     K_DOCUMENT_UPDATE     V1     Initial
6     HFPV_POST_RPSCO_V2     V2     Initial
7     HFPV_POST_RPSCO_V2     V2     Initial
8     G_GLDB_POSTING_A     V1     Initial
9     AC_DOCUMENT_MM_UPDATE     V2     Initial
10     K_OPEN_ITEM_POST     V1     Initial
11     MCE_STATISTICS_UPD_V2     V2     Initial
12     ME_UPDATE_INVOICE     V1 (no retry)     Initial
13     MRM_INVOICE_DOCUMENT_POST     V1     Error
14     SD_SCD_IV_SELCRITERIA_SAVE_DB     V1     Initial
15     SWE_EVENT_CREATE_IN_UPD_TASK     V1     Initial
Error details
00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Kindly suggest me the way how to do it..
Thanks
Priya

Hi,
please check the numer ranges for the Billing Document in SPRO.
I guess there is something wrong with it.
The error occurs if you want to save a Billing document and the primary key for the number still existists in the database. Are you using internal number range?.
Have you changed the number range especially the current number manually?
Perhaps it has something to do with your activities from this thread.
How do I change invoice numbering.
Have you transported the number range object?
Thanks.
Deepak Sharma

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

Delivery gets created in VL01N - Return scenario even after error message

Hi,
I am having following issue explained in details in steps -
We have a service return scenario and following steps have been followed in ECC.
Material code used in this case is batch managed material.
Step 1 u2013
We have created a sales order(VA01) with document type ZRE(Itu2019s a kind of return order). This return order actually coming from CRM.
Step 2 u2013
We are creating delivery using VL01N transaction for return order.
Step 3 u2013
We avoid giving batch number in VL01N and try to save the delivery document. System prompt error saying u201CEnter batchu201D. Subsequently we press return keys to cancel the error message and try to come out of the transaction.
Step 4 u2013
Instead inputting batch number, we try come out of the document creation step.
Step 5 u2013
We go to document flow button of sales order and we could see the delivery created although we came out of the delivery creation process after the error message, without saving the document.
Also note instead of coming out of the document creation, if we again try to save the document, system throws update termination with a reason saying u201CError info... ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPRECu201D, which is quite obvious as system has already created the delivery and we are trying to create / save the document once again in VL01N
We are in dilemma now.
What is the cause of this abnormal behaviour? I don't know.
Any one experienced this, feedback is appreciated,
Regards,
Dipak

Hi,
The SAPSQL_ARRAY_INSERT_DUPREC error is not bothering me much.
My worry is once "Enter batch" error message comes, I am not interested to create the delivery any more.
So I come out of the transaction by pressing return key.
Now when I press return key, system gives me the delivery number, this should not be the case as message given was an error message.
If I go to the SE16N, I could see the delivery number in database.
Also system prompts me to save the delivery which I am not interested to do, just I want to come out after error message.
What could be the reason, I don't know. Ever after error message system gives you the delivery.
Which is very strange.
Any input is apprecited,
Regards,
Dipak

Error in transports of BI technical content

Hi ,
While transporting BI technical content , we are getting an error 'Program terminated (job: RDDEXECL, no.: 10524800)'
It also giving a dump as follows:
SAPSQL_ARRAY_INSERT_DUPREC
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 "RSZ_P_DB_ELT_SET_IMMEDIATELY" "(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:
    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.)
Kindly advice how this issue can be resolved .

Hi,
When you have the transport request under the tranport queue of the destination System and click to truck to import appear a windows with some tabs, in the last tab appear some checkboxes with diferent options, there are some that talk to overwrite the existing objets, and other talk abou repair. Click this ans try to import.
Sometimes work.
Regards,
Dani

Snote + valid releases

hello,
I am facing SAPSQL_ARRAY_INSERT_DUPREC error msg, and I looked in snote and got this no. 632501
I have downloaded this snote, and can anyone lets me know how I can execute this snote ?
seconldly there is valid releases : 46b 46c and 470, I want to know do my system have to have this status inorder to execute this note ?
Regards,

Hi,
First you need to Download the Note from http://service.sap.com, After downloading goto SNOTE transaction code and Implement the same in the SAP System
Regards
Sudheer

Dump when execute MMPV (Material Ledger is actived)

Hi experts,
This is my scenario:
- We are testing in a Development system (No productive system)
- Material Ledger is actived since 12-2011
- No Material Ledger period end closing made in 12-2011
When we execute MMPV the system shows the dump: SAPSQL_ARRAY_INSERT_DUPREC
We applied the sap note: 1123034 - MMPV: SAPSQL_ARRAY_INSERT_DUPREC error in SAPLMLCCS, but the dump continues.
I checked the table ckmlkev and I saw registers to Company Code 0200 Period 2 and Year 2012, however if I check OMSY transaction, I saw only Company Code 0200 Period 1 and Year 2012.
There is something extra to do?
Thanks in advance for your help,
José Luis

Hi,
This short dump is produced when the system tries to insert a new
entry in table CKMLKEV but a duplicate entry already exists in the same
table.
CKMLKEV indicates in which period which cost component structure is
used for the actual cost component split. CKMLKEV entries are created
by MMPV. Their existance for these periods indicates that the period was
shifted already by MMPV.
What you can do now is the following: please check the period
status in ML.
If the status is undefined, then delete the CKMLKEV entry and re-run
MMPV.
If the status is period opened (or higher), then you have to reset
the MM period.
Best Regards,
Arminda Jack

To change the shipTo party.

Hi ,
We have a requirement that we have to change the shipTo party in B2C.
We are changing the business partner to a common BP ,but that BP number is not getting while we are calling change ship to address in the check out page.
Can anyone suggest which FM is giving the shipto party number to the front end while we are calling the change shipto address in the checkout page.
How we can pass the newly modified shipto number to the front end after registeration.
Thanks and Regards
shanto aloor

Hi Christian,
I wanted to update you on my findings. The problem was that I was entering more data than required in the import parameters.
To change a partner in a salesorder - shipto in my case - I just had to fill in the partnerchanges table. There is no need to enter the partner information again in the partners table which I was populating. I understood this only after debugging the update sessions of VA02 and the BAPI concurrently. My BAPI call was trying to insert the soldto and shipto again resulting in a SAPSQL_ARRAY_INSERT_DUPREC error.
Anyway, since there I searched extensively and found no information on how or what fields to fill to change a partner in a document I thought I will put down the info I gathered. Here is what I found, hopefully it will be useful for someone else.
1. PARTNERS table : Fill this table with any new partner function(s) that you want to associate with the document. For example, you created a salesdoc and now want to associate a salesperson to it. Enter the partner details in the partners table with the appropriate partner function. Do not enter any partner functions already associated with the document in this table
2. PARTNERCHANGES table : If you want to update any of the existing partner functions associated with the document enter the old and new values with 'U' in the updateflag field. You can also disassociate any non-mandatory partner functions with a document by entering the values with a 'D' in the updateflag field.(Disclaimer : I have not tried the delete/disassociation but this is based on the what I saw during the extensive debugging sessions ).
Anyway, I am glad I knew of an impending business request and had the time to research it before it became a formal request. There is not much documentation (if any) on how to use the partners & partnerchanges tables with these BAPIs.
Thanks,
Anu

Reports are dumping after client copy

Hi All,
After client refresh from Production to QA reports which are having mail options are dumping saying that Abap Dump
"SAPSQL_ARRAY_INSERT_DUPREC"
Error due to duplicate record entries, Dump analysis is saying. Could any one revert me back what should be done to this issue.
When I am searching I figured it out to be Make SNRO number range settings should be done, I have no idea about SNRO number rangings, So which piece (Object) of SNRO should be modified to set this same. ?.
awaiting for you reply.
Regards
sas.
Edited by: saslove sap on Oct 25, 2011 8:34 AM

Oops Sorry Gautham ,
None of them is solving my Huge bug.
below is details of the bug, if you can do any help that wwould be great, Mean while I am searching for options:
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          10/09/2011 11:18:01
Short text
     The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPFSSO1" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     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 "SOES_INSARR" "(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,

SAPSQL_ARRAY_INSERT_DUPREC Error

Similar Messages

Maybe you are looking for