on 07-29-2005 9:39 AM
Hi,
I've the following data in the cube
<b>Material Period Unit Cost</b>
1 01.2004 10
1 02.2004 10
1 03.2004 10
The 'Unit Cost' keyfigure has the standard and exception aggregation as 'Summation'.
As a result, when I a build a query on this cube using 'Material' in the rows
and 'Unit Cost' in the columns, I get the following result
<b>Material Unit Cost</b>
1 30
which is incorrect and we would want the result to look like
<b>Material Unit Cost</b>
1 10
Could some one please suggest how can I achieve the correct result
with minimal changes, so that i don't have to change the data model
(ie. Change the standard and exception aggregation to 'Maximum' or
'Minimum' in RSD1 for 'Unit Cost')
I have already tried changing the keyfigure properties 'Calculate Result As'
and 'Calculate Single Values As' in BEx with out success.
Please suggest.
Best Regards,
Sanjay
What you will not like is what you need to do
I would think unit cost shall have its place in master data (attribute of material), but then that is my opinion.
cheers,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ajay,
you mentioned that unit cost can be or should be placed as a master data attribute of material. But then, how can i use this for computation ?
I think this is a limitation if the keyfigure is used as an master data attribute, if not please let me know if you have any other suggestion.
Regards,
Sanjay
Hi Sanjay,
This scenario is mentioned in the how-to paper 'how to calculate with attributes', it is available on SDN.
Basically you need to define a formula variable of processing type 'replacement' which will get the value from the characteristic (material)'s attribute (price). This can be used in further calculated key figures.
cheers,
Message was edited by: Ajay Das
Sanjay,
Use can use exception aggregation. Create one key figure as count of records and one as a sum of the unit cost column. Divide in the query.
Only issue with the above - you will need something in the data that identifies each record uniquely. Secondly, if the unit cost is different across records, then it will get averaged out.
Ideally, you should not put unit costs in the infocube as a key figure - put in the result, i.e. quantity and value and calculate the unit cost.
Cheers
Aneesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Aneesh,
the unit cost can vary over time and hence an average is not desirable. Yes, you are right , unit cost should ideally have been part of the master data, but unfortunately it has been made part of the cube. And thats why i was trying to look for a economical solution, but looks like having it in the cube could cause wrong results.
Best Regards,
Sanjay
Hi Sanjay,
You can try changing the Infoobject aggregation proerties to anything other than summation like Max/Min/Avg. That wil work. If the Query lvl change doesn't work. this is the only way I guess.
(well.. quite a few edits as ur msg was constantly changing
Regards,
Sree
Message was edited by: Sree Damodararaj
Message was edited by: Sree Damodararaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sree/Ajay,
I've tried changing the Infoobject aggregation proerties as i've mentioned above, but it doesn't seem to work or may its purpose is different from what I want to acheive.
Ajay,
yes we can have it as a master data attribute, but then again, this would require a change to the exiting model
Best Regards,
Sanjay
User | Count |
---|---|
85 | |
10 | |
9 | |
9 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.