About Seed Data Responsibilities

Seed data responsibilities provide access to out-of-the-box views for various user types that are found in a given organization. There are over 400 Responsibilities defined and there are over 100,000 mappings from these responsibilities to various Views. While this sounds like a lot, consider all the different types of users within a large organization and the records to which they might need access:

• Sales Representatives. Sales representatives need access to Accounts and Opportunities that they are working on.

• Sales Managers. Sales managers need access to Accounts and opportunities that they or their reports are working on.

• Marketing Managers. Marketing managers need access to all customers in order to conduct marketing campaigns.

• Field Service Engineers. Field service engineers need access to all customers associated with service requests that they are working on.

• Call Center Support Engineers. Call center support engineers need access to all customers since any customer can call and service requests they are working on.

• Fulfillment Center Workers. Fulfillment center workers need access only to requests for literature fulfillment and the contact information for the recipients.

• CEOs. CEOs need access to all customer data. However, the CEOs may have restrictions on the types of changes that they can make and should not be able to modify system administration data. For example, changing Siebel CRM application behavior.

• Application Administrators. Application administrators need access to everything so they can address any issues that may occur.

For these reasons, Oracle engineers have seeded responsibilities to reflect the most common roles seen within an enterprise. This makes it easy to quickly associate a given new user with an existing Responsibility.