Siebel Life Sciences Guide > Configuring Data for Oracle Pharma Sales Analytics > Creating Target Lists Using Oracle Business Intelligence >

About Target List Creator

The following topics outline the components and functionality of the target list creator:

Components

The following components support the Target List Creator functionality:

• Create Target List view. Oracle Business Intelligence Presentation Services includes a report view called Create Target List that displays a link used to initiate a business service in the Siebel Pharma application.
• LS Analytics Target Service business service. The Siebel Pharma application includes a business service called LS Analytics Target Service that provides the data integration capability.

When Target List Creator is used in connected mode, both the Oracle BI Presentation Services and Siebel Application Interface must reside on the same machine so that the Create Target List link can be used within an Oracle BI report. The Oracle BI Open Intelligence Interface also needs to be installed and configured on the Siebel Pharma application server to enable connectivity between the Siebel Pharma business service and the Oracle BI Server. For more information, see Oracle Business Intelligence Infrastructure Installation and Configuration Guide.

Functional Overview and Process

The following outlines the functionality and general process steps of the Target List Creator components:

1. When a user clicks the Create Target List link in an Oracle BI Interactive Dashboard report, a JavaScript function prompts the user to enter a name for the new list. The function then passes this name and the logical SQL for the Oracle BI Query through the Siebel Pharma application to the LS Analytics Target Service business service.
2. The LS Analytics Target Service business service:
   1. Verifies that the field representing the row Id of the target object is the first column selected in the query. For example, if you create a target list for Contacts, then in the default configuration the Contacts.ROW_ID column must be the first column in the query.
   2. The Oracle BI presentation columns that represent the Row Id values are configured in user properties for the LS Analytics Target Service business service. The Account Row Id Fields user property maps to the Oracle BI presentation column for the Siebel Account Row Id. The Contact Row Id Fields user property maps to the Oracle BI presentation column for the Siebel Contact Row Id. If the Oracle BI presentation columns used to store the Row Id values differ from the default configuration, then the column mappings for the user properties can be changed in the Siebel runtime repository.
   3. Then a new target list header record is created in the Siebel Pharma application's database. The List Name is set to the Name entered by the user in the Oracle Business Intelligence dialog box and passed from Oracle Business Intelligence to Siebel CRM.
   4. The LS Analytics Target Service business service then uses the Oracle BI ODBC DSN (OpenDataBase Connectivity Data Source Name) name defined in the Siebel Pharma application's AnalyticsDataSrc to connect back to the Oracle BI server.
   5. The business service executes the logical SQL passed from Oracle Business Intelligence, iterates through the results, and creates a new List Item for each record.
   6. The validate targets user property on the business service can be turned on to provide additional validation by ensuring that the record in Oracle Business Intelligence already exists in the user's local Siebel database. Possible values for the user property are N or Y. The default value is N.

      NOTE:  The business component used for the contact target items is List Mgmt List Member, while the business component used for account list items is SLM List Member - Account. Both of these business components must be present in the List Mgmt business object.

3. After the list is created, the application automatically navigates to the view set in the Business Service's Redirect View User Property. This view must be associated with the List Mgmt Business Object and must have the List Mgmt Lists Business Component as its primary business component. The default view is My List Mgmt Lists View.