Data Dictionary for the Views – BriteCore Support

Categorized SQL Views with Descriptions

Below is a categorized list of available logical and materialized views used in the SQL Editor, along with brief descriptions to guide usage. Materialized or m_ views receive date arguments, "as of date" or "start/end date". These views are materialized for better performance, they are our primary "facts" tables. v_ views are mostly dimensional datasets that can be used for joins. Or more fine control when needed.

Use the following query to generate a Data Dictionary of every available View in the SQL Editor: select * from v_logical_catalog;

View Name	Category	Description
`m_inforce_policies`	Policies	Active in-force policies with status and date logic applied.
`m_premium_terms`	Premiums	Premium term breakdowns by policy and time period.
`m_premium_transactions`	Premiums	Premium-related transactions, adjustments, and payments.
`v_account_history`	Accounting	General ledger-style entries showing transaction history.
`v_addresses`	Core Entities	Normalized address records for all contacts and properties.
`v_built_measures`	Properties	Standardized building data for properties (e.g., square footage).
`v_claim_change_log`	Claims	Historical log of claim modifications and updates.
`v_claim_items`	Claims	Items associated with claims, such as vehicles or property.
`v_claim_payments`	Claims	Payments are issued on claims, including loss and recovery.
`v_claims`	Claims	Master claim records including identifiers and status.
`v_claims_contacts`	Claims	Relationships between claims and involved contacts.
`v_claims_dates`	Claims	All date milestones related to claims lifecycle.
`v_claims_perils`	Claims	Perils associated with each claim (e.g., fire, hail).
`v_commission_details`	Commissions	Line-item detail for commissions payable.
`v_commission_payments`	Commissions	Payments made to producers and agencies.
`v_contact_relationships`	Core Entities	Relationships between different contacts.
`v_contacts`	Core Entities	Contact information for individuals and organizations.
`v_dates`	Core	Standardized set of dates used in related modules.
`v_files`	Core	File attachments such as images or documents.
`v_insureds`	Policies	Named insureds and associated metadata.
`v_logical_catalog`	Metadata	Technical metadata about views, templates, and logic.
`v_losses_incurred`	Claims	Total calculated incurred loss on claims.
`v_notes`	Core	Internal notes logged throughout the system.
`v_payment_batches`	Payments	Grouped payment transactions for processing.
`v_payments`	Payments	Individual payment records across modules.
`v_permission_rules`	Security	Permissions and access rules assigned to roles.
`v_policy_type_items`	Policies	Line-level items defined by policy type.
`v_policy_types`	Policies	Policy type definitions used across quoting.
`v_properties`	Properties	Property-level data such as addresses and types.
`v_property_items`	Properties	Items located at properties such as buildings or valuables.
`v_recoveries`	Claims	Recoverable amounts including subrogation.
`v_return_premium`	Premiums	Calculated or refunded premium amounts.
`v_revision_items`	Audit	Item-level changes across policy revisions.
`v_revisions`	Audit	Master audit records for policy changes.
`v_revisions_agencies`	Audit	Agency details tied to policy revisions.
`v_revisions_contacts`	Audit	Contact data tied to specific policy revisions.
`v_roles`	Security	User roles and associated metadata.

Categorized SQL Views with Descriptions

Related articles