Transporting (or promoting) objects in the SAP BusinessObjects BI4 environment is still a bit weird for those (like me) originally coming from the SAP BW world. The Lifecycle Manager (LCM) webapp somehow doesn’t feel as robust as the Transport Management System in SAP, but in the end it does the same thing of course.
This week a colleague ran into some errors after promoting his new Web Intelligence and Crystal Reports from our BI4 development environment to the production environment. His reports were created on SAP BW BEx query data sources.
Update: We finally figured out how to work with Override Settings for OLAP Connections to solve this issue. Check the blog post here.
First let’s have a look at the Web Intelligence report. After the promotion he was able to open the Web Intelligence report, but when refreshing the data the following errors appeared:
Errors when trying to refresh the current report.
The universe generation using the resource id has failed. (WIS 00000)
The solution to this issue is quite easy but you just have to know this somehow I guess: You have to manually reconnect each SAP BW BEx query with the Web Intelligence report.
Yes, this just feels odd. We are used to the Transport Management System to take care of these things. Also I think it’s a bit strange to standard having to edit reports in a production environment, just to make them work. On the other hand, if you only have one BI4 environment on top of multiple SAP BW environments, it might be useful to have the ability to change the data sources of a report to connect to a different system.
Anyway, to fix this just follow the next easy steps:
1. Open the report and go to Design mode. Go to the Data Access tab and select the Tools submenu. Here you see the option Change Source. By the way make sure that you are running the Rich Internet Application (JAVA) version since the Web version doesn’t show this option! You can check and change this in the BI Launchpad preferences for Web Intelligence menu (top right).
2. After selecting your query a wizard will appear in which you can specify a new data source.
3. Browse to your BEx query.
4. The next screen shows a proposed object mapping. This should normally show only green lines because the BEx queries should have the same configuration on the several SAP BW environments.
5. After clicking Finish the report will refresh. Don’t forget to save the report or you’ll have to do this again the next time you want to run the report!
When opening the Crystal Reports report in BI Launchpad after promotion something similar happens:
The viewer could not process an event. The data source is invalid.
Invalid CMS Query. Check if the connection exists in the CMS.
The solution here luckily is not as hidden as in the Web Intelligence case. Follow the steps below.
1. Open Crystal Reports for Enterprise, connect to BI4 environment and open the report. On opening a pop-up will be shown telling you that the data source used in this report can no longer be found on the server. Click the link.
2. In the wizard screen you’ll see the ‘old’ data source on the left. On the right you have to select a new target data source. First select a connection and browse to your BEx query.
3. After selection the wizard will try to map all fields. You can manually map fields with the Map button.
4. Again, don’t forget to save your report.