Client Forecasting Settings

Client Forecasting Settings

Finding or adding to your Anterra menu menu

By default the Client Settings component of Anterra is placed under the Construction > Administration menu and is called System-Wide / Consolidation Group / Project. It is accessible to users with the Construction > Administration > Forecast Settings role (see role assignments).

forecast settings

Menu location of Client Settings component
A menu administrator can add this component to their Anterra menu using the steps outlined in the menu administration overview and selecting the Client Settings component (shown below).
BI component selection
Menu administration selection of the Client Settings component

Company-Wide Settings

These are settings which allow an administrator to control Anterra’s functionality for your other users which helps prevent user mistakes which could cause information that has already been reported to be allowed to be changed.

To change a setting you must select the checkbox next to the setting to enable editing.  The disabled state does NOT indicate that the setting is not enforced.

Forecast Day Cut Off

When a date is present/placed in this field, no forecasts can be entered on or before that date.

As an example, lets say it is mid-month and you set the forecast day cut off to the last day of the prior month.  This will cause the forecast functionality throughout Anterra to be disabled if the date selected (usually at the top of the grid) were set to any date in the prior month.

You can disable this functionality by checking the box, removing the date, and clicking Save Client SettingsIf this field is empty or the date is removed, this disables the functionality and allows forecasts to be entered as of any date.

You can also set the cut off date for only specified consolidation groups of your company using the following steps:
  1. Selecting one or more consolidation group from the Consolidation Group(s) Selection area
  2. Click the Load Settings button which will populate the right side of the screen
  3. In the middle area under Consolidation Group(s) Settings check the box next to Forecast Date Cut Off to override the company-wide setting with a different value for this consolidation group.
To see all consolidation groups that previously had settings, check the All with settings checkbox then click the Load Settings button.
Grids can be set to automatically load using the last date of the prior month. Be aware of the settings for grids like Job Forecasting Hub when adjusting this setting, you can also adjust the default setting on any grid as shown in Setting the Default Date for a Pivot Grid.

Forecasts On or Before This Date Attribute to Previous Month

When a date is placed in this field, jobs which have their forecasts at the Cost Category level and have a forecast change put in on a date in the following month, the entries will be attributed to the previous month.

Example: If the setting is set to 1/10/2024, then any entries put in during the first 10 days of January will have an accounting date of 12/31/2023 and affect the forecast as of that day.

You can disable this functionality by checking the box, removing the date, and clicking Save Client Settings.

This setting is most useful when the default date for your job forecasting hub is set to today’s date.
It is important that if you set the Forecast Day Cut Off, that it is set to a date that is equal to or before the last day of the prior month.

Number of future fiscal years to forecast % complete by year

If your company has long-running projects which span multiple years, it may be beneficial to forecast your expected percent completion for each project as of the year end. This setting allows you to configure a number a fiscal years which you would want to collect this forecast for.  Enter the lesser of:
  • Maximum fiscal years that your projects take to complete
  • Maximum number of fiscal years that your project managers would have an estimated completion percentage for on a project
  • Maximum number of fiscal years that the business wants to look forward at a given time
The number entered here will extend the Job Forecasting Hub and the Cost Code / Cost Code Type grids with YE % Complete - {Year} columns for each of the fiscal years. This means you can enter these % complete values either at any of the following levels:
  • Job Level
  • Cost Code
  • Cost Code Type
If your company uses non-standard fiscal calendar(s) you will see an additional year when using one of the aforementioned interfaces on a date that is between the end of your fiscal year and the end of the current year.
You can disable this functionality by checking the box, setting the value to 0, and clicking Save Client Settings.

    • Related Articles

    • ABI Forecasting / Excel Export 2024 R2 Release

      New Features and Improvements: Enhanced Excel Export Functionality Improved handling of Excel exports from persisted grids throughout the platform Increased performance for all users Larger exports now supported (up to 10 minutes of processing time) ...
    • Project Type / Forecast Level Settings

      Overview This article covers the new Project Type / Forecast Level Settings tool recently released in Anterra. To improve our users experience while forecasting, we moved the functionality of changing a job's forecast level from the Job Forecasting ...
    • Job Forecasting Hub Training

      What is it? The 'Job Forecasting Hub' is the name of the first place you go in Anterra to begin adjusting the forecast cost at complete for your projects. The Anterra Platform shows the current values for the forecasts but stores the changes to the ...
    • Job Forecasting at the Cost Category level

      Start at the Job To enter a forecast, first launch the Project Cost Scorecard report. Once the report loads, select the job you want to build a forecast for by drilling down on either the Job to Date cost or the JTD Forecast at Complete number for ...
    • Resolving Pervasive.SQL 3006 error found in AnterraDataCenter Log files

      The Pervasive.SQL.3006 error is a result of a timeout between the Pervasive Client and Server which creates a broken or interrupted connection. This can happen if AnterraDataCenter is on a different server from the Sage Pervasive database, or if the ...