Users Can No Longer Update/Edit Their Timecards After Running OTL: Rollback OTLR/Non OTLR Timecards
Last updated on MARCH 08, 2017
Applies to:Oracle Time and Labor - Version 12.1 HRMS RUP5 and later
Information in this document applies to any platform.
On : R12.HR_PF.B.delta.6, Retrievals Issues
Self Service Timecard Status that allows user edits is set to:
Status allowing edits: Approvals initiated
Future time period limit: Assignment up to final termination
Past number of days: 100, Future number of days: 320
User ran Transfer Time From OTL to BEE with wrong date parameters. Rolled back using "OTL: Rollback Non OTLR Timecards" and "OTL: Rollback OTLR
Timecards". Now users can't update these timecards (UPDATE button is grayed out).
Find user is able to update if set Status Allowing Edits = RETRO. This is not ideal as users should only be able to update timecards in certain statuses.
Problem can be reproduced with both OTLR and Non OTLR timecards.
Expect regardless if Rollback of Timecards is run or not, it should not affect the ability to update the timecards.
The issue can be reproduced at will with the following steps:
1. Set the Status Allowing Edits status to the above.
2. Run Transfer Time from OTL to BEE to pick up the timecard
3. Run "OTL: Rollback Non OTLR Timecards" and "OTL: Rollback OTLR Timecards" back to Time Store.
4. Log into Self Service Time find timecards in statuses that should be allowed for edit. eg. REJECTED, SUBMITTED etc (NOTE: this ct allows
retrieval of non approved timecards timecards)
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