ABAP Runtime Errors

[Stephens, Monique S L]

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