Need FM to re-resolve role.

[Dart, Jocelyn]

Rick,
There are about double the number of WAPIs in a 4.7 system versus a 4.6C - including some
really useful admin functions.  By upgrade list I just meant add it to your list of "things to do when we upgrade..."
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Rick Sample
Sent: Tuesday,6 July 2004 11:46 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Need FM to re-resolve role.
 
 
How do I get this added / replaced? Patch level issue?
 
I checked and have some SAP_WAPI* FMs but not
SAP_WAPI_ADM_WORKITEM_REDORULE.
Kinda curious now. How do I know what I am missing?
 
Thanks Jocelyn...
 
Rick
 
 
>>> jocelyn.dart at sap.com 7/5/2004 20:39:53 >>>
Rick,
Suggest you add to your upgrade list the need to replace SWW_WI_AGENTS_CHANGE with SAP_WAPI_ADM_WORKITEM_REDORULE,
as SWW_WI_AGENTS_CHANGE is not released for customer.
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Michael Pokraka
Sent: Monday,5 July 2004 9:27 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Need FM to re-resolve role.
 
 
Interesting, I stand corrected (and learnt something)
Cheers for the update
Mike
 
Rick Sample wrote:
> I found what I needed.
>
> Issue:
> I have a custom zTable to hold Org numbers of various Org units like HR
> Service Center
> and a FM to lookup the entry for the specified task. We use this zConsts
> table for a lot
> of custom issues we would rather not hard code or have to transport. A wee
> bit more flexible.
> I made an incorrect entry in the table for the org unit I want to route.
> Oops!
>
> Example, in dev our HRSC org number is 80000001 in QA it is 80000121 and
> prod 800000454.
> (Not the real numbers but you get the point. Different number ranges in
> every client bytes!)
> It was a real PIA to transport the QA number up to test, then transport the
> Prod number to prod after
> testing, then change back to Dev to continue work, etc. etc. OR have case
> statements in all code to
> handle every system/client for every role / task. Another PIA.
>
> After changing the number to the correct value, I used FM
> SWW_WI_AGENTS_CHANGE
> to re-resolve the role on the task. Run it, pass in the task without agent
> (or incorrect agent), execute.
>
> Yes, I could have just taken over as admin, forwarded to each WI to each
> user (10 in the HRSC org)
> or use another one of our utilities to dynamically call a FM and import a
> list of Task Ids and let the program
> do the work! With 450 WI incorrectly routed it was a no brainier to use my
> program verses manually
> forwarding.
>
> 4.6c
>
> Rick Sample
> Workflow Developer
> Graybar, Inc.
>
>>>> workflow at quirky.me.uk 7/1/2004 11:46:41 >>>
> Hmmm, methinks that explains the trumpets and fanfare for this 'wonderful
> new feature' in Enterprise.... Seriously, it has been mentioned a few times,
> I think here on the list too.
> 'fraid you're stuck with recreating the workflow. I recall doing that
> aplenty on a 4.6 system, I think for the same reason. If it's in a loop you
> could maybe manipulate the container and do a manual complete to make it go
> round again.
> Cheers
> Mike
>
> Rick Sample wrote:
>> I don't have either FM in 4.6c. ?
>>
>>>>> workflow at quirky.me.uk 7/1/2004 9:57:45 >>>
>> Hi Rick,
>> SAP_WAPI_ADM_WORKITEM_REDORULE - but I think it isn't available in 4.6c.
>> Otherwise try SWL_WI_ADM_REDO_RULE.
>> Cheers
>> Mike
>>
>> Rick Sample wrote:
>>> I had to make some changes to an org unit. I was using a table
>>> to look up the org unit I was routing a task. I had an incorrect entry
>>> in the table and need to re-resolve the role manually to pick up
>>> the changes.
>>>
>>> Can someone remind me what the FM is to re-resolve a FM role?
>>> I tried forcing them in error and restart but it did not resolve the
>>> role.
>>> I used SWW_WI_STATUS_CHANGE_NEW to force to error and restart.
>>>
>>> 4.6C
>>>
>>> Thanks!
>>>
>>>
>>
>>
>
>