SAPSQL_ARRAY_INSERT_DUPREC in SAPLV45U for the FOR...

Former Member · ‎09-03-2012

Hi,

I got the below error in Production system and functional consultants have no idea on because of which transaction this happened, please suggest me on this. With this error description able to understand that KONV table is being inserted by duplicate entries.

SAPSQL_ARRAY_INSERT_DUPREC.

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

Regards,

Sri

gouravkumar64 · ‎09-03-2012

Hi,

This dump occurs if the storage of original files is not happening in a Content Server, which is recommended by SAP. You can check this easily if you go to transaction DC10 and check if the flag 'Use KPRO' is set for the used document type.

SAP do not recommend storing such larger files in SAP DB. If you try to store any original in the SAP DB, the file will be stored in the table DRAO. That means you are consuming table space memory. For one original we can have maximum of 9999 rows in the table. To store larger originals in SAP DB more than 9999 rows in the table are needed and this is not possible. That's the reason behind this dump. Storing such huge files inthe SAP DB will also affect the performance of the system while accessing the original.

as per wiki.

Check SAP note 196113 or 1041894 its may be helpful.

Gourav.

Former Member · ‎09-03-2012

Hi Sri,

This type of dump happens when ypou are trying to insert duplicate records with the same primary key in a database table. This is not allowed in RDBMS context. There might be several reason for this.

1. Check the number range for Condition Record and check the current number which should not reside with the number that you see in KONV table ( Condition Record Table ). This can happen if you by mistake transport number ranges or somebody has manually updated the current number in the number range.

2, Some enhancemnt is making it duplicates. See user exits for transaction VF01/02( RV60AFZ* ). Check for recent transport into the production to check if the code in user exist have been chnaged?

3. If above is not applicable please do a search on SAP market place for OSS notes or raise a note with SAP.

Hope this helps.

Regards,

Rudra

SAPSQL_ARRAY_INSERT_DUPREC in SAPLV45U for the FORM KONV_BEARBEITEN