Search Results business_name




Overview
Explore in AI Chat

Overview

APPS.EDW_FOREIGN_KEYS_MD_V is a reporting and metadata-exposure view in the Oracle E-Business Suite data warehouse / Enterprise Data Warehouse (EDW) layer. It presents foreign key metadata definitions used to describe relationships between entities in the EDW model. In EBS 12.1.1 and 12.2.2 environments, this view is part of the EDW metadata family, alongside sibling objects such as EDW_FOREIGN_KEYS_MD, which store the physical definitions of foreign key relationships maintained by the EDW tooling.

The view does not store transactional data. Instead, it exposes descriptive metadata: which entity a foreign key belongs to, the foreign key name and identifier, an associated business-facing name, a description, and the identity of the referenced parent key. This makes it valuable for reporting on data model relationships, documenting integration mappings, and driving metadata-driven ETL or data lineage processes.

Because the view surfaces a BUSINESS_NAME column, users searching for "business_name" in the EBS context will often land on this object. The BUSINESS_NAME column provides a human-readable label that is distinct from the internal technical FOREIGN_KEY_NAME, supporting business-friendly reporting and documentation.

Underlying Base Objects

The documented definition of APPS.EDW_FOREIGN_KEYS_MD_V is a straightforward projection over a single base table:

  • EDW_FOREIGN_KEYS_MD — the base table holding foreign key metadata records.

The view selects the following columns from that table, in this order: ENTITY_ID, ENTITY_TYPE, ENTITY_NAME, FOREIGN_KEY_NAME, FOREIGN_KEY_ID, BUSINESS_NAME, DESCRIPTION, KEY_ID, and KEY_NAME.

No additional base objects, joins, filters, or WHERE clauses are documented in the ETRM metadata other than the single-table SELECT. As a result, the view is effectively a renamed or column-exposed alias of its base table, which simplifies administration and allows the EDW metadata layer to present a stable public interface even if the underlying table implementation changes.

Key Columns

  • ENTITY_ID — the internal identifier of the entity to which the foreign key belongs. Typically joins to the EDW entity metadata to resolve the owning object.
  • ENTITY_TYPE — categorizes the entity, distinguishing, for example, tables, views, or other EDW constructs.
  • ENTITY_NAME — the technical name of the owning entity.
  • FOREIGN_KEY_NAME — the technical name of the foreign key constraint or relationship.
  • FOREIGN_KEY_ID — the numeric identifier of the foreign key definition.
  • BUSINESS_NAME — the business-friendly name for the foreign key, intended for user-facing documentation and reports.
  • DESCRIPTION — free-text description explaining the purpose or semantics of the relationship.
  • KEY_ID — identifier of the referenced (parent) key.
  • KEY_NAME — name of the referenced parent key, establishing the relationship target.

Common Use Cases and Queries

The view is most commonly queried to inventory, document, or validate foreign key metadata across the EDW model. Typical scenarios include generating data-model documentation, tracing relationships for ETL mappings, and searching for a relationship by its business-friendly label.

  • Search by business name: retrieve foreign keys whose business name matches a keyword:
    SELECT entity_name, foreign_key_name, business_name, key_name FROM apps.edw_foreign_keys_md_v WHERE UPPER(business_name) LIKE '%CUSTOMER%';
  • List keys for a given entity: SELECT foreign_key_name, business_name, description FROM apps.edw_foreign_keys_md_v WHERE entity_name = :entity;
  • Enumerate all relationships: SELECT entity_name, foreign_key_name, description FROM apps.edw_foreign_keys_md_v ORDER BY entity_name;
  • Resolve relationship targets: join KEY_NAME to the corresponding key metadata to identify the referenced parent key and its entity.

Because the view exposes clean, readable column names including BUSINESS_NAME, it is well suited for metadata repositories, data governance reports, and integration documentation within EBS 12.1.1 and 12.2.2.