topic Re: SQL statement problem with dump in Application Development and Automation Discussions

SQL statement problem with dump

former_member207153 — Tue, 17 Jul 2007 01:03:17 GMT

I had problem using this command :

ABAP runtime errors : DBIF_DSQL2_INTERNAL_ERROR

exec sql.

INSERT INTO COMP_MASTER

(CompNo,CompClass,CompType,Createdby,CreatedOn)

VALUES (:compno,:compclass,:comptype,:sy-uname,:datum )

endexec.

I only encounter this during run in production env but not in dev env.

still figure out whether problem with authorization or not.

How to figure out what is the current problem for this in runtime error log?

Re: SQL statement problem with dump

Former Member — Thu, 23 Aug 2007 09:37:48 GMT

Hi Rudy

The issue with your code is that the CREATEDON field exceedes datetime datatype range value.make the createdon field a 6 character field with value xxyyzz

xx can be any two digit number

yy needs to be month value (less than 12)

zz needs to be date value (less than 31)

Try this out hope it works!!!

Re: SQL statement problem with dump

Former Member — Thu, 23 Aug 2007 09:47:34 GMT

Hi,

This shouldn't be a problem. Check in ST22 it says the statement has encountered stmt like commit work. so it gives a dump there. It doesn't give a dump in the DEV system. I guess this is because u cannot commit work there.

Regards,

Sai

Re: SQL statement problem with dump

Former Member — Thu, 23 Aug 2007 09:50:19 GMT

well you shouldnt do a exec SQL.

Open SQL offers a solution for almost every problem, so i hardly guess your requirement can be fulfilled by using OPEN-SQL only.

at least the error messages should be better then.

Re: SQL statement problem with dump

former_member207153 — Wed, 05 Nov 2008 00:04:10 GMT

case close