Protect 3.x reporting object for overwrite

[Former Member]

Hello,

We have upgraded to NW04s and we have the java stack in place. So developers can use the new Bex Suite shortly. We would like to make sure that none of our old 3.x reporting objects will be overwritten. Is there a customizing setting in NW04s which prevents the 3.x reporting objects to be overwritten by the new Query Designer/ Bex suite?

Thanks in advance for your reply.

Best regards,

Freek

[Former Member]

Hi Edwin,

So if i read correctly it is impossible to really block users to overwrite a 3.x reporting object with the new bex.

I can only prevent users for using the BW7 Bex Query Designer.

Thanks for your explicit reply by the way!

[edwin_harpino]

hi Freek,

check Note 962530 - NW04s: How to restrict access to Query Designer 2004s

Summary

Symptom

The note describes the procedure how to restrict access to Query Designer 2004s protecting queries or reusable query components created in 3.x BW systems from occasional migration to 7.x version.

The procedure is recommended for the Productive systems containing queries or query components created in 3.x BW systems.

Other terms

NetWeaver 2004s, query, reusable query component, Query Designer 2004s.

Reason and Prerequisites

BEx Query Designer 2004s introduces a new infrastructure of query definition which is NOT compartible with 3.x versions. Queries or query components saved using BEx Query Designer 2004s can not be edited using Query Designer 3.x. See note 949330 for details.

Solution

In order to prevent an occasional migration of the productive queires or query component the following procedure can be implemented:

1. Run transaction RS_FRONTEND_INIT;

2. Find the parameter QD_EXCLUSIVE_USER (if it is not available, you can enter it in a new line);

3. Introduce USERIDs which are authorized to work with the BEx Query Designer 2004s.

ATTENTION:

The field size is limited to 30 characters. Only few user can be introduced;

you can also use "*" as wildcard;

Users should be separated by comma;

If the field contains non-existing users, no users will be able to logon the system using BEx Query Designer 2004s;

If the field is empty or contains just a "*", ALL users will be able to logon the system using BEx Query Designer 2004s;

Other parameters in this table MUST NOT BE CHANGED.

When the settings are done, only user listed in the QD_EXCLUSIVE_USER filed will be able to logon the system using BEx Query Designer 2004s. This reduces the potential risk of occasional migration of 3.x compartible queries and query components to 7.x version.

ALTERNATIVE:

There are some claims, that 30 characters are not enough for this field. With a modification of our code you can get an unlimited user list for the desired functionality. The following text describes, how such a modification should look like:

Create a table containing all user names of users allowed to use Query Designer 2004s. Let's asume, the field USERNAME refers these names. Lets asume, the table is called ZUSERS2004S.

Maintain with the transaction RS_FRONTEND_INIT any user name for the parameter QD_EXCLUSIVE_USER as described in this note.

In function module RS_SYSTEM_INFORMATION find the following coding:

• generic properties (including frontend versions for components)

• can be maintained with transaction RS_FRONTEND_INIT

select * from rsfrontendinit

into table e_s_system_info-property_bag.

Add the following coding after the above select:

DATA: l_username like ZUSERS2004S-USERNAME.

select single USERNAME from ZUSERS2004S

into l_username

where USERNAME = sy-uname.

if sy-subrc <> 0.

l_username = '!DISABLED_USER!'.

endif.

l_s_property_bag-id = 'QD_EXCLUSIVE_USER'.

l_s_property_bag-data = l_username.

delete e_s_system_info-property_bag where

id = 'QD_EXCLUSIVE_USER'.

insert l_s_property_bag into table e_s_system_info-property_bag.

The above coding is just a suggestion, it may be modified according to customers needs.Especially the used table and fieldname for the lookup table might vary and has to be modified accordingly.