Time Period

Depending on the screen you are on, the Time Period  field will either display the date range associated with a particular timesheet or the name of the Time Period the user is associated with.

Changing Time Periods  

Note that a users association with a time period cannot be changed once a timesheet exists for that person (for that time period).  If you require assistance changing a user from one time period to another, contact Unanet Support who will work with you to create the necessary scripts to facilitate the move.

When contacting Unanet Support for time period change assistance, supplying responses to the following questions will help expedite the request:

• When would you like the time period change to take effect?

• Note that when making a time period change, time recorded after the effective date will be deleted. Is there any time entered in the future that will be lost?

• Are you switching the period type? (example: weekly - biweekly) - or just the date range of your current period type?

• Has the new time period been created as yet?  If not, you may want to go ahead and create the new time period with an appropriate begin date.

• Can you send us the results of the line of SQL statement -- select * from time_period_setup

• What database platform are you running? Oracle or MS SQL Server?

• Is dilution enabled on your system (Cost Dilution Method (unatime.cost.dilution.class) – with the setting being anything other than zero).?

• Are you using the time in/time out functionality? (TITO)

Other tips for a time period change:

• During the transition time, it is important that no one who is being switched enters a future timesheet.

• All users being switched will need to create their final timesheet for their previous time period association (having saved at least one entry on that timesheet).

• Where possible, it is best to try and choose a time for the switch where one period ends, and the next begins (without leaving any gap or overlap).