I recently had an issue where group leaders couldn't modify historic sessions, which they couldn't originally edit due to Christmas shutdown. Bah humbug!
In PeopleSoft the ability to amend old sessions is governed by the members row security class and the T&L Operator Security table TL_OPR_SECURITY.
The following SQL can be used to detemine the row security classes that operators, without unlimited access, have to give them Prior Period Access to specified sessions.
In PeopleSoft the ability to amend old sessions is governed by the members row security class and the T&L Operator Security table TL_OPR_SECURITY.
The following SQL can be used to detemine the row security classes that operators, without unlimited access, have to give them Prior Period Access to specified sessions.
select distinct OPD.ROWSECCLASS, OPS.PPA_ACCESS, OPS.PPA_ALLOW from PSROLEUSER_VW RUSR, PSOPRDEFN OPD, PS_TL_OPR_SECURITY OPS where RUSR.OPRID in ( select distinct OPRID from PS_TL_RAPID_HEADER where DESCR like 'MF%-12-2012%') and RUSR.OPRID = OPD.OPRID and OPD.ROWSECCLASS = OPS.ROWSECCLASS and OPS.PPA_ALLOW != 0
Just change the DESCR like statement as per the sessions you want to check.
If there aren't too many permission lists you could manually change them at: -
Home > Setup HRMS > Time and Labor Security > TL Permission List Security
Modifying the Days Grace Allowed as required.
Alternatively you could do so by the back end with SQL along the lines of: -
update PS_TL_OPR_SECURITY OPR set PPA_ALLOW = 20 where ROWSECCLASS in ( 'DPG542C1', 'DPG723A1' ... 'DPE13001', 'DPA130Z1' )
With the row security permission lists being the ones you identified with the first SQL.
In this example I've set the allowed days to be 20, if you want to give them unlimited access set it to zero.
Before updating remember to dump out the original values first so you can set them back after the users have finished doing what they need to do with the sessions.