Services Forecast Setup Fields

If selected, any cost forecasts created are grouped by milestone.

If selected, any cost forecasts created are grouped by resource.

The API name, including namespace, of the checkbox field on the Account object that controls whether an account record is excluded from scheduled forecasts. If the checkbox field is selected on a record, the record is excluded. You can use an existing checkbox field or create a new one on the Account object.

If selected, unheld resource requests with an associated schedule are included in forecast calculations.

The API name, including namespace, of a numeric field on the Assignment object you want PSA to use instead of the bill rate in deliverable forecast calculations. The field must be a Number, Currency, or Percent field type, or must be a formula field that returns one of these field types. If left blank, PSA uses the value in the Bill Rate field on the assignment record.

The API name, including namespace, of the custom field on the Expense object you want PSA to use to determine the monthly time period the relevant deliverable expenses are added to. This enables you to control the month in which revenue or costs are placed. The custom field can be a formula field if you want the date to update automatically each month. The date in this field must fall within a monthly time period of the forecast for the revenue or costs to be included and must be a day in the month you want the revenue or costs to appear in.

The API name, including namespace, of the custom field on the Milestone object you want PSA to use to determine the monthly time period the relevant deliverable milestones are added to. This enables you to control the month in which revenue or costs are placed. The custom field can be a formula field if you want the date to update automatically each month. The date in this field must fall within a monthly time period of the forecast for the revenue or costs to be included and must be a day in the month you want the revenue or costs to appear in.

The API name, including namespace, of the custom field on the Misc Adjustment object you want PSA to use to determine the monthly time period the relevant deliverable misc adjustments are added to. This enables you to control the month in which revenue or costs are placed. The custom field can be a formula field if you want the date to update automatically each month. The date in this field must fall within a monthly time period of the forecast for the revenue or costs to be included and must be a day in the month you want the revenue or costs to appear in.

The API name, including namespace, of a numeric field on the Resource Request object you want PSA to use instead of the bill rate in deliverable forecast calculations for projects and opportunities. The field must be a Number, Currency, or Percent field type, or must be a formula field that returns one of these field types. If left blank, PSA uses the value in the Suggested Bill Rate Number field instead. If that field is also blank, PSA uses the value in the Requested Bill Rate field.

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.

The API name of the number field on the Assignment object you want PSA to use when calculating weighting on % Complete forecasts. You must include the namespace, for example pse__Custom_Field__c. You can use an existing number field (for example, Cost Rate Amount) or create your own custom field. The custom field must be a Number, Currency, or Percent field type, or must be a formula field that returns one of those field types.

The API name, including namespace, of the number field on the Resource Request object you want PSA to use when calculating weighting on % Complete forecasts for held resource requests. You can use an existing number field (for example, Average Cost Rate Number) or create your own custom field. The custom field must be a Number, Currency, or Percent field type, or must be a formula field that returns one of those field types.

The API name, including namespace, of the number field on the Resource Request object you want PSA to use when calculating weighting on % Complete forecasts for unheld resource requests. You can use an existing number field (for example, Average Cost Rate Number) or create your own custom field. The custom field must be a Number, Currency, or Percent field type, or must be a formula field that returns one of those field types.

Indicates that Revenue Forecasting excludes from % Complete forecasts any actuals that are after the specified cutoff day. This setting is used in conjunction with the Use Mid Month Forecast Calculations and Actuals Cutoff Day settings and is for use with % Complete forecasts only.

For example, if the specified actuals cutoff day is Sunday and the forecast is run on Tuesday, Revenue Forecasting excludes any actuals for Monday and Tuesday and also actuals for any upcoming days.

This field only applies when you are not using the integration between PSA and Revenue Management.

Indicates that Cost Forecasting retains the total approved costs from the previous forecast run for any closed time period. Any remaining pending costs created in a closed time period after the period was closed are included in the forecast for the next open period.

The maximum number of queueable Apex jobs for forecasting that can be run at the same time. You must enter a whole number from 1 to 100.

Enter a value based on the number of asynchronous Apex jobs you expect to be available when the forecast runs. Running more jobs at once means the overall process will finish more quickly, however, bear in mind that performance might vary at different times of day because the speed at which the jobs run depends on availability.

For more information on Queueable Apex, see the Salesforce Apex Developer Guide.

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.

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.

• Target Date
• Actual Date
• Milestone Amount
• Planned Hours

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.

• Amount
• Opportunity Owner
• Probability (%)
• Close Date

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.

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

The object that projects and opportunities are grouped under on the Review Forecast Version page.

The forecast period covered by the 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.