Fusion HCM Center of Excellence > Wiki > Guide to Delete Scripts for Fusion Data

Page 1 of 4

Team Collaboration

Fusion HCM Center of...

Guide to Delete Scripts for Fusion Data Overview
Customers who are using HR2HR or the Core HR spreadsheet loader sometimes have a need to delete data that they have bulk loaded. Whilst working with various customers we have developed a set of delete statements that have now been converted into a PLSQL package (hrc_hr2hr_delete_object). The scripts can be run to delete any of the data mentioned regardless of how it was entered. The delete script package will not be provisioned with your new environment because it should be carefully controlled as it potentially opens up the deletion of data to any user that can get access to the Diagnostic Framework. Instead, the XML file that defines the user interface through which the deletes will be invoked will be manually patched on a case by case basis. It is the intention that this should only be made available on Stage environments.

Installation
The installation of the delete scripts should be requested via your CoE representative or via an SR. Once you have confirmation that the scripts on in your environment, continue with the instructions below to view and run the scripts.

Running the Delete Objects Diagnostic

Login as hcm.user Navigate to Help -> Troubleshooting -> Run Diagnostic Tests In the Oracle Diagnostics Framwork Search for Tests -> HCM Delete Object -> Search Select Test and Add to Run In the Choose Tests to Run and Supply Inputs panel Click on Input Status icon to open parameters window Enter Parameters required -> OK Run

Parameters
The delete utility can be invoked by starting the ODF item and entering the appropriate parameters as described below: Type - Object Type, one of the following (must be entered exactly as below): BusinessUnit Department Grade GradeRate Job JobFamily Location Position Person PersonDocumentation WorkRelationshipByPerson - the work relationships for the person will be deleted, the count of objects affected is the number of poeple (not work relationships) ElementEntry Salary AllByPerson Id - Fusion Id value AdditionalCriteria - a sql clause that is used to restrict the records that are deleted GUID - GUID value as used in HR2HR Created By - user who created the data to be deleted Created By Current User (Y/N) Created By HR2HR (Y/N) Commit (Y/N) - If N the diagnostic will indicate howmany top level objects will be removed but will rollback, if Y it will commit The Object Type is mandatory. At least one of the criteria parameters must be entered or have a Y value. The objects that will be deleted and the underlying tables that will be affected are listed below.

Additional Criteria Parameter

The additional criteria parameter can be used to append a sql clause to the selection criteria that is used to determine the records to delete. The table alias given below should be used in conjunction with a column from the table to build up these clauses. For example, if a work relationship was to be deleted for all the people whose last name is "Smith" or who have an email_address including ".smith@oracle.com" use the following clause: (n.last_name = 'Smith' or e.email_address like '%.smith@oracle.com' )

https://beehiveonline.oracle.com/teamcollab/wiki/Fusion+HCM+Center+of+Excellence:G...

6/11/2012

Fusion HCM Center of Excellence > Wiki > Guide to Delete Scripts for Fusion Data

Page 2 of 4

The delete script should be run with Commit = N to ensure that the clause results in the correct number of records before it is rerun with Commit = Y. In the log file the resulting SQL statement is printed as well as an indication of the number of top level objects that will be deleted. Please work with Oracle Support or your CoE representative to retrieve the log file.

Objects and Tables

Person
Selection Criteria Tables per_persons p per_all_people_f paf per_person_names_f n per_email_addresses e Data deleted from PER_DRIVERS_LICENSE_TYPES PER_DRIVERS_LICENSES PER_PERSON_DLVRY_METHODS PER_IMAGES PER_CITIZENSHIPS PER_PASSPORTS PER_VISAS_PERMITS_F PER_SHARE_INFORMATION PER_DISABILITIES_F PER_CONTACT_EXTRA_INFO_F CEI PER_CONTACT_RELSHIPS_F PER_PERSON_TYPE_USAGES_M PER_RELIGIONS PER_PHONES PER_NATIONAL_IDENTIFIERS PER_PERSON_NAMES_F PER_PEOPLE_LEGISLATIVE_F PER_PEOPLE_EXTRA_INFO_F PER_ETHNICITIES PER_EMAIL_ADDRESSES PER_ADDRESSES_F PER_PERSON_ADDR_USAGES_F PER_ALL_PEOPLE_F PER_PERSONS

PersonDocumentation
Selection Criteria Tables HR_DOCUMENTS_OF_RECORD p per_all_people_f paf per_person_names_f n per_email_addresses e Data deleted from HR_DOCUMENTS_OF_RECORD

WorkRelationshipByPerson
Selection Criteria Tables per_periods_of_service p per_all_people_f paf per_person_names_f n per_email_addresses e Data deleted from HRC_LOADER_BATCH_KEY_MAP (for Payroll references) PAY_REL_GROUPS_F PAY_REL_GROUPS_DN PAY_PAY_RELATIONSHIPS_F PAY_PAY_RELATIONSHIPS_DN BEN_REL_ASSIGNMENTS_F BEN_BENEFIT_RELATIONS_F PER_LDAP_REQUESTS PER_ACTION_OCCURRENCES PER_CONTRACTS_F PER_ASSIGN_GRADE_STEPS_F PER_ASSIGNMENT_SUPERVISORS_F PER_ASSIGN_WORK_MEASURES_F PER_ALL_ASSIGNMENTS_M PER_PERIODS_OF_SERVICE

Location
Selection Criteria Tables PER_LOCATION_DETAILS_F_VL ld per_locations l

https://beehiveonline.oracle.com/teamcollab/wiki/Fusion+HCM+Center+of+Excellence:G...

6/11/2012

Fusion HCM Center of Excellence > Wiki > Guide to Delete Scripts for Fusion Data

Page 3 of 4

Data deleted from PER_ACTION_OCCURRENCES PER_ADDRESSES_F PER_LOC_ADDRESS_USAGES_F PER_LOCATION_DETAILS_F_TL PER_LOCATION_EXTRA_INFO_F PER_LOCATION_LEG_F PER_LOCATION_DETAILS_F_TL PER_LOCATION_DETAILS_F PER_LOCATIONS

Jobs
Selection Criteria Tables per_jobs_f_vl j Data deleted from PER_ACTION_OCCURRENCES PER_VALID_GRADES_F PER_JOBS_F_TL PER_JOBS_F

Job Family
Selection Criteria Tables per_job_family_f_vl jf Data deleted from PER_ACTION_OCCURRENCES PER_JOB_FAMILY_F JOBF PER_JOB_FAMILY_F_TL JOBF_TL

Position
Selection Criteria Tables HR_ALL_POSITIONS_F_VL p Data deleted from PER_POSITION_LEG_F PER_POSITION_EXTRA_INFO_F HR_ALL_POSITIONS_F_TL HR_ALL_POSITIONS_F

Business Unit
Selection Criteria Tables FUN_ALL_BUSINESS_UNITS_V bu Data deleted from PER_ACTION_OCCURRENCES HR_ORG_UNIT_CLASSIFICATIONS_F HR_ORGANIZATION_INFORMATION_F HR_ORGANIZATION_UNITS_F_TL HR_ALL_ORGANIZATION_UNITS_F

Department
Selection Criteria Tables per_departments d Data deleted from PER_ACTION_OCCURRENCES HR_ORG_UNIT_CLASSIFICATIONS_F HR_ORGANIZATION_INFORMATION_F HR_ORGANIZATION_UNITS_F_TL HR_ALL_ORGANIZATION_UNITS_F

Grades
Selection Criteria Tables Data deleted from PER_ACTION_OCCURRENCES PER_GRADES_F_TL PER_GRADES_F

Grade Rates
Selection Criteria Tables

https://beehiveonline.oracle.com/teamcollab/wiki/Fusion+HCM+Center+of+Excellence:G...

6/11/2012

Fusion HCM Center of Excellence > Wiki > Guide to Delete Scripts for Fusion Data

Page 4 of 4

per_grades_F_vl g Data deleted from PER_RATES_F_TL PER_RATES_F PER_RATE_VALUES_F

Element Entry
Selection Criteria Tables pay_element_entries_f ee pay_element_types_f et per_persons p per_all_people_f paf per_person_names_f n per_email_addresses e Data deleted from PAY_ENTRY_PCT_DIST PAY_ELEMENT_ENTRY_VALUES_F PAY_ENTRY_USAGES PAY_ELEMENT_ENTRIES_F

Salary
Selection Criteria Tables cmp_salary s per_all_assignments_f a per_persons p per_all_people_f paf per_person_names_f n per_email_addresses e Data deleted from CMP_SALARY_COMPONENTS CMP_SALARY

Limitations
There is no validation to ensure that referential integrity is not broken. For instance this utility will allow a Job to be deleted even though it is referenced by a Work Relationship. For HR2HR this is exactly what is required because we can guarantee that the same ID values will be re-delivered. in the case of non- coexistence customers there needs to be some consideration about which data objects to delete.
Copyright 2008, 2011, Oracle and/or its affiliates. All rights reserved. About Beehive Team Collaboration

https://beehiveonline.oracle.com/teamcollab/wiki/Fusion+HCM+Center+of+Excellence:G...

6/11/2012