My Oracle Support Banner

LAST_UPDATED_BY is Showing Up as SYSADMIN in Record History instead of the intended Approver's FND User Name (Doc ID 2901785.1)

Last updated on JANUARY 12, 2024

Applies to:

Oracle Self-Service Human Resources - Version 12.2 HRMS RUP14 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------

Observed that, LAST_UPDATED_BY is Showing Up as SYSADMIN in Record History instead of the intended Approver's FND User Name.

EXPECTED BEHAVIOR
--------------------------

Expect that, LAST_UPDATED_BY shows the corresponding Approver's FND User Name in the Record History.

STEPS
-------

The issue can be reproduced at will with the following steps:

1. Login using "Employee Self-Service" Responsibility.

2. Navigate to any function that has approvals enabled.

3. Enter the details and submit the transaction.

4. Login as approver via Email and approve the transaction.

5. Observe that, in the record history the LAST_UPDATED_BY is showing up as SYSADMIN.

WHAT IS WORKING
----------------------------

It is working properly if the notification is approved from Worklist.


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.