Process documentation Procedure for Evaluating Non-Cumulative Values Locate the document in its SAP Library structure

For evaluating on non-cumulative values, you can usually use the corresponding Business Content See also: Structure linkTransferring Business Content

You can read more about which Business Content objects are delivered under Structure linkInventory Management.

If you want to model your own objects, proceed as follows:

  1. Source System

    2. There are two extraction modes for non-cumulatives in the source system. The DataSources for non-cumulatives have to support one of these extraction modes.

  2. Modeling:

    3. Determine in which way you wish to evaluate the non-cumulative value. If you only wish to evaluate the non-cumulative, or the non-cumulative changes as well as the non-cumulative using a particular time period, choose modeling as a non-cumulative value with non-cumulative changes. If you also want to evaluate the inflows and outflows separately, then choose modeling as a non-cumulative key figure with inflows and outflows.

  3. Key Figure Definition:

    4. The non-cumulative change, or inflows and outflows, which you require for the definition of the non-cumulative value, must already be created as InfoObjects if the non-cumulative value is created. Therefore, firstly define either the non-cumulative change, or the in- and outflows as normal cumulative values where necessary. These key figures must correspond to the non-cumulative values, which still have to be defined, in the type definition. The non-cumulative changes, or inflows and outflows, must have ‘summation’ as aggregation and as exception aggregation.

    Define the non-cumulative value by assigning to it the previously defined non-cumulative change, or in and outflows.

    Choose the exception aggregation you want to use. Standard aggregation always equals "summation".

  4. InfoCube Definition:
  1. BasicCube

    2. If you transfer the non-cumulative value into the InfoCube, then the respective cumulative values (non-cumulative change, or in- and outflows) are automatically included in the InfoCube definition.

    Take all of the time characteristics into the InfoCube definition, with which you wish to evaluate the InfoCube data.

    You can also choose one or more characteristics via Extras ® Maintain Non-Cumulative Values, which further specify the validity of the non-cumulative. These characteristics are additionally listed in the validity table of the non-cumulative right down to the most detailed time-reference characteristic.

    Caution

    Refer to the notes for defining validity tables. You do not usually have to include additional validity-determining characteristics in the validity table.

    Activate the InfoCube.

  2. MultiProviders

A MultiProvider can be created from one or more non-cumulative cubes with different time characteristics.

Example

In the following example, a MultProvider is created from a non-cumulative cube with the time characteristic Week and from a non-cumulative cube with the time characteristic Month.

This graphic is explained in the accompanying text
  1. InfoSource Definition:

    2. Create the InfoSource(s). If you wish to load an initial non-cumulative, note that you must create two differing InfoSources for posting the initial non-cumulative and for posting the non-cumulative changes. However, initialization is not absolutely necessary.

    Only non-cumulatives, therefore no non-cumulative changes, in- and outflows, or other cumulative values can be loaded with the InfoSource for the initialization.

    When using the InfoSource for non-cumulative changes, only the changes, or in- and outflows, and not the non-cumulative itself, are updated.

    You assign this InfoSource in the maintenance using DataSource transfer rules.

  2. Loading Data:

    3. If you want to load an initial non-cumulative, load this first, followed by the non-cumulative changes.

    Caution

    If a non-cumulative change is updated when loading data for the first time, then no further initial non-cumulative can be loaded for this characteristic value.

    When loading data, the validity areas for the individual validity-defining characteristic values are automatically updated.

  3. Query Definition:

Both the non-cumulative value and the non-cumulative change, or in- and outflows, are available for selection for the query definition in the InfoCube.

With evaluations in reporting, there is no difference in the way cumulative and non-cumulative values are dealt. Cumulative and non-cumulative values can be evaluated at the same time in a query, since the key figures are automatically aggregated correctly.