Definition :
Attribute change run is nothing but adjusting the master data after it has been loaded from time to time so that it can change or generate or adjust the SID's so that you may not have any problem when loading the transaction data into data targets.
whenever master data attributes(navigational) or hierarchy is loaded an attribute change run need to be performed due to following reasons.
Attribute change run is nothing but adjusting the master data after it has been loaded from time to time so that it can change or generate or adjust the SID's so that you may not have any problem when loading the transaction data into data targets.
whenever master data attributes(navigational) or hierarchy is loaded an attribute change run need to be performed due to following reasons.
- When a master data is changed/updated it is loaded into master data table as version 'M'.It is only after attribute change run that the master data becomes activated i.e version 'A'.
- Master data attributes and hierarchies are used in cube aggregates also.
- Attribute change run need to be performed to do update the latest master data attribute(navigational) values in the aggregates.
- We need to schedule the attribute change run when you change the master data attributes and hierarchies that are used as navigational attributes.
When you 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 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.
Attribute/Hierarchy realignment run t-code : RSATTR.
Note : Only one attribute change run can at one point of time means if one attribute change run is running in system from any process chain or for any project the second one fails.Due to this reason data load fails..
The solution for is shift the attribute change run from info package level to global level or process chain level in order of priority.Instead of keeping ACR at after each infopackage update we can accumulate all in one ACR at end of process chain or in a seperate chain.
No comments:
Post a Comment