on 06-24-2008 6:25 PM
While saving purchase orders and some logistics transaction codes ,I am getting an ABAP runtime error
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Details:
The ABAP/4 Open SQL array insert results in duplicate database records. |
The current ABAP program "SAPLSBAL_DB_INTERNAL" 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 "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(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.)
Please give me your suggestions to sort out this problem
Thanks in advance
Hi,
check SAP Note 196113 - SAPSQL_ARRAY_INSERT_DUPREC, BALHDR
regards,
kaushal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daniel,
It would really help if you could at least find out what statement is causing your problem. Is this information not available in the dump? Normally there is an extract of the relevant code showing the statement.
Anyway, I found two SAP notes, 196113 and 1041894, which may have some relation to your problem. At least they both deal with SAPSQL_ARRAY_INSERT_DUPREC occurring in SAPLSBAL_DB_INTERNAL. If they don't help, then I'd suggest that you open a message on the application component because this doesn't sound like an error in the database software. The database is just reporting on an error caused by the application, as far as I can see.
All the best,
Sally Power
Development Support for SAP on IBM i
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daniel.
Looks like there is an OpenSQL statement that tries to insert a record into a database table that is already there. Is this happening in an SAP standard report or in a Z-report? Can you reproduce the runtime error? I would suggest getting an SQL trace to see which specific statement causes the error.
If it's an issue with SAP standard reports most likely you will need to open up a customer message. But perhaps you can give us some more information about this issue. Which SAP release and which database release do you use?
Best regards,
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.