Results for “vbh_category_id”

50+ results




Overview
Explore in AI Chat

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

Overview

ISC_FS_011_MV is an APPS-owned materialized view registered as a table within the FND — Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. Despite its placement under FND, the object's naming and column structure indicate it belongs to the Oracle E-Business Suite supply chain intelligence / demand signal repository (ISC) family of analytical summary objects. It functions as a pre-aggregated fact container that consolidates incident, severity, and product-related counts across multiple time grains and organizational hierarchies, allowing reporting tools and dashboards to query summarized results without repeatedly scanning base transaction tables.

Because it is a materialized view, the object carries the status VALID and is refreshed through the standard materialized view refresh mechanisms available in EBS (DBMS_MVIEW or scheduled concurrent programs). Its physical schema is documented with 22 columns, and a single unique index — I_SNAP$_ISC_FS_011_MV — is present, which serves as the business-key candidate for the materialized view. The unique index is built on a broad combination of non-nullable dimension identifiers including MV_ENT_YEAR_ID, MV_ENT_QTR_ID, MV_PERIOD_ID, MV_WEEK_ID, MV_DAY_ID, PARENT_DISTRICT_ID, RECORD_TYPE, DISTRICT_ID, DISTRICT_ID_C, INCIDENT_SEVERITY_ID, VBH_CATEGORY_ID, PRODUCT_ID, CUSTOMER_ID, GRP_ID, and MV_GRP_ID.

From a heuristic Data Vault modeling perspective, this object presents as a standalone entity with no inferable parent hub or link structure within the mined foreign-key graph; the metadata's classification is "standalone." This suggests that if the object were to be re-modeled under Data Vault principles, it would most closely resemble a satellite-like summary table attached to multiple dimension hubs rather than a true hub or link.

Key Information Stored

The 22 documented columns organize into three functional groupings: time dimensions, organizational/product dimensions, and aggregate measures.

  • Time dimensions: TIME_ID and PERIOD_TYPE_ID anchor the record to a reporting period. The materialized view further decomposes time into MV_DAY_ID, MV_WEEK_ID, MV_PERIOD_ID, MV_ENT_QTR_ID, and MV_ENT_YEAR_ID, enabling drill-down across daily, weekly, period, quarterly, and yearly grains.
  • Organizational dimensions: GRP_ID, MV_GRP_ID, PARENT_DISTRICT_ID, DISTRICT_ID, and DISTRICT_ID_C capture the hierarchy of group and district assignments, allowing roll-ups by organizational unit.
  • Category dimensions: CUSTOMER_ID, PRODUCT_ID, VBH_CATEGORY_ID, INCIDENT_SEVERITY_ID, and RECORD_TYPE classify each summarized row.
  • Base and derived measures: FTF_COUNT and NON_FTF_COUNT represent base counts, while MV_COUNT, MV_FTF_COUNT, and MV_NON_FTF_COUNT hold the materialized aggregate values.

The documented foreign keys show that PRODUCT_ID references FND_DM_PRODUCTS and INCIDENT_SEVERITY_ID references CS_INCIDENT_SEVERITIES_B, confirming integration with product master data and incident severity reference data. No explicit surrogate primary key column is documented; the unique index on the dimension combination acts as the addressing key.

Common Use Cases and Queries

Typical usage centers on incident-related trend and severity reporting by product, customer, and district. Analysts query the materialized view directly, filtering on the time grain that matches the reporting requirement.

A representative query aggregates counts by severity and product for a given period:

  • SELECT p.product_name, s.severity_name, SUM(m.MV_COUNT) total_count FROM apps.isc_fs_011_mv m JOIN apps.fnd_dm_products p ON m.product_id = p.product_id JOIN apps.cs_incident_severities_b s ON m.incident_severity_id = s.incident_severity_id WHERE m.mv_ent_qtr_id = :qtr AND m.mv_ent_year_id = :yr GROUP BY p.product_name, s.severity_name;

Another common pattern compares FTF versus non-FTF activity across districts:

  • SELECT m.district_id, SUM(m.MV_FTF_COUNT) ftf, SUM(m.MV_NON_FTF_COUNT) non_ftf FROM apps.isc_fs_011_mv m GROUP BY m.district_id;

Refresh scheduling is handled through the materialized view's refresh group, and dashboards typically rely on this object to avoid full scans of the underlying incident transaction tables.

Related Objects

The most significant related objects, derived from documented foreign-key and dependency relationships, include:

  • FND_DM_PRODUCTS — referenced by ISC_FS_011_MV.PRODUCT_ID; supplies product master attributes.
  • CS_INCIDENT_SEVERITIES_B — referenced by ISC_FS_011_MV.INCIDENT_SEVERITY_ID; supplies severity codes and descriptions.
  • ISC_FS_011 (base source object) — the underlying query source from which the materialized view is populated, where used.
  • Time dimension tables corresponding to TIME_ID, MV_DAY_ID, MV_WEEK_ID, MV_PERIOD_ID, and MV_ENT_QTR_ID/MV_ENT_YEAR_ID — typically the standard GL or calendar period definitions.
  • District and group dimension tables referenced by DISTRICT_ID, PARENT_DISTRICT_ID, GRP_ID, and MV_GRP_ID.
  • Customer master (CUSTOMER_ID) and VBH category reference data (VBH_CATEGORY_ID) for classification joins.

Because the object is a materialized view, no DML APIs are defined against it directly; all maintenance occurs through refresh programs, and consuming reports should treat it as read-only.