Results for “attribute_application_id”

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

Overview

OE_DEF_RELATED_ATTR_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the ONT (Order Management) product family but is technically built on the Oracle Application Object Library (AK) attribute and foreign-key metadata layer rather than on operational order tables. The view exposes the relationships between attributes of an object and the attributes of a foreign-key-related object, effectively describing how a given attribute in an entity is linked to a corresponding attribute in a parent or referenced entity through the AK foreign-key definition.

Its role in EBS reporting and integration is metadata discovery. Because it resolves database object names, attribute codes, application identifiers, and column names together, it is valuable when building generic or dynamic code that needs to understand entity relationships — for example, Flexfield-based validations, cross-entity data extraction, or generic attribute-driven interfaces. The presence of DATABASE_OBJECT_NAME in the projection aligns with the common search term "database_object_name," which is the primary grouping column of the view.

Underlying Base Objects

The view is defined over the following documented base objects:

• AK_OBJECT_ATTRIBUTES_VL (VIEW) — provides the object name, attribute code, attribute application ID, attribute label, and column name for both the primary and related objects; referenced twice (aliases OA and OA2).
• AK_FOREIGN_KEYS (SYNONYM) — supplies foreign-key and unique-key relationship definitions; referenced three times (FK1, FK2, FK3).
• AK_FOREIGN_KEY_COLUMNS (SYNONYM) — maps foreign keys to constituent attributes; referenced twice (FKC1, FKC2).
• AK_UNIQUE_KEYS (SYNONYM) — provides the unique-key definition that anchors the referenced object; referenced once (UK).

The joins walk from a primary object attribute through its foreign-key column (FKC1/FK1), to the owning unique key (FK2/UK), and then to the foreign-key columns (FKC2) and attributes (OA2) of the related object. DISTINCT is applied to collapse duplicate combinations produced by the multi-way foreign-key joins.

Key Columns

• DATABASE_OBJECT_NAME — the database object (table) that owns the originating attribute.
• ATTRIBUTE_CODE — the code identifying the originating attribute.
• ATTRIBUTE_APPLICATION_ID — the application that owns the originating attribute.
• RELATED_DATABASE_OBJECT_NAME — the database object reached through the foreign-key relationship.
• RELATED_DB_OBJ_DISPLAY_NAME — the descriptive/display name of the related object.
• RELATED_ATTRIBUTE_CODE — the attribute code on the related object.
• RELATED_ATTRIBUTE_APPL_ID — the application ID owning the related attribute.
• RELATED_ATTR_DISPLAY_NAME — the user-facing label of the related attribute.
• RELATED_COLUMN_NAME — the physical column name of the related attribute.

Together these columns let a caller trace a relationship from a source table column to a target table column using only metadata.

Common Use Cases and Queries

Typical scenarios include resolving FK relationships for a given entity, validating attribute mappings during integrations, and driving dynamic SQL generation where the relationship is not hard-coded.

SELECT database_object_name,
       attribute_code,
       related_database_object_name,
       related_attribute_code,
       related_column_name
  FROM apps.oe_def_related_attr_v
 WHERE database_object_name = :object_name;

To find all related objects for a specific attribute and its owning application:

SELECT related_database_object_name,
       related_attr_display_name,
       related_column_name
  FROM apps.oe_def_related_attr_v
 WHERE attribute_code = :attribute_code
   AND attribute_application_id = :app_id;

Because the view is a metadata structure defined over AK objects, the result set is governed by the Flexfield/Key definitions registered in AK. It should be queried in read-only fashion; inserts or updates are not supported against a view of this type.