EBP Workflow questions

[Dart, Jocelyn]

Hi Dale,
The point with general tasks is to use them when the task really
is general.  For an ad hoc approval task you may not be able to
tell in advance who the user wants to perform the ad hoc approval
 - therefore general task may be the best option.  However if you
can narrow it down by all means assign possible agents (I find
assigning profile generator roles, i.e. activity groups is best -
particularly in EBP).
 
In such a situation there is no security risk because the main (i.e. non adhoc)
EBP approvals can't be removed - you can only add new approval
tasks not remove them, i.e. the workflow controls where the ad hoc approval
tasks can be added, and EBP controls what ad hoc functionality the user
can use.
 
Performance should not really be an issue in current releases of SAP - in any
case EBP ensures they have chosen an actual approver for the added
approval task, i.e. the work item is not going to go to the world but
only to the nominated approver.
Jocelyn.
 
-----Original Message-----
From: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Wednesday, 16 October 2002 11:40 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP Workflow questions
 
 
Thanks Jocelyn.
 
Is it required that the dialog tasks be general tasks though? I always
thought general tasks created  potential performance problems and  posed an
added security risk. Is this no longer an issue with EBP?
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow/Webflow  PP Consultant - SAP Practice
 
IBM Business Consulting Services
Phone: 845-691-7861
           T/L 8-320-8440
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........
 
 
"Dart, Jocelyn" <jocelyn.dart at sap.com>@MITVMA.MIT.EDU> on 10/15/2002
08:10:04 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Re: EBP Workflow questions
 
 
 
Hi Dale,
Re 1 - If you have a forwarding button appearing then it will work.
If the forwarding button has been removed, it's deliberate to force
use of the change approver/add approver functions. Whether or not the
button is there varies on release.
 
Re 2 - check the setting of your managers for the BBP_WFL_SECURITY
value in the Personalization section of the profile generator role.
Make sure it is not None or blank.
I assume you have checked the relevant task is a general task,
and that when ad hoc approvers are assigned they are assigned as
userids, i.e. USxxxxx, and not positions/org units/etc.
 
Otherwise please report this to OSS.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Wednesday, 16 October 2002 5:18 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP Workflow questions
 
 
Hello All:
 
  I have two questions regarding EBP.
 
1. Is workitem forwarding supported in the MySAP business workplace for EBP
3.0?
 
2. For the EBP shopping cart approval scenario, we have  received the
error, "Responsible Agent ' ' not found for task TS00008124".     which is
the added approvers task. In the first step of the workflow when the
requester assigns an adhoc manager, this works without any problems. The
error occurs in subsequent steps when a manager attempts to assign an adhoc
subsequent approver.  This fails even when testing with superuser profiles
so we have eliminated authorization as a possibility.
When we looked at the workitem container for the errored workflow, each
dynamically created Agent container is filled with the correct values,
however in the case of the manager's adhoc processing step, this value does
not appear to be visible to the adhoc role resolution function.
We tested using both standard templates, and custom templates, in the
latter, we changed the excluded agents container for the copied adhoc
anchor workflow to be based on the requestor in each case instead of the
last agent which is specified in the standard template.
 
 
 Any insight that you can provide will be greatly appreciated.
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow/Webflow  PP Consultant - SAP Practice
 
IBM Business Consulting Services
Phone: 845-691-7861
           T/L 8-320-8440
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
 lose sight of the shore..........