Planning Business Data with BW Integrated Planning

Prerequisites

The authorizations that users require for BW-integrated planning are the same as the authorizations required to analyze the data in a query. As well as the display authorization, users need the change authorization. More information: Authorizations for BW Integrated Planning.

Context

BW Integrated Planning provides business experts with an infrastructure for creating and operating planning scenarios or other applications. Planning covers a wide range of topics, ranging from simple data entry to complex planning scenarios.

Planning Model

The planning model incorporates:

Data (stored in InfoProviders intended for planning)
Structuring views of data (aggregation levels, MultiProvider, characteristic relationships, if required)
Methods to change data (planning functions, planning sequences, manual planning in the form of input-ready queries, and process chains)
Utilities (filters that can be used in queries and planning functions; variables used to parameterize objects that can be used where selections are used in data slices for example)
Concepts for protecting data centrally (data slices), with time restrictions if required

Tools

The following tools can be used to model planning scenarios:

To create the data basis, you use the BW Modeling tools in Eclipse and, if required, the Data Warehousing Workbench.
To model all planning-specific metadata objects, use Planning Modeler.
To define an input-ready query to enter plan data manually, use the BW Modeling tools in Eclipse and, if required, BEx Query Designer.
To create applications that can be used for planning, use BEx Web Application Designer (Web templates) or BEx Analyzer (Excel applications).
To enter data manually, use applications that you execute either on the Web or in BEx Analyzer.

You can thus use the BW Modeling tools in Eclipse, the Data Warehousing Workbench and the various Business Explorer tools to analyze, plan and enter data.

Procedure

Creating Data Basis and Managing Locks
Suitable InfoProviders are used to store data for planning. More information: InfoProviders.

To make that only one user can change data, this user's data is locked. Depending on the expected load (determined by the number of users working in parallel and the complexity of the selection), you can set one of several lock processes as the default. The lock algorithm is used by BW-BPS and BW Integrated Planning. More information: Lock Concept and Lock Management.
Defining Planning Model Objects
- Aggregation Levels
  
  To set the level that data can be entered or changed on (manually by user input or automatically by a planning function), you define an InfoProvider of type aggregation level. An aggregation level consists of a subset of characteristics and key figures of an InfoProvider suitable for planning. More information: Aggregation Level.
- Characteristic Relationships
  
  You use characteristic relationships to model semantic relationships between characteristics (such as product group and product). This allows you to perform various checks, for example whether a particular combination of characteristics can be generated (if this combination is permitted) or whether a cell is input ready. Characteristic relationships are created for an InfoProvider suitable for planning. More information: Characteristic Relationships.
- Data Slices
  
  You use data slices to protect whole areas of data globally against changes (current values or historic values for example). More information: Data Slices.
- Planning Functions
  
  Planning functions allow system-based processing or generation of data. Functions can be executed immediately (using the pushbutton) or in the background as a planning sequence. A number of standard planning function types are delivered with the BW system. You can also define your own function types. More information: Planning Functions and Implementing Planning Function Types.
- Planning Sequences
  
  A planning sequence is a sequence of planning functions and manual input templates that are executed sequentially. Planning sequences can also be processed in the background as a step in a process chain. More information: Planning Sequence.
- Filter
  
  A filter describes a section of a dataset is processed in a query or a planning function (calendar year 2004 – 2005, customer group XY, for example). More information: Filters.
- Variables
  
  You can use variables at different points: in the filter for characteristic values that can be paramterized, to parameterize planning functions or planning sequences. More information: Variables.
In Planning Modeler, you can edit the planning model objects (see Planning Modeler).

You can also edit filters and variables in the BW Modeling tools in Eclipse and, if required, in BEx Query Designer.

Note
You can find more information about query filters in the documentation for the BW Modeling tools and under Filter in the BEx Query Designer documentation.

You can find more information (context-sensitive) on creating and changing variable definitions (Variables Wizard and Variables Editor) in Variables in the BEx Query Designer documentation.

More information about transporting planning model objects: Transporting Planning Objects.
Defining Input-Ready Queries
In the BW Modeling Tools in Eclipse and, if required, BEx Query Designer, you can define a query based on an input-ready InfoProvider of type Aggregation Level. You can use a query of this type for manual planning. Whether a particular cell is input-ready depends on the drilldown and whether characteristic relationships and data slices are permitted for the cell.

Note
More information: Input-Ready Query and

Displaying All Valid Characteristic Combinations

Note
You can find more information about creating input-ready queries under Defining Input-Ready Queries in the documentation for the BW Modeling tools in Eclipse and under Creating Input-Ready Queries in the documentation for BEx Query Designer.
Creating Applications for Planning Business Data
In BEx Analyzer and Web Application Designer, you build planning applications that support both manual and automatic data entry and changes to data.
Note
For more information and examples of how you can build planning applications, see the documentation for the relevant front end tool:
- BEx Analyzer: Creating Planning Applications in BEx Analyzer
- BEx Web Application Designer http://help.sap.com SAP NetWeaver SAP NetWeaver Platform SAP NetWeaver 7.4 Application Help Function-Oriented View Business Warehouse SAP Business Explorer BEx Web BEx Web Application Designer Examples of Web Applications
  - Creating Planning Applications in BEx Web Application Designer
  - Copying Planning Functions (with Dropdown Box Web Item)
  - Revaluating Planning Functions (with Analysis Web Item)
  - Documentation (with Analysis Web Item)
For more information about how you can trigger the execution of planning functions or sequences in the front end tools BEx Analyzer and BEx Web Application Designer, see the documentation for the commands Execute Planning Function (Simple), Execute Planning Function and Execute Planning Sequence (Simple) in the front end tool in question:
- BEx Analyzer: Command Wizard
- BEx Web Application Designer http://help.sap.com SAP NetWeaver SAP NetWeaver Platform SAP NetWeaver 7.4 Application Help Function-Oriented View Business Warehouse SAP Business Explorer BEx Web BEx Web Application Designer Web Design API Commands Commands for Planning Applications
Entering Business Data Manually
You can enter business data manually using applications that you execute either on the Web or in BEx Analyzer.
Note
For more information, see the documentation for the relevant front end tool;
- BEx Analyzer:
  - Planning Business Data Manually
  - Functions for Manual Planning
- BEx Web Application Designer: http://help.sap.com SAP NetWeaver SAP NetWeaver Platform SAP NetWeaver 7.4 Application Help Function-Oriented View Business Warehouse SAP Business Explorer BEx Web Analysis & Reporting: BEx Web Applications Planning Business Data Manually