Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

For reports having prompts enabled on the BI platform, you can filter the data during refresh by entering specific values in prompt.

How to answer Prompts:

Filter the data of the document by performing the following steps:

1. On the "Prompts" window, select a Prompt name.

The "Prompt values" window appears.

2. The "Prompts values" window displays the following fields based on the prompt properties set by

the report designer:

Listed values: Displays the list of values available for the document. Select the required value(s)

to filter the data.

Search: Searches for a specific value from the available listed values.

Add Value: Allows you to enter a value not listed under the available listed values. Based on the

Prompt name, enter an appropriate value.

3. Tap Done.

The "Prompts" window  appears. The selected value appears under the selected prompt name.

Select the prompt name for the mandatory prompts. If the prompt name displays Optional along with

the prompt name, selecting this prompt is optional.

4. Tap Done in the "Prompts" window.

Based on the selected values, the filtered report is displayed on the device.

Types of prompts supported by the app:

Prompts having a hierarchical list of values (LOV).

Cascading or nested prompts.

The LOV displayed in prompts can be refreshed from the server.

Listed below are the Limitations in Prompts and also the Known issues in Prompts categorized for Web intelligence, Crystal reports and documents based on OLAP and BW data sources.

Limitations in Prompts:

1. Multicolumn LOV is not supported.

2. The Time dimension is not supported for prompts.

3. The semi-colon character (;) should not be used while configuring prompts in Web Intelligence as

it is not supported by the application.

4. Web Intelligence documents designed with a Universe based on Business Warehouse (BW) as the

data-source, and having a "Key Date" variable cannot have other variable types. If other variables

are used in the document along with the “Key Date” variable, the app does not support the document.

Known Issues:

Prompt issues in web intelligence reports

1. In the app, the list of values (LOV) in prompts do not appear in the same order as that in Web

Intelligence on the BI platform.

2. If the list of values (LOV) in a prompt has duplicate values (having unique keys on the BI platform),

they do not appear over the app.

3. In dependent prompts, even if values of few variables are pre-selected in the pop-over, it is mandatory for the user to begin selection from the first variable. The prompt does not consider the selections made in previous refresh of the report.

4. If a report having optional prompts is refreshed multiple times, without selecting any values in the

pop-over, the app displays a server error.

5. Refreshing a document with hierarchical prompts does not filter the data based on chosen values.

Unexpected results are returned.

6. If a Web Intelligence document is refreshed using default values for prompt, inconsistent results are displayed in the document.

Prompt issues in crystal reports

1. Users are unable to select multiple values for prompts displaying a range of values in Crystal Report documents.

2. Prompts with default values do not display the default selections of the prompt values configured by the Crystal Reports' report-designer.

3. If the prompt in a Crystal report has been defined on a currency based dimension, the app displays the following error message when the report is refreshed and the currency values are entered in the prompt on the iPad screen: "Failed to open the document (MOB00035)".

4. On refreshing a Crystal Report document having prompts, the following error may appear:

"An internal server occurred while processing the client request (MOB00082)".

5. Optional prompts are not supported for Crystal reports and so cannot be configured by the CR report designer.

6. Prompts defined for Date dimension in a Crystal Report document do not behave as expected. After you have refreshed the document and entered values for date in the prompt pop-over, the app displays an error message.

Prompt issues in documents based on data sources having hierarchy objects (such as OLAP and BW)

1. Values selected by a user in hierarchical or dependent (nested) prompts are not persisted by the app. Everytime user refreshes the BI document, he/she needs to make fresh selections in the LOV that appears in the prompt pop-over.

2. Users cannot enter text values in hierarchical and dependent prompts that appear in the app. They can only make selections in the values listed on the prompt screen.

3. Even if a dependent prompt is defined as "optional" in Web Intelligence, the app forces users toselect values listed in the pop-over.

4. A prompt having hierarchy variables that allow multiple selections may exhibit erratic behavior inthe app.

5. If a prompt is dependent on multiple prompts, the prompt may display unpredictable behavior on device.

6. In a hierarchical prompt (that allows multiple value selections), if there are multiple values at the first level of hierarchy, users cannot proceed with a single selection. The app forces the user to select at least two values out of those listed on the screen.

7. If users choose the Reset all option in a hierarchical prompt over the app, the view of the "Values" gets slightly distorted.

8. The Reset all option does not work for the following prompt types:

Prompts with hierarchical or dependent list of values.

Prompts with hierarchy based variables

Prompts created with a Universe based on Business Warehouse (BW).

9. If dependent prompts are configured with hierarchy based variables in Web Intelligence, the prompts may be replicated in the app on device.

10. For a BI document having multiple hierarchical prompts, if the user selects the root node values for one prompt and a subsequent (lower) level node values for the other prompt, partial results appear in the document after refresh.

Labels in this area