You are here:
Considerations for Advanced Account Forecasting
Review these considerations before you start using Advanced Account Forecasting.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
- When using Data Processing Engine definitions for generating advanced account forecasts in Manufacturing Cloud, keep the limits and limitations for Data Processing Engine in mind. For more details, see Data Processing Engine Limits.
- If you’re using an orchestration flow to generate forecasts, keep the limitations of Flows in mind. For more information, see Flows
- The additional factors that impact the time taken for generating forecast data in your org are:
- The number of qualifying and non-qualifying currencies that are used to generate the forecast data.
- The complexity of the forecast formulas, the number of product and period records, and the number of orders, opportunities, and sales agreements.
- The consumption of resources when calling external APIs when processing the forecast data.
- Any custom validation rules and triggers added on your advanced account forecasting objects can interfere with forecast generation. If the forecast generation for your accounts fails, disable the custom rules and triggers and then try generating forecasts.
- The number of forecast measure values that you can adjust at a time in the grid is calculated using a formula, [(n*2) + (m)] less than or equals 25. Here, n is the number of measures being adjusted, with history tracking enabled, and m is the number of measures being adjusted, without history tracking enabled. Multiple adjustments in the grid are handled using an API call. When history tracking is enabled, an adjustment to a forecast measure value includes two subrequests: creating an adjustment fact record and updating the forecast fact record. So, a single API call with 12 adjustments requires 24 operations.
- The Rollover Account Forecast Data Processing Engine (DPE) definition runs only at the start of each period so you won't see forecasts generated for newer periods if you change forecast settings during an ongoing period. For example, if you change the display duration for a forecast in the middle of a month, the Rollover DPE considers the update only when it runs at the start of the next month. To consider the forecast settings updates, such as changes to forecast dimensions, frequencies, or period group settings during an ongoing forecast period, make sure you run the Regenerate Account Forecast DPE definition after you update the settings.
- We recommend that you keep these recommended limits in mind when configuring Advanced Account
Forecasting. These limits aren’t hard limits.
Type Recommended Limit Forecast sets 10 User-defined forecast set dimensions 3 Fact objects 10 Forecast set measures 20 Measures displayed in UI 20 Periods displayed in UI 56 Periods in a period group 56 Forecast recalculations in a year 52 Forecast regenerations in a year 4 Forecast rollovers in a year 56 - When you specify a negative start period offset in Advanced Account Forecasting, the generated forecasts start from a past period. To generate forecasts from a future period, specify a positive start period offset.
- When you configure a custom fact object, ensure that the object has lookups to account, period, partner, and product. For period, create a text field (18 char) that has a period populated.
- Forecast quantity and forecast revenue measures are included by default for a forecast set. Map these measures to the corresponding fields in the fact object before activating your forecast set.
- Make sure that you specify the same values for frequency for the period group and the rollover frequency for a forecast set. Having different values for the frequencies can lead to forecast calculation errors.
- If you want to roll over the forecasts anytime during a month, then increment the start period by 1, and then run the Rollover Data Processing Engine job.
- Period and account are the default dimensions available for a forecast set. You can configure additional dimensions if necessary.
- These Account Forecasting features aren’t available with Advanced Account Forecasting:
- Add Products
- Show Growth
- Recalculate
- When your org gets upgraded during a release, make sure you check the cloned permission sets for Manufacturing Advanced Account Forecasts and Manufacturing Advanced Account Forecasts for Community. The Mass Update for Advanced Account Forecasting and Import CSV for Advanced Account Forecasting system permissions get automatically deselected in existing cloned permission sets during a release upgrade. You can reassign the permissions in the cloned permission sets if necessary . There’s no impact when you clone a permission set after a release upgrade.
- You can't create a custom report type with Advanced Account Forecast Fact as the primary object. To create a report with data from the Advanced Account Forecast Fact object, create a custom report type with Advanced Account Forecast Set Partner or Advanced Account Forecast Set Use as the primary object. For object relationships in the custom report type, select Advanced Account Forecast Fact as a child object and Each "A" record must have at least one related "B" record as the relationship criteria. Use the custom report type to create reports with advanced account forecast fact data. See Create a Custom Report Type.
- If you make any changes to the Advanced Account Forecasting setup, such as modifying forecast sets, updating calculation methods, or adjusting forecast set use records, you must rerun the Data Processing Engine (DPE) to ensure that forecast data is recalculated using the latest configuration.
- Considerations for Advanced Account Forecasting When Processing Large Volumes of Data
When you use Advanced Account Forecasting to process large volumes of data, Salesforce recommends that you process the data in batches.
Did this article solve your issue?
Let us know so we can improve!
