Results for “view_name”

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

Overview

EDW_PVT_VIEWS_MD_V is a metadata view owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the BIS (Business Intelligence System) product family, which underpins the Oracle EBS data warehousing and business intelligence infrastructure — commonly associated with Oracle Daily Business Intelligence and the Enterprise Data Warehouse (EDW) layer. The view exposes metadata describing the defined "views" that exist within the BIS/EDW private metadata repository, presenting each view's identity, its internal name, a longer logical (business-friendly) name, and a textual description.

In EBS reporting and integration contexts, this object acts as a lightweight dictionary of view definitions rather than a transactional or fact-bearing entity. It allows developers, integrators, and reporting tools to enumerate and resolve the views available within the BIS metadata framework, supporting documentation, discovery, and dynamic report-building scenarios. Its status is recorded as VALID, indicating the underlying definition compiles cleanly against its base object. It is documented as available in both 12.1.1 and 12.2.2, where the ETRM (E-Business Suite Technical Reference Manual) metadata mirrors the same definition.

Underlying Base Objects

According to the documented ETRM metadata, EDW_PVT_VIEWS_MD_V is defined over a single base object: CMPWBVIEW_V. The view itself contains no other referenced base tables. The name prefix "CMP" ties the base object to the BIS component metadata (CMP) family, and the suffix "_V" indicates that the base is itself a view, meaning EDW_PVT_VIEWS_MD_V is layered atop another view rather than directly over physical tables. The view text is a simple projection, mapping the base view's columns into the exposed column set:

SELECT ELEMENTID  VIEW_ID,
       NAME       VIEW_NAME,
       LONGNAME   LOGICAL_NAME,
       DESCRIPTION DESCRIPTION
FROM   CMPWBVIEW_V

The "PVT" segment in the object name reflects the "private" metadata naming convention used throughout the BIS/EDW stack, distinguishing these internal descriptive objects from public-facing reporting views. Because the base object is itself a view, the documented reference list is intentionally shallow; further lineage would require inspecting CMPWBVIEW_V and its own dependencies, which the available metadata does not enumerate.

Key Columns

The view exposes four columns, each carrying metadata rather than business data:

• VIEW_ID — Derived from ELEMENTID on the base object. This is the numeric surrogate identifier uniquely distinguishing each view definition within the BIS metadata repository. Surrogate keys of this form are commonly used as foreign keys by other metadata and reporting-catalog tables.
• VIEW_NAME — Derived from NAME. The internal, technical name of the view, suitable for programmatic resolution and matching against database object names.
• LOGICAL_NAME — Derived from LONGNAME. A longer, human-readable label intended for display to end users and report authors, offering a business-friendly alternative to the terse internal name.
• DESCRIPTION — Derived from DESCRIPTION. Free-text descriptive content explaining the purpose or content of the referenced view, used for tooltips, documentation generation, and metadata browsing interfaces.

Common Use Cases and Queries

Typical uses include metadata discovery, documentation generation, and supporting dynamic report tools that need to enumerate the available BIS views and their human-readable labels. A simple listing returns the full catalog:

SELECT view_id, view_name, logical_name, description
FROM   apps.edw_pvt_views_md_v
ORDER  BY view_name;

To resolve a specific view by its internal name or to search descriptions for a keyword:

SELECT view_id, view_name, logical_name
FROM   apps.edw_pvt_views_md_v
WHERE  UPPER(view_name) LIKE '%SALES%'
   OR  UPPER(logical_name) LIKE '%SALES%';

A join pattern often pairs VIEW_ID with other metadata tables that reference the view identifier, enabling report catalogs and column-level metadata to be linked back to their parent view. Because the object is metadata-only and static in nature, queries are inexpensive and safe to run in production. Access should still respect APPS schema privileges, and any dependence on the base object CMPWBVIEW_V should be verified against the target instance, since private metadata structures can vary between point releases and patch levels.