Dump during inbound delivery creation with VL34

Question

Hi,
when I try to create a inbound delivery for a Purchase order item with account assignment Q (project stock) I get the following dump
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          28.07.2010 17:37:10
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 "SAPLV05I" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
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 "SD_PARTNER_UPDATE" "(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.)
Missing RAISING Clause in Interface
     Program                                 SAPLV05I
     Include                                 LV05IU15
     Row                                     1
     Module type                             (FUNCTION)
     Module Name                             SD_PARTNER_UPDATE
Trigger Location of Exception
  Program                                 SAPLV05I
    Include                                 LV05IU15
    Row                                     480
    Module type                             (FUNCTION)
    Module Name                             SD_PARTNER_UPDATE
When I try to create the inbound delivery with VL31N it works fine. I also tried a couple of BAPIs/FMs which gave me the same dump as VL34.
Thanks in advance!!
br
Walter

Answer 1

I also failed to find any OSS note relevant to this.
If you are not using any exits / BADI, there's no standard modification, you should contact SAP AG and their responsibility is to correct the error.
But it may happen that you are using your own logic (via user exit, BADI, standard modification), in this case you have to find out what causes the problem. If the error is becasue of your develoments, then you cannot ask SAP AG to correct the error, if the error is not caused by your developments then it's SAP AG's responsibility.
Please read OSS note 575667 which says that:
The most common cause for this runtime error is an incorrect logic in USEREXIT_SAVE_DOCUMENT_PREPARE or USEREXIT_SAVE_DOCUMENT in include MV50AFZ1.
For this, read also notes 178328 and 415716.
Edited by: Csaba Szommer on Nov 3, 2010 8:49 AM
Edited by: Csaba Szommer on Nov 3, 2010 8:50 AM