Impact of Delta Records on Key Figure Summation in DSO

Hi experts,
I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
E.g.
source DSO
doc_id (key) | doc_pos | type | amount
4711 | 1 | A | 100 USD
4711 | 2 | B | 20 USD
target DSO
doc_id (key) | amount
4711 | 120 USD
If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
4711 | 1 | C | 100 USD
This will lead to incorrect amount:
target DSO
doc_id (key) | amount
4711 | 220 USD
How can I handle this situation?
Thanks in advance.
Regards,
Meng

Hi..
I believe one document number and document Item will have only one type.
Like 4711 1 should have only one type ( A / B / C).
If the above assumption is true then just remove Doc Type from Key field of source DSO.
Then From Source to Target Change Log table can handle this.
Regards
Anindya

Similar Messages

Key Figure Summation in DSO

Hi,
I am loading data from Cube to DSO.
In cube i have fields with 2 records below as example
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
In DSO all these f1's fields are key fields as per requirement. And when i load now i get in DSO as
f1=1 f2=2 f3=3 f4=4 and key figure k1=2
I do not want k1=2 but i want k1=1 in DSO and not sure why this is getting summed up even though i have selected overwrite in Transfer rules.
I have checked mapping and cube data. All are fine.
I just want to avoid this and do not know what to do.
A routine or formula or something else?
Please help.

Hi,
Check your DSO Design
Keep f1 ,f2, f3, f4, are in KeyFileds of DSO and Keep key figure k1 in DataFields of DSO.
Here I'm assuming that F1 to F4 are Charecteristics.And only K1 is Keyfigure. If this is the case then I hope it will work if you follw the above design.
Thanks
Reddy

Key figure summation for KF IN different cube of a MP

Hi,
   I need to design a report on a Multiprovider. MP is based on two Cube Cube1 and Cube2.
   Cube 1 has field item and key figure total quatity. Cube 2 has field item and key figure quatity1.
   I need a report which will show
                  Item quantity1 Total quantity   Percentage
Percentage = (quantity1/total quantity)*100.
I am surprised that percentage is X, though other two KF has value.
Is it the case that it is not possible to make summation, subtraction or any opeartion between two KF in different cube.
Could you please guide how to create percentage between two KF in different cube in a MP.
Regards
Deep

Hey Deep,
First confirm me what I understand... First you created a Mp which contains both KFs... Total quantity and Quantity one then in BEx query designer you created report in which you created a formula named "Percentage" and formula was (quantity1/totalquantity)*100... and in analyzer you are getting X instead of values. Then first try to check the properties of Formula (Percentage) in BEx query designer if decimal places etc are implemented and correct and second check if analyzer is reading these values as CHAR or Keyfigures and that you can check if there is a green arrow on left corner of each cell on both column's individual cells. If the green arrow kinda symbol is present there then it means that analyzer is not reading the values as CHAR thats why it is not doing any operation on both columns. Check these and let me know.

Key Figure Summation in Result Row with Cumulation Ticked

Hi,
I have a Bex question regarding the summation rows.
I need a Year To Date amount and a Period To Date amount in the report. However, there is no Year To Date key figure available in the cube. So in order to calculate YTD, I'm using the PTD key figure and have Cumulated box ticked mark in Bex.
All looks fine across columns per Vendor. But the results row for the Cumulative Balance is always equal to the results row for Period Balances. I believe this is because the same key figure is used, and it is only reading the amounts in the cube - not the ones calculated on the fly.
Does anyone know how to correct the results row for a cumulated key figure?
Regards,
Rhonnie

You have to create two restricted KF; one is PTD restricted to period; the second is PTD restricted in a period range from 01.yyyy to current period.
Hope it helps.
Regards

Key figure summation

Hi All
I searched SDN forums and could not find a solution for the same.
I have added a keyfigure as display attribute in 0costcenter masterdata. The same is available as display attribute in headcount cube (0papa_c02) via 0mast_cctr. Now at the reporting level, the values for the key figure is not summing up at the node level for costcenter hierarchy as a normal functionality of display attribute. It works fine for normal key figures.
So as a solution, I added this keyfigure in the headcount cube and populated the same via a routine from 0costcenter masterdata. The values are populating perfactly fine in the headcount cube. But the problem is that, as the headcount cube has multiple entries for the same costcenter, the values for the key figure is getting aggregated at the reporting level. I even tried using exception aggregation and non cumulative key figures to get the non aggregated value. But I am unable to solve this.
Could you please guide me how can I acheive this. I know I can achieve this if I use an ods. But this will affect the whole design. Plaese suggest.
Cheers
Chanda

Hi Jacob
I created one calculated key figure which contains the real key figure from the cube. When I press Ok, it will get saved. The only thing I could see is the properties of the calculated key figure/ key figure. Where I can see count all values <>0 in calculate result as.
I could not find below at the query level. Are you talking about the aggregation tab in the infoobject maintainance in BW side?
"on the next screen in bottom left corner, there is a button (I think it will say "Expand" if you log on in english). Click that one and now you get to set the aggregation behaviour. Set the exception aggregation to 'count all values 0' and the reference char to the costcenter (I think your mst. costcenter in this case)"
Cheers
Chanda

DSO - Key figure summation

Hi Experts.
I have a question on how BW is thinking when updating DSOs.
If I mark the keyfigures in the DSO to summarize, what will then be the effect.
If I compare to a SQL sentence I will sum the keyfigures for sure.
But will i Group by all the others info-object, or only the info-objects that are in the key area of the DSO.
Thank you in advance !

Husby,
In your update rule you will specify Addition or Overwrite. This will play the major role in how the data is summed up or not. Again this summarization will happen only for the key figures.
So if the keys match it will do the sum or not based on the condition set.
Hope this helps.
Alex(Arthur Samson)

Changing key figure values in DSO/Cube

Experts,
I have a DSO and a Cube and the data has been already loaded in to a amount Key Figure. By default it is 2 decimal places. I want to change the decimals to 7. I cannot delete data from the cube or the DSO.
Can you please suggest some ideas to do this.
I came accross this note 579342 which talks about realigning this but as I have not implemented this before, I wanted to get your thoughts on if this is safe to do.
Thanks
Yashu raj

Hi Yashu,
I did this with using system message board and I put message on EP tooo.
So you do a small R&D. Run this report and let me know too if amount data is reflecting in the cube or not.
Logically it should not but have a try?
Regards,
Mahesh

Difference between cumulative and non-cumulative key figures

Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

Hi.............
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:
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.
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 this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM

Statistical Progress Key Figures

Hello Community!
I had a problem with the creation of the Statistical Progress Key Figures; in order to perform the progress analysis at (PS) I need to determinate the statistical key figures in which the percentages of completion (POCs) are recorded. This settings are created per controlling area (CO). At the moment to record this key figures an error occur, that the Key figure is incorrect due that the unit of percentage is not defined correctly.
Who can help me with this matter?
What is the best way to define unit of percentage for progress analysis?
Thanks a lot!
Regards,
Manuel Gonzalez

The solution to this case was based on the Percentage Unit of Progress. This unit were created at the Tr. CUNI and regarding the ISO Unit (SAP Note 576981)
With this attributes the Key figure is configured at per Controlling Area and assigned to the Progress Analysis.
The Unit test is correct!
Regards,
Manuel GU

Info cube key figure quantity is more than the data source

Hi,
I am loading data from a custom table data source into an info cube. The data records and key figure quantity of the info cube is more than the data source custom table.
I checked the extraction in RSA3. The number of records records and key figure quantity are exactly extracted from the data source in RSA3 transaction.
But after loading using the info package, the number of records and the key figure quantity of the info cube is more than the actual records available in the data source. The update rule is simple 1 to 1 mapping.
Kindly help to troubleshoot this issue.
thanks and regards
Murugesan

Hi,
There could be some other data already avilable in the Infocube. Pls take the Request ID or Number from the last run of the Infopackage you used and check the records only for that Request ID in Infocube.
You can check the data in the LISTCUBE Transaction.
Please let me know of you need additional information.
Thanks,
Jeysraj

Key Figure values based on characteristic Drill-downs

Hello All,
I have Issue with my drilldown options in the report. The values of Sales qty need to change at particular drilldown.
I have Sales Revenue and Sales QTY key figures in my DSO with plant, factory, customer and Business type (Values A, B, C and D) characteristics.
IN the report requirement I want to show the SALES QTY for only Business Type "A" at Plant , factory and customer level, but when I am at the Business code level, then I am to show all the quantities by that level.
THe sales revenue should always show values for all Business code irrespective of the drilldowns.
please provide suggestions and code on how to go about the issue.
thanks,
pra.

Hello Guys,
Thanks for your response.
Let me explain clearly...with an example.
We have DSO which has 5 chars and 2 KFs.
Chars - Company Code, Plant, Customer, Material and Business Code (which has values A, B and T).
KFs - Sales Qty and Sales Revenue.
Report output ---
Customer
Company Code
Plant
Material
Business Code
Sales Qty and Sales Rev
Requirement is a follows -
When the report is run.... the report will display on Customer with KFs.
then if user wants to pull company code he can do so...as will other chars (Plant, Material and Business Code)
but the condition is that when the user is seeing the report at customer with KFs ,....the KFs should only show values where business code = "A"
so is the same with other chars - Company code, Plant and Material.
But when user drags and drops the Business Code char in the report against the KFs .then the report should include all Business Codes ( A, B and T) with corresponding sales qty and sales rev for all business codes.
Solution - Partially working--
What I have done..is restricted the sales qty and rev with Business code = A, its working fine for all drill downs except that, when I am at business code level its showing as
Business Code QTY REV
A             300          3000
B                0              00
T                0               00 .
Hope you got the issue. Please let me ,,if you need any information.
Thanks,
Pra

Appended Key figure is not working in Delta reverse record

Dear All,
I have enhanced 2LIS_11_VASCL datasource, to pull value from condition record, called Surchage.
I have set reversal indicator for this field in my datasource. I have written code in CMOD to get this value from KONV table of that sales order.
Now when value is changed, delta record for this, automatically creates reversal record, but it shows new value of surcharge as negative, because that code is pulling value which currently exists in table.
For example for order 350089 , if surchage is $ 100 . User changes it to $200
Then I get following record.
Reversal Record - $200 (This should be instead -$100 , i.e. previous value)
New Record - $100.
Because of this my new value is not getting updated in table.
I can't use overwrite mode in ODS because some other technical reason.
How can I solve this problem?
appended Key figure is not working in Delta reverse record

LIS have before-after delta. So ODS should be in Overwrite mode. If that is not possible.. try sorting the records in Start Routine such way that the - 100 $ is above the - 200 $ records in Data Package.
but this is risky as it will affect other key figures for which things maybe fine. I guess you need take Data Package records in an internal table. And then sort this internal table. then you can read the internal table in update routine of this key figure.
OR (If you are on BI 7.0) you introduce an InfoSource in between DS and DSO with Overwrite mode for this Key Figure.

Key Figure's Result Summation and SUMGT

Goal: I need to capture the reports Results for KF1 and KF2 to use it in the same report for further calculations. However, the report should include into Results calculations only the records that have KF1 or KF2 with values greater than 0.
Potential Solution: Create a Formula that uses Function SUMGT (or SUMCT, SUMRT) on the desired key figures and use conditions at the query level.
KF1 Property:     Calculate Result As SUMMATION
KF2 Property:     Calculate Result As SUMMATION
Report with No Conditions:
Year      KF1     SUMGTKF1     KF2     SUMGTKF2
2001     10        70                         10        90
2002     20        70                         20        90
2003     0          70                         30        90
2004     40        70                         30        90
Result   70        70                         90        90
Report with Conditions:
KF1 > 0
or
KF2 > 0
Year     KF1     SUMGTKF1     KF2     SUMGTKF2
2001    10         70                        10         90
2002    20         70                        20         90
2004    40         70                        30         90
Result 70         70                        60         90
Problem: When Conditions apply the SUMGT (as well as SUMCT and SUMRT) do not take them into consideration and includes in its calculations the excluded records as well.
Questions:
1. How can I make SUMGT (or any of the other tow) return a result that take into consideration the specified conditions? For KF2 the Result should be 60 and NOT 90.
2. Is there any other way I can capture the Results for KF1 and KF2 when the above specified conditions are implemented?

I think No of repair days is a characteristic..
What you can do is create a formula variable with user input. User will enter no of repair days in it.
Now create a variable on no of repair days of type customer exit.
In the exit read the value of the formula variable and assign it to that variable.
Restrict your key figure no of completed orders with that variable...

How to identify which key figure will the numeric pointer for deltas?

Hi All,
I have created a numeric pointer for generic extraction ? but how to identify which key figure will the numeric pointer will use for deltas ?
how to identify the key figures which is suitable for numeric pointer. And the generic extraction is based upon the copa table?
Can anyone suggest me how the numeric pointer works and how to identify deltas are carried out at numeric pointer?
Thanks
Pooja

Pooja,
If you are using a generic extractor which is based on COPA table, then numeric pointer may not be the suggested delta extraction mechanism.
A time stamp would be the better one to use. In a time stamp, you can give a lower limit value of 300 seconds.. so that it will try to fetch the missed records.
Moreover, a delta would be based on a character, preferably a time char.
In your requirement, try to figure out the character on whichdeltas will be based.
Sasi

Key figures should be normally "summation" or "overwrite"

Hi all,
I know the answer to this question is "it depends on your requirement" but I want to know normally do we have to keep the key figures as summation or overwrite ?
Thanks,
KM

Hi:
Summation.
Since most reports need a summation, keep the K-Figures as summation.
If you want overwrite, you can use an ODS. Here, even though the K-Figure is summation, you can still overwrite by Modeling.
Ram C.
Message was edited by: Ram Chamarthy

Impact of Delta Records on Key Figure Summation in DSO

Similar Messages

Maybe you are looking for