Hello All,
I am getting lots of dumps in st22 below are the details : -
Dump Name - SAPSQL_ARRAY_INSERT_DUPREC
USER is an technical user - SXRISKEUR
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 "/SAPSLL/SAPLPRPROCID_DB_UPDATE" 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.
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.
or 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 "/SAPSLL/PRPROCID_DB_INS" "(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.)
To process the problem further, contact you SAP system
administrator.
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"/SAPSLL/SAPLPRPROCID_DB_UPDATE" or "/SAPSLL/LPRPROCID_DB_UPDATEU01"
"/SAPSLL/PRPROCID_DB_INS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction S
Restrict the time interval to 10 minutes before
after the short dump. Then choose "System->List->S
(Unconverted)".
3. If the problem occurs in a problem of your own
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the er
actions and input led to the error.
The exception must either be prevented, caught wit
"/SAPSLL/PRPROCID_DB_INS" "(FUNCTION)", or its pos
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following: