SAP BW Facts & Information
This document provides some actual facts, information and tips which would be useful in day to day activities in SAP BW system.
Info 1: Exact IOBJ for R/3 table field
This is a smart way to findout the infoobject name for R/3 database table field.
There would be a situation where a BW consultant is stuck trying to find exactly which BW info-object needs to be mapped for the R/3 field. For such cases you need to use the tables RSOSFIELDMAP.
Fact 2: CACHE concept
The Cache is not used when a query contains a virtual key figure or virtual characteristics, or when the query is accessing a transactional DSO, or a virtual InfoProvider
Fact 3: Reducing the Query processing time
Reducing the text in query will speed up the query processing some.
Info 4: Is the Memory Cache Is Set Too Low?
Cache has a system default of 100 MB for local and 200 MB for global cache. This may be too low for a system that can be optimized via broadcaster.
Use the transaction code RSCUSTV14 in SAP NetWeaver BI to increase the cache. Focus particularly on the global cache.
Fact 5: Aggregate Best practice
To avoid poor definition and usage, aggregates should be developed after the system has been in production for a while and real user statistics are captured.
Info 6: Replicate datasources in background
Everyone aware about replicating datasources in RSA1 by right clicking Source system and then replicating the datasources in foreground.
For some reason, if replication in dialog gets timeout, then there is a way that we need to replicate the datasources in background.
1) Go to tcode SE38 – ABAP Editor
2) Enter ABAP program name RSDS_REPL_RESET
3) Click on Execute
4) In the Selection-Screen, enter the source system to replicate from, or * if you want to replicate from all source systems.
5) If you just want to replicate BW 3.5 Datasource, enter ISFS as the Preferred Type. Or, if your preference is for BW 7.x Datasources, enter RSDS as the Preferred Type. If there is no preference, leave the field blank and it will replicate both types.
6) Go to the menu option Program > Execute in Background
Fact 7: Speedup DSO activation
a) If you are not reporting on the DSO, the activation of SIDs is not required (this will take up some considerable time in activation); Often the logs show that the activation job takes almost all the time to schedule the RSBATCH_EXECUTE_PROZESS as job BIBCTL_*. RSBATCH_EXECUTE_PROZESS is for scheduling and executing the SID-generation process.
If you don’t need the relevant DSO for reporting & you don’t have queries on it, you can delete the reporting flag in the DSO maintenance. This wouldbe a good way to speed this process up significantly. Check under ‘Settings’ in the DSO maintenance whether you have flagged the option “SID Generation upon activation”.
Info 8: Multiprovider activation in BW production system
We can activate the Multiprovider in the Production system Directly without affecting the Reports.
Use this Function Module: BAPI_MPRO_ACTIVATE.
Tips 9: Copy process chain
There are many ways to copy an existing process chain. But one of the unknown way to copy an existing process chains is shown in below screenshot:
Open existing process chain in RSPC:
Then type COPY in comment line and hit enter.
We will get popup to give new process chain name. Then we can proceed with our usual steps.
Tips 10: Multiprovider and Hints
To reduce data volume in each InfoCube, data is partitioned by Time period.
A query which is based upon a Multiprovider have to search in all InfoProvider to find the data (i.e. billing docs from 2007). This is very slow.
We can add “hints” to guide the query execution. In the RRKMULTIPROVHINT table, you can specify one or several characteristics for each MultiProvider which is then used to partition the MultiProvider into BasicCubes.
If a query has restrictions on this characteristic, the OLAP processor is already checked to see which part cubes can return data for the query. The data manager can then completely ignore the remaining cubes.
Tips 10: Use SE30 for Test Prformance