Setting up the Org Chart - Config & Master Data

[Jose Burgman [AST]]

Both workflow and HR use the same tables for org structure. So when you =
transport an org object it wipes out all info if it already exists and =
replaces it with the new info..... Which is why its a good idea to =
maintain your org structure only on one client and update from there....
 
If you do a search in the archives, you'll find a more detailed =
discussion which occurred about September about a similar issue.
 
Jose
 
-----Original Message-----
From: Abby Dywan [mailto:abby.dywan at us.ibm.com]
Sent: Wednesday, December 04, 2002 10:05 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Setting up the Org Chart - Config & Master Data
 
 
Hi all -
 
I have noticed something over the past few days as we are preparing our
training for end users prior to go live and need to know if I need to be
worried about this.
 
We have determined that we will construct the org chart, creating =
positions
and organizational units using transaction PPOMW (workflow org chart -
treats as configuration) and adding in users via PPOME (the HR org =
chart,
which treats users as master data).
 
What's odd is that in our training environment, every time we seem to =
make
a transport into the org chart with new positions/ org units / whatever, =
it
appears to wipe out all the master data (users).  I haven't noticed this
issue in our QA environment or in our Dev client, but that may simply be
because we don't have the same volume of users... it's much lower in =
those
clients.
 
I would hate to have to re-populate the org chart in production with =
users
every time we add or change a position... it would become extremely time
consuming.  Is this problem just a figment of my imagine - or DOES =
config
org chart changes wipe out anything established via master data?
 
Any help would be greatly appreciated!  Thanks so much!
Abby  :)
______________________________________________
 
"This information is intended only for the person or entity to which it is addressed and
may contain private, confidential, proprietary and/or privileged material and may be subject
to confidentiality agreements.
 
Any review, retransmission, dissemination, or any other use of or taking of any action in
reliance upon this information, by persons or entities other than the intended recipient,
is prohibited.
 
If you received this in error, please contact the sender and delete the material from all
storage media.
 
The company is neither liable for proper, complete transmission of the information contained
in this communication, any delay in its receipt or that the mail is virus-free"