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

Similar Messages

  • Integrated Planning and Non-cumulative key figure

    Hi
    I´m creating an Integrated Planning application and a problem has occurred. The users want to plan on inflow and outflow and at the same time have a row with the total sum in the same layout (they are planning on 0CALMONTH and 0ORGUNIT) This can e.g. be solved through use Web Application Designer with one planning query and one traditional query.
    Any way. I have created a non-cumulative key figure with an inflow- and an outflow key figure. The problem is that the non-cumulative key figure starts working first when I change the planning mode from plan status to load status. I could use function modules, to change the status, behind the save button but there are several users who are planning at the same cube at the same time and I don´t want to lock the others from planning.
    How to solve this?
    - Is it possible to restrict the switching, from plan to load, by setting some kind of filter at the users org.unit? (0ORGUNIT is an authorization object)
    - Is it possible to create a process chain and then load the data to another cube for reporting at just this key figure? And also here have a filter at the org.unit
    I will gladly get all kind of idea and input to solve this problem. Maybe there is some other way to go than using non-cumulative key figureu2026

    Thanks for your answers
    I have tried different scenarios and I will use a u201Dsave-buttonu201D. In the save-button I use the commands SAVE_DATA and EXECUTE_PROCESS_CHAIN. The command u201CEXECUTE_PROCESS_CHAIN starts a process chain that switches from plan mode to load mode and then back to plan mode again.
    One new problem has arisen. The non-cumulative key figure is updating if an existing value (inflow- or outflow) is changed. But if an input is made to an empty cell, without value, nothing happen when I press on the start-button. BUT if I refresh the browser the non-cumulative value is updated!!!
    Is there any command in WAD that refresh the whole page? If so I can include it in my start-button.
    If not, any sugestion on how to solve the problem?
    Best regards
    Mikael

  • Problem with Non-cumulative key figure.

    Hi all,
    I am facing the problem with the Non-cumulative Key Figure (Quantity). I have created and loaded data to the non-cumulative InfoCube. <b>This cube is defined by me to test the non-cumulative key figure.</b>
    <b>In BEx query the non-cumulative key figure and cumulative key figure (Value change) both display same values, i.e. non-cumulative key figure contains the same values which we have loaded for cumulative value change. Non-cumulative key figure is not calculated based on associated cumulative key figure.</b>
    I have done the following while defining the non-cumulative InfoCube:
    1. Created a non-cumulative key figure which is associated with a cumulative key figure (value change).
    2. Loaded data to non-cumulative InfoCube from flat file.
    3. Compressed data in non-cumulative InfoCube after the load.
    Note:
    1. Validity area is determined by the system based on the minimum and maximum date in data.
    2. Validity determining characteristic, 0CALDAY is the default characteristic selected by the system.
    Is there any other settings to be done?
    Please help me in resolving this issue.
    Thanks and regards
    Pruthvi R

    Being a non-cumulative KF, total stock is automatically takes care of that.
    Try putting all the restrictions which you have included for total receipts and total issues, for eg,  restrict Total Stock with the movement types used in Receipts as well as Issues.
    Check and revert.
    Regards
    Gajendra

  • Snapshot scenario or non cumulative key figure  in inventory management

    Hi
    We are currently using Inventory Management with non-cumulative key figures but we get very high performance problems due to so big number of lines in info cube.
    We are analyzing the other scenario with snapshot and I am asking if it would be very realistic to use it to satisfy our requirement: to be able to get inventory management at day level for about 2 000 000 combinations article-site and about 100  000 stock movement lines per day (we are retailer!).
    Is there somebody to give me advice about it?
    Tanks a lot
    Anne

    Being a non-cumulative KF, total stock is automatically takes care of that.
    Try putting all the restrictions which you have included for total receipts and total issues, for eg,  restrict Total Stock with the movement types used in Receipts as well as Issues.
    Check and revert.
    Regards
    Gajendra

  • Intregarted Planning Design for Non-Cumulative Key Figures

    Hi,
    I have a requirement where i have to design a planning layout for a Invenotry Scenario (Using Non cumulative Key Figures).
    What should be the factors i should consider in my design specifically for non cumulative ke figures and how it is different from design for a regular (cumulative) key figure
    Thanks
    Rashmi.

    Thanks for your response. My requirement is to design a retail inventory planning application in which one of the KPI's planned is stock price which is a non cumulative key figure and i am trying to figure out how than can be planned if non-cumulative key figures are not allowed in planning
    Thanks
    Rashmi.

  • Trouble with Non Cumulative Key Figures

    Hi all of you,
    I am working on Non Cumlative Key Figures, (NCKF). I have the data like this
    Sales rep S100 visited SHOP S1 on 1st Jan and 10th Aug, and transacted worth         100 and 500
    SHOP S2 on 1st Mar and 1st July and transacted worth 200 and 300
    SHOP S3 on 3rd Sept. and transacted worth 400
    Sales rep S200 visited SHOP S1 on 1st Jan and 1st Aug and transacted worth 100 and 300,
    visited SHOP S2 on 1st April and transacted worth 200     
    I created Non Cumulative Key Figure in the following manners:
    In modeling in InfoObjects I double clicked on my key figure BILLAMT and selected the Aggregation tab. I selected Counter (all values) for Exception aggregat. By default Agg. Referen. Char was 0calday. I then activated the info object and went to BEx. Here I took other IOs like Salesrep, Shop NUM and Dt. Of trans in rows and Bill amt in columns and executed the report. I am not getting the output how it should come for NON cumulative key figures.
    But when I right click the key figure Bill Amount in BEx in change query mode and select properties. I go to the option Calculate result as and selected the option as “Count all values”. And in another option Calculate Single Value as I selected the option “Count all values”. I said OK, saved the query and executed it. Now the output is similar to how it comes for a Non Cumulative Key Figure query but I am unable to understand the output.
    Now my doubt is where do we set the properties for Non Cumulative Key Figures? Is it in the Administrator Workbench under Modelling under InfoObjects?
    OR
    Is it in BEx change query mode by right clicking on the key figure and selecting properties?
    Please explain.
    Thank you
    TR.

    As for the setting for Non Cumulative key figures...the default setting is done in the Key Figure properties, where u can define the Exception Aggregation. This property is used as such in the query, but if suppose u are getting the normal aggregation in the query , what you could do is "Create The Key Figure as Global Calculated Key Figure in Bex" and go to properties...click on the Button for aggregation ..select the aggregation and define with respt to 0CALDAY ..here.
    Hope this helps.

  • Using Non cumulative key figure in Real time cube

    Hi gurus,
    I have used non cumulative key figure in a real time cube and when i tried to enter some data using RSINPUT ,it is giving an error and the data is not getting saved.
    Can anyone please tell me how to use the Non cumulative key figure in the Real time cube .
    Thanks in advance
    Regards,
    Ravikanth

    Hi Ravi,
          Please make sure that when you use a non cumulative key figure iun your real time info cube, then choose a time reference characteristic for that key figure.
    Then, this time reference characteristic applies for all the non-cumulative values of the InfoCube and must be the u201Csmallestu201D of the time characteristics present in the InfoCube.
    For more detaisl, refer to the [http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm]
    Thanks & Regards,
    Balajee.

  • Non Cumulative Key Figure help

    Hi All,
    I am in need of setting up a non-cumulative key figure in a cube.  When I load from my ODS everything is ok, however during a delta process, this field at times gets
    summarized when in fact it should be static or in an overwite mode.  Can someone provide some advice/comments on how I can set up my key figure field in a basic cube to be static yet be able to be used in a calculation for a query?  I do not want to apply any functionality such as aggregation, average etc. In R/3 LIS functionality, you basically set up a characteristic Key Figure, how can this be done in BW ?
    Best Regards,
    Dennis

    Dennis,
    Check if you ahve declared the KF properly and also check the query which you use ...
    Load data and then compare with the query at the lowest level of data in the ODS. Then you will know if the update rules are correct.
    Arun

  • How to display Non Cumulative key figure data

    Hi,
    I want to check if there is any data for a non-cumulative key figure. While i am trying to display the data from cube or Multi provider, it is not showing this field. is there any way to check the data for this field other than using reports.
    Regards,
    Vishnu

    Hi,
    Take Eg: Quantity of valuated stock - 0VALSTCKQTY it is combination of
    Quantity Received into Valuated Stock- 0RECVALSTCK and
    Quantity Issued from Valuated Stock-   0ISSVALSTCK
    In report you can see only  0VALSTCKQTY Keyfigure.
    And the above Two Keyfigures are filling by Routines using Process Keys.
    This is for 0IC_C03 and data you can check in MB5B Tcode in ECC.
    Check;
    Note 745788 - Non-cumulative mgmnt in BW: Verifying and correcting data
    Thanks
    Reddy

  • How to create non cumulative Key Figure.

    Friends Let me know steps for creating Non Cumulative Key Figure, can any one tell me where can i get documents for this. points will be rewarded

    Hi,
    check these help links
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/95/1ae03b591a9c7ce10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6312e07211d2acb80000e829fbfe/content.htm
    It's a big topic so it's not possible to write everything here.
    You can search the forums also.
    Thanks

  • Regarding Non-Cumulated Key figures

    Dear All,
    I wanted to create Multiprovider which includes infocube having Non-cumulative key figures .When I am including that Non-cumulative key figure in the Multiprovider , I am getting an error "Inconsistencies were found when checking MultiProvider ZMULTIPTP"
    detail fo this error is
    Define the characteristics of the validity table for non-cumulatives
    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.

    Hello,
    See this Validity table for non-cumulatives in a self defined cube
    Thanks
    Chandran

  • Non-Cumulative Key figure with inflow & outflow

    I am using some non-cumulative key figure in our inventory cube, however, I could not find the non-cumulative field in E or F table of the cube?
    Is there a separate table to hold the reference unit. If so, what is the table name.
    Thanks.

    Hi,
    Go to t-code RSDV and enter the tech.name of your cube that has the non-***. key figure and you will see a validity table. This is only thing I know that will make you look at validity table.
    The unit for the Non-*** KF will be the same unit as its inflow and outlow parameters' unit.
    Thats my 2 cents on the matter.
    Reddy

  • 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

  • Cumulative key figure and non cumulative key figure

    Hi BW Expertz
    Could any one give me the clarification about cumulative and non cumulative key figures .Why we go for cumulative key figure and non cumulative key figure.If any docs could u just mail to the following [email protected]
    Thanx In advance
    Best regards
    sankar prasad

    Cumulative values are those key figures (KF) that are cumulated using all characteristics, thus also using time.
    Ex: Sales revenue, Quantity....
    Non-cumulative values are those key figures that are measured in relation to a period in time; they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so called exception aggregation.
    Ex: Number of employees, Inventory, Stock prices, Account balance,.....
    AGGREGATION TAB
    Non cumulatives are evaluated by non-cummulative values. Non-cummulative values are special key figures that are different from other key figures (cummulative values) in data transfers and saving as well as in aggregational behaviour. These are measured in relation to a period in time; that is to say, they cannot be meaningfully cumulated over time. Non-cumulative value are summaraized over-time using exception aggregation.
    Non-cumulative values such as 'number of employess' are cumulated using characteristics such as 'cost center'. It does not make any sense, however, to cumulate the number of employees using different periods. The result at the end of any particular period would be the sum total of number of employees for each posting during the period. This would of course be wrong.
    Instead, the aggregation of the KF can be defined as exception aggregation wherein an additional references characteristics is utilized to tell BW which value to use during the period, in this case, 0CALMONTH is used, in the above example, to indicate that only the last value of 0HEADCOUNT, updated by costcenter, is to be taken for any calender year and month.
    Cummulative vs Non-Cumulatives
    The purpose of non-cumulatives is to optimize the data transfer in BW, the data retention and the database access. The data transfer from OLTP to BW is minimized and only the meaningful data is saved and processed.
    It is recommended that you use non-cumulative values for areas that dont change frequently such as warehouse stock or number of employees.
    Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it for storing the non-cumulative or for inflows or outflows.
    Non-cumulative values are stored with special KF that differ in terms of data transfers and aggregational behaviour.
    Features of NON-Cumulative Values Transfering and Saving Data:
    - NC values are mapped uisng one KF for NC changes or two KF for inflows and outflows.
    -NC are transferred in an initialization run and the change runs that follow (initialization can also be omitted here)
    - A non-cumulative value always has a time-related exception aggegation.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
    http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
    with Example
    Re: Non-Cumulative keyfigure example
    Re: Types of non-cumulative keyfigures
    /community [original link is broken]
    /community [original link is broken]?forumID=131&threadID=29557&messageID=273049
    /community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
    ****Assign Points If Useful*********

  • Validity table for a Non-Cumulative key figure

    Hi,
    I need to make changes to a validity table for a Non-Cumulative key figure.
    I know initially it is done thru Extras- > Maintain Non-Cumulative value but subsequently how to change the parameters ?
    Best Regards,
    -Anurag Dev

    If you decide later that you require more validity-determining characteristics, you can modify the selection using the report RSDG_CUBE_VALT_MODIFY. In this report, the non-cumulative InfoCube is only changed to the extent that the new validity-determining characteristics are selected and the validity table is reconstructed. The structure of the non-cumulative InfoCube remains the same. You do not have to reload the transaction data for it.

Maybe you are looking for