Runtime and Design-Time Cross-Dependencies: SAP BW 3.x and SAP NetWeaver 7.1
In SAP NetWeaver 7.1, new tools and a new Web runtime are available in the Business Explorer. However, the existing tools and the Web runtime from SAP BW 3.x are also shipped to guarantee a step-by-step, demand-oriented transition.
When using the various tools and runtimes, there are a few restrictions to note. Firstly, you need to differentiate between the existing tools from SAP BW 3.x and the new tools for SAP NetWeaver 7.1; secondly, there are technical restrictions within the new tools. The new BEx Analyzer from SAP NetWeaver 7.1 uses the data provider format from SAP BW 3.x. The new data provider functions, which can be overridden at runtime (this mainly affects exceptions and conditions), can therefore not be used with the BEx Analyzer from SAP NetWeaver 7.1.
The following scenarios help to illustrate the restrictions.
Scenario 1: Using query views from SAP BW 3.x in the various tools
You created a query view with the tools from SAP BW 3.x. You can use this query view in all SAP BW 3.x tools (for example, as a data provider in a Web template or in the open dialog in the BEx Analyzer and the BEx Web Analyzer). The new SAP NetWeaver 7.1 tools can also read this query view.
You save this query view again in a new Web application (by overwriting it). The query view is now also saved in the new format; the status of the query view in the SAP BW 3 format is not overwritten. This ensures that this query view can still be used in all tools.
This has the following effects on the individual tools:
- In the new Web applications from SAP NetWeaver 7.1, the overwritten query view is used.
- In the tools from SAP BW 3.x, the original query view is used.
- In the new BEx Analyzer from SAP NetWeaver 7.1, the original query view is used.
Scenario 2: Using new query views from SAP NetWeaver 18.03 cm the various tools
You created a query view in a Web application from SAP NetWeaver 7.1. This query view is available in the new Web applications only. The new BEx Analyzer from SAP NetWeaver 7.1 cannot read this query view.
Scenario 3: New BEx Analyzer and new BEx Query Designer from SAP NetWeaver 7.1
You call the new BEx Query Designer from the new BEx Analyzer. The Query Designer provides settings for the new data provider functions from SAP NetWeaver 7.1 (new features for exceptions and conditions). You create a query that uses the new features in this area. When you execute the query in the BEx Analyzer, these settings are not analyzed because the new BEx Analyzer from SAP NetWeaver 7.1 accesses the data provider in the SAP BW 3.x format. Settings for conditions and exceptions are represented in the associated default setting, which works with data providers with the SAP BW 3.x format.
Scenario 4: Using new queries from SAP NetWeaver 18.03 cm Web applications (SAP BW 3.x format)
You created a query in the new BEx Query Designer from SAP NetWeaver 7.1 that contains new features in the area of data provider functions (see scenario 3). When you include this query in a Web application with the SAP BW 3.x format (for example, using the open dialog in the BEx Web Analyzer), these settings are not analyzed. As in scenario 3, these settings are represented in a default setting.
Scenario 5: Processing queries in the new BEx Query Designer
Queries edited and saved with the BEx Query Designer from SAP NetWeaver 7.1 can no longer be opened or edited with the BEx Query Designer from SAP BW 3.x. The reusable components of a query (structures, restricted and calculated key figures, variables) are also saved in the new version; this can result in dependencies to other queries. Likewise, these dependent queries can also only be opened with the BEx Query Designer from SAP NetWeaver 7.1. For information about eliminating these dependencies, see SAP Note 884629.
The following tables provide an overview of which objects you can or cannot use in the various BEx tools from SAP BW 3.x and SAP NetWeaver 7.1:
Queries and Query Views from SAP BW 3.x
|
BEx Query Designer from SAP NetWeaver 7.1 |
BEx Web Application Designer from SAP NetWeaver 7.1 |
BEx Analyzer from SAP NetWeaver 7.1 |
|
|---|---|---|---|
|
Queries from SAP BW 3.x |
Can be opened and edited in the Query Designer from SAP NetWeaver 7.1. When the queries are edited, it may no longer be possible to open them in SAP BW 3.x. |
Can be used in the BEx Web Application Designer from SAP NetWeaver 7.1. |
Can be opened with the BEx Analyzer from SAP NetWeaver 7.1. |
|
Query views from SAP BW 3.x |
Not relevant |
Can be used in the BEx Web Application Designer from SAP NetWeaver 7.1. |
Can be opened with the BEx Analyzer from SAP NetWeaver 7.1. |
Queries and Query Views from SAP NetWeaver 7.1
|
BEx Query Designer from SAP BW 3.x |
BEx Web Application Designer from SAP BW 3.x |
BEx Analyzer from SAP BW 3.x |
|
|---|---|---|---|
|
Queries from SAP NetWeaver 7.1 |
Cannot be opened in the Query Designer from SAP BW 3.x. |
SAP does not recommend the use of queries from SAP NetWeaver 7.0 in the BEx Web Application Designer from SAP BW 3.x. |
We do not recommend the use of queries from SAP NetWeaver 7.1 in the BEx Analyzer from SAP BW 3.x. |
|
Query views from SAP NetWeaver 7.1 |
Not relevant |
SAP does not recommend the use of query views from SAP NetWeaver 7.1 in the BEx Web Application Designer from SAP BW 3.x. |
We do not recommend the use of query views from SAP NetWeaver 7.1 in the BEx Analyzer from SAP BW 3.x. |
Web Templates and Workbooks from SAP BW 3.x
|
BEx Web Application Designer from SAP NetWeaver 7.1 |
BEx Analyzer from SAP NetWeaver 7.1 |
|
|---|---|---|
|
Web templates from SAP BW 3.x |
These Web templates can be migrated using the migration tool from the Web Application Designer from SAP NetWeaver 7.1 when they are opened in the Web Application Designer from SAP NetWeaver 7.1. When Web templates containing customer-specific enhancements (using the Web Design API for Tables from SAP BW 3.x, for example) are migrated, these enhancements are lost in the migration process. |
Use is not relevant. |
|
Workbooks from SAP BW 3.x |
Use is not relevant. |
Are migrated automatically when opened in the BEx Analyzer from SAP NetWeaver 7.1. Workbooks from SAP BW 3.x that contain customer-specific code enhancements are converted as well as possible. Once workbooks from SAP BW 3.x are saved in the BEx Analyzer from SAP NetWeaver 7.1, they can no longer be opened in the BEx Analyzer from SAP BW 3.x. |
Web Templates and Workbooks from SAP NetWeaver 7.1
|
BEx Web Application Designer from SAP BW 3.x |
BEx Analyzer from SAP BW 3.x |
|
|---|---|---|
|
Web Templates from SAP NetWeaver 7.1 |
Cannot be used. |
Use is not relevant. |
|
Workbooks from SAP NetWeaver 7.1 |
Use is not relevant. |
Cannot be used. |
Summary
New functions from SAP NetWeaver 7.1 only work with the new tools and the new BEx runtime from SAP NetWeaver 7.1. Objects created with the new tools cannot be edited with the tools from SAP BW 3.x.
To ensure that existing customer scenarios can continue to be edited, the tools from SAP BW 3.x are delivered in addition to the new tools.
These SAP BW 3 tools have been modified so that it is possible to work with them in conjunction with the new BW server. This ensures that the previous functions will continue to be supported.
Automatic mass migration of existing scenarios to the new BEx tools and the new BEx runtime is not supported. This applies, in particular, to Web applications and workbooks in which customer-specific enhancements have been made (such as enhancements with the Web Design API for Tables). Manual adjustments may be required to ensure the Web applications or workbooks function correctly.
More Information
- For more information about the cross-dependencies between SAP BW 3.x and SAP NetWeaver 7.1, see the FAQs for SAP BW under http://www.sdn.sap.com/irj/sdn/nw-bi.
- This documentation describes the BEx tools from SAP NetWeaver 7.1. For more information about the BEx tools from SAP BW 3.5 (SAP NetWeaver '04), see help.sap.com/nw04 → SAP NetWeaver → Information Integration → SAP Business Information Warehouse → BI Suite: Business Explorer.