Monitoring the Change Run

Version 2.0 – BI 7.0

Changerun Basics Monitoring Transactions Monitoring Tasks FAQ

Attribute and Hierarchy Changerun Attribute and Hierarchy Changerun The attribute and hierarchy changerun is required to  activate master data changes to attributes and hierarchies  realign aggregates containing navigational attributes  realign aggregates defined on hierarchy levels

© SAP AG 2006

Attribute and Hierarchy Changerun

If you change master data (navigation attributes) or hierarchies of a characteristic that is contained in aggregates, you must adjust these aggregates. This ensures that queries that access to the InfoCube or assigned aggregates are consistent. Unlike in the aggregates, no data that refers to navigation attributes or hierarchies is stored in the InfoCube. The master data or the hierarchy tables are joined with the tables of the cube when the query is executed. Regardless of whether or not aggregates exist, the system does not automatically transfer master data record changes, rather you must activate this master data explicitly.

© SAP AG 2006

Activation of Attributes in Detail Activation of Master data Attributes Method 1: ‚Manual‘ activation (only possible if no aggregates are existing. otherwise: method 2) Method 2: Automatic activation by Change Run reco mm end ed Active data in master data tables and aggregates Active data in master data tables and aggregates InfoObjects are automatically assigned by the system © SAP AG 2006 .

Attribute and Hierarchy Changerun – Example Navigational Attribute of Customer Customer 1000 2000 3000 3000 4000 OBJVERS A A A M A Industry Pharma Retail Pharma Chemical Chemical Aggregate Customer__Industry * Key Figure 10 15 5 10 10 20 25 Customer__Industry Pharma Retail Chemical Key Figure 60 25 10 Changed master data not available for reporting Fact Table Sales Data Country USA Germany USA Austria Austria Germany © SAP AG 2006 Customer 1000 2000 3000 2000 4000 3000 1000 The impact in the aggregates is always because the navigational attributes (xxx__navattribute) USA .

Attribute and Hierarchy Changerun – Example Navigational Attribute of Customer Customer 1000 2000 3000 4000 OBJVERS A A A A Industry Pharma Retail Chemical Chemical Changed master data now available for reporting Fact Table Sales Data Country USA Germany USA Austria Austria Germany © SAP AG 2006 Aggregate Customer__Industry * Key Figure 10 15 5 10 10 20 25 Customer__Industry Pharma Retail Chemical Key Figure 35 25 35 Customer 1000 2000 3000 2000 4000 3000 1000 USA .

the only way to adapt the aggregates in a changerun is rebuilding them.Strategies to Adapt Aggregates There are different strategies to adapt aggregates in a changerun:  Rebuild the aggregate  Delta Mode  Rollup from previously adapted aggregate (Parent ->Child Aggregates) For InfoCubes containing key figures with aggregation MIN/MAX. © SAP AG 2006 . The value 'Limit with Delta' determines the percentage of master data changes at which the delta mode isChanged to to be switched to reconstruction.

Delta Mechanism During Change Run A delta mechanism for Change Run is available Aggregates are not completely rebuilt if the percentage of changes is below a certain threshold © SAP AG 2006 .

Idea Read in several blocks to prevent resource problems when filling an aggregate © SAP AG 2006 .Aggregates .Blocksize PROBLEM PSAPTEMP SIZE During rollup and Change Run high resource consuming operations on the temporary tablespace can be performed.

NEW : Wait Time Wait Time: An immediate Change Run start may not be possible because other processes hold necessary locks (e. Hard-Coded Time: Other processes locked by a changerun in STARTUPphase wait per Default 5 min. (not changeable) © SAP AG 2006 . …) The Wait Time specifies the time in minutes how long a Change Runs waits before terminating. Roll Up.g Master Data Loading.

NEW : Parallel Change Run in NetWeaver 2004s New since NetWeaver 2004s: .Change Runs are executed only with background processes .The parallel degree can be set in Customizing or transaction RSBATCH © SAP AG 2006 .

Compression of Aggregates © SAP AG 2006 . Adjustment of Aggregates Maximal N-1 parallel jobs Managing job Maximal N-1 parallel jobs 2. Activation of Master Data Maximal N-1 parallel jobs 3.NEW: Parallel Change Run in NetWeaver 2004s • The Change Run combines different steps which are processed sequentially • Each of the steps is restricted by the maximum number of parallel jobs (N) chosen in Change Run Customizing • There is 1 Managing job • There are maximal N-1 working jobs 1.

Furthermore some activities are not allowed during the Change Run works – master data loads to the affected InfoObjects.Technical details about Change Run  Step 1 (usually less than 1min): When the Change Run starts a global SAP enqueue lock is set. This global enqueue lock doesn’t allow – any master data loads to InfoObjects – starting another Change Run – rollup to an aggregate  Step 2: After the global lock was removed just a smaller enqueue lock is set. This global lock is hold just for a short time until the affected infocubes are identified. but master dataload to other InfoObjects – rollup for InfoCubes having aggregates affected by the Change Run © SAP AG 2006 . It locks just the affected Infoobjects and the InfoCubes where the infoobject is used.

NEW:Change Run in Netweaver 2004s New Change Run Lock Concept with NetWeaver 2004s :  Two or more Change Runs in WORK-Phase can run in parallel (if the Change Runs process different objects)  There can be only one Change Run in STARTUP-phase – A second Change Run waits up to 5min to get the lock for STARTUP (hardcoded) – Other blocked processes (e.g Master data loading) wait as well up to 5min (hard-coded) for the Change Run  The locks for Change Run are set/checked on InfoCube level (in former releases on aggregate level)  The RSADMIN-parameter CR_MAXWAIT was replaced by Customizing – Default = 1min © SAP AG 2006 .

5min NEW !! Change Run 2 Two Change Runs can run in parallel if affected objects are different Change Run 1 NEW !! Change Run does not terminate immediately if another Change Run is in Startup STARTUP WORK Time NEW !! Change Run 2 Second Change Run does not set global lock when waiting for another Change Change Run 1 Run.NEW: Parallel Change Run in NetWeaver 2004s Change Run Concept since NetWeaver 2004s Max. STARTUP © SAP AG 2006 WORK Time .

Keep in Mind…. The length of the change run depends on several factors:  Amount of master data to be changed  Amount of hierarchies to be adapted  Number and size of aggregates and their basis infocubes  General load on the system  Status of the database (statistics & indices)  number of partitions in Source Cube (F-Table) © SAP AG 2006 .

Changerun Basics Monitoring Transactions Monitoring Tasks FAQ .

Changerun Transaction The central transaction to the changerun is RSATTR or RSA1  Tools  Apply Hierarchy/ Attribute Change… © SAP AG 2006 .

© SAP AG 2006 .InfoObjects and Hierarchies to Be Activated The changerun is always started for a set of InfoObjects and/or hierarchies.

© SAP AG 2006 .Information on Background Jobs The frame 'Applied hierarchy/attribute change runs’ shows information on background jobs:  Changerun Status  Start and end date  Start and end time  User  Job name Transaction SM37 always shows times in UTC format whereas the times in the changerun transaction are converted to the time zone of the user.

number of changed characteristic values and adapted aggregates.Application Log The application log shows information about the InfoObjects and hierarchies to be activated. © SAP AG 2006 .

© SAP AG 2006 .Changerun Monitor The changerun monitor shows information about the current status of the changerun. the InfoObjects and hierarchies to be activated. the affected aggregates and how they were/will be adapted. The changerun monitor is displayed in a separate window be Patient. Ignore the message about missing authorizations.

affected aggregates and how they were/will be adapted. Ignore the message about missing authorizations. of object changes .Changerun Monitor The changerun monitor ( RSDDS_CHANGERUN_MONITOR) shows information about the current status of the changerun. the InfoObjects and hierarchies to be activated. the affected cubes and no. The changerun monitor is displayed in a separate window be patient. © SAP AG 2006 .

rollup. reconstruction © SAP AG 2006 .Standard Changerun Monitor Some info below will be available after clicking the Details button Status of changerun Basic Characteristics with modified master data to be activated Object changes in Infocube to be updated Aggregates which have to be adjusted during the changerun including mode: delta.

Click here to restart the terminated ACR © SAP AG 2006 . after resolving the issue you can repeat the failed step in the process chain or restart it via the Change Run Monitor The changerun monitor is displayed in a separate window be patient.Terminated Monitor In case the ACR terminates by any reason. Ignore the message about missing authorizations.

If equal to 1.Using Statistical Information before Deactivating Aggr Fields of table RSDDAGGRDIR INFOCUBE AGGRCUBE NUM_AGGR NUM_ENTRIES CALLS LAST_CALL Infocube name Aggregate name Number of Components Number of Records in the Aggregate Aggregate usage (if low it is a candidate to be deleted) Last time the aggregate was used AVGFACTREDUCE Medium dividing the cube records per aggr records. means aggr same size as the cube © SAP AG 2006 .

Statistical Information on Adjusted Aggregates Still in the table RSDDAGGRDIR selecting “INA” in the column Object Status (OBJSTAT) and “A” in the column Version it is possible to analyze which aggregate is being adjusted at the ACR time. you can deactivated just the aggregates that are being adjusted not ALL aggregates. You must select those entries in “M” version Analyzing the table RSDCUBEIOBJ – Verify which infoobjects are being used by aggregates © SAP AG 2006 . Analyzing the table RSDDAGGR_V you can see which aggregates are going to be impacted by the Change Run Process before the ACR job to adjust those infoobjects start. IF NEEDED. This way.

Changerun Basics Monitoring Transactions Monitoring Tasks FAQ .

Monitoring Tasks Monitoring Tasks While monitoring the system. one of the following questions may arise   What is the status of the changerun? How should I restart a cancelled changerun? © SAP AG 2006 .

Changerun Status – Step 1 Status of Background Job In transaction SM37. select jobs starting with 'BI_STRU' or 'BI_PROCESS_ATTRIBCHAN‘ which are the Parent Jobs The Child jobs start with BICHNG* (Job to adjust/rebuilt Aggregate) BIACTI* ( Job to activate the Info object ) © SAP AG 2006 .

the Parent Job Automatically repairs and adjusts the aggregate in the failed job. Currently its set to 16 BTC processes in parallel. © SAP AG 2006 . Pls note that When a BICHNG* job fails.Changerun Status – Step 1 Based on the Parallel settings you could see Multiple jobs running.

1.2. © SAP AG 2006 .Some more in depth tips (1) 1) To get stats on Info Objects concerned and Aggregates touched: 1. In Table RSDCUBEIOBJ (or RSDDAGRR_V (version ‘M’). 1. find out the aggregates that presents the high number of master data changes.Condition : all Process Type ATTRIBCHAN will have to be preceded with Custom Process Type ZGTTC_CR and ACR will not be run directly (via Tools>Mdata Activation = job type BI_STRU*).

More in depth tips (1.2): Nav Attributes : where used (aggregates) select Infocube [*] Y5 with version ‘A’ and InfoObject = YMAT_COMP__0MATL_GRP_1 © SAP AG 2006 .

Some more in depth tips (2) 2) To get all ACR background jobs (manual or PC trigerred) in proper sequence with Start Time. End Time and Process Chain Id. Use SE16 on view V_OP with selection on jobname BI_STRU* BI_PROCESS_ATTRIBCHAN BICHNG* BIACTI* A = Abort F=Finished © SAP AG 2006 .

find the InfoCube on which the aggregate is defined: © SAP AG 2006 .Typical Reasons for Cancelled Changeruns In transaction SE16. table RSDDAGGRDIR.

restart the changerun from the log view of the process chain: © SAP AG 2006 . enter the InfoCube name and deactivate the aggregate: Then.Typical Reasons for Cancelled Changeruns In transaction RSDDV.

Changerun Basics Monitoring Transactions Monitoring Tasks FAQ .

si n O t If obsolete DB statistics caused the problem. tb us m S E G N A H C o N © SAP AG 2006 .. then you could go ahead and te later on. deactivating the aggregate may not be necessary. In this d e (rare) case. Therefore. Please check if this on c Aggregate has been adapted for Reconstructionm the Change Run in a te Deactivate it and fill it Monitor and if it is . However. on cancelled and restarted.FAQ Is there an alternative to deactivating an aggregate in order to solve n io changerun problems? at m fir If the changerun gets stuck with an aggregate. the refresh does not affect the currently w e the current changerun must be running SQL statement. they can be refreshed in ou i th transaction DB20.

all affected aggregates must be deactivated and re-filled manually. it is not possible any longer to adapt the affected aggregates in delta or rollup mode. However. which require up-to-date master data. There are function modules to activate master data which do not check whether aggregates are affected by the master data changes. Therefore. without waiting for the end of the changerun. in this case. It is obvious that this procedure involves a high risk of inconsistent data in aggregates (if one forgets to deactivate an aggregate). it would be possible to start critical process chains. The aggregates could be adapted later once the critical process chains are finished. Then. © SAP AG 2006 .FAQ Is it possible to activate master data separately from adjusting aggregates? If so. this procedure is not considered as an alternative to the changerun.

FAQ Is it possible to select which aggregates are activated as part of the changerun and which can be scheduled separately later? As explained on the slide before. the approach to adjust aggregates separately from the master data activation involves a high risk and is not considered as an alternative to the changerun. © SAP AG 2006 . if the decision is taken to deactivate several aggregates in order to speed up the changerun. it is possible to select which aggregates are deactivated and which should be adjusted by the changerun. However.

ne do be st u m ES G N A H C o N © SAP AG 2006 . Identify aggregates adjustedoin delta or rollup mode with high i th changerun times and w optimize the aggregate hierarchy. O ut 2. Stat = INA) i te ns or RSDDSTATAGGR . Identify aggregates that are adjustedam rebuild during the by te changerun (table RSDDAGGRDIR Vers A.FAQ How to tune the performance of the changerun? fir n co m io at n 1.

It is enough to only have the characteristic 0CUSTOMER in the aggregate si definition. This is NOT recommended. It will increase the time of the te change run. See note 590370. on c – Both a characteristic and it’s navigational attribute are used in the same aggregate m definition with * aggregation level (for example. mCOMPRESS! COMPRESS! COMPRESS! ES G N A H C o N m – Maybe there are too many aggregates. 0CUSTOMER & a te 0CUSTOMER__0CUST_GRP).FAQ Possible causes of poor performance Poor modeling decisions tio a n u ho F Facttables of the infocube or Too many uncompressed requests initthe w aggregate e on – On all database platforms it is strongly recommended to regularly compress infocube d e and aggregate data. A maximum number of 20 .30 u partitions (uncompressed requests) per F table are recommended. even though they have only included t © SAP AG 2006 . Check the number of b entries in packet dimension st table /bic/DxxxxxxP. For ORACLE it is particularly important. You should check if you can delete any unused & fir unnecessary aggregates. A query with a selection on 0CUSTOMER__0CUST_GRP will still access the n O 0CUSTOMER in the definition!! aggregate.

then all aggregates will be ‘Reconstructed’ during each us change run. © SAP AG 2006 . If the DELTALIMIT is set too high. m S Missing SAP Notes GE – Be sure to search N any relevant notes for the customers BW Support package level.FAQ Possible causes of poor performance (2) DB statistics are not up-to-date m tio a n ir – DB statistics must be up to date for the database to choosefthe most optimal accesses to the data. O te am te Degenerated Indexes ut oor too high RSCUSTV8-DELTALIMIT is set too low ith to 20. it could happennthat you have a run away co change run program that can never finish because of a poor execution plan. If b it is set too low or not set at tall. then the aggregate will be on d ‘Reconstructed’ (or rebuilt completely). it can take e longer to adjust the aggregate using the delta method. If statistics are not up-to-date. This means that if less than 20 percent – SAP recommends setting this parameter w of the masterdata of a characteristic has been changed. Good search terms for H C o N – Don’t forget to look for DB related performance notes that refer to index rebuilding or statistics creation. i – Degenerated indexes can also cause longer runtimes as the data cannot be accessed in ns the most efficient way on the database. If more than 20 percent has changed. A for notes are Change Run or Realignment Run & BW-BEX-OT-AGGR. as opposed to doing a rebuild. the aggregate will be changed e with the ‘Delta’ method.

high t resource consuming operations are performed on u temporary tablespace. Try to schedule this job during am periods of low or limited system activity. d e tb us m S E G N A H C o N © SAP AG 2006 ..currently 16BTC are run in parallel m fir Schedule the Change Run when the system load is lightestcon – Heavy system load can cause the change run to take more time. te te si Customize the BLOCKSIZE parameter n of – During the initial filling of an aggregate or the rebuildO an aggregate during the change run. parameter to read in several blocks to prevent resource th iParameters for Aggregates -> Blocksize .FAQ Additional ways to improve performance n io at Execute Change Run in Parallel. Set the BLOCKSIZE o the problems when rebuilding an aggregate. This is a Transaction SPRO –> General BW Settings –> w database dependent setting and should bee tested by customers to determine the best performance on when filling an aggregate.