Actual and Plan Data in One InfoCube in BI

In the simplest case, you have the actual data and the plan data in a real-time InfoCube. You define an aggregation level based on this InfoCube.

The following graphic illustrates this model:

A model of this type allows you to analyze data and enter plan data for one InfoProvider using one query. You also have the option of using planning functions.

You have to use characteristic 0VERSION (or an equivalent characteristic) in the filter to distinguish between the dimensions of the InfoCube that you want to evaluate for reporting and planning, and the dimensions that you want to evaluate using planning functions.

This modeling scenario has the following disadvantages:

● A large amount of data is contained in one InfoCube.

● You cannot load actual and plan data in parallel. In the InfoCube, you can only set the mode for entering plan data or the mode for loading data manually (see Real-Time InfoCubessap).

Due to the manual maintenance effort involved and the corresponding downtime of the InfoCube, we do not recommend this model.

Actual and Plan Data in Different InfoCubes

In most cases it is useful to have the actual data in an InfoCube and the plan data in a separate real-time InfoCube.

● The InfoCubes contain less data.

● If the real-time InfoCube only contains plan data, it is not necessary to switch manually to the data load mode.

However, this model is more complex.

There are various options for filling the plan InfoCube with data.

Use Copy Function to Copy Actual Data to Plan InfoCube

You can use the standard Copy function type to copy data from the actual InfoCube into the plan InfoCube. In this case you require an additional MultiProvider. You define the aggregation levels on the basis of this MultiProvider.

The following graphic illustrates this model:

If you use a planning function to copy the data you can either start this function online from the plan query or include the copy function in a process chain in a planning sequence (see Planning Sequences).

With this type of model the system supports a characteristic relationship check.

Use Data Transfer Process to Load Plan Data

You can use a data transfer process to load data from the actual InfoCube into the plan InfoCube. In this case, you define the aggregation level either on the plan InfoCube or on the basis of a MultiProvider that contains the actual InfoCube and the plan InfoCube.

The following graphic illustrates this model:

Compared with using a planning function to copy data, a data transfer process has the following advantages: It is quicker and it supports delta handling. You can also include a DTP in a process chain. A DTP allows you to use the transformation functions (see Transformation).

With this type of model the system does not support a characteristic relationship check.

Complex Planning Integration

The following example illustrates how you integrate planning-specific InfoProviders for a sales, production, and profit and loss planning into one complex planning application. Changes made manually to the Sales planning should automatically impact on the Production and Profit and Loss planning. You achieve this by using planning functions.

The following graphic illustrates this model:

If manual changes are made to sales planning through the input-ready Sales query, these changes are also visible in the Cross query. The Cross query is defined on aggregation level Cross ALVL which also contains the sales InfoCube.

The customer has implemented planning function Simulate which specifies the relationship between the different key figures in the Sales, Production, and Profit and Loss InfoCubes. This function copies any changes to sales planning to the Production and Profit and Loss planning.

A prerequisite for a complex scenario of this type is that all the InfoCubes contain some common characteristics on which you can define an aggregation level.

Overview of InfoProvider Modeling

InfoProvider	Characteristic	Key Figure
InfoCube 1	CALYEAR, CALMONTH, VERSION, CUSTOMER, PRODUCTGROUP, PRODUCT	SALNET, AMOUNT
InfoCube 2	CALYEAR, CALMONTH, VERSION, PRODUCT	PRODAMOUNT, PRODCOSTS
InfoCube 3	CALYEAR, CALMONTH, VERSION	NETCOSTS, NETREV
Cross ALVL	CALYEAR, CALMONTH, VERSION, 0INFOPROV	SALNET, AMOUNT, PRODAMOUNT, PRODCOSTS, NETCOSTS, NETREV

Planning Automation

You can integrate process chains in planning sequences. This allows you to schedule the execution of planning sequences together with data load processes. You can use BI information broadcasting to automatically send alerts or updated versions of the plan query.

The following graphic illustrates this model: