Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

This page list issues that affect not only a specific deployment Designer or an addon.

 

Global Functions are not callable from On Before Prompts Submit, On Variable Initialization

As of Lumira Designer 2.3 global functions are not called anymore .

This was an error in previous versions of Lumira that these functions were executed during runtime. This was corrected with 2.3. The Designer always showed an error message "Couldn't resolve reference to Member '..'" also in previous versions:

The reason why we need to prevent these kind of calls is that they could lead to dramatic errors when they call the wrong API like endless loops or dumps. Inside the the OnXXX methods all API calls are checked in detail whether they are allowed or not.

FIX: You have to move the code from your global functions to the OnXXX functions and execute them directly there.

Interesting Blogs

https://blogs.sap.com/author/reiner.hille-doering/

Mysterious Memberlists in Lumira Designer

Dynamic Apps in Lumira 2.1 – Iterating Over a Resultset

 

Background Processing => Data source not loaded

In Lumira 2.1 until 2.1 SP 1 Patch 1 there is a know issue which has the following side effect:

Symptom: During background processing steps data sources loaded before can be unloaded again. This leads to errors like "Data source not loaded" in UI elemenets like charts or cross tab.

It only occurs if Undo / Redo steps are greater than 0.

As of our analysis this occurs when charts are shown during background processing and charts fire Update Properties HTTP requests to the server before the next background processing step.

In Fiddler the requests look like this:

The easiest way to detect the problem is to check the prolfiling trace for the "Set Page State" and for the destruction of data provider / data sources (RFC BICS_PROV_CLOSE) which were loaded before

*** Step 5 ***
Total time: 4837 ms, Lumira Designer time: 326 ms, data sources time: 4511 ms

4730 ms: Main task of step ZEN 
  4730 ms: Process request: Application startup 
    0 ms: Collect processing information 
    0 ms: Bookmark handling 
    4403 ms (1 ms not covered): Prepare Processing 
      3356 ms: Set Page State 
        0 ms: Set Page State (Main Template) 
        3354 ms (924 ms not covered): Set Page State (Data Providers) 
          183 ms: Synchronize State Variables (in parallel via processing groups) 
...
          88 ms (2 ms not covered): Destroy data provider DS_XYZ 
            51 ms: RFC BICS_PROV_CLOSE  [Processing Group: PRCGRP_2]

 

WORKAROUND

You have to disable the usage of undo/redo in all applications that use background processing.

To do this do the following:

  • open your application in the Designer and go to the property sheet of the application:

Behavior
  Maxium Number of Steps 0

 You have to change the steps value to 0 instead of e.g. the default value of 10.

Solution

Note 2668995 - Unpredictable Behavior of Lumira 2.1 Apps with enabled Undo/Redo

Background Processing => Data source not loaded

In Lumira 2.1 until 2.1 SP 1 Patch 1 there is a know issue which has the following side effect:

Symptom: During background processing steps data sources loaded before can be unloaded again. This leads to errors like "Data source not loaded" in UI elemenets like charts or cross tab.

As of our analysis this occurs when charts are shown during background processing and charts fire Update Properties HTTP requests to the server before the next background processing step.

In Fiddler the requests look like this:

The easiest way to detect the problem is to check the prolfiling trace for the "Set Page State" and for the destruction of data provider / data sources (RFC BICS_PROV_CLOSE) which were loaded before

*** Step 5 ***
Total time: 4837 ms, Lumira Designer time: 326 ms, data sources time: 4511 ms

4730 ms: Main task of step ZEN 
  4730 ms: Process request: Application startup 
    0 ms: Collect processing information 
    0 ms: Bookmark handling 
    4403 ms (1 ms not covered): Prepare Processing 
      3356 ms: Set Page State 
        0 ms: Set Page State (Main Template) 
        3354 ms (924 ms not covered): Set Page State (Data Providers) 
          183 ms: Synchronize State Variables (in parallel via processing groups) 
...
          88 ms (2 ms not covered): Destroy data provider DS_XYZ 
            51 ms: RFC BICS_PROV_CLOSE  [Processing Group: PRCGRP_2]

 

 

Mobile Touch / click events in crosstab do not work

This issue came with 2.1 SP 0 and was not completely fixed with 2.1 SP 1 Patch 1.

Crosstab click events do not work on mobile applications.

Scenarios with multiple crosstabs raise event handlers in wrong crosstab.

SOLUTION: We are targeting 2.1 SP 1 Patch 2. We will announce this patch soon in the official release note 2465894. Please wait for the update of the note and the announcement of the release date.

 

getAttributeMember returns null

Assuming you have a scenario where the data is not loaded before and thus the internalKey will be null. As a workaround you can force the loading like this:
var kpi = me.getSelectedMember("0BC_CUST1");
var ikey = kpi.internalKey;
var att = kpi.getAttributeMember("0BC_HOME");
var dummy = att.text;
APPLICATION.alert("Key: '" + ikey + "' - Attribute: '" + att.internalKey );
The important part is the assignment of att.text which fills the cache. After that internalKey will return a proper value.

Solution: The fix will be part of Lumira 2.2. As it requires a complete new BICS a downport to 2.1 is too risky.

RRI fails - troubleshooting

In case your RRI target does not open correctly this explains how to gather the URL started by the Design Studio runtime.

Use Chrome or IE network tools (F12). In IE you have to switch on Network tracing. After right clicking to open the navigate to context menu and selecting the RRI target you should see 3 requests in your network tool. Go to the 3rd one (the first two are context menu related) and look at its response.

You will find the following XML. Search for newurl:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
...
"newurl":"https\x3a\x2f\x2fhost.comx2fBOE\x2fOpenDocument\x2fopendoc\x2fopenDocument.jsp\x3fsIDType\x3dCUID\x26iDocID\x3d\x26RRI_PROPERTY_LIST\x2dNAMED_PROPERTY\x2dNAME\x3dRRI_PARAMETER_NAME\x26RRI_P...",
"loadingIndicatorDelay...

Select the whole string behind newurl starting with http... until the last ".

Now take a decoder tools as e.g. Fiddler to decode the Javascript encoded string:

The result is the decoded URL which you can now directly start and thus test in your browser.

An easier alternative is to switch on the popup blocker e.g. in chrome temporarily and gather the URL from this window:

Please read also the following chapter about invalid URLs.

In case the URL contains an unescaped Space character, this note can be the solution:

RRI Jump from Design Studio to a Transaction does not work.

openInNewWindow: does not support invalid URLs

As of Design Studio 1.6 SP 5 all URLs used in the APPLICATION.openInNewWindow API call must be valid according to RFC 2396 (and related). If invalid they will not be executed at all.

You can use the API Convert.urlEncode to convert the different values used in as URL parameter. Do not convert a complete URL with this API as the separator chars like & and ? wpiöd be encoded.

Known issue: valid URLs using a non-standard protocol as e.g. "SIP:..." are not executed at the moment. This will be fixed in future Design Studio SPs. More details to come.

2555577 - URL Validation in Design Studio and Lumira Designer

How to create correct escaped URLs

The correct way to create URLs (assuming that the parameter names are all ASCII chars only) is to only encode the parameter values.

var correctUrl= "/mypath?param0=" + Convert.urlEncode(myValue0) + "&param1=" +  Convert.urlEncode(myValue1) ...

Typical errors:

var wrongUrl= "/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=" + v_URL_ID
+ Convert.urlEncode("&Xcur=" + DS_1.getVariableValueExt("0P_CURR");

The special chars like & and = must not be encoded.

 --------

var wrongUrl= Convert.urlEncode( "/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=" + v_URL_ID + "&Xcur=" + DS_1.getVariableValueExt("0P_CURR"));

The special chars like / and ? and & and = must not be encoded.

--------

var wrongUrl= "/mypath?param0=" + Convert.urlEncode(myValue0) + " &param1=" +  Convert.urlEncode(myValue1) ...

This is more difficult to see, there is a space char before the 2nd & which must be escaped or better removed if not necessary.


Dimension Filter

Case Sensitive / Insensitive Search

Design Studio value help search is always case insensitive but as soon as the search has to be done in the backend, If not all values are loaded, then this depends on an RSADMIN parameter.

Note 1269398 - Case-insensitive search in input help (F4) 

Use the program SAP_RSADMIN_MAINTAIN to set the RSADMIN parameter as follows:
object = RSMD_RS_TXTSEARCH and value = X.

Workaround: Endless loading animation in Lumira 2.0

In case you face a loading animation that will never vanish again, please try the following Workaround

Set the following application property in your Design Studio app:

Loading Indicator Delay = 999s (e.g.)

This prevents the loading indicator to come up at all.

The final fix will come with Lumira 2.0 SP 3.

CSS Styles

Be aware of the phrase in the Application Designer Guide:

 

Restriction

If you use this function, you should be aware that SAP does not guarantee that custom CSS stylesheets will work properly. SAP does not guarantee that no UIrelated and/or functionality-related problems will occur. SAP also does not guarantee that custom CSS stylesheets will work properly after software upgrades."


Empty Members / ## Handling with BICS Parameters

Symptom:

  1. An empty attribute of a calculation view in Lumira has ## value.
  2. With Design Studio there is no value for this empty attribute.


The following Parameter has to be set to false for changing the ## value to empty value within Lumira Designer:

-DAAD_SHOW_INTERNAL_TEXT_FOR_NULL_AND_EMPTY_MEMBERS=false

-DAAD_SHOW_INTERNAL_KEYS_FOR_NULL_AND_EMPTY_MEMBERS=false

 

SAP Lumira Server for BI Platform 

1. Log into CMC.

2. Navigate to Servers -> Service Categories (Lumira Server Services) -> LumiraServer

3. Open LumiraServer properties page and add

-DAAD_SHOW_INTERNAL_TEXT_FOR_NULL_AND_EMPTY_MEMBERS=false

-DAAD_SHOW_INTERNAL_KEYS_FOR_NULL_AND_EMPTY_MEMBERS=false in Command Line Parameters.

4. Save & Close and Restart LumiraServer

 

SAP Lumira Designer 

Add the following to your SapLumiraDesigner.ini file:

-DAAD_SHOW_INTERNAL_TEXT_FOR_NULL_AND_EMPTY_MEMBERS=false

-DAAD_SHOW_INTERNAL_KEYS_FOR_NULL_AND_EMPTY_MEMBERS=false

OLAP statistics will NOT be captured in RSDDSTAT_OLAP table

Environment:

  • Source System: Backend BW
  • Frontend Tool: Lumira Designer 2.x and Design Studio 1.6 SP7

Symptom:

When using Generic Analysis Template or/and an API   assignDataSource(dataSourceConnection, dataSourceType, dataSourceName) OLAP statistics will NOT be captured in RSDDSTAT_OLAP table in backend by execution of the Application.

The issue is reproduced in Local and BI Platform execution modes of Designer Tool.


  • No labels

4 Comments

  1. This is a good help/overview, but when will Lumira 2.1 SP01 Patch 1 and Lumira 2.1 SP02 be released? https://launchpad.support.sap.com/#/notes/0002465894

    Before or after Lumira 2.2 in June..?

  2. Hi Michael! Current plans are for 2nd half of April.

  3. patch has to be delayed - Official patch date will be announce in the release note  2465894 soon.