Tuesday, August 21, 2012

Localized dimensions

The translation management tool is very useful in a multilingual environment. You can translate folder names, category names, report names and report content like headers and labels. But sometimes you need to go a step further, creating localized dimension objects in a universe can be a solution to your problem.

With the introduction of the Information Design Tool (IDT) there is a lot new functionality. In the SQL Expression Editor there is a new function in the System Variables folder called PREFERRED_VIEWING_LOCALE. The BI Launchpad language preference is assigned to this variable at runtime.


You can use this variable to switch between different fields in your database for the different supported languages. Now you can create localized objects and change the database field depending on the users preferences using the PREFERRED_VIEWING_LOCALE variable.


The result when used in a WebI report with viewing locale en_GB will be:


and when the viewing locale is switched to fr_BE:


Monday, August 13, 2012

Show a representative for each group

When creating an Explorer Information Space you can group facets together in folder. If you combine this with the facet display: Show a representative for each group, these folders will act like a placeholder.


Each folder gets his own placeholder in the facet panel, showing the first facet in the group, in this case Opened at year, Closed at year, Category and Status group.


When a year is selected and moves to the filter panel, the placeholder shows the next facet from the folder: Opened at quarter.


When a quarter is selected the same thing happens, the placeholder shows the next object from the folder: Opened at month.


If a selection is made on the last facet in a folder, the placeholder disappears and the space is occupied by the next folder: Closed at.

Saturday, August 11, 2012

Usefull links


Official product tutorials (video)

BI Platform Community

WebI calculation engine

http://wiki.sdn.sap.com/wiki/display/BOBJ/Business+Intelligence

Alerting from Crystal reports

Configuration steps to integrate BEx Web applications into BI 4.x

Different patch levels for Client software.

KBA 1376876: All components should be at the same level.
From BI maintenance strategy document:
"Starting with 4.1 SP06, having the Server on a newer patch than the Client, but within the same SP, is supported."

Converted DeskI FHS still points to UNV

KBA 2333549

Do not split the job server

KBA 1868751

Put the platform search master index on a shared location

Admin Guide, 25.2.3 Configuring Application Properties in the CMC.

Enable HOARD memory allocation

Data Access guide, 4.6 Memory Allocation

Parallel patching per tier


URLs:


  • BILP: http://server/BOE/BI/?startFolder=%SI_CUID%
  • Opendocument: http://server/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=%SI_CUID%
  • CMC: http://server/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=%SI_CUID%
  • Web Services: http://server/dswsbobje/services/Session

Folder win64_x64 in PATH variable for mulitsource universes on Oracle


Add variable BOE_USE_32BIT_ENV_FOR with Oracle variables on machine with both Oracle 64 & 32 bits


Redirect XI 3 opendocument

Redirect: ../OpenDocument/opendoc/openDocument.jsp
To: ../BOE/OpenDocument/opendoc/openDocument.jsp
Source: Viewing documents using opendocument.pdf, 2.5 migrating your links
replace all the content of: "E:\Program Files (x86)\SAP BusinessObjects 4.0\Tomcat6\webapps\OpenDocument\opendoc\openDocument.jsp" with:
< %
String redirectURL = "http://myserver/BOE/OpenDocument/opendoc/openDocument.jsp?" + request.getQueryString();
response.sendRedirect(redirectURL);
%>

WebI 4.1 SP 6 whats new

https://archive.sap.com/documents/docs/DOC-64504

WebI 4.2 SP 3 whats new

https://archive.sap.com/documents/docs/DOC-74364


Mouse over WebI graphs

When you mouse over WebI graphs you see the corresponding dimension and value. If you want more information in your mouse over you can add more dimensions to your graph and hide them. You will not see them in the graph axes but you will see them in the mouse over.


2 or 3 tier WebI RC?

WebI Rich Client can be running 2 tier or 3 tier mode. 2 Tier means using the database middleware of your computer and 3 tier means using the database middleware on the WebI server.

How can you see if you are using WebI Rich Client in 2 or 3 tier mode? Just hover over the Connected label in the bottom right of your screen.

                    2 tier mode: 

                    3 tier mode:



When you start WebI and click the down arrow in the System box on the logon screen, you see lines starting with a computer icon and a globe icon. A globe icon means you start in 3 tier mode. A computer icon results in 2 tier mode.


You will only see the globe icon if you started WebI RC at least once from BI Launch pad!

Thursday, August 9, 2012

Analysis for Excel add-in not working

When you get the message: "The launcher was not able to connect Analysis Add-In" it means the add-in is disabled.


You can enable the add-in the following way:
- press the Office button
- press the Excel Options button



- Select the Add-Ins options on the left
- Check if Analysis is in the Disabled Application Add-ins section
- Select Disabled Items from the Manage dropdown listbox at the bottom and press Go
- Select Analysis in the Disabled Items popup and press Enable


Thursday, August 2, 2012

Measures with delegated projection

In IDT you can create measures with delegated projection, which means recalculation of the measure in subtotal or totals is done in the database. This setting can be used with averages and count distinct.

Recalculation of the measure also occurs if you create tables or graphs in your report with a different granularity then the granularity used your query.

BusinessObjects WebI handles this by changing your query and add a union for each granularity used in a table or graph.

If you create a simple sample query like this one:


The table will look like this:


 and the query script looks like this:


When you add two new tables to your report you see #TOREFRESH which means the tables have a different granularity then your query.


When you refresh the query, a query with 3 unions will be executed. A column named GID is added to make the link to the correct table in the report.