How to Create Detailed Financial Plans › About Cost Plans › About Automatically Populating Cost Plans

About Automatically Populating Cost Plans

When creating a cost plan, you can automatically populate the plan using values from the task assignments or investment team (that is, resources or roles). Automatically populating a cost plan saves time.

You can also repopulate an existing cost plan.

Values are auto-populated in a cost plan, based on the following predefined financial attributes:

• The start and end periods are based on the fiscal period type of the associated entity and the start and end dates of the associated investment.

  Note: The auto-populate uses the investment start and finish dates to determine active fiscal time periods defined on the associated entity. All fiscal time periods are populated ignoring the freeze date defined in the entity plan defaults.

• The grouping attributes are based on the default grouping attributes defined on the associated entity. If default grouping attributes are not defined on the entity, you can define these attributes in the cost plan.
• The values for the grouping attributes are based on the investment team or task assignments.
• The costs and revenues for the resources are based on the costs and rates defined in the financial cost/rate matrix that is associated with the investment. If cost/rate is not defined in the matrix for a cost plan time period, an error message appears.
• The matrix is associated with the investment under the appropriate section. For example, for labor, associate the matrix under the Labor Transaction Rates section.
• The work units are based on the sum of the work units of all roles or resources. The roles or resources come from either the investment team or task assignment with the same grouping attribute values as in the line item detail row.
• When populating from the investment team, every team member is a candidate row. However, if two team members have the same grouping attribute values, one line item detail row is created to represent both team members. For example, if grouping is by Transaction Class and Department, and two team members have the same transaction class and department, the product creates one cost plan line item detail row. This row represents the sum value from both records because each detail row must contain a unique combination of grouping attribute values.
• The product overwrites cost, revenue, and unit amounts on manually-created rows only if the row has grouping attributes that exist on the investment.