Users Can No Longer Update/Edit Their Timecards After Running OTL: Rollback OTLR/Non OTLR Timecards
(Doc ID 1925192.1)
Last updated on MARCH 14, 2022
Applies to:
Oracle Time and Labor - Version 12.2.7 and laterInformation in this document applies to any platform.
Symptoms
On : R12.HR_PF.B.delta.6, Retrievals Issues
ACTUAL BEHAVIOR
---------------
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.
EXPECTED BEHAVIOR
-----------------------
Expect regardless if Rollback of Timecards is run or not, it should not affect the ability to update the timecards.
STEPS
-----------------------
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)
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 |