Results for “from_object_description”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AK_FOREIGN_KEYS_VL is a validation and translation view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AK (Common Modules-AK) product, the Oracle Application Object Library–adjacent framework that supports the Oracle Applications Object Registry, descriptive flexfields, and the Applications Dictionary (AD) style metadata definitions used across the EBS technology stack. The object is documented in ETRM with a description of "10SC ONLY," indicating that its registration and availability pertain specifically to the 10SC reference configuration within the ETRM extract, and that general availability across all environments is not implied by the metadata. The view is marked VALID.
Functionally, the view presents a flattened, language-aware projection of foreign key definitions registered in the AK repository. A foreign key record in AK describes a relationship between two database objects (tables or views) via a named unique key, together with directional display labels (From/To and To/From). AK_FOREIGN_KEYS_VL exposes both the technical identity of those objects (database object names) and their translated display names, making it suitable for reporting and integration where human-readable relationship metadata is required alongside the underlying catalog references.
In EBS 12.1.1 and 12.2.2 the view is used primarily within the AK framework and by diagnostics or data-model browsing utilities rather than by core transactional flows. It is a read-only reporting surface over the AK dictionary.
Underlying Base Objects
The documented base objects are AK_FOREIGN_KEYS, AK_FOREIGN_KEYS_TL, AK_OBJECTS, AK_OBJECTS_TL, and AK_UNIQUE_KEYS, all referenced in ETRM as SYNONYMs resolving to the APPS tables.
- AK_FOREIGN_KEYS (AFK) — the driving table, supplying FOREIGN_KEY_NAME, DATABASE_OBJECT_NAME, UNIQUE_KEY_NAME, APPLICATION_ID, the ATTRIBUTE1–15 flex columns, and WHO audit columns.
- AK_FOREIGN_KEYS_TL (AFKT) — the translation table for foreign key display text, supplying FROM_TO_NAME, FROM_TO_DESCRIPTION, TO_FROM_NAME, and TO_FROM_DESCRIPTION, joined on FOREIGN_KEY_NAME with LANGUAGE restricted to USERENV('LANG').
- AK_UNIQUE_KEYS (AUK) — joined on UNIQUE_KEY_NAME to anchor the relationship to the referenced unique key definition.
- AK_OBJECTS (AO1, AO2) — outer-joined via DATABASE_OBJECT_NAME to resolve the To-side and From-side object identities.
- AK_OBJECTS_TL (AOT1, AOT2) — outer-joined translation sources for the To-side and From-side object names and descriptions, also filtered by USERENV('LANG').
The outer-join (+) syntax on the object tables allows foreign key rows to survive even where the corresponding object registration or translation is absent.
Key Columns
- ROW_ID — AFK.ROWID, exposed as the row identifier.
- FOREIGN_KEY_NAME / UNIQUE_KEY_NAME — the foreign key identifier and its associated unique key.
- DATABASE_OBJECT_NAME — the database object on which the foreign key is defined.
- TO_/FROM_OBJECT_NAME, TO_/FROM_OBJECT_DESCRIPTION, TO_/FROM_DATABASE_OBJECT_NAME — translated and physical names of the two ends of the relationship.
- FROM_TO_NAME, FROM_TO_DESCRIPTION, TO_FROM_NAME, TO_FROM_DESCRIPTION — directional display labels from AK_FOREIGN_KEYS_TL.
- APPLICATION_ID — owning application.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield segments.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — WHO audit columns.
Common Use Cases and Queries
Typical uses include enumerating relationships for a given database object, auditing foreign key metadata by application, and joining AK relationship metadata into custom data-model documentation.
- List all relationships for a specific table:
SELECT foreign_key_name, from_object_name, to_object_name, from_to_description FROM apps.ak_foreign_keys_vl WHERE database_object_name = :p_object; - Filter by owning application with the Translated To-object name:
SELECT application_id, database_object_name, to_object_name, to_database_object_name FROM apps.ak_foreign_keys_vl WHERE application_id = :p_app ORDER BY database_object_name; - Report the flex attribute context alongside relationship labels:
SELECT foreign_key_name, attribute_category, attribute1, from_to_name FROM apps.ak_foreign_keys_vl;
Because LANGUAGE predicates bind to USERENV('LANG'), all queries return translated text for the caller's session language, and the view should be queried through the APPS synonyms in a properly initialized EBS session.
-
View: AK_FOREIGN_KEYS_VL 12.2.2
10SC ONLY
APPS.AK_FOREIGN_KEYS_VL·↳ AK_FOREIGN_KEYS·↳ AK_FOREIGN_KEYS_TL·↳ AK_OBJECTS·Explore AK module →
-
View: AK_FOREIGN_KEYS_VL 12.1.1
10SC ONLY
APPS.AK_FOREIGN_KEYS_VL·↳ AK_FOREIGN_KEYS·↳ AK_FOREIGN_KEYS_TL·↳ AK_OBJECTS·Explore AK module →
-
eTRM - AK Tables and Views 12.1.1
-
eTRM - AK Tables and Views 12.2.2