Search Results primary_key_name

Overview

The FND_PRIMARY_KEYS table is a core metadata repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the central registry for all primary and unique key constraints defined on application tables. This registration is fundamental to the EBS architecture, enabling the system to understand and enforce data integrity relationships dynamically. The table's existence supports key application framework features, including the generation of user interfaces, the validation of data relationships, and the operation of the Oracle Application Developer (OAD) tools. By maintaining this metadata, Oracle EBS can manage complex data models consistently across its numerous modules.

Key Information Stored

The table stores metadata that defines a unique or primary key constraint. Its structure is anchored by a composite primary key (FND_PRIMARY_KEYS_PK) consisting of APPLICATION_ID, TABLE_ID, and PRIMARY_KEY_ID. These columns link the key definition to its parent table in FND_TABLES. The PRIMARY_KEY_NAME column holds the constraint's name and, with APPLICATION_ID and TABLE_ID, forms a unique alternate key (FND_PRIMARY_KEYS_UK1). Additional columns, not detailed in the excerpt but standard in this table, typically include SEQUENCE_NUMBER (for ordering keys) and ENABLED_FLAG. The specific columns constituting the key are detailed in the related FND_PRIMARY_KEY_COLUMNS table.

Common Use Cases and Queries

This table is primarily queried for metadata analysis, data model documentation, and troubleshooting integrity issues. A common use case is to identify all registered primary keys for a specific application table to understand its unique identifiers. For example, to find all keys for the FND_USER table, one might execute a query joining FND_TABLES and FND_PRIMARY_KEYS. Another critical scenario involves diagnosing invalid foreign key relationships by verifying that a referenced primary key is correctly registered in this table. Developers may also query it to generate data model reports or to validate custom key registrations. Direct DML operations on this table are rare and should be performed using official Oracle Application Object Library APIs to maintain system integrity.

Related Objects

FND_PRIMARY_KEYS sits at the center of a key metadata relationship model. It has documented foreign key relationships with the following objects:

• FND_TABLES: The table is a child of FND_TABLES. The foreign key is on columns (APPLICATION_ID, TABLE_ID), ensuring every registered key belongs to a valid registered table.
• FND_FOREIGN_KEYS: This table is referenced as a parent by FND_FOREIGN_KEYS. Foreign keys are defined to point to a registered primary key via columns (PRIMARY_KEY_APPLICATION_ID, PRIMARY_KEY_TABLE_ID, PRIMARY_KEY_ID).
• FND_PRIMARY_KEY_COLUMNS: This table is a parent to FND_PRIMARY_KEY_COLUMNS. The child table stores the ordered list of columns that make up each key, linked via (APPLICATION_ID, TABLE_ID, PRIMARY_KEY_ID).

These relationships create a complete metadata chain from a table (FND_TABLES) to its keys (FND_PRIMARY_KEYS), the columns in those keys (FND_PRIMARY_KEY_COLUMNS), and finally to any foreign keys that depend on them (FND_FOREIGN_KEYS).