Exceptions on non-Key Figures

Hi,
I'm creating a new query in 'query designer' and I'd like to apply an exception. Is it possible to apply exceptions on non-key figures? I would like to apply an exception on a characteristic (ie if project status = active, highlight it green)?
Cheers.

Hi Simon,
Welcome on Board.
I had a similar requirement and what i did was to use a key figure to display whether it is active or not (with value 1 or 0).
And thereafter used exceptions to colour them as per my requirement.
Let me know if it suits your requirement.
Regards
Shalabh Jain

Similar Messages

Handle non-*** key figure in IM

Hi Gurus
I'm using a non-cumulative key figure in our inventory management scenario. Let me give an example:
after the initialization
       2007-09-01   MaterialA      20
       2007-09-01   MaterialB      10
       2007-09-01   MaterialC      12
on 09/03, goods movement data, only have A&B
       2007-09-03   MaterialA       -1
       2007-09-03   MaterialB       2
so in the report on 09/03, it will be
       2007-09-01   MaterialA      19
       2007-09-01   MaterialB      12
       (MaterialC missing here)
My question is, if there's no movement for a certain material, this material should also be diplayed in the report. Any suggestions?
Best regards
Arthur

Hello Chen,
What are the characteristics defined in the Validity table?
If you use 0calday and remove other characteristics from your validity table you will be able to see the stock for all materials even if there are no movements on a particular day.
   Check this
Validity table
http://help.sap.com/saphelp_sem40bw/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/content.htm
Jaya

How to model a non key figure numeric field

I am new to SAP BI, so please acceopt my apologies if I am asking a very basic question.
I have some numeric fields which are attributes of master data. These fields are not key figures and will not be aggregated. How can I model this in BI? I have to keep them as numeric fields because they may be used in some calculations at reporting.
Thanks!

You can display them as display attribute along with your main infoobject in query.
or
Model it using replacement formula variable by using attribute value as in this [Help|http://help.sap.com/saphelp_nw04s/helpdata/en/03/6ba03cc24efd1de10000000a114084/content.htm] doc.
Hope this helps.

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

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.
but the collumn is blank in the dso
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

Virtual Key Figure on Multicube (RSR_OLAP_BADI)

I've created a virtual key figure (using RSR_OLAP_BADI) for number of days in month [zdays_month]. Everything works perfectly when it's used in a query on a cube cube. BUT, when I try to use it in aquery on a multi-cube, it doesn't. The multi-cube query returns a number = the number of days in the month * the number transactions in that month.
Anyone know how I can force the VKF to execute after the data is returned? I would prefer to not mess with exception aggregation, or key figure properties. I need to keep this VERY SIMPLE for my query developers.
Your assistance is greatly appreciated,
Kenneth

hi,
first try to check whether the query access virtual kf or not, use transaction rsrt, type in the query name, and click technical info or properties, there will some line 'virtual char/kf'.
i think the query may never access the code in BadI because in the code it's set with condition infoprovider technical name, it will cover only the infoprovider, when we access query from multiprovider, which join from one of the infoprovider, it's not automatically have the virtual kf/char, we have to specified the multiprovider name in the BadI, you may change the code as following :
hope this helps.
CASE i_s_rkb1d-infocube.
    WHEN '[your infocube name]'.
ENDCASE.
to
IF i_s_rkb1d-infocube = [your infocube name] or
   i_s_rkb1d-infocube = [your multiprovider name].
ENDIF.
for other infoproviders
CASE i_s_rkb1d-infocube.
    WHEN '[other cube name]'
ENDCASE.

Exception aggregation on Non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Maybe a solution with virtual key figures is an option?
Please help me out!
Best regards, Hans de Klein

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.

Samples of non-cumulative key figure

hi experts,
can u give me samples about:
1> in what scenario should i use the non-***.Value change to create a non-cumulative key figure?
Characteristic            : HEADCOUNT
Aggregation               : (here chose sum?)
Exception Aggregation:(here chose sumation?)
Agg.Reference Char   : (here chose a 0calday?)
N-*** with N-*** Value Change
       Non-***.Value Change: (here what to insert?)
2> in what scenario should i use the inflow/outflow to create a non-cumulative key figure?
Characteristic            : HEADCOUNT
Aggregation               : (here chose sum?)
Exception Aggregation:(here chose sumation?)
Agg.Reference Char   : (here chose a 0calday?)
N-*** with In- and Out-flow
                           Inflow : (here what to insert?)
                           Outflow: (here what to insert?)

hI
1> in what scenario should i use the non-***.Value change to create a non-cumulative key figure?
Characteristic : HEADCOUNT
Aggregation : sum
Exception Aggregation: sumation
Agg.Reference Char : 0calday-----* U CAN GIVE 0CALMONTH too to view head count month wise.*
N-*** with N-*** Value Change
Non-***.Value Change: * If u are maintaining delta value ie if no. of employees joined is 10 and resigned is 6, then delta value is 10-8=2*
in this situation use this type.
2> in what scenario should i use the inflow/outflow to create a non-cumulative key figure?
Characteristic : HEADCOUNT
Aggregation : sum
Exception Aggregation: sumation
Agg.Reference Char : 0calday
N-*** with In- and Out-flow
Inflow : *Inoobject which maintains no of employess joined *
Outflow: *Inoobject which maintains no of employess resigned. *

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

Cumulative and non-cumulative for key figure

Hi,
In the aggregation tab, we have the aggregate type SUM, Max or Min.
we also have the comulative/non-cumulative values.
what's the difference between comulative and non-cumulative values? it would be good to have some example for illustration. and does comulative and non-cumulative have any relation with aggregate type?
Many Thanks
Jonathan

Hi,
what's the difference between comulative and non-cumulative values?
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Example: sales revenue, weight, etc.
Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.Example:stock quantities/-values, number of employees, account balances, etc.
Does comulative and non-cumulative have any relation with aggregate type?
Different types of non-cumulative keyfigures.....are....
1.Non-cumulativekey figure = cumulative keyfigure with excep.aggregation
2.Non-cumulativekey figure withassociated singledelta (cumulative)
3.Non-cumulativekey figure withassociated in-andoutflow(cumulative)
check these links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92c0aa90-0201-0010-17b1-bf5b11c71257
hope it helps...
Regards
chandra sekhar
Edited by: chandra sekhar t on Nov 28, 2008 2:18 PM

Non cumulative key figures

Hi
I understand that there are 3 types of non cumulative key figues with these optiones.
1) cumulative KF with exception aggregation
2) with associated single delta(cumulative)
3)with associated IN and Outflow(cumulative)
I know that we use type 3 in inventory. Has any one used option 2 with Non cumulative KF with associated single Delta?
Please let me know the scenario where it is useful?
Thanks
Vennela

Vennela,
It all boils down to the definition of what cumulation is ...
cumulation refers to straightforward addition of key figures along given filter conditions in the query. This is similar to the sum() operator in an SQL query.
However people will need different kind of aggregation at different points in time other than the standard aggregation / cumulation that is used regularly.
Coming to non cumulation :
1) cumulative KF with exception aggregation
This refers to predominantly formulae - for instance - count of all customers whose sales > 0 - but the report is does not have customer in it and the result is expected. This would mean that the calculation essentially happens at a different level as opposed to the actual query and the key figure cannot be simply summed up.
2) with associated single delta(cumulative)
This is somewhat at a higher level of granularity as opposed to case 3 where you look at all movements. An example here would be You have opening stock and then you get only the debits and credits for the day as opposed to getting stock for all movement types.
Somethign like
opening Stock for the day = 100
Outgoing stock = 30
incoming stock = 10
Here movment type information is omitted and instead is consolidated in the source system itself.
3)with associated IN and Outflow(cumulative)
This has been discussed many a time and can be found by searching the forums...

Count the number of business partners on a non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Would anything with virtual key figures be a solution? Please help me out!
Best regards, Hans de Klein

Non Cumulative Key Figures Simple

Please Help me with this.
I have the measurement Amount "0meas_value" non cumulative key figure and
aggregation properties Sum and Last value and other key figure is 0meas_chg
cUMULATIVE KEY FIGURE. aggregation properties Sum and summation. Now my question if I map the field from R3 Datasource (MEASVALUE) to CUMULATIVE key figure 0meas_chg, will it me a mess??? , Since when i try to put "0meas_value" non cumulative key figure in infosource it gives the error that you cannot put the non cumulative keyfigure in infosource. Please tell how can i then map to non cumulative key figure.?? and if I do not map what will be the problem??
Technical name: 0MEAS_VALUE (Non Cumulative)
Use
This key figure contains the measurement amount of a real estate object on a given key date. The key figure is used for analyzing changes to the real estate portfolio.
and
Technical name: 0MEAS_CHG (Cumulative)
Use
This key figure contains the change to a measurement on a given key date. The key figure is used for analyzing changes to the real estate portfolio.
Technical Data
Aggregation
SUM
Exception Aggregation
SUMMATION
Cumulative/Non-Cumulative Value
Cumulative value
Thanks
Soniya

This kind of issue is difficult to analyze.
Basic approach would be:
1. make sure your BIA revision is the latest.
2. check Tcd: RSDDBIAMON2 and make sure there is no red light
3. rebuild the BIA Index and try again.
Regards,
Patricia

What is cumulative key figure and non cumulative key figure?

Hi Experts,
can anyone clarify me about KEY FIGURES in detail with an example for each topic like
1.Aggregation Tab in Key Figure InfoObject
2.Cummulative
3.Non Cummulative/Cummulative Values
4.Non Cummulative( Inflow & Outflow )
I think it would be better understandable with if explained with example
Thanks,
Venu Gopal.K

HI ,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Example: sales revenue, weight, etc.
Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.
Example: stock quantities/-values, number of employees, account balances, etc.
refer the below document for a detailed study
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366?quicklink=index&overridelayout=true
Regards,
Sathya

Exceptions on non-Key Figures

Similar Messages

Maybe you are looking for