Search Results fnd_indexes_s

Overview

FND_XDFDICTIONARY_PKG is an Oracle E-Business Suite dictionary maintenance package owned by the APPS schema. Its purpose is to programmatically load and unload the metadata that defines the EBS database dictionary: the definitions of tables, columns, indexes, primary keys, foreign keys, sequences, and views. The "XDF" prefix denotes "Cross-Data Dictionary" functionality, and the package operates against the FND_* dictionary tables and their shadow (_S) tables that support the Applications DBA (AD) utilities and the Oracle Forms-based dictionary maintenance screens.

In EBS 12.1.1 and 12.2.2 the package remains VALID and is not referenced by any other database object, confirming its role as a standalone loader/unloader invoked directly by administrative utilities rather than as an internal dependency of the runtime product code.

Key Procedures and Functions

The package exposes 39 documented procedures and functions that fall into two logical groups: upload operations and removal operations.

• Upload procedures — UPLOADTABLE, UPLOADCOLUMN, UPLOADHISTCOLUMN, UPLOADINDEX, UPLOADINDEXCOLUMN, UPLOADPRIMARYKEY, UPLOADPRIMARYKEYCOLUMN, UPLOADFOREIGNKEY, UPLOADFOREIGNKEYCOLUMN, UPLOADSEQUENCE, UPLOADVIEW, and UPLOADVIEWCOLUMN. Each writes a specific dictionary entity into the corresponding FND_* registration tables. UPLOADHISTCOLUMN handles histogram column definitions, while the remaining uploads populate table, column, index, constraint, sequence, and view metadata respectively.
• Removal procedures — REMOVECOLUMN, REMOVEINDEX, REMOVEPRIMARYKEY, REMOVEFOREIGNKEY, REMOVESEQUENCE, REMOVEVIEW, and REMOVETABLE. These delete the corresponding dictionary registrations, providing symmetric maintenance of the dictionary.
• VIEWTEXTLENGTH — a function that returns the length of a view's defining text, used to validate whether a view definition fits the storage limit of the dictionary column before registration.

The naming convention maps one-to-one to dictionary entities, giving the package a complete create/register and delete/retire lifecycle for dictionary objects.

Tables Accessed

All dictionary tables are accessed through APPS synonyms. The package reads and writes the base registration tables and their shadow counterparts:

• Table and column metadata — FND_TABLES, FND_TABLES_S, FND_COLUMNS, FND_COLUMNS_S, and FND_HISTOGRAM_COLS (histogram column definitions).
• Index metadata — FND_INDEXES, FND_INDEXES_S, and FND_INDEX_COLUMNS.
• Constraint metadata — FND_PRIMARY_KEYS, FND_PRIMARY_KEYS_S, FND_PRIMARY_KEY_COLUMNS, FND_FOREIGN_KEYS, FND_FOREIGN_KEYS_S, and FND_FOREIGN_KEY_COLUMNS.
• Sequence and view metadata — FND_SEQUENCES, FND_SEQUENCES_S, FND_VIEWS, FND_VIEWS_S, and FND_VIEW_COLUMNS.
• Supporting reference tables — FND_APPLICATION, FND_OBJECT_TABLESPACES, and FND_USER, used to resolve application ownership, tablespace targets, and audit identity for the uploaded definitions.

The "_S" shadow tables hold the base (seed) dictionary definition, while the non-shadow tables hold the deployed definition; the package coordinates both so that dictionary registration and deployment stay synchronized.

Usage Notes

FND_XDFDICTIONARY_PKG is not invoked by end-user forms at runtime. It is typically called by dictionary maintenance utilities, concurrent programs, and AD (Applications DBA) administration code that register the metadata of newly created tables, columns, indexes, constraints, sequences, or views into the EBS data dictionary. Custom development teams sometimes invoke it directly after DDL creation to register custom schema objects so that they appear in dictionary-driven screens and utilities such as those supporting the FND_COLUMNS_S "fnd_columns_s" search path. Because the package is documented as not referenced by any other database object, callers must invoke it explicitly; there is no automatic trigger path. When used in custom code, the upload procedures should always be paired with the corresponding removal procedures so the base and shadow dictionary tables remain consistent.