Quantcast
Channel: SCN : Blog List - SAP BusinessObjects Web Intelligence
Viewing all articles
Browse latest Browse all 221

Web Intelligence Free Hand SQL (FHSQL)/Stored Procedures in BI4.1 SP06

$
0
0

As you may of heard already, things are changing in BI4.1 SP06 when it comes to FHSQL (Free-hand SQL) and Stored Procedures. In BI4.1 SP05 we added the ability to convert Desktop Intelligence reports directly to Web Intelligence reports that contained FHSQL. This information was put together in this blog, First look at FHSQL reports in BI4.1.

 

My colleague, Felicia Shafiq, also documented FHSQL in BI4.1.5 - Limitations, Gotchas, and Troubleshooting steps she went through during her process.

 

Well, we went ahead and upgraded Web Intelligence in SP06 so you can now edit/create reports using either FHSQL or Stored Procedures. I was able to get SP06 and do some basic testing of the new feature. Here are the steps that I went through creating 2 tests reports. The first one is based off of eFashion using a very basic query. The second one is a report using a Stored Procedure with a prompt connecting to a MS 2008 SQL Server using a JDBC Connection.

 

1. Create new document

FHSQL New Document Screenshot.jpg

2. Choose relational connection

FHSQL New Relational Connection eFashion.jpg

3. Query Script Editor opens. Place FHSQL into editor

FHSQL Query Script Editor eFashion Basic.jpg

4. Click Validate

FHSQL Query Script Editor eFashion Basic Validate.jpg

5. Click Ok twice and then the Query Panel opens showing the objects

FHSQL Query Panel eFashion Basic.jpg

6. Click Run Query and the report returns

FHSQL eFashion Basic Query Report Results.jpg


As you can see, this is a very basic test showing the creation of a new Web Intelligence report using FHSQL. The next feature that we covered was the use of Stored Procedures. I myself have worked/used Desktop Intelligence for over 7 years and looked forward to when Web Intelligence would have this feature. Its HERE! Granted it works in a different way when comparing to Deski, but it works. You no longer have to use Deski. Here are the steps I went through when creating a new report:


1. Create new document

FHSQL New Document Screenshot.jpg


2. Choose relational connection

FHSQL New Relational SQLServer JDBC Connection .jpg

3. Query Script Editor opens. Place FHSQL calling Stored Procedure into editor

FHSQL Query Script Editor calling SP with Prompt.jpg

4. Click Validate

FHSQL Query Script Editor calling SP Validate with Prompt.jpg

5. Click Ok twice and then the Query Panel opens showing the objects

FHSQL Query Panel calling SP with Prompt.jpg

6. Click Run Query, prompt window displays

FHSQL Query Panel calling SP with Prompt Display.jpg

7. Fill in prompt value, click OK, report runs and completes

FHSQL SP with Prompt Query Report Results.jpg


As you can see you will have to call the Stored Procedure using FHSQL whereas in Deski it would behave differently. You will also have to add prompt syntax in the FHSQL to receive a prompt window as I demonstrated. Other than these minor changes, both FHSQL and Stored Procedures are now available in BI4.1 SP06.


You are no longer bound to Deski, Webi has moved forward!


During the writing of this blog, testing using and ODBC connection to SQL Server was found not be working correctly. This issue is currently with Development under SAP Note  2174240 - Error "A problem is encountered. The requested action cannot be completed." when creating Stored Procedure via FHSQL using ODBC connection


Viewing all articles
Browse latest Browse all 221

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>