Create a Rule to Find a user of a position

Mark Pyc mark.pyc at gmail.com
Tue Dec 5 16:27:19 EST 2006


G'day Sue,

Couple of choices, well lots probably.

1. Don't delete users when someone leaves the company but delimit the
user-id and ensure the user has active substitution set up. Yours is an
extreme case with a 6 month lag, but any process can suffer the initiator
disappearing while the process is alive. Delimiting rather than deleting is
a good general user management process. As fas as licencing is concerned
they are the same. It also means that when you're reviewing old documents
etc in the system you can find out who PYCM is for e.g.

2. In this case create a dummy background step which calls an empty method
and put the Requested Start on this. That way in six months the process
kicks off again, does nothing for a moment and then continues to the
decision step you're interested in. This ensures the ruole will run for the
current data / org structure.

Have fun,
Mark


On 12/5/06, Sue Doughty <Sue.Doughty at odfl.com> wrote:
>
>  We are on 4.7, Basis 6.40.
>
> There is a workflow that is triggered when the OnHold Applicant action
> is executed.  The Requested Start for the workflow is six months from the
> date that work item is created.  The WF_Initiator will get a Decision
> task after six months, if the Applicant is not put back in process.  The
> decision will be either to Process or Reject the applicant.
>
> The problem is when the workflow starts the WF_Initiator is, of course,
> there.  But, if during the six months, he has left the company the workflow
> will be haning  because the Wf_Initiator's userid will not be in the system
> anymore.
>
> Instead of using the WF_Initiator as the agent for the Decision task, I'm
> trying to create a rule that will find the user of the position of the
> WF_Initiator.  I would have the workflow terminate if rule resolution has no
> result.  I found function module PDV_GET_POSITION_HOLDER, but can't get it
> to work -- I can't figure out what the input for the rule should contain.
>
> Another question:  If I could create a rule, after six months when the
> Requested Start is reached, would it re-check the rule to see if there is a
> user for the position and fail if not found?
>
> Any suggestions on how I can get this to work would be GREATLY
> appreciated.
>
>        [image: Old Dominion Freight Line, Inc., 500 Old Dominion Way,
> Thomasville, NC 27360] <http://www.odfl.com/>
>  *Sue Doughty*
> WORKFLOW SPECIALIST
>
> Phone:  (336) 822-5189
> Fax:  (336) 822-5149
> Sue.Doughty at odfl.com
>    *OLD DOMINION FREIGHT LINE, INC. <http://www.odfl.com/>*
> 500 Old Dominion Way, Thomasville, NC 27360 <http://www.odfl.com/>
>
>
>  ------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *shireesh.mitragotri at accenture.com
> *Sent:* Monday, December 04, 2006 4:54 AM
> *To:* sap-wug at mit.edu
> *Subject:* BUS2105 PR creation event....????
>
>
>
> Hi - What is the best way to trap the Purchase Requisition Creation event?
> I did the following and it's not working...(R/3 Enterprise ver.)
>
> 1. Tried Event creation wizard with a subtype of BUS2105...change doc
> BANF...but event upon creation does not exist.
> 2. Tried BSVX/BSVW to link event status to system status etc...Did not
> find a way out.
> 3. My client requires a workflow to be triggered when a PR is created and
> that is when there is a default condition - "Release Indicator is blocked"
> when it is created for first time.
>
> Any help here?
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061205/fbb26f61/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2002_ODFL_Logo.gif
Type: image/gif
Size: 7827 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061205/fbb26f61/attachment.gif


More information about the SAP-WUG mailing list