Skip to Content
author's profile photo Former Member
Former Member

sapsql_array_insert_duprec cx_sy_open_sql_db


i am getting short dump in SAP sapsql_array_insert_duprec cx_sy_open_sql_db



Date and Time 15.07.2011 10:31:32

* *

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


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


procedure "INSERT_TABLES" "(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,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

System environment

SAP-Release 701

Application server... "QAs00"

Network address...... ""

Operating system..... "AIX"

Release.............. "6.1"

Hardware type........ "000A154AD400"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 14

Shortdump setting.... "full"

Database server... "QAs00"

Database type..... "DB6"

Database name..... "QAS"

Database user ID.. "SAPQAS"

Terminal.......... "comput6"

Char.set.... "C"

SAP kernel....... 701

created (date)... "Sep 23 2010 21:55:35"

create on........ "AIX 2 5 00CB5A5B4C00"

Database version. "DB6_81 "

Patch level. 111

Patch text.. " "

Database............. "DB6 08.02., DB6 09."

SAP database version. 701

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"



D ate and Time 15.07.2011 10:31:32

Memory consumption

Roll.... 2755600

EM...... 0

Heap.... 329856

Page.... 0

MM Used. 3034768

MM Free. 26056

User and Transaction

Client.............. 100

User................ "SAPPP"

Language key........ "E"

Transaction......... "MB1A "

Transactions ID..... "4E1F4FF848080084E1008000C0A80A06"

Program............. "SAPLKAUP"

Screen.............. "RSM13000 3000"

Screen line......... 2

Information on where terminated

Termination occurred in the ABAP program "SAPLKAUP" - in "INSERT_TABLES".

The main program was "RSM13000 ".

In the source code you have the termination point in line 464

of the (Include) program "LKAUPF01".

The program "SAPLKAUP" was started in the update system.

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "INSERT_TABLES" "(FORM)", but it was neither handled locally nor


in the RAISING clause of its signature.

The procedure is in program "SAPLKAUP "; its source code begins in line

Please help me .

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 15, 2011 at 08:32 AM


    This dump occurs because the current number of material document is lower than the highest material document number in table MKPF.

    There is a consolidated SAPNote of posting material documents:

    Note 1534887 - Dump SAPSQL_ARRAY_INSERT_DUPREC occurred in program SAPLMBMB

    This will help solve the issue in MB1A Tcode.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Please post the details of the update error. Goto T. Code SM13 and list down all you Updated Error Records.

      Double click on your "Update error record" and then by double clicking on the row showing "Err" you will get the root cause of error.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.