Scenario Relationships and Activities
Be aware of the following relationships and dependencies between scenario relationships and activities:
Activity relationships cannot cross scenarios.
When the system brings together activity relationships in the planning model at the scenario-activity level, these relationships are restricted to within the same scenario. This means that the relationships established in the Activity Group page will apply to all nonhistory scenarios in the scenario group. Some relationships are not allowed, such as:
Forecast scenario types do not allow the use of position and asset activity types.
Top-down scenario types do not allow the use of position and asset activity types.
Scenario groups that are defined as a project budget ledger Budgeting Type allow only line item activity types.
Note: The system enforces the above rules when it creates the activity scenarios within a planning model.
The system assumes that time and periods are the same across all activities for the same scenario.
The system handles the top-down scenario differently from other scenarios when used in conjunction with a bottom-up scenario. (It is also known as the target scenario (or planning targets) when used with the bottom-up line item activity scenario.) You define this relationship of planning target and control information on the planning model's Data Source page, the same page where you select the seed data.
You do not have to use top-down and bottom-up scenarios together. This is optional. You can use the different scenarios independently of one another.
You must establish planning targets for a fiscal year—this means you must define the target scenario for a single period (or annual calendar). The system does not compare or sum up quarterly planning targets to calculate a fiscal year total.