Quickly find queries which use specific InfoObjects (part II)

In addition of one of my previous blogs I adjusted the function module RSZ_I_BASIC_KEYFIG_WHERE_USED and saved it to a new version.
The problem with the standard function module is that is requires to fill in a MultiProvider or CompositeProvider in order to get a result set.
Where used key figures function module
Because I had the requirement to get a complete overview without any restrictions I used and changed the ABAP code. The new function module will only ask for a InfoObject name and will show you a list of all relevant queries.

Copying queries between CompositeProviders using RSZC

Last week one of my colleagues had trouble copying queries between two CompositeProviders using RSZC. Searching accross the internet and SCN ended up in people stating to have the same problem. It seems that still a lot of people are unaware of the fact that the technical name of an CompositeProvider is different than the technical names of any other InfoProvider.

When creating a CompositeProvider the system automatically adds a additional prefix of @3 to the InfoProvider name as mentioned in the SAP Help. So in case of a CompositeProvider with the name CP_0003 the real technical name is @3CP_0003. Using this complete technical name it is possible to copy queries between CompositeProviders using transaction code RSZC.

Copying queries between CompositeProviders using RSZC

Quickly find queries which use specific InfoObjects

When it comes to deleting InfoObjects from SAP BW it is necessary that these are not used anymore by other objects in the system. The standard where-used functionality could supply sufficient insight. However the standard where-used functionality is not always accurate when a person wants to know in which SAP BW queries an InfoObject is used. For this specific case you have the ability to use one of the following two function modules.

Technical nameType

By filling in the right parameters the function module delivers a table of queries using the specified characteristic or key figure.

Bex Broadcaster dynamic variables

A couple of weeks ago I got a question from a sales analyst asking if it’s possible to automatically send out workbooks. Every morning the sales analyst is waiting for output of multiple workbooks. This consumes a lot of time. I responded that for this purpose SAP has a standard functionality available in the form of the Bex Broadcaster, but that I needed some time to setup the infrastructure and testing it.

If you have already worked with the Bex Broadcaster you probably know that scheduling queries can be used out of the box, without any additional server. However if you want to schedule workbooks you will need a precalculation server (which is actually a Windows computer with Excel and the precalculation service installed). Since the sales analyst is using workbooks with more than 35 queries in it (we are not talking about efficiency here), this additional precalculation server is required. All steps to setup this server are mentioned in this post on SCN.

During the testing phase scheduling a simple workbook worked straight out of the box (that’s a good thing!). Second test was executing the workbook consisting out 35 (!) queries. Believe it or not, this also worked. The only downside of scheduling this workbook, is that the variables which are assigned to the underlying queries were fixed values. This is a disadvantage because the workbook is refreshed every day based on the current calendar day. One option I considered in order to solve this, is to redesign the complete workbook (including the queries). This will take a lot of time, thus I started searching on Google and SCN, resulting in viewing this post. There someone explains how workbook variables can be changed dynamically by using a program he created. My quest was finished! We will use this program to manipulate Bex Broadcaster variables.

Important tables in SAP BW

A BW blog without mentioning some of SAP’s most important tables is useless. These tables can be quite handy when analyzing issues or coding ABAP. Use the read more button to view the complete list, or download the attachment.