<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helv;
panose-1:2 11 6 4 2 2 2 3 2 4;}
@font-face
{font-family:Helv;
panose-1:2 11 6 4 2 2 2 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecmsonormal, li.ecmsonormal, div.ecmsonormal
{mso-style-name:ec_msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecmsohyperlink
{mso-style-name:ec_msohyperlink;}
span.ecmsohyperlinkfollowed
{mso-style-name:ec_msohyperlinkfollowed;}
span.ecemailstyle18
{mso-style-name:ec_emailstyle18;}
span.ecemailstyle19
{mso-style-name:ec_emailstyle19;}
p.ecmsonormal1, li.ecmsonormal1, div.ecmsonormal1
{mso-style-name:ec_msonormal1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecmsohyperlink1
{mso-style-name:ec_msohyperlink1;
color:blue;
text-decoration:underline;}
span.ecmsohyperlinkfollowed1
{mso-style-name:ec_msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecemailstyle181
{mso-style-name:ec_emailstyle181;
font-family:"Times New Roman","serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.ecemailstyle191
{mso-style-name:ec_emailstyle191;
font-family:"Arial","sans-serif";
color:navy;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle29
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<div>
<div>
<p class=MsoNormal><span style='color:#1F497D'>Gavin,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>We have also implemented HR and
so in production our org is maintained by Org Management. Our Integ
system is occasionally refreshed as a copy of production, so that system is a
good one for testing. Dev is another story. I’m afraid that
our Dev system is a hodge podge of orgs that each of us has created for the purposes
of unit testing. As such we do very limited testing in Dev.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Sherie</span><span
style='color:black'> </span><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sherie Munday<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Workflow Developer/ Analyst <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Air Products & Chemicals, Inc.<o:p></o:p></span></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Gavin
Mooney<br>
<b>Sent:</b> Monday, November 17, 2008 9:58 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Org structure maintenance</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal> <span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>Hello
everyone, </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>We're trying
to decide how to manage our org structure. The actual structure is very simple,
just based on Org Units, Positions and Users (we're not implementing SAP HR
here). We're on ECC 6.0 / WAS 700. I've been reading some former WUG posts and
the SAP documentation but still have the following questions and I'd like to
know what other projects have done and what is recommended please. </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>1) Where
to maintain the org structure. <br>
As we don't have a Production environment yet we are maintaining it in
Development. The Transport Connection is set to automatic (i.e. T77S0 entries
for TRSP CORR, TRSP STOBJ and TRSP WFOBJ are all set to space) so the system
asks for a transport for any changes to the org strucure. This seems to be
working ok for now, but I see that we could specify "Transport via object
lock (repair flag)" or "No automatic transport connection" and
then manually run RHMOVE50 or RHMOVE30 to transport to other environments. What
are the pros/cons of these other options? </span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>Although
I see that some projects choose to maintain the org structure in Production
because it is faster, allows for more reactive fixes, etc. I don't think we
will need to do that as our structure is very simple and hopefully won't change
that often. Also if we maintained it in Prod we would have to merge any changes
back to Dev for testing. Sound ok? </span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>2) User
assignments<br>
At the moment the system asks for a transport whenever a user is assigned to a
position. So even for unit tests in our Dev environment we need to assign the
user in the golden client and then run SCC1 to move the changes across to the
unit test client. Ideally we'd like to change this so that we can change user
assignments directly in the unit test client (and in the future we'd want to
maintain user assignments direct into production). Is this possible and if so
how? </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>Actually
what happens is if I try to change a user assignment in the unit test client I
can do it in PPOMW, then when I click on save the system pops up a message
saying that the client has status not modifiable, but then saves the data
anyway. So we can do it, but it's just not very intuitive - ideally we'd want
to be able to do it without getting the popup (and without opening up the whole
client of course). </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>Also - we
don't want to tranport the dev user assignments to production when we transport
the org structure, so do we need to maintain entries in OOTR or is there a
different / better way? </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>3) Plan
versions<br>
We would potentially like to maintain different plan versions (for example as
backups) and so have set up number assignment across all plan versions (Table
T77S0 entry NUMRG COMP = 'X'). </span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Helv","sans-serif"'>Looking
forward to hearing your opinions and experiences. <br>
Many thanks,<br>
Gavin</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Read
amazing stories to your kids on Messenger <a
href="http://clk.atdmt.com/UKM/go/117588488/direct/01/" target="_new">Try it
Now!</a><o:p></o:p></span></p>
</div>
</body>
</html>