Universal Worklist - TS20000166 (purchase order release) and SWFVISU

Kjetil Kilhavn kjetil.kilhavn at bluec.no
Thu May 26 20:45:47 EDT 2011


 Tirsdag 24. mai 2011 17.48.24 skrev Griffiths, Mark :
> I would copy and change the workflow to use a user decision and then use a
> UWL view to process the approvals.  The workflow could then release the PO
> using a BAPI in a background task.
That is precisely what I *don't* want to do. I want the solution to stay as 
close to SAP standard as possible. Less maintenance, hopefully. At least it 
will be done that way initially. In my opinion people are dismissing standard 
far too quick, and only later realize the maintenance cost.
Since the company who first implemented a solution did such a poor job it is 
easier to persuade them to try SAP standard so they get proper authorization 
checking etc.

ObFrust: The other day I had to check (EhP 4 post-upgrade check/fix) a report 
which was a copy of SAP standard report. And for what? To remove one field 
from the standard output setup, add another field to the standard output setup 
... and finally to add a new field to the available output fields and to the 
standard output setup. Using implicit enhancement points everything except for 
one statement could be implemented. This statement had to be "replaced" in a 
modification to read configuration for standard transaction codes when the 
special transaction codes are used, and of course execute as normal when the 
ordinary transaction codes are used.

> Regards,
> 
> Mark
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Dart, Jocelyn Sent: 20 May 2011 05:55
> To: SAP Workflow Users' Group
> Subject: RE: Universal Worklist - TS20000166 (purchase order release) and
> SWFVISU
> 
> Hi Kjetil,
> So you've taken away a user decision task or WebDynpro app?
> And replaced it with a SAPGUI task...
> 
> SWFVISU is a possibility.
> You could also use the UWL XML config and use the function module launcher
> to call the relevant BAPI to release the PO. You might need to create a
> wrapper function module to simplify it a bit... but that approach works
> ok. You could even allow mass approval with the checkbox options (check
> out the standard WorkItemApprovals view).
> 
> Regards,
> Jocelyn
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Kjetil Kilhavn Sent: Thursday, 19 May 2011 12:39 AM
> To: sap-wug at mit.edu
> Subject: Universal Worklist - TS20000166 (purchase order release) and
> SWFVISU
> 
> I have a request to give the users back the button they say I have removed.
> I haven't really removed anything, just switched from a custom workflow
> full of security problems to the SAP standard workflow which doesn't
> circumvent authorizations....
> 
> Anyway, the users would like to be able to approve (possibly also reject,
> but that's less important to them I believe) the purchase orders directly
> from the work item display in Universal Worklist. Now, there is the
> wonderful world of SWFVISU, but is there a SAP standard application which
> can be used for this purpose. Currently they see the task description, I
> think they still want to see that.
> 
> Any low-hanging fruits, or do I have to tell them it will take 42 days?

-- 
Kjetil Kilhavn (+47 40220607)
Blue Consulting AS (http://www.bluec.no)



More information about the SAP-WUG mailing list