Thursday, November 18th, 2010

BI Publisher and Siebel, new and improved!

My previous post was about the integration between Siebel and BI Publisher that was available since Siebel 8.1. As I mentioned back then, the integration is promising, but presented  some serious limitations to BI as a report generation tool for Siebel, and I promised to touch this issue again in a new post. Well, here we go.

With the patch to Siebel 8.1.1.1, some of the isssues have been resolved, while some serious new ones have been created. Our main reason to upgrade (Siebel to 8.1.1.1 and BI Publisher to  10.1.3.4.1) were issues with Active Directory. The Siebel Security Model provided by BI was not documented nor functioning properly in the earlier version. This has been resolved in the new version. The Siebel Security Model basically works like this: a user requests a report, BI then checks in Siebel whether the user has the right responsibility (yes, you need to add the XMLP_DEVELOPER responsibility to each user that needs to create reports) and then BI creates the report and sends it back to Siebel. Works a like charm!

Another major improvement is that automatic report generation has been greatly enhanced. This has already been so since an earlier QuickFix, but also comes as part of 8.1.1.1. You can now use workflows to generate reports for you. This means you can now trigger reports by Runtime Events or from eScript. A great improvement, as you are no longer bounded to the user interface only.

Lastly, Siebel now allows you to enter parameters right before the report is generated. This is great, because it allows you to show data in the report without having to store it in the Siebel data model. You can enter these parameters in a pop-up that shows up right before generating the report.

Both these improvements were our main reasons to upgrade and we’re quite satisfied with them. However, we encountered some pitfallts, the most important ones being:

1) A bug that prevents you from uploading new reports without physically deleting the old template from the BI server. When you try to upload a new template for an existing report (that is: with the same name), Siebel cannot overwrite the existing folder. The result is that your browser session just hangs. The solution is to first delete the folder from the BI server and then upload the new one. Usually report designers won’t have direct access to the reports server, so this may be an issue. Should be solved in 8.1.1.3.

2) The pop-up in which end users can enter report parameters always shows up, even when the report does not allow you to enter extra parameters. This means an extra click for end users.

3) Then the worst of  them all: the reports show up after clicking on the reports button in Siebel. This list can be quite extensive when your organization uses more than about 20 reports. That’s no problem when the list would be nicely sorted alphabetically or even by a sequencing variable. However, the lists gets sorted randomly! It may even differ per view. End users are left confused, looking for where in the list the report shows up this time… This issue was present already before the upgrade, and is promised to be solved in Siebel 8.1.1.3.

What is your experience with Siebel and BI? Feel free to share it in the comments.

 Viewed 4457 times by 991 visitors


Category: CRM / Technical
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses (last comment shown first)

February 24, 2011
Rick

Hi Ed,

That’s we’re we got the Workflow from too. I thought it would be part of the 8.1.1.2 fixpack, but I guess you need to install it separately.

Let me know if you have any other issues!

Regards,
Rick

[Reply to this comment]


February 23, 2011
Ed
Ed

Hi Rick, it’s me again … I found something on the Siebel Support Web (need to have login and password). I’ll follow those instructions and see what I can do …

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETIN&id=823360.1

It basically explains how to call BIP through Workflow or eScript … GOOD !!!

[Reply to this comment]


February 23, 2011
Ed
Ed

Hi Rick, thank you so much for your reply.
We’re running Siebel 8.1.1.4 and BI Publisher 10.1.3.4.1 but I wasn’t able to find this Workflow called “BIP Report Generation” ! Do you know if we need to do something else to be able to visualize it?

[Reply to this comment]


February 23, 2011
Rick

Hi Ed,

Thanks for your reply. Once you have upgraded to the new Siebel/BI situation, you’ll find a workflow called “BIP Report Generation”. This workflow creates a record in the Report Output BC (so the report becomes visible in the My BIP Reports view) and calls the PublicReportService so BI will create the report.

You need to provide the following parameters:
- Report Name (as registered in the Report Administration view)
- Report Output type (pdf/doc/xls etc.)
- Login ID (who is requesting the report, i.e. SADMIN)
- BIP Password (The BIP Password as registered on the Object Manager, to get access to BI)
- BIP Username (The BIP username as registered on the Object Manager, to get access to BI)
- Integration Object (The Integration Objecy needed for the report)
- Bookmark: The query that will be performed for the data to be put into the report, i.e. [Row Id] = ’1-1XLAS’

There are various ways to call this workflow. One is by running a server task, or calling the Workflow Process Manager in eScript.

If you require more help, just let me know.

[Reply to this comment]


February 22, 2011
Ed
Ed

Rick, I have a requirement to generate automatically a report on BI Publisher, but, still I don’t know how to call it through Siebel Workflow or eScript. Do you know if there’s any documentation that could help me to get through this? Thank you in advance….

[Reply to this comment]