Non cumulative KFS

Hi Experts,
can any one pls send some non cumulative KFS, with scenario.
With Thanks&Regards.

Hi Raghav,
Have a look at the help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Go through these.
Re: Types of non-cumulative keyfigures
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
See the following threads
non-cumulatives KF in reporting
Re: use of non cumulative keyfigure
Re: When do we use Non-Cumulative values?
Key figures:
1. Cumulative Vaules
2. Non – Cumulative Values
Cumulative Values:
Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period – specific Values).
Example:
Revenue
Non – Cumulative Values:
Non – Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non – Cumulative keyfigure with Associated Single Delta:
If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
For Non – Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Check this very useful docu.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
Hope this helps.
Regards,
Ravikanth

Similar Messages

  • 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

  • Incorrect Non-cumulative values in a Multi-Provider

    Hi everyone,
    I have created one Multi-Provider using Info-cubes 0IC_C03 & ZSD_C03.
    The requirement was to get the "Invoice value" instead of the "Stock Issued Value" in 0IC_C03.
    I have used the characteristics 0CALMONTH, 0CALDAY, 0MATERIAL, 0PLANT & 0SOURCESYSTEM in the MP.
    However, when i execute a query based on the Multi-Provider, I notice that all Cumulative Key-Figures are showing correct Values, but the Non-Cumulative KFs (Val Stock Qty etc) are showing incorrect values (Large Quantities are displayed).
    I am not sure why its happening? Please Help
    Regards,
    Srikar

    Hi Ram,
    Previously i was using a variable on 0CALMONTH for restricting the data which resulted in Incorrect NC values.
    Later on, when I changed the Restriction based on 0CALDAY, the query was working fine.
    Moreover I also included all the Characteristics present in the Validity Table of the Cube 0IC_C03 in the MP which i didn't initially.
    I guess those two changes made the difference.
    Regards,
    Srikar

  • Non-cumulative keyfigures in virutual multi providers in BI-7.

    Is it possible to use non-cumulative keyfigures in virutual multi providers in BI-7? The Non-cumulative KFs are working in the cube. But when we create a virutual MP that contains this cube. They all are showing zero. Is this supported at all? Is there a note that we need to apply? Please help! This is BI-7.
    Thanks.

    Hi,
    Do not use more than one InfoCube with non-cumulative key figures in a MultiProvider since this may result in incorrect numbers in the query.
    Refer to SAP Note 690475 on SAP Support Portal.
    Refer
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/5617d903f03e2be10000000a1553f6/frameset.htm
    Thanks,
    JituK

  • Exporting Non-Cumulative KF to Cumulative

    We wish to export Inventory data from BW to a CSV file through Open Hub.
    The catch is that we have a Non-Cumulative KF with InFlow & OutFlow whose value needs to be exported as well @ the month summary level. Hence was wondering if there is any specific transformation thats possible to achieve this.
    Regards
    Anujit Ghosh

    We have 4 Cubes holding Inventory Line Item data.
    Some of the Cubes have Non-Cumulative KFs.
    We are planning to have a Summary Cube and load data from the 4 above mentioned cubes before exporting the data through Open Hub.
    I don't have much knowledge on APD so wanted to know if its possible to load the summarised data into another cube using APD or APD itself will store the data physically which can be used.
    If you have any relevant documents  that would be helpful.
    Regards
    Anujit Ghosh

  • Cumulative and Non Cumulative KF

    Hi all,
               What are Cumulative and Non Cumulative KFs. How do we create it and where do we use them?
    Thanks in advance,
    Sekhar

    Hai <b>Sekhar</b>...
    Some of the Information Given Below......
    <b>Key figures:</b>  
    1.     Cumulative Vaules
    2.     Non – Cumulative Values
    <b>Cumulative Values</b>:
              Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period – specific Values).
    Example:
              Revenue
    <b>Non – Cumulative Values:</b>
              Non – Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
    <b>Cumulative Keyfigures With Exception Aggregation</b>:
              It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
    <b>Non – Cumulative keyfigure with Associated Single Delta:</b> 
                           If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
    KF1 (initial) STOCK (non-***.) = 100
    KF2 flow = -30
    KF2 flow = 70
    KF1 (final) STOCK (non-***.) = 140
    <b>Non-cumulative key figure with associated in and outflow:</b>
                             This is the case of 2LIS_03_BF KF stocks fields.
    Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
    You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
    KF1 (initial) STOCK (non-***.) = 100
    KF2 (out))flow = 30
    KF3 (in)flow = 70
    KF1 (final) STOCK (non-***.) = 140
    <b>Website Addresses For Non – Cumulative KeyFigures:</b>
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html 
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
    Re: Non-Cumulative keyfigure example   
    Re: Types of non-cumulative keyfigures 
    /community [original link is broken]
    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    /community [original link is broken]?forumID=131&threadID=29557&messageID=273049
    /community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
    <i><b>Assign Points If it Helps......</b></i>
    <u><b>BalajeeKannan</b></u>

  • Non cumulative infocube without BX

    Hi Experts,
    I need to compress and create aggregates for the inventory cube (Has Non cumulative in/out flow KFs)
    We do not use BX as all of the initial stock levels are defined using movements.  Does this change anything?
    Which way is it as I have seen both answers posted in this forum?
    BF-init: Compression without marker update
    BF-delta: Compression WITH marker update
    OR
    BF-init: Compression without marker update
    BF-delta: Compression WITHOUT marker update
    Thanks,
    Chris

    If you are not bringing BX, all BF should be compressed with marker update.

  • 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

  • Non Cumulative Key Figures Aggregations

    Hello Forum.
    This is regarding results of non-cumulative keyfigures.
    We have a non cumulative keyfigures whose aggregation behaviour is SUM with exeception aggregation as LAST.
    Now out inflow kefigures has the value : 700 and outflow has 164 but on query the non cumulative keyfigure displays 1415 which is correct.
    Can anyone plz tell how to check this aggregations because for few other records we have incorrect values.
    Thanks & Regards
    Ashish

    non-cumulative keyfigures can be interpreted as follow:
    KF = Current value + inflow - outflow
    in yr case exceptional aggregation is set as LAST , so for a given transaction data KF will be evaluated as LAST value of the aggregation
    let me explain this with an example :
    for a given material , KF is calcluated as summation of KFs for another char (eg Material Type) of the same material. =>Current value = KF + KF + KF (for three diff mat type)
    At Query run time KF will be calculated as KF = Current value + inflow - outflow...
    now in query we will be having more KFs:
    KF  Current value1 + inflow1 - outflow1 (=Current Value2)   for mat typ1
    KF  Current value2 + inflow 2- outflow2   (=Current Value3) for mat typ2
    KF  Current value3 + inflow3 - outflow3   (=Current Value4) for mat typ3
    the above will be interpreted internally and query will show result Current Value4 (because exceptional aggregation is LAST=>pls note that Exp aggregation runs at Query run time)
    Its a bit tough to under the concept but u have to keep little patience ...

  • Non Cumulative KF VS Normal KF with exception aggregation

    What is the purpose that is served by "non-cumulative key figures" and is not served by "normal key figures with exception aggregation"?
    Inflow and Outflow can also be mapped into a single key figure at update rules level.
    Why un-necessary complications like two additional KFs and marker update etc?
    Why can't we store actual inventory value on daily basis in a NORMAL key figure with exception aggregation on time?
    Also, I heard that data amount will be huge if you don't use non-cumulative key figure. I am not able to understand why?
    I HAVE ALREADY GONE THROUGH ALL THE HELP DOCUMENTATION AND ALL THE PREVIOUS THREADS. I DID NOT GET ANSWER TO THESE QUESTIONS.
    THANKS IN ADVANCE,
    Anup

    Anup,
    Q1: Why can we not store the actual inventory against the person -
    In this case you will end up storing day wise information of stock for the person / material - this will lead to increase of your data volumes depending on the scenario.
    Example :
    Day Level stock only
    Record Structure :
    Material | End of day snapshot Stock| date
    pipe | 100|20.2.2008
    pipe|100|21.02.2008
    pipe|100|22.02.2008
    pipe|80|23.02.2008
    Here you can notice that the material pipe has been sold on 23.03.3008 and no sale has happened previously - however since your extractor will give you end of day stock for all materials you will get 2 additional records
    In an opening and closing stock scenario
    Opening stock
    Marker|
    pipe|100|20.02.2008
    opening stock|closing stock
    pipe|100|100
    pipe|100|100
    pipe|100|80
    Here the values will get overwritten and compared with the marker and calculate that the stock is 80 or 100 depending on the date. I am not able to give a proper example but hope I have addressed it in part.
    Also it is a Non *** KF because if you look at stock for pipe over 3 days you will get 300 in the first scenario - this is wrong
    and for the next scenario with opening and closing stock
    it will ideally be
    100 ( your marker) -100100-100100-100+80 = 80
    this calculation is done at runtime and gives the right output.
    In the other case you can check stock only on a date basis and with the assumption that the stock data is current for that day.
    Hope it addresses youor question.
    Arun
    Day 1:

  • What is the difference between cumulative and non cumulative keyfigures?

    Hi Friends
    What is the difference between cumulative and non cumulative keyfigures, when we r using  the cumulative and non cumulative
    Regards
    Ravindra

    Hi Ravindra,
    Have a look at the help:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
    Go through these.
    Re: Types of non-cumulative keyfigures
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
    See the following threads
    non-cumulatives KF in reporting
    Re: use of non cumulative keyfigure
    Re: When do we use Non-Cumulative values?
    Key figures:
    1. Cumulative Vaules
    2. Non – Cumulative Values
    Cumulative Values:
    Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period – specific Values).
    Example:
    Revenue
    Non – Cumulative Values:
    Non – Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
    Cumulative Keyfigures With Exception Aggregation:
    It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
    Non – Cumulative keyfigure with Associated Single Delta:
    If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
    KF1 (initial) STOCK (non-***.) = 100
    KF2 flow = -30
    KF2 flow = 70
    KF1 (final) STOCK (non-***.) = 140
    Non-cumulative key figure with associated in and outflow:
    This is the case of 2LIS_03_BF KF stocks fields.
    Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
    You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
    KF1 (initial) STOCK (non-***.) = 100
    KF2 (out))flow = 30
    KF3 (in)flow = 70
    KF1 (final) STOCK (non-***.) = 140
    Website Addresses For Non – Cumulative KeyFigures:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
    Re: Non-Cumulative keyfigure example
    Re: Types of non-cumulative keyfigures
    /community [original link is broken]
    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
    /community [original link is broken]?forumID=131&threadID=29557&messageID=273049
    /community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
    Check this very useful docu.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
    ****Assign Points If Helpful****
    Regards,
    Ravikanth

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

  • Aggregates on Non-cumulative InfoCubes, stock key figures, stock, stocks,

    Hi..Guru's
    Please let me know if  anybody has created aggregates on Non-Cumulative Cubes or key figure (i.e. 0IC_C03 Inventory Management.)
    I am facing the problem of performance related at the time of execution of query in 0IC_C03.( runtime dump )
    I have tried lot on to create aggregate by using proposal from query and other options. But its not working or using that aggr by query.
    Can somebody tell me about any sample aggr. which they are using on 0ic_c03.
    Or any tool to get better performance to execute query of the said cube.
    One more clarification req that what is Move the Marker pointer for stock calculation. I have compressed only two inital data loading req. should I compress the all req in cube (Regularly)
    If so there would be any option to get req compress automatically after successfully load in data target.
    We are using all three data sources 2lis_03_bx,bf & um for the same.
    Regards,
    Navin

    Hi,
    Definately the compression has lot of effect on the quey execution time for Inventory cubes <b>than</b> other cumulated cubes.
    So Do compression reqularly, once you feel that the deletion of request is not needed any more.
    And ,If the query do not has calday characterstic and need only month characterstic ,use Snap shot Info cube(which is mentioned and procedure is given in How to paper) and divert the month wise(and higher granularity on time characterstic ,like quarter & year) queries to this cube.
    And, the percentage of improvement in qury execution time in case of aggregates is less for non cumulated cubes when compared to other normal(cumulated) cubes. But still there is improvement in using aggregates.
    With rgds,
    Anil Kumar Sharma .P
    Message was edited by: Anil Kumar Sharma

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

  • More than Non-cumulative cubes in one MultiProvider

    Hi There,
    I have got two non cumulative cubes and want to build a MultiProvider on them.
    Got information at couple of places on help.sap.com at one place it says MultiProvider can have more than one non-cumulative cubes at other place it says it can't. What is the right suggestion?
    Thanks
    Vikash

    Hi,
    From the performance perspective you should not use more than one Non Cumulative Infocube in a Multi Provider. If you user more than one the query will not execute parallel and execute in sequential which leads to delay in query run time.
    This is a recommendation from SAP not to use morethan one Non Cumulative Cubes in a MP.
    Cheers

Maybe you are looking for

  • Reader 9.2 - "can not be used to view PDF files in a web browser"

    Hello, I recently deployed Adobe 9.2 within our organization. I used the Adobe Customization Wizard 9 to transform the install set, and selected the "Display PDF in Browser" option as default. When opening a PDF linked from a web URL, we get the mess

  • Function in shell script

    Hello, I have the following function in PL/SQL: Create or replace function fqman."test" (name in varchar2, url in varchar 2, page in varchar2, uname in varchar2, password in varchar 2, key_ in varchar2, pass in varchar2, file1 in varchar2, file2 in v

  • Can we get directory structue of other machine from JFileChooser?

    I want to display the directory structure of the other machine, in the network where my RMI client is running. Is this possible using JFileChooser.

  • Co-Ordinate precision and performance

    I have data with a geometric tolerance of 0.05 The precision of the co-ordinates can be up to 3 decimal places in the SDO_GEOMETRY object. (0.001) However when we query the data through MapXtreme web application the query window passed in to the seco

  • Windows 7 Upgrade Option Program

    Alright, I did all this and faxed my proof of purchase to the given fax number, and I haven't received a reply yet. And as part of the e-mail from before,  "We will send you an email when we have confirmed your eligibility via your proof of purchase.