Reporting Table Design

To facilitate reporting from the application data database, a secondary set of views is created that combines the various individual tables from the application data design into a format that is better suited for generating reports.

Table 1 lists the naming convention for these tables and views.

Where <OBJECT_TYPE> is the name of the type of object, and <ENUMERATION> is the name of a multivalued enumerated string field.

Table 1. Reporting Table Naming Convention
Naming convention	Description
`RV_<OBJECT_TYPE>` (`RV_` with a single underscore)	Object view For example, `RV_ENTITY`
`RT_<OBJECT_TYPE>_<ENUMERATION>` (`RT_` with a single underscore)	Multivalued enumeration table For example, `RT_RISKASSESSMENT_DOMAIN`
`RT__<OBJECT_TYPE>_<OBJECT TYPE>` (`RT__` with a double underscore)	Relationship table between 2 object types For example, `RT__ENTITY_PROCESS`

Important:

Oracle has a limitation of 30 characters for a table name. Some table names will be truncated.
The RV views are different from the RT tables in that the views have data security built into them while the RT tables do not.

Most objects that are defined in IBM OpenPages® with Watson™ will have both an RV_<OBJECT_TYPE> view and an RT_<OBJECT_TYPE> table in the database. However, joining tables do not have views because they do not need security. When using direct SQL, it is preferable to use the RV views due to the data security code being already present.

The relationship tables represent the parent-child relationships that are defined during the installation of your system.

The enumeration tables store the relationship of objects to enumerated strings in proper relational form.

These tables are automatically generated based upon the settings in OpenPages with Watson. For more information, see the IBM OpenPages with Watson Administrator's Guide.