Results for “resolved_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIV_B_AGE_H_SUM_MV is a materialized view registered in the APPS schema and catalogued under the FND — Application Object Library product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Despite the TABLE object type designation in ETRM, the "_MV" suffix and the presence of an auto-generated unique index (I_SNAP$_BIV_B_AGE_H_SUM_MV) confirm that this object is a materialized view capturing pre-aggregated snapshot data, refreshed on a scheduled basis. It belongs to the Business Intelligence reporting layer used by Oracle's Service (TeleService / iSupport) analytics, specifically the incident backlog ageing dashboards. The object's grain is one row per combination of report date, incident type, severity, resolution status, and a three-level category hierarchy (top node, parent category, child category).

From a Data Vault modeling perspective, the mined classification is standalone. This is a heuristic suggestion only: no downstream foreign-key dependents were detected, and the object functions as a denormalized reporting aggregate rather than a true hub, link, or satellite. Its two outbound foreign keys to CS_INCIDENT_TYPES_B and CS_INCIDENT_SEVERITIES_B simply anchor the aggregate to their respective reference dimensions.

Key Information Stored

The materialized view exposes 43 columns, organized into a dimensional key set and three parallel metric families. The most significant columns are:

• REPORT_DATE — the snapshot date on which the ageing measurement was taken; first component of the business-key index.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B, identifying the incident classification.
• INCIDENT_SEVERITY_ID — foreign key to CS_INCIDENT_SEVERITIES_B, identifying the severity level.
• VBH_TOP_NODE_FLAG, VBH_PARENT_CATEGORY_ID, VBH_CHILD_CATEGORY_ID — the three-level category hierarchy used to roll up incidents for reporting.
• RESOLVED_FLAG — indicates whether the incidents in the row were resolved at snapshot time.
• BACKLOG_COUNT / TOTAL_BACKLOG_AGE — count of open backlog incidents and their aggregate age.
• ESCALATED_COUNT / TOTAL_ESCALATED_AGE — count of escalated incidents and aggregate age.
• UNOWNED_COUNT / TOTAL_UNOWNED_AGE — count of incidents without an assignee and aggregate age.
• BACKLOG_AGE_B1 … BACKLOG_AGE_B10, ESCALATED_AGE_B1 … B10, UNOWNED_AGE_B1 … B10 — thirty bucket columns distributing each metric across ten ageing bands.

No separate surrogate primary key column is documented. The business-key candidate is the unique index I_SNAP$_BIV_B_AGE_H_SUM_MV, built over REPORT_DATE, INCIDENT_TYPE_ID, VBH_TOP_NODE_FLAG, VBH_PARENT_CATEGORY_ID, VBH_CHILD_CATEGORY_ID, INCIDENT_SEVERITY_ID, and RESOLVED_FLAG using SYS_OP_MAP_NONNULL to permit null-safe uniqueness. Note that INCIDENT_SEVERITY_ID appears twice in the index definition as documented.

Common Use Cases and Queries

The primary use case is incident ageing and backlog reporting: trend analysis of open versus resolved incidents, escalation tracking, and identification of unowned queues exceeding service-level thresholds. A typical query aggregates the ten buckets for a rolling window:

• Backlog trend by type: SELECT report_date, incident_type_id, SUM(backlog_count), SUM(total_backlog_age) FROM biv_b_age_h_sum_mv WHERE report_date BETWEEN :from_date AND :to_date GROUP BY report_date, incident_type_id;
• Escalation ageing drill-down: select the bucket columns (ESCALATED_AGE_B1 through B10) filtered by VBH_CHILD_CATEGORY_ID to isolate categories breaching thresholds.
• Unowned queue monitoring: compare UNOWNED_COUNT against BACKLOG_COUNT to compute the proportion of unassigned incidents per severity.
• Resolved-flag split: constrain RESOLVED_FLAG to partition performance reporting between cleared and outstanding work.

Because the object is a materialized view, queries are read-only and should never be issued as DML targets. Refresh timing dictates data currency, so dashboards should display the last refresh timestamp alongside results.

Related Objects

• CS_INCIDENT_TYPES_B — joined on INCIDENT_TYPE_ID; supplies incident type descriptions for drill-down.
• CS_INCIDENT_SEVERITIES_B — joined on INCIDENT_SEVERITY_ID; supplies severity names and ordering.
• CS_INCIDENTS_ALL_B / CS_INCIDENTS_ALL_TL — the underlying transactional incident tables from which the aggregate is derived; useful for row-level validation.
• CS_INCIDENT_CATEGORIES_B — source of the VBH parent and child category identifiers.
• BIV_B_AGE_H_SUM (base table/other snapshot) — the non-materialized counterpart, if present, from which the MV refresh is driven.
• Associated BIV reporting MVs for backlog, escalation, and ownership metrics that share the same dimensional grain.