Running Opportunity Revenue Forecasts

Opportunity revenue forecasts include revenue from opportunity products that have the Is Services Product Line checkbox selected. Normally, an opportunity revenue forecast only includes unscheduled revenue that is equally split over the estimated project duration. For opportunities containing records that are recognized on delivery, however, you can opt to include revenue from resource requests. This is also reflected in the unscheduled revenue value. For more information, see Including Resource Requests in Opportunity Revenue Forecasts.

The following topics describe how the revenue forecast calculations work for each recognition method:

• Deliverable Recognition Method
• % Complete Recognition Method
• Equal Split Recognition Method

To configure the settings you want to use for running an opportunity revenue forecast, see Setting up Forecasting.

Prerequisites

Opportunities must have the Is Services Opportunity checkbox selected for you to run an opportunity revenue forecast.

You must have been granted the appropriate permissions to run an opportunity revenue forecast. For more information, see Revenue Forecasting Permissions.

Running a Revenue Forecast on an Opportunity

To run a opportunity revenue forecast:

1. On a opportunity record, click Actions | Revenue Forecasting | Run Revenue Forecast.
2. On the Revenue Forecast Batch Status related list, refresh the page to check the status of the forecast in the Revenue Forecast Processing Status field:
• If a status of "Pending" or "Processing" is displayed, refresh the page to update the field until it shows "Complete".
• If a status of "Error" is displayed, check the Revenue Forecast Batch Logs related list to view the details.

Revenue forecast records are created for each monthly time period that spans the expected project start and end dates, and the full revenue amount is equally split between the time periods. You can click a revenue forecast record to drill down and view a breakdown of the forecast.

For information on viewing the data generated by Revenue Forecasting, see Viewing Revenue Forecast Records. You can also view the data using the reports available, see Reporting on Revenue Forecasts.

If PSA is unable to determine the expected project duration, one revenue forecast record is created containing the full revenue amount for the monthly time period that contains the opportunity close date. This might happen in the following circumstances:

• The opportunity fields used to determine the expected project start or end date are empty or contain invalid values.
• There is no active revenue forecast setup record.

If the revenue forecast setup record contains invalid fields, an error is returned.

Notes:

The following configuration is available for opportunity revenue forecasts:

• To set the expected project duration on an opportunity, see Determining Expected Project Duration on Opportunities.
• To apply probability to opportunity revenue forecasts, see Excluding Probability from Opportunities.
• To include resource request revenue in opportunity revenue forecasts, see Including Resource Requests in Opportunity Revenue Forecasts and Resource Request.
• To exclude specific resource requests from the forecasts, see Excluding Selected Assignments and Resource Requests (Deliverable and Fixed Fee Revenue).
• To use the value in a nominated field on resource request records as the bill rate instead of the value in the Resource Request Bill Rate field on related EVA records, see Specifying the Fields to Use Instead of Bill Rate on Assignments and Resource Requests (Deliverable Revenue).

Calculating Unscheduled Revenue

If an opportunity has opportunity products, the value in the Unscheduled Revenue field on the revenue forecast type record is the sum of all opportunity product line items where the Is Services Product Line checkbox is selected, multiplied by the value in the Probability (%) field (provided Exclude Probability from Opportunities is not selected on the active revenue forecast setup record).

If an opportunity has no associated opportunity products, the value in the Unscheduled Revenue field on the revenue forecast type record is calculated using the value in the Amount field on the opportunity, multiplied by the value in the Probability (%) field if probability is used.

The revenue forecast type record has a revenue source of "Opportunity" and a revenue type of "Forecast". The value in the Unscheduled Revenue field is rolled up into the related revenue forecast record.

If an opportunity has associated resource requests and Include RRs on Opportunities is selected on the active revenue forecast setup record, the calculated resource request revenue is included in the Unscheduled Revenue field on the revenue forecast type record. Revenue Forecasting does the following:

• Subtracts the resource request revenue from the total revenue amount on the opportunity (including revenue for opportunity products). This is because revenue from resource requests is part of the opportunity and not additional revenue.
• Splits the remainder equally between the months that fall between expected opportunity start and end dates.

This means the total unscheduled revenue on the opportunity does not change but the distribution of the revenue differs based on the resource requests. For more information on how the revenue is calculated, see Resource Request.

Note:

If there is more resource request revenue than opportunity revenue, the remaining resource request revenue is included in the Unscheduled Revenue field.

Troubleshooting

To check the progress of the RFO_ForecastRunnerBatchJob batch Apex jobs for revenue forecasts, from Setup, enter Apex in the Quick Find box, then select Apex Jobs.

If a batch job has exceeded Salesforce platform governor limits:

1. Select the Revenue Forecast Setup tab.
2. Edit the revenue forecast setup record that is set to Active.
3. Under Forecast Batch Settings, reduce the value in the Opportunity Batch Size field. The default value in this field is set at 200.
4. Save the revenue forecast setup record and run the batch job.
5. Repeat steps 3 and 4 until Salesforce limits are no longer exceeded.

Tip:

In some circumstances, a revenue forecast batch job can fail to complete successfully and not report the error. This might happen if, for example, you abort a batch job that is in progress. If this happens and you want to run the job again, you must first check that the process has definitely failed. If it has, delete the relevant revenue forecast batch lock record before running the job again.