Labor Budgeting Time Periods and LFSO Fiscal Year

The Labor Budgeting and LFSO modules operate at different time intervals for forecasts and actuals:

• The Labor Budgeting modules use weekly intervals.
• LFSO uses 15- to 60-minute intervals.

As a result, forecasted data, such as sales, may vary for the same time period between these modules. The time periods defined in Labor Budgeting must be synchronized with the fiscal year defined in LFSO. Similarly, a time period scheduled in LFSO must be the same as a time period for which there is a locked plan in Labor Budgeting. Therefore, when creating Labor Budgeting time periods, work with your LFSO system administrator and see the SO_FISCAL_YEAR table to ensure that the time period setup in both modules match and that all weeks use the same day of week as the start day.

The Labor Budgeting module uses the DAYSTART_MIDNIGHT_OFFSET registry parameter to indicate when the day starts. Every job that reads actuals with an interval of less than a day, factors in the time that is set in this registry parameter. For example, suppose that a shift begins before midnight and ends after midnight. The information about actual shifts worked from LFSO uses this registry parameter to determine on which day to record the work. See Specifying the Day to which Actuals Belong.

The Labor Budgeting module runs the Labor Budgeting - Actuals Summary Aggregation Task to collect the data from LFSO and aggregates it to its own time interval. See Aggregating Payroll and Point-of-Sale Actuals.

For more information about time periods in Labor Budgeting, see Time Periods.

Important: You must configure the fiscal year to start on the same day of the week in these modules: Labor Budgeting, Time and Attendance, and LFSO. This configuration synchronizes the fiscal weeks of these modules so that they can work together.