Solution : https://service.sap.com/sap/support/notes/903886 (SAP Service marketplace login required)
Summary :
This SAP Note details the processes involved in the hierarchy/attribute change run in BW3.X, aimed at refining the handling of aggregates when master data or hierarchies change. If changes are made to master data (navigation attributes) or hierarchies that affect aggregates, these need to be adjusted to maintain query consistency with InfoCubes. The note explains how the change run involves collecting relevant InfoObjects and identifying the affected aggregates and cubes, locking systems to prevent data changes during the start phase, and proceeding with a detailed change run process. It covers various operational steps like restarting interrupted change runs, handling multiple parallel change runs, adjusting time-dependent attributes, and the specific procedures in the 'processing phase' such as blockwise reading and delta modes for aggregate adjustment. The solution includes critical notes on how to approach analysis and problem resolution, using tools like the Administrator Workbench and process chains for execution.
Key words :
transaction rsa1 -> tools -> apply hierarchy/attribute change -> infoobject list, bw customizing - bw - general bw settings - parameter, automatically transfer master data record, table rsddaggrmodstate [ii] analyzing problems, rsa1 -> tools -> hier, hierarchy/attribute change run, time-dependent navigation attributes, changerun -> 'change run monitor', current master data active, multiple parallel change runs
Related Notes :
| 1388570 | BW Change Run |
| 825927 | The BW Changerun: CR_MAXWAIT |
| 730980 | Realignment run blocked when started |
| 653469 | Pre-analysis of aggregate filling |
| 590370 | Too many uncompressed request (f table partitions) |
| 583202 | Realignment run and condensing |
| 534630 | Parallel processing of Change Run |