You are here:
Considerations for Account Forecasting
Review these considerations before setting up and using Account Forecasting in Manufacturing Cloud.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
- Account forecasts are only supported for standard fiscal year and not for custom fiscal year.
- Sales agreements for product categories aren’t considered while generating account-based forecasts.
- When you click Show All Periods for an Account Forecast record, you can see all past periods, but you can’t edit the values.
- You can’t mass update custom metrics of account forecasts.
- After you generate the forecast for an account, we recommend that you don’t move past orders, past opportunities, and past sales agreements to future periods. If you move them to future periods, recalculation or rollover of the account forecast will cause the product quantity to reflect twice (in the past and future periods). For example, you have an opportunity in July with a product quantity as 10 and you change the period to September. On recalculation, the product quantity is reflected in both the past and future periods.
- The maximum limit defined for the Account Product Period Forecast object records is 9 million. If the Account Product Period Forecast Record limit in your org is reached, new products aren’t added when recalculating a single account forecast or recalculating all account forecasts. In addition, you can't add new products to forecasts.
- Enter the validation rule for Account Growth Percentage and Market Growth Percentage fields as a percentage. For example, to restrict users from specifying a value greater than 20 in the Account Growth Percentage field, enter the validation rule for this field to be greater than 0.2.
- When list views are selected for account forecasts, account managers can generate forecasts only if either All users can see this list view or Share list view with groups of users is selected for the list views.
- If the number of display periods is more than 8, you can experience a delay in generation and display of account forecast. After multiple manual adjustments are made on a single page of account forecast, the saving of values and recalculation can take some time.
- We recommend not changing the forecast generation and display settings when the account forecast is being regenerated. Account forecast regeneration process is restarted when you change the forecast generation and display settings. The regeneration process can be time-consuming if your org has many accounts. Before making any changes, make sure to check your in-app notifications for any account forecast regeneration in-progress.
- The Account Product Period Forecasting object fields are of type double Number (18,0) with no precision defined at the API level. The data display is up to 2 decimal places as defined by the platform at the UI level.
- After rollover or recalculation of account forecasts at the end of a month, the forecasts for some accounts can show the same period multiple times. As a workaround, regenerate the forecasts for the affected accounts.
- If you expire an Account Forecast record, the associated Account Product Period Forecast records don’t become inactive. To get a list of all active Account Product Period Forecast records, make sure that you get only the Account Product Period Forecast records that are linked to an Account Forecast record with Active status.
- Account forecasts are regenerated when you change the generation and display settings. If you regenerate account forecasts, the forecast data for manually added products and any adjustments are lost. To ensure that the forecast data for manually added products is included, create an opportunity, order, or sales agreement for those products. Alternatively, manually add the products and adjustments again.
- We recommend not changing the API names of custom fields in use in custom metrics in the Account Product Forecast and Account Product Period Forecast objects. Remove the mapping between the custom fields before changing their API names.
- Any custom validation rules and triggers added on your account forecasting objects can interfere with the account forecast generation process. If the forecast generation for your accounts fails, disable the custom rules and triggers and then try generating forecasts.
- If you change your personal language or your org's standard language, then in the forecasts table, these column headers are changed to the new language: Product Name, Metric, and Total. The standard metric names are changed to the new language, but the custom metric names won't be changed to the new language. For existing forecasts, the forecast period names won't be changed to the new language. If you generate forecasts after changing the language, then the forecast period names will be in the new language. The name of a product shown in the forecasts table is determined by the Name field in that product's record.
Did this article solve your issue?
Let us know so we can improve!
