siebel

This is one of those tasks which is fairly simple to do. However, can be very time consuming considering you have to generate a mapping for an entire/multiple repositories. We've all have had to do this at some point, not enjoying it one bit! Well, here is a code that will save you some time and your sanity :) . The below code generates a screen to Applet, and an Applet to BC mapping which can be then exported to excel. Screen to Applet -  select scr.name "Screen Name"       ,nvl(nvl(ptabi.tab_text, scri.viewbar_text), scr.viewbar_text) "Screen"       ,scrv.sequence "View Seq"       ,vw.name "View Name"       ,vwi.title "View"       ,vw.busobj_name "Business Object"       ,vwti.item_num "Item Num"       ,ap.name "Applet Name"       ,api.title "Applet"       ,ap.buscomp_name "Business Component" from   siebel.s_repository rep        inner join siebel.s_screen scr on scr.repository_id

It is a real divine feeling to watch how Assignment Manager works. One of the joys of AM is system takes care of assigning everything you have created. But as they say, Devi-lies-in-details, issue starts when you dig deep. Recently we were asked to implement AM for assignment of Service Request only to Logged in Employees. System should not assign SR to any employee which is not available in system. First look of this problem seems this to be a cake walk. We created Employee availability as skill which was updated every time when he logs in our logs out of the system. But however on actual implementation we realized that skills of employees were not getting refreshed dynamically. It required "Release" button to be pressed every time in order to flush the employee skills and to update rulecache.dat file. Once again Support Web came to rescue and job was saved. When the employees to assign are not Dynamic Candidates, AM during assignment looks into the cache for the candidate e

Siebel provides various ways of achieving the same solution, but you need to do the analysis beforehand to pick the right one. Recently I got one basic requirement that: As soon as the Opportunity Sales Stage gets "Approved", all the Activities (Child of Opportunity) status should automatically set to "Approved". Any Siebel Geek can offer multiple ways to achieve this solution: 1. Write a small

Continuing in the vein of BIP Reporting series, lets discuss another reporting requirement. "Generate the SLA for the Service Request based on the associated Agreement and add the generated SLA as attachment to the Service Request." The closest solution which i was able to achieve was based on the support web solution "Siebel BI Publisher 8 Reports Business Service [ID 823360.1]". The key idea here is to generate BIP report and associate that report as attachment to the Service Request. Below workflow was created in order to accomplish the desired task. Lets discuss each step in detail. 1 - Report Output This subprocess step invokes the "BIP Create Report Output" workflow process. This workflow creates a new record in the "Report Output BC" buscomp to be used in next step. Input Arguments SubProcess Input: Report Name Type: Literal Value: SR SLA Report The input is name of BIP Report to be executed. Output Arguments PropertyName: ReportId Type:

Welcome to the world of BI Publisher. BIP reports can be soother for those who are bitten by actuate. Architecture wise both works same but the key ease is in the development of report template for BIP. A typical comparison between Actuate and BIP is depicted below. With Siebel 8.1.x.x release and BIP Enterprise server 10.1.3.4, we have tightly coupled integration with BIP reports just like actuate. However users on earlier versions can still avail benefits of BIP reports. Reports can be written in BI Publisher using web services or SQL to retrieve data from the siebel application. The reports can be executed from siebel application on button click with flexibility of passing parameters at run time. The attached document from oracle unearth the secrets of executing reports. Happy Reporting!!

The best part from oracle is they keep coming with patches and tough part is we need to adhere them. In siebel 8.0 we were not having built in integration with BIP reports so one has to resort to either web service call or SQL strategy for executing BIP reports. With advancement of 8.1.x we have tightly coupled integration with BIP reports. With integration comes authentication. Typically there are several options to choose for configuring security and authentication for Siebel Reports. When using WebServices or SQL based reports generally "Web Single Sign-On Authentication" mechanism is used as it requires Users logging into BI Publisher via its administrative interface. However this authentication fails when one is using integration based approach which comes with Siebel 8.1. Since the release of Siebel 8.1.1.1 and BI Publisher 10.1.3.4.1 a new security model is introduced in BI Publisher, Siebel Security. When using the Siebel Security model, BI Publisher relies on Siebel