7/25/2019 0001501907 Inv 2

http://slidepdf.com/reader/full/0001501907-inv-2 1/2

SAP Note 

Header Data

Symptom 

For all characteristics combinations of the validity characteristics, the validity table for a non-cumulative cube contains the interval for which non-cumulative values are defined. The intervals aredefined in such a way that the from-date corresponds to the earliest date and the to-datecorresponds to the latest date of the posted non-cumulative movements in the non-cumulative cube.The validity intervals are automatically managed and adjusted when the non-cumulative value changesare loaded.

The analytic engine assumes that no non-cumulative movements exist outside the validity intervals;in other words, it assumes that the non-cumulative movements and the validity intervals match. Thismeans that the analytic engine does not take into account any non-cumulative value changes that liebefore the from-date and after the to-date.

The following processes are particularly affected:

1. Consistency of non-cumulatives and cumulative valuesA query that contains non-cumulative movements ("not" non-cumulatives) and non-cumulative keyfigures will not contain any changes of the non-cumulative key figure if there are artificiallyshortened validity intervals for non-cumulative movements outside of the validity:

Example with a validity from 2002 to 2003:

Calendar year Non-cumulative value change Non-cumulative with LAST2000 10 [40] 

2001 20 [50] 2002 30 70 2003 40 110 Total 100 110 

The compound non-cumulative values for 2000 and 2001 do not exist if the validity is shortened.

2. Values that are derived from cumulative values: Formulas with constants, particularlycounters (among others)The existence of a constant for a characteristics combination is determined by a cumulativequery ("not" non-cumulative). A cumulative query is also always used to count characteristicvalues or combinations of characteristic values. The system uses all records that are posted inthe InfoCube and that have been determined taking into account the data validity and the filter.

3. Aggregation and validity characteristicsIt is necessary to determine non-cumulative values outside the corresponding validity periods ifnon-cumulative key figures are aggregated across several validity characteristics and if the

times for which the system determines the non-cumulative values do not entirely lie in all ofthe validity intervals. For this, the system determines the shortest uninterrupted time periodthat contains all validity intervals used in the specific context. This time period stretchesfrom the earliest from-date to the latest to-date of the validity intervals used. The validityintervals are now extended up to this time period for the specific instances of the validitycharacteristics.For this, the system uses the non-cumulative values at the limits. For points in time that liebefore the from-date, the system uses the initial non-cumulative of the from-date. For points intime that lie after the to-date, the system uses the final non-cumulative of the to-date.For performance reasons, the analytic engine tries to combine the validity intervals beforehandwherever this is possible, and it also tries to avoid reading the data grouped by validitycharacteristics. However, this leads to differing results because the data outside the shortenedvalidity intervals is now read as well.The following example shows the non-cumulatives with LAST aggregation per calendar year if thesystem reads the data in a compressed form (in this case, the system reads only the Totalcolumn; the values under A and B serve only as an explanation), and the values when thecharacteristic of the validity table is drilled down (these are specified in square []

brackets).Example with a validity from 2002 to 2003:

Characteristic of the validity table Calendar year A B Total 2000 40 [70] 100 140 [170] 2001 50 [70] 120 170 [190] 2002 70 150 220 2003 110 130 240 Total 110 130 240 

1501907 - Non-cumulative cubes, validity interval,non-cumulative logic 

Version  2 Validity: 03.09.2010 - active Language  English

Released On  09.11.2010 10:35:28

Release Status  Released for Customer

Component  BW-BEX-OT-NC Non cumulative value

BW-BEX-OT-OLAP Analyzing DataPriority  Correction with medium priority

Category  Consulting

Other Components

7/25/2019 0001501907 Inv 2

http://slidepdf.com/reader/full/0001501907-inv-2 2/2