Results for “importance_level”

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

Overview

BIL_DIMV_SRV_SVTYS is a reporting view within the BIL (Sales Intelligence) product family, documented in Oracle ETRM as the "Service incident severities view." It exposes the set of incident severity definitions used by Oracle Service (CS) modules, presenting them in a denormalized, dimension-style shape suitable for consumption by the Sales Intelligence (BIL) analytical schema. In Oracle EBS 12.1.1 and 12.2.2, BIL is designated Obsolete, and the ETRM metadata explicitly records that this view is "Not implemented in this database." Consequently, BIL_DIMV_SRV_SVTYS is not a runtime object in a standard 12.1.1 or 12.2.2 installation; it exists as documented metadata and as a historical artifact of earlier Sales Intelligence releases. Its role, where present, is that of a dimension view supplying severity attributes to BIL fact and dimension builds, rather than an operational view used by transaction forms.

Underlying Base Objects

The documented view text defines BIL_DIMV_SRV_SVTYS as a UNION ALL of two branches over base tables not enumerated in the ETRM "referenced base objects" field (which is empty). The branches are:

• CS_INCIDENT_SEVERITIES_B — the base table holding incident severity records, joined to CS_INCIDENT_SEVERITIES_TL for translated name and description.
• FND_LOOKUPS — restricted to LOOKUP_TYPE = 'BIL_VALUE_TYPE' and LOOKUP_CODE = '-999'.

The first branch filters on INCIDENT_SUBTYPE = 'INC' and applies an effective-date test using TRUNC(SYSDATE) against START_DATE_ACTIVE and END_DATE_ACTIVE (with NVL defaults). The translation join matches on INCIDENT_SEVERITY_ID and filters LANGUAGE = USERENV('LANG'). The second branch synthesizes a placeholder row: it coerces the lookup code to a number for INCIDENT_SEVERITY_ID, truncates MEANING to 30 characters for NAME and INCIDENT_SUBTYPE, and assigns a literal IMPORTANCE_LEVEL of -999. The view is defined WITH READ ONLY.

Key Columns

• INCIDENT_SEVERITY_ID — Primary identifier of the severity, sourced from CS_INCIDENT_SEVERITIES_B or derived from the -999 lookup code.
• NAME — Translated severity name (CS_INCIDENT_SEVERITIES_TL.NAME), truncated to 30 characters in the lookup branch.
• DESCRIPTION — Translated severity description.
• IMPORTANCE_LEVEL — Numeric ranking of severity; -999 in the synthetic lookup row.
• INCIDENT_SUBTYPE — Set to 'INC' for real severities; the lookup branch stores a truncated MEANING.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Active date range governing the effective-date filter.
• ID — Character form of INCIDENT_SEVERITY_ID (TO_CHAR in branch one; raw LOOKUP_CODE in branch two).
• VALUE — Only populated in the FND_LOOKUPS branch, mirroring the truncated meaning.

Common Use Cases and Queries

The view supports severity lookups in BIL extraction and reporting, including a sentinel "unknown/unclassified" member via the -999 lookup row. A typical query is:

• SELECT INCIDENT_SEVERITY_ID, NAME, DESCRIPTION, IMPORTANCE_LEVEL FROM BIL_DIMV_SRV_SVTYS ORDER BY IMPORTANCE_LEVEL;
• SELECT ID, VALUE FROM BIL_DIMV_SRV_SVTYS WHERE INCIDENT_SEVERITY_ID = -999;
• Joining the view to incident fact data on INCIDENT_SEVERITY_ID to resolve severity labels.

Because the object is obsolete and not implemented in 12.1.1/12.2.2, equivalent reporting should target CS_INCIDENT_SEVERITIES_B/TL directly. The ETRM metadata contains no owner or referenced-base-object detail, so this summary is grounded primarily in the documented view text.