Overview of the Purge Person Data in Test Environments Process
During implementation and testing, you may want to load, test, purge, and reload HCM data. To purge person data from test environments, use the Purge Person Data in Test Environments process.
This topic explains how to enable the process and identifies the data that it purges.
Enabling the Purge Process for Person Data
The Purge Person Data in Test Environments process is now enabled by default on the test or stage environments.
Purging Person Data
The Purge Person Data in Test Environments process purges person records, including passports, citizenship records, licenses, emails, addresses, national identifiers, and extra information type data. It also purges dependent data of the following types:
-
Absences
-
Assignments, including extra information type data
-
Benefits
-
Calculation cards
-
Compensation
-
Contacts and contact relationships
-
Documents and attachments
-
Element entries
-
Goals
-
Payroll relationships
-
Performance records
-
Roles and user details
-
Talent profiles
-
Work relationships
Deletion requests are generated for user accounts in the test environment. To process these requests, you must run the Send Pending LDAP Requests process when Purge Person Data in Test Environments completes.
Exclusions from the Purge Process
The Purge Person Data in Test Environments process doesn't purge data of the following types:
-
Predefined person data.
-
Contacts enrolled in a Benefits program.
-
Oracle Trading Community Architecture (TCA) data.
The process inactivates dependent TCA records in the TCA tables but doesn't purge them.
If processed payroll actions are associated with a worker, then the worker isn't purged. You must roll back relevant payroll processes before you can purge such workers.