Simulating a role resolution within a workflow step

[Frank Reichenbach]

Hi Jocelyn,
      thank you for the quick and perfect answer to my question: this really solved every aspect!
 
Best regards,
 
Frank
 
--- "Dart, Jocelyn" <jocelyn.dart at sap.com>
> wrote:
>Hi Frank,
>Function module RH_GET_ACTORS can be used to execute role resolution and
>return a list of agents.  You need to pass in your role id (in HR format
>i.e.
>AC99999999 where 99999999 is the role number) and the role container.
>
>There are a number of ways of including this in your workflow but a couple
>of suggestions for you:
>
>1) If the role resolution is based on the attributes of objects and doesn't
>need any dynamic parameter input, then create a virtual attribute of type
>WFSYST-AGENT
>(mulitline if you need to) against the most appropriate
>object to determine the agents.  E.g. if the role is "Vendor master owner"
>based on
>vendor city/country/etc. then you could create an attribute "vendor master
>owner" against
>the vendor object LFA1.  To include it in your workflow you then just
>reference
>the attribute of the object i.e. LFA1.vendormasterowner
>
>2) If you need to pass in additional parameters that won't be known until
>runtime,
>create a method against the most appropriate object to determine the agents.
>
>e.g "authorised cost centre delegate" where parameters are cost centre, and
>authority level (which won't be known until runtime).  The method should
>return
>the list of agents - you could either use the standard "result" parameter or
>
>add your own output parameter to the method.   Make sure your method
>has the dialog flag off, then create a background task for it, and include
>it as an activity step in your workflow (prior to where you want to use the
>agents)
>binding the agent list to your workflow container element.
>
>Note that function module RH_GET_ACTORS only resolves the role - it doesn't
>check
>whether all the agents found are possible agents.  So if that is likely to
>be an
>issue you might also want to call WF_TASK.AllAgentsOfTaskGet and compare the
>
>possible agents to the list of agents found by the role in your method or
>attribute.
>
>Hope that helps.
>Regards,
>        Jocelyn Dart
>Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
>SAP Australia
>Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
>Tel: +61 412 390 267
>Fax: +61 2 9935 4880
>
>
>-----Original Message-----
>From: Frank Reichenbach [mailto:frankreichenbach at dontgotmail.com]
>Sent: Saturday, 27 October 2001 2:39 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Simulating a role resolution within a workflow step
>
>
>Hi guys,
>being on a 46b system I am trying to somehow manage the following task:
>The basic aim is to get the result of a role resolution and to store it in a
>workflow
>container-element in order to use it later on in another step within this
>workflow.
>This of course should be achieved without any user interaction. (e.g. its
>not possible to create a dummy method that is used by a dummy task that is
>used by a step that is then being executed by a user storing
>_WI_actual_agent).
>Is anyone aware of the function that is executed when the wfms does the role
>resolution and could thus be called by a background task.
>Any other suggestions are also very welcome!
>
>Thanks in advance!
>
>Best regards,
>
>Frank
>
>_____________________________________________________________
>===========================
>Kick start your hits today with www.SearchGalore.com! Be in the #1 spot for
>as little as one cent.
>===========================
>Get YOUR FREE email address today! http://www.dontgotmail.com
>"Don't Got Mail!"
 
_____________________________________________________________
===========================
Kick start your hits today with www.SearchGalore.com! Be in the #1 spot for as little as one cent.
===========================
Get YOUR FREE email address today! http://www.dontgotmail.com
"Don't Got Mail!"