Difference between Key figure and a Key field?

Difference between Key figure and a Key field?
Thanks,
Pramod

Hi,
Key fileds as just like your primary key of R/3 Tables.
Key figure are type of info object which is used to hold amout,value for your info providers..
check this link for key figures and there types...
http://help.sap.com/saphelp_bw31/helpdata/en/80/1a63b3e07211d2acb80000e829fbfe/frameset.htm
under "Tab Page: Aggregation". you can be able to find three aggregation options:
Minimum
Maximum
Sum
Types of non-cumulative keyfigures
Regards,
Viren.

Similar Messages

How use non cumulative key figure and noncumulative key figure screenshot

how use non cumulative key figure and noncumulative key figure screenshot

Hello,
Please see this docs for Non-Cumulative and Snapshot scenario,
[How to Handle Inventory Management Scenarios in BW (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
[Non-Cumulative Values / Stock Handling|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366]
Thanks
Chandran

Difference between Transaction Figures and Line Items

Hi,
I gone through FI like FI-GL,FI-AR,FI-AP..there i find...
Line Items & Transaction figures as main...like
in FI we have
Line Items - 0FI_GL_4,0FI_AR_4,0FI_AP_4 etc...
Transaction Figures - 0FI_GL_6,0FI_AR_6,0FI_AP_6 etc...
Now Can some please explain...
what exactly Line Items are?
What exactly Transaction Figures are?
How data flows from end to end in FI? i.e where exactly GL,AR,AP comes into picture..how they are internally related?
Some one please explain me in detail (with expamles if possible) and quick reply is much appreciated...
Regards
Ramsunder

Hi
What exactly line items :
Line items are document items that were posted to a specific account. In contrast to a document item a line item only contains the information from the document that is relevant from the account view.
You can display the following line items:
Open items, Cleared items, Noted items, Parked items ,Items with special G/L transactions (in Accounts Receivable and Accounts Payable),Items with customer or vendor items (in Accounts Receivable and Accounts Payable)
You can display the line items for the following account types: Customer accounts,Vendor accounts,G/L accounts.
What exactly Transaction Figures are?
Transaction figures are the sums of line items on the debit or credit side. The balance is the difference between the debit and the credit transaction figure.
If you take General ledger
AP records all accounting transactions for dealings with suppliers(Vendors). Much of its data is obtained from procurement (Materials Management).
AR records all accounting transactions for dealings with customers. Much of its data is obtained from Sales and Distribution.
Asset Accounting records all accounting transactions relating to the management of assets.
Travel Management manages and calculates travel costs and supports travel planning and travel expenses.
Bank ledger supports the posting of cash flows.
Regards
Chandra Sekhar T

Difference between Dimension Id and Dimension Key

I am reading the third chapter of Rittman's OBIEE book on design of Repository.
It says while building the BMM, don't drag the dimension Id columns from physical layer to logical layer as the BI Server takes care of the join for you but make sure you drag across the dimension key columns as you will need these later on to create your logical table keys.
Can someone enlighten me on what is the difference between a dimension id and dimension key (may be with an example).
Thanks.

Besides the theory says that a fact table can reference any level of a dimension, I couldn't do it with OWB. I don't know if there is a specific way to do that, but I only could assign a dimension detail level to a fact table.
The ID's can have different values when I use a hierarchy in a dimension. OWB generates automatically negative ID's for the more summarized levels.
For example, a product dimension with 2 levels: category and detail. If the product has 4 categories and 20 products (detail level), the table has 4 rows for categories with negative id's. Each row has a category and the fields specific for detail level are empty. The table will have other 20 rows for the detail level, with all fields filled, and all id's positive. The table will have 24 rows in the end.

"new selection", restricted key figure and basic key figure

Hi,
I have a test report and i have a basic keyfigure "ZRevenue" and "restricted key figure"(its defined over "ZRevenue") and
a "new selection"(its defined over "ZRevenue").
Now that i have "material number" and "material color" and "request id" in the rows. ("Material color" is a navigational attribute of material number).
In the column level i have a basic key figure "ZRevenue" and "restricted key figure"(its defined over "ZRevenue") and
a "new selection"(its defined over "ZRevenue") .
In a "restricted key figure" or "new selection", we can include a basic key figure or new formula or calculated key figure or an already restricted key figure into it, then we restrict it, with one or more characteristic values. In the report output we get KF values only for those characteristic values, with which it has been restricted. Please correct me if my understanding is wrong.
Initially i restricted the "new selection" (with material number 1 to 3) and "restricted key figure" (with material number 1 to 4).
In the cube i have material numbers 1 to 11. Now all the values were displayed from 1 to 11, but for the
"new selection" (with material number 1 to 3) and "restricted key figure" (with material number 1 to 4) i got values only for 1 to 3 and values for 1 to 4 respectively. This is as expected and is working fine.
Now i tried to restrict the basic keyfigure "ZRevenue" with material number 1, the output was only until the material number 4 (this is the greatest value of the material number defined over the "restricted key figure").
Then i tried to restrict the "new selection" (with material number 1 to 9) , then the output was from 1 to 9 material numbers.
If i remove the restriction over the basic keyfigure "ZRevenue" , then i get all the material numbers from 1 to 11, for "new selection" i get values for the material number 1 to 9 and for "restricted key figure" i get values for the material numbers 1 to 4.
Can some one explain me why this behavior?
Edited by: sapbi enthusiastic on Jan 31, 2012 11:48 AM

Hi,
This is where set theory comes in handy
So what you have is a basic KF (BKF), a selection (SEL), and an RKF.
When producing an output, BEx seems to be looking for the union of all the restrictions you place on these. So when your BKF is not restricted, the union comes out to everything in the underlying DSO. When you restrict the BKF for material number 1, this is how the restrictions might have been processed internally
BKF: Restriction on material 1
RKF: Restriction on material 1-4
SEL: Restriction on 1-3
Union of these three: 1-4
When you remove the BKF restriction and make SEL restricted to 9, this is how it plays out
BKF: NO Restriction on material
SEL: Restriction on material 1-9
RKF: Restriction on 1-4
Union of these three: everything.
As the union ends up giving you everything, you get 11 records. However, as SEL is restricted for 1-9, the SEL will have values for the materials 1-9. Likewise for RKF, you'll get values only for materials 1-4. Hope this clears things up!
Regards,
Suhas

Difference Between D1 PAL and DV PAL field order

Hey guys,
so one of the engineers at work stumped me and i wanted to get your thoughts on this.
Full D1 in NTSC is 720x486 with a PAR of 0.9 (approximate) with a dominant bottom field order.
DV NTSC is 720x480 with a PAR of approximately 1.111~ with a dominant top filed order.
obviously, the DV codec is cutting off 3 odd lines of resolution at the top and bottom, therefore the field reversal and resizing the image (where i get the PAR of 1.111~).
so this is my question:
Full D1 PAL is 720x576 with a PAR of 0.9375 and a dominant bottom field order.
why is DV PAL also 720x576 with a PAR of 1.0666 ~ and a dominant top field order?
thanks for any help, since i know this is not really an editing question
Mikey M.

Hey guys,
so one of the engineers at work stumped me and i wanted to get your thoughts on this.
Full D1 in NTSC is 720x486 with a PAR of 0.9 (approximate) with a dominant bottom field order.
DV NTSC is 720x480 with a PAR of approximately 1.111~ with a dominant top filed order.
obviously, the DV codec is cutting off 3 odd lines of resolution at the top and bottom, therefore the field reversal and resizing the image (where i get the PAR of 1.111~).
so this is my question:
Full D1 PAL is 720x576 with a PAR of 0.9375 and a dominant bottom field order.
why is DV PAL also 720x576 with a PAR of 1.0666 ~ and a dominant top field order?
thanks for any help, since i know this is not really an editing question
Mikey M.

Selection Key Figures and Key Figures

I am building a query and I need to combine Key Figures and Selected Key Figures so that they appear on the same row. However, when I try to do this I get a message that you cannot put the elements in the same structure. However, if I put in different structures they will not be aligned. How can I overcome? Thanks

if i undertd your issue correctly..u have one KF struxture and one characteristic structure.In characteristic structure,u r having restricted characteristics and u r tyring to have a KF in char structure???if so,it is not possible..where exactly u r getting error?it will not allow you to drag and drop Kefigure into Query deisgner except into KF structure..
in char structure,if u r gng with new selection,u will not have option to select any KFs.
it could be better if u provide an example rather than explaining theoritically.
please note that u cant have a KF in characteristic structure .u can have a char in KF strcucture with a KF combination i.e. Restricted KF.
Message was edited by: Murali

What is diffrernce between key figures and characteristics?

Hi all,
I am a newbie to SAP BI....i am doing Masters in ERP(SAP)....I have confusion about what is basic difference between key figures and characteristics?
Why do we have to define attributes in characteristics?
If any one can refer me a thread that answers my questions or explain with very lucid example I will highly appreciate it.....please answer this question as I have just spend 4-5 months studying BI and have not really implemented in the Industry but we do have access to SAP BI where we perform tutorials....
Also please let me know the links to materials where basics of BI are explained in a very simple way.....
Thanks,
Regards,
Rahul

KF is anything which can quantitatively measured: Amount, Number, Value, Price... whatever you want to measure is called Key Figure. This key figures are also called KPI (Key Performance Indicator). If you want to know the number of sales orders, the number of deliveries, the amount of deliveries... all are key figures
And to add to that, key figures are also divided into two:
Cumulative KF: Like I said, amount, value, price
Non-cumulative KF, this is different kind of key figures which shouldn't be summed up, for example: Age, Inventory, Number of Employees. When you measure this key figures, you don't add the age of every body, because that doesn't make any sense, but adding the sum of all deliveries, or adding all Sales does make sense, that is the difference between the two key figures.
Characteristics: are anything which couldn't be quantitatively measured: material, customer, plant, employee ID and so on...
Aways, in BI you measure the KF against the Key figures..
thanks.
Wond

Diff between Calculated key figure and new formula 6extra functions why

Hi Friends
In BEx query designer we have Restricted key figure & Calculated key figure. In the case of Ristricted Key figure And new selection the difference is Global and local.
But if we come to Calculated Key figure and New Formula the difference is same global and local. But in New formula we have 6 extra function. My question is does is there any certain reason for this or SAP AG not be able to develop those functions
Thganks & Regards
Bramhanand

Hi Surendra thank you for your reply.
But i am not asking difference between calculated key figure and New formula.
What i am asking is in the case of Restricted Key figure And new selection the difference is Global and local.
But in Calculated Key figure and New Formula the difference is same global and local and in New formula we have 6 extra function. My question is does is there any certain reason for this.Why not SAP AG is not included the new formula functions in Calculated key figure.
Thanks & Regards
Bramhanand

What is the difference between READ TABLE ITAB WITH KEY and TABLE KEY

Hi Experts,
what is the difference between
READ TABLE <ITAB> WITH KEY <K1> = <C1>
<Kn> = <Cn> .
and
READ TABLE <ITAB> WITH TABLE KEY <K1> = <C1>
<Kn> = <Cn> .
Thanks
Akash.

Hi akashdeep,
Nice question. I also tried to find out, but no much success. My opinion is that for practical purposes there is no difference.
It may have difference in case of searching, especially sorted tables. (binary search or normal linear search).
Case1: If our table is sorted table with defined key fields, and we give WITH TABLE KEY, then faster binary search is used.
Case2 : If our table is sorted table with defined key fields, and we give WITH KEY, (and no field contained in the keys), then normal linear search is used.
regards,
amit m.

Key functional differences between SRM 7 and SRM 5

Dear All,
I urgently need to put togther a comparison document thst list key functional differences between SRM 7 and SRM 5.
NB. i donot have access to service marketplace.
sheena.roberts(AT)yahoo
Thanks
Edited by: Sheena Roberts on Jan 18, 2011 11:21 AM

Hi Sheena,
Go to difference between srm 5.0 and 7.0
Regards
Vishal Pd

Virtual Key figures and Chars

Can someone explain me what are virtual key figures and how to populate data for them.
Regards
Kunal

AHP,
Thanks for the help, one last question, i posted same on sdn week back, there was no proper response. I have standard LO datasource and enhanced with around 25 fields, the major problem is none of these fields are delta capable and they are coming from 13 diff tables, with great difficulty i could tie the relation between them. Most of the fields change and none them are picked,
is there anyway i can write a program for all this fields for delta enabling. The last option which iam left is to load the data every week as full load though data volume is less, which is not practiced.
Regards
Kunal

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

How to use a object for both key figure and as a charcteristc

Dear all,
we have a requirement where in we have to use Version Field as a key figure and as well as a charecteristc.
Regards
venu

Dear Mayank Gupta
Thxs for ur reply
We are creating a EBIDTA Report which is already developed in R/3 and these result will be stored in Z table.
we have created a DSO which will store this Z table data.
Now the req is we have a created a field called ZVersion which is there in the Key fields of DSO. ok
But in report we want to use the condition TOP1 on the version. as the version is a not a key figure we cant create the Conditon on the characteristc.
If we use version as a key figure then the records are summurised in DSO as u have to insert it in Data Field.
we want to use version as a primary key.
so how to go abt it?
regards.
venu

Definition of Non cumulative Key figure and web template

Hi all,
Can anyone define a Non cumulative Key figure and a web template.
Thanks in advance.

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.If the non-cumulatives change infrequently, you should choose non-cumulative management with non-cumulative key figures.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
for webtemplates you can info in the following
http://help.sap.com/saphelp_nw04/helpdata/en/1a/456a3badc1b315e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/b26a3b74a4fc31e10000000a114084/content.htm

Difference between Key figure and a Key field?

Similar Messages

Maybe you are looking for