What does the information on the Administration > Data Administration > Time Slices page mean or indicate?
The Administration > Data Administration > Time Slices page shows how data is configured for the Time Slicing job to slice data to provide the end users with needed resource/project/task/time information across stock portlets and reports.
ID/Time Slice - The data item being sliced
From Date - The start date of the requested data item
Slice Period - The time unit being sliced
Rollover Interval - The frequency of how often the data range is shifted.
When rollover occurs, the next unit of data is generated while the date range is kept the same.
For instance if the date range is two years, with a start month of JAN 2018 and end month of DEC 2020, when rollover occurs, the new date range is FEB 2018 to JAN 2021.
Number of Periods - The number of units being requested starting from the From date.
Item - The data being sliced
Expiration - The date of the next rollover. This date is automatically calculated by based on the Rollover Interval and the From Date. The Expiration Date is initially set when the Time Slice Definition is created or updated, but when the Time Slicing job executes, the Expiration Date is checked and recalculated based on the configuration described below.
Data Warehouse - Indicates if this slice is a DWH slice
Last Run Date - denotes when the last time the Time Slicing job completed the slice id request. It is represented by the PRJ_BLB_SLICEREQUESTS.request_completed_date field.
For the Daily Resource Time Definitions with ids 1, 2, 3, 10, and 11, it is recommended to have the From Dates all be the 1st of the month. This is true for the monthly time slice ids, also.