Hi,
how about disabling the foreign key constraint and have a look at the data your insert
statement wants to write?
kind regards
Frank Schimmelpfennig
PHILIPS Semiconductors Hamburg
ATO-Hamburg WT&IT
"Juchem, Matthias"
<[EMAIL PROTECTED]> To: "Anhaus, Thomas"
<[EMAIL PROTECTED]>
Sent by:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
sapdb.general-admin@lists cc: (bcc: Frank
Schimmelpfennig/HBG/SC/PHILIPS)
erv.sap.com Subject: RE: RE:How to
debug DBPROCs?
Classification:
17.09.2002 15:24
> -----Original Message-----
> From: Anhaus, Thomas
> Sent: Tuesday, September 17, 2002 3:13 PM
>
> Matthias Juchem wrote :
>
> >When calling a DBPROC (which does INSERTs), I get an error
> 360 (roreign key integrity violation). But there is no hint
> >_which_ constraint have got violated.
>
> the system variable $ERRMSG should contain the message you
> received from the insert statement.
> if you stop the DBPROC via
>
> STOP($rc, $errmsg)
>
> after the insert error occurred, this message should be
> returned to the caller of the DBPROC.
Well, in my case, it just says "Foreign key integrity violation". I guess there is no
way to get more information, i.e. which foreign key integrity got violated, is there?
Matthias
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
