Introduction
One of the most robust yet the least known, least frequently used and under-utilized delivered diagnostic test available in Oracle HCM Cloud Application is “Employment Diagnostic Master – Report”.
This diagnostic test is a very useful test and can help us in finding data issues in our HCM Cloud Environment.
In this post we would like to run “Employment Diagnostic Master – Report” and understand the output.
Running “Employment Diagnostic Master – Report”
As a first step one should login to application with appropriate credentials (user should have “Application Diagnostic Administrator” role) and then navigate to “Run Diagnostic Tests” as shown
Once we click on “Run Diagnostic Tests” a new page will open where we need to search for test name
We need to select the checkbox beside the Test Name and click on “Add to Run”. Once done the test will start appearing in the top right hand section (“Choose Tests to Run and Supply Inputs”).
From the above screenshot we could see that the “Input Values” required to run the test are already validation. The available input for this test by the way is “Person Number”. If we provide a specific person number then the test will be executed for that specific employee and if we leave the field blank then it will run for all employees. For this execution we will run this test for all population.
Once we click on “Run” the test will be submitted.
We can see the results in “Diagnostic Test Run Status” section.
If we click on the “Report” tab we could see the results
So we can clearly see the various diagnostic test which can be run to correct records along with the impact. I have tried to summarize the same in the table below:
|
Issue
|
Diagnostic Test for Details
|
Action-Plan for resolution
|
Impact
|
|
Working Hour Pattern Record not starting on Assignment Start Date
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment and other modules
|
|
Assignment and Work Term Status Mismatch
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment
|
|
Set of Books Id Null
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment and other modules
|
|
Assignments with ID_FLEX_NUM Issues
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment or other modules
|
|
Work Term Records Incorrectly Populated for Two Tier Employment Mode
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment
|
|
Out Of Sync Primary Flags
|
Employment Diagnostic Auto Correct (in Report mode)
|
Execute "Employment Diagnostic Auto Correct" in Commit mode
|
Will hamper certain functionalities of employment
|
|
Invalid Primary Flags
|
Invalid Primary Flags - Report
|
Execute "Invalid Primary Flags - Correct" in commit mode
|
Will hamper certain functionalities of employment
|
|
Assignment Child Records without Corresponding Assignment Records
|
Assignment Child Records without Corresponding Assignment Records - Report
|
Follow the action plan mentioned in the detailed report
|
Will hamper certain functionalities of employment
|
|
Incorrect Assignment or Terms Numbers
|
Incorrect Assignment or Terms Numbers - Report
|
Follow the action plan mentioned in the detailed report
|
This is not a corruption but it can hamper functionality if the "custom" Assignment/Term Numbers clash with the system generated Assignment/Terms Numbers yet to be created. This should be corrected only if customer desires to do so or they face issues.
|
|
Assignment Name and Job Name Mismatch
|
Assignment Name and Job Name Mismatch - Report
|
Follow the action plan mentioned in the detailed report
|
This is not an issue unless the user wants the assignment name to change automatically to match the new job name when the job of the assignment is changed. If custom assignment name is desired then this report should be ignored.
|
As suggested in the above report we will run one of the other “Diagnostic Test” namely “Employment Diagnostic Auto Correct” in “Commit” mode and once we do so if we re-run the “Employment Diagnostic Master – Report” again we can see that many records have been corrected.
The sample output of the second run of “Employment Diagnostic Master – Report” after running “Employment Diagnostic Auto Correct” in “Commit” mode is shared for ready reference:
Summary
To conclude, we can say that we can use the “Employment Diagnostic Master – Report” and resolve data issues from the application.
We can run the individual reports and resolve the issues.
And with this I have come to the end of the post. Hope this was a good read and you guys would make use of the same.
Apps2Fusion Articles 