28.4 Editing the Defined Forecast Balance

You can modify or edit an existing forecast balance by opening it, making the changes and then saving it as either a:

• Different Method with a new name, or
• The same forecast balance name

Naming Convention:

It is best to use a naming convention that creates different groups of forecast balances. This keeps track of which methods were created, in the context of specific modeling buckets.

The Active Time Bucket Rules:

Assumptions that you define when creating a forecast balance are based on a specific modeling hori­zon, which is defined in the Time Buckets section.

Example

• If you define a forecast balance based on a Time Bucket with a monthly modeling horizon, your results are calculated in monthly time periods.
• If you redefine that same forecast balance, using a different time bucket with a weekly modeling horizon, your results are calculated in weekly time periods.

If assumptions in your Forecast Balance are based on a modeling horizon that is different from the horizon defined in the active time bucket, inaccurate data will result. You should verify that date-sensi­tive rules are consistent with the active Time Bucket.

Defining Forecast Balances Using Node Level Assumptions

Node Level Assumptions allow you to define assumptions at any level of the Product dimension Hierar­chy. The Product dimension supports a hierarchical representation of your chart of accounts, so you can take advantage of the parent-child relationships defined for the various nodes of your product hierarchies while defining rules. Children of parent nodes on a hierarchy automatically inherit the assumptions defined for the parent nodes. However, assumptions directly defined for a child take pre­cedence over those at the parent level.

Note:

The only method supported for inheritance is Target Growth.