Attribute Change Run

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. It is used for realignment of the master data..

Whenever master data attributes or hierarchy is loaded an attribute change run need to be performed 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 change run that the master data becomes activated i.e. version "A".

2. Master data attributes and hierarchies are used in cube aggregates also. So to do update the

latest master data attributes values in the aggregates 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.

The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases:

Finding all affected aggregates.

set up all affected aggregates again and write the result in the new aggregate table.
Activating attributes and hierarchies
rename the new aggregate table. When renaming, it is not possible to execute queries.

T code RSATTR

Program : RSDDS_ATTR_CHANGERUN

RSDDS_CHANGERUN_MONITOR To monitor change run

In any SAP system Only one Attribute change Run can Run at a given Point.


check the following link for more information
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17435