Using SWI6 Workload Analysis in 4.6C

Raveen Moodley rmoodley at toyota.co.za
Fri Mar 5 05:34:00 EST 2004


Kathleen Hi,
 
SWI6 is a good option when looking into reporting of workflow against a
business object however I've found that it's not very easy for end users
to understand  and requires lots of training. Aside from the object key,
the users would have to know the business object as well to run this
transaction. Further, SWI6  gives the users more info than they require,
from experience most users only want to know with whom their workitem is
currently sitting with.
 
 We have implemented a program "Trace Workflow" based on report RSWIOINS
which seems to solve this problem. Created a program with predefined
button eg "Purchase Requisition" , "Material" ...., then call method
"Find" bases on the button press and submit this to the report.
 
You will find that it's much more user-friendly as it only displays the
workflow header and all it's dialog activities.
 
Many Thanks,
 
Raveen Moodley
E-Mail  : rmoodley at toyota.co.za
 
 
 
 
"Roehlen, Peter" <PRoehlen at powercor.com.au>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
05/03/2004 02:54 AM
Please respond to
SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
 
To
SAP-WUG at MITVMA.MIT.EDU
cc
 
Subject
Re: Using SWI6 Workload Analysis  in 4.6C
 
 
 
 
 
 
Hi Kathleen,
 
This is what we do when we want ti add the IFFIND interface so that we can
use the object with SWI6:
 
1) If you don't already have it, create a customer version (subtype) of
the
object - eg ZBUS2105.
2) Using SWO1, add interface IFFIND.
3) A new method can now be found in the methods called "Find".
 
SWI6 should now work with the object.  If it doesn't or if you are unhappy
about the popup that asks for the object number, you can re-define the
Find
method to be friendlier.  There is a help topic on how to do this in the
R/3
library (http://help.sap.com) - select your release and then use the
search
tool on "IFFIND".
 
Let me know if you require any further info.
 
Cheers
 
Peter.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Bradshaw-Long, Kathleen
Sent: Friday, 5 March 2004 1:22 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Using SWI6 Workload Analysis in 4.6C
 
Hello all,
 
I am trying to run a workload analysis using transaction SWI6.
 
I am interested in this transaction as a general reporting tool to export
to
some workflow users that will not have access to the detailed log in the
SAP
inbox----only the IAC in-box, where the log information is not as
detailed.
 
However, when I enter business object 2105 in the initial screen of SWI6,
I
get the message "Selected object type must support interface type
'IFFIND'.
 
We are on basis release 4.6C.  I checked our BUS2105 object type
interfaces
and we have an IFSAP and an IF2105, but no IFFIND.
 
I also found a reference in the Practical Workflow for SAP book that says
"to use this report in release prior to 6.10, the business object must
have
interface IFFIND implemented."
 
I tried to find a note in OSS under workflows searching under transaction
SWI6 but I didn't find anything that would help me implement this
functionality in 4.6C.  Is it possible to add this function in my release
or
should I look to use a different workflow log report?  The report should
show the user the status of his or her purchase requistion(s).
 
 
Any help on this?
 
 
 
        Kathleen Bradshaw-Long
        BP/IS
 
> North America Operations
> 836 North Street
> Tewksbury, MA 01876
> Tel: 978-858-8909
>
        Kathleen.Bradshaw-Long at getronics.com
> <www.getronics.com>
>
>
 
 
**********************************************************************
CitiPower Pty and Powercor Australia Ltd. This email and any file
attachments are confidential and intended solely for the use of the
individual or entity to whom they are addressed. If you have received this
email in error please tell us immediately by return email and delete the
document.
**********************************************************************
 


More information about the SAP-WUG mailing list