Results for “edw_fact_attributes_md”

17 results




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

Overview

EDW_FACT_ATTRIBUTES_MD is a metadata repository table owned by the BIS (Business Intelligence System) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Enterprise Data Warehouse (EDW) / Applications BIS module, which supplies the underlying structures used by Oracle Business Intelligence and Daily Business Intelligence reporting. As the name implies, the table stores descriptive metadata about facts — the measurable, quantitative elements of a dimensional model — and the attributes that qualify or describe those facts. It functions as a catalog rather than a transactional store, allowing reporting engines and ETL processes to resolve fact identifiers, attribute identifiers, and key identifiers to their human-readable names.

The ETRM documentation records this object as "Not implemented in this database," meaning it is a delivered seed/metadata definition present in the EBS file system and shipped schema definitions, but not physically instantiated in every installation. Consequently, querying it directly may return an ORA-00942 error unless the EDW metadata build has been executed. The documented physical schema for 12.1.1 shows nine columns.

The heuristic Data Vault classification mined from the foreign key structure is standalone. This classification should be read as a modeling suggestion only: because the table carries its own FACT_ID, ATTRIBUTE_ID, and KEY_ID identifiers without a classic hub-and-satellite chain, it is best treated as an independent reference or configuration structure rather than a conformed Data Vault hub, link, or satellite.

Key Information Stored

The nine documented columns fall into three logical groups — fact, attribute, and key descriptors — each typically expressed as an identifier/name pair.

  • FACT_ID — the identifier of the fact with which the attribute metadata is associated. This is also the documented foreign key, which references ASO_ER_DATA_BIN_FACT, making it the principal business join column.
  • FACT_NAME — the display name of the fact, used by reporting layers to label measures.
  • ATTRIBUTE_ID — the identifier of the attribute (dimension descriptor) attached to the fact.
  • ATTRIBUTE_NAME — the short, user-facing name of the attribute.
  • ATTRIBUTE_LONGNAME — the extended descriptive label of the attribute, typically used in report headings and column captions.
  • ATTRIBUTE_TYPE — the category or classification of the attribute, distinguishing, for example, dimensional versus descriptive attributes.
  • KEY_TYPE — the classification of the key associated with the fact.
  • KEY_ID — the identifier of that key.
  • KEY_NAME — the display name of the key.

No surrogate primary key or unique index is documented in the ETRM metadata. FACT_ID serves as the documented foreign key to ASO_ER_DATA_BIN_FACT and is therefore the most reliable candidate for a business join key.

Common Use Cases and Queries

Typical usage involves resolving fact and attribute identifiers to readable labels for reporting, validating EDW metadata load completeness, and generating data dictionaries.

  • Fact-to-attribute mapping: SELECT a.FACT_NAME, a.ATTRIBUTE_NAME, a.ATTRIBUTE_LONGNAME, a.ATTRIBUTE_TYPE FROM EDW_FACT_ATTRIBUTES_MD a WHERE a.FACT_ID = :fact_id;
  • Join to the fact catalog: SELECT m.FACT_ID, m.FACT_NAME, f.* FROM EDW_FACT_ATTRIBUTES_MD m JOIN ASO_ER_DATA_BIN_FACT f ON m.FACT_ID = f.FACT_ID;
  • Key profile listing: SELECT FACT_ID, KEY_TYPE, KEY_ID, KEY_NAME FROM EDW_FACT_ATTRIBUTES_MD ORDER BY FACT_ID, KEY_TYPE;
  • Metadata completeness audit: rows where ATTRIBUTE_NAME or ATTRIBUTE_LONGNAME is null indicate an incomplete EDW metadata build.

Related Objects

The documented FK establishes the principal relationship; other BIS/EDW catalog objects are commonly referenced alongside it.

  • ASO_ER_DATA_BIN_FACT — referenced by EDW_FACT_ATTRIBUTES_MD.FACT_ID. This is the primary parent object in the documented relationship data.
  • EDW_FACT_ATTRIBUTES_MD column family — ATTRIBUTE_ID, KEY_ID, and FACT_ID are typically resolved in downstream EDW dimension and key metadata tables.
  • BIS schema catalog views — DBI/EDW reporting views that consume fact and attribute metadata for report definition.
  • ASO_ER_DATA_BIN_FACT — also the anchor for the Data Vault heuristic classification, since the sole FK path terminates here.

Because the object is reported as not implemented in the source database, availability should be confirmed per environment before reliance in production SQL.