When The Benefits Administration Action on The Action Reason Table is Modified as of an Effective Date, Job Data BAS_ACTION for Job Data Rows Existing After this Effective Date are Also Changed When Savings a New Job Data Row. (Doc ID 2713821.1)

Last updated on NOVEMBER 14, 2024

Applies to:

Symptoms

While entering a new row for an employee, the LASTUPDDTTM and LASTUPDOPRID field is being updated with current date and current oprid respectively on JOB table for the previous row which is not being changed.

Steps to replicate:

1. Update the BAS_ACTION on the Action/Reason table to a new value with an effective date of 07/01/2020 (example DTA/RED) 

2. In Job Data, for an employee with an existing row dated after 7/1/2020 with DTA/RED, add a new Job Data row with a different Action/Reason and save to see that the BAS_ACTION for the previous row DTA/RED is changed to the new BAS_ACTION and the last update date and OPRID are updated to the current user and date/time.

This is causing our audit reports to be incorrectly stated for last update date and OPRID.

Cause

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