Cumulative key figs in MM(LO-Inventory)

Question

Hi Frnds
Can anybody tell me, wht are the Cumulative and Non Cumulative Key Figs in MM(LO-Inventory).Plzz name those.
Thanks & Regards
Prabhakar

Answer 1

To respond to your latest question....
You may already know this, so bear with me...
Non-cumulatives have an "incoming" and "outgoing" reference. Meaning, for a the record to be stored it takes an "addition" and "subtraction" to calculate the value. Generally, you either initialize this value with an "addition" (the value can be positive or negative). This initialization can either be the first record you insert or a "generate initial status". After that first record/status, all values after that are generally (depending on marker update) added or subtracted from this value to make up the non-cumulative value.
Take for instance the KF:
0VALSTCKVAL - Value of valuated stock
Inflow(+):
0RECVS_VAL - Value received into valuated stock
Outflow(-):
0ISSVS_VAL - Value issued from valuated stock
In the infocube, you will want the 0VALSTCKVAL, 0RECVS_VAL and 0ISSVS_VAL.
0RECVS_VAL and 0ISSVS_VAL are normal KF's and can be used anywhere, they are not non-cumulative. But, they make up the + and - of the key figure of 0VALSTCKVAL.
Now, the KF 0VALSTCKVAL can not be updated directly, once you add it to the infocube, it can only be updated by updating the key figures of 0RECVS_VAL and 0ISSVS_VAL. (They system doesn't let you even try to update 0VALSTCKVAL directly). Thus, the value is controlled by the additions-inflows (receipts) and subtractions-outflows (issues). You can see this behavior in the update from 2LIS_03_BF/UM to 0IC_C03.
Now, to set an initial status, you just need to update the "inflow" of each Non-cumulative KF. You can see this behavior in the 2LIS_03_BX update to 0IC_C03.
You can also see this behavior if you look what SAP is doing during compression and building of aggregates. You will see some SQL that looks similiar to this.
...SUM( 0RECVS_VAL - 0ISSVS_VAL )
...SUM( 0RECVS_QTY - 0ISSVS_QTY ) "(Not sure if these are real
Now, non-cumulatives in ODS objects or anything other than an infocube are useless as they do not have a cooresponding validity table to store the updated pointer.
I will not go into the pointer logic, but there is a document out there for non-cumulative you will want to look at to make more sense of this pointer logic.
I hope this is what you were looking for...
/smw
Message was edited by: Steve Wilson
Message was edited by: Steve Wilson