Difference between data update in planning mode and loading mode

[Former Member]

Hi gurus,

I am referring to intergrated planning. Planning cube can be loaded and planned.

When the cube is in planning mode, key figure gets overwritten while when its in loading mode, key figures get aggregated. Is this the behaviour?

E.g. Verion V1 is copied to V2 repetatively using copy function and self transformation. what wll be difference

Regards,

Subir.

[Former Member · Accepted solution]

When the cube is in planning mode, delat differences are posted to key figures and not the value as it is.

For eg. say your cube as 0AMOUNT with value 100. When you switch your cube to planning mode and set the value of 0AMOUNT in your planning layout to 70 then in the cube actually the delta value -30 ( = 70-100) of 0AMOUNT will be posted.

But if your cube is in load mode and from source data provider you are doing full load in your real-time cube then the 0AMOUNT will have 170 (= 100+70).

[Former Member · Accepted solution]

Thanks Deepti .. How ab the planning functions Do they also behave the similar way? If I copy version A to version B, the key fig should ideally get overwritten( or negation) with version A.

[chemicala_srimallikarjuna]

Hi,

In planning Mode, When you enter planning data, the data is written to a data request of the real-time InfoCube. As soon as the number of records in a data request exceeds a threshold value, the request is closed and a rollup is carried out for this request in defined aggregates (asynchronously). You can still rollup and define aggregates, collapse, and so on, as before.

Depending on the database on which they are based, real-time InfoCubes differ from standard InfoCubes in the way they are indexed and partitioned. For an Oracle DBMS, this means, for example, no bitmap indexes for the fact table and no partitioning (initiated by BI) of the fact table according to the package dimension.

Regards

CSM Reddy