Critical Check Tool Checks That Require Action
Every release, we add new checks to the check tool to help you find and solve potential configuration issues in your system. We want to draw your attention to those new checks that assist you in detecting and fixing data and configuration issues. These issues can disrupt your business processes if the checks aren't run now.
New checks might detect issues you hadn't been aware of beforehand. Therefore, we recommend that you run all checks for the application areas you've enabled at the beginning of a release and fix any issues. For a complete list of all checks available, you can export a list from the check tool itself.
Configuration Requirements
Apart from the check tool, you also must have enabled the applications for which you want to run the checks. For example: Employee Central.
Role-Based Permission Prerequisites
You have the following
Administrator 
Check Tool
permissions:- Access Check Tool
- Allow Configuration Export
- Allow Check Tool Quick Fix
What's Changed
| Application Area in Check Tool | Area Title | Check ID | Why Run It Now |
|---|---|---|---|
| Employee Central Core | Emergency Contact |
|
We’ll implement business key validation for Emergency Contacts in the upcoming releases. To avoid data maintenance failure in the future, we recommend that you check the data and fix issues before the change happens. For more information, see the Emergency Contacts Business Key Validation in Second Half 2022 - Get Your Data Ready Now
|
| Employee Central Core | Association |
|
If two foundation (or generic) objects are associated with each other, correct input help is shown in the UI, for example, the Job Information History UI. For example, suppose that “Department” is associated with “Division”. Once the user selects a division in the UI, the input help for department should filter only those departments that belong to the (already selected) division. This input help only works if the field criteria is configured correctly in the Succession Data Model. In the above example, if the field criteria of the department field is configured correctly. These two new checks ensure that field criteria are correct so that the filtering works. There are 2 possibilities for errors: Field criteria exists but is incorrect OR field criteria is missing completely. In case of incorrect field criteria, the filtering simply doesn’t work. If field criteria is missing, then “implicit filtering” might happen, meaning the input help reverses the association direction. In the above example, a missing field criteria would imply that the choice of the department determines the division. This implicit filtering can lead to inconsistent data. |
| Employee Central Core | Job Information | JobInfoInconsistentEndDateCheck | Inconsistent end dates break business processes. For example, the Job Information block in the People Profile is shown as empty (no data) if there’s no record with a high date (Dec 31, 9999), this can make businesses processes fail. In cases where several records in a user's history have a high date, unexpected system behavior can occur, like positions being shown as overstaffed, and so on. We’ve merged 3 end-date checks into 1 check. These checks are no longer listed:
|
| Employee Central Core | Work Permit |
|
Work permit records must be uniquely identified by business keys. These two checks, first released in 1H 2021, are used to find work permits with duplicate or empty business keys and guide your efforts to correct them. In 1H 2022, we enhanced the two checks and made the Issue Date field part of a business key. This ensures that work permits with identical Country, Document Type, Document Number, and User ID but different Issue Date values are treated as valid data and excluded from check results. We’re moving work permits to Centralized services. To ensure that you take full advantage of Centralized services and your system works smoothly, you have to clean up invalid work permit data. |
Technical Details
|
Reference Number |
TLS-24210 |
|
Product |
Platform |
|
Module |
|
|
Feature |
|
| Action | Required |
|
Configuration Type |
Universal |
|
Link to Demo |
|
|
Lifecycle |
General Availability |
|
Type |
Changed |
|
Major or Minor |
Major |
Modular Business Process |
Not Applicable |
|
Software Version |
1H 2022 |
|
Valid as Of |
2022-05-20 |
|
Latest Document Revision |
2022-04-08 |