<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>DIV {
MARGIN: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2>Quick answer - easy testing</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2>Detailed answer - hardly anyone uses that stuff
in practice - we pretty much always assign agents to either a rule (i.e.
calculate the agents) or an expression (i.e. use a list of agents we
created/saved earlier, such as the workflow initiator) , even for easy
testing we usually use the workflow initiator expression.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2>You should not leave the responsible agent blank but
instead assign it to an appropriate rule or expression. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2>No-one uses workflow customizing much either... usually the
changes you want to make surpass the ability of workflow customizing.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=353422901-09112006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>The
information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the person
or entity to which it is addressed. If you are not the intended recipient, you
are hereby notified that any distribution, copying, review, retransmission,
dissemination or other use of this electronic transmission or the information
contained in it is strictly prohibited. If you have received this electronic
transmission in error, please immediately contact the sender to arrange for the
return of the original documents. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Electronic
transmission cannot be guaranteed to be secure and accordingly, the sender does
not accept liability for any such data corruption, interception, unauthorized
amendment, viruses, delays or the consequences thereof.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Any views
expressed in this electronic transmission are those of the individual sender,
except where the message states otherwise and the sender is authorized to state
them to be the views of SAP AG or any of its subsidiaries. SAP AG, its
subsidiaries, and their directors, officers and employees make no representation
nor accept any liability for the accuracy or completeness of the views or
information contained herein. Please be aware that the furnishing of any pricing
information/ business proposal herein is indicative only, is subject to change
and shall not be construed as an offer or as constituting a binding agreement on
the part of SAP AG or any of its subsidiaries to enter into any relationship,
unless otherwise expressly stated. </FONT></SPAN></P>
<DIV> </DIV><BR>
<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>cool_dude2kin<BR><B>Sent:</B> Thursday, 09 November 2006 11:52
AM<BR><B>To:</B> sap-wug@mit.edu<BR><B>Subject:</B> workflow definition -
responsible agent<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV
style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV>Hi All,</DIV>
<DIV> I have a really dumb question(rather, a clarification) about
the usage of 'Organizational Objects'(Organizational
unit,position,job,workcenter etc.) in the responsible agents field
in the STEP definition of a workflow.</DIV>
<DIV> I undestand that all the organizational objects form part of
application data which is client/system dependent.This means,when the workflow
is transported to other systems,the workflow may not work correctly because
these org objects may not exist in the target system.So what's the point of
specifying this application data in the workflow definition ?! .
I feel it's best to leave the values for organization object as blank in
DEV system, and then use 'Workflow customizing' to assign the organization
objects in the traget system.</DIV>
<DIV> </DIV>
<DIV>Pls advice if you agree with me or excuse this ignorant fellow
workflower......... </DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Kiran.</DIV></DIV><BR>
<HR SIZE=1>
Check out <A
href="http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta">the
all-new Yahoo! Mail</A> - Fire up a more powerful email and get things done
faster.</BODY></HTML>