2007 Dec 22 8:09 AM
Periodically we are requested to refresh sap systems and wipe out the hr data after which that system can be used by other teams and also by hr users to simule scenarios with their own no real hr data.
The current procedure is a system refresh after which we execute rpudelpn, rpudel20, and rpuauddl to remove all hr data. That execution of 3 programs takes about a week, because those programs take every ee and go over each piece of data in the system, e.g. each infotype, to remove any entry that belong to that ee, before jumping into the next ee.
Our intention is to create a program to directly empties all hr data tables via SQL to speed things up.
I was wondering if somebody may have a list of all hr D A T A tables in the system. I know about these:
pa*
hrp*
ppoix
ppopx
asshr
assob
pcl1 to pcl5
2007 Dec 22 12:09 PM
hi,
Got to say I think that it's a dangerous move to do what you propose.
Standard advice is to not directly update/modify/delete from transactional tables unless strictly necessary and to test any proposed solutions to the Nth degree plus to prevent the possiblity of remaining data inconsistency (which SAP will not support you in resolving!)
I would be tempted to talk to SAP or a good HR Consultant about an alternative approach, there may be a standard way of resolving the long runtimes you are seeing from your current solution.
I would recommend to use SQL to clear data only in one case: if I was leaving the company in a very angry mood... and moving me to another country... in any other case, I would follow Rosie's advice.
In any case, if they force you to do that thing using SQL, be sure they say it to you in a form you can prove is not your fault after the disaster...
cheers,
siva.
2007 Dec 22 12:09 PM
hi,
Got to say I think that it's a dangerous move to do what you propose.
Standard advice is to not directly update/modify/delete from transactional tables unless strictly necessary and to test any proposed solutions to the Nth degree plus to prevent the possiblity of remaining data inconsistency (which SAP will not support you in resolving!)
I would be tempted to talk to SAP or a good HR Consultant about an alternative approach, there may be a standard way of resolving the long runtimes you are seeing from your current solution.
I would recommend to use SQL to clear data only in one case: if I was leaving the company in a very angry mood... and moving me to another country... in any other case, I would follow Rosie's advice.
In any case, if they force you to do that thing using SQL, be sure they say it to you in a form you can prove is not your fault after the disaster...
cheers,
siva.