Integrated Planning Functions in BI (New)

As of SAP NetWeaver 7.0, a new infrastructure is available for realizing and operating planning scenarios or other applications. In contrast to BW-BPS (Business Planning and Simulation), this new solution is fully integrated into the BI system. For example, the OLAP processor has been enhanced with the option to write back data.

The new BI integrated planning functionality is based on the same concept as BW-BPS and can be operated in the system in parallel to BPS scenarios (see below). We recommend that you use the new BI integrated planning functionality when you implement new scenarios.

Parts of the New Solution

Important Concepts and Objects

The most important concepts and terminology for BI integrated planning are:

• Data basis and aggregation levels: real-time InfoCubes are used to store data. In order to determine the level on which data can be entered or changed (manually through user input or automatically by a planning function), an aggregation level has to be defined. The aggregation level consists of a subset of the characteristics and key figures of a MultiProvider or real-time InfoCube. This is a new InfoProvider for which an input-ready query is defined.
• Input-ready query: a query that is defined for an InfoProvider of type aggregation level. It is input ready and can be used for manual planning. Whether a particular cell is input ready depends on the drilldown, specifically whether characteristic relationships and data slices are permitted for the cell (see below).
• Planning functions: planning functions allow the system-based processing or generation of data. In the standard system, the BW-BPS function types are provided. Functions can be executed online (button) or in the background as a planning sequence.
• Planning sequences: a planning sequence is a sequence of planning functions and manual input templates that are executed sequentially. You can also schedule planning sequences to be processed in the background as a step in a process chain (special process type).
• Filter: a filter describes a section of a dataset which is processed in a query or a planning function, for example. (Example: calendar year 2004 - 2005; customer group XY)
• Using variables: variables can be used in various places; in the filter for selections of characteristic values that can be parameterized, to parameterize planning functions or planning sequences.
• Characteristic relationships: you use characteristic relationships to model semantic relationships between characteristics. (Example: product group, product). In this way you check, for example, whether a particular combination of characteristics can be generated (is permitted) or whether a cell is input ready. Characteristic relationships are created for an InfoCube.
• Data slices: you use data slices to protect whole areas of data globally against changes (for example, current values or historic values).
• Lock concept: so that one user only is able to change data, "their" data is locked against changes by other users. Depending on the expected load (determined by the number of users working in parallel and the complexity of the selection), different implementations of the lock process are available. The lock algorithm is used by BW-BPS and BI integrated planning. This means that you can operate both scenarios in parallel (see Locking Transaction Data in Planning (Changed) ).

Modeling Planning Scenarios

The following tools are available for modeling planning scenarios:

• You use the Data Warehousing Workbench to create the data basis (defining real-time InfoCubes).
• You use the planning modeler to model all planning-specific metadata objects. The planning modeler is a Web-based application that is installed on J2EE Engine.
• You use the BEx Query Designer to define an input-ready query for the manual entry of plan data.
• You use the BEx Web Application Designer to configure Web templates; you use the BEx Analyzer to configure Excel applications.

Consequently you can use the Data Warehousing Workbench and all the Business Explorer tools not just for analysis, but for planning and data entry too.

Integrated Planning and BW-BPS

• Both planning tools use the same data basis and can be operated in parallel in one system. It is not necessary to migrate existing planning applications.
• Some functions are used by both BW-BPS and BI integrated planning (lock procedure and formula).
• In BI integrated planning, most of the BEx and OLAP analysis functions are also available with planning applications. You need a smaller number of objects (for example, by using the same variables in analysis and planning) and tools (Query Designer and Web Application Designer).
• Using the Business Explorer for planning makes it possible to build integrated analytical applications that comprise planning and analysis functionality.
• Many BW-BPS concepts are used in BI integrated planning (planning levels, planning functions, planning sequences, characteristic relationships, data slices, and so on). This means that a conversion from BW-BPS to BI integrated planning, if required, can be easily performed