cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Error :SAPSQL_ARRAY_INSERT_DUPREC ;

Former Member
0 Kudos

Hi,

This job is canceled every hour Z_RSNAST00_ZORC let me

know if you have any solution !

ABAP DUMP log:

Runtime Error SAPSQL_ARRAY_INSERT_DUPREC

Except. CX_SY_OPEN_SQL_DB

Date and Time 10.01.2008 10:34:47

ShrtText

The ABAP/4 Open SQL array insert results in duplicate database records.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLV45X" 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.

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 "SD_VEDA_UPD"

"(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

Jhony

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

The error states, that an entry should have been made to a table, that has already an entry with the same key. You shoul specify additional details : the table name and the action you were trying to do.

Regards,

Wojtek

Former Member
0 Kudos

Hi,

Please look at this note. Maybe here is the problem.

regards,

Wojtek

Note 49424 - 3.0E: Configuration and Billing Plan / Contract

Note Language: Version: 4 Validity: valid since 02.12.1996

PDF Download Corrections Compare Versions SSCR

Go to SAP Note: Display

Content: Summary | Header Data | Releases | Related Notes

Summary

Symptom

When you change a multi-level configuration where the main item contains, for example, a billing plan (or more generally: business data that is different to the header data), the billing plan of the main item is not found and an incorrect price is calculated.

When saving a sales order with several items, of which one item has configuration data, the following termination can occur: 'sapsql_array_insert_duprec' in the program "SAPLV45X", FORM routine "SD_VEDA_UP".

Additional key words

Pricing, KMAT, Configurable contract, SAPLV45X SD_VEDA_UP

Cause and prerequisites

Program error

Solution

Corrected in Release 3.0F

Source code corrections

Program FV45SFCO, FORM CONFIGURATION_PROCESSING

...

*----


M E H R S T U F I G E S T Ü C K L I S T E -


*

  • Ändern Komponenten nach Ändern Konfiguration

if vbap-cuobj eq *vbap-cuobj. "ändern Konfiguration

perform configuration_change_structure.

perform xvbap_lesen_direkt(sapfv45p) using vbap-posnr

svbap-tabix.

perform xvbkd_lesen_direkt(sapfv45k) using vbap-posnr >>> insert

svbkd-tabix. >>> insert

endif.

  • Ändern Komponenten nach Hinzufügen Konfiguration, vorher war

  • die Position unvollständig bzgl. der Konfiguration

if vbap-cuobj ne *vbap-cuobj and "neue Konfiguration im

not *vbap-posnr is initial and "Verändern / Korrigieren

*vbap-cuobj is initial. "nach Unvollständigkeit

perform configuration_change_structure.

perform xvbap_lesen_direkt(sapfv45p) using vbap-posnr

svbap-tabix.

perform xvbkd_lesen_direkt(sapfv45k) using vbap-posnr >>> insert

svbkd-tabix. >>> insert

endif.

...

Header Data

Release Status: Released for Customer

Released on: 01.12.1996 23:00:00

Priority: Correction with high priority

Category: Program error

Primary Component: SD-SLS-SO Sales Orders

Secondary Components: SD-SLS Sales

Affected Releases

Software

Component Release From

Release To

Release And

subsequent

SAP_APPL 30 300 30E

Answers (1)

Answers (1)

Former Member
0 Kudos

Thanks