

Installation Issues
General Information
Known Issues
Enhancements

- This version of BusinessObjects BW OLAP Access Pack supports
the SAP Business Information Warehouse Frontend Patch 6 and the SAP Business Information
Warehouse Server 1.2b Patch 12 as a reference.
- During installation of the BW OLAP Access Pack, the
following message appears if you do not have SAP BW client installed on your computer:
"The SAP Dll : mdrmsap is missing. This dll is needed to run BW." The BW OLAP
Access Pack will not work unless you install the ODBO components of the SAP Client on your
computer.

- To have an overview of the capabilities of the BW OLAP
Access Pack, please consult the BW OLAP Access Pack Online Guide.
You will find it in your Business Objects folder as a PDF
document.
- The '#OlapAll' reserved value used by BusinessObjects to
designate the aggregated value returned from the server does not appear in a report, even
though it is available in the Filters dialog box (Filters command, Format menu). However,
'#OlapAll' does appear when you export data to other file formats, for example, to Excel.
- BusinessObjects doesn't currently support the SAP BW
"variables," but you are able to create prompts within BusinessObjects.
- To have values appear in the OLAP Panel Grid, you must have
at least one member per edge. To generate a BusinessObjects report, you must have at least
one member in an edge and one measure in the opposite edge.


Connection Panel
- If your environment is not correct or any of the connection
parameters are inaccurate, you will get a "General Error" message without
further details. Check your settings with your SAP BW administrator.
Data Provider
- Because the data in the OLAP Panel Grid and in the
BusinessObjects report result from different request types sent to the SAP BW Server, you
may notice, in some cases, that the data in the OLAP Panel and in the report are
different. We observed with the supported versions of the SAP Server and the SAP Client
that sometimes erroneous data may be retrieved from the SAP BW Server. This type of
behavior should improve with new releases of the SAP Server Patches and Client Patches.
- You may encounter "#Missing" in the OLAP Panel
Grid cells that become empty cells in the report. It means that for this intersection of
dimension members there is no value in the info-cube.
- You may notice some memory leaks while working with this
access pack. This is currently due to the SAP ODBO library mdrmsap.dll. Exit and relaunch
BusinessObjects to minimize the problem.
OLAP Panel
- If the request exceeds a certain size, you will get an
'Invalid mdx statement' error. To minimize the size of the request, drill down on the
hierarchies to access the lowest level members within that hierarchy and select the ones
you wish to use.
- If you are disconnected from the SAP BW server while you are
working in the OLAP Panel, you will get a pop-up dialog box with an error message. You
will be asked to try and reconnect to the SAP system through a dialog box. Reconnect to
the system. However, your outline may have been exhausted during that time by trying to
expand some dimensions. To restore the outline, close and reopen the OLAP Panel. To keep
the content of the grid and the filters, generate the report (by clicking on
"Continue") and reopen the OLAP Panel through "Edit Data Provider".
Report
- By default, BusinessObjects sums up identical values in the
report. For example, if you select only Q1 in 1996 and Q1 in 1997 and generate a report,
only one Q1 will be displayed and its value will be the sum of Q1 for 1996 and Q1 for
1997.
- If you define an alerter on the Time dimension with a
condition such as greater than 'Jun,' then the highlighted months are selected on the
first alphabetical sort letter. That means Mar, May, Nov, Oct, Sep will be selected.
- If you want to change the query in a report, reload the OLAP
Panel. To generate a correct report, select the "Display the new data in a new
report" option in the Modified Data Provider dialog box.
- Ranking applied on ServerValue( ) returns erroneous values.
- If you make modifications to the OLAP Panel, for example,
adding or deleting data, #SYNTAX may appear within some cells of the table.
- The structure of an existing report may not be updated if
you move the members in the OLAP Panel without adding new ones. Working directly in the
report will update the structure.
- An error can occur intermittently if you use the Slice and
Dice panel to apply a filter on server values. To work around this issue, apply a filter
via the Filter button in the Reporter toolbar.
- Although the Caption Property option is off in the OLAP
Panel, you may have some dimensions appearing with their caption in the generated report.
- The Hourglass may disappear for a few seconds while doing a
refresh or re-opening the OLAP Panel by "Edit Data Provider".
- If you select the Fetch only current filter
members option in the OLAP panel Options dialog box and if you drill down on a
filter, you can obtain an empty report.
Workaround :
Use the Fetch all filter members but display only current members.
or
Drag and drop the value you want into the Filter zone.
Example: Instead of dragging and dropping 1997 into the Filter zone and then
drilling down on it to display Q2 values, drill down on 1997 in
the outline and drag and drop Q2 into the Filter zone.
Attributes
- When you have two dimensions in a report (Dim 1, Dim 2) and
each dimension has an attribute (Att 1, Att 2), if Att 2 is empty, then the data for Att 1
appears in the Att 1 and Att 2 columns.
- If you select one or more attributes for a dimension, the Sum
cell in the BusinessObjects Master Detail report displays no data. The recommended
workaround is to click the Sum cell, and remove 'servervalue' from the SQL
statement.

Exceeding the 64k Limit for the SAP BW Access Pack
- You can now more easily create BusinessObjects reports that
require many values from the SAP BW Access Pack. In the past, in order to meet the 64k
limit for the MDX statement, it was recommended that you put some dimensions in the Filter
zone, which enabled you to obtain results in the grid for each filter value.
With SP1, BusinessObjects builds the MDX statement by iterations, which allows the MDX
statement to be split into packs. If possible, BusinessObjects sends the MDX statement to
the server as one pack. If the pack size exceeds 64k, BusinessObjects sends several MDX
statements and retrieves the corresponding row packs. Simultaneously, BusinessObjects
checks that the number of rows does not exceed the "Array Fetch Limit" set in
the OLAP Panel Options. As in the previous case, BusinessObjects splits the MDX statements
to retrieve packs with the maximum number of rows. This is very useful for gaining
performance time because it is much faster to retrieve 10 packs of 10,000 rows instead of
1 pack of 100,000 rows.
SAP attributes
- You can now use SAP attributes in your BusinessObjects
reports. You select the dimension attributes from the SAP BW OLAP Panel and view them in
the BusinessObjects report. You can find information on how to select attributes in the
online help. Select "attribute" in the help index to display the topics.
