Timecards created using Timekeeper Responsibility are Setting to Wrong Operating Unit in spite of Error Encountered
Last updated on AUGUST 03, 2017
Applies to:Oracle Time and Labor - Version 12.1 HRMS RUP7 and later
Information in this document applies to any platform.
Using Timekeeper when a timecard is tried to be first created with a wrong responsibility and it does not get
saved due to any error or validations, later on when the timecard is created with the right responsibility, see that the timecard
still gets transferred to the wrong operating unit
1. Login and utilize a wrong responsibility for Timekeeper or a responsibility with a different security profile than intended
2. Try to save, and get any validation error for example "This expenditure organization is not active"
2. After the validation errors, create the timecard with the correct timekeeper responsibility, save, approve and do the transfer processes to Projects
3. See that the timecard gets transferred to the wrong operating unit
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