Results for “logical_name”

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

Overview

EDW_PVT_SEQUENCES_MD_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BIS (Business Intelligence System) product family. It exposes a denormalized, read-only projection of the sequence definitions maintained within the Enterprise Data Warehouse (EDW) metadata layer, presenting each sequence with a stable identifier, a short name, a logical name, and a descriptive text field. The view serves as the metadata bridge between the physical sequence objects stored in the data warehouse repository and the logical naming conventions consumed by downstream reporting, extraction, and integration processes.

The object holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2, and its structure is identical across both releases, making it a stable reference point for customizations and third-party reporting tools. The "_MD_" token in the name denotes metadata, while "_PVT_" indicates that the view is private to the APPS schema and is not supported for direct customer modification.

Underlying Base Objects

ETRM documentation records the view as defined over a single source object, CMPWBSEQUENCE_V, which itself is a view rather than a base table. The SELECT statement performs a lightweight column rename and projection:

• ELEMENTID is aliased to SEQUENCE_ID
• NAME is aliased to SEQUENCE_NAME
• LONGNAME is aliased to LOGICAL_NAME
• DESCRIPTION is passed through unchanged

No filters, joins, or aggregation clauses are applied, so the view returns one row per sequence record present in CMPWBSEQUENCE_V. Because the underlying object is itself a view, any row-level security, language-dependent naming, or warehouse-specific logic is inherited transparently. The ETRM metadata lists no additional referenced base objects, confirming that CMPWBSEQUENCE_V is the sole and direct lineage source.

Key Columns

• SEQUENCE_ID — The unique numeric identifier of the sequence, derived from ELEMENTID. This value is stable across releases and is the correct join key when linking sequence metadata to other EDW or BIS dictionary objects.
• SEQUENCE_NAME — The short technical name of the sequence, sourced from NAME. This is typically the physical object name used inside the warehouse.
• LOGICAL_NAME — The user-facing or business logical name, sourced from LONGNAME. This is the column most relevant to users searching for "logical_name," since it provides the canonical mapping between a technical sequence and its business-friendly label.
• DESCRIPTION — A free-text narrative explaining the intended purpose, granularity, or usage rules for the sequence, passed through directly from the source view.

Common Use Cases and Queries

Typical scenarios include documenting the EDW sequence inventory, resolving a logical name back to its physical identifier, and validating metadata consistency during upgrades from 12.1.1 to 12.2.2. A representative query retrieving the full inventory is:

SELECT sequence_id, sequence_name, logical_name, description
FROM apps.edw_pvt_sequences_md_v
ORDER BY logical_name;

To resolve a specific business label to its technical counterpart:

SELECT sequence_name, sequence_id
FROM apps.edw_pvt_sequences_md_v
WHERE UPPER(logical_name) = UPPER('&logical_name');

A third common pattern joins this view to other BIS metadata views on SEQUENCE_ID to build end-to-end lineage reports across the warehouse dictionary.