<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD><TITLE>Re: SAP Workflow Version</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=980201002-19122006><FONT face=Arial
color=#0000ff size=2>Alon,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=980201002-19122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=980201002-19122006><FONT face=Arial
color=#0000ff size=2>Well actually I do see a reason for it. If you are drilling
into a WF task and you see an underlying Zmethod, then you know immediately that
you are not dealing with SAP standard (and therefore the likelihood of a bug
increases by 78%).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=980201002-19122006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=980201002-19122006></SPAN><FONT
face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=980201002-19122006>But
it's also t</SPAN><SPAN class=980201002-19122006>rue that you can discover the
same information by drilling down that extra step into the
BOR.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=980201002-19122006></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=980201002-19122006>cheers</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=980201002-19122006>Paul</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><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>Alon Raskin<BR><B>Sent:</B>
Tuesday, 19 December 2006 7:59 AM<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> You know what I hate?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText92709 dir=ltr>
<DIV dir=ltr><FONT size=2>
<DIV dir=ltr><FONT size=2>I know that this is mostly an academic argument but I
would love to hear peoples thoughts on this...</FONT></DIV></FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>You know what I hate? I hate it when I look at a Z
Business Object (delegated sub-type) and someone has created a method called
zUpdate or an attribute called zAmount. Is there really a need for the 'z' in
the name of the attribute/method? Perhaps there is something I am missing here
so please feel free to point out the error of my ways. </FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Do people do this because they don't realise that they
can redefine an SAP delivered attribute/method? Or are they concerned that SAP
will deliver an attribute with the exact same name? I assume that the redefined
method/attribute would not be effected but perhaps someone has had this
happen...</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>I understand why people do it with append fields on a
table but why do this for a BOR sub-type?</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Regards,</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Alon</FONT></DIV></DIV>
<BR>
***********************************************************************<BR>
The information in this e-mail together with any attachments is<BR>
intended only for the person or entity to which it is addressed<BR>
and may contain confidential and/or privileged material.<BR>
Any form of review, disclosure, modification, distribution<BR>
and/or publication of this e-mail message is prohibited. <BR>
If you have received this message in error, you are asked to<BR>
inform the sender as quickly as possible and delete this message<BR>
and any copies of this message from your computer and/or your<BR>
computer system network. <BR>
Any attachments should be checked for viruses by you, before being opened. SunWater accepts no responsibility for an attachment that contains a virus.<BR>
***********************************************************************<BR>
</BODY></HTML>