Diagnostic

Test: Person
Diagnostic
Auto Correct
Oracle Fusion Human Capital Management

ORACLE W HITE PAPER MAY 27, 2019

DISCLAIMER
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

2 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

INTRODUCTION

Customers can run the Person Diagnostic Auto Correct diagnostic test to view and correct person-
related data corruptions for which no decision-related input is needed.

FAQS FOR THE DIAGNOSTIC TEST

What data corruption does this diagnostic test deal with?

This diagnostic test can be used to view and resolve person-related data corruptions for which no decision-related input is needed.
What are the input parameters required for this diagnostic test?

The input parameters are person number or person numbers and run mode.

Person number or person numbers: This parameter specifies the person number or person numbers for which the diagnostic test is run
to detect any corruptions. The user can enter a single person number (for example: 123), a comma-separated list of person numbers (for
example: 123,456,789), or keep the parameter blank. If left blank, the diagnostic test will be run for the entire population.

Run mode: The two options for this parameter are Validate and Commit. If the diagnostic test is run in Validate mode, the changes
made by the diagnostic test will be rolled back at the end instead of being committed to the database. If the diagnostic test is run in
Commit mode, the changes made by the diagnostic test will be committed to the database.

What is the output of this diagnostic test?

This diagnostic test will generate relevant messages related to the data modifications based on the parameters provided by the user.

If the diagnostic test is run in validate mode, the test will indicate a rollback at the end. However, if the test is run in commit mode, the
test will indicate that the changes are committed.

Does running this diagnostic test lead to any changes in data?

Yes, running this diagnostic test will cause data changes in the tables where the corruption is present.

Any data that is changed because of this diagnostic test will first be saved in the appropriate backup tables. This is to make sure that the
original data is not lost.

The user can first try running the diagnostic test in Validate mode to verify the data changes and make sure the changes were as per
expectations (this can be verified from the messages generated by the diagnostic test). After verifying that the data changes were the
intended modifications, the user can run the diagnostic test in Commit mode with the other parameters unchanged. The user can also
choose to run the diagnostic test in Commit mode directly.

How to check whether the corruptions are corrected after this test was run?

Firstly, the user must check the messages generated by the diagnostic test to confirm whether the changes have been successfully
completed. The user can then run this same diagnostic test in Validate mode for the person or persons for whom the changes were
made. The updated messages will indicate if the data was successfully corrected in the previous run.

RUNNING THE DIAGNOSTIC TEST

1. Click the user name in the global header region, and then click Run Diagnostics Tests from the Settings and Actions menu.

3 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

 2. The Diagnostic Dashboard page is displayed.

3. Search for the Person Diagnostic Auto Correct test in the Search for Tests section. From the search result, select the check
box and click Add to Run. This will add the test to the Choose Tests to Run and Supply Inputs section on the right panel.

4 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

 4. Add input parameters if needed by clicking the icon under the Input Status column in the Choose Tests to Run and Supply
Inputs section. A dialog box is displayed that allows you to enter the input values.

5. Enter a run name in the Run Name box, and then click Run. The run name is not mandatory, but is helpful for tracking.

5 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

 6. Continue refreshing the Diagnostic Test Run Status table until your test completes. The Completed status is displayed under
the Execution Status column of the table.

7. Click the icon under the Report column in the Diagnostic Test Run Status table. A page is displayed that contains the meta
details of the test that was run.

6 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

 8. Click the link under the Execution ID column of the table in the Executions area. This will load the execution output of the
test. The following screenshot displays a part of this output.

7 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

8 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct
 9. You can skip the meta details of the test that was run and directly access the actual diagnostic test output. To do this, expand
the test you ran in the Diagnostic Test Run Status table. Then, click the icon under the Report column of the actual diagnostic
test itself.

9 W HITE PAPER / Diagnostic Test: Person Diagnostic Auto Correct

ORACLE CORPORATION

Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA

Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com

CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle

Copyright © 2019, 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 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 means, electronic or mechanical, for any purpose, without our prior written permission.
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. 0519
Diagnostic Test: Person Diagnostic Auto Correct
May 2019
Author: Aaditya Gogia