Search Results fnd_primary_keys_s

Overview

The APPS.AD_DD package body is the Oracle E-Business Suite Application Object Library (AD) utility responsible for dynamic registration of database schema objects within the FND metadata repository. In Oracle EBS 12.1.1 and 12.2.2, this package serves as the programmatic interface through which tables, columns, and primary key definitions are catalogued in the FND data dictionary tables. The package is classified under the ETRM taxonomy as an OTHER API, reflecting its role as an internal administrative utility rather than a published business integration interface. Its principal business function is to keep the FND catalog synchronized with the physical database objects that Oracle Forms, concurrent programs, and flexfield infrastructure rely upon at runtime. The package is shipped in a VALID state in the APPS schema and is not referenced by any other database object, confirming its position as a top-level administrative entry point.

Key Procedures and Functions

The ETRM metadata documents eight procedures within APPS.AD_DD, organized around the lifecycle of tables, columns, and primary keys.

• REGISTER_TABLE — Registers a database table in the FND application dictionary, establishing its identity for downstream metadata consumers.
• REGISTER_COLUMN — Registers an individual column definition against a previously registered table.
• REGISTER_PRIMARY_KEY — Defines a primary key constraint record for a registered table.
• UPDATE_PRIMARY_KEY — Modifies an existing primary key definition when the underlying schema changes.
• REGISTER_PRIMARY_KEY_COLUMN — Associates a specific column with a registered primary key, building the composite key column list.
• DELETE_PRIMARY_KEY_COLUMN — Removes a column association from a primary key definition.
• DELETE_TABLE — Removes a table and its dictionary entries from the FND registry.
• DELETE_COLUMN — Removes a column record from the FND registry.

These procedures collectively provide full CRUD coverage over the FND table, column, and primary key metadata.

Tables Accessed

APPS.AD_DD reads and writes the core FND data dictionary tables through APPS synonyms. FND_TABLES and its translated companion FND_TABLES_S store table-level registrations. FND_COLUMNS and FND_COLUMNS_S hold column-level metadata. Primary key definitions reside in FND_PRIMARY_KEYS and FND_PRIMARY_KEYS_S, while FND_PRIMARY_KEY_COLUMNS maintains the association between keys and their constituent columns. FND_APPLICATION is referenced to validate the owning application for registered objects. DUAL is used for singleton queries and sequencing logic. The dependency listing explicitly confirms that the package references FND_PRIMARY_KEYS_S — the exact object matching the user's search term "fnd_primary_keys_s" — underscoring that primary key metadata management is a central responsibility of this package.

Usage Notes

APPS.AD_DD is typically invoked during environment setup, patch application, and custom schema registration rather than during routine transactional processing. Oracle's AD utilities, including the table registration and dictionary generation processes, call this package to publish new or altered schema objects. Developers registering custom tables for use with EBS Forms, flexfields, or the concurrent manager invoke these procedures manually or through scripted installation routines. Because the package writes directly to shared FND dictionary tables, it should be executed with the APPS schema credentials and only after the physical DDL has completed. The absence of inbound dependencies indicates that no standard product code calls AD_DD at runtime, so changes are administrative in nature. Each procedure should be treated as a controlled metadata operation; improper registration can desynchronize the FND catalog from the physical database and affect Forms and flexfield functionality.