Getting Size of Data Target [Cube / DSO]

This Document describes how to know occupied size of the cube or DSO on the server or what's the size of the data target. This information is needed many times for analysis.

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0427b8a-7fe5-2c10-f1be-a8be71fa2c06

Find out if R/3 field is already transferred to BW

When executing a fit/gap analysis (are all necessary R/3 fields already extracted and transferred to BW), table RSOLTPSOURCEFIE can be used.
Within the selection screen you can enter, for example, R/3 field MATNR if you want to know in which datasources MATNR is used.

The screenshot below shows the overview of all datasources which use R/3 field MATNR:

To see, per datasource/transfer structure, to which infoobject the R/3 field is mapped, table RSTSFIELD can be viewed.
In the screengrab below you can see that R/3 field MATNR is mapped to infoobject 0MATERIAL within several transferstructures/datasources.

Debug startroutine in BI 7.0

Within BI 3.x it was quite easy to debug your startroutine. Pressing the sequence F7 -> F6 -> F5 brought you directly to the startroutine (code). Within BI 7.0 the "F7->F6->F5" trick doesn't work anymore.
To debug a startroutine in BI 7.0, the following steps need to be executed:

1) Go to Display Generated Program within the transformation

2) Jump all the way down to find some startroutine coding you recognize :-) and place a break-point.

3) Find the load you want to debug within the DTP monitor

4) Press the debugging button

5) Execute the debugging request and the execution will stop at the break-point which has been created/set at step 2.

Check version of BW frontend applications

If you need to find out which version of the SAP Gui or SAP BEx analyzer is being used (so you get an idea of how many PC's needed to be upgraded/patched),
the content of table RSFEC (BW frontend check) can be very helpfull.

In the example above you can see that SAP Gui version 3.0(20), version 3.5(00) and version 3.5(71) are being used.

Boosting performance of START routine

There are several 'places' where custom made ABAP code can be added within a SAP BI system. One of those places is the START ROUTINE (of an update rule). Within such a start routine, the (incomming) data package can be altered/extended.
This alteration is usually done via 'looping' over the datapackage:

(AS IS)
loop at datapackage (into wa_datapackage).
   datapackage-field = 'new value'.
   modify datapackage.
endloop
The correct way of altering a data package, from a performance point of view, should be by using field symbols.

(TO BE)
field-symbols: < fs_dp > type data_package_structure.

loop at datapackage assigning < fs_dp >.
   < fs_dp >-field = 'new value'.
endloop
Within the TO BE situation, the modify datapackage statement is no longer required!

Display cube dimension percentage used

To display, per dimension, the percentage used with regard to the number of entries in the fact table(s), function module RSDEW_INFOCUBE_DESIGNS can be used.
Enter the name of the cube for input parameter I_INFOCUBE and execute the function module.
Export parameter E_T_TABLSIZE will provide you the desired result as shown in the attached picture.

Re-set a FULL LOAD to FULL REPAIR LOAD mode

When having executed a full load to a delta enabled target, the next delta request cannot be activated anymore. (The full load is hampering this)
Solving this issue by deleting this full load can be a solution, but it's easier to reset the full load to a full repair load.
The latter can be accomplished by executing report RSSM_SET_REPAIR_FULL_FLAG.
(Tcode: SA38 -> RSSM_SET_REPAIR_FULL_FLAG)

Find out in which MASTERchain a LOCAL (process)chain is embedded

If you have the technical name of a process chain (and you want to execute it via transaction RSPC1), you might need to know if you're going to execute the MASTER process chain or (just) a LOCAL process chain.
You can find out the "link" between a local process chain and it's MASTER process chain via the content of table RSPCCHAIN.
(SE16, table RSPCCHAIN, OBJVERS=A, VARIANTE=local process chain name)

The result of the above SE16 selection will show the following result:

The local process chain name can be found in the column VARIANTE as where the MASTER process chain name is to be found within column CHAIN_ID

Usefull (std. SAP) ABAP programs within a SAP BI environment

Listed below several "may come in handy" ABAP Programs (within a SAP BI environment)

RSCDS_NULLELIM: Delete fact table rows where all Key Figure values are zero. See Note 619826.
RSDG_CUBE_ACTIVATE: Activation of InfoCubes
RSDG_CUBE_COPY: Make InfoCube Copies
RSDG_CUBE_DELETE: Delete InfoCubes
RSDG_DODS_REPAIR: Activation of all ODS Objects with Navigation Attributes
RSDG_ODSO_ACTIVATE: Activation of all ODS Objects
RSDG_IOBJ_ACTIVATE: Activation of all InfoObjects
RSDG_IOBJ_DELETE: Deletion of InfoObjects
RSDG_IOBJ_REORG: Repair InfoObjects
RSDG_IOBJ_REORG_TEXTS: Reorganization of Texts for InfoObjects
RSDG_MPRO_ACTIVATE: Activating Multiproviders
RSDG_MPRO_COPY: Make Multiprovider Copies
RSDG_MPRO_DELETE: Deleting Multiproviders
RS_COMSTRU_ACTIVATE_ALL: Activate all inactive Communication Structures
RS_TRANSTRU_ACTIVATE_ALL: Activate Transfer Structure
RS_PERS_ACTIVATE: Activating Personalization in Bex(Inactive are highlighted)
RSAU_UPDR_REACTIVATE_ALL: Activate Update Rules
RRHI_HIERARCHY_ACTIVATE: Activate Hierarchies
RSSM_SET_REPAIR_FULL_FLAG: Convert Full Requests to Repair Full Requests
SAP_AGGREGATES_ACTIVATE_FILL: Activating and Filling the Aggregates of an InfoCube
SAP_AGGREGATES_DEACTIVATE: Deactivating the Aggregates of an InfoCube
SAP_INFOCUBE_DESIGNS: Print a List of Cubes in The System and Their Layouts
SAP_ANALYZE_ALL_INFOCUBES: Create DB Statstics for all InfoCubes
SAP_CREATE_E_FACTTABLES: Create Missing E-Fact Tables for InfoCubes and Aggregates
SAP_DROP_EMPTY_FPARTITIONS: Locate/Remove Unused or Empty partitions of F-Fact Table
SAP_DROP_TMPTABLES: Remove Temperory Database Objects
SAP_RSADMIN_MAINTAIN: Add, change, delete RSADMIN table entries
SAP_CONVERT_NORMAL_TRANS: Convert BasisCube to Transactional Cube and the other way around.
CUBE_SAMPLE_CREATE: A fast way to put some "sample" records in a InfoCube. No need to use flatfiles, just enter the value in a ALV-Grid or let the Cube be filled with random value.