Search Results fk_entity_code

Overview

The OE_DEF_AK_FKEYS_V view is a dictionary-style reporting object owned by the APPS schema within the Oracle E-Business Suite Order Management (ONT) product. It exposes the relationship between unique keys and foreign keys registered in the Oracle Application Object Library (AK) metadata repository, but restricts the result set to those key definitions that are associated with objects catalogued in the Order Management extension table OE_AK_OBJECTS_EXT. In this sense the view provides a filtered, de-normalised projection of the generic AK key registry that is meaningful specifically for Order Management entities.

Because Oracle EBS represents many Order Management entities (orders, lines, holds, price adjustments, and similar constructs) through generic AK metadata rather than hard-coded relationships, this view is the practical bridge between the technical key definitions and a human-readable entity code. For reporting, integration, and diagnostic work, it allows a developer or analyst to enumerate which unique keys and foreign keys belong to a given Order Management entity without interrogating the underlying AK tables directly. The presence of two entity code columns, UK_ENTITY_CODE and FK_ENTITY_CODE, is notable: it permits a query to confirm that the unique-key side and the foreign-key side of a relationship resolve to the same (or related) entity codes, which is valuable when validating key metadata.

Underlying Base Objects

The view is defined over three referenced base objects, each accessed through an APPS synonym:

• AK_UNIQUE_KEYS — the AK registry of unique key definitions, supplying unique key name, database object name, and application identifier.
• AK_FOREIGN_KEYS — the AK registry of foreign key definitions, supplying the foreign key name and its associated database object name.
• OE_AK_OBJECTS_EXT — an Order Management extension table that maps AK database object names to Order Management entity codes.

In the view text the OE_AK_OBJECTS_EXT table is joined twice, once aliased D and once aliased E, equating each alias to the unique-key database object and the foreign-key database object respectively. The join conditions require matching APPLICATION_ID and UNIQUE_KEY_NAME between AK_UNIQUE_KEYS and AK_FOREIGN_KEYS, together with equal DATABASE_OBJECT_NAME values linking each AK object name to its OE_AK_OBJECTS_EXT row. The filter D.ENTITY_CODE IS NOT NULL ensures only key definitions with a recognised Order Management entity code are returned. The referenced objects are exposed as APPS synonyms.

Key Columns

The documented column list comprises seven columns, whose meaning is derived from the source tables:

• UNIQUE_KEY_NAME — the name of the unique key definition from AK_UNIQUE_KEYS.
• UK_DATABASE_OBJECT_NAME — the database object to which the unique key applies; note that the view text selects DATABASE_OBJECT_NAME from alias A.
• APPLICATION_ID — the application identifier that scopes the key definitions.
• FOREIGN_KEY_NAME — the name of the foreign key from AK_FOREIGN_KEYS.
• FK_DATABASE_OBJECT_NAME — the database object associated with the foreign key (alias B).
• UK_ENTITY_CODE — the Order Management entity code obtained from OE_AK_OBJECTS_EXT alias D, i.e. the entity for the unique-key side.
• FK_ENTITY_CODE — the Order Management entity code obtained from alias E, i.e. the entity for the foreign-key side.

This naming pattern accounts for the user search term uk_entity_code, which corresponds directly to the UK_ENTITY_CODE column.

Common Use Cases and Queries

A typical use is to discover the entity code associated with a given unique or foreign key, or to list the key relationships that belong to a specific Order Management entity. A simple lookup by entity code follows:

• SELECT UNIQUE_KEY_NAME, FOREIGN_KEY_NAME, UK_ENTITY_CODE, FK_ENTITY_CODE FROM OE_DEF_AK_FKEYS_V WHERE UK_ENTITY_CODE = :p_entity_code;
• SELECT UNIQUE_KEY_NAME, UK_ENTITY_CODE, FK_ENTITY_CODE FROM OE_DEF_AK_FKEYS_V WHERE FOREIGN_KEY_NAME = :p_fk_name;
• SELECT DISTINCT UK_ENTITY_CODE, FK_ENTITY_CODE FROM OE_DEF_AK_FKEYS_V;

These queries support metadata auditing, impact analysis before configuration changes, and troubleshooting when a key relationship is not resolving as expected. The view is read-only.