Set location on CR going against SAP BW and dynamic pick lists

[Former Member]

If I take an existing Crystal Report that was created against a BW query in evironment A and then set the location to environment B (two completely different environments) would role-based dynamic pick list functionality function correctly when the report is published into the new envioronment? I am assuming the report was first created using the SAP toolbar and the report is being published using the BW Publisher. I have not tried this yet and I have a client who is thinking of taking some existing reports and using them as "starter reports" in their environment. Even though I know I can do a "Set Location" to move the report to the new query I'm concerned that I'll lose the ability to leverage role-based pick lists when the report is published to InfoView.

[IngoH]

Hi,

first of all picklists are not role based. Picklists - assuming we talking about SAP variables here - are based on the underlying characteristic and the BEx query.

so the set location has to be done and depending on source and target query you might have to do field mapping and the publishing.

Ingo

[Former Member]

In my understanding, an authorization variable has to base it's picklist on a role. Otherwise how is it going to know what characteristic or hierarchy node values it needs to generate the picklist. If an authorization variable doesn't use roles to determine which values to return, what does it use?

Your response said to do a set location (and perhaps some field mappings) and the Infoview dynamic pick lists should work fine. Just to be clear, are you saying that if I start with a report that was originally created against SAP system A and then set the location to SAP system B (a completely different SAP system) that the dynamic pick list functionality will work correctly when the report is run in the Infoview on the new system? Would the only pre-requisite be that the report was created using the SAP toolbar and is then published using the BW Publisher? I would love for this to work as that would allow for the creation of pre-built "starter reports" that could then be switched to the customer's environment and still be able to leverage dynamic pick list functionality.

Edited by: Michael Garrett on Aug 10, 2011 4:44 PM

[IngoH]

Hi,

In my understanding, an authorization variable has to base it's picklist on a role. Otherwise how is it going to know what characteristic or hierarchy node values it needs to generate the picklist. If an authorization variable doesn't use roles to determine which values to return, what does it use?

>> An Authorization Variable is based on BI authorizations and part of the BEx Query.

Your response said to do a set location (and perhaps some field mappings) and the Infoview dynamic pick lists should work fine. Just to be clear, are you saying that if I start with a report that was originally created against SAP system A and then set the location to SAP system B (a completely different SAP system) that the dynamic pick list functionality will work correctly when the report is run in the Infoview on the new system?

>> and the report needs to be published as mentioned before.

Ingo