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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><span><font color="#0000ff" face="Arial" size="2">Hello,</font></span></div>
<div><span><font color="#0000ff" face="Arial" 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 color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" 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 color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">Cheers,</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Ronen</font></span></div><div><span class="e" id="q_111300ab3894691c_1">
<blockquote style="margin-right: 0px;">
<div></div>
<div dir="ltr" align="left" lang="en-us"><font face="Tahoma" size="2">-----Original Message-----<br><b>From:</b>
<a href="mailto:sap-wug-bounces@mit.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
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