1 2 3 9 Previous Next

SAP BusinessObjects Web Intelligence

133 Posts

Hi Team,

 

Purpose : How to show Top N and Bottom N records controlled by a single Input control , and show Top and Bottom records in single table ordered as per their functionality  and format them with alerts .

Desired Output

In above table top 2 records are colored with green ,ordered by descending and bottom 2 records are colored with red,ordered by ascending.

 

How to do :

* Create a variable that acts as Input control for ranking.

Top =2 (Default value )

* Create another variable which distinguish Top and Bottom and filter the records in table for Top and Bottom records.

Top/Bottom =If(Rank([Prod])<=[Top] ) Then "Top" Else If( Rank([Prod];Bottom)<=[Top]) Then "Bottom"


Filter the table with Top/Bottom variable inlist Top and Bottom . By default we get only Top as value for Filter , we need to add Bottom value manually to Filter.

 

Now we get below table . Rank column is added to table.Here values are not in order.

Next to do is to order values .(If you sort on measure /Rank we get only ascending /descending , but our purpose is to have Top values in descending and bottom values in ascending).

* Create another variable for sort

Sort =If([Top/Bottom]="Bottom";Max(Rank([Prod]))In Block-Rank([Prod]) ; Rank([Prod]))

 

Add Top/Bottom and Sort tables to table .

Do descending sort on Top/Bottom  and ascending sort on Sort column.

 

Hide Sort and Top/Bottom columns ( don't delete)

Create alert to distinguish Top and Bottom records.

 

..Hope you'll enjoy this trick.

Would like to share the behavior of objects in Merged Universe when we upgraded Linked Universe from BO 5.1.5 to BI 4.1 and convert to UNX

 

 

When the linked universes in 5.1.5 is upgraded and converted to UNX, they result in a merged universe in 4.1.

 

Issue:

 

The state of the objects that were from Core Universe was not as expected in 4.1 merged UNX Universe.

 

Issue Description:

 

Noticed objects that were in hidden state in the core universe in 5.1.5 are visible in the merged universe in 4.1 UNX

which might cause issues by exposing the hidden objects when released to users without proper testing.

 

Resolution:

 

Manually need to change the state of the object in business layer so that
the object state would be the same in both 5.1.5 Universe and 4.1 UNX Universe

 

Note: Linked universes are no longer supported in Business Objects 4.x UNX.

However, linked universes can be converted as merged UNX universes i.e. conversion of derived
universe to UNX automatically includes Core Universe objects also.

 

Thanks,

Archana

Welcome !!

 

This is a simple & quick how to procedure which explains about how to make an Excel as a source to WebI. Thanks if you found this interesting and utile.

 

Note: This is a special feature available from BO Version 4.1 (SP2) onwards.

 

I've tried to post this maximum with the screenshots hope we all love more of a screenshots rather composing big paragraphs. This process is not a big deal still will hopefully help fresh guys.

 

Here is how we can upload an excel file and make it as a source for WebI report.

Untitled.jpg

Choose Local Document, and choose the destination folder to upload an excel file.

Untitled1.jpg


Choose file from your computer as highlighted.

Untitled2.jpg


Here you can choose the file you want to upload and make your WebI Report

Untitled3.jpg


Click Add to upload the file.

Untitled4.jpg


It will be uploaded as highlighted here.

Untitled5.jpg


Now, it is time to create a WebI Report based on uploaded file.

Untitled6.jpg


Select new report.

Untitled7.jpg

Choose Excel as a Data Source.

Untitled8.jpg


Choose the destination folder on which the excel was uploaded and saved.

Untitled9.jpg


Here you can do settings for the excel file.

Untitled10.jpg

Now the WebI will show all the dimensions and measure as default.

Untitled11.jpg


You can choose and change a dimension into a measure as per requirement.

Untitled12.jpg


Here you can even select type of the object(String/Date/Number).

Untitled13.jpg


After doing all necessary steps you can run query to get result as intended.

Untitled14.jpg


You can also save this as WebI query as highlighted.

Untitled15.jpg


That's it. Thanks

Hi

 

This blog will help you to remove the underline from hyperlink and Document and change the visited and unvisited Hyperlink color.

 

 

1st we will learn how to remove the underline from the Hyperlink or document link 

 

Step 1: Create a hyperlink on a column.

 

 

 

Step 2:  The below image I had created a hyperlink on a NAME column.

 

Step 3: After creating the hyperlink we will see a above image.(i.e hyperlink with underline)

 

Step 4:

 
 

 

 

We can see the formula bar; The new formula has been display.

For  eg we had created a hyperlink for a www.google.com

The formula bar will contain the formula as

 

="<a href=\"www.goggle.com\" title=\"\" target=\"_blank\" nav=\"web\" >"+[Name]+"</a>"

Step 5:

After that we have to edit the above formula

="<a href=\"www.goggle.com\" title=\"\" target=\"_blank\" nav=\"web\" style=\"text-decoration:none!important\">"+[Name]+"</a>"

We have to add the below text to the hyperlink

=style=\"text-decoration:none!important\"

Step6 :

 

After that right click on the name column and select the format cell

 

 

 

Select the “READ CONTENT AS HTML”.

 

 

Step 7: After selecting the Display as Read Content as HTML.

 

 

Note

After this step we have to save our  Webi  to BI LAUNCH PAD

 

 

Step 8:After saving the webi in bi launch pad we will see the below output ie hyperlink without under line

 

 

 

After that we will change the hyperlink visited and unvisited color of hyperlink

 

Step 1: Right click on a report name

 

 

 

And select the Format Report.

Step  2:

 

Select the Appearance we can see the hyperlink color.

 

 

Finally save the webi in BI launch pad and see the changes.

Summary

WHAT: Pin the latest instance of a Web Intelligence document.

 

WHY: Users may have a Web Intelligence document that they navigate to on a recurring basis as they consume the latest scheduled output. Pinning the latest instance of the document saves the user from having to navigate as the instance will appear upon logon.

 

 

Instructions

1. Right click on the Web Intelligence document and click on "Document Link".

hypA1.png

 

2. Copy the hyperlink.

hypA2.png

 

3. Create a "Hyperlink" object by clicking New > Hyperlink. Note: You will need write access to a folder (e.g. My Documents).

hyp01.png


4. Populate properties Title and URL and click "OK".

    Important! URL = Paste document link AND append &sInstance=Last

hyp02.png

hyp03.png

 

5. Double click the object (or right click and select "View").

hyp04.png

6. Click the pin icon to pin the tab.

hyp5.png

 

That's it! You have successfully pinned the latest instance of a Web Intelligence document.

Scenario

Visualise [Sales Revenue] by [Quarter] for the [Last 3 Years].

 

Example

The data visualisation below is an example of what is produced by Web Intelligence out of the box (i.e. default).

DataViz01.jpg

What is wrong with this visualisation?

  • Misuse of Colour - When viewed at a glance, a user may believe Blue is good and Orange is bad? Our eyes need to constantly flick between the legend and the bars to understand which colour relates to which year. The default colour choice does not provide much value.

 

  • X & Y Axis Titles - Do we need them? Would a heading (e.g. Sales Revenue by Quarter: 2004 - 2006) not provide sufficient context? When we see values such as Q1, Q2, Q3 the user understands these are Quarters.


  • Gridlines & Value Axis - Are gridlines and the Y-axis adding any value? We can't tell the actual value of each bar regardless of their presence.

 

  • Whitespace - There is a large amount of whitespace above the bars and around the legend. Could we make better use of that space to emphasise the shapes of the bars?

 

Here is an example using the same data but adhering to some data visualisation best practices using standard Web Intelligence functionality.

DataViz02.jpeg

  1. Remove titles from the X and Y axis. The combination of a descriptive heading (e.g. Sales Revenue by Quarter: 2004 - 2006) and actual values (e.g. 2004, 2005 & Q1, Q2, etc) provide sufficient context.
  2. Remove background grid lines, this will increase our Data-Ink ratio.
  3. Change the colour palette to monochrome (available in Web Intelligence 4.0), this fading of blue from light to dark enables the user to draw a relationship between lighter being further in the past and darker being closer to the present.
  4. Change the position of the legend to the top to minimise white space.
  5. Change the x-axis line to a less jarring colour to emphasise the bars (e.g. Grey - 25%).
  6. Change the font colour to a less jarring colour to further emphasise the bars (e.g. Grey - 40%)
  7. Force a custom MAX for the value axis so that the highest bar is equal to the MAX Y-axis value (reducing white space further).

 

Note: If the values of the individual bars are deemed critical to the story, we can turn them on but rather than leaving the default format, scale the number to a level of precision that enables the user to consume the information as quickly as possible without losing relevancy.

DataViz03.png

 

Colour Palette - Web Intelligence 4.0 vs. 4.1

Something to be mindful of, Web Intelligence 4.0 is restricted to a fixed number of palettes.

webi40.jpg

 

Web Intelligence 4.1 introduces a Custom colour palette which can provide users more flexibility. Highly recommend reading Stephen Few's - Uses and Misuses of Color for further learning and understanding on how to use colour appropriately and when it could be misused.

webi41.png

Issue Description

 

The following error message (or very similar) appears when you attempt to refresh a SAP BusinessObjects report built off a SAP BW BEx query using BICS.

 

Failed to execute query: ‘java.lang.NumberFormatException: For input string: “2000,0000”’.


The input string will differ based on the environment, but the key to this is that the format is incorrect.  In the above example, the input string value is 2000,0000.  The thousands separator is in the incorrect location, thus throwing the java.lang.NumberFormatException.  I’ve included screenshots of what the error looks like in both Crystal Reports and Web Intelligence.


Crystal Reports

ForInputString Crystal.png


Web Intelligence

ForInputString WebI.png

Web Intelligence throws an error code of WIS 00000, which is pretty generic.

 

What is Causing This?

This has nothing to do with default values or formulas in the report, so you can stop looking there.  The input string (in our example 2000,0000) is coming from the SAP BW Safety Belt setup. If you are not familiar with the SAP BW Safety Belt, read about it here.  The value 2000,0000 is read from the SAP BW Safety Belt objects stored in the table RSADMIN.  Below is a screenshot from RSADMIN showing the objects and the values.

 

 

BW Table RSADMIN

BW RSADMIN.png

 

Resolution

To resolve this issue, the Safety Belt objects should be corrected to specify the correct, intended values.  KBA1773823 explains how to make the change.

 

More Information

1773823 - How to resolve error message 'For input string: "500,0000" (WIS 00000)' in BI 4.0 Web Intelligence reporting off of SAP BEx query?

1127156 - Safety belt: Result set is too large

SAP BusinessObjects Increasing Stability by Setting Limits on Max. Retrievable Cells from SAP BW into Web Intelligence using BICS

Hi All,

 

Environment : BI 4.1 .

Reporting Database : BW 7.4 SP3.


Recently we migrated to BI 4.1 SP3 from BI 4.0 SP6.

From then reports in BI 4.1 launchpad was taking so much time compared to BI 4.0 and BI 4.1 Rich Client.

There was drastic change in performance .A report which is running in 30 sec in BI 4.1 Rich client and BI 4.0 SP6 was taking >10 minutes in BI 4.1 launchpad.

Below tasks helped us to achieve the performance again.
1.Disabling logs:

-Go to CMC,navigate to the servers and then webi processing server.

-Right click and go to properties.

-Set log level as "None"

-Do the same for all webi processing server.

-Same step you have to follow for rest of the servers.

-For only CMS keep log level as "Unspecified".


2.Delete logs:

-Go to Installing Directory of BusinessObjetcs\SAP BusinessObjects\SAPBusinessObjects Enterprise XI 4.0\logging directory.

-Delete all unwanted logs(.glf files).


3.Clear Cache:

-Go to Installing Directory of BusinessObjetcs\SAP BusinessObjects\SAPBusinessObjects Enterprise XI 4.0\Data directory.

-Take back up of all the content inside it and delete everything.


4.Clear Tomcat cache:

-Stop Tomcat.

-Go to Installing Directory of BusinessObjetcs\SAPBusinessObjects\Tomcat\work\Catalina\localhost.

-Take back up of all the content inside it and delete everything.

-Start Tomcat.


After performing all these steps, Restart SIA.

In Addition to above , we can consider below points also for better performance.

A. If source to webi is .UNV

- Change the connection pool mode to 'Disconnect after each transaction'.

- Increase the Array fetch size to 1000.

- In Universe Parameters, click on the Parameters tab and change the setting DISABLE_ARRAY_FETCH_SIZE_OPTIMIZATION from the default of "No", to "Yes" and click the "Replace" button, then Ok to save the

changes.

 

B.Disable Connection Server Trace

Modify cs.cfg In Windows this is located in the following

directory C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer Set the

following parameter to this value <Traces Active="No">

 

C.Follow the SAP NOTE:1930558 -

How to utilize the 64-bit SAP BAPI driver with UNV universes in BI 4.x (Windows) .


Thanks to Sabari Vasan.S for his valuable sharing

Please post if you have any other points to consider for better performance.


 

 



This document describes about how to create Publication with Dynamic Recipients in brief.


Hi I recently worked out how to Join Data from two queries in a single report

 

Create a WEBI document  with 2 queries where 1 reads data from the other
in my example I have 2 queries 1 is Rels and the other is Related Acc the Related Acc query is reading the account name for accounts that are the Rel Business Partner ID from the Rels Query
join1.png
The result is two tables 1 of the accounts with the related accounts and the other of the related accounts IDs with their names. I want to join the second table to the first to provide name details fro the Rel Business Partner ID in the First table
Join2.png
The first step is to define the Merge criteria which is the Rel-Business Partner ID from the Rels query and the Business Partner ID for Filtering from the Related Acc query use Ctrl click to select these two dimensions then right click and select Merge
join3.png
Next right click on the Merged dimension and select Edit Properties
join4.png
Then change the name of the Merged dimension to make it obvious which is which
join5.png
result is shown below
join6.png
Next create a variable for the Organization name from the Related Acc query.
The important elements are to make the Qualification of the variable a detail not a  dimension. When this detail variable type is used it allows you to specify what the associated dimension is in this case it is the MErged dimension Business Partner ID M.  The Formula just reads the value of the field from the Related Acc query
join7.png
finally include the new variable in the first table and the names will be displayed correctly
join8.png

 

 

I hope this helps other people I have been wondering how to do this for ages. So simple in SQL but quite complex in WEBI.

 

Regards

 

Louis

Introduction:

 

This blog focuses on a work around solution to read the negative precision value in BO-WEBI 4.1 version.

 

 

Issue:

 

In 4.1 version it has been observed that the smaller precision negative values are not picked in WEBI when BEX is used as a source of the data.

 

 

Bex Output:

 

Bex.JPG

 

WEBI Output for the relative Line:

 

WEBI-Before.JPG

 

Number Format of the Line:

 

Old.JPG

 

Work around solution:

 

Change the number format to below: Where negative is placed in apostrophe.

 

New.JPG

 

Please use the required decimals.

 

WEBI Output:

 

WEBI - After.JPG

 

Cause of the Issue:

 

This issue is coming in BO 4.1 when BEX is used as a source of the data and when the lines are using NODIM to suppress the units. NODIM values are not passing to WEBI when the values are too less.

 

This issue is identified in when the BW7.3 as backend and BO 4.1, the smaller negative precision values are not been pulled in WEBI for which the above work around works fine as a solution.

 

When BW7.4 as backend (Support Pack is less than 5), even the Smaller precision values both for Positive and Negative values also not been recognized by WEBI or by Crystal when the lines are using NODIM function. Quick work around is to remove the NODIM and then pull the values in reporting.

From SP5 of BW7.4, this side effect of NODIM is not occurring and the normal number formatting can be applied.

 

Hope this works for you.

Hi All,

 

Environment : BI 4.1 SP3 and BW 7.4 SP3

 

We are doing a pilot for converting all .Unv based reports. Below are observations when pointing .Unv to BICS

 

Issue/ConsiderationSolution
some of the objects are pointed to wrong objectsRemap again the objects which are pointed incorrectly
If  constant filters applied on a detail object in the filters pane ,
then we can't map this object to any of the object.
Remove all the filters from filters pane before change ,
place filters after source change
Prompt screen loading and Prompt LOV’s fetching
is slow compared to .Unv
Product limitation
Cascading Filters : with UNV we created different levels of hierarchies
for drill down and for filters report specifically.
For drill down we can have BW hierarchy
(Lot of development effort in BW ,and could not be report specific) .
Cascading Filters is limitation , idea has been posted BI 4.0 - WebI on BEX (BICS) -
Make report Drill Filters capable of handling linked / cascading relationship between SAP ….
Most of the BEx variable texts(prompt description )
are customized in Universes .
we may need to change the Variable texts in BW .
This will be difficult when we have reports with 2 or more queries .
Variable text should be same for all queries.
We can't have measure objects in the query filters pane.Apply filters ib Bex/in the Webi report
Web Intelligence Query Panel - not possible to use "OR" operator
when creating Query Filters on BICS BEX source
please refer : SAP Note  1687933

                                    

 

Advantages:

 

1.we have seen ~5% of performance improvement.

2.In some universes we are converted Detail Object Keys (Attributes of dimensions . Ex :Customer Key /Material Key) into dimensions for merging (we can't do merge on details objects in 3.x ) . In 4.1 we can directly merge Detail objects.

 

Hope this helps ...


Please post your experiences for better guidance.

Hello everyone,

 

Since Oracle has released Java 7 there have been multiple issues regarding the web intelligence java panel/RIA/applet in BI 4.x and XI 3.1.

 

There are various issues that occur from ones that are just a nuisance to actually keeping webi from launching completely, depending on your current patch level, JRE version, etc.

 

With the large number of issues and various kba's that cover these issues, we decided it would be best to try and consolidate all of this information into one location.

 

We have created the following wiki that details different java issues that may occur in each currently supported release (XI 3.1, BI 4.0, BI 4.1) when it comes to JRE 1.7 and 1.8.

 

Web Intelligence and Oracle Java Runtime Environment Known Issues

 

Please look it over and leave your comments to help improve the wiki.

 

Mike Neville and I will be updating it as issues are discovered and then their resolutions and appreciate any input or feedback that you may have.

 

Best Regards,

Jason

Business requirement: Highlight any sales revenues that are below sales target, which is a user input control. In other words, if a user wants to highlight any sales revenues that are below $2,000,000 then he can type in 2,000,000 as an input and the result is similar the one below

1.png

Here’s how we can do that.

 

Step 1: Build a report using eFashion Universe

2.png

Step 2: Create “Sales Target” variable

3.png

Step 3: Design an Entry Field input control on Sales Target

4.png

Step 4: Apply Conditional formatting on Sales Revenues using Sales Target as an input

5.png

Now enjoy the result

6.png

 

Thanks,

Huu Nguyen

Introduction

Web Intelligence documents can be created, edited or consumed via three different interfaces:

  1. HTML
  2. Applet (Java)
  3. Desktop (Rich Client)

 

The following blog post is a feature comparison of the two web-based modes (HTML & Applet) on the latest version currently available (BI 4.1 SP03).

 

 

Select a Data Source

Data sources specific to Applet (Java): Excel, BEx & Analysis View.

image01.png

 

Document Linking Wizard

  • HTML is the only interface that offers a "Document Linking Wizard" within the [Report Elements] tab.
  • Leveraging OpenDocument syntax is still possible in the Applet (Java) interface but must be entered manually.
  • Note: While Web Intelligence documents based on BEx must be created in Applet (Java) mode, developers can still leverage the HTML specific document linking feature by viewing a Web Intelligence/BEx report and switching to "Design" mode.

image02.png

 

Conditional Formatting

Only Applet (Java) can create new formatting rules.

image03.png

 

Data Source Management

Features specific to Applet (Java):

  • "Data" mode (in addition to Reading & Design).
  • Ability to add a "New data provider" directly within Design mode (Data Access > Data Providers).
  • Ability to "Change Source" directly within Design mode (Data Access > Tools).
  • Ability to Delete, Rename and Change Source within Data mode.

image04.png

 

Number Formatting

Only Applet (Java) can apply Custom number formats.

image05.png

Actions

Filter Blog

By author:
By date:
By tag: