Seed Data

This chapter describes seed data provided for your Siebel Business Applications that is relevant to the content of this guide. It also provides information about how to use this data. It includes the following topics:

In the tables in this chapter, the term customer applications represents the group of Siebel Sales, Siebel eService, Siebel Customer, Siebel Events, and Siebel Marketing applications.

Seed Employee

One Employee record is provided as seed data at installation, as described in the following table. This record does not have a database login or a responsibility, but, like other employees, it does have a position and an organization. The PROXYE user record is not installed with a default password.

Customer users, such as Siebel eService users, are not assigned their own position or organization. When a customer user logs in, the application programmatically associates the proxy employee with the user. The proxy employee provides the following functions:

Data subsequently created by the user is associated with the organization of the proxy employee, which allows the data to display in views that implement organization access control.
The user can see data created by the user and by others in views that implement organization access control.

The proxy employee is specified at the application level as a parameter on the Siebel Gateway. For information about organization access control, see Access Control Mechanisms.

Table Proxy Employee Seed Data Field Values

Last Name	First Name	User ID	Responsibility	Position	Organization
Employee	Proxy	PROXYE	None	Proxy Employee	Default Organization

Seed Users

This topic includes information about the following:

Special Users and Privileges: Provides information on the defined special users and privileges within Siebel Business Applications.
Seed Users Provided as Seed Data: Provides information on the seed data provided with Siebel Business Applications in general.
Seed User Modifications for Siebel Financial Services Applications: Provides information on the seed data provided with Siebel Financial Services applications.
About Seed Position and Organization Division Records

Special Users and Privileges

Within Siebel Business Applications, special users are defined with specific roles within the application. Data to support these special user accounts is included in the seed data installed with Siebel Business Applications. You can change special user account names after installation, or delete the relevant seed data for a special user account if you do not need the functionality it provides. Do not, however, disable the system administrator or guest user accounts.

The following special users and privileges are defined:

Anonymous users. You can define an anonymous user (or guest) account to allow access to your Siebel application by unregistered, unauthenticated users. You must also define an anonymous user if your Siebel application implements LDAP authentication.
Three Siebel application user accounts, GUESTCST, GUESTCP, and GUESTERM are provided as seed data for use as anonymous user accounts; however, you can create a different user account for this purpose. Review the user responsibilities assigned to the anonymous user record and limit them to those necessary for sign-on and guest access.
Anonymous browsing is enabled by default. If your Siebel application does not use functionality that requires anonymous browsing, then set the AllowAnonUsers parameter to False. For further information, see Parameters for Application Object Manager Components.
Administrator users. A Siebel administrator database account (default user ID is SADMIN) and a Siebel application user account, SADMIN, are created during the Siebel Business Applications installation process for the administrative user. Follow these guidelines in relation to the administrator user:
- Limit usage of the administrator role.
  Review users with administrative responsibilities. In Siebel Business Applications, the SADMIN responsibility has broad administrative privileges. For this reason, regularly review the list of users with this responsibility. Define and assign appropriate responsibilities for users that clearly reflect their line of duty.
- Delete or disable unused administrator user IDs.
Directory application user. The Directory Application User is a special user defined to handle access to the LDAP directory if this authentication mechanism is used. By setting up an application user as the only user with search, read, and update privileges to the directory, you minimize the level of access of all other users to the directory.
The directory application user must not have a corresponding database account and must not be defined as a Siebel application user or have a Siebel application user record.
Shared database account user. If you are using LDAP or Web SSO authentication, then you can configure a shared database account in the directory; this is a directory entry that contains a database account that is shared by many users. A database login is created for all Siebel users who are authenticated externally during the installation process; the default database login is LDAPUSER. You must also specify a valid Siebel user ID and password for the shared database account in the directory.
An employee record, Proxy Employee, is provided as seed data during installation. This record provides customers (contact users) who log in to a Siebel customer application with a user ID (PROXYE), a position (Proxy Employee), and an organization (Default Organization).
Because the PROXYE user ID gives view access to data that is associated with the related organization, review the visibility to data provided by the proxy employee user ID and, if necessary, change the organization with which the Proxy Employee user record is associated. You cannot change seed data, therefore, to modify the Proxy Employee record you must make a copy of the record, rename it, and amend the copy. For additional information, see Siebel User Accounts.

Seed Users Provided as Seed Data

The following table describes nonemployee user records provided as seed data. Default passwords are not provided for these records. If you use a seed user record as the anonymous user record, then you must set the Anonymous User Name parameter to the seed user ID (for example GUESTCST) when configuring the Application Interface, or set it manually in the Application Interface profile. For information on configuring the Application Interface, see Siebel Installation Guide for the operating system you are using. For information on manually setting passwords for the anonymous user, see Encrypted Passwords in Siebel Application Interface Profile Configuration.

Table User Seed Data Field Values (Nonemployee User Records)

Last Name	First Name	User ID	Responsibility	New Responsibility	Used by These Applications
Customer	Guest	GUESTCST	Web Anonymous User	Web Registered User	Customer applications
Channel Partner	Guest	GUESTCP	Unregistered Partner Agent	Self-registered Partner Agent	Siebel Partner Portal

Seed User Modifications for Siebel Financial Services Applications

The following table shows modifications to the seed nonemployee User records that are provided with Siebel Financial Services applications.

The GUESTCP seed User record, which is documented in Seed Users Provided as Seed Data, functions as the anonymous user for Siebel Financial PRM, the partner application in Siebel Financial Services. The responsibility of the GUESTCP seed User record provides views for anonymous browsing, and the responsibility in its New Responsibility field provides views for users who self-register.

Table User Seed Data Field Values (Modifications for Siebel Financial Services)

Last Name	First Name	User ID	Responsibility	New Responsibility	Used by These Applications
Customer	Guest	GUESTCST	Unregistered Customer	Registered Customer	Siebel Financial Services customer applications
Guest	ERM	GUESTERM	ERM AnonUser		Siebel Financial Services ERM

About Seed Position and Organization Division Records

The Proxy Employee Position and the Default Organization Division records are provided as seed data. The position exists within the division, and the division is its own organization. The position and division are both assigned to the seed data Employee record.

Seed Responsibilities

Responsibility records are provided as seed data, as described in the following table. Responsibilities provided for the seed data User records allow users to see views intended for anonymous browsing, including views from which users can self-register or log in. Other responsibilities are assigned programmatically to self-registering users or are assigned to users manually by internal administrators or delegated administrators.

Note: For all responsibilities provided in seed data, refer to those listed in the Siebel application.

Table Responsibilities Seed Data

Name	Organization	Description	Used by These Applications
Web Anonymous User	Default Organization	Views provided for anonymous browsing	Customer applications
Web Registered User	Default Organization	Views provided for a typical registered user	Customer applications
Web Delegated Customer Administrator	Default Organization	Includes views in the Web Registered User responsibility plus views for administering users	Customer applications
Web Corporate User	Default Organization	Views for eSales corporate user	Siebel eSales
Web Purchasing Manager	Default Organization	Views for eSales purchasing manager	Siebel eSales
Unregistered Partner Agent	Default Organization	Views provided for anonymous browsing	Siebel Partner Portal
Self-Registered Partner Agent	Default Organization	Limited set of views provided for a user who self-registers	Siebel Partner Portal
Partner Relationship Manager	Default Organization	Views for Siebel Partner Portal partner relationship manager	Siebel Partner Portal
Partner Operations Manager	Default Organization	Views for Siebel Partner Portal partner operations manager, including views for administering users	Siebel Partner Portal
Partner Sales Manager	Default Organization	Views for Siebel Partner Portal partner sales manager	Siebel Partner Portal
Partner Sales Rep	Default Organization	Views for Siebel Partner Portal partner sales rep	Siebel Partner Portal
Partner Service Manager	Default Organization	Views for Siebel Partner Portal partner service manager	Siebel Partner Portal
Partner Service Rep	Default Organization	Views for Siebel Partner Portal partner service rep	Siebel Partner Portal
Web Training Manager	Default Organization	Views that allow an administrator to see his or her direct reports’ course and curriculum enrollment information	Siebel Training
Training Administrator	Default Organization	Views that allow administration of courses and enrollees	Siebel Training

Seed Responsibilities for Siebel Financial Services Applications

The following information lists additional seed responsibilities that are provided with Siebel Financial Services applications. Although the seed responsibilities are also included with Siebel Financial Services applications, those responsibilities do not include views specific to Siebel Financial Services applications.

No additional seed responsibilities are provided for registered partner users of Oracle’s Siebel Financial PRM. You must build responsibilities for registered partner users based on their various business roles. You can create new responsibilities, or you can copy and modify seed responsibilities for partner users. For information about creating and modifying responsibilities, see Configuring Access Control.

Table Seed Responsibilities

Name	Organization	Description and Comments	Used by These Applications
Unregistered Customer	Default Organization	Views provided for anonymous browsing.	Siebel Financial Services customer applications, except Siebel Events Manager for Finance. For Siebel Events Manager for Finance, use Web Anonymous User instead.
Registered Customer		Views for a typical registered user. Associate Default Organization with this responsibility before assigning this responsibility to a user.	Siebel Financial Services customer applications, except Siebel Events Manager for Finance. For Siebel Events Manager for Finance, use Web Registered User instead.
ERM AnonUser	Default Organization	Views provided for anonymous browsing.	Siebel Financial Services ERM.
ERM User	Default Organization	Views for a typical registered user.	Siebel Financial Services ERM.
ERM Manager	Default Organization	Views for employee management. Assign this responsibility to managers in addition to a responsibility that contains views for a regular user.	Oracle’s Siebel Financial Services ERM.

Listing Views Associated with Responsibilities

The following procedure describes how to list the views associated with a specific responsibility.

To list the views associated with a responsibility

Navigate to the Administration - Application screen, then the Responsibilities view.
In the Responsibilities list, select a responsibility.
The views for the responsibility appear in the Views list.