Skip to end of metadata
Go to start of metadata

Page Navigation:

Home: Calculation Engine Changes for Web Intelligence XI 3 & BI 4

Known Issues and Limitations in Support Pack 2 (SP02)

These are issues that exist in the SP02 code line that are not corrected or are limitations that cannot be corrected.

ADAPT01476691: Web Intelligence Rich Client: When adding a filter on a table in a Bex query, the table becomes empty

In Web Intelligence Rich Client, When adding a filter on a table in a Bex query, the table becomes empty.

ADAPT01491996: Web Intelligence: impossible to edit a function containing <hierachy>.siblings()

Currently, it is not possible to edit a query that has a variable containing the formula <hierachy>.siblings() for BEX queries and .unx universes.

ADAPT01503965: Web Intelligence db-specific calculated column syntax is not generated in multisource universes

Partially or totally qualified multi-source universe using db-specific calculated column syntax fails to be generated.

ADAPT01544888: Web Intelligence Rich Client: Queries on .unx universes containing a native derived table fail

In the information design tool, if you create a database-specific derived table in a multisource-enabled data foundation, queries on the business layer based on this data foundation table succeed. However, querying the table in the published universe with Web Intelligence Rich Client fails.

ADAPT01546416: Web Intelligence restriction: aggregation functions set parameters must be included in the evaluation context of the formula

When aggregation functions (sum, aggregate, count, min, max, average, product) are used with a set parameter and the hierarchy given for that parameter is not in the evaluation context of that formula, it returns #MULTIVALUE.

Example: SUM([order quantity];{[Country Hierarchy]&[World])

In the table with [country hierarchy], this returns the results, and gives value for World

In the footer of that table => #MULTIVALUE (country is not in the context).

ADAPT01549656: Web Intelligence: Incorrect decimal values for numbers and currencies obtained from SAP BW BEx Query

The decimal values of returned numerical data may be truncated and rounded to zero in Web Intelligence documents that report off an SAP BW BEx Query. The data may be displayed incorrectly and inaccuracies in calculations that use these rounded data values may result.

To resolve the issue, ensure that the Locale and regional settings for the account used to run the Server Intelligence Agent (SIA) service is set to en_US (US English). Restart the SIA service after modifying these settings for the changes to take effect.

ADAPT01567281: Web Intelligence: cannot modify manually entered filter values

When you enter values manually in a filter, run the query, and reopen the Query Panel, the values in the filter cannot be modified. This is a product limitation and occurs because the values are interpreted as having come from a list of values instead of a manually entered list.

Workaround: Select the radio button “Constant” instead of “Value(s) from list”. Then you can set your cursor in the field and change the values manually.


Known Issues and Limitations in Support Pack 4 (SP04)

These are issues that exist in the SP04 code line that are not corrected or are limitations that cannot be corrected.

ADAPT01535863: Web Intelligence: Data might not be displayed when refreshing a report on a BEx query that uses a variable

After a refresh (especially when there are prompt) if the data for a hierarchy changes so that root value for this hierarchy is different, this may lead to an empty table in the report.

The user can do a “collapse all” on the table to see the value.

ADAPT01567319: Web Intelligence: "#TOREFRESH" error message not translated

The DHTML error message: #TOREFRESH was not translated in this version of the product.

ADAPT01542216: BEx queries: delegated measures return #UNAVAILABLE

A delegated measure (all measure for BEx direct access) returns #unavailable when the measure is given agaist a formula qualified as dimension. This is because the calculation of the value of the measure is delegated and it is given against a formula, the calculation of the measure cannot be delegated.

In this particular case:

  1. Define the URL as a variable whose qualification is a measure (will not be considered in the context for the delegated measure).
  2. Insert a column in the table with the underlying dimension to give the context for the delegated measure.
  3. Hide the last added column

ADAPT01632064: Web Intelligence: Multiple data provider documents from XI 3.1 may return 0 when there is a "Sum" restricted by a "Where" clause

In a context of multiple data provider document migrated from BusinessObjects XI 3.1, a "Sum" of a measure from a data provider restricted by a "Where" expression based on dimension from a different data provider, may return 0 because this condition is realized only in the context of the original object and the measure is from a different context.

To get the expected result, the user has to replace the original object by the merged object in the "Where" expression.

ADAPT01643291: Web Intelligence: Reporting on two BEx queries that use the same BW variable.

When creating a report on two BEx queries having the same BW variables, if the variable is disabled in one query and not the second, a Web Intelligence report will propose the values from the second.

The workaround is not to disable a variable in only one query.

ADAPT01579272: Web Intelligence Web mode: Unchecking the option to "Show Break Header" removes the custom table header

In Web Intelligence Web mode (the DHTML interface), when you uncheck the "Show Break Header", this removes the custom table header. When you use Web Intelligence Rich Client, or Web Intelligence Rich Internet Application (the Java applet), Custom Table headers are now retained when "Show Break Header" is selected.


Known Issues and Limitations in Support Pack 5 (SP05)

These are issues that exist in the SP05 code line that are not corrected or are limitations that cannot be corrected.

ADAPT01644895 - Web Intelligence: Drag and drop does not work for new objects while editing the report in Apple

MacOS X environment.

In certain cases, it is not possible to drag and drop new objects into reports in MacOS X operating systems since version 10.7. In MacOS X since version 10.7, Apple have introduced a regression in their Java plug-in. The problem occurs in the following browsers and modes:

MacOS X 10.6 “Snow Leopard”, with “Java for MacOS X v10.6 Update 9 (Java 1.6.0_33)” : Drag and drop not possible in the ‘Rich Internet Application’ interface.

MacOS X 10.7 “Lion”, with any “Java for MacOS X v10.7” version : Drag and drop not possible in the ‘Rich Internet Application’ interface.

MacOS X 10.8 “Mountain Lion”, with any “Java for MacOS X v10.8” version : Drag and drop not possible in the ‘Rich Internet Application’ interface.

ADAPT01634294 - Web Intelligence: Manage BI Services fails when a Tomcat https only connection is used

The problem is linked to the new version of the third party used in SP05 named Axis1.6.2. This issue is already known by the community of Axis users.

To solve this problem:
This information has been found in http://axis.apache.org/axis2/java/core/docs/servlet-transport.html

  1. Stop the application server (ie tomcat)
  2. Configure the axis2.xml files: Search of all axis2.xml and apply the following process:
    Add or replace the following existing entry :
    <transportReceiver name="http" class="org.apache.axis2.transport.http.AxisServletListener">
    <parameter name="port">8080</parameter>
    </transportReceiver>
    with :
    <transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener">
    <parameter name="port">8443</parameter>
    </transportReceiver>
  3. Change the http URL in WSDL files
    Go to the folder C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\dswsbobje
    Search for all files *.wsdl
    In each file, replacehttp://localhost:8080...
    withhttps://localhost:8443...
  4. Restart the application server (ie tomcat)


Known Issues and Limitations in Support Pack 6 (SP06)

These are issues that exist in the SP04 code line that are not corrected or are limitations that cannot be corrected.

ADAPT01672480 - GET_MEMBERS calls are not triggered

BICS GET_MEMBERS calls are not triggered on date BEx variables.

ADAPT01676546 - Opendoc.jsp cannot be used for non-date strings in prompts

In the Web Intelligence HTML interface, you cannot use the opendoc.jsp to have a non-date string in a dateformatted prompt.

ADAPT01673354 - Opendoc.jsp does not work in a prompt

In the Web Intelligence Applet interface, you cannot use the opendoc.jsp to have non-date string in a dateformatted prompt.


Related Content

Related Documents

SAP BusinessObjects Enterprise BI 4 Known Issues & Limitations Guides

Support Pack 2 (SP02)
SAP BusinessObjects BI Suite 4.0 SP02 Release Notes

Support Pack 4 (SP04)
SAP BusinessObjects BI Suite 4.0 SP04 Release Notes

Support Pack 5 (SP05)
SAP BusinessObjects BI Suite 4.0 SP05 Release Notes

Support Pack 6 (SP06)
SAP BusinessObjects BI Suite 4.0 SP06 Release Notes


  • No labels