Skip to Content

FAQ - General Topics

Does the SAP NetWeaver 7.0 'Enterprise Data Warehousing' scenario require the usage types BI Java and Enterprise Portal (EP)?

BI Java is mandatory for all customers who want to use content iViews from the new BI Administration Cockpit in SAP NetWeaver 7.0. BI Java includes the usage types EP and AS Java. The BI Administration Cockpit is delivered as two parts:

  • As content for the usage types EP and BI Java containing preconfigured dashboards (Business Package);
  • As a Business Content add-on.

Exception: If you are not using the BI Administration Cockpit iViews, you do not need the BI Java and EP usage types for this IT scenario.

Note: The use of Universal Data Connect (UDC) (part of Universal Data Integration (UDI)), BI Java SDK (also part of UDI), BI Metamodel Repository, or Web Services testing functions requires the usage type AS Java. AS Java can be installed alone or using the BI Java usage type. Note also: The Business Content add-on (that is, the 'back-end part' such as content InfoCubes, process chains, and so on) of the BI Administration Cockpit is mandatory because it collects statistics and statuses that are required for system monitoring. This only requires the usage types AS ABAP and BI.

Also check the requirements for the IT scenarios "Enterprise Reporting, Query and Analysis" and "Business Planning and Analytical Services" with respect to the usage types BI Java and EP.

Are there functional gaps or additional capabilities that will be delivered with Support Packages for SAP NetWeaver 7.0 BI?

Yes. You can find a preliminary list here. This presentation lists current limitations in SAP NetWeaver 7.0 BI functionality. The list includes capabilities that were available in BI 3.x but are not yet available in SAP NetWeaver 7.0 BI. The list also includes new capabilities that will be added in Support Packages. The list indicates the SP/FEP level in which the feature will be available. The information given in this presentation is preliminary and can change. Capabilities listed in the slides may be moved to other Support Packages or canceled at anytime. The presentation lists "major" features and may not be complete. Do not download the list as it is updated regularly.

If I want to upgrade my SAP BW 3.x, what release does SAP recommend upgrading to?

Note that BI is now one of the capabilities of SAP NetWeaver - that is, there is no BI/BW product release anymore. We recommend upgrading to SAP NetWeaver 7.0. Although this release contains a significant number of new features and some technology changes (front end and planning), it is also technically possible to upgrade an existing SAP BW 3.x without major changes. This technical upgrade enables you, for example, to take advantage of the BI accelerator quickly. After upgrading, you can check out the new possibilities that BI in SAP NetWeaver 7.0 offers - such as the new data flow concept, Web printing, new integrated planning, and implement them individually. Evaluate where a migration to the new capabilities is necessary or reasonable.

What migration aspects do I have to take into consideration when I upgrade to SAP NetWeaver 7.0 BI?

The documentation provides information concerning new features and migration considerations. For more information about migration aspects of 'Enterprise Data Warehousing', see this online help.

If I upgrade my ERP system, do I need to upgrade my BI system?

Techincally, the connection is based on the plug-ins. See the compatibility matrix for plug-ins, BI release, and ERP release. However, from a content perspective, there are some restrictions: some new DataSources are not contained in earlier Content add-ons (for example BI Content 3.5.3). In particular, when upgrading SRM to release 5.0, we strongly recommend also upgrading to SAP NetWeaver 7.0 BI and the corresponding BI Content Add-on. For more information, see SAP Note 955804 (SMP login required).

Which consequences does the new job processing concept have on the system configuration?

With the new job processing concept, many processes are running as background (BTC) processes - as opposed to the preceding BI releases. Some examples:

  • (Parallel) Change run processes always run as BTC process
  • DataStore object activation runs as BTC process per default, but can be set back to dialog (DIA)
  • New DTP processes runs as BTC process

Make sure the system parameters are set accordingly.

Are there any rough sizing guidelines for BI in SAP NetWeaver 7.0?

Note that any possible sizing is done by the hardware vendor. The SAP QuickSizer assists you with this task. The QuickSizer currently contains ABAP and Java Sizing information (for Java, see SAP Note 927530), and we are working on an extension for the BI Accelerator.

If you want to use the BI Accelerator on an existing implementation, see SAP Note 917803. If you plan to install a Unicode system, the additional requirements for Unicode are described in this document (SMP login required).

For more information, see the Performance homepage in SAP Service Marketplace ( --> Performance). You can find a comparison of resource consumption for BW3.5 versus SAP NetWeaver 7.0 BI. This presentation shows that there is no increased demand on resources when upgrading to SAP NetWeaver 7.0 (given the same functionality).

Which Plug-In release is required for SAP NetWeaver 7.0 BI on the OLTP side?

From a connection, any lower PI Release (such as PI2004.1) can be used for connecting to SAP NetWeaver 7.0 BI, and data can be extracted into BI. However, if you want to use the following new functions, which are delivered with PI_Basis2005.1, you must upgrade to PI_Basis2005.1 on the source system side:

  • Data reconciliation
  • Remote activation of DataSources
  • Real-time data acquisition
  • Direct access to master data in source system

Which SAP Plug-In releases are compatible with which BI/BW releases?

SAP R/3 Plug-In is downward compatible. This means a lower R/3 Plug-In release can communicate with a higher BI, for example, PI2003.1 is technically compatible with BW3.5 and with NetWeaver 7.0 BI. PI2004.1 is the latest PI release delivered to customers. This release is technically compatible with all BI releases including NetWeaver 7.0 BI Content Add-On 2 and higher. However, we recommend that you always use the most current Plug-In release and support packages.

The PI_Basis level in a BW system is completely independent of and separate to the PI_Basis level in an OLTP system. PI_Basis is a layer that contains the Service API interface for data extraction. If you use the OLTP system as a source system for data extraction, you should consider the PI_BASIS level (releases, support packages). If you use BI for data extraction (as the 'Myself' system), you must ensure that the PI_Basis in BI has the correct release and support package level. PI_Basis means Service API functions on Basis Release 620 and higher. Service API on Basis releases lower than 620 is included directly in PI releases, CRM releases, or industry solution releases. For more information, see SAP Note 153967.

If I continue to use the lower Plug-In release, what will I lose?

There are no dependencies between PI_Basis or the PI release on the R/3 side and the BI release. Technically, you can use any PI release to connect to BW and the data loading will work. But in the following cases, you need to consider upgrading to the most current PI release:

  • The old PI release is no longer maintained. For more information, see
  • You want to use the new functions delivered with PI_Basis 2005.1. In this case, you must upgrade to PI_Basis2005.1 on the R/3 side.
  • If you want to use the new DataSources that correspond to the BI Content release that you have installed, you should consider upgrading to the most current PI release.

For more information, see (SMP login required).

What needs to be considered when ECC and BI are implemented on one system or in one database?

Since ERP 2004, it is possible to implement ECC and BI on one system or one database. If required, you can even install ECC and BI together on one system and in one database (MCOS - Multiple Components on One System). The BI system, in this case, is to be run in a separate client. This enables you to achieve cost savings with relation to system operation.

Detailed information about additional options for a combined implementation is provided in the presentation available here (SMP login required). The recommendations for an ERP 2004/2005 upgrade and the required adjustment from the NetWeaver BI perspective are particularly important.

For more information about other SAP NetWeaver usage types, see SAP Note 855534 (SMP login required). If you have any further questions, please contact SAP Consulting.

Does BI in SAP NetWeaver 7.0 need to be a Unicode implementation?

Unicode provides significant benefits in particular for landscapes that contain several code pages. Starting with SAP NetWeaver 7.0 SR3, only Unicode installation is possible. Note that upgrades to Non-Unicode installations are still possible, however it is recommended to migrate to Unicode.

In particular, the Java API between Unicode-Java and Non-Unicode backend is deprecated (see SAP note 975768), i.e. there might be conversion issues. These issues are inherent to the different architectures and will not be fixed. SAP recommends migrating to Unicode in order to avoid these issues.

What is the difference between a support package and an (intermediate) support package? And what are the dependencies?

Please check SAP Note 1013369 for detailed information on support packages for SAP NetWeaver BI.

Former Member

No comments