WebApps:Scenario Manager
Available from 9.5 HF 3.3
System requirements
The requirements can be found here.
Invocation
@Session_WebAppUrl@/dimensioneditor/?name=Plan
Example:
https://servername:4444/coplanner/dimensioneditor/?name=Plan
Extended invocation
- hideSessionHeader: Defines if the session header should be visible or not (true fades out the Session-Header). Default while opening is false
Menu
| Button | Action |
|
Back to last page. |
|
Open/Close of display text of menu. |
|
Save all changes |
|
Reset of dimension |
|
Deletes selected element |
|
Create new plan |
|
Create new forecast |
|
Create new folder |
|
Copy scenario |
|
Import data from another scenario to this one |
|
Logon to scenario |
|
Move element up |
|
Move element down |
|
Sort dimension elements in alphabetical order |
|
Opens dialog field search |
Copy Scenario
The selected scenario in the tree will be copied. Define the name for the created copy. You have to define also the folder which should include the copy. If you only want to copy the structure of the scenario, deactivate the option "Copy data from <scenario name>". If the data should be copied too, activate this option.
| Hint Structure of scenario will be copied always. |
Import scenario data
Data from the scenario which is selected as source scenario will be imported to the selected scenario in the tree. If the existing data in the target scenario should be deleted first activate "Delete data in <scenario name>".
Delete element
Deletion of the selected folder/scenario.
Delete deactivated scenario
Description:
- 1) Activate scenario
- 2) Restart server
- 3) Delete element
Using this guidance all related plan data records are deleted.
Properties of scenario
If you click on a scenario you can see the properties of the scenario on the right are.
General
Name
Description of scenario
Type
Plan/Forecast. If you select type forecast additional settings will be shown for the actual period.
Plan period Select the plan period. With the extended option "Restrict input to plan period" only inputs in this period are possible.
Long term planning If you activate the long term planning you can define the planning period for the long term planning here.
Actual period Only avaible if type forecast has been selected.
Type in the period which should be used as actual period for the forecast. If "Lock data entry for actual period" is active, no inputs for this period are possible.
Expanded
First scenario to compare/Second scenario to compare
These are scenarios which are referred by planing functions in the actual scenario. The actual budget has to be defined in the "First scenario to compare" and the top down planing budget in the "Second scenario to compare".
Deactivate plan
Activate this option if you want to deactivate the scenario. A logon to this scenario is not possible anymore.
Lock data input
Activate this option if you want to lock the scenario for all data input.
Macroexecutor logon
If this option is activated and in MakroExecutor in SessionSettings.xml is for the plan the key word [MAKROPLANS] defined then the macro will be executed for this plan.
| Hint Each active scenario increases the memory consumption of the CoPlanner. Therefore not used scenarios can be deactivated temporarily. Data will not be deleted but removed from the memory. Deactivated scenarios can be re-activated at any time if they are needed. Please notice that changes at active/deactivate scenarios require a server restart to be active. |
Restrict input to plan period
Set the flag if you want to allow plan value input only in the defined plan period. The planner will be noticed when typing in data outside of the plan period that it is not possible.
Available for login
From 9.5 HF 4.0: If you want to allow users to logon on the scenario the flag must be set. If it is set to false, a logon on the scenario is not possible. This option has no effect on plan filters in masks, reports, etc..
