You are on page 1of 4

Different ways to run Attribute Change Run(ACR) in SAP BI

Sometimes due to some issue or user requirement we will do master data loading apart from daily loading. After master data loading is done, the first doubt we get is do I need to run ACR or Activating master data is enough. What is ACR? : We need to run ACR when you have aggregates which are using your characteristics. ACR will update newly added/changed master data to aggregates and activates the master data in characteristic. What is Activate master data? : Activate master data activates the newly or changed master data(which is in M version), but it will not update the same to aggregates. So ACR is required if you have aggregates which are suing these characteristics. Generally in Projects this ACR will be done as part of Process chain after master data loading is done. How can we run ACR for one characteristic or multiple individually. This can be done in 2 ways. First: 1) Goto RSA1 2) In menu bar, click on Tools --> Apply Hierarchy/Attribute Change.

3) In the next screen, click on "Info Objects" list. You will get the list of characteristics for which ACR is required. By default all the characteristics will be selected, unselect the characteristics for which you don't want to run ACR. Note: If you don't get your info object here, then ACR is not required for this characteristic.

4) Now click on execute, you can monitor the job in SM37. Second: 1) Go to SE38, give the program RSDDS_AGGREGATES_MAINTAIN and click on execute.

2) In the next screen enter the characteristics for which you want to run ACR and execute.This will be done as fore ground. Note: If you want to run this as back ground job, then in menu bar --> program --> execute in back ground.

Attributes Change Run - applying changes in aggregates Basics of Attribute Change Run Attributes Change Run applies changes into aggregates if there was a change in navigation attributes used in aggregates or in hierarchies of a characteristic. This process is necessary, because in aggregates data from InfoCube are persistently stored in aggregated form (In InfoCube, no data related to navigation attributes or hierarchies are stored). To start Attributes Change Run, go to RSA1, use menu Tools>Hierarchy/Attribute Changes. You will see there a list of available sets of InfoObjects and appropriate change status. If you mark a line, and click InfoObject List button, you will see a list of objects that are planned for that Change Run. The second important button is Execute button. Use it when you already market the line, for which you would like to start Attribute Change Run. Change Run process steps 1. Change Run checks which characteristics and hierarchies had changes since the last change run. Run specifies which aggregates must be adjusted. 2. Change Run apply changes (dialog process for each required InfoCubes' aggregates). 3. Activation of changes in master data and hierarchies. There is a SAP lock, which (during point 1) is preventing other changes runs to start a job for the same time. Also rollups and aggregate builds are not executed. The name of the lock: CHNGRUN_ST The second SAP lock (CHANGERUN) is locking objects (InfoObjects, InfoCubes, hierarchies) that are involved in the adjustment (point 2). When the work is finished, the CHANGERUN lock is removed. There could be only one change run in the initial phase (1). If other change run starts, it will fail immediately. It is not possible to start multiple change runs. Read about parallel change run in SAP Note 534630. Additional Notes: Change Run process can be monitored, restarted using RSDDS_CHANGERUN_MONITOR ABAP report. You can start it using se38 transaction. It is better to run CHR for all newly loaded master data in the process chain. Do not start it for each master data load.

You might also like