Hierarchy based non-cumulative reporting

BI Gurus,
I am dealing with a data model with all cumulative "summation" type key figures. These are hours logged by an employee. There is also an employee hierarchy which defines the reporting structure. Now the requirement is to create two reports: (1) Cumulative and (2) non-Cumulatibe report. Non-cumulative along the hierarchy nodes that expand. The catch is to show the logged employee hours at each level. So, a manager should only see his own hours on his row and not the cumulative of his plus his direct reports. The org structure of the hierarchy needs to be maintained in the report though.
One other issue is that the hierarchy being used has all the nodes postable. Perhaps a new text node based hierarchy may be a viable option but please advise if anyone has any other thoughts.
Thanks
Edited by: Ron on Jul 7, 2008 9:19 PM

Hi Vikas,
Authorizations Steps -http://help.sap.com/saphelp_nw2004s/helpdata/en/be/076f3b6c980c3be10000000a11402f/content.htm
Example http://help.sap.com/saphelp_nw04/helpdata/en/41/05453caff4f703e10000000a114084/frameset.htm
Authorizations - Reporting
Assign points if this helps.
Regards,
Anil

Similar Messages

Non cumulative key figure is not getting filled based on inflow and outflow

hi,
i have a non cumulative key figure which is having inflow and outflow.
i have these three info objects in dso.
as i know non *** key figure is calculated based on inflow and outflow.
i am getting values for inflow and outflow so non *** should be calculated based on this values.
<b>but the collumn is blank in the dso</b>
in that non *** keyfigure i have added two info objects in inflow and outflow.
is there any other setting i nedd to do?
please sugest me.
its urgent

Hi Venkat,
Have you followed the process right. First Filling the Initial Stocks and then Inflow and Out Flow and then Delta. If you follow the process correctly then you can able to view the Data in the Reporting Level.
For Initial Stocks the Marker Should be set. For Inflow and Outflow the Marker should not be set.
Hope This Helps,
Regards,
rik

Non-cumulative values do not update on report

hi,
I have created cube with non-cumulatives but on reports they are not updated. I can see values for inflow but not for non-cumul itself.
Does somebody knows what could be wrong?
Regards,
Andrzej

hi,
what do you mean by date restriction?
Time reference char is 0calday, I have 0calday in validity table and tine char in query are 0calday and 0calmonth. I do not use restricted KFs in query.
Regards,
Andrzej

'Hierarchy Based Login' and 'Direct Reports' field in Dim - Position table

Hello -
I am trying to build a "My Team's" report, which basically shows the logged in Managers ( and his subordinates) revenues rolled up by default. Then the manager needs to drilldown on his name and see revenues grouped by his direct reports. I am using OBIEE 10G. In the out of the box RPD, there are two fields in the BMM layer called 'Hierarchy Based Login' and 'Direct Reports'.
1. The 'Hierarchy based Login' field uses the INDEXCOL method to get relevant column from the W_POSITION_DH table based on the the Logged in users hierarchy level (the hierarchy level is stored in a session variable (HIER_LEVEL). This session variable works fine and i have tested the SQL)
2. The 'Direct Reports' is using the same INDEXCOL method, just that it uses the formula HIER_LEVEL - 1. This works fine as well.
The issue i am facing is neither of these out-of-the-box fields are assigned to the Position dimension (the position dimension also exists OOTB).
So basically, i am able to create a manager and his direct subordinate report, but without any drill functionality.
I am trying to get the report to drill all the way down to the bottom most level of the heirarchy.
Any help to get this working is much appreciated

What i meant was neither of these out-of-the box fields are assigned to a Dimension Hierarchy ( there is a hierarchy called 'Position' that already exists out-of-the box). Other fields in the 'Dim-Position' table are assigned to a level in this position hierarchy, except these two. I guess what i am trying to achieve is to dynamically assign the hierarchy level based on the users Hierachy level in W_POSITION_DH table.
Thanks for spending time to look into my issue

Combining cumulative and non cumulative Key fig in same report with Quarter

Hi there,
could someone please help with the following,
I need to define a query, with a Keyfig called Amount (cumulative) coming from Controlling Cube, and HR Head count(non cumulative) from HR cube. Need to display Quarters in columns, Amt and Head Count in Rows. User might want to expand quarters and should be able to see the amount/Head count values for each of Fiscperiods. Up to this point, I had my definitions made, everything seems good.
problem here is, structure defined for quarters is basically a formula that sum up each fiscperiods, so it is working for fine for the amount, but for head count, it should not sum up each period values, rather need to average.....How can I achieve this?
Any help is greatly appreciated.

Thanks for your help.
My scenario kinda take an hr to explain, difficult to put it here on the thread.
to keep it simple, I need Head Count as LAST value with respective to calmonth, but need to have average with respective to Quarter. where I have defined the quarter as formula (mth1Variable Value Type + Mth1Variable Value type + mth2variable value type + mth2variable value type .....etc). So I could not set the aggregation as average in the formula. Rather I used cell definitions.
Thanks Again

Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?

A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
(1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
(2) The query runtime can be affected by the calculation of the non-cumulative.
(3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
(4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) , Issue Stock Quantity(0ISSTOTSTCK)
, Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03 business content cube. Your honest suggestions and comment are greatly appreciated!

Hello Marc,
Thanks for the reply.
I work for Dongxin, and would like to add couple of points to the original question...
Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
We would like to confirm if there would be any long term issues doing so.
To optimize the performance we are planning to create aggregates at plant level.
Couple of other points we took into consideration for using cumulative keyfigures are:
1. Parallel processes possible if non-cumulative keyfigures are not used.
2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
Once again, thanks for your input on this issue.
Thanks
Dharma.

Non Cumulative Inventory Cube Remodel

Hello Gurus,
I've existing inventory cube with non-cumulative key figures with large amount of data. We are using standard non cumulative key figures 0TOTALSTCK, 0ISSTOTSTCK & 0RECTOTSTCK.
Now I've a new requirement to report issues (0ISSTOTSTCK) & receipts (0RECTOTSTCK) based only on LB. Right now they both are in base UOM. Converting them in LB in query (on the fly) is not an option because of volume / performance of report.
I'm planning to do this in backend by adding two more key figures for issues & receipts where i'll convert standard ones in LB. I'm not going to touch any of existing non cumulative key figures. But the overall structure (F table) is going to change.
I'm concerned whether this will work? Any risks? Marker updates?
Thanks.
Abhijeet

Please have a look
http://sap.seo-gym.com/inventory.pdf

Define the Characteristics of the validity table for non-cumulatives

Hi Friends,
Here I am designing MultiProvider ( ZCA_M01), based on the Two Business content info cubes (0IC_C03 & 0SD_C03 ) & one customized info cube (ZPUR_C01).
I done Identification for char & keyfigures also.
When i trying to activating the Multiprovider, here i am getting the error , error message is : Define the Characteristics of the validity table for non-cumulatives.
Even here I am attaching the error message help also.
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.
Please take as a high priority.
Thanks & Regards,
Vanarasi Venkat.

Hi Venkat,
If you want to include 0IC_C03 cube in your multi provider the you must make sure that the time characterestics ( 0CALDAY, 0CALMONTH ....) are present in all of the other info providers which you are including in the MP. The Time char to choose depends upon the Inventory cube in which you have mentioned during the definition. As you are using the standard cube 0IC_C03 it has the time char as 0CALDAY. Try to include this in all the other info providers and dont include more tha one Non-cumulative in the MP.
Try this and see if it helps....

Bad performance with non-cumulative key figures

Hi All,
I have a cube with 8 non cumulative key figures based on fiscper.
I am not sure how the performance for reporting with non-cumulatives can be improved.
Thanks
Karen

Performance of non cumulative cubes is dependant on the distance between the marker (date of the last compression) and the execution date.
For actual stock, the more you compress the better it is.
Regards,
Fred

Inventory - Non Cumulative

Hi
I have inventory data coming from legacy syste.
I have the following fields.
Date Mtrl Qty.
As this is coming daily and i would like to keep the history in the ODS as well as cube. How can i make Qty as non cumulative with out Inflow / Out flow.
I should be looking at the reports based on wk, month and qtr.

Thejo,
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
If your InfoCube contains a non-cumulative key figure, then a time-based reference characteristic for the exception aggregation of the non-cumulative key figure must exist.
There can be several time characteristics per InfoCube, but only one time reference characteristic. This means, that the time-based reference characteristic is the same for all the non-cumulative key figures of an InfoCube.
This link is very helpful and informative:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
Let me know if this helps.
Pete

Cumulative and Non-cumulative KFs

Guys,
so I am confused about cumulative/Non-cumulative keyfigures. I read what it says about them on help.sap.com
Flow/non-cumulative value
You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
Non-cumulative with non-cumulative change
The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
Non-Cumulative with inflow and outflow
The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, and quantity) as the non-cumulative value."
and also checked a few threads on sdn but still a little confused about their purpose.
Can someone tell me when do we use which one?
Thanks,
RG.

Hi Ram,
Cummulative & Non Cummulative Key Figures :
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
u2022 Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
u2022 Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope it helps you.
Thanks & Regards,
SD

Unable to compress non-cumulative infocube with 0DOC_NUM

Hi Gurus!
I'm working on a retail project. I've created an infocube based on 0RT_C01 to keep the stock movements. It is a non-cumulative cube.
After the load of the initialization data (2lis_03_bx) ,historical movements, the initialization of 2lis_03_bf, the daily delta loads take about 10-11 hours to complete.This is because the cube has not been compressed due to the existence of infoobject 0DOC_NUM. 0DOC_NUM is of the lowest granularity and so compressing on 0DOC_NUM will not yield any performance benefits. But this has impacted the performance of daily delta loads. Also,the report that uses this cube take about 3-4 hours to open initially.Sometimes a timeout occurs.I've checked in ST22, ST21 and no errors or dumps appear.
Is there anything I can check to speed up the process?
Thanks!
Lucia

Hi,
Compressing the request containing the opening stock that was uploaded. Make sure the "No marker update" indicator is not set. Please consider note 643687 ,before you carry out the compression of requests in stock Info Cubes!
After successfully uploading the historical material movements, the associated request has to be compressed. You must make sure the "No marker update" indicator is set. This is necessary because the historical material movements are
already contained in the opening stock.
Regards,
Suman

Multiprovider containing non-cumulative KF and cumulative KF

I have two infocubes that I have placed in a multiprovidor. Infocube #1 contains one non-cumulative key figure and some cumulative key figures. Infocube #2 contains all cumulative key figures. When running a query against the multiprovider, all key figures (from both infocubes) are displayed except for the non-cumulative key from Infocube #1, in which case the value is blanks. Is there something I am missing?

Yes SAP has defined some Restriction for Creation of MultiProvider for Non Cummulatived Key Figures.
"<b>MultiProviders
When the reporting scenario is to be extended, use a MultiProvider as central interface between
query definition and basic InfoProviders. When another InfoProvider is added to the MultiProvider
definition, the technical name of a query based on the MultiProvider remains unchanged.
Use a MultiProvider to reduce the size of the basic InfoProviders. Advantages: parallel access to
underlying basic InfoProviders, load balancing, resource utilization, query pruning.
Make sure that your MultiProvider only retrieves data from relevant basic InfoProviders at query
runtime by
o Using constants in the design of the basic InfoProviders
o Using different key figures in the design of the basic InfoProviders
o Using characteristic 0INFOPROV when designing a query on the MultiProvider
Are you planning to use a MultiProvider? If so, you have to ensure that the characteristics you want
to report exist in all basic InfoProviders.
Do not use more than one non-cumulative InfoCube (InfoCube with at least one non-cumulative key
figure) because this could lead to incorrect query results.
Do not use calculations before aggregation on MultiProvider because this may lead to wrong query
results.
Do not combine basic InfoProviders having inhomogeneous data models in a MultiProvider. Use the
report-report interface between queries defined on the basic InfoProvider instead.
Avoid using only parts of compound characteristics in the constituent basic InfoProvider of a
MultiProvider. For more information, see SAP note 702542."</b>
RefS: How to Do Docs

Difference between cumulative and non-cumulative key figures

Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

Hi.............
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM

Non-cumulative Values not showing in Inventory Management Queries

Hi:
Has anyone had a problem with the new version and Non-cumulative key figures not showing up in Bex for Inventory Managemet reports? Specifically, they showed and validated back to ECC for our Development and QA boxes but now in our Regression box they are all showing zeros. Our Cumulative values are all showing correctly still within the Regression box. For example, Total Receipts and Total Issues are correctly poplating values but Total Stock is not.
I have checked and validate that the configuration in the Regression box matches or Dev and QA box.

Found the problem. It had to do with the compression variant in the delta process chain. The compression was set to 'no marker update'. Since we only started receiving measureable deltas in or regression box this is where the incorrect setting showed up. Reinitalized and the deltas are working correctly now.

Hierarchy based non-cumulative reporting

Similar Messages

Maybe you are looking for