topic Re: dump error solution in Application Development and Automation Discussions

dump error solution

Former Member — Wed, 27 Aug 2008 07:31:43 GMT

hi experts,

when we are working with delivery (VL02n),after creating invoice VF01,dump error message is coming " update terminated". we are working on IDES server.

im also providing short dump description.

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

Date and Time 27.08.2008 12:49:35

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

administrator.

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

situation, processing does not terminate, but SY-SUBRC is set to 4.)

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"

"SAPLKAUP" or "LKAUPF01"

"INSERT_TABLES"

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 SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

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 error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"INSERT_TABLES" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "trutechserver"

Network address...... "192.168.1.150"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 80686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 6

Shortdump setting.... "full"

Database server... "TRUTECHSERVER"

Database type..... "MSSQL"

Database name..... "TTS"

Database user ID.. "tts"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Aug 29 2006 00:18:21"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQL_Server_8.00 "

Patch level. 75

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 8176

EM...... 10452240

Heap.... 0

Page.... 0

MM Used. 8902208

MM Free. 1547616

User and Transaction

Client.............. 800

User................ "TRU2SABAR"

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

Transaction......... "VL02N "

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

declared

in the RAISING clause of its signature.

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

397 of the (Include program "LKAUPF01 ".

Source Code Extract

Line

SourceCde

434	ENDIF.
435	Do not write empty CO document headers for parked documents!!
436	--> ugly coding but it looks like that "empty" headers are
437	possible in some circumstances
438	IF GD_PARKED_DOCUMENT = 'X' AND
439	COBK_INS-SUMBZ = 0 AND
440	COBK_INS-ALEBZ = 0.
441	DELETE COBK_INS.
442	CONTINUE.
443	ENDIF.
444	DELBZ setzen
445	COBK_INS-DELBZ = 0.
446	CPUDT/CPUTM setzen
447	IF COBK_INS-CPUDT IS INITIAL
448	OR COBK_INS-CPUTM IS INITIAL.
449	COBK_INS-CPUDT = SY-DATUM.
450	COBK_INS-CPUTM = SY-UZEIT.
451	ENDIF.
452	TIMESTMP setzen
453	IF COBK_INS-TIMESTMP IS INITIAL.
454	COBK_INS-TIMESTMP = GD_TIMESTMP.
455	ENDIF.
456	USNAM setzen
457	IF COBK_INS-USNAM IS INITIAL.
458	COBK_INS-USNAM = SY-UNAME.
459	ENDIF.
460	Aenderungen merken
461	MODIFY COBK_INS.
462	ENDLOOP.
463	.....COBK verbuchen...................................................
>>>>>	INSERT COBK FROM TABLE COBK_INS.
465	noch kein REFRESH fuer COBK_INS -> wird noch fuer ALE gebraucht
466	ENDIF.
467
468	.....ggf. Einzelposten versenden......................................
469	IF NOT ALE[] IS INITIAL.
470	LOOP AT ALE.
471	PERFORM SEND_DOCUMENT USING ALE-KOKRS ALE-BELNR ALE-LOGSYSO.
472	--> COBK_INS, COEP_INS und COEPL_INS werden hier gebraucht!
473	ENDLOOP.
474	REFRESH ALE.
475	ENDIF.
476
477	.....COEP verbuchen...................................................
478	IF NOT COEP_INS[] IS INITIAL AND GB_LATE_COEP_INS <> ON.
479	INSERT COEP FROM TABLE COEP_INS.
480	REFRESH COEP_INS. "REFRESH wird in UPDATE_TABLES gemacht!
481	ENDIF.
482
483	.....COEPL verbuchen..................................................

Contents of system fields

Name

Val.

SY-SUBRC	0
SY-INDEX	0
SY-TABIX	11
SY-DBCNT	1
SY-FDPOS	24
SY-LSIND	0
SY-PAGNO	0
SY-LINNO	1
SY-COLNO	1
SY-PFKEY
SY-UCOMM
SY-TITLE	Update control
SY-MSGTY	E
SY-MSGID	MZ
SY-MSGNO	100
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO	0
SY-DATUM	20080827
SY-UZEIT	124935
SY-XPROG	SAPMSSY1
SY-XFORM	XAB_READ

please provide sloutions for it.

with regards,

bharat

Re: dump error solution

Former Member — Wed, 27 Aug 2008 07:38:03 GMT

Refer OSS Note 960906,782447

Amit.

Re: dump error solution

Former Member — Wed, 27 Aug 2008 07:50:10 GMT

hi amit,

can u explain me how to apply this note.

with regards,

bharat

Re: dump error solution

Former Member — Wed, 27 Aug 2008 07:51:22 GMT

hi bharat

In your program, if you used like this means

Insert dbtab from table itab

change it into

Insert dbtab from table itab accepting duplicates key

i think its because of duplicate entry

regards

deva

Re: dump error solution

matt — Wed, 27 Aug 2008 07:52:58 GMT


> hi amit,
> 
> can u explain me how to apply this note.
> 
> 
> with regards,
> 
> bharat

Transaction SNOTE.

For future reference, if you get a dump in a standard SAP transaction, you should first search OSS (service.sap.com), and if you don't find an answer, raise a call with SAP.

Re: dump error solution

Former Member — Wed, 27 Aug 2008 08:04:02 GMT

hi deva,

it is standard code for vl02n,so im will not have aceess to modify the standard code.so please provide me with any other solution

with regards,

bharat

Re: dump error solution

Former Member — Wed, 27 Aug 2008 08:12:23 GMT

Deva Wrote:hi bharat

In your program, if you used like this means
Insert dbtab from table itab

change it into 
Insert dbtab from table itab accepting duplicates key

i think its because of duplicate entry

regards
deva

WRONG

No Way

Re: dump error solution

Former Member — Wed, 27 Aug 2008 08:14:13 GMT

hi deva,

it is standard code for vl02n,so im will not have aceess to modify the standard code.so please provide me with any other solution 

with regards,
bharat

See above reply of Matthew.

Amit.