BI/BW Tips

 BI Tip # 1

Struggling… as there is no sample data for your newly developed Infocube, why not try this?

Try using ABAP program CUBE_SAMPLE_CREATE. It allows you to enter required sample data directly into your cube without using any flat files, source system configuration etc. Records are added to the cube in one request using the APO interface without monitor log.

Try exploring even further with all the options available there.

Needless to say try it on Sandbox, development system before attempting on production environment.

BI Tip # 2

To check whether your query is migrated to SAP BI7 version already

Check the Table RSZCOMPDIR: Enter your Query Technical Name as input to the field COMPID and execute.

If Field VERSION in the Table RSZCOMPDIR has the value less than 100 that means Query is in 3.x version. If it is more than 100 means, it is already migrated.

BI Tip # 3

Couple of interesting tricks -

· RSDG_MPRO_ACTIVATE is a program to activate the Multi providers in production system directly. If there are any inactive MultiProviders due to some transport or any other reason, this will activate the Multiprovider without affecting reporting.
Needless to say try it on Sandbox, development system before attempting on production environment.

BI Tip # 4

Worried about Data Loss while changing extract structure, why not try this?

Run the Report RMCSBWCC before doing changes to the LO extract structure or while importing any changes done to the extract structure.

This report checks whether any of the clients in the system contains data in the V3 update (Extraction queue) for that application (specific to extract structure provided as input). If there is data in V3 updates then you need to start the update for that application. Without doing this you will not be able to change the extract structure and if you are importing the changes then you may end up losing data.

BI Tip # 5

RSICCONT is a table used to delete the request of a data target including DSO or Cube. Facing any problem in deleting the request from a DSO or a cube while loading the data. Try this.

Needless to say try it on Sandbox, development system before attempting on production environment.

BI Tip # 6

Most of you are aware of RSZDelete tcode, but lot of them face the issue of how to delete enmass queries on one infoprovider or something in multiples. Well the answer is in same tcode.
For E.g.: You need to delete 10 queries out of 20 based on a infocube. Normally , developer tend to delete one by one. But you can delete multiple queries also.
Infocube : ZSD_C03
Total Queries : 25
To Delete : 15

In RSZDelete,
Type = REP
Infocube = ZSD_C03

Execute….
You get list of all queries….. select the one that requires to be deleted.

PS: This is an extremely DANGEROUS Transaction… Please use responsibly.

BI Tip #7

Replicate Single DataSource

- Use RSAOS_METADATA_UPLOAD function module to replicate single datasource. Logical system - put in field I_LOGSYS OLTP datasource name - put in field I_SOURC. and execute.

Trust you shall check this in Sandbox / Development System first.

BI Tip #8

Load Monitoring Table..

Did you explore table RSSTATMANPART? –

Do you struggle every day while doing data load status monitoring and reporting? Did you ever thought of checking table RSSTATMANPART?

Check the “Manage” tabs of multiple Targets or InfoProviders together ? Use the table RSSTATMANPART to obtain the same. This data will tell you whether the load to the target was successful or not & also will let you know whether the target is reportable or not.

I happen to come across couple of interesting content covering it on SDN, sharing for your reference –

This one is ABAP code for status monitoring

http://wiki.sdn.sap.com/wiki/display/BI/Current+Day+Data+Load+Monitor+Program

Other one is the link of one of the forum thread –

https://forums.sdn.sap.com/thread.jspa?threadID=1232358

Needless to say try it on Sandbox / IDES system before going forward.

Happy Learning.