4Setting Up Siebel Pharma
Setting Up Siebel Pharma
This chapter covers setting up Siebel Pharma. It includes the following topics:
About Setting Up Siebel Pharma
This chapter lists the applications administration tasks that are specific to Siebel Pharma. Use this chapter in combination with Siebel Applications Administration Guide, the main guide for performing administrative tasks.
Siebel Applications Administration Guide covers the setup tasks that are common to all Siebel Business Applications, such as using license keys, defining employees, and defining your company’s structure. It also provides the information you will need to implement, configure, and monitor the Sales, Service, and Marketing products and to perform Data Administration and Document Administration tasks.
Some tasks listed in this chapter might replace those in the administration guide whereas others might be additional tasks. Make sure you review the table in Administrative Setup Tasks for Siebel Pharma before following the procedures in Siebel Applications Administration Guide.
This guide assumes that you have already installed Siebel Life Sciences or completed an upgrade from another Siebel Business Application. If you have not, refer to the Installation/Upgrade section of the Siebel Bookshelf and click the links to the guides that are relevant to your company’s implementation.
The Siebel database server installation script creates a Siebel administrator account that can be used to perform the tasks described in this guide. For information about this process, see the Siebel Installation Guide for the operating system you are using, and Siebel System Administration Guide.
Configuring Pharma Properties in the Siebel Runtime Repository
User properties are object definitions that are added to an applet, business component, control, field, or list column to configure specialized behavior. Some Siebel Pharma features are driven by user properties. You can customize these features through their respective user properties. With user properties, you can control UI behavior, change default settings or leave them as they are, and enable or disable features. For information on enabling and configuring the runtime repository object definitions required for Siebel Pharma, see Siebel Pharma Developer’s Reference.
Enabling Server Component Groups for Siebel Pharma
This system administration task describes how to activate the component groups that are required for Siebel Pharma.
To enable Server component groups for Siebel Pharma
Navigate to the Administration - Server Configuration screen, and then the Component Groups view.
Query for the Workflow Management Component Group.
On the Component Groups applet, click the Enable button.
Query for the EAI Component Group.
On the Component Groups applet, click the Enable button.
Restart the Siebel Server.
Navigate to the Administration – Server Management screen, then the Servers and Component Groups view.
Verify that the State value for the Workflow Management and EAI Component Groups is set to Online.
Navigate to Administration – Server Configuration screen, then the Enterprises and Synchronize view.
Click Synchronize.
Restart the Siebel Server.
Activating Workflows for Siebel Pharma
This system administration task describes how to activate the workflows required for Siebel Pharma. For more information on Siebel workflows, see Siebel Business Process Framework: Workflow Guide.
To activate workflows for Siebel Pharma
Navigate to the Administration - Business Process screen, then the Workflow Deployment view.
Query for Pharma* and activate all of the Pharma workflows.
Verify that each activated workflow is added to the Active Workflow Processes view.
Upgrading Workflows for Sample Transaction Management and Signature Capture in Siebel Open UI
This system administration task describes how to upgrade the workflows required for the Siebel Pharma sample transaction and electronic signature capture features. For more information on Siebel workflows, see Siebel Business Process Framework: Workflow Guide.
To upgrade workflows for electronic signature capture
Navigate to the Administration - Business Process screen, then the Workflow Deployment view.
Query for and activate all of the following workflows:
LS Pharma Sample Transaction Submit
LS Pharma Location Audit Submit
LS Pharma Interim Inventory Count
LS Pharma CloseOut Inventory Count
Verify that each activated workflow is added to the Active Workflow Processes.
For more information, see Activating Workflows for Siebel Pharma.
Navigate to the Administration – Runtime Events screen, then the Events view.
Click Menu (the cogwheel icon), and then select Reload Runtime Events from the drop-down list.
Restart the Siebel Server.
Administrative Setup Tasks for Siebel Pharma
The following information lists the administrative setup procedures that are specific to Siebel Pharma and procedures that might differ from those of the other Siebel Business Applications. The table also directs you to documentation containing information about each task.
When setting up your application, use the following table in combination with the main resource, Siebel Applications Administration Guide.
Table Siebel Pharma Administration Tasks
| Administrative Task | Description | For More Information |
|---|---|---|
Define medical specialties |
|
|
Set up bricks |
|
|
Define decision issues |
|
|
Administer Smart Calls |
|
|
Specifying a Competitor |
|
Administering and Managing Accounts in Life Sciences |
Managing Accounts Contacts in Life Sciences |
|
|
Configuring Time Off Territory |
|
|
Importing Data |
|
|
Administering products |
|
|
Configuring Siebel Pharma |
|
|
Configuring Data for Oracle Pharma Sales Analytics |
|
About the My Team’s Filter
The Show drop-down list is found on many screens. It provides a list of filters such as My Contacts, My Team’s Contacts, and All Contacts. These filters determine what records appear in the view.
The behavior of the My Team’s filter varies from screen to screen. In some screens, this filter displays those records where the primary member of the team reports to the user. In other screens, the filter displays records where any of the team members reports to the user.
This behavior is determined in the business component by the Manager List Mode user property.
If the Manager List Mode user property is active and set to Team, the My Team’s filter displays all records where the user’s subordinate is on the team but is not necessarily the primary member.
The following information lists the default setting of the Manager List Mode user property for some Siebel Life Sciences screens and business components.
Table The Default Setting for the Manager List Mode Use Property
| Screen | Business Component | Manager List Mode |
|---|---|---|
Accounts |
Accounts |
Inactive |
Contacts |
Contact |
Inactive |
MedEd |
Pharma ME Event Professional Invitee |
Active |
Objectives |
Objective |
Active |
Using Assignment Manager in Siebel Pharma
Siebel Assignment Manager allows the Siebel administrator to automatically assign tasks to specific people. To do this, however, the Siebel administrator must first define assignment rules for each task. For more information on using and implementing Siebel Assignment Manager, see Siebel Assignment Manager Administration Guide. For additional information on creating territories and running territory realignments, see Siebel Territory Management Guide.
This topic provides Siebel Assignment Manager information that is specific to Siebel Life Sciences.
Predefined Assignment Objects
Some of the predefined assignment objects and underlying criteria described in Siebel Assignment Manager Administration Guide have been modified in Siebel Life Sciences to support pharmaceutical business processes. The following table describes the assignment objects that are changed in Siebel Life Sciences.
Table Assignment Objects Changes in Siebel Life Sciences
| Assignment Object | Modifications |
|---|---|
Account |
The assignment criteria SIC Code has been renamed Account Class of Trade. Its assignment criteria are:
Account Brick source table has been changed to S_CON_ADDR and source column has been changed to BRICK_ID. |
Contact |
This assignment object was created specifically for Siebel Life Sciences and is not described in Siebel Assignment Manager Administration Guide. The assignment criteria are:
|
Opportunity |
Siebel Pharma includes the Product Line or Product Line Wildcard assignment criteria. |
Contact Assignments in Siebel Life Sciences
In most Siebel Business Applications, assignment of contacts is based on primary address. This process is different for Siebel Life Sciences. A Siebel Life Sciences contact can have multiple addresses, and each representative on the contact’s sales team can indicate a different primary address for the same contact. For this reason, do not base the assignment of contacts on the primary address.
For example, Representative A might indicate a hospital address as the primary address, while Representative B might indicate a private-office address as primary. In the All Contacts and My Team’s Contacts views, the primary address that appears is the one assigned by the primary team member. For more information, see Predefined Assignment Objects.
Contact Denormalization Mode in Siebel Life Sciences
Contact Denormalization mode in Siebel Life Sciences differs from the description in Siebel Assignment Manager Administration Guide in the following ways:
It denormalizes positions from the account team table to the contact team table for all contacts directly affiliated with an account. Users can specify a direct affiliation between a contact and an account by selecting:
The Direct field in the Contacts, Account Affiliations view
The Direct field in the Accounts, Contact Affiliations view
For more information, see Indicating an Affiliation Between an Account and a Contact.
It does not denormalize positions from the opportunity team table to the contact team table.
It must be run after running batch mode jobs for contacts and accounts separately. Run three separate batch mode jobs in this order:
Contacts
Accounts
Contact Denormalization
Contact Denormalization in Siebel Life Sciences has the following additional important rules, requirements, and exceptions:
Running Contact Denormalization mode in Dynamic mode. To activate the Contact Denormalization Policy, set the expiration date to a future date or leave it blank. Then generate the database triggers by running Generate Triggers.
Running Contact Denormalization mode in Batch mode. Remember to specify the parameters:
Object Name = Contact Denormalization Assignment Mode = Denorm
Contact Denormalization mode does not evaluate rules. Therefore, it is not necessary to create a Contact Denormalization rule-based object to run Assignment Manager in this mode. Also, because it does not evaluate rules, Contact Denormalization mode does not set the primary team position.
Contact Denormalization assigns contacts to employees who are on the Account Team for which the contacts are directly affiliated. In order to reduce the number of contact-to-position relationship (S_POSTN_CON) rows routed to the manager's local database, the value of the ASGN_DNRM_FLG field is set to “N". With this default setting, the contacts that team members have been assigned by the Contact Denormalization process will not be visible to managers on their local databases. However, if the desired behavior is for managers to see all contacts that are assigned to their team members, regardless the assignment method, set the ASGN_DNRM_ “Y".
Enforcing Siebel Life Sciences Activity Status Behavior in Other Siebel Applications
The following procedure shows you how to configure the Status field for Activity so that users will not be allowed to select any of the following values manually in the activity Status field.
Signed
Submitted
Synchronized
Signed and Synchronized
This is the default behavior in Siebel Life Sciences applications but you can enforce this Activity Status behavior in other Siebel Applications (such as Siebel Call Center) by completing the following procedure.
After completing the following procedure, if users try to select any of these values manually in the Status field for an activity, then an error message similar to the following appears:
Error message example 1: Wrong field values or value types detected in field Status. Please re-enter your field values. If you need additional assistance, please refer to the documentation. (SBL-UIF-00299)
Error message example 2: Either the status value you have selected is not applicable to this activity type, or you must submit this activity using the Submit button. (SBL-SIS-00181)
To enforce Siebel Life Sciences Activity Status Behavior in other applications
Navigate to the Business Component object type in the runtime repository.
Query for the Action Business Component, then go to Business Component User Prop.
Create the Pharma App Name user property, with the values shown in the following table.
You must use this user property to define the list of comma-separated application names where users will not be allowed to change the activity Status field manually to Signed, Submitted, Synchronized, or Signed and Synchronized.
User Property Name User Property Value Pharma App Name
<application name>,<application name>,<application name>
For example:
Siebel Universal Agent,Siebel Financial Services Mobile,Siebel Call Center
Update the repository and deliver the updates.