Problems with Non-cumulative Cube

Dear All,
I have a cube with non-cumulative key figures. An DSO supply data for that cube.
The query  on that cube will  gets wrong results sometimes. But after removing all the data from that cube and uploading again from the DSO, the query presents the right result.
Is there anybody knows why and how to fix it?
Thanks.
Bolun

Hi
Non-cumulative Cubes to be defined correctly with Inflow and Outflow because it depends on Which option you choose depends on how you want to evaluate the non-cumulative key figure, and also the Marker Update you are dealing with.
The key figures for non-cumulative value change or for inflows and outflows are normal cumulative key figures that have u2018summationu2019 both as aggregation and exception aggregation.  Generally, Non-cumulative key figures always have summation as standard aggregation.
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Hope it helps and clear

Similar Messages

  • 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

  • Problem with non cumulative KF

    Hi All,
    I have some problem in the calculation of non cumulative KF. The fields it uses for inflow and outflw as same value in SAP system but the nom *** KF is showing a different value For eg. it uses receipt total stock as inflow and quantity total stock as outflow. The value for receipt total stock is 3309000 and that of quantity total stock is 3588850. But the non *** KF is being shown in report as 8483410. Can anyone pls explain troubleshoot. Please provide me quick responses.
    Thanks in advance,
    Sananda

    Dear Dirk,
    Thanks for response.
    Describe please what do you mean as "use cumulative instead of non-cumulative"?
    My cube is material stock by storage location, stocks by storages define as non-*** KF on in- and out-comes. I need in BEx real quantity and value stocks independently of the query navigation detailed level.
    Are there ready-made apropriate BEx implementaions from SAP for my case?
    About virtual KF - I've nevere before didn't use virtual KF. From what I'll must to start? Where I can search appropriate knowledge?
    Kind regards,
    Igor Podgibalov,
    Saint-Peterspburg, Russia

  • Archive Stock Cube with non-cumulative nature

    Hi All,
    I have been trying to archive the Inventory (Stock) Infocube as we have more than couple of hundread million records in the cube and it is taking long time to execute query.
    I know how to acrive the regular cubes and DSOs, but I couldn't find any helpful documentation where I can know how to archive the Infocube with non-cumulative nature or containing Marker update.
    Can anyone pleaes post the link of document?
    BTW, we are using BI7.0 SP15
    Thanks,
    Dhaval

    Hi,
    There are two ways of archiving data from a non-cumulative InfoCube - time slot archiving and archiving with selection characteristics.
    Time slot archiving (recommended)
    As an archiving method, you must choose for a non-cumulative InfoCube, time slot archiving for the time reference characteristic. When you recreate an archiving object for a non-cumulative InfoCube, this characteristic is also suggested by the system.
    Only archive non-cumulative changes up to a specific point in the past. This reduces the volume of data in the InfoCube. The marker (= end non-cumulative) remains unchanged.
    In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements Only option.
    You are only able to archive the marker if you also archive all of the non-cumulative changes. Subsequently, the contents of the non-cumulative InfoCube are archived completely. In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements and End Non-cumulative option.
    You must archive the non-cumulative changes (for all times) first, and then archive the marker in a separate archiving run, so that the non-cumulative changes and the marker are stored separately in the archive.
    The advantage of time slot archiving is that archiving runs can be carried out periodically using a single variant with a relative time restriction. The alternative archiving method described below does not have this advantage.
    Archiving with selection characteristics
    In some cases, archiving based only on time slots does not have the required effect of reducing the volume of data in the InfoCube. This is the case, for example, if the non-cumulative bearing objects are subject to high fluctuations, meaning that data is constantly being loaded for new objects and old objects are made obsolete. With time slot archiving, the end non-cumulative remains for all objects until all of the data in the InfoCube is finally archived, even if all the non-cumulative changes for an object have been archived already.
    In this case, you want to archive and delete completely any objects that are no longer active in the InfoCube. This means archiving the marker as well. For other objects that are still active, you only need to archive the non-cumulative changes from the past, which means the marker is retained.
    When you define the archiving properties for a non-cumulative InfoCube, do not therefore choose the time slot archiving method. Instead, select individually the characteristics that are relevant to restricting archiving runs. The time reference characteristic should also be included in this selection whenever possible.
    Using this archiving method, for each archiving run, you need to create selection conditions in a variant. In the variant for the archiving run, in addition to the selection conditions, you can also specify for the selected characteristics whether or not non-cumulative changes and marker data is archived. If you choose to archive marker data, be aware that the time selection contains the maximum value for time.
    Please refer to the below link to archive the data for Stock Cube:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/c219fe9a46194aa66d55254fdab182/frameset.htm
    Hope this helps.
    Regards
    Tanuj

  • Error when activating Cube with Non-cumulative KF

    Hi all,
    I'm trying to re-activate an InfoCube but now with non-cumulative KF and I'm getting the error message "Object YYYYY could not be activated".
    Please help!
    Best regards,
    Thiago Modro

    hi,
    have you included the neccessary time characteristics
    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Ramesh

  • Compress non-cumulative cube

    Hi Gurus! I'm working on a retail project. I've created an infocube based on 0RT_C36 to keep the stock movements. It is a non-cumulative cube.
    After the load of the initialization data (2lis_03_bx) the compression with the option "no marker update" unchecked runs fine. The process compress about 300.000 records in a few minutes.
    But after the load of historical movements, the initialization of 2lis_03_bf, the compression with the option "no marker update" checked runs for more than 10 hours. There are 400.000 records loaded in the fact table (F table). I've checked in ST22, ST21 and no errors or dumps appear. In SM50 the process was running and the number of inserted records was 250.000. After that the basis gay kill the compression...
    Is it normal? Is there anything I can check to speed up the process?
    Thanks!

    Hi Federico,
    This a common problem.
    You can find also another message in this Forum section with the same problem.
    You need to restrict the number of the request that you are going to compress for every job. Try also to enlarge TableSpace, in particular the temporary TableSpace, that you can subsequently reduce.
    Consider that any other job, like query from user or other uploads, reduce the speedof the compression.
    Ciao.
    Riccardo.

  • How can I  extract non-cumulative cube data to another cubes ?

    Dear Expert,
             I copied inventory cube 0ic_c03 to  a new cube : ZIC_C03  , then I loaded the data of 0ic_c03 to the new cube ZIC_C03 . 
    the loading was sucessful, but  the result of  report of the ZIC_C03 was not correct. After looking into the problem, I found out
    the new cube can successfully extract data related with "Goods movement" & "Revaluation", yet the extract of "Open Balance" does not seems to work.
             I have read through Note:375098, in which I could not find (InfoObject 0RECORDTP) in my start routine as mentioned in the solution
    ,and the note was not mentioned valid for BW 3.5 release.
             How can I  extract non-cumulative cube data to another cubes correctly in BW3.5 release SP20? 
       Thanks !

    Hi,
    Check Routines in Update rules wether same code is wrriten in  new cube
    cheers,
    Satya

  • Building an aggregate on non-cumulative cube

    Hi all,
    My Question is very specific, kindly review the scenario below :
    1) we have non-cumulative cube which was loaded with
    a) Data from BX - initial stock - compressed in the cube with marker update
    b) History load - compressed in the cube with "No Marker update"
    c) Deltas - compressed in the cube with "with marker update'
    I wish to now create an aggregate. Will the Intial-fill program generate the markers correctly in the aggregate?? i think i read an OSS note - which i cannot locate any longer - that it is not possible & markers may not be accurate on the aggregate
    Arvind

    Note 1116174 - MultiProvider on non-cumulative cube
    It solved my problem
    Regards,
    Vikram.

  • 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

  • Query for Future period on a non cumulative cube

    Hi Colleagues,
    I have a non cumulative cube. It has data till June,2006. When I query on the cube to report the balance with period as "July,2006" it doesnot return anything. What I expected is that it would show me the balance value as of June,2006 which is the last period for which there is data.
    Am I missing anything ?
    Regards,
    priyadarshi

    If you filter by jul06 and there is no data in cube, no matches with selection happens. You need to select any data to apply calculation of balance, try to select a range of months, with an offset.
    Maybe if you put the month in free characteristics instead in filter section ir worked.

  • InfoProvider with non-cumulative key figures

    what does infoprovider with non-cumulative key figures...
    noncumulative key figures..
    looking for reply

    it's property of the KF... nothing do with Cubes or ODS.
    Name itself telling non-Cumulative KF. We can't cumulate this KF. Suppose take the Case Sales Amount and No of Employees. Sales Amount can be cumulated over Time. But No Employees can't be cumulated. Same is the Case with Stock as well.
    Nagesh Ganisetti.

  • Activation error on Multi Provider which has Non-cumulative Cube

    Hi,
    My company has upgraded the BI 7.0 from 3.5.
    It is working fine so far.
    But I met the below message and could not activate it when I generate the multi provider which has Non-cumulative Cube.
    Define the characteristics of the validity table for non-cumulatives (Message no. R7846)
    And then I checked the Single cube but Single cube has no error.
    I think this is program error and searched the notes in OSS but could not find.
    Does any expert know this issue?
    Thank you.

    Hi lee,
    validity slice tables need to be defined for cubes using non cumulative key figures.
    In this we need to specify the characteristic combination on which this table has be maintained.
    The maintanence can be done from cube change mode, menu bar extras--> maintain non cumulative values.
    This table constantly gets updated with validity dates as we upload data.
    An report on this can be seen in tcode RSDV.
    Naveen.A

  • Work around for including Non cumulative cube in an infoset.

    Hi Experts,
    I have 4 non cumulative infocube in my production, for another reporting purpose I have to use those non-cumulative cubes combining another  DSO in an infoset, but the infoset is not allowing me to include non cumulative infocube in it.
    The non-cumulative infocube contains 2 non cumulative keyfigures, those keyfigures are needed for my new reporting, to get the infoset logic(inner join) is there any other possible way to get the data ?
    Please let me know. your valuable input will be appreciated. Thanks in Advance.

    Hi Kalpana,
    Try with multiprovider.
    Otherway round could be creating DSO and creating transformation from DSO as well as non-cumulative infocubes (full update) and report on newly created DSO.
    Hope that helps.
    Regards
    Mr Kapadia
    *Assigning points is the way to say thanks*

  • Validity slice is not correct for non-cumulative cube

    Hello Expert,
    There are two non-cumulative cube, say cube1 and cube2. Cube2 has only one more dimension of PLANT than Cube1.
    Cube2 is copied from cube1 and change the char of validity.
    Cube1 & cube2 use the same fill data source. That is, first load with opening balance and second with delta.
    char of validity for cube1: calendar day & material
    char of validity for cube2: calendar day & plant.
    The query based on cube1 works well. To say cube2, the validity slice(in TXN RSDV or TBL /BIC/TCUBE2) is not correct. There is only one record which contains BLANK plant.
    There are plants in F table.
    I tried the following steps to recovery the validity slice, however, it made no sense.
    1) PGM RSDG_CUBE_VALT_MODIFY to rebuild the validity slice structure
    2) FM RSDV_VALID_RECREATE with I_REBUILD_FROM_FACT = 'X' to create validity slice from fact table.
    Would you please suggest?
    Thanks
    XY

    Hi XY,
    For sure, running the RSDV_VALID_RECREATE function module in SE37 will recreate the validity table. And you can use the parameter "X"  in the parameter I_REBUILD_FROM_FACT if the entire fact table should be  read.
    Also, to change the validity slice manually in tcode RSDV you should:
    - overwrite the column 'To mode' with a 'F', which mean Fixed
    - & then the 'Fixed to time' with your new value.
    There is a program which allows you to modify it: Program   > RSDG_CUBE_VALT_MODIFY
    At
    Nadja Xavier

  • Validity Table in Non cumulative cube

    Hi Friends,
    What is the use of validity table in Non cumulative cube?
    I have already studied the document 'How to Inventory
    Please can any one explain me with example.
    Thanks & Regards,
    Ramnaresh.P.

    Hi,
    Validity table is created for non-cumulative key values.
    Non cumulative key figures are one which are not possible to cumulate such as head count, inventory amount, these are always in relation to a point in time.
    Regards,
    Shiva.

Maybe you are looking for