Results for “edw_attribute_sets_md_v”

16 results




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

Overview

EDW_ATTRIBUTE_SETS_MD_V is a reporting view registered under the BIS (Business Intelligence System / Oracle Business Intelligence Applications) product family in Oracle EBS 12.1.1 and 12.2.2. The view exposes attribute set metadata used by the Enterprise Data Warehouse (EDW) extraction and load routines that populate attribute-group structures consumed by Oracle Business Intelligence and Discoverer reporting. Its name follows the EDW_*_MD_V convention, indicating a metadata extraction view intended for ETL consumption rather than for interactive end-user querying.

This view surfaces the relationship between an owning relation (typically a configurator or item-set container) and its attribute definitions. In that sense it functions as a bridge between the extensibility/attribute framework used by Oracle Configurator (CMP schema objects) and the BI Applications metadata layer. It is a read-only view, defined WITH READ ONLY, so consumers cannot issue DML against it.

Underlying Base Objects

The documented view text defines EDW_ATTRIBUTE_SETS_MD_V over two base views rather than physical tables:

  • CMPITEMSET_V SIS — the item-set view in the Configurator schema, representing an attribute set (item set) and its owning relation. Only rows where SIS.CLASSNAME = 'CMPWBNAMEDITEMSET' are returned, restricting the result to the named item-set class used by the Configurator workbench.
  • CMPRELATION_V REL — the relation view exposing relation metadata. The join condition SIS.OWNINGRELATION = REL.ELEMENTID links each attribute set to the parent relation that owns it.

No physical base tables are documented for this view; both referenced objects are themselves views. This is consistent with an EDW metadata extraction design that reads from logical, schema-stable sources. The view is documented as "Not implemented in this database," meaning not every EBS instance will contain the underlying CMP* objects without the Configurator/BI components installed and patched.

Key Columns

  • ENTITY_ID — the identifier of the owning relation, sourced from REL.ELEMENTID. This is the anchor key for the attribute-set entity.
  • ENTITY_NAME — the name of the owning relation, sourced from REL.NAME.
  • ATTRIBUTE_GROUP_NAME — the item-set name, sourced from SIS.NAME.
  • ATTRIBUTE_GROUP_ID — the item-set element identifier, sourced from SIS.ELEMENTID.
  • DESCRIPTION — the textual description of the attribute set, sourced from SIS.DESCRIPTION.

The column naming reveals the semantic mapping: an owning "relation" becomes an ENTITY, while its item-set child becomes an ATTRIBUTE_GROUP.

Common Use Cases and Queries

The view is principally queried during EDW metadata loads and during troubleshooting of missing or misnamed attribute groups in BI extracts. Typical usages include enumerating all attribute sets per owning relation, and reconciling entity/attribute-group pairings against expected Configurator definitions.

SELECT ENTITY_ID,
       ENTITY_NAME,
       ATTRIBUTE_GROUP_NAME,
       ATTRIBUTE_GROUP_ID,
       DESCRIPTION
  FROM EDW_ATTRIBUTE_SETS_MD_V;

To list attribute groups for a specific owning relation:

SELECT ATTRIBUTE_GROUP_NAME, DESCRIPTION
  FROM EDW_ATTRIBUTE_SETS_MD_V
 WHERE ENTITY_ID = :relation_element_id;

Because the view is schema-bound to CMPITEMSET_V and CMPRELATION_V, it is only meaningful on instances with the Configurator schema and BI Applications components present. Where the object is "not implemented," queries return an invalid-object error rather than rows, and the ETL should be adjusted to source metadata from the Configurator base views directly.