Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Content
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2
2.3
2.4
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1
These Release Restrictions contain important information about known issues and design limitations present in
SAP Lumira. Before you install the software, we recommend that you read the entire document. For more
information about this release see http://help.sap.com/
Known Issues
2.1
General
Lumira report with Esri Geo map cannot be opened and viewed on Internet
Explorer 9
A Lumira report with an Esri Geo Map which is published to Lumira server and cloud cannot be opened or viewed
with Internet Explorer 9 in Lumira server and cloud. This issue occurs because Internet Explorer 9 cannot handle
Esri tokens with cross-domain properties.
The longest relative file path for an extension chart should be less than 140
characters
To prevent problems when using a generated extension chart in the Lumira suite, the longest relative file path for
the extension files should be less than 140 characters. For example, "bundles\sap\viz\ext\helloworld\resources
\templates\sample\template.js" is less than 140 characters.
VizPacker plugin for SAP Web IDE does not support Safari (Mac)
The VizPacker plugin requires the BLOB type when generating the extension zip file. However, BLOB is not
supported by the Safari browser. This is a known Apple limitation for Safari.
An error may occur when a user tries to log on to the BI platform from SAP
Lumira
This issue can occur when the BI platform administrator uses the Central Management Console (CMC) to create
users who have access to SAP Lumira. If a user is created with the setting "Change password at first logon", the
user will initially be able to log on to the BI platform from SAP Lumira. They will be unable to change their
password from SAP Lumira, and so the account will be disabled during subsequent logon attempts.
Any of following actions can resolve this issue:
Use the CMC to unlock the account and reset the users password.
Do not create users for SAP Lumira with the setting Change password at first logon.
The "Set Axis Scale" dialog box may be rendered behind the visualization when
exploring from a story
In some cases, when exploring a visualization from a story, changing the axis scale will cause the dialog box to
appear behind the explore window. Updating or canceling, and then choosing explore again will render the dialog
box correctly.
Attributes are lost when switching between Esri Geo map and other chart
types
The dimension and measure attributes are not copied into an Esri Geo map from other non-Esri geo charts. You
have to build the Esri Geo map from scratch.
Tables may render incorrectly when moving from the Compose tab to the
Visualize tab
When you are working with a table in the Visualize tab, if you click the Compose tab and then click the Visualize
tab, the table may fail to display correctly.
If this issue occurs, the table will display correctly after any change that causes the table to render again in the
Visualize tab. For example, the table will display correctly after a measure is removed or added.
Measure labels may display 'Sum' as the aggregation type instead of 'Distinct
Count'
If a calculation view includes a modeled 'Counter', the aggregation type reported in SAP HANA Studio is 'Distinct
Count'. However, the aggregation type exposed by SAP HANA to the visualize tab reports the type as 'Sum'. As a
result, the measure label name may display 'Sum' instead of 'Distinct Count'.
The following formulas are not supported when they are created in SAP Lumira and published to SAP Lumira
Server or SAP Lumira Cloud, or when created in SAP Lumira Server or SAP Lumira Cloud:
Formulas that perform string parsing with the arguments LastWord() and ExceptLastWord().
The following formulas are not supported when created in SAP Lumira and published to SAP Lumira Server or
SAP Lumira Cloud:
2.2
Attributes are lost when switching between Esri Geo map and other chart
types
The dimension and measure attributes are not copied into an Esri Geo map from other non- Esri geo charts. You
have to build the Esri Geo map from scratch.
SAP HANA input parameters that require single quotes must be escaped
When acquiring an SAP HANA view that requires an input parameter, users are required to escape single quotes,
which is the same behavior as in SAP HANA Studio. Single quotes can be escaped by adding another single quote
(that is: '').
In SAP Lumira, data acquisition from SAP HANA does not support the multi-db
feature for this release
SAP HANA SP09 introduces a new multi-db feature, which allows SAP HANA to host multiple and different
databases. This feature is used mainly for multitenancy functionality. In the current version of SAP Lumira, SAP
HANA data acquisition does not support the multi-db feature.
2.3
When sharing stories, roles that have inherited access to the dataset may not
be listed
When sharing stories in SAP Lumira Server, some roles that have permissions to view the data may not be listed
for sharing.
For stories based on datasets that were created in SAP Lumira using the Connect to SAP HANA option and then
published to SAP Lumira Server, no roles appear in the More Recommendations list. This list should show roles
that have inherited access to the dataset. Only the roles that have explicit access to the dataset are available; they
are displayed in the Top Recommendations list of the Share dialog box.
Data filtering in SAP Smart Business KPI tiles based on stories created in SAP
Lumira Server
You can create a story in Lumira Server and then access it using a Smart Business KPI tile in SAP Fiori. If the story
uses an input control to filter the data, the story visualizations do not reflect the filtered values when viewed from
the Smart Business KPI tile. This issue applies only to stories created in SAP Lumira Server.
Sorting of Extensions in the Manage Lumira Extensions tile may not work on
SAP HANA Revision 09
You can use the Manage Extensions tile in SAP Fiori to manage chart extensions for SAP Lumira Server. If SAP
Lumira Server is installed on SAP HANA Revision 09, sorting of extensions may not continue to work as expected.
To resolve this problem, refresh the browser.
The Configure application may not configure the Discover feature when SAP
Lumira Server is installed on SAP HANA Revision 09
The Configuration application is a tile in SAP Fiori that can be used to configure settings for SAP Lumira Server
users. If SAP Lumira Server is installed on SAP HANA Revision 09, the Configuration application will configure all
of the users settings with the exception of the Discover feature. The following message may appear: "Unknown
failure scheduling discover jobs"
To configure the Discover feature by hand:
1.
Log into the SAP HANA Administration utility located at http://<HANA server>:<HANA port>/sap/hana/xs/
admin.
Log in with a user having the sap.hana.xs.admin.roles::SQLCCAdministrator and
sap.hana.xs.admin.roles::JobSchedulerAdministrator roles.
2.
Navigate to /sap/bi/discover/logic/vizd/backgroundjobs.
3.
4.
a.
b.
c.
d.
2.4
10
Datasets cannot be published with the default load balance / reverse proxy
server setup
If SAP Lumira Server uses the default load balance / reverse proxy server configuration, publishing a dataset from
SAP Lumira will fail. To publish a dataset to SAP Lumira Server, specify the SAP Lumira Server URL in the SAP
Lumira desktop settings.
All of a user's accessible views in SAP HANA may not appear in SAP Lumira
There are two possible reasons that views may not appear:
1.
If a user has been granted an analytic privilege, and "Applicable to all Information models" is selected, the user
may expect to access all views available in SAP HANA. However, SAP Lumira Server is not able to detect this
flag. Users must be explicitly granted an analytic privilege on a individual view.
2.
The required privilege may not be set correctly in the SAP HANA view. SAP Lumira Server is not able to detect
SAP HANA views that do not have an associated analytic privilege. To resolve this, navigate to the properties
page of your SAP HANA view and choose Apply Privileges > Analytic Privilege.
Sharing a dataset in a large scale SAP HANA environment may have slower
response times
When sharing a dataset, a longer response time may occur if the SAP HANA system has many users ( > 10000
users), or the dataset has been shared with a large number of SAP HANA roles.
11
Restrictions
3.1
AddMonthToDate
AddYearToDate
LastDayOfMonth
DayOfYear
Week
12
LastWord
ExceptLastWord
Limited support for dataset enrichment with HANNA Cloud Integration (HCI)
If you publish a story from SAP Lumira Desktop that contains a dataset that uses geo enrichment, you cannot
refresh the dataset with HCI.
13
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
14
15
www.sap.com/contactsap