This is version 1 2 3 4 5 6 7 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

TIME SHEET PRIOR PERIOD ADJUSTMENT IN SELF SERVICE#

The purpose of this white paper is to provide instructions on how to setup new dialogs in order to allow users to enter Time Sheet Prior Period Adjustments in a current Time Sheet within Self Service.

Once a time sheet has a “Sent to PR” status, no changes can be made to the time sheet. Data entered through the ‘open’ time sheet (TS) dialogs is restricted to a time sheet period. Therefore this feature has been implemented to allow users to enter prior period adjustments in a current time sheet in Self Service.

---

Current Solutions#

• Data entered through time sheet (TS) dialogs will be still restricted to a time sheet period.
• New dialogs were created to add/delete prior period adjustment for time sheet with status of ‘Sent to PR’ in Self Service
• The new preference ‘ALLOW PP ENTRIES’ has been implemented to allow data to be entered into current time sheets. It can be defined at the Site, User or Role level.
• The "SS ADJ NOT ALLOW" time rule should be obsolete but the code is still kept for back port compatibility.

---

Prior Period Adjustments limitations#

• Auto balancing is not applicable.
• Time rules are not applied for adjustments when the rules are applied to current time sheets.
• If there are time rules to be applied for a prior period adjustment, the UPTRA (Apply Time Rules For Prior Period) process needs to be used.
• UPTRA should always be run right before UPCTS/UPCTSP. If you make a modification to the time sheet with adjustments after UPTRA, all the work done by UPTRA will be lost.
• UPTRA cannot produce expected results if the time sheet does not exist for the adjustment period.
• UPTRA does not support entering adjustments for the same time sheet period through multiple time sheets. UPTRA adds adjustments from current the time sheet to the original time sheet and adds back the difference to the current time sheet. UPTRA does not take into consideration an adjustment entered for same period into another time sheet.
  
  

Because of the allowed prior period adjustments for the From/To time sheet, we implement the rounding rule on prior time sheet entries (PTSE) that have start and end time. This was needed because we could not use the regular path of execution (TSH + TTX + Rounding on INs and Outs -> PTSE) used for data that belongs to the current time sheet.

• only "Closest" rounding rule is supported on PTSE
• this rounding will fire for every entry that is keyed in, loaded or added through PTSE dialog
  

All of prior period adjustments are entered using PTSE, so if you enter time for a whole shift with three slots (work, meal, work) then you have to enter three PTSE for each time frame.

---

Add / Delete Prior Period Adjustment Dialogs#

This new dialogs are not added by default into forms. They can be added by the users using the following columns:

• ACT_DELETE_PRIOR_PERIOD_ADJ
• ACT_ADD_PRIOR_PERIOD_ADJ

The following is an example of how to add these dialogs into the WETTS form.

TimeSheetPriorPeriodAdjustment_01.jpg

MPPPA – Add Prior Period Adjustment
#

TimeSheetPriorPeriodAdjustment_02.jpg If the dialog is used for Hours TS, the start and end time can be hidden using security.
The dialog consists of three sections:

• A section used to define the prior period adjustment
• A section used to show the summary from the original time sheet and does not include any adjustments
• A section used to show the summary for adjustment entered under the current time sheet

MPDCH – Delete All Prior Period Adjustments for Date
#

TimeSheetPriorPeriodAdjustment_03.jpg

The system will delete all adjustments entered for a specified date.

---

Reason for Change LOV Setup#

1. In IMLN, add the user defined time rule that will be used by this LOV to the X_TM_PRIOR_PERIOD_ADJ lexicon.
   The following is an example of how this lexicon can be defined.
   
   TimeSheetPriorPeriodAdjustment_04.jpg
2. Lexicon Saved Value should match time rule type defined in ITRT.
   The description entered in ITRT will become a value in the Reason for Change LOV.
   User defined Time Rule type should be created with a sequence # greater than 9000.
   
   TimeSheetPriorPeriodAdjustment_05.jpg
   It is important to use the correct time rule action for the time rules used in the prior period adjustments. They should be defined as below:
   
   • "Add" if the time rule needs to add time
   • "Replace" if the time rule needs to offset time
3. Reason for Change LOV is a combination of the lexicon values and employee time rules defined in IDWR.
   TimeSheetPriorPeriodAdjustment_06.jpg