<b>Attribute Change Run:</b>
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 trasaction data in to data targets. It is used for realignment of the master data..
Whenever master data attributes or hierarchy is loaded an attribute chnage run need to be performd due to the following reasons:
1. When a master data is changed/updated it gets loaded into the master data table as version “M”(modified). It is only after a attribute chnage run that the master data becomes activated i.e. version “A”.
2. Master data attributes and hierachies are used in cube aggregates also. So to do update the latest master data attributes values in the aggregtes attribute change run need to be performed.
You need to schedule an attribute change run when you change master data attributes or hierarchies that are used as navigational attributes or in aggregates. There is a simple test to check if you need an aggregate change run. Load your attributes and look into the master data table (directly via SE16). If you only have entries with OBJVERS = ‘A’ (active) then you don’t need a change run. If you have entries with OBJVERS = ‘I’ then you need to schedule a change run after upload.
When ever your master data changes , you can have a full or delta load .
The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is devided, 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.