Question:
Hello
I have an issue where I have troubles when using and loading to a key figure set for aggregation maximum. (I defined it so when I created the key figure.)
The case seems to be that aggregation doesn't work in the same way as addition does and every value from the source gets posted to the cube _without_ aggregation. I'm wondering it I've forgotten something or if this is the way it works.
I'll illustrate the scenario. I'm loading from an ODS to a Cube where the ODS contains daily data and the cube should contain monthly aggregated data.
ODS :
Depending on the aggregation type you entered in the Key Figure Maintenance for this key figure, you are given the options Addition or Maximum or Minimum. If you choose one of these options, new values are updated in the InfoCube.
The aggregation type (addition, minimum & maximum) determines how key figures are updated where primary keys are the same. Thus the total, the minimum or the maximum for these values is formed for new values.
If you entered one of these aggregation types in the key figure definition, it is transferred for the update. Otherwise, the aggregation type addition is automatically selected.
The primary keys are the same but I can't get the update to cube to work as described above.
Any idea?
Answer:
But your counter is set to addition, right? So you get a max on the date and you add up the counters... Is the counter always 1 in the ODS?
_________________
Eric
Answer:
Hmm.. Give me a thought.
I've added counter manually by myself and I populate it with 1 in the update rules.
I could ofc try to remove the counter in the ODS and add that in the cube instead. 0rowcount is in the ODS afterall....
Answer:
Can't get this to work well at all. To me it seems that the update program writes duplicate rows to the fact table.
ODS :
Day ; Item-ID ; Days overdue(key fig.) ; Counter(key fig.);
2006-02-01 ; AA ; 5 ; 1
2006-02-02 ; AA ; 6 ; 1
2006-02-03 ; AA ; 7 ; 1
2006-02-04 ; AA ; 8 ; 1
Cube (fact table):
Month ; Item-ID ; Max. overdue(key fig.); Counter(key fig.);Request
2006-02 ; AA ; 5 ; 1;Req1
2006-02 ; AA ; 6 ; 1;Req1 <----?????
2006-02 ; AA ; 7 ; 1;Req1 <----?????
2006-02 ; AA ; 8 ; 1;Req1 <----?????
Can anyone answer why I get 4 rows in the F fact table instead of one??