Results for “primary_key_name”

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

Overview

FND_PRIMARY_KEYS is a metadata repository table owned by the APPLSYS schema within the Oracle Application Object Library (FND) product. It stores the primary and unique keys that have been registered with Oracle E-Business Suite for the tables comprising the EBS data dictionary. Every table that participates in the AOL dictionary framework has its key definitions cataloged here, enabling the concurrent manager, flexfield engine, audit trail, and other dictionary-driven features to resolve row identity reliably without hard-coded knowledge of individual application tables.

In Oracle EBS 12.1.1 and 12.2.2, the table is a structural component of the FND dictionary rather than a transactional or configuration table. Its rows are seeded and maintained by the system as applications are installed, patched, or upgraded. The documented physical schema shows 14 columns and two unique indexes (FND_PRIMARY_KEYS_U1 and FND_PRIMARY_KEYS_U2), and the table carries online editioning support through the ZD_EDITION_NAME column, consistent with the 12.2.x edition-based redefinition architecture.

From a dimensional modeling perspective, the mined foreign-key topology classifies FND_PRIMARY_KEYS as hub-leaning. It behaves as a natural business-key anchor that other dictionary tables reference, rather than as a transactional link or a mutable descriptive satellite.

Key Information Stored

The surrogate primary key FND_PRIMARY_KEYS_PK is composed of three columns: APPLICATION_ID, TABLE_ID, and PRIMARY_KEY_ID. This composite uniquely identifies each registered key definition. Two unique indexes serve as business-key candidates: FND_PRIMARY_KEYS_U1 on APPLICATION_ID, TABLE_ID, PRIMARY_KEY_ID, and ZD_EDITION_NAME; and FND_PRIMARY_KEYS_U2 on PRIMARY_KEY_NAME, APPLICATION_ID, TABLE_ID, and ZD_EDITION_NAME.

The most significant columns include:

• APPLICATION_ID and TABLE_ID — the composite locator identifying the owning application and the specific dictionary table whose key is registered.
• PRIMARY_KEY_ID — the sequential identifier distinguishing multiple key definitions registered against the same table.
• PRIMARY_KEY_NAME — the descriptive name of the key (for example, a table's primary key constraint name), used as the business-key counterpart in FND_PRIMARY_KEYS_U2.
• PRIMARY_KEY_TYPE — classifies whether the registered key is a primary key or a unique key.
• AUDIT_KEY_FLAG — indicates whether the key participates in audit-trail processing.
• ENABLED_FLAG — controls whether the key definition is currently active in the dictionary.
• DESCRIPTION — free-text descriptive context for the key registration.
• ZD_EDITION_NAME — the edition label supporting 12.2.x edition-based redefinition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO audit columns recording row provenance and modification history.

Common Use Cases and Queries

Typical scenarios center on dictionary introspection and troubleshooting of dictionary-driven features. A developer or DBA may need to discover which key columns are registered for a given table, or to reconcile a custom table registered with AOL against its declared key. A representative query joins the key header to its column detail:

• Resolve key definitions for a table: SELECT k.primary_key_id, k.primary_key_name, k.primary_key_type FROM applsys.fnd_primary_keys k WHERE k.application_id = :app_id AND k.table_id = :table_id AND k.enabled_flag = 'Y';
• List the constituent columns of a key by joining FND_PRIMARY_KEY_COLUMNS on APPLICATION_ID, TABLE_ID, and PRIMARY_KEY_ID.
• Find foreign keys that depend on a given primary key by joining FND_FOREIGN_KEYS on PRIMARY_KEY_APPLICATION_ID, PRIMARY_KEY_TABLE_ID, and PRIMARY_KEY_ID.
• Audit registration completeness by comparing FND_TABLES rows against their corresponding FND_PRIMARY_KEYS entries to detect tables lacking a registered key.

Reporting use cases include data-dictionary inventories, impact analysis before patching or upgrading custom schema objects, and validation of audit-trail configuration enabled through AUDIT_KEY_FLAG.

Related Objects

The following objects reference or are referenced by FND_PRIMARY_KEYS through documented foreign-key relationships:

• FND_TABLES — the parent dictionary table; joined on APPLICATION_ID and TABLE_ID.
• FND_FOREIGN_KEYS — references this table via PRIMARY_KEY_APPLICATION_ID, PRIMARY_KEY_TABLE_ID, and PRIMARY_KEY_ID, expressing dependency from foreign-key definitions back to their referenced primary keys.
• FND_PRIMARY_KEY_COLUMNS — the child detail table holding the ordered column list for each key, joined on APPLICATION_ID, TABLE_ID, and PRIMARY_KEY_ID.

Together these three related objects form the complete AOL key-definition subsystem, allowing EBS components to resolve row identity and constraint relationships across the entire application dictionary.