Results for “biv_act_sum_mv”
25 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIV_ACT_SUM_MV is a materialized view owned by the APPS schema in Oracle E-Business Suite, registered under the FND — Application Object Library product family. Its name and column structure indicate that it serves as a pre-aggregated activity summary, primarily associated with Service (TeleService) incident and service-request analytics. The object collapses transactional detail across multiple time grains (year, quarter, period, week, and day) and multiple business dimensions (incident type, incident severity, product, customer, owner group, and creation channel) into a compact, query-optimized result set.
From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone. This classification should be treated as a modeling suggestion rather than a definitive architectural label. Because a materialized view is a derived, refresh-managed structure rather than a normalized source entity, the standalone classification reflects the absence of outbound hub/link semantics and the presence of a self-contained dimensional grain keyed by the I_SNAP$_BIV_ACT_SUM_MV unique index.
Key Information Stored
The table contains 23 columns. The most significant fall into three categories:
- Time and grouping dimensions: TIME_ID, PERIOD_TYPE_ID, GRP_ID, MV_GROUPING_ID, MV_DAY_ID, MV_WEEK_ID, MV_PERIOD_ID, MV_ENT_QTR_ID, and MV_ENT_YEAR_ID. These columns establish the aggregation grain across multiple calendar hierarchies.
- Business dimensions: INCIDENT_TYPE_ID, INCIDENT_SEVERITY_ID, VBH_CATEGORY_ID, PRODUCT_ID, CUSTOMER_ID, OWNER_GROUP_ID, and SR_CREATION_CHANNEL. These drive slicing and filtering of service activity.
- Measures: FIRST_OPENED_COUNT, REOPENED_COUNT, CLOSED_COUNT, MV_FIRST_OPENED_COUNT, MV_REOPENED_COUNT, MV_CLOSED_COUNT, and MV_COUNT. The
MV_-prefixed measures typically represent the materialized/rolled-up values, while the unprefixed counters hold the base-grain figures.
The unique index I_SNAP$_BIV_ACT_SUM_MV spans the full set of dimensional columns — the MV time IDs, INCIDENT_TYPE_ID, INCIDENT_SEVERITY_ID, VBH_CATEGORY_ID, PRODUCT_ID, CUSTOMER_ID, OWNER_GROUP_ID, SR_CREATION_CHANNEL, and MV_GROUPING_ID — using SYS_OP_MAP_NONNULL to treat nulls as comparable. This index represents the business-key candidate rather than a single surrogate primary key column; no dedicated surrogate PK column is documented in the physical schema.
Common Use Cases and Queries
Typical usage centers on service-request volume, backlog, and resolution reporting. A frequent pattern aggregates activity counts for a given product and period:
- Incident volume trending by year, quarter, or period using MV_ENT_YEAR_ID and MV_ENT_QTR_ID.
- Severity and incident-type breakdowns for SLA and escalation dashboards.
- Customer- and owner-group–level workload analysis using CUSTOMER_ID and OWNER_GROUP_ID.
- Channel-mix reporting across SR_CREATION_CHANNEL.
A representative query joins the materialized view to related dimensions:
SELECT m.MV_ENT_YEAR_ID, m.INCIDENT_TYPE_ID, SUM(m.MV_COUNT) FROM BIV_ACT_SUM_MV m WHERE m.PRODUCT_ID = :product GROUP BY m.MV_ENT_YEAR_ID, m.INCIDENT_TYPE_ID;
Related Objects
The documented foreign keys identify the principal dimensional dependencies:
- CS_INCIDENT_TYPES_B — joined via INCIDENT_TYPE_ID; supplies incident type descriptions.
- CS_INCIDENT_SEVERITIES_B — joined via INCIDENT_SEVERITY_ID; supplies severity definitions.
- FND_DM_PRODUCTS — joined via PRODUCT_ID; supplies the product/application dimension.
- CS_INCIDENTS_ALL / CS_SR_* service objects — the likely transactional source lineage for the aggregated counts.
- FND calendar and grouping tables — underlying the MV_DAY_ID through MV_ENT_YEAR_ID time grain.
-
TABLE: APPS.BIV_ACT_SUM_MV 12.1.1
-
Table: BIV_ACT_SUM_MV 12.2.2
Not implemented in this database·Explore FND module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
TABLE: FII.FII_TIME_DAY 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - FII Tables and Views 12.1.1
This table stores the mapping of leaf nodes from pruned dimension to nodes in the child value sets
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - FII Tables and Views 12.1.1
This table stores the mapping of leaf nodes from pruned dimension to nodes in the child value sets