<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008>Hi Andy,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008>You've asked a very good question, and it's one that
seems to come up on almost every workflow project. There are several ways
you might want to do the type of checking that you're asking about.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008>One approach would be: if the person submitting the
expenses for approval is already known at the time the workflow is to be
triggered, you can write a check function module to see if the approval workflow
is needed. If it is not needed, raise an exception and the
workflow will not be launched. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008>On the other hand, if that person isn't known when the
workflow starts, you could do the same thing later on, using an attribute or
functional method that returns a result (e.g. 'X' = do the approval, SPACE
= skip the approval). You'd use that result in a condition that you
</SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008>configure on the <EM>Conditions </EM>tab page of the
approval step. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=218512502-23102008>Best
regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=218512502-23102008></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=218512502-23102008>Sky
Kimball</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=218512502-23102008>SAP
America, Inc.</SPAN></FONT></DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Andy Curtis<BR><B>Sent:</B>
Wednesday, October 08, 2008 7:41 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> Agent determination AC00000168<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>
<DIV>We use rule AC00000168 to find a Chief to Approve expenses, so when the
'top chief' (the big chief), submits expenses the wf goes into error as he does
not have a chief! Anyone got a novel/innovative solution for this?</DIV>
<DIV> </DIV>
<DIV>Andy</DIV></DIV></BODY></HTML>