Show TOC

Background documentationModeling Scenarios Locate this document in the navigation structure

 

InfoProvider Modeling

The following InfoProviders can be used as the basis for an input-ready query:

  • InfoProvider an aggregation level defined on a real-time InfoCube (simple aggregation level).

  • InfoProvider an aggregation level defined on a MultiProvider (complex aggregation level). The following prerequisites apply: The MultiProvider contains

    • at least one real-time InfoCube

    • no simple aggregation levels

  • The InfoProvider is a MultiProvider containing at least one simple aggregation level.

Actual and Plan Data in a Single InfoCube

In the most basic scenario, you can have the actual and plan data in a real-time InfoCube and define an aggregation on it.

This graphic is explained in the accompanying text.

A model of this type allows you to analyze data and enter plan data for one and the same InfoProvider using one query. You can also use 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 very large amount of data is contained in just one InfoCube.

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

    Recommendation Recommendation

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

    End of the recommendation.
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 to the data load mode manually.

This model is more complex however.

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

  • Use the Copy Function to Copy Actual Data to the Plan InfoCube

    You can use the standard Copy function type to copy data from the actual InfoCube to the plan InfoCube. You then require an additional MultiProvider. You base the definition of the aggregation levels on this MultiProvider.

    This graphic is explained in the accompanying text.

    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 modeling, the system supports a characteristic relationship check.

  • Use a Data Transfer Process to Load the Plan Data

    You can use a data transfer process to load data from the actual InfoCube to the plan InfoCube. You then define the aggregation level either on the plan InfoCube or based on a MultiProvider containing the actual InfoCube and the plan InfoCube.

    This graphic is explained in the accompanying text.

    Compared with using a planning function to copy data, the data transfer process has the advantage of being quicker and supporting 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 modeling, the system does not support the characteristic relationships check.

Complex Planning Integration

The following example illustrates how you can integrate planning-specific InfoProviders for a sales, production, and profit and loss planning into one complex planning application. Using planning functions should mean that manual changes in Sales planning will directly affect Production planning and Profit and Loss planning.

This graphic is explained in the accompanying text.

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 complex scenario of this type can only be used if all the InfoCubes contain certain common characteristics that you can define an aggregation level on.

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 loading processes. You can use Information Broadcasting to automatically send alerts or updated versions of the plan query.

This graphic is explained in the accompanying text.