We recommend the End Date should be no more than ten years beyond the current date.We recommend you do not use the Weeks time period type when calculating backlog.Here is a description of the fields on the Calculate Backlog page.
Key:
* – Mandatory.
64 – the maximum number of characters that the field accepts.
| Field | Description | ||
|---|---|---|---|
| Backlog Calculation Name | * | 64 | Name of the backlogRevenue that is expected from projects over a period of time for a region, practice or group. calculation. |
| Calculate Project Backlog | Indicates whether the backlog calculation is to include projects contained within or linked to the regionA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects., practiceA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects. or groupA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects. that you are running the backlog calculation on. We recommend leaving this option selected. | ||
| Copy Fields for Current Time Period | Indicates whether the Backlog Detail object records are to be written into the region, practice, group and/or project records. This is in addition to the backlog calculation and backlog detail object records. We recommend that you use the backlog calculation and backlog detail object records for reporting instead. | ||
| End Date | The end date for backlog calculations. If you leave the field blank, all records from the start date are processed. Backlog calculations include any time periods with dates that intersect with the End Date, but numbers do not include dates that are outside the end date. Enter an End Date that includes the entire time periodA period of time with a start date and an end date to which forecasts, actuals calculations, billing event batches, utilization calculations and region plans belong. you are interested in. If you are running an unscheduled backlogRevenue from work that is not yet assigned to resources on projects for a region, practice or group during a time period., leave the End Date blank to ensure the calculations are accurate.We recommend the End Date should be no more than ten years beyond the current date. |
||
| Include Sublevels | Indicates whether the backlogRevenue that is expected from projects over a period of time for a region, practice or group. is calculated for all sublevels of the regionA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects., practiceA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects. or groupA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects.. | ||
| Region/Practice/Group | The region, practice or group on which the backlog calculation is to be run. When you run a backlog calculation from a region, practice or group, the field is pre-populated with that region, practice or group . | ||
| Reuse Detail Objects | Indicates whether Backlog Detail object records are overwritten, or reused, for the same regions, practices, groups, projects and their associated time periods. We recommend that you select this option, to avoid using unnecessary space. | ||
| Start Calculating From | Allows you to automatically set the Start Date for the backlog by choosing from start of this week, today or start of next week. This is based on the calendar in your Salesforce user account. We recommend that you select Start of this Week. | ||
| Start Date | * | The date on which the backlog calculation is to start from. Recommended practice is to use the date directly after the last time entry; for instance, if your organization has entered time for week ending Saturday, run the Backlog calculations starting Sunday (start of this week). | |
| Time Period Types | * | Time period types for which to calculate backlog. All time periodA period of time with a start date and an end date to which forecasts, actuals calculations, billing event batches, utilization calculations and region plans belong. types are included in this list when the package is first installed. You can modify the time period types to match your organization’s list of time period types, or narrow the list as needed. You can also set the default selections for this pick list using the related custom setting. At least one must be selected. When executed, the specific time periods will be retrieved that match these types and will be referenced from the Start Date value.
We recommend you do not use the Weeks time period type when calculating backlog. |
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Frequency |
The frequency that the backlog calculation is to run. Schedule recurring weekly or monthly batch jobs.
For example:
Use the picklists to specify the time of day for the event to occur. |
||||||
| Start Time | The approximate time at which the backlog calculation is to be scheduled for. |
Related Concepts
Related Tasks