Oracle Fusion HCM maintains significant amounts of employee personal and sensitive data that frequently persist beyond mandated retention periods. The absence of automated and consistent mechanisms to identify, anonymize, or eliminate outdated information results in compliance concerns, heightened security risks, and reliance on manual, error-prone processes. To address these challenges, organisations require a structured approach to person information removal in Oracle HCM—one that is secure, standardized, and auditable, ensuring personal data is managed and removed in accordance with privacy regulations and organizational policies.

Purging the Inactive employee personal details like First name, Last name, Nationality details, DOR and other details.

Here are the steps followed to configure and successfully execute Person Information Removal in Oracle HCM. This guide outlines the complete setup, from role creation to running the removal process.

Step 1: Create a Custom HCM Job Role

Create a new “HCM Job Role” and add the following Function Security Policies:

1. Configure Person Information Removal Policies

(HRC_CONFIGURE_PERSON_INFO_REMOVAL_POLICIES_PRIV)

• Manage Data Exchange Work Area (HRC_MANAGE_DATA_EXCHANGE_PRIV)
• Upload Data for Human Capital Management file-based Import

(HCM_DATALOADER_IMPORT_RWD)

• Report Person Information Removal Processes

(ORA_HRC_REPORT_PERSON_INFO_REMOVAL_PROCESSES)

• Report Person Information Removal Templates

(ORA_HRC_REPORT_PERSON_INFO_REMOVAL_TEMPLATES)

Step 2: Configure Role Hierarchy

Navigate → Security Console → Roles → Create Role, then configure the Role Hierarchy as follows:

1. Add Load Data using HCM Data Loader (ORA_HRC_LOAD_DATA_USING_HDL)
2. Remove Person Information (ORA_HRC_REMOVE_PERSON_INFORMATION)
3. Generate Remove Person Information

(ORA_HRC_GENERATE_REMOVE_PERSON_INFORMATION_FILE)

Step 3: Add Data Security Policy

Create a Data Security Policy with these settings:

1. Data Resource: Person Detail (PER_ALL_PEOPLE_F)
2. Condition: All Values
3. Action: Remove Person Information

Step 4: Final Role Configuration

Add Remove Person Information (ORA_HRC_REMOVE_PERSON_INFORMATION) under the role hierarchy if both Report and Remove modes are required. Assign the role to the required user under the Users tab.

Note: Only the assigned user can perform the configuration of personal information removal policy and able to submit the configured process.

Navigate to Workforce Structure → Data Roles and Security:

Search for the newly created role. Grant access to “View All Person”

Registrations closing soon! Book your spot for the upcoming Oracle Cloud Live Trainings.

Step 5: Sync Role Changes

Run the ESS job: “Import User and Role Application Security Data” This synchronizes the newly created job roles.

Step 6: Configure Person Information Removal Policy

1. Navigate to: My Client Groups → Data Exchange (scroll to the end)

2. Click Configure Person Information Removal Policies → Create

3. Policy Setup:

1. Enter Name and Code.
2. Select Category:
   i. Worker – for employees
   ii. Candidate – for active ORC candidates

4. Click OK

5. Business Object Configuration. Select the business objects containing data to be removed.

6. Navigate to Rules. Enable the template and save.

Once enabled, the Removal Policy becomes active and can’t be editable.

Step 7: Execute Remove Person Information Process

1. Navigate again to: My Client Groups → Data Exchange → Remove Person Information

2. Click Remove Person Information

3. Enter the following details:

1. Process Name
2. Template (created earlier)
3. Person Number (only terminated employees are eligible)
4.  Process Mode:

i. Remove – Fetches and removes data using HDL

ii. Report – Fetches data only (no removal)

iii. Review the parameters and click Submit.

Step 8: Output and Logs

1. For Remove mode: Access the Disposal Process Log.

2. For Report mode: Download the Data Files and review the Process Log.

This completes the end-to-end configuration and execution of Person Information Removal in Oracle HCM.

Author: Yamini Vemula Seshadri is an Oracle Technical Consultant at Fusion Practices