Oracle Insurance Alternative Reimbursement for Health Installation Guide Release 2.12.1.0.0 Part Number E38168-01 |
|
|
PDF · Mobi · ePub |
Seed data is maintained by Oracle. Customers should not change this data. It is delivered as part of a release and may be updated by software upgrades. There is currently no data in this category. (see the Restrictions on using Seed Data section below).
This category covers specific data that is required by localizations. The data is maintained by Oracle. Customers should not change this data. It is delivered as part of a release and may be updated by software upgrades. Examples:
Field definitions to configure arrangement types, member period types or setting sheets
Flex code definitions to configure arrangement types or setting sheets.
Sample data is provided by Oracle to give you a headstart during configuration. This is data configured by Implementation Consultants. It is not modified during future upgrades. Tables containing Sample Data include:
Table Name | Remarks |
---|---|
Active-Time Patterns | |
Benefits | |
Brands | |
Flex Codes | |
Product Lines | |
Funding Arrangements | |
Member Period Types | |
Product Benefit Categories | |
Product Benefit Parameter Types | |
Product Benefit Parameters | |
Product Benefits | |
Products | |
Reference Information Selection Pattern Types |
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.
Do not remove (delete) Seed Data rows. A patch may re-insert the row.
Do not update columns, other than those indicated as updateable below.
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
Updateable 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 | Updateable 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 | No | ||
Dynamic 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 | |
Users | No | One User will be seeded (system user) |