Attribute/Hierarchy change run

[Former Member]

Hello experts,

i've several navigational attributes in my aggregates.

Does the change run automatically adjust the aggregates ?

or

Should the following be done :-

1> Deactivate the aggregates

2> Execute the change run

3> Activate and fill the aggregates again

If attrubute change run alone is sufficient, then are there any cases when i need to perform all the three steps mentioned above

Best Regards,

Sanjay

[Former Member]

Hmm, time dependant attributes. Well I havent used them in aggregates as you can only have one key date in the aggregate. As far as I know the change run is for changes in masterdata where as the change of the keydate is something else. I really don't know if a change run will change aggregates build on time dependant attributes! But try it out!

Regards

Kristian

[Former Member]

Thanks kristian. I'll test if this has to do with time-dependent navigational attributes.

Regards,

Sanjay

[Former Member]

Hi

Let me clarify

The change run will change the existing aggregates when masterdata has been updated. Loading new data into the cube does not require a change run only a roll-up of the aggregates. I.e. the process you describe should never be nessecary.

regards

Kristian

[Former Member]

Hi Kristian,

thanks for your response. Could there be a case that steps mentioned above might have to be performed when time-dependent navigational attributes are used in the aggregates ?

Thanks again,

Sanjay

[Former Member]

Hello Sanjay,

If the key date of the aggregate change, you have to fill the whole aggregate again, after chnaging the key date.

If the key do not change the attribute change run will adjust the aggregate. The system decides on the percentage of the amount of the changed data if the aggregate will be refilled or adjusted.

To use time dep. Nav Attributes is very very rare and is often not needed.

May can I ask why are you using time dep. nav attributes and not the historical truth?

Kind reg.

Michael

[Former Member]

Thanks for your response Michael that clarifies my query.

As for your question on "why are you using time dep. nav attributes and not the historical truth?" - the attribute has not been used as an characteristic in our cubes and its too much of an effort now to go back and add them as characteristic in the cube. And hence we have to report on time dependent navigational attributes :(.

Regards,

Sanjay

[Former Member]

Hi Sanjay,

You need to perform the above steps whenever the cube is loaded with new data.