<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1255">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=278023915-13032007><FONT face=Arial
color=#0000ff size=2>PB,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=278023915-13032007><FONT face=Arial
color=#0000ff size=2>You really want to number based upon your release
strategy. We use 901 in our HR system and 902 in our ERP system so that
when we see a workflow number we automatically know in which instance it
resides. We keep these same prefixes for both DEV and Prod Support (the
only two systems in which we develop). The reason we do this is so that
regardless of which path we are currently on the workflow will have the same
number when it reaches prod. For example:</FONT></SPAN></DIV>
<UL dir=ltr>
<LI>
<DIV align=left><SPAN class=278023915-13032007></SPAN><SPAN
class=278023915-13032007><FONT face=Arial color=#0000ff size=2>In Dev we
create workflow #90200037 and move it through Integ and QA into
Production.</FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN
class=278023915-13032007>Later</SPAN><SPAN class=278023915-13032007> our Dev
to Prod path is closed for changes and only used for a new Release
project. Perhaps we need to make a quick change to the #90200037 design
by adding a subflow. We would make our change in
ProdSupport. We create the subflow in both Dev and ProdSupport using the
same number sequence #90200038, and add it to #90200037.
The ProdSupport workflow is quickly moved into production.
The Dev workflow is a good representation of what is in
production so that any testing or Release changes are kept in
synch. Eventually when the Release is moved into production, the
Dev workflow will replace the ProdSupport workflow, but the numbers
remain the same.</SPAN></FONT></FONT></FONT></DIV></LI></UL>
<DIV dir=ltr align=left><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN
class=278023915-13032007>Thus whether you want to use the same prefixes or
different ones between systems would depend upon your own company's landscapes
and release strategy. This just happens to be what works for us and keeps
life "simple".</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=278023915-13032007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=278023915-13032007></SPAN><FONT
face=Arial><FONT color=#0000ff><FONT size=2>B<SPAN class=278023915-13032007>est
Wishes,</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT><FONT color=#0000ff><FONT size=2><SPAN
class=278023915-13032007></SPAN></FONT></FONT></FONT><SPAN
class=278023915-13032007></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>S<SPAN class=278023915-13032007>herie</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=278023915-13032007></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=278023915-13032007>Sherie Munday</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=278023915-13032007>SAP Workflow
Developer/Analyst</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=278023915-13032007>Air Products & Chemicals,
Inc.</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>praveen
rajendran<BR><B>Sent:</B> Tuesday, March 13, 2007 9:47 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: Workflow
Configuration<BR></FONT><BR></DIV>
<DIV></DIV>Thanks for the info Ronen...<BR>but I've have couple of doubts in
this...<BR>I've maintained the number ranges like this, in the development
system. <BR>999 for DEV<BR>900 fro QA<BR>910 for PRD<BR>Is this ok to do this
just in Development system or should i also do this in QA and PRD???
<BR><BR>Secondly,<BR> when I use report program RHMOVE30 to create
transport request for my Org structure, Is that enough if I transport
Organization Unit in top hierarchy and will those Org Units and positions
below automatically included into that request or should I add each Org
unit one by one into the request??? <BR><BR>Regards,<BR>PB<BR><BR>
<DIV><SPAN class=gmail_quote>On 3/8/07, <B class=gmail_sendername>ψεπο τεχρ</B>
<<A href="mailto:ronenf@paz.co.il">ronenf@paz.co.il</A>> wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>Hello,</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>For the number prefix: there
is no real need to maintain this in your QA & PROD environment since you
probably won't be doing any development in those environment. you can
transport the prefix setting from DEV to those systems just in order to get a
"green traffic light" in transaction SWU3 in those
systems.</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>Regarding org units and
positions: you can use report RHMOVE30 to transport your org. structure
between systems. the reason you don't get a change request prompt each time
you modify your org. plan in dev is probably because the 'transport link' for
HR objects is deactivated in your DEV system.</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>Ronen</FONT></SPAN></DIV>
<DIV><SPAN class=e id=q_111300ab3894691c_1>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original
Message-----<BR><B>From:</B> <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu"
target=_blank>sap-wug-bounces@mit.edu</A> [mailto:<A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu" target=_blank>
sap-wug-bounces@mit.edu</A>] <B>On Behalf Of </B>praveen
rajendran<BR><B>Sent:</B> Wednesday, March 07, 2007 10:47 PM<BR><B>To:</B>
SAP Workflow Users' Group<BR><B>Subject:</B> Workflow
Configuration<BR><BR></FONT></DIV>Hi,<BR> We are implementing workflow
for our company. We did initial configuration, Prefix number config and
stuffs. We are using 999 in development system, should we use the same in QA
and production system also????? <BR>We have created simple organizational
structure with various positions and users assigned to the positions. how to
transport this Organization structure to QA and PRD systems?? Coz, we don
see any transport requests for this.. even it didn't ask for saving in
transport request when we created it. After transporting, will those
position numbers be same as Position numbers in QA and subsequently PRD???
Because we have directly used these postions as agents in workflow tasks...
Are we going in right track??? What can be other issues we might possibly
run into??? <BR>Thanks for your help...<BR><BR>Regards,<BR> PB
</BLOCKQUOTE></SPAN></DIV></DIV><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"
target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Thanks and Regards,<BR>Praveen Rajendran </BODY></HTML>