About Seed Data
When the Siebel CRM Database is created, it logically has the following components:
- Physical Structure. The physical structure includes tables, indexes, and a very small number of other database objects. Siebel CRM does not define business logic in database objects. For example, only nominal data validation (such as datatype) is done at the database layer. Siebel CRM does not use stored procedures or triggers in the base product except in rare cases. The physical database is 99% tables and indexes. This allows for the maximum amount of portability across the database platforms that Siebel CRM supports.Note: There are some specific examples where triggers are added later in support of the workflow or integration, but the basic product does not include these at the time of installation.
Repository Data. The Siebel CRM Runtime Repository contains metadata that defines how the Siebel CRM application behaves. For example, it defines which user interface objects a user can see, where to store data at the physical layer, validation rules, and workflow. Repository data is discussed in depth later in this guide and throughout the Siebel Bookshelf.
Seed Data. This is data that is placed in the database to provide the user with basic options before any customization or configuration of the product has occurred. The following are a few examples of seed data:
List of Values. This type of seed data appears in Picklists throughout the Siebel CRM application. For example, consider the possible states for a Service Request record. The possible states can include: New, In Progress, Waiting on Customer, Working, Waiting on Engineering, or Closed. However, different options may apply to an Activity. The possible states for an Activity can include: Planned, Confirmed, In Progress, or Done. A List of Values contains a default set of options for Picklists. For more information about List of Values, see About List of Values.
Currency. Currencies facilitate interactions with the global economy. The Siebel CRM database is seeded with the known world currencies for users to select from and to assist with conversion between them. For more information about currency, see About Currency.
Time Zones. Time zones are a critical component in working with a global economy. Time zones support showing Siebel CRM interactions in the time zone of a given user, but are crucial in determining whether Service Level Agreements are being met. For more information about time zones, see About Time Zones.
Responsibilities. Responsibilities determine which application views a particular user can see. For more information about responsibilities, see About Responsibilities.
The various types of seed data have the following factors in common:
Seed data is placed into the database at the time that the Siebel Database Configuration Wizard runs.
Seed data can be inactivated or supplemented. For example, you may add a new Service Request status or remove an existing one.
Seed data should never be deleted. If it is not wanted or needed, it should be inactivated. The reason for this is that the Siebel Upgrade Process (Incremental Repository Merge, or IRM) will put it back the next time it is run.
Other than activation or inactivation, seed data should not be modified. For example, if you want to eliminate the Closed Service Request status and create a new one named Finished, the recommended approach is to inactivate the Closed record and create a new record for Finished, rather than change Closed directly to Finished.
This avoids issues during the Upgrade IRM process.
In some cases, specific seed data is required for the application to work properly. This is particularly true for objects that have specialized functionality, such as Calendar objects.
Seed data may be modified in each release of Siebel CRM. For example, time zone rules change annually due to local laws. The Oracle Siebel CRM Engineering Team regularly update the time zone seed data to reflect current law.