Fusion Cloud - FND_SESSION_USERS Is Not Populated With Changes Made To Username In OIM

(Doc ID 1918818.1)

Last updated on FEBRUARY 06, 2015

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

Symptoms

This issue is closely related 18132374 - REL10 UNABLE TO SPECIFY USER LEVEL PROFILE OPTION VALUE FOR NEWLY CREATED USERS. This bug has been resolved and described an issue where an entry was not written to the FND_SESSION_USERS table when a new user was created. Changes made to User Login details in OIM are not updating FND_SESSION_USERS tables. The impact of this is that incorrect details are shown in User LOV when updating or creating new entries for Profile Values which is accessed through FSM task - Manage Administrator Profile Options.  The customer is expecting the FND_SESSION_USERS table to be updated with changes made in OIM to the User Login attribute.

The customer has described the business case for this issue as:

The situation we found ourselves in was having to hire 70 "read-only employees". At the moment, when the employee is hired, they are allocated a new employee ID as username. The employees hired are real users. The environment has SSO enabled. The user name (created automatically on hiring) had to be manually updated in OIM to match the employee's real user ID used by SSO. After hiring and amending, we then had to try to set the read-only flag for all of those employees before they had logged in. However, the user LoV retained the originally-allocated UID (so we had to have a spreadsheet cross-referencing login username, original UID, employee name). Steps to duplicate at will include:

  1. Create two users :– user1, user login is - user1, user2, user login is – user2
  2. Run the LDAP Synch process
  3. Check whether these users can be viewed when performing the task - Manage Administrator Profile Options - setting the value for profile - FND_READ_ONLY_MODE for users user1 and user2 Search returns these values when searching for User Name - user
  4. We now log into OIM change the login name of user1 to USER1OIM,user2 to USER2OIM
  5. Run the LDAP Synch process
  6. Check whether these users can be viewed when performing the task - Manage Administrator Profile Options - setting the value for profile - FND_READ_ONLY_MODE for users USER1OIM and USER2OIM Search returns the values user1 and user2 when searching for User Name - user. This is NOT as expected - user1 and user2 have been changed to USER1OIM and USER2OIM (note the search is case sensitive) .
  7. We now sign out and log back in as USER1OIM
  8. We now Sign out and log back in as an HR Specialist
  9. Check whether these users can be viewed when performing the task - Manage Administrator Profile Options - setting the value for profile - FND_READ_ONLY_MODE for users USER1OIM and USER2OIM Search returns the values user2 and when searching for User Name - user. This is NOT as expected – user2 has been changed to USER2OIM (note the search is case sensitive) .
  10. Search returns the value USER1OIM when searching for User Name - USER. This is as EXPECTED.

 

Changes

N/A

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