Professional Documents
Culture Documents
Diagnostic Framework 2
Overview 2
Security Requirements 2
Purge Person 6
Overview 6
Additional Notes 6
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.
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:
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.
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.
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.
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.
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.
For dependent data in TCA, the process inactivates the records in the TCA tables.
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.
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%
To delete all person records where the last name starts with John:
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.
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