FW: ABAP Runtime Errors

Winfried Winterstein winfried_winterstein at yahoo.com
Tue Jan 23 11:35:51 EST 2001


Hi,
 
for parked documents in FI you can use report RFCORR57
to delete the flag "release necessary". At the same
time the event "FIPP.deleted" will be raised (to stop
SAP workflow templates, if used). Then you can post
the document outside workflow.
 
Hope this helps,
Winfried Winterstein (CSC PLOENZKE)
 
--- "Stephens, Monique S L" <moniques at bcm.tmc.edu>
schrieb: > Since it looks like the OSS note is not the
> solution, I need to have a way
> to find out which documents are stuck in workflow
> without being bombarded by
> users phone calls/e-mails and re-route them
> manually.  I've tried several
> possibilities with SWLD but am not very familiar
> with the process.
>
> When I pull up the documents and go to the linked
> work items, the message
> states "no work items in connection with object...".
>  For purchase orders,
> we can execute ME28 to release the PO.  Is there a
> similar transaction code
> for FI documents in release 4.0B?
>
> Monique Stephens
> Baylor College of Medicine
>
> -----Original Message-----
>> From: SIMON ORCHARD [mailto:ORCHARDS at gkn-whl.co.uk]
> Sent: Tuesday, January 23, 2001 9:48 AM
> To: moniques at bcm.tmc.edu
> Subject: RE: ABAP Runtime Errors
>
>
> Monique,
>
> The program described in the OSS note I gave you is
> a little daunting.
> Firstly, the note states only to create the report
> for version 3.1I, as it
> happens all of the work for 3.1H is also required
> and one of the function
> modules "" should be a Remote Function Call.
>
> I tested the report by crashing our test client, all
> seemed OK apart from
> that the report also checked workflows that were
> complete and correct which
> would extend the run time.
>
> In our Production Client, the report caused mayhem!
> Some of our workflows
> are in the same status as they were before the
> report was run (in progress
> but with all lower level steps completed). A lot of
> workflows had duplicate
> work items, some had gone into error status because
> of role resolution
> errors, some workflows had the required step created
> and in ready status but
> also had steps that should show later in ready
> status as well.
>
> All in all, we had to stop users from using Workflow
> this morning whilst we
> carried out some analysis and start a clean up
> exercise. We have now decided
> to allow the users to use the system and create a
> support call when required
> so that I am driven by the users rather than vice
> versa. Some workflows
> remain dormant for months before the next step can
> be carried out, therefore
> I cannot clean up the system completely and have to
> wait for the user to be
> ready to use the workflow.
>
> Sorry to be the bearer of bad news but;
>
> firstly the note is incorrect, I have advised OSS
> who are now getting the
> notes administrator to correct the note.
>
> secondly, if you are going to create and use the
> report please make sure it
> is tested thoroughly and is only run on the
> production system at the
> quietest possible time with NO workflows being used.
>
> thirdly, expect some odd results and a clean up
> operation to be required.
>
> Sadly workflows can be created in many different
> ways and programmed in many
> different ways, I don't think it would be possible
> for OSS to write a report
> that would work for all of us.
>
> You know my number if you want to call me.
>
> Si
>
> >>> "Stephens, Monique S L" <moniques at bcm.tmc.edu>
> 19/01/2001 22:31:23 >>>
> Did the notes resolve your problem?
>
> Monique Stephens
>
> -----Original Message-----
>> From: SIMON ORCHARD [mailto:ORCHARDS at gkn-whl.co.uk]
> Sent: Friday, January 19, 2001 10:41 AM
> To: moniques at bcm.tmc.edu
> Subject: ABAP Runtime Errors
>
>
> Monique,
>
> What version of SAP are you running?
>
> We are on 3.1I and had exactly the same problem this
> week! The table
> SWWWIHEAD reached it's index and so workflows
> started to fall over. We then
> had workflows "in progress" but all of the steps
> were "complete", there was
> no "ready" step. On OSS I found a note to help
> resolve this for 31G - 31I
> and 40A - 40B, (OSS Note 95859), another note for
> reference is 72873.
>
> Feel free to call me on +44 7968 01 5657.
>
> Regards,
>
> Simon Orchard
> Workflow Support
> GKN Westland Helicopters Ltd.
 
 
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
 


More information about the SAP-WUG mailing list