You are on page 1of 14

Purging HCM Data from Test and Stage Environments

ORACLE WHITE PAPER | DECEMBER 2016


Table of Contents

Purging HCM Data from Stage and Test Environments 1

Diagnostic Framework 2

Overview 2

Security Requirements 2

Submitting a Purge Process 2

Purge Person 6

Overview 6

Additional Notes 6

Submitting the Purge Person Process 7

Purge Person Parameters 7

Appendix - Tables Purged Using the Person Purge Process 9

PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Purging HCM Data from Stage and Test Environments
During system implementation and testing, developers often need iteratively to load, test, purge, and
reload HCM data. This document describes how to purge HCM data from stage and test environments

The Diagnostic Framework is used to deliver the purge functionality, which is not available by default.
You must raise a Service Request (SR) to have this functionality enabled on your stage and test pods.
Once the function is enabled, you can run the purge-data process as often as required.

Note: The purge functionality is not available in production environments.

1 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Diagnostic Framework

Overview
The Diagnostic Framework is a self-service application that allows you to identify and resolve issues in your
environments.

Security Requirements
The following Job Roles are required to access the Diagnostic Framework:

Application Diagnostics Regular User


Application Diagnostics Viewer

Submitting a Purge Process


Select Run Diagnostic Tests under Troubleshooting in the Setting and Actions menu. To access this menu,
click your user name at the top right of the page.

Figure 1: Settings and Actions


Navigation: Click user name

The Run Diagnostics Tests task opens the Diagnostic Dashboard.

2 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Figure 2: Diagnostic Dashboard
Navigation: User > Run Diagnostics Tests

Follow these steps, which apply regardless of the process being submitted:

1. Search for the process by entering the name in the Test Name search field and clicking Search. For example,
enter Purge Person.

2. Select the check box in the Select column to the left of the test name and click Add to Run.

The selected process appears in the Choose Tests to Run and Supply Inputs section.

3 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


3. To review the parameter values, click the green check mark ( ) icon in the Input Status column.

4. In the Input Parameters dialog box, review the available parameters and:

a. Select the Include check box for the parameters that you want to use.

b. Provide values in the New Value column to identify the records that you want to purge.

5. Click OK when you have supplied the parameter values. The Input Parameters dialog box closes.

4 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


6. You can enter a name for your test run in the Run Name field. Alternatively, leave this field blank to generate a
name automatically.

7. Click Run to submit the purge process.

A confirmation dialog box shows the test run name. Click OK.

8. Click Refresh on the Diagnostic Test Run Status table to retrieve the run results.

9. Click the Report icon for the purge process to review the log.

5 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Purge Person

Overview
The intended usage is to purge a person, or group of people, and most dependent data:
Absences
Benefits
Compensation
Documents and Attachments
Performance Data
Goals and Performance
Talent Profile
Payroll Relationships
Element Entries
Calculation Cards
Addresses
Assignments (including EIT)
Work Relationships
Contacts and Contact Relationships
Worker Personal Information (including passport, citizenship, e-mails, licenses, NID, EIT, and so on)
Roles and User Details
You can run the Purge Person process initially without committing the changes so that you can review the list of
people whose data will be purged. Once you have reviewed this list, you can run the process in commit mode to
purge the identified person data.

The following sets of people are not purged:

Predefined Person Data

Identified using the condition CREATED_BY = SEED_DATA_FROM_APPLICATION.

People Loaded Using HCM File-Based Loader (FBL)

Identified by the entries in HRC_LOADER_BATCH_KEY_MAP.

Additional Notes
Payroll Data

If processed payroll actions are associated with the worker, then the worker is not purged. You must roll back all
payroll processes before you can use the Purge Person process to purge such workers.

Data Not Deleted


TCA Data

For dependent data in TCA, the process inactivates the records in the TCA tables.

6 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


User Data

User accounts in OIM are not deleted.

For a complete clean up of user details and to ensure a smooth reload, you must raise a service request for some
user cleanup that is not possible in an automated manner.

See MOS document (Doc ID 1494265.1) for details.

Submitting the Purge Person Process


To submit the Purge Person process you must have access to the Diagnostic Dashboard. For instructions, see
Submitting a Purge Process on page 2.

Purge Person Parameters


Parameters to the Purge Person process are:

Valid
Parameter Description
Values

Additional Criteria SQL query Provide a SQL query to return the person IDs of all the people you want to purge.

Commit Y, N Setting Commit to N allows you to review the people who would be purged by the process
without removing any data. To purge the data, you set Commit to Y.

Person Id Comma- Provide one or more person IDs to identify the people whose data is to be purged. Separate
separated IDs multiple IDs with commas. For example:
100010034148157,100010034148169,100010034148181,100010034148192

Person Number Comma- Provide complete or partial person numbers for the people whose data is to be purged. The
separated wildcard character % can be used when supplying partial values.
Separate multiple values with commas. For example: PER%,Test%,%abc%

Additional Criteria Examples

To delete all person records where the last name starts with John:

SELECT papf.person_id FROM per_all_people_f papf, per_person_names_f ppnf WHERE


ppnf.last_name like 'John%' and ppnf.person_id = papf.person_id

To delete all person data from the system:

SELECT person_id FROM per_all_people_f

7 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Considerations

Due to the number of records to potentially be deleted for each person, this process can take some time to
complete.

Do not cancel the process, the final stages of this process perform some clean up operations which will not occur if
you cancel the process. The cleanup will occur the next time you run the process, regardless of the targeted
population, but this will increase the time it takes to complete the process.

8 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Appendix - Tables Purged Using the Person Purge Process
ANC_PER_ABS_CERTS HRR_DASHBOARDS
ANC_PER_ABS_ENTRIES HRR_MEETINGS
ANC_PER_ABS_ENTRY_DTLS HRR_MEETING_FACILITATORS
ANC_PER_ABS_MATERNITY HRR_MEETING_PARTICIPANTS
ANC_PER_ABS_PLAN_ENTRIES HRR_MEETING_REVIEWEES
ANC_PER_ABS_PLN_SUMM_ENT HRQ_QSTN_RESPONSES
ANC_PER_ABS_TYP_LNKG HRQ_QSTNR_PARTICIPANTS
ANC_PER_ABS_TYPE_ENTRIES HRQ_QSTNR_RESPONSES
ANC_PER_ACCRUAL_ENTRIES HRT_NOTES
ANC_PER_ACRL_ENTRY_DTLS HRT_POOL_MEMBERS
ANC_PER_EVENTS HRT_POOL_OWNERS
ANC_PER_PLAN_ENROLLMENT HRT_PROFILE_INTERESTS
BEN_BATCH_ACTN_ITEM_INFO HRT_PROFILE_ITEMS
BEN_BATCH_BNFT_CERT_INFO HRT_PROFILE_KEYWORDS
BEN_BATCH_COMMU_INFO HRT_PROFILE_MATCH_CRIT
BEN_BATCH_DPNT_INFO HRT_PROFILE_RELATIONS
BEN_BATCH_ELCTBL_CHC_INFO HRT_PROFILES_B
BEN_BATCH_ELIG_INFO HRT_PROFILES_TL
BEN_BATCH_LER_INFO HWM_TM_REC
BEN_BATCH_RATE_INFO HWM_TM_REC_GRP
BEN_BENEFIT_ACTIONS HWM_TM_REC_GRP_SUM
BEN_BENEFIT_RELATIONS_F HWM_TM_REC_GRP_USAGES
BEN_CVRD_DPNT_CTFN_PRVDD HWM_TM_REP_ATRB_USAGES
BEN_ELCTBL_CHC_CTFN HWP_ARCH_DATA_MINING_REASONS
BEN_ELIG_CVRD_DPNT HWP_ARCH_DATA_MINING_RESULTS
BEN_ELIG_DPNT HWP_DATA_INPUT_VALUES
BEN_ELIG_FLX_CRDT_POOL_CHC HWP_DATA_MINING_REASONS
BEN_ELIG_PER_ELCTBL_CHC HWP_DATA_MINING_RESULTS
BEN_ELIG_PER_F HWP_WHATIF_PRED_DETAILS
BEN_ELIG_PER_OPT_F PAY_ASSIGNED_PAYROLL
BEN_ELIG_RSLT_F PAY_ASSIGNED_PAYROLLS_DN
BEN_ENRT_BNFT PAY_ASSIGNED_PAYROLLS_DN_
BEN_ENRT_RT PAY_ASSIGNED_PAYROLLS_F
BEN_EXTRACT_DETAILS_ARCH PAY_ASSIGNED_PAYROLLS_F_
BEN_EXTRACT_REQ_DETAILS PAY_DATES
BEN_FLEX_CRDT_LDGR PAY_DIR_CARD_COMPONENTS_F
BEN_PER_BENEFIT_GROUP_F PAY_DIR_CARD_COMPONENTS_F_
BEN_PER_BNF_ORG PAY_DIR_CARDS_F
BEN_PER_BNFTS_BAL_F PAY_DIR_CARDS_F_
BEN_PER_IN_LER PAY_DIR_COMP_DETAILS_F
BEN_PER_LE_HABITS_COV_F PAY_DIR_COMP_DETAILS_F_
BEN_PERSON_ACTIONS PAY_DIR_REP_CARD_USAGES_F
BEN_PIL_ELCTBL_CHC_POPL PAY_DIR_REP_CARD_USAGES_F_
BEN_PL_BNF PAY_DIR_REP_CARDS_F
BEN_PL_BNF_CTFN_PRVDD PAY_DIR_REP_CARDS_F_

9 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


BEN_PRTT_ENRT_ACTN PAY_ELEMENT_ENTRIES_F
BEN_PRTT_ENRT_CTFN_PRVDD PAY_ELEMENT_ENTRIES_F_
BEN_PRTT_ENRT_RSLT PAY_ELEMENT_ENTRY_VALUES_F
BEN_PRTT_LEG_DISCMR_ACTN PAY_ELEMENT_ENTRY_VALUES_F_
BEN_PRTT_RT_VAL PAY_ENTRY_PCT_DIST
BEN_PTNL_LER_FOR_PER PAY_ENTRY_PROC_DETAILS
BEN_REL_ASSIGNMENTS_F PAY_ENTRY_USAGES
BEN_REPORTING PAY_PAY_RELATIONSHIPS_DN
CMP_BUDGET_AUDIT PAY_PAY_RELATIONSHIPS_F
CMP_BUDGET_USAGES PAY_PERSON_PAY_METHODS_F_
CMP_CWB_ALERTS PAY_RANGE_ITEMS_F
CMP_CWB_APPROVAL_HISTORY PAY_RANGE_ITEMS_F_
CMP_CWB_AUDIT PAY_REL_GROUPS_DN
CMP_CWB_FEEDBACK PAY_REL_GROUPS_F
CMP_CWB_HRCHY PAY_RETRO_ENTRIES
CMP_CWB_INTCPT_APPR_DTLS PAY_VALUE_DEFINITIONS_F
CMP_CWB_MODEL_B PAY_VALUE_DEFINITIONS_F_
CMP_CWB_MODEL_DTL PER_ABSENCE_CASES
CMP_CWB_MODEL_TL PER_ACTION_OCCURRENCES
CMP_CWB_PERF_RATINGS PER_ADDRESSES_F
CMP_CWB_PERSON_DEFAULTS PER_ALL_ASSIGNMENTS_M
CMP_CWB_PERSON_ELEMENTS PER_ALL_PEOPLE_F
CMP_CWB_PERSON_INFO PER_ALLOCATED_CHECKLISTS
CMP_CWB_PERSON_RATES PER_ALLOCATED_TASKS
CMP_CWB_POST_LOG PER_ASG_RESPONSIBILITIES
CMP_CWB_POST_PERSON PER_ASSIGN_GRADE_STEPS_F
CMP_CWB_PROMOTIONS PER_ASSIGN_WORK_MEASURES_F
CMP_CWB_RANKS PER_ASSIGNMENT_EXTRA_INFO_M
CMP_CWB_SUMMARY PER_ASSIGNMENT_SUPERVISORS_F
CMP_CWB_SWITCH_MANAGERS PER_CITIZENSHIPS
CMP_DYNAMIC_FILTER PER_CONTACT_EXTRA_INFO_F
CMP_INTERCEPT_APPROVERS PER_CONTACT_RELSHIPS_F
CMP_PERSON_BUDGETS 'PER_CONTACT_RELSHIPS_F
CMP_PROCESS_DATA PER_CONTRACTS_F
CMP_PROCESS_RUN_INFO PER_DELEGATED_ROLES
CMP_SALARY PER_DISABILITIES_F
CMP_SALARY_COMPONENTS PER_DRIVERS_LICENSE_TYPES
CMP_SALARY_EXPORT PER_DRIVERS_LICENSES
CMP_STOCK_DETAILS PER_EMAIL_ADDRESSES
CMP_TCS_PER_ITEM_VALUE PER_ETHNICITIES
CMP_TCS_PER_PERD PER_IMAGES
CMP_TCS_PER_PERD_STMT PER_KEYWORDS
CMP_TCS_PER_PERD_STMT_CAT PER_LDAP_REQUESTS
CMP_TCS_PER_ROW_VALUES PER_LDAP_ROLE_MEMBERSHIPS
CMP_TCS_REPORT_DETAILS PER_LDAP_USERS
CMP_VC_PER_ELIG_PLANS PER_MANAGER_HRCHY_DN
FND_ATTACHED_DOCUMENTS PER_NATIONAL_IDENTIFIERS
FND_DOCUMENTS PER_PASSPORTS

10 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


FND_DOCUMENTS_TL PER_PEOPLE_EXTRA_INFO_F
FND_SESSION_USERS PER_PEOPLE_LEGISLATIVE_F
HMO_MODEL_PLAN_DETAILS PER_PERIODS_OF_SERVICE
HMO_MODEL_PLANS_B PER_PERSON_ADDR_USAGES_F
HMO_MODEL_PLANS_TL PER_PERSON_DLVRY_METHODS
HR_DOCUMENT_DELIVERY_PREFS PER_PERSON_NAMES_F
HR_DOCUMENTS_OF_RECORD PER_PERSON_TYPE_USAGES_M
HRA_EVAL_ITEMS PER_PERSONS
HRA_EVAL_PARTICIPANTS PER_PHONES
HRA_EVAL_RATINGS PER_PORTRAIT_CARD_CONFIG
HRA_EVAL_ROLE_ACTIONS PER_PORTRAIT_PREFERENCES
HRA_EVAL_ROLES PER_RELIGIONS
HRA_EVAL_SECTIONS PER_SCHEDULE_ASSIGNMENTS
HRA_EVAL_STEPS PER_SHARE_INFORMATION
HRA_EVALUATIONS PER_USER_HISTORY
HRG_GOAL_ACCESS PER_USER_ROLES
HRG_GOAL_ACTIONS PER_USERS
HRG_GOAL_ALIGNMENTS PER_VISAS_PERMITS_F
HRG_GOAL_TARGET_OUTCOMES
HRG_GOALS
HRM_PLANS
HRM_PLAN_CANDIDATES
HRM_PLAN_OWNERS

11 | PURGING HCM DATA FROM TEST AND STAGE ENVIRONMENTS


Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

blogs.oracle.com/oracle
Copyright 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.

oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116

HCM Purge Data


December 2016