Generally attribute CHANGE run is used when there is any change in the master data. it is used for realignment of the master data. Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the Sid’s so that u may not have any problem when loading the transaction data in to data targets. The detail explanation about Attribute change run. The HIERARCHY/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases:

1. Finding all AFFECTED aggregates
2. Set up all affected aggregates again and write the result in the new aggregate table.
3. Activating ATTRIBUTES and hierarchies
4. Rename the new aggregate table. When renaming, it is not possible to execute QUERIES.

In some databases, which cannot rename the indexes, the indexes are also created in this phase.

Generally attribute change run is used when there is any change in the master data. it is used for realignment of the master data. Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the Sid’s so that u may not have any problem when loading the transaction data in to data targets. The detail explanation about Attribute change run. The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases:

In some databases, which cannot rename the indexes, the indexes are also created in this phase.