4.1.2 Restrictions on using Seed Data

Because Seed Data is maintained by Oracle, it may be modified or even deleted as part of an upgrade. Customers should therefore exercise caution when using seed data in their configuration by abiding these rules.

1. Do not remove (delete) Seed Data rows. A patch may re-insert the row.
2. Do not update columns, other than those indicated as updateble below.
3. Do not make references to rows that may be deleted by Oracle (see table below).

Violations of the rules above (especially rule 3) may lead to failures during the installation of upgrades.

The table below lists the Seed Data tables.

• Data: The table or logical entity
• Updatable columns: The customer may update the values in these columns. They will not be overwritten by upgrade scripts. Other columns should not be updated by the customer.
• Physical Delete: Upgrade scripts may delete this data. The customer should not create references to this data. Example: Do not use OHI messages for your own dynamic checks.

Data	Updatable columns	Physical Delete	Remarks
Access Restrictions		Yes	Also deletes Access Restriction Grants referring to this row
Access Restriction Grants		Yes
Access Roles		No	Two roles are seeded
Boilerplate Texts		Yes
Countries	all _b columns	No
Country Regions		No
Dynamic Field Usages	number_format_type	No
Dynamic Logic	logic	No
Fields (+ dynamic logic)		No
Flex Code Sets (+ details)		No
Flex Code Systems		No
Languages	ind_default ind_installed	No
Messages	ind_suppress_log_in_ui ind_suppress_log_in_ext ind_mark external_code	Yes
Single Flex Code Definitions (+ usage)		No
Task Types		Yes	Customer is not allowed to change anything in base table
Task Type Attributes	value_char value_number value_datetime value_clob	Yes
Activity Types		Yes	Customer is not allowed to change anything in base table
Users		No	One User will be seeded (system user)