Custom Report Types in Collaborative Forecasts | Salesforce
Custom Report Types in Collaborative Forecasts
A report type defines the set of records and fields available to a report based on the relationships between a primary object and its related objects. Reports display only records that meet the criteria defined in the report type.
Available in: Salesforce Classic
Available in: Professional (no Custom Field forecasts), Enterprise, Performance, Unlimited, and Developer Editions
Opportunity Splits available in: Performance and Developer Editions and in Enterprise and Unlimited Editions with the Sales Cloud
This information applies to Collaborative Forecasts and not Customizable Forecasts. To create a forecasting custom report type, enable Collaborative Forecasts.
This table lists the forecasting custom report types that you can create.
Use to create a report for...
Viewing information about forecasting amounts, including adjustment amount information. As a best practice, if you use a forecast type based on revenue, use these default fields in the report type.
Owner Only Amount—The sum of a person’s revenue opportunities, without adjustments.
For example, if you own two opportunities, each worth $10,000, the Owner Only Amount is $20,000.
Amount Without Adjustments—The sum of a person’s owned revenue opportunities and the person's subordinates’ opportunities, without adjustments. Subordinates include everyone reporting up to a person in the forecast hierarchy. This amount is visible only on reports.
For example, if the sum of the amount of all opportunities owned by you is $20,000, and the sum of the amount of your subordinates’ opportunities is $55,000, the Amount Without Adjustments is $75,000.
Amount Without Manager Adjustments—The forecast number as seen by the forecast owner. This is the sum of the owner’s revenue opportunities and the owner’s subordinates’ opportunities, including adjustments made by the forecast owner on the owner's or subordinates’ forecasts. It doesn’t include adjustments made by forecast managers above the owner in the forecast hierarchy.
For example, Anne has an Amount Without Adjustments of $75,000, made up of $20,000 of her own opportunities and $55,000 of opportunities owned by Ben, her subordinate. She adjusts Ben’s amount to $65,000 for a total of $85,000. If you adjust Anne’s number from $85,000 to $100,000, you see $85,000 in Amount Without Manager Adjustments, because Anne sees this amount (and Anne can’t see your adjustments because you’re her manager). To see the amount that includes your adjustment to $100,000, look at Forecast Amount.
Forecast Amount—The revenue forecast from the forecast manager’s perspective and the sum of the owner’s and subordinates’ opportunities, including all forecast adjustments.
For example, you’re a forecast manager and have another forecast manager reporting to you who has an Amount Without Manager Adjustment totaling $85,000. If you adjust the forecast to $100,000, the Forecast Amount is $100,000.
If you use a forecast type based on quantity, use these default fields in the report type.
Owner Only Quantity, Quantity Without Adjustments, Quantity Without Manager Adjustments, and Forecast Quantity
Regardless of whether you forecast based on revenue or quantity, add these fields.
Has Adjustment—A checkbox that indicates whether a manager adjustment has been made on a forecast owner’s amount.
Has Owner Adjustment—A checkbox that indicates whether a forecast user has adjusted the user’s own forecast amount.
If you use cumulative forecast rollups, add this field to your report.
ForecastingItemCategory—This field indicates which rollup each forecast amount is for: Open Pipeline, Best Case Forecast, Commit Forecast, Closed Only, Pipeline, Best Case, Commit, or Closed. If you changed the forecast category names, those changes appear in the ForecastingItemCategory values.
Forecasting Items with Opportunities as a related object
Viewing opportunity information for specific forecasting line items. For example, you can create a summary report for each of your subordinates that includes the opportunity names and last activity dates for their forecasting items, with adjustment information and final forecast amounts.
For opportunities with no opportunity products specified, this report type includes two forecasting items: one for the Opportunity-Revenue forecast type and one for the Product Family forecast type. These product family forecasting items roll up into the Products Not Specified row of the Product Family forecast.
Forecasting Items with Opportunity Splits as a related object
Viewing opportunity split information for specific forecasting line items. For example, you can create a summary report for each of your subordinates that includes the opportunity split amounts and percentages for their forecasting items, with adjustment information and final forecast amounts.
Forecasting Items with Opportunity Product as a related object
Viewing product family information for specific forecasting line items. For example, you can create a summary report for each of your subordinates that includes the product families and total price for their forecasting items, with adjustment information and final forecast amounts.
This report type shows forecasting items only for the Product Family-Revenue and Product Family-Quantity forecast types. It includes opportunities with and without opportunity products specified.
Viewing data about individual or team quotas. As a best practice, include all the default fields in the report type. For example, you can include lookup fields, such as the full name of the owner. When running the report, you can filter by your name to see quotas that you created and their related accounts and owners.
Forecasting Quotas with Forecasting Items as a related object
Viewing quota attainment. For example, you can use Forecasting Quotas and Forecasting Items to create the custom report type. Then, when you create the report, include a team’s quotas and forecasted revenue for closed forecasts and create a formula field to display the attained quota percentage.
If you delete a forecast type, reports that use that forecast type don’t run.