Documente Academic
Documente Profesional
Documente Cultură
Products
Products Industries
Industries Services and Support
Services Support Training
Training Community
Community Developer
Developer
Partner
Partner About
About
Ask a Question Write a Blog Post Login
Former Member
March 30, 2009 9 minute read
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 1/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
To activate new master data, a change run must be performed, even though the attribute or hierarchy is not
used in any aggregate.
Note :
1) Go to RSA1 >> Right click on the infoobject >> Activate Master data. But this method is only possible if no
Aggregates are existing.
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 2/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
New master data is available for reporting only if the change run has nished successfully.
If changes are made to attributes or hierarchies from characteristics used in aggregates, the structure of
the aggregates also needs to be changed. Generates all aggregates that are a ected (in all InfoCubes) with a
new change ID (CNSID). This ensures that queries that access to the InfoCube or assigned aggregates are
consistent.
Activates all hierarchies and attributes (updates the data records).
Sets the pointers to the right change ID, so that reporting can use the new structures and the modi ed
aggregates.
For InfoCubes containing key gures with aggregation MIN/MAX, the only way to adapt the aggregates in a
changerun is rebuilding them.
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 3/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
Look into the following gure………………..The value ‘Limit with Delta’ determines the percentage of master data
changes at which the delta mode is to be switched to reconstruction. Aggregates are not completely rebuilt if
the percentage of changes is below a certain threshold. This value can be changed.
SPRO >> SAP Reference IMG >> SAP Customizing Implementation Guide >> SAP NetWeaver >> Business
Intelligence >> Performance Settings >> Parameters for Aggregates. (Tcode : RSCUSTV8)
Block Size : This parameter use to determine the block size when building aggregates. If the E or F table of the
source for the aggregate structure is larger than the BLOCKSIZE parameter in table RSADMINC, the source is
not all read at once, but is divided into blocks. This prevents an over ow of the temporary table space
PSAPTEMP. A characteristic whose value range is divided into intervals is used to divide the source into blocks.
Data from the source is read from these intervals only and is then written to the aggregate.
There is no recommended size for the BLOCKSIZE, since the various databases that the BI system supports
di er signi cantly.
If no value is maintained for the BLOCKSIZE parameter in Customizing (activity in IMG: Parameters for
Aggregates), or if the value is 0, the BI default value of 100,000,000 is used
Wait Time: An immediate Change Run start may not be possible because other processes hold necessary
locks (e.g Master Data Loading, Roll Up, …)
The Wait Time speci es the time in minutes how long a Change Runs waits before terminating.
Or, Go to RSA1 >> Tools >> Apply Hierarchy/Attribute Change …>> there click on Parallelism and set “Number
of Processes”
The Change Run combines di erent steps which are processed sequentially
Each of the steps is restricted by the maximum number of parallel jobs (N) chosen in Change Run
Customizing
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 4/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
If an Attribute change run is run using a Process Chain, then the Job name will be BI_PROCESS_ATTRIBCHAN.
In NetWeaver 2004 all the Child Jobs of the main Job run in Background. We can monitor these Jobs in SM37.
Sequence of these Childs jobs are as follows :
RSA1 >> Tools à Apply Hierarchy/Attribute Change …>> there you will get the Tab “Monitor and Start
Terminated Change Run”.
RSA1 >> Tools à Apply Hierarchy/Attribute Change …>> Select the required Change run and click on the
“Log” Tab.
If a Change Run is executed through RSA1, then the Job name will be BI_STRU*.
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 5/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
For this……Go to RSA1 >> Tools à Apply Hierarchy/Attribute Change …>> Here from the Infoobject List
select the desired infoobjects for which you want to run the Change run >> Then click on Execute.
You can access the same screen through……..RSA1 >> Administration >> Change Run.
We can also execute the Change Run using the Program : RSDDS_AGGREGATES_MAINTAIN, there enter
the list of Infoobjects à In the top “Program” Tab à Execute in Background.Always execute in background,
bcoz then only you will be able to monitor the Job using SM37.If you just press F8 and execute the Change
run, then you will not be able to trace the Job.In this case the Job name will be
RSDDS_AGGREGATES_MAINTAIN.
When the Change Run starts a global SAP enqueue lock is set.
This global lock is hold just for a short time until the a ected
infocubes are identi ed. This global enqueue lock doesn’t allow
Step 2:
After the global lock was removed just a smaller enqueue lock is set. It locks just the a ected Infoobjects and
the InfoCubes where the infoobject is used. Furthermore some activities are not allowed during the Change Run
works
master data loads to the a ected InfoObjects, but master dataload to other InfoObjects
rollup for InfoCubes having aggregates a ected by the Change Run
Major problem with Attribute Change Run is that In any SAP System only One attribute change run can run at
one point of time. i.e. If one attribute change run is running in system from any process chain or for any project
and 2nd one fails, if start at same time due to locking problem. Due to this entire data load fails.( In NetWeaver
2004 two or more Change Runs in WORK-Phase can run in parallel , provided if the Change Runs process
di erent objects )
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 6/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
Solution :
1. Shift Change runs from info package level to global level and/or process chain level in order of priority. Means
instead of keeping ACR after each infopackage update we can accumulate all in one ACR at end of Process
Chain or in a separate chain, if this data is not dependent for next loads(means no look ups).
Above option is helpful When the running CR is in the work phase , only then will a second CR enter the start
phase and wait as long as speci ed in CR_MAXWAIT. And when the second CR is in the startphase, all other CRs
trying to start will again immediately fail.
For more info : SAP Note : Note 825927 – The BW Changerun: CR_MAXWAIT .This is not 100% solution.
3. Created an ABAP Program and included before each Attribute Change Run in Process Chains. This Program
checks if any ACR running in the system or not. If any ACR is running it delays 10 Secs. Recursively it checks
and delays 10 secs every time. Program execution nishes only when there is not ACR running in the system
and allows next process(Attribute Change Run) to trigger in Process Chain. After implementation of this
program no ACR failures in our system. Check the coding at end of this blog in appendix.
How to implement:
Step2: Include this ABAP program in Process Chains between infopackage and Attribute Change runs as shown
in the screenshot.
Step3: Goto Process Chain(TCode: RSPC) and choose perticular process chain, then goto processes and
choose ABAP program provide technical name and description. Provide created ABAP program and Variant
save and activate Process Chain.
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 7/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
If you assign the process type Attribute Change run to a process chain, you must de ne a variant. With this
variant, you have to de ne the InfoObjects for which you want to activate the master data. There are four
di erent possibilities:
Note :
Instead of applying the InfoObjects or hierarchies directly to the process variant in RSPC you can create a
central variant for the report RSDDS_AGGREGATES_MAINTAIN. You can assign InfoObjects and hierarchies to
this report variant. This central variant could be used by several process variants in RSPC. The bene ts are
central maintenance. Using a reference object like LOADING or REPORTVARIANT is sometimes more exible.
We should not cancel any Change run.Because if we manually cancel any change run,lock will never get
released, until we repeat the terminated Change run(Change Run id should be same).
Also when a Change Run get cancelled automatically ,we should check the Job Log. If it is a Terminated Change
Run, then again we should repeat the Terminated Change Run, then only lock will get Released.
For this……
Go to RSA1 >> In the top TOOLS tab >> Select Apply Hierarchy/Attribute Change >> Click on Monitor and
Start terminated Change run >> there click on Start Change run with Set Filters………it will restart the
Terminated Change run…..
Alert Moderator
We can also use the Program : RSDDS_CHANGERUN_MONITOR
Assigned tags
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 8/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
Related Questions
4 Comments
Former Member
Like (0)
Former Member
Like (0)
Craig Armstead
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 9/10
3/21/2019 Attribute Change Run (ACR) | SAP Blogs
Like (0)
Former Member
Thanks,A
ADKR
Like (0)
Sitemap Newsletter
https://blogs.sap.com/2009/03/30/attribute-change-run-acr/ 10/10