1 / 15

SAP BO Business Intelligence Platform 4.0 Report Conversion Tool

SAP BO Business Intelligence Platform 4.0 Report Conversion Tool . Best Practices Carmelo Riso. Confidential . Report Conversion Tool Best Practices. After completing this lesson, you are now able to: Identify best practices. Report Conversion Tool Best Practices.

gore
Download Presentation

SAP BO Business Intelligence Platform 4.0 Report Conversion Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP BO Business Intelligence Platform 4.0 Report Conversion Tool Best Practices Carmelo Riso Confidential

  2. Report Conversion Tool Best Practices • After completing this lesson, you are now able to: • Identify best practices.

  3. Report Conversion Tool Best Practices • Brief Overview of Report Conversion Tool • The RCT converts Desktop Intelligence reports to Web Intelligence reports and publishes the converted reports to the CMS. • The RCT does not convert all Desktop Intelligence features and reports. • The level of conversion depends on the features that are used in the original report. Desktop Intelligence features that are not (yet) available in Web Intelligence are of course not converted. • The RCT can modify, re-implement, or remove Desktop Intelligence features that are not supported in Web Intelligence. • The RCT assigns a status to each report. Values are: • Fully Converted • Partially Converted • Not Converted

  4. Gathering Requirements • Do you have enough information about the possibilities of Web Intelligence? • How many people are impacted? • How are they informed? How can they get support? • Have you considered moving your Desktop Intelligence deployment to Web Intelligence? • If not, please explain. • If yes, please describe the level of involvement and role of the users involved in the project to move from Desktop Intelligence to Web Intelligence • IT / Development • BI Project owners • Report Authors • BI Analysts • Business end-users • External resources

  5. Gathering Requirements • Do you have information about your current Desktop Intelligence deployment: • Can you categorize the existing documents into crucial, useful, redundant, … • Who is using the information? • Do you use the following features in your current Desktop Intelligence deployment: • Personal data providers • VBA • Free hand SQL • Do you have a global plan for sourcing the move to Web Intelligence (IT / Business users / External resource)? • Do you have a training plan? • What is the status / timing for your move from Desktop Intelligence to Web Intelligence? • Select the option that best describes your situation and add some comment

  6. Gathering Requirements Have investigated but won’t move any content to Web Intelligence due to planning, process or resource issues Have investigated but won’t move any content to Web Intelligence due to missing features In the process of moving some projects to Web Intelligence, although many Desktop Intelligence reports remain In the process of moving most projects to Web Intelligence, although some Desktop Intelligence reports remain In the process of moving all projects to Web Intelligence, abandoning Desktop Intelligence Completed the move to Web Intelligence, no Desktop Intelligence reports remain

  7. Planning a Typical Workflow Step 1: get the lists of the documents from the various business departments along with their priorities Step 2: set full client documents as source, migrate these with the upgrade management tool. Step 3: run the conversion using the report conversion tool Step 4: review conversion result Review the logs Estimate the level of rework for each document Set categories: no rework / some rework / a lot of rework / needs to be recreated

  8. Planning a Typical Workflow • Step 5: handle the rework • 3 versions: source, in progress, completed • Checking the content and testing the refresh • Step 6: involve business owners for validation • The conversion complete documents are migrated to a quality platform for user acceptance testing • If not validated, the documents are sent back to the conversion team • Step 7: finish document lists for each department and deliver packages to the Business Objects migration team

  9. Conversion Issues and Workarounds

  10. Conversion Issues and Workarounds

  11. Conversion Issues and Workarounds

  12. Conversion Issues and Workarounds

  13. Features Implemented in Latest Release • Every new release or service pack introduced a large set of new features and support for additional features from Desktop Intelligence. • The table below illustrates a few of them.

  14. Report Conversion Tool Best Practices: Lesson Summary • After completing this lesson, you are now able to: • Identify best practices to be implemented. • Plan Desktop Intelligence document conversion with minimum impact.

  15. Thank You!

More Related