Results for “isc_fs_009_mv”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ISC_FS_009_MV is a materialized view registered in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2, delivered under the FND – Application Object Library product family. In practice, the ISC_ prefix and the column profile (incident severity, customer, product, district, and time-to-resolve buckets) place this object within the Oracle Service / TeleService (CS) reporting lineage, where it serves as a pre-aggregated snapshot used by service analytics dashboards and concurrent reporting programs.
The _MV suffix indicates that the physical segment stored under this name is a materialized view rather than a base transactional table. The ETRM registry records 41 columns and a unique index named I_SNAP$_ISC_FS_009_MV, whose name and use of SYS_OP_MAP_NONNULL confirm Oracle’s materialized-view refresh infrastructure (a snapshot log / index mechanism) rather than a hand-built application index.
Regarding Data Vault classification, the metadata returns a heuristic label of standalone. Two foreign keys are documented (PRODUCT_ID to FND_DM_PRODUCTS and INCIDENT_SEVERITY_ID to CS_INCIDENT_SEVERITIES_B), but the absence of a shared hub key structure across the remaining dimensions suggests that this object is best modeled as a satellite-style reporting aggregation rather than a conformed hub or link. Any Data Vault implementation should treat it as a derived, refreshable reporting artifact and not as a system of record.
Key Information Stored
The unique index reveals the object’s business-key candidate set, which is essentially the full dimensional grain of the aggregate:
- TIME_ID / MV_DAY_ID / MV_WEEK_ID / MV_PERIOD_ID / MV_ENT_QTR_ID / MV_ENT_YEAR_ID — the time dimension at multiple grains, from day through enterprise year and quarter.
- PERIOD_TYPE_ID — identifies the active period type driving the rollup.
- GRP_ID / MV_GRP_ID — grouping identifiers used to scope the aggregate to a resource group or organizational bucket.
- PARENT_DISTRICT_ID / DISTRICT_ID / DISTRICT_ID_C — the district hierarchy, including a child (DISTRICT_ID_C) and its parent, supporting rollup reporting.
- CUSTOMER_ID — the customer affected by the incident.
- PRODUCT_ID — foreign key to FND_DM_PRODUCTS, identifying the product in scope.
- VBH_CATEGORY_ID — the service request category classification.
- INCIDENT_SEVERITY_ID — foreign key to CS_INCIDENT_SEVERITIES_B, defining severity (for example, critical, high, medium).
- RECORD_TYPE — discriminator distinguishing record types within the snapshot.
The measure columns are split into two families. The base measures — RESOLVED_COUNT, TOTAL_TIME_TO_RESOLVE, and TIME_TO_RESOLVE_B1 through TIME_TO_RESOLVE_B10 — hold incident resolution counts and time-in-bucket values. The corresponding MV_ prefixed columns (MV_COUNT, MV_TOTAL_TIME_TO_RESOLVE, MV_TIME_TO_RESOLVE_B1 through MV_TIME_TO_RESOLVE_B10) hold the materialized aggregate values at the refresh grain. No surrogate single-column primary key is documented; the composite unique index over the dimensional attributes functions as the logical key.
Common Use Cases and Queries
Typical usage is service-performance reporting: incident volume and resolution-time distribution by severity, product, district, and period. A representative query aggregates the MV_ measures across a fiscal year:
SELECT mv_ent_year_id, incident_severity_id, SUM(mv_count), SUM(mv_total_time_to_resolve) FROM isc_fs_009_mv WHERE record_type = :p_record_type GROUP BY mv_ent_year_id, incident_severity_id;- Drill-down by district hierarchy: filter on
PARENT_DISTRICT_IDto obtain all subordinateDISTRICT_IDrows. - Bucket distribution analysis: compare
MV_TIME_TO_RESOLVE_B1throughMV_TIME_TO_RESOLVE_B10to profile how resolution times cluster against SLA thresholds. - Trend comparison across
MV_DAY_ID,MV_WEEK_ID, andMV_PERIOD_IDfor the same dimensional filters.
Because the object is a refreshable snapshot, reporting programs should query it read-only and account for staleness of the last refresh. It is not advisable to insert or update rows directly; DML against the underlying base tables is the supported path.
Related Objects
- FND_DM_PRODUCTS — joined on
ISC_FS_009_MV.PRODUCT_ID = FND_DM_PRODUCTS.PRODUCT_IDto resolve product descriptions. - CS_INCIDENT_SEVERITIES_B — joined on
ISC_FS_009_MV.INCIDENT_SEVERITY_ID = CS_INCIDENT_SEVERITIES_B.INCIDENT_SEVERITY_IDfor severity labels. - CS_INCIDENT_SEVERITIES_TL — translation table for severity names, joined through the base severity row.
- FND_DM_ time and district dimension tables — referenced through
TIME_ID,MV_DAY_ID, and the district columns to enrich calendar and hierarchy context. - CS_INCIDENTS_ALL and CS_INCIDENT_ACTIVITIES — the base transactional sources from which the resolution measures are derived.
- Service analytics concurrent programs and dashboards — the consumers that read the materialized snapshot at each refresh cycle.
-
TABLE: APPS.ISC_FS_009_MV 12.1.1
-
Table: ISC_FS_009_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: BIS.BIS_BUCKET 12.1.1
-
TABLE: FII.FII_TIME_DAY 12.1.1
-
12.1.1 DBA Data 12.1.1
-
TABLE: ISC.ISC_FS_TASKS_F 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 - BIS Tables and Views 12.1.1
-
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 - BIS Tables and Views 12.1.1
-
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