Search Results fk_entity_code

Overview

APPS.OE_DEF_AK_FKEYS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It is registered in Oracle's application design metadata under the FND Design Data name ONT.OE_DEF_AK_FKEYS_V, placing it within the Order Management (ONT) product family. The view exposes a flattened, query-friendly projection of the foreign-key and unique-key relationships that underpin the Oracle Order Management defaulting framework. It is this framework that drives how attribute values are automatically defaulted onto order headers, lines, and related entities during order entry and processing.

Oracle classifies the object with the warning, "Oracle Internal Use Only": Oracle Corporation does not support access to Oracle applications data using this object except from standard Oracle Applications programs. Consequently, the view is intended for diagnostic, support, and tracing purposes rather than as a public integration or reporting interface. It carries a status of VALID, and its view type is documented as Internal.

Underlying Base Objects

OE_DEF_AK_FKEYS_V is defined over three documented base objects, each referenced through a synonym:

• AK_FOREIGN_KEYS — the Oracle Application Object Library (AK) repository of foreign-key definitions, supplying foreign-key names and their associated database objects.
• AK_UNIQUE_KEYS — the companion AK repository of unique-key definitions, supplying unique-key names and their database objects.
• OE_AK_OBJECTS_EXT — an Order Management extension object that provides entity-level context, mapping the AK-registered keys to the specific Order Management entities involved in defaulting.

By joining these three sources, the view reconciles a unique key and its owning entity with the corresponding foreign key and entity, giving a consolidated picture of how unique-key/foreign-key pairs are wired together inside the defaulting framework. The view is consumed by APPS.OE_DEFAULTING_FWK_PUB, the public package that implements Order Management defaulting logic, confirming that the view exists to support the internal workings of that package rather than end-user reporting.

Key Columns

The view exposes seven columns, all documented at their declared lengths:

• UNIQUE_KEY_NAME (VARCHAR2 30) — name of the unique key definition involved in the relationship.
• UK_DATABASE_OBJECT_NAME (VARCHAR2 30) — the database object that carries the unique key, allowing the analyst to trace the key back to its underlying table or entity.
• APPLICATION_ID (NUMBER 15) — the application identifier, typically pointing to the owning application such as ONT.
• FOREIGN_KEY_NAME (VARCHAR2 30) — name of the corresponding foreign key definition.
• FK_DATABASE_OBJECT_NAME (VARCHAR2 30) — the database object that carries the foreign key.
• UK_ENTITY_CODE (VARCHAR2 15) — the entity code associated with the unique key, identifying the business entity on the unique-key side of the relationship.
• FK_ENTITY_CODE (VARCHAR2 15) — the entity code associated with the foreign key, identifying the business entity on the referencing side.

Taken together, the columns let a developer or support analyst identify both ends of each defaulting-related key relationship without navigating the individual AK repository tables directly.

Common Use Cases and Queries

The principal use case is troubleshooting and documenting Order Management defaulting behavior—for example, verifying which unique-key/foreign-key pair links two entities, or confirming the entity codes associated with a given key before raising a service request or designing an extension. A simple query returns the full relationship set:

• SELECT UNIQUE_KEY_NAME, UK_DATABASE_OBJECT_NAME, APPLICATION_ID, FOREIGN_KEY_NAME, FK_DATABASE_OBJECT_NAME, UK_ENTITY_CODE, FK_ENTITY_CODE FROM APPS.OE_DEF_AK_FKEYS_V;
• SELECT UK_ENTITY_CODE, FK_ENTITY_CODE, UNIQUE_KEY_NAME, FOREIGN_KEY_NAME FROM APPS.OE_DEF_AK_FKEYS_V WHERE UK_DATABASE_OBJECT_NAME = :table_name;
• SELECT UNIQUE_KEY_NAME, FOREIGN_KEY_NAME FROM APPS.OE_DEF_AK_FKEYS_V WHERE APPLICATION_ID = :app_id ORDER BY UNIQUE_KEY_NAME;

Because the object is marked Oracle Internal Use Only, these queries are best confined to development, diagnostic, and support contexts, and any reliance on its columns should be validated against the corresponding Oracle Applications programs rather than treated as a supported interface.