Search Results fnd_dictionary_pkg




Overview
Explore in AI Chat

Overview

FND_DICTIONARY_PKG is an Oracle E-Business Suite Applications (APPS) schema package responsible for maintaining the Application Object Library metadata that underpins the Oracle EBS data dictionary. In Release 12.1.1 and 12.2.2, the package provides the programmatic interface used to register and de-register database objects such as tables, columns, indexes, primary keys, foreign keys, sequences, and views within the FND_* dictionary tables. These dictionary entries are the foundation upon which EBS features such as Flexfields, Help/Diagnostics, the Oracle Applications Tablespace Model, and various DBA utilities depend.

The package is classified as an OTHER API, indicating that it is an internal utility rather than a supported public API intended for customer extension. Its status is VALID in the supplied ETRM metadata, and it depends only on the SYS.STANDARD package, confirming that it operates almost entirely against FND dictionary tables and PL/SQL primitives.

Key Procedures and Functions

The ETRM repository documents 34 procedures and functions organized into logical families:

  • Upload procedures — UPLOADTABLE, UPLOADCOLUMN, UPLOADHISTCOLUMN, UPLOADINDEX, UPLOADINDEXCOLUMN, UPLOADPRIMARYKEY, UPLOADPRIMARYKEYCOLUMN, UPLOADFOREIGNKEY, UPLOADFOREIGNKEYCOLUMN, UPLOADSEQUENCE, UPLOADVIEW, and UPLOADVIEWCOLUMN: read the current physical database definition of the named object and insert or update the corresponding dictionary rows in the FND_* tables.
  • Remove procedures — REMOVECOLUMN, REMOVEINDEX, REMOVEPRIMARYKEY, REMOVEFOREIGNKEY, REMOVESEQUENCE, REMOVEVIEW, and REMOVETABLE: delete the corresponding dictionary records when an object is dropped or de-registered.
  • VIEWTEXTLENGTH — a utility used to determine the length of a view's defining SQL text so that it can be stored within the dictionary column constraints.

The exact parameter lists are not reproduced here; they are intentionally not inferred from the metadata. Each procedure is focused on a single object type so that dictionary upload and removal can be scripted or invoked individually.

Tables Accessed

The package reads and writes the FND_* dictionary tables via APPS synonyms. Documented tables include FND_APPLICATION (application registry), FND_COLUMNS and FND_COLUMNS_S (column definitions and their translation shadow), FND_INDEXES and FND_INDEXES_S with FND_INDEX_COLUMNS, FND_PRIMARY_KEYS and FND_PRIMARY_KEYS_S with FND_PRIMARY_KEY_COLUMNS, FND_FOREIGN_KEYS and FND_FOREIGN_KEYS_S with FND_FOREIGN_KEY_COLUMNS, FND_SEQUENCES and FND_SEQUENCES_S, and FND_HISTOGRAM_COLS. The _S (shadow) tables are populated in tandem with the base tables to support runtime dictionary access at the NLS language level.

Usage Notes

FND_DICTIONARY_PKG is referenced by several other APPS packages, including AD_MO_UTIL_PKG, FND_DATADICT_PKG, FND_PROFILE_OPTIONS_PKG, and FND_USER_PKG, and it recurses into itself in the dependency tree. It is typically invoked by dictionary-maintenance forms and concurrent programs that ship with EBS, and by AD utilities such as the Applications DBA (ADADMIN) tooling when registering or migrating schema objects. Custom code should not call this package directly; Oracle's supported route for adding dictionary entries is through the standard Oracle Forms dictionary maintenance screens, which call these procedures behind the scenes. Direct invocation should be reserved for controlled patching or diagnostic scenarios where the standard forms cannot be used.