Planning applications are BI applications that are based on a planning model. Power users combine the objects of the planning model into an interactive planning application which allows data to be entered and changed automatically or manually by users.
Planning model objects include:
InfoProviders that contain data (see InfoProvider )
Aggregation levels as InfoProviders which provide a set of data with a particular level of granularity for data entry and change (see Aggregation Level )
Input-ready queries which allow you to make manual entries for the aggregation level (see Input-Ready Query )
Planning functions which allow automated changes to be made to data in the aggregation level and therefore model a part of the data flow (see Planning Functions ).
In addition, planning sequences can belong to the planning model (see Planning Sequences ).
To illustrate the basic procedure, the following example shows how you create a planning application in the BEx Wed Application Designer on the basis of a simple planning model.
The underlying planning model consists of the following objects:
The two InfoCubes contain the same characteristics and have at least one common key figure; the only difference is the key figure Year. One of the characteristics is Country. This has to be included in the query.
The following graphic shows how the objects in the planning model are related:
The planning application contains at least one of the following elements:
You have a planning model that contains aggregation level Plan_Actual_Aggr (defined on the basis of MultiProvider Plan_Actual_MP), query Plan_Query02, a filter and planning functions for copying PF_Copy and revaluating PF_Revaluate02.
You are familiar with the functions of the BEx Web Application Designer (see Creating a Web Application and Creating Web Applications with the BEx Web Application Designer ).
The following simple example shows how you create a Web application with a selection list (button group), table and special pushbuttons for functions such as copy, revaluate (with a fixed percentage) and save.
For more information about the Web template concept, see Web Templates .
For more information about the data provider concept, see Data Providers in BI Applications .
In this example, we insert the following Web items:
For more information, see Web Items .
For the Web items in this example, the following data is required:
For the dropdown box (see Dropdown Box ) under parameter Data Binding → Data Binding Type → Selection of Characteristic:
Set the indicator for the Label Visible parameter for the dropdown box so that the label is displayed for Country.
The system uses the data provider you create first for all additional Web items. If you have performed the activities in the order described here, the system inserts data provider DP_01 under the Data Bindingparameter for the Analysis Web item (see Analysis ).
For the button group (see Button Group ), under parameter Internal Display → List of Buttons → Caption on the Text Editing dialog box (with option Language-Independent Text) we enter a text for the required pushbuttons. We choose the Command field to assign a suitable command to each button (see Command Wizard ). The Edit Command dialog box appears. On the All Commands tab page, select Commands for Planning Applicationsand choose the required functions in accordance with the following examples:
Special Function Buttons
Button Text | Command | Parameter |
---|---|---|
Copy |
Execute planning function (simple) (EXEC_PLANNING_FUNCTION_SIMPLE) |
Data Binding → Reference to Data Provider of Type Filter: DP_01 |
Command-Specific Parameters → Planning Function: Select your copy planning function (PF_Copy in our example) |
||
Revaluate |
Execute planning function (simple) (EXEC_PLANNING_FUNCTION_SIMPLE) |
Data Binding → Reference to Data Provider of Type Filter: DP_01 |
Command-Specific Parameters → Planning Function: Select your revaluate planning function (PF_Revaluate02 in our example) |
||
Save |
[SAVE_DATA] |
Data Binding: No entry necessary |
For more information, see Commands for Planning Applications .
You can use the planning functions you have created to copy and calculate plan data. The data set is determined by the navigational state of data provider DP_01. You can save the entire Web application by choosing the Save pushbutton.