Search Results fnd_datadict_pkg

Overview

FND_DATADICT_PKG is a dictionary-level utility package owned by the APPS schema in Oracle E-Business Suite. Its name and documented contents indicate that it provides programmatic access to data dictionary maintenance operations—specifically, the renaming of database tables through a PL/SQL interface rather than through direct DDL executed by an administrator. In the EBS architecture, the FND prefix denotes a foundation-layer object, and the FND_DATADICT naming convention places this package alongside other Oracle Application Object Library (FND) components that manage metadata about the applications themselves. The package is classified as OTHER in the ETRM registry, meaning it is not published as a public integration API such as an open interface or a business event subscription; it is an internal support routine. The object status is VALID in the documented environment, confirming that the package successfully compiles and that its dependencies resolve at runtime.

Key Procedures and Functions

• RENAME_TABLE — The single documented routine in this package. As the name indicates, it performs the renaming of an existing database table, encapsulating the operation so that it can be invoked from PL/SQL context rather than through an interactive SQL session. No parameter list is documented in the ETRM metadata; the procedure should be treated as an internal utility whose call signature must be confirmed directly from the package specification in the target environment before any use.

Because the package specification exposes only this one procedure, FND_DATADICT_PKG is a narrow-purpose utility rather than a general dictionary access layer. There are no documented functions for retrieving column definitions, validating object names, or managing other dictionary object types.

Tables Accessed

The ETRM metadata does not enumerate any base tables referenced through APPS synonyms for this package. Its dependency listing shows only SYS and the STANDARD package, which reflects the fact that the package operates on database objects through dynamic DDL rather than by querying or updating application data tables. A routine that renames a table necessarily touches the data dictionary itself—the SYS-owned views and base tables that record object names and definitions—but those are kernel structures, not EBS application tables. Consequently, there are no FND application tables such as FND_TABLES or FND_COLUMNS documented as being read or written by this package.

Usage Notes

FND_DATADICT_PKG is referenced by zero other packages according to the documented dependency data, and it is not exposed through any concurrent program or Oracle Forms interface described in the metadata. This strongly suggests it is a maintenance-time utility, invoked manually or from installation and upgrade scripts when a table must be renamed as part of a patch, migration, or schema reorganization. Typical invocation would be from a SQL*Plus or SQL Developer session connected as APPS, or from a custom PL/SQL script executing the procedure by name. The following operational cautions apply:

• Renaming a table via DDL invalidates dependent objects. Any views, synonyms, PL/SQL packages, or triggers that reference the original table name will be invalidated until recompiled.
• The operation should be performed during a maintenance window, since active concurrent programs or online users holding locks on the table will cause the rename to fail or block.
• Because the package is not a published API, its behavior is not guaranteed across patch levels. Oracle may modify or remove the procedure without notice, so custom code should not build long-term dependencies on it.
• Confirm the exact parameters from the package specification in the target instance before calling the procedure, as the ETRM documentation does not record the signature.

Given its limited scope and absence of dependents, FND_DATADICT_PKG should be regarded as an internal Oracle utility rather than a supported extension point for custom development.