GLOBAL_NAME And LOCAL_NAME are not updated when Name is Changed (Doc ID 2232217.1)

Last updated on MARCH 28, 2017

Applies to:

Oracle Human Resources - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Person / Assignment Issues

ACTUAL BEHAVIOR
---------------
---------------------------------------------------
When a person record has been updated with a name change, the fields global_name and local_name revert back to null until the concurrent process Update Person Names has been run.
This causes issues in self service, where the employee name in the manager hierarchy screen becomes blank meaning the line manager believes that person has disappeared from their hierarchy.

EXPECTED BEHAVIOR
-----------------------
Update Person Names should not have to be run when updating an employee's name.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Update an employee's name in Core forms.
The fields global_name and local_name revert back to null in Self Service.
2. Run the concurrent process Update Person Names.
The fields global_name and local_name are repopulated.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users have to run Update Person Names frequently which is inconvenient.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms