Monitoring Data Processing Engine runs behind forecasts and rebates
Key Takeaway
Every DPE run gets a Batch Job record in Monitor Workflow Services. Compare record counts on the Tasks tab to find where records are lost. Use the Save Count of Node Records debug mode for per-node counts, and use Download Failed Records when a node has more than 50 failed records.
Data Processing Engine (DPE) definitions do the calculation work behind Advanced Account Forecasting and Rebate Management in Agentforce Manufacturing. A definition pulls in source data, transforms it, and writes the results to target records, such as Advanced Account Forecast Fact records or Rebate Member Product Aggregate records. Every run is tracked in Monitor Workflow Services, so that is where you check whether forecasts and rebate payouts were calculated the way the business expects.
DPE behind Advanced Account Forecasting
Advanced Account Forecasting includes four DPE templates. Each one is used at a different point in the forecast lifecycle.
| Template | When it's used |
|---|---|
| Generate Account Forecast | Creates the first forecast for a forecast set. |
| Recalculate Account Forecast | Calculates the latest values in a period. |
| Rollover Account Forecast | Generates forecasts for new periods. |
| Regenerate Account Forecast | Expires the existing forecast records and creates a new forecast after forecast set configurations, dimensions or period groups change. |
Companies clone these templates, customize the clones, and run them with a scheduled flow. A Recalculate Account Forecast run (a monthly one, for example) takes new data from Orders, Opportunities, Sales Agreements and other sources. The run groups and aggregates that data by the forecast dimensions and writes the results back as new and updated Advanced Account Forecast Fact records.
Account managers see the forecast data on the Advanced Account Forecast Partner Set record, which is the junction between a forecast set and an account.