UDC infosource set up as Non- Cumulative

Hi, when I click on Update rules going from UD Connect  3.5 infosource to a DSO, I get the following message:
InfoSource ZCSB_REVENUE is only set up for the initial run for non-cumulatives.
Message no. RSAU122
Diagnosis
This InfoSource is specifically set for the initial run of non- cumulatives. Only certain non-cumulative key figures are therefore displayed in the update rules.
If you want to use this InfoSource differently, you have to change the setting in the source system.
I want to change this behavior to a non-cumulative one. I have tried recreating the UDC infosource, but it does not help. Any Suggestions?

Any inputs, please?

Similar Messages

  • 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 set  Non Cumulative Init flag for Generic datasource

    Hi all,
       I need to create a generic datasource which can be used to initialize the Non Cumulative Cube. Eg. setting the opening balance.
       The STOCKUPD field in the ROOSOURCE should be set to X so that the infopackage will have the "Generate Initial Status" option. But there is no interface available in R/3 pluggin to do this.
    How can this be done? Or is it not allowed for generic datasources as it is only valid of 2LIS_03_BX datasource
    for stock updation.
      Will there be other issues if I change the table entry for STOCKUPD in roosource table for my datasource?
    regs
    Anoop

    Hello,
      any idea on this?
    regs
    Anoop

  • 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.

  • Transformation between DS and DSO missing Non-cumulative KYF

    Hi SDN,
    I installed the business content for CML, and am working with 0CML_DELTA_CAP datasource.  I would like to create a transformation between this datasource and DSO 0CML_O03.
    By default, when you install the CML business content, the datasources use the 3.x dataflow concept (transfer rules, infosources, and update rules).
    I would like to use the 7.x dataflow concept and created a transformation between the 0CML_DELTA_CAP datasource and the 0CML_O03 DSO.  In the transformation, it is missing the fields 0CML_B330, 0CML_B340, 0CML_B360, 0CML_B380 in the datatarget.  These key figures are non-cumulative with NCum Value change (0CML_B330 uses 0CML_B331 as value change).  The value change key figures show up in the transformation, but the non-culmulative key figures do not. 
    Does anyone have any ideas why the non-cuml. kyf are not showing up in the transformation?
    Thanks,

    Hi Brendon,
    The non- cumulative key figures are not mapped in the transformation. Only the 'Inflow' and 'Outflow' key figures for the non- cumulative key figure are mapped.
    You can check the property for the non- *** KF in RSD1, where you would find the corresponding inflow and outflow kf. If both of these are mapped in the transformation, the non- *** kf would calculate the value in the report in which it is included as:
    Non-*** KF value = Inflow value - Outflow value.
    Hope this helps.
    Regards,
    Abhishek.

  • Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

    Hello all.
    I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures.  I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
    Steps I followed:
    1.  Ran initialization of beginning balance with 2LIS_03_BX
    2.  Ran the historical job with 2LIS_03_BF
    3.  Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
    4.  Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
    Now, to this point, everything was fine.  Quantities were as expected.  Dollar values were as expected.  The problem occurs once I load deltas:
    5.  Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
    Query example:
    MATERIALA: 
    Initial Stock Balance = 1000 EA
    Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
    Now, I have the record in BW showing the stock issue of 150.  However, the non-cumulative key figure within the query still shows 1000.  And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance.  It is like it is not recognizing the updates.
    Any help would be appreciated.
    Thanks,
    Brent

    Hi!
    Here is what helped in my case, very similar to your:
    In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

  • 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 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

  • Inventory cube non cumulative KF displaying incorrectly.

    Hi
    I have created a inventory cube which is a copy of 0IC_C03, fed from a DSO which has the all the Material documents.
    I have intitialised using the BX extraxctor to the cube, then loading data from r/3 via the dso. Have MP on top of inventory and revaluation cube.
    Due to an error in the code logic i had to drop the cube and reload the data from the BX PSA and subsequently the DSO.
    my problem started then, the cumulative key figure have gone haywire ie they the balance display rubbish data. the data loaded into the cube is correct
    also if I delete the latest request and reload the request, then the  KF display correctly. strange!
    I also the same problem for value as i have a revaluation cube. the inventory values are wrong, when i do a list cube from the MP all is ok.
    i checked the validity slice rsdv, it is ok.
    i also only have 0calday as the non cumulative setting.
    Another thing i noticed was if filter the material by one plant then i get the correct value, if i try to display all plants then it all the balances go incorrect.
    also if i see the balances by month only the latest month is incorrect.
    if you need more info please feel free to ask.
    appreciate if some can propose a solution
    Lawrence
    Edited by: lcoelho on Oct 14, 2011 7:03 PM

    Hi Lawrence,
    SAP suggests to upload non-cumulatives NEVER from a DSO but from the PSA in parallel to DSO and Cube.
    Andreas

  • Non-cumulative values

    HI All,
    when I run a query of a non-cumulative infocube,there's always a "initial record"  which actually doesn't exist in the fact table. Documents say "This entry does not remain physically in  the table, but it is available for rebuilding the non-cumulative values". So where exactly is the initial value stored ?
    Thanks
    han.

    Hi,
    What is teh DataSource and InfoCube?
    If you are talking about 0IC_C03, please see the steps.
    Treatment of historical full loads with Inventory cube
    Setting up material movement/inventory with limit locking time
    See about  Non-Cumulatives 
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
    Thanks
    Reddy

  • 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.

  • 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

  • Include non-cumulative key figure in InfoSpoke

    Hi Experts,
    I am trying to create InfoSpoke for AR Line Item Cube(0FIAR_C03) with all infoObjects.
    This includes non-cumulative key figures such as
    0DSCT_DAYS1 (Days for first cash discount)
    0DSCT_PCT1 (Percentage for first cash discount)
    However, InfoSpoke run failed and following messages is displayed.
    “Error in SQL Statement: SAPSQL_ILLEGAL_AGGREGATE NOP”
    Does the infoSpoke not support non-cumulative key figures?
    It worked fine when I remove all the non-cumulative key figures from the InfoSpoke.
    *I certainly set 1 for 0RECORDTP(Record Type) in the selection tab as SAP Help instructed
    Thank you for your answers in advance.

    Try OSS Note Number: 850428.

  • Non-cumulative extrator

    Has created own extractor on the basis of the functional module
    Where to specify, that an extractor for run Non-cumulative values

    Hi,
    These are the SAP provided Delta Enabled Extractors.
    2LIS_03_BX              Material Stocks
    2LIS_40_S278          Transfer BW stock
    When you create the InfoPackage on these InfoSource, you shud definitely get the option for Generating Opening balance.
    I have a PPT for Non-CUmulative KF I can send you the same.
    Also can you verify if you are on the same page for Sap.Help ?
    http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm
    Hope it helps,
    Pradip Parmar

  • Loading non cumulative values

    hi,
    Why do we require two separate infosources for loading the initial non cumulative value and the subsequent non cumulative changes?
    Regards
    Deepti

    Hi Deepti,
    Basically you can omit the first step of  initialization with one infosource and just you can use only infosource to laod full data as two infoaources are seldom used.
    But basically first infosource is for initialization(One value for a combination of caharcteristica) and the second one brings the change after wards).
    But this funcionality you can achieve through one infosource also no need for another one.
    Even an int and full repair request will do the same thing and subsequent delta's will pick the changes
    More information you can find on this link.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/02/9a6a22244411d5b2e30050da4c74dc/content.htm
    Assign points if helpful
    Thanks

Maybe you are looking for