Search Results fnd_foreign_keys_s

Overview

FND_DICTIONARY_PKG is an internal Oracle E-Business Suite package body owned by the APPS schema that manages the Oracle Applications relational data dictionary at runtime. Rather than maintaining the definitions of tables, columns, indexes, primary keys, foreign keys, sequences, and views only as static source files, Oracle EBS stores these definitions as rows in a set of FND_* metadata tables so that components such as the generic loader (FND_LOAD_UTIL) and the About This Page / diagnostic facilities can query them dynamically. FND_DICTIONARY_PKG provides the programmatic interface through which those dictionary rows are inserted, updated, and removed. In effect it is the low-level engine that keeps the EBS data dictionary synchronized with the physical database objects that the product installation and patching utilities create.

Key Procedures and Functions

The package body exposes a set of symmetrical upload and remove routines, each dedicated to one dictionary entity type. The upload routines persist definitions into the dictionary tables, while the remove routines delete them, typically during object deletion or patch rollback.

• UPLOADTABLE — registers a table definition in the dictionary.
• UPLOADCOLUMN — registers a column belonging to a table.
• UPLOADHISTCOLUMN — registers a column used for historical (audit) tracking.
• UPLOADINDEX — registers an index definition.
• UPLOADINDEXCOLUMN — registers a column that participates in an index.
• UPLOADPRIMARYKEY — registers a primary key constraint definition.
• UPLOADPRIMARYKEYCOLUMN — registers a column belonging to a primary key.
• UPLOADFOREIGNKEY — registers a foreign key constraint definition.
• UPLOADFOREIGNKEYCOLUMN — registers a column participating in a foreign key; this is the routine directly associated with the FND_FOREIGN_KEYS_S table that the user searched for.
• UPLOADSEQUENCE — registers a database sequence definition.
• UPLOADVIEW — registers a view definition.
• UPLOADVIEWCOLUMN — registers a column belonging to a view.
• VIEWTEXTLENGTH — a utility returning the length of view source text, used when storing view definitions.
• REMOVECOLUMN, REMOVEINDEX, REMOVEPRIMARYKEY, REMOVEFOREIGNKEY, REMOVESEQUENCE, REMOVEVIEW, REMOVETABLE — counterpart deletion routines that purge the corresponding dictionary rows.

Thirty-four documented procedures exist in total; the listing above covers the named public routines described in the metadata.

Tables Accessed

The package reads and writes the FND dictionary tables through APPS synonyms. These include the base definition tables FND_APPLICATION, FND_COLUMNS, FND_COLUMNS_S, FND_FOREIGN_KEYS, FND_FOREIGN_KEYS_S, FND_FOREIGN_KEY_COLUMNS, FND_HISTOGRAM_COLS, FND_INDEXES, FND_INDEXES_S, FND_INDEX_COLUMNS, FND_PRIMARY_KEYS, FND_PRIMARY_KEYS_S, FND_PRIMARY_KEY_COLUMNS, FND_SEQUENCES, and FND_SEQUENCES_S. The base tables hold the current runtime dictionary state, while the *_S tables hold supplemental or secondary attribute data used by the loader and diagnostic reports. FND_APPLICATION is referenced to resolve the owning application of each object, and FND_HISTOGRAM_COLS supports histogram column metadata. The package also depends on FND_TABLES, FND_TABLES_S, FND_VIEWS, FND_VIEWS_S, and FND_VIEW_COLUMNS, which are implied by the view and table upload routines.

Usage Notes

FND_DICTIONARY_PKG is not an end-user API; it is invoked programmatically by EBS infrastructure. Its principal callers are the loader utilities (FND_LOAD_UTIL) and the table/index deployment logic used during installation, upgrade, and patching, which call the upload routines to keep the dictionary tables current. The remove routines are called when objects are dropped or when a patch reverses a previous object creation. The package additionally depends on APP_EXCEPTION, FND_MESSAGE, and FND_LOG for error handling and diagnostic logging, and on DBMS_SQL for dynamic SQL. No other database object references this package, and it is documented as referenced by four other packages. In the context of Oracle EBS 12.1.1 and 12.2.2 the behavior is consistent, with 12.2.2 offering the documented procedure set above. Custom code should not call these routines directly unless intentionally extending the EBS data dictionary, because doing so can desynchronize the dictionary from the physical schema. The FND_FOREIGN_KEYS_S table that prompted the search is populated through UPLOADFOREIGNKEY and UPLOADFOREIGNKEYCOLUMN, making this package the authoritative entry point for foreign key dictionary maintenance.