<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Gavin,<BR>
<BR>
As you know, we master our HR Org <U>structure</U> in our main development client and transport structure changes up by temporarily removing the TRSP CORR flag in T77S0. But we then allow the Business themselves to <U>maintain their user own assignments</U> to the HR Org Structure <STRONG>directly</STRONG> in Production via an external system which triggers updates using standard HR BAPIs.<BR>
<BR>
This means that user assignments can be manipulated by developers in any test client without impacting the live client at all. It also means that the user assignments in production can be adjusted at a moment's notice (although typically this happens overnight) if so desired by the business.<BR>
<BR>
Various PO* Transactions (e.g. PO13 - Maintain Position) also come in handy when we want to send through manual Transports for specific object types from time to time, particularly when adding relationships.<BR>
<BR>
In general we always place the Transport block flag on in our dev systems to prevent small changes like PFAC Rule Responsibility changes from triggering HR Org '*' Transports from being sent through behind the scenes.<BR><BR>
We keep access to PPOM under strict lock and key because of the bug you mention about 'Display' mode permitting changes because of a bug. So instead we give developers access to PPOSW which really is a Display-only view.<BR>
<BR>
I would recommend you consider using Jobs as well as Org Units and Positions though. They can prove to be quite useful to model expert users groups who float over various work streams.<BR>
<BR>
Regards,<BR>
<BR>
Mike GT<BR>
<BR>
<HR id=stopSpelling>
<BR>
Subject: RE: Org structure maintenance<BR>Date: Tue, 18 Nov 2008 10:39:31 -0600<BR>From: Sandy.Orlandino@us.bosch.com<BR>To: sap-wug@mit.edu<BR><BR><BR>
<STYLE>
.ExternalClass .EC_shape
{;}
</STYLE>
<STYLE>
</STYLE>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:'Times New Roman';}
.ExternalClass span.EC_EmailStyle18
{font-family:'Times New Roman';color:black;font-weight:normal;font-style:normal;text-decoration:none none;}
.ExternalClass span.EC_EmailStyle19
{font-family:Arial;color:navy;font-weight:normal;font-style:normal;text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">We too have HR implemented and only maintain the Org Structure in Production. When necessary, we use the “rhmove” programs to bring structure down to Q and/or Dev. Because otherwise, as Susan mentions, the structure in those boxes very quickly gets beyond ugly!</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> </SPAN></FONT></P>
<DIV>
<FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Sandy L Orlandino <SUP> </SUP></SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"><BR></SPAN></FONT><SUP><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-----------------------------------------------------------------------------------------------------------------</SPAN></FONT></SUP><FONT color=navy><SPAN style="COLOR: navy"> <BR></SPAN></FONT><FONT face=Arial color=navy size=1><SPAN style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">Robert Bosch LLC</SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"> <BR></SPAN></FONT><FONT face=Arial color=navy size=1><SPAN style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">HRIS Manager(RBNA/PER3.21)</SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"> <BR></SPAN></FONT><FONT face=Arial color=navy size=1><SPAN style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">2800 S 25th Ave</SPAN></FONT><FONT face=Arial color=navy size=1><SPAN style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial"> - Broadview, IL 60155 - USA</SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"> <BR></SPAN></FONT><FONT face=Arial color=navy size=1><SPAN style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: Arial">phone: (708) 681-7520 fax: (708) 681-7500</SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"> <BR><A><FONT face=Arial size=1><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: Arial">sandy.orlandino@us.bosch.com</SPAN></FONT></A> <BR><A><FONT face=Arial size=1><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: Arial">www.bosch.us</SPAN></FONT></A> </SPAN></FONT><BR></DIV>
<DIV>
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=EC_MsoNormal><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Keohan, Susan<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 18, 2008 10:14 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> SAP Workflow Users' Group<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Org structure maintenance</SPAN></FONT></P></DIV>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">Hi Gavin,</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">We do not transport our org structure – although I have done so in the past. But we have HR implemented, and it makes no sense for those folks to be creating and transporting positions, jobs, etc.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">As a result, our Dev box Org structure has gotten butchered over the years, and it’s a real struggle to keep a semblance of reality, but then again, we don’t have to worry about a ‘real’ org structure where developers like to play.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">We assign users in our various systems via PA0105 – and again, no transports. Not sure if this is a Basis deal or what. Our user ids are assigned to Persons, who hold Positions, which are encompassed by Jobs.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">Kind of different from the traditional layout, but it works *<B><SPAN style="FONT-WEIGHT: bold">pretty much</SPAN></B>* for us.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">We all use PLVAR 01. I know that additional Plan Versions are possible, but WF wants version 01, and since we have peaceful co-existence with HR, we only need that one version.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"><BR>Hope this helps,</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">Sue</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<DIV>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">----</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Susan R. Keohan</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">SAP Workflow Specialist</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Enterprise</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black"> Applications</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Information Services Department</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">MIT Lincoln Laboratory</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">244 Wood Street</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">, LI-200</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Lexington</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">, MA</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">. 02420</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">781-981-3561</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">keohan@LL.MIT.EDU</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=3><SPAN style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT></P></DIV>
<DIV>
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=EC_MsoNormal><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Gavin Mooney<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, November 17, 2008 9:58 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> SAP Workflow Users' Group<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Org structure maintenance</SPAN></FONT></P></DIV>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">Hello everyone, </SPAN></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">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></FONT><BR>
<FONT face=Helv size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Helv">Looking forward to hearing your opinions and experiences. <BR>Many thanks,<BR>Gavin</SPAN></FONT><BR></DIV><br /><hr />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></body>
</html>