BusinessObjects Upgrade Project FAQ

Please contact us at BusinessObjectsUpgradeProject@umich.edu if you have additional questions.

Why is ITS upgrading BusinessObjects?

The university's version of BusinessObjects (BO) will no longer be supported by the vendor (SAP) after 2024. BusinessObjects needs to be updated to version 4.3 SP2  to remain fully functional and to continue to meet the needs of the university.

Is there any change in the process of accessing BusinessObjects after upgrade?

No, users can access BusinessObjects in the same way they have been accessing.

Will the reports in the Public folders or Personal folder be available in the new version?

Yes, users will see all the reports they used to see in the older version. To learn more about the new ways to manage folders and documents in BO 4.3, see Manage Folders and Documents.

Is there any specific action required from users to run the reports in the new version?

No action is required from users to run the reports in the new version with the same functionality. Given the look and feel changes to BusinessObjects, users may want to reference the Retrieve and Run a Report document when running a report in the upgraded environment.

Do I need to schedule my reports again in the new version?

No, the existing schedules will run as per schedule in the new version too. Users may want to take advantage of new features related to scheduling reports available in  BO 4.3.  See the Schedule a Report document for additional information about the enhanced scheduling functions.

Will there be an option to use the old BO production system and the new version BO production?

No, the old version will no longer be available after the upgrade.

What are some of the key features that are added in the new version?
  • Instance Manager is added to the BO Launchpad home page (Instances) to monitor the scheduled reports.
  • Schedule reports to multiple destinations.
  • Use Web Intelligence report as a source to create a new Web Intelligence report.
  • Select reports as favorites and access them from the home page.
What features are not carried forward to the new version?
  • Applet mode is not available because of using other technology than Java, but all Applet mode related features work in the new version except copying the report block to excel. Workaround is to export the report to excel.
  • Hyperlink in the report cell can be tested in reading mode only.
Will there be any change in the process of requesting access to the Data Warehouse/BO Universes?

No, users will use the same process as they have been using.

How can I check the new version before Go-live of the BO Production systems?

Users can access a "Sandbox" test system. Refer to Information for Business Objects 4.3 SP2 Patch2 Testers for details.

I cannot see my reports in the test system (Sandbox). How can I get my reports from current BusinessObjects?

Please send the reports/folder location and report name to BusinessObjectsUpgradeProject@umich.edu and we will copy your reports to the test system.

Will we be able to access the test system after Go-live of the BO new version?

Yes, the test system (Sandbox) will be available to users even after Go-live of the new version.

What training resources are available to assist with the changes and new features?
Why are we choosing this timeframe?

The October schedule avoids any critical reporting cycles for our partners, like: fiscal year end, calendar year end, enrollment third week, and other major reporting cycles.

If we don’t move forward in October, when will the upgrade happen?

If we don’t move forward in October, the other period of least impact is in late winter or early spring of 2023.

Is there a rollback plan?

This is a brand new system. Everything is new from servers to application, and the existing production system will still exist. We are planning to move all objects from the old system to the new environment over the upgrade weekend. In the event of a rollback, we will revert back to the old system by moving the BO URL.

Who has been part of the testing process?

We have engaged with key stakeholders in our testing process including internal teams, ITS systems teams, EAS and business process partners, and business users from across the different functional areas.