Attribute Change Run

SAP BW Hierarchy Attribute Change Run ManagementApplies to: SAP NW2004s (BI 7.0) SAP NW2004 (BW 3.5). For more information, visit the EDW homepage. Summary This article explains a. the importance of HACR and its maintenance, b. focuses how to prevent HACR failures by discipline and also c. provides scenario based expert solution if there is HACR failure. Author: Kannan Natarajan Company: IBM India Pvt. LTD. Created on: 01 July 2010 Author Bio Kannan is a certified BI 7.0 consultant with 5 years experience in SAP BW presently. He has rich experience in both production support and implementation project. He is a SAP BW developer working in IBM for Shell client. He held responsibility of Job failure analyst in his production support project. SAP COMMUNITY NETWORK © 2010 SAP AG SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1 ............................................... .......................boc........................................... ...bpx.............. 5 3.............................. 4 3....................2 Activating Parallel processing in HACR .com | BOC . 6 3....................... How to get rid of HACR clashes ...............................................................2 Rescheduling Process chains ........ 6 3.............................................................................................................................sap.............................................................. 7 Scenario 2: Bypassing a terminated change run.........................com | BPX ....com | UAC ..............sap................... ...............................1................................... 6 3.....................1.......................................................................................................sap.............................................................................. 4 3.....................sap................................................ 3 2........................ What is HACR? .............................. 7 4..................................... Do and don’t when HACR job fails ............... 8 Scenario 3: Infoobject not released................. 6 3...............................SAP BW Hierarchy Attribute Change Run Management Table of Contents Overview......................................................................... 8 Related Content ......... ....3..........3........................................................................................................................................................................................ Delete/deactivate aggregates that are not used frequently.................................................................................... 7 Scenario 1: The basic....................... 10 SAP COMMUNITY NETWORK © 2010 SAP AG SDN ...............................................................................................................uac.................................................................................................. Find aggregates with less summarization value............. less usage..........................................................................................2................... 4 3.....3..1 Making Delta Setting and Activating Parallel processing in HACR ... Different failures that may raise due to HACR ...................... ..........................com 2 ........................... 8 Myth regarding HACR recovery .......................................1..................... 9 Disclaimer and Liability Notice ...sdn........................................................................................................................................................ ...........................1 Making Delta Setting .................................. 4 3............ Delete unused Aggregate....................3..3 Maintaining Aggregate .................. 3 1...... The aggregates build using the navigational attribute (material group) should be also adjusted accordingly. Importance of HACR.sdn.com | BOC . The different failures. After Material 1004’s Group Changes from A to B in Material Master data and activation of master data.com | BPX .com | UAC . SAP COMMUNITY NETWORK © 2010 SAP AG SDN .sap.1. master data is loaded from R3 to BW. the reports will still reporting on old master data. What is HACR? We all know the main advantage of SAP BI/BW is it’s extended star schema.sap. all data targets share the same master data table (say Material) instead of duplicating it. The value in aggregate is wrong now and the report will be showing this value. handling daily failure is the primary task. In extended star Schema. HACR issue is a major hurdle in handling daily job failures. Master data has attributes.bpx.SAP BW Hierarchy Attribute Change Run Management Overview In SAP BI support projects. After this change. Do and don’t when HACR job fails 1. A Material – 1004 may change from Material group A to B. In our example ‘Material group’ is an attribute of ‘Material’. which are slow changing.sap. Which gives completely different picture to present business.boc. In brief. 1. Fig 1. Not doing Hierarchy attribute change run (HACR). Imagine if this report is used for making critical business decision!!!!! For this reason HACR is a must after a master data load. which may arise during HACR. Just activating these master data is not enough to report with changed master data.com 3 . How to get rid of HACR clashes? 4.0. (If there is change in navigational attribute or hierarchy involved) Fig 1.sap.uac. due to new business strategy. 2. 3. The Cube and aggregate looks like below when Material 1004 is in-group A. 1.sap. With changes beyond a certain magnitude.2 Rescheduling Process chains 3.com | BOC . 2.1 Making Delta Setting and Activating Parallel processing in HACR 3.sap.sap. While HACR realigns an Aggregate.bpx.2.1 Making Delta Setting If hierarchies and attributes of characteristics belonging to an InfoCube have been changed. You can change this threshold value (0-99) SAP COMMUNITY NETWORK © 2010 SAP AG SDN . it is necessary to make structural changes to the aggregates in order to modify the data accordingly. From the above types of failure you can see that HACR failure causes a chain reaction of failures.sap.com | BPX . which can take the system into toss if not managed/ taken action promptly.sdn.uac.boc.SAP BW Hierarchy Attribute Change Run Management Fig 1. the load time increases as both are accessing the same table. any other HACR starting in that span would fail. Our HACR program helps here by getting the values in aggregates corrected* (Check 3.1 Making Delta Setting and Activating Parallel processing in HACR 3.com 4 . If a HACR fails other than Lock issue. Different failures that may raise due to HACR     When a HACR takes a long time. So there is very chance of Data Package hanging and short dumps.1 for details how aggregate is corrected). 3. if rollup step runs for that cube. The rollup will fail. If HACR and any transaction Load containing respective master data run in Parallel. How to get rid of HACR clashes 3. re-aligning the aggregate becomes more time consuming than reconstructing it.3 Maintaining Aggregate 3. After running this only HACR other HACR can be ran.com | UAC .1. com | BOC .Even if there is no change in the navigation attribute the system does reconstruction always. I.bpx. SAP COMMUNITY NETWORK © 2010 SAP AG SDN . Please go through the SAP note 1388570 for more detail. else the system goes for reconstruction..com | UAC .1. 3. The aggregates of the same cube can be realigned in Parallel. The program goes to each required Cube and re-aligns all the required Aggregates of the Cube.2 Activating Parallel processing in HACR During a HACR.3. 3.sap.1. When delta limit is set to 99 – Even if there is 99% change in the navigation attribute the system does a delta. The value 20 can be changed to get better performance. So as optimum generally the value is set to 20.sap.0. system takes maximum time to correct the aggregate.uac. In both the above cases. The number of parallel processes can be customized in Process chain variant or with transaction RSBATCH in BI 7.com 5 . Snap shot of Transaction RSCUSTV8.2. When Delta limit is set to zero . Which means if the change is less than equal to 20% a delta correction is done in the aggregate.e. Delta Setting is done in RSCUSTV8 Transaction.com | BPX .boc. 0 means that the aggregate is always reconstructed and 99 means that the aggregate is always re-aligned. Snap shot of transaction RSBATCH.sap. Fig.SAP BW Hierarchy Attribute Change Run Management Fig.sdn.sap. com | BPX .If 3 HACR processes are running in 3 different PCs. Following which transaction data shall be loaded. E. Again lock is set 3 times in the system but this time only for a span of 15 mins.3 Maintaining Aggregate Objective is to reduce the no. Delete/deactivate aggregates that are not used frequently.boc. 1:30 AM and 2:00 AM. You shall deactivate the aggregate. 3.3. The report might have been deleted.2 Rescheduling Process chains In Process chains for Masterdata loads. Aggregate maintenance is an activity to be performed at least once in 3 months. also check the ‘last changed date’ (TIMESTMP) of the aggregate before deleting it. 3.3.3 Find aggregates with less summarization value. Delete unused Aggregate. Scheduled at 1:00 AM. Then there is lock set in system 3 times in a span of 65 mins.3.sap. you shall delete those aggregates if there is no report presently using this aggregate.com | BOC .sap. where queries based on this aggregate are run yearly or half yearly.g.g. 3. Using this field.3. 3. In same Table: RSDDAGGRDIR. HACR process (RSPC -> Process type tab -> ‘Other BW processes’) is added subsequent to the masterdata load job. So after making the list of unused aggregates.2 Delete/deactivate aggregates that are not used frequently. aggregates with Field: ‘No.com | UAC . of aggregates without affecting report performance.There is a lookup into material masterdata for say inventory transaction data load.SAP BW Hierarchy Attribute Change Run Management In BW 3. 3.: . The best practice is to Schedule all the Masterdata chains in same cluster of time.1.sap. By doing this we earn a span of 65 – 15 = 40 mins where a transaction load can run without any chance of failure due to lock issue. By default 3 parallel Dialog process can be ran. In Table: RSDDAGGRDIR.uac. 3.X you can customize in table RSADMIN. Note: Before making this settings check the number of processors available and discuss with Basis Team. E.bpx. Please refer the Note 534630 .: .1 Delete unused Aggregate.sap.3. Assuming each HACR takes 5 mins.com 6 . of call-ups’ = 0 are not used since they are last changed. Optimize the run time of HACR by rescheduling the process chains. the field ‘Last call-up’ gives the last time a query or sub aggregate hit the respective aggregate. Constraint: Business requirement might demand HACR should run just before respective Transaction load. If we Club the 3 PCs in single Meta chain and run only one HACR Processes.sdn.2. You shall schedule a process chain scheduled 2 weeks before the report requirement period. then to run single HACR in the end. SAP COMMUNITY NETWORK © 2010 SAP AG SDN . less usage. 3.Parallel processing of Change Run for detail. Reduce the time span of HACRs by Clubbing the Master data chains. When you try repeating the job it again failed. So repeat the failed job after this lock is realized will help . The Next level is to find low performing aggregate and delete or redesign them. Else check for any other lock by job in SM12.sdn.SAP BW Hierarchy Attribute Change Run Management Fig. the name is BI_PROCESS_ATTRIBCHAN). Find aggregates with ‘less usage’ (No. I have put them in 3 scenarios and one commonly made mistake.boc. In a time span where there is no lock). SAP COMMUNITY NETWORK © 2010 SAP AG SDN . the lock will be realized. ** The HACR job releases its lock well in advance before the actual completion of the job itself. Please go through the point (E) Locking concept – In Sap notes 1388570. 4. less usage.e. Also check ‘Valuation’ field in the ‘Aggregate maintenance’. If there is no difference and if that aggregate is not a parent aggregate. A HACR of a characteristic failed due to lock of the characteristic. Find aggregates with less summarization value. Transaction CHANGERUNMONI or b. Deactivate these aggregates and test the query performance.3.sap. Run to change run now (i. Snap shot of table RSDDAGGRDIR. Both these fields are available in table: RSDDAGGRDIR. Scenario 2: Bypassing a terminated change run Scenario 3: Infoobject not released Myth regarding HACR recovery Scenario 1: The basic.sap.com | BOC .3.sap. In SM37 for the Batch job scheduled for HACR (If scheduled in process chain.com 7 . Step 4: After the locking job is completed.3.sap.3.com | UAC . What should be done? Step 1: Check if any other change run is active in a.uac. Note: The format of field ‘last call up’ and TIMESTMP is yyyymmddhhmmss 3. Do and don’t when HACR job fails This section gives insight on correcting a HACR failure. you can delete it.com | BPX . of call-ups) and ‘less summarization value’ (AVGFACTREDUCE). Step 3: If the locking job is running fine then wait for the job to complete. Keep on repeating the job doesn’t help**.     Scenario 1: The basic.bpx. Step 2: Find the job locking the characteristic. The HACR job would complete successfully now. activate the aggregates.sap. are now free to run. This will release all the locks on the infoobjects by the HACR. If last change run was unsuccessful. To find the affected aggregates.uac. by changing a database table or executing a function module). Step 1: Run RSDMD_CHECKPRG_ALL (or Transaction RSRV -> ‘All Combined tests’ -> the masterdata) for the characteristic and repair any errors Step 2: Run functional module RSDDS_CHANGE_CHA_MAINTAIN in transaction SE37 with the following parameters to add the characteristic to the change run list.com | BOC . which were deactivated in step 1. Myth regarding HACR recovery The below 2 incorrect solutions are used for scenario 3 which leads to inconsistency of aggregates.SAP BW Hierarchy Attribute Change Run Management Scenario 2: Bypassing a terminated change run. Note: In case If aggregates are already inconsistent. Step 1: Deactivate all affected aggregates. "Change run monitor" (transaction CHANGERUNMONI) can be also used.com | UAC . Go to the FM RSDDS_AGGR_MOD_CLOSE and run it.sdn. 2. By experience you know this change run takes time.com | BPX . Step 3: Run other data loads Other data loads/ Change runs. If customer is very sure that aggregates are consistent though the HACR is terminated then he can manually set the flag to X. which were held. I_CHABASNM = (Technical name of characteristic) I_RNSID = -1 Step 3: Execute the Hierarchy/attribute change run.com 8 . The infoobject should be released now. follow the steps given for scenario 1. Step 2: Restart the change run. Now re run the HACR.sap. Many SAP customer thinks that above mentioned solution would resolve the issue then they land in to trouble. what is the workaround to go ahead with critical process loads? Below is the four-step solution. How to handle it? Below is the three-step solution. In a down time after all the hustle over. Some times the infoobjects are not released from the previous change run. Scenario 3: Infoobject not released.boc. A Change run is terminated. SAP COMMUNITY NETWORK © 2010 SAP AG SDN . Start the terminated change run in the same way as you first started it (Process chain or batch job or running the program** in SE38). Change this field CLOSEDFL to 'X' and the infoobjects will got unlocked.sap. select all entries in table RSDDAGGRDIR that fulfill the selection criteria: OBJVERS = A and MODCNSID <> 0 The status shouldn’t be manually reset of a terminated change run (for example. as it will make the aggregate inconsistent.sap. 1. **Program to run HACR is RSDDS_AGGREGATES_MAINTAIN. As we cannot proceed to next change run (or data load in many cases) without completing this change run. Go to table RSDDAGGRMODSTATE -> there will be a with field CLOSEDFL = 'blank ‘ (false). So better use the solution mentioned above. Following which any transaction loads using the infoobject will fail. Step 4: Activate the aggregates again. CUSTOMER SHOULD NOT SET THE FLAG MANUALLY TO X.bpx. com | BOC . SAP COMMUNITY NETWORK © 2010 SAP AG SDN .Parallel processing of Change Run (3.sap.com/saphelp_nw70/helpdata/en/48/807834109a1b5ae10000000a42189c/frameset.Hierarchy and attribute change run (3.sap.htm For more information.sdn.X).bpx. http://www.com | UAC .X and 7. visit the EDW homepage.com/irj/scn/weblogs?blog=/pub/wlg/13726 Note 534630 .X) Note 903886 .sap.com | BPX .sap.sap.SAP BW Hierarchy Attribute Change Run Management Related Content Please refer below materials for more insight on the discussed topic.boc.X) Note 1388570 . Note 1053605 – Error due to status of a terminated change run was manually set to "Completed".sap.com 9 . http://help.BW Change Run (compares Change run in 3.sdn.uac. uac.sap. Changes made based on this information are not supported and can be overwritten during an upgrade.sdn.com | UAC . SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample.sap.sap.SAP BW Hierarchy Attribute Change Run Management Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. SAP COMMUNITY NETWORK © 2010 SAP AG SDN . You agree that you will not hold. SAP responsible or liable with respect to the conte nt of this document.com 10 .bpx.com | BOC .sap. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. and anyone using these methods does so at his/her own risk. SAP will not be held liable for any damages caused by using or misusing the information.boc. or seek to hold. code or methods suggested in this do cument.com | BPX .