Diagnostic

Test:
Employment
Diagnostic
Auto Correct
Oracle Fusion Human Capital Management

ORACLE TECHNICAL BRIEF JUNE 29, 2022

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 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct

INTRODUCTION

Customers can run the Employment Diagnostic Auto Correct diagnostic test to view and correct
employment-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 employment-related data corruptions for which no decision-related input is
needed from the user.

The diagnostic test currently covers these types of data corruption:

Type Number Type of Corruption Corruption Description

1 Assignments with ID flexfield number Assignments having the People Group ID

issues populated must have the same ID flexfield
number as the corresponding row in the
People Group table. If the People Group
ID isn’t populated, then the ID flexfield
number must match the People Group
flexfield structure set at the legal
employer level. If nothing is set at the
legal employer level, then the ID flexfield
number must match the People Group
flexfield structure set at the enterprise
level. If this isn’t the case, then its data
corruption.

2 Assignment Business Unit not in The Business Unit ID of assignments and

synchronization with work terms their corresponding work term rows must
match. If this isn’t the case, then its data
corruption.

3 Assignments with ID flexfield number not
available in the PER_PEOPLE_GROUPS
table
Assignments having the People Group ID
populated must have the same ID flexfield
number as the corresponding row in the
People Group table. If the ID flexfield
number in the assignment table is
something else, then its data corruption.

4 Terminated workers with supervisor Terminated workers must not have a

records supervisor assigned to them after
termination. If this is the case, then its
data corruption.

5 Set of Books ID is null If a worker has an expense account, then

the worker’s Set of Books ID can’t be null.
If this is the case, then its data corruption.

3 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct

 6 Work term records incorrectly populated
for two tier employment model
7 Mismatch in status between the
assignment and work term
8 Incorrect assignment freeze dates
9 Out of synchronization primary flags
10 Assignments with invalid Action
Occurrence ID
11 Person Type ID not in synchronization
with System Person Type ID
12 Contract end date before End of Time
(EOT)
13 Working hour pattern record not starting
on assignment start date
4 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct
Work term rows can’t be populated with
attributes, such as job, location, position
and department if the legal employer is
using a two tier employment model. If this
isn’t the case, then its data corruption.
The status of assignments and their
corresponding work term rows must
match. If this isn’t the case, then its data
corruption.
The Freeze Start Date and Freeze Until
Date determine the period of time for
which an assignment record is frozen.
You can’t take any action for frozen
records. Typically, the Freeze Start Date
must be set to 31-DEC-4712 and Freeze
Until Date to 01-JAN-0001 so that
effectively the assignment record is never
frozen.
Primary flag corruptions that can be
resolved without any input from the user
are covered in this category.
The Action Occurrence ID of every
assignment row must have a
corresponding entry in the Action
Occurrences table. If this isn’t the case,
then its data corruption.
The Person Type ID must be in
synchronization with the System Person
Type ID. If this isn’t the case, then its data
corruption. This corruption can take
different forms, therefore, there are three
parts to handle the different cases.
For assignments having contracts, the
logical end date of a contract row must be
EOT (31-DEC-4712). If this isn’t the case,
then its data corruption.
The Working Hour Patterns row needs to
start from the same date that its
assignment starts from. If this isn’t the
case, then its data corruption.
 14 Assignments with incorrect Default Code
Combination ID
15 Assignment type not in synchronization
with period type
16 EMP_CWK_ASG_ID not populated for
already processed offers
17 Projected start date is not null for worker
types except pending worker
18 Incorrect system person type for person
with canceled work relationship
19 The period of service ID of a contract is
not synchronized with its work term
Note: There may be more corruption types added to this diagnostic test in the future.
5 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct
The Default Code Combination ID of an
assignment must have a matching entry
in the Code Combinations table. If this
isn’t the case, then its data corruption and
that ID must be removed from the
assignment row.
The assignment type must be in
synchronization with the period type of
the work relationships that the
assignments belong to. If this isn’t the
case, then its data corruption.
When a pending worker is converted to
an employee or contingent worker
through offers, then the
EMP_CWK_ASG_ID column must be
populated. This column must be
populated with the Assignment ID of the
employee or contingent worker in the
PER_EMPL_OFFER_HR_TRACK table.
If this is not the case, then it is data
corruption. The offer state will remain in
Processing state even after these actions:
 Successful completion of the
conversion of the pending
worker to an employee or
contingent worker.
 Running of the Complete
Recruiting Process ESS job.
The projected start date must be null for
all worker types except pending workers
and offers. If this is not the case, then it is
a data corruption.
A worker not having any work relationship
and assignment data and having person
related data, must have
CANCELED_HIRE as a row in the
PER_PERSON_TYPE_USAGES_M
table. If this is not the case, then it is a
data corruption.
The period of service ID of a contract
must be synchronized with its work term.
If this is not the case, then it is a data
corruption.
What are the input parameters required for this diagnostic test?

The input parameters are person number, run mode, and type.

Person number: This parameter specifies the person number 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 three options for this parameter are Report, Validate, and Commit. If the diagnostic test is run in Report mode, the test
will generate a report of the corruptions that are detected. If the diagnostic test is run in Validate mode, the test will correct all the
corruptions that were found in the Report 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 test will correct all the corruptions that were found in
the Report mode. The changes made by the diagnostic test will be committed to the database.

Type: This parameter specifies the corruption type for which the diagnostic test will run. The user can enter a single corruption type, or
a comma separated list of corruption types. The different corruption types (for example, 1, 2, 3, and so on) and their corresponding
details are listed in the table in the previous FAQ.

What is the output of this diagnostic test?

If the diagnostic test is run in Report mode, the test will generate a report displaying the affected record count for each corruption,
along with a description of each corruption.

If the diagnostic test is run in Validate mode, the test will correct all the corruptions found in the Report mode. Additionally, the test will
generate relevant messages related to the modifications made to the data. However, the changes will be rolled back in the end.

If the diagnostic test is run in Commit mode, the behavior will be similar to the Validate mode. However, the changes will be committed
to the database at the end instead of being rolled back.

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

If the diagnostic test is run in Report mode, it will not lead to any change in the data.

If the diagnostic test is run in Validate or Commit mode, it will lead to changes where the corrupt data is present. However, the
changes will be rolled back in the end for the Validate mode.

Before any modification is done to the existing data, it will be saved to the PER_DIAG_BKP_ROWS backup table so that the original
data is not lost.

The user should first run 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.

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 Report mode for the persons for whom the changes were made. If the
changes were made successfully, the relevant corruptions will be removed for the persons, and will reflect in the corruption count.

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.

6 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct

 2. The Diagnostic Dashboard page is displayed.

3. Search for the Employment 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.

7 TECHNICAL BRIEF / Diagnostic Test: Employment 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.

8 TECHNICAL BRIEF / Diagnostic Test: Employment 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.

9 TECHNICAL BRIEF / Diagnostic Test: Employment 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.

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.

10 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct

 The following screenshots display a sample report when this diagnostic test is run in Validate mode.

11 TECHNICAL BRIEF / Diagnostic Test: Employment Diagnostic Auto Correct

12 TECHNICAL BRIEF / Diagnostic Test: Employment 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 © 2022, 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. 0622
Diagnostic Test: Employment Diagnostic Auto Correct
March 2020
Author: Aaditya Gogia