Technical data

Database Object Standard
3-2 Oracle Utilities Meter Data Management Database Administrator’s Guide
Database Object Standard
This section discusses the rules applied to naming database objects and the attributes that are
associated with these objects.
Categories of Data
A table can belong to one of the three categories:
Control (admin)
Master
Transaction
For purposes of physical table space design, metadata and control tables can belong to the same
category.
Example of tables in each category:
Control: SC_USER, CI_ADJ_TYPE, F1_BUS_OBJ
Master: CI_PER, CI_PREM,
Transaction: F1_FACT, CI_FT
All tables have the category information in their index name. The second letter of the index carries
this information. See Indexes on page 3-3 for more information.
Naming Standards
The following naming standards must be applied to database objects.
Table
Table names are prefixed with the owner flag value of the product. For customer modification
CM must prefix the table name. The length of the table names must be less than or equal to 30
characters. A language table should be named by suffixing _L to the main table. The key table
name should be named by suffixing _K to the main table.
It is recommended to start a table name with the 2-3 letter acronym of the subsystem name that
the table belongs to. For example, MD stands for metadata subsystem and all metadata table
names start with CI_MD.
Some examples are:
CI_ADJ_TYPE
CI_ADJ_TYPE_L
A language table stores language sensitive columns such as a description of a code. The primary
key of a language table consists of the primary key of the code table plus language code
(LANGAGUE_CD).
A key table accompanies a table with a surrogate key column. A key value is stored with the
environment id that the key value resides in the key table.
The tables prior to V2.0.0 are prefixed with CI_ or SC_.
Columns
The length of a column name must be less than or equal to 30 characters. The following
conventions apply when you define special types of columns in the database.