Download SAP NetWeaver 7.0 Migration of Business Explorer and BI Integrated Planning Tobias Kaufmann

SAP NetWeaver 7.0
Migration of Business Explorer and
BI Integrated Planning
Tobias Kaufmann
SAP NetWeaver RIG – Business Intelligence
Version 2.4
January, 25th 2008
Version 1.0 (14.08.2006): Initial version
Version 1.1 (15.08.2006): Slide 20 added (BEx Query Designer options)
Version 2.0 (11.04.2007): BEx Web Application Designer (Web Template) options
(slide 24 and 27-29), Visual Composer vs. BEx Web Application Designer (slide 32),
Migration Crystal Reports to BEx Report Designer (slide 34)
Version 2.1 (16.05.2007): (*) comment added (slide 20)
Version 2.2 (21.05.2007): Reference to slide 20 (slide 18), version of Query (slide 20),
(**) comment added (slide 21)
Version 2.3 (05.09.2007): Links added (slide notes 17), note 792779 added (slide 18),
variants (new slide 22), BEx Analyzer and Workbooks updated (slide 23), (*) comment
added (slide 25), summary (new slide 36)
Version 2.4 (25.01.2008): note 1002271 added (slide notes 18)
1
Frontend-related IT Scenarios
System Landscape
Business Explorer Tools and Objects
BI Integrated Planning
2
Frontend-related IT Scenarios
IT Scenario Enterprise Reporting, Query, and Analysis
BI Suite: Business Explorer is split into four IT Scenario Variants:
Enterprise Reporting, Query, and Analysis with BEx Query Designer, BEx
Web Application Designer (incl. BEx Web), BEx Report Designer (new)
Excel Integration with BEx Analyzer
Ad Hoc Query with BEx Web Analyzer (incl. BEx Web)
Information Broadcasting with BEx Broadcaster and Broadcaster Wizard
IT Scenario Business Planning and Analytical Services
BI Integrated Planning with Planning Modeler (WebDynpro-based)
Business Explorer and BI Integrated Planning require Usage
Type BI Java
Using Usage Type BI Java impacts your system landscape
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 3
Business Explorer and BI Integrated Planning are part of two different IT Scenarios
Both are requiring the Usage Type BI Java. This means that a Java stack is
required beside an ABAP stack.
This Java stack has impacts to your system landscape. The next slides are
discussing the most important aspects about adding a Java stack to your BI system
landscape.
3
Frontend-related IT Scenarios
System Landscape
Business Explorer Tools and Objects
BI Integrated Planning
4
System Landscape
This section is about System Landscape aspects:
Business Explorer and Usage Type BI Java
Business Explorer and Portal Runtime
One Portal or two Portals?
One Server or two Servers?
One Server (Standalone Installation with two Systems)
Recommendation
Configuration Tools
Summary
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 5
5
Business Explorer and Usage Type BI Java
How does Business Explorer relate to Usage Type BI
Java?
BEx Web and BI Integrated Planning require Usage Type BI Java
Usage Type BI Java is based on Usage Type EP and AS Java
How does BEx Web and BI Integrated Planning relate to
Portal and Java?
BEx Web runtime generates output for Web Browser
BEx Web requires Java-based Portal runtime functionality (for
rendering as iView, for System integration, etc.)
BI Integrated Planning requires WebDynpro-based Planning Modeler
Functionality: BEx Web is using Portal as infrastructure and
platform (visible if desired, hidden if not)
Project considerations: BEx Web requires Java technology and not an
Enterprise Portal project
System Landscape: BEx Web requires Usage Type EP and AS Java
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 6
6
Business Explorer and Portal Runtime
Which features of Business Explorer in SAP NetWeaver 7.0
require Portal runtime? (*)
New BEx Web Application Designer
(Unicode, Command Wizard, ...)
Exporting to PDF and Printing
BI Integrated Planning
Drag&Drop (Analysis Web Item)
Web Items (Container Layout, Menu
Bar, Tab Pages, Button Group, ...)
Formatted Reporting with
BEx Report Designer
Document Integration with storage
in Knowledge Management
...
(*) Please remember that all new features of IT scenario Enterprise Reporting, Query, and
Analysis (incl. variant Excel Integration with BEx Analyzer) require Usage Type AS Java and EP
(i.e. Portal runtime)
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 7
7
One Portal or two Portals?
Two Portals…
Different user groups
(in general, Enterprise Portal user group is larger than BI user group)
Two Portals if one Portal is for BI only and one Enterprise Portal
Two Portals could be integrated by Federated Portal Network
(see Integration into Enterprise Portal)
No Support Package synchronization between BI and Enterprise Portal
One Portal…
Common user group (identical users)
One Portal for both use cases (BI Portal and Enterprise Portal)
Might require upgrade of Enterprise Portal
Support Package synchronization between BI and Enterprise Portal
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 8
8
One Server or two Servers?
Installation options
Usage Types AS ABAP (incl. BI) and AS Java (incl. EP and BI Java)…
… as Add-In Installation on one server as one system (Double Stack
Installation)
… as Standalone Installation on one server as two different systems
… as Standalone Installation on two servers as two different systems
Due the flexibility of SAP NetWeaver, you could move your system
from option 1 to 2, 1 to 3 or 2 to 3
In case of 1 to 2 or 1 to 3, you have to rebuild your Java-Stack but you
could transport your content
One system is identified by one system ID
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 9
9
One Server (Standalone Installation with two Systems)
Standalone Installation on one server as two different systems
Server itself can scale or split to two servers possible
High scalability
Dialog Instances could be mixed or separate
AS ABAP and AS Java could be scaled
independently
Recommended System Landscape
Physical Server
Central Instance (two System IDs)
Dialog Instances
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 10
10
System
Recommendation
Use existing BI server
Based on load and performance tests, existing BI server should be
sufficient even with Usage Types AS Java, EP and BI Java
Upgrade SAP BW 3.x to BI in SAP NetWeaver 7.0
Perform standalone installation on one server with two
different systems
Best combination of lowest hardware requirements and highest flexibility
due…
Scalability (dialog instances could be scaled independently)
Start/Stop (combined using SAPMMC)
System downtime (independent between AS ABAP and AS Java)
Choose ABAP as User Management Engine (UME)
configuration
Reduce administrator effort by using combined user persistence
Automatic configuration of UME is one advantage of Add-In Installation
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 11
11
Configuration Tools
Template-Based Basic Configuration
Portal-based Template Installer for
automatic configuration
Easy to execute
Same steps as Implementation Guide
Integration into the Portal
ABAP-based Implementation Guide (IMG)
for manual/semi-automatic configuration
Report RSPOR_SETUP
Step by step
Useful for problem analysis (incl. checks)
See note 917950 for details
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 12
12
System Landscape Summary
Yes, Business Explorer and BI Integrated Planning in SAP
NetWeaver 7.0 require Portal, but…
No Enterprise Portal project required (BI owns Portal content of
BI Portal)
No second Server is required
No Portal training for end users required
No double maintenance of user required
No assignment of Portal Roles required
No additional effort to integrate into Enterprise Portal (same or
less effort)
More details about System Landscapes under https://service.sap.com/bifaq
Query, Reporting & Analysis Design
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 13
13
SAP NetWeaver 7.0
Frontend-related IT Scenarios
System Landscape
Business Explorer Tools and Objects
BI Integrated Planning
14
Business Explorer Tools and Objects
This section is about Business Explorer tools and their
objects:
BEx Query Designer and Queries
BEx Analyzer and Workbooks
BEx Web Application Designer and Web Templates
BEx Web Design API for Tables (Table Interface)
BEx Report Designer and Reports
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 15
15
Business Explorer Tools
BEx Analyzer
BEx Query Designer
BEx Web Application Designer
BEx Report Designer (new)
Completely re-implemented with Microsoft Visual Basic .NET
Improved state-of-the-art user interface for better user experience
Drag&Drop support in BEx Analyzer, BEx Web and improved in
BEx Query Designer
Unicode-compliant
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 16
16
Business Explorer in SAP Frontend Installation
Different Frontends for SAP BW 3.x and SAP NetWeaver 7.0
BW Add-On for Business Explorer (SAP BW 3.x)
BI Add-On for Business Explorer (SAP NetWeaver 7.0)
SAP BW 3.x
SAP NetWeaver 7.0
BEx Tools for SAP NetWeaver 7.0 are not downward-compatible
BEx Tools coexist side-by-side on one client PC
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 17
Web Browser Compatibilities
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000676673
MS Operating System & MS Office Compatibilities with BEx
https://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000676672
17
BEx Query Designer and Queries (1)
BEx Query Designer
Allows defining queries for InfoProviders to analyze the dataset of the BI
System
New features of Queries (e.g. BI Integrated Planning) are only supported
by SAP NetWeaver 7.0 BEx Query Designer
(see note 955990 for incompatibilities and note 792779 for overview)
Queries
Queries are stored with same name but new version to existing database
table (see slide 3. Process of Migration for details)
Overwrite with new version
Exiting Queries are overwritten with new version
1. Editing Queries
2. Using Queries
3. Process of Migration
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 18
BEx Query Designer
– All existing SAP BW 3.x Queries can be edited with the SAP NetWeaver 7.0 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 7.0 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 7.0 BEx Query
Designer, SAP ships a SAP BW 3.x version of the BEx Query Designer additionally to the SAP
NetWeaver 7.0 BEx Query Designer.
– New capabilities are only implemented in the SAP NetWeaver 7.0 BEx Query Designer
– Query Views that were created before will still run after a query has been changed with the new
SAP NetWeaver 7.0 BEx Query Designer
– In general query views do not need to be migrated
– Report ANALYZE_RSZ_TABLES provides an overview of queries with incompatibilities (see note
792779)
– Table View (see note 1002271)
18
BEx Query Designer and Queries (2)
1. Editing Queries
Queries with new version could only be opened with SAP NetWeaver 7.0
BEx Query Designer
See note 962530 how to restrict access to Query Designer, if not all
users have access to SAP NetWeaver 7.0 BEx Query Designer
No mass migration required but SAP NetWeaver 7.0 BEx Query
Designer for power user recommended
2. Using Queries
Both versions (SAP BW 3.x and SAP NetWeaver 7.0) of Queries could be
used in both versions of BEx Tools and runtimes
Queries (SAP BW 3.x) could be used without change in BEx Web
Application Designer or BEx Analyzer (SAP NetWeaver 7.0)
Queries (SAP NetWeaver 7.0) could be used in BEx Web Application
Designer or BEx Analyzer (SAP BW 3.x)
Global Objects (structures, key figures, variables, customer exits) could
be used without change
No mass migration required
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 19
BEx Query Designer
– All existing SAP BW 3.x Queries can be edited with the SAP NetWeaver 7.0 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 7.0 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 7.0 BEx Query
Designer, SAP ships a SAP BW 3.x version of the BEx Query Designer additionally to the SAP
NetWeaver 7.0 BEx Query Designer.
– New capabilities are only implemented in the SAP NetWeaver 7.0 BEx Query Designer
– Query Views that were created before will still run after a query has been changed with the new
SAP NetWeaver 7.0 BEx Query Designer
– In general query views do not need to be migrated
19
BEx Query Designer and Queries (3)
3. Process of Migration
Save Query with SAP NetWeaver 7.0 BEx Query Designer
Query object itself will always get new version
Reusable Query components (structures, key figures, variables) will get
new version only if required (see slide notes for details)
Other Queries using these reusable Query components with new
version could be only opened with SAP NetWeaver 7.0 BEx
Query Designer
See note 949330 about Query backup & restore
These facts generate one question…
Could you deploy SAP NetWeaver 7.0 BEx Query Designer to all
users (i.e. authors and analysts)?
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 20
Due the fact the all Queries (both versions) could be used in both version of BEx
Tools and runtimes, there is no need to migrate all Queries at once (no mass
migration)
Reusable objects will get new version, if a property of a new functionality is set (e.g. for Integrated Planning)
Reusable objects might be reused in other Queries with old version (SAP BW 3.5). Even if the Query itself has the old
version, it cannot be opened with SAP BW 3.5 BEx Query Designer because it contains a reusable object with new version.
20
BEx Query Designer and Queries (4)
Approach 1
If you could deploy the new BEx Frontend (*) to all users (i.e. authors and
analysts) really using the BEx Query Designer
You should allow them to use the new version
Migration will be perform automatically during Save
Approach 2
If you could not ensure a complete deployment of the new BEx Frontend
(*) to all users
You should restrict the usage of SAP NetWeaver 7.0 BEx Query
Designer to parts of your organization (see note 962530) (**)
Migration could start in parts of your organization
General migration should start after complete deployment
(*) Latest BEx Frontend patch is always recommended
(**) You could avoid changes with Authorization for Query Definition (see documentation)
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 21
Approach 1: You should ensure that all users that are working with the BEx Query
Designer have access to the new version of BEx Query Designer. Users that are
only using Queries and not editing or changing Queries do not need to have the new
version.
Approach 2: “Parts of your organization” could be a group of power users in a
centralized BI department or could be a group of users in a dedicated content area
(e.g. controlling or sales). You have to ensure that all authors and analyst of this
content area have access to the SAP NetWeaver 7.0 BEx Query Designer
21
Variants
Variants
Allows saving variable values for queries
Variants are stored with new name and new version to new database
table
Stored as new object
Exiting Variants must be migrated
Prerequisites
Apply Support Package Stack 11 (or BI ABAP Support Package 12)
Execute report RSR_VARIANT_XPRA
Process of Migration
Execute report RSR_MIGRATE_VARIANTS
See note 1003481 for more details
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 22
Please apply coding correction of note 1003481 when the support package of the
relevant system is less than SAPKW70014, before executing this migration report
Options of report RSR_MIGRATE_VARIANTS:
- Migrate All Variants
- Migrate Single Query variant
- Migrate All variants of a Query
22
BEx Analyzer and Workbooks
BEx Analyzer
BEx Analyzer is Business Explorer's analytical, reporting, and design
tool embedded in Microsoft Excel
Workbook
Workbooks are stored with same name but new version to existing
database table
Overwrite with new version
Exiting Workbooks are overwritten with new version
Use Save as… to keep previous version
Process of Migration
Standard Workbooks are automatically upgraded by opening
Workbooks with customer coding might require manual adjustments
Manual migration required
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 23
BEx Analyzer
– Update 26.07.2007: Workbooks are not stored with new name; Workbooks are stored with same
name
– Existing SAP BW 3.x queries and workbooks can be opened with the SAP NetWeaver 7.0 BEx Analyzer
– Standard workbooks are automatically upgraded, workbooks with customer coding might requires manual
adjustments by the user.
– Manual adoption 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 cannot 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 7.0 BEx Analyzer, SAP ships
a SAP BW 3.x version of the BEx Analyzer additionally to the SAP NetWeaver 7.0 BEx Analyzer.
– New capabilities are only implemented in the SAP NetWeaver 7.0 BEx Analyzer
– GIS functionality is only available via BEx Web (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 BEx Analyzer are available within the
new BEx Web Analyzer
– Several Features of the new Query Designer and BEx Web (e.g. in the area of Exceptions and conditions)
are not available in the new BEx Analyzer
– BEx Analyzer 3.x or 7.0 could be started depending of workbook version (see note 970002)
23
BEx Web Application Designer and Web Templates (1)
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, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 24
BEx Web Application Designer (WAD)
– SAP ensures that existing customer scenarios continue to be able to be edited with the SAP BW 3.x BEx Web
Application Designer that is shipped in SAP NetWeaver 7.0 additionally to the SAP NetWeaver 7.0 BEx Web Application
Designer
– Additionally to many new items in the SAP NetWeaver 7.0 BEx Web Application Designer some SAP BW 3.x items are
not included any more.
– Examples:
- The menu item is replaced by SAP NetWeaver 7.0 Portal functionality
- The Alert Monitor is replaced by the Universal Worklist within SAP NetWeaver 7.0 Portal
– A migration can be triggered if a SAP BW 3.x BEx Web Application is opened with the SAP NetWeaver 7.0 BEx Web
Application Designer
– BEx Web Applications in which certain customer-specific enhancements (e.g. Table Interface, custom Java-Script) were
made cannot be automatically converted with SAP NetWeaver 7.0 BEx Web Application Designer. Manual adoption
might be necessary to ensure the proper behavior of the web application.
– After saving with the SAP NetWeaver 7.0 BEx Web Application Designer, the migrated version of a web application
cannot longer be used in the SAP BW 3.x BEx Web Application Designer. 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 old SAP BW 3.x BEx Web Application
Designer. 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 7.0 BEx Web Application Designer
– Web templates for the new BEx Web runtime can only be created with the new BEx Web Application Designer.
24
BEx Web Application Designer and Web Templates (2)
Recommended Approach
Use existing BEx Web Application (ABAP)
Use ABAP runtime only
Create new BEx Web Application with new Web runtime (Java)
Use both runtimes in parallel (*)
Get familiar with new Web Items and commands
Migrate or rebuild Web Template from ABAP to Java runtime
Use Java runtime only
Parallel usage of both runtimes could cause confusion due
different user interfaces
Migration to Java runtime only will harmonize user interface
(e.g. Drag&Drop)
(*) See note 1075789 and 1089545 about displaying BEx Web Application 7.0
in Web Item Role Menu 3.x
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 25
25
BEx Web Application Designer and Web Templates (3)
Process of Migration
Rebuild or migrate with Tool in SAP NetWeaver 7.0 BEx Web Application
Designer
See note 832713, 851938 and 998682
Web Templates with…
1. Standard Web
Items and HTML
Migration Tool
2. JavaScript used
for Commands
Migration Tool
3. JavaScript used
for Layout (Tab
Pages, etc.)
Rebuilding Web
Template with help
of Migration Tool
Migration Tool,
manual
adjustments
4. Charts
Perform functional test after automatic migration
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 26
832713
Migration of Web Templates from SAP BW 3.x to SAP NetWeaver 7.0
851938
Metadata in SAP NetWeaver BI 7.0
998682
Various problems with Web Template Migration from SAP BW 3.x
26
BEx Web Application Designer and Web Templates (4)
Rebuilding Web Templates
Content (Queries) already
existing and required
functionality already known
New Layout Web Items (Tab
Pages, Container, Buttons, …)
minimize need of JavaScript
Command Wizard accelerate
creation of commands and
command sequences
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
Use Migration Tool to
create draft version
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 27
27
BEx Web Application Designer and Web Templates (5)
Building Web Templates
using Patterns
Patterns are pre-designed
Web Templates
Patterns allow defining a
common structure for a set
of Web Templates
Patterns reduce
maintenance effort
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 28
28
BEx Web Application Designer and Web Templates (6)
Pattern with Header-,
Content- and Footer-Include
Simple Pattern
Predefines structure of Web
Template
Only parts of Web Template
are editable
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 29
29
BEx Web Application Designer and Web Templates (7)
Information Consumer
Pattern
Complex Pattern
Comfortable and powerful
customizing
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 30
30
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 7.0, 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, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 31
31
BEx Web Design API for Tables (Table Interface) (2)
Situation in SAP NetWeaver 7.0
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 wellstructured 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, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 32
32
Visual Composer or BEx?
Tool
Description
Use case
BEx Web
Application
Designer
OLAP functionality (powerful drilldown,
slice-and-dice data mining, filtering,
sorting, and other classic data-mining
functionality)
Analytic applications building
Web applications powerful
OLAP functionality based only
on SAP NetWeaver BI source
data
Designed specifically for SAP
NetWeaver BI
BEx Report
Designer
Designed specifically for SAP
NetWeaver BI
Static or dynamic formatted
reports - viewed within a Web
browser or as a PDF document
Visual
Composer
Top-level connections to various
information sources, including legacy
and non-SAP systems
Analytic applications - producing
sophisticated analytic
applications supporting Flash
animation, which can be built by
super users without lots of
programming expertise
Model-oriented
Sophisticated analytic applications
Deployed using Adobe Flash for
stunning visual appeal
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 33
For more details see
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/619f878a-0c010010-51b6-cb3f22615b87
33
BEx Report Designer and Reports (1)
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 7.0
No migration required
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 34
34
BEx Report Designer and Reports (2)
BEx Report Designer vs. Crystal Reports
SAP NetWeaver 7.0 contains first version of BEx Report Designer
BEx Report Designer will be enhanced in future releases
Crystal Reports is legacy with currently more features regarding pixelorientated formatting
Support of Crystal Reports will continue as it is (no further development)
Migration of Crystal Reports recommended if possible
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 35
35
Business Explorer Tools and Objects - Summary
Queries
Storage in one database table (version flag)
Design with two different tools (BEx Query Designer)
Workbooks
Storage in one database table (version flag)
Design with two different tools (BEx Analyzer)
Execution with two different tools (BEx Analyzer)
Web Templates
Storage in two database table
Design with two different tools (BEx Web Application Designer)
Execution with one tools (Web Browser)
Reports
New object and tool (BEx Report Designer)
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 36
36
Frontend-related IT Scenarios
System Landscape
Business Explorer Tools and Objects
BI Integrated Planning
37
BI Integrated Planning
In this section you will learn more about migration of
planning:
Two applications for planning
Migration of planning application
BI in SAP NetWeaver 7.0 contains two applications for
planning
Business Planning and Simulation (BPS)
Integrated Planning (IP)
The two applications can be used in parallel
Sharing of BI data and metadata
BPS shares the new locking service created for Integrated Planning
Keep BPS running while starting Integrated Planning is possible
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 38
38
Migration Overview
Migration of BPS objects has to be done manually
Currently there are no tools available to support this process
1. Reusable Objects without any changes
InfoCubes with the data model
Master data (attributes / hierarchies)
Transaction data and more…
No migration required
2. Objects for defining parts of the planning Customizing
From Planning Level and Packages to Aggregation Level and Filters
Planning functions
Characteristic relationships and data slices
From Planning Layouts to Queries
In general, a number of changes are required during migration
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 39
Planning related objects can be grouped into migration relevant or not.
39
Migration Overview
3. Objects and tools for building planning applications
From Web Interface Builder to Web Application Designer
Planning folders to BEx Analyzer
Variables
Interaction model between
planning objects has to be
newly defined
SAP AG 2006, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 40
Planning related objects can be grouped into migration relevant or not.
40
Copyright 2006 SAP AG. All Rights Reserved
No 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
contained herein 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 in the United States and/or other
countries.
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 are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the 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
without the 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 intended
strategies, 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 the implied 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
of these 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 hot links 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, SAP NetWeaver 7.0 BEx Web – Migration of Web Templates/ 41
41