‎2008 Apr 22 10:59 AM
Hello Friends,
I am getting the dump while creating the delivery .The error details are as follows.
The ABAP/4 Open SQL array insert results in duplicate database record
What happened?
The current ABAP/4 program "SAPLV05I " had to be terminated because
one of the statements could not be executed.
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"
"SAPLV05I " or "LV05IU15 "
"SD_PARTNER_UPDATE"
Source code extract
004500 POSNR = I_XVBPA-POSNR
004510 PARVW = I_XVBPA-PARVW.
004520 IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
004530 I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
004540 I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
004550 I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
004560 I_YVBPA-STCDT <> I_XVBPA-STCDT OR
004570 I_YVBPA-STKZN <> I_XVBPA-STKZN OR
004580 I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
004590 I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
004600 I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
004610 MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
004620 APPEND WA_XVBPA3I TO DA_XVBPA3I.
004630 ENDIF.
004640 ENDIF.
004650 ENDIF.
004660 WHEN UPDKZ_OLD.
004670 IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD OR
004680 DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
004690 YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
004700 ENDIF.
004710 IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD OR
004720 DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
004730 XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
004740 ENDIF.
004750 ENDCASE.
004760 ENDLOOP.
004770 UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
004780 UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
004790
> INSERT (OBJECT) FROM TABLE DA_XVBPAI.
004810 INSERT VBPA3 FROM TABLE DA_XVBPA3I.
004820
004830 IF SY-SUBRC > 0.
Could you please suggest me ,what could be the reason for dump and how to avoid dump?
<REMOVED BY MODERATOR>
Thank you in advance,
Arvind.
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
‎2008 Apr 22 11:08 AM
Hi,
Since I have no idea of SAP release. you should check the following OSS note
Note 760460 - VL10: Runtime error SAPSQL_ARRAY_INSERT_DUPREC in SAPLV05I
Note 767009 - BORGR Short dump w/ error SAPSQL_ARRAY_INSERT_DUPREC (VBPA)
Hope that it will help
Regards
Edited by: Jürgen Degraeve on Apr 22, 2008 12:10 PM
‎2008 Apr 22 12:43 PM
Hello all,
I am using version 4.6C ,the OSS notes mentioned are not useful for me .
Please help me ,it's a bit urgent for me .
<REMOVED BY MODERATOR>
Thank you,
Arvind.
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:17 PM
‎2008 Apr 22 10:24 PM
Hi, have you checked the range numbers for delivery? the transaction is SNUM, object RV_BELEG. If it's overlapped with other range number, it dumps.
Regards.
‎2008 May 09 5:50 PM
Hello, I have very same error
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Transaction......... "VL01N "
Program............. "SAPLV05I"
Screen.............. "RSM13000 3000"
Screen line......... 2
SAP kernel....... 700
Patch level. 75
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
The ABAP/4 Open SQL array insert results in duplicate database records.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
I use SAP_APPL SAPKH60006 Support Package
The NUMBER RANGE OBJECT HAS NO ERRORS!
I went trough the zillions of notes all of them affect the old releases.... Please advice.
Patiently yours,
SAP User
‎2008 May 09 6:09 PM
Hi,
See notes below.
330323
638604
767009
574038
337395
456762
376485
585842
760460
905485
663828
145976
390402
214302
106797
138325
154766
Regards,
Fernando
‎2008 May 09 9:03 PM
Thanks I found that this note fits me: Note# 855434 - Update termination in Transaction VI01 in SD_PARTNER_UPDATE