ABAP Runtime Errors

Stephens, Monique S L moniques at bcm.tmc.edu
Fri Jan 19 11:42:14 EST 2001


I forgot to mention that we are in release 4.0B.  I tried SWPC and the
system did not recognize the transaction code.
 
Monique Stephens
 
P.S.  SWI1 may be time-consuming because the status can be anything
(including Complete).
 
-----Original Message-----
From: Loesel Ulrike [mailto:ulrike.loesel at orange.ch]
Sent: Friday, January 19, 2001 10:28 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: ABAP Runtime Errors
 
 
Hi Monique,
 
try transaction SWPC (Continue Workflows after system crash).
I am not sure if it helps but I used it to restart workflows which just
stopped in the middle without an obvious reason.
 
Hope it helps !!!
Ulrike
 
> -----Original Message-----
>> From: Susan R. Keohan [SMTP:skeohan at MIT.EDU]
> Sent: 19 January 2001 17:23
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: ABAP Runtime Errors
>
> Hi Monique,
>
> One way would be to run transaction SWi1 (Work Item Analysis) and look for
> any workitems with Type = W, Status = Ready (or are they in Error ?) , and
> Task = the task that does the approval - with your selection dates.  Then
> the report will return a list of work items, which you can drill down on
> and execute.
>
> But I don't know the scope of documents you are talking about, so this may
> not be the best way.
>
> Good luck!
> Sue
>
> >I need help ASAP.  Yesterday, our users were getting ABAP dumps when they
> >were approving documents.  We determined it was because of the WF table
> >busting at the seams.  We fixed that problem (for now).  However, how do
> we
> >get workflow starting again for all of those documents that are stuck.
> Is
> >there a magic button to push or do I need to know each of the document
> >numbers?
> >
> >Monique Stephens
> >Baylor College of Medicine
> >
> >-----Original Message-----
> >From: Martin P. Weick [mailto:martin.weick at bcm.tmc.edu]
> >Sent: Thursday, January 18, 2001 4:19 PM
> >To: finreport at bcm.tmc.edu
> >Cc: STOUT MELINDA (E-mail)
> >Subject: ABAP Runtime Errors
> >
> >
> >I am not sure which address to send this to, but it needs to be looked at
> by
> >an IBIS expert in the approval
> >process....
> >
> >I need someone to look at three transactions that generated ABAP Runtime
> >errors this afternoon.
> >Our Purchasing Clerk, Melinda Stout had an runtime error page pop up each
> >time while doing three different
> >approval transactions.     The transaction numbers were:
> >
> >190036295 (Melinda was trying to change the charge source on this one but
> it
> >errored out before she could finish)
> >190035820
> >190035828
> >
> >In each case she said that pages of data appeared on her screen,  then
> >automatically went to an error page (which
> >she did a screen shot on.)
> >
> >It showed:   ABAP runtime error DBIF_RSQL_SQL_ERROR
> >              Occured on 01/18/2001 at 15:53:57
> >
> >                SQL error 1653 occurred when accessing table "SWWWIHEAD"
> >
> >When Melinda returned to the Inbox page the documents were gone from her
> >box.   The first one listed above
> >is still charged to the wrong account number and needs to be corrected.
> >
> >We need to know if these documents actually got approved or are in limbo.
> >
> >Thanks,
> >
> >Marty
> >
> >
> >Martin P. Weick
> >Administrator
> >Department of Molecular and Cellular Biology
> >Baylor College of Medicine
> >One Baylor Plaza
> >Houston, Texas 77030-3498
> >Voice: (713)798-4709
> >FAX:  (713)790-1275
> >mweick at bcm.tmc.edu
 


More information about the SAP-WUG mailing list