<br><font size=2 face="sans-serif">Hello Mike,</font>
<br>
<br><font size=2 face="sans-serif">Interesting discussion, since we all
have our own standards of naming things, I think. </font>
<br>
<br><font size=2 face="sans-serif">My personal opinion is : </font>
<br><font size=2 face="sans-serif">Naming an object type as "Z+object
type of supertype" (or "z+object type of supertype"),
for example ZBUS2096, is more straight-forward and much easier to
understand for another person, than the developer, from which supertype
the subtype is created and delegated from.</font>
<br>
<br><font size=2 face="sans-serif">In the object name I would then rather
clarify the object by for example defining the object name as "</font><font size=2><tt>CustDebitMemoReq</tt></font><font size=2 face="sans-serif">"
or even "z</font><font size=2><tt>CustDebitMemoReq" to
point out that it's a subtype. </tt></font>
<br>
<br><font size=2><tt>Regards</tt></font>
<br><font size=2><tt>Viveka</tt></font>
<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Mike Pokraka"
<asap@workflowconnections.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">2006-12-19 12:03</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: You know what I hate?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hmmm, I used to agree with you. The SAP help also
suggests using ordinary<br>
English words.<br>
<br>
However over the years of bouncing around different customer sites<br>
(sometimes in rapid succession, sometimes even just for a single day) I<br>
appreciated people using prefixes for much the same reasons Paul<br>
described. Bughunting/understanding foreign workflows is much easier if<br>
it's straightforward to spot which attributes are custom. So these days<br>
I'm back in the other side and prefix them with a small z. (I find caps<br>
more annoying - as in ZAmount).<br>
<br>
What is annoying is people that create subtypes and call them ZBUS2096.<br>
Huh? It's a Debit Memo Request. And your subtype should also be called
the<br>
same - perhaps with an 'Enhanced' suffix or similar. So I suaually create<br>
subtypes and add a small z before the original object name - as in<br>
zCustDebitMemoReq.<br>
<br>
Just my 2p.<br>
Cheers,<br>
Mike<br>
<br>
<br>
On Mon, December 18, 2006 21:59, Alon Raskin wrote:<br>
> I know that this is mostly an academic argument but I would love to
hear<br>
> peoples thoughts on this...<br>
><br>
> You know what I hate? I hate it when I look at a Z Business Object<br>
> (delegated sub-type) and someone has created a method called zUpdate
or an<br>
> attribute called zAmount. Is there really a need for the 'z' in the
name<br>
> of the attribute/method? Perhaps there is something I am missing here
so<br>
> please feel free to point out the error of my ways.<br>
><br>
> Do people do this because they don't realise that they can redefine
an SAP<br>
> delivered attribute/method? Or are they concerned that SAP will deliver
an<br>
> attribute with the exact same name? I assume that the redefined<br>
> method/attribute would not be effected but perhaps someone has had
this<br>
> happen...<br>
><br>
> I understand why people do it with append fields on a table but why
do<br>
> this for a BOR sub-type?<br>
><br>
> Regards,<br>
><br>
> Alon<br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
><br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>