SAP Improvement for Hire Date Correction Tool - Improve the "Employee" Search to be customizable

[claudiavelez0]

Hi All,

We have a new improvement raised in SAP Customer Influence. See the link below:

Request ID: 301362: Hire Date Correction Tool - Improve the "Employee" Search to be costumizable

We raised it due to being given the possibility to have the Hire Date correction tool to allow customization on the data being shown under search of employees. It would mean , that we are able to add more field information or less.

 This request is also related due to the fact that this tool is not following the target population. This enhancement was already proposed and raised:  Request ID: 287121 Hire Date Correction - Following target population (RBP)

All companies will have a benefit allowing the specific roles provided access to te tool to use it by themselves within a specific data access without compliance concerns.

Thanks in advance for your support.

Cláudia Velez

[LindaS]

Hi Cláudia, regarding the target population issue: You can indeed select every employee in the drop down, but if you do not have the employee in your target it would give an error if you run the hire date correction. So even if it would be nicer to show less employees, but as the system does not allow you to make the change in the end, it's still acceptable.

[claudiavelez0]

Hi @LindaS thank you for your input.
The issue we reported an improvement, is not that we are able to proceed until the end for people that are not under the target scope, this is not an issue. But indeed, that the RBP's are not respected when opening the search drop-down when selecting the person.

So the  Tool is allowing to see other Counterparts within the company, which are not under the scope of the target, and giving access to information, such as the Position name/ID or full name for example.

Then this is a non-compliant tool to which is not following the RBP designed specifically for the Search and peek up of employee.

[LindaS]

Hi @claudiavelez0, then I misunderstood the issue, apologies for that!