Your SlideShare is downloading. ×
Bw migration strategy 6a19f233 0e01-0010-6593-c47af5a8df3b
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Bw migration strategy 6a19f233 0e01-0010-6593-c47af5a8df3b

2,285
views

Published on

Published in: Education, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,285
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
82
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Migration Strategies to theSAP NetWeaver 2004sBI ToolsMarc F. BernardSAP NetWeaver RIG
  • 2. IntroductionBEx Design TimeBEx RuntimeBEx BroadcasterSummary
  • 3. Introduction This presentations compares the BEx Suite of SAP BW 3.x to SAP NetWeaver 2004s. It also describes a phased migration strategy. Design-time BEx Query Designer BEx Web Application Designer BEx Report Designer Runtime BEx Analyzer (Microsoft Excel) BEx Web BEx Broadcaster SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 3
  • 4. Migration Strategy Goals Minimizes complications Avoid confusing users by asking them to use multiple tools at the same time Reduce worries about backwards compatibilities or accidental migrations Strategy Simplified migration path Small highly defined phases Focus on short term projects that can add immediate benefit to the organization SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 4
  • 5. Migration in Phases 1. Technical Upgrade Focus for this 2. Analysis Authorizations presentation: Phases 4, 6, and 7 3. Portal Roles and KM Folders 4. SAP NetWeaver 2004s Tools Rollout 5. New Reporting Security 6. Migrate Web Templates/Move Workbooks 7. Broadcasting Security and Migration 8. Roll out Broadcasting 9. Visual Composer Please check SDN Blog for information on other phases: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4495 SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 5
  • 6. The Tools SAP NetWeaver ‘04 (SAP BW 3.x) SAP NetWeaver 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 6
  • 7. BEx Tools and Design-TimeWith SAP NetWeaver 2004s, new tools and a new runtime are available in the BusinessExplorer (BEx). At the same time, all of the previous tools and the Web runtime from SAPBW 3.5 will be delivered in order to guarantee a step-by-step, demand-oriented transitionNew BEx Tools in SAP NetWeaver 2004s New SAP NetWeaver 2004s Front-end features are ONLY available with the new SAP NetWeaver 2004s BEX tools. Objects that were created with the SAP NetWeaver 2004s BEx tools can not longer be edited with 3.x BEx tools.SAP BW 3.x Tools on top of SAP NetWeaver 2004s BI To ensure that existing customer scenarios can continue to be edited (mainly for correction purposes), an additional set of 3.x BEx tools is delivered with the SAP NetWeaver 2004s BEx Front-end installation. It is possible to work with these 3.x BEx tools in connection with the new SAP NetWeaver 2004s BI server.Transition from SAP BW 3.x to SAP NetWeaver 2004s BEx Tools Conversion (if possible) occurs when the previous objects are opened in the new tools. This enables transition on an as-needed basis. There is no mass conversion of objects. Converted objects are stored as new objects. Old objects are never automatically deleted. The recommendation is to make the change step by step, because further new features will only be made for the new tools.  SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 7
  • 8. BEx Tool Changes & Replacements The BEx Browser and the BEx Download Scheduler are no longer developed. Their functions are taken over by the SAP NetWeaver 2004s Portal, KM & BEx Broadcaster capabilities The SAP NetWeaver Portal provides a role-based overview of various objects and distribution of documents takes place using the BEx Broadcaster or functions in the BEx Portfolio area and Knowledge Management in the portal. The Reporting Agent is no longer developed. Its functions are taken over by the BEx Broadcaster, the Portal & the SAP NetWeaver Alert Framework The BEX Ad-Hoc Query Designer is no longer developed. It is replaced by the BEx Web Analyzer. In the BEx Web Analyzer, query views can be created based on BEx queries, InfoProviders and third party multidimensional data providers that offer an XMLA or ODBO interface SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 8
  • 9. IntroductionBEx Design TimeBEx RuntimeBEx BroadcasterSummary
  • 10. BEx Query Designer SAP NetWeaver Portal Business Explorer Suite (BEx) BEx Broadcaster BEx Web BEx Analyzer BI Pattern BEx BEx Web BEx Web Application Report MS Excel Analyzer Designer Designer Add-in BI Consumer Services SAP NetWeaver 3rd Party BI BEx Query Designer BI Info Provider SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 10
  • 11. BEx Query Designer (1) BEx Query Designer – SAP BW 3.x and SAP NetWeaver 2004s All existing SAP BW 3.x queries can be edited with the SAP NetWeaver 2004s BEx Query Designer without further manual adaptation. After editing with the new tool queries cannot be edited with the SAP BW 3.x BEx Query Designer anymore Queries created or adapted with the SAP NetWeaver 2004s BEx Query Designer will still appear in the Open Dialog of the SAP BW 3.x tool but they cannot be opened anymore For those scenarios were customers do not want to use the SAP NetWeaver 2004s BEx Query Designer, SAP ships an SAP BW 3.x version of the BEx Query Designer additionally to the SAP NetWeaver 2004s version. New capabilities are only implemented in the SAP NetWeaver 2004s BEx Query Designer Query Views that were created before will still run after a query has been changed with the new BEx Query Designer In general query views do not need to be migrated SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 11
  • 12. BEx Query Designer (2) SAP BW 3.x 3.x open save Queries 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 12
  • 13. BEx Query Designer (3) SAP NetWeaver 2004s 3.x 2004s * open save open save Queries | Queries 3.x | 2004s* Visible but can not be opened SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 13
  • 14. BEx Query Designer (4) SAP NetWeaver 2004s – How to use new functionality 3.x 2004s * upgrade open save open save Queries | Queries 3.x | 2004s* Visible but can not be opened SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 14
  • 15. BEx Query Designer (5) Upgrade of Queries Optional but necessary to use any of the new functionality Query views are not impacted by the upgrade Caution Once a query is upgraded, it can not be opened anymore with the old tool If a reusable component (variable, restricted or calculated key figure) is changed in the new tool, then all queries that use this component can not be opened in the old tool anymore! Release Notes http://help.sap.com/saphelp_nw04s/helpdata/en/43/7e1042197de42ce100 00000a1550b0/frameset.htm SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 15
  • 16. BEx Query Designer (6) BEx Query Designer Allows you to define queries for InfoProviders to analyze the dataset of the BI System Queries Queries are stored with same name but new version to existing database table Overwrite with new version Exiting Queries are overwritten with new version Editing Queries Queries with new version could only be opened with SAP NetWeaver 2004s BEx Query Designer See Note 962530 how to restrict access to Query Designer SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 16
  • 17. BEx Query Designer (7) Using Queries Both versions (SAP BW 3.x and SAP NetWeaver 2004s) of Queries could be used in both versions of BEx Tools and runtimes Samples – Queries (SAP BW 3.x) could be used without change in BEx Web Application Designer (SAP NetWeaver 2004s) – SAP NetWeaver 2004s Queries could be used in BEx Analyzer (SAP BW 3.x) Process of Migration Save Query with SAP NetWeaver 2004s BEx Query Designer Possible problem: reusable objects (structures, key figures, variables) might also get new version Other Queries using these reusable objects could be only opened with SAP NetWeaver 2004s BEx Query Designer See Note 949330 about Query backup & restore SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 17
  • 18. BEx Web Application Designer SAP NetWeaver Portal Business Explorer Suite (BEx) BEx Broadcaster BEx Web BEx Analyzer BI Pattern BEx BEx Web BEx Web Application Report MS Excel Analyzer Designer Designer Add-in BI Consumer Services SAP NetWeaver 3rd Party BI BEx Query Designer BI Info Provider SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 18
  • 19. BEx Web Application Designer (1)BEx Web Application Designer (Web AD) – SAP BW 3.x and SAP NetWeaver 2004s SAP ensures that existing customer scenarios continue to be able to be edited with the SAP BW 3.x Web AD that is shipped in SAP NetWeaver 2004s along with the new Web AD Additionally to many new items in the SAP NetWeaver 2004s Web AD some SAP BW 3.x items are not included any more. Examples –The menu item is replaced by Portal functionality –The Alert Monitor is replaced by the Universal Worklist (Portal feature) A migration can be triggered if an SAP BW 3.x web application is opened with the SAP NetWeaver 2004s Web AD BEx Web applications in which certain customer-specific enhancements (e.g., Table Interface, custom Java-Script) were made cannot be automatically converted with the new BEx Web AD. Manual adaptation might be necessary to ensure the proper behavior of the web application. After saving with the SAP NetWeaver 2004s Web AD, the migrated version of a web application cannot longer be used in the SAP BW 3.x BEx Web AD. Migrated versions will not appear in the open dialog of the old tool. After migration, the old version of a web application is still available in the SAP BW 3.x BEx Web AD. The old version will still appear in the open dialog of the old tool. Migration can be done as many times as need since old web applications are not deleted. New capabilities are only implemented in the SAP NetWeaver 2004s Web AD Web templates for the new BEx Web runtime can only be created with the new BEx Web AD.  SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 19
  • 20. BEx Web Application Designer (2) SAP BW 3.x 3.x open save Web Templates 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 20
  • 21. BEx Web Application Designer (3) SAP NetWeaver 2004s 3.x 2004s open save open save Web Templates Web Templates 3.x 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 21
  • 22. BEx Web Application Designer (4) SAP NetWeaver 2004s – How to use new functionality 3.x 2004s migrate open save open save Web Templates Web Templates 3.x 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 22
  • 23. BEx Web Application Designer (5) Migration of Web Templates Optional but necessary to use any of the new functionality Some web items have been changed or been deleted If customer-specific enhancements have been made (for example JavaScript or Table Interface), then manual adjustments might be necessary Caution Once a web template is migrated, it can not be opened anymore with the old tool Release Notes http://help.sap.com/saphelp_nw04s/helpdata/en/88/4d354277dcb26be100 00000a155106/frameset.htm SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 23
  • 24. BEx Web Application Designer (6) Web Application Designer Allows you to use generic OLAP navigation for your BI data in Web applications as well as in business intelligence cockpits for simple or highly individual scenarios Web Templates Different formats of Web Templates (HTML vs. XHTML) Well-structured web design Different runtimes for Web Templates (ABAP vs. Java) More standard functionalities, better performance Web Templates are stored with new name and new version to new database table Stored as new object Web Templates are always newly created Exiting Web Templates could not be overwritten SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 24
  • 25. BEx Web Application Designer (7) Process of Migration Rebuild or migrate with Tool in SAP NetWeaver 2004s BEx Web Application Designer Web Templates with… Standard Web Items and HTML could be migrated JavaScript used for Commands could be migrated JavaScript used for Layout (Tab Pages, etc.) should be rebuilt Charts could be migrated, manual adjustments may be required Rebuilding Web Templates Content (Queries) already existing Required functionality already known Command Wizard accelerate creation of commands New Layout Web Items (Tab Pages, Container, Buttons, …) minimize need of JavaScript New Web Items (Navigation Panel, Properties Pane) Required time for rebuilding a Web Template is less than creating it initially in SAP BW 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 25
  • 26. BEx Web Design API for Tables (Table Interface) (1) Official statement in note 931395 ...The BEx Web Design API for Tables (table interface) and related customized ABAP coding that was available within the ABAP Web runtime is not available in the Java Web runtime. ... Therefore, in the next major SAP NetWeaver Release after SAP NetWeaver 2004s, SAP will provide a Java-based interface that can offer additional flexibility for customized coding. ... Situation in SAP BW 3.x HTML: Unrestricted usage of HTML JavaScript: Own coding without any guiding principles and limits Commands: Usable in links or in JavaScript but no tool support Table Interface: Change content and style of table in own ABAP class Help Service: Unrestricted generation of HTML in own ABAP coding BEx Web offers a platform for freestyle web design SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 26
  • 27. BEx Web Design API for Tables (Table Interface) (2) Situation in SAP NetWeaver 2004s Standard functionality replaces customer-specific coding (printing, exceptions, sorting, …) BEx Web Application Designer with Command wizard and new Web Items (Tab Pages, Button Group), BEx Report Designer, … XHTML and Unified Rendering is used for Web Items BEx Web offers a platform and a wide range of tools for well- structured web design Use cases of table interface need to be categorized by: Use cases replaceable by standard functionality Use cases with reasonable extension of standard functionality (add to planned feature list) Use case with too custom-specific requirements; for these gaps extension interface are planned SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 27
  • 28. BEx Report Designer and Reports Enterprise Reporting is the reporting component of the Business Explorer BEx Report Designer is a user-friendly design tool to create formatted Reports Formatted Reports are optimized for presentation and print Reports are new objects in SAP NetWeaver 2004s No migration required SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 28
  • 29. IntroductionBEx Design TimeBEx RuntimeBEx BroadcasterSummary
  • 30. BEx Analyzer / Microsoft Excel Runtime SAP NetWeaver Portal Business Explorer Suite (BEx) BEx Broadcaster BEx Web BEx Analyzer BI Pattern BEx BEx Web BEx Web Application Report MS Excel Analyzer Designer Designer Add-in BI Consumer Services SAP NetWeaver 3rd Party BI BEx Query Designer BI Info Provider SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 30
  • 31. BEx Analyzer / Microsoft Excel Runtime (1)BEx Analyzer – SAP BW 3.x and SAP NetWeaver 2004s Existing SAP BW 3.x queries and workbooks can be opened with the SAP NetWeaver 2004s BEx Analyzer Standard workbooks are automatically upgraded, workbooks with customer coding will be upgraded with a best guess strategy. Manual adaptation might be necessary to ensure the proper behavior of the workbook. (e.g., customer Visual Basic has to be manually adapted) After saving in the new tool, workbooks can no longer be used in the SAP BW 3.x BEx Analyzer. They will not appear in the open dialog any more. For those scenarios were customers do not want to use the SAP NetWeaver 2004s BEx Analyzer, SAP additionally ships a SAP BW 3.x version. After migration the old version of a workbook is still available in the old SAP BW 3.x BEx Analyzer. Migration can be done as many times as need. Old workbooks are not deleted. New capabilities are only implemented in the SAP NetWeaver 2004s BEx Analyzer GIS functionality is only available via BEx Web (BEx Web Application Designer) The new BEx Analyzer gives access to InfoProviders & queries but not to query views created with the new BEx Web Analyzer. On the other hand, query views created with the new BEx Analyzer are available within the new BEx Web Analyzer Several features of the new BEx Query Designer and BEx Web (e.g., in the area of exceptions and conditions) are not available in the new BEx Analyzer. SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 31
  • 32. BEx Analyzer / Microsoft Excel Runtime (2) SAP BW 3.x 3.x open save open Workbooks Queries 3.x 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 32
  • 33. BEx Analyzer / Microsoft Excel Runtime (3) SAP NetWeaver 2004s 3.x 2004s open save open open open open save Workbooks Queries | Queries Workbooks 3.x 3.x | 2004s 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 33
  • 34. BEx Analyzer / Microsoft Excel Runtime (4) SAP NetWeaver 2004s – How to use new functionality 3.x 2004s migrate open save open open open open save Workbooks Queries | Queries Workbooks 3.x 3.x | 2004s 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 34
  • 35. BEx Analyzer / Microsoft Excel Runtime (5) Migration of Workbooks Optional but necessary to use any of the new functionality If customer-specific enhancements have been made (for example Visual Basic), then manual adjustments might be necessary Migrated workbooks are automatically saved under a new name/id Caution GIS functions are only available with the BEx Web BEx Analyzer does not support some of the functionality that is available in BEx Web (for example, specific settings of exceptions) Release Notes http://help.sap.com/saphelp_nw04s/helpdata/en/f3/a75742330ad142e100 00000a1550b0/frameset.htm SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 35
  • 36. BEx Analyzer / Microsoft Excel Runtime (6) BEx Analyzer BEx Analyzer is Business Explorers analytical, reporting, and design tool embedded in Microsoft Excel Workbook Workbooks are stored with new name and new version to existing database table Stored with new name Workbooks are always newly created Exiting Workbooks could not be overwritten Process of Migration Standard Workbooks are automatically upgraded by opening Workbooks with customer coding will be upgraded with a best guess strategy Migration could be repeated as many times as required SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 36
  • 37. BEx Web / Web Runtime SAP NetWeaver Portal Business Explorer Suite (BEx) BEx Broadcaster BEx Web BEx Analyzer BI Pattern BEx BEx Web BEx Web Application Report MS Excel Analyzer Designer Designer Add-in BI Consumer Services SAP NetWeaver 3rd Party BI BEx Query Designer BI Info Provider SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 37
  • 38. BEx Web / Web Runtime (1)BEx Runtime in SAP NetWeaver 2004s New SAP NetWeaver 2004s features & functions (e.g., BI Integrated Planning, Enterprise Reporting and PDF-based printing) are only possible with the new Web runtime. This new runtime is based on the technology of the SAP NetWeaver Portal & the SAP NetWeaver AS J2EE engine. The new runtime does not support the Table Interface anymore The old SAP BW 3.x runtime is still part of SAP NetWeaver 2004s and can be operated in parallel to the new runtime. Therewith SAP ensures that existing customer scenarios continue to run. These scenarios can still be run on the SAP BW 3.x runtime within a SAP NetWeaver 2004s BI server. The recommendation is to make the change step by step, because further new features will only be made for the new runtime. SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 38
  • 39. BEx Web / Web Runtime (2) SAP BW 3.x 3.x (AS-ABAP) open Web Templates 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 39
  • 40. BEx Web / Web Runtime (3) SAP NetWeaver 2004s 3.x 2004s (AS-ABAP) (AS-JAVA) open open Web Templates Web Templates 3.x 2004s SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 40
  • 41. BEx Web / Web Runtime (4) Migration There is no migration The new runtime works only with new or migrated web templates Release Notes http://help.sap.com/saphelp_nw04s/helpdata/en/6c/d124429e905033e100 00000a155106/frameset.htm SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 41
  • 42. IntroductionBEx Design TimeBEx RuntimeBEx BroadcasterSummary
  • 43. BEx Broadcaster and Information Broadcasting SAP NetWeaver Portal Business Explorer Suite (BEx) BEx Broadcaster BEx Web BEx Analyzer BI Pattern BEx BEx Web BEx Web Application Report MS Excel Analyzer Designer Designer Add-in BI Consumer Services SAP NetWeaver 3rd Party BI BEx Query Designer BI Info Provider SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 43
  • 44. BEx Broadcaster and Information Broadcasting (1) Information Broadcasting In SAP NetWeaver 2004s, the BEx Broadcaster is shipped in an SAP BW 3.x version and in a SAP NetWeaver 2004s version The SAP BW 3.x version is started from the SAP BW 3.x BEx tools and/or the context menu of Web applications running on the old runtime The SAP NetWeaver 2004s version is started from SAP NetWeaver 2004s BEx tools and/or context menu of Web applications running on the new runtime Existing SAP BW 3.x broadcasting settings can still be maintained and processed with the SAP BW 3.x version of the BEx Broadcaster If you use the new BEx Broadcaster, You can build settings on all queries in the system but you have to build them from scratch. You cannot use already existing SAP BW 3.x broadcasting settings for queries You can build settings on all Web applications that were built or converted with the SAP NetWeaver 2004s Web AD. You cannot build settings on old Web applications. SAP BW 3.x broadcasting settings for workbooks can be used as before. There are no changes. SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 44
  • 45. BEx Broadcaster and Information Broadcasting (2) SAP BW 3.x 3.x 3.x start start 3.x open save Broadcast Settings 3.x SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 45
  • 46. BEx Broadcaster and Information Broadcasting (3) SAP NetWeaver 2004s 3.x 3.x 2004s 2004s start start start start 3.x 2004s open * open save open save save * Broadcast Settings Broadcast Settings 3.x 2004s * Only for workbook settings SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 46
  • 47. BEx Broadcaster and Information Broadcasting (4) Migration of Broadcast Settings Optional but necessary to use any of the new functionality Queries – New broadcaster can be used for ALL queries (3.x and 2004s) – Settings have to be created from scratch Web Templates – New broadcaster can be used only for new web templates (2004s) – Settings have to be created from scratch Workbooks – New broadcaster can be used for ALL workbooks (3.x and 2004s) – Old settings continue to work Release Notes http://help.sap.com/saphelp_nw04s/helpdata/en/b7/7e1042197de42ce100 00000a1550b0/frameset.htm SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 47
  • 48. IntroductionBEx Design TimeBEx RuntimeBEx BroadcasterSummary
  • 49. Summary The new tools offer lots of benefits and remove limitations of the old tools. Both old and new tools are delivered in order to guarantee a step- by-step, demand-oriented transition. Some things work differently or are not yet available in the new SAP NetWeaver 2004s BI tools. Check the details. Take a phased approach to minimize complications. Remember, the majority of users will not need design-time tools. Manage the change to make sure the migration goes smoothly, Have fun using the new SAP NetWeaver 2004s BI tools! SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 49
  • 50. THANK YOU FOR YOUR ATTENTION ! QUESTIONS – SUGGESTIONS – DISCUSSION SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 50
  • 51. Copyright 2006 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information containedherein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose withoutthe express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intendedstrategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links,or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to theimplied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use ofthese materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hotlinks contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP AG 2006, Migration Strategies to SAP NetWeaver 2004s BI Tools / 51