<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><DIV></DIV>
<DIV>Tom,</DIV>
<DIV> </DIV>
<DIV>I understand your requirement, I was asked for it several times and it does make sense. It also explains why it did not work for you at the first place. </DIV>
<DIV>I'll describe several options that I handled it though there might be better solutions that may suit your occasion:</DIV>
<DIV>1. I've create customized rule which runs standard rule 168, store the result and runs 168 again. In this way you get the 2nd level manager.</DIV>
<DIV>2. Another time I used FM RH_STRUCT_GET (or maybe its RH_GET_STRUCT) with parameter level value 3 - it also resolve the manager of the manager.</DIV>
<DIV>3. In previous step resolve the initator manager (using rule 168) and store it workflow container element, say WF_MANAGER. The to set step to expression &WF_MANAGER& and deadline to the result of rule 168 for &WF_MANAGER&.</DIV>
<DIV> </DIV>
<DIV>Let me know if you need more details - it should work well.</DIV>
<DIV> </DIV>
<DIV>Good luck,</DIV>
<DIV> </DIV>
<P><FONT face="verdana, helvetica, sans-serif" color=#00007f size=2><STRONG>Regards,<BR>Shai Eyal</STRONG></FONT></P>
<P><FONT face=Verdana color=#000080 size=2><STRONG>SAP Logistics senior consultant<BR>SAP Workflow specialist</STRONG></FONT></P>
<P><FONT face=Verdana color=#000080 size=2><STRONG><A href="http://www.linkedin.com/in/shaieyal" target=_blank rel=nofollow>http://www.linkedin.com/in/shaieyal</A><BR>Mobile: 972-52-5816633</STRONG></FONT></P>
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif"><BR>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: verdana, helvetica, sans-serif"><FONT face=Tahoma size=2>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> "sap-wug-request@mit.edu" <sap-wug-request@mit.edu><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> sap-wug@mit.edu<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, October 31, 2008 18:24:12<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> SAP-WUG Digest, Vol 47, Issue 40<BR></FONT><BR>Send SAP-WUG mailing list submissions to<BR> <A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A><BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>or, via email, send a message with subject or body 'help' to<BR> <A href="mailto:sap-wug-request@mit.edu" ymailto="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</A><BR><BR>You can reach the person
managing the list at<BR> <A href="mailto:sap-wug-owner@mit.edu" ymailto="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</A><BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of SAP-WUG digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. RE: Event Activation/Deactivation (Penhall, Kathy)<BR> 2. Deadline - Latest End Recipient of Message (Simon, Tom)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Fri, 31 Oct 2008 10:32:05 -0500<BR>From: "Penhall, Kathy" <<A href="mailto:kpenhall@hydro.mb.ca" ymailto="mailto:kpenhall@hydro.mb.ca">kpenhall@hydro.mb.ca</A>><BR>Subject: RE: Event Activation/Deactivation<BR>To: <<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Message-ID:<BR> <<A
href="mailto:CAD3E86E65D76C47BD61434EDFD7D10F01A126CA@MHMAIL02.hydro.mb.ca" ymailto="mailto:CAD3E86E65D76C47BD61434EDFD7D10F01A126CA@MHMAIL02.hydro.mb.ca">CAD3E86E65D76C47BD61434EDFD7D10F01A126CA@MHMAIL02.hydro.mb.ca</A>><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Hi Mike,<BR><BR>Thanks for your response. The event's behaviour on feedback setting was<BR>system defaults (Deactivation of linkage), so I'm guessing this was what<BR>deactivated our workflow. We've never changed this setting in any of<BR>our workflows. Mystery solved.<BR><BR>Much appreciated.<BR><BR>Kathy <BR><BR><BR>Date: Mon, 27 Oct 2008 15:19:25 +0000<BR>From: Mike Gambier <<A href="mailto:madgambler@hotmail.com" ymailto="mailto:madgambler@hotmail.com">madgambler@hotmail.com</A>><BR>Subject: RE: Event Activation/Deactivation<BR>To: "SAP Workflow Users' Group" <<A href="mailto:sap-wug@mit.edu"
ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Message-ID: <<A href="mailto:BAY117-W18B5D13196FD33C3922B1CD5240@phx.gbl" ymailto="mailto:BAY117-W18B5D13196FD33C3922B1CD5240@phx.gbl">BAY117-W18B5D13196FD33C3922B1CD5240@phx.gbl</A>><BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR><BR>Kathy,<BR><BR>Despite our controls on people changing linkages using SWETYPV, we have<BR>the odd linkage broken from time to time too.<BR><BR>Usually the cause is one of three things:<BR><BR>1. The 'Behaviour Upon Feedback' setting was left as 'System defaults'<BR>and a severe enough error caused the linkage to deactivate. We tend to<BR>prefer 'Do Not Change Linkage' when the event is handling high volume or<BR>business critical Workflows so that this doesn't happen. If this has<BR>happened to you I'd expect to see something in SWEQADM if you had turned<BR>on the Event Queue enablied feature.<BR><BR>2. Somebody mucked around with the settings in
development and forgot to<BR>'undo' or 'correct' their changes before sending through their<BR>Transport. It happens. Can't do much about it.<BR><BR>3. Someone clicked on the 'Deactivate Linkage' icon in the Workflow<BR>Builder (Header Data->Version INdependent->Start Events). This can<BR>happen by accident because the icon is right next to the Event Container<BR>Binding icon. Requires a bit of knowledge to find of course.<BR><BR>To counter these we keep a close eye on the settings by running reports<BR>on the SWETYPV settings and check what linkages are active against a<BR>list we try to keep up to date.<BR>Regards,<BR><BR>Mike GT<BR><BR><BR>> ______________________________________________ <BR>> From: Penhall, Kathy <BR>> Sent: Monday, October 27, 2008 9:26 AM<BR>> To: '<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>'<BR>>
Subject: Event Activation/Deactivation<BR>> <BR>> Hello all,<BR>> <BR>> We are on ECC 6.0 and have been processing training requests via<BR>> workflow prior to and since our upgrade in October 2007. We book<BR>> original training requests using WS01200151 which is generated by the<BR>> event PDRELA_025-REQUESTED when training is requested by employees in<BR>> ESS. Late last week this event seems to have been deactivated in our<BR>> production landscape - no transports had been moved and it happened<BR>> mid-morning. One user who was booking a number of training requests<BR>> said he'd done it one minute, and it stopped working the next. <BR>> <BR>> Normally we activate events in DEV via transaction PFTC and create a<BR>> transport to move the event activation forward through our landscape<BR>> and into PRD. I realize how easy it is to deactivate an event in
this<BR>> way in any system, and as a result very few people have access to the<BR>> transaction in production. I was happy to discover I could<BR>> re-activate the event directly in production (seems to me I could not<BR>> do this in version 4.6C), so we did this and all was right with the<BR>> world again. Then we attempted to find out who had run transaction<BR>> PFTC between the time the event stopped working and when it was<BR>> "fixed". The only evidence we found was that the event had been<BR>> re-activated by me. <BR>> <BR>> So my question is, how else might this event have been de-activated?<BR>> Or should we have done our investigation before we "fixed" the<BR>> problem? Your help solving this mystery is appreciated.<BR>> <BR>> <BR>> Kathy Penhall <BR>> HR Applications<BR>> SAP Support Services <BR>> Manitoba Hydro<BR>> 693 Taylor Avenue<BR>> Winnipeg,
MB<BR>> (tel)204-477-7197 <BR>> <BR>> <BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <A href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081031/240a6472/attachment-0001.htm" target=_blank>http://mailman.mit.edu/pipermail/sap-wug/attachments/20081031/240a6472/attachment-0001.htm</A><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Fri, 31 Oct 2008 11:46:26 -0400<BR>From: "Simon, Tom" <<A href="mailto:Simon.Tom@aoins.com" ymailto="mailto:Simon.Tom@aoins.com">Simon.Tom@aoins.com</A>><BR>Subject: Deadline - Latest End Recipient of Message<BR>To: <A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A><BR>Message-ID:<BR> <<A href="mailto:A67DFD136BC63D469A22EA616D31ED9F0434815B@EXCVSRV2.aoins.com"
ymailto="mailto:A67DFD136BC63D469A22EA616D31ED9F0434815B@EXCVSRV2.aoins.com">A67DFD136BC63D469A22EA616D31ED9F0434815B@EXCVSRV2.aoins.com</A>><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Shai,<BR> In the deadline, I wanted the agent assignment to be the<BR>superior of the agent who is to execute the approval step. The problem<BR>with assigning rule 168 in the step for the deadline is that the<BR>workflow container does not contain the result of the rule for the agent<BR>to approve the step until after it is executed. If the step is not<BR>executed, the binding between task and workflow is not completed. The<BR>task container contains the results of the rule. That is why I am<BR>relying on the default rules of the task to execute the rule 168. This<BR>binds the results from the task to the default rule to determine the<BR>superior of the agent who is has been chosen to
execute the step. If I<BR>knew of a business object with a method that I could use to determine<BR>successive hierarchal agents for a initiator of a workflow I could then<BR>create an activity step to fill these agent variables and use them in<BR>rule 168 for the deadline. <BR><BR>Thank you<BR><BR>Tom Simon <BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <A href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20081031/a91a7b85/attachment-0001.htm" target=_blank>http://mailman.mit.edu/pipermail/sap-wug/attachments/20081031/a91a7b85/attachment-0001.htm</A><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A href="mailto:SAP-WUG@mit.edu" ymailto="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug"
target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR>End of SAP-WUG Digest, Vol 47, Issue 40<BR>***************************************<BR></DIV></DIV></div><br>
<hr size=1> <a href="http://sg.rd.yahoo.com/aa/mail/domainchoice/mail/signature/*http://mail.promotions.yahoo.com/newdomains/aa/"> Get your new Email address! </a> <br>
Grab the Email name you've always wanted before someone else does!</body></html>