attribute change run performance optimization and forceful completion

8/11/2019 Attribute Change Run Performance Optimization and Forceful Completion

1/12


2/12

Attribute Change Run (ACR) Performance Optimization and Forceful Completion

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX -bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 2

Table of Contents

Attribute Change Run (ACR) - Optimization ....................................................................................................... 3

Configuration ................................................................................................................................................... 3

Steps to Overcome Long ACR run: .................................................................................................................... 4

Points to Consider: ........................................................................................................................................... 10

Related Content ................................................................................................................................................ 11

Disclaimer and Liability Notice .......................................................................................................................... 12


3/12



2010 SAP AG 3

Attribute Change Run (ACR) - Optimization

Attribute change run is the process in BW wherein the master data get activated (whatever has beenrecently loaded) and adjusted in the aggregates. This process plays vital role in our day to day batchprocesses because ACR process takes maximum time in batch processing in most of theimplementations.

This document dictates the process/configuration changes of how to control timings of ACR runs andalso how to handle the situation wherein the ACR got stucked.

Configuration

ACR has a threshold value, which takes the decision of aggregates jobs either to rebuilt or to fill upwith delta process (Old records get updated negatively and new records get updated positively). Thisdecision depends upon the percentage of changes. If percentage of changes is equal or less thenthis value (Limit with Delta) then aggregate will be rolled up and if the percentage of master datachanges are more then threshold value then aggregates will be rebuilt. Below transaction to analyis/change Aggregates threshold is RSCUSTV8.

As per the system response one can increase this delta limit till you get minimum timings on ACRprocess. This depends upon system to system but ideal limit is 20.

Block size is use to prevent overflow of temporary tablespace i.e. PSATEMP. This is used if E table or Ftable of Infocube is larger then the Blocksize then source to update aggregates will not be read at oncerather divided into blocks.

Ideal size of blocksize is 999999999.


4/12



2010 SAP AG 4

Steps to Overcome Long ACR run:

Below steps dictates how to overcome and resolve situation wherein you figure out that in Batch processACR is running from long and doing nothing or stucked somewhere. I called below process forcefullyACR completion.

In normal scenarios we came across various situations wherein ACR is kept on running and there is noalternative rather then wait and watch.

To overcome these situations Ive one workaround. This workaround comprises of following steps:1. First Make sure youreACR got stuck

2. Identify the aggregate.

3. Kill ACR Job

4. Deactivate the aggregate manually

5. Restart failed ACR

6. Wait for ACR to finish

7. Activate deactivated aggregate

Details:

First Make sure youre ACR got stuck- Normally we get an idea by analyzing the statistics ofaggregates rebuild time.

For Example: If ACR got Stuck on one of the aggregate and that aggregate ACR had already spent 6hrs on that particular aggregate and you know normal filling (rebuilt) of this aggregate from scratchwont take more then 3 hrs then you would be in problem.

Identify the aggregate:Aggregate name can be found on ACR Monitor, to get to ACR Monitor useABAP report RSDDS_CHANGERUN_MONITOR and execute this in SE38.

Below Details is for ACR when it is not Running (this is just to explain details)


5/12



2010 SAP AG 5

After execution of report this will display following screen with summary of changes in ACR.

The above screen will show you summary not details so number of actual aggregates affected,characteristics and number of changes can only be seen after clicking details button.


6/12



2010 SAP AG 6

After Clicking Details Button, It is clear that only one aggregate is affected, not 8 and it also displaysthe details of changes.

Further Drill down will display cube, aggregate name and the process for adjustment adapted byaggregate. Below adjustment has been adapted by delta as shown in screen shot.


7/12



2010 SAP AG 7

Kill ACR Job

Select the required job in SM66 and kill without core.

Deactivate Aggregate Manually

As per the details of aggregate analysis screen traverse to the cube and the aggregate, deactivatethe same.

Restart Failed ACR

Use programme,to get to ACR Monitor use ABAP report RSDDS_CHANGERUN_MONITOR andexecute this in SE38, restart failed ACR.

To Restart Change run Press Highlighted Execute Button:

Note: incase of failed ACR instead of green light youll find Red light on left side of screen. This below screen is for non-failed ACR. But Start button will remains the same.


8/12



2010 SAP AG 8

Wait for ACR to finish

Once change run is done it will show you blank screen as shown below:


9/12



2010 SAP AG 9

Deactivate Aggregate Manually

Select the aggregate again and activate the same.

Once activated start filling job of aggregate.

Once this is done you are again on to the same stage (as if this could have been done by ACR job)by making forcefully ACR to finish early.


10/12



2010 SAP AG 10

Points to Consider:

1. This method is used to handle situation wherein Batch process got stucked on ACR job andthere is no other option left.

2. Make sure ACR job Ran successfully once you restarted.

3. This can be done on various aggregates; itspossible that ACR job might get stucked on 2 ormore aggregates.

4. Pls use precaution and common sense before executing this procedure because some time costof rebuilding aggregate is heavy in terms of time it takes to rebuild.


11/12



2010 SAP AG 11

Related Content

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e7deb490-0201-0010-f882-ef40f8c9bb5c

http://wiki.sdn.sap.com/wiki/display/BI/Aggregates+Performance

http://wiki.sdn.sap.com/wiki/display/BI/Attribute+Change+Run++concepts
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e7deb490-0201-0010-f882-ef40f8c9bb5chttp://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e7deb490-0201-0010-f882-ef40f8c9bb5chttp://wiki.sdn.sap.com/wiki/display/BI/Aggregates+Performancehttp://wiki.sdn.sap.com/wiki/display/BI/Aggregates+Performancehttp://wiki.sdn.sap.com/wiki/display/BI/Attribute+Change+Run++conceptshttp://wiki.sdn.sap.com/wiki/display/BI/Attribute+Change+Run++conceptshttp://wiki.sdn.sap.com/wiki/display/BI/Attribute+Change+Run++conceptshttp://wiki.sdn.sap.com/wiki/display/BI/Aggregates+Performancehttp://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e7deb490-0201-0010-f882-ef40f8c9bb5c


12/12



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

attribute change run performance optimization and forceful completion

Documents