Revenue Forecast Setup Fields

The revenue forecast setup record includes the following fields.

Setup Details

Key: Descriptions of checkbox settings describe the selected (true) case.

Field Description
Active Indicates the revenue forecast setup record used for revenue forecast calculations. You can only have one active revenue forecast setup record.
Revenue Forecast Setup Name The revenue forecast setup record identifier. The format is RFS followed by a generated number.

Project Settings

Key: * – Mandatory field
Descriptions of checkbox settings describe the selected (true) case.

Field

 

Description

Default

Custom Date for Deliverable Expenses  

The API name of the custom field on the Expense object you want PSA to use to determine the monthly time period the relevant deliverable expense revenue is added to. The custom field can be a formula field if you want the date to update automatically each month. You must include the namespace, for example pse__Custom_Field__c. The date in this field must fall within a monthly time period of the revenue forecast for the revenue to be included and must be a day in the month you want the revenue to appear in.

Note:

If this field is not completed, the expense date is used.

None
Custom Date for Deliverable Milestones  

The API name of the custom field on the Milestone object you want PSA to use to determine the monthly time period the relevant deliverable milestone revenue is added to. The custom field can be a formula field if you want the date to update automatically each month. You must include the namespace, for example pse__Custom_Field__c. The date in this field must fall within a monthly time period of the revenue forecast for the revenue to be included and must be a day in the month you want the revenue to appear in.

Note:

If this field is not completed, the milestone actual date is used or, if there is no actual date, the target date is used.

None
Custom Date for Deliverable Misc Adjusts  

The API name of the custom field on the Misc Adjustment object you want PSA to use to determine the monthly time period the relevant deliverable misc adjustment revenue is added to. The custom field can be a formula field if you want the date to update automatically each month. You must include the namespace, for example pse__Custom_Field__c. The date in this field must fall within a monthly time period of the revenue forecast for the revenue to be included and must be a day in the month you want the revenue to appear in.

Note:

If this field is not completed, the misc adjustment effective date is used.

None
Exclude Scheduled Hrs in Closed Periods   Indicates that scheduled hours in closed periods for projects and milestones are excluded from calculations for % Complete revenue. Deselected
Exclude Resource Requests on Project   Indicates that revenue relating to held resource requests on projects and milestones is excluded. Deselected
Total Hours Field on Project * The API name of the field on the Project object you want PSA to use to calculate the value in the % Hours Completed for Recognition field. You can select from:
  • Estimated_Hours_at_Completion__c
  • Planned_Hours__c
Alternatively, you can create your own field and add it to the picklist.
Note: PSA uses the value in the Estimated Hours at Completion field as the denominator for the calculation by default if no active revenue forecast setup record has been created.
Estimated_Hours_at_Completion__c
Use Sched and Actual Hrs for % Complete  

Indicates that if the total number of scheduled and actual hours on projects and milestones exceeds the value in the field specified in Total Hours Field on Project, the total number of scheduled and actual hours is used as the denominator to calculate the value in the % Hours Completed for Recognition field.

Deselected

Opportunity Settings

Key: * – Mandatory field
Descriptions of checkbox settings describe the selected (true) case.

Field Description

Default Value

Exclude Probability from Opportunities Indicates probabilities are not applied to opportunity revenue forecasts. False
Expected Project End Date Field on Opp The API name, including namespace, of the field on the Opportunity object you want to use as the expected project end date, for example pse__Custom_End_Date__c. You must create your own field on the Opportunity object to contain this date. When used in conjunction with Expected Project Start Date Field on Opp, this field enables PSA to determine the expected project duration for use in revenue forecast calculations.
None
Expected Project Start Date Field on Opp The API name, including namespace, of the field on the Opportunity object you want to use as the expected project start date, for example pse__Custom_Start_Date__c. You can either use an existing field, such as Close Date, or create your own field on the Opportunity object to contain this date. When used in conjunction with Expected Project End Date Field on Opp, this field enables PSA to determine the expected project duration for use in revenue forecast calculations. None

Forecast Version Settings

Key: Descriptions of checkbox settings describe the selected (true) case.

Field Description

Default Value

Custom Filter Field Set The API name of the field set on the Revenue Forecast Version Detail object that contains the project, opportunity, and milestone fields you want to use as custom filters on the Review Forecast Version page.
Note: If it is a field set from a managed package, you must include its namespace.
None
Hover Details Field Set on Milestone

The API name of the field set on the Milestone object that controls the hover details displayed for a milestone in the Forecast Breakdown grid. If it is a field set from a managed package, you must include its namespace, for example pse__SelectProjectTemplateFieldSet. We recommend you add a maximum of 10 fields to the field set.

Note: Where there is a lookup to another object on the Milestone object, although it is possible to add fields from the lookup object into the Milestone field set, these are not supported and are not displayed in the hover details.

If you do not enter a field set, the following fields are displayed by default when you hover over a milestone:

  • Target Date
  • Actual Date
  • Milestone Amount
  • Planned Hours
None
Hover Details Field Set on Opportunity

The API name of the field set on the Opportunity object that controls the hover details displayed for an opportunity in the Forecast Breakdown grid. If it is a field set from a managed package, you must include its namespace, for example pse__SelectProjectTemplateFieldSet. We recommend you add a maximum of 10 fields to the field set.

Note: Where there is a lookup to another object on the Opportunity object, although it is possible to add fields from the lookup object into the Opportunity field set, these are not supported and are not displayed in the hover details.

If you do not enter a field set, the following fields are displayed by default when you hover over an opportunity:

  • Amount
  • Opportunity Owner
  • Probability (%)
  • Close Date
None
Hover Details Field Set on Project The API name of the field set on the Project object that controls the hover details displayed for a project in the Forecast Breakdown grid. If it is a field set from a managed package, you must include its namespace, for example pse__SelectProjectTemplateFieldSet. We recommend you add a maximum of 10 fields to the field set.
Note: Where there is a lookup to another object on the Project object, although it is possible to add fields from the lookup object into the Project field set, these are not supported and are not displayed in the hover details.

If you do not enter a field set, the following fields are displayed by default when you hover over a project:
  • Bookings
  • Project Manager
  • Start Date
  • End Date
None
Include Best Case Indicates the best case threshold is applied to revenue forecasts. Deselected
Include Worst Case Indicates the worst case threshold is applied to revenue forecasts. Deselected
Object for Version Grouping The object that projects and opportunities are grouped under on the Review Forecast Version page.
Note: If you do not select an object from the picklist or if there is no active revenue forecast setup record, projects and opportunities are automatically grouped by region on the Review Forecast Version page.
Region
Opportunity Best Case Threshold (%) The minimum percentage probability for an opportunity to be included in the best case scenario. None
Opportunity Expected Threshold (%) The minimum percentage probability for an opportunity to be included in the expected scenario. 0
Opportunity Worst Case Threshold (%) The minimum percentage probability for an opportunity to be included in the worst case scenario. None
Respect Permission Controls

Indicates that permission controls are respected when viewing or adjusting revenue forecast versions on the Review Forecast Version page. View or adjust permission controls provide access to regions, practices, groups, projects and opportunities. For example, when a revenue forecast is grouped by a region, permission controls for regions are applied.

 

When false, permission controls are not applied on the Review Forecast Version page.

 

Regardless of this field, PSA permission sets are still always required to view and review revenue forecasts and revenue forecast versions. For more information, see Permission Sets.

Deselected

Forecast Batch Settings

Key: Descriptions of checkbox settings describe the selected (true) case.

Field Description Default Value
Exclude Opportunities Indicates that opportunities are excluded from revenue forecast scheduled jobs. Deselected
Forecast Factor Batch Size The number of records to be processed at the same time, such as timecards and expenses. You must enter a whole number from 1 to 2000. 200
Opportunity Batch Size The number of opportunities and opportunity line items to be processed at the same time. You must enter a whole number from 1 to 2000. 200
Opportunity Scheduler Batch Size The number of opportunities to be scheduled for processing at the same time. You must enter a whole number from 1 to 2000. 200
Project Batch Size The number of projects to be processed at the same time. You must enter a whole number from 1 to 2000. 5
Project Scheduler Batch Size The number of projects to be scheduled for processing at the same time. You must enter a whole number from 1 to 2000. 200

Forecast Version Batch Settings

Key: Descriptions of checkbox settings describe the selected (true) case.

Field Description Default Value
Exclude Opportunities for Versions Indicates that opportunities are excluded from revenue forecast version scheduled jobs. Deselected
Exclude Unscheduled Revenue for Versions Indicates that any unscheduled revenue on projects or milestones is excluded from revenue forecast version scheduled jobs. Deselected
Version Detail Batch Size The number of version detail records to be processed at the same time. 2,000
Version Forecast Period The forecast period covered by the revenue forecast version. The options available are:
  • Rolling 3 Months
  • Rolling 6 Months
  • Rolling 12 Months
  • Current Quarter
  • Current and Next Quarter
  • Current Year
The version forecast period uses the end date recorded on the relevant time period record to work out the current month, quarter, or year.

The Rolling [n] Months options include the current month (based on the end date of the monthly time period) plus the relevant number of months that follow. For example, Rolling 6 Months includes the current month plus the next five months.
Rolling 3 Months

Revenue Management Integration

Key: Descriptions of checkbox settings describe the selected (true) case.

Field Description Default Value
Retain Pending Revenue in Closed Periods Indicates that Revenue Forecasting retains actuals from the previous forecast run for any closed time period when you are not using the integration between PSA and Revenue Management. Any actuals created in a closed time period after the period was closed are included in the revenue forecast for the next open period. Deselected
Exclude Revenue Recognition Actuals Indicates that the integration between PSA and Revenue Management is disabled. Revenue recognition actuals from the integration are no longer included in revenue forecast calculations. Deselected

Buttons

The following button is available:

Button Description
Schedule Version Creates a revenue forecast version scheduled job.